Virtual Operator Guidelines

Have more questions? Submit a request

Virtual Operator Guidelines

Guidelines allow you to specify how Virtual Operators should behave when handling events. This page explains how to create, edit, and manage these guidelines to automate your security operations effectively.

Understanding Guidelines

Guidelines determine when and how Virtual Operators interact with events in your security system. Each guideline consists of:

  1. Triggers - Conditions that determine when the guideline should activate
  2. Actions - What the Virtual Operator should do when the triggers are met

Guidelines Processing Order

Screenshot 2025-04-14 at 12.22.50 PM.pngGuidelines are processed in priority order (top to bottom). Each guideline is checked sequentially when a Virtual Operator processes an event. When all triggers in a guideline are met, the actions associated with that guideline will run.

 

Creating a New Guideline

To create a new guideline:

  1. Navigate to the AI Settings page
  2. Scroll down to the Guidelines section
  3. Click the "Add Guideline" button
  4. A dialog will appear where you can configure your new guideline

Screenshot 2025-04-14 at 12.23.24 PM.png

Configuring a Guideline

Setting the Title

Enter a descriptive title for your guideline (e.g., "Person Seen" or "Vehicle Seen").

Adding Triggers

The Triggers tab allows you to specify conditions that must be met for the guideline to activate:

  1. Select a Subject (what to look for)
  2. Select an Operator (how to compare)
  3. Select a Value (what to compare against)
  4. Click "Add Trigger"

Available trigger types include:

  • Person Seen
  • Vehicle Seen
  • Task Plan Step Type
  • Task Plan Step Category
  • Task Plan Step

Screenshot 2025-04-14 at 12.24.19 PM.png

Adding Actions

The Actions tab allows you to specify what the Virtual Operator should do when all triggers are met:

  1. Select an Action
  2. Enter any required values for the action
  3. Click "Add Action"

Available actions include:

  • Task Plan Step Complete
  • Escalate Event to User
  • Close Event

Note: You can have multiple actions in a guideline, and they will execute in the order listed.

Screenshot 2025-04-14 at 12.25.18 PM.png

Concluding Actions

Some actions (like Close Event) are considered "concluding actions" because they finish processing the event. Concluding actions must be placed after all other actions in your guideline.

Editing Existing Guidelines

To edit an existing guideline:

  1. Find the guideline in the list
  2. Click the edit (pencil) icon next to the guideline
  3. Make your desired changes in the dialog
  4. Click "Save"

Screenshot 2025-04-14 at 12.37.45 PM.png

Reordering Guidelines

You can change the priority order of guidelines using the up and down arrows next to each guideline:

  • Click the up arrow to move a guideline higher in priority
  • Click the down arrow to move a guideline lower in priority

Note: The top guideline cannot be moved up, and the bottom guideline cannot be moved down.

Screenshot 2025-04-14 at 12.37.58 PM.png

Testing Guidelines

For best results, thoroughly test your guidelines to ensure they behave as expected:

  1. Create your guidelines
  2. Deploy Virtual Operators
  3. Monitor their performance with test events
  4. Refine your guidelines as needed

The system will check each guideline sequentially when an event occurs, and if all triggers in a guideline are met, the associated actions will run.

Articles in this section

Was this article helpful?
0 out of 0 found this helpful
Share

Comments

0 comments

Please sign in to leave a comment.