The OIIE specifications enable a major breakthrough in standards-based interoperability. Existing Commercial Off The Shelf (COTS), open-source and bespoke applications can be used in a supplier-neutral industrial digital ecosystem, which addresses both intra-enterprise and inter-enterprise activities. Collections of individual enterprise OIIE instances can be linked and managed by ecosystem administrators working for their respective enterprises, as they form and manage vendor-neutral extranets following their commercial and legal agreements with each other.
The OIIE Inter-Enterprise Connectivity Architecture that enables the creation and management of vendor-neutral extranets is depicted in the figure below.
The OIIE enables organizations in asset-intensive industries to bring their people, processes, systems, and software into alignment with each other following industry-standard OIIE Use Cases and using the industry-standard OIIE Intra and Inter Enterprise Connectivity Architectures. Included business functions span both the Secondary Business Process (Asset Lifecycle Management) and the Primary Business Process (Operations Management). Engineering, Design, Procurement, Construction, Operations, and Maintenance activities can be included as more OIIE Use Cases are developed and managed in collaboration with industry associations providing best practices in these domains.
The OIIE Intra-Enterprise Connectivity Architecture is depicted in the figure below.
The OIIE is an outgrowth of the OpenO&M Initiative, which is a collaboration between ISA, MESA/B2MML, OAGi, OPC, and MIMOSA, which are all industry Standards Developing Organizations (SDOs). Individual participating organizations continue to develop and manage their own specifications and standards, but make an effort to align them with each other. Collaboratively developed specifications such as the ISBM and CIR are owned and managed by MIMOSA along with the OpenO&M Initiative website. Other industry associations (which may not be SDOs) collaborate by helping to build and manage OIIE Use Cases framed around their best practices.
- The OIIE follows the Purdue Reference Architecture providing a supplier-neutral, solutions architecture, which enables organizations to directly implement their own OIIE instances.
- The OIIE is driven and defined by a portfolio of industry-standard OIIE Use Cases, which are broken down into reusable, standardized OIIE Scenarios and Events, following the OIIE Standard Use Case Architecture.
- The standardized OIIE Scenarios and Events leverage a portfolio of published, supplier-neutral standards and specifications, which are used in a repeatable, scalable manner.
- Suppliers of COTS solutions build, license, and maintain their own OIIE adaptors, substantially eliminating the need for traditional systems integration.
- Adaptors for bespoke or obsolete applications and systems can be developed on a cost-effective basis using standardized scenarios, adaptor development methods, and adaptor development kits.
- OIIE Administration is supplier neutral and logically independent from individual applications and supplier-specific, proprietary ecosystem administration.
- The OIIE leverages MIMOSA’s industry-leading CCOM information model for Life-cycle Asset Information Management and Associated Technical Master Data Management.
- The OIIE enables the use of Cloud Infrastructure, Infrastructure as a Service (IaaS) and Software as a Service (SaaS) implementation models.
- OIIE implementations can be more secure, adaptable, sustainable, and cost-effective than most traditional systems integration efforts, due to the standardized development, testing, and maintenance process, shared by the industry.
- The OIIE is developed and published by MIMOSA, in cooperation with multiple other industry standards organizations and key suppliers of industrial equipment, systems, software, and services.
More details about the OIIE are available on the MIMOSA and OpenO&M Initiative websites.
The OIIE Oil and Gas Interoperability (OGI™) Pilot
The OIIE OGI Pilot is implemented as an instance of the OIIE, using Oil and Gas industry asset classes, which are also applicable to many other asset-intensive industries, associated with critical infrastructure. The OIIE OGI Pilot demonstrates how the OIIE works and provides the Industry Interoperability Testbed, largely eliminating the need for integration testing in individual implementations of the OIIE. The OIIE OGI Pilot is managed by MIMOSA and the instance information is owned by MIMOSA, while the participating applications and systems remain the property of their respective developers.
The OIIE Interoperability Lab
The OIIE Interoperability Lab at the University of South Australia facilitates the piloting effort supporting the development, validation and publication of the associated specifications using the standard OIIE Development and Piloting Processes. The lab is managed by the Industrial AI Research Centre, as the OIIE includes AI elements for describing Digital Twins, while the Digital Ecosystem provides a standard “collection network” for data that is used for analytics that will often be based on AI.
ISO 18101
ISO TS 18101-1 was published by ISO, the first week of June 2019, as the 1st Part of a multi-part ISO standard. It has been published as a TS, rather than an IS, simply because of the speed of evolution of the relevant included specifications and standards.
The Foreword of ISO TS 18101-1 stipulates that it is fully based on the OIIE and uses the OIIE OGI Pilot to validate OIIE Use Cases before they are to be included in the following parts of the standard. This provides a clear path forward for asset-intensive industries to accelerate their digital business transformation using the OIIE, with an approach that can also be enforced through international contract law.
ISO TS 18101-1 may be purchased and downloaded from the ISO Store.