CTN - Architecture Documentation
Overview
Section titled “Overview”The Connected Trade Network (CTN) is a digital infrastructure initiative that implements the BDI (Basic Data Infrastructure) reference architecture framework for secure data sharing in container transport operations. This documentation follows the arc42 template to provide comprehensive architectural guidance.
Important Terminology: Throughout this documentation, we distinguish between “CTN” (the digital infrastructure initiative/system) and “container transport” (the physical business process being improved).
CTN is one of several initiatives using the BDI framework as its foundation. While BDI defines the core principles and patterns, CTN applies these specifically to the container logistics domain with the Hinterland Terminals and Portbase.
Scope for 2026
Section titled “Scope for 2026”The 2026 delivery is deliberately narrow:
- Association Register (ASR) — production-ready: participant onboarding, eHerkenning-based authentication of authorised representatives, periodic re-verification against KvK / KBO / VIES / GLEIF, M2M-credential issuance.
- Endpoint registration — data-providing parties register their endpoints (OpenAPI YAML upload, validation, discovery); data-consuming parties register their applications and obtain OAuth client credentials.
- Use case “Visibility Achterland Containerlogistiek” — first practical application: combining Portbase data with inland-terminal operational data into a dashboard for import containers moving over barge into the hinterland.
Authorisation remains local at the data provider: each data owner decides which registered party may receive which data on the basis of the conditions they configure themselves. VAD-only flow.
Later-phase concerns (Orchestration Register, dual-token VAD+VOD validation, OPA-based policy engine, full 2R+ federation) are explicitly out of scope for 2026 and are tracked in the Roadmap. Design notes for those components are parked in docs/_out-of-scope-2026/ (gitignored) and will be brought back when the corresponding phase starts.
Document Structure
Section titled “Document Structure”📚 Core Architecture Documentation
Section titled “📚 Core Architecture Documentation”| Section | Description |
|---|---|
| 01. Introduction and Goals | Business context, requirements, stakeholders |
| 02. Architecture Constraints | Technical, organizational, and political constraints |
| 03. System Scope and Context | System boundaries and external interfaces |
| 04. Solution Strategy | Core architectural decisions and approaches |
| 05. Building Block View | Component structure and detailed designs |
| 06. Runtime View | Dynamic behavior and interaction scenarios |
| 07. Deployment View | Infrastructure and deployment architecture |
| 08. Cross-Cutting Concepts | Technical concepts applied across components |
| 09. Architecture Decisions | Key decisions and their rationales (ADRs) |
| 10. Quality Requirements | Quality goals, scenarios, and metrics |
| 11. Risks and Technical Debt | Risk register and debt management |
| 12. Glossary | Terms, acronyms, and definitions |
| 13. Implementation Roadmap | Phased deployment approach |
Quick Navigation
Section titled “Quick Navigation”For Business Stakeholders:
- Start with Introduction and Goals
- Review CTN Initiative Overview
- Understand Solution Strategy
For Architects:
- Review Architecture Constraints
- Study Building Blocks
- Check Architecture Decisions
For Developers:
- Start with Building Blocks
- Review Runtime Scenarios
- Check Cross-Cutting Concepts
For Operations:
- Focus on Deployment View
- Review Quality Requirements
- Monitor Risks and Technical Debt
- Track NIS2 Compliance
Key Architectural Principles
Section titled “Key Architectural Principles”BDI Framework Foundation
Section titled “BDI Framework Foundation”CTN implements the seven core BDI principles:
- Connecting Physical and Digital - Bridging real-world logistics with digital data
- Event-Driven - Asynchronous communication via an event broker (e.g. Azure Event Grid, AWS EventBridge, Apache Pulsar)
- Zero Trust - No implicit trust between participants
- Dynamic Data - Real-time, time-sensitive information
- Data at the Source - Custodians maintain data control
- Local Decision-Making - Distributed authorisation
- Coherent Security - Integrated security framework
Governance
Section titled “Governance”Technical Advisory Board: Reviews and approves architectural decisions
Update Frequency: Monthly review, quarterly major updates
Change Process: Pull requests with architecture board review
In samenwerking met
