Reservoir Coupling

8/18/2019 Reservoir Coupling

1/39

Advanced ECLIPSE Course

Reservoir Coupling


2/39

© 2005 Schlumberger Information Solutions. All rights reserved.

Purpose

• The Reservoir Coupling option allows the engineer to couple anumber of different E1!" simulation models

• The coupled reservoirs could share a common surface networ#$ orcould be under constraints on overall production ! in%ection

• The individual simulation models run as separate processes$ eachhaving its own standard ECLIPSE data file

• The simulation models ma& have different characteristics e'g' "(

phase models ma& be coupled with )(phase models


3/39


*ow +oes It ,or#-

• .ne model is chosen to be the /ASTER$ the other models aredefined as SLA0ES

• The slave processes are activated b& the master$ and run ins&nchronisation with it

• The master process imposes production and in%ection constrainson the slaves to meet the overall targets

• Communication between the processes is handled b& themessage(passing s&stem P0/ parallel virtual machine2 ! /PI

(/essage Passing Interface)$ which must be present on the

s&stem


4/39


Slave Reservoirs

• Each slave reservoir has its own ECLIPSE input data file

• The slave could be a restart run

• Each slave must have one or more slave groups ( acting as the

path for communicating flow rates and constraints with the masterprocess

• Slave groups can be at different levels' 3ut one slave groupcannot be subordinate to another slave group

P0/

/PISlave4roup

/aster

4roup

same

ph&sicalgroup


5/39


/aster Reservoirs

• The master has its own ECLIPSE input data file

• It can be a reservoir of its own or %ust a dumm& modelcontaining the control logic

• It must have as active phases all the phases that are active inan& of the slave runs

• It must contain the group hierarch& of the whole system downas far as the slave groups in the slave reservoirs

• Slave groups are represented in the master reservoir b& master

groups which do not contain an& subordinate groups or wells

P0/

/PISlave

4roup

/aster

4roup

same

ph&sical

group


6/39


/aster(Slave *ierarch& 12


7/39


/aster(Slave *ierarch& "2

R1R2


8/39


Running the /odels 12

• At the start the master run$ the master en5uires the start date ofeach slave run

• A slave ma& start later than the master

• The master then decides about the time step length in the usual wa&$ but sub%ected to that

• it does not overshoot a reporting time step in an& of the slavereservoirs

• it #eeps the flow rate changes in the slave reservoirs withinacceptable bounds estimated from the changes over theprevious time step2


9/39


Running the /odels "2

• At the beginning of a time step$ the master en5uires from theslaves the slave groups6 production potentials ma& be used for

calculating the guide rates2

• Then the master allocates rate targets to all its master groups$based on their guide rates

• These are sent to their e5uivalent slave groups

• Slaves calculate the flows of the group under this constraint$and tells the master

• The master completes its own time step$ assuming that the ratesof the slave groups remain constant over the time step


10/39


Running the /odels )2

• ,hen the master has finished its time step the slave reservoirs areadvanced to the end of the master6s time step

• These slaves ma& ta#e one or more time steps to reach thistime

• ,hen the slaves have advanced to the new time$ the& send thenew cumulative production totals of the slave groups to the

master

• 7rom these the master calculates the average flow rates ofeach master group over its time step

• /aster updates its cumulative totals$ and writes outputs


11/39


Running the /odels 82

• This procedure continues until the master run finishes'

• The master sends a message to terminate the slave runs

• The master run and all the slave runs will terminate under the

following circumstances9• A slave run stops due to an error

• A slave run finishes earlier than the master run A:+ item ; of#e&word !C"# in the master run sets to


12/39


Reservoir Coupling 7iles

• The master run ma& write the flow rates and coupling constraintsof the master groups to a reservoir coupling file

• Subse5uentl&$ this file can be used to• substitute for one or more slave reservoirs in the master run

• slave group flows are read from file• drive a slave reservoir on its own

• master rate and constraints are read from file


13/39


4roup Control 12

• The master groups must be given guide rates

• the& ma& optionall& set as function of their potential rates

• the& ma& be e5ual to their voidage replacement need forin%ection2

• 4roups in the slave reservoir that are superior to the slave groupsmust not be given an& constraints on them

• If the slave reservoir has been alread& given such constraints$three options are available9

• ignore such constraints• honour the constraints• ta#e the minimum of these limits and the targets set b& the

master'


14/39


4roup Control "2

• If a rate constraint is applied to a phase that is not active in theslave$ it will be transformed into a active phase using a previousl&calculated phase ratio

• The overall rate targets applied to the coupled s&stem in the

master run will not be met e=actl&• reason9 the master run apportions the rate targets among the

master groups according to their slave groups6 capabilities atthe start of the time step$ but the flows are reported at the end of the time step

• remed&9 limit the master run6s time steps to #eep the e=pecteddrift within a specified tolerance item 8 of #e&wordR$%&AS'2


15/39


Re5uirements for the 4lobal :etwor#

• The master reservoir should contain a representation of the globalnetwor# down to the master groups and their own well groups

• In each slave reservoir$ the slave groups should be defined asfi=ed pressure nodes$ and the networ# e=tended down from them

to the well groups' An& groups superior to the slave groups

should not be part of the networ# in the slave reservoirs'

• Either standard or e=tended networ# can be used

:odal pressure

P0/ ! /PISlave4roup

/aster4roup

same

ph&sical

groupnode


16/39


Re5uirements for the E=tended :etwor#

• /aster reservoir9 the master groups must coincide with thesource nodes with the same names in the networ#

• Slave reservoirs9 The slave groups must coincide with the fi=ed(pressure nodes with the same names in the networ#

SEP N1

FB1

N2 N3 N4

FB2

FA2FA1

Network Group Hierarchy

Not Coincide withthe source node

COMP-A COMP-B

FB2FB1

FIEL

Coincide with

the source node


17/39


:etwor# 3alancing

• The networ# should be balanced at each time step the default in#e&word #!'(A)A#2

• All networ#s will be balanced simultaneousl& at each time step ofthe master process

• At each iteration of the balancing in the master9• /aster group nodal pressure (> slave group

• ?sing this pressure as the fi=ed pressure$ slave balances itown networ#s to convergence

• Slave sends bac# to the master the flows of the slave groups• /aster sums its flows up to the 7IEL+ level$ and updates thenodal pressures


18/39


?sing RC 7acilities ( The /aster Run 12

• +efine all active phases that are in an& of the slave run• +efine the group hierarch& using 4R?PTREE

• 4R?PTREE•


19/39


?sing RC 7acilities (The /aster Run "2

• Activate the coupled slave runs using SLA0ES• SLA0ES• (( slave slave file machine director& number of• (( name root name host name of data file Processors• This #e&word can onl& be used once in a run$so all slave processes must be started together

item 9 onl& needed when /PI is used ")aB1

onward2 It should be the same as the value in PARALLEL

• Re5uest to create a RC file9

• +?/PC?PL•


20/39


?sing RC 7acilities (The /aster Run "2

• Identif& the master groups /429• 4R?P/AST• (( /4 slave associated limiting rate• (( name name Slv 4roup fraction

•


21/39


?sing RC 7acilities (The /aster Run )2

• Set the global production rate targets and limits9• 4C.:PR.+• (( 4 C/ o w g l Actn 7ld 4Brate 4Brate• (( name ctrl- phase

• *7IEL+6


22/39


?sing RC 7acilities (The /aster Run 82

• Set the global in%ection rate targets and limits9

• 4C.:I:E

• (( 4 In% Ctl Surf resv rein% vrep fld gr gr def

• (( name phase mod rate rate frac frac ctl-•


23/39


?sing RC 7acilities (The Slave Run

• Identif& slave groups S429• 4R?PSLA0• (( S4 Assoc o w!l g res in%Bo in%Bw in%Bg• (( /4•


24/39


?sing RC 7acilities (

Reading a RC 7ile in the /aster Run 12

• +efine the RC file and its format to be read

• ?SEC?PL

•


25/39


• +efault the slave model6s name item "2 in 4R?P/AST

• R$%&AS'

• (( /4 slave associated limiting rate

• (( name name Slv 4roup fraction• *R2+A, *S)-, */I!), 0.1

• *R+A, 3 *R+A, 1

• *R+(, 3 *R+(, 1

• 1

?sing RC 7acilities(

Reading a RC 7ile in the /aster Run"2


26/39



+riving a Slave Run with a RC 7ile

• Identif& slave groups using 4R?PSLA0 as usual

• +efine the RC file and its format to be read

• $S!C$%)

• *&AS'!R, */, 1• The slaves2 will read the constraints from the RC file


27/39



S?//ARF Ge&words

• The following summar& data allows the user to e=amine the rateconstraints in the file that are applied to the slave groups in a

slave reservoir being run on its own9

• 4roup .il$4as$,ater production and in%ection rate limits9

• "%R)4 "IR)4 %R)4 IR)4 %R)4 IR)• 4roup li5uid production rate limit9

• )%R)• 4roup reservoir volume production and in%ection rate limit9

• -%R)4 -IR)


28/39


Some :otes 12

• All runs must share the same measurement units'

• The onl& global constraints that can be applied are9• group rate control• nodal pressure'

• .ther features ma& be applied within individual reservoirs$ butcannot be emplo&ed globall&9

• prioritisation$ economic limits$ automatic drilling H wor#overfacilities$ group production rules'

• The master does not #now an&thing about wells in the slave runs'


29/39


Some :otes "2

• The master time step cannot be influenced b& slaves$ other thanobserving their report time steps'

• 4as 7ield .perations9• All contract groups must be situated in the master reservoir• Each contract &ear must start at the same date in all slaves'

• 4as lift optimisation cannot be used'

• The order of solving different t&pes of wells e'g' producers$ waterin%ectors$ gas in%ectors2 must be the same in all the coupled

reservoirs'

• same top up phase in%ectors solved last2'


30/39


Run RC obs ?sing P0/12

on the Same /achine

• Start pvm9pvm

• at the pvm prompt$ t&pe command


31/39


Run RC obs ?sing P0/"2

on different machines a2

• If the master and slaves are not run on the same machine$ there issome configuration to do9

• /a#e sure that from the master machine &ou can rsh to each slavemachine without t&ping password 'rhosts file in &our home

director&2• Fou must run csh or one of its variants' It won6t wor# with Gorn or

3ourne shell'

• In the 'cshrc file$ set variables• L/BLICE:SEB7ILE ( point to the license file• P0/BR..T ( point to the location of the P0/) director&'

E'g' setenv P0/BR..TJECLPAT*!"a!pvm)• P0/BARC*9 e'g' setenv P0/BARC*


32/39



on +ifferent /achines b2

• *aving got all the set up$ run pvm on the master machine9 pvm

• at the pvm prompt$ add the machines &ou want to run slaves9 e'g'• add machine1• add machine"

• Chec# if these have been added successfull& b& t&ping


33/39



on +ifferent /achines c2

• To run master and slaves on different machines are 5uite tric#&$especiall& if the various machines are not of the same t&pe e'g'

S4I and I3/2' It is far easier to run with ever&thing on a single

machine'

• Error messages get written to the files !tmp!pvmd'uid$ and!tmp!pvml'uid$ where uid is the user id number to get it t&pe id2'


34/39


P0/ Common Error /essages

• (D 9 :o host• the host re5uested is not in the virtual machine• P0/BARC* is not set to the correct t&pe'

• (K9 P0/ cannot find the e=ecutable &ou have re5uested• Chec# the search paths in the eclpvmhost file'

• (19 :o data file'• P0/ cannot find the data file on a remote host

• (1"9 7LE License problem'• ?suall& returned if the 7LE license manager is not running or

it cannot find the 7LE license file on a remote machine'


35/39


P0/ Error /essages

• A full list M


36/39


Run RC %obs using /PI ")aB1 onward2

on PCs

• /PI is installed see the installationnotes for details2

• Item of SLA0ES is set to the value asin PARALLEL if an&2

• Clic# on


37/39


Run RC %obs using /PI ")aB1 onward2

on ?:I

• /PI is installed• Item of SLA0ES is set to the value as in PARALLEL if an&2• mpieclipse procs ) file master ver "8a

• ,here ) processors are needed• The master file is named /ASTER'+ATA• To use "8a mpieclipse• Some machines re5uire the hosts file (hostfile hosts't=t2


38/39


License Sharing

• ,hen master and slaves are running on the same host$ onl& one license is

re5uired$ I7• The licenses re5uired b& the slaves are chec#ed before the #e&word

SLA0ES in the master run

• License chec#ing

• Some options are chec#ed in R?:SPEC section$ e'g' E:+SCALE for

end point scaling• Some options are chec#ed in SC*E+?LE section$ e'g' 4R?P:ET for

standard networ#$ S,I:47AC for gas field options• ?se #e&word LICE:SES to reserve licenses in R?:SPEC section

)IC!#S!S*net6or7, 1*gasfield, 11

• If slaves are running on separate hosts$ each slave re5uires a separatelicense'


39/39

Documents

Reservoir Coupling