My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
ORANGE, COUNTY OF (53) - 2017
Clerk
>
Contracts / Agreements
>
O
>
ORANGE, COUNTY OF
>
ORANGE, COUNTY OF (53) - 2017
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
10/17/2017 4:19:31 PM
Creation date
10/12/2017 3:52:25 PM
Metadata
Fields
Template:
Contracts
Company Name
ORANGE, COUNTY OF
Contract #
A-2017-258
Agency
POLICE
Council Approval Date
9/19/2017
Expiration Date
5/31/2018
Destruction Year
2023
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
130
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
Instructions for UASI <br />• Urban Areas must propose at least one and up to 10 projects within each <br />investment in their U to describe the activities they are planning to implement <br />with UASI funds. <br />• Any projects not included in the application must be included in the first <br />BSIR. <br />• If applicable, Urban Areas are required to propose at least one investment in <br />support of a designated fusion center within the Urban Area. Recipients must <br />coordinate with the fusion center when developing a fusion center investment <br />prior to submission. <br />• If UASI funds are used by the SAA in support of the Urban Area, the SAA <br />must, as part of the up to 10 investments, propose an investment describing <br />how UASI funds will be used by the SAA to directly support the Urban Area. <br />• Recipients investing in emergency communications must describe how <br />activities align to the SLIP. Recipients must coordinate with the statewide <br />Interoperability Coordinator (SWIC) and/or statewide Interoperability <br />Governance Body (SIGB) when developing an emergency communications <br />investment prior to submission to ensure the project supports the statewide <br />strategy to improve emergency communications and is compatible and <br />interoperable with surrounding systems. <br />Instructions for OPSG <br />As part of the FY 2015 OPSG application process, each eligible local unit of government <br />at the county or Federally -recognized Tribal government level must develop their <br />Operations Order in coordination with state and Federal law enforcement agencies, to <br />include, but not limited to CBP/USBP. Operations Orders that are developed at the <br />county level should be inclusive of city, county, Tribal, and other local law enforcement <br />agencies that are eligible to participate in OPSG operational activities. The Operations <br />Order should address this in the Executive Summary. Operations Order details should <br />include the names of the agencies, points of contact, and individual funding requests. All <br />applications must be developed in collaboration with the local USBP sector office, the <br />SAA and the local unit of government. The sector office will then forward the <br />application to the SAA for final review before submission to DHS/FEMA. For more <br />information, refer to Appendix D — FY2015 OPSG Operations Order Template and <br />Instructions and Appendix E— OPSG Operational Guidance. <br />Intergovernmental Review <br />An intergovernmental review may be required. Applicants must contact their state's <br />Single Point of Contact (SPOC) to comply with the state's process under Executive Order <br />12372 (see http://www.fws.gov1policvllibrarvlrzeo]2372.12df). Name and addresses of <br />the SPOCs are maintained at the Office of Management and Budget's home page at <br />http://www.whitehouse.eov/omb/erants spot to ensure currency. <br />Funding Restrictions <br />Federal funds made available through this award may only be used for the purpose set <br />forth in this award and must be consistent with the statutory authority for the award. <br />13 <br />FY 2015 HSGP NOFO <br />
The URL can be used to link to this page
Your browser does not support the video tag.