Tutorial Ecl

ECLIPSE Office 2007.1 User Guide TutorialsOverview

25

Chapter 4Tutorials

OverviewThe tutorials provided in this chapter are designed to help you perform several typical tasks using ECLIPSE Office. The first tutorial in particular aims to give you an overview of the main areas of ECLIPSE Office, while the remaining tutorials place a greater emphasis on completing common engineering tasks.

Available tutorials1 "Tutorial 1: Standard usage" on page 29 consists of importing an existing ECLIPSE

datadeck with the following features switched on:

• API tracking (API)

• Tracer Tracking with numerical diffusion option (TRACERS)

• Endpoint scaling (ENDSCALE)

• Mobile fluid critical saturation endpoint correction (EQLOPTS)

• Threshold pressure (EQLOPTS)

This example imports an existing ECLIPSE model into ECLIPSE Office and provides information on the internal file structure used by the program, data editing, running of a simulation and viewing of results and reports. The tutorial stages are as follows:

• "Case management" on page 30

• "Data manager" on page 31.

• "Run manager" on page 38.

• "Result viewer" on page 40.

• "Result viewer" on page 40.

• "Exit ECLIPSE Office" on page 44.

26 Tutorials ECLIPSE Office 2007.1 User GuideOverview

2 "Tutorial 2: Building a model" on page 45 creates a new simulation model, using external files created by GSS programs. The input files are standard ECLIPSE keyword files and could be generated by any third party software. In this example you build a simple ECLIPSE data model, importing the data per section using export files created by GRID, PVTi, SCAL and Schedule programs. The file extensions added by these programs to the export files are as follows:

• GRID - Grid Section, containing geological model definition.grdecl or .gec

• PVTi - PVT Section, containing Reservoir Fluid Properties.pvo

• SCAL - SCAL Section, containing Special Core Analysis data.rcp

• VFPi - Schedule Section, containing Vertical Flow Performance curve data.vfp

• Schedule - Schedule Section, containing the production schedule information.sch

Files containing data associated with ECLIPSE keywords can have any file extension, as long as it is ASCII and in the ECLIPSE-specified format.The tutorial stages are as follows:

• "Model definition: data input" on page 46

• "PVT section: fluid definitions" on page 51

• "SCAL section: saturation definitions" on page 53

• "Initialization section" on page 54

• "Schedule section: production schedule" on page 56

• "Summary section" on page 56

• "Run manager" on page 57

3 In "Tutorial 3: Constructing a PEBI simulation grid" on page 60 the Unstructured Gridder is used to build the geological model from mesh/contour data, generate a PEBI (Perpendicular Bisector) grid on it and generate the geological information per keyword, as required by the ECLIPSE Simulators.The tutorial stages are as follows:

• "Problem description" on page 60

• "Getting started" on page 60

• "Importing reservoir boundary and layer data" on page 62

• "Importing/manipulating well data" on page 68

• "Importing/manipulating fault data" on page 70

• "Importing porosity and permeability data" on page 74

• "Viewing input data" on page 74

• "Generating a grid and properties" on page 75

• "Saving and exiting the Unstructured Gridder" on page 79

• "Running an ECLIPSE simulation" on page 79

ECLIPSE Office 2007.1 User Guide TutorialsOverview

27

4 In "Tutorial 4: History matching using ECLIPSE Office and SimOpt" on page 86 a history match is performed on the model created in "Tutorial 2: Building a model" on page 45. The tutorial includes a sensitivity study and a matching operation with the actual production data as observed in the field.

• "Setting up an ECLIPSE Office project from an existing simulation model" on page 86

• "Exporting an ECLIPSE Office project for use in SimOpt" on page 88

• "Setting up a history matching project in SimOpt" on page 89

• "Analyzing the current history match and designing a regression problem" on page 92

• "Exporting a SimOpt simulation model for import into ECLIPSE Office" on page 94

• "Multiple prediction runs in ECLIPSE Office" on page 94

5 In "Tutorial 5: Streamline Simulation" on page 97 a FrontSim data deck is imported into ECLIPSE Office. The tutorial explores using ECLIPSE Office as a pre/post processor and data manager for the FrontSim streamline simulator.The tutorial stages are as follows:

• "Streamline Simulation" on page 97

• "Importing existing FrontSim data" on page 98

• "Data Management" on page 98

• "Result Viewing" on page 102

6 In "Tutorial 6: Adding local grid refinement" on page 109 the project from Tutorial 1 is used to view and interpret the simulation results, add a Local Grid Refinement and observe detailed simulation output.The stages covered in this tutorial are:

• "Open existing project" on page 109

• "Insert cartesian LGR" on page 110

• "Update the Schedule Section with well specifications in the LGR" on page 112

• "Select summary vector output with regard to the LGR" on page 115

• "Run the simulation" on page 117

• "View the simulation output from the local grid" on page 118

7 In "Tutorial 7: Remote job submission" on page 125 reservoir simulations are submitted on remote machines using the various run management tools in ECLIPSE Office. For example, the ECLIPSE Office project is created on a PC, the run is submitted on a UNIX box, and then the results can be viewed on the PC.The tutorial stages are as follows:

• "Submitting runs using PVM" on page 126

• "Submitting runs using Non-PVM Remote" on page 130

• "Submitting runs with the external job option" on page 138

• "Submitting jobs to LSF from a UNIX machine" on page 143

28 Tutorials ECLIPSE Office 2007.1 User GuideOverview

8 "Tutorial 8: Using property correlations" on page 145 demonstrates the procedure for creating PVT tables to simulate fluid behavior of Live Oil in the Black Oil Simulator.The tutorial stages are as follows:

• "Importing an existing data set" on page 145

• "Generating fluid and rock properties by correlation" on page 146

• "Viewing PVT keywords graphically" on page 147

• "Saving the keywords" on page 149

• "Running the simulation" on page 149

9 "Tutorial 9: Using PEEP" on page 151 describes how to use ECLIPSE Office to prepare ECLIPSE simulator output for the PEEP economics tool. It covers generating PEEP script files and how to use the ECLIPSE-to-PEEP link.The tutorial stages are as follows:

• "Generating PEEP script files" on page 151.

• "Instructions for using the ECLIPSE to PEEP link" on page 158.

• "Importing ECLIPSE data" on page 160.

• "Running the Case" on page 161.

• "Calculating incremental value" on page 162.

Finally, "Getting to know ECLIPSE Office" on page 525 is an appendix consisting of several short demonstrations of the following operations and topics:

• "Data preparation" on page 526

• "Printing and plotting" on page 526

• "Changing screen display colors and fonts" on page 531

• "Viewing an entire file" on page 533

• "Adding and removing comments on a project" on page 533

• "Comparison between cases" on page 534

• "Units" on page 535

• "Simple cut and paste to external software" on page 535.

ECLIPSE Office 2007.1 User Guide TutorialsTutorial 1: Standard usage

29

Tutorial 1: Standard usage

IntroductionThis tutorial details the following steps: importing an existing data set, editing the data, saving the project, running and monitoring simulation, viewing results vectors, and creating reports.

This tutorial takes about thirty-five minutes to complete.

StagesTutorial stages are as follows:

1 "Case management" on page 30

2 "Data manager" on page 31

a "Case definition" on page 32

b "Grid section" on page 33

c "PVT section" on page 35

d "SCAL section" on page 36

e "Initialization section" on page 36

f "Schedule section" on page 37

g "Summary section" on page 38

3 "Run manager" on page 38

4 "Report generator" on page 39

5 "Result viewer" on page 40

a "View summary data" on page 41

b "2D Viewer: initial and solution data" on page 42

c "3D Viewer: initial and solution data" on page 43

Problem descriptionThis project simulates live oil through a heterogeneous reservoir divided into 2400 cells. The geological structure contains 2 sealing faults, dividing the reservoir up into 3 distinct fluid-in-place regions, as well as an impermeable horizon in layer 6. The following ECLIPSE features are used in this example:

• Scaling of saturation end points of the relative permeability (End-point scaling) versus depth.

• API tracking of the different PVT oils

• Tracer tracking of initial gas-cap gas and injected water

• Group control of wells

• Reperforation of wells by completion interval

30 Tutorials ECLIPSE Office 2007.1 User GuideTutorial 1: Standard usage

• Use of the drilling queue

Data preparation1 Create a working directory in a convenient place.

2 Copy the dataset BRILLIG.DATA from the installed tutorials directory, which would normally be $ECLARCH/$ECLVER/office/tutorials/example1.

Hint The location of this file depends on each individual installation of the suite of software, and can be found by typing the UNIX command env ECLPATH.

Case management1 To begin, start ECLIPSE Office from the ECLIPSE launcher (on UNIX: @office).

Create a new project1 Select File | New Project from the top menubar.

2 Select the data directory you wish to work in.

3 Call the project Tut1

Import an existing data set1 Select ECLIPSE Office | Case | Import from the top menubar.

2 Select BRILLIG.DATA.

3 In the main ECLIPSE Office panel, choose View | Display Model in DM

4 In the main ECLIPSE Office panel, choose View | Display Model in Grid Section

Note Display of the model in the Data Manager (DM) and Grid Section is OFF by default, as calculation of the display can take some time. The display can be defaulted to ON by editing the configuration file (CONFIG.ECL). See "Display options" on page 493.

ECLIPSE Office loads the ECLIPSE data set into memory. The data is grouped into 9 sections, corresponding to the sections of a simulator input file. Related data is stored in an INCLUDE file (except for the GRID section, which is subdivided into a further 4 sections). Model definition options are stored in the project file called Tut1_E100.OFF.

• Geometry keywords for the global grid and LGRs is stored in the Tut1_GGO.INC file.

• GRID section property keywords are stored in the Tut1_GPRO.INC file.

• GRID section operational and parallel keywords are stored in the Tut1_GOPP.INC file.

• Other GRID keywords not mentioned above are stored in the Tut1_GOTH.INC file.

• Grid block property modifications are stored in the Tut1_EDIT.INC file.

• PVT data is stored in the Tut1_PVT.INC file.

• Saturation properties are stored in the Tut1_SCAL.INC file.


31

• Initial solution data is stored in the Tut1_INIT.INC file.

• Regions data is stored in the Tut1_REG.INC file

• Production schedule data is stored in the Tut1_SCH.INC file.

• Summary data is stored in the Tut1_SUM.INC file.

In addition a GRID header file called Tut1_GHDR.INC is written. This stores information required by different sections of ECLIPSE Office, and contains no keywords. Therefore it is not used in any of the simulation runs.

Save the project1 Select File | Save Project from the top menubar to save the main model definition to disk.

Note The main project .OFF file contains the model definition and pointers to all data files containing the data per section. These pointers contain absolute paths to data files, and the Save Project As option should therefore be used with great care so as not to overwrite data files. If you wish to copy the project to another location, use the Backup and Restore options (see "Backup Project" on page 183) which update the absolute paths.

Data manager1 Select Data to activate the Data Manager.

2 An outline of the grid is shown. Take note of the model boundaries, the faults and the wells.

Note For PEBI models imported into ECLIPSE Office, an outline of the grid is not available.


Figure 4.1 ECLIPSE Office Data Manager module

Case definition1 Select Data Manager: Case Definition | General to view main simulation properties.

2 Change the title of the simulation to: Import case.

The gridsize in this model is 20x15x8, which means a total of 2400 gridcells are used in the simulation. Memory recommended for a BLACKOIL simulation is 2 KB per cell, which in this case is roughly 5 MB.

3 Change the date to: 1 Jan 1990.

4 Ensure that the following options had been selected:

a Treatment: Black Oil

b Units: Field

c Run Type: Normal

Note If the option Black Oil is switched on, the ECLIPSE 100 program is run.

5 Select the Reservoir file tab at the top of the window.


33

The model has 1 reservoir with an analytical aquifer, which is simulated using a cartesian grid defined by corner point geometry. The main properties of an analytical aquifer can be viewed in the Initialization Section under the aquifer group. Numerical aquifers are defined in the GRID Section. (You have to close the Case Definition Section before you can open the Initialization Section or GRID Section. See "Initialization section" on page 36.)

6 Select the PVT file tab at the top of the screen.

The reservoir fluid contains three phases: gas, oil and water. The oil is defined as a live oil with dissolved gas.

API tracking is switched on to track the different oil gravities, and numerical diffusivity control is done by an algorithm.

Hint Refer to keywords API and TRACERS in the "ECLIPSE Reference Manual".

7 Select the SCAL/INIT/Sched file tab at the top of the screen. Observe that the following options have been selected:

a Saturation endpoint scaling of relative permeabilities

b Threshold Pressure

c Initial Saturation End Point Correction.

Hint Refer to keywords ENDSCALE and EQLOPTS, in the RUNSPEC section of the "ECLIPSE Reference Manual".

8 Select Misc from the menu-tabs.

9 Change Stack Size of Previous search directions (NSTACK) to 50.

10 Click on the OK button at the bottom of window to save the changed RUNSPEC parameters and exit the Case Definition Section.

Grid section1 Select Data Manager: Grid to activate the geological data definition section.

2 Select GRID Section: Subsection | GRID Keywords to access all GRID keywords inserted.

3 Select from the listings Keyword Type | Geometry and keyword COORD to see the cartesian coordinates of the cornerpoints of the grid listed.

Hint You can toggle between keywords and descriptions using View | Keywords and View | Descriptions.

4 Select Keyword Type | Properties and keyword PORO to see the porosity values per grid-block.

5 Exit the Grid Keyword Section (File | Close).


Calculating the average porosity in the reservoir

Hint More information on the Calculator and its use is available in "The Calculator" on page 539 of this manual.

1 Select the Grid Section: Utility | Calculator option to activate the calculator.

2 Select Calculator: Show | Vectors to observe that the PORO vector contains 2400 elements.

3 Select Calculator: Show | Symbol Functions to obtain the list of functions available for use in this section of the program.

4 Write the following two lines of code on the Program panel:

Hint Alternatively File | Open can be selected to open the file avgporo.cal.

5 Run the program by selecting Calculator: Run Program option.The result is then displayed in a separate output window.

Note that the average porosity in the reservoir is in the region of 0.217.

6 Close the Calculator with File | Close and return to the Grid Section: GRID Keywords Section panel.

7 Select View | Grid Order | XZ-plane to display the cross-sectional values. Note that layer 6 has zero porosity and is impermeable.

8 Select Operational keywords from Keyword Type list.

9 Confirm that both the GRIDFILE and INIT keywords are in this keyword list. The argument for the GRIDFILE keyword should be set to “Extensible Grid File (EGRID)”.

10 Close the GRID Keyword Section panel using File | Close.

11 Save the changes to the current Grid Section INCLUDE files by selecting File | Save from the Grid Section main window.

Note The Save panel allows you to control output to the GRID include files as a whole, along with the EDIT and REGIONS files. No keywords exist in the EDIT section so this option has been disabled. The Advanced Save panel allows output to the individual GRID include files to be controlled.

Note The project is saved by default. This can be altered from the Advanced Save panel.

12 Exit the Grid Section by selecting File | Close on the Grid Section window.

av = vaverage(PORO,0,2399)

print “Average Porosity in the Reservoir:”, av


35

PVT section1 Select Data Manager: PVT to enter the fluid Pressure, Volume, Temperature

Definition Section.

2 Select Section | Keywords to display the PVT data per region and keyword.

3 Select View | Plot to observe the fluid property data graphically. (See Figure 4.2)Figure 4.2 Dry gas PVT properties plot

4 Select File | Close to close the Plot window.

5 Select PVT Tables: PVT 2 and Keyword: GRAVITY.

6 Change the oil API gravity to 30.

7 Click on the Apply button at the bottom of the window to save changes.

8 Select File | Close to exit the Keywords Editor.

9 Select PVT | File | Save. Two files are saved, the Tut1_pvt.INC file, containing all PVT properties, and the Tut1_reg.INC file, saving the PVT Section regions data, such as PVTNUM.

Note The regions file is shared amongst all the Data Manager sections; you are prompted to save it each time a section is saved.

10 Select File | Close to exit the PVT Section.


SCAL section1 Select Data Manager: SCAL to enter the saturation functions section.

A set of saturation tables is applicable to a specific region. The SATNUM keyword provides the link.

2 Select Section | Keywords to display the SCAL data per region and keyword.

3 Keep the focus on keyword SWFN. Select View | Plot to observe the saturation function data graphically. (See Figure 4.3)

Figure 4.3 Plot of water saturation functions

4 Select File | Close to close the graph window.

5 Close the SCAL Keywords Section.

6 Close the SCAL section.

Initialization section1 Select Data Manager: Initialization to see the initial solution and pressure data for the

reservoir.

2 Select EquilReg2 (Region) and APIVD (Keyword) to see the API versus Depth for the oil in Region 2.


37

Note If the Generic Keywords option is ON, the keyword is not displayed in different regions; only one region is displayed.

3 Change the Oil API at both depths to 30.

4 Click on the Apply button at the bottom of the window to save the changes.

5 Select Keyword Types | Aquifer from the top menubar to display the aquifer connections and definition.

6 Select File | Save then OK to save the changed API data. You are also prompted to save the Regions data. Select Cancel as no data has changed.

7 Select File | Close to exit the section.

Regions section1 Select Data Manager: Regions to enter the Regions Section.

2 Select Edit | Explore Keywords to open the Explore Keywords panel.

The panel initially appears containing a list of all valid Regions keywords for this data set.

Hint The keywords that are being used by the data set appear with a * next to them in the Explore Keywords panel. Keyword help can also be called up from this panel

3 Select Region Section: File | Close to return to the Data Manager main window.

Schedule section1 Select Data Manager: Schedule to enter the Schedule Section.

2 Select Schedule Section: Event | View | Group.

3 Click on ONE in the list of groups and use the >> arrow (or double-click on the selection) to add it to the selected list.

4 Click on OK when all the groups needed have been selected.

5 Click on the different timesteps to observe schedules for the selected group at each time step.

Hint A (*) by a time indicates that events exist for that time step.

6 Click on each event keyword to see details of the event.

7 Select Event | View | All to list all events again.

Observe that the reservoir oil is produced from 10 wells. Water is injected around the edges of the reservoir, and gas in the center, using well GI. The names of the water injection wells all start with the letter I to make recognition easier.

8 Select Schedule Section: File | Close to return to the Data Manager main window.


Summary sectionSummary keywords are used to indicate to the simulation program which vector output is required. Output are written to the .Snnn files.

1 Select Data Manager: Summary

2 Click on RUNSUM from the General tab.

3 Click on Add to list to add this SUMMARY keyword to the case.

Hint The selected list of keywords can be displayed by clicking on the “Selected” button in the toolbar.

4 Select Summary Section: Field from the tab menu.

5 Select Phases: OIL, Types: Production Total to see the relevant list of SUMMARY keywords.

6 Select FOPT from the list, which gives the Field Oil Production Total, and click on the Add to List button at the bottom of the screen.

7 Select Others in the Phases column, Pressure in the Types column and FPR from the Keywords list to add this SUMMARY vector to the list for output.

8 Click on Add to list.

9 Click on Summary Section: File | Save to save the newly selected keywords to the Tut1_sum.INC file.

10 Select Summary Section: File | Close to exit this section.

Exit data manager1 Select Data Manager: File | Close to exit Data Manager.

Run manager1 Select Run to activate the simulation Run Manager.

2 Click on the “Go” button to start the ECLIPSE Blackoil Simulation program.

Hint If the program does not find the current version of ECLIPSE, it asks you to select a version from the Run Environment panel (Run Manager: Options | Run Environment...). Select the latest or preferred version of the software and click on OK.

Progress on the simulation is printed to the Log window. SUMMARY files are written at each timestep, if specified, containing vector data used for monitoring the simulation process.

Run monitoringPVM is a software package that permits computers connected by a network to be used as a single large computer. More information is available in Chapter 5 of this manual, "Reference section" on page 181.


39

1 Run Manager: Monitor | Summary Vectors displays graphical presentations of the selected summary vectors, and updates the graph at every report step. This option is greyed until the first SUMMARY file is written

2 Summary Vectors: LinePlot | Field | Production Rate displays the Oil, Water and Gas production and updates each vector as the simulation progresses.

3 Select Summary Vectors: File | Close once the simulation is finished.

4 Close the Run Manager with File | Close.

Report generator1 Select Report to enter the Report Generator.

Errors and warningsView errors and warnings by reading the print file first.

2 Select Report Generator: File | Open Current Case | PRT.

3 Select Errors... from the Report drop-down.

4 Check the Errors option, and click on Generate Report. If the Errors option is grayed, no errors occurred.

Note No errors should appear at this stage. However, if errors exist, the simulator gives information to correct it. This normally involves another session in the Data Manager.

Available reportsSelect PRT Reports from the Report drop-down to see a list of available reports.

1 Select Report 0 and keyword BALANCE.

2 Click on the Add to List button to see it in the Selection List box.

3 Click on Generate Report to report on the initial fluids in place.

4 Select Output to display the report (Figure 4.4).


Figure 4.4 Report generator module

Note The contents of the report window may be copied to any text editor by using the usual window management facilities (for example: select the text, Ctrl c to copy and Ctrl v to Paste).

To compare the initial fluid in place with that at the end of the study:

5 Select Input to enter details for the next report.

6 Select Report 10 and BALANCE.

7 Click on the Add to List button.

8 Click on Generate Report.

9 Return to the Output window.

10 Toggle between the two reports generated by selecting them in the list at the left hand side of the screen. Compare the numbers displayed to get the oil recovery percentage.

Note A report may be displayed in a separate text window by selecting New Window.

11 Select File | Close to exit the Report Generator.

Result viewer1 Select Result from the main ECLIPSE Office window to activate the Result Viewer.

2 Select File | Open Current Case | SUMMARY to open the unformatted reports header file for the current case.

3 Note the Read All Summary Vectors and Read All Reports options at the top of the Extract/Load Summary Vectors panel have been selected

4 Click on the Load button at the bottom of the screen to load.


41

View summary data1 Select LinePlot | Field | Production Rate.

Oil, gas and water production data appear on the graph.

Configure graphs

1 To create the next graph to contain the FWCT and FGOR, select LinePlot | User .

2 From the list of Y-axis Vectors, click on the FWCT.

Hint Using the field at the top of the list containing “*” you can enter a filter for the list below, to reduce the choice. Enter F* to display all vectors beginning with F, or F??? for all vectors beginning with F and 4 characters long.

3 Click on Add to List to add it to the list of Vectors to Plot.

4 Do the same for FGOR versus TIME.

5 Click on the OK button to create the graph and remove the User Templates panel.

6 Double-click on the Field Production Rate plot to bring it into the main window.

7 Double-click on the graph title and add Tut1 to it.

Note The graph title can also be changed by selecting Options | Modify Graph Title.

8 Click on OK to apply.

9 Double-click in the main graph legend on FOPR to change the configuration of the line graph.

The Data Style Property Editing panel appears.

10 Click on the dark green box to change the oil vector line to green.


12 Repeat for FGPR and change the color to red.

13 Repeat for FWPR and change the color to blue, if necessary.

14 Double-click on the other plot, so far untitled, to make it active.

15 Change the title to Field Water Cut and Gas Oil Ratio.

16 Double-click on the Field Production Rate: Tut1 graph to make it active.The Result Viewer main graph should be similar to Figure 4.5.


Figure 4.5 Result Viewer - Summary Vectors plot

Printing graphs17 Create a hardcopy of the graphs by selecting File | Print | Current Picture.

• On UNIX: Supply a filename for the print file.

2D Viewer: initial and solution data1 Select File | Open Current Case | GRID.

Note that the INIT File option to load the initial reservoir conditions and the All Reports option to load the solution data of each report step are selected

2 Click on the Load button at the bottom of the panel.

Both 3D and 2D viewing options become available once the data is loaded successfully.

Note The 3D option only becomes available if a FloViz license exists.

3 Select View | 2D to view the solution and grid data.

a Alternatively click on the “2D Viewer” button .

The initial oil saturation is displayed by default.

Displaying the oil saturation 1 Select Tools | Timestep to display the Time Selector panel.

2 Select Report (10) 30-Dec-1999 from the displayed list.

3 Click on the OK button to apply and close the panel.


43

3D Viewer: initial and solution data

1 Select View | 3D or click on the 3D Viewer button . A browser page will open up titled “How to interact with the 3D viewer“. This discusses the changes in 3D viewer due to the switch-over to OpenInventor for the 2004A release.

Oil Saturation at the end of the simulation time period is displayed.

Displaying the initial water saturation1 Select 3D Viewer: Scene | Grid | Property.

2 Select SWAT from the Recurrent Property list.

3 Click on the First Timestep button , the left-most animation button in the top right corner of the display panel.

4 The image can be rotated as needed, as mentioned in the browser page mentioned above.

Hint 3D | Help option provides information on the mouse buttons used on each platform for image rotation.

5 Reposition the image in the center of the display by selecting the Auto-normalize button

.

6 Stretch the image vertically by clicking on the vertical stretch z+ button several times.

7 Switch the cell outlines off with the option 3D Viewer: View | Object Appearance...

8 Click on the dropdown arrow of the first row, Render Mode column, which currently shows Surfaces, and select Cell outlines.

a You can also click on the Display Simulation Grid Cell Outlines button to turn this feature on or off.

Switching on the tick marks1 Select 3D Viewer: Scene | Axes to display the Axes panel or click on the button in

the right-hand vertical toolbar.

a The button in the horizontal toolbar turns the axes on or off.

2 Check the Tick Marks box as well as the Axes box.

3 Click on Apply.

4 Click on Close.


Figure 4.6 3D Viewer with axes and tick marks

The Postscript option can be used to generate a file for inclusion in reports written in desktop programs, such as Microsoft Word. Use the command @gs to run the Ghostscript conversion program to convert to cgm or bmp format. This can then be imported into Microsoft Word as a picture. See a full description in "Getting to know ECLIPSE Office" on page 525.

5 3D Viewer: File | Save Image | Postscript... displays the Postscript panel on which a filename can be selected.

6 Select Write Postscript File to generate. If resizing is recommended, accept and select the Write Postscript File option again.

Caution Do not interrupt the writing process.

7 Select Postscript: Close once the operation has been completed to return to the 3D Viewer.

8 Select 3D Viewer: File | Close to return to the Result Viewer main panel.

9 Select Result Viewer: File | Close to exit to the main ECLIPSE Office window.

Exit ECLIPSE Office1 Click on File | Exit.

ECLIPSE Office 2007.1 User Guide TutorialsTutorial 2: Building a model

45

Tutorial 2: Building a model

IntroductionThis tutorial builds a Black Oil model from scratch using output generated by other SIS Simulation Software applications. It focuses on manipulation in each section in the Data Manager, but includes the submission of the simulation run, and viewing errors or warnings.

This tutorial takes about thirty-five minutes to complete.

Stages• "Model definition: data input" on page 46

• "PVT section: fluid definitions" on page 51

• "SCAL section: saturation definitions" on page 53

• "Initialization section" on page 54

• "Schedule section: production schedule" on page 56

• "Summary section" on page 56

• "Run manager" on page 57

• "Report generator" on page 58

Problem descriptionThe example simulates the production life of an oil reservoir, 5000m by 5000m and 60m thick. The reservoir fluid consists of live oil and gas, with an aquifer of uncertain volume. The second layer has numerous shale components, introducing a lower permeability in this layer. The reservoir is subdivided into a 10x10x4 grid, and history matching concentrates on determining the aquifer contribution to total energy.


2 Copy all datafiles from the Tutorial 2 directory, normally residing on /ecl/2007.1/office/tutorials/example2, to the current working directory.

Open new project1 To begin, start ECLIPSE Office.

2 Select File | New Project.

3 Call the project Build1.

46 Tutorials ECLIPSE Office 2007.1 User GuideTutorial 2: Building a model

4 Select File | Save Project to save the project file to disk.



Model definition: data input1 Click on Data to activate the Data Manager Module (DMM).

2 Select Case Definition.

3 Activate the following options:

4 Select the Reservoir tab.

5 Activate Aquifers and select Analytical

6 Grid Option: Cartesian

7 Geometry Option: CornerPoint

8 Select the PVT tab

9 Activate Water, Oil, Gas, Dissolved Gas.

Hint The Dissolved Gas option is only active if the OIL option has been selected.

Hint Input and output file formats are selected on the Run Manager panel, as well as the NOSIM option to initialize the model and perform data checking.

10 Select the Misc tab

11 Change the Stack size of previous search directions (NSTACK) to 50

12 Accept the defaults for the remaining input parameters.

13 Click on OK to store the changes and exit.

14 Select File | Save Project from the main project panel to save the Case Definition Section.

Geological definition of model and grid building1 Select Data Manager: Grid to open the grid definition section, where the geological

properties are defined.

2 Select Grid Section: File | Import File | New... and import the GRID1.GEC file by selecting the file from the browser.

Simulator Black Oil

Title Tutorial 2: Workflow

Simulation Start Date 1 Jan 1990

Model dimension (x,y,z) 10, 10, 4

Units Metric

Run Type Normal


47

Note If the file contains the SPECGRID keyword then it is not necessary to specify the dimensions in the Case Definition Section, as ECLIPSE Office inserts the grid size it reads from the keyword. The SPECGRID keyword must appear before any array-based keywords.

3 Select Grid Section: File | Save As...

4 Check that the Directory for all the GRID Section Files: entry matches the selection you wish.

5 Accept the default root name, which should be Build1.

6 Click on the Advanced... button. The GRID header, geometry and parallel/operational INCLUDE files are saved. The Properties and Other INCLUDE files are not saved yet as they contain no keywords.

7 Click on Save.

8 Select Grid Section: Subsection | Grid Keywords.

9 Check that the data for the keywords COORD and ZCORN have been inserted correctly.

Hint Select Grid Keywords: View | Keywords to show the keyword names.

10 Select Properties from the Keyword Type list to insert porosity and permeability.

11 Select Grid Keyword Section: Edit | Insert Keyword, and from the list of keywords, select PORO.

12 Select Grid Keyword Section: Edit | Box to display the Array Box Selection panel.

Setting the porosity in the horizontal plane1 Change the K-value range to be from 1 to 1, and enter .35 into the Data Value box. Make

sure that the Operation is set to Equals.

2 Click on Apply.

3 Repeat this action for the other 3 planes, with porosity values of .3, .25 and .2 for each of K = 2, 3 and 4, respectively.

4 Click on Array Box Selection: Close.

5 Select Grid Keyword Section: View | Grid Order | XZ-plane to see the following screen (Figure 4.7).


Figure 4.7 DMM - GRID Keyword section

6 Select View Edit History... in the PORO panel to display a table containing the edits which have been applied to the current keyword.

7 Select any row in the Edit History panel to display comments for a particular edit.

Note Comments which have been automatically added by Office are preceded with a “*”. You can use this panel to edit the comments.

8 Select Cancel to close the Edit History panel.

9 To insert the permeability data, Grid Keywords Section: Edit | Insert Keyword, and from the list of keywords, select PERMX. The table for data input is displayed.

10 Select Grid Keyword Section: Edit | Box to display the Array Box Selection panel.

Setting permeability per plane1 Change the K-value range to be from 1 to 1.

2 Enter 1 into the Data Value box, and select D for Darcy from the Unit dropdown-list.

3 Make sure that the Operation is set to Equals.

4 Click on Apply.

Note The data is converted to the correct unit as needed for the simulator, based on the selection of model units in the Case Definition Section - in this case, METRIC - when the data is saved to disk.


49

5 Repeat this action for the remaining 3 planes, with permeability values of .005 D, .3 D and .1 D, for each of K = 2, 3 and 4, respectively. Data should appear as in Figure 4.8.

Figure 4.8 Data Manager module Grid Keyword Section

6 Use option Grid Keyword Section: Edit | Insert Keyword to display the Keyword Selection box. Select PERMY and PERMZ from the list.

7 Click on Properties in the Keyword Types list if it is not active already. This lists the current property keywords in the model.

8 Select PERMY from the list of keywords.

9 Select Edit | Box from the menubar.

Setting PERMY to equal PERMX1 Select COPY on the Operation drop-down list.

2 Select PERMX from the Copy from drop-down list.

3 Leave the I,J,K ranges at their default values.

4 Click on Apply to perform the operation.

Setting PERMZ equal to .1*PERMX:1 Click on the PERMZ keyword in the Keyword list, to activate it.

2 Repeat the Box | COPY operation to copy PERMX into PERMZ.

3 For the next action, select Multiply as the Operation, Multiplier=.1.

4 Close the Array Box Selection edit panel.

The results should be the same as in Figure 4.9.


Figure 4.9 Grid Section keywords

5 Select View Edit History... to display a panel containing all edits which have been applied to property keywords.

Note Edit | Delete Edit History consolidates all the edits into a single keyword. This is identical to the pre-2002A behavior.

A GRID file is required by all sections in order to display region and property data during the model building phase of the project. It can be recognized by the file name extension .GRID or .EGRID for an unformatted or binary file, and .FGRID or .FEGRID for an ASCII or formatted file. The output format is selected on the main Run Manager panel.

6 To ensure that a GRID file is written as part of the output, select Operational Keywords from the Keyword Types list.

7 Confirm that the GRIDFILE keyword is in this list.

Note ECLIPSE Office writes GRIDFILE 2 to the _geom.inc file in all cases to ensure that all data required in the Result Viewer is available.

8 Select GRID Keyword Section: Edit | Insert Keyword.

9 From the same list, insert INIT to write the file containing initial properties of the grid. File extension .INIT or .FINIT.

10 Click on Apply.

11 Click on File | Close to exit the Grid Keywords panel.

12 Select Grid Section: File | Save... and save the geometrical data.


51

13 Select Grid Section: GridView | From Keywords to generate a gridfile for 2D and 3D viewing.

14 Select YES to create the GRIDFILE.

15 Select Grid Section: GridView | 3D to see the 3D image of the simulation grid.

16 Close the 3D Viewer with File | Close.

17 Select Grid Section: File | Close to exit.

PVT section: fluid definitions1 Select Data Manager: PVT to insert the PVT data.

2 Select File | Import | New... and insert the data from the pvt2.pvo file.

3 Select PVT Section: File | Save As, and use the default filename to save the data imported from the file to the Build1_pvt.inc file.

4 Update the project file at the same time, by selecting the Update Current Case and Save Project File options on the File Save As panel.

Hint Update Current Case updates the main ECLIPSE Office Case Manager panel with the link to the PVT data, and commits the data internally. Save Project File saves the project data, with the link, to the main Build1.OFF file on disk.

5 Select PVT Section: Section | Keywords from the menubar.

6 Select from the menubar PVT Keywords: Keyword Types | PVT Tables. This may be active already.

7 Observe the data inserted from the imports as in Figure 4.10:

a PVDG, which contains the Dry Gas fluid properties,

b PVTO with the Oil properties, and

c PVTW the water properties.

d Only one PVT region has been specified: PVT1.

Hint Menu option PVT Keywords: View | Keywords displays keyword names.


Figure 4.10 DMM - PVT keywords

8 Select PVT Keywords: View | Plot to view the data graphically.This shows both Oil and Gas properties.

9 Double-click on the top section workspace to toggle between the two graphs.Figure 4.11 PVDG and PVTO properties for the BUILD1_E100 model

10 Select File | Close to return to the PVT Keywords panel.

11 Select PVT Keywords: Edit | Insert keyword


53

12 Select DENSITY from the list of Keywords.

13 Insert the following values:

14 Click on Apply to commit the data.

15 Select Edit | Explore keyword|Toggle Desc/Keys and then select the ROCK keyword.

16 Enter:


18 Select PVT Keywords: Keyword Types | Miscellaneous from the menu bar.

19 Select Edit | Explore keyword|Toggle Desc/Keys and then select the RPTPROPS keyword.

20 Switch on the outputs of Oil PVT tables and Gas PVT tables.

21 Click on Apply to commit.

22 Select File | Close to exit from the PVT Keywords section.

23 Select PVT Section: File | Save to save the data to the same file that initial save was done.

Note If any regions have been specified using PVTNUM, the Region File Save panel appears, to allow these to be written to the Build1_reg.inc file.

24 Select PVT: File | Close to exit.

SCAL section: saturation definitions

SCAL keywords1 Select Data Manager: SCAL.

2 Select File | Import | New... and read the saturation keyword file scal2.rcp.

Hint Change the File Browser filter to search for *.rcp if required

3 Select SCAL Section: Section | Keywords.

4 Use SCAL Keywords: View | Plot to graphically view the Saturation versus Relative Permeability curves.

Values may be changed in the table until the graphs are more acceptable. The graph is updated automatically when you click on the Apply button.

5 Select File | Close to close the Graph panel.

Oil density 749.389 kg/m3

Water density 1000 kg/m3

Gas density 1.11242 kg/m3

Reference pressure 400 bar

Rock compressibility 4.0E-5 /bar.


6 To return to the main SCAL Section panel, select SCAL Keywords: File | Close

7 Select SCAL Section: File | Save As... to save the data to disk, as well as the project. This section is saved to Build1_scal.inc.

8 Accept the default filename.

9 Select SCAL Section: File | Close to exit.

Initialization section1 Select Data Manager: Initialization.

2 Select Initialization Section: Edit | Insert Keyword.

3 Select EQUIL to specify the initial equilibration conditions.

4 Insert the following data for EQUIL:

To indicate that the default value should be used in the simulation, the data field should be left empty, in which case ECLIPSE Office writes “1*” as a placeholder in the file.

Leave the Accuracy field empty, so that the default value is used in the simulator.


6 Insert the RSVD keyword.

7 Insert data for RSVD, using the TAB key to move between columns, and the + symbol on the top right corner of the table to add a row.

8 Click on Apply.

Aquifer data1 Select Initialization Section: Keyword Types | Aquifer to display aquifer related

keywords.

2 Select Initialization Section: Edit | Insert Keyword.

3 Click on AQUFETP to define the general aquifer parameters for a Fetkovich aquifer, and AQUANCON to define the aquifer connections with the reservoir.

4 Click on Fetkovich Aquifer and insert data for AQUFETP:

Datum depth 3000 m

Pressure at datum depth 331.65 bar

WOC depth (Oil-Water contact depth) 3085 m

OW Cap Pressure (Oil-water Pc at OWC) 0 bar

GOC (Depth of Gas contact) 3000 m

GO Cap Pressure (Gas-Oil Pc at GOC) 0 bar

RS/Pb v Depth table number 1

Rv/Pd v Depth table number 1

3000m 477.91 sm3/sm3

4000m 486.6 sm3/sm3


55

Note To change the unit of a column, click on the column with the right-mouse-button and select Change Units from the menu displayed. The Initialization: Aquifer Connections panel appears on which pressure units kPa can be selected from the drop-down lists. Save to disk converts the units as needed.

5 Enter the following data:

6 Leave the Salt Water Concentration field empty.


Hint Table edit functions are displayed when the right mouse button is pressed with the cursor on the table.

8 Insert data the following data for AQUANCON, using the TAB key to move between columns. Click on the + sign on the top right corner of the table with the cursor in last column to add a row.

The connection face (J/I) is selected from a dropdown list that becomes active once you click in the cell.


Inserting keywords1 Select Initialization Section: Keyword Types | Miscellaneous and then Edit | Insert

Keyword to insert keyword RPTSOL.

2 Check the parameters:

a Grid Block Pressures, Oil, Water and Gas Saturations

b Restarts/Initial Restart and Fluid In Place Reports with Balance Sheet.

3 Click on Apply to commit the options.

4 Use File | Save As... to write the data to the file Build1_INIT.INC and update the project with the section.

Id of Aquifer 1

Datum depth 3113.2 m

Initial Aquifer Pressure 337.582 bar

Initial Aquifer Volume 18.0E9 m3

Total Compressibility (Rock + Water) 5.0 E-5 /kPa

Aquifer Productivity Index 500 sm3/day/bar

PVT Water Property Table 1

Aquifer ID Lower I Con

Upper I Con

Lower J Con

Upper J Con

Lower K Con Upper K Con

Connection Face

1 1 10 1 1 4 4 J-

1 1 10 10 10 4 4 J+

1 1 1 1 10 4 4 I-

1 10 10 1 10 4 4 I+


5 Select Initialize Model | Run Simulation. This runs the simulator to the first time step. An initial restart file is created which contains details of grid block pressure and saturations at the beginning of the run.

6 Select Initialize Model | FIP Report to see initial fluids in place. Select this option again to return to the keywords.

Note If more than one Fluid-In-Place region has been defined using FIPNUM, then the panel will contain data on a region-by-region basis as well as at field level.

7 Select Initialization Section: File | Close to exit from the Initialization Section.

Schedule section: production schedule1 Select Schedule from the Data Manager list.

2 Use the Schedule Section: File | Import | New... to import the file sched2. All initial well specifications, well completion and well controls are specified in this file.

Hint Change the File Browser filter to *.sch, if required, to make it visible in the browser window.

3 Use File | Import | Append... to add the history data from the file wconhist.

Note Ignore the warning that the SCHEDULE keyword does not exist, and continue.

4 Select File | Save As... to save the data to the default ECLIPSE Office file Build1_SCH.INC. Update the project with the data at the same time.

5 Click on each time/date to see the events connected to it.

6 Toggle between keywords and descriptions of events using View | Description and View | Keyword.

7 Select Schedule Section: File | Close to close the section.

Note If the Generic Keywords option is ON in the Dimension Overrides section:1. In Data Manager > Section > Dimension Overrides, select Keyword Well Dimensions.2. Change the 4 dimensions to 4, 3, 2, and 5 respectively. Click on Apply and close the Dimension Overrides Section.

Summary section1 Select Data Manager: Summary

Summary variables contain vector data, such as well production rates, for each report step, and are saved in the .Snnnn files during the simulation run.

2 Select Summary Section: File | Import | New... to import the summary vectors from the file summary.dat.


57

3 Click on the Selected button to see the vectors which have been loaded.

Adding summary vectors 1 Click on the Keywords button to return to the panel where new output mnemonics may be

added.

2 Select the Field tab on the Summary Section panel

3 Select others from the Phases list, and Pressure from the Types list. FPR will be listed in the Keyword selection box.

4 Click on FPR in the Keywords list to make it active.

5 Click on Add to List to add this keyword to the selected list of summary vectors.

Producing bottomhole pressures for all wells1 Select the Well tab.

2 Select others from the Phases list, and Pressure from the Types list.

3 Select WBHP from the Keyword list.

4 Select All wells in the Wells list.

5 Click on Add to List to insert the keyword into the selected list.

6 Use Summary Section: File | Save As... to save the list to the project and the summary include file Build1_SUM.INC, on disk.

7 Summary Section: File | Close closes the Summary Section and returns you to the main Data Manager panel.

8 Select Data Manager: File | Close to return to the main ECLIPSE Office project panel.

Run manager1 Click on Run on the main ECLIPSE Office panel to activate the Run Manager.

2 Select Run Manager: Submit | Runs to submit the simulation run.

Hint If a run has been attempted on a previous occasion with the same project, the file Build1_E100.DATA might exist. In such a case the program gives you the opportunity to either use the previous data file, or overwrite it with the current data. Choose the YES option to overwrite the existing file.

3 Check the Log window to check if submission was successful and to monitor the progress of the files written to disk at each reportstep. (See Figure 4.12).


Figure 4.12 Log window with information on runs

4 Select Run Manager: Monitor | Control Simulations for information about the current run. This option is only activated once the simulation started.

5 Check the Log window for messages about the simulation.

6 Select Run Manager: File | Close once the simulation run is finished.

Report generator1 Click on Report on the main ECLIPSE Office project panel, to activate the Report

Generator.

2 Select Report Generator: File | Open Current Case | PRT... to open the PRT file created by the simulation run.

Note The BUILD1_E100.PRT file contains all output requested by the PRT* keywords selected in each data section of the data model; as well as a report on the errors or problems found during the simulation run.

3 Select Errors... from the Report drop-down.


59

Note It is sometimes useful to look at the complete .PRT file in order to resolve errors with regard to erroneous data in keyword arguments. In the .PRT file the error is generally directly after the keyword involved. The Util | Text Editor can be used at any point in time to view this file.

4 Tick ERRORS and WARNINGS then click on Generate Report.

If there are no errors, the ERRORS option is not available for selection.

Note If errors appear with a Simulation Failed message in the Log window, the errors listed in the report have to be resolved in the Data Manager before attempting a simulation run again.

5 Select Output to see the report.

6 Exit from the Report Generator module with the File | Close option.

7 Save the project on the main ECLIPSE Office project panel, using the menu option File | Save Project.

Note See "Report Generator" on page 316 and "Result Viewer" on page 284 to view the simulation results. "Tutorial 4: History matching using ECLIPSE Office and SimOpt" on page 86 shows the basic procedure of a History Matching process, using the same model as above.

8 Select File | Exit to exit.

60 Tutorials ECLIPSE Office 2007.1 User GuideTutorial 3: Constructing a PEBI simulation grid

Tutorial 3: Constructing a PEBI simulation grid

ObjectiveThe aim of this section is to demonstrate how a PEBI simulation grid can be constructed using the Unstructured Gridder option in ECLIPSE Office. The primary purpose of this tutorial is to familiarize you with the major aspects of the Unstructured Gridder; not all menu options are addressed, however.

This tutorial takes about one hour to complete.

StagesThe goal of this tutorial is to construct a PEBI simulation grid within ECLIPSE Office and then use this grid in a simulation run. This requires importing and managing a wide variety of data (that is tops, thickness, wells, porosity etc.). The tutorial stages are as follows:

• "Problem description" on page 60

• "Getting started" on page 60

• "Importing reservoir boundary and layer data" on page 62

• "Importing/manipulating well data" on page 68

• "Importing/manipulating fault data" on page 70

• "Importing porosity and permeability data" on page 74

• "Viewing input data" on page 74

• "Generating a grid and properties" on page 75

• "Editing properties of the unstructured grid" on page 78

• "Saving and exiting the Unstructured Gridder" on page 79

• "Running an ECLIPSE simulation" on page 79

Problem descriptionIn this tutorial you construct a 4-layer reservoir model from a variety of data sources. First, the reservoir boundary and layers are defined. Mesh maps of top depth and thickness are then imported to construct a framework for the model. Next, well and fault locations are added to the model. Then, porosity and permeability data is imported. Once all the pieces are in place, the grid and its properties is generated using the PEBI gridder. Finally this grid is used in an ECLIPSE simulation.

Getting startedAll the necessary data files are in the directory $ECLARCH/$ECLVER/office/tutorial/example3.

ECLIPSE Office 2007.1 User Guide TutorialsTutorial 3: Constructing a PEBI simulation grid

61

The following steps guide you into the Unstructured Gridder section of ECLIPSE Office.

1 Start ECLIPSE Office from the ECLIPSE Launcher (on UNIX: @office).

2 From the top menubar select File | New Project and give this project the name Tut3.

3 Choose File | Save Project



6 Open the Data Manager module (now referred to as DMM) by either selecting the Data button in the left column or by choosing Module | Data Manager... from the top menubar.

7 Select DMM: Case Definition

8 In the General tab set the Units to metric.

9 In the PVT tab select the following phases: Water, Oil, Gas, Dissolved Gas.

10 In the Misc tab set NSTACK (Stack size of Previous search directions) to 50.

11 Click on OK to exit the Case Definition Section.

12 Select DMM: Grid Section. The grid is empty because no data has been imported yet.

13 Select DMM: Grid | Subsection | Unstructured Gridder... to open the Unstructured Gridder.

The Unstructured Gridder contains six major sections:

Reservoir data This displays in a tree format the data that has been imported into the reservoir model. It contains both structural and property data. This is referred to throughout the tutorial as the Reservoir Data Tree.

Areal view This displays an IJ slice through the reservoir. It is initially the active window of the Unstructured Gridder.

Navigation graphThis allows you to see what portion of the reservoir is currently displayed in the active window. This is most useful when the zoom option has been used.

Cross sectionThis displays a cross section through the reservoir. The line of the cross section can be seen and moved in the Areal View window.

CaptionThis allows you to check the status of the gridding, see information about imported data, and see the number of geological and simulation layers in the model.

LegendThis displays the color legends when plotting various properties.


It is useful to hide all windows except the Unstructured Gridder so as to keep the desktop from becoming too cluttered. To do this:

1 Minimize the Unstructured Gridder

2 Minimize ECLIPSE Office

This causes all the other windows to minimize as well

3 Maximize the Unstructured Gridder window.

Importing reservoir boundary and layer dataOnce inside the Unstructured Gridder, you must first define a volume for the reservoir model. This can be done in several ways:

• Create | Main Volume | Digitize

This digitizes a boundary for the reservoir.

• Create | Main Volume | Rectangular

This creates a rectangular reservoir boundary.

• Create | Main Volume | Circular

This creates a circular reservoir boundary.

• File | Import ASCII | Volumes...

This reads in an ASCII file containing the coordinates of the boundary.

Importing a reservoir boundary1 File | Import ASCII | Volumes...

2 Select the file boundary.zon and click on Open.

This opens the Select Volume File Format window.

The Volume File Format is X Y Name.

Note The outer boundary coordinate data is currently supported with four formats. Also, UTM offsets can be input for metric data.

Make sure your data is the same as that in Figure 4.13.


63

Figure 4.13 Select Volume File Format window

3 Once the data has been entered in the Select Volume File Format panel, click on OK.

4 Settings | Map Limits...

5 Click on the Reset button in the Set Display and Mesh Map Limits window to update the Areal View window.

6 Click on OK.

The primary volume now needs a constant properties table. This table defines the number of layers and constant property values for each layer. The maps attached later in the tutorial automatically override the values defined in the constant properties table.

7 Select the Boundary in the Reservoir Data Tree.

8 Create | Const. Props.

This opens the Edit Property Data window

9 Click on the + button in the top right corner of this table to create 4 layers

10 Compare with Figure 4.14.


Figure 4.14 Edit Property Data window

11 Select OK in the Edit Property Data window.

The Props box should now appear in the Reservoir Data Tree.

Creating layers and mapsNow that the boundary and constant properties table for the reservoir are defined, layers can be added.

For this data set, four layers need to be created. Each layer has a thickness map associated with it. In addition, the top layer has a top depth map associated with it.

To create the layers and associated maps:

1 Select the Boundary in the Reservoir Data Tree (once selected it should be highlighted in red)

2 Create | Layer

Use this command four times to create four layers. These layers appear immediately in the Reservoir Data Tree.

Hint The name of a layer can be changed by double-clicking on the layer in the Reservoir Data Tree and modifying the Layer Name in the Edit Layer Data window.

3 Select Layer1 by clicking on it once in the Reservoir Data Tree.

4 Select Create | Map | Tops and Create | Map | Thickness to add tops and thickness maps to Layer1.

5 Select the other layers (one at a time) and choose Create | Map | Thickness.

This associates a thickness map with each layer.


65

Now all the layers should have maps associated with them. The Unstructured Gridder should look like the one in Figure 4.15.

Figure 4.15 Unstructured Gridder showing the addition of 4 layers and associated maps

Importing map dataThe maps have now been created, but there is no data associated with any of them. In this tutorial thickness and top depth data are imported as mesh maps. There are other options available such as contour data and scatter data that you may find useful.

When importing mesh maps the limits must first be defined by following these steps:

1 Settings | Map Limits...

This opens the Set display and mesh map limits panel.

2 Select the tab labeled Mesh Map.

3 Set the limits of the mesh maps so that -100<x<1600 and -1400<y<300.

4 Click on OK to commit the changes to mesh map limits and close the panel.

Hint It is important to set the mesh map limits before importing any mesh maps. Once a mesh map has been imported the mesh map limits become read-only. All mesh maps must be the same size.


5 Select the Tops Map in Layer 1 of the Unstructured Gridder Window | Reservoir Data Tree.

Hint If the Tops Map is not visible in the Reservoir Data Tree, click on the + button next to Layer 1 to expand this branch.

6 File | Import ASCII | Mesh Map...

7 Open the file tops.L01.

This opens the Select Mesh Map Format window in which you must specify the header format, the arrangement of the grid (ordered by rows or columns), and the location of the mesh origin.

Note The ASCII mesh map file is assumed to consist of a header area followed by a grid of NX*NY values. You can select from a number of industry standard header formats.


9 Click on OK in the Select Mesh Map Format window to complete the import of data.

Note Maps which contain mesh map data are indicated by the letter M in the Reservoir Data Tree. The tops map that was just imported should now have an M to indicate that it is a mesh map. If it does not, click on another object in the Reservoir Data section and the M should appear.

10 Select the Thickness Map in Layer1.

Caution Make sure it is highlighted red, indicating it has been selected.


12 Open thick.L01

This is the thickness data for Layer 1.

13 Click on OK in the Select Mesh Map Format window (any changes made before are now the defaults) to complete the import of thickness data for Layer 1.

14 Select the Thickness Map in Layer2


16 Open thick.L02

Mesh Map Property Unit m

Mesh Map Format ASCII NX*NY values

Data is ordered by rows Checked

Scatter/Mesh Map Origin First Pt in file is at Top Left

Coordinates are in UTM units Not checked

UTM X offset 0

UTM Y offset 0

Null Value 1000000


67

This is the thickness data for Layer2.

17 Click OK in the Select Mesh Map Format window.

18 Import the mesh map thickness data for Layer 3 (thick.L03) and Layer 4 (thick.L04) following the same procedures as above.

Cross section windowThe Cross Section window can be used to examine the newly imported data. It should now display all four layers. The location of the cross section line can be modified in several ways:

• Settings | Cross Section... opens the Cross Section Line Coordinates window in which the end points of the cross section line can be modified and applied.

• Edit | Edit Point; Edit | X Edit; and Edit | Y Edit can all be used to alter the location of the cross section line. Simply click on one endpoint of the cross section line and drag in to the desired location.

Viewing the active cross section1 Settings | Cross Section...

2 Choose the Default button or make sure that the cross section line coordinates are the same as the following data:

3 Select OK to close the Cross Section Line Coordinate window

4 Double-click in the Cross Section window to bring it into the active frame

5 Compare with Figure 4.16 to make sure that all tops and thickness data has been imported correctly.

X (m) Y(m)

-96.64 -550

1596.9 -550


Figure 4.16 Cross Section displayed as active window

6 Make the Areal View active again by double-clicking on it.

Importing/manipulating well dataFollow the steps below to import two vertical wells into the Unstructured Gridder.

1 Select the Reservoir in the Reservoir Data Tree.

2 File | Import ASCII | Vertical Wells...

3 Open the file VERT.WEL.

4 In the Select Well Format panel click on the View File button to view the well data.

This option allows you to inspect the format of the file before importing the data. This is useful because there are several different formats that are acceptable for well data.

This data file is of the format X Y MD TVD

The figure -999 is used as a marker to separate the wells in this data file

5 Choose Close View in the Select Well Format window to hide the well data.


69

6 Modify the Select Well Format window with the following data:

7 Click on OK in the Select Well File Format window to complete the import of the well data.

Note One limitation of the Unstructured Gridder is that deviated wells are not supported.

Now that the well data has been imported you can now manipulate it. If necessary, you can change the perforations

Changing well perforations1 You can modify the well perforations in the following manner:

2 Double-click on Well1 in the Reservoir Data Tree.

This opens the Edit Well Data window.

3 Click on the Perforations... button to open the Edit Perforation Data window.

4 Edit the Start location of the perforations as follows:

Hint The true vertical depth of the perforations can be seen by clicking on the True Vertical Depth... button in the Edit Perforation Data window. These values are read-only.

Note Although multiperforated wells are allowed in the Unstructured Gridder, these wells appear to be fully completed through the reservoir.

Now the Unstructured Gridder should look similar to Figure 4.17.

Well File Format X Y MD TVD

Marker value -999

UTM X Offset 0

UTM Y Offset 0

Start (m) End (m) Radius (m) Skin Active

10 0.088392 0 Yes


Figure 4.17 The Unstructured Gridder after the import of mesh maps and well data

Importing/manipulating fault dataFault data is now be added to the model. There are four faults in this model. The importation is similar to well and map imports:

1 Select the Reservoir in the Reservoir Data Tree

2 File | Import ASCII | Faults...

3 Open Fault1.FLT.

This opens the Select Fault Format window.

4 Select View File in this window to check the format of the data.

This data is ‘X Y Name’.


71

5 Click on Close View in the Select Fault Format window to hide the fault data.

6 Compare the Select Fault Format window with that shown in Figure 4.18.Figure 4.18 Select Fault Format window

7 Select OK to complete the import of fault data.

8 Repeat the above procedure to import the other three faults (fault2.flt, fault3.flt, and fault4.flt).

Note Sloping fault geometries are not supported.

Digitizing a faultSome of the faults are zig-zag in appearance. In this section we will change one of these faults to a template and digitize a new, smoother fault over the top of the old one.

1 Select Fault 4 in the Reservoir Data Tree.

2 Edit | Feature opens the Edit Fault Data window.

3 Check the Fault is a template box.

4 Click on OK to make Fault 4 into a template and close the Edit Fault Data window.

Hint Faults that are templates appear as a faint line rather than as a bold line. Fault 4 should now appear as a faint green line in the Areal View window of the Unstructured Gridder. Also, templates are not saved upon exiting the Unstructured Gridder.

5 Select Create | Fault (or use the appropriate icon ).


In the Areal View window, the cursor is now pencil shaped to indicate that you are ready to digitize.

6 Start digitizing by clicking the left mouse button on one end of the fault.

7 Click the left mouse button on several more locations along the template to make fault segments.

As you can see in Figure 4.19 a black square appears every time you create a segment of the fault.

Figure 4.19 Unstructured Gridder window during the digitization of a fault

8 Double-click or press Return when you reach the other end of the fault, to complete the fault.

The black squares disappear.

If you are not satisfied with this new fault then delete it in the following manner:

9 In the Reservoir Data Tree, select Fault 5

10 Select Edit | Delete Feature.

Once you have digitized a new fault, you can get rid of the old one. To do this:

11 In the Reservoir Data Tree, select Fault 4.

12 Select Edit | Delete Feature.

Hint An alternative way to delete features is to first select them in the Reservoir Data Tree and then select Delete feature from the right mouse button menu to remove them.


73

Smoothing faultsThe Unstructured Gridder also has an automatic fault smoothing option. To implement this option:

1 Double-click on Fault 5 in the Reservoir Data Tree to open the Edit Fault Data window

2 Click on the Smooth button to open the Smoothing Parameters window

3 Edit the Smoothing Parameters window with the following data:

Hint The amount of smoothing can be increased by increasing the noise level or switching to the least-squares linear mode.

4 Click on Smooth

5 Click on Accept to accept the new fault.

The Unstructured Gridder should now appear similar to Figure 4.20.Figure 4.20 The Unstructured Gridder displaying the smoothed faults

Identification mode Least squares linear

Noise level 155 m

Keep end points of faults Checked


Now all that is left to complete the model is to import the properties data.

Importing porosity and permeability dataThe final step in creating this model is importing porosity and permeability data. For this tutorial the porosity and permeability data are scatter data.

1 Select Layer1 in the Reservoir Data Tree.

2 Create | Map | Perm_X and Create | Map | Porosity

Hint If no Perm-Y map is defined, then both X and Y permeability are obtained from the Perm-X map. In this tutorial Perm-Z is constant and is defined in the constant properties table.

3 Repeat these steps for the other 3 layers

4 Select the Perm-X map in Layer1

5 File | Import ASCII | Scatter Data...

6 Load the permeability file permx1.cnt

Markers, indicating the locations of the scatter data, appear in the Areal View window.The Select Scatter Data Format dialog box opens up.

a Accept the defaults on the Select Scatter Data Format Window and click OK.

7 Select Scatter Data Format dialog box opens up and click OK.

8 Select the Porosity map in Layer1

9 File | Import ASCII | Scatter Data...

10 Load the porosity file poro1.cnt

11 Repeat these import steps for the other three layers.

Note In general, PEBI grids can only be used with isotropic models. In the Unstructured Gridder, anisotropic models with constant Kx:Ky ratio are supported. Fully anisotropic models are supported only for single-phase models.

Viewing input dataNow that all the data has been imported into the Reservoir Data Tree, it is useful to look at some of this data.

1 Select View | Options to open the Edit View Options window.

2 Under the Line/Text tab, deselect the Scatter/Contour data button.

This turns off the markers for the scatter data.

3 Under the Color Fill tab, select Property Display | Input Map and Layer1 Tops.

Select Contour Lines option.

4 Click on Apply.

5 Click on OK in the Edit View Options window to close the window.


75

The Unstructured Gridder Window | Areal View should now contain a color map of the tops data, similar to Figure 4.21.

Figure 4.21 Unstructured Gridder window displaying Layer 1 Tops Data

Generating a grid and propertiesWe can now generate both a grid and grid properties.

Setting grid style and grid resolutionYou can control the grid style and resolution by adjusting the grid controls. This is described below.

1 Double-click on Boundary in the Reservoir Data Tree.

This opens the Edit Primary Volume Data panel.

2 Select the Grid Controls... button.

The Volume Grid Controls panel now appears.

The Grid Style should be set to Variable (this is the default)


Hint Various PEBI gridding styles are supported. These can be selected in the drop-down menu for Grid Style.

3 Modify the following elements of the Volume Grid Controls.

a Relative minimum cell size = 0.02

b Relative maximum cell size = 0.05

Note For variable gridding style, you should specify either the relative maximum and minimum cell size or the absolute maximum and minimum cell size.

4 Click on OK in the Volume Grid Controls to apply the changes and close the panel

5 Click on OK in the Edit Primary Volume Data window.

Note The gridding around faults and wells can also be modified by you. This is done in the Grid | Grid Controls menu.

Generating the gridNow that the grid style and resolution have been edited, the grid can be generated.

1 Make sure Grid | Show grid report is selected (if it is selected a check mark should appear next to it in the drop-down menu).

2 Grid | Generate Grid

This generates the unstructured grid.

The Grid Report window appears to inform you which items have not been fully gridded. You can choose to either halve the bulk cell size to try to fully grid these items, or ignore the items that cannot be fully gridded.

3 Opt to ignore the items that cannot be fully gridded.

4 Click on OK.

This completes the grid generation.

After generating a grid the zoom options allow you to examine the grid in detail to decide if it is honoring the structural data.

Zoom options1 Select Settings | Cross Section... | Default to make sure your cross section is the same

as the tutorial, (recalled in the following table:

2 Bring the cross section into the active window by double-clicking on it.

X (m) Y(m)

-96.64 -550

1596.9 -550


77

3 Use the Rubberband Zoom In button for zooming in on the region around the fault. Zooming allows you to inspect faults and wells more closely. Select the part of the plot you wish to inspect by click-dragging around it.

4 Now unzoom completely and click on to deselect the rubberband zoom.

5 Double-click on the Areal View window to make it the active window again.

Generating propertiesNow the property data can be assigned.

1 Grid | Generate Properties

This assigns permeability and porosity values to the unstructured grid.

Hint Do not be alarmed if the Generating Grid box or the Generating Properties box appears to freeze. Grid generation can take some time.

The unstructured grid that is generated should appear similar to Figure 4.22. Figure 4.22 Unstructured Gridder after generating a grid.


Viewing properties of the unstructured gridNow that the grid has been generated you can view the permeability and porosity data for this grid as described below.

1 View | Options

This opens the Edit View Options window

2 In the Color Fill tab choose Initial property and Porosity.

3 Select Apply and OK

4 The Unstructured Gridder | Areal Viewer now displays a color map of the porosity values.

Modifying the range of the color map1 In the Areal Viewer, double-click on the numbers beneath the color legend.

2 In the Color Legend Editing dialog box, change the range to go from 0.1 to 0.2.

3 Click on OK.

Editing properties of the unstructured gridYou can view and edit the properties of individual grid blocks.

1 View | Options

This opens the Edit View Options window

2 Select the Color Fill tab

3 Choose Initial Property and Porosity

4 Click on the Edit Properties button in the Edit View Options window.

This opens the Selected Cells window

5 Deselect Unstructured Gridder: 2D | Show cell probe so that a new window is not displayed when using the cell probe

6 In the Unstructured Gridder choose 2D | Pick.

This activates the cell probe.

7 Select a cell in the Areal View window.

The porosity value and the index for this cell should now appear in the Selected Cells window.

In the Selected Cells window the porosity value of the highlighted cell can be changed.

Hint Multiple cells can be selected by holding down the Shift key and then selecting cells with the left mouse button. The Selected Cells button in the Edit Initial Property window can then be used to view or edit the values for this set of cells.

8 Click on Cancel in the Selected Cells window.

9 Click on Cancel in the Edit View Options window.


79

Saving and exiting the Unstructured GridderNow that a grid has been created it can be used by the rest of ECLIPSE Office.

1 Unstructured Gridder: File | Save opens the Save File window

The grid for visualization is saved in Tut3.pgrid.

2 Select Save to complete the save.

3 File | Close closes the Unstructured Gridder.

4 If the other ECLIPSE Office windows are minimized, maximize them now

5 Select File | Close to close the Grid Section window.

The active window should now be the Data Manager.

Running an ECLIPSE simulationNow the remaining data is imported and an ECLIPSE simulation is performed.

Importing PVT dataThe PVT data is in the file PVT.data

1 In the DMM choose the PVT button to open the PVT Section

2 Select File | Import | New to import the file PVT.data

3 File | Save As... saves this data to the file tut3_pvt.inc

4 File | Close

Importing SCAL dataThe SCAL Section data is imported as follows:

1 In the DMM choose the SCAL button to open the SCAL Section

2 Select File | Import New to import the file SCAL.data

3 File | Save As... saves this data to the file tut3_scal.inc

4 File | Close

Entering initialization dataThe initialization data is entered as follows:

5 In the DMM choose the Initialization button to open the Initialization Section.

Hint It may take some time for the Initialization Section to open because all the information for the PEBI grid must be read.

6 Choose Edit | Insert Keyword to insert the keyword EQUIL


7 Enter the following data for the EQUIL (Equilibrium Data Specification) keyword:

8 Select Apply to finalize the changes to the initialization data

9 Select File | Save As... to save the data to the files tut3_init.inc.

10 Choose File | Close to close the Initialization section

Entering Schedule dataThe Schedule Section takes a little more time to update. The well location (WELSPECS) and well connection (COMPDAT) keywords have already been input by the Unstructured Gridder. These keywords need to be checked.

1 WELSPECS: check that the preferred phase is correct

Well1: should have OIL as its preferred phase

Well2: should have OIL as its preferred phase

2 COMPDAT: check that perforations of all wells are OPEN

Specifying the well control keywords (WCONPROD) 1 In the Events All window select the last event

2 From the menu choose Event | New.

This opens the New Event panel.

3 Choose Event Types | Well Controls and Limits in the left window

4 Choose Events | Production Well Control in the right window

5 Click OK.

The keyword WCONPROD should now appear in the Events-All box in the Schedule Section.

6 Enter the following data production well control (WCONPROD):

7 Click Apply.

Depth 2000 m

Pressure 200 bar

WOC Depth 2300 m

OW Cap Pressure 0 bar

GOC Depth 2000 m

GO Cap Pressure 0 bar

Rs/Pb v Depth Table 0

Rw/Pdw v Depth Table 0

Accuracy 0

Well WELL2

Open/Shut flag OPEN

Control ORAT

Oil Rate 2000 m^3/day

BHP Target 150 bar


81

Hint It is important to check that the Well Name for the WCONPROD keyword matches exactly with that in the WELSPECS keyword. These names are case sensitive.

Specifying the well control keyword (WCONINJE) 1 From the menu choose Event | New.

This opens the New Event panel.

2 Choose Event Types | Well Controls and Limits in the left window

3 Choose Events | Injection Well Control in the right window

4 Select OK.

5 In the DMM: Schedule Section input the following data for the keyword WCONINJE:

6 Click on Apply.

The Print File Output Control keyword (RPTSCHED) is entered next


8 Choose Event Types | Output in the left window

9 Choose Events | Print File Output Control in the right window

10 Click on OK.

11 In the DMM | Schedule Section, input the following data for RPTSCHED keyword:

The simulator control keyword (TUNING) is now entered


13 Choose Event Types | Simulator Controls in the left window

14 Choose Events | Simulator Control Parameters in the right window

15 Select OK

16 In the DMM: Schedule Section, go to page 3 of the TUNING keyword and change the Max Linear Iterations in Newton Iteration to 100.

Well WELL1

Injection type WATER

Open/Shut Flag OPEN

Control Mode RATE

Liquid Surface Rate 2000 m^3/day

Grid Block Pressure Checked

Grid Block Oil Saturations Checked

Grid Block Water Saturations Checked

Grid Block Gas Saturations Checked

Grid Block Solution Gas-Oil Ratios Checked

Restarts Every Report

FIP Reports FIP Report

VFP Tables No VFP Table Output


17 Click on Apply.

Finally more dates must be added to the simulation.

18 From the top menubar choose Time | Insert to open the New Time panel

19 Choose a Date of 1 Jun 1983.

20 Use Time | Insert to enter the following dates: 1 Jan 1984 and 1 Jun 1984.

Select the first date; the Schedule Section should be similar to Figure 4.23.Figure 4.23 The Schedule Section after all necessary keywords and dates have been input

21 Now choose File | Save As to save the file tut3_sch.inc and then use File | Close to close the Schedule Section.

Importing summary dataThe summary data is in the file SUM.data

1 In the DMM choose the Summary button

2 Select File | Import | New... to import the file SUM.data

3 File | Save As saves this data to the file tut3_sum.inc


83

4 File | Close.

Note If the Generic Keywords option is ON: 1. In Data Manager > Section > Dimension Overrides, select Keyword Table Dimensions. 2. Change the 3rd, 4th and 6th fields to 22 each. Click on Apply and close the Dimension Overrides Section.

Running the simulation1 In the ECLIPSE Office window choose Module | Run Manager from the top menubar or

click on the box labeled Run on the left and Submit | Runs.

Viewing the resultsOnce the run has ended, close the Run Manager and then, in the ECLIPSE Office window, click on the Result button in the right menubar to open the Result Viewer.

1 File | Open Current Case | Summary

2 In the Result Viewer Module: Extract/Load Summary Vectors window, check the boxes to Read All Summary Vectors and Read All Reports.

3 Click on Load

4 Choose LinePlot | User to open the User Template window

5 Select Time vs. FOPR in this window.

6 Click on Add to List

7 Click OK

The resulting plot of Field Oil Production Rate versus Time is shown in Figure 4.24.


Figure 4.24 Plot of Field Oil Production Rate versus Time

Viewing grid dataIn the Result Viewer:

1 Choose File | Open Current Case | GRID... to open tut3_E100.pgrid.

In the Extract/Load Solutions window:

2 Check Read INIT file

3 Check Read All Reports

4 Click on Load.

5 Result Viewer | View | 3D.


85

Figure 4.25 The 3D Result Viewer displaying the initial oil saturation data

The 3D Viewer window should currently be displaying the oil saturation (SOIL): see Figure 4.25.

To view the gas saturation:

6 Scene | Grid | Property... This opens the Property Display window.

7 Choose SGAS, and the 3D Viewer should automatically update.

For recurrent properties the values at different timesteps can also be viewed. The timestep being displayed is recorded in the bottom right corner of the 3D Viewer window. "Tutorial 1: Standard usage" on page 29 contains more details about viewing results from simulation runs.

Importing a structured gridThis tutorial demonstrated the steps to create an unstructured grid from scratch using ECLIPSE Office. It should be noted that existing data sets can be imported into ECLIPSE Office, and the existing grid file can be converted to a PEBI grid using the Unstructured Gridder. When a structured grid is imported into the Unstructured Gridder, certain data, primarily from the Initialization and SCAL Sections, are lost. Other keywords such as WELSPECS and COMPDAT is updated by the Unstructured Gridder. After converting from a structured to an unstructured grid, all sections must be re-visited and saved to ensure that any incompatible keywords are removed. Only then should a simulation run be attempted.

86 Tutorials ECLIPSE Office 2007.1 User GuideTutorial 4: History matching using ECLIPSE Office and SimOpt

Tutorial 4: History matching using ECLIPSE Office and SimOpt

IntroductionThis tutorial examines the integration of an ECLIPSE Office project with the SIS history matching aid, SimOpt. In this example an existing simulation, along with associated historical well water-cut data, is imported into ECLIPSE Office to provide a basic project and examine the match between the simulation model and the well history.

The project is then exported into SimOpt, where the match can be analyzed using the ECLIPSE gradients option and a regression problem can be set up that is used to improve the history match.

The matched simulation model is then exported from SimOpt and associated with the ECLIPSE Office project as a new case.

Prediction simulations are made using the multiple runs options in ECLIPSE Office.

This tutorial has been broken down into stages. Each stage is self-contained and can be used independently of the full tutorial.

Hint If you are new to ECLIPSE Office or have not completed this tutorial before you are advised to complete all stages in the order in which they appear.

This tutorial takes about forty-five minutes to complete.

Stages• "Setting up an ECLIPSE Office project from an existing simulation model" on page 86

• "Exporting an ECLIPSE Office project for use in SimOpt" on page 88

• "Setting up a history matching project in SimOpt" on page 89

• "Analyzing the current history match and designing a regression problem" on page 92

• "Exporting a SimOpt simulation model for import into ECLIPSE Office" on page 94

• "Multiple prediction runs in ECLIPSE Office" on page 94

Setting up an ECLIPSE Office project from an existing simulation model1 Start ECLIPSE Office.

2 ECLIPSE Office: File | New Project…

3 Call the new project SNARKSIM.

4 ECLIPSE Office: Case | Import…

5 Import the data-set SNARKSIM.DATA

ECLIPSE Office 2007.1 User Guide TutorialsTutorial 4: History matching using ECLIPSE Office and SimOpt

87

6 ECLIPSE Office: Module | Run Manager…

7 Run Manager: Submit | Runs

8 ECLIPSE Office: Module | Results Viewer…

9 Result Viewer: File | Open Current Case | SUMMARY…

10 Select Read All Summary Vectors in the Extract/Load Summary Vectors panel.

11 Select Read All Reports in the Extract/Load Summary Vectors panel.

12 Click on Load in the Extract/Load Summary Vectors panel.

13 Results Viewer: LinePlot | User…

14 Select TIME in the X-Axis Vectors list of the User Templates panel.

15 Select WWCT:PROD1 in the Y-Axis list of the User Templates panel.

16 Click on Add to List.

17 Click OK in the User Templates panel.

Comparing simulation results and observed dataNow that the ECLIPSE Office project has been set up and the simulation run, the results can be compared with the observed well water-cut values.

1 Results Viewer: File | Open Observed | Column Format

2 Open the file prod1.wwct

3 Set the line numbers for the column format in the Column Format User Data panel from their original settings to the required settings as shown in the following table, and then click on OK .

4 Results Viewer: LinePlot | Observed…

5 Select TIME in the X-Axis Vectors list of the Select Observed Vectors for plotting panel.

6 Select WWCT:PROD1 in the Y-Axis Vectors list of the Select Observed Vectors for plotting panel.

7 Click on Add to List.

8 Select Add to Graph.

9 Click on OK.

Table 4.1 Line Numbers when importing Column Format User Data

Line Descriptions Original Line Number Required Line Number

Mnemonics 1 1

Units 2 2

Scale Factors 3 0

Well or Group Names 4 3

Lgr Name or Number 5 0

Local Cell Numbers 6 0

First Line of Data 7 4


DiscussionThe match between the simulated and historical water-cut data for well PROD1 shows that the simulation model currently does a reasonable job over the period of the simulation, but has far too much water produced far to soon in the early history period and insufficient water produced in the late history period. This could be due to transmissibility across the faults being too high, or perhaps Z-transmissibility being too high. Stage 3 of this tutorial, "Exporting a SimOpt simulation model for import into ECLIPSE Office" on page 94, will use SimOpt to examine these parameters and attempt a better history match.

Before this can be done, however, the simulation model must be made ready for SimOpt."Exporting an ECLIPSE Office project for use in SimOpt" on page 88 of this tutorial examines the transition from an ECLIPSE Office project to a SimOpt project.

Exporting an ECLIPSE Office project for use in SimOptIf you did not complete Stage 1 before starting this section of the tutorial, you will need to set up an ECLIPSE Office project with the data file SNARKSIM.DATA.

Hint If you are not sure how to set up an ECLIPSE Office project, see "Setting up an ECLIPSE Office project from an existing simulation model" on page 86

The first step in preparing a simulation model for SimOpt is to create a new case in the ECLIPSE Office project.

1 ECLIPSE Office: Case | Add Case | Clone

This creates a new ECLIPSE Office case that contains the same information as the default case. The New Case Name panel is displayed.

Note SimOpt appends the imported data set name with _1 in the file-root name (that is BASE.DATA becomes BASE_1.DATA). This is so that SimOpt versions of a simulation model are not confused with the original data set. It is important that the original dataset file-root name does not end with an underscore and a number; SimOpt rejects such datasets as they can be confused with the SimOpt versions of the simulation model.

2 Change the Case Name to ORIGINAL.

3 Click on OK.

4 Click on the ORIGINAL case to make it the active case.

5 ECLIPSE Office: File | Save Project.

Creating the INIT fileSimOpt requires GRID and INIT files as well as the dataset. By default, the GRID file is generated by this case. Before exporting the simulation model ORIGINAL from ECLIPSE Office, we need to create the INIT file.

1 ECLIPSE Office: Module | Data Manager…

2 Data Manager: Section | Grid…


89

3 Grid Section: Subsection | GRID keywords…

4 GRID Keyword Section: View | Keywords

5 Select Operational Keywords in the Keyword Type list.

6 GRID Keyword Section: Edit | Insert Keyword...

7 Select Output INIT file in the Keyword Selection panel.

8 Grid Section: File | Save

9 Click on Yes then Save to save the current contents of the Grid Section.

10 Grid Section: File | Close

11 Data Manager: File | Close


Hint This run is only to generate an INIT file (there were no changes to the simulation). The simulation can be turned off to save time.

13 Click on Turn Off Simulation (at the bottom right of the Run Manager).


15 After the run has finished, the file must be written without the NOSIM keyword, ready for SimOpt to read it.

16 Click on NOSIM (Turn Off Simulation) so that it is no longer checked.

17 Run Manager: File | Write Data.

18 Close the Run Manager and save the settings.

DiscussionSimOpt requires a working simulation model and a GRID and INIT file to set up a project. ECLIPSE Office can provide the data-checking and keyword editing facilities to create the files for a SimOpt history matching project.

Setting up a history matching project in SimOpt1 Start SimOpt and call the project SNARK.

2 The Getting Started panel appears. Click on the Specify DATA file button.

3 Import the file ORIGINAL_E100.DATA.

4 In the Getting Started panel, click on the Specify GRID file button.

5 Import the file ORIGINAL_E100.EGRID.

Note The file ORIGINAL_E100.INIT has also been imported during this step.

6 SimOpt: Project | Import | Observed Data | Production | Graf User Vector Data Format…

7 Import the file GRAF.WWCT.


8 Click on the OK button on the message box that warns you that you must set measurement errors.

Now that the basic data for a SimOpt project has been entered, save the project.

9 SimOpt: Project | Save

Note The Well Water Cut data (WWCT) that has been imported has no estimate of the error in the measurement. This information is necessary for SimOpt to calculate the RMS (root-mean-square) fit between the observed and simulated data, and so must now be added manually.

10 SimOpt: Observed Data | Control...

11 Select Set Meas. Error on the Block Action (Selected Set) radio button.

12 Enter a value of 0.01 in the Meas. Error text entry field.

13 Click on Apply Block Action.

14 Click on Close.

Sensitivity modelThe simulation model and observed data are now ready for sensitivity studies. In this case the three faults in the model and the Z-transmissibility of the entire grid will be used in the sensitivity model.

1 SimOpt: Parameter | Add…

2 Select ZTrans in the Parameter Type list and click on Apply.

3 Select Fault on the Domain radio button.

4 Select FaultTr in the Parameter Type list.

5 Click on FAULTS1 in the Domain Names list and then Shift+Click on FAULTS3 to select all three faults.

6 Click on Apply.

7 Click on Close

8 Click in the + sign to the left of the Version 1 node in the Parameter Versions hierarchy tree (that is, the central panel on the main screen).

Defining the transmissibilty multipliersThe fault transmissibility multipliers act along the entire length of each fault. The Z-transmissibility multiplier, however, acts on a number of grid cells and so its region of activity must be defined.

1 SimOpt: Parameter | IJK Region Editor...

2 IJK Region Editor: Region | Define | Using Box(es)...

Now we define the region to cover the entire grid:


91

3 Enter the following data in row 1 of the table and then click on OK:

4 Click on OK.

5 IJK Region Editor: File | Close

Defining starting valuesNow that the parameters of interest have been defined, their starting values and upper and lower bounds must be set.

1 SimOpt: Parameter | Control...

Hint The fault transmissibility multiplier varies between 0 (a sealing fault) and 1 (an invisible fault). If there is no initial estimate of the multiplier’s value, the usual situation, the following rule of thumb can be applied:A change in the transmissibility of a near-sealing fault generally has a much greater effect on reservoir flow (and thus greater sensitivity) than a change in the transmissibility of a near-invisible fault. Consequently, it is usually useful to set the initial value of the fault modifiers to, say, 0.1 and allow the value to vary between 0 and 1.

Hint Vertical transmissibility estimates can be in error by a factor of 100 or more. Consequently it is usually wise to allow the Z transmissibility multiplier to vary from the original simulation model value (that is a multiplier of 1) down from and up to 100 hundred times the original value, that is from 0.01 to 100.

2 Enter the following data in the table in the Parameter Control panel:

Hint The most efficient way to change the modifier value, minimum value and maximum value for the fault transmissibility parameters is to use the Type filter to make the table display only the parameters of type FaultTr, then use the block actions Set Modifier Value, Set Minimum Value and Set Maximum Value to make the required changes to all the fault transmissibility parameters at the same time.

3 Click on Apply in the Parameter Control panel.

4 Click on Close.

I1(nI:14) I2(nI:14) J1(nJ:14) J2(nJ:14) K1(nK:5) K2(nK:5)

1 14 1 14 1 5

Table 4.2 Parameter control starting values

Type Domain Modifier Modifier Min. Modifier Max.ZTrans Region1 1 0.01 100

FaultTr FAULTS1 0.01 1E-5 1




DiscussionA project in SimOpt contains a simulation model, GRID and INIT files, some observed well histories (with standard errors for the observations), and parameters that are varied to try to improve the history match.

The project is now complete, and so sensitivities can be calculated. By taking advantage of the Gradient option in ECLIPSE, the sensitivity analysis can be performed in a single simulation run. The next section examines the analysis of sensitivities to provide a basis for regression to improve the history match.

Analyzing the current history match and designing a regression problem1 SimOpt: Analysis | Simulate…

2 Select Gradient from the Run Mode radio buttons and then click on Start (and click on Yes when prompted to save the project).

Hint To view the simulation run while it is in progress, click, with the right mouse button, on the node for well PROD1 in the Observed Data menu and select Plot. This plots the observed data for well PROD1 with the simulation superimposed.

3 When the simulation has finished, look in the log window at the bottom of the main window.

The RMS fit between all the observed and simulated data is around 24.

Note The multipliers for FAULTS2 and FAULTS3 are marked as redundant. This means that they are not important to the fitting of the data and so can be turned off.

4 SimOpt: Parameter | Control…

5 Set the activity of FAULTS2 and FAULTS3 to Semi-active using the drop-down menus in the Activity column of the table.

Note The “semi-active” activity means that these parameters are no longer used in the analysis and their gradients are no longer calculated during a simulation, but their current modifier values are still used on the model. The only difference when using the alternative “inactive” activity is that the current modifier values are not used.

6 Click on Apply

7 Click on Close.

Reviewing the observed data and remaining parametersNow that the redundant parameters have been removed from the analysis, the remaining parameters can be viewed.

1 SimOpt: Analysis | Match…

2 Click on Update.


93

The RMS folder shows that the RMS and sensitivities of well PROD2 are zero. This is because well PROD2 shuts at time zero so the simulation will always perfectly match the (zero water cut) observed values. Including this observed data in the history match is pointless; it only serves to make the overall match (as reported by the RMS) look better than it really is. For this reason, this observed data should be taken out of the history match problem.

Note In general, all observed data in the history matching project should be examined carefully to make sure that it really contributes to the history matching problem.

3 SimOpt: Observed Data | Control...

4 In the table, set the Status of the WWCT data for PROD2 to Inactive. Click on Apply.

Note This does not delete the data from the project. It merely removes it from the RMS calculation. The data can be added back into the RMS calculation at a later stage by setting its status to active.

5 Click on Close.

Match analysis panel1 Click on Update.

This recalculates the analysis without including the PROD2 data.

2 Click on the Correlation folder.

The off-diagonal elements of the correlation matrix are around 0.33, and so the two remaining parameters are not strongly correlated. If parameters are strongly correlated, the problem may be mathematically ill-posed (which means that regression may not improve the match). In this case the problem seems well-posed and so it is possible to use non-linear regression to iteratively update the modifier values to improve the history match.

Note It is important to remember that the analysis is linear and that the response of the simulation model to changes in the multipliers will be non-linear. Consequently, it is unwise to regress for more than 3 or 4 iterations, as each iteration takes the simulation model further away from the point at which the analysis was valid.

3 SimOpt: Analysis | Simulate…

4 Select Regression in the Run Mode radio button.

5 Set the Max Runs Simulator to 3

6 Click on Update parameters (and click on Yes in the warning dialog that appears). This updates the parameter values using the gradients already calculated for the parameters.

7 Click on Start (and click on Yes when prompted to save the project).

Hint If you want to view the progress of the RMS during the regression, click on the Plot RMS button. (This updates after each simulation run). As before, runtime monitoring of well data is available.

The final RMS fit is 11.7, a big improvement over the ORIGINAL data-set imported into SimOpt.


8 To see the match between observed and simulation data, select the PROD1 WWCT node on the Observed Data hierarchy tree.

9 Select Observed Data | Plot to see the improved history match

DiscussionFollowing a sensitivity run, the gradients were analyzed using tools available in SimOpt. This analysis facilitated the design of a well-conditioned regression problem. SimOpt was then used to run the ECLIPSE simulator, iteratively updating the selected parameters to provide an improved history match.

Exporting a SimOpt simulation model for import into ECLIPSE OfficeThe new simulation model that resulted from history matching can now be exported from SimOpt and used to make prediction runs using the multiple runs feature in ECLIPSE Office.

1 SimOpt: Project | Export | Simulation Model…

2 Click on OK in the Project Export Comments panel.

3 Save the data-set with the name MATCHED.DATA

4 Close the file viewer displaying the exported DATA file.

5 SimOpt: Project | Exit

6 Click on Yes to save the project.

DiscussionThe matched simulation (that is with the multipliers applied) can be exported from SimOpt. This is the original simulation with multiplier keywords added so that, at a later stage, the original simulation model can, if required, be retrieved.

Multiple prediction runs in ECLIPSE Office1 ECLIPSE Office: File | New Project…

2 ECLIPSE Office: Case | Add Case | New

3 Change the Case Name to PREDICTION and select OK.

4 Click on the PREDICTION case to make it the active case.

5 ECLIPSE Office: Case | Import...

6 Import MATCHED.DATA.

Adding a prediction periodNow that the history matched version of the simulation model is in ECLIPSE Office, the next step is to increase the length of the simulation (that is add a prediction period).

1 ECLIPSE Office: Module | Data Manager…

2 Data Manager: Section | Schedule…


95

3 Select the last date in the data-set (1 January 2030) in the Time - Dates list.

4 Schedule Section: Time | Insert…

5 Select Time Step on the New Time Entry Choice radio button.

6 Enter 365 days as the Time Step.

7 Enter 5 in the Num entry box of the New Time panel.

8 Click on OK.

This adds five simulation timesteps, each a year in length, to the existing data-set.

Defining the rate controlsThe next step is to define rate controls for the prediction period.

1 Schedule Section: Event | New…

2 Select Well Controls and Limits in the Event Types list

3 Select Production Well Control in the Events list

4 Click on OK.

5 Enter the following information in the Schedule Section fields for the new WCONPROD keyword:

6 Click on the Multiple Runs button.

7 In the Oil Rate column, enter a value of 3000 stb/day in the second row of the Production Well Control table.

8 Click on OK in the Production Well Control panel.

9 Click on Apply in the Schedule Section panel.

10 Schedule Section: File | Save

11 Save the Schedule and Multiple Sensitivities file.

12 Schedule Section: File | Close.

Prediction runsThe multiple prediction runs are defined, so the prediction runs can now be made.



3 Ensure that the NOSIM (Turn off Simulation) checkbox is not checked because the simulation run is required for generating Summary Vector Reports.


5 Run Manager: File | Close

Well PROD1

Open/Shut flag Open

Control ORAT

Oil Rate 1000 stb/day


Viewing resultsOnce the simulations have finished, the results can be seen using the Result Viewer.

1 ECLIPSE Office: Module | Results Viewer…

2 Results Viewer: File | Open Current Case | Summary…

3 Select both cases (to select a case, click on it and then click on the >> button).

4 Click on OK.

5 Select Read All Summary Vectors and Read All Reports in the Extract/Load Summary Vectors panel

6 Click on Load

7 Results Viewer: Tools | Calculate Totals | Well Production…

8 Select All in the Names list

9 Select PROD1 in the WGNames list

10 Click on Add to List

11 Click on OK.

The graph shows the oil and water production totals for the two prediction runs. It can be seen that improved total production is achieved in scenario 2 (3000 stb/day).

DiscussionIn this final stage, multiple prediction runs were made in ECLIPSE Office so that the effects of different well controls on future production could be determined.

ECLIPSE Office 2007.1 User Guide TutorialsTutorial 5: Streamline Simulation

97

Tutorial 5: Streamline Simulation

ObjectiveECLIPSE Office can be used as a pre-processor, case manager, and post-processor for the FrontSim simulator. This tutorial is designed both to introduce streamline simulation and to demonstrate how ECLIPSE Office can be used to create data sets and visualize simulation results from FrontSim.

Stages• "Streamline Simulation" on page 97

• "Importing existing FrontSim data" on page 98

• "Data Management" on page 98

• "Run Management" on page 101

• "Result Viewing" on page 102.

Streamline SimulationStreamlines, lines that follow the instantaneous flow field, have been used in reservoir engineering as a qualitative tool for visualizing capture zones of wells and flow patterns. Streamline simulators, such as FrontSim, allow you to use streamlines as a part of typical reservoir simulation projects. Streamline simulation can complement traditional finite difference simulation.

Streamline simulation is typically used as an alternative to finite difference simulation for very large models. One of the major strengths of FrontSim for these cases is its speed. Streamline simulators require far fewer pressure solutions than finite difference methods. Additionally, the displacement calculations are one-dimensional and therefore fast to solve. Streamline methods have less numerical dispersion and no grid orientation effects, which can cause inaccuracies in finite difference solutions. Therefore, for certain reservoir simulation applications, streamline methods have a number of advantages over finite difference ones. It is important to understand the strengths and weaknesses of streamline simulation so that it can be applied to appropriate cases.

FrontSim can:

• Simulate very large models

• Simulate on complex geological models defined with corner point geometry

• Visualize reservoir flow paths (breakthrough channels, injector/producer pairs, permeability barriers).

Basically, FrontSim is suitable for large reservoir models where geological heterogeneity dominates the movement of fluids. It is also well suited to analyzing multiple geostatistical realizations of a reservoir. This is an advantage over parallel simulation, which is not well suited to analyzing more than one model.

98 Tutorials ECLIPSE Office 2007.1 User GuideTutorial 5: Streamline Simulation

FrontSim does not have the full suite of well management tools like ECLIPSE, and so is not suitable for cases where detailed well management needs to be accurately simulated.

Importing existing FrontSim dataFor the 2000A release, the FrontSim keywords were altered to make them similar to ECLIPSE keywords. Support for the old-style keywords was dropped in FrontSim and ECLIPSE Office in the 2004A release.

1 Create a working directory in a convenient place and copy /ecl/2007.1/office/tutorials/example5/FRONTSIM.DATA to this directory

2 Start ECLIPSE Office from the ECLIPSE launcher (or @office on UNIX)

3 Select File | New Project from the top menu bar

4 Call the project TUTORIAL5.

5 Case | Import... from the top menu bar and choose FRONTSIM.DATA.

6 Choose File | Save Project to save this model.

The aim of this project is to simulate the flow of oil and water through a heterogeneous reservoir. The model for this tutorial is small, about 7000 cells, but it is adequate for demonstrating the flow of data through ECLIPSE Office. Most typical FrontSim models are significantly larger (105-106 cells). Although these large models require far less time to simulate than in a finite difference simulator, they are not practical for a tutorial.

Data ManagementThis section is intended for people who are not familiar with the ECLIPSE Office Data Manager. If you have used the Data Manager for ECLIPSE projects, this should simply be a review of the most commonly used features.

In this section of the tutorial you are shown how to

• View and edit keyword data

• Visualize keyword and initialization data in 2D and 3D Viewers

• Access manual pages and online help.

This is some of the most useful functionality in the Data Manager.

Now that you have imported the initial data set into ECLIPSE Office, you can use the Data Manager to access and edit this data.

1 In the ECLIPSE Office panel, choose View | Display Model in DM.

2 In the ECLIPSE Office panel, choose View | Display Model in Grid Section.

3 Choose Module | Data Manager to open the Data Manager module (DMM).

The areal view in the Data Manager shows that this is a model with 16 wells and 4 faults. This panel allows access to all sections of the data set. It should be noted that only one section can be opened and edited at a time.

4 Choose DMM: Case Definition.


99

The case definition for FrontSim is much simpler than for ECLIPSE. In the General section, the simulation start date, model dimension, run type, and units are defined. In the Options section the phases and solution scheme are chosen.

Note The only valid run types for FrontSim are Normal and Restart.

From the Case Definition Section you can see the following:

• General tab:

• The start date of the simulation is 1 Jan 2000

• The dimensions of the grid are 20 x 29 x 12

• The units are Field

• The run type is Normal

• Options tab:

• The phases present are Oil and Water.

5 Click on OK to close the Case Definition Section.

6 Choose DMM: Grid to open the Grid Section.

Because we chose to display the model in this section (see step 2), the main Grid Section window contains an areal view of the grid. For very large models, it is sensible to turn off this viewer as the grid can take a long time to draw.

7 Choose Subsection | Grid Keywords to view the keywords associated with this section.

8 In the Grid Section Keywords panel, choose Edit | Explore Keywords.

This panel shows all keywords which are valid for the Grid section of FrontSim models. You can toggle between keywords and descriptions. All keywords that are in the current data set are marked with a *.

9 In the Explore Keywords panel choose Action | Go to Help Pages.

10 Use the Toggle Desc/Keys button to display keywords.

11 Select NTRNSAVE from the list of keywords to see the manual page for this FrontSim-specific keyword.

Note In order to access manual and online help pages Adobe FrameViewer must be installed. Also the path on the local machine must be correctly set so that FrameViewer can be started properly. Please see the release notes if you are unable to access the manual pages.

12 Choose Close on the Explore Keywords panel.

13 Choose File | Close on the Grid Keyword Section panel.

14 In the main Grid Section panel, choose GridView | From Keywords.

15 Answer NO to the question about writing a GRID file.

16 Choose GridView | 2D.

17 In the 2D Viewer, choose View | Options.

18 On the Edit View Options panel select the tab Color Fill | Initial Property | PORO.


Note The 2D Viewer can be used to edit keywords. For details of this see "Tutorial 3: Constructing a PEBI simulation grid" on page 60.

19 Close the 2D Viewer and the Grid Section.

20 Choose DMM: PVT section.

21 Select Section | Keywords from the main DMM - PVT Section panel.

Note The main PVT Section and SCAL Section panels are blank. This is because FrontSim does not contain the many ECLIPSE-specific features, such as API tracking or endpoint scaling, which are set in these panels.

22 Choose View | Plot to display PVDO data on a line plot.

23 Close this panel.

24 Use the Explore keywords panel again to see all valid FrontSim PVT keywords.

25 Uncheck the Valid Keywords Only box and click on Apply.

All FrontSim PVT keywords are now displayed. If you try to insert an invalid keyword, an appropriate error message is given.

26 Close the PVT Section.

The SCAL Section is very similar to the PVT Section. Open and explore this section using steps similar to 21-26 above. For more details on SCAL see "Tutorial 1: Standard usage" on page 29.

27 Choose DMM: Initialization.

28 Insert the RPTSOL keyword in order to produce an initial RESTART file.

Hint You can insert the RPTSOL keyword using either the Explore Keywords panel or the Insert Keyword panel. To use the Insert Keyword panel, you must first select Keyword Types | Miscellaneous.

29 Select Initialize Model | Run Simulation.

30 Answer YES to the question about saving include files.

This option creates a data set with all keywords except the Schedule Section ones. Choosing this option creates a GRID, INIT and initial RESTART file for FrontSim.

31 Select Initialize Model | 3D to see the initial configuration of oil and water in this model.

32 Close the Initialization Section.

33 Choose DMM: Schedule section.

34 Select View | Keywords to see all the keywords for the first time step.

Note the first two keywords RPTLINFS and TUNEFSSA. These are FrontSim specific keywords. The first controls output from the simulator to the SUMMARY files. The second controls the tuning of the pressure and saturation solver in FrontSim. For further details, please refer to the manual pages.


101

Note A very important FrontSim specific keyword is TUNEFSPR. This keyword determines the frequency with which the pressure field is updated. Unlike traditional finite difference simulators, you must decide the frequency with which the pressures are updated.

35 Select the keyword TUNEFSSA.

36 Change the starting point for Streamline to “Choose”

37 Close the Schedule Section.

38 Close the Data Manager.

Note The Summary Section is not accessible for FrontSim cases. This is because FrontSim outputs a predetermined set of summary vectors. Currently you have no control over this list of vectors.

DiscussionThe above steps were designed to familiarize the new user with the Data Manager in ECLIPSE Office. Much of the functionality of this section was not covered, as it is addressed in other tutorials.

Run ManagementThe Run Manager for FrontSim is somewhat different than for ECLIPSE. This is because FrontSim cannot interact with PVM for remote job submission.

• In this section of the tutorial you are given instructions on;

• Controlling output of data from FrontSim simulator

• Submitting runs using various run environments

• Creating and running restart data sets.

1 From the main ECLIPSE Office window, choose Module | Run Manager.

2 For Output File Type select the Unified radio button.

Note The valid run environments for FrontSim are Non-PVM Local, Non-PVM Remote, External Job and LSF. For details on these run environments consult "Tutorial 7: Remote job submission" on page 125.

3 On the Environment drop-down menu select NON-PVM LOCAL.

Note Unlike ECLIPSE, FrontSim does not support formatted output. If you need to view formatted SUMMARY files or RESTART files, use the macros $convert (PC) or @convert (UNIX).

To run this simulation on the local machine:

4 Choose Submit | Runs to start the simulation

To run this simulation on a remote machine


5 Choose Non-PVM Remote on the Environment drop down menu

6 Set Add Simulation Resources to 1

7 Choose Options | Run Environment and insert the relevant data for the remote machine

8 Apply the changes in the Run Environment panel

9 Choose Submit | Runs to start the simulation on the remote machine

Hint If you need to kill or pause a simulation, use the Monitor | Control Simulations or Monitor | Kill Simulations panel.

A message appears in the Log window when the simulation is finished.

10 Close the Run Manager panel.

Adding a Restart RunAdding a RESTART case for FrontSim needs some care. This is because FrontSim does not generate a RSSPEC file. This file is basically an index to the RESTART files which have been created by a simulation. ECLIPSE Office needs this file in order to know which timesteps are available for restart.

The following section shows you how to create a RSSPEC file for a FrontSim run and then how to add a RESTART case in the ECLIPSE Office Case Manager.

1 Open the Result Viewer.

2 Choose Options | Create Restart index file.

3 Select TUTORIAL5_FRONT.UNRST from the file dialog.

ECLIPSE Office should report that it is generating a RSSPEC file.

4 Chose File | Close in the Result Viewer panel.

5 In the main ECLIPSE Office window, choose Case | Add Case | Restart.

6 Select a time step from the Select Report Step to Restart panel.

ECLIPSE Office now creates a restart data set beginning with the selected report step.

Result ViewingViewing results from a streamline simulation is somewhat different than for a traditional finite difference simulator. You now have access to two sorts of data: Grid data and Streamline data. Both of these are useful in interpreting the results of the simulation.

This section is primarily intended to describe the major functionality in the 3D Viewer for displaying streamline data. Please refer to other tutorials for further details of the 2D and 3D Viewers.

Loading in the Grid, Solution, and Streamlines1 In the main ECLIPSE Office window make sure the base case is highlighted.

2 Select Module | Result Viewer.

3 Choose File | Open Current Case | Grid.

4 Select Load on the Extract/Load Solutions panel to import INIT and RESTART data.


103

5 Select View | 3D.

6 In the 3D Viewer, choose File | Import Streamlines.

7 Select OK (Open on PC) to load the streamlines for the current grid.

8 Choose View | Object Appearance and Hide the Grid.

Hint You can also Hide the grid by deselecting the following two icons:

The following section gives details on how to manipulate the streamline display.

Displaying Streamline PropertiesThe first step to displaying streamline properties in a meaningful way is to switch the object for the color legend from grid properties to streamline properties.

1 Select Scene | Color Legend | Object for Color Legend

2 Switch from Grid to Streamlines in the Object for Color Legend panel and Close.

3 Select View | Timesteps... and highlight the first timestep, or click on to move to the first timestep.

4 Advance to the next timestep in order to see some streamlines.

5 Choose Scene | Streamlines | Streamline display to open the Streamline Display panel.

The Streamline Display panel is divided into three folder pages:

• Attributes

This section allows you to choose the property to be displayed on a streamline. If no property is chosen, you can edit the default color of streamlines in this section.

• Filtering

This section allows you to display either every nth streamline using a sample factor, or all the streamlines associated with a given well. Several wells can be selected from the well list at a time.

• Thresholding

This section allows you to view the portion of the streamline which falls within a defined range. Simultaneous thresholding on multiple properties is possible.

6 In the Attributes section select ID_BEG to color streamlines according to injection well.

The current property for the Color Legend is ID_BEG. The numbering for the well display is taken from the order that the WELSPECS are defined in the data set. In this model there are 16 wells. Well 17 in this display represents streamlines that are not starting from an injection well. These streamlines are due to the compressibility of fluids and to boundary conditions.

At the first time step, it is clear that WELL 6 (HALITE-H) is an injector that is greatly influencing the movement of fluids. Several producers such as JASPER-D and PHLOGOPI are producing fluids from areas of the reservoir not influenced by HALITE-H.

Figure 4.26 show streamlines at the first time step of the simulation colored by INJECTORS. Most streamlines begin at the one active injector HALITE-H; these are the streamlines shown in blue. A few wells are extracting fluids that are not being influenced by this injection well.


7 To display fewer streamlines, set Every Nth to a value of 2 in the Filtering section of the Streamline Display panel.

Click on Apply to see every other streamlineFigure 4.26 Plot of Streamlines by ID_BEG

Streamlines can also be used to visualize injector/producer pairs.

8 In the Streamline Display panel, use the right mouse button to turn on Auto Apply.

9 In the Filtering section choose Select All Wells.

10 From the main 3D window choose View | Timesteps.

11 Select the fifth timestep.

From this view (see Figure 4.27) it is easy to see which injection and production wells are paired. JASPER-D for example is producing fluid due to injection in HALITE-H, QUARTZ-A, and ANHYDRIT.

Hint In order to make the well labels more visible in Figure 4.27, the ID_BEG Color Map Editor option Edit Step | Edit Color was used.


105

Figure 4.27 Injector producer pairs at fifth timestep

Streamline properties can be animated over several timesteps. The following steps illustrate how to animate the movement of water fronts from injection wells. This example makes use of thresholding.

12 In the Attributes section of the Streamline Display panel select SWAT as the property.

The water saturation at timestep five should now be visible in the 3D window.

13 Click on the Play icon to see the water saturation move for all timesteps.

Note At the third and fifth timestep new injectors begin operating.

It is useful to see the areas of the reservoir where water has swept completely, leaving behind residual oil. In this model, oil becomes immobile at a saturation of 0.147. Because there are only two phases present, thresholding for water saturations greater than or equal to 0.853 displays areas of residual oil. To do this:

14 Use the Timesteps panel to return to time step 1.

15 Use the right mouse button to turn off Auto Apply.

16 In the Thresholding section of the Streamline Display panel, select SWAT from the Streamline Properties list.

17 Select to move SWAT to the Selected Properties list.

18 Make sure that SWAT is highlighted in the Selected Properties list

19 Set the minimum value of SWAT to 0.85 and the maximum value to 0.95.


20 Click on Apply.

21 Click on the Play icon to see the water saturation move for all time steps.

22 At the final time step you can see the regions of the reservoir that have had complete sweep from the injection wells (see Figure 4.28)

Figure 4.28 Plot of streamlines with water saturation greater than or equal to 1-Sor

Another piece of useful streamline information that is available from FrontSim is time-of-flight. Time-of-flight captures information about how fast fluids are moving in a reservoir. In FrontSim this information is described by two quantities that can be plotted in the 3D Viewer, TIME_BEG (time-of-flight) and TTD (time-to-destination).

The following example shows how TIME_BEG can be used to visualize when injection water breaks through at a nearby production well.

23 In the Line Color section select TIME_BEG.

24 In the Filtering section select QUARTZ-A.

25 Click on Apply on the Streamline Display panel.

Note QUARTZ-A is an injection well that begins injection at the third timestep, 01 July, 2001.

26 Select the third timestep.

The default range for TIME_BEG is much too large, so this must be adjusted to something similar to the length of the simulation.

27 Double-click on the color legend (or choose Scene | Color Legend | Color Legend Editor).


107

28 In the TIME_BEG Color Map Editor, override the Min/Max values with 0 to 2000 days.

29 Press Apply in the TIME_BEG Color Map Editor.

30 Zoom in near the well QUARTZ-A (see Figure 4.29).

It is clear that the injector QUARTZ-A is pushing water towards three production wells: JADE-A4, DOLOMITE, and JASPER-D. The TIME_BEG is simply the time it will take a particle injected at that timestep to reach a certain distance along a streamline. So in Figure 4.29, water injected on 1 Jan 2002 takes 2000 days to travel to the red part of the streamline.

The TIME_BEG given for the streamline configuration at timestep 3 indicates that water breaks through at JADE-A4 very quickly. Breakthrough occurs next at DOLOMITE in less 800 days. If injection and production patterns remain similar, it is unlikely that water will break through at well JASPER-D before the end of this simulation.

It is important to remember that this streamline pattern reflects the conditions only at this timestep. Play through the rest of the timesteps to see how different the configuration of streamlines is for this simulation.

31 Click on the “Play” icon to see the TIME_BEG for all timesteps.

32 For the all timesteps, confirm that the travel times to well JADE-A4 and DOLOMITE are consistent with the third timestep.

Figure 4.29 Plot representing Time from Beginning for injector QUARTZ-A. Time is in days

The water-cut data from production well JADE-A4 and DOLOMITE confirm this 3D view.

What is more interesting is the predictions that you can make about JASPER-D. Given the TIME_BEG data for JASPER-D, it appears that water from QUARTZ-A should breakthrough at about 3000 days. Water from HALITE-H should arrive after around 10000 days.


Adding further timesteps with the same well controls confirms this prediction.

DiscussionThis tutorial demonstrated some of the basic functionality of ECLIPSE Office for handling FrontSim simulations. The 3D visualization section emphasized the various ways streamline data can be used to observe fluid flow paths.

ECLIPSE Office 2007.1 User Guide TutorialsTutorial 6: Adding local grid refinement

109

Tutorial 6: Adding local grid refinement

ObjectiveIn this tutorial we take you through the stages of adding Local Grid Refinement (LGR) to an existing project, where the LGR is added to the gridcells containing a production well. The tutorial is based on the same data set as used in "Tutorial 1: Standard usage" on page 29.

This tutorial takes about one hour to complete.

StagesThe stages covered in this tutorial are:

• "Open existing project" on page 109

• "Insert cartesian LGR" on page 110

• "Run the simulation" on page 117

• "View the simulation output from the local grid" on page 118

Problem descriptionPlease refer to "Tutorial 1: Standard usage" on page 29 for a description of the model.


2 Copy all the files from the Tutorial 6 directory, normally residing in /ecl/2007.1/office/tutorials/example6.

Open existing project1 Start ECLIPSE Office from the ECLIPSE launcher or using the @office command on

UNIX.

2 Open a new project File | New Project, calling it LGR

3 Use menu option Case | Import to import the existing file brillig-6.data

4 Save the project with File | Save Project.



110 Tutorials ECLIPSE Office 2007.1 User GuideTutorial 6: Adding local grid refinement

Note On sites where the ECLIPSE Flux Boundary option has not been switched on, the FLUX option on the Data Manager: Case Definition | Reservoir panel has to be deselected, and the DUMPFLUX keyword removed from the Data Manager: GRID Section | Subsection | Grid Keywords | Flux Options panel, using the Edit | Delete Keyword option. Data in the Grid Section has to be saved, using the Data Manager: Grid | File Save option.

Insert cartesian LGR

Switch LGR option on in the case definition section1 From the Data Manager panel, select Section | Case Definition.

2 Select the Reservoir tab and activate the Local Grid Refinement and Coarsening (LGR) option.


Note If the option is not available, use the licensing utility on the main ECLIPSE Office panel to establish whether the option has been purchased, and if so, whether the available licenses are currently in use. If not, the SIS @lmstat utility ($lmstat in a DOS shell on a PC) can be activated outside ECLIPSE Office to establish the status of the FLEXLM license manager.

Edit keywords in the grid section1 From the DMM, select the Grid Section.

2 Select Grid Section: Subsection | GRID Keywords.

3 Select Local Grid Refinement from the Keyword Type list.

4 Select Edit | Insert Keyword to display the list of keywords relevant to local grid refinement.

5 Select CARFIN keyword for insertion.

The program distinguishes between local and global grids, using the DOMAIN concept throughout the program. A domain has to be selected each time there is a need to refer to a geological property or physical condition associated with a grid cell.

6 Give the LGR name as CARLU1

The LGR is restricted to a one-cell column in the global grid.

7 Enter the row in the global grid in which the LGR is inserted:

I1(start row) 14

I2 (end row) 14


111

8 Set the global grid column to:

9 Set the layers in the global grid to:

This allows the LGR to reach over all the completion layers for the well LU1.

10 Set the number of local grid cells to be 3 in both the X (I-counter) and Y (J-counter) directions, with NX=3 and NY=3.

11 NZ is the total number of cells in the LGR in the K-direction, and should be an integer multiple of the number of global grid layers included in the LGR; in this case 6 layers.

Insert the number NZ=6, that is the LGR has the same number of layers as the global grid.

NWMAX is the maximum number of wells allowed in this LGR, which in this case is 1.

Hint The input databox for NWMAX is colored. This indicates that it is an optional data field that can be left open, as ECLIPSE calculates a value as required.


Viewing permeability values in the global grid 1 Select Edit | Set LGR/Global domain and select Global from the list.

2 Select Properties from the Keyword Type list.

3 Select PERMY from the Keywords list.

4 Choose menu option Grid Keyword Section: View | Grid Order | XZ-Plane.

5 Move the Plane slider to 8 and click on Apply to advance to the 8th plane.

6 Use the horizontal scrollbar to scroll to the 14th column (X14).

7 Take note of the permeability values in the column (I=14, J=8) where Well LU1 is located.

Inserting permeability values 1 Select Edit | Set LGR/Global domain to display the list of global and local domains.

2 Select the domain to be the local refined grid CARLU1.

3 Choose Grid Keyword Section: Edit | Insert Keyword to display the list of keywords.

4 Select PERMY from the list.

J1 (start column) 8

J2 (end column) 8

K1 (start layer) 2

K2 (end layer) 7


5 Select Grid Keyword Section: Edit | Box and insert the following values:

6 Set the multiplier to 0.95, then use the Operation option Multiply to change the permeability in the immediate region of the borehole.

Inserting LGR permeabilites (PERMX)1 Use Edit | Insert Keyword and select PERMX from the list.

2 Choose Edit | Box

3 Set Operation to Copy

4 Set Copy from to PERMY to copy the values from PERMY to PERMX.


6 Close the Grid Keyword Section, using File | Close.

7 Save the changes to the GRID INCLUDE files using GRID Section: File | Save.

8 Close the GRID section.

Update the Schedule Section with well specifications in the LGR

Note The changes to be made manually in this section can also be imported using the Schedule: File | Import | New option, selecting Yes to clear all data, and importing datafile LGR_SCH_LU1.INC. Ignore the fact that the SCHEDULE keyword is not found by selecting Yes, and then continue this tutorial section from step 3.

Well specifications and completions for well LU1 need to be redefined in terms of the newly created local refined grid CARLU1. To do this:

1 Open the Schedule Section from the Data Manager.

2 Use menu option Schedule Section: Event | View | Well, and select LU1 from the list, to view all the events relevant to well LU1.

3 Select Event | View | All to restore to all events listed.

4 Select Event | New to display the New Event panel.

5 Select Local Grid Refinement from the Event Types list

6 Select Define LGR Well from the Events list.

7 Click on Apply to add the keyword.

K mD

1 1407

2 501

3 102

4 760

5 0

6 2684


113

Hint Click on Toggle Desc/Keys to display the keyword WELSPECL

8 Enter the following information for the LGR Well (WELSPECL)

9 Click on Apply.

Note The sequence of keywords in the Schedule Section is important. Keywords can be moved using the Event | Move menu to move up or down the current list of events, or to a specified timestep.

10 Delete the original WELSPECS event for the well LU1. This keyword is in relation to the global grid, whilst WELSPECL refers to the local grid:

11 Click on the WELSPECS-LU1 event to set the focus.

12 Use the option Schedule: Event | Delete to delete the original WELSPECS data for LU1.

Completions for well LU1 should be declared in relation to the local grid as well, using the keyword COMPDATL, while the COMPDAT-LU1 keyword should be deleted.

Note Use View | Keywords to toggle the keywords on instead of the descriptions.

13 Click on the COMPDAT keyword for all wells starting with LU*, which schedules a completion event for all wells starting with LU to be completed in layers 2 to 5 in the global grid.

14 Change the Well to LU2.


16 Select Schedule Section: Event | New to display all of the events for selection.

17 Select Local Grid Refinement from the Event Types list. Only events associated with this type are now displayed in the Events list.

18 Click on the Toggle Desc/Keys to display the actual keywords.

19 Select COMPDATL from the Events list.

20 Click on OK to add to the Schedule Section.

Well LU1

Group ONE

LGR CARLU1

I Location 2

J Location 2

Datum Depth 7300 ft

Preferred Phase OIL

Inflow Equation STD

Automatic Shut-In Instruction SHUT

Crossflow YES

PVT Property table 2

Density Calculation SEG


21 Insert the following data for the keyword COMPDATL:


Note Note that the I,J,K data refer to the local grid.

23 Repeat the steps for the completion in layer 7 of the global grid:

24 Change COMPDAT (set at Well = LU*, K = 7) to have Well = LU2.

25 Insert COMPDATL with Well = LU1 and completion in K = 6 of the local grid, only:

Lumping of completions, defined by the COMPLUMP keyword, should also be defined in terms of the local grid for well LU1.

Note Again the completions of all LU* wells are lumped in the same way: layers 2 to 5 (global grid) are lumped together, and the completion in layer 7 is handled separately.

26 Click on the COMPLUMP keyword for Well = LU* and completions in layers 2 to 5.

27 Change to Well = LU2.


29 Repeat for COMPLUMP, Well =LU* and completion in layer 7.

Well LU1

LGR CARLU1

I Location 2

J Location 2

K Upper 1

K Lower 4

Open/Shut Flag AUTO

Well Bore ID 0.71 ft

Skin Factor -2

Direction Z

Well LU1

LGR CARLU1

I Location 2

J Location 2

K Upper 6

K Lower 6

Open/Shut Flag OPEN

Well Bore ID 0.71 ft

Skin Factor -2

Direction Z


115

Lumping completions in the local grid1 Select menu option Schedule: Event | New to display the keyword lists.

2 Select Local Grid Refinement on the Events Types list and COMPLMPL from the Events List.

3 Click on Apply twice to insert the COMPLMPL event twice.

4 Insert the data for COMPLMPL:

a First COMPLMPL event

b Second COMPLMPL event

Removing the group control event

Note The group control event GCONTOL cannot be used with LGRs.

1 Click on the Group Control Target Tolerance or GCONTOL in the Events-All list, to make the keyword current

2 Select Event | Delete to remove the current keyword.

3 Select Schedule: File | Save to save all changes to the data.

4 Exit from the Schedule Section using File | Close.

5 Update the case using Data Manager: File | Update.

6 Click on Yes to recalculate the wells.

Select summary vector output with regard to the LGR1 Open the Summary Section from the Data Manager.

Well LU1

LGR CARLU1

I Location 2

J Location 2

K Upper 1

K Lower 4

Completion no 1

Well LU1

LGR CARLU1

I Location 2

J Location 2

K Upper 6

K Lower 6

Completion no 2


2 Select the LBlock tab (click on the arrows at top right to locate it if necessary) to see the list of Summary Vectors related to the local grid blocks.

3 Select the LBOSAT keyword, and Cells (2,2,1) to (2,2,6) to output the Local Block Oil Saturation per timestep of these cells.

4 Click on Add to List Button to add to the list

5 Select the menu tab LWell to display Summary Vectors related to the well completed in the local grid:

6 Click on Add to List to add to the Selected Vectors list.

7 In order to output the gas and water production as well, select and add LWGPR (Phases: Gas) and LWWPR (Phases: Water) for LU1.

8 Add each to the Selected Vectors list.

Listing oil and water flow rates per local completion1 Select the LComp tab to display the lists of keywords related to local completions.

2 Select LCOFR (Local Completion Oil Flow Rate), with I=2, J=2 and K=1 to 6.

3 Click on Add to List for each cell.

4 Select LCWFR (Local Completion Water Flow Rate) for the same local cells.

5 Click on the Selected button in the toolbar to see the list of selected vectors.

The Selected Vectors list should now contain the following additional vectors (see Figure 4.30):

Phases OIL

Types Production Rate

Keywords LWOPR


117

Figure 4.30 Selected Vector List

6 Use Summary Section: File | Save to save the new list to file LGR_sum.inc.

7 Exit the Summary Section, by selecting File | Close.

8 Close the Data Manager with File | Close.

Run the simulation1 Open the Run Manager from the main ECLIPSE Office panel by clicking on the Run

button.

2 Select Run Manager: Submit | Runs to start the simulation .

3 If a warning appears that a .DATA file exists, select Yes to overwrite it.

4 Check the Log window to see the progress on the simulation run.

5 Close the Run Manager once the message Simulations Finished. Timer Stopped appears in the Log window, using File | Close.

Caution Any errors reported during a simulation run that fails should be resolved before continuing. The simulation needs to be repeated until a successful run is obtained.


View the simulation output from the local grid1 Open the Result Viewer from the main ECLIPSE Office panel by clicking on Result.

2 File | Open Current Case | Summary.

3 Tick on the Read All Summary Vectors checkbox.

4 Click on the Load button to execute.

5 Select LinePlot | User to display the User Template panel .

Selecting the Local Grid Oil saturation per block1 Select Time from the X-Axis Vectors list

2 In the Y-Axis Vectors list, type LBOSAT* in the filter box.

3 Multiple-select by clicking on LBOSAT:CARLU1:(2,2,1) and while holding down the Shift key, click on LBOSAT:CARLU1:(2,2,6).

4 Click on the Add to List button.

5 Click on OK to draw the curves selected. (See Figure 4.31)

Figure 4.31 Summary Vectors: Local Block Saturation

6 Select LinePlot | User to display the User Templates panel.

7 From here select: LWOPR, LWGPR and LWWPR to draw the production rates of well LU1.


119

Figure 4.32 Summary vectors: Local Well Production

Hint To change the title of a plot, double-click on the current title. This opens the Title Edit box.

Comparing the well production per completion1 Select LinePlot | User option to display the User Templates panel.

2 Select summary vectors for Y-axis as follows:

The graph displaying the oil production per completion in the locally defined grid CARLU1 is created when you click on Apply.

Note The production in the fifth layer is zero, as no completion exists in this layer of the local grid. Oil production in layer 6 stopped completely between 800 and 900 days, whilst production from the completions in layers 1 to 4 (local grid) was started round about 2000 days, with the highest production rate from layer 1. The same can be done for the water production rate.

X-Axis Vectors

Y-Axis Vectors

TIME LCOFR:CARLU1:LU1(2,2,1)

LCOFR:CARLU1:LU1(2,2,2)






Figure 4.33 Oil Production per completion

2D viewer1 Select Result Viewer: File | Open Current Case | GRID and load the Grid geometry and

solution data. Figure 4.34 Result Viewer module - extract/load solutions


121

2 Select the option Result Viewer: View | 2D to display the simulation solution results in

the 2D Viewer .

3 Select Result Viewer: 2D | Options | Well Display and un-check Only Show Wells Completed in Current Slice. This switches on well labels for all wells in the model.

4 Select 2D | Slice and select Direction=K, Slice Number=2, the top layer in the global grid containing the LGR.

5 Select 2D | Property to display the Property Selector panel.

6 Select SWAT from the Recurrent Property list to view water saturation in the grid blocks around the well.

7 Select 2D | Cross Section | Generate.

8 Position the cursor over the cross-section line on the 2D areal view, and drag the line to cross the block (global gridcell 14,8) in which the well LU1 appears. The cross section view will update.

9 Use option View | Rubberband Zoom In to enlarge the area of the LGR.

10 Deselect Rubberband Zoom In followed by Unzoom Completely to reset the cursor.

11 To see how the LGR is connected to the global grid switch on the NNC (non-neighbor connections) display use 2D | Options | Show NNCs | Cells. In both views this will mark each cell that has an NNC with a triangle.

12 To see the connections between the NNC cells switch on 2D | Options | Show NNCs | Connections. Lines will be drawn between cells that have NNCs showing which cells are connected to which. Also it should be possible to see how the cells around the fault are connected.

13 Select both the above options once more to remove the NNC displays.

14 Use the Next timestep button to step through each timestep, observing the change in water saturation in the local grid around well LU1 in order to detect signs of water coning.

15 Actual values in cells can be obtained with the Cell Probe option and clicking on the cell.

Values for the recurrent properties (per timestep) are displayed in the cell probe panel and the status bar at the bottom of the window.

3D viewer1 Select Result Viewer: View | 3D to activate the 3D Viewer, after the GRID data has been

loaded .

2 Switch cell outlines on if necessary with option 3D: View | Object Appearance | Render

Mode: Cell Outlines .


Viewing the LGR

1 Select option View | Set View | Top to view the grid from the top .

2 Select option Scene | Grid | IJK Slice to display the IJK Slice panel.

3 Select layer 2 from the K-Slicing tab to display the Cartesian grid on well LU1.

The grid displayed should appear as in Figure 4.35:

Figure 4.35 IJK slice grid

In order to view the local grid and the well LU1, the following needs to be done:

4 Switch AutoApply Off, by:

• Click on the IJK Slice panel with the right mouse button, keeping the button depressed

• Drag the cursor down to select the AutoApply option to toggle it between On and Off.

5 Select IJK Slice: Reset All Domains to display the full grid again.

6 Select the IJK Slice: IJK Extents menu tab.

7 Set I Min = I Max = 14 and J Min = J Max = 8

8 Click on Apply.

9 Select View | Set View | User to return to viewing the grid and an angle.

10 Click on the Vertical stretch button several times until the local grid is visible.


123

11 Select 3D Viewer: Scene | Wells and change the height factor to 2 and the width factor to 4 to enhance well symbols.

Note Acceptable values will differ per installation.

12 Turn on the display of Well Status, Connections and Show All Wells.

13 Grid transparency can be changed using the option 3D Viewer: Scene | Grid | Transparency.

Hint Switch AutoApply on.

14 To observe possible water coning effects, select option Scene | Grid | Property

15 Select the Recurrent Property SWAT

16 Select the First Timestep button to set the time to the start of the simulation.

17 Rotate view using the right mouse button to drag the image.

Hint If the image is not fully visible, use the Autonormalize button to reposition and resize the image.

18 Select the Play button .

Figure 4.36 Water Saturation in local grid CARLU1


19 Observe the water saturation changes in the region of well LU1 for the duration of the simulation period.

20 Close the 3D Viewer with File | Close

21 Before closing the Result Viewer you may wish to create a Graphics Run File (GRF) containing all the Line Plot and 2D displays that you have created interactively. To do this, select File | Write GRF and enter a file name in the browser which appears. The next time you open the Result Viewer for this model, you can select File | Open GRF to recreate your pictures.

22 Close the Result Viewer with File | Close.

23 Save the project, using ECLIPSE Office: File | Project Save.

24 Exit ECLIPSE Office using File | Exit.

ECLIPSE Office 2007.1 User Guide TutorialsTutorial 7: Remote job submission

125

Tutorial 7: Remote job submission

ObjectiveThe ECLIPSE Office Run Manager allows you to submit simulation runs on a combination of local and remote machines. One major advantage to this is that the ECLIPSE Office executable can be run on a local machine (a PC for instance) to carry out all the pre/post processing of the data and then the simulation run can easily be submitted remotely on a larger machine.

This tutorial is designed to introduce you to the submission of simulations runs on remote machines. In addition, both the multiple runs capability, and the multiple sensitivities option are used.

This tutorial takes about forty-five minutes to complete.

Stages• "Submitting runs using PVM" on page 126

• "Configuration" on page 126

• "Starting PVM and ECLIPSE Office" on page 127

• "Run simulations" on page 128

• "Monitoring simulation runs" on page 129

• "Submitting runs using Non-PVM Remote" on page 130

• "Configuration" on page 130

• "Creating a new project" on page 130

• "Open schedule section" on page 131

• "Opening a multiple runs or sensitivities panel" on page 131

• "Run simulations" on page 134

• "Result viewer" on page 135

• "Submitting runs to LSF queues" on page 136

• "Requirements" on page 136

• "Method" on page 136

• "Submitting runs with the external job option" on page 138

• "Running from a PC to a UNIX machine using NFS drives and dos2unix, dos2aix or to_unix" on page 138

• "Submitting jobs to LSF from a UNIX machine" on page 143

126 Tutorials ECLIPSE Office 2007.1 User GuideTutorial 7: Remote job submission

Submitting runs using PVMThe PVM (Parallel Virtual Machine) software allows a group of computers connected over a network to be used as a single large computer. This software allows ECLIPSE Office to communicate directly with the simulator it is running, providing the ability to control the simulator and view results as they are produced.

Before beginning this tutorial you need to be sure that PVM is properly installed on both the local and remote machines. "PVM" on page 513 explains the environmental variables which need to be set in order to run PVM, but a brief discussion is also provided here.

Note All examples presented in this tutorial assume that the ECLIPSE and ECLIPSE 300 executables are from the 2005A release, and the ECLIPSE Office executable is 2005A.

ConfigurationIn order to get PVM running properly be sure to set the following variables.

1 On the Local Machine check the following environmental variables are set:

a PVMXDR=TRUE

b PVM_ROOT is set, for example PVM_ROOT=C:\ecl\2005a\pvm3

c PVM_RSH is set, for example, PVM_RSH=C:\WINNT\system32\rsh.exe

d PVM_ARCH is set, for example, PVM_ARCH=WIN32

Hint On the PC you may need to reset PVM_RSH and/or PVM_ROOT in the Registry Editor.

Note For the PC, an rsh.exe must be installed. The installation CD contains Ataman rsh in the utilities directory, which can be used with PVM.

2 On the Local Machine check the pvmhost.2005a (PC) or eclpvmhost.2005a (UNIX) to ensure that it contains the correct executable paths for the simulators. An example PVM host file follows:

Caution In the 2005A PVM host file, you must insert a semi-colon (;) between executable paths for PC hosts and a colon (:) between executable paths for UNIX hosts. Otherwise the application is unable to find the remote executable.

Note The PVM host file is written to the \ecl\home directory on the PC and to your home directory on UNIX machine. This file is created the first time PVM is run.

pc-mjc ep=D:\ecl\2005a\bin\pc

sg-1 ep=/ecl/2005a/bin/sgi


127

3 On the Remote Machine check the following are set in the .cshrc file:

a PVMXDR=TRUE

b PVM_ROOT points to an installed version of PVM. For example,

c LM_LICENSE_FILE is set to the license server

Note Your login shell on the remote machine must be a C-shell.

Starting PVM and ECLIPSE Office4 Start PVM from the ECLIPSE launcher or type @pvm on UNIX machines

Hint It is recommended that you run the version of PVM that corresponds to the ECLIPSE or ECLIPSE 300 version you want to run.

5 To check that your PVM setup is correct, type the command conf at the PVM prompt.

This produces a list machines on the coupled system. If you need to add more machines to the system use the add command as detailed in "PVM" on page 513.

For example, to add a host called sun-comm2, with ECLIPSE executable in the directory /ecl/2005a/bin/sgi use the following command:

6 Use the command quit to exit the PVM console program but leave the PVM daemon running (the halt command kills the PVM daemon and exits the PVM console program).

7 Start ECLIPSE Office from the ECLIPSE launcher.

Note Notice in the Log window the message that reports that PVM is running.

8 Open a new project File | New Project, calling it TUTORIAL.

9 Click on the folder to the left of the project name, with the right mouse button, and add a new case.

10 Double click on the new case and rename it to BLACKOIL.

11 Repeat step 9 to add another two new cases.

12 Rename the new cases COMPOS and ECLIPSE.

13 Click on case BLACK OIL and import a data set using the menu option Case | Import. Import the file: /ecl/2007.1/Office/tutorials/example7/BB_20_20.DATA.

14 Repeat step 7 for COMPOS and ECLIPSE and import data sets respectively

/ecl/2007.1/Office/tutorials/example7/CC_20_20.DATA

/ecl/2007.1/Office/tutorials/example7/EE_20_20.DATA


PVM_ROOT=/ecl/2005a/pvm3

add ‘sun-comm2 ep=/ecl/2005a/eclipse/bin/sgi’


Run simulations1 Select case BLACKOIL and activate the Run Manager from the main ECLIPSE Office

panel by clicking on the Run button, or using the menu option ECLIPSE Office: Module | Run Manager. See "Run manager" on page 38.

2 Select the appropriate Run Environment, in this example PVM

3 Set Add Simulation Resources to 1.

4 Ensure that the Run Time Monitoring Summary check box is ticked.

Note See "Monitoring simulation runs" on page 129 before starting a simulation.

5 Choose Options | Run Environment to open the PVM Environment panel.

6 From the drop down Hosts menu choose the name of the machine you want to submit the run on.

7 Check that the appropriate executable name appears, in this case e300.exe.

Note It is essential that the file pvmhost.2005a (on the PC) and eclpvmhost.2005a (on UNIX machines) has the correct executable path for the simulators on the remote machine.

8 Give a Host Temporary Path.

This is a directory on the remote machine where you have write permissions. Temporary files are stored in this directory during the simulation run. If the box next to Remove remote host files is ticked, then the simulation input and output is deleted from the remote machine after the run.

Note The default Host Temporary Path is /tmp/.

9 Submit the simulation run by choosing the toolbar button or selecting the menu item

Submit | Runs .

Messages about the run status appear on the screen in the Log window.

Hint If the message Error:Error opening log file appears in the Log window, this indicates that you do not have write permission to the Host Temporary Path specified in step 8.

10 Repeat for cases COMPOS and ECLIPSE and try submitting on various different machines.

Caution Be sure to set Add Simulation Resources to 1 in each Run Manager panel.


129

Monitoring simulation runsAs soon as the first summary time/report step message Summary step for run 1 appears in the Log window on any of the modules, the Monitor | Summary Vectors menu item is available. This means the results start to arrive back from the simulators to the Run Manager.

1 Open the Summary Vector module using the toolbar button or the menu item Monitor | Summary Vectors in each run module.

2 Display the Field Production Rate on each window, using the menu option Summary Vectors LinePlot | Field | Production Rate.

The summary vectors are updated at each time/report step arrived from the simulator to the Run Manager.

3 Select LinePlot: Well | Production Rate for all simulations for well P9.

Note You can control the runs, holding or killing the run with Run Manager: Monitor | Control Simulations... or the button.

Figure 4.37 Summary Vectors for the three completed runs

4 Save and close this project.


Submitting runs using Non-PVM RemoteThe Non-PVM Remote option for running the simulators from ECLIPSE Office allows you to submit jobs from a PC (NT/98/2000) to the local network environment. The requirements for getting such submission to work are detailed below.

ConfigurationThere are several things that must be done to ensure that the ECLIPSE simulator can be run on a remote host.

On the remote host1 Check that your login shell is a C-shell.

2 Check that you can execute ECLIPSE on the remote host by trying the @eclipse command.

3 Create or update the .rhosts file in your home directory. Either add + + to allow access to all machines on the local network or insert the name of the specific machine you wish to allow access.

4 Make sure that no version of PVM is running on the remote machine.

On the local host5 It is strongly recommended that you have the same login on both the local and remote

machines. However, if you have a different login on the remote host the following changes must be made to the Win.ini file:

If this appeared in Win.ini, the local user name would be test and WinsockRCP and WinsockRCMD uses this name at the remote host.

Caution Making these changes on Windows 98/2000 machines may cause serious problems and is therefore not encouraged.

Creating a new project1 In the main ECLIPSE Office panel choose File | New Project, calling it NONPVM.

2 Use Case | Import to import the existing file BRILLRST.DATA.

This is a restart run based on the output from a previous simulation. The current run starts from the second report step of the previous simulation. This is indicated by the RESTART keyword in the Data Manager: Initialization Section.


[RCMD]

User=test

[RCP]

User=test


131

Open schedule sectiona Open the Data Manager from the main ECLIPSE Office panel by selecting the Data

button, or using the menu option Module | Data Manager.

4 Select the Schedule Section.

5 Insert the Production Well Control (WCONPROD) keyword by selecting the Event | New option to display all keywords.

6 Select Well Controls and Limits from the Event Types list.

7 Select Production Well Control from the Events list.

8 Click on OK to insert

9 Insert the following data into the WCONPROD keyword and click on Apply:

Opening a multiple runs or sensitivities panelThe details of the Multiple Runs and Multiple Sensitivities panels are presented below. For the purposes of this tutorial please continue with Step 1. You can vary the WCONPROD parameter values for different runs by selecting one of the two buttons:

Multiple runs 1 Selecting this option opens a panel as shown in Figure 4.38:

Well U*

Open/Shut Flag AUTO

Control THP

Oil Rate 20000

Water Rate 20000

Gas Rate 20000

Liquid Rate 30000

Reservoir Volume 50000

BHP Target 2000

THP Target 200

VFP Table 1

ALQ Default


Figure 4.38 Multiple Runs panel

2 Stretch the panel to get the required number of rows in the table, three rows in this case.

Each row represents a run. The parameter names are listed at the top of the table, for example Oil Rate. The first row in the table is the base run where all the values of the parameters are displayed.

3 Now fill the cells with the required values. Empty cells take the default base run values.

4 Click on the OK button to save these values and exit the panel.

5 From the File menu select Save or Save As to save the changes in the ECLIPSE Office MULT INCLUDE file NONPVM_MULT.INC.

Hint If the panel is displayed again the selected values are shown and they can be edited again.

Multiple sensitivities1 Selecting this option displays a panel as shown below:


133

Figure 4.39 Multiple Sensitivities panel

This panel is different from the above one if the you want to select a range of values for each parameter.

2 Start by typing in the number of runs required (3 in this example).

3 The first column in the panel is the keyword Parameters name. The second column is the corresponding values of the base run.

4 The third and fourth columns are the lower and upper limits respectively. The limits should be typed in for the parameters that are to be varied. The empty limits take the default values.

5 Click on the OK button to save and calculate the mean values for the selected parameters.

6 From the File menu select Save or Save As... to save the changes in the ECLIPSE Office MULT INCLUDE file Nonpvm_MULT.INC.

The same steps can be repeated with other keywords and different time steps.

Note Note the Sensitivities section in the main ECLIPSE Office window appears with the number of runs.

Multiple sensitivity data1 Select the Sensitivities button.



a Number of Runs - 3

3 Click on OK to commit the data

4 Select Schedule Section: File | Save and accept the default filenames.

The program writes two files, the Nonpvm_sch.inc file and the Nonpvm_mult.inc file.

5 Close the Schedule Section with File | Close.

6 Close the Data Manager with File | Close.

Run simulations1 Activate the Run Manager from the main ECLIPSE Office panel by clicking on the Run

button, or using the menu option Module | Run Manager. See "Run manager" on page 38.

2 Select NON-PVM REMOTE from the list of possible Environments.

3 Set Add Simulation Resources to 3 (this should not exceed number of runs).

4 Choose Options | Run Environment, and on the Simulation Resources panel specify the name of the remote host(s) that the runs are submitted on

5 Click on the OK button, which opens the NON-PVM Remote Environment panel where you choose the following:

a Hosts from the drop-down menu

b Executable Names

c Parameters

d Host Temporary Path

e Whether or not to remove files from the remote host.

Note The temporary host path is the name of the directory where ECLIPSE Office copies all the data necessary for the simulation run. You must have write permission in this directory. If Remove files is chosen, then all the data and results for the simulation are deleted from the remote host after the transfer back to the local machine.

6 Choose Run Manager: Submit | Runs to set the simulation running on the remote machine(s).

Parameter Value Lower Upper

Oil Rate (stb/day) 20000 10000 60000

Water Rate (stb/day) 20000

Gas Rate (Mscf/day) 40000 10000 40000

Liquid Rate (stb/day) 30000

Reservoir Volume (rb/day) 50000

BHP Target (psia) 2000 1000 5000

THP Target (psia) 200 150 250


135

Note Currently NON-PVM REMOTE does not allow for runtime monitoring of summary or solutions data.

Result viewer1 Once all the simulations are completed, activate the Result Viewer from the main

ECLIPSE Office panel by clicking on the Results button.

2 Select Result Viewer: File | Open Current Case | SUMMARY and select all 3 files.

3 Click on OK to read.

4 Select the Read All Summary Vectors and All Reports options on the Extract panel.

5 Click on the Load button.

6 Select LinePlot | User to display the User Templates panel.

7 Select the following reports:

8 Click on OK to draw the graph, and close the User Templates panel.

The following graph (see Figure 4.40) is produced, showing the oil production for each simulation run:

Figure 4.40 Summary Vectors: Field Oil Production

9 Select Result Viewer: File | Close

10 Select ECLIPSE Office: File | Save Project

11 Select ECLIPSE Office: File | Close Project.

File NONPVM_E100_1

X-Axis Vectors TIME

Y-Axis Vectors FOPR


Submitting runs to LSF queuesThe LSF Run Environment option allows you to send simulation runs to the LSF queue. This section details the requirements to correctly set up and access the LSF Run Environment panel in ECLIPSE Office. The limitations, see "Limitations" on page 138, of this run environment are also discussed.

RequirementsThis section describes the requirements for running ECLIPSE Office on a PC and submitting the ECLIPSE job to an LSF queue on a UNIX machine.

1 The ECLIPSE Office project must be in a directory, which is shared by both machines, so that the same physical disk space is used by both the PC applications and the UNIX simulators.

2 This directory may contain an LSF.CONFIG file or have the location of the LSF.CONFIG file in the ECL.CFG file (Refer to "Result Viewer" on page 494).

Method1 Create an LSF.CONFIG file. This file contains information about the queues that are

available and the location and versions of the simulator executables. An example is included in your standard installation /ecl/2007.1/office/tutorial7/LSF.CONFIG, and is further explained in Appendix G.

2 Start ECLIPSE Office on the PC, and create a new project in the shared directory

3 Import a data set into this ECLIPSE Office project, and then save the project

4 Open the Run Manager panel, and select LSF from the drop-down menu of run environments.

5 Select Options| Run Environment to open the LSF panel (see "LSF environment panel" on page 137)

Note In the LSF.CONFIG file, each version must be unique. ECLIPSE Office gives a warning in the Log window if this file contains duplication of versions.


137

Figure 4.41 LSF environment panel

6 On the LSF Run Environment panel, select the Queue, Version, Architectures and Executable you wish to use. All the fields in yellow can be defaulted.

Caution When submitting jobs from the PC you must fill in the Path section of this panel. Here you should enter the UNIX pathname to ensure that ECLIPSE can find the data set.

7 Select OK on the panel


Hint The Run Manager remembers the setting that you have chosen on the LSF Run Environment panel. These are included in the ECLIPSE Office project file when you next save it.

8 Select Go on the Run Manager panel.

ECLIPSE Office writes the bsub command to the Log window.

The ECLIPSE run should now be in the queue that has been selected. Various LSF commands, such as bqueues, can be used to monitor the run.

LimitationsThere are several limitations in the use of ECLIPSE Office with LSF.

• In this tutorial we demonstrate runs that are executed in a shared directory. A facility for moving the data between machines has been introduced in the 2004A release, but this requires system installation.

• Messages about the progress of the job (pending, running, finished or killed) are written to the log window. However, there is no run-time monitoring of the simulation output available.

• There is no way to kill the simulation job using the ECLIPSE Office Run Manager panel. This can only be done using LSF commands, such as bkill.

• A LSF.CONFIG file may be in the shared directory or in a central place with its location specified in the ECL.CFG file. (Refer to "Result Viewer" on page 494).

Submitting runs with the external job optionThe external job option for running the simulators from ECLIPSE Office provides open access to tailor the submitted job to the local network environment. This tutorial provides an example scenario for typical environments. It is important to remember that local conditions must be taken into consideration when setting up such jobs.

Running from a PC to a UNIX machine using NFS drives and dos2unix, dos2aix or to_unixThis describes a set-up for running the pre- and post- processors on a PC and submitting the ECLIPSE jobs to a UNIX machine.

Requirements1 The UNIX machine must have dos2unix (SUN), dos2aix (IBM), or to_unix (SGI)

2 The directory on the UNIX machine must be mapped to an NFS network drive on the PC, so that the same physical disk space is used by both the PC applications and the UNIX simulators.

3 The PC must have rsh.exe.


139

Method1 First address the problem of converting DOS files to UNIX files.

The PC writes out ASCII files that a UNIX program does not recognize. This is due to the end-of-line character used by the PC. The dos2unix/dos2aix/to_unix program converts text files written by a PC into text files that are UNIX-readable.

The following C-shell script is an example of performing the necessary dos2unix commands for ECLIPSE Office files:

In this example, this file is called @all_dos2unix. This runs on the UNIX machine and must be available in the PATH on that machine.

2 The next step is to write a DOS *.bat file to handle the arguments that ECLIPSE Office sends to it.

As default, the following command is sent by ECLIPSE Office:

Where:

\\full\path\on\PC is the full path to the working directory on the PC.

PROJECTNAME_E100 is the name of the ECLIPSE data set to be run.

In this example it is assumed that the working directory is shared as an NFS network drive, so the -path parameter can be discarded. However, the script needs to know the name of the machine, so a -machine parameter must be recognized.

#!/bin/csh -f

# (-f) suppresses the .cshrc file in the new C shell...

# Avoid problems with aliases set up by users

#

unalias mv

# Run the foreach loop below with .DATA, .data, .DAT

# .dat .INC and .inc extensions (*.H* and *.h* are

# for SimOpt’s include files)

foreach i (`ls *.data *.DATA *.DAT *.INC *.inc *.H* *.h*`)

dos2unix $i > tempfile.txt

mv -f tempfile.txt $i

end

batch_file.bat -data \\full\path\on\PC -file PROJECTNAME_E100


The following PC *.bat file parses the values ECLIPSE Office sends and generates the correct remote shell (rsh) command to execute the run:

@echo off

REM

REM NAME:

REM $jobonunix.bat

REM

REM PURPOSE:

REM Submits jobs to UNIX machine from a PC running Office

REM via the "External Job" option

REM

REM HOW TO RUN:

REM Set the run-type to "External Job" and use the -machine

REM parameter to give the machine name

REM Set-up the UNIX filespace as an NFS drive on the PC

REM Write the Eclipse files to the UNIX filespace

REM NOTE: This script requires the presence of dos2unix

REM on the UNIX machine

REM

REM FLAGS:

REM The following flags are accepted as arguments:

REM -file the Eclipse data file

REM -ver the version of Eclipse (e.g. 99a_1)

REM -machine the UNIX machine name

REM NOTE: All other flags are read but then ignored

REM NOTE: Office writes out -ver and -file as default

REM so you only need to add -machine

REM

REM STRUCTURE:

REM This script is effectively composed of 2 parts:

REM 1. SWITCH statement block - this performs an equivalent

REM job to "switch" in C or Java. It parses the command

REM line arguments.


141

REM 2. execution block - this submits the job on the

REM UNIX machine

REM (after converting the files using dos2unix)

REM =====================================

REM Start of SWITCH block

REM =====================================

REM Loop around all passed arguments

:ChkArgs

if "%1"=="" goto AllChkd

REM check for -machine

if "%1"=="-machine" goto Machine

if "%1"=="-MACHINE" goto Machine

goto NotMachine

:Machine

shift

if NOT "%1"=="" set machine=%1

shift

goto ChkArgs

:NotMachine

REM check for -ver

if "%1"=="-ver" goto Version

if "%1"=="-VER" goto Version

goto NotVersion

goto NotVersion

:Version

shift

if NOT "%1"=="" set version=%1

shift

goto ChkArgs

:NotVersion

RREM check for -file

if "%1"=="-file" goto File

if "%1"=="-FILE" goto File

goto NotFile


The final step is to set up ECLIPSE Office or SimOpt to run the job. The following steps set the Run Manager in ECLIPSE Office to execute the script:

1 In the Run Manager set the Environment to External Job.

2 Run Manager: Options | Run Environment...

3 Set the Executable to your script name (for example $jobonunix.bat)

4 Set the Simulator Parameters to the include the machine name and the version (for example -machine myunixbox -ver 2005a).

5 Now run simulations as usual.

shift

if NOT "%1"=="" set file=%1

shift

goto ChkArgs

:NotFile

REM Cover ourselves by handling any unexpected arguments

REM by ignoring them - they are put to into the ignore variable

set ignore=%1

shift

goto ChkArgs

REM

REM All arguments handled

REM

:AllChkd

REM =====================================

REM End of SWITCH block

REM =====================================

REM =====================================

REM Start of execution block

REM =====================================

rsh %machine% @all_dos2unix

rsh %machine% @eclipse -ver %version% %file%

exit

REM =====================================

REM End of execution block

REM =====================================


143

Hint If you run with non-unified output, ECLIPSE Office can provide run-time monitoring by way of the SUMMARY vectors.

Submitting jobs to LSF from a UNIX machineThis describes a set-up for submitting ECLIPSE jobs to an LSF queue from a UNIX machine.

The following C-shell script allows a job to be submitted to an LSF queue:

#!/usr/bin/csh

#

# NAME

# @lsf

#

# PURPOSE:

# Sets up a job to run under lsf

# because the full executable path is specified (-exec)

# any simulator can be run using this script.

## FLAGS:

# The following flags are accepted as arguments:

# -file the data file

# -exec the full path to the executable

# NOTE: all other flags are read but discarded.

#

# Store the command line arguments in local variables

# the arguments should be -argument_type argument

while ($#argv)

s

switch ($1)

case -exec:

if ($#argv == 1) breaksw

shift

set ecl_exec = $1

breakswcase -file:


shift

set ecl_file = $1

breaksw


When running this script the command line arguments are:

• -exec the full path to the executable (that is not the @eclipse macro but eclipse.exe).

• -file the name of the ECLIPSE file to be executed (this is supplied as default by both ECLIPSE Office and SimOpt).

default:


set ecl_file = $1

shift

endsw

if ($#argv >= 1) shift

end

# Now we have extracted the file and exec names, run the job

bsub $ecl_exec $ecl_file

ECLIPSE Office 2007.1 User Guide TutorialsTutorial 8: Using property correlations

145

Tutorial 8: Using property correlations

IntroductionECLIPSE Office includes industry-standard correlations for the generation of fluid properties. This tutorial describes how oil, water, gas and rock properties can be generated using correlations and included as keywords in a simulation.

This tutorial takes about thirty minutes to complete.

Stages• "Importing an existing data set" on page 145

• "Generating fluid and rock properties by correlation" on page 146

• "Viewing PVT keywords graphically" on page 147

• "Saving the keywords" on page 149

• "Updating Correlation Values" on page 149

• "Running the simulation" on page 149

• "Discussion" on page 150.

Data preparationThe files used in this tutorial are:

pvt_tutorial.data

GRID1.GEC

PERMX.GEC

PORO.GEC

They are located in

/ecl/2007.1/office/tutorial/example8/

and should be copied to the working directory before beginning the tutorial.

Importing an existing data setTo begin with a existing ECLIPSE data set is imported. This simulation data set does not contain any oil, water, gas or rock property information.

1 Start ECLIPSE Office.

2 ECLIPSE Office: File | New Project...

3 Call the project PVT.off.

4 Case | Import...

146 Tutorials ECLIPSE Office 2007.1 User GuideTutorial 8: Using property correlations

5 Import pvt_tutorial.data

6 Select ECLIPSE as the Simulator Type.

7 File | Save Project

8 Module | Data Manager...

9 Data Manager: Section | Case Definition...

10 In the Case Definition Section panel, select the PVT tab.

This shows that the simulation model contains oil (with dissolved gas), water and gas. The properties of these are determined in this tutorial.

11 Click on OK to close the Case Definition Section panel.

12 Data Manager: Section | PVT...

Generating fluid and rock properties by correlation1 PVT Section: Section | Keywords...

The PVT Keywords panel shows the default (empty) set of PVT tables, PVT1.

Steps 2–7 (illustrating how empty keywords can be inserted) are optional, as the default keywords will be automatically inserted on viewing the correlations.

2 PVT Keywords: View | Keywords

a PVT Keywords: Edit | Insert Keyword...

b Select DENSITY

3 PVT Keywords: Edit | Insert Keyword...

a Select PVTO


a Select PVDG


a Select PVTW

6 Click Edit | Explore Keywords to open the Explore Keywords panel. Click Toggle Desc/Key once to switch to keyword view if not already in that view.

a Select ROCK

Now that the blank keywords have been created, they can be filled using the correlations.

Hint If no PVT keywords are available, empty keywords appropriate to the defined fluid phases will automatically be created when you view the correlations.

7 PVT Keywords: View | Correlations.


147

Hint The entry fields are configured according to the chosen correlations. There are 2 sets of correlations (Set I - 2005A release onwards and Set II - prior to 2005A release). The default correlation set selection is Set I. However this tutorial is based on Set II, and hence this option needs to be selected whenever this screen is encountered. The default correlations are applicable in a wide range of circumstances. If you wish to specify the set of correlations for your region you can select the correlations by clicking on the Advanced... button.

The inputs are filled with typical default parameters. Most of these can be left at their default settings.

8 Verify, and if necessary change, the entry fields shown in Table 4.3.

9 Click on Apply.

10 PVT Keywords: View | Correlations.

a Verify that the keywords have been filled by the correlations.

Viewing PVT keywords graphicallyThe gas (PVDG) and oil (PVTO) keywords contain tables of values. ECLIPSE Office provides a graphical view of these keywords.

1 PVT Keywords: View | Plot...

The PVT_E100 window provides a graphical plot of the oil and gas keywords (Figure 4.42).

Table 4.3 Information for the correlations

Item ValueOil Gravity 32 API

Gas gravity 0.7 sg_Air_1

Input choice GOR

Gas oil ratio 300 scf /stb

Reservoir temperature 200 C

Reference Pressure 400 bar

Minimum Pressure 20 bar

Maximum Pressure 500 bar

Output table length 20


Figure 4.42 The PVT_E100 panel showing the PVTO (live oil properties) keyword as a plot

2 Double-click on the PVDG plot to make it the main plot (Figure 4.43).Figure 4.43 The PVT_E100 panel showing the PVDG (dry gas properties) keyword as the main plot


149

3 PVT_E100: File | Close

Closes the Plot window.

4 PVT Keywords: File | Close

Closes the Keywords section.

Saving the keywords1 PVT Section: File | Close

2 Click on Yes to confirm that changes should be saved, selecting the option to overwrite the existing (empty) PVT file with the keywords generated from the correlations.

3 Click on OK to overwrite the existing PVT and Regions file.

Updating Correlation ValuesThis part of the tutorial demonstrates the ability to switch between the correlations view and the view of the keywords. This is particularly useful when the information used in the correlation inputs has changed.

Hint The comments stored with the keywords contain all the information required to restore the correlation library. This means that a round-trip workflow is available. The keywords can be updated for changing oil gravity, for example, without having to locate and re-enter all the other information.

1 Data Manager Module: Section | PVT...

2 PVT Section: Section | Keywords...

3 PVT Keywords: View | Correlations...

Note The correlation information is restored as entered in "Generating fluid and rock properties by correlation" on page 146. In the current release the correlation parameters are always shown in Field units.

4 Change the oil gravity to 35 APIoil.

5 Click on Apply

Running the simulationNow that oil, water, gas and rock properties have been defined, the simulation can be run.

1 PVT Section: File | Close

Save the results of the updated correlations.


3 Module | Run Manager...

4 Run Manager Module: Submit | Runs


Note The simulation may take a few minutes to run.

Hint The results of simulation can be viewed using the Result Viewer, as described in "Tutorial 2: Building a model" on page 45.

DiscussionFluid properties were generated using the correlations in ECLIPSE Office. This completed the simulation model so that the simulation could be run.

The correlations offer a method for creating consistent sets of black-oil tables from limited surface information. ECLIPSE Office provides full round-trip handling of PVT regions created in this way, the correlation set-up being interchangeable with the keyword tables. There is a strong level of protection, through warnings to the user, to prevent accidental over-writing of keywords by the correlations.

ECLIPSE Office 2007.1 User Guide TutorialsTutorial 9: Using PEEP

151

Tutorial 9: Using PEEP

IntroductionThis tutorial describes how to use ECLIPSE Office to prepare ECLIPSE simulator output for the PEEP economics tool. It covers generating PEEP script files and how to use the ECLIPSE-to-PEEP link.

Stages• "Generating PEEP script files" on page 151.

• "How to generate files" on page 152

• "Instructions for using the ECLIPSE to PEEP link" on page 158.

• "Importing ECLIPSE data" on page 160.

• "Running the Case" on page 161.

• "Calculating incremental value" on page 162.

Data preparationThe data for this tutorial can be found in the standard installation directory /ecl/2007.1/office/tutorials/example9. You should prepare the data by importing the data set BRILL21.DATA and performing a simulation run. The details of how to prepare the ECLIPSE results for PEEP are described in the following section.

Generating PEEP script files

OverviewThis section of the tutorial contains instructions for generating PEEP script files (*.CIP) from ECLIPSE summary files (*.SMSPEC) using ECLIPSE Office.

For each quantity you wish to report in the .CIP file you need a corresponding vector in your summary file:

Table 4.4 Quantities and their corresponding vectors

Quantity Summary VectorOil Production FOPR or FOPT

Water Production FWPR or FWPT

Gas Production FGPR or FGPT

Water Injection FWIR or FWIT

Gas Injection FGIR or FGIT

152 Tutorials ECLIPSE Office 2007.1 User GuideTutorial 9: Using PEEP

How to generate files1 Start ECLIPSE Office

2 Go to the Report Generator module

3 File | Open SUMMARY | Load all vectors, and select the summary file you wish to use

4 Select Economics from the Report drop-down listFigure 4.44 Report Generator module, General tab

5 In the General tab, specify the Case Name and the frequency at which you want data to be reported (Monthly or Yearly).

Number of Production Wells Operating FMWPR

Number of Injection Wells Operating FMWIN

Number of Wells Drilled FMWDR or FMWDT

Number of Workovers FMWWO or FMWWT

Table 4.4 Quantities and their corresponding vectors (Continued)

Quantity Summary Vector


153

We recommend that you leave the Model Name defaulted to ECLIPSE and the Global Parm Name set to ECLIPSE Default. However, you may change the Model and Global Parm Name to any valid PEEP parameters (see the PEEP documentation for further information).

6 Select Field to create an economics report base on field wide data. You can also create reports for individual wells or groups.

Specifying the vectors1 In the Production tab, use the first column of input to specify the vectors you wish to use

to calculate the reported quantities. Leave it empty for quantities you do not wish to report in the .CIP file. Use the second column to specify whether you want to report Rates or Volumes in the .CIP file.

For example, in Figure 4.45, the vector FOPR is used to calculate and report oil production volumes; FGPT is used to calculate and report gas production rates. Water production, water injection, and gas injection are not reported. FMWPR and FMWIN are used to output the number of production and injection wells that are operating, respectively. When reported, the injected gas quantity is always output as volume.


Figure 4.45 Production tab


155

2 In the Price tab, specify the oil and gas price that are reported in the .CIP file.

There are four methods for specifying the price:

Table 4.5 Methods for specifying price

Method DescriptionIgnore Use this to prevent output of the Oil/Gas Price parameter in the .CIP file.

Name Use this to specify a Name for a parameter that is stored in PEEP’s database (for example Oil Price, Gas Price).

Array Use this to specify Oil/Gas Price versus Time. After generating the report, ECLIPSE Office creates an array where you can manually enter time-varying values for the Oil/Gas Price

Single Value Use this to specify a constant value for the Oil/Gas Price.


Figure 4.46 Price tab

3 In the OpCost tab, specify the operating cost quantities that you wish to export to PEEP.

Note OpCost uses the same methods for specifying costs as those used by Price for specifying prices.

4 In the CapEx tab, choose the vectors you want to use to calculate the number of drilling and workover events. (You may also opt not to report these quantities.) Also, specify the drilling and workover cost.


157

5 Click on the Generate Report button at the bottom of the Input panel to calculate and report the quantities that you requested.

Note This does not create the .CIP file. It generates an output panel where you can examine the reported quantities before finally writing them to the .CIP file.

Viewing the report1 Click on Output at the top of the Report Generator to go to the Output panel and check

the report.

Note At this point, if you have used the Array method to specify prices/costs in either the Price tab or the OpCost tab, you need to fill in the array(s) that ECLIPSE Office created for you. There will be a table, with columns for the arrays you have requested, in the respective tabs.

Figure 4.47 Output panel, showing the report


Generating the CIP file1 Click on Write to write the .CIP file.

2 In the Write PEEP File panel, specify the location and name of the .CIP file and click on Save.

Instructions for using the ECLIPSE to PEEP link

Setting up PEEPBefore importing data from ECLIPSE into PEEP, it is necessary to ensure that there is a suitable model available within the PEEP database. This model must contain the elements that ECLIPSE populates. A default model for calculating before-tax cashflows is available in the import file /ecl/2007.1/office/tutorials/example9/Eclipse.pex.

Importing the pex file into PEEP1 Start PEEP

2 Select the Import/Export tab from the document select window, and open the PEEP docs from file option

Figure 4.48 Import/Export tab

3 On the Import panel, select the Load Import File button and locate the Eclipse.pex file.

4 Click on Start Import to import the data into PEEP.

Caution It is possible that there may be data in the import file that conflicts with information already in the database. If this occurs, a message is shown and you can choose to overwrite the data or keep the original.


159

Figure 4.49 Importing PEX file

Report template fileTo ensure that reports are always generated when the case is calculated, a report template file needs to be specified.

1 Open the Edit | Preferences dialog or use the button on the toolbar

2 Select the Reports tab and click on Select...

3 Navigate to the location of the eclipse.prt file and select it. This file is located in the directory /ecl/2007.1/office/tutorials/example9.


Figure 4.50 Reports tab

4 Click on Apply to save your changes.

This file defines that a summary report and a detailed Revenue and Cost report is generated for all the information coming from ECLIPSE.

Importing ECLIPSE dataWhen a suitable model is available in the PEEP database, ECLIPSE data can be imported into PEEP, to create cases.

1 After creating the appropriate file from ECLIPSE, select the Import/Export tab in PEEP, and open the Case script files option.

Figure 4.51 Importing Case scripts


161

2 Use Select Directory... to select the directory where the import scripts are located. The last directory used is automatically shown.

3 Select the file(s) to be imported and choose the model and Global parameter document name that you want associated with the imported data.

4 Click on Convert to bring the data into PEEP.

5 After the import has finished, inspect the Error Log tab to verify that there were no problems in the import process.

Figure 4.52 Script import

Running the CaseNow that the data is imported, you can calculate the case and produce the cashflows.

1 Select the Cases tab, and open the case that was importedFigure 4.53 Running the imported case


2 When the case is displayed, extra data can be added if appropriate and then the case calculated using the toolbar button , or the Options | Calculate option.

If the steps described above in the setup process have been followed, the reports are automatically generated. You can then view and print them.

Calculating incremental valueThe ECLIPSE to PEEP link can easily be used to determine the incremental value of a development scenario. A consolidation document is created that allows the base project cashflow values to be subtracted from those of the development scenario.

1 Create a case for both the base and development scenario and import it into PEEP as shown above.

2 Select the Group documents tab.

3 Create a new consolidation document by right-clicking in the window area and selecting the New Document option, or by using the File | New option.

4 Select the two cases that form the base and the development scenario, and move them over to the right list. The order is unimportant.

5 To subtract the base case, select the base case in the right list, and select Factor...

6 When prompted, enter −1 for the factor.

7 Select the Settings side tab, and set the Model and Global parameter documents. This ensures that the correct factors are used for discounting the cashflows, and that the appropriate reports are generated.

Figure 4.54 Parameter settings for cashflow discount calculations

8 Calculate the consolidation and view or print the reports.

Hint This is done in the same way as for a single case.

ECLIPSE Office 2007.1 User Guide TutorialsTutorial 10: Using the Coal Bed Methane template

163

Tutorial 10: Using the Coal Bed Methane template

ObjectiveThe aim of the tutorial is to familiarize you with the main features of the Coal Bed Methane Template workflow, from model generation through running the simulation to results viewing. The tutorial demonstrates how a simulation model may be built quickly using the template. Where feasible, the input data are preassigned default values, to facilitate this process.

Problem descriptionIn this tutorial you will build a number of models. These are taken from the “Numerical Simulator Comparison Study for Enhanced Coalbed Methane Recovery Processes”, by D.H. Law et al, SPE 75669.

We first model primary recovery using a single well quarter model. This is extended to include CO2 injection in a quarter 5 spot model using the ECLIPSE Solvent model. This is then duplicated and the solvent model is replaced with a full compositional treatment. The effect of rock compaction is also considered.

Stages• "Workflow" on page 165

• "Reservoir Description" on page 165

• "Wells" on page 166

• "Production" on page 167

• "Fluid Properties" on page 168

• "Simulation Controls" on page 168

• "Running the Model and Viewing the Results" on page 169

• "Extended CBM using CO2 Injection with the ECLIPSE Solvent Model" on page 169

• "Extended CBM using CO2 Injection with the ECLIPSE Compositional Model" on page 171


164 Tutorials ECLIPSE Office 2007.1 User GuideTutorial 10: Using the Coal Bed Methane template

Getting started

Note You may need to edit your config.ecl file (under /ecl/macros) to enable the Coal Bed Methane Template. Under the SECTION OFFICE add the following lines:

SUBSECT MODULESCBM TRUECBM-GRF d:/ecl/2007.1/office/coalbedmethane.grf

1 Start ECLIPSE Office from the ECLIPSE Launcher.

2 From the top menubar select File | New Project and assign this project the name cbm.off.

3 Select Case | Add Case | Template.

The Template Model Selection panel will be displayed.

4 Set the Case Name to cbm-1.

5 Select the Coal Bed Methane Model.

Click on OK to open the coal bed methane template editor.

The Coal Bed Methane Model user interface consists of two windows:

WorkflowThe first window is the workflow interface with which you can change the features of the coal bed methane model. You can select each stage in the workflow using the radio buttons, and navigate through each of the pages defining the selected workflow stage using the <<Previous and Next>> buttons (where applicable).

DisplayThe second window is a display of the current reservoir model. This model may be updated at any time using the Generate Model button on the workflow window. A simulation grid is automatically created which honors the features of the model. When one or more wells have been defined, the location of the wells will also be included in the reservoir model display. By default, automatic gridding is applied to the reservoir according to the well locations, the phase contact depths and the presence or absence of additional features such as fractures. In general, grid refinements are applied in the vicinity of these physical features. In consequence, the displayed reservoir grid may change during the process of data entry as various values are entered or modified. Note that grid refinements in the vicinity of the well will only be applied if the well completions have been specified.


165

Workflow

Model DefinitionThe first workflow page contains the general model definitions. The model is defaulted to consist of Gas and Water. The only other option currently available with coal bed methane models is gas only. The ECLIPSE simulator will be used for modeling the reservoir behavior as a function of time. By default, a single set of initial conditions is assumed to apply to the entire reservoir. Equilibrium initialization will be employed, and the gas is assumed not to contain either ash or moisture. These three default conditions may be modified by selecting the check boxes.

1 Tick the checkboxes to indicate that:

a the model employs non-equilibrium initialization

b the coal is defined on a unit weight basis with ash and moisture content.

Reservoir DescriptionThe second workflow page provides access to the reservoir description. This consists of five data entry windows which are described below. In these windows, data entry fields which are colored yellow signify that if a value is not supplied by the user, a default value will be provided automatically. Data entry fields which are colored white require a value to be entered by the user.

Layers The Layers data entry window specifies the reservoir dimensions and location with respect to sea level.

1 Enter the following values:

2 After entering these values, click on Apply.

The reservoir system employed by the coal bed methane template is top-left-back. The above set of data defines a rectangular reservoir of dimensions 165 x 165 x 30 ft with the depth of the top of the layer at 4113 ft below sea level.

Layer Name: Layer1

Rock Name: (No entry, this will default to “RESERVOIR”)

Top Depth Left (ft): 4113

Top Depth Right (ft): 4113

Horiz Disp (ft): 0

Thickness (ft): 30

Length (ft): 165

Width (ft): 165


Rock Properties Coal beds consist of dual porosity systems. The primary porosity system (matrix) contains the bulk of the gas, whereas the secondary porosity system (natural fracture) provides the interconnection mechanism within the reservoir and with the well bore for fluid flow. The matrix is assumed to be impermeable; the gas storage mechanism is adsorption under pressure, such that gas is desorbed when the pressure is reduced. Darcy flow is used to model gas movement through the natural fracture system.

The Rock Properties data entry panel specifies the rock properties for the coal bed methane fracture system. The matrix porosity is determined from the fracture porosity and the matrix permeability is assumed to be zero.

1 For the fracture rock properties, enter the following values:

a Name: RESERVOIR

b Fracture Porosity: 0.001

c Bulk X-dir Perm. (mD): 3.65

d Bulk Y-dir Perm. (mD): 3.65

e Bulk Z-dir Perm. (mD): 3.65

f Coal Compress. (1/psia): 1.0E-6

2 After entering these values, click on Apply.

Non-Equilibrium Initial Conditions 1 In this example, the following initial conditions should be specified:

a Reservoir Pressure: 1109 (psia)

b Water saturation: 0.592

2 Click on Apply.

Aquifers No aquifers are required for this tutorial.

Fractures No fractures are required for this tutorial.

Generate model1 In the Workflow area, click on Generate Model to see a 3D view of the reservoir at this

point in the workflow.

WellsThe third workflow data entry page is used to define the well location in terms of its deviation survey coordinates. These are absolute values which are referenced to the reservoir coordinate system which is top-left-back.

The first step is to create a well.

1 Click on the “Field” icon with the left mouse button to highlight it, and click on it with the right mouse button.

The Create Well floating menu option appears.


167

2 Select the Create Well option.

A dialog appears prompting for the name of the well. Enter the name as “Well1”, and click

on OK. A well icon appears below “Field” .

The Deviation Survey data entry folder appears in the right of the current window.

3 Click twice with the left mouse button on the + symbol in the top right corner of the table, or click twice on Insert row below the table, to insert two empty rows.

4 Enter the following coordinates in the x, y and z columns.

Hint If you click once to insert one row, enter the first line of data, then insert the second row, all the data values are copied automatically. This can be a useful timesaver.

5 Click on Apply.

The measured depth column updates automatically.

ProductionThe fourth workflow data entry page is used to define the well completion and production characteristics.

1 Click on Well1 to highlight it.

The list of Available event types is populated.

2 Select “Production from Well1” from the event drop-down box.

Click on New Event.

The Production Well Schedule Data panel opens showing the Well Controls folder.

3 Leave Start Date at “SOS” and Open/Shut Flag at “Open”.

Select the Control Mode of “Gas Rate” and specify a Target of 800 Mscf/day.

4 Click on the Limits tab.

5 Select a “BHP” Limit Type with a Limit Value of 40 psia and click on Add/Update to add this to the list of limits that will apply to the well.

OK to close the panel.

6 From the Available event types drop-down, select “Perforation Well1”.

Click on New Event.

The Perforation_1 data entry panel opens, showing the well completion which has been defaulted to apply over the full layer depth of the reservoir. Note that whereas the well deviation coordinates are specified relative to sea level, the completion depth extent is specified in terms of measured depth (MD) relative to the top of the reservoir layer.

OK to close the window, applying these values.

x (ft) y (ft) z (ft)

10 10 4100

10 10 4300


7 Click on Generate Model.

The model has been refined in the vicinity of the well completion.

Fluid PropertiesThe fifth workflow data entry page is used to define the PVT and fluid properties for the gas-water system, and the gas concentration properties for the coal bed methane. All of the required properties are calculated automatically by means of correlations.

Click though the PVT Correlations, Rel. Perm., Coal Bed Methane and Advanced tabs to see and modify the available options.

1 PVT Correlations

a Reference Temperature: 113 F

b Gas Gravity:0.55 sg_Air_1

c Reference Pressure: 1 psia

d Maximum Pressure: 3000 psia

2 Leave the Rel Perm data at defaults.

3 Coal Bed Methane

Diffusive Flow Input

a Gas Diffusion Coefficient: 12 ft^2/day

b Gas Desorption Time: 4e-6 day

c Coal Re-adsorption Factor: 1

4 Langmuir Isotherm Input

a Langmuir Pressure Constant: 625 psia

b Langmuir Concentration Constant: 486 scf/USton(daf)

c Coal Ash content weight fraction: 15.6%

d Coal Moisture content: 6.72%

e Coal Density: 1.433 g/cc

Advanced1 Click on Load Data from Correlations, and then Plot Data to view graphical plots of the

generated data.

Simulation ControlsThe sixth workflow data entry page is used to refine the simulation gridding controls.

1 Check the following default values have been entered:

a Regular Grid: checked

b Cells Per Layer:

Nx: 11

Ny: 11


169

Nz: 1

2 Click on Apply.

Running the Model and Viewing the ResultsThere are three buttons which are available throughout the workflow: Generate Model, Run ECLIPSE and View Results.

1 Click on Run ECLIPSE.

This validates the model and updates the display window. The input data file for the simulator is then written, and the simulator is launched in a separate command line window. Refer to the Log Window for progress reports. The command line window will close when the simulation has completed.

Wait until the message “Simulations finished. Timer Stopped” appears in the Log Window. You will then be able to view the output from the simulator.

2 Select View Results.

The ECLIPSE Office Result Viewer is displayed. The output from the simulator is automatically loaded, and a number of graphical displays automatically created.

The display in the Result Viewer is controlled using a Graphics Run File (GRF). The location of this file is set by lines in the ECLIPSE Office config file, such as:

Note Experienced users may edit the supplied GRF or define their own, to customise the display in the Result Viewer. For more information on the GRF file format please refer to "Graphics Run File" on page 347.

3 Toggle between pictures by selecting different nodes on the Pictures tree.

4 Select View | 2D. A new picture is created containing an areal view of the model.

5 Select Tools | Timestep.

Select Play from Animation Controls with the button. Individual timesteps may be displayed by selecting the appropriate time from the list above the controls.

Refer to "Result Viewer" on page 284 for more details of the features of the Result Viewer.

6 Close the Result Viewer.

Extended CBM using CO2 Injection with the ECLIPSE Solvent ModelWe will now copy the current Template model and create one which demonstrates CO2 injection using the ECLIPSE Solvent Model.

SECTION OFFICE

SUBSECT MODULES

CBM-GRF d:/ecl/2007.1/office/templates/coalbedmethane.grf


1 Close the current template. Highlight it in the ECLIPSE Office case tree, click on it with the right mouse button, and select Add Clone Case from the pop-up list.

2 Name the new case Solvent and click on OK.

3 Select CO2 Gas Injection from the Model Definition panel.

Wells1 Move to the Wells panel.

2 Create an Injection well I1 following the same procedure as before.

a Enter the following coordinates in the x, y and z columns.

3 Click on Apply.

The measured depth column updates automatically.

ProductionAdd Perforation and Well controls for the injector. The fourth workflow data entry page is used to define the well completion and production characteristics.

1 Click on the I1 icon.

This displays the available event types.

2 Select the “Injection in I1” event type from the event drop-down box.

Click on New Event.

The Injection Well Schedule Data panel opens showing the Well Controls folder.

3 Select the Injector Type to be CO2, Control Mode to be Surface Flow Rate, and specify the Target to be 250 Mscf /day.

4 Click on the Limits Tab.

5 Select a BHP limit of 2175 psia and click on the Add/Update button to add this to the list of limits that will apply to the well.

6 From the Available event types drop-down, select “Perforation l1”.

Click on New Event.

The Perforation_1 data entry panel opens, showing the well completion which has been defaulted to apply over the full layer depth of the reservoir. Note that whereas the well deviation coordinates are specified relative to sea level, the completion depth extent is specified in terms of measured depth (MD) relative to the top of the reservoir layer.

7 OK to close the window, applying these values.


160 160 4100

160 160 4300


171

Fluid Properties1 Go to the Coal Bed Methane tab and input the following values and click on Apply:

a CO2 Langmuir Pressure Constant: 276 psia

b Langmuir Concentration Constant: 993.8 scf/USton(daf)

Running the Model and Comparing the Results1 Click on Run ECLIPSE.

2 After the simulation is complete Select Case | Compare... in the main ECLIPSE Office menu bar.

Note that there is considerably more methane produced when CO2 is used to displace the methane from the coal.

Extended CBM using CO2 Injection with the ECLIPSE Compositional ModelWe will now copy the current Template model and create one which demonstrates CO2 injection using the ECLIPSE Extended Langmuir model.

1 Close the current Template.

2 Highlight the Solvent Case in the ECLIPSE Office Case tree and right click. Select Add Clone Case from the pop up list.

3 Name the new case Compos and click on OK.

4 Select Use Compositional Model from the Model Definition panel.

Reservoir Description1 Select the Rock Properties tab and set the Rock density to 89.5 lb/ft^3.

Fluid PropertiesThe Extended Langmuir Model requires a full compositional description of the fluids. In the PVT Composition table enter the INITIAL fluid composition and include all components that will be present at any time during the simulation. This list is exported to the PVTi Equation of State program, which will run in batch mode and export the properties of the components.

1 For this example set the C1 component fraction to 1.0.

The CO2 component is automatically exported (with initial fraction 0) by virtue of it being selected in the Model Definition page.

The Langmuir coefficients are entered in the Coal Bed Methane tab:


2 Enter the following values in the table

3 Click on Apply.

Running the model and comparing the results1 Click on Run ECLIPSE.

The PVTi program will run automatically in batch mode.

Note On some machines there will be a message that Application Fonts are not available. This is a benign message and does not interfere with the running of the simulator.

2 After the simulation is complete select Case | Compare... in the main ECLIPSE Office menu bar.

Note that the Gas Production curves from the SOLVENT and COMPOSITIONAL models are very similar. The benefit of using the COMPOSITIONAL model is that we can report individual component production.

3 In the Result Viewer, add the output vectors FCWGPR_n (Field Component Wet Gas Production).

The components are numbered in the order they appear in the PVT Composition table; in this case, 1 is CO2 and 2 is Methane.

DiscussionThis tutorial familiarized you with the main features of the Coal Bed Methane Template workflow, from model generation through running the simulation to results viewing. The tutorial demonstrated how a simulation model may be built quickly using the template.

ComponentPressure Constant

psiaConcentration Constant

Mscf/USton(daf)Sorption time

daysRe-adsorption Coefficient

fraction

CO2 276 0.9938 Default value:

0.001152 day

Default value:

0Methane (C1) 625 0.485

ECLIPSE Office 2007.1 User Guide TutorialsTutorial 11: Using the Completions Modeling Tool template

173

Tutorial 11: Using the Completions Modeling Tool template

ObjectiveThe aim of this tutorial is to present the main features of the Completions Modeling Tool template, including the workflows required for completion model generation, running the simulation and result evaluation. The tutorial demonstrates how to build completion models and evaluate results quickly, using an autogenerated graphics run file (GRF) to load in available simulation quantities and to build useful graphs.

Problem DescriptionIn this tutorial you construct a simple, rectangular model of a centrally-located vertical well with a single completion. The reservoir fluid consists of live oil above bubble point.

Stages• "Workflow" on page 175.

• "Reservoir Description" on page 175.

• "Wells" on page 176.

• "Production" on page 178.

• "Fluid Properties" on page 179.

• "Simulation Controls" on page 179.

• "Running the model and viewing the results" on page 179.


Getting Started

Note You may need to edit your config.ecl file (in directory /ecl/macros) to enable the Completion Modeling Tool template.

174 Tutorials ECLIPSE Office 2007.1 User GuideTutorial 11: Using the Completions Modeling Tool template

1 Under SECTION OFFICE add the following lines:

2 Start ECLIPSE Office from the ECLIPSE Launcher.

3 Select File | New Project from the top menubar.

4 Call the project cmt.off.

5 Select Case | Add Case | Template.The Template Model Selection panel is displayed.

6 Select Completions Modeling Tool.

7 Click on OK to open the Completions Modeling Tool Template Workflow panel.

The Completions Modeling Tool user interface consists of two windows:

WorkflowThe first window is the workflow interface. It displays all the sections required to construct the completions model, along with the functionality to simulate the model and evaluate results. You can select each stage in the workflow using the radio buttons, and navigate through the pages defining the selected workflow stage using the <<Previous and Next>> buttons.

Display (Template 3D Model Viewer)The second window is a display of the current reservoir model. This model may be updated at any time using the Generate Model button on the workflow section. A simulation grid is automatically created which honors the features of the model. When one or more wells have been defined, the location of the wells will also be included in the reservoir model display. By default, automatic gridding is applied to the reservoir according to the well locations, the phase contacts depths and the well workovers. In general, grid refinements are applied in the vicinity of these physical features. In consequence, the displayed reservoir grid may change during the process of data entry as various values are entered or modified. Note that grid refinements in the vicinity of the well will only be applied if the well completions have been specified.

SECTION OFFICE

-- Enable the Completions Modelling Tool

CMT TRUE

-- Set the generic GRFs which will be read into the Result Viewer launches from the a template model

CMT-GRF $ECLARCH/$ECLVER/office/templates/cmt.grf

VALVE-GRF $ECLARCH/$ECLVER/

DOWNHOLE-TUBULAR-CATALOG $ECLARCH/$ECLVER/


175

WorkflowModel DefinitionThe first workflow page contains the general model definitions. The model is defaulted to contain oil above bubble point as fluid conditions. The other options to define the state of the fluids in the model are: Dry Gas, Oil & Dissolved Gas, Oil & Water, Gas & Water and Oil, Gas & Water. The ECLIPSE simulator will be used for modeling the reservoir behavior as a function of time. By default, a single set of initial conditions is assumed to apply to the entire reservoir, but selecting the check box in the Model Parameters section activates the option to model independent zones with separate initial conditions.

The default assignments will be used for this tutorial.

Reservoir DescriptionThe second workflow page provides access to the reservoir description. This consists of four data entry windows, which are described below. In these windows, data entry fields, which are colored yellow, signify that if you do not supply a value, a default value is provided automatically. Data entry fields, which are colored white, require that you enter the value.

LayersThe Layers data entry window specifies the reservoir dimensions and location with respect to sea level.

1 Enter the following values:

a When these values are entered, click on Apply.

Note The above set of data defines a rectangular reservoir of dimensions 800 x 800 x 150 ft with the depth of the top of the layer at 5000 ft below sea level.

Rock PropertiesThe Rock Properties data entry panel specifies the rock properties for each layer of the model specified in the Layers data entry panel.

1 Leave the default RESERVOIR values and click on the Apply button.

Layer Name: Layer1

Rock: (No entry, this will default to “RESERVOIR”)

Top Depth Left (ft): 5000

Top Depth Right (ft): 5000

Horiz Disp (ft): 0

Thickness (ft): 150

Length (ft): 800

Width (ft): 800


Initial ConditionsDepending on the phases present, different data entries will be required to initialize the model. In this example, only oil above bubble point has been defined, hence the following initial conditions should be specified:

AquifersNo aquifers are required for this tutorial.

WellsThe third workflow data entry page is used to define the well location in terms of its deviation surveys coordinates. These are absolute values which are referenced to the reservoir coordinate system, which is top-left-back. The first step is to create a well:

1 Click on the “Field” button with the left mouse button to highlight it.

2 Click on the button with the right mouse button and select Create Well.

A window appears which prompts for the name of the well.

3 Enter the name as Well1, and click on OK.

A “Well stem” button appears below the “Field” button. The Deviation Survey data entry folder appears in the right of the current window.

4 Click twice with the left mouse button on the + symbol in the top right-hand corner of the table, to insert two empty rows.

5 Enter the following coordinates in the x, y and z columns:

6 Click on Apply.

The Measured Depth column updates automatically.

7 In the Workflow area, click on the Generate Model button to see a 3D view of the reservoir at this point in the workflow.

Note You can also create a vertical well in terms of its areal position and depth by selecting and using the Add Vertical Well button on the Field panel.

Note When a well is created using “Add Vertical Well” or “Add Well” button on the Field panel, then a default casing also gets created along with the well.

Reservoir Pressure: 6000 (psia)

Datum Depth (TVDSS): 5040 (ft)


400 0 5000

400 0 5150


177

CasingThe Casing data entry panel is used to define the properties and locations of the open holes and casings in the current model.

1 Click on Add casing from catalog.

2 Select the row with the following casing specifications:

3 Click on OK.

A casing with the specifications selected from the catalog will be added to the table.

4 In the Casings table, enter the Casing Name as Casing1, and click on Apply.

TubingThe Tubing data entry panel is used to define the properties and locations of the tubings in the model.

1 Click on New Tubing.

2 Enter Tubing Name as Tubing1, and click on OK.

3 Enter the following tubing properties for Tubing1:

4 Click on Apply.

Downhole DevicesThe Downhole Devices data entry panel allows you to position different types of downhole devices in the well completion. Inlet Valves, Flow Control Valves, Gas Lift Valves, Packers and Pumps can be included using this panel.

1 In the Available Device Types drop-down menu, select Packer as the device type.

2 Click on the New Device button.

3 A window appears which prompts you for the packer specifications. Enter the following information:

Outer Diameter (in) 9.625

Weight Per Length (lbf/ft) 47

Thickness (in) 0.472

Inner Diameter (in) 8.681

Drift Diameter (in) 8.525

Coupling OD (in) 10.625

End Branch Well1

End Measured Depth (ft) 90

Inner Diameter (in) 3.958

Outer Diameter (in) 4.5

Inner Roughness (in) 0.012

Outer Roughness (in) 0.012

Name Packer1

Casing Casing1 (selected from drop-down menu)

MD (ft) 70


4 Click on OK. The packer created will be added to the Existing devices list.

ProductionThe fourth workflow data entry page is used to define the well events and production characteristics.

1 Click on the “Well1” button .

This displays all the available event types for Well1.

2 In the Available event types dropdown menu, select Perforation Well1 as the event type. Click on New Event.

The perforation data window is displayed.

3 Enter the name as Perforation1 and the following perforation properties:

4 Click on OK to add Perforation1 to the list of Existing events.

5 Click on the “Well1 stem” button .

6 Select "Production from Well 1" from the Available event types dropdown menu and click on New event.

7 The Production Well Schedule Data panel is displayed showing the Well Controls folder.

8 Select the Control Mode to be Oil Rate and specify the Target to be 0 stb/day.

9 Click on OK to add the production data to the list of existing events.

Note A limitation of the current release requires that you specify a rate limit for the Well Stem even if a packer has been included to avoid production. This is only a validation check of the application, and does not affect the model created.

10 Click on the “Tubing1” button

11 Select Production from Tubing1 from the Available event types dropdown menu and click on New Event.

The Production Well Schedule Data panel is displayed showing the Well Controls folder.

12 Select the Control Mode to Oil Rate and specify the Target as 300 stb/day.

13 Now go to the Limits folder. Select Limits of BHP, specify a Limit Value of 2300 psia Click on Add/Update.

14 Click on OK to add the production data to the list of existing events.

15 Click on Generate Model in the Workflow panel.

The model has been refined in the vicinity of the well completion.

Start Date SOS

Start MD (ft) 100

Stop MD (ft) 140

Skin Factor 0

Well Bore Diameter (ft) 1


179

Fluid PropertiesThe fifth workflow data entry page is used to define the PVT and fluid properties for the oil system. All of the required properties are calculated automatically by means of correlations.

We will use the default values for this tutorial.

Simulation ControlsThe sixth workflow data entry page is used to set the simulation gridding controls.

1 Check the following default values have been entered:

a Grid to Phase Contacts: checked.

b Grid to Well Workovers: checked.

c Minimum Cell Sizes:

X: 1 ft

Y :1 ft

Z: 1 ft

d Maximum Cell Sizes:

X: 1000 ft

Y: 1000 ft

Z: 1000 ft

e Growth Factors:

X: 2

Y: 2

Z: 2

f Phase Contacts:

Minimum z adjacent to contact: 1 ft.

2 Click on Apply.

Running the model and viewing the resultsNote that there are four buttons that are available throughout the workflow: Generate Model, Run Simulation, View Results and Generate Report.

1 Click on Run ECLIPSE.

This validates the model and updates in the display window. The input data file for the simulator is then written. The simulator is launched in a separate command line window. Refer to the Log Window for progress reports. This command line window will close when the simulation has completed.

Wait until the message “Simulations finished. Timer Stopped” appears in the Log Window. You will then be able to view the output from the simulator.

2 Select View Results.


The ECLIPSE Office Result Viewer is displayed. The output from the simulator will be automatically loaded and a number of graphical displays automatically created. The display in the Result Viewer is controlled using a Graphics Run File (GRF). The location of this file is controlled by the following lines in the ECLIPSE Office config file:

Note Advanced users may edit the supplied GRF or define their own in order to customize the display in the results viewer. For more information on the GRF file format please refer to "Graphics Run File" on page 347.

3 Toggle between pictures by selecting different nodes on the Pictures tree.

4 Select View | 2D. A new picture is created containing an areal view of the model.

5 Select Tools | Timestep... Select Play from Animation Controls using the Play control button.

6 Individual timesteps may be displayed by selecting the appropriate time from the list above the controls.

Note Please refer to "Result Viewer" on page 284 for more details of the features of the Result Viewer.

7 Close the Result Viewer.

DiscussionThis tutorial presented the main features of the Completions Modeling Tool template, including the workflows required for completion model generation, running the simulation and result evaluation. The tutorial demonstrated how to build completion models and evaluate results quickly, using an autogenerated graphics run file (GRF) to load in available simulation quantities and to build useful graphs.

SECTION OFFICE

SUBSECT MODULES

CMT-GRF d: /ecl/2007.1/office/templates/

Documents

Tutorial Ecl