Skip to content

Reservoir or Reuse or Accounting Plan to a User by Exchange (ityopr=28)

The type 28 operating rule provides a method to release water from a Reservoir, or ReUse Plan (type 4 or 6), or Out-of-Priority (OOP) Plan (type 9), or Accounting Plan (11), or Changed Water Right Plan (type 13) to a diversion, reservoir, instream flow, or carrier by exchange. In addition, it can be used to release water to an instream flow node or reach. The following are noted:

  • A “ReUse Plan” is a plan type that can be used identify the location of a reusable water supply associated with a CU transfer or transmountain import (see Section 7.8 for more details about plans).
  • An “Accounting Plan” is a plan type that is used for accounting only (see Section 7.8 for more details about plans).
  • An “OOP Plan” is a plan type that is associated with a diversion or storage taken out-of-priority by a type 38 operating rule.
  • A “Changed Water Right Plan” is a plan type that can be used to identify the location of water diverted by a Changed Water Right Operating Rule (type 26).
  • If the source is a Reuse, Accounting Plan or Changed Water Right, the destination may be reusable (i.e. creuse is a reuse plan (type 3 or 4).
  • If the source is an Changed Water Right Plan (plan type 13), the variable Oprlimit must have a value between 5 and 9.
  • If the source is a reservoir, the source data may be tied to an out-of-priority Plan (i.e. creuse is an OOP plan (type 9)).
  • If carrier losses are calculated (OprLoss>0), the return flow pattern and return locations are those assigned to the SOURCE (CARRIER) structure in the diversion station file (*.dds) (e.g. if the source is a water right tied to structure X, then the return flow pattern and locations are those provided for structure X in the diversion station file (*.dds)).
    • The variable OprLimit is used to constrain a release to to an operating rule that contains monthly and annual limits, the amount diverted by another operating rule or, if the source is a Changed Water Right, the operating rule that diverted the Changed Water Right. If the variable OprLimit set to 1 or 6, StateMod will warn the user a value of 1 or 6 are not currently operational but are reserved for potential future enhancements.
    • If the variable OprLimit is set to 2, 4 or 7, the operating rule ID specified in row 4’s monthly and annual limits will be decreased and limit the amount released.
    • If the variable OprLimit is set to 3, 4 or 8, the operating rule ID specified in row 4 or 5 will limit a release to the amount diverted byanother operating rule.
    • If the variable OprLimit is set to 4 or 9, the operating rule ID specified in row 4 should be an operating rule with monthly and annual limits (similar to Oprlimit = 2), the operating rule ID specified in row 5 should be the operating rule that will limit a release to the amount diverted by that operating rule (similar to OprLimit = 3).
    • If the variable OprLimit is set to 5, 7, 8 or 9, the source should be a Changed Water Right Plan (type 13) and operating rule ID specified in row 4, 5 or 6 should be the operating rule that diverted the Changed Water Right.
  • Terms and Conditions (T&C Plans) may be calculated if the source 2 variable (ciopso2) is set to a T&C plan. The variable iousou(4,1) is used to indicate how and when T&C demands are calculated.
    • If the user is implementing T&C on a changed water right, it is recommended the user implement Changed Water Rights plan operations (See Section 7.11 and Section 4.13.26) and associate the T&C plan when the water is released from the Changed Water Rights plan.
    • When ciopso2 = Plan ID and iopsou(4,1) = -1 the destination must be an accounting plan and the T&C Obligation is calculated when water is released from that Accounting plan using a type 27 or 28 rule.
    • When ciopso2 = Plan ID and iopsou(4,1) = 1 a standard return pattern is used to calculate the T&C Obligation. A Standard Return Pattern calculates the T&C Obligation to be:
      • \(\text{T&C Obligation (standard)} = (\text{Data in the return flow file (*.urm)}) \times ((\text{Released Water}) \times (1.0 - \text{CU Factor}))\) where the CU Factor is provided in row 5. The first value in a standard return flow table corresponds to the month diverted, the second to the month after a diversion, etc. Data that associates a Plan ID with any number of Return Flow Location(s), Percent(s), and Return Table ID(s) is provided in the plan Return File (*.prf).
    • When ciopso2 = Plan ID and iopsou(4,1) = 2 a fixed return pattern is used to calculate the T&C Obligation. A Fixed Return Pattern calculates the T&C Obligation to be:
      • \(\text{T&C Obligation (fixed)} = (\text{Data in the return flow file (*.urm)}) \times (\text{Released Water})\) The first value in a fixed return flow table corresponds to the first month in the simulation (e.g. January for a calendar year simulation), the second month to February (again for a calendar year simulation), etc. Data that associates a Plan ID with any number of Return Flow Location(s), Percent(s), and Return Table ID(s) is provided in the plan Return File (*.prf).
    • When ciopso2 = Plan ID and iopsou(4,1) = 3 a mixed return pattern is used to calculate the T&C Obligation. Mixed Return Pattern contains both a Standard and Fixed component and calculates the T&C Obligation to be:
      • \(\text{T&C Obligation (standard)} = (\text{Data in the return flow file (*.urm)}) \times ((\text{Released Water}) \times (1.0-\text{CU Factor}))\) where the CU Factor is provided in row 5. The first value in a standard return flow table corresponds to the month diverted, the second to the month after a diversion, etc. Data that associates a Plan ID with any number of Return Flow Location(s), Percent(s), and Return Table ID(s) is provided in the plan Return File (*.prf).
      • \(\text{T&C Obligation (fixed)} = (\text{Data in the return flow file (*.urm)}) \times (\text{Released Water})\) The first value in a fixed return flow table corresponds to the first month in the simulation (e.g. January for a calendar year simulation), the second month to February (again for a calendar year simulation), etc. Data that associates a Plan ID with any number of Return Flow Location(s), Percent(s), and Return Table ID(s)is provided in the plan Return File (*.prf).
    • When ciopso2 = Plan ID and iopsou(4,1) = 4 a default return pattern is used to calculate the T&C Obligation. A Default Return Pattern has a standard component that uses historic return flow data associated with the source water right to calculate the T&C Obligation.
    • If the variable ciopso2 is set to a T&C Plan ID and iopsou(4,1) is greater than zero then CU Factors are expected to be provided in card 5. Note the CU Factors typically represent negotiated values related to, but not necessarily the same as, the efficiency of the Transfer From Structure. Also these factors are only used when iopsou(4,1) = 1 (Standard Return) or 3 (Mixed Return) even though they are required as input.
  • Releases from a Plan by a Type 28 operating rule are reported in the Stream Report (*.xdd) as follows:
    • At the source, the water release to the destination is reported as Carried, Exchanged or Bypassed.
    • At the destination, the water diverted is reported as From River by Other.
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 Intervening Structure Switch
+n Number of intervening structures (max = 10)
12 Monthly (12) on/off values
-n Include -12 monthly on/off values minus n intervening structures. Note, when a negative value is provided, it should be -13 or less for 12 monthly values and one intervening structure
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 structure (diversion or reservoir or instream flow or plan)
1-7 iopdes(2,1) Destination structure account
For a diversion or plan or instream flow destination enter 1
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) ReUse Plan or Accounting Plan or Reservoir
1-9 iopsou(2,1) If ciopso(1) is a plan enter the ownership %
If ciopso(1) is a reservoir enter the account #
1-10 ciopso(2) T&C Plan ID (enter NA if none)
1-11 iopsou(4,1) 0 if ciopso(2) = NA
1 for a standard return pattern
2 for a fixed return pattern
3 for a mixed (standard and fixed) return pattern
Type Data
1-12 ityopr(1) 28
Associated Plan Data
1-13 creuse Reuse Plan ID (enter NA if none)
Diversion Type
1-14 cdivtyp Diversion or Depletion
If the destination is a reservoir set to Diversion
Conveyance Loss (%)
1-15 OprLoss 0 = No Transit loss
-1 = Provide intervening structure with loss data in row 3.
Miscellaneous Limits
1-16 OprLimit 0 = Do not constrain the release by another operating rule. Note OprLimit must be 5, 7, 8 or 9 if the source is an Changed Water Right Plan (type 13).
1 = Not operational. Preserved for potential enhancement.
2 = Decrease monthly and annual releases limits of the operational rule specified in row 4.
3 = Limit the amount released by the amount diverted by the operational rule in row 4 or row 5.
4 = Include the functionality of oprlimit = 2 in row 4 and oprlimit = 3 in row 5.
5 = If the source is a Changed Water Right Plan (type 13), enter the operational right ID that diverted the Changed Water Right.
6 = Not operational. Preserved for a potential enhancement.
7 = A combination of Oprlimit = 2 and 5.
8 = A combination of Oprlimit = 3 and 5.
9 = A combination of Oprlimit = 4 and 5.
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
Intervening Structure Data with loss
3 Free Format ( Include only if OprLoss > 0 or = -1 and the variable (dumx) = 1-10 or < -12. Note that intervening structure data without a loss is not operational, use a zero carrier loss to model these operations. See Section 7.11.4 for the approach used to model an augmentation station (e.g. a structure that carries a diversion, typically with loss, then returns non-lost water to the river).)
3b-1 intern(1,1) Intervening structure ID (e.g. a Diversion ID or Stream ID)
3b-2 OprLossC(l,1) Carrier Loss for Structure ID %
3b-3 InternT(1,1) Intervening Structure Type
Enter Carrier if it is a diversion structure located on the river
Enter Return if it is a return location on the River
Repeat for +dumx values
Associated Operating Rule
4 Free Format (Include only if the switch (OprLimit) = 2, 3, 4, 5, 7, 8 or 9)
4-1 cx If OprLimit = 2, 4, 7 or 9 Operating Rule ID with monthly and annual limits
If OprLimit = 3 or 8 Operating Rule ID that will LIMIT the amount released
If Oprlimit = 5, Operating Rule ID that diverted water to a Changed Water Right Plan (type 13)
Associated Operating Rule
5 Free Format (Include only if the switch (OprLimit) = 4, 7, 8 or 9)
5-1 cx If OprLimit = 4, 8 or 9 Operating Rule ID that will limit the amount diverted
If OprLimit = 7, Operating Rule ID that diverted water to a Changed Water Right Plan (type 13)
Associated Operating Rule
6 Free Format (Include only if the switch (OprLimit) = 9)
6-1 cx If OprLimit = 9, Operating Rule ID that diverted water to a Changed Water Right Plan (type 13)
T&C CU Factors
7 Free Format (Include only if ciopso(2) is a T&C Plan and iopsou(4,1) > 0. If iopsou(4,1) = 2 (fixed) or 4 (default) enter -1.0 since this data is not used.)
7-1 OprFac(1) CU factor in month 1
7-2 OprFac(2) CU factor in month 2
7-12 OprFac(12) CU factor in month 12
Repeat for number of return flow locations