Video Management System A&E Spec

1. Summary

   1.01.   SUMMARY

   1. Section includes description, architectural and functional requirements, data security requirements, operational capabilities, and computer equipment requirements for an on-premises Video Management System (VMS) supporting an unlimited number of users, cameras, servers, sites and video walls.
   2. Related Sections:
      1. Section 27 00 00 Communications (Division 27).
         1. Section 27 05 00 Common Work Results for Communications.
            1. Section 27 05 28 – Pathways For Communication Systems.
         2. Section 27 10 00 – Structured Cabling.
            1. Section 27 13 00 – Communications Backbone Cabling.
         3. Section 27 15 00 – Communications Horizontal Cabling.
      2. Section 28 00 00 Electronic Safety and Security (Division 28).
         1. Section 28 05 00 - Common Work Results For Electronic Safety And Security. 
         2. Section 28 08 00 Commissioning Of Electronic Safety And Security. 
         3. Section 28 08 11 Testing For Baseline Performance Criteria.

2. References

   1.02.    REFERENCES

   1. Abbreviations And Acronyms:
      1. AES: Advanced Encryption Standard.
      2. API: Application Programming Interface.
      3. CE: Conformity for Europe.
      4. DES: Data Encryption Standard.
      5. FPS: Frames per Second.
      6. GOP: Groups of Pictures.
      7. HTTPS: Hyper Text Transfer Protocol Secure.
      8. MIP SDK: Milestone Integration Platform Software Development Kit
      9. NAT: Network address translation.
      10. NVR: Network Video Recorder.
      11. PTZ: Pan-tilt-zoom.
      12. REST: Representational State Transfer.
      13. SaaS: Software as a Service.
      14. SLC: Software License Code.
      15. SNMP: Simple Network Management Protocol.
      16. UPnP: Universal Plug and Play.
      17. VMS: Video Management System.
   2. Definitions:
      1. Access Control: A function or a system that restricts access to authorized persons only.
      2. Active Video Storage: High-performance video storage used for active video recording.
      3. Archived Video Storage: Secondary video storage used for storing video beyond an initial retention period.
      4. API: Application Programming Interface, a set of clearly defined methods of communication between various software components.
      5. Authentication: A process that establishes the origin of information, or determines an entity’s identity.
      6. Authorization: A process that associates permission to access a resource or asset with a person and the person’s identifier(s) for the purpose of granting or denying access.
      7. Groups of Pictures (GOP): Each coded video stream has different types of encoded pictures, whose sequencing into picture groups is a configurable setting. Pictures are grouped together in ways that enhance the visual result of a video sequencing, and also to enhance video searching.
      8. Multi-site: Reference to a VMS system that spans multiple physical site locations.
      9. PTZ Patrol or PTZ Tour: Automatic pre-programmed zooming into and out of a PTZ camera’s preset PTZ positions.
      10. PTZ Scan: Automatic pre-programmed camera panning and tilting, back and forth across a PTZ camera’s field of view.
      11. REST: Representational State Transfer (REST) is a software architecture style consisting of guidelines and best practices for creating scalable web services.
      12. RESTful API: Web service API that adhere to the REST architectural constraints.
      13. Simple Network Management Protocol: Simple Network Management Protocol (SNMP) is an Internet-standard protocol for collecting and organizing information about managed devices on IP networks and for modifying that information to change device behavior and to be alerted to changes in device status.
      14. Smart Wall: Video display wall composed of consumer-grade video display monitors, whose contents are managed by event-based application rules applied in real-time.
      15. SNMP Trap. Alert messages sent from an SNMP-enabled device or application agent to a central collector such as SNMP management software.
      16. Universal Plug and Play: A set of networking protocols that permits networked devices, such as personal computers, printers, Internet gateways, Wi-Fi access points, IP video cameras and mobile devices to seamlessly discover each other's presence on the network and establish functional network services for data sharing and communications.
   3. Trademarks used in this document:
      1. Immervision: ImmerVision Enables®
      2. Intel: Intel®, Xeon®
      3. Microsoft: Microsoft®, Windows®, Active Directory®, Hyper-V®
      4. Milestone: XProtect®, Husky™, Arcus™, Milestone Interconnect™
      5. Veracity: COLDSTORE™
      6. VMWare: VMWare®
      7. Western Digital: MyCloud™

3. Submittals

   1.03.    SUBMITTALS

   1. Submit under provisions of Section 01 30 00 - Administrative Requirements.
   2. Product Data: Manufacturer's data sheets on each product to be used, including:
      1. Preparation instructions and recommendations.
      2. Storage and handling requirements and recommendations.
      3. Installation methods.
   3. Shop Drawings: Schematic of system components with physical space requirements.

4. Quality Assurance

   1.04.    QUALITY ASSURANCE

   1. Install and test VMS, including its workstations and integrations.
   2. Qualifications:
      1. Manufacturers:
         1. Manufacturer shall regularly and presently produce, as one of the manufacturer's principal products, the equipment, services, and material specified for this project.
      2. Contractors / Installers:
         1. Contractor or security sub-contractors shall be licensed to perform security installations in the state the work is to be performed.
         2. Contractor or security sub-contractor shall have a minimum of five (5) years’ experience installing and servicing systems of similar scope and complexity. 
         3. Contractor shall provide four current references from clients with systems of similar scope and complexity which became operational in the past three years. 
            1. Provide at least three references utilizing the same system components, in a similar configuration as the proposed system. 
            2. References shall include a current point of contact, company or agency name, address, telephone number, complete system description, date of completion, and approximate cost of the project.  The owner reserves the option to visit the reference sites, with the site owner’s permission and representative, to verify the quality of installation and the reference’s level of satisfaction with the system. 
         4. Utilize only factory-trained technicians to install, program, and service VMS equipment. 
            1. Provide copies of system manufacturer certification for all technicians. 
            2. Ensure technicians have a minimum of five continuous years of technical experience in electronic security systems. 
         5. A local service facility is required. 
            1. Facility shall be located within 60 miles of the project site. 
            2. Facility shall maintain sufficient spare parts inventory to support the service requirements associated with this contract, as agreed by Owner Representative. 
            3. Facility shall include appropriate diagnostic equipment to perform diagnostic procedures. 
            4. Owner’s Representative reserves the option of surveying the company’s facility to verify the service inventory and presence of a local service organization.
         6. Provide evidence that installing service company is an authorized dealer in good standing for the product’s manufacturer, and that it meets the manufacturer’s technical certification requirements.

5. Delivery, storage, and handling

   1.05.    DELIVERY, STORAGE AND HANDLING

   1. Deliver materials in manufacturer’s labeled packages.  Store and handle in accordance with manufacturer’s requirements.

6. Warranty

   1.06.    WARRANTY

   1. Manufacturer Warranty:
      1. The manufacturer shall warrant that the software and hardware products are free from defect in materials and/or workmanship for a period of one year from the date of shipment.
      2. During the warranty period, the manufacturer shall provide periodic updates.
   2. Special Warranty:
      1. Maintenance & Service:
         1. General Requirements
            1. Contractor shall provide all services required and equipment necessary to maintain the VMS in an operational state as specified for a period of one year after formal written acceptance of the system.  Contractor shall provide all necessary material required for performing scheduled adjustments or other non-scheduled work.  Impacts on facility operations shall be minimized when performing scheduled adjustments or other non-scheduled work. 
         2. Description of Work:
            1. Deploy VMS including installation and setup of new server hardware and software, plus any new and existing equipment specified in Article 2.1. OWNER-FURNISHED PRODUCTS.  
         3. Personnel:
            1. Provide service personnel certified in the maintenance and repair of the selected type of equipment and integrations, and qualified to accomplish all work promptly and satisfactorily. 
         4. Schedule of Work:
            1. Perform work during regular working hours, Monday through Friday, excluding federal holidays.
         5. Emergency Service:
            1. The owner shall initiate service calls whenever the system is not functioning properly. 
            2. Provide Owner with an emergency service center telephone number.  Emergency service center shall be staffed 24 hours a day 365 days a year.  Owner shall have sole authority for determining catastrophic and non-catastrophic system failures within parameters stated in General Project Requirements.
            3. For catastrophic system failures, provide same day four-hour service response with a defect correction time not to exceed eight hours from notification.  Catastrophic system failures are defined as any system failure that Owner determines will place a facility at increased risk. 
            4. For non-catastrophic failures, provide service response within eight hours with a defect correction time not to exceed 24 hours from notification.
         6. Operation:
            1. As part of scheduled adjustments and repairs, verify operation of the system as demonstrated by the applicable portions of the performance verification test.

7. Licensing

   1.07.    LICENSING

   1. Provide manufacturer licensing of installed VMS system for a period of one year from date of substantial completion.
   2. Pricing shall conform to an on-demand model, with no up-front licensing expense.
   3. Licensing shall not require the use of hardware dongles.
   4. Provide a “changes without activation” function that allows additions and replacements of limited number of devices without requiring license activation.

1. Owner-furnished products

   2.01.    OWNER-FURNISHED PRODUCTS

   1. New Products:
      1. [SPECIFIER: list new products furnished by owner, such as computers, cameras or other devices, or delete paragraph A.]
   2. Existing Products:
      1. [SPECIFIER: list existing products/systems furnished by owner, such as cameras, computers and network infrastructure, or delete paragraph B.]

2. Systems

   2.02.     SYSTEMS

   1. Manufacturer: 
      1. BluBØX, Inc., 9 Bartlett Street, Suite 334, Andover, MA 01810
         1. Telephone: (844) 425-8209
         2. Website: www.BluBØX.com
      2. Substitution Limitations:  No Substitutions.
   2. Product Options: 
      1. Editions: VMS software editions are:
         1. Expert: Provides a Milestone XProtect Expert VMS system supporting:
            1. Distributed Recording: Management of local and remote Recording Servers with central surveillance monitoring using a Distributed Recording Servers Architecture.
            2. Central Hierarchical Management: Connection to Corporate systems under a hierarchical Federated Architecture, enabling parent Corporate systems to centrally manage child Expert and Corporate systems, with infinite scalability for central and regional site system management.
            3. Central Surveillance Participation:  Connection to a central Corporate system performing central surveillance operation across geographically dispersed sites under a Driver-Connected Architecture.
         2. Corporate: Provides Milestone XProtect Corporate VMS system with all of the capabilities of an Expert system, plus central management (using a Federated Architecture) and central surveillance monitoring capabilities (using a Driver-Connected Architecture) across geographically-distributed individually-managed site systems, including a variety of compatible VMS and NVR systems, with option to perform central recording for remote sites including mobile vehicle systems and other intermittently connected systems, 
         3. Compatible VMS and NVR Systems: The following Milestone products may be utilized by a central Corporate system in a driver-connected multi-site architecture deployment to gain central surveillance operaion accross geographically dispersed sites and sysems, using the specified or later product versions:
            1. XProtect Corporate 2013
            2. XProtect Expert 2013
            3. XProtect Enterprise 8.0
            4. XProtect Professional 8.0
            5. XProtect Express 1.0
            6. XProtect Essential 2.0
            7. XProtect NVR SE 1.0
            8. Husky NVR M10 1.4
            9. Husky NVR M30 2013
            10. Husky NVR M50 2013
            11. Milestone NVR Husky 500 2013
            12. Arcus 1.4, embedded software in such third-party systems as:
                1. LenovoEMC px2-300d NVR and LenovoEMC px4-400d NVR
                2. Veracity COLDSTORE Arcus
                3. Western Digital My Cloud™ Surveillance Series NAS
      2. Trial Versions: Trial versions are offered for both editions that can be easily upgraded to a paid version without having to redo integrations or configurations.
   3. Video Management System (VMS):
      Description. Video surveillance management system supporting an unlimited number of users, cameras, servers and sites, with options for high availability, smart video walls, mobile devices and central surveillance operations.
      1. VMS shall consist of:
         1. One or more VMS servers:
            1. Physical Windows servers.
            2. Virtualized Windows servers, using:
               1. Microsoft Hyper-V.
               2. VMWare.
         2. One or more software components per VMS server:
            1. Management Server. The central application component of the VMS responsible for handling system configuration, distributing the configuration to other system components, such as recording servers, and for facilitating user authentication.
            2. Failover Management Server. An installation of the management server application in a Microsoft Windows Cluster, which ensures that another server takes over the management server function, should the first server fail.
            3. Recording Server. The server application responsible communications, recording and event handling for all devices (cameras, video and audio encoders, input/output (I/O) modules, metadata sources, etc.), including:
               1. Retrieving video, audio, metadata and I/O event streams from the devices.
               2. Recording video, audio and metadata.
               3. Providing access to live and recorded video, audio and metadata.
               4. Providing access to device status.
               5. Triggering system and video events on device failures, events, etc.
               6. Performing motion detection and generate Smart Search metadata.
               7. Communicating with other Milestone products when using the Milestone Interconnect technology.
                  1. The recording server writes video streams, audio streams and their metadata to a high-performance media database.
            4. Failover Recording Server (Corporate edition only). The failover recording server application is responsible for taking over the recording task should a recording server fail.
               1. The failover recording server can operate in two modes: cold-standby for monitoring multiple recording servers and hot-standby for monitoring a single recording server.
               2. Both code- and hot-standby mechanisms shall offer fully automatic and user transparent failover in the event of hardware or system failure, with automatic synchronization at system recovery.
            5. Event Server. The event server application handles various tasks related to events, alarms, maps and third-party integrations via the Milestone Integration Platform Software Development Kit (MIP SDK).
            6. Failover Event Server. An installation of the event server application is achieved by installing the event server in a Microsoft Windows Cluster, which ensures that another server takes over the event server function should the first server fail.
            7. Log Server. The server application is responsible for storing to a database all log messages for the entire system. There are three types of logs: System Log for errors, warnings and system information; Audit Log for user activity in client applications; and Rule Log used by the system administrator for the creation of logs entries on the occurrence of specific events.
            8. Service Channel. The service channel application is responsible for communicating various service and configuration messages to the Smart Client and mobile server, and to third-party components listening to the service channel.
            9. Mobile Server. The server application responsible for hosting the Web Client and for providing access to the VMS for the Web Client and Milestone Mobile client users.
            10. SQL Server. The database server application for the management server, event server and log server applications.
            11. Active Directory (required for multi-site systems). Active Directory is not required for single-site systems, but is recommended for cyber security purposes. See VMS manufacturer’s documentation. There are two options for Active Directory deployment:
                1. Use of an existing customer Active Directory domain.
                2. VMS-specific Active Directory domain.
         3. One or more PCs or laptops for client software applications.
         4. Client software application components, intended to run on Windows-based PCs and laptops:
            1. Management Client. The administration interface for all parts of the VMS, designed to be run remotely from, for example, an administrator’s computer.
            2. Smart Client. Designed for day-to-day use by dedicated operators, to be run remotely on the operator’s computer.
         5. One or more tablets or smartphones for the web client or the mobile app.
         6. Tablet or smartphone mobile app and web-client app:
            1. Mobile Client.  App for smartphone or tablet users, for easy access to live and playback of cameras, and to activate system events and outputs. Additionally, for use as a remote recording device by using the mobile device’s built-in camera, whereby video from the device’s camera is streamed back to the VMS and recorded like a standard camera.
         7. Browser-based software intended for personal computing devices such as PCs, laptops, tablets, and smartphones:
            1. Web Client. Browser-based application (Web Client) for the occasional or remote user that needs easy access to live video monitoring, video playback and export.
         8. Optionally one or more smart video walls.
            1. See Section 28 51 19.13 SMART VIDEO WALLS.
         9. Optionally one or more individual Milestone video systems and products connected to gain central surveillance operation across geographically dispersed sites.
            1. See paragraph C.4 Multi-System Architectures.
         10. Ethernet Networks:
             1. Camera Network. Local network whose capacity and configuration is suitable for the level of video data transmission established by the system design and its intended usage.
             2. Server Network. Internet-connected network whose capacity and configuration is suitable for the level of video data transmission, systems integration, and user operations established by the system design and its intended usage, including remote VMS sites and remote users.
             3. Network Traversal:
                1. Enable software clients to access recording servers from outside a network address translation (NAT) firewall (port forwarding).
                2. Enable secure remote connections to cameras across different types of private and public networks.
   4. Performance / Design Criteria:
      1. Scalability: Provide component-based system architecture to support scaling of VMS from small systems (50 to 100 cameras) to very large systems (several thousand cameras) for single-site or multi-site deployment, whereby:
         1. For Small Systems: All software components can be installed on the same server if the server is able to handle the combined load.
         2. For Large Systems: Software components can be installed on separate dedicated servers to scale and distribute the load.
      2. Availability and High Performance: Provide the following capabilities to ensure high VMS availability and performance.
         1. Failover Servers: Provide hot and cold failover server capabilities.  
         2. Load Balancing: Support Windows Server Failover Clustering.
      3. Operating Systems. Provide server and client software applications that are native 32-bit or 64-bit Microsoft Windows applications.
      4. Network Addressing. Provide support for both IPv4 and IPv6 addressing.
      5. SNMP Agent. Provide VMS functionality to act as an SNMP agent that can generate an SNMP trap upon a rule activation.
      6. Video Encoding. Provide simultaneous digital multi-channel live streaming and recording of video from IP cameras and IP video encoders without any software limitations on the number of cameras per recording server, with support for the following standards and options:
         1. Standards:
            1. H.264 and H.265
            2. JPEG images
            3. MPEG-4 and MPEG-4 ASP
            4. MJPEG
            5. MxPEG
         2. Options:
            1. Toggling between recording key frames only or full video stream.
            2. Adjustable group-of-picture (GOP) length for MPEG-4, H.264 and H.265 video.
      7. Multi-Live Video Streaming. Provide multiple streams for live viewing using any combination of supported standards, video resolutions and frame rates. 
      8. Device Video Quality Optimization. Video quality optimized per available bandwidth, device screen resolution, and View camera window sizes:
         1. Smart Client Optimization. Optimize viewing performance for remote viewing according to the available bandwidth and View layouts, maximizing video stream quality per display capabilities of defined Views.
         2. Web Client and Mobile Client Optimization: Optimize transcoding by capping video stream resolution and frame rate for transmission to Web Client and Mobile Client.
         3. Direct-to-Web-Client Option. Option to bypass transcoding logic and send video streams direct to Web Clients.
      9. Multicasting. Provide optimization of network load in systems with many users by sending one video stream per camera to multiple Smart Clients.
      10. Multiple Language Support. Provide the following support for multiple languages:
          1. Management Client: Arabic, Chinese (Simplified), Chinese (Traditional), Czech, Danish, Dutch, English, French, German, Italian, Japanese, Korean, Polish, Russian, Spanish, Swedish.
          2. Smart Client, Web Client, Mobile Client: Arabic, Bulgarian, Chinese (Simplified), Chinese (Traditional), Croatian, Czech, Danish, Dutch, English, Farsi, Finnish, French, German, Hebrew, Hindi, Hungarian, Icelandic, Italian, Japanese, Korean, Norwegian (Bokmål), Polish, Portuguese (Brazilian), Russian, Serbian, Slovak, Spanish, Swedish, Thai and Turkish.
      11. True Multi-Window Support. Provide true multi-window support whereby secondary windows have full functionality and can be operated in independent mode or synchronized mode where they follow the control of the main window.
      12. System Capacities. Provide the following maximum capacities, constrained only by the physical performance capabilities of installed server hardware and network infrastructure:
          1. Unlimited cameras.
          2. Unlimited client software users.
          3. Unlimited user mobile devices.
          4. Unlimited client PCs or laptops.
          5. Unlimited servers.
          6. Unlimited smart video walls, with an unlimited number and combination of display monitors.
          7. Unlimited sites.
          8. Unlimited system rules.
          9. Unlimited time profiles.
          10. Unlimited software client profiles.
          11. Unlimited active video storage.
          12. Unlimited archived video storage.
          13. Recording rates of at least 30 frames per second per camera, limited only by hardware capabilities.
      13. Data Security. Provide the following data security capabilities:
          1. On-premises camera data in transit. HTTPS connections from recording server to cameras that support HTTPS connections.
          2. On-premises recorded video in transit. HTTPS connections from recording server to client software.
          3. Off-premises live and recorded video in transit. HTTPS connections from recording server to browser-based web clients and XProtect mobile apps.
          4. Data integrity of exported video. Support for:
             1. Limiting viewing of recorded video to the Smart Client Player application.
             2. Per-export password protection for playback.
             3. 256-bit AES Encryption.
             4. Digital signature inclusion with export.
             5. Player’s Verify Signatures function to validate authenticity of exported video recording.
          5. Digital Certificates Options. Use of system default-generated or customer-provided digital certificates for connections to the Mobile Server.
          6. Data access control. Support for:
             1. Secure Windows Active Directory AD user authentication.
             2. User profiles restricting camera access and video viewing, playback and export, including by day and time-of-day.
             3. Timestamped audit log of who logged in, viewed liver or recorded video, or exported video.
             4. Option to prevent re-export of exported video.
          7. Data at rest integrity and encryption. Implementation of:
             1. Two modes of video database encryption using DES-56 encryption:
                1. Light Encryption. Encrypts only the first part of the JPEG or MPEG-4/H.264 video data (the header), to use less processing power to encrypt the video. Video cannot be decoded without the information contained in the encrypted header.
                2. Strong Encryption. Encrypts all parts of the video data stored in the database.
             2. Digital signing of video databases.
          8. System Hardening. Provide a system hardening guide that:
             1. Describes data security, network security and physical security measures and best practices for securing the installed video management software (VMS) against cyber-attacks. This includes security considerations for the hardware and software of servers, clients and network device components of a video surveillance system.
             2. Incorporates standard security and privacy controls and maps them to each hardening recommendation.
      14. Multi-System Architectures. Provide three architecture options for multi-site deployments:
          1. Distributed Recording Servers. The Distributed Recording Servers architecture, intended for sites with stable network connections between the central site and any number of remote sites.
             1. Management server is at central site, providing user access and system management only at central site.
             2. Other server functions may run at central site.
             3. Each site has at least one Recording server and optionally a Failover Recording server for any or all of its Recording servers.
          2. Federated Architecture. Federated architecture, intended for sites with stable network connections between all sites, establishes central management of, and central surveillance operations for, geographically dispersed sites via one or more levels of parent/child system connections.
             1. Parent systems must be Corporate systems.
             2. Child systems may be any number of Corporate, Expert, Husky M500 Advanced and Husky M550 Advanced systems.
             3. Child Corporate and Expert systems function as autonomous sites upon loss of network connectivity.
          3. Driver-Connected Architecture. Driver-connected architecture is suitable for providing central surveillance operations capabilities for a centrally managed and distributed system where all or some of the network connections between the local systems are unstable or intermittent, including vehicle mobile systems:
             1. Central surveillance system must be Corporate edition.
             2. All or some systems are running on different network domains.
             3. Local access is available for each site system.
             4. Any number of remote sites, which may run any size and any number of separate supported VMS and NVR systems. See paragraph B.1.c Compatible Systems.  
   5. Application Functions. Provide the following video management system features and functions in the Management Client.
      1. Time Profiles. Named periods of time by day and time of day, used in defining schedules, event triggers, and other time-based system functions. Time Profiles include:
         1. Daily, Weekly, Monthly and Yearly intervals.
         2. Range of occurrence by start and end date, or number of occurrences.
      2. Metadata. Category of searchable data that may be associated with events and other data, including:
         1. User-provided data, such as notes about events.
         2. Device-provided data such as video analytics data, GPS location data.
      3. Rules Engine. Used for automating system actions, including:
         1. Control of alarm-based and event-based recording.
         2. Display of camera views and maps.
         3. Change of smart wall configuration.
         4. PTZ camera scans and tours.
         5. Event-based notifications.
         6. External system interactions.
         7. Single manual macro-actions for executing multiple system actions.
      4. Customizable Dashboards. Customizable built-in dashboards:
         1. System Monitor. Real-time display and reporting of errors and system conditions including, but not limited to:
            1. Customizable Normal, Warning and Critical system monitor and event triggers for:
               1. CPU and Memory usage on servers.
               2. Hard disk free space.
               3. Storage space utilization.
               4. Predicted retention time for storage definitions.
               5. Per-video stream FPS for live and recording video.
            2. Task- and component-specific live monitoring.
            3. Dockable tab with system performance and use information.
         2. System Dashboard. Dashboard display containing detailed and up-to-date information about current recording servers, cameras, microphones and their storage areas. Dashboard displays include the following items:
            1. Storage Overview. Includes information about database and archive
               1. Recording Server Database. Pie-chart status information for the storage elements on each hard:
                  1. Video recordings and archives.
                  2. Other data, including video archives from other archive storage locations (such as network drives).
                  3. Free space.
                  4. Disk size.
               2. Current Tasks. An overview of tasks of the selected database, their begin time, estimated end time and progress.
               3. Storage Database. An overview of the selected storage and the database(s) in it.
               4. Camera Group/Microphone Group/Speaker Group Database. A table containing all devices in the selected group, showing their names, storage, the space used in the storage area and the database status.
               5. Camera/Microphone/Speaker Database. A table containing the selected device, showing its name, storage, the space used in the storage area and the database status.
         3. Customer Dashboard. Configurable display for system, server, storage and device status and errors.
      5. Backup and Restore. Built-in backup and restore support for manual system backup of all configuration data, including but not limited to:
         1. All system configuration data.
         2. Full device configuration data.
         3. Maps.
         4. Alarm settings and definitions.
         5. User-defined rules, events and dashboard customizations.
         6. Recorded video bookmarks.
         7. Software client camera views.
      6. Configuration Reporting. Provide complete or partial documentation of system configuration, including custom and site-specific free-text information, contractor’s notes and option for logo inclusion.
      7. User Authentication:
         1. Log-in Options. System log-in via:
            1. Microsoft Active Directory.
            2. Local Windows user accounts.
            3. Basic user system account (username and password credentials).
            4. Dual authentication, a.k.a. two-person rule, requiring two verified persons to gain access (Corporate only). 
         2. Auto-Log-In. Use of current Windows logon for authentication, with Auto-log-in and auto-restore of camera views.
         3. Smart Client Dual Authorization Option. System access granted only after approval by a second logged-in user or supervisor.
      8. Customizable Application Workspaces. Users may adapt the application layout and personalize the application for their individual preferences and task performance requirements.
      9. User Rights Management. Common and central detailed management of user rights across all user and programmatic (SDK) interfaces, using roles, users, and user groups.
         1. Roles. Defining roles establishes permissions (also called “rights”) that determine which system features may be accessed by users and groups.
         2. Overall system permissions. Globally allow or deny permissions for devices and functions (such as manage, read, edit and delete).
         3. Device-specific permissions.  Allow or deny permissions for specific individual devices and functions (such as manage, read, edit and delete).
         4. Permissions. Categories of permissions:
            1. User Rights: Define roles, create user groups, add and delete users, manage permissions for roles, user groups and users, generate user rights management reports. Tiered user management rights shall enable differentiated administrator rights per administrator role.
            2. Tiered User Rights: (Corporate only) Assign partial management permissions to system administrators using the Management Client.
            3. User Rights Inheritance: (Corporate only) Create sub-management domains where management of a specific set of devices can be assigned to a specific system administrator.
            4. General: Management Client and Smart Client profiles, Evidence Lock profile, dual authorization rights, system log-in time profile.
            5. Cameras: Visibility, administrate, live view (within time profile), playback (within time profile), search sequences, export, smart search, AUX commands, manual recording, bookmark functions, Evidence Lock functions.
            6. Microphones and speakers: Visibility, administrate, listen to live audio (within time profile), playback audio (within time profile), search sequences, export, manual recording, bookmark functions, Evidence Lock functions, speak to speakers.
            7. Inputs and outputs: Visibility, administrate, status, activation.
            8. PTZ control: Manual control, activate PTZ presets, PTZ priority, manage PTZ presets and patrolling, lock/unlock PTZ presets, reserve and release PTZ session.
            9. Remote recordings: Retrieve remote recordings.
            10. External events: Visibility, administrate, trigger.
            11. Servers: Enterprise server access and authentication details, Federated Architecture site permissions.
            12. Alarms: Visibility of alarms and ability to manage alarms.
            13. MIP: Milestone Integration Platform plug-in permissions.
            14. Application: Manager, Smart Client/Web Client/Mobile, live/ playback/setup, status API and service registration API.
            15. Smart Wall: Visibility, administrate, control, playback.
      10. Application Workspace Optimization. Options for optimizing application workspaces in the Management Client software.
          1. Themes. User interface color schemes enabling user choice of dark or light themes.
          2. Display of Application Functions. Toggle on and off the availability of functions.
          3. Client Profiles. User-defined profile-base central management of workspace optimization for categories of users and user skill levels. (Also available in Smart Client.)
      11. Device Discovery. Wizard function to automatically add devices to the system using Universal Plug and Play (UPnP) discovery, IP network range scanning, or manual device detection. Hardware wizard provides:
          1. Swift replacement of malfunctioning devices with preservation of configuration settings and recordings, including those for attached cameras, microphones, speakers, inputs, outputs and metadata devices.
          2. Moving of devices and attached devices between recording servers in during runtime with no loss of settings, recordings, rules, permission, etc.
          3. User ability to enable and disable devices for purposes of maintenance or temporary deactivation.
      12. Smart Connect. Easy configuration of internet access to the Mobile Server by automatic configuration of firewalls and internet routers via UPnP, with verification of configuration and operation of internet connection, with option to email connection details to Mobile Client users. Includes automatic Mobile Server on LAN via UPnP.
      13. Camera Image and Video Stream Management. Adjustment of per-camera and per-video stream settings, with each camera allowed one stream for live viewing and one stream for recording, including an optional per-camera or per-camera-group preview window:
          1. Per Camera or Camera Group. Settings for brightness, color level, compression, maximum bit rate, resolution and image rotation.
          2. Per Video Stream. Settings for frames per second (FPS), resolution, image quality, video encoding format, FPS, and resolution.
          3. Privacy Masks. System-defined camera image privacy masks hide certain areas in the camera image for live view, recording, and video export.
      14. PTZ Camera Control. Camera-based and system-based PTZ camera control including the following capabilities:
          1. Camera PTZ preset positions. Camera-based PTZ presets may be imported from the camera and renamed for use in system-based manual and automatic PTZ control.
          2. Automated Use of PTZ Presets. Scheduled and event-based rules capability to move PTZ cameras to pre-set positions.
          3. System-based PTZ preset positions. System-based PTZ presets are definable for use in system-based manual and automatic PTZ control.
          4. PTZ Scans. Pre-programmed automatic scans of the camera’s field of view, for cameras supporting system-based control.
          5. PTZ Patrols. Multiple per-camera PTZ patrolling schemes may be defined with the following options:
             1. Adjustable wait times between preset position changes.
             2. Disabling of motion detection to avoid false detection alarms.
             3. Multiple patrolling schedules per camera per day, with different schedule for days, nights and weekends.
          6. PTZ Control Priorities:
             1. Provide 32,000 PTZ priority levels for control of rights between different operators and automatic scanning and patrolling schemes.
             2. PTZ Scans and Patrols shall pause for higher-priority manual or event-based camera control, and resume after manual session timeout and completion of event camera control period.
          7. Manual PTZ Control. Manual PTZ control options:
             1. Joystick.
             2. Virtual joystick function.
             3. Lock PTZ control.
             4. Overlay buttons.
             5. PTZ point-and-click control.
             6. PTZ preset positions.
             7. PTZ zoom to a defined rectangle.
             8. Start, stop and pause patrolling.
             9. Video overlaid PTZ control.
             10. View who have PTZ control and time to automatic release.
          8. 360° PTZ Viewing. Capability for continuous 360° camera views is provided through utilization of the ImmerVision Enables panomorph lens technology.
      15. System Management. Configuration management for all sites, systems, licenses, devices, rules, schedules, users, maps, alarms, recording, client views, with configuration changes applied instantly including while recording is in operation.
      16. Single-Computer Pre-Configuration. Upon selection of “Single Computer” installation type at software installation time, configuration settings specific to single-computer installations are automatically performed to simplify installation.
      17. Configuration Fallback for Local Access. Local recording server configuration data becomes available during periods where the central management server is inaccessible.
      18. Configuration Backup. Manual data backup capability for all configuration data.
      19. Video Playback. Smart Client video playback includes, but is not limited to, the following functions:
          1. Playback. Play back video of camera windows on the Playback tab or Sequence Explorer tab. Independent playback capability provides the simultaneous independent playback of recorded video from one or more cameras.
          2. Playback Digital Zoom. Magnification of recorded video to facilitate detail viewing.
          3. Navigation. Advanced video navigation includes fast/slow playback, jump to date/time, single step and video motion search
          4. Multi-Window Timeline. Integrated video timeline with time navigation and playback controls, including an integrated function to select a time interval for export or video retrieval from Edge Storage devices and interconnected systems, including toggle between simple and advanced timeline mode
          5. Bookmarks. Manually define quick or detailed bookmarks, with optional Headline and Description information that is searchable and editable.
             1. Bookmarks are shown in timeline with instant preview.
             2. Listing and previewing of bookmarks in recording search.
             3. Bookmark reports enable effortless incident documentation.
             4. Direct video export of a bookmark reduces the time needed to prepare forensic video material.
          6. Overview. An overview of recorded sequences and bookmarks.
          7. Instant Camera Window Placement. Drag-and-drop camera placement provides instant replacement of window content with selected camera.
      20. Video Export and Print. Options for video export and printing include, but are not limited to:
          1. Snapshot. Produce instant visual documentation of a camera by saving the camera image to a file, or sending it directly to a printer
          2. Storyboarding. The storyboarding function makes it possible to include video sequences from different or overlapping time intervals form different cameras in the one and the same export.
          3. Export. Export in XProtect format; including the standalone Smart Client Player application for simple instant viewing by authorities.
          4. Export Preview. Review video just prior to export, with looped playback option.
          5. Export Data Protection. Encryption and password protection of exported video material with choice of following encryption algorithms: 56-bit DES 128, 192 and 256-bit AES.
          6. Export Digital Signature. Secure video evidence handling with a digital signature of exported video material that enables users to verify the video has not been modified or tampered with when viewing the exported video in the Smart Client Player.
          7. Export Formats: Create evidence material in media player format (AVI files), MKV format, or still image format (JPEG images).
          8. Re-Export. Re-Export allows an authorized individual to export a selection from the original video exported. Option to disable re-export prevents undesirable re-distribution of sensitive video recordings.
          9. Bulk Export. In a single step, export in multiple formats to multiple destinations, including direct export to optical media, to ensure consistency across exported video sequences in various formats, and reduce human error possibilities.
          10. Export comment.  Two video formats support inclusion of comments in exported video:
              1. XProtect format. Include general and/or camera-specific comments to a video export file.
              2. Media Player format. Include comments as pre/post slides.
          11. Video incident Report Printing. Utilize still images rather than clips to print incident reports including images, surveillance details and free-text user comments.
      21. Sequence Explorer. Provides thumbnail-based video review capabilities in support of investigation tasks via several approaches to searching sequences of video:
          1. Sequence Search. Search in recording sequences on one or more cameras based on motion detection, events or bookmarks.
          2. Timeline Search. Navigate through video content using the timeline.
          3. Smart Search. Search for motion only in selected areas on a single camera.
          4. Bookmark Search. Search for bookmark headlines or descriptions, with matching results shown instantly in the thumbnail overview.
          5. Navigation. Smooth navigation with sliding preview and “drag-and-throw” function for video thumbnails.
          6. Preview. Selected sequence previews with auto play and direct export support.
      22. Event and Alarm Management. Single-point alarm management function of all internal system alarms and external security alarms. Events are pre-defined or user-specified incidents on the VMS system that can be set up to trigger an alarm, including analytics events. Alarm management capabilities include, but are not limited to:  
          1. User-definable alarm descriptions and work instructions.
          2. Alarm list with extensive filtering capabilities and an alarm preview in both live and playback mode.
          3. Customizable alarm priorities.
          4. Extensive alarm sort and filtering functions to facilitate identification of the most critical alarms.
          5. Instant preview of primary and related cameras to facilitate false alarm reduction.
          6. Map locations automatically linked to alarms.
          7. Tight integration with the map function allowing operators to indicate and acknowledge active alarms via map.
          8. Automatic assignment of user alarm ownership including optional escalation and alarm forwarding.
          9. Alarm escalation with option to forward alarms to operators with appropriate skills to handle specific types of alarms.
          10. Automatic association of alarms with one or more cameras, with automatic display of camera video in the alarm preview window.
          11. Customizable alarm statuses to enable alignment of the alarm handling workflow with existing workflows and security systems.
          12. Alarm notification to a single or a groups of Milestone Mobile client users using Push Notifications.
          13. Alarm handling result codes enabling the tracking of alarm outcomes.
          14. Alarm time profiles specifying that response actions must take place within the specified time profile.
          15. Optional sound notifications for different alarm priorities for notification of new incoming alarms.
          16. Alarm disabling option shall enable users to suppress alarms from a given device for a specified time period.
          17. Common alarm list for all interconnected sites.
          18. Global common alarm list for all sites in a Federated Architecture.
          19. Alarm handling reports providing information about alarm inflow and alarm handling performance.
      23. Trigger Events. Pre-defined and custom-defined events are used in rules to trigger actions.
          1. Event Categories. Events fall into the following categories:
             1. Hardware: Events relating to physical hardware devices connected to the system.
             2. Devices: Events relating to certain functions and states of devices available via connected hardware devices.
             3. External: Events relating to VMS integrations.
             4. Recording Server: Events relating to failover, archiving and database functions.
             5. Analytics: Events from integrated analytics applications and systems.
             6. User-Defined: custom-configured events enabling users to manually trigger actions and events in the system.
      24. Email Notifications. System capability to send email notifications to single or multiple recipients with optional attachment of a camera still image or AVI video clip. Email notifications can be triggered by rules and events.
      25. Two-Way Audio. Audio from cameras with built-in or attached microphones can be configured for listening. Camera built-in or attached speakers can configured for use to talk to individuals in the vicinity of speakers. Additional capabilities include:
          1. Broadcast. Broad announcements can be made by selecting the All Speakers option when talking.
          2. Lock to Selected Audio Devices. Enables continued use of microphones and speakers from selected cameras, while viewing video from a different set of cameras. This enables, for example, informing an individual at risk about the safety status of nearby areas.
          3. Level Meter. Level meter indicates the volume of the speaking operator’s voice, to indicate whether the operator is at a correct distance from the microphone.
      26. Camera-Independent Motion Detection. Provide real-time, camera-independent motion detection with the ability to generate searchable motion metadata.
      27. Camera Navigators. User-defined views of specific sets of cameras in relation to each other, for example, according to floor plan, to enable visually tracking people and objects as they move from one camera’s field of view to another.
      28. Camera Windows. Live and recorded camera video displayed in resizable windows, utilized in several workspaces within the application. Each camera window contains three status indicators:
          1. ​​​​​​​Video Status Indicator. A round dot indicating one of four states:
             1. Green. A connection to the camera is established.
             2. Red. Video from the camera is being recorded.
             3. Yellow. Playing back recorded video.
             4. Gray. The video has not changed for more than two seconds.
          2. Motion Indicator. An icon of a moving person that appears only when motion is detected.
          3. ​​​​​​​Event Indicator. A cyan lightning bolt that appears only when specific events occur, as defined by system administrator.
      29. PTZ Camera Window Controls. PTZ camera windows can be configured to provide virtual joystick camera control and PTZ navigation buttons overlaid on the video image.
      30. Views. Views can display up to 100 content items including, camera windows, web pages, still images, text and interactive items.  View capabilities include, but are not limited to:
          1. Overlay Buttons. Used to add manually control speakers, events, outputs, PTZ cameras and to start/stop recording.
          2. Carousels. Sequenced viewing of video from a specified set of cameras.
          3. Matrix. Shows live video from multiple cameras in any view layout with customizable rotation paths, remotely controlled by computers sending matrix remote commands.
          4. Camera Navigators. Camera navigators facilitate following up on camera view activity.
          5. Navigable HTML Map Pages. Static or active HTML map pages may be used to provide a good overview of premises, and for for switching between different views, such as map page displaying a floor plan.
          6. Private or Shared Views. Private views can only be access by the user who created them. Views may be shared generally and available to all users, or restricted to specific users. Viewing of a content item in a shared view is subject to the viewer’s permissions relating to the content item.
          7. Update on motion only. Optimizes CPU use by allowing motion detection to control whether the image should be decoded and displayed.
      31. View Groups. View groups facilitate view navigation and simplify searching across multiple views by narrowing search scope.
      32. Video Playback. Views provide camera playback capabilities including, but not limited to:
          1. Independent Video Playback. Playback of video in multiple camera windows, each on its own independent timeline.
          2. Timeline Video Playback. Video from multiple camera windows integrated to a common video timeline, with common timeline control from any of the integrated camera windows, including the ability to select a time interval for multiple camera window video export or video retrieval from Edge Storage devices and interconnected systems.
          3. Playback Control. Fast/slow playback, jump to date/time, single step and video motion search.
          4. Overview. Overview of recorded sequences and bookmarks.
          5. Instant Change of Camera. Drag-and-drop placement of a different camera in a camera window, instantly changes the content to video from the new camera, according to the camera window’s current timeline position.
          6. Playback Zoom. Digital zoom allows the operator to see magnified details in video playback.
      33. ​​​​​​​​​​​​​​Maps. Multi-layered physical over view of surveillance video coverage, with interactive access to and control of the VMS system, including the following elements:
          1. Map Images. Map images may be illustrated maps or photographs. Supported image file formats are: bmp, gif, jpg, jpeg, png, tif, tiff, and wmp.
          2. ​​​​​​​Camera Icons. Maps contain camera icons at camera locations on the map. PTZ camera icons show preset camera views as colored angles radiating from the camera.
             1. Live Preview. Hovering mouse pointer over a camera icon displays a live preview in a resizable window.
             2. PTZ Preset Display. Clicking on a PTZ icon preset moves the camera to the preset position.
          3. Microphone Icons. Microphone icons show microphone locations on the map.
             1. Live Listening. Place mouse over microphone icon; press and hold left mouse button to listen to incoming audio from microphone.
          4. ​​​​​​​Speaker Icons. Speaker icons show speaker locations on the map.
             1. Live Speaking. Place mouse over speaker icon; press and hold left mouse button to talk through speaker.
          5. ​​​​​​​​​​​​​​​​​​​​​Hot Zones. Hot zones provide vertical navigation through a hierarchy of maps by clicking on a hot zone.
          6. Map Overview Window. The Map Overview window provides a navigable overview of the map hierarchy set up in Smart Client.
          7. Smart Wall Integration. Maps include drag-and-drop integration with XProtect Smart Wall.
          8. Map Image Updates. Map images may be replaced by an updated version of the map image of the same scale, keeping map icons and other elements in their original locations.
          9. ​​​​​​​Map Display Information. Information display options include but are not limited to:
             1. Real-time status monitoring indication from all system components including cameras, I/O devices and system servers.
             2. Graphical visualization of the system status through color coding.
             3. Hierarchical propagation of status indications to higher ordered maps.
             4. Make different levels of status indications available (alarm, warning and errors).
             5. System performance data for cameras and servers including camera resolution, FPS, network use and disk space.
             6. Option to suppress status indications (such as error and warning) for a given device.
             7. Option to edit device names in a map and assign map-specific names and references to devices in a map, subject to user permissions.
      34. Smart Maps. Uses a geographic information system to accurately reflect geography in the real world, enabling video view and cameras access at multiple locations around the world in a geographically correct way. Unlike maps, which utilize a different map for each location, Smart Map provides the complete picture in a single view.
          1. ​​​​​​​GIS Services. GIS services require Internet access and a service subscription. Supported services include:
             1. Bing Maps.
             2. Google Maps.
             3. OpenStreetMaps.
          2. Default World Map. A standard world geographic background is provided. While it contains contain geo-reference data, it does not contain geographic reference features such as county boundaries, and cities.
          3. Map Layers. Users may toggle on and off the display of map data layers, including but not limited to:
             1. Camera name and field of view.
             2. Quick links.
             3. Street Names.
             4. Building and Business Names.
      35. ​​​​​​​Logging. System actions, events, and conditions are logged to a database with time, date and other related information. Several system logs are provided with multi-system support and settable logging limits: 
          1. Alarm Log. Log of all alarm events.
          2. Event Log. Log of all pre-defined and user-defined events.
          3. System Log. Log of all system-related information.
          4. Audit Log. Detailed log of all user system accesses, configuration changes and operator actions.
          5. Rule Log. Log of all execution and non-execution of rules.
          6. Server Log. Provides information, error and warning logs for VMS server applications and operating systems, including errors reported by cameras.
          7. Multi-site Systems Logging. Individual system logs shall also consolidate centrally from all servers and clients, with caching on the local system during offline scenarios.
          8. ​​​​​​​​​​​​​​​​​​​​​User-Definable Logging Limits. Adjustable size and time limitations for each log file.
      36. ​​​​​​​​​​​​​​Video Storage Management. One or more video storage containers definable with the following characteristics:
          1. Each container consists of a live database and one or more optional secondary disk systems or network drives for archiving recordings, with container-specific archiving schemes and retention times.
          2. Recording capacity shall be limited only by available disk space.
          3. Recording of each device is assigned to a specific storage container.
          4. The assigned storage container for a device or group of devices may be changed from one container to another.
          5. Recorded video data may be manually or automatically moved from a container’s live database storage to its archived storage.
          6. Archived data is still online and available to client software.
          7. Maximum recording times may be set for manual recording.
      37. ​​​​​​​Edge Video Storage. Provide utilization of camera-based storage including the following capabilities:
          1. Video Retrieval.  based on time schedules, events or manual requests, to support retrieving video recordings across low-bandwidth connections. 
          2. Video Consolidation. Provide consolidation of video from multiple storage mechanisms:
             1. Seamless merging of video stored centrally in recording server, and video retrieved from associated camera edge storage, or from an interconnected system.
             2. Optionally consolidate pre-event images recorded locally in camera or video encoder.
      38. ​​​​​​​​​​​​​​Mobile Video Push. Provide Mobile Client software capability for mobile device users to use their mobile device cameras as cameras in the VMS system.  
          1. ​​​​​​​No Mobile Setup. No mobile device setup is required for Mobile Video Push.
          2. ​​​​​​​Metadata Support. Mobile users may include metadata in the video submitted.
          3. ​​​​​​​Central Video Push Configuration. Server-side Video Push configuration enables mobile device use of Video Push feature without required mobile-side configuration.   
      39. Mobile Video Export. Provide video support for mobile device users through the Web Client and Smart Client software via a server-side export function that includes providing a link for later download of the exported data to computers with greater network bandwidth and data storage capabilities.
      40. ​​​​​​​Evidence Lock. (Corporate only) Provide capabilities for assuring the availability of recorded video selected for evidentiary use, including:
          1. ​​​​​​​Extension of video retention. Manual extension of video retention time for a selected set of cameras in a given time interval, where the operator selects an extended retention time from a pre-defined set of retention time options, defined retention and grooming policies.
          2. Video Sequence Metadata. Users may add headline and comments information to locked video sequences in order to enhance their manageability.
          3. Overview of Locked Video Sequences. Search, filter and listing functions provide an overview of locked video to facilitate managing locked evidence, including editing comments, modifying the extended retention time and removing an Evidence Lock.
          4. Locked Video Export. Locked video may be exported though a single step operation.
      41. Server CLustering. The servers on which the following applications reside shall have optional failover capability via Windows Server Clustering:
          1. System management.
          2. Event and alarm management.
          3. Recording.
      42. Reporting. Report capabilities are identified above in the descriptions of software applications providing them.
   6. SDK-Based Integration. Provide an SDK for integration with third-party systems that includes:
      1. Seamless integration of video analytics algorithms and other third-party applications in Smart Client and Management Client.
      2. Compatibility with XProtect Transact and XProtect Retail, which integrate video surveillance with ATMs, point-of-sale (POS) and enterprise resource planning (ERP) systems for managing loss prevention and fraud.
      3. Compatibility with XProtect LPR for automatic reading and tracking of vehicle license plates.
      4. Generic event integration via a simple message-based socket communication interface.
   7. Computer Equipment. Consult with VMS manufacturer to determine current computer requirements appropriate for system design, intended use and desired level of performance. Optimize computer count, and server application distribution across computers, to account for likely system expansion. The following are minimum requirements.
      1. Computer running Management Server:
         1. CPU: Intel Xeon, minimum 2.0 GHz (Dual Core recommended).
         2. RAM: Minimum 1 GB (2 GB or more recommended).
         3. Network: Ethernet (1 Gbit recommended).
         4. Graphics Adapter: Onboard GFX, AGP or PCI-Express, minimum 1024×768, 16 bit colors.
         5. Hard Disk Type: E-IDE, PATA, SATA, SCSI, SAS (7200 RPM or faster).
         6. Hard Disk Space: Minimum 50 GB free (depends on number of servers, cameras, rules, and logging settings).
         7. Operating System: Microsoft Windows Server 2008 R2 (64 bit), Microsoft Windows Server 2008 (32 or 64 bit), Microsoft Windows Server 2003 (32 or 64 bit). Furthermore, to run clustering/failover servers, a Microsoft Windows Server 2003/2008 Enterprise or Data Center edition is needed.
         8. Software:
            1. Microsoft .NET 3.5 SP1 and .NET 4.0 and Internet Information Services (IIS) 5.1 or newer (requires both).
            2. 500 Cameras or less: SQL Server Express Edition. For larger systems or to support frequent database backups, run SQL Server on its own server.
      2. Computer Running SQL Server (if not running SQL Server Express Edition on Management Server computer):
         1. CPU: Intel Xeon, minimum 2.0 GHz (Dual Core recommended).
         2. RAM: Minimum 1 GB (2 GB or more recommended) Network: Ethernet (1 Gbit recommended).
         3. Graphics Adapter: Onboard GFX, AGP, or PCI-Express, minimum 1024×768, 16 bit colors.
         4. Hard Disk Type: E-IDE, PATA, SATA, SCSI, SAS (7200 RPM or faster).
         5. Hard Disk Space: Minimum 100 GB free.
         6. Operating System: Microsoft Windows Server 2008 R2 (64 bit).
         7. Software:
            1. Microsoft .NET 4.0.
            2. SQL Server 2014.
      3. Computer running Recording Server or Failover Server:
         1. CPU: Dual Core Intel Xeon, minimum 2.0 GHz (Quad Core recommended).
         2. RAM: Minimum 1 GB (2 GB or more recommended) Network: Ethernet (1 Gbit recommended).
         3. Graphics Adapter: Onboard GFX, AGP, or PCI-Express, minimum 1024×768, 16 bit colors.
         4. Hard Disk Type: E-IDE, PATA, SATA, SCSI, SAS (7200 RPM or faster).
         5. Hard Disk Space: Minimum 100 GB free (depends on number of cameras and recording settings).
         6. Operating System: Microsoft Windows 7 Ultimate (32 bit or 64 bit), Microsoft Windows 7 Enterprise (32 bit or 64 bit), Microsoft Windows 7 Professional (32 bit or 64 bit), Microsoft Windows Server 2008 R2 (64 bit), Microsoft Windows Server 2008 (32 or 64 bit), Microsoft Windows Vista Business (32 or 64 bit), Microsoft Windows Vista Enterprise (32 or 64 bit), Microsoft Windows Vista Ultimate (32 or 64 bit) or Microsoft Windows Server 2003 (32 or 64 bit).
            1. Recording servers must always run 32-bit Windows.
            2. Multiple instances of the 32-bit Recording Server service may be run on 64-bit Windows with sufficient additional RAM.
         7. Software: Microsoft .NET 4.0.
         8. ​​​​​​​Disk formatting: Follow VMS manufacturer instructions to change disk allocation unit size setting from 4 to 64 kilobytes, to establish required hard disk recording performance.
      4. Computer Running Management Client:
         1. CPU: Intel Core2™ Duo, minimum 2.0 GHz.
         2. RAM: Minimum 1 GB.
         3. Network: Ethernet (100 Mbit or higher recommended).
         4. Graphics Adapter: AGP or PCI-Express, minimum 1024×768 (1280×1024 recommended), 16 bit colors.
         5. Hard Disk Space: Minimum 100 MB free.
         6. Operating System: Microsoft Windows 7 Professional (32 bit or 64 bit), Microsoft Windows 7 Enterprise (32 bit or 64 bit), Microsoft Windows 7 Ultimate (32 bit or 64 bit), Microsoft Windows Vista Ultimate (32 bit or 64 bit), Microsoft Windows Vista Enterprise (32 bit or 64 bit), Microsoft Windows Vista Business (32 bit or 64 bit), Microsoft Windows Server 2008 (32 bit or 64 bit), Microsoft Windows Server 2008 R2 (64 bit) or Microsoft Windows Server 2003 (32 bit or 64 bit). Note that Management Client always runs as 32-bit Windows service.
         7. Software: Microsoft .NET 4.0 Framework, DirectX 9.0 or newer, and Windows Help (WinHlp32.exe).
      5. Computer Running Event Server:
         1. CPU: Intel Xeon, minimum 2.0 GHz (Dual Core recommended).
         2. RAM: Minimum 1 GB (2 GB or more recommended).
         3. Network: Ethernet (1 Gbit recommended).
         4. Graphics Adapter: Onboard GFX, AGP or PCI-Express, minimum 1024×768, 16 bit colors.
         5. Hard Disk Type: E-IDE, PATA, SATA, SCSI, SAS (7200 RPM or faster).
         6. Hard Disk Space: Minimum 10 GB free (depends on number of servers, cameras, rules, and logging settings).
         7. Operating System: Microsoft Windows Server 2008 R2 (64 bit), Microsoft Windows Server 2008 (32 or 64 bit), Microsoft Windows Server 2003 (32 or 64 bit).
         8. ​​​​​​​Software: Microsoft .NET 4.0 and Internet Information Services (IIS) 5.1 or newer.
      6. Computer Running Log Server:
         1. CPU: Intel Xeon, minimum 2.0 GHz (Dual Core recommended).
         2. RAM: Minimum 1 GB (2 GB or more recommended).
         3. Network: Ethernet (1 Gbit recommended).
         4. Graphics Adapter: Onboard GFX, AGP or PCI-Express, minimum 1024×768, 16 bit colors.
         5. Hard Disk Type: E-IDE, PATA, SATA, SCSI, SAS (7200 RPM or faster).
         6. Hard Disk Space: Minimum 10 GB free (depends on number of servers, cameras, rules, and logging settings).
         7. Operating System: Microsoft Windows Server 2008 R2 (64 bit), Microsoft Windows Server 2008 (32 or 64 bit), Microsoft Windows Server 2003 (32 or 64 bit).
         8. Software: Microsoft .NET 4.0 and Internet Information Services (IIS) 5.1 or newer.
      7. Computer Running Service Channel:
         1. CPU: Intel Xeon, minimum 2.0 GHz (Dual Core recommended).
         2. RAM: Minimum 1 GB (2 GB or more recommended).
         3. Network: Ethernet (1 Gbit recommended).
         4. Graphics Adapter: Onboard GFX, AGP or PCI-Express, minimum 1024×768, 16 bit colors.
         5. Hard Disk Type: E-IDE, PATA, SATA, SCSI, SAS (7200 RPM or faster).
         6. Hard Disk Space: Minimum 10 GB free (depends on number of servers, cameras, rules, and logging settings).
         7. Operating System: Microsoft Windows Server 2008 R2 (64 bit).
         8. Software: Microsoft .NET 4.0 Framework, and Internet Information Services (IIS) 5.1 or newer.
      8. Computer Running Smart Client:
         1. CPU: Intel Core2 Duo, minimum 2.0 GHz (Quad Core recommended for larger views).
         2. RAM: Minimum 512 MB (1 GB recommended for larger views, 1 GB recommended on Microsoft Windows Vista).
         3. Network: Ethernet (100 Mbit or higher recommended).
         4. Graphics Adapter: AGP or PCI-Express, minimum 1280×1024, 16 bit colors.
         5. Hard Disk Space: Minimum 500 MB free.
         6. Operating System: Microsoft Windows 7 Professional (32 bit or 64 bit), Microsoft Windows 7 Enterprise (32 bit or 64 bit), Microsoft Windows 7 Ultimate (32 bit or 64 bit), Microsoft Windows Server 2008 R2 (64 bit), Microsoft Windows Vista Ultimate (32 bit or 64 bit), Microsoft Windows Vista Enterprise (32 bit or 64 bit), Microsoft Windows Vista Business (32 bit or 64 bit), Microsoft Windows Server 2008, Microsoft Windows Server 2003 (32 bit or 64 bit), Microsoft Windows XP Professional (32 bit or 64 bit). Note that Smart Client always runs as a 32-bit Windows service/application.
         7. Software: Microsoft .NET 4.0 Framework, DirectX 9.0 or newer, and Windows Help (WinHlp32.exe).
      9. Computer Accessing Remote Client:
         1. CPU: Intel Pentium 4, minimum 2.4 GHz
         2. RAM: Minimum 256 MB (512 MB recommended for larger views, 1 GB recommended on Microsoft Windows Vista).
         3. Network: Ethernet (100 Mbit or higher recommended).
         4. Graphics Adapter: AGP or PCI-Express, minimum 1024 x 768 (1280x1024 recommended), 16 bit colors.
         5. Hard Disk Space: Minimum 10 MB free.
         6. Operating System: Microsoft Windows 7 Professional (32 bit or 64 bit), Microsoft Windows 7 Enterprise (32 bit or 64 bit), Microsoft Windows 7 Ultimate (32 bit or 64 bit), Windows Vista Ultimate (32 bit or 64 bit), Windows Vista Enterprise (32 bit or 64 bit), Windows Vista Business (32 bit or 64 bit), Microsoft Windows Server 2008 R2 (64 bit), Microsoft Windows Server 2008, Windows Server 2003 (32 bit or 64 bit), Microsoft Windows XP Professional (32 bit or 64 bit). Note that Remote Client always runs as a 32‑bit Windows service/application.
         7. ​​​​​​​Software: DirectX 9.0 or newer, and Windows Help (WinHlp32.exe).

1. Examination 

   3.01.    EXAMINATION

   1. Verification Of Conditions:
      1. The Contractor shall visit the site and verify that site conditions are in agreement with the design package.  The Contractor shall report all changes to the site or conditions which will affect performance of the system to the Owner.  The Contractor shall not take any corrective action without written permission from the Owner.
      2. General:
         1. Verify that existing site conditions are acceptable for product installation in accordance with manufacturer’s instructions.
         2. Verify that wire runs, related items, and conditions are ready to receive work of this Section.
      3. Cable & Wiring:
         1. Examine pathway elements intended for cables.  Check raceways, cable trays, and other elements for compliance with space allocations, installation tolerances, hazards to cable installation, and other conditions affecting installation.
         2. Examine roughing-in for LAN and control cable conduit systems to PCs and other cable-connected devices to verify actual locations of conduit and back boxes before device installation.
      4. LAN/WAN
         1. Verify LAN connections for server and workstation computers.
         2. Provide access to the internet for the primary VMS server.
      5. Power Connections
      6. Verify power circuits which are existing or have been previously installed under other sections are acceptable for product installation in accordance with manufacturer’s instructions.

2. Preparation 

   3.02.    PREPARATION

   1. Review configurable features of the VMS with the Owner’s Representative and document the results of the meeting in the Project planning documents.  The following configuration topics shall be resolved prior to configuring equipment and services:
      1. Internet Service Provider, firewall, and IP schema for VMS devices.
      2. Time server synchronization scheme for overall security system.
      3. Plan for system testing, startup, and demonstration.
      4. Acceptance test concept and, on approval, develop specifics of the test.
      5. List of default user IDs and passwords (factory defaults) for VMS application, servers and workstations.
   2. Provide a schedule with a list of participants to attend monthly coordination and progress update meeting until job completion.  Attendees shall include:
      1. Owner’s Representative of Facilities Management, Information Services, Security Management.
      2. Contractor Project Manager.
      3. Manufacturer(s) Employed Representative.
      4. Architect / Engineer / Security Consultant.
   3. At all coordination meetings with Owner’s Representative, present Project planning documents and review, adjust, and prepare final setup documents.  Use final documents to set up system software.
   4. The Owner’s Representative and Owner shall assist in establishing procedural guidelines and in defining terminology and conditions unique to the Owner’s operation.
   5. Supervise installation to appraise ongoing progress of other trades and contracts, make allowances for all ongoing work, and coordinate the requirements of the installation of the Physical Access Control System.
   6. Coordinate Owner installation or update of workstation operating system software and web browser software to a version as specified by the VMS provider. 
   7. Coordinate Owner-managed computer and network security practices as specified by the VMS provider.

3. Installation 

   3.03.    INSTALLATION

   1. VMS system shall be deployed in accordance with the manufacturer’s deployment instructions, including workstation, kiosk, and integration instructions and requirements.
   2. Supervise installation to appraise ongoing progress of other trades and contracts, make allowances for all ongoing work, and coordinate the requirements of the VMS installation.
   3. Drawings and Diagrams
      1. System devices identified on building drawings are intended to generally indicate areas where such devices are to be located. Determine final location of these devices in accordance with Owner’s requirements.
      2. Riser diagrams are schematic and do not show every conduit, wire box, fitting, or other accessories. Provide such materials as necessary for a complete and functioning installation.
   4. Comply with manufacturer’s written data, including product technical bulletins, product catalog installation instructions and product carton installation instructions.
   5. Install, configure, and test VMS for complete and proper operation.

4. Site Quality Control 

   3.04.    SITE QUALITY CONTROL

   1. Site Tests and Inspections:
      1. Submit documented test plan to Owner at least (14) days in advance of final acceptance test, inspection and check-off.
      2. Perform final acceptance testing in the presence of Owner’s representative, executing a point by point inspection against a documented test plan that demonstrates compliance with system requirements as designed and specified.
      3. Conduct acceptance tests in presence of Owner’s representative, verifying that each device point and sequence is operating correctly and properly reporting back to control panel and control center, and provide the Owner’s Representative with a written report on the results of that test.
      4. Consider VMS accepted only after all acceptance test items have been successfully checked-off.  
         1. Beneficial use of part or all of the system shall not be considered as acceptance.
      5. As required to sufficiently demonstrate the VMS functionality, request the console operator on duty and his/her superior to perform certain daily operations using the VMS.
      6. Complete all required training prior to initiation of the final acceptance test.
      7. Following the VMS head-end equipment review, inspect the installation of all field computers and devices. 
         1. Point out the general neatness and quality of installation, test the full functionality of each individual device, and show that mounting, backbox and conduit meet compliance requirements.
      8. Owner’s Representative shall, upon successful completion of the final acceptance test (or subsequent punch list retest), issue a letter of final acceptance.
      9. Owner’s Representative retains the right to suspend and/or terminate testing at any time when the system fails to perform as specified. 
         1. Collaborate with Owner’s Representative prior to start of testing, to establish criteria pass/fail criteria and classification of test execution problems, such as:
            1. Pass/fail: criteria determining what constitutes a test pass or failure.
            2. Suspension and resumption: criteria determining when testing must be suspended and resulted later.
            3. Show Stopper: Stop test, fix problem and restart test from beginning.
            4. Major Problem: Fix problem before test can be resumed or concluded.
            5. Minor Problem: Add problem to “punch list”, complete test.
            6. Special Issue: Investigate to determine which problem category above category applies.
         2. If it becomes necessary to suspend the test, work diligently to complete/repair all outstanding items to the condition specified in the Specification and as indicated on the security drawings. 
         3. Supply the Owner’s Representative with a detailed completion schedule outlining phase by phase completion dates and a tentative date for a subsequent punch list retest. 
         4. During the final acceptance test, make no adjustments, repairs or modifications to the system without the permission of the Owner’s Representative.

5. Adjusting 

   3.05.    ADJUSTING

   1. Perform field software changes after the initial programming session to “fine tune” operating parameters and sequence of operations based on any revisions to the Owner’s operating requirements.
   2. Security Hardening Procedures:
      1. Installer/Factory User Accounts:
         1. Remove all (default, installer, or temporary) user accounts and passwords used during installation that are not part of the End-user’s final operational requirements.
      2. User accounts that match factory defaults user accounts shall have new passwords assigned that are substantially different from factory default passwords.
      3. Apply appropriate measures from manufacturer’s system hardening guide.

6. Closeout Activities 

   3.06.    CLOSEOUT ACTIVITIES

   1. Training:
      1. General:
         1. Submit training plans and instructor qualifications to Owner’s Representative for approval.
         2. Coordinate with Owner’s Representative to accommodate owner shift schedules to reduce impact to regular operations.
      2. Administration and Visitor Processing:
         1. Determine training requirements for Owner's personnel and collaborate to schedule training.
         2. Provide training as scheduled. 
         3. Deliver printed or electronic reference materials which cover the entire training presentation. 

7. Protection 

   3.07.    PROTECTION

   1. Maintain strict security during the installation of equipment and software.  Rooms housing accessible equipment and workstations that have been powered up shall be locked and secured during periods when a qualified operator in the employ of Contractor is not present.
   2. Protect installed work of other trades when working in the same location.
   3. Protecting all completed work prior to acceptance by owner, unless Owner has specifically relieved Contractor from this burden. 
   4. Incremental and As-built Configuration Backup
      1. Perform a full back-up of all configuration settings and data from VMS at the completion of critical milestones, immediately prior to the strart of acceptance testing, and immediately after acceptance testing is completed.
      2. Deliver VMS instructions for the restoration of the back-up upon completion of acceptance testing.

8. Maintenance 

   3.08.    MAINTENANCE

   1. Software updates and upgrades to VMS application shall be delivered automatically without contractor/installer/Owner intervention.
      1. Maintenance updates shall be delivered by VMS manufacturer per agreed schedule.
      2. Software upgrades shall be delivered by VMS manufacturer per agreed schedule.

#