Senstar Avigilon Unity Video / Network Manager Integration
senstar.com
Monitor and control Senstar sensors within Avigilon Unity Video
The NMS-Unity Video integration provides a software integration between Senstar perimeter intrusion detection sensors and Unity Video, avoiding the need for relay output modules and corresponding hardware intrusion panels.
Senstar's Network Manager software provides a common interface for monitoring Senstar sensors from VMS, SMS, and PSIM systems. The Network Manager Service includes functionality to integrate Senstar sensors and devices with Unity Video via its POS Transactions interface. The Network Manager software also includes a Watchdog service, ensuring that any loss of communications between the sensor network and Unity Video generates a notification.
From within Unity Video, operators can:
- View sensor alarms in Alarm or Focus of Attention windows
- View video associated with alarms
- Acknowledge alarms
- Monitor equipment faults
- Monitor communication status
Features and Benefits
- Display zone alarms, hardware diagnostic faults, and communication faults from Senstar sensors within Unity Video
- Sensor events are received as POS Transactions that can be selected for monitoring and used to trigger alarms and rules
- Watchdog timer ensures any loss of communications between sensor network and Unity Video generates a notification
- Support for Network Manager redundancy
- Supported sensors include FlexZone®, FiberPatrol® FP1150, FiberPatrol® FP400, Senstar LM100, OmniTrax®, UltraWave™, UltraLink™ I/O, and XField®
- Alarm Logic Engine support
- Based on the Unity Video POS Transaction Engine (generic text interface)
- Compatible with Unity Video version versions 7.14.x.x and 8.x.x.x and newer, and NMS 2.54 or newer
[Image Description: Screenshot showing Avigilon Unity Video interface with alarms and video feeds, labeled "Avigilon Unity Video integrated with Senstar perimeter intrusion detection sensors"]
Unity Video User Interface
Senstar sensor alarms appear in Unity Video as POS Transaction events, which can be used to trigger alarms, camera callups, and rules.
[Image Description: Screenshot of Avigilon Unity Video interface displaying active alarms for "LM100 Zone 2" and "Front Gate", with timestamps and options to acknowledge or open in view.]
System Integration
[Diagram Description: A system integration diagram showing "Senstar Sensors" connected to "NM/Watchdog configuration set-up tools". This leads to "Network Manager Service (NMS)". NMS connects to "POS Engine", which then interfaces with "Avigilon Unity Video". The diagram also shows "Unity Video displays sensor events" and "Unity Video server with Network Manager Watchdog". The overall flow is labeled "NMS-Unity Video system integration".]
Configuration Overview
Configuration consists of three main steps:
- Configure the Senstar Network Manager software.
- Install and configure Senstar's NM Watchdog software on the Unity Video server.
- Configure the Unity Video software to accept NM events via its POS Transactions interface.
Configure SMS Settings in NMS Front Panel
1. In the NMS Front Panel, enter the SMS properties for the sensor network under the Text tab:
Parameter | Value |
---|---|
Server interface type, TCP addresses and ports | As required |
Message Start prefix | 3E |
Message End delimiter | 3C |
Encoding | ASCII |
Message Block Min Size | 40 |
Message Block Fill | 00 |
In the Nodes tab, enter text strings for the ON state of every sensor alarm to be reported in Unity Video. Define strings for OFF states only if you want to program something like an auto-acknowledge when alarm goes inactive (in this case, it would still require a "purge" step in Unity Video).
Install NMS Watchdog
1. Install Senstar's NMS Watchdog (included in the NM software suite) on the Unity Video server.
2. In the NM Watchdog Cfg, enter the SMS properties under the SMS tab:
Parameter | Value |
---|---|
Server interface type, TCP addresses and ports | As required |
Message Start prefix | 3E |
Message End delimiter | 3C |
Encoding | ASCII |
Message Block Min Size | 40 |
Message Block Fill | 00 |
NMS Configuration
3. On NMS tabs (one for each NMS to be monitored):
- Enter the NM Id and IP address.
- Enter a text string for the Offline state. Define strings for Online state only if you want to program something like an auto-acknowledge when alarm goes inactive (in this case, it would still require a "purge" step in Unity Video).
[Image Description: Screenshot of "NM Watchdog Cfg" showing settings for NM Id, IP Address, and text strings for Offline/Online states.]
Configure Unity Video
1. In Setup > POS Transactions, define a POS transaction source (one for NMS Watchdog and each NMS instance):
a. Enter the IP and TCP port number to connect to Watchdog/NMS as well as the Client connection type.
b. Define Transaction Source Data Format:
Parameter | Value |
---|---|
Name | NMS |
Description | NMS message interface |
Transaction Start Text | > |
Transaction End Text | < |
Encoding | UTF-8 |
Filters | Remove `\00' |
Set Transaction Exceptions for each Watchdog/NMS alarm:
- Enter a unique name for each alarm reported.
- Enter a text string matching the entry in NMS.
[Image Description: Screenshot of "POS Transactions Setup" showing configuration for transaction source, data format, and exceptions.]
c. Select Linked Cameras and save the transaction's name and description.
[Image Description: Screenshot of "Select Linked Cameras" and "Set Transaction Source Name and Description" in POS Transactions setup.]
2. In Setup > Alarms, create an entry for each Watchdog/NMS alarm:
- Select Alarm Trigger Source for External Software Event.
- Select device to link to alarm (suggest camera with view of alarm detection zone).
- Select alarm recipients (users to be notified of alarm) and sound to be played when alarm triggered.
- Define Alarm properties (Display name, priority, schedule).
[Image Description: Screenshot of "Alarms Setup" showing alarm properties and linking to devices.]
3. In Setup > Rules, define rules that link Transaction Exceptions to alarms (for each Watchdog/NMS alarm):
- Select Rule event to trigger rule of POS transaction exception:
- Specify the transaction exception using the previously defined name.
- Specify the transaction source using the previously defined source.
- Select Action of triggering an alarm.
- Select one of the alarms defined above.
- Define Rule Properties (Display name, schedule).
[Image Description: Screenshot of "Rules Setup" showing rule creation based on POS transaction exceptions and triggering alarms.]
Version: R3-E-01/24. Copyright ©2024. All rights reserved. Features and specifications are subject to change without notice. The Senstar name and logo, FiberPatrol, and FlexZone are registered trademarks of Senstar Corporation. UltraWave and the Senstar LM100 are trademarks of Senstar Corporation.