OdysseyGPT

Oil and gas package builders

Package vendor documentation in oil and gas: from the requisition to the record book, with every sub-vendor in between

For package engineers, proposal engineers and document controllers at builders of injection, metering, wellhead control and separation packages, and at makers of wellhead equipment.

By Ademola Afolabi, Founder, New Odyssey Ltd ยท Last reviewed:

The short answer

A package builder answers a requisition that points to dozens of specifications across mechanical, piping, electrical, instrument and painting disciplines, then passes those requirements to sub-vendors. After award the builder owes one document list, one inspection plan, one acceptance test and one record book that hold every sub-vendor's documents as well as its own.

Key Takeaways

  • A package requisition is read by discipline. One engineer rarely sees every specification that applies.
  • Sub-vendor deviations become your deviations. If they do not reach your list before award, you carry them.
  • The customer's document list names you. Half the documents on it are written by someone else.
  • OdysseyGPT checks documents against the customer's requirements. It is not a document control system and it does not read P&IDs.

Free sample: a quotation-vs-PO check. Send your quotation and the customer's purchase order. Get a list of what changed between them. Get the free result

How does a package builder answer a requisition?

A packaged unit is bought as one item with one tag, but it is specified like a small plant. The material requisition lists the scope and then points outward: to a package specification, to the operator's general specifications, and to a discipline specification for almost everything bolted to the frame. The proposal engineer's first job is to work out which of those documents apply to which part of the package, and who in the office or the supply chain has to read each one.

The layers of a package requisition and who reads them
LayerWhat it holdsWho has to read it
Material requisitionScope of supply, tag numbers, battery limits, the list of attached documents with revisions, and the document submission requirementsProposal engineer and document controller
Package specification and process datasheetDuty, design conditions, performance guarantees and what the package must containPackage or process engineer
Operator's general specificationsRules that apply to every supplier: units, tagging, quality system, documentation, preservation, spare partsProposal engineer and quality
Mechanical specificationsPumps, vessels, filters, exchangers and their codesMechanical engineer and the equipment sub-vendors
Piping and valve specificationsPiping classes, valve datasheets, welding, NDE and pressure testingPiping engineer and the valve and fittings suppliers
Electrical specificationsMotors, heaters, cables, junction boxes, earthing and hazardous area requirementsElectrical engineer and the panel builder
Instrumentation and control specificationsInstrument datasheets, tubing, control panels, the control system interface and any safety functionInstrument engineer and the instrument sub-vendors
Painting and insulation specificationsCoating systems for steel, piping and bought-out equipmentWhoever buys the paint, and every sub-vendor who paints their own item
Approved or recommended sub-vendor listWhich makes the customer accepts for each kind of itemPurchasing, before any sub-vendor is asked to quote

Three questions decide how well the offer holds up later. Which specification applies to bought-out items: the operator's, or the sub-vendor's standard? Does the sub-vendor list bind you, and what does it take to add a name? And which documents does the requisition list at a revision you were not actually sent? Each is cheap to ask before the bid and expensive to find after award.

Which standards come up for oil and gas packages?

Standards and programmes often named in package requisitions (own summary at name level; use the edition your contract names)
StandardWhat it isWhere it touches a package
API Spec Q1The American Petroleum Institute's quality management system specification for organisations that supply products to the petroleum and natural gas industryThe customer's quality clause may ask for a Q1 system or registration, from you and from named sub-vendors
API 6AAPI's specification for wellhead and tree equipmentIt applies where the scope includes wellhead or tree equipment, such as valves or chokes bought to it. Its ratings and classes differ from the piping classes on the rest of the skid
NACE MR0175 / ISO 15156Requirements for metallic materials exposed to H2S in oil and gas productionIt reaches every wetted part, including tubing, fittings and instrument parts that sub-vendors supply
NORSOK M-650A Norwegian petroleum industry standard for qualifying manufacturers of special materials such as duplex stainless steelThe mills, foundries and forges behind your pipe, fittings and valve bodies need a qualification the customer accepts
NORSOK standardsStandards developed by the Norwegian petroleum industry and published by Standards Norway, covering materials, piping, coating, documentation and moreThey are named on Norwegian shelf projects and on some projects elsewhere. NORSOK Z-018 covers supplier's documentation of equipment
IOGP JIP33Standardised procurement specifications from the International Association of Oil and Gas Producers, written as supplements to existing industry standardsEach one comes as a technical specification, a procurement datasheet, a quality requirements specification and an information requirements specification
ATEXThe European Union's rules for equipment used in potentially explosive atmospheres (Directive 2014/34/EU)Electrical and some mechanical items on the package need the right certificate and marking for the area classification
IECExThe IEC's international certification system for equipment used in explosive atmospheresProjects outside Europe often ask for it in place of ATEX, or for both

These documents do different jobs. API Q1 is about how your organisation works. API 6A and the JIP33 specifications are about a product. MR0175 and M-650 are about materials and who made them. ATEX and IECEx are about certification of individual items. A requisition can name all of them at once, and most of the evidence comes from sub-vendors. Most of these are paid documents. This page names them and does not reproduce their content.

Why are package deviation lists so long?

A single-item manufacturer answers one product specification. A package builder answers all of them, for items it does not make. Three things make the list grow.

  • Many disciplines. Each discipline engineer reads their own specifications and returns their own exceptions. Nobody reads the whole set, so the same point is raised twice in different words, and points that fall between disciplines are raised by no one.
  • Sub-vendor deviations flow up. The pump maker takes exception to the painting specification. The panel builder offers its standard cable glands. The instrument supplier cannot meet a material requirement on one wetted part. Each of these is now your deviation to the customer, in your numbering, against the customer's clause.
  • Conflicts between documents. The package specification says one thing and the general specification another. The instrument datasheet names a material the piping class does not allow. The requisition lists revision C of a specification and the package contains revision B.
  • Requirements written for a plant, applied to a skid. General specifications assume site construction. On a compact package some clauses cannot be met as written, such as access and spacing rules, and each needs a row.
  • Documentation requirements. The document list asks for items in a format, a language or a time frame that a sub-vendor will not meet for a small order.

The usual failure is timing. Sub-vendor offers arrive in the last days before the bid is due, and their exception lists are not read against the customer's clauses until after award. By then the price is fixed. The technical deviation list guide covers the format. After award, the Deviation Register (beta) keeps one list of what was agreed, including the rows that came from sub-vendors.

A conflict is a clarification, not a deviation

When two customer documents disagree, you are not deviating from either. Ask which governs, quote both passages, and state the assumption your price is based on. Most requisitions set an order of precedence, but it rarely settles a conflict between two documents at the same level.

Which documents does a package builder owe after award?

Package documentation after award, and where sub-vendors come in
DocumentWhat it doesThe sub-vendor problem
Document list (SDRL or VDRL)Lists every document you must submit, with its due date and whether the customer reviews it. See SDRL and VDRLThe customer's list has one line for instrument datasheets. Behind it sit documents from several suppliers, each with their own dates
Sub-vendor documentationDatasheets, drawings, certificates, manuals and test reports for every bought-out itemIt arrives in the supplier's own numbering and layout, and has to be given your number and the customer's before it can be submitted
Inspection and test plan (ITP)Sets out each inspection across structural, piping, mechanical, electrical and instrument work, and who attendsSub-vendors have their own ITPs. The customer's witness points have to appear in them, not only in yours
ProceduresWelding, NDE, pressure test, flushing, painting, FAT and preservation proceduresSome need customer approval before work starts, which puts the customer on your critical path
Factory acceptance test (FAT) of the assembled packageShows the package works as a unit: leak test, function test, instrument and control checks, as the procedure definesCertificates, calibration records and open non-conformances from sub-vendors have to be in hand before the customer travels
Manufacturing record book (MRB)The quality records, filed in discipline sections to the customer's index. See manufacturing record bookEach discipline section depends on sub-vendor records. One missing certificate holds the whole book
Hazardous area dossierThe certificates and declarations for each item installed in a classified area, where the customer asks for them as a setEvery certificate comes from a different manufacturer, and the model on the certificate has to match the item fitted
Preservation and packing recordsWhat was done to protect the package for shipment and storage, and what the site must keep doingSub-vendors set preservation rules for their own items, and those rules have to reach the package procedure

The pattern is the same on every line. The customer holds the package builder responsible, and the package builder is waiting on someone else. Good builders write their own document list to each sub-vendor at purchase order stage, with dates earlier than the customer's, and chase against it. The VDRL guide and the vendor document register template cover the register itself.

How does OdysseyGPT help?

OdysseyGPT reads documents and checks them against what the customer asked for. Every finding quotes the passage it rests on, and your engineers decide what to do with it. It works on text and tables: specifications, datasheets, registers, certificates, procedures and reports. It does not read P&IDs, general arrangement drawings or wiring diagrams.

Package documents and the OdysseyGPT tool that checks them
StagePackage documents you uploadToolWhat it reports
BidThe requisition's specifications, with your standard package specification or a sub-vendor's offer as the other sideDocument ReviewA compliance matrix and a draft deviations and clarifications list. Each row quotes the customer's clause and your document
BidThe package specification and the general and discipline specifications behind itCustomer Specification Review (beta)Technical, quality, documentation and test requirements listed with their source, plus items that are unclear or missing
BidYour requisition to sub-vendors and the offers that came backTechnical Bid Evaluation (beta)Each sub-vendor's answer to each requirement, with declared and undeclared deviations and draft clarification questions
Bid and afterThe project instrument or equipment datasheet and the sub-vendor's datasheetDatasheet Comparison (beta)Fields that differ, such as a wetted material, a range or a certification entry, and fields present on one sheet only
AwardThe customer's requirements, your offer and the clarification repliesDeviation Register (beta)One register of agreed, open and undeclared deviations, with duplicates merged
AwardThe SDRL or VDRL spreadsheet, the order's documentation clauses and your scheduleVDRL/MDR Tracker (beta)Overdue lines, lines with no clear due date, and documents the order requires that the list leaves out
Before manufactureThe customer's quality specification and the package ITPITP Validator (beta)Stages the ITP does not cover, intervention points set lower than the customer asked, and stages with no acceptance reference
Goods receiptMaterial certificates from sub-vendors and the purchase requirementsMaterial Certificate Review (beta)Wrong certificate type, results outside the stated requirement, and required tests the certificate does not show
Before the FATThe FAT procedure, ITP, calibration evidence, non-conformance register and punch listFAT Readiness Check (beta)Blockers such as an open non-conformance or a missing witness notice, listed apart from review items
Record bookThe customer's MRB instructions or index and your documentation folderMRB Readiness Check (beta)Each required section and document marked present, missing, awaiting approval, wrong revision or incomplete
Record bookThe compiled record book, tag list and ITPMRB Traceability Verification (beta)Broken links from tag to part to heat to certificate, and from test to instrument to calibration
Record bookThe customer's index template and the approved documentsMRB Compiler (beta)A manifest in index order, with index entries that have no document and documents that fit no entry

The same checks apply one level down. A sub-vendor's offer can be read against the clauses you passed to them, and a sub-vendor's data book can be read against the index you gave them. That is where most package findings come from, because it is the reading that gets skipped when the bid or the FAT date is close.

What does a result look like for a package?

The example below is invented. The package, tag numbers, sub-vendors, document numbers and dates come from no real project. It shows the shape of the findings and nothing else.

Invented example: documents for a chemical injection package checked against the customer's requisition before the FAT
IDFindingWhy it was raisedCategorySeverityConfidence
F-SDR-01Hazardous area certificate dossier is required by the order and has no line in the SDRLThe requisition's documentation clause lists a dossier of certificates for all equipment in classified areas. No row of the SDRL spreadsheet carries that title or a matching document code.Missing deliverableHighHigh
F-SDR-02Sub-vendor data book for injection pumps P-4101A/B is overdueThe SDRL rule is submission four weeks before the FAT. The schedule gives the FAT as 2026-06-15 and the line has no revision recorded.Overdue documentHighHigh
F-DS-01Sub-vendor datasheet for pressure transmitter PT-4107 gives a different diaphragm materialThe project instrument datasheet states Alloy C-276 for the diaphragm. The sub-vendor datasheet states 316L stainless steel in the same field.Value mismatchCriticalHigh
F-DS-02Certification entry for level transmitter LT-4103 omits IECExThe project datasheet asks for ATEX and IECEx certification. The sub-vendor datasheet lists an ATEX certificate number only.Missing field valueHighMedium
F-DEV-01Pump sub-vendor's exception to the painting specification is not on the package deviation listThe sub-vendor's offer states its standard coating system will be applied. The deviation list sent to the customer has no row against the painting specification for bought-out equipment.Undeclared deviationHighMedium
F-MTC-01Certificate for instrument tubing does not report hardnessThe purchase requirement calls for material suitable for sour service with hardness reported. The certificate for heat 7TQ218 gives chemistry and tensile results and no hardness value.Missing test resultHighHigh
F-ITP-01Package ITP shows the control panel function test as a review pointThe customer's quality specification marks the function test of the local control panel as a witness point with ten working days' notice.Downgraded inspection pointMediumHigh
F-FAT-01Non-conformance NCR-031 on relief valve PSV-4102 is still openThe register shows NCR-031 as open with no disposition. The FAT procedure requires all non-conformances on tested items to be closed or accepted by the customer before the test.Open NCRCriticalHigh
F-MRB-01Electrical section of the record book holds no certificate for junction box JB-4105The customer's MRB index requires a hazardous area certificate for each junction box on the tag list. Certificates are filed for JB-4101 to JB-4104 only.Missing documentHighHigh
F-MRB-02Sub-vendor ITP for the calibration pot is filed at a superseded revisionThe document register records revision 3 as approved by the customer. The copy in the mechanical section is revision 1.Wrong revisionMediumHigh

Each row carries the document name, the page or cell and the quoted words, so the engineer can check it in a minute. Some rows will be filing errors and some will be real. On a package, both kinds stop a FAT or a record book from being accepted, so both are worth knowing about a month early.

Where OdysseyGPT falls short

  • It does not read P&IDs, general arrangement drawings, isometrics, wiring diagrams or loop diagrams. A requirement that exists only on a drawing will not be found.
  • It does no process, mechanical, structural or electrical design, and it does not size anything.
  • It is not a document control system. It does not number documents, issue transmittals, hold the master copy or connect to the customer's portal. Your document controller and your existing system still do that. See DocBoss alternatives for where each kind of tool fits.
  • It does not judge whether a hazardous area certificate is valid for the area classification. It reports whether the document is there and whether the entries it can read match what the customer's documents say.
  • It does not assess a sub-vendor's quality system or a manufacturer's qualification. It can report that the evidence the customer asked for is missing from the set.
  • It only knows the documents you upload. If a discipline specification listed in the requisition is not in the set, its requirements are missed. The requisition's document list is the first thing to check.
  • Poor scans of sub-vendor documents may not be read correctly. Check any finding on them against the page itself.
  • A fair test is a package you have already delivered. Run its requisition and record book through a review and compare the findings with the punch list you remember.

Which tools are available now

Document Review is generally available. The other tools on this page are in beta: you request access and we onboard each team ourselves. See OdysseyGPT for manufacturing and the order module.

Try it on your own documents

Free sample: a quotation-vs-PO check

Send your quotation and the customer's purchase order. Get a list of what changed between them.

Get the free result

Buyer questions

20 questions bid engineers, proposal engineers and buyers ask. Last reviewed:

What are the documentation requirements for a skid package?

The customer's document list sets them. It normally covers datasheets, drawings and calculations, procedures, an inspection and test plan, sub-vendor documentation, a factory acceptance test procedure and report, a manufacturing record book in discipline sections, certificates for equipment in hazardous areas, manuals, and preservation and packing records. Read the purchase order text as well, because it can require documents the list does not show.

What is package vendor documentation in oil and gas?

It is everything a package builder submits to the customer to show what was designed, bought, built and tested. It differs from single-item documentation in one way: much of it is written by sub-vendors. The builder collects it, checks it against the customer's requirements, gives it project numbering and submits it under its own name, and is held responsible for all of it.

What does a package requisition contain?

A material requisition with the scope and tag numbers, a package specification and process datasheet, the operator's general specifications, and discipline specifications for mechanical, piping, electrical, instrumentation and painting work. It usually adds a quality specification, a document list and a list of accepted sub-vendors. Check that every document the requisition lists was actually sent, at the revision stated.

How do package builders control sub-vendor documents?

They issue each sub-vendor a document list with the purchase order. It names the documents, the format and dates earlier than the customer's. Incoming documents are checked against the requirement, renumbered and logged before submission. The weak points are a list that was never issued and dates with no margin. A document control system holds the register. Checking the content is separate work.

Is an SDRL different from a VDRL?

In purpose, no. Both are the customer's schedule of documents a supplier must submit, with codes, due dates and review requirements. The name depends on the customer. See SDRL and VDRL. What matters for a package is that each line is matched to the sub-vendor who will fill it, before the order is placed.

Why is a package deviation list longer than an equipment one?

Because the builder answers every discipline specification, for items it does not make. Each sub-vendor returns exceptions to the clauses passed down, and each becomes the builder's deviation to the customer. Customer documents also conflict with one another across disciplines. And general specifications written for a plant contain clauses that a compact skid cannot meet as written, so each needs a row.

What should we do with deviations raised by sub-vendors?

Read each one against the customer's clause before the bid goes in. Then decide: reject it and hold the sub-vendor to the requirement, absorb it by changing the scope, or carry it to the customer on your own deviation list. A sub-vendor exception that stays in the sub-vendor's offer and never reaches your list becomes your cost after award.

What if two customer specifications contradict each other?

Raise a clarification, not a deviation. Quote both passages, say which you have assumed governs and state that the price rests on that assumption. The contract's order of precedence may settle it, but it often does not help when both documents sit at the same level, such as an instrument datasheet and a piping class.

Does the customer's sub-vendor list bind us?

Read the wording. Some lists are mandatory, some are recommendations, and most give a route for proposing another make. If your usual supplier is not on a mandatory list, declare it before award and ask what approval needs. Substituting a sub-vendor after award without agreement is a common cause of rejected documents and late packages.

Does a package builder need API Q1?

Only if the contract says so. API Spec Q1 is a quality management system specification, and customers name it in their quality requirements. Check whether the clause accepts ISO 9001 as an alternative, and whether it asks for Q1 evidence from your sub-vendors too. If you hold ISO 9001 and the clause says Q1 only, declare that as a deviation.

When does API 6A apply to a package?

When the scope includes wellhead or tree equipment that the requisition asks to be supplied to it. API 6A uses its own pressure ratings, temperature classes, material classes and product specification levels, which differ from the piping classes on the rest of the skid. State clearly in your offer which items are to API 6A and which are not.

How does sour service affect a package?

It reaches every wetted part, not only the vessels and pipe. Instrument diaphragms, tubing, fittings, valve trim and bolting all come from sub-vendors, and each needs material and certificates that meet NACE MR0175 / ISO 15156 as the customer applies it. Pass the requirement down in every purchase order and check what comes back. An engineer still judges compliance.

What does NORSOK M-650 mean for a package builder?

NORSOK M-650 is about who made the material. Where the contract names it, the mills, foundries and forges behind your duplex or similar alloy pipe, fittings and valve bodies need a qualification that covers the grade and product form. Ask sub-vendors for the original manufacturer and its qualification evidence at enquiry stage, before material is bought.

Which hazardous area documents does a package need?

The customer's specification decides. Projects commonly ask for ATEX or IECEx certificates, or both, for each item installed in a classified area, collected in one dossier with a register by tag. Every certificate comes from a different manufacturer. The usual gaps are a missing certificate and a certificate for a different model from the one fitted.

How is an ITP written for a multi-discipline package?

It covers structural, piping, mechanical, electrical and instrument work, then the assembled package: pressure or leak test, function test, coating, and preservation. Each stage gives the acceptance reference and who holds, witnesses or reviews. Sub-vendor inspection plans sit beneath it, and the customer's witness points must appear in those too. See the ITP Validator (beta).

What has to be ready before a package FAT?

An approved test procedure, the witness notice sent on time, calibration certificates valid on the test date, sub-vendor certificates and test reports in hand, and non-conformances closed or accepted by the customer. The punch list should be short and agreed. A package can fail its acceptance test on missing sub-vendor paperwork even when the equipment itself works.

How is a package manufacturing record book organised?

To the customer's index, normally in discipline sections: structural, piping, mechanical equipment, electrical, instrumentation, coating, testing and release. Each section mixes the builder's own records with sub-vendor data books. See manufacturing record book. Build the index at the start and file records as they arrive. A book assembled after the test always has gaps.

Does OdysseyGPT replace a document control system?

No. It does not number documents, issue transmittals, hold master copies or connect to a customer's portal. It reads documents and registers and reports where they differ from the customer's requirements, quoting the source for each finding. The VDRL/MDR Tracker (beta) checks your document list against the order's clauses and dates. Your document controller still makes every submission.

Can OdysseyGPT read P&IDs, GA drawings or wiring diagrams?

No. It reads text and tables in PDF, Word, Excel and CSV files: specifications, datasheets, registers, certificates, procedures and reports. A requirement that exists only on a drawing will not be found. It also does no process or mechanical design. Engineers review every finding and decide what to do with it.

How does OdysseyGPT check sub-vendor offers?

Technical Bid Evaluation (beta) reads the requirements you passed down and each sub-vendor's offer. It reports each supplier's answer to each requirement, with declared and undeclared deviations and draft clarification questions, all quoted from the offers. Document Review does a two-way check of one offer against one specification package. Your engineers decide which findings stand.

Frequently asked questions

What documentation does a skid package vendor have to supply?

Whatever the customer's document list requires. It usually covers datasheets, drawings and calculations, procedures, an inspection and test plan, sub-vendor documentation, a factory acceptance test procedure and report, a manufacturing record book in discipline sections, hazardous area certificates, manuals, and preservation and packing records.

Who is responsible for sub-vendor documents on a package?

The package builder. The customer's contract is with the builder, so a late or wrong sub-vendor document is the builder's late or wrong document. That is why builders issue their own document list to each sub-vendor with earlier dates.

Is OdysseyGPT a document control system for package vendors?

No. It does not number, transmit or store controlled documents. It reads the documents and registers you already have and reports where they differ from the customer's requirements, with a quote for each finding.

Can OdysseyGPT read the P&ID for a package?

No. It reads text and tables in PDF, Word, Excel and CSV files. Give it the specifications, datasheets, registers, certificates and reports. Drawings are outside what it checks.

References

API Monogram and APIQR programmes

American Petroleum Institute

What API Spec Q1 is and how it relates to the Monogram Program.

Visit source

API Specification 6A, 21st Edition

American Petroleum Institute

Publisher's announcement for the wellhead and tree equipment specification. The specification is a paid document.

Visit source

NORSOK M-650: Qualification of manufacturers of special materials

Standards Norway

Scope and purpose as described by the publisher.

Visit source

JIP33 frequently asked questions

IOGP

The four documents in a JIP33 specification and how they relate to parent standards.

Visit source

Directive 2014/34/EU (ATEX)

EUR-Lex

Equipment and protective systems intended for use in potentially explosive atmospheres.

Visit source

IECEx frequently asked questions

IECEx

What the IECEx system is and how it differs from ATEX.

Visit source

NACE MR0175 / ISO 15156 and NORSOK Z-018

AMPP, ISO and Standards Norway

Paid standards, named here by title and subject only.

Related Pages

Module

Order & Document Control

The module hub: its tools, what they read and the free result.

Standards

API 6A wellhead and tree equipment

The designations a purchaser specifies, and a requisition checklist.

Standards

API Spec Q1 explained

The quality system specification and what customers ask suppliers to show.

Standards

NACE MR0175 / ISO 15156

Sour service material requirements and what to check.

Glossary

Supplier document requirements list (SDRL)

The customer's document list, and the one you issue to sub-vendors.

Glossary

NORSOK M-650

Qualification of manufacturers of special materials.

Glossary

API Monogram

What the mark on a product means and what it does not.

Glossary

Skid package

Equipment, piping and instruments on one frame, with one dossier.

Product

VDRL/MDR Tracker (beta)

Your document list checked against the order's documentation clauses and dates.

Product

Document Review

A requisition's specifications checked against your documents, in both directions.

Product

Technical Bid Evaluation (beta)

Sub-vendor offers compared against the requirements you passed down.

Product

MRB Readiness Check (beta)

The record book folder checked against the customer's index.

Template

Sour service material checklist template

A checklist for wetted parts, hardness and certificates.

Template

MRB index template

A record book index layout to adapt to the customer's.

Industry

Steel fabricators and skid builders

The structural records for the frame under the package.

Industry

Pressure vessel manufacturers

The vessel records that arrive as a sub-vendor data book.

Pillar guide

Technical deviation list guide

The deviations you agree at bid stage are the ones you verify and record later.

Industry

OdysseyGPT for manufacturing

Cited document checks for engineered-equipment manufacturers, from tender to handover.