Ecrin Guided Session #1...Plugin' and then using the 'Browse' button point to the folder where the BLI files have been previously extracted (i.e. C:\Program Files\KAPPA\Ecrin 4.20\Examples\EcrGS01-BLI)

$Page 1: Ecrin Guided Session #1...Plugin' and then using the 'Browse' button point to the folder where the BLI files have been previously extracted (i.e. C:\Program Files\KAPPA\Ecrin 4.20\Examples\EcrGS01-BLI)$
Ecrin v4.20 - Doc v4.20.01 - © KAPPA 1988-2011 Ecrin Guided Session #1 • EcrGS01 - 1/36

Ecrin Guided Session #1

A01 • Ecrin overview

When installing Ecrin, you are given the choice to install it as an integrated workstation or a

stand-alone application. If the user chooses the stand-alone application option, the program

will ask which application to install (e.g. Saphir or Topaze). In that case, although the full Ecrin

suite is installed, only the chosen application is available (e.g. Saphir or Topaze) and you will

not have access to the different module selections in the 'Application – Settings' panel, or to

the usual toolbar used to switch between the modules .

To change from a stand-alone application to an Ecrin workstation where you can switch

between the different modules, you can either select workstation at installation, or change the

choice afterwards in the 'Application – Settings' panel. If the installation choice is the

workstation, the program will ask which module(s) to install. By default, all modules will be

installed. Here again, the full Ecrin suite will be installed but this time you will be able to switch

between different modules, and it will also allow the reading and creation of files of the

installed-module type (provided a valid license is found). If a module is installed but you do

not have the required license for it, only the reader version of the module will be available: this

is indicated in the switch module toolbar with an ‘R’ superimposed on the module icons

.

Note: In this guided session it is assumed that you have installed Ecrin as a workstation and

have a valid license for Diamant, Saphir and Topaze.

B01 • Objectives

The objective of this document is to introduce the key features of the Ecrin software suite and

introduce you to the easy and intuitive interaction between the modules: Diamant, Saphir and

Topaze.

You will first be guided through the starting up of the project with the loading of Permanent

Gauge Data in the Data Management module Diamant. This loading step will illustrate the data

filtration and updating. Then, you will be shown how to transfer these data with ease to the

Pressure Transient Analysis module (Saphir) via different methods, to go through the

simplification steps of a complex rate history using a few clicks, and to do a partial analysis of

these data in order to highlight some of the features of the software.

Finally the data will be dragged and dropped to the Production Analysis package, Topaze, and

a production analysis and a production forecast will be performed for illustration.


B01.2 • Requirements

Two data sets for this session are stored in a zip file named 'EcrGS01_v420.zip' which can be

downloaded from the KAPPA site - use the WEB menu in the main menu bar of Ecrin and

choose to connect to Ecrin download. After unzipping, the files will occupy 100 Mb on the hard

disk. If Ecrin has been installed from a KAPPA CD, the 'EcrGS01_v420.zip' file content must

have been copied from the CD to the Examples subdirectory. The data sets in

EcrGS01_v420.zip are the files EcrGS01-Pressure.kbl and EcrGS01-Rates.kbl. These files are

binary files that characterize the KAPPA BLI format, a format that Diamant uses internally for

mirroring which provides compact fast access data sets. BLI stands for Binary Large Indexed.

B01.3 • Guided session organization

Section C: Loading and filtering the data in Diamant (=Diamant Guided Session#1);

Section D: Preparing the data for PTA; and

Section E: PTA analysis of the data in Saphir;

Section F: PA analysis of the data and forecast in Topaze;

Note: By default, the plot ‘Always show scales’ option is on. In this guided session, it has been

turned off (in Settings – Plot Aspects - Plots tab).

C01 • Creating a new Field/Document (Guided Session)

After starting up a new Ecrin session, choose the module that will be the starting point

of the project. The module toolbar contains all the active applications for

which a license exists. Click on the icon to start Diamant and choose to start a new project

with a click on the icon . You will then be prompted to enter some field information.

Set the reference date and time to 22 July 2001 at 07:00:00 (AM).

Fig. C01.1 Startup screen


You have access to the field characteristics, Units and general information in the above dialog.

Each field is characterized by the followings:

Name: editable at the field creation; named after the Diamant document thereafter.

File.

Path.

Country.

Location: reference point in degrees, or reference point in decimal.

Latitude and longitude: East and North coordinates according to the format defined

in 'location'.

Reference date and time, this would normally refer to first production start-up.

# of Group(s), Well (s), Gauge (s) and Data.

Click OK and the Diamant main screen is displayed.

Fig. C01.2 • Main Screen


The left side of the main screen displays the content of the browser. The right side of the

window is the 'display' window for the current node shown in the hierarchical browser. After

creating a new field there are 2 active display modes: View List , and View Info .

After data have been loaded, the View Plot and View Table modes are also activated.

Each node type has its own default view mode.

The Browser toolbar provides options to create items for the active field: PVT and Kr, Well

groups, Wells, Sub-folder for the 'Associated files' directory, 'Associated files', and Plots can be

added with a simple click on the corresponding icon.

We will add the PVT and Kr objects which characterize the

reservoir of the newly created field by using their respective

buttons and from the Browser toolbar.

Define a PVT for the current field by accepting the default

PVT settings, and click OK. Define a default 'Oil and Gas' Kr

module in the same way.

Two new items have been added to the 'Technical Objects'

node (see right). Diamant gives an explicit name to each

module depending on the selection made; this name can be

changed.

The objective of this session is to load the production data (single oil rate and pressure)

recorded respectively from a downhole venturi rate sensor and a permanent pressure gauge.

Data are available in two BLI data sets EcrGS01-Pressure and EcrGS01-Rates.

These BLI files are stored in a zipped file named 'EcrGS01_v420.zip' which can be downloaded

from the KAPPA website, use the WEB menu in the main menu bar of Ecrin and choose to

connect to Ecrin download.

If the installation has been done with a KAPPA CD, the files will already have been copied to

the installation directory.

Extract the content of 'EcrGS01_v420.zip' towards the Examples folder of the Ecrin main

installation directory, C:\Program Files\KAPPA\Ecr420\Examples\EcrGS01-BLI.

Note: After unzipping, the files will occupy 100 Mb on the hard disk.


C01.1 • Adding a new well to the field

Before loading the production data, we need to create a well for the field.

Use for instance the 'Add New Well' icon from the 'Browser' toolbar .

Fig. C01.3 • Well Properties

Accept the defaults and exit the Well

Properties dialog with 'OK'. In the Data

Browser, a 'Wells' node has been created

under which the newly created 'Well #1' node

has been added. Expand the 'Well #1’ node

(see right).

At the same time, a 'Field Production' node is

created; this node includes the cumulative

rates ('Sigma' Rates) for each phase by

adding up the wells production belonging to

the same field.

C01.2 • Loading the oil rate

As previously indicated, the raw data for this session are in BLI format. This can be loaded in

Ecrin using a specific plugin. The load plugins are the basic components to access external data

sources, and more specifically to access databases. A plugin corresponds physically to a DLL,

and the modularity permits adding or modifying data access easily. Loading from BLI files is

similar to loading from a database and will illustrate what it takes to access a new database.

To proceed we first need to create a Data Access definition. The only information needed

for the particular case will be the BLI folder location; in the general case, it will depend on

the plugin.


Click on the 'Oil Rate' node in the browser

and right-click. From the 'OIL Rate' popup

menu select 'Load…'. See Figure opposite.

We will load the full rate history comprising

3 MM points (EcrGS01-Rate).

Load - Step 1: Define Data Source

Click on the Database icon to create a BLI data source definition, below left, Figure C01.4.

Fig. C01.4 • Load – Step 1

Fig. C01.5 • Data Source definition

From the Plugin type drop down menu, select the 'KappaBli Plugin' type and press 'Create',

Figure C01.5.


Fig. C01.6 • Kappa Bli definition

Fig. C01.7 • Load – Data source selection

Once in the Kappa Bli Database dialog (Figure C01.6), input a Definition name, i.e. 'EcrGS01

Plugin' and then using the 'Browse' button point to the folder where the BLI files have been

previously extracted (i.e. C:\Program Files\KAPPA\Ecrin 4.20\Examples\EcrGS01-BLI) and

press OK.

Check the Database option and click to proceed. See Figure C01.7.

Fig. C01.8 • Tag selection

The 'Database – Tag Search' dialog pops up (Figure C01.8), click on 'Search' to look for the

'EcrGS01-Rates' data set. Once selected, press OK or double click on this file.

This will automatically lead you to the 'Load – Step 2 – Data Format' dialog.


Load - Step 2: Data Format

When selecting the BLI File, the content of the file is displayed.

Fig. C01.9 • Loading the OIL Rate

Start the load . Diamant scans one point every 1000 (this parameter can be

changed in the 'Loading Data' option in the 'Settings' control panel). Ecrin will detect

automatically that a large number of points are being loaded and therefore an intermediate

filtering step is needed, as can be seen with the checkbox ‘filter’.

Load - Step 3: Filtration Process

Once the initial scan is completed, Diamant displays the filtering dialog which allows the

following steps displayed by the various tabs.

Input file statistics

Preview and Load Window

Pre-load

Filter

Load

You can change the scanning scheme for ‘Quick Stats’ (in this case one every 24 hours) by

changing the duration between two scanned points ('Re-calculate Quick Stats scanning one

data every...'), before clicking on the corresponding calculate icon. The software reads the file

at the appropriate sampling rate and stores this sample in memory.

On this basis, an estimate of the number of points, and the spanned intervals (X&Y) are made.

The next figure illustrates the results of this step.


Fig. C01.10 • Load Data – Quick Stats

Click . A preview plot of the scanned data is displayed. In this plot the zoom

functions can be used to set the load window and thereby easily eliminate outliers and

obviously false data points.

Do not press the calculator button if zoom has been performed. It would set the load

window within the current plot scale. The white dotted line corresponds to the XYMin / XYMax

of the current window.

There is a second level of discarding outliers where the wavelet algorithm is automatically used

on the sample to determine the trend of the data. You can then set the pressure band (ribbon)

to be applied on the trend. Points outside of this band are discarded as outliers.

At each step of the Load data process, text on the bottom of the dialog indicates what the next

action is.

Fig. C01.11 • Load Data – Preview & Window

Fig. C01.12 • Load Data – Pre-load


Click on , the next step consists in pre-loading a portion of the data for filtering

parameters determination. The number of data points to preload can be chosen (see Figure

C01.12). Leave the default value 100,000.

Press at the bottom of the dialog to continue.

This real set of data starts with a gap of more than the imposed condition (1 hour here)

between the first point and the remaining one which makes the first pre-load to fail.

It will automatically switch to the next available portion of data satisfying the preload

conditions. Accept the warning and press OK to go to the following data interval.

The data is displayed and will undergo three steps: Re-sample / Wavelet / Post-filtration. The

wavelet algorithm requires that the data be re-sampled evenly, and the sampling interval

typically depends on the application type. For welltests, the minimum delta time may be used

(1sec or smaller). For production data, a large time step is usually sufficient (5min). An

Intermediate value (15 sec) by default should provide a good compromise for both applications

in most cases.

On the pre-loaded set, the wavelet algorithm is tuned (filter level wheel, can be moved to both

negative and positive levels, zero is the default filtering level), and finally the post-filtration is

set using default values. In this example we leave the filter level at zero. Click on the 'TEST'

button and it can be seen in the below figures, that out of the 19814 points in the window,

around 1763 points are selected in the end after the three steps process.

Note: the 'Keep local extrema' option should not be checked.

On the right (Figure C01.14 Load Data – Active Filtration), bottom view, the difference

between the original and filtered sets is displayed.

Fig. C01.13 • Load Data – Filters

Fig. C01.14 • Load Data – Active Filtration


Once the filter parameters are selected the total data history can be loaded and filtered by

parts of 100,000 points. Select the button at the bottom right of the dialog. For

each new interval, the filter is applied, and the new section is visualized on the screen as can

be seen on Figure C01.15.

If the software finds overlaps in the file, select 'Ignore new data' and click on , the

load proceeds normally.

Fig. C01.15 • Load Data – Processing

The major advantage of this process is that the entire

data is never loaded completely in memory.

You can interrupt the process at any time and decide

to:

Stop the load without saving the current data,

Stop and keep the loaded data,

Resume load without changing any parameters,

Change the filtration parameters for the rest of

the data.


Choose to 'Resume load' to complete the

loading for the entire data set.

At the end of the process, the 'Load statistics'

dialog displays the global statistics

information. Over the original 2,997,346 raw

measurements, around 30,000 lines have

been actually sampled after filtration. That is

1% of the original dataset size, so one

hundred times smaller than the initial size.

Exit the 'Load data' dialog with an OK.

Fig. C01.16 • Load data finished

Select the 'View Info' mode for the OIL Rate node: information related to the original file

and loading process has been updated. Switching to the 'View Plot' mode will display the

OIL rate production plot as seen in Figure C01.18. It can be noticed that although the OIL Rate

has been input as Points, the data can be displayed as points or as steps.

Fig. C01.17 • Oil rate – View Info

Fig. C01.18 • Oil rate – View Plot


C01.3 • Loading the pressure

In the browser, select the node 'Well #1', right click to

display the popup menu and choose to ‘Add new gauge

(mirror)’.

A Gauge (or mirror) is a replica of the original data

gauge, which will be used for creating one or multiple

filtered data samples for use in analysis later on.

Before creating a Gauge, you need to save the file in

order to create the BLI subdirectory containing the

mirror file.

The created gauge will contain the full rate history

comprising about 3 millions points (EcrGS01-Pressure).

We will create later a downsized filtered data set from

this gauge.

Now, repeat the loading process as the one used to load the production data with the pressure

BLI file 'EcrGS01-Pressure'.

In the 'Define Data Source' dialog, select ‘EcrGS01 Plugin' in the Database drop down menu

and press 'Next >>'.

In the 'Database – Tag Search' dialog, press 'Search' and select 'EcrGS01-Pressure'. Press OK.

In the 'Data Format' dialog, the ‘EcrGS01 Plugin' format will be recognized as valid, with the

data type correctly set to Pressure. The BLI file unit Pa has been recognized.

Leave everything else as default.


Fig. C01.19 • Data Format - Pressure

Press ‘Create’ to start the load process. The data are loaded by blocks automatically following

the mirror settings. Their size can be adjusted in the dialog ‘Mirroring settings’ accessed in the

drop list:

You will be warned to use the refresh button following the creation of the gauge.

Once the 3,377,929 points are loaded (they are stored in Well #1-EcrGS01-Pressure_001.kbl.

A preview sample is created (1000 time less points). Note that this is just a preview of the

mirrored gauge and is not the result of the filtering process. The points are just picked

following a regular sampling frequency for speed of display.


You can click on the gauge icon to visualize the data:

Fig. C01.20 • Gauge preview

C01.4 • Filtered Pressure data creation

Right click on the node gauge and select ‘Add

new filtered data’.

Let’s follow the same process as for the production data filtering.

When the filtering dialog appears continue to click and accept the defaults until the

'Filters' tab is displayed. Leave the filter settings as their defaults suggested by Diamant.

Accept the post-filtration with defaults, click the 'TEST' button, and then proceed

to .


For the sake of illustrating the 'Dynamic Update' option in Diamant, we will the

loading process, approximately half way before completion. This time, do not resume loading

after the interruption, but choose the 'Stop but keep current data' option.

Fig. C01.21 • Loading Pressure

From the data browser, select EcrGS01p and choose the 'View Plot' display mode: Pressure

data are shown as points by default as opposed to the rates that are shown as steps.

Click on the icon and change the appearance of the pressure data to red points, click on

the button in the data set properties dialog, and change the screen appearance to red.

Select the 'Well #1' node and hit the

‘Show/hide data set’ icon in the

toolbar.

This option allows you to select the

data set that you wish to display.

You can either enable ‘EcrGS01p’ or

press the ‘Show all’ button. Hit OK to

confirm your selection.

Fig. C01.22 Show/hide data set

The plot is updated and now includes both the oil rate and the (incomplete) pressure data set

as seen on Figure C01.23.


Fig. C01.23 • View Plot – Well #1

C01.5 • Pressure Data Update

We will now proceed and update the partially loaded pressure. You can update a data set in

two different ways:

Right click on EcrGS01p Filtered data node, and select the 'Filter last data' option

from the popup menu or from the plot toolbar, or

In the main toolbar, click on the 'Update all' button , the update process will be

triggered provided EcrGS01p has its 'Dynamic Update' flag set to 'ON'. Right click

on and select the option 'Set Dynamic Update ON'. will then

display a green play mark which means that it can be dynamically updated. You can also

access this option by right clicking on the node to choose the option

'Properties' from the popup menu. Set the 'Status' option to 'ON' instead of 'OFF'.

In this case, Diamant will scan through the document to update ALL the data sets for

which the 'Dynamic Update' flag is set to 'ON'.

Choose to update the pressure data set using the popup menu. Diamant will scan through the

file (the path is stored for each specific data set) and start the loading process from the last

recorded data point (Figure C01.24). The last filtration parameters used during the previous

load have been memorized and are used. Validate with OK and at the end of the process,

Diamant reports a summary of the data update (Figure C01.25).


Fig. C01.204 • Load from last recorded point

Fig. C01.25 • Update Data Summary

The 'Well #1' view plot displays the entire pressure data set as one can see on Fig.C01.26

below. If the entire pressure data is not displayed, click on the Zoom reset icon .

Fig. C01.26 • Pressure data updated

Save the file 'Field #1.kdm'.


D01 • Shut-in identification

A number of Build-ups are visible on the pressure history. Yet the rate history of Well#1,

loaded from the raw downhole permanent sensor is unlikely to present clear null sections

synchronized with the pressure history. In order to ensure synchronization between rate and

pressure for analysis, we will just tag the existing build-ups as such.

D01.1 • Shut-in indicator

Select the EcrGS01p filtered pressure data node in the data tree (in Plot view and not in table

view); at the far right of the Plot toolbar there are several options with the ‘Shut-ins’ title:

This first icon is used to display the shut-in indicator channel, a logical channel equal to 1

inside build-ups, 0 outside, which will be used later on for pressure / production

synchronization. Since we have not defined any build-up yet in the history, this will not cause

any change in the display.

The second icon, disabled at this point, can be used to set a time selection as a build-up.

To enable this option you need first to select period with , then select to confirm it is a

well shut in. This is the manual selection tool.

The third button runs a semi-automatic option to define build-up. The principle of this

option is to pick any points within a build-up, and to let Diamant find the start and end times

automatically. After enabling this option just click anywhere in the period and the shut in will

be defined.

The fourth button is a fully-automatic option to define shut-ins periods. This time the

algorithm will automatically find all the shut-in periods for you, based on a minimum duration

and delta p settings. We will demonstrate in details the use of this option in D01.3

For the moment, let us select the longest shut-in as shown, using the semi-automatic function

click anywhere in the build up to define it, then click on and pick it again to select it

for use:


Fig. D01.1 • Detected build up

A node ‘Shut-in indicator’ will appear in the browser. This is a logical function that is 1 when a

shut-in is detected, and 0 anywhere else.

D01.2 • Shut-in express

Once a build-up is tagged within the build-up indicator channel, it is possible to get a quick

look at the corresponding loglog plot in Saphir with just a few clicks.

A shading appears on the longest build up, since we have selected it .

Click the ‘Shut-in express’ icon; this is the last option of the ‘Shut-in’ toolbar .

A dialog is displayed to control the transfer of data to Saphir, Figure D01.2.


Fig. D01.2 • Shut-in express called for the main build-up

Through this option, a Saphir file will be built on the fly with the current pressure data, and

‘some rate history’ which will be 0 over the shaded zone (the selected shut-in period). For the

rate history prior to the build-up we need to select a given fluid (here only Oil is available) and

we need to select among:

The actual production = ‘OIL Rate’ channel under Well#1.

Part of the actual production only.

A manual entry of production time tp, and rate Q.

We will choose the first option – select ‘Use the total production history’ in the dialog. Leave

the ‘truncate data at the end of the last shut-in’ checked so that only data up to the selected

shut-in period is carried over to Saphir.

Note: the rate history currently holds more than 26000 rates. When we go into a real analysis

later we will reduce those rates to something smaller in Saphir; for the time being all we want

is to have a quick look at the loglog trend without calculating any model but only time

superposition so this is OK

Without further inputs, we are taken straight into Saphir after the Extract dP step. See

Figure D01.3.


Fig.D01.3 • Shut-in express

If we wanted to carry on with a real analysis, the first step would be to visit the Main

Information section of the Saphir document to enter the proper Test and PVT parameters. We

will not do it in this session.

Close the Saphir file (do not save).

Note: you can select several shut-ins periods and still use ‘Shut-in express’ . By doing so,

when in Saphir you will have multiple build-ups or fall-offs extracted at the same time in the

loglog plot and the semilog plot, very useful for comparison.

D01.3 • Automatic Shut-in

Go back to Diamant and stay in the EcrGS01p Fltd data node. This time we are going to use

the automatic shut-in functionality to define all the build-ups in one go. This option allows the

user to define multiple shut-ins in the history using an algorithm which considers the pressure

behaviour and shape.

Click right on the node, then above the plot window, click on to reset the

channel to 0. You can do this by right clicking on the shut-in Indicator node as well. All the

defined shut-in periods will be erased.

Click on the EcrGS01p Fltd data node and display the plot.

Click on the button .


The shut-in detection settings dialog appears:

Make sure that ‘analyze the signature of the

data’ is checked with the displayed option

selected.

Set the minimum pressure change for a shut-

in to be 200 psia and minimum shut-in

duration to be 1 hour.

Press OK.

All the BUs detected, according to the criteria, are highlighted. see Figure D01.1 below.

Fig. D01.4 • Detected build ups

Clicking on the node ‘Shut-in indicator’ displays the all the BU’s detected.

Before using these multiple build ups for analysis purpose, we need to clean and adjust the

production history in order to get it synchronized with the pressure history.

Note: Although the automatic detection is very useful and can speed up significantly the data

pre-processing stage, it is based on an algorithm which may sometimes come up with incorrect

limits if the pressure build-up exhibits such behaviors as irregular humping, soft shut-ins, very

noisy shut-ins, etc. In those situations, you can correct the limits manually or semi

automatically. In our current case, the selection made automatically can be kept.


D01.4 • Corrected production

Click right on the well# 1 node and select the

option ‘Create/Reset corrected production’.

Keep the default setting in the dialog:

Press OK.

The created ‘Corrected data’ is a pre-defined derived channel (explained below), its equation

can be seen by double clicking on the ‘oil rate’ channel under the ‘corrected production’ node

(expand the node to see the ‘oil rate’ channel):

Fig. D01.5 • Derived channel definition

Set the ‘corrected production’ oil rate curve in red.


The objective of a derived channel is to create an output data set resulting from n input

channels. Writing ‘Y’ the Y values in the inputs, the values of the new channel are defined as:

Ynew[t]= f(Y1[t], Y2[t], Y3[t], …, Yn[t],a1,a2,…, ak).

Where the parameters ‘a1’… ‘ak’ are user defined constraints.

In this particular case, the channel is defined in such a way that the resulting ‘corrected

production oil rate’ channel is set strictly to Zero whenever a shut-in is detected in the build-up

indicator channel, and will leave the rate as it is originally in ‘raw production’ anywhere else.

As a derived channel, the corrected production would be extended automatically as the input

oil rate gets updated via the database. All we would need to get this channel up-to-date is to

pick the future build-ups so that the build-ups definition is up-to-date.

Fig. D01.6 • Real rates; BU Indicator; Corrected rates

You can select the Plot view for Well#1 , select ‘raw data production oil rate, ‘corrected

production oil rate’ and ‘shut-in indicator’, to view the difference between the original

production and the modified one. A blown-up view at the beginning of one of the longest build-

up is presented on the Fig. D01.6. Note that the corrected production is a representation of the

surface rates. When downhole rates are present and we have soft shut-ins of the kind above, it

may be preferable to define the build-ups only at the time when the downhole rate vanishes.

This is beyond the scope of this session.

By applying this formula we can see here that the rate now is strictly zero when the build up

indicator is 1 (means that a shut-in is selected), eliminating thus potential noises when there is

no flow, and strictly cut to zero at the start of shut-in for synchronization with pressure

history.


E01 • Initializing a Saphir (PTA) project based on the automatic shut in

detection and the corrected production

In the application toolbar , choose Saphir . Start a new project by a click

on the icon, keep all parameters and PVT defaults.

Go back to Diamant and click on the node ‘Fltd data’ under ‘EcrGS01p’, then on the top bar

icon , to send the pressure channel to Saphir:

Fig. E01.1 • Selection of the Saphir session

Proceed in the same manner for the ‘oil rate’ channel, under ‘Corrected Production’:

Go back to Diamant, click on the node ‘Corrected Production / Oil rate’, press on the icon in

the toolbar to send it to the same Saphir session.

Note: the transfer could also be done through the browser:

Open the data browser and click on the button displaying the hierarchical tree of both

the Diamant and Saphir project. Select the Diamant and Saphir project in the 'Opened

documents' pane by ticking the corresponding checkbox. Now drag the pressure gauge in

Diamant to the Saphir project (Figure E01.2).

Fig. E01.2 • Pressure drag and drop in the browser


Note: a final method to transfer data: in the same manner, create a new Saphir project.

In Saphir, under ‘Interpretation’ tab in the left hand bar, click on and select the option

‘from an opened Ecrin document’. Choose the corresponding oil rate to load.

Perform the same when loading pressure with .

Let us go back to Saphir.

E01.1 • Extracting multiple build-ups

Proceed to load multiple build-ups. Click on the 'Extract dP' icon and choose 'List' on

the 'Group' line in the next dialog.

Then specify to extract 'Any build-up' with duration of more than 5 hours.

The loglog and semilog plots are shown, Figure E01.3.

If you wish to have the legend appearing in the plots, click on the Legend icon .

Fig. E01.3 • Loglog and semilog of multiple extracted periods

As a selection of the build-ups has been extracted it is possible to investigate if there has been

any major change in skin and permeability during the recorded production history.


When extracting multiple build ups on the loglog plot, sometimes it is difficult to distinguish

among all the plots the one that we would like to observe. In that case, the user can use the

‘pick’ option to highlight the wanted build up. Maximize the loglog plot, click on in the

toolbar above, and select for example build up #15 (grey) as shown in the figure below.

Fig. E01.4 • Loglog of multiple extracted periods showing the highlighted BU#15

Right click in the loglog plot and choose from the 'Line' option, the 'Multiple + vs. time' and

'Select range', as shown in the figure E01.5. The range to select is indicated by the white

square (click and drag) in the loglog plot of this Figure.

Fig. E01.5 • Multiple straight lines (vs. time + Select Range)

Two distinct options exist to draw lines simultaneously on a set of extracted build-ups: 'All', or

'Select Range'. When using the 'All' option, a time range is specified and Saphir runs a non

linear regression on each build-up in turn.


When using 'Select Range', the process starts in the same manner, then any build-up with a

deduced kh leading to a derivative level outside the specified box is discarded. For the valid

build-ups, a non linear regression is run imposing a unique slope, and one intercept per period.

A plot of Skin versus Time is displayed that can be used to evaluate the change of the well

potential over time. Right click on the plot and select ‘Line - Show’ and ‘Average – Show’ to

display the straight lines. Figure E01.6 is the Semilog plot and Figure E01.7 is the plot of Skin

versus Time, after deletion of one point.

Fig. E01.6 • Semilog plots

Fig. E01.7 • Skin versus Time

The skin deduced from the straight line on few Build-up are off and they can be removed from

the line calculation by clicking on them an specifying not to use them in the least square line

calculation.

E01.2 • Pressure Transient Analysis

To determine the most appropriate model, extract Build-up #2 only. In the toolbar, select

Build-up #2 from the ‘Group’ drop list. It is evident from both the derivative curve, and the

depleting pressure observed in the history plot that the reservoir is limited and bounded.

Fig. E01.8 • Loglog plot of Build-up # 2

Right click in the plot and select 'Line' and 'Delete' to hide the semilog straight line marker.

In the top tool bar, click on next to the gauge name to rename it as ‘Fltd data Backup’.

Since the pressure history was filtered using wavelets (in Diamant) we will first check that we

did not distort the shape of the derivative.


This can be done as follows:

1. Make Diamant active again by clicking on in the toolbar.

2. In Diamant, click on EcrGS01p Fltd data and select the Plot View mode .

3. Zoom in on Build-up #2 using the toolbar icon (start around August 3rd, 2001, end

at August 6th 2001) and use the time selection icon in the plot toolbar to highlight a

time interval containing the build-up. You can zoom in several times to obtain better

results. You can also perform a zoom reset whenever necessary to start the

selection again.

4. It is possible to re-load the data for the highlighted section only. The 'Partial re-load'

option is called with the icon . You will be prompted to backup your original data.

Activate ‘Backup the original data’ and press ‘OK’ to continue. Diamant reconnects to

the source of the data and positions itself on the selected interval. We may now change

the filter settings for that section. In this case we will not choose not to use any filtering

and re-download raw data only. (Fig. E01.8).

5. In the Filters dialog uncheck: 'Wavelet', and 'Post-filtration'. Press 'Load'. (Fig. E01.9).

6. The modified EcrGS01p Fltd data gauge contains now the raw data in Build-up#2. If

you check the information of the new data, you can now see the number of points is

about 370 000 instead of 26 000.

7. Click on the icon to send this ‘repopulated’ data set to Saphir.

Fig. E01.9 • Selecting the Build-up # 1

Fig. E01.10 • Partial re-load with no filter

No noticeable difference is seen in the shape of the derivative other

than added noise, Figure E01.11. The wavelet filter, as we set it

originally, did capture the characteristic features of the response while

significantly reducing the number of points and thus eliminating the

noise. So in the Saphir document, we can safely revert the analysis

pressure to the first gauge (Fltd data Backup), see opposite.


Fig. E01.11 • Build-up#2 with all the raw data

In addition to the pressure depletion observed in the history plot, with the radial flow line

(white dotted line on the loglog) placed as illustrated in Figure E01.12 the diagnostic is quite

straightforward: the system is closed and the well is near two faults much closer to the well.

If the radial flow line needs to be moved, click on the white dotted line and drag the line

accordingly.

Note: the rate history is at this stage of the visit made of about 30 000 values. Before running

any model it is necessary to reduce the number of flow period in order to make the simulation

duration reasonable.

To do so, go to Edit rates, select all the rate data , open the processing box , select the

tab ‘Simplify’ and impose a ‘% Delta’ of 5% for rate simplification.

Click on the ‘Test’ button, check that the rate number is reduced to around 2150 points.

Press OK to exit.

After setting the radial flow line, start the interpretation using the automatic model to

estimate skin and adjust the early time match.

To access this option, select 'Interpretation' and then press Shift + . A message

indicates that the model is being generated.

Then, open the 'Model' dialog to add the closest faults, using the intersecting sealing fault

option: choose 'Intersecting faults – Any angle' in the Boundary model section.

Add a fault at 950 and 4700 ft at an intersecting angle of 90°. Set kh to 13000 mDft

and C to 0.011 bbl/psi and S to -1. Run the model clicking 'Generate' and the match

between the model and the data in the loglog plot of Build-up # 2 should be very close.

See Figure E01.13.


Fig. E01.12 • Loglog match of Buildup # 2

Change the extracted group to build-up to #15 (main build-up).

You can use the pick option in the ‘Extract dP’ dialog: in the pick dialog, you need to first

erase the current selection with .

Looking at the history plot and the build-up#15 shows the necessity to close the reservoir

system completely. See Figures E01.13 a&b.

Fig. E01.13 a&b • Model displayed on loglog for Build-up #15 and history plot

The challenge is now to change the model to a closed rectangle and vary the distance to the

two other closed boundaries until a match has been obtained. For the sake of demonstration,

the final match in this guided session is a rectangle with the following distances to the closed

boundaries:

South 950 ft

East 4700 ft

North 20,000 ft

West 12,000 ft

In the 'Model' dialog, select 'Rectangle' as boundary model and input the above distances.

Generate.


The Final match is shown in Figure E01.14.

Fig. E01.14 • Final match

F01 • Initializing a Topaze (PA) project based on data loaded in Diamant and

Saphir

In the application toolbar of Ecrin , choose the Topaze application.

Start a new project by a click on the icon , keep all parameters default. Open the browser

and click on the button to display the hierarchical tree of both the Topaze and the Saphir

projects.

Select the Saphir and Topaze documents in the 'Opened documents' left pane. Drag the whole

Saphir project and drop it on the newly created Topaze session.

Fig. F01.1 • Browser drag and drop

This will launch the complete startup process of Topaze automatically. All the information, well

and reservoir characteristics, PVT and data will be copied. Extraction will take place, and you

can generate the same model as the one used in the Saphir pressure transient analysis. Close

the Browser dialog. By default you will end up with the screen seen in Figure F01.2. You may

need to press on the Zoom Reset icon on certain plots to get the proper display.


Fig. F01.2 • Topaze window

By dragging the Saphir project directly to Topaze, the Topaze file has used the simplified rate

history that was prepared in Saphir. As Topaze is a production analysis tool it is best to have

many points describing the production, thus it can use the original rate file loaded in Diamant.

In the Browser , activate the required opened documents, then drag and drop the oil rate

from the Diamant project to the Topaze session, as illustrated in Figure F01.3.

Fig. F01.3 • Browser, drag and drop the 'Corrected OIL Rate'

from Diamant to Topaze


Because the rate data are very flat at the beginning, it is

necessary to set the range start time to 25/07/2001

at 12:30:00 am (select ‘absolute time’ option).

Be sure to 'Keep the current match values' before

re-generating.

Close the Browser.

Click on the Model button , check generate q(p), p(q) and single step response.

Uncheck the fast model option if selected. Adjust pi to 9800 psia (if you check the pressure

gauge this is closer to the starting values).

Click 'Generate', the final results are obtained, as displayed in Figure F01.4 (for the sake of

ease of reading, several plots were deleted, others rescaled).

Fig. F01.4 • Topaze screen


In this case the Arps analysis is not useful since there is no significant rate decline during the

history. The Fetkovich plot is not useful either since its validity assumes constant flowing

pressure which is not the case in this example.

This highlight the necessity to model the well production behavior with theoretical models

taking into account reservoir geometry and material balance, similar to those used in pressure

transient analysis, as these are the only tools that can make reasonable forecast in such cases.

F01.1 • Forecast

Click the Forecast button and choose to extrapolate the current model

and to generate q(p).

Click on the button to enter the forecast criteria.

Hit the Duration unit header, change it from ‘Hours’ to 'Day'.

Add two lines to forecast the production forward 200 days, respectively 100 days at a

pressure of 4,000 psia (expected flowing bottomhole pressure) and 100 days at a pressure

of 3,990 psia.

Fig. F01.5 • Forecast criteria

Click 'OK' and 'Generate'. Forecast is displayed in the history plot, Figure F01.6.

Fig. F01.6 • Forecast

Documents

Ecrin Guided Session #1...Plugin' and then using the 'Browse' button point to the folder where the BLI files have been previously extracted (i.e. C:\Program Files\KAPPA\Ecrin 4.20\Examples\EcrGS01-BLI)