CCTV Tech WriteUp

Spec_BVMS_VRM_Ver3.1.05.
13
Regional Sales Office APR
Video Surveillance System

Consultant Specifications
Page 1 of 56
Spec_BVMS_VRM_Ver3.1.05.13
1.
Brief Overview.
1.1. The primary objective of the Video Surveillance System (VSS) is to
provide, the security officers, visual surveillance coverage and recording of
movements at all designated locations.
1.2. The following clauses outline the minimum requirements for the design,
supply, delivery, installation, testing, commissioning and maintenance of the
proposed VSS.
1.3. The VSS shall be an integrated hybrid / full Internet Protocol (IP)
system which consist, but not limited to, the following:
1.3.1. Fixed colour cameras for indoor and outdoor application
complete with lens and mounting brackets.
1.3.2. Pan/Tilt/Zoom (PTZ) colour day/night dome remote controllable
CCTV cameras.
1.3.3. Video
servers.
management
software
functions,
including
system
1.3.4. Digital Video Storage Subsystem (DVSS) as called for in the

tender specification.
1.3.5. Video client viewing software functions, including workstation.
1.3.6. Single / Multi-channel high performance video encoders /
decoders.
1.3.7. Monitor Display (Analog / Digital LCD).
1.3.8. Monitor wall.
1.3.9. Keyboard and video controllers.
1.4. The VSS shall preferably be interfaced as part of the integrated
network with high level interface to a Security Management System (SMS), if
called for in the Project Specification.
1.5. The VSS shall support the interface with advanced intelligent video
content analysis (IVA) techniques built into the IP cameras / encoders from
the same manufacturer to provide advanced motion detection and video
analysis.
1.6. A documented Software Development Kit (SDK) shall be provided to
allow integration with other application software.
Page 2 of 56
1.7. The VSS shall be designed to provide control, integration and

seamless operation of the cameras, monitors, and DVSS to the user via
Graphical User Interface (GUI).
1.8. The VSS shall be designed such that any failure in this system shall
not affect the normal operation of the entire system, the remaining system
components shall continue to operate with partial or full functionality.
1.9. The VSS shall be capable of recording real time digital video at a
recording rate of 30 images per second (NTSC) / 25 images per second (PAL).
1.10. Video recording and storage shall be based on H.264 compression
technologies. The VSS shall support both H.264 BP+ (Baseline Profile +) and
H.264 MP (Main Profile) video compression.
1.11. Normal recording rate shall be set at 6ips 4CIF. Upon alarm activation,
the related alarm cameras shall automatically switched to alarm recording
mode at 25ips 4CIF. Pre- and Post alarm recording shall be provided and
configurable.
1.12. The recording shall be based on a first-in-first-out mode. Sufficient hard
drive storage shall be provided for a minimum thirty (30) days of video storage.
1.13. The recording of all cameras will be based on 90% active scenes. The
Tenderer should submit their storage calculation table to show that sufficient
storage capacity is propose and according to the specification written.
1.14. All cameras proposed by the Tenderer shall be able to capture the
picture detail in both the highlight and lowlight areas to maximize the
information visible in the picture.
1.15. Both outdoor and indoor cameras shall have auto iris, varifocal lenses
as required by the application to allow manual zoom and focus adjustment
and shall be mounted on adjustable supports.
1.16. Special care should be taken to ensure that the desired viewing area is
maintained. Correct camera positions, proper mounting, fixing and adjusting
the angle of each camera and selection of the right characteristics of the lens
(focal length, etc) shall be the responsibility of the contractor to achieve the
required view. This will be verified by the Engineer-in-charge before
acceptance of the complete system.
1.17. All outdoor cameras shall be provided in a NEMA 4X or IP66 certified,
rugged, weather-resistant package complete with self cleaning features.
These cameras shall be installed in weatherproof and dust-proof housings
complete with sun shields, heater and fan.
Page 3 of 56
1.18. The wiring to all cameras shall pass from the back-box through the
mount and into the housing. Exposed wiring of any kind shall not be
acceptable. This includes wiring outside of the mount encased in seal-tight,
electrical tape or similar wrap.
1.19. The VSS shall be modular and expandable, with the ability to connect
with future buildings and facilities without having to shift the point of
connection or interrupt system operation. The design shall provide no less
than 20% spare for future expansion.
1.20. The VSS shall be manufactured by a manufacturer whose quality
system is in compliance with the I.S./ISO 9001/EN 29001, QUALITY SYSTEM.
Page 4 of 56
2.
Video Management System (VMS).
2.1.
System Architecture.
2.1.1. The Video Management System (VMS) shall be a client server
based video surveillance system that provides seamless management
of digital video, audio and data across an IP network infrastructure.
2.1.2. The VMS design shall provide the flexibility to allow owner to
add or remove any components and / or controlled functions, in the
event when operating requirements changes as system expands.
2.1.3. The VMS shall be scalable to an enterprise management
system that allows a user of an operator client to simultaneously
access the devices of multiple subsystems.
2.1.4. The VMS shall consist of the following modules:
a.
Management Server:
b.
Enterprise Management Server [Remove if Enterprise
Management Server is not required]
c.
Mobile Video Service. [Not valid for Enterprise solution,
support only BOSCH devices]
d.
Configuration Client.
e.
Operator Client.
2.1.5. The Management Server software shall provide management,

monitoring, and control of the entire system. This shall include, but not
limited to:
a.
Data stream management.
b.
Alarm management
c.
Priority management
d.
Central logbook
e.
Central configuration
f.
User management.
g.
Central software update to the operator client and
configuration client.
Page 5 of 56
h.
Time synchronization reference for all VSS devices within
the network.
2.1.6. The Management Server shall run as services on Windows
Server 2008R2 and Windows 7.
2.1.7. The VMS shall be designed in such a way the Management
Server downtimes shall not affect the functionality of the recording
services.
2.1.8. The Enterprise Management Server shall manage multiple
Management Servers. Each connection from the Enterprise
Management Server to the Management Server shall be independent
from the other connections. A change in a Management Servers
configuration shall be automatically reflected in the Enterprise
Management Server. [Remove if Enterprise Management Server is not
required]
2.1.9. The Enterprise Management Server shall run as services on
Windows Server 2008R2. [Remove if Enterprise Management Server is
not required]
2.1.10.
The Mobile Video Service shall provide transcoding
service that transcode the video stream to be received, live or playback
video data, by mobile video clients like an iPad / iPhone. The service
shall run as an application on Server 2008R2 or Windows 7. [Not valid
for Enterprise solution, support only BOSCH devices]
2.1.11.
The authorized mobile video clients shall be able to
access live and recording data of all cameras in the VMS.
2.1.12.
The Configuration Client software shall provide the user
interface for system configuration and management. The service shall
run as an application on Server 2008R2 or Windows 7.
2.1.13.
The Operator Client software shall provide the user
interface for live monitoring, storage retrieval, and alarm handling. The
service shall run as an application on Windows 7.
2.1.14.
The VMS shall be capable to be deployed in Local Area
Networks (LAN) as well as in Wide Area Networks (WAN). For
establishing remote connections across WAN, it shall be possible to
setup a port mapping table within the configuration manager in order to
map the public port to a private IP and port of the devices. The VMS
shall provide a RRAS configuration tool to transfer the port mapping
table to a RRAS Service.
Page 6 of 56
2.2.
Function.
2.2.1. The VMS shall provide an easy and comfortable way to the
operator to select and connect to a management server from a list of
servers during logon. The tool shall provide a search function to quickly
find the server by searching for content appearing in the name or
description of the servers. This tool to connect to servers shall be
capable of listing up to 9.999 servers in its list. [Remove if Enterprise
Management Solution is not required]
2.2.2. The VMS shall automatically detect when management servers
are located in different time zones by means of the local time settings
in the servers. The operator shall see from the server list in device tree,
which management servers time zone is currently displayed in the
operators User Interface. The operator shall be given the possibility to
set his own operation time to a dedicated time zone of one of the
management servers. Selected time zone shall be applied to live view,
playback, the alarm list and the logbook. Operator shall also be able to
select UTC time. [Remove if Enterprise Management Solution is not
required]
2.2.3. The VMS shall support live and recorded video viewing, alarms
and events monitoring, system supervision and history archiving, by
multiple users simultaneously, without degradation of any functionality
specified system or operation.
2.2.4. The VMS shall support multiple languages (e.g. English,
German, Simplified Chinese, Traditional Chinese, Thai, Japanese,
Korean and Arabic).
2.2.5. The VMS shall allow specifying the language per user group.
The VMS shall allow specifying the language for configuration client. If
Default System language is specified, the system shall use the same
language as the operating system language.
2.2.6. The VMS shall support ONVIF compliant products as part of a
total video security management system to provide full virtual matrix
switching and control capability.
2.2.7. The VMS shall support ONVIF compliant cameras. It shall be
possible to access live streams, record based on JPEG or RTSP, and
control PTZ functionality.
2.2.8. The VMS shall provide auto-discovering function to scan for
connected devices on the same and different network subnets.
2.2.9. The VMS shall allow the configuration of the IVA parameters
and react as per configuration to the events triggered by it. [Please
decide if IVA is required]
Page 7 of 56
2.2.10.
The VMS shall support an administrator-configured
logical tree. The logical tree shall be freely configurable with any tree
structure, with nodes consisting of devices such as, cameras, inputs,
and relays, folders, maps, sequences, documents, URLs, and
command scripts.
2.2.11.
The VMS shall provide up to 10 different and independent
programmable recording schedules. The schedules may be
programmed to provide different record frames rates for day, night, and
weekend periods as well as holidays and exception days.
2.2.12.
The VMS shall support advanced task schedules for
scheduling various events such as, specify allowed logon times for
user groups, when events may trigger alarms, and when data backups
should occur.
2.2.13.
The VMS shall allow adding of holidays and exception
days to the recording and task schedule. The recording schedules shall
share the same holidays and exception days while each standard task
schedule shall has its own holidays or exception days patterns.
2.2.14.
The VMS shall support pre-programmed camera
sequences. These sequences will allow cameras to be automatically
displayed on the computer image panes and/or analog monitors
connected to decoders.
2.2.15.
The sequences shall support simultaneous display on
multiple image panes or monitors. The sequences shall also support
camera prepositions for each PTZ camera on each sequence step. The
system shall be configurable such that operators can select these
sequences from the logical tree or a site map.
2.2.16.
The sequences shall support simultaneous display on
multiple image panes or monitors. The sequences shall also support
camera prepositions for each PTZ camera on each sequence step. The
system shall be configurable such that operators can select these
sequences from the logical tree or a site map.
2.2.17.
The VMS shall allow the establishment of user groups
and enterprise user groups that have access rights to the following:
a.
Specific cameras
b.
Priority for pan/tilt/zoom control
c.
Rights for exporting video,
d.
Access rights to system event log files.
Page 8 of 56
2.2.18.
Access to live, playback, audio, PTZ control, preset
control, and auxiliary commands shall be programmable on an
individual camera basis.
2.2.19.
The VMS shall support a centrally stored user profile to
store settings individual for each operator. These settings shall include,
but not limited to, sequence dwell times, instant playback replay time
and image pane ratio settings (16:9 or 4:3) for individually per monitor.
These settings shall be available independently of the physical
workstation to the operator.
2.2.20.
Analog monitor support
a.
The VMS shall support analog monitors connected to IP
decoders, and monitor walls.
b.
It shall be possible to configure analog monitors in full
screen mode or quad mode. When in quad mode, the VMS shall
be able to select video and control cameras in any quadrant.
c.
The VMS shall support grouping of analog monitors into
Analog Monitor Groups (
d.
s). An AMG shall specify a monitor arrangement of rows
and columns.
e.
The VMS shall support restricting access to AMGs to
specified operator client workstations.
f.
Pre-programmed camera sequences shall be displayed in
Operator Client and on AMG.
2.2.21.
Monitor wall shall support an Enterprise System, i.e. all
monitor walls configured on the subsystems management server
computers shall be usable on an Enterprise Operator Client. [Valid for
Enterprise solution only]
2.2.22.
Mobile video service.
a.
The VMS shall provide a mobile video service that
transcode the video stream from a camera configured in the
system to be received, live or playback video data, by mobile
video clients like an iPad / iPhone.
b.
The mobile video clients shall be able to access live and
recording data of all cameras in the video management system.
It shall be possible to access the VMS from mobile video clients
with the user accounts in the VMS.
Page 9 of 56
c.
The mobile video clients shall be able to access live and
recording data of all cameras in the video management system.
It shall be possible to view up to 4 video streams at once on a
web client or iPad and mix live and playback streams.
d.
The mobile video clients shall further more provide an
option for the user to zoom in as well as to opt between high
resolution and smooth motion (higher rate of frames per second).
It shall be possible to access the video management system
from mobile video clients with the user accounts in the video
management system.
2.2.23.
Relays and Inputs / Outputs.
a.
The VMS shall control and monitor the status of the
inputs and relay outputs from the connected devices including IP
cameras, video encoders and external digital input/output (I/O)
modules. The open and close states shall be indicated on the
OC user interface and shall be able to be queried via the VMS
SDK.
b.
Relays from the devices connected to the system shall be
controllable via command scripts, the VMS SDK, and icons on
the OC user interface.
c.
Input and relay state changes from the devices
connected to the system shall be recognizable as events in the
VMS.
d.
The VMS shall provide a software interface that allows
that support third-party software to create a virtual input that
generates events in the VMS.
e.
The software interface shall support any COM
programming languages (e.g. Visual Basic and C++), any .Net
programming language (e.g. C#) or JavaScript.
f.
The VMS shall allow third-party software to include up to
10 data fields and an Alarm ID along with the virtual input event.
These fields shall be searchable in the system logbook.
g.
The virtual input data shall be optionally displayed in the
OC playback mode synchronously with the associated video.
Page 10 of 56
2.2.24.
Command Scripts
a.
The VMS shall provide a built-in command script editor
that allows customized command scripts to be written to control
the system functions.
b.
The built-in command script editor shall support C# and
VB.NET.
c.
Operators shall be able to execute the created scripts by
double-clicking on representative icons in a logical tree or site
map.
d.
The command script shall be able to be executed
automatically in response to a system event. The automatic
event-driven execution shall optionally be schedule-dependent.
e.
The VMS shall be configurable to execute a user-group
dependent command script on user logon.
f.
The VMS shall be configurable to execute an alarmdependent command script on user acceptance of the alarm.
2.2.25.
Logbook
a.
The VMS shall record every event and alarm in a logbook
database based on MS SQL database. The alarm entry shall
contain the camera titles that have been recorded due to this
alarm.
b.
The logbook database shall be able to store up to
500,000 entries per hour. The record shall be based on a FirstIn-First-Out mode.
c.
The logbook database shall use 64 bits indexing.
d.
The operator, with the right authorization, shall be able to
search the logbook for events and alarms. The user shall be
able to export the search results into a comma separated value
list.
e.
The logbook shall log the log on procedure to identify a
single user or a dual authorization log on. Subsequent user
actions shall be logged as the actions of the first user.
f.
The VMS shall included and install a ready-to-use SQL
database. The system shall optionally allow the usage of a
separately installed MS SQL database.
Page 11 of 56
2.2.26.
The VMS shall be capable of monitoring the status of the
connected equipment via Simple Network Management Protocol
(SNMP).
2.2.27.
The VMS shall provide an OPC server for integration into
third-party software systems. The OPC interface shall follow the OPC
Alarms and Events standard.
2.3.
Configuration Management.
2.3.1. The VMS shall be designed in such a way that configuration
changes to any part of the system shall not interrupt operational tasks,
until the operator decides to update re-fresh the workstation
configuration.
2.3.2. System configuration changes made in the VMS shall modify a
working copy of the configuration, and shall not affect the active
operating configuration.
2.3.3. The VMS shall allow the activation of the working copy through
a user action in the configuration client, at which point the working
becomes the new active operating configuration.
2.3.4. It shall be possible to set a date and time in the future at which
the working copy becomes active.
2.3.5. The VMS shall support viewing list of all configuration
activations that have been applied to the system.
2.3.6. The VMS shall allow selection of any of the activated
configurations, and have the system "roll back" to an earlier
configuration.
2.3.7. The VMS shall allow the activation of configuration and leave it
to the operator to refresh the configuration locally instantly or at a later
point in time. It shall be possible to enforce configuration activation for
every operator client connected to the Management Server.
Page 12 of 56
2.4.
User Management.
2.4.1. The VMS shall support the establishment of user groups and
enterprise user groups [Valid for Enterprise solution only]. The
administrator shall be able to define specific access-rights for each
user groups which include:
a.
Access to system resources (specific cameras, encoders,
monitors) individually controlled per user group.
b.
Individual per-camera privileges assignable per user
group for live access, playback, audio, meta data display, dome
control
c.
User group priority assignment for PTZ control and
camera access.
d.
Logical Tree customized per user group.
e.
User group rights for protecting, deleting, exporting, and
printing video.
f.
Access rights to system event log files.
2.4.2. The VMS shall support a centrally stored user profile to store
settings individual for each operator. These settings shall be available
independently of the physical workstation to the operator.
2.4.3. The VMS shall support dual authorization logon, functioning as
follows:
a.
Dual Authorization user groups may be created.
b.
Logon pairs, consisting of any two (2) normal user groups,
shall be allowed to assign to each Dual Authorization user group.
c.
A separate set of privileges and priorities can be
assigned for each Dual Authorization user group.
d.
For each user group assigned as part of a logon pair, it
shall be configurable whether the group can:
i.
pair
Log on either individually or as part of the logon
ii.
Or log on only as part of the logon pair.
Page 13 of 56
e.
If a user that is part of logon pair logs on individually, then
he shall receive the privileges and priorities of his assigned user
group.
f.
If the same user logs in as part of a logon pair, then the
user shall receive the privileges and priorities assigned to the
dual authorization group to which the pair is assigned.
g.
Dual authorization shall also be available for an
Enterprise Management System. [Valid for Enterprise solution
only]
2.4.4. Only authorized personnel with the valid login username and
password shall be able to access, configure and administrate the
system.
2.4.5. The VMS shall support Lightweight Directory Access Protocol
(LDAP) that allows integration with enterprise user management
systems such as Microsoft Active Directory.
2.4.6. LDAP shall also be available for an Enterprise Management
System. LDAP shall be configurable in an Enterprise user group. [Valid
for Enterprise solution only]
2.5.
Alarm Handling and Management.

2.5.1. The VMS shall provide the operator a simple and efficient way to
handle any incoming alarms.
2.5.2. The VMS shall provide the capability to allow alarms to be
schedule-dependent.
2.5.3. The VMS shall allow alarms to be individually allocated to
specific user groups for processing.
2.5.4. The VMS shall support replication of events such that a single
physical event causes multiple system events. These multiple events
shall be independently configurable to allow independent handling of
the alarms by multiple operator groups, or to be handled differently
according to different schedules.
2.5.5. The VMS shall be programmable to selectively, based on per
alarm and per user group, pop-up the pre-assigned alarm video images
automatically.
2.5.6. Alarm videos shall be displayed in a separate Alarm Image
window so that operators do not have to search their display screens to
find the video images related to the alarm.
Page 14 of 56
2.5.7. For each alarm, up to five (5) alarm image panes in a row within
the alarm image window shall be configurable to display the alarm
related images. Each incoming alarm image display shall occupy one
(1) complete row.
2.5.8. The alarm image panes shall be configurable to display live
video, playback video, text documents, HTML files, or web-sites
(URLs) if connected to the internet.
2.5.9. The alarm image panes shall be displayed in order of their
priority, with rows for higher priority alarms always displayed above
lower priority alarm rows. The display order for equal priority alarms
shall be selectable between new alarms displayed above existing
alarms, or new alarms displayed below existing alarms.
2.5.10.
The VMS shall provide an alarm reaction time of
maximum two (2) seconds when sufficient network bandwidth is
available.
2.5.11.
The VMS shall distribute alarm notifications, via entries in
the alarm list of the operator user interface, to all members of the user
groups to which the alarm is assigned. The alarms shall appear in all
said users' alarm lists.
2.5.12.
When an operator accepts an alarm, the same alarm
message shown at other members of the operators groups alarm list
shall automatically be removed from their screen.
2.5.13.
Upon operator acceptance of the alarm, there shall be an
association of workflows with the alarms if required. Workflows shall
consist of action plans and comment boxes. An action plan shall
display a text document, HTML page, or web site that typically contains
instructions for handling the alarm. Comments entered in the comment
boxes shall be logged in to the system database.
2.5.14.
The VMS shall allow alarms to be configured to send PTZ
cameras to prepositions or to execute camera Aux commands on
alarm occurrence.
2.5.15.
The VMS shall be configurable to put any relative alarm
cameras into alarm recording mode on alarm occurrence.
2.5.16.
The operator shall have also the flexibility to un-accept a
particular alarm from his alarm list he had earlier accepted, if he is
unable to process it. In this case, the alarm shall re-appear in the alarm
lists of all other members of the user groups authorised to process the
same alarm.
Page 15 of 56
2.5.17.
The VMS shall be configurable to force an alarm workflow.
In this case, the alarm cannot be cleared until the workflow is
processed.
2.5.18.
The VMS shall offer the possibility to automatically clear
alarms when the originating event condition is no longer true.
2.5.19.
The VMS shall be configurable to send an e-mail or SMS
message in response to alarms.
2.5.20.
The VMS shall be capable of displaying video on
monitors or multiple AMGs in response to alarms, with configurable
assignment of individual assignment of alarms to monitor groups
2.5.21.
As new alarms are received, alarm rows shall stack in
priority order on the analog monitors.
2.5.22.
The VMS shall take advantage of the row and column
arrangement AMGs by associating a row of analog monitors with each
active alarm. Each alarm may display video on multiple monitors,
limited by the number of columns in the analog monitor group.
2.5.23.
In an Enterprise System, each alarm shall be indicated
the subsystems management server that triggered the alarm. [Only
valid for Enterprise solution]
2.6.
Operator Client Requirement.

2.6.1. The Operator Client (OC) shall support user to log on to the
Management Server or Enterprise Management Server.
2.6.2. Operator logging on to the Enterprise Management Server shall
be able to simultaneously access the devices of the subsystems. [Valid
for Enterprise solution only]
2.6.3. An operator client user logging on to an Enterprise Management
Server shall be able to simultaneously access the devices of up to 10
subsystems.
2.6.4. If an operator client loses its connection to the management
server, the user shall nevertheless be able to continue working with the
connected devices.
2.6.5. The OC shall supports Independent Operator Client features.
When the OC is disconnected and offline from the Management Server,
it shall be possible to continue operation for live, playback and export.
2.6.6. Each user group shall only see items in the logical tree for which
the administrator has granted access based on their operator login
profile.
Page 16 of 56
2.6.7. The user shall be able to search the logical tree for item names.
2.6.8. The OC shall support user-dependent logical favourites tree,
containing maps, folders, devices and complete views such as image
pane patterns with camera assignments of their interest.
2.6.9. The operator's favourite tree shall be available irrespective of
the computer with which the operator logs on to the system.
2.6.10.
The OC shall provide an image matrix window that
displays a collection of image panes.
2.6.11.
The OC shall support selection of 16:9 and 4:3 cameo
layouts. The layout shall be optimized for non-widescreen and
widescreen monitors:
a.
For non-widescreen monitors, the number of image
panes per image matrix window shall be selectable between 1
(i.e. a single full-window video) and 25 (i.e. matrix view),
arranged in 1, 2x2, 3x3, 4x4, and 5x5 grid format.
b.
For widescreen monitors, the number of image panes per
image matrix window shall be selectable between 1 and 30,
arranged in grids of 1x1, 3x2, 4x3, 5x4, and 6x5 grid formats.
2.6.12.
The OC shall allow the image panes within the image
matrix window to be enlarged or decreased in size within the grid.
Image pane shall be able to be resized by just clicking and dragging on
any of its corner, dragging the corner to the desired size. As such, any
pattern shall feasible be created within the grid structure.
2.6.13.
The OC shall implement the concept of a selected image
pane, where the selected image pane shall be highlighted. There shall
always be a selected image pane for control commands.
2.6.14.
The OC shall support the display of site maps that are of
standard vector graphics format such as AutoCAD DWF, containing
hot-spot icons for devices such as cameras, relays, and inputs,
command script initiation, camera sequence initiation, and links to
other site maps.
2.6.15.
The site maps shall be capable of being zoomed and
panned to show a desired location simply using a standard PC mouse
and there shall be a separate overview map that shows the operator
the portion of the zoomed site map currently in view.
2.6.16.
All icons shall be provided in vector format, such that
when the operator performs zoom-in and out of the map, the icon size
scales automatically with respect to the size of the image view.
Page 17 of 56
2.6.17.
The OC shall display live streams from encoders / IP
cameras. It shall be possible to configure per workstation and
individually per camera which encoding stream (Stream 1 or Stream 2)
of these devices shall be displayed.
2.6.18.
The OC shall support switching of cameras to monitors
connected to decoders. The cameras shall be selectable via drag and
drop from the logical tree or from the sitemaps.
2.6.19.
The OC shall support automatic sequencing. It shall be
possible for operators to select multiple cameras by control-click or
shift click keyboard function, and drag the multiple-selection to an
image pane. All of the cameras in the selection shall then sequence in
the image pane or monitor at a user-selectable rate. It shall also be
possible to drag a folder containing a list of connected cameras to an
image pane or analog monitor and all the cameras shall start
sequencing.
2.6.20.
The OC shall provide PTZ camera control via a dedicated
on-screen graphical joystick, as well as by clicking the mouse within
the image panes. The mouse cursor shall change to indicate the
Pan/Tilt direction while hovering over the corresponding image pane.
2.6.21.
The Pan/Tilt speed shall increase as the mouse cursor
moves farther from the centre of the image pane. An area in the centre
of the image pane shall be used for zoom-in/zoom-out control. Once
zoom is initiated, likewise the zoom speed shall increase as the mouse
cursor moves farther from the centre of the image pane.
2.6.22.
The OC shall support digital zoom of any image pane. A
dedicated graphical control shall be provided in the user interface for
this purpose. In addition, the mouse wheel shall control digital zoom
when the mouse cursor is hovering over a selected image pane.
2.6.23.
The OC shall support the following keyboards function
when connected to the OC workstations:
a.
Control the current image pane selection.
b.
Control the AMGs or any image pane.
c.
Control PTZ operation of the selected cameras.
d.
Control set and call-up PTZ prepositions of the selected
camera.
e.
Execute PTZ cameras Aux commands of the selected
camera.
Page 18 of 56
f.
Control playback of video, including both Instant Playback
and Playback-mode synchronous playback.
g.
2.6.24.
Support jog-shuttle emulation during playback control.

When in Jog-shuttle emulation mode:
a.
Rotating the Keyboard joystick will control forward and
reverse playback, with playback speed proportional to the
amount of joystick rotation.
b.
Moving the joystick up shall set the video into slow
forward playback mode. Additional upward movements shall
incrementally increase forward playback speed
c.
Moving the joystick down shall set the video into slow
backward playback mode. Additional downward movements
shall incrementally increase backward playback speed.
d.
Moving the joystick right shall set the video into pause
mode. Additional rightward movements shall step the video one
frame forward.
e.
Moving the joystick left shall set the video into pause
mode. Additional leftward movements shall step the video one
frame backward.
2.6.25.
The OC shall be able to do an instant playback that
displays recorded images on one or multiple image panes. The instant
playback function shall support:
a.
Pause.
b.
Play forward.
c.
Play reverse.
d.
Single step forward
e.
Single step reverse
f.
Fast-forward
g.
Fast-reverse.
2.6.26.
Recorded images from a single camera shall able to be
played back on multiple panes.
Page 19 of 56
2.6.27.
The OC shall provide a timeline that provides a graphical
overview of video stored on the disk. The timeline shall display a
timescale that shall be adjustable.
2.6.28.
For each camera displayed in playback mode, there shall
be a line provided within the timeline that depicts the video storage for
that camera.
2.6.29.
The line shall show if video is recorded for the displayed
time period, and if so, if it is normal recording, motion recording, or
alarm recording. The line shall be cross-hatched if the video is
protected from deletion. The line shall also indicate if associated audio
is recorded during the displayed time period.
2.6.30.
The OC shall support simultaneous time-synchronous
playback of up to 16 cameras. The following functions shall be
supported during playback:
a.
Single-step forward and backwards.
b.
Play normal speed forward and backwards.
c.
Play high-speed forward and backwards.
d.
Play slow-speed forward and backwards.
2.6.31.
The OC shall optionally display the information of the
video analytics such as cells with detected motion, object masks, and
trajectories in live and playback, upon the activation of the IVA function.
[Please decide if IVA is required]
2.6.32.
on:
The OC shall support searching of recorded video based
a.
Motion event in user-specified areas of a camera image.
b.
Time / date range.
c.
Event type(s).
d.
Alarm priority.
e.
Alarm state.
f.
Device(s).
g.
Combination of the above.
Page 20 of 56
2.6.33.
The OC shall support saving and recalling the search
parameters.
2.6.34.
The OC shall support searching of recorded video based
on the following on IVA criteria: [Please decide if IVA is required]
a.
Object size.
b.
Object colour.
c.
Direction of moving object.
d.
Speed of moving object.
e.
Detection of objects entering or leaving designated areas.
2.6.35.
The OC shall graphically display device status on its
icons in the logical tree structure and on sitemaps. The following status
shall be provided:
a.
Loss of analog video signal.
b.
Loss of network connection.
c.
Video signal too noisy.
d.
Video signal too bright
e.
Video signal too dark
f.
Video includes associated audio
g.
Open or close status for relay or contact inputs
2.6.36.
The VMS shall support the audio channels of the
encoders and IP cameras. It shall be possible to assign audio sources
to cameras. The OC shall be able to turn on/off the replay of the audio
per camera.
2.6.37.
The VMS shall support two different audio modes,
a.
Single source audio mode only the audio source
assigned to the camera in the selected image pane is replayed.
b.
Multi source audio mode all audio sources of the
cameras displayed in the client application are replayed.
Page 21 of 56
2.6.38.
The OC shall support audio intercom function through the
activation of the button within the GUI. When the button is pressed, the
operator shall be able to speak into a microphone installed on the
operator client workstation. The audio shall be transmitted to the audio
source which is assigned to the currently selected camera.
2.6.39.
The OC shall have the capability to export the archived
video, audio and data to the following two(2) different formats into a
CD/DVD drive, a network drive, or a USB drive:
a.
ASF file format, which can be played back using standard
software such as MS Windows Media Player.
b.
System native recording file format, which can be played
back on any standard Windows based PC using its viewer
software included during the export process.
2.7.
System Servers / Workstations.

2.7.1. The VMS and VRM server shall be provided based on dedicated
hardware server platform.
2.7.2. The CPU provided for both servers shall be reliable and robust
in construction to perform all the necessary functions as described in
this document relative to the management of all video systems.
2.7.3. The VMS and VRM servers shall meet the following minimum
hardware requirements: [Please check on the availability of product in
individual countries]
a.
Intel Xeon Processor E5620 2.40GHz, 12MB cache,
5.86 GT/s QPI, Turbo, HT, 4C
b.
16 GB Memory, 1333MHz, Single Rank LV RDIMMs
c.
Microsoft(R) Windows(R) Server 2008 x64 R2 SP1
Standard Edition (64 bits)
d.
500GB 15K RPM,6Gbps SAS 3.5 " Hot Plug Hard Drive
(for non video storage usage)
e.
DVD+/-RW, SATA, Internal
f.
Dual Integrated 100/1000 Ethernet NIC
g.
I/O Expansion Option
h.
Keyboard and Optical Mouse
i.
Monitor 20 inch flat LCD panel.
Page 22 of 56
j.
Standard 19 rack mount version with a quick-deploy rail
system, including sliding universal rails.
2.7.4. The client workstations shall meet the following minimum
hardware requirements: [Please check on the availability of product in
individual countries]
a.
Intel Xeon E5620 2.40GHz, 12M cache, 5.86 GT/s
QPI, Turbo, HT, 4C
2.8.
b.
8GB DDR3 UDIMM Memory, 1333MHz,ECC
c.
500GB 7200 RPM 3.5 SATA Hard Drive
d.
Microsoft Windows 7 Professional (64 bits)
e.
DVD+/-RW, SATA, Internal
f.
NVIDIA Quadro 5000 PCIe 2.5 GB graphics card
g.
Integrated 100/1000 Ethernet NIC
h.
Keyboard and Optical Mouse
i.
23" W Full HD LED Monitor
System Redundancy.
2.8.1. System redundancy shall be implemented for the VMS server.

2.8.2. The system shall be designated to operate in a High Availability
(HA) redundancy mode. If a server fails, affected machines are
restarted on other production servers.
2.8.3. The Tender shall ensure that the all server hardware provided
for system redundancy is of sufficient requirement for long term stable
operation.
2.8.4. The design of the system redundancy implements the
abstractions that allow hardware resources to be allocated to the
workloads in fully isolated environments.
2.8.5. The redundancy solution shall allow the operating system to be
installed on the host system and not directly onto the hardware.
2.8.6. The redundancy solution shall allow the corresponding operating
system installed to make used of shared resources, e.g. memory, CPU
and network resources.
Page 23 of 56
2.8.7. The redundancy solution shall continuously monitor all servers

in a resource pool and detects server failures. Software agent shall be
placed on each server maintains a heartbeat with the other servers in
the resource pool and a loss of heartbeat initiates the failover
procedure.
2.8.8. The redundancy solution shall ensure that sufficient resources
are available in the resource pool at all times to be able to restart
system on different physical servers in the event of server failure. A
clustered file system shall be in placed to give multiple server instances
read-write access to the same virtual machine files, concurrently.
2.8.9. The redundancy solution shall be able to support manual
migrating of system from one resource to the other; in support of
maintenance work has to be done on one machine.
2.8.10.
Two or more physical server shall be used for installation
of any software which provides for redundancy if one server fails. To
prevent from network errors the redundancy server systems shall be
connected by two independent ports to independent IP switches.
2.8.11.
The network for access to the shared storage shall
consist of a dedicated Gigabit backbone. It should be connected by two
paths via two switches to provide for redundancy in case of a switch
failure.
Page 24 of 56
3.
Digital Video Storage System (DVSS).

3.1.
Video Recording Management (VRM).
3.1.1. The VRM shall work in conjunction with an iSCSI based DVSS
to provide a long-term distributed / centralized network video storage
and retrieval solution for video and audio via the IP network.
3.1.2. The VRM shall offer high performance, flexible, scalable and a
highly reliable storage management solution.
3.1.3. The VRM shall act as the central manager for recording allowing
the DVSS to be attached anywhere on a standard IP network.
3.1.4. The VRM shall be installed and run as a service on a dedicated
hardware server platform.
3.1.5. The VRM shall support the encoders and cameras to directly
stream the data to the iSCSI disk arrays. The VRM shall not be
involved in the processing of the data.
3.1.6. The VRM shall manage all disk arrays in the system as a single
virtual common pool of storage. It shall dynamically assign portions of
that pool to the encoders and IP-Cameras.
3.1.7. The VRM shall support intelligent storage allocation, allowing
each camera / encoder to be able to use any storage space it actually
required without having to allocate the storage size before hand.
3.1.8. The VRM shall offer fast and flexible retrieval via a search
database of the recordings and metadata. The metadata shall consist
of events, video content analysis data etc.
3.1.9. The metadata shall be recorded together with the video data to
allow a faster and easy way for the search engine in the playback to
quickly locate specified video recordings.
3.1.10.
The VRM shall have a database that keeps track of the
locations of all the recording blocks. In the event if such database is
lost, the VRM system shall have a self-healing capability to recreate
that same database again by reading the stored metadata.
Page 25 of 56
3.1.11.
The VRM shall support the following recording modes:
a.
Automatic Mode: automatically uses the storage
properties Bandwidth and iSCSI Connectivity to equally
distribute the load within the VRM system. This mode may be
configured in a redundant or in a capacity oriented (no explicit
redundancy) setup.
b.
Dedicated Mode: Manual assignment of a primary and an
optional secondary iSCSI target. The primary and the optional
secondary target must be located in storage pool.
3.1.12.
It shall be possible to secure the access to the VRM
software against unauthorized access via password.
3.1.13.
The VRM shall provide status monitoring information as a
web interface. The following information shall be provided:
3.2.
a.
Uptime of the VRM software
b.
Bit rate information for the recorded data
c.
Retention times per camera
d.
Status on recording and storage
iSCSI Disk Array.
3.2.1. The disk arrays shall be state of the art storage platforms,
utilizing iSCSI protocol, designed for the digital video storage
applications.
3.2.2. The disk arrays shall be of modular design to improve the
serviceability of the unit and minimize downtime.
3.2.3. The disk arrays shall support configurable hardware based
RAID protection. It shall support:
a.
RAID 5 protection for capacity-oriented environments.
b.
RAID 6 protection for availability-oriented environments.
3.2.4. The disk arrays shall be designed as a scale-out system. One

(1) base unit shall support up to seven (7) SAS interface disk shelf
expansion units.
3.2.5. The base unit shall provide a maximum of twelve (12) disk bays
and each disk shelf expansion unit will provide a maximum of twelve
(12) disk bays.
Page 26 of 56
3.2.6. The disk arrays shall support a data performance of up to

500Mbit/s write (record), 32Mbit read (replay), and up to 400
concurrent iSCSI connections. [Based on RAID 5 configuration]
3.2.7. The disk arrays shall support a data performance of up to
400Mbit/s write (record), 25Mbit read (replay), and up to 400
concurrent iSCSI connections. [Based on RAID 6 configuration]
3.2.8. The disk arrays provide the following connection:
a.
Serial console connector
b.
Two (2) x 100Mbps dedicated Ethernet management
ports for management access
c.
Two (2) x 10 Gigabit Ethernet iSCSI host ports, each
configured with a separate IP address.
3.2.9. The disk arrays shall offer dual redundant hot-swap power and
cooling.
3.2.10.
The disk arrays shall support high-availability features:
a.
Automatic drive failover and detection and rebuild using
global hot spare drives.
b.
Mirrored data cache with battery backup and destage to
flash.
c.
SANtricity Proactive Drive Health monitoring identifies
problem drives before they create issues.
3.2.11.
The disk arrays shall offer a Command Line Interface
(CLI) which is remotely accessible by SSH.
3.2.12.
The disk arrays shall provide full SNMP support with
MIB II and NetApp custom MIBs supported.
3.2.13.
In the event of component failures, the SNMP or e-mail
alert notifications will be generated. In additional, an alert notification
shall be logged onto a central Major Event Log.
3.2.14.
The disk arrays shall be of a standard 19-inch, rack
mounted chassis design. Optional slider rails shall be available from
the product manufacturer for rack mounting.
3.2.15.
a.
Operating environmental specifications:

Temperature: +10C to +35C.
Page 27 of 56
b.
Humidity: 20% to 80%, non-condensing
Page 28 of 56
4.
IP Cameras SD Fixed IP Domes.
4.1. The camera shall be a compact, rugged, CCD camera with progressive
scan technology.
4.2. The camera shall utilize 1/3-inch format CCD image sensor capable of
producing 540 TVL of horizontal resolution.
4.3. The camera shall provide a monochrome night mode operation utilizing
NightSense technology that automatically activates under low light conditions.
When in the night mode operation, the sensitivity of the camera shall be
enhanced by a factor of 3.
4.4. The camera shall conform to the Open Network Video Interface Forum
(ONVIF) specification.
4.5. The camera shall provide H.264 IP video to the network. The IP
camera shall support both H.264 BP+ (Baseline Profile +) and H.264 MP
(Main Profile).
4.6. The camera shall be capable of producing two (2) H.264 video streams
(dual streaming) at the rate of 25 / 30 images per second (PAL / NTSC) with
DVD-quality 4CIF resolution.
4.7. The camera shall have tri-streaming capability; each channel
generates two independent video streams and one MJPEG stream at different
rates and resolution where one stream may be used for local recording and
the second stream may be transmitted over the network for live viewing.
4.8. The camera shall provide an On-Screen Display (OSD) for access to
all camera features.
4.9.
The camera shall support video streaming as follows:

4.9.1. In a unicast function that allows communication between a
single sender and a single receiver via a network.
4.9.2. In a multi-unicast mode that supports 5 simultaneously
connected receivers via a network.
4.9.3. In multicast video streaming that allows communication between
a single sender and multiple receivers when used in a suitably
configured network using UDP and IGMP protocols.
Page 29 of 56
4.10. The camera shall allow selection of the following resolutions and frame
rate (PAL/NTSC):
4.10.1.
704 x 576/480 4CIF: 25/30 ips
4.10.2.
352 x 288/240 CIF: 25/30 ips
4.11. The camera shall produce a composite video signal, 1.0V peak to peak
at 75ohms, via a BNC connector.
4.12. The camera shall be housed in cast aluminium housing with a
thermostatically-controlled heater, a polycarbonate dome bubble, and a
hardened inner liner capable of withstanding the equivalent of 120 lbs of force.
The dome bubble is supplied with a UV blocking anti-scratch coating.
4.13. The camera shall comes complete with one of the following automatic
iris, integral, vari-focal lenses, as required by the application, to allow manual
zoom and focus adjustment:
4.13.1.
2.8 to 10.0 mm, F1.2-360, varifocal lens.
4.13.2.
4.14. The camera shall be protected against water and dust to NEMA-4X
(IP66) standards.
4.15. The camera shall provide four (4) independent, fully programmable
privacy mask areas.
4.16. The camera shall provide MOTION+ video motion detection analysis
system that provides basic video content analysis. Six (6) distinct preprogrammed operational modes shall be stored in the camera.
4.17. The camera shall offer optional embedded Intelligent Video Analysis
(IVA) algorithm. This algorithm is based on digital imaging technology that
uses multi-level image analysis of pixel, texture and motion (trajectory)
changes.
4.18. The camera shall support provide a 10/100 Base-T, auto-sensing, half /
full duplex, Ethernet port.
Page 30 of 56
4.19. The camera shall support the following security options:

4.19.1.
802.1x authentication using a RADIUS server for
identification.
4.19.2.
Secure web browser access with HTTPS using a SSL
certificate that is stored in the unit.
4.19.3.
Independent AES encryption with 128-bit keys for each
communication channel video, audio, or serial I/O for total data
protection.
4.20. The camera shall support Power over Ethernet (IEEE 802.3af Class 3)
connection.
4.21. The camera shall provide an alarm input that may be triggered by
either a normally opened or normally closed contact.
4.22. The camera shall provide the capability on alarm to display up to a 17
character, programmable alarm message.
4.23. The camera shall provide a relay output that may be selected for
normally opened or normally closed operation. The relay can be activated
from an external alarm input to the camera, manual activation from the
browser, upon video motion detection, or video loss.
4.24. The camera shall provide an automatic black level feature to enhance
the contrast by removing veiling glare from the picture.
4.25. The camera shall provide selectable on/off backlight compensation.
4.26. The camera shall provide manual and automatic control of White
Balance for optimal colour reproduction. The modes provided shall include:
4.26.1.
Automatic Tracking White Balance (ATW) that allows the
camera to constantly adjust for optimal colour reproduction.
4.26.2.
White Balance Hold (ABW).
4.26.3.
Manual mode that allows manual gain adjustment of red,
green and blue.
Page 31 of 56
4.27. The camera shall provide a built-in test pattern generator:

4.27.1.
Color bars 100%
4.27.2.
Grayscale 11-step
4.27.3.
Sawtooth 2H
4.27.4.
Checker board
4.27.5.
Cross hatch
4.27.6.
UV plane
4.28. Sensitivity (3200 K, scene reflectivity 89%)

Based on NDC-455V03 (F1.2)
Full Video
(100 IRE)
Usable
Picture
(50 IRE)
Usable
Picture
(30 IRE)
a.
Colour
2.6 lx
(0.26fc)
0.65 lx
(0.065 fc)
0.30 lx
(0.03 fc)
b.
Monochrome
1.04 lx
(0.104 fc)
0.26 lx
(0.0026 fc)
0.012 lx
(0.0012 fc)
Usable
Picture
(50 IRE)
Usable
Picture
(30 IRE)

Full Video
(100 IRE)
a.
Colour
2.9 lx
(0.29fc)
0.75 lx
(0.075 fc)
0.37 lx
(0.073 fc)
b.
Monochrome
1.25 lx
(0.13 fc)
0.30 lx
(0.03 fc)
0.14 lx
(0.014 fc)
4.29. Signal-to-noise ratio: 50 dB or better.

4.30. Auto Gain Control: up to 30 dB, selectable.
4.31. The camera shall provide the following shutter modes:
4.31.1.
Auto (1/50 [1/60] to 1/10000) selectable
4.31.2.
selectable.
Auto (1/50 [1/60] to 1/50000) automatic flickerless, fixed
Page 32 of 56
4.32. The camera shall support the following audio standard / compression:
4.32.1.
G.711; 300 Hz to 3.4 kHz at 8 kHz Sampling Rate
4.32.2.
Signal-to-noise Ratio: > 50 dB
4.32.3.
Vpp max.
Signal Line In: 3.5 mm stereo jack, 9 kohm typical, 5.5
4.32.4.
Line Out: 3.5 mm stereo jack, 3.0 Vpp at 10 kohm typical
4.33. The camera shall support these network protocols: RTP, Telnet, UDP,
TCP, IP, HTTP, HTTPS, FTP, DHCP, IGMP V2/V3, ICMP, ARP, SMTP,
SNTP, SNMP, 802.1x, UPnP.
4.34. Environmental specifications:
4.34.1.
Operating temperature range: -20C to +50C (-4F to
+122F) with heater off.
4.34.2.
+122F) with heater on.
4.34.3.
Operating humidity: 5% to 93% non-condensing
4.35. Impact Protection:

4.35.1.
IEC 60068-2-75 test Eh, 50 J
4.35.2.
EN 50102, exceeding IK 10
4.36. Electromagnetic Compatibility:

4.36.1.
EMC immunity: EN50130-4 (PoE, +12 VDC), EN50121-4
(CE), EN55024 (24 VAC)
4.36.2.
EMC emission: EN55022 class B, FCC part 15, EN61003-2, EN6100-3-3
Page 33 of 56
4.37. The camera shall be day/night, utilizing 1/3-inch day/night CCD image
sensor; WDR dual shutter, capable of producing up 540 TVL of resolution.
4.38. The camera design shall be based on a 20-bit DSP image processing
technology to provide enhanced sensitivity and extended dynamic range
coverage.
(Main Profile).
4.43. The camera shall support video streaming as follows:
4.43.1.
In a unicast function that allows communication between
a single sender and a single receiver via a network.
4.43.2.
In a multi-unicast mode that supports 5 simultaneously
4.43.3.
In multicast video streaming that allows communication
between a single sender and multiple receivers when used in a suitably
rate (PAL/NTSC):
4.44.1.
704 x 576/480 4CIF: 25/30 ips
4.44.2.
352 x 288/240 CIF: 25/30 ips
Page 34 of 56
4.46. The camera shall be housed in cast aluminium housing with a

thermostatically-controlled heater, a polycarbonate dome bubble, and a
hardened inner liner capable of withstanding the equivalent of 120 lbs of force.
The dome bubble is supplied with a UV blocking anti-scratch coating.
4.47. The camera shall comes complete with one of the following automatic
iris, integral, vari-focal lenses, as required by the application, to allow manual
zoom and focus adjustment:
4.47.1.
4.47.2.
4.48. The camera shall be protected against water and dust to NEMA-4X
(IP66) standards.
4.50. The camera shall provide a feature (SensUP) that enhances camera
sensitivity by increasing the integration time on the CCD (lowering shutter
time from 1/50 s to 1/5 s PAL; 1/60 s to 1/6 s - NTSC).
4.51. The camera shall provide enhanced night viewing through the increase
of IR sensitivity by automatically switching a motorized IR filter from colour to
monochrome operation in low-light or IR illuminated applications. The IR filter
shall also be switched manually via the alarm input, or pre-programmed in the
camera mode or profile.
4.52. The camera shall utilize XF-Dynamic technology to extend the dynamic
range of the camera to provide a sharper image, simultaneously, in both the
high-light and low-light areas of the scene.
4.53. The camera shall utilizes 2X-Dynamic technologies to extend the
dynamic range of the camera to provide a sharper, more detailed image for
increased accuracy in colour reproduction in harsh lighting conditions.
privacy mask areas.
changes.
Page 35 of 56
4.58.1.
identification.
4.58.2.
4.58.3.
protection.
connection.
4.64. The camera shall utilize pixel-by-pixel analysis to automatically
compensate for bright areas of a high contrast scene (Back light) without
having to define a window or area. Backlight compensation shall work in
conjunction with dynamic range.
4.65.1.
4.65.2.
4.65.3.
green and blue.
Page 36 of 56

4.66.1.
Color bars 100%
4.66.2.
Grayscale 11-step
4.66.3.
Sawtooth 2H
4.66.4.
Checker board
4.66.5.
Cross hatch
4.66.6.
UV plane

Full Video
(100 IRE)
Usable
Picture
(50 IRE)
Usable
Picture
(30 IRE)
a.
Colour
2.486 lx
(0.23 fc)
0.621 lx
(0.058 fc)
0.28 lx
(0.027 fc)
b.
Monochrome
1.01 lx
(0.093 fc)
0.23 lx
(0.0021 fc)
0.099 lx
(0.0092 fc)
Usable
Picture
(50 IRE)
Usable
Picture
(30 IRE)

Full Video
(100 IRE)
a.
Colour
2.7 lx
(0.26 fc)
0.69 lx
(0.064 fc)
0.321 lx
(0.03 fc)
b.
Monochrome
1.1 lx
(0.090 fc)
0.27 lx
(0.026 fc)
0.11 lx
(0.01 fc)

4.70.1.
4.70.2.
selectable.
Page 37 of 56
4.71. The camera shall support the following audio standard / compression:
4.71.1.
4.71.2.
4.71.3.
Vpp max.
4.71.4.
4.73. Environmental specifications:
4.73.1.
+122F) with heater off.
4.73.2.
+122F) with heater on.
4.73.3.
Operating humidity: 20% to 93% non-condensing
4.74. Impact Protection:

4.74.1.
IEC 60068-2-75 test Eh, 50 J
4.74.2.
EN 50102, exceeding IK 10

4.75.1.
(CE), EN55024 (24 VAC)
4.75.2.
Page 38 of 56
5.
IP Cameras SD Fixed IP Cameras.
5.1. The camera shall be a compact, rugged, CCD camera with progressive
scan technology.
5.2. The camera shall utilize 1/3-inch format CCD image sensor capable of
producing 540 TVL of horizontal resolution.
5.3.
The camera shall allow the use of C or CS Mount type lenses.
5.4. The camera shall accept fixed iris lenses, manual iris lenses, DC autoiris lenses, and video-iris lenses. For ease of installation, the camera shall
auto detect the type of lens used and optimize performance accordingly.
5.5. The camera shall provide a lens wizard during lens back focus setup to
allow focusing at maximum lens opening to ensure the object of interest within
the field of view always remains in focus.
5.6. The camera shall provide a monochrome night mode operation utilizing
NightSense technology that automatically activates under low light conditions.
When in the night mode operation, the sensitivity of the camera shall be
enhanced by a factor of 3.
(Main Profile).
Page 39 of 56

5.12.1.
5.12.2.
5.12.3.
rate (PAL/NTSC):
5.13.1.
704 x 576/480 4CIF: 25/30 ips
5.13.2.
352 x 288/240 CIF: 25/30 ips
privacy mask areas.
changes.
5.19.1.
802.1 x authentications using a RADIUS server for
identification.
5.19.2.
5.19.3.
protection.
Page 40 of 56
connection.
5.25. The camera shall provide selectable on/off backlight compensation.
5.26.1.
5.26.2.
5.26.3.
green and blue.
5.27.1.
Color bars 100%
5.27.2.
Grayscale 11-step
5.27.3.
Sawtooth 2H
5.27.4.
Checker board
5.27.5.
Cross hatch
5.27.6.
UV plane
Page 41 of 56

Colour
Monochrome
2.6lx (0.26fc)
1.04 lx (0.104 fc)
a.
Full Video
(100 IRE)
b.
Usable Picture 0.65 lx (0.065 fc)

(50 IRE)
0.26 lx (0.0026 fc)
c.

(30 IRE)
0.012 lx (0.0012 fc)

5.31.1.
5.31.2.
selectable.
5.32. The IP camera shall support the following audio standard /

compression:
5.32.1.
5.32.2.
5.32.3.
Vpp max.
5.32.4.
5.34. Environmental Specifications:
5.34.1.
113F)
Operating temperature range: -20C to 45C (-4F to
5.34.2.
Operating humidity: 20% to 93% relative humidity
Page 42 of 56

5.35.1.
(CE), EN55024 (24 VAC)
5.35.2.
Page 43 of 56
5.36. The camera shall be day/night, utilizing 1/3-inch day/night CCD image
sensor; WDR dual shutter, capable of producing up 540 TVL of resolution.
5.37. The camera design shall be based on a 20-bit DSP image processing
technology to provide enhanced sensitivity and extended dynamic range
coverage.
(Main Profile).
5.40. The IP camera shall conform to the Open Network Video Interface
Forum (ONVIF) specification.
5.42.1.
5.42.2.
5.42.3.
rate (PAL/NTSC):
5.43.1.
704 x 576/480 4CIF: 25/30 ips
5.43.2.
352 x 288/240 CIF: 25/30 ips
5.45. The camera shall allow the use of C or CS Mount type lenses.
5.46. The camera shall accept fixed iris lenses, manual iris lenses, DC autoiris lenses, and video-iris lenses. For ease of installation, the camera shall
auto detect the type of lens used and optimize performance accordingly.
Page 44 of 56
5.47. The camera shall provide a lens wizard during lens back focus setup to
allow focusing at maximum lens opening to ensure the object of interest within
the field of view always remains in focus.
5.49. The camera shall provide a feature (SensUP) that enhances camera
sensitivity by increasing the integration time on the CCD (lowering shutter
time from 1/50 s to 1/5 s PAL; 1/60 s to 1/6 s - NTSC).
5.50. The camera shall provide enhanced night viewing through the increase
of IR sensitivity by automatically switching a motorized IR filter from colour to
monochrome operation in low-light or IR illuminated applications. The IR filter
shall also be switched manually via the alarm input, or pre-programmed in the
camera mode or profile.
5.51. The camera shall utilize XF-Dynamic technology to extend the dynamic
range of the camera to provide a sharper image, simultaneously, in both the
high-light and low-light areas of the scene.
5.52. The camera shall utilizes 2 X-Dynamic technologies to extend the
dynamic range of the camera to provide a sharper, more detailed image for
increased accuracy in colour reproduction in harsh lighting conditions.
privacy mask areas.
changes.
Page 45 of 56

5.57.1.
identification.
5.57.2.
5.57.3.
protection.
connection.
5.63. The camera shall utilize pixel-by-pixel analysis to automatically
compensate for bright areas of a high contrast scene (Back light) without
having to define a window or area. Backlight compensation shall work in
conjunction with dynamic range.
5.64.1.
5.64.2.
5.64.3.
green and blue.
Page 46 of 56

5.65.1.
Color bars 100%
5.65.2.
Grayscale 11-step
5.65.3.
Sawtooth 2H
5.65.4.
Checker board
5.65.5.
Cross hatch
5.65.6.
UV plane

Colour
Monochrome
2.4 lx (0.223fc)
0.98 lx (0.091 fc)
a.
Full Video
(100 IRE)
b.

(50 IRE)
0.188 lx (0.0174 fc)
c.

(30 IRE)
0.060 lx (0.0056 fc)

5.69.1.
5.69.2.
selectable.
5.70. The IP camera shall support the following audio standard /

compression:
5.70.1.
5.70.2.
5.70.3.
Vpp max.
5.70.4.
Page 47 of 56
5.72.1.
113F)
5.72.2.

5.73.1.
(CE), EN55024 (24 VAC)
5.73.2.
Page 48 of 56

5.76.1.
5.76.2.
selectable.

5.77.1.
131F)
5.77.2.

5.78.1.
EMC immunity: EN50130-4 (CE), EN50121-4 (CE)
5.78.2.
EMC emission: EN55022 class B, FCC part 15 class B,
EN6100-3, EN50121-4
Page 49 of 56
6.
High Performance Video Decoder.
6.1. The HD decoder shall be capable of decoding high definition and

standard definition streams using H.264 compression technology at up to 30
ips.
6.2. The HD decoder shall be capable of decoding two (2) full HD 1080p30
streams or four (4) HD 720p30 streams with up to 10 Mbps each.
6.3. The HD decoder shall be capable of decoding six (6) standard
definition streams with up to 6 Mbps each or up to 30 video streams at a lower
resolution.
6.4. The HD decoder shall be capable of directly driving an HD display
device.
6.5.
The HD decoder shall support the following security options:

6.5.1. Two (2) levels of password protection to prevent unauthorized
connection or configuration changes to the unit.
6.5.2. [Independent AES encryption with 128-bit keys for each
protection.
6.6. The HD decoder shall be capable of decoding the following stream

options:
6.6.1. Four (4) H.264 720p30 streams at 10 Mbps
6.6.2. Two (2) H.264 1080p30 streams at 10 Mbps
6.6.3. Six (6) H.264 standard definition streams at up to 6 Mbps
6.6.4. Twelve (12) H.264 standard definition streams at up to 2.5 Mbps
6.7. The HD decoder shall provide one (1) DVI-I, one (1) HDMI, and one
(DP) monitor outputs (only one output can be used at a time).
6.8. The HD decoder shall be capable of displaying four (4) high definition
streams (720p30) in a quad-view display.
6.9. The HD decoder shall be capable of switching screen layouts based on
the controlling video management system or on alarm scenarios.
7.
8.
High Performance Video Transcoder.

Monitor Display.
Page 50 of 56
8.1.
The HD monitor shall support Full HD 1080p resolution (1920 x 1080).
8.2.
The HD monitor shall offer an LED backlight panel.
8.3.
The HD monitor shall have a viewable picture area of 42 inches.
8.4. The HD monitor shall automatically focus on setting the correct color,
temperature, and gamma curve settings.
8.5.
The HD monitor shall display images using an aspect ratio of 16:9.
8.6. The HD monitor shall offer an active display area of (H) 930.24 mm x
(V) 523.26 mm (36.6 x 20.6 in.).
8.7.
The HD monitor shall be capable of displaying 1,073 million colors.
8.8.
The HD monitor shall provide 500 cd/m2 luminance.
8.9.
The HD monitor shall provide a 4,000:1 contrast ratio.
8.10. The HD monitor shall offer 178 horizontal and vertical viewing angles.
8.11. The HD monitor shall have the following video connections:
8.11.1.
One looping composite video (BNC) input.
8.11.2.
One looping composite video (BNC) output.
8.11.3.
One digital DVI-D input.
8.11.4.
One digital HDMI input.
8.11.5.
One analog RGB (VGA) input.
8.11.6.
One analog RGB (VGA) output.
8.11.7.
One component (Y, Pb, Pr) input.
8.11.8.
One looping Y/C (S-video) input.
8.11.9.
One trigger input.
8.12. The HD monitor shall have the following audio connections:
Page 51 of 56
8.12.1.
Two RCA audio inputs (left/right).
8.12.2.
One phono jack input.
8.12.3.
One RCA audio output (left/right).
8.12.4.
One speaker output.
8.13. The HD monitor shall provide a rear control panel that allows the user
to adjust image quality, brightness, size, position, and geometry for optimal
viewing.
8.14. The HD monitor shall provide a rear control lockout feature so that only
authorized users can adjust menu settings.
8.15. The HD monitor shall have front panel LED indicators that convey the
state of the monitor.
8.16. The HD monitor shall automatically adapt to fluctuating electricity loads.
8.17. Environmental:
8.17.1.
Operating Temperature: 0
8.17.2.
Humidity: Maximum 0% to 90% relative
to +50 C (32
to 122 F)
Page 52 of 56
8.18. The HD monitor shall support Full HD 1080p resolution (1920 x 1080).
8.19. The HD monitor shall offer an LED backlight panel.
8.20. The HD monitor shall have a viewable picture area of 55 inches.
8.21. The HD monitor shall automatically focus on setting the correct color,
temperature, and gamma curve settings.
8.22. The HD monitor shall display images using an aspect ratio of 16:9.
8.23. The HD monitor shall offer an active display area of (H) 1209.6 mm x
(V) 648.4 mm (47.6 x 25.5 in.).
8.24. The HD monitor shall be capable of displaying 1.073 million colors.
8.25. The HD monitor shall provide 450 cd/m2 luminance.
8.26. The HD monitor shall provide a 4,000:1 contrast ratio.
8.27. The HD monitor shall offer 178 horizontal and vertical viewing angles.
8.28. The HD monitor shall have the following video connections:
8.28.1.
One looping composite video (BNC) input.
8.28.2.
One looping composite video (BNC) output.
8.28.3.
One digital DVI-D input.
8.28.4.
One digital HDMI input.
8.28.5.
One analog RGB (VGA) input.
8.28.6.
One analog RGB (VGA) output.
8.28.7.
One component (Y, Pb, Pr) input.
8.28.8.
One looping Y/C (S-video) input.
8.28.9.
One trigger input.
8.28.10.
One 100-240 VAC power input.
8.29. The HD monitor shall have the following audio connections:
Page 53 of 56
8.29.1.
Two RCA audio inputs (left/right).
8.29.2.
One phono jack input.
8.29.3.
One RCA audio output (left/right).
8.29.4.
One speaker output.
8.30. The HD monitor shall provide a rear control panel that allows the user
to adjust image quality, brightness, size, position, and geometry for optimal
viewing.
8.31. The HD monitor shall provide a rear control lockout feature so that only
authorized users can adjust menu settings.
8.32. The HD monitor shall have front panel LED indicators that convey the
state of the monitor.
8.33. The HD monitor shall automatically adapt to fluctuating electricity loads.
8.34. Environmental:
8.34.1.
Operating Temperature: 0
8.34.2.
Humidity: Maximum 0% to 90% relative
to +50 C (32
to 122 F)
Page 54 of 56
9.
Equipment Rack.
9.1. The Tenderer shall provide sufficient 19 equipment rack to house the
security equipment system. There shall be at least 20% spare rack capacity in
the equipment racks to cater for future expansion.
9.2.
The rack shall conform to ANSI / EIA-310-D standard.
9.3. The equipment mounting shall have metallic bar straps for grouping
purpose.
9.4. The rack shall include locks for the front, rear and side panels and are
keyed the same.
9.5.
The rack shall have movable frames with detachable panels.
9.6. The rack shall consist of removable fan tray with sufficient fans for
ventilation.
9.7. The rack shall have an attached power bar on the side of the rack with
at least 8 nos. 230VAC, 13A power supply. Each power distribution outlet
shall be equipment with surge protector and integrated Earth Leakage Circuit
Breaker (ELCB).
9.8.
The rack shall be equipped with patch panel for security LAN system.
Page 55 of 56
10.
Lightning Protection.
10.1. The Tenderer shall supply, install, test and commissioning for the
lightning protection for the CCTV system.
10.2. The lightning protection system shall be installed in accordance with
the code of practice for lightning protection. [Insert the country code of
practice for lightning protection]
10.3. Lightning protection system is provided to prevent damage to any
outdoor equipment and equipment installed in the building.
10.4. The Tenderer shall provide proper connection for any outdoor
equipment by copper tapes. All connection between any existing lightning
protection and outdoor equipment by copper tapes shall be made by 25mm x
3mm high conductivity, soft annealed copper tapes secured at a maximum of
1000mm intervals and bi-metallic connectors.
10.5. All video and control cable shall be protected against line surge due to
lightning or unforeseen circumstances. All power supply shall also be
protected against line surges.
10.6. Outdoor equipment shall be protected against line surges through
video, control and power cables.
Page 56 of 56

CCTV Tech WriteUp

Transféré par

Informations du document

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

CCTV Tech WriteUp

Transféré par

Droits d'auteur :

Formats disponibles

Spec_BVMS_VRM_Ver3.1.05.

Regional Sales Office APR

Video Surveillance System

Video Surveillance System

Regional Sales Office APR

1.3.4. Digital Video Storage Subsystem (DVSS) as called for in the

Video Surveillance System

Regional Sales Office APR

1.7. The VSS shall be designed to provide control, integration and

Video Surveillance System

Regional Sales Office APR

Video Surveillance System

Regional Sales Office APR

Video Management System (VMS).

2.1.5. The Management Server software shall provide management,

Data stream management.

Video Surveillance System

Regional Sales Office APR

Video Surveillance System

Regional Sales Office APR

Video Surveillance System

Regional Sales Office APR

Priority for pan/tilt/zoom control

Rights for exporting video,

Access rights to system event log files.

Video Surveillance System

Regional Sales Office APR

Analog monitor support

Mobile video service.

Video Surveillance System

Regional Sales Office APR

Relays and Inputs / Outputs.

Video Surveillance System

Regional Sales Office APR

The logbook database shall use 64 bits indexing.

Video Surveillance System

Regional Sales Office APR

Video Surveillance System

Regional Sales Office APR

Logical Tree customized per user group.

Access rights to system event log files.

Dual Authorization user groups may be created.

Video Surveillance System

Log on either individually or as part of the logon

Or log on only as part of the logon pair.

Regional Sales Office APR

Alarm Handling and Management.

Video Surveillance System

Regional Sales Office APR

Video Surveillance System

Regional Sales Office APR

Operator Client Requirement.

Video Surveillance System

Regional Sales Office APR

Video Surveillance System

Regional Sales Office APR

Control the current image pane selection.

Control the AMGs or any image pane.

Control PTZ operation of the selected cameras.

Video Surveillance System

Regional Sales Office APR

Support jog-shuttle emulation during playback control.

Single step forward

Single step reverse