Third-Party Inspection and API 510/570/653 Program Support for Austin Manufacturing Facilities

What third-party inspection actually involves on an Austin engagement

Third-party inspection is independent verification against a written scope — not a general quality check, and not the vendor's or operator's own sign-off. On a new capital project, that scope is the inspection and test plan approved against the purchase order: hold points that stop work until the nominated party attends and signs, witness points that invite attendance within a notified window and may proceed if nobody comes, and review points that are document checks rather than site visits. On equipment already in service, the equivalent scope is the facility's own mechanical integrity programme — most often an API 510, API 570 or API 653 inspection plan — and the third-party role shifts from ITP surveillance to inspection execution and data review against that programme.

Verification means something specific in either case. It is not a technician looking at a weld and forming an opinion. It means confirming that the procedure in force on the date of the test is the correct, current revision; that the technician's certification covers the method, level and product examined and is valid on that date; that the instrument or gauge used carries a current calibration certificate; and that the acceptance criterion applied is a clause reference from a named code, not a subjective judgment call. Where any of those four elements is missing, the result is unverifiable regardless of how the work actually turned out.

What the client receives is a record, not just an attendance. A defensible inspection engagement produces a signed report tied to a specific asset identifier, thickness or examination data referenced against the prior reading, any indication disposed against a stated acceptance standard, and — where a hold point was involved — a signature from the party authorized to release it. A campaign that produces attendance without that paper trail has bought a presence on site, not third-party inspection.

The industrial base in Austin that this kind of oversight actually serves

Austin sits at the center of what is often called the Silicon Hills corridor — a concentration of semiconductor fabrication, electronics assembly and precision manufacturing that has grown steadily across central Texas. That base is supported by a layer of infrastructure most visitors never see: central utility plants that supply compressed air, process cooling, ultra-pure water and industrial gas to cleanroom tool sets, plus the bulk chemical delivery systems that feed etch, clean and deposition processes. None of that runs on the chip line itself, but none of it is optional either.

The region's rapid data center and advanced-manufacturing buildout has added a second layer of fixed equipment that is easy to overlook: standby diesel generation, and the aboveground fuel storage tanks that back it up. A facility that cannot tolerate a grid interruption for even a few minutes typically holds significantly more stored diesel on site than a conventional commercial generator would need, and that fuel sits in tanks that are themselves subject to inspection obligations most facility teams did not inherit any expertise in managing.

The general industrial base around Austin also includes precision machining, aerospace and defense component suppliers, renewable-energy equipment manufacturing and general fabrication shops serving the wider Central Texas market. Individually, none of these read as a heavy-industry site in the way a refinery or petrochemical complex does. Collectively, the fixed pressure equipment, process piping and storage infrastructure behind them is real, ages the same way any equipment ages, and is not exempt from mechanical integrity obligations simply because the product coming off the line is a wafer or a battery pack rather than a barrel of fuel.

The codes that actually govern this equipment mix

Fixed pressure equipment in and around a semiconductor or manufacturing campus is built to the same fabrication codes as anywhere else. Pressure vessels — compressed air receivers, chemical delivery and mix tanks, refrigeration vessels for process and cleanroom cooling — are built to ASME Boiler and Pressure Vessel Code Section VIII Division 1. Process piping distributing nitrogen, hydrogen, specialty gases and bulk chemicals is built to ASME B31.3. Neither code cares what the plant manufactures; both care about design pressure, material, weld quality and the documentation that proves it.

API 510, API 570 and API 653 are the in-service inspection codes most owner-operators use to manage that equipment once it is running, and their scope is broader than the refining and petrochemical world they were originally written for — each code's own language permits use on other covered equipment where an owner elects to apply it. In practice that means a facility with ASME Section VIII vessels and B31.3 piping in continuous or intermittent service can, and often does, run those assets under an API-based mechanical integrity programme even though the site is a fab or an assembly plant rather than a refinery. Supporting standards fill in the detail: API 574 for piping inspection practices, API 576 for pressure relief device testing, ASME PCC-2 for repair methods, and NB-23, the National Board Inspection Code, for repairs and alterations to boilers and pressure vessels.

Storage tanks split by construction method. Larger field-erected, welded steel tanks — the kind used for significant bulk chemical or fuel storage — fall under API 653. Smaller shop-fabricated diesel day tanks and UL-142 tanks common at generator installations are usually inspected to STI SP001 instead, which is written specifically for that construction type and carries its own interval logic. Getting that distinction wrong at the scope-of-work stage is one of the more common errors we see on Austin engagements. Personnel performing the NDT behind any of this — UT, radiography, magnetic particle, penetrant, phased array — should hold certification under ASNT SNT-TC-1A or ISO 9712 at a level appropriate to the method and the scope of work.

What a defensible inspection report package has to contain

A report that says a vessel or a piping circuit 'passed' is not a defensible record. A defensible package ties every finding back to a specific, permanently marked location — a condition monitoring location for a piping circuit, a grid reference for a tank floor scan — so the next inspection compares the same point rather than an approximate one. It states the procedure and revision used, the acceptance criterion as a clause reference, the instrument and its current calibration certificate, and the technician's certification and its validity on the date of the work.

For thickness-based inspection, the number that actually matters is the trend, not the single reading. A corrosion rate calculated from two comparable readings against the same CML, projected against the minimum required thickness, sets the remaining life and therefore the next inspection date — which is the entire logic behind a risk-based inspection interval. A report that delivers a single number with no reference to the prior reading has not given the client anything they can plan around.

Where a finding falls outside a code's built-in acceptance criteria — a thinned area below minimum thickness, a crack-like indication, damage from an unanticipated mechanism — the correct next step is not a field judgment call. It routes to an engineering fitness-for-service evaluation, and the technical basis behind that evaluation, and behind the acceptance criteria the field inspection is measured against in the first place, is the kind of work covered under ASNT Level III consulting support.

How an Atlantis engagement is mobilized and run for an Austin campaign

Atlantis is headquartered in Houston, with a second base in Hyderabad, and inspectors or technicians mobilize from one of those locations to the Austin site for the duration of the defined scope of work — a turnaround, a capital project's fabrication and installation phase, or an ongoing inspection programme running for months at a time. The engagement is built around continuity rather than a rotating pool: the same personnel who sat through the kickoff meeting and learned the site's access, badging and safety requirements are still there when the programme closes out.

Reporting is structured so the client's engineering and reliability teams see a consistent picture across the whole engagement — attendance and findings after each visit or shift, a rolling punch list where fabrication work is involved, and a data set that feeds directly into the client's own asset records rather than arriving as a stack of disconnected PDFs. Where a facility runs several concurrent scopes — say, an ongoing thickness monitoring round alongside a planned turnaround — reporting is coordinated so the two don't produce contradictory readings on the same equipment.

Every engagement is scoped against the client's own documents: their approved ITP for new equipment, or their existing API 510/570/653 written practice and inspection plan for equipment in service, and — where one is engaged — their Authorized Inspection Agency's requirements. Atlantis personnel work inside that framework rather than substituting one of our own, with the specific scope, schedule and reporting format agreed before mobilization begins rather than improvised on site.

Manpower Supply for API Inspection Programs

A recurring need on Austin engagements is not a full inspection programme design — it's qualified hands to execute one that already exists. Atlantis supplies NDT technicians and inspection support personnel — ultrasonic thickness and shear-wave UT, phased array UT, radiography, magnetic particle and liquid penetrant, certified under ASNT SNT-TC-1A or ISO 9712 as applicable — to augment a client's own API 510, API 570 or API 653 programme, mobilized from Houston or Hyderabad for the duration of the engagement and working inside the client's or their Authorized Inspection Agency's written practice.

This is technician supply and inspection execution support. It is not, and is never represented as, placement of an Authorized Inspector. Atlantis is not an API Authorized Inspector and does not act as inspector of record on any asset in Austin or anywhere else — that role, and the signature that goes with it, stays with the client's own API-credentialed inspector, whether they hold an API 510 certification directly or work through their appointed Authorized Inspection Agency. Our technicians generate the field data — thickness readings, weld examination results, CML trend data, relief valve test records — that the inspector of record reviews and signs against.

The engagement shapes vary with the client's need. Turnaround crew augmentation is the most common: a planned outage compresses months of CML rounds and internal vessel inspection into a fixed window, and the client's own crew is not sized for the peak. Multi-month programme staffing covers the opposite case — a facility running an ongoing thickness monitoring or piping inspection programme across a large equipment population that needs steady, dedicated coverage rather than a burst. Short-notice mobilization covers the case nobody plans for: an unplanned shutdown, an unexpected finding on a routine round, or a relief event that suddenly needs additional qualified hands on site faster than a standard hiring cycle allows.

Damage mechanisms worth watching given Austin's climate and equipment mix

Central Texas runs a humid subtropical climate — hot, wet summers and enough rainfall through the year to make corrosion under insulation a real, recurring finding on insulated piping and vessels rather than a theoretical one. CUI develops beneath the jacket, invisible from the outside, wherever moisture gets past a damaged vapor barrier or a poorly sealed penetration, and it concentrates at predictable places: pipe supports, low points, valve and flange interfaces, and the bottom third of vertical vessels. A CUI inspection programme has to include deliberate insulation removal at those locations, not just external visual walkdowns.

Outdoor storage tanks and exposed structural steel see ordinary atmospheric corrosion accelerated by the same humidity, plus the occasional severe winter event — the kind of hard freeze central Texas has experienced more than once in recent years — that stresses coatings, gaskets and instrumentation not designed with wide temperature swings in mind. Piping carrying specialty or corrosive gases needs its own material-compatibility review independent of the general corrosion picture, since some of those services attack specific alloys or weld metals in ways ordinary carbon steel thickness monitoring will not catch.

None of these findings resolve themselves through more frequent monitoring alone. Where a thickness reading, a CUI finding, or a metallurgical concern falls outside the acceptance criteria built into API 510, 570 or 653, the defensible next step is an engineering evaluation — fitness-for-service assessment under API 579-1/ASME FFS-1 — rather than a field decision to re-inspect and hope the number improves next round.

Documentation, traceability and the risk-based inspection link

An in-service API inspection programme is only as defensible as its records. That means an equipment record for every covered vessel, line and tank — design data, material of construction, maximum allowable working pressure, corrosion allowance — plus a complete inspection history, a CML database with every reading tied to a permanently marked location, and the calculated corrosion rate and remaining life that history supports. A facility that can produce a current inspection report but not the two or three readings before it cannot show a trend, and a trend is what an interval decision is actually based on.

Risk-based inspection formalizes that logic across a whole equipment population instead of one asset at a time — ranking each item by likelihood of failure and consequence of failure, then setting the next inspection date and the inspection method and extent from that ranking rather than from a flat calendar interval. The field data our technicians collect on an Austin engagement — thickness readings, coating condition, indications and their disposition — is exactly the input an RBI programme needs to stay current; stale field data is the most common reason an RBI-driven interval quietly drifts away from reality.

The traceability chain matters as much for an audit years later as it does on the day of the test. Procedure revision control, personnel certification records valid on the date of examination, instrument calibration certificates, and a non-conformance register that was actually written contemporaneously rather than reconstructed afterward — all of it has to survive being pulled at random by an insurer, a jurisdictional authority, or a new engineering team years after the original inspection. Records are never recreated after the fact; where a gap exists, the honest response is to document what actually exists and re-verify where it doesn't.

What to specify in a scope of work before mobilizing to an Austin site

The quality of an inspection engagement is set before anyone arrives on site. A workable scope of work names the equipment population by identifier, states the governing code basis for each asset class, and specifies whether technicians are executing against an existing ITP, an existing API 510/570/653 written practice, or both. It states the notification protocol and lead time for hold points, the reporting format and how often reports are delivered, and who on the client side has authority to release a hold or accept a disposition.

The gaps we see most often on Austin scopes are not technical. They're logistical: site access and badging lead time that a semiconductor fab's security and cleanroom gowning requirements can push out well beyond a typical industrial site, an undefined interface with the client's Authorized Inspection Agency where one is engaged, and acceptance criteria left as 'per applicable code' without naming the specific edition and clause. Every one of those gaps is cheap to close in the scope-of-work stage and expensive to discover mid-engagement.

If you're planning a turnaround, a new capital installation, or an ongoing API-based inspection programme in the Austin area and want the scope written against your actual equipment and written practice rather than a generic template, reach out and we'll build the engagement around it.

Request a consultation