TECHNICAL SPECIFICATIONS
PART 1 - EXECUTIVE SUMMARY
The Norwalk Transit District (Owner) is seeking proposals from qualified contractors for
a complete turnkey video over IP Surveillance System.
The installation location is as follows:
Norwalk Transit District Video Surveillance System Upgrade
275 Wilson Avenue
Norwalk, CT 06854
Attention: Mr. Louis Schulman
A Mandatory Pre-Proposal Conference will be held on Wednesday, June 20, 2012 at
1:00 PM during which time documentation will be reviewed and a question and answer
session will be held to address issues related to this RFP and other matters germane to
this project, as outlined in the sections below.
The Contractor must insure that the Norwalk Transit District is not defaced in any way
during the course of the project but that all materials used are aesthetically and
architecturally compatible with the building.
As part of the proposal process, proposers will be asked to submit samples of materials
that they propose using such as wire mold, camera mounts, wireless access points,
NEMA enclosures as appropriate.
While a detailed list of the requirements and design parameters are presented below
with the intention that proposers follow them, the Norwalk Transit District is open to
alternative recommendations for accomplishing the stated goals if the proposer can
demonstrate that such alternatives would provide a significant value-add to the project
when completed. However, 100 percent compatibility and the open system concept must
be maintained with any existing system.
The system must be entirely IP based. The use of converters, mux devices and IP to
serial converters is excluded from this proposal. The system must meet the
requirements for video digital recording as stated in exhibit A. The storage capacity
should be 30 days for all cameras attached to the system at 5 frames per second and
assuming 25 % motion. The data storage server should be sized appropriately to
accomplish these needs.
Division 28 Electronic Safety and Security
Level 1 28 20 00 Electronic Surveillance
Level 2 28 23 00 Video Surveillance
Level 3 28 23 29 Video Surveillance Remote Devices and Sensors
PRODUCTS - GENERAL
A. Part number(s) and specifications for the products are accurate at the time of
Page 1 of 34
writing; they are subject to change by the manufacturer at any time. All systems and
components shall have gone through a documented quality assurance process by the
manufacturer. The manufacturer’s warranty, extended warranty and replacement
policies shall be included for each specified component.
B. The High Definition H.264 Day/Night IP Camera Series and related components
shall be installed and commissioned by authorized integrators certified by the
manufacturer. Certification and training for authorized integrators shall be available
from the manufacturer.
C. The manufacturer shall have a dedicated professional services group providing
Integrators and End Users the following fee-based services, including but not limited
to: training, installation, commissioning, remote diagnostics and integration with 3rd
party software and hardware systems.
DESCRIPTION
A. The High Definition H.264 Day/Night IP Camera Series (including 2.0MP-HDH264-B1):
1)
shall support 100BASE-TX and PoE 802.3af network interfaces for
streaming video and control data over standards compliant networks;
2)
shall operate in the Avigilon Control Center (ACC) environment with
support for automatic detection of cameras, encoders and NVRs in the
same broadcast domain;
3)
shall be ONVIF compliant;
4)
shall have multi-streaming support including different frame rate, bit rate,
resolution, quality and compression format from an individual camera;
5)
shall have a built-in web server to make video and configuration available
in a standard browser environment; the built-in web server shall support
multiple users with different permission levels and unique usernames and
passwords;
6)
shall support user configuration of network parameters including: Static IP
address, Subnet Mask, Gateway, and Control Port for control
communications;
7)
shall support user configuration of camera parameters including: Camera
Name, Location and Logical ID;
8)
shall support user configuration of image acquisition parameters
including: Exposure Control, Flicker Control, Iris Control, Day/Night
Control, White Balance Control, Color Saturation and Sharpening;
9)
shall support a mode that automatically removes the IR filter and enters a
monochrome mode when the available light drops below a set threshold;
10)
shall support user configuration of an unlimited number of independent
motion detection zones within the camera field of view;
11)
shall support user configuration of up to 3 privacy zones within the
camera field of view;
12)
shall support remote zoom and focus control of the lens and performing
automatic focus;
13)
shall support user configuration of compression format, compression
quality, maximum bit rate, key frame interval, and image rate per
individual camera;
Page 2 of 34
14)
15)
16)
17)
18)
19)
shall have input/output terminals for connecting alarm inputs and alarm
outputs;
shall have an audio input for connecting external microphones;
shall have a video output for connecting external monitors;
shall support UDP transport;
shall be remotely upgradeable over an IP network for feature
enhancements and investment protection; and,
shall meet or exceed the following design and performance specifications.
B. High Definition H.264 IP Camera Specifications (Model # 2.0MP-HD-H264-B1
and other Megapixel Cameras as specified:
1)
Image Sensor: 1/2.7” progressive scan CMOS
2)
Active Pixels: 1920 (H) x 1080 (V)
3)
Imaging Area: 5.9 mm (H) x 3.3 mm (V); 0.231" (H) x 0.129" (V)
4)
Minimum Illumination: 0.4 lux (F1.6) in color mode; 0.04 lux (F1.6) in
monochrome mode
5)
Dynamic Range: 69 dB
6)
Lens: 4.7-84.6 mm, F1.6, auto iris, remote focus and zoom
7)
Angle of View: 4° - 64°
8)
Image Compression: H.264 (MPEG-4 Part 10/AVC), Motion JPEG
9)
Image Rate: 30 (all resolutions)
10)
Resolution Scaling: Down to 352 x 240
11)
Motion Detection Selectable sensitivity and threshold
12)
Electronic Shutter: Automatic, Manual (1/30 to 1/8000 sec)
13)
Iris Control: Automatic, Manual
14)
Day/Night Control: Automatic, Manual
15)
Flicker Control: 50 Hz, 60 Hz
16)
White Balance: Automatic, Manual
17)
Privacy Zones: Up to 3 zones
18)
Audio Input Line input, A/V mini-jack (3.5 mm)
19)
Audio Compression Method: G.711 PCM 8kHz
20)
Video Output NTSC/PAL, A/V mini-jack (3.5 mm)
21)
I/O Terminals: Alarm In, Alarm Out; terminal strip
C. Electrical Specifications:
1)
Power Source: PoE: IEEE 802.3af Class 3 compliant 24 VAC, 12 VDC
2)
Power Consumption: 6W maximum
3)
Power Connector: 2 pin terminal block
D. Network Specifications:
1)
Network: 1000BASE-TX 1000baseFX between switches
2)
Cabling: CAT6
3)
Connector: RJ-45
4)
API: ONVIF compliant (www.onvif.org)
5)
Security: Password protection, HTTPS encryption, digest authentication,
WS authentication, user access log
6)
Protocols: IPv4, HTTP, HTTPS, SOAP, DNS, NTP, RTSP, RTCP, RTP,
TCP, UDP, IGMP, ICMP, DHCP, Zeroconf, ARP
7)
Streaming Protocols: RTP/UDP, RTP/UDP multicast, RTP/RTSP/TCP,
RTP/RTSP/HTTP/TCP, RTP/RTSP/HTTPS/TCP, HTTP
Page 3 of 34
E. Physical and Environmental Specifications:
1)
Dimensions: 156 mm x 69 mm x 54 mm; 6.1” x 2.7” x 2.5”
2)
Weight: 0.56 kg (1.2 lbs)
3)
Camera Mount: 1/4” UNC-20 (top & bottom)
4)
Operating Temp: -10°C to +50°C (14°F to 122°F); -10°C to +45°C (14°F
to 113°F) (with 12 VDC power source)
5)
Storage Temp: -10°C to +70°C (14°F to 158°F)
6)
Humidity: 20 - 80%, relative humidity (non-condensing)
F. Certifications and Regulations:
1)
FCC, Class B
2)
CE, Class B
3)
UL/cUL Listed
G. Warranty:
1)
36 months, parts and labor
H. Part Numbers and Accessories:
1)
2.0MP-HD-H264-B1 2.0 Megapixel, High Definition H.264, Day/Night, IP
Camera
Cameras that are placed in areas such as the entrance license plate shots that are not
accessible to cabling must be installed using a wireless Ethernet system. The link must
be a spread spectrum point to point Ethernet wireless link. All traffic from the access
point to the video server must be encrypted end to end.
PART 2 - GENERAL SUMMARY
2.1. WORK NEEDED AND REQUIREMENTS
The installation of IP video cameras both interior and exterior will be performed at
locations provided during the walk through and subsequently by floor plans provided. All
exterior cameras will be placed in such a manner as that roof lines will be visible when
possible. All cameras will be mounted in such a way that will minimize vandalism to the
device. The use of vandal resistant or vandal proof housings must be included in the
proposal. Interior cameras will be mounted in such a way that they will pose no hazard
and grant a full view of the area specified for coverage. Recessed ceiling mounts should
be used when possible.
There is a requirement for the installation of Category 6 cabling to support each
camera’s installation point. It is the vendor’s responsibility to integrate a new VLAN into
the existing switching infrastructure to support the camera installation. New switches will
be required at each network closet. This network will run independently of the existing
network infrastructure but must be integrated into the current infrastructure. It is the
vendor’s further responsibility to insure enough Ethernet ports are available in the
existing infrastructure and to integrate the cameras within that infrastructure. A fiber
connection will be required between closets to insure the VLAN separation the network
will require. And that network routing and quality of service for video traffic be integrated
into the new VLAN as well as the existing network infrastructure. It is further understood
that the cameras will be available for viewing anywhere on the existing LAN/WAN. A
Page 4 of 34
mobile gateway must be integrated into the solution and all firewall configurations must
be performed to accomplish this task. The vendor must have and use manufacturer
certified technicians to perform the network integration. The vendor must submit a
detailed plan of how they will achieve the network integration once the project is
awarded and before any work can commence.
Current required Certifications include the following Manufacturers: Fortinet and HP.
There is a requirement to provide patch cords for the installation. Patch cable count
should include one 3 foot cable for connection between the switching infrastructures and
patch panel. Also a 7 foot Cat 6 patch cable should be provided at each camera location.
All areas are constructed or have been refurbished with modern construction materials.
The cabling system specified in this document shall be an end-to-end solution that is
sourced from a single manufacturer or partnered manufacturers.
The work shall include but not be limited to the following. Provide and install:
1)
2)
3)
4)
5)
6)
7)
8)
9)
10)
11)
12)
13)
14)
15)
16)
17)
18)
Horizontal cabling,
Equipment enclosures,
Termination blocks, patch panels and hardware,
Cable management accessories,
Connectors and jacks,
Connector faceplates and mounting accessories,
Raceways and/or cable trays, J-hooks/cable hangers,
Labeling of all installed work,
Testing and Certification of cables,
Fire stopping,
Network programming,
VLAN configuration,
Camera and mount installation,
Camera Patrol schemes for different time intervals,
Configuration of the video recorder with network access and with all
cameras on the network,
Installation and update to latest patch levels of all software,
Installation of virus protection or proof of network isolation of the server
and camera network, and,
Routing and wireless configuration as required.
As-Built records/diagrams will be required at the completion of this project in both digital
and hard copies in a format acceptable to both parties.
The following will also be required by the Owner as part of the project:

Detailed schedule of work including start dates and end dates. Upon award of
contract, and prior to the start of any work, the Contractor will consult and
coordinate with the Owner, to complete an industry standard project schedule
and checklist, such as the AIA’s Form D200. Upon start of work, weekly
schedules will be required to be submitted to the Owner. A weekly project
Page 5 of 34
meeting will be held at a time and place agreeable to all parties. Weekly
schedules will be submitted to the Owner at these weekly meetings.

Furnish as built drawings and 3 copies of Certification results.
2.2 QUALIFICATIONS
A. The selected Contractor shall have a proven track record in the field of the
specified project. Personnel shall be competent and qualified by experience and
training for installation of the systems.
B. Contractor must provide a cover letter with the name, legal status (e.g.,
corporation, sole proprietor, etc.) address, and telephone number of the legal
entity with whom the Owner may execute any Master Contract arising from this
RFP.
C. In addition, please respond to the following:

State whether Contractor has been doing business under another name
during the past five (5) years. If so, provide the name(s) and addresses.

Has Contractor been cited by OSHA/WISHA for any safety violations in the
last five (5) years? If yes, provide details of the citation(s). If no, so declare.

Has Contractor been cited by the State of Connecticut Department of Labor
for any violations in the last five (5) years? If so, submit full details including
the project, the number of violations and any penalties incurred. If no, so
declare.
D. The selected Contractor must list all Subcontractors they intend to use in
connection with this RFP. Subcontractors must comply with and provide all
information requested in this section. The successful vendor shall not employ
any Subcontractor to fulfill any of the duties as herein specified without express,
prior written approval by the Owner.
E. The successful vendor must have under its employ 2 Certified Network
Technicians including CCNA and CCDA, 2 Wireless Certified Technicians, 2 IP
Video Surveillance Software Certified Technicians, 2 IP Camera Certified
Technicians, and 1 Microsoft Certified Professional. The vendor must have the
ability to respond onsite to emergencies within 2 working hours. The vendor
must have 24 x 7 Network Operations Center facilities and the ability to remotely
manage the installed equipment. The vendor shall possess the ability for the
Owner, through web access, to view purchased equipment and warranty dates.
The Owner must be able to place and review project and service requests via a
web page. The vendor should optionally provide management services to
facilitate RMA Replacement, warranty replacement, equipment and or circuit
failures.
2.3 CODES AND STANDARDS
A. All products, services and materials provided and performed under the scope of
this project shall conform to the following codes and standards, where
Page 6 of 34
applicable.
1) Telecommunications Industries Association/Electronic Industries Association
(TIA/EIA)
a) TIA/EIA-568-B.2 Commercial Building Telecommunications Cabling
Standard Part 2: Balanced Twisted-Pair Cabling Components
b) TIA/EIA-568-B.2-1 Commercial Building Telecommunications Cabling
Standard Part 2: Balanced Twisted-Pair Cabling Components –
Addendum 1 – Transmission Performance Specifications for 4-Pair 100
ohm Category 6 Cabling
c) TIA/EIA-568-B.2-2 Commercial Building Telecommunications Cabling
Standard Part 2: Balanced Twisted-Pair Cabling Components –
Addendum 2 – Revision of Sub-clauses
d) TIA/EIA-568-B.2-3 Commercial Building Telecommunications Cabling
Standard Part 2: Balanced Twisted-Pair Cabling Components –
Addendum 3 – Additional Considerations for Insertion Loss & Return Loss
Pass/Fail Determination
e) TIA/EIA-568-B.2-4 Commercial Building Telecommunications Cabling
Standard Part 2: Balanced Twisted-Pair Cabling Components –
Addendum 4 – Solderless Connection Reliability Requirements for
Copper Connecting Hardware
f) TIA/EIA-568-B.2-5 Commercial Building Telecommunications Cabling
Standard Part 2: Balanced Twisted-Pair Cabling Components –
Addendum 5 – Corrections to TIA/EIA-568-B.2
g) TIA/EIA-568-B.2-6 Commercial Building Telecommunications Cabling
Standard Part 2: Balanced Twisted-Pair Cabling Components –
Addendum 6 – Category 6 Related Component Test Procedures
h) TIA/EIA-568-B.2-11 Commercial Building Telecommunications Cabling
Standard Part 2: Balanced Twisted-Pair Cabling Components –
Addendum 11 - Specification of 4-Pair UTP and SCTP Cabling
i) TIA-569-B Commercial Building Standard for Telecommunications
Pathways and Spaces
j) TIA/EIA-606-A Administration Standard for the Telecommunications
Infrastructure of Commercial Buildings
k) J-STD-607-A Commercial Building Grounding (Earthing) and Bonding
Requirements for Telecommunications
2) Institute of Electrical and Electronic Engineers (IEEE)
a) IEEE 802.3
3) National Electrical Code
a) Article 800 Communications Circuits
4) National Electrical Manufacturers Association (NEMA)
5) National Fire Protection Association
a) NFPA 70 National Electrical Code
b) NFPA 75 Protection of Electronic Computer 1 Data Processing
Equipment
6) Safety and Health Standards
a) OSHA 29 CFR 1926/1910
7) Underwriters Laboratories, Inc.(UL) Listed and UL Approved
Where a conflict exists, local codes, ordinances, and building officials will
supersede all other requirements.
Page 7 of 34
B. All products, services and materials provided and performed under the scope of
this specification shall conform to manufacturer’s recommendations.
C. The Contractor shall obtain all necessary and required permits. All work shall
conform to applicable building, safety and fire codes.
2.4 SUBSTITUTIONS, DEVIATIONS, AND CHANGES
A. Any proposed substitution in whole or part, must be submitted in writing for
review and approval by the Owner or it’s Representative.
B. Certify in writing that any substituted components will meet or exceed the
specification requirements and system performance detailed in this
specification. The Owner or its Representative reserves the right to reject for
any reason, at its sole discretion, any substitution on the grounds of adherence
to standards, quality, performance, utility, function and/or appearance.
2.5 SYSTEM TESTING
A. A test demonstration day shall be arranged by the contractor for the purpose of
demonstrating and agreeing to the test procedures, equipment to be used, and
format of test results. The test demonstration shall cover all tests to be
performed. The Owner and Owner’s representative shall attend this test
demonstration day.
B. Perform tests following installation and termination to ensure that the cabling
plant and associated components conform to this specification.
C. If a component fails a particular test, rectify, rework or replace the component.
D. Re-test the component and associated link once the component has been reworked or replaced. This process shall continue until the component and
associated link/channel passes all relevant tests.
F. Acceptance in writing will occur only after the project is fully completed and
tested in accordance with the procedures outlined below and mutually agreed
upon by both the contractor and the Owner and to the satisfaction of the Owner
or its duly authorized representative.
2.6 WARRANTY
A.
Contractor shall provide an extended performance warranty for the end-to-end
solution including cables, connectors, patch panels and all other termination
hardware. The vendor must state the warranty in his RFP reply.
2.7 JOB CONDITIONS
A. Site Survey (Pre-Proposal Conference)
Prior to submitting proposals, all potential Contractors will be required to attend a
mandatory Pre-Proposal Conference in order to survey all areas of the project to
Page 8 of 34
locate raceways, hand-holes, presets, furniture openings, sleeves, conduits,
cable trays, conduit stub-ups, and back boxes, pull boxes ladder racks, cable
trays, cable ties, and cable hangers cameras.
B. Work Impact
1) The Owner desires to have all work completed during normal business hours;
however, after hours work may be permitted under terms and conditions
specified by the Owner.
2) The Contractor will be required to work with the Owner to ensure interruptions
to existing services are minimal or avoided. The Contractor will not
discontinue any existing network services without first obtaining approval
from the Owner.
C. Cleanup and Damage to Existing Equipment
1) The Contractor will be responsible for any costs required to replace, repair or
restore any equipment, property or finishes that are damaged as a result of
the Contractor’s actions or negligence during the course of the project.
2) The Contractor will be responsible for daily cleanup in all areas in which work
is being performed, including reinstallation of all equipment disturbed during
the work activity. Garbage will not be allowed to be stored or accumulated in
any area, and must be removed from the site on a daily basis. Ceiling tiles
are not to be left open in areas where work is not actively being performed.
Ceiling tiles must not be left open overnight and must be installed in all areas
at the completion of each work day.
2.8 SUBMITTALS
A. Pre-Construction - The following documents must be submitted by the contractor
prior to commencing construction:
1) Product Data Sheets
2) Manufacturer Product and Application Warranty
3) Network nitration plan with prebuilt configurations.
B. Post-Construction
1) Field Tests Reports (in electronic format and hardcopy)
2) As-Built Drawings (in electronic format and hardcopy)
2.9 SUBMITTALS - GENERAL PROCEDURES
A. General
1) Do not commence work that requires review of any submittals until receipt of
returned submittals with appropriate final action.
2) Any illegible submittals will be rejected
2.10 PRODUCT DATA/WARRANTY SHEETS
A. Submit manufacturer's product data/warranty sheets for each component of the
project. Certify that the data sheets depict the components to be installed to
make up the complete system as described in this specification. The Product
Data/Warranty Sheet submittal shall consist of the following:
 Cover Sheet
Page 9 of 34







B.
Project name and address
Number of submittal
Date of submittal
Name and address of the Communications Contractor
Table of contents
Product name and manufacturer
Page number(s)
Preparation and Transmittal
Submit all product data sheet submittals for each system, subsystem, or unit
of work as one submittal.
2.11 QUALITY ASSURANCE AND FACTORY TESTS
A.
Contents: Each factory test submittal shall consist of the following:

Cover Sheet

Project name and address

Number of submittal.

Date of submittal.

Name and address of the Contractor.

Table of contents

Product name and manufacturer.

Page number(s).

Page number(s) of the corresponding Specification or Drawing
number(s) of the corresponding Contract Drawings
B.
Quality Assurances
New and best of their respective kind, free from defects and listed by
Underwriters Laboratories for the intended use and bearing their label.
C.
Preparation and Transmittal
Submit all factory test submittals for each system, subsystem, or unit of work as
one submittal.
2.12 SHOP DRAWINGS
A.
Contents: Each shop drawing submittal shall consist of the following:
 Title Block
 Project name and address
 Number of submittal
 Date of submittal
 Name and address of the Contractor
 Drawing scale
1) Diagrams showing evidence of compliance with Contract Documents and
coordination with other trades.
2) Associated wiring diagrams of all equipment, with types and model numbers
specified under these Contract Documents.
3) Fully dimensioned housing and mounting drawings, including information on
Page 10 of 34
finishes.
4) Specific notation of field measurements at accurate scale.
5) Identification of specific products and materials used.
6) Cross-reference all related Contract Documents (drawings, detail numbers,
Specifications sections, etc.)
7) Compliance with specified standards.
8) Dimensions at accurate scale.
2.13 FIELD TEST REPORTS
A.
Contents: Each field test submittal shall consist of the following:
 Cover Sheet
 Project name and address
 Number of submittal
 Date of submittal
 Name and address of the Contractor
 Table of Contents
 Cable type and number
 Page number(s)
 Page number(s) of the corresponding Specification or Drawing number(s)
of the corresponding Contract Drawings.
 Cable test results as specified.
B.
Preparation and Transmittal
1)
All test results must be entered electronically in an MS Excel compatible
spreadsheet format.
2)
Submittal format
a. Soft copy: Excel compatible saved on CD-ROM.
b. Hard copy: Sheet size shall be 8 1/2" x 11"
c. Submit three (3) hard copies and one (1) soft copy on completion of
the testing.
2.14 AS BUILT PACKAGE (RECORD DOCUMENTS)
A.
Contents: Each field test submittal shall consist of the following:
 Title Block
 Project name and address
 Number of submittal
 Installation schedule, including all cross-connection and patching
schedule
 Date of submittal
 Name and address of the Contractor
 Drawing scale
 Floor plans indicating outlet locations and labels.
1) The as built drawings shall include, but are not limited to block diagrams,
frame and cable labeling, cable termination points, equipment room layouts
and frame installation details. The as-built documents shall include all field
changes made up to construction completion:
a. Station cable routing changes.
Page 11 of 34
b. Associated detail drawings.
c. Updated floor plans with the labels of new cables legibly noted.
d. Network changes and IP addresses of each device
B.
Preparation and Transmittal
1) Prepare as built packages in electronic and hardcopy format.
2) Space for action marking shall be adjacent to the title block.
3) Submittal format
a. Soft copy: electronic files saved on CD-ROM.
b. Hard Copy: Sheet size shall be 8 1/2" x 11"
c. Submit three (3) hard copies and one (1) soft copy on completion of
the testing
PART 3 - EQUIPMENT
3.1 CABLING
A.
Plenum rated, Category 6, 4-pair, UTP cable shall be used.
1) Each cable shall be a 4-pair, unshielded twisted-pair that meets or
exceeds the specifications for Category 6 cables detailed in the TIA/EIA
568-B-2.1- Commercial Building Telecommunications Standard: Part 2.1
Transmission Performance 4 pair 100 Ohm Category 6 Ethernet
2) UL listed, Type CMP.
3.2 CONNECTORS
A.
RJ45 Category 6 - UTP Connectors shall at a minimum conform to the
following specifications:
1) 100-Ohm Balanced Twisted-Pair Telecommunications Outlet/Connector
2) Each 4 pair cable shall be terminated on an 8 position modular jack, and
all UTP and ScTP telecommunications outlets shall meet or exceed the
requirements of IEC 60603-7, as well as ANSI/TIA/EIA 568-B.2 and the
terminal marking and mounting requirements of ANSI/TIA/EIA-570-A.
3) T568B will be employed for the new Category 6 data cables in this
project.
3.3 TERMINATION HARDWARE
A.
Patch Panels
1) Patch panels will be mounted in existing racks that are present in each of
the closets.
2) Patch panels can be provided in 24-port or 48-port sizes.
3) Patch panels must be Category 6, wired to TIA/EIA-T568B.
4) Mounting hardware must be provided.
5) Store cable reserve with no bends sharper than 2" bend radius.
6) Provide sufficient finger space to allow connectors to be mounted and
demounted readily.
7) Shall have sufficient space for labeling of each individual connector
8) Shall allow any individual cable to be terminated or otherwise handled
without disturbing other cables.
Page 12 of 34
3.4 CABLE MANAGEMENT AND ACCESSORIES
A.
Horizontal Wire Management Panels
1) EIA 19" rack mountable, 1 RU and 2RU high.
2) Provide front and rear cable organizers with minimum 5 support rings of
3.5" width protrusion minimum.
3) Provide snap on/off protective covers front and rear.
B.
Vertical Wire Management Panels
1) Provide front and rear cable organizers with the front having cable guides
at 1-RU spacing.
2) Provide snap on/off protective covers front and rear.
3.5 PATHWAYS
A.
Cable tray, raceway, J-Hooks, cable hangers, D-rings, Velcro straps and/or
equivalents shall be installed as required to properly support the structured
cabling system.
B.
Installation of wire mold or other exposed surface-mounted raceway must be
approved by the Owner in writing.
3.6 LABELING
A.
Labeling System
1) Labeling shall comply with EIA/TIA-606-A.
2) Labeling systems should be used for each of the following:
a. Horizontal cabling
b. Patch panels
c. Jacks/Connectors
d. Jack/Connector faceplates
3) All Ethernet jacks shall be clearly labeled with the appropriate jack
number. Each cable run must be labeled at its terminating jack faceplate
and at its corresponding patch panel port. Handwritten labels shall not be
permitted. Labeling convention shall be such that the Owner will be able
to identify the following information, at a minimum, from the applied label:
a. Closet number
b. Patch panel number.
c. Patch panel port number
3.7 FIRESTOP
A.
Firestop will be required as specified by code, local ordinance, or building
official at any existing or newly created penetration, sleeve, conduit or stub
that is occupied by newly installed cable(s), or that has had existing cable(s)
removed, or in any locations where the Contractor has removed previously
installed fire stop.
Page 13 of 34
PART 4 - WORK EXECUTION
4.1 GENERAL
A.
Delivery, Handling, and Protection
1) Installation shall include the delivery, unloading, setting in place, fastening
to walls, floors, ceilings, counters, or other structures where required,
interconnecting wiring of the system components, equipment alignment
and adjustments, and all other work whether or not expressly required
herein which is necessary to result in complete operational systems.
2) During the installation, and up to the date of final acceptance, th
Contractor shall be under obligation to protect his finished and unfinished
work against damage and loss. In the event of such damage or loss, he
shall replace or repair such work at no cost to the Owner.
3) Notify any discrepancies between specifications, drawings, field
conditions, and the manufacturer’s recommendations immediately in
writing
4.2 INSTALLATION
B.
Cable and Connecting Hardware Testing
1) Cables and connecting hardware shall as a minimum comply with
mechanical and electrical requirements of EIA/TIA-568-B.2.
2) The following field or factory component and full channel test results shall
be submitted for all cables and connecting hardware for approval.
a. Length (ft)
b. Wire map
c. Return Loss (dB)
d. Insertion loss (dB)
e. Near end crosstalk (NEXT) loss (dB)
f. Power sum near-end crosstalk (PSNEXT) loss (dB)
g. Equal level far-end crosstalk (ELFEXT) loss (dB)
h. Power Sum equal level far-end crosstalk (PSELFEXT) loss (dB)
i. Propagation delay for 4-pair horizontal cable (ns)
j. Propagation delay skew for 4-pair horizontal cable (ns)
k. Attenuation to crosstalk ratio (ACR)
l. Power Sum Attenuation to crosstalk ratio (PSACR)
4.3 PRICING
The Owner is seeking a single dollar amount addressing all labor, hardware, and
materials. The quote should be itemized in such a way that labor and all installation
items are separated with individual pricing. The Owner reserves the right to adjust
quantities either up or down and the quote should facilitate this process. The Contractor
will comply with all applicable wage requirements of State and Federal law.
4.4 DESIGNATED PERSONNEL
Upon award of this project the successful vendor will appoint a designated project liaison
to work with the Owner’s representatives. This designated representative will be
responsible for working with the Owner regarding any and all issues related to this
Page 14 of 34
project.
4.5 CLARIFICATIONS
The Owner has presented this Technical Specification in good faith and has made every
effort to supply any and all required technical information. If, upon review, proposers
believe there to be any errors or inconsistencies it will be their responsibility to bring
them to the attention of the Owner in writing for written clarification prior to proposal
submission.
PART 5 - A&E SPECIFICATIONS - CSI MASTERFORMAT 2004
PRODUCT
Division 28
Level 1
Level 2
Level 3
Avigilon Control Center (ACC)
Network Video Management Software (NVMS) and NVR Hardware
Electronic Safety and Security
28 20 00 Electronic Surveillance
28 23 00 Video Surveillance
28 3 13 Video Surveillance Control and Management Systems
PRODUCTS
5.1 GENERAL
A. All systems and components shall have undergone a thoroughly documented
quality assurance process by the manufacturer. The manufacturer’s
warranty, extended warranty and replacement policies shall be included for
each specified component.
B. The Network Video Management Software, NVR Hardware and related
components shall be installed and commissioned by authorized integrators
trained and certified by the manufacturer. Certification and training for
authorized integrators shall be available from the manufacturer.
C. The manufacturer shall have a dedicated professional services group
providing Integrators and End Users the following fee-based services
including but not limited to: training, installation, commissioning, remote
diagnostics and integration with 3rd party software and hardware systems.
5.2 DESCRIPTION
A. The Network Video Management Software (NVMS) shall be Avigilon Control
Center (ACC) version 4.8 or later. The NVMS shall be available as a standalone software offering or pre-loaded on turn-key workstations and servers
running Microsoft Windows with configurable storage.
B. The Network Video Management Software (NVMS) shall be an enterprise
level software solution that shall be scalable from one client, server, and
camera to hundreds of clients, servers, and cameras.
C. The Network Video Management Software (NVMS)shall consist of server
software applications and client software applications.
D. The Network Video Management Software (NVMS)shall include a gateway
software application that connects mobile devices to the NVMS.
Page 15 of 34
E. The Network Video Management Software (NVMS)shall be available in the
following language:
•
English
F. The Network Video Management Software (NVMS) shall include the
following applications:
•
Server Software Applications
• Control Center Server
• Control Center Admin Tool
• Control Center Gateway
• Client Software Applications
• Control Center Client
• Control Center Web Client
• Control Center Player
• Control Center Camera Installation Tool
G. The Network Video Management Software (NVMS) shall permit server and
client software applications to be installed and run on both the same
computer or on separate computers.
H. The Network Video Management Software (NVMS) shall support edge based
storage and processing of video and audio.
I.
The Network Video Management Software (NVMS) shall support High
Definition Stream Management (HDSM) architecture which includes:
•
Support for industry standard JPEG2000, MJPEG, MPEG-4, and
H.264 compression formats
• Support for reducing the required client bandwidth and processing
power by only transmitting what is necessary to view the video stream
at full quality (e.g. if a user is viewing a 16MP camera in a 1MP
window then a 1MP representation of the 16MP image shall be
transmitted).
J. The Network Video Management Software (NVMS) shall support recording
and management of video and audio sources including:
•
•
•
•
•
•
•
•
Avigilon HD IP Cameras (1 – 5 Megapixel)
Avigilon HD IP Dome Cameras (1 – 5 Mega pixels)
Avigilon Panoramic HD IP Dome Cameras (8 Megapixel)
Avigilon HD H.264 Day/Night IP Cameras (1– 2 Megapixel)
Avigilon HD H.264 Day/Night IP Dome Cameras (1– 2 Megapixel)
Avigilon HD PRO IP Cameras (2 – 16 Megapixel)
Composite video from analog cameras, PTZ domes and thermal
imagers via Avigilon ENC-4PORT and ENC-4P-H264 analog
encoders
Third-Party IP Devices
• ACTi Cameras/Encoders
• Arecont Cameras
• Axis Cameras/Encoders
Page 16 of 34
•
IQInVision Cameras
• Mobotix Cameras
• ONVIF 1.00. 1.02, and 2.00 Cameras
• Panasonic Cameras
• Pelco Cameras
• Samsung Cameras
• Sanyo Cameras
• Sightlogix Cameras
• Sony Cameras
• VideoIQ Cameras
K. The Network Video Management Software (NVMS) shall support receiving
digital input triggers and triggering digital outputs through an I/O board.
L.
The Network Video Management Software (NVMS) shall support recording
and monitoring video and audio streams from sources with bandwidth up to
90 Mbit/sec, frame rate up to 60 fps, and video resolution up to 16 MP
(4872 x 3248).
M. The Network Video Management Software (NVMS) shall support the
decompression of H.264 video through the client graphics card instead of
using the client processing power.
N. The Network Video Management Software (NVMS) shall require no
proprietary recording hardware, no hardware multiplexer or time-division
technology for video and audio recording or monitoring.
O. The Network Video Management Software (NVMS) shall not limit the storage
capacity and shall allow for upgrades of recording capacity.
P. The Network Video Management Software (NVMS) shall digitally sign
recorded video and audio using 256-bit encryption so video can be
authenticated for evidentiary purposes.
Q. The Network Video Management Software (NVMS) shall securely transmit all
command and control data via TCP/IP using cryptographic keys based on
SSL to prevent eavesdropping or tampering.
R. The Network Video Management Software (NVMS) shall be installed on
systems which meet or exceed the manufacturer’s requirements found in this
link:
http://avigilon.com/support/req/
S.
The Network Video Management Software (NVMS) shall also be available in
turn-key NVR platforms utilizing enterprise-grade servers and workstations
pre-loaded with NVMS software and tested to manufacturer specifications for
deployment in enterprise applications.
T.
The Network Video Management Software (NVMS) shall be available in
either a licensed Enterprise or Standard edition.
U. The Network Video Management Software (NVMS) shall support integration
with the GE Security Facility Commander Wnx v7.x platform for Electronic
Access Control and Alarm Monitoring (Access System).
Page 17 of 34
•
Network Video Management Software (NVMS) will provide the
mechanism by which individual alarm(s) from the Access system can
be pre-selected and configured to be monitored and, in turn, trigger
event driven video operations
• The Network Video Management Software shall support software
level integration (via the Wnx API) with GE Facility Commander for
facilitating real-time response to monitored events processed by Wnx
v7.x. Alarm events. The API integration should include:
• Bi-directional alarm event processing for monitoring and
acknowledgement
• Receiving card access activity events
• Receiving digital input events
• Receiving intrusion zone events
• Occurrences for “Alarm” and “Reset” conditions for each of the preselected Access system alarms will be processed and managed from
the NVMS system’s Live View workspace that is reserved for
displaying alarm notifications in the alarm list message pane or from
the FCWnx alarm viewer. If the Alarm pane is hidden, the alarm can
be acknowledged from the Camera display tile.
• Once an Access system initiated alarm occurrence is acknowledged
from the NVMS system, it should be automatically acknowledged and
processed in the Access System alarm monitor queue without further
operator intervention.
V. The Network Video Management Software (NVMS) shall support integration
with Lenel OnGuard.
W. The Network Video Management Software (NVMS) shall support integration
with Cardax FT Command Center.
X. The Network Video Management Software (NVMS) shall support integration
with RS2.
Y. The Network Video Management Software (NVMS) shall support integration
with DSX.
Z.
The Network Video Management Software (NVMS) shall support integration
with Jacques VoIP Voice Communication System.
AA. The Network Video Management Software (NVMS) shall support
integration with Stentofon AlphaCom XE.
AB. The Network Video Management Software (NVMS) shall support integration
with DDS Amadeus.
AC. The Network Video Management Software (NVMS) shall support integration
with Software House CCure 9000.
AD. The Network Video Management Software (NVMS) shall be capable of being
upgraded from one version to another without having to uninstall the previous
version.
AE. The Network Video Management Software (NVMS) shall be capable of being
upgraded from Standard edition to Enterprise edition without having to
uninstall the application.
Page 18 of 34
AF. The Network Video Management Software (NVMS) shall automatically detect
if video or audio source firmware is out of date with respect to the current
installed software and upgrade it.
AG. The Network Video Management Software (NVMS) shall automatically
detect if client application software is out of date with respect to the current
installed server software and upgrade it.
AH. The Network Video Management Software (NVMS) shall run as a service
configured to automatically start when the server or workstation is powered
on and automatically recover from failure or attempted tampering.
AI. The Network Video Management Software (NVMS) shall allow system
administration, and live and recorded video and audio monitoring all from a
single client application that can be located anywhere on the network.
AJ. The Network Video Management Software (NVMS) shall automatically
discover all Control Center Server instances running on computers
connected to the same network as the Control Center Client.
AK. The Network Video Management Software (NVMS) shall provide a search
functionality to discover Control Center Server instances running on
computers connected on a different network segment than the Control Center
Client by using IP addresses or hostnames.
AL. The Network Video Management Software (NVMS) shall automatically
discover video and audio sources that are connected to the same network as
the Control Center Server.
AM. The Network Video Management Software (NVMS) shall provide a search
functionality to discover video and audio sources that are connected on a
different network segment than the Control Center Server.
AN. The Network Video Management Software (NVMS) shall provide the ability
to connect a video or audio source to multiple NVRs to achieve redundant
recording.
AO. The Network Video Management Software (NVMS) shall provide the ability
to create a failover connection for a video or audio source. If the NVR that the
video or audio source is connected to goes offline then the failover NVR will
take over the connection.
AP. The Network Video Management Software (NVMS) shall provide
administration of all system connections from a single window.
AQ. The Network Video Management Software (NVMS) shall support receiving
Simple Network Management Protocol (SNMP) messages from servers and
alert the user.
AR. The Network Video Management Software (NVMS) shall detect if the video
or audio signal is lost and alert the system administrator.
AS. The Network Video Management Software (NVMS) shall provide the
capability to rename all video and audio sources and NVRs.
AT. The Network Video Management Software (NVMS) shall record video and
audio streams based on a recording schedule that can be defined individually
Page 19 of 34
for each video source. The schedule shall be created with the following
parameters:
•
Recording Mode
• Continuous
• Motion
• Digital Inputs
• Alarms
• POS Transactions
• License Plates
• Time and Date Settings
• Daily
• Weekly
AU. The Network Video Management Software (NVMS) shall provide the ability to
manually trigger recording.
AV. The Network Video Management Software (NVMS) shall provide a pre-event
and post-event recording option.
AW. The Network Video Management Software (NVMS) shall provide a reference
frame recording option in the absence of events.
AX. The Network Video Management Software (NVMS) shall perform motion
detection on each individual video source with adjustable sensitivity,
threshold and detection zones.
AY. The Network Video Management Software (NVMS) shall provide the ability to
reduce the image rate of recorded video over time as a means of increasing
record time. The image rate shall be able to be reduced to one half or one
quarter of the original image rate. This setting can be configured separately
for each video source.
AZ. The Network Video Management Software (NVMS) shall provide the ability to
set a maximum recorded video retention time for each video source.
BA. The Network Video Management Software (NVMS) shall perform dynamic
bandwidth management to ensure that the total bandwidth does not overload
the system.
BB. The Network Video Management Software (NVMS) shall authenticate users
before granting access to the system. Access rights for each user can be
defined individually for each user, and shall include:
•
•
Viewing live images
• Using PTZ controls
• Locking PTZ controls
• Trigger manual recording
• Trigger digital outputs
• Listen to microphones
• Broadcast to speakers
Viewing recorded images
• Exporting images
Page 20 of 34
•
BC.
Backup recorded images
• Manage user sessions
• Connect and disconnect cameras
• Setup cameras
• Setup general settings
• Setup network settings
• Setup image and display settings
• Setup compression and image rate
• Setup image dimension settings
• Setup motion detection settings
• Setup privacy zone settings
• Setup manual recording settings
• Setup digital input & output settings
• Setup microphone settings
• setup speaker settings
• Setup servers
• Setup general settings
• Setup schedule settings
• Setup recording and bandwidth settings
• Setup user and group settings
• Setup alarm management settings
• Setup scheduled backup settings
• Setup POS transaction settings
• Setup email settings
• Setup rule engine settings
• View system log
• Access to individual video and audio sources
The Network Video Management Software (NVMS) shall provide the ability to
import members of Active Directory groups as users in the NVMS. Changes
made to members in the Active Directory are automatically synced with the
NVMS.
BD.
The Network Video Management Software (NVMS) shall optionally support
using Windows credentials to authenticate users.
BE.
The Network Video Management Software (NVMS) shall provide the ability to
create and schedule alarms.
BF.
The Network Video Management Software (NVMS) shall provide the ability to
schedule backups of recorded video with associated events to a local folder
or mapped network drive.
BG.
The Network Video Management Software (NVMS) shall provide the ability to
email users and system administrators when an event or system health error
occurs.
Page 21 of 34
BH.
The Network Video Management Software (NVMS) shall provide the ability to
schedule when email notifications are sent.
BI.
The Network Video Management Software (NVMS) shall provide the ability to
include camera images in email notifications.
BJ.
The Network Video Management Software (NVMS) shall maintain an event
log for the following events:
•
Server Events
• Server application starting up
• Server application shutting down
• Server application terminated unexpectedly
• Server application low on resources
• Server application installation error
• Licensed feature expires soon
• Licensed feature expired
• Database error
• Data initialization error
• Data volume failed
• Data volume recovered
• Data volume size reduced
• Data write error
• Data upgrade started
• Data upgrade completed
• Data upgrade failed
• Data recovery started
• Data recovery completed
• Data recovery failed
• Network connection found
• Network connection lost
• Network error
• Network error resolved
• Email send error
• Server hardware error
• Backup started
• Backup completed
• Backup failed
•
Device Events
• Connection created
• Connection removed
• Connection created to standby server
• Connection removed from standby server
Page 22 of 34
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Connection failure
Connection restored
Network packet loss unacceptable
Network packet loss acceptable
Motion detection started
Motion detection ended
Recording started
Recording ended
Recording interrupted
Recording resumed
Digital input activated
Digital input deactivated
Firmware upgrade started
Firmware upgrade completed
Firmware upgrade failed
User Events
•
•
•
User login
• User logout
• Server setting changed
• Device setting changed
• Device connected
• Device disconnected
• Digital output triggered
• Bookmark added
• Bookmark updated
• Bookmark deleted
• PTZ moved
• PTZ idle
• Export performed
• Speaker activated
• Speaker deactivated
Alarm Events
• Alarm acknowledged
• Alarm auto acknowledged
• Alarm triggered
• Alarm assigned
• Alarm unassigned
• Alarm purged
POS Transaction Events
• POS transaction started
• POS transaction ended
Page 23 of 34
•
BK.
POS transaction exception
• License Plate Recognition Events
• License plate detection started
• License plate detection ended
• License plate watchlist match
The Network Video Management Software (NVMS) shall have the capability
to schedule and execute any of the following actions in response to any of
the events listed above:
•
BL.
User Notification Actions
• Display on-screen message
• Send an email
• Play a sound
• Monitoring Actions
• Start live streaming video
• Device Actions
• Reboot camera
• Trigger digital output
• PTZ Actions
• Go to Preset
• Run a Pattern
• Set Auxiliary
• Clear Auxiliary
• Alarm actions
• Trigger an alarm
• Acknowledge an alarm
The Network Video Management Software (NVMS) shall provide the ability to
create customized on-screen messages and email notifications.
BM.
The Network Video Management Software (NVMS) shall provide a
maintenance log and audit trail of all system errors and events.
BN.
The Network Video Management Software (NVMS) shall provide the ability to
receive transaction information from point-of-sale sources.
BO.
The Network Video Management Software (NVMS) shall support multiple
encoding formats from point-of-sale sources.
BP.
The Network Video Management Software (NVMS) shall provide the ability to
monitor live and recorded transactions from point-of-sale sources with linked
video.
BQ.
The Network Video Management Software (NVMS) shall provide the ability to
generate events based on point-of-sale transaction exceptions.
BR.
The Network Video Management Software (NVMS) shall provide the ability to
define a region of an image where license plate detection is performed.
Detected license plates shall be stored along with the video data.
Page 24 of 34
BS.
The Network Video Management Software (NVMS) shall provide the ability to
create a watchlist that will be used to create events when any license plate
on the watchlist is detected in the images being analyzed.
BT.
The Network Video Management Software (NVMS) shall provide the ability to
enable and configure PTZ control on the RS-485 interface of a video source.
BU.
The Network Video Management Software (NVMS) shall support the
following list of PTZ camera protocols:
•
•
•
•
•
•
•
•
•
•
•
•
•
BV.
American Dynamics Sensormatic
AXSYS
AXSYS DCU
Ernitec ERNA
Honeywell Diamond
Kalatel ASCII
Pelco D
Pelco P
TEB Ligne
Vicon extended
Vicon normal
Videotec Legacy
Videotec MACRO
The Network Video Management Software (NVMS) shall provide the ability to
change the network settings for a video and audio source.
BW.
The Network Video Management Software (NVMS) shall provide the ability to
change image quality and image rate parameters for a video source without
affecting the settings on the other video sources.
BX.
The Network Video Management Software (NVMS) shall provide the ability to
enable a secondary stream for live viewing.
BY.
The Network Video Management Software (NVMS) shall provide the ability to
change the exposure, iris, IR filter, backlight compensation, gain, priority,
sharpening, saturation, focus, and white balance settings for a video source.
BZ.
The Network Video Management Software (NVMS) shall provide the ability to
change the image dimensions for a video source.
CA.
The Network Video Management Software (NVMS) shall provide the ability to
rotate the image 90°, 180° or 270° for a video source.
CB.
The Network Video Management Software (NVMS) shall provide the ability to
add privacy zones to a video source to block unwanted areas in the image
field of view.
CC. The Network Video Management Software (NVMS) shall provide the ability to
set a maximum recording duration for manually triggered recording for a
video source.
CD.
The Network Video Management Software (NVMS) shall provide the ability to
change the input, output, gain and volume for an audio source.
Page 25 of 34
CE.
The Network Video Management Software (NVMS) shall provide for fullduplex two- way audio communication.
CF.
The Network Video Management Software (NVMS) shall provide the ability to
link any audio source to any video source.
CG. The Network Video Management Software (NVMS) shall provide the ability to
set a limit on the maximum bandwidth transmitted to the Control Center
Client application from the Control Center Server application.
CH.
The Network Video Management Software (NVMS) shall provide the ability to
automatically log in to an NVR.
CI.
The Network Video Management Software (NVMS) shall provide the ability to
override user access to an NVR if there are insufficient licenses.
CJ.
The Network Video Management Software (NVMS) shall provide the ability to
automatically log out of an NVR when the application is left idle.
CK.
The Network Video Management Software (NVMS) shall provide the ability to
save and restore the window layout.
CL.
The Network Video Management Software (NVMS) shall provide the ability to
control the system using a PC keyboard or joystick.
CM. The Network Video Management Software (NVMS) shall provide the ability to
import and export client settings such as maps, views, and web pages.
CN.
The Network Video Management Software (NVMS) shall support live or
recorded video monitoring of 1 to 36 video streams simultaneously on a
single monitor with the following standard layouts:
•
•
•
•
•
•
•
•
•
•
Full Screen
2x2
3x3
4x4
5x5
6x6
1+5
1+7
1+ 12
2+8
CO. The Network Video Management Software (NVMS) shall support live or
recorded video monitoring in a customizable video display beyond the
standard layouts.
CP.
The Network Video Management Software (NVMS) shall support the ability to
bias the displayed video to a higher frame rate or to a lower image resolution
if the client network bandwidth or client processing power is insufficient to
display the full frame rate and image resolution.
CQ. The Network Video Management Software (NVMS) shall support the ability to
display the following list of image overlays:
•
•
Camera Name
Camera Location
Page 26 of 34
•
•
•
•
•
CR.
Timestamp
Record Indicator
PTZ Controls
Motion Activity
License Plate
The Network Video Management Software (NVMS) shall support an
unlimited number of monitors for monitoring video and audio streams.
CS.
The Network Video Management Software (NVMS) shall support monitoring
live and recorded video and audio streams simultaneously on the same
monitor.
CT.
The Network Video Management Software (NVMS) shall support viewing the
same live or recorded video stream at different zoom levels.
CU.
The Network Video Management Software (NVMS) shall support the ability to
switch from live to recorded video on demand for an instant replay of
recently recorded video.
CV.
The Network Video Management Software (NVMS) shall support the creation
of unlimited views with unique layouts of video streams.
CW. The Network Video Management Software (NVMS) shall support the ability to
full-screen a view.
CX.
The Network Video Management Software (NVMS) shall support the ability to
save views.
CY.
The Network Video Management Software (NVMS) shall support the ability to
cycle through views (guard tour) based on a specified interval.
CZ.
The Network Video Management Software (NVMS) shall display all video
sources connected to the system.
DA.
The Network Video Management Software (NVMS) shall support the ability to
drag and drop a video source from a tree of video sources into a window for
live or recorded video and audio monitoring.
DB.
The Network Video Management Software (NVMS) shall support the ability to
drag and drop a view from a tree of views into a window for live or recorded
video and audio monitoring.
DC.
The Network Video Management Software (NVMS) shall support the ability to
configure how the tree of video sources and views is displayed.
DD.
The Network Video Management Software (NVMS) shall support the ability to
designate one or more regions in a window for displaying video directly linked
to triggered alarms and rules.
DE.
The Network Video Management Software (NVMS) shall support the ability to
acknowledge alarms from the designated video display area.
DF.
The Network Video Management Software (NVMS) shall support the ability to
manually trigger digital output.
DG.
The Network Video Management Software (NVMS) shall support the ability to
create a map that represents the physical location of cameras and other
devices throughout the surveillance system. Maps shall be created from
Page 27 of 34
images stored in JPEG, BMP, PNG, or GIF image formats. Maps shall have
the ability to contain links so as to create a hierarchy of interlinked maps.
DH.
The Network Video Management Software (NVMS) shall support the ability to
create a map that has a link to a section of the entire image region.
DI.
The Network Video Management Software (NVMS) shall support the ability to
drag and drop a video source from a map into a window for live or recorded
video and audio monitoring.
DJ.
The Network Video Management Software (NVMS) shall highlight a camera
on a map when an alarm linked to the camera is triggered.
DK.
The Network Video Management Software (NVMS) shall highlight a linked
map that contains a camera when an alarm linked to the camera is triggered.
DL.
The Network Video Management Software (NVMS) shall support the ability to
save a link to a web page and view the web page in a window.
DM. The Network Video Management Software (NVMS) shall support digital
zooming and panning on live and recorded video streams.
DN.
The Network Video Management Software (NVMS) shall support controlling
mechanical pan-tilt-zoom, iris, and focus as well as setting presets and
patterns.
DO.
The Network Video Management Software (NVMS) shall provide the ability to
name pan-tilt-zoom presets.
DP.
The Network Video Management Software (NVMS) shall support controlling
mechanical pan-tilt-zoom camera on-screen display and auxiliary controls.
DQ.
The Network Video Management Software (NVMS) shall support locking PTZ
controls.
DR.
The Network Video Management Software (NVMS) shall support control of a
mechanical pan-tilt-zoom camera with a USB joystick.
DS.
The Network Video Management Software (NVMS) shall support forward and
reverse playback of recorded video and audio at variable speeds.
DT.
The Network Video Management Software (NVMS) shall synchronously
playback recorded video and audio from selected video sources.
DU.
The Network Video Management Software (NVMS) shall support navigation
of recorded video and audio via calendar, timeline, or events.
DV.
The Network Video Management Software (NVMS) shall support a timeline
that displays all connected video sources and the corresponding motion and
recording events.
DW. The Network Video Management Software (NVMS) shall support a timeline
that can display the entire time range down to one second of recorded video
and audio.
DX.
The Network Video Management Software (NVMS) shall support creating
bookmarks for recorded video and audio from multiple sources, displaying
the bookmarks on the timeline, and searching for bookmarks.
Page 28 of 34
DY.
The Network Video Management Software (NVMS) shall support protecting a
bookmark so the video and audio data is never overwritten.
DZ.
The Network Video Management Software (NVMS) shall support monitoring
alarms.
EA.
The Network Video Management Software (NVMS) shall support the ability to
assign alarms to users.
EB.
The Network Video Management Software (NVMS) shall support the ability to
acknowledge alarms.
EC.
The Network Video Management Software (NVMS) shall support the ability to
bookmark alarms.
ED.
The Network Video Management Software (NVMS) shall support searching
through bookmarks based on various search criteria including bookmark
name, notes, and linked camera names.
EE.
The Network Video Management Software (NVMS) shall support searching
through recorded video and audio based on various search criteria including
time, date, video source, and events.
EF.
The Network Video Management Software (NVMS) shall support searching
through recorded video based on motion in user defined areas (pixel search).
EG.
The Network Video Management Software (NVMS) shall support searching
through recorded video based on time, date, video source, and image region
and have the results displayed as a series of thumbnail images.
EH.
The Network Video Management Software (NVMS) shall support searching
through recorded video based on alarm events.
EI.
The Network Video Management Software (NVMS) shall support searching
through recorded video based on point-of-sale transaction events.
EJ.
The Network Video Management Software (NVMS) shall support searching
through recorded video based on license plates detected in the images of the
video source.
EK.
The Network Video Management Software (NVMS) shall support the ability to
export recorded video in the following formats:
•
•
•
•
•
•
•
•
EL.
EM.
Native
JPEG
PNG
TIFF
AVI
WAV
PDF
Print
The Network Video Management Software (NVMS) shall support the ability to
export recorded audio in WAV format.
The Network Video Management Software (NVMS) shall support the ability to
take a snapshot of a live or recorded image and export it from the system.
Page 29 of 34
EN.
The Network Video Management Software (NVMS) shall support the ability to
export a live stream of images in the following formats:
•
•
•
EO.
JPEG
PNG
TIFF
The Network Video Management Software (NVMS) shall support the ability to
export video from multiple camera streams in Native format.
EP.
The Network Video Management Software (NVMS) shall support reviewing
video and audio that was exported in the Native format.
EQ.
The Network Video Management Software (NVMS) shall provide the camera
properties and time zone for video exported in Native format.
ER.
The Network Video Management Software (NVMS) shall support
authenticating video that was exported in the Native format to validate that it
was not tampered with.
ES.
The Network Video Management Software (NVMS) shall support converting
video that was exported in the Native format to an industry standard format.
ET.
The Network Video Management Software (NVMS) shall support reviewing
video and audio stored in a backup.
5.3 SURVEILLANCE CAMERA COVERAGE
A. This video surveillance upgrade project shall incorporate an expectation of
quantified playback quality on very specific scenes required for forensic and real
time use of the video management system for the Norwalk Transit District
headquarters. The final sign off by the Owner will include the specific distance
and horizontal field of view for each scene with a “pixels per foot” quantification
upon playback with the given scenes except where situational awareness is
specified as the objective for a particular camera. In this manner the Owner can
be assured that the technical specification will be met by the successful proposer
and that the installation’s resulting performance during playback will meet that
expectation. License plate capture for 24/7 use is required for each of the two
entrances for this project. Surge protection such shall be used on all camera
connections and server shall have a 15 minute UPS.
B. This is an open proposal process and other than meeting best practices for IP
systems and megapixel cameras it is not vender specific as far as a video
management system (VMS) is concerned although the basis for this design is
Avigilon.
C. The VMS manufacturer must offer on line training with recorded audio video
tutorials for end user training. This will be used as a secondary resource to the
dealer with VMS regional personnel for training on site at their convenience.
D. The VMS manufacturer must have a tool for calculating and proving pixels on
target with a given camera, lens and field of view that will support all submittals
for this technical specification.
Page 30 of 34
E. Record duration: Two weeks at 4 PPS with data aging capability. Outdoor
cameras at 75% motion and interior cameras at 25% motion based on 24/7/365.
F. Camera Scenes:
G. Camera 1:
Second Floor Lobby of Administration Building
 Use a 180 degree FOV camera to encompass stairway and two
hallways.
 Use wall pendant style mount for dome housing.
 At 20’ distance by 30’ wide and 10’ high see 118 pixels per foot on
a 180 degree basis.
 Clean up: Remove existing cameras and patch wall by others.
 Run new Category wires do not use old coax.
H. Camera 2:
Main Lobby
 Situated on first floor with existing conventional wedge housing, with
wide angle lens and body camera.
 2 Megapixel to view Dispatch and main entrances.
 See 20’ by 20’ HFOV and minimum 64 pixels per foot (p/f) upon
playback.
I.
Cameras 3, 4, 5:
Main Parking Lot
 Use 3 ea of 5 Megapixel (MP) cameras all body style in conventional
environmental IP 66 rated tube style housings with heater blower.
Wall mounted on front of building for optimized situational coverage
of lot considering trees that will be pruned. This placement will be
approved by the Facilities Director before mounting permanently.
 Each camera sees 200’ by 75’ HFOV and at 100’ sees 35 p/ft at that
distance.
Page 31 of 34


Camera 5 will look across the building looking northwest and see
from 170’ distance by 100’ wide and render 26 p/ft at the maximum
distance. At 80’ distance the playback daytime video will render 52
p/ft.
Primary goal here is for “slip and fall” documentation so optimized
situational coverage is of primary concern.
J. Camera 6:
Main Entrance Choke Point LP Shot.
 Mount a 3 MP body style camera in an IP 66 rated housing by either
the left or right side of the driveway entrance for the most effective
shot and optimal angle off center ( roadside) as possible for day
night license plate capture. The entrance is approximately 33’ wide
and will require infrared light to get the highest percentage of rear
license plates entering the complex even at when not daylight hours.
Bidders shall decide to wire, trench or use Ethernet Bridge such as
manufactured by Firetide. There is power that potentially could be
accessed at the gate controller.
 See 30’ wide from this distance with min 50 p/ft.
 Use IR lighting rated for 2X actual distance.
K. Camera 7:


Wilson Ave Perimeter Along Building Viewing Fence Line
Where Present Cameras Are Located.
1 MP camera with remote focus and remote optical zoomviewing
along building mounted near existing camera (to be removed) and
viewing in the same direction toward the main lot entrance but
viewing the fence general area along Wilson Ave.
Use same IP66 body style environmental housing as in main parking
lot.
L. Camera 8:
Wilson Ave Perimeter
 Looking along building looking east toward bus entrance.
 This camera shall be a 1 megapixel day night camera with remote
focus and remote zoom in a conventional tube style environmental
housing looking along fence line toward the opposite direction as
camera 7.
M. Camera 9:
Wilson Ave Perimeter
 View West along fence line and toward the main lot with 1 Megapixel
camera with remote focus and remote zoom with conventional style
IP66 housing.
N. Camera 10:
Service Gate
 View of Choke Point off Wilson Ave for License Plate (LP) Shot.
 See 32’ wide from 20 ‘ distance for rear plate shot with IR lighting
that is rated 2X actual distance with 3 Megapixel camera.
 Mount near Gate operator enclosure and trench to building for
connectivity. Access to power could be available at gate operator at
entrance.
Page 32 of 34
O. Camera 11:
Service Lot A. Surveillance Coverage
 See from 142’ distance by 88’ wide and 29 p/ft. at the maximum
distance using a 5 megapixel camera and conventional body style
housing.
 Mount on Wilson Ave side corner of Maintenance Garage looking
toward lot for first sector once bus enters the service lot.
P. Camera 12:
Service Lot B. Coverage
 See from 142’ distance by 88’ wide and 29 p/ft. at the maximum
distance using a 5 megapixel camera outfitted in an IP66 body style
housing.
 Mount on corner of garage door section to view the second sector of
the lot.
 View fuel pump scene within this scene.
 Use IR lighting for night surveillance
Q. Camera 13:
Bus Wash Entrance and Fueling Area
 Mounted under right corner of Maintenance Garage.
 Mount by wash entrance overhead by entrance to see 30’D by
30’Wide with 5 MP dome camera.
R. Camera 14:
Rear Driveway View
 1 MP dome camera looking down driveway to middle lot to see
vehicles- on road and corner of building with remote auto focus and
remote optical zoom.
S. Camera 15:
Middle Lot A
 Mounted on rear of bus wash building by door to see dumpster and
beyond where oil reservoir and generator is located 100’ wide from
111’ distance to include the Fare box depository. 5 MP body style
camera and IP66 environmental housing will show 26 p/ft on
playback at that distance.
T. Camera 16:
Middle Lot B
 Mounted on the upper corner toward the dumpster area looking back
at the left to right of the bus wash entrance door half way over to
toward the right. A 5 MP camera with body style IP66 environmental
housing from 110 ‘ away and 50’ wide will show 52 p/ft.
U. Camera 17:
Middle Lot C
 Mounted over maintenance entrance to the opposite second half of
the bus storage garage. A 5 MP camera will show 52 p/ft from 110
with a 5 MP camera.
V. Camera 19:
Front Visitor Walkway Shot
 Mounted on front corner wall outdoors looking toward front door
sidewalk with a 2 megapixel body style IP66 environmental housing.
Camera shall have remote auto focus and remote optical zoom.
Page 33 of 34
Camera sees 60’ distance by 30’ wide and 47 ppf at the maximum
distance.
W. Cameras 20, 21,22 : Money Room
 Use three each of 2 megapixel dome cameras overhead for counter
and optimal highest percentage of video room coverage.
 See money denomination upon playback for two operators counting
money. Approximately 11’ distance by 6’ wide and 215 pixels per
foot.
 Coordinate camera placement under the direction of the Site
Supervisor in Charge.
5.4 NETWORK INFRASTRUCTURE
A.
IP network switches shall have a backplane suitable for video usage.
Provide POE output in a wattage that exceeds the power budget of the
cameras connected to it by 20 %.
B.
A power budget spreadsheet should be attached to the proposal.
C.
A Bandwidth requirement spreadsheet should be attached to the proposal.
D.
Switches may be located in the field to minimize cable pulls.
E.
This is a dedicated video surveillance network with LAN viewing only, The
contractor will be responsible for locating switches in remote locations all
switches placed above ceiling tile must be approved by the owner and be
plenum rated.
F.
Approved switch Manufacturers include Aruba Networks, HP, GE - IFS and
Meridian. Any switch used must be manageable; IP addressed and support
802.1q VLAN tags.
G.
A mobile gateway shall be provided for iPhone and iPad use and be
configured through the existing Firewall for the new server.
H.
Viewing shall be done with an additional 42” monitor in Operations on a new
client PC with a suitable graphics card meeting the specifications set by the
VMS manufacturer. An additional new workstation and desk monitor with a
24” widescreen will be placed in the Administrator’s office. Connections from
the PC to the Monitor must be HDMI. New cabling to the workstations from
the data closets will be required and meet all cabling specifications.
5.5 INFRARED LIGHTING
A.
Proposers shall provide a separate quote for low voltage or POE Infrared
Illumination where additional night time viewing would warrant it.
Page 34 of 34