CVO13-Freight Assignment Tracking
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. Periodically or asynchronously, the Alerting and Advisory Agency systems (e.g., Trucking Information Sharing and Analysis Center or ISAC) may send alerts and advisories to the Fleet and Freight Management Subsystem.

  2. Periodically the Basic Commercial Vehicle sends measurements (commercial vehicle measures) to the Commercial Vehicle Subsystem regarding the brake status, the mileage traveled, the location of the vehicle, the state of the driver and ability to drive, and the vehicle identity and its safety status.

Shipments are initiated with the cooperation of several entities and information flows are exchanged to notify all vested agencies of the plan for the goods movement. This process is part of the Typical Freight Operations of CVO02: Freight Administration.

  1. Once a shipment has been initiated (freight transport booking), the plan for shipment (i.e., booking) is sent back to the Intermodal Freight Shipper (booking status) and then monitored throughout is course, from origin to destination. Several steps are involved in this monitoring:

    • Whenever a Commercial Vehicle Driver enters the Commercial Vehicle, his driver identity characteristics are sent to the Commercial Vehicle Subsystem (CVS) and the cv driver credential is read by the CVS from the Driver Identification Card.

    • Similarly, whenever cargo is loaded onto a trailer and/or the trailer/chassis is connected to the commercial vehicle, the identification of the Freight Equipment is sent to the Commercial Vehicle Subsystem (freight equipment information).

    • Periodically and continually during the shipment, the identities of the driver, the freight equipment (and consequently the freight itself), and the vehicle are sent to the Fleet and Freight Management Subsystem from the Basic Commercial Vehicle. This information (booking status) is also forwarded from the Fleet and Freight Management Subsystem to both the Intermodal Freight Shipper and the Intermodal Freight Depot so that all vested agencies are aware of the status of the goods movement.

  2. The tracking of the booking continues throughout the shipment. If no exceptions arise then nothing else occurs and the goods arrive at their destination according to the booking. However, should any unplanned changes occur during the tracking, a series of steps is initiated:

    • Initially, the exception is sent from the Fleet and Freight Management Subsystem to the Fleet and Freight Manager (fleet and freight alerts).

    • The Fleet and Freight Manager analyses the exception and determines if this is acceptable and reasonable and possibly updates the booking. Alternatively, the Fleet and Freight Manager may decide that there is something wrong and that further action must be taken to abort the shipment and prevent further adverse outcomes. In either case, the alert response is sent from the Fleet and Freight Manager back to the Fleet and Freight Management Subsystem.

    • If enough time has passed without a response from the Fleet and Freight Manager, or if the response indicates an unacceptable situation has occurred, the Fleet and Freight Management Subsystem would send an alarm to the Emergency Management Subsystem.

    • A notification of assignment exception is also sent to the Alerting and Advisory Systems as fleet and freight threat information.


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