Form FERC-730 Report of Transmission Investment Activity

[Excerpt from NOPR in Docket No. RM20-10]

Appendix B

OMB Control Number: 1902-0239

Expiration Date: nn/nn/nnnn

Annual Due Date: April 18

FERC-730, Report of Transmission Investment Activity

Company Name: ________________________________________

To file this form, respondents should follow the instructions for eFiling available at https://www.ferc.gov/docs-filing/efiling.asp.

Template for Table 1

Table 1: Actual and Projected Electric Transmission Capital Spending by Project

			Total Actual and Projected Project Spending on Transmission Facilities During Each Time Period ($ Thousands) (1)
			Actual		Projected
Report Year	Project Code	Project Description	Prior to Report Year	Report Year +0	Report Year +1	Report Year +2	Report Year +3	Report Year +4	Report Year +5	After Report Year +5	Notes
(2)	(3)	(4)	(5)	(6)	(7)					(8)	(9)

Instructions for completing “Table 1”:

(1) Total Actual and Projected Project Spending on Transmission Facilities During Each Time Period is the total actual and projected spending on each project until it is completed. Transmission facilities are defined to be transmission assets as specified in the Uniform System of Accounts in account numbers 350 through 359 (see, 18 CFR Part 101, Uniform System of Accounts Prescribed for Public Utilities and Licensees Subject to the Provisions of the Federal Power Act, for account definitions). The Transmission Plant accounts include: Accounts 350 (Land and Land Rights), 351 (Energy Storage Equipment- Transmission), 352 (Structures and Improvements), 353 (Station Equipment), 354 (Towers and Fixtures), 355 (Poles and Fixtures), 356 (Overhead Conductors and Devices), 357 (Underground Conduit), 358 (Underground Conductors and Devices), and 359 (Roads and Trails).

(2) Report Year is the year associated with data reported in that row. For example, if it is April 2021 and the public utility is reporting on 2020 project activity, the report year is 2020. A public utility can use the same form to correct a prior year’s data. It would just report the data associated with the previous report year as an entry in Table 1.

(3) Project Code is the same Project Code associated with the project as in Table 2 below. Project Code is a 12-character alphanumeric string unique to each project. Respondents should add as many additional rows as are necessary to list all relevant projects. The combination of Report Year and Project Code is the primary key for each record. The primary key allows Table 1 and Table 2 data to be combined into a single table.

(4) Project Description is a descriptive name for the project. It is the same description associated with the project code in Table 2.

(5) Prior to the Report Year is the sum of all Actual spending associated with the project prior to the report year. All capital spending data is formatted as a currency number.

(6) Report Year +0 is the sum of all Actual spending associated with the project during the report year.

(7) Report Year +n means the sum of all Projected spending on the project in the calendar year of the Report Year plus n. For example, if n equals one, and the report year is 2020, then Report Year +1 will be 2021 and that entry would be sum of all Projected spending on the project in the calendar year 2021.

(8) After Report Year +5 means the sum of all Projected spending on the project more than five years past the Report Year. For example, if the report year is 2020, then this entry would be the sum of all spending starting at the beginning of 2026 and continuing until the project is complete. Note, that this entry can be estimated by using the total projected spending on the project, which the public utility already knows.

(9) Notes includes information about spending and estimated spending not included elsewhere. Notes is a 120-character string.

Below is an example of Table 1 associated with a fictitious public utility with two fictitious projects.

Table 1: Actual and Projected Electric Transmission Capital Spending by Project

			Total Actual and Projected Project Spending on Transmission Facilities During Each Time Period ($ Thousands)
			Actual		Projected
Report Year	Project Code	Project Description	Prior to Report Year	Report Year +0	Report Year +1	Report Year +2	Report Year +3	Report Year +4	Report Year +5	After Report Year +5	Notes
2019	AKX0303	Piney Ridge to Fulton	$2600	$28,500	$60,000 (10)	$60,000	$50,000	$0	$0	$0	Revision to 2019 actual
2020	AKX0303	Piney Ridge to Fulton	$31,100	$30,500	$30,000	$40,000	$50,000	$40,000	$0	$0	Cost forecasts are higher and further out due to reroute
2020	AKX0304	Fulton to Grey Pike	$1100	$1000	$36,000	$50,000	$20,000	$0	$0	$0	N/A

(10) The developer should not revise projected data from what it originally reported unless the developer is correcting an obvious data entry mistake.

In this example, the public utility revised the 2019 data. The public utility cannot revise projected data; however, it is appropriate to revise actual data if that data has been reported incorrectly. For example, in 2020 the Prior to Report Year data for project code AKX0303 is $31.1 million. If the sum of Prior to Report Year and Report Year +0 for project code AKX0303 and report year 2019 did not sum to $31.1 million, then the public utility reported the data incorrectly in 2019 and should revise those entries.

Template for Table 2

Table 2: Project Status Details

Report Year	Project Code	Project Description	Project Voltage (kV)	Project Type	Expected Project Completion Date (month/year)	Completion Status	Was Project on Schedule? (Y/N)	If Project Was Not on Schedule, Indicate Reasons for Delay
(1)	(2)	(3)	(4)	(5)	(6)	(7)	(8)	(9)

Instructions for completing “Table 2”:

(1) Report Year is the year of the report data and should be the same as reported in Table 1. There should be no information in Table 2 that could not be known at the end of the report year.

(2) Project Code is a public utility-created alphanumeric designator twelve digits or less that is unique to each project. Project Code is the same project code from Table 1 above. Respondents must list all projects included in Table 1 that received a project-specific transmission incentive. Projects that only received the RTO-Participation Incentive need only be listed if they are projected to be at least $3 million. It can be identical to the code used by the RTO/ISO if it is unique to the project and is 12 digits or less. This code never changes during the time the project is developed and is never reused for any subsequent project. Respondents should add as many additional rows as are necessary to list all relevant projects. The combination of Report Year and Project Code is the primary key for each record. The primary key allows Table 1 and Table 2 data to be combined into a single table.

(3) Project Description is the same description used in Table 1 associated with the Project Code. Respondents should incorporate the name given by the public utility when requesting incentives into the Project Description, whenever possible. The Project Description never changes. Project Description is a 40-character string. Respondents must create a Project Description, using plain English, that will uniquely identify the project. The same Project Description cannot be used for two different Project Codes and each Project Code has only one Project Description ever.

(4) Project Voltage is the maximum voltage associated with the project. If no voltage could logically be associated the project, then respondents should enter a Project Voltage value of -9. Project Voltage is a numeric value so -9 is a way of indicating that there is no number for this entry.

(5) Respondents should select between the following Project Types to complete the Project Type column: New Build, Upgrade of Existing, Refurbishment/Replacement, or Generator Direct Connection. Project Type is a 40-character string.

(6) Expected Project Completion Date is the date the public utility forecasts as the date that the project will be completed at the end of Report Year. If the project was completed during the report year, then Expected Project Completion Date is the actual project completion date. Project Completion date is formatted mm/yyyy.

(7) Respondents should select between the following designations to complete the Completion Status column: Complete, Under Construction, Pre-Engineering, Planned, Proposed, and Conceptual. If the project is completed between the end of the report year and the day the public utility reports the data, the Completion Status would be Under Construction because that was the project status at the end of the report year. Completion Status is a 20-character string.

(8) Was Project on Schedule? (Y/N) is either Y (yes) or N (no) depending on whether the project was on schedule at the end of the report year. Was Project on Schedule? (Y/N) is a 1-character string.

(9) If the Project Was Not on Schedule, Indicate Reasons for the Delay is a 120-character string. The utility has 120 characters to explain why the project was delayed at the end of the report year. If there was no delay at the end of the report year, then the respondent can just enter N/A.

Below is an example of Table 2 associated with the same fictitious public utility with the same two fictitious projects as used in the example of Table 1.

Table 2: Project Status Details

Report Year	Project Code	Project Name	Project Voltage (kV)	Project Type	Expected Project Completion Date (month/year)	Completion Status	Was Project on Schedule? (Y/N)	If the Project Was Not on Schedule, Indicate Reasons for the Delay
2020 (10)	AKX0303	Piney Ridge to Fulton	230	New Build	06/2024	Under Construction	No	Unable to site original route
2020	AKX0304	Fulton to Grey Pike	230	New Build	09/2023	Pre-Engineering	Yes	N/A

(10) There is no revision for the 2019 AKX0303 Table 2 entry even though the public utility now knows that the route will be delayed because this information was not knowable at the end of the report year. Revisions to data are only to correct information that would have been known to be incorrect at the end of the report year.

Paperwork Reduction Act of 1995 (PRA) Statement: The PRA (44 U.S.C. 3501 et seq.) requires us to inform you the information collected in the Form 730 is necessary for the Commission to evaluate its incentive rates policies, and to demonstrate the effectiveness of these policies. Further, the Form 730 filing requirement allows the Commission to track the progress of electric transmission projects granted incentive-based rates, providing an accurate assessment of the state of the industry with respect to transmission investment, and ensuring that incentive rates are effective in encouraging the development of appropriate transmission infrastructure. Responses are mandatory. An agency may not conduct or sponsor, and a person is not required to respond to a collection of information unless it displays a currently valid OMB Control Number. Public reporting burden for reviewing the instructions, completing, and filling out this form is estimated to be 36 hours per response. Send comments regarding the burden estimate or any other aspect of this form to DataClearance@FERC.gov, or to the Office of the Executive Director, Information Clearance Officer, Federal Energy Regulatory Commission, 888 First Street, NE, Washington, DC 20426.

Title 18, U.S.C. 1001 makes it a crime for any person knowingly and willingly to make to any Agency or Department of the United States any false, fictitious, or fraudulent statements as to any matter within its jurisdiction.