DCSA Reference Documentation / Standards / Standard Releases / Operational Vessel Schedules / Archive / Operational Vessel Schedules v3.0.0

DCSA OVS 3.0.0 - Introduction

Archived release: Operational Vessel Schedules v3.0.0 has been superseded. View the current v3 documentation.

This page is published as part of the complete documentation set for this version. The content has been updated to align with other standards; its intent and meaning remain unchanged.

Contents

What can you expect from the DCSA Interface Standard?

The DCSA Interface Standard aims at standardizing the communication between data consumers and data providers. For Operational Vessel Schedules, this means standardizing the exchange of vessel schedule information between vessel operators and operational stakeholders, such as shared service partners, terminals, and other relevant parties involved in operational planning.

While the standardised processes and terminology can be applied to any messaging media, such as email, EDI, or other forms of structured data exchange, APIs (Application Programming Interfaces) are the modern standard for interoperable digital data communication. APIs enable more consistent, automated, and timely exchange of operational vessel schedule information, supporting improved planning, reduced ambiguity, faster innovation, and better customer and partner experience. You can read more about the benefits of APIs here: The benefits of replacing EDI with APIs in container shipping.

In collaboration with its member carriers, DCSA has developed OpenAPI specifications supporting the use cases and user stories defined in the DCSA Interface Standards. The Operational Vessel Schedules OpenAPI specification is available to the general audience and developers for usage and feedback.

Suggested improvements

The DCSA Interface Standard is an evolving document, which will change as processes and best practices across the industry change. For this reason, DCSA is always interested in feedback that can improve the quality of published work and drive standardisation and digitalisation going forward. If you have any input, please use this form to provide your feedback.