Agenda

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
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
PRODML Producing Asset Scope
The Production Domain
4
PRODML Headlines

• Scope
• Data Transfer and Web Services Standards
• Focus Support Production Optimization Processes
• Focus Support Field Production Reporting
• Status
• Completing 3rd 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
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
PRODML Positioning
Business Processes
After Chevron, ExxonMobil
30
Many Production Applications
THE PROBLEM Multiple Component Solutions Lack of
Interoperability standards
THE SOLUTION PRODML Open Standards
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
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).
• ltwells xmlns"http//www.witsml.org/schemas/query/
  131"gt
• ltwell uidgt
• ltcountry queryValueMexico /gt
• ltnameLegal/gt
• lt/wellgt
• lt/wellsgt

9
PRODML - New Capabilities

• Shared Asset Model
• Generic Data Access

10
PRODML for Web Services Data Exchange
Presentation
BusinessLogic
Data
Provider Integration Layer
PRODML Service Provider(s)
PRODML Logical Integration Facility
PRODML Service Consumer(s)
Consumer Integration Layer
Presentation
BusinessLogic
Data
11
PRODML Reference Architecture
PRODML Integration Architecture
Solution Sets
Service Specifications
Architectural Abstractions
Reference Data
Protocols
Schemas
Definitions
12
PRODML 1.0, 1.1, x.x Services
PRODML Server
PRODML Server
PRODML Servers
PRODML Server
Servers Applications
SimpleData Store
Historian Data Store
Optimiser
SimulationModel

• PROD_WellTest
• GetServiceInfo
• GetDataSync
• GiveData
• GetDataAsyncInitiate
• GetDataAsyncStatus
• GetDataAsyncControl
• GetDataAsyncResults
• GetSupportedPatterns

• PROD_ProductionVolume
• GetServiceInfo
• GetDataSync
• GiveData
• GetDataAsyncInitiate
• GetDataAsyncStatus
• GetDataAsyncControl
• GetDataAsyncResults
• GetSupportedPatterns

• PROD_ProductFlowModel
• GetServiceInfo
• GetDataSync
• GiveData
• GetDataAsyncInitiate
• GetDataAsyncStatus
• GetDataAsyncControl
• GetDataAsyncResults
• GetSupportedPatterns

Services Methods
SchemawellTest
SchemaproductionVolume
SchemaproductFlowModel

• PROD_DtsInstalledSystem
• PROD_DtsMeasurement
• PROD_ProductionOperation

13

• Shared Asset Model

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
SAM and Service Implementation
Outside scope of the specifications
Inside scope of the specifications
SAM Database
Sources of Meta Data
VendorApplication A
SAMServices
ENDPOINT
VendorApplication A
SAM Application
SAM Service Implementation
Asset Model Schema
Service A
SAM Service Consumer
VendorApplication A
Service B
Asset Model 1
Asset Model 1
synchronize
Asset Model Instance 1
Service n
maintain
16

• Generic Data Access Interface Methods

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
Proposal for Generic Data AccessScope
Schemas
PRODML Client Application
PRODML Data Server
GetData
GDA Interface
PutData
Binary transfers Asynchronous operations
GetCapability
19
GetCapability Method
Allows a client to find out what data types a
server can provide. (Equivalent to WITSML
Profiling)
public NameObjectPair GetCapability(ref Context
context)
20
GetData Method
Allows a client to obtain specific data.
ServerResponse GetData(ref Context
context, RequestObject requests) public
class RequestObject public string
dataType public string idList public
NameObjectPair criteria public
NameObjectPair options