Remaining life and the next inspection date

The next inspection date is the most consequential number an integrity program produces and the least examined. It sets when a unit comes down, how much scaffold gets built and whether a vessel runs another five years or another eighteen months. It is derived from a remaining life calculation that is itself derived from a required minimum thickness and a corrosion rate, each of which involves a choice. When the date is wrong, it is usually because one of those choices was invisible. This paper walks the calculation as API 510, API 570 and API 653 set it out and describes what the record must show so the date can be checked rather than trusted.

What is remaining life and how is it calculated?

The remaining life formula is the same across the standards:

Remaining life (years) = (t actual minus t required) divided by corrosion rate.

The three inputs:

• t actual is the current measured thickness at the controlling CML, the one that gives the shortest remaining life on the component.
• t required (tMin) is the minimum thickness the equipment needs to carry its design conditions, from the design code, or a structural minimum where that governs.
• Corrosion rate is the governing rate, chosen between the long-term and short-term rates at that CML as described in API 510 and API 570.

The formula is trivial. The engineering is in the inputs. A remaining life of eight years on one CML and two years on the CML next to it is not an inconsistency; it is the reason CMLs exist. The component's remaining life is the minimum across its CMLs, and the record must show which CML controlled and why.

Remaining life is recalculated at every inspection. A component that showed twelve years remaining at the last inspection and eight years now has lost more than the interval implies, and the rate should be examined before the date is set.

Where does the required minimum thickness come from?

tMin is not a lookup. It is computed from the design code for the equipment type at the design pressure and temperature, and it can be governed by pressure or by structure.

• Pressure vessels use ASME Section VIII Division 1. For a cylindrical shell under internal pressure the circumferential stress formula gives t equal to PR divided by (SE minus 0.6P), where P is design pressure, R is inside radius, S is the allowable stress at temperature and E is the joint efficiency. Heads, cones and nozzles have their own formulas.
• Piping uses ASME B31.3. The pressure design thickness is t equal to PD divided by 2(SEW plus PY), where D is outside diameter, W is the weld joint strength reduction factor and Y is the temperature coefficient. Piping frequently has a structural minimum, from API 574 tables or the owner's practice, that exceeds the pressure design thickness for small bore and low pressure lines. The higher of the two governs.
• Atmospheric storage tanks use API 653 for the in-service shell minimum, computed course by course from the liquid height and specific gravity, with an absolute floor stated in the standard. Bottom plates have a separate minimum thickness at the next internal inspection.

Two records matter here. First, the design conditions and material used in the calculation must be the equipment's actual design conditions, from the data sheet or U-1 form, not a default. Second, the record should show the code, the formula and each input, so the tMin is a reproducible calculation rather than a value someone typed. When the design basis changes (a rerate, a change in allowable stress edition, a new relieving pressure), tMin changes and every remaining life on the equipment moves with it.

How do API 510, API 570 and API 653 cap the interval?

Each standard takes remaining life and turns it into a maximum interval.

API 510 (pressure vessels). The internal or on-stream inspection interval is no more than half the remaining life or ten years, whichever is less. When the remaining life is less than four years, the interval may be the full remaining life up to a maximum of two years. External inspection is due at least every five years or at the internal or on-stream interval, whichever is less. A documented risk-based inspection assessment under API 580 may set different intervals, with the assessment reviewed at intervals the standard specifies.

API 570 (piping). Thickness measurement intervals are capped by class: Class 1 at five years, Class 2 and Class 3 at ten years, with Class 4 optional. Within those ceilings, the interval is no more than half the remaining life. External visual inspection intervals are also class-based. Injection points and soil-to-air interfaces have their own, shorter, requirements.

API 653 (tanks). Shell external ultrasonic thickness intervals depend on whether a corrosion rate is known: a shorter default when it is not, and a longer ceiling when the rate supports it, with the half-life logic applied to the shell remaining life. The internal inspection interval is set so the bottom does not fall below its minimum before the next inspection, with a maximum stated in the standard and extension possible under a documented risk-based assessment.

The common structure: remaining life sets a half-life interval, the standard imposes a ceiling, and the shorter governs. Any departure from that requires a documented risk-based assessment, not a management decision.

What are the common errors in the next inspection date?

The errors are rarely in the division. They are in what went into it and what came out.

• Wrong tMin basis. Using nominal minus corrosion allowance as tMin, or using a pressure design thickness where the structural minimum governs. Both produce a remaining life that is not the equipment's.
• Nominal used as t initial without mill tolerance. For long-term rate on equipment with no baseline reading, nominal thickness overstates the starting wall and the rate.
• Stale rate. Carrying last inspection's governing rate forward without recomputing from the new reading.
• Controlling CML missed. Computing remaining life on the average or on the CML the inspector happened to read, rather than the minimum.
• Interval applied from the wrong date. Counting from the date the report was signed rather than the date the thickness was measured, which can shift the due date by months on a long turnaround.
• Half-life applied without the ceiling. A remaining life of forty years does not produce a twenty-year interval under API 510; ten is the cap.
• Rerate not propagated. Design pressure or allowable stress changed and tMin was not recalculated, so remaining life still reflects the old basis.
• Repair not reflected. A weld repair or replacement spool reset the thickness at a CML, and the history was not restarted, so the long-term rate is computed across a discontinuity.

Every one of these is invisible on a record that shows only the next inspection date. Every one is obvious on a record that shows the chain.

What should the record show for the date to be defensible?

A reviewer, an auditor or a successor inspector should be able to reproduce the next inspection date from the record without a phone call. That means the record for a component carries:

1. Design basis: code and edition, design pressure and temperature, material and allowable stress, joint efficiency, corrosion allowance, and the source document.
2. tMin with the formula, each input, the resulting value, and whether pressure or structural minimum governs.
3. Thickness history at each CML: every reading with date, technician, gauge and procedure.
4. Corrosion rates at each CML: long-term, short-term and the governing rate with the reason for the choice.
5. Remaining life at each CML, and the controlling CML for the component.
6. Interval: the half-life value, the standard's ceiling, any risk-based assessment applied, and the resulting interval.
7. Next inspection date with the date it was counted from.
8. Verification: who reviewed the calculation and when, since a computed value is provisional until an engineer accepts it.

This is more than most programs record, and less than most programs know. The gap is between what the inspector worked out and what was written down.

How intelliSPEC handles it

intelliINTEGRITY computes the chain end to end and shows its work. tMin routes by equipment type to ASME B31.3 for piping, ASME Section VIII Division 1 for vessels or API 653 for tanks, and the result is returned with the design code and the formula used. MAWP is computed alongside. Each CML record carries nominal thickness, tMin and its method, design pressure, material, outside diameter and schedule, allowable stress, joint efficiency, corrosion allowance, latest thickness and three corrosion rates, with the maximum governing by default. Remaining life is (t minus tMin) divided by the governing rate, and the API 510 or API 570 interval is capped at half the remaining life.

Every calculated result is provisional until an engineer verifies it, and the product never auto-derates equipment. API 579-1 Part 4 Level 1 screening is available for general metal loss (RSF as measured thickness over tMin); API 579 Part 5 Level 1 for local metal loss is deliberately not implemented pending licensed-engineer verification, which is the honest position for software to take. Completed records pin the configuration and reference options they were executed with, so the calculation an auditor sees in five years is the one the engineer verified.

The thickness readings behind the calculation arrive from gauges over Bluetooth or keyboard wedge without retyping, and the intelliNDT record holds the procedure and technician qualification with each reading. For the semi-quantitative risk-based scoring that can support a documented departure from the half-life interval, see the API 580 and 581 approach on the same module page, and for term definitions see the glossary.