Architecture & Engineering Specification Proprietary Milestone Information

BZ.– Definitions

1. 
   DVMS system
   

1. 
   Modules
   

1. 
   Hardware variations
   

1. 
   The hardware manufacturer shall offer a rack-mounted hardware variation with the following specifications as seen in the table below:
   

Dimensions	43 (W) x 40 (D) x 8.8 (H) cm 17 (W) x 16.4 (D) x 3.5 (H) inches
Memory	16 GB
CPU	Intel i7
Storage	8 TB, 16 TB, 32 TB, 48 TB
Maximum power consumption	90-120 watts (configuration dependent), 24 V DC input
Power input	200W / 100~240V
O/S and video management software	Windows 10, hardware manufacturer
Solid state drive	64 GB for VMS and O/S environment
Operation temperature	0~40°C
Storage temperature	-20~70° C
Certificate	CE, FCC, UL
Accessory	1x DVI to VGA connector

1. 
   The rack-mounted hardware variation shall have 8 camera channel licenses which shall be preloaded by the hardware manufacturer
   
2. 
   The rack-mounted variation shall support up 128 IP cameras (video stream dependent).
   
3. 
   The rack-mounted hardware variation shall have a maximum recording rate of up to 544 Mbit/s (JBOD).
   
4. 
   The rack-mounted hardware variation shall support an unlimited number of supported servers
   
5. 
   The rack-mounted hardware variation shall support an unlimited maximum number of users
   
6. 
   The rack-mounted hardware variation shall support multiple video export formats
   
7. 
   The rack-mounted hardware variation shall support video push for the mobile viewing client application
   
8. 
   The rack-mounted hardware variation shall support an optional RAID storage
   
9. 
   The rack-mounted hardware variation shall support include a 3-year hardware warranty
   
10. 
    The rack-mounted hardware variation shall support the mobile viewing client
    
11. 
    The rack-mounted hardware variation shall support the web viewing client
    
12. 
    The rack-mounted hardware variation shall support the full viewing client
    
13. 
    The rack-mounted hardware variation shall support the smart search function
    
14. 
    The rack-mounted hardware variation shall support the alarm management function
    
15. 
    The rack-mounted hardware variation shall support third-party applications, such as video analytics or data storage
    
16. 
    The rack-mounted hardware variation shall support archiving to network storage
    
17. 
    The rack-mounted hardware variation shall support the map function
    
18. 
    The rack-mounted hardware variation shall support one-way audio
    
19. 
    The rack-mounted hardware variation shall support two-way audio
    
20. 
    The rack-mounted hardware variation shall support ONVIF cameras
    
21. 
    The rack-mounted hardware variation shall support H.264, MPEG-4 and M-JPEG codecs
    
22. 
    The rack-mounted hardware variation shall support pan-tilt-zoom (PTZ) support
    
23. 
    The rack-mounted hardware variation shall support Microsoft Active Directory
    
24. 
    The rack-mounted hardware variation shall support an interconnected systems functionality that shall allow the NVR to connect to other DVMS’es of the same manufacturer
    
25. 
    The rack-mounted hardware variation shall support an online monitoring function
    

26. 
    The rack mounted hybrid shall include 8 IP channel licenses and licenses for 32 analog cameras via an encoder.
    
27. 
    The rack-mounted hybrid shall support the same software features as the rack-mounted hardware variation.
    
28. 
    The rack-mounted hybrid shall support add-on IP camera licensing
    

Dimensions	30 (W) x 30 (D) x 9 (H) cm 11.8 (W) x 11.8 (D) x3.8 (H) inches
Memory	8 GB
CPU	Intel i5
Storage	2 TB, 4 TB, 8 TB, 12 TB
Maximum power consumption	68-74 watts (configuration dependent), 24V DC input
Power input	200W / 100~240V
O/S and video management software	Windows 10, hardware manufacturer software
Solid state drive	64 GB for VMS and O/S
Operation temperature	0~40°C
Storage temperature	-20~70°C
Certificate	CE, FCC, UL
Accessory	1x DVI to VGA connector
System I/O	Rear I/O

1. 
   The medium workstation shall include 8 camera channel licenses which shall be preloaded by the hardware manufacturer
   
2. 
   The medium workstation shall support up to 32 IP cameras (video stream dependent).
   
3. 
   The medium workstation shall have a maximum recording rate of 136 Mbit/s.
   
4. 
   The medium workstation shall support an unlimited number of supported servers
   
5. 
   The medium workstation shall support an unlimited maximum number of users
   
6. 
   The medium workstation shall support multiple video export formats
   
7. 
   The medium workstation shall support dual network interface cards (NICs)
   
8. 
   The medium workstation shall support video push for the mobile viewing client application
   
9. 
   The medium workstation shall support include a three-year hardware warranty
   
10. 
    The medium workstation shall support the mobile viewing client
    
11. 
    The medium workstation shall support the web viewing client
    
12. 
    The medium workstation shall support the full viewing client
    
13. 
    The medium workstation shall support the smart search function
    
14. 
    The medium workstation shall support the alarm management function
    
15. 
    The medium workstation shall support third-party applications, such as video analytics or data storage
    
16. 
    The medium workstation shall support archiving to network storage
    
17. 
    The medium workstation shall support the map function
    
18. 
    The medium workstation shall support one-way audio
    
19. 
    The medium workstation shall support two-way audio
    
20. 
    The medium workstation shall support ONVIF cameras
    
21. 
    The medium workstation shall support H.264, MPEG-4 and M-JPEG codecs
    
22. 
    The medium workstation shall support pan-tilt-zoom (PTZ) support
    
23. 
    The medium workstation shall support support Microsoft Active Directory
    
24. 
    The medium workstation shall support an interconnected systems functionality that shall allow the NVR to connect to other VMS’s of the same manufacturer
    
25. 
    The medium workstation shall support an online monitoring function
    

29. 
    The medium workstation hybrid shall include 8 IP channel licenses and licenses for 16 analog cameras via an encoder.
    

26. 
    The medium workstation hybrid shall support the same software features as the medium workstation.
    
27. 
    The medium workstation hybrid shall support add-on IP camera licensing.
    

Form Factor	Rack Mounted	Hybrid Rack Mounted	Medium	Hybrid Medium
Number of cameras	8 IP included	32 Analogue / 8 IP included	8 IP included	16 Analogue / 8 IP included
Number of supported servers	Unlimited	Unlimited	Unlimited	Unlimited
Maximum number of users	Unlimited	Unlimited	Unlimited	Unlimited
Dual network interface cards	Yes	Yes	Yes	Yes
Multiple video export formats	Yes	Yes	Yes	Yes
Video Push Support	Yes	Yes	Yes	Yes
Optional RAID storage	Yes	No	No	No
Software Upgrade Plan (SUP) 3-year	Included	Included	Included	Included
Hardware Warranty 3-year	Included	Included	Included	Included
Supports Mobile Client	Yes	Yes	Yes	Yes
Supports Web Client	Yes	Yes	Yes	Yes
Supports Smart Client	Yes	Yes	Yes	Yes
Smart Search	Yes	Yes	Yes	Yes
Alarm Manager	Yes	Yes	Yes	Yes
3rd-party application support (Ex. video analytics, data storage)	Yes	Yes	Yes	Yes
Archiving to network storage	Yes	Yes	Yes	Yes
Map function	Yes	Yes	Yes	Yes
One-way audio support	Yes	Yes	Yes	Yes
Two-way audio support	Yes	Yes	Yes	Yes
Supports ONVIF cameras	Yes	Yes	Yes	Yes
Codecs supported	H.264, MPEG-4, MJPEG	H.264, MPEG-4, MJPEG	H.264, MPEG-4, MJPEG	H.264, MPEG-4, MJPEG
Pan-tilt-zoom (PTZ) support	Yes	Yes	Yes	Yes
Microsoft Active Directory support	Yes	Yes	Yes	Yes
Interconnect™ support	Yes	Yes	Yes	Yes
Customer Dashboard support	Yes	Yes	Yes	Yes
Integrated encoder	No	Yes	No	Yes

2. 
   Recording Server Application
   

1. 
   The software solution shall support an unlimited number of recording servers. One or more recording servers shall be used in a software solution, depending on the number of cameras or the configuration of the physical system.
   

CF.Each recording server shall have a default storage folder where the database content, primarily recordings from the connected cameras, shall be stored. Recordings from each connected cameras shall be stored in individual camera databases.

CG.Recordings from each connected cameras shall be stored in individual camera databases.

CH.The software solution shall not limit the amount of storage allocated for each connected device.

Event server

1. 
   An event server shall manage all event- and map-related communication. It shall store events, image files and map configurations, and shall make status information about the surveillance system available.
   

1. 
   The mobile server shall handle communication between the software solution, and the mobile viewing client and web viewing client.
   

1. 
   Management application
   

1. 
   The management application shall provide a feature-rich and intuitive interface for initial configuration and day-to-day administration of the software solution.
   

Full viewing client

1. 
   The full viewing client shall enable operators to connect to the software solution for initial authorization. Upon authorization, the full viewing client shall be able to connect to the recording server(s), for access to video recordings.
   

Cross-platform web viewing client

1. 
   The software solution shall support a free web viewing client accessible through Internet browsers that shall allow users to access cameras, views and recordings without installing any software.
   

CM.The web viewing client shall be able to run on the supported browsers without installing any components on the client PC.

CN.The web viewing client shall connect to the software solution through a server component that shall be installed on the software solution.

CO.The software solution shall allow users of the web viewing client to make video exports without transferring the data to the client PC. It shall then be possible to download exports on-demand from the web viewing client, or access them directly from the software solution system storage.

1. 
   The software solution shall support a free iOS, Android and Windows 8 Phone-compatible mobile viewing client that shall allow users to access cameras, views and recordings on the mobile devices (mobile phones, tablets and portable music players).
   

CQ.The mobile viewing client shall be able to stream live video from mobile device cameras to the software solution from where it can be seen live in other clients and recorded for later viewing.

12. 
    Standalone viewing client
    

1. 
   The software solution shall include a standalone viewing client that shall be able to play back video files exported from clients.
   

2. 
   It shall be possible to switch between a basic version of the standalone viewing client with a minimum set of features and an advanced version with a higher number of features.
   
3. 
   It shall be possible to place a standalone viewing client on drives used to store recordings and archiving databases. This shall make it possible to read the databases in cases where a drive is removed from a server and used at a later stage without being connected to a recording server. The recording server shall create a file on each drive that describes the cameras whose recordings are on the given drive.
   

1. 
   Unlimited number of recording servers per system
   

1. 
   The software solution shall support an unlimited number of recording servers. One or more recording servers shall be used in a system, depending on the number of cameras or the configuration of the physical system.
   

1. 
   The software solution shall allow for the connection of a defined number of cameras or other devices for each recording server.
   

1. 
   The software solution shall not place limits on video retention time, making it possible to save recorded video for as long as needed.
   

1. 
   The software solution shall support simultaneous live, recording, playback and export capability.
   

1. 
   The software solution shall be able to automatically detect and install cameras that support Simple Service Discovery Protocol (SSDP), mDNS or ONVIF discovery when cameras supporting one of these protocols are added to a local network.
   
2. 
   Discovered cameras shall be automatically added to a default window in the full viewing client.
   

1. 
   The software solution’s management application shall include a wizard that allows users to search for cameras and automatically add them to the DVMS. Once installed, such cameras shall appear in a default view in the full viewing client.
   

1. 
   The software solution shall inform users of the management application when service releases or new version of device drivers drivers are available and allow them to download and install updates from inside the management application.
   

1. 
   The software solution shall support two-way audio from a microphone at the operator’s PC to a loudspeaker mounted elsewhere, and from a microphone mounted elsewhere to a loudspeaker at the operator’s PC.
   

1. 
   The software solution shall make it possible to enable or disable audio recording on a per device basis.
   

1. 
   The software solution shall support H.264, MPEG-4 (both ASP and SP), and MJPEG compression formats for the video stream from all devices including analog cameras connected to encoders, DVRs, and IP cameras connected to the system.
   
2. 
   The software solution shall support the MxPEG video compression algorithm, unique to Mobotix. MxPEG encoding shall have the capability to maintain high image quality for megapixel cameras while dramatically decreasing bandwidth consumption.
   

1. 
   The software solution shall support interoperability with the IP camera standards Physical Security Interoperability Alliance (PSIA) and the Open Network Video Interface Forum (ONVIF).
   

1. 
   The software solution shall include a universal driver that shall support any generic network camera. The driver must be able to handle standard video streaming formats including MJPEG, MPEG4 and H.264.
   

1. 
   A continuously updated list of supported brands and models shall be made available by the manufacturer.
   

1. 
   The video management system shall support the use of secure Hypertext Transfer Protocol Secure (HTTPS) using Secure Sockets Layer (SSL) to establish a secure connection between supported hardware devices and the software solution.
   

1. 
   The software solution shall allow users to display and record independent streams of video from the camera to the server, with different resolution, encoding and frame rate, for example to save disk space and network bandwidth on one of the streams.
   

1. 
   The VMD shall be able to detect motion on key frames or on a specific part of the video in regular quality or low-resolution video.
   

CU.The software solution shall be able to automatically adjust motion detection sensitivity to optimize the motion detection algorithm according to the background noise level in a video stream in changing light conditions.

1. 
   The software solution shall provide the possibility to set video motion detection on per camera basis.
   

1. 
   It shall be possible for video formats with key frames to record only key frames, and then speed up by recording all frames when motion is detected, an event is triggered, or on a relevant time schedule.
   

1. 
   The DVMS shall support setting up or adding events rules in the DVMS which shall be used for triggering actions. The DVMS shall support the following events:
   

1. 
   Hardware-related events (configurable or predefined)
   
2. 
   Device-related events (configurable or predefined)
   
3. 
   External events (Predefined, generic or user-defined)
   

CW.Analytic events (video content analysis events from third-party developers)

CX.The DVMS shall support attaching external units, typically external sensors, to input ports on devices.

CY.The DVMS shall support attaching external units to output ports on devices. This shall allow operators to, for example, turn on/turn off lights.

1. 
   The software solution shall make it possible to:
   

4. 
   Change the direction and/or zoom of cameras with pan-tilt-zoom capabilities.
   

DA.Define a go-to preset on event feature.

DB.Define patrolling profiles.

DC.Combine patrolling and go-to preset on event.

DD.Set and change a scanning/transition speed.

DE.Define PTZ priorities

DF.Go to preset positions

DG.Pause patrolling at manual operation

DH.Support for 360° fisheye and Immervision Enables® panomorph lenses, with two-by-two layout support

DI.Built-in de-warping lens support for 180° and 360° views

DJ.Joystick support

DK.Auxiliary commands (wash and wipe)

1. 
   The software solution shall support Active Directory to add users and groups.
   

4. 
   The software solution shall support defining users directly in the DVMS.
   

1. 
   The DVMS shall support an alarm management feature which shall be a single-point alarm function that shall be integrated with the map function and provide a clear and consolidated list and overview of security and system-related alarms and give instant access to cameras.
   

1. 
   Trigger alarms on events.
   

DN.Set a customizable alarms, priority levels, sound notifications, customizable alarm categories, alarm statuses, and customizable codes for how the alarm was resolved.

DO.View triggered alarms.

DP.Manage alarms (reassign, change status, comment, set category, status and result code).

DQ.Show up to 15 related cameras in an alarm preview window.

DR.View alarm handling reports

DS.View alarm logs

DT.In the full viewing client, the alarm management feature shall make it possible to:

1. 
   See an alarm list in live and playback views
   

DV.See instant preview of primary camera and related cameras

DW.Manage alarms (reassign, change status, comment)

DX.Integrate with map function

DY.See an alarm description and work instructions

DZ.Perform escalation and forwarding handling

EA.Print alarm report

EB.See alarm location maps in alarm list

EC.Have combined access to live and playback video

ED.See a report of alarm handling

EE.Use a dedicated alarm management tab that can be displayed as floating window.

Privacy masking

1. 
   The management application shall allow an administrator to define privacy masks, where areas of a camera image can be blocked from a view in clients as well as in exported video material.
   

Camera navigation feature

1. 
   A camera navigation feature shall make it possible to drag multi-level maps with cameras onto live view. This shall automatically display the positions of defined cameras in relation to each other based upon map data, for example as cameras are laid out in a floor plan either in relation to each other or relative to the current view.
   

1. 
   A video-sharing feature shall support distributed viewing of any camera on the system on any monitor connected to the software solution.
   

Map function

1. 
   The full viewing client shall include a built-in map function which shall provide an intuitive overview of the system and shall offer integrated access to all system components.
   

EI.It shall be possible to use any number of layered maps and to easily drag-and-drop and point-and-click icons representing cameras, servers, microphones, speakers, I/O devices, connection areas, and PTZ presets to maps.

Email and SMS notifications

1. 
   The software solution shall include an email and SMS notifications feature that can inform users about system errors such as archiving failures or camera failures.
   
2. 
   The software solution shall make it possible to include variables with metadata, such as camera name, name/timestamp of triggering event or an error text.
   
3. 
   The software solution shall make it possible to add a time schedule for notifications to make it possible to set a fixed period within which the DVMS may send notifications to users.
   

13. 
    Integration platform (software development kit) for third-party application integration
    

1. 
   The software solution shall support a software development kit (SDK) that shall allow for integrating the DVMS with third-party applications, for example access control, video analytics, and so on.
   

EK.Integration through protocol shall allow for the possibility to choose coding platform.

EL.Integration through the .NET-framework shall allow for using software components to integrate with the DVMS.

EM.Integration through a plug-in embedded directly into the DVMS environment shall run as part of the software solution and client applications.

1. 
   The software solution shall support the use of 360° panomorph video technology and it shall be possible to define the physical location of such a hardware device, for example on a wall, the ground or in the ceiling.
   

1. 
   Archiving of recordings
   

1. 
   The software solution shall support archiving (an automatic transfer) of recordings from a camera’s default database to another location on a time-schedule, without the need for user action, or initiation of the archiving process.
   
2. 
   Archiving shall support that the duration of the camera’s recordings can exceed the camera’s default database capacity.
   
3. 
   Archives shall be located either on the recording server computer or on a connected network drive. If the storage area on a network drive becomes unavailable for recording, the system shall be able to trigger actions such as automatic e-mails to defined personnel.
   

1. 
   It shall be possible to access all recordings for playback, whether the recordings are archived or not.
   

1. 
   It shall be possible for archiving and recording processes to take place at the same time, which shall enable recording to continue when the software solution is archiving databases.
   

1. 
   It shall be possible to archive at a particular point in time, up to 24 times a day, with a minimum of one hour between each, in order to prevent that a camera database becomes full.
   
2. 
   Recordings shall be archived automatically if a camera’s database is full.
   

1. 
   Dynamic archiving shall make it possible to archive to different drives. It shall be possible to specify a number of different archiving paths.
   
2. 
   Dynamic archiving shall make it possible to archive to the drive with most available space at any time, provided a camera database is using that drive.
   

1. 
   It shall be possible to use network drives such as Network Attached Storage (NAS) as an archiving location.
   

1. 
   The management application shall offer an overview of the available storage in the software solution.
   

1. 
   The DVMS shall make it possible to select between two video archiving system modes that define how to handle recorded video when system storage reaches full capacity.
   

The DVMS shall include a system mode that stops saving new recordings on the system storage once full capacity is reached. This shall allow law enforcement to preserve already existing video for evidence collection purposes.

EP.Export

1. 
   The software solution shall have an export function to make it possible to export still images and video files from the DVMS to external sources.
   

14. 
    The software solution shall support the following:
    

5. 
   Export in still image format (JPEG)
   

ER.Export in MKV media format (MKV)

ES.Encrypted export with password

ET.Auto-export of standalone viewing client

EU.Prevention of re-export of an exported file

EV.Additional export-specific privacy masks

EW.Direct export to optical media

EX.Flexible camera selection for export

EY.Bulk export to multiple media formats

EZ.General and camera specific export comments

FA.Pre/post comment slides for AVI files

FB.Integration

1. 
   Video content analysis support
   

1. 
   The software solution shall support video content analysis through third-party integrations that use the SDK.
   

5. 
   Recording server application programming interface (API)
   

1. 
   The SDK shall offer a full API for access to the recording server.
   

6. 
   Client plug-in support
   

1. 
   The full viewing client shall be able to extend standard functionality through third-party plugins that enable support for video content analysis, access control or other functionality.
   

7. 
   Open integration platform and/or software development kit
   

1. 
   The SDK shall be available to allow third-party development of functionality that shall be able to integrate to the software solution through an open integration platform.
   

8. 
   Generic events via TCP/IP
   

1. 
   The software solution shall be able to trigger events when receiving specific data sent via TCP/IP.
   

1. 
   Configuration wizards
   

1. 
   The configuration wizards shall guide administrators through the process of adding cameras, configuring videos, setting up recordings, adjusting motion detection and configuring user settings.
   

1. 
   The software solution shall be able to scan a network for hardware device and list these in real-time as they are detected.
   
2. 
   The software solution shall be able to recognize relevant hardware devices, such as cameras and video encoders, and include them in the device scanning process.
   

1. 
   A device replacement wizard shall make it possible to replace an already added and configured hardware device with a new hardware device.
   

1. 
   The software solution shall run the recording server, image server, mobile server and event server as Windows Services.
   
2. 
   The software solution shall have the possibility to monitor, start, stop and restart servers running as Windows Services.
   

1. 
   The software solution shall have the possibility to schedule when a device shall be on/off.
   

1. 
   The software solution shall be able to export and import configuration data.
   

1. 
   The software solution shall include system configuration restore points that shall make it possible to return to a previous configuration state.
   

Online and offline activation

1. 
   The software solution shall support activation of license files either via online or offline activation.
   

FF.Logging

1. 
   The software solution shall provide system logs, event logs and audit logs.
   

1. 
   The basic functionality of the full viewing client, the mobile viewing client and the web viewing client is listed in chapter 1.
   

1. 
   Access control module solution
   

9. 
   The software solution shall be able to integrate the DVMS with third-party access control solutions and to operate such third-party access control solutions in the full viewing client through an access control module solution.
   

15. 
    The access control module solution shall provide a access monitor view item option that shows a combined camera view and an event list displaying events from a defined access point. It shall be possible to use access monitor view items in independent playback.
    
16. 
    The access control module solution shall be able to display real-time door status, such as locked, unlocked, closed or open, to provide control functions for the defined access point and to display real-time cardholder information.
    
17. 
    The access control module solution shall provide an access request notification option that opens a notification flyout in the full viewing client when selected events are triggered.
    
18. 
    The access control module solution shall support two-way audio to make it possible to communicate with a person by the access point triggering an access request notification.
    
19. 
    The access control module solution shall make it possible for operators of the full viewing client to have direct visibility of the status on an access point and to control the access point remotely.
    
20. 
    The access control module solution shall make it possible to instantly view recorded video related to any access event.
    
21. 
    The access control module solution shall be able to show access controlled doors and associated events to the door in maps and operators of the full viewing client shall be able to directly control access points via the map functionality in the full viewing client.
    
22. 
    The access control module solution shall be able to use events from integrated access control systems to generate alarms in the alarm management feature.
    

2. 
   Transactional data solution
   

1. 
   The transactional data solution shall enable the operator to search and view transaction data from third-party systems that are time-linked with video recordings of the relevant transaction activities.
   

FI.License plate recognition solution

1. 
   The license plate recognition solution shall be video-based content analysis (VCA) and recognition of vehicle license plates.
   

FJ.Screen recording service

1. 
   The screen recording service shall enable a computer with Windows installed to act as an IP video camera, sending the contents of its desktop to the recording server to which it is connected.
   

The screen recording service shall only be able to connect to and request video from a computer with the screen recording service installed.

FK.Utilities

1. 
   Software manager utility
   

1. 
   The software manager utility shall offer a centralized platform from which to install, uninstall and upgrade large-scale, multi-server installation of the software solution.
   

FL.Utility to detect system failures

The utility to detect system failures shall immediately notify operators by a siren or beacon light, when there is a system failure (such as hard disk failure, camera failure, and power failure on the recording system).

FM.Hardware Features

1. 
   The NVR shall be available in workstation and rack-mounted form factors to suit different office and data center environments.
   

FO.The NVR shall have a CPU that features Intel Quick Sync Video technology for hardware accelerated decoding of video streams and improved local display performance up to 300 FPS @ 720p.

FP.The NVR shall feature a solid-state storage drive (SSD) on which is installed the operating system (O/S) and VMS software. The SSD is separate from the video recording database to ensure higher performance, faster recovery, and maximum uptime of the system.

FQ.The NVR shall feature video grade hard disk drives, tested and supplied by the manufacturer. The hard disk drives are engineered for write performance and durability, while writing large sequential data blocks during constant operation.

FR.The rack-mounted NVR shall have hot plug disk drives that can be installed or removed while the system is running RAID configuration. (When RAID is not configured then hard discs must be down- powered prior to exchange.) The rack-mounted NVR shall offer RAID configurations to optimize performance, redundancy, and rebuilding of the video recording database in the case that there is a hard disc failure

FS.The rack-mounted NVR height shall be two rack units (2U), or 3.5 inches (88.9 mm).

FT.The workstation NVR shall have standard VESA mount points to be easily mounted to a wall, stand, or monitor.

FU.The NVR shall have dual gigabit network interface cards (NICs) to allow for maximum throughput for recording camera streams and client viewing and playback.

FV.The NVR shall allow easy access to the hard disk drives for upgrade and replacement in the field.

FW.The NVR shall have low power consumption, less than 120W max

FX.All components of the NVR, including processor, network interface, and included RAID controllers, shall have sufficiently high bitrate performance to allow the system to take full advantage of the maximum recording and playback performance of the hard disk drives.

FY.The NVR shall utilize a Windows 10 or later operating system (O/S) for maximum software extensibility.

FZ.The NVR shall be preinstalled with a VMS software suite with configuration wizards to aid setting up cameras, storage, users, motion detection, and included camera licenses, for rapid deployment and set up.

GA.The NVR shall be compatible with thousands of IP cameras, using a camera-specific software driver that takes advantage of each individual camera’s unique features, such as remote configuration, analytics and alarms.

GB.The NVR shall be available with integrated encoders for the direct connection of analog CCTV cameras.

GC.The NVR shall require only one camera channel license per IP address connected, even in cases where an attached encoder can connected more than one analog camera.

GD.The NVR shall offer camera add-on licensing to ensure maximum value and flexibility in the licensing scheme.

GE.The NVR shall be compatible with software add-ons that provide video analytics, retail point of sale (POS) integration, and license plate recognition, and other functionality.

GF.The NVR shall be compatible with third-party software that provide video analytics, retail point of sale (POS) integration, and license plate recognition, and other functionality.

GG.The manufacturer shall not charge a license fee for third-party integrations.

GH.The NVR shall be accessible from a central video management system for remote viewing, remote desktop configuration, video upload, and to centralize maps and alarms. This functionality shall be enabled out of the box with no additional integration required.

GI.The NVR shall support a master/slave configuration that allows video to be viewed from cameras connected to the slave NVRs by connecting to the master NVR only.

GJ.The NVR shall support both local viewing and remote viewing clients for viewing live video and playback of recorded video.

GK.The number of remote viewing clients shall not be limited by the NVR licensing scheme.

GL.The NVR shall include an online system monitoring service that enables resellers to monitor the health of the system and proactively resolve technical issues.

GM.The entire NVR system shall be tested and supported by the manufacturer, including hardware, hard disk drives, and VMS software.

GO.– design drawings

A.Rack-mounted workstation





B.Medium workstation

Directory: files
files -> Answer True False 2 points Question 2
files -> Integer programming and game theory
files -> 4 Integer Programming
files -> Bpa vehicle Window Repair Scenario #1 task: Procure vehicle window relacement. Objective
files -> Pop Warner History
files -> North Carolina Inclusion Initiative Mapping Where Children with ieps are Being Served Purpose
files -> Fall 2013 Spring 2014 Program Data: Standard 1 Exhibit 4d
files -> Hanban – asia society confucius classrooms network 2010 request for proposal
files -> Northern England’s set-jetting locations

Download 192.05 Kb.

Share with your friends: