Loading ...
Loading ...
Loading ...
Example Explanation
Rule Combining
Time, Events, and
Devices
When motion is detected (event condition) on Camera 1, and the day of the week
is Saturday or Sunday (time condition), Camera 1 and Camera 2 should start
recording (action) immediately, and a notification should be sent to the security
manager (action). Then, 5 seconds after motion is no longer detected on Camera
1 or Camera 2, the 2 cameras should stop recording (stop action).
Depending on your organization's needs, it is often a good idea to create many simple rules rather than a few
complex rules. Even if it means you have more rules in your system, it provides an easy way to maintain an
overview of what your rules do. Keeping your rules simple also means that you have much more flexibility
when it comes to deactivating/activating individual rule elements. With simple rules, you can
deactivate/activate entire rules when required.
Rules and events (explained)
Rules are a central element in your system. Rules determine highly important settings, such as when cameras
should record, when PTZ cameras should patrol, when notifications should be sent, etc.
Example - a rule specifying that a particular camera should begin recording when it detects motion:
Events are central elements when using the Manage Rule wizard. In the wizard, events are primarily used for
triggering actions. For example, you can create a rule which specifies that in the event of detected motion, the
surveillance system should take the action of starting recording of video from a particular camera.
The following types of conditions can trigger rules:
Name Description
Events
When events occur on the surveillance system, for example when motion is detected or
the system receives input from external sensors.
Administrator manual | XProtect® VMS 2023 R1
74 | Overview
Loading ...
Loading ...
Loading ...