Interface: Commercial Vehicles - Private Commercial Vehicle Dispatch Centers

Commercial Vehicles to Private Commercial Vehicle Dispatch Centers Interface Diagram

Information Flow Definitions

commercial vehicle breach  (Planned)  

Information about a breach or tamper event on a Commercial Vehicle or its attached freight equipment which includes identity, type of breach, location, and time.

driver alert response  (Planned)  

Commercial Vehicle Driver response to a breach alert for a Freight Equipment breach or tamper event, or other alerts provided to the driver.

driver to fleet request  (Planned)  

Requests from the driver and vehicle for routing, payment, and enrollment information.

fleet to driver update  (Planned)  

Updated instructions to the driver including dispatch, routing, travel and parking information, and special instructions. Special instructions include incident management instruction, operational tasks, impacted transport orders in case of an incident, task descriptions with trip/route/load plan, transport order status information, driver information, vehicle information, cargo information and trip information.

freight equipment information  (Planned)  

Container, trailer, or chassis information regarding identity, type, location, brake wear data, mileage, seal #, seal type, door open/close status, chassis bare/covered status, tethered / untethered status, temperature, humidity, power, battery levels, brake wear data, and bill of lading/information regarding the cargo/content.

on-board vehicle data  (Planned)  

Information about the commercial vehicle stored on–board (for maintenance purposes, gate access, cargo status, lock status, etc.). The request flow is not explicitly shown.

route deviation alert  (Planned)  

An alert that indicates a deviation from a planned route has been detected. The alert will contain the current Commercial Vehicle location and identity.

trip log  (Planned)  

Driver's daily log, vehicle location, mileage, and trip activity (includes screening, inspection and border clearance event data as well as fare payments). The request flow is not explicitly shown.