Fleet and Freight Management Center --> Freight Consolidation Station:
container pickup confirmation
Definitions
container pickup confirmation (Information Flow): Notice confirming that a container has been picked up at an intermodal facility and that control has been transferred to a shipping or drayage agency.
Fleet and Freight Management Center (Source 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.
Freight Consolidation Station (Destination Physical Object): The 'Freight Consolidation Station' is an intermediate point (usually an intermodal terminal located at a port) prior to (or after) container-based shipping, where less-than-container load or less-than-truckload cargoes are consolidated into full container loads (or full containers are disbursed), for cost-effective intermodal shipping.
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:
- None
This Triple has the following triple relationships:
None |
Communication Solutions
- (None-Data) - Secure 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
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 | 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 | 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 |