LevelOne FCS-5051 Manual - Page 72

Event Management

Get LevelOne FCS-5051 PDF manuals and user guides View all LevelOne FCS-5051 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 72 highlights

OneSecure Video Management Software Amdinstrator Manual V3.0.09 Event Management When something happens on camera site, such as someone walks by, the door opens or closes, a fire breaks out or the sun goes down - these are all Events. Events which occur in the environment or were preprogrammed in the camera may be used as Triggers. Triggers cause the device to react with Responses. The link between trigger and response is governed by Event Rules. Event rules become active or inactive based upon a weekly Schedule. Each event rule detects one specific trigger and may initiate multiple responses. An example rule would be for NVR to send e-mail to alert the supervisor (Response 1) and trigger alarm (Response 2) when motion detection from camera is triggered (Trigger) during the event handing active period (Schedule). How Does NVR Handle Events In OneSecure, each device can be involved in several event rules. As different device models possess various capabilities, the supported event trigger types would vary. For example, a PIR built-in camera can execute a PIR-triggered event rule, while this option is not provided to other models without this feature; similarly, the supported response types would vary by device models, like Goto-preset behavior can only be executed by PTZ devices. The below chart shows NVR server supported Trigger types and Response types. Once a device is added to NVR server, the server would create empty rules with compatible trigger types for you to configure. 72

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
OneSecure Video Management Software Amdinstrator Manual V3.0.09
72
Event Management
When something happens on camera site, such as someone walks by, the door opens or
closes, a fire breaks out or the sun goes down
–
these are all
Events
. Events which occur in
the environment or were preprogrammed in the camera may be used as
Triggers
. Triggers
cause the device to react with
Responses
. The link between trigger and response is governed
by
Event Rules
. Event rules become active or inactive based upon a weekly
Schedule
. Each
event rule detects one specific trigger and may initiate multiple responses.
An example rule
would be for NVR to send e-mail to alert the supervisor (
Response 1
) and trigger alarm
(
Response 2
) when motion detection from camera is triggered (
Trigger
) during the event
handing active period (
Schedule
).
How Does NVR Handle Events
In OneSecure, each device can be involved in several event rules. As different device models
possess various capabilities, the supported event trigger types would vary. For example, a PIR
built-in camera can execute a PIR-triggered event rule, while this option is not provided to
other models without this feature; similarly, the supported response types would vary by device
models, like Goto-preset behavior can only be executed by PTZ devices. The below chart
shows NVR server supported
Trigger
types and
Response
types. Once a device is added to
NVR server, the server would create empty rules with compatible trigger types for you to
configure.