Freight Equipment --> Fleet and Freight Management Center:
container seal status
Definitions
container seal status (Information Flow): The status of an electronic seal on a container, indicating sealing time, location, and authority, and any openings or tampering.
Freight Equipment (Source Physical Object): 'Freight Equipment' represents a freight container, intermodal chassis, or trailer and provides sensory, processing, storage, and communications functions necessary to support safe, secure and efficient freight operations. It provides equipment safety data and status and can alert the appropriate systems of an incident, breach, or tamper event. It also provides accurate position information to support in-transit visibility of freight equipment.
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) - Guaranteed Secure Wireless Internet (EU) (32)
- (None-Data) - Guaranteed Secure Wireless Internet (ITS) (32)
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 | True |
Cardinality | Unicast |
Initiator | Destination |
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 | High | |
Basis | Possibly competetive information. If available in aggregate or large scale to actors with competing interests to the actors legitimately involved with the container, information as to where the container is and is projected to be at different times could be abused to the actor's advantage.For high value containers, this may be HIGH. | Due to the nature of this information, it is impossible to be certain that what it states is true, thus it cannot have a HIGH integrity. However, it should be as accurate as possible. | Other triples using this flow may consider this MODERATE because it is in a wireless environment. That is unlikely to be the case here, so best to remove as much variability in the eventual conveyence of this information, thus HIGH. |
Security Characteristics | Value |
---|---|
Authenticable | True |
Encrypt | True |