Vendor Surveillance and Third-Party Inspection at Dammam Supplier Works

What Vendor Surveillance at a Dammam Works Actually Involves

Third-party inspection is often sold as attendance and bought as reassurance. What it really is, is a chain of verifications tied to a purchase order: confirming that the material which arrived is the material specified, that the people welding it hold current qualifications, that the examinations performed match the procedures approved, that heat treatment and testing happened as written, and that the paperwork describing all of it is internally consistent before anything ships.

On a Dammam contract that chain runs from the pre-inspection meeting through material receipt, fit-up, welding, NDE, post-weld heat treatment, machining, assembly, pressure testing, coating and preservation, to release. Each of those has a defined intervention type. The inspector is the purchaser's representative at the works, not part of the supplier's quality department, and the value comes precisely from that separation.

The commercial pattern in this market is monthly or campaign-based rather than per-visit, because equipment is built continuously. A wellhead order, a valve batch and a set of vessels progress in parallel across several works in Dammam, Khobar and the Jubail corridor. Booking inspection by the visit against that reality guarantees you miss operations; booking a deployed inspector against the campaign does not. Scoping which points genuinely need attendance, and which can be closed by document review, is where ASNT Level III consulting earns its place before a single inspector mobilises.

Reading the ITP Before It Is Approved, Not After

The inspection and test plan is the contract for inspection. Once it is approved, it defines what the supplier owes you and what your inspector is entitled to see. Almost every dispute later in the order traces back to an ITP that was approved quickly because the schedule was tight.

Three things need attention before signature. First, the intervention type on each line: H for hold, W for witness, R for document review, M for monitor. An operation marked R when it should have been H cannot be recovered later. Second, the acceptance reference on each line, naming the code, clause and revision rather than the phrase as per specification. Third, the deliverable each line produces, because a line that generates no document generates no evidence.

Look specifically at the lines suppliers prefer to soften: thermocouple attachment before PWHT, hardness survey locations on sour-service items, seat test hold durations, surface preparation before blast, and NDE performed by a subcontracted crew. Those are where evidence goes missing. If your inspector is only reviewing the ITP after approval, you have already bought a weaker plan than the one you thought you specified.

Hold Points, Witness Points and What a Waiver Really Costs

A hold point is a genuine stop. The supplier cannot proceed past the operation without the inspector present or a written waiver. A witness point invites attendance and allows progress if the inspector does not arrive within the notified window. The distinction only means something if the notification period, usually five working days for a scheduled attendance, carries a consequence for failure to notify.

Waivers are normal and are not the problem. Undocumented waivers are. When a hold point is released by telephone under delivery pressure and nobody records it, the manufacturing record book contains a signature line for an operation nobody attended. Months later the certifying party, or the operator's own audit, asks how the PWHT thermocouple locations were verified, and there is no answer that survives the question.

The cost is asymmetric and it lands after shipment. A witnessed hydrostatic test costs one attendance. A hydrostatic test released on trust, disputed at commissioning, costs a valve pulled from a live line, a re-test, a shutdown extension and a claim nobody can substantiate. Discipline about waivers is the cheapest control on the entire order: write them down, number them, and reconcile them at release.

Codes and Client Specifications Governing Equipment Built Here

Eastern Province works produce a specific mix, and the code stack follows the product. Pipeline valves are built to API 6D; gate, globe and check valves to API 600, 602, 594 and 608 with pressure-boundary requirements from ASME B16.34 and flanges to B16.5 or B16.47. Wellheads, trees and their components fall under API 6A with its product specification levels. Pressure vessels follow ASME Section VIII Division 1 or 2, piping spools ASME B31.3, storage tanks API 650, and structural steel AWS D1.1.

Valve testing deserves separate attention because it is where release most often stalls. API 598 sets the shell, backseat and closure tests, and the required hold durations scale with size. A shell test held for the minimum on a large-bore valve, or a closure test performed with an uncalibrated gauge at the wrong range, produces a certificate that is technically invalid and practically indefensible.

Above the construction codes sit client documents: engineering standards, material system specifications, coating schedules, and for Saudi Aramco orders the typical inspection plans and inspection checklists that shape the ITP itself. Those documents, not the construction code, usually contain the requirement that catches a supplier out. Keeping every one of them, at the correct revision, tied to the purchase order line it governs is a records problem, and it is exactly what an inspection management system is built to solve.

Sour Service: Hardness, MR0175 and the Weld Procedure Trap

A large share of Eastern Province equipment is destined for sour service, and NACE MR0175 with ISO 15156 governs it. The requirement that bites is hardness: carbon and low alloy steel base metal, weld metal and heat affected zone must stay within the specified limit, commonly expressed as 22 HRC or the equivalent Vickers value, and it must be demonstrated on the material and the weld as manufactured, not on a generic coupon.

The trap is procedural rather than metallurgical. A welding procedure qualified without hardness traverse cannot support a sour-service claim, and neither can a production weld whose PWHT cycle differed from the qualified one. Suppliers who requalify consumables or change heat input mid-campaign without re-establishing hardness compliance create equipment that is compliant on paper and non-compliant in fact.

Practically, an inspector deployed for the campaign checks three things repeatedly: that the PQR supporting each production weld carries hardness data, that hardness testing on production items is done at the specified locations rather than the convenient ones, and that the hardness tester's calibration is current at the time of the test. Every one of those has been the subject of a nonconformance somewhere in this market, and every one is cheap to catch at the works.

Expediting: Inspection and Delivery Are the Same Conversation

Expediting and inspection are usually bought separately and should not be. The inspector standing at the works already knows whether the forgings arrived, whether the machining queue is realistic, and whether the coating booth is committed to another order. A separate expeditor calling from another country learns the same facts several weeks later and less accurately.

Effective expediting on a Dammam order starts at the sub-order level: which long-lead items are actually placed, with which sub-supplier, against which delivery, and whether the material certificates for those items are the type the purchase order demands. A promised delivery date that assumes a forging order not yet placed is the most common form of schedule fiction, and it is visible on the shop floor long before it appears in a progress report.

Reporting matters as much as observing. A useful expediting report names the operation, the quantity completed, the constraint, the recovery action and the revised date, and it does so on a fixed cadence the buyer can plan around. Where the schedule is genuinely at risk, that report is what lets a procurement team re-sequence rather than react. A short conversation about scope and cadence before mobilisation avoids most of the friction; that is what a consultation is for.

The Release Package a Buyer Can Actually Defend

Release is a documentation event. The manufacturing record book, sometimes called the MRB or the manufacturing data report, has to reconcile against the approved ITP line by line, and every hold and witness point must show either an attendance signature or a numbered waiver. Missing or mismatched entries are what stop equipment at the client's document review, often weeks after it left the works.

A defensible package carries, at minimum: the reconciled ITP; material test certificates of the type specified under EN 10204, cross-referenced to heat numbers; PMI records where alloy verification applies; welder and procedure qualification records mapped to joint numbers; NDE procedures, reports and technician certifications; PWHT charts with thermocouple maps; hardness records for sour service; pressure test records with gauge calibration; coating and dry film thickness reports; the nonconformance register with dispositions; and the signed inspection release note.

The second-order problem is quality of content rather than presence of documents. An NDE report that describes a technique different from the one the technician actually used will pass a completeness check and fail a technical one. Where a package must withstand an operator's or certifying authority's scrutiny, an independent technical read of the reports against the procedures is the control that catches it, which is the purpose of independent report validation.

How the Deployment Works for a Dammam Campaign

Atlantis inspection teams mobilise from Houston and Hyderabad to the client's site or to the supplier works, and once mobilised they remain deployed for the duration of the contract. For a Dammam vendor surveillance campaign that means a named inspector at the works through the manufacturing programme rather than a sequence of visiting inspectors, each of whom would arrive without the previous week's context.

Continuity is the operating advantage. The same inspector who attended the pre-inspection meeting knows which welders the supplier trusts on the difficult joints, how the PWHT furnace behaves on a full load, which sub-supplier is habitually late with certificates, and which clauses of the client specification this particular works reads differently. That knowledge is what turns the third occurrence of a problem into a one-hour conversation instead of a nonconformance.

Coverage extends across multiple works within a campaign where the purchase orders warrant it, with a fixed reporting cadence to the buyer and escalation direct to the procurement or quality lead. Scope, intervention points, reporting frequency and the release criteria are agreed before mobilisation. Where a buyer is also building a longer-term record of supplier performance across orders, structuring that data properly from the start is covered in the inspection data management guide.

Wellhead and Christmas tree equipment: the PMI scope buyers most often under-specify

Wellhead and Christmas tree equipment fabricated in the Dammam and Al-Khobar cluster is frequently ordered against an API 6A specification sheet that names the required material class and PSL level correctly, but the purchase order's inspection scope stops short of requiring positive material identification on the pressure-containing components themselves. The specification sheet states the requirement; it does not guarantee the inspection scope actually tests it, and those are two different documents written by two different people at two different stages of the order.

The exposure this creates is specific to sour service equipment. A wellhead body or a valve body specified in a sour-service-rated alloy but never PMI-verified at the works can reach location with a mill certificate claiming the correct material and no independent confirmation that the certificate matches the part — precisely the substitution risk API RP 578 exists to catch on plant piping, applied here to wellhead components where the consequence of a wrong-alloy body in sour service is materially worse.

A vendor surveillance scope for wellhead equipment should state PMI verification on pressure-containing components as an explicit hold point, witnessed and documented separately from the general dimensional and hydrostatic test inspection, rather than assumed as part of a general inspection visit that may not include it. A release package assembled without that hold point on record is exactly the gap a buyer's own incoming inspection is likely to find months later, at a point where re-inspection means opening equipment already installed rather than a supplier's works visit.

For sour-service PSL 3 and PSL 4 equipment specifically, the surveillance scope should also confirm that the shop's own PMI equipment carries current calibration certificates rather than relying on the fabricator's verbal assurance, since a handheld analyser drifting out of calibration produces readings that look plausible without being traceable, and traceability rather than plausibility is what a buyer's incoming audit will actually test. That distinction between a plausible reading and a traceable one is exactly what separates a defensible release package from one that only looks complete.

Request a consultation