Skip to Content

Proposed Rule

Revised Public Utility Filing Requirements for Electric Quarterly Reports

Document Details

Information about this document as published in the Federal Register.

Published Document

This document has been published in the Federal Register. Use the PDF linked in the document sidebar for the official electronic format.

Start Preamble May 19, 2008.

AGENCY:

Federal Energy Regulatory Commission.

ACTION:

Notice seeking comments on proposed revisions to Electric Quarterly Report (EQR) data dictionary.

SUMMARY:

In this notice, the Federal Energy Regulatory Commission (Commission) proposes to revise the EQR Data Dictionary to clarify the definition of Contract Commencement date. If adopted, this proposal will make reporting this information less burdensome and more accessible.

DATES:

Comments on the proposal are due June 27, 2008.

ADDRESSES:

You may submit comments on the proposal, identified by Docket No. RM01-8-010, by one of the following methods:

  • Agency Web Site: http://www.ferc.gov. Follow the instructions for submitting comments via the eFiling link found in the Comment Procedures Section of the preamble.
  • Mail: Commenters unable to file comments electronically must mail or hand deliver an original and 14 copies of their comments to the Federal Energy Regulatory Commission, Secretary of the Commission, 888 First Street, NE., Washington, DC 20426. Please refer to the Comment Procedures Section of the preamble for additional information on how to file paper comments.
Start Further Info

FOR FURTHER INFORMATION CONTACT:

Michelle Veloso (Technical Information), Office of Enforcement, Federal Energy Regulatory Commission, 888 First Street, NE., Washington, DC 20426, (202) 502-8363.

Gary D. Cohen (Legal Information), Office of the General Counsel, Federal Energy Regulatory Commission, 888 First Street, NE., Washington, DC 20426, (202) 502-8321.

End Further Info End Preamble Start Supplemental Information

SUPPLEMENTARY INFROMATION:

1. The Commission is proposing to revise the Electric Quarterly Report (EQR) Data Dictionary to clarify the definition of Contract Commencement Date in Field 22.

Background

2. On April 25, 2002, the Commission issued Order No. 2001, a Final Rule establishing revised public utility filing requirements.[1] This rule revised the Commission's filing requirements to require companies subject to the Commission's regulations under section 205 of the Federal Power Act [2] to file quarterly reports that: (1) Provide data identifying the utility on whose behalf the report is being filed (ID Data); (2) summarize pertinent data about the utility's currently effective contracts (Contract Data); and (3) summarize data about wholesale power sales the utility made during the reporting period (Transaction Data). The requirement to file EQRs replaced the requirement to file quarterly transaction reports summarizing a utility's market-based rate transactions and sales agreements that conformed to the utility's tariff.

3. In Order No. 2001, the Commission also adopted a new section in its regulations, 18 CFR 35.10b, which requires that the EQRs are to be prepared in conformance with the Commission's software and guidance posted and available from the Commission website. This obviates the need to revise 18 CFR 35.10b to implement revisions to the software and Start Printed Page 30544guidance. Since the issuance of Order No. 2001, as need has arisen, the Commission has issued orders to resolve questions raised by EQR users and has directed Staff to issue additional guidance.

4. On September 24, 2007, the Commission issued Order No. 2001-G, adopting an EQR Data Dictionary that collected in one document the definitions of certain terms and values used in filing EQR data (previously provided in Commission orders and in guidance materials posted at the Commission's website) and providing formal definitions for fields that were previously undefined. On December 20, 2007, the Commission issued Order No. 2001-H, which addressed a pending request for rehearing and clarifying the information to be reported in several EQR data fields.

5. In Order 2001-H, the Commission defined Contract Commencement Date, (Field 22 in the Contract Data section of the EQR), as:

The date the terms of the contract reported in the EQR were effective. If the terms reported in the Contract Data section of the EQR became effective or if service under those terms began on multiple dates (i.e.: due to an amendment), the date to be reported as the Commencement Date is the date when service began pursuant to the most recent amendment to the terms reported in the Contract Data section of the EQR.[3]

6. On February 26, 2008, the Commission held an EQR Technical Conference to “review the EQR Data Dictionary and address questions from EQR users.” [4] During this technical conference, Contract Commencement Date was a topic of considerable discussion.

7. On March 3, 2008, the Commission issued notice of a proposal to revise the EQR Data Dictionary to clarify the requirement to report all ancillary service transactions, consistent with the Commission's decision in Order No. 697 [5] that information about third party sales of ancillary services at market-based rates should be reported in EQR filings, rather than being reported on a separate OASIS-like Internet site.[6]

8. On April 10, 2008, in its response to the March 2008 Notice, Edison Electric Institute (EEI) included comments related to the definition of Commencement Date in Field 22.[7] Those issues are more pertinent to the notice we are issuing in the instant subdocket (i.e., RM08-1-010) than to the March 2008 Notice. We address those comments here.

Discussion

9. In Order No. 2001-H, the Commission clarified the information that should be reported in the Contract Execution Date and Contract Commencement Date fields. The Commission's findings on the information that should be reported in the Contract Execution Date and Contract Commencement Date fields was based on commenters' argument that Contract Execution Date (Field No. 21) should reflect the date the contract was originally signed.

10. In Order No. 2001-G, the Commission determined that the date a contract was “materially amended” was to be reported as the Contract Execution Date. Commenters argued that it would be helpful if, despite contract revisions, the Contract Execution Date would remain the date the contract was first executed, for the entire life of the contract.[8] It was argued that this would help EQR users understand exactly what contract was being referenced. In response to these concerns, in Order No. 2001-H, the Commission was persuaded to have the Contract Execution Date stay unchanged for the life of the contract.[9] In addition, given the Commission's interest in tracking the date of contract revisions, Order No. 2001-H provided that amendment dates would be reported in the Contract Commencement Date field. Thus, the Commission determined in Order No. 2001-H that Contract Commencement Date should report “[t]he date the terms of the contract reported in the EQR were effective.” [10] The terms of each contract reported in the EQR are represented by the thirty-one fields in each record of the Contract Data Section. The Commission determined that any changes in the reporting of these thirty-one fields would require a change in the Contract Commencement Date field.

11. At the February 2008 Technical Conference, Commission staff highlighted for EQR users the import of the changes adopted by the Commission in Order Nos. 2001-G and 2001-H. Although Order No. 2001-H was unchallenged when issued, some filers expressed concern at the February 2008 Technical Conference about the portion of the definition of Contract Commencement Date that describes using “the date when service began pursuant to the most recent amendment.” In addition, several participants were concerned that it would be difficult to identify the exact date when “service” begins.

12. The Contract Commencement Date is intended to reflect the effective date of either the contract or the most recent amendment. The language in question was added for clarity in two respects. First, where no effective date is provided in the contract or the amendment, the EQR filer should use the date service began under the contract as a substitute. Second, if there have been a number of amendments to the contract, the filer should use the date of the amendment that accounted for the most recent change in the terms reported in the EQR.

13. In its comments on the March 2008 Notice, EEI encouraged the Commission to confirm that Field 22 needs to be completed in conformance with the new definition only for contracts amended after January 1, 2008. EEI also suggests that the Commission should refine the definition of Contract Commencement Date so that revisions to Customer Company Name, Company DUNS Number, or Customer DUNS Number would not trigger a need for a revised Contract Commencement Date. EEI also suggests that Field 22 be given a different name that would better reflect the information that would be reported in this field.[11]

14. As a result of the discussions at the EQR Technical Conference and the points raised in the EEI comments in Docket No. RM01-8-009, the Commission invites comments on the following proposed definition of Contract Commencement Date:

The date the terms of the contract reported in the Contract Products section of the EQR (Field Nos. 26 through 45) were effective. If the terms reported in the Contract Data section of the EQR became effective on multiple dates (i.e.: due to one or more amendments), the date to be reported as the Commencement Date is the date the most recent amendment became effective. If the contract or the most recent reported amendment does not have an effective date, the date when service began pursuant to the contract or most recent reported amendment may be used. If the terms of the contract reported in the Contract Products section Start Printed Page 30545have not been amended since January 1, 2008, the initial date the contract became effective may be used.

15. The new definition clarifies the Commission's intention regarding the effective date of amendment. It also limits the types of changes that would require a new date to those affecting the products and services under the contract (the terms provided in Field Nos. 26 through 45); changes in the name of the counterparties to the contract, Field Nos. 15 and 16, for example, are not included. The new definition also allows the original contract commencement date to be used if the contract has not been amended since January 1, 2008, to simplify compliance with the revised requirement.

16. The Commission also invites comments regarding renaming Field 22 to “Commencement Date of Contract Terms” to reflect this revised definition.

Comment Procedures

17. The Commission invites interested persons to submit comments on the matters and issues proposed in this notice, including any related matters or alternative proposals that commenters may wish to discuss. Comments are due June 27, 2008. Comments must refer to Docket No. RM01-8-010, and must include the commenter's name, the organization they represent, if applicable, and their address. Comments may be filed either in electronic or paper format.

18. Comments may be filed electronically via the eFiling link on the Commission's Web site at http://www.ferc.gov. The Commission accepts most standard word processing formats and commenters may attach additional files with supporting information in certain other file formats. Commenters filing electronically do not need to make a paper filing. Commenters that are not able to file comments electronically must send an original and 14 copies of their comments to: Federal Energy Regulatory Commission, Secretary of the Commission, 888 First Street, NE., Washington, DC 20426.

19. All comments will be placed in the Commission's public files and may be viewed, printed, or downloaded remotely as described in the Document Availability section below. Commenters on this proposal are not required to serve copies of their comments on other commenters.

Document Availability

20. In addition to publishing the full text of this document in the Federal Register, the Commission provides all interested persons an opportunity to view and/or print the contents of this document via the Internet through the Commission's Home Page (http://www.ferc.gov) and in the Commission's Public Reference Room during normal business hours (8:30 a.m. to 5 p.m. Eastern time) at 888 First Street, NE., Room 2A, Washington, DC 20426.

21. From the Commission's Home Page on the Internet, this information is available in the eLibrary. The full text of this document is available in the eLibrary both in PDF and Microsoft Word format for viewing, printing, and/or downloading. To access this document in eLibrary, type the docket number excluding the last three digits of this document in the docket number field.

22. User assistance is available for eLibrary and the Commission's Web site during our normal business hours. For assistance contact FERC Online Support at FERCOnlineSupport@ferc.gov or toll-free at (866) 208-3676, or for TTY, contact (202) 502-8659.

Start Signature

By direction of the Commission.

Kimberly D. Bose,

Secretary.

End Signature

Attachment A—Proposed Revisions to Electric Quarterly Report Data Dictionary Version 1.1 (issued December 21, 2007)

EQR Data Dictionary

Field #FieldRequiredValueDefinition
ID Data
1Filer Unique IdentifierFR1(Respondent)—An identifier (i.e., “FR1”) used to designate a record containing Respondent identification information in a comma-delimited (csv) file that is imported into the EQR filing. Only one record with the FR1 identifier may be imported into an EQR for a given quarter.
1Filer Unique IdentifierFS# (where “#” is an integer)(Seller)—An identifier (e.g., “FS1”, “FS2”) used to designate a record containing Seller identification information in a comma-delimited (csv) file that is imported into the EQR filing. One record for each seller company may be imported into an EQR for a given quarter.
1Filer Unique IdentifierFA1(Agent)—An identifier (i.e., “FA1”) used to designate a record containing Agent identification information in a comma-delimited (csv) file that is imported into the EQR filing. Only one record with the FA1 identifier may be imported into an EQR for a given quarter.
2Company NameUnrestricted text (100 characters)(Respondent)—The name of the company taking responsibility for complying with the Commission's regulations related to the EQR.
2Company NameUnrestricted text (100 characters)(Seller)—The name of the company that is authorized to make sales as indicated in the company's FERC tariff(s). This name may be the same as the Company Name of the Respondent.
2Company NameUnrestricted text (100 characters)(Agent)—The name of the entity completing the EQR filing. The Agent's Company Name need not be the name of the company under Commission jurisdiction.
3Company DUNS Numberfor Respondent and SellerNine digit numberThe unique nine digit number assigned by Dun and Bradstreet to the company identified in Field Number 2.
4Contact NameUnrestricted text (50 characters)(Respondent)—Name of the person at the Respondent's company taking responsibility for compliance with the Commission's EQR regulations.
Start Printed Page 30546
4Contact NameUnrestricted text (50 characters)(Seller)—The name of the contact for the company authorized to make sales as indicated in the company's FERC tariff(s). This name may be the same as the Contact Name of the Respondent.
4Contact NameUnrestricted text (50 characters)(Agent)—Name of the contact for the Agent, usually the person who prepares the filing.
5Contact TitleUnrestricted text (50 characters)Title of contact identified in Field Number 4.
6Contact AddressUnrestricted textStreet address for contact identified in Field Number 4.
7Contact CityUnrestricted text (30 characters)City for the contact identified in Field Number 4.
8Contact StateUnrestricted text (2 characters)Two character state or province abbreviations for the contact identified in Field Number 4.
9Contact ZipUnrestricted text (10 characters)Zip code for the contact identified in Field Number 4.
10Contact Country NameCA—Canada, MX—Mexico, US—United States, UK—United KingdomCountry (USA, Canada, Mexico, or United Kingdom) for contact address identified in Field Number 4.
11Contact PhoneUnrestricted text (20 characters)Phone number of contact identified in Field Number 4.
12Contact E-MailUnrestricted textE-mail address of contact identified in Field Number 4.
13Filing QuarterYYYYMMA six digit reference number used by the EQR software to indicate the quarter and year of the filing for the purpose of importing data from csv files. The first 4 numbers represent the year (e.g. 2007). The last 2 numbers represent the last month of the quarter (e.g., 03=1st quarter; 06=2nd quarter, 09=3rd quarter, 12=4th quarter).
Contract Data
14Contract Unique IDAn integer proceeded by the letter “C” (only used when importing contract data)An identifier beginning with the letter “C” and followed by a number (e.g., “C1”, “C2”) used to designate a record containing contract information in a comma-delimited (csv) file that is imported into the EQR filing. One record for each contract product may be imported into an EQR for a given quarter.
15Seller Company NameUnrestricted text (100 characters)The name of the company that is authorized to make sales as indicated in the company's FERC tariff(s). This name must match the name provided as a Seller's “Company Name” in Field Number 2 of the ID Data (Seller Data).
16Customer Company NameUnrestricted text (70 characters)The name of the counterparty.
17Customer DUNS NumberNine digit numberThe unique nine digit number assigned by Dun and Bradstreet to the company identified in Field Number 16.
18Contract AffiliateY (Yes), N (No)The customer is an affiliate if it controls, is controlled by or is under common control with the seller. This includes a division that operates as a functional unit. A customer of a seller who is an Exempt Wholesale Generator may be defined as an affiliate under the Public Utility Holding Company Act and the FPA.
19FERC Tariff ReferenceUnrestricted text (60 characters)The FERC tariff reference cites the document that specifies the terms and conditions under which a Seller is authorized to make transmission sales, power sales or sales of related jurisdictional services at cost-based rates or at market-based rates. If the sales are market-based, the tariff that is specified in the FERC order granting the Seller Market Based Rate Authority must be listed.
20Contract Service Agreement IDUnrestricted text (30 characters)Unique identifier given to each service agreement that can be used by the filing company to produce the agreement, if requested. The identifier may be the number assigned by FERC for those service agreements that have been filed with and accepted by the Commission, or it may be generated as part of an internal identification system.
21Contract Execution DateYYYYMMDDThe date the contract was signed. If the parties signed on different dates, use the most recent date signed.
Start Printed Page 30547
22Commencement Date of Contract TermsYYYYMMDDThe date the terms of the contract reported in the Contract Products section of the EQR (Field Nos. 26 through 45) were effective. If the terms reported in the Contract Data section of the EQR became effective on multiple dates (i.e.: due to one or more amendments), the date to be reported as the Commencement Date is the date the most recent amendment became effective. If the contract or the most recent reported amendment does not have an effective date, the date when service began pursuant to the contract or most recent amendment may be used. If the terms of the contract reported in the Contract Products section have not been amended since January 1, 2008, the initial date the contract became effective may be used.
23Contract Termination DateIf specified in the contractYYYYMMDDThe date that the contract expires.
24Actual Termination Date ExtensionIf contract terminatedYYYYMMDDThe date the contract actually terminates.
25Provision DescriptionUnrestricted textDescription of terms that provide for the continuation of the contract.
26Class NameSee definitions of each class name below.
26Class NameF—FirmFor transmission sales, a service or product that always has priority over non-firm service. For power sales, a service or product that is not interruptible for economic reasons.
26Class NameNF—Non-firmFor transmission sales, a service that is reserved and/or scheduled on an as-available basis and is subject to curtailment or interruption at a lesser priority compared to Firm service. For an energy sale, a service or product for which delivery or receipt of the energy may be interrupted for any reason or no reason, without liability on the part of either the buyer or seller.
26Class NameUP—Unit Power SaleDesignates a dedicated sale of energy and capacity from one or more than one specified generation unit(s).
26Class NameN/A—Not ApplicableTo be used only when the other available Class Names do not apply.
27Term NameLT—Long Term, ST—Short Term, N/A—Not ApplicableContracts with durations of one year or greater are long-term. Contracts with shorter durations are short-term.
28Increment NameSee definitions for each increment below.
28Increment NameH—HourlyTerms of the contract (if specifically noted in the contract) set for up to 6 consecutive hours (≤6 consecutive hours).
28Increment NameD—DailyTerms of the contract (if specifically noted in the contract) set for more than 6 and up to 60 consecutive hours (>6 and ≤60 consecutive hours).
28Increment NameW—WeeklyTerms of the contract (if specifically noted in the contract) set for over 60 consecutive hours and up to 168 consecutive hours (>60 and <168 consecutive hours).
28Increment NameM—MonthlyTerms of the contract (if specifically noted in the contract) set for more than 168 consecutive hours up to, but not including, one year (>168 consecutive hours and <1 year).
28Increment NameY—YearlyTerms of the contract (if specifically noted in the contract) set for one year or more (≥1 year).
28Increment NameN/A—Not ApplicableTerms of the contract do not specify an increment.
29Increment Peaking NameSee definitions for each increment peaking name below.
29Increment Peaking NameFP—Full PeriodThe product described may be sold during those hours designated as on-peak and off-peak in the NERC region of the point of delivery.
29Increment Peaking NameOP—Off-PeakThe product described may be sold only during those hours designated as off-peak in the NERC region of the point of delivery.
29Increment Peaking NameP—PeakThe product described may be sold only during those hours designated as on-peak in the NERC region of the point of delivery.
29Increment Peaking NameN/A—Not ApplicableTo be used only when the increment peaking name is not specified in the contract.
30Product Type NameSee definitions for each product type below.
30Product Type NameCB—Cost BasedEnergy or capacity sold under a FERC-approved cost-based rate tariff.
Start Printed Page 30548
30Product Type NameCR—Capacity ReassignmentAn agreement under which a transmission provider sells, assigns or transfers all or portion of its rights to an eligible customer.
30Product Type NameMB—Market BasedEnergy or capacity sold under the seller's FERC-approved market-based rate tariff.
30Product Type NameT—TransmissionThe product is sold under a FERC-approved transmission tariff.
30Product Type NameOtherThe product cannot be characterized by the other product type names.
31Product NameSee Product Name Table, Appendix ADescription of product being offered.
32QuantityIf specified in the contractNumber with up to 4 decimalsQuantity for the contract product identified.
33UnitsIf specified in the contractSee Units Table, Appendix EMeasure stated in the contract for the product sold.
34RateOne of four rate fields (34, 35, 36, or 37) must be includedNumber with up to 4 decimalsThe charge for the product per unit as stated in the contract.
35Rate MinimumOne of four rate fields (34, 35, 36, or 37) must be includedNumber with up to 4 decimalsMinimum rate to be charged per the contract, if a range is specified.
36Rate MaximumOne of four rate fields (34, 35, 36, or 37) must be includedNumber with up to 4 decimalsMaximum rate to be charged per the contract, if a range is specified.
37Rate DescriptionOne of four rate fields (34, 35, 36, or 37) must be includedUnrestricted textText description of rate. If the rate is currently available on the FERC website, a citation of the FERC Accession Number and the relevant FERC tariff including page number or section may be included instead of providing the entire rate algorithm. If the rate is not available on the FERC website, include the rate algorithm, if rate is calculated. If the algorithm would exceed the 150 character field limit, it may be provided in a descriptive summary (including bases and methods of calculations) with a detailed citation of the relevant FERC tariff including page number and section. If more than 150 characters are required, the contract product may be repeated in a subsequent line of data until the rate is adequately described.
38Rate UnitsIf specified in the contractSee Rate Units Table, Appendix FMeasure stated in the contract for the product sold.
39Point of Receipt Balancing Authority (PORBA)If specified in the contractSee Balancing Authority Table, Appendix BThe registered NERC Balancing Authority (formerly called NERC Control Area) where service begins for a transmission or transmission-related jurisdictional sale. The Balancing Authority will be identified with the abbreviation used in OASIS applications. If receipt occurs at a trading hub specified in the EQR software, the term “Hub” should be used.
40Point of Receipt Specific Location (PORSL)If specified in the contractUnrestricted text (50 characters). If “HUB” is selected for PORCA, see Hub Table, Appendix CThe specific location at which the product is received if designated in the contract. If receipt occurs at a trading hub, a standardized hub name must be used. If more points of receipt are listed in the contract than can fit into the 50 character space, a description of the collection of points may be used. “Various,” alone, is unacceptable unless the contract itself uses that terminology.
41Point of Delivery Balancing Authority (PODBA)If specified in the contractSee Balancing Authority Table, Appendix BThe registered NERC Balancing Authority (formerly called NERC Control Area) where a jurisdictional product is delivered and/or service ends for a transmission or transmission-related jurisdictional sale. The Balancing Authority will be identified with the abbreviation used in OASIS applications. If delivery occurs at the interconnection of two control areas, the control area that the product is entering should be used. If delivery occurs at a trading hub specified in the EQR software, the term “Hub” should be used.
Start Printed Page 30549
42Point of Delivery Specific Location (PODSL)If specified in the contractUnrestricted text (50 characters). If “HUB” is selected for PODCA, see Hub Table, Appendix CThe specific location at which the product is delivered if designated in the contract. If receipt occurs at a trading hub, a standardized hub name must be used.
43Begin DateIf specified in the contractYYYYMMDDHHMMFirst date for the sale of the product at the rate specified.
44End DateIf specified in the contractYYYYMMDDHHMMLast date for the sale of the product at the rate specified.
45Time ZoneSee Time Zone Table, Appendix DThe time zone in which the sales will be made under the contract.
Transaction Data
46Transaction Unique IDAn integer proceeded by the letter “T” (only used when importing transaction data)An identifier beginning with the letter “T” and followed by a number (e.g., “T1”, “T2”) used to designate a record containing transaction information in a comma-delimited (csv) file that is imported into the EQR filing. One record for each transaction record may be imported into an EQR for a given quarter. A new transaction record must be used every time a price changes in a sale.
47Seller Company NameUnrestricted text (100 Characters)The name of the company that is authorized to make sales as indicated in the company's FERC tariff(s). This name must match the name provided as a Seller's “Company Name” in Field 2 of the ID Data (Seller Data).
48Customer Company NameUnrestricted text (70 Characters)The name of the counterparty.
49Customer DUNS NumberNine digit numberThe unique nine digit number assigned by Dun and Bradstreet to the counterparty to the contract.
50FERC Tariff ReferenceUnrestricted text (60 Characters)The FERC tariff reference cites the document that specifies the terms and conditions under which a Seller is authorized to make transmission sales, power sales or sales of related jurisdictional services at cost-based rates or at market-based rates. If the sales are market-based, the tariff that is specified in the FERC order granting the Seller Market Based Rate Authority must be listed.
51Contract Service Agreement IDUnrestricted text (30 Characters)Unique identifier given to each service agreement that can be used by the filing company to produce the agreement, if requested. The identifier may be the number assigned by FERC for those service agreements that have been filed and approved by the Commission, or it may be generated as part of an internal identification system.
52Transaction Unique IdentifierUnrestricted text (24 Characters)Unique reference number assigned by the seller for each transaction.
53Transaction Begin DateYYYYMMDDHHMM (csv import), MMDDYYYYHHMM (manual entry)First date and time the product is sold during the quarter.
54Transaction End DateYYYYMMDDHHMM (csv import), MMDDYYYYHHMM (manual entry)Last date and time the product is sold during the quarter.
55Time ZoneSee Time Zone Table, Appendix DThe time zone in which the sales will be made under the contract.
56Point of Delivery Balancing Authority (PODBA)See Balancing Authority Table, Appendix BThe registered NERC Balancing Authority (formerly called NERC Control Area) abbreviation used in OASIS applications.
57Point of Delivery Specific Location (PODSL)Unrestricted text (50 characters). If “HUB” is selected for PODBA, see Hub Table, Appendix CThe specific location at which the product is delivered. If receipt occurs at a trading hub, a standardized hub name must be used.
58Class NameSee class name definitions below.
Start Printed Page 30550
58Class NameF—FirmA sale, service or product that is not interruptible for economic reasons.
58Class NameNF—Non-firmA sale for which delivery or receipt of the energy may be interrupted for any reason or no reason, without liability on the part of either the buyer or seller.
58Class NameUP—Unit Power SaleDesignates a dedicated sale of energy and capacity from one or more than one specified generation unit(s).
58Class NameBA—Billing AdjustmentDesignates an incremental material change to one or more transactions due to a change in settlement results. “BA” may be used in a refiling after the next quarter's filing is due to reflect the receipt of new information. It may not be used to correct an inaccurate filing.
58Class NameN/A—Not ApplicableTo be used only when the other available class names do not apply.
59Term NameLT—Long Term, ST—Short Term, N/A—Not ApplicablePower sales transactions with durations of one year or greater are long-term. Transactions with shorter durations are short-term.
60Increment NameSee increment name definitions below.
60Increment NameH—HourlyTerms of the particular sale set for up to 6 consecutive hours (≤ 6 consecutive hours) Includes LMP based sales in ISO/RTO markets.
60Increment NameD—DailyTerms of the particular sale set for more than 6 and up to 60 consecutive hours (>6 and ≤ 60 consecutive hours) Includes sales over a peak or off-peak block during a single day.
60Increment NameW—WeeklyTerms of the particular sale set for over 60 consecutive hours and up to 168 consecutive hours (>60 and ≤ 168 consecutive hours). Includes sales for a full week and sales for peak and off-peak blocks over a particular week.
60Increment NameM—MonthlyTerms of the particular sale set for set for more than 168 consecutive hours up to, but not including, one year (>168 consecutive hours and < 1 year). Includes sales for full month or multi-week sales during a given month.
60Increment NameY—YearlyTerms of the particular sale set for one year or more (≥ 1 year). Includes all long-term contracts with defined pricing terms (fixed-price, formula, or index).
60Increment NameN/A—Not ApplicableTo be used only when other available increment names do not apply.
61Increment Peaking NameSee definitions for increment peaking below.
61Increment Peaking NameFP—Full PeriodThe product described was sold during Peak and Off-Peak hours.
61Increment Peaking NameOP—Off-PeakThe product described was sold only during those hours designated as off-peak in the NERC region of the point of delivery.
61Increment Peaking NameP—PeakThe product described was sold only during those hours designated as on-peak in the NERC region of the point of delivery.
61Increment Peaking NameN/A—Not ApplicableTo be used only when the other available increment peaking names do not apply.
62Product NameSee Product Names, Table, Appendix ADescription of product being offered.
63Transaction QuantityNumber with up to 4 decimalsThe quantity of the product in this transaction.
64PriceNumber with up to 6 decimalsActual price charged for the product per unit. The price reported cannot be averaged or otherwise aggregated.
65Rate UnitsSee Rate Units Table, Appendix FMeasure appropriate to the price of the product sold.
66Total Transmission ChargeNumber with up to 2 decimalsPayments received for transmission services when explicitly identified.
67Total Transaction ChargeNumber with up to 2 decimalsTransaction Quantity (Field 63) times Price (Field 64) plus Total Transmission Charge (Field 66).
Start Printed Page 30551

EQR Data Dictionary

Product NameContract productTransaction productDefinition
Appendix A. Product Names
BLACK START SERVICEService available after a system-wide blackout where a generator participates in system restoration activities without the availability of an outside electric supply (ancillary Service).
BOOKED OUT POWEREnergy or capacity contractually committed bilaterally for delivery but not actually delivered due to some offsetting or countervailing trade (Transaction only).
CAPACITYA quantity of demand that is charged on a $/KW or $/MW basis.
CUSTOMER CHARGEFixed contractual charges assessed on a per customer basis that could include billing service.
DIRECT ASSIGNMENT FACILITIES CHARGECharges for facilities or portions of facilities that are constructed or used for the sole use/benefit of a particular customer.
EMERGENCY ENERGYContractual provisions to supply energy or capacity to another entity during critical situations.
ENERGYA quantity of electricity that is sold or transmitted over a period of time.
ENERGY IMBALANCEService provided when a difference occurs between the scheduled and the actual delivery of energy to a load obligation.
EXCHANGETransaction whereby the receiver accepts delivery of energy for a supplier's account and returns energy at times, rates, and in amounts as mutually agreed if the receiver is not an RTO/ISO.
FUEL CHARGECharge based on the cost or amount of fuel used for generation.
GRANDFATHERED BUNDLEDServices provided for bundled transmission, ancillary services and energy under contracts effective prior to Order No. 888's OATTs.
INTERCONNECTION AGREEMENTContract that provides the terms and conditions for a generator, distribution system owner, transmission owner, transmission provider, or transmission system to physically connect to a transmission system or distribution system.
MEMBERSHIP AGREEMENTAgreement to participate and be subject to rules of a system operator.
MUST RUN AGREEMENTAn agreement that requires a unit to run.
NEGOTIATED-RATE TRANSMISSIONTransmission performed under a negotiated rate contract (applies only to merchant transmission companies).
NETWORKTransmission service under contract providing network service.
NETWORK OPERATING AGREEMENTAn executed agreement that contains the terms and conditions under which a network customer operates its facilities and the technical and operational matters associated with the implementation of network integration transmission service.
OTHERProduct name not otherwise included.
POINT-TO-POINT AGREEMENTTransmission service under contract between specified Points of Receipt and Delivery.
REACTIVE SUPPLY & VOLTAGE CONTROLProduction or absorption of reactive power to maintain voltage levels on transmission systems (Ancillary Service).
REAL POWER TRANSMISSION LOSSThe loss of energy, resulting from transporting power over a transmission system.
REGULATION & FREQUENCY RESPONSEService providing for continuous balancing of resources (generation and interchange) with load, and for maintaining scheduled interconnection frequency by committing on-line generation where output is raised or lowered and by other non-generation resources capable of providing this service as necessary to follow the moment-by-moment changes in load (Ancillary Service).
REQUIREMENTS SERVICEFirm, load-following power supply necessary to serve a specified share of customer's aggregate load during the term of the agreement. Requirements service may include some or all of the energy, capacity and ancillary service products. (If the components of the requirements service are priced separately, they should be reported separately in the transactions tab.)
SCHEDULE SYSTEM CONTROL & DISPATCHScheduling, confirming and implementing an interchange schedule with other Balancing Authorities, including intermediary Balancing Authorities providing transmission service, and ensuring operational security during the interchange transaction (Ancillary Service).
SPINNING RESERVEUnloaded synchronized generating capacity that is immediately responsive to system frequency and that is capable of being loaded in a short time period or non-generation resources capable of providing this service (Ancillary Service).
SUPPLEMENTAL RESERVEService needed to serve load in the event of a system contingency, available with greater delay than SPINNING RESERVE. This service may be provided by generating units that are on-line but unloaded, by quick-start generation, or by interruptible load or other non-generation resources capable of providing this service (Ancillary Service).
SYSTEM OPERATING AGREEMENTSAn executed agreement that contains the terms and conditions under which a system or network customer shall operate its facilities and the technical and operational matters associated with the implementation of network.
TOLLING ENERGYEnergy sold from a plant whereby the buyer provides fuel to a generator (seller) and receives power in return for pre-established fees.
Start Printed Page 30552
TRANSMISSION OWNERS AGREEMENTThe agreement that establishes the terms and conditions under which a transmission owner transfers operational control over designated transmission facilities.
UPLIFTA make-whole payment by an RTO/ISO to a utility.

EQR Data Dictionary

Balancing authorityAbbreviationOutside US *
Appendix B. Balancing Authority
AESC, LLC—Wheatland CINAEWC
Alabama Electric Cooperative, Inc.AEC
Alberta Electric System OperatorAESO
Alliant Energy Corporate Services, LLC—EastALTE
Alliant Energy Corporate Services, LLC—WestALTW
Ameren TransmissionAMRN
Ameren Transmission. IllinoisAMIL
Ameren Transmission. MissouriAMMO
American Transmission Systems, Inc.FE
Aquila Networks—KansasWPEK
Aquila Networks—Missouri Public ServiceMPS
Aquila Networks—West Plains DispatchWPEC
Arizona Public Service CompanyAZPS
Associated Electric Cooperative, Inc.AECI
Avista Corp.AVA
Batesville Balancing AuthorityBBA
Big Rivers Electric Corp.BREC
Board of Public UtilitiesKACY
Bonneville Power Administration TransmissionBPAT
British Columbia Transmission CorporationBCTC
California Independent System OperatorCISO
Carolina Power & Light Company—CPLWCPLW
Carolina Power and Light Company—EastCPLE
Central and SouthwestCSWS
Central Illinois Light CoCILC
Chelan County PUDCHPD
Cinergy CorporationCIN
City of HomesteadHST
City of Independence P & L Dept.INDN
City of TallahasseeTAL
City Water Light & PowerCWLP
Cleco Power LLCCLEC
Columbia Water & LightCWLD
Comision Federal de ElectricidadCFE
Constellation Energy Control and Dispatch—ArkansasPUPP
Constellation Energy Control and Dispatch—City of Benton, ARBUBA
Constellation Energy Control and Dispatch—City of Ruston, LADERS
Constellation Energy Control and Dispatch—Conway, ArkansasCNWY
Constellation Energy Control and Dispatch—Gila RiverGRMA
Constellation Energy Control and Dispatch—HarquehalaHGMA
Constellation Energy Control and Dispatch—North Little Rock, ARDENL
Constellation Energy Control and Dispatch—West Memphis, ArkansasWMUC
Dairyland Power CooperativeDPC
DECA, LLC—Arlington ValleyDEAA
Duke Energy CorporationDUK
East Kentucky Power Cooperative, Inc.EKPC
El Paso ElectricEPE
Electric Energy, Inc.EEI
Empire District Electric Co., TheEDE
EntergyEES
ERCOT ISOERCO
Florida Municipal Power PoolFMPP
Florida Power & LightFPL
Florida Power CorporationFPC
Gainesville Regional UtilitiesGVL
Georgia System Operations CorporationGSOC
Georgia Transmission CorporationGTC
Grand River Dam AuthorityGRDA
Start Printed Page 30553
Grant County PUD No. 2GCPD
Great River EnergyGRE
Great River EnergyGREC
Great River EnergyGREN
Great River EnergyGRES
GridAmericaGA
Hoosier EnergyHE
Hydro-Quebec, TransEnergieHQT
Idaho Power CompanyIPCO
Illinois Power Co.IP
Illinois Power Co.IPRV
Imperial Irrigation DistrictIID
Indianapolis Power & Light CompanyIPL
ISO New England Inc.ISNE
JEAJEA
Kansas City Power & Light, CoKCPL
Lafayette Utilities SystemLAFA
LG & E Energy Transmission ServicesLGEE
Lincoln Electric SystemLES
Los Angeles Department of Water and PowerLDWP
Louisiana Energy & Power AuthorityLEPA
Louisiana Generating, LLCLAGN
Madison Gas and Electric CompanyMGE
Manitoba Hydro Electric Board, Transmission ServicesMHEB
Michigan Electric Coordinated SystemMECS
Michigan Electric Coordinated System—CONSCONS
Michigan Electric Coordinated System—DECODECO
MidAmerican Energy CompanyMEC
Midwest ISOMISO
Minnesota Power, Inc.MP
Montana-Dakota Utilities Co.MDU
Muscatine Power and WaterMPW
Nebraska Public Power DistrictNPPD
Nevada Power CompanyNEVP
New Brunswick Power CorporationNBPC
New Horizons Electric CooperativeNHC1
New York Independent System OperatorNYIS
North American Electric Reliability CouncilTEST
Northern Indiana Public Service CompanyNIPS
Northern States Power CompanyNSP
NorthWestern EnergyNWMT
Ohio Valley Electric CorporationOVEC
Oklahoma Gas and ElectricOKGE
Ontario—Independent Electricity Market OperatorIMO
OPPD CA/TPOPPD
Otter Tail Power CompanyOTP
P.U.D. No. 1 of Douglas CountyDOPD
PacifiCorp-EastPACE
PacifiCorp-WestPACW
PJM InterconnectionPJM
Portland General ElectricPGE
Public Service Company of ColoradoPSCO
Public Service Company of New MexicoPNM
Puget Sound Energy TransmissionPSEI
Reedy Creek Improvement DistrictRC
Sacramento Municipal Utility DistrictSMUD
Salt River ProjectSRP
Santee CooperSC
SaskPower Grid Control CentreSPC
Seattle City LightSCL
Seminole Electric CooperativeSEC
Sierra Pacific Power Co.—TransmissionSPPC
South Carolina Electric & Gas CompanySCEG
South Mississippi Electric Power AssociationSME
South Mississippi Electric Power AssociationSMEE
Southeastern Power Administration—HartwellSEHA
Southeastern Power Administration—RussellSERU
Southeastern Power Administration—ThurmondSETH
Southern Company Services, Inc.SOCO
Southern Illinois Power CooperativeSIPC
Southern Indiana Gas & Electric Co.SIGE
Start Printed Page 30554
Southern Minnesota Municipal Power AgencySMP
Southwest Power PoolSWPP
Southwestern Power AdministrationSPA
Southwestern Public Service CompanySPS
Sunflower Electric Power CorporationSECI
Tacoma PowerTPWR
Tampa Electric CompanyTEC
Tennessee Valley Authority ESOTVA
Trading HubHUB
TRANSLink Management CompanyTLKN
Tucson Electric Power CompanyTEPC
Turlock Irrigation DistrictTIDC
Upper Peninsula Power Co.UPPC
Utilities Commission, City of New Smyrna BeachNSB
Westar Energy—MoPEP CitiesMOWR
Western Area Power Administration—Colorado-MissouriWACM
Western Area Power Administration—Lower ColoradoWALC
Western Area Power Administration—Upper Great Plains EastWAUE
Western Area Power Administration—Upper Great Plains WestWAUW
Western Farmers Electric CooperativeWFEC
Western Resources dba Westar EnergyWR
Wisconsin Energy CorporationWEC
Wisconsin Public Service CorporationWPS
Yadkin, Inc.YAD
* Balancing authorities outside the United States may only be used in the Contract Data section to identify specified receipt/delivery points in jurisdictional transmission contracts.

EQR Data Dictionary

HUBDefinition
Appendix C. Hub
ADHUBThe aggregated Locational Marginal Price (“LMP”) nodes defined by PJM Interconnection, LLC as the AEP/Dayton Hub.
AEPGenHubThe aggregated Locational Marginal Price (“LMP”) nodes defined by PJM Interconnection, LLC as the AEPGenHub.
COBThe set of delivery points along the California-Oregon commonly identified as and agreed to by the counterparties to constitute the COB Hub.
Cinergy (into)The set of delivery points commonly identified as and agreed to by the counterparties to constitute delivery into the Cinergy balancing authority.
Cinergy Hub (MISO)The aggregated Elemental Pricing nodes (“Epnodes”) defined by the Midwest Independent Transmission System Operator, Inc., as Cinergy Hub (MISO).
Entergy (into)The set of delivery points commonly identified as and agreed to by the counterparties to constitute delivery into the Entergy balancing authority.
FE HubThe aggregated Elemental Pricing nodes (“Epnodes”) defined by the Midwest Independent Transmission System Operator, Inc., as FE Hub (MISO).
Four CornersThe set of delivery points at the Four Corners power plant commonly identified as and agreed to by the counterparties to constitute the Four Corners Hub.
Illinois Hub (MISO)The aggregated Elemental Pricing nodes (“Epnodes”) defined by the Midwest Independent Transmission System Operator, Inc., as Illinois Hub (MISO).
MeadThe set of delivery points at or near Hoover Dam commonly identified as and agreed to by the counterparties to constitute the Mead Hub.
Michigan Hub (MISO)The aggregated Elemental Pricing nodes (“Epnodes”) defined by the Midwest Independent Transmission System Operator, Inc., as Michigan Hub (MISO).
Mid-Columbia (Mid-C)The set of delivery points along the Columbia River commonly identified as and agreed to by the counterparties to constitute the Mid-Columbia Hub.
Minnesota Hub (MISO)The aggregated Elemental Pricing nodes (“Epnodes”) defined by the Midwest Independent Transmission System Operator, Inc., as Minnesota Hub (MISO).
NEPOOL (Mass Hub)The aggregated Locational Marginal Price (“LMP”) nodes defined by ISO New England Inc., as Mass Hub.
NIHUBThe aggregated Locational Marginal Price (“LMP”) nodes defined by PJM Interconnection, LLC as the Northern Illinois Hub.
NOBThe set of delivery points along the Nevada-Oregon border commonly identified as and agreed to by the counterparties to constitute the NOB Hub.
NP15The set of delivery points north of Path 15 on the California transmission grid commonly identified as and agreed to by the counterparties to constitute the NP15 Hub.
NWMTThe set of delivery points commonly identified as and agreed to by the counterparties to constitute delivery into the Northwestern Energy Montana balancing authority.
PJM East HubThe aggregated Locational Marginal Price nodes (“LMP”) defined by PJM Interconnection, LLC as the PJM East Hub.
Start Printed Page 30555
PJM South HubThe aggregated Locational Marginal Price (“LMP”) nodes defined by PJM Interconnection, LLC as the PJM South Hub.
PJM West HubThe aggregated Locational Marginal Price (“LMP”) nodes defined by PJM Interconnection, LLC as the PJM Western Hub.
Palo VerdeThe switch yard at the Palo Verde nuclear power station west of Phoenix in Arizona. Palo Verde Hub includes the Hassayampa switchyard 2 miles south of Palo Verde.
SOCO (into)The set of delivery points commonly identified as and agreed to by the counterparties to constitute delivery into the Southern Company balancing authority.
SP15The set of delivery points south of Path 15 on the California transmission grid commonly identified as and agreed to by the counterparties to constitute the SP15 Hub.
TVA (into)The set of delivery points commonly identified as and agreed to by the counterparties to constitute delivery into the Tennessee Valley Authority balancing authority.
ZP26The set of delivery points associated with Path 26 on the California transmission grid commonly identified as and agreed to by the counterparties to constitute the ZP26 Hub.

EQR Data Dictionary

Time zoneDefinition
Appendix D. Time Zone
ADAtlantic Daylight
APAtlantic Prevailing
ASAtlantic Standard
CDCentral Daylight
CPCentral Prevailing
CSCentral Standard
EDEastern Daylight
EPEastern Prevailing
ESEastern Standard
MDMountain Daylight
MPMountain Prevailing
MSMountain Standard
NANot Applicable
PDPacific Daylight
PPPacific Prevailing
PSPacific Standard
UTUniversal Time

EQR Data Dictionary

UnitsDefinition
Appendix E. Units
KVKilovolt
KVAKilovolt Amperes
KVRKilovar
KWKilowatt
KWHKilowatt Hour
KW-DAYKilowatt Day
KW-MOKilowatt Month
KW-WKKilowatt Week
KW-YRKilowatt Year
MVAR-YRMegavar Year
MWMegawatt
MWHMegawatt Hour
MW-DAYMegawatt Day
MW-MOMegawatt Month
MW-WKMegawatt Week
MW-YRMegawatt Year
RKVAReactive Kilovolt Amperes
FLAT RATEFlat Rate

EQR Data Dictionary

Rate unitsDefinition
Appendix F. Rate Units
$/KVdollars per kilovolt
$/KVAdollars per kilovolt amperes
$/KVRdollars per kilovar
$/KWdollars per kilowatt
$/KWHdollars per kilowatt hour
$/KW-DAYdollars per kilowatt day
$/KW-MOdollars per kilowatt month
$/KW-WKdollars per kilowatt week
$/KW-YRdollars per kilowatt year
$/MWdollars per megawatt
$/MWHdollars per megawatt hour
$/MW-DAYdollars per megawatt day
$/MW-MOdollars per megawatt month
$/MW-WKdollars per megawatt week
$/MW-YRdollars per megawatt year
$/MVAR-YRdollars per megavar year
$/RKVAdollars per reactive kilovar amperes
CENTScents
CENTS/KVRcents per kilovolt amperes
CENTS/KWHcents per kilowatt hour
FLAT RATErate not specified in any other units
End Supplemental Information

Footnotes

1.  Revised Public Utility Filing Requirements, Order No. 2001, 67 FR 31043 (May 8, 2002), FERC Stats. & Regs. ¶ 31,127 (Apr. 25, 2002), reh'g denied, Order No. 2001-A, 100 FERC ¶ 61,074, reconsideration and clarification denied, Order No. 2001-B, 100 FERC ¶ 61,342, order directing filings, Order No. 2001-C, 101 FERC ¶ 61,314 (2002), Order No. 2001-D, order directing filings, 102 FERC 61,334, Order No. 2001-E, order refining filing requirements, 105 FERC ¶ 61,352 (2003), clarification order, Order No.2001-F, 106 FERC ¶ 61,060 (2004), order adopting EQR Data Dictionary, Order No. 2001-G, 120 FERC ¶ 61,270 (2007), order on reh'g and clarification, Order No. 2001-H, 121 FERC ¶ 61,289 (2007).

Back to Citation

3.  Order 2001-H, Data Dictionary at Field 22. There were no requests for rehearing or appeal filed in response to Order No. 2001-H.

Back to Citation

4.  See Notice of Electric Quarterly Reports Technical Conference, January 7, 2008 (http://www.ferc.gov/​EventCalendar/​Files/​20080108075834-RM01-8-000TC.pdf).

Back to Citation

5.  Market-Based Rates for Wholesale Sales of Electric Energy, Capacity and Ancillary Services by Public Utilities, Order No. 697, 72 FR 39904 (July 20, 2007), FERC Stats. & Regs. ¶ 31,252 (June 21, 2007), clarifying order, 121 FERC ¶ 61,260 (2007).

Back to Citation

6.  Revised Public Utility Filing Requirements for Electric Quarterly Reports, 73 FR 12983 (Mar. 11, 2008), FERC Stats. & Regs. ¶ 35,557 (Mar. 3, 2008) (March 2008 Notice).

Back to Citation

7.  EEI Comments, Docket No. RM08-1-009 (filed April 10, 2007).

Back to Citation

8.  See Order No. 2001-H at P 8-9.

Back to Citation

9.  Id. at P 10.

Back to Citation

10.  Id. at Data Dictionary, Field 22.

Back to Citation

11.  EEI suggests that Field 22 be labeled as “Latest Modification Date.”

Back to Citation

[FR Doc. E8-11861 Filed 5-27-08; 8:45 am]

BILLING CODE 6717-01-P