C-UAS Investment Justification Form.docx

Counter-Unmanned Aircraft Systems (C-UAS) Grant Program Investment Justification (IJ) Template Introduction and Instructions Paperwork Burden Disclosure Notice:

Public reporting burden for this data collection is estimated to average 15 hours per response. The burden estimate includes the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and submitting this form. This collection of information is required to obtain or retain benefits. You are not required to respond to this collection of information unless a valid Office of Management and Budget (OMB) control number is displayed on this form. Send comments regarding the accuracy of the burden estimate and any suggestions for reducing the burden to: Information Collections Management, Department of Homeland Security (DHS), Federal Emergency Management Agency (FEMA), 500 C Street, SW., Washington, DC 20472-3100, Paperwork Reduction Project (1660-0125) NOTE: Do not send your completed form to this address.

Privacy Notice:

GENERAL: This information is being collected for the primary purpose of facilitating correspondence between the grant applicant and the DHS and for determining eligibility and administration of the C-UAS Grant Program.

AUTHORITY: Section 2004 of the Homeland Security Act of 2002 (Pub. L. No. 107-296, as amended) (6 U.S.C. § 605).

USES AND SHARING: The information on this form may be disclosed as generally permitted under 5 U.S.C. § 552a(b) of the Privacy Act of 1974, as amended. This includes using this information as necessary and authorized by the routine uses published in DHS/FEMA-004 Non-Disaster Grant Management Information Files System of Records, 87 FR 41141 (July 11, 2022), and upon written request, by agreement, or as required by law. Further information regarding FEMA’s use and sharing of information can be found with the DHS/FEMA/PIA – 013 Grants Management Programs Privacy Impact Assessment. The Department’s list of Privacy Impact Assessments can be found on the Department's website at https://www.dhs.gov/privacy-impact-assessments.

EFFECTS OF NONDISCLOSURE: The disclosure of information on this form is voluntary; however, failure to provide the information requested may delay or prevent the organization from receiving grant funding.

Instructions:

As part of the overall application submission directly to FEMA via email, eligible applicants are required to include at least one IJ as a subapplication. Specific deadlines for submission can be found in the Notice of Funding Opportunity (NOFO). Information on the C-UAS Grant Program goals and objectives is included in Section 3 of the NOFO.

Requirements:

· Application level: This application includes a section for each of the allowable activities listed in the NOFO. Section headers specify each allowable activity. Applicants must complete the section for each funding category for which they are requesting funding. Additionally, each IJ must clearly distinguish between recipient and subrecipient activities.

· For each allowable activity for which the applicant is requesting funding, an IJ must be completed that includes the following sections:

· Project Description: Describe planned activities.

· Capability Gap: Explain how planned activities will address or have addressed gaps in public safety and security.

· Project Objectives: Specify how requested funding will address objectives listed in Appendix B of the NOFO for the relevant allowable activity.

· Subrecipient Impact (if Applicable): Describe how subrecipients will assist in described activities.

· Performance Goals: Specify how requested funding will address performance goals listed in the NOFO for the relevant allowable activity.

· Budget and Timeline: Provide a detailed budget breakdown and timeline for project completion and implementation of costs.

· General Notes for all IJs:

· Subrecipient Coordination: Include details on how subrecipients will be selected, managed, and monitored to ensure alignment with program priorities.

Helpful Hints:

Moving Through the IJ Template: While entering information in the Template, applicants should try to minimize the use of the Tab and Enter keys to move between data entry fields. As the Template consists of a combination of text boxes and cells, using these keys may cause the cursor to move to an undesired location.

Copying & Pasting in the IJ Template: Some applicants may find it helpful to begin drafting their IJ information in Microsoft Word and then pasting this into the Template. However, please be aware that, when copying and pasting information from Word into the text boxes in the Template, any formatting may not carry over.

Character Count: The data entry fields included in the IJ allow for the maximum number of characters noted for that section, plus an additional number of characters to account for spaces. Once that limit has been reached, users will not be able to include any additional text.

Spell Check: It is suggested that applicants use a word processor’s spell check software to ensure that the entered information is spelled correctly.

Self-Certification of Eligibility:

The C-UAS Grant Program will use a discretionary grant allocation method for Fiscal Year (FY) 2026 applications. In order to ensure fair dispersal of funding, applicants must self-certify as to whether they meet the eligibility requirements. Self-certification will be provided in this IJ form below.

Please sign the certification below to ensure accurate allocation of C-UAS Grant Program funds.

A) Certification: I certify that I am an eligible state administrative authority. I have read and will abide by the requirements of the C-UAS Grant Program NOFO.

B) Print signatory name: ______________________________

C) Please sign here: _________________________________

DEPARTMENT OF HOMELAND SECURITY

Federal Emergency Management Agency

This draft Investment Justification Template should be used until the final form is approved by OMB

OMB Control Number: TBD Expiration date: TBD

APPLICANT POINT OF CONTACT (POC) INFORMATION

POC Name:

POC Title:

POC Address:

POC Phone Number:

POC Email Address:

ACTIVITY I: PLANNING

PART I. PROJECT DESCRIPTION

I. Describe the planned activities, services, or equipment purchases that will be funded by the grant. Provide a clear overview of the project’s purpose, scope, and intended outcomes.

PART II. CAPABILITY GAP

II. Explain how the planned activities will address or have addressed gaps in public safety and security. Describe the specific threats, vulnerabilities, or risks posed by UAS in the applicant’s jurisdiction. Highlight current gaps in UAS detection, tracking, or response capabilities.

PART III. PROJECT OBJECTIVES

III. Specify how the requested funding will address the objectives listed in Appendix B of the NOFO for the relevant allowable activity. Describe how the project will enhance public safety, protect critical infrastructure, and mitigate UAS-related threats.

PART IV. SUBRECIPIENT IMPACT

IV. (If applicable) Describe how subrecipients (e.g., local or tribal governments, public safety entities) will assist in the described activities. Explain how subrecipient projects will contribute to achieving the program’s goals.

PART V. PERFORMANCE GOALS

V. Specify how the requested funding will address the performance goals listed in Section 3.E of the NOFO. Identify specific, measurable outcomes that will be used to evaluate the project’s success.

PART VI. BUDGET AND TIMELINE

VI. A. Provide a detailed budget breakdown for project costs, including labor, materials, equipment, and administrative expenses. Include timelines for project completion and implementation, with key milestones clearly identified.

VI. B. Provide a timeline for costs.

The implementation schedule table should be used as a planning tool for the key activities associated with each objective for which the applicant is requesting funding. For each project and each year of the grant, the applicant should include the activities necessary to accomplish the goals of each project, as well as the estimated start and completion dates (by calendar quarter) for each activity.

The standard definition of a project is a temporary endeavor with a defined beginning and end (usually time-constrained, and often constrained by funding or a deliverable), undertaken to meet unique goals and objectives, typically to bring about beneficial change or added value. Applying this standard to projects using preparedness grant funds, a project is a related set of activities and purchases supporting the building or sustaining of core capabilities; and it is associated with a single entity responsible for execution.

This approach will allow FEMA and applicants to categorize the grant-funded project as a discrete unit for post-award management, reporting, and monitoring purposes. The main steps and processes of the Project Management Lifecycle are Initiate, Execute, Control, Close Out.

a. Initiate: The authorization to begin work or resume work on any particular activity.

b. Execute: The period within the project life cycle during which the actual work of creating the project’s deliverables is carried out.

c. Control: A mechanism which reacts to the current project status to ensure accomplishment of project objectives. This involves planning, measuring, monitoring, and taking corrective action based on the results of the monitoring.

d. Close Out: The completion of all work on a project. Can also refer to completion of a phase of the project.

For additional information on the Project Management Lifecycle, please visit Project Management Institute's (PMI) A Guide to the Project Management Body of Knowledge (PMBOK Guide) at http://www.pmi.org/PMBOK-Guide-and-Standards.aspx. Specifically, applicants are encouraged to reference Chapter three of the PMBOK Guide, The Standard for Project Management of a Project.

Appendix A: Identify projects/activities, with start and end dates, which will be implemented during the period of performance

ACTIVITY II: ORGANIZATION

PART I. PROJECT DESCRIPTION

I. Describe the planned activities, services, or equipment purchases that will be funded by the grant. Provide a clear overview of the project’s purpose, scope, and intended outcomes.

PART II. CAPABILITY GAP

II. Explain how the planned activities will address or have addressed gaps in public safety and security. Describe the specific threats, vulnerabilities, or risks posed by UAS in the applicant’s jurisdiction. Highlight current gaps in UAS detection, tracking, or response capabilities.

PART III. PROJECT OBJECTIVES

III. Specify how the requested funding will address the objectives listed in Appendix B of the NOFO for the relevant allowable activity. Describe how the project will enhance public safety, protect critical infrastructure, and mitigate UAS-related threats.

PART IV. SUBRECIPIENT IMPACT

IV. (If applicable) Describe how subrecipients (e.g., local or tribal governments, public safety entities) will assist in the described activities. Explain how subrecipient projects will contribute to achieving the program’s goals.

PART V. PERFORMANCE GOALS

V. Specify how the requested funding will address the performance goals listed in Section 3.E of the NOFO. Identify specific, measurable outcomes that will be used to evaluate the project’s success.

PART VI. BUDGET AND TIMELINE

VI. A. Provide a detailed budget breakdown for project costs, including labor, materials, equipment, and administrative expenses. Include timelines for project completion and implementation, with key milestones clearly identified.

VI. B. Provide a timeline for costs.

The implementation schedule table should be used as a planning tool for the key activities associated with each objective for which the applicant is requesting funding. For each project and each year of the grant, the applicant should include the activities necessary to accomplish the goals of each project, as well as the estimated start and completion dates (by calendar quarter) for each activity.

The standard definition of a project is a temporary endeavor with a defined beginning and end (usually time-constrained, and often constrained by funding or a deliverable), undertaken to meet unique goals and objectives, typically to bring about beneficial change or added value. Applying this standard to projects using preparedness grant funds, a project is a related set of activities and purchases supporting the building or sustaining of core capabilities; and it is associated with a single entity responsible for execution.

This approach will allow FEMA and applicants to categorize the grant-funded project as a discrete unit for post-award management, reporting, and monitoring purposes. The main steps and processes of the Project Management Lifecycle are Initiate, Execute, Control, Close Out.

a. Initiate: The authorization to begin work or resume work on any particular activity.

b. Execute: The period within the project life cycle during which the actual work of creating the project’s deliverables is carried out.

c. Control: A mechanism which reacts to the current project status to ensure accomplishment of project objectives. This involves planning, measuring, monitoring, and taking corrective action based on the results of the monitoring.

d. Close Out: The completion of all work on a project. Can also refer to completion of a phase of the project.

For additional information on the Project Management Lifecycle, please visit Project Management Institute's (PMI) A Guide to the Project Management Body of Knowledge (PMBOK Guide) at http://www.pmi.org/PMBOK-Guide-and-Standards.aspx. Specifically, applicants are encouraged to reference Chapter three of the PMBOK Guide, The Standard for Project Management of a Project.

Appendix A: Identify projects/activities, with start and end dates, which will be implemented during the period of performance

PART IV. SUBRECIPIENT IMPACT

ACTIVITY III: EQUIPMENT

PART I. PROJECT DESCRIPTION

I. Describe the planned activities, services, or equipment purchases that will be funded by the grant. Provide a clear overview of the project’s purpose, scope, and intended outcomes.

PART II. CAPABILITY GAP

II. Explain how the planned activities will address or have addressed gaps in public safety and security. Describe the specific threats, vulnerabilities, or risks posed by UAS in the applicant’s jurisdiction. Highlight current gaps in UAS detection, tracking, or response capabilities.

PART III. PROJECT OBJECTIVES

III. Specify how the requested funding will address the objectives listed in Appendix B of the NOFO for the relevant allowable activity. Describe how the project will enhance public safety, protect critical infrastructure, and mitigate UAS-related threats.

PART IV. SUBRECIPIENT IMPACT

IV. (If applicable) Describe how subrecipients (e.g., local or tribal governments, public safety entities) will assist in the described activities. Explain how subrecipient projects will contribute to achieving the program’s goals.

PART V. PERFORMANCE GOALS

V. Specify how the requested funding will address the performance goals listed in Section 3.E of the NOFO. Identify specific, measurable outcomes that will be used to evaluate the project’s success.

PART VI. BUDGET AND TIMELINE

VI. A. Provide a detailed budget breakdown for project costs, including labor, materials, equipment, and administrative expenses. Include timelines for project completion and implementation, with key milestones clearly identified.

VI. B. Provide a timeline for costs.

The implementation schedule table should be used as a planning tool for the key activities associated with each objective for which the applicant is requesting funding. For each project and each year of the grant, the applicant should include the activities necessary to accomplish the goals of each project, as well as the estimated start and completion dates (by calendar quarter) for each activity.

The standard definition of a project is a temporary endeavor with a defined beginning and end (usually time-constrained, and often constrained by funding or a deliverable), undertaken to meet unique goals and objectives, typically to bring about beneficial change or added value. Applying this standard to projects using preparedness grant funds, a project is a related set of activities and purchases supporting the building or sustaining of core capabilities; and it is associated with a single entity responsible for execution.

This approach will allow FEMA and applicants to categorize the grant-funded project as a discrete unit for post-award management, reporting, and monitoring purposes. The main steps and processes of the Project Management Lifecycle are Initiate, Execute, Control, Close Out.

a. Initiate: The authorization to begin work or resume work on any particular activity.

b. Execute: The period within the project life cycle during which the actual work of creating the project’s deliverables is carried out.

c. Control: A mechanism which reacts to the current project status to ensure accomplishment of project objectives. This involves planning, measuring, monitoring, and taking corrective action based on the results of the monitoring.

d. Close Out: The completion of all work on a project. Can also refer to completion of a phase of the project.

For additional information on the Project Management Lifecycle, please visit Project Management Institute's (PMI) A Guide to the Project Management Body of Knowledge (PMBOK Guide) at http://www.pmi.org/PMBOK-Guide-and-Standards.aspx. Specifically, applicants are encouraged to reference Chapter three of the PMBOK Guide, The Standard for Project Management of a Project.

Appendix A: Identify projects/activities, with start and end dates, which will be implemented during the period of performance

ACTIVITY IV: TRAINING

PART I. PROJECT DESCRIPTION

I. Describe the planned activities, services, or equipment purchases that will be funded by the grant. Provide a clear overview of the project’s purpose, scope, and intended outcomes.

PART II. CAPABILITY GAP

II. Explain how the planned activities will address or have addressed gaps in public safety and security. Describe the specific threats, vulnerabilities, or risks posed by UAS in the applicant’s jurisdiction. Highlight current gaps in UAS detection, tracking, or response capabilities.

PART III. PROJECT OBJECTIVES

III. Specify how the requested funding will address the objectives listed in Appendix B of the NOFO. Describe how the project will enhance public safety, protect critical infrastructure, and mitigate UAS-related threats.

PART IV. SUBRECIPIENT IMPACT

IV. (If applicable) Describe how subrecipients (e.g., local or tribal governments, public safety entities) will assist in the described activities. Explain how subrecipient projects will contribute to achieving the program’s goals.

V. PERFORMANCE GOALS

V. Specify how the requested funding will address the performance goals listed in Section 3.E of the NOFO for the relevant allowable activity. Identify specific, measurable outcomes that will be used to evaluate the project’s success.

PART VI. BUDGET AND TIMELINE

VI. A. Provide a detailed budget breakdown for project costs, including labor, materials, equipment, and administrative expenses. Include timelines for project completion and implementation, with key milestones clearly identified.

VI. B. Provide a timeline for costs.

The implementation schedule table should be used as a planning tool for the key activities associated with each objective for which the applicant is requesting funding. For each project and each year of the grant, the applicant should include the activities necessary to accomplish the goals of each project, as well as the estimated start and completion dates (by calendar quarter) for each activity.

The standard definition of a project is a temporary endeavor with a defined beginning and end (usually time-constrained, and often constrained by funding or a deliverable), undertaken to meet unique goals and objectives, typically to bring about beneficial change or added value. Applying this standard to projects using preparedness grant funds, a project is a related set of activities and purchases supporting the building or sustaining of core capabilities; and it is associated with a single entity responsible for execution.

This approach will allow FEMA and applicants to categorize the grant-funded project as a discrete unit for post-award management, reporting, and monitoring purposes. The main steps and processes of the Project Management Lifecycle are Initiate, Execute, Control, Close Out.

a. Initiate: The authorization to begin work or resume work on any particular activity.

b. Execute: The period within the project life cycle during which the actual work of creating the project’s deliverables is carried out.

c. Control: A mechanism which reacts to the current project status to ensure accomplishment of project objectives. This involves planning, measuring, monitoring, and taking corrective action based on the results of the monitoring.

d. Close Out: The completion of all work on a project. Can also refer to completion of a phase of the project.

For additional information on the Project Management Lifecycle, please visit Project Management Institute's (PMI) A Guide to the Project Management Body of Knowledge (PMBOK Guide) at http://www.pmi.org/PMBOK-Guide-and-Standards.aspx. Specifically, applicants are encouraged to reference Chapter three of the PMBOK Guide, The Standard for Project Management of a Project.

Appendix A: Identify projects/activities, with start and end dates, which will be implemented during the period of performance

ACTIVITY V: EXERCISES

PART I. PROJECT DESCRIPTION

I. Describe the planned activities, services, or equipment purchases that will be funded by the grant. Provide a clear overview of the project’s purpose, scope, and intended outcomes.

PART II. CAPABILITY GAP

II. Explain how the planned activities will address or have addressed gaps in public safety and security. Describe the specific threats, vulnerabilities, or risks posed by UAS in the applicant’s jurisdiction. Highlight current gaps in UAS detection, tracking, or response capabilities.

PART III. PROJECT OBJECTIVES

III. Specify how the requested funding will address the objectives listed in Appendix B of the NOFO for the relevant allowable activity. Describe how the project will enhance public safety, protect critical infrastructure, and mitigate UAS-related threats.

PART IV. SUBRECIPIENT IMPACT

IV. (If applicable) Describe how subrecipients (e.g., local or tribal governments, public safety entities) will assist in the described activities. Explain how subrecipient projects will contribute to achieving the program’s goals.

V. PERFORMANCE GOALS

V. Specify how the requested funding will address the performance goals listed in Section 3.E of the NOFO. Identify specific, measurable outcomes that will be used to evaluate the project’s success.

PART VI. BUDGET AND TIMELINE

VI. A. Provide a detailed budget breakdown for project costs, including labor, materials, equipment, and administrative expenses. Include timelines for project completion and implementation, with key milestones clearly identified.

VI. B. Provide a timeline for costs.

The implementation schedule table should be used as a planning tool for the key activities associated with each objective for which the applicant is requesting funding. For each project and each year of the grant, the applicant should include the activities necessary to accomplish the goals of each project, as well as the estimated start and completion dates (by calendar quarter) for each activity.

The standard definition of a project is a temporary endeavor with a defined beginning and end (usually time-constrained, and often constrained by funding or a deliverable), undertaken to meet unique goals and objectives, typically to bring about beneficial change or added value. Applying this standard to projects using preparedness grant funds, a project is a related set of activities and purchases supporting the building or sustaining of core capabilities; and it is associated with a single entity responsible for execution.

This approach will allow FEMA and applicants to categorize the grant-funded project as a discrete unit for post-award management, reporting, and monitoring purposes. The main steps and processes of the Project Management Lifecycle are Initiate, Execute, Control, Close Out.

a. Initiate: The authorization to begin work or resume work on any particular activity.

b. Execute: The period within the project life cycle during which the actual work of creating the project’s deliverables is carried out.

c. Control: A mechanism which reacts to the current project status to ensure accomplishment of project objectives. This involves planning, measuring, monitoring, and taking corrective action based on the results of the monitoring.

d. Close Out: The completion of all work on a project. Can also refer to completion of a phase of the project.

For additional information on the Project Management Lifecycle, please visit Project Management Institute's (PMI) A Guide to the Project Management Body of Knowledge (PMBOK Guide) at http://www.pmi.org/PMBOK-Guide-and-Standards.aspx. Specifically, applicants are encouraged to reference Chapter three of the PMBOK Guide, The Standard for Project Management of a Project.

Appendix A: Identify projects/activities, with start and end dates, which will be implemented during the period of performance

FEMA FORM XXX (MM/YY) Page 2 of 2