2D defect mapping
Position of defects and repaired zones on the equipment sheet, campaign after campaign.
Software category · IDMS
Inspection Data Management System for Industrial Assets
An inspection data management system (IDMS) turns the findings locked inside your inspection reports into a usable, asset-by-asset condition history. Integrity Loop is the Assets 4.0 IDMS.
An inspection data management system solves a precise problem. The findings produced during inspections stay locked inside PDFs, filed by provider and by date. They are rarely turned into a per-equipment history.
Integrity Loop imports those reports and extracts measurements, findings and deadlines. Every value is linked to the right piece of equipment, and health KPIs recompute at each import. It all runs on-premise, off-cloud, on your workstation or your network.
Your inspection findings already exist. Nobody reads them at asset-base scale.
The problem
On a single site, hundreds of assets are inspected every year: non-destructive testing, thickness measurements, periodic requalifications, provider service reports.
The fieldwork is done, and done well, by certified technicians. But the output lives in heterogeneous PDFs, filed by provider, by site and by date. The formats look nothing alike from one contractor to the next.
An inspection data management system, or IDMS, sits exactly there. It stands between the report that holds the finding and the decision that should follow. It gathers what already exists, links it to the right equipment, and makes it legible over time.
Without it, nobody can quickly answer the simple questions:
- Which pieces of equipment carry an open finding?
- Which requalifications fall this quarter?
- How is an asset degrading, campaign after campaign?
- Where do the same defects keep coming back?
The answer is there, buried in the reports. Reconstructing it by hand takes hours, every time.
The real blocker is not a lack of data but the absence of a per-equipment history.
What an IDMS does, and what Integrity Loop is not
Definition
An IDMS puts the reports you already hold to work. It turns them into structured, per-asset tracking. It performs no inspection: it consolidates what already exists.
What Integrity Loop does
It turns your reports into a history
- Imports an inspection report PDF, or the whole folder at once.
- Analyses each report through a per-format calibrated adapter. An unsupported format is archived and flagged rather than guessed.
- Links every finding to the right piece of equipment or zone, with a validated identity.
- Builds a per-equipment inspection history, up to ten years deep.
- Recomputes per-asset and per-site health KPIs at every import.
What Integrity Loop is not
Neither a CMMS, an instrument, nor an oracle
- It is neither a CMMS nor an EAM. It plans no work and manages no spare parts.
- It is not an NDT instrument: it takes no measurement itself.
- It performs no inspection and does not replace the inspector's expertise.
- It announces neither automatic remaining life nor failure prediction.
Data extracted
- Measurements, including thickness and metal loss.
- Findings, severity and locations.
- Identifiers, dates and deadlines.
- Inspector recommendations.
Users
- Inspection, maintenance and methods managers, for field prioritisation.
- Technical and HSE management, for multi-site asset-base steering.
Decisions supported
- Which equipment to address first, by criticality and risk.
- Which requalifications to prepare, by site and by period.
- Where the same defects concentrate across the base.
- How to evidence up-to-date regulatory tracking.
How the findings in a report become a per-asset history
How it works
You provide your existing reports. Integrity Loop does the rest, in verifiable steps, with no tool change and no data migration.
Import
You drop in an inspection report or the whole folder, in its original format, whatever the provider or site.
Adapter analysis
A per-format calibrated adapter reads the report and extracts the useful content. An unsupported format is archived and flagged rather than guessed.
Data extraction
Measurements, findings, deadlines, identifiers, dates, locations and severity are extracted and normalised.
Equipment matching
Every value is linked to the right piece of equipment or zone, with a validated identity.
History & mapping
Defect tracking and a 2D map of defects and repaired zones build up on the equipment sheet, campaign after campaign.
KPIs & deadlines
Health KPIs recompute at every import; upcoming inspections and overdue items surface on their own from the periodicity.
Advisory follow-up and roll-out are covered on the inspection report tracking page.
See the Integrity Loop software Book a meetingWhat you drop in, what you get back
Inputs and outputs
Your reports in. A usable history and dashboards out, with the source PDF linked to every value.
What you drop in
Your current documents
- Non-destructive testing reports and thickness measurements.
- Periodic requalifications and integrity tests.
- Provider and manufacturer service reports.
- History already accumulated, whatever its format.
What you get back
A steerable history
- A per-equipment inspection history, traceable back to the source PDF.
- A 2D map of defects and repaired zones.
- Health KPIs recomputed at every import, per asset and per site.
- An audit dossier assembled in minutes, exportable to Excel, PDF or CSV.
Defect mapping, health KPIs and deadlines that surface on their own
Steering
Once reports are linked, Integrity Loop gives a condition read. Asset by asset, then across the whole base.
Health KPIs per asset and site
Compliance rate, critical assets, overdue inspections and open recommendations, recomputed at every import.
Regulatory deadlines
Derived from periodicity; upcoming inspections and overdue items surface on their own, with no re-entry.
Criticality and prioritisation
Critical equipment ranked by criticality and risk, so you know what to address first.
Tracked recommendations
Inspector recommendations become actions with a status, from finding to close-out.
Year-over-year comparison
Measurements for the same asset compare from one year to the next, without reopening the reports.
What taking back control of a multi-site base looks like
In practice
IllustrationTake a multi-site operator. Its pressure equipment and piping are inspected by several providers. Over a year, the reports arrive in different formats: well-structured native PDFs, provider-formatted records.
You drop the whole set into Integrity Loop. The software extracts the data and links each finding to the right equipment. It then classifies that finding by severity and deadline.
From there, the inspection manager opens a vessel's sheet. They see its history, its open findings, its defect map and its next due date.
Technical management views the same base site by site: assets carrying a critical finding, requalifications approaching, defects that recur. The data hasn't changed source. It has become legible, comparable and traceable back to the original PDF.
An illustration of how it works on a generic case. It is not a quantified client result.
A per-asset history also serves your tracking obligations
Regulatory angle
Steering an asset base through data helps you meet your in-service tracking obligations.
In France, the order of 20 November 2017 governs pressure equipment. It requires an operating file for each piece of equipment and sets periodicities.
- A periodic inspection at most every six years.
- A periodic requalification in principle every ten years.
- Brought down to six years when the equipment holds a corrosive fluid.
A consolidated per-asset history makes these due dates visible before they arrive. It gathers findings by equipment, which helps keep the register up to date.
The certification of practitioners is a matter for COFREND, to the EN ISO 9712 standard; COFRAC accredits COFREND. Integrity Loop does not intervene in the qualification of technicians.
Outside France, the traceability logic is comparable. The in-service inspection codes API 510, API 570 and API 653 call for a reliable record of every inspection. The OSHA Process Safety Management program applies the same principle to mechanical integrity records: a record that is up to date and retrievable.
The software consolidates that record without substituting for the standards.
Where an IDMS fits between CMMS, EAM, DMS, field app and AIM platform
Category comparison
An IDMS does not replace these categories. It fills the gap between them, turning accumulated reports into a consolidated per-asset history.
| Criterion | CMMS | EAM | DMS | Field inspection app | AIM platform | IDMS (Integrity Loop) |
|---|---|---|---|---|---|---|
| Main role | Plan maintenance | Manage asset lifecycle | Store documents | Capture in the field | Steer integrity | Put inspection data to work |
| Reads and structures PDFs | Not designed for it | Rarely | Files without reading | Produces entries | Variable | Automatic import and extraction |
| Links to the right equipment | Depends on setup | Depends on setup | Absent | By manual entry | Variable | Validated identity before linking |
| Per-asset history | Partial | Yes, on entered data | Not consolidated | Per isolated report | Yes | Up to ten years, from the reports |
| 2D defect mapping | Absent | Rare | Absent | Sometimes | Module-dependent | On the equipment sheet |
| Deployment | Server or cloud | Often heavy | Server or cloud | Mobile | Often cloud | Local, offline |
| Traceability to source PDF | Low | Variable | The document alone | The report it produces | Variable | PDF linked to every value |
AIM, IDMS, CMMS, EAM, DMS, field app: who does what
Distinctions
The acronyms overlap constantly in tenders. Here is a short definition of each category, to place Integrity Loop without ambiguity.
AIM / AIMS: asset integrity management
The approach and platforms that steer equipment integrity across its whole lifecycle. The IDMS is its inspection-data building block.
IDMS: inspection data management
Consolidates the findings in inspection reports into a per-asset history: measurements, findings, deadlines, health KPIs. This is Integrity Loop's role.
CMMS: maintenance management
Plans interventions, work orders and spare parts. It organises the work; it does not put inspection reports to work.
EAM: enterprise asset management
Covers the lifecycle and financial side of assets. Broader than a CMMS, it stays centred on managing them.
DMS: document management
Files and archives documents, inspection PDFs among them. It stores the document; it extracts neither measurements nor findings.
Field inspection app: on-site capture
Used to record findings and readings during the intervention. It produces reports; it does not consolidate them into an asset-base history.
Sovereign, off-cloud, on your workstation or your network
On-premise deployment
Your inspection data stays inside your walls
Inspection data is sensitive. It describes the real condition of your equipment. Integrity Loop runs locally and offline. The reports, the history and the KPIs stay on your workstation or your network, with no transfer to a cloud.
Every value stays linked to its source PDF, one click away. Traceability runs from the consolidated finding back to the original document.
The base consolidates from group down to site, with a steering dashboard that surfaces priorities and deadline alerts. An audit dossier assembles in minutes and exports to Excel, PDF or CSV. The technical decision stays yours: the software structures and clarifies, your experts decide.
What Integrity Loop does not replace
Limits
- It doesn't inspectNon-destructive testing stays with certified technicians. Your providers produce the reports. The software puts them to work without standing in for them.
- It computes no automatic remaining lifeIt performs neither a full RBI nor a failure prediction. It structures, prioritises and makes the history comparable; interpretation stays with the expert.
- It is neither a CMMS nor an EAMIt plans no work and manages no spare parts. It lives alongside those tools, on the inspection data.
- Output quality depends on input qualityAn unsupported format is archived and flagged rather than guessed. An illegible report yields a more cautious summary. Anything that cannot be linked with certainty is flagged.
Frequently asked questions
What inspection managers ask us about inspection data
What is an inspection data management system (IDMS)?
An IDMS centralises the findings held in inspection reports and turns them into a per-equipment history. It imports the PDFs, extracts measurements, findings and deadlines, links every value to the right asset, then recomputes health KPIs. Integrity Loop is the Assets 4.0 IDMS; it performs no inspection and does not replace your CMMS.
How does an IDMS differ from a CMMS or an EAM?
A CMMS plans maintenance and work orders; an EAM manages the lifecycle and cost of assets. Neither is built to read heterogeneous inspection PDFs and draw a per-equipment history from them. The IDMS fills that precise gap, between the report and the decision, and connects to your existing tools rather than replacing them.
Can Integrity Loop read reports from different formats and providers?
Yes. A per-format calibrated adapter reads each report and links its findings to the right equipment, even across several providers and layouts. The equipment identity is validated, never guessed. A format not yet covered is archived and flagged rather than interpreted uncertainly, so nothing enters your history that hasn't been reliably matched.
Does our data stay on our side?
Yes. Integrity Loop runs locally and offline. The reports, the history and the KPIs stay on your workstation or your network, with no transfer to a cloud. Every value stays linked to its source PDF, one click away. Both the traceability and the confidentiality of your inspection data are preserved.
Does it perform inspections or calculate remaining life?
No. The software carries out no inspection and is not an NDT instrument. It produces neither automatic remaining life, nor a full RBI, nor a guaranteed failure prediction. It extracts, links and structures the existing findings for the decision; the technical interpretation stays with your inspectors.
How soon do we get a first per-asset history?
As soon as a first batch of reports is imported, Integrity Loop produces a history over that scope, with health KPIs and deadlines. The roll-out then extends site by site, from group down to each site, without interrupting your operations and without migrating your existing data.
Our expertise
Written from field experience
Assets 4.0
Integrity Loop was born in the field.
- Seven years of B2B business development in industry.
- In close contact with non-destructive testing, inspection and technical management.
- On both the provider and operator sides.
We saw the same scene repeat: serious reports, produced by experts, that stay unused. An IDMS answers that precise gap, without encroaching on the work of certified technicians.
Published on 11 August 2026. Updated on 11 August 2026.
Go further
- Integrity Loop, the Assets 4.0 IDMS (product page)
- Inspection report tracking: the implementation
- AI Maintenance Intelligence: the solutions hub
- COFREND · non-destructive testing in France
- Order of 20 November 2017 · Légifrance
By the Assets 4.0 team · Published on 11 August 2026 · Updated on
The return on investment
Estimate what a usable inspection history saves you.
Deadlines held, audit dossiers assembled in minutes, hours spent reading reports: start from your own figures.
Calculate the ROIYour inspection reports already exist. Let's make them a per-asset history.
Integrity Loop, the Assets 4.0 IDMS, imports your reports, links them to the right equipment and turns them into asset-base steering, on-premise.
