API 580 and 581 Training: Risk-Based Inspection and Base Resource Document

Inspecting everything on the same interval spends the most effort where the least is at stake. Risk based inspection redistributes it, and the redistribution is the point: the same budget, aimed at the equipment where failure would actually hurt. API 580 sets out what a defensible programme contains and API 581 provides the quantitative method underneath. This week covers both, and spends as much time on the parts that make programmes fail as on the calculation: damage mechanisms identified wrongly, data nobody maintains, and a risk register never revisited after the consultant left.

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.

• Identify credible damage mechanisms for a given service and material.
• Assess probability and consequence of failure, qualitatively and quantitatively.
• Place equipment on a risk matrix and defend where it sits.
• Convert risk into inspection scope, method and interval.
• Keep the programme alive through evergreening rather than letting it date.

Inspection and integrity engineers, reliability engineers, maintenance and turnaround planners, and managers accountable for inspection spend.

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.

• A risk assessment for one equipment group, start to finish.
• An inspection plan derived from that risk rather than from the calendar.
• An evergreening routine with named owners and triggers.

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.