Corridor Program Name: Date of Submission: Version Number:
H igh-Speed Intercity Passenger Rail (HSIPR) Program
Track 2–Corridor Programs:
Application Form
Welcome to the Application Form for Track 2–Corridor Programs of the Federal Railroad Administration’s High-Speed Intercity Passenger Rail (HSIPR) Program.
This form will provide information on a cohesive set of projectsrepresenting a phase, geographic segment, or other logical groupingthat furthers a particular corridor service.
Definition: For purposes of this application, a “Corridor Program” is “a group of projects that collectively advance the entirety, or a ‘phase’ or ‘geographic section,’ of a corridor service development plan.” (Guidance, 74 Fed, Reg. 29904, footnote 4). A Corridor Program must have independent utility and measurable public benefits.
In addition to this application form and required supporting materials, applicants are required to submit a Corridor Service Overview.
An applicant may choose to represent its vision for the entire, fully-developed corridor service in one application or in multiple applications, provided that the set of improvements contained in each application submitted has independent utility and measurable public benefits. The same Service Development Plan may be submitted for multiple Track 2 Applications. Each Track 2 application will be evaluated independently with respect to related applications. Furthermore, FRA will make its evaluations and selections for Track 2 funding based on an entire application rather than on its component projects considered individually.
We appreciate your interest in the HSIPR Program and look forward to reviewing your entire application. If you have questions about the HSIPR program or the Application Form and Supporting Materials for Track 2, please contact us at [email protected].
Instructions for the Track 2 Application Form:
Please complete the HSIPR Application electronically. See Section G of this document for a complete list of the required application materials.
In the space provided at the top of each section, please indicate the Corridor Program name, date of submission (mm/dd/yyyy), and an application version number assigned by the applicant. The Corridor Program name must be identical to the name listed in the Corridor Service Overview Master List of Related Applications. Consisting of less than 40 characters, the Corridor Program name must consist of the following elements, each separated by a hyphen: (1) the State abbreviation of the State submitting this application; (2) the route or corridor name that is the subject of the related Corridor Service Overview; and (3) a descriptor that will concisely identify the Corridor Program’s focus (e.g., HI-Fast Corridor-Main Stem).
Section B, Question 10 requires a distinct name for each project under this Corridor Program. Please the following the naming convention: (1) the State abbreviation; (2) the route or corridor name that forms part of the Corridor Program name; and (3) a project descriptor that will concisely identify the project’s focus (e.g., HI-Fast Corridor-Wide River Bridge). For projects previously submitted under another application, please use the same name previously used on the project application.
For each question, enter the appropriate information in the designated gray box. If a question is not applicable to your Track 2 Corridor Program, please indicate “N/A.”
Narrative questions should be answered within the limitations indicated.
Applicants must up load this completed and all other application materials to www.GrantSolutions.gov by October 2, 2009 at 11:59 pm EDT.
Fiscal Year (FY) refers to the Federal Government’s fiscal year (Oct. 1- Sept. 30).
Corridor Program Name: Date of Submission: Version Number:
Point of Contact and Application Information
|
POC Title:
|
|||
Applicant State Agency or Organization Name:
|
||||
Street Address:
|
City:
|
State:
|
Zip Code:
|
Telephone Number:
|
Email: |
Fax: |
Corridor Program Name: Date of Submission: Version Number:
B. Corridor Program Summary
Corridor Program Name:
|
|
||||||||||||||||||
Start Date: End Date:
|
|
||||||||||||||||||
Of the total cost above,, how much would come from the FRA HSIPR Program: (YOE Dollars**) $
Indicate percentage of total cost to be covered by matching funds: %
Please indicate the source(s) for matching funds:
* Year-of-Expenditure (YOE) dollars are inflated from the base year. Applicants should include their proposed inflation assumptions (and methodology, if applicable) in the supporting documentation. ** This is the amount for which the Applicant is applying. |
|
||||||||||||||||||
Describe the main features and characteristics of the Corridor Program, including a description of:
|
|
||||||||||||||||||
|
|
||||||||||||||||||
Additional Service Frequencies Improved Service Quality Improved On-Time performance on Existing Route Reroute Existing Service
|
Increased Average Speeds/Shorter Trip Times New Service on Existing IPR Route New Service on New Route Other (Please Describe):
|
|
|||||||||||||||||
|
|
||||||||||||||||||
Type of Railroad |
Railroad Right-of-Way Owner |
Route Miles |
Track Miles |
Status of agreements to implement projects |
|
||||||||||||||
|
|
|
|
|
|
||||||||||||||
|
|
|
|
|
|
||||||||||||||
|
|
|
|
|
|
||||||||||||||
|
|
||||||||||||||||||
Type of Service |
Name of Operator |
Top Speed Within Boundaries |
Number of Route Miles Within Boundaries |
Average Number of Daily One-Way Train Operations within Boundaries1 |
Notes |
|
|||||||||||||
Passenger |
Freight |
|
|||||||||||||||||
|
|
|
|
|
|
|
|
||||||||||||
|
|
|
|
|
|
|
|
||||||||||||
|
|
|
|
|
|
|
|
||||||||||||
|
|
||||||||||||||||||
Name of Operating Partner:
Status of Agreement:
|
|
||||||||||||||||||
|
|
||||||||||||||||||
Project Name |
Project Type |
Project Description |
Project Start Date (mm/yyyy) |
Estimated
Project Cost |
Was this Project included in a prior HSIPR application? Indicate track number(s). |
Are more detailed project costs included in the Supporting Forms? |
|
||||||||||||
Total Cost |
Amount Applied For |
|
|||||||||||||||||
|
|
|
|
|
|
|
|
|
|||||||||||
|
|
|
|
|
|
|
|
|
|||||||||||
|
|
|
|
|
|
|
|
|
|||||||||||
|
|
|
|
|
|
|
|
|
|||||||||||
|
|
|
|
|
|
|
|
|
|||||||||||
|
|
|
|
|
|
|
|
|
|||||||||||
|
|
|
|
|
|
|
|
|
|||||||||||
|
|
|
|
|
|
|
|
|
|||||||||||
|
|
|
|
|
|
|
|
|
|||||||||||
|
|
|
|
|
|
|
|
|
|||||||||||
|
|
|
|
|
|
|
|
|
|||||||||||
|
|
|
|
|
|
|
|
|
|||||||||||
|
|
|
|
|
|
|
|
|
|||||||||||
|
|
|
|
|
|
|
|
|
|||||||||||
|
|
|
|
|
|
|
|
|
|||||||||||
|
|
|
|
|
|
|
|
|
|||||||||||
|
|
|
|
|
|
|
|
|
|||||||||||
|
|
|
|
|
|
|
|
|
|||||||||||
|
|
|
|
|
|
|
|
|
|||||||||||
|
|
|
|
|
|
|
|
|
|||||||||||
|
|
|
|
|
|
|
|
|
|||||||||||
|
|
|
|
|
|
|
|
|
|||||||||||
Note: In addition to program level supporting documentation, all applicable project level supporting documentation is required prior to award. If project level documentation is available now, you may submit it; however, if it is not provided in this application, this project may be considered as a part of a possible Letter of Intent but will not be considered for FD/Construction grant award until this documentation has been submitted.
|
|||||||||||||||||||
In narrative form, please describe the sequencing of the projects listed in Question 10. Which activities must be pursued sequentially, which can be done at any time, and which can be done simultaneously? Please limit response to 4,000 characters.
|
Corridor Program Name: Date of Submission: Version Number:
Eligibility Information
State Amtrak
If one of the following, please append appropriate documentation as described in Section 4.3.1 of the HSIPR Guidance: Group of States Interstate Compact Public Agency established by one or more States Amtrak in cooperation with a State or States
|
|||||||
Please provide information on the status of the below Service and Implementation Planning Activities: |
|||||||
|
Select One of the Following: |
Provide Dates for all activities: |
|||||
|
No study exists |
Study Initiated |
Study Completed |
Start Date (mm/yyyy) |
Actual or Anticipated Completion Date (mm/yyyy) |
||
Service Planning Activities/Documents |
|||||||
Purpose & Need/Rationale |
|
|
|
|
|
||
Service/Operating Plan |
|
|
|
|
|
||
Prioritized Capital Plan |
|
|
|
|
|
||
Ridership/Revenue Forecast |
|
|
|
|
|
||
Operating Cost Forecast |
|
|
|
|
|
||
Assessment of Benefits |
|
|
|
|
|
||
Implementation Planning Activities/Documents |
|||||||
Program Management Plan |
|
|
|
|
|
||
Financial Plan (capital & operating – sources/uses) |
|
|
|
|
|
||
Assessment of Risks |
|
|
|
|
|
||
Note to applicants: Prior to obligation of funds for FD/Construction activities under Track 2, all project specific documents will be required (e.g. Project NEPA, Financial Plan, and Project Management Plan).
|
|||||||
Documentation |
Date (mm/yyyy) |
Describe How Documentation Can be Verified |
|||||
|
|
|
|||||
|
|
|
|||||
|
|
|
|||||
|
|||||||
Documentation |
Date (mm/yyyy) |
Hyperlink (if available) |
|||||
|
|
|
|||||
|
|
|
|||||
|
|
|
Corridor Program Name: Date of Submission: Version Number:
Public Return on Investment
How is the Corridor Program anticipated to improve Intercity Passenger Rail (IPR) service? Describe the overall transportation benefits, including information on the following (please provide a level of detail appropriate to the type of investment):
|
|||||
1B. Operational and Ridership Benefits Metrics: In the table(s) below, provide information on the anticipated levels of transportation benefits and ridership that are projected to occur in the corridor service or route, following completion of the proposed Corridor Program. Note: The “ActualFY 2008 levels” only apply to rail services that currently exist. If no comparable rail service exists, leave column blank. |
|||||
Corridor Program Metric |
Actual – FY 2008 levels |
Projected Totals by Year |
|
||
First full year of operation |
Fifth full year of operation |
Tenth full year of operation |
|
||
Annual passenger-trips |
|
|
|
|
|
Annual passenger-miles (millions) |
|
|
|
|
|
Annual IPR seat-miles offered (millions) |
|
|
|
|
|
Average number of daily round trip train operations (typical weekday) |
|
|
|
|
|
On-time performance (OTP)2– percent of trains on time at endpoint terminals |
|
|
|
|
|
Average train operating delays: minutes of en-route delays per 10,000 train-miles3 |
|
|
|
|
|
Top passenger train operating speed (mph) |
|
|
|
|
|
Average scheduled operating speed (mph) (between endpoint terminals) |
|
|
|
|
|
Describe the contribution the Corridor Program is intended to make towards economic recovery and reinvestment, including information on the following:
|
||||
2B. Job Creation. Provide the following information about job creation through the life of the Corridor Program. Please consider construction, maintenance and operations jobs. |
||||
Anticipated number of onsite and other direct jobs created (on a 2080 work-hour per year, full-time equivalent basis).
|
FD/ Construction Period |
First full year of operation |
Fifth full year of operation |
Tenth full year of operation |
|
|
|
|
|
How will the Corridor Program improve environmental quality, energy efficiency, and reduce in the Nation’s dependence on oil? Address the following:
|
||||
How will the Corridor Program foster Livable Communities? Address the following:
|
Corridor Program Name: Date of Submission: Version Number:
Application Success Factors
1A. Applicant qualifications. Management experience: Does the applicant have experience in managing rail investments and Corridor Programs of a similar size and scope to the one proposed in this application?
Yes - Briefly describe experience (brief project(s) overview, dates) No- Briefly describe expected plan to build technical and managerial capacity. Provide reference to Project Management Plan. Please limit response to 3,000 characters.
1B. Describe the organizational approach for the different Corridor Program stages included in this application (e.g., final design, construction), including the roles of staff, contractors and stakeholders in implementing the Corridor Program. For construction activities, provide relevant information on work forces, including railroad contractors and grantee contractors. Please limit response to 3,000 characters.
1C. Does any part of the Corridor Program require approval by FRA of a waiver petition from a Federal railroad safety regulation? (Reference to or discussion of potential waiver petitions will not affect FRA’s handling or disposition of such waiver petitions).
YES- If yes, explain and provide a timeline for obtaining the waivers NO Please limit response to 1,500 characters.
1D. Provide a preliminary self-assessment of Corridor Program uncertainties and mitigation strategies (consider funding risk, schedule risk and stakeholder risk). Describe any areas in which the applicant could use technical assistance, best practices, advice or support from others, including FRA. Please limit response to 2,000 characters.
|
|||||||||||
Under each of the following categories, describe the applicant’s progress in developing requisite agreements with key stakeholders. In addition to describing the current status of any such agreements, address the applicant’s experience in framing and implementing similar agreements, as well as the specific topics pertaining to each category.
2A. Ownership Agreements – Describe how agreements will be finalized with railroad infrastructure owners listed in the “Right-of-Way Ownership” and “Service Description” tables in Section B. If appropriate, “owner(s)” may also include operator(s) under trackage rights or lease agreements. Describe how the parties will agree on Corridor Program design and scope, benefits, implementation, use of Corridor Program property, maintenance, scheduling, dispatching and operating slots, Corridor Program ownership and disposition, statutory conditions and other essential topics. Summarize the status and substance of any ongoing or completed agreements. Please limit response to 3,000 characters.
2B. Operating Agreements – Describe the status and contents of agreements with the intended operator(s) listed in “Services” table in the Application Overview section above. Address Corridor Program benefits, operation and financial conditions, statutory conditions, and other relevant topics. Please limit response to 3,000 characters.
2C. Selection of Operator – If the proposed operator railroad was not selected competitively, please provide a justification for its selection, including why the selected operator is most qualified, taking into account cost and other quantitative and qualitative factors, and why the selection of the proposed operator will not needlessly increase the cost of the Corridor Program or of the operations that it enables or improves. Please limit response to 3,000 characters.
2D. Other Stakeholder Agreements – Provide relevant information on other stakeholder agreements including State and local governments. Please limit response to 3,000 characters.
2E. Agreements with operators of other types of rail service - Are benefits to non-intercity passenger rail services (e.g., commuter, freight) foreseen? Describe any cost sharing agreements with operators of non-intercity passenger rail service (e.g., commuter, freight). Please limit response to 3,000 characters.
|
|||||||||||
3A. Capital Funding Sources. Please provide the following information about your funding sources (if applicable). |
|||||||||||
Non FRA Funding Sources
|
New or Existing Funding Source? |
Status of Funding4 |
Type of Funds |
Dollar Amount (millions of $ YOE) |
% of Program Cost |
Describe uploaded supporting documentation to help FRA verify funding source |
|||||
|
|
|
|
|
|
|
|||||
|
|
|
|
|
|
|
|||||
|
|
|
|
|
|
|
|||||
|
|
|
|
|
|
|
|||||
3B. Capital Investment Financial Agreements. Describe any cost sharing contribution the applicant intends to make towards the Corridor Program, including its source, level of commitment, and agreement to cover cost increases or financial shortfalls. Describe the status and nature of any agreements between funding stakeholders that would provide for the applicant’s proposed match, including the responsibilities and guarantees undertaken by the parties. Provide a brief description of any in-kind matches that are expected. Please limit response to 3,000 characters.
|
|||||||||||
3C. Corridor Program Sustainability and Operating Financial Plan. Please report on the Applicant’s projections of future financial requirements to sustain the service by completing the table below (in YOE dollars) and answering the following question. Describe the source, nature, share, and likelihood of each identified funding source that will enable the State to satisfy its projected financial support requirements to sustain the operation of the service addressed in this Corridor Program. Please limit response to 2,000 characters.
Note: Please enter supporting projections in the Track 2 Application Supporting Forms, and submit related funding agreements or other documents with the Supporting Materials described in Part G of this Track 2 Application. The numbers entered in this table must agree with analogous numbers in the Supporting Forms.
|
|||||||||||
Funding Requirement (as identified on the Supporting Form) |
|
Projected Totals by Year ($ Millions Year Of Expenditure (YOE)* Dollars - One Decimal) |
|||||||||
Baseline Actual-FY 2009 Levels (State operating subsidy for FY 2009 if existing service) |
First full year of operation |
Fifth full year of operation |
Tenth full year of operation |
||||||||
Indicate the Fiscal Year |
2009 |
|
|
|
|||||||
Surplus/deficit after capital asset renewal charge5
|
|
|
|
|
|||||||
Total Non-FRA sources of funds applicable to the surplus/deficit after capital asset renewal
|
|
|
|
|
|||||||
Funding Requirements for which Available Funds Are Not Identified
|
|
|
|
|
|||||||
* Year-of-Expenditure (YOE) dollars are inflated from the base year. Applicants should include their proposed inflation assumptions (and methodology, if applicable) in the supporting documentation. Note: Data reported in this section should be consistent with the information provided in the Operating and Financial Performance supporting form for this application. |
|||||||||||
|
|||||||||||
|
|||||||||||
Final Design Duration: |
months |
||||||||||
Construction Duration: |
months |
||||||||||
Rolling Stock Acquisition/Refurbishment Duration: |
months |
||||||||||
Service Operations Start date: |
(mm/yyyy) |
||||||||||
|
|||||||||||
|
Corridor Program Name: Date of Submission: Version Number:
Additional Information
|
Corridor Program Name: Date of Submission: Version Number:
Summary of Application Materials
Note: In addition to the requirements listed below, applicants must comply with all requirements set forth in the HSIPR Guidance and all applicable Federal laws and regulations, including the American Recovery and Reinvestment Act of 2009 (ARRA) and the Passenger Rail Investment and Improvement Act of 2008 (PRIIA).
Application Forms |
Required for Corridor Programs |
Required for Projects
|
Reference |
Comments |
This Application Form |
|
|
HSIPR Guidance Section 4.3.3.3 |
|
Corridor Service Overview (Same Corridor Service Overview may be used for multiple applications) |
|
|
HSIPR Guidance Section 4.3.3.3 |
|
Supporting Forms (Forms are provided by FRA on Grant Solutions and the FRA website) |
Required for Corridor Programs |
Required for Projects
|
Reference |
Comments |
General Info |
|
|
HSIPR Guidance Section 4.3.5 |
FRA Excel Form |
Detailed Capital Cost Budget |
|
|
HSIPR Guidance Section 4.3.5 |
FRA Excel Form |
Annual Capital Cost Budget |
|
|
HSIPR Guidance Section 4.3.5 |
FRA Excel Form |
Operating and Financial Performance and Any Related Financial Forms |
|
|
HSIPR Guidance Section 5.3.5 |
FRA Excel Form |
Program or Project Schedule |
|
|
HSIPR Guidance Section 4.3.5 |
FRA Excel Form |
Supporting Documents (Documents to be generated and provided by the applicant) |
Required for Corridor Programs |
Required for Projects
|
Reference |
Comments |
Map of Corridor Service |
|
|
Corridor Service Overview Question B.2 |
|
Service Development Plan |
|
|
HSIPR Guidance Section 1.6.2eference |
|
“Service” NEPA |
|
|
HSIPR Guidance Section 1.6.2ference |
|
Project Management Plan |
|
|
HSIPR Guidance Section 4.3.3.2ference |
|
“Project” NEPA (Required before obligation of funds) |
|
|
HSIPR Guidance Section 1.6.2ference |
|
PE Materials |
|
|
HSIPR Guidance Section 1.6.2ference |
|
Stakeholder Agreements |
|
|
HSIPR Guidance Section 4.3.3.2ference |
|
Financial Plan |
|
|
HSIPR Guidance Section 4.3.3.2ference |
|
Job Creation |
|
|
HSIPR Guidance Section 1.6.2ference |
|
Standard Forms (Can be found on the FRA website and www.forms.gov) |
Required for Corridor Programs |
Required for Projects
|
Reference |
Comments |
SF 424: Application for Federal Assistance
|
|
|
HSIPR Guidance Section 4.3.3.3eference |
Form |
SF 424C: Budget Information- Construction
|
|
|
HSIPR Guidance Section 4.3.3.3 |
Form |
SF 424D: Assurances-Construction
|
|
|
HSIPR Guidance Section 4.3.3.3 |
Form |
FRA Assurances Document
|
|
|
HSIPR Guidance Section 4.3.3.3 |
Form |
Note: Items checked under “Corridor Programs” are required at the time of submission of this Track 2 Corridor Programs application. Items checked under “Projects” are optional at the time of submission of this Track 2 Corridor Programs application, but required prior to FD/Construction grant award. |
PRA Public Protection Statement: Public reporting burden for this information collection is estimated to average 16 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. According to the Paperwork Reduction Act of 1995, a federal agency may not conduct or sponsor, and a person is not required to respond to, nor shall a person be subject to a penalty for failure to comply with, a collection of information unless it displays a currently valid OMB control number. The valid OMB control number for this information collection is 2130-0583.
1 One round trip equals two one-way train operations.
2 ‘On-time’ is defined as within the distance-based thresholds originally issued by the Interstate Commerce Commission, which are: 0 to 250 miles and all Acela trains10 minutes; 251 to 350 miles15 minutes; 351 to 450 miles20 minutes; 451 to 550 miles25 minutes; and 551 or more miles30 minutes.
3 As calculated by Amtrak according to its existing procedures and definitions. Useful background (but not the exact measure cited on a route-by-route basis) can be found at pages E-1 through E-6 of Amtrak’s May 2009 Monthly Performance Report at http://www.amtrak.com/pdf/0905monthly.pdf
4 Reference Notes: The following categories and definitions are applied to funding sources:
Committed: Committed sources are programmed capital funds that have all the necessary approvals (e.g. legislative referendum) to be used to fund the proposed phase without any additional action. These capital funds have been formally programmed in the State Rail Plan and/or any related local, regional, or State Capital Investment Program CIP or appropriation. Examples include dedicated or approved tax revenues, State capital grants that have been approved by all required legislative bodies, cash reserves that have been dedicated to the proposed phase, and additional debt capacity that requires no further approvals and has been dedicated by the sponsoring agency to the proposed phase.
Budgeted: This category is for funds that have been budgeted and/or programmed for use on the proposed phase but remain uncommitted, i.e., the funds have not yet received statutory approval. Examples include debt financing in an agency-adopted CIP that has yet to be committed in their near future. Funds will be classified as budgeted where available funding cannot be committed until the grant is executed, or due to the local practices outside of the phase sponsor's control (e.g., the phase development schedule extends beyond the State Rail Program period).
Planned: This category is for funds that are identified and have a reasonable chance of being committed, but are neither committed nor budgeted. Examples include proposed sources that require a scheduled referendum, requests for State/local capital grants, and proposed debt financing that has not yet been adopted in the agency's CIP.
5 The “capital asset renewal charge” is an annualized provision for future asset replacement, refurbishment, and expansion. It is the annualized equivalent to the “continuing investments” defined in the FRA’s Commercial Feasibility Study of high-speed ground transportation (High-Speed Ground Transportation for America, September 1997, available at http://www.fra.dot.gov/us/content/515 (see pages 5-6 and 5-7).
Page
Form FRA F 6180.134a (07-09)
File Type | application/msword |
File Title | High Speed Intercity Passenger Rail (HSIPR) Program |
Author | Grossman, Sarah Meegan |
Last Modified By | frauser1 |
File Modified | 2009-11-03 |
File Created | 2009-11-03 |