ASME PCC-2 repairs: recording the fix with the finding

A repair is where an inspection finding stops being information and becomes metal. It is also where the record most often breaks. The finding lives in the inspection report, the repair lives in a work order, the weld procedure lives with the contractor, the pressure test lives in a QA file, and the temporary clamp that was supposed to come off at the next turnaround lives in nobody's memory. ASME PCC-2 gives repair methods a common structure, and that structure is also the outline of a defensible repair record. This paper describes what PCC-2 covers, how repair classification drives the documentation, and how to record a fix so it stays attached to the finding it addressed.

What is ASME PCC-2 and how is it organized?

ASME PCC-2, Repair of Pressure Equipment and Piping, collects accepted repair methods for pressure-retaining equipment built to ASME and similar codes. It does not replace the inspection code (API 510, API 570, API 653, or the National Board Inspection Code) that decides when a repair is needed and what approvals it requires. It describes how the repair is done.

The standard is organized into parts and articles.

• Part 2, Welded repairs. Butt-welded insert plates, external weld buildup to repair internal thinning, seal-welded threaded connections, welded leak boxes, full encirclement steel reinforcing sleeves for piping, fillet welded patches with and without reinforcing plug welds, alternatives to preheat and to post-weld heat treatment, in-service welding onto carbon steel, weld overlay and clad restoration, threaded or welded plug repairs, and field heat treating of vessels.
• Part 3, Mechanical repairs. Replacement of pressure components, freeze plugs, damaged threads in tapped holes, flaw excavation and weld repair, flange repair and conversion, mechanical clamp repair, pipe straightening, damaged anchors in concrete, valves with pressure-seal bonnets, hot bolting and hot and half bolting removal, and inspection and repair of shell and tube heat exchangers.
• Part 4, Nonmetallic and bonded repairs. Composite repair systems for high-risk and low-risk applications, and sprayed nonmetallic internal linings for buried pipe.
• Part 5, Examination and testing. Pressure and tightness testing of piping and equipment, and nondestructive examination in lieu of pressure testing.

Every article follows the same seven headings: description, limitations, design, fabrication, examination, testing and references. That consistency is a gift to the record keeper. A repair record built on the same seven headings captures what the standard considers essential for that method, and the limitations heading in particular forces the question a review will ask later: was this method applicable to this situation.

Repair or alteration: why the classification matters

Before any article is chosen, the inspection code decides what kind of work this is, and the classification governs everything downstream.

• Repair restores the equipment to a condition suitable for safe operation at the existing design conditions. Examples are a weld buildup on a thinned area, replacement of a corroded section in kind, or a fillet welded patch within the code's limits.
• Alteration is a physical change with design implications affecting pressure-containing capability beyond the scope of the original data report. Adding a nozzle above a certain size, changing a shell course thickness, or installing a different head are alterations.
• Rerating changes the design pressure or temperature, up or down, and requires engineering calculations and, where applicable, revised nameplate data.

The distinction determines who must approve, what engineering is required, whether jurisdictional forms are needed where the jurisdiction adopts the National Board Inspection Code, and whether a pressure test is mandatory. API 510, for example, normally requires a pressure test after an alteration and leaves the test after a repair to the inspector's judgment, with NDE permitted as a substitute under defined conditions. The classification is therefore the first field of the repair record, and it needs a name and a date behind it. Misclassifying an alteration as a repair is one of the most common audit findings in mechanical integrity programs, and it is nearly always a documentation failure rather than a bad weld.

Which PCC-2 repair methods are temporary?

PCC-2 does not label articles temporary or permanent; the inspection codes and the engineering evaluation do. But some methods are used as temporary repairs far more often than not, and the record must treat them differently.

• Welded leak boxes (Article 2.4). An enclosure welded around a leaking or thinned area. Requires design for the full pressure, consideration of the sealant and the trapped process fluid, and a monitoring plan.
• Mechanical clamps (Article 3.6). Bolted enclosures with sealant, often installed on a live leak. Bolt torque, sealant life, and the condition of the pipe under the clamp are all unknowns that a monitoring plan has to cover.
• Full encirclement sleeves (Article 2.6). Type A sleeves are not welded circumferentially to the pipe and reinforce a non-leaking defect; Type B sleeves are fillet welded at the ends and can contain pressure. Type A is not appropriate for a defect that may leak, and the record must state the type.
• Composite wrap repairs (Articles 4.1 and 4.2). Fiber-reinforced polymer systems engineered to restore strength for a stated design life. The design life is a documented value, not an assumption, and the installation record needs surface preparation, ambient conditions, cure, number of layers and material batch identification. Installer qualification is part of the method.
• Fillet welded patches (Articles 2.7 and 2.12). Permitted with limits on size, thickness and service; often used as temporary repairs on vessels and later replaced by insert plates.

API 510 and API 570 both expect temporary repairs to be replaced with permanent repairs at the next available maintenance opportunity. A temporary repair may stay longer only if the engineer and inspector evaluate, approve and document it. That sentence describes a record with a clock on it: an install date, a design life or review date, a monitoring requirement, an owner, and a planned permanent repair. A plant that cannot list its temporary repairs from its records has a population of clamps whose age nobody knows.

What does each repair record need to carry?

Using the PCC-2 article structure as the outline, a repair record that will survive audit contains the following.

• The finding. Which inspection, on which component, found what. Thickness readings, crack indications, photographs and the assessment (including any API 579 evaluation) that concluded a repair was needed.
• The classification. Repair, alteration or rerate, with the name of the person who classified it and the code basis.
• The method. The PCC-2 article, and any owner or jurisdictional specification that supplements it.
• Limitations check. Confirmation that the article's limitations were reviewed and the method applies to this material, service, temperature and geometry.
• Design. Calculations or the engineering basis for the repair, including for composite repairs the design life and design pressure, and for sleeves the type and the reinforcement basis.
• Fabrication. Materials with certifications, the welding procedure specification and procedure qualification record, welder qualifications, preheat and heat treatment records, and any in-service welding controls.
• Examination. The NDE performed, method, extent, procedure, technician qualification, and results with the acceptance criteria applied.
• Testing. The pressure or tightness test with pressure, medium, duration and result, or the documented decision to substitute NDE under Article 5.2 and the code, with the approvals.
• Acceptance. Inspector and engineer signatures with dates, and where required the jurisdictional documentation.
• Temporary repair controls. Install date, design life or review date, monitoring plan and results, owner, and the planned permanent repair with its target window.

Each item is a field or a document, and the entire set belongs against the component in the equipment record, not in a project folder that closes when the turnaround does.

How is a repair examined and tested?

Part 5 of PCC-2 covers the closing steps, and the inspection codes decide when they are required.

Article 5.1 addresses pressure and tightness testing: hydrostatic and pneumatic tests, test pressure relative to design, temperature limits for brittle fracture, hold times, gauge requirements and safety exclusion zones. The record needs the test pressure and its basis, the medium, the metal temperature, the duration, the gauges used and their calibration, and the witnessing inspector.

Article 5.2 addresses NDE in lieu of pressure testing, for cases where a test is impractical or harmful: a vessel that cannot be filled, a system that cannot be isolated, or a lining that water would damage. It sets conditions under which volumetric and surface examination of the repair welds, with defined coverage and acceptance criteria, may be accepted instead. API 510 and API 570 permit the substitution when the inspector and, for API 510, the engineer approve. The record must show the decision was made deliberately, who made it, and the examination that replaced the test.

A repair that passed a pressure test nobody recorded is, for audit purposes, a repair that was not tested.

For in-service welding (Article 2.10), the examination record also has to address the specific risks of welding on live equipment: burn-through controls tied to remaining wall thickness, hydrogen cracking controls tied to cooling rate and flow, and the qualification of the procedure for those conditions.

How do temporary repairs get closed out?

The closing of a temporary repair is a second repair record, linked to the first.

• The permanent repair references the temporary repair it replaces, and the temporary repair record is updated with the removal date and the condition found underneath. What is found under a clamp is inspection data, and often the only measurement of how fast the defect grew while covered.
• If the permanent repair is deferred, the deferral is an engineering decision with a new review date, a reassessment of the monitoring, and the approvals the code requires.
• Turnaround scope should be generated from the temporary repair register, so that every open temporary repair appears on the work list for the outage in which it is due, and its closure is confirmed before the gate review signs the unit back to operations.

Programs that treat temporary repairs as work orders lose them when the work order closes. Programs that treat them as open findings on the equipment record keep them until the record says they are closed.

How intelliSPEC handles it

intelliSPEC keeps the finding, the repair and the component in one asset record, so a repair is a workflow against the finding that caused it rather than a document in a separate system. Findings and repairs are captured in intelliINSPECT with photos and video bound to the component at capture, PDF and drawing annotation, and a signature widget that records per-signer identity even on a shared device, so the technician, the inspector and the engineer each sign as themselves. Coating repairs that follow a metal repair carry dry film thickness verification with readings from supported DeFelsko gauges entering the record without retyping.

Because forms and workflows are configured through the form designer rather than code, a repair record can carry the PCC-2 headings as structured fields, with classification, article, limitations check, design basis, examination and test as recorded values, and a temporary repair can carry its install date, design life, monitoring plan and planned permanent repair as fields with a workflow state. The platform's workflow transitions include submit, approve, reject, hold, resume, reopen and owner sign-off, which map directly onto the life of a temporary repair: approved, held while monitored, reopened when found again, and signed off when the permanent repair closes it. Completed records pin the form configuration they were executed with, so a repair record from a prior outage renders as it was signed.

Turnaround scope generated from open repairs is managed in intelliPROJECTS, where events, activities, daily progress, delay events, gate reviews and cost entries share the same record, so a temporary repair due for replacement appears in the outage scope and its closure is visible at the gate review. Personnel records in intelliCREW carry qualifications, skills and training against each crew member, checked at assignment. Every create, update, approval and sign-off 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 can recompute for auditors; audit events are never auto-deleted. The terms used here are defined in the glossary.

PCC-2 describes how to make the repair. The record is what proves it was the right repair, done to the method, and closed.