Freight Distribution and Logistics Center --> Vessel Service Provider Center:
vessel services request

Definitions

vessel services request (Information Flow): Request from a vessel or carrier system for port services required to support vessel arrival, berthing, servicing, or departure. Typical services include piloting, towing, mooring, bunkering, and other port support services. This information supports service coordination between vessels, port operators, and vessel service providers.

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.

Vessel Service Provider Center (Destination Physical Object): 'Vessel Service Provider Center' routinely provides a service or supplies to vessels to facilitate their operations and/or meet regulatory requirements. Vessel service providers include vessel pilots, tug boats, bunker (fueling) providers, ship chandlers, waste reception, inspection services, vessel agents, and others.

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:

Communication Solutions

Solutions are sorted in ascending Gap Severity order. The Gap Severity is the parenthetical number at the end of the solution.

Selected Solution

(None-Data) - Guaranteed Secure Internet (ITS)

Solution Description

This solution is used within Australia, Canada, the E.U. and the U.S.. It combines standards associated with (None-Data) with those for I-I: Guaranteed Secure Internet (ITS). The (None-Data) standards include an unspecified set of standards at the upper layers. The I-I: Guaranteed Secure Internet (ITS) standards include lower-layer standards that support secure communications with guaranteed delivery between ITS equipment using X.509 or IEEE 1609.2 security certificates.

ITS Application Entity
Mind the gapMind the gapMind the gap

Development needed
Click gap icons for more info.

Mgmt
Facilities
Mind the gap

Development needed
Security
Mind the gapMind the gap
TransNet

IP Alternatives
IETF RFC 9293
Access

Internet Subnet Alternatives
TransNet TransNet

TempBCL2 TempSTDL2

TempBCL3 TempSTDL3

TempBCL4 TempSTDL4

TempBCL5 TempSTDL5

Access Access

TempBCL2 TempSTDL2

TempBCL3 TempSTDL3

TempBCL4 TempSTDL4

TempBCL5 TempSTDL5

ITS Application ITS Application

TempBCL2 TempSTDL2

TempBCL3 TempSTDL3

TempBCL4 TempSTDL4

TempBCL5 TempSTDL5

Mgmt Mgmt

TempBCL2 TempSTDL2

TempBCL3 TempSTDL3

TempBCL4 TempSTDL4

TempBCL5 TempSTDL5

Facility Facility

TempBCL2 TempSTDL2

TempBCL3 TempSTDL3

TempBCL4 TempSTDL4

TempBCL5 TempSTDL5

Security Security

TempBCL2 TempSTDL2

TempBCL3 TempSTDL3

TempBCL4 TempSTDL4

TempBCL5 TempSTDL5

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

CharacteristicValue
Time Context Recent
Spatial Context Regional
Acknowledgement True
CardinalityUnicast
InitiatorSource
AuthenticableTrue
EncryptTrue


InteroperabilityDescription
RegionalInteroperability 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 High High
Basis Could be operationally sensitive. Must be timely and correct to ensure proper harbor navigation, docking and other service fulfillment, or schedules and port operations may be significantly impacted. Must be timely and correct to ensure proper harbor navigation, docking and other service fulfillment, or schedules and port operations may be significantly impacted.


Security CharacteristicsValue
AuthenticableTrue
Encrypt True