Oil and gas supplier qualification: what does approval actually cover?

Topics: oil and gas supplier qualification; oilfield vendor approval; approved supplier scope; supplier qualification records.

A supplier that has delivered pump assemblies for years offers to repair one of them. Its vendor code is active, its bank details are verified and the buyer can create a purchase order. The missing question is whether its repair service falls within the approved scope.

Oil and gas supplier qualification needs a scope that the buyer can test against the proposed purchase. “Approved vendor” is too broad if it hides differences between supplying a product, carrying out a repair and performing work at a particular location.

Define the scope the buyer can use

Start with the contracting legal entity. Then identify the manufacturing or service location, category, approved activity, applicable restrictions, evidence references, approving authority and validity conditions. Where the organisation's policy requires asset or site-specific qualification, include that relationship explicitly.

Separate the commercial master from technical qualification. Tax identifiers, payment details and commercial registration make a supplier usable in the accounting process. They do not demonstrate that a particular activity has been assessed. Likewise, technical qualification does not itself approve the price or award.

Policy varies by purchaser and contract. Oil India publishes distinct procurement manuals for goods, services and works; they are an operator's policy resources, not a universal approval scheme for the sector. Oil India procurement manuals

The useful system question is therefore: “Which current decision allows this entity and location to provide this category under these conditions?” A green tick becomes meaningful only when the user can open the answer.

Record the roles in the supply chain too. An approved distributor may quote equipment made by another entity, while a repair business may subcontract part of the work. Link the contracting supplier, manufacturer and performing location where the purchasing policy requires them. Otherwise a buyer can select the right vendor code and still source from an unassessed location. Manufacturer approval should not be assumed to extend to every reseller or subcontractor.

Follow one supplier through a scope gap

Illustrative example. Delta Equipment Services is a fictional supplier with two locations. The buyer is considering a repair order for an assembly used at Asset West.

The buyer records the gap and seeks the required assessment. The supplier remains eligible for purchases within its existing approved scope unless an authorised decision changes that position. A missing repair approval should neither become automatic approval nor accidentally block unrelated, valid supply categories.

Suppose Delta changes the proposed repair location to Location 1. That still does not prove approval. The record covers new supply from that location, not necessarily repair. The buyer must compare the activity as well as the address.

If an urgent purchase requires an exception process, use the organisation's existing authority and record its scope, conditions and duration. A buyer editing a category field to make the workflow pass is not an exception process.

What evidence belongs in the register?

The register should point to the assessed evidence rather than become a large attachment folder. For each requirement, retain its source, applicable category, submitted version, reviewer disposition and any follow-up. Distinguish a document being present from its content being accepted.

For equipment specifications, separate technical, information and quality requirements where the adopted procurement framework does so. JIP33's document structure is a useful reference, but its suitability and adoption must be established for the purchase. IOGP JIP33 FAQ

For example, a supplier may submit a certificate that belongs to a different legal entity. The document exists and may be current, but it does not resolve the requirement until a qualified reviewer confirms its relevance. Record “entity mismatch” rather than “missing document”; the next action is different.

Not every approval has a simple annual expiry. Some depend on a periodic review, a particular contract, unchanged facilities or completion of an action. Model these conditions explicitly. A reminder engine cannot interpret an unwritten condition.

Recheck scope at the decision points defined by the procurement policy. An RFQ invitation, award and later order amendment may occur months apart. Store the result used at each point instead of assuming the status seen when the enquiry began is still current. For an existing order affected by a suspension, the procurement authority decides the treatment; the software should identify affected orders and retain that decision.

Handle changes without rewriting the past

When a supplier changes ownership, location, process or approved scope, retain the previous decision and open a new review. The sourcing record should still show which approval version was relied on at the time. Current eligibility and historical evidence answer different questions.

Performance records can initiate that review. Three late document submissions might justify investigating an information-delivery problem. They do not automatically establish that every technical capability is invalid. The procurement owner should distinguish an isolated transaction dispute, a category-specific concern and a broader issue requiring authorised suspension.

A practical exception queue includes expired evidence, conflicting entity details, changed supplying locations, overdue qualification actions and purchases outside the recorded scope. Each needs an owner and next decision. A single “supplier risk score” obscures these differences unless users can inspect the underlying reasons and authority.

Configure first, integrate when the gap is real

An ERP may already support category controls, blocks and approval workflows. Evaluate those before building a separate portal. A linked qualification register becomes useful when approvals involve several locations, document revisions or specialist reviews that the master record cannot represent clearly.

If systems are separate, decide which one owns qualification status and how the buyer sees stale or unavailable data. The integration should carry the approval reference and restrictions, not just a Boolean. When a status cannot be verified, follow the approved exception path instead of retaining yesterday's green tick indefinitely.

If document extraction is used, have the reviewer confirm the entity, location and dates against the original page. The recurring scope check can then compare those reviewed fields with the purchase, leaving new qualification decisions with procurement, engineering and quality.

Summary and next actions

A supplier becomes eligible for a purchase through a traceable scope decision. Making that scope visible protects the buyer from relying on an active vendor code that answers a different question.

1. Sample ten recent RFQs and identify the exact approval scope used for each.
2. Separate commercial registration, technical qualification and award authority in the data model.
3. Assign owners to scope gaps and changed evidence, preserving historical approval versions.
4. Use the bid-evaluation guide to carry the approved scope into quotation comparison.

A focused qualification-register review should begin with one supplier category and its current approval handover, rather than an organisation-wide supplier scoring project.