Operational
Pressure vessel inspection software — a working guide for program owners
What pressure vessel inspection software has to do: the asset register, the inspection schedule, the NDE records, the deficiency tracking, and the renewal — under ASME, NBIC, and OSHA PSM mechanical integrity.
QEHS safety desk
Safety practitioners on staff
9 min read · 9 sections
Why pressure vessel inspection is a software problem
A pressure vessel program is a scheduling problem before it is an engineering problem. The same plant that would never let a forklift certificate lapse will run a boiler past its internal inspection because no one owned the date. The asset register, the inspection schedule, the non-destructive examination records, the deficiency corrections, and the renewal certificates are five separate data sets in most plants, and the gap between them is where the findings live. Pressure vessel inspection software closes that gap by putting all five against the asset, with the schedule driving the work and the work generating the evidence.
The regulatory frame — ASME, NBIC, and OSHA PSM
Three standards govern a pressure vessel program, and a good platform holds them in one place. ASME Boiler and Pressure Vessel Code Section VIII governs the design and construction of the vessel — the U-stamp on the nameplate is the evidence the vessel was built to code. The National Board Inspection Code (NBIC) governs in-service inspection, repair, and alteration once the vessel is operating. OSHA Process Safety Management (29 CFR 1910.119) applies to vessels that hold a hazardous substance above the threshold quantity, and its mechanical-integrity element adds inspection-and-testing procedures, deficiency correction, and documentation on top of the NBIC baseline. For the definitional entry, see the [pressure vessel inspection](/glossary/pressure-vessel) glossary hub.
Most vessels in a process plant are not PSM-covered, but the ones that are carry the heaviest obligation. A platform that treats PSM vessels and non-PSM vessels differently — different intervals, different documentation depth, different change-control — is doing the right thing. A platform that treats them the same is either over-documenting the routine vessel or under-documenting the PSM one.
What the inspection-software module has to do
- Asset register — every vessel with its ASME U-stamp serial, National Board number, design pressure, MAWP, year of manufacture, and jurisdictional classification.
- Inspection schedule — external annual, internal every 3 to 5 years, ultrasonic thickness testing at corrosion-prone points, relief-device testing and recalibration, all driven off the asset.
- NDE records — the methods used (ultrasonic, magnetic-particle, dye-penetrant, radiography), the readings, the wall-thinning map, and the remaining-life calculation.
- Deficiency tracking — every finding opens a corrective action with a due date, a responsible party, and a permit link for the shutdown repair.
- Renewal and certification — the Authorized Inspector sign-off, the R-1 repair form, the certificate of inspection, and the next due date filed against the asset.
Inspection types and intervals
There are five inspection types and they run on different clocks. An external inspection is performed annually while the vessel is in service, checking for leaks, corrosion, insulation damage, and relief-valve condition. An internal inspection requires the vessel to be shut down, isolated, and entered (or boroscoped) on a 3- to 5-year interval to examine the shell, heads, welds, and internal components. Thickness testing maps remaining wall at corrosion-prone locations and feeds the remaining-life calculation that sets the next interval. Pressure-relief devices are tested and recalibrated on their own schedule. Non-destructive examination — ultrasonic, magnetic-particle, dye-penetrant, and radiography — is used for weld inspection and crack detection without removing material.
The intervals are set by the NBIC, the manufacturer, and the jurisdiction, and many states and provinces require a commissioned inspector and a filed report. A platform that lets the program override an interval without recording the engineering basis is a liability; a platform that forces the override to carry the basis and the sign-off is the audit trail.
Certification and the R-Stamp repair workflow
Pressure vessel certification is the authority to sign off an inspection or perform a repair. In-service inspection is typically performed by an Authorized Inspector commissioned by the National Board, often working for an Authorized Inspection Agency (AIA) or, in jurisdictions that operate it, the state boiler inspector. Repairs and alterations must be performed by an ASME-certified organization holding an R Stamp (the NBIC repair stamp), and the repair must be documented on an R-1 form filed with the National Board.
Documentation — the record an auditor asks for
Every inspection must produce a record that identifies the vessel (ASME U-stamp serial and National Board number), the inspector and their commission, the methods and tests performed, the thickness readings and the remaining-life calculation, any corrosion or crack findings, the corrective actions, and the next inspection due date. In a QEHS platform these records live against the asset, so the inspection history, the repair history, and the change history are one click apart. An auditor who asks to see the last internal inspection on vessel PV-1042 should not wait while someone searches three systems.
The documentation is also what the insurer reads. Boiler and machinery carriers require current inspection records as a condition of coverage, and many jurisdictions require a valid certificate of inspection before a vessel may legally operate. An overdue inspection can exclude the vessel from property and liability policies and void business-interruption cover.
How it ties to PSM mechanical integrity, MOC, and permit-to-work
For PSM-covered vessels, the mechanical-integrity element of 29 CFR 1910.119 requires written inspection-and-testing procedures, deficiency correction, and documentation. That ties the inspection program to three other programs the platform runs. Management of change (MOC) has to fire when a vessel is altered, when the service changes, or when the inspection interval is re-baselined — see the [management of change](/glossary/moc) and [process safety management](/glossary/psm) entries. The permit-to-work system has to govern the shutdown, the isolation, and the confined-space entry that the internal inspection requires — see the [permit-to-work deep dive](/guides/permit-to-work-deep-dive). The corrective-action workflow has to close the deficiency the inspection found, with the same root-cause discipline that closes any other nonconformance.
The integration is the point. A pressure vessel inspection that lives in a standalone spreadsheet cannot tie its findings to a permit or to an MOC, and that is the gap that turns a routine finding into a reportable incident.
Configuring pressure vessel inspection in the Composer
- Create the asset register from the pressure-vessel template — one record per vessel, with the ASME and National Board identifiers as required fields.
- Set the inspection schedule per vessel class — external annual, internal 3 to 5 years, thickness testing, relief devices — and let the renewal engine flag the next due date.
- Wire the inspection work order to a permit-to-work for the shutdown, so isolation and confined-space entry are not separate conversations.
- Attach the NDE record template (method, readings, wall-thinning map, remaining-life) to the inspection work order, so the evidence is captured at the point of the work.
- Route every deficiency to a corrective action with a due date and a responsible party; block closure without the R-1 reference if the deficiency is a repair.
- Tag PSM-covered vessels so their inspection depth, change-control, and documentation meet the 1910.119 mechanical-integrity bar without over-burdening the routine vessel.
The findings an auditor writes
The findings an auditor or an insurer writes on a pressure vessel program are remarkably consistent, and they are almost all data gaps rather than engineering failures. The vessel register does not match the plant walkdown. The last internal inspection is on record but the thickness readings are missing. A repair was performed but the R-1 form is not filed. A relief device is overdue for recalibration. A PSM-covered vessel is being inspected at the non-PSM interval. The next inspection date is not on the asset. Each of those is a single record-keeping failure, and each is closed by a platform that owns the schedule, the record, and the renewal in one place.