The BriefCam Processing Server requires an NVIDIA GPU to process video. The exact model and amount of GPU cards required will depend on the requirements of the resolution of video to be processed along with the number of hours of video to process per day.
For a system with a large video processing requirement, multiple GPUs can be installed in each processing server, as well as the ability to utilize multiple processing servers simultaneously.
Each GPU installed in the BriefCam server must be assigned to process video in a specific processing mode, either for on-demand processing (REVIEW and RESEARCH modules) or for real-time processing (RESPOND module), a single GPU cannot process video both real-time and on-demand. If you have any questions regarding specific GPU compatibility or support, please reach out to BriefCam to confirm.
When a new video processing request is submitted, the VIDEO SYNOPSIS® technology Server (VSServer) will query each individual Processing Server (PS) to determine which server has spare bandwidth to process the requested video and will automatically assign the next available PS server to process the request.
NOTE: The capacity of each PS server to process video is based on a few different factors such as the resolution of the requested video to be processed along with the graphical processing unit (GPU) specifications, namely the total memory and TFLOPS (peak single precision FP32 performance).
Yes, BriefCam supports an on-premises architecture.
Yes, BriefCam supports a virtual architecture. The architecture is not affected by the deployment on a virtual environment as the components and requirements remain the same as long as the virtualized server has dedicated resources that match those of its physical equivalent. The virtualized server’s dedicated resources must not be shared between other instances or virtual machines as this can create a situation where certain services would not receive the required resources.
The BriefCam has a cloud demo available that is accessed through the Google Chrome browser by visiting https://demo.briefcam.com/. An account can be requested via your Regional Sales Director.
BriefCam currently uses NVIDIA GRID on the cloud demo platform and can confirm that it is supported and working.
Yes, BriefCam supports video processing from infrared, thermal, and black and white cameras. BriefCam Class categories (People, Two-Wheeled Vehicles, Other Vehicles, Illumination Changes, and Animals), as well as object behaviors (Speed, Size, Direction, and Dwell) will still be usable and accurate while object Attributes, such as Color, Appearance Similarity, and Face Recognition will have a lower level accuracy depending upon the video quality.
The BriefCam credentials are hashed using a one-way hashing function according to RFC 2898, https://www.ietf.org/rfc/rfc2898.txt, using a standard .NET framework implementation.
The video management system (VMS) and active directory (AD) credentials are stored using the standard symmetric Rijndael encryption implementation, or Advanced Encryption Standard (AES), provided by the .NET framework.
BriefCam is licensed according to the specific variant (e.g. Investigator (single user or multi-user), Insights, or Protect). For specific variants, expansion licenses can be purchased to increase the following aspects:
BriefCam is licensed according to the specific variant (e.g. Investigator (single user or multi-user), Insights, or Protect). For specific variants, expansion licenses can be purchased to increase the following aspects:
Definitions
Term | Description |
---|---|
GA Date | The date when a product is made generally available. |
Major Version | Up until v6.4, the major version is defined by the number to the left of the decimal point.
Beginning with v2023 M1, the major version is defined by the inclusion of the letter “M” in the product name. |
Policies
Policy | Description | Affected Versions |
---|---|---|
End of Sales | No new licenses of the product will be available for sale. | Any product that is not the current GA version or the immediate previous GA version. |
End of Support | No support will be provided and upgrades from this version will not be available. | Any product that is not the current major GA version or the immediate previous major GA version. |
Bug Fixes | To benefit from a bug fix, customers must upgrade to the latest version. | The current GA version. |
End of Life (EOL) | The date after which no support of any kind is available for the specific version.
No support will be provided, no bugs will be fixed, and no update packs will be released. |
Any product whose GA release date was more than 3 years ago. |
Note: Versions mentioned above include any update packs that were released for those versions.
Disclaimer
Only customers with BriefCam products that are currently covered by a valid Support and Maintenance contract are entitled to the benefits set forth by the End-of-Life Policy. BriefCam may continue offering Support services beyond the standard EOL date at its sole discretion and reserves the right to charge additional fees for continuing Support services on any EOL products. BriefCam reserves the right to reduce or amend Support services offerings available for renewal under this policy at any time in its sole discretion, with or without notice.
BriefCam is supported with a combined effort between First Level support, which is provided by the Reseller’s trained support personnel to supported end-users, and Second Level support, which is provided by BriefCam support personnel in the form of an online knowledge base and an online ticketing platform.
The BriefCam Open API (BOA) is a unified REST API allowing developers to introduce BriefCam functionality into their own applications. The APIs allow for:
BriefCam’s Video Integration API (API) is a generic HTTP RESTful request-based plug-in that enables third party integration with BriefCam solutions, including real-time (RSTP) video ingestion.
The BriefCam Respond Outbound API enables integration of BriefCam alerts into third party alerting infrastructure by issuing a generic RESTful call to the third-party alerting custom endpoint with detailed information on the alerting event, a downloadable thumbnail, and a downloadable video clip.
The BrieCam Hub Outbound API is for customers with multi-site deployments who want to send alerts from the Hub to a third-party system. The Hub Outbound API includes all the data sent in a regular Outbound API (as described in the RESPOND Alerts Outbound API section above) – with some additions: All objects of a multi-object alert (count-based and proximity alerts) are sent and not just a single object (as in the RESPOND Alerts Outbound API). For each object, the alert data (such as the event time) and the thumbnail URL are included. NOTE: This feature requires a dedicated license.
BriefCam’s System Events API can send a message to a webhook provided by the user whenever a new event is registered in the BriefCam Administrator Console. This message includes the severity of the system event, the type of system event, the time that the system event occurred, and a description of the system event including camera name, camera ID, camera external ID, and error.
The BriefCam GUI is accessed through the Google Chrome, Mozilla Firefox or Microsoft Edge web browser by navigating to the server’s hostname or IP address (NOTE: Only the Google Chrome, Mozilla Firefox and Microsoft edge web browsers are supported at this time).
The BriefCam GUI can also be embedded within the Genetec Security Center and Milestone XProtect Smart Client video management system (VMS) software platform.
For more information on how to convert an standalone location to a Site on the Hub, please Contact Us.
BriefCam can create either a Basic Custom Dashboard, which includes up to 6 widgets for video sources only, or can create an Advanced Custom Dashboard, which includes up to 10 widgets for video sources and up to one external source. This service is purchased under a separate product SKU.
You can also use the Chart Suggestions and Insight Advisor to auto-generate and prioritize relevant charts and analytics.
BriefCam’s RESPOND module helps you receive Real-Time Alerts, Smart Alerts and People Counting alerts for critical events to increase safety and security with proactive responses.
Depending on which Video Management System (VMS) BriefCam is integrating into, a Respond alert can be immediately sent to the Alarm Manager within the VMS. Otherwise, you will be notified within the BriefCam GUI natively or the Respond Alerts Outbound API can be utilized to send alerts into third party alerting infrastructure.
BriefCam® invented and owns the worldwide patents for the VIDEO SYNOPSIS tool, an innovative approach that allows organizations to review hours of video in minutes and sometimes seconds. The VIDEO SYNOPSIS innovation superimposes objects on a stationary background, simultaneously displaying events that have occurred at different times, with the ability to link back to the original video.
While BriefCam, the company, does not store personal information on individuals either by itself or through its users, You, the user/customer, are collecting and/or processing personal information on individuals and storing such personal information at your site on one or more servers that include the BriefCam product, in accordance to your own settings and preferences. With that said, BriefCam’s software is a GDPR compliant product that includes tools that can help you in your compliance efforts with GDPR.
BriefCam provides online training and either remote and/or on-site training depending on the requirements. There are separate training modules for different audiences such as End Users, Installers, and System Administrators with a dedicated syllabus outlining the agenda for each module.
For more information regarding our Self-Paced or Instructor-Led training offerings, visit our User Training page or BriefCam’s Training Portal.