Other CVAS (Terminator*)
This terminator is intended to provide a source and destination for ITS data flows between peer (e.g. inter-regional) commercial vehicle administration functions. It enables commercial vehicle administration activities to be coordinated across different jurisdictional areas. In the Physical Architecture, this terminator is a reciprocal Commercial Vehicle Administration Subsystem (CVAS). This terminator encompasses all functions associated with commercial vehicle safety, registration, and operating authority for non-U.S. based commercial motor vehicle carriers. The agencies represented herein may include Federal, state, provincial, and local regulatory entities outside the U.S.Inputs/Outputs: Architecture Flows* and 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*:
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*:

