My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
2016-05-09-minutes-public-works-study-session
>
Meetings
>
2016
>
10. October
>
2016-10-04 10:00 AM - Commissioners' Agenda
>
2016-05-09-minutes-public-works-study-session
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
5/12/2020 1:35:43 PM
Creation date
5/12/2020 1:30:23 PM
Metadata
Fields
Template:
Meeting
Date
10/4/2016
Meeting title
Commissioners' Agenda
Location
Commissioners' Auditorium
Address
205 West 5th Room 109 - Ellensburg
Meeting type
Regular
Meeting document type
Supporting documentation
Supplemental fields
Alpha Order
a
Item
Approve Minutes
Order
1
Placement
Consent Agenda
Row ID
32188
Type
Minutes
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
117
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
Procedures <br />Introduction/Flovy Chart <br />As noted in Chapter 1, L1Ds are not the most complicated thing in the world, but they do require <br />attention to detail and processes. The narrative in this Chapter 3 is intended to "flesh out" the <br />Legal Summary in Chapter 2. Your LID administrator will want to make a copy of the <br />Checklist/Outline in Chapter 2 and/or other resources in the online appendices. Some of us <br />(engineers mostly) may find the LID flow chart, based on Chapters 35.43 through 35.56, on the <br />following pages useful. <br />Pre -Formation Activities <br />An LID may originate with an inquiry from a c tizen asKing about improvements in his/her <br />neighborhood. Or an LID may be considered by an agency as a source of funding for a project <br />in the capital improvement program. An LID may be looked to as a method to mitigate impacts <br />of a proposed development and distribute costs equitably to other landowners benefitting from <br />the improvements in the development. Whatever the reason for an LID, the agency's LID <br />administrator (which may vary by project) and public works staff must review the proposed <br />project to de -ermine if it is practical or feasible and whether it lends itself to financing through <br />an LID. To determine preliminarily whether an LID is feasible, the LID administrator and public <br />works staff often should consult with a civil engineer, as well as experts in finance, law, and land <br />value. <br />After a project is found to be feasible, a typical first step by the LID Administrator is to determine <br />the extent of landowner support for the project. One cost effective method of making this <br />determination is for the Administrator to prepare a fact sheet and informal petition (not to be <br />confused with a formal petition for LID formation per the statutes)for circulation by the project <br />proponent(s). <br />This informal petition should describe the nature of the project, the extent of the proposed <br />improvements, the district boundaries, the method of payment, and the length of time of the <br />payments (amortization period). Frequently, it is not economical to provide "up front" cost <br />information, but if possible, a project cost estimate should be included on the petition However, <br />avoid providing estimated costs whenever there is a reasonable possibility that the costs will be <br />too low or whenever the proposed project may not occur far an extended period of time. Failing <br />to provide costs will not be a popular choice; however, the escalation of costs overtime usually <br />will make this the correct choice. Grant funds and city and/or developer contributions to the <br />proposed project should be identified as early as possible, as these contributions will reduce <br />assessments to properties in the LID. <br />Local and Road Improvement 0Istricts Manual for Washington State Sigh Edition 23 <br />
The URL can be used to link to this page
Your browser does not support the video tag.