Enter Add to add a system-monitored event.
and clickThe fields in the following image indicate two elements in the rule: "event source" and "triggering event".
These two fields refer to "event source" in the rule, defining the specific entity (such as cameras, devices, servers, etc.) which can trigger this event.
When setting a thermal related event for thermal cameras, you can select areas, points, or lines as event sources.
This field refers to "triggering event" in the rule. The specific event type detected on the event source will trigger a system-monitored event.
If the source type you selected is Resource Group, you need to set extra conditions to define the triggering event.
Currently, you can set Person Amount More/Less than Threshold and Person Amount More/Less than Threshold (Pre-Alarm) for people analysis group. For these two events, you need to set the threshold which determines whether the selected people analysis groups will trigger an event when the detected number of people stayed less than or more than the threshold.
For example, if you set the threshold as "≥ 100 or ≤ 10", when the number of people detected in the selected people analysis group is more than 100 or less than 10, an event will be triggered to notify the security personnel.
If the source type you selected is Person and the triggering event is Card Number Matched Event, you need to select cards from the Person List so that when someone presents these cards on the card readers of the event sources, an event will be triggered.
For example, if the card of one resident is stolen, you can set a card number matched event for this card. If someone punches this card on the card readers to gain access, an event will be triggered and you can quickly locate the suspect.
If the source type you selected is Parking Lot and the triggering event is Frequently Appeared Vehicle, you can pre-define the frequency.
For example, if you set the frequency to daily 3 times, when the devices in the source parking lot detect the license plate numbers of the vehicles in the selected vehicle list for more than 3 times in one day, an event will be triggered.
If the source type you selected is Vehicle Features and the triggering event is Vehicle Type Matched Event, you need to specify the vehicle type(s). When the source camera detects a vehicle the type of which matches with the one(s) you selected here, a vehicle type matched event will be triggered.
For example, if oil tank truck is not allowed on one road, you can set a vehicle type matched event for the camera mounted on this road and set the vehicle type as Oil Tank Truck. When the camera detects an oil tank truck, an event will be triggered.
This function is used to avoid the same event occurs frequently in a short time, which may aggravate the burden of the event center. You need to set the Ignore Events Recurred in (s) which is the threshold of the recurring events.
For example, if you set the Ignore Events Recurred in (s) to 30 s, the events of the same type occurred on the same camera within 30 s will be regarded as one event.
The Ignore Events Recurred in (s) is 15 s by default. You can set it from 15 s to 1800 s.
The field in the following image indicates one element in the rule: "when". It defines during specified time period, the linkage actions can be triggered.
In the notification duration in the notification schedule, when the source detects the triggering event, an event will be triggered and link the configured linkage actions.
For setting customized template, refer to Configure Arming Schedule Template.
The fields in the following image indicate one element in the rule: "what to do". It defines what actions the system will take to record the event details and trigger basic actions.
Compared with alarm, the system monitored event's linkage actions can be used to record the event details (such as recording and capturing) and trigger basic actions (such as locking or unlocking access point, triggering alarm output, sending email, etc.).
Select the cameras to record video when the event occurs and set the storage location for storing the video footage. You can play back the recorded video footage when checking events in the Alarm & Event Search of the Control Client.
If the event source is a camera, you can trigger the source camera itself for recording by selecting Source Camera.
To trigger other cameras, select Specified Camera and click Add to add other cameras. For example, when the camera outside the door detects suspicious person entering, you can configure to trigger the cameras inside the room to record video.
View Pre-Event Video: If the camera has recorded video before the event, you can view the video recorded from periods preceding the event. Specify the number of seconds which you want to view the recorded video for before the event starts. For example, when someone opens a door, you can view the recorded video to see what happens right before the door opened.
Post-record: Record video from periods following detected event. Specify the number of seconds which you want to record video for after the event stops.
Lock Video Files for: Set the days for protecting the video footage from being overwritten.
Select the cameras to record video when the event occurs and set the storage location for storing the video files. The system will add a tag to the event triggered video footage for convenient search. The tagged video can be searched and checked via the Control Client.
If the event source is a camera, you can trigger the source camera itself for tagged recording by selecting Source Camera.
To trigger other cameras for tagged recording, select Specified Camera and click Add to add other cameras.
You can enter the tag name as desired. You can also click the button below to add the related information to the name.
Set the time range to define the tagged length of the video footage. For example, you can record the tagged video started from 5 seconds before the event and lasted until and 10 seconds after the event. The tagged video can be searched and checked via the Control Client.
Add the description to the tagged video as needed.
Select one camera to capture pictures during the event, and you can view the captured pictures when checking event in the Alarm & Event Search of the Control Client.
Only one camera can be set for capturing pictures.
If the event source is a camera, you can trigger the source camera itself for capturing pictures by selecting Source Camera.
To trigger other camera for capturing pictures, select Specified Camera and select one camera for capturing pictures.
Capture Picture When: Specify the number of seconds to define when the camera will capture pictures for the event. After you set the number of seconds for pre/post-event, the camera will capture one picture at three time points respectively: at the configured seconds before the event starts, at the configured seconds after the event ends, and at the middle of the event (as shown in the picture below).
The pre-event picture is captured from the camera's recorded video footage. This pre-event capture function is only supported by the camera which stores the video in the Recording Server (Cloud Storage Server, Hybrid SAN, or pStor).
You can enable this function to trigger the access points (including doors and floors).
For doors, the doors can be locked, unlocked, remained locked, or remained unlocked when the event occurs.
For floors, the elevators can access the floors freely, with credentials, temporarily, or access forbidden.
For example, you can trigger all the doors remaining locked and all the floors access forbidden when intrusion of a suspicious person is detected.
All Access Points: When the event occurs, the system will trigger all the doors and floors to take certain action.
Specified Access Point: Click Add to select specified access points or emergency operation groups as the linkage targets. When the event occurs, the system will trigger these doors, floors, or doors/floors in the emergency operation groups to take certain action.
Select alarm inputs and these alarm inputs will be armed or disarmed when the event occurs.
For example, when adding an intrusion alarm of camera A, which is mounted at the entrance of the building, you can link the alarm input B, C, and D to arm them, which are PIR detectors mounted in different rooms in the building and are disarmed usually. When camera A detects intrusion alarm, these PIR detectors will be armed and trigger other events or alarms (if rules configured) when they detect new motions, so that the security personnel will get to known where the suspect goes.
Select alarm output (if available) and the external device connected can be activated when the event occurs.
Up to 64 alarm outputs can be selected as event linkage.
Close Alarm Output: The added alarm output(s) can be closed manually, or you can set the time period(unit: s) after which the alarm output(s) will be closed automatically.
When the source you selected for this event rule is resource group, the alarm output can also be closed automatically when the amount of people stayed is less than the threshold you configured here.
Call the preset, patrol or pattern of the selected cameras when the event occurs.
Up to 64 PTZ linkages can be selected as event linkage.
Click Add to select the resources integrated from third-party platform and set the control about detailed operations that will happen when the event occurs.
Select an email template to send the event information according to the defined email settings.
You can select Add New to create a new email template.
For details about setting email template, refer to Set Email Template.
If the source type you selected is Alarm Input, you can select an entry & exit counting group from the drop-down list to attach a report of entry & exit counting in the sent email.
For example, if the fire alarm input detects fire in the building, the security personnel will receive a file, which contains the information such as the number of people still in the building, their names and profiles, phone numbers, and locations of last access.
If the source type you selected is Alarm Input, you can link to print the entry & exit counting report of certain entry & exit counting group.
For example, if the fire alarm input detects fire in the building, the platform will automatically send the entry & exit counting report to all the printers configured in the system so that they can get the information such as the number of people stuck in the building, their names and profiles, phone numbers, and locations of last access.
For details about printer settings, refer to Set Printer.
Trigger user-defined events when the system-monitored event is triggered.
You can select the pre-defined user-defined events in the event list.
You can also click Add New below to set a new user-defined events.
Up to 16 user-defined events can be selected as event linkage.
For setting the user-defined event, refer to Configure User-Defined Event.
After adding a system-monitored event, you can perform the following operations if needed.
Operation |
Description |
---|---|
Trigger Event as Alarm |
Click in the Operation column of system-monitored event settings page to set the alarm properties, recipients, actions, and other parameters. Note:
For details, refer to Configure Alarm. |
Test Event |
Click in the Operation column of system-monitored event settings page to trigger the event manually, and you can check whether the linkage actions take effect. |
Delete Event |
Select the event(s) and click Delete to delete the selected event(s). |
Manage Invalid Event |
If appears near the event name, it means the event is not supported by the device and it is invalid. You should hover the cursor over the and click Delete on the tooltip to delete the event. |
Delete All Invalid Events |
Click Delete All Invalid Items to delete all the invalid events in a batch. |
Filter Event |
Click to expand the filter conditions. Set the conditions and click Filter to filter the events according to the conditions. |
Enter Add to add a system-monitored event.
and clickThe fields in the following image indicate two elements in the rule: "event source" and "triggering event".
These two fields refer to "event source" in the rule, defining the specific entity (such as cameras, devices, servers, etc.) which can trigger this event.
When setting a thermal related event for thermal cameras, you can select areas, points, or lines as event sources.
This field refers to "triggering event" in the rule. The specific event type detected on the event source will trigger a system-monitored event.
If the source type you selected is Resource Group, you need to set extra conditions to define the triggering event.
Currently, you can set Person Amount More/Less than Threshold and Person Amount More/Less than Threshold (Pre-Alarm) for people analysis group. For these two events, you need to set the threshold which determines whether the selected people analysis groups will trigger an event when the detected number of people stayed less than or more than the threshold.
For example, if you set the threshold as "≥ 100 or ≤ 10", when the number of people detected in the selected people analysis group is more than 100 or less than 10, an event will be triggered to notify the security personnel.
If the source type you selected is Person and the triggering event is Card Number Matched Event, you need to select cards from the Person List so that when someone presents these cards on the card readers of the event sources, an event will be triggered.
For example, if the card of one resident is stolen, you can set a card number matched event for this card. If someone punches this card on the card readers to gain access, an event will be triggered and you can quickly locate the suspect.
If the source type you selected is Parking Lot and the triggering event is Frequently Appeared Vehicle, you can pre-define the frequency.
For example, if you set the frequency to daily 3 times, when the devices in the source parking lot detect the license plate numbers of the vehicles in the selected vehicle list for more than 3 times in one day, an event will be triggered.
If the source type you selected is Vehicle Features and the triggering event is Vehicle Type Matched Event, you need to specify the vehicle type(s). When the source camera detects a vehicle the type of which matches with the one(s) you selected here, a vehicle type matched event will be triggered.
For example, if oil tank truck is not allowed on one road, you can set a vehicle type matched event for the camera mounted on this road and set the vehicle type as Oil Tank Truck. When the camera detects an oil tank truck, an event will be triggered.
This function is used to avoid the same event occurs frequently in a short time, which may aggravate the burden of the event center. You need to set the Ignore Events Recurred in (s) which is the threshold of the recurring events.
For example, if you set the Ignore Events Recurred in (s) to 30 s, the events of the same type occurred on the same camera within 30 s will be regarded as one event.
The Ignore Events Recurred in (s) is 15 s by default. You can set it from 15 s to 1800 s.
The field in the following image indicates one element in the rule: "when". It defines during specified time period, the linkage actions can be triggered.
In the notification duration in the notification schedule, when the source detects the triggering event, an event will be triggered and link the configured linkage actions.
For setting customized template, refer to Configure Arming Schedule Template.
The fields in the following image indicate one element in the rule: "what to do". It defines what actions the system will take to record the event details and trigger basic actions.
Compared with alarm, the system monitored event's linkage actions can be used to record the event details (such as recording and capturing) and trigger basic actions (such as locking or unlocking access point, triggering alarm output, sending email, etc.).
Select the cameras to record video when the event occurs and set the storage location for storing the video footage. You can play back the recorded video footage when checking events in the Alarm & Event Search of the Control Client.
If the event source is a camera, you can trigger the source camera itself for recording by selecting Source Camera.
To trigger other cameras, select Specified Camera and click Add to add other cameras. For example, when the camera outside the door detects suspicious person entering, you can configure to trigger the cameras inside the room to record video.
View Pre-Event Video: If the camera has recorded video before the event, you can view the video recorded from periods preceding the event. Specify the number of seconds which you want to view the recorded video for before the event starts. For example, when someone opens a door, you can view the recorded video to see what happens right before the door opened.
Post-record: Record video from periods following detected event. Specify the number of seconds which you want to record video for after the event stops.
Lock Video Files for: Set the days for protecting the video footage from being overwritten.
Select the cameras to record video when the event occurs and set the storage location for storing the video files. The system will add a tag to the event triggered video footage for convenient search. The tagged video can be searched and checked via the Control Client.
If the event source is a camera, you can trigger the source camera itself for tagged recording by selecting Source Camera.
To trigger other cameras for tagged recording, select Specified Camera and click Add to add other cameras.
You can enter the tag name as desired. You can also click the button below to add the related information to the name.
Set the time range to define the tagged length of the video footage. For example, you can record the tagged video started from 5 seconds before the event and lasted until and 10 seconds after the event. The tagged video can be searched and checked via the Control Client.
Add the description to the tagged video as needed.
Select one camera to capture pictures during the event, and you can view the captured pictures when checking event in the Alarm & Event Search of the Control Client.
Only one camera can be set for capturing pictures.
If the event source is a camera, you can trigger the source camera itself for capturing pictures by selecting Source Camera.
To trigger other camera for capturing pictures, select Specified Camera and select one camera for capturing pictures.
Capture Picture When: Specify the number of seconds to define when the camera will capture pictures for the event. After you set the number of seconds for pre/post-event, the camera will capture one picture at three time points respectively: at the configured seconds before the event starts, at the configured seconds after the event ends, and at the middle of the event (as shown in the picture below).
The pre-event picture is captured from the camera's recorded video footage. This pre-event capture function is only supported by the camera which stores the video in the Recording Server (Cloud Storage Server, Hybrid SAN, or pStor).
You can enable this function to trigger the access points (including doors and floors).
For doors, the doors can be locked, unlocked, remained locked, or remained unlocked when the event occurs.
For floors, the elevators can access the floors freely, with credentials, temporarily, or access forbidden.
For example, you can trigger all the doors remaining locked and all the floors access forbidden when intrusion of a suspicious person is detected.
All Access Points: When the event occurs, the system will trigger all the doors and floors to take certain action.
Specified Access Point: Click Add to select specified access points or emergency operation groups as the linkage targets. When the event occurs, the system will trigger these doors, floors, or doors/floors in the emergency operation groups to take certain action.
Select alarm inputs and these alarm inputs will be armed or disarmed when the event occurs.
For example, when adding an intrusion alarm of camera A, which is mounted at the entrance of the building, you can link the alarm input B, C, and D to arm them, which are PIR detectors mounted in different rooms in the building and are disarmed usually. When camera A detects intrusion alarm, these PIR detectors will be armed and trigger other events or alarms (if rules configured) when they detect new motions, so that the security personnel will get to known where the suspect goes.
Select alarm output (if available) and the external device connected can be activated when the event occurs.
Up to 64 alarm outputs can be selected as event linkage.
Close Alarm Output: The added alarm output(s) can be closed manually, or you can set the time period(unit: s) after which the alarm output(s) will be closed automatically.
When the source you selected for this event rule is resource group, the alarm output can also be closed automatically when the amount of people stayed is less than the threshold you configured here.
Call the preset, patrol or pattern of the selected cameras when the event occurs.
Up to 64 PTZ linkages can be selected as event linkage.
Click Add to select the resources integrated from third-party platform and set the control about detailed operations that will happen when the event occurs.
Select an email template to send the event information according to the defined email settings.
You can select Add New to create a new email template.
For details about setting email template, refer to Set Email Template.
If the source type you selected is Alarm Input, you can select an entry & exit counting group from the drop-down list to attach a report of entry & exit counting in the sent email.
For example, if the fire alarm input detects fire in the building, the security personnel will receive a file, which contains the information such as the number of people still in the building, their names and profiles, phone numbers, and locations of last access.
If the source type you selected is Alarm Input, you can link to print the entry & exit counting report of certain entry & exit counting group.
For example, if the fire alarm input detects fire in the building, the platform will automatically send the entry & exit counting report to all the printers configured in the system so that they can get the information such as the number of people stuck in the building, their names and profiles, phone numbers, and locations of last access.
For details about printer settings, refer to Set Printer.
Trigger user-defined events when the system-monitored event is triggered.
You can select the pre-defined user-defined events in the event list.
You can also click Add New below to set a new user-defined events.
Up to 16 user-defined events can be selected as event linkage.
For setting the user-defined event, refer to Configure User-Defined Event.
After adding a system-monitored event, you can perform the following operations if needed.
Operation |
Description |
---|---|
Trigger Event as Alarm |
Click in the Operation column of system-monitored event settings page to set the alarm properties, recipients, actions, and other parameters. Note:
For details, refer to Configure Alarm. |
Test Event |
Click in the Operation column of system-monitored event settings page to trigger the event manually, and you can check whether the linkage actions take effect. |
Delete Event |
Select the event(s) and click Delete to delete the selected event(s). |
Manage Invalid Event |
If appears near the event name, it means the event is not supported by the device and it is invalid. You should hover the cursor over the and click Delete on the tooltip to delete the event. |
Delete All Invalid Events |
Click Delete All Invalid Items to delete all the invalid events in a batch. |
Filter Event |
Click to expand the filter conditions. Set the conditions and click Filter to filter the events according to the conditions. |