This article describes how a Tattile camera can be connected to BVMS. 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
This article helps you to configure three aspects:
Match list configuration: the Tattile cameras can load a license plate match list from an FTP server. This article describes how you can enable an FTP server on the BVMS management server and use this as a source of the license plate match list.
Camera configuration: the Tattile camera itself requires specific settings before it can be added to BVMS.
BVMS Configuration: adding the Tattile camera to BVMS.
Check list configuration
Tattile cameras can have up to two check lists: A and B. This article helps you to configure check list A based on an FTP server running on the BVMS management server. The article is written based on Windows Server 2019 but can also be used Windows Server 2016 and Windows Server 2012 R2 as they look and feel similar.
1. Setting up an FTP server on the BVMS management server
Open the Internet Information Services Manager and add an FTP site to the local server.
You can give the FTP site an arbitrary name. The physical path needs to be accessible for a user with both read and write access on the file system as well as via the FTP site.
The FTP site should not be configured with SSL. The other settings can be adjusted based on the security-level of the installation. The security-level can be increased by applying, for example, IP filtering on the FTP site or in the Windows Firewall. This way, only configured cameras can access the FTP site.
The FTP site uses Basic authentication. This means that the FTP authentication uses the Windows authentication mechanisms in the background. Users (cameras) should only have read access on the FTP site. This prevents unauthorized modifications of the match list.
Use the computer manager to create a special user, for example, "ftp_user". This user should have read and write access on the FTP site folder and on the file system.
Create a file in the FTP site, for example, BlackList.txt using Notepad. Save the file using UTF8 encoding:
The contents of the file should match the following format: License plate; Country;Comments Please be aware that the Country identifier always consists of three letters. ### can be used as a wildcard and represents all countries
AB134HK;ITA; Test BS46588;###; Substitute car RS054HG;ITA; President’s car
Test if you can open the file using your favorite browser by entering the FTP address: ftp://ftpuser:firstname.lastname@example.org:21/ BlackList.txt. The username and password dialogue should not pop-up and you should have direct access to the content of the BlackList.txt file.
1.1. Synchronizing the check list in the camera with the FTP server
Plate Reader => Check List => Check List A You should enable check list A and configure the List Location as FTP. The FTP IP should match the location of the IP address from the BVMS management server. The File Name should match the name of the file storing the check list.
When you click Reload List, the List Loaded message should appear, including the number of license plates you have put on the list. Multiple cameras can point to the same check list. The checklist can also be generated by an external application that writes the file considering the required format.
1.2. Configure match list management from BVMS Operator Client
BVMS operators can manage the check list from the BVMS Operator Client. The user account the operator uses to login to Windows needs to have read and write access to the file that the FTP server hosts. You can achieve this by creating a new shared folder or by using the existing (hidden) shared folder. In the example below we use an existing (hidden) share folder: c$. Use the BVMS configuration client to open the resource manager.
Add a new resource, in our case, an external application.
The external application launched notepad.exe and points to the location of the check list using an argument.
Add the external application to the BVMS logical tree. This way operators can access it when they want to adjust the check list. Of course you can also put the external application in a folder.
2. Camera configuration
The Tattile camera can handle one admin connection simultaneously. As a result, you can add one camera to one BVMS system.
2.1. Add user
System => HTTP Users Change the default usernames and passwords or add an additional admin user that BVMS can use to login to the camera.
2.2. Configure communication protocol
System => Protocols => VRC BVMS communicates with the Tattile cameras using a secured protocol (VRCS). Configure the VRC server settings as indicated in the image below.
System => Network Configure the IP address from the BVMS management server in the Static hosts section. The Names must state BvmsLpr_Server (case sensitive).
If the Names does not match BvmsLpr_Server, in this dialog or in the events / action settings, the BVMS management server will not receive events from the Tattile camera.
2.3 Configure event and action settings
Plate Reader => Events Actions The Tattile camera has several events and actions. We use two events: Ocr Read and Match On List A. Configure the Template Message for these events by clicking on the image.
You should configure both events in the same way using the example below. The Server name/IP must state BvmsLpr_Server .
The Text Value should state:
Apply the changes. Plate Reader => Events Actions => Template Configuration (Config, bottom of the page) Additionally, you need to upload a template message. Click the Upload Page and load the file C:\ProgramFiles\Bosch\VMS\Appdata\LPR_Event_Template.txt on systems where the BVMS configuration client is installed.
2.4. Configure separator plate
Optionally you can configure a separator plate for specific countries. This determines how the detected license plates are written into the BVMS logbook. The camera user manual contains more information.
3. BVMS configuration
The BVMS configuration manual also describes how to add LPR devices to the BVMS configuration.
3.1. Add LPR camera
Add an LPR device by right clicking on the LPR devices node.
3.2. Add video (RTSP) camera
Some Tattile cameras also have a video output (Not possible for the basic family). You can add these cameras to the Video Streaming Gateway (VSG) configuration as an RSTP camera.
Use the rstp://x.x.x.x without authentication to load the video stream into BVMS.
3.3. Configure LPR events
You can use the Events and Alarms tab in the BVMS configuration client to configure the events and alarms. BVMS receives License plate detected (Ocr read) and License plate identified (Match On List A) from the camera.
We recommend to configure an alarm on the License plate identified event and store the License plate detected event in the BVMS logbook.
3.4. Allow only users in the "Admin" group to manage license plates
Some user groups might not be allowed to edit the check list. You can remove the rights by de-selecting the node in the logical tree on the User groups tab in the BVMS configuration client.
Alarms from the camera are processed using the normal BVMS alarm management. The check list can be easily edited by an operator by dragging and dropping the Manage License Plates application into an image pane, editing the file, and saving it (either by CTRL+S or by clicking File / Save).
4.1 Alarm Handling
If the License plate identified or License plated detected events are configured to trigger alarms, the following information will be displayed in an alarm:
The standard BVMS alarm information as timestamp, event type, alarm title, triggering device, etc.
The license plate itself
The country identified (DEU for Germany, etc.)
4.2 Investigation / Reporting
With the LPR events License plate identified and License plate detected stored in the BVMS logbook, it is possible to solve use cases as "When did a car enter and leave the premises". Open the logbook search in the Operator Client, define a search filter for the License Plate detected or License Plate identified event and run the search, if you want to get an overview of all detected plates. If you look for a specific number plate, you can additionally enter the license plate in the Text Data field.
The results are listed below and can be exported using the Save results button.
... View more
Security guards as well as operators are all member of this Slack channel and use the channel to collaborate. Guards can use their mobile phones to upload still images or movies to the channel for archiving by the security operators. Security operators are able to send snapshots (directly from BVMS), videos (exported), or chat messages to instruct security guards.
BVMS automatically posts events to the channel and, optionally, can post camera snapshots or short video clips of incidents into the channel automatically.
The attached document provides more insights into the system configuration.
... View more
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.
The BVMS Project Checklist is an Excel-based tool which makes it easier to design a BVMS system
🛈 Approval of this checklist is in best effort as it includes a storage estimation and a Encoder CPU load estimation. The actual scene variations in the project will ensure that the encoder CPU load and/or estimated storage may be different than presented in this checklist. As a result, Bosch Security Systems cannot take any responsibility for the storage estimations done in this checklist.
For BVMS Enterprise systems: each sub-systems requires it separated file.
Visualization Since version 13.0, the colors in the tool have changed.
Approvals change log
Keep track of the changes in a project. Collaborate with multiple persons on one checklist.
(Beta) generate license order quantities in one overview.
Overview of available storage devices. Adjust the RAID level and Global spares on this tab.
Bit Rate Guide (Manual)
Manual Bit Rate Guide: use when the project requires special encoding profiles.
Calculate the lifetime of an SD card.
Calculate local recording storage requirements.
The tool includes a basic validation. This is summarized in line 33 and 34. Line 33 displays the approval status overview. If the system is planned to be extended in the future, the number of channels is higher than 500, the number of workstations is higher than 20, the number of keyboard expansions is higher than 20, or the number of DVR expansions is higher than 20, the design needs to be checked by a Bosch BVMS (BU) expert.
Lines which contain mandatory fields are marked in column A: if, for example, line A37 is red, this line contains mandatory fields which are not filled in properly.
Approvals change log
The approvals change log can be (optionally) used to track the system over longer time. It is recommended to increase the document version with every system expansion.
The related approval number can be entered, next to the total number of cameras and workstations connected to the system.
The comment field is free text and can be used for additional comments related to the expansion of the system.
The tool uses two types of pools: cameras can be pooled in groups with similar properties.
The tool is limited to 5 camera groups.
For each group the type of camera can be selected, including an ONVIF camera.
Each group of cameras can be assigned to a storage pool.
All camera groups can be assigned to the same storage pool, which means they will record onto the same pool of storage devices.
System design steps The system design steps represent the steps indicated in the tool.
1. Camera/Encoder selection
In the first step cameras are selected and related to the camera groups.
Bosch cameras are natively available in the tool and the bandwidth is automatically calculated based on the profiles configured in BVMS.
Select the camera from the alphabetically sorted list. The camera platform (CPP) and the CTN is automatically filled in.
The available stream configurations (stream 1- stream 2) are available on the selected camera model.
The profile is set to balanced standard by default, but can be changed when necessary. The codec is set to h_264 by default, but can be changed when necessary.
🛈 Only CPP7 cameras or newer are able to encoder video in H.265. Please note that BVMS can decode H.265 video, but the recording profiles are based on H.264 encoding. If H.265 is selected the BVMS recording profiles need to be adjusted.
If an encoding codec is not supported by a camera, this is indicated.
2. Recording stream
The recording stream configuration is used to automatically calculate the bandwidth and storage consumed by the camera.
Select the recording stream based on the stream configuration and a supported framerate.
Based on the selected profile the target and maximum bandwidth are automatically calculated.
3. Live stream
The live stream is configuration is used to ensure the encoder is not overloaded. Select the live stream based on the stream configuration and a supported framerate.
4. Number of cameras
The number of cameras in a group can be configured. A group name can be set optionally.
5. Bandwidth calculation
Based on the selected profile, codec, recording stream and recording framerate the video bandwidth is automatically calculated and applied.
There is a manual override available that is also available for ONVIF cameras and Bosch cameras that are not natively available in the tool.
Audio recording can be enabled optionally.
6. VRM settings
The VRM parameters (sanity check and downtime) can be adjusted when needed.
The VRM downtime specifies how long cameras continue to record without being assigned new blocks by the VRM.
For example, 4 means the cameras will record approximately 4 days even if the VRM is down during those 4 days. In this case the VRM assigns sufficient recording blocks for 4 days to the cameras.
The amount of how many blocks are needed for a camera are determined on the bitrate that is specified for this camera. High value increases the required storage capacity of the system.
The sanity check determines how much data a camera has produced in the last days.
Depending on the traffic the number of blocks that a camera needs to cover the downtime period is determined.
6.1 Primary VRM Pool assignment
The group of cameras is assigned to a storage pool.
6.2 Primary VRM storage calculation The retention time is set and an quiet time / alarm time configuration can be set (hidden by default).
This can be used in cases in which, for example, during night time a "bit rate optimized" profile is selected while during day time a "balanced" is selected or motion recording is used.
In these cases a manual reduction (or increase) of bandwidth consumption can be configured: the amount of hours configured in this line represents the hours per day a camera is generating a reduced amount of data.
The video bandwidth represents the reduced (or increased) amount of data generated by the camera. This can be manually calculated using the Bit Rate Guide (Manual) tab.
The result of the camera settings on the required amount of storage is shown.
6.3 Secondary VRM pool assignment Optionally, the secondary (dual-recording) VRM can be configured for a number of cameras in the group. If this is needed, assign the cameras to a second storage pool.
6.4 (Hidden) Secondary VRM storage calculation The details of the secondary VRM storage calculation are hidden and can be visualized by expanding the "+".
6.5 VRM Pool configuration The VRM pool configuration shows how much storage is required for each pool.
The iSCSI failover option is set by default. This means that at least two storage devices are required and one of those devices needs to be able to handle the entire recording performance (bandwidth).
This minimum retention time might not be possible at this time.
7. Storage device selection
Based on information entered throughout the sheet a list of appropriate storage arrays are presented for the specific pool. The most efficient choice (based on the calculated overhead) is presented in the cell above the selection itself. If multiple arrays result in the same efficiency, this is visualized as well. The number of devices required in the specific configuration is available, but not taken into account in the overhead calculation.
Additionally the required VRM hardware needs to be selected.
8. Software licenses
Depending on the amount of cameras configured in the system a BVMS family base package is recommended.
The number of required camera/decoder expansions is automatically calculated based on the amount of cameras configured in the tool as well as the amount of decoders configured.
The number of workstations is automatically calculated based.
The number of dual recording expansions is automatically calculated based on the number of cameras assigned to a secondary VRM.
9. Servers and Workstations
Configure the amount and type of servers and workstations.
Configure the amount of transcoders, decoders and additional project information.
Sign the form with a date and name. This helps your colleagues to track back the information in case questions arise.
RAID level The RAID level of a device can be configured on the StorageDevices tab and affects all storage pools. Only the RAID levels available on the device can be selected.
Global spares The number of global spares can be configured on the StorageDevices tab and affects all storage pools. Only if a device offers a number of global spares, these can be selected.
... View more