***MASTER REGIONAL DIALOGUE***

***CONTRACT TEMPLATE***

*This template shows the similarities and differences between individual
templates. It contains the clauses that are either identical or nearly
identical for all templates (Load Following, Block, Slice/Block, RPSA,
and NR Block). It does NOT contain clauses that are unique to the
following templates: Slice/Block, RPSA, and NR Block. **It does not
identify all differences and should be used only as a general guide. ***

*1.* Black non-italicized text indicates draft contract language.

*2. **[All text in italics will be deleted]{.underline}** before the
contracts are finalized.*

> *(a) **Pink italicized text** indicates [notes to BPA AEs and contract
> staff]{.underline} who will tailor the template for each particular
> customer within the limits stated. Pink text will be deleted after
> August 1 when the template is converted to a contract for each
> particular customer.*
>
> *(b) **Blue italicized text** indicates [notes to the reviewers
> (customers and others.)]{.underline} This blue text will be deleted
> after the draft template is finalized on August 1.*
>
> *(c)* **Red text** indicates where a drafter must 'fill-in-the-blank.'
> Red text will be converted to black text and will become part of the
> final contract.
>
> *(d) **Green italicized text** indicates contract provisions that are
> unique to the Load Following, Block, and Slice/Block prototype
> templates. Green text will be deleted whenever the Master Template is
> split out into the individual templates.*

*3. Grey shaded text is used to help reviewers of the template
understand how different versions of a particular clause are [either the
same or different,]{.underline} and is most often used to help reviewers
understand subtle variations between the Load Following, Block and
Slice/Block templates. The shading will be deleted when the templates
are finalized*

> **[Pacific Northwest Investor-Owned Utilities' Interlineated
> Comments]{.mark}**
>
> **[and Revisions---July 14, 2008]{.mark}**
>
> Contract No. 09PB-«#####»
>
> **DRAFT** 7/2/2008 3:16 PM

**POWER SALES AGREEMENT**

**executed by the**

**BONNEVILLE POWER ADMINISTRATION**

**and**

**«FULL NAME OF CUSTOMER»**

**Table of Contents**

**Section Page**

> **1. T****erm**
>
> **2. Definitions**
>
> *Include for **BLOCK**: Drafter's Note: Delete the Block product not
> purchased. END*
>
> **3. Load Following Power Purchase Obligation or Block Power Purchase
> Obligation Without Shaping Capacity or Block Power Purchase\
> Obligation With Shaping Capacity or Slice/Block Power Purchase
> Obligation *CHANGE title to reflect the product purchased***
>
> **4. This Section Intentionally Left Blank**
>
> **5. This Section Intentionally Left Blank**
>
> **6. Tiered Rate Methodology**
>
> **7. High Water Marks**
>
> **8. Applicable Rates**
>
> **8.1 Priority Firm Power Rates and Contract High Water Mark**
>
> **1. PF Tier 1 and PF Tier 2 Rates**
>
> **2. Contract Demand Quantities**
>
> **8.2 New Resource Firm Power Rate**
>
> **8.3 Firm Power Products and Services Rate**
>
> **8.4 Additional Charges**
>
> **8.5 Resource Support Services**
>
> **9. Elections to Purchase Power Priced at PF Tier 2 Rates**
>
> **10. Order of Tier 2 Remarketing and Resource Removal**
>
> **11. One-Time Right to Change Purchase Obligation**
>
> **12. Billing Credits and Residential Exchange**
>
> **13. Scheduling**
>
> **14. Delivery**
>
> **15. Metering**
>
> **16. Billing and Payment**
>
> **17. Information Exchange and Confidentiality**
>
> **18. Conservation and Renewables**
>
> **19. Resource Adequacy**
>
> **20. Notices and Contact Information**
>
> **21. Uncontrollable Forces**
>
> **22. Governing Law and Dispute Resolution**
>
> **23. No Warranty**
>
> **24. Statutory Provisions**
>
> **24.1 Retail Rate Schedules**
>
> **24.2 Insufficiency and Allocations**
>
> **24.3 New Large Single Loads and CF/CTs**
>
> **24.4 Priority of Pacific Northwest Customers**
>
> **24.6 Prohibition on Resale**
>
> **24.7 Use of Regional Resources**
>
> **24.8 BPA Appropriations Refinancing**
>
> **25. Standard Provisions**
>
> **25.1 Amendments**
>
> **25.2 Entire Agreement and Order of Precedence**
>
> **25.3 Assignment**
>
> **25.4 No Third-Party Beneficiaries**
>
> **25.5 Waivers**
>
> **25.6 BPA Policies**
>
> **25.7 Rate Covenant and Payment Assurance**
>
> **25.8 Bond Assurances**
>
> **26. Termination**
>
> **27. Signatures**
>
> **Exhibit A Net Requirements and Resources**
>
> **Exhibit B High Water Marks and Contract Demand Quantities**
>
> **Exhibit C Purchase Obligations**
>
> **Exhibit D Additional Products and Special Provisions**
>
> **Exhibit E Metering**
>
> *[Drafter's Note]{.underline}: Choose title of Exhibit F to reflect
> scheduling option*
>
> **Exhibit F «Transmission Scheduling Service or Scheduling»**
>
> *Option 1: Include for customer served by Transfer Service*
>
> **Exhibit G Principles of Non-Federal Transfer Service**
>
> *END Option 1*
>
> *Option 2: Include for Non-transfer service customers*
>
> **Exhibit G This Exhibit Intentionally Left Blank**
>
> *END Option 2*
>
> **Exhibit H Renewable Energy Certificates and Carbon Attributes**

This POWER SALES AGREEMENT (Agreement) is executed by the UNITED STATES
OF AMERICA, Department of Energy, acting by and through the BONNEVILLE
POWER ADMINISTRATION (BPA), and «FULL NAME OF CUSTOMER» («Customer
Name»), hereinafter individually referred to as "Party" and collectively
referred to as the \"Parties\". «Customer Name» is a «public utility
district, people's utility district, non-profit corporation, municipal
corporation, mutual association tribal utility, federal agency»,
organized and authorized under the laws of the State of «State», to
purchase and distribute electric power to serve retail consumers from
its distribution system within its service area. *[Drafter's
Note]{.underline}: modify the previous sentence for tribal utilities and
federal agencies to reflect their legal status independent of the
state[.]{.mark}*[\[\[BPA's authority to sell power under section 5(b) of
the Northwest Power Act is limited to sales to a]{.mark} ["public body,
cooperative or investor-owned utility]{.mark} [in the Region " and to
"Federal agencies in the region." The list of entities above]{.mark}
[does not include investor-owned utility, apparently because this clause
is not applicable to the NR Block template---this should be
clarified.]{.mark} [Also, the phrase "mutual association tribal utility"
is unclear---is there a missing comma between "mutual association" and
"tribal utility"? If so, this should be clarified.]{.mark}
[Further,]{.mark} [the list above]{.mark} [should not include non-profit
corporation or mutual association insofar as those entities are not a
"public body, cooperative or investor-owned utility in the Region" or
any "Federal agencies in the region."\]\]]{.mark}

RECITALS***(06/05/08 Version)***

«Customer Name»'s current power sales agreement (Contract
No. «##PB‑#####») continues through September 30, 2011, and will be
replaced by this Agreement on October 1, 2011.

BPA has functionally separated its organization in order to separate the
administration and decision-making activities of BPA's power and
transmission functions. References in this Agreement to Power Services
or Transmission Services are solely for the purpose of clarifying which
BPA function is responsible for administrative activities that are
jointly performed.

BPA is authorized to market federal power to qualified entities that are
eligible to purchase such power. Under section 5(b)(1) of the Pacific
Northwest Electric Power Planning and Conservation Act, P.L. 96‑501 of
1980 (Northwest Power Act), BPA is obligated to offer a power sales
agreement to eligible customers for the sale and purchase of federal
power to serve their retail consumer load in the Region that is not met
by the customer's use of its non-federal resources.

BPA has proposed the adoption of a tiered rates pricing methodology for
federal power sold to meet BPA's obligations under section 5(b) of the
Northwest Power Act to eligible customers, in order to maintain the
benefits of the federal system in the future and encourage BPA customers
to develop regional power resource infrastructure to meet regional
consumer loads under this Agreement.

To effect that purpose, in this Agreement BPA establishes a Contract
High Water Mark for «Customer Name» that will define the amounts of
power «Customer Name» may purchase from BPA at the Tier 1 rate, as
defined in BPA's Tiered Rate Methodology.

The Parties agree:

> *[Option 1]{.underline}: Include the following for customers who do
> NOT need RUS approval. (See Customer Characteristic Spreadsheet or
> Janet Rickman)*

**1. TERM*(06/30/08 Version)***

> This Agreement takes effect on the date signed by the Parties and
> expires on September 30, 2028. Performance by BPA and «Customer Name»
> shall commence on October 1, 2011, with the exception of those actions
> required prior to that date that are included in:
>
> \(1\) section 3, Power Purchase Obligation;
>
> \(2\) section 9, Elections to Purchase Power Priced at PF Tier 1
> Rates;
>
> \(3\) section 17, Information Exchange and Confidentiality;
>
> \(4\) section 18, Conservation and Renewables;
>
> \(5\) section 19, Resource Adequacy;
>
> \(6\) section 22, Governing Law and Dispute Resolution;
>
> \(7\) section 26, Termination;
>
> \(8\) Exhibit A, Net Requirements and Resources;
>
> \(9\) Exhibit B, High Water Marks and Contract Demand Quantities; and,
>
> \(10\) Exhibit C, Purchase Obligations.
>
> Section 22, Governing Law and Dispute Resolution will only apply to
> the extent there is a dispute regarding actions required after the
> Effective Date in the above referenced sections and exhibits.
>
> *END Option 1*
>
> *[Option 2]{.underline}: Include the following for customers who must
> obtain RUS approval to execute this Agreement. (See Customer
> Characteristics Spreadsheet or Janet Rickman)*

**1. TERM*(06/30/08 Version)***

> This Agreement takes effect on the date signed by the Parties and
> expires on September 30, 2028, subject to approval of the United
> States Department of Agriculture Rural Utilities Service. Performance
> by BPA and «Customer Name» shall commence on October 1, 2011, with the
> exception of those actions required prior to that date that are
> included in:
>
> \(1\) section 3, Power Purchase Obligation;
>
> \(2\) section 9, Elections to Purchase Power Priced at PF Tier 1
> Rates;
>
> \(3\) section 17, Information Exchange and Confidentiality;
>
> \(4\) section 18, Conservation and Renewables;
>
> \(5\) section 19, Resource Adequacy;
>
> \(6\) section 22, Governing Law and Dispute Resolution;
>
> \(7\) section 26, Termination;
>
> \(8\) Exhibit A, Net Requirements and Resources;
>
> \(9\) Exhibit B, High Water Marks and Contract Demand Quantities; and,
>
> \(10\) Exhibit C, Purchase Obligations.

Section 22, Governing Law and Dispute Resolution will only apply to the
extent there is a dispute regarding actions required after the Effective
Date in the above referenced sections and exhibits.

*END Option 2*

**2. DEFINITIONS** ***(06/05/08 Version)***

> Capitalized terms below shall have the meaning stated. Capitalized
> terms that are not listed below are either defined within the section
> in which the term is used, or if not so defined, shall have the
> meaning stated in BPA's applicable Wholesale Power Rate Schedules,
> including the General Rate Schedule Provisions (GRSPs).

1.  "Above-RHWM Load"***(06/11/08 Version)*** means forecasted annual
    Total Retail Load that is above «Customer Name»'s RHWM.

2.  "Annexed Load"***(05/15/08 Version)*** means existing load and
    distribution system, and/or service territory «Customer Name»
    acquires from another utility, by means of annexation, merger,
    purchase or trade, and authorized by a final state, regulatory or
    court action, for which «Customer Name» has the right, [and]{.mark}
    has obtained an ownership interest in the facilities necessary, to
    serve the load.

3.  "Balancing Authority"***(06/10/08 Version)*** means the responsible
    entity that integrates resource plans ahead of time, maintains
    load-interchange-generation balance within a Balancing Authority
    Area, and supports interconnection frequency in real time.

4.  "Balancing Authority Area"***(06/10/08 Version)*** means the
    collection of generation, transmission, and loads within the metered
    boundaries of the Balancing Authority. The Balancing Authority
    maintains load-resource balance within this area.

5.  "Business Day(s)"***(05/13/08 Version)*** means every Monday through
    Friday except federal holidays.

6.  "Consumer-Owned Resource"***(06/16/08 Version)*** means a Generating
    Resource connected to «Customer Name»'s distribution system that is
    owned by a retail consumer, has a nameplate capability greater than
    200 kilowatts, and is operated or applied to load on a sustained
    basis rather than operated occasionally or intermittently as a
    back-up energy source at times of maintenance or forced outage.

7.  "Contract Demand Quantities" or "CDQ"***(06/11/08 Version)*** shall
    have the meaning as defined in section 6.6.1.

8.  "Contract High Water Mark" or "CHWM"***(06/11/08 Version)*** shall
    have the meaning as defined in section 6.6.1.

9.  "Contract High Water Mark Contract" or "CHWM Contract"***(05/15/08
    Version)*** means a Regional Dialogue Contract that contains a CHWM,
    allowing the customer to purchase power at tiered rates, or as
    defined in the TRM.

10. "Contract Resources"***(07/02/08 Version)*** means any sources or
    amounts of electric power that «Customer Name» acquires from
    identified or unidentified electricity-producing units by contract
    purchase from an [identified]{.mark} electricity supplier, and for
    which the amounts received by «Customer Name» do not depend on the
    same actual production from an identified Generating Resource.

11. "Diurnal" ***(07/01/08 Version)*** means the distribution of hours
    of months between Heavy Load Hours (HLH) and Light Load Hours (LLH).
    HLH and LLH are as defined by the North American Electric
    Reliability Corporation (NERC) and are subject to change by the
    NERC.

12. "Dedicated Resource(s)" ***(05/28/08 Version)*** means those
    Specified Resources and Unspecified Resource Amounts that «Customer
    Name» obligates itself to provide or is required by statute to
    provide under this Agreement for use to serve its Total Retail Load.

*Include in **BLOCK** template:*

13. "Diurnal Distribution Factors"***(05/27/08 Version)*** are as
    established in section 1.2.2.1 of Exhibit C, Purchase Obligations.

*END **BLOCK** template.*

14. "Diurnal Flattening Service" or "DFS"***(06/16/08 Version)*** means
    the service that converts the hour to hour output from a resource
    into a shape that is flat within each of the 24 HLH and LLH periods
    of a year.

15. "Due Date"***(05/25/08 Version)*** shall have the meaning as
    described in section 16.2 of this Agreement.

16. "Effective Date"***(06/05/08 Version)*** means the date on which
    this Agreement has been signed by «Customer Name» and BPA.

17. "Environmental Attribute(s)"***(04/04/08 Version)*** shall have the
    meaning as defined in Exhibit H, Renewable Energy Certificates and
    Carbon Attributes.

18. "Environmentally Preferred Power RECS" or "EPP RECs"***(04/01/08
    Version)*** shall have the meaning as defined in Exhibit H,
    Renewable Energy Certificates and Carbon Attributes.

19. "Existing Resources"***(05/27/08 Version)*** means those Specified
    Resources listed in section 2 of Exhibit A that were dedicated to
    «Customer Name»'s Total Retail Load prior to October 1, 2006.

20. "Firm Requirements Power"***(06/05/08 Version)*** means federal
    power that BPA sells under this Agreement and makes continuously
    available to «Customer Name» under this Agreement, except for an
    Uncontrollable Force, to meet BPA's obligations to «Customer Name»
    under section 5(b) of the Northwest Power Act.

21. "Fiscal Year" or "FY"***(02/28/08 Version)*** means the period
    beginning each October 1 and ending the following September 30.

*Include in **LOAD FOLLOWING** template:*

22. "Flat Annual Shape"***(05/27/08 Version)*** means the shape of the
    Dedicated Resource amounts are shown in equal average megawatt
    amounts for each month within a year.

*END **LOAD FOLLOWING** template.*

*Include in **LOAD FOLLOWING** template:*

23. "Flat Within-Month Shape"***(05/27/08 Version)*** means the shape of
    the Dedicated Resource amounts are shown in equal megawatt amounts
    for each hour within a month.

*END **LOAD FOLLOWING** template.*

24. "Forced Outage Reserve Service" or "FORS"***(06/30/08 Version)***
    means the service that provides an agreed-to amount of capacity and
    energy to load during the forced outages of a resource, transmission
    line, or other asset.

25. "Forecast Year"***(05/27/08 Version)*** means the Fiscal Year ending
    one full year prior to the commencement of a Rate Period.

26. "Generating Resources"***(05/28/08 Version)*** means any sources or
    amounts of electric power from identified electricity-producing
    units, and for which the amounts of power received by «Customer
    Name» or «Customer Name»'s retail consumer are determined by the
    actual power production from such identified electricity-producing
    units. Such units may be owned by «Customer Name» or «Customer
    Name»'s retail consumer in whole or in part, or the output from such
    units may be owned for a defined period by contract.

*Include in **LOAD FOLLOWING** template:*

27. "HLH Diurnal Shape"***(05/27/08 Version)*** means a distribution of
    energy between the Diurnal periods in which more megawatt-hours per
    hour are applied in the Heavy Load Hour (HLH) periods than
    megawatt-hours per hour applied in the Light Load Hour (LLH)
    periods. Such distributions are determined by «Customer Name»
    consistent with section 8.2 of Exhibit A, Net Requirements and
    Resources.

*END **LOAD FOLLOWING** template.*

28. "Integrated Network Segment"***(05/29/08 Version)*** shall have the
    meaning as defined in section 14.1.

29. "Interchange Points"***(04/01/08 Version)*** means the points where
    Balancing Authority Areas interconnect, and at which the interchange
    of energy between Balancing Authority Areas is monitored and
    measured.

*Include in **BLOCK** template:*

30. "Monthly Distribution Factors"***(05/27/08 Version)*** are as
    established in section 1.2.1.1 of Exhibit C, Purchase Obligations.

*END **BLOCK** template.*

31. "Net Requirement"***(05/15/08 Version)*** means the amount of
    federal power that a customer is entitled to purchase from BPA to
    serve its Total Retail Load minus its Dedicated Resource amounts as
    shown in Exhibit A, Net Requirements and Resources, consistent with
    section 5(b)(1) of the Northwest Power Act.

32. "Network Integration Transmission Service"***(05/29/08 Version)***
    shall have the meaning as defined in section 14.1.

33. "Network Resource"***(05/29/08 Version)*** shall have the meaning as
    defined in section 14.1.

34. "New Large Single Load" or "NLSL"***(06/05/08 Version)*** has the
    meaning specified in section 3(13) of the Northwest Power Act and in
    BPA's NLSL policy.

35. "New Resources" ***(05/27/08 Version)*** means those Specified
    Resources listed in section 2 of Exhibit A that were or are
    [first]{.mark} dedicated to «Customer Name»'s Total Retail Load
    after September 30, 2006, and any Unspecified Resource Amounts
    listed in section 3.1 of Exhibit A.

36. "Notice Deadlines"***(05/27/08 Version)*** are as established in
    section 9.1.1 of the body of this Agreement.

37. "Onsite Consumer Load"***(06/30/08 Version)*** means retail consumer
    electric loads of «Customer Name» that are electrically
    interconnected directly with a Consumer-Owned Resource, that are
    entirely within «Customer Name»'s service territory or on an
    integrated portion of «Customer Name»'s distribution system, that
    consume energy generated by such Consumer-Owned Resource, and that
    require no schedule of power from such Consumer-Owned Resource.

38. "Operating Year"***(03/27/08 Version)*** means the period, beginning
    each August 1 and ending the following July 31, that is designated
    under the Pacific Northwest Coordination Agreement (PNCA) for
    resource planning and operational purposes.

39. "Point of Delivery" or "POD"***(05/15/08 Version)*** means the point
    where power is transferred from a transmission provider to «Customer
    Name».

40. "Point of Metering" or "POM"***(05/15/08 Version)*** means the point
    at which power is measured.

41. "Power Services"***(09/04/07 Version)*** means the organization, or
    its successor organization, within BPA that is responsible for the
    management and sale of federal power from the Federal Columbia River
    Power System.

*Include in **LOAD FOLLOWING** template:*

42. "PNCA Update Shape" ***(05/27/08 Version)*** means the shape
    «Customer Name»'s dedicated hydro resource amounts will be revised
    each Fiscal Year per the results of the final PNCA planning
    hydro-regulation study published for the Operating Year that began
    on the August 1 immediately preceding the Fiscal Year. If the final
    study is not published 30 days prior to the beginning of the Fiscal
    Year, the shape of «Customer Name»'s dedicated hydro resource
    amounts will be revised per the results of the modified PNCA study
    published for the same Operating Year. The August and September
    amounts published for the Operating Year will be used as the August
    and September amounts for the Fiscal Year.

*END **LOAD FOLLOWING** template.*

43. "Primary Points of Receipt"***(05/29/08 Version)*** shall have the
    meaning as defined in section 14.1.

44. "Purchase Periods"***(05/27/08 Version)*** are as established in
    section 9.1.1 of the body of this Agreement.

45. "Rate Case Year"***(05/27/08 Version)*** means the Fiscal Year
    ending prior to the commencement of a Rate Period. The Rate Case
    Year immediately follows the Forecast Year and is the year in which
    the general rate case is conducted.

46. "Rate Period"***(05/13/08 Version)*** means the effective period of
    a particular rate schedule, generally two years; the period over
    which a rate is designed to recover costs allocated to it.

47. "Rate Period High Water Mark" or "RHWM"***(06/11/08 Version)***
    shall have the meaning as defined in section 6.6.1.

48. "Region"***(09/04/07 Version)*** means the Pacific Northwest as
    defined in the Northwest Power Act.

49. "Renewable Energy Certificates" or "RECs"***(05/29/08 Version)***
    shall have the meaning as defined in Exhibit H, Renewable Energy
    Certificates and Carbon Attributes.

*Include in **LOAD FOLLOWING** template:*

50. "Resource Diurnal Shape"***(05/27/08 Version)*** means the Diurnal
    shape in which the Generating Resource, listed in section 2.1 of
    Exhibit A, Net Requirements and Resources, were initially dedicated
    pursuant to section 3.3.1 of this Agreement.

*END **LOAD FOLLOWING** template.*

*Include in **LOAD FOLLOWING** template:*

51. "Resource Monthly Shape"***(05/27/08 Version)*** means the monthly
    shape in which the Generating Resource, listed in section 2.1 of
    Exhibit A, Net Requirements and Resources, were initially dedicated
    pursuant to section 3.3.1 of this Agreement.

*END **LOAD FOLLOWING** template.*

*Include in **LOAD FOLLOWING** template:*

52. "Resource Supports Services" or "RSS" ***(06/30/08 Version)*** means
    the Diurnal Flattening Service, Forced Outage Reserve Service,
    Secondary Crediting Service, and any other related service BPA
    provides to support resources.

*END **LOAD FOLLOWING** template.*

*Include in **BLOCK** and **SLICE/BLOCK** template:*

53. "Resource Supports Services" or "RSS" ***(06/30/08 Version)*** means
    the Diurnal Flattening Service, Forced Outage Reserve Service, and
    any other related service BPA provides to support resources that are
    renewable resources and are dedicated to load after September 30,
    2006.

*END **BLOCK** and **SLICE/BLOCK** template.*

54. "Scheduling Points of Receipt"***(05/29/08 Version)*** shall have
    the meaning as defined in section 14.1.

*Include in **LOAD FOLLOWING** template:*

55. "Secondary Crediting Service" or "SCS"***(06/30/08 Version)*** means
    the service that provides a monetary credit for the secondary output
    from an Existing Resource that has a firm critical component and a
    secondary energy component.

*END **LOAD FOLLOWING** template.*

*Include in **BLOCK** template:*

56. "Shaping Capacity"***(05/27/08 Version)*** is as established in
    section 1.4 of Exhibit C, Purchase Obligations.

*END **BLOCK** template.*

*Include in **LOAD FOLLOWING** template:*

57. "Small Non-Dispatchable Resources"***(05/27/08 Version)*** means
    those Specified Resources connected to «Customer Name»'s
    distribution system the output of which cannot be shifted between
    Diurnal periods or days by the resource owner or operator. Such
    resources are further defined as:

> \(1\) Existing Resources that individually have a nameplate capability
> less than or equal to 3.000 megawatts, or
>
> \(2\) New Resources that have a nameplate capability less than or
> equal to 1.000 megawatt, both individually and in aggregate for all
> such resources of «Customer Name».

*END **LOAD FOLLOWING** template.*

58. "Specified Resources"***(06/30/08 Version)*** means Generating
    Resources or Contract Resources that have nameplate capabilities or
    maximum hourly purchase amounts greater than 200 kilowatts, that
    «Customer Name» has named and that «Customer Name» is required by
    statute or agrees to dedicate to serve its Total Retail Load. Such
    resources are identified as specific non-federal resources or as
    specific contracts with identified parties.

59. "Statement of Intent"***(05/27/08 Version)*** shall have the meaning
    as defined in section 2.3 of Exhibit C, Purchase Obligations.

*Include in **LOAD FOLLOWING** template:*

60. "Super Peak Hours"***(06/05/08 Version)*** means the hours BPA
    defines, consistent with the TRM, each Rate Period in which
    «Customer Name» must provide additional capacity from its Dedicated
    Resources to receive a Super Peak Resource Credit consistent with
    the TRM.

*END **LOAD FOLLOWING** template.*

*Include in **LOAD FOLLOWING** template:*

61. "Super Peak Resource Credit"***(06/05/08 Version)*** means a
    reduction in «Customer Name»'s demand billing determinants,
    consistent with the TRM, equal to the amount of additional capacity
    provided by a Dedicated Resource, during Super Peak Hours, over the
    amount of capacity that would have been provided by an equivalent
    amount of energy delivered flat across the monthly HLH period.

*END **LOAD FOLLOWING** template.*

62. "Surplus Firm Power"***(02/28/08 Version)*** means firm power that
    is in excess of BPA's obligations under sections 5(b), 5(c), and
    5(d) of the Northwest Power Act, as available.

63. "Third Party Transmission Provider"***(03/17/08 Version)*** means a
    transmission provider other than BPA that delivers power to
    «Customer Name».

64. "Tier 1 RECs"***(05/29/08 Version)*** shall have the meaning as
    defined in Exhibit H, Renewable Energy Certificates and Carbon
    Attributes.

65. "Tier 2 RECs"***(05/29/08 Version)*** shall have the meaning as
    defined in Exhibit H, Renewable Energy Certificates and Carbon
    Attributes.

66. "Tier 2 Cost Pool"***(06/16/08 Version)*** shall have the meaning as
    defined in Exhibit H, Renewable Energy Certificates and Carbon
    Attributes.

67. "Total Retail Load"***(06/05/08 Version)*** means all retail
    electric power consumption, including electric system losses, within
    «Customer Name»'s electrical system excluding:

> \(1\) nonfirm or interruptible loads agreed to by the Parties,
>
> \(2\) transfer loads of other utilities served by «Customer Name», and
>
> \(3\) any loads not on «Customer Name»'s electrical system that are
> not specifically agreed to by BPA.

*Include in **LOAD FOLLOWING** template:*

68. "Total Retail Load Monthly Shape"***(05/27/08 Version)*** means the
    distribution among months of «Customer Name»'s annual Total Retail
    Load, listed in the table in section 8.1 of Exhibit A. The FY 2010
    Total Retail Load Monthly Shape from the table will apply for the
    FY 2012-2014 and FY 2015-2019 Purchase Periods; the FY 2015 Total
    Retail Load Monthly Shape will apply for the FY 2020-FY 2024
    Purchase Period; and the FY 2020 Total Retail Load Monthly Shape
    will apply for the FY 2025-2028 Purchase Period.

*END **LOAD FOLLOWING** template.*

69. "Transfer Service"***(03/17/08 Version)*** means the transmission,
    distribution and other services provided by a Third Party
    Transmission Provider to deliver electric energy and capacity over
    its transmission system.

70. "Transmission Services"***(09/04/07 Version)*** means the
    organization, or its successor organization, within BPA that is
    responsible for the management and sale of transmission service on
    the Federal Columbia River Transmission System [(FCRTS).]{.mark}

71. "Uncontrollable Force"***(05/25/08 Version)*** shall have the
    meaning as defined in section 21.1.

72. "Unspecified Resource Amounts**"*(03/21/08 Version)*** means an
    amount of firm power «Customer Name» has agreed to supply and
    dedicate to serve its Total Retail Load and which is not attributed
    to a particular Generating Resource or Contract Resource.
    ["Unspecified Resource Amounts"]{.mark} [shall be]{.mark} [limited
    to]{.mark}

> [(i) market purchases that are to serve load that does not match the
> customer's existing resources and delivery of Federal power from time
> to time;]{.mark} [*provided*, that]{.mark} [«Customer Name»
> shall]{.mark} [make any such market purchases to serve that portion of
> load that does not match such customer's existing resources and
> delivery of Federal power under all such circumstances, and]{.mark}
>
> []{.mark}
>
> [(ii) Unspecified Resource Amounts]{.mark} [inserted by BPA]{.mark}
> [pursuant]{.mark} [to section 3.2 of Exhibit A for]{.mark} [Northwest
> Power Act Section 9(c) or Regional Preference Act Section 3(d) Export
> Decrements pursuant to section 3.5.2 of the body of this
> Agreement.]{.mark}

[]{.mark}

> [\[\[Comment:]{.mark} [The use of]{.mark} ["Unspecified Resource
> Amounts**"**]{.mark} [in the draft templates must be eliminated or
> circumscribed, consistent with the language and intent of section
> 5(b)(1) of the Northwest Power Act. The above language edit parallels
> the 5(b) 9(c) Policy, which requires "a customer who elects to use
> market purchases to serve load that does not match the customer's
> existing resources and delivery of Federal power from time to time
> shall make such market purchases to serve that portion of load that
> does not match such customer's existing resources and delivery of
> Federal power under all such circumstances." 5(b) 9(c) Policy, page
> 5.\]\]]{.mark}

*Include in **LOAD FOLLOWING** template:*

**3. LOAD FOLLOWING POWER PURCHASE OBLIGATION*(06/30/08 Version)***

> 3.1 **Purchase Obligation**
>
> From October 1, 2011, and continuing through September 30, 2028, BPA
> shall sell and make available, and «Customer Name» shall purchase,
> Firm Requirements Power in hourly amounts equal to «Customer Name»'s
> hourly Total Retail Load minus the hourly firm energy from each of
> «Customer Name»'s Dedicated Resources as listed in Exhibit A, Net
> Requirements and Resources, and pursuant to section 3.3 below.
>
> 3.2 **Take or Pay**
>
> «Customer Name» shall pay for the amount of power it has committed to
> purchase under section 3.1 of this Agreement, at the rates BPA
> establishes as applicable to such power, whether or not «Customer
> Name» took actual delivery of such power.
>
> 3.3 **List and Application of Dedicated Resources**
>
> «Customer Name» agrees to dedicate those resources for service to its
> Total Retail Load that it has listed as Dedicated Resources in
> Exhibit A as follows:
>
> \(1\) Specified Resources that are Generating Resources, except Small,
> Non-Dispatchable Resources, shall be listed in section 2.1 of
> Exhibit A,
>
> \(2\) Specified Resources that are Contract Resources shall be listed
> in section 2.2 of Exhibit A,
>
> \(3\) Specified Resources that are Small, Non-Dispatchable Resources
> shall be listed in section 2.3 of Exhibit A, and
>
> \(4\) Unspecified Resource Amounts shall be listed in section 3.1 of
> Exhibit A.
>
> «Customer Name» shall specify its Dedicated Resource amounts, and
> shall apply its Dedicated Resources to its Total Retail Load, as
> stated below for each specific resource and type:
>
> 3.3.1 **Specified Resources**
>
> 3.3.1.1 **Application of Specified Resources**
>
> «Customer Name» shall apply the output of all Specified Resources,
> listed in section 2 of Exhibit A, Net Requirements and Resources, to
> «Customer Name»'s Total Retail Load in predefined hourly amounts
> consistent with section 3.8 below, except for Small Non-Dispatchable
> Resources and Specified Resources «Customer Name» is supporting with
> DFS or SCS from BPA. «Customer Name» shall apply all Specified
> Resources supported with DFS or SCS from BPA to «Customer Name»'s
> Total Retail Load consistent with section 2 of Exhibit D, Additional
> Products and Special Provisions. «Customer Name» shall apply all of
> the output from its Small Non-Dispatchable Resources, listed in
> section 2.3 of Exhibit A, Net Requirements and Resources, to «Customer
> Name»'s Total Retail Load.
>
> 3.3.1.2 **Specified Resource Energy Amounts**
>
> «Customer Name» shall state firm energy amounts for each Specified
> Resource, listed in section 2 of Exhibit A, Net Requirements and
> Resources, for each month and Diurnal period beginning with the later
> of (1) the date the resource was dedicated to load, as shown in
> section 2 of Exhibit A, Net Requirements and Resources, or
> (2) October 1, 2011, through the earlier of (1) the date the resource
> will be permanently removed, as shown in section 2 of Exhibit A, Net
> Requirements and Resources, or (2) September 30, 2028. The firm energy
> amounts for each Specified Resource for each month and Diurnal period
> shall be based on the allowable shapes established in section 3.4
> below.
>
> 3.3.1.3 **Specified Resource Peak Amounts**
>
> Within 180 days after BPA provides notice that it has adopted a new
> standard for determining «Customer Name»'s firm resource peaking
> energy amounts, BPA in consultation with «Customer Name» shall
> calculate peaking amounts for each Specified Resource listed in
> section 2 of Exhibit A and BPA shall update the tables in Exhibit A
> with such peaking amounts. BPA's peaking standard shall be developed
> in a public process occurring after the Effective Date.
>
> 3.3.2 **Unspecified Resource Amounts**
>
> 3.3.2.1 **Application of Unspecified Resource Amounts**
>
> In addition to the resource amounts listed in section 2 of Exhibit A,
> Net Requirements and Resources, «Customer Name» shall serve its Total
> Retail Load with Unspecified Resource Amounts to meet its obligations
> «Customer Name» stated in Exhibit C, Purchase Obligations, to serve
> its Above-RHWM Load with Dedicated Resource amounts. [\[\[The
> preceding sentence does not seem to parse.\]]{.mark}\] «Customer Name»
> shall apply its Unspecified Resource Amounts, listed in section 3 of
> Exhibit A, Net Requirements and Resources, to «Customer Name»'s Total
> Retail Load in predefined hourly amounts consistent with section 3.8
> below.
>
> 3.3.2.2 **Unspecified Resource Energy Amounts**
>
> By March 31 of each Rate Case Year, BPA shall calculate and update the
> tables in section 3.1.2 of Exhibit A, Net Requirements and Resources,
> with «Customer Name»'s Unspecified Resource Amounts for the two years
> of the upcoming Rate Period. Such Unspecified Resource Amounts shall
> be calculated using the monthly and Diurnal shapes listed in
> section 3.1.1 of Exhibit A, Net Requirements and Resources. Upon
> termination or expiration of this Agreement, «Customer Name» may
> discontinue serving its Total Retail Load with any Unspecified
> Resource Amounts.

3.4 **Shaping of Dedicated Resource Amounts**

> «Customer Name»'s Dedicated Resources shall be shaped as follows:
>
> 3.4.1 **Initial Dedicated Resource Shapes**
>
> The Dedicated Resource amounts from each Dedicated Resource listed in
> Exhibit A shall have one of the following initial shapes consistent
> with each identified type of resource:
>
> \(1\) Generating Resources in the shape each resource generates
> output.
>
> \(2\) Contract Resources in equal megawatt amounts for each hour in a
> year.
>
> \(3\) Small Non-Dispatchable Resources in the shape the resource is
> expected to generate output.
>
> \(4\) Unspecified Resource Amounts in equal megawatt amounts for each
> hour in a year.
>
> 3.4.2 **Reshaping Dedicated Resource Amounts**
>
> By each Notice Deadline «Customer Name» may elect in writing, pursuant
> to section 3.4.3 below, to reshape its Dedicated Resource amounts
> listed in sections 2.1, 2.2, and 3.1 of Exhibit A, except for those
> Specified Resources «Customer Name» is supporting with DFS from BPA,
> for the corresponding Purchase Period. After BPA receives such written
> notice from «Customer Name», BPA shall, by the following March 31,
> revise Exhibit A to reflect such written elections. If «Customer Name»
> elects the "PNCA Update Shape" for a particular hydro resource, BPA
> shall update the shape of such resource annually, to be completed no
> later than September 15 preceding the start of the applicable Fiscal
> Year.
>
> 3.4.3 **Resource Shape Options**
>
> Consistent with section 3.4.2 above, «Customer Name» may elect to
> reshape one or more of its Dedicated Resources using the allowable
> monthly and Diurnal shapes described below. If «Customer Name» elects
> to reshape its Dedicated Resources, «Customer Name» shall elect both a
> monthly and a Diurnal shape for each Dedicated Resource that is
> reshaped.
>
> 3.4.3.1 **Generating Resources**
>
> For each Generating Resource listed in section 2.1 of Exhibit A, Net
> Requirements and Resources, «Customer Name» may elect to apply each
> resource in any of the following monthly shapes: (1) Total Retail Load
> Monthly Shape; (2) Resource Monthly Shape; (3) Flat Annual Shape; or
> (4) PNCA Update Shape, if the resource is designated as a Pacific
> Northwest Coordination Agreement (PNCA) resource in section 2.1 of
> Exhibit A, Net Requirements and Resources. «Customer Name» may elect
> to apply each Generating Resource in any of the following Diurnal
> shapes: (1) Resource Diurnal Shape; (2) Flat Within-Month Shape; or
> (3) HLH Diurnal Shape.
>
> 3.4.3.2 **Contract Resources**
>
> For each Contract Resource listed in section 2.2 of Exhibit A, Net
> Requirements and Resources, «Customer Name» may elect to apply each
> resource in any of the following monthly shapes: (1) Total Retail Load
> Monthly Shape; or (2) Flat Annual Shape. «Customer Name» may elect to
> apply each Contract Resource in any of the following Diurnal shapes:
> (1) Flat Within-Month Shape; or (2) HLH Diurnal Shape.
>
> 3.4.3.3 **Unspecified Resource Amounts**
>
> «Customer Name» may elect to apply its Unspecified Resource Amounts,
> listed in section 3.1 of Exhibit A, Net Requirements and Resources, in
> any of the following monthly shapes: (1) Total Retail Load Monthly
> Shape; or (2) Flat Annual Shape. «Customer Name» may elect to apply
> its Unspecified Resource Amounts in any of the following Diurnal
> shapes: (1) Flat Within-Month Shape; or (2) HLH Diurnal Shape.
>
> 3.4.4 **Super Peak Resource Credit**
>
> 3.4.4.1 **Super Peak Hours**
>
> By September 30 of each Forecast Year BPA shall notify «Customer Name»
> in writing of the Super Peak Hours for the upcoming Rate Period.
>
> 3.4.4.2 **Super Peak Amounts**
>
> By October 31 of each Rate Case Year «Customer Name» shall notify BPA
> in writing of the monthly megawatt amounts of additional capacity
> «Customer Name» elects to apply to its Total Retail Load for the
> upcoming Rate Period, for which «Customer Name» shall receive a Super
> Peak Resource Credit. «Customer Name» shall establish such amounts
> consistent with section 9 of Exhibit A, Net Requirements and
> Resources. After BPA receives such notification from «Customer Name»
> BPA shall revise section 9 of Exhibit A, by March 31 of the same Rate
> Period Year, to reflect monthly megawatt amounts «Customer Name»
> submitted to BPA.

*END **LOAD FOLLOWING** template.*

*Include in **BLOCK** template:*

*[Option 1]{.underline}: Include if customer does [not]{.underline}
choose **Shaping Capacity**:*

**3. BLOCK POWER PURCHASE OBLIGATION WITHOUT SHAPING CAPACITY*(06/30/08
Version)***

> 3.1 **Purchase Obligation**
>
> From October 1, 2011, and continuing through September 30, 2028, BPA
> shall sell and make available, and «Customer Name» shall purchase,
> Firm Requirements Power each hour in specific amounts to serve
> «Customer Name»'s forecasted Net Requirements, as listed in Exhibit A,
> Net Requirements and Resources. «Customer Name» shall serve any
> portion of its Total Retail Load that is not served with Firm
> Requirements Power with the Dedicated Resources listed in Exhibit A,
> Net Requirements and Resources. The annual, monthly, and Diurnal
> amounts of Firm Requirements Power priced at PF Tier 1 rates and PF
> Tier 2 rates are listed in Exhibit C, Purchase Obligations.

*End Option 1*

*[Option 2]{.underline}: Include if customer chooses **Shaping
Capacity**:*

*[Reviewers Note]{.underline}: Shaded text is identical to Block without
Shaping Capacity:*

**3. BLOCK POWER PURCHASE OBLIGATION WITH SHAPING CAPACITY *(06/30/08
Version)***

> 3.1 **Purchase Obligation**
>
> From October 1, 2011, and continuing through September 30, 2028, BPA
> shall sell and make available, and «Customer Name» shall purchase,
> Firm Requirements Power each hour in planned amounts, including
> Shaping Capacity in accordance with section 1.4 of Exhibit C, Purchase
> Obligations, to serve «Customer Name»'s forecasted Net Requirements,
> as listed in Exhibit A, Net Requirements and Resources. «Customer
> Name» agrees to serve any portion of its Total Retail Load that is not
> served with Firm Requirements Power with the Dedicated Resources
> listed in Exhibit A, Net Requirements and Resources. The annual,
> monthly, and Diurnal amounts of Firm Requirements Power priced at PF
> Tier 1 rates and PF Tier 2 rates are listed in Exhibit C, Purchase
> Obligations.

*End Option 2*

*END **BLOCK** template.*

*Include in **SLICE/BLOCK** template:*

**3. SLICE/BLOCK POWER PURCHASE OBLIGATION**

> 3.1 **Purchase Obligation**
>
> *[Reviewer's Note]{.underline}: This is a placeholder for now. Slice
> Team will drop in their version.*

*END **SLICE/BLOCK** template.*

*Include in **BLOCK** and **SLICE/BLOCK** templates:*

> 3.2 **Take or Pay**
>
> «Customer Name» shall pay for the amount of power it has committed to
> purchase under section 3.1 of this Agreement, at the rates BPA
> establishes as applicable to such power, whether or not «Customer
> Name» took actual delivery of such power.
>
> 3.3 **List and Application of** **Dedicated Resources**
>
> *[Reviewer's Note]{.underline}: The shaded language below is the same
> as the Load Following language.*
>
> «Customer Name» agrees to dedicate those resources for service to its
> Total Retail Load that it has listed as Dedicated Resources in
> Exhibit A as follows:
>
> \(1\) Specified Resources that are Generating Resources shall be
> listed in section 2.1 of Exhibit A,
>
> \(2\) Specified Resources that are Contract Resources shall be listed
> in section 2.2 of Exhibit A, and
>
> \(3\) Unspecified Resource Amounts shall be listed in section 3.1 of
> Exhibit A.
>
> «Customer Name» shall apply such resources to its Total Retail Load as
> state below for each specific resource and type:
>
> 3.3.1 **Specified Resources**
>
> «Customer Name» shall apply the output from all Specified Resources
> listed in section 2 of Exhibit A, Net Requirements and Resources, to
> serve its Total Retail Load. BPA shall use the amounts listed in
> Exhibit A, Net Requirements and Resources, to determine «Customer
> Name»'s Net Requirement under this Agreement; the amounts listed are
> not intended to interfere with «Customer Name»'s decisions on how to
> operate its Specified Resources.
>
> 3.3.2 **Unspecified Resource Amounts**
>
> In addition to the resource amounts listed in section 2 of Exhibit A,
> Net Requirements, «Customer Name» shall serve its Total Retail Load
> with Unspecified Resource Amounts to meet any power supply obligations
> «Customer Name» made in Exhibit C, Purchase Obligations, to serve its
> Above-RHWM Load with Dedicated Resource amounts. [\[\[The preceding
> sentence does not seem to parse.\]\]]{.mark} By September 15, 2011,
> and by each September 15 thereafter, BPA shall calculate, and fill in
> the table in section 3.1 of Exhibit A with, «Customer Name»'s
> Unspecified Resource Amounts for the upcoming Fiscal Year. Upon
> termination or expiration of this Agreement, «Customer Name» may
> discontinue serving its Total Retail Load with allUnspecified Resource
> Amounts.

3.4 **Dedicated Resource Amounts for Specified Resources**

> 3.4.1 **Specified Resource Energy Amounts**
>
> «Customer Name» shall state firm energy amounts for each Specified
> Resource, listed in section 2 of Exhibit A, Net Requirements and
> Resources, for each month and Diurnal period beginning with the later
> of (1) the date the resource was dedicated to load, as shown in
> section 2 of Exhibit A, Net Requirements and Resources, or
> (2) October 1, 2011, through the earlier of (1) the date the resource
> will be permanently removed, as shown in section 2 of Exhibit A, Net
> Requirements and Resources, or (2) September 30, 2028.
>
> 3.4.1 **Specified Resource Peak Amounts**
>
> Within 180 days after BPA provides notice that it has adopted a new
> standard for determining «Customer Name»'s firm resource peaking
> energy amounts, BPA in consultation with «Customer Name» shall
> calculate peaking amounts for each Specified Resource listed in
> section 2 of Exhibit A and BPA shall update the tables in Exhibit A
> with such peaking amounts. BPA's peaking standard shall be developed
> in a public process occurring after the Effective Date.

*END **BLOCK** and **SLICE/BLOCK** templates.*

3.5 **Changes to Dedicated Resources**

> 3.5.1 **Resource Additions for a BPA Insufficiency Notice**
>
> If BPA provides «Customer Name» a notice of insufficiency in
> accordance with section 24.2, Insufficiency and Allocations, of the
> body of this Agreement, «Customer Name» shall add Dedicated Resources
> to Exhibit A, Net Requirements and Resources, to replace amounts of
> Firm Requirements Power BPA will not be providing due to
> insufficiency.
>
> 3.5.2 **Decrements for [Northwest Power Act Section]{.mark}** **9(c)
> [and Regional Preference Act Section 3(d)]{.mark}** **Export**
>
> If BPA determines (in accordance with section 24.7, Use of Regional
> Resources, of the body of this Agreement) that an export of a
> Specified Resource listed in section 2 of Exhibit A, Net Requirements
> and Resources, requires a reduction in the amount of Firm Requirements
> Power BPA sells «Customer Name», then BPA shall add Unspecified
> Resource Amounts to section 3.2 of Exhibit A, Net Requirements and
> Resources. BPA shall notify «Customer Name» of the amount and duration
> of the reduction in «Customer Name»'s Firm Requirements Power
> purchases from BPA.

*Include in **LOAD FOLLOWING** and **BLOCK** templates:*

> 3.5.3 **Temporary Resource Removal**
>
> BPA shall remove «Customer Name»'s Dedicated Resource amounts in
> Exhibit A, Net Requirements and Resources, pursuant to section 10,
> Order of Tier 2 Remarketing and Resource Removal, of the body of this
> Agreement. When only a portion of the output of a resource is being
> removed, BPA shall proportionally remove «Customer Name»'s Dedicated
> Resource amounts within a Fiscal Year to maintain the same shape the
> non-federal resource amounts were dedicated in for such Fiscal Year.

*END **LOAD FOLLOWING** and **BLOCK** templates.*

*Include in **SLICE/BLOCK** template:*

> 3.5.3 **Temporary Resource Removal**
>
> BPA shall remove «Customer Name»'s Dedicated Resource amounts in
> Exhibit A, Net Requirements and Resources, pursuant to section 10,
> Order of Tier 2 Remarketing and Resource Removal, of the body of this
> Agreement. BPA shall remove «Customer Name»'s Dedicated Resource
> amounts within a Fiscal Year consistent with «Customer Name»'s written
> notice provided to BPA containing such reduction amounts, submitted
> pursuant to section 10.7 of the body of this Agreement.

*END **SLICE/BLOCK** template.*

> 3.5.4 **Permanent Discontinuance of Resources**
>
> The Specified Resources listed in section 2 of Exhibit A, Net
> Requirements and Resources, may be removed permanently by «Customer
> Name» consistent with BPA's Policy on Determining Net Requirements of
> Pacific Northwest Utility Customers Under Sections 5(b)(1) and 9(c) of
> the Northwest Power Act issued May 23, 2000, as clarified March 21,
> 2003 (5(b)/9(c) Policy), on statutory discontinuance for permanent
> removal. If BPA makes a determination that «Customer Name»'s resource
> has met BPA's standards for a permanent removal, BPA shall revise
> Exhibit A accordingly. «Customer Name»'s additional power purchases
> under this Agreement, as a result of such a resource removal, may be
> subject to additional rates or charges as established in the GRSPs.
>
> 3.5.5 **Resource Additions for Annexed Loads**
>
> To serve amounts of Annexed Loads that are added after the Effective
> Date, «Customer Name» may add Dedicated Resources to Exhibit A, Net
> Requirements and Resources, pursuant to «Customer Name»'s elections to
> purchase Firm Requirements Power from BPA, as stated in Exhibit C,
> Purchase Obligations. «Customer Name»'s additional power purchases
> under this Agreement, as a result of such Annexed Loads, may be
> subject to additional rates or charges as established in the GRSPs.
>
> 3.5.6 **Resource Additions/Removals for NLSLs**
>
> To serve NLSLs (established in Exhibit D, Additional Products and
> Special Provisions) that are added after the Effective Date, «Customer
> Name» may add Dedicated Resource amounts, in monthly and Diurnal
> amounts, to section 4 of Exhibit A, Net Requirements and Resources.
> «Customer Name» may discontinue serving its NLSL with the Dedicated
> Resource amounts listed in section 4 of Exhibit A if BPA determines
> that «Customer Name»'s NLSL is no longer an NLSL in «Customer Name»'s
> service territory.
>
> *[Reviewer's Note]{.underline}: BPA (acting on behalf of the United
> States Entity) needs the following information to administer the
> Columbia River Treaty with Canada. BPA also needs the following
> information for 9(c) determinations.*
>
> 3.6 **Resources Not Dedicated to Total Retail Load**
>
> «Customer Name» shall list in section 6 of Exhibit A, Net Requirements
> and Resources, any non-federal resources «Customer Name» owns that are
> (1) not Specified Resources listed in section 2 of Exhibit A, and
> (2) greater than 200 kilowatts of nameplate capability. At BPA's
> request «Customer Name» shall provide BPA with additional data if
> needed to verify the information listed in section 6 of Exhibit A.
>
> 3.7 **Consumer-Owned Resources**
>
> Except for any Consumer-Owned Resources serving an NLSL which
> «Customer Name» shall apply to load consistent with section 24.3.7,
> Renewable Resource/Cogeneration Exception, «Customer Name» shall apply
> the output of its Consumer-Owned Resources as follows:
>
> [\[\[The draft Template should not include any commitment by BPA that
> would preclude BPA in the future from including in]{.mark} [the
> billing demand for BPA Network Service any load served by
> Consumer-Owned Resources.\]\]]{.mark}
>
> *[Reviewer's Note]{.underline}: Prior to contract signing all
> customers will have to designate, in sections 7.1 or 7.2 of Exhibit A,
> whether their existing Consumer-Owned Resources will or will not be
> serving Onsite Consumer Load for the term of this Agreement.*
>
> 3.7.1 **Existing Consumer-Owned Resources**
>
> «Customer Name» has designated, in sections 7.1 and 7.2 of Exhibit A,
> whether each of its existing Consumer-Owned Resources will or will not
> serve Onsite Consumer Load. Such designation(s) shall apply for the
> term of this Agreement.
>
> 3.7.2 **New Consumer-Owned Resources**
>
> «Customer Name» shall designate whether each of its new Consumer-Owned
> Resources will or will not serve Onsite Consumer Load. «Customer Name»
> shall make such designation(s) to BPA, in writing, within 120 days of
> the first production of energy by such resource. Such designation(s)
> shall apply for the term of this Agreement.
>
> Consistent with «Customer Name»'s designation(s), BPA shall list
> Consumer-Owned Resources serving Onsite Consumer Load in section 7.1
> of Exhibit A and Consumer-Owned Resources not serving Onsite Consumer
> Load in section 7.2 of Exhibit A.
>
> 3.7.3 **Application of Consumer-Owned Resources Serving Onsite
> Consumer Load**
>
> Power generated from Consumer-Owned Resources listed in section 7.1 of
> Exhibit A shall serve «Customer Name»'s Onsite Consumer Load. If on
> any hour, power generated from a Consumer-Owned Resource exceeds
> Onsite Consumer Load, the amount of such excess power on that hour
> shall be treated as inadvertent flow for which «Customer Name» shall
> receive no compensation from BPA.
>
> 3.7.4 **Application of Consumer-Owned Resources Serving Load Other
> than Onsite Consumer Load**
>
> Power generated from Consumer-Owned Resources listed in section 7.2 of
> Exhibit A shall be scheduled for delivery and either (1) sold to
> another utility in the Region for use in its Total Retail Load,
> (2) purchased by «Customer Name» for use in its Total Retail Load
> (consistent with section 3.3 of this Agreement), or (3) marketed as an
> export.
>
> 3.7.5 **Changes to Consumer-Owned Resources**
>
> Prior to each Fiscal Year «Customer Name» shall notify BPA in writing
> of any changes in ownership, expected resource output, or other
> characteristic of Consumer-Owned Resources identified in Section 7 of
> Exhibit A.

*Include in **LOAD FOLLOWING** template only:*

> 3.7.6 **Data Requirements for Consumer-Owned Resources**
>
> Except for any Consumer-Owned Resources in which the owner of the
> resource only receives power from «Customer Name» to serve the
> resource's station service load, the following data requirements are
> applicable:
>
> \(1\) «Customer Name» shall meter all Consumer-Owned Resources listed
> in section 7 of Exhibit A and shall provide such meter data to BPA
> pursuant to section 17.3, Meter Data.
>
> \(2\) «Customer Name» shall provide BPA with hourly schedule data for
> all Consumer-Owned Resources listed in section 7.2 of Exhibit A for
> each month within five business days after the end of such month.
> «Customer Name» shall e‑mail its hourly schedule data to BPA at
> kslf@bpa.gov.

*END **LOAD FOLLOWING** template.*

*Include in **LOAD FOLLOWING** template:*

> 3.8 **Hourly Dedicated Resource Schedule**
>
> By June 30 of each Rate Case Year, «Customer Name» shall provide BPA
> an aggregated hourly schedule, in whole megawatt amounts consistent
> with section 3.8.3 below and in the format described in section 3.8.2
> below, for its Dedicated Resources with amounts in each hour,
> calculated pursuant to section 3.8.1 below, for the two years of the
> upcoming Rate Period ("Submitted Schedule"). «Customer Name» shall
> schedule such hourly amounts to its Total Retail Load consistent with
> section 13, Scheduling.
>
> 3.8.1 **Schedule Amounts**
>
> The amounts in the Submitted Schedule shall equal the sum of all
> Dedicated Resource amounts, listed in sections 2 and 3 of Exhibit A,
> except for those Small Non-Dispatchable Resources, listed in
> section 2.3 of Exhibit A, and those Specified Resources supported with
> Diurnal Flattening Services, listed in section 2 of Exhibit D.
>
> The amounts in the Submitted Schedule shall be in equal megawatt
> amounts during all LLH of a month and during all HLH of a month,
> unless «Customer Name» reshapes its HLH amounts pursuant to
> section 3.4.4 above. If «Customer Name» reshapes its HLH amounts
> pursuant to section 3.4.4 above, then the HLH amounts in «Customer
> Name»'s Submitted Schedule shall be in (1) equal megawatt amounts
> during all HLH of a month that are not Super Peak hours, and (2) equal
> megawatt amounts during all HLH of a month that are Super Peak hours.
> The amounts in the Super Peak Hours shall reflect the additional
> capacity amounts listed in section 9 of Exhibit A, Net Requirements
> and Resources.
>
> If the amounts in sections 2 of Exhibit A change per to the PNCA
> Update Shape, consistent with section 3.4.2 above, «Customer Name»
> shall send BPA an updated Submitted Schedule using the updated
> Dedicated Resource amounts by September 25 of each Fiscal Year for the
> upcoming Fiscal Year.
>
> 3.8.2 **Schedule Format**
>
> «Customer Name» shall provide the hourly resource schedule to BPA
> electronically in a comma-separated-value (csv) format with the
> time/date stamp in the first column and load amounts, with units of
> measurement specified, in the following column.
>
> 3.8.3 **Whole Megawatt Amounts**
>
> If «Customer Name»'s Submitted Schedule would otherwise have amounts
> in fractional megawatts-per-hour, «Customer Name» shall vary its
> hourly amounts by one megawatt in some hours so that over the course
> of the applicable month the amounts as scheduled in whole megawatts
> sum to the appropriate total. If «Customer Name»'s Dedicated Resource
> amounts are less than one megawatt-per-hour in any Diurnal period of a
> month, then «Customer Name» shall schedule one megawatt starting with
> the first hour of the Diurnal period of that month, and scheduling in
> each subsequent hour of the Diurnal period until the appropriate
> amount has been scheduled for that Diurnal period of such month.

*END **LOAD FOLLOWING** template.*

*Include in **LOAD FOLLOWING** and **BLOCK** templates:*

> *[Reviewer's Note]{.underline}: These sections are included in Slice
> customers' contracts; Load Following and Block customers will have
> blank sections to maintain consistent numbering among the templates.*

*[Include in]{.mark}* ***[SLICE/BLOCK,]{.mark}*** ***[LOAD
FOLLOWING]{.mark}*** *[and]{.mark}* ***[BLOCK]{.mark}***
*[templates]{.mark}* *[(but do not include in]{.mark}* ***[NR
BLOCK]{.mark}*** *[template)]{.mark}*

> []{.mark}
>
> [If and to the extent that]{.mark}
>
> []{.mark}
>
> [(1) «Customer Name»'s Total Retail Load exceeds]{.mark}
>
> []{.mark}
>
> [(2) the sum of]{.mark} [«Customer Name»'s Firm Requirements Power
> plus its Specified Resources, then]{.mark}
>
> []{.mark}
>
> [to such extent any]{.mark} [«Customer Name»]{.mark} [resources that
> are "owned or purchased" pursuant to section 7(b)(2)(D) of the
> Regional Power Act but that are not Specified Resources shall be
> considered committed to the]{.mark} [«Customer Name»'s load pursuant
> to section 5(b) of the Northwest Power Act for purposes of the
> Northwest Power Act section 7(b(2) rate test.]{.mark}

**4. THIS SECTION INTENTIONALLY LEFT BLANK *(05/29/08 Version)***

**5. THIS SECTION INTENTIONALLY LEFT BLANK *(05/29/08 Version)***

*END **LOAD FOLLOWING** and **BLOCK** templates.*

*Include in **SLICE/BLOCK** template:*

**4. NEW SLICE SECTION *(05/23/08 Version)***

> *[Reviewer's Note]{.underline}: This is a placeholder for now. Slice
> Team will drop in their version.*

**5. NEW SLICE SECTION *(05/23/08 Version)***

> *[Reviewer's Note]{.underline}: This is a placeholder for now. Slice
> Team will drop in their version.*

*END **SLICE/BLOCK** template.*

**6. TIERED RATE METHODOLOGY *(06/13/08 Version)***

> *[Reviewer's Note]{.underline}: The following language in this section
> 6 is a placeholder for now and is in the process of being updated.*
>
> 6.1 BPA has proposed a Tiered Rate Methodology (TRM) to FERC, for a
> period up to 20 years (through September 30, 2028), which will
> establish a rate design for the PF Tier 1 power rate and the PF Tier 2
> power rate. The then-effective TRM shall govern all rates for power
> sold under this Agreement.
>
> 6.2 In the event that FERC approves the TRM for a period less than
> through September 30, 2028, BPA shall, before the approved period of
> the TRM expires: (1) propose continuation of the TRM in a hearing
> conducted pursuant to section 7(i) of the Northwest Power Act or its
> successor: and then (2) resubmit the TRM to FERC for approval through
> September 30, 2028.
>
> 6.3 BPA shall not propose any modification to the TRM, except as
> provided for and pursuant to the procedures set forth in sections 12
> and 13 of the TRM that is current as of the Effective Date. [\[\[Any
> restrictions included in any BPA power sales contract on BPA's
> proposing any modification to the TRM should also be included in BPA's
> residential exchange purchase and sale agreements.\]\]]{.mark}
>
> 6.4 The Parties intend that the TRM will be binding on them in
> accordance with its terms, but references to rates or the TRM in this
> Agreement do not make the rates or TRM a matter of contract. This
> Agreement shall not be construed as causing any rate issue or TRM
> matter to become a contract issue or matter. Disputes over the meaning
> and implementation of the TRM shall be resolved exclusively pursuant
> to the procedures set forth in the TRM.
>
> 6.5 BPA shall not publish a Federal Register Notice regarding BPA
> rates or the TRM that prohibits, limits, or restricts «Customer
> Name»'s right to submit testimony or brief issues on rate matters
> regarding the implementation of the TRM or establishment of BPA rates
> pursuant to it, provided however for purposes of this paragraph a
> "rate matter" shall not be deemed to include budgetary and revenue
> requirement issues. [\[\[Any such restrictions included in any BPA
> power sales contract on what BPA may publish in a Federal Register
> Notice should also be included in BPA's residential exchange purchase
> and sale agreements.\]\]]{.mark}
>
> 6.6 The Tiered Rate Methodology (TRM) established by BPA as of the
> Effective Date includes, among other things, the following:
>
> 6.6.1 Definitions (from Definitions section of the TRM):
>
> **Contract High Water Mark (CHWM).** The amount used to define each
> customer's access to Tier 1-priced power, expressed in average
> megawatts. CHWM is equal to the customer's Eligible Load (as defined
> in the TRM), proportionately scaled to the firm critical output of
> Tier 1 System Resources (as defined in the TRM), and adjusted for
> credited conservation. The CHWM is specified in each eligible
> customer's CHWM Contract. See section 4.2 (of the TRM).
>
> **Rate Period High Water Mark (RHWM).** The amount used to define each
> customer's eligibility to purchase power at a Tier 1 price for the
> relevant Rate Period (as defined in the TRM), subject to the
> customer's Net Requirement, expressed in average megawatts. RHWM is
> equal to the customer's CHWM as adjusted for changes in Tier 1 System
> Resources (as defined in the TRM). The RHWM is determined for each
> eligible customer in the RHWM Process (as defined in the TRM)
> preceding each rate case. See section 4.3 (of the TRM).
>
> **Contract Demand Quantity (CDQ).** The historical quantity of demand
> that is subtracted from the Customer's System Peak (CSP) (as defined
> in the TRM) as part of the process of determining the customer's
> Demand Charge Billing Determinant (as defined in the TRM). See
> section 5.3.2 (of the TRM).
>
> 6.6.2 Rate Period High Water Mark Calculation (from section 4.3.1 of
> the TRM):
>
> Expressed as a formula, the RHWM will be calculated by BPA for each
> customer as follows:
>
> ![](media/image1.wmf){width="2.0in" height="0.4861111111111111in"}

where:

> *RHWM* = Rate Period High Water Mark, expressed in average megawatts
>
> *CHWM* = Contract High Water Mark
>
> *ΣCHWM* = sum of all customers' Contract High Water Marks
>
> *T1SR* = forecast output of Tier 1 System Resources (as defined in the
> TRM), averaged for the Rate Period
>
> 6.6.3 The above-recited, and all other, TRM language may only be
> changed in accordance with the requirements of the TRM for TRM
> changes. Reference in this contract to the TRM or recitation in this
> contract of what the TRM provides with regard to the RHWM or other
> matters does not make implementation of the TRM, or issues or disputes
> regarding BPA's implementation of the TRM, matters of contract;
> rather, they retain their character as administrative matters.
> However, repudiation by BPA of its obligation here and under the TRM
> to change the TRM only in accordance with the TRM section 12 and 13
> procedures for change would be a matter of contract.

**7. HIGH WATER MARKS *(06/13/08 Version)***

7.1 **Contract High Water Mark (CHWM)**

> BPA shall establish «Customer Name»'s CHWM in the process defined in
> section 4.2 of the TRM that was current as of the Effective Date.
> «Customer Name»'s CHWM and the circumstances under which it can change
> are stated in Exhibit B, High Water Marks and Contract Demand
> Quantities. BPA shall use «Customer Name»'s CHWM to determine
> «Customer Name»'s RHWM as prescribed in section 4.3 of the TRM.
>
> *[Reviewer's Note]{.underline}: See "Timeline for HWMs & Above-RHWM
> Elections"*
>
> 7.2 **Rate Period High Water Mark (RHWM)**
>
> «Customer Name»'s CHWM will also be «Customer Name»'s RHWM for FY 2012
> and FY 2013. BPA shall establish «Customer Name»'s RHWM for the next
> Rate Period by September 30, 2012, and for subsequent Rate Periods by
> September 30 of each Forecast Year thereafter. BPA shall establish
> «Customer Name»'s RHWM in a process defined in section 4.3 of the TRM
> that was current as of the Effective Date. BPA shall designate
> «Customer Name»'s RHWM in the initial proposal for each general rate
> case.

**8. APPLICABLE RATES *(06/13/08 Version)***

> Purchases under this Agreement are subject to the following rate
> schedules, or their successors: Priority Firm Power (PF), New Resource
> Firm Power (NR), and Firm Power Products and Services (FPS). Billing
> determinants for any purchases are included in each rate schedule.
> Power purchases under this Agreement are subject to BPA's rates, its
> GRSPs (or their successors), and the TRM. [\[\[Comment:]{.mark} [Any
> section 7(b)(2) trigger amount must be allocated to all rates (other
> than the PF Preference rate for]{.mark} [regional firm load net
> requirements, exclusive of any new large single load), including (but
> not necessarily limited to) the PF Exchange rate, the IP rate, the NR
> rate, the FPS rate, and the portion of the Slice rate attributable to
> secondary energy. Any BPA contract for the sale of power under such
> rates should expressly contemplate, and must not purport to
> prohibit,]{.mark} [the supplemental rate charge required by section
> 7(b)(3) of the Northwest Power Act for any section 7(b)(2) trigger
> amount.\]\]]{.mark}
>
> 8.1 **Priority Firm Power Rates**
>
> BPA shall establish its PF power rates that apply to purchases under
> this Agreement pursuant to section 7 of the Northwest Power Act, and
> in accordance with the TRM. BPA's PF power rates shall include a rate
> schedule for purchase amounts at PF Tier 1 rates and purchase amounts
> at PF Tier 2 rates.

*Include in **LOAD FOLLOWING** template:*

> 8.1.1 **PF Tier 1 and PF Tier 2 Rates**
>
> «Customer Name»'s purchase of Firm Requirements Power shall be priced
> as follows:
>
> \(1\) PF Tier 1 rates shall apply to Firm Requirements Power that
> «Customer Name» purchases under this Agreement, less: (a) amounts of
> Firm Requirements Power priced at PF Tier 2 rates elected by «Customer
> Name» in section 2 of Exhibit C, Purchase Obligations, and (b) any
> amounts purchased for NLSLs.
>
> \(2\) PF Tier 2 rates shall apply to planned annual amounts of Firm
> Requirements Power that «Customer Name» purchases to serve its
> Above-RHWM Load minus «Customer Name»'s New Resources. The details of
> this calculation, including the use of a forecasted RHWM for FY 2012
> and FY 2013, are established in the TRM.

*END **LOAD FOLLOWING** template.*

*Include in **BLOCK** template:*

> 8.1.1 **PF Tier 1 and PF Tier 2 Rates**
>
> «Customer Name»'s purchase of Firm Requirements Power shall be priced
> as follows:
>
> \(1\) Subject to «Customer Name»'s Net Requirement, all amounts of
> «Customer Name»'s planned annual purchase of Firm Requirements Power
> that are equal to or less than «Customer Name»'s RHWM shall be priced
> at PF Tier 1 rates.
>
> \(2\) Subject to «Customer Name»'s Net Requirement, all amounts of
> «Customer Name»'s planned annual purchase of Firm Requirements Power
> that is above «Customer Name»'s RHWM shall be priced at PF Tier 2
> rates elected by «Customer Name» in section 2 of Exhibit C, Purchase
> Obligations.

*END **BLOCK** template.*

> []{.mark}

*Include in **SLICE/BLOCK** template:*

*[Reviewer's Note]{.underline}: The Slice Template probably needs
additional language here that includes more specifics about Tier 1 and
Tier 2 applicability (similar to LF and Block) and that is synched up
with the Slice Exhibit C.*

> 8.1.1 **PF Tier 1 and PF Tier 2 Rates**

*END **SLICE/BLOCK** template.*

> 8.1.2 **Contract Demand Quantities (CDQs)**
>
> BPA shall establish «Customer Name»'s CDQs pursuant to the TRM.
> «Customer Name»'s CDQs are listed in Exhibit B, High Water Marks and
> Contract Demand Quantities.
>
> 8.2 **New Resource Firm Power Rate**
>
> Any amounts of power provided to «Customer Name» from BPA for service
> to an NLSL, listed in Exhibit D, Additional Products and Special
> Provisions, shall be purchased at the NR Rate.
>
> 8.3 **Firm Power Products and Services Rate**
>
> Amounts of power and other services sold to «Customer Name» under the
> FPS rate, if any, are listed in Exhibit D, Additional Products and
> Special Provisions.

*Include in **LOAD FOLLOWING** template:*

> 8.4 **Additional Charges**
>
> The Resource Shaping Charge (RSC) shall apply to «Customer Name»'s New
> Resources that are dedicated to load in unequal megawatt amounts for
> each hour of the year. «Customer Name» may incur additional charges or
> penalty charges in the GRSPs, including the Unauthorized Increase
> (UAI) Charge or its successors.
>
> 8.5 **Resource Support Services (RSS)**
>
> For «Customer Name»'s Specified Resources, «Customer Name» may elect
> to purchase RSS products under this Agreement, as listed in Exhibit D,
> Additional Products and Special Provisions.

*END **LOAD FOLLOWING** template.*

*Include in **BLOCK** and **SLICE/BLOCK** templates:*

> 8.4 **Additional Charges**
>
> «Customer Name» may incur additional charges or penalty charges as
> established in the GRSPs, including the Unauthorized Increase (UAI)
> and the Resource Shaping Charge (RSC), or their successors.

*END **BLOCK** and **SLICE/BLOCK** templates.*

**9. ELECTIONS TO PURCHASE POWER PRICED AT PF TIER 2 RATES *(06/13/08
Version)***

> *[Reviewer's Note]{.underline}: See "Timeline for HWMs & Above-RHWM
> Elections"*
>
> 9.1 **Determination and Notice to Serve Above-RHWM Load**
>
> «Customer Name» shall determine and provide notice, as described
> below, to BPA whether «Customer Name» shall serve its Above-RHWM Load
> that is greater than 8,760 megawatt-hours and is not an NLSL, with
> either: (1) Firm Requirements Power purchased from BPA at a PF Tier 2
> rate or rates, (2) Dedicated Resources, or (3) a specific combination
> of both (1) and (2). «Customer Name» shall make such determination and
> provide such notice as follows:
>
> 9.1.1 **Notice Deadlines and Purchase Periods**
>
> Notice Deadlines and corresponding Purchase Periods are as follows:

  ------------------------------------------------------------------------
  **Notice Deadline**                       **Purchase Period**
  -------------------------------- -------- ------------------------------
  November 1, 2009                 for      FY 2012 -- FY 2014

  September 30, 2011               for      FY 2015 -- FY 2019

  September 30, 2016               for      FY 2020 -- FY 2024

  September 30, 2021               for      FY 2025 -- FY 2028
  ------------------------------------------------------------------------

> 9.1.2 **Elections to Purchase at PF Tier 2 Rates**
>
> By each Notice Deadline, «Customer Name» shall elect in writing to
> purchase, or not to purchase, Firm Requirements Power at PF Tier 2
> rates for at least the upcoming Purchase Period. If «Customer Name»
> elects to purchase Firm Requirements Power at PF Tier 2 rates,
> «Customer Name» shall make such election pursuant to sections 2.2
> through 2.4 of Exhibit C, Purchase Obligations. BPA shall update
> Exhibit C, Purchase Obligations, to state «Customer Name»'s PF Tier 2
> rate purchase elections.
>
> 9.1.3 **Elections Not to Purchase at PF Tier 2 Rates**
>
> If «Customer Name» elects not to purchase Firm Requirements Power at
> PF Tier 2 rates for a Purchase Period, BPA shall update section 2.1 of
> Exhibit C, Purchase Obligations, to indicate such election. Such
> election shall not eliminate any prior obligation to purchase Firm
> Requirements Power at PF Tier 2 rates for future rate periods.

*Include in **LOAD FOLLOWING** template:*

> 9.1.4 **Failure to Make an Election**
>
> If «Customer Name» makes no election by a Notice Deadline in section
> 9.1.1 above, for the corresponding Purchase Period «Customer Name»
> shall be deemed to have elected alternative (A) in section 2.4.1 of
> Exhibit C, Purchase Obligations, with zero amounts listed in the table
> in section 2.4.1.1(2) of Exhibit C, Purchase Obligations.

*END **LOAD FOLLOWING** template.*

*Include in **BLOCK** and **SLICE/BLOCK** templates:*

> 9.1.4 **Failure to Make an Election**
>
> If «Customer Name» makes no election by a Notice Deadline in section
> 9.1.1 above, for the corresponding Purchase Period «Customer Name»
> shall be deemed to have elected not to purchase Firm Requirements
> Power at PF Tier 2 rates, except for any previously obligated PF
> Tier 2 purchase amounts.

*END **BLOCK** and **SLICE/BLOCK** templates.*

*Include in **LOAD FOLLOWING** template:*

> 9.2 **Tier 2 Rate Alternatives**
>
> Subject to the requirements stated in Exhibit C, Purchase Obligations,
> «Customer Name» shall have the right to purchase Firm Requirements
> Power priced at the following PF Tier 2 Rates:
>
> 9.2.1 **PF Tier 2 Load-Growth Rate**
>
> «Customer Name» has two opportunities to elect to purchase Firm
> Requirements Power from BPA at the PF Tier 2 Load-Growth Rate to serve
> «Customer Name»'s Above-RHWM Load for the remaining term of this
> Agreement. «Customer Name» shall make such election in accordance with
> section 2.2 of Exhibit C, Purchase Obligations.
>
> 9.2.2 **PF Tier 2 Vintage Rate(s)**
>
> Subject to eligibility requirements specified in Exhibit C, Purchase
> Obligations, «Customer Name» may elect to purchase Firm Requirements
> Power from BPA at a PF Tier 2 Vintage Rate(s) to serve «Customer
> Name»'s Above-RHWM Load for a specified term. A PF Tier 2 Vintage
> Rate(s) is based on the costs of specific resources and is set in each
> general rate case. «Customer Name» shall make such election(s) in
> accordance with section 2.3 of Exhibit C, Purchase Obligations.
>
> 9.2.3 **PF Tier 2 Short-Term Rate**
>
> «Customer Name» may elect by a Notice Deadline to purchase Firm
> Requirements Power from BPA at the PF Tier 2 Short-Term Rate to serve
> «Customer Name»'s Above-RHWM Load for the corresponding Purchase
> Period. «Customer Name» shall make such election in accordance with
> section 2.4 of Exhibit C, Purchase Obligations.

*END **LOAD FOLLOWING** template.*

*Include in **BLOCK** and **SLICE/BLOCK** templates:*

> *[Reviewers Note]{.underline}: Shaded text is identical to Load
> Following text (absent the Load-Growth Rate Alternative):*

9.2 **Tier 2 Rate Alternatives**

> Subject to the requirements stated in Exhibit C, Purchase Obligations,
> «Customer Name» shall have the right to purchase Firm Requirements
> Power priced at the following PF Tier 2 Rates:
>
> 9.2.1 **PF Tier 2 Vintage Rate(s)**
>
> Subject to eligibility requirements specified in Exhibit C, Purchase
> Obligations, «Customer Name» may elect to purchase Firm Requirements
> Power from BPA at a PF Tier 2 Vintage Rate(s) to serve «Customer
> Name»'s Above-RHWM Load for a specified term. A PF Tier 2 Vintage
> Rate(s) is based on the costs of specific resources and is set in each
> general rate case. «Customer Name» shall make such election(s) in
> accordance with section 2.3 of Exhibit C, Purchase Obligations.
>
> 9.2.2 **PF Tier 2 Short-Term Rate**
>
> «Customer Name» may elect by a Notice Deadline to purchase Firm
> Requirements Power from BPA at the PF Tier 2 Short-Term Rate to serve
> «Customer Name»'s Above-RHWM Load for the corresponding Purchase
> Period. «Customer Name» shall make such election in accordance with
> section 2.4 of Exhibit C, Purchase Obligations.

*END **BLOCK** and **SLICE/BLOCK** templates.*

> 9.3 **Obligation to Apply Non-Federal Resources**
>
> «Customer Name»'s obligation to apply its Dedicated Resources to serve
> its Above-RHWM Load is stated in section 3 of the body of this
> Agreement and Exhibit C, Purchase Obligations.

*Include in **LOAD FOLLOWING** template:*

**10. ORDER OF TIER 2 REMARKETING AND RESOURCE REMOVAL*(05/27/08
Version)***

> 10.1 **Order of Removal for Each Rate Period**
>
> By October 31, 2012, and by October 31 of each Rate Case Year
> thereafter, BPA shall establish «Customer Name»'s Above-RHWM Load for
> each year of the upcoming Rate Period. If the sum of «Customer Name»'s
> PF Tier 2 rate purchase amounts, stated in Exhibit C, Purchase
> Obligations, plus the amounts of «Customer Name»'s New Resources
> exceeds «Customer Name»'s Above-RHWM Load for one or more years of a
> Rate Period, then BPA shall remarket the PF Tier 2 rate purchase
> amounts and BPA shall remove such New Resource amounts, for each year
> of the Rate Period, in the amount established in section 10.2 below.
> BPA shall remarket such PF Tier 2 rate purchase amounts and remove
> such New Resource amounts in the following order:
>
> \(1\) Amounts of Firm Requirements Power priced at PF Tier 2 rates
> listed in Exhibit C, Purchase Obligations, then
>
> \(2\) «Customer Name»'s Unspecified Resource Amounts listed in
> section 3.1 of Exhibit A, Net Requirements and Resources, then
>
> \(3\) «Customer Name»'s Specified Resources that are New Resources
> listed in section 2 of Exhibit A, Net Requirements and Resources. If
> «Customer Name» has multiple Specified Resources that are New
> Resources, BPA shall remove such resources in a last added, first
> removed order based on the order in which «Customer Name» made its
> resource additions.
>
> 10.2 **Extent of Removal**
>
> BPA shall remarket «Customer Name»'s purchase amounts at PF Tier 2
> rates and BPA shall remove the amounts of «Customer Name»'s New
> Resources until:
>
> \(1\) the remarketed PF Tier 2 rate purchase amounts plus the removed
> New Resource amounts equals the amount that «Customer Name»'s PF
> Tier 2 rate purchase amounts plus its New Resources exceeds its
> Above-RHWM Load, or
>
> \(2\) all of «Customer Name»'s PF Tier 2 rate purchase amounts are
> remarketed and all of its New Resources are removed.
>
> 10.3 **Remarketing of Federal Power Priced at PF Tier 2 Rates**
>
> Consistent with rates established under the TRM, «Customer Name» shall
> be subject to applicable charges or credits associated with BPA's
> remarketing of purchase amounts of Firm Requirements Power at PF
> Tier 2 rates. «Customer Name» shall be responsible for remarketing of
> any amounts of its Dedicated Resources, Specified or Unspecified, that
> are removed under this section 10, Order of Tier 2 Remarketing and
> Resource Removal.

*END **LOAD FOLLOWING** template.*

*Include in **BLOCK** and **SLICE/BLOCK** templates:*

**10. ORDER OF TIER 2 REMARKETING AND RESOURCE REMOVAL *(05/27/08
Version)***

> *[Reviewer's Note]{.underline}: See "Timeline for HWMs & Above-RHWM
> Elections"*
>
> 10.1 **Order of Removal -- First Fiscal Year of Rate Period**
>
> By September 15 of each Rate Case Year, BPA shall remarket «Customer
> Name»'s PF Tier 2 rate purchase amounts and BPA shall remove «Customer
> Name»'s New Resources for the first Fiscal Year of the upcoming Rate
> Period if the sum of «Customer Name»'s PF Tier 2 rate purchase
> amounts, as established in Exhibit C, Purchase Obligations, plus
> «Customer Name»'s RHWM exceeds «Customer Name»'s annual Net
> Requirement forecast established in section 1.2 of Exhibit A, Net
> Requirements and Resources. The amount of such remarketing and
> resource removal is established in section 10.3 below. BPA shall
> remarket the PF Tier 2 rate purchase amounts and remove such New
> Resource amounts for the first Fiscal Year in the following order:
>
> \(1\) Amounts of Firm Requirements Power priced at PF Tier 2 rates
> listed in Exhibit C, Purchase Obligations, then
>
> \(2\) «Customer Name»'s Unspecified Resource Amounts listed in
> section 3.1 of Exhibit A, Net Requirements and Resources, then
>
> \(3\) «Customer Name»'s Specified Resources that are New Resources
> listed in section 2 of Exhibit A, Net Requirements and Resources. If
> «Customer Name» has multiple Specified Resources that are New
> Resources, BPA shall remove such resources in a last added, first
> removed order based on the order in which «Customer Name» made its
> resource additions.
>
> 10.2 **Order of Removal -- Second Fiscal Year of Rate Period**
>
> By September 15, 2012, and by September 15 of each Forecast Year
> thereafter, the process established in section 10.1 above shall also
> apply for the second Fiscal Year of the effective Rate Period and BPA
> shall remove «Customer Name»'s Existing Resources in the amount
> established in section 10.4 below. If «Customer Name» has multiple
> Existing Resources, BPA shall remove such resources in a last added,
> first removed order based on the order in which «Customer Name» made
> its resource additions.
>
> 10.3 **Extent of Removal for the First Fiscal Year of Each Rate
> Period**
>
> For the first Fiscal Year of a Rate Period BPA shall continue to
> remarket «Customer Name»'s PF Tier 2 rate purchase amounts and BPA
> shall continue to remove the amounts of «Customer Name»'s New
> Resources until:
>
> \(1\) the amount of PF Tier 2 rate purchase amounts remarketed by BPA
> plus the amount of New Resource removals equals the amount that
> «Customer Name»'s PF Tier 2 rate purchase amounts plus its RHWM
> exceeds its annual Net Requirement forecast, or
>
> \(2\) all of «Customer Name»'s PF Tier 2 rate purchase amounts are
> remarketed and all of its New Resources are removed.
>
> 10.4 **Extent of Removal for the Second Fiscal Year of Each Rate
> Period**
>
> For the second Fiscal Year of a Rate Period BPA shall first apply the
> process established in section 10.3 above. If «Customer Name»'s annual
> Net Requirement forecast for the second Fiscal Year of a Rate Period
> is lower than such forecast for the first Fiscal Year of the same Rate
> Period, then BPA shall then remove «Customer Name»'s Existing
> Resources. As long as «Customer Name» has Existing Resources to
> remove, the amount of such removal shall equal the lesser of: (1) the
> remaining amount that «Customer Name»'s RHWM exceeds its annual Net
> Requirement forecast, or (2) the difference between «Customer Name»'s
> annual Net Requirement forecasts for the first and second Fiscal Years
> of the Rate Period. If «Customer Name»'s annual Net Requirement
> forecast for the second Fiscal Year of a Rate Period is greater than
> or equal to such forecast for the first Fiscal Year of the same Rate
> Period, BPA shall remove zero amounts of «Customer Name»'s Existing
> Resources.
>
> 10.5 **Rounding of PF Tier 2 Rate Purchase Amounts**
>
> To the extent remarketing of PF Tier 2 rate purchase amounts results
> in an amount less than a whole average megawatt, BPA shall round such
> amount to a whole average megawatt.
>
> 10.6 **Remarketing of Federal Power Priced at PF Tier 2 Rates**
>
> Consistent with rates established under the TRM, «Customer Name» shall
> be subject to applicable charges or credits associated with BPA's
> remarketing of amounts of Firm Requirements Power at PF Tier 2 rates.
> «Customer Name» shall be responsible for remarketing of any amounts of
> its Dedicated Resources, Specified or Unspecified, that are removed
> under this section 10, Order of Tier 2 Remarketing and Resource
> Removal.

*END **BLOCK** and **SLICE/BLOCK** templates.*

*Include in **SLICE/BLOCK** template:*

> 10.7 **Monthly Resource Removal**
>
> In addition to the remarketing and resource removal described above,
> «Customer Name» shall annually remove or add monthly Dedicated
> Resource amounts to balance «Customer Name»'s Net Requirement with its
> purchase obligations under this Agreement. By September 15, 2011, and
> by September 15 of each Fiscal Year thereafter, «Customer Name» shall
> notify BPA in writing of the monthly Dedicated Resource amounts that
> «Customer Name» shall remove or add for the upcoming Fiscal Year.
> «Customer Name» shall remove or add its monthly Dedicated Resource
> amounts to ensure that «Customer Name»'s actual monthly Total Retail
> Load minus its monthly Dedicated Resource amounts is always greater
> than or equal to the sum of:
>
> \(1\) «Customer Name»'s monthly Critical Slice Amounts in section 2 of
> Exhibit I, Critical Slice Amounts,
>
> \(2\) «Customer Name»'s Tier 1 monthly purchase amounts (converted to
> megawatt-hours) listed in section 1.3 of Exhibit C, Purchase
> Obligations, and
>
> \(3\) «Customer Name»'s Tier 2 purchase amounts (converted to
> megawatt-hours) listed in section 2.5 of Exhibit C, Purchase
> Obligations.

*END **SLICE/BLOCK** template.*

[]{.mark}

*Include in **LOAD FOLLOWING** and **BLOCK** templates:*

***DELETE PRODUCT BELOW***

**11. RIGHT TO CHANGE PURCHASE OBLIGATION*(04/04/08 Version)***

> «Customer Name» shall have a one-time right to change its purchase
> obligation, identified in section 3 of this Agreement, to another
> purchase obligation available from BPA, including ***DELETE PRODUCT
> from TEMPLATE that customer purchases in section 3***Load Following,
> Block, or Slice/Block. If «Customer Name» chooses to change its
> purchase obligation, «Customer Name» shall first provide notice to BPA
> of its intent and then confirm its decision as established below. Any
> elections of rate alternatives, resource additions, or other notices
> given to BPA under this Agreement shall continue to be applicable
> under the new purchase obligation, provided that BPA may update such
> terms and conditions consistent with the then current terms of the new
> purchase obligation, and additional costs may apply for service under
> the new purchase obligation as described in section 11.2 below.
>
> 11.1 **Notice to Change**
>
> By June 30, 2016, «Customer Name» shall provide written notice to BPA
> that it is requesting to change its purchase obligation effective
> October 1, 2019, subject to confirmation described in section 11.3
> below. «Customer Name»'s notice shall state the type of service
> requested, and if requesting a change to the Slice/Block purchase
> obligation, «Customer Name» shall state a range of Slice amounts
> between a specified minimum and maximum amount of Slice that «Customer
> Name» will accept.
>
> 11.2 **Charge to Change Purchase Obligation**
>
> «Customer Name» may be subject to charges as a result of «Customer
> Name»'s request to change its purchase obligation. By October 31,
> 2016, BPA shall determine and present «Customer Name» with any such
> charges. In no event shall BPA make payment to «Customer Name» as a
> result of «Customer Name» changing its purchase obligation.
>
> 11.3 **Change Confirmation**
>
> Within 30 days of BPA's presentation to «Customer Name» of the charges
> determined in 11.2 above, «Customer Name» shall provide BPA with
> written confirmation of its decision to change its purchase
> obligation. If «Customer Name» is requesting a change to the
> Slice/Block purchase obligation, such confirmation constitutes
> agreement that «Customer Name» shall purchase an amount of Slice
> within «Customer Name»'s specified range of acceptable Slice amounts,
> if made available by BPA.
>
> 11.4 **Slice Amount**
>
> If «Customer Name» requests a change to the Slice/Block purchase
> obligation, BPA shall determine «Customer Name»'s specific amount of
> Slice as follows:
>
> \(1\) BPA shall determine the total amount of Slice available for
> purchase by all customers requesting a change to Slice/Block.
>
> \(2\) If such amount is sufficient to meet the requested maximum
> amount of Slice from all customers requesting a change to Slice/Block,
> BPA shall provide to «Customer Name» its requested maximum amount of
> Slice as part of the new agreement.
>
> \(3\) If such amount is insufficient to meet the requested maximum
> amount of Slice from all customers requesting a change to Slice/Block,
> BPA shall reduce individual Slice amounts of customers requesting a
> change to Slice/Block pro rata based on the requested maximum amount
> of Slice. If «Customer Name»'s individual Slice amount is below its
> specified minimum, «Customer Name» shall retain its current purchase
> obligation.
>
> 11.5 **Agreement Amendment**
>
> Following «Customer Name»'s confirmation of its decision to change its
> purchase obligation, the Parties shall amend this Agreement to replace
> the terms of «Customer Name»'s current purchase obligation with the
> terms of the new purchase obligation. The amendment shall be effective
> no later than October 1, 2019.

*END **LOAD FOLLOWING** and **BLOCK** templates.*

*Include in **SLICE/BLOCK** template:*

**11. RIGHT TO CHANGE PURCHASE OBLIGATION*(04/04/08 Version)***

> 11.1 **One-Time Right to Change Purchase Obligation**
>
> *[Reviewers Note]{.underline}: Shaded text is identical to Load
> Following and Block text:*
>
> «Customer Name» shall have a one-time right to change its purchase
> obligation, identified in section 3 of this Agreement, to another
> purchase obligation available from BPA, including Load Following or
> Block. If «Customer Name» chooses to change its purchase obligation
> under this section 11.1, «Customer Name» shall first provide notice to
> BPA of its intent and then confirm its decision as established below.
> Any elections of rate alternatives, resource additions, or other
> notices given to BPA under this Agreement shall continue to be
> applicable under the new purchase obligation, provided that BPA may
> update such terms and conditions consistent with the then current
> terms of the new purchase obligation, and additional costs may apply
> for service under the new purchase obligation as described in
> section 11.2 below.
>
> 11.1.1 **Notice to Change**
>
> By May 31, 2016, «Customer Name» shall provide written notice to BPA
> that it is requesting to change its purchase obligation effective
> October 1, 2019, subject to confirmation described in section 11.3
> below. «Customer Name»'s notice shall state the type of service
> requested.
>
> 11.1.2 **Charge to Change Purchase Obligation**
>
> «Customer Name» may be subject to charges as a result of «Customer
> Name»'s request to change its purchase obligation. By September 30,
> 2016, BPA shall determine and present «Customer Name» with any such
> charges. In no event shall BPA make payment to «Customer Name» as a
> result of «Customer Name» changing its purchase obligation.
>
> 11.1.3 **Change Confirmation**
>
> Within 30 days of BPA's presentation to «Customer Name» of the charges
> determined in 11.2 above, «Customer Name» shall provide BPA with
> written confirmation of its decision to change its purchase
> obligation.
>
> 11.1.4 **Agreement Amendment**
>
> Following «Customer Name»'s confirmation of its decision to change its
> purchase obligation, the Parties shall amend this Agreement to replace
> the terms of «Customer Name»'s current purchase obligation with the
> terms of the new purchase obligation. The amendment shall be effective
> no later than October 1, 2019.
>
> 11.2 **Additional Rights to Change Purchase Obligation** ***(07/02/08
> Version)***
>
> In addition to the opportunity to change its purchase obligation
> provided in section 11.1 above, «Customer Name» may elect to change
> its purchase obligation to that stated in section 11.2.4 below after
> the occurrence of any of the events listed in sections 11.2.1 through
> 11.2.3 below by providing BPA with written notice by the dates shown
> below. The notice shall state an effective date for the contingent
> contract amendment as established in 11.2.4 below, of not later than
> 90 days after the date of such notice.
>
> 11.2.1 **Simulator Fails Simulator Performance Test**
>
> 11.2.1.1 **Definition**
>
> "Simulator Performance Test" means a three (3) part test, as described
> in section 11.2.1.3, that is conducted by BPA to assess the
> (1) energy, (2) peaking, and (3) ramp down capabilities of the
> Simulator.
>
> 11.2.1.2 **Simulator Performance Test To Be Completed No Later than
> October 15, 2010**
>
> No later than August 1, 2010, BPA shall provide «Customer Name» access
> to the version of the Simulator that will be used by BPA to conduct
> the Simulator Performance Test. The Simulator Performance Test shall
> be conducted by BPA no later than October 15, 2010.
>
> 11.2.1.3 **Description of Simulator Performance Test**
>
> The Simulator Performance Test shall be conducted by BPA and will
> consist of three separate tests: an energy test, a peaking test, and a
> ramp down test. Each test is described separately in section 2.1.5.3
> of Exhibit M.
>
> 11.2.1.4 **Simulator Fails Simulator Performance Test**
>
> If, as of October 15, 2010, the Simulator has failed one or more of
> the three tests that comprise the Simulator Performance Test, then
> «Customer Name» may change its purchase obligation to that stated in
> 11.2.4 below by providing written notice to BPA. Such written notice
> must be received by BPA no later than December 15, 2010. The Simulator
> Performance Test shall continue to be conducted by BPA after
> October 15, 2010, until such time as it passes, pursuant to
> section 5.12.2 above.
>
> 11.2.1.5 **Simulator Passes Simulator Performance Test**
>
> If, as of October 15, 2010, the Simulator has passed the Simulator
> Performance Test, then «Customer Name» shall not have the option to
> change its purchase obligation pursuant to this section 11.2.1.
>
> 11.2.2 **No Slice Output Available on a Forecasted Basis**
>
> «Customer Name» may change its purchase obligation to that stated in
> 11.2.4 below not later than 60 days after BPA forecasts prior to the
> first day of any FY that there will be no Slice Output available for
> delivery to «Customer Name» during such FY and the immediately
> following FY, or in the event there is no Slice Output available to
> «Customer Name» during any two consecutive FYs.
>
> 11.2.3 **Transmission Conversion*(05/25/08 Version)***
>
> «Customer Name» may change its purchase obligation to that stated in
> 11.2.4 below not later than 60 days after FERC has issued a final
> order approving rates, terms and conditions, or the Balancing
> Authority or a regulatory authority with jurisdiction over the
> Balancing Authority, adopts standards, rules, practices or procedures
> that require «Customer Name» to declare a Point of Receipt and a
> energy amount (in megawatts) for each of the Slice System resources
> from which «Customer Name» may receive Slice Output under this
> Agreement.
>
> 11.2.4 **Alternative Requirements Power Purchase Obligation**
>
> *[Drafter's Note]{.underline}: Insert the purchase obligation that the
> Slice/Block customer wants to convert to if it changes its purchase
> obligation under 11.2.1 through 11.2.3 above*
>
> «Customer Name» selects the *«*Load Following Purchase Obligation
> ***or*** Block Without Shaping Capacity Purchase Obligation ***or***
> Block With Shaping Capacity Purchase Obligation*»* as the purchase
> obligation that it will purchase in the event «Customer Name» changes
> its purchase obligation under the events specified in sections 11.2.1
> through 11.2.3 above. No later than June 30, 2009, the Parties shall
> execute a contingent contract amendment for the selected purchase
> obligation. Such contingent contract amendment shall contain the same
> terms and conditions as this Agreement, including any elections or
> choices made under this Agreement, that are applicable to the purchase
> obligation selected by «Customer Name». Such contingent contract
> amendment shall become effective on the date provided in «Customer
> Name»'s notice under section 11.2 above.
>
> 11.2.5 **Waiver of Certain Claims for Damages**
>
> In the event that «Customer Name» changes its purchase obligation in
> accordance with this section 11.2, «Customer Name» agrees not to seek
> and hereby waives the right to pursue any claim for damages from BPA
> due to any such change. This waiver is limited to any claims «Customer
> Name» may have arising from changes to «Customer Name»'s purchase
> obligation under this section 11.2. This waiver has no application to,
> and «Customer Name» hereby expressly preserves, any claims for damages
> arising under any other section of this Agreement including, without
> limitation, section [«#»]{.mark}.

*END **SLICE/BLOCK** template.*

*[Include in]{.mark}* ***[SLICE/BLOCK, LOAD FOLLOWING, and BLOCK (except
NR BLOCK)]{.mark}*** [*templates:*]{.mark}

**12. BILLING CREDITS AND RESIDENTIAL EXCHANGE *(06/10/08 Version)***

> 12.1 **Billing Credits*(02/28/08 Version)***
>
> If «Customer Name» develops a Generating Resource to serve its retail
> loads above its RHWM, «Customer Name» agrees that it shall forego any
> request for, and BPA is not obligated to include, billing credits, as
> defined in section 6(h) of the Northwest Power Act, on «Customer
> Name»'s bills under this Agreement. This section does not apply to any
> billing credit contracts in effect as of the execution date of this
> Agreement.
>
> 12.2 **Residential Exchange *(06/16/08 Version)***
>
> If «Customer Name» elects to seek residential exchange benefits from
> BPA pursuant to section 5(c) of the Northwest Power Act, «Customer
> Name» agrees it will not seek and shall not receive exchange benefits:
> (1) for Total Retail Load in excess of «Customer Name»'s RHWM load, or
> (2) based upon the cost of [any]{.mark} resources [except]{.mark}
> «Customer\'s Name»'s resource[s (in the]{.mark} amounts
> [thereof)]{.mark} used in calculating its CHWM [and that were acquired
> on or before September 30, 2006. \[\[Comment: The RPSA Template
> includes the following provision for public customers: "«Customer
> Name»]{.mark} [agrees that, for purposes of determining ASC,]{.mark}
> [«Customer Name»]{.mark} [shall only include in each Appendix 1 filing
> the costs of resources that were acquired on or before September 30,
> 2006."\]\]]{.mark} The determination of what exchange benefits
> «Customer Name» shall not receive as a consequence of «Customer
> Name»'s agreement in the preceding sentence will be made by BPA
> pursuant to BPA's then-existing ASC Methodology.
>
> The preceding paragraph will also be included in any Residential
> Purchase and Sale Agreement entered into between «Customer Name» and
> BPA during the term of this Agreement.

*[End]{.mark}* ***[SLICE/BLOCK, LOAD FOLLOWING, and BLOCK (except NR
BLOCK)]{.mark}*** *[templates.]{.mark}*

*Include in **LOAD FOLLOWING** template:*

**13. SCHEDULING*(03/27/08 Version)***

> *[Option 1]{.underline}: Include for Transfer Service customers with a
> BPA NT Transmission Agreement:*
>
> From October 1, 2011, through September 30, 2028, Power Services shall
> provide and «Customer Name» shall purchase Transmission Scheduling
> Service. The Parties shall administer «Customer Name»'s Transmission
> Scheduling Service consistent with Exhibit F, Transmission Scheduling
> Service.
>
> *End Option 1*
>
> *[Option 2]{.underline}: Include for **non-**Transfer Service
> customers with a BPA NT Transmission Agreement:*
>
> Over the term of this Agreement, «Customer Name» may be required to
> purchase, or may have the option to purchase, Transmission Scheduling
> Service from Power Services in accordance with Exhibit F, Scheduling.
> If «Customer Name» is required or elects to purchase Transmission
> Scheduling Service from Power Services, Exhibit F, Scheduling shall be
> replaced with the Transmission Scheduling Service exhibit. If
> «Customer Name» is not purchasing Transmission Scheduling Service from
> Power Services, «Customer Name» shall comply with the scheduling
> requirements described in sections 2 and 3 of Exhibit F, Scheduling.
>
> *End Option 2*
>
> *[Option 3]{.underline}: Include for customers with a BPA PTP
> Transmission Agreement:*
>
> «Customer Name» shall be responsible for scheduling transmission to
> serve its Total Retail Load. In addition, «Customer Name» shall comply
> with the scheduling requirements described in Exhibit F, Scheduling.
>
> *End Option 3*

*END **LOAD FOLLOWING** template.*

*Include in **BLOCK** and **SLICE/BLOCK** templates:*

**13. SCHEDULING** ***(03/27/08 Version)***

> «Customer Name» shall schedule power in accordance with Exhibit F,
> Scheduling.

*END **BLOCK** and **SLICE/BLOCK** templates.*

**14. DELIVERY** ***(03/17/08 Version)***

> 14.1 **Definitions**
>
> 14.1.1 "Integrated Network Segment"***(03/17/08 Version)*** means
> those facilities of the Federal Columbia River Transmission System
> that are required for the delivery of bulk power supplies, the costs
> for which are recovered through generally applicable rates, and that
> are identified as facilities in the Integrated Network Segment, or its
> successor, in the BPA segmentation study for the applicable
> transmission Rate Period as determined in a hearing establishing or
> revising BPA's transmission rates pursuant to section 7(i) of the
> Northwest Power Act.
>
> 14.1.2 "Primary Points of Receipt"***(03/17/08 Version)*** means the
> points on the Pacific Northwest transmission system where Firm
> Requirements Power is forecasted to be made available by Power
> Services to «Customer Name» for purposes of obtaining a long-term firm
> transmission contract.
>
> 14.1.3 "Scheduling Points of Receipt"***(03/17/08 Version)*** means
> the points on the Pacific Northwest transmission system where Firm
> Requirements Power is made available by Power Services to «Customer
> Name» for purposes of transmission scheduling.
>
> 14.2 **Transmission Service *(03/17/08 Version)***
>
> *[Option 1]{.underline}: Include the following for customers who are
> NOT served by transfer:*
>
> 14.2.1 «Customer Name» is responsible for delivery of power from the
> Scheduling Points of Receipt.
>
> *End option 1*
>
> *[Option 2]{.underline}: Include the following for customers who ARE
> served by transfer.*
>
> 14.2.1 «Customer Name» is responsible for delivery of power from the
> Scheduling Points of Receipt, except as provided under section 14.6
> below.
>
> *End option 2*
>
> 14.2.2 «Customer Name» shall provide at least 60 days' notice to Power
> Services prior to changing Balancing Authority Areas.
>
> 14.2.3 At «Customer Name»'s request, BPA shall provide «Customer Name»
> with Primary Points of Receipt and other information needed to enable
> «Customer Name» to obtain long-term firm transmission for delivery of
> power sold under this Agreement. If required by Transmission Services
> for purposes of transmission scheduling, Power Services shall provide
> «Customer Name» with Scheduling Points of Receipt. Power Services has
> the right to provide power to «Customer Name» at Scheduling Points of
> Receipt that are different than the Primary Points of Receipt. If BPA
> does provide power to «Customer Name» at Scheduling Points of Receipt
> that are different than the Primary Points of Receipt, then BPA shall
> reimburse «Customer Name» for any incremental, direct,
> non-administrative costs incurred by «Customer Name» to comply with
> delivering Firm Requirements Power from such a Scheduling Point of
> Receipt to «Customer Name»'s load if the following conditions, as
> outlined, have been met:
>
> \(1\) Customer Name» has requested long-term firm transmission service
> to deliver its Firm Requirements Power using the Primary Points of
> Receipt and other information provided by Power Services; and,
>
> \(2\) This condition only applies if «Customer Name» has long-term
> Point to Point (PTP) transmission service (as defined in BPA's Open
> Access Transmission Tariff) for delivery of Firm Requirements Power to
> its load: «Customer Name» has submitted a request to redirect its
> long-term firm PTP transmission service to deliver Firm Requirements
> Power from the Scheduling Point of Receipt on a firm basis, but that
> request was not granted; and
>
> \(3\) «Customer Name»'s transmission schedule was curtailed due to
> non-firm status under PTP transmission service or its secondary
> service status under Network Integration Transmission Service (as
> defined in BPA's Open Access Transmission Tariff) and «Customer Name»
> can provide proof of the reimbursable costs incurred to replace the
> curtailed schedule.
>
> 14.3 **Liability for Delivery*(05/25/08 Version)***
>
> «Customer Name» waives any claims against BPA arising under this
> Agreement for nondelivery of power to any points beyond the applicable
> Scheduling Points of Receipt, except as described in section 14.2.3
> above. BPA shall not be liable under this Agreement for any
> third-party claims related to the delivery of power after it leaves
> the Scheduling Points of Receipt. Neither Party shall be liable under
> this Agreement to the other Party for damage that results from any
> sudden, unexpected, changed, or abnormal electrical condition
> occurring in or on any electric system, regardless of ownership. These
> limitations on liability apply regardless of whether or not this
> Agreement provides for transfer service.

*Include in **LOAD FOLLOWING** and **BLOCK** templates:*

> 14.4 **Real Power Losses *(03/14/08 Version)***
>
> BPA is responsible for the real power losses necessary to deliver Firm
> Requirements Power to «Customer Name»'s PODs listed in Exhibit E,
> Metering.

*END **LOAD FOLLOWING** and **BLOCK** templates.*

*Include in **SLICE/BLOCK** template:*

> *[Option 1]{.underline}: Include the following if customer purchases
> the Slice/Block product and is NOT served by Transfer.*
>
> 14.4 **Real Power Losses *(03/14/08 Version)***
>
> BPA is responsible for the real power losses necessary to deliver Firm
> Requirements Power under the Block power product to «Customer Name»'s
> PODs listed in Exhibit E, Metering. «Customer Name» shall be
> responsible for all real power losses associated with the delivery of
> power under the Slice power product.
>
> *End Option 1*
>
> *[Option 2]{.underline}: Include the following if customer purchases
> the Slice/Block product and IS served by Transfer.*
>
> 14.4 **Real Power Losses *(03/14/08 Version)***
>
> BPA is responsible for the real power losses necessary to deliver Firm
> Requirements Power under the Block power product to «Customer Name»'s
> PODs listed in Exhibit E, Metering.
>
> «Customer Name» shall be responsible for all real power losses
> associated with the delivery of power under the Slice power product
> except BPA shall be responsible for real power losses associated with
> the delivery of Firm Requirements Power across the Third Party
> Transmission Provider's system to «Customer Name»'s load.
>
> *End Option 2*

*END **SLICE/BLOCK** template.*

> 14.5 **Metering Losses** ***(05/14/08 Version)***
>
> BPA shall adjust measured amounts of power to account for losses, if
> any, that occur between «Customer Name»'s PODs and the respective
> POMs, as specified in Exhibit E, Metering.
>
> *[Option]{.underline}: Include section 14.6 for Transfer Service
> Customers. (\*Note: section 14.6 is over 2 pages long)*
>
> 14.6 **Delivery by Transfer *(04/03/08 Version)***
>
> Subject to the limitations in this section, BPA agrees to acquire and
> pay for Transfer Service to deliver Firm Requirements Power and
> Surplus Firm Power to «Customer Name»'s PODs, as listed in Exhibit E,
> Metering, in an amount not to exceed «Customer Name»'s Total Retail
> Load on an hourly basis. *[Drafter's Note]{.underline}: Include the
> following sentence for all Transfer Service customers **with** ARTS
> contracts and add the ARTS contract number. Delete the following
> sentence for the following* *Transfer Service customers without ARTS
> contracts (See Customer Characteristics Spreadsheet to verify):
> Columbia REA, City of Weiser, Port of Seattle, Whatcom Co PUD, and
> Clark PUD:*In the event that a conflict exists between the provisions
> of this Agreement and the Agreement Regarding Transfer Service (ARTS)
> Contract No. 05EO-«#####», this Agreement shall govern.\]
>
> 14.6.1 **Ancillary Services *(02/28/08 Version)***
>
> BPA shall acquire and pay for Ancillary Services (as defined in BPA's
> Open Access Transmission Tariff) needed for «Customer Name»'s Transfer
> Service subject to the following limitations:
>
> \(1\) «Customer Name» shall reimburse BPA for regulation service or
> its replacement at the applicable Transmission Services rate, or its
> successor.
>
> \(2\) BPA shall pay for the Ancillary Service(s) charged by a
> Third-Party Transmission Provider to deliver Firm Requirements Power
> to the PODs listed in Exhibit E, Metering, only if «Customer Name» is
> also purchasing such Ancillary Service(s) from Transmission Services
> to deliver Firm Requirements Power to the PODs in Exhibit E, Metering.
> If at any time «Customer Name» is not purchasing Ancillary Service(s)
> from Transmission Services to deliver Firm Requirements Power to one
> or more of the PODs listed in Exhibit E, Metering, then «Customer
> Name» shall reimburse BPA for the Ancillary Service(s) charges BPA
> incurs from the Third Party Transmission Provider to deliver power to
> such POD(s), at the applicable or equivalent Transmission Services
> Ancillary Services rate.
>
> 14.6.2 **Low Voltage Delivery *(02/28/08 Version)***
>
> Low Voltage Delivery is service over the Low Voltage Segment by any
> Third Party Transmission Provider's system. "Low Voltage Segment"
> means the facilities of a Third-Party Transmission Provider that are
> equivalent to the voltage level of the facilities excluded by
> Transmission Services from the Integrated Network Segment. For Low
> Voltage Delivery, «Customer Name» shall pay Power Services the
> applicable General Transfer Agreement (GTA) Delivery Charge, or its
> successor rate, consistent with the applicable BPA Wholesale Power
> Rate Schedules and GRSPs. The Parties shall list «Customer Name»'s
> PODs that require Low Voltage Delivery in Exhibit E, Metering.
>
> 14.6.3 **Direct Assignment Costs *(03/26/08 Version)***
>
> «Customer Name» shall pay BPA for all directly assigned costs,
> including but not limited to: facility or system studies costs,
> construction costs, upgrade costs, and expansion costs, or other
> capital costs for facilities directly associated with service to any
> «Customer Name» PODs assessed by the Third Party Transmission Provider
> to BPA. Such costs shall be consistent with Transmission Services'
> "Guidelines for Direct Assignment Facilities," and the "Final
> Supplemental Guidelines for Direct Assignment of Facilities Costs
> Incurred Under Transfer Agreements" included in BPA's Long Term
> Regional Dialogue Final Policy, July 2007, or any other revision of
> that policy, or as proposed in a BPA general rate case. [\[\[This
> provision should not refer to a BPA proposal in a general rate case,
> which may or may not be adopted.\]\]]{.mark}
>
> 14.6.4 **Penalties Assessed By the Third Party Transmission Provider**
>
> BPA has the right to directly pass through to «Customer Name» any
> penalty charges assessed by the Third Party Transmission Provider that
> are associated with BPA's acquisition of Transfer Service to the PODs
> identified in Exhibit E, Metering. Such charges may include, but are
> not limited to, power factor penalties or excessive energy imbalance
> penalties.
>
> 14.6.5 **Removal of PODs*(05/14/08 Version)***
>
> BPA may terminate deliveries at a POD if «Customer Name» consents to
> the termination or if the Parties determine that «Customer Name»'s
> requirements for power at such point may be adequately supplied under
> reasonable conditions and circumstances at different POD(s):
>
> \(1\) directly from the FCRTS,
>
> \(2\) indirectly from the facilities of another transmission
> owner/operator, or
>
> \(3\) both.
>
> 14.6.6 **Annexed Loads** ***(03/14/08 Version)***
>
> BPA shall arrange and pay for Transfer Service for federal power
> deliveries to serve «Customer Name»'s Annexed Load. «Customer Name»
> shall provide BPA written notice of any Annexed Load acquired greater
> than 1 average megawatt no later than 90 days prior to the
> commencement of service to the Annexed Load.
>
> However, BPA's obligation to provide Transfer Service to «Customer
> Name»'s Annexed Load shall be limited by the megawatt caps and process
> for annexed and new public customers set forth in BPA's Long Term
> Regional Dialogue Final Policy, July 2007, or any revision of that
> policy.
>
> [\[\[Comment: BPA has failed to explain its legal authority for
> providing and paying for Transfer Service for new and annexed
> loads---including, in particular, transfer service for non-federal
> power---and such legal authority is not apparent from the statutes. In
> any event,]{.mark} [BPA should not provide transfer service to annexed
> loads and new publics. Providing such transfer service would be an
> unjustified and unwarranted subsidy that will provide a financial
> incentive for annexation of investor owned utilities' service
> territories.\]\]]{.mark}
>
> 14.6.7 **Non-Federal Deliveries** ***(04/03/08 Version)***
>
> If «Customer Name» has a non-federal resource or is acquiring a
> non-federal resource necessary to serve its Total Retail Load above
> the established RHWM, and «Customer Name» has requested that BPA
> assist in the acquisition of transmission services for such resource,
> BPA shall offer «Customer Name» a separate agreement for specific
> terms and conditions under which BPA will obtain Transfer Service on a
> Third Party Transmission Provider's system for delivery of that
> resource to «Customer Name»'s system. Such agreement shall not be
> subject to section 22, Governing Law and Dispute Resolution. BPA shall
> develop the agreement consistent with the principles of service
> specified in Exhibit G, Principles of Non-Federal Transfer Service.
>
> *[Drafter's Note]{.underline}: Include section for the following
> customers with load interconnected to multiple transmission systems
> (See Customer Characteristics Spreadsheet to verify): Asotin County
> PUD, Benton REA, Big Bend, Central Electric Coop, Clark Co,
> Clearwater, Columbia Basin, Columbia Power, Columbia REA, Columbia
> River, Cowlitz, Douglas Electric, Emerald, Harney, Hood River, Inland,
> Kittitas, Klickitat, Lane, Lewis, Northern Lights, Oregon Trail,
> Surprise Valley, Tillamook, Umatilla Electric, Wasco, Wells Rural,
> West OR, Whatcom:*
>
> 14.6.8 **Proportional Scheduling Of Non-Federal Resources Over
> Multiple Transmission Systems *(07/02/08 Version)***
>
> If «Customer Name» has load interconnected to multiple transmission
> systems, and if «Customer Name» is applying non-federal resources to
> serve its Above-RHWM Load, such non-federal resources shall be
> scheduled proportionately to «Customer Name»'s load based on the
> ratios listed in Exhibit D, Additional Products and Special
> Provisions, except as provided below.
>
> 14.6.8.1 **De Minimis Exception**
>
> If «Customer Name»'s Above-RHWM load interconnected to a transmission
> system is less than 8,760 megawatt-hours, then «Customer Name»'s
> non-federal resources serving Above-RHWM Load shall be delivered to
> the load on the transmission system serving the majority of the load.
> If «Customer Name» is eligible for this de minimis exception for the
> upcoming Rate Period, BPA shall notify «Customer Name» of such
> eligibility by July 31, 2010 and by July 31 of every Forecast Year
> through the term of this Agreement.
>
> 14.6.8.2 **Alternative Scheduling of Non-Federal Resources**
>
> If «Customer Name» is not eligible for the de minimis exception, and
> if «Customer Name» seeks to schedule its non-federal resources serving
> Above-RHWM Load at a ratio different than that included in Exhibit D,
> Additional Products and Special Provisions, «Customer Name» may notify
> BPA by August 15, 2010 and by August 15 of every Forecast Year through
> the term of this Agreement to request an alternative scheduling
> exception. Upon such request, BPA shall assess whether «Customer Name»
> has sufficient load interconnected to the transmission system
> «Customer Name» proposes to deliver the non-federal resource to
> accommodate the non-federal resource.
>
> If BPA determines that «Customer Name»'s load is not sufficient to
> accommodate the non-federal resource during the upcoming Rate Period,
> BPA shall notify «Customer Name» that «Customer Name» shall apply its
> non-federal resources to serve its Above-RHWM Load proportionately to
> «Customer Name»'s load based on the ratios in Exhibit E, Metering.
>
> If BPA determines that «Customer Name»'s load is sufficient to
> accommodate the non-federal resource during the upcoming Rate Period,
> BPA shall notify «Customer Name» that «Customer Name» qualifies for
> the alternative scheduling exception for the upcoming Rate Period.
>
> BPA shall pass through to «Customer Name» any costs BPA determines are
> shifted to BPA by «Customer Name»'s non-federal resources serving
> Above-RHWM Load not scheduled proportionately to its load. Such
> incremental costs include, but are not limited to: losses, risk of
> increased curtailments, and ancillary services. BPA shall calculate
> the value of «Customer Name»'s cost shifts and notify «Customer Name»
> of such costs by September 15, 2010 and by September 15 of every
> Forecast Year through the term of this Agreement.
>
> By September 30, 2010 and by September 30 of every Forecast Year
> through the term of this Agreement, «Customer Name» must notify BPA if
> it shall accept the alternative scheduling exception and the
> associated costs, or if «Customer Name» will apply its non-federal
> resources to serve its Above-RHWM Load, proportionately to «Customer
> Name»'s load based on the ratios listed in Exhibit D, Additional
> Products and Special Provisions.
>
> If «Customer Name» chooses the alternative scheduling exception, BPA
> shall amend Exhibit D, Additional Products and Special Provisions to
> include the alternative amount and/or ratio of non-federal resources
> to serve Above-RHWM Load that shall be scheduled.
>
> By July 31 each Forecast Year over the term of this Agreement, BPA
> shall determine «Customer Name»'s load ratio proportions and the
> Parties shall update the ratio table in Exhibit D, Additional Products
> and Special Provisions. Each Rate Period «Customer Name» shall elect,
> consistent with the timeline described above, whether it will continue
> the alternative scheduling exception. If «Customer Name» continues
> with such, BPA shall price the cost shift of this election based on
> the updated load forecast, any changes to «Customer Name» non-federal
> resources, and any transmission conditions that have changed since the
> last update of the cost shift pricing.
>
> *End Option 14.6.8 Proportional Scheduling*
>
> *END Option 14.6 for Transfer Service Customers.*

*Include in **LOAD FOLLOWING** template:*

**15. METERING *(06/04/08 Version)***

> 15.1 **Measurement *(06/03/08 Version)***
>
> By September 30, 2010, «Customer Name» shall ensure that meters are
> installed on all PODs listed in Exhibit E, Metering, consistent with
> the requirements of this section 15, Metering. «Customer Name» shall
> pay for the amount of power measured by such meters. If the Parties
> agree that metering is economically or technologically impractical,
> then:
>
> \(1\) the Parties shall use scheduled amounts to measure the amount of
> power purchased if such power is scheduled into or out of «Customer
> Name»'s service territory; or
>
> \(2\) the Parties shall use mutually acceptable load profiles to
> measure the amount of power purchased if such power is not scheduled
> into or out of «Customer Name»'s service territory.
>
> *[Reviewer's Note]{.underline}: The Meter Usage Data Estimations
> provision of GRSPs will be developed prior to 2011. These provisions
> are currently contained in BPA billing procedures.*
>
> If the metering equipment associated with the meters listed in
> Exhibit E, Metering, fails to properly measure or record the interval
> readings, BPA shall apply the procedure set out in the Meter Usage
> Data Estimations provision of the GRSPs to determine the appropriate
> billing adjustment.
>
> 15.2 **Existing BPA Owned Meters*(05/13/08 Version)***
>
> At BPA's expense, BPA shall operate, maintain, and replace, as
> necessary, all metering equipment owned by BPA that is needed to plan,
> schedule, and bill for power. «Customer Name» authorizes BPA to
> install any metering equipment on «Customer Name»'s facilities that is
> reasonably necessary to forecast, plan, schedule, and bill for power.
> With reasonable notice from BPA, and for the purpose of implementing
> this provision, «Customer Name» shall grant BPA physical access to BPA
> owned meters at BPA's request.
>
> If, at any time, BPA or «Customer Name» determines that a BPA owned
> meter is defective or inaccurate, BPA shall adjust, repair, or replace
> the meter to provide accurate metering as soon as practical.
>
> 15.3 **Non-BPA Owned Meters*(05/29/08 Version)***
>
> «Customer Name» shall operate, maintain, and replace, as necessary at
> «Customer Name»'s expense, all non-BPA metering equipment owned by
> «Customer Name» that is needed by BPA to forecast, plan, schedule, and
> bill for power for:
>
> \(1\) points of interconnection between «Customer Name»'s system and
> parties other than BPA;
>
> \(2\) all loads that require separate measurement for purposes of
> forecasting, planning, scheduling, or billing for power; and
>
> \(3\) Generating Resources listed in Exhibit A, Net Requirements, that
> are interconnected to «Customer Name»'s system.
>
> For non-BPA owned meters not owned by «Customer Name» needed by BPA to
> forecast, plan, schedule and bill for power, «Customer Name» shall
> arrange for such meters to be operated, maintained and replaced, as
> necessary, for the measurements described above in sections 15.3(1)
> and 15.3(2), and for any Generating Resources listed in Exhibit A, Net
> Requirements, that require metering.
>
> This section 15.3 shall not apply to non-BPA owned meters that are
> owned by a Third-Party Transmission Provider with which BPA holds a
> transmission contract for service to «Customer Name» load. In these
> cases the metering arrangements shall be between BPA and the
> Third-Party Transmission Provider.
>
> «Customer Name» shall give BPA direct, electronic access to meter data
> from all meters not owned by BPA that are capable of being accessed
> electronically. For the purpose of inspection, «Customer Name» shall
> grant BPA reasonable physical access to «Customer Name» meters at
> BPA's request.
>
> If, at any time, BPA or «Customer Name» determines that a non-BPA
> owned meter listed in Exhibit E, Metering is defective or inaccurate,
> «Customer Name» shall adjust, repair, or replace the meter to provide
> accurate metering as soon as practical. BPA shall have the right to
> witness any meter tests on non-BPA owned meters listed in Exhibit E,
> Metering and, with reasonable advance notice, BPA may conduct tests on
> such meters. «Customer Name» shall have the right to witness any meter
> tests conducted by BPA.
>
> 15.4 **New Meters *(06/10/08 Version)***
>
> «Customer Name» and Transmission Services may enter into a separate
> agreement addressing the location, cost responsibility, access,
> maintenance, testing, and liability of the Parties with respect to new
> meters.
>
> All new and replaced meters shall meet American National Standard
> Institute standards, including, but not limited to C12.20, Electricity
> Meters---0.2 and 0.5 Accuracy Classes, and the Institute of Electrical
> and Electronics Engineers, Inc. standard C57.13, Requirements for
> Instrument Transformers, or their successors. Any new and replaced
> meters shall be able to record meter data hourly and store data for a
> minimum of 45 days.
>
> 15.5 **Metering an NLSL *(06/13/08 Version)***
>
> «Customer Name» shall meter any loads that are monitored by BPA for an
> NLSL determination and any NLSLs consistent with section 24.3.4,
> Metering an NLSL.
>
> 15.6 **Metering Exhibit *(05/13/08 Version)***
>
> «Customer Name» shall provide meter data specified in section 17.3,
> Information Exchange and Confidentiality, and shall notify BPA of any
> changes to PODs, POMs, Interchange Points and related information for
> which it is responsible. BPA shall list «Customer Name»'s PODs and
> meters in Exhibit E, Metering.

*END **LOAD FOLLOWING** template.*

*Include in **BLOCK** and **SLICE/BLOCK** templates:*

**15. METERING** ***(06/03/08 Version)***

> *[Reviewer's Note]{.underline}: The customer list below is subject to
> change.*
>
> *[Option 1]{.underline}: Include this subsection for customers that do
> NOT have meters on **all** PODs: (See Customer Characteristics
> Spreadsheet to verify: EWEB, Grant PUD, Okanogan PUD, Seattle, Tacoma,
> Port of Seattle).*
>
> 15.1 **Requirements for Meters**
>
> «Customer Name»'s purchase commitment in section 3 of this Agreement
> does not require load meters for billing and payment. For purposes of
> forecasting and planning, BPA may require «Customer Name» to provide
> BPA some or all of «Customer Name»'s load data, as required by
> section 17.5, Hourly Total Retail Load Data.
>
> If, during the term of this Agreement, BPA determines that the load
> data BPA has requested and «Customer Name» has provided to BPA is not
> adequate or verifiable, or if BPA determines that either load or
> resource meter data is needed to administer this Agreement, «Customer
> Name» shall allow BPA to install BPA owned meters, at BPA's expense,
> to collect such data. For all existing meters listed in Exhibit E,
> Metering used by BPA for forecasting and planning, and for new meters,
> the following requirements shall apply.
>
> *End Option 1*
>
> *[Reviewer's Note]{.underline}: The customer list below is subject to
> change.*
>
> *[Option 2]{.underline}: Include this subsection for customers that
> currently have load meters accessible to BPA on all of the customer's
> load: (See Customer Characteristics Spreadsheet to verify: Benton PUD,
> Blachly-Lane, Central, Clatskanie PUD, Clearwater, Consumer's Power,
> Coos-Curry, Douglas Electric, Fall River, Franklin PUD, Grays Harbor,
> Idaho Falls, Lane, Lost River, Northern Lights, Okanogan Electric,
> Pend Oreille, Raft River, Salmon River, Snohomish, Umatilla, West
> Oregon).*
>
> 15.1 **Requirements for Meters**
>
> BPA shall access «Customer Name»'s load meter data for purposes of
> forecasting and planning. The following requirements shall apply to
> all meters listed in Exhibit E, Metering.
>
> *End Option 2*
>
> 15.1.1 **BPA Owned Meters**
>
> BPA shall operate, maintain, and replace, as necessary all metering
> equipment owned by BPA that is needed to forecast and plan for
> «Customer Name»'s power needs under this Agreement. «Customer Name»
> authorizes BPA to maintain and replace any BPA owned meter on
> «Customer Name» facilities. With reasonable notice from BPA and for
> the purpose of implementing this provision, «Customer Name» shall
> grant BPA physical access to BPA owned meters at BPA's request.
>
> If, at any time, BPA or «Customer Name» determines that a BPA owned
> meter is defective or inaccurate, BPA shall adjust, repair, or replace
> the meter to provide accurate metering as soon as practical.
>
> 15.1.2 **Non-BPA Owned Meters**
>
> For all non-BPA owned metering equipment owned by «Customer Name» that
> is needed by BPA to forecast and plan for «Customer Name»'s power
> needs under this Agreement «Customer Name» shall give BPA direct,
> electronic access to meter data from all meters not owned by BPA that
> are capable of being accessed electronically. For the purpose of
> inspection, «Customer Name» shall grant BPA reasonable physical access
> to «Customer Name»'s meters at BPA's request.
>
> This section 15.1.2 shall not apply to non-BPA owned meters that are
> owned by a Third-Party Transmission Provider with which BPA holds a
> transmission contract for service to «Customer Name» load. In these
> cases the metering arrangements shall be between BPA and the
> Third-Party Transmission Provider.
>
> «Customer Name» shall operate, maintain, and replace, as necessary at
> «Customer Name» expense, all non-BPA metering equipment owned by
> «Customer Name». For non-BPA owned meters listed in Exhibit E,
> Metering that are not owned by «Customer Name» but are needed by BPA
> to forecast and plan, «Customer Name» shall arrange for such meters to
> be operated, maintained and replaced, as necessary.
>
> If, at any time, BPA or «Customer Name» determines that a non-BPA
> owned meter listed in Exhibit E, Metering is defective or inaccurate,
> «Customer Name» shall adjust, repair, or replace the meter to provide
> accurate metering as soon as practical. BPA shall have the right to
> witness any meter tests conducted by «Customer Name» on non-BPA owned
> meters listed in Exhibit E, Metering and, with reasonable advance
> notice, BPA may conduct tests on such meters. «Customer Name» shall
> have the right to witness any meter tests conducted by BPA.
>
> 15.1.3 **New Meters**
>
> The Parties shall enter into a separate agreement, if such an
> agreement is not already in place, addressing the ownership, location,
> access, maintenance, replacement, testing, and liability of the
> Parties with respect to new and replaced meters. All new meters
> installed by BPA or «Customer Name» shall meet the American National
> Standard Institute standards, including, but not limited to, C12.20,
> Electricity Meters---0.2 and 0.5 Accuracy Classes and the Institute of
> Electrical and Electronics Engineers, Inc. standard C57.13,
> Requirements for Instrument Transformers, or their successors. Any new
> and replaced meters shall be able to record meter data hourly, store
> data for a minimum of 45 days, and be accessed electronically.
>
> 15.2 **Metering an NLSL *(06/13/08 Version)***
>
> «Customer Name» shall meter any loads that are monitored by BPA for an
> NLSL determination and any NLSLs consistent with section 24.3.4,
> Metering an NLSL.
>
> 15.3 **Metering Exhibit**
>
> «Customer Name» shall provide meter data specified in section 17.3,
> Information Exchange and Confidentiality, and shall notify BPA of any
> changes to PODs, POMs, Interchange Points and related information for
> which it is responsible. BPA shall list «Customer Name»'s PODs and
> meters in Exhibit E, Metering.

*END **BLOCK** and **SLICE/BLOCK** templates.*

**16. BILLING AND PAYMENT**

> 16.1 **Billing*(05/14/08* *Version)***
>
> BPA shall bill «Customer Name» monthly for all products and services
> provided during the preceding month(s). BPA may send «Customer Name»
> an estimated bill followed by a final bill. BPA shall send all bills
> on the bill's issue date. If electronic transmittal of the entire bill
> is not practical, BPA shall transmit a summary electronically, and
> send the entire bill by United States mail.
>
> 16.2 **Payment*(03/26/08 Version)***
>
> «Customer Name» shall pay all bills electronically in accordance with
> instructions on the bill. Payment of all bills, whether estimated or
> final, must be received
>
> [(i)]{.mark} [by the 20^th^ day after the issue date of the bill,
> or]{.mark}
>
> []{.mark}
>
> [(ii)]{.mark} [if the 20^th^ day is a Saturday, Sunday, or federal
> holiday, by]{.mark} [the]{.mark} [the next Business Day]{.mark}
>
> []{.mark}
>
> [(Due Date). If «Customer Name» has made payment on an estimated bill
> then:]{.mark}
>
> \(1\) if the amount of the final bill exceeds the amount of the
> estimated bill, «Customer Name» shall pay BPA the difference between
> the estimated bill and final bill by the final bill's Due Date; and
>
> \(2\) if the amount of the final bill is less than the amount of the
> estimated bill, BPA shall pay «Customer Name» the difference between
> the estimated bill and final bill by the [Due Date]{.mark}.
>
> 16.3 **Late Payments*(03/26/08 Version)***
>
> After the Due Date, a late payment charge equal to the higher of:
>
> \(1\) the Prime Rate (as reported in the Wall Street Journal or
> successor publication in the first issue published during the month in
> which payment was due) plus 4 percent, divided by 365; or
>
> \(2\) the Prime Rate times 1.5, divided by 365;
>
> shall be applied each day to any unpaid balance.
>
> 16.4 **Termination*(05/14/08 Version)***
>
> If «Customer Name» has not paid its bill in full by the Due Date, it
> shall have 45 days to cure its nonpayment. If «Customer Name» is more
> than 45 days late in paying its bill, BPA may require additional forms
> of payment assurance acceptable to BPA. If «Customer Name» does not
> provide such payment assurance within three Business Days after
> receipt of written notice from BPA, and BPA determines in its sole
> discretion that «Customer Name» is unable to make the payments owed,
> BPA may terminate this Agreement. Written notices sent under this
> section must comply with section 20, Notices and Contact Information.
>
> 16.5 **Disputed Bills*(05/14/08 Version)***
>
> 16.5.1 If «Customer Name» disputes any portion of a charge or credit
> on «Customer Name»'s bill, «Customer Name» shall provide notice to BPA
> with a copy of the bill noting the disputed amounts. If any portion of
> the bill is in dispute, «Customer Name» shall pay the entire bill by
> the Due Date. Unpaid amounts on a bill (including both disputed and
> undisputed amounts) are subject to the late payment charges provided
> above. Notice of a disputed charge on a bill does not constitute BPA's
> agreement that a valid claim under contract law has been stated.
>
> 16.5.2 If the Parties agree, or if after dispute resolution[,]{.mark}
> «Customer Name» is entitled to a refund of any portion of the disputed
> amount, then BPA shall make such refund with simple interest computed
> from the date of receipt of the disputed payment to the date the
> refund is made. The daily interest rate shall equal the Prime Rate (as
> reported in the Wall Street Journal or successor publication in the
> first issue published during the month in which payment was due)
> divided by 365.

**17. INFORMATION EXCHANGE AND CONFIDENTIALITY**

> 17.1 **General Requirements** ***(03/30/08 Version)***
>
> Each Party shall [upon request]{.mark} provide the other Party with
> any information that is necessary to administer this Agreement, and to
> forecast «Customer Name»'s Total Retail Load, forecast BPA system
> load, comply with NERC reliability standards, prepare bills, resolve
> billing disputes, administer transfer service, and to otherwise
> implement this Agreement. This obligation includes transmission and
> power scheduling information and load and resource metering
> information (such as one-line diagrams, metering diagrams, loss
> factors, etc.). [Such information shall be provided in a timely
> manner.]{.mark}
>
> 17.2 **Reports *(05/14/08 Version)***
>
> 17.2.1 Within 30 days after final approval by the «Customer Name»'s
> governing body [or authorized officer]{.mark}, «Customer Name» shall
> e‑mail its annual financial report and statements to BPA at
> kslf@bpa.gov[;]{.mark} [provided, that such e-mailing shall not be
> required if such annual financial statement is filed with the
> Securities and Exchange Commission and]{.mark} [«Customer Name»
> e-mails to BPA notice of such filing.]{.mark}
>
> 17.2.2 Within 30 days after their submittal to the Energy Information
> Administration (EIA), «Customer Name» shall e‑mail a copy of its
> Annual Form EIA-861 Reports to BPA at kslf@bpa.gov. If «Customer Name»
> is not otherwise required to submit such reports to the EIA, then this
> requirement does not apply.
>
> 17.3 **Meter Data *(06/10/08 Version)***
>
> 17.3.1 In accordance with section 15, Metering, and Exhibit E,
> Metering, «Customer Name» shall notify BPA of any changes to PODs,
> POMs, Interchange Points and related information for which it is
> responsible. «Customer Name» shall ensure BPA has access to all data
> from load and resource meters that BPA determines is necessary to
> forecast, plan, schedule, and bill. Access to this data shall be on a
> schedule determined by BPA. Meter data shall be in hourly increments
> for all meters that record hourly data. Meter data includes, but is
> not limited to: «Customer Name»'s actual amounts of energy used or
> expended for loads and resources, and the physical attributes of
> «Customer Name»'s meters.
>
> 17.3.2 «Customer Name» consents to allow Power Services to receive the
> following information from Transmission Services or BPA's metering
> function: (1) «Customer Name»'s meter data, as specified above in
> section 17.3.1, section 15, Metering, and Exhibit E, Metering, and
> (2) notification of outages or load shifts.
>
> 17.3.3 At least 15 calendar days in advance, «Customer Name» shall
> e‑mail BPA at: (1) mdm@bpa.gov and (2) the contact shown in
> section 20, Notices and Contact Information, when the following events
> are planned to occur on «Customer Name»'s system that will affect
> meters listed in Exhibit E, Metering: (1) installation of a new meter,
> (2) changes or updates to an existing meter not owned by BPA, (3) any
> planned line or meter outages, and (4) any planned load shifts.
>
> 17.3.4 If an unplanned load shift or outage occurs affecting meters
> listed in Exhibit E, Metering, «Customer Name» shall e‑mail BPA at:
> (1) mdm@bpa.gov, and (2) the contact shown in section 20, Notices and
> Contact Information, within 72 hours after the event.
>
> 17.4 **Data for Determining CHWM and CDQs *(03/27/08 Version)***
>
> Upon request, «Customer Name» shall provide to BPA any load and
> resource information that BPA deems necessary to determine «Customer
> Name»'s CHWM and CDQs. This may include historical load data not
> otherwise available to BPA and other data necessary to allow BPA to
> adjust for weather normalization.

*Include in **LOAD FOLLOWING** template:*

> *[Option 1]{.underline}: Only include the following if customer was a
> BLOCK or a SLICE/BLOCK customer during Subscription. See Customer
> Characteristics Spreadsheet. (\*Note: Option 1 is over a page long)*
>
> 17.5 **Hourly Total Retail Load Data *(06/05/08 Version)***
>
> *[Reviewer's Note]{.underline}: The data required below will be used
> by BPA for purposes of determining each customer's Net Requirement.*
>
> BPA shall notify «Customer Name» by June 30, 2009, if BPA determines
> that it does not have adequate hourly meter data to calculate
> «Customer Name»'s Total Retail Load. If BPA sends such notification,
> «Customer Name» shall e-mail the following hourly data to BPA at
> kslf@bpa.gov according to the schedule below. «Customer Name» shall
> submit such data in a comma-separated-value (csv) format with the
> time/date stamp in one column and load amounts, with units of
> measurement specified, in another column.
>
> \(1\) By December 31, 2009, «Customer Name» shall send to BPA
> «Customer Name»\'s actual hourly Total Retail Load data for Fiscal
> Year 2002 through Fiscal Year 2009.
>
> \(2\) By December 31, 2010, «Customer Name» shall send to BPA
> «Customer Name»\'s actual hourly Total Retail Load data for each Point
> of Delivery for Fiscal Year 2010.
>
> 17.6 **Transparency of Net Requirements and Load Forecast Processes
> *(05/27/08 Version)***
>
> 17.6.1 **Transparency for Net Requirements**
>
> By July 31 of each Forecast Year, BPA shall make the following
> information publicly available to «Customer Name» and all other BPA
> regional utility customers with a CHWM:
>
> \(1\) «Customer Name»'s measured Total Retail Load data for the
> previous two Fiscal Years in monthly energy amounts and monthly
> customer-system peak amounts,
>
> \(2\) BPA's forecast of «Customer Name»'s Total Retail Load, for the
> two years of the upcoming Rate Period, in monthly energy amounts and
> monthly customer-system peak amounts, and
>
> \(3\) «Customer Name»'s total Dedicated Resource monthly energy
> amounts and peaking amounts for the two years of the upcoming Rate
> Period as listed in section 5 of Exhibit A, Net Requirements and
> Resources.
>
> 17.6.2 **Transparency for Above-RHWM Load Amounts**
>
> By July 31 of each Forecast Year, BPA shall publish the draft
> Above-RHWM Load amounts that BPA intends to use in the upcoming
> general rate case for each customer with a CHWM
>
> 17.6.3 **Waiver of Confidentiality and Comment Process**
>
> «Customer Name» waives all claims of confidentiality regarding the
> data described above in sections 17.3.1 and 17.3.2. «Customer Name»
> may provide comments regarding the published data to BPA within
> 10 Business Days after notification. After reviewing any comments and
> no later than 60 days from the date BPA originally releases such data,
> BPA shall make available a final set of data and an explanation of any
> changes to «Customer Name» and all other customers with a CHWM.
>
> 17.7 **Confidentiality *(01/17/08 Version)***
>
> Before «Customer Name» provides information that is subject to a
> privilege of confidentiality or nondisclosure to BPA, «Customer Name»
> shall clearly designate such information as confidential. BPA shall
> notify «Customer Name» as soon as practicable of any request received
> under the Freedom of Information Act (FOIA), or under any other
> federal law or court or administrative order, for any confidential
> information. BPA shall only release such confidential information to
> comply with FOIA or if required by any other federal law or court or
> administrative order. BPA shall limit the use and dissemination of
> confidential information within BPA to employees who need it for
> purposes of administering this Agreement.
>
> *End Option 1*
>
> *[Option 2]{.underline}: Include the following if customer purchased a
> product **other than** BLOCK or a SLICE/BLOCK customer during
> Subscription. See Customer Characteristics Spreadsheet. (\*Note:
> Option 2 is about a page long)*
>
> 17.5 **Transparency of Net Requirements and Load Forecast Processes
> *(06/10/08 Version)***
>
> 17.5.1 **Transparency for Net Requirements**
>
> By July 31 of each Forecast Year, BPA shall make the following
> information publicly available to «Customer Name» and all other BPA
> regional utility customers with a CHWM:
>
> \(1\) «Customer Name»'s measured Total Retail Load data for the
> previous two Fiscal Years in monthly energy amounts and monthly
> customer-system peak amounts,
>
> \(2\) BPA's forecast of «Customer Name»'s Total Retail Load, for the
> two years of the upcoming Rate Period, in monthly energy amounts and
> monthly customer-system peak amounts, and
>
> \(3\) «Customer Name»'s total Dedicated Resource monthly energy
> amounts and peaking amounts for the two years of the upcoming Rate
> Period as listed in section 5 of Exhibit A, Net Requirements and
> Resources.
>
> 17.5.2 **Transparency for Above-RHWM Load Amounts**
>
> By July 31 of each Forecast Year, BPA shall publish the draft
> Above-RHWM Load amounts that BPA intends to use in the upcoming
> general rate case for each customer with a CHWM
>
> 17.5.3 **Waiver of Confidentiality and Comment Process**
>
> «Customer Name» waives all claims of confidentiality regarding the
> data described above in sections 17.3.1 and 17.3.2. «Customer Name»
> may provide comments regarding the published data to BPA within
> 10 Business Days after notification. After reviewing any comments and
> no later than 60 days from the date BPA originally releases such data,
> BPA shall make available a final set of data and an explanation of any
> changes to «Customer Name» and all other customers with a CHWM.
>
> 17.6 **Confidentiality *(01/17/08 Version)***
>
> Before «Customer Name» provides information that is subject to a
> privilege of confidentiality or nondisclosure to BPA, «Customer Name»
> shall clearly designate such information as confidential. BPA shall
> notify «Customer Name» as soon as practicable of any request received
> under the Freedom of Information Act (FOIA), or under any other
> federal law or court or administrative order, for any confidential
> information. BPA shall only release such confidential information to
> comply with FOIA or if required by any other federal law or court or
> administrative order. BPA shall limit the use and dissemination of
> confidential information within BPA to employees who need it for
> purposes of administering this Agreement.
>
> *End Option 2*

*END **LOAD FOLLOWING** template.*

*Include in **BLOCK** and **SLICE/BLOCK** templates:*

> 17.5 **Hourly Total Retail Load Data *(06/10/08 Version)***
>
> BPA shall notify «Customer Name» by June 30, 2009, if BPA determines
> that it does not have adequate hourly meter data to calculate
> «Customer Name»'s Total Retail Load. If BPA sends such notification,
> «Customer Name» shall e-mail the following hourly data to BPA at
> kslf@bpa.gov according to the schedule below. «Customer Name» shall
> submit such data in a comma-separated-value (csv) format with the
> time/date stamp in one column and load amounts, with units of
> measurement specified, in another column.
>
> 17.5.1 By December 31, 2009, «Customer Name» shall send to BPA
> «Customer Name»\'s actual hourly Total Retail Load data for Fiscal
> Year 2002 through Fiscal Year 2009.
>
> 17.5.2 By December 31, 2010, «Customer Name» shall send to BPA,
> «Customer Name»\'s actual hourly Total Retail Load data for each for
> Point of Delivery for Fiscal Year 2010.
>
> 17.5.3 By December 31, 2011, and by December 31 of each year
> thereafter, «Customer Name» shall send BPA «Customer Name»\'s actual
> hourly Total Retail Load data for the immediately preceding Fiscal
> Year.
>
> 17.6 **Total Retail Load Forecast *(03/28/08 Version)***
>
> *[Reviewer's Note]{.underline}: The data required below will be used
> by BPA for purposes of calculating Net Requirements and meeting WECC
> data reporting requirements.*
>
> By June 30, 2011, and by June 30 of each year thereafter, «Customer
> Name» shall provide BPA a forecast of «Customer Name»'s monthly energy
> and «Customer Name»'s system coincidental peak of «Customer Name»'s
> Total Retail Load for the upcoming 10 Fiscal Years. «Customer Name»
> shall e‑mail the forecast to BPA at kslf@bpa.gov, in a
> comma-separated-value (csv) format. «Customer Name» shall send the csv
> file with the following data elements in separate columns:
>
> \(1\) four-digit calendar year,
>
> \(2\) three-character month identifier,
>
> \(3\) monthly energy forecast,
>
> \(4\) unit measurement of monthly energy forecast,
>
> \(5\) monthly «Customer Name»-system coincidental peak forecast, and
>
> \(6\) unit measurement of monthly «Customer Name»-system coincidental
> peak forecast.
>
> 17.7 **Transparency of Net Requirements and Load Forecast Processes
> *(05/27/08 Version)***
>
> 17.7.1 **Transparency for Net Requirements**
>
> By July 31, 2011, and by July 31 every year thereafter, BPA shall make
> the following information publicly available to «Customer Name» and
> all other BPA regional utility customers with a CHWM:
>
> \(1\) «Customer Name»'s measured Total Retail Load data for the
> previous Fiscal Year in monthly energy amounts and monthly
> customer-system peak amounts,
>
> \(2\) BPA's forecast of «Customer Name»'s Total Retail Load, for the
> upcoming Fiscal Year, in monthly energy amounts and monthly
> customer-system peak amounts, and
>
> \(3\) «Customer Name»'s total Dedicated Resource monthly energy
> amounts and peaking amounts for the upcoming Fiscal Year listed in
> section 5 of Exhibit A, Net Requirements and Resources.
>
> 17.7.2 **Transparency for Above-RHWM Load Amounts**
>
> By July 31 of each Forecast Year, BPA shall publish the draft
> Above-RHWM Load amounts that BPA intends to use in the upcoming
> general rate case for each customer with a CHWM
>
> 17.7.3 **Waiver of Confidentiality and Comment Process**
>
> «Customer Name» waives all claims of confidentiality regarding the
> data described above in sections 17.3.1 and 17.3.2. «Customer Name»
> may provide comments regarding the published data to BPA within
> 10 Business Days after notification. After reviewing any comments and
> no later than 60 days from the date BPA originally releases such data,
> BPA shall make available a final set of data and an explanation of any
> changes to «Customer Name» and all other customers with a CHWM.
>
> 17.8 **Confidentiality *(01/17/08 Version)***
>
> Before «Customer Name» provides information that is subject to a
> privilege of confidentiality or nondisclosure to BPA, «Customer Name»
> shall clearly designate such information as confidential. BPA shall
> notify «Customer Name» as soon as practicable of any request received
> under the Freedom of Information Act (FOIA), or under any other
> federal law or court or administrative order, for any confidential
> information. BPA shall only release such confidential information to
> comply with FOIA or if required by any other federal law or court or
> administrative order. BPA shall limit the use and dissemination of
> confidential information within BPA to employees who need it for
> purposes of administering this Agreement.

*END **BLOCK** and **SLICE/BLOCK** templates.*

**18. CONSERVATION AND RENEWABLES *(04/05/08 Version)***

> 18.1 **Conservation *(05/14/08 Version)***
>
> 18.1.1 **Evaluations**
>
> At BPA's expense, BPA may conduct, and «Customer Name» shall cooperate
> in, conservation impact and project implementation process evaluations
> to assess the amount, cost-effectiveness, and reliability of
> conservation in BPA's or «Customer Name»'s service area.
>
> BPA shall select the timing, frequency, and type of such evaluations.
> BPA shall do so with reasonable consideration of «Customer Name»'s and
> «Customer Name»'s consumers' needs.
>
> 18.1.2 **Reporting Requirements**
>
> 18.1.2.1 Beginning June 1, 2010, and no later than June 1 every two
> years thereafter, «Customer Name» shall create and submit a 10‑year
> conservation plan stating «Customer Name»'s projection of planned
> conservation, including biennial conservation targets. If «Customer
> Name» is required under state law (such as the Washington State Energy
> Independence Act (RCW 19.285)) to create and submit a conservation
> plan, «Customer Name» may submit to BPA a copy of such plan to meet
> the requirements of this section 18.1.2.1 if it includes, or is
> supplemented by, the information required above. The requirements of
> this section 18.1.2.1 are waived if «Customer Name» purchases all of
> its power from BPA to serve its Total Retail Load.
>
> 18.1.2.2 «Customer Name» shall verify and report all cost-effective
> (as defined by section 3(4) of the Northwest Power Act) non-BPA-funded
> conservation measures and projects savings achieved by «Customer Name»
> through the Regional Technical Forum's Planning, Tracking and
> Reporting System or its successor tool. Verification protocols of
> conservation measures and projects, reporting timelines and
> documentation requirements shall comply with BPA's Energy Efficiency
> Implementation Manual or its successor.
>
> 18.2 **Renewable Resources *(04/05/08 Version)***
>
> 18.2.1 **Renewable Energy Certificates**
>
> BPA shall transfer Renewable Energy Certificates (RECs), or their
> successors, to «Customer Name» in accordance with Exhibit H, Renewable
> Energy Certificates and Carbon Attributes.
>
> 18.2.2 **Reporting Requirements*(06/04/08 Version)***
>
> Beginning September 1, 2012, and by September 1 every year thereafter,
> «Customer Name» shall provide BPA with the following:
>
> \(1\) updated information on power generated by renewable resources
> greater than 200 kilowatts, including net metered renewable resources
> operating behind the BPA meter, used by «Customer Name» to serve its
> Total Retail Load, under Exhibit A, Net Requirements and Resources.
> Such information shall include: project name, fuel type(s), location,
> date contract signed, project energization date, capacity, capacity
> factor, remaining term of purchase (or if direct ownership remaining
> life of the project), and the percentage of output dedicated to serve
> «Customer Name»'s Total Retail Load for the forthcoming calendar year.
>
> \(2\) all purchases of RECs used to meet requirements under state or
> federal law for the forthcoming calendar year. Such information shall
> include: quantity, fuel type(s), location and energization date of the
> RECs producing resource(s), as well as the calendar quarter and the
> year in which the RECs will be generated.
>
> \(3\) an updated long-term renewable resource plan. This shall include
> «Customer Name»'s 2‑year forecast of expected acquisitions of power
> generated by renewable resources greater than 200 kilowatts. Such
> forecast shall disclose the expected amount of such power to be
> purchased, capacity of expected acquisitions by fuel type, and
> percentage of output dedicated to serve «Customer Name»'s Total Retail
> Load.
>
> The three preceding renewable resource requirements are waived if
> «Customer Name» purchases all of its power for service to its Total
> Retail Load from BPA.

**19. RESOURCE ADEQUACY** ***(02/28/08 Version)***

> By November 30, 2010, and by November 30 each year thereafter,
> «Customer Name» shall provide to the Pacific Northwest Utilities
> Conference Committee (PNUCC), or its successor, forecasted loads and
> resources data to facilitate a region-wide assessment of loads and
> resources in a format, length of time, and level of detail specified
> in PNUCC's Northwest Regional Forecast Data Request.
>
> After consultation with the Regional Resource Adequacy Forum, BPA may
> require «Customer Name» to submit additional data to the Northwest
> Power and Conservation Council (Council) that BPA determines is
> necessary for the Council to perform a regional resource adequacy
> assessment.
>
> The requirements of this section are waived if «Customer Name»
> purchases all of its power from BPA to serve its Total Retail Load.

**20. NOTICES AND CONTACT INFORMATION** ***(06/13/08 Version)***

> Any notice required under this Agreement shall be provided in writing
> to the other Party in one of the following ways:
>
> \(1\) delivered in person;
>
> \(2\) by a nationally recognized delivery service with proof of
> receipt;
>
> \(3\) by United States Certified Mail with return receipt requested;
>
> \(4\) electronically, if both Parties have means to verify the
> electronic notice's origin, date, time of transmittal and receipt; or,
>
> \(5\) by another method agreed to by the Parties.
>
> Notices are effective when received. Either Party may change the name
> or address for delivery of notice by providing notice of such change
> or other mutually agreed method. The Parties shall deliver notices to
> the following person and address:
>
> *([Drafter's Note]{.underline}: Check BPA address and phone number
> prefix to ensure it is applicable.)*

+-----------------------------------+-----------------------------------+
| If to «Customer Name»:            | If to BPA:                        |
|                                   |                                   |
| «Utility Name»                    | Bonneville Power Administration   |
|                                   |                                   |
| «Street Address»                  | «Street Address»                  |
|                                   |                                   |
| «P.O. Box »                       | «P.O. Box»                        |
|                                   |                                   |
| «City, State, Zip»                | «City, State, Zip»                |
|                                   |                                   |
| Attn: «Contact Name»              | Attn: «AE Name - Routing»         |
|                                   |                                   |
| «Contact Title»                   | «Senior »Account Executive        |
|                                   |                                   |
| Phone: «###-###-####»             | Phone: «###-###-####»             |
|                                   |                                   |
| FAX: «###-###-####»               | FAX: «###-###-####»               |
|                                   |                                   |
| E-Mail: «E-mail address»          | E-Mail: «E-mail address»          |
+-----------------------------------+-----------------------------------+

**21. UNCONTROLLABLE FORCES *(05/14/08 Version)***

> []{.mark}
>
> 21.1 The Parties shall not be in breach of their respective
> obligations to the extent the failure to fulfill any obligation is due
> to an Uncontrollable Force. "Uncontrollable Force" means an event
> beyond the reasonable control of, and without the fault or negligence
> of, the Party claiming the Uncontrollable Force, that prevents that
> Party from performing its contractual obligations under this Agreement
> and which, by exercise of that Party's reasonable care, diligence and
> foresight, such Party was unable to avoid. Uncontrollable Forces
> include, but are not limited to:
>
> \(1\) any unplanned curtailment or interruption of firm transmission
> service used to deliver Firm Requirements Power sold under this
> Agreement to «Customer Name»;
>
> \(2\) any planned curtailment or interruption of long-term firm
> transmission service used to deliver Firm Requirements Power sold
> under this Agreement to «Customer Name» if such curtailment or
> interruption occurs on BPA\'s or a Third Party Transmission Provider's
> System;
>
> \(3\) any failure of «Customer Name»\'s distribution or transmission
> facilities that prevents «Customer Name» from delivering power to
> end-users;
>
> \(4\) strikes or work stoppage;
>
> \(5\) floods, earthquakes, other natural disasters, or terrorist acts;
> and
>
> \(6\) final orders or injunctions issued by a court or regulatory body
> having competent subject matter jurisdiction which the Party claiming
> the Uncontrollable Force, after diligent efforts, was unable to have
> stayed, suspended, or set aside pending review by a court of competent
> subject matter jurisdiction.
>
> 21.2 Neither the unavailability of funds or financing, nor conditions
> of national or local economies or markets shall be considered an
> Uncontrollable Force. The economic hardship of either Party shall not
> constitute an Uncontrollable Force. Nothing contained in this
> provision shall be construed to require either Party to settle any
> strike or labor dispute in which it may be involved.
>
> 21.3 If an Uncontrollable Force prevents a Party from performing any
> of its obligations under this Agreement, such Party shall:
>
> \(1\) immediately notify the other Party of such Uncontrollable Force
> by any means practicable and confirm such notice in writing as soon as
> reasonably practicable;
>
> \(2\) use its best efforts to mitigate the effects of such
> Uncontrollable Force, remedy its inability to perform, and resume full
> performance of its obligation hereunder as soon as reasonably
> practicable;
>
> \(3\) keep the other Party apprised of such efforts on an ongoing
> basis; and
>
> \(4\) provide written notice of the resumption of performance.
>
> Written notices sent under this section must comply with section 20,
> Notices and Contact Information.

**22. GOVERNING LAW AND DISPUTE RESOLUTION *(05/16/08 Version)***

> This Agreement shall be interpreted consistent with and governed by
> federal law. The Parties shall identify issue(s) in dispute and make a
> good faith effort to negotiate a resolution of disputes before either
> Party may initiate litigation or arbitration. Such good faith effort
> shall include discussions or negotiations between the Parties'
> executives or managers. Pending resolution of a contract dispute or
> contract issue between the Parties or through formal dispute
> resolution of a contract dispute arising out of this Agreement, the
> Parties shall continue performance under this Agreement unless to do
> so would be impossible or impracticable. Unless Parties elect binding
> arbitration, the Parties reserve their rights to seek judicial
> resolution of any dispute arising under this Agreement.
>
> 22.1 **Judicial Resolution**
>
> Final actions subject to section 9(e) of the Northwest Power Act are
> not subject to arbitration under this Agreement and shall remain
> within the exclusive jurisdiction of the United States Ninth Circuit
> Court of Appeals. Such final actions include, but are not limited to,
> the establishment and implementation of rates and rate methodologies.
> Any dispute regarding any rights of the Parties under any BPA policy,
> including the implementation of such policy, shall not be subject to
> arbitration under this Agreement. For purposes of this section 22,
> Governing Law and Dispute Resolution, BPA policy means any written
> document adopted by BPA as a final action in a record of decision that
> establishes a policy of general application or makes a determination
> [of general application]{.mark} under an applicable statute. If either
> Party asserts that a dispute is excluded from arbitration under this
> section 22, Governing Law and Dispute Resolution then both Parties
> shall apply to the federal court having jurisdiction for an order
> determining whether such dispute is subject to arbitration under this
> section 22, Governing Law and Dispute Resolution.
>
> 22.2 **Arbitration**
>
> Any contract dispute or contract issue between the Parties arising out
> of this Agreement, which is not excluded by section 22.1 above, shall
> be subject to arbitration, as set forth below.
>
> The Parties may agree to use binding arbitration, consistent with
> BPA's Binding Arbitration Policy or its successor, to resolve disputes
> that the Parties agree are strictly issues of fact and that fall
> within BPA's Binding Arbitration Policy or its successor. Before
> initiating binding arbitration, the Parties shall draft and sign an
> agreement to engage in binding arbitration, which shall set forth the
> precise issue in dispute, the amount in controversy, and the maximum
> monetary award allowed, pursuant to BPA's Binding Arbitration Policy
> or its successor.
>
> [The]{.mark} [Parties may agree to use]{.mark} [n]{.mark}onbinding
> arbitration to resolve any dispute that is not excluded by
> [section]{.mark} [22]{.mark}.1 above, and is not resolved via binding
> arbitration. [Before initiating nonbinding arbitration, the Parties
> shall draft and sign an agreement to engage in nonbinding arbitration,
> which shall set forth the precise issue in dispute.]{.mark}
>
> [Any dispute between the Parties arising out of this Agreement that is
> not excluded by section 22.1 above and that is not resolved pursuant
> to the preceding provisions of this section 22.2 shall be subject to
> resolution between the Parties in any forum with jurisdiction to
> resolve such dispute.]{.mark}
>
> 22.3 **Arbitration Procedure**
>
> Any arbitration shall take place in Portland, Oregon, unless the
> Parties agree otherwise. The Parties agree that a fundamental purpose
> for arbitration is the expedient resolution of disputes; therefore,
> the Parties shall make best efforts to resolve an arbitrable dispute
> within one year of initiating arbitration. The rules for arbitration
> shall be agreed to by the Parties.
>
> 22.4 **Arbitration Remedies**
>
> The payment of monies shall be the exclusive remedy available in any
> arbitration proceeding. Under no circumstances shall specific
> performance be an available remedy against BPA.
>
> 22.5 **Finality**
>
> 22.5.1 In binding arbitration, the arbitration award shall be final
> and binding on both Parties, except that either Party may seek
> judicial review based upon any of the grounds referred to in the
> Federal Arbitration Act, 9 U.S.C. §1-16 (1988). Judgment upon the
> award rendered by the arbitrator[(s)]{.mark} may be entered by any
> court having jurisdiction thereof.
>
> 22.5.2 In nonbinding arbitration, the arbitration award is not binding
> on the Parties. Subsequent to nonbinding arbitration, if a Party other
> than BPA rejects the arbitration award or if BPA rejects the
> arbitration award, the Party may seek judicial resolution of the
> dispute.
>
> 22.6 **Arbitration Costs**
>
> Each Party shall be responsible for its own costs of arbitration,
> including legal fees. The arbitrator(s) may apportion all other costs
> of arbitration between the Parties in such manner as the arbitrator(s)
> deem reasonable taking into account the circumstances of the case, the
> conduct of the Parties during the proceeding, and the result of the
> arbitration.

**23. NO WARRANTY *(03/26/08 Version)***

> Nothing in this Agreement, or any dispute arising out of this
> Agreement, shall limit the Administrator's responsibility to establish
> rates to recover costs and timely repay the U.S. Treasury or to take
> actions that are effectively required by a court order. It is the
> Parties' intent to structure a durable commercial relationship that is
> based on existing statutory requirements and to provide «Customer
> Name» with protection against change to those guiding statutes as is
> reasonably possible. However, BPA does not warrant or represent that
> this Agreement is immune from costs imposed by court order or agency
> regulations of a general and public nature or is immune from
> subsequently enacted legislation.

**24. STATUTORY PROVISIONS**

> 24.1 **Retail Rate Schedules *(09/04/07 Version)***
>
> «Customer Name» shall make its retail rate schedules available to BPA,
> as required by section 5(a) of the Bonneville Project Act,
> P.L. 75‑329, within 30 days of each of «Customer Name»'s retail rate
> schedule effective dates. [This requirement may be satisfied
> by]{.mark} [«Customer Name»'s]{.mark} [posting on its public website
> of its retail rate schedules.]{.mark}
>
> 24.2 **Insufficiency and Allocations *(04/04/08 Version)***
>
> If BPA determines, consistent with section 5(b) of the Northwest Power
> Act and other applicable statutes, that it will not have sufficient
> resources on a planning basis to serve its loads after taking all
> actions required by applicable laws then BPA shall give «Customer
> Name» a written notice that BPA may restrict service to «Customer
> Name». Such notice shall be consistent with BPA's insufficiency and
> allocations methodology, published in the Federal Register on
> March 20, 1996, and shall state the effective date of the restriction,
> the amount of «Customer Name»'s load to be restricted and the expected
> duration of the restriction. BPA shall not change that methodology
> without the written agreement of all public body, cooperative, federal
> agency and investor-owned utility customers in the Region purchasing
> federal power from BPA under section 5(b) of the Northwest Power Act.
> Such restriction shall take effect no sooner than five years after BPA
> provides notice to «Customer Name». If BPA imposes a restriction under
> this provision then the amount of Firm Requirements Power that
> «Customer Name» is obligated to purchase pursuant to section 3 and
> Exhibit C of this Agreement shall be reduced to the amounts available
> under such allocation methodology for restricted service.
>
> 24.3 **New Large Single Loads and CF/CTs** [\[\[Comment:]{.mark}
> [Utilities should be able to dedicate resources to NLSLs under RPSAs
> in the same manner as utilities may do so in section 5(b) contracts
> for the purchase of net requirements power.\]\]]{.mark}
>
> 24.3.1 **Determination of an NLSL *(05/15/08 Version)***

In accordance with BPA's NLSL Policy, BPA may determine that a load is
an NLSL as follows:

> 24.3.1.1 BPA shall determine an increase in production load to be an
> NLSL if [it is a]{.mark} load associated with a new facility, an
> existing facility, or an expansion of an existing facility, which is
> not contracted for, or committed to, as determined by the
> Administrator, by a public body, cooperative, investor-owned utility,
> or federal agency customer prior to September 1, 1979, and which will
> result in an increase in power requirements of such customer of ten
> average megawatts (87,600,000 kilowatt hours) or more in any
> consecutive twelve-month period..
>
> 24.3.1.2 For the sole purpose of computing the increase in energy
> consumption between any two consecutive 12‑month periods of comparison
> under this section 24.3.1, reductions in the end-use consumer's load
> associated with a facility during the first twelve-month period of
> comparison due to unusual events reasonably beyond the control of the
> end-use consumer shall be determined by BPA, and the energy
> consumption shall be computed as if such reductions had not occurred.
>
> 24.3.1.3 The Parties may agree that the installed production equipment
> at a facility will exceed 10 average megawatts consumption over any
> 12 consecutive months and such agreement shall constitute a binding
> NLSL determination.
>
> 24.3.2 **Determination of a Facility *(09/04/07 Version)***
>
> BPA shall make a written determination as to what constitutes a single
> facility, for the purpose of identifying an NLSL, based on the
> following criteria:
>
> \(1\) whether the load is operated by a single end-use consumer;
>
> \(2\) whether the load is in a single location;
>
> \(3\) whether the load serves a manufacturing process which produces a
> single product or type of product;
>
> \(4\) whether separable portions of the load are interdependent;
>
> \(5\) whether the load is contracted for, served or billed as a single
> load under «Customer Name»'s customary billing and service policy;
>
> \(6\) consideration of the facts from previous similar situations; and
>
> \(7\) any other factors the Parties determine to be relevant.
>
> 24.3.3 **Administrative Obligations and Rights *(4/06/08 Version)***
>
> 24.3.3.1 «Customer Name»'s CF/CT loads and NLSLs are listed in
> Exhibit D, Additional Products and Special Provisions.
>
> 24.3.3.2 «Customer Name» shall provide reasonable notice to BPA of any
> expected increase in a single load that may qualify as an NLSL. The
> Parties shall list any such potential NLSLs in Exhibit D, Additional
> Products and Special Provisions. If BPA determines that any load
> associated with a single facility that is capable of growing
> 10 average megawatts or more in a consecutive 12‑month period, then
> such load shall be subject to monitoring by BPA.
>
> 24.3.3.3 When BPA makes a request, «Customer Name» shall provide
> physical access to its substations and other service locations where
> BPA needs to perform inspections or gather information for purposes of
> implementing section 3(13) of the Northwest Power Act, including but
> not limited to making a final NLSL, facility, or CF/CT determination.
> «Customer Name» shall also require the end-use consumer to provide BPA
> physical access to inspect any facility for these purposes.
>
> 24.3.3.4 Unless the Parties agree pursuant to section 24.3.1.3 above,
> BPA shall unilaterally determine whether a new load or an increase in
> existing load at a facility is an NLSL. If BPA determines that the
> load is an NLSL, BPA shall notify «Customer Name» and the Parties
> shall add the NLSL to Exhibit D, Additional Products and Special
> Provisions.
>
> 24.3.4 **Metering an NLSL *(03/30/08 Version)***
>
> For any loads that are monitored by BPA for an NLSL determination, and
> at any facility that is determined by BPA to be an NLSL, «Customer
> Name» agrees to either consent to BPA installing BPA owned meters or
> «Customer Name» shall install meters meeting the exact specification
> BPA provides to «Customer Name». «Customer Name» and BPA shall enter
> into a separate agreement for the location, ownership, cost
> responsibility, access, maintenance, testing, replacement and
> liability of the Parties with respect to such meters. «Customer Name»
> shall arrange for metering locations that allow accurate measurement
> of the facility's load. «Customer Name» shall arrange for BPA to have
> physical access to such meters and «Customer Name» shall ensure BPA
> has access to all NLSL meter data that BPA determines is necessary to
> forecast, plan, schedule, and bill for power.
>
> 24.3.5 **Undetermined NLSLs*(04/06/08 Version)***
>
> If BPA does not determine at the outset that an increase in load is an
> NLSL, then the Parties shall install metering equipment as required by
> section 24.3.4, above, and BPA shall bill «Customer Name» for the
> increase in load at the applicable PF Rate during any consecutive
> twelve-month monitoring period. If BPA later determines that the
> increase in load is an NLSL, then BPA shall revise «Customer Name»'s
> bill to reflect the difference between the applicable PF rate and the
> applicable NR rate in effect for the monitoring period in which the
> increase takes place. «Customer Name» shall pay that bill with simple
> interest computed from the start of the monitoring period to the date
> the payment is made. The daily interest rate shall equal the Prime
> Rate (as reported in the Wall Street Journal or successor publication
> in the first issue published during the month in which the monitoring
> period began) divided by 365.
>
> If BPA concludes in its sole judgment that «Customer Name» has not
> fulfilled its obligations under sections 24.3.3 and 24.3.4, BPA may
> determine any load subject to NLSL monitoring to be an NLSL. Such NLSL
> determination shall be final unless «Customer Name» proves to BPA's
> satisfaction that the applicable load did not exceed 10 aMW in any
> 12‑month monitoring period.

*Include in **LOAD FOLLOWING** template.*

> 24.3.6 **Service Election for an NLSL** ***(02/28/08 Version)***
>
> Before the Parties add an NLSL to Exhibit D, Additional Products and
> Special Provisions, «Customer Name» shall elect, in writing, to:
>
> \(1\) have BPA serve the NLSL at the NR rate; or
>
> \(2\) serve the NLSL with a Dedicated Resource in Exhibit A, Net
> Requirements and Resources, that is not already dedicated to serve
> «Customer Name»'s firm consumer load in the region*.*
>
> This election shall be binding on «Customer Name» for the remaining
> term of this Agreement.

*END **LOAD FOLLOWING** template.*

*Include in **BLOCK** and **SLICE/BLOCK** templates.*

> 24.3.6 **Service Elections for an NLSL *(02/28/08 Version)***
>
> «Customer Name» shall serve all NLSLs with non-federal firm resources
> that are not Dedicated Resources in Exhibit A, Net Requirements and
> Resource, Exhibit D, Additional Products and Special Provisions, to
> serve «Customer Name»'s Total Retail Load in the region. «Customer
> Name» agrees to provide such Dedicated Resources on a continuous basis
> as identified in Exhibit A, Net Requirements and Resources. Under no
> circumstances shall BPA be required to acquire firm power for service
> to such NLSLs.

*END **BLOCK** and **SLICE/BLOCK** templates.*

> 24.3.7 **Renewable Resource/Cogeneration Exception *(04/06/08
> Version)***
>
> An end-use consumer served by «Customer Name», with a facility whose
> load is, in whole or in part, an NLSL, may reduce its NLSL to less
> than 10 average megawatts by applying an onsite renewable resource or
> onsite cogeneration behind «Customer Name»'s meter to its facility
> load. «Customer Name» shall ensure that such resource is continuously
> applied to serve the NLSL, consistent with BPA's "Renewables and
> On-Site Cogeneration Option under the NLSL Policy" portion of its
> Policy for Power Supply Role for Fiscal Years 2007-2011, adopted
> February 4, 2005, and the NLSL policy included in BPA's Long Term
> Regional Dialogue Final Policy, July 2007, as amended or replaced. If
> the NLSL end-use consumer meets the qualification for the exception,
> the Parties shall: (1) list the Consumer-Owned Resource(s) serving the
> NLSL in section 7.3 of Exhibit A, Net Requirements and Resources and
> (2) amend Exhibit D, Additional Products and Special Provisions to add
> the onsite renewable resource or cogeneration facility and the
> requirements for such service.
>
> If «Customer Name» serves an NLSL with a Consumer-Owned Resource that
> does not qualify for the renewable resource or cogeneration exception,
> the Parties shall list such Consumer-Owned Resource serving the NLSL
> in section 7.3 of Exhibit A, Net Requirements and Resources.
>
> 24.4 **Priority of Pacific Northwest Customers *(09/04/07 Version)***
>
> The provisions of sections 9(c) and 9(d) of the Northwest Power Act
> and the provisions of P.L. 88‑552 as amended by the Northwest Power
> Act are incorporated into this Agreement by reference. «Customer
> Name», together with other customers in the Region, shall have
> priority to BPA power consistent with such provisions.
>
> 24.5 **Prohibition on Resale *(09/04/07 Version)***
>
> «Customer Name» shall not resell Firm Requirements Power except to
> serve «Customer Name»'s Total Retail Load or as otherwise permitted by
> federal law.
>
> 24.6 **Use of Regional Resources *(05/15/08 Version)***
>
> 24.6.1 Within 60 days prior to the start of each Fiscal Year,
> «Customer Name» shall provide notice to BPA of any Firm Power from a
> Generating Resource, or a Contract Resource during its term, that has
> been used to serve firm consumer load in the Region and that «Customer
> Name» plans to export for sale outside the Region in the next Fiscal
> Year. For purposes of this section 24.6, "Firm Power" means electric
> power which is continuously made available from «Customer Name»'s
> operation of generation or from its purchased power, which is able to
> meet its Total Retail Load, except when such generation or power is
> curtailed or restricted due to an Uncontrollable Force. Firm Power
> includes firm energy and firm peaking energy or both.
>
> BPA may request additional information on «Customer Name»'s sales and
> dispositions of non-federal resources if BPA has information that
> «Customer Name» may have made such an export and not notified BPA. BPA
> may request and «Customer Name» shall provide within 30 days of such
> request, information on the planned use of any or all of «Customer
> Name» Generating and Contract Resources.
>
> [« Customer Name» shall have no obligation to notify]{.mark}
> [BPA]{.mark} [under this subsection 24.6 if and for so long as the
> Firm Power amounts as established]{.mark} [under]{.mark} [section 3.1
> above are equal to zero.]{.mark}
>
> 24.6.2 «Customer Name» shall be responsible for monitoring any Firm
> Power from Generating Resources and Contract Resources it sells in the
> Region to ensure such Firm Power is planned to be used to serve firm
> consumer load in the Region.
>
> 24.6.3 If «Customer Name» fails to report to BPA in accordance with
> section 24.6.1, above, any of its planned exports for sale outside the
> Region of Firm Power from a Generating Resource or a Contract Resource
> that has been used to serve firm consumer load in the Region, and BPA
> makes a finding that an export which was not reported was made, BPA
> shall decrement the amount of its Firm Requirements Power sold under
> this Agreement by the amount of the export that was not reported, for
> the duration of the export. When applicable such decrements shall be
> identified in section 3.2 of Exhibit A, Net Requirements and
> Resources.
>
> 24.6.4 For purposes of this section, an export for sale outside the
> Region means a contract for the sale or disposition of Firm Power from
> a Generating Resource, or a Contract Resource during its term, that
> has been used to serve firm consumer load in the Region in a manner
> that such output is no longer used or not planned to be used solely to
> serve firm consumer load in the Region. Delivery of Firm Power outside
> the Region under a seasonal exchange agreement that is made consistent
> with BPA's section 9(c) policy will not be considered an export. Firm
> Power from a Generating Resource or a Contract Resource used to serve
> firm consumer load in the Region means the firm generating or load
> carrying capability of a Generating Resource or a Contract Resource as
> established under Pacific Northwest Coordination Agreement resource
> planning criteria, or other resource planning criteria generally used
> for such purposes within the Region.
>
> 24.7 **BPA Appropriations Refinancing** ***(05/14/08 Version)***
>
> The Parties agree that the Bonneville Power Administration Refinancing
> section of the Omnibus Consolidated Rescissions and Appropriations Act
> of 1996 (BPA Refinancing Act), P.L. 104‑134, 110 Stat. 1321, 350, as
> stated in the United States Code on the date this Agreement is signed
> by the Parties, is incorporated by reference and is a material term of
> this Agreement.

**25. STANDARD PROVISIONS**

> 25.1 **Amendments *(09/04/07 Version)***
>
> Except where this Agreement explicitly allows for one Party to
> unilaterally amend a provision or exhibit, no amendment of this
> Agreement shall be of any force or effect unless set forth in a
> written instrument signed by authorized representatives of each Party.
>
> 25.2 **Entire Agreement and Order of Precedence *(09/26/07 Version)***
>
> This Agreement, including documents expressly incorporated by
> reference, constitutes the entire agreement between the Parties [with
> respect to the subject matter of this Agreement.]{.mark} It supersedes
> all previous communications, representations, or contracts, either
> written or oral, which purport to describe or embody the subject
> matter of this Agreement. The body of this Agreement shall prevail
> over the exhibits to this Agreement in the event of a conflict.
>
> 25.3 **Assignment *(03/28/08 Version)***
>
> This Agreement is binding on any successors and assigns of the
> Parties. Neither Party may otherwise transfer or assign this
> Agreement, in whole or in part, without the other Party's written
> consent. Such consent shall not be unreasonably withheld. Without
> limiting the foregoing, BPA's refusal to consent to assignment shall
> not be considered unreasonable if, in BPA's sole discretion: (1) the
> sale of power by BPA to the assignee would violate any applicable
> statute, or (2) such sale might adversely affect the tax-exempt status
> of bonds issued as part of an issue that finances or refinances the
> Columbia Generating Station or that such sale might limit the ability
> to issue future tax-exempt bonds to finance or refinance the Columbia
> Generating Station. «Customer Name» may not transfer or assign this
> Agreement to any of its retail consumers.
>
> 25.4 **No Third‑Party Beneficiaries *(10/01/07 Version)***
>
> This Agreement is made and entered into for the sole benefit of the
> Parties, and the Parties intend that no other person or entity shall
> be a direct or indirect beneficiary of this Agreement.
>
> 25.5 **Waivers *(10/01/07 Version)***
>
> No waiver of any provision or breach of this Agreement shall be
> effective unless such waiver is in writing and signed by the waiving
> Party, and any such waiver shall not be deemed a waiver of any other
> provision of this Agreement or any other breach of this Agreement.
>
> 25.6 **BPA Policies *(09/04/07 Version)***
>
> Any reference in this Agreement to BPA policies, including any
> revisions, does not constitute agreement of «Customer Name» to
> [any]{.mark} such policy [(or revision)]{.mark} by execution of this
> Agreement, nor shall [any such reference or execution]{.mark} be
> construed to be a waiver of the right of «Customer Name» to seek
> judicial review of any such policy [(or revision)]{.mark}.
>
> 25.7 **Rate Covenant and Payment Assurance *(03/28/08 Version)***
>
> «Customer Name» agrees that it shall establish, maintain and collect
> rates or charges for power and energy and other services, facilities
> and commodities sold, furnished or supplied by it through any of its
> electric utility properties. BPA may require additional forms of
> payment assurance if: (1) BPA determines that such rates and charges
> may not be adequate to provide revenues sufficient to enable «Customer
> Name» to make the payments required under this Agreement, or (2) BPA
> identifies in a letter to «Customer Name» that BPA has other
> reasonable grounds to conclude that «Customer Name» may not be able to
> make the payments required under this Agreement. If «Customer Name»
> does not provide payment assurance satisfactory to BPA, BPA may
> terminate this Agreement.
>
> *([Option]{.underline}: Include this section ONLY for cooperatives.)*
>
> 25.8 **Bond Assurances** ***(03/28/08 Version)***
>
> BPA has advised «Customer Name» that: (1) the Columbia Generating
> Station has been financed and refinanced in large part by bonds that
> are intended to bear interest that is exempt from Federal income tax
> under Section 103 of the Internal Revenue Code of 1954, as amended,
> and Title XIII of the Tax Reform Act of 1986, and (2) the tax-exempt
> status of those bonds and other bonds issued together with those bonds
> might be jeopardized if «Customer Name» or any other nongovernmental
> person has a contract to purchase additional amounts of the output of
> the Columbia Generating Station.
>
> Consequently, «Customer Name» shall notify BPA at least 90 days before
> «Customer Name» acquires an Annexed Load, or «Customer Name» is
> acquired, in whole or in part, as an Annexed Load. «Customer Name»
> hereby acknowledges and agrees that BPA shall have the right to reduce
> «Customer Name»'s CHWM in connection with any such Annexed Load to the
> extent the aggregate CHWM, including the Annexed Load, (or the
> aggregate CHWM, including the Annexed Load, of related entities)
> otherwise would result in a nongovernmental customer with a CHWM share
> of the Tier 1 System Resources that exceeds 2.8 percent.
>
> *End Option 25.8*
>
> [25.9]{.mark} **[Severability]{.mark}** [If any term of this Agreement
> is found to be invalid by a court of competent jurisdiction, then such
> term shall remain in force to the maximum extent permitted by law. All
> other terms of this Agreement shall remain in force except if and to
> the extent determined not to be severable from all other provisions of
> this Agreement by such court.]{.mark}

**26. TERMINATION *(07/02/08 Version)***

> 26.1 **BPA's Right to Terminate**
>
> BPA may terminate this Agreement if:
>
> \(1\) «Customer Name» fails to make payment as required by
> section 16.4, Billing and Payment, or
>
> \(2\) «Customer Name» fails to provide payment assurance satisfactory
> to BPA as required by section 25.7, Rate Covenant and Payment
> Assurance.
>
> 26.2 **Customer's Right to Terminate*(07/2/08 Version)***
>
> «Customer Name» may provide written notice to terminate this Agreement
> not later than 60 days after a Final FERC Order is issued declining to
> approve the Tiered Rates Methodology if such approval is required, or
> a Final FERC Order disapproves rates established consistent with the
> TRM. The notice shall include a date of termination not later than
> 90 days after the date of such notice. For purposes of this
> section 26.3, "Final FERC Order" means a dispositive order by FERC on
> the merits, and does not include any interim order. A dispositive
> order on the merits is, for purposes of this section, final when
> issued and there is no need to await a FERC order on rehearing before
> the decision is considered final.

**27. SIGNATURES *(10/01/07 Version)***

> The signatories represent that they are authorized to enter into this
> Agreement on behalf of the Party for which they sign.

+------------------------------------+---------------------------------+
| «FULL NAME OF CUSTOMER»            | UNITED STATES OF AMERICA        |
|                                    |                                 |
|                                    | Department of Energy            |
|                                    |                                 |
|                                    | Bonneville Power Administration |
+------------------------------------+---------------------------------+

  ------- -------------------------- -- ------- ----------------------------
  By                                    By      

                                                

  Name                                  Name    

          *(Print/Type)*                        *(Print/Type)*

  Title                                 Title   

                                                

  Date                                  Date    
  ------- -------------------------- -- ------- ----------------------------

(PS«X/LOC»- «File Name with Path».DOC) «mm/dd/yy» *{[Drafter's
Note]{.underline}: Insert date of finalized contract here}*

**Exhibit A**

**NET REQUIREMENTS AND RESOURCES**

*Include in **LOAD FOLLOWING** template:*

**1.** **NET REQUIREMENTS**

> «Customer Name»'s Net Requirement equals its Total Retail Load minus
> «Customer Name»'s Dedicated Resource amounts listed in sections 2, 3,
> and 4 of this exhibit. «Customer Name» shall not add resource amounts
> to reduce its purchase obligations from BPA under section 3.1 of the
> body of this Agreement except to meet obligations in section 3.5 of
> the body of this Agreement.

*END **LOAD FOLLOWING** templates.*

*Include in **BLOCK** and **SLICE/BLOCK** template:*

**1.** **NET REQUIREMENTS**

> «Customer Name»'s Net Requirement equals its Total Retail Load minus
> «Customer Name»'s Dedicated Resource amounts listed in sections 2, 3,
> and 4 of this exhibit. «Customer Name» shall not add resource amounts
> to reduce its purchase obligations from BPA under section 3.1 of the
> body of this Agreement except to meet obligations in section 3.5 of
> the body of this Agreement.
>
> BPA shall annually calculate a forecast of «Customer Name»'s Net
> Requirement for the upcoming Fiscal Year as follows:
>
> *[Option 1]{.underline}: Include if SLICE/BLOCK or BLOCK customer does
> [NOT]{.underline} take Shaping Capacity.*
>
> 1.1 **Forecast of Total Retail Load**
>
> By September 15, 2011, and by each September 15 thereafter, BPA shall
> fill in the table below with «Customer Name»'s Total Retail Load
> forecast (submitted pursuant to section 17.6 of the body of this
> Agreement) for the upcoming Fiscal Year. BPA shall notify «Customer
> Name» by July 31 immediately preceding the start of the Fiscal Year if
> BPA determines «Customer Name»'s submitted forecast is reasonable or
> not reasonable. If BPA determines «Customer Name»'s submitted forecast
> is not reasonable, BPA shall fill in the table below with a forecast
> BPA determines to be reasonable by September 15 immediately preceding
> the start of the Fiscal Year.
>
> *[Drafter's Note]{.underline}*: The table below will be blank at
> contract signing.

  --------------- ------ ------ ------ ------ ------ ------ ------ ------ ------
  **Annual                                                                
  Forecast of                                                             
  Total Retail                                                            
  Load -- Energy                                                          
  (aMW)**                                                                 

  **Fiscal Year** 2012   2013   2014   2015   2016   2017   2018   2019   2020

  **Annual aMW**                                                          

  **Fiscal Year** 2021   2022   2023   2024   2025   2026   2027   2028   

  **Annual aMW**                                                          

  Note: Fill in                                                           
  the table above                                                         
  with annual                                                             
  average                                                                 
  megawatts                                                               
  rounded to                                                              
  three decimal                                                           
  places.                                                                 
  --------------- ------ ------ ------ ------ ------ ------ ------ ------ ------

> 1.2 **Forecast of Net Requirements**
>
> By September 15, 2011, and by each September 15 thereafter, BPA shall
> calculate, and fill in the table below with, «Customer Name»'s Net
> Requirement forecast for the upcoming Fiscal Year. «Customer Name»'s
> Net Requirement forecast equals «Customer Name»'s Total Retail Load
> forecast, shown in section 1.1 above, minus «Customer Name»'s total
> Dedicated Resource Amounts, shown in section 5 below.
>
> Consistent with section 3 of the body of this Agreement, «Customer
> Name» shall dedicate additional resource energy amounts to serve any
> «Customer Name» energy needs above «Customer Name»'s RHWM and any PF
> Tier 2 rate amounts listed in section 2.5 of Exhibit C, Purchase
> Obligations. «Customer Name» shall also serve any «Customer Name» peak
> load above the sum of «Customer Name»'s monthly purchase amounts at
> Tier 1 rates in section 1.3 of Exhibit C, Purchase Obligations, and
> any purchase amounts at Tier 2 rates in section 2.5 of Exhibit C,
> Purchase Obligations, with additional resource peak amounts.
>
> *[Drafter's Note]{.underline}*: The table below will be blank at
> contract signing.

  --------------- ------ ------ ------ ------ ------ ------ ------ ------ ------
  **Annual                                                                
  Forecast of Net                                                         
  Requirements --                                                         
  Energy (aMW)**                                                          

  **Fiscal Year** 2012   2013   2014   2015   2016   2017   2018   2019   2020

  **Annual aMW**                                                          

  **Fiscal Year** 2021   2022   2023   2024   2025   2026   2027   2028   

  **Annual aMW**                                                          

  Note: Fill in                                                           
  the table above                                                         
  with annual                                                             
  average                                                                 
  megawatts                                                               
  rounded to                                                              
  three decimal                                                           
  places.                                                                 
  --------------- ------ ------ ------ ------ ------ ------ ------ ------ ------

> *End Option 1*
>
> *Option 2: Include if BLOCK customer takes Shaping Capacity.*
>
> *[Reviewer's Note]{.underline}: Only the shaded language and the
> monthly peak tables differ from Option 1.*
>
> 1.1 **Forecast of Total Retail Load**
>
> By September 15, 2011, and by each September 15 thereafter, BPA shall
> fill in the tables below with «Customer Name»'s Total Retail Load
> forecast (submitted pursuant to section 17.6 of the body of this
> Agreement) for the upcoming Fiscal Year. BPA shall notify «Customer
> Name» by July 31 immediately preceding the start of the Fiscal Year if
> BPA determines «Customer Name»'s submitted forecast is reasonable or
> not reasonable. If BPA determines «Customer Name»'s submitted forecast
> is not reasonable, BPA will fill in the tables below with a forecast
> BPA determines to be reasonable by September 15 immediately preceding
> the start of the Fiscal Year.
>
> *[Drafter's Note]{.underline}: The table below will be blank at
> contract signing.*

  ------------------------------------------------------------------------------
  **Annual                                                                
  Forecast of                                                             
  Total Retail                                                            
  Load -- Energy                                                          
  (aMW)**                                                                 
  --------------- ------ ------ ------ ------ ------ ------ ------ ------ ------
  **Fiscal Year** 2012   2013   2014   2015   2016   2017   2018   2019   2020

  **Annual aMW**                                                          

  **Fiscal Year** 2021   2022   2023   2024   2025   2026   2027   2028   

  **Annual aMW**                                                          

  Note: Fill in                                                           
  the table above                                                         
  with annual                                                             
  average                                                                 
  megawatts                                                               
  rounded to                                                              
  three decimal                                                           
  places.                                                                 
  ------------------------------------------------------------------------------

> *[Drafter's Note]{.underline}: The table below will be blank at
> contract signing.*

  -----------------------------------------------------------------------------------------------------------------------------------
  **Annual                                                                                                                  
  Forecast of                                                                                                               
  Total                                                                                                                     
  Retail Load                                                                                                               
  -- Peak                                                                                                                   
  (MW)**                                                                                                                    
  ----------- --------- --------- --------- --------- --------- --------- --------- --------- --------- --------- --------- ---------
  **Fiscal    **Oct**   **Nov**   **Dec**   **Jan**   **Feb**   **Mar**   **Apr**   **May**   **Jun**   **Jul**   **Aug**   **Sep**
  Year**                                                                                                                    

  2012                                                                                                                      

  2013                                                                                                                      

  2014                                                                                                                      

  2015                                                                                                                      

  2016                                                                                                                      

  2017                                                                                                                      

  2018                                                                                                                      

  2019                                                                                                                      

  2020                                                                                                                      

  2021                                                                                                                      

  2022                                                                                                                      

  2023                                                                                                                      

  2024                                                                                                                      

  2025                                                                                                                      

  2026                                                                                                                      

  2027                                                                                                                      

  2028                                                                                                                      

  Note: Fill                                                                                                                
  in the                                                                                                                    
  table above                                                                                                               
  with                                                                                                                      
  megawatts                                                                                                                 
  rounded to                                                                                                                
  whole                                                                                                                     
  megawatt                                                                                                                  
  amounts.                                                                                                                  
  -----------------------------------------------------------------------------------------------------------------------------------

> 1.2 **Forecast of Net Requirements**
>
> By September 15, 2011, and by each September 15 thereafter, BPA shall
> calculate, and fill in the tables below with, «Customer Name»'s Net
> Requirement forecast for the upcoming Fiscal Year. «Customer Name»'s
> Net Requirement forecast equals «Customer Name»'s Total Retail Load
> forecast, shown in section 1.1 above, minus «Customer Name»'s total
> Dedicated Resource Amounts, shown in section 5 below.
>
> Consistent with section 3 of the body of this Agreement, «Customer
> Name» shall dedicate additional resource energy amounts to serve any
> «Customer Name» energy needs above «Customer Name»'s RHWM and any PF
> Tier 2 rate amounts listed in section 2.5 of Exhibit C, Purchase
> Obligations. «Customer Name» shall also serve any «Customer Name» peak
> load above the sum of «Customer Name»'s monthly purchase amounts at
> Tier 1 rates in section 1.3 of Exhibit C, Purchase Obligations, any
> purchase amounts at Tier 2 rates in section 2.5 of Exhibit C, Purchase
> Obligations, and any Shaping Capacity amounts in section 1.4.1 of
> Exhibit C, Purchase Obligations, with additional resource peak
> amounts.
>
> *[Drafter's Note]{.underline}: The table below will be blank at
> contract signing.*

  --------------- ------ ------ ------ ------ ------ ------ ------ ------ ------
  **Annual                                                                
  Forecast of Net                                                         
  Requirements --                                                         
  Energy (aMW)**                                                          

  **Fiscal Year** 2012   2013   2014   2015   2016   2017   2018   2019   2020

  **Annual aMW**                                                          

  **Fiscal Year** 2021   2022   2023   2024   2025   2026   2027   2028   

  **Annual aMW**                                                          

  Note: Fill in                                                           
  the table above                                                         
  with annual                                                             
  average                                                                 
  megawatts                                                               
  rounded to                                                              
  three decimal                                                           
  places.                                                                 
  --------------- ------ ------ ------ ------ ------ ------ ------ ------ ------

> *[Drafter's Note]{.underline}: The table below will be blank at
> contract signing.*

  -----------------------------------------------------------------------------------------------------------------------------------
  **Annual                                                                                                                  
  Forecast of                                                                                                               
  Total                                                                                                                     
  Retail Load                                                                                                               
  -- Peak                                                                                                                   
  (MW)**                                                                                                                    
  ----------- --------- --------- --------- --------- --------- --------- --------- --------- --------- --------- --------- ---------
  **Fiscal    **Oct**   **Nov**   **Dec**   **Jan**   **Feb**   **Mar**   **Apr**   **May**   **Jun**   **Jul**   **Aug**   **Sep**
  Year**                                                                                                                    

  2012                                                                                                                      

  2013                                                                                                                      

  2014                                                                                                                      

  2015                                                                                                                      

  2016                                                                                                                      

  2017                                                                                                                      

  2018                                                                                                                      

  2019                                                                                                                      

  2020                                                                                                                      

  2021                                                                                                                      

  2022                                                                                                                      

  2023                                                                                                                      

  2024                                                                                                                      

  2025                                                                                                                      

  2026                                                                                                                      

  2027                                                                                                                      

  2028                                                                                                                      

  Note: Fill                                                                                                                
  in the                                                                                                                    
  table above                                                                                                               
  with                                                                                                                      
  megawatts                                                                                                                 
  rounded to                                                                                                                
  whole                                                                                                                     
  megawatt                                                                                                                  
  amounts.                                                                                                                  
  -----------------------------------------------------------------------------------------------------------------------------------

> *End Option 2*

*END **BLOCK** and **SLICE/BLOCK** templates.*

**2. LIST OF SPECIFIED RESOURCES**

> *[Drafter's Note]{.underline}: List each Specified Resource, in the
> applicable subsection, using the format shown below in section 2.1(1).
> Determine the Dedicated Resource amounts for Specified Resources per
> the updated 5(b)/9(c) Policy (which is currently under review).*
> [\[\[Any proposed updated 5(b) 9(c) Policy should be made available
> for comment prior to its adoption.\]\]]{.mark}*When using PNCA studies
> to calculate Dedicated Resource amounts use the most current study
> released as of August 18, 2008. The most current PNCA study will
> either be the Modified Regulation for 2008-2009 (released in May 2009)
> or the Final Regulation for 2008-2009 (release forthcoming).*

*Include in **LOAD FOLLOWING** template:*

> 2.1 **Generating Resources**
>
> All of «Customer Name»'s Generating Resources dedicated to serve its
> Total Retail Load, except Small Non-Dispatchable Resources, are listed
> below.

*END **LOAD FOLLOWING** template.*

*Include in **BLOCK** and **SLICE/BLOCK** templates:*

> 2.1 **Generating Resources**
>
> All of «Customer Name»'s Generating Resources dedicated to serve its
> Total Retail Load are listed below.

*END **BLOCK** and **SLICE/BLOCK** templates.*

> *[Drafter's Note:]{.underline} If «Customer Name» does not have any
> Generating Resources delete sections 2.1(1)(A),(B), and (C) below and
> leave only the following text in this section:*
>
> No Generating Resources at this time*.*
>
> \(1\) **«Resource Name»**
>
> *[Drafter's Note:]{.underline} If «Customer Name» has Generating
> Resources dedicated to its TRL complete the following steps for each
> resource: insert the resource name as the title for section 2.1(1),
> add any special provisions for such resource to section 2.1(1)(A),and
> fill in the tables in section 2.1(1)(B) and (C). Delete "No Generating
> Resources at this time" from above.*
>
> \(A\) **Special Provisions**
>
> *[Drafter's Note]{.underline}: Include any special provisions here
> that are applicable to this resource. If none, retain this section and
> state "None".*
>
> \(B\) **Resource Profile**

  ----------------------- ------------- ------------ ----------- -------------
  **Fuel Type**           **Date        **Date of    **Percent   **Nameplate
                          Resource      Resource     Dedicated   Capability
                          Dedicated to  Removal**    to Load**   (MW)**
                          Load**                                 

                                                                 
  ----------------------- ------------- ------------ ----------- -------------

  ------------- ------ ------------ -------- ------------------- ------ ----------- ------ ------------ -------
  **Statutory          **Diurnal             **Dispatchable?**          **PNCA?**          **If PNCA,   
  Status**             Flattening                                                          PNCA         
                       Service?**                                                          Updates?**   

  5b1A          5b1B   Yes          No       Yes                 No     Yes         No     Yes          No

                                                                                                        

  Note: Fill in                                                                                         
  the table                                                                                             
  above with                                                                                            
  "X"s.                                                                                                 
  ------------- ------ ------------ -------- ------------------- ------ ----------- ------ ------------ -------

> \(C\) **Specified Resource Amounts**

  ---------------------------------------------------------------------------------------------------------------------------------------------------
  **Specified                                                                                                                               
  Resource                                                                                                                                  
  Amounts**                                                                                                                                 
  ----------------- --------- --------- --------- --------- --------- --------- --------- --------- --------- --------- --------- --------- ---------
                    **Oct**   **Nov**   **Dec**   **Jan**   **Feb**   **Mar**   **Apr**   **May**   **Jun**   **Jul**   **Aug**   **Sep**   **Total
                                                                                                                                            (annual
                                                                                                                                            aMW)**

  **Fiscal Year                                                                                                                             
  2012**                                                                                                                                    

  **Total (MWh)**                                                                                                                           

  **HLH (MWh)**                                                                                                                             

  **LLH (MWh)**                                                                                                                             

  **Peak (MW)**                                                                                                                             

  **Fiscal Year                                                                                                                             
  2013**                                                                                                                                    

  **Total (MWh)**                                                                                                                           

  **HLH (MWh)**                                                                                                                             

  **LLH (MWh)**                                                                                                                             

  **Peak (MW)**                                                                                                                             

  **Fiscal Year                                                                                                                             
  2014**                                                                                                                                    

  **Total (MWh)**                                                                                                                           

  **HLH (MWh)**                                                                                                                             

  **LLH (MWh)**                                                                                                                             

  **Peak (MW)**                                                                                                                             

  **Fiscal Year                                                                                                                             
  2015**                                                                                                                                    

  **Total (MWh)**                                                                                                                           

  **HLH (MWh)**                                                                                                                             

  **LLH (MWh)**                                                                                                                             

  **Peak (MW)**                                                                                                                             

  **Fiscal Year                                                                                                                             
  2016**                                                                                                                                    

  **Total (MWh)**                                                                                                                           

  **HLH (MWh)**                                                                                                                             

  **LLH (MWh)**                                                                                                                             

  **Peak (MW)**                                                                                                                             

  **Fiscal Year                                                                                                                             
  2017**                                                                                                                                    

  **Total (MWh)**                                                                                                                           

  **HLH (MWh)**                                                                                                                             

  **LLH (MWh)**                                                                                                                             

  **Peak (MW)**                                                                                                                             

  **Fiscal Year                                                                                                                             
  2018**                                                                                                                                    

  **Total (MWh)**                                                                                                                           

  **HLH (MWh)**                                                                                                                             

  **LLH (MWh)**                                                                                                                             

  **Peak (MW)**                                                                                                                             

  **Fiscal Year                                                                                                                             
  2019**                                                                                                                                    

  **Total (MWh)**                                                                                                                           

  **HLH (MWh)**                                                                                                                             

  **LLH (MWh)**                                                                                                                             

  **Peak (MW)**                                                                                                                             

  **Fiscal Year                                                                                                                             
  2020**                                                                                                                                    

  **Total (MWh)**                                                                                                                           

  **HLH (MWh)**                                                                                                                             

  **LLH (MWh)**                                                                                                                             

  **Peak (MW)**                                                                                                                             

  **Fiscal Year                                                                                                                             
  2021**                                                                                                                                    

  **Total (MWh)**                                                                                                                           

  **HLH (MWh)**                                                                                                                             

  **LLH (MWh)**                                                                                                                             

  **Peak (MW)**                                                                                                                             

  **Fiscal Year                                                                                                                             
  2022**                                                                                                                                    

  **Total (MWh)**                                                                                                                           

  **HLH (MWh)**                                                                                                                             

  **LLH (MWh)**                                                                                                                             

  **Peak (MW)**                                                                                                                             

  **Fiscal Year                                                                                                                             
  2023**                                                                                                                                    

  **Total (MWh)**                                                                                                                            

  **HLH (MWh)**                                                                                                                              

  **LLH (MWh)**                                                                                                                              

  **Peak (MW)**                                                                                                                              

  **Fiscal Year                                                                                                                             
  2024**                                                                                                                                    

  **Total (MWh)**                                                                                                                           

  **HLH (MWh)**                                                                                                                             

  **LLH (MWh)**                                                                                                                             

  **Peak (MW)**                                                                                                                             

  **Fiscal Year                                                                                                                             
  2025**                                                                                                                                    

  **Total (MWh)**                                                                                                                           

  **HLH (MWh)**                                                                                                                             

  **LLH (MWh)**                                                                                                                             

  **Peak (MW)**                                                                                                                             

  **Fiscal Year                                                                                                                             
  2026**                                                                                                                                    

  **Total (MWh)**                                                                                                                           

  **HLH (MWh)**                                                                                                                             

  **LLH (MWh)**                                                                                                                             

  **Peak (MW)**                                                                                                                             

  **Fiscal Year                                                                                                                             
  2027**                                                                                                                                    

  **Total (MWh)**                                                                                                                           

  **HLH (MWh)**                                                                                                                             

  **LLH (MWh)**                                                                                                                             

  **Peak (MW)**                                                                                                                             

  **Fiscal Year                                                                                                                             
  2028**                                                                                                                                    

  **Total (MWh)**                                                                                                                           

  **HLH (MWh)**                                                                                                                             

  **LLH (MWh)**                                                                                                                             

  **Peak (MW)**                                                                                                                             

  Note: Fill in the                                                                                                                         
  table above with                                                                                                                          
  megawatt-hours                                                                                                                            
  rounded to whole                                                                                                                          
  megawatt-hours,                                                                                                                           
  with megawatts                                                                                                                            
  rounded to whole                                                                                                                          
  megawatts, and                                                                                                                            
  annual average                                                                                                                            
  megawatts rounded                                                                                                                         
  to three decimal                                                                                                                          
  places.                                                                                                                                   
  ---------------------------------------------------------------------------------------------------------------------------------------------------

2.2 **Contract Resources**

> All of «Customer Name»'s Contract Resources dedicated to serve its
> Total Retail Load are listed in tables below.
>
> *[Drafter's Note:]{.underline} If «Customer Name» does not have any
> Contract Resources delete sections 2.2(1) below and leave only the
> following text in this section:*
>
> No Contract Resources at this time*.*
>
> \(1\) **«Resource Name»**
>
> *[Drafter's Note:]{.underline} If «Customer Name» has Contract
> Resources dedicated to its TRL list the resources below and complete
> the following steps for each resource using the format in section
> 2.1(1): insert the resource name as a title for section 2.2(1), add
> any special provisions for such resource to section 2.2(1)(A), add a
> resource profile table to section 2.2(1)(B) using the table format in
> section 2.1(1)(B), add dedicated resource amounts to section 2.2(1)(C)
> using the table format in section 2.1(1) (C). Delete "No Contract
> Resources at this time" from above.*

*Include in **LOAD FOLLOWING** template:*

> 2.3 **Small Non-Dispatchable Resources**
>
> All of «Customer Name»'s Small Non-Dispatchable Resources dedicated to
> serve its Total Retail Load are listed in tables below.
>
> *[Drafter's Note:]{.underline} If «Customer Name» does not have any
> Small Non-Dispatchable Resources delete sections 2.3(1) and leave only
> the following text in this section:*
>
> No Small Non-Dispatchable Resources at this time*.*
>
> \(1\) **«Resource Name»**
>
> *[Drafter's Note:]{.underline} If «Customer Name» has Small
> Non-Dispatchable Resources dedicated to its TRL list the resources
> below and complete the following steps for each resource using the
> format in section 2.1(1): insert the resource name as a title for
> section 2.3(1), add any special provisions for such resource to
> section 2.3(1)(A), add a resource profile table to section 2.3(1)(B)
> using the table format in section 2.1(1)(B), add dedicated resource
> amounts to section 2.3(1)(C) using the table format in section 2.1(1)
> (C). Delete "No Small Non-Dispatchable Resources at this time" from
> above.*

*END **LOAD FOLLOWING** template.*

**3. UNSPECIFIED RESOURCE AMOUNTS**

> [Unspecified Resource Amounts are limited to]{.mark}
>
> []{.mark}
>
> [(i) market purchases that are to serve load that does not match the
> customer's existing resources and delivery of Federal power from time
> to time;]{.mark} [*provided*, that]{.mark} [«Customer Name»
> shall]{.mark} [make any such market purchases to serve that portion of
> load that does not match such customer's existing resources and
> delivery of Federal power under all such circumstances, and]{.mark}
>
> []{.mark}
>
> [(ii)]{.mark} [Unspecified Resource Amounts inserted by BPA pursuant
> to section 3.2 of]{.mark} [this]{.mark} [Exhibit A for Northwest Power
> Act Section 9(c) or Regional Preference Act Section 3(d) Export
> Decrements pursuant to section 3.5.2 of the body of this
> Agreement.]{.mark}

*Include in **LOAD FOLLOWING** template:*

> 3.1 **Unspecified Resource Amounts Dedicated to Total Retail Load**
>
> 3.1.1 **Shape of Unspecified Resource Amounts**
>
> «Customer Name»'s Unspecified Resource Amounts shall be calculated
> using the selected monthly and Diurnal shapes listed below. BPA shall
> update the table below consistent with section 3.4.2 of the body of
> this Agreement.
>
> *[Drafter's Note:]{.underline} The following table shall appear "as
> is" at contract signing.*

  ----------------- ------------- ------------- ------------ --------------
  **Shape of                                                 
  Unspecified                                                
  Resource                                                   
  Amounts**                                                  

  ** **             **Monthly                   **Diurnal    
                    Shape                       Shape        
                    Choice**                    Choice**     

  **Purchase        **Total       **Flat Annual **HLH        **Flat
  Period**          Retail Load   Shape**       Diurnal      Within-Month
                    Monthly                     Shape**      Shape**
                    Shape**                                  

  FY 2012 --                      X                          X
  FY 2014                                                    

  FY 2015 --                      X                          X
  FY 2019                                                    

  FY 2020 --                      X                          X
  FY 2024                                                    

  FY 2025 --                      X                          X
  FY 2028                                                    
  ----------------- ------------- ------------- ------------ --------------

> 3.1.2 **Unspecified Resource Amounts**
>
> «Customer Name»'s Unspecified Resource Amounts dedicated to serve its
> Total Retail Load are listed in the table below.

*END **LOAD FOLLOWING** template.*

*Include in **BLOCK** and **SLICE/BLOCK** templates:*

> 3.1 **Unspecified Resource Amounts Dedicated to Total Retail Load**
>
> «Customer Name»'s Unspecified Resource Amounts dedicated to serve its
> Total Retail Load are listed in the table below.

*END **BLOCK** and **SLICE/BLOCK** templates.*

> *[Drafter's Note:]{.underline} If «Customer Name» does not have any
> Unspecified Resource Amounts delete the table below and leave only the
> following text in this section:*
>
> No Unspecified Resource Amounts at this time*.*
>
> *[Drafter's Note:]{.underline} If «Customer Name» has Unspecified
> Resource Amounts list them in the table below adding additional years
> as needed. Delete "No Unspecified Resource Amounts" from above.*

  --------------------------------------------------------------------------------------------------------------------------------------------------
  **Unspecified                                                                                                                            
  Resource                                                                                                                                 
  Amounts**                                                                                                                                
  ---------------- --------- --------- --------- --------- --------- --------- --------- --------- --------- --------- --------- --------- ---------
                   **Oct**   **Nov**   **Dec**   **Jan**   **Feb**   **Mar**   **Apr**   **May**   **Jun**   **Jul**   **Aug**   **Sep**   **Total
                                                                                                                                           (annual
                                                                                                                                           aMW)**

  **Fiscal Year                                                                                                                            
  2012**                                                                                                                                   

  **Total (MWh)**                                                                                                                          

  **HLH (MWh)**                                                                                                                            

  **LLH (MWh)**                                                                                                                            

  **Fiscal Year                                                                                                                            
  2013**                                                                                                                                   

  **Total (MWh)**                                                                                                                          

  **HLH (MWh)**                                                                                                                            

  **LLH (MWh)**                                                                                                                            

  Note: Fill in                                                                                                                            
  the table above                                                                                                                          
  with                                                                                                                                     
  megawatt-hours                                                                                                                           
  rounded to whole                                                                                                                         
  megawatt-hours                                                                                                                           
  and with annual                                                                                                                          
  average                                                                                                                                  
  megawatts                                                                                                                                
  rounded to three                                                                                                                         
  decimal places.                                                                                                                          
  --------------------------------------------------------------------------------------------------------------------------------------------------

> 3.2 **Unspecified Resource Amounts for** **[Northwest Power Act
> Section 9(c) or]{.mark}** **[Regional Preference Act Section
> 3(d)]{.mark}** **Export Decrements**
>
> Pursuant to section 3.5.2 of the body of this Agreement, BPA shall
> insert a table below for any decrements due to export of resources in
> the shape, duration, and amount of the export.

**4. DEDICATED RESOURCE AMOUNTS FOR AN NLSL**

> «Customer Name»'s Dedicated Resource amounts serving an NLSL are
> listed in the table(s) below.
>
> *[Drafter's Note:]{.underline} If «Customer Name» does not have any
> Dedicated Resource amounts serving an NLSL then leave only the
> following text in this section:*
>
> No Dedicated Resource amounts serving an NLSL at this time*.*
>
> *[Drafter's Note:]{.underline} If «Customer Name» has Unspecified
> Resource Amounts serving an NLSL list the amounts in a table below
> using the table format above in section 3.1 and adding additional
> years as needed. Delete "No Dedicated Resource Amounts serving an NLSL
> at this time" from above.*
>
> *[Drafter's Note:]{.underline} If «Customer Name» has Specified
> Resources serving an NLSL list the resources below and complete the
> following steps for each resource using the format in section 2.1(1):
> insert the resource name as a title for section 4(1), add any special
> provisions for such resource to section 4(1)(A), add a resource
> profile table to section 4(1)(B) using the table format in section
> 2.1(1)(B), add Dedicated Resource amounts to section 4(1)(C) using the
> table format in section 2.1(1)(C). Delete "No Dedicated Resource
> amounts serving an NLSL at this time" from above.*

**5. TOTAL DEDICATED RESOURCES AMOUNTS**

> The amounts in the table below equal the sum of all resource amounts
> dedicated to «Customer Name»'s Total Retail Load listed above in
> sections 2, 3, and 4.
>
> *[Drafter's Note:]{.underline} If «Customer Name» does not have any
> Dedicated Resource amounts listed in section 2, 3, or 4 above then
> leave only the following text in this section:*
>
> No Dedicated Resource amounts at this time*.*
>
> *[Drafter's Note:]{.underline} If «Customer Name» has any Dedicated
> Resource amounts listed in section 2, 3, or 4 above insert a table
> below, using the table format in section 2.1(1)(C), with amounts equal
> to the sum of all Dedicated Resource amounts listed in section 2, 3,
> and 4. Delete "No Dedicated Resource amounts at this time from above.*

**6. LIST OF RESOURCES NOT DEDICATED TO TOTAL RETAIL LOAD**

> Pursuant to section 3.6 of the body of this Agreement, all of
> «Customer Name»'s Generating and Contract Resources not dedicated to
> serve its Total Retail Load that are greater than 200 kilowatts
> nameplate capability are listed in tables below.
>
> *[Drafter's Note:]{.underline} If «Customer Name» does not have any
> resources not dedicated to its TRL then delete sections 6(1), 6(1)(A),
> and 6(1)(B) and leave only the following text in this section:*
>
> No resources at this time*.*

\(1\) **«Resource Name»**

> *[Drafter's Note:]{.underline} If «Customer Name» has resources not
> dedicated to its TRL complete the following steps for each resource:
> insert the resource name as the title for section 6(1) and fill in the
> tables in section 6(1)(A) and (B). Delete "No resources at this time"
> from above.*
>
> \(A\) **Resource Profile**

  -------------------------- -------------- --------------- --------------
  **Fuel Type**              **Type of                      **Nameplate
                             Resource**                     Capability
                                                            (MW)**

                             **Generating   **Contract      
                             Resource**     Resource**      

                                                            
  -------------------------- -------------- --------------- --------------

> \(B\) **Expected Resource Output**

  --------------- ------ ------ ------ ------ ------ ------ ------ ------ ------
  **Expected                                                              
  Output --                                                               
  Energy (aMW)**                                                          

  **Fiscal Year** 2012   2013   2014   2015   2016   2017   2018   2019   2020

  **Annual aMW**                                                          

  **Fiscal Year** 2021   2022   2023   2024   2025   2026   2027   2028   

  **Annual aMW**                                                          

  Note: Fill in                                                           
  the table above                                                         
  with annual                                                             
  average                                                                 
  megawatts                                                               
  rounded to                                                              
  three decimal                                                           
  places.                                                                 
  --------------- ------ ------ ------ ------ ------ ------ ------ ------ ------

**7. LIST OF CONSUMER-OWNED RESOURCES**

> 7.1 **Consumer-Owned Resources Serving Onsite Consumer Load**
>
> Pursuant to section 3.7 of the body of this Agreement, all of
> «Customer Name»'s Consumer-Owned Resources serving Onsite Consumer
> Load, except any Consumer-Owned Resources serving an NLSL which are
> listed below in section 7.3 of this Exhibit, are listed in tables
> below.
>
> *[Drafter's Note:]{.underline} If «Customer Name» does not have any
> Consumer-Owned Resources serving Onsite Consumer Load then delete
> sections 7.1(1), 7.1(1)(A), and 7.1(1)(B) and leave only the following
> text in this section:*
>
> No Consumer-Owned Resources serving Onsite Consumer Load at this time.
>
> \(1\) **«Resource Name»**
>
> *[Drafter's Note:]{.underline} If «Customer Name» has Consumer-Owned
> Resources serving Onsite Consumer Load complete the following steps
> for each resource: insert the resource name as the title for section
> 7.1(1) and fill in the tables in section 7.1(1)(A) and (B). Delete "No
> Consumer-Owned Resources serving Onsite Consumer Load at this time"
> from above.*
>
> \(A\) **Resource Profile**

  --------------------------- ------------------------- ------------------
  **Resource Owner**          **Fuel Type**             **Nameplate
                                                        Capability (MW)**

                                                        
  --------------------------- ------------------------- ------------------

> \(B\) **Expected Resource Output**

  --------------- ------ ------ ------ ------ ------ ------ ------ ------ ------
  **Expected                                                              
  Output --                                                               
  Energy (aMW)**                                                          

  **Fiscal Year** 2012   2013   2014   2015   2016   2017   2018   2019   2020

  **Annual aMW**                                                          

  **Fiscal Year** 2021   2022   2023   2024   2025   2026   2027   2028   

  **Annual aMW**                                                          

  Note: Fill in                                                           
  the table above                                                         
  with annual                                                             
  average                                                                 
  megawatts                                                               
  rounded to                                                              
  three decimal                                                           
  places.                                                                 
  --------------- ------ ------ ------ ------ ------ ------ ------ ------ ------

> 7.2 **Consumer-Owned Resources Serving Load Other than Onsite Consumer
> Load**
>
> Pursuant to section 3.7 of the body of this Agreement, all of
> «Customer Name»'s Consumer-Owned Resources serving load other than
> Onsite Consumer Load are listed in tables below.
>
> *[Drafter's Note:]{.underline} If «Customer Name» does not have any
> Consumer-Owned Resources serving load other than Onsite Consumer Load
> then delete sections 7.2(1), 7.2(1)(A), and 7.2(1)(B) and leave only
> the following text in this section:*
>
> No Consumer-Owned Resources serving load other than Onsite Consumer
> Load at this time.
>
> \(1\) **«Resource Name»**
>
> *[Drafter's Note:]{.underline} If «Customer Name» has Consumer-Owned
> Resources serving load other than Onsite Consumer Load complete the
> following steps for each resource: insert the resource name as the
> title for section 7.2(1) and fill in the tables in section 7.2(1)(A)
> and (B). Delete "No Consumer-Owned Resources serving load other than
> Onsite Consumer Load at this time" from above.*
>
> \(A\) **Resource Profile**

  --------------------------- ------------------------- ------------------
  **Resource Owner**          **Fuel Type**             **Nameplate
                                                        Capability (MW)**

                                                        
  --------------------------- ------------------------- ------------------

> \(B\) **Expected Resource Output**

  --------------- ------ ------ ------ ------ ------ ------ ------ ------ ------
  **Expected                                                              
  Output --                                                               
  Energy (aMW)**                                                          

  **Fiscal Year** 2012   2013   2014   2015   2016   2017   2018   2019   2020

  **Annual aMW**                                                          

  **Fiscal Year** 2021   2022   2023   2024   2025   2026   2027   2028   

  **Annual aMW**                                                          

  Note: Fill in                                                           
  the table above                                                         
  with annual                                                             
  average                                                                 
  megawatts                                                               
  rounded to                                                              
  three decimal                                                           
  places.                                                                 
  --------------- ------ ------ ------ ------ ------ ------ ------ ------ ------

> 7.3 **Consumer-Owned Resources Serving an NLSL**
>
> Pursuant to section 24.3.7 of the body of this Agreement, all of
> «Customer Name»'s Consumer-Owned Resources serving an NLSL are listed
> in tables below.
>
> *[Drafter's Note:]{.underline} If «Customer Name» does not have any
> Consumer-Owned Resources an NLSL then delete sections 7.3(1),
> 7.3(1)(A), and 7.3(1)(B) and leave only the following text in this
> section:*
>
> No Consumer-Owned Resources serving an NLSL at this time.
>
> \(1\) **«Resource Name»**
>
> *[Drafter's Note:]{.underline} If «Customer Name» has Consumer-Owned
> Resources serving an NLSL complete the following steps for each
> resource: insert the resource name as the title for section 7.3(1) and
> fill in the tables in section 7.3(1)(A) and (B). Delete "No
> Consumer-Owned Resources serving an NLSL at this time" from above.*
>
> \(A\) **Resource Profile**

  --------------------------- ------------------------- ------------------
  **Resource Owner**          **Fuel Type**             **Nameplate
                                                        Capability (MW)**

                                                        
  --------------------------- ------------------------- ------------------

> \(B\) **Expected Resource Output**

  --------------- ------ ------ ------ ------ ------ ------ ------ ------ ------
  **Expected                                                              
  Output --                                                               
  Energy (aMW)**                                                          

  **Fiscal Year** 2012   2013   2014   2015   2016   2017   2018   2019   2020

  **Annual aMW**                                                          

  **Fiscal Year** 2021   2022   2023   2024   2025   2026   2027   2028   

  **Annual aMW**                                                          

  Note: Fill in                                                           
  the table above                                                         
  with annual                                                             
  average                                                                 
  megawatts                                                               
  rounded to                                                              
  three decimal                                                           
  places.                                                                 
  --------------- ------ ------ ------ ------ ------ ------ ------ ------ ------

*Include in **LOAD FOLLOWING** template:*

**8.** **TABLES FOR ALLOWABLE DEDICATED RESOURCE SHAPES**

> 8.1 **Total Retail Load Monthly Shape**
>
> By March 31 immediately following each of the Fiscal Years 2010, 2015,
> and 2020, BPA shall fill in the table below with «Customer Name»'s
> Total Retail Load Monthly Shape. «Customer Name»'s Total Retail Load
> Monthly Shape shall be calculated by dividing «Customer Name»'s Total
> Retail Load (in megawatt-hours) in each month of Fiscal Years 2010,
> 2015, and 2020 by the Fiscal Year total of «Customer Name»'s Total
> Retail Load (in megawatt-hours). BPA shall weather-normalize «Customer
> Name»'s Total Retail Load data, prior to calculating the Total Retail
> Load Monthly Shape, using the same weather-normalization procedures
> used to calculate CHWMs.
>
> *[Drafter's Note]{.underline}: The table below will be blank at
> contract signing.*

  ----------------------------------------------------------------------------------------------------------------------------------------------
  **Total                                                                                                                            
  Retail                                                                                                                             
  Load                                                                                                                               
  Monthly                                                                                                                            
  Shape                                                                                                                              
  (%)**                                                                                                                              
  ---------- --------- --------- --------- --------- --------- --------- --------- --------- --------- --------- --------- --------- -----------
  ** **      **Oct**   **Nov**   **Dec**   **Jan**   **Feb**   **Mar**   **Apr**   **May**   **Jun**   **Jul**   **Aug**   **Sep**   **Total**

  FY2010                                                                                                                             100.0

  FY2015                                                                                                                             100.0

  FY2020                                                                                                                             100.0

  Note: Fill                                                                                                                         
  in the                                                                                                                             
  table                                                                                                                              
  above with                                                                                                                         
  percents                                                                                                                           
  rounded to                                                                                                                         
  the                                                                                                                                
  nearest                                                                                                                            
  one                                                                                                                                
  decimal                                                                                                                            
  place                                                                                                                              
  ----------------------------------------------------------------------------------------------------------------------------------------------

> 8.2 **HLH Diurnal Shape**
>
> 8.2.1 **Specified Resources**
>
> If «Customer Name» elects the HLH Diurnal Shape for its Specified
> Resources, «Customer Name» shall fill in a table with monthly LLH and
> HLH amounts (in megawatts) for each year of the upcoming Purchase
> Period for each Specified Resource. The monthly LLH and HLH
> distributions shall be the same across all years. «Customer Name»
> shall submit the tables to BPA when «Customer Name» makes its
> reshaping elections. BPA shall update the appropriate Dedicated
> Resource amounts pursuant to «Customer Name»'s submitted elections and
> consistent with section 3.4.2 of the body of this Agreement.
>
> 8.2.2 **Unspecified Resource Amounts**
>
> If «Customer Name» elects the HLH Diurnal Shape for its Unspecified
> Resource Amounts, «Customer Name» shall notify BPA in writing the
> percent of Unspecified Resource Amounts which will be greater in HLH
> than in LLH for each month. BPA shall update the table below pursuant
> to «Customer Name»'s submitted elections and consistent with
> section 3.4.2 of the body of this Agreement. BPA shall calculate
> «Customer Name»'s Unspecified Resource Amounts using the percents in
> the table below if «Customer Name» elects the HLH Diurnal Shape.
>
> *[Drafter's Note]{.underline}: The table below will be blank at
> contract signing.*

  ----------------------------------------------------------------------------------------------------------------------------------------
  **HLH Diurnal                                                                                                                  
  Shape for                                                                                                                      
  Unspecified                                                                                                                    
  Resource                                                                                                                       
  Amounts**                                                                                                                      
  -------------- ----------- --------- --------- --------- --------- --------- --------- --------- --------- --------- --------- ---------
  **Purchase     **Greater                                                                                                       
  Period**       Percent in                                                                                                      
                 HLH**                                                                                                           

                 **Oct**     **Nov**   **Dec**   **Jan**   **Feb**   **Mar**   **Apr**   **May**   **Jun**   **Jul**   **Aug**   **Sep**

  FY 2012 --                                                                                                                     
  FY 2014                                                                                                                        

  FY 2015 --                                                                                                                     
  FY 2019                                                                                                                        

  FY 2020 --                                                                                                                     
  FY 2024                                                                                                                        

  FY 2025 --                                                                                                                     
  FY 2028                                                                                                                        

  Note: Fill in                                                                                                                  
  the table                                                                                                                      
  above with                                                                                                                     
  percents                                                                                                                       
  rounded to one                                                                                                                 
  decimal place.                                                                                                                 
  ----------------------------------------------------------------------------------------------------------------------------------------

**9. SUPER PEAK AMOUNTS**

> «Customer Name» may reshape all of its HLH Dedicated Resource amounts
> for its (1) Specified Resources listed in section 2 of Exhibit A,
> except for any Small Non-Dispatchable Resources and any Specified
> Resources «Customer Name» is supporting with Diurnal Flattening
> Services from BPA; and (2) Unspecified Resource Amounts listed in
> section 3.1.2 of Exhibit A; into Super Peak Hours to receive a Super
> Peak Resource Credit. BPA shall update the table below consistent with
> section 3.4.4 of the body of this Agreement.
>
> *[Drafter's Note]{.underline}: The table below will be blank at
> contract signing.*

  -----------------------------------------------------------------------------------------------------------------------------------
  **Super                                                                                                                   
  Peak                                                                                                                      
  Amounts                                                                                                                   
  (MW)**                                                                                                                    
  ----------- --------- --------- --------- --------- --------- --------- --------- --------- --------- --------- --------- ---------
  **Fiscal    **Oct**   **Nov**   **Dec**   **Jan**   **Feb**   **Mar**   **Apr**   **May**   **Jun**   **Jul**   **Aug**   **Sep**
  Year**                                                                                                                    

  2012                                                                                                                      

  2013                                                                                                                      

  2014                                                                                                                      

  2015                                                                                                                      

  2016                                                                                                                      

  2017                                                                                                                      

  2018                                                                                                                      

  2019                                                                                                                      

  2020                                                                                                                      

  2021                                                                                                                      

  2022                                                                                                                      

  2023                                                                                                                      

  2024                                                                                                                      

  2025                                                                                                                      

  2026                                                                                                                      

  2027                                                                                                                      

  2028                                                                                                                      

  Note: Fill                                                                                                                
  in the                                                                                                                    
  table above                                                                                                               
  with                                                                                                                      
  megawatts                                                                                                                 
  rounded to                                                                                                                
  the nearest                                                                                                               
  three                                                                                                                     
  decimal                                                                                                                   
  places.                                                                                                                   
  -----------------------------------------------------------------------------------------------------------------------------------

**10. REVISIONS**

> BPA shall make adjustments to this exhibit to reflect (1) BPA's
> determinations under this Agreement and BPA's 5(b)/9(c) Policy, and
> (2) «Customer Name»'s elections regarding the application and use of
> all resources listed by «Customer Name» to serve its Total Retail
> Load, as provided under this Agreement.

*END **LOAD FOLLOWING** template.*

*Include in the **BLOCK** and **SLICE/BLOCK** template:*

**8. REVISIONS**

> BPA shall make adjustments to this exhibit to reflect (1) BPA's
> determinations under this Agreement and BPA's 5(b)/9(c) Policy, and
> (2) «Customer Name»'s elections regarding the application and use of
> all resources listed by «Customer Name» to serve its Total Retail
> Load, as provided under this Agreement.

*END **BLOCK** and **SLICE/BLOCK** template.*

> (PS«X/LOC»- «File Name with Path».DOC) «mm/dd/yy» *{[Drafter's
> Note]{.underline}: Insert date of finalized contract here}*

**Exhibit B**

**HIGH WATER MARKS AND CONTRACT DEMAND QUANTITIES**

**1. CONTRACT HIGH WATER MARK (CHWM)** ***(06/13/08 Version)***

> *[Reviewer's Note]{.underline}: See "Timeline for HWMs & Above-RHWM
> Elections"*
>
> 1.1 **CHWM Amount**
>
> By September 15, 2011, BPA shall update the table below with «Customer
> Name»'s CHWM. Once established, «Customer Name»'s CHWM shall not
> change for the term of this Agreement except as allowed in section 1.2
> below.
>
> *[Drafter's Note]{.underline}: Leave table blank at contract signing.*

  -------------------------------------- --------------------------------
  **CHWM (annual aMW):**                 

  Note: BPA shall round the number in    
  the table above to three decimal       
  places.                                
  -------------------------------------- --------------------------------

> 1.2 **Changes to CHWM**
>
> If a change is made to «Customer Name»'s CHWM pursuant to this
> section, BPA shall determine and notify «Customer Name» the date such
> change will be effective.
>
> 1.2.1 If a load included in «Customer Name»'s Measured 2010 Load, as
> defined in the TRM, is later found to be an NLSL, BPA shall reduce
> «Customer Name»'s CHWM by the amount of the NLSL.
>
> 1.2.2 If «Customer Name» acquires an Annexed Load from a utility that
> has a CHWM, BPA shall increase «Customer Name»'s CHWM by adding part
> of the other utility's CHWM to «Customer Name»'s CHWM. The amount of
> the CHWM addition shall equal:

  ---- ------------------------------------ ---- --- ---- --------------------- ----
  \[   Annexed Load minus any annexed NLSLs \]   ×   \[   Other utility's       \]
                                                          pre-annexation CHWM   

       Other utility's pre-annexation Total                                     
       Retail Load minus total NLSLs, if                                        
       any                                                                      
  ---- ------------------------------------ ---- --- ---- --------------------- ----

> *\[[Drafter's Note]{.underline}: Include the following sentence for
> any cooperative. If not a cooperative, delete the following
> sentence:*Any change to «Customer Name»'s CHWM related to the
> acquisition of an Annexed Load is subject to section 25.8 of the body
> of this Agreement.*\]*
>
> 1.2.3 If another utility with a CHWM annexes load of «Customer Name»,
> BPA shall reduce «Customer Name»'s CHWM by adding part of «Customer
> Name»'s CHWM to the other utility's CHWM. The amount of the CHWM
> reduction shall equal:

  ---- -------------------------------------- ---- ---- ---- ------------------ ----
  \[   Annexed Load minus any annexed NLSLs   \]   ×    \[   «Customer Name»'s  \]
                                                             pre-annexation     
                                                             CHWM               

       «Customer Name»'s pre-annexation Total                                   
       Retail Load minus total NLSLs, if any                                    
  ---- -------------------------------------- ---- ---- ---- ------------------ ----

> []{.mark}
>
> 1.2.4 BPA may change «Customer Name»'s CHWM if BPA's Administrator
> determines that BPA is effectively required by court order to make
> such changes. BPA shall determine the effective date of such a change
> and shall update this exhibit with the changed CHWM.

**2. CONTRACT DEMAND QUANTITIES (CDQs)** ***(05/27/08 Version)***

> 2.1 **CDQ Amounts**
>
> By September 15, 2011, BPA shall update the table below with «Customer
> Name»'s monthly CDQs. Applicability of such CDQs is established in the
> TRM. «Customer Name»'s monthly CDQs shall not change for the term of
> this Agreement except as allowed below.
>
> *[Drafter's Note]{.underline}*: Leave table blank at contract signing.

  -------------- --------- --------- --------- --------- --------- --------- --------- --------- --------- --------- --------- ---------
  **Monthly                                                                                                                    
  Contract                                                                                                                     
  Demand                                                                                                                       
  Quantities**                                                                                                                 

                 **Oct**   **Nov**   **Dec**   **Jan**   **Feb**   **Mar**   **Apr**   **May**   **Jun**   **Jul**   **Aug**   **Sep**

  **MW**                                                                                                                       

  Note: BPA                                                                                                                    
  shall round                                                                                                                  
  the megawatt                                                                                                                 
  amounts in the                                                                                                               
  table above to                                                                                                               
  three decimal                                                                                                                
  places.                                                                                                                      
  -------------- --------- --------- --------- --------- --------- --------- --------- --------- --------- --------- --------- ---------

> 2.2 **Changes Due to Annexation**
>
> The Parties shall determine when changes to «Customer Name»'s CDQs, as
> allowed below, will become effective.
>
> \(1\) If «Customer Name» acquires an Annexed Load from a utility that
> has monthly CDQs, BPA shall increase «Customer Name»'s CDQ for each
> month by adding the portion of the other utility's CDQ that is
> attributable to such Annexed Load.
>
> \(2\) If another utility with monthly CDQs annexes load of «Customer
> Name», BPA shall reduce «Customer Name»'s CDQ for each month by
> removing the portion of «Customer Name»'s CDQ that is attributable to
> the load that was annexed.

**3. REVISIONS *(03/30/08 Version)***

> BPA may revise this exhibit to the extent allowed in sections 1 and 2
> above. All other changes shall be made by mutual agreement.

(PS«X/LOC»- «File Name with Path».DOC) «mm/dd/yy» *{[Drafter's
Note]{.underline}: Insert date of finalized contract here}*

**Exhibit C**

**PURCHASE OBLIGATIONS**

*Include in **LOAD FOLLOWING** template:*

**1. FIRM REQUIREMENTS POWER AT PF TIER 1*(06/13/08 Version)***

> PF Tier 1 rates shall apply as established in section 8.1.1(1) of the
> body of this Agreement.

*END **LOAD FOLLOWING** template.*

*Include in **BLOCK** template:*

**1. FIRM REQUIREMENTS POWER AT PF TIER 1*(05/27/08 Version)***

1.1 **Block Power - Annual Average Amount**

> The annual average amount of Firm Requirements Power priced at PF
> Tier 1 rates shall equal the lesser of «Customer Name»'s RHWM, or
> «Customer Name»'s forecast annual Net Requirement load stated in
> Exhibit A, Net Requirements and Resources.

*[Option 1]{.underline}: Include if customer chooses a Flat Block:*

1.2 **Flat Block**

> Except for amounts specified in section 1.4 below, amounts of Firm
> Requirements Power priced at PF Tier 1 rates shall be equal in all
> hours of the year for the term of this Agreement. The megawatt amounts
> of such power for each Heavy Load Hour (HLH) and each Light Load Hour
> (LLH) shall equal the annual average megawatt amount established in
> section 1.1 above.
>
> *End Option 1*
>
> *[Option 2]{.underline}: Include if customer chooses a block shaped to
> their Monthly Net Requirement:*

1.2 **Block Shaped to Net Requirement**

> The amounts of Firm Requirements Power priced at PF Tier 1 rates for
> each month, and for each Heavy Load Hour (HLH) and each Light Load
> Hour (LLH) within each month, are established as follows:
>
> 1.2.1 **Amounts Each Month**
>
> 1.2.1.1 **Determination of Monthly Distribution Factors**
>
> BPA shall use «Customer Name»'s Monthly Distribution Factors, to be
> listed below, to calculate the monthly amount of Firm Requirements
> Power priced at PF Tier 1 rates. BPA shall establish «Customer Name»'s
> Monthly Distribution Factors by applying the following formula for
> each month:

  ---- ----------- ---- ------------ ------ ------------- ---- ------------- ----
  \[   Monthly     \-   Monthly      \] ÷   Sum of the    \-   Sum of the    \]
       load in MWh      resources in \[     monthly loads      monthly       
                        MWh                 in MWh             resources in  
                                                               MWh           

  ---- ----------- ---- ------------ ------ ------------- ---- ------------- ----

> For this calculation:
>
> "Load" means «Customer Name»'s measured FY 2010 Total Retail Load
> adjusted for use in determining «Customer Name»'s CHWM, pursuant to
> the TRM, and
>
> "Resources" means «Customer Name»'s Existing Resources as defined in
> the TRM.
>
> By September 15, 2011, BPA shall update the table below with «Customer
> Name»'s Monthly Distribution Factors. These Monthly Distribution
> Factors shall not change for the term of this Agreement.
>
> ***[Drafter's Note]{.underline}: Leave table blank at contract
> signing:***

  -------------- --------- --------- --------- --------- --------- --------- --------- --------- --------- --------- --------- -----------
  **Monthly                                                                                                                    
  Distribution                                                                                                                 
  Factors**                                                                                                                    

  **Oct**        **Nov**   **Dec**   **Jan**   **Feb**   **Mar**   **Apr**   **May**   **Jun**   **Jul**   **Aug**   **Sep**   **Total**

                                                                                                                               1.000

  Note: Round                                                                                                                  
  the factors in                                                                                                               
  the table                                                                                                                    
  above to three                                                                                                               
  decimal                                                                                                                      
  places.                                                                                                                      
  -------------- --------- --------- --------- --------- --------- --------- --------- --------- --------- --------- --------- -----------

> 1.2.1.2 **MWh Amounts**
>
> The megawatt-hours priced at PF Tier 1 rates each month shall equal:

  ---- ---------------- ------- ------------ ------ ---------------------- ----
  \[   annual aMW       \] × \[ total number \] ×   «Customer Name»'s      \]
       priced at PF             of hours in  \[     Monthly Distribution   
       Tier 1 from              Fiscal Year         Factor from            
       section 1.1                                  section 1.2.1.1 for    
                                                    each month             

  ---- ---------------- ------- ------------ ------ ---------------------- ----

> *[Sub-Option 1]{.underline}: Include if customer chooses a flat block
> within each month:*
>
> 1.2.2 **Amounts Within Each Month**
>
> Except for amounts specified in section 1.4 below, amounts of Firm
> Requirements Power priced at PF Tier 1 rates within each month shall
> be the same for all hours of the month. The megawatt amount of such
> power for each HLH and each LLH is the total megawatt-hours in the
> month as established in section 1.2.1.2 above divided by the number of
> hours in the month.
>
> *End Sub-Option 1*
>
> *[Sub-Option 2]{.underline}: Include if customer chooses a block that
> is shaped to their Net Requirement up to 60% HLH within each month:*
>
> 1.2.2 **Amounts Within Each Month**
>
> 1.2.2.1 **Determination of Diurnal Distribution Factors**
>
> BPA shall use «Customer Name»'s Diurnal Distribution Factors, to be
> listed below, to calculate the amount of Firm Requirements Power
> priced at PF Tier 1 rates for each HLH and each LLH within each month.
> BPA shall establish «Customer Name»'s Diurnal Distribution Factors as
> follows:
>
> The HLH Distribution Factor for each month shall equal the lesser of
> 0.6 or:

  ---- ----------- ---- ------------ ------- ------------- ---- ------------- ----
  \[   Monthly HLH \-   Monthly HLH  \] ÷ \[ Monthly HLH   \-   Monthly HLH   \]
       load in MWh      resources in         and LLH load       and LLH       
                        MWh                  in MWh             resources in  
                                                                MWh           

  ---- ----------- ---- ------------ ------- ------------- ---- ------------- ----

> For this calculation:
>
> "Load" means «Customer Name»'s measured FY 2010 Total Retail Load
> adjusted for use in determining «Customer Name»'s CHWM, pursuant to
> the TRM, and
>
> "Resources" means «Customer Name»'s Existing Resources as defined in
> the TRM.
>
> The LLH Distribution Factor for each month shall equal one minus that
> month's HLH Distribution Factor. By September 15, 2011, BPA shall
> update the table below with «Customer Name»'s Diurnal Distribution
> Factors. These Diurnal Distribution Factors shall not change for the
> term of this Agreement.
>
> *[Drafter's Note]{.underline}*: Leave table blank at contract signing:

  -------------- --------- --------- --------- --------- --------- --------- --------- --------- --------- --------- --------- ---------
  **Diurnal                                                                                                                    
  Distribution                                                                                                                 
  Factors**                                                                                                                    

                 **Oct**   **Nov**   **Dec**   **Jan**   **Feb**   **Mar**   **Apr**   **May**   **Jun**   **Jul**   **Aug**   **Sep**

  **HLH**                                                                                                                      

  **LLH**                                                                                                                      

  **Total**      1.000     1.000     1.000     1.000     1.000     1.000     1.000     1.000     1.000     1.000     1.000     1.000

  Note: Round                                                                                                                  
  the factors in                                                                                                               
  the table                                                                                                                    
  above to three                                                                                                               
  decimal                                                                                                                      
  places.                                                                                                                      
  -------------- --------- --------- --------- --------- --------- --------- --------- --------- --------- --------- --------- ---------

> 1.2.2.2 **HLH and LLH Amounts**
>
> Except for amounts specified in section 1.4 below, the megawatt amount
> of Firm Requirements Power for each HLH of each month is:

  ---- ------------------- ------ ---------------------- ------ ----------- ----
  \[   total MWh in month  \] ×   HLH Diurnal            \] ÷   HLH in      \]
       from section        \[     Distribution Factor    \[     month       
       1.2.1.2                    for month from section                    
                                  1.2.2.1                                   

  ---- ------------------- ------ ---------------------- ------ ----------- ----

> The megawatt amount of Firm Requirements Power for each LLH of each
> month is:

  ---- ------------------- ------ ---------------------- ------- --------- ----
  \[   total MWh in month  \] ×   LLH Diurnal            \] ÷ \[ LLH in    \]
       from section        \[     Distribution Factor            month     
       1.2.1.2                    for month from section                   
                                  1.2.2.1                                  

  ---- ------------------- ------ ---------------------- ------- --------- ----

> *End Sub-Option 2*

*End Option 2 for Block shaped to Net Requirement*

1.3 **Current Tier 1 Block**

By September 15, 2011, and by September 15 of each Fiscal Year
thereafter, BPA shall update the table below with whole megawatt amounts
of Firm Requirements Power priced at PF Tier 1 rates for the upcoming
Fiscal Year as established according to sections 1.1 and 1.2 above.

> *[Drafter's Note]{.underline}*: Leave table blank at signing:

  ---------------------------------------------------------------------------------------------------------------------------------------------------------
  **Tier 1 Monthly                                                                                                                                
  Block Amounts                                                                                                                                   
  (MW/hr)**                                                                                                                                       
  --------------------- ----------- --------- --------- --------- --------- --------- --------- --------- --------- --------- --------- --------- ---------
  **Fiscal Year**       **Diurnal   **Oct**   **Nov**   **Dec**   **Jan**   **Feb**   **Mar**   **Apr**   **May**   **Jun**   **Jul**   **Aug**   **Sep**
                        Period**                                                                                                                  

  2012                  **HLH**                                                                                                                   

                        **LLH**                                                                                                                   

  2013                  **HLH**                                                                                                                   

                        **LLH**                                                                                                                   

  2014                  **HLH**                                                                                                                   

                        **LLH**                                                                                                                   

  2015                  **HLH**                                                                                                                   

                        **LLH**                                                                                                                   

  2016                  **HLH**                                                                                                                   

                        **LLH**                                                                                                                   

  2017                  **HLH**                                                                                                                   

                        **LLH**                                                                                                                   

  2018                  **HLH**                                                                                                                   

                        **LLH**                                                                                                                   

  2019                  **HLH**                                                                                                                   

                        **LLH**                                                                                                                   

  2020                  **HLH**                                                                                                                   

                        **LLH**                                                                                                                   

  2021                  **HLH**                                                                                                                   

                        **LLH**                                                                                                                   

  2022                  **HLH**                                                                                                                   

                        **LLH**                                                                                                                   

  2023                  **HLH**                                                                                                                   

                        **LLH**                                                                                                                   

  2024                  **HLH**                                                                                                                   

                        **LLH**                                                                                                                   

  2025                  **HLH**                                                                                                                   

                        **LLH**                                                                                                                   

  2026                  **HLH**                                                                                                                   

                        **LLH**                                                                                                                   

  2027                  **HLH**                                                                                                                   

                        **LLH**                                                                                                                   

  2028                  **HLH**                                                                                                                   

                        **LLH**                                                                                                                   

  Note: Round the                                                                                                                                 
  megawatt-per-hour                                                                                                                               
  amounts in the table                                                                                                                            
  above to whole                                                                                                                                  
  megawatts-per-hour.                                                                                                                             
  ---------------------------------------------------------------------------------------------------------------------------------------------------------

*[Option 1]{.underline}: Include if customer [does not]{.underline}
purchase Shaping Capacity:*

1.4 **Shaping Capacity**

> «Customer Name» is not purchasing any amount of Shaping Capacity.

*End Option 1*

*[Option 2]{.underline}: Include if customer is purchasing Shaping
Capacity:*

1.4 **Shaping Capacity** ***(05/27/08 Version)***

> 1.4.1 **Amounts**
>
> BPA shall establish amounts of Shaping Capacity for each month by
> applying the following formula for each month:

  ---- ------------ --- ------------- ----- -------------- ------ ------------- ----
  \[   FY 2010                        \] ×  FY 2012 HLH    \] -   FY 2012 HLH   \]
       monthly peak                   \[    block amount   \[     block amount  
       in MW                                from section          from section  
                                            1.3                   1.3           

       Monthly HLH  ÷   HLH in month                                            
       load in MWh      during FY2010                                           
  ---- ------------ --- ------------- ----- -------------- ------ ------------- ----

> For this calculation:
>
> "Monthly HLH load" means the HLH load portion of «Customer Name»'s
> measured FY 2010 Total Retail Load adjusted for use in determining
> «Customer Name»'s CHWM, pursuant to the TRM, and
>
> "FY 2010 monthly peak" means «Customer Name»'s FY 2010 customer system
> peak for the month.
>
> By September 15, 2011, BPA shall update the table below with «Customer
> Name»'s amounts of Shaping Capacity in whole megawatts. These amounts
> shall not change for the term of this Agreement except as specified in
> section 1.4.3 below. «Customer Name» shall pay for the full amount of
> Shaping Capacity megawatts listed below whether or not «Customer Name»
> used such Shaping Capacity.
>
> *[Drafter's Note]{.underline}*: Leave table blank at contract signing:

  ------------ --------- --------- --------- --------- --------- --------- --------- --------- --------- --------- --------- ---------
  **Monthly                                                                                                                  
  Shaping                                                                                                                    
  Capacity                                                                                                                   
  Amounts                                                                                                                    
  (MW)**                                                                                                                     

               **Oct**   **Nov**   **Dec**   **Jan**   **Feb**   **Mar**   **Apr**   **May**   **Jun**   **Jul**   **Aug**   **Sep**

  **HLH**                                                                                                                    

  Note: Round                                                                                                                
  the megawatt                                                                                                               
  amounts in                                                                                                                 
  the table                                                                                                                  
  above to                                                                                                                   
  whole                                                                                                                      
  megawatts.                                                                                                                 
  ------------ --------- --------- --------- --------- --------- --------- --------- --------- --------- --------- --------- ---------

> 1.4.2 **Scheduling Shaping Capacity**
>
> \(1\) «Customer Name» may preschedule for any HLH any amount that is
> greater than or less than the block amount listed above in section 1.3
> within the Shaping Capacity amounts listed in section 1.4.1 above. For
> the HLH period each day, «Customer Name» shall preschedule an average
> megawatt amount equal to the HLH block megawatt amount stated in
> section 1.3 above.
>
> \(2\) When using Shaping Capacity, «Customer Name» shall preschedule
> according to Exhibit F, Scheduling.
>
> 1.4.3 **Additional Provisions**
>
> \(1\) BPA shall limit the amounts of Shaping Capacity megawatts listed
> in section 1.4.1 above for any month(s) where «Customer Name»'s
> monthly peaking Net Requirement listed in section 1.2 of Exhibit A,
> Net Requirements and Resources, is less than the sum of:
>
> \(A\) «Customer Name»'s monthly HLH PF Tier 1 rate purchase amount
> listed in section 1.3 above,
>
> \(B\) «Customer Name»'s monthly PF Tier 2 rate purchase amount
> established in section 2 below, and
>
> \(C\) the monthly Shaping Capacity amounts listed in section 1.4.1
> above.
>
> \(2\) If BPA determines that the Shaping Capacity amount for all
> customers purchasing Shaping Capacity exceeds 200 aMW in any month,
> BPA may unilaterally amend this exhibit to add limits for such months
> to the amounts that prescheduled megawatts can vary from one hour to
> the next.

*End Option 2 for Shaping Capacity*

*END **BLOCK** template.*

*Include in **SLICE/BLOCK** template:*

**1. FIRM REQUIREMENTS POWER AT PF TIER 1*(05/27/08 Version)***

*END **SLICE/BLOCK** template.*

**2. FIRM REQUIREMENTS POWER AT PF TIER 2*(06/13/08 Version)***

2.1 **Notice to Purchase Zero Amounts at PF Tier 2 Rates**

> If «Customer Name» elects not to purchase Firm Requirements Power at
> PF Tier 2 rates for a Purchase Period as established in section 9 of
> the body of this Agreement, by March 31 immediately following the
> corresponding Notice Deadline, BPA shall update this exhibit to
> indicate such election by adding an "X" to the applicable cell in the
> following table. Such election means that for the Purchase Period
> specified below, «Customer Name» shall: (1) purchase zero amounts of
> Firm Requirements Power at PF Tier 2 rates, and (2) apply its
> Dedicated Resources to serve all of «Customer Name»'s Above-RHWM Load.
>
> *[Drafter's Note]{.underline}: Leave table blank at contract signing:*

  -----------------------------------------------------------------------
  **Zero PF Tier 2**              **Purchase Period**
  ------------------------------- ---------------------------------------
                                  FY 2012 - FY 2014

                                  FY 2015 - FY 2019

                                  FY 2020 - FY 2024

                                  FY 2025 - FY 2028

  Indicate Election with an \"X\" 
  -----------------------------------------------------------------------

*Include in **LOAD FOLLOWING** template:*

2.2 **PF Tier 2 Load-Growth Rate**

> 2.2.1 **First Election Opportunity**
>
> If «Customer Name» elects by the first Notice Deadline (November 1,
> 2009) to purchase Firm Requirements Power at the PF Tier 2 Load-Growth
> Rate starting October 1, 2011, in its election «Customer Name» shall
> elect one of the three PF Tier 2 Load-Growth Rate options listed in
> section 2.2.3 below. If «Customer Name» elects Option 3, «Customer
> Name» shall state the amounts to be listed in the table in
> section 2.2.3.3 below and «Customer Name»'s PF Tier 2 Short-Term Rate
> election pursuant to section 2.4.1 below. BPA shall amend this exhibit
> by March 31, 2010 to indicate «Customer Name»'s election by adding an
> "X" to the "1^st^ Notice Deadline" box next to the applicable option
> below. If «Customer Name» does not elect to purchase Firm Requirements
> Power at the PF Tier 2 Load-Growth Rate by the first Notice Deadline,
> then «Customer Name» shall not have the right to purchase Firm
> Requirements Power at the PF Tier 2 Load-Growth Rate during the first
> Purchase Period.
>
> 2.2.2 **Second Election Opportunity**
>
> 2.2.2.1 If «Customer Name» does not elect to purchase Firm
> Requirements Power at the PF Tier 2 Load-Growth Rate starting the
> first Purchase Period, «Customer Name» may purchase Firm Requirements
> Power at a PF Tier 2 Load-Growth Rate starting October 1, 2014,
> provided:
>
> \(1\) any elections of rate alternatives or resource additions given
> to BPA under this Agreement shall continue to be applicable, and
>
> \(2\) the PF Tier 2 Load-Growth Rate applicable under this election
> may not be the same PF Tier 2 Load-Growth Rate that was available
> during the first Purchase Period.
>
> 2.2.2.2 If «Customer Name» elects by the second Notice Deadline
> (September 30, 2011) to purchase Firm Requirements Power at a PF
> Tier 2 Load-Growth Rate, in its election «Customer Name» shall elect
> one of the three PF Tier 2 Load-Growth Rate options listed in
> section 2.2.3 below. In such case, «Customer Name» shall purchase Firm
> Requirements Power at the PF Tier 2 Load-Growth Rate under such
> elected option starting October 1, 2014.
>
> 2.2.2.3 If «Customer Name» elects Option 3, described in
> section 2.2.3.3 below, «Customer Name» shall state the amounts to be
> listed in the table in section 2.2.3.3 below and «Customer Name»'s PF
> Tier 2 Short-Term Rate election pursuant to section 2.4.1 below. If
> «Customer Name» has prior elections of rate alternatives or resource
> additions that extend beyond the first Purchase Period, «Customer
> Name» shall not have the right to elect Options 1 or 2 below. In such
> case, «Customer Name» shall elect Option 3 and the amounts listed in
> the table in section 2.2.3.3 below shall not be less than the sum of
> «Customer Name»'s prior elections for each year.
>
> 2.2.2.4 BPA shall amend this exhibit by March 31, 2012, to indicate
> «Customer Name»'s election by adding an "X" to the "2^nd^ Notice
> Deadline" box next to the applicable option below. If «Customer Name»
> does not elect to purchase Firm Requirements Power at the PF Tier 2
> Load-Growth Rate by the second Notice Deadline, then «Customer Name»
> shall not have the right to purchase Firm Requirements Power at the PF
> Tier 2 Load-Growth Rate for the term of this Agreement.
>
> 2.2.3 **PF Tier 2 Load-Growth Rate Options**
>
> 2.2.3.1 **Option 1 - Full PF Tier 2 Load-Growth Rate**
>
> «Customer Name» shall purchase Firm Requirements Power under the PF
> Tier 2 Load-Growth Rate for all of «Customer Name»'s Above-RHWM Load.
>
> 2.2.3.2 **Option 2 - Shared Rate Plan**
>
> \(1\) **Obligation**
>
> Provided that BPA determines «Customer Name» qualifies under the limit
> for the Shared Rate Plan as established in section 7 of the TRM,
> «Customer Name» shall pay rates under the Shared Rate Plan for Firm
> Requirements Power purchased under this Agreement. If BPA determines
> «Customer Name» does not qualify under such limit, «Customer Name»
> shall not have the right to elect this option and «Customer Name»
> shall purchase Firm Requirements Power at the PF Tier 2 Load-Growth
> Rate under Option 1 as established in 2.2.3.1 above. For the second
> election opportunity stated in section 2.2.2 above, availability under
> the limit for the Shared Rate Plan established in section 7 of the TRM
> shall equal such limit minus the amounts used by other customers who
> elected this Option 2 by the first Notice Deadline.
>
> \(2\) **Terminating Participation**
>
> «Customer Name» may stop participation in the Shared Rate Plan if
> «Customer Name» notifies BPA in writing by March 31 of a Forecast
> Year. In such case, the change shall be effective the next Rate
> Period. If «Customer Name» stops participation in the Shared Rate
> Plan, «Customer Name» shall not have the right to resume
> participation. «Customer Name» shall continue to purchase Firm
> Requirements Power priced at the PF Tier 2 Load-Growth Rate for all of
> «Customer Name»'s Above-RHWM Load.
>
> 2.2.3.3 **Option 3 -- Partial PF Tier 2 Load-Growth Rate**
>
> «Customer Name» shall purchase Firm Requirements Power under the PF
> Tier 2 Load-Growth Rate for all of «Customer Name»'s Above-RHWM Load
> minus the amounts stated in the table below that «Customer Name»
> elects are not subject to the PF Tier 2 Load-Growth Rate. «Customer
> Name» shall establish such amounts at the time «Customer Name» elects
> this option and such amounts shall not change for the term of this
> Agreement. «Customer Name» may serve such amounts with Dedicated
> Resources or with Firm Requirements Power purchased at other PF Tier 2
> rates. BPA shall update the table below by March 31 immediately
> following «Customer Name»'s election of this option.
>
> *[Drafter's Note]{.underline}: Leave table blank at contract signing:*

  ------------------------------------------------------------------------------
  **Load Amounts                                                          
  Not Subject To                                                          
  PF Tier 2                                                               
  Load-Growth                                                             
  Rate (aMW)**                                                            
  --------------- ------ ------ ------ ------ ------ ------ ------ ------ ------
  **Fiscal Year** 2012   2013   2014   2015   2016   2017   2018   2019   2020

  **Annual aMW**                                                          

  **Fiscal Year** 2021   2022   2023   2024   2025   2026   2027   2028   

  **Annual aMW**                                                          

  Note: Fill in                                                           
  the table above                                                         
  with annual                                                             
  average                                                                 
  megawatts                                                               
  rounded to                                                              
  three decimal                                                           
  places.                                                                 
  ------------------------------------------------------------------------------

*END **LOAD FOLLOWING** template.*

*Include in **BLOCK** and **SLICE/BLOCK** templates:*

2.2 **PF Tier 2 Load-Growth Rate**

> «Customer Name» shall not have the right to purchase Firm Requirements
> Power at the Load-Growth Rate for the term of this Agreement.

*END **BLOCK** and **SLICE/BLOCK** templates.*

*Include in **LOAD FOLLOWING** template:*

> 2.3 **PF Tier 2 Vintage Rate(s)**
>
> If «Customer Name» elects Option 1 or 2 in section 2.2.3 above, then
> this section shall not apply. Otherwise:
>
> 2.3.1 If BPA makes Firm Requirements Power available at one or more PF
> Tier 2 Vintage Rates, «Customer Name» may purchase amounts of such
> power, subject to section 2.4.2 below, only if and up to the megawatt
> amount that «Customer Name» has purchased Firm Requirements Power from
> BPA at the PF Tier 2 Short-Term Rate. If «Customer Name» elects to
> purchase Firm Requirements Power from BPA at a PF Tier 2 Vintage Rate,
> «Customer Name» shall sign a Statement of Intent offered by BPA.
> "Statement of Intent" means a statement prepared by BPA and signed by
> «Customer Name» that «Customer Name» shall purchase Firm Requirements
> Power at a specific rate, subject to section 2.3.2 below, based on the
> costs of a resource to be acquired by BPA as set in each general rate
> case. A signed Statement of Intent from «Customer Name» specifying the
> amount and term of the purchase is necessary before BPA will acquire
> any cost-effective resource on a long-term basis to serve load under a
> PF Tier 2 Vintage Rate.
>
> 2.3.2 If BPA establishes the PF Tier 2 Vintage Rate consistent with
> the Statement of Intent, «Customer Name» agrees to have the portion of
> its PF Tier 2 rate power purchase specified in the Statement of
> Intent, priced at that rate. If BPA is unable to establish the PF
> Tier 2 Vintage Rate, «Customer Name» agrees to purchase such amount of
> Firm Requirements Power at the PF Tier 2 Short-Term Rate.
>
> 2.3.3 If «Customer Name» purchases Firm Requirements Power at a PF
> Tier 2 Vintage Rate, BPA shall insert applicable tables, terms, and
> conditions for each Vintage rate here.

*END **LOAD FOLLOWING** template.*

*Include in **BLOCK** and **SLICE/BLOCK** templates:*

> 2.3 **PF Tier 2 Vintage Rate(s)**
>
> *[Reviewers Note]{.underline}: Shaded text is identical to Load
> Following (absent the first sentence)*
>
> 2.3.1 If BPA makes Firm Requirements Power available at one or more PF
> Tier 2 Vintage Rates, «Customer Name» may purchase amounts of such
> power, subject to section 2.4.2 below, only if and up to the megawatt
> amount that «Customer Name» has purchased Firm Requirements Power from
> BPA at the PF Tier 2 Short-Term Rate. If «Customer Name» elects to
> purchase Firm Requirements Power from BPA at a PF Tier 2 Vintage Rate,
> «Customer Name» shall sign a Statement of Intent offered by BPA.
> "Statement of Intent" means a statement prepared by BPA and signed by
> «Customer Name» that «Customer Name» shall purchase Firm Requirements
> Power at a specific rate, subject to section 2.3.2 below, based on the
> costs of a resource to be acquired by BPA as set in each general rate
> case. A signed Statement of Intent from «Customer Name» specifying the
> amount and term of the purchase is necessary before BPA will acquire
> any cost-effective resource on a long-term basis to serve load under a
> PF Tier 2 Vintage Rate.
>
> 2.3.2 If BPA establishes the PF Tier 2 Vintage Rate consistent with
> the Statement of Intent, «Customer Name» agrees to have the portion of
> its PF Tier 2 rate power purchase specified in the Statement of
> Intent, priced at that rate. If BPA is unable to establish the PF
> Tier 2 Vintage Rate, «Customer Name» agrees to purchase such amount of
> Firm Requirements Power at the PF Tier 2 Short-Term Rate.
>
> 2.3.3 If «Customer Name» purchases Firm Requirements Power at a PF
> Tier 2 Vintage Rate, BPA shall insert applicable tables, terms, and
> conditions for each Vintage rate here.

*END **BLOCK** and **SLICE/BLOCK** templates.*

*Include in **LOAD FOLLOWING** template:*

2.4 **PF Tier 2 Short-Term Rate**

> If «Customer Name» elects Option 1 or 2 in section 2.2.3 above, then
> this section shall not apply. Otherwise:
>
> 2.4.1 **Short-Term Rate Purchases**
>
> Unless «Customer Name» elects, in section 2.1 above, not to purchase
> Firm Requirements Power at PF Tier 2 rates for a given Purchase
> Period, by each Notice Deadline «Customer Name» shall elect in writing
> either alternative (A) or (B) below for the duration of the
> corresponding Purchase Period. If «Customer Name» elects alternative
> (A) and elects to apply Dedicated Resources to serve its Above-RHWM
> Load, «Customer Name» shall state the amounts to be listed in the
> table in section 2.4.1.1(2) below. If «Customer Name» elects
> alternative (B), «Customer Name» shall state the amounts to be listed
> in the table in 2.4.1.3 below. By March 31 immediately following each
> Notice Deadline, BPA shall update the tables in this section 2.4.1 to
> show «Customer Name»'s PF Tier 2 Short-Term Rate election for the
> corresponding Purchase Period.
>
> 2.4.1.1 **Alternative A -- Customer Planned Load Not Otherwise
> Served**
>
> «Customer Name» shall purchase Firm Requirements Power priced at the
> PF Tier 2 Short-Term Rate to serve all of «Customer Name»'s Above-RHWM
> Load that «Customer Name» has not otherwise agreed to serve with:
>
> \(1\) Firm Requirements Power purchased at other PF Tier 2 rates, or
>
> \(2\) the amounts of Dedicated Resources, stated in the table below,
> that «Customer Name» shall apply during the Purchase Period to serve
> its Above-RHWM Load. If «Customer Name» purchases power at the PF
> Tier 2 Load-Growth Rate, these Dedicated Resource amounts shall not
> exceed the amounts stated in the table in section 2.2.3.3 above.
> «Customer Name» shall apply the amounts of Dedicated Resources stated
> below pursuant to section 3.3 of the body of this Agreement.
>
> *[Drafter's Note]{.underline}*: Leave table blank at contract signing:

  -------------------------------------------------------------------------
  **Purchase Period                                               
  non-Federal Resource                                            
  Elections**                                                     
  ----------------------- --------- --------- --------- --------- ---------
  **Fiscal Year**         2012      2013      2014      2015      2016

  **Election**                                                    

                                                                  

  **Fiscal Year**         2017      2018      2019      2020      2021

  **Election**                                                    

                                                                  

  **Fiscal Year**         2022      2023      2024      2025      2026

  **Election**                                                    

                                                                  

  **Fiscal Year**         2027      2028                          

  **Election**                                                    

  Note:                                                           

  Insert amounts in aMW                                           
  rounded to three                                                
  decimal places for each                                         
  year of the applicable                                          
  Purchase Period.                                                
  -------------------------------------------------------------------------

> 2.4.1.2 **Alternative B -- Limited Amounts**
>
> «Customer Name» shall purchase Firm Requirements Power priced at the
> PF Tier 2 Short-Term Rate to serve «Customer Name»'s Above-RHWM Load
> that «Customer Name» has not otherwise agreed to serve with Firm
> Requirements Power purchased at other PF Tier 2 rates; provided
> however, that amounts purchased at the PF Tier 2 Short-Term Rate shall
> not exceed the amounts (including zero amounts) stated in the table in
> section 2.4.1.3 below. «Customer Name» agrees to apply, pursuant to
> section 3.3 of the body of this Agreement, any amount of Dedicated
> Resources to serve all of «Customer Name»'s Above-RHWM Load that BPA
> is not serving with Firm Requirements Power.
>
> 2.4.1.3 **PF Tier 2 Short-Term Rate Elections**
>
> If «Customer Name» elects alternative (A) above, BPA shall indicate
> that election by adding an "X" to the table below for each year of the
> applicable Purchase Period. If «Customer Name» elects alternative (B)
> above, BPA shall indicate that election by adding amounts (in aMW
> rounded to three decimal places) to the table below for each year of
> the applicable Purchase Period.
>
> *[Drafter's Note]{.underline}: Leave table blank at contract signing:*

  -------------------------------------------------------------------------
  **PF Tier 2 Short-Term                                          
  Rate Table**                                                    
  ----------------------- --------- --------- --------- --------- ---------
  **Fiscal Year**         2012      2013      2014      2015      2016

  **Election**                                                    

                                                                  

  **Fiscal Year**         2017      2018      2019      2020      2021

  **Election**                                                    

                                                                  

  **Fiscal Year**         2022      2023      2024      2025      2026

  **Election**                                                    

                                                                  

  **Fiscal Year**         2027      2028                          

  **Election**                                                    
  -------------------------------------------------------------------------

> 2.4.2 **Conversion to PF Tier 2 Vintage Rates**
>
> 2.4.2.1 **Right to Convert**
>
> Subject to the amounts of power available under PF Tier 2 Vintage
> Rates offered by BPA, «Customer Name» shall have the right to convert
> only those amounts of Firm Requirements Power it purchases at the PF
> Tier 2 Short-Term Rate to an equivalent purchase amount at a PF Tier 2
> Vintage Rate.
>
> 2.4.2.2 **Conversion Costs**
>
> Upon establishment of a PF Tier 2 Vintage Rate for which «Customer
> Name» signed a Statement of Intent, «Customer Name» shall be liable
> for payment of any outstanding costs under the PF Tier 2 Short-Term
> Rate that apply to «Customer Name». BPA shall determine such costs, if
> any, in the first general rate case that establishes the applicable PF
> Tier 2 Vintage Rate(s). In no event shall BPA make payment to
> «Customer Name» as a result of «Customer Name»'s conversion of
> purchase amounts at the PF Short-Term Rate to purchase amounts at a PF
> Tier 2 Vintage Rate(s).
>
> 2.4.2.3 **Exhibit Updates**
>
> By September 15 immediately following the establishment of a PF Tier 2
> Vintage Rate for which «Customer Name» signed a Statement of Intent,
> BPA shall amend this exhibit to show «Customer Name»'s PF Tier 2
> Vintage Rate purchase amounts and remove «Customer Name»'s PF Tier 2
> Short-Term Rate purchases by the amounts purchased at the PF Tier 2
> Vintage Rate.
>
> 2.4.3 **Right to Reduce PF Tier 2 Short-Term Rate Purchase Amounts**
>
> 2.4.3.1 **Notice**
>
> If «Customer Name» notifies BPA in writing by October 31 of a Rate
> Case Year, «Customer Name» may reduce, in equal amounts for all hours
> of the year, some or all of the amounts of Firm Requirements Power
> that «Customer Name» is obligated to purchase at the PF Tier 2
> Short-Term Rate. The reduction may be effective any time during the
> following Rate Period and shall be effective for the remaining
> duration of the applicable Purchase Period(s). In its written notice,
> «Customer Name» shall state the amount of the reduction and the date
> the reduction shall take effect. «Customer Name» shall replace all
> reduced PF Tier 2 Short-Term Rate purchase amounts with amounts of
> Dedicated Resources applied pursuant to section 3.3 of the body of
> this Agreement.
>
> 2.4.3.2 **Charges to Reduce Purchase Amounts**
>
> «Customer Name» shall be liable for payment of any costs that apply as
> a result of «Customer Name» reducing, under section 2.4.3.1 above, the
> amounts of Firm Requirements Power that «Customer Name» is obligated
> to purchase at the PF Tier 2 Short-Term Rate. Such costs shall be
> those that BPA: (1) has incurred and will not recover from «Customer
> Name» as a result of the reduction, and (2) is unable to recover
> through market transactions. BPA shall determine such costs, if any,
> during the general rate case that follows «Customer Name»'s notice. If
> BPA determines that «Customer Name» owes payment for such costs,
> «Customer Name» shall pay BPA in 24 equal monthly amounts starting the
> first month of the next Rate Period. In no event shall BPA make
> payment to «Customer Name» as a result of «Customer Name» reducing the
> amounts of Firm Requirements Power that «Customer Name» is obligated
> to purchase at the PF Tier 2 Short-Term Rate.
>
> 2.4.3.3 **Exhibit Updates**
>
> By March 31 following «Customer Name»'s notice, BPA shall amend this
> exhibit and Exhibit A, Net Requirements and Resources, to show
> «Customer Name»'s reduced PF Tier 2 Short-Term Rate purchase amounts
> and «Customer Name»'s Dedicated Resource additions.

*END **LOAD FOLLOWING** template.*

*Include in **BLOCK** and **SLICE/BLOCK** templates:*

2.4 **PF Tier 2 Short-Term Rate**

> 2.4.1 **Short-Term Rate Purchases**
>
> If «Customer Name» elects by a Notice Deadline to purchase Firm
> Requirements Power at the PF Tier 2 Short-Term Rate for a Purchase
> Period, in its election «Customer Name» shall state its purchase
> amounts of such power for each year of the corresponding Purchase
> Period. By March 31 immediately following each Notice Deadline, BPA
> shall update the table below to show «Customer Name»'s purchase
> amounts, if any, at the PF Tier 2 Short-Term Rate for the
> corresponding Purchase Period.
>
> *[Drafter's Note]{.underline}: Leave table blank at contract signing:*

  ---------------------------------------------------------------------------
  **PF Tier 2 Short-Term                                            
  Rate Table**                                                      
  ------------------------- --------- --------- --------- --------- ---------
  **Fiscal Year**           2012      2013      2014      2015      2016

  **aMW**                                                           

                                                                    

  **Fiscal Year**           2017      2018      2019      2020      2021

  **aMW**                                                           

                                                                    

  **Fiscal Year**           2022      2023      2024      2025      2026

  **aMW**                                                           

                                                                    

  **Fiscal Year**           2027      2028                          

  **aMW**                                                           

  Note: Insert whole                                                
  megawatt amounts for each                                         
  year of the applicable                                            
  Purchase Period.                                                  
  ---------------------------------------------------------------------------

> 2.4.2 **Conversion to PF Tier 2 Vintage Rates**
>
> *[Reviewers Note]{.underline}: Shaded text is identical to Load
> Following text:*
>
> 2.4.2.1 **Right to Convert**
>
> Subject to the amounts of power available under PF Tier 2 Vintage
> Rates offered by BPA, «Customer Name» shall have the right to convert
> only those amounts of Firm Requirements Power it purchases at the PF
> Tier 2 Short-Term Rate to an equivalent purchase amount at a PF Tier 2
> Vintage Rate.
>
> 2.4.2.2 **Conversion Costs**
>
> Upon establishment of a Vintage Rate for which «Customer Name» signed
> a Statement of Intent, «Customer Name» shall be liable for payment of
> any outstanding costs under the PF Tier 2 Short-Term Rate that apply
> to «Customer Name». BPA shall determine such costs, if any, in the
> first general rate case that establishes the applicable PF Tier 2
> Vintage Rate(s). In no event shall BPA make payment to «Customer Name»
> as a result of «Customer Name»'s conversion of purchase amounts at the
> PF Short-Term Rate to purchase amounts at a PF Tier 2 Vintage Rate(s).
>
> 2.4.2.3 **Exhibit Updates**
>
> By September 15 immediately following the establishment of a Tier 2
> Vintage Rate for which «Customer Name» signed a Statement of Intent,
> BPA shall amend this exhibit to show «Customer Name»'s PF Tier 2
> Vintage Rate purchase amounts and remove «Customer Name»'s PF Tier 2
> Short-Term Rate purchases by the amounts purchased at the PF Tier 2
> Vintage Rate.

*END **BLOCK** and **SLICE/BLOCK** templates.*

*Include in **LOAD FOLLOWING** template:*

> *[Reviewer's Note]{.underline}: See "Timeline for HWMs & Above-RHWM
> Elections"*

2.5 **Amounts of Power to be Billed at PF Tier 2 Rates**

> 2.5.1 **Treatment for FY 2012 -- FY 2013**
>
> By March 31, 2010, BPA shall update the table in section 2.5.2 below
> with «Customer Name»'s forecasted purchase amounts of Firm
> Requirements Power which «Customer Name» shall purchase at applicable
> PF Tier 2 rates for the FY 2012 -- FY 2013 Rate Period.
>
> 2.5.2 **Amounts of Power for Subsequent Rate Periods**
>
> For each Rate Period after the FY 2012 -- FY 2013 Rate Period, BPA
> shall establish for the upcoming Rate Period: (1) the planned annual
> average amounts of Firm Requirements Power which «Customer Name» shall
> purchase at applicable PF Tier 2 rates, and (2) any remarketed PF
> Tier 2 rate purchase amounts. By March 31, 2013, and by March 31 of
> each Rate Case Year thereafter, BPA shall update the table below with
> such amounts for each year of the upcoming Rate Period.
>
> *[Drafter's Note]{.underline}: Leave table blank at contract signing:*

<table>
<colgroup>
<col style="width: 26%" />
<col style="width: 8%" />
<col style="width: 8%" />
<col style="width: 8%" />
<col style="width: 8%" />
<col style="width: 8%" />
<col style="width: 8%" />
<col style="width: 8%" />
<col style="width: 8%" />
<col style="width: 8%" />
</colgroup>
<thead>
<tr class="header">
<th colspan="10"><strong>Annual Amounts Priced at PF Tier 2 Rates
(aMW)</strong></th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td><strong>Fiscal Year</strong></td>
<td>2012</td>
<td>2013</td>
<td>2014</td>
<td>2015</td>
<td>2016</td>
<td>2017</td>
<td>2018</td>
<td>2019</td>
<td>2020</td>
</tr>
<tr class="even">
<td><strong>«No Tier 2 at this time»</strong></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td><strong>Remarketed Amounts</strong></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td><strong>Fiscal Year</strong></td>
<td>2021</td>
<td>2022</td>
<td>2023</td>
<td>2024</td>
<td>2025</td>
<td>2026</td>
<td>2027</td>
<td>2028</td>
<td rowspan="3"></td>
</tr>
<tr class="even">
<td><strong>«No Tier 2 at this time»</strong></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td><strong>Remarketed Amounts</strong></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td colspan="10"><p>Notes:</p>
<p>1_ List each applicable Tier 2 rate in the table above. For the first
applicable Tier 2 rate replace <strong>«No Tier 2 at this time»</strong>
with the name of the applicable Tier 2 rate. For each additional Tier 2
rate, add a new row above the <strong>Remarketed Amounts</strong> row.
If «Customer Name» elects not to purchase at Tier 2 rates, leave
<strong>«No Tier 2 at this time»</strong> in the table and leave the
remainder of the table blank.</p>
<p>2_Fill in the table above with annual average megawatts rounded to
three decimal places.</p></td>
</tr>
</tbody>
</table>

*END **LOAD FOLLOWING** template.*

*Include in **BLOCK** and **SLICE/BLOCK** templates:*

> *[Reviewer's Note]{.underline}: See "Timeline for HWMs & Above-RHWM
> Elections"*

2.5 **Amounts of Power to be Billed at Tier 2 Rates**

> Prior to each Fiscal Year BPA shall determine the amounts, if any, of
> Firm Requirements Power at PF Tier 2 rates that need to be remarketed
> subject to section 10 of the body of this Agreement. By September 15
> of each Fiscal year beginning September 15, 2011, BPA shall update the
> table below for the upcoming Fiscal Year with: (1) the annual average
> amounts of Firm Requirements Power which «Customer Name» shall
> purchase at each applicable PF Tier 2 rate, (2) any remarketed PF
> Tier 2 rate purchase amounts, and (3) the total amount of Firm
> Requirements Power priced at PF Tier 2 rates, net of remarketed
> amounts.

*[Drafter's Note]{.underline}*: Leave table blank at contract signing:

<table>
<colgroup>
<col style="width: 26%" />
<col style="width: 8%" />
<col style="width: 8%" />
<col style="width: 8%" />
<col style="width: 8%" />
<col style="width: 8%" />
<col style="width: 8%" />
<col style="width: 8%" />
<col style="width: 8%" />
<col style="width: 8%" />
</colgroup>
<thead>
<tr class="header">
<th colspan="10"><strong>Annual Amounts Priced at PF Tier 2 Rates
(aMW)</strong></th>
</tr>
<tr class="odd">
<th><strong>Fiscal Year</strong></th>
<th>2012</th>
<th>2013</th>
<th>2014</th>
<th>2015</th>
<th>2016</th>
<th>2017</th>
<th>2018</th>
<th>2019</th>
<th>2020</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td><strong>«No Tier 2 at this time»</strong></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td><strong>Minus Remarketed Amounts</strong></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td><strong>Total Amount at Tier 2</strong></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td><strong>Fiscal Year</strong></td>
<td>2021</td>
<td>2022</td>
<td>2023</td>
<td>2024</td>
<td>2025</td>
<td>2026</td>
<td>2027</td>
<td>2028</td>
<td rowspan="4"></td>
</tr>
<tr class="even">
<td><strong>«No Tier 2 at this time»</strong></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td><strong>Minus Remarketed Amounts</strong></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td><strong>Total Amount at Tier 2</strong></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td colspan="10"><p>Notes:</p>
<p>1_ List each applicable Tier 2 rate in the table above. For the first
applicable Tier 2 rate replace <strong>«No Tier 2 at this time»</strong>
with the name of the applicable Tier 2 rate. For each additional Tier 2
rate, add a new row above the <strong>Remarketed Amounts</strong> row.
If «Customer Name» elects not to purchase at Tier 2 rates, leave
<strong>«No Tier 2 at this time»</strong> in the table and leave the
remainder of the table blank.</p>
<p>2_Fill in the table above with whole annual average
megawatts.</p></td>
</tr>
</tbody>
</table>

*END **BLOCK** and **SLICE/BLOCK** templates.*

2.6 **Flat Block**

> Amounts of Firm Requirements Power priced at PF Tier 2 rates shall be
> equal in all hours of the year.

**3. MONTHLY PF RATES*(04/06/08 Version)***

> Applicable monthly PF Tier 1 and PF Tier 2 rates are specified in BPA
> rate schedules.

**4. REVISIONS*(05/27/08 Version)***

> BPA shall revise this exhibit to reflect Customer Name»'s elections
> regarding service to its Above-RHWM Load and BPA's determinations
> under this Agreement.

(PS«X/LOC»- «File Name with Path».DOC) «mm/dd/yy» *{[Drafter's
Note]{.underline}: Insert date of finalized contract here*

**Exhibit D**

**ADDITIONAL PRODUCTS AND SPECIAL PROVISIONS**

**1. CF/CT AND NEW LARGE SINGLE LOADS*(05/25/08 Version)***

> *[Option 1]{.underline}: Include the following if customer has **no**
> CF/CT loads.*
>
> 1.1 **CF/CT Loads**
>
> «Customer Name» has no loads that were contracted for, or committed to
> (CF/CT), as of September 1, 1979, as defined in section 3(13)(A) of
> the Northwest Power Act.
>
> *End Option 1*
>
> *[Option 2]{.underline}: Include the following if customer **has**
> CF/CT loads.*
>
> *[Drafter's Note]{.underline}: If customer has more than one CF/CT,
> number each separately as (1), (2), etc. and indent appropriately.*
>
> 1.1 **CF/CT Loads**
>
> The Administrator has determined that the following loads were
> contracted for, or committed to be served (CF/CT), as of September 1,
> 1979, as defined in section 3(13)(A) of the Northwest Power Act, and
> are subject to the applicable cost-based rate for the rest of
> «Customer Name»'s load:
>
> End-use consumer's name:
>
> Facility name:
>
> Facility location:
>
> Facility description:
>
> Amount of firm energy (megawatts at 100 percent load factor)
> contracted for, or committed to:
>
> *End Option 2*
>
> *[Option 1]{.underline}: Include the following if customer **has no**
> POTENTIAL NLSLs.*
>
> 1.2 **Potential NLSLs**
>
> «Customer Name» has no potential NLSLs.
>
> *End Option 1*
>
> *[Option 2]{.underline}: Include the following if customer **has**
> POTENTIAL NLSL(s).*
>
> *[Drafter's Note]{.underline}: If customer has more than one potential
> NLSL, number each separately as (1), (2), etc. and indent
> appropriately.*
>
> 1.2 **Potential NLSLs**
>
> «Customer Name» has the following potential NLSL(s):
>
> End-use consumer name:
>
> Facility location:
>
> Potential load size:
>
> Date load anticipated:
>
> Description of potential NLSL:
>
> *End Option 2*
>
> 1.3 **Existing NLSLs**
>
> *[Option 1]{.underline}: Include the following if customer **has no**
> existing NLSLs AND DELETE sections 1.3.1 and 1.3.2.*
>
> «Customer Name» has no existing NLSLs.
>
> *End Option 1*

*Include in **LOAD FOLLOWING** template:*

> *[Option 2]{.underline}: Include the following if customer **has** an
> existing NLSL and BPA will serve the NLSL at **NR rate**.*
>
> 1.3.1 **NLSLs*(04/03/08 Version)***
>
> «Customer Name» has an NLSL and elects to have BPA serve the NLSL at
> the NR rate, consistent with section 8, Applicable Rates. The Parties
> shall administer service to the following NLSL consistent with
> section 24.3 of this Agreement. The Parties shall insert a table below
> that establishes the HLH and LLH megawatt amounts.
>
> End--use consumer name:
>
> Facility location:
>
> Date load determined as an NLSL:
>
> Approximate load:
>
> Description of NLSL:
>
> Manner of service:
>
> *End Option 2*
>
> *[Option 3]{.underline}: Include the following if customer **has** an
> existing NLSL and will serve the NLSL with **firm resource**.*
>
> 1.3.1 **NLSLs**
>
> «Customer Name» has an NLSL and elects to serve the NLSL with a firm
> resource that is not already dedicated to serve its other firm end-use
> consumer loads. The Parties shall list such Dedicated Resource(s) in
> Exhibit A, Net Requirements and Resources. The Parties shall
> administer service to the following NLSL consistent with section 24.3
> of this Agreement.
>
> End--use consumer name:
>
> Facility location:
>
> Date load determined as an NLSL:
>
> Approximate load:
>
> Description of NLSL:
>
> Manner of service:
>
> *End Option 3*
>
> *[Option 1]{.underline}: Include the following if customer **has no**
> onsite renewable or cogeneration facilities to apply to an NLSL:*
>
> 1.3.2 **Renewable Resource/Cogeneration Exception**
>
> «Customer Name»'s end-use consumer is not currently applying an onsite
> renewable resource or cogeneration facility to an NLSL.
>
> *End Option 1*
>
> *[Option 2]{.underline}: Include the following if customer **has** an
> onsite renewable or cogeneration facility to apply to an NLSL.*
>
> 1.3.2 **Renewable Resource/Cogeneration Exception**
>
> *[Drafter's Note]{.underline}: Use Revision 5 to Exhibit D under
> Flathead's Subscription Contract 00PB-12172 as a template and
> coordinate with the NLSL expert and general counsel to add specific
> renewable or cogeneration resource information.*
>
> *[Option]{.underline}: Choose whether customer is applying a renewable
> or cogeneration facility.*
>
> «Customer Name»'s end-use consumer is applying an onsite «renewable
> resource or cogeneration facility» to its NLSL listed in section 2.3.1
> above.
>
> *End Option 2*

*END **LOAD FOLLOWING** template.*

*Include in **BLOCK** and **SLICE/BLOCK** templates:*

> *[Option 2]{.underline}: Include the following if customer **has** an
> existing NLSL*
>
> 1.3.1 **NLSLs**
>
> «Customer Name» has an NLSL and agrees to serve the NLSL with a firm
> resource that is not already dedicated to serve its other firm end-use
> consumer loads. The Parties shall list such Dedicated Resources in
> Exhibit A, Net Requirements and Resources. The Parties shall
> administer service to the following NLSL consistent with section 24.3
> of this Agreement.
>
> End--use consumer name:
>
> Facility location:
>
> Date load determined as an NLSL:
>
> Approximate load:
>
> Description of NLSL:
>
> Manner of service:
>
> *End Option 2*
>
> *[Option 1]{.underline}: Include the following if customer **has no**
> onsite renewable or cogeneration facilities to apply to an NLSL:*
>
> 1.3.2 **Renewable Resource/Cogeneration Exception**
>
> «Customer Name»'s end-use consumer is not currently applying an onsite
> renewable resource or cogeneration facility to an NLSL.
>
> *End Option 1*
>
> *[Option 2]{.underline}: Include the following if customer **has** an
> onsite renewable or cogeneration facility to apply to an NLSL.*
>
> 1.3.2 **Renewable Resource/Cogeneration Exception**
>
> *[Drafter's Note]{.underline}: Use Revision 5 to Exhibit D under
> Flathead's Subscription Contract 00PB-12172 as a template and
> coordinate with the NLSL expert and general counsel to add specific
> renewable or cogeneration resource information.*
>
> *[Option]{.underline}: Choose whether customer is applying a renewable
> or cogeneration facility.*
>
> «Customer Name»'s end-use consumer is applying an onsite «renewable
> resource or cogeneration facility» to its NLSL listed in section 2.3.1
> above.
>
> *End Option 2*

*END **BLOCK** and **SLICE/BLOCK** templates.*

**2.** **RESOURCE SUPPORT SERVICES*(06/16/08 Version)***

> BPA shall develop the RSS products to support applicable Specified
> Resources listed in section 2 of Exhibit A for the FY 2012-2014
> Purchase Period and offer such as a revision to this exhibit by
> August 1, 2009. Prior to that date, BPA shall provide «Customer Name»
> a reasonable opportunity to provide input into the development of the
> products and the related contract provisions. If «Customer Name»
> requests that BPA provide such service, the Parties shall execute a
> revision to this exhibit by the November 1, 2009 Notice Deadline.
>
> By each Notice Deadline thereafter, «Customer Name» may purchase RSS
> from BPA to support applicable Specified Resources listed in section 2
> of Exhibit A for the corresponding Purchase Period. If «Customer Name»
> dedicates a new Specified Resource to its Total Retail Load to meet
> its obligations to serve Above-RHWM Load with Dedicated Resource
> amounts, consistent with section 2 of Exhibit C, «Customer Name» may
> purchase RSS from BPA to support such resource. Such purchase shall be
> for the remainder of the Purchase Period and for the following
> Purchase Period. «Customer Name» shall notify BPA of its decision to
> purchase RSS for a new Specified Resource prior to October 31 of a
> Rate Case Year and the elected RSS will be effective at the start of
> the next Rate Period.

> *[Option]{.underline}: Include the following for customers who are
> eligible to receive irrigation rate mitigation; delete this section if
> not applicable.*

**3. IRRIGATION RATE MITIGATION *(05/15/08 Version)***

> Subject to the terms specified in BPA's applicable Wholesale Power
> Rate Schedules and GRSPs:
>
> 3.1 for billing purposes, in the months listed below for each year
> during the term of this Agreement, BPA shall apply Irrigation Rate
> Mitigation to the lesser of the corresponding PF Tier 1 amount
> purchased in the month or the energy amount in the table below:

Irrigation Amounts (kWh)

  ------------ ------------- ------------- ------------- ------------- -------------
               **May**       **Jun**       **Jul**       **Aug**       **Sept**

  **HLH        000,000,000   000,000,000   000,000,000   000,000,000   000,000,000
  Energy**                                                             

  **LLH        000,000,000   000,000,000   000,000,000   000,000,000   000,000,000
  Energy**                                                             
  ------------ ------------- ------------- ------------- ------------- -------------

> Total Irrigation Amount (kWh): **\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_**
>
> 3.2 after the end of each irrigation season, the Parties shall
> administer a true-up process to ensure «Customer Name»'s irrigation
> load meets or exceeds the total eligible irrigation amount (kWh)
> listed above; and,
>
> 3.3 «Customer Name» shall be responsible for implementing
> cost-effective conservation measures on irrigation systems in their
> service territories. «Customer Name» shall verify and report all
> conservation measures and project savings consistent with
> section 19.1.2 of the body of this Agreement.
>
> *End IRM Option*

**#. «PLACEHOLDER FOR SPECIAL PROVISIONS» *(06/17/08 Version)***

*[Drafter's Note]{.underline}: Insert any special provisions unique to
the customer here, **before** the revisions section, and number sections
accordingly. Otherwise, delete this section if not applicable.*

**#. REVISIONS *(09/04/07 Version)***

> This exhibit shall be revised by mutual agreement of the Parties to
> reflect additional products «Customer Name» purchases during the term
> of this Agreement.

(PS«X/LOC»- «File Name with Path».DOC) «mm/dd/yy» *{[Drafter's
Note]{.underline}: Insert date of finalized contract here}*

***[Option 1]{.underline}:** for Customers who do not operate their own
Balancing Authority Areas.*

**Exhibit E**

**METERING*(06/16/08 Version)***

**1. METERING**

> *[Drafter's Note]{.underline}: **Direct** means the customer is
> directly connected to BPA's system.*
>
> 1.1 **Directly Connected Points of Delivery and Load Metering**
>
> *[Drafter's Note]{.underline}: List all PODs for this customer that
> are directly connected. If there is only one POD, remove the numbering
> "(1)" from this section, move indent appropriately to line up and
> renumber the metering section. Make sure that each section ends with a
> semicolon, except the last item ends with a period.*
>
> \(1\) **BPA POD Name:** «BPA POD Name»;
>
> **BPA POD Number:** «BPA POD #»;
>
> **WECC Balancing Authority:** «BA Name»;*{[Drafter's
> Note]{.underline}: WECC Balancing Authority Area is the new term for
> Control Area.}*
>
> **Location:** the point«s» in «Owner's Name»'s «Substation Name»
> Substation where the «##» kV facilities of «BPA» and «Customer Name»
> are connected;
>
> **Voltage:** «##» kV;
>
> *[Drafter's Note]{.underline}: List all POMs for this POD. If there is
> only one POM, remove the numbering "(A)" from this section, format it
> similarly to the Location section above and renumber the meter
> information below.*
>
> **Metering:**
>
> \(A\) in «Owner's Name»'s «Substation Name» Substation in the «##» kV
> circuit«s» over which such electric power flows;
>
> *[Drafter's Note]{.underline}: List all meters for this POM. If there
> is only one meter, remove the numbering "(i)" from this section and
> move indent appropriately to line up.*
>
> \(i\) **BPA Meter Point Name:** «BPA POM Name»;
>
> **BPA Meter Point Number:** «BPA POM #»;
>
> **Direction for PF Billing Purposes:** «Positive/Negative»;
>
> **Manner of Service:** «Direct, BPA to Customer or Customer to BPA»;
>
> \(ii\) **BPA Meter Point Name:** «BPA POM Name»;
>
> **BPA Meter Point Number:** «BPA POM #»;
>
> **Direction for PF Billing Purposes:** «Positive/Negative»;
>
> **Manner of Service:** «Direct, BPA to Customer or Customer to BPA»;
>
> *[Drafter's Note]{.underline}: If there is more than one POM for this
> POD that requires metering loss factor adjustment, then list them by
> name. Enter "None" if there aren't any.*
>
> **Metering Loss Adjustment:** BPA shall adjust for losses between the
> POD and the «BPA POM Names» POM(s). Such adjustments shall be
> specified in writing between the BPA and «Customer Name»;
>
> *[Drafter's Note]{.underline}: Edit this to include any exceptions for
> this POD. Enter "None" if there aren't any. If there are none or only
> one, then format similar to Metering Loss Adjustment above.*
>
> **Exception«s»:**
>
> *[Drafter's Note]{.underline}: The following exceptions are guidelines
> for possible exceptions needed in sections 1.1 and 1.2 of the Metering
> Exhibit. Do not include in the final exhibit if not applicable.*
>
> \(A\) The period of service for «BPA POD Name or BPA POM Name» shall
> commence when the «substation or equipment» is energized for
> commercial operation; *([Drafter's Note]{.underline}: Use only when
> adding a new metering point that has not yet been energized.)*
>
> \(B\) The period of service for « BPA POD Name or BPA POM Name» shall
> commence at «####» hours on «Month dd, yyyy»; *([Drafter's
> Note]{.underline}: Use only if added a new metering point during the
> term of the contract and the date is known.)*
>
> \(C\) The period of service for « BPA POD Name or BPA POM Name» shall
> end at «####» hours on «Month dd, yyyy»; *([Drafter's
> Note]{.underline}: Use only if deleting a metering point during the
> term of the contract and the date is known.)*
>
> \(D\) The revenue meters for «BPA POM Name» POM are owned by «Owner
> Name»; *([Drafter's Note]{.underline}: Use only if revenue meters are
> not owned by BPA.)*
>
> \(E\) This POD is subject to charges for Low Voltage Delivery
> established in section 14.6.2 of the body of this Agreement;
> *([Drafter's Note]{.underline}: Use only if the POD is served by
> transfer and is subject to Low Voltage Delivery charges.)*
>
> \(F\) This POD is subject to a «#,###» kWh demand limit; *([Drafter's
> Note]{.underline}: Use only if the POD is subject to demand limit
> under the Transfer Agreement.)*
>
> \(G\) «Customer Name» provides «#» kV step-down to «#» kV delivery
> service at «Owner Name»'s «Substation Name» Substation. *([Drafter's
> Note]{.underline}: Use only if customer is providing step-down service
> and it is not a BPA owned substation.)*
>
> \(2\) **BPA POD Name:** «BPA POD Name»;
>
> **BPA POD Number:** «BPA POD #»;
>
> **WECC Balancing Authority:**  «BA Name»;
>
> **Location:** the point«s» in «Owner's Name»'s «Substation Name»
> Substation where the «##» kV facilities of «BPA» and «Customer Name»
> are connected;
>
> **Voltage:** «##» kV;
>
> **Metering:**
>
> \(A\) in «Owner's Name»'s «Substation Name» Substation in the «##» kV
> circuit«s» over which such electric power flows;
>
> \(i\) **BPA Meter Point Name:** «BPA POM Name»;
>
> **BPA Meter Point Number:** «BPA POM #»;
>
> **Direction for PF Billing Purposes:** «Positive/Negative»;
>
> **Manner of Service:** «Direct, BPA to Customer or Customer to BPA»;
>
> \(ii\) **BPA Meter Point Name:** «BPA POM Name»;
>
> **BPA Meter Point Number:** «POM #»;
>
> **Direction for PF Billing Purposes:** «Positive/Negative»;
>
> **Manner of Service:** «Direct, BPA to Customer or Customer to BPA»;
>
> **Metering Loss Adjustment:** BPA shall adjust for losses between the
> POD and the «BPA POM Names» POM(s). Such adjustments shall be
> specified in writing between the BPA and «Customer Name»;
>
> **Exception«s»:**
>
> *[Drafter's Note]{.underline}: **Transfer** means the customer is
> served by transfer over a Third Party Transmission Provider's system.*
>
> *[Drafter's Note]{.underline}: **If a customer is not served by
> transfer, enter a return after the header (1.2 Transfer Points) and
> enter None. Then delete all information down to section 1.3.***
>
> 1.2 **Transfer Points of Delivery and Load Metering**
>
> *[Drafter's Note]{.underline}: List all PODs for this customer that
> are served by Transfer. If there is only one POD, remove the numbering
> "(1)" from this section, move indent appropriately to line up and
> renumber the metering section. Make sure that each section ends with a
> semicolon, except the last item ends with a period.*
>
> \(1\) **BPA POD Name:** «BPA POD Name»;
>
> **BPA POD Number:** «BPA POD #»;
>
> **WECC Balancing Authority:** «BA Name»;*{[Drafter's
> Note]{.underline}: WECC Balancing Authority is the new term for
> Control Area.}*
>
> **Location:** the point«s» in «Owner's Name»'s «Substation Name»
> Substation where the «##» kV facilities of «BPA» and «Customer Name»
> are connected;
>
> **Voltage:** «##» kV;
>
> *[Drafter's Note]{.underline}: List all POMs for this POD. If there is
> only one POM, remove the numbering "(A)" from this section, format it
> similarly to the Location section above and renumber the meter
> information below.*
>
> **Metering:**
>
> \(A\) in «Owner's Name»'s «Substation Name» Substation in the «##» kV
> circuit«s» over which such electric power flows;
>
> *[Drafter's Note]{.underline}: List all meters for this POM. If there
> is only one meter, remove the numbering "(i)" from this section and
> move indent appropriately to line up.*
>
> \(i\) **BPA Meter Point Name:** «BPA POM Name»;
>
> **BPA Meter Point Number:** «BPA POM #»;
>
> **Direction for PF Billing Purposes:** «Positive/Negative»;
>
> **Manner of Service:** « Transfer, BPA to Transferor to Customer or
> Customer to Transferor to BPA»;
>
> \(ii\) **BPA Meter Point Name:** «BPA POM Name»;
>
> **BPA Meter Point Number:** «BPA POM #»;
>
> **Direction for PF Billing Purposes:** «Positive/Negative»;
>
> **Manner of Service:** « Transfer, BPA to Transferor to Customer or
> Customer to Transferor to BPA»;
>
> *[Drafter's Note]{.underline}: If there is more than one POM for this
> POD that requires metering loss factor adjustment, then list them by
> name. Enter "None" if there aren't any.*
>
> **Metering Loss Adjustment:** BPA shall adjust for losses between the
> POD and the «BPA POM Names» POM(s). Such adjustments shall be
> specified in writing between the BPA and «Customer Name»;
>
> *[Drafter's Note]{.underline}: Edit this to include any exceptions for
> this POD. Enter "None" if there aren't any. If there are none or only
> one, then format similar to Metering Loss Adjustment above.*
>
> **Exception«s»:**
>
> *[Drafter's Note]{.underline}: **If a customer does not have
> resources, enter a return after the header (1.3 Resource Locations)
> and enter None. Then delete all information down to section 2
> Revisions.***
>
> 1.3 **Resource Locations and Metering**
>
> []{.mark}
>
> *[Drafter's Note]{.underline}: If there is only one resource, remove
> the numbering "(1)" from this section, move indent appropriately to
> line up and renumber the metering sections.*
>
> \(1\) **Resource Name:** «Resource Name»
>
> *[Drafter's Note]{.underline}: If there is only one metering location,
> remove the numbering "(A)" from this section, move indent
> appropriately to line up and renumber the meter information below.*
>
> **Metering:**
>
> \(A\) in «Owner's Name»'s «Substation Name» Substation in the «##» kV
> circuit«s» over which such electric power flows;
>
> *[Drafter's Note]{.underline}: List all meters for this POM. If there
> is only one meter, remove the numbering "(i)" from this section and
> move indent appropriately to line up.*
>
> \(i\) **BPA Meter Point Name:** «BPA POM Name»;
>
> **BPA Meter Point Number:** «BPA POM #»;
>
> **Direction for PF Billing Purposes:** «Positive/Negative»;
>
> *[Drafter's Note]{.underline}: Below **Directly Connected** means the
> resource is directly connected to the customer's system, **Wheeled**
> means the resource is not connected directly to the customer's system
> and the power and energy from that resource is brought to the
> customer's system over another utility's transmission system.*
>
> **Manner of Service:** «Directly Connected/Wheeled, Resource to BPA to
> Customer or Resource to Customer to BPA»;
>
> \(ii\) **BPA Meter Point Name:** «BPA POM Name»;
>
> **BPA Meter Point Number:** «POM #»;
>
> **Direction for PF Billing Purposes:** «Positive/Negative»;
>
> **Manner of Service:** «Direct/Transfer, Resource to BPA to Customer
> or Resource to Customer to BPA»;
>
> *[Drafter's Note]{.underline}: If there is more than one POM that
> requires metering loss factor adjustment, then list them by name.
> Enter "None" if there aren't any.*
>
> **Metering Loss Adjustment:** BPA shall adjust for losses between the
> «BPA POD Name» POD and the «BPA POM Names» POM(s). Such adjustments
> shall be specified in written correspondence between the BPA and
> «Customer Name»;
>
> *[Drafter's Note]{.underline}: Edit this to include any exceptions for
> this resource. Enter "None" if there aren't any. If there are none or
> only one, then format similar to Metering Loss Adjustment above. See
> section 1.1.1 for examples.*
>
> **Exception«s»:**

**2. REVISIONS**

> Each Party shall notify the other in writing if updates to this
> exhibit are necessary to accurately reflect the actual characteristics
> of POD and meter information described in this exhibit. The Parties
> shall revise this exhibit to reflect such changes. The Parties shall
> mutually agree on any such exhibit revisions and agreement shall not
> be unreasonably withheld or delayed. The effective date of any exhibit
> revision shall be the date the actual circumstances described by the
> revision occur.

(PS«X/LOC»- «File Name with Path».DOC) «mm/dd/yy» *{[Drafter's
Note]{.underline}: Insert date of finalized contract here}*

*End option 1 for Customers who do not operate their own Balancing
Authority Areas.*

***[Option 2]{.underline}:** for Customers who operate their own
Balancing Authority Areas.*

**Exhibit E**

**METERING*(06/11/08 Version)***

**1. DESCRIPTION OF INTERCHANGE METERS**

> Although the following interchange meters are not necessary in order
> to prepare «Customer Name»'s power bills, inclusion of this
> information will help both Parties administer this Agreement.
> Information about the points of interchange and meter to interchange
> relationships are useful in providing the Parties a better
> understanding of the scope of «Customer Name»'s and BPA\'s Balancing
> Authority Areas and assist both Parties in administration of this
> Agreement. This information will also help BPA review its forecasting
> assumptions.
>
> *[Drafter's Note]{.underline}: If there is only one Point of
> Interchange, remove the numbering "(a)" from this section, move indent
> appropriately to line up, and renumber the metering to start with
> "1.1".*
>
> 1.1 **Name of Interchange Point: «NAME» INTERCHANGE**
>
> **Owner:** «Owner»;
>
> **Metering:**
>
> *[Drafter's Note]{.underline}: List all meters for this Interchange
> Point. If there is only one meter, remove the numbering "(A)" from
> this section and move indent appropriately to line up.*
>
> \(1\) in «Owner's Name»'s «Substation Name» Substation in the «##» kV
> circuit«s» over which such electric power flows.
>
> \(2\) in «Owner's Name»'s «Substation Name» Substation in the «##» kV
> circuit«s» over which such electric power flows.

**2. REVISIONS**

> Each Party shall notify the other in writing if updates to this
> exhibit are necessary to accurately reflect the actual characteristics
> of POD and meter information described in this exhibit. The Parties
> shall revise this exhibit to reflect such changes. The Parties shall
> mutually agree on any such exhibit revisions and agreement shall not
> be unreasonably withheld or delayed. The effective date of any exhibit
> revision shall be the date the actual circumstances described by the
> revision occur.

(PS«X/LOC»- «File Name with Path».DOC) «mm/dd/yy» *{[Drafter's
Note]{.underline}: Insert date of finalized contract here}*

*End option 2 for Customers who operate their own Balancing Authority
Areas.*

*Include in **LOAD FOLLOWING** template:*

*[Option 1]{.underline}: Include for Transfer Service customers with a
BPA NT Agreement:*

**EXHIBIT F**

**TRANSMISSION SCHEDULING SERVICE**

**1. PURPOSE AND PARAMETERS *(02/11/08 Version)***

> 1.1 **Purpose**
>
> Transmission Scheduling Service is provided by Power Services to help
> «Customer Name» manage certain aspects of its BPA Network Integration
> Transmission Service Agreement (BPA NT Agreement), to allow BPA to use
> the inherent resource flexibilities of «Customer Name»'s Network
> rights in combination with other Network customers rights to manage
> BPA's power resources efficiently, and to provide seamless scheduling
> for Transfer Service customers.
>
> 1.2 **Parameters of Transmission Scheduling Service**
>
> Beginning October 1, 2011, and through the term of this Agreement,
> Power Services shall provide and «Customer Name» shall purchase
> Transmission Scheduling Service. Power Services shall schedule
> «Customer Name»'s federal and non-federal generation resources to
> «Customer Name»'s Total Retail Load under «Customer Name»'s BPA NT
> Agreement and/or other transmission agreement(s). Power Services shall
> not provide Transmission Scheduling Service for anything other than
> delivery to «Customer Name»'s Total Retail Load.
>
> Power Services shall perform all necessary prescheduling and real time
> scheduling functions, and make other arrangements and adjustments
> consistent with any RSS products «Customer Name» is purchasing from
> Power Services. «Customer Name» shall continue to be responsible for
> all non-scheduling provisions of its transmission agreement(s) used to
> serve «Customer Name»'s Total Retail Load including, but not limited
> to, the designation and undesignation of Network Resources, as defined
> by the applicable OATT.
>
> Transmission Scheduling Service shall be subject to the rates, terms
> and conditions specified in BPA's applicable Wholesale Power Rate
> Schedules and GRSPs.

**2. ASSIGNMENT OF SCHEDULING RIGHTS *(02/08/08 Version)***

> Prior to commencement of Transmission Scheduling Service, «Customer
> Name» shall:
>
> \(1\) notify Transmission Services that Power Services is the
> scheduling entity for service taken under «Customer Name»'s BPA NT
> Agreement;
>
> \(2\) assign Power Services the right to acquire and manage secondary
> service pursuant to section 28.4 of the BPA OATT as necessary to
> fulfill BPA's obligations under this Agreement; and
>
> \(3\) provide copies of «Customer Name»'s transmission agreement(s)
> used to serve «Customer Name»'s Total Retail Load.
>
> Additionally, over the term of this Agreement, «Customer Name» shall
> provide Power Services with any additional transmission agreements
> «Customer Name» enters into which are used for service to its Total
> Retail Load and all amendments and modifications to current copies of
> «Customer Name»'s transmission agreement(s).

**3. LOAD FORECAST *(02/08/08 Version)***

> If a daily load forecast is required by «Customer Name»'s transmission
> agreement(s), BPA shall develop the daily and hourly load forecasts
> for «Customer Name»'s Total Retail Load. «Customer Name» shall
> cooperate with BPA in all load forecasting. If any load specific
> information is needed for developing daily or hourly load forecast,
> «Customer Name» shall provide such information in a timely manner.

**4. SCHEDULING OF «CUSTOMER NAME»'s NON-FEDERAL RESOURCES**

> 4.1 **Prescheduling**
>
> «Customer Name» shall submit a generation schedule to Power Services
> for its non-federal resource for delivery to its Total Retail Load
> which shall include information such as the source of the schedule,
> the point of receipt, any oasis reservation reference numbers needed
> for the delivery of non-federal power, the daily MW profile and all
> purchasing selling entities in the path. The delivery schedule shall
> be submitted to Power Services before the earliest of:
>
> \(1\) 0800 hours Pacific Prevailing Time (PPT) on preschedule day or
>
> \(2\) one hour prior to the earliest of the transmission prescheduling
> deadlines associated with «Customer Name»'s transmission agreement(s)
> delivery of power to «Customer Name»'s Total Retail Load.
>
> «Customer Name» shall submit all required prescheduled information in
> a format specified by Power Services.
>
> At Power Services' request, «Customer Name» shall provide Power
> Services information on real power losses associated with «Customer
> Name»'s transmission agreement(s).
>
> 4.2 **Real Time Scheduling**
>
> Power Services shall accept megawatt adjustments to «Customer Name»'s
> nonfederal resource schedule(s) up to the earliest of 45 minutes prior
> to the hour of delivery or 25 minutes prior to the earliest of the
> transmission real time scheduling deadlines associated with delivery
> of power to «Customer Name»'s Total Retail Load.
>
> «Customer Name» shall submit all required real time scheduling
> information in a format specified by Power Services.
>
> 4.3 **Transmission Curtailments and Generation Outages*(02/28/08
> Version)***
>
> The timelines below apply to «Customer Name» if «Customer Name» has
> not acquired Forced Outage Reserves from Power Services:
>
> \(1\) **Curtailment or Outage Prior to 45 Minutes Before Delivery
> Hour**
>
> «Customer Name» shall be responsible for securing replacement energy
> within or to the BPA Balancing Authority Area and notifying Power
> Services of the revised schedule prior to 45 minutes before the hour
> of delivery.
>
> If Power Services is unable to secure secondary network transmission
> for the replacement resource because «Customer Name» did not notify
> Power Services of the revised schedule prior to 45 minutes prior to
> the hour of delivery or secondary network transmission is unavailable,
> «Customer Name» shall be subject to charges consistent with the
> provisions of this Agreement and all related products and BPA's rate
> schedules, including UAI charges.
>
> \(2\) **Curtailment or Outage After 45 Minutes Before Delivery Hour**
>
> Power Services shall not accept replacement schedules for transmission
> curtailments generation outages that occur after 45 minutes before
> delivery hour. Customer Name» shall be subject to charges consistent
> with the provisions of this Agreement and all related products and
> BPA's rate schedules, including UAI charges.

**5. E‑TAGS**

> To the extent electronic tags (E‑Tags) are required by transmission
> provider(s), Power Services shall create all E‑Tags necessary for
> delivery of energy to «Customer Name»'s Total Retail Load.

**6. GENERATION IMBALANCE**

> «Customer Name» is responsible for costs associated with deviations
> between the scheduled non-federal generation for an hour and the
> actual generation produced across such hour. Provided, however, if
> «Customer Name» submits a delivery schedule consistent with all
> provisions of this Exhibit and BPA receives that schedule, and a
> generation imbalance results from the BPA error, BPA shall accept
> responsibility for the generation imbalance associated with the BPA
> scheduling error.

**7. PENALTIES*(03/21/08 Version)***

> If «Customer Name» fails to submit presecheduling or real-time
> scheduling information to BPA as required and by the deadlines in
> section 4 above, then «Customer Name» may be subject to applicable
> unauthorized increase charges, consistent with BPA's applicable
> Wholesale Power Rate Schedules and GRSPs.

**8. AFTER THE FACT**

> BPA and «Customer Name» agree to reconcile all transactions, schedules
> and accounts at the end of each month (as early as possible within the
> first 10 calendar days of the next month). BPA and «Customer Name»
> shall verify all transactions per this Agreement, as to product or
> type of service, hourly amounts, daily and monthly totals, and related
> charges.

**9. REVISIONS**

> BPA may unilaterally revise this exhibit:
>
> \(1\) to implement changes that BPA determines are necessary to allow
> it to meet its power and scheduling obligations under this Agreement,
> or
>
> \(2\) to comply with requirements of the WECC, NAESB, or NERC, or
> their successors or assigns.
>
> Revisions are effective 45 days after BPA provides written notice of
> the revisions to «Customer Name» unless, in BPA's sole judgment, less
> notice is necessary to comply with an emergency change to the
> requirements of the WECC, NAESB, NERC, or their successors or assigns.
> In this case, BPA shall specify the effective date of such revisions.

(PS«X/LOC»- «File Name with Path».DOC) «mm/dd/yy» *{[Drafter's
Note]{.underline}: Insert date of finalized contract here}*

*End Option 1*

*[Option 2]{.underline}: Include for non-transfer customers with a BPA
NT Agreement:*

**EXHIBIT F**

**SCHEDULING**

1\. **TRANSMISSION SCHEDULING SERVICE**

If «Customer Name»:

> \(1\) acquires BPA's Diurnal Flattening Service; and/or,
>
> \(2\) acquires BPA's Secondary Crediting Service; and/or
>
> \(3\) purchases power from BPA at a Tier 2 rate,
>
> then Power Services shall provide and «Customer Name» shall purchase
> Transmission Scheduling Service. In such case, the Parties shall
> revise this exhibit to include the terms and conditions of such
> service.
>
> If «Customer Name» is not required to purchase Transmission Scheduling
> Service, pursuant to the paragraph above, then «Customer Name», with
> 6 months notice, may purchase Transmission Scheduling Service from
> Power Services and the Parties shall modify this exhibit to add the
> terms and conditions of such service.

**2. SCHEDULING OF NON-FEDERAL RESOURCES**

> «Customer Name» shall electrically copy BPA Power Services on all
> preschedule and real-time electronic tags (E‑Tags) associated with the
> delivery of «Customer Name»'s non-federal resources, if any, as listed
> in Exhibit A, Net Requirements and Resources.

**3. AFTER THE FACT**

> BPA and «Customer Name» agree to reconcile all transactions, schedules
> and accounts at the end of each month (as early as possible within the
> first 10 calendar days of the next month). BPA and «Customer Name»
> shall verify all transactions per this Agreement, as to product or
> type of service, hourly amounts, daily and monthly totals, and related
> charges.

**4. REVISIONS**

> BPA may unilaterally revise this exhibit:
>
> \(1\) to implement changes that BPA determines are necessary to allow
> it to meet its power and scheduling obligations under this Agreement,
> or
>
> \(2\) to comply with requirements of the WECC, NAESB, or NERC, or
> their successors or assigns.
>
> Revisions are effective 45 days after BPA provides written notice of
> the revisions to «Customer Name» unless, in BPA's sole judgment, less
> notice is necessary to comply with an emergency change to the
> requirements of the WECC, NAESB, NERC, or their successors or assigns.
> In this case, BPA shall specify the effective date of such revisions.

(PS«X/LOC»- «File Name with Path».DOC) «mm/dd/yy» *{[Drafter's
Note]{.underline}: Insert date of finalized contract here}*

*End Option 2*

*[Option 3]{.underline}: Include for customers with a BPA PTP
Transmission Agreement:*

**EXHIBIT F**

**SCHEDULING**

**1. SCHEDULING OF NON-FEDERAL RESOURCES**

> «Customer Name» shall electrically copy BPA Power Services on all
> preschedule and real-time E‑Tags associated with the delivery of
> «Customer Name»'s non-federal resources, if any, as listed in
> Exhibit A, Net Requirements and Resources.

**2. AFTER THE FACT**

> BPA and «Customer Name» agree to reconcile all transactions, schedules
> and accounts at the end of each month (as early as possible within the
> first 10 calendar days of the next month). BPA and «Customer Name»
> shall verify all transactions per this Agreement, as to product or
> type of service, hourly amounts, daily and monthly totals, and related
> charges.

**3. REVISIONS**

> BPA may unilaterally revise this exhibit:
>
> \(1\) to implement changes that BPA determines are necessary to allow
> it to meet its power and scheduling obligations under this Agreement,
> or
>
> \(2\) to comply with requirements of the WECC, NAESB, or NERC, or
> their successors or assigns.
>
> Revisions are effective 45 days after BPA provides written notice of
> the revisions to «Customer Name» unless, in BPA's sole judgment, less
> notice is necessary to comply with an emergency change to the
> requirements of the WECC, NAESB, NERC, or their successors or assigns.
> In this case, BPA shall specify the effective date of such revisions.

(PS«X/LOC»- «File Name with Path».DOC) «mm/dd/yy» *{[Drafter's
Note]{.underline}: Insert date of finalized contract here}*

*End Option 3*

*END **LOAD FOLLOWING** template.*

*Include in **BLOCK** template:*

**EXHIBIT F**

**SCHEDULING*(4/25/08 version)***

**1. SCHEDULING FEDERAL RESOURCES**

> «Customer Name» is responsible for creating E‑Tags for all deliveries
> of federal power purchased under this Agreement.
>
> *[Option]{.underline}: Include if customer is purchasing Shaping
> Capacity:*
>
> «Customer Name» shall submit its hourly megawatt schedule to Power
> Services by 1100 hours Pacific Prevailing Time (PPT) as follows:

  -----------------------------------------------------------------------
  **Day Before Preschedule:**             
  ------------------------------ -------- -------------------------------
  Friday                         For      Tuesday

  Monday                         For      Wednesday

  Tuesday                        For      Thursday

  Wednesday                      For      Friday, Saturday

  Thursday                       For      Sunday, Monday
  -----------------------------------------------------------------------

> For non-standard scheduling days specified by WECC (e.g. holidays),
> «Customer Name» shall preschedule at least 24 hours earlier than as
> specified by WECC. «Customer Name» shall not have the right to change
> planned amounts of Firm Requirements Power on a shorter timeline than
> as stated above.
>
> With written notice, BPA may require «Customer Name», when using
> Shaping Capacity, to submit its hourly megawatt schedule to Power
> Services by 0900 hours PPT instead of 1100 hours PPT.
>
> *End Option*

**2. AFTER THE FACT**

> BPA and «Customer Name» agree to reconcile all transactions, schedules
> and accounts at the end of each month (as early as possible within the
> first 10 calendar days of the next month). BPA and «Customer Name»
> will verify all transactions per this Agreement, as to product or type
> of service, hourly amounts, daily and monthly totals, and related
> charges

**3. REVISIONS**

> BPA may unilaterally revise this exhibit: (1) to implement changes
> that are applicable to all customers who are subject to this exhibit
> and that BPA determines are reasonably necessary to meet its power and
> scheduling obligations under this Agreement or (2) to comply with
> requirements of the WECC, NAESB, or NERC, or their successors or
> assigns.
>
> Revisions are effective 45 days after BPA provides written notice of
> the revisions to «Customer Name» unless, in BPA's sole judgment, less
> notice is necessary to comply with an emergency change to the
> requirements of the WECC, NAESB, NERC, or their successors or assigns.
> In this case, BPA shall specify the effective date of such revisions.

*END **BLOCK** template.*

*Include in **SLICE/BLOCK** templates:*

**EXHIBIT F**

**SCHEDULING *(04/30/08 Version)***

*[Reviewer's Note]{.underline}: This is a placeholder for now. Slice
Team will drop in their version.*

*END **SLICE/BLOCK** templates.*

*[Option 1]{.underline}: Include the following for non-Transfer Service
customers.*

**Exhibit G*(05/25/08 Version)***

**THIS EXHIBIT INTENTIONALLY LEFT BLANK**

(PS«X/LOC»- «File Name with Path».DOC) «mm/dd/yy» *{[Drafter's
Note]{.underline}: Insert date of finalized contract here}*

*End Option 1*

*[Option 2]{.underline}: Include the following exhibit for Transfer
Service customers.*

**Exhibit G*(06/13/08 Version)***

**PRINCIPLES OF NON-FEDERAL TRANSFER SERVICE**

As provided by section 14.6.7 of the body of this Agreement and BPA's
Long-Term Regional Dialogue Final Policy, July 2007, or any other later
revision of that policy, if «Customer Name» acquires non-federal
resources to serve its retail load above its established RHWM, BPA\'s
support and assistance to «Customer Name» shall be consistent with the
following principles:

**1.** **Established Caps and Limitations**

> BPA shall provide financial support for the transmission capacity
> associated with non-federal resource purchases to all Transfer Service
> customers up to a maximum of 41 megawatts per fiscal year, cumulative
> over the duration of the agreement. This cumulative megawatt limit is
> shown in the table below.

  -----------------------------------------------------------------------
  **Fiscal Year**       **Per Year MW Limit**   **Cumulative MW Limit**
  --------------------- ----------------------- -------------------------
  FY 2012               41                      41

  FY 2013               41                      82

  FY 2014               41                      123

  FY 2015               41                      164

  FY 2016               41                      205

  FY 2017               41                      246

  FY 2018               41                      287

  FY 2019               41                      328

  FY 2020               41                      369

  FY 2021               41                      410

  FY 2022               41                      451

  FY 2023               41                      492

  FY 2024               41                      533

  FY 2025               41                      574

  FY 2026               41                      615

  FY 2027               41                      656

  FY 2028               41                      697
  -----------------------------------------------------------------------

**2.** Application of section 14.6.7 of body of this Agreement shall be
on a first come, first served basis in each year based on the date each
request is received by BPA. Requests not met, in whole or in part, in
any Fiscal Year will have priority over subsequent requests the
following year. Once granted, BPA shall honor such request for the
duration of the resource acquisition period.

**3. Process and Parameters For Initially Choosing A Non-Federal
Resource**

> 3.1 BPA obtains Transfer Service from Third Party Transmission
> Providers pursuant to OATT Network Integration Transmission Service.
> Additionally, BPA acquires firm transmission for all load service
> obligations incurred. Therefore, BPA shall, on behalf of «Customer
> Name», pursue Network Resource designation, as defined in the FERC
> OATT. BPA shall provide all information the Third Party Transmission
> Provider requires to evaluate the Network Resource designation
> request. «Customer Name» shall provide all relevant information BPA
> determines is required and necessary to submit an application for
> designation of the resource as a Network Resource per section 29 of
> the OATT.
>
> 3.2 «Customer Name» shall notify BPA of its intent and/or actions to
> acquire or purchase a non-federal resource at least one year prior to
> delivery. Such acquisition or purchase shall be for a period of no
> less than one year in duration.
>
> 3.3 If BPA's existing Transfer Service to «Customer Name» is pursuant
> to a non-OATT contractual arrangement, BPA shall pursue all reasonable
> arrangements, including but not limited to, OATT service, sufficient
> to enable «Customer Name» to utilize the non-federal resource to serve
> its load.
>
> 3.4 BPA shall not be liable to «Customer Name» in the event that
> Network Resource designation cannot be obtained.
>
> 3.5 BPA shall only obtain or pay for Transfer Service for «Customer
> Name»'s non-federal resource if it is designated as a Network Resource
> under the Third Party Transmission Provider's OATT with a commitment
> of at least one year. The limitations in this principle 3 do not
> pertain to market purchases and the use of secondary network
> transmission, which are addressed below in principle 15.

**4.** «Customer Name» shall provide BPA all information BPA determines
is reasonably necessary to obtain and administer firm network
transmission service over the Third Party Transmission Provider's
system.

**5.** BPA shall only pay the capacity costs associated with
transmission service to «Customer Name» over the transmission facilities
of the Third Party Transmission Provider that either (1) interconnect
directly to «Customer Name»'s facilities or (2) interconnect to BPA
transmission facilities which subsequently interconnect with «Customer
Name»'s facilities. «Customer Name» shall arrange for, and pay any costs
associated with, the delivery of non-federal power to an interconnection
point with the Third Party Transmission Provider, including obtaining
and paying for firm transmission across all intervening transmission
systems.

**6.** «Customer Name» shall pay a portion of the costs of all Ancillary
Services necessary to deliver any non-federal resource to serve its
load. The Ancillary Service costs imposed by the Third Party
Transmission Provider shall be apportioned between BPA and «Customer
Name» based on either:

> \(1\) metered/scheduled quantities of the non-federal resource,
> expressed as a percentage of total load, multiplied by the total costs
> assessed BPA by the Third Party Transmission Provider; or,
>
> \(2\) actual charges assessed by the Third Party Transmission
> Provider.
>
> However, BPA shall treat the cost of load regulation service
> consistent with the load regulation service cost as described in
> section 14.6.1.1 of the body of this Agreement. BPA shall be
> responsible for the cost of generation supplied reactive power, and
> «Customer Name» shall be responsible for any generation imbalance
> costs, if any, related to «Customer Name»'s non-federal resource.

**7.** «Customer Name» shall be responsible for the costs of all other
transmission services for non-federal deliveries not included in
principles 5 and 6 above, including, but not limited to: redispatch,
congestion management costs, system and facility study costs associated
with adding the non-federal generation as a network resource, direct
assigned system upgrades, distribution and low-voltage charges, if
applicable and real power losses.

**8.** «Customer Name» shall be responsible for all costs of
interconnecting generation to a transmission system.

**9.** «Customer Name» shall be responsible for acquiring transmission
services from BPA, including wheeling for non-federal resources. If
«Customer Name» does not require transmission services from BPA for
wheeling non-federal resources, «Customer Name» shall be responsible for
a pro rata share of the Third Party Transmission Provider transmission
costs that BPA incurs to serve «Customer Name».

**10.** «Customer Name» shall be responsible for all integration
services to support its non-federal resources:

> \(1\) in accordance with all requirements of the host Balancing
> Authority and/or Third Party Transmission Provider, and
>
> \(2\) which are necessary for designation of the non-federal resource
> as a Network Resource.

**11.** As necessary, «Customer Name» shall meet all resource metering
requirements including compliance with BPA standards and any
requirements of the generation host Balancing Authority and/or Third
Party Transmission Provider.

**12.** The Parties shall cooperate to establish the protocols,
procedures, data exchanges or other arrangements the Parties deem
reasonably necessary to support the transmission of «Customer Name»'s
non-federal resource(s).

**13.** Unless otherwise agreed, «Customer Name» shall be responsible
for managing any non-federal resource and shall schedule power
consistent with Exhibit F, Transmission Scheduling Service.

**14.** BPA shall have no obligation to pay for Transfer Service for
non-federal power to serve any portion of «Customer Name»'s retail load
that «Customer Name» is obligated to serve with federal power pursuant
to this Agreement.

**15.** Once «Customer Name»'s non-federal resource has been designated
as a Network Resource, BPA will not undesignate «Customer Name»'s
Network Resource for marketing purposes. Also, once such Network
Designation has been made, «Customer Name» may make market purchases to
displace the Network Resource, which BPA shall schedule on Secondary
Network Service, provided that:

> \(1\) such market purchases are at least one day in duration;
>
> \(2\) the megawatt amount of the market purchase does not exceed the
> amount of the designated Network Resource that «Customer Name» would
> have scheduled to its load;
>
> \(3\) such market purchases are only scheduled in preschedule
> consistent with section 4.1 of Exhibit F, Transmission Scheduling
> Service;
>
> \(4\) «Customer Name» does not, under any circumstances, remarket its
> designated Network Resource or perform any other operation that would
> cause BPA to be in violation of its obligations under the Third Party
> Transmission Providers OATT;
>
> \(5\) «Customer Name» is responsible for any additional energy
> imbalance, redispatch, and/or UAI charges that result from a
> transmission curtailment that impacts the resulting Secondary Network
> Schedule; and
>
> \(6\) any RSS products that «Customer Name» has purchased from BPA are
> not applied to the market purchase(s).

**16.** These principles will be the basis for a separate agreement BPA
shall offer to «Customer Name» to support the Transfer Service of
«Customer Name»'s non-federal resource. BPA shall include terms specific
to a particular non-federal resource in exhibits to the separate
agreement, with a separate exhibit for each non-federal resource.
«Customer Name» is under no obligation to accept this separate agreement
or the exhibit for the particular non-federal resource and BPA is not
bound to acquire or pay for Transfer Service for non-federal resources
if «Customer Name» does not accept the separate agreement or the exhibit
for the particular non-federal resource.

(PS«X/LOC»- «File Name with Path».DOC) «mm/dd/yy» *{[Drafter's
Note]{.underline}: Insert date of finalized contract here}*

*End Option 2*

**Exhibit H*(06/17/08 Version)***

**RENEWABLE ENERGY CERTIFICATES AND CARBON ATTRIBUTES**

> [\[\[Comment: The draft Regional Dialogue Contract Templates fail to
> take into account the fact that costs of resources acquired by BPA are
> assigned to various rates, including both the PF Preference rate and
> the PF Exchange rate. Regional Dialogue contracts must not assign
> Environmental Attributes or carbon emission credits or similar carbon
> instruments associated with those resources solely to PF Preference
> rate customers. Instead, PF Exchange rate customers are entitled to a
> full share---if, as, and when PF Preference customers share in any
> Environmental Attributes (or the value thereof) and in any carbon
> emission credits and similar carbon instruments (or the value
> thereof), associated with BPA resources. This is true with respect any
> Environmental Attributes and any carbon emission credits and similar
> carbon instruments associated with either Tier 1 resources or Tier 2
> resources, insofar as the PF Exchange rate resource costs reflect the
> costs of both Tier 1 resources and Tier 2 resources. The draft
> Template and the Residential Exchange Purchase and Sale Agreement
> ("RPSA") template should reflect this full share for PF Exchange rate
> customers of Environmental Attributes and carbon emission credits and
> similar carbon instruments associated with those resources.
> Additionally, it is not apparent that the terms of the proposed
> Exhibit H (in the draft Template or any other similar BPA draft
> template) is consistent with applicable provisions of federal law or
> regulations that govern the disposition of federal property. In any
> event, adoption of Exhibit H as proposed by BPA would be arbitrary and
> capricious or otherwise contrary to law.\]\]]{.mark}

**1. DEFINITIONS**

> 1.1 "Environmental Attribute(s)"***(04/04/08 Version)*** means the
> current or future credits, benefits, emission reductions, offsets and
> allowances attributable to the generation of energy from a specific
> renewable resources. One megawatt hour of energy generation from such
> renewable resource is associated with 1 megawatt hour of Environmental
> Attributes.
>
> 1.2 "Renewable Energy Certificates" or "RECs"***(03/20/08 Version)***
> means the certificates that document the ownership of Environmental
> Attributes.
>
> 1.3 "Tier 1 RECs"***(04/04/08 Version)*** means the Environmental
> Attributes composed of a blend, by fuel source, based on annual
> generation of the specified renewable resources listed in section 2
> below.
>
> 1.4 "Tier 2 Cost Pools"***(06/16/08 Version)*** means the collection
> of Tier 2 costs, to be recovered by means of the application of Tier 2
> Rates, or as defined in the TRM. Each Tier 2 Rate will be based on a
> corresponding Tier 2 Cost Pool.
>
> 1.5 "Tier 2 RECs"***(03/27/08 Version)*** means the Environmental
> Attributes generated by specified renewable resources whose costs are
> recovered in a Tier 2 Cost Pool.
>
> 1.6 "Environmentally Preferred Power RECS" or "EPP RECs"***(04/01/08
> Version)*** means the portion of BPA's Tier 1 RECs that is equal to an
> amount up to 130 percent of the annual average of environmentally
> preferred power (EPP) contracted for as of October 1, 2009, for
> FYs 2010 and 2011 under Subscription power sales contracts containing
> rights to Environmental Attributes through FY 2016.

**2. BPA'S TIER 1 REC INVENTORY**

> BPA shall use its share of generation from the following renewable
> resources to establish the Tier 1 REC inventory: Foote Creek I, Foote
> Creek II, Stateline, Condon, Klondike I, Klondike III, and Ashland
> Solar. BPA shall maintain a current list of renewable resources BPA
> uses to establish its Tier 1 REC inventory on a publicly accessible
> BPA website. BPA may update this list at any time. BPA shall calculate
> its inventory of Tier 1 RECs annually and after-the-fact based on
> energy generated by listed resources during the previous calendar
> year.

**3. «CUSTOMER NAME»'S SHARE OF TIER 1 RECS** ***(05/14/08 Version)***

> Beginning April 15, 2012, and by April 15 every year thereafter over
> the duration of this Agreement, BPA shall:
>
> \(1\) transfer to «Customer Name», or manage in accordance with
> section 5 below, at no additional charge or premium, a pro rata share
> of Tier 1 RECs based on «Customer Name»'s RHWM divided by the total
> RHWMs of all holders of CHWM Contracts; and,
>
> \(2\) for transferred RECs, provide «Customer Name» with a letter
> assigning title of such Tier 1 RECs to «Customer Name».
>
> The amount of Tier 1 RECs available to BPA to transfer or manage shall
> be subject to the amount of available Tier 1 REC inventory, excluding
> amounts of Tier 1 REC inventory used to provide EPP RECs.

**4. TIER 2 RECS *(06/16/08 Version)***

> If «Customer Name» chooses to purchase Firm Requirements Power at a PF
> Tier 2 Rate, and such power includes RECs, then beginning April 15,
> 2012 and by April 15 every year thereafter for the duration of
> «Customer Name»'s Tier 2 purchase obligation, BPA shall, based on
> «Customer Name»'s election pursuant to section 5 below, transfer to or
> manage for «Customer Name», a pro rata share of applicable Tier 2 RECs
> generated during the previous calendar year. The pro rata share of
> Tier 2 RECs BPA transfers to «Customer Name» shall be the ratio of
> RECs associated with «Customer Name»'s PF Tier 2 purchase obligation
> to the RECs associated with the purchase obligation of all other
> customers from the respective Tier 2 Cost Pool.

**5. TRANSFER, TRACKING, AND MANAGEMENT OF RECS *(06/16/08 Version) ***

> Subject to BPA's determination that the commercial renewable energy
> tracking system WREGIS is adequate as a tracking system, BPA shall
> transfer «Customer Name»'s share of Tier 1 RECs, and Tier 2 RECs if
> applicable, to «Customer Name» via WREGIS. If, over the term of this
> Agreement, BPA determines that WREGIS is not adequate as a tracking
> system, then BPA may change commercial tracking systems with one year
> advance notice to «Customer Name». In such case, the parties shall
> establish a comparable process for BPA to provide «Customer Name» its
> RECs.
>
> Starting on July 15, 2011, and by July 15 prior to each Rate Period
> through the duration of this Agreement, «Customer Name» shall notify
> BPA which one of the following three options it chooses for the
> transfer and management of «Customer Name»'s share of Tier 1 RECs, and
> Tier 2 RECs if applicable, for each upcoming Rate Period:
>
> \(1\) BPA shall transfer «Customer Name»'s RECs into «Customer Name»'s
> own WREGIS account, which shall be established by «Customer Name»; or
>
> \(2\) BPA shall transfer «Customer Name»'s RECs into a BPA-managed
> WREGIS subaccount. Such subaccount shall be established by BPA on
> «Customer Name»'s behalf and the terms and conditions of which shall
> be determined by the Parties in a separate agreement; or,
>
> \(3\) «Customer Name» shall give BPA the authority to market «Customer
> Name»'s RECs on «Customer Name»'s behalf. BPA shall annually credit
> «Customer Name» for «Customer Name»'s pro rata share of revenues
> generated by such sales on its April bill, issued in May.
>
> If «Customer Name» fails to notify BPA of its election by July 15
> before the start of each Rate Period, BPA shall market «Customer
> Name»'s RECs and annually credit «Customer Name» for «Customer Name»'s
> pro rata share of revenues generated by such marketing on «Customer
> Name»'s April bill issued by BPA in May.
>
> Any RECs BPA transfers to «Customer Name» by April 15, 2012, shall be
> limited to those generated October 1, 2011, through December 31, 2011.

**6. FEES *(06/16/08 Version)***

> BPA shall pay any reasonable fees associated with (1) the provision of
> «Customer Name»'s RECs and (2) the establishment of any subaccounts in
> «Customer Name»'s name pursuant to sections 5(1) and 5(2) above.
> «Customer Name» shall pay all other fees associated with any WREGIS or
> successor commercial tracking system, including WREGIS retirement,
> reserve, and export fees.

**7. CARBON ATTRIBUTES *(06/17/08 Version)***

> In the absence of carbon regulations or legislation directly affecting
> BPA, BPA intends to convey the value of any future carbon emission
> credits, or similar carbon instruments, associated with resources
> whose costs are recovered in PF Tier 1 or PF Tier 2 rates to «Customer
> Name» on a pro rata basis. This value may be conveyed as: (1) the
> carbon emission credit, or similar carbon instrument, itself; (2) a
> revenue credit after BPA markets such carbon emission credits, or
> similar carbon instruments; or, (3) the ability to claim that power
> purchases at the applicable PF rate are derived from specific federal
> resources.
>
> The value of carbon emission credits, or similar carbon instruments,
> associated with resources whose costs are recovered in a Tier 1 rate
> will be shared on a pro rata basis among all holders of CHWM
> Contracts. The value of carbon emission credits, or similar carbon
> instruments, associated with resources whose costs are recovered in a
> PF Tier 2 rate will be shared on a pro rata basis among customers
> within the same respective Tier 2 Cost Pool.

**8. BPA'S RIGHT TO TERMINATE «CUSTOMER NAME»'S RECS *(05/29/08
Version)***

> Consistent with any federal regulation or legislation addressing
> carbon emission credits, or similar carbon instruments, or any form of
> renewable energy attribute(s) applicable to BPA which includes
> compliance costs, BPA may, upon 5 years' notice to «Customer Name»,
> terminate «Customer Name»'s contract rights to Tier 1 RECs under
> section 3 above.

(PS«X/LOC»- «File Name with Path».DOC) «mm/dd/yy» *{[Drafter's
Note]{.underline}: Insert date of finalized contract here}*