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. In that AP we saw, for the first time, an Annex M with a list of standard instances of the AP 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 STEPlib activities a group of approx. Electrical, Piping, Rotating equipment, etc.
|Published (Last):||11 May 2018|
|PDF File Size:||15.14 Mb|
|ePub File Size:||12.45 Mb|
|Price:||Free* [*Free Regsitration Required]|
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.
In that AP we saw, for the first time, an Annex M with a list of standard instances of the AP 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 STEPlib activities a group of approx. Electrical, Piping, Rotating equipment, etc. The development of STEPlib was extended with many additional classes and relationships between classes and published as Open Source data.
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.
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 This merging process has been finished. In the work on an earlier version of Part 7 started. Part 7 passed the first ISO ballot by the end of , and an implementation project started. However, it was decided then to split Part 7 into more than one part, because the scope was too wide.
The full report is over pages. Please improve this article by removing excessive or inappropriate external links, and converting useful links where appropriate into footnote references. The purpose of ISO is to facilitate integration of data to support the lifecycle activities and processes of production facilities. Part 2  - Data Model. Part 3 - Reference data for geometry and topology. Parts 4  - Reference Data, the terms used within facilities for the process industry.
Part 7  - Integration of life-cycle data for process plants including oil and gas production facilities - Part 7: Implementation methods for the integration of distributed systems: Template methodology. Part 10 in development - Test Methods. Part 11 in development - Industrial Usage Guidelines. 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 The purpose of ISO 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. For validation and reasoning purposes all are represented in First-Order Logic as well. Each participating computer system maps its data from its internal format to such ISO-standard Node and Template instances.
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. May
ISO 15962 PDF