Routing alarms from the video surveillance system

The framework treats alarms generated by a video camera, such as motion detected, as event points (Image). This procedure explains how to configure each type of alarm point with an alarm extension and route the output from the extension to an alarm class in the Supervisor station. These steps are for a generic video driver. Some details may not apply to all drivers. Exceptions are noted, where possible.
Prerequisites: All video hardware is installed, discovered, configured and reporting a status of {ok}. You are connected to a station with sufficient editing privileges.
  1. Expand the video network down to the camera, make a new Workbench tab (Ctrl + T), double-click the Events node in the Nav tree.
    If there is no Events node under the camera device, the camera does not support importing video surveillance system alarms. Event-enabled video drivers typically support the following types of events:
    • Camera Fail (the camera is in a fault state)
    • Motion Detected (the video surveillance system detected motion)
    The Video Event Manager view opens.

    Some video drivers do not require event discovery. These drivers automatically populate the Discovered pane when this view opens.

  2. If no events open in the view, click the Discover button at the bottom of the view.
    The discovery job runs and any video events open in the Discovered pane.
  3. From the Discovered pane, select one or more events and click Add.
    The Add window opens, displaying selected event(s) as potential Boolean points.
    Image
  4. If the video driver supports other point types (for example string), select the supported point type, and click OK.
    The events open in the Database pane and expand under the Events node in the Nav tree.
    Image

    For each added point, the value under the Out column in the Database pane indicates the event status. For example, an Out value of true indicates that an alarm event is occurring; false indicates no event.

  5. To select an event in preparation to configure its routing, double-click on the alarm event point (Motion Detected, for example), under the Events node in the Nav tree.
    The event Property Sheet opens.
  6. Open the alarm palette, expand the Extensions node, drag a BooleanChangeOfStateAlarmExt to the Motion Detected Boolean Point’s Property Sheet, drop it on the component name and click OK.
  7. To associate a stored video with this alarm, close the alarm palette, open the videoDriver palette, expand the Alarm node, drag a VideoAlarmExtParameters component to the BooleanChangeOfStateAlarmExt in the Property Sheet, drop it on the extension name and click OK.
    When you drop the VideoAlarmExtParameters on the alarm extension, it automatically fills in the associated camera information.
  8. To confirm that the Camera Ord contains the location of the camera, scroll down to Meta Data property.
  9. Create motion in front of the camera, go back to the Event tab and confirm that the Out property changes to true {alarm, unackedAlarm}.
    You may need to switch to the camera and ping the recording server again. The motion-detection recording may take some time.
    The recorded motion should create an alarm in the Alarm Console.