Regional Architecture Logo
 

Send Your Comments

 E-Mail

On-board Transit Signal Priority Equipment Package

 Architecture Geographic Scope

Description:

 On-board systems to provides request signal priority through short range communication directly with traffic control equipment at the roadside (intersections, crossings, ramp meters, etc.).

 

Included in:

 Colorado Valley Transit Vehicles
Golden Crescent Transit Vehicles
Victoria Transit Vehicles

Functional Requirements:

1The transit vehicle shall determine the schedule deviation and estimated times of arrival (ETA) at transit stops.
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.
3The transit vehicle shall send the schedule deviation data and status of priority requests to the transit vehicle operator.
  

User Service Requirements (fully or partially addressed):

2.0PUBLIC TRANSPORTATION MANAGEMENT
2.1.0ITS shall include a Public Transportation Management (PTM) function.
2.1.1PTM shall include an Operation of Vehicles and Facilities (OVF) function that provides computer assisted control of the operation of vehicles and their associated facilities.
2.1.1.1To enable the automation of the vehicle and facilities operations OVF shall provide the capability to gather the needed data to include, but not be limited to, the following:
2.1.1.1(d)Drive-line operating condition.
2.1.1.1(f)Real-time vehicle location reports.
2.1.1.2OVF shall include a Command and Control (CC) capability.
2.1.1.2.1CC shall provide the capability for real-time Vehicle Command and Control (VCC).
2.1.1.2.1.1VCC shall provide the capability to compare received information with predetermined operating condition specifications and note any deviations.
2.1.1.2.1.4VCC shall provide the capability to automatically issue corrective instructions to the operator including, but not limited to, the following:
2.1.1.2.2When CC detects a vehicle(s) has deviated from schedule it shall provide the capability to automatically determine the optimum scenario for returning the vehicle or fleet to schedule.
2.1.1.2.3CC shall include an integrated traffic control capability that provides traffic signal preemption when required for schedule adjustment to Transit Vehicles at traffic signals (i.e., centralized or distributed).
2.1.1.2.4CC shall include the capability for its computational capabilities to be located either on-vehicle and/or at remote locations.
2.1.2PTM shall include a Planning and Scheduling Services (PSS) function to automate the planning and scheduling of public transit operations.
2.1.2.2The PSS shall include a Schedule Generation capability.
2.1.2.2.1The PSS Schedule Generation function shall collect data for schedule generation including, but not limited to, the following:
2.1.2.2.1(a)Route segment running-time.
2.1.2.2.1(b)Passenger loading at each stop.
  
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-27-2005 using Ronald C. Ice and Associates Web Spinner Technology.