Intelligent Transportation System

The vendor is required to provide intelligent transportation system (ITS) to establish a contract for upgrade, purchase and implementation of current state-of-the art ITS technology on city of transit buses.
- Announcements
1. Automated stop announcements
•    System must be able to perform audible and visual announcements of bus stops inside of the bus, as well as audible announcements outside of the bus by way of the exterior speaker 
•    Announcements must be determined to be satisfactory by the association
•    Announcements must be able to be made at a predetermined distance from a bus stop 
•    The distance where the triggered announcement occurs should be variable by bus stop to department preference 
•    Announcements and interior passenger signs must be able to be customized to department preference 
•    Offeror will explain in detail how audio and visual announcements are created, maintained, and changed for the system including who is responsible and capable of making changes to announcements 
•    System should be able to have a procedure that public service announcements, service alerts, and advertisements can be triggered at predetermined locations by department
•    If such a procedure is present, offeror should explain in detail what the procedure is as well as who is responsible and capable of creating the announcements 
•    System should be able to somehow notify the operator that an announcement was not performed 
•    System should allow for the volume of the announcements to be easily adjustable for each vehicle 
•    System should allow for the announcements to be played through all speakers of the bus, including the driver speaker
2. Infotainment
•    System must include infotainment screens for interior of buses. 
•    Screens must be able to provide details on current route progress 
•    Screens must additionally have space for non-route information (such as alerts, announcements, advertisements, etc.) 
•    Screens must display the date or time
- Passenger info
•    A native application for their ITS system for passenger convenience 
•    Application must be available for download in both android and apple stores 
•    An advanced programming interface (API) for third-party development if desired by department
•    The ability to incorporate passenger information signs at bus stops 
•    If the proposed solution does have this capability, explain the following: 
•    The ability to give passengers bus stop arrival information for their route in real-time 
•    Explain in detail how the system makes real-time arrival predictions 
•    Explain the various methods that passengers can use to get arrival information 
•    Information for route layover points should display the departure time instead of the arrival time 
•    The system should have an online tutorial or simple user guide that customers can refer to if they are unsure how to obtain passenger information 
•    Trip planning capability for passengers integrated in a website, so that passengers have one place to plan for a trip and get arrival information 
•    Offeror must explain any third-party tools that are utilized for trip planning (ex. google transit), and work with the agency to ensure that data is updated on the third-party’s interface in a reasonable time
•    Offeror must have the ability to send out service alerts and public service announcements to passengers 
•    Explain the various methods that alerts and announcements can be disseminated to passengers 
•    The system should, upon a customer opening the app, force the customer to acknowledge any general system service alerts 
•    the System app should allow for push notifications to the customer’s mobile device 
•    Offeror should in some way be able to provide a passenger feedback mechanism 
•    explain how passengers can send feedback to department
•    Explain if there is an ability that when a passenger wants to send feedback, the system can autofill some of the relevant information in the feedback form depending on where the user is in the app (ex. a user submitting feedback that is viewing information about route a. 
•    The user submits the feedback, route a’ would be populated without requiring the user to do so, to streamline feedback)
- Driver technology
1. Driver MDT and tablet
•    The time displayed on the MDT and tablet must measure at least one inch wide and one-half inch tall for readability purposes 
•    The time should display in HH: mm: ss format 
•    The MDT and tablet must be able to display schedule adherence to the driver 
•    Schedule adherence must be based by either individual bus stops or by timepoints 
•    department prefers that schedule adherence is performed at each stop 
•    Offeror will explain and illustrate how schedule adherence is displayed and relayed to the driver 
•    The MDT and tablet should have the ability to tally passengers based on the type of passenger.
•    Passenger types should be customizable as necessary 
•    The MDT and tablet should have the capability to perform pre-trip and post-trip inspections 
•    Inspection form should be customizable to the needs of department
•    Inspection form should allow for typed input from the driver to specifically address issues 
•    The system should force a post-trip inspection at the end of the day for the vehicle 
•    Device should be capable of sending inspection reports to email, server, and department third-party fleet management program. 
•    Inspection should be capable of detecting when specific items of the pre-trip and post trip were not executed. (i.e., whether the operator cycled the ramp or not) 
•    Inspection should be capable of verifying the functionality and accuracy of the APCs. 
•    The system should have a notification system via email and etc. to management for any inspections that report issues beyond normal 
•    The MDT and tablet must go to a lockout screen and not be accessible while the bus is in motion
•    department is open to options as to what should be displayed when the screen is locked out, but at a minimum the screen should show a clock, the next stop, and the schedule adherence for the currently assigned route.
2. The MDT and tablet should allow for messaging
•    The MDT and tablet should have the capability for drivers to send canned messages to dispatch, but not driver to driver. 
•    The MDT and tablet should show the health of the installed system on the bus (GPS location, logged into job, etc.) 
•    The offeror must explain whether the MDT and tablet that is proposed is proprietary or not, and explain the reasoning behind it 
•    The MDT and tablet should be a single point of logon for all relevant systems in the bus 
•    The logon procedure should display a list of available runs to log into, and somehow notify and prevent multiple unauthorized logons to the same run 
•    The system should have a way to bypass the pre-trip and post-trip inspection procedure when inspections do not need to be performed, for example tripper buses that have multiple runs performed in a single day. 
•    The MDT and tablet can enable and disable automated vehicle announcements 
•    The MDT and tablet upon logon and logoff of a job can change the exterior passenger head sign 
•    The MDT and tablet should be able to edit passenger counts as necessary 
•    The offeror must have automatic passenger counters that can be deployed as part of the solution 
•    Offeror must explain how the proposed APCs work 
•    Offeror must explain why the proposed APCs will work in an environment where dozens of passengers are boarding and alighting at both doors at each stop 
•    APCs should be able to be national transit database (NTD) certified once installed. 
•    the proposed solution should include head signs that integrate with, at minimum, the MDT to ensure accurate information is being displayed. 
•    A driver enters the job they are driving, the system should change the head sign to reflect that job 
•    The system should determine by bus location when it is necessary to change the head sign, and should do so when the bus travels to the end of the line of a route.
3. Dispatch technology
•    Solution must have a system status screen for dispatchers or managers to be able to view routes and the status of the bus or buses running the routes
o    System must illustrate if buses are off route, off job and etc. 
o    System must show schedule adherence of buses and any system alerts if present 
o    System must enable dispatchers to log buses on and off of jobs if necessary 
o    System should have some sort of alert system to notify the user if a bus goes off route and is speeding not reporting and etc.
•    Solution must be able to show location of buses and bus routes in real time on an interactive map whether a bus is logged into a job or not 
•    System should be able to accommodate detours in the system where routes must be adjusted due to road closures 
•    System should have a yard map, showing available vehicles at the yard 
•    System does not need to provide a covert emergency alarm capability.

- Contract Period/Term: 3 years
- Questions/Inquires Deadline: October 15, 2025