Seveso III in a chemical plant with AI — the report is not a sprint, it is living evidence.

The problem

Seveso documentation that starts ageing the day after you sign it.

The technical director of a Seveso III chemical plant has a drawer full of documents that are live by contract and dead in practice. The Major Accident Prevention Policy was drafted three years ago. The internal emergency plan was updated in the last cycle, and since then two operating procedures, one response team and one substance in the inventory have changed. The Safety Report is delivered every five years after a sprint of several weeks — the sprint where everybody drops what they were doing to rebuild the reality of the plant on paper.

This is not a problem of willingness. It is structural: the information the report needs is spread across the SCADA, the ERP, the inventory sheets, the maintenance work orders, the training records and, above all, the heads of three or four people. When the civil protection inspection or the insurer's audit arrives, the plant goes into war mode for weeks to reconcile what the paper says with what actually happens. And in a major-accident plant, that gap is not paperwork: it is the space where the real risks slip through.

How it fits the IRIS system

iLEAN does not add another management system — it seals the cracks between the ones you already have.

The Seveso problem is not a lack of information: it is information living on islands that reaches the report weeks after it changed on the plant floor. iLEAN acts as the putty that fills the gaps between SCADA, ERP, maintenance systems and operational reality, without asking you to change anything you already have.

Tracer sees what changes. Writer drafts what the agent proposes. The safety manager signs. The audit becomes continuous — never the other way round.

The three iLEAN pieces applied to Seveso III compliance:

• Tracer — captures every change that is relevant to Seveso, whether it comes from the SCADA (a new safety valve), from the ERP (a substance added to the inventory), from a maintenance work order, from a response team's training session or from an email from the authority. Connect feeds Tracer with everything that enters the plant — email, a supplier's WhatsApp message, an operator's photo, a reading from the old panel.
• Writer — the agent cross-references each change with the section of the internal emergency plan, of the Safety Report or of the package sent to the external emergency plan that it affects, and prepares the new wording in the format of Royal Decree 840/2015 (or the applicable national transposition). The safety manager reviews and signs.
• Agent — it checks consistency between the inventories, the accident scenarios in the report, the operating procedures and the reality of the plant. When something drifts (a response team whose training has not been renewed, a substance that exceeds the declared threshold, a scenario that no longer applies to the current configuration), it alerts the manager. It never acts on OT alone — the three safety rings guarantee that the ring with the PLCs and the SCADA stays intact.

See the full IRIS architecture →

Before and after

Manual Seveso compliance vs. live evidence with iLEAN

Aspect	Manual compliance + a five-yearly sprint	With iLEAN Tracer + Writer + Agent
Internal emergency plan	Updated on long cycles, out of step with reality	Continuous update triggered by the real change
Safety Report	A sprint of weeks every five years	A live draft, closed in hours when it is due
Coordination with the external plan	An information package rebuilt for every request	A bundled, signed dossier, ready to send
Inventory of substances	A spreadsheet with the manager's latest update	Cross-referenced with the ERP, with automatic notification if a threshold is exceeded
Training of response teams	A folder in HR, manual expiry reminders	The agent warns before the qualification expires
Documentary traceability for the auditor	Rebuilt by hand, weeks of work	A signed history of every change, searchable in seconds

Impact estimate

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

The block below is an estimate to be validated with the specific data of your plant. We put it forward so the committee has an order of magnitude; we refine it during the diagnostic.

• Upper-tier Seveso chemical plant, with a mixed SCADA landscape (modern in the newer plant, legacy in the historical one), a substance inventory in the ERP and operating procedures in a document management system.
• Tracer + Writer pilot focused on the update cycle of the internal emergency plan and the Safety Report, without touching the OT network. First value expected within a few weeks: a draft of the internal emergency plan updated with the real changes of the last year.
• Indicative payback between 4 and 9 months, depending on the volume of internal hours spent today on the report sprint and the average cost of a non-conformity at the last inspection.
• Expected reduction in the effort of maintaining Seveso documentation of more than 30% (a conservative estimate), freeing the safety team for field work.

And the CAIO/CIO's reasonable doubt

“What if the AI writes a paragraph of the safety report badly and it slips through into a submission to the authority?” — hallucination is a problem of free generation, not of anchored tasks. In tasks where the AI merely recontextualizes a piece of data from one system into another (a SCADA change into a paragraph of the internal emergency plan, an ERP entry into an inventory line), the best models brought error below 1.5% ^[1]. And the human signature is mandatory: the agent proposes, the safety manager signs. The three iLEAN safety rings also guarantee that the plant's critical OT network receives nothing with full autonomy — it is the axiom of IEC 62443 turned into architecture.

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