Intermodal Terminal --> Fleet and Freight Management Center:
container delivery confirmation
Definitions
container delivery confirmation (Information Flow): Notice confirming the arrival and transfer of control of a container at a container handling facility, for example an intermodal terminal.
Intermodal Terminal (Source Physical Object): The 'Intermodal Terminal' represents the terminal areas corresponding to modal change points. This includes interfaces between roadway freight transportation and air, rail, and/or water shipping modes. The basic unit of cargo handled by the Intermodal Terminal physical object is the container; less-than-container load handling is typically handled at a different facility (i.e., Freight Consolidation Station). The Intermodal Terminal can include electronic gate control for entrance and exit from the facility, automated guidance of vehicles within the facility, alerting appropriate parties of container arrivals and departures, and inventory and location of temporarily stored containers.
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
- US: UBL - Secure Internet (ITS) (7)
- (None-Data) - Secure Internet (ITS) (32)
Selected Solution
Solution Description
ITS Application Entity
OASIS UBL |
Click gap icons for more info.
|
||
Mgmt
|
Facilities
W3C XML OASIS UBL |
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 | Local |
Acknowledgement | True |
Cardinality | Unicast |
Initiator | Destination |
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 | Moderate | Moderate | |
Basis | Container status information may be competitive but certainly is trackable data, and needs to be obfuscated to avoid such tracking or business-related espionage. | Container status information should be correct in real-time, or pickup, delivery and related activities will be confused and slowed, creating supply chain issues and mobility problems. | Container status information should be correct in real-time, or pickup, delivery and related activities will be confused and slowed, creating supply chain issues and mobility problems. |
Security Characteristics | Value |
---|---|
Authenticable | True |
Encrypt | True |