About marioverhaeg

This guide 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.   Configuration   This guide helps you to configure three aspects: Match list configuration: the Tattile cameras can load a license plate match list from an FTP server. This guide 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 guide helps you to configure check list A based on an FTP server running on the BVMS management server. The guide 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.   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:password@x.x.x.x: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.     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.   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.   Tattile Vega II (Stark) - Camera configuration     1 Network configuration   System settings -> Network Ensure that the camera is part of the same network as your BVMS system.   System settings -> Services Enable the HTTPS port 443 on the device.   2 Add User Group/User   Either use the default user and change the default passwords or add an additional admin user that BVMS can use to login to the camera. User -> Groups Create a new user group that has the required permissions.   User -> Users Create a new user e.g. "admin"   3 Configure Hosts & Secrets   Hosts & Secrets -> Hosts Add the IP address from the BVMS management server as a new Host to the camera.   Hosts & Secrets -> Credentials Add new credentials in the camera. IMPORTANT: Credentials must match exactly to the given parameter here (case sensitive). Parameter Value Alias BVMS-Credentials User Camera With Password Enabled Password any character - BVMS server will replace it.     4 Configure messages, events and actions settings   The Tattile camera offers several messages, events and actions. To be able the receive events in BVMS corresponding entries have to be created. 4.1 Messages Output -> Messages For BVMS two message must be created which must exactly match the given pattern here (case sensitive). A) BVMS Plate Detection JSON { "plate_string": "${TRANSIT.PLATE_TEXT}", "event_type": "Ocr Read", "country_code": "${TRANSIT.PLATE_COUNTRY}", "event_date": "${VIRTUAL.DATE}", "event_time": "${VIRTUAL.TIME}", "serial_number": "${DEVICE.SERIAL_NUMBER}", "device_sn": "${DEVICE.SERIAL_NUMBER}" }   B) BVMS Plate Identification JSON { "plate_string": "${TRANSIT.PLATE_TEXT}", "event_type": "Match On List A", "country_code": "${TRANSIT.PLATE_COUNTRY}", "event_date": "${VIRTUAL.DATE}", "event_time": "${VIRTUAL.TIME}", "serial_number": "${DEVICE.SERIAL_NUMBER}", "device_sn": "${DEVICE.SERIAL_NUMBER}" }   After this you must have two messages configured.   4.2 Actions Output -> Actions The camera will only send the message if an action is specified. For BVMS you need two actions configured.   A) BVMS Send Detected Action must contain: Destination: Select configured host Authentication: This must be set to "Basic" and select the configured credentials "BVMS-Credentials" Body: Select the "BVMS Plate Detection JSON" message to be send.   B) BVMS Send Identified Action must contain: Destination: Select configured host Authentication: This must be set to "Basic" and select the configured credentials "BVMS-Credentials" Body: Select the "BVMS Plate Identification JSON" message to be send.   After this you must have two actions configured.   4.3 Events Output -> Events Under Events you must now specify the action that shall be executed for the event and under which conditions. For BVMS two Events need to be specified: A) BVMS Detected Select the "BVMS Send Detected" action as main action. Enable the filtering and select "All conditions". For Predicates add the "DATALOOKUPMATCHED@ <your list name> " with the value "is False". This will trigger an event for plates that are not in the list of known number plates. For DATALOCKUP configuration refer to chapter 6.   B) BVMS Identified Select the "BVMS Send Identified" action as main action. Enable the filtering and select "All conditions". For Predicates add the "DATALOOKUPMATCHED@ <your list name> " with the value "is True". This will trigger an event for plates that are part of the list of known number plates. For DATALOCKUP configuration refer to chapter 6.   5 Plate Recognition Anpr -> Plate recognition 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.     6 DataLookup Anpr -> Data Lookup To be able to identify number plates you have to specify a source file, this can either be local on the camera or remote on an FTP. The alias name of the given source will be used in the filtering of the Events described in chapter 4.     Tattile Vega - Camera configuration     This chapter explains how to configure previous generation of Tattile cameras to BVMS.   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.   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).     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: %EVENT_DESC%PLATE_STRING%PLATE_COUNTRY%SN%UTC_DATE%UTC_TIME 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:\Program Files\Bosch\VMS\Appdata\LPR_Event_Template.txt on systems where the BVMS configuration client is installed.   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.     ⚠️ Be aware that the time server must be registered in the camera so that the alarms are displayed with the correct time in the BVMS.   BVMS configuration   The BVMS configuration manual also describes how to add LPR devices to the BVMS configuration.   Add LPR camera   Add an LPR device by right clicking on the LPR devices node.   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.   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.   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.   Operation   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).   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.)   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 OperatorClient, 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.     Troubleshoot   1. BVMS Patch: BVMS111165 Patch Tattile Improvements 398299, 398300, 398396 This patch fixes issue 398299 by solving the authentication problem with regards to Tattile cameras. This patch fixes issue 398300 by mapping the events from different Tattile cameras correctly. This patch fixes issue 398396 by solving the problem of not showing events of Tattile cameras after changin the system. If using Tattile LPR camera, after upgrading to BVMS 12.0 the following steps are required, due to changes in the camera firmware: Upload new “LPR_Event_Template.txt” file to the camera Open “Edit” dialog for Tattile camera and press “Authenticate” to retrieve updated information from the camera Verify, that correct “Device Serial Number” is displayed on Properties tab.   2. Tattile Vega Basic LPR camera & BVMS: connection issue  Error message “Connection to xxx.xxx.xx.xx:xxxxx failed” A new Firmware version for fixing this issue is available. In order to update the firmware, please contact FAE_Traffic@tattile.com, specifying the Part Number of your camera and the version of the firmware currently uploaded on it. ... View more

Possible causes and solution(s)   Causes   This article describes the considerations that need to be taken into account when designing a video surveillance system that is suitable for person identification.  Terms and Abbreviations Product / Service Name  Description BVMS Person Identification powered by AnyVision BVMS Person Identification powered by AnyVision allows security system operators to identify persons of interest. Person Identification is a feature expansion of BVMS and supported by BVMS 10.0.  DL380 Gen10 AI Server (AI Server) The DL380 Gen 10 AI Server is specifically designed for AI use cases and comes with a LINUX OS and 2 x P4000 NVIDIA GPUs. The AI Server is capable of analyzing 8 video streams (1080p) simultaneously.  Person Identification Device (PID)  Corresponding hardware   Solution   Camera Placement   Field of View   Field of View (FOV) refers to the view of the world that is visible through a camera’s lens and encompasses everything that the camera’s lens sees. Each camera is positioned in a particular location and orientation in space. Objects outside a camera’s FOV are not recorded in a video or photograph. Proper and strategic camera positioning is crucial for capturing usable facial features in a video.   Capturing Facial Features - Mathematical Models   Facial features are represented in AnyVision as a mathematical model (also called a vector). AnyVision creates a mathematical model that represents each face detected in the FOV of a camera video feed. AnyVision also creates a mathematical model of all the faces that are enrolled into the AnyVision system (meaning that they were added as a Person of Interest (POI) to the AnyVision Watchlist). AnyVision can then recognize the appearance of POIs in a video by comparing the mathematical model of all enrolled faces with all the faces detected in the FOV. While AnyVision is quite powerful, there are some minimal requirements for video capture and camera location/positioning that are necessary in order to enable AnyVision’s artificial-intelligent, neural-network to generate a high-quality mathematical model of people’s facial features. While the AnyVision detector can locate faces that are quite small and that have been recorded in imperfect video capture conditions, the quality of the facial feature mathematical model is degraded when conditions are sub-optimal.   High-Quality Mathematical Models   The following sections describe various aspects for determining the optimal camera locations, angles, FOV and other factors in order to get the best results from your Face Recognition system. The best facial recognition results are achieved by providing the conditions to enable AnyVision to create the highest quality facial mathematical model. High-quality facial mathematical models enhance the precision with which AnyVision recognizes POIs. This results in optimal identification of POIs, optimal representation of faces for future use, less false positives (meaning incorrectly recognizing a person as a POI) and less false negatives (meaning not recognizing a POI in the camera’s FOV).   Video Face Size   How many pixels does BVMS person identification need?   Generally, high-quality mathematical models can be created from faces that are represented by at least 80 x 80 Pixels Per Face (PPF). Faces of this size enable AnyVision to not only detect that there is a face, but also to recognize a person as being a POI (meaning someone that was added to the Bosch Person Identification Subjectlist). More so, AnyVision provides recognition performance for face sizes of as low as 45 x 45 PPF. Example: The following is an example of how to calculate the minimum PPM for face recognition, which is 280 PPM (45 PPF). A typical face is 16 cm wide, which is 16% of a meter. If a camera is going to be set up in a corridor that is 4 m wide, then the number of pixels captured by the camera per meter is one quarter of the entire view width of the camera. For example, a typical Full High Definition (FHD) (2MP) camera resolution is 1080 (height) x 1920 (width) pixels. Therefore, 1920 pixels covers the entire width of the corridor, meaning 1920/4 = 480 pixels per meter. An average face is 16 cm wide, meaning 480 pixels x 16% = 76.8 Pixels Per Face (PPF).   Distance   Faces that are close to the camera appear larger than those that are far away. The following are some general rules of thumb regarding the number of PPMs and PPFs at varying distances from a typical Full High Definition (FHD) (2MP) camera.   Before installing the camera, assess the distance from the camera lens at which the video will capture the best frontal view of faces. Then calculate the camera resolution in order to estimate the FOV width in meters in the zone of interest (where faces are expected to be captured).   Adjusting camera focal length   When using PTZ or varifocal lenses, it is possible to change the focal length (Zoom) of the camera and to enable face recognition at further distances from the camera. This adjustment narrows the area in the FOV of the camera. The main objective is to change the distance between the camera and the capture point. The width of the capture line never changes as it is directly linked to the number of pixels. The diagram below demonstrates how the distance from the camera changes, but the width of the zone is fixed at 6m. In this area, we capture faces with sizes ranging from 45 x 45 (6.5m width for FHD camera) to 100 x 100 (3m width for FHD camera). The blue below shows a wider zoom and the red a narrower zoom.   The image below also demonstrates that the best facial recognition (the Interests Zone) is achieved closer to the camera (between 4 and 6 m away from the camera) when the zoom is wider, and further from the camera (starting from 8 m away) when the zoom is narrower.   Camera Height and Angle   AnyVision can detect faces with up to 45º angle of interest. However, reliable person identification is achievable when the angle of view is up to 30º. Optimal results are achieved when the camera is positioned at a 0º ‒ 20º angle from the angel of interest. It is possible to decrease the angle of interest by moving the camera further away and using optical zoom or lenses.   The image above demonstrates how it is also important to consider additional factors, such as when people’s faces are tilted downward (descending steps or checking mobile phones). It is necessary to compensate for these factors by directing the angle of the camera. Also, in order to ensure that people wearing caps/hats are captured with maximum performance, the camera should be placed at the shallowest angle while maintaining a clear line of sight to the capture line. The image shows the optimal angle of 30° looked down as a blue area, the yellow area is reasonable and the red area of 45% is more challenging.   Direction of Movement   Frontal view is best achieved in areas of movement   The highest quality mathematical models and recognition results are achieved when cameras are positioned to obtain a frontal view of people’s faces. This is true even though the system can detect and recognize up to a 90º side view (also called full profile, where the nose is facing sideways). In real-world environments, people tend to turn and talk to associates, to look at things in their surroundings and so on. Therefore, a best practice is to place cameras so that they are pointed at and focusing on areas where people are moving (walking and so on). While walking, people tend to look forward and may be facing in similar directions. Choke points (where people tend to congregate) may also be applicable. However, people who are not moving, tend to congregate in a cluster and face inwards, which may block recognition angles.   Moving towards the camera   When moving across a camera’s field of view, side profiles are most likely captured. This means there will likely be no increase of the face size (because they’re not coming closer to the camera) and details are blocked.     It is preferable to place cameras where people are moving towards the camera (their faces get larger as they come closer to the camera) rather than crossing the scene, as shown in the diagram below.   The angle of movement may affect video quality as artifacts may appear and faces may be slightly smeared, which lowers the quality of the facial mathematical model. This typically occurs when people are crossing the scene at high speeds, as shown in the picture above on the left. In the image below, Camera A is located in the corner of a corridor and covers both sides. Considering typical walking paths, Camera A’s faces will be detected in small size (wide angle lens) and in profile view, while Camera B’s placement will typically capture faces that are looking towards the camera direction in a higher PPF. Therefore, Camera B’s location will generate better results.   Psychological Aspects   An interest zone is the area at which the camera should be pointed and focused in order to ensure optimal capture of people’s face (frontal view, sharp image, and so on). This might be in a specific area of a room, building entrance, hallway or so on. When considering the camera’s field of view, various aspects of human psychology and behavior should be taken into account in order to ensure that people are not looking down at the time and place where the camera is recording them. This significantly increases the probability of achieving a high-quality mathematical model. Focal points attract attention: When a camera is located in an area that attracts attention, such as near a TV screen or an attractive advert, it is more likely that people will look up at it. Sounds also attract people’s attention. For example, people tend to look towards speakers during announcements, towards crowded loud areas when passing them, and at screens with sound. This may be considered either as a focal point or a distraction, depending on camera placement. New Areas: People typically look down when they enter a new area, such as after going through a gate, or when they need to take special care of the next step (such as when getting on/off an escalator). In this case, the person will look down to find his/her next step and will then look up and forward immediately afterwards. Avoiding Areas with Long Walks: In open areas where people walk a long distances, many will concentrate on their mobile devices with their face pointing downwards, which makes it more difficult to get a good facial view.   Camera Focus   In most of the video surveillance camera deployments, the camera is set to auto focus mode. In this case, the camera algorithm will look for sharp angles in the field of view and set the focus according to that location. In many cases, this focuses the camera on patterns on the ground (such as the carpet), a picture on the wall and so on. In many cases, the camera’s focus is not set up to identify a moving face. Because of the fact that the system seeks facial details, it is essential that the focus be set manually so that it will catch a face in the interest zone. It is best to set the maximum focal range, which because it increases the depth of the captured area.   Lens Selection   When planning the Interest Zone, its distance from the camera and the expected field of view width differs according to the various types of lenses that may be used, each which may have a different focal length. It is important to calculate the required focal length for the scene. Using a shorter focal length, widens the field of view, and the interest zone will be closer to the camera.   It is not recommended to use fisheye lenses, which tend to have shorter focal lengths and wider angles. Fisheye lenses also may create a distorted view that impacts the recorded facial quality.   Light   Increasing the exposure of light on faces increases the level of detail the system can acquire on the faces. Different cameras with different setups generate a different image quality, and each has its own fixed lux (lowlight camera performance) level, which cannot be adjusted. Therefore, it is best to select cameras that have the best possible lux.   It is best to use cameras that provide High Dynamic Range (HDR), Wide Dynamic Range (WDR), Image Sensor Sensitivity (ISO) as an essential compensating measure for challenging dim environments. The picture below shows strong backlight which results in a dark face, making it difficult to distinguish facial details.   Person identification works best in areas with even lighting levels. It is common to find down lighters that create stark shadows directly underneath where people may be standing. In these areas, selecting a capture line preceding the light, with a lower but a more even lighting level, will provide better performance. Mirrors and marble floors can also reflect light, which influences the face’s light level. It is recommended to avoid these settings.   Bit Rate   In many video management systems, a low bit rate is used in order to save video storage. If a low bit is used, when there is a movement in the picture, there may not be enough bit rate budget to encode the video and artifacts. The resulting pixelization will generate low video quality which degrades the face’s mathematical model quality. In order to ensure the best video quality when a person is in the picture, camera settings should be set to Variable Bit Rate (VBR) mode instead of Constant Bit Rate (CBR) mode. You should also consider using camera view areas to maximize the quality for any given bit rate (especially prevalent when padding could be used).   Face Enrollment   When a picture of a person of interest is added to the BVMS Person Identification subjectlist, AnyVision creates a mathematical model of that person’s facial features, which is used as a reference for recognizing that person. This process is called Face Enrollment. After a face has been enrolled, AnyVision can recognize that person when they are in the field of view  of any camera configured for Person Identification. A high quality reference picture is critical in order to generate the unique mathematical model that will influence the system results. The following are the requirements for optimal face enrollment: Picture in JPG format Updated picture Face is in focus Colored photos Balanced light and no shadow Picture is not stretched or distorted Face size is at least 100 x 100 pixels (picture size of 200 x 200 pixels when the face is at least half of the picture) Facing the camera The entire face is visible Neutral expression and both eyes open Without sunglasses Single face in the picture     It is most preferable to enroll the highest quality picture of a person of interest possible into the BVMS Person Identification subjectlist. When the reference picture is of lower quality, it is best to use it for manually searching for this person of interest.   ... View more

Question How does the BVMS - Operator collaboration with Slack work? Answer 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. Purpose 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.   Tabs Name Description Approvals change log Keep track of the changes in a project. Collaborate with multiple persons on one checklist. BVMS Checklist Actual tool. Ordering (Beta) generate license order quantities in one overview. StorageDevices 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. SD lifetime Calculate the lifetime of an SD card. Local recording Calculate local recording storage requirements.   Validation 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. Pools 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.   Step-by-step guide   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.   10. Miscellaneous   Configure the amount of transcoders, decoders and additional project information.   11. Signature   Sign the form with a date and name. This helps your colleagues to track back the information in case questions arise.   Optional changes   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

Question 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. Answer Sure! Maintained Article Description   Bosch Visio Design Icons Set of Visio Design icons for Bosch products. 28 May 2021 BVMS - Device Compatibility This document describes how BVMS works with older and newer Bosch cameras. 01 Mar 2021 BVMS - Single port connectivity  This document describes how the SSH functionality works. 01 Mar 2021 BVMS - Configure time services  This document provides a guideline on how to configure time services. 01 Mar 2021 BVMS - Merging VRM systems  This document describes how to merge two VRM systems into a single system. 02 Mar 2021 BVMS - Operator quick guide This document serves as a quick guide for operators. 02 Mar 2021 BVMS - Streamlining This document describes the streamlining concept. 27 Mar 2020 BVMS - Configuring a Microsoft iSCSI target This document explains how a Microsoft iSCSI target can be configured. 08 Aug 2022 BVMS - Deployment guide This document describes how a BVMS system can be deployed from the commandline. This is useful when using software deployment environments. 24 Jun 2021 Virtualization - A concept explained This document explains virtualization. 06 Aug 2023  BVMS - Upgrade guide Described the process on how to upgrade a system (checklist) 28 Aug 2023  BVMS - BIS Connectivity Describes how to connect BVMS to BIS 28 Aug 2023  BVMS - SDK help Provides instructions and examples on how to use the BVMS SDK 17 Aug 2018 BVMS - Keyboard shortkeys Shows a (normal computer) keyboard and the shortkeys that are available for BVMS. 05 Oct 2018 BVMS - OPC Server Describes the functionality available in the OPC server. 30 Apr 2019  BVMS - Mobile Video Service Describes the Mobile Video Service conceptually. 26 Aug 2019  BVMS - GDPR Description on how GDPR impacts BVMS. 23 Aug 2023  BVMS - Network design guide First version composed together with ASA. Feedback welcome! 15 Aug 2023  BVMS - System design guide Previously known as pre-sales guide. 08 Aug 2018  BVMS - Policy based recording Describes the “cameras and recordings” tab, in addition to the product manuals. 26 Apr 2023  BVMS - Blueprints Shows general BVMS system design blueprints. 13 Jan 2022  How to activate a BVMS v11 and above Lite demo license? Describes how customer can generate and activate their own demo license. Includes link to the LIF file. 31 Aug 2023 BVMS - AE Specification Architects and Engineering specification. 02 Oct 2018  BVMS - Automatic login of Operator Client Describes the parameters which allow the operator client to automatically login. 31 Aug 2023 BVMS - ONVIF Compatibility Lists the tested ONVIF devices. 29 Oct 2018  BVMS - Configuring LDAP Explains how BVMS can be connected to a LDAP environment. 10 Oct 2018  Safe software delivery Describes how customers can check the integrity of the installation zip files. 26 Oct 2022  BVMS - Client installation package Describes how a reduced client installation package can be used. 27 Sep 2022  BVMS - Decoding performance Shows the workstation performance 18 Jul 2019  BVMS - Migrating SQL Database Describes how to migrate the SQL database to a different server. 19 Aug 2020  BVMS - Securing the security systems Describes how to secure a BVMS system. 26 Aug 2019  BVMS - ANPR by ISS Describes how to configure ISS SecureOS and BVMS to combine ANPR functionality. 08 Feb 2019   BVMS - IEC62676-1 Describes how BVMS meets the requirements specified in IEC62676-1 29 Mar 2022  How-to: Transition from Project Assistant to (B)VMS Have you ever wondered how to best transition from the Project Assistant to (B)VMS? 18 Sept 2019  Software-defined video surveillance storage Describes the collaboration between HPE, SUSE and Bosch in modernizing video surveillance storage. 19 Sept 2019  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. 15 Aug 2023 Software Service and Support Describes how software moves through the product lifecycle. 06 Apr 2020 VRM eXport Wizard Describes how to use the VRM eXport wizard 30 Aug 2023 BVMS Project checklist The BVMS Project Checklist is an Excel-based tool which makes it easier to design a BVMS system. 26 Oct 2022 BVMS - Automated firewall configuration How does BVMS 10.0.1 (or newer) configure the firewall during the installation of the system? 30 Mart 2020  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? 30 Mart 2020  BVMS - Demonstrating (JPEG) cameras How can I use "virtual" cameras to demonstrate BVMS? 14 Jul 2020  How to create CA signed certificates for cameras and distribute  Configure video authenticity / integrity using CA signed certificates 19 Aug 2020  BVMS - Operator collaboration using Slack  Configure BVMS to integrate with Slack. 19 Aug 2020  BVMS - Person Identification Camera Placement Guide  Describes best-practices on camera placement when using person identification. 01 Dec 2020  BVMS - Tattile configuration  Describes how to configure Tattile (LPR) cameras and BVMS. ... View more