Professional Documents
Culture Documents
Conventional well models treat the entire wellbore as a single entity, averaging all the
fluid properties in the well bore. This means that, for example, if an upper zone is flowing
gas and a lower zone is flowing water, the density assumed in calculating the pressure
drop in the wellbore will be incorrect.
The default segregated well model in ECLIPSE100 and ECLIPSE 300 improves on this
by treating the fluid from each flowing connection separately.
However, neither an average nor a segregated well model can account for:
Frictional pressure drops, which are dominant in horizontal wells
Devices such as valves, pumps, etc.
Multiple flow paths, such as those that arise from flow behind tubing or multi-lateral
wells
For these effects, you need to use the multi-segmented well model. This divides the
wellbore into segments, much like the reservoir is divided up into grid-cells.
FrontSim does not support the segregated or multi-segmented well models. Multi-lateral
or horizontal wells, or wells with large amounts of cross flow, are likely to give different
results from FrontSim than from ECLIPSE 100 or ECLIPSE 300. FrontSim does have a
simpler well bore friction model for use with horizontal wells, but Petrel 2007.1 does not
generate data for this option.
Petrel 2007.1 assumes that tables used in this way include both the frictional and
hydrostatic pressure drops. If the table only includes the frictional pressure drop and you
want ECLIPSE to calculate and add the hydrostatic pressure drop, after exporting your
model use the Keyword editor to edit the WSEGTABL keyword and change item 5 from
FH to F-
When the flow is in the opposite direction to that assumed when calculating the table, the
simulator reverses the flow for horizontal segments, and uses the minimum flow rate
(to approximate a hydrostatic only pressure drop) for vertical or inclined segments.
Petrel treats segments between 45 and 135 degrees as horizontal (reversing the pressure
drop) and other segments as vertical.
Flow paths and Segments
Petrel analyzes the well completions to determine the path along which fluid will flow.
The flow path may be displayed in the well section window by pressing the toggle flow
path display button on the Well completion design or Define well segmentation function
bar.
If a well segmentation set is selected for display on the input tree, and the well being
viewed is included in that segmentation set, then the display of well segments will
override display of the flow path. The segments are displayed along the flow path, so the
display is very similar: the main difference being that the flow path stops at the well head,
whereas the segmentation stops at the bottom hole pressure reference depth, and
obviously that the segmentation display shows the segments:
ECLIPSE supports only a tree like structure for the flow path loops are not supported.
A single well may have two flow paths to surface: flow up the tubing, and flow behind
the tubing in the annulus. Petrel 2007.1 does not support more than one tubing at a time
in the well. Wells with more than one flow path to surface are modeled as two separate
wells in the simulator.
Multiple well bores in Petrel may be connected together to form a single multi-lateral
well; either by creating them in Petrel using the Well path design process, or by
specifying them as laterals when importing the well path see Formats for Well data. A
multi-lateral well will be modeled as a single well in the simulator.
Segmentation Parameters
The segmentation parameters are used to control how the well is divided up into
segments. Generally speaking, the more segments you use, the more accurate the model
of the well (up to a point) but the slower your simulation will be. Segments are always
created to represent devices such as valves, pumps, measuring devices, etc.
The parameters are:
Segment up to (TVD)
This sets the depth in the well below which segments will be created. The pressure drop
above this depth may be modeled with a flow performance table, assigned using a rule in
the Define development strategy process.
This depth is also the Bottom Hole Pressure (BHP) reference depth. To ensure that
all BHPs reported by the simulator are reported at a common datum, set this depth the
same for all wells.
If a branch of a multi-lateral joins the well above the specified depth, Petrel will
generate an error message when exporting the well to the simulator.
If this depth is not set, Petrel will segment up to the top change in flow path diameter,
typically the bottom of the production tubing, or the top point at which a device exists, or
the top point at which a lateral joins the well bore. Note that if the tubing extends below
the top perforation or multi-lateral join, the BHP reference depth may be set below the
top segment in a true vertical depth sense, although it is nearer the wellhead along the
flow path:
convergence, resulting in less time steps. No additional parameters are required - see the
Eclipse documentation for more information.
Accounting for segments roughness when behind tubing. If a segment is in annulus and
we have coincident tubing then, to account correctly for roughness, we export the
Hydraulic (or Equivalent) diameter and the diameter-weighted-average roughness of the
casing and tubing. These values are used by Eclipse to calculate the Fanning friction
factor.
Known issues
If properties of segments (diameter or roughness) change over time, these will not be
reflected in the exported deck. The segment properties will reflect the completion item
that originally generated the segment. This issue will be addressed in a future release.
If a cell is connected to more than one branch of a well (for example, at an open hole
lateral kick off), we currently only export the connection for one of the branches.
Roughness cannot currently be set for valves or pumps. Instead they inherit the
roughness from their associated tubing.
The default roughness for casing and tubing pre-2007.1 was 0.0077" which is
unrealistic. Although casing and tubing roughness could be set prior to 2007.1, the values
were never used. We have taken the decision to auto-correct this value on project import
to the PVTi default of 0.0006". This conversion will only take place the first time a pre2007.1 project is loaded.