PRODML Operational Pilot Test Results

1
PRODML Operational Pilot Test Results

• Petrotech 2007 Alan Doniger
• New Delhi, India Chief Technology Officer
• 18 January 2007 Energistics

2
Abstract

• The completion of the year-long PRODML initiative
  in late 2006 not only resulted in published
  industry standards, but also resulted in the
  active implementation involvement of all eight
  participating software vendors in four realistic
  pilot activities.
• Reviewing the content and coverage of these pilot
  activities is a very good way to become familiar
  with the value of the new PRODML optimization
  standards.
• Similar pilot activities using realistic data and
  actual application products are planned for 2007.

3
Pilot Teams

• PRODML formed 4 teams that address a range of
  production optimization challenges
• Plug-and-play
• Vendor suite integration
• Transitional value enhance existing solutions
• Transformational value enable major change in
  when, how, where and which people collaborate

• PRODML established a micro data center
• 8 vendors with dedicated servers
• Main pilot visualization is through portals and
  loggers

4
The Pilots
5
Shell Pilot Testing Activities

• Free-Flowing Well Surveillance
• Purpose
• Notify operator whenever measured and projected
  production volumes differ beyond a defined
  threshold
• Uses three sources of information
• Actual and two sets of simulation results
  (Plug-and-Play)
• Data Validator Application Invensys InFusion
• Triggered according to a schedule
• Historian OSIsoft PI
• Simulation 1 Petex Prosper
• Simulation 2 Weatherford WellFlo
• Notification Invensys

6
Shell Pilot
Invensys InFusion App Env
Invensys Notification
6
8
PETEX Prosper
Weatherford WellFlo
OSISoft PI Historian
7
BP Pilot Testing Activities

• Gas Lift Optimization
• Purpose
• Optimize Gas Lift by recommending revised lift
  gas rate changes
• Plug-and-Play demonstrated by 2 Monitor
  applications
• Data Consolidator 1 (Monitor) OSIsoft ACE
• Data Consolidator 2 (Monitor) Intellifield
  SITECOM
• Historian OSIsoft PI
• Optimizer Weatherford GL Optimizer
• Notification Intellifield Portal

8
BP Pilot
Sense Intellifield SITECOM Consolidator
Weatherford GL Optimiser
Sense Intellifield Portal
OSISoft PI Historian
OSISoft ACE Consolidator
9
Chevron Pilot Field Example Setting

• Fact Surge volume in water injection station
  scheduled to decrease
• Result Potential for facility upset
• Manifestation
• Tank overflow
• Excess water passed to field
• Water production (with associated oil) shut in
• Scale
• Over 1000 wells and a single water injection
  station

10
Chevron Pilot Concept

• Choices
• Add surge capacity (capital cost)
• Improve reaction time (anticipate change)
• Accept facility upset
• Tank overflow
• Excess water passed to field
• Water production (with associated oil) shut in

11
Chevron Pilot Improve Reaction Time

• Model surge tank (production system)
• Estimate produced water into plant for seven days
  based on prior seven days
• Plant operators view of water production
• Model allocated production (test system)
• Estimate produced water from the field for seven
  days based on prior seven days allocated daily
  production
• Allow for scheduled maintenance by including well
  status changes
• Allows for introducing new information to the
  plant operator
• Compare the two
• Are they equal? If not, notify operator

12
Chevron Pilot Testing Activities

• Field-wide Water Management
• Production Accounting TietoEnator EC
• Monitor Application Invensys InFusion
• Historian Invensys InSQL
• Simulator Weatherford LOWIS
• Forecasting Landmark DSS
• Data Integrator Schlumberger
• Notification Invensys

13
Chevron Pilot InteractionsWhat does this look
like in practice
Invensys Notification
Data Integrator
Weatherford LOWIS Well Status Forecast
Halliburton DSS Well Production Forecast
Invensys InFusion Tank Forecast
Energy Components Daily Allocation / Status /
Well Listing
Invensys Facility SCADA History
Weatherford Well Test History
Local System Field Oil Sales / Inventory History
Local System Field Gas Sales History
Weatherford Status History
14
Statoil Pilot Testing Activities

• Optimize smart wells (Snorre B)
• Purpose
• Optimize 29 smart wells with sliding sleeves
• Highly Instrumented, Large Volume of Data
• Report recommended operational parameters
• Intend to Continue to Test Deploy PRODML
• Statoil, TE, SLB Committed to Test Lab Data
  Consolidator (Monitor) Schlumberger DECIDE
• Historian Out of Scope
• Production Accounting and Operational Parameters
  TietoEnator, PROSTY
• Optimizer Asset Models - Simulators
  Schlumberger IAM
• Simulator Petex PROSPER

15
Statoil Pilot
Energy Components PROSTY
Aspentech Historian
2
4
Schlumberger DECIDE
Schlumberger DL
10
Schlumberger DL
PETEX Prosper
11
Schlumberger IAM
16
Lessons Learned

• Successfully demonstrated PRODML concepts
• GetFromStore,AddToStore,GetDataInvoke
  (asynchronous)
• Data types are ProductVolumeReport, WellTest,
  Notification
• Four vendors and one operator interacting
• Ability to include forecast data proven
• Current state response time is in minutes
• Data did not kill the product over 1000 wells
  called by both LOWIS and DSS
• Performance can be optimized
• Cache to keep requests to recent data
• Call larger increments than individual wells
• Understand timeouts
• Understand how much data processing is behind a
  request

17
In the Marketplace

• Vendors are planning to develop commercial
  PRODML-based versions of products during 2007.
• This work will be enhanced by the additional work
  planned for 07, e.g. widening the footprint, as
  this will strengthen the market for such
  products.
• Without PRODML strength and growth, there are
  risks
• Point solutions will continue to be developed
• Preventing low-cost, low-risk innovative
  optimization deployments, especially those that
  mix and match products from multiple vendors
• Energy companies will develop solutions
  themselves
• Further fragmenting the market and making
  conversion to standards-based solutions more
  difficult

18
Vision for 2007 and Beyond

• For end of 2007
• Demonstrate additional PRODML-based functionality
  through Pilot Testing Activities.
• Build on Version 1.0 try to maintain
  compatibility
• Encourage the PRODML SIG Steering Committee to
  define a multi-year roadmap for PRODML Standards,
  that increasingly
• Helps reduce cost, time, complexity and risk for
  production optimization solutions using
  communications and computing technologies
• Enables novel and valuable workflows with
  integration not conceived or not practical until
  now
• Work with other solutions and standards related
  to production optimization, wells, reservoirs,
  processing plants, production accounting, etc.

19
Vision for 2007 and Beyond

• Consider similar efforts in associated areas,
  such as
• Well Management
• Well Optimization
• Reservoir Performance
• Opportunity Portfolio Management
• Facility Optimization
• Etc.
• The PRODML approach and the PRODML architecture
  may fit well in some or all of these areas.

20
PRODML 07 Work Group Scope Flow Network Model

• Requirements
• Basic Flow Network Model content Units, Ports,
  Connections, Locations, etc.
• Enable applications to respond to configuration
  changes either of Units/Connections or
  operational parameters
• Address connections with adjacent models, e.g.
  reservoir
• Enable levels of abstractions and subsets
• Enable different depths of information about
  Units
• Enable interactions with existing / emerging
  standards
• Proposed Pilot Testing Activities
• Support multiple levels of detail and support
  major/minor configuration changes
• Consider Web Services to supply Flow Network
  information to applications, including
  information about changes

21
PRODML 07 Work Group Scope Well Types

• Possible Pilot Testing Activities for 07
• Power-Assisted Artificial Lift
• Consider electrical motors at the surface
• ESP Wells
• Consider mechanical lift
• Sucker-Rod Pump Wells
• Down-Hole Sensors
• Consider wellbore configuration (WITSML
  Completion)
• Higher-rate wells with permanent down-hole
  sensors
• Consider multi-zone allocated volumes
• Production reporting with allocation to
  multi-zones

22
PRODML 07 Work Group Scope Well Types

• Classifying Types of Wells for PRODML
• Free Flowing and Fluid-Driven Artificial Lift
  Wells
• Addressed by PRODML Work Group in 2006
• More precisely
• Production Wells
• Naturally Flowing
• Artificially Lifted (Fluid Driven), e.g. Gas
  Lifted
• Injection Wells
• Disposal Wells

23
PRODML 07 Work Group Scope Well Types

• Classifying Types of Wells for PRODML
• Fluid-Assisted Artificial Lift Wells
• Gas Lift Continuous or Intermittent
• Plunger
• Jet or Hydraulic Pumped
• Power-Assisted Artificial Lift Wells
• Electric Submersible Pumps
• Sucker Rod Pumps
• Progressive Cavity Pumps
• Smart Wells
• Wells with down-hole sensors
• Wells with down-hole control valves

24
PRODML 07 Work Group Scope Well Types

• Priorities for 07
• Fluid-Driven Artificial Lift Surface
  Connections only
• Consider Time Cycles for intermittent gas
  lift/plunger lift
• Jet and Hydraulic Pump wells
• Power-Assisted Artificial Lift
• Consider electric motors at the surface
• Consider mechanical lift
• Consider variable frequency drives in electrical
  controllers later
• Down-Hole Sensors
• Consider wellbore configuration (WITSML
  Completion)
• Consider multi-zone allocated volumes
• Consider further aspects of well description
  later
• Down-Hole Equipment after progress on the above
• Consider down-hole gas lift for surveillance
• Consider artificial lift device internals, e.g.
  motor / pump shaft
• Consider flow controller devices

25
Thank You ???????