Title: PRODML Project Status Report Iniative Review
1PRODML Project Status ReportIniative Review
- Jerry Blaker
- May 17, 2006
- Houston
2PRODML - Introduction
- What is PRODMLs scope?
- Who is building PRODML?
- How far along are we?
- www.prodml.org
- Pilots
- Final thoughts
3PRODML 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 typical 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.
4Scope Asset View
The Production Domain
- Decisions we can effect in a day
5The 3 (work) Flows
6Scope 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
7Who is building PRODML?
- Operators
- BP
- Chevron
- ExxonMobil
- Shell
- Statoil
- Vendors
- Halliburton
- Invensys
- OSIsoft
- PETEX
- Schlumberger
- Sense Intellifield
- TietoEnator
- Weatherford
8PRODML Project Timeline UpdateMay 17, 2006 -
Status
Steering Committee Meetings
Months
2
4
6
8
10
12
- Project planning
- Team Kick-Off
Steering CommitteeMarch 20, 2006 Go For Pilots
May 17, 2006
- Workshop preparation and scheduling
- Standards investigation
- Develop Scope
Content
- Conduct workshops
- Detailed Requirements
- Macro Design
- Design Communication Plan
- Develop Test Bed Scenarios
Technology
- Process mapping
- Technology assessment
- Detailed Requirements
- Macro Design
- Implementation guide outline
- Process flow documentation
- Plan Pilot
Start August 16, 2005
End September 1, 2006
- Project Management
- Communication
Requirements
Build Communicate
Design-Develop-Test
Implementation
Phase 1 Scope and Define
9PRODML Current Status
- Four Pilot Teams have formed, each focused on one
of the following Major Operating Companies, each
with from 3 to 5 Vendors - Shell
- Chevron
- Statoil
- BP
- Pilot Teams are implementing 4 workflows using
the PRODML - Milestone Dates
- 3/10/2006 - Deadline for Pilot Proposals
- 3/20/2006 - Pilots Selected and Funded
- 3/30/2006 - PRODML Pilot (v.81) Reference
Architecture and XML Schema are Complete - 4/03/2006 - Pilot Project Development Kick Off
- 5/10/2006 Publish V.81 RA, Schema, API
- 5/01/2006 Manual XML Templates Passed
- 6/01/2006 API applied and automation introduced
- 7/15/2006 Unit Testing Complete
- 8/15/2006 - Pilots System Testing Complete
- 8/31/2006 V1.0 PRODML Standard Published
- 8/31/2006 Transfer PRODML Deliverables to POSC
for maintenance continued development. - 9/31/2006 - First PRODML compliant Production
Optimization Applications Announced
Working
10WWW.PRODML.ORG
114 - 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
12Pilot No. 1 Model Management
TietoEnator PROSTY Production Database
Schlumberger DECIDE Data Validator
PETEX Prosper Well Model
Well Pressures Well Temperatures
Well Pressures Well Temperatures
Well Pressures Well Temperatures
Well Pressures Well Temperatures Derived Volumes
Derived Volumes Model Alerts
Field Systems with Smart Wells
Schlumberger Avocet Model Validator
Schlumberger Eclipse Reservoir Simulator
Aspentech IP21 Historian
Example XML Consumer
Derived Volumes Model Alerts
Aspentech HYSYS Facility Model
13Pilot No. 2 Model Management
Model Alerts Data Alerts
Invensys InFusion Data Model Validator
Well Pressures Well Temperatures Metered Volumes
Invensys InFusion Notification
Derived Volumes
Well Pressures Well Temperatures
OSISoft PI Historian
PETEX Prosper Well Model
Field Systems
Well Pressures Well Temperatures
Weatherford WellFlo Well Model
Derived Volumes
14Pilot No. 3 Gas Lift Optimization
Manual and Non-Historian Data
Sense Intellifield Portal
Optimizer Constraints Optimizer Targets
Optimizer Constraints Optimizer Targets Well
Pressures Well Temperatures
OSISoft ACE Data Distributor
Well Pressures Well Temperatures
Optimizer Constraints Optimizer Targets
Schlumberger GL Optimizer
OSISoft SiteCom Data Distributor
Optimizer Constraints Optimizer Targets Well
Pressures Well Temperatures
Well Pressures Well Temperatures
OSISoft PI Historian
Field Systems
Well Pressures Well Temperatures
Optimizer Recommendations
15Pilot No. 4 Field Optimization
Invensys InSQL Historian
Tank Outlet Rate Take Inlet Rate Tank
Availability Tank Levels Tank Capacity
Notification Generic
Production (Allocation) Out of Scope
Disposal Well Rates
Network Models
TietoEnator Energy Components
SAP-PRA
Recommended Rates / Time Stamp Production,
Injections, Disposal Wells
Instruction Processor
Water Capacity Simulator Schlumberger RTPRO Opti
mizer
Set Points
PRODML Prod Injection Profile
Allocated Historical
Recommended Rates / Time Stamp Production,
Injections, Disposal Wells
Reporter PRODML
Landmark DSS Forecast
Well Tests
Decline Curves Production Injection
Availability Schedule Production Injectors
(Discover)
Historical Injection
Notification (Lowis)
Production Database Weatherford Lowis
Static Month Injections Rates Days On Well
Injection Target Well Injection Capacity
Well Models
16Final Thoughts
- End goals
- Commercial applications (not a stack of paper)
- Change the software landscape in upstream
operations - Completion target is SOON September 2006
- How can you be involved?
- www.prodml.org