Transit Security Grant Program Eligibility: A Project-Fit Guide for Existing Cameras
A security team has identified a promising use for cameras already watching a transit facility. Before pricing or application work begins, test five gates: Is a TSGP cycle open? Is the agency named as eligible? Does the security record support the need? Does the project address terrorism-related transit risk? Are its costs allowable? A project can pass four gates and still fail the fifth.
Is your organization eligible for the Transit Security Grant Program?
For FY 2026, an organization was eligible only if its passenger rail, intra-city bus, or ferry system appeared in Appendix 1 of FEMA's official notice, and appearing there did not guarantee funding. A public-transit mission, government status, or location in a large urban area was not a substitute for being named. The application deadline was July 24, 2026, so that cycle is closed as of September 19, 2026. Use that notice as a planning reference, then recheck the next notice before acting.
Closed-cycle notice
Status as of September 19, 2026: FY 2026 TSGP applications are closed. This guide does not imply that a later cycle is open, that the same agencies will remain eligible, or that the next notice will preserve the same project and cost rules.
- Confirm that the current notice is open. Do not reuse an old deadline or assume an annual schedule.
- Find the exact legal applicant in the current notice's eligibility appendix. A vendor, consultant, or partner cannot replace the named applicant.
- Check the eligibility foundation. FY 2026 required an updated security plan based on a security assessment conducted within the specified three-year period.
- Separate applicant eligibility from recipient obligations. In FY 2026, agencies receiving funds were required to participate in a Regional Transit Security Working Group.
- Stop if the organization is not eligible. FY 2026 did not allow subapplicants or subawards, so an ineligible organization could not cure that problem by joining another applicant's proposal.
Ferry operators had an additional program-choice issue in FY 2026: under the current-cycle notice, participating in TSGP excluded participation in that year's Port Security Grant Program, and the reverse also applied. That choice belongs in the first budget meeting, not at submission. Organizations comparing programs can use the broader federal and state security-funding briefing to identify alternatives, but only the governing notice controls eligibility.
Can an existing-camera analytics project fit TSGP?
Potentially, but an expressly listed camera project does not automatically make every analytics configuration allowable. The FY 2026 notice included security cameras among physical-security enhancements at rail and bus stations in UASI jurisdictions. It also identified detection equipment, terrorism-incident-prevention equipment, and physical-security-enhancement equipment as acquisition categories. Equipment outside the Authorized Equipment List required prior FEMA approval. The correct conclusion is “confirmable candidate,” not “preapproved technology.”
Swipe or scroll horizontally to view all table columns.
| Proposed purpose | Stronger fit signal | What can break the fit | Required evidence |
|---|---|---|---|
| Restricted-area or perimeter monitoring | A documented transit-security vulnerability at a high-risk asset, tied to access control or physical protection | A general operations or property-management rationale with no terrorism nexus | Assessment finding, asset map, configured zone, alert owner, response procedure |
| Visible-weapon detection | A defined screening, search, detection, or soft-target protection gap in a camera-covered transit area | Treating product availability as proof of grant allowability or promising outcomes the evidence cannot support | Threat scenario, compatible views, verification workflow, responder handoff, current equipment determination |
| Vehicle activity around a secured asset | A specific vehicle-related vulnerability affecting a protected transit facility or perimeter | Broad traffic analytics, parking optimization, or unrelated fleet efficiency | Risk record, covered approach or gate, prohibited movement, response path |
| Camera-system cybersecurity | A vulnerability in cameras, sensors, access controls, or supporting systems | A routine replacement project without a documented cyber risk or security outcome | Cyber assessment, affected components, remediation scope, applicable framework |
| Camera expansion or replacement | A physical-security enhancement at an eligible location supported by the assessment | Replacing usable hardware solely because a vendor prefers a new camera estate | Coverage analysis, compatibility findings, equipment list, procurement justification |
The allowability boundary
Potentially allowable is not the same as approved. Confirm the exact hardware, software, licensing, integration, installation, cybersecurity, maintenance, and service costs against the current notice, the current AEL, FEMA policy, and the assigned Preparedness Officer. Do not infer that software is allowable merely because cameras appear in an example project.
Existing-camera reuse can strengthen the business case when technically supportable by reducing unnecessary replacement scope. Validate compatibility, field of view, lighting, network architecture, alert routing, and acceptance tests before fixing the budget. The AI video analytics RFP checklist supplies a separate procurement framework; it does not establish FEMA eligibility.
What evidence makes a camera-analytics project defensible?
A defensible project traces one documented vulnerability through one proposed capability to a measurable operational result. The FY 2026 notice required Investment Justifications and detailed budgets. The opportunity's 2020-form Investment Justification attachment asks applicants to address gaps and deficiencies, explain risk reduction, provide output and outcome metrics, and cover implementation and sustainment. Its printed form date should not be mistaken for a current rule; the current-cycle notice controls.
Keep the security assessment and PT-RAM duties separate
The FY 2026 notice imposed two distinct requirements that should not be collapsed into one checkbox. Applicant eligibility required an updated security plan based on a security assessment, such as TSA's BASE, conducted within the prescribed three-year period. Separately, FY 2026 recipients had to provide a Public Transit Risk Assessment completed within the past three years or implement one in conjunction with the award. An agency could therefore satisfy the security-plan foundation yet still need to address PT-RAM as a recipient condition.
Build the threat-to-response chain
- Asset: Identify the station, platform, yard, gate, tunnel, control room, or other eligible transit asset inside the properly controlled grant record.
- Vulnerability: Cite the current assessment or security-plan gap. Separate terrorism-related exposure from ordinary loss prevention or operational inconvenience.
- Detection event: Define the visible condition the system is meant to identify, such as a person crossing a configured perimeter or a visible weapon in a usable camera view.
- Human decision: Assign who receives the event image and location, who verifies it, and what information is needed before escalation.
- Response: Connect the alert to an existing procedure, transit police, security operations, or another authorized responder. Detection is not the response plan.
- Measure: Use auditable outputs and outcomes, such as validated camera coverage, completed integrations, personnel trained, exercised workflows, and documented response decisions. Do not promise perfect detection or prevention.
Handle application evidence as SSI
The FY 2026 notice treated every TSGP Investment Justification as Sensitive Security Information until DHS/FEMA completed its SSI review and directed applicants to label application documents as SSI under 49 C.F.R. § 1520.13. Keep vulnerability findings, asset maps, technical specifications, response details, and draft IJs inside authorized systems and follow the notice and agency SSI procedures. Do not paste protected details into ordinary email, chat, vendor intake forms, or general collaboration tools.
Make the budget traceable to the project
Separate compatible-camera assessment, software, approved equipment, installation, configuration, integration, training, project management, and sustainment assumptions. For each line, identify quantity, unit basis, project purpose, and supporting estimate. The FY 2026 notice had no cost-share requirement and stated that a voluntary match would not affect funding potential. A local contribution can still remove an uncertain cost from the federal request or support sustainment, provided the application describes it accurately and does not present the contribution as a competitive advantage.
Test whether the plan fits the award period and can be sustained. Do not purchase an alerting layer without owners, escalation rules, training, maintenance responsibility, and a path for recurring costs. The transit, rail, and aviation sector playbook can place the project in a larger architecture, but the Investment Justification must remain specific to the applicant's risk and operations.
Should you pursue, revise, or stop the project?
Pursue only when applicant eligibility, documented risk, project purpose, technical feasibility, cost allowability, evidence handling, and operational ownership all align. Revise when the security need is valid but the scope or evidence is incomplete. Stop when the applicant or purpose falls outside the program.
Swipe or scroll horizontally to view all table columns.
| Decision | Use it when | Next action |
|---|---|---|
| Pursue | The current cycle is open; the agency is named; the security record supports the gap; the project addresses an eligible transit-security purpose; costs can be confirmed; owners can implement and sustain it. | Develop the project-specific Investment Justification, detailed budget, milestones, controlled evidence file, and procurement plan. |
| Revise | The applicant and threat fit, but camera compatibility, alert ownership, cost classification, metrics, SSI handling, PT-RAM planning, or sustainment is unresolved. | Run a bounded technical assessment, consult the Preparedness Officer, assign document controls, and remove unsupported features or costs before writing. |
| Do not pursue through TSGP | The agency is absent from the current eligibility list, the cycle is closed, the purpose is primarily operational rather than security-related, or the project cannot connect to the assessment. | Use local capital, another eligible program, or a later cycle. Do not force a terrorism narrative onto an unrelated purchase. |
A “revise” decision identifies a defect to solve before application work continues. Record the failed gate, needed evidence, owner, handling requirements, and review date. Remove any cost FEMA will not confirm instead of obscuring it inside a broader line item.
What should agencies do after the FY 2026 deadline?
Prepare reusable evidence without drafting against rules that may change. The next notice must control the applicant list, deadline, priorities, forms, allocation, recipient conditions, and cost rules.
- Preserve the current security plan, assessment date, approval record, working-group documentation, and PT-RAM status in the agency's access-controlled grant workspace.
- Apply the agency's SSI procedures before collecting vulnerability findings, asset maps, technical details, or draft Investment Justifications. Limit distribution to people with authorization and a need to know.
- Rank candidate assets by documented vulnerability and consequence. Do not begin with a vendor feature list.
- For each project, write a one-sentence risk statement and a one-sentence operational outcome. Reject projects that cannot connect the two.
- Inventory existing cameras and supporting systems, then document compatibility questions, coverage gaps, cybersecurity constraints, and integration owners in the appropriate controlled record.
- Prepare a scalable base scope and clearly separated options. Obtain current estimates without treating them as a future FEMA-approved budget.
- When the next notice appears, rerun every gate and revise the project against the new text before authorizing application work.
Where can IntelliSee fit, and where does grant responsibility remain?
IntelliSee can help evaluate whether compatible existing cameras support a defined detection scenario, but the eligible agency retains responsibility for grant eligibility, risk documentation, SSI handling, cost allowability, procurement, and response design. IntelliSee's current page describes perimeter control for configured restricted areas. That product information can inform technical scoping; it does not constitute FEMA approval.
Swipe or scroll horizontally to view all table columns.
| IntelliSee evaluation can address | The applicant must establish |
|---|---|
| Whether selected camera views are technically suitable for a defined visual event | Why that event represents a documented transit-security vulnerability |
| How configured detections can reach responsible personnel | Who verifies, escalates, responds, documents, and exercises the workflow |
| What software, integration, and deployment elements belong in a proposed scope | Whether every cost is allowable under the current notice, AEL, and award conditions |
| How to test the proposed configuration before acceptance | The procurement method, SSI controls, grant milestones, records, reporting, PT-RAM compliance, and long-term sustainment |
If your agency passes the applicant and security-purpose gates, bring a non-sensitive camera inventory, controlled assessment reference, proposed response workflow, and current notice to a scoping discussion. Contact IntelliSee to examine technical fit before building a grant budget. Share SSI only through authorized channels when necessary. The objective is a supportable decision, not a promise of funding.
Frequently asked questions
Is the FY 2026 Transit Security Grant Program still open?
No. FEMA's official notice set July 24, 2026 as the application deadline. As of September 19, 2026, that cycle is closed. Agencies should monitor FEMA and Grants.gov for a later notice and should not assume the next applicant list, schedule, allocation, or rules will be identical.
Who was eligible for FY 2026 TSGP funding?
According to FEMA's FY 2026 notice, eligibility was limited to the passenger rail, intra-city bus, and ferry systems named in Appendix 1. Eligibility did not guarantee funding. The notice also required the security-plan and recent-assessment foundation, and it did not allow subapplicants or subawards.
Is PT-RAM the same as the security assessment supporting the security plan?
No. The FY 2026 notice separately required an updated security plan based on a recent security assessment, such as BASE, for applicant eligibility. It also required recipients to provide a Public Transit Risk Assessment completed within the past three years or implement one in conjunction with the award.
Does TSGP fund security cameras?
The FY 2026 notice expressly listed security cameras as an example of physical-security enhancements at qualifying rail and bus stations in UASI jurisdictions. That language does not automatically approve every camera, analytics product, license, integration, or service. Each item must fit the current notice, applicable equipment rules, project purpose, and approved budget.
Can TSGP fund analytics added to existing cameras?
It may be possible when the configuration addresses a documented transit-security vulnerability and its components fall within allowable categories. The FY 2026 notice did not give blanket approval to all video analytics. Confirm the precise equipment and cost treatment through the current AEL, FEMA guidance, and the assigned Preparedness Officer.
How should an agency handle its TSGP Investment Justification?
For FY 2026, the official notice required every TSGP Investment Justification to be treated as Sensitive Security Information until DHS/FEMA review and required application documents to carry SSI labeling under 49 C.F.R. § 1520.13. Agencies should follow the governing notice and their SSI procedures rather than sharing vulnerability or technical details through ordinary collaboration channels.
Did FY 2026 TSGP require a local match?
No. The FY 2026 notice stated that there was no cost-share requirement and that a voluntary match would not affect funding potential. Agencies must recheck this point in any later notice.
What should an agency prepare before the next TSGP notice?
Using the FY 2026 notice only as a planning reference, maintain the current security plan and assessment record, document PT-RAM status, establish SSI handling procedures, rank assets by documented vulnerability, inventory compatible cameras, define alert and response ownership, prepare a scalable scope, and collect supportable estimates. Once the next notice appears, rerun applicant eligibility, project purpose, allowability, recipient conditions, deadline, and documentation checks before writing.
Sources
Your people. Your spaces.
See it on the cameras you already have.
Bring one priority event and one camera view. We will walk through how IntelliSee turns it into an alert your team can act on.