| A | B | C | D | E | F | |
|---|---|---|---|---|---|---|
| 1 | ATTACHMENT A RFP-4153-15-NJ | |||||
| 2 | Row | Category | Functional Requirements | Importance | Vendor Response Y/N/O | Response Comments |
| 3 | 1 | Server and Storage | Meet or exceed manufacturer's recommended requirements | R | ||
| 4 | 2 | Windows Server 2012 Operating System | R | |||
| 5 | 3 | RAID Configuration | R | |||
| 6 | 4 | Adequate storage for a minimum of 30 Days with built in redundant storage | R | |||
| 7 | 5 | Client Devices | Windows 7 (64-bit) desktops and upgradable | R | ||
| 8 | 6 | Thin Clients (VMware) | R | |||
| 9 | 7 | Mobile Devices (Apple, Android) | R | |||
| 10 | 8 | General | Not limit the number of concurrent connections for viewing live or recorded feeds | O | ||
| 11 | 9 | Not limit the number of workstations used for monitoring video and audio streams | R | |||
| 12 | 10 | Support receiving digital input triggers and triggering digital output triggers | R | |||
| 13 | 11 |
Display auditable image overlays on both live and recorded video,
including: * Camera name, camera location * Timestamp |
R | |||
| 14 | 12 | Support guard tours / view cycling based on specified interval for applicable cameras | O | |||
| 15 | 13 | Transmissions must be secured, preferred HTTPS (if other, describe) | R | |||
| 16 | 14 | NVMS shall not limit the storage capacity and shall allow for upgrades of recording capacity without additional licensing | R | |||
| 17 | 15 | System must be scalable | R | |||
| 18 | 16 |
The system, without any degradation to video quality, shall simultaneously
offer: - Continuous video playback - Video playback transmission to the network - Continuous video receiving from the network - User selectable video archiving of pre-existing recordings - Video export |
R | |||
| 19 | 17 | Access Control |
JAIL - Integrate through the HMI workstation with Sierra Systems
(Door control System) CJSD - Integrate with existing RS2 door conrol system for door release |
R | ||
| 20 | 18 | Integrate with camera call-up system through digital means rather than through matrix | R | |||
| 21 | 19 | * Describe how the proposed system will accomplish camera call-ups with a full IP-based CCTV solution | R | |||
| 22 | 20 | Integrate with existing analog intercom system | R | |||
| 23 | 21 | Support software level integrations (configurable events, alarms, etc.) | R | |||
| 24 | 22 | Alarm Management | Provide a method for managing alarms, including event triggered alarms, system notifications, user entered | R | ||
| 25 | 23 | Audible alarms | R | |||
| 26 | 24 | Timed notifications / reminders | O | |||
| 27 | 25 | Alarm notification by email | R | |||
| 28 | 26 | Alarm notification by text message | O | |||
| 29 | 27 | Alarm notifications on-screen | R | |||
| 30 | 28 | Alarm escalation (if alarm is unacknowledged) | R | |||
| 31 | 29 | Customizable alarm/alert messages | O | |||
| 32 | 30 | Ability to create grids to pinpoint alarm trigger locations | R | |||
| 33 | 31 | Audio | Synchronize audio with video regardless of frame-rate, resolution or bitrate for both live and recorded video | R | ||
| 34 | 32 | Audio in all booking and pre-screen cameras recording full time | R | |||
| 35 | 33 | Video with associated audio must be exported in a single file and audio must be synchronized wtih video | R | |||
| 36 | 34 | Cameras | Proposed cameras may include Fixed IP, PTZ IP, Panoramic IP and/or Specialized Cameras taking into account location, environment, viewshed and lighting conditions | R | ||
| 37 | 35 | All cameras should have sufficient resolution for positive identification within their viewshed | R | |||
| 38 | 36 |
Support remote PTZ protocols and controls for applicable cameras - On live and recorded video - Set presets and create guard tours |
R | |||
| 39 | 37 |
Support IR / Night Time video capture for applicable cameras with
auto iris lenses / light sensitivity control - external cameras must have sun hoods |
R | |||
| 40 | 38 | Ability to add privacy masks | O | |||
| 41 | 39 |
15 FPS minimum - internal cameras 30 FPS minimum - external cameras |
R | |||
| 42 | 40 | Describe compression | I | |||
| 43 | 41 |
Demonstrate cameras ability to capture clear images: - reduction in motion blur - electronic image stabilization - light sensitivity |
I | |||
| 44 | 42 |
Built in intelligence - Motion detection - Record to SD card in the event of dropped network connection or server interuption - Tamper detection |
O | |||
| 45 | 43 | All cameras/enclosures to be corrections/detention grade | R | |||
| 46 | 44 | All cameras shall carry Electromagnetic Emissions and Immunity Certifications | R | |||
| 47 | 45 | Accept SD Cards to record video as a backup measure | O | |||
| 48 | 46 | Disaster Recovery | Describe methods and safeguards in place to prevent the loss of recorded data | I | ||
| 49 | 47 | Provide a method to detect dropped audio or video signals and alert system administrators | R | |||
| 50 | 48 | Schedule backups of recorded video with associated events to a networked location | R |
| 51 | 49 | Maintain a comprehensive event log for server and software | R | |||
|---|---|---|---|---|---|---|
| 52 | 50 | Facility Map | Interactive facility map / diagram with camera locations and/or viewsheds | O | ||
| 53 | 51 | Provide a visual alert to show cameras with triggered alarms/events | O | |||
| 54 | 52 | Master Control Station | Display supports simultaneous live and recorded viewing of multiple input feeds with configurable layouts | R | ||
| 55 | 53 |
MCDF: 4 - 32" Monitors CJSD: 2 - 32" Monitors per building |
R | |||
| 56 | 54 | POE Switches | Cisco Switches | R | ||
| 57 | 55 | Recording Modes | Provide at a minimum the following recording modes with the ability to configure each camera indiviually: continuous, manual, scheduled, event triggered, and motion detection. | R | ||
| 58 | 56 | Capable of setting pre and post event recording options | R | |||
| 59 | 57 | Configurable video retention periods per video source | O | |||
| 60 | 58 | User Authentication |
Provide a method to control user access and system functions by
at least the following: * Individually * Team or Group level * By Facility (Mesa County Detention Facility / Criminal Justice Services Department) |
R | ||
| 61 | 59 | Provide comprehensive audit logging of user access and activity on the system | R | |||
| 62 | 60 | Microsoft Active Directory enabled | O | |||
| 63 | 61 | User Experience | Save preset layouts/views based on user or teams | O | ||
| 64 | 62 | Ability to schedule tasks/reminders | O | |||
| 65 | 63 | Video Analytics | Describe available video analytics | I | ||
| 66 | 64 | Video Viewing | Provide multiple search functions for recorded events, including custom area of interest, date and time ranges, bookmarks. Search on multiple cameras simultaneously based on AOI. | R | ||
| 67 | 65 | Ability to zoom and select different areas of interest on recorded video | R | |||
| 68 | 66 | Forward and reverse playback of video and audio at variable speeds | R | |||
| 69 | 67 | Recorded video with associated audio will playback synchronously | R | |||
| 70 | 68 | Live viewing from multiple locations | R | |||
| 71 | 69 | Recorded viewing from multiple locations | R | |||
| 72 | 70 | The monitoring should be conducted through client software which will be required on multiple monitoring stations | R | |||
| 73 | 71 | All network video recorders should be sufficient for 30 days of storage with built-in redundant storage | R | |||
| 74 | 72 | Ability to export recordings in both native and standard format. | R | |||
| 75 | 73 | Verifiable recording metadata so file can be authenticated as original | R | |||
| 76 | 74 | Metadata should also include: date and time, video and audio parameters, event/alarm information, vector motion and transactional data | R | |||
| 77 | 75 | Wiring and punch down blocks | Category 6e | R | ||
| 78 | 76 | Plenum Shielded | R | |||
| 79 | 77 | Professionally installed, tested and certified | R | |||
| 82 | Importance | |||||
| 83 | R | Required | ||||
| 84 | O | Optional/Preferred | ||||
| 85 | I | Information Requested | ||||
| 87 | Response | |||||
| 88 | Y | Completely meets / "out of box" solution | ||||
| 89 | F | Future (Specify Release Version / Date) | ||||
| 90 | 3P | Third Party Software Required | ||||
| 91 | M | Modification (Change Using Built-in Toolset) | ||||
| 92 | C | Custom development Required (Provide cost estimate in comments section) | ||||
| 93 | N | Cannot be met / Not available | ||||
| 95 | Abbreviations | |||||
| 96 | NVMS | Network Video Management System | ||||
| A | B | |
|---|---|---|
| 1 | Importance | |
| 2 | R | Required |
| 3 | O | Optional/Preferred |
| 5 | Response | |
| 6 | Y | Completely meets / "out of box" solution |
| 7 | F | Future (Specify Release Version / Date) |
| 8 | 3P | Third Party Software Required |
| 9 | M | Modification (Change Using Built-in Toolset) |
| 10 | C | Custom development Required (Provide cost estimate in comments section) |
| 11 | N | Cannot be met / Not available |
| 13 | Abbreviations | |
| 14 | NVMS | Network Video Management System |