Third-Party Inspection Services in Galveston, Texas: API Programme Support, NDT Execution, and Release Documentation

What Third-Party Inspection Covers on a Galveston Contract

Third-party inspection is a contractual role, not a single test performed once. An inspection and test plan built by the client or their engineering contractor lays out a sequence of hold points, where work cannot proceed until the inspector has attended and signed off, and witness points, where the inspector is notified and may attend, but the fabricator can proceed on schedule if the inspector does not show. On a Galveston fabrication or repair contract, a third-party inspector working those points is verifying that what actually happened on the shop floor or at the job site — a weld pass, a hydrotest, a dimensional check, a coating thickness reading — matches the approved drawing, procedure, and code requirement, not just that paperwork exists saying it happened.

That verification role includes reviewing welder and welding procedure qualifications before work starts, witnessing or performing volumetric and surface NDE at the stage the ITP specifies, checking material certifications against the purchase order and code requirements, and confirming that any nonconformance was dispositioned through the client's management-of-change or NCR process rather than worked around informally. The independence matters because the fabricator carries schedule pressure the inspector does not share, and because the client — an owner-operator, an EPC, or a shipyard — needs a result it can rely on regardless of how the production schedule is running that week. For definitions of the ITP terminology used across these contracts, see our glossary.

Galveston's Industrial and Equipment Base

Galveston's economy runs on the port and the industrial corridor around it. Bulk-liquid and breakbulk terminals move refined products, chemicals, and project cargo through piping manifolds, storage tanks, and loading arms that see continuous cyclic service and routine exposure to salt-laden Gulf air. Marine fabrication and repair yards build and maintain barges, offshore-support vessels, and structural steel used in both marine and onshore process work, running welded hull plate, deck structure, and piping systems through the same shops that also handle onshore fabrication packages.

Offshore-support and supply vessels staged out of Galveston carry deck cranes, winches, and mooring hardware that need periodic volumetric and surface examination both in drydock and during service. Inland from the waterfront, the city's refining and petrochemical works run pressure vessels, heat exchangers, and piping circuits that fall under the same in-service inspection codes used across the wider Gulf Coast — API 510 for pressure vessels, API 570 for piping, and API 653 for atmospheric storage tanks; see our API 653 overview for how those in-service inspection intervals are structured. The combination of new-fabrication acceptance work at the yards and in-service degradation assessment at the process plants means a Galveston inspection programme often has to cover both in the same crew rotation, with technicians moving between a shop witness point one week and a turnaround weld list the next.

Codes and Standards Governing Galveston Inspection Scopes

The code set that governs a Galveston scope depends on whether the equipment is new-build or in-service, and whether it sits on the marine side or the process side of the port. In-service pressure vessels fall under API 510, piping circuits under API 570, and atmospheric storage tanks under API 653 — all three call up ASME Section V for the NDE methods themselves and ASME Section IX for welder and welding-procedure qualification whenever a repair is involved. New fabrication of structural steel for dock, berth, and topside work is typically built and inspected to AWS D1.1, which sets its own acceptance criteria for weld profile, undercut, and porosity that differ from the ASME vessel code's criteria. Offshore-support vessel hardware — cranes, padeyes, mooring fittings — is commonly inspected to API RP 2X for ultrasonic and magnetic-particle examination of offshore structures, alongside classification-society rules where the vessel is under class. A scope of work that names the wrong code family for the equipment in front of the inspector is one of the more common sources of a rejected report months later; our standards reference maps these code families to equipment type in more detail.

Building a Defensible Release Package

A release package that survives an audit or a later failure investigation has to do more than state a pass or fail result. At minimum it needs to identify the exact code edition and acceptance criteria applied, not just the code family — a UT report that says accepted per API 510 without the edition and any client-specific supplement leaves the acceptance decision effectively unverifiable years later when someone has to reconstruct what standard actually governed the call. It needs equipment records: the make, model, and current calibration date of every instrument used, from UT flaw detectors and PAUT phased-array units to MPI yokes and PT developer batch numbers, because a result generated on out-of-calibration equipment is not defensible regardless of how clean the reading looked.

It needs personnel records showing the technician's current certification level and method under ASNT SNT-TC-1A or ISO 9712, matched to the technique actually performed on that joint. Weld maps or line drawings marked up with the real location of each indication — not just a summary indication count — let a later engineer or the client's Authorized Inspection Agency trace a finding back to a specific joint years after the original crew has moved to another contract. And any indication that was accepted, rejected, or dispositioned through repair needs its own record showing who made that call, against what criteria, and when, kept separate from the raw NDE data sheet itself.

How Atlantis Mobilizes for a Galveston Campaign

Atlantis is headquartered in Houston, within reach of the Galveston port and industrial corridor, with a second technical base in Hyderabad, India that supports report review, procedure development, and coverage across time zones on multi-shift programmes. For a Galveston engagement, a crew — sized to the scope, from a single PAUT technician covering a turnaround weld list to a multi-method team running parallel shop and field work — mobilizes to the site for the duration of the contract, working the client's shift pattern and reporting through whatever document control system the project already uses.

Equipment, calibration records, and technician certification packages travel with the crew and are staged before the first hold point on the ITP so there is no ramp-up delay once the work window opens. Procedure development, technique qualification, and report review can run in parallel from either base while the field crew executes, which keeps a Galveston campaign moving without idle inspector time waiting on paperwork to clear. When the contract scope changes mid-campaign — a turnaround extends, or additional joints get added to the weld list — crew size adjusts against the existing mobilization rather than triggering a fresh procurement cycle. Contact Atlantis to scope a Galveston mobilization against a specific ITP and code requirement.

Manpower Supply for API Inspection Programs

A significant share of Atlantis's Galveston work is manpower supply rather than a standalone inspection contract: augmenting a client's own API 510, API 570, or API 653 inspection programme with qualified execution capacity rather than replacing it. Atlantis supplies NDT technicians and inspection support personnel — UT, phased array UT (PAUT), RT, MT, and PT operators certified to ASNT SNT-TC-1A or ISO 9712 — who work inside the client's written practice or that of the client's Authorized Inspection Agency, performing the examinations, logging the readings, and generating field data that the client's own API-credentialed inspector reviews and dispositions. This is technician supply and inspection execution support. It is not placement of an Authorized Inspector: Atlantis is not an API Authorized Inspector and does not act as inspector of record on a Galveston programme; that authority, and the signature on the final acceptance, stays with the client's own API 510, 570, or 653-commissioned inspector or their Authorized Inspection Agency.

Two engagement shapes cover most of what comes up on the Gulf Coast. The first is turnaround crew augmentation — a refinery or terminal outage where the in-house inspection group needs additional UT and PAUT hands for a compressed weld and CML list, staffed for the outage window and released at completion. The second is multi-month programme staffing, where a client running an ongoing API 653 tank inspection cycle or a rolling API 570 piping circuit programme needs a steady technician headcount for the length of the programme rather than a single outage. Short-notice mobilization — a failed component, an unplanned shutdown — draws on the same certified technician pool, staged from Houston, without a separate procurement cycle for each callout.

Damage Mechanisms Common to Gulf Coast Marine and Process Equipment

The damage mechanisms an inspection programme is actually screening for in this region are fairly consistent across the process and marine equipment mix. Corrosion under insulation is a persistent finding on insulated piping and vessels exposed to Gulf Coast humidity and salt-laden air, concentrated at penetrations, supports, and terminations where moisture gets trapped against the steel — API 570 and API 653 programmes both budget inspection windows specifically for CUI-prone zones. Wet H2S service in refining and petrochemical units raises the risk of hydrogen-induced cracking and sulfide stress cracking in susceptible steels, which is why UT shear-wave and PAUT techniques capable of detecting subsurface, laminar-oriented indications are specified over straight-beam UT alone in those circuits.

On the marine side, splash-zone and atmospheric corrosion on hull plate, deck structure, and mooring hardware runs faster than fully submerged corrosion because of the wet-dry cycling, and microbiologically influenced corrosion shows up in ballast and seawater-cooled systems. Where a finding raises a question about whether a component can keep running rather than simply whether it passed or failed a single reading, a fitness-for-service evaluation under API 579 — see our FFS overview — is the mechanism for making that call on engineering grounds instead of a blanket replace decision.

Documentation and Traceability Requirements

Inspection data only has value if it can be traced back to a specific component years later and compared against the last reading taken at that same location. That means condition monitoring location numbering has to stay consistent between inspection cycles, thickness readings need to reference the same grid or point ID every time rather than a fresh nearest-approximate spot, and NDE result sheets need to cite the specific line number, spool, or vessel nozzle rather than a general area description.

For clients running a risk-based inspection programme, the traceability requirement is even tighter, because RBI corrosion-rate calculations and remaining-life estimates depend on comparing like-for-like readings across inspection intervals — a broken CML chain forces the RBI model back onto conservative default corrosion rates rather than measured ones, which shows up later as unnecessarily short reinspection intervals or premature component replacement. Atlantis field crews working under a client's RBI programme match data collection to whatever CML and interval structure the programme already runs on rather than introducing a parallel numbering scheme that has to be reconciled afterward. Where a client is setting up or revising an RBI programme from scratch, our RBI programme design work covers how CML placement and interval logic get established in the first place.

What to Specify in a Galveston Scope of Work

A scope of work that leaves inspection requirements implicit is one of the more common drivers of disputed results later in a contract. At minimum, a Galveston scope should name the code and edition governing the equipment — API 510's 2022 edition versus an older one matters when acceptance criteria have changed — list the specific hold and witness points rather than a generic instruction for the inspector to attend as required, and state the NDE methods and acceptance criteria per weld or component class rather than leaving method selection to whoever shows up that day. It should specify the certification level required of technicians — ASNT SNT-TC-1A Level II or III, or the equivalent ISO 9712 level, by method — and whether calibration records need to be submitted before mobilization or only produced on request.

For port and marine-adjacent work specifically, the scope should address site access requirements up front: a Transportation Worker Identification Credential (TWIC) is standard for unescorted access to secured port terminal areas, and the lead time for background processing should be built into the mobilization schedule rather than discovered the week work is supposed to start. Report turnaround time and the format the client's document control system requires — PDF package, structured data export, or a specific report-writing platform — should be fixed in the scope itself, not negotiated after the first deliverable comes back late or in the wrong format.

Request a consultation