3108 Digital Video Recorder(DVR)

R5 Visual Intelligence Software

Architectural and Engineering Specifications

CSI Master Format

Document Revision 4.0

November 2006

March Networks Confidential

Information in this document is subject to change without notice.

MARCH NETWORKS and the MARCH NETWORKS logo are trademarks of March Networks Corporation

Table of Contents

PART 1GENERAL

1.01Introduction

A.Contractor’s Responsibility

B.Specification Language

C.Drawings and Specifications

D.Intent and Correlation

1.02References

1.03Definitions

A.Exceptions

B.Meanings

1.04Design Requirements – CONTRACTOR DESIGN

A.Project Drawings

B.Codes and Ordinances

C.Project Management

D.Miscellaneous

1.05System Description

A.DVR Unit Characteristics

B.DVR Unit Configuration

C.Configuration and Viewing Applications

D.Concept of Operation

E.System Security

F.System Management

G.Automated Configuration

H.Reliability

I.Alarm Cut Detection

J.Video Capture

K.Video Loss Detection

L.Field of View Monitoring

M.Video Output

N.Audio Capture

O.Storage

P.Recorded Information

Q.Recorded Format

R.Continuous Recording

S.On-Event Recording

T.Scheduled Recording

U.Time Synchronization

V.Live Video/Audio Viewing

W.Video Zoom/Full Screen Display

X.PTZ control

Y.Video Image Settings

Z.Data Ports

AA.Switch Control

BB.Alarm Notification

CC.Time Zones

DD.Search of Alarms

EE.Search and Retrieval of Recordings

FF.Playback Viewing

GG.Playback Controls

HH.Time Ruler

II.Video Images - Copy, Save and Print

JJ.Video Clips – Security Sealed

1.06Submittals

A.Product Data

B.Procedures

C.Shop Drawings

D.Manufacturers Installation and Programming Instructions

E.Project Record Drawings

F.System Documentation

G.Closeout Submittals

1.07Quality Assurance

A.Qualifications

B.Supervision and Construction Procedures

C.Regulatory Requirements

D.Permits

E.Certifications

1.08Delivery, storage, and handling

A.Delivery to Job Site

B.Storage and Protection

1.09Project/Site Conditions

A.Environmental Conditions

B.Existing Conditions

C.Accident Reports

1.10Sequencing

A.Description

B.Approach

1.11Scheduling

1.12Warranty

1.13System Start-Up

1.14Owner’s Instructions

A.Coordination with [Client]

B.Coordination with Manufacturer

1.15Commissioning

Part 2Products

2.01General Requirements

A.Contractor Responsibility

B.Product Availability

C.Wire and Cable

D.Conduit and Raceway Systems

E.Junctions and Pull Boxes

F.Lightning Protection

G.Surge Protection

2.02General System Specifications – DVR Hardware

2.03General System Specifications – Network Communications

2.04General System Specifications – R5 Visual Intelligence Software

A.R5 Administrator Console

B.R5 Investigator and Evidence Manager

C.R5 Evidence Reviewer

D.R5 Enterprise Service Manager (ESM)

E.R5 Financial Transaction Investigation

F.R5 Retail Transaction Investigation

G.Software Integration

PART 3EXECUTION

3.01Preparation

3.02INSTALLATION

A.General

B.Mounting

C.Workmanship

D.Equipment Pre-Test

E.Wire and Cable

F.Wire and Cable Terminations

G.Conduit and Raceway Installation

H.Penetrations

I.Grounding

J.Power to Security Equipment

K.Cutting and Patching

L.Painting

M.Plywood Backing

3.03Field Quality Control

A.Final Tests & Inspection

B.Documentation

C.Training

Section 13775

CCTV Digital Video Recorder and Transmission System

PART 1GENERAL

1.01Introduction

  1. Contractor’s Responsibility

Unless otherwise provided in the Drawings and Specifications, the Contractor shall provide and pay for all labor, materials, equipment, tools, utilities, construction equipment and machinery, transportation and other facilities and services necessary for the proper execution, operation and completion of the Work.

  1. Specification Language

Specifications and notes are written in imperative and abbreviated form. Imperative language of the technical specifications is directed at the Contractor, unless specifically noted otherwise. Incomplete sentences shall be completed by inserting “shall”, “shall be”, “the Contractor shall”, and similar mandatory phrases by inference. The words “shall be” shall be supplied by inference where a colon (:) is used within product specifications.

  1. Drawings and Specifications

Contractor shall be provided three (3) sets of the Drawings and Specifications for his use. Additional sets, if requested by Contractor, shall be furnished to the Contractor for the actual cost of reproduction.

Contractor shall carefully study the Drawings and Specifications, and shall at once report any error, unforeseen circumstances, inconsistency or omission he may discover.

The [Client] Project Manager shall be the interpreter of the requirements of the Drawings and Specifications, subject to the final approval of [Client]. All interpretations and opinions of the Security Consultant shall be made in writing or in the form of drawings.

  1. Intent and Correlation

The intent of the Project Drawings and Specifications is to include all items necessary for the proper execution and completion of the Work.

The Project Drawings and Specifications are complementary, and what is required by any one shall be as binding as if required by both.

1.02References

NFPA 70 - National Electrical Code - current version during Notice to Proceed.

1.03Definitions

  1. Exceptions

Words that are in common use are used throughout the Drawings and Specifications, except words that have well-known technical or trade meanings, which are used in accordance with such recognized meanings.

  1. Meanings

Whenever the following listed words and phrases are used, they shall be mutually understood to have the following respective meanings:

  1. The words “as indicated.” means: as shown on the Drawings, and in accordance with the Specifications.
  2. The words “as required.” means: as required to provide a complete and satisfactory Work in full conformance with the Drawings and Specifications.
  3. The word “New” means: new Work to be provided by Contractor.
  4. The word “Provide” means: furnish, install, connect, test and make ready for use.
  5. The words “Relocate Existing” means: remove existing item from present location. Reinstall, re-connect, and test existing item and make ready for use at new location as shown on the Drawings.
  6. The words “Remove Existing” means: remove existing item and return item to [Client].
  7. The word “Replace” means: remove existing item and return item to [Client]. Provide new item as indicated.
  8. The word “Work”: The Work is the completed construction required by the Drawings and Specifications, and includes all labor necessary to produce such construction, and all materials and equipment incorporated or to be incorporated in such construction.
  9. The word “Furnish” means: supply item as specified. Item to be installed by others.

1.04Design Requirements – CONTRACTOR DESIGN

  1. Project Drawings

The Project Drawings represent the level of system design to be provided by [Client]. Contractor shall provide all additional system design work required, including:

  1. Conduit layout and sizing.
  1. Wire and cable layout and sizing.
  2. Point-to-point wiring and equipment hook-up information.
  3. Equipment mounting details.
  4. Design of equipment cabinets.
  5. Other detailed design work required.
  1. Codes and Ordinances

Contractor’s design shall conform to all applicable codes and ordinances. All electrical design, including the sizing and placement of conduit, raceways and conductors, shall be in accordance with NFPA 70: National Electrical Code unless local codes establish more stringent requirements.

  1. Project Management

Contractor’s design work is subject to review and approval by [Client]’s Project Manager.

  1. Miscellaneous
  1. Contractor shall provide all wire, cable, conduit, connectors and junction boxes required for system operation.
  1. Contractor shall provide complete testing of all wiring and cables prior to connecting to any equipment or power.
  2. Contractor shall provide complete “as-built” documentation of all security systems, including documentation of existing equipment, wiring, conduits, and raceways.
  3. Contractor shall perform other Work as defined within the Project Drawings and Specifications.

1.05System Description

  1. DVR Unit Characteristics

Combined with R5 Visual Intelligence Software, the DVR unit shall have the following characteristics:

  1. The system shall be a networked device purpose built exclusively for the capture and processing of digital video and supporting audio, alarm, storage and other services. The system shall not be based on generic industry PC components and architectures.
  1. The DVR shall be a desk or wall-mount system contained in a standard 20” (h) x 14.5” (w) x 4.5” (d) structured wiring enclosure with a removable screw-closure front panel containing LEDs for unit, operation and hard-drive status indication. All cables are to be terminated and restrained within the unit on an I/O panel. The single internal hard-drive shall be accessible easily for service or upgrade..
  2. The DVR shall employ an embedded Linux operating system, housed in flash memory and capable of being upgraded remotely if needed, such that no system software shall be stored on hard-drive media, and the operating environment shall be more robust and immune to virus and illicit attack than other common operating systems. At the client desktop, however, all software applications shall support Windows®2000/Windows XP operating environments.
  3. The DVR shall employ a software interface common with other March Networks DVR/NVR models. This will yield consistent user training materials, documentation and system interaction.
  4. The DVR shall provide a ‘hybrid’ architecture, capable of supporting traditional analog cameras in the quantities shown below as well as a number of IP cameras (see below) to increase the aggregate camera support, provide high-resolution video capture in critical customer areas, and allow migration to this new camera technology according to customer need
  1. DVR Unit Configuration

The DVR unit shall be available in the following configuration:

  1. 8 BNC video inputs capable of accepting an NTSC or PAL composite signal, and 1 NTSC or PAL composite output for video monitoring
  2. 60 frame-per-second aggregate video capture, configurable per camera based on viewing requirements
  3. 2 bi-directional, half-duplex audio inputs/outputs
  4. 4 alarm inputs and 1 switch output
  5. 1 RS-232, 1 RS-485 and 1 USB data port for integrating banking ATM transaction or retail POS transaction capture information, PTZ camera controllers, and USB modems or CD burners respectively
  6. 1 RJ-45 10/100BaseT Ethernet network connection for LAN-based system access and management
  7. 8 individually fused terminal-block connections supplying 12 VDC and 24 VAC camera power
  8. Support for up to two IP cameras via the 10/100BaseT Ethernet port
  9. 1 internal, high-capacity, EIDE hard disk drives, at a minimum of 400 GB each, and mounted for easy servicing
  1. Configuration and Viewing Applications

The R5 configuration and viewing applications shall be Windows® 2000/Windows XP PC compatible. Each application shall be installed from a CD using an automatic installation program. All applications shall have similar interfaces in order to reduce learning time, and shall operate consistently across all members of the DVR product family.

  1. Concept of Operation
  1. Combined with R5 software, the DVR unit shall capture, digitize and compress video (using industry-standard MPEG-4 video compression technology and unique Adaptive Compression Technology to further optimize transmitted and stored video) and, if desired, accompanying audio signals on all enabled inputs. Once compressed, the unit shall either distribute the compressed data to any number of authorized users requesting the data over the unit’s internal, wide area and/or wireless network connection, and using the Windows-based client software.
  1. In parallel, the unit shall also store all compressed data to the available internal hard disk drive. The unit shall be configurable with either no drive in a ‘video server’ configuration or with a single high-capacity drive for extensive in-system storage.
  2. Internal system storage shall take advantage of Intelligent Video archiving and Retention technology that includes an up-front Critical Recording Buffer (CRB) that is user-configurable and captures by default video from all connected cameras at the highest per-camera frame rates available on the unit (based on model selected), providing always-on high quality recording on all cameras in keeping with the FBI/Scientific Working Group on Image Technology [SWGIT] recommendations, and eliminating the need for a feature to buffer video for increased recording rates on alarms.
  3. After the selected CRB period, Longer-Term Storage functionality shall kick in whereby all video of potential interest (e.g., motion video, alarm video, retail or financial transaction video) shall be tagged for retention, ‘thinned’ out and stored for a user-defined period of time. All disk space freed up by this ‘thinning’ process shall be available for new video storage. Beyond long-term storage, a further Extended Storage window shall be available to further thin and retain critical video for an extra period of time.
  4. Together with the MPEG-4 and Adaptive Compression features mentioned, this efficient retention/storage technology shall create a net increase of almost 30% more storage performance relative to other recording systems.
  5. At any time, selected video/audio data shall be available for export by users across the network to their PCs as well as through a USB-connected media storage device (e.g., CD Burner or USB memory stick) at the DVR. This video shall be completely appropriate for use in evidentiary purposes, and shall include a security (authentication) seal for continuity purposes and an auto-run Evidence Reviewer’ utility for playback and assessment by third parties such as law enforcement officials.
  6. The unit shall simultaneously handle recording, retrieving, and live distribution of video and audio. The unit shall operate in a continuous record mode, even if only event driven recordings, scheduled recordings or motion detection recordings are to be retained for longer periods of time. The unit must be capable of independent operation with network access and control, centralized management in conjunction with a number of other DVR units, or operation under the control of a centralized, enterprise-level suite of multiple-system management software.
  1. System Security
  1. The unit shall be able to mount on a desktop or wall, and have a locking hinged front panel such that the unit cannot be easily powered down or have the disk drive accessed inappropriately
  1. Each DVR shall be deployed almost exclusively ‘behind’ an existing network security firewall, benefiting from that equipments default virus protection software and its encryption options to prevent hacker attacks.
  2. Each DVR shall use an embedded (in flash memory) Linux operating system, which is inherently more robust in architecture and less susceptible to virus and other “hacker” attacks than other operating systems. Each DVR shall minimize the number of access points for hackers to try and gain access to the unit or by which a virus may attack the unit. Communications with the DVR shall be very restricted, with most external ports being blocked and no way made available to open them.
  3. The DVR unit shall not share any known or unknown vulnerabilities associated with popular PC or computer operating systems. It shall achieve a C2 level of security. All TCP and UDP ports not required for use will be blocked thus ensuring that points of network attack will be minimized.
  4. The DVR unit shall operate without the requirement for a keyboard, monitor or mouse - also known as ‘headless’ operation – instead being controlled across the network from authorized client PCs. As a result, no tampering shall be possible at the unit itself.
  5. All analog video shall be captured and transmitted to the DVR over coaxial cables, directly connected to the rear of the units. No interception of these video streams shall be possible without physically tapping into the specific cable inside the customer premises.
  6. All IP-camera-based video shall be captured and transmitted to the DVR using the IP protocol. The DVR shall connect with the IP cameras through a routed network.
  7. The DVR unit shall allow for the use of password authentication to prevent unauthorized access to the DVR. Two levels of authentication shall be supported (user and administrator) when the DVR is managed in a peer-to-peer fashion. When the DVR is being managed by server-based management software, the system shall support a large number of users and user groups, as well as a rich set of privileges. In this enterprise configuration, external user authentication using an existing enterprise application shall also be supported, providing the net effect for users of ‘single sign-on’ or single authentication through their traditional system access utility.
  8. The DVR shall ensure video data packets are encrypted for network transmission using SSL security technology.
  9. The system shall provide the ability to limit operator access to DVR resources. Administrators shall be able to manage user rights to a fine granularity of control, down to the level of access to the individual resource (for example, a single camera, audio channel, or data port).
  10. The local or centralized system administrator shall be able to access all DVR units that are visible on the network, subject to each user’s privilege level. Each individual DVR unit shall keep a log of any user access to the unit. The log shall be retrievable remotely by an administrator, but no user will be able to remove entries from the log. The log shall be maintained automatically by removing entries that are six months old. It shall be an option to copy and save the report to a text-formatted file for import into a third party application. It shall be an option to print the report. These capabilities shall be scalable such that they will work seamlessly under the control of a centralized, enterprise-level suite of multiple-system management software.
  1. System Management

All DVR units shall be capable of being managed locally or centrally over a TCP/IP LAN or WAN network, using individual system or enterprise-level management utilities. All systems shall be capable of being managed by a set of consistent user interface applications which operate consistently across all members of the DVR product family. The enterprise-level management application shall be capable of managing system programming, health and users, of upgrading the software on a DVR unit, synchronizing the time on a DVR unit, remotely managing a DVR unit, and more.

Reports on systems use, problems, and alarms shall be capable of being printed. Reports shall also be capable of being copied or saved for importing into third party applications.

  1. Automated Configuration

As DVR units are added to the network, the DVR management application shall automatically detect their presence on the network to support rapid configuration and administration.

  1. Reliability
  1. The DVR shall use an embedded (in flash memory) Linux operating system, which is inherently more robust in architecture and reliability than other operating systems.
  1. No DVR operating software shall reside on the DVR hard drive, eliminating hard-drive failure as a reliability issue and allowing the unit to operate without any hard-drives present (e.g., in a video streaming application).
  2. The DVR unit shall contain hardware and software watchdog circuitry that maximize fault-free operation. The central management application shall report all problems detected by any DVR units on the network. The DVR configuration software shall continuously supervise the health of both the unit and the network, including dial-up extensions. The management utility shall periodically connect to all dial-up connected DVR units in order to ascertain the health of both the unit and the line/modem on which the unit is connected. An option to ‘connect on demand’ shall also be provided to support low-activity DVR deployments.
  3. The DVR shall use SMART disk technology to provide real-time monitoring of the hard-disc, including diagnostics and health reporting, to provide further system reliability.
  4. The administrator shall control the level of problem reporting (thresholds) in order to ensure the reliability of the DVR and the equipment connected to the DVR unit, but also to manage the amount of communications consumed by this activity. The administrator shall be able to have notification of problems e-mailed to specific users.
  5. The DVR unit shall be capable of fan-less operation, reducing the need for maintenance.
  1. Alarm Cut Detection

The DVR unit shall constantly monitor all enabled alarm inputs for cuts or breaks in the wire and provide notification on detection.