My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
1A, 2010 Engineering Work Plan
ArdenHills
>
Administration
>
City Council
>
City Council Packets
>
2010-2019
>
2010
>
03-15-10-WS
>
1A, 2010 Engineering Work Plan
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
10/15/2024 12:55:23 AM
Creation date
3/15/2010 2:11:52 PM
Metadata
Fields
Template:
General
Document
2010 Engineering Work Plan
General - Type
2010 Engineering Work Plan
Date
3/15/2010
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
6
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
position or a part time position dedicated to Arden Hills. The timelines for these options <br /> vary. <br /> • Shared full-time employee (FTE): A shared FTE would not possible until 2011. <br /> This is the result of the City's budgeting cycle. Roseville does not have the funds <br /> available to pay for a half FTE in the 2010 budget. We would need to work with <br /> Arden Hills to determine a set number of additional hours based on what your <br /> long term engineering needs are, and then justify the remaining hours as a part of <br /> Roseville's 2011 budget process. If this is acceptable to both the Arden Hills and <br /> Roseville City Councils, it would address the long term need, but would not <br /> address our ability to deliver the 2010 Work Plan. <br /> • Part-time employee (PTE): if a PTE was hired that was not a shared employee, <br /> the timeline could be shorter. It would require the amendment of the JPA to <br /> expand the minimum hours to cover a set number of hours based on what your <br /> long term engineering needs are and the approval of the amended JPA by both <br /> Cities. Once that is complete, it would take around three months to advertise and <br /> hire a new employee. This still would not address our ability to deliver the 2010 <br /> Work Plan. <br /> Both of these scenarios would require that some of the tasks in the 2010 Work Plan be <br /> moved to 2011. <br /> As a part of the February discussion regarding additional Roseville JPA hours, the <br /> Council was provided financial spreadsheets showing the 2009 engineering expenditures. <br /> This information showed all monies paid out to Roseville and Consulting companies to <br /> complete the 2009 Work Plan. Attached is a table summarizing the work that could have <br /> been completed with Roseville engineering staff if there was available capacity? <br /> 3. Can some of the 2010 Work Plan items be pushed to the end of the year/2011? <br /> We have highlighted six tasks on the work plan that we recommend be shifted to 2011. <br /> This would reduce the 2010 work plan to 1,621.25 Engineering Hours and 982.75 <br /> Technician Hours. This still would not address our ability to deliver the 2010 Work Plan. <br /> Recommended Option: <br /> At this time Staff is recommending that both option 1 and 3 be implemented. This would <br /> reduce the 2010 work plan to 1,425.25 Engineering Hours and 950.75 Technician Hours. <br /> While this is still 706 over the 1670 hours committed to in the JPA, we have determined <br /> that Roseville has adequate engineer and technician time to deliver this revised work <br /> plan. If Roseville has the capacity at the end of the year, it may be possible to start <br /> working on the items on the 2010 Work Plan that are proposed to be shifted to 2011. <br /> These working hours are estimates; some of the projects may take more hours, while <br /> others may take less. There will also be additional tasks that will come up over the <br /> course of the year that will affect this work plan. <br /> City Council Worksession <br /> \\Metro-inet.us\ardenhills\PR&PW\Engineering\Council_Actions\2010\Worksessions\3-15-1 OMemo_2010Workplan.doc <br /> Page 3 of 3 <br />
The URL can be used to link to this page
Your browser does not support the video tag.