Transit Fixed Route Software Application

The vendor is required to provide the authority with software applications for transit fixed route scheduling and daily operations.
- The applications shall provide fixed-route scheduling and planning including, but not limited to, blocking, run-cutting, costing, rostering, and online bidding and daily operations including operator attendance and pay calculation.
- Software applications that are currently in place are as follows:
• Agency currently utilizes trapeze FX for fixed-route scheduling and trapeze ops for daily fixed-route operations. 
• Agency is currently finishing up implementation of avail technologies CAD/AVL for dispatching, vehicle locating and automated passenger counting. 
• The current contract for the avail system concludes in 2030. 
• Agency human resources management platform is ADP workforce now. 
• Agency utilizes remix planning software for routes planning and initial high level routes evaluation. 
• Currently agency ERP/EAM system is ellipse by Hitachi and this contract agreement expires in 2026. 
• Agency plans to competitively bid this software application system prior to the expiration of the agreement.
- One key functionality agency desires are optimization of resources via the ability to run multiple iterations of blocking, run-cutting, and rostering per user input and editable parameters.
- Demonstrate a compelling, comprehensive, and technically responsive service provided by a firm to support agency goals of cost-effective service planning, quality of life for agency operators, and efficient operation of agency fixed-route transit system.
- Scheduling software functionality
• Provide management and development of service schedules including the ability to build and modify from a database of route patterns, stops, and timetables. 
• Provide a visual mapping interface allowing users to define and view routes, patterns, traces, stops, relief points, break points, and garages. 
• Allow for recording bus stop amenities including shelters, benches, signage, etc. preferably include ability to import photos or other documents into stop records. 
• Allow for regular updates to map data with latest available infrastructure. proposer shall specify the base map system (google, Bing, here, etc.) to be utilized and include any one-time and recurring costs involved in keeping the map data current. 
• Provide all required schedule data to support agency existing avail technologies CAD/AVL system. 
• Proposer must specify the method to be used for providing data to avail, previous experience integrating with avail CAD/AVL systems, and any one-time and/or recurring costs involved in integration with the avail system. 
• Proposed software must be able to import actual runtime and other pertinent data from the avail CAD/AVL system and compare that data to the schedule in order to determine areas of consistent lateness or earliness and provide recommended adjustments to the schedule. 
• Proposer must specify the method to be used for receiving data from avail, previous experience integrating with avail cad/AVL systems, and any one-time and/or recurring costs involved in integration with the avail system. 
• System must provide the ability to define and easily update collective bargaining agreement work rules to be used in the creation of blocks and run-cuts. 
• System must have a user-friendly mechanism for copying a complete schedule or individual pieces (routes, trips, blocks, runs, etc.) from one signup period to another. 
• System must provide warning if copied data will be overwriting existing data.
• System must allow for working independently on multiple signup periods at the same time. 
• System must provide a method for locking a signup period as read-only. 
• Access to the capability to lock and unlock a signup must be limited to certain user roles. 
• Proposed fixed-route scheduling solution must be able to automatically export data to, and be fully Compatible with, the proposed daily operations software solution. 
• proposer must specify the method to be used for providing data to the daily operations software, previous experience integrating with that software, and any one-time and recurring costs involved in integration with that software.
- Route building
• System shall allow users to define routes as a set of points, patterns, and stops in either a tabular or graphical (map-based) manner. 
• System shall allow interactions with the map functions within the software to select point/stop locations and sequentially place them in order in a route table establishing the latitude, longitude, and distance from the previous location. 
• System must allow creation of multiple patterns within one overall route. 
• Patterns may be comprised of one or more segments of the route with user selectable start and end points
• User shall be able to designate any stop along a specific route to serve as a timepoint/node for that route. 
• There shall not be a limit to the number of timepoints allowed on a route or pattern
• System shall provide information including, but not limited to, route length and estimated running time. 
• System shall allow head sign codes to be assigned to individual patterns of a route.
- Contract Period/Term: 2 years
- Non-Mandatory Pre-Proposal Meeting Date: July 18, 2025
- Questions/Inquires Deadline: July 25, 2025