Third-Party Inspection Services for Karratha's LNG and Iron Ore Export Industry

What Third-Party Inspection Actually Verifies on a Karratha Contract

Third-party inspection is built around the project's Inspection and Test Plan (ITP), a document that assigns every fabrication and testing activity a status: hold, witness, review, or surveillance. A hold point stops work until the inspector physically attends and releases it; a witness point lets work proceed on notice if the inspector cannot attend but still requires documented notification; a review point means the inspector checks records after the fact rather than attending in person. The ITP is negotiated between client, EPC, and fabricator before work starts, and it is this document, not general industry custom, that determines what gets inspected and when.

At each hold or witness point, verification typically covers four things: dimensional and visual conformance to the approved drawing, weld quality against the applicable procedure and acceptance criteria, material identity through mill certificates and heat-number traceability, and correct execution of any specified NDT method. A term like "hold point" or "release note" carries a specific meaning under most fabrication contracts; see the glossary for how these terms are used across ITPs, weld procedures, and release documentation.

The output of each verified point is a signed record, either a release allowing the next fabrication step to proceed or a non-conformance report describing what failed and what corrective action is required before re-inspection. On a Karratha-bound scope, that record travels with the equipment as part of the final documentation dossier handed over at commissioning.

The Industrial Base Behind Karratha's Inspection Demand

Karratha anchors one of Western Australia's two major Pilbara export streams. LNG liquefaction and processing trains in the area convert offshore and onshore gas into export product, running pressure vessels, cryogenic and process piping, rotating compression equipment, and storage systems continuously, with planned shutdowns rather than continuous access driving most inspection windows. The neighboring Dampier port precinct handles iron ore export for the region's mining operations, moving ore through crushing, screening, conveying, stockyard, and ship-loading infrastructure that is almost entirely structural steel and mechanical handling equipment operating under constant cyclic and abrasive loading.

Supporting both industries is a network of fabrication and maintenance yards, some local to the Pilbara coast, many in Perth, other Australian states, or overseas, that build the piping spools, vessels, structural modules, and skids later shipped or trucked to site for final assembly. That split between where equipment is built and where it is installed is the structural reason third-party inspection matters here: a client's site-based QA/QC team cannot be in a shop in another state or country at the moment a critical weld is made, so verification has to happen at the point of fabrication, not just at receipt.

The result is a mixed inspection landscape on any given Karratha-linked contract, spanning shop inspection at multiple vendor locations, receiving inspection at site, and in-service or turnaround inspection once equipment is operating. Each stage draws on different personnel qualifications and different sections of the same ITP.

Codes and Standards That Govern the Equipment Mix

Pressure equipment installed in Western Australia is generally designed to AS 1210, the Australian pressure vessel code, and brought into service under the state's dangerous goods and pressure equipment safety framework administered by WorkSafe WA, with AS 3788 governing in-service inspection intervals once equipment is operating. Process piping on LNG and gas processing scopes is very commonly specified to ASME B31.3, reflecting how much of the engineering for Pilbara LNG infrastructure has historically drawn on American design codes even on an Australian site, sometimes alongside the Australian piping code AS 4041 depending on the contract.

Storage and low-pressure containment equipment is typically inspected against API 650 for atmospheric tanks and API 620 for low-pressure and refrigerated storage, both American Petroleum Institute standards that remain the default reference internationally for welded steel tanks regardless of country. Structural steel on ship-loaders, conveyor structures, and stockyard infrastructure falls under AS/NZS 1554.1, the Australian structural welding code, with acceptance criteria that differ meaningfully from the pressure-equipment codes in how weld defects are categorized and sized.

Personnel performing the NDT itself are qualified under either ASNT SNT-TC-1A, the American framework common on projects with US engineering influence, or ISO 9712, the international framework that underpins Australian NDT certification through AINDT. Projects frequently specify one or accept both, and a defensible ITP states which framework applies rather than leaving it implied. For a fuller picture of how these codes interact across a project, the standards reference covers the major pressure, piping, and structural codes referenced on Pilbara-bound work.

What a Defensible Release Package Has to Contain

A release that will hold up under a client audit, an insurer's review, or a later fitness-for-service question needs more than a signed inspection report. At minimum it should include the material test certificates for every heat number used, cross-referenced to a weld map that shows which welder made which joint with which procedure; the NDT technique sheets and result reports for every hold or witness point, not just a summary pass/fail line; post-weld heat treatment charts where PWHT was specified; hydrotest certificates showing pressure, hold time, and instrument calibration; and the calibration records for every piece of test equipment used to generate a result.

Non-conformances need their own trail: the original finding, the disposition (repair, reject, use-as-is with engineering justification), the re-inspection that closed it, and sign-off from whoever had authority to accept the disposition. A package missing this chain is difficult to defend later if a defect surfaces in service, and it complicates any subsequent fitness-for-service evaluation under API 579 if a flaw is found during an in-service inspection years after the original fabrication; a complete original release package is what makes that later assessment possible at all, a topic covered in more depth under fitness-for-service assessment.

Personnel qualification records referenced in the report, the specific procedure revision used for each weld or NDT technique, and the equipment serial numbers for radiography or ultrasonic instruments round out a package that a client's document control system can actually trace years later, not just at handover.

How an Atlantis Team Deploys for a Karratha Campaign

Atlantis engages Karratha work by mobilizing an inspection or NDT team for the duration of the contract, drawing personnel from its Houston and Hyderabad bases and deploying them to the fabrication shop, the site, or both, depending on where the ITP places the hold and witness points. The team is scoped and staffed against the client's specific ITP and schedule before mobilization, not assembled generically, so the certifications, methods, and headcount match what the contract actually requires.

For work executed at a supplier's shop away from the Pilbara coast, inspectors travel to the fabrication location for the relevant scope and stay through the hold points that scope covers; for site-based turnaround or receiving inspection, the team mobilizes to Karratha itself for the shutdown or campaign window, working the client's shift pattern and reporting structure for as long as the contract requires. Logistics, site induction, and any client-specific competency verification are handled as part of mobilization planning rather than left to be sorted out after the team lands.

Because the team scales to the contract rather than sitting on permanent standby, staffing can flex with the fabrication or turnaround curve, larger during peak weld and NDT activity, smaller during slower phases, without carrying a fixed local overhead structure. Scopes are discussed and quoted through contact once the ITP, code basis, and schedule are defined.

Manpower Supply for API Inspection Programs

Alongside third-party fabrication inspection, Atlantis supplies qualified NDT technicians and inspection support personnel, covering UT, PAUT, RT, MT, and PT, to augment a client's own API 510, API 570, or API 653 in-service inspection programme in Karratha. Technicians are certified to ASNT SNT-TC-1A or ISO 9712 and are mobilized for the contract duration, working inside the client's or their Authorized Inspection Agency's written practice rather than under a separate Atlantis-run program.

This is technician supply and inspection execution support: running the UT thickness surveys, PAUT scans, or surface NDT that an API inspection programme requires, and reporting results in the format the programme's written practice specifies. It is explicitly not placement of an Authorized Inspector and not an inspector-of-record service. Atlantis is not an American Petroleum Institute Authorized Inspector and does not act as inspector of record on any API 510, API 570, or API 653 programme; that role, and the associated sign-off authority, stays with the client's own API-credentialed inspector or their AIA. Background on what the credential covers is available on the API 510 reference page.

Two engagement shapes come up most often on Karratha work. The first is turnaround crew augmentation, adding certified technicians to an existing inspection team for a defined shutdown window when internal or currently contracted resources cannot cover the volume of UT, PAUT, or MT/PT work in the available outage time. The second is multi-month programme staffing, where technicians are embedded for an extended run supporting a rolling API 510 or API 653 inspection schedule across multiple vessels or tanks. A third, shorter pattern, short-notice mobilization to backfill an unplanned personnel gap on an active programme, also occurs, though it depends on certification and induction lead time rather than being instantaneous.

Damage Mechanisms That Shape the Inspection Scope

Karratha's coastal, cyclone-season climate and continuous industrial operation combine to drive specific, well-documented damage mechanisms. Salt-laden humidity accelerates external atmospheric corrosion on structural steel, piping, and tank shells, and corrosion under insulation (CUI) is a recognized risk on insulated piping and vessels operating near ambient-to-moderate temperatures where moisture can migrate under the cladding without being visible from outside.

On the LNG processing side, cyclic thermal loading from startup/shutdown cycles and, on cryogenic lines, low-temperature service add fatigue and brittle-fracture considerations to the standard corrosion picture, which is part of why process piping inspection under ASME B31.3 pays close attention to weld quality at nozzle and branch connections where stress concentration is highest.

Iron ore handling infrastructure, conveyors, transfer chutes, ship-loaders, and stockyard structures, experiences cyclic fatigue loading from continuous material movement and vibration, which is why structural weld inspection under AS/NZS 1554.1 pays particular attention to full-penetration butt welds on primary members rather than treating every weld as equal risk. Abrasive wear from ore handling adds a mechanical-damage dimension distinct from the corrosion and cracking mechanisms more typical of the LNG processing side. Where a flaw found during inspection raises a question about continued fitness for service rather than simple repair, that assessment is a separate engineering exercise from the inspection itself.

None of these mechanisms are unique to Karratha, but their combination, marine atmosphere, cyclonic weather exposure, and high-throughput continuous operation, is what makes inspection scope and frequency on Pilbara export infrastructure a genuinely engineered decision rather than a generic maintenance calendar.

Traceability Across a Multi-Vendor Supply Chain

A single piece of equipment installed at a Karratha facility may carry material from one mill, be fabricated at a shop in another state or country, be coated at a third location, and be inspected at each stage by different personnel. Traceability is what ties all of that back together: every heat number on the material certificate has to map to a specific location on the weld map, every weld has to map to a welder qualification record and procedure revision, and every NDT result has to map to a specific technician certification and calibrated instrument.

This matters practically, not just for audit purposes. If a flaw is later found in service, whether during an API 510 vessel inspection or an API 653 tank inspection, the ability to trace that location back to its original fabrication record, including which NDT method covered it and at what acceptance criteria, is often what determines whether the finding is treated as a new in-service defect or an original fabrication issue, which changes the engineering response.

Given the number of parties typically involved in supplying a Pilbara industrial project, digital record-keeping that keeps weld maps, MTCs, NDT reports, and calibration records linked rather than siloed in separate vendor systems is increasingly what separates a package a client's document control team can actually use from one that just gets filed.

What to Specify in the Scope of Work Before Mobilization

A scope of work that produces a defensible inspection outcome names the code edition being used (not just "ASME B31.3" but the specific edition and addenda), the acceptance criteria for each NDT method, the exact hold and witness points rather than a generic "inspect as required" clause, and the personnel certification standard, ASNT SNT-TC-1A or ISO 9712, expected of the inspector or technician.

For storage tank work specifically, a scope tied to an existing API 653 inspection programme should specify whether NDT support is covering shell thickness surveys, floor scanning, or nozzle and weld inspection, and should reference the tank's inspection interval basis under the client's written practice; background on what that credential and inspection cycle covers is on the API 653 reference page.

Finally, the scope should state the non-conformance reporting protocol, who has disposition authority, what documentation format the client's system requires, and the notice period the inspector needs for witness points. Ambiguity on any of these points is where inspection programs on multi-vendor projects most often lose time, not on the inspection work itself.

Request a consultation