My WebLink
|
Help
|
About
|
Sign Out
NEIGHBORHOOD STABILIZATION PROGRAM 2
City of Pleasanton
>
CITY CLERK
>
LONG TERM AGREEMENT
>
A
>
ALAMEDA COUNTY
>
NEIGHBORHOOD STABILIZATION PROGRAM 2
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
2/9/2015 1:07:53 PM
Creation date
1/4/2010 3:39:05 PM
Metadata
Fields
Template:
LONG TERM AGREEMENTS
LONG TERM AGREEMENTS - DOCUMENT DATE
12/1/2009
LONG TERM AGREEMENTS - NAME
NEIGHBORHOOD STABILIZATION
LONG TERM AGREEMENTS - TYPE
MISC AGMT
LONG TERM AGREEMENTS - RECORD SERIES
704-06 (Long Term Agreements)
LONG TERM AGREEMENTS - DESTRUCTION DATE
PERMANENT
LONG TERM AGREEMENTS - NOTES
ARRA
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
47
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
Section 2.5 Program Income. <br /> If any Program Income is generated by the expenditure of Consortium Funds <br /> received by the County, (i) the County shall cause such funds to be used for eligible <br /> NSP2 Activities, (ii) the County shall keep appropriate records of such Program Income, <br /> and (iii) the County shall report such Program Income to the Steering Committee as part <br /> of the reports required by Section 3.5. In accordance with NSP2 Requirements, <br /> substantially all Program Income must be disbursed for eligible NSP2 Activities before <br /> the County may expend additional NSP2 funds. <br /> ARTICLE 3. <br /> PERFORMANCE OF NSP2 ACTIVITIES <br /> Section 3.1 Performance of NSP2 Activities. <br /> The County shall perform and cooperatively carry out all NSP2 Activities <br /> described in the Grant Application in a timely manner and in compliance with the NSP2 <br /> Requirements. The County shall carry out the NSP2 Activities described in the Grant <br /> Application within the Consortium jurisdiction. <br /> Section 3.2 Lead Member Administrative Responsibilities. <br /> The County, as Lead Member, has the duties set forth in the Consortium <br /> Agreement. In addition, the Lead Member is responsible for (i) entering into the Grant <br /> Agreement, (ii) using best efforts to ensure that the NSP2 Program is effected in <br /> compliance with all NSP2 requirements, (iii) providing support and guidance to all <br /> Members in carrying out NSP2 Activities, and (iv) submitting documents to HUD as <br /> required for participation in the NSP2 Program, including but not limited to all DRGR <br /> System reporting. <br /> The City, as a Member of the Consortium, will participate in the Steering <br /> Committee, and provide one city staff person to participate in these quarterly meetings. <br /> Section 3.3 Selection of Developers. <br /> The County shall participate in a cooperative effort with other Members to <br /> prepare and distribute a Local Request for Proposals (RFP) to request proposals from <br /> potential Developers. As previously decided by the Steering Committee during its first <br /> meeting in June 2009, those Members whom have conducted previous competitive <br /> processes for NSP may submit their selected Developer as an approved developer under <br /> the NSP2 program To date, Alameda County has conducted a competitive process on <br /> behalf of the Urban County; the City of Livermore has conducted a competitive process <br /> on behalf of a group of cities funded by the State under the State NSP 1 program; and the <br /> City of Hayward has conducted a competitive process under the State NSP1 program. <br /> The Steering Committee shall make a final decision regarding the number of Developers <br /> to use in this program. Once Developers have been selected, the County will separately <br /> contract with one or more such Developers to implement NSP2 Activities through -out the <br /> Alameda County and City of Pleasanton <br />
The URL can be used to link to this page
Your browser does not support the video tag.