Extract data from an Eclipse data Deck and Import into Petrel

It is possible to load a complete *.DATA file into Petrel. But changing any parameters
are limited to the use of the Keyword editor. To use the GUI capacity of Petrel to make
changes to the simulation model it might be necessary to break down the data files and
create Petrel items. The current items that can be backwards engineered and imported
into Petrel are still limited. This will change as more functionality is added to Petrel. As
more functionality is added some of the steps described here might be redundant. This
document describes which and how the different properties/data can be imported into
Petrel.

1. INITIALIZE AND IMPORT GRID ........................................................................... 2

2. IMPORT FLUID PROPERTIES ................................................................................ 3
3. EXTRACT AND IMPORT SATURATION FUNCTIONS (SCAL DATA) ........... 4
3.1 IMPORT KEYWORDS FROM FAMILY 1 ......................................................................... 4
3.2 IMPORT KEYWORDS FROM FAMILY 2 ......................................................................... 4
4. EXTRACT AND IMPORT WELL DEVIATION FILES (*.DEV) ......................... 5
4.1 EXTRACTING WELL DEVIATION WITH NWM (NEAR WELL BORE MODELING) ........... 5
4.2 EXTRACTING WELL DEVIATION WITH SCHEDULE (THE APPLICATION) ........................ 7
5. EXTRACT AND IMPORT OBSERVED DATA (*.VOL) ....................................... 9
6. EXTRACT AND IMPORT EVENTS....................................................................... 11

1
1. INITIALIZE AND IMPORT GRID
The grid intended for a simulation run and usually contained in the *.DATA file or an
include file can be extracted from the file and imported into Petrel. Once the grid and
properties are imported into Petrel the Petrel tools can be used to further modify the
model.
1. In the *.DATA file, comment out any GRIDFILE, NOGGF and FMTOUT
keywords if they are present.
2. For the purpose of importing a grid with initial properties, restart properties are
not needed, thus include a NOSIM keyword in the RUNSPEC section.
3. Run to initialize the *.DATA deck using the simulator of choice. A *.GRID (or
*.EGRID) and *.INIT have now been created.
4. In a new or existing Petrel project go to Project | Project Settings | Units tab,
change Project units to the same as the *.DATA file. (Grid and Initial properties
units will be converted on import, but some other data might not, thus it is usually
a good idea to convert the units prior to import.)
5. The next step is to import the grid and properties into Petrel. Right Mouse Button
(RMB) click in the Models tab | Import (on tree)…
6. In the pop-up dialog browse to the directory where the files are stored and select
any of the files from the simulation run and click OPEN.
7. In the next import dialog pop up window, select only the Grid Geometry and
Initial Properties. Remove the tick marks (if any) next to the other properties such
as Keyword data, Restart properties, Streamlines or Summary data. These
properties can of course be imported as well, but for the purpose of importing a
Grid with properties, these are not needed. Click OK.

8. The grid and initial properties are now imported into the project.

2
2. Import Fluid properties
The process of importing Fluid Properties and creating a fluid item into the Petrel Project
is fairly straightforward. Note that there are several keywords that are not supported on
import.

1. In a new Petrel Project or a project not containing any fluid items, click on the
Input tab. In the main menu; Insert | New Fluid Folder
2. RMB click on the Fluid folder in the Input tree. Select Import (on selection)…
3. In the import dialog, browse to find your *.DATA file or any file containing the
fluid keywords. Select and click OPEN.

4. If any of the keywords are not recognized, a Warning message and a log window
will pop up, giving a list of the fluid properties keywords that are not recognized.
5. The PVT properties can now be visualized, edited and plotted. Note; the imported
keywords cannot be altered through the Make Fluid Process in Petrel, only
through the settings panel and Spreadsheet.

3
3. Extract and import Saturation Functions (SCAL data)
There are two saturation keywords families that can be used with Eclipse. The first
family can be imported directly into Petrel. The second family of keywords is not
possible to import without some extra effort.

ƒ Family 1. SWOF, SGOF, SLGOF imports Ok

ƒ Family 2. SWFN, SGFN, SGWFN, SOF2, SOF3, SOF32D is not possible to
import. SGWFN is an exception and can be imported similar to Family 1.

3.1 Import Keywords from Family 1

Importing any of the keywords in the first family is straightforward and similar to how
fluid properties are imported. The steps below describe how to import saturation
functions from Family 1.

1. In a new Petrel Project or a project not containing any fluid items, click on the
input tab. In the main menu; Insert | New Saturation Folder.
2. RMB click on the Saturation Functions folder in the Input tree. Select Import (on
selection)…
2. In the import dialog, browse to find Your *.DATA file or any file containing the
saturation functions keywords. Select and click OPEN.
3. If any of the keywords are not recognized, a Warning message and a log window
will pop up, giving a list of the saturation function keywords that are not
recognized.
4. The saturation functions can now be visualized edited and plotted. Note the
imported keywords cannot be altered through the Make saturation Function
process in Petrel, only through the settings panel and Spreadsheet.

3.2 Import Keywords from Family 2

Importing keywords from the second saturation function family requires some additional
steps. Import the data into SCAL and then export the data as keyword of Family 1. Then
import into Petrel as described in step 3.1 above.
See Intouch content 4021941 for more information on Saturation Functions and how to do the
conversion using SCAL.

4
4. Extract and import well deviation files (*.dev)
The only well path data contained in *.DATA set is in the SCHEDULE section.
Combined with the corresponding grid the COMPDAT keyword contains information
about the well path. Extracting a well path is somewhat more tedious than the other steps,
but the processes are described step by step below. Below are two descriptions; both
should give the same results. The NWM approach is probably the easiest, unless you are
an experienced Schedule user.

4.1 Extracting well deviation with NWM (Near Well bore Modeling)
Follow the steps below to extract deviation files with NWM.

1. In the Petrel main menu go to Tools | Launch Eclipse Office… or Launch Eclipse
Office from the Geoquest Launcher | Eclipse Office.
2. In the main Eclipse Office menu, select File | New Project. In the Import file
dialog, changes files of type to *.DATA and select your *.DATA file to import.
Click Open to dismiss the dialog.
3. When the data has finished loading, Click on the NWM button on the lower left
side. Click Yes when prompted if You want to create a new NWM study. If the
model has not been run, give the NWM Case Study any name and click yes, or
run the case to create a grid and init file.
4. In the NWM module go to the Wells tab. RMB click on the Sim Wells folder |
Reconstruct. Click Yes when prompted to create wells without a deviation files.
The wells deviations have now been created.

5
5. Still on the Wells tab RMB click on the Wells icon | Well Path | Write Deviation
Survey. In the Write deviation survey to dialog, give the file a name and click
Save to save the file and dismiss the panel.
6. The next step is to import the newly created deviation files into Petrel. If the
Petrel Projects had no wells, click in the input tab. Then on the main menu go to
Insert | New Well Folder. If the project only contains a well folder in the input
tree, skip this step.
7. In the Input tab, RMB click on the Wells Folder | Import (on selection)…
8. In the Import File dialog, from the drop down menu Files of Type, select Multiple
well paths/deviations (ASCII) (*.*). Browse to select the file created in step 9.
Click Open to dismiss the dialog.
9. In the Import Multiple Well Paths dialog, toggle on the MD box. In the Name line
Prefix box type “WELLNAME”. In the Data line format box add an extra N, it
should be like “N N N N”. In the Undef value box type “–999”. Click Ok to
dismiss the panel.

10. If any warning messages pops up Click Yes to continue, or address the problem if
desired. The wells with their deviation files have now been imported into Petrel,
and can be seen in the Wells folder on the Input tree.

6
4.2 Extracting well deviation with Schedule (the application)
To extract well deviation files from Schedule follow the steps below. The process is
somewhat more tedious than using NWM.

1. In the Petrel main menu go to Tools | Launch Schedule… or Launch Schedule

from the Geoquest Launcher | Schedule. When prompted, select the working
directory where the files are stored.
2. When Schedule is launched, go to Setup | Units and select the proper unit system.
3. In the main Schedule menu, go to Import | Grid | Select Single Porosity or Dual
Porosity. (A dual porosity grid cannot be imported into Petrel at the moment,
though the well paths can still be extracted and imported into Petrel). In the
import dialog browse and select the grid file. The grid has now been imported into
schedule.
4. In the main Schedule menu go to Import | Schedule Section. In the import dialog
browse and select the relevant *.DATA or any file containing the Schedule
section. The Schedule section has now been imported.
5. The grid and COMPDAT information have now been read, and it is possible to
generate well deviation files. In the main Schedule menu go to Data | Extract Data
from Keywords. A pop up message is displayed; click Cancel.
6. In the Extract Data From keywords panel, select Extract Trajectory. In the Extract
Trajectory for All Wells dialog leave as default and click Build Trajectory. Click
Close to dismiss the Extract Trajectory for All Wells panel.

7. On the Extract Data From keywords panel click Build Deviations. A new dialog is
displayed, on the Build Deviation for All Wells panel click Build Deviation. Click
Close to dismiss the panel.

7
8. On the Extract Data From keywords panel click Close to dismiss the panel.
9. In the Schedule main menu select Export | Deviations. In the file name box; type
an appropriate name and click save. The deviation file has now been exported and
saved.
10. The next step is to import the newly created deviation files into Petrel. If the
Petrel Projects had no wells, click in the input tab. Then on the main menu go to
Insert | New Well Folder. If the project only contains a well folder in the input
tree, skip this step.
11. In the Input tab, RMB click on the Wells Folder | Import (on selection)…
12. In the Import File dialog, from the drop down menu Files of Type, select Multiple
well paths/deviations (ASCII) (*.*). Browse to select the file created in step 9.
Click Open to dismiss the dialog.
13. In the Import Multiple Well Paths dialog, toggle on the MD box. In the Name line
Prefix box type “WELLNAME”. In the Data line format box add an extra N, it
should be like “N N N N”. In the Undef value box type “–999”. Click Ok to
dismiss the panel.
14. If any warning messages pops up Click Yes to continue, or address the problem if
desired. The wells with their deviation files have now been imported into Petrel,
and can be seen in the Wells folder on the Input tree.

8
5. Extract and Import observed data (*.vol)

If the Model contains a production/injection history, this information can be extracted

from the WCONHIST and WCONINJH keywords using the Schedule application. It is
possible to load a *.vol file containing production, injection and pressure data into Petrel.
This *.vol file can be created by following the steps below.

1. In the Petrel main menu go to Tools | Launch Schedule… or Launch Schedule

from the Geoquest Launcher | Schedule. When prompted, select the working
directory where the *.DATA or schedule files are stored.
2. When Schedule is launched, go to Setup | Units and select the proper unit system.
3. In the main Schedule menu go to Import | Schedule Section. In the import dialog
browse and select the relevant *.DATA or any file containing the Schedule
section. The Schedule section has now been imported.
4. In the main Schedule menu go to Data | Extract Data from Keywords. A pop up
message is displayed; click Cancel.
5. In the Extract data from Keywords panel click on Extract Production Data.
6. In the Extract Production Data for All Wells dialog. Click Close to dismiss the
panel.

7. Click on Close in the Extract data from Keywords dialog. In the Schedule main
menu select Export | Production History | Monthly to export the historical data. .
In the file name box type an appropriate name and click save. The historical data;
*.vol file has now been exported and saved. (Before exporting it is possible to
visualize and QC the data before exporting. Schedule also offers more edit/export
facilities than described here. See the Schedule manual for further details)
8. The historical production data can now be imported into Petrel. If the Petrel
Projects had no wells, click in the input tab. Then on the main menu go to Insert |
New Well Folder. If the project contains a well folder in the input tree, skip this
step. Note that it is recommended that well deviation files should be imported
before importing historical data, though this is not required.

9
9. RMB click on the wells folder | Import (on selection)… In the Import File dialog
select file of Type Well Observed Data (ASCII) (*.vol). Browse and select your
file, click Open. The panel is dismissed and a new import dialog pops up.

10. On the Import Observed Data dialog simply Click Ok to import and dismiss the
panel. It is possible to do changes to the import settings, use the Petrel Manual for
more information.

10
6. Extract and import events
The schedule section of a data deck might include information about completion events.
This information can be extracted to produce an event file (*.ev). This event file can in
turn be imported into Petrel. On import into Petrel, the events will be converted to
Completion Items. The Schedule application is used to extract the events, please follow
the steps below.
If you used NWM to extract the well paths it is advised to also use NWM to extract the
events. This is to avoid any mismatch. You can export the events by right clicking on the
Wells folder and then selecting Well Events | Export Bore Events.

1. In the Petrel main menu go to Tools | Launch Schedule… or Launch Schedule

from the Geoquest Launcher | Schedule. When prompted, select the working
directory where the *.DATA or schedule files are stored.
2. When Schedule is launched, go to Setup | Units and select the proper unit system.
3. In the main Schedule menu, go to Import | Grid | Select Single Porosity or Dual
Porosity. (A dual porosity grid cannot be imported into Petrel at the moment,
though the well paths can still be extracted and imported into Petrel). In the
import dialog browse and select the grid file. The grid has now been imported into
schedule.
4. In the main Schedule menu go to Import | Schedule Section. In the import dialog
browse and select the relevant *.DATA or any file containing the Schedule
section. If prompted, type in the Start date of your simulation. (This is in the
RUNSPEC section of the data deck) The Schedule section has now been
imported.
5. In the main Schedule menu go to Data | Extract Data from Keywords. A pop up
message is displayed; click Cancel.
6. In the Extract Data From keywords panel, select Extract Trajectory. In the Extract
Trajectory for All Wells dialog leave as default and click Build Trajectory. Click
Close to dismiss the Extract Trajectory for All Wells panel.
7. In the Extract Data From keywords panel, select Extract Events. On the Extract
Events for All Wells panel leave settings as default and click Extract Events.
Click Close to dismiss the panel.

11
8. Close the Extract Data From keywords panel.
9. In the Schedule main menu select Export | Events to export the events. In the file
name box type an appropriate name and click save. An event file *.ev file has
now been exported and saved.
10. The events can now be imported into Petrel. Well deviation should be loaded
prior to importing events. RMB click on the wells folder | Import (on selection)…
In the Import File dialog select file of Type: Well Event Data (Ascii) (*.ev).
Browse and select your file, click Open. The panel is dismissed and a new import
dialog pops up.
11. On the Import Event Data dialog leave the Wells tab as is. On the Settings tab,
toggle on Add casing if desired (this is recommended if you do not have a tubing
*.tub file and intend to import events). Specify the date format on the event file.
(The date format might be unnecessary depending on your regional settings). Any
other options in the Import dialog are described in the Petrel manual.

12