OnSSI’s Ocularis 5 has been specifically optimized for the banking industry with a ground-breaking integrated solution for improving safety and security.
OnSSI’s Ocularis 5 has been specifically optimized for the banking industry with a ground-breaking integrated solution for improving safety and security. Ocularis 5 is compliant of multiple standards, including 256 bit end-to-end encryption of the transactions between client and server. With the integration between the video management system’s open platform and ConvergenceTP’s (C2P) Event Streaming Engine solution, transaction data is now correlated with video to make searching and tracking a smoother, faster and more efficient process.
“The correlation of data with video creates an extremely effective and intelligent security solution by offering a more complete picture of questionable activities,” said Ken LaMarca, VP of Sales and Marketing, OnSSI. “Ocularis’ open architecture makes this integration not only possible but a fully realized powerful tool that delivers comprehensive intelligence to the banking community.”
Transaction alerts can be set for high dollar amount withdrawals, high value deposits and ATM card swipes made without a transaction. Rule-defined alerts and real-time charting aid in alerting users of possible fraudulent actions. The integrated solution allows for a hypermedia search engine and graphing to assist in forensic search after an incident. In the event of a dispute or problem, the bank can enter any piece of information from the transaction, such as customer name, time or amount, and the system can quickly bring up the transaction including the data and video associated with it. Disputes over teller transactions can be verified and settled, and banks can quickly access transaction video and view details such as denominations and quantities of bills counted out to the customer.
All transaction data is stored with corresponding video. Users can search by transaction amount, name, account number and more. The data is returned in an interactive spreadsheet form enabling the user to play the video associated with each event listed. The system can be customized to automatically create a log of certain events, such as multiple transactions by an individual in a single day.
Keywords are taken from the metadata in real time and used to annotate alert messages. These messages are also automatically populated with user-defined information known as Standard Operating Procedures (SOP), including who to alert, how to contact them, etc. The keywords are also used to provide real-time analytics of events, enabling the user to track reoccurring events and display them as a camera view. Procedures are then used to engage the Ocularis Event Fusion technology. Ocularis allows the user to choose the next step with options including pushing video of the event to predefined client screens, locking/unlocking doors, blowing horns, turning PTZs, and sending email and/or SMS alerts.
Designed to protect sensitive banking information, the solution includes 256-bit end-to-end encryption from camera to server to Client. In addition, the Ocularis 5 video database is scrambled in order to avoid any possibility of tampering of evidence. This high level of security helps to ensure customer names, account numbers and images are shielded and kept safe. The video management system is based on a new recorder and features automatic load balancing for managing recordings across system servers, which yields a significant increase in system performance, all while reducing storage costs. Ocularis 5 also allows for multiple recorders to be combined under the same Base (including legacy Ocularis 4.X recorders) with centralized user and event management.
Ocularis 5 is offered in three models: Professional, designed for organizations operating multiple locations with small to mid-sized camera counts; Enterprise, built for a wide range of mid to large IT-centric organizations; and Ultimate, created for large organizations with extended command and control needs along with recording server failover.