Commercial Vehicle OBE --> Fleet and Freight Management Center:
on-board vehicle data
Definitions
on-board vehicle data (Information Flow): Information about the commercial vehicle stored on-board (for maintenance purposes, gate access, cargo status, lock status, etc.). The request 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.
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:
- CVO01: Carrier Operations and Fleet Management
- CVO02: Freight Administration
- CVO11: Freight Drayage Optimization
This triple is associated with the following Functional Objects:
- CV Driver Work Records
- CV On-Board Access Monitoring
- CV On-Board Drayage Support
- CV On-Board Mass Monitoring
- CV On-Board Speed Monitoring
- CV On-Board Trip Monitoring
- Fleet Administration
- Fleet Maintenance 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
- (None-Data) - Secure Wireless Internet (EU) (32)
- (None-Data) - Secure Wireless Internet (ITS) (32)
- (None-Data) - Apache Kafka over Wireless (36)
- (None-Data) - OMG DDS over Wireless (36)
- (None-Data) - OASIS MQTT over Wireless (42)
- (None-Data) - OASIS AMQP over Wireless (45)
Selected Solution
Solution Description
ITS Application Entity
Development needed |
Click gap icons for more info.
|
||
Mgmt
|
Facilities
Development needed |
Security
|
|
TransNet
|
|||
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 | Regional |
Acknowledgement | False |
Cardinality | Unicast |
Initiator | Source |
Authenticable | True |
Encrypt | True |
Interoperability | Description |
---|---|
Local | In cases where an interface is normally encapsulated by a single stakeholder, interoperability is still desirable, but the motive is vendor independence and the efficiencies and choices that an open standards-based interface provides. |
Security
Information Flow Security | ||||
---|---|---|---|---|
Confidentiality | Integrity | Availability | ||
Rating | Moderate | Moderate | Moderate | |
Basis | Contains identifiers, location and other data related to freight systems. Interception of this information would compromise the owner and/or operator of the commercial vehicle. | Sensitivity of data will vary depending on what is being requested and what the commercial vehicle is carrying. In the most extreme case this could be data describing the condition of a hazardous material, which should be correct and timely to avoid the FFMC erroneously taking emergency-related actions. | Sensitivity of data will vary depending on what is being requested and what the commercial vehicle is carrying. In the most extreme case this could be data describing the condition of a hazardous material, which should be correct and timely to avoid the FFMC erroneously taking emergency-related actions. |
Security Characteristics | Value |
---|---|
Authenticable | True |
Encrypt | True |