On-Board Video Surveillance System

• Farebox Facing Interior* • Rear Door Interior* • Curbside Interior Front • Curbside Interior Rear • Streetside Interior Front • Streetside Interior Rear • Forward Facing Interior • Curbside Exterior • Streetside Exterior • Rear Facing Exterior • Road View • Driver Facing Interior* • Door Facing Interior* • Lift Gate Interior* • Rear Facing Interior • Forward Facing Interior • Curbside Exterior • Streetside Exterior • Rear Facing Exterior • Road View *These views shall include audio. RFP 2024-01 Page 10 of 51 PROPOSALS ARE DUE NO LATER THAN 2:00 PM CENTRAL TIME ON JUNE 6, 2024 2.3 Software Requirements 2.3.1 A centralized Video Management Software (VMS) shall manage all functions of the OBVSS including: video requests, video review, and system configuration. 2.3.2 The VMS should not require a specialized PC or other PC equipment to view, download, or access recorded content. 2.3.3 The VMS must allow for downloaded files to be distributed for use without additional user licenses or software being required. 2.3.4 The VMS shall be able to pause and resume downloading requested video. For example, if a large file does not download completely because the vehicle leaves the Wi-Fi coverage area, it should be able to resume downloading once the vehicle returns to the coverage area without restarting the download. 2.3.5 VMS users shall be able to review partially downloaded video if the entire video segment has not completed downloading. 2.3.6 Requested video shall be provided as a single file instead of segmented blocks. 2.3.7 The VMS shall be installed on at least 3 workstations without additional licensing or user agreements. 2.3.8 The VMS shall integrate with the District’s current CAD/AVL. The District currently uses the IVN4 and IVN5 systems provided by Clever Devices. The integration shall allow the following CAD/AVL-provided information to be