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.
table that charts list comparision
Inventory as of this Action
Requested
Previously Approved
06/30/2018
36 Months From Approved
06/30/2018
3,802
0
3,802
31,104
0
31,104
0
0
0
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.
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.â
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.
RM16-7-000 NOPR supporting statement FINAL5-26-2016.docx
16 USC 824o.pdf
RM16-7-000 (Reliability Standard BAL-002-2)