2008-2011 STIP Final - Laserfiche WebLink

New Search

FINAL 2008-2011 STATEWIDE TRANSPORTATION IMPROVEMENT PROGRAM STIP Development Process Steps In general, the STIP development process involves the following sequence. Note that this sequence does not spell out the planning steps that precede STIP development. These preceding steps, which are extremely impor- tant for positioning projects to be considered for funding approval, are complex and must be completed before a project can be in- cluded in the STIP.2 A diagram depicting the STIP development process is included at the end of this section; it divides the STIP development process into four major steps: setting goals and funding levels, selecting projects, reviewing the draft program, and approving the fmal program. The graphic also shows the approximate time it takes to complete these steps. highway corridors that may lead to facil- ity plans and refinement plans that iden- tify engineering solutions. • Most local governments have adopted long-range (usually 20 year) TSPs that identify system improvement needs; STIP projects need to be consistent with adopted TSPs.3 • MPOs prepare long-range RTPs that identify capacity-related system im- provements; STIP projects in metropoli- tan areas need to be consistent with adopted RTPs. • Tribes and federal land management agencies prepare long range plans for the road systems they manage. During the STIP development process, the following steps generally occur: Before the STIP process begins: • Management systems, collectively known as the Oregon Transportation Management Systems, have been devel- oped for some programs that help define conditions that warrant putting a project on a "watch" list. Conditions may in- clude things like pavement wear, safety problems (determined by crash records), traffic counts at intersections, or bridge ratings; field inspections refine informa- tion about asset conditions. • The OTC may update policy documents and related plans, like the Oregon Transportation Plan, Oregon Bicycle and Pedestrian Plan, Oregon Highway Plan, and Oregon Bridge Options Re- port, in which policies, investment pri- orities, and/or performance criteria are established for state transportation facili- ties. • ODOT regions work with local govern- ments to identify problem locations in z There is more information about the steps that must be completed before projects can be included in the STIP in the STIP Users' Guide at http://www.oregon.~ov/ODOT/HWY/STIl'/ Setting_Goals and Fundin L~ls • ODOT divisions assess overall transpor- tation system needs for highway, public transit, and multi-modal systems. • The Highway Program Office (HPO) prepares a revenue forecast for the STIP from various funding sources. • Program managers establish preliminary program funding levels; ODOT execu- tive staff determines recommended pro- gram funding levels for the OTC. • Program advisory committees meet to review how well their programs are achieving adopted goals. • Transit program managers, highway program managers, region managers, ACTs, MPOs, the Oregon Freight Advi- sory Committee (OFAC), and other stakeholders provide comments to the 3 According to the state's Transportation Planning Rule (Oregon Administrative Rule Chapter 660, Di- vision 12 [OAR 660-012]), cities with populations of 2,500 or more and counties with populations of 25,000 or more are required to prepare TSPs. OAR 660-012 provides guidelines for the preparation of TSPs. Page 8 J ~: .) _. ,. ~ , (~ l ~-- ~-~