Or. Admin. Code § 660-044-0045 - Adoption of Regional Plans to Implement the Preferred Scenario
(1) Within one year
of the commission's order approving Metro's amendments to the regional
framework plan to select, incorporate, or amend a preferred land use and
transportation scenario, Metro shall adopt regional functional plan amendments
to implement the framework plan amendments.
(2) Functional plan amendments shall
establish requirements, deadlines, and compliance procedures for amendments to
local comprehensive plans, transportation system plans, and land use
regulations as necessary to implement the framework plan amendments. The
functional plan amendments shall require affected cities and counties to adopt
implementing amendments to comprehensive plans and land use regulations within
two years of acknowledgement of Metro's functional plan amendments or by a
later date specified in the adopted functional plan.
(3) Functional plan amendments shall include
requirements that local governments amend local comprehensive plans,
transportation system plans, and land use regulations to:
(a) Use population, housing and employment
allocations to specific areas and land use design types that are consistent
with estimates in the framework plan including assumptions about densities,
infill, and redevelopment;
(b)
Apply comprehensive plan designations and zoning districts that are consistent
with land use design type, allowing uses and densities that are consistent with
land use design type and limiting uses that would be incompatible with the
design type specified in the preferred scenario; and,
(c) Include other provisions needed to
implement the amended framework plan.
(4) As part of its adoption of functional
plan amendments under this rule, Metro shall adopt findings demonstrating that
actions required by the functional plan amendments are consistent with and
adequate to implement the relevant portions of the preferred land use and
transportation scenario set forth in the adopted framework plan amendments. The
findings shall demonstrate that assumptions or allocations of housing and
employment growth to specific areas are consistent with the estimates or
assumptions in the framework plan amendments. In the event Metro's allocations
or assumptions vary from those upon which the framework plan amendments are
based, Metro shall demonstrate that the revised assumptions or allocations, in
combination with other measures adopted as part of the functional plan will
meet the greenhouse gas emission reduction target in OAR
660-044-0020.
(5) Those portions of the preferred scenario
in the framework plan that Metro chooses to implement by establishing
requirements for city and county comprehensive plans and land use regulations
shall be set forth in amendments to the functional plan. The amendments shall
meet the following minimum planning standards:
(a) For adoption of amendments to the
regional framework plan, the Metro Council shall follow the process set forth
in the Metro Charter;
(b) For
adoption of amendments to the functional plan, the Metro Council shall follow
the process set forth in the Metro Charter for adoption of
ordinances;
(c) The Metro Council
shall strive for flexibility when establishing new requirements for cities and
counties, and shall consider offering optional compliance paths to cities and
counties, such as adoption of a model ordinance developed by Metro;
(d) Metro shall make new requirements for
cities and counties included in the functional plan amendments adopted under
this rule enforceable by Metro pursuant to ORS
268.390(6).
(6) When it adopts an updated
regional transportation system plan required by OAR chapter 660, division 12,
Metro shall demonstrate that the updated plan is consistent with framework plan
amendments adopting a preferred scenario as provided in OAR
660-044-0040(3).
Notes
Statutory/Other Authority: ORS 197.040 & 2009 OL Ch. 865 §37(8) (HB 2001)
Statutes/Other Implemented: 2009 OL Ch. 865 §37(8) (HB 2001)
State regulations are updated quarterly; we currently have two versions available. Below is a comparison between our most recent version and the prior quarterly release. More comparison features will be added as we have more versions to compare.
No prior version found.