An API 510 pressure vessel inspection reporting workflow should make the condition, inspection history, calculations, and disposition of an in-service pressure vessel traceable from inspection scope through final review. The record should connect vessel identity, components, CML/TML locations, thickness measurements, damage mechanisms, NDE results, calculations, drawings, photographs, repair or alteration records, and inspector/engineering review.
Software can provide assisted data entry, automated calculations and report assembly, but an authorized inspector and responsible engineer or owner-user personnel remain responsible for interpreting the evidence and making decisions under the applicable code and inspection program.
1. Establish the vessel record and inspection scope
Start with the vessel number, service, manufacturer or design information available to the inspection team, component list, prior inspection reference, current inspection date and scope. Identify the vessel components and examination areas applicable to the scope, such as shells, heads, nozzles, manways, welds, attachments, supports, internals, and areas associated with expected damage mechanisms. The scope should distinguish visual inspection, thickness measurement, NDE, relief-device information, repairs and any special study rather than treating the vessel as one undifferentiated record.
Drawings and a consistent location convention make the record repeatable. Link CML/TML identifiers to a vessel drawing, shell course, orientation, weld, nozzle or other physical reference. SketchMapp inspection drawing and CML mapping can support the location view when the report needs a clear relationship between the point list and the equipment drawing.
2. Collect CML/TML readings and inspection evidence
Record nominal or reference thickness, current thickness, measurement date, instrument or technique, units, calibration information and the exact CML/TML identifier. Repeat measurements at the same locations where comparison is valid. Add photos of the vessel, access, coating, corrosion, insulation removal, welds and local findings with labels that identify the component and location. Technique sheets, NDE reports, inspector qualifications or certifications and field notes should remain connected to the inspection package.
Review the data before calculating trends. Look for duplicate point names, missing readings, changed locations, mixed units, implausible jumps and measurements that do not represent the same surface or datum as the previous inspection. A clean record makes later engineering review faster because the reviewer can trace a result back to the field evidence.
3. Trend thickness and perform supported calculations
Use comparable inspection data to determine metal loss, corrosion rate, remaining corrosion allowance, remaining service life, and inspection interval where applicable. A simple corrosion-rate expression may be represented as thickness loss divided by elapsed time, while remaining service life relates current actual thickness to the required thickness using the selected corrosion rate. The applicable API 510 requirements, owner-user procedure, data quality, damage mechanism, and engineering basis control the actual calculation and interval decision.
CR = thickness loss / elapsed time
RL = (current thickness − required thickness) / corrosion rate
The selected method, required thickness, data screening, time basis, rounding and uncertainty must follow the applicable procedure and engineering basis.
Where applicable, retain the inputs and basis used for minimum required thickness, vessel-part MAWP, overall vessel MAWP, remaining corrosion allowance, rerating, or other supported code calculations. Record material, geometry, temperature, pressure, weld or joint assumptions, required thickness and the governing code or procedure. Calculated MAWP, required thickness, corrosion rate, remaining service life, and inspection interval are technical inputs to the inspection decision. Final acceptance, continued-service decisions, rerating, repair, or alteration remain subject to the applicable API 510 requirements, owner-user program, and qualified inspector/engineering review.
4. Compile drawings, photos and the final report
Bring together the cover, scope, vessel description, inspection personnel, CML/TML tables, thickness trends, calculation pages, drawings, photos, technique sheets, certifications, NDE reports, findings, damage-mechanism observations, recommendations where applicable, repair/alteration records, inspection intervals, and required review/signature information. Check that identifiers and dates agree across the report, attachments and calculation pages.
The API/NDE reporting workflow keeps vessel inspection data, calculations, drawings, photos, checklists and final report compilation in one project record. It supports the inspection and reporting workflow; it does not replace the API 510 Authorized Pressure Vessel Inspector, owner-user inspection organization, or engineering review required by the applicable program.
Questions inspectors ask
Should every vessel component use the same CML layout?
No. CML placement should reflect component geometry, expected damage mechanisms, access, prior history, and the inspection plan. The important controls are stable identifiers, reproducible physical locations, and enough coverage to support meaningful trending and condition assessment.
Can the calculated MAWP be copied directly into the report conclusion?
No. Review the code basis, inputs, assumptions, measurement quality and applicable engineering procedure before using the calculation in a conclusion.
What makes an API 510 report traceable?
Consistent component and CML/TML identifiers, linked field evidence, stated calculation inputs, clear drawings, dated inspection records and documented review make the decision path readable.