Completion Object Overview
June 2013
WITSML/PRODML Standards
Completion Object Project
• Started: May, 2011 with participation from both WITSML
and PRODML
• Participating companies: Chevron (sponsoring operator),
Weatherford, Peloton, (lead vendors), Schlumberger,
Paradigm, ExxonMobil, BP, Total, Halliburton with
Energistics
• Delivery for Special Interest Group and subsequent public
review: January 2013.
• After review, final version release: June 2013
Business Case and Benefits
High Level Application of Completion Object
Primary Initial Usage
1. Drilling – Production hand-offs
– DB to DB sync & transfer
– Initial completion & subsequent workovers
2. Initial Completion transfer from rig
3. Well services through life of asset
4. Engineering applications transfers
– Eg, Nodal analysis models
– Well surveillance
Primary Initial Use Case: Over the Well Lifecycle, Drilling &
Production MUST Pass Data Back and Forth
Drilling & Completions Domain Production Domain
Primary Initial Usage
New Completion
Drilling system
Current WITSML Completion DB
Workover Planned
Now
Enabled Data
Updates
Drilled As Completed
Well Well
DTS
Well Services
SSSV
E.g. Gas Lift
Tubing Change
Perm.
Packer Gauge
Perforations
Business Drivers and Benefits
• Eliminate multiple data entry requirements thereby
improving accuracy and saving time
• Improved safety. Knowledge of what is down hole
will improve operations
• Improved data consistency, accuracy, quality
• Improved planning and scheduling (through faster
access to better quality data and by eliminating
manual re-entry of data)
• Reduce reliance on paper or spread sheet well files
Concepts for Completion Object
Three Use Cases dealt with in this release
1. Snapshot of completion at a point in time
– “what is current status?” eg for completion diagram,
engineering application eg Nodal
2. Change Log of events which alter completion between
one time and another
– Eg, from well services contractor
3. Cumulative History – whole life of well capable of
generating current snapshot or any previous one
– Eg, for sync or transfer between databases
Example Snapshot at One Instant
Snapshot is akin to a
DTS completion diagram
SSSV
at one instant in time
Tubing Casing
Perm.
Packer Gauge
Perforations
Example Change Log for Single Job
DTS DTS
SSSV SSSV
Tubing Casing Tubing Casing
Perm. Perm.
Packer Gauge Packer Gauge
Perforations
Well CM [Construction
Perforation Job
and Maintenance]
Ledger entry
Perforations Data concerning change, in
Downhole Components
Example Well Cumulative History
Day 1 Day 4
Events Well equipment
Well CM Ledger Downhole Components
gets added to added, updated or removed
cumulatively by Events
Data Organization
4 top-level objects:
1. Downhole Component - contains wellbore
equipment
2. Well Construction Management Ledger - contains
details of Jobs & Events
3. Well Completion –associates a wellhead stream
with one or more wellbore completions (completed
zones) in the well
4. Wellbore Completion – represents a section of
wellbore open to flow with reservoir.
Scope of Downhole Components
Wellhead Accessory
Wellhead: not described
Cement: placement as
in full detail
well as properties (also
Downhole String Set other fills)
Casings: multiple strings
Accessories to strings:
supported, can include
e.g. packers, gas lift
joint tally
valves
Tubings: multiple strings
supported, can include Borehole String Set
joint tally Borehole: the open hole
sizes as drilled
Perforation Sets Formation Layers: with
String Equipment
Perforation Set: physical Equipment: the basic properties
description of components used
perforations etc.
Assembly: groups of
components
Scope of Well Construction Management
Ledger
1. Identity information such as the well name
2. Event Information, eg depth & time ranges of
operation
3. Completion reference information including references
to string, equipment.
4. Operational/management information eg, business
associate, w/order number, cost, rig ID, flags if
operation was planned/unplanned etc.
5. eventExtension - contains the job data (limited types),
may have reference to details in a WITSML object
6. Participant – enables link to be made to any WITSML
object, eg a log. No semantic meaning conveyed.
Nesting of Jobs containing multiple Events
• An event in the ledger can have a parent event ID.
• Events can be organized into a hierarchy.
• Eg, “Job Producer” = top level event
– “Sub Job” Events with this “Job Producer” parent:
– “Job – Well Service Rig Crew”
– “Job – Site Work”
– “Job – Tubing Inspection”
– From Different Service
providers
– Hence, each service
provider can supply their
report to operator using
the data-object
Scope of Flow Paths, Reservoir to Wellhead
Parent =well Parent =wellbore Parent =
downholeComponent
Well Completion: a
commingled “flow” in
the well, eg “X”
A References Well Completion X
Not Specified: flow
Wellbore Completion: through specific tubing
section of borehole strings etc
open to flow , eg “A”
Contains Contact Intervals
These would be further
Contact Interval: physical
Wellbore Completions &
connection to reservoir,
Contact Intervals, linked to the
4 types: perf, o/h, slot, g/p
2nd tubing string’s Well
References Perf set, borehole, Completion
equipment as appropriate
AND Geology feature
String Equipment: has
Perforation Set: physical
Ref’d Perforated Intervals: from
perforation details
this component (eg casing)
Role of Well and Wellbore in Completion
The whole completion
Well Completion (where spans multiple wellbores
Well “flows” are defined so Downhole Components
has parent Well has parent Well
String and Equipment
have parent downhole
Each wellCMLedger entry component and are
in wellCMLedgers can associated with a wellbore
apply to a different well (in (the end (bottom) point
addition to wellbore) will define which
wellbore)
Borehole has parent
downhole component
and is associated with
a wellbore
Wellbore Completion
and Contact Interval
has parent wellbore
Future Plans (Possible)
• Surveillance, flow paths etc – where are instruments,
flows reported & measured (PDGs, DTS, etc.)
– in complex completions especially
• Optimization – addition of inflow performance and
description, fluid properties Nodal Analysis
• Reservoir connection made explicit e.g. with link to
RESQML layers
• Tree and surface equipment
• Further “xxxJob” objects, eg perfJob, gravelPackJob,
which contain full details of operations (not just “end
result” of the jobs)
Other (secondary) Use Cases in Production
Domain
Production Domain
Completion DB
Optimization using
Nodal models
Flowing DTS
Intervals,
sensor depths
Perm.
Gauge
Summary
• A Major new Capability for life of well completion data
management
• Needs promotion and adoption now
• Potential to Expand Data Coverage and Usage
• Potential to support new “Well Services DOF” industry
approach with standard services reporting method
