Freight Distribution and Logistics Center --> Intermodal Terminal:
vessel estimated time of arrival
Definitions
vessel estimated time of arrival (Information Flow): The estimated date and time that a vessel is expected to arrive at its destination port. This information may originate from vessel systems, carrier operational systems, or voyage scheduling systems and is used to support berth planning, terminal preparation, and port operational coordination.
Freight Distribution and Logistics Center (Source Physical Object): The 'Freight Distribution and Logistics Center' provides intermodal logistics support and support for the efficient distribution of freight across transport systems and modes. This can include consolidation arrangements, warehousing, information sharing systems, and consignor-to-consignee intermodal shipping arrangements. These capabilities may be provided as part of intermodal fleet management activities or can be provided by an independent logistics specialist.
These systems may also include centralized platforms that coordinate vessel operations, cargo documentation, ground transport reservations, and operational information exchange among vessels, terminals, cargo owners, transport operators, and other port stakeholders to support efficient and coordinated port and intermodal freight operations.
Intermodal Terminal (Destination 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.
Included In
This Triple is in the following Service Packages:
This triple is associated with the following Functional Objects:
- FDLC Port Community Information Sharing
- FDLC Vessel Tracking and Monitoring
- Maritime Terminal Management
This Triple is described by the following Functional View Data Flows:
- None
This Triple has the following triple relationships:
| None |
Communication Solutions
-
Port: vessel eta/etd - Secure Internet (ITS) (0)
-
(None-Data) - Secure Internet (ITS) (43)
Selected Solution
Port: vessel eta/etd - Secure Internet (ITS)Solution Description
|
ITS Application Entity
DCSA Operational Vessel Schedules ![]() ANSI X12 TS323 ![]() |
Click gap icons for more info.
|
||
|
Mgmt
|
Facilities
|
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 | False |
| 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 | Low | Moderate | Low | |
| Basis | This information can be computed based on observation. | Will be used for planning, so should be correct and timely. If incorrect could have an outsize ripple effect, but the lead time here is large given vessel speeds, thus MODERATE integrity and LOW availability. | Will be used for planning, so should be correct and timely. If incorrect could have an outsize ripple effect, but the lead time here is large given vessel speeds, thus MODERATE integrity and LOW availability. | |
| Security Characteristics | Value |
|---|---|
| Authenticable | True |
| Encrypt | False |

