Standardisation
From standards to semantics: Bridging the gap in valve data interoperability
For decades, the valve industry, spanning manufacturers,
EPCs, distributors and end users, has struggled with a singular, persistent challenge: fragmented data. Inconsistent specifications across projects lead to delays, rework, and inefficiencies throughout the asset lifecycle, from design and procurement to commissioning and maintenance.
By Michael Maar, MRC Global
While valves themselves are engineered to exacting tolerances, the data that describes them remains chaotic. Two industry voices frame this challenge from different angles: Onno Paap, Semantic Technologies and Data Interoperability at Fluor, brings the EPC perspective:“ Standards are essential— but their sheer number creates complexity.” When every project references a slightly different subset of standards or uses inconsistent naming conventions for the same attribute, confusion follows. Glen Beal, Engineering Manager at MRC Global and former Piping Material Technology Leader at Dow, adds the distributor and end-user viewpoint:“ You can’ t ignore standardisation— 80 % of valve attribute titles can and should be common and mappable. The remaining 20 %— special features, definitions, and requirements— is where flexibility and latitude come in.” Both agree on a critical reality: standards work is largely volunteer-driven, underfunded and spread across overlapping initiatives. This resource scarcity has historically killed attempts to build a unified“ master index” of valve data. Manual mapping is simply too slow and expensive. Now, however, AI and semantic frameworks make interoperability not only possible, but scalable and practical.
The 80 / 20 principle: Where standardisation ends and engineering judgment begins
The solution lies in a practical division: the 80 / 20 principle. This acknowledges that while total uniformity is impossible in a highly engineered industry, the vast majority of data points can be standardised without controversy. The framework is clear: 1. Standardisation accelerates the common 80 %. 2. Semantic mapping ensures the remaining 20 % is interoperable without forcing rigidity.
1. The 80 %: Standardised core attributes These are the foundational data elements that should remain consistent regardless of project or end user:
• Core physical attributes: Size( NPS / DN), pressure class( ASME Class), and temperature range— the non-negotiables of valve design.
• End connections: Standard interfaces such as flanged( ASME B16.5 / B16.47), threaded, or socket weld. Standardising terms like“ RF”( Raised Face) eliminates ambiguity.
• Materials & trims: Common alloys for body, seat, and stem. There is little need for variation when referring to 316 Stainless Steel or A216-WCB.
• Design & test references: Compliance with API 600( gate), API 608( ball), and API 598( testing).
• Quality and inspection deliverables: Standard document sets that accompany valve delivery— material test reports( MTRs), NDE records, fire-safe certifications.
Note: While US operations focus on API / ASME, global interoperability also requires accounting for ISO equivalents. The data model must be robust enough to handle both the US standard and its international counterpart without treating them as entirely different concepts.
2. The 20 %: Engineered and ownerspecific features As Glen Beal emphasized:“ The 20 % isn’ t just about exceptions— it’ s where engineering judgment lives.” This includes:
• Special features( i. e. stem extension,); special testing( testing other than what’ s defined in codes & standards).
• Owner-specific actuator logic, torque curves or fail-safe requirements.
• Fully engineered valves or custom features— often just 1 – 2 % of cases, but critical for complex service
This portion must remain flexible and extensible, but not isolated. The data model must allow these features to be captured without breaking alignment with the 80 %. This is where semantics play a crucial role. Before diving into that, however, it’ s important to first outline a few key industry initiatives that are shaping the standardisation landscape.
JIP33 and CFIHOS( JIP36): The foundation for lifecycle data integrity
The industry now has two powerful, aligned tools to bridge the gap between procurement and operations:
1. JIP33 – Standardising procurement Led by the International Association of Oil & Gas Producers( IOGP), JIP33 standardizes procurement specifications for commonly purchased equipment, including valves. With over 55 specifications published and freely available, it delivers:
32 Valve World February 2026 www. valve-world. net