Results (
Thai) 2:
[Copy]Copied!
GVD Video Management System (VMS) Specifications
1. VIDEO MANAGEMENT SYSTEM (VMS)
1.1 The Video Management System (VMS) shall be a highly scalable enterprise level Turnkey (hardware + software) solution.
1.2 The VMS will offer a complete video surveillance solution that will be scalable from one to thousands of cameras that can be added on a unit-by-unit basis.
1.3 The VMS system shall operate in a server / client configuration, allowing multiple users to share common server resources.
1.4 The VMS shall provide seamless management of video, having camera data recorded across the system (Edge Storage, NVR, Failover Server, Backup Server) but reachable through a single client application.
1.5 The VMS shall include the following applications:
1.5.1 Server Applications
a. Directory Server (DS) to store all related devices configurations for client requests
b. Failover Directory Server (DS)
c. Network Video Recorder (NVR)
d. NVR Failover Server
e. Backup (Archive) server
f. Virtual Matrix
g. Hardware and Software Watchdog
h. Integration Gateway for ACS / POS / LPR / IVS systems
1.5.2 Client Software Applications (CSA)
a. Control Workstation for operators to monitor and configure entire VMS system
b. Decoder for Video Wall
c. Archive Player
d. Mobile Client (Smart Phone / Tablet applications)
e. Browser Client
1.6 The VMS design shall provide the flexibility to allow owner to add or remove any components and/or controlled functions, in the event when operating requirements changes as system expands. The system should not affect other components which are not related to the changes and continue to function as a system.
1.7 All video streams supplied from cameras shall be digitally encoded in and recorded in real time simultaneously at bandwidth ranging from 8 Kbits/sec to 8 Mbits/sec, frame rates ranging from 1 fps to 30 fps and resolution ranging from ¼ CIF (176X144) to 20 Megapixel (10240 x 1920) resolutions.
1.8 Each camera’s bit rate, frame rate and resolution will be set independently from other cameras in the system, and altering these settings will not affect the recording and display settings of other cameras.
1.9 The VMS shall support the following minimum list of Network PTZ camera, Network Camera and Codec:
1.9.1 Panasonic
1.9.2 Pelco P
1.9.3 Bosch
1.9.4 Arecont Vision
1.9.5 Axis
1.9.6 Sony
1.10 The VMS shall support PTZ keyboard which can control all PTZ cameras which has been recognized by the VMS. The Keyboard should support Virtual Matrix switching capability.
1.11 The Hardware / Software Watchdog shall monitor operation of all VMS applications and restarts them if they are malfunctioning.
1.12 In case of malfunction of software components, the watchdog shall be responsible for restarting the application or in a last resort restart the PC.
1.13 The system shall be auto restart to its configured system set up and applications.
2 VMS APPLICATION SERVERS
2.1 The VMS Application Server shall consist turnkey solution of the Directory, the Failover Directory, the Backup / Archive Server, the Virtual Matrix, the Integration Gateway.
2.2 The Applications mentioned in this section shall offer the capability to be installed on several hardware servers to enable distributed archiving in a LAN or WAN environment. There shall not be a limit to the number of PCs which can be networked together to form a distributed archive server system.
2.3 Directory Server
2.3.1 The Directory Server shall maintain a catalogue of settings for all NVR, Failover server, Backup Server, Virtual matrix in the system.
2.3.2 The Directory Server, in the case that a camera signal is lost, shall detect the video loss and have the capability to alert the systems administrator.
2.3.3 The Directory Server shall receive all incoming events (motion detection and triggered digital input and relay output) in the system and take appropriate actions based on user-defined event/action relationships.
2.3.4 The Directory shall create log files of events and user activities.
2.3.5 The Directory shall authenticate users and give access to the VMS based on predefined user access rights.
2.4 Failover Directory Server
2.4.1 The Failover Directory Server shall synchronize its configuration database with the Directory Server.
2.4.2 The Failover Directory Server shall take over as the VMS’s Directory in the event which the primary directory Server fails.
2.5 Virtual Matrix (VMX)
2.5.1 The VMX Manager shall be capable of registering up to 20 VMX Decoder or up to 40 monitors for video wall display. It shall be installed in the Control Workstation and managed together with other applications.
2.5.2 The system shall be capable of handling the video resolution from CIF, D1, up to 20 Megapixel. When monitoring cameras with Full HD resolution, each VMX Decoder must display up to sixteen (16) cameras.
2.5.3 The system shall support simultaneous operation on VMX Manager and VMX Decoder for video viewing, instant playing back and PTZ control on any monitor connected to the video wall.
2.5.4 The VMX Manager / Decoder shall support the following the following features:
2.5.4.1 ‘Sequence’ function which has one or more customized static patterns constantly rotate at preset intervals for touring.
2.5.4.2 ‘Dynamic Pattern’ function which has one or multiple dynamic viewers set to rotate between a set of cameras while the other viewers remain static.
2.5.4.3 ‘Hotspot Pattern’ function which uses a main viewer that constantly rotate at regular intervals between other viewers in the same pattern.
2.5.4.4 ‘ROI’ (Region Of Interest) function which allow user to select the interested area from main video and show the zoom-in video on another viewer on the same pattern.
2.5.4.5 ‘Tag Management’ function which user can customize the tags by inputting the text and selecting a background color. User can link the tags to one multiple cameras for quick searching by Grouping or Filtering.
2.5.5 The system shall support automatically network bandwidth control and management.
2.5.6 The VMX shall allow user to dispatch camera video to the remote display by drag-and-drop the camera icon from camera list to Display Control Panel.
2.5.7 The VMX shall allow user to dispatch ‘Static’, ‘Sequence’, ‘Dynamic’ and ‘Hotspot’ patterns from a sequence to the remote display by drag-and-drop the pattern from pattern list to the Display Control Panel.
2.5.8 The VMX shall allow user to change the layout of remote display by selecting a pattern layout in the Display Control Panel.
2.5.9 The VMX shall be able to receive and show the alarm notice from Directory Server and allow user to dispatch the alarm recording video to the remote display for playback.
2.5.10 The VMX shall support Keyboard Mode which allow user to control up to 3000 cameras.
2.5.11 The VMX shall be capable of displaying live images and playing back images in any monitor window of a selected monitoring layout. Playback of any camera in a particular window in a multi-camera display configuration shall not stop live viewing of cameras in the other windows.
2.6 Failover Server for NVR
2.6.1 The Failover server for NVR should be a N+M turnkey solution which provides guarding of all NVR in the network.
2.6.2 In the event of NVR malfunctioning in the network, the Failover Server will take over the recording of the NVR within 45 seconds.
2.6.3 Multiple Failover Server should be managed in a single VMS Client workstation for ease of monitoring.
2.6.4 During take over, the client connected to the system should not have any changes in the way of search for camera or recorded data.
2.7 Backup (Archive) server
2.7.1 The Backup server will support maximum 128 cameras backup at 2Mbps bitrate.
2.7.2 User may select any cameras in different NVR for backup in the same Backup Server.
2.7.3 The Backup server shall support ‘Mirror’, ‘Event’ and ‘Schedule’ backup functions.
2.7.4 The Backup server shall have the selection of receiving video stream from Edge Devices or NVR in the system.
2.7.5 In the event which the primary video source for the Backup server is not available, the Backup server shall automatically switch to pre-configured alternative video source available in the system.
2.8 Integration Gateway
2.8.1 The Integration Gateway shall be fully integrated with third party systems such as Access Control System, License Plate Recognition, Point of Sales and Intelligent Video Analytics.
2.8.2 In any given event of the third party system, the Integration Gateway shall trigger the VMS for alarm notification, video pop-up. Actions and relationship of third party system and the VMS can be configured through the interface of Integration Gateway.
2.8.3 The Integration Gateway shall support TCP/IP and Modbus protocol.
3 NETWORK VIDEO RECORDERS (NVR)
3.1 The NVR shall be based on modular architecture and provide for future upgrading and additional storage devices as and when required.
3.2 The NVR shall support up to 128 cameras at 2 Mbps per camera in a single server. It shall also support various resolutions of camera ranging from CIF to 20 Megapixel.
3.3 The NVR shall support 3TB hard disks and minimum 48TB storage capacity. The storage within the NVR shall be using Raid 5 / 6 storage array for storage redundancy. The NVR shall support DAS for connecting to external storage to support up to 192TB Storage Capacity.
3.4 The system shall be open platform to support IP camera and devices from any brand. It shall also support ONVIF / RTSP standards.
3.5 The NVR shall have the capability to simultaneously live display, record and playback video. None of the video operations shall interfere with each other.
3.5.1 The system shall support 16 simultaneous playback video at 4CIF resolution.
3.5.2 The system shall support 16 live display camera views at 4CIF resolution.
3.6 The NVR playback search time for any camera recorded data until it displays the video
Being translated, please wait..