Skip to content
570 InspectAheadHome Pricing

API 570 / Calculations guide

API 570 calculations: reasoning and practice

API 570 calculation questions reward a controlled method more than a memorised result. You need to identify what is being asked, select the applicable relationship, keep every quantity on a consistent basis and check whether the answer makes physical sense. This guide covers that workflow without publishing numerical examples or replacing the current code documents.

On this page
  1. Set up the problem
  2. Work through the method
  3. Check the result

Set up the problem

Begin by naming the decision behind the calculation. The task may concern corrosion rate, remaining life, minimum required thickness, maximum allowable working pressure or an inspection interval. Those outputs are related, but they are not interchangeable. Write the target first so that a familiar-looking value does not pull you toward the wrong method.

  • State the requested output before choosing a method.
  • List each input with its unit and meaning.
  • Identify the applicable reference and edition context.
  • Keep assumptions visible until the final check.

Units and assumptions#

Create one unit system before you calculate. Convert dimensions, pressure, time and rate inputs deliberately, then carry the units through each line. Do not round intermediate values just to make the arithmetic tidy. A clean setup should also show whether loss is treated as a positive rate and whether measurements are being compared on the same thickness basis.

Work through the method

For corrosion rate, the reasoning connects a change in measured thickness with elapsed service time. The important checks are that the measurements are comparable, the time direction is correct and the resulting rate describes loss rather than growth. If readings come from different locations or inspection methods, pause before treating them as one trend.

Remaining life uses the usable thickness margin together with the selected corrosion rate. Minimum required thickness and pressure calculations depend on the applicable design basis, while inspection intervals are constrained by the governing inspection rules and the condition being evaluated. Keep these stages separate so that one result is not reused before its assumptions have been checked.

Check the result

  1. Check dimensions, sign and scale

    A result is not finished when the calculator stops. Check its dimensions, sign and scale. Ask whether a higher corrosion rate should shorten remaining life, whether the pressure or thickness relationship moves in the expected direction and whether a conversion was applied twice. Rework the problem from the stated inputs when an answer choice looks plausible but the units do not.

  2. Keep practice and field decisions apart

    Keep educational practice separate from integrity decisions on operating equipment. InspectAhead exercises are original preparation material, not certified engineering software, an inspection plan or approval for continued service. Real evaluations require the current governing documents, verified plant data, employer procedures and qualified professional judgement appropriate to the installation.

Frequently asked questions

Which calculation families should I practise for API 570?#

Build fluency with corrosion rate, remaining life, thickness, pressure-related checks and inspection-interval reasoning as they appear in the current Body of Knowledge and effectivity documents.

How can I reduce unit errors?#

Write the unit beside every input, convert to one consistent system before substitution and perform a dimensional check before accepting the result.

Are InspectAhead calculations suitable for real equipment decisions?#

No. They are educational exercises. Decisions about operating equipment require verified site data, current governing documents, employer controls and qualified professional judgement.

Should I memorise every formula?#

Memorise the purpose and structure of common methods, but practise locating applicable open-book rules and reading their limits in the legally obtained code documents.

↑ Back to the top