Automation Scenarios for Security Center 5.13 - This guide provides typical Security Center automation examples that you can adapt to your specific needs. - Security Center 5.13

You can use a Security Center automation to play an audio clip, such as a pre-recorded message or a specific sound bite, when a specific event occurs in your system. Alternatively, you can use an event-to-action to achieve the same result.

1. Configure the speaker unit in Security Center.
   You must enroll the speaker unit as a video unit.
2. Configure the automations to trigger output behaviors on the speaker unit.
   You must create two automations: one for activating an output based on a triggering event, and another for deactivating the output when the condition is no longer present.
3. Configure the rule to play an audio clip on the speaker unit.
   This step is performed on the speaker unit's web interface. The output you selected in Security Center becomes an input on the speaker unit.

To trigger a speaker announcement with an automation, you must first enroll the speaker unit in Security Center as a video unit.

1. Connect to your system using Config Tool.
2. Enroll the AXIS speaker unit in Security Center as a video unit.
   The speaker unit is added as a video unit to your system.
3. On the unit's Properties page, select the Enable virtual inputs option, and click Apply.
   The unit reboots, and its icon turns red.
4. After the unit is back online (when its icon turns black), click the Peripherals tab.
   Virtual outputs (1–32) are added to the list of peripherals.

   Now that virtual outputs are enabled on the AXIS speaker unit, you can trigger I/O state changes to these virtual outputs from Security Center.

As the second step in the speaker announcement scenario, you must create two automations: one to activate an output based on a triggering event, and another to deactivate the output when the condition is no longer present.

1. Create a first automation or event-to-action to set an output relay to the Active state.
   For the triggering event, you can choose any event you want. In our example, we use the Alarm triggered event on the Warehouse Security Camera alarm.

   For the action, select Trigger an output, apply it to a virtual output on the speaker unit, and select Active as the output behavior.

2. Create a second automation or event-to-action to set the same output relay to the Normal state.
   For the triggering event, select something that signals that the original condition is cleared. In our example, we use the Alarm acknowledged event on the Warehouse Security Camera alarm.

   For the action, select Trigger an output, apply it to the same virtual output as before, and select Normal as the output behavior.

3. Click Apply.

The final step in the speaker announcement scenario is to create an action on the speaker unit to play the audio clip. This operation is performed from the unit’s web interface.

1. Connect to the unit's web interface.
2. Load the audio clip you want to play when an input is triggered onto the speaker unit.
   1. Click Audio > Audio clips > Add clip.
   2. In the dialog box that opens, enter the Name of the audio clip.
   3. Click the upload button () or drag your audio clip file to the window.
   4. Click Upload.
3. Create the rule to play the audio clip when an input is triggered.
   A rule for an Axis device is similar to an event-to-action in Security Center.
   1. Click System > Events > Rules > Add a rule.
   2. In the dialog box that opens, click Use this rule, and enter the name of the rule.
   3. Click Add a condition, and select Virtual input active from the drop-down list.
   4. Select the port number that corresponds go the virtual output number configured in the automations.
   5. Under the Action label, select Play audio clip while the rule is active.
   6. Click Save.

When access to a door isn't available through a card reader, you can use a Security Center automation to unlock the door when a desk-mounted or wall-mounted button is pressed.

1. Create an event-based automation or event-to-action to unlock the door when the input on the video unit is in the Active state.
   NOTE: To keep the illustrations compact, we only show the screenshot of event-to-actions.

   For the triggering event, select Input active and apply it to the input on the video unit that is connected to the unlock button.

   For the action, select Unlock a door explicitly, and apply it to the door that you want to unlock.

2. Click Apply.

You can use a Security Center automation to email a system report saved as a public task on a regular basis to a selected group of users or cardholders.

1. Create an scheduled automation or scheduled task to email the report.
   NOTE: To keep the illustrations compact, only screenshots for the automation creation are shown.

   In the following example, we create an automation to email a report to the cardholders Andrew and Brandon, and to the Admin user, on the first of every month at midnight.
2. For the response, select Email a report, and select the report you want to send, saved as a public task.
   For this example, we used the Health history task saved under the name Role errors last month.

   For the email recipients:

   • All cardholders and users must have an email address configured.
   • For cardholders and external recipients, you must configure their user profile in the Report Manager role's Properties page.
3. Click OK > Apply.

You can use a Genetec Mission Control™ incident to email a warning message to your system administrator when a unit remains offline for more than X minutes.

1. In Mission Control, create an incident.
   For this example, we’re calling the incident Unit lost. You can choose a different name if it’s more appropriate for your use case.
2. In the Triggers page, click Add event, then select Unit lost.
   We do not specify a source, so the event can apply to any unit in your system.
3. Click Save > Apply.
4. Click the Automation tab, drag the generic activity Parallel tasks to the automation flowchart, and connect it to the Start node.
   For information about Mission Control automation, see Configuring incident automation workflows for Mission Control.
5. Double-click the Parallel tasks activity to open it, then, from the Generic activities group, drag a Delay and a Sequence inside as parallel activities.
6. Double-click the Delay activity, then configure the delay after which you want the system to email a warning to the system administrator.
   In this example, we chose 2 minutes. You can set any delay you want.

   
7. In the blue breadcrumbs, click Parallel tasks, then double-click the Sequence activity to configure it.
8. From the Incident management activities group, drag the Wait for event and Close incident activities inside the Sequence.
   
9. Double-click the Wait for event activity to configure it.
10. In the Wait for event activity box, click the Wait for event drop-down list, then select Specific event.
11. Click Add an item (), then select Unit connected.
12. Click the Event sources drop-down list, select Incident location, then click OK.
    With this configuration, the Wait for event activity ends when the Unit connected event from the same unit that triggered the Unit lost event is received.
13. (Optional) In the blue breadcrumbs, click Sequence, then double-click the Close incident activity.
    The default settings of Any state and a delay of 0 seconds are what we want, so there’s nothing to change.

    The idea here is to close the incident as soon as we receive confirmation that the unit is reconnected to its role, so there’s no need to send a warning message.

    
14. In the blue breadcrumbs, click Flowchart, drag the Security Center activity Send an email to the flowchart, then connect it to the Parallel tasks activity.
15. Double-click the Send an email activity and configure the details.
    1. Select the Admin user as the email recipient, or choose whoever you want to receive the warning email.
       For more information, see How do I configure email sending in Security Center?
    2. Click Edit email and configure the email body.
       In the email configuration dialog box , click the Field button to add fields to the email subject and message.
    3. Click Save when you're finished.
    4. Change the email Priority if necessary.
16. Click Apply.
17. Test the incident first. If it works as expected, change its operational status to In service.