My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
ORANGE COUNTY TRANSPORTATION AUTHORITY (2)
Clerk
>
Contracts / Agreements
>
INACTIVE CONTRACTS (Originals Destroyed)
>
O (INACTIVE)
>
ORANGE COUNTY TRANSPORTATION AUTHORITY (2)
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
7/23/2015 9:26:12 AM
Creation date
11/16/2006 9:08:34 AM
Metadata
Fields
Template:
Contracts
Company Name
ORANGE COUNTY TRANSPORTATION AUTHORITY OCTA
Contract #
A-2005-310-23
Agency
Police
Council Approval Date
9/19/2005
Destruction Year
2012
Jump to thumbnail
< previous set
next set >
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
253
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
View images
View plain text
<br />FY05 HOMELAND SECURITY GRANT PROGRAM - VERSION 2.0. 12-22-2004 <br /> <br />submitted to ODP by February 16. 2005. ODP will provide technical assistance to <br />the urban areas throughout the strategy development process. <br /> <br />4. Allocation of Funds. The intent of the grant is to establish a metropolitan area- <br />wide approach to homeland security. Therefore. the use and allocation of all grant <br />funds available through the FY05 UASI Program must focus on the implementation <br />of the Urban Area Homeland Security Strategy, They must also be consistent with <br />the validated Urban Area Homeland Security Strategy, the State Homeland Security <br />Strategy, and the UASI Program guidelines. Additionally, the SAA pac, in <br />coordination with the UAWG, must develop a methodology for allocating funding <br />available through the UASI Program. The core city(ies), core county(ies), and <br />SAA must provide written concurrence on the spending plan and allocation of <br />funds. Written concurrence must be provided to the ODP Preparedness <br />Officer prior to the obligation or drawdown of funds. <br /> <br />C. Authorized Program Expenditures <br /> <br />Allowable expenditures for FY05 UASI comport with FY05 SHSP (except for the use of <br />funds for operational costs) and funding is expended based on the Urban Area <br />Homeland Security Strategies, Please refer to Appendix A: Authorized Program <br />Expenditures for detailed information on authorized and unauthorized UASI <br />expenditures. <br /> <br />Operational Activities <br />In support of FY05 UASI efforts to build an enhanced and sustainable capacity to <br />prevent, respond to, and recover from threats or acts of terrorism, states and urban <br />areas may use FY05 UASI funds to support select operational activities. No more than <br />25% of the gross amount of the UASI award may be used for operational expenses and <br />overtime costs for the operational activities noted below, which includes the operational <br />costs in Operational Costs Guidance on page 26. These funds may be used for the <br />following three (3) operational activities: <br /> <br />1. States and local jurisdictions may use up to 25% of FY05 UASI funds to support <br />select operational overtime costs associated with increased security measures at <br />critical infrastructure sites in UASI jurisdictions during periods of heightened alert. <br /> <br />. Of this amount, up to 10% of FY05 UASI funds may be used to support <br />operational overtime costs incurred at Code Yellow or Orange that are <br />associated with increased security measures at critical infrastructure sites in <br />UASI jurisdictions. <br /> <br />. The remaining 15% of FY05 UASI funds may be used to support operational <br />overtime costs incurred only at Code Orange that are associated with <br />increased security measures at critical infrastructure sites in UASI <br />jurisdictions. <br /> <br />DEPARTMENT OF HOMELAND SECUR(TY I OFF(CE FOR DOMEST(C PREPAREDNESS <br /> <br />72 <br /> <br />
The URL can be used to link to this page
Your browser does not support the video tag.