Hubbry Logo
search
logo
ISO 15926 avatar
ISO 15926
ISO 15926
current hub
I

ISO 15926

logo
Community Hub0 Subscribers
Read side by side
ISO 15926
View on Wikipedia
from Wikipedia

ISO 15926 is a standard for data integration, sharing, exchange, and hand-over between computer systems.

The title, "Industrial automation systems and integration—Integration of life-cycle data for process plants including oil and gas production facilities", is regarded too narrow by the present ISO 15926 developers. Having developed a generic data model and reference data library for process plants, it turned out that this subject is already so wide, that actually any state information may be modelled with it.

History

[edit]

In 1991 a European Union ESPRIT-, named ProcessBase, started. The focus of this research project was to develop a data model for lifecycle information of a facility that would suit the requirements of the process industries. At the time that the project duration had elapsed, a consortium of companies involved in the process industries had been established: EPISTLE (European Process Industries STEP Technical Liaison Executive). Initially individual companies were members, but later this changed into a situation where three national consortia were the only members: PISTEP (UK), POSC/Caesar (Norway), and USPI-NL (Netherlands). (later PISTEP merged into POSC/Caesar, and USPI-NL was renamed to USPI).

EPISTLE took over the work of the ProcessBase project. Initially this work involved a standard called ISO 10303-221 (referred to as "STEP AP221"). In that AP221 we saw, for the first time, an Annex M with a list of standard instances of the AP221 data model, including types of objects. These standard instances would be for reference and would act as a knowledge base with knowledge about the types of objects. In the early nineties EPISTLE started an activity to extend Annex M to become a library of such object classes and their relationships: STEPlib. In the STEPlib activities a group of approx. 100 domain experts from all three member consortia, spread over the various expertises (e.g. Electrical, Piping, Rotating equipment, etc.), worked together to define the "core classes".

The development of STEPlib was extended with many additional classes and relationships between classes and published as Open source data. Furthermore, the concepts and relation types from the AP221 and ISO 15926-2 data models were also added to the STEPlib dictionary. This resulted in the development of Gellish English, whereas STEPlib became the Gellish English dictionary. Gellish English is a structured subset of natural English and is a modeling language suitable for knowledge modeling, product modeling and data exchange. It differs from conventional modeling languages (meta languages) as used in information technology as it not only defines generic concepts, but also includes an English dictionary. The semantic expression capability of Gellish English was significantly increased by extending the number of relation types that can be used to express knowledge and information.

For modelling-technical reasons POSC/Caesar proposed another standard than ISO 10303, called ISO 15926. EPISTLE (and ISO) supported that proposal, and continued the modelling work, thereby writing Part 2 of ISO 15926. This Part 2 has official ISO IS (International Standard) status since 2003.

POSC/Caesar started to put together their own RDL (Reference Data Library). They added many specialized classes, for example for ANSI (American National Standards Institute) pipe and pipe fittings. Meanwhile, STEPlib continued its existence, mainly driven by some members of USPI. Since it was clear that it was not in the interest of the industry to have two libraries for, in essence, the same set of classes, the Management Board of EPISTLE decided that the core classes of the two libraries shall be merged into Part 4 of ISO 15926. This merging process has been finished. Part 4 should act as reference data for part 2 of ISO 15926 as well as for ISO 10303-221 and replaced its Annex M. On June 5, 2007 ISO 15926-4 was signed off as a TS (Technical Specification).

In 1999 the work on an earlier version of Part 7 started. Initially this was based on XML Schema (the only useful W3C Recommendation available then), but when Web Ontology Language (OWL) became available it was clear that provided a far more suitable environment for Part 7. Part 7 passed the first ISO ballot by the end of 2005, and an implementation project started. A formal ballot for TS (Technical Specification) was planned for December 2007. However, it was decided then to split Part 7 into more than one part, because the scope was too wide.

Need for ISO15926

[edit]

In 2004, the National Institute of Standards and Technology (NIST) released a report on the impact of the lack of digital interoperability in the capital projects industry. The report estimated the cost of inadequate interoperability in the U.S. capital facilities industry to be $15.8 billion per year. This was considered likely to be a conservative figure.[1]


The standard

[edit]

ISO 15926 has thirteen parts (as of February 2022):

  • Part 1 - Overview and fundamental principles
  • Part 2 - Data model [2]
  • Part 3 - Reference data for geometry and topology
  • Part 4 - Reference Data, the terms used within facilities for the process industry
  • Part 6 - Methodology for the development and validation of reference data (under development)
  • Part 7 - Template methodology
  • Part 8 - OWL/RDF implementation
  • Part 9 - Implementation standards, with the focus on standard web servers, web services, and security (under development)
  • Part 10 - Conformance testing
  • Part 11 - Methodology for simplified industrial usage of reference data (under development)
  • Part 12 - Life cycle integration ontology in Web Ontology Language (OWL2)
  • Part 13 - Integrated lifecycle asset planning

Description

[edit]

The model and the library are suitable for representing lifecycle information about technical installations and their components.

They can also be used for defining the terms used in product catalogs in e-commerce. Another, more limited, use of the standard is as a reference classification for harmonization purposes between shared databases and product catalogues that are not based on ISO 15926.

The purpose of ISO 15926 is to provide a Lingua Franca for computer systems, thereby integrating the information produced by them. Although set up for the process industries with large projects involving many parties, and involving plant operations and maintenance lasting decades, the technology can be used by anyone willing to set up a proper vocabulary of reference data in line with Part 4.

In Part 7 the concept of Templates is introduced. These are semantic constructs, using Part 2 entities, that represent a small piece of information. These constructs then are mapped to more efficient classes of n-ary relations that interlink the Nodes that are involved in the represented information.

In Part 8 the Part 7 Templates are defined in OWL and instantiated in RDF. For validation and reasoning purposes all are represented in First-Order Logic as well.

In Part 9 these Node and Template instances are stored in an RDF triple store, set up to a standard schema and an API. Each participating computer system maps its data from its internal format to such ISO-standard Node and Template instances.

Data can be "handed over" from one triple store to another in cases where data custodianship is handed over (e.g. from a contractor to a plant owner, or from a manufacturer to the owners of the manufactured goods). Hand-over can be for a part of all data, whilst maintaining full referential integrity.

Documents are user-definable. They are defined in XML Schema and they are, in essence, only a structure containing cells that make reference to instances of Templates. This represents a view on all lifecycle data: since the data model is a 4D (space-time) model, it is possible to present the data that was valid at any given point in time, thus providing a true historical record. It is expected that this will be used for Knowledge Mining.

Data can be queried by means of SPARQL. In any implementation a restricted number of triple stores can be involved, with different access rights. This is done by means of creating a CPF Server (= Confederation of Participating Façades). An Ontology Browser allows for access to one or more triple stores in a given CPF, depending on the access rights.

Projects and applications

[edit]

There are a number of projects working on the extension of the ISO 15926 standard in different application areas.

Capital-intensive projects

[edit]

Within the application of Capital Intensive projects, some cooperating implementation projects are running:

  • The DEXPI project: The objective of DEXPI is to develop and promote a general standard for the process industry covering all phases of the lifecycle of a (petro-)chemical plant, ranging from specification of functional requirements to assets in operation.

Finalised projects include:

  • The EDRC Project of FIATECH Capturing Equipment Data Requirements Using ISO 15926 and Assessing Conformance.[3][4]
  • The ADI Project of FIATECH, to build the tools (which will then be made available in the public domain)
    • The tools and deliverables can be seen on the ISO 15926 knowledge base
  • The IDS Project of POSC Caesar Association, to define product models required for data sheets
  • A joint ADI-IDS project is the ISO 15926 WIP

Upstream Oil and Gas industry

[edit]

The Norwegian Oil Industry Association (OLF) has decided to use ISO 15926 (also known as the Oil and Gas Ontology) as the instrument for integrating data across disciplines and business domains for the Upstream Oil and Gas industry. It is seen as one of the enablers of what has been called the next (or second) generation of Integrated operations, where a better integration across companies is the goal.[5]

The following projects are currently running (May 2009):

Finalised projects include:

  • The Integrated Information Platform (IIP) project working on establishing a real-time information pipeline based on open standards. It worked among others on:
    • Daily Drilling Report (DDR) to including all terms and definitions in ISO 15926. This standard became mandatory on February 1, 2008[7] for reporting on the Norwegian Continental Shelf by the Norwegian Petroleum Directorate (NPD) and Safety Authority Norway (PSA).[8] NPD says that the quality of the reports has improved considerably since.
    • Daily Production Report (DPR) to including all terms and definitions in ISO 15926. This standard was tested successfully on the Valhall (BP-operated) and Åsgard (StatoilHydro-operated) fields offshore Norway.[9] The terminology and XML schemata developed have also been included in Energistics’ PRODML standard.

Some technical background

[edit]

One of the main requirements was (and still is) that the scope of the data model covers the entire lifecycle of a facility (e.g. oil refinery) and its components (e.g. pipes, pumps and their parts, etc.). Since such a facility over such a long time entails many different types of activities on a myriad of different objects it became clear that a generic and data-driven data model would be required.

A simple example will illustrate this. There are thousands of different types of physical objects in a facility (pumps, compressors, pipes, instruments, fluids, etc). Each of these has many properties. If all combinations would be modelled in a "hard-coded" fashion, the number of combinations would be staggering, and unmanageable.

The solution is a "template" that represents the semantics of: "This object has a property of X yyyy" (where yyyy is the unit of measure). Any instance of that template refers to the applicable reference data:

  • physical object (e.g. my Induction Motor)
  • indirect property type (e.g. the class "cold locked rotor time")
  • base property type (here: time)
  • scale (here: seconds)

Without being able to make reference to those classes, via the Internet, it will be impossible to express this information.

References

[edit]
[edit]
Revisions and contributorsEdit on WikipediaRead on Wikipedia

ISO 15926

View on Grokipedia
from Grokipedia
ISO 15926 is an international standard series developed by the International Organization for Standardization (ISO) under the title "Industrial automation systems and integration—Integration of life-cycle data for process plants including oil and gas production facilities."[1] It specifies a conceptual data model and ontology-based framework for representing, exchanging, and integrating information throughout the entire life cycle of process plants, from initial conceptual design through engineering, construction, operation, maintenance, and decommissioning.[1] The standard enables semantic interoperability among diverse software systems and stakeholders by using a common vocabulary and reference data libraries, facilitating efficient data sharing in capital-intensive industries like oil, gas, and chemicals.[2] The primary purpose of ISO 15926 is to address longstanding challenges in data silos and interoperability within process industries, where fragmented information systems hinder collaboration and increase costs during plant development and operations.[3] By adopting a "4D" approach—treating plant assets as four-dimensional entities that evolve over time—it captures both static and dynamic aspects of assets, such as changes in design specifications or operational states.[3] This time-dependent modeling supports lifecycle management by allowing historical data to be queried and reused, ultimately reducing engineering rework and improving decision-making across project phases.[4] The standard is particularly applicable to process plants but extends to broader industrial automation contexts, promoting digital transformation through standardized data representation.[1] ISO 15926 comprises multiple parts that build upon its foundational principles outlined in Part 1, which provides an overview and defines the scope for life-cycle data integration.[1] Key components include Part 2, which details the data model using an upper ontology inspired by four-dimensionalism; Part 4, specifying core reference data items for consistent terminology; and Part 8, focusing on implementation via Resource Description Framework (RDF) and Web Ontology Language (OWL) for semantic web compatibility.[5][6] Additional parts address specific applications, such as conformance testing (Part 10), integration methodologies (Part 12), and ontologies for asset planning (Part 13).[7][8][9] The series aligns with related ontologies like the Industrial Data Ontology (IDO), a W3C OWL 2 DL-compliant ontology that supports integration of ISO 15926 reference data for enhanced logical consistency and scalability in large datasets.[10] Development of ISO 15926 began in the late 1990s, driven by industry consortia like the POSC Caesar Association (PCA), which aimed to create a vendor-neutral standard for data exchange in response to inefficiencies in traditional formats like STEP or XML.[2] The first parts were published around 2003–2004, with ongoing updates to incorporate semantic technologies and align with emerging digital standards.[1][10] Adoption has grown through initiatives like the DEXPI format for P&ID data exchange and EU-funded projects such as Optique, demonstrating its role in enabling production-grade interoperability in real-world engineering workflows.[11][10] As of 2025, the standard continues to evolve, with recent developments including the publication of ISO/TS 15926-4:2024 and ISO 15926-6:2024, as well as the April 2025 availability of the semantic representation of ISO 15926-4 edition 4 on PCA's cloud-based reference data platform to support Industry 4.0 applications.[5][12][13]

Introduction

Overview

ISO 15926 is an international standard comprising parts ISO 15926-1 through ISO 15926-13, developed by the International Organization for Standardization (ISO) to enable the representation and integration of lifecycle data for process plants, encompassing stages from conceptual design and engineering to construction, operation, maintenance, and decommissioning.[1] This framework addresses the complex information needs of industrial automation systems, particularly in sectors like oil and gas production facilities, by providing a structured approach to data management throughout the asset's life.[2] The core purpose of ISO 15926 is to facilitate semantic interoperability among disparate computer systems, allowing them to exchange information with unambiguous, shared meaning to support inferencing, knowledge discovery, and data federation.[2] It achieves this through a generic, ontology-based data model that leverages first-order logic and Semantic Web technologies, such as RDF and OWL, to ensure consistent interpretation of data across applications.[14] This model serves as a "Lingua Franca" for global data sharing, promoting efficient integration without loss of context or fidelity.[2] While primarily designed for process industries, the standard's ontology is applicable to any domain involving state-based information, extending its utility beyond traditional plant lifecycle management.[2] ISO 15926 evolved from the STEP standard (ISO 10303), adapting its principles for product data representation to better suit the dynamic, time-dependent requirements of process plant data.[15] It incorporates reference data libraries and a template methodology to standardize common elements and enable flexible data exchange.[14]

Scope and Objectives

ISO 15926 defines the scope for the integration of life-cycle data pertaining to process plants, encompassing technical installations in industries such as oil, gas, and chemicals. It addresses both static and dynamic data representations across all phases of the plant lifecycle, including feasibility studies, engineering design, construction, commissioning, operation, maintenance, and decommissioning. This scope emphasizes a "4D approach" that models physical objects, their properties, classifications, assemblies, connections, and temporal changes to enable comprehensive data management for process facilities.[2][3] The primary objectives of ISO 15926 are to facilitate vendor-neutral data exchange and achieve global semantic interoperability, ensuring that information shared between systems carries unambiguous meaning. By supporting the use of semantic web technologies, such as those from the W3C, the standard enables machine-readable data that can be archived, collected, and integrated for applications like computer-aided engineering (CAE), digital twins, and operational optimization. A key goal is to reduce the costs associated with data interoperability challenges in the capital facilities industry, which includes process plants; for instance, a 2004 NIST study estimated annual U.S. losses at $15.8 billion due to inadequate interoperability across design, construction, and operations phases.[2][16][17] The standard explicitly excludes non-technical aspects of plant management, such as financial modeling or human resources data, concentrating instead on the conceptual information modeling of technical elements rather than prescribing specific software implementations or protocols. While it builds upon the foundations of ISO 10303 (STEP) for static product data representation—leveraging application protocols like AP 221 for functional data and AP 227 for spatial configuration—ISO 15926 extends these capabilities to handle time-variant process data and evolutionary changes in plant configurations throughout the lifecycle.[3]

Historical Development

Origins

The origins of ISO 15926 trace back to the early 1990s, when the process industries faced significant challenges due to proprietary data formats in computer-aided design (CAD) and computer-aided engineering (CAE) systems, leading to frequent integration failures during capital projects such as plant construction and maintenance.[18] These issues stemmed from fragmented data exchange across disciplines and project phases, prompting collaborative efforts to develop neutral, lifecycle-spanning data models for improved interoperability.[4] A pivotal early initiative was the 1991 ProcessBase ESPRIT project, an EU-funded research effort aimed at creating a data model for integrating process plant lifecycle information using object-oriented modeling techniques.[4] Managed by Framatome and involving multiple European partners, ProcessBase focused on neutral formats for exchanging and managing process data across all phases of plant development, laying foundational concepts for standardized data representation in the sector.[19] In 1993, the Process Industries STEP (PISTEP) consortium was formed as a collaboration among European firms to adapt ISO 10303 Application Protocol 221 (AP221) specifically for piping and process plant data, enhancing engineering information exchange to boost industry competitiveness.[20] Building on this, the EPISTLE consortium emerged in the late 1990s through the merger of PISTEP, POSC/Caesar (a Norway/U.S. initiative), and USPI-NL, with a primary focus on developing lifecycle data dictionaries to support dynamic information management over plant lifespans.[20] EPISTLE coordinated international projects to address gaps in existing STEP standards, emphasizing semantic consistency and long-term data evolution.[18] Parallel to these efforts, STEPlib was developed in the 1990s as an early reference data library by USPI-NL, PISTEP, and POSC/Caesar, providing a structured collection of classes and relationships for process plant data based on AP221.[20] This library evolved into the Gellish English dictionary, a semantic representation system that extended STEPlib's concepts for ontology-based data storage and communication, incorporating upper ontology elements to enable precise, machine-readable expressions of engineering knowledge.[21]

Standardization Milestones

The standardization of ISO 15926 began with the publication of its first formal component in 2003, when Part 2 was released as an International Standard, specifying the conceptual data model in EXPRESS language for representing process plant life-cycle information. This marked the initial step in formalizing the upper ontology for integration of life-cycle data in industrial automation systems, particularly for process plants including oil and gas production facilities.[22] In 2007, Part 4 was published as a Technical Specification (ISO/TS 15926-4), establishing the initial reference data library by merging elements from STEPlib (derived from ISO 10303 application protocols) and the POSC/Caesar Reference Data Library (RDL), providing a foundational set of standardized classes and properties for equipment and processes.[23] This part enabled consistent categorization of industrial objects, facilitating interoperability across systems.[24] Between 2011 and 2018, several key parts were developed and published to extend the standard's implementation and ontology capabilities. Part 7 (ISO/TS 15926-7:2011) introduced the template methodology, defining reusable patterns for expressing relationships in life-cycle data exchange.[25] Part 8 (ISO/TS 15926-8:2011) specified implementation methods using OWL and RDF for semantic web representation, allowing for distributed system integration.[6] Part 12 (ISO/TS 15926-12:2018) provided an OWL-based ontology for life-cycle integration, building on the core data model to support advanced reasoning.[8] Additionally, Part 13 (ISO 15926-13:2018) was issued, focusing on ontologies for integrated life-cycle asset planning in process industries.[9] Part 10 (ISO 15926-10:2019), closely following this period, outlined conformance testing methodologies to validate compliance with the standard's requirements.[7] More recent advancements include the 2023 revision of Part 11 as ISO/TS 15926-11:2023, which addresses simplified industrial usage through product knowledge models tailored for systems engineering in process sectors, revising the original 2015 technical specification.[26] In 2024, Part 6 was published (ISO 15926-6:2024), detailing the methodology for developing and validating reference data libraries aligned with Part 4.[12] Ongoing efforts as of November 2025 involve the second edition of Part 2 to update the core data model as an ontology base, along with a new technical report ISO/TR 15926-200 providing practical implementation guidance following a 2024 review.[27] Development continues on Part 4 edition 4, incorporating additional discipline spreadsheets and an improved hierarchy, with publication targeted for early 2026; a semantic representation of this edition became available in April 2025.[28] [27] Efforts also include a new Part 100 on vocabulary, with a draft circulated in August 2025.[29] Previous work on Part 5 (procedures for reference data registration and maintenance, previously canceled) and Part 9 (implementation for triple stores and facades) remains under consideration in broader contexts.[4] These updates reflect the standard's adaptation to digital transformation in industrial automation.[30]

Rationale and Benefits

Industry Challenges Addressed

In the process industries, such as oil and gas, chemical processing, and power generation, data silos arise from the use of proprietary formats in engineering software like CAD and ERP systems, which isolate information across different tools and stakeholders.[4] These silos necessitate manual data re-entry during project handovers, introducing errors and inefficiencies that compound over the plant lifecycle.[17] Lifecycle fragmentation further exacerbates these issues, as data representations remain inconsistent across project phases—from conceptual design and construction to operations and maintenance—spanning decades.[4] This inconsistency results in fragmented information that hinders seamless transitions, contributing to significant economic burdens; a 2004 NIST analysis estimated annual U.S. costs of $15.8 billion due to inadequate interoperability in the capital facilities sector, which encompasses process plants.[17] During plant upgrades, maintenance data is particularly vulnerable to loss when legacy systems fail to integrate with new ones, causing incomplete records and operational disruptions.[4] Scalability challenges emerge from the explosive growth of data volumes in complex projects, such as offshore oil platforms, where semantic standards are absent, making it difficult to manage and analyze vast datasets across global teams.[31] Vendor lock-in compounds this by restricting integration of systems from multiple suppliers in capital-intensive sectors like oil and gas, where proprietary ecosystems limit flexibility and increase long-term dependency costs.[4] These interconnected problems underscore the need for standardized data exchange to mitigate risks and enhance efficiency throughout the plant lifecycle.[15]

Advantages of Adoption

Adopting ISO 15926 offers significant cost savings in industrial data management by reducing the need for rework and data conversion during project handovers and integrations. For instance, standardization through its reference data libraries minimizes redundant data mapping efforts, leading to more efficient capital project executions. Studies indicate that such interoperability can lower overall ownership costs by streamlining information flows across the plant lifecycle.[32][33] The standard enhances data accuracy via semantic consistency, which ensures precise representation of engineering concepts and reduces errors in lifecycle transitions. This reliability supports advanced applications like predictive maintenance, where unambiguous data handover prevents misinterpretations that could lead to operational failures. By enforcing a shared ontology, ISO 15926 maintains fidelity in information exchange between diverse systems, fostering trustworthy decision-making in complex environments.[34][33] Scalability is a key advantage, as the reusable reference data libraries allow organizations to adapt quickly to new projects or evolving regulations without rebuilding data models from scratch. This modular approach enables extension of the standard's framework to handle increasing data volumes, making it suitable for both small-scale implementations and large enterprise deployments.[35][33] Interoperability is greatly improved, facilitating seamless plug-and-play integration between legacy systems and modern technologies, including IoT devices and digital twins for process plants. This capability extends the usability of existing assets while incorporating real-time data streams, promoting a connected ecosystem that enhances operational agility.[34][32][36] In the long term, ISO 15926 enables knowledge reuse across entire asset lifecycles, substantially lowering total ownership costs in capital-intensive projects. By providing a persistent, vendor-neutral data structure, it supports ongoing value extraction from historical information, reducing the need for repeated data recreation and enhancing sustainability in industrial operations.[34][32]

Components of the Standard

Core Parts

The core parts of ISO 15926, specifically Parts 1 through 4, establish the foundational architecture for representing life-cycle data in process plants, including oil and gas production facilities, by providing conceptual principles, a generic data model, and initial reference data libraries.[1] These parts focus on static, timeless elements that support data integration across engineering, construction, and operational phases without delving into dynamic implementation methods.[37] Part 1, titled "Overview and fundamental principles," outlines the scope and objectives of the standard, emphasizing a unified representation of process plant information that accommodates time-variant aspects through a four-dimensional (4D) approach to entities.[1] It defines key concepts such as classes and relationships, where a class is described as "a category or division of things based on one or more criteria for inclusion and exclusion," serving as the basis for an upper ontology that structures all subsequent data models.[38] This part guides the conceptual use of the standard by introducing principles like the three-schema architecture for data independence and the role of reference data in ensuring consistency across applications.[37] Although detailed entity definitions like "possible individual" are formalized in Part 2, Part 1 establishes the philosophical framework for handling time-variant entities as things that exist in space and time, enabling the modeling of changes over a plant's life cycle.[39] Part 2, "Data model," specifies a conceptual data model expressed in the EXPRESS language (ISO 10303-11), known as the ECM (Engineering Conceptual Model) schema version 4.5.1, which forms the generic backbone for representing technical information about process plants.[39] The schema, defined as the lifecycle_integration_schema, includes core entities such as thing as the supertype for all elements, class for categorizing objects, possible_individual for entities that exist in space and time (e.g., a specific pump instance across its operational history), and relationship for linking elements with defined cardinalities.[40] For physical objects, it provides classes like physical_object, materialised_physical_object (e.g., tangible equipment such as valves), and functional_physical_object (e.g., roles like flow control), extended through space-time worms to capture temporal variations.[41] Activities are modeled via entities such as activity, event, and participation, allowing representation of processes like maintenance or production linked to specific time periods and participants.[40] Relationships are handled through subtypes like other_relationship and classification, enabling hierarchical connections between individuals or classes, all illustrated in EXPRESS-G diagrams for clarity.[39] Part 3, "Reference data for geometry and topology," extends the data model in Part 2 by providing standardized classes and instances for spatial representations, independent of specific software applications, to support 3D modeling in process plant design.[42] It defines geometric concepts such as points, lines, and surfaces as basic shapes, allowing the description of object boundaries and forms in three-dimensional space.[43] Topological elements include connections and adjacencies, such as edge-face relationships or vertex incidences, which model how components like pipes or equipment interconnect without relying on coordinate systems.[44] For example, in 3D models, a vessel's shell might be represented as a bounded surface connected topologically to nozzles, ensuring interoperability in plant layout simulations.[42] These reference data items are instantiated as classes in the Part 2 schema, promoting reuse across life-cycle stages like construction and maintenance.[43] Part 4, "Core reference data" (ISO/TS 15926-4:2024), establishes the Reference Data Library (RDL) as a foundational collection of standardized classes and properties tailored to process industries, serving as the initial dictionary for common elements like equipment and materials.[5] It comprises 16 sets of reference data items, including categories for activities, connections, electrical components, piping, and valves, each with unique identifiers, definitions, and subclass hierarchies. The RDL integrates established libraries such as those from POSC Caesar Association (PCA), incorporating classes for equipment (e.g., pumps, heat exchangers) and materials (e.g., alloys, insulation types) to ensure broad applicability in oil and gas contexts.[45] For instance, a "centrifugal pump" class might subclass under "rotating machine," linking to Part 2 entities for consistent usage across databases. This part emphasizes maintenance through registration procedures, with data represented in accessible formats like spreadsheets for easy adoption.[5] Collectively, Parts 2 through 4 provide the static backbone of the standard—the data model in Part 2 populated by reference instances in Parts 3 and 4—while Part 1 offers the guiding principles for their conceptual application, ensuring a coherent upper ontology for timeless data representation.[1] This foundation supports extensions in later parts without altering the core structure.[37]

Advanced Parts

The advanced parts of ISO 15926, numbered 6 through 13, extend the foundational elements defined in the core parts by providing methodologies, implementation guidelines, and extensions tailored for practical application in lifecycle data integration for process plants. These parts emphasize tools for managing reference data, standardizing templates, ensuring semantic compatibility, and supporting conformance, while addressing specific needs in systems engineering and asset planning. They build upon the conceptual data model and reference data libraries outlined in earlier parts, enabling scalable adoption across industries such as oil, gas, and manufacturing.[12] Part 6, published in 2024, specifies the structure and content requirements for reference data libraries that support ISO/TS 15926-4, focusing on the identification and definition of reference data items using the EXPRESS-based model from ISO 15926-2. It details how to record these items, including their representation in spreadsheet formats for accessibility, while excluding administrative aspects like source tracking or proprietary maintenance procedures. This part ensures that RDLs are standardized for use in integrating geometry, topology, and industrial terminology across plant lifecycles. It also provides rules for the development and validation of reference data items.[12] Part 7 introduces the template methodology for defining reusable patterns within the ISO 15926 framework, enabling efficient data exchange and lifecycle information integration based on the upper ontology in Part 2. Templates, such as those for "functional objects," provide strict, predefined models of conceptual elements to represent common process plant scenarios, reducing redundancy in data modeling. This approach facilitates the instantiation of complex relationships, like equipment configurations or process flows, in a consistent manner across distributed systems.[25] Part 8 details the implementation of ISO 15926 using RDF and OWL for semantic web compatibility, specifying methods to integrate lifecycle data for process plants through ontology-based representations. It implements the upper ontology from Part 2 and templates from Part 7, including models for reference data from Parts 3 and 4, along with metadata handling. Electronic attachments in the standard provide OWL declarations and example instance data to guide developers in achieving interoperability via web technologies.[6] Part 9, currently under development, aims to establish general implementation standards for ISO 15926, focusing on methods for populating data endpoints and integrating multiple information sources in lifecycle contexts. It addresses broader adoption challenges by defining protocols for triple stores and data federation, though its scope excludes specific syntax or serialization details. Progress on this part involves ongoing collaboration within ISO/TC 184/SC 4 to align with emerging digital twin and Industry 4.0 requirements.[4] Part 10 defines conformance testing procedures for software implementations of the ISO 15926 series, establishing principles and methods to verify compliance with the standard's data model and integration requirements. It offers guidance on developing test cases and scenarios, including simple conformance checks against Parts 1 and 2, to ensure reliable data sharing in process industries. This part supports certification efforts by outlining how implementations can be validated for accuracy in handling reference data and templates.[7] Part 11, as a Technical Specification updated in 2023, provides a simplified methodology for using ISO 15926 in product knowledge models within systems engineering, leveraging RDF triples, reference data dictionaries, and standardized relationships for flexible data exchange. It includes an initial set of relationships for representing process plant lifecycles and configuration management practices to track changes and enable baselining. Applicable primarily to process industries but extensible to manufacturing and aerospace, it excludes serialization methods to focus on conceptual modeling.[26] Part 12 specifies a lifecycle integration ontology represented in OWL 2, facilitating the unification of industrial data across all phases from design to decommissioning. This ontology extends the core model by defining classes and properties for temporal, spatial, and functional aspects of assets, allowing for extensible subclasses to accommodate domain-specific needs. It promotes semantic reasoning and data federation in distributed environments, enhancing decision-making in plant operations.[8] Part 13, published in 2018, focuses on integrated lifecycle asset planning, including maintenance and operations for process plants such as oil and gas facilities, through an ontology and accompanying XML schema. It addresses planning activities like resource allocation and risk assessment, integrating with prior parts to support end-to-end asset management. The standard emphasizes practical extensions for operational phases, enabling better handover and sustainment of plant data.[9]

Technical Framework

Data Model and Reference Data

The data model of ISO 15926 forms the semantic foundation for representing process plant lifecycle information in a timeless, computer-interpretable manner. It is defined as an upper ontology in Part 2 of the standard, which establishes a generic framework for entities, relationships, and properties that support data integration across the entire lifecycle, from design to decommissioning. This ontology distinguishes between timeless definitions, such as classes that represent general concepts, and time-stamped instances that capture specific occurrences or states. Central to this structure are key metaclasses like ClassOfIndividual, which defines categories of entities (e.g., types of equipment or processes), and PossibleIndividual, which encompasses actual or potential instances of those classes, including physical objects and events that exist in space and time.[4][32] The formal representation of this upper ontology is provided through the EXPRESS schema language, as specified in ISO 15926-2:2003. This schema, often referred to as the ECM (EPISTLE Core Model) schema in its developmental origins, comprises approximately 201 concepts, including over 200 classes that model core entities such as physical objects, functional systems, and relational structures. These classes enable the explicit definition of attributes, hierarchies, and dependencies, ensuring that data remains consistent and extensible for process industries. For instance, the schema supports the modeling of equipment classifications and their properties without tying them to specific implementations, allowing for vendor-neutral representations.[20][46] Complementing the data model are the Reference Data Libraries (RDLs), detailed in ISO/TS 15926-4:2024, which serve as standardized, hierarchical dictionaries of domain-specific vocabulary. These libraries contain over 20,000 classes organized taxonomically, covering equipment like valves and pumps, as well as properties, materials, and activities essential for process plants. RDLs are extensible, permitting industry-specific extensions while maintaining compatibility with the core schema, and each entry includes unique identifiers, definitions, and relationships to ensure semantic precision.[47] Geometry integration is addressed in ISO/TS 15926-3:2009, which incorporates standardized topological and geometric concepts into the overall model. This allows for the representation of spatial data, such as shapes, boundaries, and assemblies of plant components, using a subset of ISO 10303 (STEP) geometric primitives adapted to the ISO 15926 framework. Topological elements, like faces and edges, enable precise modeling of interconnections and layouts without proprietary formats.[42] At its core, ISO 15926 adopts a data-driven approach where the reference data libraries supply the controlled vocabulary for domain terms, while the generic data model provides the grammatical rules for combining and relating them, facilitating unambiguous information exchange.

Templates and Ontologies

ISO 15926 employs templates as defined in Part 7 to provide parameterized patterns for expressing reusable semantic constructs based on the underlying data model in Part 2. These templates consist of a first-order logic predicate, a signature specifying parameter types, and an axiom expansion that maps to entity data types, enabling the representation of common information patterns without requiring extensive custom schemas.[25] For instance, the ClassificationOfIndividual template assigns a class to an individual, while InstanceOfRelation templates link relationships to specific classes, thereby reducing schema complexity by standardizing the encoding of frequent assertions across life-cycle data.[48] Parts 8 and 12 of ISO 15926 facilitate the conversion of the EXPRESS-based schema from Part 2 into Web Ontology Language (OWL) and Resource Description Framework (RDF) formats, supporting semantic web technologies for data integration. Part 8 outlines rules for mapping the data model, reference data from Part 4, and templates from Part 7 to RDF triples and OWL constructs, including the use of reification for n-ary relations and OWL 2 DL for decidable reasoning.[6] Part 12 extends this by specifying a comprehensive OWL 2 ontology that integrates life-cycle data, representing entities such as physical objects, activities, and events through object, datatype, and annotation properties, while incorporating temporal aspects via ISO 8601 for time-series handling.[8] The ontology structure in ISO 15926 organizes knowledge into taxonomies of classes (e.g., for equipment types), properties (e.g., relations like participation or location), and individuals (specific instances of classes), enabling hierarchical classification and relational modeling that aligns with the reference data libraries (RDLs). This structure supports automated reasoning, such as inferring properties from class memberships or temporal constraints, over dynamic datasets including time-series information from plant operations.[49] These templates and ontologies enhance scalability by allowing complex queries across distributed systems without proprietary mappings, as the standardized patterns and semantic encodings facilitate efficient inference engines and SPARQL-based retrievals for large-scale life-cycle integration.[35] An illustrative extension is Gellish, a semantic network formalism that builds on ISO 15926 RDLs to express knowledge in a formalized natural language, supporting interchangeable data exchange through RDF-compatible triples.[50]

Implementation Approaches

Integration Methods

Integration of systems using ISO 15926 relies on standardized data exchange formats that facilitate seamless handover between tools across the plant lifecycle, such as from design to operations. The standard employs Resource Description Framework (RDF) triples to represent statements about physical objects, activities, and relationships, enabling the serialization and sharing of instance data.[26] SPARQL queries are utilized to retrieve and manipulate this RDF-based data, supporting federated access across distributed systems.[8] Additionally, APIs can be implemented to automate data transfer, often wrapping RDF exports in XML formats like those defined in ISO 15926-8 for project data exchange.[4] System architectures for ISO 15926 typically center on triple stores to manage and query large volumes of template instances and reference data. These stores, such as those compliant with RDF and OWL standards, allow for the persistent storage of graph-based data, enabling efficient inference and retrieval.[35] Middleware solutions play a crucial role in bridging legacy systems by providing adapters that map proprietary data models to ISO 15926-compliant formats, often using export/import mechanisms to convert internal schemas into RDF triples.[4] This architecture supports a federated model where multiple triple stores can be queried via SPARQL endpoints, ensuring scalability for lifecycle data integration.[51] The typical workflow for integrating proprietary schemas with ISO 15926 begins with mapping source data elements to standardized templates, which encapsulate complex relationships from the ISO 15926-2 data model. This mapping process involves identifying objects of interest, selecting appropriate templates, and validating the resulting RDF instances against Shapes Constraint Language (SHACL) rules before serialization in an RDF format compatible with OWL ontologies for enhanced interoperability and reasoning.[4] Once mapped, the data can be imported into target systems via SPARQL updates or API calls, allowing for automated population of operational databases from design outputs. Recent updates, including ISO 15926-6:2024 for reference data library structure and the 2025 semantic OWL representation of ISO/TS 15926-4 edition 4, further support advanced implementations using updated RDLs.[12][28] Several tools support these integration efforts, including open-source options like the POSC Caesar Reference Data Library (RDL) browser, which provides a web interface for exploring and validating reference data classes aligned with ISO 15926-4.[52] Commercial tools, such as Intergraph's SmartPlant P&ID ISO 15926 Export Utility, enable direct export of piping and instrumentation diagrams to XML formats compliant with the standard, facilitating handover to 3D design and operations systems.[53] Best practices for ISO 15926 adoption emphasize a phased approach, starting with validation of reference data against the RDL to ensure semantic consistency before scaling to full instance data exchange. This involves initial modeling of core lifecycle elements using OWL ontologies, followed by iterative mapping and testing of adapters to minimize errors in legacy data integration. Organizations are advised to certify export adapters per emerging guidelines in ISO 15926-10 and leverage automated reasoning tools for ongoing data quality checks.[4][51]

Conformance and Testing

ISO 15926-10:2019 establishes the principles and methods for conformance testing of software implementations supporting the standard, focusing on verifying compliance with its data models, templates, and reference data requirements. This part offers guidance for creating test cases that assess model adherence, including validation of template instantiations to ensure they correctly reference and utilize elements from the Reference Data Library (RDL), such as classes and properties defined in ISO 15926-4 and subsequent parts. These test cases typically involve checking the structural integrity of data exchanges, confirming that instantiated objects align with predefined templates without introducing inconsistencies in relationships or attributes.[7] ISO 15926 defines conformance principles that allow for varying degrees of implementation depth, including requirements for proper usage of reference data from the RDL for semantic consistency and incorporation of OWL-based semantics for advanced querying and reasoning, as outlined in ISO 15926-10. These levels help vendors and users gauge the robustness of their systems, from simple data export to comprehensive ontology-driven integrations.[7] Testing procedures under ISO 15926 emphasize automated tools and structured evaluations to maintain quality. Automated scripts are commonly employed for schema validation, parsing RDF or XML files to detect deviations from the core data model in ISO 15926-2 and ensuring compliance with serialization formats in ISO 15926-8. Interoperability demonstrations between vendor systems, such as joint data exchange simulations, further verify practical adherence by testing end-to-end workflows without proprietary extensions. The NIST has contributed to this by developing conformance checking tools that analyze information models against the upper ontology, templates, and RDLs.[33] ISO 15926-13:2018 extends the standard's ontology to support integrated asset planning across the life-cycle of process plants, including oil and gas facilities, with provisions for XML schemas that facilitate data integration. Testing in this context includes asset planning scenarios that incorporate maintenance data, such as evaluating the mapping of historical maintenance records to ontology classes for predictive analytics and handover processes. These extensions enable verification of how maintenance information from operational phases aligns with planning ontologies, ensuring seamless data flow in multi-vendor environments.[9][54] Challenges in conformance and testing arise particularly with under-developed parts like ISO 15926-9, which addresses triple stores for semantic data storage and remains in draft status, complicating full-stack validations that rely on RDF triple representations. Certification processes involve oversight by bodies aligned with ISO procedures, such as audits conducted through ISO/TC 184/SC 4, to accredit software adapters and ensure they meet Part 10 criteria without introducing errors in data mapping or export.[4]

Applications and Projects

Process Industries

ISO 15926 has seen broad adoption across key process industries, including oil and gas (encompassing both upstream exploration and production as well as downstream refining and distribution), chemicals, and pharmaceuticals, where it supports the integration of life-cycle data for plant design, engineering, and operational management. In the oil and gas sector, the standard facilitates seamless data exchange from initial facility planning through to maintenance, addressing the complex needs of global supply chains and asset management. Similarly, in chemicals and pharmaceuticals, it enables consistent representation of process equipment, materials, and workflows, ensuring interoperability between design software and operational systems throughout a facility's lifecycle. This adoption is driven by the standard's focus on process plant information, as outlined in its core scope for industrial automation systems.[2] To accommodate sector-specific requirements, ISO 15926 employs extensions to its Reference Data Libraries (RDLs), which provide standardized vocabularies that can be subclassed for domain adaptations. For instance, in upstream oil and gas, RDLs are extended to include specialized classes for drilling equipment and subsurface assets, allowing precise modeling without compromising the core ontology's interoperability. These extensions, defined in parts like ISO/TS 15926-4, enable the incorporation of industry-tailored reference data while maintaining semantic consistency across applications. In chemicals and pharmaceuticals, similar adaptations support vocabulary for reaction vessels and compliance-related equipment, enhancing data reusability in multi-vendor environments.[55][4] Regulatory compliance in these sectors is supported through ISO 15926's data models, which align with established standards such as the American Petroleum Institute (API) specifications for oil and gas equipment integrity and European Union directives like REACH for chemical safety and environmental reporting. By standardizing data representation, the framework ensures traceable and auditable information flows, aiding adherence to safety and reporting mandates without custom integrations. This alignment reduces compliance risks in highly regulated environments.[56][4] The standard's implementation yields significant general impacts on engineering, procurement, and construction (EPC) workflows, streamlining data handover and collaboration among stakeholders to minimize errors and interfaces. In process industries, this results in reduced project delays, with reported productivity gains of up to 30% in EPC phases through improved data portability and automation. Additionally, ISO 15926 is widely utilized in front-end engineering design (FEED) phases for accurate cost estimation, leveraging its templates and ontologies to model plant configurations early and forecast expenses with greater precision. These benefits underscore its role in enhancing efficiency across the sector's value chain.[56][57]

Specific Case Studies

The DEXPI initiative, launched in 2011 by a consortium of process industry stakeholders including owner-operators, engineering firms, and software vendors, establishes a standardized format for exchanging piping and instrumentation diagrams (P&IDs) in the petrochemical sector.[58] It leverages ISO 15926 Parts 7 and 8 to define an XML-based schema that captures both graphical and topological data, enabling seamless transfer between computer-aided design systems while aligning with the broader ISO 15926 reference data library.[59] This approach facilitates interoperability across the plant lifecycle, from design to operations, by mapping P&ID elements to standardized classes and relationships.[60] In October 2025, DEXPI released version 2.0 of its specification, introducing enhanced process modeling capabilities and a standardized serialization format for P&IDs to support Industry 4.0 applications.[61] FIATECH, a U.S.-based industry consortium focused on capital project efficiency, advanced ISO 15926 adoption through several targeted projects in the 2000s and 2010s. The Equipment Data Requirements Capture (EDRC) project, completed in 2015, developed methods to specify and validate equipment data using ISO 15926 templates, involving collaboration with manufacturers to assess conformance and reduce handover discrepancies in engineering procurement construction processes.[62] Complementing this, the Accelerating Deployment of ISO 15926 (ADI) project built software tools for automated data integration, while the Intelligent Data Sets (IDS) initiative, in partnership with POSC Caesar, created reusable data packages for U.S. capital projects in oil and gas, emphasizing reference data alignment to streamline project information exchange.[63] In the upstream oil and gas sector, the Norwegian Oil Industry Association (OLF) mandated the use of ISO 15926 for Daily Drilling Reports (DDRs) starting February 1, 2008, requiring operators to submit standardized reports to the Norwegian Petroleum Directorate that incorporate all relevant terms and definitions from the standard.[64] This integration utilizes ISO 15926 templates to structure well data, including drilling activities, equipment status, and environmental metrics, enabling automated population of over 80% of report fields and improving data quality for regulatory compliance and partner sharing.[65] The mandate has supported real-time onshore access to offshore data, enhancing integrated operations across Norway's continental shelf.[66] The POSC Caesar Association, a key contributor to ISO 15926 development, has integrated the standard into the Open Subsurface Data Universe (OSDU) platform to support digital oilfields. OSDU leverages ISO 15926 Part 12, which defines an ontology for lifecycle data integration, to enable consistent representation of subsurface assets, well data, and production information across cloud-based ecosystems.[67] This application promotes data interoperability in exploration and production, allowing operators to query and exchange standardized datasets for advanced analytics and simulation in virtual reservoir environments.[4] Recent extensions of ISO 15926 include the publication of ISO 15926-6:2024, specifying requirements for reference data library structure and content, and the updated ISO/TS 15926-4:2024, expanding core reference data items for process plants including oil and gas production facilities. These updates facilitate broader applications in digital twins and asset management. Additionally, synergies with the Capital Facilities Information Handover Specification (CFIHOS) have been developed to provide common reference data libraries, enhancing data exchange in EPC workflows across process industries.[12][5][68]

Current Status and Future Outlook

Recent Developments

In 2023, the International Organization for Standardization published the second edition of ISO/TS 15926-11, which provides a methodology for creating simplified industrial models using reference data as defined in ISO/TS 15926-4.[26] This technical specification supports systems engineering processes by enabling flexible product knowledge models and data exchange across supply chains in process industries, including oil, gas, and power sectors, through RDF triples and standardized relationships.[26] It replaces the 2015 edition with technical revisions focused on lifecycle data integration and configuration management, excluding serialization methods or specific formats.[26] The following year, in December 2024, ISO 15926-6 was finalized as the first edition, establishing rules for the development and validation of reference data libraries (RDLs) aligned with ISO/TS 15926-4.[12] This part specifies technical requirements for the structure and content of RDLs, using ISO 15926-2 for identification and definition, and presents them in spreadsheet format for improved accessibility.[12] By providing these guidelines, it enhances the usability of Part 4's reference data, facilitating consistent application in process plant lifecycle data integration.[12] Recent integrations of ISO 15926 with Industry 4.0 technologies have emphasized semantic interoperability, particularly through OWL2 representations in Part 12, which defines a life-cycle integration ontology for industrial data.[8] This ontology, covering physical objects, activities, events, and 4D space-time relationships, supports the creation of digital twins by standardizing data models for process plants, enabling real-time synchronization and simulation in manufacturing environments.[8] Additionally, alignments with Industrial Internet of Things (IIoT) data streams leverage ISO 15926's upper ontology to extend condition-based predictive maintenance architectures, incorporating open standards for enhanced interoperability in smart factories.[69] Community-driven efforts have advanced ISO 15926 implementation, with the POSC Caesar Association (PCA) updating its RDL to incorporate semantic representations of ISO 15926-4 (edition 4) on a cloud platform, promoting structured data sharing via OWL 2 ontologies.[70] These updates build on prior PCA RDL versions, integrating improvements like CFIHOS items to align with ISO/TR 15926 core reference data.[71] Complementing this, open-source tools such as the dot15926 Python library enable ontology modeling, semantic editing, and reasoning for ISO 15926-compliant data, including SPARQL querying of public endpoints and URI generation for reference classes.[72] In 2025, the ISO Technical Committee 184/Subcommittee 4/Working Group 3 continued active development on multiple parts, including Part 9, which focuses on implementation methods for integrating distributed systems via facades and web services to support lifecycle data exchange.[73] Additionally, a new work item was approved for ISO 15926-2 (ISO/AWI 15926-2) on November 10, 2025, aiming to update the conceptual data model for process plants.[74] Progress was also made on Part 100, which reached the Draft International Standard (DIS) stage in 2025, defining vocabulary terms for the ISO 15926 series.[75] Adoption of ISO 15926 is expanding in sustainable energy transitions within process industries, including hydrogen production plants, where its data integration capabilities aid in managing complex lifecycle information for decarbonization projects.[76]

Ongoing Challenges

Despite its potential, the adoption of ISO 15926 faces significant barriers, including the inherent complexity of its ontologies, which can be challenging for non-experts to navigate and apply effectively in engineering workflows.[77] Additionally, tool support remains limited, primarily confined to niche vendors and lacking broad, integrated solutions for multilevel ontology development and maintenance.[78] These factors contribute to slower industry uptake, particularly in sectors requiring rapid data integration without extensive specialized training.[79] The standard's development is incomplete in key areas, with Part 9 remaining under development to specify implementation methods for integrating distributed systems via facade architectures for triple data repositories.[73] Furthermore, the Reference Data Library (RDL) requires broader coverage to encompass emerging sectors like renewables, such as offshore wind and solar facilities, where current classes inadequately represent specialized equipment and lifecycle data.[49] Emerging needs highlight the necessity for enhanced integration with artificial intelligence and machine learning to support predictive analytics in process plants, enabling better handling of big data streams from sensors for real-time decision-making.[80] This involves harmonizing ISO 15926 data models with ML pipelines to address data quality and interoperability challenges in dynamic environments.[81] Future directions emphasize harmonization efforts with complementary standards, such as ISO 19650 for building information modeling (BIM) in civil engineering contexts, to facilitate seamless data exchange across plant and infrastructure lifecycles.[82] Similarly, alignment with semantic standards like the Financial Industry Business Ontology (FIBO) could extend applicability to financial and supply chain modeling, promoting reusable content across domains.[83] A potential expansion, building on the Industrial Data Ontology (formerly Part 14), may incorporate sustainability metrics to track environmental impacts in global operations.[49] Research gaps persist, particularly in empirical validation studies assessing return on investment (ROI) for small and medium-sized enterprises (SMEs), where resource constraints amplify implementation hurdles.[80] Scalability for global supply chains also lacks comprehensive analysis, with limited investigations into how ISO 15926 performs under high-volume, multi-vendor data exchanges across international boundaries.[81]

References

  1. ISO 15926-1:2004 - Industrial automation systems and integration
  2. ISO 15926
  3. [PDF] Ontology-based Interoperability - PCA Reference Data and Services
  4. [PDF] ISO 15926 "Life Cycle Data for Process Plant": an Overview - HAL
  5. [PDF] ISO 15926 - PERA.net
  6. ISO/TS 15926-4:2019 - Industrial automation systems and integration
  7. ISO/TS 15926-8:2011 - Industrial automation systems and integration
  8. ISO 15926-10:2019 - Industrial automation systems and integration
  9. ISO 15926-13:2018 - Industrial automation systems and integration
  10. ISO 15926 in Action: Production Grade Exchange of P&ID Drawings
  11. Semantic representation of ISO 15926-4 ed. 4 now available | PCA
  12. Standards - 15926.blog
  13. ISO 15926 "Life Cycle Data for Process Plant": an Overview
  14. ISO 15926-1:2004(en), Industrial automation systems and integration
  15. [PDF] Cost Analysis of Inadequate Interoperability in the U.S. Capital ...
  16. ISO 15926 | SpringerLink
  17. CAESAR research projects
  18. ISO 15926 - USPI-NL
  19. [PDF] Data Models for Home Services - Fruct
  20. ISO 15926-2:2003(en), Industrial automation systems and integration
  21. ISO/TS 15926-4:2007 - Industrial automation systems and integration
  22. https://www.iso.org/obp/ui/en/#%21iso:std:41329:en
  23. ISO/TS 15926-7:2011 - Industrial automation systems and integration
  24. ISO/TS 15926-12:2018 - Industrial automation systems and integration
  25. ISO/TS 15926-11:2023 - Industrial automation systems and integration
  26. ISO 15926-6:2024 - Industrial automation systems and integration ...
  27. Information about the 15926 projects
  28. OTC-35625-MS Automatic Daily Drilling Mud Report Processing ...
  29. 15926.org
  30. An upper ontology based on ISO 15926 - ScienceDirect.com
  31. [PDF] Modeling and Conformance Testing for the Engineering Information ...
  32. [PDF] ISO 15926 - bentleyuser.dk
  33. [PDF] ISO 15926 templates and the Semantic Web - W3C
  34. https://ieeexplore.ieee.org/document/10848585
  35. https://www.iso.org/obp/ui/en/#!iso:std:29556:en
  36. [PDF] ISO 15926-1 - iTeh Standards
  37. ISO 15926-2:2003 - Industrial automation systems and integration
  38. [PDF] ISO 15926-2 - iTeh Standards
  39. https://www.iso.org/obp/ui/en/#!iso:std:29557:en
  40. ISO/TS 15926-3:2009 - Industrial automation systems and integration
  41. [PDF] ISO/TS 15926-3 - iTeh Standards
  42. https://www.iso.org/obp/ui/en/#!iso:std:42875:en
  43. [PDF] ISO/TS 15926-4:2007 - iTeh Standards
  44. https://www.iso.org/obp/ui/en/#!iso:std:41329:en
  45. [PDF] ISO 15926 Reference Data Engineering Methodology - Ontolog
  46. Proposed levels for ISO 15926-2 - ResearchGate
  47. RDL Views - ISO 15926
  48. [PDF] TECHNICAL SPECIFICATION ISO/TS 15926-7 - iTeh Standards
  49. [PDF] Draft of Industrial Data Ontology Formerly known as “ISO 15926 Part ...
  50. [PDF] ISO 15926-14:2020(E) - READI
  51. https://www.iso.org/obp/ui/en/#!iso:std:57859:en
  52. PCA Services
  53. Intergraph® Supports the ISO 15926 Standard with the Release of ...
  54. ISO 15926-CCOM Transform Rules - MIMOSA
  55. Use of Asset Administration Shell Coupled with ISO 15926 to ... - MDPI
  56. [PDF] Position paper Fluor Corporation. For use Oil Gas Work Group - W3C
  57. [PDF] interoperability standard for process plants ISO 15926, and the data ...
  58. [PDF] Data exchange with ISO 15926 – A way to improve doing business
  59. Introduction — DEXPI P&ID Specification Version 1.4
  60. [PDF] DEXPI P&ID Specification
  61. [PDF] Capturing Equipment Data Requirements Using ISO 15926 and ...
  62. [PDF] Implementation of ISO 15926 - Engineering.com
  63. Using Semantic Technology to Auto-generate Reports: Case Study ...
  64. [PDF] The Evolution, Not Revolution, of Digital Integration in Oil and Gas
  65. Maritime Data Integration Using Standard ISO 15926 | International ...
  66. PCA Reference Data and Services
  67. [PDF] Towards an Open Standards-based Architecture for Condition ...
  68. News | PCA - POSC Caesar
  69. [PDF] Reference Data Libraries and Ontologies for Digitizing ... - MIMOSA
  70. TechInvestLab/dot15926: Ontology modeller, semantic data ... - GitHub
  71. Integration of distributed plant lifecycle data using ISO 15926 and ...
  72. Energy transition technology comes with new process safety ...
  73. (PDF) Re-engineering the ISO 15926 Data Model: A Multi-Level ...
  74. [PDF] Toward Ontology Evaluation across the Life Cycle
  75. On the application of software modelling principles on ISO 15926
  76. (PDF) Towards a Systematic Data Harmonization to Enable AI ...
  77. Big data and machine learning: A roadmap towards smart plants
  78. https://www.iso.org/obp/ui/ru/#!iso:std:79005:en
  79. [PDF] Reuse of Content from ISO 15926 and FIBO - Ontolog
User Avatar
No comments yet.