TheIndependent

LNVR shall be
camera
able to
setup
store
forrecorded
frame rate,
video
resolution,
on any industry
compression
standard
5. storage
Digital Videoas
rate, brightness,
medium, Management
contrast
long asanditother
meets (With
factor Lenel
thesetups. Network
Manufacturer’s
This architecture
minimum
Videoa) Recorders)
specification.
shall allow System
The userAdministrators
shall be able to
tooptimize
choose camera-recording
the appropriate storage
medium
settings.
Overview for Each
their camera
application, shallsuchhaveas thea ability
hard diskto be storage
set to operate
array, storage
with a
The
area Digital
different
network, Video
frame Management
or network
rate, resolution,
attached System (DVMS)rate,
compression
storage. shallbrightness,
be available as a
contrast
standalone
TheandLNVR other solution
shall provide
factor or
setups. as an integrated solution that
a fully modular architecture that offers upgrades is seamlessly
integrated
in-place for with other
additional
Total system solution to enable Total
recording Security
capacityKnowledge
and shall
enterprise-wide, Management
continuously
networked, Solution
record
multi-user
Modules,
up to an including
unlimited Access
number Control
of video
access to all system resources via a wide range of options for & Alarm
sources. Monitoring,
The LNVR Asset
shall
Management,
simultaneously
connectivity with Credential
record Management,
thevideo/audio,
customer’s existing and
display live Visitor
LAN video/audio,
and WAN. Management.
and display All
functionality
recorded
Scalable, described
video/audio.
yet compact from
None system this
of the point
video
design forward shall
operations
that offers modular reflect functionality
shall interfere
expansion with
to
of the
the seamlessly
other. Recording integrated
protect CUSTOMER investment. shall notsystem.
stop The
playback,DVMS shall
live work
viewing, inorconjunction
storage of
with
video. a Manufacturer Network Video Recorder
Independent camera setup configurations for pre-event, event, and (LNVR)
The LNVR
The LNVR shall shall not utilizeevent-based
support any multiplexer-type
recording technology forrecord
video
post-event states shall be available. User shall be and/or shall
able to determine
recording.
continually Information
24 hours supplied from IP camera sources via Ethernet shall
independent framearate day. The amount
settings for these of states.
local online storage camera
Independent that is
be digitally
available for recorded
playback simultaneously
from the LNVR to a LNVR.
shall be The
dependantLNVR shall
on support
the size a
of
setup configurations for time-lapse mode shall be available.
variety
the hard of industry in standard
drive camera the LNVR IP Cameras from multiple manufacturers.
Independent setup or other storage
configurations for medium
live versus asrecorded
well as the
individual camera configuration (FrameshallRate, Resolution, Compression).
Theplayback
The LNVR
LNVR shall shall
shall be be available.
available
support in User
a Turnkey
Multicast-streaming be able
Solution to as
technology determine as adifferent
wellwhereby, Software
once
Onlyframe rate settings
In a for
Software live
Onlyviewing and
version, recorded
one user has requested a live video stream other system users shall the
version. users shall playback.
be able to load be
LNVR to
able software
view onto the samean industry videostandard
stream PC platform
without of theira choice,
opening separate as
long as it meets the Manufacturer’s minimum
connection. Multicast streaming technology helps limit the amount of specifications.
bandwidth required for system operation/monitoring.
The
The Turnkey
LNVR shall Solution
support shallUnicast-streaming
also be available technologyin a hybrid whereby configuration,each
allowing for the unit to record video
request for recorded video will require a separate stream. from both IP and analog source
video inputs. The analog sources shall be supported by video capture
The
board LNVR
options:shall support the limiting of frames per second to individual
clients. This 1) shall MPEG4:
be mutually8-Channel Video with
exclusive Board the(up to 2 boards per
Multicast-streaming
technology. chassis) which supports 8 channels at 3.75fps (NTSC) at 640 x
While the LNVR 240 (640 is continuously
x 480 interlaced) recording or archiving
resolution; or 8 video,
channels an unlimited
at 7.5fps
number of (NTSC) authorized at 320System x 240 Operators
resolution. shall access video
8 channels from a(PAL)
at 3.7fps centralat
archive server 640 xfrom 240 client
(640 xworkstations
480 interlaced) connected
resolution; to theor 8 data network
channels at
(via a LAN 6.2fpsor WAN connection).
(PAL) at 320 x 240 Up to 32 simultaneous System Operators
resolution.
shall access live or recorded video from a LNVR. Using a centralized
2)
system administration MPEG4:tool, 4-Channel 30fps Video
user defined profilesBoard (upeach
restrict to 4 System
boards
Operator’sper chassis)
security which to
access allows simultaneous
specific video andrecording to specific of upsystem
to 16
high motion cameras. Each camera
operations, such as video monitoring, playback, adding, modifying, and may record at 30fps,
A user-friendly
deleting 15fps, database
cameras. 7.5fps, 2fps, query tool (NTSC)
or 1fps shall enable
and 25fps, authorized
12.5fps,System6.2fps,
Operators 2fps, to quickly
or 1fps locate(PAL). video fromcan
These anyberecorder
at 320x240, and transparently
640x480 or
play it back. The SYSTEM shall enable CUSTOMER to use off the shelf
720x480.
3)
video enhancement H.264: 16-Channel
software. These FULLimageframe enhancementrate High kitsResolution
allow the
System Operator to enhance a single video capture frame. of
Video Board, which allows simultaneous recording Theup single
to 16
captured frames high motionshall be cameras.
a copy Each of thecamera
originalmay recordvideo.
recorded at 1/16, 1/8,
System
1/4, 1/2, 1, 2, 4, 6, 8, 10,
Operators cannot alter the original recorded video in any way. The LNVR12, 15, 16, 18, 20, 22,
30(NTSC)/25(PAL). Resolutions
shall come with an image enhancement tool that shall be built into the will support, NTSC:
The design
digital video ofplayer
the LNVR
352*240(CIF), (DVP). shall be flexible and
704*240(2CIF), allow for the following:
528*320(DCIF), 704*480(4CIF);
PAL: 352*288(CIF), 704*288(2CIF), 528*384(DCIF),
704*576(4CIF).

LENEL
LENEL -- A
A UTC
UTC FIRE
FIRE && SECURITY
SECURITY COMPANY
COMPANY
® ®
OnGuard
Functional
OnGuard Functional Specifications
Specifications Version
Version 6.3 Series
6.3 Series PagePage
115116
 b) Network
TheInterface
LNVR shall connect to an existing network. Various types of network
architectures shall be supported including Ethernet 100BT and 1 Gigabit
Ethernet. Various types of network protocols shall be supported including
TCP/IP, IPX, and UDP.
The network interface shall allow remote access of the recording system
from various System Configuration and Alarm Monitoring client
workstations located throughout the customer's facility.

Playback Over the LAN/WAN

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

c) Seamless Integration with Total Security Knowledge

Management Modules
1) Seamless Integration with Access Control and
Alarm
The LNVR shallMonitoring
seamlessly integrate with the Access Control &
Alarm Monitoring System. Any alarm/event in the SYSTEM shall
have the ability to be associated with a digital video clip in real
time. Each alarm/event in the SYSTEM shall store a pre-defined
number of seconds of video before the event occurred and a pre-
defined number of seconds of video after the event occurred. This
video clip shall be retrieved at any system Alarm Monitoring client
workstation.
LENEL - A UTC FIRE & SECURITY COMPANY
®
OnGuard Functional Specifications Version 6.3 Series Page 117
 The same database MUST store information from both the LNVR
and the Access Control & Alarm Monitoring System. A separate
database for the two systems is unacceptable.

2) Seamless Integration with Asset

Management
The LNVR shall seamlessly integrate with the Asset Management
System. Any asset alarm/event in the SYSTEM shall have the ability
to be associated with a digital video clip in real time. Each
alarm/event in the SYSTEM shall store a predefined number of
seconds of video before the event occurred and a pre-defined
number of seconds of video after the event occurred. This video
clip shall be retrieved at any system Alarm Monitoring client
The same database MUST store information from both the LNVR
workstation.
and the Asset Management System. A separate database for the
two systems is unacceptable.
3) Seamless Integration with ID Credential
Management
The LNVR shall seamlessly integrate with the ID Credential
Management System. Any ID Credential Management or cardholder
alarm/event in the SYSTEM shall have the ability to be associated
with a digital video clip in real time. Each ID Credential alarm/event
in the SYSTEM shall store a pre-defined number of seconds of video
before the event occurred and a pre-defined number of seconds of
video after the event occurred. This video clip shall be retrieved at
any system Alarm Monitoring client workstation.
The same database MUST store information from both the LNVR
and the ID Credential Management System. A separate database
for the two systems is unacceptable.

4) Seamless Integration with the Visitor

Management
The LNVR shall seamlessly integrate with the Visitor Management
System. Any Visitor Management cardholder alarm/event in the
SYSTEM shall have the ability to be associated with a digital video
clip in real time. For each Visitor alarm/event in the SYSTEM shall
store a pre-defined number of seconds of video before the event
occurred and a pre-defined number of seconds of video after the
event occurred. This video clip shall be retrieved at any system
Alarm Monitoring client workstation.
The same database MUST store information from both the LNVR
and the Visitor Management System. A separate database for the
two systems is unacceptable.
d) Manufacturer Network
Recorders
The Manufacturer Network Video Recorder (LNVR) main storage medium
shall be a digital hard drive. All video information can be stored on the
LNVR internal hard drive for immediate playback. The hard drive shall
work in a FIFO (First In First Out) mode to allow new video clips to
overwrite old clips. The LNVR shall be able to be configured to
LENEL - A UTC FIRE & SECURITY COMPANY
®
OnGuard
Functional Specifications Version 6.3 Series Page 118
only store video for a user definable number of days. Any recorded video
older then the user defined number of days shall not be available for
either 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 system
shall support the use of the Nexsan ATAboy 2 (IDE/ATA Drives) unit,
Nexsan SATABoy (iSCSI/SATA Drives), Nexsan SATABeast (Fibre/SATA
Drive). In all cases, initial system configuration shall take place via the
respective third party software. However, system function thereafter
shall be seamless to the user.
The LNVR shall communicate with the SYSTEM Alarm Monitoring and
System Administration client workstations over the CUSTOMER network
or a private security network. The LNVR shall support networks such as
Ethernet 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 light
cameras.
Each LNVR shall have the ability to be given a realistic name of up to 32
alphanumeric characters and shall have the ability to be marked on-line
or off-line. Each LNVR shall be given a workstation name as well as an IP
address of where the LNVR is connected to the network. Each LNVR shall
also have a World Time Zone setting to allow LNVR to reside in different
areas of the world.
Should the LNVR go offline, a specific alarm will be sent to Alarm
Monitoring. 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 shall
no longer display.
The SYSTEM shall allow an operator to view the available storage and
performance information directly from the configuration of the camera.
This shall include the available storage, resource usage and recording
rates for the network video recorder. Threshold alarms shall also be
configurable when the amount of available storage falls below a set
number of days.
The Turnkey LNVR shall be available in the following
configurations:
1) LDVR/UVS Extended Storage Chassis (DVC-EX1),
shall include 3U, 19-inch rack mount chassis with Intel P4
3.0GHz single core CPU, 1GB 533MHz RAM, Windows XP
Professional operating system, Dual 10/100/1000
Ethernet ports, one 80GB OS only hard drive, UP TO 8
data hard drives – KIT OPTIONS AVAILABLE, DVD/CD ROM,
mouse and rack mount rail kit.
2) Premium Extended Storage Chassis (DVC-EX2), shall
include 3U, 19-inch rack mount chassis with Intel Core 2
Duo E8400 3.0GHz dual core CPU, 2GB 667MHz RAM,
Windows XP Professional operating system, Dual
10/100/1000 Ethernet ports, one 80GB OS
LENEL - A UTC FIRE & SECURITY COMPANY
®
OnGuard Functional Specifications Version 6.3 Series Page 119
 only hard drive (UP TO 8 data hard drives – KIT
OPTIONS AVAILABLE), DVD/CD ROM, mouse and rack
mount rail kit.
3) LNVR Low Profile Storage Chassis (DVC-1U), shall
include 1U rack mount chassis with Intel Xeon x3230
2.66GHz quad core CPU, 2GB 533MHz RAM, Windows XP
Professional operating system, Dual 10/100/1000 Ethernet
ports, one 80GB OS only hard drive (UP TO 3 data drives –
KIT OPTIONS AVAILABLE), CD/RW-DVD/R, mouse and rack
mount rail kit.
4) 2U Standard Chassis (DVC-2U), shall include 2U, 19-
inch rack mount chassis with Intel Celeron D E1400
2.0GHz dual core CPU, 1GB 667MHz RAM, Windows XP
Professional operating system, 10/100/1000 Ethernet
port, one 80GB OS only hard drive (UP TO 4 data hard
drives – KIT OPTIONS AVAILABLE), DVD/CD ROM, mouse
and rack mount rail kit.
e) Digital Video
Cameras1) Individual Camera Input
Setup
Each digital video camera or video encoder shall be independently
configured to record digital video.

Each camera shall have the ability to be given a realistic name of

up to 32 alphanumeric characters and shall allow for the setup and
adjustment of brightness, contrast, archiving, motion detection,
Pan/Tilt/Zoom, on a per camera basis.

The SYSTEM shall recognize the LNVR and channel that the camera
is connected. System Administrators shall define whether each
camera allows Pan/Tilt/Zoom commands to be accomplished from
the Digital Video Player.
The LNVR shall support multiple network enabled Video Cameras
and Video Encoders. The Video Encoder technologies shall allow
the LNVR to interface with analog and PTZ cameras. The LNVR
shall support the following video formats simultaneously on the
same system:
1) MJPEG

2) MPEG-4

3) H.264

The LNVR shall support both formats simultaneously on the same

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

LENEL - A UTC FIRE & SECURITY COMPANY

®
OnGuard Functional Specifications Version 6.3 Series Page 120
 576 PAL), VGA (640 x 480) and mega-pixel resolutions. These
resolutions shall be dependent on the network enabled video
device. Each camera and video encoder shall have recording
settings to customize the recording properties of the camera
including:
1) Compression – The compression of video input used by
the particular encoder (MJPEG, MPEG-4, H.264) depending
on camera type.
2) Resolution – The size of the image expressed in pixels.
(example: 320 x 240, 640 x 480) This shall depend on the
type of camera or video encoder.

3) Frame rate – The number of frames per second the

network enabled video camera or video encoder transmits a
video stream to the LNVR.
4) Pre-Roll - The number of seconds of video that the
LNVR will store previous to the event time that a linked
event is generated. This time is specific to the associated
event. The SYSTEM shall support up to 900 seconds of pre-
roll.
2) Post-Roll - The number of seconds of video that the
LNVR will store after a linked event is generated. This time is
specific to the associated event.

2) Generate Motion Detection

Alarms
If supported by the camera or video encoder, each camera or
video encoder shall have the ability to record video to the LNVR
based on motion detection at the camera or video encoder. The
times that motion detection recording occurs shall be user defined
by time-zones. A sensitivity bar shall be available to adjust the
sensitivity for motion in the cameras. If supported within the
camera or video encoder, each camera shall have the ability to
have a separate time zone and motion detection settings if
desired. Areas of the video picture shall be configured to detect
3)Motion
motion. Time-Lapse
in these areas shall generate alarms.
Recording
The LNVR shall allow the ability to configure time-lapse recording
on a “by camera” or video encoder basis. System Administrators
shall have the ability to configure cameras or video encoder to
record one frame of video every (x) seconds (2-3600 seconds)
when there is no motion in the viewing area. Once motion is
detected, the LNVR shall automatically increase recording rate to a
predefined frame rate, or can simply always record at the time-
lapse rate. The LNVR shall also be able to use an event from other
integrated SYSTEM modules to start recording at the increased
frame rate.

LENEL - A UTC FIRE & SECURITY COMPANY

®
OnGuard Functional Specifications Version 6.3 Series Page 121
 4) Audio Support
The LNVR shall support unidirectional and, if supported by the
camera or video encoder, synchronized audio recording through
cameras or video encoder that support this option. The ability to
record synchronized audio and video shall be enabled through and
stored in the LNVR. The audio shall be available for both recorded
video and live video playback. The audio shall be exclusively
available for recording purposes. The SYSTEM shall only support
audio 5) Firmware
protocol downloads
G.711.
Select cameras and video encoders shall have the ability to receive
automatic firmware downloads. These automatic firmware
downloads shall be scheduled through the use of the SYSTEM
Scheduling mechanism.
6) Dry Contacts
The LNVR shall support both inputs and outputs that are provided
by cameras or video encoder. The LNVR shall monitor the camera’s
inputs and upon state change, shall report an alarm to the
SYSTEM. Outputs shall be available for linkage through the Global
I/O feature of the SYTEM. These outputs shall also be able to be
triggered by the System Operator through alarm monitoring.
7) Camera Storage Support
Depending on camera/encoder capabilities, IP cameras and IP video
encoders shall be able to utilize internal or external storage areas
to reduce and schedule bandwidth usage between the camera and
the LNVR. System Users shall be able to use camera memory to
record video-based on internal motion detection events, this video
shall then be transferred from the camera to the LNVR during a
scheduled Time zone. This shall not prevent live video from being
viewed from the camera on demand by the System Operator. The
System Operator shall also be able to request to view video that
has yet to be transferred and is still on the camera’s memory. This
information 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 compatible
cameras from MJPEG to MPEG-4 while preserving the pre-established link
setup on that camera.
9) User Permissions for Viewable
The SYSTEMCameras
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 in

conjunction with RTSP. The System Operator shall be able to configure
the system to receive video
LENEL - A UTC FIRE & SECURITY COMPANY
®
OnGuard
Functional Specifications Version 6.3 Series Page 122
from RTP-enabled cameras. The following methods are supported by the
SYSTEM: RPT via Multicast, RTP via RTSP, RTP via RTSP via HTTP, and
RTP via UDP/IP.
f) IP Based Camera Video
TheSurveillance
LNVR offers CUSTOMER an IP-based video surveillance only solution.
The LNVR shall allow for camera and video encoder configuration and
viewing of live video from industry standard IP cameras and IP encoders
via the System Administration and Alarm Monitoring applications.

The LNVR software shall be loaded on the SYSTEM Access

Control/Security Server to allow for the seamless integration of SYSTEM’s
Total Security Knowledge Management product suite with industry
standard IP surveillance products. Customers shall be able to view video
from many cameras simultaneously and only limited by frames per
second, image resolution, compression, network bandwidth and client PC
The system shall support the use of IP based camera and IP encoder
capabilities.
hardware for live (surveillance only) viewing through the Alarm
Monitoring Application. The viewing of live video from these
cameras/encoders via the Alarm Monitoring Module shall be seamless to
the System Operator. Each IP camera/encoder shall be assigned a unique
IP address so that users can use the SYSTEM to configure, view, and
administer each camera/encoder individually.
IP cameras/encoders shall be treated exactly the same as their analog
counterparts except as noted below. IP cameras /encoders shall be
accessed directly from an embedded web server page located within the
camera/encoder. Access shall be by device IP address. Local
camera/encoder authentication shall be enforced to prevent
Recording
unauthorizedrates shall be equal to or less than the live video frames per
access.
second (FPS) rate setting and shall stream from the LNVR unless the
recorder is removed by network fault for a time period specified by the
administrator after which live video may be automatically streamed
directly from the camera for live viewing at a client workstation within
the same network subnet.
g) IP Camera Discovery
TheUtility
SYSTEM shall provide an IP Camera Discovery Utility (UTILITY) for
searching and discovering IP cameras on a network, specifically for the
purpose of identifying the IP cameras’ IP addresses. The UTILITY shall
discover devices in the local subnet as well as across the multiple subnets
configured on the network. The UTILITY shall be able to search and
discover cameras produced by at least three (3) different camera
manufacturers.
h) Device
TheLinkages
LNVR shall seamlessly integrate with the Access Control & Alarm
Monitoring System. Each access control field hardware device that is
configured in the SYSTEM may be configured to be linked with a
camera/encoder from the LNVR. A

LENEL - A UTC FIRE & SECURITY COMPANY

®
OnGuard
Functional Specifications Version 6.3 Series Page 123
camera/encoder shall have the ability to be linked with multiple access
control hardware devices and an access control hardware device shall
have the ability to be linked with multiple cameras/encoders. An
unlimited number of access control hardware/device links shall be
configurable.
A video viewing priority shall be given to each access control hardware
device link. In the event that multiple cameras/encoders linked to a
single access control hardware device generate an alarm, the
camera/encoder with the higher priority will show in the Alarm Monitoring
Video Window first, followed by cameras/encoders with lower priority.

Each alarm/event condition shall have the ability to mark the start of a
video event or the end of a video event in real time. For example, when
a 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 can
mark the end of the video event. For alarms that mark the start of the
video event, a default Video Event Timeout shall be available that will
end the video event in the case that a restored alarm does not occur or
if there is no restored alarm for the event.
System Administrators shall have the option for each alarm/event to
automatically launch the Digital Video Player at the Alarm Monitoring
client workstation when an alarm or event is generated. If an alarm is
configured to automatically launch the Video Player, the system operator
can configure it to launch recorded video in addition to live video. This
functionality 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 System
Administrators step by step by asking a series of questions that, when
answered, will allow the LNVR to automatically configure device-camera
links.
i) Purging
Each LNVR shall have the ability to be configured for purging locked
video events instead of archiving. In that case, the Archive Server shall
simply purge events from that LNVR rather than transfer them to the
storage volume. Event locking and purging is available for all LNVRs.

j) Video Viewing
Layouts
The Digital Video Management System (DVMS) shall provide a user the
ability to save the list of camera/encoders currently being played along
with the currently selected template, if one is selected, under a layout
name provided by the user. The DVMS shall allow for user created
layouts, single view, matrix view, and other preconfigured layouts to
loaded as desired by the System User.

LENEL - A UTC FIRE & SECURITY COMPANY

®
OnGuard
Functional Specifications Version 6.3 Series Page 124
 k) Browser Based Video
Viewer
The SYSTEM shall provide a browser based video viewer option. The
SYSTEM shall automatically download and install any required
components directly onto the browser. The browser based video viewer
shall have the ability to select multiple view templates. This browser
based video viewer shall provide the following functionality:
1) Ability to be loaded on a PC through a web browser with minimal
effort
2) Authenticate through a SYSTEM user account

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

HTTP protocol 4) Be limited to only viewing/controlling such video
over the
as has been allowed by the
SYSTEM’s user permissions 5) Ability to view live and recorded

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

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

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

firewall friendly HTTP or HTTPS

protocol

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

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

HTTP

11) Ability to perform seeking operations on the recorded

format

video
a) Ability to perform seeking using the seeking slider bar, including
start
goto
b) Ability to change start/end time of the displayed video clip on

c)
theAbility
fly to change playback speed using

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

controls

12)interface
Ability to listen to the audio stream over the HTTP

13) Digital zooming/panning

protocol

14) PTZ camera control

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

LENEL - A UTC FIRE & SECURITY COMPANY

®
OnGuard
Functional Specifications Version 6.3 Series Page 125
 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 multiple

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

19) Limit the number of cameras a user is permitted to

view
20) Browser Based PTZ Locking

When a System User selects a cell that contains a PTZ camera the
SYSTEM shall attempt to lock it to eliminate another System User
with lower priority from taking control of the camera. To allow a
System User with lower priority to use the PTZ camera the initial
System User must unlock the PTZ camera.
l) Alarm
Monitoring
The 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 associated
with the alarm. Once launched, the System Operator shall have the
ability to adjust the start and end time of the segment.
The SYSTEM Alarm Monitoring Module shall be able to save the list of
video windows, the video windows’ sizes, the video windows’ locations,
and the all the selected camera options under a System Operator’s
profile. The next time the System Operator runs Alarm Monitoring the
same list of video windows, the video windows’ sizes, the video windows’
locations, and the all the selected camera options shall be automatically
launched.
1) Real Time Monitoring
The LNVR shall allow monitoring of real time video from any Alarm
Monitoring client workstation. The System Operator shall be able to
monitor any camera by using the System Hardware Status Tree
and choosing the appropriate camera. Output of video for real time
monitoring shall be transferred to an Alarm Monitoring client
workstation over the LAN/WAN.
In the LNVR, authorized System Operators shall be able to
concurrently playback recorded video from any clip, even as that
video clip is being recorded. The Play
LENEL - A UTC FIRE & SECURITY COMPANY
®
OnGuard
Functional Specifications Version 6.3 Series Page 126
 button shall enable System Operators to play back a single video
segment at the maximum recording configuration. The LNVR has
an integrated Matrix View which shall enable viewing of Live and
Recorded streams simultaneously. The Maximum displayable
frames on a given client PC shall be determined by the resolution,
compression, video type and PC specifications of the client
machine. Benchmark data will be made available.
The SYSTEM shall monitor the firmware revision of the LNVR as
well as hard drive space percentage used. The DVMS shall support
the automatic upgrade of firmware through the use of the SYSTEM
scheduling 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 distinct
cells. There shall be one cell for the live video and one cell for a
recorded stream. The recorded stream shall be able to be
configured 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 camera
on a triggered alarm if the device that triggered the alarm is
monitored by more then one camera, When the alarm is generated
the DVMS shall launch a video window for each camera associated
with the triggered device.
4) Playback Control
The LNVR Playback Control shall offer the following features for full
System Operator control of video playback:

a) Start and Stop Playback

During operation of the viewer application, the
authorized System Operator shall be able to start and
stop playback. This operation shall not affect any other
operation.
b) Pause and Resume
During playback of video, the System Operator shall be
able to pause and resume current playback. This
operation shall not affect any other operation.

c) Fast Forward
During playback of video, the System Operator shall be
able to use the Fast Forward button to view the
playback at faster than normal speed. This operation
shall not affect any other operation.

LENEL - A UTC FIRE & SECURITY COMPANY

®
OnGuard
Functional Specifications Version 6.3 Series Page 127
 a. Skip Backward
During playback of video, the System Operator shall be
able to use the Skip Backward button to rewind the
playback. This operation shall not affect any other
operation.
d) Frame Advance
During playback of video, the System Operator shall be able to
use the Frame Advance button to advance the video clip one
frame at a time. This operation shall not interfere with any other
operation.
The System Operator shall also have the ability to switch
between other cameras if the device that generated the event
has more than one camera associated with it. The System
Operator shall have the ability to adjust the start and end times
of the video segment once the video segment is displayed. The
System Operator shall also have the ability to adjust the
playback speed of the video segment from slower than normal
The System
to real time toOperator shall
high speed have the option to switch to Live
playback.
Mode from a camera at any time during the operation. The
System Administrator shall also have the ability to load any
video file from a backup device into the digital video player at
any time.
The digital video player shall be user configurable to show the
date and time of the video clip frame, as well as the current
mode of the player (play or live).
The System Operator shall have the ability to display or not
display the informational text.

The digital video player shall also have the option to

automatically launch upon a critical alarm occurring in the
SYSTEM to show live video at the video camera linked to that
hardware device.
5) Video Player
The Video Player shall support an advanced Matrix View of On-line
camera views. The frame rate limitation shall be any combination
of live or recorded video. The number of video streams in the
matrix is dependent on the frame rate and resolution of the
cameras/video clips being requested and the hardware of the client
viewing PC. Benchmark data must be available from the
manufacturer on select PC platforms. The Matrix view shall allow
the sizing of the matrix windows.
6) Two-Way Audio
The Alarm Monitoring client shall support a dialog that will enable
audio communication to and from audio enabled IP video sources.
The user shall be able to manually send voice or saved audio files
to the audio enabled IP video
LENEL - A UTC FIRE & SECURITY COMPANY
®
OnGuard
Functional Specifications Version 6.3 Series Page 128
source to be played through the devices speaker. The users shall
also be able to hear audio from the audio enabled IP video
source’s microphone. The SYSTEM shall only support audio
protocol G.711.
7) Pan/Tilt/Zoom Control from Alarm
Monitoring
The LNVR shall support pan/tilt/zoom (PTZ) controls from the Alarm
Monitoring Workstation using a PC mouse, USB direct play
controller device (joystick) or RS-485 device. The PTZ control shall
be supported in conjunction with IP PTZ cameras. Supported
command 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

 shall also provide a timeout feature that will “unlock” the PTZ
after a Administrator assigned amount of
System
inactivity.
d) Proportional PTZ Control
The DVMS shall provide PTZ control that is proportional to
the view of the camera. This proportional control shall take
the current zoom position into account. For example, if the
camera is zoomed in, a mouse click will cause a slower
movement then if the camera was zoomed out and the
same 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 a
new single video window. The new window shall have PTZ
enabled automatically.
f) Preset Alarm Actions
The DVMS shall store the priority level of the System
Operator who creates the preset alarm action and will use
that priority when
8) Addition issuing the go to preset PTZ command.
Pan/Tilt/Zoom
Features
The DVMS shall support the use of pan/tilt/zoom (PTZ) security
and priority levels.User
g) System Configured
The following features outline the increased
Presets
security
ThetoDVMS
the Digital Video System
shall allow PTZ control.
Operators the ability to record
the current PTZ
a) Priority Levels location, absolute, pan, tilt, and zoom
positions, under a user defined name. The System Operator
The DVMS
will then beshall
ablesupport
to bringpriority
up the levels
presetused in conjunction
camera location by
with PTZ control. The DVMS shall contain
selecting the user defined name from a drop down a user friendly
list.
check box system to denote a System Operator’s ability to
h) Preset
control PTZTour
cameras. The DVMS shall also contain an edit
box
Thethat
DVMS willshall
allow the System
support Administrator
the ability to record to assign
a set of PTZPTZ
priority levels.
commands andThese two features
save them under ashall be used totour
user-definable allow only
name.
SystemThe Systemwith
Operators Operator will then bepermission
the appropriate able to select levelsthethe
tour name
ability to have
to take controlthese commands
of PTZ cameras. repeated at a future
b) Device
point Group
in time. Control
The DVMS must be able to record the order of
each command
The DVMS shall as well as
provide thethe timing
ability forofSystem
each command. The
DVMS shall be able to conduct multiple
Administrators to limit the System Operators’ access Preset Tours without
to
client
certainapplications
camera device running through the use of a dedicated
groups.
service to control the tours.
c)
9) PTZ
Video Override
CameraControl
Groups/Video Camera
Tours
The DVMS
The DVMS shall allow
shall support a System
camera Operator
grouping who
to allow is video
for controlling
camera
a PTZ camera the ability to temporarily
tours to occur in the SYSTEM Alarm Monitoring Module. “lockout” other
System Operators, with lower priority levels, from
controlling the same PTZ camera. The DVMS

LENEL - A UTC FIRE & SECURITY COMPANY

®
OnGuard
Functional Specifications Version 6.3 Series Page 130
129
 An unlimited number of camera groups shall be supported in the
SYSTEM and each camera group shall support an unlimited
number of cameras. Cameras within a camera group shall span
multiple Digital Video Recorders. Cameras shall have the ability to
be placed into multiple camera groups.
Once grouped, the System Operator shall be able to start a video
camera tour that shall rotate live video between each of the
cameras defined in the video camera group at a user defined
increment. The time increment between switching cameras shall
be user definable in one second increments.
10) Still Image Capture
During playback or monitoring of video, the System Operator shall
use the Pause button followed by selecting Enhance Image from
the 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 to
save single video frames to the client workstation hard drive in a
standard 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 to

File
The System Operator shall have to ability to save and export
recorded video to a file for the purpose of sharing and reviewing
video clips. The start and end times for each video segment shall
be determined by the System Operator. The exported video clip
shall be viewable via a standard Windows media player or via a
video player provided by Manufacturer. Optional Time, Date
Stamp, and User Defined text shall be able to be overlaid onto the
video during export using an optional transparency level.
13) Video Image
Processing
The DVMS shall support video image processing of a single frame
captured image through use of an image processing module. The
image processing module shall show both the original captured
image side by side next to the processed image. The following
effects shall be available to System Operators to apply to an
original captured image in any combination desired:
1) Intensity - Increases or decreases the overall intensity
level of the light in the image. Adjusts the brighter areas by
making them brighter or darker.
2) Contrast - Increases or decreases the range of gray
levels contained in the image. It adjusts the distinction
between the lightest and darkest tones in the image.

LENEL - A UTC FIRE & SECURITY COMPANY

®
OnGuard Functional Specifications Version 6.3 Series Page 131
 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 by
adjusting the middle tones without affecting the darkest and
5) HistoContrast
lightest areas. - Adjusts the number of pixels per gray
level 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 particular
color that distinguishes it from other colors.
7) HistoEqualize - Redistributes shades of colors to adjust
imbalances. It makes the darkest colors black and the
lightest 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,
14) Sharpen
resulting in a -blurring
Enhances theimage.
of the edges and brings out the
15) Halftone - Converts the image to a black and white (1
detail.
bit/pixel) image in which different shades of gray (luminance)
are represented by different patterns of black and white
pixels.
16) Median - Reduces the amount of graininess (noise) in an
image.
17) Emboss - Converts the image to a raised relief style with its
source directed from the top left.
light
18) Gray Scale - Represents the image using up to 256 shades
19) Invert - Inverts the colors in the image as on a photographic
of gray.
20) Mosaic - Converts the image to a grid of square blocks of
negative.
21) Posterize - Reduces the color resolution, which is the number of
color.
shades of color that shall be displayed
simultaneously.

LENEL - A UTC FIRE & SECURITY COMPANY

®
OnGuard Functional Specifications Version 6.3 Series Page 132
 The DVMS shall allow for the System Operator to save any
combination of effects as a profile to be used on other still images
for image processing. Profiles shall have the ability to be added or
deleted from the SYSTEM at any time.
14) Resizable Video Window
Function
During playback or monitoring of video, the System Operator shall
be able to enlarge the size of the video screen to twice the
recorded resolution to have video display larger on the monitor
screen. This operation shall not affect any other operation. The
USER shall have the option to monitor the video at any user
specified 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 camera
to the video recorder is disconnected or malfunctions, the video
recorder supervision shall detect the video loss and will alert the
System Operator via the alarm monitoring client workstation
window, audible alarm, visual alarm, or pager can be optionally
set. 16) Dual Path Failover and
Redundancy
The LNVR shall support the ability to configure a second location
(or path) for an IP camera or IP encoder to failover in the event
that the primary LNVR fails. For example, if the system is
comprised of two 16 channel LNVRs and one of the LNVRs should
fail, the cameras that normally record to it will failover and begin
recording to the second LNVR. This failover will be seamless to the
System Operator. The failover shall occur in less than 60 seconds
from the time the primary recorder goes offline, thus minimizing
the loss of video during the failed condition.
The second location may also be configured as a redundant
recording location. In this mode two (2) copies of the video data
will exist, one at each location.
In the event of a primary recorder failure, the SYSTEM shall
automatically route video from the appropriate source to any open
client connections without user intervention. This shall work for
Live and Recorded video playback.
Channel alarms such as Motion Detection will be masked from the
secondary recorder unless the primary recorder fails. Alarms from
the secondary recorder will be visibly marked as secondary
recorder alarms.
17) Analog PTZ Camera Support via IP
Encoders Units
The LNVR shall integrate the video encoders’ ability to support a
specific set of analog PTZ cameras. These analog cameras are
converted to digital using the video encoders and are then
controlled in the same method as other IP/Network cameras in the
system.

LENEL - A UTC FIRE & SECURITY COMPANY

®
OnGuard
Functional Specifications Version 6.3 Series Page 133
 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 be
assigned to a preset on the camera.

The DVMS shall have the ability to record video based on motion
detection of the camera. The times that motion detection
recording occurs shall be user definable on a time zone basis. Each
camera shall have the ability to have a separate time zone and
motion detection settings if desired. Areas of the video picture
shall be configured to monitor motion. Motion in these areas shall
19)alarms.
generate Event Locking

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

specific video clips regardless of their date and time. Each
event/alarm in the system has the ability to be locked and/or
unlocked by appropriately permissioned users.
20) UNC Path Support

The LNVR must be able to support Network Attached Storage

Devices/Storage Architecture. This means for the storage path,
you must be able to input a UNC path to write to instead of a hard
drive 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, the
SYSTEM shall generate a ‘blind camera’ alarm in Alarm Monitoring.

22) Configuration of Off-line

Cameras
The System Administrator shall be able to mark a camera offline by
marking a check box in the camera configuration tab. Access to
this feature shall be based on System Administrator privileges,
username and password. The ability of generating a report on the
time, camera, recorder, and user who marked a camera offline
shall be supported.
23) Video Capture On Event

The DVMS shall support the ability to capture (record) video only
when an event occurs. The System Administrator shall be able to
configure devices to trigger the recording of events. The event
shall be trigged by either camera inputs, cameras motion
detection, or other events configured within the SYSTEM.
24) Camera Time Stamps

LENEL - A UTC FIRE & SECURITY COMPANY

®
OnGuard
Functional Specifications Version 6.3 Series Page 134
 The LNVR, by default, must provide time stamps at the time the
video is received. This shall enable the use of time stamps
generated by the camera for other purposes.

25) Automatic IP Camera password

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

26) Optionally set the Browser-Based Video Viewing

Client to be Default Player

The DVMS shall support the ability to choose whether the standard
player interface included in the main Alarm Monitoring client or the
Browser-Based video viewing client is the default. If the browser
based video viewing client is the default, when launching video from
the main Alarm Monitoring client, a browser will be launched and
capable of automatically logging in a displaying the requested video
through the browser.

m) Intelligent Motion Video

TheSearching
DVMS shall support advanced automated motion video searching
against prerecorded video. The automated motion video search shall
analyze frames in a pre-configured video segment polygon to detect
motion activity from image to image. It shall display thumbnail images of
the frames with activity, complete with a histogram depicting the relative
amount of activity within each frame. System Operators shall be able to
perform this search by selecting a specific camera and a specific time
period in which the suspected activity took place. The DVMS Search
Mechanism shall then locate all motion events associated with that
camera and time period and display them in trace format or by
thumbnail format. The System Operator can then select the event or
thumbnail and the system shall automatically begin playing the motion
event. The System Operator shall then be able to view each of the
n)
individual Video
events through the camera video window.
Export
The DVMS shall be able to export user selected video clips to the
industry standard .ASF format for viewing in industry standard video
viewers such as Microsoft Windows Media Player format. The System
Operator shall be able to add text to the clip as well as be able to modify
the color, size and position of the font. The System Operator will be able
to position the time/date stamp as well as modify the color, and size of
The video clip may be sent via email, burned to disc or stored on a
the font.
directory. The recipient will have the ability to view video without the
need for having the SYSTEM Client software installed on their PC
machine.

LENEL - A UTC FIRE & SECURITY COMPANY

®
OnGuard
Functional Specifications Version 6.3 Series Page 135
 o) Remote
TheMonitor
DVMS shall support a Remote Monitoring Application (RMA). The
RMA shall be able to be run from any computer, The SYSTEM shall not be
required to be installed on the computer using RMA. System Operators
shall be able to configure the RMAs in the SYSTEM and use the Alarm
Monitoring component to send them video requests. The RMA shall also
provide the following functionality: A redistributable Remote Monitoring
application must be installed on each Remote Monitoring computer to
utilize the Remote Monitoring functionality. Remote Monitor shall
support the ability to run multiple sessions on a single computer. These
sessions shall have the option of being defined to represent each
physical monitor on the Remote Monitor PC. A Remote Monitor session
shall be distinguished by the port it communicates to a monitor. Each
The
RemoteSystem Operator
Monitor shall
session be be
shall able to configure Remote
independently Monitors
controlled (RMs)
from the
and
Alarm Remote Monitor
Monitoring Groups (RMGs) in System Administration
application.
The System Operator shall have the ability to view RMs and their status
in the Alarm Monitoring system hardware tree, as well as in the device
group view in case RMGs are defined
The System Operator shall be able to view the status of the Remote
Monitor Cells (RMCs) under the RM items in the system hardware tree.
The System Operator shall be able to drag and drop cameras onto the
RM and RMG icon. This will start the live video playback on the RM (or
all RMs in a RMG)
The System Operator shall have the ability to drag and drop alarms,
with associated video onto the RM or RMG icon. This will start the
recorded video playback for all the cameras associated with that alarm.
The System Operator shall be able to send matrix mode, camera
selection, and video playback commands to the RMSRMA via RM’s
context menu. In the system hardware tree or device group view. Also
this menu shall allow System Operators to remove all RMCs from the
RM, as well as re-synchronize the RMA (by sending a download database
command)
The System Operator shall be able to send video playback commands to
the RMA via the RMC’s context menu in the system hardware tree. This
menu also shall allow the user to remove the current RMC, as well as
select it when in single player mode
The System Operator shall the ability to launch the Local Monitor
Window (LMW) by right clicking on the RM or RMC and selecting launch
video. Matrix mode, camera selection, and video playback commands
performed in the LMW will be also sent to RMA.
The System Operator shall be able to configure the Remote Monitor to
run in full screen mode.
The System Operator shall be able to load saved video layouts directly
to a Remote Monitor Instance.

• The System Operator shall be able to select various Video

Quality Enhancement (VQE) algorithms that will improve the viewing
quality 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 fog
in the foreground shall be diminished.
The System Operator shall be able to select the De-Interlacing
algorithm and the artifacts affects of compression and interlacing
shall be diminished.
The System Operator shall be able to select the sharpen algorithm
and a camera view which is blurred shall be diminished.
The impact on the above three VQE algorithms shall only impact
the workstation in which the changes were made and shall not
impact recorded video or other workstation viewing of the video.

LENEL - A UTC FIRE & SECURITY COMPANY

®
OnGuard Functional Specifications Version 6.3 Series Page 136