Title: Digital Tidal Wave or Steady Erosion
1Digital Tidal Wave or Steady Erosion
2Upstream EP Value Chain
DATA are the DETAILS
Now we are managing the decline now as well as
adding reserves!
3Digital intensitythe impending tidal wave
800 TB
500 TB
Active technical data storage for ChevronTexaco
in TB
200
160
120
80
40
0
2004
1997
1998
1999
2000
2001
2002
2003
4Oil fields of the future real-time oil and gas
operations
Onshore Facilities
Offshore Facilities
Decision Centers
new capabilities much more data much more
exposure
5Knowledge Management (Perhaps better thought of
as knowledge utilization/integration?)
Extract knowledge from the information for some
goal
- Application integration, information integration
happens to create better tools and data sources
to leverage How do we extend this to help
integrate business processes? - How can I combine multiple sources of
information to create knowledge to act on? - How can I share this with someone else or use it
in an unintended way? - How would information flow seamlessly through my
workflows? - Who are the experts in this subject area? Who
can help me? Who else needs to know about this?
Information Management
Organize the bits into records that describe
our subject areas and manage those records
- Ownership
- Single source of truth? Where is the trusted
data? - Replication and Synchronization of copies?
- How do I find what I created in the past?
Value of data changes over time most data
becomes less valuable over time how to we
measure the value over time?
Data Management
Access directly from process on same
machine Client server access Client server
through some middle ware isolating apps from data?
Manage the bits of data
- How is the data accessed?
- Where is the data physically stored?
- How is the data organized online and/or offline?
- Where is the data accessed from (desktop,
server, cluster, web service)? - SECURITY! SECURITY!
Hardware solution that provides best efficiency,
performance and cost for the users requirement
Largely application dependent and dependent on
local business process for consistency in
implementation there are dos and donts and
things that can help
6Basic Bits of Petrotechnical Data
- Lease
- Corners, Operator ship, Owners,
- Well (GUWI)
- Status, Surface Location, Directional Survey, KB
Elevation, Operator, - Completion
- Depth, Type,
- Surface Equipment
- Pumps, Compressors,
- Subsurface Equipment
- Well jewelry
- Reservoir
- Name, Penetrations
- Field
- Name, Outline,
- Logs
- Gamma Ray, Porosity, Resistivity,
- Calculated Logs
- Water saturation, porosity, etc.
- Production (ProdML)
- Well tests
- Allocated Production
- Injection
- Rates, Pressures,
- Maintenance
- Surface Equipment
- Subsurface Equipment
- SCADA
- Surface Equipment
- Subsurface
- Financial
- Costs
- Seismic
- Navigation Data
- Trace Data
- Attributes
- Drilling
- Depth, survey, mechanical, perfs, completion
info,
7Why ProdML
- For Operators,
- Reduces costs of moving data,
- Enables Plug and Play
- Reduces integration costs
- Facilitates BluePrinting
- Facilitates choice of vendor
- For Service Companies,
- Reduces support costs (having to maintain
different systems for different operators) - Accelerates introduction of new technology
ProdML will help accelerate implementation of
smart field technologies in the oilfield, while
reducing the cost of operating them
8Benefits of Well Identifier Standardization (GUWI)
- Wells/wellbores would be properly identified with
a UWI and name - thus reducing confusion, misidentification
- Would help enormously in digital data exchange
- Oilfield service companies (e.g. Schlumberger) to
oil companies - Technical service companies/consultants (Core
Labs, Fugro Robertson etc) to oil companies - Data exchange between partners. Well related data
(wells, log curves, production etc) are currently
delivered with the partner's internal ID which is
meaningless to CT and vice versa. Current
examples where we get regular partner data are
Congo and Chad - Bid round packages
- Farm-ins/Farm outs
- When we are trying to integrate/incorporate new
data from various sources for interpretation/analy
sis, first thing is to identify/match wells and
compare to what we already have. - Building national repositories - operators will
be sending well master, directional surveys, log
curves, documents probably separately with only
inconsistent well names for ID. It will take
extra time/effort/cost for the Schlumberger's and
Halliburton's who build/manage these repositories
9Value of well locations and free exchange of well
header info
- The advent of global positioning satellites and
geographical information systems has increased
the accuracy of spatial measurements by orders of
magnitude. - The luxury of these accurate measurements may
induce us to forget some basic cartographic
principles of data precision which govern older
spatial datasets. - A study of well locations from Country X show
that data rounding and truncation, not
cartographic datum shifts are the most likely
source of well location errors. - To rectify this 45 slides later through geodesic
forensics the wells are put in a
reasonable/internally consistent location but not
necessarily in the right place. - With a GUWI, the initial well match between
different sources would be automatic and save
some upfront time in matching wells. - It would also allow you to automate the initial
assessment of differences. - Exchange formats for well spatial, including
surface locations and directional surves, should
always include cartographic and geodetic
information - for seismic nav, UKOOA and
SEG-P1/P3 exchange formats have had this for more
than a decade
10Digital Tidal Wave or Steady Erosion
- Enabling technologies just dont get mega
funding. - These goals are best accomplished by setting less
lofty near term goals and showing success. - Witsml is an Example of that.
- ProdML could be.
- GUWI could be.
- Long term strategies are important, but given the
business environment we are in it behooves us to
show results.