Per-asset history
Every inspection of an asset gathered on one sheet, up to ten years back.
Software · Inspection report management
Your inspection reports already exist. They sit in network folders, email attachments and local desktops. Lucens Integrity centralises those PDFs, links every finding to the right equipment and turns them into per-asset tracking you can actually use, campaign after campaign.
Inspection report management software centralises the reports produced across an industrial asset base and finally makes them usable. Lucens Integrity, built by Assets 4.0, imports your PDFs, a single file or an entire folder, extracts the measurements, findings, deadlines and locations, then links each value to the right equipment. You get a per-asset history, health KPIs recomputed at every import and an exportable audit dossier. Everything runs 100% locally, off-cloud, under your control.
The problem
Every year a plant has dozens to hundreds of pieces of equipment inspected: non-destructive testing (NDT), thickness measurements, periodic requalifications, manufacturer health checks. The fieldwork is done, and done well by certified technicians. But the report itself lands in a network folder, an email attachment or a local desktop, in a layout that looks nothing like the next provider's.
The result: no one answers the simple questions quickly. Which equipment has an open finding? Which requalifications fall due this quarter, across every site? How is an asset degrading from one campaign to the next? Where do the same defects keep coming back? The answer is buried in the PDFs, and it takes hours of manual reading to rebuild it, every single time.
At the scale of a multi-site group, that runs into thousands of reports. The data exists in bulk. It stays unreadable for lack of being gathered, linked to the right equipment and made comparable from one year to the next.
In short: inspection report management software does not carry out the checks. It puts to work the ones already produced, links them to each piece of equipment and makes them retrievable and comparable.
Definition
Lucens Integrity is the inspection report management software built by Assets 4.0. It puts to work the reports you already hold and turns them into structured asset-integrity tracking. It replaces neither your tools nor your experts: it consolidates what already exists.
How it works
You provide your existing reports. The software does the rest, in verifiable steps, without you changing any tool.
You drop in one report or a whole folder of PDFs, whatever the provider or the format.
A format-calibrated adapter reads the report. A format no adapter covers yet is archived and flagged, never guessed. There is no OCR claim on images.
Each finding is attached to the right equipment or zone. The identity is validated, never guessed; anything uncertain is flagged for your team.
Measurements, findings, deadlines, identifiers, dates, locations and severity are extracted, then feed the per-asset history and the 2D map of defects and repaired zones.
Per-asset and per-site health KPIs are recomputed at every import and surface in a pilot dashboard, consolidated from group down to site.
Fidelity principle: the software invents nothing. Attaching a finding to a piece of equipment is validated, never guessed, and a report whose format is not covered by an adapter is archived and flagged rather than interpreted at random.
Inputs and outputs
The principle: the inputs are documents you already have; the outputs are usable straight away by the field and by management, and traceable back to the source PDF.
Every value stays linked to its source PDF. One click opens the original report at the right page to check a finding, without ever leaving the tracking.
Book a meetingKey capabilities
Every inspection of an asset gathered on one sheet, up to ten years back.
Position of defects and repaired zones on the equipment sheet, campaign after campaign.
Compliance rate, critical assets, overdue inspections and open recommendations, at every import.
Computed from periodicity: upcoming inspections and overdue items surface on their own, before the due date.
Prioritisation
Once the reports are linked to the equipment, the software helps decide where to put the effort first.
In practice
IllustrationTake a multi-site operator whose pressure vessels and piping are inspected by several providers. Over a year the reports arrive in different formats: well-structured native PDFs for some, in-house layouts for others. You drop the whole set into the software. It reads each document, links every finding to the right equipment, then classifies the finding by type of check, result, severity and associated deadline.
The inspection manager then opens the sheet for one specific vessel and sees, at a glance, its history, its open findings and its next requalification. Technical management views the same asset base across every site: which assets carry a critical finding, which deadlines are coming up, where the same defects recur. The data has not changed source. It has simply become retrievable and usable.
An illustration of how it works on a generic case. It is not a quantified client result.
Regulatory angle
Centralising the reports helps directly with in-service monitoring obligations. In France, the order of 20 November 2017 governs pressure equipment: it requires an operating file per piece of equipment and sets periodicities, with a periodic inspection at most every six years and a requalification in principle every ten years, brought down to six years for a corrosive fluid. The tracking produced by the software helps keep this register up to date, gathers findings by asset and makes deadlines visible before they arrive. Certifying practitioners is a separate matter, handled by COFREND to the EN ISO 9712 standard; COFRAC accredits COFREND. The software never intervenes in the qualification of technicians.
For a group operating outside France too, the traceability logic is comparable. In the United States, mechanical integrity relies on the in-service inspection codes API 510 (vessels), API 570 (piping) and API 653 (tanks), and on the mechanical-integrity records required under the OSHA Process Safety Management program. In both frameworks the stake is the same: to hold a reliable, up-to-date and retrievable record of every inspection. That is exactly what the software consolidates, without substituting itself for the standards or the bodies that maintain them.
Tool comparison
Inspection report management software replaces none of these tools. It fills the gap between them: turning accumulated reports into consolidated integrity tracking.
| Criterion | Document management (DMS) | CMMS / EAM | Field inspection app | IDMS / AIM | Lucens Integrity |
|---|---|---|---|---|---|
| Primary role | Store files | Plan maintenance | Capture checks on site | Manage integrity, often heavy to deploy | Put existing reports to work |
| Reads inspection PDFs | None, opened by hand | Not designed for it | Produces new records | Depends on setup | Automatic, one file or a folder |
| Links findings to equipment | Manual | Depends on config | Per isolated check | Central, after data entry | Validated, never guessed |
| Per-asset history | To rebuild | Partial | Not consolidated | Yes | Up to ten years, at import |
| Audit dossier | Compiled by hand | Variable | Not applicable | Often yes | Assembled in minutes |
| Hosting | Internal server | Often cloud | Cloud or mobile | Cloud or server | 100% local, offline |
To place each term: a DMS (document management system) stores files without understanding them; a CMMS and an EAM plan maintenance and asset management; an IDMS (inspection data management system) and AIM (asset integrity management) software manage integrity, often at the cost of heavy data entry and deployment; a field-inspection app is used to carry out the inspection itself. Lucens Integrity starts from the reports already produced and makes them usable, with no migration.
Scope
Local deployment
Lucens Integrity runs 100% locally, off-cloud. Your inspection data never leaves the company's machine or network.
Data stays on the company's machine or network, under your control.
No external connection is required to import, analyse and consult your reports.
Every value stays linked to its original PDF, openable in one click.
Audit dossier and tracking exportable to Excel, PDF or CSV, to share as you wish.
If your inspection data still lives in a spreadsheet you keep alive by hand, the ROI calculator estimates, from your own figures, what centralised tracking can free up. To see the wider approach to inspection data, explore Maintenance Intelligence and the Lucens Integrity software itself. In short: your reports already hold the answers, and Lucens Integrity is what makes them retrievable, comparable and defensible in an audit.
Frequently asked questions
No. Lucens Integrity is not a CMMS or an EAM, and it does not plan work orders or manage spare parts. It reads the inspection reports you already produce and runs alongside your existing tools. You import your PDFs, a single file or an entire folder, with no data migration and no change to how your teams work day to day.
Yes, that is exactly what it is built for. A format-specific adapter, calibrated for each report layout, reads every document and brings it back to a common per-equipment structure. When a report uses a format no adapter covers yet, the file is archived and flagged for review rather than guessed, so nothing is ever interpreted at random.
Lucens Integrity relies on per-format calibrated adapters to extract the technical data from your reports. It does not claim optical character recognition on images. When a report's format is not covered by an adapter, the file is archived and flagged instead of being interpreted with uncertainty, so the values you see always come from a layout the software actually understands.
Matching relies on the identifiers present in the report and on the equipment's identity in your asset base. That identity is validated, never guessed. If the software cannot attach a finding to an asset with certainty, it flags it explicitly so your inspection team can decide, rather than assigning it to the wrong equipment or zone.
No. Lucens Integrity runs entirely on your own machine or network, off-cloud and offline. Your inspection reports and the extracted data stay under your control, with no transfer to any external service. Every value also stays linked to its source PDF, so a single click opens the original report to verify a measurement or a finding.
As soon as a first batch of reports is imported, the software produces a per-asset summary over that scope and recomputes the health KPIs. Coverage then widens site by site as you add more reports, without interrupting operations. An exportable audit dossier can be assembled in minutes from whatever has already been imported.
Our expertise
Useful links and references
By the Assets 4.0 team · Published on 11 August 2026 · Updated on
The return on investment
Manual search, re-keying, audit dossiers rebuilt from scratch: estimate, from your own figures, what centralised tracking can free up.
Calculate the ROILucens Integrity turns the reports you accumulate into a per-asset history, health KPIs and an exportable audit dossier, 100% local, so scattered PDFs finally become a view you can steer.
Making industry intelligent