New Search
My WebLink
|
Help
|
About
|
Sign Out
New Search
2010-2013 STIP Draft
COE
>
PW
>
Admin
>
Execs
>
Executive non-confidential
>
Historical
>
2010-2013 STIP Draft
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
8/21/2009 11:13:52 AM
Creation date
6/1/2009 12:22:14 PM
Metadata
Fields
Template:
PW_Exec
PW_Division_Exec
Administration
PWA_Project_Area
ODOT
PW_Subject
STIP
Document_Date
10/1/2008
External_View
No
Jump to thumbnail
< previous set
next set >
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
274
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).
Show annotations
View images
View plain text
DRAFT 2010-2013 STATEWIDE TRANSPORTATION IIvIPROVEMENT PROGRAM <br />proved metropolitan TIP. Other projects utilizing federal funds shall be selected by the MPO in <br />cooperation with the State and transit operators. <br />In MPO areas not designated as TMAs, projects using federal Title 23 or Federal Transit Act <br />funds, other than Federal Lands Highways program funds, shall be selected by the State and/or <br />the transit operator, in cooperation with the MPO, from the approved metropolitan Regional <br />Transportation Plan. <br />Outside MPO areas, transportation projects undertaken on the NHS and projects funded under <br />the Bridge and Interstate Maintenance programs will be selected by the State in consultation with <br />the affected local officials. Other transportation projects undertaken with funds administered by <br />FHWA, other than federal lands highway projects, shall be selected by the State in cooperation <br />with the affected local officials and projects undertaken with Federal Transit Act funds shall be <br />selected by the State in cooperation with the appropriate affected local officials and transit opera- <br />tors. <br />ACTS and MPOs should consult with each other during their STIP and MTIP development proc- <br />esses to achieve a coordination of projects wherever possible. Where ACT and MPO boundaries <br />overlap, a higher level of clearly defined coordination is needed. Where this occurs, the MPO <br />and ACT should jointly agree on a process for maintaining consistency between ACT recom- <br />mendations and the MPO Plan and MTIP (Policy on Formation and Operation of the Area <br />Commissions on Transportation, Section VII. G, Coordination). <br />Project Elig7bility Criteria <br />ACTs, MPOs, or regional or statewide advisory groups advising the OTC on the selection of <br />STIP projects for funding on the state highway system or for off-system projects that support <br />implementation of the OHP shall apply the project eligibility criteria. The project eligibility cri- <br />teria are a first screen so that additional efforts can be focused to determine which projects they <br />will evaluate further for funding. The eligibility criteria are not listed in any particular order. <br />Projects must satisfy these criteria, at a minimum, before they are given further consideration. <br />Prioritization Factors <br />The prioritization factors are to be used to ensure consistent consideration of the relative merits <br />of projects by ACTS, MPOs and regional or statewide advisory groups. With the exception of <br />project readiness which shall have greater weight, the prioritization factors are not listed in any <br />particular order and do not have any implied weight. To provide for regional differences, ACTS, <br />MPOs and regional or statewide advisory groups may use additional factors to rank projects pro- <br />vided the factors are consistent with the factors adopted by the OTC. If an ACT, MPO or re- <br />gional or statewide advisory group chooses to use additional prioritization factors, they must in- <br />form those developing project proposals about the factors prior to the beginning of the project <br />submittal period. When developing a tool to evaluate OHP policies, OHP Appendix A2 provides <br />definitional information to facilitate shared understanding of the goals, policies and actions of the <br />OHP policy element. <br />Page 207 <br />
The URL can be used to link to this page
Your browser does not support the video tag.