Planning

• To get a clear overview of the status of the customer’s installed objects, it is recommended to only install the required extension modules and store objects.
• Before creating the IBaseConfigurationScript.json file for an extension, make sure that you have all relevant information on networks, devices, and drivers that you want to include in the configuration. You can also configure the properties.
• You must specify the configuration options for a library, for example, devices and their properties and libraries in the IBaseConfigurationScript.json file, that you want to have included in the IBase report before executing the IBase script.
• When modifying the configuration file for an extension, consider:
• The OM or the property name can contain the wildcard asterisk (*). For example, GMS_BACNET_NETWORK* indicate that all the OMs starting with GMS_BACNET_NETWORK are reported.
• You can also use the wildcard asterisk (*) in the Designation name field, for example, ManagementView.*. However, we recommend to provide the complete Designation name, if known, for example,
  System1.ManagementView:ManagementView.FieldNetworks.BACnetNetwork_1.Hardware.BACnetDevice.
• To display the parent child relationship thus indicating which objects can be assigned as children (subordinate) objects for the OMs, make sure that the parent OMs for the configured OMs are also specified. The data is reported under the parent OM. However, if no parent OM is found, the data is represented as a separate instance of OM as shown below:
  <Parent ObjectModel="GMS_BACNET_NETWORK_1" />
• Invalid configuration in this file, for example, not matching well-defined type, leads to error and the value will not be reported.