Before the Interval Lengthens: Rebuilding the Inspection Evidence an Ageing Asset Never Collected

The case for moving off a calendar is well rehearsed. Fixed intervals spend inspection effort evenly across equipment whose risk is anything but even. Risk-based inspection puts the effort where probability and consequence of failure are highest, and relaxes it where they are not. Most integrity teams running ageing platforms, gas plants and terminals accept the argument. Much of the debate that follows is about method: qualitative, semi-quantitative or fully quantitative, and which scheme to adopt.

That debate matters less than it appears. Whatever method you choose, your first risk-based cycle is built on inspection history that was collected for a different purpose. The calendar asked one question: was it inspected on time? A risk-based programme asks a harder one: how confident are we in the current condition of this item, for this damage mechanism, at this location, and in the rate at which it is degrading? Twenty years of records can answer the first question perfectly and the second barely at all.

So before any interval lengthens, the inherited evidence has to be audited and graded. That is the step most migrations underestimate, and it is where they either earn credibility or quietly lose it.

What calendar-era records look like

On an ageing fixed platform, topsides piping may carry two decades of ultrasonic spot readings — taken at points re-marked after every painting campaign, by several contractors, with different instruments. On an FPSO, separator internal inspections may be recorded as “no significant findings” without saying what was examined. At an onshore gas plant, an amine contactor may have had a visual internal at every turnaround and nothing else. At an LNG receiving terminal, the insulated cold piping may have almost no history beneath the cladding, because removing insulation is expensive and the calendar never demanded it, while the ambient send-out and seawater systems carry a respectable thickness record.

None of this is negligence. It is what a time-based programme produces. But a risk model fed with it will report more certainty than the evidence supports.

Four questions to ask of every record

Can the reading be tied to the same physical point? A corrosion rate needs a series, and a series needs a fixed location. If condition monitoring locations were re-established, renumbered or lost in a drawing revision, the readings either side of the change are not one series. Record continuity explicitly rather than assuming it.

Could the technique have found the mechanism you now care about? Screen the damage mechanisms against API RP 571 first, then ask whether the historical inspection could have detected them. Spot UT will not reliably find localised pitting under deposits; an external visual says nothing about internal corrosion; a general thickness survey will not detect wet H₂S cracking in sour service. API RP 581 grades inspection effectiveness in five categories, from highly effective to ineffective. Whatever methodology you use, you need an equivalent grading, because a clean report from an ineffective inspection is not evidence that the damage is absent.

Is the thickness series trustworthy? Check baselines: was the first reading measured, or assumed from nominal wall? Were through-coating readings compensated? Do sudden step changes coincide with a change of contractor rather than a change of condition? API 510 and API 570 both depend on credible short- and long-term corrosion rates, and an unreliable baseline corrupts both.

Where are the gaps, and what happened during them? Missed campaigns, deferred scopes, weather-lost access windows and unrecorded changes of service all leave holes. A gap during a period of stable operation is a minor uncertainty. A gap across a feed change or an extended shutdown is a significant one.

What the grades decide

Graded evidence sorts the asset into three groups.

Where history is continuous, relevant to the active mechanisms and well located, it genuinely supports a longer interval, and API 580, API 510 and API 570 all allow risk-based intervals where the assessment justifies them.

Where history exists but is weak, the current interval holds as a conservative interim, and the next inspection is designed to produce evidence: the right technique for the mechanism, at re-established locations, with its effectiveness recorded.

Where history does not exist — typically under insulation, inside dead legs and on cold service — the item is treated as unknown, not as clean. Some intervals will shorten. That is the programme working, not failing.

This reframes the first cycle. It is partly a risk assessment and partly an evidence-collection programme, and it should be planned and budgeted as both.

Stage it, don’t switch it

Few teams can migrate an entire estate in one step, and they should not try. Start where the records are strongest and the consequences are best understood — one platform, one train or one tank area — and prove the full chain: audited history, graded evidence, assessment, revised plan, inspection and update. Then extend it asset by asset, so confidence is earned rather than declared. Keep structural integrity, managed under API RP 2SIM for fixed offshore structures, in its own programme rather than folding it into a process-equipment migration.

Above all, keep the grading itself. When a verifier, auditor or regulator asks why an interval moved from four years to eight, the answer is not the risk matrix. It is the documented judgement that the evidence beneath it was good enough.

Where ONE fits

ONE was developed with operators managing ageing North Sea assets through exactly this kind of transition, and the discipline transfers to any process estate. The Component Asset Register holds equipment, corrosion circuits and monitoring locations with their full history attached, so continuity can be checked rather than assumed. Risk Based Assessment runs on your own probability, consequence and confidence scales, and supersedes rather than overwrites, so the calendar-era basis remains reviewable beside the new one. Workpacks and Inspections and Mobile ONE capture the technique, location and coverage of each new inspection at source, so tomorrow’s records arrive already graded. Reporting and KPIs shows, asset by asset, how much of the programme rests on strong evidence and how much on assumption.

If you are planning a move from time-based to risk-based inspection, or are partway through one, request a demo or talk to us about how your inspection history can be audited and graded before the first interval changes.

Frequently Asked Questions

What is the difference between time-based and risk-based inspection?

Time-based inspection examines equipment at fixed calendar intervals, regardless of its condition or the consequence of it failing. Risk-based inspection, set out in API RP 580, ranks equipment by probability and consequence of failure and directs inspection effort to where the risk is highest. This often lengthens intervals on low-risk items and shortens them on high-risk ones.

Can risk-based inspection extend inspection intervals?

Yes, where the assessment justifies it. API 510 for pressure vessels and API 570 for piping both allow intervals set by a risk-based assessment carried out to API RP 580. The extension has to be supported by credible inspection history, and the assessment has to be revisited when conditions change.

What is inspection effectiveness in RBI?

Inspection effectiveness describes how likely an inspection was to detect and size a particular damage mechanism. API RP 581 grades it in five categories, from highly effective to ineffective. A clean result from an ineffective technique gives little confidence that the damage is absent, so effectiveness affects how much credit a past inspection earns in the risk assessment.

What data do you need before moving to risk-based inspection?

You need a reliable register of equipment and corrosion circuits, the materials and operating conditions of each, a screened list of active damage mechanisms, and inspection history tied to fixed monitoring locations. Each historical inspection should record its technique and coverage. Where that history is missing or weak, the first risk-based cycle should keep conservative intervals and gather better evidence.