Global Collaboration for Open Standards

Global Collaboration for Open Standards Introduction to Energistics • An open standards industry consortium • Twenty-one years serving the upstream industry • Over 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 Company Members Our Flagship Standards… WITSML Update 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 Supported Data Objects in Version 1.4.1 • Well & Wellbore • Cement Job • CRS • Frac / Stimulation • Rig / Rig Equipment • Fluids • Tubular / string • Drilling • Wellbore Geometry • Operations • BHA Run • Survey Program • Target Reporting • Trajectory & Tool Error Contextual • Log • Mudlog • Message • Formation Marker • Attachment • Core • Change log • Risk • Object Group General Subsurface 8 Source: BakerHughes/Paradigm WITSML SIG: Collaboration • Accenture • IDS • Petris Technology • Atman Consulting • Institut Francais du Petrole • Petrolink • Baker Hughes • INT • Pioneer Natural Res. • Beijing Sunny Tech • Kongsberg • Roxar • BP • LIOS Technology • RPS Group • Chevron • Merrick Systems • Saudi Aramco • Devon Energy • Microsoft • Schlumberger • US DOI • National Oilwell Varco • SDC Geologix • Digital Oilfield Sol. • Oil Teams S.R.L. • SMT • DrillScan • ONGC • Shell • Dynamic Graphics • OpenSpirit • Statoil • ExxonMobil • Paradigm • TCS • Geolog SPA • Pason • TOTAL • Geoservices • Peloton • Weatherford • Halliburton • Perfomix • Wellstorm • HRH Limited • Woodside Energy WITSML Roadmap Planning 2017 2014 More automation Focus on plug and New use/new data play including support for 2011(1.4.1) automation stimJob object “Tiered” usage (high Error model end/low end) Support for plug-and- Major release - not play backward compatible PRODML Update PRODML…Focus on Optimisation Produced fluids optimisation Gas compression optimisation Equipment optimisation Gas lift optimisation Production optimisation Natural lift optimisation Single-well optimisation Multi-well optimisation Injection optimisation PRODML Data Objects 1. Flow Network 2. Product Volume 3. Production Operation 4. Well Test 5. DTS (Distributed Temperature Survey) 6. Time series 7. Fluid Sample and Analysis 8. Wireline formation tester (coming) 9. Shared Asset Model (SAM) (coming) RESQML Update What is RESQML? • RESQML is predominantly concerned with representing models of the earth • RESQML is a next generation XML based standard for data exchange coupled with the HDF5 standard for large array data • It is a replacement of the ‘end of life’ RESCUE data exchange standard for reservoir and earth models Dublin Core Coord sys defns meta data XSD schema WITSML well PRODML data XSD production data schema XSD schema • Needed by Geoscientists & Engineers for: RESQML XSD HDF5 schema specs more robust way to share & use reservoir and earth models across our subsurface toolkit Refers to XML HDF portfolio. file file(s) Data Exchanges Overview RESQML SIG Members Energy Industry Profile (EIP) v1.0 Release Candidate A Metadata Initiative for the Energy Industry Release Candidate Review Release Date: September 1, 2011 Comments Due Date: October 12, 2011 Vision for Industry Metadata Exchange & Use Externally Harvested External (Commercial,Gov’t, Metadata Catalog & Academic) Partner & Application Metadata Subscription Managed Catalog Delivered Legend: Metadata exchange via EIP standard Unstructured Use cases Structured resources resources 19 Areas for Cross-SIG Collaboration •MARKETING – A collective term for the WITSML, PRODML, RESQML products and communities. – Communicates a message of a broader set of standards that cover the full upstream spectrum. •PEOPLE & PROCESSES – Cross-SIG forum to leverage common approaches and strategies for schema development and versioning, service specification. – Each SIG brings unique experience and history. • WITSML – Large mature schema base (SOME of which are cross-functional) • RESQML - HDF5 for binary objects. •TECHNOLOGY – Common set of low level schemas for shared types. – Common set of service definitions – where it makes sense. 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 Final Thoughts on Standardization • Standards developed in collaboration, widely adopted and deeply deployed: – Have tangible business value • Standards developed collaboratively but not widely adopted: – Have only potential business value • Standards developed in a proprietary fashion: – Have no business value stimJob Object Overview • Fracturing services are performed on wells for the primary purpose of enhancing oil and gas production • Fracturing treatments are a very complex process result in the generation of large volumes of data • Makeup/SUMMARY Reports – What was pumped – How it was pumped – Observations during job – Interpretations of observations http://w3.energistics.org/schema/witsml_v1.4.1_support/WITSML_stimJob_Object_Usage_Guide.pdf Business Process - old vs new Historically Historically there has not been a standardized, post-job fracturing treatment data The problem Inconsistent terminology, Digital data required unique and specific formats to transfer Business Process - old vs new Standardize The stimJob Object was developed to standardize the service company output thus ensuring that customers not only know what to expect but can also specify what they are expecting Key Business Objectives: 1. Create an object that would allow consistent post job reporting 2. To enable reporting to use a consistent terminology 3. Provide the opportunity for efficiencies Structure - Relationship -Terminology •Job (the parent) •Holds typical parameters asked for by customers •Well name, well API, engineer, job type •Jobs are performed on the well •Treatment Intervals. •This is the zone of interest/pump in. •The accumulation of all these intervals create the one Job •Flow Path (the pipe) •Each treatment interval may have one or more flow paths •Summary of flow path data define the treatment(s) •Stage •Stage /specific steps define what’s being performed via the flow path •What material traversed the tubular and entered the formation Hanging off the stage are the •Fluid •Type, name, function used on a stage •Fluids (carrier media) •contain additives, proppants Design Concepts – Include all post-job treatment data for all fracturing services – Well and wellbore WITSML data-objects are parent objects – Object instance at every level contains summary of levels below – mainly to capture summary of total proppant in a multi-flow path scenario – At every stage fluids, proppants and additives are captured separately to allow for the data-object to be as rich or as lean as necessary – Diagnostic tests performed on an interval, so data is rolled up to a sub-object: cs_stimJobInterval – Perforation data is treated similarly – localized to one treatment interval – Designed to handle different types of operations: • Acid • Simple fracturing • Foam • Multi-stage • Multi-flowpath Data sub-objects obj_stimJob grp_stimJob cs_stimAdditive cs_stimEvent cs_fetTest cs_stimFlowPath cs_stimFluid cs_stimJobInterval cs_stimJobStage cs_stimPdatSession cs_stimPerforationSet cs_stimPressureFlowRate cs_stimProppant cs_stimProppantUsage cs_stimPumpFlowBackTest cs_stimReservoirInterval cs_stimShutInPressure cs_stimStepDownTest cs_stimStepTest cs_stimTestStep cs_stimTubular Questions .

Load more