26-8704_Solicitation.pdf
PDF 557 KB Posted
- Solicitation number
- 26-8704
- Issued by
- Collier County, Florida
About this file
This Request for Proposals (RFP) is issued by Collier County Board of County Commissioners Procurement Services Division on behalf of the Fiscal and Public Transportation and Services Division to procure a fully automated, real-time paratransit dispatch and monitoring software solution. The software system must combine Geographic Information Systems (GIS) based route mapping with trip reservation, scheduling, and route generation capabilities to support the CATconnect paratransit system, which currently provides approximately 125,000 annual passenger trips as a door-to-door service for eligible residents and visitors. The solution must support a minimum of 48 revenue vehicles with scalability for fleet growth and achieve performance targets of 90% on-time performance and 2.0 passengers per revenue hour. A non-mandatory pre-proposal conference is scheduled for November 10, 2026, at 11:00 AM in Naples, Florida, with virtual attendance options available. Proposals are due on December 10, 2026, at 3:00 PM via the Collier County Procurement Services Division Online Bidding System. The County intends to award to a single vendor under a six-year base contract term with two optional one-year renewal periods, with all pricing to remain firm for the full contract term.
The pricing proposal must be completed on the 26-8704 Price Proposal Form with detailed cost justifications covering software hosting, dispatch and reservations licensing, scheduling and reports, interactive voice response system, passenger portal and mobile application, payment solution, operator mobile application, implementation costs, data conversion, training, and one year of maintenance and technical support. Historically, County departments have spent approximately $60,000 annually, though this may not be indicative of future costs. Implementation must be completed, tested, debugged, and fully operational within 12 months of purchase order issuance. The vendor must be responsible and responsive, demonstrating proven success on similar projects and possessing requisite business integrity and financial capability. No set-asides are identified in the solicitation. The evaluation criteria comprise business plan (30 points), cost of services (20 points), experience and capacity of firm (35 points), specialized expertise of team members (15 points), and cover letter/management summary (0 points). Proposals should not exceed 170 pages and must address all evaluation criteria in the specified order to avoid non-responsiveness determination.
View the file
Other files
Show all 13
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
COLLIER COUNTY
BOARD OF COUNTY COMMISSIONERS
REQUEST FOR PROPOSALS (RFP)
GRANT FUNDED
FOR
PARATRANSIT DISPATCH AND MONITORING SOFTWARE
SOLICITATION NO.: 26-8704
HANNAH JONES, PROCUREMENT STRATEGIST, II
PROCUREMENT SERVICES DIVISION
3295 TAMIAMI TRAIL EAST, BLDG C-2
NAPLES, FLORIDA 34112
TELEPHONE: (239) 252-1306
Hannah.Jones@collier.gov (Email)
SOLICITATION PUBLIC NOTICE
REQUEST FOR PROPOSALS
(RFP) NUMBER:
26-8704
PROJECT TITLE: PARATRANSIT DISPATCH AND MONITORING SOFTWARE
NON-MANDATORY PRE-
PROPOSAL CONFERENCE:
TUESDAY NOVEMBER 10, 2026 AT 11:00AM
LOCATION: PROCUREMENT SERVICES DIVISION, CONFERENCE ROOM
A, 3295 TAMIAMI TRAIL EAST, BLDG C-2, NAPLES, FLORIDA
34112
FOR VIRTUAL ATTENDANCE SEE LINK IN OPENGOV
DUE DATE: THURSDAY DECEMBER 10, 2026, at 3:00 PM
PLACE OF RFP OPENING: PROCUREMENT SERVICES DIVISION
3295 TAMIAMI TRAIL EAST, BLDG C-2
NAPLES, FL 34112
All proposals shall be submitted online via the Collier County Procurement Services Division Online Bidding System: https://procurement.opengov.com/portal/collier-county-fl.
INTRODUCTION
As requested by the Fiscal and Public Transportation and Services Division (hereinafter, the “Division or Department or FPTSD”), the Collier County Board of County Commissioners Procurement Services Division (hereinafter, “County”) has issued this Request for Proposals (hereinafter, “RFP”) with the intent of obtaining proposals from interested and qualified Proposers in accordance with the terms, conditions and specifications stated herein, in the Solicitation and/or attachments. The Proposers, at a minimum, must achieve the requirements of the Specifications, Scope of Services, or Scope of Work stated herein. All references to “Proposer” are also referred to as “Consultant,” “Firm,” “Offeror,” “Contractor,” and “Vendor.”
The purpose of this RFP is to purchase a fully automated, real-time, batch order taking, scheduling, and dispatching software solution that will schedule standard paratransit demand response trips. The solution will combine Geographic Information Systems (GIS) based route mapping tools with trip reservation, schedule, and route generation.
Historically, County departments have spent approximately $60,000.00 annually; however, this may not be indicative of future buying patterns.
BACKGROUND
Collier County Fiscal and Public Transportation and Services Division administers the Paratransit system, known as CATconnect (hereinafter, “CAT”), for Collier County. CAT currently provides approximately 125,000 annual passenger trips as a door-to-door service for residents and visitors who do not have access to any other transportation, including the Fixed Route system. The CAT program provides transportation service for eligible individuals through several funding programs, including the Federal Transit Administration (FTA) and the Florida Commissions for the Transportation Disadvantaged (FCTD). CAT can be used for medical appointments, work, school and other trips depending on the funding program the individual qualifies under.
The County is the designated Community Transportation Coordinator (CTC) under Florida Statute Chapter 427. As the CTC, the Fiscal and Public Transportation and Services Division administers the coordination of transportation services for the disabled and economically disadvantaged throughout the entire County, including the City of Naples, Marco Island, Immokalee and Everglades City.
Currently all trips require reservation at least the day before the intended trip although trips may be scheduled up to two (2) weeks in advance. Standing order (recurring) trips can also be established when a customer regularly travels to and from the same destination two or more times a week at the same time. Passengers may be accompanied by a personal care attendant (PCA) or guest. Many passengers travel with wheelchairs or other mobility devices; some may require a service animal or other special considerations for their travel.
Fares range from $1.00 to $5.00 per trip. All passengers and their guests must pay the applicable fare. The program has policies for when a passenger is “Ready early”, “Will-call”, “Cancelations” and “no-shows”. The service operates https://procurement.opengov.com/portal/collier-county-fl under a “Negotiated Trip” system whereby if the exact time a passenger would like to travel is not available, Customer Service may offer options available for travel time.
CAT is constantly seeking new ways to serve its customers, create partnerships and the utilization of new products and technology to enhance the service. Intelligent Transportation System (ITS) applications can offer great opportunities for CAT to improve existing products and services, for the convenience of the customer.
AWARD AND TERM OF AGREEMENT
Collier County reserves the right to select one, or more than one Proposers for award as deemed the best value to the County; however, it is the intent to:
• Single awardee
The agreement term is intended to be for six (6) years with two (2) one (1) year renewal options. Prices put forth in the pricing sheet shall remain firm for the full term of this contract.
DETAILED SCOPE OF WORK
The purpose of this RFP is to purchase a fully automated, real-time, batch order taking, scheduling, and dispatching software solution that will schedule standard paratransit demand response trips. The solution will combine GIS based route mapping tools with trip reservation, schedule, and route generation.
A prerequisite for award is that the offeror must be responsible and must submit a responsive offer. To be responsible means the offeror has the requisite business integrity, as well as financial and organizational capabilities, to ensure good-faith performance and has demonstrated proven success performing projects that are similar in size, scope and complexity. To be responsive an offer must conform to the evaluation criteria described in this RFP including but not limited to all stated requirements and cost information being included in the 26-8704 Price Proposal Form.
Technical Specifications
Improve the efficiency and effectiveness (On-Time Performance and Passengers per Revenue Hour) of CAT’s demand response transportation services. The County seeks to achieve a minimum On-Time Performance of 90% and 2.0 Passengers per Revenue Hour through the acquisition and implementation of a centralized, cloud-based scheduling and dispatching software solution supporting no fewer than 48 revenue vehicles, with the capability to scale as fleet size grows.
The proposed software system and mobile application (described herein) must substantially enhance the agency’s capabilities to manage customer records, generate optimized schedules, and eliminate reliance on manual schedule production. The proposed solution must reduce manual data duplication, increase the accuracy of statistical reporting, reduce no-shows and same-day cancellations, provide dispatchers with proactive tools to manage service delivery in real time, support enhanced billing functionality, and deliver management with greater oversight and visibility into daily operations.
Scheduling and Dispatching Software Systems – Technical Specifications
The successful software solution will contain the following elements:
Client Database
A. Transition Plan The proposer will describe the proposed plan for transitioning data points from the current paratransit software to the new implementations. The selected Vendor will describe what data sets will be transitioning to the new system. Database Attributes at a minimum shall be capable of providing a full range of data elements for each client in the system. Information shall include full identification including gender, address, contact details, third party/emergency contacts, disability status, mobility aides used, required accommodations, caregiver, language spoken by client, program affiliation, and third-party contract payee options. Additionally, System will permit assignment of various demographic codes, such as elderly, youth, etc. System will be capable of tracking trip purpose for each trip with customization possible in terms of defining various trip purposes.. The Vendor will be responsible for providing a fully functional client database functionality file suitable to transit system needs.
B. Customer Look-Up
The customer database shall provide functionality to allow customer service agents to readily look-up client records for editing, trip-booking, etc. Search capabilities should be based on customer name, and identification number, or similar characteristics. When looking up a customer, auto-complete features are desirable to minimize user input.
C. New Client Entry/Customer Edits System will be capable of registering new clients, capturing information about addresses, disability type, space requirement, load/unload time, fares, payment options, eligibility conditions, funding sources, etc. while a customer service agent has the new customer on the telephone.
System will permit editing of all fields in a customer record in a real-time basis and will permit suspensions (temporary) of service. System will have the option to identify what kind of service, (American Disability Act or Transportation Disadvantage) based on the new customer’s address and don’t have access to one of our fixed route options.
D. Client Details
System will be capable of recording and displaying trip history details specific to each client, such as recent trip dates, trip origins, or trip destinations.
System must have the ability to capture information on trip cancellations and no-shows specific to individual customers.
E. Letter/Label Utility.
The system will allow for automatic and manual letter generation (e.g., approval, denial, recertification)
F. Certification Date/Expiration Date.
The system shall allow entry of a certification date defining when the client is authorized to begin receiving service. Because some clients have temporary eligibility, the system must also allow entry of a certification expiration date. Certification and expiration dates must be capable of being specified separately for specific funding sources. Eligibility expiration dates must prevent the reservation on trips outside of the expiration date parameters.
G. GIS and Mapping Functions - General
CAT requires that vendor offerings provide GIS functionality in the software product offered. Mapping capabilities and the dispatcher’s abilities to identify approximate current locations, based on last known point in the schedule, is essential.
H. Service Area
CAT requires that the service area boundary be readily identifiable and graphic, or query functionality must be present to determine if requested trip origins and destinations are within the service area. Fixed Route data must be easily uploaded into the system, addresses shall be associated to routes within the American Disability Act (ADA) corridor when applicable.
I. GIS Functionality
The software must incorporate GIS capabilities and allow user access to map views of the service area; individual routes or runs, and/or bus stops; specific street address; or other specified user-defined zoom levels. Panning/Zoning must be incorporated into the mapping capabilities.
In addition to providing support to the software’s primary scheduling and customer information functions, the GIS functionality of the proposed software must support other GIS analyses. The software must be capable of:
• printing/producing camera ready printed output
• providing geographically based query functions
J. Export of Map Data
System must be capable of exporting data and graphic images to other software platforms. If the software is limited to basic mapping functions, then data must be exportable to standard GIS software (e.g., Environmental Systems Research Institute (ESRI) mapping products) enabling external GIS analyses. The system must be capable of printing maps to system printers or other devices (plotters, etc.).
K. Map Features and Attributes
Access to maps must be seamless from within the scheduling software (e.g., users should be able to generate maps with single mouse click or menu selection). Base maps must contain current attributes on street segments, addressing, speed limits, etc. Vendor shall be responsible for supplying a fully up-to-date map complete with all attributes necessary for point-to-point scheduling using street level routing geography (not zones). Street network shall permit definition of segment characteristics, such as speed limits, one-way direction, etc.
System shall provide methods of allowing user editing of the base map to add new streets, change municipal boundaries, define incomplete address ranges, etc.
GIS functionality shall include:
• ability to develop overlays or coverages of municipal boundaries and other key geographies.
• ability to define service-based zones, such as fare zones, etc.
This is critical functionality that must be provided. Systems shall permit definition and display of physical features that act as barriers to transportation. System shall be capable of defining and displaying point files, indicating system time points, bus stops, major intersections, major transfer points, and major destinations of travel, or other points of interest.
L. Geocoding
Service area map shall contain definitions of street segment name and address ranges. System shall have full geocoding capability allowing CAT to enter an address and locate the address on the map.
System shall be capable of handling various abbreviations of names (e.g., St. for Street, etc.) in the geocoding process.
System shall permit manual assignment of x- and y- coordinates in the event an address cannot be geocoded based on existing map address range attributes.
M. Distance Computation
Systems shall have the capability to use street level GIS map data speed to calculate driving and length duration during the scheduling process as well as the capability to use the street GIS level map data to identify one-way street information while calculating drive length and duration.
N. Graphical Display of Trips/Tour
For any trip reservation, system shall be capable of providing, using the GIS capabilities of the software, a map image of the trip origin and/or destination. Trip data shall be compatible for viewing and integration on Google Earth applications.
Trip Reservations
A. Real Time Trip Details Entry
System shall permit trip booking while transit personnel are on the phone with the client/customer.
System must be capable of processing both subscription (standing order) and demand response trips in this manner. System shall be capable of processing, scheduling and dispatching same day trip orders without the need to manual intervention from users. System shall permit the necessary tools to negotiate the trip based on our guidelines during the time of reservation. System shall permit reservation staff to access client records by entering client’s last name, telephone number, or other ID number. Typical protocols involve booking trips using client’s last name. Additional details must be available to the customer service agent in order to distinguish between customers with the same last name. System will have the capability to automatically populate the reservation screen with the customer data, including commonly used locations, mobility device, eligibility, PCA, etc. after the individual has been identified. Pop-up windows or list boxes shall be used to display lists of clients for easy access and selection. Once selected, pertinent data from the client database file shall be accessible to the reservation clerk, either through on-screen display or pop-up window.
B. Default and Common Pick-Up Address
System shall default to the client’s home address as the pick-up location. System shall provide ability to enter alternative addresses through key stroke entry or through use of list boxes of alternative pick-up addresses associated with that client (e.g., common travel destinations of that customer).
C. Client Trip Destinations
System shall be capable of displaying, through pop-up window, list box, or similar alternative, a list of most frequent client travel destinations and/or recent destinations of travel for easy insertion into the destination field. User must be able to select destination from these fields and populate trip destination fields through this selection process. System shall have the capability of creating one-way trip, round trip or multiple destinations from the same reservation screen, but with different confirmation number for each leg of the trip.
D. Trip Reversals
System shall be capable of automatically generating trip reversals or booking the return trip from the originating trip destination to trip origin.
E. Short term re-occurring trips/duplication System shall be capable of scheduling multiple trips within a week period and/or duplicate recently booked trips.
F. Pick-Up Time, Appointment Time, and Allowances
System shall be capable of scheduling based on requested pick-up time or customer appointment time and shall take into account appropriate travel time to ensure on-time arrival at a destination.
System shall be capable of incorporating a user-specified policy on pick-up time negotiation with the client. System must be capable of incorporating multiple policies.
G. Advance Reservations
System shall be capable of accepting trip reservations for a period of at least up to 14 days in advance of the requested trip date.
H. Standing Order Trip Entry System shall be capable of accepting standing orders. System shall permit day of the week type travel dates and monthly calendar-based travel dates, (e.g., first and third Wednesday of each month). System shall be capable of setting finite limits on the length of subscription orders. Systems shall permit transit personnel to “turn off,” on a temporary basis, a client’s standing order. System shall permit entry of both a start date and end date of the time period when the client will not take the standing order trip.
I. Trip Reservation Editing
System must provide means for a customer service representative to easily and quickly access existing trip reservations for the client in order to edit travel destination, trip dates, and/or travel times. System must permit cancellation of any trip in the system in advance consistent with defined system policies on trip cancellations. System must maintain a cancellation record, by client, to facilitate system management of sanctions for excessive customer abuse of cancellation policies.
J. Suspended Service
System must be capable of temporarily suspending a client’s eligibility for service. System must permit entry of both a start date and end date of the time period when the client’s ridership privileges are suspended. During this period, system must not permit trip booking. System must have provisions, in the event an individual customer’s service is temporarily or permanently suspended, to display a warning alert or physically block a reservation agent from booking a suspended client’s trip.
K. Personal Care Attendants, Companions, and Escorts
System must be capable, during the course of the reservation entry process, of allowing customer service agents to add personal care attendants and companions to the trip order.
L. Fare Computation
System, at the conclusion of trip booking, must provide a confirmation of the booking with fare(s), if applicable, to be paid by the user(s), escorts, or companion. System should give dispatch the capability to mark if a passenger paid one-way, round trip or multiple trips either at pick up or at the end of their trip.
M. Trip Cancellation System must provide methods to enable customer service agents to easily retrieve an existing trip reservation and, upon customer request, cancel the reservation. System must provide various trip codes to document the reason for the cancellation (e.g., “cancelled on customer request” etc.).
N. Group Trip Bookings
System must allow the call taker to designate any completed trip booking as a group booking (e.g., a trip for a group of two or more individuals travelling to a common destination that will be scheduled, as a matter of system policy, to the same run) and then add or delete individual clients from the group booking.
Scheduling
System must have capability to perform fully automated scheduling, either in batch mode or the scheduling of individual trips. The system must provide the scheduler with web-based tools to proactively manage productivity (passengers per hour, trips per hour). The scheduling process must be completely automated and have a proven capability to function without a scheduling position initiating the scheduling. The automated scheduling process must continuously look to improve schedules based on real time operating factors such as cancellations, no-shows, vehicles positions, driver performance, etc.
A. Automated Batch Scheduling System must be capable of scheduling, in batch mode on a next-day basis as well as 14 day in advance, all reservations for a designated travel day. Scheduling must be based on the actual street network in the service area (e.g., actual x- and y- coordinates, not zones), parameters associated with network segments as established in the GIS system, physical barriers, speed parameters, time of day, and appropriate dwell times for the boarding and alighting of passengers.
B. Subscription Trips
System must permit the establishment of base runs or subscription templates based on existing standing orders. System must be capable of evaluating base runs in order to optimize run in terms of least distance and travel time, based on network factors.
C. Unscheduled Trips
System must permit trips to be placed in the system schedule but remain unassigned to a specific run through a user manual setting of the trip to “unassigned” or “will-call” category or similar means. The System must also be capable of permitting manual insertion of such trips into the schedule, with automatic dynamic updating of the remaining scheduled pick- ups and drop-offs on the run.
D. Same Day Trip Orders
System must be capable of taking trip orders on a same day basis and dynamically scheduling the trip into existing schedules. System must consider existing path of route travel, existing customer assigned trips, and system policies on travel and pick up time windows in making the scheduling assignment. If system is capable of producing multiple solutions to the trip assignment, priorities, expressed on some type of score or other method, it shall show the best possible choice of assignment as the default selection. When a same day order is accepted and assigned to a run (or unassigned run is assigned to a run), it is imperative that the system shall be capable of dynamically updating the remaining scheduled pick-ups and drop-offs on the run’s schedule. System shall allow the scheduling of trips for a route-deviation service.
E. Service Zones
System shall be capable of producing schedules, by run, in chronological order or by sequential run number, indicating projected arrival time of system vehicles at each origin and destination.
Schedules must be developed on zones or counties, based on user specified service zones. System must be capable of recognizing geographic zones and assign trips to the proper zone when systems serve multiple counties with dedicated vehicles and staff.
F. Display
Once generated, system shall be able to display all schedules for all runs on a given day. Display shall contain all pertinent run data and contain necessary menu and edit tools to provide manual adjustments, as necessary, to the scheduled runs. If any manual adjustments are made, dispatchers should be notified of the changes.
G. Validation/Violations
System shall have internal validation controls to ensure that schedules do not violate schedule and work rules. Additionally, system shall have capacity to evaluate overall travel time for individual passengers to ensure that system travel time limitations are not exceeded. System shall be capable of generating or identifying trips that violate system parameters so that staff can attempt to remedy the violation.
H. Manual Override
System shall provide the capability of scheduling staff to manually move trips after schedule development. When such overrides are made, the system shall record and timestamp the override action in the trip record (or in an associated database) in order to provide a historical account of changes to the original (booked) reservation.
I. Labor Rules
System shall be capable of scheduling trips to established runs taking into account system labor rules on work hours, breaks, and employee work hours.
J. Vehicle Assignment
In assigning passengers to vehicles and/or vehicles to system runs, system shall be capable of recognizing the need for accessible vehicles, vehicle capacity, etc., in making said assignments.
System shall have the capability of assigning vehicles to zones or counties. They system shall prevent double booking of vehicle to run scheduling.
Vehicles shall be allowed to be assigned runs for next day service without impacting day of service.
Runs shall be assigned to vehicles in advance, a minimum of one day, and schedule trips to the run.
K. Editing Schedules
System shall be capable of adding trips to a previously generated schedules or re-assigning trips from one run to another in dynamic fashion. System shall be capable of evaluating individual trip parameters and select runs that best satisfy the requirements of the reservation while maintaining the integrity of existing reservations on the same run. If system generates a range of alternatives, system shall present alternatives in rank order with the highest ranked alternative indicating the “best” selection. The best selection will be chosen based on vehicle Global Positioning System (GPS) of current vehicles on the road (in the case of same day trips) and the information of other trips currently within the schedule for the time that the trip in question is being booked.
L. Dynamic Update of All Schedules
Anytime a schedule is edited, the system must be capable of updating the schedules of all other impacted trips so all previously scheduled trips must remain on time, not violate travel time rules, etc. The scheduling process must be completely automated and have the capability to function without a scheduling position initiating the scheduled. The automated scheduling process must continuously be looking to improve schedules based on real time operating factors such as cancellations, no-shows, vehicles positions or driver performance. The system must optimize same day trip orders with advance trip orders and automatically send updates to the Operator Mobile Application .
M. Unscheduled Trips If the system cannot schedule all orders for the day of travel being scheduled, then the system shall be capable of displaying all such trips in its own dataset so that staff may consider manual overrides to the schedule and/or assignment of the trip.
N. GIS Display of Schedules
Once trips are assigned to a scheduled run, the system shall be capable of graphically displaying, on the GIS system, the sequence of pick-ups, drop-offs, and route path for the run.
O. Manifests
The system shall produce a daily manifest for each run, indicating pull-in and pull-out times, the projected arrival time of CAT vehicle at each pick-up and drop-off location, and listing the trip events in chronological order.
P. Runs The system shall allow runs to be created and assigned to vehicles. Run start and end times shall be manually adjustable and capable of being locked. Schedule optimization shall not modify these locked times. The assignment of runs to vehicles shall also support the allocation of deadhead time and pre‑trip time.
Dispatching
A. Access to Dispatch Information Systems shall allow dispatchers access to run itineraries based on run number, vehicle number, drivers name, or client name. System shall be capable of displaying the run number, number of passengers on the run, scheduled arrival time, estimated time of arrival and any special circumstances. Information displays must associate with the time of day (e.g., 10:00 a.m. events are displayed at the top of the list window when the dispatcher makes queries at 10:00 a.m.). System shall allow the dispatchers and supervisors to monitor On Time Performance (OTP), no-shows, cancellations, subscriptions and late trips. The system shall automatically send updates of the dispatched trips to the MDT’s. The web-based tools provided will allow managers/supervisors to monitor their driver’s performance on real-time. The system shall optimize same day trip orders with advance trip orders and automatically send updates to the MDTs. The system shall have the capability to automatically notify drivers of special needs for a particular passenger and provide a method for the drivers to acknowledge the alert/information has been received in order to execute the trip. The scheduling process shall be completely automated and have a proven capability to function without a scheduling position initiating the scheduling. The automated scheduling process shall continuously look to improve live schedules based on real time operating factors such as cancellations, no-shows, vehicles positions, driver performance, etc.
B. Driver Assignment
System shall be capable of assigning drivers to runs. System shall take into account driver work schedules, qualifications, and other factors to ensure compliance with system policies.
C. Vehicle Assignment
System shall be capable of assigning vehicles to scheduled runs taking into account mobility needs of customers assigned to the run, thereby always ensuring sufficient wheelchair capacity. Dynamic updating of assigned vehicles must be possible in order to take into account vehicles pulled from service due to mechanical failure, lift failure, or other failure event found during the driver’s pre-trip inspection. If a vehicle must be removed from service, the system shall allow the dispatcher to associate a newly assigned vehicle with the run. If no alternate vehicle is available and the run must be cancelled, the system shall attempt to dynamically reschedule all the affected trips unto existing runs, with priority to any trips that were already underway on the affected vehicle.
D. Cancellations/No-Shows
System shall be capable of allowing dispatchers to process late cancellations (cancellations received after system policy time) and no-shows.
E. Same Day Reservation Changes/Add-Ons
System shall be capable of automatically displaying to the dispatcher/scheduler cancellations, same day reservations, and will-call return trips waiting for vehicle assignment (e.g., trips/reservations made but not yet assigned/scheduled).
F. Removal of Vehicles from Service
If the dispatcher is advised that a vehicle is not fit for service, system shall be capable of programming a vehicle substitution on the affected run(s).
G. Dashboard Access
System shall be capable of allowing dispatchers to summarize and easily address upcoming late trips, and access to OTP data and real time maps of all vehicles.
H. Active Schedule Optimization
The system must include an active schedule optimization capability that continuously evaluates operational conditions, resource availability, task duration changes, and priority adjustments. The system should automatically recommend or apply optimized scheduling adjustments in real time to improve efficiency, minimize conflicts, and maintain service levels. The optimization engine must function without the need for specialized hardware. The system should also provide clear visibility into proposed schedule changes and allow authorized users to accept, modify, or override optimization recommendations.
I. Vehicle Mapping
The system shall be capable of displaying vehicle locations on a map, with location data refreshing every 10 seconds. This should be a live view without need to refresh the screen/data manually.
General
A. Web Interface The solution must be fully web-based and functional on all modern evergreen browsers, including Google Chrome, Microsoft Edge, Mozilla Firefox, and Apple Safari (current and prior major releases).
No proprietary browser plugins, ActiveX controls, or legacy browser dependencies shall be required.
Mobile-responsive design is required for all passenger-facing and supervisor-facing interfaces.
System must be offeror or third-party hosted and may not require hardware or software installation on CAT servers.
B. Online Trip Booking Portal and Eligibility Portal System shall have the capability for our passengers to have a web-based portal for trip booking and eligibility. The trip booking and eligibility portal needs to be Protected Personal Information (HIPPA) Compliant and meet all ADA.
C. System Parameters
System shall have capability for user specified settings that govern the scheduling process (e.g., average speed; dwell times; load times; etc.).
Reporting
A. Standard Reports Software shall be capable of generating a comprehensive range of management and service reports necessary to permit sufficient oversight of the paratransit service. Software shall utilize an open architecture supporting integration with third-party business intelligence (BI) platforms, data warehouses, and analytics tools via documented APIs (RESTful or equivalent). Software must also generate reports that satisfy National Transit Database (NTD) reporting requirements and applicable state reporting mandates. The software system shall support real-time, web-based operational supervision and on-time performance monitoring. All reports shall be fully web-based, executable on demand, and exportable in standard formats including CSV, PDF, Excel, and Word. The system shall also support scheduled report delivery, allowing users to configure specific reports to be automatically generated and delivered to designated email addresses at user-defined intervals (e.g., daily, weekly, monthly), in a user-specified file format.
B. Ad-Hoc Reports
System shall be capable of permitting the user to create, format, and print user- defined reports based on any data element contained in the database.
Operator Mobile Application
The solution must be provided as an Operator Mobile Application capable of running on all modern tablet devices, including iOS, Android, and Windows‑based tablets. The software must not rely on specialized or proprietary hardware to operate. It should be optimized for touch‑based interaction, support offline functionality when applicable, and maintain consistent performance across devices with varying screen sizes and processing capabilities.
Embedded Google Maps or like GPS mapping for reliable up to date addresses able to keep with the ever growing population and community development.
Log-On Functionality
A. Initial Power-On Sequence/ Progression of Manifest Once the MDT/Tablet unit is powered up, it will automatically display a driver log-on form screen requesting the driver’s identification number and the vehicle’s odometer reading. The Operator Mobile Application will display the vehicle’s current odometer reading as calculated. The Operator Mobile Application will allow the driver to manually correct the calculated vehicle odometer value.
B. Driver Log-In
Drivers must be able to log-on to the Operator Mobile Application by entering their employee identification, run number, and/or the vehicle’s odometer reading into the Tablet unit. The Operator Mobile Application will validate the log-on information with the scheduling/dispatch software. Should the driver turn off the ignition during the course of his/her shift for less than 30 minutes, he/she must not be required to logon again as current data will be retained in the Tablet unit.
Display Functionality
A. Basic Functionality All driver screens shall always display the following information:
• Current system time, the time should be able to be depicted by a twenty-four (24) hour clock, or alternatively an AM/PM designation;
• Communication network status; and
• New message indicator.
B. Basic Controls
• Operator Mobile Application will also provide users with the ability to:
• Switch between a “day” mode graphics display and a “night” mode graphics display that have been optimized for the ambient lighting expected under those conditions;
• Adjust volume; and
• Adjust backlighting of display.
Communication Functionality
The Operator Mobile Application shall have, at a minimum, the following communication functionalities:
A. Visual/Audio Alerts
• Provide visual and audible alerts to indicate incoming messages.
• Send a message and notifying the driver of the success or failure of the transaction.
B. Operator Response
The driver must be able to acknowledge incoming messages (as deemed necessary). After the driver acknowledges an incoming message, it shall be displayed on the Operator Mobile Application with the following capabilities:
• Allow the driver to respond to a message. This acknowledgement shall be through use of the units’ function keys.
• Sending a message and notifying the driver of the success or failure of the transaction. The option will be given to the driver to resend the message should the message not be delivered successfully. This sending method is known as “Send and Notify.”
• Restrict access to all functions while the vehicle is in motion. GPS telemetry, current system time, communication network status, and new message indicator may be displayed during vehicle motion.
C. Messages and Message Queue
The Operator Mobile Application must be capable of the following listed:
• Receiving pre-defined messages when a specific numeric code is sent from the host application.
• Queuing messages in a buffer and repeatedly attempting to deliver them to the host application.
Each message shall be configured to attempt delivery indefinitely or to attempt delivery only for a fixed period of time after which the message will be discarded. This sending method is known as “Store and Forward.”
• Sending messages that are sent only once, regardless of whether they are acknowledged. This sending method is known as “Send and Forget,”
• Receiving pre-defined messages when a specific numeric code is sent from the host application.
• Sending a series of “canned” messages that can be user defined by the customer in conjunction with the vendor.
• Requesting the manifest from the server.
Automatic Vehicle Location
A. Communication Protocols The Operator Mobile Application will have an option that will allow Automatic Vehicle Location information to be passed to the server and stored in the database based on automatic refresh rates every 60 seconds or more frequently depending upon the transmission capacity of the communications infrastructure.
B. Navigation Functionality
The Operator Mobile Application shall also have the following capabilities:
• Displaying in-vehicle maps and providing turn list directions.
• Providing navigation directions including voice annunciation and visual display of trip route and turn directions. This process shall be hands-free, and drivers should not have to enter destination address to use the map navigation, as the software will do this automatically.
• Drivers will not have to start the map navigation as a separate software application. The navigation functionality will be integrated into the in-vehicle software application. The Vendor shall provide information on the integrated 3rd party Navigation solution.
• Embedded Google Maps or like GPS mapping for reliable up to date addresses able to keep with the ever growing population and community development.
C. Display Functionality
The Operator Mobile Application shall also have the following capabilities:
• Allow the driver to scroll through the manifest up to the maximum number of transmitted trips as determined by the paratransit operator.
• Adding, updating, and saving new trip data without driver action.
• Provide drivers with a manifest, passenger/trip information and other screen displays that permit performance of other actions.
• Alert driver to changes in manifest via color-coded messages and with an audible tone.
D. Manifest Screens
The Operator Mobile Application Manifest Screen must provide drivers with an overview of their manifest sufficiently detailed to understand trip origins, destinations, times, services and sequence.
• Additional trip message lines must be available by scrolling.
• All trips must be shown on the display in ascending order of estimated stop times. The current trip must be located at the top of the manifest screen.
• When the driver completes the current trip, the Operator Mobile Application shall automatically delete it from the manifest screen. The screen must display multiple rider pick- ups and drop-offs from the same address.
• At any time after the driver has logged on to the system and received a manifest, the Operator Mobile Application shall have capability to dynamically update the manifest by inserting additional trips sent to it by the dispatch system. Trip insertions must also follow the protocol of displaying trips in ascending order of estimated stop time. At any time after the driver has logged on to the system and received a manifest, the Operator Mobile Application shall update the manifest and delete all cancelled trips.
• The driver must be able to access the additional screens that provide additional functionality via single keystrokes, use of function keys, or similar one-stroke methods. Access to additional screens must be restricted while the vehicle is in motion. The driver must also be able to access the passenger/trip information screen from the Manifest Screen by a single keystroke, using a keypad key.
E. Passenger/Trip Information Screen
The MDT/Tablet shall also of the capabilities to do the following:
• Passenger/trip information screen that provides the driver with detailed information about each stop (pick-up or drop-off). If the level of detail in this screen exceeds the visible viewing area of the display screen, additional lines of trip information shall be viewable through use of a scrolling function.
• The driver shall be able to edit trip information by pressing the arrow keys. Vendor should indicate which data elements are editable by the driver; information, at a minimum, should include passenger type, fare, and number of passengers at stop.
• The driver must be able to access the manifest screen from any display screen on the unit via a single touch or keystroke.
• The driver must be able to access additional screens from the detailed passenger trip information screen by a by a single touch or keystroke.
• If the rider and trip numbers, number of riders, attendants and companions, and fare amounts and types were in the original trip message that was transmitted to the MDT/Tablet unit, the MDT/Tablet shall have preformatted screens where this data is automatically populated in the appropriate fields.
• Perform and Arrive functions shall only occur within a proximity of the geocode address.
• The Operator Mobile Application shall enable operators to process fare collection with ease, requiring minimal actions. The fare collection process shall prevent the use of account balances when sufficient funds are not available in the passenger’s account.
F. Other Action Screens
The Operator Mobile Application shall provide additional functionality to permit voiceless communication between vehicle and dispatch.
• Such screens shall display a list of information requests to be completed by the driver and transmitted to system dispatch that are necessary to complete data required for each trip.
• Automatically providing some data, such as odometer reading, and shall be capable of time-stamping all critical events.
• After the driver has used the Operator Mobile Application to record a rider’s boarding, the unit shall issue prompts regarding any other data that needs to be completed by the driver before the driver can return to any other screen.
G. Data Messaging
Predefined Messages: The following types of message traffic shall be supported by the Operator Mobile Application, enabling voiceless communication between driver and dispatch. To the extent feasible, information flow/transmission shall be packaged as pre-defined, enabled by the driver by simple keystrokes or touch screen action. Pre-defined messaging shall be customizable and shall be established, based on consultation between the County and the vendor, prior to installation. Messages shall include, but not necessarily be limited to:
• Driver log-on
• Driver log-off
• Pick-up location arrival
• Pick-up performed
• Drop-off location arrival
• Drop-off performed
• Additional passenger boarding
• Additional passenger alighting
• Rider no-show
• Rider cancels at the door
• Rider not ready within pick-up window
The Operator Mobile Application shall automatically provide odometer reading, timestamp, and coordinate location with the transmission of each of the message types above.
Hardware
CAT shall supply the onboard tablets. Currently Samsung Tablets have been deployed for the use of the mobile application.
Dispatch Interface/GPS/AVL Functionality
In addition to the in-vehicle functionality described above, the Vendor’s technology solution shall provide the following functionality to system dispatch operations:
A. Event Based Reporting When a function is performed, the location of the vehicle shall be reported along with any data relevant to the performance of the particular function.
B. Distance Traveled Reporting Every time the vehicle has moved a predetermined distance the MDT shall automatically report the vehicle’s location to the host system in order to avoid unnecessary reports from vehicles that have not moved from their previously reported positions.
C. Time Elapsed Reporting
Vendor shall indicate the frequency of coordinate reporting, based, in part, upon the transmission capacity of the communications infrastructure, costs, etc. If a report is not received at the specified interval, then the host system shall be alerted to the fact that for one reason or another that vehicle is out of coverage.
D. Hybrid GPS Reporting System may incorporate the advantages of all three of the preceding methods. The requirement of GPS is to receive information ONLY WHEN desired and not waste airtime sending GPS information that is not useful to the dispatch operations.
E. Poll-on-Demand
MDT shall be capable of reporting GPS based on a polling request message from the Host-end Application Software at the dispatch location.
Interactive Voice Response (IVR)
The Vendor shall include a fully dynamic, real-time IVR system with the capabilities of making automated calls the day before and the day of service. The IVR system must integrate with live operational data including GPS vehicle positions, traffic conditions, incident reports, and vehicle breakdown or delay events to deliver accurate, up-to-the-minute passenger notifications rather than static pre-scheduled messages. This real-time responsiveness is a required feature; proposals that do not address dynamic IVR updates based on live operational conditions will not be considered responsive. IVR shall also have the ability to provide the following options or capabilities:
A. The option to configure a personalized message with different prompts. This is the ability to record customized greetings, messages and prompts so that when customers call to have a personalized experience.
B. To have pre-recorded IVR messages. This is to be used if we don’t want to use our own recorded voices, we have the choice/option of using the pre-recorded IVR messages.
C. Ability to collect information about our callers/passengers. This is the ability for the IVR to collect information about the customer’s needs and have the ability to transfer calls to the most appropriate agent or department depending on their IVR input. It is important that the IVR routes the callers/passengers to the most appropriate department or agent that is most qualified to meet their needs.
D. The opportunity for passengers to cancel trips during the night before the call center is open.
E. Be capable of providing real-time call-ahead notifications for day-of service with dynamically updated estimated times of arrival based on current vehicle location, route progress, and traffic conditions.
F. Be capable of automatically triggering outbound passenger notifications when a driver is delayed due to traffic, an accident, a vehicle breakdown, or any other real-time operational disruption, providing the passenger with an updated estimated arrival time.
G. Be capable of Floodgate Messaging, The IVR system shall include a floodgate or systemwide override feature that allows authorized staff to instantly broadcast a single high priority message to all callers and/or affected passengers during emergencies or major service disruptions (such as severe weather, road closures, or flooding). When activated, the floodgate message shall temporarily override regular IVR menus and standard operational notifications, ensuring that critical information is delivered immediately and consistently across all channels until the disruption has been resolved.
Account Based Payment Solution
The Vendor shall include an Account Based payment Solution that is customer facing. This is the ability for customers to have access to a web-based portal to manage payments. The items listed below must be included in the Account Based payment Solution:
A. The ability to be accessed 24/7; on mobile devices as well as any device that can access the web.
B. Customizable recurring billing option. This provides the customer to reload their account, based on the number of trips they take weekly/monthly.
C. A feature that alerts customers/passenger when account balance is low or in the negative to avoid disruption of service.
D. Payment card Information (PCI) certified for enhance payment security.
E. Deduct funds associated with the passenger fare from the account for completed trips.
F. Passengers shall not be allowed to…
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .