A Representation and Implementation of Process

International Conference on Product Lifecycle Management

1

A Representation and Implementation of Process Plant Models using OWL and ISO 15926 Byungchul Kim*, Hans Teijgeler **, Duhwan Mun***, Danhe Sun*, Jinsang Hwang****, Soonhung Han* * Department of Mechanical Engineering, KAIST ** OntoConsult *** Corresponding Author, MOERI/KORDI 171 Jang-dong, Yuseong-gu, Daejeon, 305-343, Republic of Korea FAX: +82-42-869-0405, TEL: +82-42-869-0402 ****PartDB Co., Ltd. E-mail: [email protected]; [email protected]; [email protected]; [email protected]; [email protected]; [email protected] Abstract: ISO 15926 is an international standard for the representation of process plant lifecycle data. However, it is not easy to implement Part 2 Data Model and Part 4 Initial Reference Data Library because of their complexity in terms of data structure and a shortage of related development toolkits. In order to overcome this problem, ISO 15926 Part 7 is under development. This part of the standard specifies implementation methods for sharing and exchange of process plant data across its lifecycle by utilizing OWL and Web Services. For the application of ISO 15926 Part 7, we first discuss how to represent technical specifications of process plant equipment by utilizing the user defined Reference Data Library and Object Information Model with an example of reactor coolant pumps located in the reactor coolant system of an APR 1400 nuclear power plant. An implementation plan of ISO 15926 Part 7 is also addressed after analyzing enabling technologies and surveying related tools. Keyword : Implementation Method, Integration, ISO 15926-7, Lifecycle Data, OWL, Process Plant, RDF, Semantic Web, SPARQL, Web Service, XML

1

Motivation

Various organizations geographically dispersed with different cultures and languages participate across plant lifecycle. This trend is being accelerated due to globalization of market and increase in competition among companies. Therefore it becomes important to effectively manage plant data and share them among different organizations locating in different places and participating at different lifecycle phases starting from design and finishing to demolition through construction, and operation and maintenance. Especially, for efficient operation and maintenance of process plants, operators should be provided with easy access to plant data created in earlier phases such as the design and construction stages. Although each organization reaches a certain level of

Copyright © 200x Inderscience Enterprises Ltd.

Byungchul Kim, Hans Teijgeler, Duhwan Mun, Danhe Sun, Jinsang Hwang, Soonhung Han automation, data sharing among organizations is poor. This necessitates manual redefinition of the plant model, which can lead to the introduction of errors in the process. A typical method to facilitate the handover of nuclear power plant information is the construction of a neutral model-based data warehouse and sharing plant data among different application systems at different lifecycle phases. Applicable neutral models for the nuclear energy industry include GPM (Generic Product Model)[2,3] developed by Hitachi, Japan through PlantCALS, PlantEC, VIPNET Programs[1]; ISO 10303 STEP[4,5]; and ISO 15926 Process Plants [6,7,8]. The GPM is specialized for nuclear power plants, in contrast with ISO10303 AP221, AP227 and ISO15926, which can be used in any plant facility. Studies on constructing a neutral data warehouse based on GPM and implementing its application S/Ws for Korean nuclear power plants have been conducted[9,10,11]. However, since it is not an international standard, GPM has limitations in terms of wide usability and interoperability. ISO 15926 is an international standard for the representation of process plant lifecycle data including oil and gas production facilities[12]. Major parts of ISO 15926 are Part 2 and Part 4. ISO 15926 Part 2 provides a generic data model that is stable and flexible for the representation of process plant data, enabling integration of information [6]. ISO 15926 Part 4 specifies the initial set of common reference data items, which can be used to record information about process plants[7]. Based on ISO 15925 Part 4, reference data as a de-facto standard in a particular industry is constructed, followed by reference data specific for companies or organizations. The ISO 15926 standard, which is supported by several plant design systems, has been applied in studies aimed at supporting the lifecycle data of naval ships[16] and building a plant equipment data library [17]. Yoon developed a data dictionary for 45 types of equipment comprising a reactor coolant system (RCS) by utilizing ISO 15926 Part 2 and Part 4 instead of GPM[13]. However, it is not easy to implement application S/Ws by utilizing ISO 15926 Part 2 data model and Part 4 initial reference data, for the following reasons: z The ISO 15926-2 data model is complex and does not provide high level modeling constructs. Therefore, it is difficult for application S/W developers to use the ISO 15926-2 data model. For example, expressing “equipment e has an indirect property of p of which unit is u.” requires instantiating several Part 2 entity data types, referencing Part 4 reference data, and specifying the relations between them. z Since the ISO 15926 data model is expressed in EXPRESS language[14], there are limitations in available toolkits and developers. The T25 Oil, Gas, Process and Power team within the ISO TC184/SC4/WG3 is developing ISO 15926 Part 7, which provides an implementation method for OWL (Ontology Web Language)–based exchange and integration of process plant data. ISO 15926 Part 7 is in CD/TS (committee draft/technical specification) ballot (as of February, 2008). ISO 15926 Part 7 provides predefined high-level modeling constructs called templates, enabling convenient implementation of plant data exchange and integration. Furthermore, since templates and object information models of ISO 15926 Part 7 are expressed in OWL, there are many developers and various development toolkits [15] available for the ISO 15926 Part 7-based implementation.

A Representation and Implementation of Process Plant Models using OWL and ISO 15926 The present study aims at providing ISO 15926-based representation of nuclear power plant data and sharing them among different organizations across plant lifecycle, focusing on the application of resources specified by ISO 15926 Part 7. First, the implementation concept of ISO 15926 Part 7 and its related technologies are introduced. The authors discuss the OIMs (object information model)s for the equipment in the RCS of APR 1400 nuclear power plant defined by the specialization of templates provided by ISO 15926 Part 7. According to the defined OIMs, scenarios for sharing equipment data among participating organizations across the plant lifecycle and an implementation plan of application S/Ws are provided at the end of the paper.

Equipment Specifications

Configuration of Plant system

Figure 1

2

Shape data

Nuclear power plant data representation and sharing based on ISO 15926

Representation and sharing of plant models using ISO 15926 Part 7

ISO 15926 Process Plants is composed of Part 2, Part 4, and Part 7, as depicted in Fig. 2. ISO 15926 Part 2 is a generic data model with 201 entity data types, ISO 15926 Part 4 specifies core classes, object models, and reference individuals, and 15926 Part 7 provides an otology-based implementation method. Plant data is represented by templates and OIMs of ISO 15926 Part 7, which are expressed in OWL. The template, an instance of class_of_multidimensional_object entity data type defined in ISO 15926 Part 2, is a standard structure that relates instances of ISO 15926-2 entity data types to represent plant information. The OIM for a class is an ontology that defines the standard types of lifecycle information, defined by a set of specialized templates, in which that class plays a direct role, and with references to the ISO 15926 Part 4 reference data. In the ISO 15926 standard, information is described by a complex relationship between objects that exist independently from that relationship. That complex relationship is represented by a template. Templates have two representation forms: longhand templates and shorthand templates. Longhand templates are defined using instances of ISO 15926-2 entity data types. They are normally not instantiated but used

Byungchul Kim, Hans Teijgeler, Duhwan Mun, Danhe Sun, Jinsang Hwang, Soonhung Han for definition purposes. Shorthand templates, on the other hand, are n-ary relationships, properties of which refer to the variant parts of the companion longhand template. They are instantiated and used for the representation of information about individuals. Each shorthand template shall have an rdfs:isDefinedBy relation with it companion longhand template. As an example of templates provided by ISO 15926 Part 7, the template ST3401 used for representing an indirect property of an object is diagrammed in Fig. 3. ISO15926-7 (Implementation Method) Represented by

Distinct Process Plant Data

Confirms to

Template Classes

References ISO15926-2(DATA MODEL) OIMs

Thing subClassOf

subClassOf

Possible Individual

ISO15926-4(IRDL)

Abstract Object subClassOf

subClassOf

subClassOf

PUMP Relationship

Class

Multidimensional Object

subClassOf

subClassOf

ClassOf Relationship

Template

NOZZLE

Figure 2

VEHICLE

HEAT TRANSFER EQUIPMENT VESSEL

…

Information model structure of ISO 15926

Advantages of ISO 15926 Part 7 templates are, from the viewpoint of developers, that they provide developers with a convenient way of composing Part 2 entity data types into application models, and representing high level concepts easily. The application S/W development can be separated from information model development. In that respect, ISO 15926 Part 7 templates play the same role as the API (Application Programming Interface) used for S/W programming. An OIM is defined by the inheritance and specialization of a template, referring to reference data in order to represent the kind of lifecycle information that possibly may apply to the members of a specific owl:Class. The OIM for the indirect property Design Pressure of Pump class can be specified by the inheritance of the ST-3401 template, as shown in Fig. 4. After OIMs are defined, real plant data is represented according to the OIMs. ISO 15926 Part 7 is based on the use of OWL. ISO 15926 Part 2 data model and Part 4 initial reference data should therefore be mapped in OWL form for application of the implementation method of ISO 15926 Part 7. The method to convert into OWL format

A Representation and Implementation of Process Plant Models using OWL and ISO 15926 has been dealt with in detail by other authors[18,19]. Materials regarding ISO 15926 Part 7 can be found at the 15926.ORG homepage[20] and the InfowebML homepage[21].

Figure 3

3

Shorthand template ST-3401 and its companion longhand template LT-3401 [21]

Essential components for implementation of ISO 15926 based on ontology

While the template of ISO 15926 Part 7, which is an upper level of a modeling object, makes its implementation easy, new challenging issues must be confronted when it is represented by OWL, which is an ontology language. For the implementation of ISO 15926, it is necessary to understand not only the data model in ISO 15926 Part 2 but also

Byungchul Kim, Hans Teijgeler, Duhwan Mun, Danhe Sun, Jinsang Hwang, Soonhung Han OWL, a technology used for implementing the Semantic Web and Web Services. In this section, various components for implementing the Semantic Web will be overviewed.

Physical Object

Pump has an indirect property of Design Pressure of which unit is psia.

isSubClassOf Inanmiate PhysicalObject

ClassOf IndirectProperty

Scale

type

isSubClassOf

type

Design Pressure

Pump

propertyType

psia

XmlSchemaFloat

numericalValue

possessor

unitOfMeasure

isPossessorIn ST-PUMP-3401-001

ST-3401

isSubClassOf

Figure 4

Definition of OIM by utilizing a specialized ST-3401 template class

3.1 OWL OWL is a Web ontology language and one of the Recommendations of the World Wide Web Consortium (W3C) for the Semantic Web. OWL is designed for use in applications that need to process the content of information instead of merely presenting information to users [22, 23]. OWL provides three increasingly expressive sublanguages designed for use by specific purposes: OWL Lite, OWL DL, and OWL Full. OWL is based on Extensible Markup Language (XML), which makes it possible to define the schemas of user-defined tags, and the Resource Description Framework (RDF), which enables flexible representation of data. In OWL, a class is a type of owl:Class, and an object, which is a member of a class, is a type of owl:Thing. Most entities defined in ISO 15926 Part 4 are defined as both subtypes of the classes and members of other meta classes defined in ISO 15926 Part 2. For this reason, the version of OWL that is used to represent ISO 15926 standard-based data is OWL-Full.

A Representation and Implementation of Process Plant Models using OWL and ISO 15926

3.2 SPARQL SPARQL is a query language and data access protocol for the Semantic Web, defined in a W3C Recommendation [24]. SPARQL is basically composed of three parts. The SELECT clause is used to define the data items of RDF data that will be returned by a query. The FROM clause identifies the RDF data against which the query will be run. The WHERE clause specifies the conditions used by a query. The reason that SPARQL is attracting increasing attention is that it enables users to easily query data and obtain a result in the Semantic Web. The following is an example of SPARQL. PREFIX table: SELECT ?name FROM WHERE { ?element table:name ?name. }

3.3 Web Services Web Services is a distributed component technology that is based on XML and the Internet. Web Services comprise a number of standard specifications, the most basic specifications among them being the Web Services Description Language (WSDL), the XML Schema, the Simple Object Access Protocol (SOAP), and the Universal Description, Discovery and Integration (UDDI) [25]. In addition, they are written in XML. The relationship among them is shown in Fig. 5. Service Broker UDDI UDDI

i WSDL WSDL

f(x) Service Requester

Figure 5

Web Services

WSDL WSDL

SOAP SOAP

Service Provider

Byungchul Kim, Hans Teijgeler, Duhwan Mun, Danhe Sun, Jinsang Hwang, Soonhung Han WSDL is a language that describes the interfaces of Web Services. A WSDL file usually specifies the data types, the messages, the protocol bindings, and the interfaces for interacting with Web Services. Data types are specified by XML Schema. XML Schema is an XML-based language that defines the structure of an XML file. A service requester of a Web Services needs a WSDL file of the Web Services in order to identify the functions that the Web Services provides. WSDL has a similar role to that of Interface Description Language (IDL), which is used to describe the interfaces of CORBA, and Microsoft IDL (MIDL), which is used to describe those of COM. SOAP describes the protocol used to exchange messages of Web Services over a computer network. SOAP enables Web Services to exchange an XML file that contains the input and output of the Web Services. UDDI plays a role of a service registry, which connects a service requester with a service provider.

4

Data dictionary for equipment in a reactor coolant system

As a first step of establishing a data dictionary for the equipment in a RCS, OIMs for reactor coolant pumps (RCPs) are defined. Technical specifications of RCPs are listed in Fig. 6.

1-431-M-PP02A

1-431-M-PP01A

1-431-M-PP03A

1-431-M-PP04A

RCS

Figure 6

Technical specifications of reactor coolant pumps

For the exchange of technical specifications of plant equipment, ISO 15926 Part 4 could be extended for reflecting classes, object models, and reference individuals specific to an application domain if necessary. For examples, the RCP should be added as a subclass of the Coolant Pump class of ISO 15926 Part 4, as shown in Fig. 7. After extending ISO 15926 Part 4 initial reference data, OIMs for the application domain are defined by utilizing templates of ISO 15926 Part 7. For the OIMs, the reference data library as well as templates is used. For example, the OIM for representing

A Representation and Implementation of Process Plant Models using OWL and ISO 15926 "RCP has an indirect property Design Flow Rate of which unit is gpm." can be defined by inheriting the ST-3401 template, as shown in Fig. 8. DEFINED IN THE RDL PUMP A liquid pressure increasing device that is an artefact intended to add energy to a pumped fluid in order to increase the pressure required for the process in which the pump is in operation. COOLANT PUMP A centrifugal pump that is used or intended to be used to pump coolant.. SPECIALIZATION IN THE RCS_RDL REACTOR COOLANT PUMP A coolant pump and a water-sealed pump which circulates the coolant through the reactor coolant system.

Figure 7

Definition of Reactor Coolant Pump class as a subclass of Coolant Pump class

Byungchul Kim, Hans Teijgeler, Duhwan Mun, Danhe Sun, Jinsang Hwang, Soonhung Han Figure 8

5

An OIM for representing Design Pressure property of Reactor Coolant Pump

Implementation Plan

In future work, we will define OIMs for all of the equipment of the RCS, and implement a Façade and Web Services for sharing the technical specifications of equipment in the RCS according to the implementation method of ISO 15926 part 7. For the implementation of the system, the data exchange scenario shown in Fig. 9 is assumed. First, the technical specifications of equipment located in the system of KOPEC is exported, and then mapped to the data transfer file. The specifications in the file are populated to the KOPEC Façade, and then handed over to the KHNP Façade. [Implementation Scope] ISO 15926 standard

Data model (part 2) Templates (part 7)

Reference data (part 4)

User-defined reference data

OIM (part 7)

User-defined OIMs

Façade schema (part 7)

Industry & User Org.

User-defined document type RDF / XML

RDF / XML Data Transfer File

Map

Populate

KOPEC Façade

Handover

Data Transfer File

Query

Import

KHNP Façade

Query KHNP system

KOPEC system Ontology Browser

Check Access rights

CPF Server

*CPF = Confederation of Participating Facades

Figure 9

Data exchange scenario of nuclear power plant equipment

The following is the implementation environment under consideration for the Façade and its Web Services which are based on ISO 15926 Part 7. z OWL editor: SWOOP 2.3 beta z OWL API: JENA API z SPARQL query: JENA API z Web Service framework: Apache Axis2 z Development environment: Eclipse z Database: MySQL z DGN data extraction API: ODA [28]

A Representation and Implementation of Process Plant Models using OWL and ISO 15926 A standalone translator, which has capability of a map function that generates a data transfer file from the DGN file, is implemented using ODA. ODA is the API for the DGN data input and output. The populate function, which saves the data transfer file to the KOPEC Façade, is implemented as Web Services by referring to the WSDL file provided by ISO 15926 Part 7. Apache Axis2 is used to implement the Web Services. JENA API affords storage and management of the plant ontology data, because it provides integration modules with commercial RDBMS. The architecture of the façade and data sharing system of the equipment of a nuclear power plant to which ISO 15926 part 7 is implemented is shown in Fig. 10. They consist of a database, the API for the database and ontology, the Web Services, the control logics, the interfaces for the Web Services, the ontology for the equipment, and the Java classes. Data model (part 2)

Reference data (part 4)

Templates (part 7)

RCS_RDL.owl

RCS_OIM.owl

RCS_Doc.owl

RCS_RDL.java

RCS_OIM.java

RCS_Doc.java

Ontology Layer

….

Internal S/W Layer

Web Service Interface (WSDL)

Web Service, Control Logic (Java Code) Jena API Model

JDBC

RDBMS

Figure 10 Architecture of ISO 15926 –based data sharing system for nuclear power plant equipment

Under the leadership of Fiatech, the ADI project [26,27] is developing a toolkit for the implementation of ISO 15926 Part 7. The results of this study may be helpful for implementing ISO 15926 Part 7.

6

Conclusions

As an initial study for the implementation of ISO 15926 Part 7, the component technologies of ISO 15926 Part 7 have been analyzed and their results have been explained. The implementation architecture of ISO 15926 Part 7 has been introduced, and the results that define a data dictionary for the reactor coolant pump, a component of the RCS, by inheriting and specializing the templates and OIMs of ISO 15926 Part 7 have been discussed.

Byungchul Kim, Hans Teijgeler, Duhwan Mun, Danhe Sun, Jinsang Hwang, Soonhung Han From the view point of product lifecycle management, contribution of the present study is that representing plant data with ontology, it sets a foundation for automatic semantic processing and sharing of plant data in the web services environment where application, process, and data integration among distributed information systems is supported. Study on the application of ISO 15926 Part 7 to the representation and sharing of the configuration data of RCS as well as the technical specifications of RCS is also necessary. In addition, it is necessary to participate in the ADI project led by Fiatech in order to find a way to share the research results of the project.

References 1 2 3 4

5 6

7

8

9

10

11

12 13

14

15

VIPNET project, http://www.openknow.com/vipnet/, 2005. Y. Yoshinari, T. Yoshinaga, K. Shibao, M. Igoshi, F. Kimur, “Virtual Production Enterprise Network (MATRIX/VIPNET)”, IMS 0231 Summary Report, IMS Promotion Center, 2003. Yuuichi Koizumi, Hiroshi Seki, Taesung Yoon, “Data Integration Framework Based On a Generic Product Model”, Proceedings of the TMCE 2004, Lausanne, Switzerland, 2004. ISO, Industrial automation systems and integration – Product data representation and exchange – part 221: Application Protocol: Functional data and their schematic representation for process plant, ISO/DIS 10303-221. ISO, Industrial automation systems and integration – Product data representation and exchange – part 227: Application Protocol: Plant spatial configuration, ISO 10303-227. ISO, Industrial automation systems and integration – Integration of lifecycle data for process plants including oil and gas production facilities – part 2: Data model, ISO:2003 15926-2, 2003. ISO, Industrial automation systems and integration – Integration of lifecycle data for process plants including oil and gas production facilities – part 4: Initial reference data, ISO/TS 15926-4, 2007. ISO, Industrial automation systems and integration – Integration of lifecycle data for process plants including oil and gas production facilities – part 7: Implementation methods for the integration of distributed systems, ISO/ CD TS 15926-7, ISO/TC 184/SC4/WG3 N2382, 2007. Duhwan Mun, Jinsang Hwang, Soonhung Han, Hiroshi Seki, Jeongsam Yang, "Sharing product data of nuclear power plants across their lifecycles by utilizing a neutral model”, Annals of Nuclear Energy, Vol. 35, No. 2, pp. 175-186, 2008. Duhwan Mun, Soonhung Han, Chan-Cook Park, Youngju Kang, Inhan Kim, Jaero Yoon, Taesung Yoon, “Constructing a neutral data warehouse for sharing product data of nuclear power plants”, PLM06 Conference, pp. 137~151, 2006 K. Cho, C. Park, “Implementation of the KNGR class library based on the GPM and semantic network for co-design”, Computer-Aided Design and Application, Vol.2, No.1, 2005 David Leal, "ISO 15926 "Life cycle data for process plant": An overview", Oil & Gas Science and Technology - Rev. IFP, Vol. 60, No. 4, pp. 629-637, 2005. Jinhyun Yoon, Duhwan Mun, Soonhung Han, Kwangjong Cho, “Development of the ISO 15926-based Classification Structure for Nuclear Plant Equipment (In Korean)”, Transactions of the Society of CAD/CAM Engineers, Vol. 12, No. 3, 2007. ISO, Industrial automation systems and integration — Product data representation and exchange - Part 11: Description methods: The EXPRESS language reference manual, ISO10303-11, 2004 Semantic Web Tool, http://esw.w3.org/topic/SemanticWebTools#preview, 2007.

A Representation and Implementation of Process Plant Models using OWL and ISO 15926 16 17 18

19 20 21 22 23 24 25

26 27 28

Tor Arne Irgens, Trine Hansen, Jochen Haenisch, “PLCS Pilot for New Norwegian Frigates”, PDT Europe 2004. Tektonisk ShareCAT, http://www.sharecat.com, 2007. Tore Christiansen, Marius Jensen, David Leal, David Price, Magne Valen-Sendstad, “Representing the ISO 15926-2 Core Data Model in OWL” , http://www.olf.no/?30089.pdf, 2005. Tore Christiansen, Marius Jensen, Magne Valen-Sendstad, “Defining ISO 15926-4 Reference Data Library classes in OWL”, http://www.olf.no/?30090.pdf, 2005. 15926.ORG Web site, http://15926.org/home/tiki-index.php, 2007. InfowebML: OWL-based Information Exchange and Integration based on ISO 15926, http://www.infowebml.ws, 2007. W3C OWL Web site, http://www.w3.org/2004/OWL/, 2007. OWL Web Ontology Language Guide: http://www.w3.org/TR/owl-guide/, 2007. SPARQL Query Language for RDF, W3C Recommendation, 15 January 2008 Byungchul Kim and Soonhung Han, “Retrieval of CAD Model Information Using Web Services”, Proceedings of Design Engineering Workshop (DEWS) 2007, 7th IJCC JapanKorea CAD/CAM Workshop, Tokyo University, pp. 26-29, July 2007. Fiatech ADI Project Web Site, http://www.fiatech.org/projects/idim/iso15926.html, 2007. ADI Project Overview, http://www.fiatech.org/pdfs/projects/ADI_PROJECTPLAN.pdf, 2007. Open Design Alliance, http://www.opendesign.com/, 2008