Intermodal Customer System --> Fleet and Freight Management Center:
breach response
Definitions
breach response (Information Flow): This is an Intermodal Freight Shipper's response to a breach or tamper event of their freight equipment. There maybe instructions for handling of the shipment, possible re-routing or pickup.
Intermodal Customer System (Source Physical Object): The 'Intermodal Customer System' represents organizations that engage in the shipment of freight, either originator (consigner or shipper) or recipient of the cargo shipment. They enable the movement of goods on routes that require the use of other modes of transportation such as heavy rail, air, sea, etc. The Intermodal Customer System includes those personnel responsible for the movement of freight across international borders.
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:
This Triple is described by the following Functional View Data Flows:
This Triple has the following triple relationships:
None |
Communication Solutions
- (None-Data) - Secure Internet (ITS) (43)
- (None-Data) - Apache Kafka (44)
- (None-Data) - OMG DDS (44)
- (None-Data) - OASIS MQTT (50)
- (None-Data) - OASIS AMQP (61)
Selected Solution
Solution Description
ITS Application Entity
Development needed |
Click gap icons for more info.
|
||
Mgmt
|
Facilities
Development needed |
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 | Moderate | High | Moderate | |
Basis | Indicates a commercial vehicle safety or security event response that a hostile third party might use to cause harm to the shipper. | Response to any kind of emergency, safety or security event needs to be timely and correct to minimize negative consequences of the event. This flow contains high-priority information that may affect safety of life for vehicle operators. Loss, corruption or modification of this flow could hamper response, which would have a severe impact on those operators. | Response to any kind of emergency, safety or security event needs to be timely and correct to minimize negative consequences of the event. |
Security Characteristics | Value |
---|---|
Authenticable | True |
Encrypt | True |