PRODML Business Case Pilot Demos

1
PRODML Business Case Pilot Demos

• Jerry Blaker
• Others

2
PRODML Project Timeline UpdateOctober 20, 2006 -
Status
Steering Committee Meetings
Months
2
4
6
8
11
14
November 15, 2006 V1.0 Release

• Project planning
• Team Kick-Off

Content

• Conduct workshops
• Detailed Requirements
• Macro Design

• Workshop preparation and scheduling
• Standards investigation
• Develop Scope

Technology

• Design Communication Plan
• Develop Test Bed Scenarios

• Process mapping
• Technology assessment
• Detailed Requirements
• Macro Design

• Design POC
• Build POC

Build

• Implementation guide outline
• Process flow documentation
• Plan Pilot

Pilot
Industry Review
Start August 16, 2005
Strong Typing
End November 15, 2006

• Project Management
• Communication

Requirements
Build Communicate
Design-Develop-Test
Implementation
Phase 1 Scope and Define
3
PRODML Scope Statement

• Scope
• Select a part of the business for which a
  standard data exchange can be readily used.
• Limit the scope from an IT architecture
  perspective
• Document 2 usecases on how different application
  could be used together to solve real and
  relatively complex business problems
• Identify a number of applications that together
  can provide the required functionality.
• Constraints
• Be large enough to provide interoperability
  between a suite of applications that can be used
  in practice to solve a realistic and meaningful
  business problem,
• Be chosen such that an implementation can be
  demonstrated within 12 months.
• Interoperability should be demonstrated between
  applications from at least four different
  vendors.
• The scope should concentrate on application in
  the area of production of hydrocarbons, and more
  precisely on optimisation of an existing
  production facility using production data in a
  near-realtime fashion.

4
Use Case 1 Offshore

• Wells produce gas lifted oil, associated gas,
  non-associated gas and condensate
• Gas contaminated with CO2 - varies across the
  field
• Gas to power plant 50 daily demand variation,
  CO2 contamination limits
• Gas sold to LNG plant penalties for missed
  targets, opportunities for spot sales, limited
  CO2 tolerance
• System available to blend-off CO2 gas
• Oil production limited by gas sales
• Flaring contractually penalised

5
Use Case 1 Constraints

• Day-to-day optimisation accomplished by
  manipulating the existing operational facilities.
  
• Planned infrastructure changes must be taken into
  account.
• Scheduled maintenance leads to equipment outages
• All elements of the production system must be
  operating within their limits

6
Use Case 2 Onshore

• 1000 remote natural gas wells, condensate
  by-product and oil wells with associated gas
• Gas, crude, condensate, water separation
  important - water sent to disposal
• Gas gathering systems with compression
• Optimizing gas gathering system is critical
• The crude and condensate are sold at the lease

7
Use Case 2 Constraints

• Dynamic regulatory environment impacts the
  production optimization process requirements
• Legacy IT infrastructure, data base architectures
  
• Day-to-day optimisation by manipulating the
  existing operational facilities
• Infrastructure changes to be taken into account
• Scheduled maintenance and inaccessible assets
  not remotely operated during parts of the year
• Process must be operating within limits. (e.g.
  max draw down, min/max flow rates etc)

8
Scope Asset View
The Production Domain

• Decisions we can effect in a day

9
Scope IT View
External data transfer
Data Processing / monitoring and reporting
software
AP 3
AP x
AP 4
AP 5
AP 2
AP 1



Office Domain
Application Databases
Historian

DCS and real time applications
real time apps
DCS historian

Process Control Domain
Fields instruments
10
Who is building PRODML?

• Operators
• BP
• Chevron
• ExxonMobil
• Shell
• Statoil

• Standards
• POSC

• Vendors
• Halliburton
• Invensys
• OSIsoft
• PETEX
• Schlumberger
• Sense Intellifield
• TietoEnator
• Weatherford

11
4 - Pilot Project Workflows

• Plug and Play
• Interface without the need of a central server
• Universal data structure (XML Schema and API)
• Pilot 1 Model data management
• Pilot 2 Model data management
• Pilot 3 Steady-state gas lift optimization
• Pilot 4 Dynamic field-wide optimization focused
  on momentum of water distribution used for
  flooding
• Demos BP and/or Shell

12
PRODML Shell Pilot Demo

• Laurence Ormerod

13
Agenda Friday, October 20