IT Transformation and Operational Excellence at CLdN — short sea shipping, multimodal transport, automotive logistics. Multiple terminals across different countries. Role: strategic leadership and hands-on delivery.
Active Projects
| Project | Status | Key Decision |
|---|---|---|
| BC Migration (Business Central) | Active | Seeburger vs. Norriq Interface Accelerator |
| Qargo TMS Implementation (D2D) | Active | Building customs tracking on top of TMS |
| CRM Rollout | Active | 30-person sales team, expanding to 2nd BU |
| Auto Terminal Scanning | Research | Eliminate manual scanning — which vendors? |
| OpEx Communication Structure | Research | Async cadence alongside monthly meetings |
| Microservices / DDD Architecture | Planned | Internal transition — event-based, domain-driven |
| TOS Selection & Implementation | Research | Replacing RoRo.NET — 583 use cases workshopped, vendor selection pending |
Related Deliverables
- TOS Selection Project (domains & capabilities)
- TOS Reference Architecture & DDD
- OpEx Framework & Initiatives
- AI Use Cases for CLdN
- IT Applications Transformation — TOM
- Project Portfolio Dashboard
Architecture Decisions
Seeburger vs. Norriq Interface Accelerator
Accounting wants to push Norriq Interface Accelerator as the integration layer for BC. Joan’s objection: additional vendor dependency, a new layer on top of Seeburger which already exists. Preference: Seeburger as the sole middleware, preserving vendor independence.
“Build what differentiates, buy what is commodity. Middleware choice is architecture — not a procurement decision.”
BC Integration Landscape
- Seeburger — central middleware (Joan’s preference)
- Qargo TMS — customer data directly via .NET Masterdata (not via Seeburger)
- Eyeshare — document management
- Ultimo — inventory management (being connected)
- In-house billing — sales invoices from TMS
- .NET Masterdata — unique accounting codes, credit limits
D2D Customs — Approach
Qargo TMS currently has limited customs tracking functionality. CLdN D2D operates own equipment (trailers, containers) but no own drivers. Customs steps (ICS2, EU-UK flows, manifest post vessel departure) are being built on top of the TMS.
Systems & Tools
| System | Category | Role |
|---|---|---|
| ADONIS + ADOIT (BOC Group) | EA / Processes | Single repository for NIS2, ISO, AEO |
| Seeburger | Middleware | Central integration layer |
| Microsoft Business Central | ERP | Migration in progress |
| Qargo TMS | Transport | D2D operations + customs (under construction) |
| Eyeshare | Documents | Invoice and document management |
| Ultimo | Maintenance/Inventory | Being connected to BC |
| IDEM Telematics | IoT | Trailer tracking — API integration under review |
| Microsoft Copilot Studio | AI | Custom agents — under research/execution |
OpEx — 5 Pillars
- Process — ADONIS/ADOIT as central process repository
- People — production-oriented organisational transformation
- Technology — BC, Seeburger, TOS, Copilot
- Data — Master data centralised, data-driven integrations
- Governance — NIS2, ISO, AEO compliance
View full OpEx Framework & Initiatives
Open Questions
- Seeburger vs. Norriq — decision pending with accounting
- Auto terminal scanning — compile vendor shortlist
- Async OpEx communication — which platform? (not Teams Shared Channel)
- Microservices transition — when to start, which domains first?
- IDEM Telematics API — confirm feasibility