Prestressing traceability for precast beams — a tensioning report should not take a week to surface.

The problem

Three critical data points, three systems, one paper report at the end of the bed.

Prestressing traceability for a precast beam is not optional: it is the basis of the DoP the manufacturer signs under CPR 305/2011 and of the EHE-08 code that the site inspection can invoke at any moment. And yet, in the vast majority of plants it lives unstitched in three different places:

1. The steel batch certificate — a supplier PDF, filed in the quality manager's folder.
2. The tensioning bed report — paper signed by the bed lead with the applied load, the estimated losses and the date.
3. The concrete and curing record — in the MES if there is one, in a lab spreadsheet if not.

When everything goes well, nobody asks for the dossier. When a crack appears in a beam installed two years ago, the site inspection asks for the evidence and a week-long search begins. And if the beam shared a tensioning run with five siblings on a long bed, you have to rebuild per beam what was recorded per tensioning run. The classic system works because good people fill in the reports and file them. The day the bed lead retires, half the plant leaves with him.

How it fits the IRIS system

iLEAN does not add a fourth system — it stitches the three you already have so the evidence exists on its own.

The prestressing problem is not a lack of information: it is information living in islands that at the critical moment (the random audit, the claim three years later) never comes together in time. iLEAN acts as the putty that fills the gaps between the supplier's steel certificate, the tensioning bed report and the concrete record — without asking you to change the bed, the jack, or the ERP.

Connect reads the steel certificate, the jack report and the lab record wherever they live. The agent allocates the tensioning run per beam according to the production sheet. The person signs the DoP — Tracer does not sign, it prepares.

The three iLEAN pieces applied to prestressing traceability:

• Tracer (Connect + Agents) — captures through every channel you already use: the supplier's steel certificate PDF, a serial read from the hydraulic jack's console, the concrete lab record, the bed operator's report dictated by voice. It works with what is already there; it does not require changing the bed.
• Edge optional — if the bed has a critical point (anomalous load detection, strand identification passing through the reader), an Edge terminal records it in milliseconds, with or without a network, and fires the traffic light to the bed lead if the load drifts out of range.
• Agent — cross-references the tensioning run with the beam sheet (length, section, strand positions) and splits the master event among the bed siblings, associates the steel certificate with each specific strand, builds the per-beam dossier and prepares the DoP for the quality manager to sign. Tracer proposes, the person signs.

See the full IRIS architecture →

Before and after

Paper reports and reconstruction vs. traceability stitched with iLEAN Tracer

Aspect	Paper reports + PDFs in a folder	With iLEAN Tracer + optional Edge
Steel batch per strand	Matched by memory/date	Certificate read and linked to the physical strand
Jack load per tensioning run	Handwritten report signed by the bed lead	Serial read from the console, recorded in real time
Per-beam allocation on a long bed	Position rebuilt by hand	The agent allocates by beam sheet automatically
Concrete and curing	Lab spreadsheet	Integrated into the per-beam dossier
Signed DoP	Word template + manual work	Template generated by the agent, digital human signature
Time to answer an audit	Days to weeks	Minutes

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.

• Plant with two prestressing beds, mixed production of floor beams, prestressed beams for small bridges and hollow-core slabs — multi-SKU on the same bed.
• Tracer pilot on one bed (integration with the jack console + OCR of the steel certificate + reading of the lab report + per-beam dossier). First value expected within a few weeks: a per-beam dossier issued automatically and signed by the manager.
• Indicative payback between 4 and 9 months, depending on the frequency of audits and site-inspection claims, and the hours per week currently spent hunting for reports and rebuilding certificates.
• The hard lever is a single claim resolved in hours instead of weeks (no beam held on site, no penalty), plus a reduction ≥ 30% in the quality manager's administrative time assembling dossiers.

And the quality manager's reasonable doubt

“What if the AI builds a dossier with a strand assigned to the wrong beam?” — hallucination is a problem of free generation, not of anchored tasks. In tasks where the AI merely reads a certificate PDF, a serial read from the jack and a production sheet, and joins them under an explicit rule, the best models brought error below 1.5% ^[1]. And even so, the DoP is never signed alone: the agent builds the dossier, the quality manager 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.