Commercial Vehicle (Subsystem*)
The Commercial Vehicle Subsystem (CVS) resides in a commercial vehicle and provides the sensory, processing, storage, and communications functions necessary to support safe and efficient commercial vehicle operations. The Commercial Vehicle Subsystem provides two-way communications between the commercial vehicle drivers, their fleet managers, attached freight equipment, and roadside officials, and provides HAZMAT response teams with timely and accurate cargo contents information after a vehicle incident. This subsystem provides the capability to collect and process vehicle, cargo information from the attached freight equipment, and driver safety data and status and alert the driver whenever there is a potential safety or security problem. Basic identification, security and safety status data are supplied to inspection facilities at mainline speeds. In addition, the subsystem will automatically collect and record mileage, fuel usage, and border crossings.Subsystem Interfaces Diagram
Get the Source Graphic, a Enhanced Windows Metafile (EMF), in ZIP format.
Functionality: Equipment Packages* and PSpecs*
- On-board Cargo Monitoring (Equipment Package*)
PSpecs: - On-board CV Electronic Data (Equipment Package*)
PSpecs:- 2.2.3-Provide CV Driver Electronic Credential and Tax Filing Interface
- 2.3.7-Produce Commercial Vehicle Driver Message on Vehicle
- 2.4.1-Communicate Commercial Vehicle On-board Data to Roadside
- 2.4.6-Provide Commercial Vehicle On-board Data Store Interface
- 2.6.2-Transmit Commercial Vehicle Tag Data
- 2.6.3-Provide Commercial Driver Tag Data Interface
- 2.6.4-Provide Lock Tag Data Interface
- 2.6.5-Manage Commercial Vehicle Tag Data Store
- On-board CV Safety and Security (Equipment Package*)
PSpecs:- 2.3.7-Produce Commercial Vehicle Driver Message on Vehicle
- 2.4.1-Communicate Commercial Vehicle On-board Data to Roadside
- 2.4.2-Collect On-board Commercial Vehicle Sensor Data
- 2.4.3-Analyze Commercial Vehicle On-board Data
- 2.4.4-Provide Commercial Vehicle Driver Interface
- 2.4.5-Communicate Commercial Vehicle On-board Data to Vehicle Manager
- 2.4.6-Provide Commercial Vehicle On-board Data Store Interface
- 2.4.7-Manage CV On-board Data
- 2.6.2-Transmit Commercial Vehicle Tag Data
- On-board Driver Authentication (Equipment Package*)
PSpecs: - On-board Trip Monitoring (Equipment Package*)
PSpecs:- 2.1.4-Provide Commercial Vehicle Driver Routing Interface
- 2.2.2-Provide Vehicle Static Route
- 2.2.4-Provide Commercial Vehicle Driver Communications
- 2.4.2-Collect On-board Commercial Vehicle Sensor Data
- 2.4.3-Analyze Commercial Vehicle On-board Data
- 2.4.4-Provide Commercial Vehicle Driver Interface
- 2.4.5-Communicate Commercial Vehicle On-board Data to Vehicle Manager
- 2.4.6-Provide Commercial Vehicle On-board Data Store Interface
- 2.4.7-Manage CV On-board Data
- 2.4.8-Correlate Commercial Vehicle Route
Inputs/Outputs: Architecture Flows* and Data Flows*
Basic Commercial Vehicle
Commercial Vehicle
- commercial vehicle measures (Architecture Flow*) - Commercial vehicle and driver status measured by on-board ITS equipment.
Data Flows*:
Border Inspection Systems
Commercial Vehicle
- border pass/pull-in (Architecture Flow*) - Command to commercial vehicle to pull into or bypass border inspection station
Data Flows*: - clearance notification (Architecture Flow*) - Notification that cargo has been cleared through customs.
Data Flows*:
Commercial Vehicle
Basic Commercial Vehicle
- safe vehicle disable (Architecture Flow*) - Control signal disabling or enabling commercial vehicle.
Data Flows*:
Commercial Vehicle
Border Inspection Systems
- tag data (Architecture Flow*) - Unique tag ID and related vehicle information.
Data Flows*:
Commercial Vehicle
Commercial Vehicle Administration
- driver log (Architecture Flow*) - A daily log showing hours in service for the current driver. The query flow is not explicitly shown.
Data Flows*: - on-board safety data (Architecture Flow*) - Safety data measured by on-board sensors. Includes information about the vehicle, vehicle components, cargo, and driver. The query flow is not explicitly shown.
Data Flows*:
Commercial Vehicle
Commercial Vehicle Check
- border clearance data (Architecture Flow*) - Trip specific data regarding the movement of goods across international borders. Includes trip identification number. May also include results from recent border crossing screening events.
Data Flows*: - commercial vehicle breach (Architecture Flow*) - 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.
Data Flows*: - commercial vehicle disable status (Architecture Flow*) - This flow provides the status of the disable flag in the commercial vehicle.
Data Flows*: - driver log (Architecture Flow*) - A daily log showing hours in service for the current driver. The query flow is not explicitly shown.
Data Flows*: - electronic lock data (Architecture Flow*) - Notification to roadside (via transponder) of the presence and status of electronic cargo locks.
Data Flows*: - expected driver identity characteristics (Architecture Flow*) - Driver identification information e.g. encrypted PIN codes issued to drivers, encrypted driver biometric parameters.
Data Flows*: - freight equipment information (Architecture Flow*) - 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, Bill of Lading, and sensor status.
Data Flows*: - on-board safety data (Architecture Flow*) - Safety data measured by on-board sensors. Includes information about the vehicle, vehicle components, cargo, and driver. The query flow is not explicitly shown.
Data Flows*: - safety inspection record (Architecture Flow*) - Record containing results of commercial vehicle safety inspection.
Data Flows*: - screening event record (Architecture Flow*) - Results of CVO electronic screening activity.
Data Flows*: - tag data (Architecture Flow*) - Unique tag ID and related vehicle information.
Data Flows*:
Commercial Vehicle
Commercial Vehicle Driver
- alerts (Architecture Flow*) - This flow represents the visual or auditory interface with ITS equipment containing specific alerts and messages related to commercial vehicles (e.g. trucks not advised, trucks over 10 tons not allowed on bridge, route details). This also includes detected route deviations and warning indications detected by on-board sensors (e.g., safety) and freight equipment sensors (e.g., breach, cargo).
Data Flows*: - CVO pass/pull-in message (Architecture Flow*) - This flow represents the visual or auditory interface with ITS equipment containing a message sent to commercial vehicle driver indicating whether to bypass or requesting pull in to inspection/verification stop along with inspection results (e. g., LED indicator on transponder or variable message sign).
Data Flows*: - trip log information (Architecture Flow*) - This flow represents the tactile or auditory interface with ITS equipment containing the information entered into the trip log, or request for update.
Data Flows*:
Commercial Vehicle
Emergency Management
- hazmat spill notification (Architecture Flow*) - Information provided to emergency response organizations when cargo sensors detect a release of hazardous material. This information will include sensor information, vehicle location and identification, and carrier identification.
Data Flows*:
Commercial Vehicle
Fleet and Freight Management
- commercial vehicle breach (Architecture Flow*) - 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.
Data Flows*: - driver alert response (Architecture Flow*) - Commercial Vehicle Driver response to a breach alert for a Freight Equipment breach or tamper event.
Data Flows*: - driver log (Architecture Flow*) - A daily log showing hours in service for the current driver. The query flow is not explicitly shown.
Data Flows*: - driver to fleet request (Architecture Flow*) - Requests from the driver and vehicle for routing, payment, and enrollment information.
Data Flows*: - freight equipment information (Architecture Flow*) - 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, Bill of Lading, and sensor status.
Data Flows*: - identities (Architecture Flow*) - Identification information for the Commercial Vehicle (e.g., license plate number or USDOT number), Freight Equipment (e.g., container, chassis, or trailer identification), and Driver.
Data Flows*: - on-board safety data (Architecture Flow*) - Safety data measured by on-board sensors. Includes information about the vehicle, vehicle components, cargo, and driver. The query flow is not explicitly shown.
Data Flows*: - on-board vehicle data (Architecture Flow*) - Information about the commercial vehicle stored on-board (for maintenance purposes, gate access, cargo status, lock status, etc.).
Data Flows*: - route deviation alert (Architecture Flow*) - An alert that indicates a deviation from a planned route has been detected. The alert will contain the current Commercial Vehicle location and identity.
Data Flows*: - trip log (Architecture Flow*) - Driver's daily log, vehicle location, mileage, and trip activity (includes screening, inspection and border clearance event data as well as fare payments).
Data Flows*:
Commercial Vehicle
Vehicle
- commercial vehicle data (Architecture Flow*) - Information about the commercial vehicles cargo, credentials, and payments.
Data Flows*:
Commercial Vehicle Administration
Commercial Vehicle
- safety inspection record (Architecture Flow*) - Record containing results of commercial vehicle safety inspection.
Data Flows*:
Commercial Vehicle Check
Commercial Vehicle
- border clearance data request (Architecture Flow*) - Request for trip specific data regarding the movement of goods across international borders. Includes trip identification number. May also include results from recent border crossing screening events.
Data Flows*: - border clearance event (Architecture Flow*) - Reports clearance event data regarding action taken at border, including acceptance or override of system decision, and date/time stamp
Data Flows*: - electronic lock data request (Architecture Flow*) - Request from roadside for data regarding presence and status of electronic cargo locks.
Data Flows*: - electronic screening request (Architecture Flow*) - Request for identification data to support electronic screening.
Data Flows*: - pass/pull-in (Architecture Flow*) - Command to commercial vehicle to pull into or bypass inspection station.
Data Flows*: - request tag data (Architecture Flow*) - Request for tag information including credit identity, stored value card cash, etc.
Data Flows*: - safety inspection record (Architecture Flow*) - Record containing results of commercial vehicle safety inspection.
Data Flows*: - safety inspection request (Architecture Flow*) - Request for safety inspection record.
Data Flows*: - screening event record (Architecture Flow*) - Results of CVO electronic screening activity.
Data Flows*: - trigger area notification (Architecture Flow*) - Notification to activate wireless roadside inspection safety data message collection.
Data Flows*:
Commercial Vehicle Driver
Commercial Vehicle
- alert response (Architecture Flow*) - This flow represents the tactile or auditory interface with ITS equipment containing the response by a Commercial Vehicle Driver or Fleet-Freight Manager that confirms or cancels an alert.
Data Flows*: - CVO driver initialization (Architecture Flow*) - This flow represents the tactile or auditory interface with ITS equipment containing the commercial vehicle driver and vehicle information. This flow contains inquiries to the commercial vehicle managing system, interaction with on-board equipment including setup, configuration, and initiation of self tests, and entry of carrier, driver, vehicle, and route information.
Data Flows*:- fcvd-activity_request
- fcvd-carrier_number
- fcvd-driver_data_input
- fcvd-driver_general_message
- fcvd-driver_input_type
- fcvd-driver_number
- fcvd-enrollment_payment_request
- fcvd-enrollment_request
- fcvd-other_data_input
- fcvd-request_routing_instructions
- fcvd-request_tag_data_output
- fcvd-route_data
- fcvd-route_request
- fcvd-vehicle_number
- driver identity characteristics (Architecture Flow*) - The physical or visible characteristics of a commercial vehicle driver that can be measured to uniquely identify a driver. Could be an Identification Card with a Personal Identification Number, biometrics, or visual verification by an operator.
Data Flows*: - trip identification number input (Architecture Flow*) - Commercial vehicle driver input containing the unique trip load number for a specific cross-border shipment.
Data Flows*:
Driver Identification Card
Commercial Vehicle
- cv driver credential (Architecture Flow*) - Driver information (e.g., identity, biometrics, address, date of birth, endorsements, restrictions) stored on a driver’s license or other official identification card used to identify a driver of commercial vehicles.
Data Flows*:
Fleet and Freight Management
Commercial Vehicle
- commercial vehicle disable (Architecture Flow*) - This flow safely disables a specific commercial vehicle.
Data Flows*: - driver log (Architecture Flow*) - A daily log showing hours in service for the current driver. The query flow is not explicitly shown.
Data Flows*: - expected driver identity characteristics (Architecture Flow*) - Driver identification information e.g. encrypted PIN codes issued to drivers, encrypted driver biometric parameters.
Data Flows*: - fleet to driver update (Architecture Flow*) - Updated instructions to the driver including dispatch, routing, and special instructions.
Data Flows*: - on-board vehicle request (Architecture Flow*) - Request for on-board vehicle data.
Data Flows*: - safety inspection record (Architecture Flow*) - Record containing results of commercial vehicle safety inspection.
Data Flows*: - trigger area (Architecture Flow*) - A geographic area a commercial motor vehicle crosses into, which initiates a request to compile and transmit a safety data message. May be associated with a time period.
Data Flows*: - trigger area notification (Architecture Flow*) - Notification to activate wireless roadside inspection safety data message collection.
Data Flows*: - trip identification number (Architecture Flow*) - The unique trip load number for a specific cross-border shipment.
Data Flows*: - trip log request (Architecture Flow*) - Request for trip log.
Data Flows*:
Freight Equipment
Commercial Vehicle
- freight breach (Architecture Flow*) - Information about a breach or tamper event on Freight Equipment which includes identity, type of breach, location, and time.
Data Flows*: - freight equipment information (Architecture Flow*) - 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, Bill of Lading, and sensor status.
Data Flows*:
Intermodal Freight Shipper
Commercial Vehicle
- trip identification number (Architecture Flow*) - The unique trip load number for a specific cross-border shipment.
Data Flows*:
Location Data Source
Commercial Vehicle
- position fix (Architecture Flow*) - Information which provides a traveler's or vehicle's geographical position.
Data Flows*:
Vehicle
Commercial Vehicle
- commercial vehicle data request (Architecture Flow*) - Requests from the vehicle for information about the commercial vehicle's cargo, credentials, and payments.
Data Flows*:

