New Search
My WebLink
|
Help
|
About
|
Sign Out
New Search
Traffic Operations Policy and Procedures
COE
>
PW
>
Admin
>
Finance
>
Operating
>
2011
>
Traffic Operations Policy and Procedures
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
10/12/2010 3:55:02 PM
Creation date
10/12/2010 2:04:30 PM
Metadata
Fields
Template:
PW_Operating
PW_Document_Type_ Operating
Policy
Fiscal_Year
2008
PW_Division
Maintenance
External_View
No
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
46
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
SECTION 1: GENERAL <br />' The provisions herein shall go into effect July 1, 2006. <br />LA AUTHORITY. <br />This operational policy and procedure document was prepared and enacted under the administrative and rule- <br />' making authority granted the City Manager by Section 2.019 of the Eugene Code, 1971 and the authority <br />granted the City Traffic Engineer by Chapter 5 of the Eugene Code, 1971, Administrative Order No. 58-00-29 - <br />F, and Administrative Rule R- 5.045. <br />LA.1 Eugene Code — Chapter 5 - TRAFFIC <br />Eugene Code, Chapter 5, identifies specific areas of authority for the administration of traffic responsibilities by <br />the City Manger or manager's designee. Chapter five also identifies the recognized appeal process for review <br />of chapter five actions. <br />1.A.2 Administrative Orders and Rules <br />1 Administrative Orders and Rules may be used to complement, supplement, or modify existing Eugene Code. <br />The Administrative Order process was utilized to delegate specific traffic authority to the City Traffic Engineer. <br />1.A.3 Engineering Judgment <br />Engineering judgment is a complex, involved process requiring consideration of legal requirements, design, <br />history, use, safety, intent, and an engineering study. The Traffic Engineer has ultimate authority for exercising <br />engineering judgment in the application of traffic control. <br />1.E INTRODUCTION. <br />It is the objective of Public Works - Traffic Operations to establish an operational policy and procedure <br />1 document which clearly identify standards utilized in implementing consistent decisions as the local road <br />authority, defined by ORS 810, for the City of Eugene. <br />' In implementing traffic standards, Traffic Operations operates under several federal and state requirements. For <br />operational consistency within the transportation system, the Federal Highway Administration requires <br />individual States to adopt the Manual of Uniform Traffic Control Devices ( MUTCD) or develop operational <br />standards consistent with the MUTCD. The State of Oregon adopts the MUTCD — with Oregon amendments. <br />Local road authorities are required to comply with the Oregon adopted standards. <br />' Traffic Operations utilizes specific language similar to the MUTCD in this policy and as follows: <br />e Standard — a statement of required, mandatory, or specifically prohibitive practice regarding a traffic <br />control device. The verb "shall" is typically used. <br />e Guidance — a statement of recognized general practice in typical situations, with deviations allowed if <br />engineering judgment or engineering study indicates the deviation to be appropriate and in conformance <br />' with recognized objectives. The verb "should" is typically used. <br />e Option — a statement of practice that is a permissive condition and carries no requirement or <br />recommendation. The verb "may"'is typically used. <br />Page 7 of 36 <br />Lest Revised: 2127106 <br />
The URL can be used to link to this page
Your browser does not support the video tag.