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.
| Layer | What it holds | Who has to read it |
|---|---|---|
| Material requisition | Scope of supply, tag numbers, battery limits, the list of attached documents with revisions, and the document submission requirements | Proposal engineer and document controller |
| Package specification and process datasheet | Duty, design conditions, performance guarantees and what the package must contain | Package or process engineer |
| Operator's general specifications | Rules that apply to every supplier: units, tagging, quality system, documentation, preservation, spare parts | Proposal engineer and quality |
| Mechanical specifications | Pumps, vessels, filters, exchangers and their codes | Mechanical engineer and the equipment sub-vendors |
| Piping and valve specifications | Piping classes, valve datasheets, welding, NDE and pressure testing | Piping engineer and the valve and fittings suppliers |
| Electrical specifications | Motors, heaters, cables, junction boxes, earthing and hazardous area requirements | Electrical engineer and the panel builder |
| Instrumentation and control specifications | Instrument datasheets, tubing, control panels, the control system interface and any safety function | Instrument engineer and the instrument sub-vendors |
| Painting and insulation specifications | Coating systems for steel, piping and bought-out equipment | Whoever buys the paint, and every sub-vendor who paints their own item |
| Approved or recommended sub-vendor list | Which makes the customer accepts for each kind of item | Purchasing, 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?
| Standard | What it is | Where it touches a package |
|---|---|---|
| API Spec Q1 | The American Petroleum Institute's quality management system specification for organisations that supply products to the petroleum and natural gas industry | The customer's quality clause may ask for a Q1 system or registration, from you and from named sub-vendors |
| API 6A | API's specification for wellhead and tree equipment | It 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 15156 | Requirements for metallic materials exposed to H2S in oil and gas production | It reaches every wetted part, including tubing, fittings and instrument parts that sub-vendors supply |
| NORSOK M-650 | A Norwegian petroleum industry standard for qualifying manufacturers of special materials such as duplex stainless steel | The mills, foundries and forges behind your pipe, fittings and valve bodies need a qualification the customer accepts |
| NORSOK standards | Standards developed by the Norwegian petroleum industry and published by Standards Norway, covering materials, piping, coating, documentation and more | They are named on Norwegian shelf projects and on some projects elsewhere. NORSOK Z-018 covers supplier's documentation of equipment |
| IOGP JIP33 | Standardised procurement specifications from the International Association of Oil and Gas Producers, written as supplements to existing industry standards | Each one comes as a technical specification, a procurement datasheet, a quality requirements specification and an information requirements specification |
| ATEX | The 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 |
| IECEx | The IEC's international certification system for equipment used in explosive atmospheres | Projects 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?
| Document | What it does | The 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 VDRL | The customer's list has one line for instrument datasheets. Behind it sit documents from several suppliers, each with their own dates |
| Sub-vendor documentation | Datasheets, drawings, certificates, manuals and test reports for every bought-out item | It 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 attends | Sub-vendors have their own ITPs. The customer's witness points have to appear in them, not only in yours |
| Procedures | Welding, NDE, pressure test, flushing, painting, FAT and preservation procedures | Some need customer approval before work starts, which puts the customer on your critical path |
| Factory acceptance test (FAT) of the assembled package | Shows the package works as a unit: leak test, function test, instrument and control checks, as the procedure defines | Certificates, 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 book | Each discipline section depends on sub-vendor records. One missing certificate holds the whole book |
| Hazardous area dossier | The certificates and declarations for each item installed in a classified area, where the customer asks for them as a set | Every certificate comes from a different manufacturer, and the model on the certificate has to match the item fitted |
| Preservation and packing records | What was done to protect the package for shipment and storage, and what the site must keep doing | Sub-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.
| Stage | Package documents you upload | Tool | What it reports |
|---|---|---|---|
| Bid | The requisition's specifications, with your standard package specification or a sub-vendor's offer as the other side | Document Review | A compliance matrix and a draft deviations and clarifications list. Each row quotes the customer's clause and your document |
| Bid | The package specification and the general and discipline specifications behind it | Customer Specification Review (beta) | Technical, quality, documentation and test requirements listed with their source, plus items that are unclear or missing |
| Bid | Your requisition to sub-vendors and the offers that came back | Technical Bid Evaluation (beta) | Each sub-vendor's answer to each requirement, with declared and undeclared deviations and draft clarification questions |
| Bid and after | The project instrument or equipment datasheet and the sub-vendor's datasheet | Datasheet Comparison (beta) | Fields that differ, such as a wetted material, a range or a certification entry, and fields present on one sheet only |
| Award | The customer's requirements, your offer and the clarification replies | Deviation Register (beta) | One register of agreed, open and undeclared deviations, with duplicates merged |
| Award | The SDRL or VDRL spreadsheet, the order's documentation clauses and your schedule | VDRL/MDR Tracker (beta) | Overdue lines, lines with no clear due date, and documents the order requires that the list leaves out |
| Before manufacture | The customer's quality specification and the package ITP | ITP Validator (beta) | Stages the ITP does not cover, intervention points set lower than the customer asked, and stages with no acceptance reference |
| Goods receipt | Material certificates from sub-vendors and the purchase requirements | Material Certificate Review (beta) | Wrong certificate type, results outside the stated requirement, and required tests the certificate does not show |
| Before the FAT | The FAT procedure, ITP, calibration evidence, non-conformance register and punch list | FAT Readiness Check (beta) | Blockers such as an open non-conformance or a missing witness notice, listed apart from review items |
| Record book | The customer's MRB instructions or index and your documentation folder | MRB Readiness Check (beta) | Each required section and document marked present, missing, awaiting approval, wrong revision or incomplete |
| Record book | The compiled record book, tag list and ITP | MRB Traceability Verification (beta) | Broken links from tag to part to heat to certificate, and from test to instrument to calibration |
| Record book | The customer's index template and the approved documents | MRB 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.
| ID | Finding | Why it was raised | Category | Severity | Confidence |
|---|---|---|---|---|---|
| F-SDR-01 | Hazardous area certificate dossier is required by the order and has no line in the SDRL | The 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 deliverable | High | High |
| F-SDR-02 | Sub-vendor data book for injection pumps P-4101A/B is overdue | The 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 document | High | High |
| F-DS-01 | Sub-vendor datasheet for pressure transmitter PT-4107 gives a different diaphragm material | The project instrument datasheet states Alloy C-276 for the diaphragm. The sub-vendor datasheet states 316L stainless steel in the same field. | Value mismatch | Critical | High |
| F-DS-02 | Certification entry for level transmitter LT-4103 omits IECEx | The project datasheet asks for ATEX and IECEx certification. The sub-vendor datasheet lists an ATEX certificate number only. | Missing field value | High | Medium |
| F-DEV-01 | Pump sub-vendor's exception to the painting specification is not on the package deviation list | The 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 deviation | High | Medium |
| F-MTC-01 | Certificate for instrument tubing does not report hardness | The 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 result | High | High |
| F-ITP-01 | Package ITP shows the control panel function test as a review point | The customer's quality specification marks the function test of the local control panel as a witness point with ten working days' notice. | Downgraded inspection point | Medium | High |
| F-FAT-01 | Non-conformance NCR-031 on relief valve PSV-4102 is still open | The 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 NCR | Critical | High |
| F-MRB-01 | Electrical section of the record book holds no certificate for junction box JB-4105 | The 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 document | High | High |
| F-MRB-02 | Sub-vendor ITP for the calibration pot is filed at a superseded revision | The document register records revision 3 as approved by the customer. The copy in the mechanical section is revision 1. | Wrong revision | Medium | High |
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.
