IOGP S-562 Version 4.0: The Owner Overlay Reaches the Pipeline's Commonest Valve

The ball valve is the pipeline's commonest valve, and its specification stack just moved again. The JIP33 programme of the International Association of Oil & Gas Producers lists version 4.0 of IOGP S-562, Ball Valves (API 6D), dated April 2026 and active. The timing lands on a second movement already recorded on this site: the base standard, API 6D's 25th edition, is being incorporated into US federal pipeline safety law. The owner layer and the base layer are each moving on their own clock — and for the valve type where that layering matters most. This article sets out what the S-562 layer is, what the public record shows, and where the record stops. It is not a compliance determination.

What is the S-562 layer?

A minimum common set of supplementary requirements the owner community writes on top of API 6D, clause by clause, for ball valves.

JIP33's overlays follow a fixed grammar: the supplement mirrors the parent standard's clause structure, marks every intervention as an add, a replace or a delete, and leaves untouched clauses to apply as written in the parent. The instrument is a four-document set — the technical requirements specification, a procurement data sheet, an information requirements specification and a quality requirements specification — which with the purchase order forms the complete technical specification. API 6D itself is the product specification for pipeline valves; the overlay is where a group of large owners records what fleet experience says the product standard does not pin down tightly enough.

Why does the ball valve's overlay carry the widest reach?

Because ball valves are the default shutoff device of the pipeline world — trunk lines, stations, terminals — and the most numerous object any pipeline-valve specification governs.

A tightening written into a niche valve's supplement touches few projects; the same tightening written into S-562 touches nearly all of them. The parent standard's scope runs across gate, globe, check, ball and plug valves, but the ball valve dominates the population — floating and trunnion-mounted, soft- and metal-seated, from distribution to Class 900 transmission duty. When the owner community revises its overlay for that population, the revision propagates through every procurement package that invokes it.

What does the public record show about version 4.0?

The version line, the date and the active status — and little more, which is itself the record.

JIP33's published specification list records S-562 at version 4.0, dated April 2026, status active, alongside its siblings — the air-compressor and centrifugal-pump overlays this site has covered on sister publications. What changed between the previous version and 4.0 is not in the free record: the specification documents are distributed through IOGP's channels, and no public changelog details the April 2026 revision's clause content.

The readable part of the record is the timing. API 6D's 25th edition was published in 2021 and has since been named in US federal pipeline safety regulation — the layer that turns a consensus standard into law. S-562's fourth version lands inside that same window, the owner layer keeping pace with a base standard whose legal weight just changed.

Where does the public record stop?

At three places.

Version 4.0's clause content is not public. The free record shows the version, the date and the document family, not the changes themselves.

Edition is a contractual fact, not an ambient one. Which version of S-562 — and which edition of API 6D beneath it — governs any order is decided by the documents the contract names.

Nothing here assesses any valve or any package. Conformity is established per valve, per order, against the invoked documents.

What does the trend add up to?

The two layers of pipeline-valve specification are tightening in sequence: the base standard into federal law on one side, the owner overlay to its fourth version on the other. For a buyer, the durable discipline is the same one the overlay's structure teaches: name the edition of both layers on the face of the document, or the package is citing a moving target.

What this article does not cover

Note that this article does not reproduce the supplement's requirements, does not compare valve products, does not state which edition any project must invoke, and gives no prices. It records the public version record of a revised owner specification. It is not a compliance determination.

Where the next constraint sits

The base layer of this pair — what federal adoption of API 6D's 25th edition changes for pipeline valves — is set out in API 6D Enters US Pipeline Law: What Federal Adoption of the 25th Edition Changes.

And before either layer is cited, the valve's job has to be read in the right order — function first, class second, material third — as set out in Valve Selection Guide: From Function to Class to Material.

Sources