My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
Golf Course Advisory Board Agenda and Packet 2014 03 17
PORTAL
>
BOARDS COMMISSIONS COMMITTEES RECORDS (20.000)
>
GOLF COURSE ADVISORY BOARD
>
2014 Golf Course Advisory Board Agendas and Packets
>
Golf Course Advisory Board Agenda and Packet 2014 03 17
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
3/10/2021 2:43:05 PM
Creation date
3/18/2014 9:13:43 AM
Metadata
Fields
Template:
City Council Records
Doc Type
Boards Commissions Committees Records
Supplemental fields
Test
GCABPKT 2014 03 17
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
148
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).
Show annotations
View images
View plain text
Golf Course Advisory Board Minutes <br />February 102014 <br />Page 3 of 4 <br /> <br />and US 36. If adopted the estimated $12M cost would be allocated among all <br />downstream affected communities. <br />FEMA has provided a number of comments on the project and how to <br />proceed, some of them contradictoryas FEMA staff change. FEMA expects <br />to conduct Design Reviewsof the Project as plans become30%, 60% and <br />90% complete. We have already pre-submitted a Project worksheet and Staff <br />feel that we are already at the 30% design completion stage and some of the <br />formal design reviews may be skipped. Approval from theState Office of <br />Emergency Managementis also required. FEMA has conducted a <br />preliminary Walk-through on the Golf Course and it is felt that work can be <br />started on items which clearly fall into the category of Storm Damage, for <br />example draining the pondsaffected by the flood. <br />LUadvised that no specific actions such as fertilization or fungicide <br />application are needed before or during construction. <br />Senior Advisor Sackett reminded the Board that we are working on a complex <br />project and opencommunication between Board Members and Staff isvital. <br />By the May /June timeframe we need to agree on what items are to be <br />included and this may require Special Meetings to expedite progress. <br />Chairman Gambon and Dennis Maloney will continue towork with Staff as a <br />sub-team to prepare issues for Board Discussion. <br />Joe Stevens advised that he was meeting with Lisa Norgard and Heike <br />Nielsen on initial ideas for a Marketing Plan.In general, the Board felt that, <br />although getting some initialideas was good,it was premature to go into <br />much detail on a MarketingPlan.Focus should be applied to an overall <br />Business Plan and that alone will require other sub-teams to be set up as the <br />Business plan is quite distinct from the Marketing Plan.City Staff are <br />working on a Business plan for discussion at future Board Meetings. <br />7Presentation of Project Schedule <br />The Board discussed the Gantt Chartprovided by LU. As the project moves <br />forward, much underlying detail will be added. Staff are concerned that FEMA <br />approval may be a pacing factor. In general, approval is expected within 3 <br />weeks of final applicationfrom most of the relevant agencies.The schedule <br />shows that FEMA Approval is needed by March 18 to allow the major work on <br />courseconstruction to start by the end of March. The new Irrigation System must <br />be on-line by July 1 to support grassing and the grow-in period. Any significant <br />delay to this program could make us miss the 2014 grow-in period and push back <br />the expected re-opening. The Board agreed that the grow-in period should not <br /> <br />·· <br />Parks and Recreation Department 749 Main Street Louisville, CO 80027 <br />· <br />(303) 335-4735 FAX (303) 335-4738 <br />www.louisvilleco.gov <br />Parks Recreation Senior Services OSpace Forestry Trails <br />Golf <br />4 <br />
The URL can be used to link to this page
Your browser does not support the video tag.