Section 335.09. Criteria for priority ranking.  


Latest version.
  • (1)  The department shall develop a priority ranking process for the purpose of determining funding priorities for applications under this chapter.
    (2)  The department may use an advisory committee to help develop the priority ranking process.
    (3)  The priority ranking process shall be reviewed and adjusted, if necessary, based on experience from past grant cycles and public safety priorities, prior to the notice of a new grant cycle.
    (4)  The following criteria may be used by the department in the priority ranking process. The criteria are not listed in any order of priority:
    (a) Hazard of the dam based on existing land use downstream.
    (b) Extent of land use controls currently in effect downstream of the dam to prevent development in the hydraulic shadow of the dam.
    (c) Financial need of the applicant.
    (d) Total eligible project costs.
    (e) Navigability of the watercourse.
    (f) Size classification of the dam.
    (g) Extent to which the project improves the safety in the area downstream of the dam.
    (h) Severity of the deficiencies of the dam.
    (i) Time frame in which the project can start construction.
    (j) Presence of approved emergency action plan and inspection, operation and maintenance plan for the dam.
    (k) Availability of public access to the impoundment created by the dam.
    (L) Extent of effort by the owner to responsibly operate and maintain the dam.
    (m) Any other criteria that the department identifies as necessary to improve the ranking process based on past experience with the grant program.
    (5)  The department shall determine the priority ranking points for an applicant based on information found on the grant application and in supplemental material; department files, map repositories and databases; on-site inspections or reports from past inspections; and discussion with the owner.
History: Cr. Register, April, 1991, No. 424 , eff. 5-1-91; CR 10-032 : r. and recr. Register October 2010 No. 658 , eff. 11-1-10.