My WebLink
|
Help
|
About
|
Sign Out
SR 05:304
City of Pleasanton
>
CITY CLERK
>
AGENDA PACKETS
>
2005
>
SR 05:304
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
10/20/2005 3:22:01 PM
Creation date
10/20/2005 3:04:12 PM
Metadata
Fields
Template:
CITY CLERK
CITY CLERK - TYPE
STAFF REPORTS
DOCUMENT NO
SR 05:304
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
27
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 /> EDAW INe WORK PROGRAM <br /> TRANSIT_O~IENTED :;PECIFIC PLAN <br />FOR THE H;,CI':NDA BUSINESS PARK <br />PRODUCTS We wi]] also work \vith the public. Our public <br /> process will need to be carefully tailored to ensure <br />We will provide five copies of all Administrativ'e the re~11ization of the Project Team's vision, and to <br />Draft products; one copy of a Glmera ready draft of be consistent with the City's General Plan Update <br />all ready~for-release Draft documents; five ha:d process. We anticipate meetings to be held upon <br />copies; and one camera ready copy and onl~ completion of the Background Report, <br />electronic copy (Microsoft Word, Adobe Acrobat, Alternatives, and Draft and Final Report. <br />or InLJesign) of all final products. All elect::onic <br />copies will be provided on a CD. <br />COMMUNICATION PROCESS <br />The implementation of this Plan \lv:.I1 affect many; <br />property owners, area residents, the City of <br />Pleasanton, and BART to name a few. <br />Consequently, it will be essential that infcrmation <br />be distributed and collected throughout the We will distribute information during these <br />planning process. sessions and solicit comments; however, our <br />In order to ensure an even and controlled flow of primary goal will be to prepare a Plan that <br /> implements the Project Team's vision for Transit <br />information, we propose a hierarchical Oriented Development at Haciend<1. <br />relationship between concerned parties,. incl uding <br />three basic groups: This process will be refined during project <br /> initiation, but the overarching consideration is to <br />. Project Management Team (Project Team and collect important input during the process and to <br />Consultant Team) distribute a clear and cohesive message <br />. Core Area Planning Team characterizing the intent and content of the plan. <br />. Public <br /> Cost <br />Our primary relationship will be vvith the Project <br />Team, and as described in uur vvork SCOPI~, \ve will The total fee proposal for plan preparation, <br />maintain a cluse relationship throughout. This excluding expenses incurred by te(lm members is <br />will include day-to-day communications, meeting~ $352,175.00. <br />at key junctures and review and discussion of edch <br />work product prepared. This fee is summarized by team members as <br /> follows: <br />Our next most frequently contacted grO'LLl y.,'ill be <br />the Core Area Planning Team, including property' EDAW: $120,000.00 <br />owners outside of the Core Planning Are.:l, cmd Strategic Economics: $47,000.00 <br />City and agency staff and others determined to be Fehr Zind Peers: $145,00000 <br />appropriate by the Project Team Ellen Creenberg, AICP: $40,175.00 <br />In addition to early interviews, WE' propose Timeline <br />ongoing communications on an as-needed basi.s <br />(i.e. working with City transportation staff It is anticipated that this planning process would <br />throughout the process etc.) and meetings or take approximately 10 months to complete. This is <br />workshops when work tasks are compieted a very aggressive timeline and will require timely <br />including the Background Report, Alternatives, action and response in order to execute. Of <br />Draft and Final Plan. <br /> C'::~ <br />
The URL can be used to link to this page
Your browser does not support the video tag.