Other CV Administration Centers --> Commercial Vehicle Administration Center:
accident report
This triple is bi-directional. See also
Commercial Vehicle Administration Center --> Other CV Administration Centers: accident report
Definitions
accident report (Information 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.
Other CV Administration Centers (Source Physical Object): 'Other CV Administration Centers' is intended to provide a source and destination for information flows between peer (e.g. inter-regional) commercial vehicle administration centers. It enables commercial vehicle administration activities to be coordinated across different jurisdictional areas. It 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.
Commercial Vehicle Administration Center (Destination Physical Object): The 'Commercial Vehicle Administration Center' performs administrative functions supporting credentials, tax, and safety regulations associated with commercial vehicles. It issues credentials, collects fees and taxes, and supports enforcement of credential requirements. It communicates with motor carriers to process credentials applications and collect fuel taxes, weight/distance taxes, and other taxes and fees associated with commercial vehicle operations. It also receives applications for, and issues special Oversize/Overweight and HAZMAT permits in coordination with cognizant authorities. It coordinates with other Commercial Vehicle Administration Centers (in other states/regions) to support nationwide access to credentials and safety information for administration and enforcement functions. It communicates with field equipment to enable credential checking and safety information collection at the roadside. It makes safety information available to qualified stakeholders to identify carriers and drivers that operate unsafely.
Included In
This Triple is in the following Service Packages:
This triple is associated with the following Functional Objects:
This Triple is described by the following Functional View Data Flows:
This Triple has the following triple relationships:
None |
Communication Solutions
- (None-Data) - Secure Internet (ITS) (43)
- (None-Data) - Apache Kafka (44)
- (None-Data) - OMG DDS (44)
- (None-Data) - OASIS MQTT (50)
- (None-Data) - OASIS AMQP (61)
Selected Solution
Solution Description
ITS Application Entity
Development needed |
Click gap icons for more info.
|
||
Mgmt
Apache Zookeeper |
Facilities
Development needed Apache Kafka Apache Zookeeper |
Security
IETF RFC 8446 |
|
TransNet
|
|||
Access
Internet Subnet Alternatives |
Note that some layers might have alternatives, in which case all of the gap icons associated with every alternative may be shown on the diagram, but the solution severity calculations (and resulting ordering of solutions) includes only the issues associated with the default (i.e., best, least severe) alternative.
Characteristics
Characteristic | Value |
---|---|
Time Context | Recent |
Spatial Context | National |
Acknowledgement | True |
Cardinality | Unicast |
Initiator | Destination |
Authenticable | True |
Encrypt | True |
Interoperability | Description |
---|---|
National | This triple should be implemented consistently within the geopolitical region through which movement is essentially free (e.g., the United States, the European Union). |
Security
Information Flow Security | ||||
---|---|---|---|---|
Confidentiality | Integrity | Availability | ||
Rating | Moderate | Moderate | Moderate | |
Basis | Commercial vehicle safety accident report will include particulars of involved operators and vehicles and possibly other PII. | Repurcussions of inaccurate data likely limited to the operators involved which should be small in number. Any such repurcussions are pos-real time and so should have measures for correcting inaccurate data, thus limited to MODERATE. | Timely access required for some application functionality, but borderline to LOW availability as none of this should be strictly real-time. |
Security Characteristics | Value |
---|---|
Authenticable | True |
Encrypt | True |