PRODML Overview

1
PRODMLNov 18, 2005

2
Topics

• PRODML History
• Scope
• Primary Deliverables and TimeLine
• Relationship to WITSML
• PRODML POSC
• Thoughts About Future Branding
• Ongoing work (Flow model and flows)

3
PRODML Some History

• Drilling Completion Standard (WITSML)
• Version 1.0 established in 2000
• 12 month concentrated effort
• Handed over to POSC
• Production Operations Standard
• Most commonly identified next step
• POSC tasked to develop production data exchange
  standards
  
• Limited traction from 2001 2005
• Production Reporting (Norwegian sector), DTS
• Rustys opinion
• To produce PRODML, we need a concentrated effort
• Use WITSML model

4
Scope Deliverables

• Scope
• Industry standard data exchange for
• Production Domain
• Eventually its the well completion to point of
  sale
  
• Current focus is a subset of Production
  Optimization"
  
• See next slide
• Deliverables
• Documentation yes, of course
• PRODML compliant commercial applications
  primary objective

5
Production Optimization
The Production Domain
6
PRODML Proposed Project Timeline
The three phases in the project timeline
Months
2
4
6
8
10
12
Scope Method

• Project planning
• Team Kick-Off

Steering Committee Meetings
Future State Detailed Design

• Workshop preparation and scheduling
• Standards investigation

Pilot Documentation
Current State

• Conduct workshops

• Process mapping
• Technology assessment
• Standards development

• Implementation guide outline
• Process flow documentation
• Plan Pilot

3 sub teams
5 sub teams
N sub teams

• Pilot

• Project Management
• Communication

Design-Develop-Test
Implementation
Mobilization
7
PRODML - 2005

• June
• BP, Shell, Chevron, Statoil Agree to pursue
  PRODML project
  
• Aug
• Kickoff meeting
• BP, ExxonMobil, Shell, Chevron, Statoil
• SenseIntellifield, Halliburton/Landmark, OSISoft,
  eProduction Solutions, Microsoft, Petex,
  TietoEnator, Case Services, Schlumberger, IBM,
  Invensys
• Sep Oct
• Teams Sub-teams formed and meeting weekly
  (minimum)
  
• Primary Teams Content Technical
• Secondary Communication, Legal
• First joint session of Content Technical Teams
• Abstract submitted to SPE (Amsterdam - April)
• Nov - Dec
• Second joint Content Technical Team meeting
  (Rijswijk)
  
• WWW.PRODML.ORG goes public
• News Release

8
Relationship to WITSML

• PRODML should build on WITSML
• PRODML should not be incompatible with WITSML
• If PRODML exposes a deficiency in WITSM
• Work with WITSML SIG to achieve a solution both
  camps can live with

9
PRODML POSC

• Initial effort requires considerable energy from
  operators and suppliers
  
• POSC has been member of PRODML since kickoff
• Ensure alignment with WITSML
• Share learning's from WITSML experience
• When PRODML 1.0 emerges, it will be handed over
  to POSC for ownership and stewardship
  
• SIG will address care feeding over time

10
Thoughts About Future Branding

• Given that
• The intent is for PRODML and WITSML to be "ONE
  ML
  
• We will eventually want exploration and perhaps
  capital projects domains to be addressed
  
• We should be thinking about a different branding
  in the future.
  
• One Example
• PETROML as the overall brand for upstream oil
  gas
  
• Subsets WITSML, PRODML, EXPLML, PROJML

11
Short Term Deliverables

• Phase 1
• Specification Of Scope Draft 2
• Process and Standards for PRODML including a
  comparison of PRODML components, flows and
  processes to WITSML, OPC-UA, and other
  standards.
• Phase 2
• Detail Design Requirements (Data, flows,
  objects, etc.) in the form 4-5 representative
  Flows developed through a logical representation
  and model.
• Technical Validation and Architecture Design
  required supporting the designated Flows.
  
• 2 or more logical Proof of Concept (POC) paper
  specifications of actual flows
  
• At least one working Physical POC rendered in
  XML.
  
• A Unified Project Plan (UPP) This will be a
  combination of the Content Team and the Technical
  Teams specific activities to achieve the above
  Phase 2 objectives.

12
Flow Model and PRODML flows

• Product Flow Model
• Flow 1 and 2

13
Injection
Flow 1
Production
Wing Master Valve
Controller or Casing Choke
Flowline Choke
10
11
20
12
25
27
26
21
22
13
3
Separator
4
15
14
5
16
Compressor 1
From Well
23
Compressor 2
To Well
Production Header
24
Gas Header
Compressor 3
From Well
Gas Lift Valve
To Well
Tubing
Valve Choke Measurement
Casing
Packer
1
Perforations
1
2
14
(No Transcript)
15
Injection
Production
Wing Master Valve
Controller or Casing Choke
Flowline Choke
10
11
20
F
12
E
25
27
26
21
22
13
3
Separator
4
15
14
5
16
C
Compressor 1
From Well
H
D
23
Compressor 2
To Well
Production Header
24
Gas Header
G
Compressor 3
From Well
B
Gas Lift Valve
To Well
A
Tubing
Valve Choke Measurement Unit Boundary Unit N
ame
Casing
Packer
1
Perforations
1
2
A
16
Injection
Production
Wing Master Valve
Controller or Casing Choke
Flowline Choke
10
11
20
F
12
E
25
27
26
21
22
13
3
Separator
4
15
14
5
16
C
Compressor 1
From Well
H
D
23
Compressor 2
To Well
Production Header
24
Gas Header
G
Compressor 3
From Well
B
Gas Lift Valve
To Well
A
Tubing
Valve Choke Measurement Unit Boundary Unit N
ame
Casing
Packer
1
Perforations
1
2
A
17
Model-based Well Surveillance
Flow 2
Data Acquisition Control system
Raw real time data
Orchestration Tools
Inform staffand track actions
Data Validator
Cleansed Data
Applications to derive well oil, gas, water f
lows

Advisory Tools
Reconciled data
Model Validator
Applications to predict performance
Well tests (from Energy components
Real time data
Non-real time data
Model data