2017 ORS 757.212¹
Resource rate plans
  • customers who may elect to be exempt
  • order approving plan
  • effect of approving plan
  • rules

(1) For purposes of this section:

(a) “Resource rate plan” means a plan by a public utility to construct a generating plant or to enter into a wholesale power purchase or sales agreement with a term that is longer than one year.

(b) “Site” means:

(A) Buildings or other related structures that are interconnected by facilities owned by a single public utility customer and that are served through a single electric meter; or

(B) A single contiguous area of land containing buildings or other structures that are separated by not more than 1,000 feet, such that:

(i) Each building or structure included in the site is not more than 1,000 feet from at least one other building or structure in the site;

(ii) Buildings and structures in the site, and land containing and connecting buildings and structures in the site, are owned by a public utility customer who is billed for electricity use at the buildings and structures; and

(iii) Land shall be considered to be contiguous even if there is an intervening public or railroad right of way, provided that rights-of-way land on which municipal infrastructure facilities exist, such as street lighting, sewerage transmission and roadway controls, shall not be considered contiguous.

(2) The Public Utility Commission may approve a resource rate plan as an alternative form of regulation plan under ORS 757.210 (Hearing to establish new schedules). A public utility must make a separate tariff filing for each proposed resource rate plan. If the commission approves a resource rate plan by a public utility based on the construction of a generating plant, the order approving the plan must state how the commission will reflect the costs and revenues of the generating plant in the utility’s rates during all or a portion of the expected useful life of the generating plant. If the commission approves a resource rate plan based on a wholesale power purchase or sales agreement with a term longer than one year, the order approving the plan must state how the commission will reflect the costs and revenues under the wholesale power purchase or sales agreement in the utility’s rates during all or a portion of the term of the agreement.

(3) A customer receiving electricity from a public utility may elect to be exempt from the costs and benefits of a resource rate plan for any single site at which the customer has had a peak load in excess of nine megawatts in any hour during the 12-month period immediately preceding the date on which the public utility files a tariff under this section. A public utility filing a tariff under this section must give written notice of the provisions of this subsection to all of its customers that are eligible to make an election under this subsection. The notice must be given within three days after the tariff is filed. An election under this subsection must be made by a customer within 30 days after the tariff is filed.

(4) A public utility customer that elects to be exempt under subsection (3) of this section may also elect to be exempt from the costs and benefits of a resource rate plan for any single site at which the customer has had a peak load in excess of one megawatt in any hour during the 12-month period immediately preceding the date on which the public utility files a tariff under this section. An election under this subsection must be made as part of the election under subsection (3) of this section.

(5) The commission shall ensure that customers making an election under subsection (3) or (4) of this section are charged the market cost for all electricity that is required to replace the electricity that would otherwise have been provided under the resource rate plan, and that the election does not result in increased costs or risks to the public utility or to other customers of the public utility.

(6) The commission, by rule, may allow customers of a public utility other than those customers described in subsection (3) of this section to elect to be exempt from the costs and benefits of a resource rate plan.

(7) If the commission approves a resource rate plan, the order of the commission must also address:

(a) The extent to which the public utility will use power from the generating plant or from the power purchase or sales agreement to serve its retail customers in Oregon;

(b) The allocation of power available from the generating plant or power purchase or sales agreement among different classes of the public utility’s customers;

(c) The ratemaking consequences of the generating plant or power purchase or sales agreement, including the consequences of variations in the amount of power that is actually available after the plan is in operation compared with the amount of power that was anticipated to be available at the time the plan was approved; and

(d) Any other issue the commission chooses to consider.

(8) If the commission approves a resource rate plan, the commission may not thereafter review the costs and rates specific to the resource rate plan or other obligations of the public utility under the plan, or consider any complaint under ORS 756.500 (Complaint) seeking review of the costs and rates specific to the resource rate plan or other obligations of the public utility under the plan, except for the purpose of determining whether the public utility is in compliance with the plan and has established rates in accordance with the plan.

(9) A resource rate plan and a public utility’s rates under a resource rate plan are not subject to ORS 757.355 (Costs of property not presently providing utility service excluded from rate base).

(10) The commission may not set aside or modify an order approving a resource rate plan unless the public utility operating under the plan approves the setting aside or modification. [2001 c.913 §2; 2005 c.638 §8]

Note: 757.212 (Resource rate plans) was added to and made a part of 757.205 (Filing schedules with commission) to 757.220 (Notice of schedule changes required) by legislative action but was not added to any smaller series therein. See Preface to Oregon Revised Statutes for further explanation.

Notes of Decisions

Public Utility Commissioner’s rule, which passed on utility expenses for pay­ment of county’s net business income tax to county ratepayers only, rather than to all utility ratepayers, was valid because com­mis­sioner is granted both broad regulatory authority over rates by ORS 756.040 (General powers) and broad rulemaking authority by ORS 756.060 (Authority to adopt rules and regulations). Multnomah County v. Davis, 35 Or App 521, 581 P2d 968 (1978), Sup Ct review denied

Chapter 757

Notes of Decisions

Under regulatory scheme, Public Utility Commissioner has authority to promulgate rule limiting telephone company’s liability for directory listing errors or omissions. Garrison v. Pacific NW Bell, 45 Or App 523, 608 P2d 1206 (1980)

Refund is proper exercise of Public Utility Commission’s general powers if refund (1) is based only on in­for­ma­­tion in existence at time of rate order for which refund is being made; (2) is not based on evalua­tion of public utility’s actual expenses or revenues; and (3) is not effectuated by offsetting future rates. Gearhart v. Public Utility Commission, 255 Or App 58, 299 P3d 533 (2013), aff’d 356 Or 216, 339 P3d 904 (2014)

Atty. Gen. Opinions

Authority of Governor and Public Utility Commissioner to enter into binding agree­ments with respect to uniform curtail­ment plans, (1977) Vol 38, p 861

1 Legislative Counsel Committee, CHAPTER 757—Utility Regulation Generally, https://­www.­oregonlegislature.­gov/­bills_laws/­ors/­ors757.­html (2017) (last ac­cessed Mar. 30, 2018).
 
2 Legislative Counsel Committee, Annotations to the Oregon Revised Stat­utes, Cumulative Supplement - 2017, Chapter 757, https://­www.­oregonlegislature.­gov/­bills_laws/­ors/­ano757.­html (2017) (last ac­cessed Mar. 30, 2018).
 
3 OregonLaws.org assembles these lists by analyzing references between Sections. Each listed item refers back to the current Section in its own text. The result reveals relationships in the code that may not have otherwise been apparent.