API 510 vessel inspection: what the record must carry

An API 510 vessel file gets asked two questions. Is the vessel fit to run to the next inspection, and can you show how you decided. The first question is engineering. The second is record-keeping, and it is the one that fails audits. Thickness readings live in a gauge export, the corrosion rate lives in a spreadsheet, the MAWP check lives in an engineer's notebook, and the repair record lives in a contractor's PDF. Each piece may be correct. Together they cannot be defended, because nobody can show the chain from reading to interval. This paper lays out what the record has to carry under API 510 and the ASME Section VIII construction basis, and what that implies for the software holding it.

What does API 510 require the inspection record to contain?

API 510 places the record on the owner-user. The inspection agency and the authorized inspector contribute, but the file belongs to the operator, and the code expects it to be permanent and progressive for the life of the vessel. The records section of the code groups the content into four families.

• Construction and design information. The manufacturer's data report, design drawings, design pressure and temperature, materials, nominal thicknesses, joint efficiencies, corrosion allowance, and the construction code edition. Without these, tMin and MAWP cannot be recomputed later.
• Inspection history. Every inspection report with its date, type (internal, external, on-stream), extent, findings, thickness readings at each condition monitoring location (CML), the corrosion rates derived from them, and the remaining life and interval that followed.
• Repair, alteration and rerating information. What was done, by whom, to which procedure, the examination and pressure test that closed it, and the engineering approval behind any change of design conditions.
• The inspection plan. API 510 requires a plan for each vessel: the damage mechanisms expected, the inspection methods and extent chosen to find them, the surface preparation needed, and the interval. The plan is a living record and changes when findings change.

The word that matters is progressive. A record that is rebuilt from scratch for every turnaround is not an API 510 record. The file must show each reading against the one before it, at the same location, on the same vessel, so that a trend is a fact rather than an inference.

How are corrosion rate and remaining life calculated under API 510?

The calculation is short, but the record around it is not. API 510 defines two rates and asks the inspector to consider both.

• Long-term rate = (initial thickness minus actual thickness) divided by the years between those readings. This smooths out measurement noise and reflects the whole service history.
• Short-term rate = (previous thickness minus actual thickness) divided by the years between those two readings. This reacts to a change in feed, temperature or chemistry.

Remaining life = (actual thickness minus required thickness) divided by the corrosion rate. The required thickness is the greater of the pressure-design tMin from the construction code and any structural minimum the owner has adopted. The inspector, with a corrosion specialist where the mechanism is uncertain, selects the rate that best represents expected service; a common conservative practice is to take whichever rate gives the shorter remaining life. For a vessel entering new service with no history, API 510 accepts a rate estimated from similar service or published data, and if neither is available, thickness determinations after approximately a thousand hours of operation.

The record has to hold the choice, not just the answer. An auditor who sees a remaining life of fourteen years and a rate of four mils per year will ask which rate that is, what the previous reading was, and who decided. If the answer is a cell in a spreadsheet, the trail ends there.

How is the API 510 inspection interval set?

The interval rules are the part of API 510 most people can recite, and the part most files cannot substantiate.

• Internal or on-stream inspection: the lesser of one half of the remaining life or ten years.
• Remaining life under four years: the interval may be the full remaining life, but not more than two years.
• External inspection: at least every five years, or at the internal interval, whichever is shorter.
• Pressure relieving devices: inspected and tested per API 576 at intervals set by performance, with code maximums of five years for typical process service and ten years for clean, non-corrosive service.
• On-stream inspection in place of internal: permitted when the conditions the code lists are met, including a characterized general corrosion mechanism, a known rate, and adequate remaining life, with no cracking or hydrogen damage mechanisms expected.
• Risk-based intervals: API 510 allows an RBI assessment to API 580 to set the interval, including beyond the fixed maximum, provided the assessment is documented, approved, and reassessed after each inspection, after process changes, and at the maximum cycle the code sets.

Each bullet is a rule, and each rule needs its inputs on file. The half-life cap needs the remaining life. The two-year cap needs the trigger. The on-stream substitution needs the evidence that the conditions held. The RBI interval needs the assessment and its approvals. Software that stores only the next due date has stored the least useful part.

What must the thickness record carry for each CML?

A CML is not a number. It is a location with a design basis, a history, and a method. To recompute anything later, each CML record needs at least the following.

• Identity: vessel, component (shell course, head, nozzle), position, and the drawing or grid reference that lets the next technician find the same spot.
• Design basis: nominal thickness, design pressure and temperature, material and allowable stress, joint efficiency, inside radius or diameter, corrosion allowance.
• Required thickness: tMin, the method that produced it (which code formula, which structural minimum), and the date it was set.
• Readings: every thickness with its date, instrument, technician and method (UT, RT, profile), never overwritten.
• Derived values: short-term rate, long-term rate, the governing rate, remaining life, and the interval that follows.

The reason the design basis sits on the CML and not only on the vessel is that nozzles, heads and shell courses have different tMin values. A head to ASME VIII Division 1 uses a different formula from a cylindrical shell. Storing one tMin per vessel is the most common structural error in a thickness database, and it usually understates the required thickness on the component that governs.

How does the record handle MAWP and tMin?

API 510 ties condition back to the construction code. For a cylindrical shell under ASME VIII Division 1, the required thickness for circumferential stress is t = PR / (SE minus 0.6P), and the corresponding MAWP is SEt / (R plus 0.6t), with R the inside radius, S the allowable stress at temperature, and E the joint efficiency. Heads, cones and nozzle reinforcement have their own formulas, and the record has to say which one it used.

When a vessel has corroded, API 510 asks for MAWP to be recomputed with the actual thickness minus twice the corrosion expected before the next inspection, which is the rate multiplied by the interval, doubled. This is why the interval and the MAWP are coupled: shorten the interval and less future corrosion is subtracted. If the MAWP falls below the pressure the relief system is set to protect, the options are rerate, repair, or reduce the interval, and each is a recorded decision.

A number without its formula is an assertion. A number with its formula, inputs and edition is a calculation someone else can repeat.

That sentence is the practical test for any thickness record. If the file shows tMin as 0.312 inches with no formula and no allowable stress, the next engineer has to rebuild the calculation to trust it. If the file shows the formula, the inputs, the code edition and the date, the calculation is evidence.

What does an auditor look for in an API 510 vessel file?

Regulators, insurers and internal audit groups differ in emphasis, but the questions converge.

• Is every vessel in the plan, and does every vessel have a current inspection plan with named damage mechanisms?
• Is the interval traceable to a remaining life, and the remaining life to readings and a rate?
• Are the readings at the same CMLs over time, or has the CML set drifted so the trend is meaningless?
• Were repairs and alterations classified correctly, executed to a documented procedure, and closed with the examination and test the code requires?
• Who signed, were they qualified, and could that person have changed the record after signing?
• Can the report issued at the time be reproduced exactly, even if the form has changed since?

The last two questions are where paper files and generic document systems fail. A signature scanned into a PDF proves nothing about later edits. A form that was redesigned last year cannot reproduce a report from three years ago unless the system pinned the configuration the report was executed with.

How intelliSPEC handles it

intelliSPEC treats the vessel record as the durable object and the inspection as an event against it. Thickness readings land in intelliNDT from seven supported gauge profiles over Bluetooth or keyboard wedge, including DeFelsko and Evident ultrasonic gauges, without retyping. Each CML carries 64 fields, including nominal thickness, tMin and the method that set it, design pressure, material, allowable stress, joint efficiency, corrosion allowance, grid geometry, latest thickness and three corrosion rates.

The calculation engine routes tMin by equipment type, so a vessel is computed to ASME VIII Division 1, piping to ASME B31.3 and tanks to API 653, and each result returns the design code and the formula alongside the number. MAWP is computed from the same inputs. The corrosion summary produces short-term, long-term and maximum rates, takes the maximum as governing, and computes remaining life as thickness minus tMin over the rate. The API 510 interval is capped at half the remaining life. These sit among 199 registered calculators, each with its own permission grant, so who may run and who may approve a calculation is a role decision, not a habit.

Visual and internal inspections are captured in intelliINSPECT with photos, drawing annotation that detects CML points automatically, and signatures with per-signer identity on a shared device. Completed records pin the form configuration, locale and reference options they were executed with, so a report from a prior turnaround renders as it was issued even after the form has been redesigned. Every create, update and delete carries actor, tenant, request id, IP address and user agent, and is linked into a SHA-256 hash chain per tenant that a verify routine recomputes for auditors. Audit events are never auto-deleted. RBI and fitness-for-service assessments that extend or shorten the interval are handled in intelliINTEGRITY, and the terms used throughout are defined in the glossary.

None of this changes what API 510 asks for. It makes the chain from reading to interval a query rather than a reconstruction.