Click the Browse button to select an Excel File that contains the source of the data to convert. Control Conversion only supports Excel as the Data Source type.
Click the drop-down button to select a Control Binding Template file to use as the source of Control Bindings. Clicking the Browse button will display a list of all Control Binding type (*.xcb) files that reside in the loaded Solution. This template defines the control bindings that will be used to bind the data from the Excel DataSource to the target control strategy parameter data.
Click this button to build a data Model using the attached Excel Data Source. The Data Source Model provides Control Strategy data and references used when analyzing Control strategies for displaying a Control Graph.
Click the Browse button to select a document file to attach to this Control Conversion Template as a reference. You can open the document using its registered Open Verb by clicking the View button.
Click this button to open the attached document reference. The registered Open Verb is used to open the file. For example if the document is an Excel file, then the Open Verb should be registered to use Excel as the application to open the file.
Click the Browse button to select a PKS XML Configuration file to use as an empty Control Module. This Control Module should not contain any embedded Function blocks. This function supports hierarchical embedded Control Module development.
Specify the suffix to append to all auto-generated container Control Module strategies. The container Control Module that is generated is used to contain (embed) Control strategies that are generated as a result of executing a Data Collection saved from this view in a Workflow Control Conversion Activity task. This is currently not supported.
Click this button to define the mapping between Honeywell PKS XML configuration templates and Control Architect defined identifiers. Control Architect provides a solution for migrating Honeywell legacy Control System platforms to EPKS that require PKS XML configuration templates that contain a specific Function Block structure. During the conversion analysis the default BasedOn type may need to be changed to properly build the converted Control Strategy. The conversion analyzer will define a new BasedOn Template that is predefined in this set of mappings. This button is only visible if a PKS type is chosen as the Output Adapter type.
Click this button to view the last saved Data Collection view results. When a Data Collection is generated you must save the results that are then used in a Workflow Control Conversion Activity task. When the Control Conversion Activity task has been executed, you can view the results of this activity in this saved Data Collection. The status of all Parameter item conversions are automatically updated in the Data Collection.
Select from the drop-down list a Data Table to use as the source of the data. Each Worksheet found in the attached Excel Workbook file is identified as a Table in this list. You can specify multiple control conversion bindings in this DataGrid where each DataGrid row represents a binding between a single DataSource table (Excel Worksheet) and a target set of Control properties (parameters) that represent a Control Strategy.
Select the data column in this Data Table that represents the Primary Key to use as the data that uniquely identifies each entity in the data. This will typically be a data column that identifies the Control Strategy or Entity name.
Specify an expression that is used to filter the data within the selected Data Table. You would typically use this to filter a scope of strategies that will conform using the adapter specified Control Binding Template file and its corresponding BasedOn file.
Select the Control Binding Template that will be used that defines the binding or mapping between source data and the target Control Strategy parameters. The Control Binding template file that is attached supports multiple control binding types.
Click here to change the BasedOn Template file that will be used as the basis for all output files that are created. This file displayed here is the file that was used to import the Control properties for the specified Target Control Property source in the referenced Control Binding Template. You can click within this data cell to display a Browse button that will allow you to change the file reference.
By default all Data Source entities visible in the Data Source view become the scope when executing the Data Collection. You can choose to define this scope by selecting one more more Data Source rows in the Data Source view and clicking the Define Scope button.
This status reflects the current scope of Data Source entities to use when the Data Collection task is executed. By default all entities contained in the selected Data Source Table are defined as the scope. If you choose to redefine this scope, you can click the drop-down button in this cell to display the current scope list of entities. You can also remove entities from this list by selecting them and clicking the Delete key to remove them.
Select from the drop-list a Special Function that is to be the basis for the Conversion analysis. Control Architect provides several special function types that provide support for legacy Honeywell Control System platform conversions.
Specify a Container name here that will be applied to all Control modules that are generated. This provides support for hierarchical Control Module development. When a name is specified here, the Data Collection task will automatically parent all generated Control modules to this Container name. The containing Control Module that is also generated will use the PKS XML configuration file specified in the options. You can specify a hierarchy of embedded Control modules to create as in "HIWAY01\EC_BOX32". A task with a hierarchical specification such as this example would embed the Control Module in the container named "EC_BOX32". The container named "EC_BOX32" would itself be embedded in the container Module "HIWAY01".
Displays the current filter expression that is active for the Data Source view. By default when the Data View Hyperlink is clicked to view its Table data, the expression that is specified in the Adapter binding Filter Expression column is used as the filter expression source. You can also change this expression here to change the filter temporarily without changing the Adapter binding filter expression.
Click this button to choose the columns that are displayed in the Data Source view. By default, the first 100 column found in the Data Source Table are displayed to improve performance when working with the Data Source view. Some Data Source tables such as a table that holds Honeywell Application Module Regulatory types may contain a 1000 or more columns depending on the size of any referenced CL Package items.
Specify the number of columns to view in the Data Source View. Data Source tables such as [CUSTOMAM] may contain hundreds of columns that can impact the performance of the DataGrid View that displays the Data Source table data. It is recommended to keep the number of visible columns in this view < 200. By default the view will pick the specified column count in alphabetic order. In special cases where you need to view more parameters click the Columns picker and check the additional columns to view.
When analyzing data to display in the Control Graph View it is required that certain columns be visible in order to properly graph data connections. For example in an Extended Controller the columns ZSLTSRC and ZSIGNAL must be visible to be able to read the data references specified in these data columns for display in the Control Graph View.
Click this button to refresh the Excel Data Source connection. When you make changes to the referenced Excel file while this view is opened, click this button to refresh the connection to be able to see the changed data.
Choose this option to support an Excel document where Entity names are duplicated for example in the NAME column. This allows you to develop Excel Data sources where Parameters are defined on an Excel row basis vs. column basis.
Specify the number of Excel data rows to skip beginning with the1st row. Use this to skip unwanted data that is often embedded in the beginning of an Excel document.
Choose this option when generating a Data Collection to rebuild the output entities and not treat existing output entities as being modified. This is a one-shot option and will be reset after executing a Data Collection.
You will often want to use this option if the target set of properties has changed, which may invalidate the existing output entities as new Parameters may need to be added or the structure of the configuration document has change such as adding/deleted an embedded block.
Choose this option to auto-build a containing Module for entities that are generated. The specified Control Module container Template file along with the specified suffix are used to generate the new Control Module entity.
