G._BBB_OBVSS_System_Requirements_Matrix.xlsx
XLSX spreadsheet 20 KB Posted
- Solicitation number
- 491
- Issued by
- Los Angeles County, San Francisco City, California
About this file
This is a System Requirements Matrix for an Onboard Bus Video Surveillance System (OBVSS) procurement by the City of Santa Monica Department of Transportation (SMDOT) for the Big Blue Bus fleet. The document outlines 109 technical requirements organized across multiple categories including onboard recording and storage, wireless and cellular connectivity, video management and evidence handling, camera systems, audio recording, multiplex integration, cybersecurity, installation and acceptance, warranty and lifecycle support, training and documentation, and maintenance and customer support. The OBVSS must be a turnkey solution featuring high-definition IP-based onboard recorders capable of supporting up to 32 camera channels with mixed resolutions (32 FHD and up to eight 4K/UHD cameras), a minimum of 600 hours of video retention per vehicle, redundant mirrored storage, GPS and telemetry capture, and 3-axis accelerometer for event detection. Camera coverage requirements mandate at least eight cameras for 30/40-foot buses and ten cameras for 60-foot articulated buses, with specific resolutions and coverage zones. The system must integrate with the existing Dinex/I/O Controls multiplex architecture, support both on-premises and cloud-hosted video management platforms, provide real-time live viewing and remote configuration, and include synchronized time management via NTP.
The proposal must address cybersecurity integration with the City's identity management environment and complete the City's VISA and Technology/Architecture questionnaires. Installation services must be performed by the vendor or approved subcontractor with minimal vehicle downtime (not exceeding one service day without written approval), pilot installations on representative bus types, and a 30-day operational acceptance period. The vendor must provide at least one year of warranty with optional four-year extended coverage, comprehensive hardware and software support including updates and security patches at no additional cost during the support term, preventive maintenance instructions, initial and follow-up training for operations and maintenance users, and detailed as-built documentation. Optional offerings include replacement of existing passenger-facing entry monitors, AI and computer-vision analytics capabilities, forward-facing camera solutions for approximately 15 non-revenue vehicles, and ridership/APC validation functionality. All pricing must separately identify one-time costs (hardware, installation) and recurring costs (cellular/data/SIM/cloud/licensing) for both on-premises and cloud-hosted options.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| Request_for_Proposals_for_Onboard_Bus_Video_Surveillance_System.pdf | ||
| Fleet_Information.xlsx | XLSX spreadsheet | |
| Technology_Insurance_Requirements_-_Including_On_Site_Work.docx | DOCX document | |
| F._BBB_OBVSS_Cost_Proposal.xlsx | XLSX spreadsheet | |
| B._Enterprise_Core_Technologies.pdf | ||
| D._City_of_Santa_Monica_VISA_Questionnaire.pdf | ||
| C._Architecture_Questionnaire.pdf | ||
| Proposer_Checklist.pdf | ||
| Software_as_a_Service_Template_(11-25).docx | DOCX document | |
| Software_Maintenance_Agreement_Template.docx | DOCX document |
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
System Requirements Matrix
| Big Blue Bus — OBVSS System Requirements Matrix | |||||||
| Vendor Instructions: Select a response for each requirement. Describe all exceptions, dependencies, substitutions, or proposed alternatives and cite the applicable proposal section. Requirements below are concise summaries; the RFP Technical Specifications remain controlling. | |||||||
| Requirement ID | Source Clause | Category | Requirement | Requirement Type | Vendor Response | Comments/Exceptions | Proposal Reference |
| OBVSS-001 | 3.3.1.1 | Onboard Recording & Storage | Provide a high-definition IP-based NVR or equivalent onboard recorder; analog recorders are not acceptable. | Mandatory | |||
| OBVSS-002 | 3.3.1.2 | Onboard Recording & Storage | NVR must withstand transit vibration, -10°F to 120°F, and 5%–95% non-condensing humidity. | Mandatory | |||
| OBVSS-003 | 3.3.1.3 | Onboard Recording & Storage | Support the initial camera configuration and future expansion up to 32 IP camera channels. | Mandatory | |||
| OBVSS-004 | 3.3.1.4 | Onboard Recording & Storage | Support required camera types/resolutions, including up to 32 FHD channels and up to eight 4K/UHD cameras. | Mandatory | |||
| OBVSS-005 | 3.3.1.5 | Vehicle Data & Events | Provide at least six discrete inputs for vehicle-state/event association with video. | Mandatory | |||
| OBVSS-006 | 3.3.1.6 | Onboard Recording & Storage | Support both battery and ignition power configurations. | Mandatory | |||
| OBVSS-007 | 3.3.1.7 | Vehicle Data & Events | Capture GPS, vehicle speed, and other telemetry. | Mandatory | |||
| OBVSS-008 | 3.3.1.8 | Vehicle Data & Events | Detect acceleration/deceleration and G-force events using a 3-axis accelerometer or equivalent; create synchronized event tags. | Mandatory | |||
| OBVSS-009 | 3.3.1.9 | Onboard Recording & Storage | Provide configurable post-ignition shutdown with continued video/audio recording; identify supported duration. | Mandatory | |||
| OBVSS-010 | 3.3.1.10 | Wireless & Cellular | Allow Wi-Fi video downloads to continue after ignition-off on battery power until the configured limit or download completion. | Mandatory | |||
| OBVSS-011 | 3.3.1.11 | Onboard Recording & Storage | Operate with SMDOT fleet electrical characteristics, including 9–32 VDC. | Mandatory | |||
| OBVSS-012 | 3.3.1.12 | Vehicle Data & Events | Maintain synchronized time across recordings, metadata, events, and logs using NTP; describe timekeeping during connectivity/power loss. | Mandatory | |||
| OBVSS-013 | 3.3.1.13 | Vehicle Data & Events | Support vehicle-system and metadata integration requirements in Sections 3.3.6.2–3.3.6.4. | Mandatory | |||
| OBVSS-014 | 3.3.1.14 | Onboard Recording & Storage | Store and manage interior and exterior camera video onboard the vehicle. | Mandatory | |||
| OBVSS-015 | 3.3.1.15 | Onboard Recording & Storage | Use removable/interchangeable storage supporting manual retrieval via review/docking solution and rapid media replacement; identify media type. | Mandatory | |||
| OBVSS-016 | 3.3.1.16 | Onboard Recording & Storage | Provide at least 600 hours (approx. 30 days) of usable recorded-video retention per vehicle after redundancy and storage overhead. | Mandatory | |||
| OBVSS-017 | 3.3.1.18 | Onboard Recording & Storage | Provide storage-sizing calculations showing camera count, resolution, frame rate, codec, bitrate, installed/usable storage, and estimated retention. | Mandatory | |||
| OBVSS-018 | 3.3.1.19 | Onboard Recording & Storage | Maintain evidentiary video quality; do not reduce required resolution or frame rate solely to meet retention. | Mandatory | |||
| OBVSS-019 | 3.3.1.20 | Onboard Recording & Storage | Provide redundant mirrored storage or equivalent fault-tolerant architecture. | Mandatory | |||
| OBVSS-020 | 3.3.1.21 | Spares & Maintenance | Include pricing for recommended spare components at 10–15% of deployed quantities and identify critical spares. | Mandatory | |||
| OBVSS-021 | 3.3.1.22 | Spares & Maintenance | Provide pricing for optional spares such as antennas, SIM/modems, status indicators, and event marker buttons. | Optional | |||
| OBVSS-022 | 3.3.1.23 | Onboard Recording & Storage | Provide standards-based PoE for required cameras; identify standards, per-port capability, and any external PoE equipment. | Mandatory | |||
| OBVSS-023 | 3.3.1.24 | Onboard Recording & Storage | Provide at least 120W aggregate PoE capacity for all required cameras operating simultaneously. | Mandatory | |||
| OBVSS-024 | 3.3.1.25 | Onboard Recording & Storage | Avoid unreasonable camera-to-PoE-port restrictions; disclose any port or power/connectivity limitations. | Mandatory | |||
| OBVSS-025 | 3.3.1.26 | Wireless & Cellular | Provide onboard communications for wireless data download and remote camera-system configuration via router/Wi-Fi. | Mandatory | |||
| OBVSS-026 | 3.3.1.27 | System Health & Diagnostics | Provide an operator-accessible visual indicator of basic OBVSS operating status. | Mandatory | |||
| OBVSS-027 | 3.3.1.28 | Vehicle Data & Events | Provide an operator event marker that time-stamps incidents and preserves configurable pre/post-event video; identify integration method. | Mandatory | |||
| OBVSS-028 | 3.3.2.1 | Video Management & Evidence | Provide a unified or integrated VMS platform for video requests/review, configuration, fleet health, and related functions. | Mandatory | |||
| OBVSS-029 | 3.3.2.2 | Video Management & Evidence | Do not require specialized PC equipment to view, download, or access recordings beyond a hard-drive dock. | Mandatory | |||
| OBVSS-030 | 3.3.2.3 | Video Management & Evidence | License all required SMDOT users without additional per-user charges during the warranty/support term. | Mandatory | |||
| OBVSS-031 | 3.3.2.4 | Hosting & Architecture | Describe VMS architecture, including client/browser, server/cloud, database, and other required components. | Informational | |||
| OBVSS-032 | 3.3.2.5 | Cybersecurity & Identity | Support integration with the City's identity management environment. | Mandatory | |||
| OBVSS-033 | 3.3.2.6 | Video Management & Evidence | Allow immediate or scheduled video/data retrieval requests and status tracking through completion. | Mandatory | |||
| OBVSS-034 | 3.3.2.7 | Video Management & Evidence | Export to common formats, distribute without proprietary software, and support selectable download quality/resolution. | Mandatory | |||
| OBVSS-035 | 3.3.2.8 | Video Management & Evidence | Support automated video/audio retrieval and collection of fleet health/diagnostic information. | Mandatory | |||
| OBVSS-036 | 3.3.2.9 | Video Management & Evidence | Allow archived-video search by date and time. | Mandatory | |||
| OBVSS-037 | 3.3.2.10 | Video Management & Evidence | Allow retrieval by vehicle location in addition to date, time, vehicle, and other metadata. | Mandatory | |||
| OBVSS-038 | 3.3.2.11 | Hosting & Architecture | Maintain data architecture for cataloging/searching video, audio, metadata, and health records; describe the database/architecture. | Informational | |||
| OBVSS-039 | 3.3.2.12 | Video Management & Evidence | Export requested video as a continuous reviewable file; segmented video/blocks are not acceptable. | Mandatory | |||
| OBVSS-040 | 3.3.2.13 | Video Management & Evidence | Pause and resume interrupted video downloads without restarting the transfer. | Mandatory | |||
| OBVSS-041 | 3.3.2.14 | Video Management & Evidence | Allow review of available portions of requested video before the full transfer completes, where supported. | Mandatory | |||
| OBVSS-042 | 3.3.2.15 | Video Management & Evidence | Provide real-time/live-look video monitoring over cellular or Wi-Fi. | Mandatory | |||
| OBVSS-043 | 3.3.2.16 | Video Management & Evidence | Support adaptive/primary-secondary streaming for remote viewing without reducing local evidentiary recording quality. | Mandatory | |||
| OBVSS-044 | 3.3.2.17 | Video Management & Evidence | Provide map-based vehicle-location visualization correlated with live and/or recorded video. | Mandatory | |||
| OBVSS-045 | 3.3.2.18 | Video Management & Evidence | Display applicable time-synchronized vehicle/event metadata during video review. | Mandatory | |||
| OBVSS-046 | 3.3.2.19 | Video Management & Evidence | Provide capability to blur or block identifying features during retrieval or post-download. | Mandatory | |||
| OBVSS-047 | 3.3.2.20 | System Health & Diagnostics | Automatically identify reportable system health conditions and notify designated SMDOT personnel, including by email. | Mandatory | |||
| OBVSS-048 | 3.3.2.21 | System Health & Diagnostics | Provide fleet- and vehicle-level health/diagnostic information and historical logs for monitored OBVSS components. | Mandatory | |||
| OBVSS-049 | 3.3.2.22 | Hosting & Architecture | Support either City on-premises deployment or Proposer-provided cloud hosting. | Mandatory | |||
| OBVSS-050 | 3.3.2.23 | Hosting & Architecture | Provide separate pricing for on-premises and cloud-hosted VMS options and identify associated costs. | Mandatory | |||
| OBVSS-051 | 3.3.3.1 | Camera System | Use digital IP cameras with PoE or equivalent standards-based connectivity; new analog HD/AHD cameras are not acceptable. | Mandatory | |||
| OBVSS-052 | 3.3.3.2 | Camera System | Provide minimum native 1920x1080 resolution except where higher resolution is required. | Mandatory | |||
| OBVSS-053 | 3.3.3.3 | Camera System | Provide usable low-light evidentiary video using IR or equivalent technology where required. | Mandatory | |||
| OBVSS-054 | 3.3.3.4 | Audio Recording | Support synchronized interior audio; identify microphone configuration and whether microphones are integrated or separate. | Mandatory | |||
| OBVSS-055 | 3.3.3.5 | Camera System | Exterior cameras/exposed components must be transit-grade and rated IP67 or greater. | Mandatory | |||
| OBVSS-056 | 3.3.3.6 | Camera System | Provide stable camera images free from vibration. | Mandatory | |||
| OBVSS-057 | 3.3.4.1–3.3.4.4 | Camera Coverage | Meet specified coverage areas, minimize blind spots, and support appropriate fixed/360°/fisheye camera technologies. | Mandatory | |||
| OBVSS-058 | 3.3.4.5 | Camera Coverage | For 30/35/40-foot buses, provide at least eight cameras including one 4K forward roadway camera and all listed coverage zones/resolutions. | Mandatory | |||
| OBVSS-059 | 3.3.4.6 | Camera Coverage | For 60-foot articulated buses, provide at least ten cameras including one 4K forward roadway camera and all listed coverage zones/resolutions. | Mandatory | |||
| OBVSS-060 | 3.3.5.1 | Audio Recording | Provide intelligible, time-synchronized passenger-compartment audio attributable to the applicable source/area and independently reviewable. | Mandatory | |||
| OBVSS-061 | 3.3.6.1 | Multiplex & MFD Integration | Be compatible with existing Dinex/I/O Controls multiplex architecture and display logic for rear-view and driver MFD functions. | Mandatory | |||
| OBVSS-062 | 3.3.6.2 | Vehicle Data & Events | Support available vehicle trigger states, including reverse, turn signals, hazards, doors, kneel/ramp, and J1939/CAN inputs. | Mandatory | |||
| OBVSS-063 | 3.3.6.3 | Vehicle Data & Events | Capture and associate available vehicle/event metadata with corresponding video for evidentiary review. | Mandatory | |||
| OBVSS-064 | 3.3.6.4 | Vehicle Data & Events | Time-synchronize required metadata with video and make it available during review/retrieval. | Mandatory | |||
| OBVSS-065 | 3.3.6.5 | Multiplex & MFD Integration | Automatically route the rear-facing camera to the existing MFD/rear-view monitor with minimal latency; identify HDMI/BNC interface. | Mandatory | |||
| OBVSS-066 | 3.3.6.6 | Multiplex & MFD Integration | Identify and provide required interfaces, converters, configuration, programming coordination, and integration modules. | Mandatory | |||
| OBVSS-067 | 3.3.6.7 | Multiplex & MFD Integration | Do not assume replacement of existing MFDs, rear-view monitors, or multiplex hardware unless proposed as an approved alternate. | Mandatory | |||
| OBVSS-068 | 3.3.6.8 | Multiplex & MFD Integration | Provide a written integration description and schematic for the existing multiplex/Dinex control logic. | Mandatory | |||
| OBVSS-069 | 3.3.7.1–3.3.7.2 | Passenger Entry Monitor | Provide separately priced replacement of existing passenger-facing entry monitors and identify all required installation components. | Optional | |||
| OBVSS-070 | 3.3.7.3 | Passenger Entry Monitor | Replacement monitors must be ≥10 inches, HDMI-capable, continuously display the entrance feed, transit-grade/vandal-resistant, and daylight-visible. | Optional | |||
| OBVSS-071 | 3.3.7.4 | Passenger Entry Monitor | Price passenger-entry monitor replacement separately; it is not part of the base proposal. | Optional | |||
| OBVSS-072 | 3.3.8.2–3.3.8.3 | Wireless & Cellular | Provide a dedicated OBVSS communications solution for live view, offload, remote configuration, and health monitoring; do not assume existing Clever/CradlePoint as the primary path. | Mandatory | |||
| OBVSS-073 | 3.3.8.4 | Wireless & Cellular | Support live video streaming over yard Wi-Fi and cellular connectivity and remote onboard camera-system configuration. | Mandatory | |||
| OBVSS-074 | 3.3.8.5 | Wireless & Cellular | Describe OBVSS capabilities over 5G cellular and BBB's current Wi-Fi infrastructure. | Informational | |||
| OBVSS-075 | 3.3.8.6 | Wireless & Cellular | Support remote transfer of requested video, audio, metadata, and system information over yard Wi-Fi and proposed cellular service. | Mandatory | |||
| OBVSS-076 | 3.3.8.7 | Wireless & Cellular | Support commercial 4G LTE/5G and BBB-compatible Wi-Fi, including 802.11ax and 5 GHz; identify supported standards/bands. | Mandatory | |||
| OBVSS-077 | 3.3.8.8 | Wireless & Cellular | Separately identify one-time and recurring cellular/data/SIM/cloud/licensing and optional managed-service costs. | Mandatory | |||
| OBVSS-078 | 3.3.9.1 | Cybersecurity & Architecture | Complete and submit the City's VISA and Technology/Architecture questionnaires as part of the technical response. | Mandatory | |||
| OBVSS-079 | 3.4.1–3.4.2 | Installation & Acceptance | Perform installation at BBB within stated bus/bay/time constraints; SMDOT will provide secure project equipment storage. | Informational | |||
| OBVSS-080 | 3.4.3 | Installation & Acceptance | Remove existing OBVSS equipment. | Mandatory | |||
| OBVSS-081 | 3.4.4 | Installation & Acceptance | Use a certified disposal process for items containing sensitive data, such as storage drives. | Mandatory | |||
| OBVSS-082 | 3.4.5 | Installation & Acceptance | Installation must be performed by the vendor or its selected subcontractor. | Mandatory | |||
| OBVSS-083 | 3.4.6.1–3.4.6.2 | Installation & Acceptance | Complete pilot installations on a 40-foot bus and a 60-foot articulated bus, if applicable, and obtain SMDOT approval before fleet rollout. | Mandatory | |||
| OBVSS-084 | 3.4.7.1 | Installation & Acceptance | Provide a detailed fleet installation schedule with quantities, sequence, milestones, and total project duration. | Mandatory | |||
| OBVSS-085 | 3.4.8.1–3.4.8.2 | Installation & Acceptance | Minimize downtime; no vehicle may be out of service more than one service day without written approval. | Mandatory | |||
| OBVSS-086 | 3.4.9.1 | Installation & Acceptance | Perform post-installation functional verification of cameras, audio, live view, offload, display integrations, triggers, GPS, and metadata. | Mandatory | |||
| OBVSS-087 | 3.4.10.1 | Installation & Acceptance | Complete a 30-day operational acceptance period covering system functions, downloads, live viewing, storage, and alerts. | Mandatory | |||
| OBVSS-088 | 3.4.11.1 | Installation & Acceptance | Restore vehicle panels, compartments, wireways, mounting surfaces, and finishes after installation. | Mandatory | |||
| OBVSS-089 | 3.4.12.1 | Installation & Acceptance | Provide as-built documentation by vehicle type, including wiring, camera/monitor/NVR locations, and multiplex integration points. | Mandatory | |||
| OBVSS-090 | 3.5.1–3.5.2 | Warranty & Lifecycle Support | Provide at least a one-year warranty on hardware and maintenance support beginning at project completion/sign-off. | Mandatory | |||
| OBVSS-091 | 3.5.3 | Warranty & Lifecycle Support | Offer optional extended warranty coverage for an additional four years at the City's discretion. | Optional | |||
| OBVSS-092 | 3.5.4 | Warranty & Lifecycle Support | Include hardware/software support, updates, security patches, firmware, bug fixes, upgrades, licensing, installation, and integration at no additional cost during the support term. | Mandatory | |||
| OBVSS-093 | 3.6.1–3.6.2 | Training & Documentation | Provide in-person initial training at BBB and a detailed training plan with topics and hours for maintenance and operational users. | Mandatory | |||
| OBVSS-094 | 3.6.3 | Training & Documentation | Provide maintenance/VMS training covering repair, installation, troubleshooting, PM, retrieval, reporting, alerts, configuration, access, and asset management. | Mandatory | |||
| OBVSS-095 | 3.6.4 | Training & Documentation | Provide digital user guides, troubleshooting/PM instructions, equipment lists, wiring diagrams, and system use/maintenance documentation. | Mandatory | |||
| OBVSS-096 | 3.7.1 | Maintenance & Customer Support | Describe the RMA process, submission method, turnaround time, expedited options, tracking communications, and customer costs. | Mandatory | |||
| OBVSS-097 | 3.7.2.1 | Maintenance & Customer Support | Provide documented preventive-maintenance instructions, recommended frequency, and inspection checklists for onboard equipment. | Mandatory | |||
| OBVSS-098 | 3.8.1–3.8.6 | Optional Technology | Describe and separately price any available/emerging AI, computer-vision, analytics, or pilot capabilities, including maturity, deployments, limitations, dependencies, and timeline. | Optional | |||
| OBVSS-099 | 3.9.1–3.9.4 | Optional Non-Revenue Vehicles | Optionally propose forward-facing camera solutions for ~15 non-revenue vehicles, including platform, integration, storage, retrieval, metadata, connectivity, support, and limitations. | Optional | |||
| OBVSS-100 | 3.9.5 | Optional Non-Revenue Vehicles | Provide separate cost-per-vehicle pricing for the optional non-revenue solution, including hardware, installation, software, connectivity, warranty, and recurring fees. | Optional | |||
| OBVSS-101 | 3.10.1–3.10.2 | Optional Technology | Describe available ridership/APC validation functionality, event-identification method, integrations, and required hardware/software/licensing. | Optional | |||
| OBVSS-102 | 3.11.1 | Project Deliverables | Deliver a fully functional turnkey OBVSS meeting all technical, operational, integration, installation, and performance requirements. | Mandatory | |||
| OBVSS-103 | 3.11.2 | Project Deliverables | Provide implementation services including pilot, fleet installation, removal/disposal, configuration, integration, testing, acceptance, and commissioning. | Mandatory | |||
| OBVSS-104 | 3.11.3 | Project Deliverables | Provide integration with applicable communications equipment, multiplex/MFDs, passenger monitors, Wi-Fi/cellular infrastructure, and City identity management. | Mandatory | |||
| OBVSS-105 | 3.11.4 | Project Deliverables | Provide complete system documentation, including manuals, guides, wiring/as-built drawings, camera schematics, training, and support documentation. | Mandatory | |||
| OBVSS-106 | 3.11.5 | Project Deliverables | Provide warranty, software/firmware updates, maintenance support, RMA procedures, and technical support for the applicable term. | Mandatory | |||
| OBVSS-107 | 3.11.6 | Warranty & Lifecycle Support | Ensure future/replacement components remain supported, fully compatible, and equal or better in quality/performance without reducing functionality. | Mandatory | |||
| OBVSS-108 | 3.11.7 | Project Deliverables | Provide project management covering schedule, installation sequencing, pilot, communications, QA, testing, acceptance, and closeout. | Mandatory | |||
| OBVSS-109 | 3.11.8 | Project Deliverables | Provide initial and follow-up training for operations, maintenance, safety, and administrative users. | Mandatory |
File details come from the government source that posted it. Updated .