3.0 SECURITY CAMERA EQUIPMENT & SOFTWARE

3.1 OVERVIEW

The Security Equipment and Software is designed to be integrated into the District network with security services originating from a server at the Main Distribution Frame (MDF). From the MDF, cables shall extend to various Intermediate Distribution Frame (IDF) locations distributed throughout the campus. An extensive conduit system extends throughout most of the larger campuses and provides cable pathways to each of the buildings.

The purpose of this solution is to provide an IP Based Video Surveillance Solution for the Oakland Unified School District including but not limited to all Electrical requirements, Pathways, Cabling, Cameras and all other equipment necessary for a complete functional District wide video safety system

The system will offer remote observation capabilities locally as well as at Police Services and Facilities Project Manager using fixed position or omniview cameras to capture the exterior and interior of each campus. Cameras shall be locally recorded on network video recorders. These recorders shall be connected to the security LAN data network. This connection shall enable authorized personnel utilizing client computers to access these network recorders and monitor live or recorded video remotely via the GUI interface on the client computers. PTZ cameras cannot be used or installed.

3.2 GENERAL ABBREVIATIONS, ACRONYMS AND STANDARDS

Click to expand
  • JPEG: Joint Photographic Experts Group (image format)

  • LAN: Local Area Network

  • Lux: A standard unit of illumination measurement

  • MPEG: Moving Picture Experts Group

  • Multicast: Communication between a single sender and multiple receivers on a network

  • NTP: Network Time Protocol

  • NTSC: National Television System Committee – a color encoding system based on 60Hz

  • ONVIF: Global standard for the interface of IP-based physical security products

  • PoE: Power over Ethernet (IEEE 802.3af/at) standard for providing power over network cable

  • Progressive scan: An image scanning technology which scans the entire picture

  • SDK: Software Development KitACC: Video Codec “Active Content Compression

  • ADDS: Active Directory Domain Services

  • AGC: Automatic gain control

  • API: Application Programming Interface

  • Bit Rate: The number of bits/time unit sent over a network

  • Bonjour: Enables automatic discovery of computers, devices, and services on IP networks.

  • DHCP: Dynamic Host Configuration Protocol

  • DVR: Digital Video Recorder

  • DNS: Domain Name System

  • FPS: Frames per Second

  • FTP: File Transfer Protocol

  • GbE: Gigabit Ethernet (1000Mbps)

  • H.264/5 (Video Compression Format)

  • IEEE 802.1x: Authentication framework for network devices

  • IP: Internet Protocol

  • RAID: Redundant Array of Independent Disks

  • SMTP: Simple Mail Transfer Protocol

  • SNMP: Simple Network Management Protocol

  • SSL: Secure Sockets Layer

  • TCP: Transmission Control Protocol

  • TLS: Transport Layer Security

  • Unicast: Communication between a single sender and single receiver on a network

  • UPnP: Universal Plug and Play

  • VMS: Video Management System

3.3 BASIC CONTRACTOR RESPONSIBILITIES

The Contractor shall, at a minimum, possess the following attributes:

  • Shall be a licensed security Contractor with a minimum of five (5) years’ experience installing and servicing systems of similar scope and complexity.

  • All software and camera installations, configuration, setup, program and related work shall be performed by software/electronic technicians thoroughly trained by the manufacturer in the installation and service of the equipment provided.

  • Shall submit certifications from the manufacturer of the equipment from the last two years of the highest level of training provided.

  • Shall have 24/7/365 service technicians and be a stocking contractor of the manufacturers equipment. The Integrator shall be able to respond to a service call on site and have trained resources within 60 miles of the owner’s location.

  • The Integrator’s main resources within the project shall carry proper certification issued by the manufacturer and provide recent certifications to confirm sufficient product and technology knowledge.

  • The Integrator shall follow the installation instructions provided by the manufacturer to ensure the system is designed, calculated and installed per the manufacturer recommendations.

  • The database shall be reviewed by the Owner and approved before the Integrator enters it into the system.

  • All equipment shall be tested and configured in accordance with instructions provided by the manufacturer prior to testing and training of the owner.

  • All firmware in products shall be the latest and most up-to-date provided by the manufacturer, or of a version as specified by the provider of the Video Management System to ensure approved integration compatibility.

  • F. A proper installation shall meet NEC (National Electrical Code – US only) per the guidelines of that year’s revision and the local authority having jurisdiction. When properly installed equipment meets Low Voltage, Class 2 classification of the NEC.


3.4 SOFTWARE


Video Management System

Unless otherwise noted the VMS will be Xprotect Professional+ as manufactured by Milestone Systems and supplied by a Certified Factory representative. This will allow Police Services and Facilities Project Manager to be able to access and manage all of the video recorders remotely for each site as well as locally by authorized personnel. Only authorized personnel will have access to the software which includes the Facilities Project Manager, Maintenance Vendor, and Technology Services for the purposes of configuring the recorders using the VMS. The Video Management System shall be manufactured by a corporation utilizing quality best practices meeting the specified features.

The VMS shall utilize an (SDK) which enables seamless integration of video analytics algorithms and other third-party applications in XProtect Smart Client and Management Client. The integration option shall support Milestone ONVIF Bridge that enables full video interoperability in multivendor installations using a standardized ONVIF compliant video-out interface. Generic event integration shall enable easy and fast integration of third-party applications and systems via a simple message-based socket communication interface. The system configuration API shall enable external applications to make changes to the system’s configuration.


VMS Software Installation Locations

VMS software will be installed locally on a desktop computer in a location as determined by the site administrator. VMS software will not be installed on any portable computing device (e.g. laptop, tablet, smartphone). Local desktop installation shall be at the following locations;

High School

  1. Principal’s office

  2. Each Vice Principal’s office

  3. Lead Site Security Officer office

Middle School

  1. Principal’s office

  2. Each Vice Principal’s office

  3. Lead Site Security Officer office

Elementary School

  1. Principal’s office

  2. Vice Principal’s office

  3. Lead Site Security Officer office

Recorded camera footage is to be kept for a minimum of 30 days.


Video Management System Accessibility, Authorization, & Authentication

For the purposes of safety and due to the nature of the use of security surveillance systems, local accessibility to the video management software is to be limited to authorized personnel only. Police Services and Facilities Project Manager will provide a list of authorized site personnel that will be given access to the VMS.

Typical authorized personnel is as follows:

  1. Principal

  2. Vice Principal (may be more than one if located at a middle school or high school)

  3. Lead Site Security Officer

For any additional authorized personnel consult with the Police Services and Facilities Project Manager.

Authentication

  • System log-in shall use Microsoft Active Directory, local Windows or basic user account. Hereby, current windows logon shall be used for authentication.

  • Dual authorization shall offer an optional additional level of system security, where Management Client users are granted access to the system only when a second user or supervisor has confirmed the log-in with a successful authorization of the second user.

Management Server & Management Client

The Management Server & Client shall be configured as stated below:

  • The Management server shall enable user authentication logon, system configuration and logging.

  • The Management Client shall enable administration of the system such as recording servers, devices, security, rules and logging.

  • The Management Client shall be compatible with XProtect Professional+ 18 and newer.

  • All configuration and logs from the entire system shall be stored in a Microsoft SQL database and accessible by the management server only.

  • The Failover solution for the management server shall provide a resilient system solution based on Windows Server Clustering, ensuring high system availability.

  • The Management server manager shall be available in the local console notification area (icon tray) for status messages and to start/stop the service.

  • The management server shall run as a Windows service under local system account or optional local Windows user or Microsoft active directory account with run-as-a-service privileges.

  • The management client’s graphical user interface shall be available in a minimum of 12 languages including: American English, Chinese (Simplified), Chinese (Traditional), Danish, German, French, Italian, Japanese, Korean, Portuguese (Brazil), Russian and Spanish.

  • The management client’s built-in help shall be available in a minimum of 6 languages including: American English, Chinese (Simplified), French, Japanese, Korean and Portuguese (Brazil).

  • To register and validate your licenses, the system shall offer easy-to-use automatic or manual online activation via the Internet and alternatively, offline activation via email and web for closed surveillance networks.

  • XProtect Professional+ shall support both IPv4 and IPv6 addressing. XProtect Professional+ shall also be backwards compatible with XProtect 2018 and newer versions.

  • Logs of system, audit and rule entries shall consolidate from all recording servers and clients. Each log file shall have adjustable size and time limitations.

Milestone Interconnect Remote Site

  • The System concept shall interconnect all Milestone XProtect video management software (VMS), Milestone Arcus and Milestone Husky units to gain operation and cost-effective management of geographically dispersed surveillance sites.

  • Intelligent video storage management shall make optimal use of remote video storage and available network bandwidth with a choice to store video recordings remotely, or combined with flexible revival of the remotely stored video.

  • XProtect Professional+ includes the possibility that shall define time interval and bandwidth cap for upload of video from a remote interconnected site.

  • XProtect Professional+ shall enable the proactive detection of errors and cost-efficient management of connected sites by propagation of system status events and embedded remote management of connected system.

  • XProtect Professional+ has the ability that shall detect system problems and remotely manage interconnected sites reducing operational costs and the need for on-site visits.

Storage

  • Allows the definition of one or more storage containers with individual archiving schemes and retention times. The recording capacity shall be limited only by disk space. All recordings are to be kept for a minimum of 30 days.

  • Each storage container shall be defined as a live database and one or more optional archives, where the video data is moved from the live database to secondary disk systems or network drives. The archived data shall be still online and available for clients.

  • Archiving schemes shall define when video is archived to the next archiving stage in the storage container and how long the video data is retained before deletion.

  • The storage functionality shall enable the ability to allocate individual devices to different storage containers.

  • XProtect Professional+ shall allow to move a device or a group of devices between two storage containers.

  • Storage overview shall give instant indication of used vs. available storage in total and for individual cameras.

  • The VMS shall manage maximum recording time for manual recordings.

Devices

  • The Hardware wizard shall add devices; automatically using Universal Plug and Play (UPnP) discovery, via IP network range scanning, or using manual device detection. All methods support automatic or manual model detection.

  • The Wizard shall enable swift replacement of malfunctioning devices with preserved configuration settings and recordings.

  • The Wizard shall enable easy moving of hardware devices (with attached cameras, microphones, speakers, inputs, outputs and metadata devices) between recording servers in runtime without losing settings, recordings, rules, permissions etc. It shall enable and disable devices if they are not used or are down for maintenance.

  • It shall allow to adjust settings such as brightness, color level, compression, maximum bit rate, resolution and rotation per camera or camera group; select and configure video format, frames per second (FPS), resolution and quality for the video streams used per camera; select and configure one, or more, video streams per camera to be used for live viewing. Each stream can be in different video format, FPS, resolution and quality.

  • XProtect Professional+ shall enable adjustable group of pictures (GOP) length for MPEG4 H.264 and H.265 encoded video. It also shall enable assigning camera shortcut number for easy operation by clients and shall provide optional preview window for immediate verification of video settings per camera or for a group of cameras.

  • The VMS shall allow to run multiple patrolling schedules per camera per day, for example, run different schedules for day/night/weekend.

  • Privacy mask shall consistently hide certain areas in the camera view in live and playback video and in exported material.

  • It shall allow to configure device events like motion detection with pre- and post-buffers, or input signal behavior options and allow to fine-tune motion detection sensitivity per camera manually or automatically.

  • The VMS shall allow to apply one or multiple exclusion zones for where motion detection is to be disabled to avoid unwanted detection.

Rules, time profiles and notifications

  • The Powerful Microsoft Outlook®-style rule system shall support an unlimited number of rules.

  • Time profiles with recurring time selection and expire condition shall support an unlimited number of time profiles.

  • Start actions: The triggering events may initiate a wide set of actions in the VMS system,

  • The VMS shall enable multi-recipient customizable email notification with image and/or AVI attachment of incidents.

User Rights Management

  • User rights management shall enable common management of all user rights across all user and programmatic (MIP SDK) interfaces.

  • Overall system security definition shall make it possible to globally allow or deny permission to devices and functions (such as manage, read, edit and delete).

  • Device-specific security definition shall make it possible to allow or deny permission to individual devices and functions (such as manage, read, edit and delete).

  • User rights management shall control roles, user and administrator access to:

  1. Inputs and outputs: visibility, administrate, status, activation

  2. manual control, activate fixed position or omniview camera priority, manage fixed position or omniview camera and patrolling, reserve and release fixed position or omniview camera session

  3. Remote recordings: retrieve remote recordings

  4. External events: visibility, administrate.

  5. Alarms: visibility of alarms and ability to manage alarms

  6. MIP: Plug-in permissions

  7. Application: manager, XProtect Smart Client/XProtect Web Client/Milestone Mobile, live/ playback/setup, status API and service registration API

Management Client Profiles

  • Management Client profiles shall enable the ability to tailor the availability of main/sub functions in the Management Client for different user roles.

X-Protect Smart Client Profiles

  • Smart Client profiles shall enable the ability to enforce or recommend optional XProtect Smart Client application options for a user or group of users, using up to 3 XProtect Smart Client profiles.

  • Profiles shall enable defining general XProtect Smart Client application options, including (listing not exhaustive): visibility of time, visibility of camera live indicators, default image quality, default frame rate, keyboard and joystick setup, startup mode and deinterlacing filters.

  • XProtect Smart Client profiles also shall:

  1. provide access to live mode and the availability of individual control panes and overlay buttons

  2. Shall provide access to playback mode and the availability of individual control panes, overlay buttons and settings for specific functions, such as default export path

  3. provide access to setup mode and the availability of individual control panes and setup functions

  4. provide access to Sequence Explorer, Alarm Manager, System Monitor

  5. provide access to setup mode and the availability of individual control panes and setup functions

  6. define available view layouts

System Administration

  • System administration shall include built-in backup and restore support for manual system backup of all configuration data, including (listing not exhaustive): system configuration data, maps alarm settings and definitions and client views.

  • System administration shall enable historic performance and usage investigation and reports of; storage usage, network use, server and camera performance.

  • Configuration Reporting shall enable complete or partial documentation of system configuration. Custom and site-specific free-text information, integrator’s notes and logo can be added to the printer-friendly reports.

License Administration

  • License overview shall include add-on products, Milestone Care coverage and renewal date. The License owner information shall synchronize with the software registration page on the Milestone website.

  • License administration shall provide expanded license information for multi-site installations where both the total used licenses for the common SLC is presented and the license use in the specific system. It shall provide license overview that presents the license use of all the individual sites running on the same SLC.

  • The “Changes without activation” function shall allow additions and replacements of limited number of devices without requiring license activation.

Event Server

  • The alarm manager shall manage single-point alarm management of all internal system alarms and external security alarms. It shall provide alarm descriptions and work instructions to make alarms actionable for operators.

  • An alarm location map shall be linked to each alarm providing instant situational awareness to the operator dealing with the alarm.

  • Customizable alarm priorities shall allow operators to focus on the most critical alarms and shall enable logical grouping of alarms dependent on their type and nature.

  • Customizable alarm statuses shall enable alignment of the alarm handling workflow with existing workflows and security systems.

  • The alarm handling result code shall enable tracking of the outcome of the alarms.

  • The alarm manager shall enable automatic allocation to alarm owners with escalation and alarm forwarding possibilities.

  • The alarm manager shall enable time profiles for definition of active alarms. It shall provide the possibility to associate one or more cameras to an alarm (maximum 15 cameras can be displayed simultaneously in the alarm preview window).

  • A set of alarm handling reports shall give valuable information about alarm inflow and alarm handling performance.

  • The alarm manager shall enable extensive logging of alarms.

  • Microsoft Clustering shall support the event server enables secure and redundant alarm handling.

Milestone Mobile Server

  • The Milestone Mobile server shall run as a dedicated service, allowing it to be installed either on the same server as other system components or on dedicated hardware in more demanding installations.

  • The Milestone Mobile server shall transcode video so streams are robust and can adapt to changing connection bandwidth. The server also optimizes the use of available bandwidth to get the best possible stream quality.

  • Adjustable transcoding logic shall enable capping of video resolution and frame rate for video streams provided to XProtect Web Clients and Milestone Mobile clients.

  • The server shall provide an option to bypass the transcoding logic and send direct streams to XProtect Web Clients.

  • Installing the Milestone Mobile server plugin in the Management Client shall give access to Milestone Mobile server management in order to change settings, read out miscellaneous status information, configure codecs used for exports as well as manage ongoing and completed exports.

  • Milestone Mobile servers shall be installed in parallel, offering redundancy and/or allowing more simultaneous users.

  • Milestone Mobile servers shall be configured through the tray controller to easily adjust or update settings Shall provide option to either a default-generated certificate for HTTPS encrypting the connection to the Milestone Mobile server or provide your own custom certificate.

  • Video Push configuration shall be done from the server, so users can download and use Milestone Mobile without having to do any configuration.

  • Milestone Mobile server shall support creating server-side export through XProtect Web Client and Milestone Mobile.

  • XProtect Web Client, including optional browser plug-ins, shall be included with the Milestone Mobile server. No additional setup is needed

  • Smart Connect shall enable easy configuration of internet access to the Mobile Server by automatic configuration of firewalls and internet routers via UPnP. Smart Connect shall also verify the configuration and operation of the internet connection, and can be used to email connection details to Mobile Client users.

XProtect Smart Client

General

  1. XProtect Smart Client shall provide dedicated task-oriented tabs for the Sequence Explorer, Alarm Manager and System Monitor, in addition to the traditional Live and Playback tabs.

  2. The client shall provide application theme support with choice of dark or light themes.

  3. XProtect Smart Client shall provide true multi-window support where secondary windows have full functionality and can be operated in independent mode or synchronized mode where they follow the control of the main window.

  4. It shall enable shortcuts to select a specific window or specific camera in a window.

  5. The client shall provide a camera search function that promptly finds cameras, types of cameras and views in the system with the ability to create temporary views to display all or a subset of cameras matching the search criteria.

  6. XProtect Smart Client shall display metadata bounding boxes from supported devices in live views and playback.

Customization

  1. The application options shall enable customization of the general behavior and look of the XProtect Smart Client. The customization shall be able to either be made as individual personalization managed by each operator.

  2. The application shall offer a simplified user interface with the possibility to toggle between “Simple” and “Advanced” modes, where Advanced mode is default.

  3. The XProtect Smart Client shall enable control of general look & feel and navigation properties, such as color mode, camera title bar, grid sizes etc.

  4. The client shall provide the availability of control panes and functions in live and playback tabs, and in setup mode, as well as the behavior and availability of the Professional+ function.

  5. The application shall allow to include information in timeline in the playback tab, setup keyboard shortcuts and joystick controls, as well as specific behavior of alarms and access control notifications.

Live View

  1. XProtect Smart Client shall enable to view live video from 1-100 cameras per computer monitor/view. Multiple computer monitor support shall provide a main window and any number of either floating windows or full screen views.

  2. Live view digital zoom shall allow a full view of recordings while the operator can digitally zoom in to see details.

  3. Live view shall support multiple view layouts optimized for 4:3 and 16:9 display settings in both landscape and portrait.

  4. Independent playback capability shall allow for instant playback of recorded video for one or more cameras, while in live mode.

  5. Live view provides the possibility to instantly re-arrange cameras in views for optimized monitoring of incidents, with single click restore of original view.

  6. It shall provide seamless access to cameras in remote interconnected systems.

  7. Live view shall enable instant camera placement in live view allows for instant replacement of cameras in a view, where new cameras can be placed in a particular view and positioned through a simple drag-and drop operation.

  8. Live view shall update on “motion only” optimizes CPU use by allowing motion detection to control whether or not the image should be decoded and displayed.

  9. Global hotspot function shall allow users to work in detail with any camera selected from any view. Local hotspot function shall allow users to work in detail with a camera selected from the same view.

  10. Carousel function shall allow a specific view item to rotate between pre-defined cameras that are not necessarily present in the view at the same time. Operators shall select default or custom display times for each camera, and they are able to manually switch to the next or previous camera in the carousel list.

  11. Matrix function shall show live video from multiple cameras in any view layout with customizable rotation paths, remotely controlled by computers sending matrix remote commands.

  12. Live view shall import static or active HTML maps for fast navigation to cameras and to provide a good overview of premises.

  13. It shall hide the HTML page toolbar in HTML page views.

  14. Live view shall activate matrix via graphical maps of premises using JavaScript or integrate with centralized access control systems.

  15. It shall allow the operator can assign outputs and views as actions to joystick buttons and as keyboard shortcuts.

  16. Two-way audio support shall enable XProtect Smart Client to record and play live audio from camera- connected microphones and outgoing audio from the operator’s microphone to one or multiple camera speakers.

  17. Live view shall enable adaptive deinterlacing option secures high video quality, based on the actual video content received. XProtect Smart Client shall optionally apply a filter to areas of the image where jagged edges would otherwise show up.

  18. Operators shall start/stop manual recording on individual cameras, where the recording status is propagated to all XProtect Smart Client users active in the system.

I/O and Events

  1. Overlay buttons shall provide intuitive control of cameras, camera-integrated devices and other integrated systems directly from the camera view.

  2. I/O and events shall enable to manually trigger output port relay operation, for example when controlling gates.

  3. I/O and events shall enable to manually trigger events by activating a server-defined event from a list.

Bookmarking

  1. Bookmarking shall enable users to manually add bookmarks with the bookmark function.

  2. Bookmarks shall be shown in timeline with instant preview.

  3. The function shall enable users to listen and preview bookmarks in recording search.

  4. Bookmark reports shall enable effortless incident documentation.

  5. Direct video export of a bookmark shall reduce the time needed to prepare forensic video material.

Playback

  1. Playback shall provide playback video from 1-100 cameras per computer monitor/view.

  2. Advanced video navigation shall include fast/slow playback, jump to date/time, single step and video motion search.

  3. Playback shall include integrated video timeline with time navigation and playback controls, including an integrated function to select a time interval for export, video retrieval from Edge Storage devices and remote interconnected systems.

  4. Playback shall allow to toggle between simple and advanced timeline mode.

  5. Playback shall allow to toggle between simple and advanced timeline mode.

  6. Independent playback capability shall allow the independent playback of recorded video from one or more cameras.

  7. Instant camera placement in playback view shall allow users to instantly replace cameras in a view, where a new camera can be placed in a particular view and position with a simple drag-and drop operation.

  8. Digital zoom shall allow the operator to see magnified details in the recorded video.

Export & Print

  1. The snapshot function shall enable operators to produce instant visual documentation of a camera by saving the camera image to a file, or sending it directly to a printer.

  2. The storyboarding function shall make it possible to include video sequences from different or overlapping time intervals from different cameras in the one and the same export.

  3. The export and print function shall provide export in XProtect format; including the standalone XProtect Smart Client - Player application for instant and easy viewing by authorities.

  4. The function shall allow export preview with looped playback.

  5. Export and print shall enable encryption and password protection of exported video material with a choice of following strong encryption algorithms: 56-bit DES 128, 192 and 256-bit AES.

  6. Export and print shall allow to create evidence material in media player format (AVI files), MKV format, or still image format (JPEG images).

  7. The function shall allow to disable the re-export option to prevent undesirable distribution of sensitive evidence material.

  8. Export and print shall allow bulk camera export in multiple formats to multiple destinations, including direct export to optical media, results in more efficient video exports and more secure handling of evidence material.

  9. Export comment function shall enable users to add general and/or camera-specific comments to a video export when exporting to XProtect format.

  10. In media player format comments shall be added as pre/post slides.

  11. The VMS shall allow to print incident reports including image, surveillance details and free-text user comments.

Sequence Explorer

  1. The smart client shall include a dedicated tab for the Sequence Explorer.

  2. The search options shall be: Manual Search.

  3. The sequence explorer shall include smooth navigation with sliding preview and “drag-and-throw” function for video thumbnails.

  4. The VMS shall include preview of selected sequence with auto play and direct export support.

Map Function

  1. Built-in map function in XProtect Smart Client shall provide an intuitive overview of the system and offers integrated access to all system components.

  2. Map images shall be in standard graphic file formats including JPG, GIF, PNG and TIF.

  3. Map function shall include any number of layered maps such as city, street, building and room.

  4. The function shall enable instant camera preview on “mouse over” and one-click shows all cameras on map.

  5. The function shall allow depiction of camera view zones on map with clickable fixed position or omniview camera zones for instant fixed position or omniview camera control.

  6. Map function shall allow easy drag-and-drop and point-and-click definition of: cameras, servers, microphones, speakers, I/O devices, hot-zones for map hierarchies, camera view zones.

  7. The function shall provide integrated control of speakers, microphones, and events and output I/O control, including: doors, gates, light and access control systems.

  8. Map function shall also:

  • provide real-time status monitoring indication from all system components including cameras, I/O devices and system servers

  • provide graphical visualization of the system status through color coding

  • provide hierarchical propagation of status indications to higher ordered maps

  • make different levels of status indications available (alarm, warning and errors)

  • provide system performance data for cameras and servers including camera resolution, FPS, network use and disk space

  • be able to suppress status indications (such as error and warning) for a given device

  • provide the possibility to edit device names in a map and assign map-specific names and references to devices in a map

  • Map editing subject to user rights

Camera Navigator

  1. The camera navigator shall provide consistent and comprehensive visual verification, ensuring easier tracking of moving objects in geographically complex environments.

  2. The navigator shall automatically display thumbnail views of nearby cameras.

  3. The camera navigator shall provide add-on to the map application with no special configuration needed.

Alarm Manager

  1. The Smart Client shall provide a dedicated dockable tab for the Alarm Manager.

  2. The alarm manager shall include an alarm list with extensive filtering capabilities and an alarm preview in both live and playback mode.

  3. The alarm manager shall enable extensive alarm sort and filtering functions allow operators to focus on most critical alarms.

  4. Instant preview of primary and related cameras shall reduce the number of false alarms.

  5. Tight integration with the map function shall allow operators to indicate and acknowledge active alarms in the map.

  6. Alarm descriptions and work instructions shall make alarms actionable for operators.

  7. Alarm escalation and alarm forwarding possibilities shall allow operators with appropriate skills to handle different alarms.

  8. Alarm reports shall enable incident documentation.

  9. Alarm location map shall present the alarm operator with a map showing the alarm area when an alarm is selected.

  10. The alarm manager shall provide alarm notification to a single or a group of Milestone Mobile client users using Push Notifications.

  11. The manager shall provide optional sound notifications for different alarm priorities for notification of new incoming alarms.

  12. Alarm disabling option shall enable users to suppress alarms from a given device in a certain time period.

  13. The alarm manager shall enable instant access to both live and recorded video from the cameras that are related to the alarm.

  14. Alarm handling reports shall give valuable information about alarm inflow and alarm handling performance.

  15. The manager shall provide a common alarm list for all interconnected sites.

System Monitor

  1. The system monitor shall provide a dedicated dockable tab with system performance and use information.

  2. The system monitor shall provide historic performance and usage investigation and reports of; storage usage, network use, server and camera performance.

Set-up & Management

  1. Download and install XProtect Smart Client from a web page on the management server. It shall enable notification about new updates at log-in.

  2. Application options shall allow users to adapt the layout and personalize the application to their particular preferences.

Authentication

  1. System log-in shall use Microsoft Active Directory, local Windows or a basic user account. Furthermore, it shall use current Windows log-on for authentication, and use Auto-log-in and auto-restore views.

  2. Dual authorization shall offer an optional additional level of system security, where XProtect Smart Client users are granted access to the system only when a second user or supervisor has confirmed the log-in with a successful authorization of the second user.

System

  1. The system shall support IPv4 and IPv6 addressing.

  2. The 64-bit Windows® operating system support shall enable better performance when viewing and operating many cameras.

  3. It shall support hardware accelerated decoding using Intel Quick Sync video.

XProtect Smart Client Player

  1. XProtect Smart Client - Player shall be able to play back recorded or archived video and audio evidence, including edited storyboard exports.

  2. The player shall include the same user-friendly interface and most functions as XProtect Smart Client.

  3. The player shall offer a simplified user interface with the possibility option to toggle between “Simple” and “Advanced” modes.

  4. It shall provide instant one-click playback for easy viewing of exported video evidence.

  5. Advanced second-level investigation tools shall make it easy to refine exported video and re-export the most essential evidence.

  6. Metadata bounding boxes included in exports shall be displayed time synchronized in XProtect Smart Client – Player.

  7. The project tool shall allow users to merge video exports or archives from two different locations or XProtect systems together into one new export.

  8. Xprotect Smart Client Player shall also:

    • provide view up to 100 cameras time-synced during playback

    • provide camera search function promptly finds cameras, types of cameras and camera views in the system

    • provide scrollable activity timeline with magnifying feature

    • provide instant search on recordings based on date/time and activity/alarm (video motion detection)

    • Shall allow to view, modify or add general and/or camera-specific comments for a given video export

    • Shall allow de-interlacing of video from analog cameras

    • Shall support 360° ImmerVision Enables® panomorph lens technology

  9. Evidence shall be generated as a printed report, a JPEG image, an AVI or MKV film or in XProtect format Shall include export audio recordings in WAV, MKV or AVI format.

  10. Exported video shall be digitally zoomed to view an area of interest and minimize export footprint size.

  11. The player shall enable re-export evidence containing XProtect format and XProtect Smart Client - Player for instant, easy viewing by authorities.

  12. The player shall provide encryption and password protection of exported video material with a choice of the following strong encryption algorithms: 56-bit DES 128, 192 and 256-bit AES.

XProtect Web Client

  1. XProtect views shall be accessed through the browser and avoid advanced setup.

  2. Camera search function shall promptly find cameras, types of cameras and camera views in the system.

  3. The client shall include:

  • Easy multi camera video playback including fast/slow playback, single frame step and jump to date/time with frame preview while adjusting time.

  • Investigation function with ability to save exports for later usage or download

  • ption for client-side video decoding via browser plug-ins

  • Control fixed position or omniview camera cameras remotely, including preset positions

  • Dynamic bandwidth optimization when streaming from server to client gives better use of bandwidth

  • Create AVI files or save JPEG images

  • Preview exports on the server without downloading them

  • System log-in using XProtect user name and password

  • System log-in using Microsoft Active Directory user

  • Secure connection through HTTPS

  1. The XProtect Web Client shall allow export on the server to avoid moving large video files back and forth. The client shall allow to only download needed files or save them for downloading when on a faster connection.

  2. There shall be no installation needed on the client computer.

Milestone Mobile

  • Milestone mobile shall support any mobile device running Android® 2.2, iOS5, and Windows® Phone 8, or newer versions.

  • Add log-in credentials for multiple servers in Milestone Mobile shall allow to easily switch between sites or different connection addresses.

  • Views shall be inherited from the connected XProtect VMS system. The client shall automatically obtain the user’s private and shared views from the system to be used as camera lists in Milestone Mobile.

  • A view with all cameras shall be automatically generated, allowing Milestone Mobile to be used when no views are set up. It shall also provide a quick way of searching through cameras.

  • Camera search function shall promptly find cameras, types of cameras and camera views in the system.

  • Cameras shall be viewed in full screen to take better advantage of the device’s screen. It is also possible to search through cameras in a view while in fullscreen by swiping left or right.

  • Digital pinch-to-zoom shall enable users to zoom in on a part of the image for closer review and conduct detailed investigation of video when using megapixel or high-definition cameras.

  • Milestone Mobile shall allow to play back recordings from the database and select a specific time or recorded sequence to start playback, step through recordings and select a playback speed.

  • Milestone Mobile shall allow to view recordings from the database while keeping an eye on what is currently happening. The client shall display a live picture-in-picture frame of the same camera when in playback mode. The picture-in-picture shall be moved by dragging and double-tapping and will return to live view.

  • Control over the fixed position or omniview camera cameras shall be given with Milestone Mobile either manually or by selecting predefined presets for quick navigation.

  • Video Push shall allow users to use their mobile devices’ cameras as cameras in the XProtect VMS. It is easy to use and requires no setup in the mobile device.

  • Milestone Mobile shall include the option to include location metadata in Video Push.

Licensing Structure

Server Base License

  1. An XProtect Professional+ server base license is mandatory for installing the product.

  2. The base server license permits the following deployments within the legal entity purchasing the base server license:

  • Unlimited number of Management Servers

  • Unlimited number of Recording Servers

  • Unlimited number of XProtect Smart Clients, XProtect Web Clients and Milestone Mobile applications

Hardware Device License

  1. To connect cameras, audio devices, video encoders and other devices to XProtect Professional+, one license per physical hardware devices required.

  2. In total, for all copies of the product installed under this license, the product may only be used with hardware devices as you have purchased hardware device licenses for.

  3. An unlimited number of hardware device licenses can be purchased. To extend an installation with additional hardware device licenses, the base server license number (SLC) is required when ordering.

Licensing of Milestone remote Interconnect

  1. One Milestone Interconnect device license is required per device (camera) in an interconnected site that is enabled in the XProtect Professional+ system.

3.5 SECURITY CAMERA DESIGN & INTENT

Camera Locations

Site walk is to be conducted prior to installation to determine mounting height and exact location of cameras. Prior to installation, Camera locations are to be approved by Police Services, District Facilities Project Manager and Site Administrator. Location of the camera is determined by line of sight and what the camera is trying to capture. Locations are to eliminate “dead spots” within the site both interior and exterior and playfields. Playfields may require wireless cameras and equipment. Camera placement for elementary schools will be exterior only whereas for high schools and middle schools cameras will be placed in both interior and exterior spaces. Cameras are not to be placed in restrooms, locker rooms, showers, drama dressing rooms, etc or any other locations where a person’s body will be exposed on camera. Cameras are to be tied to Milestone and/or AiPhone IP addressable intercom systems.


Camera height

Camera heights vary per site. Camera height should be determined by building height, roof line, and whether it is interior or exterior location.

  • Minimum height for an exterior location is 12’-0”

  • Minimum height for an interior location is 8’-0” (dependent upon ceiling height within the space)

  • Cameras are not to be installed on swing arm mounting poles.


Analog to Digital Migration

For sites where analog cameras are present, they are required to be tied into the digital server. An encoder is to be provided by the contractor for the translation from an analog signal to a digital signal. Due to the power requirements of the encoder and per the requirements stated in the Technology Services Data & Communications Specifications under Distribution Frame Room, Electrical for MDF a 30 amp outlet needs to be provided.


Analog to Digital Encoder

IKVISION DS-6716HQHIS-SATA with the following key features:

  1. Connects to HD-TVI and Analog Cameras

  2. Connects to Turbo/HD Camera/Dome with long with long transmission distance

  3. Redundant recording and holiday recording

  4. Manual video quality diagnostics

  5. VCA detection alarm (line crossing detection and intrusion detection)

  6. Locks and unlocks video files

  7. HDD quota and group management; different capacities can be assigned to different cameras under quota mode

  8. 2 SATA interfaces

  9. 1 self adaptive 10m/100m/1000m network interface

  10. HIKVISION DDNS (Dynamic Domain Name System)

  11. NETWORK DETECTION


3.6 SECURITY CAMERAS & LOCAL SECURITY CAMERA RECORDING SERVER


All camera cabling shall be routed to the nearest IDF. Consult with Technology Services as to the route and the nearest IDF location prior to installation.


Security Cameras

Hanwha Wisenet QNV-8080R

  • 5 Megapixel resolution

  • 3.2~10mm (3.1x) motorized varifocal lens

  • 30fps@all resolutions (H.265/H.264)

  • H.265, H.264, MJPEG codec supported, Multiple streaming

  • Day & Night (ICR), WDR (120dB)

  • Defocus detection, Directional detection, Motion detection, Enter/Exit, Tampering, Virtual line

  • micro SD (128GB) memory slot, PoE

  • IR viewable length 30m, IP66, IK10

  • Hallway view support

  • Analog video out & simple focus for easy installation

  • LDC support (Lens Distortion Correction)

Hanwha Wisenet PNM-C32083RVQ

  • 8MP x 4ch multi-directional camera, using one IP address

  • 15fps@8MP (H.265, H.264) AI ON, 20fps@8MP (H.265, H.264) AI OFF

  • 3.3~5.7mm (FoV H: 109°~56°, V: 55°~31°) motorized varifocal lens

  • Integrated IR that rotates with camera head, IR viewable length [PoE+] 15m (49ft) / [HPoE*] 20m (65ft)

  • H.265, H.264, MJPEG codec, Multi-streaming

  • 120dB WDR

  • USB port for easy installation

  • Analytics events based on AI engine: Object detection [Person/Vehicle (Car/Bus/Truck/Motorcycle/Bicycle)], IVA (Virtual line/Area, Enter/Exit, Loitering, direction, intrusion), Appear/Disappear

  • WiseNR Ⅱ (using AI engine), WiseStreamⅢ (Based on AI engine)

  • I/O Box compatibility for audio & alarm I/O

  • TPM with FIPS 140-2 level 2

  • micro SD card 512GB x2

  • Operating Temperature: -40°C~+55°C (-40°F~+131°F)

  • PoE+ / HPoE* powered

  • Hard-coated dome bubble

  • IP66, IK10, NEMA4X

  • Easy Gangbox mounting installation

Hanwha Wisenet PNM-9031RV

  • (5MP X 4 sensors) 15MP @ 20fps

  • Triple codec H.265/H.264/MJPEG with WiseStream II technology

  • WDR 120dB

  • IR viewable length 20m (65.5’)

  • Built-in video analytics and sound classification

  • Heatmap

  • Bi-directional audio support

  • Micro SD 2 slots

    • IP66/IK10/NEMA4X

  • TPM 2.0 (FIPS 140-2 level 2) for enhanced cybersecurity

  • PoE+/12VDC powered


Installation

Installation of cameras will be per the manufacturer recommended installation.

Central server is virtualized


Local Security Camera Recording Server Requirements

  • The system shall facilitate simultaneous digital multi-channel MJPEG, MPEG4, MPEG-4 ASP, MxPEG,and H.265 video recording of IP cameras and IP video encoders without any software limitations on number of cameras per server.

  • The two-way audio shall allow users to transmit and record audio from connected microphones and audio from the operator’s microphone to attached speakers.

  • The generic framework shall receive and store metadata from compatible devices and clients.

  • Route traffic between multiple connected cameras and multiple clients shall be able to request live view, playback and export.

  • A dedicated recording stream shall enable optimization stream properties (resolutions, encodings and frame rate) for video storage and forensic usage.

  • The system shall secure a high speed recording database holding JPEG images or MPEG4, MPEG-4 ASP, MxPEG, H.264 or H.265 streams.

  • Flexible control of recording characteristics for MPEG4/H.264/H.265 streams, shall make it possible to toggle between recording keyframes only or the full stream.

  • The system shall record more than 30 frames per second per camera, limited only by hardware. Recording quality shall depend entirely on camera and video encoder capabilities with no software limitations.

  • Pre-recording buffer (used for event/motion based recording) in RAM shall minimize the disk read/write operations when no video is recorded.

  • Edge Storage with flexible retrieval shall enable video retrieval from camera storage. This shall enable users to effectively retrieve video recordings across low-bandwidth connections.

  • Scalable Video Quality Recording™ (SVQR) shall enable seamless merging of video stored in the recording server, and video retrieved from a camera associated edge storage, or interconnected system.

  • The system shall enable the possibility to import pre-event images recorded locally in camera or video encoder.

  • Built-in, real-time, camera-independent motion detection with the ability to generate motion metadata for Smart Search.

  • The recording server shall run as a Windows service under local system account or optional local Windows user or Microsoft Active Directory account with run-as-a-service privileges

  • Port forwarding shall enable clients to access the recording servers from outside a network address translation (NAT) firewall.

  • The system shall support both IPv4 and IPv6 addressing.

  • The 64-bit recording servers shall allow more cameras to be run on a single server unit

  • The secure HTTPS camera connection on devices shall support HTTPS.

  • Remote Connect Services shall enable you to securely connect remote cameras across different types of private and public networks.

  • I/O and events

  1. XProtect Professional+shall support devices with one or more input and output ports.

  2. The Powerful rule processing engine shall execute start and stop actions triggered by events or time profiles.

  • Setup and management

  1. Download and install the recording server from a web page on the management server. The recording server shall be completely managed via the Management Client and configuration changes shall be applied instantly while recording is in operation.

  2. Local recording server configuration data shall be available during periods where the management server is inaccessible.

  3. Recording server manager shall be available in the local console notification area (icon tray) for status messages, start/stop of the service and change of network settings.

  • Clients shall be authenticated and authorized at the management server and shall use a session-limited access token to access the recording server.

  • Shall enable logging of system, audit and rule entries to the management server with local caching during offline scenarios.


Local Security Camera Server for fewer than 30 cameras

  • Contact Technology Services for current model.


Local Security Camera Server for more than 30 cameras

  • Contact Technology Services for current model.


Intercoms & Emergency Stations

AiPhone IX Series IP Addressable Intercoms & Emergency Stations

  1. Master Station
    Architect to consult with District Project Manager for Specific model

  2. Sub Master Station
    Architect to consult with District Project Manager for Specific model

  3. Video Stations
    Architect to consult with District Project Manager for Specific model

  4. Audio Stations
    Architect to consult with District Project Manager for Specific model

  5. Adapters
    Architect to consult with District Project Manager for Specific model


Warranty

The contractor shall warrant their work to be free of defects for a period of twelve (12) months from the date of issuance of the Notice of Completion. The manufacturer’s warranty period for video recording equipment shall be a minimum of thirty-six (36) months from the manufacture date code under normal use and service. The warranty period for cameras shall be a minimum of twelve (12) months from date of manufacture.

All equipment and workmanship of entire system shall be under warranty for 1 year from date of system final acceptance by the Facilities Project Manager, Police Services, and Technology Services. NEW Component warranties shall be honored for the term established by the manufacturer, if greater than 1 year. The Contractor shall include in the warranty one site visit at the end of the warranty period to check and adjust all equipment and restore all systems to original performance standards.

During the Warranty period Contractor shall respond to Service Calls for equipment failures resulting in complete or partial network outages. Contractor shall respond to such calls within 4 hours and be on-site within 24 hours with replacement components as required to restore the network to original performance standards

Activate all manufacturers’ equipment warranties on NEW product in Owner’s name to commence on the date of acceptance. In the case of Contractor- modified equipment, the manufacturer’s warranty is normally voided. In such cases, the Contractor shall provide the Owner with a warranty equivalent to that of the original manufacturer.


Warranty Documentation

All warranty documentation shall consist of the following:

  • Warranty shall be a twenty (20) year manufacturer supported extended warranty issued to the customer upon completion of the project.

  • Documentation from the manufacturer that the contractor has authority to provide the warranty on behalf of the manufacturer.

  • Complete documentation regarding the manufacturer’s warranty shall be submitted as part of the proposal. This shall include, but is not limited to: a sample of the warranty that would be provided to the customer when the installation is complete and documentation of the support procedure for warranty issues.

  • A systems application assurance manual documenting the vendor supported applications and application guidelines shall be provided as part of the submittals.


Training Requirements

Respondent’s project price shall include (2) two orientation sessions with OUSD’s Police Services, Technology Services and facility support personnel. These sessions, which for planning purposes may last up to four (4) hours each at a minimum of two (2) hours, shall:

  • Provide an overview of the architecture and its functionality

  • Provide on-the-job training to designated personnel, to instruct them in the operation and maintenance of the systems.

  • Review as-built documentation

  • Establish recommendations for effective management and maintenance of the installed VMS.

  • Arrange with the equipment manufacturer for such instruction, at no additional cost, in the event qualified instructors are not available on staff for certain sophisticated equipment.

  • Provide training on the use of the Service Ticketing Email System if the security system or a camera malfunctions or breaks.

The first training session will commence within (10) days after final completion and the second will occur within 1 year after final completion.


3.7 SYSTEMS TESTING AND ACCEPTANCE


Pre-Test & Final Testing

Facilities Project Manager and Technology Services shall be notified 72 hours prior to any and all acceptance testing of security camera systems, so monitoring of the security camera system can be initiated, and OUSD project team shall be scheduled to attend the testing.

Facilities Project Manager and Technology services shall always be present and participate in all testing on a project whether it is a pre-test or final acceptance test. Verification of cameras, labels and device addresses shall be made via Service Ticketing Email System and confirmed with the vendor, Facilities Project Manager or Technology Services during the testing.

Prior to the final acceptance test, the vendor shall perform a complete pre-test with the Facilities Project Manager and Technology Services. The pre-test shall be for all security camera equipment and testing records of the pre-test shall be provided to ensure a successful final acceptance test. As part of the completion of work on the security camera systems, a full documented test of all the components on the security camera system shall be performed. A representative from the OUSD project team shall be present for the test. Any deficiencies reported by the district representatives and/or district consultant shall be corrected and retested prior to calling for the final inspection. As part of the testing, the vendor shall provide the OUSD project team with a points list of all the devices to be tested. A record set of approved plans shall also be available on site during the testing for reference.

If the pre-test is successful, at the discretion of the Facilities Project Manager and Technology Services, the pre-test may be considered the final acceptance test.

Prior to any final acceptance test, the Facilities Project Manager and Technology Services must be sent an email listing the total number of new cameras installed, and the number of existing cameras prior to the start of the final acceptance test. For any final acceptance test that is scheduled after working hours or weekends, the vendor must perform a pre-test of the system during a time when the Facilities Project Manager and Technology Services are able to verify the receipt of the camera signals at the time of pre-testing.

System acceptance tests shall not be performed until the initial system commissioning has been completed. The system acceptance tests shall be supervised by the Facilities Project Manager, Technology Services, and the vendor and shall consist of the following:

  • Take a physical inventory of all equipment and materials on site and compare to equipment lists in the contract documents.

  • Demonstrate the operation of all system equipment.

  • Application tests will be required to determine compliance and interoperability with core network based applications.

  • In the event further adjustment is required, or defective equipment must be repaired or replaced, tests may be suspended or continued at the option of the vendor.

  • If acceptance of the system is delayed because of defective equipment or because the equipment does not fulfill this specification, reimburse the Owner for all time and expenses of the vendor for these tests during any extensions of the acceptance-testing period.

If the security camera installation or modification is in “phased” stages or if there are substantial corrections and additions to the scope of the project, then the Contractor shall assume responsibility for subsequent testing and retesting of the security camera system installation. After the last phase of the security camera system has been completed and tested totally, ten percent of the previously completed phases are to be tested with the final test phase.

Punch list items are only allowed on issues that do not create safety issues, such as hardware or software failures, any trouble conditions, equipment failures, or for items that do not affect a fully operation security camera system with complete coverage in order to conduct a final acceptance test. Non-critical items such as painting and patching, demolition, access issues are examples of what may be considered as “Punch List” items.

Once a security camera installation has been tested, and subsequent changes are made after the final test that affect the configuration of the original installation and scope of the project’s security camera system, a new final security camera test shall be performed due to the changes of the originally installed system. Label changes do not require a new final security camera test. Only changes, such as device additions, deletions or changes to functional programming shall require a new final security camera test.

Acceptance & Sign-off

Spare parts are required and noted within these Standards shall be delivered to the Facilities Project Manager prior to scheduling a final test. No FINAL test date will be accepted until the spare parts indicated in the project specifications and these Standards have been received by the Facilities Project Manager.

No system troubles or equipment failures shall be present at the final acceptance testing. If there are troubles, the test shall not occur.

Facilities Project Manager, Police Services, and Technology Services as the End User/Owner of these systems reserves the right to not accept any installation that does not adhere to these Standards. The vendor shall correct all issues to the Facilities Project Manager’s, Police Services’, and Technology Services’ satisfaction before the Facilities Project Manager, Police Services, and Technology Services will accept the system handover.