DCSA Reference Documentation / Standards / Standard Releases / Operational Vessel Schedules / Archive / Operational Vessel Schedules v3.0.2
DCSA OVS 3.0.2 - Changelog
Archived copy: This immutable copy preserves Operational Vessel Schedules v3.0.2. View the current v3 documentation.
Contents
Version 3.0.2 - 2026-06-12
Add facilityTypeCode to timestamps to support ETA Pilot Boarding Place. This change enables carriers to include ETA Pilot Boarding Place in OVS by adding facilityTypeCode to the timestamp object. Timestamps can then be qualified as BRTH for berth or PBPL for pilot boarding place, with BRTH as the default when omitted to preserve backward compatibility. This allows ETA PBP to be exchanged together with the relevant vessel schedule and terminal call information, avoiding the need for a separate API.
Add an optional responseScope query parameter to control whether full voyages or only matched transport calls are returned. This change enables API consumers to control whether the Service Schedules endpoint returns the full matched voyage or only the transport calls matching the query parameters. The optional parameter, responseScope, supports FULL_VOYAGE and MATCHED_CALLS. If omitted, the value must be interpreted as FULL_VOYAGE to preserve backward compatibility.
Version 3.0.1 - 2025-11-14
Added property delayReasonCodes to support Multiple Delay Reasons per timestamp. This property takes precedence over delayReasonCode (if both are present - only the ones provided in delayReasonCodes property are used). Deprecated delayReasonCode from 3.0.1 onward. This allows OVS implementers to submit multiple delay reasons for a timestamp to reflect real-world situations where multiple causes apply.
Added property statusCodes to support multiple status codes per transport call. This property takes precedence over statusCode (if both are present - only the ones provided in statusCodes property are used). This property also supports the codes: DRYD (Dry Dock), BUNK (Bunkering), OOSV (Out of service) Deprecated statusCode from 3.0.1 onward. This allows OVS implementers to submit multiple statuses for a transport call to reflect real-world situations where multiple statuses apply.
The API specification includes a recommendation to follow for the naming of dummy vessels. Applies to properties: vesselName, isDummyVessel. This allows carriers to distinguish between dummy vessels in the same schedule.
Relax Import Voyage Number constraint by defining a no voyage number value = 9999R. This allows carriers to provide a “no voyage number” import voyage number in edge cases (e.g., dry dock), without failing validation.
The API specification includes more detail in the property eventClassifierCode for clarification of classifier use, which remains aligned with the OVS Definitions document. Give further guidance in the API on when to send planned, estimated, and actual timestamps and semantics so the user can align expectations with partners.
Added MMSINumber property as a query parameter and an optional property in the payload. This allows carriers to provide an MMSI number when available when an IMO is or not available.
Added vesselOperatorSMDGLinerCode as an optional filter. This allows filtering schedules’ requests based on the vessel operator SMDG liner code.
Adjusted pagination. Specified what limit does and added the Next-Page-Cursor header for the next page.
Version 3.0.0 - December 2023
N/A.