RM15-25NOPR non-substantive change_supp state_11-6-2015

FERC-725 (OMB Control No. 1902-0225)

NOPR (Issued 9/17/2015), in Docket RM15-25-000

RIN: 1902-AF11

Supporting Statement for

FERC-725, Certification of Electric Reliability Organization;

Procedures for Electric Reliability Standards

Non-substantive change request for proposal

in the NOPR in Docket RM15-25-000

The Federal Energy Regulatory Commission (Commission or FERC) requests that the Office of Management and Budget (OMB) review and approve this request for a non-substantive change to the FERC-725 information collection. This request is triggered by the Notice of Proposed Rulemaking (NOPR)¹ issued 9/17/15 in Docket RM15-25.

Under section 215 of the Federal Power Act, the Federal Energy Regulatory Commission (Commission or FERC) directs the North American Electric Reliability Corporation (NERC), the Commission-certified Electric Reliability Organization (ERO), to provide Commission staff with access (i.e., view and download data), on a non-public and ongoing basis, to certain databases compiled and maintained by NERC. The Commission’s proposal applies to the following three NERC databases: (1) the Transmission Availability Data System (TADS), (2) the Generator Availability Data System (GADS), and (3) the protection system misoperations database. Access to these databases, which will be limited to data regarding U.S. facilities, will provide the Commission with information necessary for the Commission to determine the need for new or modified Reliability Standards and to better evaluate NERC’s periodic reliability and adequacy assessments.

The Commission proposes to amend its regulations, pursuant to section 215 of the Federal Power Act (FPA), and locate the above proposed requirement within section 39.11 of the Commission’s regulations, which governs the preparation and submission of reliability reports.² Section 39.2(d) of the Commission’s regulations requires NERC and each Regional Entity to “provide the Commission such information as is necessary to implement section 215 of the Federal Power Act.”³ Section 39.2(d) of the Commission’s regulations also requires each user, owner and operator of the Bulk-Power System within the United States (other than Alaska and Hawaii) to provide the Commission, NERC and each applicable Regional Entity with “such information as is necessary to implement section 215 of the Federal Power Act as determined by the Commission and set out in the Rules of the Electric Reliability Organization and each applicable Regional Entity.”⁴

NERC conducts ongoing data collections from registered entities to populate databases for transmission outages through TADS, generation outages through GADS, and protection system misoperations through NERC’s protection system misoperations database. Each of these NERC databases is discussed below.

TADS Database

NERC began collecting TADS data on a mandatory basis in 2007, pursuant to a data request issued in accordance with section 1600 of the NERC Rules of Procedure.⁵ Currently applicable entities (transmission owners) are required to provide certain data for the on-line TADS database based on a common template⁶ each quarter. The TADS database compiles transmission outage data in a common format for:  (1) bulk electric system AC circuits (overhead and underground); (2) transmission transformers (except generator step-up units); (3) bulk electric system AC/DC back-to-back converters; and (4) bulk electric system DC circuits.⁷ The TADS data collection template includes the following information fields: (1) type of facilities, (2) outage start time and duration, (3) event type, (4) initiating cause code, and (5) sustained cause code (for sustained outages).⁸ “Cause codes” for common causes of transmission outages include: (1) lightning, (2) fire, (3) vandalism, (4) failed equipment (with multiple sub-listings), (5) vegetation, and (6) “unknown.”⁹ There were 10,787 TADS events between 2012 and 2014.¹⁰

NERC uses TADS data to develop transmission metrics to analyze outage frequency, duration, causes, and other factors related to transmission outages.¹¹ NERC also provides individual transmission owners with TADS metrics for their facilities.¹² NERC issues an annual public report based on TADS data that shows aggregate metrics for each NERC Region, with the underlying data typically accorded confidential treatment.¹³

GADS Database

The collection of GADS data has been mandatory since 2012, pursuant to a data request issued in accordance with section 1600 of the NERC Rules of Procedure.¹⁴ Currently applicable entities (generator owners) are required to provide certain data for the on-line GADS database based on a common template¹⁵ each quarter. The GADS database collects, records, and retrieves operating information on power plant availability, including event, performance, and design data.¹⁶

Specifically, the GADS database collects outage data pertaining to ten types of conventional generating units with capacity of 20 MW and larger, including: (1) fossil steam including fluidized bed design; (2) nuclear; (3) gas turbines/jet engines; (4) internal combustion engines (diesel engines); (5) hydro units/pumped storage; (6) combined cycle blocks and their related components; (7) cogeneration blocks and their related components; (8) multi-boiler/multi-turbine units; (9) geothermal units; and (10) other miscellaneous conventional generating units (e.g., biomass, landfill gases).¹⁷ The GADS data collection template includes the following design, event, and performance information: (1) design records, (2) event records and (3) performance records.¹⁸ Design records refer to the characteristics of each unit such as GADS utility code, GADS unit code, NERC Regional Entity where the unit is located, name of the unit, commercial operating date, and type of generating unit (fossil, combined cycle, etc.).¹⁹ Event records include information about when and to what extent the generating unit could not generate power.²⁰ Performance records refer to monthly generation, unit‐attempted starts, actual starts, summary event outage information, and fuels.²¹ For 2011-2013, the GADS database contains data from more than 5,000 units.²²

NERC uses GADS data to measure generation reliability and publishes aggregate performance metrics for each NERC Region in publicly available annual state of reliability and reliability assessment reports.²³ The underlying data are typically accorded confidential treatment.

Protection System Misoperations Database

Protection system misoperations data have been reported by transmission owners, generator owners and distribution providers on a mandatory basis since 2011 pursuant to Reliability Standard PRC-004.²⁴ Following implementation of Reliability Standard PRC-004-4, the obligation to report misoperation data will be made mandatory via an on-line database based on a common template²⁵ each quarter. Currently, the protection system misoperations database collects more than 20 fields for a reportable misoperation event, including: (1) misoperation date; (2) event description; (3) protection systems/components that misoperated; (4) equipment removed from service (permanently or temporarily) as the result of the misoperation; (5) misoperation category; and (6) cause(s) of misoperation.²⁶ For 2014, the protection system misoperations database contains information on approximately 2,000 misoperation events.²⁷

Protection system misoperations have exacerbated the severity of most cascading power outages, having played a significant role in the August 14, 2003 Northeast blackout, for example.²⁸ NERC uses protection system misoperations data to assess protection system performance and trends in protection system performance that may negatively impact reliability.²⁹ NERC publishes aggregate misoperation information for each NERC Region in annual public state of reliability reports, with the underlying data typically being accorded confidential treatment.³⁰

Summary of Estimated Burden of this Collection

The Commission’s proposal would make TADS, GADS, and protection system misoperations data, currently collected by the ERO, available to Commission staff on a non-public and ongoing basis. The proposal would not require ERO to collect new information, compile information into any kind of report, or reformulate the raw data. Accordingly, the Commission estimates that the one-time burden associated with compliance with this proposed rule is de minimis and is limited to the ERO reviewing the Commission’s proposed regulation and providing Commission staff with access to the existing TADS, GADS, and protection system misoperations databases.

In addition, the requirement for the ERO to provide the proposed data access to the Commission is included in the existing FERC-725, Certification of Electric Reliability Organization; Procedures for Electric Reliability Standards (OMB Control No. 1902-0225). FERC-725 includes information used by the Commission to implement the statutory provisions of section 215 of the FPA. FERC-725 includes the burden, reporting and recordkeeping requirements associated with: (a) Self Assessment and ERO Application, (b) Reliability Assessments, (c) Reliability Standards Development, (d) Reliability Compliance, (e) Stakeholder Survey, and (f) Other Reporting.

For these reasons, for the NOPR in Docket RM15-25 for FERC-725, the Commission is submitting this non-substantive change. FERC expects no change to existing burden to industry (NERC), and no change to the existing FERC’s federal cost (staffing level).³¹.

For further background and additional information, the last supporting statement (header which formerly indicated “Updated 8/29/12”) for FERC-725 follows. That supporting statement was used for the following submittals:

• GMD Final Rule in Docket RM12-22 for which a non-substantive change request was submitted originally on 5/23/2013 (ICR 201305-1902-009). The OMB decision was ‘pre-approved’. Due to administrative issues, the package was re-submitted on 11/5/2015 (ICR 201511-1902-003).

• ICR 201207-1902-002 (renewal with no change) , submitted 7/10/2012, and approved by OMB on 11/6/2012

Supporting Statement for

FERC‑725, Certification of Electric Reliability Organization;

Procedures for Electric Reliability Standards

(OMB Control No. 1902-0225)

The Federal Energy Regulatory Commission (Commission or FERC) requests that the Office of Management and Budget (OMB) review and approve the extension (for a three-year period) of FERC‑725, Certification of Electric Reliability Organization; Procedures for Electric Reliability Standards.

This is the second time FERC is seeking renewal of the FERC-725 since its initial approval. During the first clearance cycle the Electric Reliability Organization (ERO) program was barely getting started. By the time of the first renewal in 2009, the Commission knew much more about the program, public burden, parties involved, and costs, and provided this information in the clearance package.

Now, after approximately three more years, the ERO program is well established and the Commission believes that the estimates provided in this package are reflective of the current program.

A. JUSTIFICATION

1. CIRCUMSTANCES THAT MAKE THE COLLECTION OF INFORMATION NECESSARY

The Energy Policy Act of 2005 added Section 215 to the Federal Power Act (FPA)³², enhancing the Commission’s ability to strengthen the reliability of the interstate electric grid. Section 215 of the FPA aids the Commission’s efforts to strengthen the reliability of the interstate grid through the granting of new authority to provide for a system of mandatory Reliability Standards developed by the Electric Reliability Organization (ERO) and reviewed and approved by FERC.

On February 3, 2006, the Commission issued Order No.672³³ certifying a single ERO [the North American Electric Reliability Corporation (NERC)], to oversee the reliability of the United States’ portion of the interconnected North American Bulk-Power System, subject to Commission oversight. The ERO is responsible for developing and enforcing the mandatory Reliability Standards. The Reliability Standards apply to all users, owners and operators of the Bulk-Power System. The Commission has the authority to approve all ERO actions, to order the ERO to carry out its responsibilities under these statutory provisions, and (as appropriate) to enforce Reliability Standards. The ERO can delegate its enforcement responsibilities to a Regional Entity. Delegation is effective only after the Commission approves the delegation agreement. A Regional Entity can also propose a Reliability Standard to the ERO for submission to the Commission for approval.

2. HOW, BY WHOM, AND FOR WHAT PURPOSE THE INFORMATION IS TO BE USED AND THE CONSEQUENCES OF NOT COLLECTING THE INFORMATION

The FERC-725 contains the following information collection elements:

Self Assessment and ERO Application: The Commission requires the ERO to submit to FERC a performance assessment report every five years. The next assessment is due in 2015. Each of regional entity submits a performance assessment report to the ERO. Submitting an application to become an ERO is also part of this collection.³⁴

Reliability Assessments: 18 CFR 39.11 requires the ERO to assess the reliability and adequacy of the Bulk-Power System in North America. Subsequently, the ERO must report to the Commission on its findings. Regional entities perform similar assessments within individual regions. Currently the ERO submits to FERC three assessments each year: long term, winter, and summer.

Reliability Standards Development: Under Section 215 of the FPA the ERO is charged with developing Reliability Standards. Regional entities may also develop regional specific standards. Reliability Standards are the principal mechanism provided FERC to ensure reliability on the Bulk-Power System.

Reliability Compliance: Reliability Standards are mandatory and enforceable upon approval by FERC. In addition to the specific information collection requirements contained in each standard (cleared under other information collections), there are general compliance, monitoring and enforcement information collection requirements imposed on applicable entities. Audits, spot checks, self-certifications, exception data submittals, violation reporting, and mitigation plan confirmation are included in this area.

Stakeholder Survey: The ERO used a stakeholder survey to solicit feedback from registered entities³⁵ in preparation for its three year performance assessment. The Commission assumes that the ERO will perform another survey prior to the 2014 performance assessment.

Other Reporting: This category refers to all other reporting requirements imposed on the ERO or regional entities in order to comply with the Commission’s regulations. For example, FERC may require NERC to submit a special reliability assessment. This category is mention to capture these types of one-time filings required of NERC or the Regions.

The Commission implements its responsibilities through 18 CFR Part 39.

Without the FERC-725 information, the FERC, ERO, and Regional Entities will not have the data needed to determine whether sufficient and appropriate measures are being taken to ensure the reliability of the nation’s electric grid.

3. DESCRIBE ANY CONSIDERATION OF THE USE OF IMPROVED TECHNOLOGY TO REDUCE BURDEN AND TECHNICAL OR LEGAL OBSTACLES TO REDUCING BURDEN.

All of the information that is reported to the Commission in this collection may be submitted electronically, through the Commission’s eFiling system (as described at http://www.ferc.gov/docs-filing/efiling.asp). For the remaining information collection requirements (information not submitted to the Commission), the use of current or improved technology is not controlled by the Commission, and is therefore left to the discretion of each reporting entity. However, there is evidence that entities/regions are working together. For example, with the proposed revisions to the definition of “Bulk Electric System” the regional entities are working together to develop common forms to be used for submittal of information (covered under FERC-725J, OMB Control Number 1902-0259).

4. DESCRIBE EFFORTS TO IDENTIFY DUPLICATION AND SHOW SPECIFICALLY WHY ANY SIMILAR INFORMATION ALREADY AVAILABLE CANNOT BE USED OR MODIFIED FOR USE FOR THE PURPOSE(S) DESCRIBED IN INSTRUCTION NO. 2

Filing requirements are periodically reviewed as OMB review dates arise, or as the Commission may deem necessary in carrying out its responsibilities, in order to eliminate duplication and ensure that filing burden is minimized. The Commission believes there are no similar sources of information available that can be used or modified for these reporting purposes.

5. METHODS USED TO MINIMIZE BURDEN IN COLLECTION OF INFORMATION INVOLVING SMALL ENTITIES

This collection impacts small registered entities. The Commission allows small entities to join a joint action agency or similar organization, which could accept responsibility for compliance with the Reliability Standards and related reporting requirements on behalf of its members. In NERC’s compliance database there are 154 entries for Joint Registration Organizations (JROs). FERC does not have records to indicate how many of the 154 entries are small business entities or parties of a joint action agency or similar organization but FERC does estimate that at least half of the listed JROs are large organizations.

The Commission does not know of any barriers that prevent entities from entering into joint action agreements. Generally entities that enter into agreements do this because of shared responsibilities or geographic convenience.

6. CONSEQUENCE TO FEDERAL PROGRAM IF COLLECTION WERE CONDUCTED LESS FREQUENTLY

This collection focuses on electric reliability reporting requirements that are not contained within any Reliability Standards. The Commission approves of these requirements as necessary for the reliable operation of the bulk electric system. Any reduction in frequency may diminish the ability of NERC, Regional Entities, or FERC in maintaining reliability on the bulk electric system.

7. EXPLAIN ANY SPECIAL CIRCUMSTANCES RELATING TO THE INFORMATION COLLECTION

The guidelines of 5 CFR 1320.5(d) are being followed.

8. DESCRIBE EFFORTS TO CONSULT OUTSIDE THE AGENCY: SUMMARIZE PUBLIC COMMENTS AND THE AGENCY'S RESPONSE TO THESE COMMENTS

In accordance with OMB requirements in 5 CFR 1320.8(d), a notice requesting comments on the reporting requirements of FERC-725 was issued in FERC Docket No. IC12-11 on 4/16/12 (at http://elibrary.ferc.gov/idmws/common/opennat.asp?fileID=12947696) and published in the Federal Register (77 FR 24189, 4/23/12). There were no comments filed in response to this notice.

9. EXPLAIN ANY PAYMENT OR GIFTS TO RESPONDENTS

No payments or gifts have been made to respondents.

10. DESCRIBE ANY ASSURANCE OF CONFIDENTIALITY PROVIDED TO RESPONDENTS

The Commission generally does not consider the data to be confidential. However, certain actions have confidentiality provisions which prevent the disclosure of information relating to enforcement actions and critical energy infrastructure information. The following provisions may be used to prevent disclosure of confidential information under FERC 725: (1) 18 CFR § 39.7(b)(4), 39.7(e)(7), 18 CFR § 388.112, and (4) 18 CFR § 388.113.

There are procedures in 18 CFR § 39.7(b)(4), and 39.7(e)(7), which prevent disclosure of information received pursuant to Section 215 of the Federal Power Act, which pertain to violations of Reliability Standards. Section 39.7(b)(4) provides that “each violation or alleged violation shall be treated as nonpublic until the matter is filed with the Commission as a notice of penalty or resolved by an admission that the user, owner or operator of the Bulk-Power System violated a Reliability Standard or by a settlement or other negotiated disposition. The disposition of each violation or alleged violation that relates to a Cybersecurity Incident or that would jeopardize the security of the Bulk-Power System if publicly disclosed shall be nonpublic unless the Commission directs otherwise.” Similarly, Section 39.7(e)(7) provides that “a proceeding for Commission review of a penalty for violation of a Reliability Standard will be public unless the Commission determines that a nonpublic proceeding is necessary and lawful, including a proceeding involving a Cybersecurity Incident. For a nonpublic proceeding, the user, owner or operator of the Bulk-Power System that is the subject of the penalty will be given timely notice and an opportunity for hearing and the public will not be notified and the public will not be allowed to participate.”

In addition,18 C.F.R. 388.112 provides that “any person submitting a document to the Commission may request privileged treatment by claiming that some or all of the information contained in a particular document is exempt from the mandatory public disclosure requirements of the Freedom of Information Act, 5 U.S.C. 552, and should be withheld from public disclosure.”

Finally, 18 CFR § 388.113 of the Commission’s rules and regulations governs access to critical energy infrastructure information (CEII). Under 18 CFR § 388.113(b), the Commission may restrict access to previously filed documents as well as Commission-generated documents which contain CEII information.

11. PROVIDE ADDITIONAL JUSTIFICATION FOR ANY QUESTIONS OF A SENSITIVE NATURE THAT ARE CONSIDERED PRIVATE.

There are no questions of a sensitive nature that are considered private.

12. ESTIMATED BURDEN OF COLLECTION OF INFORMATION; and

The Commission estimates the total public reporting burden for this information collection as:

FERC-725: Certification of the ERO4; Procedures for Electric Reliability Standards
Type of Respondent	Type of Reporting Requirement3	Number of Respondents (A)	Number of Responses Per Respondent (B)36	Total Number of Responses (A)x(B)=(C)	Average Burden Hours per Response (D)	Estimated Total Annual Burden (C)x(D)
Electric Reliability Organization (ERO)3	Self-Assessment	1	0.33	0.33	10,400	3,432
	Reliability Assessments		11	11	3,120	34,320
	Reliability Compliance		1	1	66,467	66,467
	Standards Development		1	1	51,834	51,834
	Other Reporting		1	1	2,080	2,080
Regional Entities	Self-Assessment	8	0.33	2.64	16,640	43,930
	Reliability Assessments		1	8	16,679	133,432
	Reliability Compliance		1	8	39,442.125	315,537
	Standards Development		1	8	4,142 (rounded)	33,134
	Other Reporting		1	8	1,040	8,320
Registered Entities	Stakeholder Survey	1,627	0.33	537	4	2,148
	Reliability Compliance		1	1,627	312.1 (rounded)	507,794
Subtotals:
ERO	N/A6					158,133
Regional						534,353
Registered						509,942
TOTAL		1,636	N/A37	N/A6	N/A6	1,202,428

We provide below more details on the assumptions we used to calculate the burden and where we obtained our information.

ERO and Regional Entities:

Self-assessment: For the ERO we based the figure on the NERC 2009 Business Plan and Budget (in Docket No. RR08-6). 2009 was the last time NERC was required to submit its self-assessment. NERC must submit its next self-assessment in 2014. We assumed one Full-Time Equivalent (FTE) (2,080 hours per year) for each region. Because the assessment will only occur once in the next three years, we assumed 0.33 responses per year.

Reliability Assessments: We based the total hourly amount on the NERC 2012 Business Plan and Budget (in Docket No. RR11-07).

Reliability Compliance: We obtained much of the data from NERC’s 2012 Business Plan and Budget (in Docket No. RR11-07); 2012 Compliance, Monitoring and Enforcement Plan; 2012 Actively Monitored Reliability Standards; and the 2012 Audit Schedule. (For the latter three documents, see http://www.nerc.com/elibrary.php?doc_class=&doc_dept=3&submit=Filter.) We estimated burden hour figures (such as hour per audit, mitigation plan and violation) based on internal staff calculations and some past interaction with NERC staff.

Standards Development: We based the total hourly amount on the NERC 2012 Business Plan and Budget (in Docket No. RR11-07).

Other Reporting: We assumed one FTE for NERC and 0.5 FTE for each Regional Entity.

Registered Entities:

Stakeholder Survey: The 2009 survey contained 70 questions and 135 stakeholders responded. We assume that NERC will use a similar survey for the 2014 self-assessment. Because we are unsure of what the response rate might be for the 2014 survey, we assume that all registered entities will respond and it will require 4 hours per response. Because the survey will only occur once in the next three years we assumed 0.33 responses per respondent per year.

Reliability Compliance: (See “Reliability Compliance” section above.)

Note: Documents in FERC Docket numbers referenced above can be accessed at http://www.ferc.gov/docs-filing/elibrary.asp

The following table shows on aggregate how the collection is impacted by the burden adjustments.

FERC-725	Total Request	Previously Approved	Change due to Adjustment in Estimate	Change Due to Agency Discretion
Annual Number of Responses	2,213	1,809	+404	-
Annual Time Burden (Hr)	1,202,428	972,305	+230,123	-
Annual Cost Burden ($)	65,000	59,390,474	-59,325,474	-

13. ESTIMATE OF THE TOTAL ANNUAL COST BURDEN TO RESPONDENTS

The total estimated annual cost burden related to burden hours is $90,934,468 ($14,197,181 + $41,551,289 + $35,185,998).

ERO Cost: 158,133 hours @ $89.78/hr = $14,197,181

Regional Entity Cost: 534,353 hours @ $77.76/hr = $41,551,289

Registered Entity Cost: 509,942 hours@ $69/hr = $35,185,998

The hourly cost figures are loaded (i.e. includes salary and other personnel costs). The Commission used NERC’s 2012 Business Plan and internal FERC salary estimates for these cost figures.

The Commission also estimates software costs related to the information collections for the ERO at $15,000/year and for the Regional Entities at $50,000/year. These costs are included in ROCIS/reginfo.gov. The costs associated with wages and benefits are not included in the ROCIS metadata.

14. ESTIMATED ANNUALIZED COST TO FEDERAL GOVERNMENT

	Number of Employees (FTEs)	Estimated Annual Federal Cost
Analysis and Processing of filings38	2.67	$383,252
Data Clearance Cost	N/A39	$1,58840
FERC Total	N/A7	$384,840

15. REASONS FOR CHANGES IN BURDEN INCLUDING THE NEED FOR ANY INCREASE

The Commission first estimated the burden for this collection in 2006, at a time when the Reliability program was not yet established. In 2009 the Commission sought renewal of this collection and was able to estimate the burden more accurately than in 2006. In preparing the current renewal request package, the Commission closely examined the current Reliability program and corresponding data. Based on this research, the Commission found that it is necessary to adjust the previous burden estimate. The data show that in the area of Reliability Compliance the number of audits, self-certifications, spot checks, and mitigation plans has increased. The ERO generally decides what Reliability Standard requirements will be audited and which standards will be subject to self-certification. Some of the increase can be accounted for by NERC’s decisions on what to include and not include for compliance activities in a given year. The Commission also found that the area of Reliability Standards development was not included in prior estimates and is including the associated burden in this renewal.

The following table shows how the total burden hours for each group of entities have changed since the last renewal. The figures do not exactly match what appears in ROCIS/RegInfo.gov under the individual ICs because the prior renewal did not split up the ICs by entity type. The IC listed as “modified” (now titled “Registered Entities”) in ROCIS/RegInfo.gov is the IC that did contain the entire collection prior to this submittal.

	2009 Total Burden Hrs	2012 Total Burden Hrs	Difference (adjustment)
ERO	47,64441	158,133	+110,489
Regional Entities	216,880	534,353	+317,473
Registered Entities	707,781	509,942	-197,839

It is important to note that the Commission does not directly control many of the variables that cause the burden hours to need adjustment. NERC, in its role as ERO is charged with the Reliability Standard development, compliance, enforcement, and monitoring. Each year NERC issues updated information regarding the focus of audits and other compliance and monitoring activities. The regional entities also have some autonomy over compliance activities in their respective regions, subject to NERC/Commission oversight.

The increase in burden is necessary in order for FERC, NERC and the Regional Entities to continue to improve the reliability of the bulk-power system.

16. TIME SCHEDULE FOR PUBLICATION OF DATA

There are no tabulations, statistical analysis or publication plans for the information collection. The data are used for regulatory purposes.

17. DISPLAY OF THE EXPIRATION DATE

It is not appropriate to display the expiration date for OMB approval of the information collected. The information will not be collected on a standard, preprinted form which would avail itself to that display. The reporting requirements contain a mixture of narrative descriptions and empirical support that varies depending on the nature of the transaction.

18. EXCEPTIONS TO THE CERTIFICATION STATEMENT

The data collected for this reporting requirement are not used for statistical purposes.

1 The NOPR is posted in FERC’s eLibrary at http://elibrary-backup.ferc.gov/idmws/common/OpenNat.asp?fileID=13989466; Commissioner LaFleur’s statement appears at http://elibrary-backup.ferc.gov/idmws/common/OpenNat.asp?fileID=13989195; the News Release appears at http://elibrary-backup.ferc.gov/idmws/common/OpenNat.asp?fileID=13989193.

2 18 CFR 39.11.

3 18 CFR 39.2(d).

4 Id.

5 See generally NERC, Summary of Phase I TADS Data Collection (November 9, 2007), available at http://www.nerc.com/pa/RAPA/tads/TADSTF%20Archives%20DL/TADS_Data_Request_Summary.pdf.

6 See generally NERC, Transmission Availability Data System (TADS) Data Reporting Instruction Manual (November 20, 2007), available at http://www.nerc.com/ comm/PC/Transmission%20Availability%20Data%20System%20Working%20Grou/TADSTF%20Archives/Data_Reporting_Instr_Manual_11_20_07.pdf.

7 See NERC TADS Home Page, available at http://www.nerc.com/pa/RAPA/tads/Pages/default.aspx.

8 See Transmission Availability Data System (TADS) Data Reporting Instruction Manual (August 1, 2014), available at http://www.nerc.com/pa/RAPA/tads/Documents/2015_TADS_DRI.pdf.

9 See Transmission Availability Data System Definitions (August 1, 2014), available at http://www.nerc.com/pa/RAPA/tads/Documents/2015_TADS_Appendix_7.pdf.

10 See, e.g., NERC, State of Reliability 2015, Appendix A (Statistical Analysis for Risk Issue Identification and Transmission Outage Severity Analysis) at 86 (May 2015), available at http://www.nerc.com/pa/RAPA/PA/Performance%20Analysis%20DL/2015%20State%20of%20Reliability.pdf.

11 See NERC TADS Home Page.

12 Id.

13 Id.

14 See NERC, Generating Availability Data System Mandatory Reporting of Conventional Generation Performance Data at 2 (July 2011), available at http://www.nerc.com/pa/RAPA/gads/MandatoryGADS/Revised_Final_Draft_GADSTF_Recommendation_Report.pdf; see also NERC GADS Home Page, available at http://www.nerc.com/pa/RAPA/gads/Pages/default.aspx.

15 See generally NERC, Transmission Availability Data System (TADS) Data Reporting Instruction Manual (November 20, 2007), available at http://www.nerc.com/ comm/PC/Transmission%20Availability%20Data%20System%20Working%20Grou/TADSTF%20Archives/Data_Reporting_Instr_Manual_11_20_07.pdf.

16 See NERC GADS Home Page.

17 Generating Availability Data System Mandatory Reporting of Conventional Generation Performance Data at 15.

18 Id., Appendix V (Rules of Procedure Section 1600 Justification) at 35.

19 Id.

20 Id.

21 Id.

22 State of Reliability 2015, Appendix B (Analysis of Generation Data) at 107.

23 See, e.g., id., Appendix B (Analysis of Generation Data).

24 The Commission approved Reliability Standard PRC-004-1 (Analysis and Reporting of Transmission Protection System Misoperations) in Order No. 693. Mandatory Reliability Standards for the Bulk-Power System, Order No. 693, FERC Stats. & Regs. ¶ 31,242, at PP 1467-1469, order on reh’g, Order No. 693-A, 120 FERC ¶ 61,053 (2007). The Commission subsequently approved the following revisions and interpretations to Reliability Standard PRC-004, which was renamed Analysis and Mitigation of Transmission and Generation Protection System Misoperations: Reliability Standards PRC-004-1a, PRC-004-2, PRC-004-2a, PRC-004-2.1a, PRC-004-2.1(i)a, PRC-004-3, and PRC-004-4. See North American Electric Reliability Corporation, 136 FERC ¶ 61,208 (2011) (approving interpretation resulting in Reliability Standard PRC-004-1a and Reliability Standard PRC-004-2a); North American Electric Reliability Corp., 134 FERC ¶ 61,015 (2011) (approving Reliability Standard PRC-004-2); Generator Requirements at the Transmission Interface, Order No. 785, 144 FERC ¶ 61,221 (2012) (approving Reliability Standard PRC-004-2.1a); North American Electric Reliability Corp., 151 FERC ¶ 61,129 (2015) (approving Reliability Standard PRC-004-3); North American Electric Reliability Corporation, 151 FERC ¶ 61,186 (2015) (approving Reliability Standards PRC-004-2.1(i)a and PRC-004-4).

As noted in the delegated order in Docket No. RD15-3 (issued 5/29/2015), the reporting requirements for Reliability Standard PRC-004-3, approved by the Commission in Docket No. RD14-14, are pending OMB review under FERC-725G1 (ICR No. 201508-1902-004).

25 See generally NERC, Transmission Availability Data System (TADS) Data Reporting Instruction Manual (November 20, 2007), available at http://www.nerc.com/ comm/PC/Transmission%20Availability%20Data%20System%20Working%20Grou/TADSTF%20Archives/Data_Reporting_Instr_Manual_11_20_07.pdf.

26 Id. at 13-14; see also NERC, Protection System Misoperations Home Page, available at http://www.nerc.com/pa/RAPA/ri/Pages/ProtectionSystemMisoperations.aspx.

27 State of Reliability 2015 at 47.

28 See Request for Data or Information Protection System Misoperation Data Collection at 5.

29 See id. at 14.

30 See, e.g., State of Reliability 2015 at 45-48.

31 Burden for Industry. The existing OMB-approved FERC-725 inventory is a total of 1,202,428 burden hours. (158,133 of those 1,202,428 burden hours relate to the burden imposed on the ERO (NERC).) FERC does not anticipate a change to the burden inventory due to this NOPR in RM15-25; the time associated in providing access to the 3 databases is part of the burden and requirements already covered for the ERO. (Additional details on the components of the burden hours are provided below in #12 of the following supporting statement.)

Federal Cost. As noted in #14 of the supporting statement below, the existing federal cost (staffing level) associated with analysis and processing of the FERC-725 information is 2.67 full-time equivalent employees. FERC has been preparing various analyses. When staff is able to access the databases as proposed in the NOPR in RM15-25, staff expects to improve effectiveness with the additional data and to gain efficiencies. For those reasons and as described above, FERC does not anticipate a change (due to the NOPR in RM15-25) in the number of employees (federal cost) associated with analyzing and processing information.

32 Section 215 was added by the Energy Policy Act of 2005, Pub. L. No. 109-58, 119 Stat. 594 (2005) (codified at 42 USC 16451, et seq.)

33 Rules Concerning Certification of the Electric Reliability Organization; and Procedures for the Establishment, Approval, and Enforcement of Electric Reliability Standards ¶ 31,204 71 FR 8662 (2006) Order on rehearing, 71 FR 19,814 (2006), FERC Statutes and Regulations ¶ 31,212 (2006).

34 The Commission does not expect any new ERO applications to be submitted in the next three years and is not including any burden for this requirement in the burden estimate. FERC still seeks to renew the regulations pertaining to a new ERO application under this renewal but is expecting the burden to be zero for the foreseeable future. 18 CFR 39.3 contains the regulation pertaining to ERO applications.

35 A “registered entity” is an entity that is registered with the ERO. All Bulk-Power System owners, operators and users are required to register with the ERO. Registration is the basis for determining the Reliability Standards with which an entity must comply. See http://www.nerc.com/page.php?cid=3%7C25 for more details.

36 In all instances below where the number of responses per respondent is “1” the Commission acknowledges that actual number of responses varies and cannot be estimated clearly.

37 N/A = not applicable

38 Based upon 2012 FTE average salary plus benefits ($143,540)

39 Not applicable

40 The Commission bases the cost of data clearance on an average of 24 hours per clearance per year. The data clearance cost represents the activities and efforts of FERC staff to comply with the Paperwork Reduction Act of 1995.

41 In the 2009 clearance package this figure was “47,643.67”. The number is rounded up here.

5