Regional Architecture Logo
 

Send Your Comments

 E-Mail

On-board Paratransit Operations Equipment Package

 Architecture Geographic Scope

Description:

 This equipment package forwards paratransit dispatch requests to the driver and forwards acknowledgements to the center. It coordinates with, and assists the driver in managing multi-stop runs associated with demand responsive, flexibly routed transit services.

 

Included in:

 BUS Transit Vehicles
Lower RGV Development Council Transit Vehicles
Rainbow Lines Transit Vehicles

Processes:
4.2.1.5Process Demand Responsive Transit Vehicle Availability Data
4.2.1.6Provide Demand Responsive Transit Driver Interface
  

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 link all PPT service 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 07-16-2003 using Ronald C. Ice and Associates Web Spinner Technology.