Commercial Vehicle Service Provider Center --> Fleet and Freight Management Center:
driver log
Definitions
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.
Fleet and Freight Management Center (Destination Physical Object): The 'Fleet and Freight Management Center' provides the capability for commercial drivers and fleet-freight managers to receive real-time routing information and access databases containing vehicle and/or freight equipment locations as well as carrier, vehicle, freight equipment and driver information. The 'Fleet and Freight Management Center' also provides the capability for fleet managers to monitor the safety and security of their commercial vehicle drivers and fleet.
Included In
This Triple is in the following Service Packages:
This triple is associated with the following Functional Objects:
- CVOBE-SP Information Exchange
- CVOBE-SP Safety and Security Administration
- Fleet Driver Log Management
- Freight Administration and Management
This Triple is described by the following Functional View Data Flows:
This Triple has the following triple relationships:
| None |
Communication Solutions
-
US: SAE J3067 (J2735 SE) - Secure Internet (ITS) (22)
-
(None-Data) - Secure Internet (ITS) (43)
Selected Solution
US: SAE J3067 (J2735 SE) - Secure Internet (ITS)Solution Description
|
ITS Application Entity
 
SAE J3067  |
Click gap icons for more info.
|
||
|
Mgmt
|
Facilities
SAE J2945 |
Security
|
|
|
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 | Regional |
| Acknowledgement | True |
| Cardinality | Unicast |
| Initiator | Source |
| Authenticable | True |
| Encrypt | True |
| Interoperability | Description |
|---|---|
| Regional | 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). |
Security
| Information Flow Security | ||||
|---|---|---|---|---|
| Confidentiality | Integrity | Availability | ||
| Rating | High | High | Moderate | |
| Basis | 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. | |
| Security Characteristics | Value |
|---|---|
| Authenticable | True |
| Encrypt | True |