DOCSLIB.ORG

Openo&M Oil & Gas Industry Use Cases with Scenarios and Enabling

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Openo&M Oil & Gas Industry Use Cases with Scenarios and Enabling OpenO&M Oil & Gas Industry Use Cases with Scenarios and Enabling Technology Ken Bever MIMOSA CTO [email protected] +1 (513) 276-4105 1 Use Cases 1 Handover Information from EPC to O/O 2 Engineering Upgrades to O&M 3 Field Changes to Plant/Facility Engineering 4 Up-to-Date Product Data Library (from On-line RDL) 5 O&M Asset Configuration Updates 6 Preventive Maintenance Triggering 7 (Semi-) Automatic Triggering of Condition Based Maintenance (CBM) 8 Early Warning Notifications 9 Incident Management/Accountability 10 Information Provisioning of O&M Systems 2 Systems Requiring Interoperability AHMS Asset Health Management System MES Manufacturing Execution System CIR Common Interoperability Registry MMS Maintenance Management System CMS Condition Monitoring System OPM Operational Performance Modelling & Optimization System DCS Distributed Control System ORM Operational Risk Management System DMS Document Management System PDM Product Data Management System EAM Enterprise Asset Management System PLC Programmable Logic Controller ENG Engineering Schematic Topology and PORT Enterprise KPI/Event Portal Instrumentation Tag Configuration Management System ERM Enterprise Risk Management System PSMS Process Safety Management System ERP Enterprise Resource Planning System QMS Quality Management System HMI Human-Machine Interface (Operator Console) REG O&M Product, Structure, Asset Registry with System Standardised Data Dictionary and Taxonomy ISBM Information Service Bus Model SCADA Supervisory Control and Data Acquisition LIMS Lab Information Management System SHES Safety, Health, and Environmental System 3 OpenO&M Systems Landscape Data Flow Diagram with Use Case Scenarios Open Standards Which Define Data Content for Information Exchange OAGIS, CIDX OpenO&M Common Interop. Registry ISO 15926 / iRING B2MML B2MML & PRODML MIMOSA, B2MML & PRODML NOTE: Arrows with Do Not MIMOSA Connect Directly to Another System Publish Information OPC Which Can Be Subscribed to Fieldbus (Foundation, Profibus, etc.) By Multiple Systems 4 2 28 3 6 9 1 27 23 24 19 21 4 5 20 22 11 31 14 15 16 12 10 17 18 13 29 30 8 26 7 25 Scenarios No. Method Data From System To System As-Designed/As-Built Engineering 1 Publish ENG REG-STRUCTURE Network/Segment/Tag As-Designed/As-Built Engineering 2 Publish REG-STRUCTURE O&M Network/Segment/Tag 3 Publish As-Maintained Engineering Network/Segment/Tag O&M O&M ENG, 4 Publish As-Built Engineering Asset REG-ASSET CONSTRUCT 5 Publish As-Built Engineering Asset REG-ASSET O&M 6 Publish As-Maintained Engineering Asset O&M O&M 7 Pull OEM Model OEM PDM REG-PRODUCT 8 Pull OEM Model REG-PRODUCT O&M 9 Publish OEM Model O&M O&M 10 Push Asset Removal/Installation CMS MMS 11 Publish Asset Removal/Installation MMS O&M 7 Scenarios (cont.) No. Method Data From System To System 12 Pull Usage Readings CONTROL MMS, ORM 13 Publish Usage Readings CONTROL MMS, ORM 14 Push CBM Advisories ORM MMS 15 Pull Maintenance Work Status/Work History MMS O&M 16 Publish Maintenance Work Status/Work History MMS O&M ERP, ERM, PORT, 17 Pull Maintenance KPIs MMS MES, OPM ERP, ERM, PORT, 18 Publish Maintenance KPIs MMS MES, OPM ERP, ERM, PORT, 19 Pull Performance KPIs ORM OPM ERP, ERM, PORT, 20 Publish Performance KPIs ORM OPM ERP, ERM, PORT, 21 Pull Significant ORM Events ORM OPM ERP, ERM, PORT, 22 Publish Significant ORM Events ORM OPM 8 Scenarios (cont.) No. Method Data From System To System ERP, ERM, PORT, 23 Pull OPM KPIs OPM MES ERP, ERM, PORT, 24 Publish OPM KPIs OPM MES 25 Publish Product/Part Engineering Change Advisories OEM PDM REG-PRODUCT 26 Publish Product/Part Engineering Change Advisories REG-PRODUCT O&M 27 Publish Plant/Process Change Advisories ENG REG-STRUCTURE 28 Publish Plant/Process Change Advisories REG-STRUCTURE O&M CONTROL, ORM, 29 Pull Current Operating Data and Events CMS OPM CONTROL, ORM, 30 Publish Current Operating Data and Events CMS OPM 31 Pull Historical Operating Data and Events HIST ORM, OPM 9 OpenO&M Systems Landscape Data Flow Diagram with Use Case 1 scenarios 1 4 10 Use Case 1 – Handover EPC to O/O • Handover of As-Designed, As-Engineered and As-Built Information from Engineering, Procurement, and Construction (EPC) Contractor(s) to Owner/Operator – A core problem for Owner/Operators (O/O), vendors and systems implementers is the lack of good mechanisms for managing the needed information exchanges between EPC activities and the O&M related systems, applications and technologies. • Information to Be Exchanged: Information is needed to properly bootstrap O&M systems with as-designed functional segment data (including P&ID diagram information of network topologies, breakdown structures and process/equipment data sheets), and asset and installation data. Need to have access to “tag” databases which identify where sensors have been installed for control and monitoring, related to the process equipment they are monitoring, and the meta-data about them (tag ID, update frequency, engineering unit, etc.). • Scenarios Activated: 1, 4 11 Use Case 1 – Handover EPC to O/O Scenarios • The first scenario is (2) Publish As-Designed / As-Built Engineering Network / Segment / Tag data from REG- STRUCTURE to O&M . This scenario details the batch exchange of structural design information that forms part of the registry master data required by most O&M systems. This information originates from the Structural Registry (which stores Plant Breakdown Structures, Logical P&IDs and PFDs) and is sent to all applicable O&M systems. • The second scenario is (5) Publish As-Built Engineering Asset data from REG-ASSET to O&M . This scenario is similar to the previous, but details the exchange of asset and installation information. This information originates from the Asset Registry and is sent to all applicable O&M systems. 12 Use Case 2 – Engineering Upgrades • Recurring Updates – Send Open Engineering Upgrades to O&M: Once a site is operational, plant or facility engineering and design organizations may continue to make changes to the as-designed information models on a recurring basis . These changes can be driven by the need to operate more efficiently or with greater safety in support of the originally intended process supporting the same product mix or they can be associated with the need to change the process to yield new products, not envisioned in the original design. Once the new design information is developed it may be managed in several different ways depending on the driver for the change and the associated priority it will be assigned. Depending on the nature and scale of the changes involved, the actual work may be performed by the maintenance staff, a maintenance contractor or a construction contractor. In all cases, some type of appropriate feedback loop must be provided to ensure that the status is known and shared by Engineering Reference Databases and O&M systems. • Information to Be Exchanged: Need to propagate changes to functional segment data, including P&ID diagram information related to process/equipment data sheets with guaranteed delivery despite network hiccups. • Scenarios Activated: 1, 2, 4, 5 13 Use Case 3 – Field Changes • Field Engineering – Changes Sent To Plant or Facilities Engineering: In a perfect world, fully leveraging best practices, all engineering changes would flow through the enterprise design engineering and approval systems on a “waterfall” basis, even if the actual design work is done locally or through an independent contractor. All such engineering changes would be fully reconciled and rationalized before the work was actually done and the integrity of the Engineering Reference Databases would be ensured as a specialization of use case 2. Unfortunately, there are many situations where this does not occur (and may be impractical). This frequently results when a centralized plant or facilities engineering organization is overwhelmed by emergent situations and the plant or facilities manager must take responsibility for the situation without the ideal level of centralized support. Lack of proper synchronization of this work can result in anomalies with respect to the system of record for the engineering information, since in this case, the most up-to-date as-designed information is flowing from the field to the enterprise, rather than the other way around. • Information to Be Exchanged: The information is very similar to that which is contained in Use Case 2, but it now needs to flow from the field to the Engineering Reference Database so that the systems can be kept in sync. Need to propagate changes to functional segment data, including P&ID diagram information related to process/equipment data sheets with guaranteed delivery despite network hiccups. • Scenarios Activated: 3, 6 14 Use Case 4 – Online Product Data • Open On-line Product Data Library: All of the Use Cases contained in this document anticipate the on-line availability of appropriate product data libraries containing the detailed engineering reference information for makes and models of important classes of physical assets . Critical elements of ERM including both Operational Risk Management (ORM) and EH&S depend on the Enterprise Asset Management (EAM), Reliability Management (RM), Condition Based Maintenance (CBM) and ORM systems leveraging the most current product data. Manufacturers are often reluctant to publish some quality and reliability data about their products which is extremely important and this information needs to be gathered from trusted third parties and/or internal operating experience. As this new experience-based information becomes available, it also needs to be properly persisted and synchronized. • Information to Be Exchanged: For all key originally installed and replaced equipment, ORM and EAM systems need on-line access to motor/pump/gear/bearing/valve/sensor OEM cut-sheet specification data in order for ORM systems to perform equipment diagnostics, validate current configurations meet the required process requirements, and for EAM systems to display to maintenance personnel.
Load more

Recommended publications
  • Iot4cps Deliverable
    IoT4CPS – Trustworthy IoT for CPS FFG - ICT of the Future Project No. 863129 Deliverable D5.1 Lifecycle Data Models for Smart Automotive and Smart Manufacturing Deliverable number: D5.1 Dissemination level: Public Delivery data: 13. June 2018 Editor: Violeta Damjanovic-Behrendt Author(s): Violeta Damjanovic-Behrendt (SRFG) Michaela Mühlberger (SRFG) Cristina de Luca (IFAT) Thomos Christos (IFAT) Reviewers: Heinz Weiskirchner (NOKIA) Edin Arnautovic (TTTech) The IoT4CPS project is partially funded by the “ICT of the Future” Program of the FFG and the BMVIT. The IoT4CPS Consortium: IoT4CPS – 863129 Lifecycle Data Models for Smart Automotive and Smart Manufacturing AIT – Austrian Institute of Technology GmbH AVL – AVL List GmbH DUK – Donau-Universität Krems IFAT – Infineon Technologies Austria AG JKU – JK Universität Linz / Institute for Pervasive Computing JR – Joanneum Research Forschungsgesellschaft mbH NOKIA – Nokia Solutions and Networks Österreich GmbH NXP – NXP Semiconductors Austria GmbH SBA – SBA Research GmbH SRFG – Salzburg Research Forschungsgesellschaft SCCH – Software Competence Center Hagenberg GmbH SAGÖ – Siemens AG Österreich TTTech – TTTech Computertechnik AG IAIK – TU Graz / Institute for Applied Information Processing and Communications ITI – TU Graz / Institute for Technical Informatics TUW – TU Wien / Institute of Computer Engineering XNET – X-Net Services GmbH Document Control Title: Lifecycle Data Models for Smart Automotive and Smart Manufacturing Type: Public Editor(s): Violeta Damjanovic-Behrendt Author(s): Violeta
    [Show full text]
  • Multi-Domain Semantic Information and Physical Behavior Modeling of Power Systems and Gas Turbines Expanding the Common Information Model
    SPECIAL SECTION ON CYBER-PHYSICAL SYSTEMS Received October 20, 2018, accepted November 7, 2018, date of publication November 20, 2018, date of current version December 19, 2018. Digital Object Identifier 10.1109/ACCESS.2018.2882311 Multi-Domain Semantic Information and Physical Behavior Modeling of Power Systems and Gas Turbines Expanding the Common Information Model FRANCISCO J. GÓMEZ 1, (Member, IEEE), MIGUEL AGUILERA CHAVES2, LUIGI VANFRETTI 3, (Member, IEEE), AND SVEIN HARALD OLSEN4 1Royal Institute of Technology, SE-100 44 Stockholm, Sweden 2Instituto Costarricense de Electricidad, San José 10032-1000, Costa Rica 3Renssealer Polytechnic Institute, Troy, NY 12180-3590, USA 4Statnett SF, 0423 Oslo, Norway Corresponding authors: Francisco J. Gómez ([email protected]) and Luigi Vanfretti ([email protected]) The work of F. J. Gómez was supported by the ITEA3 Project 14018, Open Cyber-Physical System Model-Driven Certified Development (openCPS). The work of L. Vanfretti was supported in part by the Engineering Research Center Program of the National Science Foundation and the Department of Energy under Award EEC-1041877 and in part by the CURENT Industry Partnership Program. ABSTRACT Due to the rapid increase of intermittent energy resources (IERs), there is a need to have dispatchable production available to ensure secure operation and increase opportunity for energy system flexibility. Gas turbine-based power plants offer flexible operation that is being improved with new technology advancements. Those plants provide, in general, quick start together with significant ramping capability, which can be exploited to balance IERs. Consequently, to understand the potential source of flexibility, better models for gas turbines are required for power system studies and analysis.
    [Show full text]
  • A Conceptual Framework for Constructing Distributed Object Libraries Using Gellish
    A Conceptual Framework for Constructing Distributed Object Libraries using Gellish Master's Thesis in Computer Science Michael Rudi Henrichs [email protected] Parallel and Distributed Systems group Faculty of Electrical Engineering, Mathematics and Computer Science Delft University of Technology June 1, 2009 Student Michael Rudi Henrichs Studentnumber: 9327103 Oranjelaan 8 2264 CW Leidschendam [email protected] MSc Presentation June 2, 2009 at 14:00 Lipkenszaal (LB 01.150), Faculty EWI, Mekelweg 4, Delft Committee Chair: Prof. Dr. Ir. H.J. Sips [email protected] Member: Dr. Ir. D.H.J. Epema [email protected] Member: Ir. N.W. Roest [email protected] Supervisor: Dr. K. van der Meer [email protected] Idoro B.V. Zonnebloem 52 2317 LM Leiden The Netherlands Parallel and Distributed Systems group Department of Software Technology Faculty of Electrical Engineering, Mathematics and Computer Science Delft University of Technology Mekelweg 4 2826 CD Delft The Netherlands www.ewi.tudelft.nl Sponsors: This master's thesis was typeset with MiKTEX 2.7, edited on TEXnicCenter 1 beta 7.50. Illustrations and diagrams were created using Microsoft Visio 2003 and Corel Paint Shop Pro 12.0. All running on an Acer Aspire 6930. Copyright c 2009 by Michael Henrichs, Idoro B.V. Cover photo and design by Michael Henrichs c 2009 http:nnphoto.lemantle.com All rights reserved. No part of the material protected by this copyright notice may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying, recording or by any information storage and retrieval system, without the prior permission of the author.
    [Show full text]
  • A Method for Reusing and Re-Engineering Non-Ontological Resources for Building Ontologies
    Departamento de Inteligencia Artificial Facultad de Informatica´ PhD Thesis A Method for Reusing and Re-engineering Non-ontological Resources for Building Ontologies Author : Msc. Boris Marcelo Villazon´ Terrazas Advisor : Prof. Dr. Asuncion´ Gomez´ Perez´ 2011 ii Tribunal nombrado por el Sr. Rector Magfco. de la Universidad Politecnica´ de Madrid, el d´ıa...............de.............................de 20.... Presidente : Vocal : Vocal : Vocal : Secretario : Suplente : Suplente : Realizado el acto de defensa y lectura de la Tesis el d´ıa..........de......................de 20...... en la E.T.S.I. /Facultad...................................................... Calificacion´ .................................................................................. EL PRESIDENTE LOS VOCALES EL SECRETARIO iii iv Abstract Current well-known methodologies for building ontologies do not consider the reuse and possible subsequent re-engineering of existing knowledge resources. The ontologization of non-ontological resources has led to the design of several specific methods, techniques and tools. These are mainly specific to a particular resource type, or to a particular resource implementation. Thus, everytime ontol- ogy engineers are confronted with the task of re-engineering a new resource into an ontology, they develop ad-hoc solutions for transforming such resource into a single ontology. Within the context of the NeOn project, we propose a novel methodology for building ontology networks: the NeOn Methodology, a methodology based on sce- narios. One
    [Show full text]
  • ISO 15926, and the Data Handover Standard CFIHOS Based on It
    Enabling step-change For managers: About the interoperability standard for process plants ISO 15926, and the data handover standard CFIHOS based on it. ISO 15926 & CFIHOS Onno Paap – https://www.linkedin.com/in/onnopaap/ March 2020 Purpose Interoperability using standards: For data integration ─ISO 15926 For data handover from Engineering contractor to Owner/Operator ─CFIHOS (Capital Facilities Information Handover Spec) Purpose: Decrease risk by higher data quality and save cost. 2 ISO 15926 – what is it? International standard, ISO TC184-SC4 WG3 (industrial data related to discrete products); Neutral layer used for data integration; Federation of databases – Semantic Web technology; Interoperability standard; Interoperability meaning: “the ability of different types of computers, networks, operating systems, and applications to work together effectively, without prior communication, in order to exchange information in a useful and meaningful manner”. 3 What is in ISO 15926? Reference data library (RDL) = A central online database http://data.posccaesar.org/rdl And also a work-in-progress database http://data.15926.org/rdl Data integration and interoperability methodology Open source software http://15926.tools 4 Why did we need ISO 15926? Shell said: We need a data model that can withstand the changes of the times. A process plant can be running for a period up to 50 years while software typically is changing every 2 years. BP said: A system of systems must interoperate through major projects and operations Reference data is critical, but does not deliver interoperability alone Standard connectors are required to deliver interoperability Commercially available ‘interoperability’ solutions depend on fragile, expensive and proprietary integration 5 What is the scope of ISO 15926? ISO 15926 is targeted for data on process plants.
    [Show full text]
  • Data Exchange Solutions Using ISO 15926 Adaptive Information Model Manoj Dharwadkar, Phd., Director of Technology Management Bentley Systems Inc
    Data Exchange Solutions using ISO 15926 Adaptive Information Model Manoj Dharwadkar, PhD., Director of Technology Management Bentley Systems Inc. Semantic Days 2008, Stavanger, Norway Outline • Bentley Overview • Data interoperability strategy based on ISO 15926 • Bentley’s implementation of ISO 15926 • The role of Bentley Class Editor and Adaptive Information Model Bentley’s Mission Help improve the world’s infrastructure Serving Distributed Enterprises Conceptual Mechanical Construction Financing Procurement Design Design Project Site Structural Fabrication Management Design Design The business of infrastructure entails distributed enterprises A Strong Global Company • 24 years of growth and stability • 2,500+ employees, 80 offices, 40 countries Distinctions 1. A comprehensive software portfolio that is multi-discipline and integrated, just like your projects 2. Collaboration servers that allow distributed enterprises to successfully deliver infrastructure projects 3. A commitment to interoperability to maximize the return on your investments in data Portfolio of Products POSC Caesar IDS and FIATECH ADI are accelerating ISO 15926 • Collaboration between both projects – IDS (Intelligent Data Sets) • Reference data expansion and Methodologies • Online reference data hosting, browsing, and editing • Simple implementation approaches •Training – ADI (Accelerating Deployment of ISO 15926) • Focus on implementation and tools • Reference Data System (RDS) software and utilities •Training • Bentley is very active in both projects Slide: 8 Data
    [Show full text]
  • Modeling and Conformance Testing for the Engineering Information Integration Standard ISO 15926
    NISTIR 7917 Modeling and Conformance Testing for the Engineering Information Integration Standard ISO 15926 Peter Denno Mark Palmer http://dx.doi.org/10.6028/NIST.IR.7917 NISTIR 7917 Modeling and Conformance Testing for the Engineering Information Integration Standard ISO 15926 Peter Denno Mark Palmer Systems Integration Division Engineering Laboratory http://dx.doi.org/10.6028/NIST.IR.7917 February, 2013 U.S. Department of Commerce Rebecca Blank, Acting Secretary National Institute of Standards and Technology Patrick D. Gallagher, Under Secretary of Commerce for Standards and Technology and Director ABSTRACT The process and power industries and their suppliers have invested in multiple initiatives to develop and deploy a new information exchange and integration standard, ISO 15926, Industrial automation systems and integration — Integration of life-cycle data for process plants including oil and gas production facilities. Although the potential benefits of this standard have been demonstrated in pilot projects, broad, cost-effective deployment may require improved methods, tools, and testing. This publication identifies requirements for successful implementation of ISO 15926-based information exchange. Currently there exists a draft methodology for information modeling with ISO-15926, documented in a patchwork of ISO-approved and draft-status documents, and supplemented by documents produced by industry projects [1], [2]. However, there are variations and no consensus as to the criteria for achieving interoperability. There are reasons to believe that successful implementation of ISO 15926 - based exchanges will require substantial refinement of the methodology. Further, there are many more requirements for successful implementation – matters of technical sufficiency and organizational responsibility – that have received insufficient attention.
    [Show full text]
  • The Role of ISO 15926 for Applying Enterprise Service Bus Technologies in Oil & Gas Industry Solutions
    Dr. Udo Pletat IBM Deutschland Research & Development GmbH Böblingen, Germany, [email protected] Semantic Days 2010 Tutorial The role of ISO 15926 for applying enterprise service bus technologies in oil & gas industry solutions Dr. Udo Pletat IBM Germany, Boeblingen © 2010 IBM Corporation Dr. Udo Pletat IBM Deutschland Research & Development GmbH Böblingen, Germany, [email protected] Topic areas Enterprise Application Integration flashback Industry standard information models and EAI – ISO 15926 and Reference Semantic Model ISO 15926 and Reference Semantic Model alignment revisited Relating iRING and IIF from an EAI bus perspective Summary 2 © 2010 IBM Corporation Dr. Udo Pletat IBM Deutschland Research & Development GmbH Böblingen, Germany, [email protected] Motivation Observe existence of different application integration infrastructures & technologies –Enterprise application level: Enterprise Service Bus approach to connect ERP, EAM, CRM systems –Production Control Level: Open Process Control (OPC) to integrate DCS and MES systems Integrate integration infrastructures vertical application integration 3 © 2010 IBM Corporation Dr. Udo Pletat IBM Deutschland Research & Development GmbH Böblingen, Germany, [email protected] Enterprise Application Integration flashback to year 2000 Application 1 SemanticSemantic modelmodel // Application 2 syntacticsyntactic representationrepresentation ASBO 1 ASBO 2 Adapter 1 Adapter 2 GBO GBO Integration flows based on Generic Business Objects GBO Enterprise Service Bus GBO Adapter 3 Adapter
    [Show full text]
  • Product Data Sheet Ontology
    NISTIR 8035 Product Data Sheet Ontology Binyam Abeye Edward Barkmeyer Peter Denno This publication is available free of charge from: https://doi.org/10.6028/NIST.IR.8035 NISTIR 8035 Product Data Sheet Ontology Binyam Abeye Edward Barkmeyer Peter Denno National Institute of Standards and Technology This publication is available free of charge from: https://doi.org/10.6028/NIST.IR.8035 December 2014 U.S. Department of Commerce Penny Pritzker, Secretary National Institute of Standards and Technology Willie May, Acting Under Secretary of Commerce for Standards and Technology and Acting Director NIST Product Data Sheet Ontology Authors: Binyam Abeye, Edward Barkmeyer, Peter Denno, NIST December 5, 2014 Draft 13 November 2014 Abstract Data exchange transactions for the engineering, procurement, and operation of process equipment depend heavily on product data sheets. Product data sheets are traditional paper forms that serve as the main method of communicating detailed equipment specifications. There are many standards for the layout and use of product data sheets, but there are still problems with the data exchanges that use them. First, most transactions are still done with the exchange of document images, e.g., scanned product data sheets, which have to be interpreted by humans and transcribed for use in a software tool. Second, the commonly used machine-interpretable forms of product data sheets are created using spreadsheet tools, but there is often disagreement on terminology and on the intended meaning of certain fields. This publication introduces the concept of a Product Data Sheet Ontology covering the types of information included on product data sheets. The ontology is a formal machine-readable terminology that is based on industry standard glossaries of terms and definitions.
    [Show full text]
  • Technical Report
    TECHNICAL REPORT SEMICOLON : STATE OF THE ART REPORT NO 2008-0996 DET NORSKE VERITAS DET NORSKE VERITAS TECHNICAL REPORT Date of first issue: Project No: DET NORSKE VERITAS AS 1. December 2008 Approved by: Organisational unit: 1322 Høvik Jon Ølnes Norway Principal Engineer Tel: Client: Client ref.: Fax: http://www.dnv.com NO 945 748 931 MVA Summary: Report No: Subject Group: 2008-0996 Indexing terms Report title: Keywords Service Area Semicolon: State Of The Art Market Sector Work carried out by: Terje Grimstad, Per Myrseth, Henrik Smith- Unrestricted distribution (internal and external) Meyer, Lasse Udjus, Hans Solli-Sæther, Dag Belsnes, Tore Christiansen, Riitta Hellman, Birger Unrestricted distribution within DNV Møller-Pedersen, Audun Stolpe, Arild Waaler, Jim Yang. Limited distribution within DNV after 3 years Work verified by: No distribution (confidential) Date of this revision: Revision No: Number of pages: <rev> 143 © 2002 Det Norske Veritas AS All rights reserved. This publication or parts thereof may not be reproduced or transmitted in any form or by any means, including photocopying or recording, without the prior written consent of Det Norske Veritas AS. Semicolon_SOTA_v1.0 DET NORSKE VERITAS Report No: 2008-0996 TECHNICAL REPORT Table of Contents Page 1 EXECUTIVE SUMMARY.............................................................................................................3 2 INTRODUCTION..........................................................................................................................3 2.1 Norwegian
    [Show full text]
  • Technical Specification Iso/Ts 15926-8:2011(E)
    TECHNICAL ISO/TS SPECIFICATION 15926-8 First edition 2011-10-15 Industrial automation systems and integration — Integration of life-cycle data for process plants including oil and gas production facilities — Part 8: Implementation methods for the integration of distributed systems: Web Ontology Language (OWL) implementation Systèmes d'automatisation industrielle et intégration — Intégration de données de cycle de vie pour les industries de «process», y compris les usines de production de pétrole et de gaz — --```,``,,,``,``,,,,``````````,,-`-`,,`,,`,`,,`--- Partie 8: Méthodes de mise en œuvre pour l'intégration de systèmes distribués: Mise en oeuvre du langage d'ontologie du Web (OWL) Reference number ISO/TS 15926-8:2011(E) Provided by IHS under license with ISO © ISO 2011 Copyright International Organization for Standardization Not for Resale, 12/26/2014 14:28:53 MST Licensee=University of Alberta/5966844001, User=ahmadi, rozita ISO/TS 15926-8:2011(E) COPYRIGHT PROTECTED DOCUMENT © ISO 2011 All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from either ISO at the address below or ISO's member body in the country of the requester. ISO copyright office Case postale 56 CH-1211 Geneva 20 Tel. + 41 22 749 01 11 Fax + 41 22 749 09 47 E-mail [email protected] Web www.iso.org Published in Switzerland --```,``,,,``,``,,,,``````````,,-`-`,,`,,`,`,,`--- ii Provided by IHS under license with ISO © ISO 2011 – All rights reserved Copyright International Organization for Standardization Not for Resale, 12/26/2014 14:28:53 MST Licensee=University of Alberta/5966844001, User=ahmadi, rozita ISO/TS 15926-8:2011(E) Contents Page Foreword .
    [Show full text]
  • Re-Engineering the ISO 15926 Data Model: a Multi-Level Metamodel Perspective⋆,⋆⋆
    Re-engineering the ISO 15926 Data Model: A Multi-Level Metamodel Perspective?;?? Andreas Jordan, Georg Grossmann, Wolfgang Mayer, and Markus Stumptner University of South Australia School of Information Technology and Mathematical Sciences Mawson Lakes Blvd, Mawson Lakes, South Australia [email protected] {georg.grossmann,wolfgang.mayer,markus.stumptner}@unisa.edu.au http://kse.cis.unisa.edu.au/ Abstract. The ISO 15926 standard was developed to facilitate the in- tegration of life-cycle data of process plants. The core of the standard is a highly generic and extensible data model. However the data model is replete with confusing terminology, circular definitions and inconsisten- cies that make the standard difficult to understand and less likely to be adopted in practice. In this paper we look at re-engineering the ISO 15926 data model as a multilevel metamodel, and aim to (re-)formalise criti- cal aspects of the data model which we believe simplifies the model and eases the adoption process. Keywords: Conceptual modelling, multilevel modelling, metamodel en- gineering 1 Introduction ISO 15926 aims to deliver a solution capable of supporting the information repre- sentation needs of a broad category of organisations that encompass the process- driven industry. This is in order to support the representation and sharing of life-cycle data across organisations spanning design, engineering, operations and maintenance. At the heart of the standard is a generic data model (ISO 15926-2) such that any organisation within the process-driven industry can adopt and use. Combined with a reference data library (ISO 15926-4) and a set of initial tem- plates (ISO 15926-7) to facilitate (intended) use, enables information exchange at the semantic level between these organisations.
    [Show full text]