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 />• <br />• <br />JM: expressed concern over draft language that considers the budget (operating or <br />CIP) to be approved by JPA member if they do not respond in 60 days. It may not be <br />legally binding. <br />TW noted that timing is becoming critical. He offered to review and offer language in <br />the 'governance' section (Sec. 4: Powers & Duties of the Board). <br />PE said the formula does need to be in the JPA. He referenced the checklist of <br />requirements BWSR looks at when reviewing Joint Powers Agreements. <br />Timeline established: <br />• August 23: all comments due on the JPA. Send them to the VLAWMO office. <br />Now is the time to comment, if there is something you can or cannot live with. <br />All comments received will be distributed to all of the other JPA members. <br />♦ September first half): JPA Meeting to consider comments / alternative JPA <br />language <br />• November r: Final JPA language deadline. JPA distributed to membership <br />for authorization in November or December. <br />i. The new JPA language recommends either the primary commissioner or the alternate be <br />an elected official to provide fiscal oversight (JPA, Sec. III, subd. 2). It DOES NOT <br />require elected officials serve on the VLAWMO board. <br />ii. However, the JPA again recommends that the `elected' board member, if there is one, <br />attend at least the annual meeting and the meeting where the annual budget will be <br />discussed (JPA, Sec. III, subd. 9). <br />b. The Technical Advisory Committee would advise on project & program efforts, review project & <br />operational budgets and other efforts (city engineers, BWC engineers, etc). <br />c. The Citizens Advisory Committee could work with specific program areas [e.g. education, strategic <br />lake planning, monitoring, etc.] and could include the volunteer lake monitors, Birch Lake <br />Improvement District, & others. <br />d. The draft JPA continues the current practice of disallowing any compensation of Commissioners by <br />VLAWMO, no stipend or per -diem. This does not keep the appointing body from providing some <br />compensation. There has been discussion that an annual stipend might mitigate Commissioner <br />expenses involved in driving, lost work hours, etc. There is precedent in other watersheds. Should <br />this be changed? <br />e. The VLAWMO Board changed the regular meeting time to evenings to allow for those with <br />daytime jobs better access to regular board meetings. <br />2. Annual Budget Process <br />a. Income options are expanded to allow for levy or stormwater utility fees. <br />b. The VLAWMO budget is broken in to operations (0) and capital improvement project (CIP) <br />expense, with slightly different approval processes. JPA members have 60 days from June 1st to <br />review and approve both budgets. NO comment constitutes approval. CIP budget elements may be <br />funded through Storm Water Utility Fees (if legal opinion says we can use it or our name is added <br />to list of agencies who can do this — legislatively) or by assessing a specific subwatershed if we <br />receive levy authority. Communities within an affected area would have the opportunity to review <br />and approve. <br />
The URL can be used to link to this page
Your browser does not support the video tag.