The operation procedure steps contained in a workflow are central for processing events and messages. They contain organizational and event-related or message-related notices for the operator and are either automatically or manually processed step-by-step, depending on the configuration.

Creating Operation Procedure Steps

The objects for which an OPS annotation is defined can be located in the Location Tree or in the System Tree. Annotations can be copied between trees. If one object is located in both trees all annotations from both trees are considered and also annotations will be inherited in both trees.

  • The OPS/Workflow Configuration perspective is displayed.
  1. In the Location Tree or in the System Tree, right-click a node and select Create Annotation > Create Operation Procedure Step.
  1. In the Comment tab, enter a comment if necessary.
  1. In the General tab, define the order of the operation procedure steps. The lower the number, the earlier the operation procedure step is processed. If you enter the same value for multiple operation procedure steps, they are performed in parallel.
  1. In the Workflow/Escalation tab, define the options for which the operations procedure step is to be assigned to an event. You have the following options:
  • For Context: Select the context for which the workflow handling is to be triggered. To only trigger the workflow handling for new started events, select Event or keep the default value. To trigger the workflow handling for both, events and incoming messages, select Event and Message. To only trigger the workflow handling for incoming messages, select Message.
  • For Workflow: The operation procedure step is only started for the selected workflow.
  • For SOP: A workflow can consist of multiple operation procedure step lists. When an operation procedure step is processed, the lists are performed in the defined workflow sequence in parallel or successively with the operation procedure steps configured for them. Thus, the list is used to determine the point in time when an operation procedure step is ultimately to be performed.
  • For Keyword: The operation procedure step to be performed is only started for the values specified here. No entry means the action is valid for all possible values.
  • For Subkeyword: The operation procedure step to be performed is only started for the values specified here. No entry means the action is valid for all possible values.
  • For Escalation Level: The operation procedure step to be performed is only started for the values specified here. No entry means the action is valid for all possible values.
  1. In the OPS to be performed tab, define the operation procedure step. You have the following options:
  • Label: Enter a concise description for the operation procedure step, since this information will be displayed first for the operator. You can also add dynamic text by clicking .
  • Mandatory Performings: You can decide whether or not an operation procedure step is mandatory. Enter 0 for an optional operation procedure step and 1 for a mandatory operation procedure step. Keep in mind that mandatory operation procedure steps are performed first during processing. Thus, any mandatory operation procedure step should be placed before an optional one.
  • Additional Performings: Here you can choose whether or not mandatory operation procedure steps can be repeated. Enter -1 for the mandatory operation procedure step to be processed at least once and then repeated as required and enter 0 for the operation procedure step to be performed once.
  1. In the Affected Objects tab, you have the following options:
  • On Objects of Type: The command is only performed for object of the object type selected. If no object type is selected, all objects are included.
  • For Objects of Subtype: Click and select a subtype from the Select Subtype dialog and click Finish.
  • Attribute: The command is only performed, if the attribute matches the attribute for the object in use. If no attribute is selected, all attributes are included.
  • In state: The command is performed on the objects in use in the selected status. If no state is selected, all states are included.
  1. In the Options tab, you have the following options:
  • Manual Performing Required: Define whether or not the operator has to confirm an operation procedure step. Yes: The operation procedure step has to be confirmed manually. No: The operation procedure step is confirmed automatically. Keep in mind that every automatic operation procedure step is only performed after processing and confirming mandatory manual operation procedure steps that appear first in sequence. Optional manual operation procedure steps do not block subsequent automatic operation procedure steps.
  • Time Intervals: Specify time intervals to add to the operation procedure step and during which the operation procedure step should be valid. Click Add, select time intervals which you have created and click Finish. You can add more than one time interval to the OPS. To remove time intervals from the operation procedure step, select them and click Remove. For more information on how to create time intervals, refer to: Creating Time Intervals.
  • Visible in UI: The check box is marked per default. If you unmark the check box, the operation procedure step is not displayed in the SOP and the operator cannot see the operation procedure step. You can only unmark the check box, if the operation procedure step is performed automatically.
  • Visible in Printout: The check box is marked per default. If you unmark the check box, the operation procedure step is not added in a printout.
NOTICE
The plausibility is not checked by Siveillance Control. The commissioning engineer or data administrator are responsible for determining which types of operation procedure steps are configured as automatic and which as manual.
  1. Click Finish.

Parameters for Mandatory and Optional OPS

  • Manual mandatory OPS, to be performed once:
    • Mandatory Performings: 1
    • Additional Performings: 0
    • Manual Performing Required: Ok
  • Manual mandatory OPS, to be performed at least once, can also be performed several times:
    • Mandatory Performings: 1
    • Additional Performings: -1
    • Manual Performing Required: Ok
  • Manual optional OPS, can be performed several times:
    • Mandatory Performings: 0
    • Additional Performings: -1
    • Manual Performing Required: Ok
  • Automatic OPS, performed once:
    • Mandatory Performings: 1
    • Additional Performings: 0
    • Manual Performing Required: None

Editing Operation Procedure Steps

NOTICE
Processed events can probably no longer be concluded and have to be ended at management level.

Before activating the change, make sure that the modified operation procedure step is not being processed in any event.

  • The OPS/Workflow Configuration perspective is displayed.
  1. In the Operation Procedure Steps view, click the annotation you want to edit. You have the following options:
  • Right-click the annotation and select Edit OPS Annotation.
  • Double-click the annotation.
  1. Enter your changes.
  1. Click Finish.

Copying and Pasting Operation Procedure Steps

  • The OPS/Workflow Configuration perspective is displayed.
  1. In the Operation Procedure Steps view, click the existing OPS annotation you want to copy.
  1. Select either one or more than one OPS annotation from the Operation Procedure Steps view.
  1. Right-click the OPS annotation and select Copy OPS annotation.
  1. In the Location Tree, select one or more areas/data points.
  1. Right-click and select Paste OPS annotation.
  • A copy of the OPS annotation for all selected areas or data points is created.
  1. Edit the newly created OPS annotations, if required.
  1. Click Finish.

Adding or Overwriting Time Intervals

In case there are several OPSs with time intervals configured, you can overwrite their time intervals or add more time intervals to those that already exist.

  • The OPS/Workflow Configuration perspective is displayed.
  • Operating procedure steps are created.
  1. In the Operation Procedure Steps view, right-click one or several OPSs and select Set Time Intervals.
  1. To add time intervals to those that already exist, you have the following options:
  • Click Add, select time intervals which you have created and click Finish.
  • Mark the Add to existing check box.
  1. To overwrite time intervals, click Add, select time intervals which you have created and click Finish.
  • Previously configured time intervals are removed and replaced by the selected intervals.
  1. To remove time intervals, select them and click Remove.
  1. Click Finish.

Adding or Overwriting Time Intervals Recursively

For areas in the Location Tree with time intervals assigned to OPSs, you can recursively overwrite their time intervals or add more time intervals to those that already exist.

  • The OPS/Workflow Configuration perspective is displayed.
  1. In the Location Tree, right-click an area and select Set Time Intervals in Hierarchy.
  1. Enter the following information:
  • Type: Keep the default setting: OPS Annotation.
  • Direction: This is the direction in which the Location Tree is processed to update OPSs. Bottom to Top: Based on the selected area in the Location Tree, all OPSs found in the superordinate areas will be updated. Top to Bottom: Based on the selected area in the Location Tree, all OPSs found in the subordinate areas will be updated.
  1. To add time intervals to those that already exist, you have the following options:
  • Click Add, select time intervals which you have created and click Finish.
  • Mark the Add to existing check box.
  1. To overwrite time intervals, click Add, select time intervals which you have created and click Finish.
  • Previously configured time intervals are removed and replaced by the selected intervals.
  1. To remove time intervals, select them and click Remove.
  1. Click Finish.

Selecting Operation Procedure Step Types

  • The OPS/Workflow Configuration perspective is displayed.
  • The Create/Edit Operation Procedure Step dialog box is displayed.
  1. Open the OPS to be Performed tab.
  1. Select an OPS Type.
  1. Click Finish.

Sending Emails with Event/Message Information as PDF Attachment

  • The OPS/Workflow Configuration perspective is displayed.
  • The Create/Edit Operation Procedure Step dialog box is displayed.
  1. Open the OPS to be Performed tab.
  1. In the OPS Type field, select Send Email.
  1. Enter the name of the recipient to send an email. Emails can be sent to multiple recipients by separating them by semicolon (;).
  1. In the Subject field, you have the following options:
  • Enter a text.
  • Click and select a variable to construct a dynamic text for the subject.
  1. In the Message field, you have the following options:
  • Enter a text.
  • Click and select a variable to construct a dynamic text for the subject.
    Keep in mind that variables for Event are not filled out in the runtime. Variables for Message are fully supported and filled out based on the incoming message belonging to this OPS. The PDF Attachment for message based OPS will use the alarm printout instead of event printout.
  1. The PDF attachment is enabled by default. Uncheck the With Event/Message as PDF Attachment check box, if you do not want to send PDF document along with the email.
  1. Click Finish.
  • A PDF document with information on the event, such as the event name, device, date and time of the event, and the graphic layout of the area where the event occurred will be added to an email.
  • A PDF document with information on the message, such as the message name, device, date and time of the message, and the graphic layout of the area where the message occurred will be added to an email.

Defining Simple Text Services

You can display an unformatted text as an operation procedure step. This text is displayed in the Rate Message window when processing an operation procedure step.

  • The Create/Edit Operation Procedure Step dialog box is displayed.
  1. Open the OPS to be Performed tab.
  1. In the OPS Type field, select Simple Text Service.
  1. In the Label field, enter a text. The text later appears in the Rate Message window.
  1. To add a dynamic value for primary messages or events, select a variable by clicking .
  • The variable is transferred as a placeholder to the Label field at the cursor position. The value replaces the placeholder when later processing an event.
  1. Click Finish.

Opening Specific Bookmarks

You can use saved bookmarks to start and process as an operation procedure step.

  • The Create/Edit Operation Procedure Step dialog box is displayed.
  1. Open the OPS to be Performed tab.
  1. In the OPS Type field, select Open (specific) bookmark.
  1. Select the required bookmark in the Bookmark to open field.
  1. Open the Options tab.
  1. In the Manual Performing Required field, select Ok.
  1. Click Finish.

Defining URLs

As an operation procedure step, you can define the call up of an HTML website. As default, websites are displayed in the Windows system's browser. For display of websites in a browser view inside the Siveillance Control client a license is required. For more information refer to: License Import.

You can also define an operation procedure step, that opens a web application, such as dashboards based on Siveillance Data Feed, or Operation Scheduler.

  • The license for internal display of websites is available. For more information refer to: License Overview.
  • The Create/Edit Operation Procedure Step dialog box is displayed.
  1. Open the OPS to be Performed tab.
  1. In the Label field, enter a text.
  1. In the OPS Type field, select Open URL.
  1. Enter both the Browser Title and the URL.
  1. To add a dynamic value for primary messages or events for the Label, Browser Title and URL, select a variable by clicking .
  • The variable is transferred as a placeholder at the cursor position. The placeholder is replaced by the requested value when later processing the message or the event.
  1. Mark the In ext. Browser checkbox to open the URL in an external browser window. Leave the check box unmarked, to open the URL in an internal browser view.
  1. Open the Options tab.
  1. In the Manual Performing Required field, select Ok.
  1. Click Finish.

Defining Commands

You can select a command for all detectors in use. All runnable commands are also included in the OPS Type drop-down list.

  • The Create/Edit Operation Procedure Step dialog box is displayed.
  1. Open the OPS to be Performed tab.
  1. In the Label field, enter a text.
  1. In the OPS Type field, select a command.
  1. Open the Affected objects tab, which is only displayed for the OPS Type command.
  1. Enter the settings.
  1. Click Finish.

Defining Commands for Multiple Given Objects

You can add an OPS annotation where a command will be performed for one or more objects.

  • The Create/Edit Operation Procedure Step dialog box is displayed.
  1. Open the OPS to be Performed tab.
  1. In the Label field, enter a text.
  1. In the OPS Type field, select Perform Command (for Given Object).
  1. Add one or more objects to the Object field.
  1. In the Command field, you have the following options:
  • Select a command.
  • Select More OIS Commands and in the OIS Command field select one of the OIS commands provided as More Commands.
  1. Click Finish.

Defining Commands with OIS Order Number

You can perform an OIS order from Siveillance Control using the order number defined in an OPS.

  • The OPS/Workflow Configuration perspective is displayed.
  1. In the Location Tree, right-click an object and select Create Annotation > Create Operation Procedure Step.
  • The Create/Edit Operation Procedure Step dialog box is displayed.
  1. Open the OPS to be Performed tab.
  1. In the Label field, enter a text.
  1. In the OPS Type field, select Perform Command with OIS Number.
  1. Enter the order number of an OIS order in the OIS Number of Command field.
  1. Click Finish.

Defining Time Delays

You can define a time delay meaning that subsequent operation procedure steps can only be processed when the defined time delay has expired and the action has the status performed. A time delay makes sense, for example if you want to disable all detectors in a room due to maintenance work.

  • The Create/Edit Operation Procedure Step dialog box is displayed.
  1. Open the OPS to be Performed tab.
  1. In the Label field, enter a text.
  1. In the OPS Type field, select Time delay.
  1. In the Time delay (in minutes) field, enter the time for which you want to delay the operation procedure step.
  1. Click Finish.

Setting Operation Mode

You can define an OPS that automatically activates operation mode and sets the selected operation mode. With operation modes, message distribution can be changed. For more information, refer to: Message Control.

  • The Create/Edit Operation Procedure Step dialog box is displayed.
  1. Open the OPS to be Performed tab.
  1. In the Label field, enter a text.
  1. In the OPS Type field, select Set Operation Mode.
  1. Click next to the Operation Mode field.
  1. Select the operation mode and click Finish.
  1. Click Finish.

Deactivating Operation Mode

You can define an OPS that automatically deactivates the operation mode. Without operation modes, the default message distribution is applied. For more information, refer to: Message Control. An operation mode can be set manually again at any time.

  • The Create/Edit Operation Procedure Step dialog box is displayed.
  1. Open the OPS to be Performed tab.
  1. In the Label field, enter a text.
  1. In the OPS Type field, select Set Operation Mode.
  1. To deactivate the operation mode, keep the Operation Mode field empty.
  1. Click Finish.

Starting Video Stream Recordings

You can create an OPS for starting a video stream recording. The recorded video stream can be viewed in the VMS client and used as an evidence.

  • The connection to the VMS has been set up.
  • The cameras have been synchronized in Siveillance Control.
  • The camera sequence element is created. For more information refer to: Creating Camera Sequence Elements in Subsystems Integration with Video API.
  • The OPS/Workflow Configuration perspective is displayed.
  1. In the OPS to be Performed tab, you have the following options:
  • Label: Enter a description for the operation procedure step.
  • OPS Type: Select Start Video Recording.
  1. Click Finish.

Stopping Video Stream Recordings

You can create an OPS for stopping a video stream recording.

  • The connection to the VMS has been set up.
  • The cameras have been synchronized in Siveillance Control.
  • The camera sequence element is created. For more information refer to: Creating Camera Sequence Elements in Subsystems Integration with Video API.
  • The OPS/Workflow Configuration perspective is displayed.
  1. In the OPS to be Performed tab, you have the following options:
  • Label: Enter a description for the operation procedure step.
  • OPS Type: Select Stop Video Recording.
  1. Click Finish.

Creating Bookmarks for Recorded Video Streams

You can create bookmarks for recorded video streams.

  • The connection to the VMS has been set up.
  • The cameras have been synchronized in Siveillance Control.
  • The OPS/Workflow Configuration perspective is displayed.
  1. In the OPS to be Performed tab, you have the following options:
  • Label: Enter a description for the operation procedure step.
  • OPS Type: Select Bookmark Video.
  1. Click Finish.