Regional Architecture Logo
 

Send Your Comments

 E-Mail

On-board Transit Trip Monitoring Equipment Package

 Architecture Geographic Scope

Description:

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

 

Included in:

 ATCOG-RTD Transit Vehicles
Independent School District Buses
TAPS Demand Response Vehicles
The Connection Vehicles

Functional Requirements:

1The transit vehicle shall compute the location of the transit vehicle based on inputs from a vehicle location determination function.
2The transit vehicle shall support the computation of the location of a transit vehicle using on-board sensors to augment the location determination function. This may include proximity to the transit stops or other known reference points as well as recording trip length.
3The transit vehicle shall record transit trip monitoring data including vehicle mileage and fuel usage.
4The transit vehicle shall record transit trip monitoring data including operational status information such as doors open/closed, passenger loading, running times, etc.
5The transit vehicle shall send the transit vehicle trip monitoring data to center-based trip monitoring functions.
  

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(a)Vehicle passenger loading by bus stop and trip segment.
2.1.1.1(b)Bus running times between time points.
2.1.1.1(d)Drive-line operating condition.
2.1.1.1(e)Mileage accumulated by individual buses.
2.1.1.1(f)Real-time vehicle location reports.
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.
2.1.3PTM shall include a Personnel Management (PM) function to facilitate the management of operator, and maintenance personnel.
2.1.3.1PM shall include a Maintenance Personnel Management (MPM) function.
2.1.3.1.1MPM shall automatically track vehicle miles on each bus in real-time.
  
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.