Clovis Transit Round Up Demand Response Transit Vehicle - 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 Connection Protection

Monitors vehicle schedule performance and provides it to the transit center for connection protection processing. Also recognizes travelers who have arranged for connection protection and provides information regarding them to the transit center.

IDRequirementStatus
1The transit vehicle shall monitor vehicle schedule performance and provides it to the transit center for connection protection processing.Existing
2The transit vehicle shall receive operator instructions from the transit center relating to managing connection protection.Existing
3The transit vehicle shall recognizes individual travelers who have arranged for connection protection and provides information regarding them to the transit center.Existing

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.Existing
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.Existing
3The transit vehicle shall transmit vehicle maintenance data to the center to be used for scheduling future vehicle maintenance.Existing

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
1The transit vehicle shall manage data input to sensor(s) on-board a transit vehicle to determine the vehicle's availability for use in demand responsive and flexible-route transit services based on identity, type, and passenger capacity.Existing
2The transit vehicle shall receive the status of demand responsive or flexible-route transit schedules and passenger loading from the transit vehicle operator.Existing
3The transit vehicle shall provide the transit vehicle operator instructions about the demand responsive or flexible-route transit schedule that has been confirmed from the center.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 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.Existing
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.Existing
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.Existing
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.Existing
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.Existing
10The transit vehicle shall provide fare statistics data to the center.Existing