Security: Video

This article summarizes the BVMS design details, and serves as a guide to planning a BVMS system with Bosch cameras and storage. It focuses on BVMS combined with the VRM.

In this article you can find an overview of the tested and supported ONVIF cameras for BVMS.

Find out from this article how many cameras can be opened before the workstation is overloaded.

This articles describes how a BVMS system meets the requirements specified by IEC62676-1.

This attached 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.

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.

Find out from this article which Bosch encoders and decoders are compatible with BVMS

This article lists the scenarios in which technical support normally request dump file from a BVMS system.

This article 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. Moreover, this article describes how data, as processed during the Person Identification steps, can be classified. Finally, this article lists technical measures for data protection in the context of BVMS Person Identification.

Follow this article and download the Bosch Data Security Guidebooks attached

This article presents a consistent overview of the available BVMS articles on the Knowledge Base

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

This article explains how BVMS can be configured to connect to an LDAP (or Microsoft Active Directory) and use it as a base for user authentication.   BVMS is able to function in a (Windows) domain-controlled environment. The BVMS (and related) services run under the local system account. If another (domain-controlled) account is used to run these services, their permissions level should be the same as the local system account. It is recommended to add the Windows server to the domain first (as a domain member), before installing the BVMS software. The BVMS configuration is independent from the domain configuration, however, crucial changes in the domain could break the connection between the BVMS system and the LDAP authentication mechanism.

As video surveillance use grows in commercial, government and private use cases, the need for low-cost storage at scale is growing rapidly. BVMS, Bosch cameras, HPE hardware and SUSE Enterprise Storage provide a platform that is an ideal target for recording these streams.

BVMS Version 10.0: please note that the export mechanisms provided in the BVMS Configuration Client might not export the user-data. Check this article for more details!

When using the BVMS 9.0 installer on a Windows 10 "October 2018 update" machine (Build 1809) the SNMP services cannot be installed. Microsoft has changed the way the SNMP services are installed in Windows 10 "October 2018 update".

The BVMS Logbook database can be moved to another SQL Server. This article describes the steps that are necessary to migrate the database and describes how to confirm if the migration was successful.   BVMS is using Microsoft SQL Server Express to store its logbook. Based on the information provided by Microsoft (Compare SQL Server 2017 editions), SQL Server Express is limited to a 10GB database size. This could be insufficient for larger installations or installations that require a very long logbook retention time. Additionally, some organizations have a dedicated SQL server environment which should be utilized by all applications. The BVMS Logbook database can be moved to another SQL Server. This guide describes the steps that are necessary to migrate the database and describes how to confirm if the migration was successful.

This article describes how to configure a generic Microsoft Windows Server (2012 R2, 2016 or 2019) based server to serve as an iSCSI target for a Bosch video surveillance environment. SCSI (Small Computer System Interface) is most commonly used for the communication between computers and peripheral devices, such as hard drives. iSCSI enables devices to use SCSI over a network interface, therefore it makes a lot of sense for cameras to use iSCSI to record video. The camera is a small computer that needs a (network) connection to a "hard drive" to store video footage. In other systems this job is performed by the network video recorder (NVR).

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, Operator Client This article describes the initial information needed to start troubleshooting Operator Client Crash.   General Information   SMA validity How to retrieve the Hardware ID for BVMS and check the Software Maintenance Agreement (SMA) status? BVMS stand alone or appliance Detailed problem description   Symptom specific Information Problem Description   Note down the events that lead to crash Classify the crash reproducible crashes that trigger Windows Error Reporting crashes/ hangs/ freezes that are hard to reproduce, or take long before repeating   Logging Information   Dump file from the crash – refer to the following article How To create BVMS memory dump?  ConfigCollection from the machine where the crashing Operator Client is running.