|
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.
-
The Fleet-Freight Manager may request (fleet manager inquiry) the fleet status from the Fleet and Freight Management Subsystem (FFMS), including enrollment status, routing/itinerary information, emergency information, current vehicle locations and other information. As part of a new driver enrollment the Commercial Vehicle Administration (CVAS) will provide the commercial vehicle driver's record (cv driver record) along with any credentials status information that will in turn be presented to the manager.
-
On an asynchronous basis the Commercial Vehicle Subsystem tracks its location (position fix). The Commercial Vehicle Subsystem can send the vehicle's location, along with driver messages and on-board sensor data, to the Fleet and Freight Management Subsystem (on-board vehicle data) upon request (on-board vehicle request).
-
The Fleet and Freight Management Subsystem can periodically request information about a trip (trip log request). The Commercial Vehicle Subsystem can electronically provide the Fleet and Freight Management Subsystem with the driver's daily log, mileage and trip activity (trip log).
-
Initial dissemination and periodic updates of restrictions in routing (route restrictions) are provided by the Commercial Vehicle Administration Subsystem to the Fleet and Freight Management Subsystem.
-
Periodically or asynchronously, the Fleet and Freight Management Subsystem may make a map update request and receive map updates from the Map Update Provider. Alternatively, via a subscription, the Map Update Provider may push updates to the Fleet and Freight Management Subsystem as changes occur. Map updates are necessary in order for the Fleet and Freight Management Subsystem to determine the best routes for commercial goods shipments.
-
Asynchronously and periodically, the Information Service Provider Subsystem can provide the Fleet and Freight Management Subsystem with current and forecasted traffic information (road network conditions and incident information), which could be used to alter an existing route or as a parameter for the Fleet and Freight Management Subsystem's route generation program.
-
When preparing for a trip, typical fleet operations include several process steps:
-
The Commercial Vehicle Driver can contact the Commercial Vehicle Subsystem with trip specific information, which may include carrier, driver and vehicle information, or a request for a route (CVO driver initialization).
-
The Commercial Vehicle Subsystem will forward the route request to the Fleet and Freight Management Subsystem (driver to fleet request).
-
The Fleet and Freight Management Subsystem can internally generate a route or forward the request on to the Information Service Provider Subsystem (route request).
-
Using the constraints provided with the route request and any route restrictions (if applicable), the Information Service Provider Subsystem generates a route and sends it to the Fleet and Freight Management Subsystem (route plan).
-
The route information, along with any messages, alerts, or special instructions, is sent to the Commercial Vehicle Subsystem (fleet to driver update) where it is forwarded to the Commercial Vehicle Driver as updates to the trip log (trip log information) or alerts or messages (alerts).
-
Based upon previously arranged routes for the commercial vehicle (and driver), via the fleet to driver update flow, the current route is monitored by the Commercial Vehicle Subsystem.
-
In addition, the route is also monitored by the Fleet and Freight Management Subsystem using the on-board vehicle data.
-
If the current location is off route or not according to the previously established itinerary, the Commercial Vehicle Subsystem sends an alert to the Commercial Vehicle Driver (alerts). The driver may then choose to provide a response to the Commercial Vehicle Subsystem alert indicating the reason for the deviation (alert response) which is forwarded to the Fleet and Freight Management Subsystem (driver alert response).
-
The Commercial Vehicle Subsystem will send a route deviation alert to the Fleet and Freight Management Subsystem with the driver’s reason or without any reason if enough time has passed without driver response.
-
Upon receipt of a route deviation alert, the Fleet and Freight Management Subsystem will notify the Fleet and Freight Manager of the deviation (fleet and freight alerts). The Fleet and Freight Manager can then determine if the deviation is acceptable and update the planned route/itinerary to reflect the deviation. If the deviation is unacceptable, the Fleet and Freight Manager would so indicate (alert response).
-
If enough time has passed without a response from the Fleet and Freight Manager, or if the response indicates an unacceptable deviation, the Fleet and Freight Management Subsystem would send an alarm to the Emergency Management Subsystem.
-
A deviation from planned route is also sent to the Alerting and Advisory Systems as fleet and freight threat information.
-
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. The Fleet and Freight Management Subsystem may alter the routes chosen or contact the Fleet-Freight Manager and Commercial Vehicle Driver to alert them to the nature of the advisory.
|
-
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.
