Revised Public Utility Filing Requirements for Electric Quarterly Reports, 65526-65541 [E8-26209]
Download as PDF
<![CDATA[
65526
Federal Register / Vol. 73, No. 214 / Tuesday, November 4, 2008 / Rules and Regulations
specifically prescribed and every
amendment to such application, and
every statement of fact formally filed in
support of, or in opposition to, any
application or declaration shall be
verified by the person executing the
same. An instrument executed on behalf
of a corporation shall be verified in
substantially the following form, but
suitable changes may be made in such
form for other kinds of companies and
for individuals:
The undersigned states that he or she
has duly executed the attached ______
dated ______, 20 ___ for and on behalf
of (name of company); that he or she is
(title of officer) of such company; and
that all action by stockholders,
directors, and other bodies necessary to
authorize the undersigned to execute
and file such instrument has been taken.
The undersigned further states that he
or she is familiar with such instrument,
and the contents thereof, and that the
facts therein set forth are true to the best
of his or her knowledge, information
and belief.
llllllllllllllllll
l
(Signature)
*
*
*
*
*
Dated: October 29, 2008.
By the Commission.
Florence E. Harmon,
Acting Secretary.
[FR Doc. E8–26183 Filed 11–3–08; 8:45 am]
BILLING CODE 8011–01–P
DEPARTMENT OF ENERGY
information less burdensome and more
accessible.
DATES: Effective Date: This order will
become effective upon publication in
the Federal Register. The definitions
adopted in this order shall be used in
filing the Q1, 2009 EQR due on April
30, 2009 and in subsequent filings of the
EQR.
FOR FURTHER INFORMATION CONTACT:
Mark Blazejowski (Technical
Information), Office of Enforcement,
Federal Energy Regulatory
Commission, 888 First Street, NE.,
Washington, DC 20426, (202) 502–
6055.
Gary D. Cohen (Legal Information),
Office of the General Counsel, Federal
Energy Regulatory Commission, 888
First Street, NE., Washington, DC
20426, (202) 502–8321.
SUPPLEMENTARY INFORMATION:
Before Commissioners: Joseph T.
Kelliher, Chairman; Suedeen G. Kelly,
Marc Spitzer, Philip D. Moeller, and
Jon Wellinghoff.
1. In this order, after consideration of
the comments filed in response to our
notices seeking comment,1 we are
revising the Electric Quarterly Report
(EQR) Data Dictionary. Specifically, we
are revising the EQR Data Dictionary to
define and rename Field 22 of the EQR
to ‘‘Commencement Date of Contract
Terms,’’ as this field is intended to be
used to identify when the current terms
of the reported contract became
effective. This order also clarifies the
information to be reported in the EQR
concerning ancillary services.
Federal Energy Regulatory
Commission
I. Background
18 CFR Part 35
2. On April 25, 2002, the Commission
issued Order No. 2001, a final rule
establishing revised public utility filing
requirements. This rule requires public
utilities to file EQRs summarizing
specified pertinent data about their
currently effective contracts (contract
data) and data about wholesale power
sales they made during the reporting
period (transaction data).2 The
requirement to file EQRs replaced the
requirement to file quarterly transaction
reports summarizing a utility’s market-
A. EQRs and EQR Data Dictionary
[Docket Nos. RM01–8–009 and RM01–8–
010]
Revised Public Utility Filing
Requirements for Electric Quarterly
Reports
Issued October 28, 2008.
Federal Energy Regulatory
Commission, DOE.
ACTION: Order No. 2001–I; Order
Revising Electric Quarterly Report
(EQR) Data Dictionary.
AGENCY:
In this order, the Federal
Energy Regulatory Commission
(Commission) revises the EQR Data
Dictionary to define and rename Field
22 of the EQR to ‘‘Commencement Date
of Contract Terms’’ and to clarify the
information to be reported in the EQR
concerning ancillary services. These
revisions will make reporting this
dwashington3 on PRODPC61 with RULES
SUMMARY:
VerDate Aug<31>2005
15:01 Nov 03, 2008
Jkt 217001
1 Revised Public Utility Filing Requirements for
Electric Quarterly Reports, 73 FR 12983 (Mar. 11,
2008), FERC Stats. & Regs. ¶ 35,557 (2008) (EQR
Ancillary Services Notice); Revised Public Utility
Filing Requirements for Electric Quarterly Reports,
73 FR 30543 (May 28, 2008), FERC Stats. & Regs.
¶ 35,558 (2008) (Commencement Date Notice).
2 Revised Public Utility Filing Requirements,
Order No. 2001, 67 FR 31043, FERC Stats. & Regs.
¶ 31,127 (2002), reh’g denied, Order No. 2001–A,
100 FERC ¶ 61,074 (2002), reh’g denied, Order No.
2001–B, 100 FERC ¶ 61,342 (2002).
PO 00000
Frm 00032
Fmt 4700
Sfmt 4700
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’s Web site. This provision
obviates the need to revise the
Commission’s regulations to implement
revisions to the EQR 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 on how to report certain
transactions.3
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 and providing
formal definitions for fields that were
previously undefined.
B. Commencement Date
5. On December 20, 2007, the
Commission issued Order No. 2001–H,
which addressed a pending request for
rehearing and clarified the information
to be reported in several EQR data
fields. In Order No. 2001–H, the
Commission defined Field 22 in the
Contract Data section of the EQR, named
‘‘Contract Commencement Date,’’ 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.4
6. On February 26, 2008, the
Commission held a technical conference
to ‘‘review the EQR Data Dictionary and
address questions from EQR users.’’ 5
3 See, e.g., Notice Providing Guidance on the
Filing of Information on Transmission Capacity
Reassignments in Electric Quarterly Reports, 124
FERC ¶ 61,244 (2008), which provided guidance on
complying with the Commission’s Order No. 890–
B reporting requirements; Revised Public Utility
Filing Requirements, Order No. 2001–E, 105 FERC
¶ 61,352 (2003), where the Commission
standardized the terminology for control areas; and
Revised Public Utility Filing Requirements, 67 FR
65973 (Oct. 29, 2002), FERC Stats. & Regs. ¶ 35,045
(Oct. 21, 2002), which provided general guidance
for using the EQR software.
4 Revised Public Utility Filing Requirements for
Electric Quarterly Reports, Order No. 2001–H, 121
FERC ¶ 61,289 (2007), Data Dictionary at Field 22.
5 See Notice of Electric Quarterly Reports
Technical Conference, 73 FR 2477 (Jan. 15, 2008).
E:\FR\FM\04NOR1.SGM
04NOR1
Federal Register / Vol. 73, No. 214 / Tuesday, November 4, 2008 / Rules and Regulations
During this technical conference, the
participants discussed, among other
matters, whether the Commission
intended in Order No. 2001–H for the
commencement date field to be used to
report the date the contract terms
reported in the EQR (original or
amended) became effective. On April
17, 2008, in response to participants’
requests, the Commission’s Director,
Office of Enforcement, issued a waiver,
for the first quarter of 2008, of the
requirement to file EQRs using the
commencement date definition as
clarified in Order No. 2001–H.6 On July
9, 2008, the waiver was extended until
final action is taken in this docket.7
7. On May 28, 2008, the Commission
issued the Commencement Date Notice
to invite comment on the issues raised
in the technical conference. In addition,
the Commencement Date Notice
proposed defining commencement date
as:
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
have not been amended since January 1,
2008, the initial date the contract became
effective may be used.
8. The Commission also proposed
renaming the field to ‘‘Commencement
Date of Contract Terms.’’ 8 On April 10,
2008, three entities filed timely
comments on the Commencement Date
Notice.9
dwashington3 on PRODPC61 with RULES
C. Ancillary Service Reporting
9. Order No. 888 adopted six ancillary
services to be included in the open
access transmission tariff (OATT):
Scheduling, System Control and
Dispatch (Schedule 1); Reactive Supply
and Voltage Control (Schedule 2);
Regulation and Frequency Response
(Schedule 3); Energy Imbalance
(Schedule 4); Operating Reserve—
6 See Edison Electric Institute, Docket Nos.
RM01–8–000, RM01–8–007 and ER02–2001–000
(Apr. 17, 2008) (unpublished letter order).
7 See Edison Electric Institute, Docket Nos.
RM01–8–000, RM01–8–007 and ER02–2001–000
(July 9, 2008) (unpublished letter order).
8 As noted above, Field 22 has been previously
titled ‘‘Contract Commencement Date.’’
9 Timely comments on the Commencement Date
Notice were filed by: Edison Electric Institute (EEI);
Sempra Energy, Inc. (Sempra); and Occidental
Power Services, Inc. (Occidental).
VerDate Aug<31>2005
15:01 Nov 03, 2008
Jkt 217001
Spinning-or Spinning Reserve—
(Schedule 5); and Operating Reserve—
Supplemental—or Supplemental
Reserve—(Schedule 6).10
10. The six ancillary services
established in Order No. 888 are now
offered under the Order No. 890 pro
forma OATT. In Order No. 890, the
Commission also adopted ‘‘generator
imbalance’’ as a new ancillary service.11
11. On June 21, 2007, the Commission
issued Order No. 697, a Final Rule that
codified and, in certain respects, revised
the Commission’s standards for marketbased rate authority for sales of electric
energy, capacity, and ancillary
services.12 Among other matters, Order
No. 697 addressed the posting and
reporting requirements for third-party
sellers of ancillary services at marketbased rates.
12. The matter of third-party sellers of
ancillary services at market-based rates
had previously been addressed in Avista
Corporation, 87 FERC ¶ 61,223, order on
reh’g, 89 FERC ¶ 61,136 (1999) (Avista),
among other cases. Avista provided a
policy that third-party ancillary service
providers that could not perform a
market power study would be allowed
to sell ancillary services at market-based
rates, under certain conditions. The
authorization in Avista extended only to
the following four ancillary services:
Regulation Service; Energy Imbalance
Service; Spinning Reserves; and
Supplemental Reserves.
13. On March 3, 2008, the
Commission issued the EQR Ancillary
Services Notice to clarify the
requirement to report third-party
ancillary service transactions. The
notice proposed adding the phrase
‘‘Reported for power sales and
transmission-related transactions’’ to
10 Promoting Wholesale Competition Through
Open Access Non-discriminatory Transmission
Services by Public Utilities; Recovery of Stranded
Costs by Public Utilities and Transmitting Utilities,
Order No. 888, 61 FR 21540 (May 10, 1996), FERC
Stats. & Regs. ¶ 31,036 (1996), order on reh’g, Order
No. 888–A, 62 FR 12274 (Mar. 14, 1997), FERC
Stats. & Regs. ¶ 31,048 (1997), order on reh’g, Order
No. 888–B, 81 FERC ¶ 61,248 (1997), order on reh’g,
Order No. 888–C, 82 FERC ¶ 61,046 (1998), aff’d in
relevant part sub nom. Transmission Access Policy
Study Group v. FERC, 225 F.3d 667 (D.C. Cir. 2000)
(TAPS v. FERC), aff’d sub nom. New York v. FERC,
535 U.S. 1 (2002).
11 Preventing Undue Discrimination and
Preference in Transmission Service, Order No. 890,
72 FR 12266 (Mar. 15, 2007), FERC Stats. & Regs.
¶ 31,241, at P 668 (2007), order on reh’g, Order No.
890–A, 73 FR 2984 (Jan. 16, 2008), FERC Stats. and
Regs. ¶ 31,261 (2007), order on reh’g, Order No.
890–B, 123 FERC ¶ 61,299 (2008).
12 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 (2007),
clarifying order, 121 FERC ¶ 61,260 (2007), order on
reh’g, Order No. 697–A, 73 FR 25,832 (May 7,
2008), FERC Stats. & Regs. ¶ 31,268 (2008).
PO 00000
Frm 00033
Fmt 4700
Sfmt 4700
65527
clarify the EQR reporting requirements
with regard to Energy Imbalance,
Regulation & Frequency Response,
Spinning Reserve, and Supplemental
Reserve—the four products identified in
Avista—‘‘to clarify that sales of these
services must be reported both in the
Contract and Transaction sections of the
EQR.’’ The notice also proposed to add
Generator Imbalance as a Product Name
in the EQR.13 On June 27, 2008, three
entities filed comments in response to
the EQR Ancillary Services Notice.14
II. Discussion
A. Commencement Date
1. Comments
14. CAISO states that it supports the
intent of the proposed clarification of
the definition of the ‘‘Contract
Commencement Date’’ in the EQR Data
Dictionary and the proposal to rename
that EQR field as ‘‘Commencement Date
of Contract Terms.’’ However, CAISO is
concerned that the proposed
commencement date definition (Field
22) is confusing because it refers to ‘‘the
Contract Data section of the EQR’’ in the
second sentence and ‘‘the Contract
Products section’’ elsewhere.15 CAISO
recommends that the Commission only
require that entries to Field 22 be
changed as a result of matters affecting
the Contract Products section of the
contract data and not based on any other
revisions to a contract. CAISO argues
that other information included in the
EQR has no substantive effect on Field
22. CAISO also suggests that, rather than
referring to the ‘‘Commencement Date,’’
the definition should refer specifically
to ‘‘Commencement Date of Contract
Terms.’’
15. EEI’s comments generally support
the proposed modification. EEI,
however, requests that the Commission
modify the definition to make clear that
if the terms of the contract reported in
the Contract Products section have not
been amended since January 1, 2008,
the filer may, at its election, use the
initial date the contract became effective
(or absent an effective date the initial
13 EQR Ancillary Services Notice, FERC Stats. &
Regs. ¶ 35,557 at P 12.
14 Timely comments on the EQR Ancillary
Services Notice were filed by: EEI; California
Independent System Operator Corporation (CAISO);
and PJM Interconnection, L.L.C. (PJM).
15 EQR filers summarize their contracts in the
Contract Data section of the EQR: Fields 14 through
45. Fields 14 through 20 of the Contract Data
section capture the seller/customer identification
information and fields 21 through 25 capture
relevant contract dates such as commencement and
termination dates. The Contract Products section
(Fields 26 through 45) is a subset of the Contract
Data section describing the various offerings under
the contract such as firm and non-firm, long-term,
short-term.
E:\FR\FM\04NOR1.SGM
04NOR1
65528
Federal Register / Vol. 73, No. 214 / Tuesday, November 4, 2008 / Rules and Regulations
date when service began) as the contract
commencement date, even if the terms
of the contract reported in the Contract
Products section were amended prior to
January 1, 2008.
16. PJM states that the proposed
commencement date definition seems to
raise the possibility that an EQR filer
may begin reporting a contract upon its
effective date. PJM raises the concern
that this conflicts with the statement in
Order No. 2001 that ‘‘the requirement to
file contract data and transaction data
begins with the first Electric Quarterly
Report filed after service commences
under an agreement.’’ 16 PJM asks that
the Commission ‘‘permit public utilities
to report agreements in their EQRs upon
their effective dates * * * rather than
when service is taken under the
agreements.’’
2. Commission Determination
17. With regard to CAISO’s comments
regarding which revisions to contract
terms necessitate changes to the date
reported in the commencement date
field, we note that, in Order No. 2001–
H, the Commission stated:
dwashington3 on PRODPC61 with RULES
There is a very real public interest in
identifying when key terms of the contract
were determined. As market conditions
change over time, it is imperative to be able
to sort the deals that occurred years ago from
those that were confirmed more recently. To
better understand the market conditions at
the time a contract was put in place, it is
necessary to document the date that key
terms were established.17
18. As discussed below, based on our
consideration of the comments, the
Commission concludes that additional
specificity is needed to provide clarity.
As an initial matter, we adopt the
NOPR’s proposal to change the name of
Field 22 to ‘‘Commencement Date of
Contract Terms.’’ We note that several
commenters filed comments supporting
such a change, and no comment was
filed that raised objections to this
proposal.
19. In addition, as discussed below,
we are also revising the definition of
Field 22 to clearly delineate the
contractual changes that would require
a change in the date reported.
20. With regard to EEI’s comments,
we agree with the suggestion regarding
pre-2008 amendments. In particular, EEI
suggests we add the phrase ‘‘or absent
an effective date the initial date when
service began.’’ We find this additional
phrase further clarifies that the
Commission does not intend to require
filers to research contract histories to
comply with its requirements for this
16 Order
No. 2001, FERC Stats. & Regs. ¶ 31,127
at P 216.
17 Order No. 2001–H, 121 FERC ¶ 61,289 at P 12.
VerDate Aug<31>2005
15:01 Nov 03, 2008
Jkt 217001
field and, accordingly, we will adopt
this proposal.
21. Second, we reject EEI’s suggestion
that we add the phrase ‘‘the Filer at its
election may use’’ because we find that
such a phrase would result in greater
ambiguity, rather than clarity, by
offering a range of options on what may
be reported rather than requiring a
standard by which all filers must
comply. Further, the notion of
inconsistent filings is contrary to the
intention of the EQR Data Dictionary,
which was created to reduce the range
of possible interpretations for
appropriate entries in the EQR. Such
allowable disparities make the data less
uniform and less useful.
22. Finally, we reject the EEI
suggestion to add the phrase, ‘‘even if
the terms of the contract reported in the
Contract Products section were
amended prior to January 1, 2008’’
because we find it redundant and
subject to conflicting interpretations.
23. Accordingly, we rename Field 22
in the EQR as ‘‘Commencement Date of
Contract Terms.’’ The field is defined as:
The date the terms of the contract reported
in fields 18, 23 and 25 through 45 (as defined
in the data dictionary) became effective. If
those terms became effective on multiple
dates (i.e., due to one or more amendments),
the date to be reported in this field 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 reported in fields
18, 23 and 25 through 45 have not been
amended since January 1, 2009, the initial
date the contract became effective (or absent
an effective date the initial date when service
began) may be used.
24. This definition will become
effective on January 1, 2009 and will be
applicable for EQRs filed beginning in
the first quarter of 2009. The start date
for the reporting of contract
amendments has been changed in the
definition to January 1, 2009, to account
for the effective date of the revised EQR
Data Dictionary that we are adopting in
this order. The limited waiver for
compliance that the Commission
granted on April 17, 2008 and extended
on July 9, 2008 will apply to all 2008
EQRs.18
25. PJM is incorrect in its
interpretation that the proposed
commencement date definition raises
the possibility that an EQR filer may
begin reporting a contract upon its
effective date. The commencement date
18 The expiration date of the limited waiver also
applies to the Increment Name fields (Fields 28 and
60), for which additional time was provided to
comply with Order No. 2001–G.
PO 00000
Frm 00034
Fmt 4700
Sfmt 4700
definition specifies which date should
be used to populate the field and does
not otherwise address when a contract
must first be reported in the EQR. The
Commission recognizes that,
logistically, it may be more convenient
to begin reporting a contract upon
execution. Although the requirement to
file a contract in the EQR once service
under that contract commences will
remain in effect, the Commission
neither prohibits nor discourages the
earlier reporting of contracts.
B. Ancillary Service Reporting
1. Comments
26. With regard to third-party
ancillary service transactions, the EQR
Ancillary Services Notice proposed to
add to the phrase ‘‘Reported for power
sales and transmission-related
transactions’’ to clarify the EQR
reporting requirements with regard to
Energy Imbalance, Regulation &
Frequency Response, Spinning Reserve,
and Supplemental Reserve in Appendix
A (Product Names) to the EQR Data
Dictionary. The notice also proposed to
add the product ‘‘Generator Imbalance’’
in the Appendix.
27. In response to this notice, EEI
filed comments arguing that ancillary
services associated with transmission
contracts should not be reported in the
EQR. Thus, EEI suggests that the
reporting requirements regarding Energy
Imbalance, Regulation & Frequency
Response, Spinning Reserve, and
Supplemental Reserve be changed to
read as follows: ‘‘For Contracts, reported
if the contract provides for sale of the
product. For Transactions, sales by
third-party providers (i.e., nontransmission function) are reported.’’
EEI argues that its proposed language is
superior to that proposed by the
Commission, because the language
proposed in the EQR Ancillary Services
Notice may cause confusion over
whether transmission-related
agreements are to be reported in the
EQR. EEI states that ‘‘the Commission
has never required transmission
functions to report ancillary service
sales in the Transactions portion of the
EQR, which was established in Order
No. 2001,’’ and ‘‘the suggested changes
to the Appendix A definitions may not
clearly enough reflect this existing
policy.’’
28. EEI also states that ‘‘the definition
for Energy Imbalance and the proposed
definition for Generator Imbalance do
not indicate that they may be Ancillary
Services’’ and asks ‘‘the Commission to
clarify that Energy Imbalance and
Generator Imbalance can be an [sic]
Ancillary Services, and that * * *
E:\FR\FM\04NOR1.SGM
04NOR1
Federal Register / Vol. 73, No. 214 / Tuesday, November 4, 2008 / Rules and Regulations
[o]nly ancillary services provided by a
marketer are reportable transactions,
though both marketers and transmission
functions must list them in the
Contracts section of the EQR.’’
2. Commission Determination
29. Order No. 2001 stated:
dwashington3 on PRODPC61 with RULES
We clarify that ancillary service transaction
data associated with transmission need not
be reported when the transmission services
are provided on an unbundled basis * * *
On the other hand, ancillary service
transaction data associated with power sales
are currently required to be filed in Quarterly
Transaction Reports and the requirement to
file these data is retained in this rule.19
30. Our proposal in the EQR Ancillary
Services Notice was intended to provide
clarification regarding the EQR
reporting requirements for ancillary
services provided in association with
unbundled sales of transmission
services rather than to change the policy
(quoted immediately above) that we
established in Order No. 2001.20
31. Accordingly, with regard to EEI’s
suggested changes to the reporting
requirements for Energy Imbalance,
Regulation & Frequency Response,
Spinning Reserve, and Supplemental
Reserve, the Commission finds that
EEI’s proposal provides additional
clarity and we therefore adopt EEI’s
proposal.
32. Specifically, we revise the
ancillary service Product Names as
follows:
Energy Imbalance: Service provided
when a difference occurs between the
scheduled and the actual delivery of
energy to a load obligation (Ancillary
Service). For Contracts, reported if the
contract provides for sale of the product.
For Transactions, sales by third-party
providers (i.e., non-transmission
function) are reported.
Generator Imbalance: Service
provided when a difference occurs
between the output of a generator
located in the Transmission Provider’s
Control Area and a delivery schedule
from that generator to (1) another
Control Area or (2) a load within the
Transmission Provider’s Control Area
over a single hour (Ancillary Service).
For Contracts, reported if the contract
provides for sale of the product. For
Transactions, sales by third-party
providers (i.e., non-transmission
function) are reported.
Regulation & Frequency Response:
Service providing for continuous
balancing of resources (generation and
interchange) with load, and for
19 Order
20 Order
No. 2001 at P 271.
No. 697, FERC Stats. & Regs. ¶ 31,252 at
P 1058.
VerDate Aug<31>2005
15:01 Nov 03, 2008
Jkt 217001
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). For Contracts,
reported if the contract provides for sale
of the product. For Transactions, sales
by third-party providers (i.e., nontransmission function) are reported.
Spinning Reserve: Unloaded
synchronized generating capacity that is
immediately responsive to system
frequency and that is capable of being
loaded in a short time period or nongeneration resources capable of
providing this service (Ancillary
Service). For Contracts, reported if the
contract provides for sale of the product.
For Transactions, sales by third-party
providers (i.e., non-transmission
function) are reported.
Supplemental Reserve: Service
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 nongeneration resources capable of
providing this service (Ancillary
Service). For Contracts, reported if the
contract provides for sale of the product.
For Transactions, sales by third-party
providers (i.e., non-transmission
function) are reported.
C. Reporting of Ancillary Service
Product Type Names
1. Comments
33. EEI asks the Commission to
‘‘clarify the appropriate manner to
report the Product Type Name [Field
No. 30] for ancillary service sales in the
Contracts portion of the EQR,’’ namely,
that an ancillary service ‘‘reported by a
transmission function’’ should be
identified with a Product Type Name of
‘‘T,’’ indicating the product was sold
under a FERC-approved transmission
tariff. Alternatively, a merchant sale
would be reported as sold under a
FERC-approved cost-based tariff by
entering ‘‘CB’’ or market-based tariff by
entering ‘‘MB’’ as ‘‘factual
circumstances dictate.’’
34. Occidental seeks clarification
‘‘that imbalances that are settled in the
real-time markets operated by the ISOs
and RTOs are not intended to be
reported as ‘Generator Imbalances’
under the proposed revisions to the EQR
Data Dictionary.’’ Occidental states that
‘‘imbalances that are settled within the
organized markets [are] handled through
PO 00000
Frm 00035
Fmt 4700
Sfmt 4700
65529
the settlement process, in which the
generator pays the real-time price for
any under production and is paid the
real-time price for any over production
[and] should not be reported in the
EQRs as ‘Generator Imbalances’ under
this [FERC-proposed] definition.’’
2. Commission Determination
35. Regarding EEI’s request for
clarification, if the transmission
provider (i.e., non-merchant function)
makes an ancillary service sale, the
product type is ‘‘T.’’ With respect to
third-party sales, the product type is
listed as ‘‘CB,’’ if the third-party sale is
made under a cost-based rate tariff or
‘‘MB,’’ if the third-party sale is made
under a market-based rate tariff. We
believe that Product Type Name [Field
No. 30] adequately addresses this
distinction and, thus, do not find any
reason to revise the ancillary service
reporting requirements that we
proposed in the EQR Ancillary Services
Notice to add clarity on this issue.
36. In addition, we find that
Occidental is correct in its
interpretation of the difference between
energy imbalance service offered as an
ancillary service in general and the
method by which organized markets
address imbalances through settlement
in the Real-Time market. The
Commission has adopted conventions
for reporting trading within Real-Time
markets.21 This order does not change
those conventions.
D. Whether Ancillary Services Not
Included in the OATT Should Be
Reported in EQRs
1. Comments
37. The EQR Ancillary Services
Notice invited comment on the need to
include additional non-OATT ancillary
services in the list of Product Names in
the EQR Data Dictionary. Two
commenters filed comments addressing
this issue. EEI states that it
‘‘recommends against including any
other ancillary services in the EQR at
this time.’’
38. Sempra comments that ‘‘the
industry may benefit from additional
clarification with respect to the
reporting of ISO/RTO-specific ancillary
services that may not be currently
reflected’’ in the OATT. Sempra also
suggests that there are benefits to
clarifying ‘‘the reporting of other ISO/
RTO-specific products.’’ To this end,
Sempra asks that the Commission
clarify ‘‘the appropriate reporting
‘bucket’ for other CAISO products, such
21 Revised Public Utility Filing Requirements for
Electric Quarterly Reports, Order No. 2001–G, 120
FERC ¶ 61,270, at P 55 (2007).
E:\FR\FM\04NOR1.SGM
04NOR1
65530
Federal Register / Vol. 73, No. 214 / Tuesday, November 4, 2008 / Rules and Regulations
as Instructed Imbalance Energy and
Uninstructed Imbalance Energy.’’ As to
whether the Commission should add
specific new ancillary services to the
EQR Data Dictionary, Sempra asks that
the Commission ‘‘consider whether any
additional CAISO products or ancillary
services should be included in the EQR
Data Dictionary once the CAISO MRTU
[Market Redesign and Technology
Upgrade] program is put into effect.’’ 22
2. Commission Determination
39. The Commission will continue its
policy of identifying only the standard
OATT ancillary services as ancillary
services in the Product Name field of
the EQR. This policy is consistent with
the Commission’s intention, in
establishing the EQR filing
requirements, that the same kinds of
information be reported by all EQR
filers, in the same format and using the
same definitions. This approach is
intended to allow EQR users and
Commission staff to readily compare
and contrast the transactions and
contracts reported by one utility to those
of other utilities. We will continue to
add products that reflect common and
new offerings by the industry where it
appears that these products are widely
offered, but, in this case, we agree with
EEI that the current list of ancillary
service product names to be reported in
the EQR is sufficient.
40. As to Sempra’s comments about
providing clarification regarding the
appropriate reporting of the specific
products offered by CAISO, in Order
No. 2001–E, the Commission
encouraged RTOs and ISOs to work
with Commission staff to develop EQRready reports to ease the filing process
for respondents and to improve
consistency in reporting within and
among the organized markets.23 Three
ISOs—New York ISO, Midwest ISO and
ISO New England—currently provide
reports to their members that format
settlement data for the EQR. PJM
expects to begin doing so by the end of
2008.
41. In addition, we note that CAISO’s
staff met with Commission staff and
market participants on May 18, 2004 to
map the CAISO’s products to the EQR
product list.24 Likewise, we encourage
CAISO to meet with Commission staff
on MRTU product mapping and provide
EQR-ready reports to ease the filing
process for respondents.
III. Document Availability
42. 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 (https://
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.
43. 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 Web site during the
Commission’s normal business hours.
For assistance contact the Commission’s
Online Support services at
FERCOnlineSupport@ferc.gov or tollfree at (866) 208–3676, or for TTY,
contact (202) 502–8659.
The Commission orders:
(A) The Commission hereby adopts
the changes in the EQR Data Dictionary
shown in the Attachment, as discussed
in the body of this order.
(B) This order will become effective
upon publication in the Federal
Register. The definitions adopted in this
order shall be used in filing the Q1,
2009 EQR due on April 30, 2009 and in
subsequent filings of the EQR.
(C) The limited waiver for compliance
granted on April 17, 2008 and extended
on July 9, 2008 will apply to all 2008
EQRs and only to 2008 EQRs, regardless
of when they are filed.
By the Commission.
Kimberly D. Bose,
Secretary.
Attachment
Electric Quarterly Report Data
Dictionary Version 1.1 (Issued October
28, 2008)
EQR DATA DICTIONARY
Field No.
Field
Required
Value
Definition
ID Data
Filer Unique Identifier ........
X ..................
FR1 ....................................
1 ...............
Filer Unique Identifier ........
X ..................
FS# (where ‘‘#’’ is an integer).
1 ...............
Filer Unique Identifier ........
X ..................
FA1 ....................................
2 ...............
dwashington3 on PRODPC61 with RULES
1 ...............
Company Name .................
X ..................
Unrestricted text (100 characters).
22 We note that, while Sempra asks the
Commission to consider these matters, it does not
explicitly advocate that the Commission add any
additional products to the EQR Data Dictionary.
VerDate Aug<31>2005
15:01 Nov 03, 2008
Jkt 217001
23 Order
(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.
(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.
(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.
(Respondent)—The name of the company taking responsibility for complying with the Commission’s regulations related to the EQR.
No. 2001–E, 105 FERC ¶ 61,352 at P 11.
of Electric Quarterly Reports Western
Outreach Session, 69 FR 25897 (May 10, 2004). The
24 Notice
PO 00000
Frm 00036
Fmt 4700
Sfmt 4700
mapping developed in this meeting is available on
the Commission’s Web site (https://www.ferc.gov/
EventCalendar/EventDetails.aspx?ID=1096&Cal
Type=%20&Date=5/18/2004&CalendarID=116).
E:\FR\FM\04NOR1.SGM
04NOR1
Federal Register / Vol. 73, No. 214 / Tuesday, November 4, 2008 / Rules and Regulations
65531
EQR DATA DICTIONARY—Continued
Field No.
Field
Required
Value
Definition
2 ...............
Company Name .................
X ..................
Unrestricted text (100 characters).
2 ...............
Company Name .................
X ..................
Unrestricted text (100 characters).
3 ...............
Company DUNS Number ..
Nine digit number ..............
4 ...............
Contact Name ....................
for Respondent and
Seller.
X ..................
4 ...............
Contact Name ....................
X ..................
Unrestricted text (50 characters).
4 ...............
Contact Name ....................
X ..................
5 ...............
Contact Title .......................
X ..................
6 ...............
7 ...............
Contact Address ................
Contact City .......................
X ..................
X ..................
8 ...............
Contact State .....................
X ..................
9 ...............
Contact Zip ........................
X ..................
10 .............
Contact Country Name ......
X ..................
11 .............
Contact Phone ...................
X ..................
12 .............
13 .............
Contact E-Mail ...................
Filing Quarter .....................
X ..................
X ..................
Unrestricted text (50 characters).
Unrestricted text (50 characters).
Unrestricted text .................
Unrestricted text (30 characters).
Unrestricted text (2 characters).
Unrestricted text (10 characters) CA—Canada,
MX—Mexico.
US—United States, UK—
United Kingdom.
Unrestricted text (20 characters).
Unrestricted text .................
YYYYMM ...........................
(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.
(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.
The unique nine digit number assigned by Dun and
Bradstreet to the company identified in Field Number
2.
(Respondent)—Name of the person at the Respondent’s company taking responsibility for compliance
with the Commission’s EQR regulations.
(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.
(Agent)—Name of the contact for the Agent, usually
the person who prepares the filing.
Title of contact identified in Field Number 4.
Unrestricted text (50 characters).
Street address for contact identified in Field Number 4.
City for the contact identified in Field Number 4.
Two character state or province abbreviations for the
contact identified in Field Number 4.
Zip code for the contact identified in Field Number 4.
Country (USA, Canada, Mexico, or United Kingdom)
for contact address identified in Field Number 4.
Phone number of contact identified in Field Number 4.
E-mail address of contact identified in Field Number 4.
A 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
Contract Unique ID ............
X ..................
An integer preceded by the
letter ‘‘C’’ (only used
when importing contract
data).
15 .............
Seller Company Name ......
X ..................
Unrestricted text (100 characters).
16 .............
Customer Company Name
X ..................
17 .............
Customer DUNS Number ..
X ..................
Unrestricted text (70 characters).
Nine digit number ..............
18 .............
dwashington3 on PRODPC61 with RULES
14 .............
Contract Affiliate ................
X ..................
Y (Yes), N (No) ..................
VerDate Aug<31>2005
15:01 Nov 03, 2008
Jkt 217001
PO 00000
Frm 00037
Fmt 4700
Sfmt 4700
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 commadelimited (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.
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).
The name of the counterparty.
The unique nine digit number assigned by Dun and
Bradstreet to the company identified in Field Number
16.
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.
E:\FR\FM\04NOR1.SGM
04NOR1
65532
Federal Register / Vol. 73, No. 214 / Tuesday, November 4, 2008 / Rules and Regulations
EQR DATA DICTIONARY—Continued
Field
Required
Value
Definition
19 .............
FERC Tariff Reference ......
X ..................
Unrestricted text (60 characters).
20 .............
Contract Service Agreement ID.
X ..................
Unrestricted text (30 characters).
21 .............
Contract Execution Date ....
X ..................
YYYYMMDD ......................
22 .............
Commencement Date of
Contract Terms.
X ..................
YYYYMMDD ......................
23 .............
Contract Termination Date
YYYYMMDD ......................
Actual Termination Date ....
YYYYMMDD ......................
The date the contract actually terminates.
25 .............
Unrestricted text .................
26 .............
26 .............
Extension Provision Description.
Class Name .......................
Class Name .......................
If specified in
the contract.
If contract
terminated.
X ..................
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.
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.
The date the contract was signed. If the parties signed
on different dates, use the most recent date signed.
The date the terms of the contract reported in fields
18, 23 and 25 through 45 (as defined in the data
dictionary) became effective. If those terms became
effective on multiple dates (i.e.: due to one or more
amendments), the date to be reported in this field 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 reported in fields 18, 23 and 25 through
45 have not been amended since January 1, 2009,
the initial date the contract became effective (or absent an effective date the initial date when service
began) may be used.
The date that the contract expires.
24 .............
X ..................
X ..................
............................................
F—Firm ..............................
26 .............
Class Name .......................
X ..................
NF—Non-firm .....................
26 .............
Class Name .......................
X ..................
UP—Unit Power Sale ........
26 .............
Class Name .......................
X ..................
N/A—Not Applicable ..........
27 .............
Term Name ........................
X ..................
28 .............
28 .............
dwashington3 on PRODPC61 with RULES
Field No.
Increment Name ................
Increment Name ................
X ..................
X ..................
LT—Long Term, ST—Short
Term, N/A—Not Applicable.
............................................
H—Hourly ..........................
28 .............
Increment Name ................
X ..................
D—Daily .............................
28 .............
Increment Name ................
X ..................
W—Weekly ........................
Description of terms that provide for the continuation of
the contract.
See definitions of each class name below.
For 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.
For 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.
Designates a dedicated sale of energy and capacity
from one or more than one specified generation
unit(s).
To be used only when the other available Class
Names do not apply.
Contracts with durations of one year or greater are
long-term. Contracts with shorter durations are shortterm.
See definitions for each increment below.
Terms of the contract (if specifically noted in the contract) set for up to 6 consecutive hours (≤ 6 consecutive hours).
Terms 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).
Terms 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).
VerDate Aug<31>2005
15:01 Nov 03, 2008
Jkt 217001
PO 00000
Frm 00038
Fmt 4700
Sfmt 4700
E:\FR\FM\04NOR1.SGM
04NOR1
Federal Register / Vol. 73, No. 214 / Tuesday, November 4, 2008 / Rules and Regulations
65533
EQR DATA DICTIONARY—Continued
Field
Required
Value
Definition
28 .............
Increment Name ................
X ..................
M—Monthly ........................
28 .............
Increment Name ................
X ..................
Y—Yearly ...........................
28 .............
29 .............
Increment Name ................
Increment Peaking Name ..
X ..................
X ..................
N/A—Not Applicable ..........
............................................
29 .............
Increment Peaking Name ..
X ..................
FP—Full Period .................
29 .............
Increment Peaking Name ..
X ..................
OP—Off-Peak ....................
29 .............
Increment Peaking Name ..
X ..................
P—Peak .............................
29 .............
Increment Peaking Name ..
X ..................
N/A—Not Applicable ..........
30 .............
30 .............
Product Type Name ...........
Product Type Name ...........
X ..................
X ..................
............................................
CB—Cost Based ................
30 .............
Product Type Name ...........
X ..................
CR—Capacity Reassignment.
30 .............
Product Type Name ...........
X ..................
MB—Market Based ............
30 .............
Product Type Name ...........
X ..................
T—Transmission ................
30 .............
Product Type Name ...........
X ..................
Other ..................................
31 .............
Product Name ....................
X ..................
Quantity ..............................
33 .............
Units ...................................
34 .............
Rate ...................................
35 .............
Rate Minimum ....................
36 .............
Rate Maximum ...................
If specified in
the contract.
If specified in
the contract.
One of four
rate fields
(34, 35,
36, or 37)
must be included.
One of four
rate fields
(34, 35,
36, or 37)
must be included.
One of four
rate fields
(34, 35,
36, or 37)
must be included.
See Product Name Table,
Appendix A.
Number with up to 4 decimals.
Terms 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).
Terms of the contract (if specifically noted in the contract) set for one year or more (≥ 1 year).
Terms of the contract do not specify an increment.
See definitions for each increment peaking name
below.
The product described may be sold during those hours
designated as on-peak and off-peak in the NERC region of the point of delivery.
The product described may be sold only during those
hours designated as off-peak in the NERC region of
the point of delivery.
The product described may be sold only during those
hours designated as on-peak in the NERC region of
the point of delivery.
To be used only when the increment peaking name is
not specified in the contract.
See definitions for each product type below.
Energy or capacity sold under a FERC-approved costbased rate tariff.
An agreement under which a transmission provider
sells, assigns or transfers all or portion of its rights
to an eligible customer.
Energy or capacity sold under the seller’s FERC-approved market-based rate tariff.
The product is sold under a FERC-approved transmission tariff.
The product cannot be characterized by the other
product type names.
Description of product being offered.
32 .............
dwashington3 on PRODPC61 with RULES
Field No.
VerDate Aug<31>2005
15:01 Nov 03, 2008
Jkt 217001
PO 00000
Quantity for the contract product identified.
See Units Table, Appendix
E.
Measure stated in the contract for the product sold.
Number with up to 4 decimals.
The charge for the product per unit as stated in the
contract.
Number with up to 4 decimals.
Minimum rate to be charged per the contract, if a
range is specified.
Number with up to 4 decimals.
Maximum rate to be charged per the contract, if a
range is specified.
Frm 00039
Fmt 4700
Sfmt 4700
E:\FR\FM\04NOR1.SGM
04NOR1
65534
Federal Register / Vol. 73, No. 214 / Tuesday, November 4, 2008 / Rules and Regulations
EQR DATA DICTIONARY—Continued
Field No.
Field
Required
Value
Definition
37 .............
Rate Description ................
One of four
rate fields
(34, 35,
36, or 37)
must be included.
Unrestricted text .................
38 .............
Rate Units ..........................
See Rate Units Table, Appendix F.
39 .............
Point of Receipt Balancing
Authority (PORBA).
If specified in
the contract.
If specified in
the contract.
Text description of rate. If the rate is currently available
on the FERC Web site, 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 Web site, 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.
Measure stated in the contract for the product sold.
40 .............
Point of Receipt Specific
Location (PORSL).
If specified in
the contract.
Unrestricted text (50 characters). If ‘‘HUB’’ is selected for PORCA, see
Hub Table, Appendix C.
41 .............
Point of Delivery Balancing
Authority (PODBA).
If specified in
the contract.
See Balancing Authority
Table, Appendix B.
42 .............
Point of Delivery Specific
Location (PODSL).
If specified in
the contract.
43 .............
Begin Date .........................
44 .............
End Date ............................
45 .............
Time Zone ..........................
If specified in
the contract.
If specified in
the contract.
X ..................
Unrestricted text (50 characters). If ‘‘HUB’’ is selected for PODCA, see
Hub Table, Appendix C.
YYYYMMDDHHMM ...........
See Balancing Authority
Table, Appendix B.
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.
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. 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.
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.
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.
First date for the sale of the product at the rate specified.
YYYYMMDDHHMM ...........
Last date for the sale of the product at the rate specified.
See Time Zone Table, Appendix D.
The time zone in which the sales will be made under
the contract.
Transaction Data
dwashington3 on PRODPC61 with RULES
46 .............
VerDate Aug<31>2005
Transaction Unique ID .......
15:01 Nov 03, 2008
Jkt 217001
X ..................
PO 00000
An integer preceded by the
letter ‘‘T’’ (only used
when importing transaction data).
Frm 00040
Fmt 4700
Sfmt 4700
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.
E:\FR\FM\04NOR1.SGM
04NOR1
Federal Register / Vol. 73, No. 214 / Tuesday, November 4, 2008 / Rules and Regulations
65535
EQR DATA DICTIONARY—Continued
Field
Required
47 .............
Seller Company Name ......
X ..................
Unrestricted text (100
Characters).
48 .............
Customer Company Name
X ..................
49 .............
Customer DUNS Number ..
X ..................
Unrestricted text (70 Characters).
Nine digit number ..............
50 .............
FERC Tariff Reference ......
X ..................
Unrestricted text (60 Characters).
51 .............
Contract Service Agreement ID.
X ..................
Unrestricted text (30 Characters).
52 .............
Transaction Unique Identifier.
Transaction Begin Date .....
X ..................
53 .............
Transaction End Date ........
X ..................
Last date and time the product is sold during the quarter.
55 .............
Time Zone ..........................
X ..................
56 .............
Point of Delivery Balancing
Authority (PODBA).
X ..................
Unrestricted text (24 Characters).
YYYYMMDDHHMM (csv
import),
MMDDYYYYHHMM
(manual entry).
YYYYMMDDHHMM (csv
import),
MMDDYYYYHHMM
(manual entry).
See Time Zone Table, Appendix D.
See Balancing Authority
Table, Appendix B.
The unique nine digit number assigned by Dun and
Bradstreet to the counterparty to the contract.
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.
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.
Unique reference number assigned by the seller for
each transaction.
First date and time the product is sold during the quarter.
54 .............
57 .............
Point of Delivery Specific
Location (PODSL).
X ..................
58 .............
58 .............
Class Name .......................
Class Name .......................
X ..................
X ..................
Unrestricted text (50 characters). If ‘‘HUB’’ is selected for PODBA, see
Hub Table, Appendix C.
............................................
F—Firm ..............................
58 .............
Class Name .......................
X ..................
NF—Non-firm .....................
58 .............
Class Name .......................
X ..................
UP—Unit Power Sale ........
58 .............
Class Name .......................
X ..................
BA—Billing Adjustment ......
58 .............
Class Name .......................
X ..................
N/A—Not Applicable ..........
59 .............
dwashington3 on PRODPC61 with RULES
Field No.
Term Name ........................
X ..................
60 .............
60 .............
Increment Name ................
Increment Name ................
X ..................
X ..................
LT—Long Term, ST—Short
Term, N/A—Not Applicable.
............................................
H—Hourly ..........................
60 .............
Increment Name ................
X ..................
D—Daily .............................
VerDate Aug<31>2005
15:01 Nov 03, 2008
Jkt 217001
X ..................
PO 00000
Value
Frm 00041
Fmt 4700
Sfmt 4700
Definition
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).
The name of the counterparty.
The time zone in which the sales will be made under
the contract.
The registered NERC Balancing Authority (formerly
called NERC Control Area) abbreviation used in
OASIS applications.
The specific location at which the product is delivered.
If receipt occurs at a trading hub, a standardized
hub name must be used.
See class name definitions below.
A sale, service or product that is not interruptible for
economic reasons.
A 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.
Designates a dedicated sale of energy and capacity
from one or more than one specified generation
unit(s).
Designates 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.
To be used only when the other available class names
do not apply.
Power sales transactions with durations of one year or
greater are long-term. Transactions with shorter durations are short-term.
See increment name definitions below.
Terms of the particular sale set for up to 6 consecutive
hours (≤ 6 consecutive hours). Includes LMP based
sales in ISO/RTO markets.
Terms 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.
E:\FR\FM\04NOR1.SGM
04NOR1
65536
Federal Register / Vol. 73, No. 214 / Tuesday, November 4, 2008 / Rules and Regulations
EQR DATA DICTIONARY—Continued
Field No.
Field
Required
Value
Definition
60 .............
Increment Name ................
X ..................
W—Weekly ........................
60 .............
Increment Name ................
X ..................
M—Monthly ........................
60 .............
Increment Name ................
X ..................
Y—Yearly ...........................
60 .............
Increment Name ................
X ..................
N/A—Not Applicable ..........
61 .............
61 .............
Increment Peaking Name ..
Increment Peaking Name ..
X ..................
X ..................
............................................
FP—Full Period .................
61 .............
Increment Peaking Name ..
X ..................
OP—Off-Peak ....................
61 .............
Increment Peaking Name ..
X ..................
P—Peak .............................
61 .............
Increment Peaking Name ..
X ..................
N/A—Not Applicable ..........
62 .............
Product Name ....................
X ..................
63 .............
Transaction Quantity ..........
X ..................
64 .............
Price ...................................
X ..................
See Product Names Table,
Appendix A.
Number with up to 4 decimals.
Number with up to 6 decimals.
Terms 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.
Terms of the particular sale 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.
Terms 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).
To be used only when other available increment
names do not apply.
See definitions for increment peaking below.
The product described was sold during Peak and OffPeak hours.
The product described was sold only during those
hours designated as off-peak in the NERC region of
the point of delivery.
The product described was sold only during those
hours designated as on-peak in the NERC region of
the point of delivery.
To be used only when the other available increment
peaking names do not apply.
Description of product being offered.
65 .............
Rate Units ..........................
X ..................
66 .............
Total Transmission Charge
X ..................
67 .............
Total Transaction Charge ..
X ..................
See Rate Units Table, Appendix F.
Number with up to 2 decimals.
Number with up to 2 decimals.
The quantity of the product in this transaction.
Actual price charged for the product per unit. The price
reported cannot be averaged or otherwise aggregated.
Measure appropriate to the price of the product sold.
Payments received for transmission services when explicitly identified.
Transaction Quantity (Field 63) times Price (Field 64)
plus Total Transmission Charge (Field 66).
EQR DATA DICTIONARY
[Appendix A. Product Names]
Contract
product
Transaction
product
Definition
BLACK START SERVICE
X
X
BOOKED OUT POWER ...
........................
X
CAPACITY ........................
CUSTOMER CHARGE .....
X
X
X
X
DIRECT ASSIGNMENT
FACILITIES CHARGE.
EMERGENCY ENERGY ...
X
........................
X
........................
ENERGY ...........................
ENERGY IMBALANCE .....
dwashington3 on PRODPC61 with RULES
Product name
X
X
X
X
EXCHANGE ......................
X
X
FUEL CHARGE ................
X
X
Service available after a system-wide blackout where a generator participates in
system restoration activities without the availability of an outside electric supply
(Ancillary Service).
Energy or capacity contractually committed bilaterally for delivery but not actually
delivered due to some offsetting or countervailing trade (Transaction only).
A quantity of demand that is charged on a $/KW or $/MW basis.
Fixed contractual charges assessed on a per customer basis that could include
billing service.
Charges for facilities or portions of facilities that are constructed or used for the
sole use/benefit of a particular customer.
Contractual provisions to supply energy or capacity to another entity during critical situations.
A quantity of electricity that is sold or transmitted over a period of time.
Service provided when a difference occurs between the scheduled and the actual delivery of energy to a load obligation (Ancillary Service). For Contracts,
reported if the contract provides for sale of the product. For Transactions,
sales by third-party providers (i.e., non-transmission function) are reported.
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.
Charge based on the cost or amount of fuel used for generation.
VerDate Aug<31>2005
15:01 Nov 03, 2008
Jkt 217001
PO 00000
Frm 00042
Fmt 4700
Sfmt 4700
E:\FR\FM\04NOR1.SGM
04NOR1
Federal Register / Vol. 73, No. 214 / Tuesday, November 4, 2008 / Rules and Regulations
65537
EQR DATA DICTIONARY—Continued
[Appendix A. Product Names]
Contract
product
Transaction
product
Definition
GENERATOR IMBALANCE.
X
X
GRANDFATHERED BUNDLED.
INTERCONNECTION
AGREEMENT.
X
X
X
........................
MEMBERSHIP AGREEMENT.
MUST RUN AGREEMENT
NEGOTIATED-RATE
TRANSMISSION.
NETWORK ........................
NETWORK OPERATING
AGREEMENT.
X
........................
Service provided when a difference occurs between the output of a generator located in the Transmission Provider’s Control Area and a delivery schedule
from that generator to (1) another Control Area or (2) a load within the Transmission Provider’s Control Area over a single hour (Ancillary Service). For
Contracts, reported if the contract provides for sale of the product. For Transactions, sales by third-party providers (i.e., non-transmission function) are reported.
Services provided for bundled transmission, ancillary services and energy under
contracts effective prior to Order No. 888’s OATTs.
Contract 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.
Agreement to participate and be subject to rules of a system operator.
X
X
........................
X
X
X
........................
........................
OTHER ..............................
POINT-TO-POINT
AGREEMENT.
REACTIVE SUPPLY &
VOLTAGE CONTROL.
REAL POWER TRANSMISSION LOSS.
REGULATION & FREQUENCY RESPONSE.
X
X
X
........................
X
X
X
X
X
X
REQUIREMENTS SERVICE.
X
X
SCHEDULE SYSTEM
CONTROL & DISPATCH.
X
X
SPINNING RESERVE ......
X
X
SUPPLEMENTAL RESERVE.
X
X
SYSTEM OPERATING
AGREEMENTS.
X
........................
TOLLING ENERGY ..........
X
X
TRANSMISSION OWNERS AGREEMENT.
X
........................
UPLIFT ..............................
X
X
dwashington3 on PRODPC61 with RULES
Product name
VerDate Aug<31>2005
15:01 Nov 03, 2008
Jkt 217001
PO 00000
Frm 00043
An agreement that requires a unit to run.
Transmission performed under a negotiated rate contract (applies only to merchant transmission companies).
Transmission service under contract providing network service.
An 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.
Product name not otherwise included.
Transmission service under contract between specified Points of Receipt and
Delivery.
Production or absorption of reactive power to maintain voltage levels on transmission systems (Ancillary Service).
The loss of energy, resulting from transporting power over a transmission system.
Service 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). For Contracts,
reported if the contract provides for sale of the product. For Transactions,
sales by third-party providers (i.e., non-transmission function) are reported.
Firm, 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.)
Scheduling, 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).
Unloaded 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).
For Contracts, reported if the contract provides for sale of the product. For
Transactions, sales by third-party providers (i.e., non-transmission function)
are reported.
Service 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). For Contracts, reported if the contract provides
for sale of the product. For Transactions, sales by third-party providers (i.e.,
non-transmission function) are reported.
An 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.
Energy sold from a plant whereby the buyer provides fuel to a generator (seller)
and receives power in return for pre-established fees.
The agreement that establishes the terms and conditions under which a transmission owner transfers operational control over designated transmission facilities.
A make-whole payment by an RTO/ISO to a utility.
Fmt 4700
Sfmt 4700
E:\FR\FM\04NOR1.SGM
04NOR1
65538
Federal Register / Vol. 73, No. 214 / Tuesday, November 4, 2008 / Rules and Regulations
EQR DATA DICTIONARY
[Appendix B. Balancing Authority]
dwashington3 on PRODPC61 with RULES
Balancing authority
Abbreviation
Outside US *
AESC, LLC—Wheatland CIN ......................................................................................................................
Alabama Electric Cooperative, Inc ..............................................................................................................
Alberta Electric System Operator ................................................................................................................
Alliant Energy Corporate Services, LLC—East ...........................................................................................
Alliant Energy Corporate Services, LLC—West ..........................................................................................
Ameren Transmission ..................................................................................................................................
Ameren Transmission, Illinois ......................................................................................................................
Ameren Transmission, Missouri ..................................................................................................................
American Transmission Systems, Inc .........................................................................................................
Aquila Networks—Kansas ...........................................................................................................................
Aquila Networks—Missouri Public Service ..................................................................................................
Aquila Networks—West Plains Dispatch .....................................................................................................
Arizona Public Service Company ................................................................................................................
Associated Electric Cooperative, Inc ...........................................................................................................
Avista Corp ..................................................................................................................................................
Batesville Balancing Authority .....................................................................................................................
Big Rivers Electric Corp ..............................................................................................................................
Board of Public Utilities ...............................................................................................................................
Bonneville Power Administration Transmission ..........................................................................................
British Columbia Transmission Corporation ................................................................................................
California Independent System Operator ....................................................................................................
Carolina Power & Light Company—CPLW .................................................................................................
Carolina Power and Light Company—East .................................................................................................
Central and Southwest ................................................................................................................................
Central Illinois Light Co ...............................................................................................................................
Chelan County PUD ....................................................................................................................................
Cinergy Corporation .....................................................................................................................................
City of Homestead .......................................................................................................................................
City of Independence P&L Dept ..................................................................................................................
City of Tallahassee ......................................................................................................................................
City Water Light & Power ............................................................................................................................
Cleco Power LLC .........................................................................................................................................
Columbia Water & Light ..............................................................................................................................
Comision Federal de Electricidad ................................................................................................................
Constellation Energy Control and Dispatch—Arkansas ..............................................................................
Constellation Energy Control and Dispatch—City of Benton, AR ...............................................................
Constellation Energy Control and Dispatch—City of Ruston, LA ...............................................................
Constellation Energy Control and Dispatch—Conway, Arkansas ...............................................................
Constellation Energy Control and Dispatch—Gila River .............................................................................
Constellation Energy Control and Dispatch—Harquehala ..........................................................................
Constellation Energy Control and Dispatch—North Little Rock, AK ...........................................................
Constellation Energy Control and Dispatch—West Memphis, Arkansas ....................................................
Dairyland Power Cooperative ......................................................................................................................
DECA, LLC—Arlington Valley .....................................................................................................................
Duke Energy Corporation ............................................................................................................................
East Kentucky Power Cooperative, Inc .......................................................................................................
El Paso Electric ...........................................................................................................................................
Electric Energy, Inc ......................................................................................................................................
Empire District Electric Co., The .................................................................................................................
Entergy .........................................................................................................................................................
ERCOT ISO .................................................................................................................................................
Florida Municipal Power Pool ......................................................................................................................
Florida Power & Light ..................................................................................................................................
Florida Power Corporation ...........................................................................................................................
Gainesville Regional Utilities .......................................................................................................................
Georgia System Operations Corporation ....................................................................................................
Georgia Transmission Corporation ..............................................................................................................
Grand River Dam Authority .........................................................................................................................
Grant County PUD No. 2 .............................................................................................................................
Great River Energy ......................................................................................................................................
Great River Energy ......................................................................................................................................
Great River Energy ......................................................................................................................................
Great River Energy ......................................................................................................................................
GridAmerica .................................................................................................................................................
Hoosier Energy ............................................................................................................................................
Hydro-Quebec, TransEnergie ......................................................................................................................
Idaho Power Company ................................................................................................................................
Illinois Power Co ..........................................................................................................................................
Illinois Power Co ..........................................................................................................................................
Imperial Irrigation District .............................................................................................................................
Indianapolis Power & Light Company .........................................................................................................
AEWC ........................
AEC ...........................
AESO ........................
ALTE .........................
ALTW ........................
AMRN ........................
AMIL ..........................
AMMO .......................
FE ..............................
WPEK ........................
MPS ...........................
WPEC ........................
AZPS .........................
AECI ..........................
AVA ...........................
BBA ...........................
BREC ........................
KACY .........................
BPAT .........................
BCTC .........................
CISO ..........................
CPLW ........................
CPLE .........................
CSWS ........................
CILC ..........................
CHPD ........................
CIN ............................
HST ...........................
INDN ..........................
TAL ............................
CWLP ........................
CLEC .........................
CWLD ........................
CFE ...........................
PUPP .........................
BUBA .........................
DERS ........................
CNWY .......................
GRMA ........................
HGMA ........................
DENL .........................
WMUC .......................
DPC ...........................
DEAA .........................
DUK ...........................
EKPC .........................
EPE ...........................
EEI .............................
EDE ...........................
EES ...........................
ERCO ........................
FMPP ........................
FPL ............................
FPC ...........................
GVL ...........................
GSOC ........................
GTC ...........................
GRDA ........................
GCPD ........................
GRE ...........................
GREC ........................
GREN ........................
GRES ........................
GA .............................
HE .............................
HQT ...........................
IPCO ..........................
IP ...............................
IPRV ..........................
IID ..............................
IPL .............................
........................
........................
X
........................
........................
........................
........................
........................
........................
........................
........................
........................
........................
........................
........................
........................
........................
........................
........................
X
........................
........................
........................
........................
........................
........................
........................
........................
........................
........................
........................
........................
........................
X
........................
........................
........................
........................
........................
........................
........................
........................
........................
........................
........................
........................
........................
........................
........................
........................
........................
........................
........................
........................
........................
........................
........................
........................
........................
........................
........................
........................
........................
........................
........................
X
........................
........................
........................
........................
........................
VerDate Aug<31>2005
15:01 Nov 03, 2008
Jkt 217001
PO 00000
Frm 00044
Fmt 4700
Sfmt 4700
E:\FR\FM\04NOR1.SGM
04NOR1
Federal Register / Vol. 73, No. 214 / Tuesday, November 4, 2008 / Rules and Regulations
65539
EQR DATA DICTIONARY—Continued
[Appendix B. Balancing Authority]
dwashington3 on PRODPC61 with RULES
Balancing authority
Abbreviation
Outside US *
ISO New England Inc ..................................................................................................................................
JEA ..............................................................................................................................................................
Kansas City Power & Light Co ....................................................................................................................
Lafayette Utilities System ............................................................................................................................
LG&E Energy Transmission Services .........................................................................................................
Lincoln Electric System ...............................................................................................................................
Los Angeles Department of Water and Power ...........................................................................................
Louisiana Energy & Power Authority ...........................................................................................................
Louisiana Generating, LLC ..........................................................................................................................
Madison Gas and Electric Company ...........................................................................................................
Manitoba Hydro Electric Board, Transmission Services .............................................................................
Michigan Electric Coordinated System ........................................................................................................
Michigan Electric Coordinated System—CONS ..........................................................................................
Michigan Electric Coordinated System—DECO ..........................................................................................
MidAmerican Energy Company ...................................................................................................................
Midwest ISO ................................................................................................................................................
Minnesota Power, Inc ..................................................................................................................................
Montana-Dakota Utilities Co ........................................................................................................................
Muscatine Power and Water .......................................................................................................................
Nebraska Public Power District ...................................................................................................................
Nevada Power Company .............................................................................................................................
New Brunswick Power Corporation .............................................................................................................
New Horizons Electric Cooperative .............................................................................................................
New York Independent System Operator ...................................................................................................
North American Electric Reliability Council .................................................................................................
Northern Indiana Public Service Company .................................................................................................
Northern States Power Company ................................................................................................................
NorthWestern Energy ..................................................................................................................................
Ohio Valley Electric Corporation .................................................................................................................
Oklahoma Gas and Electric .........................................................................................................................
Ontario—Independent Electricity Market Operator .....................................................................................
OPPD CA/TP ...............................................................................................................................................
Otter Tail Power Company ..........................................................................................................................
P.U.D. No. 1 of Douglas County .................................................................................................................
PacifiCorp-East ............................................................................................................................................
PacifiCorp-West ...........................................................................................................................................
PJM Interconnection ....................................................................................................................................
Portland General Electric .............................................................................................................................
Public Service Company of Colorado .........................................................................................................
Public Service Company of New Mexico ....................................................................................................
Puget Sound Energy Transmission .............................................................................................................
Reedy Creek Improvement District .............................................................................................................
Sacramento Municipal Utility District ...........................................................................................................
Salt River Project .........................................................................................................................................
Santee Cooper .............................................................................................................................................
SaskPower Grid Control Centre ..................................................................................................................
Seattle City Light .........................................................................................................................................
Seminole Electric Cooperative ....................................................................................................................
Sierra Pacific Power Co.—Transmission ....................................................................................................
South Carolina Electric & Gas Company ....................................................................................................
South Mississippi Electric Power Association .............................................................................................
South Mississippi Electric Power Association .............................................................................................
Southeastern Power Administration—Hartwell ............................................................................................
Southeastern Power Administration—Russell .............................................................................................
Southeastern Power Administration—Thurmond ........................................................................................
Southern Company Services, Inc ................................................................................................................
Southern Illinois Power Cooperative ...........................................................................................................
Southern Indiana Gas & Electric Co ...........................................................................................................
Southern Minnesota Municipal Power Agency ............................................................................................
Southwest Power Pool ................................................................................................................................
Southwestern Power Administration ............................................................................................................
Southwestern Public Service Company ......................................................................................................
Sunflower Electric Power Corporation .........................................................................................................
Tacoma Power .............................................................................................................................................
Tampa Electric Company ............................................................................................................................
Tennessee Valley Authority ESO ................................................................................................................
Trading Hub .................................................................................................................................................
TRANSLink Management Company ...........................................................................................................
Tucson Electric Power Company ................................................................................................................
Turlock Irrigation District ..............................................................................................................................
Upper Peninsula Power Co .........................................................................................................................
ISNE ..........................
JEA ............................
KCPL .........................
LAFA .........................
LGEE .........................
LES ............................
LDWP ........................
LEPA .........................
LAGN .........................
MGE ..........................
MHEB ........................
MECS ........................
CONS ........................
DECO ........................
MEC ..........................
MISO .........................
MP .............................
MDU ..........................
MPW ..........................
NPPD ........................
NEVP .........................
NBPC ........................
NHC1 .........................
NYIS ..........................
TEST .........................
NIPS ..........................
NSP ...........................
NWMT .......................
OVEC ........................
OKGE ........................
IMO ............................
OPPD ........................
OTP ...........................
DOPD ........................
PACE .........................
PACW ........................
PJM ...........................
PGE ...........................
PSCO ........................
PNM ..........................
PSEI ..........................
RC .............................
SMUD ........................
SRP ...........................
SC .............................
SPC ...........................
SCL ...........................
SEC ...........................
SPPC .........................
SCEG ........................
SME ...........................
SMEE ........................
SEHA .........................
SERU ........................
SETH .........................
SOCO ........................
SIPC ..........................
SIGE ..........................
SMP ...........................
SWPP ........................
SPA ...........................
SPS ...........................
SECI ..........................
TPWR ........................
TEC ...........................
TVA ...........................
HUB ...........................
TLKN .........................
TEPC .........................
TIDC ..........................
UPPC ........................
........................
........................
........................
........................
........................
........................
........................
........................
........................
........................
X
........................
........................
........................
........................
........................
........................
........................
........................
........................
........................
X
........................
........................
........................
........................
........................
........................
........................
........................
X
........................
........................
........................
........................
........................
........................
........................
........................
........................
........................
........................
........................
........................
........................
X
........................
........................
........................
........................
........................
........................
........................
........................
........................
........................
........................
........................
........................
........................
........................
........................
........................
........................
........................
........................
........................
........................
........................
........................
........................
VerDate Aug<31>2005
15:01 Nov 03, 2008
Jkt 217001
PO 00000
Frm 00045
Fmt 4700
Sfmt 4700
E:\FR\FM\04NOR1.SGM
04NOR1
65540
Federal Register / Vol. 73, No. 214 / Tuesday, November 4, 2008 / Rules and Regulations
EQR DATA DICTIONARY—Continued
[Appendix B. Balancing Authority]
Balancing authority
Abbreviation
Outside US *
Utilities Commission, City of New Smyrna Beach ......................................................................................
Westar Energy—MoPEP Cities ...................................................................................................................
Western Area Power Administration—Colorado-Missouri ...........................................................................
Western Area Power Administration—Lower Colorado ..............................................................................
Western Area Power Administration—Upper Great Plains East ................................................................
Western Area Power Administration—Upper Great Plains West ...............................................................
Western Farmers Electric Cooperative .......................................................................................................
Western Resources dba Westar Energy .....................................................................................................
Wisconsin Energy Corporation ....................................................................................................................
Wisconsin Public Service Corporation ........................................................................................................
Yadkin, Inc ...................................................................................................................................................
NSB ...........................
MOWR .......................
WACM .......................
WALC ........................
WAUE ........................
WAUW .......................
WFEC ........................
WR ............................
WEC ..........................
WPS ..........................
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
[Appendix C. Hub]
HUB
Definition
ADHUB .................................
The aggregated Locational Marginal Price (‘‘LMP’’) nodes defined by PJM Interconnection, LLC as the AEP/Dayton Hub.
The aggregated Locational Marginal Price (‘‘LMP’’) nodes defined by PJM Interconnection, LLC as the
AEPGenHub.
The set of delivery points along the California-Oregon commonly identified as and agreed to by the counterparties
to constitute the COB Hub.
The set of delivery points commonly identified as and agreed to by the counterparties to constitute delivery into
the Cinergy balancing authority.
The aggregated Elemental Pricing nodes (‘‘Epnodes’’) defined by the Midwest Independent Transmission System
Operator, Inc., as Cinergy Hub (MISO).
The set of delivery points commonly identified as and agreed to by the counterparties to constitute delivery into
the Entergy balancing authority.
The aggregated Elemental Pricing nodes (‘‘Epnodes’’) defined by the Midwest Independent Transmission System
Operator, Inc., as FE Hub (MISO).
The 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.
The aggregated Elemental Pricing nodes (‘‘Epnodes’’) defined by the Midwest Independent Transmission System
Operator, Inc., as Illinois Hub (MISO).
The set of delivery points at or near Hoover Dam commonly identified as and agreed to by the counterparties to
constitute the Mead Hub.
The aggregated Elemental Pricing nodes (‘‘Epnodes’’) defined by the Midwest Independent Transmission System
Operator, Inc., as Michigan Hub (MISO).
The set of delivery points along the Columbia River commonly identified as and agreed to by the counterparties
to constitute the Mid-Columbia Hub.
The aggregated Elemental Pricing nodes (‘‘Epnodes’’) defined by the Midwest Independent Transmission System
Operator, Inc., as Minnesota Hub (MISO).
The aggregated Locational Marginal Price (‘‘LMP’’) nodes defined by ISO New England Inc., as Mass Hub.
The aggregated Locational Marginal Price (‘‘LMP’’) nodes defined by PJM Interconnection, LLC as the Northern
Illinois Hub.
The set of delivery points along the Nevada-Oregon border commonly identified as and agreed to by the
counterparties to constitute the NOB Hub.
The 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.
The set of delivery points commonly identified as and agreed to by the counterparties to constitute delivery into
the Northwestern Energy Montana balancing authority.
The aggregated Locational Marginal Price nodes (‘‘LMP’’) defined by PJM Interconnection, LLC as the PJM East
Hub.
The aggregated Locational Marginal Price (‘‘LMP’’) nodes defined by PJM Interconnection, LLC as the PJM
South Hub.
The aggregated Locational Marginal Price (‘‘LMP’’) nodes defined by PJM Interconnection, LLC as the PJM
Western Hub.
The 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.
The set of delivery points commonly identified as and agreed to by the counterparties to constitute delivery into
the Southern Company balancing authority.
The 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.
The set of delivery points commonly identified as and agreed to by the counterparties to constitute delivery into
the Tennessee Valley Authority balancing authority.
AEPGenHub .........................
COB ......................................
Cinergy (into) ........................
Cinergy Hub (MISO) ............
Entergy (into) ........................
FE Hub .................................
Four Corners ........................
Illinois Hub (MISO) ...............
Mead ....................................
Michigan Hub (MISO) ..........
Mid-Columbia (Mid-C) ..........
Minnesota Hub (MISO) ........
NEPOOL (Mass Hub) ..........
NIHUB ..................................
NOB ......................................
NP15 ....................................
NWMT ..................................
PJM East Hub ......................
PJM South Hub ....................
PJM West Hub .....................
dwashington3 on PRODPC61 with RULES
Palo Verde ...........................
SOCO (into) .........................
SP15 .....................................
TVA (into) .............................
VerDate Aug<31>2005
15:01 Nov 03, 2008
Jkt 217001
PO 00000
Frm 00046
Fmt 4700
Sfmt 4700
E:\FR\FM\04NOR1.SGM
04NOR1
Federal Register / Vol. 73, No. 214 / Tuesday, November 4, 2008 / Rules and Regulations
65541
EQR DATA DICTIONARY—Continued
[Appendix C. Hub]
HUB
Definition
ZP26 .....................................
The 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
EQR DATA DICTIONARY—Continued
Appendix D. Time Zone
Appendix F. Rate Units
Time zone
Definition
AD .....................
AP .....................
AS .....................
CD ....................
CP .....................
CS .....................
ED .....................
EP .....................
ES .....................
MD ....................
MP ....................
MS ....................
NA .....................
PD .....................
PP .....................
PS .....................
UT .....................
Rate units
$/MW–DAY .......
$/MW–MO ........
Atlantic Daylight.
Atlantic Prevailing.
Atlantic Standard.
Central Daylight.
Central Prevailing.
Central Standard.
Eastern Daylight.
Eastern Prevailing.
Eastern Standard.
Mountain Daylight.
Mountain Prevailing.
Mountain Standard.
Not Applicable.
Pacific Daylight.
Pacific Prevailing.
Pacific Standard.
Universal Time.
Definition
dollars per megawatt day.
dollars per megawatt
month.
dollars per megawatt
week.
dollars per megawatt year.
dollars per megavar year.
dollars per reactive kilovar
amperes.
cents.
cents per kilovolt amperes.
cents per kilowatt hour.
rate not specified in any
other units.
$/MW–WK ........
$/MW–YR .........
$/MVAR–YR .....
$/RKVA .............
CENTS .............
CENTS/KVR .....
CENTS/KWH ....
FLAT RATE ......
[FR Doc. E8–26209 Filed 11–3–08; 8:45 am]
BILLING CODE 6717–01–P
EQR DATA DICTIONARY
SOCIAL SECURITY ADMINISTRATION
Appendix E. Units
20 CFR Parts 404 and 416
Units
Definition
KV .....................
KVA ..................
KVR ..................
KW ....................
KWH .................
KW–DAY ..........
KW–MO ............
KW–WK ............
KW–YR .............
MVAR–YR ........
MW ...................
MWH .................
MW–DAY ..........
MW–MO ...........
MW–WK ...........
MW–YR ............
RKVA ................
FLAT RATE ......
Kilovolt.
Kilovolt Amperes.
Kilovar.
Kilowatt.
Kilowatt Hour.
Kilowatt Day.
Kilowatt Month.
Kilowatt Week.
Kilowatt Year.
Megavar Year.
Megawatt.
Megawatt Hour.
Megawatt Day.
Megawatt Month.
Megawatt Week.
Megawatt Year.
Reactive Kilovolt Amperes.
Flat Rate.
EQR DATA DICTIONARY
Appendix F. Rate Units
Rate units
Definition
dwashington3 on PRODPC61 with RULES
$/KV ..................
$/KVA ...............
$/KVR ...............
$/KW .................
$/KWH ..............
$/KW–DAY .......
$/KW–MO .........
$/KW–WK .........
$/KW–YR ..........
$/MW ................
$/MWH ..............
VerDate Aug<31>2005
dollars per
dollars per
peres.
dollars per
dollars per
dollars per
dollars per
dollars per
dollars per
dollars per
dollars per
dollars per
kilovolt.
kilovolt amkilovar.
kilowatt.
kilowatt hour.
kilowatt day.
kilowatt month.
kilowatt week.
kilowatt year.
megawatt.
megawatt hour.
15:01 Nov 03, 2008
Jkt 217001
[Docket No. SSA–2007–0093]
RIN 0960–AG02
Technical Revisions to Overpayment
Rules
Social Security Administration.
Final rules.
AGENCY:
ACTION:
SUMMARY: These rules amend our title II
regulations to explicitly provide that we
apply an underpayment due an
individual to reduce an overpayment to
that individual in certain cases. Our title
XVI regulations already state this policy.
Additionally, these rules reflect our
procedures for collecting overpayments
when a payment of more than the
correct amount is made to a
representative payee on behalf of a
beneficiary after the beneficiary’s death.
These rules clarify that we collect
overpayments in this situation from
only the representative payee or his
estate but not from the representative
payee’s spouse or from the spouse’s
estate.
These rules are effective
December 4, 2008.
DATES:
FOR FURTHER INFORMATION CONTACT:
Joshua Silverman, Office of Regulations,
Social Security Administration, 6401
Security Boulevard, Baltimore, MD
21235–6401, (410) 594–2128, for
PO 00000
Frm 00047
Fmt 4700
Sfmt 4700
information about these rules. For
information on eligibility or filing for
benefits, call our national toll-free
number, 1–800–772–1213 or TTY
1–800–325–0778, or visit our Internet
site, Social Security Online, at https://
www.socialsecurity.gov.
SUPPLEMENTARY INFORMATION:
Electronic Version
The electronic file of this document is
available on the date of publication in
the Federal Register at https://
www.gpoaccess.gov/fr/.
Explanation of Changes
Reducing Overpayments
We can apply underpayments to
reduce overpayments. 42 U.S.C.
404(a)(1)(A) and 1383(b)(1)(A). Our
current title XVI regulations explicitly
provide that we ‘‘apply any
underpayment due an individual to
reduce any overpayment to that
individual that we determine to exist
* * * for a different period, unless we
have waived recovery of the
overpayment * * *.’’ 20 CFR 416.543.
However, there is no parallel section in
our current title II regulations. We are
modifying our regulations to reflect our
current process of applying
underpayments to reduce overpayments
under title II.
We are amending 20 CFR 404.503 to
state that we will apply any
underpayment due an individual to
reduce any overpayment owed by that
individual that we determine to exist for
a different period, unless we waive
recovery. In cases when the underpaid
individual has died, we will make the
adjustment before distributing any
underpayment according to the priority
list in 20 CFR 404.503(b).
Overpayments Made to Representative
Payees
Under title II, we currently collect
overpayments from an overpaid
beneficiary, from any other beneficiary
entitled to benefits based an overpaid
beneficiary’s earnings, or from the estate
of a deceased overpaid individual. 20
CFR 404.502. Under title XVI, we may
collect overpayments from the overpaid
recipient, his eligible spouse, or the
recipient’s or eligible spouse’s estate if
one of them dies before we finish
E:\FR\FM\04NOR1.SGM
04NOR1
]]>Agencies
[Federal Register Volume 73, Number 214 (Tuesday, November 4, 2008)]
[Rules and Regulations]
[Pages 65526-65541]
From the Federal Register Online via the Government Printing Office [www.gpo.gov]
[FR Doc No: E8-26209]
=======================================================================
-----------------------------------------------------------------------
DEPARTMENT OF ENERGY
Federal Energy Regulatory Commission
18 CFR Part 35
[Docket Nos. RM01-8-009 and RM01-8-010]
Revised Public Utility Filing Requirements for Electric Quarterly
Reports
Issued October 28, 2008.
AGENCY: Federal Energy Regulatory Commission, DOE.
ACTION: Order No. 2001-I; Order Revising Electric Quarterly Report
(EQR) Data Dictionary.
-----------------------------------------------------------------------
SUMMARY: In this order, the Federal Energy Regulatory Commission
(Commission) revises the EQR Data Dictionary to define and rename Field
22 of the EQR to ``Commencement Date of Contract Terms'' and to clarify
the information to be reported in the EQR concerning ancillary
services. These revisions will make reporting this information less
burdensome and more accessible.
DATES: Effective Date: This order will become effective upon
publication in the Federal Register. The definitions adopted in this
order shall be used in filing the Q1, 2009 EQR due on April 30, 2009
and in subsequent filings of the EQR.
FOR FURTHER INFORMATION CONTACT:
Mark Blazejowski (Technical Information), Office of Enforcement,
Federal Energy Regulatory Commission, 888 First Street, NE.,
Washington, DC 20426, (202) 502-6055.
Gary D. Cohen (Legal Information), Office of the General Counsel,
Federal Energy Regulatory Commission, 888 First Street, NE.,
Washington, DC 20426, (202) 502-8321.
SUPPLEMENTARY INFORMATION:
Before Commissioners: Joseph T. Kelliher, Chairman; Suedeen G. Kelly,
Marc Spitzer, Philip D. Moeller, and Jon Wellinghoff.
1. In this order, after consideration of the comments filed in
response to our notices seeking comment,\1\ we are revising the
Electric Quarterly Report (EQR) Data Dictionary. Specifically, we are
revising the EQR Data Dictionary to define and rename Field 22 of the
EQR to ``Commencement Date of Contract Terms,'' as this field is
intended to be used to identify when the current terms of the reported
contract became effective. This order also clarifies the information to
be reported in the EQR concerning ancillary services.
---------------------------------------------------------------------------
\1\ Revised Public Utility Filing Requirements for Electric
Quarterly Reports, 73 FR 12983 (Mar. 11, 2008), FERC Stats. & Regs.
] 35,557 (2008) (EQR Ancillary Services Notice); Revised Public
Utility Filing Requirements for Electric Quarterly Reports, 73 FR
30543 (May 28, 2008), FERC Stats. & Regs. ] 35,558 (2008)
(Commencement Date Notice).
---------------------------------------------------------------------------
I. Background
A. EQRs and EQR Data Dictionary
2. On April 25, 2002, the Commission issued Order No. 2001, a final
rule establishing revised public utility filing requirements. This rule
requires public utilities to file EQRs summarizing specified pertinent
data about their currently effective contracts (contract data) and data
about wholesale power sales they made during the reporting period
(transaction data).\2\ 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.
---------------------------------------------------------------------------
\2\ Revised Public Utility Filing Requirements, Order No. 2001,
67 FR 31043, FERC Stats. & Regs. ] 31,127 (2002), reh'g denied,
Order No. 2001-A, 100 FERC ] 61,074 (2002), reh'g denied, Order No.
2001-B, 100 FERC ] 61,342 (2002).
---------------------------------------------------------------------------
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's Web site. This provision
obviates the need to revise the Commission's regulations to implement
revisions to the EQR 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 on how to report certain transactions.\3\
---------------------------------------------------------------------------
\3\ See, e.g., Notice Providing Guidance on the Filing of
Information on Transmission Capacity Reassignments in Electric
Quarterly Reports, 124 FERC ] 61,244 (2008), which provided guidance
on complying with the Commission's Order No. 890-B reporting
requirements; Revised Public Utility Filing Requirements, Order No.
2001-E, 105 FERC ] 61,352 (2003), where the Commission standardized
the terminology for control areas; and Revised Public Utility Filing
Requirements, 67 FR 65973 (Oct. 29, 2002), FERC Stats. & Regs. ]
35,045 (Oct. 21, 2002), which provided general guidance for using
the EQR software.
---------------------------------------------------------------------------
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 and
providing formal definitions for fields that were previously undefined.
B. Commencement Date
5. On December 20, 2007, the Commission issued Order No. 2001-H,
which addressed a pending request for rehearing and clarified the
information to be reported in several EQR data fields. In Order No.
2001-H, the Commission defined Field 22 in the Contract Data section of
the EQR, named ``Contract Commencement Date,'' 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.\4\
---------------------------------------------------------------------------
\4\ Revised Public Utility Filing Requirements for Electric
Quarterly Reports, Order No. 2001-H, 121 FERC ] 61,289 (2007), Data
Dictionary at Field 22.
6. On February 26, 2008, the Commission held a technical conference
to ``review the EQR Data Dictionary and address questions from EQR
users.'' \5\
[[Page 65527]]
During this technical conference, the participants discussed, among
other matters, whether the Commission intended in Order No. 2001-H for
the commencement date field to be used to report the date the contract
terms reported in the EQR (original or amended) became effective. On
April 17, 2008, in response to participants' requests, the Commission's
Director, Office of Enforcement, issued a waiver, for the first quarter
of 2008, of the requirement to file EQRs using the commencement date
definition as clarified in Order No. 2001-H.\6\ On July 9, 2008, the
waiver was extended until final action is taken in this docket.\7\
---------------------------------------------------------------------------
\5\ See Notice of Electric Quarterly Reports Technical
Conference, 73 FR 2477 (Jan. 15, 2008).
\6\ See Edison Electric Institute, Docket Nos. RM01-8-000, RM01-
8-007 and ER02-2001-000 (Apr. 17, 2008) (unpublished letter order).
\7\ See Edison Electric Institute, Docket Nos. RM01-8-000, RM01-
8-007 and ER02-2001-000 (July 9, 2008) (unpublished letter order).
---------------------------------------------------------------------------
7. On May 28, 2008, the Commission issued the Commencement Date
Notice to invite comment on the issues raised in the technical
conference. In addition, the Commencement Date Notice proposed defining
commencement date as:
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 have not been amended
since January 1, 2008, the initial date the contract became
effective may be used.
8. The Commission also proposed renaming the field to
``Commencement Date of Contract Terms.'' \8\ On April 10, 2008, three
entities filed timely comments on the Commencement Date Notice.\9\
---------------------------------------------------------------------------
\8\ As noted above, Field 22 has been previously titled
``Contract Commencement Date.''
\9\ Timely comments on the Commencement Date Notice were filed
by: Edison Electric Institute (EEI); Sempra Energy, Inc. (Sempra);
and Occidental Power Services, Inc. (Occidental).
---------------------------------------------------------------------------
C. Ancillary Service Reporting
9. Order No. 888 adopted six ancillary services to be included in
the open access transmission tariff (OATT): Scheduling, System Control
and Dispatch (Schedule 1); Reactive Supply and Voltage Control
(Schedule 2); Regulation and Frequency Response (Schedule 3); Energy
Imbalance (Schedule 4); Operating Reserve--Spinning-or Spinning
Reserve--(Schedule 5); and Operating Reserve--Supplemental--or
Supplemental Reserve--(Schedule 6).\10\
---------------------------------------------------------------------------
\10\ Promoting Wholesale Competition Through Open Access Non-
discriminatory Transmission Services by Public Utilities; Recovery
of Stranded Costs by Public Utilities and Transmitting Utilities,
Order No. 888, 61 FR 21540 (May 10, 1996), FERC Stats. & Regs. ]
31,036 (1996), order on reh'g, Order No. 888-A, 62 FR 12274 (Mar.
14, 1997), FERC Stats. & Regs. ] 31,048 (1997), order on reh'g,
Order No. 888-B, 81 FERC ] 61,248 (1997), order on reh'g, Order No.
888-C, 82 FERC ] 61,046 (1998), aff'd in relevant part sub nom.
Transmission Access Policy Study Group v. FERC, 225 F.3d 667 (D.C.
Cir. 2000) (TAPS v. FERC), aff'd sub nom. New York v. FERC, 535 U.S.
1 (2002).
---------------------------------------------------------------------------
10. The six ancillary services established in Order No. 888 are now
offered under the Order No. 890 pro forma OATT. In Order No. 890, the
Commission also adopted ``generator imbalance'' as a new ancillary
service.\11\
---------------------------------------------------------------------------
\11\ Preventing Undue Discrimination and Preference in
Transmission Service, Order No. 890, 72 FR 12266 (Mar. 15, 2007),
FERC Stats. & Regs. ] 31,241, at P 668 (2007), order on reh'g, Order
No. 890-A, 73 FR 2984 (Jan. 16, 2008), FERC Stats. and Regs. ]
31,261 (2007), order on reh'g, Order No. 890-B, 123 FERC ] 61,299
(2008).
---------------------------------------------------------------------------
11. On June 21, 2007, the Commission issued Order No. 697, a Final
Rule that codified and, in certain respects, revised the Commission's
standards for market-based rate authority for sales of electric energy,
capacity, and ancillary services.\12\ Among other matters, Order No.
697 addressed the posting and reporting requirements for third-party
sellers of ancillary services at market-based rates.
---------------------------------------------------------------------------
\12\ 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 (2007),
clarifying order, 121 FERC ] 61,260 (2007), order on reh'g, Order
No. 697-A, 73 FR 25,832 (May 7, 2008), FERC Stats. & Regs. ] 31,268
(2008).
---------------------------------------------------------------------------
12. The matter of third-party sellers of ancillary services at
market-based rates had previously been addressed in Avista Corporation,
87 FERC ] 61,223, order on reh'g, 89 FERC ] 61,136 (1999) (Avista),
among other cases. Avista provided a policy that third-party ancillary
service providers that could not perform a market power study would be
allowed to sell ancillary services at market-based rates, under certain
conditions. The authorization in Avista extended only to the following
four ancillary services: Regulation Service; Energy Imbalance Service;
Spinning Reserves; and Supplemental Reserves.
13. On March 3, 2008, the Commission issued the EQR Ancillary
Services Notice to clarify the requirement to report third-party
ancillary service transactions. The notice proposed adding the phrase
``Reported for power sales and transmission-related transactions'' to
clarify the EQR reporting requirements with regard to Energy Imbalance,
Regulation & Frequency Response, Spinning Reserve, and Supplemental
Reserve--the four products identified in Avista--``to clarify that
sales of these services must be reported both in the Contract and
Transaction sections of the EQR.'' The notice also proposed to add
Generator Imbalance as a Product Name in the EQR.\13\ On June 27, 2008,
three entities filed comments in response to the EQR Ancillary Services
Notice.\14\
---------------------------------------------------------------------------
\13\ EQR Ancillary Services Notice, FERC Stats. & Regs. ] 35,557
at P 12.
\14\ Timely comments on the EQR Ancillary Services Notice were
filed by: EEI; California Independent System Operator Corporation
(CAISO); and PJM Interconnection, L.L.C. (PJM).
---------------------------------------------------------------------------
II. Discussion
A. Commencement Date
1. Comments
14. CAISO states that it supports the intent of the proposed
clarification of the definition of the ``Contract Commencement Date''
in the EQR Data Dictionary and the proposal to rename that EQR field as
``Commencement Date of Contract Terms.'' However, CAISO is concerned
that the proposed commencement date definition (Field 22) is confusing
because it refers to ``the Contract Data section of the EQR'' in the
second sentence and ``the Contract Products section'' elsewhere.\15\
CAISO recommends that the Commission only require that entries to Field
22 be changed as a result of matters affecting the Contract Products
section of the contract data and not based on any other revisions to a
contract. CAISO argues that other information included in the EQR has
no substantive effect on Field 22. CAISO also suggests that, rather
than referring to the ``Commencement Date,'' the definition should
refer specifically to ``Commencement Date of Contract Terms.''
---------------------------------------------------------------------------
\15\ EQR filers summarize their contracts in the Contract Data
section of the EQR: Fields 14 through 45. Fields 14 through 20 of
the Contract Data section capture the seller/customer identification
information and fields 21 through 25 capture relevant contract dates
such as commencement and termination dates. The Contract Products
section (Fields 26 through 45) is a subset of the Contract Data
section describing the various offerings under the contract such as
firm and non-firm, long-term, short-term.
---------------------------------------------------------------------------
15. EEI's comments generally support the proposed modification.
EEI, however, requests that the Commission modify the definition to
make clear that if the terms of the contract reported in the Contract
Products section have not been amended since January 1, 2008, the filer
may, at its election, use the initial date the contract became
effective (or absent an effective date the initial
[[Page 65528]]
date when service began) as the contract commencement date, even if the
terms of the contract reported in the Contract Products section were
amended prior to January 1, 2008.
16. PJM states that the proposed commencement date definition seems
to raise the possibility that an EQR filer may begin reporting a
contract upon its effective date. PJM raises the concern that this
conflicts with the statement in Order No. 2001 that ``the requirement
to file contract data and transaction data begins with the first
Electric Quarterly Report filed after service commences under an
agreement.'' \16\ PJM asks that the Commission ``permit public
utilities to report agreements in their EQRs upon their effective dates
* * * rather than when service is taken under the agreements.''
---------------------------------------------------------------------------
\16\ Order No. 2001, FERC Stats. & Regs. ] 31,127 at P 216.
---------------------------------------------------------------------------
2. Commission Determination
17. With regard to CAISO's comments regarding which revisions to
contract terms necessitate changes to the date reported in the
commencement date field, we note that, in Order No. 2001-H, the
Commission stated:
There is a very real public interest in identifying when key
terms of the contract were determined. As market conditions change
over time, it is imperative to be able to sort the deals that
occurred years ago from those that were confirmed more recently. To
better understand the market conditions at the time a contract was
put in place, it is necessary to document the date that key terms
were established.\17\
---------------------------------------------------------------------------
\17\ Order No. 2001-H, 121 FERC ] 61,289 at P 12.
18. As discussed below, based on our consideration of the comments,
the Commission concludes that additional specificity is needed to
provide clarity. As an initial matter, we adopt the NOPR's proposal to
change the name of Field 22 to ``Commencement Date of Contract Terms.''
We note that several commenters filed comments supporting such a
change, and no comment was filed that raised objections to this
proposal.
19. In addition, as discussed below, we are also revising the
definition of Field 22 to clearly delineate the contractual changes
that would require a change in the date reported.
20. With regard to EEI's comments, we agree with the suggestion
regarding pre-2008 amendments. In particular, EEI suggests we add the
phrase ``or absent an effective date the initial date when service
began.'' We find this additional phrase further clarifies that the
Commission does not intend to require filers to research contract
histories to comply with its requirements for this field and,
accordingly, we will adopt this proposal.
21. Second, we reject EEI's suggestion that we add the phrase ``the
Filer at its election may use'' because we find that such a phrase
would result in greater ambiguity, rather than clarity, by offering a
range of options on what may be reported rather than requiring a
standard by which all filers must comply. Further, the notion of
inconsistent filings is contrary to the intention of the EQR Data
Dictionary, which was created to reduce the range of possible
interpretations for appropriate entries in the EQR. Such allowable
disparities make the data less uniform and less useful.
22. Finally, we reject the EEI suggestion to add the phrase, ``even
if the terms of the contract reported in the Contract Products section
were amended prior to January 1, 2008'' because we find it redundant
and subject to conflicting interpretations.
23. Accordingly, we rename Field 22 in the EQR as ``Commencement
Date of Contract Terms.'' The field is defined as:
The date the terms of the contract reported in fields 18, 23 and
25 through 45 (as defined in the data dictionary) became effective.
If those terms became effective on multiple dates (i.e., due to one
or more amendments), the date to be reported in this field 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 reported in fields 18,
23 and 25 through 45 have not been amended since January 1, 2009,
the initial date the contract became effective (or absent an
effective date the initial date when service began) may be used.
24. This definition will become effective on January 1, 2009 and
will be applicable for EQRs filed beginning in the first quarter of
2009. The start date for the reporting of contract amendments has been
changed in the definition to January 1, 2009, to account for the
effective date of the revised EQR Data Dictionary that we are adopting
in this order. The limited waiver for compliance that the Commission
granted on April 17, 2008 and extended on July 9, 2008 will apply to
all 2008 EQRs.\18\
---------------------------------------------------------------------------
\18\ The expiration date of the limited waiver also applies to
the Increment Name fields (Fields 28 and 60), for which additional
time was provided to comply with Order No. 2001-G.
---------------------------------------------------------------------------
25. PJM is incorrect in its interpretation that the proposed
commencement date definition raises the possibility that an EQR filer
may begin reporting a contract upon its effective date. The
commencement date definition specifies which date should be used to
populate the field and does not otherwise address when a contract must
first be reported in the EQR. The Commission recognizes that,
logistically, it may be more convenient to begin reporting a contract
upon execution. Although the requirement to file a contract in the EQR
once service under that contract commences will remain in effect, the
Commission neither prohibits nor discourages the earlier reporting of
contracts.
B. Ancillary Service Reporting
1. Comments
26. With regard to third-party ancillary service transactions, the
EQR Ancillary Services Notice proposed to add to the phrase ``Reported
for power sales and transmission-related transactions'' to clarify the
EQR reporting requirements with regard to Energy Imbalance, Regulation
& Frequency Response, Spinning Reserve, and Supplemental Reserve in
Appendix A (Product Names) to the EQR Data Dictionary. The notice also
proposed to add the product ``Generator Imbalance'' in the Appendix.
27. In response to this notice, EEI filed comments arguing that
ancillary services associated with transmission contracts should not be
reported in the EQR. Thus, EEI suggests that the reporting requirements
regarding Energy Imbalance, Regulation & Frequency Response, Spinning
Reserve, and Supplemental Reserve be changed to read as follows: ``For
Contracts, reported if the contract provides for sale of the product.
For Transactions, sales by third-party providers (i.e., non-
transmission function) are reported.'' EEI argues that its proposed
language is superior to that proposed by the Commission, because the
language proposed in the EQR Ancillary Services Notice may cause
confusion over whether transmission-related agreements are to be
reported in the EQR. EEI states that ``the Commission has never
required transmission functions to report ancillary service sales in
the Transactions portion of the EQR, which was established in Order No.
2001,'' and ``the suggested changes to the Appendix A definitions may
not clearly enough reflect this existing policy.''
28. EEI also states that ``the definition for Energy Imbalance and
the proposed definition for Generator Imbalance do not indicate that
they may be Ancillary Services'' and asks ``the Commission to clarify
that Energy Imbalance and Generator Imbalance can be an [sic] Ancillary
Services, and that * * *
[[Page 65529]]
[o]nly ancillary services provided by a marketer are reportable
transactions, though both marketers and transmission functions must
list them in the Contracts section of the EQR.''
2. Commission Determination
29. Order No. 2001 stated:
We clarify that ancillary service transaction data associated
with transmission need not be reported when the transmission
services are provided on an unbundled basis * * * On the other hand,
ancillary service transaction data associated with power sales are
currently required to be filed in Quarterly Transaction Reports and
the requirement to file these data is retained in this rule.\19\
---------------------------------------------------------------------------
\19\ Order No. 2001 at P 271.
30. Our proposal in the EQR Ancillary Services Notice was intended
to provide clarification regarding the EQR reporting requirements for
ancillary services provided in association with unbundled sales of
transmission services rather than to change the policy (quoted
immediately above) that we established in Order No. 2001.\20\
---------------------------------------------------------------------------
\20\ Order No. 697, FERC Stats. & Regs. ] 31,252 at P 1058.
---------------------------------------------------------------------------
31. Accordingly, with regard to EEI's suggested changes to the
reporting requirements for Energy Imbalance, Regulation & Frequency
Response, Spinning Reserve, and Supplemental Reserve, the Commission
finds that EEI's proposal provides additional clarity and we therefore
adopt EEI's proposal.
32. Specifically, we revise the ancillary service Product Names as
follows:
Energy Imbalance: Service provided when a difference occurs between
the scheduled and the actual delivery of energy to a load obligation
(Ancillary Service). For Contracts, reported if the contract provides
for sale of the product. For Transactions, sales by third-party
providers (i.e., non-transmission function) are reported.
Generator Imbalance: Service provided when a difference occurs
between the output of a generator located in the Transmission
Provider's Control Area and a delivery schedule from that generator to
(1) another Control Area or (2) a load within the Transmission
Provider's Control Area over a single hour (Ancillary Service). For
Contracts, reported if the contract provides for sale of the product.
For Transactions, sales by third-party providers (i.e., non-
transmission function) are reported.
Regulation & Frequency Response: Service 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). For
Contracts, reported if the contract provides for sale of the product.
For Transactions, sales by third-party providers (i.e., non-
transmission function) are reported.
Spinning Reserve: Unloaded 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). For Contracts, reported if
the contract provides for sale of the product. For Transactions, sales
by third-party providers (i.e., non-transmission function) are
reported.
Supplemental Reserve: Service 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). For Contracts, reported if the contract provides
for sale of the product. For Transactions, sales by third-party
providers (i.e., non-transmission function) are reported.
C. Reporting of Ancillary Service Product Type Names
1. Comments
33. EEI asks the Commission to ``clarify the appropriate manner to
report the Product Type Name [Field No. 30] for ancillary service sales
in the Contracts portion of the EQR,'' namely, that an ancillary
service ``reported by a transmission function'' should be identified
with a Product Type Name of ``T,'' indicating the product was sold
under a FERC-approved transmission tariff. Alternatively, a merchant
sale would be reported as sold under a FERC-approved cost-based tariff
by entering ``CB'' or market-based tariff by entering ``MB'' as
``factual circumstances dictate.''
34. Occidental seeks clarification ``that imbalances that are
settled in the real-time markets operated by the ISOs and RTOs are not
intended to be reported as `Generator Imbalances' under the proposed
revisions to the EQR Data Dictionary.'' Occidental states that
``imbalances that are settled within the organized markets [are]
handled through the settlement process, in which the generator pays the
real-time price for any under production and is paid the real-time
price for any over production [and] should not be reported in the EQRs
as `Generator Imbalances' under this [FERC-proposed] definition.''
2. Commission Determination
35. Regarding EEI's request for clarification, if the transmission
provider (i.e., non-merchant function) makes an ancillary service sale,
the product type is ``T.'' With respect to third-party sales, the
product type is listed as ``CB,'' if the third-party sale is made under
a cost-based rate tariff or ``MB,'' if the third-party sale is made
under a market-based rate tariff. We believe that Product Type Name
[Field No. 30] adequately addresses this distinction and, thus, do not
find any reason to revise the ancillary service reporting requirements
that we proposed in the EQR Ancillary Services Notice to add clarity on
this issue.
36. In addition, we find that Occidental is correct in its
interpretation of the difference between energy imbalance service
offered as an ancillary service in general and the method by which
organized markets address imbalances through settlement in the Real-
Time market. The Commission has adopted conventions for reporting
trading within Real-Time markets.\21\ This order does not change those
conventions.
---------------------------------------------------------------------------
\21\ Revised Public Utility Filing Requirements for Electric
Quarterly Reports, Order No. 2001-G, 120 FERC ] 61,270, at P 55
(2007).
---------------------------------------------------------------------------
D. Whether Ancillary Services Not Included in the OATT Should Be
Reported in EQRs
1. Comments
37. The EQR Ancillary Services Notice invited comment on the need
to include additional non-OATT ancillary services in the list of
Product Names in the EQR Data Dictionary. Two commenters filed comments
addressing this issue. EEI states that it ``recommends against
including any other ancillary services in the EQR at this time.''
38. Sempra comments that ``the industry may benefit from additional
clarification with respect to the reporting of ISO/RTO-specific
ancillary services that may not be currently reflected'' in the OATT.
Sempra also suggests that there are benefits to clarifying ``the
reporting of other ISO/RTO-specific products.'' To this end, Sempra
asks that the Commission clarify ``the appropriate reporting `bucket'
for other CAISO products, such
[[Page 65530]]
as Instructed Imbalance Energy and Uninstructed Imbalance Energy.'' As
to whether the Commission should add specific new ancillary services to
the EQR Data Dictionary, Sempra asks that the Commission ``consider
whether any additional CAISO products or ancillary services should be
included in the EQR Data Dictionary once the CAISO MRTU [Market
Redesign and Technology Upgrade] program is put into effect.'' \22\
---------------------------------------------------------------------------
\22\ We note that, while Sempra asks the Commission to consider
these matters, it does not explicitly advocate that the Commission
add any additional products to the EQR Data Dictionary.
---------------------------------------------------------------------------
2. Commission Determination
39. The Commission will continue its policy of identifying only the
standard OATT ancillary services as ancillary services in the Product
Name field of the EQR. This policy is consistent with the Commission's
intention, in establishing the EQR filing requirements, that the same
kinds of information be reported by all EQR filers, in the same format
and using the same definitions. This approach is intended to allow EQR
users and Commission staff to readily compare and contrast the
transactions and contracts reported by one utility to those of other
utilities. We will continue to add products that reflect common and new
offerings by the industry where it appears that these products are
widely offered, but, in this case, we agree with EEI that the current
list of ancillary service product names to be reported in the EQR is
sufficient.
40. As to Sempra's comments about providing clarification regarding
the appropriate reporting of the specific products offered by CAISO, in
Order No. 2001-E, the Commission encouraged RTOs and ISOs to work with
Commission staff to develop EQR-ready reports to ease the filing
process for respondents and to improve consistency in reporting within
and among the organized markets.\23\ Three ISOs--New York ISO, Midwest
ISO and ISO New England--currently provide reports to their members
that format settlement data for the EQR. PJM expects to begin doing so
by the end of 2008.
---------------------------------------------------------------------------
\23\ Order No. 2001-E, 105 FERC ] 61,352 at P 11.
---------------------------------------------------------------------------
41. In addition, we note that CAISO's staff met with Commission
staff and market participants on May 18, 2004 to map the CAISO's
products to the EQR product list.\24\ Likewise, we encourage CAISO to
meet with Commission staff on MRTU product mapping and provide EQR-
ready reports to ease the filing process for respondents.
---------------------------------------------------------------------------
\24\ Notice of Electric Quarterly Reports Western Outreach
Session, 69 FR 25897 (May 10, 2004). The mapping developed in this
meeting is available on the Commission's Web site (https://
www.ferc.gov/EventCalendar/
EventDetails.aspx?ID=1096&CalType=%20&Date=5/18/
2004&CalendarID=116).
---------------------------------------------------------------------------
III. Document Availability
42. 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 (https://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.
43. 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 Web site
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 changes in the EQR Data
Dictionary shown in the Attachment, as discussed in the body of this
order.
(B) This order will become effective upon publication in the
Federal Register. The definitions adopted in this order shall be used
in filing the Q1, 2009 EQR due on April 30, 2009 and in subsequent
filings of the EQR.
(C) The limited waiver for compliance granted on April 17, 2008 and
extended on July 9, 2008 will apply to all 2008 EQRs and only to 2008
EQRs, regardless of when they are filed.
By the Commission.
Kimberly D. Bose,
Secretary.
Attachment
Electric Quarterly Report Data Dictionary Version 1.1 (Issued October
28, 2008)
EQR Data Dictionary
----------------------------------------------------------------------------------------------------------------
Field No. Field Required Value Definition
----------------------------------------------------------------------------------------------------------------
ID Data
----------------------------------------------------------------------------------------------------------------
1.................. Filer Unique X.................... FR1................. (Respondent)--An
Identifier. 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.
1.................. Filer Unique X.................... FS (where (Seller)--An identifier
Identifier. ``'' is an (e.g., ``FS1'',
integer). ``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.
1.................. Filer Unique X.................... FA1................. (Agent)--An identifier
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.
2.................. Company Name........ X.................... Unrestricted text (Respondent)--The name
(100 characters). of the company taking
responsibility for
complying with the
Commission's
regulations related to
the EQR.
[[Page 65531]]
2.................. Company Name........ X.................... Unrestricted text (Seller)--The name of
(100 characters). 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.
2.................. Company Name........ X.................... Unrestricted text (Agent)--The name of the
(100 characters). entity completing the
EQR filing. The Agent's
Company Name need not
be the name of the
company under
Commission
jurisdiction.
3.................. Company DUNS Number. for Respondent and Nine digit number... The unique nine digit
Seller. number assigned by Dun
and Bradstreet to the
company identified in
Field Number 2.
4.................. Contact Name........ X.................... Unrestricted text (Respondent)--Name of
(50 characters). the person at the
Respondent's company
taking responsibility
for compliance with the
Commission's EQR
regulations.
4.................. Contact Name........ X.................... Unrestricted text (Seller)--The name of
(50 characters). 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.
4.................. Contact Name........ X.................... Unrestricted text (Agent)--Name of the
(50 characters). contact for the Agent,
usually the person who
prepares the filing.
5.................. Contact Title....... X.................... Unrestricted text Title of contact
(50 characters). identified in Field
Number 4.
6.................. Contact Address..... X.................... Unrestricted text... Street address for
contact identified in
Field Number 4.
7.................. Contact City........ X.................... Unrestricted text City for the contact
(30 characters). identified in Field
Number 4.
8.................. Contact State....... X.................... Unrestricted text (2 Two character state or
characters). province abbreviations
for the contact
identified in Field
Number 4.
9.................. Contact Zip......... X.................... Unrestricted text Zip code for the contact
(10 characters) CA-- identified in Field
Canada, MX--Mexico. Number 4.
10................. Contact Country Name X.................... US--United States, Country (USA, Canada,
UK--United Kingdom. Mexico, or United
Kingdom) for contact
address identified in
Field Number 4.
11................. Contact Phone....... X.................... Unrestricted text Phone number of contact
(20 characters). identified in Field
Number 4.
12................. Contact E-Mail...... X.................... Unrestricted text... E-mail address of
contact identified in
Field Number 4.
13................. Filing Quarter...... X.................... YYYYMM.............. A 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
----------------------------------------------------------------------------------------------------------------
14................. Contract Unique ID.. X.................... An integer preceded An identifier beginning
by the letter ``C'' with the letter ``C''
(only used when and followed by a
importing contract number (e.g., ``C1'',
data). ``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.
15................. Seller Company Name. X.................... Unrestricted text The name of the company
(100 characters). 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).
16................. Customer Company X.................... Unrestricted text The name of the
Name. (70 characters). counterparty.
17................. Customer DUNS Number X.................... Nine digit number... The unique nine digit
number assigned by Dun
and Bradstreet to the
company identified in
Field Number 16.
18................. Contract Affiliate.. X.................... Y (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.
[[Page 65532]]
19................. FERC Tariff X.................... Unrestricted text The FERC tariff
Reference. (60 characters). 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.
20................. Contract Service X.................... Unrestricted text Unique identifier given
Agreement ID. (30 characters). 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.
21................. Contract Execution X.................... YYYYMMDD............ The date the contract
Date. was signed. If the
parties signed on
different dates, use
the most recent date
signed.
22................. Commencement Date of X.................... YYYYMMDD............ The date the terms of
Contract Terms. the contract reported
in fields 18, 23 and 25
through 45 (as defined
in the data dictionary)
became effective. If
those terms became
effective on multiple
dates (i.e.: due to one
or more amendments),
the date to be reported
in this field 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
