Workflow Offline Engineering

Workflow Offline Engineering
  1. For the Logical and User View, create one configuration file each (see below).
    Note: No configuration files are needed if none of the two views are used.
  1. (Optional) In the EDE file, supplement the function to the given data points.
  1. Check import rules.
  1. Import the EDE data.
  1. Supplement the imported data points with Function (only if this is not done under Step 2).

Creating/Modifying Configuration Files

  • Configuration files for the Logical or User View (optional) are created. The imported objects are only displayed in Management View if no configuration file is available.
  1. Check the delimiters in your EDE file. Open the EDE file using a text editor.
  1. Using a text editor, create a new Hierarchy-User.txt file or Hierarchy-Logical.txt file (see example at the end of the workflow).
    Note: The mapping files must be in the same folder as the import files.
  1. (Optional) Add the correct code-page information for encoding, for example, !encoding!UTF-8.
  1. (Optional) In separators-1 change the default separator (;) for the EDE file according to your requirements.
  1. (Optional) In separators-2 change the delimiter for the State text and Unit text columns according to your requirements.
  1. (Optional) In separators-3 change the separator (|) for languages according to your requirements.
  1. In the Reference column, set the hierarchy mapping (default column = keyname).
    Note: If the Keyname field is empty on an object, no Logical View or User View is created for this object. The object is, however, displayed in Management View.
  1. Define the following entries (for example, location, building, floor, etc.) for each hierarchy level:
  • Hierarchy Separator for the reference column (for example, _ ' :). Required for parsing the various hierarchy levels.
  • Minimum length of the corresponding hierarchy level.
  • Maximum of the corresponding hierarchy level.
    Note: For fixed field lengths, the minimum and maximum length must be the same and the hierarchy separator left out.
  • State text references to existing text groups.
  • (Optional) A description of the corresponding hierarchy level.
    Note: The description for a virtual hierarchy object is displayed in System Browser.
  1. Select File > Save.
  1. Copy the file to the folder where the EDE file is located.
  1. For multilingual support, check that the order in the TXT files and EDE files match the definition on the System Management Console.

Example for Hierarchy-User.txt or Hierarchy-Logical.txt file with three languages (en-US, fr-FR and de-DE):

!encoding!utf-8

#separators-1#;

#separators-2#,;

#separators-3#|

:column-name:keyname

,_,1,15,Location|Location|Standort

,:,1,15,Building|Bâtiment|Gebäude

,_,1,15,Floor|Plancher|Stockwerk

,_,1,20,Plant|Installation|Anlage

,_,1,20,Object|Objet|Objekt

,_,1,25,Data point|Point|Datenpunkt

(Optional) Extension family name

The selected files are checked for proper syntax prior to import. If an error message is displayed, click Open Log for additional information.
If the Hierarchy-User.txt and Hierarchy-Logical.txt files are used, the minimum and maximum length of the hierarchy level of the data point is checked. An error message is displayed if it is too short or too long. The data point is created in the database, but not visible for the corresponding view.

Supplement EDE File with Function

  1. In Excel, open the EDE file (CSV or XLSX).
  2. Add the column name Function on the same line as the keyword Keyname.
  3. In the Function column, enter a unique function-key for each data point.
  4. Click Save.

Creating a Function Key

Add the Function to the EDE file, if:

  • The third-party BACnet device has a standardized data point name
  • Multiple data points have the same function
  • Future projects have the same data point names of the third-party BACnet device

Workflow

  1. Supplement function key in the EDE file.
  2. Extend import rules for third-party BACnet devices.
  3. (Optional) Export the import rules for additional projects.
  4. (Optional) Import import rules to the new project
  1. Select Project > System Settings > Libraries > L1 Headquarter > BA > Device > BACnet > Import rules.
  1. Click Modify and OK.
  • A project-specific library is created.
  1. Select Project > System Settings > Libraries > L4 project > BA > Device > BACnet > Import rules.
  1. In the Import rules tab, open the Instance Attributes Mapper expander.
  1. Click Add.
  • A new function key line is added.
  1. In the Standard Feature drop-down list box, enter the Reference column text field in the EDE file (for example, FunctionKey).
  1. Define the FunctionKey entries based on the following example:
  • Value of FunctionKey: T_SU
  • Function name: Sensor
  • Discipline: Building automation
  • Subdiscipline: Air handling
  • Type: Heating coils
  • Subtype: Preheater
  1. Repeat Steps 6 to 8 for each function key.
  1. Click Save .
  1. Export the created function keys.
Definition of a Function Key

Exporting a Function Key

Scenario: You want to reuse the configuration in another project.

  • The function keys are created on project level L4.
  1. Select Project > System Settings > Libraries > L4 project > BA > Device > BACnet > Import rules.
  1. In the Import rules tab, open the Instance Attributes Mapper expander.
  1. Click Export.
  1. In the dialog box, select a path and enter a name.
  1. Click Save.
  1. Save the file to another medium.
  • All function keys for L1 – L4 are exported.

Importing Function Keys

Scenario: You created a configuration for another project and want to reuse it on this project.

  • A function key file is available.
  • A L4 project level is available. If the L4 project level is not available, you can create it with Modify .
  1. Select Project > System Settings > Libraries > L4 project > BA > Device > BACnet > Import rules.
  1. In the Import rules tab, open the Instance Attributes Mapper expander.
  1. Click Import.
  1. Select the folder and file name.
  1. Click Open.
  • The function keys are imported to the project.

Conduct Initial EDE Data Import

  • The network and BACnet driver are created and active.
  • The data file includes a description for each data point. The missing description is displayed with the symbol ~.
  • (Optional) Create Hierarchy-User.txt and Hierarchy-Logical.txt configuration files for the Logical View and User View.
  1. Select Project > Field Networks > [Field Network].
  1. In the Import tab, click Browse and select the EDE file.
  1. Click Open and select the EDE file.
  1. In the File type drop-down list, select EDE text file (*.csv) file type or EDE Excel (*.XLSX).
    Note: If the Hierarchy-User.txt and Hierarchy-Logical.txt files are used for mapping the views, they must be located in the same location as the import files.
  1. Select the import file:
    NOTE 1: The Hierarchy-User.txt (optional) and Hierarchy-Logical.txt (required) files cannot be selected.
    NOTE 2: If an error is found while analyzing the file, a message box displays that must be confirmed by clicking OK. Click Open Log for additional Information.
  1. Click Open.
  • The pre-processor creates the files Hierarchy-Logical-Map.csv and Hierarchy-User-Map.csv.
  • No texts are available in column B for the description.

Supplement Texts for Hierarchy Folder

The various objects in System Browser receive different names by supplementing file Hierarchy-Logical-Map.csv and Hierarchy-User-Map.csv.

Files Hierarchy-Logical-Map.csv and Hierarchy-User-Map.csv

Without translation

With translation

 

  1. Open the files Hierarchy-Logical-Map.csv and Hierarchy-User-Map.csv.
  1. Supplement the descriptions in column B. Use the special character #separators-3#| (Hierarchy-logical.txt) as separate the language entries.
    Note: The sequence of the languages must match the one defined on the System Management Console.

  1. Create a backup copy of Hierarchy-Logical-Map.csv and Hierarchy-User-Map.csv.
  1. Copy Hierarchy-Logical-Map.csv and Hierarchy-User-Map.csv back to the original location.

Conduct Second or Additional EDE Data Imports

  • Files Hierarchy-Logical-Map.csv and Hierarchy-User-Map.csv are translated.
  1. Select Project > Field Networks > [Field Network].
  1. In the Import tab, click Browse and select the EDE file.
  1. Click Open and select the EDE file.
  • Note: Missing entries are supplemented in the existing files if new hierarchy objects are found during an additional import. Supplement the texts and repeat the import.
  1. In the Source Items list, click to select all files.
    Note: If Delete unselected objects from views is activated, all automation stations and linked objects that are not located in the selected import file are deleted. The main objects must be deleted manually in Logical View and Physical View as well as User View.
  1. Click Import.
  • A message is displayed at the end of the import process that summarizes the results in a detailed log.

Assigning/Changing a Function

  1. Select Project > Field Networks > [Network] > Hardware > [Device name] > [Data point].
  1. Click the Object Configurator tab.
  1. Open the Main expander.
  1. In the Function drop-down list, select the corresponding function.
  1. Click Save .
  1. Repeat Steps 1 to 5 for each additional data point.