Skip to content

Hamburg Port — logistics twin#

Liaison: Cartagena / ERTICO · Supporter: Hamburg Port Authority (supporting stakeholder, letter of support) · Profile owner: to be confirmed · LDT-UC-04 · Status: 🔴 needs owner confirmation

1–2 · Identity, problem & context#

The Hamburg port logistics twin, with Hamburg Port Authority (supporting stakeholder, letter of support), joins the LDT as an operational/commercial twin, demonstrating interconnection with heavy-logistics data (vessel/hinterland flows, emissions) and the replication path for port-city ecosystems.

3–5 · Objectives, stakeholders, data#

Needs owner — liaison (Cartagena / ERTICO) with Hamburg Port Authority (supporting stakeholder, letter of support).** This profile has no confirmed owner, and six weeks after the v0.5 deadline that is itself becoming a decision by default. The scheme needs four things, in this order:

  1. Who signs. An accession agreement needs a signatory. If the Port participates only as a supporter, the scheme needs the lightweight Observer/associate accession described in section 6 — and that document does not exist.
  2. What flows. Which datasets or indicators move to and from the LDT. The profile's own position is that commercial logistics data stays restricted and only derived indicators cross, which is workable but unconfirmed.
  3. ESRI-stack interoperability. The interconnection must remain non-ESRI-portable per the funder recommendation (Annex 9) — in this scheme that is a general portability rule, not a vendor objection. Needed: which interfaces are open and documented.
  4. Whether to proceed at all. If the Port's effort cannot be secured, the honest course is to record Hamburg as out of scope for PD4 rather than carry it as pending — see Use case development section 8.

6 · Sharing rules this use case needs from the scheme#

  • Supporter/observer participation form: the scheme must define a lightweight Observer/associate accession for supporters that consume/contribute limited data without full membership.
  • Commercial logistics data under restricted tier with derived-indicator publication rights.

7–12 · Architecture, timeline, value, risks#

Proposed Pending the scoping call, the scheme's drafting position:

  • Architecture — the lightest interconnection that preserves the trust chain: the Port publishes derived indicators through a documented open interface; the LDT consumes them under an Observer-tier arrangement; no connector deployment is asked of the Port.
  • Timeline — not schedulable until an owner is confirmed.
  • Value — port-city replication, and evidence that the scheme accommodates participants who contribute without joining fully. That second point is worth something to PD4 independently of Hamburg: a data space that only works for fully committed members does not scale.

Proposed Risk to manage, restated plainly: supporter status versus data-contribution expectations. The scheme currently expects data the Port has not committed to provide. Either the expectation drops or the commitment is secured, and leaving the gap unresolved means PD4 describes a flow that may not exist.

Needs owner — liaison + ERTICO.** Hold the scoping call, or recommend descoping. Both are acceptable outcomes; carrying it forward unchanged is not.