Importing detector data ensures the conformity between Siveillance Control and the Subsystems. The configuration data is taken either from the subsystems and their configuration tools or from OIS. In order to fully configure the subsystem in Siveillance Control and be able to process data coming from the subsystem, you have to import the subsystem data points file.
Importing Subsystem Data Points
- The Engineering perspective is displayed.
- The data points file is available. For more information refer to: Transferring the Data Points File in Subsystems Integration with OIS.
- Click Import Data.
- In the Data channel field, select OIS Datapoint List.
- Click Next.
- Select the required data points file.
- In the Source ID input field, enter a meaningful ID. It is recommended to use a short source ID.
- If you import data from multiple control panels, make sure that all files have the same source ID. Otherwise, the configuration cannot be completed.
- In the MOX Detail Change dialog box, select the advanced settings and click Next. For more information refer to: Advanced Import Settings.
- Click Next.
- In case of import errors, note the address to later check if the error can be ignored or needs to be fixed.
- If you configured investigation times (t1, t2) in the subsystem, they will be displayed as unknown attributes in the Data Import dialog box when importing data into Siveillance Control. This information on investigation times when an alarm is triggered is not supported in Siveillance Control.
- Click Next.
- In the Importer Settings dialog box, keep the default settings and click Next. For more information refer to: Import Settings.
- Click Finish.
- If necessary, repeat the import for all data points files.
Element types that are transmitted from the Subsystem may not yet be known in Siveillance Control.
The elements in question are assigned in this case – where possible – to a higher-level type such as a fire alarm. While the messages and alarms are displayed, the measures may not be generated correctly