COMPORD
Recognised by the OPM Flow parserSCHEDULE
The COMPORD keyword defines how the well connection data entered on the COMPDAT keyword in the SCHEDULE section are to be ordered for a well.
Notes:
The keyword is followed by any number of records.
Each record is terminated by a “/” and the keyword should be terminated by a “/”.
See also the COMPDAT keyword in the SCHEDULE section.
Note
If visual inspection of the well trajectories in the model indicate problematic or unrealistic well connections, the options on this keyword may be useful in correcting the issue.
- Records
- One or more records, each terminated by
/ - Items per record
- 2
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 | ORDER_manual: COMPORD | A character string that defines the method for ordering the well connections given on the COMPDAT keyword, and should be set to DEPTH, INPUT, or TRACK. DEPTH: The connections are ordered by a connection’s true vertical depth from the shallowest to the deepest. If multiple connections are at the same depth then these connections are sub ordered by the sequence they were entered on the COMPDAT keyword. INPUT: This option results in the connections being ordered in the same sequence as entered via the COMPDAT keyword. In this case the connections should be declared in the correct sequence, starting with the connection nearest the well head and then working along the wellbore towards the bottom or toe of the well. Atgeirr Rasmussen 2017-09-20T11:54:43 AFR This option is somewhat involved to explain precisely, should we insert an explanation of the algorithm used here? If not here, where? TRACK David Baxendale 2017-10-02T17:52:03.846000000 DBx Reply to Atgeirr Rasmussen (09/20/2017, 11:54): "..." Yes, we need to document this but I think this can wait until we get the first release out, otherwise we will never finish. I’ll keep the comments so we can trackt it. : This option enables OPM Flow to trace the well connections through the grid to obtain the correct order for the connections. If the supplied COMPDAT indicates the well is vertical (via the DIRECT variable being equal to Z on the COMPDAT keyword) then the DEPTH option will be applied instead. This option is somewhat involved to explain precisely, should we insert an explanation of the algorithm used here? If not here, where? Reply to Atgeirr Rasmussen (09/20/2017, 11:54): "..." Yes, we need to document this but I think this can wait until we get the first release out, otherwise we will never finish. I’ll keep the comments so we can trackt it. All options are now supported by OPM Flow. | STRING | TRACK |
Example
The following example defines the connections for two vertical oil wells using the COMPDAT keyword and the COMPORD to defined the connection ordering for the wells.
--
-- WELL CONNECTION DATA
--
-- WELL --- LOCATION --- OPEN SAT CONN WELL KH SKIN D DIR
-- NAME II JJ K1 K2 SHUT TAB FACT DIA FACT FACT FACT PEN
COMPDAT
OP01 1* 1* 20 56 OPEN 1* 1* 0.708 1* 0.0 1* 'Z' /
OP01 1* 1* 75 100 SHUT 1* 1* 0.708 1* 0.0 1* 'Z' /
OP02 35 96 75 100 OPEN 1* 1* 0.708 1* 0.0 1* 'Z' /
--
-- DEFINE WELL CONNECTION ORDERING
--
-- WELL COMPL
-- NAME ORDER
COMPORD
OP01 DEPTH /
OP02 DEPTH /
/
The DEPTH option has been chosen because both wells are vertical. Also one could use the following format instead for the COMPORD:
--
-- DEFINE WELL CONNECTION ORDERING
--
-- WELL COMPL
-- NAME ORDER
COMPORD
* DEPTH /
/
as both wells should utilize the DEPTH option. This version would set all wells in the model to DEPTH connection ordering.
| Note If visual inspection of the well trajectories in the model indicate problematic or unrealistic well connections, the options on this keyword may be useful in correcting the issue. |
|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|Manual source: parts/chapters/subsections/12.3/COMPORD.fodt