Standards work rarely makes headlines, but it determines what lands in valve specifications for the next decade. This year's activity across the API portfolio deserves attention from anyone who writes or reviews valve specifications.
API 6D and the pipeline valve baseline
API 6D remains the backbone standard for pipeline valves, and interpretation questions around its latest revision continue to generate the most technical inquiries we receive. The areas that trip up specifications most often are double-block-and-bleed definitions, seat testing acceptance criteria, and the documentation package requirements that accompany monogrammed products. Teams writing pipeline valve specifications should verify their templates reference the current edition β several projects we reviewed this year still carried language from superseded editions.
Fire-safe testing alignment
Fire-safe certification requirements under API 607 and ISO 10497 continue to converge, which simplifies life for manufacturers but creates transition questions for buyers holding certificates under older editions. When evaluating fire-safe certificates, check the edition date and the scope: a certificate for a reduced-bore configuration does not automatically cover the full-bore variant.
What the hydrogen drafts mean
The hydrogen valve test methods moving through ISO and ASME working groups matter beyond the hydrogen economy itself. The material qualification approaches β hardness ceilings, helium leak acceptance, cycle testing β are already appearing in project specifications as provisional requirements. Manufacturers and buyers who engage with the drafts now will find project negotiations easier when publication arrives.
- Verify specification templates reference current standard editions
- Fire-safe certificates must be checked for edition and configuration scope
- Hydrogen test methods are already entering project specs as provisional requirements
Our advice
Standards transitions reward early engagement. Buyers who ask suppliers pointed questions about edition compliance during qualification β rather than during delivery β avoid the awkward conversations that surface when documentation packages arrive. And specifiers who maintain a living cross-reference between their templates and current editions turn standards churn from a risk into a routine.
