A pressure vessel is a contained energy system. The energy stored in a pressurised vessel — whether the content is steam, hydrocarbon, process gas, or chemical — is released suddenly and completely when the pressure boundary fails. The consequence is not proportional to the size of the defect that initiated the failure. A pinhole corrosion pit that penetrates a vessel wall in a high-energy service does not produce a pinhole release. It produces a catastrophic one.
Pressure vessel integrity management exists to prevent that progression. Not to respond to it. API 510, ASME Section VIII, and the NBIC collectively define what prevention requires — measurement, trending, assessment, and documented decision-making at defined intervals, by qualified personnel, against established acceptance criteria. What most Ontario facilities operate is something substantially less than that. The gap is not a matter of degree. It is a matter of programme architecture.
A pressure vessel that is registered with TSSA, inspected on the TSSA-mandated interval, and returned to service with a valid certificate of inspection is not necessarily in a compliant integrity programme. TSSA registration confirms the vessel exists and has been examined. It does not confirm that the examination included wall thickness measurement, corrosion rate calculation, remaining life estimation, or a fitness-for-service determination. A vessel can be fully TSSA-current and simultaneously accumulating damage that no one has measured.
The Pressure Vessel Family in Industrial Service
Pressure vessels in industrial facilities are not a single asset type. Each vessel type operates under different process conditions, accumulates damage through different mechanisms, and presents different inspection challenges. A programme that does not differentiate by vessel type and service condition will apply the wrong examination method to the wrong location and miss the dominant failure mode.
What API 510 Actually Requires
API 510, Pressure Vessel Inspection Code: In-Service Inspection, Rating, Repair, and Alteration, is the governing standard for the in-service inspection of pressure vessels in refinery, petrochemical, and general industrial service. It is not a TSSA document. It is an industry standard that defines what competent pressure vessel inspection practice requires — and its requirements substantially exceed what TSSA mandates as a minimum.
Inspector Qualification
API 510 requires that pressure vessel inspections be conducted by or under the direction of an Authorized Pressure Vessel Inspector — a qualification defined in API 510 Appendix B and administered through API's Individual Certification Programme. The API 510 inspector is not simply a person who has examined pressure vessels. They hold a specific certification that demonstrates knowledge of damage mechanisms, NDE methods, fitness-for-service assessment, repair standards, and regulatory requirements. A programme that assigns pressure vessel inspection to a maintenance technician or an unqualified contractor is not API 510 compliant — regardless of how thorough the examination appears.
Damage Mechanism Identification
Before any inspection is planned, API 510 requires identification of the active and credible damage mechanisms for each vessel based on its process service, operating conditions, and construction materials. API 571, Damage Mechanisms Affecting Fixed Equipment in the Refining Industry, provides the reference taxonomy — covering over sixty damage mechanisms from general corrosion through stress corrosion cracking, hydrogen embrittlement, creep, and fatigue. The inspection plan is built from the damage mechanism assessment. An inspection that was not preceded by damage mechanism identification has no technical basis for the examination methods it selected or the locations it examined.
Risk-Based Inspection Interval Setting
API 510 allows — and in practice requires for a defensible programme — risk-based inspection intervals derived from a probability of failure assessment combined with a consequence of failure assessment. API 581 provides the quantitative RBI methodology. The resulting interval is not a fixed number from a table. It is a calculated value that reflects the specific vessel's damage rate, remaining life, consequence category, and inspection effectiveness. Two identical vessels in different services will have different inspection intervals under RBI. A programme that applies a single fixed interval to all vessels of the same nominal type is not operating a risk-based programme.
NDE-Based Thickness Measurement and Corrosion Rate Calculation
Every API 510 inspection includes ultrasonic thickness measurement at defined locations — not spot checks, but a documented grid of measurement points sufficient to characterise the corrosion profile across the vessel shell, heads, and nozzles. Results are compared against previous measurements at the same locations. A corrosion rate is calculated — in mils per year or mm per year — from the difference between measurements divided by the elapsed time. Remaining life is calculated from the corrosion rate and the remaining thickness above the minimum required by ASME Section VIII. The next inspection interval is set from the remaining life calculation. This is the measurement chain that drives a compliant programme. Without it, there is no programme — there is only a visual inspection on a schedule.
Fitness-For-Service Assessment
When an inspection reveals damage — a corroded region, a crack, a dent, a weld flaw — the decision of whether the vessel is acceptable for continued service is not made by the inspector on the day. It is made through a documented fitness-for-service assessment under API 579. API 579 provides assessment levels — from simple screening calculations through detailed stress analysis — for every major damage type. The FFS assessment produces a documented conclusion: acceptable as-is, acceptable with a reduced maximum allowable working pressure, requires repair before return to service, or retire. That conclusion and its basis become part of the vessel's permanent record. A programme that returns vessels to service after discovering damage without a documented FFS assessment has made an undocumented engineering decision — which is not a decision at all.
The Five Programme Failures That Drive Vessel Failures
The TSSA Regulatory Position in Ontario
In Ontario, pressure vessels above the thresholds defined in the Technical Standards and Safety Act and Ontario Regulation 220/01 are subject to mandatory registration, periodic inspection, and certificate of inspection renewal administered by TSSA. The obligations are not optional programme elements — they are legal requirements with enforcement consequences including equipment shutdown orders and administrative penalties.
TSSA's inspection intervals and requirements represent the regulatory minimum. API 510, ASME Section VIII, and the NBIC represent the industry standard of care. A facility operating at the regulatory minimum without meeting the industry standard of care has a documented gap between its legal obligation and its programme practice — a gap that will be identified in any regulatory audit and exploited in any civil proceeding following a failure.
Repairs to registered pressure vessels in Ontario must be performed by a TSSA-authorised repair organisation holding an NBIC R-stamp. A repair data report must be filed. The vessel's registration must be updated. These are not administrative preferences — they are the documented chain of custody for the vessel's condition history that TSSA will require and that liability defence requires.
RISL assesses pressure vessel inspection programmes against API 510, API 579, API 581, ASME Section VIII, NBIC, and TSSA O. Reg. 220/01. The assessment identifies the gap between regulatory compliance and industry standard of care — and produces an execution-grade corrective programme that closes it. Every vessel in scope is assessed. Every damage mechanism is identified. Every inspection record is reviewed for measurement completeness and corrosion rate calculability. The output is a programme, not a report.
The Governing Standards
What a Compliant Programme Produces
A pressure vessel inspection programme that meets API 510 and supports TSSA compliance simultaneously produces the following — for every vessel in scope, at every inspection interval:
A damage mechanism assessment that identifies every active and credible damage mechanism for the vessel in its service, referenced to API 571, and updated whenever process conditions change.
A risk ranking derived from consequence of failure and probability of failure assessments under API 581, producing a documented inspection interval that is specific to the vessel and defensible against challenge.
An inspection plan that specifies examination methods, examination locations, and acceptance criteria for each damage mechanism identified — not a generic visual and UT package applied uniformly to every vessel regardless of service.
A thickness measurement record with documented measurement locations, results, comparison to previous measurements at the same locations, calculated corrosion rate, calculated remaining life, and a next inspection date derived from the remaining life.
A fitness-for-service determination for every instance of damage found — whether the result is acceptable as-is, acceptable at reduced MAWP, requires repair, or requires retirement. Documented. Signed. Filed with the vessel record.
A repair record for every repair performed — NBIC R-stamp organisation, repair data report, TSSA filing, and updated registration. No undocumented repairs. No returns to service without documented authorisation.
This is not an aspirational standard. It is the documented industry practice for pressure vessel integrity management. The facilities that operate to it do not experience catastrophic pressure vessel failures. The facilities that operate below it accumulate damage they have not measured, make decisions they have not documented, and eventually produce events that were entirely predictable — and entirely preventable.
RISL assesses pressure vessel inspection programmes against API 510, API 579, NBIC, and TSSA O. Reg. 220/01. Damage mechanism identification, corrosion rate trending, fitness-for-service documentation, and repair record completeness — each element assessed, each gap closed with an execution-grade programme.
Engage RISL