From f61c58f83fe36e76926c9e4806c106da1522ea3f Mon Sep 17 00:00:00 2001 From: "henrik.larsen@dcsa.org" Date: Fri, 19 Sep 2025 13:23:02 +0200 Subject: [PATCH 1/2] JIT 2.0: SD-2448: Rename Just in Time -> Port Call (JIT) --- jit/v2/JIT_v2.0.0.yaml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/jit/v2/JIT_v2.0.0.yaml b/jit/v2/JIT_v2.0.0.yaml index df515bece..2249e14da 100644 --- a/jit/v2/JIT_v2.0.0.yaml +++ b/jit/v2/JIT_v2.0.0.yaml @@ -2,10 +2,10 @@ openapi: 3.0.3 info: version: 2.0.0 title: | - DCSA Just in Time Port Calls API + DCSA Port Calls (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). From 7c0992c1b61a4421e0be455ff884c15b7ddd49fb Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Henrik=20Helm=C3=B8=20Larsen?= Date: Fri, 19 Sep 2025 13:28:06 +0200 Subject: [PATCH 2/2] Fix typo --- jit/v2/JIT_v2.0.0.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/jit/v2/JIT_v2.0.0.yaml b/jit/v2/JIT_v2.0.0.yaml index 2249e14da..a82951843 100644 --- a/jit/v2/JIT_v2.0.0.yaml +++ b/jit/v2/JIT_v2.0.0.yaml @@ -2,7 +2,7 @@ openapi: 3.0.3 info: version: 2.0.0 title: | - DCSA Port Calls (JIT) API + DCSA Port Call (JIT) API description: | # 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.