My WebLink
|
Help
|
About
|
Sign Out
Home
Search
09/06/2006 Council Packet
LinoLakes
>
City Council
>
City Council Meeting Packets
>
1982-2020
>
2006
>
09/06/2006 Council Packet
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
4/25/2014 3:39:05 PM
Creation date
4/25/2014 11:32:27 AM
Metadata
Fields
Template:
City Council
Council Document Type
Council Packet
Meeting Date
09/06/2006
Council Meeting Type
Work Session Regular
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
66
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 />B. Response to letter of concerns from the St. Paul Regional Water Service. <br />(Dialogue to address individual concerns // Who should be a part? // When? // <br />Dialogue facilitator) <br />The idea of forming a task force to answer the letter was proposed. TW: felt the letter <br />was expected and that it was appropriate and necessary to address all of the concerns <br />raised by the Board of Water Commissioners in their letter. He noted that there does not <br />have to be unanimity on all issues. <br />Could the JPA be reformed without SPRWS? BWSR staff has responded affirmatively. <br />SS: saw the draft Plan as a vision, but needs more substance. <br />PE: expressed concern about the short list of projects, noting that new projects would <br />require Plan amendments. <br />DS: it was noted that projects grow after diagnostic studies show where & how to focus <br />the energy. <br />MS expressed concern over the language signifying the JPA had broken the law. He <br />noted the WBL representative had continued through completing his term. Volunteers <br />are sometimes hard to find, but a new Commissioner has been appointed. <br />TW: expressed concern over continuing the conversation with SPRWS representatives if <br />there was a potential lawsuit pending. SPRWS representatives indicated the AG's office <br />had declined authority at this time. <br />Essential question: Who drafts & approves the annual budget? <br />TW: Municipalities currently fund operations and must set levies. They are accountable <br />to their citizens. He noted that the original '06 budget clearly could not be approved. It <br />was too radical a change. They considered the adjusted budget `half full.' <br />DS (How does the association with SPRWS benefit VLAWMO ?): * monitoring of water <br />quality for the main & Lambert chain of wetlands & lakes; * help getting grant funding <br />(both through `drinking water' leverage and providing substantial in -kind [staff time & <br />cash] matching); * technical assistance for multiple watershed projects or programs. <br />C. Direction for JPA issues <br />The current draft (61406) of the JPA features: <br />1. Board structure and functioning <br />a. Who? Members of the JPA may appoint whoever they choose so long as the choice is compliant <br />with state law. Several of the membership have expressed a need to have accountability to the <br />taxpayers for operational and capital expenses. The new draft language attempts to balance this <br />need with the organizational need to knowledgeable Board Commissioners guiding the annual <br />budget process. <br />PE: the new language suggests elected officials be on the board or as an alternate <br />Commissioner. <br />MS: noted there were both technical and fiscal responsibilities and both can be <br />accommodated with a variety of structures. Perhaps the Board of elected officials <br />could meet up to 4x yearly, but delegate some of its authority to a monthly operation <br />committee (Technical Advisory Committee ?). A budget sent to the communities must <br />only be passed by a majority. The delegates would need to "sell" or explain & <br />support the budget to the Councils. Get the Council liaisons involved early so <br />Councils are not surprised. <br />
The URL can be used to link to this page
Your browser does not support the video tag.