DVTEL Server Based Analytics (Build 4.5.2) Release Notes
Table of Contents TABLE OF CONTENTS... 2 INTRODUCTION... 3 SERVER BASED ANALYTICS COMPONENTS... 4 BEHAVIOR WATCH (BW) OR VIDEO CONTENT ANALYTICS (VCA)... 4 CORTEX SERVER... 4 CORTEX POLICY MANAGER... 5 RULES MANAGER... 6 INTEGRATION WITH LATITUDE... 6 SERVER BASED ANALYTICS LIMITATIONS... 7
Introduction DVTEL s Server Based Analytics solutions leverage powerful, field-proven video analytics algorithms to turn any camera connected to the Latitude NVMS into an intelligent, proactive, real-time detection system. Built-in rule-based alert functionality enables control room personnel to precisely define which event warrants an alert, based on their organization s unique needs. This document lists the components of the server based analytics solution and offers references to more detailed user guides for deeper exploration. It also offers list of known limitations and suggests mitigations for both short term and long term.
Server Based Analytics Components The server based analytics solution is comprised of the following components: 1. Behavior Watch (BW) or Video Content Analytics (VCA). 2. Cortex Server 3. Cortex policy manager 4. Rules Manager 5. Integration with Latitude Behavior Watch (BW) or Video Content Analytics (VCA) The VCA is the brain behind the Server Based Analytics. VCA is an advanced Video Detection Unit for real-time detection and tracking of people and objects in video images, for rule-based event identification, and for display and investigation of detected events. The product utilizes robust video analytics technology to process up to 24 concurrent video streams. The BW user guide includes the following subjects: 1. Overview: general overview of Behavior Watch. 2. Setup: procedures for setting up the hardware and software. 3. Getting Started: running the Behavior Watch software, and a description of the start-up Application. 4. Video Source: overview on setting up video sources. 5. Scanner: overview of the Scanner and its functionality. Cortex Server The Cortex Server is the manager of all server based analytics components. It sets the standard for managing numerous live video alarms, simultaneously, from multiple video analytics devices installed in local or remote sites. Cortex server remotely configures and controls multiple VCA units for object detection and tracking, behavior identification, counting and alarm and video transmission. The Cortex Server user guide includes the following subjects: 1. Overview: general overview of Cortex.
2. Setup: procedures for installing the hardware and software. 3. Getting Started: running the application and a description of the Cortex start-up application. 4. Cortex Viewer: installation of the Cortex application without the Cortex Server application and a description of the start-up application. 5. Main Interface: overview of the Cortex Viewer interface. 6. Operation: overview of the functionality of Cortex Viewer. 7. Mapping: overview of using the mapping features. 8. Cortex Searcher: a tool for searching through recorded video alarms. 9. Rules Manager/Device Explorer: overview of the Rules Manager application and procedures on how to set up the rules for triggering alarms, implementing a site map and customizing a map with camera locations. 10. AVCS: application to store the video clip sequence. 11. CountWatch DB Writer: application for connecting devices to a single database. 12. Reporter Manager: security and administrative tool for CW Reports. 13. CW Reports: web-based application that retrieves and presents stored counting data. 14. DB Maintenance: overview of the database maintenance utility. 15. Alerter: optional application for generating alarm reports and sending them to specific Email addresses. 16. Cortex Server: guide to the Cortex Server and its functionality. Cortex Policy Manager The Cortex policy manager is an administrative tool enabling a system administrator to prohibit unauthorized access to the VCA and the information generated by these units. Certain users can be given or denied permission to view video and alarms originating from a specific camera, as well as to setup rules or other VCA parameters by using the Rules Manager. The Cortex policy manager user guide includes the following subjects: 1. Overview: general overview of Behavior Watch. 2. Cortex Policy Manager Interface: general overview of the Interface. 3. Managing Sites: procedures for setting up and managing sites. 4. Managing Users: procedures for setting up and managing users. 5. Managing Groups: procedures for setting up and managing groups.
Rules Manager The Rules Manager configures and manages video detection rule-sets. The Rules Manager user guide includes the following subjects: 1. Launching Rules Manager/Device Explorer 2. Device Explorer View 3. Rules Manager View 4. Working with MSFs 5. Working with Alarm Geometries 6. Setting Alarms 7. Alarm Types Integration with Latitude The integration with Latitude provides seamless archiving and monitoring of video analytic events inside Latitude s Control Center, where room operators see analytic alarm indications as an overlay on live and playback video. Latitude NVMS will tag, archive and maintain every incident originating from an analytic alarm. These alarms can be managed at a later time to query and retrieve recorded video streams The integration with Latitude user guide includes the following subjects: 1. System requirements 2. Installation 3. Configuration 4. Metadata On Screen Display (OSD) 5. Video Analytics map 6. Upgrading / uninstalling 7. Limitations 8. Troubleshooting
Server Based Analytics Limitations The following section lists a few known limitations with the server based analytics and suggests mitigations for both short term and long term. 1. Pricing: Limitation in the same server all analytics channels must have the same package price. If packages are mixed in the same server, the higher package price applies to all channels. Mitigation avoid using mix packages, otherwise use separate servers in case mixed packages are needed. 2. Overlay misplaced due to resolution change: Limitation some cameras change the region of interest (ROI) upon switching resolutions. The analytic is performed on ROI A while the video displayed on ROI B and therefore OSD is misplaced on the video display. This happens on separate stream scenario. Mitigation In the short term verify that both streams have the same ROI. In the long term we will remove this limitation for all DVTEL cameras. 3. False alarm and misdetection due to resolution change: Limitation some cameras change the region of interest (ROI) upon switching resolutions. If analytic configuration is done on ROI A and video resolution is changed after configuration and ROI B is being analyzed by the analytic server false alarms and misdetection will happen. Mitigation when resolution change causes ROI change - reconfigure the rule. 4. Reconfiguration of alarm type actions after removing and adding analytics camera: Limitation when removing camera from the analytics cameras list the associated alarm type and its configured actions will be deleted. Mitigation avoid as much possible to remove camera from analytics list and then re-add it. If removed and added again, reconfigure alarm type actions. In the long term, this limitation will be removed.