Skip to Content

Notice

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 September 24, 2007.

AGENCY:

Federal Energy Regulatory Commission, DOE.

ACTION:

Order Adopting Electric Quarterly Report Data Dictionary.

SUMMARY:

The Federal Energy Regulatory Commission is adopting an Electric Quarterly Report (EQR) Data Dictionary that collects in one document the definitions of certain terms and values used in filing EQR data, in conformance with Commission Order No. 2001, which established revised public utility filing requirements.

DATES:

Effective Date: This order will become effective October 4, 2007.

Start Further Info

FOR FURTHER INFORMATION CONTACT:

Mark A. Blazejowski, Office of Enforcement, Federal Energy Regulatory Commission, 888 First Street, NE., Washington, DC 20426.

Gary D. Cohen, Office of the General Counsel, Federal Energy Regulatory Commission, 888 First Street, NE., Washington, DC 20426.

End Further Info End Preamble Start Supplemental Information

SUPPLEMENTARY INFORMATION:

Before Commissioners: Joseph T. Kelliher, Chairman; Suedeen G. Kelly, Marc Spitzer, Philip D. Moeller, and Jon Wellinghoff.

Order Adopting Electric Quarterly Report Data Dictionary

Issued September 24, 2007.

1. In this order, after consideration of the comments filed in response to our Start Printed Page 56736notice seeking comments,[1] we are adopting an Electric Quarterly Report (EQR) Data Dictionary that collects 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 Web site) and are issuing formal definitions for those fields that were previously undefined.

I. Background

2. On April 25, 2002, the Commission issued Order No. 2001, a final rule establishing revised public utility filing requirements.[2] This rule revised the Commission's filing requirements to require companies subject to the Commission's regulation under section 205 of the Federal Power Act (FPA) 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 Web site. This obviates the need to revise section 35.10b to implement revisions to the software and guidance. 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.[3]

4. Likewise, on December 23, 2003, the Commission issued Order No. 2001-E, to resolve some recurring issues faced by EQR filers, to help filers better understand the requirements of Order No. 2001, and to improve the quality and consistency of EQR data.[4] To this end, the Commission: (1) Ordered standard formats to be used for certain location fields; (2) established an EQR Refiling Policy; and (3) streamlined and defined allowable data entries in certain data fields. The Commission instructed Staff to issue filing guidance to address these changes.[5] This guidance was posted on the EQR page of the Commission's Web site on March 25, 2004.[6] Commission Staff posted additional guidance on the Internet at the http://www.ferc.gov Web site, and several EQR Users Group meetings have been held to address the questions of EQR filers.

5. After issuance of Order No. 2001-E, the Commission recognized that rapid change in the electric industry may require flexibility in adding or changing the entries allowed in restricted fields in the EQR. The North American Electric Reliability Corporation (NERC), for example, frequently adds and deletes balancing authorities (previously “control areas”) from its Transmission System Information Network (TSIN) rolls. In an order issued on March 25, 2004, the Commission directed Staff to alert EQR users of any future changes to allowable entries for restricted fields by e-mail, and to post these changes on the EQR page of the Commission's Web site.[7]

6. Since 2004, the Commission has performed outreach to the industry to determine which current EQR definitions are sufficient and understandable and which should be revised.[8] The Commission has concluded that, to improve the quality of EQR filings, it would be appropriate to place in a single document the definitions of certain terms and values used in filing EQR data and to issue formal definitions for those fields that are currently undefined. Thus, the Commission issued a notice (i.e., the EQR Notice) proposing the adoption of a formal EQR Data Dictionary. The EQR Notice was published in the Federal Register and, in it, the Commission invited comment on the proposed definitions.[9] A total of seven comments were filed in response to the EQR Notice.[10]

II. Discussion

7. With one exception, the comments in response to the EQR Notice were generally supportive of the proposal for the Commission to adopt an EQR Data Dictionary; [11] however, they made a number of suggestions on possible revisions to the definitions. We will now separately discuss each of these suggestions.

A. Field Nos. 2, 15 and 47—Seller Company Name

8. The EQR Notice proposed defining Seller Company Name as “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.”

9. EEI suggests that the definition of Company Name for the Seller be changed to add “or its agent as specified in the tariff (if the full name is over 70 characters).” EEI explains that this change is necessary to provide flexibility when there are multiple parties to a contract, exceeding the field's 70-character limit.

Commission Conclusion

10. Only companies that are authorized to sell power under Part 35 of the Commission's regulations should make sales in the wholesale power market. The EQR is intended to report the activities of those specific companies. The Seller information is used to identify those companies.

11. The Commission is not persuaded to revise the definition proposed in the EQR Notice as suggested by EEI. We find this suggestion unnecessary, because under the definition proposed in the EQR Notice, the agent may be identified as the Seller if the company's tariff authorizes the agent to make the sales, even without the language change suggested by EEI. However, we will expand the size of the Seller Company Start Printed Page 56737Name field to 100 characters to allow filers to identify those contracts where more than one party is involved as seller and/or where one party is acting as agent for (or on behalf of) one or more other parties.

B. Field Nos. 16 and 48—Customer Company Name

12. The EQR Notice proposed defining Customer Company Name as “The name of the counterparty to the contract.”

13. EEI suggests the phrase “to the contract” be deleted from the proposed definition of Customer Company Name to account for multi-lateral membership agreements where no bilateral contract is necessary.

Commission Conclusion

14. The suggested change meets the Commission's goal of further clarifying the intended meaning of the field. Thus, this order adopts this suggested revision to these fields.

C. Field Nos. 19 and 50—FERC Tariff Reference

15. The EQR Notice proposed defining FERC Tariff Reference as “The FERC tariff reference cites the document that specifies the terms and conditions under which a Seller is authorized to make transmission sales or power sales 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.”

16. EEI suggests the phrase “or sales of related jurisdictional services” be added to the definition of FERC Tariff Reference to clarify that jurisdictional services other than transmission or power sales should also be reported in the EQR. In addition, EEI requests that the Commission confirm that cost-based sales made under the Western Systems Power Pool (WSPP) Agreement should cite the WSPP tariff, and market-based sales made under the WSPP Agreement should cite the Seller's market-based rate tariff.

Commission Conclusion

17. We will adopt EEI's suggestion to add the phrase “or sales of related jurisdictional services” to the definition of FERC Tariff Reference because we agree that this phrase helps clarify that jurisdictional services other than transmission or power sales should be reported in the EQR. In addition, as requested by EEI, we confirm that cost-based sales made under the WSPP Agreement should cite the WSPP tariff, and market-based sales made under the WSPP Agreement should cite the Seller's market-based rate tariff. This interpretation is consistent with the proposed definition.

D. Field Nos. 20 and 51—Contract Service Agreement ID

18. The EQR Notice proposed defining Contract Service Agreement ID as “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.”

19. Transalta suggests a change to the proposed Contract Service Agreement ID definition so that the field need not be unique in itself but only unique when combined with the Customer Company Name (Field Nos. 16 and 48). Transalta explains that it does not assign unique identifiers to each of its service agreements. Instead, it has an identification number that may be assigned to multiple service agreements but which, when combined with the counterparty designation, allows Transalta to identify separate transactions within its system.

Commission Conclusion

20. In adopting the initial definition for this field in Order No. 2001, the Commission provided considerable latitude for this field. The company can use the number assigned by FERC to those service agreements that had previously been filed or the number could be assigned from an internal system.[12] The one requirement in the original definition was that the identifier be unique. The changes in the proposed definition were intended to clarify that the identifier may include alphabetical characters.[13]

21. The Contract Service Agreement ID serves the dual purpose of being a unique method for identifying a particular contract when it is requested and a means of tracking a contract and the activity under a contract from quarter to quarter. Adding a second free form text field to this method of identification decreases our ability to do this tracking. We will, therefore, not adopt Transalta's suggested change. Companies whose current Contract Service Agreement IDs are not compliant with this longstanding EQR requirement may consider using some type of customer identifier in their Contract Service Agreement ID to make it unique.

E. Field No. 21—Contract Execution Date

22. The EQR Notice proposed defining Contract Execution Date as “The date the contract was signed. If the parties signed on different dates, or there are contract amendments, use the most recent date signed.”

23. Both Reliant and EEI suggest that the Contact Execution Date should not change because of a minor amendment to the contract. Both commenters note that, frequently, contract amendments are minor changes such as changes in an address or payment terms that do not affect the key operational parameters of the agreement.

Commission Conclusion

24. We agree with Reliant and EEI that the usefulness of the data may be increased with a single execution date for each contract across all periods. However, if there are material amendments to the contract, then the contract execution date must be changed.

F. Field No. 23—Contract Termination Date

25. The EQR Notice proposed defining Contract Termination Date as “The date that the contract expires.”

26. Transalta expresses concern that this field requires filers to provide a Contract Termination Date even if none exists.

Commission Conclusion

27. We find Transalta's concern misplaced. As indicated in the EQR Notice, a Contract Termination Date is only required “if specified in the contract.” EQR filers, therefore, may continue leaving Field No. 23 blank for contracts without termination dates. Thus, we have not changed the proposed definition.

G. Field Nos. 26 and 58—Class Name

28. The EQR Notice proposed defining Class Name in the Contract Data section of the EQR as “F-Firm: For transmission sales, service or product that always has priority over non-firm service. For power sales, service or product that is not interruptible for economic reasons. NF-Nonfirm: For transmission sales, 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. An energy sale for which delivery or receipt of the energy may be interrupted for any Start Printed Page 56738reason or no reason, without liability on the part of either the buyer or seller. UP-Unit Power Sale: Designates a dedicated sale of energy and capacity from one or more than one generation unit(s). N/A-Not Applicable: To be used only when the other available Class Names do not apply.”

29. In addition, the Transaction Data section of the EQR Notice proposes to define the Class Name “BA-Billing Adjustment” (Field No. 58 only) as: “Incremental positive or negative material change to previous EQR totals.”

30. In its comments on the Class Name fields, EEI suggested some editorial changes to clarify the respective meanings of “Firm” and “Non-Firm.” EEI also recommends adding the word “specified” to clarify that the Class Name “UP-Unit Power Sale” is not intended to refer to general system firm sales.

31. Occidental suggests that the use of the Class Name “BA-Billing Adjustment” should be expanded to reflect changes that become available after a quarterly filing has been made, but before the next quarterly filing is due. Order No. 2001-E allowed the “BA” class name to be used for material changes after the next quarterly filing is due.[14] Occidental cites the effort required in truing up estimated California ISO sales data received prior to the EQR filing deadline with actual sales data received after the filing deadline.

Commission Conclusion

32. We will adopt EEI's suggested editorial changes to the terms “Firm” and “Non-Firm” and its suggestion to add the word “specified” to the Class Name “UP-Unit Power Sale” because we agree these changes add clarity.

33. As to Occidental's suggestion to expand the use of the Class Name “BA-Billing Adjustment” to include changes that become available after a quarterly filing has been made, the Commission already considered and rejected these arguments in developing the “BA” class name in Order No. 2001-E. The EQR is the Commission's primary means of fulfilling its statutory obligation to have entities' rates on file in a market where prices do not receive prior regulatory approval.[15] Changes in the EQR that would affect the accuracy of the rates provided must be carefully considered.

34. The “BA” class name is intended to be an option allowing EQR filers to reflect material price changes long after the settled prices were considered final. Occidental's observation that RTO/ISO sales data are likely to change after the EQR filing deadline strengthens the Commission's conviction that the data must be refiled to reflect the actual rates charged and that simply reflecting these changes as a single “BA” entry is insufficient. Given our finding on this issue, we believe that it would be helpful to revise the definition of “BA-Billing Adjustment” proposed in the EQR Notice to clarify the intended nature of the “BA” class name. Thus, we have revised the definition for “BA-Billing Adjustment” in the EQR Data Dictionary that we are adopting in this order to provide this clarification.

H. Field Nos. 28 and 60—Increment Name

35. The EQR Notice proposed defining Increment Name in the Contract Data section of the EQR as “H-Hourly: Terms of the contract (if specifically noted in the contract) set for up to 6 consecutive hours (≤6 consecutive hours). D-Daily: Terms of the contract (if specifically noted in the contract) set for more than 6 and up to 36 consecutive hours (>6 and ≤36 consecutive hours). W-Weekly: Terms of the contract (if specifically noted in the contract) set for over 36 consecutive hours and up to 168 consecutive hours (>36 and ≤168 consecutive hours). M-Monthly: Terms of the contract (if specifically noted in the contract) set for more than 168 consecutive hours up to one month (>168 consecutive hours and ≤1 month). Y-Yearly: Terms of the contract (if specifically noted in the contract) set for one year or more (≤1 year). S-Seasonal: Terms of the contract (if specifically noted in the contract) set for greater than one month and less than 365 consecutive days (> 1 month and < 1 year). N/A-Not Applicable: Terms of the contract do not specify an increment.” The definitions in the Transaction Data section are the same except that they refer to the “particular sale” rather than the “contract” as a whole.

36. Reliant, EEI, Occidental, and MISO each commented on the Increment Name definitions. Reliant recommends reverting to the definitions used as the basis for discussion at the EQR Users Group meeting on November 29, 2006.[16] Reliant appears to be interpreting the change from the discussion draft terminology of “one month or the balance of a month if longer than one week” to “more than 168 consecutive hours up to one month” as confusing the meaning of the definition because a peak-only sale for the course of a month would involve power flowing during no more than 16 consecutive hours.

37. MISO, EEI, and Occidental each offer alternative numbers of hours to define the increment names. For example, EEI and Occidental suggest different numbers to differentiate “D-Daily” and “W-Weekly” and MISO, EEI and Reliant request the deletion of the proposed increment name “S-Seasonal.”

Commission Conclusion

38. The Commission finds Reliant's suggested reading of the Increment Name definition to be problematic. The definition proposed in the EQR Notice used specific numbers of hours for the terms in order to simplify the process of implementing the definition and ensure consistency in the data. These specific numbers were not intended to change the meaning of the definition.

39. The Increment Name field is intended to provide information regarding the duration of the terms agreed upon in the contract or transaction. If completed correctly, this field provides information about whether a sale at a given price for a full day was the result of a daily sale or, possibly, a monthly sale with a daily index.

40. The proposed definitions expressly refer to the “terms of the contract” (Field No. 28) and the “terms of the particular sale” (Field No. 60). The definitions do not refer to the characteristics of the sales themselves. For example, a monthly peak-only sale priced on a daily index would be designated as “M” in Field No. 60 because the quantity sold, the hours of flow, and the pricing method are set for the entire month.

41. MISO, EEI, and Occidental each comment on the numbers of hours used to define the increment names. While MISO's suggested numbers are the simplest, they do not address the purpose of the field. For example, a single-day, peak-only sale would be classified as “H—Hourly” under MISO's definition even though industry practice would commonly refer to the deal as daily. We are not persuaded to make this change.

42. EEI and Occidental suggest different numbers to differentiate “D—Daily” and “W—Weekly.” The Commission proposed a break point at 36 hours. Occidental recommends 60 Start Printed Page 56739hours, explaining that sales with terms lasting over a long weekend are typically designated as “D” consistent with industry practice. EEI recommends 104 hours citing, but not expounding upon, industry practice. We find Occidental's explanation compelling and adopt 60 hours as the break point between “D” and “W.”

43. MISO, EEI and Reliant request the deletion of the proposed increment name “S—Seasonal” with adjustments in the “M—Monthly” and “Y—Yearly” definitions in light of the proposed changes to the other Increment Name definitions. We find this suggestion adds clarity and, thus, we will adopt this suggested revision.

I. Field No. 29—Increment Peaking Name

44. The EQR Notice proposed defining Increment Peaking Name as “FP—Full Period: The product described may be sold during all hours under the contract. OP—Off-Peak: The product described may be sold only during those hours designated as off-peak in the NERC region of the point of delivery. P—Peak: The product described may be sold only during those hours designated as on-peak in the NERC region of the point of delivery. N/A—Not Applicable: To be used only when the increment peaking name is not specified in the contract.”

45. EEI suggests that the definition for the Increment Peaking Name “FP—Full Period” be changed to clarify that sales under a contract need not occur around the clock to qualify as Full Period.

Commission Conclusion

46. The suggested change meets the Commission's goal of clarifying the definition of the field. Thus, the Commission will adopt this suggested change.

J. Field No. 30—Product Type Name

47. The EQR Notice proposed defining Product Type Name as “CB—Cost Based: Energy or capacity sold under a FERC-approved cost-based rate tariff. MB—Market Based: Energy sold under the seller's FERC-approved market-based rate tariff. T—Transmission: The product is sold under a FERC-approved transmission tariff. Other: The product cannot be characterized by the other product type names.”

48. EEI suggests that the words “or Capacity” be added to the definition of “MB-Market-Based” to clarify that capacity may be sold under a market-based tariff.

Commission Conclusion

49. EEI makes a valid point in identifying the proposed definition of “MB” as too restrictive. Accordingly, we will adopt EEI's suggested revision to the definition.

50. Under Order No. 890, all transmission capacity reassignments must “be accomplished by the assignee executing a service agreement with the transmission provider that will govern the provision of reassigned service” and those agreements must be reported in the providers' EQRs.[17] In preparing the EQR Data Dictionary, the term “Capacity Reassignment” was inadvertently included as a Product Name (Field Nos. 31 and 62, Appendix B) not a Product Type Name (Field No. 30) as described in Order 890.[18] This has been corrected in the attached EQR Data Dictionary that we are adopting in this order.

K. Field Nos. 31 and 62—Product Name

51. The EQR Notice proposed defining Product Name as “Description of product being offered.” See Appendix A for more specific definitions of product names.

52. Transalta requests clarification regarding whether a trade in which it sells power into an RTO/ISO's day ahead market at one point and simultaneously buys it back in the day ahead market at another point constitutes an “Exchange” as it has been defined. Because the proposed definition stipulates the return of energy “later at times, rates, and in amounts as mutually agreed,” [19] Transalta asks whether the definition applies to a simultaneous action.

Commission Conclusion

53. It was not the Commission's intention to exclude simultaneous trades at different locations from the definition of “Exchanges.” By including the word “later,” the definition also appears to be incorrectly excluding half the exchange activity—those sales that occur on the “return” side of the transaction. To clarify and correct the definition, the word “later” has been dropped.

54. The specific example that Transalta raises, where the counterparty is an ISO, is a special case. In Order No. 2001, the Commission exempted ISOs from transactional reporting where title does not pass to the ISO.[20] Further, several ISOs (New York Independent System Operator, Inc. (NYISO), MISO, and ISO New England, Inc. (ISO-NE) have created systems that provide their members' data files in an EQR compatible format. Identifying specific sales as exchanges in those files that match with simultaneous trades may be problematic and unnecessarily delay implementation of the data dictionary. Therefore, the definition of “Exchange” has been changed to exclude organized markets; EQR filers will continue to be allowed to report sales in organized markets as the product settled. Thus, the EQR Data Dictionary that we are adopting in this order (in Appendix A—“Product Names”) defines an “Exchange” as a “Transaction 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.”

55. The change in the definition should not be interpreted as excluding activities in Real-Time markets that offset sales in Day-Ahead markets. These trades will continue to be considered the organized markets' equivalent to bookouts and should be reported using the conventions adopted to ease the reporting process.[21]

L. Field No. 37—Rate Description

56. The EQR Notice proposed defining Rate Description as “Text description of rate. May reference FERC tariff, or, if a discounted or negotiated rate, include algorithm.”

57. EEI requests that filers be allowed to enter the tariff location into the rate description field in lieu of a detailed description of the rate itself. EEI cites the difficulty of putting complex rates into the 150-character field.

Commission Conclusion

58. The EQR fulfills the Commission's statutory obligation under the FPA to have companies' rates on file. The Commission relies on the EQR to satisfy the FPA requirement that rates provided in a contract be publicly disclosed and on file. Thus, it is imperative that the information reported in EQRs provide an adequate level of detail and transparency.

59. A tariff reference alone, instead of the actual rate description, does not meet that standard. Allowing filers to Start Printed Page 56740substitute a tariff reference in place of an actual rate description would force EQR users seeking this information to conduct further research to track down the contents of the tariff on file. This is clearly less transparent than a rate description that actually describes the rate.

60. If the tariff reference is coupled with a descriptive summary of the rate, where the rate is the function of a complex algorithm, the standard is met. Rate information will continue to be available to the public at a level sufficient to explain the bases and methods of calculation with additional detail available upon request to interested persons. Thus, the EQR Data Dictionary that we are adopting in this order defines “Rate Description” as “Text description of rate. Include 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.”

M. Field No. 39—Point of Receipt Balancing Authority (PORBA) and Field Nos. 41 and 56—Point of Delivery Balancing Authority (PODBA)

61. The EQR Notice proposed defining Point of Receipt Balancing Authority (PORBA) as “The registered NERC Balancing Authority (formerly called NERC Control Area) abbreviation used in OASIS applications or `Hub' if point of receipt is at a restricted trading hub.” The EQR Notice proposed defining Point of Delivery Balancing Authority (PODBA) as “The registered NERC Balancing Authority (formerly called NERC Control Area) abbreviation used in OASIS applications or 'Hub' if point of receipt is at a restricted trading hub.”

62. Powerex notes that when it sends power sourced in the United States to British Columbia for use by British Columbia Hydro and Power Authority (BC Hydro), the PODBA is British Columbia Transmission Corporation (BCTC). BCTC is not included as an option for the fields in the EQR. Powerex suggests that BCTC was inadvertently omitted as a Balancing Authority and asks the Commission to clarify the steps filers should take if the field cannot be completed because the correct value is not available.

Commission Conclusion

63. We agree with Powerex that the EQR does not currently include the BCTC balancing authority. While, as explained below, this balancing authority would only be used in a narrow set of instances, we will modify the dictionary to include BCTC as well as other balancing authorities located outside the United States.

64. For purposes of EQR reporting, we can categorize sales from the United States heading towards Canada into three categories: (1) Sales originating in the United States that are delivered in the United States; (2) sales originating in the United States where title changes on the United States' side of the United States-Canada border; and (3) sales originating in the United States where title changes in Canada. In the first instance, the sale is reported in the EQR with the PODBA being a balancing authority within the United States.[22] In the second instance, the sale is reported in the EQR with a PODBA on the United States' side of the United States-Canada border. In the third instance, the sale, which is not jurisdictional, would not be reported in the EQR.

65. In the case of sales from Canada, for purposes of EQR reporting we can likewise divide these sales into three categories: (1) Sales originating in Canada that are delivered within Canada; (2) sales originating in Canada where title changes on the Canadian side of the United States-Canada border; and (3) sales originating in Canada where title changes in the United States. In the first instance, the sale, which is not jurisdictional, would not be reported in the EQR. Likewise, sales in the second instance would not be jurisdictional and would not be reported in the EQR; however, if there is a subsequent resale that takes that power from the border into the United States, that resale would be reported with a PODBA within the United States. In the third instance, the sale would be reported using a United States' PODBA.

66. Powerex's comment also reveals a weakness in the proposed PODBA/PORBA definitions. As presented, the definitions focus on the list of acceptable entries without classifying what characterizes those entries. Field Nos. 39 and 41, for example, are defined identically in the EQR Notice, which provides:—“The registered NERC Balancing Authority (formerly called NERC Control Area) abbreviation used in OASIS applications or ‘Hub’ if point of receipt is at a restricted trading hub”—even though the former refers to a receipt point and the latter refers to a delivery point. We have changed the field definitions to address this issue. Thus, the EQR Data Dictionary that we are adopting in this order defines “PORBA” as “The 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.” In addition, the EQR Data Dictionary that we are adopting in this order defines “PODBA” as “The 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.”

67. Regarding Powerex's more general comment requesting clarification on the steps filers should take if data needed to make an entry is not available, the Commission stated in Order No. 2001-E that it would use the list “kept current as part of the Transmission Service Information Network (TSIN) by the North American Electric Reliability Council (NERC)” as the source for the abbreviations in this field.[23] Commission staff reviews this list each quarter to identify any changes, additions and deletions. Changes to the list are implemented and filers notified using procedures authorized after Order No. 2001-E.[24] When the final EQR Data Dictionary is issued, any changes in the list will be posted in a revised Appendix B. If, for some reason, a TSIN-identified Balancing Authority where jurisdictional sales may occur is not included in the EQR software, interested parties may send an e-mail to EQR@ferc.gov to alert staff to the omission.

68. Regarding the specific Balancing Authority identified as “MISO” in Appendix B, MISO seeks to clarify that MISO is not yet a certified NERC balancing authority. MISO asks the Commission to indicate in Appendix B that this is an “administrative classification.” Start Printed Page 56741

69. The Commission recognizes that at present there are multiple balancing authorities with responsibilities within the Midwest ISO footprint. The Midwest ISO provides settlement and EQR reporting detail at the balancing authority level. When a sale occurs in one of the balancing authorities, the particular PODBA should be identified in the EQR. Nevertheless, TSIN.com, the OASIS registration Web site chosen by the Commission in Order No. 2001-E to determine balancing authorities, identifies “MISO” as a balancing authority. Further, there are certain system-wide products offered in MISO such as “Uplift” that cannot be linked to a single PODBA. Therefore, “MISO” will be included in the list of available balancing authorities for system-wide products.

N. Field Nos. 40 and 42—Point of Receipt Specific Location (PORSL) and Point of Delivery Specific Location (PODSL)

70. The EQR Notice proposed defining Point of Receipt Specific Location (PORSL) as “The 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.” The EQR Notice proposed defining Point of Delivery Specific Location (PODSL) as “The 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.”

71. EEI recommends that the Commission allow contracts with numerous Points of Receipt to be reported as “Various” for the Point of Receipt Specific Location. In its comments, EEI identifies two hubs in Appendix C that no longer exist, “AEP (into)” and “ComEd (into).” In addition, EEI suggests that the definition of the Palo Verde Hub in Appendix C be changed to include the Hassayampa switchyard 2 miles south of Palo Verde.

Commission Conclusion

72. EEI's suggestion to report Points of Receipt as “Various” would undermine the usefulness of this field by allowing various points defined in the contract to be described using the same nomenclature as points defined as “Various” in the contract. However, EEI's concern about fitting several distinct points within the limited space provided is well founded. To balance the limitations of this EQR field with the requirement for contract information to be provided, the definition has been changed to allow for a descriptive summary of the points listed in the contract.

73. As to EEI's suggestion that the “AEP (into)” and “ComEd (into)” hubs be removed from Appendix C, we agree that this is appropriate since these two hubs are no longer in operation. In addition, we will adopt EEI's suggestion to revise the definition of the Palo Verde Hub in Appendix C to include the Hassayampa switchyard 2 miles south of Palo Verde. This change is intended to make the definition consistent with Commission policy since 2001 treating Palo Verde and the Hassayampa switchyard as a common bus.[25]

O. Field No. 46—Transaction Unique ID

74. The EQR Notice proposed defining Transaction Unique ID as “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.”

75. Transalta requests that the Commission clarify that, for index priced deals only, a new unique ID is not required each time the price changes so long as each new price is reported. Transalta also seeks confirmation that a single transaction using a single Transaction Unique ID may contain multiple records.

Commission Conclusion

76. Transalta is correct that filers must enter a new record each time the price changes in a sale. Transalta is also correct in that a single transaction using a single Transaction Unique ID may contain multiple records. This is not a departure from definitions or guidance that the Commission has given in the past.

P. Field Nos. 53, 54 and 64—Transaction Begin Date, Transaction End Date and Price

77. The EQR Notice proposed defining Transaction Begin Date as “First date and time the product is sold during the quarter at the specified price.” The EQR Notice proposed defining Transaction End Date as “Last date and time the product is sold during the quarter at the specified price.” The EQR Notice proposed defining Price as “Price charged for the product per unit.”

78. EEI recommends changing the definition for the beginning and ending dates. This change makes the date entered unique to the transaction reported while eliminating the uniqueness of price.

Commission Conclusion

79. The Commission will adopt EEI's suggested revisions. The removal of the phrase “at the specified price” from the date fields should not be interpreted to mean that the Commission intends to allow aggregation of prices. To fulfill the Commission's FPA obligations, the prices reported must reflect the actual prices charged. Each price change will continue to require a new record to be reported. To ensure that this requirement is clear, the definition of “Price” has been changed to specify that the price reported cannot be averaged or otherwise aggregated.

Q. Field No. 61—Increment Peaking Name

80. The EQR Notice proposed defining Increment Peaking Name as “FP-Full Period: The product described may be sold during all hours under the contract. OP-Off-Peak: The product described may be sold only during those hours designated as off-peak in the NERC region of the point of delivery. P-Peak: The product described may be sold only during those hours designated as on-peak in the NERC region of the point of delivery. N/A-Not Applicable: To be used only when the other available increment peaking names do not apply.”

81. EEI suggests that the words “Peak” and “Off-Peak” be used in the definition of “FP-Full Period” instead of “all” to clarify that full period sales need not last 24 hours. EEI also suggests that the phrase “under the contract” be deleted to clarify that this field refers to Transaction Data. EEI further recommends changing the verb tense in all the Increment Peaking Name definitions to clarify that the transactions being reported occurred in the past.

Commission Conclusion

82. The Commission finds that EEI's suggestions—to use the words “Peak” and “Off-Peak” instead of “all” in the definition of “FP-Full Period”—add clarity and we will revise this definition accordingly. In addition, we will also adopt EEI's suggestion to change the verb tense in all the Increment Peaking Name definitions to clarify that the transactions being reported occurred in the past. Start Printed Page 56742

III. Implementation Issues

83. EEI requests that changes requiring additional programming be kept to a minimum and adequate time be provided to implement any changes. The proposed changes to the EQR are minimal. Over the past five years, Commission staff has given filing guidance based on Order No. 2001 and related issuances. Little in this order goes beyond or changes that guidance, so this order should raise minimal implementation concerns.

84. Nonetheless, to minimize any impact on filers, the Commission is making the EQR Data Dictionary we are adopting in this order effective for the first quarter of 2008, rather than immediately. This effective date provides companies until the April 30, 2008 filing deadline to make their internal filing processes compliant with the EQR Data Dictionary. The new date has the additional benefit of creating a consistent data set across the calendar year.

85. CVPS requests that the Commission consider a size threshold for implementing new definitions or, if new definitions are to be adopted for all, that implementation be phased-in to allow smaller companies additional time to comply. In other words, CVPS is requesting that smaller companies would make their EQR filings based on one set of definitions, while everyone else would make their EQR filings based on a different set of definitions.[26]

86. In Order No. 2001, the Commission indicated that it would “consider granting waivers in appropriate circumstances.” While several waivers have been issued, the Commission has found, over time, that the amount of effort to complete the EQR tends to correspond with the size of the company. Thus, small companies with few sales tend to have smaller EQRs and a correspondingly smaller filing burden. However, because the EQR is one of the foundations of the market-based rate program, the Commission has granted waivers sparingly and always in regard to a company's entire filing and not to particular parts of the filing.

87. The proportion of company size to filing size may not apply if the small entity sells to an RTO/ISO. A company making a single baseload energy sale into an ISO will have over 2,000 lines of transaction data during any given quarter. Three of the organized markets, NYISO, ISO-NE, and MISO, however, provide their participants data files intended to simplify the filing process.

88. The Commission will not waive compliance with the EQR Data Dictionary definitions for particular companies. It would be confusing and hinder the transparency provided by the EQR if some filers made their filings based on one set of definitions, while others made their filings based on another understanding of those terms. Moreover, it would undermine the purpose of adopting a standard set of definitions. The Commission will, however, entertain requests for extension of time to file Q1 2008 EQR filings in cases where companies' implementation of the Data Dictionary definitions is incomplete.

89. EEI's requests that the Commission clarify that the changes in filing requirements associated with the EQR Data Dictionary are prospective only and will not be applied to past filings. Of course, this is true. Nonetheless, the Commission will continue to expect that those companies that have been filing EQRs since 2002 comply with the then-effective filing requirements.

90. Finally, EEI notes that some ISO/RTOs have documented how they map their settlement billing elements to EQR products to generate their EQR-ready data files. EEI asks that the Commission review and endorse or correct these mappings.

91. The Commission is on record as endorsing this effort and encouraging Commission staff to work with the ISOs and their members to develop these maps so that the ISOs can provide EQR-ready data files to their members.[27] Commission staff has worked closely with the three ISOs that are providing this service as well as with the California Independent System Operator Corporation and PJM Interconnection, LLC, which have not yet competed these tasks. Commission staff has reviewed these maps for the ISOs and participated in long, detailed discussions at ISO Committee meetings to ensure their consistency with Commission policy.

92. Nonetheless, the task of the instant proceeding is to create an EQR Data Dictionary. It is not the appropriate forum in which to address the specific issue of ISO data mappings for EQR-ready reports. Our finding here is without prejudice to this matter subsequently being raised in another proceeding.

IV. Implementation Dates

93. This order will become effective upon publication in the Federal Register. The definitions adopted in this order shall be used in filing the Q1 2008 EQR due on April 30, 2008 and in subsequent filings of the EQR.

V. Document Availability

94. 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.

95. 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 “RM01-8” in the docket number field. User assistance is available for eLibrary and the Commission's website during the Commission's normal business hours. For assistance contact the Commission's Online Support services at FERCOnlineSupport@ferc.gov or toll-free at (866) 208-3676, or for TTY, contact (202) 502-8659.

The Commission orders:

(A) The Commission hereby adopts the EQR Data Dictionary shown in the Attachment, as discussed in the body of this order.

(B) The definitions adopted in this order shall be applied to EQR filings beginning with the Q1 2008 EQR (due on April 30, 2008) and in subsequent EQR filings due thereafter.

Start Signature

By the Commission.

Kimberly D. Bose,

Secretary.

End Signature

Attachment—Electric Quarterly Report Data Dictionary Version 1.0 (Issued September 24, 2007) Start Printed Page 56743

EQR Data Dictionary

Field No.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.
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.
Start Printed Page 56744
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 or materially amended. If the parties signed on different dates use the most recent date signed.
22Contract Commencement DateYYYYMMDDThe date the contract was effective. If it is not specified in the contract, the first date of service under the contract.
23Contract Termination DateIf specified in the contractYYYYMMDDThe date that the contract expires.
24Actual Termination DateIf contract terminatedYYYYMMDDThe date the contract actually terminates.
25Extension Provision 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.
H-HourlyTerms of the contract (if specifically noted in the contract) set for up to 6 consecutive hours (≤ 6 consecutive hours).
Start Printed Page 56745
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 one month (>168 consecutive hours and ≤1 month).
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 Based Energy or capacity sold under a FERC-approved cost-based rate tariff.
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. Include 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.
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.
Start Printed Page 56746
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.
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.
Start Printed Page 56747
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.
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 one month (>168 consecutive hours and ≤ 1 month). 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.
Start Printed Page 56748
67Total Transaction ChargeNumber with up to 2 decimalsTransaction Quantity (Field 63) times Price (Field 64) plus Total Transmission Charge (Field 66).

EQR Data Dictionary—Appendix A. Product Names

Product nameContract productTransaction productDefinition
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).
Start Printed Page 56749
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.
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—Appendix B. Balancing Authority

Balancing authorityAbbreviationOutside U.S.*
AESC, LLC—Wheatland CINAEWC
Alabama Electric Cooperative, IncAEC
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, IncFE
Aquila Networks—KansasWPEK
Aquila Networks—Missouri Public ServiceMPS
Aquila Networks—West Plains DispatchWPEC
Arizona Public Service CompanyAZPS
Associated Electric Cooperative, IncAECI
Avista CorpAVA
Batesville Balancing AuthorityBBA
Big Rivers Electric CorpBREC
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 DeptINDN
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, ArkansasDENL
Constellation Energy Control and Dispatch—West Memphis, ArkansasWMUC
Dairyland Power CooperativeDPC
DECA, LLC—Arlington ValleyDEAA
Duke Energy CorporationDUK
East Kentucky Power Cooperative, IncEKPC
El Paso ElectricEPE
Electric Energy, IncEEI
Empire District Electric Co., TheEDE
Start Printed Page 56750
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
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 CoIP
Illinois Power CoIPRV
Imperial Irrigation DistrictIID
Indianapolis Power & Light CompanyIPL
ISO New England IncISNE
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, IncMP
Montana-Dakota Utilities CoMDU
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
Start Printed Page 56751
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, IncSOCO
Southern Illinois Power CooperativeSIPC
Southern Indiana Gas & Electric CoSIGE
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 CoUPPC
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, IncYAD
* 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 Dictonary.—Appendix C. Hub

HUBDefinition
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”) nodes 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”) nodes 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”) nodes 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”) nodes 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”) nodes 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.
Start Printed Page 56752
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.
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—Appendix D. Time Zone

Time zoneDefinition
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—Appendix E. Units

UnitsDefinition
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—Appendix F. Rate Units

Rate unitsDefinition
$/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 for Electric Quarterly Reports, 72 FR 26091 (May 8, 2007), FERC Stats. & Regs. ¶ 35,050 (2007) (EQR Notice).

Back to Citation

2.  Revised Public Utility Filing Requirements, Order No. 2001, 67 FR 31043, FERC Stats. & Regs. ¶ 31,127, 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).

Back to Citation

3.  Examples cited in EQR Notice at P 3.

Back to Citation

4.  Order No. 2001-E, 105 FERC ¶ 61,352 at P 2.

Back to Citation

5.  Id. at P 8.

Back to Citation

7.  Revised Public Utility Filing Requirements, 106 FERC ¶ 61,281 (2004).

Back to Citation

8.  Examples cited in EQR Notice at P 6.

Back to Citation

9.  Notice Seeking Comments on Proposed Electric Quarterly Report Data Dictionary, 72 FR 26091 (May 8, 2007).

Back to Citation

10.  Timely comments on the EQR notice were filed by: Edison Electric Institute (EEI); Transalta Energy Marketing (U.S.) Inc. (Transalta); The Midwest Independent Transmission System Operator, Inc. (MISO); Reliant Energy, Inc. (Reliant); Occidental Power Services, Inc. (Occidental); and Powerex Corp. (Powerex). In addition, Central Vermont Public Service (CVPS) submitted late-filed comments that included a request that the Commission accept them. The Commission will consider all the comments filed in response to the EQR Notice, including the late-filed comments of CVPS.

Back to Citation

11.  The one exception is CVPS, which filed comments arguing that the EQR Data Dictionary should either (1) Not apply to small entities or (2) not be adopted. We will separately discuss this comment below.

Back to Citation

12.  Order No. 2001, FERC Stats. & Regs. ¶ 31,127 at P 12.

Back to Citation

13.  EQR Notice, FERC Stats. & Regs. ¶ 35,050 at P 13.

Back to Citation

14.  Order No. 2001-E, 105 FERC ¶ 61,352 at P 9.

Back to Citation

15.  Order No. 2001, FERC Stats. & Regs. ¶ 31,127 at P 44-46

Back to Citation

16.  See Notice of Electric Quarterly Reports Users Group Meeting, November 8, 2006. The discussion version of the data dictionary was posted on the Commission calendar (http://www.ferc.gov/​EventCalendar/​Files/​20061117145410-Staff%20Draft%20of%20EQR%20Data%20Dictionary.xls), and a transcript of the meeting is posted online.

Back to Citation

17.  Preventing Undue Discrimination and Preference in Transmission Service, Order No. 890, 72 FR 12266, FERC Stats. & Regs. ¶ 31,241 at P 816-817 (2007).

Back to Citation

18.  Id. at n. 499.

Back to Citation

19.  Transalta Comments on EQR Notice at 3.

Back to Citation

20.  Order No. 2001, FERC Stats. & Regs. ¶ 31,127 at P 335.

Back to Citation

21.  A description of these conventions may be found in the EQR section of the Commission's Web site at Day Ahead/Real Time Reporting in the EQR (http://www.ferc.gov/​docs-filing/​eqr/​news-help/​real-time.pdf).

Back to Citation

22.  The PORBA, if specified, would be reported in the EQR's Contract Data section and not in Transaction Data. If a contract is jurisdictional and reported in the EQR, a Canadian PORBA or PODBA would be reported in instances where provided by the contract.

Back to Citation

23.  Order No. 2001-E, 105 FERC ¶ 61,352 at P 4.

Back to Citation

24.  See Revised Public Utility Filing Requirements, 106 FERC ¶ 61,281 (2004).

Back to Citation

25.  Arizona Public Service Co., 96 FERC ¶ 61,156 (2001).

Back to Citation

26.  CVPS is not arguing here that small entities be excused from making EQR filings; rather, it is arguing that small entities be permitted to continue to make those filings under the Commission's prior guidance, without regard to the clarifications provided in the EQR Data Dictionary we are adopting in this order.

Back to Citation

27.  Order No. 2001-E, 105 FERC ¶ 61,352 at P 11.

Back to Citation

[FR Doc. E7-19484 Filed 10-3-07; 8:45 am]

BILLING CODE 6717-01-P