Commercial Vehicle Administration (Subsystem*)
The Commercial Vehicle Administration Subsystem (CVAS) will operate at one or more fixed locations within a region. This subsystem performs administrative functions supporting credentials, tax, and safety regulations. It issues credentials, collects fees and taxes, and supports enforcement of credential requirements. This subsystem communicates with the Fleet Management Subsystems associated with the motor carriers to process credentials applications and collect fuel taxes, weight/distance taxes, and other taxes and fees associated with commercial vehicle operations. The subsystem also receives applications for, and issues special Oversize/Overweight and HAZMAT permits in coordination with other cognizant authorities. The subsystem coordinates with other Commercial Vehicle Administration Subsystems (in other states/regions) to support nationwide access to credentials and safety information for administration and enforcement functions. This subsystem supports communications with Commercial Vehicle Check Subsystems operating at the roadside to enable credential checking and safety information collection. The collected safety information is processed, stored, and made available to qualified stakeholders to identify carriers and drivers that operate unsafely.Subsystem Interfaces Diagram
Get the Source Graphic, a Enhanced Windows Metafile (EMF), in ZIP format.
Functionality: Equipment Packages* and PSpecs*
- Credentials and Taxes Administration (Equipment Package*)
PSpecs:- 2.5.1-Manage Commercial Vehicle Trips and Clearances
- 2.5.2-Obtain Electronic Credential and Tax Filing Payment
- 2.5.4-Communicate with Other Commercial Vehicle Administration System
- 2.5.5-Manage Commercial Vehicle and Driver Credentials and Enrollment
- 2.5.8-Process Data Received from Roadside Facilities
- 5.4.6-Process CV Violations
- 7.4.1.1-Process Commercial Vehicle Payments
- CV Data Collection (Equipment Package*)
PSpecs:- 2.5.9-Manage Commercial Vehicle Archive Data
- CV Information Exchange (Equipment Package*)
PSpecs:- 2.5.1-Manage Commercial Vehicle Trips and Clearances
- 2.5.3.1-Communicate with Border Inspection
- 2.5.3.2-Analyze Border Clearance Data
- 2.5.4-Communicate with Other Commercial Vehicle Administration System
- 2.5.5-Manage Commercial Vehicle and Driver Credentials and Enrollment
- 2.5.6-Output Commercial Vehicle Enrollment Data to Roadside Facilities
- 2.5.8-Process Data Received from Roadside Facilities
- 5.4.6-Process CV Violations
- CV Safety and Security Administration (Equipment Package*)
PSpecs:- 2.5.4-Communicate with Other Commercial Vehicle Administration System
- 2.5.5-Manage Commercial Vehicle and Driver Credentials and Enrollment
- 2.5.6-Output Commercial Vehicle Enrollment Data to Roadside Facilities
- 2.5.7-Process Commercial Vehicle Violations
- 2.5.8-Process Data Received from Roadside Facilities
- 5.4.6-Process CV Violations
- International CV Administration (Equipment Package*)
PSpecs:
Inputs/Outputs: Architecture Flows* and Data Flows*
Alerting and Advisory Systems
Commercial Vehicle Administration
- 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*:
Archived Data Management
Commercial Vehicle Administration
- archive requests (Architecture Flow*) - A request to a data source for information on available data (i.e. "catalog") or a request that defines the data to be archived. The request can be a general subscription intended to initiate a continuous or regular data stream or a specific request intended to initiate a one-time response from the recipient.
Data Flows*: - archive status (Architecture Flow*) - Notification that data provided to an archive contains erroneous, missing, or suspicious data or verification that the data provided appears valid. If an error has been detected, the offending data and the nature of the potential problem are identified.
Data Flows*:
Border Inspection Administration
Commercial Vehicle Administration
- client verification request (Architecture Flow*) - Request for information such as commercial drivers license information and carrier safety status.
Data Flows*: - pre-arrival notification (Architecture Flow*) - Identification of a vehicle or driver that is approaching a border crossing.
Data Flows*:
Border Inspection Systems
Commercial Vehicle Administration
- arrival notification (Architecture Flow*) - Notification of arrival (and departure) of a motor vehicle at the inspection station.
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 Administration
Archived Data Management
- commercial vehicle archive data (Architecture Flow*) - Information describing commercial vehicle travel and commodity flow characteristics. Content may include a catalog of available information, the actual information to be archived, and associated meta data that describes the archived information.
Data Flows*:
Commercial Vehicle Administration
Border Inspection Administration
- border clearance status (Architecture Flow*) - Notification regarding the crossing status of commercial freight shipment scheduled to enter the U.S. Includes portions of border agency and transportation agency clearance results, as they become available.
Data Flows*: - client verification information (Architecture Flow*) - Information about carriers who have made border credential applications such as commercial drivers license information and carrier safety status.
Data Flows*: - screening results (Architecture Flow*) - Results of commercial vehicle screening event at a border crossing - reports clearance event data regarding action taken at border, including acceptance or override of system decision, and date/time stamp.
Data Flows*:
Commercial Vehicle Administration
Commercial Vehicle
- safety inspection record (Architecture Flow*) - Record containing results of commercial vehicle safety inspection.
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 Administration
CVO Information Requestor
- 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*: - 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 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*:
Commercial Vehicle Administration
Enforcement Agency
- 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*: - 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*: - 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 Administration
Financial Institution
- payment request (Architecture Flow*) - Request for payment from financial institution.
Data Flows*:
Commercial Vehicle Administration
Fleet and Freight Management
- 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 status (Architecture Flow*) - Notification regarding the crossing status of commercial freight shipment scheduled to enter the U.S. Includes portions of border agency and transportation agency clearance results, as they become available.
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*: - commercial vehicle permit (Architecture Flow*) - Permit for oversize, overweight, or hazmat shipments.
Data Flows*: - compliance review report (Architecture Flow*) - Report containing results of carrier compliance review, including concomitant out-of-service notifications, carrier warnings/notifications. The information may be provided as a response to a real-time query of 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*: - route restrictions (Architecture Flow*) - Information about routes, road segments, and areas that do not allow the transport of security sensitive hazmat cargoes or include other restrictions (such as height or weight limits).
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*: - 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*:
Commercial Vehicle Administration
Information Service Provider
- route restrictions (Architecture Flow*) - Information about routes, road segments, and areas that do not allow the transport of security sensitive hazmat cargoes or include other restrictions (such as height or weight limits).
Data Flows*:
Commercial Vehicle Administration
Intermodal Freight Shipper
- border clearance status (Architecture Flow*) - Notification regarding the crossing status of commercial freight shipment scheduled to enter the U.S. Includes portions of border agency and transportation agency clearance results, as they become available.
Data Flows*:
Commercial Vehicle Administration
Map Update Provider
- route restrictions (Architecture Flow*) - Information about routes, road segments, and areas that do not allow the transport of security sensitive hazmat cargoes or include other restrictions (such as height or weight limits).
Data Flows*:
Commercial Vehicle Administration
Other CVAS
- 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 status (Architecture Flow*) - Notification regarding the crossing status of commercial freight shipment scheduled to enter the U.S. Includes portions of border agency and transportation agency clearance results, as they become available.
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*: - commercial vehicle permit coordination (Architecture Flow*) - Information for the coordination of commercial vehicle permits for oversize, overweight, or for dangerous goods.
Data Flows*: - credential fee coordination (Architecture Flow*) - Jurisdiction's rates for various credentials (IRP, IFTA, etc.) that are exchanged between agencies.
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*: - route restrictions (Architecture Flow*) - Information about routes, road segments, and areas that do not allow the transport of security sensitive hazmat cargoes or include other restrictions (such as height or weight limits).
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*:
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*:
CVO Information Requestor
Commercial Vehicle Administration
- request for data review (Architecture Flow*) - Request that data reported about a motor carrier or driver be reviewed for potential mis-assignment or other error.
Data Flows*:
DMV
Commercial Vehicle Administration
- registration (Architecture Flow*) - Registered owner of vehicle and associated vehicle information.
Data Flows*:
Enforcement Agency
Commercial Vehicle Administration
- 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*: - targeted list (Architecture Flow*) - List of carriers, drivers, and/or vehicles of interest for enforcement purposes.
Data Flows*: - trigger area definition (Architecture Flow*) - Information that defines the desired trigger area for wireless roadside inspection safety data message submission.
Data Flows*: - trigger control (Architecture Flow*) - Controls to enable or disable a particular trigger.
Data Flows*:
Financial Institution
Commercial Vehicle Administration
- transaction status (Architecture Flow*) - Response to transaction request. Normally dealing with a request for payment.
Data Flows*:
Fleet and Freight Management
Commercial Vehicle Administration
- audit data (Architecture Flow*) - Information to support a tax audit.
Data Flows*: - credential application (Architecture Flow*) - Application for commercial vehicle credentials. Authorization for payment is included.
Data Flows*: - cv repair status (Architecture Flow*) - Information about the completion of a repair to a 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*: - 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*: - request for permit (Architecture Flow*) - Request by fleet management for oversize, overweight, or hazmat permit.
Data Flows*: - tax filing (Architecture Flow*) - Commercial vehicle tax filing data. Authorization for payment is included.
Data Flows*:
Maintenance and Construction Management
Commercial Vehicle Administration
- current asset restrictions (Architecture Flow*) - Restrictions levied on transportation asset usage based on infrastructure design, surveys, tests, or analyses. This includes standard facility design height, width, and weight restrictions, special restrictions such as spring weight restrictions, and temporary facility restrictions that are imposed during maintenance and construction.
Data Flows*:
Other CVAS
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 status (Architecture Flow*) - Notification regarding the crossing status of commercial freight shipment scheduled to enter the U.S. Includes portions of border agency and transportation agency clearance results, as they become available.
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*: - commercial vehicle permit coordination (Architecture Flow*) - Information for the coordination of commercial vehicle permits for oversize, overweight, or for dangerous goods.
Data Flows*: - credential fee coordination (Architecture Flow*) - Jurisdiction's rates for various credentials (IRP, IFTA, etc.) that are exchanged between agencies.
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*: - route restrictions (Architecture Flow*) - Information about routes, road segments, and areas that do not allow the transport of security sensitive hazmat cargoes or include other restrictions (such as height or weight limits).
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*:

