Reservoir to Reservoir Transfer (Bookover) (ityopr=6)
The type 6 operating rule allows a reservoir to reservoir bookover to occur. It is commonly used to transfer water from one reservoir storage account to another in a particular month. In addition, the amount booked over may be constrained by a diversion demand or the amount diverted by another operating rule.
The following are noted:
- If variable
iopsou(2,1)is set to a diversion structure, variableiopsou(4)is set to 99 and variableoprlimitis set to 0, the book over can be limited by the demand specified in the direct diversion demand file (*.ddm). - If variable
iopsou(2,1)is set to a operating rule, variableiopsou(4)is set to 0, and variableoprlimitis set to 0, the book over can be limited by the amount divered by another operating rule. - If variable
iopsou(2,1)is set to a operating rule,iopsou(4)is set to 0 andoprlimitis set to 1, the bookover can be limited to not occur after the operating ruleiopsou(2,1)operates. This capability was added for several reservoirs located in the San Juan Basin where water needs to get booked from several accounts in a reservoir to an account in that same reservoir then booked back from that account in order to reallocate total reservoir storage to each individual account at the beginning of the reservoir’s administration year.
A Bookover is reported in the reservoir report (*.xre) as follows:
- When a Type 6 Bookover operating rule is used to book water from one reservoir account to another without making a release to the river,
the reservoir report (*.xwb) for the total reservoir (account 0) and the account where the water was booked shows the water under the column
7,
From Carrier by Other. In addition, the reservoir report (*.xwb) for the individual account along with the operating rule reporting (*.xop) reflect the actual amount diverted. - When a Type 6 Bookover operating rule is used to book water from one account to another and then back at the same reservoir, the reservoir
report (*.xwb) for the total reservoir (account 0) shows the water moving twice (once out and once back in) under the column 7,
From Carrier by Other. However, the reservoir report (*.xwb) for the individual accounts along with the operating rule reporting (*.xop) reflect the actual amount diverted. - See Section 7.5 for additional discussion on modeling reservoir operations, including bookovers.
| Row-data | Variable | Description |
|---|---|---|
| Control Data | ||
| 1 | Format (a12, a24, 12x, 4x, f12.5, f8.0, i8, 3(1x,a12,i8), i8, 1x,a12, 1x,a12,1x, 2f8.0, 2i8) | |
| 1-1 | cidvri(1) | Operational right ID |
| 1-2 | nameo(1) | Operational right name |
| 1-3 | rtem(1) | Administration number |
| 1-4 | dumx | Monthly and Structure Switch |
| 0 = No monthly on/off values | ||
| 12 = Number of monthly on/off switches provided | ||
| 1-5 | ioprsw(1) | Annual On/Off Switch |
| 0 = off | ||
| 1 = on | ||
| +n = Begin in year n | ||
| n = Stop after year n | ||
| Destination Data | ||
| 1-6 | ciopde | Destination reservoir ID |
| 1-7 | iopdes(2,1) | Destination structure account |
| For a reservoir destination, enter: | ||
| +n = Account served by this right | ||
| -n = Fill the first n accounts based on the ratio of their ownership | ||
| Supply Data | ||
| 1-8 | ciopso(1) | Supply reservoir ID |
| 1-9 | iopsou(2,1) | Supply reservoir account |
| 1-10 | ciopso(2) | If not required enter 0 |
| If limited by the amount diverted under an operating rule, enter the operating rule ID | ||
| If limited by a diversion demand amount enter the diversion structure ID | ||
| 1-11 | iopsou(4,1) | 0 = if ciopso(2) is 0 or an operating rule ID |
99 = if ciopso(2) is a diversion structure ID |
||
| Type Data | ||
| 1-12 | ityopr(1) | 6 |
| Associated Plan Data | ||
| 1-13 | creuse | NA |
| Diversion Type | ||
| 1-14 | cdivtyp | NA |
| Conveyance Loss (%) | ||
| 1-15 | OprLoss | 0 |
| Miscellaneous Limits | ||
| 1-16 | OprLimit | 0 if ciopso(2) is 0 |
1 if ciopso(2) is a operating rule and the user wants this (cidvri(1)) operating rule to not operate after the the operating rule specified by ciopso(2) operates. (See above for additional discussion of this capability). |
||
| Start Date | ||
| 1-17 | IoBeg | First year of operation |
| End Date | ||
| 1-18 | IoEnd | Last year of operation |
| Monthly Data | ||
| 2 | Free Format (Include only if the variable (dumx) = 12 or less than -12) |
|
| 2-1 | imonsw(1) | Monthly switch 0 = off, 1 = on |
| +n = Day first used that month | ||
| -n = Day last used that month | ||
| Note the first entry corresponds to the first month specified in the control file. |