Cloud Based Transit Data Analytics Platform

The Vendor is required to provide for a cloud-based transit data platform using its own data to provide enhanced real-time information to both riders on the street and internally for departments to use for analytics and data-driven decision-making.
- This product must be already developed, deployed, and functioning in the real world.
- They should assist in creating a roadmap for the agency, including a comprehensive onboarding process, access to online training materials, and help with the launch of customer and internal-facing tools.
- Solution that directly handles either route or scheduling planning, but it should be able to inform such activities by staff.
- Solutions should be able to combine multiple feeds, in real-time, with the intent of producing higher level data accuracy and data redundancy in case one feed goes down.
- Solutions proposed by the vendor should have the ability to ingest incoming data from various devices no more than every ten seconds.
- Any solution should be able to ingest all vehicle assignment data.
- Technology should be able to correlate and/or determine vehicle assignments to ensure data matches correctly to the right route, trip, etc. even if an operator does not login into the CAD/AVL system.
- Any solution proposed must have tools/components that enable agency staff to monitor data feed uptime and health, automated preferably.
- Requires a live web-browser-based map display of routes, stops, and vehicle locations.
- The interface shall include embedded links to GPS Playback, allowing instant replay of individual trips.
- Users should have the ability to control the advancing through the specific date/time range. The control will display the time of the displayed vehicle.
- This interface should allow users to investigate vehicles at a minimum the following:
•    The route being operated
•    The head sign of the vehicle (from agency-Static data)
•    The trip and/or block operated by the vehicle
•    The real-time vehicle adherence expressed in minutes to one decimal point
•    Driver ID (if provided by agency)
•    Vehicle speed
•    On-time performance
- The predictions must be able to be accessed by passengers through any web browser, on any device, regardless of screen size.
- The interface shall adjust itself to provide optimal experiences on desktops, tablets, and mobile devices.
- ensure enhanced passenger information and predictions are accessible to native iOS and Android mobile applications and other modal applications.
- The solution should be capable of analyzing and visualizing millions of data points in seconds, allowing staff to investigate issues.
- This interface should allow staff to carry out before-and-after studies to measure the impact of service changes and determine whether such changes were successful or not.
- On-time performance reports should be able to include all scheduled stops and those without an observed departure time including missing data and missing service.
- Running times should visualized both in chart and table formats.
- Terms of analysis, utilizing thousands of observations:
•    Show overall system performance
•    Show route-level running times
•    Show trip-level running times for a route
•    Show stop-level running times
•    Segment the different components of travel times – typical drive time, traffic and dwell
•    Show segment (stop-to-stop or time point to time point) level running times
•    Depict configurable percentiles of groupings of running times
•    Selection of day type – weekday, Saturday, Sunday, or all
•    Allow for the specification of route/trip direction
•    Display running times separated into minimum running time composite of the fastest observed travel time, dwell at stops, and additional minutes in transit
•    Display total and component run time and distribution and configurable percentages for individual trips and all trips across a selected timeframe – this should be able to calculate any percentile of interest
•    Be able to make comparisons between actual travel times to actual durations against scheduled durations – this includes overall trip running times for two different schedule periods and/or day types
•    Ability to see reporting by run number
•    Color-coded as applicable to analysis
- The interface should offer suggested run times that maximize potential on-time performance based on historical run-time data, be able to communicate the on-time performance impacts if suggested running times were implemented, and aid in determining and quantifying changes whether schedule change, transit priority, or other infrastructure project.
- The solution should not be reliant upon geofencing to ensure real-time information matches with mobile applications, Google Maps, the website, and other customer facing locations.
- There shall be no limits on the number of individuals who can be given access to the solution.
- The solution should be able to utilize a query builder or SQL-like interface for ad hoc reporting. If not, the vendor must explain why and offer an alternative approach that fulfills this.

- Contract Period/Term: 1 year
- Questions/Inquires Deadline: November 6, 2025