Third-Party API Inspection Services in Billings, Montana: Refinery and Petrochemical Equipment Verification

What Third-Party Inspection Verifies in Billings

Third-party inspection is verification performed by an organization with no commercial stake in the fabrication, repair, or maintenance work being checked — distinguishing it from a contractor's own quality control and from the owner-operator's internal inspection department. On a Billings refinery or terminal project, that independence is what makes the resulting reports acceptable to insurers, regulators, and the asset owner's own risk-based inspection program. The scope is built around an Inspection and Test Plan (ITP) that assigns each activity — fit-up, weld completion, NDE, hydrotest — a hold point (work stops until the inspector signs off) or a witness point (the inspector may be notified but the contractor can proceed if not attended within a set window).

What verification actually covers on a typical job: dimensional and visual checks against the approved drawing, confirmation that welders and procedures are qualified (WPS/WPQ per ASME Section IX), positive material identification on alloy and dissimilar-metal joints, the NDE itself (UT, RT, MT, PT, or PAUT depending on the joint type and code), and review of the contractor's own records before they're accepted into the final data package. On piping and vessel work specifically, that includes checking that wall-thickness readings and CML (condition monitoring location) data tie back to the asset's retirement thickness calculation, not just that a weld looks sound.

Who typically initiates third-party inspection on a Billings job varies by contract structure. An owner-operator running its own mechanical integrity program may bring in outside inspectors purely for capacity during a turnaround; an EPC contractor building new piping or a replacement vessel may be contractually required to use a third party the owner approves; and an insurer or a purchaser accepting equipment from a fabricator may require independent verification before releasing payment or accepting delivery, regardless of what the fabricator's own quality system already checked.

Billings' Refining and Petrochemical Equipment Base

Billings sits at the center of Montana's petroleum refining corridor along the Yellowstone River, one of the few significant refining concentrations in the northern Rockies. The refineries and associated petrochemical operations in and around the city process a mix of regional crude — Bakken-formation light sweet crude from North Dakota and Western Canadian heavy crude delivered by pipeline — through crude distillation, catalytic reforming, hydrotreating, and coking units, alongside the pressure vessels, fired heaters, exchangers, and tankage that support them.

That equipment runs continuously between scheduled turnarounds, typically every three to five years depending on unit and jurisdiction, which means most of the inspection demand in Billings is concentrated in short, intense windows rather than spread evenly across the year. Storage terminals and pipeline interconnects around the city add a parallel stream of API 653 tank-inspection work that runs on its own cycle, largely independent of the refinery turnaround calendar. Gas processing and NGL fractionation infrastructure tied to Bakken and Powder River Basin production adds a further layer of piping and vessel assets governed by the same core codes.

Codes and Standards Governing Inspection Work in Billings

The code set that governs Billings refining and petrochemical inspection work is consistent with any comparable US refining hub: API 510 for in-service pressure vessels, API 570 for process piping, and API 653 for aboveground storage tanks, all of which reference ASME Section VIII (vessels) or B31.3 (piping) for original construction and repair rules, and ASME Section V for the NDE methods themselves. Weld procedure and welder qualification sits under ASME Section IX; where a vessel is repaired under National Board rules rather than an ASME stamp, NB-23 (the National Board Inspection Code) governs.

A few standards get disproportionate use on Montana refining equipment specifically: API 574 for piping inspection practices and CML selection, API RP 578 for positive material identification programs (important given the dissimilar-metal and alloy upgrades common in sour and high-temperature services), and API 571 as the reference for the damage mechanisms most likely to be found. Full detail on how these standards interact — and where they diverge from one another on inspection interval and acceptance criteria — is covered on our standards reference.

Personnel certification standards run alongside the technical codes: API 510, 570, and 653 all require that NDE be performed by individuals qualified under a documented programme, typically ASNT SNT-TC-1A employer-based certification or ISO 9712 third-party certification, at the method and level appropriate to the technique being used. API RP 577 adds welding-inspection and metallurgy guidance that's increasingly referenced on sour-service and high-temperature piping work, on top of the base ASME and API set.

What a Defensible Inspection Report Package Contains

An inspection report that will actually hold up — to an insurer, a regulator, or a future fitness-for-service evaluation — has to be more than a pass/fail stamp. At minimum it needs the NDE technique sheet (method, equipment model and serial number, calibration block and reference reflector, scan coverage, and the technician's certification level), the calibration record tied to that specific job, and a weld map or line schedule showing exactly which joints were examined and with what result.

Material traceability matters just as much: heat numbers and mill certs for the base material, PMI results for any alloy or dissimilar-metal joint, and non-conformance reports for anything that didn't pass on first inspection, along with the disposition (repair, reject, accept-as-is with engineering sign-off) and the re-inspection that closed it out. The final release document — the hydrotest certificate or return-to-service sign-off — should reference every one of those records by document number so the chain from raw material to final acceptance is auditable years later. Definitions for the terms used across that package are collected in our glossary.

Photographic evidence increasingly rounds out the package: geo- and time-stamped photos of the joint before closure, of the NDE indication itself where relevant, and of the completed repair, filed against the same document numbers as the written report. None of that replaces the technique sheet or the calibration record, but it gives a reviewer years later a faster way to confirm what was actually inspected without re-deriving it from prose alone.

How an Atlantis Engagement Works for a Billings Campaign

For a Billings engagement, Atlantis scopes the job first — method mix, code basis, staffing count, and duration — then mobilizes a team from our Houston base or our Hyderabad technical center for the length of the contract, whether that's a two-week turnaround push or a multi-month programme. Technicians are matched to the job by method certification and, where the client requires it, by specific procedure experience (PAUT on girth welds, MFL floor scanning on tanks, RT on thick-wall coker piping).

Mobilization planning accounts for Montana specifically: winter access and weather contingency for outdoor tank and piping work, equipment shipment lead time, and site-specific orientation and safety onboarding before the crew steps on site. Throughout the engagement, the team reports into the client's own site QA/QC lead or their Authorized Inspection Agency, working the ITP the client (or their AIA) has already approved rather than setting inspection policy independently. When the contract scope closes, the crew demobilizes and the completed data package transfers to the client's record system. Reach out through contact with the scope and timeline and we'll put together a staffing and mobilization plan.

Manpower Supply for API Inspection Programs

A large share of the work Atlantis does in refining hubs like Billings is manpower supply, not inspection authority: qualified NDT technicians and inspection support personnel — UT, PAUT, RT, MT, and PT, certified to ASNT SNT-TC-1A or ISO 9712 — who augment a client's own API 510, API 570, or API 653 inspection programme for the length of a contract. This is technician supply and inspection execution support. It is not, and is never sold as, an Authorized Inspector placement: Atlantis is not an API Authorized Inspector and does not act as inspector of record on any Billings engagement. That role, and the acceptance authority that comes with it, stays with the client's own API-credentialed inspector or their Authorized Inspection Agency (AIA), and every technician we supply works under that party's written practice and procedures, not ours.

In practice that shows up in a few recurring engagement shapes. The most common is turnaround crew augmentation — a client's in-house or AIA inspection team has approved the ITP and needs additional certified hands to execute the NDE volume inside a compressed outage window; Atlantis supplies the technicians, and the client's inspector reviews and accepts the results. The second is multi-month programme staffing, where a Billings facility is running a standing API 570 piping or API 653 tank inspection programme year-round and needs consistent technician coverage without carrying that headcount permanently; a supplied crew rotates through the programme under the client's written practice for the duration of the arrangement. The third, less frequent but real, is short-notice mobilization — an unplanned shutdown or a failed CML reading that requires additional UT or PAUT coverage faster than a client can staff internally. For background on what the underlying inspector credential actually requires — useful context even though Atlantis's role here is staffing execution, not holding that credential ourselves — see our reference page on the API 570 certification. Atlantis does not administer or sell that certification.

Damage Mechanisms Relevant to Montana Refining Service

The damage mechanisms an inspection programme in Billings needs to be tuned for follow directly from the unit types running there. Crude and vacuum units see naphthenic acid and sulfidation corrosion where acidic, sulfur-bearing crude fractions attack carbon and low-alloy steel piping and vessel internals, showing up as localized wall loss that generic CML grids can miss if they're not placed at known high-velocity or turbulent points. Hydrotreating and reforming units bring high-temperature hydrogen attack (HTHA) risk on older carbon-steel equipment and hydrogen-induced or wet H2S cracking in sour water and amine services, both of which call for wet fluorescent MT or specific UT backscatter techniques rather than routine thickness gauging alone.

Montana's climate adds a mechanism that's easy to underweight: corrosion under insulation (CUI) driven by repeated freeze-thaw cycling rather than steady humidity, which tends to concentrate damage at insulation jacket penetrations, pipe supports, and low points where meltwater collects rather than uniformly under the lagging. A risk-based inspection programme that weights CML and CUI-inspection-window placement by these local factors — not a generic API 571 checklist — catches more before it becomes a repair. That's the kind of programme design work covered under our risk-based inspection program design consulting.

Documentation and Traceability Requirements

Refining equipment in Billings is typically in service for decades, which means an inspection record has to outlive the technician who wrote it, the contract it was written under, and often the software the client used to store it. Traceability runs in both directions: forward from a material heat number through the weld it went into, the NDE that cleared it, and the final release document; and backward from any future finding — a CML that's trending faster than expected, an anomaly on a re-inspection — to every prior record for that same weld or component.

Practically, that means every report Atlantis delivers carries the identifiers needed to make that link: equipment tag number, CML or weld ID consistent with the client's own numbering system, technician certification number and level, and calibration records referenced by date and equipment serial number rather than described in prose. Where a CML trend or an unexpected finding needs an engineering disposition rather than an automatic repair, that path runs through fitness-for-service evaluation under API 579 — see our fitness-for-service work — rather than through the inspection report alone. Traceability is what lets that fitness-for-service evaluation start from real data instead of an estimate.

What to Specify in a Billings Inspection Scope of Work

Buyers writing a scope of work for third-party inspection support in Billings get better outcomes when the SOW is specific rather than generic. At minimum it should name the governing code for each equipment class (API 510 / API 570 / API 653, with the ASME Section VIII, B31.3, or Section V edition and addenda in effect), state explicitly who holds Authorized Inspector or AIA authority and who is being asked only to supply execution personnel, and list the acceptance criteria reference for each NDE method rather than leaving "per applicable code" as the only guidance.

It should also set the certification standard for supplied technicians (ASNT SNT-TC-1A written practice versus ISO 9712, and the method/level required for each activity — PAUT commonly needs a Level II with specific procedure qualification, not just a general UT card), the hold and witness points on the ITP, mobilization lead time given Montana's logistics and weather windows, and the reporting format and turnaround the client needs to keep pace with a compressed outage schedule. A scope built this way is also easier to audit later, since every requirement in it maps to a specific line in the final data package.

Request a consultation