To guarantee a working and consistent configuration, you can perform several data checks, for example simulating messages or validation. If everything works properly, you can activate the data on the runtime client.
Simulating Messages
You can simulate messages to check the configuration. Simulation also demonstrates the function of a message list. Messages can be simulated without an active connection to OIS or VMS.
Starting Message Simulations
Events do not differentiate between simulated and real messages. When an event is created for a simulated message, the simulated message is treated like a real message. Automatic operation procedure steps are also performed immediately for simulated messages.
- You have administrator rights.
- You have the following options to simulate a message:
- In the Location Tree of the Engineering perspective, right-click a detector for which you want to simulate a message.
- In the Location Tree of the Single, +3 or +5 perspective of the runtime client, right-click a detector for which you want to simulate a message.
- In the Graphic view, right-click a detector for which you want to simulate a message.
- To simulate messages for more detectors of the same type simultaneously, select several detectors and right-click the detectors.
- Select Simulation > Simulate Message.
- In the State Attribute field, select the message type.
- In the State Attribute Value field, select a status for the simulated message.
- Click Finish.
- The message is simulated and appears in the Message List view with the message text Simulated Message.
Ending Message Simulations
- You have the following options to end message simulation:
- In the Location Tree of the Engineering perspective, right-click the detector for which you want to end the simulation.
- In the Location Tree of the Single, +3 or +5 perspective of the runtime client, right-click the detector for which you want to end the simulation.
- In the Graphic view, right-click the detector for which you want to end the simulation
- Select Simulation > Simulate Message.
- Select the previously selected state attribute again.
- Select the corresponding status in the drop-down list.
- Click Finish.
Validating Data
Before an activation, possible data inconsistencies have to be identified and resolved. However, the validation process only checks whether configured data is inherently correct. The consistency of detectors in the graphic with actual local conditions cannot be checked. Thus, the commissioning engineer is the only person to ultimately release the configuration.
- The Engineering perspective is displayed.
- Click the following symbol:
- Wait until the displayed dialog box closes.
- If configuration problems such as tasks, errors or inconsistencies exist, then they appear in the Tasks view.
Activating Data
For both the engineering and runtime mode, the data is saved on different servers. Thus, changes made on the engineering server are not automatically available on the runtime server and need to be activated first. The reason for this is to avoid problems during the operator’s daily work.
- A new or modified configuration has been prepared in the engineering mode.
- The upload of the configuration has been done in the quietest operating phase possible.
- No configuration problems have been identified in the engineering mode during the data validation.
- The modified action is not being processed in any event in the runtime mode. Otherwise, the relevant events being processed can no longer be concluded and have to be ended manually at management level.
- The final release of a configuration is carried out by an administrator in consultation with a commissioning engineer.
- Administrator rights are available. For more information refer to: Creating and Importing Users and User Groups.
- Engineering and runtime clients have been set to the same time. This prevents problems with the delta activation.
- Start Siveillance Control in runtime mode.
The connection to the subsystem can get lost in Siveillance Control. Consider the possibility that alarms from the subsystems are not processed during the activation time.
- Click Activation.
- Enter the engineering system hostname and click Next.
- Enter your authorization data.
- You now have two options:
- To only transfer data modified since the last activation, mark the Delta Activation check box. This option is only available after the first activation. The Delta Activation normally has the same effect as a full activation but is significantly faster. In case of problems after delta activation, you can repeat the activation by unmarking the Delta Activation check box and performing the full activation.
- To perform a full activation and transfer all data from the engineering system, unmark the Delta Activation check box.
- If you perform the first data activation or an activation after changing the hostname or username, you can configure the Remember Settings check box. You have the following options:
- If the Remember Settings check box is marked, for the next data activation hostname and username are entered automatically in the respective fields. You only need to enter the password. These settings remain in the system even if you log off or restart the server.
- If the Remember Settings check box is unmarked, type in hostname and username with every data activation.
- Click Next.
- A data validation operation is carried out on the engineering server. If tasks or inconsistencies are identified, the activation operation is aborted.
- Click Finish.
- After restarting the runtime server, the configuration is transferred.
- If you disconnected the OIS, connect it again.