Big Data Analytics Services

The vendor required to provide big data analytics services to enhance fixed-route real-time arrival predictions and support historical analysis of service delivery.
- Required system functionalities
1. Generate ridership reports
•    Ability to automatically receive unprocessed automated passenger counter (APC) from existing hardware and existing data pipelines without the cost of additional hardware
•    Ability to analyze processed ridership data and produce recommendations for dart administration and operations. 
•    Create user-friendly dashboards that visualize ridership trends, including interactive graphs and maps. 
•    These maps and graphs must be able to easily translate into presentations for reporting. 
•    Ability to track long-term ridership trends and identify seasonal variations and shifts in demand. 
•    Ability to show ridership split by mode and city. 
•    Must also be able to show modal allocation by city 
•    Ability to build and distribute custom reports for sharing across multiple departments 
•    Ability to automate common analytical workflows (average weekday, Saturday, and Sunday ridership, for example), including trend analysis and geographical mapping. 
•    Ability to manage raw data processing into dashboards by route, line and direction and combine this analysis with on-time performance (OTP) to recommend scheduling adjustments. 
•    Ability to schedule proactive notifications when custom ridership events are detected. 
•    This would be for planned and unplanned events. 
•    Ability to combine ridership data and stop amenities data, allowing users to filter stops by amenity type and ridership data performance. 
•    Ability to have a strong application programming interface (API) to power all custom analysis. 
•    Produce an integrated layer builder to analyze ridership patterns directly on a map, like transit centers, short- and long-term construction zones, and route detours, etc. 
•    Ability to integrate vehicle data, OTP, APC, dispatcher information, and NTD certification in one platform. 
•    Final month ridership reporting will need to be complete no later than the fifth business day of the following month.
2. APC data analysis:
•    Ability to accurately match APC data with schedule information to include route, stop, and trip details. 
•    Contractor shall not “toss out” any data that does not match up to a schedule and should provide a report by vehicle number for further analysis. 
•    Ability to filter our driver boardings and layover activity. 
•    Ability to provide ridership data at the trip and block level. 
•    Route, trip, and stop levels should all aggregate to the same ridership numbers by mode. 
•    Ability to expand data for modes without full APC coverage and ability to explain methodology for APC recertifications. 
•    Methodology should document all unlinked passenger trips (UPT) and passenger miles traveled (PMT) factoring methodology, and provide dart with the ability to audit and replicate factors internally. 
•    Ability to ensure an accuracy level no less than 95 percent for both unlinked passenger trips (UPT) and passenger miles traveled (PMT) as defined by the national transit database. 
•    Ability to analyze ridership across multiple options, including dates and time, routes, stops, trips, blocks, geography, etc. 
•    Ability to produce a dashboard that allows dart to drill down to route, trip level, or stop level in specific areas for further detailed analysis. 
•    Ability to identify inefficiencies at the micro level. 
•    Ability to assess the impact of service changes using historical data. 
•    Ability to provide dart with visualization tools to filter ridership data by graphical and geospatial analyses. 
•    Ability to calculate KPI’s such as ridership per hour and passenger miles traveled. 
•    Ability to upload customer shapefiles so ridership can be grouped and analyzed by member and nonmember city. 
•    Ability to calculate “loads” and “load factors” by route and by trip.
•    Ability to take OTP and ridership by route level and make recommendations for improved ridership by combining these two elements using one platform.
- Upgrade or update "dart data analytic" software
•    Provide dart with the latest versions of APC reporting tools and ensure correct operation for each user. 
•    All existing reports relevant to bus ridership and hardware diagnostics. 
•    Future changes in the structure of reports; dart-planning will provide the list and the structure for each report. 
•    Adding new reports relevant to ridership. 
•    As a result of the ever-changing nature of ridership reports, new reports shall be added to all reporting tools.

- Questions/Inquires Deadline: January 6, 2026