Oil & Gas Inspection Software: Managing API 510, API 570, API 653 and Pipeline Inspection Records

Oil and gas inspection is one of the most records-intensive disciplines in the TIC sector. Every pressure vessel, every piping circuit, every above-ground storage tank carries its own inspection history, its own corrosion monitoring programme, and its own regulatory clock — a set of inspection due dates that, if missed, create both a safety risk and a legal liability. The API inspection standards that govern this work — API 510, API 570, API 653, and the risk-based inspection methodology of API 580 and 581 — are detailed, prescriptive, and unforgiving on documentation. An inspection programme that produces good field results but poor records is not a compliant inspection programme.

For inspection companies operating in upstream production, midstream transmission, downstream refining, and petrochemical manufacturing, the challenge is managing this at scale. A single refinery may contain thousands of pressure vessels, tens of thousands of pipe circuit segments, and hundreds of storage tanks — each with its own CML network, its own inspection history, and its own schedule of upcoming due dates. Managing that with spreadsheets and shared drives is not a documentation strategy; it is a liability waiting to be triggered.

This article covers what oil and gas inspection actually involves, the standards that govern it, the qualification requirements that inspectors must meet, the records that must be produced and retained, and how purpose-built oil and gas inspection software changes the management equation.

What Oil & Gas Inspection Covers

Oil and gas inspection — in the sense covered here — refers specifically to the in-service inspection of fixed equipment: the static, pressure-containing plant items that form the process boundary of oil and gas operations. This is distinct from construction inspection (which occurs during fabrication) and operational integrity monitoring (which is a continuous process), though both feed into the fixed equipment inspection programme.

Pressure vessels are closed containers designed to hold fluids — gas, liquid, or multi-phase — at pressures above atmospheric. In oil and gas operations, pressure vessels include separators (separating oil, gas, and water from production streams), knock-out drums, flash drums, surge drums, reactors, and heat exchangers. Every pressure vessel above defined thresholds must be registered and inspected at defined intervals under the API 510 standard and, in jurisdictions with statutory registration requirements, under applicable workplace health and safety legislation.

Piping systems are the networks that move process fluids between vessels, equipment, and custody transfer points. In a refinery or petrochemical plant, piping circuits run to hundreds of kilometres in total length. API 570 governs the in-service inspection of process piping — not utility piping such as water, air, or steam below defined pressure thresholds, but the process streams carrying hydrocarbons, chemicals, acids, and other materials whose failure would have safety or environmental consequences. API 570 inspection focuses on corrosion-susceptible locations: injection points, deadlegs, elbows, small-bore connections, and areas of known turbulence or flow-accelerated corrosion.

Above-ground storage tanks (ASTs) hold the inventory of crude oil, refined products, chemical feedstocks, and other liquids that oil and gas operations require at every stage of the value chain. API 653 governs the inspection, repair, alteration, and reconstruction of tanks originally built to API 650 (welded tanks for oil storage) or similar standards. Tank inspection under API 653 is particularly demanding — the floor and lower shell courses are the primary corrosion concern, and floor inspection requires the tank to be taken out of service, emptied, cleaned, and entered, with comprehensive thickness measurement across the floor plate area.

Rotating equipment — pumps, compressors, turbines — also falls within the scope of oil and gas inspection and mechanical integrity programmes, though the inspection methodology differs significantly from fixed equipment. Rotating equipment inspection is governed more by OEM recommendations, vibration analysis, and predictive maintenance programmes than by API fixed-schedule inspection standards. For the purposes of this article, the focus remains on fixed equipment.

Structural and civil inspection — foundations, pipe racks, supports, and pressure relief valve systems — rounds out the scope of a comprehensive mechanical integrity inspection programme. Pressure safety valves (PSVs) and pressure relief valves (PRVs), in particular, require periodic removal, testing, and recertification, with records maintained for regulatory and insurance purposes.

API Inspection Standards

The American Petroleum Institute's inspection standards are the most widely adopted framework for in-service inspection of fixed equipment in the oil and gas industry globally — including in Australia, the Middle East, Southeast Asia, and many other regions where API standards are adopted by reference in engineering specifications and regulatory frameworks.

API 510 — Pressure Vessel Inspection Code. API 510 is the foundational standard for in-service inspection of pressure vessels in the petroleum and chemical process industries. It defines inspection intervals, inspection methods, minimum documentation requirements, acceptance criteria for thickness readings, and the qualifications required of personnel who conduct and authorise inspections. API 510 distinguishes between external inspection (which can be conducted with the vessel in service), internal inspection (which requires the vessel to be taken out of service, depressurised, and entered), and on-stream inspection (external inspection supplemented by non-intrusive techniques such as UT scanning, which can defer internal inspection under defined conditions).

The fixed-schedule inspection intervals under API 510 are maximums, not targets. For a vessel with an established corrosion rate, the actual interval should be set at no more than half the calculated remaining life — which may be considerably shorter than the maximum. API 510 explicitly states that the inspection interval for a vessel in deteriorating condition must be shortened accordingly.

API 570 — Piping Inspection Code. API 570 applies to metallic piping systems used in petroleum refinery, chemical, pharmaceutical, and related process industries. It classifies piping circuits into risk-based classes — Class 1 (highest risk: flammable, toxic, or lethal service), Class 2 (high risk), and Class 3 (lower risk) — with inspection intervals that decrease as the risk class increases. Class 1 piping must receive thickness measurement every five years; Class 3 piping may be extended to ten years under defined conditions.

API 570 mandates specific attention to injection points — locations where a chemical is injected into a process stream, often creating an accelerated corrosion zone — and deadlegs, which are sections of piping with no or minimal flow, susceptible to settling, condensation, and localised corrosion. These high-consequence locations require more frequent inspection and closer CML spacing than the general piping circuit.

API 653 — Tank Inspection, Repair, Alteration, and Reconstruction. API 653 covers the inspection of above-ground storage tanks that were originally designed and built to API 650 or similar standards. It defines inspection types — external inspection (with the tank in service), internal inspection (with the tank out of service), and ultrasonic thickness measurement — and the intervals for each. The most demanding inspection requirement is the internal inspection interval, which depends on the corrosion rate of the floor — calculated from successive thickness measurement campaigns — and is typically in the range of five to twenty years depending on conditions.

API 653 inspection requires measurement of the floor plate thickness across a defined grid, measurement of shell course thickness at each strake, assessment of the annular plate, evaluation of the nozzles and connections, and inspection of the roof structure. The records generated are substantial and must be retained and compared against previous inspection campaigns to establish thickness trends and remaining life.

API 1104 — Welding of Pipelines and Related Facilities. While not an in-service inspection standard per se, API 1104 governs the qualification of welding procedures, welders, and inspection of welds in pipeline construction and maintenance. Pipeline inspection companies operating under API 1104 must maintain welding procedure qualifications, welder qualification records, and weld inspection results traceable to individual joints — the same traceability requirements that apply to pressure vessel and structural welding under ASME codes.

ASME inspection codes. In pressure equipment regulated under jurisdictional requirements — Australian state and territory WHS regulations, Canadian provincial boiler and pressure vessel legislation, or US state regulations — the ASME Boiler and Pressure Vessel Code (BPVC) provides the construction standard that establishes the design basis against which in-service condition is assessed. ASME Section VIII (Pressure Vessels), ASME B31.3 (Process Piping), and ASME B31.4 and B31.8 (liquid and gas pipeline transportation) are the most commonly referenced codes. API in-service inspection standards are designed to be used in conjunction with ASME construction codes — not as replacements for them.

API 580 and API 581 — Risk-Based Inspection. API 580 provides the framework for establishing an RBI programme: the principles, intent, and methodology. API 581, the companion document, provides the quantitative methodology — a structured approach to calculating probability of failure (PoF) and consequence of failure (CoF) for each piece of equipment, and combining them into a risk ranking that drives inspection planning. RBI under API 580/581 allows inspection intervals to be extended beyond the API 510/570/653 fixed-schedule maximums for low-risk equipment, and shortened for high-risk equipment, based on the actual risk profile of each asset.

API 579 — Fitness for Service. API 579 (combined with ASME FFS-1) provides the methodology for assessing whether equipment containing a defect — corrosion pitting, cracking, mechanical damage, or material degradation — can continue to operate safely, and under what conditions. An FFS assessment is required whenever an inspection finding exceeds the standard acceptance criteria (i.e., the measured remaining thickness is below the minimum required thickness) but the operator believes the equipment can remain in service. The FFS assessment must be documented and retained as part of the inspection record.

Inspector Qualification and Certification

API inspection standards specify who is authorised to conduct and sign off inspections. This is not a general competency requirement — it is a certification requirement, with specific examinations, eligibility criteria, and renewal obligations.

API 510 Certified Inspector. The API 510 certification qualifies an individual to inspect pressure vessels in accordance with API 510. The examination tests knowledge of the API 510 standard, the ASME BPVC sections relevant to pressure vessels, API 579 fitness-for-service methodology, and materials and corrosion fundamentals. Eligibility requires a combination of engineering or technician education and documented inspection experience. The Authorized Inspector (AI) designation under API 510 additionally requires that the inspector be employed by or working under the approval of an Authorized Inspection Agency — an organisation accredited to provide inspection services under API or an equivalent national programme.

API 570 Certified Inspector. The API 570 certification qualifies an individual to inspect piping systems under API 570. The examination covers the API 570 standard, ASME B31.3, applicable sections of the ASME BPVC (particularly Section IX for welding), corrosion fundamentals, and NDE methods applicable to piping inspection. API 570 inspectors must also understand the specific vulnerabilities of piping systems — injection points, deadlegs, erosion zones — that are not typical concerns in pressure vessel inspection.

API 653 Certified Inspector. The API 653 certification qualifies an individual to inspect above-ground storage tanks. The examination covers API 653, API 650 (the construction standard), API 651 (cathodic protection for above-ground storage tanks), API 652 (lining of above-ground storage tank floors), and relevant sections of ASME standards for welding and NDE. API 653 inspection requires specific competence in floor plate inspection methodology — including the use of MFL (magnetic flux leakage) scanning equipment and the interpretation of floor plate thickness data across large surface areas.

NDE qualification requirements. Most API inspection work involves direct NDE — particularly UT thickness measurement, which is the primary tool for corrosion monitoring at CMLs. Inspectors who personally perform NDE are expected to hold NDE qualifications appropriate to the method and level of interpretation required. UT Level II under ISO 9712, ASNT SNT-TC-1A, or the equivalent national scheme is the standard expectation for inspectors performing UT thickness measurements and interpreting results. For advanced NDE methods — PAUT (Phased Array UT), TOFD, AUT — Level II or III under the applicable method is required.

Certification expiry and renewal. API inspector certifications are valid for three years. Renewal requires accumulating professional development hours — a defined number of hours of inspection work in the relevant discipline, plus participation in API seminars, technical committee work, or approved training courses. Failure to renew on time requires re-examination before the certification can be reinstated. For inspection companies managing multiple API-certified inspectors across different certification types and expiry dates, tracking certification currency is a material compliance obligation — not an administrative afterthought. An inspection conducted by an inspector whose certification has lapsed is not a valid API inspection, regardless of the technical quality of the work.

Inspector certification expiry alerts — automated notifications to the inspector and their manager before an API certification lapses — are a core requirement for any oil and gas inspection software handling API-qualified personnel. Without them, expiry is discovered reactively, usually when preparing an inspection report that requires a valid certification number.

Records Required for API Inspection

The record requirements for API inspection are defined in each standard, and they are substantial. The key principle across all three standards is that inspection records must enable any subsequent inspector — not just the one who conducted the original inspection — to understand the full history of the equipment and make informed decisions about its current condition and future inspection schedule.

Vessel or equipment record. The baseline record for each piece of equipment must capture its design data: the original design code, design pressure and temperature, MAWP (Maximum Allowable Working Pressure), materials of construction (shell, heads, nozzles), corrosion allowance, weld joint efficiency, and the original fabrication NDE results. For pressure vessels, this is typically the information on the ASME nameplate and the Manufacturer's Data Report (MDR or U-1 form). For storage tanks, the equivalent baseline is the API 650 data sheet and as-built drawings. This design data is the reference against which every subsequent thickness measurement is compared — without it, remaining life cannot be calculated.

Corrosion Monitoring Locations (CMLs). CMLs are defined measurement points on a vessel or piping circuit where thickness is measured at each inspection cycle. The selection of CMLs is one of the most technically important decisions in setting up an inspection programme — they must be located at the areas most susceptible to corrosion or erosion based on the process service, flow dynamics, and operating conditions. For a pressure vessel, CMLs might be at the bottom head (corrosion sump), at nozzle connections (flow disturbance zones), and along shell courses at defined intervals. For a piping circuit, CMLs are placed at injection points, elbows, reducers, and deadlegs. Each CML must have a unique identifier, a defined measurement method and instrument type, and a measurement record covering every inspection cycle.

Thickness measurement records. For each inspection cycle, the measured wall thickness at every CML must be recorded with the date of measurement, the measurement method (contact UT, pulse-echo, A-scan), the instrument type and serial number, and the operator's name and qualification. The measured thickness is compared against the previous measurement to calculate the corrosion rate (typically expressed in mm/year or mpy — mils per year). The corrosion rate is used to calculate remaining life (the time until the measured thickness reaches the minimum required thickness) and to set the next inspection interval.

Inspection histories and finding records. Each inspection must be documented in an inspection report that records what was inspected, by what method, by whom, on what date, and what was found. Findings — corrosion, pitting, cracking, mechanical damage, coating failure — must be described with enough detail to allow comparison at the next inspection: location on the vessel or piping circuit, dimensions of the affected area, measured severity. The report must be signed by the Authorized Inspector responsible for the inspection and retained with the equipment record.

Fitness-for-service assessments. Where an inspection finding exceeds the standard acceptance criteria — for example, a measured thickness below the calculated minimum required thickness — an FFS assessment is required before the equipment can remain in service. The FFS assessment, conducted in accordance with API 579, must be documented with the input data (defect dimensions, material properties, operating conditions), the methodology applied, and the conclusions: fit for continued service, fit subject to operating restrictions, or unfit for service. The FFS assessment and its conclusions must be retained as part of the equipment record.

Repair records. Where corrosion, cracking, or mechanical damage has been repaired — by weld overlay, insert plate, grinding, or other means — the repair must be documented with the repair procedure used, the welding procedure specification (if welding was involved), the qualified welder's identity, and the post-repair NDE results confirming acceptance. Repairs must be authorised by the Authorized Inspector, and the repair record must be permanently linked to the equipment record so that subsequent inspectors are aware of the repair location, method, and history.

Mechanical integrity records. For facilities subject to OSHA PSM (Process Safety Management) regulations in the US, or equivalent process safety regulations in other jurisdictions, mechanical integrity records are a regulatory requirement. The mechanical integrity programme encompasses the inspection, testing, and preventive maintenance records for all process equipment. API inspection records form the core of the mechanical integrity record set for fixed equipment. Gaps in mechanical integrity records are a primary finding in process safety audits and incident investigations.

HSSE records. Health, Safety, Security, and Environment records associated with inspections — confined space entry permits, hot work permits, gas testing results, scaffolding inspection records, and personal protective equipment requirements — must be retained alongside the technical inspection records. For entry into pressure vessels and storage tanks, confined space entry management records are a statutory requirement in most jurisdictions and must demonstrate that the entry was conducted with appropriate risk controls in place.

Risk-Based Inspection (RBI) and Corrosion Management

Risk-based inspection, as defined in API 580 and quantified in API 581, is the most significant methodological development in fixed equipment inspection management in the past three decades. Its adoption has transformed how inspection intervals are set, how resources are allocated, and how inspection data is used to inform engineering decisions.

What RBI is — and what it is not. RBI is a structured methodology for prioritising inspection based on risk. Risk, in the API 580/581 sense, is the product of probability of failure (PoF) and consequence of failure (CoF). High-risk equipment — high probability of failure combined with high consequence if it does fail — receives more frequent, more intrusive inspection. Low-risk equipment can be inspected less frequently, freeing resources for where they matter most.

RBI is not an excuse to reduce inspection. It is a tool for optimising inspection. For equipment that is genuinely low-risk — a water-service pressure vessel in a low-hazard location, operating well within its design envelope — extending the inspection interval from the fixed-schedule maximum to a longer RBI-based interval is technically defensible and cost-effective. For a vessel in hydrogen sulphide service with a history of stress corrosion cracking, RBI typically demands more frequent inspection than the fixed schedule would require — because the risk profile demands it.

Probability of failure. PoF in API 581 is calculated from the degradation mechanisms active in the equipment: general corrosion, localised corrosion, stress corrosion cracking, hydrogen embrittlement, fatigue, creep, and others. Each mechanism has a defined calculation method based on the material, the process environment, the operating conditions, and the inspection history. The inspection history directly affects the PoF — effective past inspection reduces uncertainty about the current condition, which reduces the calculated probability of failure. Poor inspection quality or infrequent inspection increases the PoF, because uncertainty about condition is itself a contributor to risk.

Consequence of failure. CoF in API 581 is calculated from the consequence if the equipment does fail — the inventory that could be released, the physical properties of the fluid (flammability, toxicity, reactivity), the likely release scenario (leak, rupture), and the population exposed. A small vessel containing a non-flammable, non-toxic fluid in a remote location has low consequence of failure. A large separator vessel containing sour gas (H2S) adjacent to a process control room has extremely high consequence of failure. The CoF drives the overall risk classification and directly influences the inspection interval and the level of inspection required.

Inspection planning from RBI. An RBI programme produces an inspection plan for each asset — defining what should be inspected, by what method, at what interval, and focusing on which areas of the equipment (based on the dominant degradation mechanism and the location of prior findings). For a vessel susceptible to stress corrosion cracking in the weld heat-affected zones, the RBI-derived inspection plan will specify UT or wet fluorescent magnetic particle testing (WFMT) in those specific areas, at the interval calculated from the risk analysis. This is qualitatively different from a fixed-schedule inspection that examines the vessel generically — it is an inspection targeted at where failure is most likely to initiate.

Corrosion loop management. A corrosion loop is a grouping of piping or equipment that experiences similar process conditions, materials of construction, and degradation mechanisms — and therefore similar corrosion rates and failure modes. Corrosion loop management is the discipline of understanding which equipment is in which loop, what the expected and actual corrosion rates are within each loop, and how findings from one piece of equipment in a loop should influence the inspection scope for others. A thickness measurement campaign that finds unexpectedly high corrosion in one vessel should trigger increased inspection of adjacent equipment in the same corrosion loop, because the same process mechanism is acting on all of them.

RBI software requirements. An RBI programme generates considerable data — consequence calculations, probability assessments, inspection history inputs, risk rankings, and inspection plan outputs — for every piece of equipment in the programme. Managing this in spreadsheets is technically feasible for small fleets but becomes unmanageable at refinery scale. RBI software that integrates with the inspection record system — so that new inspection data automatically updates the risk calculation — is the standard expectation for large oil and gas operations. The key requirement is that the RBI calculation draws on actual, current inspection data rather than assumptions — which means the underlying inspection records must be complete, structured, and accessible to the calculation engine.

Oil & Gas Inspection Sectors and Scope

Oil and gas inspection spans the full value chain, from wellhead to end user. Each sector has its own mix of asset types, applicable standards, and inspection challenges.

Upstream — exploration and production. Upstream operations cover the extraction of oil and gas from the reservoir to the point of first separation. Fixed equipment inspection in upstream includes wellheads and Christmas trees (the valve assemblies at the top of production wells), manifolds (the gathering systems that combine production from multiple wells), separators (the primary separation vessels that split oil, gas, and water from the production stream), and flare systems (pressure relief and emergency vent systems). Upstream inspection is characterised by the diversity of asset types, the remote location of many facilities, and the variability of production stream composition — which directly affects the corrosion regime. Sour production (containing H2S) adds the risk of hydrogen embrittlement and stress corrosion cracking to the standard corrosion concerns.

Midstream — transportation and storage. Midstream covers the pipelines, compressor stations, and storage facilities that move hydrocarbons from production to processing or to market. Pipeline inspection at the midstream level involves both in-line inspection (using pipeline inspection gauges, or PIGs, that travel through the pipeline measuring wall thickness and detecting corrosion, cracking, and mechanical damage) and above-ground inspection of the exposed sections, valves, supports, and associated above-ground facilities. Compressor stations — which contain high-pressure gas compressors, separators, and associated process equipment — are regulated as pressure equipment and require API 510 inspection programmes. Above-ground storage tanks at terminal and pipeline facilities fall under API 653.

Downstream — refining and petrochemical. Downstream operations represent the highest concentration of fixed equipment requiring API inspection. A large refinery may contain 2,000 to 5,000 pressure vessels, each requiring an API 510 inspection programme. The piping network at a refinery — hundreds of distinct circuits, each classified under API 570 — can run to tens of thousands of CMLs. Storage tank farms serving a refinery or petrochemical plant may contain dozens to hundreds of tanks covered by API 653. The inspection workload in downstream is enormous, and the consequences of failure — fire, explosion, toxic release — are severe. The downstream sector drives most of the demand for structured oil and gas inspection software, because the data volumes and the compliance stakes both exceed what manual systems can manage.

Petrochemical manufacturing. Petrochemical plants process refinery products into base chemicals — ethylene, propylene, benzene, methanol, and others — which are then converted into plastics, fibres, resins, and other materials. The inspection requirements in petrochemical manufacturing overlap significantly with downstream oil and gas but add the complexity of highly reactive process streams, specialised materials (including austenitic stainless steels, high-alloy materials, and lined equipment), and the presence of aggressive chemical environments that create degradation mechanisms not commonly found in crude oil processing — high-temperature hydrogen attack (HTHA), chloride stress corrosion cracking, and ammonium bisulphide corrosion among them.

Offshore and subsea. Offshore oil and gas production — fixed platforms, floating production systems (FPSO, FLNG), and subsea infrastructure — presents additional inspection challenges driven by the marine environment, the limited accessibility of equipment, and the consequence severity of failures in a remote, high-consequence setting. Topside fixed equipment on offshore platforms is subject to API 510/570/653 inspection programmes, with the additional requirement of managing corrosion under insulation (CUI) — a pervasive and difficult-to-detect degradation mechanism in the humid, salt-laden offshore environment. Subsea inspection — pipelines, risers, subsea manifolds, and wellheads — uses specialist inspection vessels and ROV (remotely operated vehicle) systems, with inspection data managed as part of the broader pipeline integrity management programme. Offshore inspection record management must integrate with the operator's safety case — the overarching safety management document that regulators require for offshore operations.

Managing Oil & Gas Inspection Records with Software

The scale and complexity of oil and gas inspection records creates a genuine data management problem that purpose-built oil and gas inspection software exists to solve. The problem is not just volume — though volume is significant. It is the combination of volume, interconnection, and regulatory consequence that makes manual management inadequate.

Job management and inspection scheduling. In an operational inspection programme covering hundreds or thousands of assets, the most fundamental requirement is knowing what is due when. Each asset has multiple inspection types on different schedules — external inspection, internal inspection, CML thickness surveys — each with its own due date and its own consequence if missed. Purpose-built inspection software manages this as a live schedule: each asset's next due dates are calculated from the previous inspection date and the applicable interval, and upcoming inspections are presented as a work queue. Jobs are assigned to qualified inspectors (those with the relevant API certification and current NDE qualifications), travel logistics and site access requirements are recorded, and the progress of each inspection from assignment through fieldwork to report issuance is tracked in the system.

CML tracking and thickness trending. For each CML on each asset, the inspection software should hold the CML definition (location, measurement method, reference thickness from the previous campaign), the measurement history across all inspection cycles, and the calculated corrosion rate and remaining life. When a new measurement is entered, the system should automatically calculate whether the new result is within the expected range, flag any accelerated corrosion that would require a shortened inspection interval, and update the next due date accordingly. Trend charts — showing the thickness at each CML across successive inspection dates — turn a set of numbers into an interpretable picture of how the asset is ageing. An inspector reviewing a trend chart showing steady wall loss at a defined rate makes different decisions than one looking at a table of numbers without context.

Report generation and API-standard templates. Inspection report generation from a purpose-built system should produce structured reports that meet API requirements without manual document assembly. The inspector records findings in the system — CML measurements, visual findings, abnormal conditions — and the report is generated from that data using a template that includes all required elements: the asset identification, the inspection type, the date and inspector certification number, the findings, the remaining life calculation, and the next inspection due dates. Reports generated this way are consistent in format, traceable in content, and can be reviewed and approved through a digital workflow before issuance to the client. For inspection companies issuing large numbers of API inspection reports, the difference between a structured, system-generated report and a manually assembled document is measured in hours per report and in the frequency of errors.

Inspector qualification and certification expiry alerts. Every API inspection report must reference the certifying inspector's name and certification number. An inspection signed off by an inspector with a lapsed certification is not a valid API inspection — a finding that can invalidate the compliance record for every inspection conducted during the lapse period. Inspector certification expiry alerts — automated notifications sent to the inspector and their manager 90 days, 60 days, and 30 days before an API certification expires — are a non-negotiable feature of any inspection management system used in oil and gas. The same alerts apply to NDE qualifications, confined space entry medicals, and any other time-limited authorisation that affects the inspector's eligibility to conduct and sign off work.

HSSE record management. Confined space entry into pressure vessels and storage tanks generates a specific record set that must be retained with the inspection record: the entry permit, the gas testing results (confirming that the confined space is clear of toxic and flammable gases before entry), the rescue plan, and the post-entry sign-off confirming all personnel and equipment have exited. For inspection companies managing confined space entries across multiple sites and multiple concurrent jobs, centralised HSSE record management — with the entry permits and gas test records linked to the specific inspection job — is essential for demonstrating compliance if an incident occurs or an authority requests records.

Client portal and certificate delivery. Oil and gas operators who commission API inspection services expect timely, accessible inspection records. A client portal — where the operator can access their asset's inspection history, download the latest inspection report, and view the status of upcoming inspections — removes the administrative overhead of report distribution and provides the operator with a current, accessible record of their mechanical integrity programme. For inspection companies competing for contracts with major oil and gas operators, the ability to offer client portal access to live inspection data is a differentiator — demonstrating operational maturity and reducing the reporting burden on both sides.

How OMS addresses oil and gas inspection management. OMS manages the full lifecycle of oil and gas inspection records. Each pressure vessel, piping circuit, and storage tank is set up as a structured asset record containing its design data, CML network, and inspection history. Inspector qualification records — API certification numbers, NDE qualifications, and expiry dates — are stored in the personnel module with automated alerts before any certificate lapses. Inspection jobs are scheduled from the asset's due date calendar, assigned to qualified inspectors, and tracked from field execution through report generation to client delivery. Inspection reports are generated from structured data using API-aligned templates, reviewed and approved through a digital workflow, and issued with QR-verified certificate references. The client portal gives operators real-time access to their assets' inspection histories without requiring a separate reporting cycle.

For inspection companies expanding into oil and gas inspection, or for owner-operators looking to improve the structure and accessibility of their mechanical integrity records, OMS provides the record management foundation that API inspection programmes require — without the infrastructure overhead of legacy enterprise systems.