Commands to Subsystems - Operation Manual - P54592-P101-A1 - P54592-P118-A1

Depending on the subsystem and detector type, the following commands are possible:

Note that the commands specified in the table as well as their meaning can be adapted, if necessary, by a commissioning engineer in OIS in line with specific customer requirements or specifications.

You receive an overview of the commands from the administrator in this case.

Fire, Intrusion, TBS, Access Control

Fire, Intrusion, TBS

Fire

TBS

Access Control

You can only send commands when Siveillance Control has assumed responsibility for this subsystem. How responsibilities are taken over depends on the configuration of the subsystem. The following options are possible:

Automatic Takeover of Responsibilities

If a subsystem detects that an integration exists with a management system, the responsibility is immediately dispensed automatically to this management system without further steps. If an OIS connection is therefore started in Siveillance Control, Siveillance Control takes over responsibility for this subsystem following startup. The operator can immediately send commands. The following actions indicate that the responsibility is taken over:

• The OIS connection is started, if you receive messages from a subsystem.
• Siveillance Control has responsibility for the subsystem, if you can send commands successfully.

Taking Over Responsibility Using Commands

• Either the Single, +3 or +5 perspective is displayed.

• An operating panel with the external ID Operating Panel is created in the system tree for the subsystem.

1. Open the System Tree.

2. Right-click an operating panel and select Perform Command > Take over responsibility without dialog.

• Siveillance Control takes over the responsibility for the subsystem.

You can select several objects and send a command by using multi-selection, for example for detectors, detector groups or intrusion zones. In order to send the command, the objects need to have the same data point type and to be listed under the same component.

• Either the Single, +3 or +5 perspective is displayed.

• The integration with the subsystem has been started.

• Siveillance Control has assumed responsibility for the relevant subsystem.

1. You have the following options to send commands:

• In the Location Tree, right-click one or more objects and select Perform Command > [Command].

• In the System Tree, right-click one or more objects and select Perform Command > [Command].

• In the System State List view, right-click one or more detectors or detector groups and select Perform Command > [Command].

• In the graphic, right-click one or more objects and select Perform Command > [Command].

2. To display subsystem specific commands, select Perform Command > More Commands > [Command].

• If you select more than one object, but you do not have the permission to send commands for a specific object type, the command is sent only for the object for which you have permission. For more information refer to: Creating Simple Permission Rules in Configuration.

• If you do not have the permission to send subsystem-specific commands, ask your administrator. For more information refer to: Creating OIS Commands Permission Rules in Configuration.

• The command is sent to the subsystem and processed if possible.

• Acknowledgments of the command processing appear in the info line.

You can send commands to sum detectors without having to navigate to each single detector.

• Either the Single, +3 or +5 perspective is displayed.

• A sum detector is added to the Location tree and to the graphic.

1. Either in the graphic or Location tree, right-click a sum detector and select Perform Command.

• In the Objects list, the objects belonging to the selected sum detector and their states are displayed.

2. To find objects in the Objects list, you have the following options:

• In the Filter field, enter a name. You can filter by an object name, for example.

• In the Discipline drop-down list, enter a discipline. To display all objects, deselect the discipline.

• In the Filter by State field, enter a name of the detector's state you want to filter for.

3. Select one or multiple objects in the Objects list. To select all objects in the Objects list, click an object and press Ctrl + A.

• The Commands list displays the standard commands set available for the selected object(s). To only display the subsystem specific commands, mark the More Commands check box. Keep in mind that the More Commands check box is the only possibility to trigger commands to a subsystem if a sum detector with the External ID (Wildcard possible) parameter manages unknown data points which have active messages from OIS. Since such data points have not been imported into Siveillance Control, their types are unknown and therefore the standard commands set cannot be evaluated and displayed.

4. To send commands, you have the following options:

• Select a command and click Perform Command.

• Select a command and double-click it.

• The dialog box remains open so that multiple commands can be sent at the same time.

• In the State column or in the graphic, the detector's state is changed.

5. To finish, click Cancel.

You can return the responsibility again.

• Either the Single, +3 or +5 perspective is displayed.

1. Open the System Tree.

2. Right-click an operating panel and select Perform Command > Dispense responsibility without dialog.

• The responsibility for the subsystem is returned.

If you issue a command where the two-man rule is configured, perform the following steps.

1. Click the command you want to send.

2. Ask another user to confirm your issuing of the command.

3. Select the user who is to confirm the command from the drop-down list.

4. Have the user enter their password in the Operator 2 Pin field.

5. Click OK.

If you want to send a command where the mandatory comment annotation is configured, perform the following steps.

1. Click the command that you want to send.

• The Order Confirmation dialog box appears.

2. Enter a reason or comment for sending the command. Make sure that the length of the comment equals or exceeds the comment length displayed in the Order Confirmation dialog.

3. Click Ok.

If you want to send a command where both the Two-man rule and mandatory comment annotation are configured, perform the following steps.

1. Click the command that you want to send.

• The Order Confirmation dialog box appears.

2. Ask another user to confirm your issuing of the command.

3. Select the user who has to confirm the command from the drop-down list.

4. Have the user enter their password in the Operator 2 Pin field.

5. Enter a reason or comment for sending the command. Make sure that the length of the comment equals or exceeds the comment length displayed in the Order Confirmation dialog.

6. Click Ok.

Type and source of hazard

If you want to swend the same command for two detectors simultaneously, with the two-man rule configured for the command of the first detector and the mandatory comment annotation configured for the same command of the second detector, repeat the steps above. In this case, it is expected to enter Operator 2 Pin only for the first detector and the Comment with the mentioned length only for the second detector.

You can directly send commands to subsystems by using a command button. With only one click it is possible for example to arm or disarm zones for maintenance purposes. Command buttons must first be created in the engineering mode and then activated in runtime mode.

States of Command Buttons

The current state of each command button is displayed by the button's symbol in the graphic. A dot placed in the lower right corner of the symbol displays the current state of the command button. A detailed information about the state of all OPSs is displayed in the dialog window which you can open by right-clicking the command button and selecting Edit Command Properties.

The following states are possible:

• Idle State

The Idle state is the initial state of a command button. The dot placed in the lower right corner of the symbol is displayed in green. You can send a command by left-clicking the command button.

• Processing State

The Performing state is a state for which a command button has been clicked and the configured OPS is still being processed. The dot placed in the lower right corner of the symbol is displayed in yellow. Once the command is processed successfully, the state of the command button changes to the Idle state. A detailed information about the state of all OPSs is displayed in the dialog window. It provides an overview of all OPSs of the command button and their current states during the processing.

• Failure State

The Failure state is an state for which one or several OPSs for a command button cannot to be processed. The dot placed in the lower right corner of the symbol is displayed in red. A detailed information about the state of all OPSs is displayed in the dialog window. It provides an overview of all OPSs of the command button and their current states during the processing. It displays that OPS could not be processed successfully and it is failed. You can perform the OPS again by right-clicking it and using the context menu or double-clicking it. Once all OPSs are processed successfully, the state of the command button changes to the Idle state.

Also, overriding of the failed state is possible by right-clicking the OPS and using the context menu. If overriding of all failed OPSs represents a lot of effort, you can reset the command button. This will reset the state of the command button and thus reaches the Idle state.

Display of Command Buttons

If a command button is not configured to be a button with toggle functionality, the default symbol of the visualization variant along with the state is displayed in the graphic. There states are possible:

• Idle
• Processing
• Idle/Failure

Display of Command Buttons with Toggle Functionality

If a command button is configured to be a button with toggle functionality, the visualization variant display reflects its state. The following states of the command buttons with the toggle functionality are possible:

• Off Visualization Variant and Idle State

This is the initial state of a command button. The dot placed in the lower right corner of the symbol is displayed in green. It indicates the Idle state.

• Off Visualization Variant and Processing State

The symbol is displayed when the OPS for the On subkeyword is being processed. The dot placed in the lower right corner of the symbol is displayed in yellow. It indicates the Performing state.

• On Visualization Variant and Idle State

The symbol is displayed when the OPS for the On subkeyword is processed successfully. The dot placed in the lower right corner of the symbol is displayed in green. It indicates the Idle state.

• On Visualization Variant and Performing State

The symbol is displayed when the OPS for the Off subkeyword is being processed. The dot placed in the lower right corner of the symbol is displayed in yellow. It indicates the Performing state.

• Off or On Visualization Variants and Failure State

The Failure state is an state for which one or several OPSs for a command button cannot to be processed. The dot placed in the lower right corner of the symbol is displayed in red. A detailed information about the state of all OPSs is displayed in the dialog window. It provides an overview of all OPSs of the command button and their current states during processing. It displays that OPS could not be processed successfully and it is failed. You can perform the OPS again by right-clicking it and using the context menu or double-clicking it. Once all OPSs are processed successfully, the state of the command button changes to the Idle state.

Also, overriding of the failed state is possible by right-clicking the OPS and using the context menu. If overriding of all failed OPSs represents a lot of effort, you can reset the command button. This will reset the state of the command button and thus reaches the Idle state.