A closed-PDF as-built does not survive the first field incident.

The problem

The classic as-built is assembled at the end of the FAT — and whatever never reached the PDF does not exist.

The classic documentation package for a nacelle runs to some 1,500 pages: component list with serials, tightening torque records by station, approved non-conformities, electrical and mechanical FAT results, certificates. It is consolidated at the end, in a quality office, out of very heterogeneous sources:

1. Tightening tools that emit the real torque inside their own software — and dump it into a spreadsheet at the end of the shift (if nobody loses the USB stick).
2. Component serial readings (gearbox, generator, converter, yaw drives) — done by hand with a scanner gun in many plants, with the chance of misreading or tying the serial to the wrong sub-assembly.
3. Deviation approvals that cross the supervisor's desk verbally or on a signature sheet that ends up in the physical filing cabinet.
4. FAT tests with their own templates, their own measurement systems and their own owners.

Consolidation works — most of the time. Until it does not: a nacelle delivered 18 months ago shows abnormal vibration in the field, and O&M asks for the exact torque used on the hub bolts. The data exists somewhere — but reconstructing it from signature books, the assembler's photos and the supervisor's memory takes weeks. And meanwhile, the turbine stays down or the customer stays doubtful.

The sector that knows this pain better than anyone is aerospace. The good news: the solution proven in aerospace fits wind.

How it fits the IRIS system

iLEAN Tracer is the filler between the digital tools, the operator and the living dossier.

The data exists — it is in the tightening tool, on the component label, in the supervisor's voice. What is missing is capturing it at second zero and tying it to the nacelle ID, instead of consolidating it two days later into a PDF. iLEAN Tracer sits on top of the line without asking you to change tools, MES or suppliers.

Connect reads the tool and the supervisor's voice. Edge reads the serial on the component label. The agent builds the living as-built per nacelle. The person signs — never the other way round.

The iLEAN pieces applied to unit-by-unit as-built:

• Connect on tightening tools — captures the real torque of every shot at second zero and ties it to the specific bolt via the operation sequence. If the tool is old and only outputs its curve on a local industrial PC, Connect reads it from there. If the supervisor approves a deviation by voice, it is recorded with a timestamp and a signature.
• Edge on assembly stations — a vision terminal that reads the label of every component (gearbox, generator, converter, yaw) and the nacelle ID. If the network drops, it keeps reading and recording locally. Zero manual note-taking by the operator for data a camera can read.
• As-built agent — builds the living dossier per nacelle: torques by bolt, serials by component, approved deviations, electrical and mechanical FAT. When the question comes from the customer or from post-sale O&M, the answer is immediate and queryable. If a pattern shows up (a fastener supplier with out-of-range torques, a gearbox batch with a recurring assembly stamp), the agent flags it. The person signs every conclusion that affects handover or a field campaign.

See the full IRIS architecture →

Before and after

As-built consolidated into a PDF vs. living as-built with iLEAN Tracer

Aspect	Classic PDF as-built	With iLEAN Tracer
Tightening torque capture	USB stick from the tool at end of shift	Stream at second zero, bolt by bolt
Component serial reading	Manual scanner gun, risk of wrong association	Edge reads and associates automatically
Approved deviations	Signature sheet in a physical cabinet	Approval with timestamp and signature in the system
O&M question 18 months later	Weeks of manual reconstruction	Direct query in the living dossier
Cross-nacelle pattern detection	Impossible without massive reconstruction	The agent flags it automatically
Behaviour if the network drops	n/a	Edge keeps reading and recording locally

Impact estimate

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

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

• Nacelle plant with 2-3 critical stations (hub, drivetrain, electrical integration). Connect on tightening tools + Edge on component serial reading as the pilot.
• First value expected within a few weeks: a living as-built running for the nacelles that pass through the pilot station, demonstrable to customer and to O&M.
• Indicative payback between 4 and 9 months, depending on the historical average cost of post-handover claims whose root cause takes long to reconstruct and on the weight of premium wind customers in your portfolio.
• Hard levers: reduction of dossier reconstruction hours ≥ 30% of the historical baseline; claims closed in hours instead of weeks; commercial premiums tied to demonstrable traceability.

And the quality director's reasonable doubt

“What if the AI ties a torque to the wrong bolt?” — hallucination is a problem of free generation, not of anchored tasks. In tasks where AI merely recontextualises an existing data point (tying a torque shot to a bolt according to the operation sequence), the best models pushed the error below 1.5% ^[1]. And even so, nothing critical is decided alone: the agent proposes, the person signs. The three security rings are there precisely for this — the assembly OT network is never touched, it is only handed a signed envelope that a human decides to open.

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