Regional Architecture Logo
 

Send Your Comments

E-Mail

On-board Paratransit Operations Equipment Package

Architecture Geographic Scope

Description:

On-board systems to manage paratransit and flexible-route dispatch requests, including multi-stop runs. Inputs based on the transit vehicle’s type and passenger capacity.

 

Included in:

ATCOG-RTD Transit Vehicles
TAPS Demand Response Vehicles
The Connection Vehicles

Functional Requirements:

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.
2The transit vehicle shall receive the status of demand responsive or flexible-route transit schedules and passenger loading from the transit vehicle operator.
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.
  

User Service Requirements (fully or partially addressed):

2.0PUBLIC TRANSPORTATION MANAGEMENT
2.3.0ITS shall include a Personalized Public Transit (PPT) function.
2.3.3The PPT shall include a Data Collection function.
2.3.3.1Data Collection shall include on-board sensors to monitor, but not be limited to, the following:
2.3.3.1(a)Vehicle location.
2.3.3.1(b)Passenger loading.
2.3.3.1(c)Fare collection.
2.3.3.2Data Collection shall process and store collected data so that it is available for:
2.3.3.2(a)Real-time schedule adjustments.
2.3.3.2(b)Off-line analysis and planning.
2.3.3.3Data Collection shall support the off-line billing for fares paid by agencies.
2.3.5The PPT shall include a Communications function.
2.3.5.1The Communications function shall provide the capability to link all PPT services into a single entity.
2.3.5.2The Communications function shall provide a two-way communications capability between vehicles and a central base for:
2.3.5.2(a)Voice communications.
2.3.5.2(b)Data communications.
2.3.5.3The Communications function shall provide the capability for sensor data (either raw or processed) to be transmitted from vehicles to a central headquarters or dispatch station.
2.3.5.4The Communications function shall provide the capability for data to be transferred between dispersed points and central base including:
2.3.5.4(a)Data from vehicles.
2.3.5.4(b)Data from locations where passengers are located.
  
The detailed process and user service requirement traceability information on this page was extracted from the National ITS Architecture. Consult the National ITS Architecture web site for more information.

Last updated on 05-12-2005 using Ronald C. Ice and Associates Web Spinner Technology.