Commercial Vehicle Check (Subsystem*)
The Commercial Vehicle Check Subsystem (CVCS) supports automated vehicle identification at mainline speeds for credential checking, roadside safety inspections, and weigh-in-motion using two-way data exchange. These capabilities include providing warnings to the commercial vehicle drivers, their fleet managers, and proper authorities of any safety problems that have been identified, accessing and examining historical safety data, and automatically deciding whether to allow the vehicle to pass or require it to stop with operator manual override. The Commercial Vehicle Check Subsystem also provides supplemental inspection services to current capabilities by supporting expedited brake inspections, the use of operator hand-held devices, mobile screening sites, on-board safety database access, and the enrollment of vehicles and carriers in the electronic clearance program.Subsystem Interfaces Diagram
Get the Source Graphic, a Enhanced Windows Metafile (EMF), in ZIP format.
Functionality: Equipment Packages* and PSpecs*
- Citation and Accident Electronic Recording (Equipment Package*)
PSpecs: - International Border Crossing (Equipment Package*)
PSpecs: - Roadside Electronic Screening (Equipment Package*)
PSpecs:- 2.3.1-Produce Commercial Vehicle Driver Message at Roadside
- 2.3.2.1-Administer Commercial Vehicle Roadside Credentials Database
- 2.3.2.2-Process Screening Transactions
- 2.3.3.1-Provide Commercial Vehicle Checkstation Communications
- 2.3.3.3-Administer Commercial Vehicle Roadside Safety Database
- 2.3.4-Detect and Classify Commercial Vehicles and Freight Equipment
- 2.3.5-Provide Commercial Vehicle Roadside Operator Interface
- 2.3.6-Provide Commercial Vehicle Reports
- Roadside HAZMAT Detection (Equipment Package*)
PSpecs: - Roadside Safety and Security Inspection (Equipment Package*)
PSpecs:- 2.3.1-Produce Commercial Vehicle Driver Message at Roadside
- 2.3.3.1-Provide Commercial Vehicle Checkstation Communications
- 2.3.3.2-Provide Commercial Vehicle Inspector Handheld Terminal Interface
- 2.3.3.3-Administer Commercial Vehicle Roadside Safety Database
- 2.3.3.4-Carry-out Commercial Vehicle Roadside Safety Screening
- 2.3.3.5-Carry-out Commercial Vehicle Roadside Inspection
- 2.3.4-Detect and Classify Commercial Vehicles and Freight Equipment
- 2.3.5-Provide Commercial Vehicle Roadside Operator Interface
- 2.3.6-Provide Commercial Vehicle Reports
- Roadside WIM (Equipment Package*)
PSpecs:
Inputs/Outputs: Architecture Flows* and Data Flows*
Alerting and Advisory Systems
Commercial Vehicle Check
- alerts and advisories (Architecture Flow*) - Assessments (general incident and vulnerability awareness information), advisories (identification of threats or recommendations to increase preparedness levels), and alerts (information on imminent or in-progress emergencies). This flow also provides supporting descriptive detail on incidents, threats, and vulnerabilities to increase preparedness and support effective response to threats against the surface transportation system.
Data Flows*:
Basic Commercial Vehicle
Commercial Vehicle Check
- CVO weight and presence (Architecture Flow*) - Physical attribute of commercial vehicle that can be measured (for example, weight, number of axels, axel spacing, etc.).
Data Flows*: - identification information (Architecture Flow*) - The physical characteristics of a commercial vehicle that can be used to determine a vehicle's identity, such as a license plate number, USDOT number, ICC number, bar code, etc.
Data Flows*:
Border Inspection Systems
Commercial Vehicle Check
- inspection results (Architecture Flow*) - Report of results of border inspection on a particular load.
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 Administration
Commercial Vehicle Check
- accident report (Architecture Flow*) - Report of commercial vehicle safety accident. The information may be provided as a response to a real-time query or proactively by the source. The query flow is not explicitly shown.
Data Flows*: - border agency clearance results (Architecture Flow*) - Notification regarding the granting of permission for commercial freight shipment to enter the U.S.
Data Flows*: - carrier participation report (Architecture Flow*) - Report that summarizes motor carrier participation in CVO programs. Used to identify the level of active participation and to report which enrolled carriers are not participating as expected.
Data Flows*: - citation (Architecture Flow*) - Report of commercial vehicle citation. The citation includes references to the statute(s) that was (were) violated. It includes information on the violator and the officer issuing the citation. A citation differs from a violation because it is adjudicated by the courts. The information may be provided as a response to a real-time query or proactively by the source. The query flow is not explicitly shown.
Data Flows*: - credentials information (Architecture Flow*) - Response containing full vehicle fuel tax and registration credentials information. "Response" may be provided in reaction to a real-time query or a standing request for updated information. The query flow is not explicitly shown.
Data Flows*: - credentials status information (Architecture Flow*) - Credentials information such as registration, licensing, insurance, check flags, and electronic screening enrollment data. A unique identifier is included. Corresponds to the credentials portion of CVISN "snapshots." The status information may be provided as a response to a real-time query or as a result of a standing request for updated information (subscription). This may also include information about non-U.S. fleets for use by U.S. authorities, and information regarding U.S. fleets made available to Mexican and Canadian authorities. The query flow is not explicitly shown.
Data Flows*: - cv driver record (Architecture Flow*) - Information typically maintained by a state driver licensing agency about a driver of a commercial vehicle including driver identification data, license data, permit data, and driving history details. The query flow is not explicitly shown.
Data Flows*: - safety inspection report (Architecture Flow*) - Report containing results of commercial vehicle safety inspection. The information may be provided as a response to a real-time query or proactively by the source. The query flow is not explicitly shown.
Data Flows*: - safety status information (Architecture Flow*) - Safety information such as safety ratings, security ratings or flags, inspection summaries, and violation summaries. A unique identifier is included. Corresponds to the safety and security portion of CVISN "snapshots." The status information may be provided as a response to a real-time query or as a result of a standing request for updated information (subscription). This may also include information about non-U.S. fleets for use by U.S. authorities, and information regarding U.S. fleets made available to Mexican and Canadian authorities. The query flow is not explicitly shown.
Data Flows*: - targeted list (Architecture Flow*) - List of carriers, drivers, and/or vehicles of interest for enforcement purposes.
Data Flows*: - transportation border clearance assessment (Architecture Flow*) - Includes directions for commercial driver to proceed to nearest vehicle weigh and inspection station for further review if required.
Data Flows*: - trigger control (Architecture Flow*) - Controls to enable or disable a particular trigger.
Data Flows*: - trip declaration identifiers (Architecture Flow*) - Specific identifiers extracted from notification containing information regarding pending commercial freight shipment into the U.S. Includes carrier, vehicle, and driver identification data.
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 Check
Commercial Vehicle Administration
- accident report (Architecture Flow*) - Report of commercial vehicle safety accident. The information may be provided as a response to a real-time query or proactively by the source. The query flow is not explicitly shown.
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*: - citation (Architecture Flow*) - Report of commercial vehicle citation. The citation includes references to the statute(s) that was (were) violated. It includes information on the violator and the officer issuing the citation. A citation differs from a violation because it is adjudicated by the courts. The information may be provided as a response to a real-time query or proactively by the source. The query flow is not explicitly shown.
Data Flows*: - daily site activity data (Architecture Flow*) - Record of daily activities at commercial vehicle check stations including summaries of screening events and inspections.
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*: - 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*: - roadside data message (Architecture Flow*) - Data set collected by roadside sensors to identify and characterize a vehicle, carrier, and (potentially) driver.
Data Flows*: - safety inspection report (Architecture Flow*) - Report containing results of commercial vehicle safety inspection. The information may be provided as a response to a real-time query or proactively by the source. The query flow is not explicitly shown.
Data Flows*: - violation notification (Architecture Flow*) - Notification to enforcement agency of a violation. The violation notification flow describes the statute or regulation that was violated and how it was violated (e. g., overweight on specific axle by xxx pounds or which brake was out of adjustment and how far out of adjustment it was). A violation differs from a citation because it is not adjudicated by the courts.
Data Flows*:
Commercial Vehicle Check
Commercial Vehicle Driver
- 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*:
Commercial Vehicle Check
CVO Inspector
- CVO inspector information (Architecture Flow*) - This flow represents the visual or auditory interface with ITS equipment containing credential, safety, and preclearance information and instructions to the commercial vehicle inspector.
Data Flows*:
Commercial Vehicle Check
Emergency Management
- alarm (Architecture Flow*) - Information about a Commercial Vehicle or Freight Equipment breach, non-permitted security sensitive hazmat detected at the roadside, route deviation, or Commercial Vehicle Driver / Commercial Vehicle / Freight Equipment assignment mismatches which includes the location of the Commercial Vehicle and appropriate identities.
Data Flows*:
Commercial Vehicle Check
Enforcement Agency
- violation notification (Architecture Flow*) - Notification to enforcement agency of a violation. The violation notification flow describes the statute or regulation that was violated and how it was violated (e. g., overweight on specific axle by xxx pounds or which brake was out of adjustment and how far out of adjustment it was). A violation differs from a citation because it is not adjudicated by the courts.
Data Flows*:
CVO Inspector
Commercial Vehicle Check
- CVC override mode (Architecture Flow*) - This flow represents the tactile or auditory interface with ITS equipment containing the manual override of automated pass/pull-in decisions generated by the Commercial Vehicle Check station.
Data Flows*: - CVO inspector input (Architecture Flow*) - This flow represents the tactile or auditory interface with ITS equipment containing requests from the commercial vehicle inspector to operate the commercial vehicle inspection station.
Data Flows*:
Driver Identification Card
Commercial Vehicle Check
- 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*:
Enforcement Agency
Commercial Vehicle Check
- information on violators (Architecture Flow*) - Information on violators provided by a law enforcement agency. May include information about commercial vehicle violations or other kinds of violations associated with the particular entity. The information may be provided as a response to a real-time query or proactively by the source. The query flow is not explicitly shown.
Data Flows*:
Freight Equipment
Commercial Vehicle Check
- 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*: - hazmat environmental factors (Architecture Flow*) - Sensed characteristics of a vehicle that are analyzed to indicate if the vehicle is carrying a security sensitive substance, e.g. detection of radiation or ammonia compounds.
Data Flows*:

