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
2.X.2 Privately Engineered Public Improvement (PEPI) <br />2.X.3 Pavement Preservation Project (PPP) <br />2.Y Inspection of Projects <br />Inspections of projects are generally performed by Public Works Engineering (PWE) inspectors <br />assigned to the project. Final inspection of traffic control devices and street lighting shall be <br />performed by Traffic Operations staff. PWE project inspectors shall not approve final <br />inspections without approval of Traffic Operations. <br />2.Y.1 Capitol Improvement Project (CIP) <br />2.Y.2 Privately Engineered Public Improvement (PEPI) <br />2.Y.3 Pavement Preservation Project (PPP) <br />2.Y.4 Right -of -Way Issues <br />Traffic Operations staff may be called on to review a variety of right -of -way issues and concerns. <br />Traffic Operations staff may require or effect immediate action when a concern for safety or <br />unauthorized restricted mobility exists. <br />22 Service Requests (APWA 31.04) <br />Service requests are official or formal requests for additions or modifications to the existing <br />transportation system. Requests are received from many sources and may include citizens, <br />businesses, internal staff, LTD, ODOT, Lane County, Universityof Oregon, and others. Internal <br />and external requests are treated equally. The service request system serves the function of <br />petitioning Traffic Operations for the placement of traffic control devices. <br />Service requests received by Traffic Operations are logged electronically and assigned to <br />appropriate staff based on workload, nature, and complexity of the request. The electronic <br />database used to manage service requests includes the nature of request, contact information, <br />research and investigation steps conducted, and the outcome of the request. Generally, Traffic <br />Operations is able to make an initial contact on service requests within two weeks. However, <br />workload and seasonal priorities, along with complexity of the requests may delay initial <br />contacts for several months. Following the review and decision process, Traffic Operations staff <br />contacts requestors and explain findings and basis for decisions. <br />2.AA Lane Transit District Coordination <br />Page 34 of 36 <br />Last ReWsed. 3110108 <br />
The URL can be used to link to this page
Your browser does not support the video tag.