COMPLMPL
Recognised by the OPM Flow parserSCHEDULE
The COMPLMPL keyword assigns well connections in a LGR, as defined by the COMPDATL keyword in the SCHEDULE section, to completion intervals. This “lumping” of the connections to various completion intervals allows automatic workovers and economic criteria to be applied to the completions (that is a set of connections) as opposed to the connections. This allows for a more realistic approach for workovers operations.
For example, if the water cut criteria for working over a well was set to 95%, and the average grid block connection thickness was one meter, then once a well’s water cut reached 95% the worst offending one meter connection would be shut-in. If the well’s actual perforation interval was 10 meters and the 10 connections were lumped as one completion, then when the water cut limit of 95% is reach, the completion would be shut-in, that is all of the 10 connections within the completion would be shut-in.
As the keyword is used to lump connections into a completions, the simulator adds together the contribution from all connections in the completion and uses the total values to test the economic limits. Note that a connection can only belong to one completion. In addition, completions can be used instead of connections in the WELOPEN and WPIMULT keywords if the completions have been defined by COMPLUMP for a well.
This keyword is not supported by OPM Flow but would change the results if supported so the simulation will be stopped.
Notes:
The keyword is followed by any number of records.
Each record is terminated by a “/” and the keyword should be terminated by a “/”.
Multiple grid block connections can be defined on one record for vertical wells by assigning different values to K1 and K2, for deviated and horizontal wells this may not be possible and therefore each grid block connection must be separately defined by setting K1 equal to K2.
See also the COMPDATL keyword in the SCHEDULE section.
- Records
- One or more records, each terminated by
/ - Items per record
- 7
Parameters
| No. | Name | Description | Type | Default |
|---|---|---|---|---|
| 1 | WELLmanual: WELNAME | A character string of up to eight characters in length that defines the well name for which the well connection data are being defined. Note that the well name (WELNAME) must have been declared previously using the WELSPECS keyword in the SCHEDULE section, otherwise an error may occur. | STRING | None |
| 2 | GRIDmanual: LGRNAME | A character string of up to eight characters in length that defines the LGR name for which the well LGR connection data are being defined. Note that the well name (LGRNAME) must have been declared previously using the WELSPECL keyword in the SCHEDULE section, otherwise an error may occur. If defaulted with 1* the LGR on the WELSPECL keyword will be utilized. | STRING | Defined |
| 3 | I | A positive integer greater than or equal to zero and less than or equal to NX that defines the connection location in the I-direction. If set to zero or defaulted with 1* then all connections in the I-direction that also satisfy J, K1 and K2 criteria are assigned the ICOMP completion number. | INT | 0 |
| 4 | J | A positive integer greater than or equal to zero and less than or equal to NY that defines the connection location in the J-direction. If set to zero or defaulted with 1* then all connections in the J-direction that also satisfy I, K1 and K2 criteria are assigned the ICOMP completion number. | INT | 0 |
| 5 | UPPER_manual: K1 | A positive integer greater than or equal to one and less than or equal to NZ that defines the UPPER connection location in the K-direction. If set to zero or defaulted with 1* then the upper most connection in the well is used. | INT | 0 |
| 6 | LOWER_manual: K2 | A positive integer greater than or equal to K1 and less than or equal to NZ that defines the LOWER connection location in the K-direction. If set to zero or defaulted with 1* then the low most connection in the well is used. | INT | 0 |
| 7 | COMPLETION_manual: ICOMP | An integer greater than or equal to one and less than or equal to MXCONS as defined on the WELLDIMS keyword in the RUNSPEC section, that defines the completion number of the currently defined set of connections. If I, J, K1, K2 are all set to zero or defaulted to 1*, then all connections in the well have the same completion number of ICOMP. | INT | None |
Example
The following example defines the connections for two vertical oil wells using the COMPDATL keyword and the re-allocation of the connections to completions intervals using the COMPLMPL keyword.
--
-- WELL CONNECTION DATA FOR LGR WELLS
--
-- WELL LGR --- LOCATION --- OPEN SAT CONN WELL D DIR
-- NAME NAME II JJ K1 K2 SHUT TAB FACT DIA FACT PEN
COMPDATL
OP01 OP01LGR 14 13 20 56 OPEN 1* 1* 0.708 3* Z /
OP01 OP01LGR 14 13 75 100 SHUT 1* 1* 0.708 3* Z /
OP02 OP02LGR 35 96 75 100 OPEN 1* 1* 0.708 3* Z /
/
--
-- ASSIGN WELL CONNECTIONS TO COMPLETIONS
--
-- WELL LGR --- LOCATION --- COMPL
-- NAME NAME II JJ K1 K2 NO. COMPLMPL OP01 OP01LGR 1* 1* 20 56 1 / COMPLETION NO. 01
OP01 OP01LGR 1* 1* 75 100 2 / COMPLETION NO. 02
OP02 OP02LGR 1* 1* 75 85 1 / COMPLETION NO. 01
OP02 OP21LGR 1* 1* 86 100 2 / COMPLETION NO. 02
/
Here the well OP01 connections (14, 13, 20) to (14, 13, 56) are assigned to completion number one and connections (14, 13, 75) to (14, 13, 100) are assigned to completion number two. Well OP02 has only one set of connection data from cells (35, 96, 75) to cells (35, 96, 100), but they have split into two separate completion intervals, with connections (35. 96, 75) to (35. 96, 85) assigned to completion interval number one and (35, 96, 86) to (35, 96, 100) to completion number two.Manual source: parts/chapters/subsections/12.3/COMPLMPL.fodt