Technical & Functional

8/8/2019 Technical & Functional

1/23


2/23

5. Digital Video Management (With Lenel NetworkVideo Recorders)a)

OverviewThe Digital Video Management System (DVMS) shall be available as astandalone solution or as an integrated solution that is seamlesslyintegrated with other Total Security Knowledge Management SolutionModules, including Access Control & Alarm Monitoring, AssetManagement, Credential Management, and Visitor Management. Allfunctionality described from this point forward shall reflect functionalityof the seamlessly integrated system. The DVMS shall work in conjunctionwith a Manufacturer Network Video Recorder (LNVR)

The LNVR shall not utilize any multiplexer-type technology for videorecording. Information supplied from IP camera sources via Ethernet shall

be digitally recorded simultaneously to a LNVR. The LNVR shall support avariety of industry standard IP Cameras from multiple manufacturers.

The LNVR shall be available in a Turnkey Solution as well as a SoftwareOnly version. In a Software Only version, users shall be able to load theLNVR software onto an industry standard PC platform of their choice, aslong as it meets the Manufacturers minimum specifications.

The Turnkey Solution shall also be available in a hybrid configuration,allowing for the unit to record video from both IP and analog sourcevideo inputs. The analog sources shall be supported by video captureboard options:

1) MPEG4: 8-Channel Video Board (up to 2 boards perchassis) which supports 8 channels at 3.75fps (NTSC) at 640 x240 (640 x 480 interlaced) resolution; or 8 channels at 7.5fps(NTSC) at 320 x 240 resolution. 8 channels at 3.7fps (PAL) at640 x 240 (640 x 480 interlaced) resolution; or 8 channels at6.2fps (PAL) at 320 x 240 resolution.

2) MPEG4: 4-Channel 30fps Video Board (up to 4 boardsper chassis) which allows simultaneous recording of up to 16high motion cameras. Each camera may record at 30fps,15fps, 7.5fps, 2fps, or 1fps (NTSC) and 25fps, 12.5fps, 6.2fps,

2fps, or 1fps (PAL). These can be at 320x240, 640x480 or720x480.3) H.264: 16-Channel FULL frame rate High ResolutionVideo Board, which allows simultaneous recording of up to 16high motion cameras. Each camera may record at 1/16, 1/8,1/4, 1/2, 1, 2, 4, 6, 8, 10, 12, 15, 16, 18, 20, 22,30(NTSC)/25(PAL). Resolutions will support, NTSC:352*240(CIF), 704*240(2CIF), 528*320(DCIF), 704*480(4CIF);PAL: 352*288(CIF), 704*288(2CIF), 528*384(DCIF),704*576(4CIF).

LENEL - A UTC FIRE & SECURITY COMPANY

OnGuard

Functional Specifications Version 6.3 Series Page 115

The LNVR shall be able to store recorded video on any industry standardstorage medium, as long as it meets the Manufacturers minimumspecification. The user shall be able to choose the appropriate storage

medium for their application, such as a hard disk storage array, storagearea network, or network attached storage.

The LNVR shall provide a fully modular architecture that offers upgradesin-place for additional recording capacity and shall continuously recordup to an unlimited number of video sources. The LNVR shallsimultaneously record video/audio, display live video/audio, and displayrecorded video/audio. None of the video operations shall interfere withthe other. Recording shall not stop playback, live viewing, or storage ofvideo.

The LNVR shall support event-based recording and/or shall recordcontinually 24 hours a day. The amount of local online storage that is

available for playback from the LNVR shall be dependant on the size ofthe hard drive in the LNVR or other storage medium as well as theindividual camera configuration (Frame Rate, Resolution, Compression).

The LNVR shall support Multicast-streaming technology whereby, onceone user has requested a live video stream other system users shall beable to view the same video stream without opening a separateconnection. Multicast streaming technology helps limit the amount ofbandwidth required for system operation/monitoring.

The LNVR shall support Unicast-streaming technology whereby eachrequest for recorded video will require a separate stream.

The LNVR shall support the limiting of frames per second to individual

clients. This shall be mutually exclusive with the Multicast-streamingtechnology.While the LNVR is continuously recording or archiving video, an unlimitednumber of authorized System Operators shall access video from a centralarchive server from client workstations connected to the data network(via a LAN or WAN connection). Up to 32 simultaneous System Operatorsshall access live or recorded video from a LNVR. Using a centralizedsystem administration tool, user defined profiles restrict each SystemOperators security access to specific video and to specific systemoperations, such as video monitoring, playback, adding, modifying, anddeleting cameras.A user-friendly database query tool shall enable authorized System

Operators to quickly locate video from any recorder and transparentlyplay it back. The SYSTEM shall enable CUSTOMER to use off the shelfvideo enhancement software. These image enhancement kits allow theSystem Operator to enhance a single video capture frame. The singlecaptured frames shall be a copy of the original recorded video. SystemOperators cannot alter the original recorded video in any way. The LNVRshall come with an image enhancement tool that shall be built into thedigital video player (DVP).The design of the LNVR shall be flexible and allow for the following:

LENEL - A UTC FIRE & SECURITY COMPANYOnGuard


Independent camera setup for frame rate, resolution, compressionrate, brightness, contrast and other factor setups. This architectureshall allow System Administrators to optimize camera-recording

settings. Each camera shall have the ability to be set to operate with adifferent frame rate, resolution, compression rate, brightness, contrastand other factor setups.

Total system solution to enable enterprise-wide, networked, multi-useraccess to all system resources via a wide range of options forconnectivity with the customers existing LAN and WAN.Scalable, yet compact system design that offers modular expansion toprotect CUSTOMER investment.Independent camera setup configurations for pre-event, event, andpost-event states shall be available. User shall be able to determineindependent frame rate settings for these states. Independent camera

setup configurations for time-lapse mode shall be available.Independent camera setup configurations for live versus recordedplayback shall be available. User shall be able to determine differentframe rate settings for live viewing and recorded playback.


3/23

b) Network Interface

The LNVR shall connect to an existing network. Various types of networkarchitectures shall be supported including Ethernet 100BT and 1 GigabitEthernet. Various types of network protocols shall be supported including

TCP/IP, IPX, and UDP.

The network interface shall allow remote access of the recording systemfrom various System Configuration and Alarm Monitoring clientworkstations located throughout the customer's facility.

Playback Over the LAN/WAN

The LNVR shall be configured to playback stored video over theLAN/WAN for remote access of video clips.

c) Seamless Integration with Total Security Knowledge

Management Modules1) Seamless Integration with Access Control andAlarm MonitoringThe LNVR shall seamlessly integrate with the Access Control &

Alarm Monitoring System. Any alarm/event in the SYSTEM shallhave the ability to be associated with a digital video clip in realtime. Each alarm/event in the SYSTEM shall store a pre-definednumber of seconds of video before the event occurred and a pre-defined number of seconds of video after the event occurred. Thisvideo clip shall be retrieved at any system Alarm Monitoring clientworkstation.


OnGuard



4/23


5/23

only store video for a user definable number of days. Any recorded videoolder then the user defined number of days shall not be available foreither play back or viewing.

The system shall support the use of local RAID 5 storage subsystems,which connect directly to the LNVR via RAID Controller Card. The systemshall support the use of the Nexsan ATAboy 2 (IDE/ATA Drives) unit,Nexsan SATABoy (iSCSI/SATA Drives), Nexsan SATABeast (Fibre/SATADrive). In all cases, initial system configuration shall take place via therespective third party software. However, system function thereaftershall be seamless to the user.

The LNVR shall communicate with the SYSTEM Alarm Monitoring andSystem Administration client workstations over the CUSTOMER networkor a private security network. The LNVR shall support networks such asEthernet and over TCP/IP, IPX, and UDP protocols.

The LNVR shall record camera signals from fixed color and fixed black &white cameras, dome, infrared cameras, x-ray cameras, and low lightcameras.Each LNVR shall have the ability to be given a realistic name of up to 32alphanumeric characters and shall have the ability to be marked on-lineor off-line. Each LNVR shall be given a workstation name as well as an IPaddress of where the LNVR is connected to the network. Each LNVR shallalso have a World Time Zone setting to allow LNVR to reside in differentareas of the world.Should the LNVR go offline, a specific alarm will be sent to AlarmMonitoring. Furthermore, a red X will display over the LNVR icon in the

system status tree. Once the LNVR is brought back online, the red X shallno longer display.

The SYSTEM shall allow an operator to view the available storage andperformance information directly from the configuration of the camera.

This shall include the available storage, resource usage and recordingrates for the network video recorder. Threshold alarms shall also beconfigurable when the amount of available storage falls below a setnumber of days.

The Turnkey LNVR shall be available in the followingconfigurations:

1) LDVR/UVS Extended Storage Chassis (DVC-EX1),shall include 3U, 19-inch rack mount chassis with Intel P43.0GHz single core CPU, 1GB 533MHz RAM, Windows XPProfessional operating system, Dual 10/100/1000Ethernet ports, one 80GB OS only hard drive, UP TO 8data hard drives KIT OPTIONS AVAILABLE, DVD/CD ROM,mouse and rack mount rail kit.2) Premium Extended Storage Chassis (DVC-EX2), shallinclude 3U, 19-inch rack mount chassis with Intel Core 2Duo E8400 3.0GHz dual core CPU, 2GB 667MHz RAM,Windows XP Professional operating system, Dual10/100/1000 Ethernet ports, one 80GB OS


OnGuard



6/23

only hard drive (UP TO 8 data hard drives KITOPTIONS AVAILABLE), DVD/CD ROM, mouse and rackmount rail kit.

3) LNVR Low Profile Storage Chassis (DVC-1U), shallinclude 1U rack mount chassis with Intel Xeon x32302.66GHz quad core CPU, 2GB 533MHz RAM, Windows XPProfessional operating system, Dual 10/100/1000 Ethernetports, one 80GB OS only hard drive (UP TO 3 data drives KIT OPTIONS AVAILABLE), CD/RW-DVD/R, mouse and rackmount rail kit.4) 2U Standard Chassis (DVC-2U), shall include 2U, 19-inch rack mount chassis with Intel Celeron D E14002.0GHz dual core CPU, 1GB 667MHz RAM, Windows XPProfessional operating system, 10/100/1000 Ethernet

port, one 80GB OS only hard drive (UP TO 4 data harddrives KIT OPTIONS AVAILABLE), DVD/CD ROM, mouseand rack mount rail kit.

e) Digital VideoCameras1) Individual Camera Input

SetupEach digital video camera or video encoder shall be independentlyconfigured to record digital video.

Each camera shall have the ability to be given a realistic name ofup to 32 alphanumeric characters and shall allow for the setup andadjustment of brightness, contrast, archiving, motion detection,

Pan/Tilt/Zoom, on a per camera basis.

The SYSTEM shall recognize the LNVR and channel that the camerais connected. System Administrators shall define whether eachcamera allows Pan/Tilt/Zoom commands to be accomplished fromthe Digital Video Player.

The LNVR shall support multiple network enabled Video Camerasand Video Encoders. The Video Encoder technologies shall allowthe LNVR to interface with analog and PTZ cameras. The LNVRshall support the following video formats simultaneously on thesame system:

1) MJPEG

2) MPEG-4

3) H.264

The LNVR shall support both formats simultaneously on the samesystem. The LNVR shall support multiple video resolutions in bothNTSC and PAL configuration. These resolutions will include CIF (352x 240 NTSC or 352 x 288 PAL), 4CIF (704 x 480 NTSC or 704 x 576PAL), D1 (720 x480 NTSC or 720 x


OnGuard



7/23

576 PAL), VGA (640 x 480) and mega-pixel resolutions. Theseresolutions shall be dependent on the network enabled videodevice. Each camera and video encoder shall have recording

settings to customize the recording properties of the cameraincluding:

1) Compression The compression of video input used bythe particular encoder (MJPEG, MPEG-4, H.264) dependingon camera type.2) Resolution The size of the image expressed in pixels.(example: 320 x 240, 640 x 480) This shall depend on thetype of camera or video encoder.

3) Frame rate The number of frames per second thenetwork enabled video camera or video encoder transmits a

video stream to the LNVR.4) Pre-Roll - The number of seconds of video that theLNVR will store previous to the event time that a linkedevent is generated. This time is specific to the associatedevent. The SYSTEM shall support up to 900 seconds of pre-roll.2) Post-Roll - The number of seconds of video that theLNVR will store after a linked event is generated. This time isspecific to the associated event.

2) Generate Motion DetectionAlarms

If supported by the camera or video encoder, each camera orvideo encoder shall have the ability to record video to the LNVRbased on motion detection at the camera or video encoder. Thetimes that motion detection recording occurs shall be user definedby time-zones. A sensitivity bar shall be available to adjust thesensitivity for motion in the cameras. If supported within thecamera or video encoder, each camera shall have the ability tohave a separate time zone and motion detection settings ifdesired. Areas of the video picture shall be configured to detectmotion. Motion in these areas shall generate alarms.3) Time-Lapse

RecordingThe LNVR shall allow the ability to configure time-lapse recordingon a by camera or video encoder basis. System Administratorsshall have the ability to configure cameras or video encoder torecord one frame of video every (x) seconds (2-3600 seconds)when there is no motion in the viewing area. Once motion isdetected, the LNVR shall automatically increase recording rate to apredefined frame rate, or can simply always record at the time-lapse rate. The LNVR shall also be able to use an event from otherintegrated SYSTEM modules to start recording at the increasedframe rate.


OnGuard



8/23

4) Audio Support

The LNVR shall support unidirectional and, if supported by the

camera or video encoder, synchronized audio recording throughcameras or video encoder that support this option. The ability torecord synchronized audio and video shall be enabled through andstored in the LNVR. The audio shall be available for both recordedvideo and live video playback. The audio shall be exclusivelyavailable for recording purposes. The SYSTEM shall only supportaudio protocol G.711.5) Firmware downloads

Select cameras and video encoders shall have the ability to receiveautomatic firmware downloads. These automatic firmwaredownloads shall be scheduled through the use of the SYSTEMScheduling mechanism.

6) Dry ContactsThe LNVR shall support both inputs and outputs that are providedby cameras or video encoder. The LNVR shall monitor the camerasinputs and upon state change, shall report an alarm to theSYSTEM. Outputs shall be available for linkage through the GlobalI/O feature of the SYTEM. These outputs shall also be able to betriggered by the System Operator through alarm monitoring.

7) Camera Storage Support

Depending on camera/encoder capabilities, IP cameras and IP videoencoders shall be able to utilize internal or external storage areasto reduce and schedule bandwidth usage between the camera and

the LNVR. System Users shall be able to use camera memory torecord video-based on internal motion detection events, this videoshall then be transferred from the camera to the LNVR during ascheduled Time zone. This shall not prevent live video from beingviewed from the camera on demand by the System Operator. TheSystem Operator shall also be able to request to view video thathas yet to be transferred and is still on the cameras memory. Thisinformation shall be presented as if it was recorded on the LNVR.

8) MJPEG to MPEG-4 Conversion

The LNVR shall allow System Operators the ability to change compatiblecameras from MJPEG to MPEG-4 while preserving the pre-established linksetup on that camera.

9) User Permissions for ViewableCamerasThe SYSTEM shall allow System Administrators to limit the maximum

number of viewable camera channels for a User.

10) Support for RTP Protocol

The SYSTEM shall support Real-time Transport Protocol (RTP) working inconjunction with RTSP. The System Operator shall be able to configurethe system to receive video




9/23

from RTP-enabled cameras. The following methods are supported by theSYSTEM: RPT via Multicast, RTP via RTSP, RTP via RTSP via HTTP, andRTP via UDP/IP.

f) IP Based Camera VideoSurveillance

The LNVR offers CUSTOMER an IP-based video surveillance only solution.The LNVR shall allow for camera and video encoder configuration andviewing of live video from industry standard IP cameras and IP encodersvia the System Administration and Alarm Monitoring applications.

The LNVR software shall be loaded on the SYSTEM AccessControl/Security Server to allow for the seamless integration of SYSTEMs

Total Security Knowledge Management product suite with industrystandard IP surveillance products. Customers shall be able to view videofrom many cameras simultaneously and only limited by frames per

second, image resolution, compression, network bandwidth and client PCcapabilities.The system shall support the use of IP based camera and IP encoderhardware for live (surveillance only) viewing through the AlarmMonitoring Application. The viewing of live video from thesecameras/encoders via the Alarm Monitoring Module shall be seamless tothe System Operator. Each IP camera/encoder shall be assigned a uniqueIP address so that users can use the SYSTEM to configure, view, andadminister each camera/encoder individually.IP cameras/encoders shall be treated exactly the same as their analogcounterparts except as noted below. IP cameras /encoders shall beaccessed directly from an embedded web server page located within the

camera/encoder. Access shall be by device IP address. Localcamera/encoder authentication shall be enforced to preventunauthorized access.Recording rates shall be equal to or less than the live video frames persecond (FPS) rate setting and shall stream from the LNVR unless therecorder is removed by network fault for a time period specified by theadministrator after which live video may be automatically streameddirectly from the camera for live viewing at a client workstation withinthe same network subnet.

g) IP Camera DiscoveryUtility

The SYSTEM shall provide an IP Camera Discovery Utility (UTILITY) forsearching and discovering IP cameras on a network, specifically for the

purpose of identifying the IP cameras IP addresses. The UTILITY shalldiscover devices in the local subnet as well as across the multiple subnetsconfigured on the network. The UTILITY shall be able to search anddiscover cameras produced by at least three (3) different cameramanufacturers.

h) DeviceLinkagesThe LNVR shall seamlessly integrate with the Access Control & Alarm

Monitoring System. Each access control field hardware device that isconfigured in the SYSTEM may be configured to be linked with acamera/encoder from the LNVR. A




10/23

camera/encoder shall have the ability to be linked with multiple accesscontrol hardware devices and an access control hardware device shallhave the ability to be linked with multiple cameras/encoders. An

unlimited number of access control hardware/device links shall beconfigurable.A video viewing priority shall be given to each access control hardwaredevice link. In the event that multiple cameras/encoders linked to asingle access control hardware device generate an alarm, thecamera/encoder with the higher priority will show in the Alarm MonitoringVideo Window first, followed by cameras/encoders with lower priority.

Each alarm/event condition shall have the ability to mark the start of avideo event or the end of a video event in real time. For example, whena door forced open is activated, the LNVR can mark the start of the video

event. When the door forced open restored alarm occurs, the LNVR canmark the end of the video event. For alarms that mark the start of thevideo event, a default Video Event Timeout shall be available that willend the video event in the case that a restored alarm does not occur orif there is no restored alarm for the event.System Administrators shall have the option for each alarm/event toautomatically launch the Digital Video Player at the Alarm Monitoringclient workstation when an alarm or event is generated. If an alarm isconfigured to automatically launch the Video Player, the system operatorcan configure it to launch recorded video in addition to live video. Thisfunctionality must be configured on each Alarm Monitoring workstation.

The LNVR shall support device linkage configuration setup wizard to

guide System Administrators through the configuration of the device-camera/encoder links. The setup wizard shall guide SystemAdministrators step by step by asking a series of questions that, whenanswered, will allow the LNVR to automatically configure device-cameralinks.

i) Purging

Each LNVR shall have the ability to be configured for purging lockedvideo events instead of archiving. In that case, the Archive Server shallsimply purge events from that LNVR rather than transfer them to thestorage volume. Event locking and purging is available for all LNVRs.

j) Video ViewingLayoutsThe Digital Video Management System (DVMS) shall provide a user the

ability to save the list of camera/encoders currently being played alongwith the currently selected template, if one is selected, under a layoutname provided by the user. The DVMS shall allow for user createdlayouts, single view, matrix view, and other preconfigured layouts toloaded as desired by the System User.




11/23

k) Browser Based VideoViewerThe SYSTEM shall provide a browser based video viewer option. The

SYSTEM shall automatically download and install any requiredcomponents directly onto the browser. The browser based video viewershall have the ability to select multiple view templates. This browserbased video viewer shall provide the following functionality:

1) Ability to be loaded on a PC through a web browser with minimaleffort2) Authenticate through a SYSTEM user account

3) Only SYSTEM authenticated users shall be able to access the video

over theHTTP protocol 4) Be limited to only viewing/controlling such video

as has been allowed by theSYSTEMs user permissions 5) Ability to view live and recorded

video 6) Log user transactions for accessing of video (Who, When,

What videosegments, PTZ) 7) Display live and recorded video from any

supported DVR or NVR 8) Receive live video from LNVR over

firewall friendly HTTP or HTTPSprotocol

9) Ability to view live video from a multiple number of channels over

HTTP10) See live video from cameras that support MPEG-4/MJPEG/H.264

format11) Ability to perform seeking operations on the recorded

videoa) Ability to perform seeking using the seeking slider bar, including

gotostart

b) Ability to change start/end time of the displayed video clip on

the flyc) Ability to change playback speed using

controlsd) Ability to synchronize selected camera cells to a single control

interface12) Ability to listen to the audio stream over the HTTP

protocol13) Digital zooming/panning

14) PTZ camera control

a) Relative Mode (Drag or double-click-to-center)




12/23

b) Mixed Mode (continuous or click-to-center)

c) Continuous Mode (click and hold to move)

15) Click to center

16) Export video

17) Monitor zones

18) Ability to access video from multiplerecorders

The browser based video viewer shall use an N-tier architecture.Browser based video viewer requires the use of Internet Explorer6.0 or 7.0 and 1024x768 resolution.

19) Limit the number of cameras a user is permitted toview20) Browser Based PTZ Locking

When a System User selects a cell that contains a PTZ camera theSYSTEM shall attempt to lock it to eliminate another System Userwith lower priority from taking control of the camera. To allow aSystem User with lower priority to use the PTZ camera the initialSystem User must unlock the PTZ camera.

l) AlarmMonitoringThe LNVR shall seamlessly integrate with the SYSTEM Alarm Monitoring

Module. Upon generation of an alarm that is configured to mark video,the System Operator shall be able to recall the video segment associatedwith the alarm. Once launched, the System Operator shall have theability to adjust the start and end time of the segment.

The SYSTEM Alarm Monitoring Module shall be able to save the list ofvideo windows, the video windows sizes, the video windows locations,and the all the selected camera options under a System Operatorsprofile. The next time the System Operator runs Alarm Monitoring thesame list of video windows, the video windows sizes, the video windowslocations, and the all the selected camera options shall be automaticallylaunched.

1) Real Time Monitoring

The LNVR shall allow monitoring of real time video from any AlarmMonitoring client workstation. The System Operator shall be able tomonitor any camera by using the System Hardware Status Treeand choosing the appropriate camera. Output of video for real timemonitoring shall be transferred to an Alarm Monitoring clientworkstation over the LAN/WAN.In the LNVR, authorized System Operators shall be able toconcurrently playback recorded video from any clip, even as thatvideo clip is being recorded. The Play




13/23

button shall enable System Operators to play back a single videosegment at the maximum recording configuration. The LNVR hasan integrated Matrix View which shall enable viewing of Live and

Recorded streams simultaneously. The Maximum displayableframes on a given client PC shall be determined by the resolution,compression, video type and PC specifications of the clientmachine. Benchmark data will be made available.

The SYSTEM shall monitor the firmware revision of the LNVR aswell as hard drive space percentage used. The DVMS shall supportthe automatic upgrade of firmware through the use of the SYSTEMscheduling mechanic.

2) Double Video On Alarm

The SYSTEM shall support the ability to have a SYSTEM

event/alarm trigger associated video to be displayed in two distinctcells. There shall be one cell for the live video and one cell for arecorded stream. The recorded stream shall be able to beconfigured to pause at alarm time or playback the pre-roll data.

This shall be configured on a per alarm basis.3) Multi-Camera Alarms

The LNVR shall provide the ability to launch more then one cameraon a triggered alarm if the device that triggered the alarm ismonitored by more then one camera, When the alarm is generatedthe DVMS shall launch a video window for each camera associatedwith the triggered device.

4) Playback ControlThe LNVR Playback Control shall offer the following features for fullSystem Operator control of video playback:

a) Start and Stop Playback

During operation of the viewer application, theauthorized System Operator shall be able to start andstop playback. This operation shall not affect any otheroperation.

b) Pause and Resume

During playback of video, the System Operator shall beable to pause and resume current playback. Thisoperation shall not affect any other operation.

c) Fast Forward

During playback of video, the System Operator shall beable to use the Fast Forward button to view theplayback at faster than normal speed. This operationshall not affect any other operation.




14/23

a. Skip Backward

During playback of video, the System Operator shall be

able to use the Skip Backward button to rewind theplayback. This operation shall not affect any otheroperation.

d) Frame Advance

During playback of video, the System Operator shall be able touse the Frame Advance button to advance the video clip oneframe at a time. This operation shall not interfere with any otheroperation.

The System Operator shall also have the ability to switchbetween other cameras if the device that generated the eventhas more than one camera associated with it. The System

Operator shall have the ability to adjust the start and end timesof the video segment once the video segment is displayed. TheSystem Operator shall also have the ability to adjust theplayback speed of the video segment from slower than normalto real time to high speed playback.The System Operator shall have the option to switch to LiveMode from a camera at any time during the operation. TheSystem Administrator shall also have the ability to load anyvideo file from a backup device into the digital video player atany time.

The digital video player shall be user configurable to show thedate and time of the video clip frame, as well as the currentmode of the player (play or live).

The System Operator shall have the ability to display or notdisplay the informational text.

The digital video player shall also have the option toautomatically launch upon a critical alarm occurring in theSYSTEM to show live video at the video camera linked to thathardware device.

5) Video Player

The Video Player shall support an advanced Matrix View of On-linecamera views. The frame rate limitation shall be any combinationof live or recorded video. The number of video streams in the

matrix is dependent on the frame rate and resolution of thecameras/video clips being requested and the hardware of the clientviewing PC. Benchmark data must be available from themanufacturer on select PC platforms. The Matrix view shall allowthe sizing of the matrix windows.

6) Two-Way Audio

The Alarm Monitoring client shall support a dialog that will enableaudio communication to and from audio enabled IP video sources.

The user shall be able to manually send voice or saved audio filesto the audio enabled IP video




15/23

source to be played through the devices speaker. The users shallalso be able to hear audio from the audio enabled IP videosources microphone. The SYSTEM shall only support audio

protocol G.711.7) Pan/Tilt/Zoom Control from AlarmMonitoring

The LNVR shall support pan/tilt/zoom (PTZ) controls from the AlarmMonitoring Workstation using a PC mouse, USB direct playcontroller device (joystick) or RS-485 device. The PTZ control shallbe supported in conjunction with IP PTZ cameras. Supportedcommand settings shall be available for:

1. Pan Left 7. Focus Near

2. Pan Right 8. Focus Far

3. Tilt Up 9. Iris Open

4. Tilt Down 10. Iris Close

5. Zoom In 11. Go to Preset

6. Zoom Out 12. Stop PTZ Movement


16/23

8) Addition Pan/Tilt/ZoomFeatures

The DVMS shall support the use of pan/tilt/zoom (PTZ) securityand priority levels. The following features outline the increasedsecurity to the Digital Video PTZ control.

a) Priority Levels

The DVMS shall support priority levels used in conjunctionwith PTZ control. The DVMS shall contain a user friendlycheck box system to denote a System Operators ability tocontrol PTZ cameras. The DVMS shall also contain an editbox that will allow the System Administrator to assign PTZpriority levels. These two features shall be used to allow onlySystem Operators with the appropriate permission levels theability to take control of PTZ cameras.b) Device Group Control

The DVMS shall provide the ability for SystemAdministrators to limit the System Operators access tocertain camera device groups.

c) PTZ Override Control

The DVMS shall allow a System Operator who is controllinga PTZ camera the ability to temporarily lockout otherSystem Operators, with lower priority levels, fromcontrolling the same PTZ camera. The DVMS



shall also provide a timeout feature that will unlock the PTZafter aSystem Administrator assigned amount ofinactivity.

d) Proportional PTZ Control

The DVMS shall provide PTZ control that is proportional tothe view of the camera. This proportional control shall takethe current zoom position into account. For example, if thecamera is zoomed in, a mouse click will cause a slowermovement then if the camera was zoomed out and thesame mouse click occurred.

e) Matrix View PTZ Accessibility

The DVMS shall allow System Operators the ability to

double click on a single video in matrix mode to launch anew single video window. The new window shall have PTZenabled automatically.

f) Preset Alarm Actions

The DVMS shall store the priority level of the SystemOperator who creates the preset alarm action and will usethat priority when issuing the go to preset PTZ command.

g) System User ConfiguredPresets

The DVMS shall allow System Operators the ability to recordthe current PTZ location, absolute, pan, tilt, and zoompositions, under a user defined name. The System Operatorwill then be able to bring up the preset camera location byselecting the user defined name from a drop down list.

h) Preset Tour

The DVMS shall support the ability to record a set of PTZcommands and save them under a user-definable tourname. The System Operator will then be able to select thetour name to have these commands repeated at a futurepoint in time. The DVMS must be able to record the order of

each command as well as the timing of each command. TheDVMS shall be able to conduct multiple Preset Tours withoutclient applications running through the use of a dedicatedservice to control the tours.9) Video Camera Groups/Video CameraTours

The DVMS shall support camera grouping to allow for video cameratours to occur in the SYSTEM Alarm Monitoring Module.




17/23

An unlimited number of camera groups shall be supported in theSYSTEM and each camera group shall support an unlimitednumber of cameras. Cameras within a camera group shall span

multiple Digital Video Recorders. Cameras shall have the ability tobe placed into multiple camera groups.Once grouped, the System Operator shall be able to start a videocamera tour that shall rotate live video between each of thecameras defined in the video camera group at a user definedincrement. The time increment between switching cameras shallbe user definable in one second increments.

10) Still Image Capture

During playback or monitoring of video, the System Operator shalluse the Pause button followed by selecting Enhance Image fromthe Options Menu to create a still picture. This operation shall not

affect any other operation and shall not alter the recorded video.

11) Still Image Save

The captured image Export button shall allow System Operators tosave single video frames to the client workstation hard drive in astandard file format. The System Operator shall be able to later e-mail, print, or transfer the file to any other media.

12) Export Video Clip toFile

The System Operator shall have to ability to save and export

recorded video to a file for the purpose of sharing and reviewingvideo clips. The start and end times for each video segment shallbe determined by the System Operator. The exported video clipshall be viewable via a standard Windows media player or via avideo player provided by Manufacturer. Optional Time, DateStamp, and User Defined text shall be able to be overlaid onto thevideo during export using an optional transparency level.

13) Video ImageProcessing

The DVMS shall support video image processing of a single framecaptured image through use of an image processing module. Theimage processing module shall show both the original captured

image side by side next to the processed image. The followingeffects shall be available to System Operators to apply to anoriginal captured image in any combination desired:

1) Intensity - Increases or decreases the overall intensitylevel of the light in the image. Adjusts the brighter areas bymaking them brighter or darker.

2) Contrast - Increases or decreases the range of graylevels contained in the image. It adjusts the distinctionbetween the lightest and darkest tones in the image.


OnGuard



18/23

3) Saturation - Adjusts the purity of color (the number of

colors used to create a particular color).

4) Gamma Correct - Enhances detail in the image byadjusting the middle tones without affecting the darkest and

lightest areas.5) HistoContrast - Adjusts the number of pixels per graylevel to create a linear relationship between gray levels,used to bring out the detail in dark areas of the image.

6) Hue - Adjusts the main characteristic of a particularcolor that distinguishes it from other colors.

7) HistoEqualize - Redistributes shades of colors to adjustimbalances. It makes the darkest colors black and thelightest colors white and stretches the colors in-between.

8) Flip - Flips the image horizontally (the image will

appear upside down).

9) Reverse -Flips the image vertically, creating a mirror

image of the original.

10) Rotate - Rotates the image 0-360

degrees.11) Shear - Applies the look of three-dimensionality to the

image, while maintaining the original size and shape.

12) Add Noise - Creates a granular effect that adds texture

to a flat or overly blended picture.

13) Average - Converts each pixel in the image to the

average of itself and the pixels to the right and bottom,

resulting in a blurring of the image.14) Sharpen - Enhances the edges and brings out the

detail.15) Halftone - Converts the image to a black and white (1bit/pixel) image in which different shades of gray (luminance)are represented by different patterns of black and whitepixels.16) Median - Reduces the amount of graininess (noise) in animage.17) Emboss - Converts the image to a raised relief style with its

lightsource directed from the top left.18) Gray Scale - Represents the image using up to 256 shades

of gray.19) Invert - Inverts the colors in the image as on a photographic

negative.20) Mosaic - Converts the image to a grid of square blocks of

color.21) Posterize - Reduces the color resolution, which is the number ofshades of color that shall be displayed

simultaneously.


OnGuard



19/23

The DVMS shall allow for the System Operator to save anycombination of effects as a profile to be used on other still imagesfor image processing. Profiles shall have the ability to be added or

deleted from the SYSTEM at any time.14) Resizable Video WindowFunction

During playback or monitoring of video, the System Operator shallbe able to enlarge the size of the video screen to twice therecorded resolution to have video display larger on the monitorscreen. This operation shall not affect any other operation. TheUSER shall have the option to monitor the video at any userspecified size with out maintaining aspect ratio.

15) Video Validation

The LNVR shall detect video loss from any or all cameras. If a

camera stops transmitting video or the BNC cable from a camerato the video recorder is disconnected or malfunctions, the videorecorder supervision shall detect the video loss and will alert theSystem Operator via the alarm monitoring client workstationwindow, audible alarm, visual alarm, or pager can be optionallyset. 16) Dual Path Failover and

RedundancyThe LNVR shall support the ability to configure a second location(or path) for an IP camera or IP encoder to failover in the eventthat the primary LNVR fails. For example, if the system iscomprised of two 16 channel LNVRs and one of the LNVRs shouldfail, the cameras that normally record to it will failover and begin

recording to the second LNVR. This failover will be seamless to theSystem Operator. The failover shall occur in less than 60 secondsfrom the time the primary recorder goes offline, thus minimizingthe loss of video during the failed condition.

The second location may also be configured as a redundantrecording location. In this mode two (2) copies of the video datawill exist, one at each location.In the event of a primary recorder failure, the SYSTEM shallautomatically route video from the appropriate source to any openclient connections without user intervention. This shall work forLive and Recorded video playback.Channel alarms such as Motion Detection will be masked from the

secondary recorder unless the primary recorder fails. Alarms fromthe secondary recorder will be visibly marked as secondaryrecorder alarms.

17) Analog PTZ Camera Support via IPEncoders Units

The LNVR shall integrate the video encoders ability to support aspecific set of analog PTZ cameras. These analog cameras areconverted to digital using the video encoders and are thencontrolled in the same method as other IP/Network cameras in thesystem.




20/23

18) Presets on Alarm

The LNVR shall integrate presets that are called based on alarm

conditions. Each event/alarm in the SYSTEM shall be able to beassigned to a preset on the camera.

The DVMS shall have the ability to record video based on motiondetection of the camera. The times that motion detectionrecording occurs shall be user definable on a time zone basis. Eachcamera shall have the ability to have a separate time zone andmotion detection settings if desired. Areas of the video pictureshall be configured to monitor motion. Motion in these areas shallgenerate alarms.19) Event Locking

The LNVR shall have a clip-lock option to prevent overwriting of

specific video clips regardless of their date and time. Eachevent/alarm in the system has the ability to be locked and/orunlocked by appropriately permissioned users.

20) UNC Path Support

The LNVR must be able to support Network Attached StorageDevices/Storage Architecture. This means for the storage path,you must be able to input a UNC path to write to instead of a harddrive letter.

21) Blind Camera Alarm

The LNVR shall support the blind camera alarm. If for example,

someone places something over the lens of the camera, theSYSTEM shall generate a blind camera alarm in Alarm Monitoring.

22) Configuration of Off-lineCameras

The System Administrator shall be able to mark a camera offline bymarking a check box in the camera configuration tab. Access tothis feature shall be based on System Administrator privileges,username and password. The ability of generating a report on thetime, camera, recorder, and user who marked a camera offlineshall be supported.

23) Video Capture On Event

The DVMS shall support the ability to capture (record) video onlywhen an event occurs. The System Administrator shall be able toconfigure devices to trigger the recording of events. The eventshall be trigged by either camera inputs, cameras motiondetection, or other events configured within the SYSTEM.

24) Camera Time Stamps




21/23

The LNVR, by default, must provide time stamps at the time thevideo is received. This shall enable the use of time stampsgenerated by the camera for other purposes.

25) Automatic IP Camera passwordchange

The DVMS shall support the ability for automatic changes to thepasswords for both IP cameras and IP encoders.

26) Optionally set the Browser-Based Video ViewingClient to be Default Player

The DVMS shall support the ability to choose whether the standardplayer interface included in the main Alarm Monitoring client or theBrowser-Based video viewing client is the default. If the browserbased video viewing client is the default, when launching video fromthe main Alarm Monitoring client, a browser will be launched andcapable of automatically logging in a displaying the requested videothrough the browser.

m) Intelligent Motion VideoSearchingThe DVMS shall support advanced automated motion video searching

against prerecorded video. The automated motion video search shallanalyze frames in a pre-configured video segment polygon to detectmotion activity from image to image. It shall display thumbnail images ofthe frames with activity, complete with a histogram depicting the relativeamount of activity within each frame. System Operators shall be able toperform this search by selecting a specific camera and a specific timeperiod in which the suspected activity took place. The DVMS SearchMechanism shall then locate all motion events associated with thatcamera and time period and display them in trace format or bythumbnail format. The System Operator can then select the event orthumbnail and the system shall automatically begin playing the motionevent. The System Operator shall then be able to view each of theindividual events through the camera video window.n) Video

Export The DVMS shall be able to export user selected video clips to theindustry standard .ASF format for viewing in industry standard videoviewers such as Microsoft Windows Media Player format. The SystemOperator shall be able to add text to the clip as well as be able to modifythe color, size and position of the font. The System Operator will be ableto position the time/date stamp as well as modify the color, and size ofthe font.The video clip may be sent via email, burned to disc or stored on adirectory. The recipient will have the ability to view video without theneed for having the SYSTEM Client software installed on their PCmachine.




22/23


23/23


OnGuard


The System Operator shall be able to configure the Remote Monitor torun in full screen mode.

The System Operator shall be able to load saved video layouts directlyto a Remote Monitor Instance.

The System Operator shall be able to select various VideoQuality Enhancement (VQE) algorithms that will improve the viewingquality of specified video channels on the client viewing station.

The System Operator shall be able to select the "Fog Removal"algorithm. The System Operator shall have improved video as fogin the foreground shall be diminished.

The System Operator shall be able to select the De-Interlacingalgorithm and the artifacts affects of compression and interlacingshall be diminished.

The System Operator shall be able to select the sharpen algorithmand a camera view which is blurred shall be diminished.

The impact on the above three VQE algorithms shall only impactthe workstation in which the changes were made and shall notimpact recorded video or other workstation viewing of the video.

Technical & Functional

Documents

Transcript of Technical & Functional