1. 1 Agenda Introduction Energistics Standards Panorama / History / Participants Web Services Interoperability Standards v1.0 WITSML Version 1.x Services / Data Specifications PRODML Version 1.x Services / Data Specifications RESQML plan Adjacent Technologies and External Specifications Subjects for Subsequent Meetings Candidates for Next Stage Deliverables Next Steps Adjourn

2. 2 PRODML Helping achieve production optimization  Freely available, universally applicable  Enables low-risk and low-cost use of proven optimization solutions  Accelerates and encourages innovation

3. 3 Gathering Separation & Distribution Injection (Water, Steam, CO2) Water Handling Gas Treating Facilities Oil Treating Facilities Gas Export Facilities Oil Export Facilities Reservoir Management: Gas & Oil Contract Deliverability The Production Domain PRODML Producing Asset Scope 2006 Initial Scope From bottom of the well to initial separation Decisions we can effect in a day

4. 4 PRODML Headlines Scope –Data Transfer and Web Services Standards –Focus: Support Production Optimization Processes –Focus: Support Field Production Reporting Status –Completing 3 rd Year (started in Aug. 2005) –Focus: Iterative Development & Implementations –Growing User Community (SIG) of ~40 Organizations –Four In-person Working Meeting Annually –Active SIG teams and Implementation-Focused Work Group –Version 1.0 (Q4 2006) –Version 1.1 (Q4 2008) –Testing Starting on Additional Services and Objects

5. 5 PRODML: Active Participants Founders (from Aug. 2005) [13] –BP, Chevron, ExxonMobil, Shell, StatoilHydro –Halliburton, Invensys, Kongsberg Intellifield, OSISoft, Petroleum Experts, Schlumberger, TietoEnator, Weatherford Joined in 2007 [17] –ConocoPhillips, Pioneer Natural Resources, ONGC –AspenTech, Euriware, Honeywell, IBM, Infosys, Intelligent Agent, Matrikon, P2 Energy Solutions, Petris, Roxar, Satyam, SensorTran, TIBCO Joined in 2008 [8] –Total –Atos Origin, BearingPoint, Merrick Systems, Petrolink, PDS, PKO Services, SAIC, Tata Consultancy

6. 6 THE PROBLEM Multiple Component Solutions Lack of Interoperability standards THE SOLUTION PRODML Open Standards PRODML Positioning SCADA Systems Sensor Data Reservoir Models Geoscience Data OPC Domain De facto Standards PRODML Domain High FrequencyLow Frequency 30 Drilling Systems WITSML Domain Maintenance Systems Maintenance Domain Many Production Applications Application A Application B Application etc. Application C Business Processes After Chevron, ExxonMobil

7. 7 Relationship of First Versions to WITSML Data schemas were created using the same construction criteria as WITSML. –A PRODML schema could be used with the WITSML web service interface. Some business processes require a combination of WITSML and PRODML data objects (e.g., production reporting). Current objects: –dtsInstalledSystem (dependent on wellbore) –dtsMeasurement (dependent on wellbore) –productFlowModel –productionOperation –productVolume –wellTest (dependent on well)

8. 8 Differences of First Versions From WITSML SOAP message style is “literal wrapped document” style (versus “RPC”). –One object schema per method. Not yet concerned with “CRUD”. –That is, only GET or GIVE. No persistence presumed. Template moves all element content to an attribute so that empty elements are valid. –compliant with “generated” template schema).

9. PRODML - New Capabilities Shared Asset Model Generic Data Access ‹#›

10. 10 PRODML for Web Services & Data Exchange ‹#› Presentation Business Logic Data Provider Integration Layer PRODML Service Provider(s) PRODML Logical Integration Facility Presentation Business Logic Data Consumer Integration Layer Data Exchange Web Service Integration Mechanisms PRODML Service Consumer(s)

11. 11 PRODML Reference Architecture ‹#› PRODML Integration Architecture Architectural Abstractions Service Specifications Reference Data Solution Sets Core Services Independent Data Transfer Full Services PRODML Service Providers PRODML Message Providers PRODML Service Consumers PRODML Message Consumers Service Provider Interface Service Consumer Interface Protocols Schemas Definitions XSD Business Services Data Services Functional Services (Future) Support Services

12. 12 PRODML Server PRODML ServersPRODML Server PROD_ProductionVolume GetServiceInfo GetDataSync GiveData GetDataAsyncInitiate GetDataAsyncStatus GetDataAsyncControl GetDataAsyncResults GetSupportedPatterns PROD_ProductFlowModel GetServiceInfo GetDataSync GiveData GetDataAsyncInitiate GetDataAsyncStatus GetDataAsyncControl GetDataAsyncResults GetSupportedPatterns PRODML 1.0, 1.1, x.x Services Simple Data Store Historian Data Store Optimiser Simulation Model Services + Methods Servers + Applications Schema: wellTest Schema: productionVolume Schema: productFlowModel … PROD_WellTest GetServiceInfo GetDataSync GiveData GetDataAsyncInitiate GetDataAsyncStatus GetDataAsyncControl GetDataAsyncResults GetSupportedPatterns PROD_SamInfo GetServiceInfo … PROD_Sam Registry GetServiceInfo … PROD_SamServerRef GetServiceInfo … Service Discovery Server Shared Asset Model Server PROD_GDA GetServiceInfo GetCapability GetData PutData GetDataAsyncInitiate GetDataAsyncStatus GetDataAsyncControl GetDataAsyncResults Service Discovery Server Shared Asset Model Server PRODML Support Services PROD_ServiceDiscovery GetServiceInfo GetServices GetURL … Schema: ALL SCHEMAS PROD_DtsInstalledSystem PROD_DtsMeasurement PROD_ProductionOperation ‹#›

13. Shared Asset Model ‹#›

14. 14 What is the Shared Asset Model ? The purpose of a PRODML Shared Asset Model (SAM) is to provide a single place to go to: –Obtain asset-related information – a single authoritative source of metadata (identifiers, associations, and state - as opposed to measurement values) about production components associated with a production asset. –Obtain identifiers for production components that can be used throughout an installation. –Obtain references to business services that provide additional information for production components –Select individual components of the production system and to obtain their identifiers. The purpose of the SAM Services is to provide consumers and maintainers of SAM information with functionality to query and maintain models of production assets that organize metadata about assets in a consistent way. ‹#›

15. 15 SAM and Service Implementation ‹#› Sources of Meta Data SAM Application SAM Database SAM Service Implementation SAM Services Asset Model 1 Outside scope of the specifications Inside scope of the specifications Vendor Application A SAM Service Consumer Service A Service B Service n synchronize maintain Asset Model 1 Asset Model Instance 1 Asset Model Schema Vendor Application A Vendor Application A

16. Generic Data Access Interface Methods ‹#›

17. 17 Generic Data Access Interface Methods Supports targeted data exchange Get and Put of Generic Objects –WSDL defines the range of standard objects that can be exchanged –Extensible to exchange further objects Discovery of server capability ‹#›

18. 18 Proposal for Generic Data Access Scope PRODML Client Application PRODML Data Server GetData PutData GetCapability Binary transfers Asynchronous operations GDA Interface Schemas ‹#›

19. 19 GetCapability Method public NameObjectPair[] GetCapability(ref Context context) Allows a client to find out what data types a server can provide. (Equivalent to WITSML Profiling) ‹#›

20. 20 GetData Method ServerResponse GetData(ref Context context, RequestObject[]requests); public class RequestObject { public string dataType; public string[] idList; public NameObjectPair[]criteria; public NameObjectPair[]options; } Allows a client to obtain specific data. ‹#›