Vessel Systems --> Freight Distribution and Logistics Center:
berth availability request
Definitions
berth availability request (Information Flow): Request from a vessel or carrier system to determine or coordinate berth availability at a destination port. This includes vessel identification, estimated time of arrival, and berth scheduling information necessary to support berth allocation and port operational planning.
Vessel Systems (Source Physical Object): 'Vessel Systems' resides on a vessel and provides the processing, storage, and communications functions that support vessel operations. A vessel is a general classification of maritime vehicles that includes ships, barges, and boats. In ARC-IT we are focused on vessels that provide marine transport of cargo, including containerized cargo, bulk cargo, and vehicles.
Freight Distribution and Logistics Center (Destination 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.
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
Characteristics
| Characteristic | Value |
|---|---|
| Time Context | Recent |
| Spatial Context | Continental |
| 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 | All port status information can be considered competitive and sensitive from a physical security standpoint. While many flows describe information that could be ascertained using aerial photography or other in-person methods, widespread availability of port status may impact national security. | This flow contains operational status information that if incorrect, could lead to a vessel making a decision that is impractical and causes a loss of time and/or money. The information contained in the message must be correct and available to avoid such loss. | This flow contains operational status information that if incorrect, could lead to a vessel making a decision that is impractical and causes a loss of time and/or money. The information contained in the message must be correct and available to avoid such loss. | |
| Security Characteristics | Value |
|---|---|
| Authenticable | True |
| Encrypt | True |