API 570 Piping Inspection Code: Repair, Alteration, & Rerating of In-Service Piping Systems

API 570 governs piping that is already in service, which is a different problem from piping being built. The material is degrading, the data is incomplete, and the question is rarely whether a line is perfect but whether it can keep running and for how long. This week works through the inspection intervals, the thickness measurement and the corrosion rate calculations that produce a remaining life, then through what the code permits when the answer is uncomfortable: a repair, an alteration, or a rerate. Calculations are done by hand on real figures, because a number produced by a spreadsheet nobody present can check is not evidence.

It runs 7 times over the published calendar, in 6 cities and live online. Every date is the same programme with the same content and the same certificate.

• Apply the inspection intervals and classify piping by service.
• Calculate corrosion rate, minimum thickness and remaining life from real readings.
• Choose inspection methods that will find the damage mechanism actually present.
• Separate repair from alteration from rerating, and follow the route each requires.
• Assemble records that support the decision when it is questioned years later.

Piping and plant inspectors, integrity and reliability engineers, maintenance engineers responsible for static equipment, and QA staff preparing for the certification examination.

Short input, then work. Across 5 days of roughly 6 teaching hours each, the balance sits deliberately with the second: a programme where the trainer talks for six hours produces notes rather than capability.

• Your own material

  Exercises run on situations delegates bring, not on a case study written for a different organisation in a different decade.

• A capped cohort

  Small enough that everybody is asked something. Executive programmes are capped tighter still.

• Practice under scrutiny

  The difficult conversation, the challenged assumption, the decision defended out loud. Judgement is not built by watching.

• Something to take back

  Each day ends with a thing you can use on Monday rather than a slide deck you will not reopen.

• Worked remaining life calculations on your own thickness data.
• An inspection plan for one circuit, with intervals and methods justified.
• A rerating file structure that satisfies the code.

A GATI certificate recording what you attended, issued after the programme has run and attendance has been taken. Attending at least 80 per cent of the days earns a certificate of completion; attending less earns a certificate of attendance stating exactly what was attended.

Every certificate carries a code that anybody can check against GATI's own record, which is what makes it worth holding. It records participation. This site will not imply one it does not have.