Commercial Vehicle Service Provider Center --> Commercial Vehicle Administration Center:
malfunction report (Information Flow): Information describing malfunctions of OBEs monitored by the providing center, as well as malfunctions of the center's ICT system.
Commercial Vehicle Service Provider Center (Source Physical Object): The 'Commercial Vehicle Service Provider Center' is an Australia-specific physical object that provides data exchange and commercial vehicle tracking services to other parties involved in commercial vehicle management. It also manages CV OBEs and the operational software on those devices.
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.
This Triple is in the following Service Packages:
- CVO16: Electronic Driver Logs
- CVO17: Intelligent Access Program
- CVO18: Intelligent Access Program - Weight Monitoring
- CVO19: Intelligent Speed Compliance
This Triple is described by the following Functional View Functional Objects:
This Triple is described by the following Functional View Data Flows:
This Triple has the following triple relationships:
- (None-Data) - Secure Internet (ITS) (32)
- (None-Data) - OASIS MQTT (42)
- (None-Data) - OASIS AMQP (45)
ITS Application Entity
Click gap icons for more info.
OASIS MQTT DMP
IP Security Alternatives
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.
|Interoperability throughout the geopolitical region is highly desirable, but if implemented differently in different transportation management jurisdictions, significant benefits will still accrue in each jurisdiction. Regardless, this Information Flow Triple should be implemented consistently within a transportation jurisdiction (i.e., the scope of a regional architecture).
|Information Flow Security
|May include PII, identifying the vehicle and device.
|Malfunction reports will trigger repair-related actions, which if not taken will lead to an operator not properly monitored, and if taken in error will waste resources.
|Frequency is likely low, however when malfunctions happen this flow needs to operate or vehicles may not be properly repaired for extended periods. Considering the operating environment for many heavy vehicles, this could entail thousands of miles of operation without proper monitoring, which has a safety impact.