Back to roadmapBack to list

Port call optimization

The purpose of Port Call Optimisation (PCO) is to make such visits by vessels take place as safely and efficiently as possible.

DigitalisationMarine shipping

Introduction

By ensuring consistent and interoperable data exchange across ports and ships, Port Call Optimization (PCO) can improve operational efficiency, contribute to more sustainable operations and reduce unnecessary waiting time for vessels that causes further disruption along the supply chain. The IAPH and IHMA have developed a guide outlining the fundamentals of PCO (see References). While port calls can be further advanced in creating an optimized port call, this factsheet focuses on the starting point defined in the IAPH & IHMA guide: a standardized framework for the electronic exchange of a minimum, high-value set of port call data.

Value proposition

  • Better informed decisionmaking

  • Better management of resources

  • Increase operational efficiency

  • Eliminate unnecessary waiting time

  • Reduce GHG emissions

  • Reduce operational costs

Actors in the port call process are faced with different data in different formats and standards from multiple sources on a daily basis. This makes it difficult to operate ships in a safe and sustainable manner. Port calls can be optimized through the provision of standardized, accurate, and timely information, creating a shared and transparent view of the port call process. While improved data exchange alone delivers limited benefits, it enables stakeholders to make better-informed decisions and adjust their planning and operations accordingly. Therefore, it supports better management of assets, resources, and personnel, improves safety and regulatory compliance, and can increase operational efficiency. It can eliminate unnecessary waiting time that causes disruptions across the supply chain. As a result, PCO may reduce emissions and operational costs for shipping lines, shippers, terminals, ports, and nautical service providers involved in safe arrivals and departures.

Port applicability

PCO, as described in de IAPH & IHMA guide, is applicable to all ports accommodating SOLAS ships. Currently, it is not applicable to inland shipping, although the data network may be expanded to barge and other modalities in a later stage, when PCO has been implemented successfully for marine vessels.

Groups of innovations

  • There are no groups identified within this solution.

Impact

Impact level per aspect
ImpactLevelRemark
SafetyMedium impact
Increased safety by accurate and timely information provision.
Lower energy consumptionLimited impact
By optimizing port calls, ships can sail more efficiently within the port passage planning area, decreasing energy consumption.
GHG emissionsLimited impact
By optimizing port calls, ships can sail more efficiently within the port passage planning area, reducing GHG emissions
Digital port ecosystemLarge impact
PCO can strengthen the digital port ecosystem by enabling standardized, interoperable data exchange between ports and multiple users through a single interface. This reduces system fragmentation and supports scalable digital services across the maritime value chain.
Operational efficiencyLarge impact
Standardized formatting prevents errors and enhanced efficiency. Optimal planning reduces unnecessary waiting times.
International cooperationLimited impact
Standardized data formatting supports international cooperation.

Port characteristics

Ports should get their data base well organized, in such a way that the correct data can be shared with other parties.

Barriers and enablers

Enablers

  • Standards & regulationEnabler

    PCO uses international standards proposed by the IMO, IHO and ISO to ensure interoperability and global consistency.

Barriers

  • Stakeholder interactionBarrier

    In realizing Just In Time operations, the coordination between the berth and the port planning is crucial. Data sharing between port planner and berth planner can be a challenge, as the berth planner is often a private organization and the port planner a public organization.

  • TechnologyBarrier

    The complexity of implementation of PCO depends on the size and data maturity of the port.

How to implement?

  1. Step 1

    Identify all sources of data and establish a single point of truth

    Port planner

  2. Step 2

    Compare the data model to the international data model and adjust where necessary

    Port planner

  3. Step 3

    Create API to fit the API testbed of the IHO

    Port planner

  4. Step 4

    Apply to the IHO testbed to verify the data on completeness and accuracy

    Port planner

  5. Step 5

    If approved, the port is conneted to the PCO network and monitored by the IHO

    IHO

  6. Step 6

    Increasing the operational efficiency using PCO

    All stakeholders

Timeline

The arrow below represents the expected development of the TRL of port call optimization.
* Technical Readiness Level

What should a port do in the next 3 years?

The implementation of PCO requires that: 1. Terminals and berths have consistent identification, as names often change or are misspelled. The Global Location Number (GLN) offers a globally unique reference code to exchange data from terminals and berths. 2. The Planned Time of Arrival Pilot Boarding Place and Planned Time of Departure Berth are available for SOLAS ships The PCO network for the electronic exchange of a minimum, high-value set of port call data is ready for implementation in a large number of ports. The dataset defines the minimum required information, providing a practical starting point for adoption by ports. Over time, this can be expanded with additional data elements and applied to a broader range of modalities across the supply chain, like barge transport.

Investment overview

Investments can be found in improving the data quality (creating single point of truth) and building the API connection to the PCO Network (the latter are minor cost). There are no specific investments needed to be connected to the PCO Network.

Stakeholder overview

Below is an overview of the required involved stakeholders.
Blue stakeholders are essential, white stakeholders are enabling

Knowledge base