|
The source graphic, a Windows Metafile (WMF), for the TSDs can be downloaded here:
TSD Part 1,
TSD Part 2,
The following discusses how the National ITS Architecture provides the transportation service described by this service package. Each numbered item describes the operation of that portion of the service package identified with the corresponding number on the transaction set diagram.
-
Throughout this process a Fleet and Freight Management Subsystem (FFMS) that is the carrier's operations system managing the fleet of vehicles will send information to the Fleet-Freight Manager (fleet status) automatically, or in response to a fleet manager inquiry.
-
The Commercial Vehicle Subsystem (CVS) receives the cv driver credential from the Driver Identification Card and CVO driver initialization inputs from the Commercial Vehicle Driver that represent the driver's interaction with on-board equipment including setup, configuration, and initiation of self-tests, and entry of carrier, driver, vehicle, and route information. FFMS may provide a copy of the driver log that it has maintained to load into the CVS on-board computer - either as part of the initialization when a driver may be switching vehicles or to develop a safety data message for reporting later.
-
The Commercial Vehicle Subsystem (CVS) will receive position fix readings from a Location Data Source that will be used to support various safety and navigation functions on board including a trigger of safety data message transmission when required. On an asynchronous basis, the Basic Commercial Vehicle can send vehicle safety and security information measured by non-ITS equipment to the Commercial Vehicle Subsystem (commercial vehicle measures) and instrumented Freight Equipment, including the chassis, trailer, container, or cargo area can provide freight equipment information to the CVS equipment. The Commercial Vehicle Subsystem will process this data and forward any safety related warnings to the Commercial Vehicle Driver (alerts) to which the driver may respond with alert response to acknowledge the alert or initiate another action.
-
An Enforcement Agency will define a geographic area, time frame, and other parameters that will govern the collection of commercial vehicle safety data and will send the trigger area definition to the Commercial Vehicle Administration Subsystem (CVAS). CVAS will, in turn, publicize the trigger area configuration data to the Fleet and Freight Management Subsystems (FFMS). FFMS will then pass this information onto its fleet of commercial vehicles also (trigger area).
-
When it is time to start the collection process with the predefined trigger areas, the Enforcement Agency will notify the Commercial Vehicle Administration Subsystems (CVAS) to begin collecting data from vehicles within the trigger areas (trigger control). CVAS will send trigger control commands to the Commercial Vehicle Check Subsystem (CVCS) components located in the field. Commercial Vehicle Operations (CVO) Inspectors may also provide a CVO inspector input to control the CVCS equipment locally. CVAS will also inform the Fleet and Freight Management Subsystems (FFMS) that data collection has begun so the enrolled carriers can inform their vehicles (trigger area notification). Commercial Vehicle Subsystem (CVS) on-board equipment may also receive a trigger area notification signal directly from the CVCS at or along the roadside.
-
The Commercial Vehicle Check Subsystem (CVCS) will read identification information data from passing commercial vehicles and the equipped Commercial Vehicle Subsystems (CVS) that are within range of a CVCS will provide their daily log indicating the hours of service for the current driver (driver log) and information about the vehicle, vehicle components, cargo, and driver (on-board safety data). CVCS will provide the collected set of vehicle date up to the Commercial Vehicle Administration Subsystem (CVAS) to analyze the results (driver log and on-board safety data).
-
The Commercial Vehicle Check Subsystem (CVCS) can request identity and credentials data stored electronically on-board (request tag data). This data will be provided by the Commercial Vehicle Subsystem (CVS) on-board equipment to the CVCS (tag data). After analyzing the data provided by the CVS, a decision is made to either allow the vehicle to pass or require it to be stopped. CVCS can send the decision to the CVS (pass/pull-in), which will provide an indicator to the Commercial Vehicle Driver (CVO pass/pull-in message). Alternately, the CVCS can send the decision directly to the Commercial Vehicle Driver using a (CVO pass/pull-in message). Once the data has been collected and analyzed and any subsequent detailed inspections have been complete, the CVCS will send the completed safety data message for the vehicle onto the Commercial Vehicle Administration Subsystem (CVAS) for filing and storage.
-
Commercial Vehicle Subsystem (CVS) on-board equipment may also be able to use the positioning information it has from step 3 above to know that it is within a trigger area and to begin sending its driver log and on-board safety data to the Fleet and Freight Management Subsystem (FFMS) or directly on to the Commercial Vehicle Administration Subsystem (CVAS). FFMS will provide the collected set of driver log and on-board safety data inputs from its fleet of vehicles to the CVAS. Either CVAS or the carrier (FFMS) can provide a record of the safety inspection data that it has collected back down to the on-board equipment in the CVS (safety inspection record).
|
-
This icon indicates that the associated architecture flow either has
been or will be addressed by ITS Standards. Select the architecture flow
for more information on relevant standards activities.
