In order to quickly offer a technical solution or to provide a professional advice for the next analysis steps, the technical support specialists need to get some general and basic information.
Ticket content should always be in English and provided in a well summarized and structured way in order to be able to provide a quick and appropriate feedback.
Not following the guideline will impact the processing time of the ticket.
Related Products: BVMS SDK, BVMS
Analyzing BVMS systems with SDK components is a challenging task, because the functionality and the runtime behavior of those systems are harder to determine than for a BVMS systems without SDK functionality.
In order to troubleshoot BVMS systems with SDK components support needs the following information and logging.
Please prove the following information to support:
Symptom specific Information
How to retrieve the Hardware ID for BVMS and check the Software Maintenance Agreement (SMA) status?
BVMS stand alone or appliance
Detailed description of the expected behavior of the SDK functionality.
Detailed description of the actual behavior of the SDK functionality.
What type is the standalone SDK application (based on ClientSDK, ServerSDK, or CameoSDK) and on which machine is it running?
Are there additionally client scripts, server scripts or workstation startup scripts?
Do SDK components interact with remote Operator Clients?
Do SDK components interact with the Operator Client UI?
Do SDK components control devices?
How often are client scripts triggered?
How often are scripts triggered by BVMS event?
Which shared resources are accessed by SDK actions? (Dome cameras, AMG, Operator Client UI)
Do SDK components interact with an unreliable environment? (Unstable network, offline devices, offline PCs, etc.)
Do SDK components properly handle offline situations? (offline devices, configuration changes, etc.)
Please provide the Scriplet and/or Log files
The optimal approach is to provide both the scriplet and logging.
ClientScript logfiles: can be found in the ConfigCollection of Operator Client machines.
ServerScript logfiles: can be found in the ConfigColletion of Management Server machines.
Make sure that logging is implemented in the script and that logging is activated in the configuration.
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.
This article 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.
Applications: - Detect parked cars in no-parking zones - Detect blocked emergency exits - Detect the removal of museum exhibits - Detect suspiciously left packages in high-security areas - Detect idle bags in walk-through areas
Limitations: - Not available on thermal cameras - Does not work in crowds - No abandoned baggage detection - No differentiation between baggage and persons sitting or lying down - Does not work in front of moving background like wind in trees or water - Does not work during illumination changes or camera brightness adaptations
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.
BVMS / MVS / VSDK
On request from development to provide a dump file from MVS system please follow the steps in the solution section.
Reproduce the issue
Download the Microsoft debugger procdump (https://technet.microsoft.com/en-us/sysinternals/dd996900.aspx). The procdump tool is also attaced to the article :How To create BVMS memory dump?
When application is crashing, do not click any buttons on the appeared error window that will change the program state.
Run the procdump.exe from the directory where you copied the tool with following command line (Start - cmd):
procdump.exe –ma <name of the programm exe> <dump file name>.dmp
In the case of MVS you need to do that for all 4 MVS services:
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.
Dear Bosch, you have so many nice articles related to BVMS on the knowledge base( 😉 ). I would really like to have a consistent overview of the available information.
Bosch Visio Design Icons
Set of Visio Design icons for Bosch products.
BVMS - Device Compatibility
This document describes how BVMS works with older and newer Bosch cameras.
BVMS - Single port connectivity
This document describes how the SSH functionality works.
BVMS - Configure time services
This document provides a guideline on how to configure time services.
BVMS - Merging VRM systems
This document describes how to merge two VRM systems into a single system.
BVMS - Operator quick guide
This document serves as a quick guide for operators.
BVMS - Streamlining
This document describes the streamlining concept.
BVMS - Configuring a Microsoft iSCSI target
This document explains how a Microsoft iSCSI target can be configured.
BVMS - Deployment guide
This document describes how a BVMS system can be deployed from the commandline. This is useful when using software deployment environments.
Virtualization - A concept explained
This document explains virtualization.
BVMS - Upgrade guide
Described the process on how to upgrade a system (checklist)
BVMS - BIS Connectivity
Describes how to connect BVMS to BIS
BVMS - SDK help
Provides instructions and examples on how to use the BVMS SDK
BVMS - Keyboard shortkeys
Shows a (normal computer) keyboard and the shortkeys that are available for BVMS.
BVMS - OPC Server
Describes the functionality available in the OPC server.
BVMS - Mobile Video Service
Describes the Mobile Video Service conceptually.
BVMS - GDPR
Description on how GDPR impacts BVMS.
BVMS - Network design guide
First version composed together with ASA. Feedback welcome!
BVMS - System design guide
Previously known as pre-sales guide.
BVMS - Policy based recording
Describes the “cameras and recordings” tab, in addition to the product manuals.
BVMS - Blueprints
Shows general BVMS system design blueprints.
BVMS - Activate demo license
Describes how customer can generate and activate their own demo license. Includes link to the LIF file.
BVMS - AE Specification
Architects and Engineering specification.
BVMS - Automatic login of Operator Client
Describes the parameters which allow the operator client to automatically login.
BVMS - ONVIF Compatibility
Lists the tested ONVIF devices.
BVMS - Configuring LDAP
Explains how BVMS can be connected to a LDAP environment.
Safe software delivery
Describes how customers can check the integrity of the installation zip files.
BVMS - Client installation package
Describes how a reduced client installation package can be used.
BVMS - Decoding performance
Shows the workstation performance
BVMS - Migrating SQL Database
Describes how to migrate the SQL database to a different server.
BVMS - Securing the security systems
Describes how to secure a BVMS system.
BVMS - ANPR by ISS
Describes how to configure ISS SecureOS and BVMS to combine ANPR functionality.
BVMS - IEC62676-1
Describes how BVMS meets the requirements specified in IEC62676-1
BVMS Lite - Quick start guide
Describes how BVMS Lite can be set-up.
How-to: Transition from Project Assistant to (B)VMS
Have you ever wondered how to best transition from the Project Assistant to (B)VMS?
Software-defined video surveillance storage
Describes the collaboration between HPE, SUSE and Bosch in modernizing video surveillance storage.
BVMS Person Identification - Data Protection Information
The attached document aims to provide concerned parties, such as customers, users, operators or consultants, with an overview of data privacy and protection related features of BVMS Person Identification.
Software Service and Support
Describes how software moves through the product lifecycle.
VRM eXport Wizard
Describes how to use the VRM eXport wizard
BVMS Project checklist
The BVMS Project Checklist is an Excel-based tool which makes it easier to design a BVMS system.
BVMS - Automated firewall configuration
How does BVMS 10.0.1 (or newer) configure the firewall during the installation of the system?
BVMS - Store snapshot of all cameras
My customers asks me to store the field of view of the cameras connected to BVMS. Is there an easy way to achieve this without opening every camera manually?
BVMS - Demonstrating (JPEG) cameras
How can I use "virtual" cameras to demonstrate BVMS?
How to create CA signed certificates for cameras and distribute
Configure video authenticity / integrity using CA signed certificates
BVMS - Operator collaboration using Slack
Configure BVMS to integrate with Slack.
BVMS - Person Identification Camera Placement Guide
Describes best-practices on camera placement when using person identification.
BVMS - Tattile configuration
Describes how to configure Tattile (LPR) cameras and BVMS.
The attached documents should help you to make the upgrade process as smooth as possible. The upgrade itself is not restricted to BVMS software only. The supported software and firmware versions can be found in the release notes of the related BVMS version.