Energistics SIGs, Work Groups and Program Management Update: PRODML WITSML GUWI

1
Energistics SIGs, Work Groups and Program
Management UpdatePRODML / WITSML / GUWI

• Energistics Western Europe Region SIG Meeting
• NPD
• Stavanger, Norway
• 17 June 2008

2
Presentation Outline

• WITSML
• Drilling Data Exchange Web Services Standards
• WITSML SIG
• PRODML
• Production Data Exchange Web Services Standards
• PRODML SIG and PRODML Work Group 2008
• GUWI Initiative
• Well Identity Standards Services
• Asset Data Management SIG and WIS Work Group
• Other Initiatives

ltPRODML/gt
ltWITSML/gt
2
3
Basics

• Principles
• Success is delivering value to industry through
  collaborative efforts of members
• Value is focused on increasing operational
  efficiency

ltPRODML/gt
ltWITSML/gt
3
4
Basics

• Major Initiatives
• Associated with EP subject areas within Special
  Interest Groups (SIGs)
• May be accelerated to achieve specific goals with
  Work Groups (WGs) operating inside SIGs
• Objectives for initiatives are expressed through
  value-oriented, multi-year use case road maps

ltPRODML/gt
ltWITSML/gt
4
5
Basics

• Challenges Learn how to
• Align vision with business strategic objectives
• Strategic Standards Management
• Define progression of capabilities leading to
  vision
• Competency Maturity Models
• Help members deploy widely and achieve value
• Awareness, Adoption, and Deployment Planning
• Quantify deployment progress and value received
• Value Measurement Methodology

ltPRODML/gt
ltWITSML/gt
5
6
Energistics Membership and SIGs
Board of Directors Management Staff
Membership Advisory Council
SIGs are standardsuser communities
PRODML SIGParticipants
WITSML SIG
Data Management SIG
Other SIGs
Energistics StandardsWITSML, PRODML, etc.
7
Energistics Subject Areas
Asset DataManagementSIG
eRegulatory SIG

• Industry Services SIG
• Technical Architecture
• Energy Identity Trust

AssetManagement
IntegratedReservoirModelingSIG
Reservoir

Reservoir

Production

Production

Geology SIG
Engineering
Engineering
Geology
Geology
Expl

Petrophysics
Petroleum

Expl

Petrophysics
Petroleum

Geology
Engineering
Geology
Engineering
Drilling

Production

Facilities

Drilling

Production

Facilities

Facilities SIG (n/a)
Engineering
Engineering
Engineering
Engineering
Engineering
Engineering
Completion
Drilling
Production

Drilling

Completion

Production



Geophysics
Operations
Workover
Operations
Geophysics
Operations
Workover
Operations
Geophysics SIG
WITSML SIG
PRODML SIG
8
WITSML (Drilling)
9
Wellsite Information Transfer Standard Markup
Language

• WITSML WWW.WITSML.ORG
• The right-time seamless flow of well-site
  data between operators and service companies to
  speed and enhance decision-making
• Open Information Transfer and Web Services
  Standards for the Oilfield

10
What is WITSML ?

• WITSML is a Web Services framework for moving
  drilling data between rig and office-based
  computer systems.
• Context
• Internet
• XML Schema
• Web Services
• Openly available to all to implement.
• www.energistics.org
• www.witsml.org
• Hosted by Energistics
• User community is the WITSML Special Interest
  Group

11
WITSML Special Interest Group Members

• A set of Data Exchange and Web Services Standards
• First published in 2001
• Version 1.4 due in Q3
• 50 Companies
• Hosted and Facilitated by Energistics
• Semi-annual Events

12
Next Major WITSML Events
Location Dubai UAE SIG Working Meetings Nov.
16-18 Public Seminar Vendor Exhibition Nov.
19 Host Organization Sponsorships Available
13
WITSML Data Objects / XML Schemas

• General
• Well
• Message
• Operations Report
• Real Time
• Wellbore
• Wellbore Geometry
• Risk
• ChangeLog

• Communication
• Subscription
• Server Capabilities

• Rig Instrumentation
• Rig / Rig Equipment
• Cement Job

• Fluids Systems
• Fluids Report

• Surface Logging
• Mud Log

• Coring
• Sidewall Core
• Conventional Core

• Surveying
• Survey Program
• Target
• Trajectory

• Directional Drilling Systems
• Tubular /
• Bit Record
• BHA Run

• Logging While Drilling
• Log ? Well Log (includes Wireline)
• Formation Marker

• Completion
• Completion

Original Updated Added
Source BakerHughes/Paradigm
14
WITSML Public Web Site
15
Product Certification Program
KSI (2) LIOS (1) Kongsberg(3) Geologix (1) INT
(1) Petrolink (4) HRH Petris
16
Product Certification Program

• First Level Server Testing Capability
• Launch by year-end
• Testing WITSML Server Products
• Testing Program Consists of
• Server Test Software
• Testing Scripts/Queries
• Test Data
• Expected Results

16
17
User Registration Program

• Open for WITSML User Organizationsthat are
  Energistics Members
• Launched at May 2008 WITSML Meetings
• User Profile
• Use Policy in Place
• Use Cases Supported(real-time acquisition, other
  acquisition, field data control, field
  analysis, transfer from field to office, office
  analysis, completion processes, intervention
  processes, production processes, other)
• Types of Products Used (Client Producer, Client
  Consumer, Server, etc.)
• Data Objects Used and How Used(well, wellbore,
  realtime, wellLog, rig, etc.)(read, write, etc.)

17
18
WITSML Timeline
Years
2000-2001
2002-2003
2004-2005
2006-2007
2008-2009
2010-2011
Version 1.0
Version 1.1
Version 1.2
Version 1.3.0
Version 1.3.1
Version 1.3.1.1
Version 1.4
Version 1.4.1
Version 1.5 or 2.0
19
WITSML Strategic ChallengesMay 2007, Paris

• Increase from Early Adopter to Full Deployment
• Increase the number of data objects in use
• Put Completion data object to use
• Address automation, QC, integration needs
• Address workovers, maintenance (interventions)
• Address analytical, decision-making processes
• Study and upgrade to current SOA/WS/W3C
• Study and align with PRODML and external
  standards
• Address bi-directional data flows, i.e. to the
  drilling site

20
Drilling Data Architecture (with WITSML)
21
Simplicity and Integration

• Simplicity
• Achieved through
• Consistent data element and structure definitions
  and semantics
• Consistent interfaces among cooperating software
  components

• Integration
• Achieved through the ability to
• Compare and
• Combine
• Data from multiple diverse sources.

22
What are WITSML Benefits for BP?

• Simplify the award of contracts to service
  companies
• Enable remote working and automation
• Encourage adoption of multi-service-company
  solutions
• Speed up deployment of technical applications
• Improve health, safety, and environmental factors
• Improve operational efficiency
• Help address the big crew change

23
What are WITSML Benefits for Total?

• More secure data streaming from rig to office
• Improve wellsite geology and surveillance
• Pore pressure analysis, mudlogging, etc.
• Improve data quality and accessibility
• Integrated data sharing drilling-production
  (PRODML)
• Enables future technology evolution at minimum
  costs
• Well seismic, wired-pipe, etc.

24
What are WITSML Benefits for StatoilHydro?

• WITSML and WITSML-based processes and products
  can make it cost effective to implement complex
  and challenging business cases
• Complexity of the physical environment
• Diversity of service companies involved
• WITSML can be a catalyst to the identification of
  new business opportunities

Largest well in the Troll field superimposed over
Bergen (to scale)
25
What are WITSML Benefits for Shell?

• Moves Data effortlessly, neutrally
• Enables real-time data flows
• Supports well planning and design
• Combining expertise leads to optimal well
  delivery
• Office staff involved in well execution
• Reduction of personnel on the rig
• Improved partner reporting
• Timely, high quality exchange of data without
  restriction on how that data is used or
  interpreted

26
WITSML Summary

• WITSML is ready to deliver value for you today.
• Embed WITSML as part of your real-time data
  architecture
• Use WITSML to get the right data to the right
  person
• Real-time validation and optimization to improve
  drilling performance
• Improve reporting quality with less effort
• Demonstrate value from WITSML usage and expand
  scope of use

27
PRODML (Production)
28
Production Data Transfer Markup Language

• PRODML WWW.PRODML.ORG
• The right-time seamless flow of
  production data among optimization, reporting
  and management processes.
• Open Information Transfer and Web Services
  Standards for producing fields.

ltPRODML/gt
29
What is PRODML ?

• PRODML is a Web Services framework for moving
  production data among analytical and reporting
  components.
• Context
• Internet
• XML Schema
• Web Services
• Openly available to all to implement.
• www.energistics.org
• www.prodml.org
• Hosted by Energistics
• User community is the PRODML Special Interest
  Group

30
PRODML Special Interest Group Members

• A set of Data Exchange and Web Services Standards
• First published in 2006
• Version 1.1 due in Q3
• 30 Companies
• Hosted and Facilitated by Energistics
• Quarterly Workshops
• First Public Tutorial in May 2008

31
WITSML Data Objects / XML Schemas

• Flow Network Topology (Product Flow Model)
• Production and injection wells, equipment, etc.
• Static Model of Flow connections outlet to inlet
• Measurements (Production Volume Report)
• Production volumes and flow rates
• Pressures, temperatures, etc.
• Test results (Well Test)
• Production Activity Report
• Distributed Temperature Survey

32
PRODML Public Site
33
PRODML Background

• Boom in highly instrumented fields. Energy
  companies keen to exploit opportunity for better
  use of near real-time data in optimal operation
  of assets. (aka Digital Oilfield etc.)
• Current landscape is fragmented multiple
  commercial and in-house tools
• Efficient means of interoperability between these
  tools is essential for more efficient workflows

34
Types of PRODML Applications

• Operational Modeling
• Predict future measurements from history and
  operational plans
• Allocation and Reconciliation
• Derive critical values from measurements, as in
  back-allocation
• Surveillance and Monitoring
• Continuous comparison of actual to predicted
  measurements
• Simulation and Optimization
• Predict future measurements and set points to
  achieve objectives
• Advisory and Alert
• Invoked when predicted and actual performance
  differ significantly

35
PRODML Material Progress 2006-08

• A common language for production data has been
  created
• Commercial application has commenced, eg
• Production Reporting (Statoil)
• Waterflood management (Chevron)
• DTS data management (Weatherford)
• First Commercial Applications (Schlumberger)
• RD Proofs of Concept have been substantial
• Gas Lift Optimisation
• Downhole sensors
• 2,000 well dataset transfers
• Network Model changes moving between applications

36
PRODML Addresses Key Area of Asset Management
Business Processes
After Chevron, ExxonMobil
30
2006 PRODML Initial Scope
2008
2010
Many Production Applications
THE PROBLEM Multiple Component Solutions Lack of
Interoperability standards
THE SOLUTION PRODML Open Standards
37
PRODML Focus Production OptimizationRoadmap in
place 2 1/2 more years to industry standard
Business Processes
Low Frequency
High Frequency
30
38
PRODML Current Activities

• Release of Version 1.1
• Technical work closed
• Now preparing release candidate material
• Followed by reviews and Release in Q3
• Post-Version 1.1 Infrastructure Additions
• Initiated in 2007 after a technical review with
  vendors
• More efficient and flexible data access methods
  for time critical interactions
• Authoritative source of production component
  identities

39
PRODML Current Activities

• Work Group 08 Candidate Field Deployment
  Projects
• Chevron (Nodal Analysis Well Modeling, NOJV
  Partner Reporting)
• ConocoPhillips (NOJV Partner Reporting)
• ExxonMobil (NOJV Partner Reporting)
• ONGC with BG (NOJV Partner Reporting)
• Pioneer (Reporting)
• Shell (NOJV Partner Reporting)
• StatoilHydro (NOJV Partner Regulatory
  Reporting, Field Optimization)
• Total (Artificial Lift Well Test Validation),

40
PRODML Timeline
Years
2000-2001
2002-2003
2004-2005
2006-2007
2008-2009
2010-2011
WG06 Version 1.0
WG07
Version 1.1
WG08 Version 2.0
WG09
Version 2.1
WG10
Version 2.2
41
BP PRODML Pilot Implementation

• Sub-set of Horn Mountain
• PI Historian data June 2nd to June 10th
• Three gas lift wells
• The purpose was to test PRODML not the Technical
  applications
• PRODML Interactions (Web Services)
• Plug Play Applications (OSIsoft or Kongsberg
  Consolidator)
• Pilot overview Four phases
• Monitor Gas lift gas rates from the PI Historian
  
• Alert Trigger based on minimum gas lift gas
  available value
• Optimize Run optimizer - Triggered by user
  manual inputs
• Report Report optimizer results

41
42
Chevron PRODML Pilot Implementations

• Based on a large old waterflood field
• Concentrating on water handling
• Providing a number of vendor opportunities
• Developing in-house capability
• Expanding in scope over time
• 2006 Compared actual vs. forecasts 1700 wells
• 2007 Forecasting, Managing Capacity, Optimizing
  Field Network, Visualizing Cross-Functional Data
• 2008 Refine plug-n-play, Testing Post V1.1
  Capabilities, NOJV Partner Reporting, Well
  Modeling Nodal Analysis using Drilling Data

43
Shell PRODML 07 Pilot Implementation

• DTS (Distributed Temperature Sensing) gives a
  continuous temperature profile along a well
• One way to improve accuracy is to reconcile the
  DTS profile to a single point-source temperature
  sensor
• Energy company assets can have DTS and PT sensors
  from multiple vendors
• A standardized method to transfer raw and
  calibrated DTS logs To/From a DTS database as
  well as point temperature readings - typically
  from a well-agnostic process historian is
  beneficial
• In case there is a need to change the DTS or PT
  sensors, this can be done seamlessly without
  affecting the subsequent process flows

44
Work Group 08 Types of Projects

• Field Deployment Project
• Led by an energy company
• Target is deployment in a particular field
• Product Development Project
• Led by a product supplier
• Target is a potential commercial product
• Both
• Ideally have 25 of scope in new capabilities
  for PRODML
• Can lead to 1 or more WG08 Res Dev Activities
• To test proof of concept for new capabilities
• Can invite participation from companies with
  opportunity for compensation.

45
PRODML Summary

• PRODML can deliver value for you today
  selectively
• Embed PRODML (and WITSML) in data architecture
• Use PRODML to get the right data to applications
  through Web Services
• Real-time optimization components
• Improve reporting quality with less effort
• Demonstrate value from PRODML usage and expand
  scope of use
• Expand deployments of same types of optimization
• Expand to new types of optimization

46
GUWI Initiative
47
Well Identity Standards Services

• Began at PNEC in 2003
• to address the long-standing global well
  identification problem.
• Taken forward by an industry steering team
• focused on an industry-marketplace solution
• Strategy
• Previously proprietary identifiers ? industry
  standards
• Contracted Well Identity Services
• Registration/Assignment of new identifiers
• Official source data provision and release into a
  publicly accessible industry dataset
• Search/Match

48
Anticipated Benefits

• Direct cost savings
• Reduced effort to manage well/wellbore identity
  registration, query, and conflict resolution
• Indirect cost savings
• Fewer instances of redoing work necessitated by
  the discovery of a well/wellbore identity problem
• Reduced effort to perform data integration
• Improved efficiency of Acquisition Divestiture
  activities
• Etc.

49
User Service Fee Structure

• User Service Fees
• Access to industry dataset no fee
• Search/Match transactions
• Free for up to 90 thereafter 20 USD
• Industry Accessibility transactions
• Free for up to 120 thereafter 40 USD
• Minimum total fee 500 USD per quarter
• Negotiated fees for large quantities

50
Sponsorship and Industry Cost Structure

• Industry Sponsorship Costs (initial cost)
• 50 of 2008 Contributing Member dues
• Entitlement to join the WIS Work Group
• Must also join the Asset Data Management SIG
• Additional sponsorship costs as needed
• Industry Service Costs (quarterly basis)
• Fixed-fee for general processing and maintenance
  activities
• 2.4k USD
• Transaction based fees to pay for free services
• Search/Match transactions 150 minimum, 1200
  maximum
• Industry Accessibility transaction 120 minimum,
  1080 maximum

51
Steering Team Companies (03-07)

• A2D
• Burlington Resources
• ChevronTexaco
• ConocoPhillips co-chair
• Deloitte
• ExxonMobil
• Fugro-Robertson

• IHS Energy
• Marathon
• Nexen
• Energistics facilitation
• Shell co-chair
• Tobin
• US DOI
• Wood Mackenzie

52
Well Identity Service Roles
Valid SourceAccessibilityRequest
Energistics Asset Data Mgt. SIG
IHSTransactions
Search/MatchServiceRequest
Valid SourceRegister/Update
WIS Work Group Service definition, Industry
alignment, Adoption, Funding
IHSCommercialBusiness
IHSPrimary Service Provider
temp.
Energistics Contract Holder Public data custodian
ID only
53
Basic Well Identity Standards

• Global Unique Well Identifiers under these
  Energistics Standards shall be known as GUWIs
• GUWIs shall be identifiers of Wellbores
• GUWIs shall refer to Parent GUWIs to establish
  Wells
• GUWIs shall be global, independent of location
• GUWIs shall be unique, never used for a different
  wellbore
• GUWIs shall have values that are 12-digit
  numbersa 4-digit prefix number and an 8-digit
  sequence number
• Initially and for the tenure of IHS as service
  provider, GUWI prefix numbers shall have the
  value 1000

54
Data Elements 1 of 2

• Well Name Number
• Alternate Well Name (1)
• Alternate Well Name (2)
• Alternate Well Name (3)
• Country Name
• Region state, province, etc.
• Situation Onshore or Offshore
• Field Name
• License / Block
• Operator Name

55
Data Elements 2 of 2

• Total Depth in m or ft, as specified
• Kick-off point in m or ft, as specified
• Spud Date
• Completion Date
• Latitude decimal degrees, in local datum or WGS
  84, as specified
• Longitude same
• Geodetic datum vertical reference
• Well Status final, Result and Technical
  Status

56
Data Elements Status Values

• Result
• Suspended
• Abandoned
• Tight
• Junked
• Completed

• Technical Status
• Oil
• Gas
• Oil Shows
• Gas Shows
• Oil and Gas
• Gas and Condensate
• Water

57
The GUWI Initiative at Shell

• How the initiative benefits Shell International
  EP (SIEP)
• Provides an industry-recognized well identifier
  for the SIEP Corporate Data Store (CDS)
• Eliminates possible well duplication / UWI
  collision using other well identification systems
• Matches approximately 75 of internal well
  coverage
• Provides a solution for countries that do not
  have a government UWI system

• Challenges to Shell SIEP
• CDS is well/wellbore data model GUWI on
  wellbore
• 25 of wells not currently found in IHS data set
  are predominantly NOC wells so temporary UWI is
  assigned until registry issue is resolved
• Data exchanges remain complicated until regional
  operating units adopt GUWI
• Global pre-spud well registry not yet implemented

58
Global Unique Well Identifier Timeline
Years
2000-2001
2002-2003
2004-2005
2006-2007
2008-2009
2010-2011
Requirements Discussion Paper
New Approach
Planning
V1.0 Deploy 1.0
IHS Approach Negotiation
V1.1 Deploy 1.1
V1.2 Deploy 1.2
59
Summary

• Main goal produce a common system for well
  identification for the oil and gas industry
• Accomplished by associating a GUWI with a
  wellbore through a commercial service provider,
  IHS
• And by releasing the wellbore identifier together
  with data from a valid source for use throughout
  the industry
• Energistics will promote the use of the Standards
  and Services globally
• Initially, applies outside N. America
• Work Group can determine value of extending to N.
  America
• Early Work Group Activities
• Oversight of service operational effectiveness
• Promoting awareness
• Coordinating country/regional roll-out plans

60
Summary

• Launch on July 1
• Founding sponsorships
• Energy Companies BP, Chevron, ExxonMobil,
  Pioneer, Shell, Total
• Service/Solution Companies Accenture,
  Halliburton, Schlumberger, and IHS (as primary
  service provider)
• Government Agencies UK BERR
• All organizations are invited to join as sponsors
• Sponsors are starting to place people in the WIS
  Work Group

61
Other Initiatives
62
Asset Management / Catalog

• Asset Management / Catalog (Assessment)
• In 2007, Standards Advisory Council (SAC)
  identified this as a candidate next major
  initiative
• An SAC sub-team consisting of Chevron, Pioneer,
  Schlumberger and Energistics has been scoping
  this area
• The sub-team recommends that the assessment be
  continued as an Asset Data Management SIG
  activity
• Interested parties are asked to contact
  Energistics

63
Geophysics

• Geophysics (Assessment)
• During 2007, a proposal for a funded assessment
  was accepted by ONGC
• An assessment study has now been completed
• The resulting report is being reviewed
• Linkage with SEG (EAGE last week)
• Global recruiting beginning

64
Energy Indentity Trust

• Energy Identity Trust (Assessment)
• Secure External Access
• People to computing resources (e.g. Partners,
  Contractors, etc.)
• Computing processes to computing resources (e.g.
  Web Services)
• Joint company team access to collaboration tools
  (e.g. Shared File Space)
• Shell and Chevron led ? with BP, ExxonMobil, and
  suppliers
• Incremental plan with business case being drafted
• Sponsorships to be offered to ensure focus and
  drive

65
Integrated Reservoir Modeling

• Integrated Reservoir Modeling (Transition Plan)
• RESCUE planning team defined transition plan
• End current RESCUE Work Group at year-end
• Prepare business case plan for SIG/WG aligned
  with Web Services and XML Data Exchange Standards
  as used in Drilling, Production, etc.
• Work sessions in July and September for energy
  company and supplier representatives
• Forming the SIGs Use Case Team and
  Specifications Team
• Joint meeting with PRODML SIG planned for
  September at SPE ATCE

66
Infrastructure Enterprise IT Architecture

• Infrastructure Enterprise IT Architecture
  (Enabler)
• Need recognized in 2007
• WITSML needs upgrades after eight years
• PRODML needs alignment with WITSML, etc.
• Other xxxMLs are or will be joining WITSML and
  PRODML
• All families of standards need alignment with
  developing industry enterprise IT architecture
  policies and guidelines
• Decide to form group in Q1 of 2008
• A Web Services Interoperability Group formed
  independently
• led by BP, Shell, Chevron with more
  organizations
• Energistics invited this group to become our Work
  Group
• Drafting initial standards now
• followed by reviews and publication by end Q3

67
eRegulatory and National Repositories

• Regulatory U.S.
• WITSML-based state permit XML schema
  specifications agreed by group of US states in
  2007
• Deployment expected in Colorado early in 2008
• State policies revised -- delay
• National Data Repository Conferences
• NDR7 Columbia, September 2006
• NDR8 S. Africa, February 2008
• NDR9 to-be-determined, middle/late 2009
• Until now, each was organized by the same
  dedicated leaders and local organizers
• Momentum was not consistent ? limited
  follow-through
• From now on, Energistics will play an overall
  coordinating role

68

• Thank You!