Your SlideShare is downloading. ×
1.01.doc
1.01.doc
1.01.doc
1.01.doc
1.01.doc
1.01.doc
1.01.doc
1.01.doc
1.01.doc
1.01.doc
1.01.doc
1.01.doc
1.01.doc
1.01.doc
1.01.doc
1.01.doc
1.01.doc
1.01.doc
1.01.doc
1.01.doc
1.01.doc
1.01.doc
1.01.doc
1.01.doc
1.01.doc
1.01.doc
1.01.doc
1.01.doc
1.01.doc
1.01.doc
1.01.doc
1.01.doc
1.01.doc
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

1.01.doc

705

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
705
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
5
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  1. DIGITAL VIDEO MANAGEMENT SOFTWARE SymSecure Enterprise 4 April 2008 SymSecure Enterprise 4 / April 2008 1
  2. Table of Contents PART 1 DIGITAL VIDEO MANAGEMENT SOFTWARE (DVMS).....................................................3 1General............................................................................................................................................................3 1.02 IP Video....................................................................................................................................................4 1.03 Hardware Independence...........................................................................................................................4 PART 2 SERVER SOFTWARE MODULES (SSM)..................................................................................9 2.01 General......................................................................................................................................................9 2.02 Directory...................................................................................................................................................9 2.03 Standby Directory...................................................................................................................................13 2.04 Gateway..................................................................................................................................................13 2.05 Federation Server....................................................................................................................................13 2.06 Archiver..................................................................................................................................................14 2.07 Standby Archiver....................................................................................................................................16 2.08 Redundant Archiver................................................................................................................................17 2.09 Auxiliary Archiver..................................................................................................................................17 2.10 Restore Archiver.....................................................................................................................................17 2.11 Media Gateway.......................................................................................................................................17 2.12 Metadata Engine.....................................................................................................................................17 2.13 Standby Metadata Engine.......................................................................................................................18 2.14 Virtual Matrix.........................................................................................................................................18 2.15 Standby Virtual Matrix...........................................................................................................................18 2.16 Watchdog................................................................................................................................................19 2.17 Server Administrator..............................................................................................................................19 PART 3 CLIENT SOFTWARE APPLICATIONS (CSA).......................................................................20 3.01 General....................................................................................................................................................20 3.02 Configuration Tool.................................................................................................................................24 3.03 Live Viewer............................................................................................................................................28 3.04 Archive Player........................................................................................................................................31 3.05 Web Live Viewer....................................................................................................................................32 3.06 Web Archive Player................................................................................................................................34 3.07 Macro Editor...........................................................................................................................................35 3.08 Report Viewer.........................................................................................................................................35 3.09 Software Development Kit (SDK).........................................................................................................36 SymSecure Enterprise 4 / April 2008 2
  3. SymSecure Enterprise 4 Part 1: Digital Video Management Software (DVMS) 1.01General A.The DVMS shall be a highly scalable enterprise level software solution. B.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. C.The DVMS shall include the following applications: 1.Server Software Modules (SSM): a.Directory (System Server) b.Standby Directory c.Gateway d.Federation Server e.Archiver f.Standby Archiver g.Redundant Archiver h.Auxiliary Archiver i.Restore Archiver j.Media Gateway k.Metadata Engine l.Standby Metadata Engine m.Virtual Matrix n.Standby Virtual Matrix o.Watchdog p.Server Administrator 2.Client Software Applications (CSA): a.Configuration Tool b.Live Viewer c.Archive Player d.Web Live Viewer e.Web Archive Player f.Macro Editor g.Report Viewer 3.Software Development Kit (SDK)
  4. 1.02IP Video A.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. B.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. C.The DVMS shall support the following IP video servers: 1.GE video servers a.DVMRe b.GE CamPlus IP c.GE Megapixel d.Legend IP e.SymDec1 f.SymDec4 g.SymDec16 h.SymNet i.SymSafe Pro 4/8/16 D.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.03Hardware Independence A.The DVMS shall require no proprietary recording hardware, no hardware multiplexer or time-division technology for video or audio recording and monitoring. B.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. C.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. 1.The DVMS shall support the following list of PTZ camera protocols with respect to the configuration outlined in Paragraph C above: a.360 Vision b.Astel TC20 c.Axsys d.Bosch Bilinx e.Bosch TC8650 & TC700 Series f.Canon VC-C1 g.Canon VC-C4 h.CNB i.Cohu (CCR communication protocol revision 1.0 including iDOME series) j.Creco Black Box V2.4 Protocol k.Dynacolor l.Elbex m.Elbex Ex2000-8000 n.Ernitec
  5. o.GE Kalatel ASCII p.GE Legend q.Guardall Dome r.GYYR Vortex (V6 Series, VM Series and VDN Series Cameras) s.Hytec (HYTEC DTR 100 Z ADF NTSC) t.Image Labs u.IR516 Thermal Camera v.ISAP w.ISAP/QuickSet x.ISAP/QuickSet QPT130 y.ISS z.Javelin J0308 (ACU, ACULV, ACUX) aa.JVC TK-676 PTZ bb.JVC JCCP-F cc.JVC JCPB-S dd.LMW ee.Merit Li-Lin Fastdome Protocol including PIH-7625 Series, PIH-7000 and PIH-7600 Series ff.Panasonic Conventional gg.Panasonic BB-HCM381 hh.Pelco D ii.Pelco P jj.Philips kk.Philips Fixed Speed ll.QuickSet mm.QuickSet QPT130 nn.QuickSet/ISAP oo.Radian pp.RVision Dome qq.Samsung SPD 1600 rr.Samsung SPD SCC-641/643 ss.Samsung SPD SCC-C6405P tt.Sanyo Z protocol uu.Sensormatic RS422 vv.Sensormatic SpeedDome Ultra IV and AD DeltaDome ww.Sony BRC-300 xx.Sony Visca yy.ThermoVision zz.ThermoVision/QuickSet aaa.Ultrak
  6. bbb.V1LC ccc.VCL VCLTP protocol ddd.Vicon V15UVS eee.Vicon V1x00R-PVP fff.Videoalarm VLPT400 EIA485/EIA 422 communication protocol ggg.Videotec 2.The DVMS shall support the following list of PTZ keyboard protocols: a.GE ImpactNet 3.The DVMS shall support the following CCTV matrix switches: a.GE Kalatel ASCII 4.The DVMS shall support the following access control systems and access control system communication protocols: a.GE Picture Perfect D.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. E.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. F.The DVMS shall have long-term storage capabilities on any Windows supported tape backup. G.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. H.The DVMS shall encrypt the VSIP control channel with SSL. I.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. J.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: 1.Local time of camera 2.Local time of the SSM 3.Local time of user’s workstation 4.GMT Time 5.Other time zone K.The DVMS shall consist of server software modules (SSM) and client software applications (CSA). L.Both the SSM and CSA shall run on Windows® XP Professional with Service Pack 2 or Windows® 2003 Server operating systems. M.It shall be possible to install both the SSM and CSA on a single workstation or on separate workstations. N.SSM and CSA shall be able to operate on separate networks. O.The configuration of the hardware running the CSA shall be: 1.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 card
  7. 2.Medium: Intel® Core®2 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 card 3.High: Intel® Core®2 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 card P.The recommended configuration of PCs running the SSM: 1.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 2.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 drive 3.High: 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 4.The hard drives must be purchased from one of the following manufacturers: a.IBM b.Maxtor c.Quantum d.Western Digital e.Seagate Q.Audio and Video storage configuration for the SSM shall either be: 1.Internal or external IDE organized or not in a RAID configuration; 2.Internal or external SCSI/Fibre Channel organized or not in a RAID configuration; 3.It shall be possible to include within the overall storage system disks located on external PCs on a LAN or WAN as well as; 4.Network Attached Servers (NAS) on a LAN or WAN as well as; 5.Storage Area Networks (SAN); R.The SSM shall not limit the actual storage capacity configured per server. S.DVMS shall be upgraded from one version to another without the user having to uninstall the previous version. T.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: 1.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. 2.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. 3.The CSA requires one of the following video cards for dual screen operation: a.nVidia Quadro FX550 or better
  8. Part 2: Server Software Modules (SSM) 2.01General A.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. B.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. 2.02Directory A.The Directory shall maintain a catalogue of settings (configuration database) for all CSA, SSM and DVS in the system. B.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). C.The Directory shall give the capacity to view all DVS in a network even if the DVS are assigned to different archive servers. D.The Directory, in the case that a camera signal loss, shall detect the video loss and have the capability to alert the system administrator. E.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. F.The Directory shall create an audit trail of events and user activities. G.The Directory shall perform dynamic bandwidth management. H.The Directory shall authenticate users and give access to the DVMS based on predefined user access rights. I.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. J.The Directory shall receive and log all of the following events: 1.Alarm Events: a.Trigger b.Activate/Reactivate c.Forward d.Snooze e.Ack (default) f.Ack (alternate) b.Ack (custom) 2.Application Events: a.Application lost b.Application connected
  9. 3.Archiver Events: a.Archiving queue full b.Archiving stopped c.Backup started d.Backup success e.Backup failed f.Cannot write on a specified location g.Cannot write to any drive h.Database lost i.Database recovered j.Disk(s) full k.Disk load is over 80% l.Invalid custom encryption values m.Not enough disk space for logging n.Protected video threshold exceeded 4.Camera Events: a.Camera not archiving b.File deleted c.Live bookmark added d.Playback bookmark added e.Motion on f.Motion off g.Network connection lost h.Receiving RTP packets from multiple sources i.Recording started (by alarm) j.Recording stopped (by alarm) k.Recording started (by schedule) l.Recording stopped (by schedule) m.Recording started (by programmed action) n.Recording stopped (by programmed action) o.Recording started (through motion detection) p.Recording stopped (through motion detection) q.Recording started (by user) r.Recording stopped (by user) s.RTP packets lost t.Signal lost u.Signal recovered 5.Digital Input Events: a.Digital input contact opening
  10. b.Digital input contact closing 6.Directory Events: a.Connection lost with the alarm database b.Connection recovered with the alarm database c.Directory Failover Coordinators not synchronized d.Not enough disk space for logging 7.DVS Events: a.Invalid configuration in DVS b.Signal lost c.Signal recovered d.Unit discovered e.Unit lost 8.Macro Events: a.Macro error b.Macro started c.Macro stopped 9.Plug-in Events: a.Plug-in error b.Plug-in started c.Plug-in stopped d.Database out of disk space 10.PTZ Events: a.PTZ activated b.PTZ locked c.PTZ stopped 11.User events: a.User logon b.User logoff K.The Directory shall have the capability to execute any of the following actions in response to any of the events listed above: 1.Archiving Actions: a.Start recording b.Stop recording c.Add a bookmark d.Override with manual recording quality e.Override with event recording quality f.Recording quality as standard configuration g.Start applying video protection h.Stop applying video protection 2.Monitoring Actions:
  11. a.Block a camera b.Unblock a camera c.View a camera on an analog monitor d.View a camera in the Live Viewer e.View a camera in a free window of the Live Viewer f.View a map in the Live Viewer g.Display a URL address in a Live Viewer 3.PTZ Actions: a.Go to preset b.Run a pattern c.Set PTZ auxiliary d.Clear PTZ auxiliary e.Go home 4.User Notification Actions: a.Send a message b.Send an alert sound c.Send an email d.Trigger Alarm 5.Output Relay Actions: a.Set the output relay to the opposite of its default state b.Set the output relay to its default state c.Set the output relay to on d.Set the output relay to off e.Set the output relay to pulse (pulse is configurable) 6.Device Control Actions: a.Send a string on the serial port b.Reboot a DVS 7.Macro Actions a.Execute a macro L.Shall support Advanced Alarm Management, which shall have the ability: 1.To assign alarms and procedures to specific users or user groups. 2.To escalate alarms to other users after a configurable time that an alarm has not been acknowledged. 3.To allow a user to queue alarms, and view alarm history. 4.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. 5.To configure multiple cameras to display upon an alarm. 6.To display alarms in block, salvo or simple mode. 7.To allow the administrator to assign a priority to each type of alarm, ranging from 1-30. 8.To display an alarm pane with past alarms and associated data.
  12. 2.03Standby Directory A.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. B.The DVMS shall support multiple Directories on standby, lined up to take over as the acting Directory in a cascading fashion. C.The Standby Directory shall keep its configuration database synchronized with the primary Directory. D.The Standby Directory shall be able to act as a global standby or a local standby. 1.The global Standby Directory is one that can take over the entire load of the primary Directory. 2.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. 3.The DVMS shall accept a configuration featuring both global and local Standby Directories. 2.04Gateway A.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. B.Multiple Gateways shall be used on large DVMS installations to increase the service availability and to provide manually controlled or automatic load balancing. C.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. 2.05Federation Server A.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. B.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. C.The Federation Server shall be able to join DVMS systems running SymSecure v4.1 versions together. D.The Federation Server shall allow the viewing of live as well as archived videos from the federated DVMS systems. E.The Federation Server shall allow the Federation host to receive the events issued by DVS owned by the Federation members. 2.06Archiver A.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. B.The Archiver shall protect archived audio/video files and the system database against network access and non- administrative user access. C.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. D.The Archiver shall offer a plug and play type hardware discovery service with the following functionalities: 1.Automatically discover DVS units as they are attached to the network. 2.Discover DVS units on different network segments including the Internet and across routers with or without network address translation (NAT) capabilities. E.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.
  13. F.Shall provide the functionality of storing of video and audio streams based on triggering events such as: 1.Digital motion detection 2.Digital input activation 3.Macros 4.Through SDK application recording G.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: 1.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. 2.Full Screen Unit: This is the same as the Full Screen but the motion detection takes place in the DVS. 3.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. 4.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. 5.Disabled: No motion detection is made on this camera. H.The Archiver shall allow for multiple recording schedules to be assigned to a single camera, each schedule shall be created with the following parameters: 1.Recording mode: a.Continuous b.On Motion/Manual c.Manual d.Disabled 2.Recurrence pattern: a.Once on specific days b.Specific days on a yearly basis c.Specific days on a monthly basis d.Specific days on a weekly basis e.Daily 3.Time coverage: a.All day b.Specific time range(s) c.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. I.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. 1.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: a.Live
  14. b.Recording c.Remote d.Low resolution e.High resolution 2.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: a.Maximum bit rate b.Maximum frame rate c.Image quality d.Key frame interval e.Etc. J.The Archiver shall have the ability to dynamically boost the quality of the "recording stream" (see previous bullet) based on specific events: 1.When a user starts recording manually. 2.When recording is triggered by a macro, an alarm or detected motion. K.The Archiver shall have the capacity to communicate with DVS using 128 bits SSL encryption. L.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. M.The Archiver shall empower the administrator with a full range of disk management options: 1.The Archiver shall allow the administrator to choose the disks to use for archiving and to set a maximum quota for each. 2.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. 3.The Archiver shall offer the following options to clean up old archives, on a camera by camera basis: a.After a preset number of days b.Deleting oldest archives first when disks run out of space c.Stop archiving when disks are full N.The Archiver shall allow important video sequences to be protected against normal disk cleanup routines. 1.Users shall have the following options when protecting a video sequence: a.Until a specified date b.For a specified number of days c.Indefinitely (until the protection is explicitly removed) 2.The Archiver shall allow the administrator to put a cap on the percentage of storage space occupied by protected video. O.The Archiver shall keep a log and compile statistics on disk space usage. 1.The statistics shall be available by disk group or for the whole Archiver. 2.The statistics shall show the percentage of protected video over the total used disk space. P.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. Q.The Archiver shall have the capacity to down-sample video streams for storage saving purposes. The down- sampling options available are the following:
  15. 1.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. 2.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. 2.07Standby Archiver A.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. B.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. C.It shall be possible for a single Archiver to fail over multiple Standby Archivers simultaneously. D.It shall be possible for a single Archiver to act as the standby for multiple other Archivers. E.Any Archiver in the system can be designated as another's standby. 2.08Redundant Archiver A.The Standby Archiver shall have the ability to act as a Redundant Archiver. B.The Redundant Archiver shall maintain an exact copy of everything recorded by the default Archiver, i.e. audio/video archives, events and bookmarks. C.Redundancy shall be configured on a camera-by-camera basis. D.The Redundant Archiver shall use a multicast video stream from the DVS and shall not require an additional connection to any DVS. 2.09Auxiliary Archiver A.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. B.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. 2.010Restore Archiver A.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. B.The Restore Archiver shall provide the option to restore partially a backup set. 2.011Media Gateway A.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. B.The Media Gateway shall allow for the configuration of resolution and text overlay. 2.012Metadata Engine A.The Metadata Engine shall extend the functionalities of the DVMS through the use of appropriate Metadata Engine plug-ins (ME plug-ins). 1.The ME plug-ins shall give the DVMS the capability to perform the following: 2.Interface with GE Security’s Picture Perfect Integrated Security Management System 3.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. 4.The ME plug-ins shall create metadata events that can be queried and displayed on video archive timelines. 5.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.
  16. 6.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). 7.The administrator shall be able to control the retention period of the metadata on a plug-in by plug-in basis. B.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. C.The DVMS shall accept multiple instances of Metadata Engine. 2.013Standby Metadata Engine A.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. B.Each ME plug-in in the system shall have its own list of Standby Metadata Engines, called the failover list. When a plug-in’s default Metadata Engine fails, the next one in its failover list will continue the execution of the plug-in. C.It shall be possible for a single Metadata Engine to fail over multiple Standby Metadata Engines simultaneously. D.It shall be possible for a single Metadata Engine to act as the standby for multiple other Metadata Engines. E.Any Metadata Engine in the system can be designated as another's standby. 2.014Virtual Matrix A.The Virtual Matrix shall have the capability of creating camera sequences with the following functionality: 1.Each Sequence shall have a maximum of 500 cameras. 2.Each camera in the sequence shall have its own individual dwell time, from 1 to 999 seconds. 3.Each entry in a sequence shall have the capacity to trigger camera presets, patterns or auxiliaries. 4.Multiple users shall be able to view the same camera sequence simultaneously. Users shall be able to pause the sequence without affecting other viewers. B.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). C.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). D.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. E.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. 2.015Standby Virtual Matrix A.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. B.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. C.It shall be possible for a single Virtual Matrix to fail over multiple Standby Virtual Matrices simultaneously. D.It shall be possible for a single Virtual Matrix to act as the standby for multiple other Virtual Matrices. E.Any Virtual Matrix in the system can be designated as another's standby. 2.016Watchdog A.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.
  17. 2.017Server Administrator A.The Server Administrator shall provide the capability to configure the running environment of the SSM modules such as: 1.Database Servers 2.Storage Disks 3.Storage File Size 4.SSL certificates 5.Encryption Keys 6.DVS Discovery Options 7.Network Connection Modes 8.Network Connection Addresses and Ports
  18. PART 3 CLIENT SOFTWARE APPLICATIONS (CSA) 3.01General A.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. B.The CSA shall perform the following functions simultaneously without interfering with any of the SSM operations (Recording, Alarms, etc.): 1.Live display of cameras on a workstation. 2.Live display of cameras on an analog monitor. 3.Live display of camera sequences on a workstation. 4.Live display of camera sequences on an analog monitor. 5.Control of PTZ cameras. 6.Playback of archived video on a workstation. 7.Retrieval of archived video. 8.Instant Replay of live video on a workstation. 9.Use of maps. 10.Use of procedures. 11.Configuration of system settings. 12.Execution of system macros. 13.Display and management of alarms on a workstation. 14.Display and management of alarms on an analog monitor. 15.Create and print snapshots of live video feeds. 16.Create and print snapshots of archived video feeds. 17.Block cameras from less privileged users. 18.Unblock cameras. C.All applications shall support any form of IP network connectivity, including: LAN, WAN, VPN, Internet, and Wireless (WiFi and Cellular) technologies. D.All applications shall support IP Multicast (UDP) and Unicast (TCP or UDPs) video streaming. E.All applications shall automatically adapt to the network topology and use the best available method to receive streaming video. F.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: 1.Connection time based on schedules: a.Time when access to the system is allowed b.Time when access to the system is denied
  19. 2.Access rights to sites: a.Sites are logical groupings of cameras and other system resources b.Sites shall form hierarchies c.Denying access to a site will deny access to all resources grouped under that site 3.Access or not to types of applications: a.Live Viewer b.Archive Player c.Configuration Tool d.Macro Editor e.Web Live Viewer f.Web Archive Player g.Media Gateway h.SDK 4.Priorities/Limitations: a.Over camera viewing b.Over PTZ control c.Over archived video (limit to a certain number of days in the past) 5.Privileges (see next bullet) G.The privileges that can be assigned to users shall include: 1.Configuration privileges: a.Site configuration, creation and deletion b.DVS configuration (1)Firmware upgrade (2)Creation and deletion c.Camera configuration (1)Video quality settings (2)Recording settings (3)Motion detection settings d.Analog monitor configuration e.Audio configuration f.Serial ports configuration g.Input pin configuration h.Output pin configuration
  20. i.PTZ configuration, creation and deletion j.Hardware matrix configuration, creation and deletion k.Schedules configuration, creation and deletion l.Custom events and actions configuration, creation and deletion m.Alarms configuration (1)Creation and deletion (2)Delete alarm instances n.Macros configuration, creation and deletion o.Camera sequence configuration, creation and deletion p.CCTV Keyboard configuration, creation and deletion q.Access control system configuration, creation and deletion r.Monitor group configuration, creation and deletion s.Camera group configuration, creation and deletion t.Viewer layout configuration and deletion u.Backup operator v.Modify logical IDs w.Plug-in configuration, creation and deletion 2.Archive Player privileges: a.Export video files 3.Live Viewer privileges: a.Change the displayed entities (1)Change layout selection (2)Change the tile pattern (3)Edit/Save the layout configuration (4)Change content in armed tiles (5)Arm/disarm tiles b.Start/Stop guard tour c.Edit guard tour dwell time d.Acknowledge alarms e.Forward alarms f.Snooze alarms g.Audio (listen/talk) h.Access Digital Zoom i.Do instant replay
  21. j.Execute Macros k.Change macro hot keys l.Local recording 4.PTZ controls: a.Do basic operations b.Change focus and iris settings c.Use presets d.Edit presets e.Use patterns f.Edit patterns g.Use auxiliaries h.Edit auxiliaries i.Use menu j.Lock PTZ k.Override PTZ lock 5.Other privileges: a.Record Manually b.Add bookmarks c.View cameras on an analog monitors d.Block cameras e.Send messages f.Send sounds g.Send emails h.Send on serial ports i.Execute custom actions j.Save and print snapshots k.Control camera sequences l.Change own password m.Protect video from deletion n.Remove video protection o.Change application options p.Change client views H.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. I.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. J.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.
  22. K.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. L.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. M.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. 3.02Configuration Tool A.The Configuration Tool application shall allow the administrator or users with appropriate privileges to change system configuration. B.It shall have the following minimum capabilities: 1.Shall provide decentralized administration of the entire system from anywhere on the network. 2.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. 3.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. 4.Shall have the capability to define access and privileges by user group as well as by individual users 5.Shall provide the ability to configure brightness, contrast and hue settings for each camera on the same DVS. 6.Shall provide the capability to enable audio recording on DVS units that support audio 7.Shall provide the ability to change audio parameters, serial port and I/O configuration of individual DVS units. 8.Shall provide the capability to rename all DVS units based on system topology and add descriptive information to each DVS. 9.Shall provide the capability to regroup specific cameras together and restrict or enable access rights to this group on a per user basis. 10.Shall provide the ability to set recording schedules and modes for each individual camera. The recording mode can be: a.Continuous b.On motion and Manual c.Manual only d.Disabled 11.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: a.Acknowledge alarm b.Acknowledge alarm in Live Viewer c.Acknowledge alarm in Live Viewer using type d.Acknowledge alarm using context e.Acknowledge alarm using context and type f.Acknowledge alarm using type g.Add a bookmark h.Add find results
  23. i.Arm/disarm active tile for alarms j.Block a camera k.Change input focus in Live Viewer l.Change instant replay playback speed m.Change PTZ speed of the viewed camera n.Close serial port o.Connect encoder to decoder p.Control PTZ q.Create custom action r.Create custom event s.Create object t.Cycle layout u.Cycle pattern v.Cycle tile w.Destroy object x.Disconnect encoder from decoder y.Display a camera z.Display a sequence aa.Display a URL address in a Live Viewer bb.End macro cc.Expand current tile dd.Find ee.For each block ff.Forward alarm gg.Forward alarm using context hh.Get connected decoders list ii.Get connected encoder jj.Get current decoder ID kk.Get current decoder type ll.Get current encoder ID mm.Get current encoder type nn.Get current macro arguments oo.Get current macro GUID pp.Get current tile qq.Get current user GUID rr.Get custom action description ss.Get custom event description tt.Get entity uu.Get entity GUID
  24. vv.Get entity ID ww.Get entity type xx.Get number of result yy.Get user GUID zz.Go to preset aaa.Go to step bbb.Hold sequence ccc.If block (conditional block) ddd.Listen audio on viewed camera eee.Next sequence fff.Open serial port ggg.Override with event recording quality hhh.Override with manual recording quality iii.Prevent replacement of connected tiles jjj.Previous sequence kkk.Record viewed camera lll.Recording quality as standard configuration mmm.Remove camera from tile nnn.Remove current tile ooo.Remove sequence from tile ppp.Resume sequence qqq.Run a pattern rrr.Run macro sss.Run macro instance ttt.Run macro instance with context uuu.Send a message vvv.Send a message through the Archive Player www.Send a message through the Live Viewer xxx.Send an alert sound yyy.Send an email zzz.Send custom action aaaa.Send custom event bbbb.Set callback interface cccc.Set current tile dddd.Set logged on user eeee.Set PTZ auxiliary ffff.Set the output relay to its default state gggg.Set the output relay to the opposite of its default state hhhh.Set tile pattern
  25. iiii.Start backup jjjj.Start recording kkkk.Stop macro llll.Stop recording mmmm.Talk on viewed camera nnnn.Trigger alarm oooo.Trigger alarm using a context pppp.Unblock a camera qqqq.View a map in the Live Viewer rrrr.Wait ssss.Write to serial port 12.Shall support the creation of schedules to which any of the following functional aspects can be attached: a.Video quality (for each video stream per camera) b.Recording (for each camera) c.Motion detection (for each detection zone per camera) d.Brightness, Contrast, Hue (for each camera) e.Events / actions f.User Logon g.Camera sequence execution h.Macro execution i.Alarms 13.Shall support creation of unlimited recording schedules and assign any camera to any schedules. 14.Shall detect and warn user of any conflict within assigned schedules. 15.Shall provide tools to define automatic actions to be taken in response to internal/external events. 16.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. 17.When a new unit is added to the DVMS, it shall be assigned a default preset device name. 18.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. 3.03Live Viewer A.The Live Viewer application shall allow live viewing of video and live audio communications with individual DVS units. B.It shall have the following minimum capabilities: 1.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. 2.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. 3.Shall enable operators to choose from a number of possible camera display patterns ranging from 1 tile to 16 tile display patterns. 4.Shall display all cameras attached to the system and all cameras attached to federated systems (see Federation Server).
  26. 5.Shall display all camera sequences created in the system and all camera sequences created on federated systems (see Federation Server). 6.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. 7.Shall display all analog monitors attached to the system. 8.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. 9.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. 10.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. 11.Video streams may be assigned to tiles that are not presently visible in the currently displayed pattern. 12.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. 13.The operator shall be able to drag and drop a camera from a map into a window for live viewing. 14.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. 15.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. 16.Shall support touch screen technology. 17.The operator shall be able to optimize the monitor for touch screen technology. 18.Shall support digital zoom on live camera video streams. 19.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). 20.Shall allow the user to choose any of the video streams associated to a camera for viewing. 21.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. 22.Shall enable the user to perform the following actions on alarms: a.Acknowledge (default method) b.Acknowledge (alternate method) c.Acknowledge (custom method) d.Snooze (for a preset number of seconds) e.Forward to other users on the system f.Show a procedure associated to the alarm g.Show the history of an alarm h.Launch the Archive Player to review past alarms 23.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.
  27. 24.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. 25.The operator shall easily navigate between this application and the other CSA applications (if he has access rights) by single point and click functionality. 26.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. 27.Users shall be able to control PTZ functions with a standard PC joystick. 28.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. 29.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. 30.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. 31.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. 32.The operator shall have the capability to activate or de-activate viewing of all system events as they occur. 33.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: a.Pause b.Lock Speed c.Forward Playback at: 1x, 2x, 4x, 10x, 20x, 40x, 100x d.Reverse Playback I-frame by I-frame e.Fast rewind at: -10x, -20x, -40x, -100x f.Slow Forward Playback at: Frame by frame, 1/8x, 1/4x, 1/3x, 1/2x, 1x g.Loop playback between two time markers 34.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. 35.Users shall be able to take snapshots of live video feeds in the Live Viewer and be able to save or print the snapshots. 36.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. 37.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). 38.The user shall have the ability to execute frequently used macros from a pane or a function key in the Live Viewer. 39.The user shall be able to view the same camera multiple times in different tiles. 40.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: a.Tile archiving: Video displayed within a specific tile is recorded. Cameras can be switched within a tile. b.Layout archiving: Video streams displayed in all tiles within a specific layout are recorded. Cameras can be switched within the tiles.
  28. 41.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. 42.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. 43.The user shall have full control over the application workspace: a.Show/hide window panes b.Show/hide menus/toolbars c.Show/hide overlaid information on video d.Resize different window panes e.Choice of tile display pattern/layout 44.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. 45.Shall allow the local user (with permissions) to remotely control the workspace of other Live Viewer applications in the system. 3.04Archive Player A.The Archive Player application shall allow video and audio archive playback. B.It shall have the following minimum capabilities: 1.Shall support audio and video playback of any time span. 2.Shall support the display of up to 16 archived video sequences at once. 3.Shall enable operators to choose from a number of possible camera display patterns ranging from 1 tile to 16 tile patterns. 4.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. 5.Shall allow the operator to simultaneously view the same camera in multiple tiles at different time intervals. 6.Shall allow the operator to control the playback with: a.Pause b.Lock Speed c.Forward Playback at: 1x, 2x, 4x, 10x, 20x, 40x, 100x d.Reverse Playback I-frame by I-frame e.Fast rewind at: -10x, -20x, -40x, -100x f.Slow Forward Playback at: Frame by frame, 1/8x, 1/4x, 1/3x, 1/2x, 1x g.Loop playback between two time markers 7.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. 8.Shall display the level of motion at any point on a timeline. 9.Shall clearly display bookmarks and metadata events on the timeline(s) (see Metadata Engine for more details). 10.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. 11.Shall display the drive on which a file is located in a results pane when a query search is performed in the Client Application. 12.Shall provide the tool to search video and associated audio on user-defined events or motion parameters.
  29. 13.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. 14.Shall allow operators to browse through a list of all bookmarks created on the system and select any bookmarked event for viewing. 15.Shall allow operators reviewing video to quickly skip between next and previous bookmarks. 16.Shall allow the user to add bookmarks to previously archived video for easier searching and retrieval. 17.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). 18.Shall allow operators to validate if a digitally signed video sequence has been tampered with or not. 19.Shall support digital zoom on playback video streams. 20.Shall provide still image export to JPEG and BMP format with Date and Time stamp on the image. 21.Shall provide tools to export video sequences and a self contained video player on various media such as a CD-ROM. 22.Shall provide tools to export video sequences in standard video formats, such as AVI and ASF. 23.Shall allow operators to load previously exported video files from their computer or network. 24.The operator shall easily navigate between this application and the other CSA applications (if he has access rights) by single point and click functionality. 25.Shall allow queries to be saved upon closing the Archive Player Application and reappear when the application is reopened. 3.05Web Live Viewer A.The Web Live Viewer application shall allow live viewing of video and live audio communications with individual DVS units. B.It shall have the following minimum capabilities: 1.Shall enable live monitoring of 1 to 16 video streams simultaneously on a single 1024x768 monitor. 2.Shall enable operators to choose from a number of possible camera display patterns ranging from 1 tile to 16 tile display patterns. 3.Shall display all cameras attached to the system and all cameras attached to federated systems (see Federation Server). 4.Shall display all camera sequences created in the system and all camera sequences created on federated systems (see Federation Server). 5.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. 6.Shall display all analog monitors attached to the system. 7.All cameras, sequences and analog monitors shall be displayed in a logical tree. 8.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. 9.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. 10.Video streams may be assigned to tiles that are not presently visible in the currently displayed pattern. 11.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.
  30. 12.The operator shall be able to drag and drop a camera from a map into a window for live viewing. 13.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. 14.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. 15.Shall support digital zoom on live camera video streams 16.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). 17.Shall allow the user to choose any of the video streams associated to a camera for viewing. 18.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. 19.Shall enable the user to perform the following actions on alarms: a.Acknowledge (default method) b.Acknowledge (alternate method) c.Acknowledge (custom method) d.Snooze (for a preset number of seconds) e.Forward to other users on the system f.Show a procedure associated to the alarm g.Show the history of an alarm h.Launch the Archive Player to review past alarms 20.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. 21.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. 22.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. 23.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. 24.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. 25.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. 26.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. 27.The operator shall have the capability to activate or de-activate viewing of all system events as they occur. 28.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: a.Pause b.Lock Speed c.Forward Playback at: 1x, 2x, 4x, 10x, 20x, 40x, 100x
  31. d.Reverse Playback I-frame by I-frame e.Fast rewind at: -10x, -20x, -40x, -100x f.Slow Forward Playback at: Frame by frame, 1/8x, 1/4x, 1/3x, 1/2x, 1x g.Loop playback between two time markers 29.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. 30.Users shall be able to take snapshots of live video feeds in the Live Viewer and be able to save or print the snapshots. 31.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. 32.The user shall be able to view the same camera multiple times in different tiles. 3.06Web Archive Player A.The Web Archive Player application shall allow video and audio archive playback. B.It shall have the following minimum capabilities: 1.Shall support audio and video playback of any time span. 2.Shall support the display of up to 16 archived video sequences at once. 3.Shall enable operators to choose from a number of possible camera display patterns ranging from 1 tile to 16 tile patterns. 4.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. 5.Shall allow the operator to simultaneously view the same camera in multiple tiles at different time intervals. 6.Shall allow the operator to control the playback with: a.Pause b.Lock Speed c.Forward Playback at: 1x, 2x, 4x, 10x, 20x, 40x, 100x d.Reverse Playback I-frame by I-frame e.Fast rewind at: -10x, -20x, -40x, -100x f.Slow Forward Playback at: Frame by frame, 1/8x, 1/4x, 1/3x, 1/2x, 1x g.Loop playback between two time markers 7.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. 8.Shall display the level of motion at any point on a timeline. 9.Shall clearly display bookmarks and metadata events on the timeline(s) (see Metadata Engine for more details). 10.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. 11.Shall display the drive on which a file is located in a results pane when a query search is performed in the Client Application. 12.Shall provide the tool to search video and associated audio on user-defined events or motion parameters. 13.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.
  32. 14.Shall allow operators to browse through a list of all bookmarks created on the system and select any bookmarked event for viewing. 15.Shall allow operators reviewing video to quickly skip between next and previous bookmarks. 16.Shall allow the user to add bookmarks to previously archived video for easier searching and retrieval. 17.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). 18.Shall allow operators to validate if a digitally signed video sequence has been tampered with or not. 19.Shall support digital zoom on playback video streams. 20.Shall provide still image export to JPEG and BMP format with Date and Time stamp on the image. 21.Shall provide tools to export video sequences and a self contained video player on various media such as a CD-ROM. 22.Shall provide tools to export video sequences in standard video formats, such as AVI and ASF. 23.Shall allow operators to load previously exported video files from their computer or network. 24.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. 3.07Macro Editor A.The Macro Editor shall be an integrated development environment for writing macros created for the DVMS (see Virtual Matrix Section B). B.It shall have the following minimum capabilities: 1.Shall provide a code editor with syntax highlight. 2.Shall provide a standalone execution environment, without the need of any SSM applications to be installed. 3.Shall report syntax and execution errors and indicate the position of the error in the source code. 4.Shall be able to import and export macrocode to files. 3.08Report Viewer A.The Event Reporting Application shall provide reports on system activity. B.System events shall be logged into a Microsoft SQL server. C.The Event Reporting shall be equipped with templates for: 1.User activity Reports 2.System Health reports 3.Event/Action report D.Database schema shall be made available to users for custom report generation. 3.09Software Development Kit (SDK) A.The SDK shall provide the capability to embed the monitor and archive player applications in third party applications. B.It shall have the following minimum capabilities: 1.Shall support Windows NT/2000/XP. 2.Shall support running in Internet Explorer 5.0 or higher for Web base solutions. 3.Shall support viewing of more than one live camera in the same application. 4.Shall support playback of a recorded camera for a given time span. 5.Shall support export of a video sequence for a given time span. 6.Shall support high-level languages such as JScript, VBScript, Visual Basic, Java, C and C++.
  33. 7.Shall support different topologies of IP networks such as: LAN, WAN, VPN, Internet, Wireless and Cellular. 8.Shall support multicast streaming on LAN and WAN. 9.Shall support functionality that enables audio and video streams to go through NATs and Firewalls.

×