DOCSLIB.ORG

Enabling the Integration of Work Processes in Upstream Oil and Gas

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

Enabling Integration of Core Work Processes in Upstream Oil and Gas Kaare Finbak & Pål Rylandsholm Det Norske Veritas, Ray Verhoeff, OSIsoft Topics Covered • Integrated Information Platform (IIP) project – Background • The new operation concept Integrated Operations (IO) • OLF’s strategy for Quality Information – Purpose and deliverables • Objectives • Deliverables – Take-up process • OLF’s Daily Production Reporting project • OSIsoft RtPM for Production Data Exchange in Upstream Oil & Gas OLF = Norwegian Oil Industry Association Copyright © 2006 OSIsoft, Inc. Company Confidential. All rights reserved. 2 DNV - Det Norske Veritas • Independent foundation • Objective: To “Safeguard life, property, and the environment” • Established in 1864 in Norway • Top 3 certification body world- wide • Top 4 ship classification society world-wide • Global representation • 6095 employees Copyright © 2006 OSIsoft, Inc. Company Confidential. All rights reserved. 3 DNV – Information Quality Management • Business Information Services – Requirements – Governance – Architecture • Information Quality Assessment and Rating • Information Training and Education – Standards • Information Models & Data Standards • Test Center Managing risk by – Compliance to Standards (Software) managing information – Validation according to Standards (Data) • Independent Data and Information Hosting Copyright © 2006 OSIsoft, Inc. Company Confidential. All rights reserved. 4 According to OLF, IO increases revenue and reduces costs Trondheim Bergen Vendor’s onshore Expert Expert operation center center centre Stavanger Aberdeen Control room Operator’s onshore operation centre Expert center Source: OLF, 2005 Copyright © 2006 OSIsoft, Inc. Company Confidential. All rights reserved. 5 OLF predicts that IO will be implemented in two main steps Automatic IO Generation 2 optimization Vendor • Integrated operation centers of operators and vendors • Heavily instrumented Operator facilities • Heavy automation and multi- Intelligent domain optimization of facilities Real-time Vendor processes pipeline Real-time Reservoir & collaboration production IO Generation 1 rooms management • Integrated onshore and offshore centers Drilling & completion • Intra-domain optimization of work processes Traditional Operation & facilities maintenance Source: OLF, 2005 Copyright © 2006 OSIsoft, Inc. Company Confidential. All rights reserved. 6 OLF intends to establish an information pipeline that supports both IO generations Automatic optimization Vendor Web portals Processes Field data Web services • Health, safety, environment Operator • Drilling & completion Schemas for automatic • Reservoir & exchange of data production management Vendor • Operation & maintenance Terminology Taxonomy Ontology Semantic oil & gas web Source: OLF, 2005 Copyright © 2006 OSIsoft, Inc. Company Confidential. All rights reserved. 7 Terminology, taxonomy and ontology? Reservoir & production optimization Services Well Reservoir Production monitoring monitoring monitoring XML HSE Drilling Completion Reservoir Production Operation Maintenance Terminologies Taxonomies Ontologies Project Copyright © 2006 OSIsoft, Inc. Company Confidential. All rights reserved. 8 The IIP project delivers required terminologies, taxonomies and ontologies Automatic Generation 2 optimization • Complete ontologies supporting automated reasoning or inference of data using logical rules Intelligent • Taxonomies for multiple facilities Oil & gas domains ontology Real-time collaboration rooms Generation 1 • Terminologies for single domains • The basis for XML schemas for automatic transferal of data between Traditional applications in same domain facilities Copyright © 2006 OSIsoft, Inc. Company Confidential. All rights reserved. 9 The project targets key business domains Develops terminologies based on solid business knowledge Production – Input from project participants – Other projects specifications – Domain specific standards Prepares approval of the Drilling terminologies by international standardization bodies Geometry and – ISO and W3C topology – POSC Caesar and POSC Addresses short term … – Terminologies and XML schemas Reservoir characterization for real-time exchange of data Condition … as well as long term business monitoring needs – Taxonomy and ontology supporting Equipment optimization of processes across domains Safety and Automation System Copyright © 2006 OSIsoft, Inc. Company Confidential. All rights reserved. 10 Deliverables will be available on the Internet Publicly available from www.posccaesar.com during Q2 2006 Copyright © 2006 OSIsoft, Inc. Company Confidential. All rights reserved. 11 Visualization Terms Definition http://ht.vestforsk.no/demo/production/index.html Copyright © 2006 OSIsoft, Inc. Company Confidential. All rights reserved. 12 The project is supported by many key players POSC Caesar Association Copyright © 2006 OSIsoft, Inc. Company Confidential. All rights reserved. 13 Project schedule and budget Total current budget: Project Duration: 24 MNOK (3 MEUR) 16.06.04 – 30.06.07 The project is partly funded by The Norwegian Research Council program PETROMAX and by the project participants. Copyright © 2006 OSIsoft, Inc. Company Confidential. All rights reserved. 14 OLF’s Daily Production Reporting project One of several fast-track take-up projects initiated by OLF Daily Production Report - Project details • Scope: Develop ontology and common XML schemas for daily production report • Participants: All major operating companies on the Norwegian Continental Shelf • IIP contribution: Terminology and standard XML • Pilots: Åsgard and Valhall • Implementation: Started January 1, 2006 Source: OLF, 2005 Copyright © 2006 OSIsoft, Inc. Company Confidential. All rights reserved. 16 Daily Production Report - System overview Operator ISO LicenseWeb Authorities, operator 15926 & partners Internal Excel reports prod. XML Std. reports data file License Web system Non-std. reports Prod. XML Valhall report file Åsgard • Benefits: Efficient exchange of production data and daily production reporting Source: OLF, 2005 Copyright © 2006 OSIsoft, Inc. Company Confidential. All rights reserved. 17 A Daily Production Report XML based on standard XSD Standard report Source: OLF, 2005 Copyright © 2006 OSIsoft, Inc. Company Confidential. All rights reserved. 18 OSIsoft RtPM And The IIP Project Provides terminologies, Provides framework taxonomies and ontologies for collecting, to be used for real-time structuring, storing optimization of reservoir and analyzing real- and production for heavily time field data from instrumented oil and gas heavily instrumented fields oil and gas fields May enable Reliable real-time information pipeline supporting G1 and G2 integrated operations Copyright © 2006 OSIsoft, Inc. Company Confidential. All rights reserved. 19 OSIsoft RtPM in Upstream • About the upstream business… • Problems & Solutions • Exchanging data • The ProdML Initiative Copyright © 2006 OSIsoft, Inc. Company Confidential. All rights reserved. 20 Priorities in Upstream • Cambridge Energy Research Associates (CERA) polled leading E&P firms in 2006: – “Total Asset Awareness” • better sensor technology • better in-field communication systems • advanced data mgmt solutions – Visualization & Analytics • automated model updating • improved visualization • system-wide optimization (both surface and subsurface) Copyright © 2006 OSIsoft, Inc. Company Confidential. All rights reserved. 21 OSIsoft in Production & Refining • 37% of the world’s refined products are monitored by PI • Installed in 26% of the world’s refineries • 15% -20% of the world’s oil fields are monitored by PI Copyright © 2006 OSIsoft, Inc. Company Confidential. All rights reserved. 22 OSIsoft RtPM in Upstream • Green field, brown field, offshore • Production is a complex business… – Few free flowing wells – Most done by injection of steam or gas Copyright © 2006 OSIsoft, Inc. Company Confidential. All rights reserved. 23 Injection Production Controller or Wing & Master Valve Casing Choke Flowline Choke 10 11 20 12 21 22 25 26 27 13 3 14 15 4 16 5 Separator Compressor 1 From Well 23 To Well Compressor 2 Production Header 24 Gas Header Compressor 3 From Well Gas Lift Valve To Well Tubing Valve Casing Choke Packer Measurement # 1 Perforations 1 2 Gas Lift Well Copyright © 2006 OSIsoft, Inc. Company Confidential. All rights reserved. 24 Upstream Data Management Problems • Frequently changing flow network configurations • Hard-to-measure data – “3 phase” flow meters rare • Data reconciliation and estimation needed • Back-allocation • Optimization • Reporting must be accurate Copyright © 2006 OSIsoft, Inc. Company Confidential. All rights reserved. 25 Interaction of Applications • “Chaining” of applications needed in the field – Measured data feeds estimated algorithms – Estimated feeds enter back-allocation algorithm – Allocated data fed to modeling software – Modeling software drives optimization – … Copyright © 2006 OSIsoft, Inc. Company Confidential. All rights reserved. 26 Solutions abound • Many vendors offer analytical solutions • Data exists, but from a variety of sources • This suggests a data exchange standard! Copyright © 2006 OSIsoft, Inc. Company Confidential. All rights reserved. 27 Full Production Facility Copyright © 2006 OSIsoft, Inc. Company Confidential. All rights reserved. 28 Rendering in XML <unit> <name>A</name> <flow> <name>…</name> <kind> … </kind> <port> <direction>inlet</direction> <temp> … </temp> <pres> … </pres> <product> <period> <kind> … </kind> <dTimStart>
Recommended publications
  • Business Overview of PRODML

    Business Overview of PRODML

    Business Overview of PRODML This document introduces the PRODML™ family of standards and provides an overview of what they are for and how and why they were developed. What is PRODML? The software applications used to support production workflows are available from multiple vendors. However, they cannot be integrated easily because they typically have their own data structures and incompatible designs. This leads to high cost of integration, a proliferation of point to point links, high cost of maintenance and poor flexibility to cope with change. PRODML is the name of an industry initiative to provide standard interfaces between software tools used to monitor, manage and optimize hydrocarbon production. It is also the name of the family of web services and data exchange standards that the initiative has created. The purpose of PRODML is to increase innovation in the composition of optimization solutions for production systems while reducing cost and risk. This translates into enabling the development of plug compatible software by energy sector vendors as well as energy companies. The PRODML standards form a framework within which energy companies can configure processes related to operations, optimization, reporting, and/or information management. PRODML enables the vision of Digital Oil Fields of the Future PRODML reduces the lifetime cost of information exchange in the Energy industry. PRODML standards are key components in today's IT Enterprise Architectures PRODML schemas standardize information exchange The PRODML standards are managed by energy companies and vendors participating in the PRODML Special Interest Group (SIG) that is facilitated by the Energistics consortium. PRODML supports workflows for Production Operations and Optimization PRODML focuses on production workflows from the reservoir-wellbore boundary to the custody transfer point, and on production optimization decisions that can be effected within a day.
  • Energistics Update

    Energistics Update

    Energistics Update Jerry Hubbard Chief Operating Officer PPDM 9 March 2011 The Challenge of Standardization • Strategic Perspective – Strategic Standardization Management • Standards Collaboration – Focus on highest value standards that don‟t impact competition • Industry Commitment – Internal and external commitment to implementation • Value Delivery – Measuring the business value of implementation Our Flagship Standards… Wellsite Information Transfer Standard Markup Language “The „right-time‟ seamless flow of well-site data between operators and service companies to speed and enhance decision-making” An Open Information Transfer Standard for the Oilfield WITSML Data Object Schemas (XML) General •Coordinate Ref Sys Communication •Well •Drill Report •Subscription •Message •Attachment •Server Capabilities •Operations Report •StimJob •Real Time Rig Instrumentation •Wellbore •Rig / Rig Equipment •Wellbore Geometry •Cement Job •Risk Surface Logging Fluids Systems •Mud Log •Fluids Report Surveying Coring •Survey Program •Sidewall Core •Target •Conventional Core •Trajectory Logging While Directional Drilling Drilling Systems •Log Well Log (includes Wireline) •Tubular / •Formation Marker •Bit Record Original •BHA Run Updated Added Source: BakerHughes/Paradigm WITSML SIG: Member Companies • Accenture • IDS • Petris Technology • Atman Consulting • Institut Francais du Petrole • Petrolink • Baker Hughes • INT • Pioneer Natural Res. • Beijing Sunny Tech • Kongsberg • Roxar • BJ Services • LIOS Technology • RPS Group • BP • Mahindra Satyam • Saudi
  • Use Case: Ontology-Driven Information Integration and Delivery a Survey of Semantic Web Technology in the Oil and Gas Industry

    Use Case: Ontology-Driven Information Integration and Delivery a Survey of Semantic Web Technology in the Oil and Gas Industry

    > Semantic Web Use Cases and Case Studies Use Case: Ontology-Driven Information Integration and Delivery A Survey of Semantic Web Technology in the Oil and Gas Industry Frank Chum, Chevron Information Technology Company April 2007 Introduction The purpose of this paper is to survey some significant applications of Semantic Web technology in the oil and gas industry, and describe a use case on how the industry can leverage this technology. Key Business Drivers “There is a million miles of spaghetti eaten every day!” The same can be said about data in the oil and gas Industry. A large amount of data is generated every day from multiple sources such as seismic data, well data, drilling data, transportation data, and marketing data. Integrating these heterogeneous data to capitalize on their information value has been complex and costly. These data exist in a structured form in databases, and in semi-structured forms in spreadsheets and documents such as reports and multimedia collections. To deal with the flood of information, as well as the heterogeneous data formats of the data, we need a new approach for information search and access. For the major capital projects (see application examples below) in the industry, information needs to be standardized and integrated across systems, disciplines and organizational boundaries. This information integration will enable better decision making within collaborations, as high quality data will be accessible in a timely fashion. “Semantic Web provides a common framework that allows data to be shared and reused across application, enterprise, and 1 community boundaries.” The Semantic Web technology provides a standard for machine-operational declarative specification of the meaning of terms based on the Resource Description Framework (RDF).
  • AKSIO – Active Knowledge Management in the Petroleum Industry

    AKSIO – Active Knowledge Management in the Petroleum Industry

    AKSIO – Active knowledge management in the petroleum industry David Norheim 1, Roar Fjellheim 2 1UniK and Computas AS, Norway, [email protected] 2Computas AS, Norway, [email protected] Abstract . The AKSIO project is developing a process-enabled knowledge management system to support operations of offshore oilfields. The system will provide timely and contextual knowledge for work processes. Experiences will be processed and annotated by experts and linked to various resources and specialist knowledge networks. AKSIO will allow discovery of experiences through the support of a domain ontology. Core functionality of the AKSIO system is provided by careful application of Semantic Web technology, including ontology-based annotation and contextual ontology driven retrieval of content. 1 Introduction As the third largest exporter of crude oil (ca. 3 million barrels/day or 4% of the world’s oil production), the oil and gas industry is of major importance to Norway. The petroleum resources are located in the North Sea, a challenging environment for oil and gas production. Oil companies have deployed advanced technology to increase output and reduce cost. Increased output from the fields is possible due to new use of technology and methods e.g. injection of Natural Gas, Water and CO 2 in the oil wells. To various degrees all major operators and service companies in the North Sea are implementing the concept of Integrated Operations (IO). In IO, the offshore oil platforms are connected by high-speed data links to on-shore control centers, where multidisciplinary teams collaborate to optimize operations and rapidly solve any problems. The ultimate goal of IO is to maximize value created from petroleum resources, which can only be ensured by a continuous stream of right decisions made at the right time.
  • ISO 15926, and the Data Handover Standard CFIHOS Based on It

    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.
  • Work Plan for 2007

    Work Plan for 2007

    POSC Caesar Work Plan for 2007 POSC Caesar Telephone: Telefax E-mail c/o Det Norske Veritas +47 67 57 73 73 +47 67 80 59 40 [email protected] N-1322 HØVIK NORWAY 17 - 1 POSC Caesar Work Plan for 2007 Contents 1 SUMMARY......................................................................................................................................................... 3 2 ADMINISTRATION.......................................................................................................................................... 5 1.1 HOUSING AND ADMINISTRATIVE FUNCTIONS ............................................................................................... 5 1.2 NEW VERSION OF THE REFERENCE DATA SYSTEM....................................................................................... 5 1.3 WEB SITE ..................................................................................................................................................... 5 1.4 EXISTING AND NEW MEMBERS .................................................................................................................... 6 1.5 COLLABORATIONS ....................................................................................................................................... 6 1.6 SPECIAL INTEREST GROUPS ......................................................................................................................... 6 1.7 MANAGERIAL /TECHNICAL COURSES, CONFERENCE / SEMINARS, MEMBERSHIP MEETING ......................... 7 2 ISO 15926 ...........................................................................................................................................................
  • Establishing and Proving Interoperability Welcome and Introduction

    Establishing and Proving Interoperability Welcome and Introduction

    Establishing and Proving Interoperability Welcome and Introduction Joint PCA and MIMOSA Meeting San Antonio, 25 March 2013 Nils Sandsmark Agenda y 08:00 AM Welcome and Introduction y 08:30 AM JORD – Creating the iRING core y 10:00 AM Break y 10:30 AM OGI Pilot – Proving Standard Based Interoperability y 12:00 AM Lunch and open discussion y 12:30 AM Meeting Close POSC Caesar Association (PCA) • PCA is a global, not-for-profit, The vision of ISO 15926 independent member organization data interoperability and life cycle developing, enhancing, and promoting methodology, content and solutions for data interoperability with special focus on ISO 15926 / iRING and W3C recommendations • PCA has 35 members in 12 countries on 5 continents • PCA arranges forums and member meetings every year in: Focus areas have evolved so far: • Asia/Australia 1. Handover EPC - OO (1993+) • Europe/Africa 2. Integrated operations (2004+) 3. Operations & maintenance (2008+) America • 4. Integration between engineering and O & M (2010+) • PCA was established in 1997 iRING Reference data architecture n ISO io Change t a iz Requests d r a d Reference / n a t Synchronize S Change PCA Requests Reference / Synchronize Company Feed Back Capital Project and Operations & Maintenance Standards Leadership Council ‐ Members Organization Senior Executive Comments Energistics Jerry Hubbard MIMOSA Alan T. Johnston The Open Geospatial Consortium (OGC) Mark Reichardt International Association of Oil & Gas Producers Observer (OGP) OPC Foundation Thomas Burke PIDX International Anthony Aiming The Pipeline Open Data Standard Association Janet Sinclair (PODS) POSC Caesar Association Nils Sandsmark Professional Petroleum Data Management Trudy Curtis Association (PPDM) Troika International Jill Lewis W3C Frank Chum (Chevron) Observer Standards Leadership Council (SLC) For the upstream Oil & Gas Industry Objectives: • Identify areas of intersection to avoid creating duplicate or conflicting standards • Identify opportunities for synergy, so we can build on our successes together.
  • Collaborative Technologies for Exploration

    Collaborative Technologies for Exploration

    COLLABORATIVE TECHNOLOGIES FOR EXPLORATION Authors: Randy Clark, Jerry Hubbard (Energistics) Presented by: Paul Maton (Energistics and Sillimanite Consultants) Upstream Standards. Bottom Line Results. Introduction to Energistics • An open standards industry consortium • Twenty years serving the upstream industry • With 100 active members… – Integrated, independent & national energy companies – Oilfield service and professional service companies – Software, hardware and integration vendors – Regulatory agencies, institutes and media partners Our Energy Standards Resource Centre Our Energy Company Members Our Government Agency Members Our Energistics Community • Global Regions: – Africa (South Africa, Angola, Equatorial Guinea, Nigeria…) – Asia Pacific (China, Japan, Korea, Vietnam, Philippines…) – Eastern Europe (Russia, Kazakhstan and non-EU states) – Latin America (Mexico, Central and South America) – Middle East (Saudi Arabia, Kuwait, UAE, Oman, Bahrain…) – North America (United States and Canada) – South Asia (India, Australia, Malaysia, Pakistan…) – Western Europe (European Union and Norway) The Challenge of Standardization • Strategic Perspective – Strategic Standardization Management • Standards Collaboration – Focus on highest value standards that don’t impact competition • Industry Commitment – Internal and external commitment to implementation • Value Delivery – Measuring business value of implementation vs. the cost of not making standardization a strategic goal Importance of Open Data Exchange Standards • Optimising highly instrumented
  • Purpose, Intended Use and Evolution

    Purpose, Intended Use and Evolution

    Purpose, Intended Use and Evolution PRODML™ Enabling Production Operations, Optimization, Reporting and Data Management for the Exploration and Production (E&P) Domain. Version: PRODML Version 1.1 Abstract This document comprises a high level overview of the PRODML standard. It explains the background to the development of the initial version of the standard, the business problems addressed, and the pilot implementations used to develop and test the standard. A brief description of the PRODML architecture and embedded standards is included. Prepared by: Energistics and the PRODML SIG Date published: 6 March 2009 Document type: Specification Keywords: web services, production, interoperability Purpose, Intended Use and Evolution - PRODML Version 1.1 Document Information DOCUMENT VERSION: 1.1 DATE: 6 March 2009 Technical Color: R: 210 G:124, B50 Language US English This document was produced by Energistics and the PRODML SIG Energistics™, POSC®, Epicentre®, WITSML™, PRODML™, Upstream Standards. Bottom Line Results.™, The Energy Standards Resource Centre™ and their logos are trademarks or registered trademarks of Energistics. Access, receipt, and/or use of these documents and all Energistics materials are generally available to the public and are specifically governed by the Energistics Product Licensing Agreement (http://www.energistics.org/posc/Product_License_Agreement.asp) Page 2 of 14 Purpose, Intended Use and Evolution - PRODML Version 1.1 Amendment History Version Date Comment By V1.1 6 March Prepared for final release. Gary Masters 2009 V1.1 Dec 2008 Revised for 1.1 release Robin Getty V 1.0 11/13/2006 Improvements based upon R. Cutler’s feedback Jake Booth V1.0 11/06/2006 Clarified comments on “Plug and Play” Jake Booth RC_1.0 08/30/2006 Release Candidate Jake Booth 0.91 08/24/2006 Added Documentation Mapping Jerry Blaker 0.80 08/21/2006 Create First Draft Jerry Blaker Page 3 of 14 Purpose, Intended Use and Evolution - PRODML Version 1.1 Table of Contents Preface 5 1.
  • Application of Remote Real-Time Monitoring to Offshore Oil and Gas Operations

    Application of Remote Real-Time Monitoring to Offshore Oil and Gas Operations

    Transportation Research Board Special Report 322 Application of Remote Real-Time Monitoring to Offshore Oil and Gas Operations Prepublication Copy • Uncorrected Proofs TRANSPORTATION RESEARCH BOARD 2016 EXECUTIVE COMMITTEE* Chair: James M. Crites, Executive Vice President of Operations, Dallas–Fort Worth International Airport, Texas Vice Chair: Paul Trombino III, Director, Iowa Department of Transportation, Ames Executive Director: Neil J. Pedersen, Transportation Research Board Victoria A. Arroyo, Executive Director, Georgetown Climate Center; Assistant Dean, Centers and Institutes; and Professor and Director, Environmental Law Program, Georgetown University Law Center, Washington, D.C. Scott E. Bennett, Director, Arkansas State Highway and Transportation Department, Little Rock Jennifer Cohan, Secretary, Delaware Department of Transportation, Dover Malcolm Dougherty, Director, California Department of Transportation, Sacramento A. Stewart Fotheringham, Professor, School of Geographical Sciences and Urban Planning, Arizona State University, Tempe John S. Halikowski, Director, Arizona Department of Transportation, Phoenix Susan Hanson, Distinguished University Professor Emerita, Graduate School of Geography, Clark University, Worcester, Massachusetts Steve Heminger, Executive Director, Metropolitan Transportation Commission, Oakland, California Chris T. Hendrickson, Hamerschlag Professor of Engineering, Carnegie Mellon University, Pittsburgh, Pennsylvania Jeffrey D. Holt, Managing Director, Power, Energy, and Infrastructure Group, BMO
  • Thumbs Package Example

    Thumbs Package Example

    Information and Communication Technologies for Integrated Operations of Ships Liping Mu Information and Communication Technologies for Integrated Operations of Ships A Dissertation Submitted in Partial Fulfillment of the Requirements for the Degree of Philosophiae Doctor (PhD) in Information and Communication Technology University of Agder Faculty of Engineering and Science 2013 iii Doctoral Dissertation by the University of Agder 74 ISBN: 978-82-7117-753-9 ISSN: 1504-9272 Copyright c by Liping Mu, 2013 All rights reserved unless otherwise stated. Printed by the Printing Office, University of Agder Kristiansand iv To my parents v vi Preface and Acknowledgments This dissertation is a result of the research work carried out at the Department of Information and Communication Technology (ICT), University of Agder (UiA) in Grimstad, Norway, from April 2009 to October 2012. This work is part of the project entitled “Maritime Communications - broadband at sea (MarCom)”. The MarCom project is a joint initiative from several research and development insti- tutions, universities and colleges, public authorities and industry. The project is funded by the industry itself, and the Norwegian Research Council. First of all, I want to express my sincere thanks to my principal supervisor, Pro- fessor Andreas Prinz. His valuable guidance, suggestions and continuous support helped me from the very beginning till the completion of this work. I believe that the lessons I learned from working together with him will always guide me forward in the future. I also must say thanks a lot to my co-supervisor, Professor Frank Re- ichert. Without his encouragement and supervision, I could not have developed an overview understanding of this subject and mapped it into the thesis.
  • 2019 “State of Energistics” Orientation

    2019 “State of Energistics” Orientation

    2019 “STATE OF ENERGISTICS” ORIENTATION Jana Schey, COO Jay Hollingsworth, CTO January 31, 2019 1 February 2019©2019 Energistics Inc. 1 Introductions Philip Neri Jana Schey Jay Hollingsworth Marketing Director Chief Operating Officer Chief Technology Officer 1 February 2019 ©2019 Energistics Inc. 2 Agenda » About Energistics » Standards Overview » 2019 Plans » How We Work » Q&A 1 February 2019 ©2019 Energistics Inc. 3 About Energistics 1 February 2019 ©2019 Energistics Inc. 4 Energistics…past and present » Energistics is not a vendor. We are a non-profit industry organization. » Our role is to help companies manage and share data more efficiently and cost-effectively by using industry-defined data exchange standards » We have served the industry for more than 25 years » Our 110+ members include leading E&P companies, oilfield service companies, software vendors, system integrators, regulatory agencies » Our standards are the result of open collaboration between members, facilitated by Energistics » In short, the standards are created by the industry and for the industry 1 February 2019 ©2019 Energistics Inc. 5 Our Current Members – Come Join Us! 1 February 2019 © 2019 Energistics 6 Standards Overview 1 February 2019 ©2019 Energistics Inc. 7 Energistics’ Spectrum of Standards UNIVERSAL INTEROPERABILITY • Defined by collaboration between member SMEs DRILLING/WELL PRODUCTION RESERVOIR • Coherent set of standards to eliminate data ‘friction’ • Goal is to cover all key activities in upstream • Shared components enable cross-functional workflows Energistics Transfer Protocol (ETP) Common Technical Architecture (CTA) 1 February 2019 ©2019 Energistics Inc 8 Well Information Standards: WITSML™ » Consistent high-quality transfer of wellbore Reference and drilling-related data Well 1532-e • Real-time data transfer Reports Growing Reference objects – Well and Wellbore Growing objects – Log (time, depth), Trajectory, Mud Log, etc.