Overview of events and output

Available functionality depends on the system you are using. See the Product comparison chart for more information.

Types of events:

Name

Description

Analytics events:

You can use analytics events as alarms and integrate seamlessly with the Alarms feature.

Analytics events are typically data received from external third-party video content analysis (VCA) providers. An example of a VCA-based system could be an access control system.

Hardware input events:

Hardware input, such as door sensors, can be attached to input ports on hardware devices. Input from such external hardware input units can be used for generating events in the system.

Events based on input from hardware input units attached to hardware devices are called hardware input events.

Some hardware devices have their own capabilities for detecting motion, for detecting moving and/or static objects and more (configured in the hardware devices' own software, typically by accessing a browser-based configuration interface on the hardware device's IP address.) When this is the case, your system considers such detections as input from the hardware, and you can use such detections as input events as well.

Lastly, hardware input events can be based on the system detecting motion in video from a camera, based on motion detection settings in the system.

This type of hardware input events is also called system motion detection events or VMD (Video Motion Detection) events. In earlier versions of the surveillance system, VMD events were an event type of their own. They are now considered a type of hardware input event.

Hardware output:

Hardware output units can be attached to output ports on many hardware devices, allowing you to activate lights, sirens, and more from the system. Such hardware output can be activated automatically by events, or manually from clients.

Manual events:

Events may be generated manually by the users selecting them in their clients. These events are called manual events.

Manual events can be of the type Global events or Timer events:

Global events apply to all hardware whereas timer events are separate events, triggered by the hardware input event, manual event or generic event under which they are defined. Timer events occur a specified number of seconds or minutes after the event, under which they are defined, has occurred. Timer events may be used for a wide variety of purposes, typically for stopping previously triggered actions.

Example:

A camera starts recording based on a hardware input event, for example when a door is opened. A timer event stops the recording after 15 seconds.

Generic events:

Input may also be received in the form of TCP or UDP data packages, which the system can analyze, and—if they match specified criteria—use to generate events. Such events are called generic events.

Output control on event:

Hardware output can be activated automatically when events occur. For example, when a door is opened (hardware input event), lights are switched on (hardware output).

When you configure the output control, you can select between all output and events defined in the system. You are not limited to selecting output or events defined on particular hardware devices. You can use a single event for activating more than one output.

Before you configure events of any type, configure general event handling, such as which ports the system should use for event data. Normally, you can just use the default values, but it is a good idea to verify that your organization is not already using the ports for other purposes. See Configure general event handling.

Before you specify use of hardware input and hardware output units on a hardware device, verify that sensor operation is recognized by the hardware device. Most hardware devices are capable of showing this in their configuration interfaces, or via CGI script commands. Also check the surveillance system's release notes to verify that input and output controlled operations are supported for the hardware device and firmware used. If you are using several servers in a master/slave setup, input and output on a specific hardware device should be defined on one of the servers only. Do not define the same input or output on the same hardware device on several servers.

You do not have to configure hardware input units separately. Any hardware input units connected to hardware devices are automatically detected when you add the hardware devices to the system. The same goes for hardware output, but hardware output does require some simple configuration in the system.

If you want to configure hardware output and automatically trigger output when events occur, so that, for example, lights are switched on when a door is opened or when motion is detected in video, see Add a hardware output and Configure hardware output on event.

When you are ready to configure events, see Add a hardware input event, Add a generic event, and Add a manual event. If you want to use timer events with your other events, see Add a timer event.

© 2018 Milestone Systems A/S