API 570 risk-based inspection intervals for in-service piping

API 570, the Piping Inspection Code, provides a framework for deciding when fixed process piping should be inspected while it remains in service. Its risk-based approach relates the likelihood of degradation to the consequences of a leak, rupture or other credible failure, rather than applying one calendar interval to every line.

A defensible programme needs more than due dates. It requires system boundaries, verified design and inspection data, controls for identified damage mechanisms, repair records and approval by competent personnel under the applicable code edition. Australian facilities must also align that basis with local safety, dangerous goods and asset-owner requirements.

Why interval planning matters

A shorter interval is generally warranted when a credible failure has serious consequences, degradation is active, or inspection coverage is weak. A longer interval may be justified only when the piping system has lower exposure, well-understood behaviour and reliable evidence that deterioration remains detectable. Neither consequence nor condition should be assessed in isolation.

The maximum interval for an in-service thickness assessment is not the same as routine visual surveillance, process monitoring or supplementary examinations. Operators should preserve the distinction defined by the code, document every repair and change, and reassess the plan after significant alteration, upset, corrosion event or operation outside design assumptions.

Building a defensible risk basis

Begin with clear system boundaries and a complete pressure and temperature inventory. Relevant data includes piping class, design and operating conditions, service fluid, fill medium, nominal and actual wall thickness, corrosion allowance, weld history, supports, inspections and previous repairs. Missing information should be treated as uncertainty, not silently omitted.

Estimate both failure likelihood and consequence. Corrosion and erosion may progress predictably, while fatigue or stress corrosion cracking can require different inspection methods and shorter reassessment periods. Occupancy, fluid toxicity, ignition potential, escalation pathways and environmental impact help establish the consequence category.

The piping owner and authorised inspection authority must apply the current edition and its stated limits. The resulting risk-based inspection plan should remain traceable and reviewable; a spreadsheet or engineering model cannot extend acceptable risk beyond code requirements.

Using inspection evidence to set intervals

Thickness measurements provide a baseline for loss of metal, but readings must be mapped to expected damage locations and compared with the minimum required wall thickness. Corrosion allowance is not spare capacity to consume indefinitely. Suitable examinations may include visual work, ultrasonic thickness measurements and other nondestructive methods selected for the service and damage mechanism.

Inline inspection, radiography, guided wave testing and corrosion coupons can strengthen the evidence base when their coverage suits the geometry and piping system. Their value lies in verified detection capability, not in the sophistication of the technique. Process alarms, leak detection and operating trends also matter when linked to defined response and reassessment processes.

Where baseline data are absent, a provisional shorter interval or broader nondestructive examination may be more defensible than an optimistic calculation. New service, modified chemistry, higher temperatures, changed insulation or a damaged coating can alter the mechanism and rate of loss, triggering review before the next scheduled interval arrives.

Australian compliance and site realities

API 570 is a consensus code, not an Australian law. A process plant may invoke it through owner standards, design contracts, insurance or auditor requirements, while SafeWork NSW, Queensland workplace health and safety legislation and the Australian Dangerous Goods Code may impose separate duties. Transmission and distribution gas pipelines commonly follow AS/NZS 2885 rather than API 570, so system classification matters.

Environmental detail must be local. Pilbara projects face high ambient temperatures and dust; Kwinana and Geelong plants require attention to salt-laden coastal exposure; Newcastle industrial sites can combine marine air, port logistics and multiple imported process systems. These conditions can change corrosion rates and inspection accessibility, especially beneath insulation or at supports.

Customs clearance of imported skids or pressure equipment does not establish Australian design or inspection compliance. Technical documents, welders, testing personnel and competent reviewers still need to satisfy the project’s applicable requirements. For cross-checking adjacent international references, a broader technical standards library can complement—but not replace—the controlled API and Australian documents used by the facility.

Turning the code into an inspection programme

Secure the correct API 570 edition, addenda and referenced technical documents, then place them under document control. The same revision discipline illustrated in electronics rework standards applies: record the issue date, superseded copies, clarifications and site-specific interpretations so every inspector works from the same basis.

Implementation should assign responsibility for data validation, interval approval, examination, defect evaluation, repair and overdue-action management. Build in review triggers and ensure calculations remain valid when equipment, service or environmental assumptions change. Records should show what was inspected, what was found, what remains unresolved and who accepted the residual risk.

Review API 570 in the Document Bays catalogue, select the applicable issue for your facility and use the downloadable format to support a controlled reference library. With multi-currency checkout for the Australian market, teams can prepare a traceable standards package before developing their risk-based inspection schedule.