Commercial Vehicle OBE --> Commercial Vehicle Check Equipment:
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 OBE (Source Physical Object): The Commercial Vehicle On-Board Equipment (OBE) resides in a commercial vehicle and provides the sensory, processing, storage, and communications functions necessary to support safe and efficient commercial vehicle operations. It provides two-way communications between the commercial vehicle drivers, their fleet managers, attached freight equipment, and roadside officials. A separate 'Vehicle OBE' physical object supports vehicle safety and driver information capabilities that apply to all vehicles, including commercial vehicles. The Commercial Vehicle OBE supplements these general ITS capabilities with capabilities that are specific to commercial vehicles.
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.
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
- US: SAE J3067 (J2735 SE) - Local Unicast Wireless (1609.2) (19)
- (None-Data) - Local Unicast Wireless (EU) (54)
Selected Solution
Solution Description
ITS Application Entity
SAE J3067 |
Click gap icons for more info.
|
||
Mgmt
Addressed Elsewhere |
Facilities
SAE J2945 |
Security
|
|
TransNet
IEEE 1609.3 |
|||
Access
|
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 | Local |
Acknowledgement | True |
Cardinality | Unicast |
Initiator | Source |
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 | 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 |