View Information Collection Request (ICR) Package
Skip to main content
An official website of the United States government
The .gov means it's official.
Federal government websites often end in .gov or .mil. Before sharing sensitive information, make sure you're on a federal government site.
The site is secure.
The https:// ensures that you are connecting to the official website and that any information you provide is encrypted and transmitted securely.
Search:
Agenda
Reg Review
ICR
This script is used to control the display of information in this page.
Display additional information by clicking on the following:
All
Brief and OIRA conclusion
Abstract/Justification
Legal Statutes
Rulemaking
FR Notices/Comments
IC List
Burden
Misc.
Common Form Info.
Certification
View Information Collection (IC) List
View Supporting Statement and Other Documents
Please note that the OMB number and expiration date may not have been determined when this Information Collection Request and associated Information Collection forms were submitted to OMB. The approved OMB number and expiration date may be found by clicking on the Notice of Action link below.
View ICR - OIRA Conclusion
OMB Control No:
1902-0268
ICR Reference No:
201605-1902-002
Status:
Historical Inactive
Previous ICR Reference No:
201504-1902-002
Agency/Subagency:
FERC
Agency Tracking No:
FERC-725R
Title:
FERC-725R, (NOPR in RM16-7) Mandatory Reliability Standards: BAL Reliability Standards
Type of Information Collection:
Revision of a currently approved collection
Common Form ICR:
No
Type of Review Request:
Regular
OIRA Conclusion Action:
Comment filed on proposed rule and continue
Conclusion Date:
09/14/2016
Retrieve Notice of Action (NOA)
Date Received in OIRA:
05/26/2016
Terms of Clearance:
OMB files this comment in accordance with 5 CFR 1320.11(c) of the Paperwork Reduction Act and is withholding approval of this collection at this time. This OMB action is not an approval to conduct or sponsor an information collection under the Paperwork Reduction Act of 1995. The agency shall examine public comment in response to the Notice of Proposed Rulemaking and will include in the supporting statement of the next ICR, to be submitted to OMB at the final rule stage, a description of how the agency has responded to any public comments on the ICR. This action has no effect on any current approvals.
Inventory as of this Action
Requested
Previously Approved
Expiration Date
06/30/2018
36 Months From Approved
06/30/2018
Responses
3,802
0
3,802
Time Burden (Hours)
31,104
0
31,104
Cost Burden (Dollars)
0
0
0
Abstract:
NOPR in Docket RM16-7. Reliability Standard BAL-002-2 has three requirements that clarifies the obligations associated with BAL-002 by streamlining and organizing the responsibilities required, thus, enhancing the obligation to maintain reserves and further defining events that predicate action under the standard. Requirement R1: Requirement R1 requires responsible entities [Balancing Authorities (BA) or Reserve Sharing (RSG) Groups] experiencing a Reportable Balancing Contingency Event to deploy its contingency reserves to recover its ACE to prescribed values within the Contingency Event Recovery Period of 15 minutes. Part 1.3.1 provides that a BA or RSG is not subject to Requirement R1, Part 1.1 if: (1) is experiencing a Reliability Coordinator declared Energy Emergency Alert Level; (2) is utilizing its contingency reserve to mitigate an operating emergency in accordance with its emergency Operating Plan, and (3) has depleted its contingency reserve to a level below its Most Severe Single Contingency (MSSC). Part 1.3.2 provides that a BA or RSG is not subject to Requirement R1, Part 1.1 if the balancing authority or reserve sharing group experiences: (1) multiple Contingencies where the combined megawatt (MW) loss exceeds its MSSC and that are defined as a single Balancing Contingency Event or (2) multiple Balancing Contingency Events within the sum of the time periods defined by the Contingency Event Recovery Period and Contingency Reserve Restoration Period whose combined magnitude exceeds the Responsible Entity’s MSSC. Requirement R2: R2 requires responsible entities to demonstrate that their process for calculating their MSSC “surveys all contingencies, including single points of failure, to identify the event that would cause the greatest loss of resource output used by the [reserve sharing group or balancing authority] to meet Firm Demand.” NERC further states that Requirement R2 supports Requirements R1 and R3 in proposed Reliability Standard BAL-002-2 “as these requirements rely on proper calculation of [Most Severe Single Contingency].” Requirement R3: Requirement R3provides that “each Responsible Entity, following a Reportable Balancing Contingency Event, shall restore its Contingency Reserve to at least its Most Severe Single Contingency, before the end of the Contingency Reserve Restoration Period [90 minutes], but any Balancing Contingency Event that occurs before the end of a Contingency Reserve Restoration Period resets the beginning of the Contingency Event Recovery Period.” NERC states that the proposed new definitions for Balancing Contingency Event and Reportable Balancing Contingency Event more clearly identify the types of events that cause frequency deviations necessitating action under the proposed Reliability Standard and provide additional detail regarding the types of resources that may be identified as contingency reserves.
Authorizing Statute(s):
US Code:
16 USC 824o
Name of Law: EPACT 2005
Citations for New Statutory Requirements:
None
Associated Rulemaking Information
RIN:
Stage of Rulemaking:
Federal Register Citation:
Date:
1902-AF21
Proposed rulemaking
81 FR 33441
05/26/2016
Federal Register Notices & Comments
Did the Agency receive public comments on this ICR?
No
Number of Information Collection (IC) in this ICR:
3
IC Title
Form No.
Form Name
RM13-11 Final Rule
RM14-10 Final Rule
RM16-7-000 (Reliability Standard BAL-002-2)
Burden increases because of Program Change due to Agency Discretion:
Yes
Burden Increase Due to:
Miscellaneous Actions
Burden decreases because of Program Change due to Agency Discretion:
No
Burden Reduction Due to:
Short Statement:
The estimated annual burden for the FERC-725R information collection increased due to the NOPR in RM16-7: • The Measure (M1) related to the new Requirement R1 states: Each Responsible Entity shall have, and provide upon request, as evidence, a CR Form 1 with date and time of occurrence to show compliance with Requirement R1. If Requirement R1 part 1.3 applies, then dated documentation that demonstrates compliance with Requirement R1 part 1.3 must also be provided. • The Measure (M2) related to the new Requirement R2 states: “Each Responsible Entity will have the following documentation to show compliance with Requirement R2.” • Data Retention says in part “The Responsible Entity shall retain data or evidence to show compliance for the current year, plus three previous calendar years, unless directed by its Compliance Enforcement Authority to retain specific evidence for a longer period of time as part of an investigation.”
Annual Cost to Federal Government:
$5,193
Does this IC contain surveys, censuses, or employ statistical methods?
No
Is the Supporting Statement intended to be a Privacy Impact Assessment required by the E-Government Act of 2002?
No
Is this ICR related to the Affordable Care Act [Pub. L. 111-148 & 111-152]?
No
Is this ICR related to the Dodd-Frank Wall Street Reform and Consumer Protection Act, [Pub. L. 111-203]?
No
Is this ICR related to the American Recovery and Reinvestment Act of 2009 (ARRA)?
No
Is this ICR related to the Pandemic Response?
Uncollected
Agency Contact:
Enakpodia Agbedia 202 502-6750 enakpodia.agbedia@ferc.gov
Common Form ICR:
No
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:
(a) It is necessary for the proper performance of agency functions;
(b) It avoids unnecessary duplication;
(c) It reduces burden on small entities;
(d) It uses plain, coherent, and unambiguous language that is understandable to respondents;
(e) Its implementation will be consistent and compatible with current reporting and recordkeeping practices;
(f) It indicates the retention periods for recordkeeping requirements;
(g) It informs respondents of the information called for under 5 CFR 1320.8 (b)(3) about:
(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;
(h) It was developed by an office that has planned and allocated resources for the efficient and effective management and use of the information to be collected.
(i) It uses effective and efficient statistical survey methodology (if applicable); and
(j) It makes appropriate use of information technology.
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.
Certification Date:
05/26/2016
An official website of the United States government
The .gov means it's official.
The site is secure.
