CCTV –Operating and management Software


Mirror: G K Bhat

As continued part of our discussion initiated last week about video management system we will be discussing this week the system server, SDK , Alarm management system ect , These are all  most important and essential features required in the video management system of a surveillance CCTV system.
gk m
VMS should be installed on Standard Servers and storage technologies.
VMS should support installation and ability to run on virtualized windows servers
The VMS system should be compatible to single and multiple processor servers.  The server processor & hardware should be optimized in all cases.
The Video Management System should support Latest Microsoft Windows operating system
The Surveillance System Server should support the use of separate networks, VLANs or switches for connecting the cameras to the Recording Servers to provide physical network separation from the clients and facilitate the use of static IP addresses for the devices.
The Surveillance System Server should support H.264, MPEG-4 (both ASP and SP), and MJPEG compression formats for the video stream from all devices including analogue cameras connected to encoders, DVRs, and IP cameras connected to the system.
 Multi-stream Support – The Surveillance System Server should support H.264 / MPEG-4 / MJPEG bandwidth optimized multi-streaming.
The VMS should support interoperability with IP camera standards including, at a minimum, the Open Network Video Interface Forum (ONVIF).
The VMS recording servers should support interface to cameras with universal serial bus (USB) communications.
The Surveillance System Server should support full two-way audio between the Video client viewers and remote cameras/devices.
Multi-stream should support two independent streams from a camera to the recording server with different resolutions, encodings and frame rates, dependent on camera capabilities.
Multi-live streaming should define multiple streams for live viewing with different properties.
System should ensure that once recorded, video cannot be altered.
The system should have different recording modes i.e. continuous, manual programmed, event activated etc. on date, time camera wise. It should be possible to configure each mode using user friendly tools. It should be possible to search and replay the recorded video date, time, camera, event wise.
Each recording server should be mapped to a specific port and this port must be forwarded through the firewall to the recording server’s internal IP address.
The system should allow the management server to be installed on multiple servers within a cluster of servers ensuring that another server in the cluster automatically takes over in case the first server fails
The Video Management System should support high availability of recording servers. A failover option should provide standby support for recording servers with automatic synchronization to ensure maximum uptime and minimum risk of lost data. Minimum required is N: 1 OR N: N Redundancy.
In case of Network Failover, the video should be able to locally store on the Camera, once the network is established the stored video should be able to synchronize with the central storage system.
The VMS should provide a documented Software Development Kit (SDK) to allow integration with other application software.
The SDK should provide a comprehensive library of reusable software components that can be used by other software applications to integrate a wide range of IP video devices under a single object API.
The SDK should consists of high level “objects” that can be manipulated by a client software application through a set of well-defined COM interfaces, abstracting various underlying control and streaming protocols with a common API.
The SDK should be access password protected and should be accessible from all .Net programming languages.
The Video Management System should support full two-way audio between clients and remote devices. Two-way audio integration should support the following features and functions.
The Audio should be broadcasted through loud speakers from control room to the cameras connected to external speakers. Operator should be able to select particular camera speaker to enable the public addressing.
The system should maintain a single alarm stack for the complete system, which should include events received from other system, or events detected by video analytics, network loss, video loss etc. It should be possible to assign priorities to alarms. System should maintain audit trail for alarms and actions taken by users in response to alarm should be recorded and made available for audit.
The VMS should support a central alarm management and monitoring function, providing an alarm / event queue where all incoming events are on display. The alarm queue should provide, but not limited to, the following information:
Alarm date and time
Alarm status
Current alarm condition
Detector/input name/address
Alarm location
Message priority
Operator who is working on the alarm/event when it was acknowledged.
All incoming alarms at the SMS GUI workstation should consist of the following
Comprehensive alarm message.
Blinking icon representing new alarm.
Status of the alarm messages
Graphical map showing alarm location with flashing icon associated with the alarm.
Audible alarm / buzzer.
The alarm and event messages received should be classified into the following status:
  NEW – All the incoming messages that have not been accepted by any operator are marked NEW. These messages are displayed to all operators authorized to accept these messages.
Acknowledge – All messages which have been accepted by any operator are marked Acknowledge. The name of the operator who accepted the message should be displayed. Only this operator can delete the message or put it into the progress.
PROGRESS – Messages that have been placed in the workflow are marked PROGRESS. These messages are displayed to all operators authorized to accept these messages.
The alarm support should allow for continuous monitoring of the operational status and event-triggered alarms from servers, cameras and other devices.
The alarm support should provide a real-time overview of alarm status, or technical problems, while allowing for immediate visual verification and troubleshooting.
The Video Management System should incorporate intuitive map functions allowing for multi-layered map environment. The map functionality should allow for the interactive control of the complete surveillance system, at-a-glance overview of system integrity, and seamless drag-and-drop integration with video wall module option.
The activation of the VMD or Camera disconnected alarm should display the alarm location with animated camera’s icon shown in the location map, and the pre-defined alarm documents.
The supervisor is able to manually control by easily Dragging & Dropping the camera from the MAP to the desired Client station monitor views. The same camera view should be updated in the tile automatically at Client’s monitor.
Server software should allow the clients seamless operation of all cameras regardless of the actual connection to different recording servers. Software should allow the client applications to interact with all the camera/database servers simultaneously and allow simultaneous display of live video/recorded video regardless of the zone in which the client is connected.
It should be possible to define priority based camera control rights for each camera or a group of cameras. The users should be defined on a hierarchical basis with a minimum of three levels. A higher priority user can take control of camera being controlled by a lower priority’ user. In addition the user should have facility to request access of any camera and the existing situation permits the user should be to control the camera.
On screen controls should be provided to achieve remote operation i.e. PTZ operation of cameras.
It should be possible to view live video from cameras on the surveillance system from 1 to 64 per view.
To access views of cameras on any PC with a client viewer application installed.
Use multiple screens as well as floating windows for displaying different views simultaneously.
View images from several cameras in sequence in a single camera position in a view – a so called carousel.
View video from selected cameras in greater magnification and/or higher quality in a designated hotspot.
Receive and send video through the matrix functionality, control PTZ cameras.
Use digital zoom on live as well as recorded video.
To activate manually triggered events.
Get quick overview of sequences with detected motion.
Get quick overviews of alerts.
The operator should have the ability to use digital zoom where the zooming is performed in the image only on any number of cameras simultaneously. This functionality should be the default for fixed cameras. The use of digital zoom should have no effect on recording, or other users.
It is a requirement that all user actions on the system Operator Station to be recorded in a log file along with the Security System or Control System’s actions.
Interventions such as manual recording and configuration setting changes.
Cameras viewed, Video replayed, Video exported, Cameras pan/tilt/zoomed and pre-set switching.
It should be possible for operators to manually set video wall to pre-sets and set a video wall monitor to show specific cameras.
The supervisor client should be provided with dynamic control of the layout of the video wall, and content should easily be added by dragging and dropping cameras into view positions on the video wall.
This log must also contain a history of the status of the system components. It should list the status of all cameras, servers and other system components including when they were disabled or foiled. This log should be maintained for a minimum period of 30 days.
It should be possible to playback multiple no. of camerason the surveillance system, with a selection of advanced navigation tools, including an intuitive timeline browser.
The Client should support search of recorded video for motion event in user-specified areas of a camera image
The VMS should allow the operator to capture / Export video from the workstation. The recording should be captured in a standard format, such as AVI, so as to allow playback using Windows Media Player. The recording should include audio for video sources if audio recording is used.
The Video Management System software should provide fast evidence export by exporting in video to various formats, including video from multiple cameras in encrypted native database format with an included viewer.
With this  the specification and general function of the VMS has to come to a concluding stage . We will discuss about the switch specifications and other network components in our next week topic.

G K Bhat
[email protected] 


Please enter your comment!
Please enter your name here