In accordance
with 5 CFR 1320, the information collection is approved for three
years with the following terms of clearance. In the resubmission of
this information collection for renewal, the Commission is
requested to include a brief summary of (1) publically-available
analyses, rulemakings, and aggregated data dissemination that this
collection enabled, and/or (2) Commission plans for public
dissemination of this information at a level that maintains the
confidentiality of the data.
Inventory as of this Action
Requested
Previously Approved
06/30/2015
36 Months From Approved
6
0
0
2,334
0
0
0
0
0
[Please note FERC-921 is a new
collection. However it received a 'placeholder' OMB control No. at
the NOPR stage but was not approved by OMB at that point.] FERC is
revising its regulations to require each regional transmission
organization (RTO) and independent system operator (ISO) to
electronically deliver to the FERC, on an ongoing basis, data
related to the markets that it administers. FERC, acting pursuant
to sections 301(b) and 307(a) of the Federal Power Act (FPA), will
amend its regulations to establish ongoing electronic delivery of
data relating to physical and virtual offers and bids, market
awards, resource outputs, marginal cost estimates, shift factors,
financial transmission rights (FTR), internal bilateral contracts,
uplift, and interchange pricing. Such data will facilitate the
FERC's development and evaluation of its policies and regulations
and will enhance FERC efforts to detect anti-competitive or
manipulative behavior, or ineffective market rules, thereby helping
to ensure just and reasonable rates.
The Final Rule minimizes the
added burden on regional organized market administrators by phasing
in implementation requirements and not requiring data to be
consistently formatted across all regional organized markets.
[Those changes resulted from comments since issuance of the
proposed rule.] FERC recognizes that there will be an initial
implementation burden associated with providing the FERC with RTO
and ISO data. This includes submitting a compliance filing to the
FERC, which FERC estimates as a burden of 7 hours per RTO and ISO,
and implementing a process to automatically upload data to an SFTP
site for FERC use (including development, testing and production).
FERC estimates a burden of 1040 hours per RTO and ISO for the
development, testing and production of an automated process to
provide the Commission with the data required in this final rule.
In this regard, though, RTO and ISO markets have already developed
capabilities necessary to handle RTO and ISO data in an automated
manner. For instance, through their Open Access Same-time
Information Systems (OASIS), RTOs and ISOs already make certain
market data publicly available using automated procedures.
Likewise, some RTOs and ISOs have developed procedures similar to
those contained in this final rule to deliver data to their MMUs.
For the recurring effort involved in electronically delivering RTO
and ISO data to the Commission, the Commission anticipates that the
additional burden associated with this rule will be minimal
(estimated at an average of 40 hours per year per respondent). Any
recurring burden would be associated with addressing updates to RTO
and ISO data as the data that they process changes and due to
occasional errors in the data handling or data upload process.
On behalf of this Federal agency, I certify that
the collection of information encompassed by this request complies
with 5 CFR 1320.9 and the related provisions of 5 CFR
1320.8(b)(3).
The following is a summary of the topics, regarding
the proposed collection of information, that the certification
covers:
(i) Why the information is being collected;
(ii) Use of information;
(iii) Burden estimate;
(iv) Nature of response (voluntary, required for a
benefit, or mandatory);
(v) Nature and extent of confidentiality; and
(vi) Need to display currently valid OMB control
number;
If you are unable to certify compliance with any of
these provisions, identify the item by leaving the box unchecked
and explain the reason in the Supporting Statement.