Video surveillance users gain access to Video Analytics once the administrator assigns permissions for the relevant analytics types and defines the number of licenses available at each level. For details, refer to the Administrator guide for Analytics.
Video Analytics capabilities are available across all interfaces of the video surveillance system, enabling end users to work with data conveniently through the web, desktop, and mobile application.
The Analytics functionality of each platform is optimized for its specific features, so the available options vary depending on the interface.
In the Analytics section of the Desktop app, users can perform the following actions:
-
Create and configure cases for specific Analytics types.
-
Set up system reactions for detected cases.
-
Monitor detected events and related data.
In the Desktop app, users can create cases for specific Analytics types. The Desktop app supports the creation of cases for the following Analytics types:
-
People counting in an area
-
Zone intrusion detection
-
Camera damage/ overlap/ vandalism detection
-
Loud sound detection
-
Smoke and fire detection
-
Line crossing detection
Cases for the following Analytics types can only be created and edited in the Web app. Once created in the Web app, they are automatically synchronized with the Desktop app: the cases appear in the lists, and their detected events are displayed in the Events section along with other Analytics events. However, users cannot view case details or edit these cases from within the Desktop app.
-
Visitor counting
-
Face recognition
-
License plate recognition
-
Container number recognition
The Analytics tab of the Desktop app includes the following sections:
-
The Cameras tab includes the cameras associated with analytics cases.
-
The Analytics cases tab lists all existing Analytics cases. Here, users can create and edit cases, view reactions to the cases, monitor statuses of Analytics cases.
-
The Licenses tab gives an overview of both allocated and currently used licenses.
For more details, refer to the relevant documentation page: