Third-Party Inspection Services in Hyderabad: API- and ASME-Based QA/QC for Aerospace, Defence and Pharma Manufacturing

What Third-Party Inspection Covers in a Hyderabad Contract

Third-party inspection is verification carried out by a party independent of the buyer and the fabricator, working strictly to the purchase order's technical requirements rather than either party's commercial interest. On a Hyderabad-based contract this typically starts with review and agreement of an Inspection and Test Plan (ITP) before fabrication begins — a document that maps every stage of manufacture (material receipt, forming, welding, heat treatment, machining, NDE, pressure testing, final assembly, coating, packing) against a governing code or specification and marks each stage as a hold point, a witness point, or a review point. A hold point stops work until the inspector has attended and signed off; a witness point allows work to proceed if the inspector, given notice — commonly 48 hours for a witness point and several working days for a hold point on Indian sub-vendor contracts — does not attend. Review points are checked from documentation alone, without a site visit. Definitions of these terms and related inspection vocabulary are collected in the glossary.

The verification itself covers more than watching an NDE technician work. It includes checking incoming material against mill certificates and the purchase specification, confirming welder and procedure qualifications are current before welding starts, witnessing or reviewing NDE results against the applicable acceptance criteria, checking dimensions and surface finish against the drawing, witnessing pressure or leak tests, and reviewing the finished documentation package before the item is released for shipment. On a well-run programme, the inspector's authority is limited to what the ITP and the referenced code actually require — the value of a third-party inspector comes from consistent, documented application of an agreed standard, not from arbitrary rejection.

Hyderabad's Industrial Base: Why the Inspection Load Looks Different Here

Hyderabad's manufacturing economy is built around two clusters that do not usually show up together in one Indian industrial city: aerospace and defence production, and bulk-drug and pharmaceutical manufacturing. The aerospace and defence cluster covers structural and engine components, precision-machined parts, castings and forgings, and hydraulic and pneumatic assemblies supplied into airframe, engine and ordnance programmes — work where dimensional tolerance, material pedigree and freedom from subsurface defects are safety-of-flight or mission-reliability issues, not just contractual ones. A cracked casting or an out-of-spec heat lot that reaches assembly in this sector is a fundamentally different order of problem than the same defect in a piece of general industrial equipment.

The pharmaceutical and bulk-drug cluster is just as significant to the inspection workload, though the failure mode is different. Reactors, jacketed vessels, stainless steel process and utility piping, clean-in-place skids and associated pressure equipment have to meet both mechanical integrity requirements and hygienic design requirements — a pinhole leak or a poorly finished internal weld affects product purity as much as pressure containment. These plants also run conventional utility infrastructure — boilers, compressed air and steam systems, cooling water piping, storage tanks — that falls under the same in-service inspection codes used across the process industry, regardless of what the plant ultimately manufactures. A Hyderabad inspection scope regularly spans AS9100-driven aerospace acceptance criteria on one contract and ASME/API-driven process equipment acceptance criteria on the next, sometimes within the same client's supply base.

Codes and Standards That Actually Govern the Work

Which code applies is set by the end use of the component, not by the fact that it was made in Hyderabad, so a credible inspection scope of work names the specific standard rather than a generic reference to 'NDT.' For aerospace and defence suppliers, the quality system baseline is typically AS9100D, special processes such as heat treatment, welding, plating and non-destructive testing are frequently required to run under NADCAP accreditation, and first-article acceptance follows AS9102. For pharmaceutical and bulk-drug process equipment, the relevant references are usually ASME Section VIII Division 1 for pressure vessel design and fabrication, ASME BPE for bioprocessing equipment surface finish and hygienic-weld requirements, and ASME B31.3 for process piping, with ASME Section V governing the NDE methods — radiography, ultrasonic, liquid penetrant, magnetic particle, eddy current — used to examine welds under any of those codes.

Valves and other pressure-retaining trim are commonly qualified to API 598 for inspection, examination and pressure testing, with design and material requirements tied back to ASME B16.34. Structural steelwork and pipe supports typically follow AWS D1.1 or the client's project specification. On the personnel side, NDE technicians performing this work are expected to hold current certification under ASNT SNT-TC-1A (an employer-based written-practice scheme) or ISO 9712 (a third-party certification scheme), at a method and level appropriate to the technique and the acceptance criteria being applied. A fuller index of the codes referenced across Atlantis's inspection programmes is maintained on the standards page.

What a Defensible Release Package Has to Contain

An inspection report is only useful if it can be defended later — in a warranty dispute, an insurance claim, or a regulatory audit — and that means the package has to stand on its own, without relying on someone's memory of the job. At minimum, a defensible release package identifies the ITP revision it was executed against and shows sign-off at every hold and witness point, references the specific NDE procedure number and revision used for each examination together with the technician's certification level and current certificate number, and includes calibration records for the equipment used — reference blocks, calibration blocks, film or digital detector verification, gauge certificates — traceable to a recognized standard.

It also needs material certification in the format the contract calls for (commonly EN 10204 3.1 or 3.2, or the ASTM equivalent), the raw NDE records themselves (radiographic film or digital images, UT scan data, MT/PT indication maps) retained for the period the contract or code specifies, a non-conformance report log showing every rejection and its disposition, and a final release note that ties the whole package back to the purchase order revision it satisfies. Where a recorded indication is found to be within acceptable limits under a fitness-for-service evaluation rather than simply rejected, that evaluation — typically run under API 579-1/ASME FFS-1 — needs to be referenced and attached rather than summarized; Atlantis's separate fitness-for-service work covers that evaluation when a client needs one. A package missing any of these elements is not really a release package — it is a claim that can't be checked.

How an Atlantis Deployment Runs for a Hyderabad Campaign

For a Hyderabad campaign, Atlantis mobilizes an inspection team, drawing on personnel based in Houston and in Hyderabad, for the duration of the specific contract — sized and deployed to that engagement rather than kept on a standing retainer. Mobilization starts before the first hold point: the ITP is agreed with the client, the applicable code and acceptance criteria are confirmed against the purchase specification, and the inspection team is sized to the actual inspection load in the plan. A single technician attending witness points on a modest fabrication order looks nothing like the multi-person team needed to cover concurrent hold points across several vendor shops during a busy production window.

Once mobilized, the team works to the vendor's production schedule rather than a fixed calendar, attending hold points as they come due and reporting findings back to the client on an agreed cadence rather than only at the end of the job — so a recurring problem at one vendor surfaces while there is still time to correct it, not after the batch has shipped. Equipment (calibration blocks, gauges, portable NDE instrumentation) travels with the team or is sourced and verified locally against the same calibration requirements written into the ITP. When the contract or campaign ends, the mobilization ends with it; there is no ongoing retainer implied. Clients with a scope of work ready for review can start the conversation through contact.

Manpower Supply for API Inspection Programs

A number of process and utility systems inside Hyderabad's pharmaceutical and industrial facilities — boilers, pressure vessels, tank farms, process and utility piping — fall under API in-service inspection codes regardless of what the plant's end product is: API 510 for pressure vessels, API 570 for piping systems, and API 653 for atmospheric storage tanks. Running these programmes well usually needs more qualified NDE hands than a plant keeps on staff year-round, which is where Atlantis's manpower supply comes in. Atlantis supplies qualified NDT technicians and inspection support personnel — covering ultrasonic testing (UT), phased array ultrasonic testing (PAUT), radiographic testing (RT), magnetic particle testing (MT) and liquid penetrant testing (PT) — certified to ASNT SNT-TC-1A or ISO 9712, mobilized for the duration of the assignment to augment a client's own API 510/570/653 in-service inspection programme.

This is technician supply and inspection execution support: the personnel work under the client's own written practice, or that of the client's Authorized Inspection Agency (AIA), performing the examinations the programme calls for. It is explicitly not the placement of an API Authorized Inspector — Atlantis is not an API Authorized Inspector and does not act as inspector of record on any assignment; that role, and the associated sign-off authority, stays with the client's own API 510/570/653-credentialed inspector or their AIA. Two engagement shapes come up most often. The first is turnaround or shutdown crew augmentation: a plant scheduled for a short, high-intensity outage needs a burst of certified UT/PT/MT technicians to clear internal and external exams on vessels, piping and tanks within a fixed outage window, and Atlantis sizes and mobilizes a crew for that window specifically. The second is multi-month programme staffing: an ongoing in-service inspection cycle, often driven by a risk-based inspection schedule, needs steady technician coverage over months rather than a single event, and Atlantis staffs and rotates personnel for the length of that assignment. A related short-notice variant covers unplanned events — a suspected leak or a non-conformance that needs an immediate exam — where mobilization timelines compress but the same boundary on role still applies. Background on the underlying programme technicians support is available on the API 510 reference page.

Damage Mechanisms and the Documentation Trail They Leave

The damage mechanisms worth watching for track the two industrial clusters described above. In aerospace and defence-grade castings and forgings, the concern is subsurface porosity, shrinkage, cold shuts and inclusions from casting, plus fatigue-initiating machining defects or grinding burns that a visual check will not catch — which is why radiography and penetrant testing remain central even on parts that look flawless. In stainless steel pharma process equipment, the recurring issues are weld-related: lack of fusion or incomplete penetration in orbital or manual TIG welds, sensitization and subsequent intergranular attack from poor heat control during welding, and chloride-driven pitting or stress corrosion cracking in piping and vessels exposed to cleaning or process chemistries — all of which push toward radiographic or ultrasonic weld examination plus positive material identification (PMI) to confirm alloy grade before the weld is ever made.

In-service equipment governed by API 510, 570 and 653 programmes adds thinning from general or localized corrosion, and cracking at high-stress locations such as nozzle-to-shell welds, as the mechanisms an inspection programme is built to catch before they become a failure. Where the same damage mechanism recurs across a facility's equipment population, the more useful move is often to fold the finding into a formal risk-based inspection programme rather than treat each occurrence as an isolated repair — that is the kind of programme-level work covered under Atlantis's RBI programme design consulting. Whatever the mechanism, the documentation discipline is the same: every indication found, evaluated and dispositioned needs to be traceable back to a specific weld, heat number or equipment tag, not just noted as 'defect found and repaired,' because that traceability is what lets a future fitness-for-service evaluation, a warranty claim or a later inspection actually use the finding.

What to Put in the Scope of Work Before Mobilization Starts

The quality of a third-party inspection engagement is set largely by how specific the scope of work is before anyone mobilizes. A scope that simply says 'NDT inspection per applicable code' leaves the applicable code, the acceptance criteria, and the split of hold versus witness points to be argued about mid-fabrication, which is the worst time to argue about them. A workable scope names the governing code and edition explicitly (ASME Section VIII Division 1, API 598, AS9100D, or whichever applies), states the acceptance criteria to be applied rather than assuming the base code's default table is intended, and specifies which stages are hold points versus witness points along with the notice period the vendor is required to give — building that structure directly into the ITP rather than leaving it as a separate understanding.

It should also specify the minimum NDE method, technique and personnel certification level required for each examination (for example, PAUT to a written technique versus conventional shear-wave UT, or PT Level II versus Level I with Level II sign-off), the material certification format required from the vendor, and the retention period and format for NDE records and radiographs. For programmes expected to run for months rather than weeks, it is worth specifying the reporting cadence separately from the final release documentation, so recurring issues at a vendor surface during the programme rather than only in the closing report. Buyers assembling this kind of scope for the first time, or auditing one written by a vendor, often benefit from an outside read before it goes out to bidders rather than after fabrication is already under way.

Request a consultation