OIS functions both as a translator and data evaluator between the subsystem and Siveillance Control. For this purpose, the following unit types are always available:
- Cu-Handler unit: This unit ensures communication between OIS and the subsystem. By default, this unit is generally named like the subsystem.
- Programmable Logic Controller unit (PLC): This unit contains the OIS logic and ensures communication between the Vu-Handler and Cu-Handler units. Furthermore, the PLC unit controls and checks incoming data and makes decisions.
- Vu-Handler unit: This unit ensures communication between OIS and Siveillance Control. There can be more than one Vu-Handler unit (for example engineering and runtime).
Each time information comes from either the subsystem or Siveillance Control, the PLC unit communicates with an internal database through a dispatcher to check whether the processed data points already exist. If the PLC unit decides that all data points are existing, communication proceeds. Both the Cu-Handler and Vu-Handler process the data such that it becomes understandable for either the subsystem or Siveillance Control. If multiple Siveillance Control servers are used, the data is processed through a switch first.
The following installation and configuration steps are necessary:
Subsystem Tasks | OIS Tools Tasks | Siveillance Control Tasks |
|---|---|---|
Configuring the subsystem onsite. This is not part of this documentation. | On the OIS server, you first have to install and set up Debian and OIS. For more information refer to: Debian Installation and OIS Installation. | In Siveillance Control, you first have to transfer the data points file. For more information refer to: Transferring the Data Points File. |
You have to prepare the subsystem for the connection to OIS, for example create data points files. Keep in mind that some tasks only can be completed after OIS Tools is set up in browser. For more information refer to: Subsystem Configuration. | After the installation you can start the configuration of the subsystem including sites, gateways, units and, if necessary, devices. For more information refer to: Subsystem Configuration with OIS Tools. | You then have to create and configure an OIS connection. For more information refer to: Creating and Editing the OIS Connection. |
| For some systems, you have to import data points. For more information refer to: Importing the Certificate and Subsystem Configuration File. | Afterwards, you can import the data points and configure the OIS connection. For more information refer to: Connections to Subsystems in Configuration. |
| When the gateway configuration is completed, you have to upload it. For more information refer to: Uploading the Gateway Configuration. |
|
| For a secure and encrypted connection to Siveillance Control, you have to export the root certificate. For more information refer to: Creating and Importing the OIS Root Certificate. |
|
| Additionally, you have to export data points to make them available for Siveillance Control. For more information refer to: Transferring the Data Points File. |
|