The BVMS Project Checklist is an Excel-based tool which makes it easier to design a BVMS system.
This article describes how to use the project checklist.
Pick the attachment you need, depending on the version of BVMS you have
Until some years ago, new released cameras, encoders, domes and decoders that were 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, 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 manual provides information for Mobile Video Service (MVS) within Bosch Video Management System.
You can find: - how to configure the router and Internet Information Service (IIS) - how to add MVS to BVMS - user guide - some troubleshooting tips
This document can also be found online here.
Trying out the BVMS Lite is easy!
Download BVMS Lite from the Download Area and use the quick installation guide to set-up the system.
BVMS Lite contains
8 video channels
1 intrusion panel and can be used without a time limit.
BVMS Lite can be expanded to 42 channels using license extensions.
A step-by-step instruction on how to install the BVMS Lite demo license can be found to this page.
A transfer of the license from the Bosch Software License Manager System (SLMS) to the Bosch Remote Portal is required for every BVMS system to be upgraded from 10.1 to 11.0
Starting with BVMS 11.0 the license activation will be done via the Bosch Remote Portal.
To upgrade an existing system, the BVMS licenses need to be migrated from the old licensing system, Bosch Software License Manager System (SLMS), to the new licensing system available in Bosch Remote Portal.
This article describes the steps that need to be followed when upgrading a system to BVMS 11.0.
Prerequisites for upgrading a system to BVMS 11.0:
Existing license activated in SLMS
Valid Software Assurance (SMA) PRO
Valid account on Bosch Remote Portal
❗ ❗ ❗ IMPORTANT
In BVMS 10.x the computer signature is the link to the license in the SLMS
When upgrading to 11.x the computer signature becomes obsolete and the new Remote Portal tool no longer takes it into consideration
The software Order ID is transferred in the background from SLMS to the Remote Portal
This allows the activation of BVMS 11.x in the Remote Portal using the new identifiers for the Management Server Hardware called System Fingerprint, contained in the System Info file.
In terms of license activation process and compared to other versions of BVMS (<v11.0), the Bosch Remote Portal replaces the Bosch Software License Manager System (SLMS), starting with BVMS v11.0.
A new user registration is required in Bosch Remote Portal and the mandatory information for license activation is the System Info file (generated in the Configuration Client) and the Software order ID (received from the Bosch order desk by e-mail → ordering remains unchanged: still utilizes the Bosch Order Desk)
The remote portal will then provide a "Activation file" which includes all activation details. It needs to be uploaded to the newly installed BVMS system.
The activation process defines the start date of the software maintenance agreement (SMA - software assurance) period.
The end date is shown on the License manager of the BVMS Configuration Client after activation
NEW: Software version-less ordering process: Ordering a BVMS Base or Expansion licenses is not software dependent anymore starting with BVMS 11.0 upwards. During license activation only "non End of Life" (EOL) versions are assigned to the license.
Follow this article and find out the steps that need to be performed when activating a new BVMS 11.0 license.
If you just added a device to BVMS, you get the possible stream options as per a “Config table” known to BVMS.
In this case we have added the FlexiDome IP starlight 7000 VR:
Please follow the steps below, if you wish to use the settings as per the devices current configured capabilities.
With BVMS 11.0, new licensing system was introduced.
Attached document describes how to migrate existing activated BVMS licenses from the Bosch Software License Manager System (SLMS) licensing system to the new Bosch Remote Portal licensing.
Starting with BVMS 11.0, the standard BVMS licensing scheme also applies to the DIVAR IP units.
Attached document describes how the upgrade process to BVMS 11.0 looks like and what kind of licenses are needed for a DIVAR IP unit!
Do you have any doubts, regarding BVMS licensing?
Attached whitepaper might serve as comprehensive source of knowledge for BVMS licensing topics, like:
BVMS product editions and license types
License activation process
Assurance PRO ordering process
Managing your licenses in Remote Portal
and much more!
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.
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 document will provide a basic explanation and simple examples of the interfacing (scripting, calling functions by external applications) functionality in Bosch Video Management System. The interfacing functionality is based on Bosch VMS SDKs. The Bosch VMS SDKs contain all interfaces, object types and methods that are needed for automation and integration to and of Bosch VMS.
The document can be found in the attachments section on the bottom of the page or at the right side of the page. Please look for the attachment icon.
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.
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.