driver log (Information Flow): A daily log showing hours in service for the current driver. The query flow is not explicitly shown.
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 Check Equipment (Destination Physical Object): 'Commercial Vehicle Check Equipment' 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. Commercial Vehicle Check Equipment also provides supplemental inspection services such as 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.
This Triple is in the following Service Packages:
This Triple is described by the following Functional View Functional Objects:
- CVCE Safety and Security Inspection
- CVOBE-SP Information Exchange
- CVOBE-SP Safety and Security Administration
This Triple is described by the following Functional View Data Flows:
This Triple has the following triple relationships:
- US: SAE J3067 (J2735 SE) - Secure Internet (ITS) (19)
- (None-Data) - Secure Internet (ITS) (32)
ITS Application Entity
Click gap icons for more info.
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
|Driver log contains PII, personal identification and work conditions and by definition, log of hours worked. This is personal and competitive with regulatory use. It should be available only to the intended recipient.
|Driver log data is covered under commercial regulatory schemes in most jurisdictions. Forgery of driver log data would have significant competitive implications, not to mention being a regulatory violation.
|There are alternative mechanisms for exchanging the driver log, though all have a negative impact on the driver's time, which is why MODERATE and not LOW.