ISO tank ADR class 3: the custody chain does not break between the loading bay and the consignee.

The problem

Five custodians, one seal, zero shared memory.

An ISO tank carrying a class 3 flammable liquid (UN 1268, UN 1993, petrol, aromatic solvents, industrial ethanol) travels, between loading bay and destination, through a sequence involving at least five sets of hands: shipper's loading bay → origin forwarder → port terminal → shipping line → destination terminal → destination forwarder → discharge. Every handover generates a different document in a different system:

1. Loading bay: loading note, ADR declaration, photo of the seal on the valve, the operator's report (sometimes in a spreadsheet, sometimes only in their head).
2. Forwarder: CMR, written ADR instructions, truck status sent by the driver from the road.
3. Terminal and shipping line: EDI / Bill of Lading / port status, EDIFACT messages that live in another world.
4. Consignee: receipt sheet, seal reading on arrival, chemical validation of the sample.

The chemical logistics manager knows all this, but cannot be in five places at once. When something goes wrong — a seal that does not match the one at origin, a six-hour stop with no explanation, an EDI message that never arrives — reconstructing the file takes weeks, and the claim or the ADR penalty is already running. The classic system works 99% of the time. That 1% is the one that reaches the inspector and the insurance company — and a badly closed ADR class 3 ISO tank is not an incident: it is a risk.

How it fits into the IRIS system

iLEAN Tracer does not add another system — it seals the cracks between the five already involved.

The custody chain problem is not a lack of information: it is information living on five islands that, at the critical moment (acceptance at destination, the inspector walking in, a claim at two in the morning), does not reach the decision-maker in time. iLEAN Tracer acts as the filler for those gaps, without asking the forwarder, the shipping line or the consignee to change their software.

Connect captures on any channel. Edge reads the ISO tank OCR and the seal photo. The agent cross-checks against the ADR data and the route events. A person signs at every leg — discharge is never authorised on its own.

The iLEAN pieces applied to the custody chain of an ADR class 3 ISO tank:

• Edge — a terminal with machine vision (CNN) at the loading bay and at discharge. It reads the BIC code of the ISO tank, the ADR plate and the photo of the seal on the valve before departure and on receipt. It works without a network: if the port terminal loses connectivity, the read-and-sign cycle carries on, because what is critical cannot depend on WiFi.
• Connect — captures everything arriving outside the shipper's ERP: port EDI, the shipping line's Bill of Lading, the forwarder's CMR, the driver's mid-route message with the seal photo, the customs agent's email. Every message enters the batch custody chain at second zero, with nobody forwarding anything.
• Agent — cross-checks ADR data, physical seal, ISO tank OCR, route events and the shipper's ADR plan. If the seal on arrival is not the one that left, if the temperature of an instrumented ISO tank moves outside the range for a class 3 product with a low flash point, or if there is an unplanned stop, it holds acceptance at destination and alerts the responsible person. The person validates and signs; discharge is never authorised on its own. The three safety rings exist precisely for this.

See the full IRIS architecture →

Before and after

Custody chain in a spreadsheet vs. custody chain signed with iLEAN Tracer

Aspect	Spreadsheet + email + messaging	With iLEAN Tracer
Seal photo at the loading bay	On the operator's phone, sometimes lost	Captured by Connect, linked to the batch and the BIC code
Reading the ISO tank BIC code	Manual, sometimes mistranscribed	Edge OCR — milliseconds, no typing errors
Shipping line EDI / Bill of Lading	In the forwarder's inbox, arrives late	Captured and merged into the batch custody chain
Route events (stops, deviations)	Only if the driver calls	Detected and signed leg by leg
Acceptance at destination	Operator opens the valve and signs afterwards	Automatic hold if the seal does not match — a person signs
File for the ADR inspector / insurer	Rebuilt by hand, weeks	Per-batch dossier, automatic, with photo, OCR, EDI and human signature

Impact estimate

Impact estimate for your plant — to be validated against your numbers.

The block below is an estimate to be validated against the specific data of your operation. We set it out so the committee has an order of magnitude; we refine it during the diagnostic.

• A chemical shipper with 6-10 ADR class 3 ISO tanks per week, two loading bays, terminals in one or two European ports, mixed consignees (industry + resale).
• A Tracer pilot at one loading bay and one consignee (Edge for BIC code + seal, Connect for EDI/CMR/driver messages, the agent signing each leg). First expected value within a few weeks: the custody chain of the first batches is already reconstructible in minutes.
• Indicative payback between 4 and 9 months, depending on the frequency of incidents (mismatched seals, late EDI, unexplained stops) and the average cost of each manual file reconstruction for an inspector or an insurer.
• A reduction of ≥30% in the time it takes to rebuild the ADR file, with a defensible floor far below the cost of a single well-defended dispute with an insurer.
• The hard lever is one single well-defended claim: seal photo, ISO tank OCR, EDI, route events and a human signature at every leg. One claim pays for the pilot.

And the chemical logistics manager's reasonable doubt

"What if the AI gets a BIC code or an EDI message wrong and puts a false data point into the custody chain?" — hallucination is a problem of free generation, not of anchored tasks. In tasks where the AI merely recontextualises a data point from one system to another (reading a BIC code, extracting the UN number from an ADR declaration, parsing an EDI message), the best models brought the error rate below 1.5% ^[1]. And even so, what is critical is never decided alone: iLEAN holds acceptance and a person signs. The three safety rings exist precisely for this.

^[1] OpenAI paper "Why Language Models Hallucinate", 2025 — on the reliability of AI in anchored tasks.