Skip to content

JIT 2.0: SD-2448: Rename Just in Time -> Port Call (JIT) #556

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
HenrikHL merged 2 commits into from
Sep 19, 2025
Merged

JIT 2.0: SD-2448: Rename Just in Time -> Port Call (JIT) #556

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
f61c58f
JIT 2.0: SD-2448: Rename Just in Time -> Port Call (JIT)
HenrikHL Sep 19, 2025
7c0992c
Fix typo
HenrikHL Sep 19, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions jit/v2/JIT_v2.0.0.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,10 +2,10 @@ openapi: 3.0.3
info:
version: 2.0.0
title: |
DCSA Just in Time Port Calls API
DCSA Port Call (JIT) API
description: |
# DCSA OpenAPI specification for Just in Time Port Call process
The DCSA API for **Just In Time Port Call** aims to simplify and standardize the exchange of operational information between carriers, terminals, port authorities, and service providers, to orchestrate and optimize port calls. JIT can be used for negotiating services execution via timestamps, informing timestamps, or informing moves forecasts, between the parties involved in any given location.
# DCSA OpenAPI specification for Port Call (JIT) process
The DCSA API for **Port Call (JIT)** aims to simplify and standardize the exchange of operational information between carriers, terminals, port authorities, and service providers, to orchestrate and optimize port calls. JIT can be used for negotiating services execution via timestamps, informing timestamps, or informing moves forecasts, between the parties involved in any given location.

The planning and execution of events always follow the same pattern, in which several instances of the estimated (`E`), requested (`R`), and planned (`P`) times (from now on referred to as: `ERP`-pattern) can occur if a new estimated or requested time is given after the initially planned time. Some events, specified in this document, do not need the `ERP`-pattern, as they are informative and reflect actuals (`A`) only (i.e. vessel readiness for cargo operations).

Expand Down