Commercial Schedules 1.0
Standard documentation
What can you expect from the DCSA interface standard for Commercial Schedules 1.0?
DCSA and its member carriers have published the DCSA standard for Commercial Schedules for the global container shipping industry. This standard is designed to expand the scope of applicability of OVS by providing to BCOs, LSPs, and Platforms with three alternatives to consume schedules from carriers. With these standards in place, carriers can digitally share point-to-point routings, port schedules, and vessel schedules. The aim is to ensure that the end-user experience remains consistent across all industry participants who use these standards. This will provide transparency, efficiency, and enable better planning and optimisation of shipping activities.
As part of the Commercial Schedules standard, DCSA has also published CS OpenAPI definitions on SwaggerHub, an open–source API development platform. The OpenAPI definitions for Commercial Schedules follow the DCSA API design principles. Carriers can use the definitions to implement DCSA standard-compliant APIs rapidly. Documentation on the Operational Vessel Schedules standard, including versioning guidance, can be found on GitHub.
Commercial schedule 1.0
Suggested improvements
The DCSA Interface Standard is an evolving document, which will change as processes and best practises 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 the feedback form to provide your feedback
Commercial Schedules documents
Below an overview of all documentation for the different releases. Make sure to always adopt the latest release.
2024
Ready to adopt?
Whether you are a cargo owner, solution provider, or ocean carrier interested in implementing an API based on this standard, go to the Developer Portal or reach out to us for additional information.
Ready to adopt?
Whether you are a cargo owner, solution provider, or ocean carrier interested in implementing an API based on this standard, go to the Developer Portal or reach out to us for additional information.
