Petrel TIPS&TRICKS from SCM

(1)

Petrel is a mark of Schlumberger

4801 Woodway Drive, Suite 150W • Houston, TX 77056 • www.scminc.com • [email protected]

1 K n o w l e d g e W o r t h S h a r i n g

Petrel TIPS&TRICKS from SCM

Importing Well Completion Data

Importing well data in Petrel can be a time‐consuming process. There are multiple types of data (headers,

logs, completion, etc.), each having multiple possible formats. Hopefully, your company database takes

care of much of this import for you. However, you will probably have to import data at one time or

another (new wells drilled, wells missing from database, data bought from another party, etc.). Most

experienced Petrel users are familiar with importing a lot of the data it takes to fully describe a well. Many

have never tried importing completion data. That is the purpose of this TIPS&TRICKS.

Usually, importing well data has up to five separate imports. They are:

1. Importing Headers

2. Importing Deviation Surveys

3. Importing Logs

4. Importing Tops

5. Importing Completion Information

The first four are fairly common and not a part of this document. Here, we will focus on importing

completion information only. This document was written using Petrel 2011.2, however earlier versions of

Petrel are very similar.

(2)

2 File Types

Completion data in Petrel consists of two files, events and tubing. We will discuss both in turn.

First, the events file. Contained in the events file are:

Event in File Petrel Completion Name Perforation Perforation Barefoot Perforation Rework Perforation Acidize Stimulation Stimulate Stimulation Frac Stimulation Plug Plug Squeeze Squeeze Welltest Well test Hydr‐frac Hydraulic fracture

An example of an event file is:

Note that it always starts with a “UNITS” line.

(3)

3 Contained in the tubing file are:

 Casing

 Tubing

 Bullplugs

 Chokes

 Packers

 Inflows (AFCV – Annular FCV ‐ Flow Control Valve)

 Inflows (NICD – Nozzle ICD ‐ Inflow Control Device)

 Inflows (SICD – Spiral ICD)

 Inflows (LICD – Labyrinth ICD)

An example of a tubing file is:

(4)

4 Note that it also always starts with a “UNITS” line.

(5)

5 Event File

To import an event file, right‐click on the Global completions folder under the main Wells folder and

choose Import (on selection)…:

This brings up an Import file window:

a. Navigate to the correct folder

b. Change the Files of type: to Well event data (ASCII) (.ev)*

c. Select the File name as the file (or files) containing the event information.

d. Click Open

(6)

6

You are asked to match the data in the event file to the wells already in the Petrel project using the following window: If a well name in the file doesn’t match a well inside Petrel, you may ignore the data, or choose the well to assign the data to. After clicking OK, the data is imported and can be seen under the Global completions folder under the main Wells folder.

(7)

7 Event Data Format

The event data file must start with a “UNITS” line. This line looks like: UNITS METRIC where the second word tells the units of the data. Choices are METRIC and FIELD (feet) for the data. The units need not be the same as the units used within the Petrel project as Petrel converts them as they are imported. The file may have comments (lines in the file but not used as data) to show information. A comment line starts with two dashes (‐‐). An example comment line is: ‐‐ Data for well A10 You may also specify units for specific dimensions using keywords. They keywords are DEPTH, DIAMETER and PRESSURE. The line for DEPTH looks like: UNITS DEPTH units where “units” is any recognized depth unit symbol. You may similarly set the units for DIAMETER and PRESSURE with: UNITS DIAMETER units UNITS PRESSURE units Again, the units are converted upon import into Petrel. Data is separated into the different wells in this file. Each well group starts with a “WELLNAME” line. This line looks like: WELLNAME A10 where “A10” in the example above is the name of the well. This name will be matched to the wells already inside the Petrel project. The different types of event data for a well have different formats Perforation, Barefoot and Rework data are converted to Perforation events inside Petrel. Perforation and rework events both have the same format and have the following columns: Date of event, “event type”, Top MD, Base MD, Wellbore Diameter, Skin Examples are: 01/01/1995 perforation 1858 1865 .5 0 01/12/1997 perforation 1870 1878 .5 0 05/18/2006 rework 1900 1925 .5 0

(8)

8

Barefoot data does not contain the Base MD. It’s columns are: Date of event, “barefoot”, Top MD, Wellbore Diameter, Skin 03/05/2005 barefoot 1922 .5 0 Welltest data has the following columns: Date of event, “welltest”, Kh An example is: 02/01/1900 welltest 1883 Acidize, Stimulate and Frac data are converted to Stimulate events inside Petrel. They all have the same format: Date of event, “event type”, Top Depth (MD), Base Depth (MD), Skin Examples are: 02/06/2004 acidize 2000 2015 0 10/07/2001 frac 1942 1955 ‐2 07/22/2002 stimulate 2150 2230 10 Squeeze data is formatted as follows: Date of event, “squeeze”, Top Depth (MD), Base Depth (MD) Examples are: 01/01/1995 squeeze 2000 2150 01/01/1995 squeeze 2250 2300 Plug data is formatted as follows: Date of event, “plug”, Depth (MD) and all deeper An example is: 02/01/2000 plug 2400 Hydraulic Fracture data is formatted as follows: Date of event, “hydr‐frac”, Center (MD), Top(TVDSS), Bottom (TVDSS), Length, Orientation, Permeability, Width An example is: 02/01/2000 hydr‐frac 1900 1880 1920 100 0 10000 0.005 Combined, some events might look like: WELLNAME A15 01/01/1995 perforation 1858 1865 .5 0 02/01/1995 welltest 1883 02/01/2000 frac 1942 1955 10 01/01/2002 squeeze 2250 2300 02/01/2003 plug 1800 To find information about this in the Petrel help file, go to the Search tab and key in “well event file format”. Filter to the Title “Well event file format” in the Petrel location (among the multiple documents returned by Petrel Help) and you will find more information.

(9)

9

Perforation data looks like this in a 3D Window (left) and a Well Section Window (right): Well Test data looks like this in a 3D Window (left) and a Well Section Window (right):

(10)

10

Stimulation data looks like this in a 3D Window (left) and a Well Section Window (right): Squeeze data looks like this in a 3D Window (left) and a Well Section Window (right):

(11)

11

Plug data looks like this in a 3D Window (left) and a Well Section Window (right):

Tubing Data

To import a Tubing file, again right‐click on the Global completions folder under the main Wells folder and choose Import (on selection)…

(12)

12

This brings up an Import file window: a. Navigate to the correct folder b. Change the Files of type: to Well tubing data (ASCII) (*.tub) c. Select the File name as the file (or files) containing the event information. d. Click Open Again, you might have to match wells:

(13)

13

After clicking OK on the window where wells are matched, the data is imported and again shown under the Global completions folder under the top‐level Wells folder in the Input pane. Expanding the Completions folder under an individual well shows what was imported for that well.

(14)

14 Tubing Data Format

The tubing data file must start with a “UNITS” line. This line looks like: UNITS METRIC where the second word tells the units of the data. Choices are the same as with the event data file (METRIC and FIELD). The file may also have comments to show information. A comment line again starts with two dashes. Data is separated into the different types in this file:  Casing  Tubing  Bullplugs  Chokes  Packers  Inflows The different types of tubing data for a well have different formats Casing data has 3 lines for each entry. The first line has: “CASING”, well name The second line has: Top Depth (MD), Casing Diameter, Casing Roughness The third line has: Bottom Depth (MD) An example of a complete entry is: CASING A15 0 0.15 0.001 1955 Tubing data also has 3 lines per entry. The first line has: “TUBING”, Tubing Name, Start Well, Stop Well The second line has either: Top Depth (MD), Internal Diameter, Internal Roughness, External Diameter, External Roughness OR Top Depth (MD), The name of the equipment that describes the casing The third line contains: Base Depth (MD)

(15)

15

A complete example showing diameters and roughness is: TUBING Tubing11 C2 C2 0 0.12 0.01 0.14 0.01 2470 A complete example showing the equipment is: TUBING Tubing11 C2 C2 2300 “T‐API‐1.050/J‐55/1.20” 2470 Currently, Petrel only supports tubing that starts and ends in the same well. If the start and end well names are not the same, a tubing will be created from the top of the end well to the specified end MD. Also, Petrel only supports tubing that starts at the top of a well. If the start MD is not 0, Petrel will ignore the value. Bullplugs are used to seal the tubing toe (to force fluid flow in through an ICD). This data must have a TUBING for the well before you can define a BULLPLUG (The TUBING line must precede the BULLPLUG line). The line contains: “BULLPLUG”, Well Name, Tubing to be plugged An Example is: BULLPLUG C2 Tubing11 Choke data is modeled in Petrel as an inline FCV. Tubing must be previously defined before entering the choke values. To specify the location of a choke, use the following format: “CHOKE”, choke name, tubing for the choke, choke MD, (optional) choke length or equipment ID An example using defaults is: CHOKE Choke11 Tubing11 2200 An example specifying the length is: CHOKE Choke11 Tubing11 2200 4.5 An example specifying the equipment is: CHOKE Choke11 Tubing11 2200 IFCV_1 Packer data uses the following format: “PACKER”, packer name, well name, DEPTH (MD), (optionally) length: An example is: PACKER Packer01 A10 2200 5 We have had problems using this information when the optional parameter, length, was NOT entered. Inflow data specifies the locations of inflow control valves or devices. Tubing must be previously defined before the Inflow information may be entered. The format is: “INFLOW”, inflow type, inflow name, tubing for the inflow valve/device, Depth (MD), (optionally) device length or equipment ID.

(16)

16

An example with optional length is: INFLOW NICD ICD03 Tubing12 2453 12 An example with the optional equipment ID is: INFLOW NICD ICD03 Tubing12 2453 NICD‐4.50/4x4.0 To find information about this in the Petrel help file, go to the Search tab and key in “well tubing file format”. Filter to the Title “Tubing description file format” in the Petrel location (among the multiple documents returned by Petrel Help) and you will find more information. Casing data looks like this in a 3D Window (left) and a Well Section Window (right): Tubing data looks like this in a 3D Window (left) and a Well Section Window (right):

(17)

17

Packer data looks like this in a 3D Window (left) and a Well Section Window (right): Choke data looks like this in a 3D Window (left) and a Well Section Window (right):

(18)

18

Inflow (NICD) data looks like this in a 3D Window (left) and a Well Section Window (right):

(19)

19 Editing completion Data

Right‐clicking on the Global Completions folder and choosing Show completion errors prints in the Petrel Message log window any errors encountered in the completion data. These errors may be fixed either by correcting the ASCII files imported earlier and re‐importing the data or often you can fix them in the Completions manager.

(20)

20

To see the Completions Manager, right‐click on the Global completions folder and choose Completions manager. The Completions Manager shows, in spreadsheet form, all the completions inside the Petrel project.

(21)

21

All items in the Name column shown with a red background contain an error. To find the error, hold the cursor over the cell with the red background and the tooltip will explain the error. Often, fixing one will fix others. You may change the data in the Completions manager and, if changed correctly, the red background will disappear. Clicking on a line will show data in more detail in the right side of the window.

(22)

22

In the input file, the packer length wasn’t entered, using the default. This overlapped with the perforation. Putting a length on the packer and re‐importing fixed this problem and all the others in well A10. Checking the next red cell reveals that the well test has a bad date. The date of the test is in the year 1900 while the well was not drilled until 1990. Change the date of the bad year until the data is correct. Continue checking the file until all cells with red backgrounds have been fixed.

Petrel TIPS&TRICKS from SCM

1

K n o w l e d g e W o r t h S h a r i n g

Petrel TIPS&TRICKS from SCM

Importing Well Completion Data

Importing well data in Petrel can be a time‐consuming process. There are multiple types of data (headers,

logs, completion, etc.), each having multiple possible formats. Hopefully, your company database takes

care of much of this import for you. However, you will probably have to import data at one time or

another (new wells drilled, wells missing from database, data bought from another party, etc.). Most

experienced Petrel users are familiar with importing a lot of the data it takes to fully describe a well. Many

have never tried importing completion data. That is the purpose of this TIPS&TRICKS.

Usually, importing well data has up to five separate imports. They are:

1. Importing Headers

2. Importing Deviation Surveys

3. Importing Logs

4. Importing Tops

5. Importing Completion Information

The first four are fairly common and not a part of this document. Here, we will focus on importing

completion information only. This document was written using Petrel 2011.2, however earlier versions of

Petrel are very similar.

2

File Types

Completion data in Petrel consists of two files, events and tubing. We will discuss both in turn.

First, the events file. Contained in the events file are:

An example of an event file is:

Note that it always starts with a “UNITS” line.

3

Contained in the tubing file are:

 Casing

 Tubing

 Bullplugs

 Chokes

 Packers

 Inflows (AFCV – Annular FCV ‐ Flow Control Valve)

 Inflows (NICD – Nozzle ICD ‐ Inflow Control Device)

 Inflows (SICD – Spiral ICD)

 Inflows (LICD – Labyrinth ICD)

An example of a tubing file is:

4

Note that it also always starts with a “UNITS” line.

5

Event File

To import an event file, right‐click on the Global completions folder under the main Wells folder and

choose Import (on selection)…:

This brings up an Import file window:

a. Navigate to the correct folder

b. Change the Files of type: to Well event data (ASCII) (*.ev)

c. Select the File name as the file (or files) containing the event information.

d. Click Open

6

7

Event Data Format

8

9

10

11

Tubing Data

12

13

14

Tubing Data Format

15

16

17

18

19

Editing completion Data

20

21

22

b. Change the Files of type: to Well event data (ASCII) (.ev)*