ACTIONW

Recognised by the OPM Flow parserSCHEDULE

This keyword starts the definition of an ACTIONW section that stipulates the Boolean conditions to test the nominated well parameters, and the resulting SCHEDULE keywords to be executed, if the Boolean condition evaluates to true. An ACTIONW Definition Section is terminated by an ENDACTIO keyword on a separate line. Here, the keyword defines a series of conditions applied to wells only, that invoke run time processing of ACTION functions, and is similar to executing a run time script for conditions and variables at the well level. The ACTION series of keywords (ACTION, ACTIONG, ACTIONR, ACTIONS and ACTIONW) can apply Boolean conditional tests to variables at the field, group, region, well segment and well levels.

Note that one should use caution when using this facility as it may result in the simulator aborting, because the ACTIONW keyword enables the user to implement complex functionality and therefore it is advisable to start with simple expressions before adding the desired complexity.

See also the PYACTION keyword in the SCHEDULE that implements OPM Flow’s Python scripting facility using the Python scripting language.

This keyword is not supported by OPM Flow but would change the results if supported so the simulation will be stopped; use the ACTIONX keyword instead.

Notes:

There is no terminating “/” for this keyword, instead the ENDACTIO keyword terminates the keyword.

The well SUMMARY vectors that can be used with the ACTIONW keyword by OPM Flow and the commercial black-oil simulator are outlined in Table 12.5.

No.

Well SUMMARY Vector Description

SUMMARY

Mnemonic

1

Bottom-Hole Pressure

WBHP

2

Gas Injection Rate

WGIR

3

Gas Injection Total

WGIT

4

Gas-Liquid Ratio

WGLR

5

Gas-Liquid Ratio (Bottom Hole)

WBGLR

6

Gas-Oil Ratio

WGOR

7

Gas Production Rate

WGPR

8

Gas Production Total

WGPT

9

Liquid Production Rate

WLPR

10

Liquid Production Rate

WLPT

11

Oil Injection Rate

WOIR

12

Oil Injection Total

WOIT

13

Oil Production Rate

WOPR

14

Oil Production Total

WOPT

15

Polymer Production Concentration

WCPC

16

Polymer Production Rate

WCPR

17

Salt Production Concentration

WSPC

18

Salt Production Rate

WSPR

19

Tracer Production Concentration (Tracer name should be added to WTPC)

WTPC

20

Tracer Production Rate (Tracer name should be added to WTPC)

WTPR

21

Tubing Head Pressure

WTHP

22

Voidage Injection Rate

WVIR

23

Voidage Injection Total

WVIT

24

Voidage Production Rate

WVPR

25

Voidage Production Total

WVPT

26

Water Cut

WWCT

27

Water Injection Rate

WWIR

28

Water Injection Total

WWIT

29

Water Production Rate

WWPR

30

Water Production Total

WWPT

31

Water-Gas Ratio

WWGR

32

User Defined Quantity

WUXXXXXX

Notes:

Cells under the No. column not colored show that the SUMMARY vector is functional within an ACTIONW block.

Cells under the No. column colored orange show that the SUMMARY vector is currently not supported within an ACTIONW block.

Table 12.5: ACTIONW Supported Well SUMMARY Variables

See also the ACTDIMS and UDADIMS keywords in the RUNSPEC section to define the dimensions for the ACTION series of keywords and associated variables. In addition, the EXIT keyword in the SCHEDULE section that allows for terminating the simulation for when a condition within an ACTIONW definition is satisfied

Although most SCHEDULE section keywords should work with the ACTIONW keyword, Table 12.8 under the description ofACTIONX – Define Action Conditions and Command Processing shows the status of keywords that have been tested and known to work, together with keywords that are currently planned to be implemented.

As mentioned previously,the UDQ keyword stipulates the variables and operations used to access the User Defined Quantities features in OPM Flow. UDQ variables can be constants, SUMMARY variables, as defined in the SUMMARY section,or a formula using various mathematical functions together with constants and SUMMARY variables.

Note

Within an ACTIONW Definition Section any UDQ variables utilizing well variables, must have their associated wells previously fully defined in the commercial simulator, otherwise an error will occur. For example, if a well’s GOR is being used as part of a UDQ definition, then the well must be fully characterized prior to declaring the UDQ definition.

This restriction does not apply to OPM Flow; however, it should be considered if the same deck is to be run with both simulators.

User Defined Quantities can also be used as User Defined Arguments (“UDA”) in the SCHEDULE section with various group, well, and connection keywords. In this case, the UDA variables are used to replace numerical values on these keywords by UDA variables that have been defined by the UDQ keyword. For example, if we wish to make the oil rate for certain wells to be a function of their water cut, then one can define the function using the UDQ keyword that results in a UDQ variable, WU_WOPR say, and then use WU_WOPR as a UDA variable on the WCONPROD keyword for the ORAT parameter. See Table 12.76for a list of keywords that can be used with UDA variables in the UDQ - Declare User Define Quantities (“UDQ”)keyword section.

Records

Fixed number of records

Record count

1

Items per record

7

Parameters

Example

The first example uses the ACTIONW keyword to re-complete a gas injection well, GI01, when the well’s bottom-hole pressure exceeds the fracture pressure of the formation, and to open up a structurally higher zone in the well. The keyword NEXTSTEP is used to set the next step to 0.1 days to avoid convergence issues due to a well event.
--
-- ACTIONW WELL COMMANDS
--
ACTIONW
-- ACTION WELL ACTION ACTION ACTION MAX INCREMENT
-- NAME NAME LHS TEST RHS ACTIONS RHS
ACTW-1 GI01 WBHP > 6800.0 /
--
-- ACTION COMMANDS TO BE EXECUTED
--
-- NEXT ALL
-- STEP TIME
NEXTSTEP
0.1 'NO' /
--
-- WELL PRODUCTION STATUS
--
-- WELL WELL --LOCATION-- COMPLETION
-- NAME STAT I J K FIRST LAST
WELOPEN
GI01 SHUT /
GI01 SHUT 0 0 0 2 2 /
GI01 OPEN /
GI01 OPEN 0 0 0 1 1 /
/
ENDACTIO
The second example shows how to reduce a producing well's deliverability due to water production. Here, well OP01’s productivity index is reduced by 2% when the well’s liquid production total is greater than 100,000 stb. The reduction is repeated 300 times and each time the action is executed the ACTRHS constant is increased by 10,000 stb.
--
-- ACTIONW WELL COMMANDS
--
ACTIONW
-- ACTION WELL ACTION ACTION ACTION MAX ICREMENT
-- NAME NAME LHS TEST RHS ACTIONS RHS
ACTW-01 OP01 WLPT > 100E3 300 10E3 /
--
-- DEFINE WELL CONNECTION MULTIPLIERS
--
-- WELL PI --LOCATION-- COMPLETION
-- NAME MULT I J K FIRST LAST
WPIMULT
OP01 0.980 1* 1* 1* 1* 1* /
/
ENDACTIO
The final example is similar to the previous example, and shows how to nest ACTIONW blocks and how to apply ACTIONW to all the oil producers when the Boolean condition are satisfied.
--
-- ACTIONW WELL COMMANDS
--
ACTIONW
-- ACTION WELL ACTION ACTION ACTION MAX ICREMENT
-- NAME NAME LHS TEST RHS ACTIONS RHS
ACTW-01A 'OP*' WLPT > 100E3 300 10E3 /
--
-- ACTIONW WELL COMMANDS
--
ACTIONW
-- ACTION WELL ACTION ACTION ACTION MAX ICREMENT
-- NAME NAME LHS TEST RHS ACTIONS RHS
ACTW-01B 'OP*' WPI > 5.0 1 0.0 /
--
-- DEFINE WELL CONNECTION MULTIPLIERS
--
-- WELL PI --LOCATION-- COMPLETION
-- NAME MULT I J K FIRST LAST
WPIMULT
'?' 0.980 1* 1* 1* 1* 1* /
/
ENDACTIO
ENDACTIO
In this case the outer ACTIONW checks if the liquid production for each OP* well is great than the calculated ACTRHS constant, if it is, then inner ACTIONW reduces all the selected wells’ productivity indices by 2%, provided the well’s productivity index is greater than five.
| Note Within an ACTIONW Definition Section any UDQ variables utilizing well variables, must have their associated wells previously fully defined in the commercial simulator, otherwise an error will occur. For example, if a well’s GOR is being used as part of a UDQ definition, then the well must be fully characterized prior to declaring the UDQ definition. This restriction does not apply to OPM Flow; however, it should be considered if the same deck is to be run with both simulators. |
|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|

Manual source: parts/chapters/subsections/12.3/ACTIONW.fodt