Client Overlay — Tanger Med · CBAM Apportionment & Reefer Visibility
Builds on Morocco UNS Standard v0.1 and Annex E — Ports & Logistics. The Moroccan Industrial Digital Maturity Dossier 2026 identifies Mohamed Eddoujaji at Tanger Med as a named contact. Tanger Med is the CBAM ledger boundary for everything Morocco exports to the EU — a uniquely high-leverage position.
1. Strategic positioning
Tanger Med is not a typical industrial pilot target. Three angles converge:
- CBAM apportionment hinge. Every Moroccan CBAM-relevant cargo (phosphate, fertilizer, cement clinker, steel) crosses Tanger Med (or Casablanca, or Jorf Lasfar). The port is where production heat IDs → bills of lading → vessel destinations are joined. Without port-side data, upstream CBAM declarations cannot close.
- Continental benchmark. Tanger Med is top-5 globally on container performance and the operational reference for African ports. A standard that runs there is taken seriously continent-wide.
- Reefer + cold-chain. Cold-chain export (citrus, tomato, fish) carries direct economic value distinct from CBAM.
This is the only overlay where the port is the customer of the standard, not the producer. The standard’s value to Tanger Med is in giving it a clean way to ingest signed upstream signals from OCP, Sonasid, LafargeHolcim, etc.
2. Named contacts
| Role | Name | Notes |
|---|---|---|
| Primary | Mohamed Eddoujaji | Per dossier — confirmed Tanger Med contact |
| Operations sponsor | (TBD) APM Terminals or Eurogate operations director | Owns TOS access |
| Authority sponsor | (TBD) Tanger Med Port Authority (TMSA) | Owns port-wide systems and PCS (PortNet) integration |
3. Technical scope
The overlay has two complementary tracks. Run them in parallel; either survives if the other slips.
3.1 Track A — CBAM apportionment ingestion
The port subscribes to upstream conformant UNS feeds and joins them to outbound bills of lading. Track A’s deliverable is a working CBAM ledger at the port for one upstream supplier (OCP).
In-scope signals (from Tanger Med side):
| Area | Equipment | Signals |
|---|---|---|
gate | gate-lane-04 | truck-count, truck-license-plate, ocr-read-count |
weigh-bridge | weigh-bridge-01 | weight-t, vehicle-id |
quay-3 | sts-crane-04 | twin-lift-count, single-lift-count, total-loaded-t |
tos | site-summary | vessel-arrival-count, containers-loaded-count, vessel-imo, vessel-destination-iso2, bill-of-lading-id |
Subscriptions from upstream (OCP, eventually Sonasid, LafargeHolcim):
- All
cbam_relevant: truesigned payloads, joined onbatch-id→bill-of-lading-id
The CBAM aggregator (already specified in Morocco UNS Standard v0.2 — Security & i18n §11.4) runs in Tanger Med’s tenant.
3.2 Track B — Reefer visibility
Per-plug temperature alignment to booking set-points; alarm consolidation; shipper portal.
| Area | Equipment | Signals |
|---|---|---|
yard-reefer | reefer-plug-r247 | container-id, set-temperature-c, actual-temperature-c, energy-kwh, alarm-state |
This is operationally valuable independent of CBAM — pays for itself in claims reduction.
3.3 Path examples
ma/ma-01/apm-terminals/tanger-med-port/quay-3/sts-crane-04/total-loaded-t
ma/ma-01/apm-terminals/tanger-med-port/yard-reefer/reefer-plug-r247/actual-temperature-c
ma/ma-01/tanger-med/tanger-med-port/tos/site-summary/vessel-destination-iso2
ma/ma-01/tanger-med/tanger-med-port/gate/gate-lane-04/truck-count
3.4 Code alignment
Per Annex E — Ports & Logistics §E.6:
- Vessel ID → IMO 7-digit
- Container ID → ISO 6346 (BIC code)
- Vessel destination → ISO 3166-1 alpha-2
- Customs declaration → Moroccan ADII reference
- Cargo type → UN/EDIFACT 7085
This minimizes friction with the existing PCS (PortNet).
4. Entry route
4.1 Primary: Mohamed Eddoujaji direct
Frame: “Every CBAM-exposed Moroccan exporter needs port-side data to close the ledger. The standard is published. We’d like to align Tanger Med’s data with it before OCP and Sonasid start asking.”
This positions the port as the enabling actor, not the customer of a service.
4.2 Secondary: TMSA + ANP (Agence Nationale des Ports)
A standard endorsed by TMSA cascades to Casablanca, Jorf Lasfar, Safi, Agadir, Nador automatically through ANP. Pursue endorsement after the Tanger Med technical pilot lands.
4.3 Tertiary: APM Terminals corporate
APM Terminals corporate (Maersk Group) has its own digital agenda; bypass-around-the-local-team is risky. Use only if local channel stalls and only with explicit Eddoujaji agreement.
5. Commercial structure
5.1 Pilot offer (Track A + Track B, 14 weeks)
| Item | Detail |
|---|---|
| Duration | 14 weeks (slightly longer than standard pilot — three stakeholder layers: APM/Eurogate, TMSA, customs) |
| Team | 1 architect, 2 engineers, 1 PM, 1 ports SME |
| Deliverables | (a) UNS broker integrated with one terminal’s TOS; (b) reefer plug visibility for ≥ 100 plugs; (c) CBAM aggregator running with one upstream supplier (OCP) for one cargo; (d) ISO 6346 / IMO / UN-EDIFACT alignment validated; (e) PortNet integration plan |
| Fee band | 1.8–2.5M MAD (≈ 165–230k EUR) |
| Payment | 25% kickoff, 25% reefer visibility live, 25% CBAM extract live, 25% on PortNet integration plan accepted |
| KPI gate | (a) reefer alarm latency < 60 s p95; (b) one signed CBAM extract reproducible; (c) zero topic violations in audit log over weeks 11–14 |
5.2 Beyond pilot
| Phase | Scope | Indicative |
|---|---|---|
| Phase 2 | Full reefer estate at Tanger Med (~3,000 plugs) | 3–4M MAD over 6 months |
| Phase 3 | CBAM aggregator scaled to all upstream Moroccan exporters | 5–8M MAD over 12 months; or SaaS-style retainer |
| Phase 4 | Casablanca, Jorf Lasfar, Safi, Agadir, Nador via ANP framework | Framework-priced |
5.3 Why the fee is higher than other overlays
- Three-stakeholder coordination (TOS operator, port authority, customs)
- Longer duration
- Continental reference value to IEIA
6. Why now
- CBAM January 2026 + May 2027 declarations create demand-pull from upstream exporters; Tanger Med becomes the bottleneck if not ready.
- Mohamed Eddoujaji is a named warm contact. Same decay logic as Adil Ousti — months, not years.
- No competitor has a Moroccan-port UNS reference. 4Sight Holdings does not operate in North Africa; MaestroHub withdrew from MENA. The position is open.
- Cascading endorsement through ANP turns a single Tanger Med deployment into a national port standard with no incremental sales effort.
7. Special note — coordination with the OCP overlay
The Overlay — OCP Safi Pilot and this overlay are technically interlocking: a successful CBAM extract at Tanger Med requires OCP-side signed payloads, and a successful CBAM extract at OCP requires port-side bill-of-lading-id joins. Run them in coordinated sequence:
- OCP Safi pilot starts (Track A): produces signed payloads.
- Tanger Med pilot starts ~6 weeks later: subscribes to OCP signed payloads, joins to bill-of-lading.
- Joint Phase 2 — first end-to-end CBAM cargo declaration with OCP and Tanger Med as co-references.
This is the highest-impact narrative IEIA can produce in 2026.