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.
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?
+++ Update: new [dns] tag available since PA1.4 +++
The template file can now be extended to using the tag [dns] for importing the DNS server address. This now also allows you to import URLs for the time server address, not only IP addresses.
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!
The attached technical notes give a short introduction to scripting alarm and counter tasks with Intelligent and Essential Video Analytics in FW 7.60. It also provides a broad selection of example scripts for explanation as well as including real world application examples.
IR filter sometimes fails to switch during day/night change
Affected camera models: NBN-932, NBN-832, NBN-733, NBN-63013-B, NBN-63023-B, NBN-65023-B, NBN-73013-BA, NBN-73023-BA, NBN-75023-BA
The inner tube of the LVF-5005C-S1803 lens can hit the IR filter frame and block the mechanism. This can happen in the maximized focus position of the lens. Result is the day/night switch can fail.
See above showing the inner tube of the lens, and in second picture the DINION IR filter frame
When installing the lens follow the following steps:
Open the Lens Wizard in the camera web interface and click the Center button to center the motorized back focus mechanism
Manually focus the lens by rotating the focus ring on the lens
Click Local Range Autofocus button in the Lens Wizard to fine tuning the focus settings.
If the steps above are followed the lens will not touch the IR filter.
In rare cases userc might have seen random reboots of the NetApp E2800 contorllers in a
simplex controller E2800 iSCSI storage system or
dual controller E2800 iSCSI storage system.
For example Order number:
DSA-N6C8X4-60AT, DSA-N6C8X8-60AT, DSA-N6C8XA-60AT, DSA-N6C8XC-60AT, DSA-N6C8XC-60AT as well as others like:
Commercial Type No. DSA-N2E8X4-12AT / Product No. F.01U.346.434, Commercial Type No. DSA-N2C8X4-12AT / Product No. F.01U.346.474, Commercial Type No. DSA-N2E8X8-12AT / Product No. F.01U.346.477, Commercial Type No. DSA-N2C8X8-12AT / Product No. F.01U.346.479, Commercial Type No. DSA-N2E8XC-12AT / Product No. F.01U.361.550, Commercial Type No. DSA-N2C8XC-12AT / Product No. F.01U.361.549,
Only for those useres recognizing such a E2800 iSCSI sysstem controller did show an unplanned reboot, can consult the NetApp Major Event Log (MEL). Customers reported this to BOSCH using a NetApp controller firmware 11.40, 11.50.2 or 11.50.R2. Based on that Bosch immediately contacted NetApp and requested support solutions from NetApp.
A basic step when dealing with technical questions for NetApp E2800 iSCSI storage systems is, to register the system with Serial No. by using the following registration form: https://resources-boschsecurity-cdn.azureedge.net/public/documents/Registration_DIP_600_Special_enUS_9007222920871435.docx NetApp and BOSCH want to inform, that we expect a new SANtricity firmware, provided by NetApp, which will contains a fix for the controller random reboot issue which were reported back to Bosch by some customers. The firmware version / SANtricitiy firmware for E2800 iSCSI models is delayed and planned for May 2020.
As this NetApp SANtricity firmware is desigend by NetApp for BOSCH use cases with 24/7 video recording + replay and even worst case situations during a running reconstruct, this Firmware is not yet available via NetApp NOW. NetApp agreed with BOSCH to cover all improvements and fixes in a global and public release around June/July 2020. BOSCH will inform here in this article about the comming release when available.
Potential for Data Inconsistency Issues on E-Series Storage Systems
With the controller firmware 11.50.1 and newer version an issues are fixed by NetApp, which enforce an immediate update of all E2800 iSCSI Storage Systems (their controllers). In July 2019 BOSCH announced the need to update from all former NetApp controller firmware 08.30.40.00 to newer versions. These newer versions should be certified and approved by BOSCH. In 2019 there was also an announcement by NetApp. All customers owning a NetApp storage system with valid warranty agreement and registered unit do have access to the public announcemnt of NetApp. This was announced by NetApp on their support websites (see https://mysupport.netapp.com/).
Bosch approval 31st of January 2018
Bosch approval 7th of May 2019
Bosch approval 20th of September 2019
outlook May 2020
NetApp Firmware 08.30.40.00 no longer allowed for usage
NetApp Firmware: 11.50.R1 no longer allowed for usage
NetApp Firmware: 11.50.2 no longer allowed for usage
NetApp works on a global release of a version newer than 11.60.1 - Please ensure that Bosch has certified any newer version before installing!
Please follow our BOSCH Knowledge Base and monitor for updates at this article for important news. The BOSCH submodel ID 356 ensures that the NetApp system is optimized for 24/7 video recording. See article here: ℹ️ https://community.boschsecurity.com/t5/Security-Video/TB-VS-date-2020-04-22-New-Firmware-11-50-3R1P3-is-available-for/ta-p/12778
All DSA E-Series (E2800 12-bay) and DSA E-Series (E2800 60-bay)
Example product variants:
DSA-N2E8X4-12AT Base unit 12x4TB High-performance and high-capacity storage system base unit with iSCSI disk arrays, single controller. DSA E2800, 12 x 4 TB HDD, Order number DSA-N2E8X4-12A
DSA-N2C8X4-12AT Dual controller unit 12x4TB High-performance and high-capacity storage system base unit with iSCSI disk arrays, dual controller. DSA E2800, 12 x 4 TB HDD, Order number DSA-N2C8X4-12AT
Note: There are other models with various HDD capacity (e.g. 8TB harddrives and larger) available For more details visit the BOSCH product website
Summary of issue
NetApp® has become aware of issues that could occur when an E-Series controller reboots at certain points during the evacuation of data from a drive that is performed as part of the sequence when a drive is being failed by the controller. As a result, there is a small possibility of data inconsistency on controllers running certain versions of E-Series SANtricity® OS controller software.
First announced in 06/2019: The issues are possible on E-Series controllers running 8.30, 8.40, 11.30, 11.40, and 11.50 versions of E-Series SANtricity OS controller software. The overall probability of these issues occurring is very low, but RAID 1 volumes have a higher probability of encountering the issues than other RAID levels or NetApp Dynamic Disk Pools. These issues do not affect traditional RAID volume groups that have no global hot spare drives because drive evacuation does not occur in this configuration. For information about fixes in these releases, view the readme notes for each revision release.
No workaround available. Controller Firmware update is needed. HDD Firmware update is not in relation to the descdribed issue here, but it is in general recommended to install the latest offered HDD firmware that is recommended by BOSCH and NetApp. The same applies for HDD firmware.
Solution: Update the NetApp Controller Firmware
Upgrade E-Series SANtricity OS controller software to the latest applicable revision release for each platform as soon as possible. Please reach out to your local BOSCH technical team and BOSCH BT-SC/ETP-MKP team to ensure that the relevant NetApp Firmware has been approved to be usable for 24/7 video recording and replay use case. Even the global NetApp Firmware can be installed on BOSCH submodel ID 356
Where to get the Controller Firmware
All customers with a full NetApp NOW support account and valid warranty on their system can download the controller firmware by using the own NetApp user account. The verison offered at the NetApp NOW platform should be certified and allowed by BOSCH for video use cases. See also: https://community.boschsecurity.com/t5/Security-Video/TB-VS-date-2020-04-22-New-Firmware-11-50-3R1P3-is-available-for/ta-p/12778
In caase the download option is not offered to one of our customers, we kindly ask to make sure that the unit is registered on the company and that the NetApp NOW account belongs to the company that has registered the unit. In all other cases, please recout out to the BOSCH Support organisation or local Bosch Technical Support desk.
A NetApp SANtricity firmware / controller firmware package for E2800 model can be downloaded from the NetApp NOW website. Revisions can be found at https://mysupport.netapp.com/NOW/cgi-bin/software/ See also: https://mysupport.netapp.com/products/web/ECMLP2854621.html
Additional information is available at NetApp and accessible after user registration. First go to https://mysupport.netapp.com/ to register. Product Release Notes from NetApp: https://mysupport.netapp.com/ecm/ecm_download_file/ECMLP2842060
NetApp Support Bulletin, please view the following URL: https://kb.netapp.com/app/answers/answer_view/a_id/1086731 (As the URL can change any time by NetApp, search for the KB id 1086731)
Steps to update
The E-Series SANtricity ® OS package includes data for simplex controller and duplex controller systems and the firmware file itself.
NVSRAM File for for duplex.
NVSRAM file for simplex
and the controller firmware
Download the latest SANtricity OS software files from the NetApp Support Site to your management client.
From SANtricity System Manager, select Support > Upgrade Center .
In the area labeled “SANtricity OS Software upgrade,” click NetApp Support .
On the NetApp Support Site, click the Downloads tab, and then select Software .
Locate E-Series/EF-Series SANtricity OS (Controller Firmware) .
For the platform, select E2800 , and click Go!
Select the version of SANtricity OS (Controller Firmware) you want to install, and click View & Download .
Follow the online instructions to complete the file download.
Attention: Risk of data loss or risk of damage to the storage array — Do not make changes to the storage array while the upgrade is occurring. Maintain power to the storage array.
Not all Cisco PoE+ switches are able to power up the UHO-PoE-10 or VSP-UHO-PoE-10 outdoor housing (F.01U.300.502, F.01U.332.052).
Bosch has introduced the UHO-PoE-10 in 2014 following the IEEE802.3-2009 standards
Cisco claims that the Bosch UHO-PoE-10 at startup for a short moment (around 1 micro second) exceeds maximum current peek allowed by the updated IEEE 802.3-2015 standard, allowing the PSE (Power Source Equipment) to withdraw the power as a protective measure.
Due to analogue overcurrent protector components in the Cisco switch it can happen that tolerances may cause variety in behavior over different Cisco switches, even when the same model and setups are used.
Currently this behavior is only known on some Cisco models. (reports were seen on C2960X, C3560CX and recently C9200.)
Applying the Bosch NPD-6001B midspan is a way that can be recommended in case the switch is found to be strict in its port protection to be able to power the housing.
Though beyond the scope of this article, there are also other reasons for a switch to not provide power. Some trouble shooting pointers to consider:
Ensure that CDP protocol is disabled
Ensure that the camera is configured for extra power request (Network->Advanced->LLDP power config->Additional Power, claim: 25,5W) due to application in UHO (also see installation guide)
Ensure that switch has sufficient power allocatable, check the power budget
Check if enable or disable LLDP for the port or complete switch could improve the situation
Check if static 30W power allocation could work, instead of the auto power negotiation
Check if Cisco 2-event allocation could improve the situation
Check if increasing Ethernet cable length increase could improve the situation
Check with Switch supplier if an I max situation exists and could be resolved. Some example PoE-Imax-Errors-on-Catalyst-3850 series.html and General Catalyst 3850 PoE port configuration info
What's new in version 1.4.0?
## Bosch Remote Portal ## Easily register cameras to the Bosch Remote Portal - the IoT hub to connect all Bosch BT products. For End-Customers and Installers it provides device management and value-added services as well as camera application management benefits.
## Faster configuration ## Cameras delivered with firmware version 7.10 and newer do not require a reboot anymore when changing the IP address or other network settings. This version of the Project Assistant takes this into account, speeding up the commissioning process even more.
## Specify DNS server address ## A DNS server address is now supported in the application. Now you can simply add a time server URL or connect your cameras, with static IP addresses, to the Bosch Remote Portal.
We always appreciate feedback, which you can share here our Knowledge Base as well as as via email (security.apps.com). Thank you and please stay safe in these challenging times.
Your Bosch Security App Team
PS: The Windows version will be available shortly in our Download Area and the Android respectively iOS versions will made available in the stores once the publishing process completed.
When a support case involves a Bosch DIVAR AN, DIVAR network or DIVAR hybrid for further technical analysis it usually requires obtaining the service log. This is a short how-to manual for retrieving this service log.
There are 2 options to retrieve the service log:
1) Using a USB stick and access to the local user interface.
1. Insert a USB memory stick in the device 2. Log on as administrator in the local unit (or ADMINISTRATOR for DIVAR AN model) 3. Access the Main menu by right-clicking the mouse for the Quick menu, and select ‘Main menu' 4. Select Export (or Backup for DIVAR AN model) 5. Select the USB device in field ‘Selected device’. 6. Press on front panel first ‘Shift’ and then within one second the button up.
7. Press OK to save the Service Log on USB stick. The Service log is saved in a protected ZIP file (e.g. ServiceLog-20200302T172254.zip).
2) access to the web interface
1. start browser and enter: http://<IPaddress>/cgi-bin/loadSvrfile/ServiceLog.zip 2. A dialog will popup “The server <ip-address> at Device_CGI requires a username and password”. Enter administrator (or ADMINISTRATOR for DIVAR AN) and password 3. Dialog for the File Download will open stating “Do you want to open or save this file”, propose to Select save and choose preferred filename and location for the Service Log 4. The service log is saved in a password protected zip file
With the VRM eXport Wizard 2.0 encrypted and unencrypted VRM recordings can be exported (VRM block export) from any video surveillance system based on Bosch Video Recording Manager (VRM) and exported recordings can be converted to mp4-files. Therefore, the VRM eXport Wizard 2.0 offers the following two options, compare also Figure 1:
Export VRM recordings of cameras
Convert already exported data to mp4-file
Export VRM recordings
To export recordings, no matter if encrypted or un-encrypted recordings, from a video surveillance system based on VRM, the user first needs to select and connect to the Bosch VRM system that contains the source video data the user wants to export. To optimize the data traffic, the user can further select the number of maximum sources exported in parallel and set the maximum bit rate used per source, see Figure 2.
Note: To avoid any performance loss of the VRM system it is not recommended to run the VRM eXport Wizard on the same hardware as the VRM itself or any other system critical server (e. g. VRM server, BVMS MS, etc.).
In the next step (Figure 3) the user selects the cameras and the time period that shall be included in the export. Additionally, the user can change the name of the export file and add a comment.
Once the user is done with the camera selection, the export destination has to be selected in the "Select Type and Destination" window, see Figure 4. Here the user can choose between CIFS export, iSCSI export and export to a file system.
Note: The tape export some users might know from previous older versions is no longer supported.
Once the destination is selected, the export process can be started. The VRM export Wizard informs about the current status of the export process and tells the user when the export is completed, compare Figure 5. The exported blocks can now be found on the before choosen destination platform.
Please note for mass exports, if the overall export time is longer than the respective retention time for a camera not all video data might be exported before being overwritten / deleted.
As already mentioned above, this export procedure works for unencrypted as well as encrypted VRM recordings (encrypted and unencrypted VRM blocks).
Unfortunately, for playback of the exported material we have to differentiate between encrypted and unencrypted exported recordings. For playback of unencrypted video data exported by the VRM eXport Wizard BVMS is the best choice, as the user can then also take advantage of the meta data like IVA information. For now, this is not possible for encrypted recordings, because the re-import of encrypted VRM block exports is not yet supported. Instead, the user has to take advantage of the new mp4 conversion functionality of the VRM eXport Wizard. Of course, the conversion also works for unencrypted recordings. Both cases are explained in the following.
Convert already exported data to mp4
To convert VRM block exports to mp4 format the user has to choose the option "Convert already exported data to mp4-file", see Figure 6.
Max file size per MP4 file is 500 MiB
How to convert unencrypted recordings to mp4?
In the "Select exported data for conversion" screen the user can choose the source, in this case unencrypted recording blocks, and the output directory, where the mp4 files shall be saved to, Figure 7. To choose the exported VRM blocks, which shall be converted to mp4 format, the user has to navigate to the corresponding camera folder and has to select the related BIN.file. This is illustrated in Figure 8. For unencrypted VRM blocks no further information is needed and conversion can be started by pressing the next button in the "Select exported data for conversion" screen.
Similar to the export procedure the VRM eXport Wizard also shows the status of the conversion process. Once it is successfully finished, the screen will look like in Figure 9.
How to convert encrypted recordings to mp4?
The conversion of encrypted VRM blocks starts in the same way as the "unencrypted recordings" case above. However, in the "Select exported data for conversion" screen the user needs to add a valid redundancy key for encryption. Therefore, the checkbox "Source is encrypted" needs to be checked and the redundancy key (a .pfx file) needs to be selected and the password needs to be entered, as demonstrated in Figure 10 and Figure 11.
The VRM eXport wizard is a tool that allows you to export video directly from the VRM. You can find the VRM eXport wizard setup file in the bonus directory of the BVMS zip file. Exports made with the VRM eXport Wizard 1.20.0010 can be open in BVMS (Viewer) 9.0 or newer. The attached document describes how to use the VRM eXport Wizard. BVMS 10 comes with the VRM eXport Wizard 1.20.0016.
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.
What is the decoding performance of BVMS? How many cameras can I open on the screen before the systems is overloaded (and frames are being dropped)?
The BVMS client performance overview is attached to this article and shows, based on several workstation configurations and a specific BVMS version, how many cameras can be opened before the workstation is overloaded.
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.
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.
How can I use "virtual" cameras to demonstrate BVMS?
Demonstrating a video surveillance system typically requires a couple of cameras. However, when you only have a couple of cameras, the screen can look boring and empty. Did you know you can use the video streaming gateway to pull in any online JPEG picture as a camera into BVMS? This makes your demonstration more interesting! Additionally, you can set-up your own webserver and host customer JPEG images yourself. You can find a warehouse example below, fully based on JPEG based static images.
The attached document describes how to configure JPEG 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?
The embedded BVMS script engine makes this easy to achieve. The attached document explains how to achieve this and included an example script.