Organizing Tank UT Thickness Data for API 653 Inspections

FieldSight

Organizing Tank UT Thickness Data for API 653 Inspections

Tank UT thickness data is only as useful as your ability to say exactly where each reading was taken, how it was taken and how it compares with the last inspection. Organize readings around a location scheme that the next crew can repeat. Record the context alongside each value, and carry the same record into the calculations and the report instead of retyping it. The rest of this article explains how to set that up for shell and bottom readings.

This is a workflow guide, not a summary of code requirements. The applicable edition of API 653, the owner’s procedures and the inspector or engineer responsible for the evaluation decide what must be measured, where, and what the results mean.

Why thickness data becomes hard to use

Most teams don’t have a measurement problem. They have a record problem. Readings get collected well in the field and then lose their meaning on the way to the report:

  • Ambiguous locations. A reading listed as “Course 2, north” can’t be found again with confidence. Next time, a different technician takes a reading a few feet away, and the comparison is no longer like for like.
  • Grids that change between inspections. If the previous report numbered bottom plates or shell locations differently, someone has to reconcile two schemes before any comparison means anything.
  • Transcription. Readings move from a gauge or notebook to a spreadsheet, then to a calculation sheet, then to a report table. Every transfer is another chance for a value to land in the wrong row.
  • Missing context. A number with no date, instrument, technician or surface note is hard to defend when an owner asks how it was obtained.

Build a location scheme that survives the next inspection

Decide on the location scheme before anyone picks up a transducer, and write it down so it can be repeated.

Shell readings

  • Identify each course consistently, starting from the same end every time.
  • Tie circumferential positions to a fixed, documented reference, such as a named nozzle, the manway or a compass orientation shown on the tank diagram, rather than to “left of the stairs”.
  • Record how elevation within the course was referenced if your readings aren’t taken at a single standard height.
  • Keep nozzle and appurtenance readings identified by the nozzle tag used on the drawing, so they don’t get mixed into general shell data.

Bottom readings

  • Use a plate numbering scheme that matches the bottom layout drawing, and keep it the same from one inspection to the next where the plates haven’t changed.
  • Locate indications by X/Y from a stated reference corner or point on each plate, and record which reference you used.
  • Keep annular ring or critical-zone readings identifiable separately where your scope treats them separately.
  • Note whether a value came from a spot reading or from follow-up of a scanning indication, so the reviewer knows what the number represents.

If the previous inspection used a different scheme, don’t silently renumber. Record how the old locations map to the new ones, or note that they can’t be matched, so whoever calculates corrosion rates knows which comparisons are valid.

What to record with every reading

The reading itself is one field. The context is what makes it usable later. For each reading or group of readings, capture:

  • The location ID from your scheme, plus the component (shell course, plate, nozzle, roof).
  • The measured value and the units it was recorded in.
  • The date and the technician who took it.
  • The instrument used and its calibration reference, per your company procedure.
  • Surface condition notes that affect interpretation, such as coating, pitting or areas that couldn’t be cleaned.
  • Whether the location was inaccessible, and why, so a missing reading is explained rather than just blank.

Field checklist before you leave the tank

  1. Every planned location has a reading or a recorded reason it doesn’t.
  2. Each low or unexpected reading has been rechecked and has a note and a photo where one helps.
  3. Bottom indications are located on the plate with their X/Y reference recorded.
  4. Location IDs match the tank diagram the report will use.
  5. Readings that need follow-up are flagged as findings, not buried in a table.
  6. Construction and service inputs that the calculations depend on, such as nominal thickness, material, product and fill height, are recorded with their source, or marked as unknown.

Catching a gap here costs a few minutes. Catching it at the desk can mean a phone call to site or a return trip.

Comparing with the previous inspection

Corrosion rates and remaining-life results depend on comparing the same locations over time. Before using earlier data:

  • Confirm that the earlier readings came from the correct report and the same locations.
  • Record the dates of both data sets, since the comparison depends on the time between them.
  • Flag any location where the earlier reading is suspect or the location can’t be matched. The inspector or engineer decides how to treat it, and that decision should be written down.

How rates are calculated and which readings govern depend on the applicable standard and the owner’s requirements. The data organization above doesn’t change that. It makes the inputs to that judgment easy to check. The API 653 inspector qualification itself is described on the API 653 certification page.

How FieldSight supports thickness data

FieldSight keeps the API 653 inspection in one record: field data, shell and bottom thickness readings, calculations, Annex B settlement evaluation, interactive tank diagrams, findings, photographs and the final report. Readings are entered once in that record. The calculations, diagrams and report draw on them from there, so you don’t keep a separate spreadsheet copy.

  • Readings tied to the drawing: interactive tank diagrams are built inside the inspection, so locations on the drawing and locations in the data come from the same job.
  • Inputs stay visible: calculation inputs remain attached to the inspection. When required inputs are missing, the safe-fill versus specific-gravity chart shows a message saying it can’t produce a result instead of drawing one.
  • Findings and photos with the data: findings are recorded with separate issue, recommendation and priority fields, and photos stay linked to the inspection items they document.
  • One source for deliverables: branded PDF and Word reports, CAD/DXF output and shared client reports come from the same finalized record.

FieldSight doesn’t replace the inspector’s evaluation or certify engineering correctness. It keeps the readings, their locations and the results in one place where they can be reviewed. If you’re comparing tools, see what API 653 teams should evaluate in tank inspection software.

Check your current thickness records

Open the last report your team issued and pick five readings at random. Can you find each one on the drawing, name who took it and match it to the previous inspection without opening another file? If not, see how FieldSight keeps thickness data, calculations and the report in one inspection record.