Shared Mobility Data Services

The Vendor is required to provide shared mobility device program is set to expire on March 31, 2025.
- Data Display
• Provide real-time (or near real time) fleet observation.
• Provide dynamic maps and/or charts for all relevant system metrics (e.g. trips, vehicle availability, fleet cap limits, device geographic distribution, violation locations, deployment time/locations, Location of non-resolvable vehicles, etc.).
• Provide visualization of trip path data -- GPS breadcrumbs matched to street segments.
• Display a zone-based availability metric tailored to correspond to City regulatory policy.
• Provide a metric dashboard that allows City staff to evaluate and analyze operator compliance with a minimum of post-processing, covering flexible timeframes.
• Provide a public-facing dashboard to communicate program performance and usage patterns while maintaining
- Data Parsing
• Provide the ability to parse all displayed data by:
1. Date & time
2. Operator
3. Vehicle type
4. Start and end geography
• Provide the ability to load custom geographies by which to parse data.
1. Equity zones, Beach operation zones, hex grids, transit buffers, etc.
- Data Exports
• Provide interface to export all dashboard metrics, par sable by date/time, operator, and device type.
• Provide detailed metrics – including trip starts, trip ends, min/mean/maximum device availability – at the level of individual drop zone and other City-specified geographies.
• Provide interface to export raw event data and processed trip path data for specified date ranges.
- Policy Functions
• Provide the ability to upload and display Policy-relevant spatial files (shapefile, geojson, etc.) in system.
• Provide the ability to push policy files (for drop zones, no-ride zones, special events, etc.) to providers from or through the system.
1. Allow for the ability to set zone-specific device occupancy limits and push these limits to providers.
• Provide operators with sufficient dashboard access to coordinate operational expectations with the City.
- Administrative Upkeep
• Update system to ingest and support the latest stable version of Mobility Data Specification (MDS).
• Conduct adequate validation procedures to ensure the accuracy and completeness of operators’ MDS APIs.
• Provide communications on maintenance and ETA for repair in the event of system failure, operator pipeline failure, and repair reporting.
- Desired Elements
- Data integration
• Demonstrate ability to integrate Shared Mobility data platform with broader mobility data platform(s) (e.g. curb management dashboard, near-miss collision dashboard, etc.).
• Demonstrate potential to use Shared Mobility data to develop broader transportation planning-relevant data. For example:
1. Segment-level active transportation volumes.
2. Trip path circuity and other patterns in trip paths, parable by time and trip start/end location.
3. Shared Mobility device-derived safety data, such as abrupt brakes and/or near-misses.
- Contract Period/Term: 2 years
- Questions/Inquires Deadline: March 18, 2025