Security: Video

Upcoming with FW 7.10 and CM 6.20, Camera Trainer is a licensable Intelligent Video Analytics module that allows uses to define objects of intereste and train their own detectors for them based on examples of target objects and non-target objects. In contrast to the moving objects detected in general by IVA 7.10, Camera Trainer allows detection of both moving and non-moving objects, separates and immediately classifies them. Training can be done both on live video as well as on recordings available through the respective camera. The resulting detectors can be down- and uploaded for distribution to other cameras. The attached fact sheet lists the cameras that support Camera Trainer. The attached technical note describes in-depth what Camera Trainer is, how it works, what to use it for and what not, and how to configure it. The configuration is also shown in the following how-to videos: Setup Camera Trainer Camera learning phase with recorded video   Configure Camera Trainer Task   Backup Camera Trainer Configuration - Method 1   Backup Camera Trainer Configuration - Method 2 Setup VCA Masking

Related Products: BVMS Operator Client, BRS Overview: BVMS CS gets from BRS the camera states and the events. BVMS OC connects to BRS for camera live view and playback. The BVMS OC to BRS connection is DCOM based (BVMS CS to BRS connection - either web services or DCOM). Troubleshooting and information providing steps: 1. Connectivity issues between BVMS OC and BRS. We speak for BVMS OC to BRS connectivity issue when: BVMS CC scans the BRS and BVMS CS gets the camera states and events (red dot on camera icon when the camera is recording for example) but BVMS OC get no live view or playback from the BRS cameras.      Step 1.  Check if the cameras are correctly configured in BRS and that BRS itself gets live view and recording from the cameras Step 2. DCOM "ConnectionServer" is not registered correctly. "dcomcnfg.exe" navigate to "Component Services - Computers - My Computer - DCOM Config" check if entry "ConnectionServer" is listed. if there is no such entry, register the ConnectionServer out of the installation dir. Open console and navigate to the BVMS installation DCOM directory, e.g. C:\Porgram files (x86)\Bosch\VMS\DCOM type "ConnectionServer.exe /regserver" - press enter refresh DCOMconfig window and check if entry "ConnectionServer" is listed. Restart OC and BRS cameras should work. Step 3. Check and correct the DCOM settings on OC. start dcomcnfg go to Computer and then to MyComputer right click on MyComputer and open properties switch to DCOM-Security Go one after other to both tabs "Edit Limits" and for the accounts "Everyone" and "Anonymous" check all the checkers under the option "Allow" restart the PC   2. BVMS OC doesn’t get BRS cameras Live View, but playback from the same cameras works. Reproduce the issue, note the date and time. Is there other BVMS OC machine where the liveview works as expected? Is the live view working in BRS itself? provide the answer to the above questions and the BVMS OC Configuration Collector Logs to technical support   3. BVMS OC doesn’t get playback from BRS cameras, but gets live view from the same cameras Does the BVMS OC find the time line of the recording? Is it possible to get the playback of the camera on the BRS Appliance itself? Is there other BVMS OC machine where the playback works as expected? Is the playback working in BRS itself? Reproduce the issue provide the answer to the above questions and the BVMS OC Configuration Collector Logs to technical support

Related Products: Video Analytics for Firmware 6.60 and above This article covers traffic monitoring of Bosch Video Analytics with How to Videos (one already available and one in planning) Default scenario of wrong way detection Learn how to use the default scenario of wrong way detection: A predefined scenario that can be used to detect an object that is traveling the wrong way.   Default scenario traffic incidents This predefined scenario is designed to detect common traffic incidents on roads: Wrong way – triggers an alarm if object travels in wrong direction Pedestrian – triggers an alarm if pedestrian is on the road Slow vehicle – triggers an alarm if vehicle moves slower then predefined speed. Stopped vehicle – triggers an alarm when vehicle is stopped longer than predefined time span. Dropped object – Triggers and alarm if an object is dropped on the road   This how to video shows in detail how to use the predefined tasks Wrong way, Slow vehicle and Stopped vehicle.   Note: If needed you can get additional how to information on camera calibration.  

+++ Update: new Excel template file with detailed explanations of all parameters +++ Intro: The Project Assistant offers two ways of importing existing project data: Option 1) Importing a .bpassist file, which was exported from the app at some point and which contains all information and data ever created/entered inside the app for that specific project. Simply select the "Project Assistant" mode >> click "continue" >> and press "import". Option 2) Importing from a tab-separated text file. This option may be useful, if you have existing project data, e.g. in an Excel spreadsheet, which you want to transfer into the Project Assistant for further use. This article deals with option 2 and explains the steps potentially needed before you can refer to the steps explained in the following Youtube video ("Import from file"). Let's assume you already have existing project data prepared in an Excel spreadsheet and you want to transfer that data into a format that can be imported to the Project Assistant Go to the Bosch Security Systems DownloadStore and download the provided template file "example_project_import_report_template.txt" or the NEW Excel file " 2019_02_20_example_project_IMPORT_template.xlsx" , which also includes detailed instructions and explanations on each parameter. Import the .txt template file into Excel by opening the template file with Excel and following these steps:  Select "delimited" as well as "My data has headers." Select "Tab" in the Delimiters section and finish up the Excel import by pressing "Finish". INSTEAD, you can also use the NEW Excel file, where you can avoid the above described initial import step of the .txt file.   [Option A] According to the provided data columns, copy and paste your existing data from your initial spreadsheet file into the template file (you do not need to populate every column of the template) [Option B] This option works the other way around. Use the Project Assistant header tags, e.g. [ip], [mac], etc., which you can find in the template file and add these tags to the column headers in your initial Excel spreadsheet (cf. screenshot below). The Project Assistant is capable of searching the .txt import file for these tags and of filtering out the corresponding columns (no matter the order of the columns). Go to "Save As" in Excel and save the newly populated template file as a "Unicode Text (*.txt")" file   Transfer the file to where you can find it with the Project Assistant and start the app Create a new project Set a password for the project itself as well as default passwords for the cameras that you would like to assign That's it - Now it is time to refer to the Youtube video mentioned above Enjoy using the Project Assistant and feel free to share your feedback with us!  

This Video should help you to understand, what calibration means, why and when to calibrate the cameras.

Related Products: Video Analytics for Firmware 6.60 and above Technical Note on Intrusion Detection The technical Note  attached to this article contains detailed technical description of Intrusion Detection, set up guidance for different usage scenarios and best practices. It is useful to get in depth knowledge about Intrusion detection or to find the answer of frequently asked questions.   Intrusion detection without calibration Learn how to use the default scenario - Intrusion detection no camera calibration: A predefined scenario that can be used to detect intruders in small areas and controlled environments   Intrusion detection one field   Learn how to use the default scenario - Intrusion detection one field: A predefined scenario that can be used to detect intruders in small areas.   Intrusion detection two fields   Learn how to use the default scenario - Intrusion detection two fields: A predefined scenario that can be used to detect intruders in large outdoor areas.  Note: If needed you can get additional how to information on camera calibration.

 Related Products: Video Analytics for Firmware 6.60 and above This article describes how to count with Bosch Video Analytics with How to Video and a Technical Note on the topic. View the video to get initial idea how to set up the feature, short explanations on the prerequisites and an example configuration.    For in depth description of the feature counting please check the attached Technical Note. It provides background information and technical details and can support you to configure and optimize a particular counting scenario.  How to Video: People counting default scenario Learn how to configure the default scenario - People counting: A predefined scenario that can be used to count people that are crossing a specified / specific line.   Technical Note on Counting The attached document describes in depth the count feature of Video Analytics. It explains how to plan the camera perspective and best practices for camera view, the set up for the scenario people counting and the options to access the counter data.   Note: If needed you can get additional how to information on camera calibration.

Never lose track of an object of interest! Intelligent Tracking automatically zooms in to and follows a selected Intelligent Video Analytics object as far as possible with the camera. For AUTODOME / MIC IP 7000, this means automatically steering the camera to zoom in to the object and follow it. For a FLEXIDOME IP panoramic 7000, Intelligent Tracking is available in the Virtual PTZ video and steers the dewarped cut-out. For DINION / FLEXIDOME IP 7000 / 8000 cameras, Intelligent Tracking can steer a region of interest (ROI) stream. The technical note in the attachment discribes how to set Intelligent Tracking up with FW 6.30 and lists the differences based on the camera types.

Object classification takes an object detected and tracked by either Essential or Intelligent Video Analytics, evaluates its geometric and speed properties, and decides whether the object is an upright person, a bike, a car or a truck. The technical note in the attachment provides an overview of object classification, describes how to configure it with FW 6.30, and what the limitations are.

The museum mode of Intelligent and Essential Video Analytics is an optimized tracking mode to detect whenever someone tries to reach towards and touch a valuable asset like a museum exhibit. It can also be used in any other application where approaching a sterile zone from a more crowded environment shall be detected. The attached tech note describes when and how to use it with FW 6.30.

The technical note in the attachment describes how to track ships using Intelligent Video Analytics with FW 6.30, how to configure this and what the limitations are.

The attached technical note describes the camera tamper detection options available with FW 6.30: Scene too dark / bright, global change, reference image check

The attached technical note describes idle and removed object detection with Intelligent or Essential Video Analytics in FW 6.30, how to configure it and what the limitations are.

The attached technical note describes w hich camera settings influence the performance of Essential or Intelligent Video Analytics in Bosch IP cameras, and what the best practices are.

The attached technical note describes h ow to benchmark and differentiate video analytics solutions.

There are several Video Content Analysis (VCA) algorithms available in Bosch IP cameras: Tamper Detection, MOTION+, Essential Video Analytics, Intelligent Video Analytics and Intelligent Tracking. To receive alarm events from them and visualize the results, a client is needed. Each client can choose to present only a part of information and in a different way. The attached technical note gives a high-level overview of the clients supplied by Bosch and the different integration possibilities into 3rd party systems available today. Further information concerning integration into 3rd party software can be found at the Integration Partner Program (IPP) webpage.

The tech note in the attachment describes how to set up map displays of objects detected and tracked by Intelligent Video Analytics, Essential Video Analytics or Intelligent Tracking with FW 6.4x and Video Security Client 2.1.

The attached technical notes give a short introduction to scripting alarm and counter tasks with Intelligent and Essential Video Analytics in FW 6.60. It also provides a broad selection of example scripts for explanation as well as including real world application examples.

The technical note in the attachment details device-specific as well as version-specific differences of Intelligent and Essential Video Analytics from FW 4.0 up to FW 6.60.

How to export the Archive Player in IE