Subsystems and Integrations - Operation Manual - P54592-P101-A1 - P54592-P118-A1

You can either start an OIS connection or a component. If you start a component first, the OIS connection is started automatically, too.

In order to receive messages, the OIS connection must be up and running. The connection to the subsystem can remain for as long as at least one client is logged in to receive messages. Otherwise, the connection is stopped. The connection can also be stopped due to disturbances. For more information refer to: Loss of Connection.

• The Single, +3 or +5 perspective is displayed.

• The System Tree is displayed.

1. To switch on a component, right-click it and select Switch on. You can switch on several components using multi-selection.

2. To switch on a group of components, right-click the subsystem container and select Switch on all.

• The synchronization with OIS starts.

• When the synchronization is finished, the OIS component appears with a green symbol.

If no more workstations are actively logged on the Siveillance Control server, OIS disconnects. In case of an unexpected loss of the last connection between the Siveillance Control server and the workstation, the OIS is disconnected, too. From the operator’s point of view, the connection to the system is stopped. OIS has no further management system to send alarm messages and thus transfers responsibility to the subsystem and its control panels, stops the Cu-Handler and exits. The following scenarios are possible:

Only one client is logged in

• If the only logged in workstation is logged out, the connection to OIS can be maintained for a configured time. The OIS connection remains activated in the intervening time. For more information refer to: Exiting the Software.
• The only logged in client is ended automatically in the event of an error. The OIS connection is stopped automatically after one minute.
• The only logged in client loses the network connection. The OIS connection is stopped automatically after one minute.

At least two clients are logged in

• A client is exited from an operator and another client remains active. The OIS connection remains activated. The connection to the OIS is maintained.
• A client is exited automatically in the case of an error and another client remains active. The OIS connection remains activated. The connection to the OIS is maintained.
• In the case of two logged in clients, it is theoretically possible that an error arises in the first client but is not detected initially. If the second client is exited from an operator in the intervening time (maximum one minute), it is assumed at this time that there is an additional active client. The OIS connection remains activated. If the error with the first client is then identified, this client is exited automatically. Because no other client is logged in, the OIS connection is stopped automatically after one minute.

When the connection between the runtime server and OIS is stopped, you receive an error message. For more information refer to: Failure of OIS Connection.

• A service technician has resolved the fault.

• Right-click the corresponding integration and select Switch on.

• As soon as the integration with OIS is started, Siveillance Control automatically commences the restart.

When the connection between OIS and the subsystem is stopped, you receive an error message. For more information refer to: Cu-Handler Errors.

The restart (OIS update) commences after Siveillance Control has established integration with OIS again. The restart phase ensures that the objects in Siveillance Control are synchronized with those of the subsystem. The current detector states are received from the previously disrupted integration with OIS or the subsystem. In the process, Siveillance Control receives all detectors from OIS that are not currently in a quiet state. This information is used to purge the message list and the status lists. Messages that were in an active state before the fault and are in a quiet state following a fault are flagged as quiet messages in the Message List view.

If OIS is not configured properly or the configuration is incomplete, an Invalid OIS message is issued. Double-clicking this message opens the Rate Message window. A message of this type is generated in the following cases:

• If the data point of the detector cannot be found in the database, an Unknown data point message is generated.
• If an attribute is transmitted that is not intended for the data point, Invalid message is output.
• If an attribute cannot be set at present (in other words it is not a status attribute), Invalid message is output.
• If the attribute value being set is not valid, Invalid message is output.
• If the number format of a numeric attribute is invalid, Invalid message is output.
• If a mandatory attribute is not transmitted, Invalid message is output.

This message is usually created in addition to the actual message since Siveillance Control tries to display as much of the incomplete data package as possible. Several Invalid OIS messages can also be created for an incomplete data package. These are then created as submessages to the standard message and are thus also visible in the message list.

When OIS receives messages that cannot be interpreted uniquely, a special data package is sent to Siveillance Control.

The following causes are possible for messages that are not unique:

• The data point (detector or address) cannot be assigned in OIS.
• The data point incident (detector) is not known.
• The specified attribute is not known.

OIS transmits a special message to Siveillance Control in such cases. Unknown data points have to be supplied subsequently in order to be able to assign future incidents from this source.

The Cu-Handler is the integration software for OIS and handles the communication with the subsystems. At the same time, the Cu-Handler monitors the connection between the subsystem and OIS.

In case of a connection failure, you receive a fault message for the relevant subsystem. The following causes are possible for a faulty connection:

• The connection between the Cu-Handler and the subsystem fails, for example there is a broken cable connection.
• There is an error in the Cu-Handler, for example a software process that is no longer functioning.

For technical reasons, you only receive a unique fault message as a system message, if a Cu-Handler is configured correctly in each case for the integrated subsystem(s) in Siveillance Control.

Fault Message for Correctly Configured Cu-Handler

You receive a fault message as a system message. The name of the Cu-Handler is displayed in the subsystem text. If a specific device is specified for the Cu-Handler, this is displayed additionally in the subsystem text.

Fault Message for Incorrectly Configured Cu-Handler

You receive a fault message of the type Unit failure. The fault message contains a submessage Unknown data point. This error indicates a problem in the configuration and must be resolved by the administrator or commissioning engineer. The number of fault messages or submessages corresponds to the number of logic addresses of the OIS connection. Once the fault has been resolved, the quiet message is issued for the Cu-Handler.

The connection between OIS and the runtime server is established by means of an internal program interface, the OIS connection. As long as the runtime server is operational, data can be received from the OIS. The connection between OIS and Siveillance Control may fail. When the connection fails, you no longer receive messages from the subsystem in question.

The following causes are possible for a failure of the OIS connection:

• No (LAN) connection between the computers running Siveillance Control server and OIS (for example: LAN connector unplugged, LAN cable defective).
• There is an error in OIS. The OIS software is no longer working. This can happen for example if the PlcController software process is stopped.
• There is a temporary network disconnection or downtime for OIS Server.

Example of an Error Scenario

OIS and the Siveillance Control server are started. The OIS connection is started in the Siveillance Control server. Messages can be received. If you have administrator rights for the runtime system, you can view the object properties of the OIS connection in the Engineering perspective.

If the connection between the Siveillance Control server and OIS is interrupted, you receive a fault message in the Message List view. There can be a short delay before the fault message reaches the Message List view for system-related reasons. You can also view the fault in the Object Properties view. Siveillance Control tries to restore the connection automatically for every 60 seconds, until the OIS connection is established. However, if the automatic re-connection fails for a long time, the operator can manually stop the OIS re-connection and start the connection again, once the problem is resolved in OIS. For more information on starting and stopping OIS connections refer to: Starting OIS Connections and Stopping OIS Connections . As soon as the connection is established between the server and OIS, you receive a quiet message in the Message List view.

The following reasons are possible for VMS disconnection:

• There is a temporary network disconnection in VMS.
• There is a down-time for VMS Server.

If the VMS connection is interrupted, Siveillance Control tries to restore the connection automatically for every 60 seconds, until the VMS connection is established.

However, if the automatic reconnecting fails for a long time, you can manually disconnect the VMS connection and connect again, once the problem is resolved in VMS. Keep in mind that you have to wait at least for the minimal waiting time of 60 seconds before reconnecting to VMS, after disconnected manually.