Lawrence Transit Vehicles - Transit Vehicle Functionality

Subsystem Description

The Transit Vehicle Subsystem (TRVS) resides in a transit vehicle and provides the sensory, processing, storage, and communications functions necessary to support safe and efficient movement of passengers. The types of transit vehicles containing this subsystem include buses, paratransit vehicles, light rail vehicles, other vehicles designed to carry passengers, and supervisory vehicles. The subsystem collects accurate ridership levels and supports electronic fare collection. The subsystem supports a traffic signal prioritization function that communicates with the roadside subsystem to improve on-schedule performance. Automated vehicle location functions enhance the information available to the Transit Management Subsystem enabling more efficient operations. On-board sensors support transit vehicle maintenance. The subsystem supports on-board security and safety monitoring. This monitoring includes transit user or vehicle operator activated alarms (silent or audible), as well as surveillance and sensor equipment. The surveillance equipment includes video (e.g. CCTV cameras), audio systems and/or event recorder systems. The sensor equipment includes threat sensors (e.g. chemical agent, toxic industrial chemical, biological, explosives, and radiological sensors) and object detection sensors (e.g. metal detectors). In addition, the subsystem supports vehicle operator authentication prior to operation of the vehicle and remote vehicle disabling. The subsystem also furnishes travelers with real-time travel information, continuously updated schedules, transfer options, routes, and fares.

Functional Area: On-board Maintenance

On-board systems to collect and process transit vehicle maintenance data including mileage and vehicle operating conditions for use in scheduling future vehicle maintenance.

IDRequirementStatus
1The transit vehicle shall collect and process vehicle mileage data available to sensors on-board.Medium-term
2The transit vehicle shall collect and process the transit vehicle's operating conditions such as engine temperature, oil pressure, brake wear, internal lighting, environmental controls, etc.Medium-term
3The transit vehicle shall transmit vehicle maintenance data to the center to be used for scheduling future vehicle maintenance.Medium-term

Functional Area: On-board Paratransit Operations

On-board systems to manage paratransit and flexible-route dispatch requests, including multi-stop runs. Passenger data is collected and provided to the center.

IDRequirementStatus
2The transit vehicle shall receive the status of demand responsive or flexible-route transit schedules and passenger loading from the transit vehicle operator.Existing
4The transit vehicle shall provide the capability to log passenger boardings and alightings and make passenger use data available to the transit center.Existing

Functional Area: On-board Passenger Counting

On-board systems collect transit vehicle loading data and make it available to the center.

IDRequirementStatus
1The transit vehicle shall count passengers boarding and alighting.Medium-term
2The passenger counts shall be related to location to support association of passenger counts with routes, route segments, or bus stops.Medium-term
3The passenger counts shall be timestamped so that ridership can be measured by time of day and day of week.Medium-term
4The transit vehicle shall send the collected passenger count information to the transit center.Medium-term

Functional Area: On-board Schedule Management

Collecting of data for schedule generation and adjustment on-board a transit vehicle. Supports communication between the vehicle, operator, and center.

IDRequirementStatus
1The transit vehicle shall receive a vehicle assignment including transit route information, transit service instructions, traffic information, road conditions, and other information for the operator.Existing
2The transit vehicle shall use the route information and its current location to determine the deviation from the predetermined schedule.Existing
3The transit vehicle shall calculate the estimated times of arrival (ETA) at transit stops.Existing
4The transit vehicle shall determine scenarios to correct the schedule deviation.Medium-term
5The transit vehicle shall provide the schedule deviations and instructions for schedule corrections to the transit vehicle operator if the deviation is small, or the transit vehicle is operating in an urban area.Medium-term
6The transit vehicle shall send the schedule deviation and estimated arrival time information to the center.Existing
7The transit vehicle shall support the operations of a flexible route service. This may include requests for route deviations that would then lead to schedule corrective actions.Medium-term
8The transit vehicle shall notify the transit center of vehicle location and operational status as the vehicle exits and returns to the transit facility to support future vehicle assignments.Existing

Functional Area: On-board Transit Fare Management

On-board systems provide fare collection using a travelers non-monetary fare medium. Collected fare data are made available to the center.

IDRequirementStatus
1The transit vehicle shall read data from the traveler card / payment instrument presented by boarding passengers.Existing
2The transit vehicle shall provide an image of all travelers which shall be used for violation processing of those who do not have a traveler card / payment instrument or whose transit fare transaction fails.Existing
3The transit vehicle shall determine the traveler's travel routing based on the transit vehicle's current location and the traveler's destination.Existing
4The transit vehicle shall calculate the traveler's fare based on the origin and destination provided by the traveler as well as factors such as the transit routing, transit fare category, traveler history, and route-specific information.Existing
5The transit vehicle shall have access to the complete range of transit services (routes and schedules) that are available to the traveler.Existing
6The transit vehicle shall provide a transit fare payment interface that is suitable for travelers with physical disabilities.Existing
7The transit vehicle shall include a database on-board the transit vehicle for use in fare processing from which the fares for all possible trips within the transit operational network can be determined.Medium-term
8The transit vehicle shall support an emergency fare structure overriding all other fares that can be activated during disasters, states of emergency or evacuations.Existing
9The transit vehicle shall support the support advanced payments for tolls, and/or parking lot charges, and/or transit fares via the traveler card / payment instrument.Medium-term
10The transit vehicle shall provide fare statistics data to the center.Medium-term

Functional Area: On-board Transit Security

On-board video/audio surveillance systems, threat sensors, and object detection sensors to enhance security and safety on-board a transit vehicles. Also includes silent alarms activated by transit user or vehicle operator, operator authentication, and remote vehicle disabling.

IDRequirementStatus
1The transit vehicle shall perform video and audio surveillance inside of transit vehicles and output raw video or audio data for either local monitoring (for processing or direct output to the transit vehicle operator), remote monitoring or for local storage (e.g., in an event recorder).Existing
3The transit vehicle shall output an indication of potential incidents or threats and the processed video or audio information to the center along with the vehicle’s current location.Existing
6The transit vehicle shall output an indication of potential incidents or threats and the processed sensor information to the center along with the vehicle’s current location.Existing
8The transit vehicle shall monitor and output surveillance and sensor equipment status and fault indications.Existing
9The transit vehicle shall accept emergency inputs from either the transit vehicle operator or a traveler through such interfaces as panic buttons, silent or audible alarms, etc.Existing
10The transit vehicle shall output reported emergencies to the center.Existing
11The transit vehicle shall receive acknowledgments of the emergency request from the center and output this acknowledgment to the transit vehicle operator or to the travelers.Existing
12The transit vehicle shall be capable of receiving an emergency message for broadcast to the travelers or to the transit vehicle operator.Existing

Functional Area: On-board Transit Signal Priority

On-board systems request signal priority through short range communication directly with traffic control equipment at the roadside (intersections, ramps, interchanges, etc.).

IDRequirementStatus
1The transit vehicle shall determine the schedule deviation and estimated times of arrival (ETA) at transit stops.Medium-term
2The transit vehicle shall send priority requests to traffic signal controllers at intersections, pedestrian crossings, and multimodal crossings on the roads (surface streets) and freeway (ramp controls) network that enable a transit vehicle schedule deviation to be corrected.Medium-term
3The transit vehicle shall send the schedule deviation data and status of priority requests to the transit vehicle operator and provide the capability for the transit vehicle operator to control the priority system.Medium-term
4The transit vehicle shall prevent a priority request from being sent when the transit vehicle cannot use the priority (e.g., when the transit vehicle makes a passenger stop on the approach to an intersection).Medium-term

Functional Area: On-board Transit Trip Monitoring

Support fleet management with automatic vehicle location (AVL) and automated mileage and fuel reporting and auditing.

IDRequirementStatus
1The transit vehicle shall track the current location of the transit vehicle.Existing
3The transit vehicle shall record transit trip monitoring data including vehicle mileage and fuel usage.Existing