Out-Of-Priority Reservoir Bookover (ityopr=8)
The type 8 operating rule works in concert with an out-of-priority diversion (type 38) to book water:
- From an out-of-priority reservoir account to another reservoir account or
- From an out-of-priority (OOP) plan to reduce its obligation.
This rule was significantly enhanced in order to address 1. Out out-of-priority diversions in addition to out-of-priority storage and 2. Out-of-priority storage and diversions occurring at more than one reservoir and diversion with regard to the same subordinated reservoir.
When the destination is a reservoir the out-of-priority diversion is typically kept in a separate account of the junior reservoir (e.g. an OOP account). Also an out-of-priority plan is used to track the amount taken. If the volume of water stored in the OOP plan exceeds the remaining capacity of the subordinated reservoir right, the Type 8 rule books water from the out-of-priority account to another general purpose account within the junior reservoir and the OOP plan obligation is reduced. To perform this activity the operating rule “associated” with the OOP diversion or storage being booked over must be known to the type 8 operating rule. If the subordinated reservoir right does not fill then a type 27 operating rule is typically used to transfer the water from the out-of-priority reservoir to the subordinated reservoir and adjust the obligation stored in the OOP Plan.
When the destination is an OOP Plan the out-of-priority diversion is stored under the OOP Plan. Once the volume of water stored in the OOP plan exceeds the remaining capacity of the subordinated reservoir right, the obligation stored in the OOP plan is reduced. To perform this activity the operating rule “associated” with the OOP diversion or storage being booked over must be known to the type 8 operating rule. If the subordinated reservoir right does not fill then a type 27 operating rule is typically used to transfer the water from a reservoir to the subordinated reservoir and adjust the obligation stored in the OOP Plan.
The following are noted:
- The variable
ciopso(2)(row-data 1-10) is used to identify the senior decree that is being subordinated. - The variable
intern(n,1)(rule n, value 1) is used to identify the junior decree that will be credited withdiverting water out of priority when booked over. - The variables
intern(n,2)(rule n, value 2) throughintern(n,10)(rule n, value 10) are used to identify up to 9 operating rules associated with this OOP plan. - If the destination is a reservoir all OOP diversions are charged against the junior reservoir’s water right when they are booked over to an account where they can be released.
- If the subordinated water right is not filled, the water stored out of priority is released to the subordinated reservoir at the end of the administration year
assigned to each reservoir (see variable
rdatein a reservoir station file (*.res)). - The type 8 operating rule has generic applications but was originally developed to handle the Blue River decree that allows OOP storage of water in Dillon Reservoir (an upstream junior reservoir), OOP storage of water in Blue Lake (an upstream reservoir), OOP diversion to Roberts Tunnel (an upstream junior diversion), and an OOP diversion to the Con Hoosier system before Green Mountain Reservoir (a downstream senior) is filled. See Section 7.16.1 for additional description of the Blue River Decree implementation to the Colorado River Basin.
| 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 switch |
| Enter 2 if no on/off switches are provided e.g. one for an associated Water Right and one for an associated operating Rule | ||
| Enter -14 if on/off switches are provided e.g. twelve on/off switches, one for an associated Water Right and one for an associated operating Rule | ||
| 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 or Plan ID |
| 1-7 | iopdes(2,1) | Destination structure account |
| For a reservoir destination, enter: | ||
| +n = Account to be served by this right | ||
| -n = Fill the first n accounts based on the ratio of their ownership | ||
| Supply Data | ||
| 1-8 | ciopso(1) | If the destination is a reservoir enter the supply reservoir ID (same as the destination ID) |
| If the destination is a Plan enter NA | ||
| 1-9 | iopsou(2,1) | If the destination is a reservoir enter the supply reservoir account |
| If the destination is a Plan enter NA | ||
| 1-10 | ciopso(2) | Supply (subordinated) water right ID |
| 1-11 | iopsou(4,1) | 0 |
| Type Data | ||
| 1-12 | ityopr(1) | 8 |
| Associated Plan Data | ||
| 1-13 | creuse | Out-of-Priority Plan ID |
| Diversion Type | ||
| 1-14 | cdivtyp | NA |
| Conveyance Loss (%) | ||
| 1-15 | OprLoss | 0 |
| Miscellaneous Limits | ||
| 1-16 | OprLimit | 0 |
| Start Date | ||
| 1-17 | IoBeg | First year of operation |
| End Date | ||
| 1-18 | IoEnd | Last year of operation |
| Monthly Data | ||
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 | ||
| Destination Water Right or Associated Reservoirs | ||
| 3 | Format (36x, 10a12) (Include only if the variable (dumx) = +n or < -12 ) |
|
| 3-1 | intern(1,1) | The destination water right ID (the one storing Out-of-Priority) |
| 3-2 | intern(1,2) | The OOP operational right associated with this bookover. Note must be provided in the *.opr file before the bookover right. |