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 - Upgrade guide
Describes how to upgrade a BVMS system step by step.
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 show the different design options that are available when designing a BVMS system.
For BVMS 10.1, we have extended the blueprints with Person Identification, the Access Management System, and updated the Enterprise overview.
From BVMS 10.0 onwards BVMS is an ONVIF Profile S conformant client. Cameras which are listed as Profile S compliant product on the ONVIF website are supported based on the ONVIF Profile S functionality. In the table below you can find an overview of the tested and supported ONVIF cameras for BVMS.
List of tested cameras
BVMS 7.5 list of tested ONVIF cameras
BVMS 8.0 List of tested ONVIF cameras
BVMS 9.0 List of tested ONVIF cameras
BVMS 10.0 List of tested ONVIF cameras
BVMS 10.0.1 List of tested ONVIF cameras
BVMS 10.1 List of tested ONVIF cameras
The table below shows in which situation a specific camera can be connected to BVMS and is supported.
BVMS 9.0 and older
BVMS 10.0 and newer
ONVIF Profile S compliant camera
BVMS tested camera
For BVMS version 10.0 and above, please make sure to go through these steps:
Please check the List of tested cameras.
If the device is not listed in the List of tested cameras, then please check here and make sure that your device is ONVIF Profile S compliant.
If your camera is not listed in the tested cameras and is not listed on the ONVIF website as Profile S conformant, we cannot help you when you have an issue with this device. You should approach the device manufacturer to certify the device as ONVIF Profile S conformant.
For example, if you have an Axis camera, M1004 model, please fill in your product details in the Application Type, Profile(s), Manufacturer and the Product Name fields, under the Product Search option, and press on the “Search” button:
3. If your device is ONVIF profile S compliant you can contact Bosch Central Technical Support and request assistance.
Cameras listed as tested are owned by Bosch and issues can be fully investigated by Bosch.
Cameras not listed as tested are not owned by Bosch. Solving issues might take longer as it requires collaboration with the camera vendor.
Bosch support teams might need to refer to the camera manufacturer’s support line to help fixing the issue.
We consider the firmware listed on the ONVIF website as the minimum firmware version of a camera. Please let us know if you run into issues with newer firmware versions so that we can investigate those accordingly. If the problem is a firmware regression, we might need to refer you to the camera manufacturer for support.
Let’s suppose that you have one setup which consists in an Adam 6060 I/O module, BVMS 10.1 and a DINION IP thermal 8000 camera.
Can the state of an ADAM relay module be changed when the IVA from the camera generates an alarm?
This guide is meant to help you adding new cameras in VRM in Configuration Client and display their images in Operator Client.
Before adding a new camera there are a few things that need to be taken into consideration:
You are not exceeding the maximum number of channels allowed. Each unit has a maximum number of channels. For example:
DIP 5000 AIO the maximum number of channels is 42
DIP 6000/ 7000 AIO the maximum number of channels is 128
You have the neccesarry number of licenses installed on the system
The units come with 8 channels pre-licensed. If you want to add more cameras or encoders/ decoders, you need first to make sure that licenses have been purchased.
The system has enough storage to cover the retention time of the cameras. If there is no storage available, there is a risk that your system will stop recording.
The bandwidth available of the unit is not exceeded. For example:
Bandwidth DIP 5000 AIO: 170 Mbit/s
Bandwidth 6000/ 7000 AIO: 550 Mbit/s
PC/ Server/ Workstation
Depending on the license type you have installed in the Bosch Video Management System (BVMS), you can add a certain number and different types of cameras/ encoders. BVMS s upports 3 rd party cameras as well, but they need to be compliant to ONVIF Profile S.
This article explains how to add new ONVIF cameras to a system that runs in full Bosch Video Management System (BVMS) via the Configuration Client. We recommend using Bosch Workstations and Servers. They are fully tested and optimized for Bosch Video Management System.
PC/ Server/ Workstation
A possible situation can occur when you have, for example, one DIP 3000 with BVMS 8.0 and CPP7.3 cameras. The cameras are not working because the firmware is old.
The problem that might arise could be:
Configuration Client will display a message like: "unknown platform"
Gaps in recordings or not recording at all
VCA settings cannot be changed
Logs warning: "2020-11-22 04:49:29.339;cameraId=10.13.22.98\0\1;Sender;Error;This device has an abnormal high storage consumption. To protect other recordings, storage allocation is reduced. But this may result in recording gaps for this device"
The attached document describes how a Tattile camera can be connected to BVMS and describes the provided functionality in the BVMS operator client. We recommend keeping the Tattile camera documentation and BVMS configuration manual at hand to fine tune the system configuration to the specific needs of your project.
The BVMS Project Checklist is an Excel-based tool which makes it easier to design a BVMS system. The attachments include a document describing how to use the project checklist and the project checklist itself.
Compared to hardware, in which it is relatively easy to define an end-of-support concept based on the expected lifetime, software behaves totally different. In theory, when the environment does not change, software can still be running ten years after it has been installed. As new versions of the software are released regularly, it is important for customers to know what they can expect from Bosch Building Technologies when the software is purchased. This document describes how Bosch Building Technologies handles the life-cycle of the BVMS, BIS, AMS, and APE, and in which state a specific release can reside. Additionally this document lists the up-to-date situation for all of those software packages.
Which Bosch encoders and decoders are compatible with BVMS?
Up until some years ago, new released cameras, encoders, domes and decoders that are introduced into market after a BVMS release could not be connected to an existing BVMS version because these cameras where not known to the BVMS. In the BVMS 4.5.1, a new concept was introduced. This concept treats Bosch video encoders and decoders as generic devices, and automatically recognizes specific device functionality (for example the number of streams, relays and inputs). Based on this information the, at that time, unknown device is added to the system and can be used by the operator. The attached document provides a detailed description of this functionality.
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.
An attachment is added to this article for each BVMS version. Currently the upgrade guides for BVMS 8.0 and 9.0 are attached to this article. From BVMS 10.0 onwards a description on how to migrate systems has been included as well.
In order to use the software modules, the software needs to be licensed and to receive licenses for the software, the keys need to be registered online.
This article explains how to license a system that runs in full Bosch Video Management System (BVMS) mode with help of Security Systems Software License Manager tool (SLMS).
This technical brief will provide the step-by-step procedure on how to configure “BVMS” presets and save views.
In order to better utilize system resources, BVMS no longer pre-allocates 99 black presets to newly added PTZ cameras in the system. BVMS does not read any existing presets already configured in the camera.
Exporting video with Video Analytics meta data is very useful in the process of optimization of Video Content Analytics performance. One could configure VA, record particular scene and then replay this scene over and over again using different VA configurations.
Moreover the video could be exported and replayed multiple times with different VA configuration settings.
This article describes the different possibilities - BVMS Operator Client and BVMS Viewer, VRM eXpport Wizard, Web Interface of a Bosch Camera. The choice of the tool depends on the way the camera and recording are managed.
When working with previous versions of BVMS, remote connectivity was cumbersome due to the amount of port mapping that needed to be configured. BVMS 7.5 provides a new method of remote connectivity utilizing Secure Shell (SSH) Tunnelling.
The attached document (attachments can be found on the bottom of the page) describes the set-up and configuration of the SSH functionality in BVMS.
In BVMS 10.1 we have added the capability for a management server (or DIVAR IP) to act as a bridge between a corporate network and a video network. We have described the configuration of this scenario in the BVMS 10.1 - Unteaming network interface cards document.