Rider Information and Trip Planning Platform Solution

The vendor required to provide rider information and trip planning platform solution must offer mobile (iOS and android) and web access, integrate with existing transit data systems, support agency planning needs, and provide tools for managing live service updates, including detours. 
- Platform requirements
1. Real-time service information
•    Live vehicle tracking with predictive arrival times.
•    Integration with GTFS and GTFS-real-time feeds.
•    Clear presentation of service alerts, disruptions, and stop-level updates.
2. Trip planning
•    Multimodal, real-time trip planner using both scheduled and real-time data.
•    Accessibility-friendly routing and walking connections.
•    Support for bike, pedestrian, and shared mobility options where applicable.
3. Live detour and service change management
•    Ability for agency staff to create and publish detours in real time.
•    Tools to adjust stop-level routing and communicate service changes immediately.
•    Detours reflected in trip planning and rider-facing interfaces.
4. Planning and analytics tools
•    Aggregated, anonymized rider behavior data (e.g., trip planning trends, peak usage).
•    Exportable reports in standard formats (csv, json, etc.).
•    Interactive dashboard with visualizations such as maps, timelines, and usage heatmaps.
•    Filters for date ranges, route-level insights, and event-specific analysis.
5. Customer engagement and communication
•    Push notifications and service alert tools.
•    Rider feedback collection features.
•    Optional modules for conducting rider surveys.
6. Admin portal
•    Centralized, role-based platform for managing alerts, detours, and platform settings.
•    Visual management tools for live service oversight.
•    Full audit trail for updates and changes made by staff.
7. Accessibility and language support
•    WCAG 2.1 aa compliance for all user-facing interfaces.
•    Support for multiple languages.
•    Fully responsive mobile and desktop experience.
8. Integration and future readiness
•    Open API support and compatibility with GTFS and GTFS-rt and other industry standards.
•    Future open API support and compatibility with GTFS-flex and other industry standards, if requested.
•    Architecture that supports future mobile fare payment integration.
•    Optional support for real-time data exchange with 3rd-party systems
9. Security and privacy
•    Compliance with all relevant data privacy laws.
•    Secure data storage, transmission, and user privacy protection.
•    Use of anonymized data wherever possible.

- Contract Period/Term: 3 years
- Pre-Proposal Meeting (Non-Mandatory) Date: November 18, 2025
- Questions/Inquires Deadline: December 2, 2025