EU Export Compliance Operating System
ICT sits on top of your ERP, MES, SCADA and supplier data. It calculates product-level embedded emissions, shows your CBAM cost in euros, and produces the data package for your EU importer and the Digital Product Passport.
No sign-up · fictional "Anadolu Steel" data
Primary billet supplier changed and has no actual data (EU default used). Line scrap rate rose to 6.8%.
The clock is already running
The problem
Purchasing in ERP, production in MES, energy in SCADA, supplier declarations in email attachments. One product-level number takes weeks.
Without actual data, the EU's default values with mark-ups apply – which can multiply the cost per tonne.
"Our carbon is 18,423 tonnes" is not a decision. You need to see which product, customer and supplier drives the cost.
The one question we ask in the first meeting:
“Can you see the CBAM cost of your 2026 EU-bound production by product and customer – and prove with an audit trail which ERP, MES, energy and supplier records that number came from?”
How it works
Modules
Product → BOM → material → supplier → site → line, with versions.
Direct, indirect and precursor emissions per product, batch and month – every number traceable.
€ cost from CN code, free-allocation phase-out, ETS price and carbon price paid at origin.
Collect emission data and documents via a one-time link, no account needed; automatic reminders.
JSON-LD passport with persistent UUID and QR, versioned and ready for the EU Registry.
SHA-256 hashed, versioned, immutable document archive with integrity checks.
Scores suppliers with missing, expired, unverified or high-intensity data.
Switch supplier, cut scrap, buy green power: see the 2026–2034 € impact instantly.
Exposure and data quality by product, customer and supplier for the CFO/COO.
Start with templated Excel/CSV, connect ERP/MES/SCADA via REST API.
Every factor, BOM and document change: who, when, old → new value.
Read documents, find missing data, explain cost changes – never change data without approval.
AI that does real work
"This supplier has no emission data" → drafts a request, sends it on approval, follows up.
Reads incoming PDF declarations, extracts value and period, matches the material, flags anomalies.
"Why did CBAM cost rise 17%?" → separates supplier change, electricity intensity and scrap effects.
Pilot
BOM and purchasing from ERP, production from MES, energy from SCADA; CN code mapping.
Product graph, carbon engine; portal requests to critical suppliers.
Product-level SEE, CBAM cost, data quality and evidence chain.
Importer data package, DPP drafts, CFO scenarios and roll-out plan.
1 line → whole plant → other plants → all suppliers → DPP → supplier risk → optimisation
Who it's for
No. ICT runs on top of ERP/MES/SCADA. The pilot starts with templated exports; API or scheduled transfer follows.
The authorised CBAM declarant in the EU (usually your importer) files it. You provide the installation- and product-level embedded emissions with evidence – ICT produces that package.
No. Each request carries a unique, time-limited link; suppliers upload data and documents without signing up.
No. Agents produce suggestions; nothing is written to factors, BOMs or reports without human approval, and every approval is logged.
Company data is isolated per tenant; documents are stored with SHA-256 hashes. Hosting and data-protection requirements are agreed during the pilot.
A 30-minute call about your products, EU customers and current systems to define the pilot scope together.