- Field Data Import

Use this method for all field subsystems that do not support auto discovery. It is also recommended for offline commissioning: that is, projects where all of the work—creating graphics, setting up the networks, and so on—is done prior to arriving at the job site.

It involves the following steps:

• Export the field panel databases from the commissioning tool (for example, using the SiB-X Export Tool).
• Import the databases using the Desigo CC import tool.

Use this method for field subsystems that support auto discovery where the field panels are already installed and online (online commissioning).

• Use the Desigo CC Discovery application to set filters and detect your devices on the network, which then display in System Browser.

Desigo CC supports the following formats for the import:

• XML (SiB-X files)
• CSV
• SIBX
• EXP
• XLSX
• S1X
• ZIP
• CFG

Selection of File to Import

• When browsing and selecting a file to import, its format is validated. If the file is correct, the item list displays in the Source Items list; otherwise, a message asks you to select another file.
• If you change your selection in System Browser after selecting a file to import, a message warns you that this will clear the current Source Items list.
• Click Yes to proceed. The Source Items list will be lost.
• Click No to cancel. The system ignores the last selection you made in System Browser, and the existing Source Items list is retained.

Selection of Items to Import

Once you select the configuration file you can:

• View the devices available in the selected configuration file (Source Items).
• Search for specific devices to import.
• Have preview of the devices that will be imported when you click the Import button.
• Transfer the devices from the Source Items list to the Items to Import list in one of the following ways:
• One-by-one: Double-click (or select) an item and click .
• Multiple transfer: select the items and click .
• Similarly, you can use or to move items back from the Items to Import list to the Source Items list.
• When you choose the items to import you can filter the Source Items list by typing some text in the Search field. Delete the text to clear the filter.

Delete unselected items from the views

Before importing the configuration data you can select this option that lets you specify whether, during the import, any devices that are not present in the file to import must be removed from the views. You can use this option, for example, when there are some pre-existing devices in the system for that view, but you do not want to retain them.

Hierarchies Mapping

• By default, after you extract data from one or several files, the Hierarchies Mapping expander displays the hierarchies for the selected files and any indications—based on the import rules—about the System Browser view root to link for each hierarchy.
• The hierarchies mapping is saved only when the import starts. If you modify the mapping without starting the import, any change is lost.
• Once the import is complete you cannot change this mapping unless you delete the root of the physical view, logical view, or user-defined view in System Browser. This results in clearing the view in the hierarchies mapping that can be edited again.

To speed configuration, make sure the Desigo CC Transaction Mode is set to Simple or the Automatic Switch of Transaction Mode is set to True.
The automatic switch setting is recommended. Without it, to re-enable the logs, you need to set the Transaction Mode to Logging at the end of the configuration procedure.

• Before starting the import of subsystem data: verify that the import rules are available for the library of the concerned product family; create any views required in the project; specify the hierarchies mapping for the selected configuration file (remember to map the hierarchies before proceeding with the import, especially when selecting a SiB-X file, for example, for a BACnet network.) For details refer to the specific subsystem.
• When executing a SiB-X import under a network (for example, a BACnet network), you can also select multiple files. The import operation results in all the devices for the selected files being imported.
• When selecting multiple files, if they contain devices having the same ID, a message informs you that only the device contained in the last file will be imported.

• When you click the Import button, you may get a warning or error if the number of source items selected for import will cause the system to approach or exceed the system limits (maximum permitted number of objects). For details, see Hardware and Peripherals.

• During the import, when uploading a SiB-X formatted configuration file, if a new object is detected it is automatically imported under the corresponding family or device.
• During the import, the Import tab refreshes to display the Import in progress page where you can check the import state.
• When importing a SiB-X file, as the operation proceeds, the imported hierarchies and the corresponding devices appear under the assigned views.
• If you change your selection in System Browser while an import is in progress, a message box warns you about the ongoing operation and asks you what to do.

During the import of a SiB-X file, any Description texts in the different languages are also imported.
The import is carried out whether the different languages in the SiB-X file match with the languages available with the Desigo CC installation.
When the import is completed, description texts will display to the users according to the users’ culture setting. Note that the Desigo CC default language (English US) will be used for any texts in a language not present in the SiB-X file.

• The re-import either partially or completely re-imports existing data in order to update it (matching the configuration file data). This may imply adding, modifying, or deleting data stored in the database.
• During a re-import, the validation level is checked for the device objects (such as, field panels or control units): the re-import of device data is always carried out based on the higher validation profile of the device objects (the user is prompted with the Validation Required dialog box). For background information, see the reference section.
• During the re-import, if an object has the Override Protection check box selected in the Main expander of the Object Configurator, this option will prevent the override of any modifications manually made by the user (see Setting Override Protection for Objects). In particular, depending on the different Import applications, one or several of the following attributes for the specific object will be protected against the override:
• Description
• Function
• Alias
• Discipline
• Sub-Discipline
• Type
• Sub-Type
• The Override Protection check box does not affect the deletion of the nodes. Furthermore, the Desigo CC import applications do not provide information to the user about protected objects.

The Maximum backup size of imported files property of the Main Server sets the amount of space allocated to store backup copies of field import files. The limit applies separately for each field network.

On project creation or restore, it is by default set to 0, which means that backup creation is disabled altogether. You can set this to a nonzero value to allow space for backups.
For example, if the Maximum backup size... limit is set to 5 MB, this means that, for any given network, at most 5 MB of import file backups will be kept.
For instructions, see Handling Backup Size of Imported Files.

If the Maximum backup size... limit is set, backups are handled as described below:

• When a field data import is carried out, a ZIP file is created under [Project]\Imported_Config_Files\[field network], containing backup copies of the files imported for that field network.
  In case of a re-import for the same network, a new ZIP file will be created in the same folder. The name of each ZIP backup indicates the date and time of the import (yyyy-mm-dd_hh-mm-ss.zip).
• If multiple stored ZIP backups cause a [field network] folder to exceed the Maximum backup size... limit, the oldest backup copies will be removed to free up space.
  However, at least one ZIP backup is always kept.

NOTE: If a field network is deleted, the relevant backup copies of the imported files are not deleted automatically.
Backup copies of imported files can only be deleted manually.