1.01.doc
Post on 21-Oct-2014
1.009 views
DESCRIPTION
TRANSCRIPT
DVMRe Pro
DIGITAL VIDEO MANAGEMENT SOFTWARE
SymSecure Enterprise 4
April 2008
Table of Contents
PART 1 DIGITAL VIDEO MANAGEMENT SOFTWARE (DVMS)3
1.01 REF _Ref196040710 \h \* MERGEFORMAT General3
1.02 IP Video4
1.03 Hardware Independence4PART 2 SERVER SOFTWARE MODULES (SSM)9
2.01 General9
2.02 Directory9
2.03 Standby Directory13
2.04 Gateway13
2.05 Federation Server13
2.06 Archiver14
2.07 Standby Archiver16
2.08 Redundant Archiver17
2.09 Auxiliary Archiver17
2.10 Restore Archiver17
2.11 Media Gateway17
2.12 Metadata Engine17
2.13 Standby Metadata Engine18
2.14 Virtual Matrix18
2.15 Standby Virtual Matrix18
2.16 Watchdog19
2.17 Server Administrator19
PART 3 CLIENT SOFTWARE APPLICATIONS (CSA)20
3.01 General20
3.02 Configuration Tool24
3.03 Live Viewer28
3.04 Archive Player31
3.05 Web Live Viewer32
3.06 Web Archive Player34
3.07 Macro Editor35
3.08 Report Viewer35
3.09 Software Development Kit (SDK)36SymSecure Enterprise 4
Part 1: Digital Video Management Software (DVMS)
General
The DVMS shall be a highly scalable enterprise level software solution.
The DVMS will offer a complete video surveillance solution that will be scalable from one to tens of thousands of cameras that can be added on a unit-by-unit basis.
The DVMS shall include the following applications:
Server Software Modules (SSM):
Directory (System Server)
Standby Directory
Gateway
Federation Server
Archiver
Standby Archiver
Redundant Archiver
Auxiliary Archiver
Restore Archiver
Media Gateway
Metadata Engine
Standby Metadata Engine
Virtual Matrix
Standby Virtual Matrix
Watchdog
Server Administrator
Client Software Applications (CSA):
Configuration Tool
Live Viewer
Archive Player
Web Live Viewer
Web Archive Player
Macro Editor
Report Viewer
Software Development Kit (SDK)
IP Video
All video streams supplied from analog cameras or IP cameras shall be digitally encoded in MPEG-4 or MJPEG compression formats and recorded simultaneously in real time.
The DVMS shall interface with analog-to-digital video encoders and IP cameras, hereafter referred to as digital video servers (DVS). The DVMS shall support DVS from GE Security.
The DVMS shall support the following IP video servers:
GE video servers
DVMRe
GE CamPlus IP
GE Megapixel
Legend IP
SymDec1
SymDec4
SymDec16
SymNet
SymSafe Pro 4/8/16
Each cameras 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.
Hardware Independence
The DVMS shall require no proprietary recording hardware, no hardware multiplexer or time-division technology for video or audio recording and monitoring.The DVMS shall be based on the use of nonproprietary PC storage hardware that shall not limit the storage capacity and shall allow for gradual upgrades of recording capacity.
The DVMS shall be able to use a GE Security CCTV keyboard with a GE Security video server to operate the entire set of analog cameras throughout the system, including cameras of various manufacturers brands, including their PTZ functionalities.The DVMS shall support the following list of PTZ camera protocols with respect to the configuration outlined in Paragraph C above:
360 Vision
Astel TC20
Axsys
Bosch Bilinx
Bosch TC8650 & TC700 Series
Canon VC-C1
Canon VC-C4
CNB
Cohu (CCR communication protocol revision 1.0 including iDOME series)
Creco Black Box V2.4 Protocol
Dynacolor
Elbex
Elbex Ex2000-8000
Ernitec
GE Kalatel ASCII
GE Legend
Guardall Dome
GYYR Vortex (V6 Series, VM Series and VDN Series Cameras)
Hytec (HYTEC DTR 100 Z ADF NTSC)
Image Labs
IR516 Thermal Camera
ISAP
ISAP/QuickSet
ISAP/QuickSet QPT130
ISS
Javelin J0308 (ACU, ACULV, ACUX)
JVC TK-676 PTZ
JVC JCCP-F
JVC JCPB-S
LMW
Merit Li-Lin Fastdome Protocol including PIH-7625 Series, PIH-7000 and PIH-7600 Series
Panasonic Conventional
Panasonic BB-HCM381
Pelco D
Pelco P
Philips
Philips Fixed Speed
QuickSet
QuickSet QPT130
QuickSet/ISAP
Radian
RVision Dome
Samsung SPD 1600
Samsung SPD SCC-641/643
Samsung SPD SCC-C6405P
Sanyo Z protocol
Sensormatic RS422
Sensormatic SpeedDome Ultra IV and AD DeltaDome
Sony BRC-300
Sony Visca
ThermoVision
ThermoVision/QuickSet
Ultrak
V1LC
VCL VCLTP protocol
Vicon V15UVS
Vicon V1x00R-PVP
Videoalarm VLPT400 EIA485/EIA 422 communication protocolVideotec
The DVMS shall support the following list of PTZ keyboard protocols:
GE ImpactNet
The DVMS shall support the following CCTV matrix switches:
GE Kalatel ASCII
The DVMS shall support the following access control systems and access control system communication protocols:GE Picture Perfect
The DVMS shall allow for a GE Security CCTV keyboard to be attachable directly to an encoder/decoder via its serial port and shall be able to control a Live Viewer application with the use of a PC.The DVMS shall allow users to activate all live viewing controls using a standard PC keyboard. All standard camera switching and automation functions of a CCTV keyboard shall be available using a PC keyboard.
The DVMS shall have long-term storage capabilities on any Windows supported tape backup.
The DVMS shall digitally sign recorded video using 248-bit RSA public/private key cryptography. The user shall have the capability of changing the encryption key. The DVMS shall encrypt the VSIP control channel with SSL.
The SSM shall transmit all command and control messages using TCP/IP protocol and use cryptographic keys based on SSL V.3.0 protocol when communicating with digital video servers (DVS) to prevent eavesdropping, tampering or message forgery. The DVMS shall allow for the configuration of a time zone for each camera connected to a DVS and for each SSM. For playback review, users shall have the ability to search for video based on the following options:
Local time of camera
Local time of the SSM
Local time of users workstation
GMT Time
Other time zone
The DVMS shall consist of server software modules (SSM) and client software applications (CSA).
Both the SSM and CSA shall run on Windows XP Professional with Service Pack 2 or Windows 2003 Server operating systems.It shall be possible to install both the SSM and CSA on a single workstation or on separate workstations.
SSM and CSA shall be able to operate on separate networks.
The configuration of the hardware running the CSA shall be:
Low: Intel Pentium D 2.8 GHz, 2 MB Cache, 800 MHz FSB, Microsoft Windows XP Pro SP2 32-bit/64-bit, or Microsoft Windows Vista, Business or Ultimate 32-bit/64-bit, 1.0 GB of RAM, 80 GB of storage or more, 256 MB ATI Radeon X600 dual-head, or equivalent, 1024 x 768 or higher screen resolution, 10/100 Ethernet Network Interface Card, 16x DVD+/-RW drive1, Sound cardMedium: Intel Core2 Duo 2.4 GHz or higher, 4 MB Cache, 1066 MHz FSB, Microsoft Windows XP Pro SP2 32-bit/64-bit, or Microsoft Windows Vista, Business or Ultimate 32-bit/64-bit, 1.0 GB of RAM, 160 GB of storage or more, 128 MB x16 nVidia Quadro FX550 dual-head, or better, 1280 x 1024 or higher screen resolution, 10/100/1000 Ethernet Network Interface Card, 16x DVD+/-RW drive1, Sound cardHigh: Intel Core2 Extreme 2.93 GHz, 4 MB Cache, 1066 MHz FSB, Microsoft Windows XP Pro SP2 32-bit/64-bit, or Microsoft Windows Vista, Business or Ultimate 32-bit/64-bit, 2.0 GB of RAM, 250 GB of storage or more, 256 MB x16 nVidia Quadro FX3450 dual-head, or better, 1600 x 1200 or higher screen resolution, 10/100/1000 Ethernet Network Interface Card, 16x DVD+/-RW drive1, Sound cardThe recommended configuration of PCs running the SSM: Low: Intel Xeon 3.0 GHz, 2 MB Cache, 800 MHz FSB, Microsoft Windows XP Pro SP2 32-bit/64-bit, Windows Server 2003 SP1/SP2, 32-bit/64-bit, or Windows Server 2003 R2 32-bit/64-bit, 2 GB of RAM, 80 GB hard drive for OS, Additional hard drive(s) for video storage, Standard SVGA video card, 800 x 600 or higher screen resolution, 10/100 Ethernet Network Interface Card, DVD ROM drive
Medium: Dual Core Intel Xeon 5150, 2.66 GHz, 4 MB Cache, 1333 MHz FSB, Microsoft Windows Server 2003 SP1/SP2 32-bit/64-bit, or Windows Server, 2003 R2 32-bit/64-bit, 2 GB of RAM, 80 GB hard drive for OS, Additional hard drive(s) for video storage, Standard SVGA video card, 800 x 600 or higher screen resolution, 10/100/1000 Ethernet Network Interface Card, DVD ROM driveHigh: 2x Dual Core Intel Xeon 5160, 3.00 GHz, 4 MB Cache, 1333 MHz FSB, Microsoft Windows Server 2003 SP1/SP2 32-bit/64-bit, or Windows Server, 2003 R2 32-bit/64-bit, 4 GB of RAM, 80 GB hard drive for OS, Additional hard drive(s) for video storage, Standard SVGA video card, 800 x 600 or higher screen resolution, 10/100/1000 Ethernet Network Interface Card, DVD ROM drive
The hard drives must be purchased from one of the following manufacturers:
IBM
Maxtor
Quantum
Western Digital
Seagate
Audio and Video storage configuration for the SSM shall either be:
Internal or external IDE organized or not in a RAID configuration;
Internal or external SCSI/Fibre Channel organized or not in a RAID configuration;
It shall be possible to include within the overall storage system disks located on external PCs on a LAN or WAN as well as;
Network Attached Servers (NAS) on a LAN or WAN as well as;
Storage Area Networks (SAN);
The SSM shall not limit the actual storage capacity configured per server.
DVMS shall be upgraded from one version to another without the user having to uninstall the previous version.
The recommended configuration of a PC running CSA to support simultaneous viewing of 16 cameras at an average bit rate of 600 kbps at CIF resolution shall be:
The PC shall be a Pentium 4 CPU operating with a minimum speed of 2.8 GHz with 1.0 GB of RAM, 10/100 Base T LAN card, and 80 GB or larger hard drive.
The PC shall have a XGA (1024 x 768) graphics card with a minimum of 256MB of memory and with hardware based YUV to RGB conversion support.
The CSA requires one of the following video cards for dual screen operation: nVidia Quadro FX550 or better
Part 2: Server Software Modules (SSM)
General
The SSM shall consist of the Directory, the Directory, the Standby Directory, the Gateway, the Federation Server, the Archiver, the Standby Archiver, the Auxiliary Archiver, the Redundant Archiver, the Restore Archiver, the Media Gateway, the Metadata Engine, the Standby Metadata Engine, the Virtual Matrix, the Standby Virtual Matrix, the Watchdog and the Server Administrator.
The SSM shall offer the capability to be installed on several PCs to enable distributed archiving in a LAN or WAN environment. The SSM shall not limit the number of PCs that can be networked together to form a distributed archive server system.
Directory
The Directory shall maintain a catalogue of settings (configuration database) for all CSA, SSM and DVS in the system.
The Directory shall enable CSA to dynamically create connections between different DVS in the entire network and this on individual streams (audio, video, serial ports and digital I/Os).The Directory shall give the capacity to view all DVS in a network even if the DVS are assigned to different archive servers.
The Directory, in the case that a camera signal loss, shall detect the video loss and have the capability to alert the system administrator. The Directory shall receive all incoming events, e.g. alarm events, application events, camera events, etc. (see bullet "J." below), in the system and take appropriate actions based on user-defined event/action relationships.
The Directory shall create an audit trail of events and user activities. The Directory shall perform dynamic bandwidth management.
The Directory shall authenticate users and give access to the DVMS based on predefined user access rights.
The Directory shall provide the option to have an integrated user management system throughout the organization by synchronizing the DVMS user base with a Microsoft Active Directory already in place. The Directory shall receive and log all of the following events:
Alarm Events:
Trigger
Activate/Reactivate
Forward
Snooze
Ack (default)
Ack (alternate)
Ack (custom)
Application Events:
Application lost
Application connected Archiver Events:
Archiving queue full
Archiving stopped
Backup started
Backup success
Backup failed
Cannot write on a specified location
Cannot write to any drive
Database lost
Database recovered
Disk(s) full
Disk load is over 80%
Invalid custom encryption values
Not enough disk space for logging
Protected video threshold exceeded Camera Events:
Camera not archiving
File deleted
Live bookmark added
Playback bookmark added
Motion on
Motion off
Network connection lost
Receiving RTP packets from multiple sources
Recording started (by alarm)
Recording stopped (by alarm)
Recording started (by schedule)
Recording stopped (by schedule)
Recording started (by programmed action)
Recording stopped (by programmed action)
Recording started (through motion detection)
Recording stopped (through motion detection)
Recording started (by user)
Recording stopped (by user)
RTP packets lost
Signal lost
Signal recovered
Digital Input Events:
Digital input contact opening
Digital input contact closing Directory Events:
Connection lost with the alarm database
Connection recovered with the alarm database
Directory Failover Coordinators not synchronized
Not enough disk space for loggingDVS Events:
Invalid configuration in DVS
Signal lost
Signal recovered
Unit discovered
Unit lost
Macro Events:
Macro error
Macro started
Macro stopped
Plug-in Events:
Plug-in error
Plug-in started
Plug-in stopped
Database out of disk space PTZ Events:
PTZ activated
PTZ locked
PTZ stopped
User events:
User logonUser logoff
The Directory shall have the capability to execute any of the following actions in response to any of the events listed above: Archiving Actions:
Start recording
Stop recording
Add a bookmark
Override with manual recording quality
Override with event recording quality
Recording quality as standard configuration
Start applying video protection
Stop applying video protection Monitoring Actions:
Block a camera
Unblock a camera
View a camera on an analog monitor
View a camera in the Live Viewer
View a camera in a free window of the Live Viewer
View a map in the Live Viewer
Display a URL address in a Live Viewer PTZ Actions:
Go to preset
Run a pattern
Set PTZ auxiliary
Clear PTZ auxiliary
Go home
User Notification Actions:
Send a message
Send an alert sound
Send an email
Trigger Alarm
Output Relay Actions:
Set the output relay to the opposite of its default state
Set the output relay to its default state
Set the output relay to on
Set the output relay to off
Set the output relay to pulse (pulse is configurable) Device Control Actions:
Send a string on the serial port
Reboot a DVS
Macro Actions
Execute a macro
Shall support Advanced Alarm Management, which shall have the ability:
To assign alarms and procedures to specific users or user groups.
To escalate alarms to other users after a configurable time that an alarm has not been acknowledged.
To allow a user to queue alarms, and view alarm history.
To display on a workstation or an analog monitor an alarm composed of live video streams, playback video streams, or a set of still images of the alarm. A combination of these alarm display options can be configured for each alarm.
To configure multiple cameras to display upon an alarm.
To display alarms in block, salvo or simple mode.
To allow the administrator to assign a priority to each type of alarm, ranging from 1-30.
To display an alarm pane with past alarms and associated data.
Standby Directory
The Standby Directory shall act as a replacement SSM on hot standby, ready to take over as the acting Directory in case the primary Directory fails. The failover will occur in less than 1 minute. No action from the user will be required.The DVMS shall support multiple Directories on standby, lined up to take over as the acting Directory in a cascading fashion.
The Standby Directory shall keep its configuration database synchronized with the primary Directory. The Standby Directory shall be able to act as a global standby or a local standby. The global Standby Directory is one that can take over the entire load of the primary Directory.
The local Standby Directory is only intended to take over part of the original load, typically, applications within the same LAN. In this scenario, when the primary Directory fails, all local Directories will start simultaneously, each taking part of the whole load. The DVMS shall accept a configuration featuring both global and local Standby Directories.
Gateway
The Gateway shall act as a doorway to the Directory for all CSA and SSM on the system, regardless where they are connecting from, on the same LAN, a remote LAN or via Internet. Multiple Gateways shall be used on large DVMS installations to increase the service availability and to provide manually controlled or automatic load balancing.
The Gateways shall be able to take each others load if one of them should become unavailable. The transfer should be transparent to the CSA and SSM. Federation Server
The Federation Server shall be the bridge that joins multiple independent DVMS systems together into one big system, called the Federation. The DVMS hosting the Federation Server is called the Federation host. The Federation Server shall allow users on the Federation host to view cameras belonging to other members of the Federation (independent DVMS systems) simultaneously, as though they belong to the same DVMS system.
The Federation Server shall be able to join DVMS systems running SymSecure v4.1 versions together.
The Federation Server shall allow the viewing of live as well as archived videos from the federated DVMS systems. The Federation Server shall allow the Federation host to receive the events issued by DVS owned by the Federation members.Archiver
The Archiver shall use an event and timestamp database for advanced search of audio/video archives. This database shall be a Microsoft SQL Express 2005, Microsoft SQL 2005 Enterprise or Microsoft SQL 2000 Enterprise server with Service Pack 3. The Archiver shall protect archived audio/video files and the system database against network access and non-administrative user access.
The Archiver shall digitally sign recorded video using 248-bit RSA public/private key cryptography. The user shall have the capability of changing the encryption key. The Archiver shall offer a plug and play type hardware discovery service with the following functionalities:
Automatically discover DVS units as they are attached to the network.
Discover DVS units on different network segments including the Internet and across routers with or without network address translation (NAT) capabilities.
The Archiver shall provide a pre-alarm and post-alarm recording option that can be set between one second and 5 minutes on a per camera basis. Shall provide the functionality of storing of video and audio streams based on triggering events such as:
Digital motion detection
Digital input activation
Macros
Through SDK application recording
The Archiver shall perform video motion detection on each individual camera based on a grid of 1320 motion detection blocks. However, unit motion detection is only available with the CamPlus IP model. All of the video motion detection settings are configurable on schedule. A global sensitivity threshold is available to reduce motion detection sensitivity where video signal is noisy or a lot of false hits are incurred. Video motion detection itself can be set into four different modes:
Full Screen: All 1320 blocks on screen are activated, a general threshold for the overall motion in the entire image can be set and when reached it can trigger recording and a motion event or a custom event.
Full Screen Unit: This is the same as the Full Screen but the motion detection takes place in the DVS.
Detection Zone: Six overlapping zones can be defined in the 1320 blocks on screen, each of these zones has its own threshold and when reached each one of them can trigger recording and a motion event or a custom event. Each zone triggering its own event allows for the configuration of directional motion detection events and other complex motion detection logic.
Detection Zone Unit: This is the same as the Detection Zone but the motion detection takes place in the DVS and only one zone is supported.
Disabled: No motion detection is made on this camera.
The Archiver shall allow for multiple recording schedules to be assigned to a single camera, each schedule shall be created with the following parameters: Recording mode:
Continuous
On Motion/Manual
Manual
Disabled
Recurrence pattern:
Once on specific days
Specific days on a yearly basis
Specific days on a monthly basis
Specific days on a weekly basis
Daily
Time coverage:
All day
Specific time range(s)
Daytime or nighttime based on the times of sunrise and sunset, automatically calculated from the time of year and a geographical location. Provision shall be given to offset the calculated sunrise or sunset time by plus or minus 3 hours. The Archiver shall allow each camera (video source) to be encoded multiple times in the same or different video formats (MPEG-4, or MJPEG), limited only by the capabilities of each DVS. Whenever multiple video streams are available from the same camera, users shall be free to use any one of them based on their assigned usage. The standard video stream usage are:
Live
Recording
Remote
Low resolution
High resolution
The Archiver shall allow the video quality to vary according to predefined schedules. Such schedules shall have the same configuration flexibility as the recording schedules mentioned earlier. The video quality shall be based on, but not limited to, the following parameters:
Maximum bit rate
Maximum frame rate
Image quality
Key frame interval
Etc.
The Archiver shall have the ability to dynamically boost the quality of the "recording stream" (see previous bullet) based on specific events:
When a user starts recording manually.
When recording is triggered by a macro, an alarm or detected motion.
The Archiver shall have the capacity to communicate with DVS using 128 bits SSL encryption.
For network topologies that restrict the DVS from sending multicast UDP streams, the Archiver shall redirect audio/video streams to active viewing clients on the network using multicast UDP. The Archiver shall empower the administrator with a full range of disk management options:The Archiver shall allow the administrator to choose the disks to use for archiving and to set a maximum quota for each.
The Archiver shall allow the admnistrator to spread the archiving of different cameras on different disk groups (groups of disks controlled by the same controller) so that archiving could be carried out in parallel on multiple disks.
The Archiver shall offer the following options to clean up old archives, on a camera by camera basis:
After a preset number of days
Deleting oldest archives first when disks run out of space
Stop archiving when disks are full
The Archiver shall allow important video sequences to be protected against normal disk cleanup routines. Users shall have the following options when protecting a video sequence:
Until a specified date
For a specified number of days
Indefinitely (until the protection is explicitly removed)
The Archiver shall allow the administrator to put a cap on the percentage of storage space occupied by protected video.
The Archiver shall keep a log and compile statistics on disk space usage.
The statistics shall be available by disk group or for the whole Archiver.
The statistics shall show the percentage of protected video over the total used disk space.
The Archiver shall have the capacity to schedule backups of the video archives, with associated database events, to either a tape drive or mapped network drive. The Archiver shall have the capacity to down-sample video streams for storage saving purposes. The down-sampling options available are the following:
For MPEG-4 streams the down-sampling options are: 1 frames/s, 2 sec/frame, 5 sec/frame, 10 sec/frame, 15 sec/frame, 30 sec/frame. 60 sec/frame 120 sec/frame.
For MJPEG streams the down-sampling options are: 15 frames/s, 10 frames/s, 5 frames/s, 2 frames/s, 1 frame/s, 2 sec/frame, 5 sec/frame, 10 sec/frame, 15 sec/frame, 30 sec/frame, 60 sec/frame 120 sec/frame.
Standby Archiver
The Standby Archiver shall act as a replacement SSM on hot standby, ready to take over the functions of the primary Archiver. The failover will occur in less than 1 minute. No action from the user will be required. Each DVS in the system shall have its own list of Standby Archivers, called the failover list. When a DVS's default Archiver fails, the next one in its failover list will assume the command and control of the DVS.
It shall be possible for a single Archiver to fail over multiple Standby Archivers simultaneously. It shall be possible for a single Archiver to act as the standby for multiple other Archivers.
Any Archiver in the system can be designated as another's standby. Redundant Archiver
The Standby Archiver shall have the ability to act as a Redundant Archiver.
The Redundant Archiver shall maintain an exact copy of everything recorded by the default Archiver, i.e. audio/video archives, events and bookmarks. Redundancy shall be configured on a camera-by-camera basis.
The Redundant Archiver shall use a multicast video stream from the DVS and shall not require an additional connection to any DVS. Auxiliary Archiver
The Auxiliary Archiver shall be used to produce redundant archives (video, events, bookmarks) for any camera in the system, on a case-by-case basis. The Auxiliary Archiver shall have the ability to archive any of the standard video streams for archiving. The standard video stream usage is: Live, Recording, Remote, Low Resolution, and High Resolution.
Restore Archiver
The Restore Archiver shall have the capability to restore a previously backed up video archive and its associated event database, and make all information in the backup set available to the original or other DVMS systems. The Restore Archiver shall provide the option to restore partially a backup set.
Media Gateway
The Media Gateway shall enable the streaming of video from the DVMS to an external media server, allowing for broadcasting of video in a standard format. The Media Gateway shall convert the video streams in a format supported by Windows Media Server. The Media Gateway shall allow for the configuration of resolution and text overlay.
Metadata Engine
The Metadata Engine shall extend the functionalities of the DVMS through the use of appropriate Metadata Engine plug-ins (ME plug-ins). The ME plug-ins shall give the DVMS the capability to perform the following:
Interface with GE Securitys Picture Perfect Integrated Security Management System
The ME plug-ins shall be mapped to DVMS cameras or other devices, and extract/collect pertinent information, called metadata, from the video feeds or the mapped devices.
The ME plug-ins shall create metadata events that can be queried and displayed on video archive timelines.
The metadata collected by ME plug-ins from cameras shall be kept in a database. The criteria used for metadata query shall be dependant on each type of plug-in.
The execution of the plug-ins shall be controlled by schedules. A schedule shall define a "recurrence pattern" and a "time coverage" (see Archiver, feature H for details).
The administrator shall be able to control the retention period of the metadata on a plug-in by plug-in basis.
The Metadata Engine shall digitally sign recorded metadata using 512-bit RSA public/private key cryptography. The user shall have the capability of changing the encryption key. The DVMS shall accept multiple instances of Metadata Engine.
Standby Metadata Engine
The Standby Metadata Engine shall act as a replacement SSM on hot standby, ready to take over the functions of the primary Metadata Engine. The failover will occur in less than 1 minute. No action from the user will be required. Each ME plug-in in the system shall have its own list of Standby Metadata Engines, called the failover list. When a plug-ins default Metadata Engine fails, the next one in its failover list will continue the execution of the plug-in.
It shall be possible for a single Metadata Engine to fail over multiple Standby Metadata Engines simultaneously. It shall be possible for a single Metadata Engine to act as the standby for multiple other Metadata Engines.
Any Metadata Engine in the system can be designated as another's standby. Virtual Matrix
The Virtual Matrix shall have the capability of creating camera sequences with the following functionality:
Each Sequence shall have a maximum of 500 cameras.
Each camera in the sequence shall have its own individual dwell time, from 1 to 999 seconds.
Each entry in a sequence shall have the capacity to trigger camera presets, patterns or auxiliaries.
Multiple users shall be able to view the same camera sequence simultaneously. Users shall be able to pause the sequence without affecting other viewers.
The Virtual Matrix shall have the capability to create and execute VBScript macros (or other scripting languages) on events or on schedules. A schedule shall define a "recurrence pattern" and a "time coverage" (see Archiver, feature 2.06H for details).
The Virtual Matrix shall have the capability to execute plug-ins (called VM plug-ins) based on predefined schedules. A schedule shall define a "recurrence pattern" and a "time coverage" (see Archiver, feature 2.06H for details). The Virtual Matrix shall have the capability to interface with video walls via a CCTV keyboard connected to a DVS decoder for live video ONLY.
The Virtual Matrix shall allow DVMS users to control cameras connected to a GE Security legacy CCTV matrix as though they were directly connected to DVSs. Standby Virtual Matrix
The Standby Virtual Matrix shall act as a replacement SSM on hot standby, ready to take over the functions of the primary Virtual Matrix. The failover will occur in less than 1 minute. No action from the user will be required. Each device in the system controlled by a Virtual Matrix (Macro, Camera Sequence, CCTV Matrix, CCTV Keyboard) shall have its own list of Standby Virtual Matrices, called the failover list. When a device's default Virtual Matrix fails, the next one in its failover list will continue the control of the device.
It shall be possible for a single Virtual Matrix to fail over multiple Standby Virtual Matrices simultaneously. It shall be possible for a single Virtual Matrix to act as the standby for multiple other Virtual Matrices.
Any Virtual Matrix in the system can be designated as another's standby.Watchdog
The Watchdog shall monitor operation of all SSM services and restarts them if they are malfunctioning. As a last resort, in the case where the Watchdog is unable to restart the DVMS, it will restart the PC. Server Administrator
The Server Administrator shall provide the capability to configure the running environment of the SSM modules such as:
Database Servers
Storage Disks
Storage File Size
SSL certificates
Encryption Keys
DVS Discovery Options
Network Connection Modes
Network Connection Addresses and Ports
PART 3 CLIENT SOFTWARE APPLICATIONS (CSA)
General
CSA shall consist of a Configuration Tool application, a Live Viewer application, an Archive Player application, a Web Live Viewer application, a Web Archive Player application, a Macro Editor and an Event Report generating application.
The CSA shall perform the following functions simultaneously without interfering with any of the SSM operations (Recording, Alarms, etc.):
Live display of cameras on a workstation.
Live display of cameras on an analog monitor.
Live display of camera sequences on a workstation.
Live display of camera sequences on an analog monitor.
Control of PTZ cameras.
Playback of archived video on a workstation.
Retrieval of archived video.
Instant Replay of live video on a workstation.
Use of maps.
Use of procedures.
Configuration of system settings.
Execution of system macros.
Display and management of alarms on a workstation.
Display and management of alarms on an analog monitor.
Create and print snapshots of live video feeds.
Create and print snapshots of archived video feeds.
Block cameras from less privileged users.
Unblock cameras.
All applications shall support any form of IP network connectivity, including: LAN, WAN, VPN, Internet, and Wireless (WiFi and Cellular) technologies.
All applications shall support IP Multicast (UDP) and Unicast (TCP or UDPs) video streaming.
All applications shall automatically adapt to the network topology and use the best available method to receive streaming video.
All applications shall provide an authentication mechanism, which verifies the validity of the user. As such, the administrator (who has all rights and privileges) can define specific access-rights for each user in the system which include:
Connection time based on schedules:
Time when access to the system is allowed
Time when access to the system is denied Access rights to sites:
Sites are logical groupings of cameras and other system resources
Sites shall form hierarchies
Denying access to a site will deny access to all resources grouped under that site
Access or not to types of applications:
Live Viewer
Archive Player
Configuration Tool
Macro Editor
Web Live Viewer
Web Archive Player
Media Gateway
SDK
Priorities/Limitations:
Over camera viewing
Over PTZ control
Over archived video (limit to a certain number of days in the past)
Privileges (see next bullet)
The privileges that can be assigned to users shall include:
Configuration privileges:
Site configuration, creation and deletion
DVS configuration
Firmware upgrade
Creation and deletion
Camera configuration
Video quality settings
Recording settings
Motion detection settings
Analog monitor configuration
Audio configuration
Serial ports configuration
Input pin configuration
Output pin configurationPTZ configuration, creation and deletion
Hardware matrix configuration, creation and deletion
Schedules configuration, creation and deletion
Custom events and actions configuration, creation and deletion
Alarms configuration
Creation and deletion
Delete alarm instances
Macros configuration, creation and deletion
Camera sequence configuration, creation and deletion
CCTV Keyboard configuration, creation and deletion
Access control system configuration, creation and deletion
Monitor group configuration, creation and deletion
Camera group configuration, creation and deletion
Viewer layout configuration and deletion
Backup operator
Modify logical IDs
Plug-in configuration, creation and deletion
Archive Player privileges:
Export video files
Live Viewer privileges:
Change the displayed entities
Change layout selection
Change the tile pattern
Edit/Save the layout configuration
Change content in armed tiles
Arm/disarm tiles
Start/Stop guard tour
Edit guard tour dwell time
Acknowledge alarms
Forward alarms
Snooze alarms
Audio (listen/talk)
Access Digital Zoom
Do instant replayExecute Macros
Change macro hot keys
Local recording
PTZ controls:
Do basic operations
Change focus and iris settings
Use presets
Edit presets
Use patterns
Edit patterns
Use auxiliaries
Edit auxiliaries
Use menu
Lock PTZ
Override PTZ lock
Other privileges:
Record Manually
Add bookmarks
View cameras on an analog monitors
Block cameras
Send messages
Send sounds
Send emails
Send on serial ports
Execute custom actions
Save and print snapshots
Control camera sequences
Change own password
Protect video from deletion
Remove video protection
Change application options
Change client views
Common access rights and privileges shared by multiple users shall be defined as User Groups. Individual group members shall inherit the rights and privileges from their parent user groups. User group nesting shall be allowed.
All CSA applications (with the exception of the Web based clients) shall maintain a message box for pop-up system messages that are not acknowledged within 10 seconds. Users shall be allowed to read those messages and delete them at their own convenience.
Each workstation running the CSA (with the exception of the Web based clients) shall be able to use a GE Security CCTV keyboard (and GE Security Video Server) or PC Keyboard that can control the entire set of cameras throughout the system, even if the system consists of motorized analog cameras produced by different manufacturers.
All CSA applications shall allow for multiple instances to run simultaneously, by one or multiple users. The number of instances of the Live Viewer, Archive Player, Web Live Viewer and Web Archive Player applications shall only be limited by the number of available application licenses.
The CSA applications shall provide administrators with the ability to block video streams to lower level users. The CSA provide the ability to set 10 different user levels. Higher priority users can block live video feeds to lower priority users.
All CSA applications (not applicable to the Web based clients) shall support the automatic update capability. Once enabled, the administrator shall have the ability to schedule updates to be carried out automatically or following the user's acceptance.
Configuration Tool
The Configuration Tool application shall allow the administrator or users with appropriate privileges to change system configuration.
It shall have the following minimum capabilities:
Shall provide decentralized administration of the entire system from anywhere on the network.
Camera Layouts shall be available to all users in the DVMS and shall be stored in the Directory and applied to all Live Viewer applications connected to that Directory.
Shall provide the ability to change video quality, bandwidth and frame rate parameters on a per camera (stream) basis for both live and recorded video.
Shall have the capability to define access and privileges by user group as well as by individual users
Shall provide the ability to configure brightness, contrast and hue settings for each camera on the same DVS.
Shall provide the capability to enable audio recording on DVS units that support audio
Shall provide the ability to change audio parameters, serial port and I/O configuration of individual DVS units.
Shall provide the capability to rename all DVS units based on system topology and add descriptive information to each DVS.
Shall provide the capability to regroup specific cameras together and restrict or enable access rights to this group on a per user basis.
Shall provide the ability to set recording schedules and modes for each individual camera. The recording mode can be:
Continuous
On motion and Manual
Manual only
Disabled
Shall provide a wizard to create complex macros that can activate on event. The wizard shall be available from a tab in the configuration Client Application and will allow the user to choose from a variety of common and complex commands:
Acknowledge alarm
Acknowledge alarm in Live Viewer
Acknowledge alarm in Live Viewer using type
Acknowledge alarm using context
Acknowledge alarm using context and type
Acknowledge alarm using type
Add a bookmark
Add find results
Arm/disarm active tile for alarms
Block a camera
Change input focus in Live Viewer
Change instant replay playback speed
Change PTZ speed of the viewed camera
Close serial port
Connect encoder to decoder
Control PTZ
Create custom action
Create custom event
Create object
Cycle layout
Cycle pattern
Cycle tile
Destroy object
Disconnect encoder from decoder
Display a camera
Display a sequence
Display a URL address in a Live Viewer
End macro
Expand current tile
Find
For each block
Forward alarm
Forward alarm using context
Get connected decoders list
Get connected encoder
Get current decoder ID
Get current decoder type
Get current encoder ID
Get current encoder type
Get current macro arguments
Get current macro GUID
Get current tile
Get current user GUID
Get custom action description
Get custom event description
Get entity
Get entity GUID
Get entity ID
Get entity type
Get number of result
Get user GUID
Go to preset
Go to step
Hold sequence
If block (conditional block)
Listen audio on viewed camera
Next sequence
Open serial port
Override with event recording quality
Override with manual recording quality
Prevent replacement of connected tiles
Previous sequence
Record viewed camera
Recording quality as standard configuration
Remove camera from tile
Remove current tile
Remove sequence from tile
Resume sequence
Run a pattern
Run macro
Run macro instance
Run macro instance with context
Send a message
Send a message through the Archive Player
Send a message through the Live Viewer
Send an alert sound
Send an email
Send custom action
Send custom event
Set callback interface
Set current tile
Set logged on user
Set PTZ auxiliary
Set the output relay to its default state
Set the output relay to the opposite of its default state
Set tile pattern
Start backup
Start recording
Stop macro
Stop recording
Talk on viewed camera
Trigger alarm
Trigger alarm using a context
Unblock a camera
View a map in the Live Viewer
Wait
Write to serial port
Shall support the creation of schedules to which any of the following functional aspects can be attached:
Video quality (for each video stream per camera)
Recording (for each camera)
Motion detection (for each detection zone per camera)
Brightness, Contrast, Hue (for each camera)
Events / actions
User Logon
Camera sequence execution
Macro execution
Alarms
Shall support creation of unlimited recording schedules and assign any camera to any schedules.
Shall detect and warn user of any conflict within assigned schedules.
Shall provide tools to define automatic actions to be taken in response to internal/external events.
Shall provide the capability to set a pan-tilt-zoom protocol to a specific DVS serial port and allow mixing domes of various manufacturers within a system.
When a new unit is added to the DVMS, it shall be assigned a default preset device name.
User shall have the ability to configure a return to home function after a predefined time of inactivity for PTZ cameras. The inactivity time is configurable from 1 to 7200 seconds.
Live Viewer
The Live Viewer application shall allow live viewing of video and live audio communications with individual DVS units.
It shall have the following minimum capabilities:
Shall enable live monitoring of 1 to 16 video streams simultaneously on a single 1024x768 monitor, depending on frame rate, resolution and quality of streams.
Shall support as many monitors as the PC video adapters are capable of taking. Each monitor should be able to display 1 to 16 video streams.
Shall enable operators to choose from a number of possible camera display patterns ranging from 1 tile to 16 tile display patterns.
Shall display all cameras attached to the system and all cameras attached to federated systems (see Federation Server).
Shall display all camera sequences created in the system and all camera sequences created on federated systems (see Federation Server).
Shall allow operators to control (Pause/Play, skip forwards, skip backwards) Camera sequences without affecting other operators ability to view and control the same sequence.
Shall display all analog monitors attached to the system.
All cameras, sequences and analog monitors shall be displayed in a logical tree. The operator shall have tools to quickly find any camera based on partial name or description.
The operator shall be able to drag and drop a camera from a tree of cameras into a window or an analog monitor icon for live viewing.
The operator shall be able to drag and drop a camera sequence from a tree of cameras into a window or an analog monitor icon for live viewing.
Video streams may be assigned to tiles that are not presently visible in the currently displayed pattern.
Shall support Mapping functionality, where digital maps are used to represent the physical location of cameras and other devices throughout the surveillance system. Maps shall have the ability to contain hyperlinks so as to create a hierarchy of interlinked maps. The mapping functionality shall be able to import maps from any graphical software supporting BMP, JPEG, and/or GIF image formats.
The operator shall be able to drag and drop a camera from a map into a window for live viewing.
The operator shall be able to click on an icon in a map to initiate a camera preset, run a pattern or send a I/O stream.
Shall support the procedure functionality, where procedures can be triggered to appear during a certain event and can be used to provide detail instructions to the operator as to the actions he should take.
Shall support touch screen technology.
The operator shall be able to optimize the monitor for touch screen technology.
Shall support digital zoom on live camera video streams.
Shall support guard-tour (automatic sequencing of camera layouts) with a pre-assigned dwell time through pre-defined monitor views (for example: rotating views from a quad view to a 16 camera view to a full view at specified intervals).
Shall allow the user to choose any of the video streams associated to a camera for viewing.
Each Live Viewer shall have an icon indicating the number of alarms in queue that are assigned to the logged on user. The alarms shall also be displayed in an alarm pane at the bottom of the screen. The alarm pane shall display the currently active alarms as well as alarms acknowledged, auto-acknowledged, forwarded and snoozed.
Shall enable the user to perform the following actions on alarms:
Acknowledge (default method)
Acknowledge (alternate method)
Acknowledge (custom method)
Snooze (for a preset number of seconds)
Forward to other users on the system
Show a procedure associated to the alarm
Show the history of an alarm
Launch the Archive Player to review past alarms
Shall enable the user to spontaneously trigger alarms based on something he sees on a camera. The camera of interest shall be sent as part of the alarm to selected users.
Shall allow for audio communication with DVS units. The operator shall have the option of using full duplex or half duplex mode (to act as an IP intercom system). Audio shall be archived on the same storage as video from cameras.
The operator shall easily navigate between this application and the other CSA applications (if he has access rights) by single point and click functionality.
The operator shall be able to control pan-tilt-zoom, iris, focus, dome relays, dome patterns, dome presets and the dome configuration menus. He/she shall also be able to set an unlimited number of presets and patterns.
Users shall be able to control PTZ functions with a standard PC joystick.
Each operator shall be assigned a PTZ priority ranging from 1 to 255. This allows a prioritization between operators on who has control over a camera.
The system shall allow users to have the ability to lock PTZ control. Users with a higher PTZ priority can unlock PTZs from users with lower priorities.
Shall allow operators to bookmark important events for later retrieval on any archiving camera. Operators can uniquely name each bookmark in order to facilitate future searches.
The operator shall be able to start/stop recording on any camera in the system, which is configured to allow manual recording, by clicking on a single button.
The operator shall have the capability to activate or de-activate viewing of all system events as they occur.
Shall allow operators to view an instant replay of the video for any archiving camera. The operator will be able to define the amount of time he wishes to go back (unlimited). He will be able to control as well the playback with:
Pause
Lock Speed
Forward Playback at: 1x, 2x, 4x, 10x, 20x, 40x, 100x
Reverse Playback I-frame by I-frame
Fast rewind at: -10x, -20x, -40x, -100x
Slow Forward Playback at: Frame by frame, 1/8x, 1/4x, 1/3x, 1/2x, 1x
Loop playback between two time markers
The Instant Replay function shall playback video at the time of the alarm when activated in a tile displaying an alarm. With a graphical timeline representation, the user shall be able to control what time he is looking at. The instant replay pane can be undocked to allow video window resizing.
Users shall be able to take snapshots of live video feeds in the Live Viewer and be able to save or print the snapshots.
Shall allow operators to add bookmarks or view their instant replay in the Archive Player application by clicking on a single button in the Instant Replay tab.
The operator shall be able to choose and trigger an action from a list of actions. (see Directory Section 2.02J for list of events and actions).
The user shall have the ability to execute frequently used macros from a pane or a function key in the Live Viewer.
The user shall be able to view the same camera multiple times in different tiles.
Users shall be able to archive live video streams locally on the workstation. No SSM need to be installed on the workstation. Recording is activated and terminated manually by the user. Two recording methods are available to the user:
Tile archiving: Video displayed within a specific tile is recorded. Cameras can be switched within a tile.
Layout archiving: Video streams displayed in all tiles within a specific layout are recorded. Cameras can be switched within the tiles.
Users shall be able to display a layout of video streams within a PC monitor that removes all non-video graphical components. Delimiters between tiles are two pixels wide.
Users shall be able to switch easily between a Simple and an Advanced operation mode. In the Simple mode, only the most common commands shall be available.
The user shall have full control over the application workspace:
Show/hide window panes
Show/hide menus/toolbars
Show/hide overlaid information on video
Resize different window panes
Choice of tile display pattern/layout
The Live Viewer shall enable the administrator to freeze the application's workspace to certains users so that look and feel cannot be changed by the user.
Shall allow the local user (with permissions) to remotely control the workspace of other Live Viewer applications in the system.
Archive Player
The Archive Player application shall allow video and audio archive playback.
It shall have the following minimum capabilities:
Shall support audio and video playback of any time span.
Shall support the display of up to 16 archived video sequences at once.
Shall enable operators to choose from a number of possible camera display patterns ranging from 1 tile to 16 tile patterns.
Shall allow the operator to select between synchronous playback of all selected video streams, allowing operators to view events from multiple angles or across several camera fields, or non-synchronous playback.
Shall allow the operator to simultaneously view the same camera in multiple tiles at different time intervals.
Shall allow the operator to control the playback with:
Pause
Lock Speed
Forward Playback at: 1x, 2x, 4x, 10x, 20x, 40x, 100x
Reverse Playback I-frame by I-frame
Fast rewind at: -10x, -20x, -40x, -100x
Slow Forward Playback at: Frame by frame, 1/8x, 1/4x, 1/3x, 1/2x, 1x
Loop playback between two time markers
Shall display a single timeline, or optionally one timeline for each selected video stream, with which the operator can navigate through the video sequence by simply clicking on any point in the timeline.
Shall display the level of motion at any point on a timeline.
Shall clearly display bookmarks and metadata events on the timeline(s) (see Metadata Engine for more details). Shall be able to query archived video from one or multiple archived video servers using various search criteria, including but not limited to, time, date, camera, site and past alarms.
Shall display the drive on which a file is located in a results pane when a query search is performed in the Client Application.
Shall provide the tool to search video and associated audio on user-defined events or motion parameters.
Shall allow operators to define an area of the video field in which to search for motion as well as define the amount of motion that will trigger search results. The Archive Player then retrieves all archived video streams that contain motion that meets the search parameters. There shall be a graphical timeline where the time of each search hit shall be indicated.
Shall allow operators to browse through a list of all bookmarks created on the system and select any bookmarked event for viewing.
Shall allow operators reviewing video to quickly skip between next and previous bookmarks.
Shall allow the user to add bookmarks to previously archived video for easier searching and retrieval.
Shall allow the user to protect important video sequences against deletion during normal disk cleanup routines performed by the Archiver (see Archiver Section 2.06N.1).
Shall allow operators to validate if a digitally signed video sequence has been tampered with or not.
Shall support digital zoom on playback video streams.
Shall provide still image export to JPEG and BMP format with Date and Time stamp on the image.
Shall provide tools to export video sequences and a self contained video player on various media such as a CD-ROM.
Shall provide tools to export video sequences in standard video formats, such as AVI and ASF.
Shall allow operators to load previously exported video files from their computer or network.
The operator shall easily navigate between this application and the other CSA applications (if he has access rights) by single point and click functionality.
Shall allow queries to be saved upon closing the Archive Player Application and reappear when the application is reopened.
Web Live Viewer
The Web Live Viewer application shall allow live viewing of video and live audio communications with individual DVS units.
It shall have the following minimum capabilities:
Shall enable live monitoring of 1 to 16 video streams simultaneously on a single 1024x768 monitor.
Shall enable operators to choose from a number of possible camera display patterns ranging from 1 tile to 16 tile display patterns.
Shall display all cameras attached to the system and all cameras attached to federated systems (see Federation Server).
Shall display all camera sequences created in the system and all camera sequences created on federated systems (see Federation Server).
Shall allow operators to control (Pause/Play, skip forwards, skip backwards) Camera sequences without affecting other operators ability to view and control the same sequence.
Shall display all analog monitors attached to the system.
All cameras, sequences and analog monitors shall be displayed in a logical tree.
The operator shall be able to drag and drop a camera from a tree of cameras into a window or an analog monitor icon for live viewing.
The operator shall be able to drag and drop a camera sequence from a tree of cameras into a window or an analog monitor icon for live viewing.
Video streams may be assigned to tiles that are not presently visible in the currently displayed pattern.
Shall support Mapping functionality, where digital maps are used to represent the physical location of cameras and other devices throughout the surveillance system. Maps shall have the ability to contain hyperlinks so as to create a hierarchy of interlinked maps. The mapping functionality shall be able to import maps from any graphical software supporting BMP, JPEG, and/or GIF image formats.
The operator shall be able to drag and drop a camera from a map into a window for live viewing.
The operator shall be able to click on an icon in a map to initiate a camera preset, run a pattern or send a I/O stream.
Shall support the procedure functionality, where procedures can be triggered to appear during a certain event and can be used to provide detail instructions to the operator as to the actions he should take.
Shall support digital zoom on live camera video streams
Shall support guard-tour (automatic sequencing of camera layouts) with a pre-assigned dwell time through pre-defined monitor views (for example: rotating views from a quad view to a 16 camera view to a full view at specified intervals).
Shall allow the user to choose any of the video streams associated to a camera for viewing.
Each Web Live Viewer shall have an icon indicating the number of alarms in queue that are assigned to the logged on user. The alarms shall also be displayed in an alarm pane at the bottom of the screen. The alarm pane shall display the currently active alarms as well as alarms acknowledged, auto-acknowledged, forwarded and snoozed.
Shall enable the user to perform the following actions on alarms:
Acknowledge (default method)
Acknowledge (alternate method)
Acknowledge (custom method)
Snooze (for a preset number of seconds)
Forward to other users on the system
Show a procedure associated to the alarm
Show the history of an alarm
Launch the Archive Player to review past alarms
Shall enable the user to spontaneously trigger alarms based on something he sees on a camera. The camera of interest shall be sent as part of the alarm to selected users.
The operator shall easily navigate between this application and the other Web based CSA applications (if he has access rights) by single point and click functionality.
The operator shall be able to control pan-tilt-zoom, iris, focus, dome relays, dome patterns, dome presets and the dome configuration menus. He/she shall also be able to set an unlimited number of presets and patterns.
Each operator shall be assigned a PTZ priority ranging from 1 to 255. This allows a prioritization between operators on who has control over a camera.
The system shall allow users to have the ability to lock PTZ control. Users with a higher PTZ priority can unlock PTZs from users with lower priorities.
Shall allow operators to bookmark important events for later retrieval on any archiving camera. Operators can uniquely name each bookmark in order to facilitate future searches.
The operator shall be able to start/stop recording on any camera in the system, which is configured to allow manual recording, by clicking on a single button.
The operator shall have the capability to activate or de-activate viewing of all system events as they occur.
Shall allow operators to view an instant replay of the video for any archiving camera. The operator will be able to define the amount of time he wishes to go back (unlimited). He will be able to control as well the playback with:
Pause
Lock Speed
Forward Playback at: 1x, 2x, 4x, 10x, 20x, 40x, 100x
Reverse Playback I-frame by I-frame
Fast rewind at: -10x, -20x, -40x, -100x
Slow Forward Playback at: Frame by frame, 1/8x, 1/4x, 1/3x, 1/2x, 1x
Loop playback between two time markers
The Instant Replay function shall playback video at the time of the alarm when activated in a tile displaying an alarm. With a graphical timeline representation, the user shall be able to control what time he is looking at. The instant replay pane can be undocked to allow video window resizing.
Users shall be able to take snapshots of live video feeds in the Live Viewer and be able to save or print the snapshots.
Shall allow operators to add bookmarks or view their instant replay in the Archive Player application by clicking on a single button in the Instant Replay tab.
The user shall be able to view the same camera multiple times in different tiles.
Web Archive Player
The Web Archive Player application shall allow video and audio archive playback.
It shall have the following minimum capabilities:
Shall support audio and video playback of any time span.
Shall support the display of up to 16 archived video sequences at once.
Shall enable operators to choose from a number of possible camera display patterns ranging from 1 tile to 16 tile patterns.
Shall allow the operator to select between synchronous playback of all selected video streams, allowing operators to view events from multiple angles or across several camera fields, or non-synchronous playback.
Shall allow the operator to simultaneously view the same camera in multiple tiles at different time intervals.
Shall allow the operator to control the playback with:
Pause
Lock Speed
Forward Playback at: 1x, 2x, 4x, 10x, 20x, 40x, 100x
Reverse Playback I-frame by I-frame
Fast rewind at: -10x, -20x, -40x, -100x
Slow Forward Playback at: Frame by frame, 1/8x, 1/4x, 1/3x, 1/2x, 1x
Loop playback between two time markers
Shall display a single timeline with which the operator can navigate through the selected video sequence by simply clicking on any point in the timeline.
Shall display the level of motion at any point on a timeline.
Shall clearly display bookmarks and metadata events on the timeline(s) (see Metadata Engine for more details). Shall be able to query archived video from one or multiple archived video servers using various search criteria, including but not limited to, time, date, camera, site and past alarms.
Shall display the drive on which a file is located in a results pane when a query search is performed in the Client Application.
Shall provide the tool to search video and associated audio on user-defined events or motion parameters.
Shall allow operators to define an area of the video field in which to search for motion as well as define the amount of motion that will trigger search results. The Web Archive Player then retrieves all archived video streams that contain motion that meets the search parameters. There shall be a graphical timeline where the time of each search hit shall be indicated.
Shall allow operators to browse through a list of all bookmarks created on the system and select any bookmarked event for viewing.
Shall allow operators reviewing video to quickly skip between next and previous bookmarks.
Shall allow the user to add bookmarks to previously archived video for easier searching and retrieval.
Shall allow the user to protect important video sequences against deletion during normal disk cleanup routines performed by the Archiver (see Archiver Section 2.06N.1).
Shall allow operators to validate if a digitally signed video sequence has been tampered with or not.
Shall support digital zoom on playback video streams.
Shall provide still image export to JPEG and BMP format with Date and Time stamp on the image.
Shall provide tools to export video sequences and a self contained video player on various media such as a CD-ROM.
Shall provide tools to export video sequences in standard video formats, such as AVI and ASF.
Shall allow operators to load previously exported video files from their computer or network.
The operator shall easily navigate between this application and the other Web based CSA applications (if he has access rights) by single point and click functionality.
Macro Editor
The Macro Editor shall be an integrated development environment for writing macros created for the DVMS (see Virtual Matrix Section B).
It shall have the following minimum capabilities:
Shall provide a code editor with syntax highlight.
Shall provide a standalone execution environment, without the need of any SSM applications to be installed.
Shall report syntax and execution errors and indicate the position of the error in the source code.
Shall be able to import and export macrocode to files.
Report Viewer
The Event Reporting Application shall provide reports on system activity.
System events shall be logged into a Microsoft SQL server.
The Event Reporting shall be equipped with templates for:
User activity Reports
System Health reports
Event/Action report
Database schema shall be made available to users for custom report generation.
Software Development Kit (SDK)
The SDK shall provide the capability to embed the monitor and archive player applications in third party applications.
It shall have the following minimum capabilities:
Shall support Windows NT/2000/XP.
Shall support running in Internet Explorer 5.0 or higher for Web base solutions.
Shall support viewing of more than one live camera in the same application.
Shall support playback of a recorded camera for a given time span.
Shall support export of a video sequence for a given time span.
Shall support high-level languages such as JScript, VBScript, Visual Basic, Java, C and C++.
Shall support different topologies of IP networks such as: LAN, WAN, VPN, Internet, Wireless and Cellular.
Shall support multicast streaming on LAN and WAN.
Shall support functionality that enables audio and video streams to go through NATs and Firewalls.
SymSecure Enterprise 4 / April 2008
2