Executive Summary

Eight industry sources were researched for reference architectures, data models, and standards applicable to terminal operating systems at a mixed RoRo terminal like CLdN Ports Zeebrugge. The findings reveal a fragmented landscape:

Critical Gap: No open/published RoRo TOS reference architecture exists equivalent to TIC4.0 for containers. The RoRo domain model must be synthesized from Navis Master Terminal, Tideworks Mainsail, PIANC WG 167, and actual CLdN operations.

Source Relevance for Mixed RoRo Terminal

Source Type RoRo Rating Key Value
TIC 4.0 Open Standard Medium Container-side semantic data model; Carrier Visit / Cargo Visit framework
Navis N4 / Master Terminal Commercial TOS High (MT) Detailed RoRo deck model, VIN tracking, mixed cargo support
Kalmar One Automation Middleware Low Container automation layer only; IEC 62443-4-1 certified
Tideworks Mainsail Commercial TOS High Native RoRo module; production-proven at TOTE Alaska
EU Projects (SAURON/PRECINCT) EU Research Low (TOS) / High (Security) Port cyber-physical security architecture
ISO 28000 Series ISO Standard Medium Security management framework; ISO 28004-2 seaport guidance
PIANC WG 167 Design Guideline High (ops context) RoRo/RoPax terminal physical & operational design
World Bank Port Reform Toolkit Governance Framework Medium Smart port maturity model; Module 9 digitalization

1. TIC 4.0 — Terminal Industry Committee 4.0

TIC4.0 is the only open industry initiative focused on defining a shared semantic framework for the cargo terminal industry. Brussels-based non-profit (founded 2019), 70+ member companies, 17 published releases (2021–2025).

Data Model Core

Carrier Visit
  → has many Cargo Visits
       → each Cargo Visit involves Movements
            → each Movement involves a CHE
                 → CHE executes Cycles
                      → Cycle contains Moves

Technology-agnostic: compatible with REST/JSON, SOAP/XML, OPC-UA, MQTT. PAS 4000 (BSI) formalization in progress.

CLdN Actionable: Use TIC4.0's Carrier Visit / Cargo Visit / Movement framework for the container side. Monitor for RoRo extensions.


2. Navis N4 / Master Terminal

Dominant container TOS globally (320+ deployments, now under Kaleris). Java-based metadata-driven platform.

Core Domain Entities

LayerKey Entities
FacilityComplex, Facility, Yard (Block/Bay/Row/Tier), Berth
OperationsVessel Visit, Unit, Unit Facility Visit, Equipment, Work Instruction
PlanningVessel Bay Plan, Berth Assignment, Yard Strategy
AdministrativeBooking, Service Event, Hold, Bill of Lading, Carrier
GateGate Transaction, Truck Visit, Driver

Master Terminal — RoRo Extensions

CLdN Actionable: Master Terminal is architecturally the closest product for mixed RoRo. N4 patterns inform domain model even if not deployed.


3. Kalmar One Automation System

Not a TOS — automation middleware between TOS and physical equipment. Equipment-agnostic fleet management: ASC, ARTG, AGV, AutoTT, AutoStrad. First port solution certified IEC 62443-4-1 (OT/IT security).

CLdN Actionable: Relevant only for container automation side. SmartPort modules (SmartLane, SmartRead, SmartMap) useful even in semi-automated contexts.


4. Tideworks Mainsail

North American TOS (100+ marine and intermodal terminals). SaaS on AWS. One of the few TOS systems with a native, production-proven RoRo module.

Product Suite

ProductFunction
Mainsail (core)Container, RoRo, break-bulk terminal management
Mainsail Ro/Ro moduleRolling stock tracking & tracing, vehicle lifecycle
SpinnakerGraphical vessel & yard planning
Traffic ControlElectronic equipment dispatch
Intermodal PRORail terminal TOS

CLdN Actionable: TOTE Alaska deployments are closely analogous to CLdN's mixed RoRo operations. Limitation: primarily North American vendor.


5. EU Port Security Projects

No EU project named "PROTECT" found for port TOS architecture. Related projects focus on cyber-physical security:

CLdN Actionable: Security architecture outputs from SAURON/PRECINCT inform NIS2 compliance design for TOS.


6. ISO 28000 Series

Security management system standard (Annex SL structure, like ISO 9001/27001). Key standard: ISO 28004-2:2014 for seaport operations implementation.

CLdN Actionable: Treat ISO 28004-2 as security requirements baseline for TOS gate management, dangerous goods, and access control.


7. PIANC WG 167 — RoRo/RoPax Terminal Design (2023)

Authoritative physical design reference. Covers ship approach, linkspan design, terminal layout, vehicle flow, marshalling areas, safety zones. Effectively defines functional requirements for a RoRo TOS module.

TOS Requirements Derived from PIANC

CLdN Actionable: Use WG 167 + WG 213 (multipurpose terminals) as the physical/operational requirements basis.


8. World Bank Port Reform Toolkit (3rd Ed., 2025)

Module 9 covers digitalization and cybersecurity. Positions TOS as "the digital backbone of any terminal." Smart port maturity model (5 levels) and NIS2/IMO alignment.

CLdN Actionable: Module 9 provides board-level language for the TOS initiative. Maturity model useful for positioning current vs target state.


Cross-Cutting Synthesis

Common Entity Mapping Across Sources

EntityTIC4.0Navis N4Tideworks
Ship visitCarrier VisitVessel VisitVessel Visit
Cargo unitCargo VisitUnit (Facility Visit)Unit
Unit movementMovementWork InstructionWork Order
EquipmentCHEEquipmentEquipment
PositionPositionBlock/Bay/Row/TierYard Position
Gate transactionGate TransactionGate Transaction

RoRo-Specific Entities (Gap in Open Standards)

EntitySource
Vehicle (VIN)Master Terminal, Tideworks, GullsEye
Deck definitionMaster Terminal, PIANC WG 167
Vehicle LaneMaster Terminal, PIANC WG 167
Ramp / LinkspanPIANC WG 167
PDI RecordMaster Terminal
Companion (driver)
Trailer manifestTideworks
Marshalling zonePIANC WG 167

Container vs RoRo Differentiation

DimensionContainer TOSRoRo TOS
Core cargo unitISO container (TEU/FEU)Vehicle (VIN) or trailer
Position modelBlock/Bay/Row/Tier (stack)Lane/Row/Zone (flat parking)
Vessel modelBay plan (grid)Deck plan (lanes, zones, heights)
Key equipmentCrane, RTG, straddleShore ramp, tractor, reach stacker
Pre-processingSeal check, weight, EDIVIN scan, damage inspection (PDI)
Throughput metricCrane moves per hourVehicles per hour over ramp

Architecture Recommendations for CLdN

Proposed Domain Model for Mixed RoRo TOS

FACILITY
  Berth (type: RoRo, Container, General)
  Quay Zone
  Yard Zone (type: Vehicle, Trailer, Container, Breakbulk)
    Lane (for vehicles)
    Block/Bay/Row (for containers)
  Gate (inbound/outbound)

CARRIER VISIT (= Vessel Call)
  Vessel (static definition)
  Voyage
  Berth Assignment
  Deck Plan
    Deck (with height, weight, ramp access)
    Vehicle Lane (per deck)
    Container Zone (per deck)
    General Cargo Zone (per deck)

CARGO UNIT
  Vehicle Unit (VIN, make, model, weight class)
    PDI Record
    Damage Report
  Container Unit (ISO, TEU/FEU, type)
    Reefer parameters
    IMO dangerous goods
  Trailer Unit (accompanied/unaccompanied)
    Cargo Manifest
  Breakbulk Unit (lot/commodity/piece)

MOVEMENT
  Work Order / Work Instruction
  Equipment Assignment
  Position (From → To)
  Timestamp / Execution Status

GATE TRANSACTION
  Truck Visit
  Driver
  Cargo Declaration
  Customs Status

BILLING
  Service Event
  Rate / Tariff
  Invoice

NIS2 and Cybersecurity Requirements


Standards Hierarchy

INTERNATIONAL STANDARDS
  ISO 28000 series       Security management (compliance)
  UN/EDIFACT             EDI messages (BAPLIE, COARRI, COPRAR)
  IMO FAL / MSC          Maritime operational standards

INDUSTRY STANDARDS
  TIC4.0                 Semantic data model for CHE and TOS
  PAS 4000 (BSI)         Forthcoming formal specification

PHYSICAL DESIGN GUIDELINES
  PIANC WG 167 (2023)    RoRo/RoPax terminal design
  PIANC WG 213 (2020)    Multipurpose terminals

GOVERNANCE FRAMEWORKS
  World Bank Toolkit     Module 9: Digitalization & cybersecurity

COMMERCIAL TOS
  Navis N4 / Master Terminal    Mixed/RoRo (Kaleris)
  Tideworks Mainsail            RoRo-capable (Blackstone)
  GullsEye                      Cloud RoRo+container
  OSCAR (TGI Maritime)          Container/RoRo

AUTOMATION MIDDLEWARE
  Kalmar One                    CHE automation (container)

Research conducted March 26, 2026. All source URLs verified via direct fetch. Full 875-line research document available as PDF download above.