Incidents provide an overview of currently ongoing incidents related to the premises under control of the operator. Standard operating procedures (SOP) provide steps on resolving incidents. An incident can be any type of event that needs the operator's action for example, an alarm raised by a connected subsystem. If multiple alarms are received from the same location or device, they are automatically assigned to an incident until that incident is acknowledged. Once an existing incident is acknowledged, any new alarms from the same location or device are assigned to a new incident. If the subsystem is not connected, contact your administrator. For more information on creating the incident manually, refer to: Creating incidents.
The operator will acknowledge the incident and classify the incident. Depending on the classification a preconfigured SOP is displayed. The SOP guides the operator through the required response to the incident. The SOP may include decisions, that the operator needs to take. Depending on the decision taken the SOP adapts and provides different procedure steps for different situations.
The SOP may change at any time until the incident is closed, for example if the classification is changed. Uncompleted operating procedure steps (OPS) may also disappear with the change. If already completed, OPS no longer belong to a changed SOP. They stay in the SOP list to document the incident’s history. The type of a completed but invalid OPS is changed to Deleted.
Video alarms
For video alarms, only one video alarm can be assigned to an incident. When a video alarm is triggered, the corresponding incident recording and live streaming feeds display in the Video playback section of the specific incident.
Live: Helps in the continuous monitoring of premises and providing an immediate response when an incident occurs. This is indicated with a green dot.
Incident recording: Provides an immediate access to review the incident, thereby ensuring a better assessment and timely response. The incident recording video includes a 25 second playback, capturing 5 seconds before and 20 seconds after the alarm is triggered.
Each video feed has an expansion icon, and if one feed is expanded, the other is hidden.
To ensure the Arcules video alarm is visible in Incidents, a rule needs to be configured in Arcules. All updates to the status of video alarms in Security Manager are also synchronized with Arcules.
The camera recording settings should be configured in Arcules to match the video playback duration in Security Manager. So, the video will play for 25 seconds as mentioned above.