APTS06-Transit Fleet Management
Transaction Set Diagram



Get the Source Graphic, a Windows Metafile (WMF), in ZIP format.
More about ZIP files

The following discusses how the National ITS Architecture provides the transportation service described by this market package. Each numbered item describes the operation of that portion of the market package identified with the corresponding number on the transaction set diagram.

  1. To automate the maintenance of the transit vehicles, the TRMS sends a request to the Transit Vehicle Subsystem (TRVS) for vehicle performance and maintenance data collected by on-board sensors (request for vehicles measures). The TRVS responds with data containing vehicle performance and maintenance data collected by onboard sensors (transit vehicle conditions). Some of this data is obtained from sensors or systems in the Basic Transit Vehicle (the non-ITS portion of the transit vehicle) as transit vehicle measures.

  2. Transit Operations Personnel manage the overall process of transit vehicle management, inputting transit maintenance requirements, requested maintenance actions, as well as initializing and updating a vehicle assignment (as part of transit operations personnel inputs) to the Transit Management Subsystem (TRMS). The overall status of vehicle's activities as well as status of individual vehicle maintenance would be presented to the Transit Operations Personnel (as a part of transit operations status).

  3. At the beginning of a work day or shift, TRMS will send the transit schedule information to the TRVS in order to initialize the transit vehicle with a vehicle assignment to a particular block, monitor schedule performance, and develop corrective actions on-board. In turn, TRVS will provide TRMS with transit vehicle location data to support the tracking of its progress relative to its assignment and other management functions.

Hypertext Architecture Version 6.0.0 generated on 4/23/2007 from the following databases
Physical Architecture dated 4/6/2007,
Logical Architecture dated 4/23/2007,
Market Packages dated 4/23/2007,
Security dated 4/20/2007,
User Services dated 4/9/2007,
AppMap dated 4/23/2007 and the
SDOMAP dated 4/23/2007