Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
ISO 28005-3:2024 Electronic Port Clearance — Ship and Port Operation Data Elements
Operational data exchange specifications for efficient port call execution and coordination
ISO 28005-3:2024 extends the core data dictionary established in ISO 28005-2 with additional data elements specifically required for ship and port operational processes during a vessel’s stay in port. This standard addresses the detailed operational data exchange needs that arise during port calls, including pilotage, towage, mooring, bunkering, waste disposal, ship repairs, stores provisioning, crew changes, port service requests, and other operational interactions that occur between the vessel and various port service providers.
While ISO 28005-2 covers the minimum data required for port clearance formalities mandated by the IMO FAL Convention, ISO 28005-3 adds the operational data elements that enable efficient port call execution and coordination among multiple service providers.
Operational Data Categories and Stakeholder Requirements
ISO 28005-3 defines data elements for operational processes organized into six major categories: port service requests (pilotage, tugboats, mooring, line handling), supply chain logistics (bunker fuel specifications, fresh water, provisions, spare parts), waste management (MARPOL Annex categories I through VI, disposal manifests, reception facility coordination), repair and maintenance (dry dock scheduling, classification society surveys, repair specifications), crew logistics (shore leave, repatriation, medical assistance, crew change transport), and port authority interactions (security screenings, safety inspections, gangway monitoring).
| Operational Domain | Key Data Elements | Primary Stakeholders |
|---|---|---|
| Pilotage and Towage | Pilot boarding time and position, tug count and bollard pull, mooring line configuration, berth assignment | Pilot authority, tug operators, mooring gang, port traffic control |
| Bunkering Operations | Fuel type and ISO 8217 grade, quantity in metric tons, delivery method (barge or truck), sulfur content, bunker delivery note reference | Bunker suppliers, port authority, customs, environmental protection |
| Ship Waste Management | Waste category per MARPOL Annex, estimated quantity, storage capacity remaining, reception facility booking, disposal certificate | Waste contractors, port environmental office, flag state |
| Vessel Repairs and Surveys | Repair description and classification, estimated duration, classification society, survey type and due date, dry dock dimensions required | Repair yards, classification societies, equipment suppliers |
| Crew Logistics | Crew member identity details, joining or leaving flag, transport mode and schedule, visa status, medical fitness certificate | Immigration, crew manning agencies, airlines, medical services |
Operational data elements have complex interdependencies that require event-driven processing. For example, a bunkering request may simultaneously trigger customs notification, environmental monitoring alerts, safety zone establishment, and fire service standby activation.
Event-Driven Architecture and Real-Time Data Exchange
A significant engineering advancement in ISO 28005-3 is the specification of event-driven data exchange patterns using publish-subscribe messaging. Rather than requiring all operational data to be submitted in batch format, the standard defines event types with associated data payloads, priority levels (critical, normal, informational), and acknowledgment requirements. Time-critical events such as medical emergencies, security incidents, or pollution events use the highest priority level with mandatory acknowledgment within specified timeframes. The standard also specifies webhook callback patterns for real-time notifications.
Ports implementing ISO 28005-3 operational data exchange report 30-50% improvement in port call execution efficiency. The standardized operational data flows eliminate telephone and email coordination, reduce waiting times, and enable automated service provider scheduling.
Integration with Port Community Systems and Maritime Single Windows
ISO 28005-3 is designed for seamless integration with Port Community Systems and maritime single window platforms. The standard provides detailed mapping guidance between its data elements and those used in common PCS implementations worldwide, including alignment with IMO FAL Compendium data sets and EU Maritime Single Window environment requirements. This interoperability focus ensures that operational data flows seamlessly across different port systems, national boundaries, and regulatory jurisdictions, supporting the maritime industry’s digitalization objectives.
Q: What is the relationship between ISO 28005-3 and the IMO FAL Convention?
A: ISO 28005-3 extends the mandatory IMO FAL data set with operational elements not covered by the convention while maintaining full backward compatibility with all FAL data requirements.
A: ISO 28005-3 extends the mandatory IMO FAL data set with operational elements not covered by the convention while maintaining full backward compatibility with all FAL data requirements.
Q: How are data updates handled when operational plans change during a port call?
A: The standard supports data versioning with timestamp tracking and revision history. Updates to previously submitted data are managed through formal amendment messages that maintain complete audit trails.
A: The standard supports data versioning with timestamp tracking and revision history. Updates to previously submitted data are managed through formal amendment messages that maintain complete audit trails.
System Architecture and Implementation Planning
Implementing ISO 28005-3 operational data exchange requires a service-oriented architecture that supports both synchronous request-response and asynchronous publish-subscribe communication patterns. The recommended architecture includes an API gateway for message routing and authentication, a message broker for event distribution, a data transformation service for protocol conversion, and a monitoring dashboard for operational visibility. The standard provides reference architecture diagrams and implementation patterns that ports can adapt to their existing infrastructure.
The implementation should follow a phased approach starting with the highest-value operational domains, typically port service requests and waste management, which offer immediate efficiency gains. Secondary domains such as repair coordination and crew logistics can be added in subsequent phases. Each phase includes stakeholder onboarding, system integration testing, user training, and operational validation before proceeding to the next domain.
Q: What middleware technologies are recommended for event-driven operational data exchange?
A: The standard supports common messaging protocols including AMQP, MQTT, and WebSocket for real-time event distribution. Message queuing with guaranteed delivery is recommended for critical operational notifications.
A: The standard supports common messaging protocols including AMQP, MQTT, and WebSocket for real-time event distribution. Message queuing with guaranteed delivery is recommended for critical operational notifications.
Q: How is data security maintained across multiple operational stakeholders?
A: Role-based access control with data segmentation ensures that each stakeholder can only access operational data relevant to their function. All data exchanges are encrypted and logged.
A: Role-based access control with data segmentation ensures that each stakeholder can only access operational data relevant to their function. All data exchanges are encrypted and logged.
Performance Monitoring and Continuous Optimization
ISO 28005-3 recommends establishing key performance indicators for operational data exchange, including message delivery times, system availability, data quality metrics, stakeholder satisfaction, and time savings in port call execution. These KPIs should be monitored through dashboards and reviewed regularly to identify optimization opportunities. The standard also supports data analytics approaches where historical operational data can be analyzed to identify patterns, predict service demand, and optimize resource allocation across port services.
Benefits of Standardized Operational Data Exchange
The implementation of ISO 28005-3 brings measurable benefits to port stakeholders. Shipping agents report reduced communication effort, port authorities gain better visibility of port operations, service providers can optimize resource allocation, and ship operators experience shorter port turnaround times. The standard’s event-driven architecture also enables the development of value-added services such as real-time port call optimization, predictive berth scheduling, and automated service coordination.
