IOGP S-615 Version 2.01: The Owner Overlay That Follows API 610

A pump specification at an oil and gas major is written in two layers, and both layers moved within twelve months of each other. In December 2025 the International Association of Oil & Gas Producers' JIP33 programme listed version 2.01 of IOGP S-615, the supplementary specification to API Standard 610 for centrifugal pumps. Six months later, in June 2026, API published the 13th edition of API 610 itself. The overlay arrived first; the base text it annotates has since changed underneath it.

This article sets out what the S-615 layer is, what the public record shows about its December 2025 revision, why the two-layer structure matters to anyone writing or reading a pump order, and where the record stops. It is not a compliance determination.

What is the S-615 layer?

A minimum common set of supplementary requirements that the oil and gas producers' association writes on top of API 610, clause by clause.

The JIP33 overlay follows the parent standard's clause structure and marks every intervention as an add, a replace or a delete, so that a reader can see exactly where the owner community has tightened the base text. Clauses the supplement does not touch apply as written in the parent standard. The instrument is a four-document set — the technical requirements specification itself, a procurement data sheet, an information requirements specification and a quality requirements specification — which together with the purchase order define the complete technical specification for a procurement.

The stated order of precedence is: regulatory requirements, then the contract documents, then the purchaser's own documents, then the supplement, then the base standard. In other words, "meets API 610" is the floor of an order's technical content, not its ceiling.

What does the public record show about version 2.01?

The version line and the timing — and little more, and that is itself the fact worth recording.

JIP33's published specification list records S-615, Centrifugal Pumps (API 610), at version 2.01 dated December 2025, status active. The previous public baseline was version 2.0 of January 2023, whose redline publication documents the overlay's structure against API 610's 12th edition. What changed between the two versions is not in the free record: no public changelog details the December 2025 revision's clause-level content.

The timing, though, is legible. The overlay's second edition was written against the 12th edition of the base standard; version 2.01 landed in December 2025; the base standard's 13th edition followed in June 2026. Every overlay inherits this relationship: it is written against a named edition of a base standard, and the base standard moves on its own clock.

Why does the two-layer structure matter to a buyer?

Because an order written against one layer and read against another produces silent mismatches.

A supplier quoting against the 13th edition of API 610 while the purchaser's package invokes S-615 against the 12th is not a theoretical problem — clause numbering, datasheet fields and referenced standards all moved between those editions. The overlay's discipline exists precisely to keep the two legible together: the supplement names its parent edition, and the purchase documents name both.

For a buyer outside the JIP33 membership, the value of the layer is different but real: it is a public record of what experienced owner-operators found necessary to add to the base standard — the failure modes and ambiguities that fleet operations surfaced. Even without adopting it, reading the overlay's structure tells you where the base standard's purchasers historically needed more.

Where does the public record stop?

At three places.

Version 2.01's clause content is not public. The specification documents are distributed through IOGP's channels; the free record shows the version, the date and the document structure, not the December 2025 changes themselves.

The re-basing question is open. Whether and when the supplement is re-issued against API 610's 13th edition is not announced in the public record. A project must therefore name editions explicitly rather than assume alignment.

Nothing here assesses any pump or any package. The supplement is a procurement instrument; conformity is established per order, per unit, against the documents the contract names.

What does the trend add up to?

Two movements.

The owner layer is being maintained on a faster clock than the base standard — annual or near-annual version touches against the base's five-year cycle — which is where fleet experience gets written down first. And the two layers' versions will perpetually drift: anyone whose documents cite "API 610" or "S-615" without an edition is citing a moving target.

The discipline this implies is simple and old: name the edition, of both layers, on the face of the document.

What this article does not cover

Note that this article does not reproduce the supplement's requirements, does not evaluate any pump or any procurement package, does not advise which edition a project should invoke, and gives no prices. It records the structure and the public version record of a two-layer specification system. It is not a compliance determination.

Where the next constraint sits

The base layer of this pair — what the 13th edition of API 610 itself changed in June 2026 — is set out in API 610's 13th Edition: What the June 2026 Revision Changes for Centrifugal Process Pumps.

And before either layer is cited, the duty has to be read in the right order — risk first, medium second, duty point third — as set out in Chemical Pump Selection Guide: Risk, Medium and Duty Point — in That Order.

Sources