Standards explainer

NORSOK L-001 and IOGP S-562 (JIP33) datasheet review: handling vendor deviations

What NORSOK L-001 and the JIP33 ball valve specification are, why JIP33 changes how valve tenders are written, what to check in your datasheet, and how to record deviations against a JIP33-based specification.

By Ademola Afolabi, Founder, New Odyssey Ltd · Last reviewed:

The short answer

NORSOK L-001 is the Norwegian petroleum industry standard for piping and valves. IOGP S-562 is the JIP33 specification that adds common purchaser requirements to API 6D for ball valves. Check your datasheet against the API standard, the S-562 documents and the project's data sheet, and record each gap against the document it comes from.

Key Takeaways

  • NORSOK L-001 (Piping and valves) is published by Standards Norway; the current edition is Edition 4, January 2017.
  • JIP33 specifications build on an industry standard. S-562 builds on API 6D for ball valves.
  • A JIP33 set has four documents: the supplementary specification, a procurement data sheet, an information requirements specification and a quality requirements specification.
  • Record each deviation against the layer it comes from: the API standard, the JIP33 specification, the purchaser's data sheet selections or the project's own additions.

What NORSOK L-001 covers

NORSOK standards are written by the Norwegian petroleum industry and published by Standards Norway (Standard Norge). NORSOK L-001 is titled "Piping and valves". Standards Norway lists Edition 4, published 1 January 2017, as current, and the 1999 edition as withdrawn (Standard Norge). Other NORSOK standards depend on it: NORSOK M-630, the material data sheets for piping, applies to piping selected according to L-001.

For a valve maker, L-001 usually reaches you through the piping class or valve reference the tender quotes, and through the NORSOK material and coating standards it brings with it. Read the requisition for the edition it names: a tender written against an older edition can refer to sheets or codes that have changed.

What JIP33 and IOGP S-562 are

JIP33 is a joint industry programme run by IOGP, the International Association of Oil & Gas Producers. IOGP started it in 2016 in response to project cost and schedule overruns of more than 40%. Its aim is to standardise procurement specifications so that operators stop issuing a different set of extra requirements on every project. Each JIP33 specification builds on an existing industry standard, and all of them are free to download (JIP33).

The four documents in a JIP33 specification set (own summary of the JIP33 description)
DocumentWhat it holdsWhat it means for your offer
Supplementary specification (technical requirements specification)Requirements that add to, or modify, the industry standardThe technical requirements you check clause by clause, on top of the API standard
Procurement data sheetThe purchaser's selected options and project-specific detailsThe values for this order: the options the purchaser picked
Information requirements specificationDocuments and data the supplier must deliverYour document list and submission dates
Quality requirements specificationQuality management requirements and the purchaser's involvement in inspection and testingHold and witness points, inspection levels and their cost

IOGP S-562 is the JIP33 specification for ball valves to API Specification 6D. The revision issued for public review in December 2024 follows API 6D 25th Edition (November 2021) with Addendum 2 (September 2024). It has the four documents above. It also has a version of the technical requirements with the reasoning behind each requirement (JIP33). The four documents, together with the purchase order, make up the technical specification. See API 6D explained for the base standard.

Why JIP33 matters for valve buyers and suppliers

  • Fewer one-off requirements: when operators adopt the same supplementary specification, a supplier can qualify a design and its documents once and reuse that work across customers.
  • A clear place for the purchaser's choices: options sit in the procurement data sheet, so the technical requirements stay the same from order to order.
  • Documents and quality are separate: the information and quality requirements are their own documents, so your document list and inspection costs can be priced from them directly.
  • The reasoning is published: the version with justifications explains why a requirement exists, which helps you judge whether a deviation is likely to be accepted.
  • It is still not the whole tender: the project specification, the owner's own standards and the requisition can add to or override a JIP33 set. Check the order of precedence.

What to check in a vendor datasheet against a JIP33-based specification

Datasheet checks for a ball valve offered against API 6D, IOGP S-562 and a project data sheet
CheckQuestion to answerWhere the requirement usually sits
Documents and revisionsWhich API 6D edition and addenda, and which S-562 revision, does the tender name? Do they match each other?Requisition, project specification
Order of precedenceDoes the project specification or an owner standard override the JIP33 set anywhere?Requisition, project specification
Purchaser selectionsHave you answered every option on the procurement data sheet, and does each answer match your design?Procurement data sheet
Valve designMounting, seat arrangement, bore, ends and operator offered against what is selectedAPI 6D, data sheet
MaterialsBody, trim, seats, bolting and sour-service requirements against your material listsSupplementary specification, data sheet, NORSOK or owner material standards
TestingPressure tests, any supplementary tests and fugitive-emission tests such as ISO 15848-1API 6D, supplementary specification
Inspection and witness pointsWhich tests the purchaser witnesses or reviews, and at what inspection levelQuality requirements specification
CertificatesInspection document type for each part, such as EN 10204 3.1 or 3.2Supplementary specification, quality requirements
DocumentsEach document and data item, its format and when it is dueInformation requirements specification

Our datasheet vs specification checklist covers the remaining checks in order, and the compliance matrix template gives you one row per requirement to work through.

How to record deviations against a JIP33-based specification

Write the deviation list the usual way, one row per gap with the clause, requirement, offer, justification and cost of withdrawal. Then add one column: the document layer the requirement comes from. A buyer reviewing an offer against a JIP33 set wants to know straight away where each deviation sits. Is it against the industry standard, the common JIP33 requirements, a selection they made on the data sheet, or a project addition? These lead to different conversations.

Illustrative rows against an invented JIP33-style package, PS-VAL-001 (fictional; not IOGP or NORSOK text)
LayerClauseRequirementOfferedStatusJustificationCost of withdrawal
Base standardPS-VAL-001-TRS §3.1Valve to API 6D, edition stated in the requisitionAPI 6D, edition as requestedCompliesNoneNot applicable
Supplementary specificationPS-VAL-001-TRS §6.4Additional low-pressure gas seat testLiquid seat test onlyDeviationGas test rig not available for this sizeThird-party gas test: +3%, +2 weeks
Data sheet selectionPS-VAL-001-PDS line 14Purchaser selected the seat arrangement shown on the data sheetStandard seat arrangementDeviationSelected arrangement not qualified on this sizeRequalification: +5%, +6 weeks
Quality requirementsPS-VAL-001-QRS §2.2Purchaser witnesses hydrostatic shell testShell test witnessed; seat test by review of recordsClarificationConfirm whether seat test witnessing is requiredNo cost
Information requirementsPS-VAL-001-IRS item 9Fugitive-emission type-test report with the offerReport supplied after orderClarificationReport available; confirm timingNo cost
  1. Quote the exact document and line, including the data sheet line, not just the clause of the base standard.
  2. Where a JIP33 requirement is stricter than the API standard, say which one you meet. "Complies with API 6D" does not answer a supplementary requirement.
  3. Use the published justification to frame your case: if your design meets the purpose behind a requirement, say how.
  4. Keep one list per package. Start from the technical deviation list template, and read the technical deviation list guide for the full format.

Find every requirement before you start

Requirements for one valve can sit in five or more documents. Paste a section of the specification into the free spec requirement extractor to list the clauses and the standards it calls up, such as NORSOK L-001 and API 6D, in your browser. When the package is evaluated, the buyer will use something like the technical bid evaluation template; it helps to see your offer the way they will.

OdysseyGPT reads the whole package, including the data sheet and the quality and information requirements, and drafts a compliance matrix and deviation list with a source quote for every row. An engineer checks and decides each one. See OdysseyGPT for manufacturing and valve manufacturers.

Answering a JIP33-based valve tender?

Bring one past tender package to a demo and see the cited deviation list OdysseyGPT drafts from it. Managed plans are from $999/month.

Request a demo

Buyer questions

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

What does NORSOK L-001 cover?

NORSOK L-001 is the Norwegian petroleum industry standard for piping and valves. For a valve maker, it usually arrives through the piping class or valve reference quoted in the tender, and through the NORSOK material and coating standards that come with it. Standards Norway lists Edition 4, January 2017, as current. Check which edition your tender names.

Who publishes NORSOK standards?

Standards Norway (Standard Norge) publishes them. The Norwegian petroleum industry writes them, to set common requirements for oil and gas facilities on the Norwegian continental shelf. Operators elsewhere also call them up. You buy NORSOK standards from Standards Norway, so make sure your bid team has the edition the tender names before you check your datasheets against it.

What is JIP33?

JIP33 is a joint industry programme run by IOGP, the International Association of Oil & Gas Producers. It started in 2016 to cut project cost and schedule overruns by standardising procurement specifications. Each JIP33 specification builds on an existing industry standard, such as API 6D, and adds a common set of purchaser requirements. All of them are free to download.

What are the four documents in a JIP33 specification?

Each JIP33 set has a supplementary specification with the technical requirements, a procurement data sheet with the purchaser's choices, an information requirements specification listing the documents to supply, and a quality requirements specification for inspection and quality. Together with the purchase order, they make up the technical specification. Check all four, not just the technical one.

What is a JIP33 procurement data sheet?

It is where the purchaser records options and project details for the order, such as design choices and service conditions. The technical requirements stay the same across orders, while the data sheet changes. Answer every line on it and compare each answer with your design. A selection your design does not meet is a deviation against that data sheet line.

What is a JIP33 information requirements specification?

It lists the documents and data the supplier must deliver, with their format and timing. In other words, it does the job of a vendor data requirements list. Price every item, because documents take engineering time, and check that your due dates match it. See the VDRL guide for how document lists are usually handled.

What is a JIP33 quality requirements specification?

It sets the quality management requirements and how far the purchaser takes part in inspection and testing, such as hold, witness and review points. The level chosen affects your cost and schedule, because each witnessed step needs planning and an inspector. Price the level asked and reflect it in your inspection and test plan.

How does a JIP33 supplementary specification relate to the base standard?

It adds to or changes the base standard, clause by clause, without repeating it. So you need both documents side by side to know the full requirement. A design that complies with API 6D may still miss a supplementary requirement. Check every supplementary clause and say plainly in your offer which ones you meet and which you do not.

Why read the JIP33 version with justifications?

Because it explains why each requirement exists. When your design differs, you can show how it still meets the purpose behind the requirement. That makes a deviation easier for the buyer to accept, or tells you early that it will not be accepted. Use the reasoning in your justification column, in your own words.

Which revision of IOGP S-562 should my offer state?

State the revision the tender names, and the API 6D edition and addenda it is based on. JIP33 specifications are revised, and a tender may reference an older or newer issue than the one your team has read. Check the JIP33 specification library for the current issue. If the tender does not name a revision, raise a clarification.

Do operators still add project requirements on top of JIP33?

Often, yes. The project specification, the owner's own standards and the requisition can add to or override a JIP33 set. Check the order of precedence in the tender so you know which document wins when two disagree. Treat every project addition as its own requirement row, because it is where many unexpected deviations hide.

What if the JIP33 set and the project specification disagree?

Follow the order of precedence the tender sets. If it does not set one, or the conflict is still unclear, raise a technical query before you price. Write down which document you followed in your offer. Do not quietly pick the cheaper option. See governing-document precedence for how precedence usually works.

What are common deviations against JIP33 ball valve specifications?

Typical gaps are supplementary tests your rig cannot run, data sheet selections your design is not qualified for, and witness points you did not price. Document timing and format often differ from the information requirements too. Material and certificate requirements beyond API 6D are another frequent source. Record each one against the document layer it comes from.

How should I record a deviation in a JIP33-based tender?

Use your normal deviation list, with one row per gap, and add a column for the document layer: base standard, supplementary specification, data sheet selection, information requirements, quality requirements or project addition. Quote the exact document and line. Buyers want to see at once where each deviation sits, because each layer leads to a different conversation.

What should I check first in a NORSOK valve tender?

Start with the editions named, the order of precedence and the piping class or valve references for each tag. Then list the NORSOK material, coating and documentation standards the tender brings in. A tender written against an older edition can point to sheets or codes that have since changed. Raise a query for anything that does not match your copy.

How do I check a ball valve datasheet against a JIP33 set?

Check each datasheet line against API 6D, the supplementary specification and the procurement data sheet, in that order. Then check documents against the information requirements and inspection against the quality requirements. Mark each line complies, deviates or needs clarification. The compliance matrix template gives one row per requirement to work through.

Are JIP33 specifications mandatory?

No. A JIP33 specification only applies when a purchaser calls it up in a tender or purchase order. Many operators have adopted them, but each project decides. When a tender does name one, its requirements become contract requirements, including the data sheet, documents and quality levels. Read which specifications are named for each item.

Can I reuse JIP33 compliance work across operators?

Often, in part. The idea behind JIP33 is that operators share the same technical requirements, so a design and its documents can be qualified once and reused. In practice, each order still has its own data sheet selections, project additions and possibly a different revision. Reuse your earlier answers, but check each one against the current package.

How does OdysseyGPT check a JIP33 or NORSOK valve tender?

OdysseyGPT reads the whole package, including the data sheet and the information and quality requirements, when they are supplied. It checks each requirement against your own datasheets, standard specifications and test procedures, with a quote and page or line from the source. You export an editable compliance matrix and a deviations and clarifications list for an engineer to decide.

What can OdysseyGPT not do on a JIP33 or NORSOK tender?

It does not ship copies of NORSOK, JIP33 or API documents, so it can only check what they say if that text is in your upload. It does not certify compliance, read drawings, or send anything to the buyer. It drafts the matrix and deviation list from your documents. Your engineers check each row and decide every open item.

Frequently asked questions

What is IOGP S-562?

IOGP S-562 is the JIP33 procurement specification for ball valves to API Specification 6D. It adds a common set of purchaser requirements to API 6D and comes with a procurement data sheet, information requirements and quality requirements.

Does IOGP S-562 replace API 6D?

No. JIP33 specifications build on an industry standard. You still design and test to API 6D, and S-562 adds requirements on top of it.

Are JIP33 specifications free?

Yes. JIP33 states that all its specifications are free to download for anyone.

Is NORSOK the same as JIP33?

No. NORSOK standards are written by the Norwegian petroleum industry and published by Standards Norway. JIP33 is an IOGP programme that writes supplementary specifications to international industry standards. A tender can call up both.

Where should a deviation against a JIP33 data sheet selection go?

In the same deviation list as the others, quoting the data sheet line. Mark it as a data sheet selection so the buyer can see it is a choice they made for this project, not a common JIP33 requirement.

References

NORSOK L-001:2017, Piping and valves

Standard Norge (Standards Norway)

Buy the standard from Standards Norway.

Visit source

About JIP33

IOGP JIP33

Visit source

S-562 Ball Valves (API) launched for public review

IOGP JIP33

Visit source

API Specification 6D: Specification for Valves

American Petroleum Institute

Visit source

Related Pages