text
stringlengths 2
132k
| source
dict |
|---|---|
Ph.D. Dissertation. The University of California at Davis. 1999. 19. Hultgren, L. and K. Kawada. San Diego ’s Interstate 15 High-Occupancy/Toll Facility Using Value Pricing. Institute of Transportation Engineers Journal, June 1999. 20. Supernak. San Diego State University, Task 3.2.2 Report, May 1998. 21. Deakin, E. Urban Transportation Congestion Pricing Effects on Urban Form. Transportation Research Board Special Report 242, 1994. 22. Guide for the Design of High Occupancy Vehicle Facilities . American Association of State Highway and Transportation Officials, Washington, D.C., 1992. 23. A Policy of Geometric Design of Highways and Streets. American Association of State Highway and Transportation Officials, Washington, D.C, 1994. 24. Manual on Uniform Traffic Control Devices . Federal Highway Administration, Washington, D.C., 1986. 25. Turnbull, Katherine F. and James Hanks, Jr., A Description of High-Occupancy Vehicle Facilities in North America . Texas Transportation Institute for the Texas Department of Highways and Public Transportation, July 1990. 89 26. 407 Express Toll Route. URL: January 2000. 27. Worrall, H.W. Central Florida Experiences Significant Benefits from Electronic Toll Collection. Institute of Transportation Engineers Journal, Washington, D.C., 1999. 28. Turner, Shawn. Video Enforcement for HOV Lanes. Field Test Results for the I-30 HOV Lane in Dallas. Report No. FHWA/TX-98/2901-S. Texas Department of Transportation, Texas Transportation Institute, July 1998. 29. Chui, Margaret and William F. McFarland. The Value of Travel Time: New Estimates Developed Using a Speed Choice Model . Transportation Research Record No.1116, 1987. 30. Hau, Timothy. Economic Fundamentals of Road Pricing: A Diagrammatic Analysis . World Bank Policy Research Working Paper Series, WPS 1070. The World Bank, Washington, D.C., December 1992. 31. Josef, Robert R., Edward Regan, and Jerry C. Porter. Estimating Demand and Revenue Potential for Route 91 Express Lanes . ITE compendium of Technical Papers. 1991. 32. Poole, Robert W. and Kenneth Orski . Building
|
{
"page_id": null,
"source": 7320,
"title": "from dpo"
}
|
a Case for HOT Lanes: A New Approach to Reducing Urban Highway Congestion. Reason Public Policy Institute, Policy Study No. 257, 1999. 33. Mekky, Ali. Forecasting Toll Revenues for Fully Electronic Highways Operating Under Transponder and Video Imaging Systems . Transportation Research Board. 1999. 34. Muller, Robert H. “Examining Toll Road Feasibility Studies. ” Public Works Financing .June 1995. 35. Viton, Philip A. “Private Roads. ” Journal of Urban Economics . Vol. 37, pp. 260-289, 1995. 36. Hau, Timothy. Economic Fundamentals of Road Pricing: A Diagrammic Analysis . World Bank Policy Research Working Paper Series, WPS 1070. The World Bank, Washington, D.C., December 1992. 37. I-15 Express Pass Focus Groups conducted for the San Diego Association of Governments. Godbe Research and Analysis. July 1997. 38. Litman, Todd. Using the Revenues from Road Pricing: Economic Efficiency and Equity Considerations . Transportation Research Record No. 1558, TRB National Research Council, Washington, D.C., 1996. 39. Spock, Linda M. Tolling Practices for Highway Facilities. Synthesis of Highway Practice. National Cooperative Highway Research Program Report No. 262. National Research Council, National Academy Press, Washington, D.C., 1998. 90 40. “Exploring Key Issues in Public Private Partnerships for Highway Development: Searching for Solutions. ” A Policy Discussion Series, Number 2. Federal Highway Administration, June 1992. 41. Higgins, Thomas J. “Congestion Pricing: Implementation Considerations. ” Transportation Quarterly , Vol. 48, No. 3. Eno Transportation Foundation, Lansdowne, Virginia, Summer 1994. 42. Horan, Thomas, Lucille Chang, and Grant McMurran. Task 4 and 5: Lane Use and Equity Issues in Congestion Pricing. A Compositional Analysis of Five Corridor Markets in Southern California with an Exploration of the Equity Considerations for High Occupancy (HOT) Lanes. A paper prepared for the Congestion Pricing Research Study sponsored by the U.S. Department of Transportation Federal Highway Administration and the University of Minnesota Hubert Humphrey
|
{
"page_id": null,
"source": 7320,
"title": "from dpo"
}
|
Institute of Public Affairs in cooperation with the Minnesota Department of Transportation. Claremont, California, November 1997. 43. Gomez-Ibanez, Jose A. and Kenneth A. Small. “Road Pricing for Congestion Management: A Survey of International Practice. ” National Cooperative Highway Research Program: Synthesis of Highway Practice No. 210. Transportation Research Board, National Research Council, National Academy Press. Washington, D.C. 1994 44. Van Hattum, David and Maria Zimmerman. Buying Time: A Guidebook for Those Considering Congestion Relief Tolls in Their Communities. State and Local Policy Program, Hubert Humphrey Institute of Public Affairs, University of Minnesota, October 1996. 45. Poole, Jr., Robert W. Bringing Market Forces into America ’s Highway System. Reason Public Policy Foundation, Los Angeles, California, October 1998. 46. Small, Kenneth A. and Jose A. Gomez-Ibanez. Road Pricing for Congestion Management: The Transition from Theory to Practice. Draft for presentation at the Taxation, Resources and Economic Development Conference on Alternative Strategies for Managing Externalities. Lincoln Institute of Land Policy, Cambridge, Massachusetts, September 1994.
|
{
"page_id": null,
"source": 7320,
"title": "from dpo"
}
|
Title: Design Manual M 22-01 June 2006 URL Source: Markdown Content: # Design Policy and Standards Revisions # Design Manual – May /June 2006 Revisions # The Revision starts after page 5 of this document Revision marks are used throughout the manual to highlight content changes. These consist of sidebars, and underlining. Manual users should periodically check the Design Manual Errata web page. They should also report all undocumented errors they believe they have found. General • Review and update references, definitions, titles, & acronyms as appropriate. • The “Documentation” subheadings are revised to direct the reader to the Documentation Check list online. Chapter 141 Project Development Roles and Responsibilities for Projects with Structures May 2006 Revision: • Minor spot revisions made to the narrative and flow chart figure to reference WSDOT’s new Project Management On-Line Guide Chapter 315 Value Engineering May 2006 Revision: • minor spot revisions for punctuation, and: • 315.04 (1) Selection Phase, Page 315-2: Revised preliminary project cost estimate value from $2 million to $5 million (relative to a statement about projects that could have high potential for value improvements through a VE study) Chapter 330 Design Documentation, Approval, and Process Review May 2006 Revision: • Revised to include the use of design criteria of the AASHTO A Policy on Geometric Design of Highways and Streets to justify a deviation from the Design Manual criteria. Chapter 410 Basic Design Level May 2006 Revision: • Revised 410.03 Minor Safety and Minor Preservation Work, to provide guidance on rechannelizing existing intersections to accommodate turning lanes. This further clarifies the previous guidance on intersection channelizaton to ensure greater consistency in the evaluation and treatment of intersection related accidents. This guidance applies to pavement preservation projects. Chapter 430 Modified Design Level May 2006 Revision: • Chapter 430 is revised
|
{
"page_id": null,
"source": 7320,
"title": "from dpo"
}
|
to include Design Manual Supplements dated March 25, 2004 and June 29, 2004. • Stopping Sight Distance revised to use 2001 values with a 2.00 ft object height. • Superelevation rate revised to use the minimum radius equation when existing pavement remains. • Ramp widths revised using AASHTO Exhibit 3-55. • Chapter reformatted to more closely follow the Design Matrices Chapter 520 Design of Pavement Structures May 2006 Revision: • Revised to incorporate Design Manual Supplement “Pavement Type Selection Protocol” previously approved by FHWA on April 18, 2005, and effective May 16, 2005. Chapter 610 Traffic Analysis (previously Highway Capacity) May 2006 Revision: • Complete rewrite of an old chapter; new title • Emphasis on the “what’s” and “how’s” on preparation of TIA (Traffic Impact Analysis) Report • More emphasis added regarding WSDOT involvement with local agencies / developers when their projects affect state highways • Designer is informed chapter no longer covers capacity analysis and directs reader to use the Highway Capacity Manual . Chapter 650 Sight Distance May 2006 Revision: • Revised to incorporate Stopping Sight Distance Design Manual Supplement, which was dated October 9, 2002. • Allow the AASHTO 2-foot object height for stopping sight distance in urban areas. • Adopt the AASHTO 2-foot object height for evaluating existing stopping sight distance. Chapter 700 Roadside Safety May 2006 Revision: • Revised to provide policy on centerline rumble strips. • Numerous minor changes in wording to add clarity. Chapter 720 Impact Attenuators May 2006 Revision: • New design guidance: Figure 720-6 • Selection criteria: Figure 720-5a & 5b • Additional guidance for Work Zone applications • Added two new approved systems: Quest & SCI70GM • Reflection of manufacturer’s update to existing approved system: REACT 350 Wide • Updates to the description, function, foundation, slope, operational characteristics, etc, for
|
{
"page_id": null,
"source": 7320,
"title": "from dpo"
}
|
some systems Chapter 830 Delineation May 2006 Revision: • Changed to bring into conformity with MUTCD & to reflect organizational changes in WSDOT • Chapter rewritten; no revision marks were included Chapter 910 Intersections At Grade May 2006 Revision: • List of information to be included on Intersection Plan was replaced with an internet checklist. • The beginning of the 50-foot opening before the left-turn storage was moved from end of taper to point where 13-foot lane width is achieved. • Corrected chapter errata. • The changes to Chapter 910 expand on the previous guidance related to shoulder widths in intersection areas. The intent is to reduce conflict points, while balancing the needs of motorists, bicyclists, and pedestrians. This guidance applies to all projects designed with Full Design Level. Chapter 960 Median Crossovers May 2006 Revision : Revised to Clarify: • Circumstances that crossings will be considered. • How to apply for approval of new or relocated crossings • Provide additional guidance on the location of crossings Chapter 1010 Auxiliary Lanes May 2006 Revision :• Changed size of truck used to warrant climbing lane to 200 lb/HP • Reduced speed reduction to warrant a climbing lane from ________ to 10 mph • Changed minimum shoulder width for slow vehicle shoulder driving to 10 feet (with 12 feet preferred.) • The above revisions were to match AASHTO Chapter 1025 Pedestrian Design Considerations May 2006 Revision : • Complete rewrite of chapter; no revision marks • Revised to reflect ADA accessibility requirements, changes in WSDOT organizational structure • Several new sections such as: ADA Compliance; Vehicle Bridges and Underpasses; Railroad Crossings; Managing Speed and Flow (Traffic Calming); Work Zone Pedestrian Considerations • Some existing sections revised, including: Funding Program Structure; Pedestrian Human Factors; Pedestrian Activity Generators, which have been removed to the
|
{
"page_id": null,
"source": 7320,
"title": "from dpo"
}
|
document: Understanding Flexibility in Transportation Design – Washington . Chapter 1410 Right of Way Considerations May 2006 Revision : • Updated WSDOT R/W policies and procedures to reflect WSDOT organizational changes. Chapter 1425 Interchange Justification Report (Previously Access Point Decision Report) May 2006 Revision : • Revised chapter; new title; complete rewrite for the most part; no revision marks • Revised to better align with national terminology, and reflect procedural and organizational changes in WSDOT. • New Term: IJR, Old Term: APDR • Renumbered 8 Policy Points to coincide with national convention for IJR format / layout • No change to Policy; simply rewrote to better clarify procedure and documentation products; and extent of documentation needed for various access breaks (from a locked gate to a full blown new interchange.) Chapter 1440 Surveying and Mapping May 2006 Revision : • Revised to bring into conformity with Highway Surveying Manual and to reflect WSDOT organizational changes. Chapter 1450 Monumentation May 2006 Revision: • Provides designer an overview of the placement, protection and replacement of highway control monuments, alignment monuments and control monuments. • Revised to bring into conformity with Highway Surveying Manual. Chapter 1460 Fencing May 2006 Revision: • Revised in two primary areas: fencing of special sites and deletion of two types of chain link fence: • Text on fencing at storm-water detention facilities and wetland mitigation sites has been separated to better reflect requirements for fencing in each case. • Types 1 and 6 chain link fence have been deleted from the chapter. These fence types have top rail. • Justification is required for not taking corrective action to remove Type 1 or 6 within project limits. • Other editorial or clarifying text throughout chapter Publications Transmittal Transmittal Number Date PT 06-032 June 2006 Publication Distribution To: All English
|
{
"page_id": null,
"source": 7320,
"title": "from dpo"
}
|
Design Manual holders Publication Title Publication Number Design Manual (English) Revision 2006-1 M 22-01 Originating Organization Environmental and Engineering Service Center, Design Office, Design Policy, Standards, and Safety Research Unit through Engineering Publications Remarks: Additional copies may be purchased from: Washington State Department of Transportation Finance and Administration Directional Documents and Engineering Publications PO BOX 47408 Olympia, WA 98504-7408 Phone: (360) 705-7430 Fax: (360) 705-6861 E-mail: engrpubs@wsdot.wa.gov Instructions: Page numbers and corresponding sheet-counts are given in the table below to indicate portions of the Design Manual that are to be removed and inserted to accomplish this revision. Remove Insert Chapter Pages Sheets Pages Sheets Letter’s List N/A N/A N/A 1 Contents 1 – 26 13 1 - 26 13 141, “Project Development Roles and Responsibilities for Projects with Structures” 1 - 3 2 1 – 3 2 315, “Value Engineering” 1 – 7 4 1 – 7 4 330, “Design Documentation, Approval, and Process Review” 1 – 16 8 1 – 16 8 410, “Basic Design Level” 1 – 2 1 1 – 2 1 430, “Modified Design Level” 1 – 11 6 1 – 15 8 520, “Design of Pavement Structures” 1 – 2 1 1 – 2 1 610, “Traffic Analysis” previously known as “Highway Capacity” 1 – 6 3 1 – 10 5 650, “Sight Distance” 1 – 9 5 1 – 12 6 700, “Roadside Safety” 1 – 17 9 1 - 18 9 720, “Impact Attenuator Systems” 1 – 16 8 1 – 20 10 830, “Delineation” 1 – 8 4 1 – 10 5 910, “Intersections At Grade” 1 – 14 25 – 28 37 – 38 7 2 1 1 – 14 25 – 28 37 – 38 7 2 1 960, “Median Crossovers” 1 – 2 1 1 – 2 1 1010,
|
{
"page_id": null,
"source": 7320,
"title": "from dpo"
}
|
“Auxiliary Lanes” 1 – 14 7 1 – 14 7 Page 1 of 2 Remove Insert Chapter Pages Sheets Pages Sheets 1025, “Pedestrian Design Considerations” 1 – 19 10 1 – 24 12 1410, “Right of Way Considerations” 1 – 6 3 1 – 6 3 1425, “Interchange Justification Report” previously known as “Access Point Decision Report” 1 – 15 8 1 – 16 8 1440, “Surveying and Mapping” 1 – 5 3 1 – 6 3 1450, “Monumentation” 1 – 8 4 1 – 9 5 1460, “Fencing” 1 – 3 2 1 – 3 2 Index 1 – 18 9 1 – 18 9 Distributed By Phone Number Signature Directional Documents and (360) 705-7430 Engineering Publications FAX: 705-6861 Page 2 of 2 Design Manual M 22-01 Contents Spring 2006 Amendments Washington State Department of Transportation # Design Manual Supplements and Instructional Letters May, 2006 > In Effect Chapter Date Type Subject/Title No 650 10/09/02 DM Supplement Stopping Sight Distance No No 430 440 3/25/2004 DM Supplement Design Speed No No No No 430 1025 325 340 6/29/2004 DM Supplement ADA Accessible Facilities on Road, Street, and Highway Projects Yes 520 5/16/2005 DM Supplement Pavement Type Selection Protocol (PTSP) Yes Yes 820 850 8/5/2005 DM Supplement Overhead Sign Illumination (Lighting) Yes 860 12/30/2005 DM Supplement Systems Engineering for Intelligent Transportation Systems Yes 1120 4/24/2006 DM Supplement Vertical Falsework Clearance for Bridges Over Highways Notes: • Changes since the last revision to the Design Manual are shown in bold print. • Items with No in the In Effect column were superseded by the latest revision and will be dropped from the next printing of this list. • The listed items marked yes have been posted to the web at the following location: Design Manual M 22-01 Contents May 2006
|
{
"page_id": null,
"source": 7320,
"title": "from dpo"
}
|
Page 1 > Date ## Division 1 General Information Chapter 100 Manual Description June 2005 100.01 Purpose 100.02 Presentation and Revisions 100.03 Design Manual Applications 100.04 How the Design Manual is to be Used 100.05 The Project Development Process 100.06 How the Design Manual is Organized Chapter 120 Planning January 2005 120.01 General 120.02 References 120.03 Acronyms and Definitions 120.04 Legislation and Policy Development 120.05 Planning at WSDOT 120.06 Linking Transportation Plans 120.07 Linking WSDOT Planning to Programming Chapter 140 Managing Project Delivery January 2005 140.01 General 140.02 References 140.03 Definitions 140.04 Resources 140.05 Managing Project Delivery 140.06 Responsibilities 140.07 Documentation Chapter 141 Project Development Roles and Responsibilities for Projects with Structures May 2006 141.01 General 141.02 Procedures Chapter 150 Project Development Sequence June 2005 150.01 General 150.02 References 150.03 Definitions 150.04 Project Development Sequence # Contents > Date Contents Design Manual M 22-01 Page 2 May 2006 > Date ## Division 2 Hearings, Environmental, and Permits Chapter 210 Public Involvement and Hearings December 1998 210.01 General 210.02 References 210.03 Definitions 210.04 Public Involvement 210.05 Hearings 210.06 Environmental Hearing 210.07 Corridor Hearing 210.08 Design Hearing 210.09 Access Hearing 210.10 Combined Hearings 210.11 Administrative Appeal Hearing 210.12 Documentation Chapter 220 Project Environmental Documentation June 2005 220.01 Introduction 220.02 References 220.03 Definitions / Acronyms 220.04 Determining the Environmental Documentation 220.05 Identifying the Project Classification 220.06 Environmental Impact Statements – Class I Projects 220.07 Categorical Exclusions – Class II Projects 220.08 Environmental Assessments – Class III Projects 220.09 Reevaluations 220.10 Commitment File 220.11 Documentation Chapter 240 Environmental Permits and Approvals June 2005 240.01 Introduction 240.02 Permits and Approvals 240.03 Project Types and Permits 240.04 Design Process and Permit Interaction ## Division 3 Project Documentation Chapter 315 Value Engineering May 2006 315.01 General 315.02 References 315.03 Definitions 315.04 Procedure 315.05 Documentation Chapter 325 Design
|
{
"page_id": null,
"source": 7320,
"title": "from dpo"
}
|
Matrix Procedures January 2005 325.01 General (325-15 June 2005) 325.02 Selecting a Design Matrix 325.03 Using a Design Matrix Design Manual M 22-01 Contents May 2006 Page > Date Chapter 330 Design Documentation, Approval, and Process Review May 2006 330.01 General 330.02 References 330.03 Definitions 330.04 Design Documentation 330.05 Project Development 330.06 Scoping Phase 330.07 FHWA Approval 330.08 Design Approval 330.09 Process Review Chapter 340 Minor Operational Enhancement Projects June 2005 340.01 General 340.02 References 340.03 Definitions 340.04 Minor Operational Enhancement Matrix Procedures 340.05 Selecting a Minor Operational Enhancement Matrix 340.06 Project Type 340.07 Using a Minor Operational Enhancement Matrix 340.08 Project Approval 340.09 Documentation ## Division 4 Project Design Criteria Chapter 410 Basic Design Level May 2006 410.01 General 410.02 Required Basic Safety Items of Work 410.03 Minor Safety and Minor Preservation Work Chapter 430 Modified Design Level May 2006 430.01 General 430.02 Design Speed 430.03 Alignment 430.04 Roadway Widths 430.05 Cross Slope 430.06 Side Slopes 430.07 Bike and Pedestrian 430.08 Bridges 430.09 Intersections 430.10 Documentation Contents Design Manual M 22-01 Page May 2006 > Date Chapter 440 Full Design Level January 2005 440.01 General 440.02 References 440.03 Definitions 440.04 Functional Classification 440.05 Terrain Classification 440.06 Geometric Design Data 440.07 Design Speed 440.08 Traffic Lanes 440.09 Shoulders 440.10 Medians 440.11 Curbs 440.12 Parking 440.13 Pavement Type 440.14 Structure Width 440.15 Right of Way Width 440.16 Grades 440.17 Documentation ## Division 5 Soils and Paving Chapter 510 Investigation of Soils, Rock, and Surfacing Materials May 2004 510.01 General 510.02 References 510.03 Materials Sources 510.04 Geotechnical Investigation, Design, and Reporting 510.05 Use of Geotechnical Consultants 510.06 Geotechnical Work by Others 510.07 Surfacing Report 510.08 Documentation Chapter 520 Design of Pavement Structure January 2005 520.01 Introduction (520-1 May 2006) 520.02 Estimating Tables Chapter 530 Geosynthetics April 1998 530.01 General (530-11,
|
{
"page_id": null,
"source": 7320,
"title": "from dpo"
}
|
12 and 13 May 2004) 530.02 References 530.03 Geosynthetic Types and Characteristics 530.04 Geosynthetic Function Definitions and Applications 530.05 Design Approach for Geosynthetics 530.06 Design Responsibility 530.07 Documentation Design Manual M 22-01 Contents May 2006 Page > Date ## Division 6 Geometrics Chapter 610 Traffic Analysis May 2006 610.01 General 610.02 References 610.03 Design Year 610.04 Definitions 610.05 Travel Forecasting (Transportation Modeling) 610.06 Traffic Analysis 610.07 Scope of Traffic Impact Analysis 610.08 Traffic Data 610.09 Traffic Impact Analysis Methodologies 610.10 Traffic Analysis Software 610.11 Mitigation Measures 610.12 Traffic Impact Analysis Report Chapter 620 Geometric Plan Elements May 2004 620.01 General (620-1 through 6 January 2005) 620.02 References 620.03 Definitions 620.04 Horizontal Alignment 620.05 Distribution Facilities 620.06 Number of Lanes and Arrangement 620.07 Pavement Transitions 620.08 Procedures 620.09 Documentation Chapter 630 Geometric Profile Elements May 2004 630.01 General 630.02 References 630.03 Vertical Alignment 630.04 Coordination of Vertical and Horizontal Alignments 630.05 Airport Clearance 630.06 Railroad Crossings 630.07 Procedures 630.08 Documentation Chapter 640 Geometric Cross Section January 2005 640.01 General (640-14 June 2005) 640.02 References 640.03 Definitions 640.04 Roadways 640.05 Medians and Outer Separations 640.06 Roadsides 640.07 Roadway Sections 640.08 Documentation Chapter 641 Turning Roadways January 2005 641.01 General 641.02 References 641.03 Definitions 641.04 Turning roadway widths 641.05 Documentation Contents Design Manual M 22-01 Page 6 May 2006 > Date Chapter 642 Superelevation January 2005 642.01 General 642.02 References 642.03 Definitions 642.04 Rates for Open Highways and Ramps 642.05 Rates for Low-Speed Urban Managed Access Highway 642.06 Existing Curves 642.07 Turning Movements at Intersections 642.08 Runoff for Highway Curves 642.09 Runoff for Ramp Curves 642.10 Documentation Chapter 650 Sight Distance May 2006 650.01 General 650.02 References 650.03 Definitions 650.04 Stopping Sight Distance 650.05 Passing Sight Distance 650.06 Decision Sight Distance 650.07 Documentation ## Division 7 Roadside Safety Elements Chapter 700 Roadside
|
{
"page_id": null,
"source": 7320,
"title": "from dpo"
}
|
Safety May 2006 700.01 General 700.02 References 700.03 Definitions 700.04 Clear Zone 700.05 Hazards to Be Considered for Mitigation 700.06 Median Considerations 700.07 Other Roadside Safety Features 700.08 Documentation Chapter 710 Traffic Barriers January 2005 710.01 General 710.02 References 710.03 Definitions 710.04 Project Requirements 710.05 Barrier Design 710.06 Beam Guardrail 710.07 Cable Barrier 710.08 Concrete Barrier 710.09 Special Use Barriers 710.10 Bridge Rails 710.11 Other Barriers 710.12 Documentation Chapter 720 Impact Attenuator Systems May 2006 720.01 Impact Attenuator Systems 720.02 Design Criteria 720.03 Selection 720.04 Documentation Design Manual M 22-01 Contents May 2006 Page > Date ## Division 8 Traffic Safety Elements Chapter 810 Work Zone Traffic Control December 2003 810.01 General 810.02 References 810.03 Public Information 810.04 Work Zone Classification 810.05 Work Zone Types 810.06 Project Definition 810.07 Work Zone Safety 810.08 Regulatory Traffic Control Strategies 810.09 Traffic Control Plans and Devices 810.10 Documentation Chapter 820 Signing November 1999 820.01 General 820.02 References 820.03 Design Components 820.04 Overhead Installation 820.05 Mileposts 820.06 Guide Sign Plan 820.07 Documentation Chapter 830 Delineation May 2006 830.01 General 830.02 References 830.03 Definitions 830.04 Pavement Markings 830.05 Guideposts 830.06 Barrier Delineation 830.07 Object Markers 830.08 Wildlife Warning Reflectors 830.09 Documentation Chapter 840 Illumination December 2003 840.01 General (840-15 and 16 May 2004) 840.02 References 840.03 Definitions 840.04 Required Illumination 840.05 Additional Illumination 840.06 Design Criteria 840.07 Documentation Chapter 850 Traffic Control Signals May 2001 850.01 General (850-15 and 16 May 2004) 850.02 References 850.03 Definitions 850.04 Procedures 850.05 Signal Warrants 850.06 Conventional Traffic Signal Design 850.07 Documentation Contents Design Manual M 22-01 Page May 2006 > Date Chapter 860 Intelligent Transportation Systems November 1999 860.01 General 860.02 References 860.03 Traffic Data Collection 860.04 Traffic Flow Control 860.05 Motorist Information 860.06 Documentation ## Division 9 Interchanges and Intersections Chapter 910 Intersections At Grade
|
{
"page_id": null,
"source": 7320,
"title": "from dpo"
}
|
January 2005 910.01 General (910-1 through 14 May 2006) 910.02 References (910-25 through 28 May 2006) 910.03 Definitions (910-38 May 2006) 910.04 Design Considerations 910.05 Design Vehicle 910.06 Right-Turn Corners 910.07 Channelization 910.08 Roundabouts 910.09 U-Turns 910.10 Sight Distance at Intersections 910.11 Traffic Control at Intersections 910.12 Interchange Ramp Terminals 910.13 Procedures 910.14 Documentation Chapter 915 Roundabouts May 2004 915.01 General (915-8 and 9 January 2005) 915.02 References (915-16 through 18 January 2005) 915.03 Definitions (915-22 January 2005) 915.04 Roundabout Categories 915.05 Capacity Analysis 915.06 Geometric Design 915.07 Pedestrians 915.08 Bicycles 915.09 Signing and Pavement Marking 915.10 Illumination 915.11 Access, Parking, and Transit Facilities 915.12 Procedures 915.13 Documentation Chapter 920 Road Approaches December 2003 920.01 General 920.02 References 920.03 Definitions 920.04 Design Considerations 920.05 Road Approach Design Template 920.06 Sight Distance 920.07 Road Approach Location 920.08 Drainage Requirements 920.09 Procedures 920.10 Documentation Design Manual M 22-01 Contents May 2006 Page > Date Chapter 930 Railroad Grade Crossings January 2005 930.01 General 930.02 References 930.03 Plans 930.04 Traffic Control System s930.05 Pullout Lanes 930.06 Crossing Surfaces 930.07 Crossing Closure 930.08 Traffic Control During Construction and Maintenanc e930.09 Railroad Grade Crossing Petitions and WUTC Orders 930.10 Section 130 Grade Crossing Improvement Projects 930.11 Light Rail 930.12 Documentation Chapter 940 Traffic Interchanges September 2002 940.01 General (940-1 and 2 June 2005) 940.02 References (940-5 January 2005) 940.03 Definitions (940-11 January 2005) 940.04 Interchange Design (940-23 and 24 January 2005) 940.05 Ramps (940-28 January 2005) 940.06 Interchange Connections 940.07 Ramp Terminal Intersections at Crossroads 940.08 Interchanges on Two-Lane Highways 940.09 Interchange Plans 940.10 Documentation Chapter 960 Median Crossovers May 2006 960.01 General 960.02 Analysis 960.03 Design 960.04 Approval 960.05 Documentation ## Division 10 Auxiliary Facilities Chapter 1010 Auxiliary Lanes May 2006 1010.01 General 1010.02 References 1010.03 Definitions 1010.04 Climbing Lanes 1010.05 Passing Lanes
|
{
"page_id": null,
"source": 7320,
"title": "from dpo"
}
|
1010.06 Slow-Moving Vehicle Turnouts 1010.07 Shoulder Driving for Slow Vehicles 1010.08 Emergency Escape Ramps 1010.09 Chain-Up Areas 1010.10 Documentation Contents Design Manual M 22-01 Page 10 May 2006 > Date Chapter 1020 Bicycle Facilities May 2001 1020.01 General (1020-25 and 26 September 2002) 1020.02 References 1020.03 Definitions 1020.04 Planning 1020.05 Design 1020.06 Documentation Chapter 1025 Pedestrian Design Considerations May 2006 1025.01 General 1025.02 References 1025.03 Definitions 1025.04 Policy 1025.05 Pedestrian Facility Design 1025.06 Documentation Chapter 1030 Safety Rest Areas and Traveler Services December 2003 1030.01 General 1030.02 References 1030.03 Documentation Chapter 1040 Weigh Sites May 2000 1040.01 General (1040-5 and 6 May 2004) 1040.02 Definitions 1040.03 Planning, Development, and Responsibilities 1040.04 Permanent Facilities 1040.05 Portable Facilities 1040.06 Shoulder Sites 1040.07 Federal Participation 1040.08 Procedures 1040.09 Documentation Chapter 1050 High Occupancy Vehicle Facilities May 2003 1050.01 General (1050-1, 3, 5 and 9 June 2005) 1050.02 Definitions (1050-10 January 2005) 1050.03 References (1050-12 through 14 January 2005) 1050.04 Preliminary Design and Planning 1050.05 Operations 1050.06 Design Criteria 1050.07 Documentation Chapter 1055 HOV Direct Access June 2005 1055.01 General 1055.02 References 1055.03 Definitions 1055.04 HOV Access Types and Locations 1055.05 Direct Access Geometrics 1055.06 Passenger Access 1055.07 Traffic Design Elements 1055.08 Documentation Design Manual M 22-01 Contents May 2006 Page 11 > Date Chapter 1060 Transit Benefit Facilities December 1991 1060.01 Introduction (1060-14 March 1994) 1060.02 Definitions (1060-16 through 18 March 1994) 1060.03 Park and Ride Lots (1060-19 May 2004) 1060.04 Transfer/Transit Centers (1060-20 through 22 March 1994) 1060.05 Bus Stops and Pullouts (1060-23 and 24 July 1994) 1060.06 Passenger Amenities (1060-25 through 34 March 1994) 1060.07 Roadway and Vehicle (1060-35 and 36 July 1994) Design Criteria Characteristics (1060-37 and 38 March 1994) 1060.08 Intersection Radii 1060.09 Disabled Accessibility 1060.10 References ## Division 11 Structures Chapter 1110 Site Data for Structures December 2003
|
{
"page_id": null,
"source": 7320,
"title": "from dpo"
}
|
1110.01 General 1110.02 References 1110.03 Required Data for All Structures 1110.04 Additional Data for Waterway Crossings 1110.05 Additional Data for Grade Separations 1110.06 Additional Data for Widenings 1110.07 Documentation Chapter 1120 Bridges January 2005 1120.01 General 1120.02 References 1120.03 Bridge Location 1120.04 Bridge Site Design Elements 1120.05 Documentation Chapter 1130 Retaining Walls and Steep Reinforced Slopes May 2003 1130.01 References (1130-22 and 23 December 1998) 1130.02 General (1130-30 December 1998) 1130.03 Design Principles 1130.04 Design Requirements 1130.05 Guidelines for Wall/Slope Selection 1130.06 Design Responsibility and Process 1130.07 Documentation Chapter 1140 Noise Barriers May 2003 1140.01 General 1140.02 References 1140.03 Design 1140.04 Procedures 1140.05 Documentation Contents Design Manual M 22-01 Page 12 May 2006 > Date ## Division 12 Hydraulics Chapter 1210 Hydraulic Design September 2002 1210.01 General 1210.02 References 1210.03 Hydraulic Considerations 1210.04 Safety Considerations 1210.05 Design Responsibility ## Division 13 Roadside Development Chapter 1300 Roadside Development January 2005 1300.01 General 1300.02 References 1300.03 Legal Requirements 1300.04 Roadside Classification Plan 1300.05 Roadside Manual 1300.06 Project Development 1300.07 Documentation Chapter 1310 Contour Grading December 2003 1310.01 General 1310.02 References 1310.03 Procedures 1310.04 Recommendations 1310.05 Documentation Chapter 1320 Vegetation January 2005 1320.01 General 1320.02 References 1320.03 Discussion 1320.04 Design Guidelines 1320.05 Documentation Chapter 1330 Irrigation December 2003 1330.01 General 1330.02 References 1330.03 Design Considerations 1330.04 Documentation Chapter 1350 Soil Bioengineering December 2003 1350.01 General 1350.02 References 1350.03 Uses 1350.04 Design Responsibilities and Considerations 1350.05 Documentation Design Manual M 22-01 Contents May 2006 Page 1 > Date ## Division 14 Right of Way and Access Control Chapter 1410 Right of Way Considerations May 2006 1410.01 General 1410.02 References 1410.03 Special Features 1410.04 Easements and Permits 1410.05 Programming for Funds 1410.06 Appraisal and Acquisition 1410.07 Transactions 1410.08 Documentation Chapter 1420 Access Control December 2003 1420.01 General 1420.02 References 1420.03 Definitions 1420.04 Vocabulary Chapter 1425
|
{
"page_id": null,
"source": 7320,
"title": "from dpo"
}
|
Interchange Justification Report May 2006 1425.01 General 1425.02 References 1425.03 Definitions 1425.04 Procedures 1425.05 Interchange Justification Report and Supporting Analyses 1425.06 Documentation Chapter 1430 Limited Access December 2003 1430.01 General 1430.02 Achieving Limited Access 1430.03 Full Control (Most Restrictive) 1430.04 Partial Control 1430.05 Modified Control (Least Restrictive) 1430.06 Access Approaches 1430.07 Frontage Roads 1430.08 Turnbacks 1430.09 Adjacent Railroads 1430.10 Modifications to Limited Access Highways 1430.11 Documentation Chapter 1435 Managed Access December 2003 1435.01 General 1435.02 Managed Access Classes 1435.03 Corner Clearance Criteria 1435.04 Access Connection Categories 1435.05 Access Connection Permit 1435.06 Permit Process 1435.07 Design Considerations 1435.08 Other Considerations 1435.09 Preconstruction Conference 1435.10 Adjudicative Proceedings 1435.11 Documentation Contents Design Manual M 22-01 Page 1 May 2006 > Figure Number Title Page Last Date Figure Number Title Page Last Date Chapter 1440 Surveying and Mapping May 2006 1440.01 General 1440.02 References 1440.03 Procedures 1440.04 Datums 1440.05 Global Positioning System 1440.06 WSDOT Monument Database 1440.07 Geographic Information System 1440.08 Photogrammetric Surveys 1440.09 Documentation Chapter 1450 Monumentation May 2006 1450.01 General 1450.02 References 1450.03 Definitions 1450.04 Control Monuments 1450.05 Alignment Monuments 1450.06 Property Corners 1450.07 Other Monuments 1450.08 Documentation 1450.09 Filing Requirements Chapter 1460 Fencing May 2006 1460.01 General 1460.02 References 1460.03 Design Criteria 1460.04 Fencing Types 1460.05 Gates 1460.06 Procedure 1460.07 Documentation ## Index May 2006 Design Manual M 22-01 Contents May 2006 Page 1 > Figure Number Title Page Last Date Figure Number Title Page Last Date # Figures > Figure Number Title Page Last Date 120-1 Relationship Between Transportation Plans and Planning Organizations 120-15 January 2005 120-2 Transportation Improvement Programs 120-16 January 2005 120-3 Linking Planning and Programming 120-17 January 2005 140-1 Overlapping Disciplines for Successful Project Delivery 140-1 January 2005 140-2 Project Management Trade-Off Triangle 140-2 January 2005 140-3 Relative Effort 140-3 January 2005 140-4 Steps and Elements 140-4
|
{
"page_id": null,
"source": 7320,
"title": "from dpo"
}
|
January 2005 140-5 Risk Probability – Impact Matrix 140-9 January 2005 140-6 Using MPD Iteratively 140-16 January 2005 141-1a Determination of the Roles and Responsibilities for Projects with Structures (Project Development Phase) 141-2 May 2006 141-1b Determination of the Roles and Responsibilities for Projects with Structures (Project Development Phase) 141-3 May 2006 150-1 Program Elements 150-6 June 2005 150-2 Program Elements 150-7 June 2005 210-1 Sequence for a Hearing 210-16 December 1998 240-1a Permits and Approvals 240-2 June 2005 240-1b Permits and Approvals 240-3 June 2005 240-1c Permits and Approvals 240-4 June 2005 240-1d Permits and Approvals 240-5 June 2005 240-1e Permits and Approvals 240-6 June 2005 240-2 Project Environmental Matrix 1 Permit Probabilities for Interstate Routes (Main Line) 240-9 June 2005 240-3 Project Environmental Matrix 2 Permit Probabilitiy for Interstate Interchange Areas 240-10 June 2005 240-4 Project Environmemtal Matrix 3 Permit Probability for NHS Routes Non-Interstate (Main Line) 240-11 June 2005 240-5 Project Environmental Matrix 4 Interchange Areas, NHS (Except Interstate) and Non-NHS 240-12 June 2005 240-6 Project Environmental Matrix 5 Non-NHS Routes (Main Line) 240-13 June 2005 240-7a Endnotes for Project Environmental Matrices 240-14 June 2005 240-7b Endnotes for Project Environmental Matrices 240-15 June 2005 240-7c Endnotes for Project Environmental Matrices 240-16 June 2005 240-8 Environmental Interrelationship: HMA/PCCP/BST Mainline Overlay 240-18 June 2005 240-9 Environmental Interrelationship: Safety Corridor Channelization Main Line 240-19 June 2005 315-1 Eight-Phase Job Plan for VE Studies 315-5 May 2006 315-2 Request for Value Engineering Study 315-6 May 2006 315-3 VE Study Team Tools 315-7 May 2006 325-1 Design Matrix Selection Guide 325-1 January 2005 325-2a NHS Highways in Washington 325-9 January 2005 325-2b NHS Highways in Washington 325-10 January 2005 Contents Design Manual M 22-01 Page 16 May 2006 > Figure Number Title Page Last Date 325-3 Design Matrix 1 Interstate Routes (Main
|
{
"page_id": null,
"source": 7320,
"title": "from dpo"
}
|
Line) 325-11 January 2005 325-4 Design Matrix 2 Interstate Interchange Areas 325-12 January 2005 325-5 Design Matrix 3 Main Line NHS Routes (Except Interstate) 325-13 January 2005 325-6 Design Matrix 4 Interchange Areas, NHS (Except Interstate) and Non-NHS 325-14 January 2005 325-7 Design Matrix 5 Main Line Non-NHS Routes 325-15 June 2005 330-1 Design Matrix Documentation Requirements 330-5 May 2006 330-2a Design Approval Level 330-9 May 2006 330-2b Design Approval Level 330-10 May 2006 330-3a Approvals 330-11 May 2006 330-3b Approvals 330-12 May 2006 330-4 PS&E Process Approvals 330-13 May 2006 330-5 Common Components of Design Documentation Package 330-14 May 2006 330-6 Deviation and Evaluate Upgrade Request/Documentation Content List 330-15 May 2006 340-1 Minor Operational Enhancement Matrix Selection Guide 340-4 June 2005 340-2 Minor Operational Enhancement Matrix 1 Interstate & NHS Freeway Routes 340-8 June 2005 340-3 Minor Operational Enhancement Matrix 2 NHS Non-freeway Routes 340-9 June 2005 340-4 Minor Operational Enhancement Matrix 3 Non-NHS Routes 340-10 June 2005 340-5a Q Project Design Summary/Approval Template 340-11 June 2005 340-5b Q Project Design Summary/Approval Template (continued) 340-12 June 2005 340-6 Refuge Lane for T-Intersections on 2 Lane Highways 340-13 June 2005 430-1 Desirable Design Speed 430-1 May 2006 430-2 Stopping Sight Distance, Modified Design Level 430-2 May 2006 430-3 Minimum Crest Vertical Curve Length, Modified Design Level 430-3 May 2006 430-4 Minimum Superelevation, Modified Design Level 430-3 May 2006 430-5 Side Friction Factor 430-3 May 2006 430-6 One-Way Roadway and Ramp Turning Roadway Widths, Modified Design Level 430-4 May 2006 430-7 Design Vehicles, Modified Design Level 430-6 May 2006 430-8 Evaluation for Stopping Sight Distance for Crest Vertical Curves, Modified Design Level 430-7 May 2006 430-9a Evaluation for Stopping Sight Distance for Horizontal Curves, Modified Design Level 430-8 May 2006 430-9b Evaluation for Stopping Sight Distance Obstruction for Horizontal Curves, Modified
|
{
"page_id": null,
"source": 7320,
"title": "from dpo"
}
|
Design Level 430-9 May 2006 430-10 Multilane Highways and Bridges, Modified Design Level 430-1 0 May 2006 430-11 Two-Lane Highways and Bridges, Modified Design Level 430-1 1 May 2006 430-12a Minimum Total Roadway Widths for Two-Lane Two-Way Highway Curves, Modified Design Level 430-1 2 May 2006 430-12b Minimum Total Roadway Widths for Two-Lane Two-Way Highway Curves, Modified Design Level 430-1 3 May 2006 430-13 Main Line Roadway Sections, Modified Design Level 430-1 4 May 2006 430-14 Ramp Roadway Sections, Modified Design Level 430-1 5 May 2006 Design Manual M 22-01 Contents May 2006 Page 1 > Figure Number Title Page Last Date 440-1 Desirable Design Speed 440-5 January 2005 440-2 Minimum Shoulder Width 440-6 January 2005 440-3 Shoulder Width for Curbed Sections 440-7 January 2005 440-4 Geometric Design Data, Interstate 440-11 January 2005 440-5a Geometric Design Data, Principal Arterial 440-12 January 2005 440-5b Geometric Design Data, Principal Arterial 440-13 January 2005 440-6a Geometric Design Data, Minor Arterial 440-14 January 2005 440-6b Geometric Design Data, Minor Arterial 440-15 January 2005 440-7a Geometric Design Data, Collector 440-16 January 2005 440-7b Geometric Design Data, Collector 440-17 January 2005 440-8 Geometric Design Data, Urban Managed Access Highways 440-18 January 2005 510-1 Material Source Development Plan 510-15 May 2004 520-1 Estimating – Miscellaneous Tables 520-2 January 2005 520-2a Estimating – Hot Mix Asphalt Pavement and Asphalt Distribution Tables 520-3 January 2005 520-2b Estimating –Asphalt Distribution Tables 520-4 January 2005 520-3 Estimating – Bituminous Surface Treatment 520-5 January 2005 520-4 Estimating – Base and Surfacing Typical Section Formulae and Example 520-6 January 2005 520-5a Estimating - Base and Surfacing Quantities 520-7 January 2005 520-5b Estimating - Base and Surfacing Quantities 520-8 January 2005 520-5c Estimating - Base and Surfacing Quantities 520-9 January 2005 520-5d Estimating - Base and Surfacing Quantities 520-10 January 2005 520-5e Estimating -
|
{
"page_id": null,
"source": 7320,
"title": "from dpo"
}
|
Base and Surfacing Quantities 520-11 January 2005 520-5f Estimating - Base and Surfacing Quantities 520-12 January 2005 520-5g Estimating - Base and Surfacing Quantities 520-13 January 2005 520-5h Estimating - Base and Surfacing Quantities 520-14 January 2005 530-1 Selection Criteria for Geotextile Class 530-3 April 1998 530-2 Maximum Sheet Flow Lengths for Silt Fences 530-8 April 1998 530-3 Maximum Contributing Area for Ditch and Swale Applications 530-8 April 1998 530-4 Design Process for Drainage and Erosion Control Geotextiles and Nonstandard Applications 530-12 May 2004 530-5 Design Process for Separation, Soil Stabilization, and Silt Fence 530-13 May 2004 530-6a Examples of Various Geosynthetics 530-14 April 1998 530-6b Examples of Various Geosynthetics 530-15 April 1998 530-7a Geotextile Application Examples 530-16 April 1998 530-7b Geotextile Application Examples 530-17 April 1998 530-7c Geotextile Application Examples 530-18 April 1998 530-7d Geotextile Application Examples 530-19 April 1998 530-8 Definition of Slope Length 530-20 April 1998 530-9 Definition of Ditch or Swale Storage Length and Width 530-21 April 1998 530-10 Silt Fences for Large Contributing Area 530-22 April 1998 530-11 Silt Fence End Treatment 530-23 April 1998 530-12 Gravel Check Dams for Silt Fences 530-24 April 1998 Contents Design Manual M 22-01 Page 1 May 2006 > Figure Number Title Page Last Date 610-1 Measures of Effectiveness by Facility Type 610-4 May 2006 620-1 Maximum Angle Without Curve 620-3 January 2005 620-2a Alignment Examples 620-6 January 2005 620-2b Alignment Examples 620-7 May 2004 620-2c Alignment Examples 620-8 May 2004 630-1 Grade Length 630-3 May 2004 630-2a Coordination of Horizontal and Vertical Alignments 630-5 May 2004 630-2b Coordination of Horizontal and Vertical Alignments 630-6 May 2004 630-2c Coordination of Horizontal and Vertical Alignments 630-7 May 2004 630-3 Grading at Railroad Crossings 630-8 May 2004 640-1 Divided Highway Roadway Sections 640-7 January 2005 640-2 Undivided Multilane Highway Roadway Sections
|
{
"page_id": null,
"source": 7320,
"title": "from dpo"
}
|
640-8 January 2005 640-3 Two-Lane Highway Roadway Sections 640-9 January 2005 640-4a Ramp Roadway Sections 640-10 January 2005 640-4b Ramp Roadway Sections 640-11 January 2005 640-5a Shoulder Details 640-12 January 2005 640-5b Shoulder Details 640-13 January 2005 640-6a Divided Highway Median Sections 640-14 June 2005 640-6b Divided Highway Median Sections 640-15 January 2005 640-6c Divided Highway Median Sections 640-16 January 2005 640-7a Roadway Sections in Rock Cuts, Design A 640-17 January 2005 640-7b Roadway Sections in Rock Cuts, Design B 640-18 January 2005 640-8 Roadway Sections With Stepped Slopes 640-19 January 2005 640-9a Bridge End Slopes 640-20 January 2005 640-9b Bridge End Slopes 640-21 January 2005 641-1a Traveled Way Width for Two-Lane Two-Way Turning Roadways 641-3 January 2005 641-1b Traveled Way Width for Two-Lane Two-Way Turning Roadways 641-4 January 2005 641-2a Traveled Way Width for Two-Lane One-Way Turning Roadways 641-5 January 2005 641-2b Traveled Way Width for Two-Lane One-Way Turning Roadways 641-6 January 2005 641-3a Traveled Way Width for One-Lane Turning Roadways 641-7 January 2005 641-3b Traveled Way Width for One-Lane Turning Roadways 641-8 January 2005 641-3c Traveled Way Width for One-Lane Turning Roadways 641-9 January 2005 642-1 Minimum Radius for Normal Crown Section 642-2 January 2005 642-2 Side Friction Factor 642-3 January 2005 642-3a Superelevation Rates (10% max) 642-5 January 2005 642-3b Superelevation Rates (6% max) 642-6 January 2005 642-3c Superelevation Rates (8% max) 642-7 January 2005 642-4 Superelevation Rates for Low-Speed Urban Managed Access Highways 642-8 January 2005 642-5a Superelevation Transitions for Highway Curves 642-9 January 2005 642-5b Superelevation Transitions for Highway Curves 642-10 January 2005 642-5c Superelevation Transitions for Highway Curves 642-11 January 2005 642-5d Superelevation Transitions for Highway Curves 642-12 January 2005 642-5e Superelevation Transitions for Highway Curves 642-13 January 2005 Design Manual M 22-01 Contents May 2006 Page 1 > Figure Number Title Page Last
|
{
"page_id": null,
"source": 7320,
"title": "from dpo"
}
|
Date 642-6a Superelevation Transitions for Ramp Curves 642-14 January 2005 642-6b Superelevation Transitions for Ramp Curves 642-15 January 2005 650-1 Design Stopping Sight Distance 650-2 May 2006 650-2 Design Stopping Sight Distance on Grades 650-2 May 2006 650-3 Stopping Sight Distance on Grades 650-3 May 2006 650-4 Sight Distance, Crest Vertical Curve 650-3 May 2006 650-5 Sight Distance, Sag Vertical Curve 650-4 May 2006 650-6 Sight Distance Area on Horizontal Curves 650-4 May 2006 650-7 Sight Distance, Horizontal Curves 650-4 May 2006 650-8 Existing Stopping Sight Distance 650-5 May 2006 650-9 Passing Sight Distance 650-6 May 2006 650-10 Decision Sight Distance 650-7 May 2006 650-11 Stopping Sight Distance for Crest Vertical Curves 650-8 May 2006 650-12 Stopping Sight Distance for Sag Vertical Curves 650-9 May 2006 650-13a Horizontal Stopping Sight Distance 650-10 May 2006 650-13b Horizontal Stopping Sight Distance 650-11 May 2006 650-14 Passing Sight Distance for Crest Vertical Curves 650-12 May 2006 700-1 Design Clear Zone Distance Table 700-11 May 2006 700-2a Design Clear Zone Inventory Form 700-12 May 2006 700-2b Design Clear Zone Inventory Form 700-13 May 2006 700-3 Recovery Area 700-14 May 2006 700-4 Design Clear Zone for Ditch Sections 700-15 May 2006 700-5 Guidelines for Embankment Barrier 700-16 May 2006 700-6 Mailbox Location and Turnout Design 700-17 May 2006 700-7 Glare Screens 700-18 May 2006 710-1 Type 7 Bridge Rail Upgrade Criteria 710-4 January 2005 710-2 Longitudinal Barrier Deflection 710-5 January 2005 710-3 Longitudinal Barrier Flare Rates 710-6 January 2005 710-4 Traffic Barrier Locations on Slopes 710-8 January 2005 710-5 Old Type 3 Anchor 710-11 January 2005 710-6 Guardrail Connections 710-12 January 2005 710-7 Concrete Barrier Shapes 710-14 January 2005 710-8 Concrete Barrier Placement Guidance (Assessing Impacts to Wildlife) 710-17 January 2005 710-9 Safety Shaped Concrete Bridge Rail Retrofit 710-19 January 2005 710-10 Transitions and Connections
|
{
"page_id": null,
"source": 7320,
"title": "from dpo"
}
|
710-20 January 2005 710-11a Barrier Length of Need 710-21 January 2005 710-11b Barrier Length of Need 710-22 January 2005 710-11c Barrier Length of Need on Curves 710-23 January 2005 710-11d W-Beam Guardrail Trailing End Placement for Divided Highways 710-24 January 2005 710-12 Beam Guardrail Post Installation 710-25 January 2005 710-13 Beam Guardrail Terminals 710-26 January 2005 710-14 Cable Barrier Locations on Slopes 710-27 January 2005 710-15 Thrie Beam Rail Retrofit Criteria 710-2 8 January 2005 Contents Design Manual M 22-01 Page 20 May 2006 > Figure Number Title Page Last Date 720-1 Impact Attenuator Sizes 720-7 May 2006 720-2a Impact Attenuator Systems – Permanent Installations 720-9 May 2006 720-2b Impact Attenuator Systems – Permanent Installations 720-10 May 2006 720-2c Impact Attenuator Systems – Permanent Installations 720-11 May 2006 720-2d Impact Attenuator Systems – Permanent Installations 720-12 May 2006 720-2e Impact Attenuator Systems – Permanent Installations 720-13 May 2006 720-3a Impact Attenuator Systems – Work Zone Installations 720-14 May 2006 720-3b Impact Attenuator Systems – Work Zone Installations 720-15 May 2006 720-4a Impact Attenuator Systems – Older Systems 720-16 May 2006 720-4b Impact Attenuator Systems – Older Systems 720-17 May 2006 720-5a Impact Attenuator Comparison 720-18 May 2006 720-5b Impact Attenuator Comparison 720-19 May 2006 720-6 Impact Attenuator Distance Beyond Length of Need 720-20 May 2006 810-1a Work Zone Types 810-13 December 2003 810-1b Work Zone Types 810-14 December 2003 810-1c Work Zone Types 810-15 December 2003 810-2a Sign Placement — Rural Areas 810-16 December 2003 810-2b Sign Placement — Urban Areas 810-17 December 2003 810-3 Channelization Devices 810-18 December 2003 810-4 Barricade Types 810-19 December 2003 810-5 Barrier Delineators 810-20 December 2003 820-1a Sign Support Locations 820-5 November 1999 820-1b Sign Support Locations 820-6 November 1999 820-2 Wood Posts 820-7 November 1999 820-3 Steel Posts 820-8 November 1999 820-4 Laminated
|
{
"page_id": null,
"source": 7320,
"title": "from dpo"
}
|
Wood Box Posts 820-9 November 1999 830-1 Pavement Marking Material Guide 830-9 May 2006 830-2 Guidepost Placement 830-10 May 2006 840-1 Freeway Lighting Applications 840-9 December 2003 840-2 Freeway Lighting Applications 840-10 December 2003 840-3 Roadway Lighting Applications 840-11 December 2003 840-4 Roadway Lighting Applications 840-12 December 2003 840-5 Roadway Lighting Applications 840-13 December 2003 840-6 Light Levels and Uniformity Ratios 840-14 December 2003 840-7 Light Standard Locations 840-15 May 2004 840-8 Luminaire Wattage, Lumens, and Mounting Heights 840-16 May 2004 850-1 Signal Display Maximum Heights 850-13 May 2001 850-2 Signal Display Areas 850-14 May 2001 850-3 Responsibility for Facilities 850-17 May 2001 850-4 Standard Intersection Movements and Head Numbers 850-18 May 2001 850-5 Phase Diagrams-Four Way Intersections 850-19 May 2001 850-6 Turn Lane Configuration Preventing Concurrent Phasing Double Left Turn Channelization 850-20 May 2001 850-7 Railroad Preemption Phasing 850-21 May 2001 850-8a Pedestrian Push Button Locations 850-22 May 2001 850-8b Pedestrian Push Button Locations 850-23 May 2001 850-9 Dilemma Zone Loop Placement 850-24 May 2001 Design Manual M 22-01 Contents May 2006 Page 21 > Figure Number Title Page Last Date 850-10 Railroad Queue Clearance 850-25 May 2001 850-11a Intersections With Railroad Crossings 850-26 May 2001 850-11b Intersections With Railroad Crossings 850-27 May 2001 850-12a Traffic Signal Display Placements 850-28 May 2001 850-12b Traffic Signal Display Placements 850-29 May 2001 850-12c Traffic Signal Display Placements 850-30 May 2001 850-12d Traffic Signal Display Placements 850-31 May 2001 850-12e Traffic Signal Display Placements 850-32 May 2001 850-13 Mast Arm Signal Moment and Foundation Depths 850-33 May 2001 850-14a Strain Pole and Foundation Selection Procedure 850-34 May 2001 850-14b Strain Pole and Foundation Selection Procedure 850-35 May 2001 850-15 Strain Pole and Foundation Selection Example 850-36 May 2001 850-16 Conduit and Conductor Sizes 850-37 May 2001 910-1 Intersection Area 910-2 May 2006
|
{
"page_id": null,
"source": 7320,
"title": "from dpo"
}
|
910-2 Design Vehicle Types 910-4 May 2006 910-3 Intersection Design Vehicle 910-5 May 2006 910-4 Left-Turn Storage With Trucks (ft) 910-7 May 2006 910-5 U-Turn Spacing 910-11 May 2006 910-6a Turning Path Template 910-15 January 2005 910-6b Turning Path Template 910-16 January 2005 910-6c Turning Path Template 910-17 January 2005 910-7 Right-Turn Corner 910-18 January 2005 910-8a Left-Turn Storage Guidelines (Two-Lane, Unsignalized) 910-19 January 2005 910-8b Left-Turn Storage Guidelines (Four-Lane, Unsignalized) 910-20 January 2005 910-9a Left-Turn Storage Length (Two-Lane, Unsignalized) 910-21 January 2005 910-9b Left-Turn Storage Length (Two-Lane, Unsignalized) 910-22 January 2005 910-9c Left-Turn Storage Length (Two-Lane, Unsignalized) 910-23 January 2005 910-10a Median Channelization (Widening) 910-24 January 2005 910-10b Median Channelization (Median Width 11 ft or more) 910-25 May 2006 910-10c Median Channelization (Median Width 23 ft to 26 ft) 910-26 May 2006 910-10d Median Channelization (Median Width of More Than 26 ft) 910-27 May 2006 910-10e Median Channelization (Minimum Protected Storage) 910-28 May 2006 910-10f Median Channelization (Two-way Left-Turn Lane) 910-29 January 2005 910-11 Right-Turn Lane Guidelines 910-30 January 2005 910-12 Right-Turn Pocket and Right-Turn Taper 910-31 January 2005 910-13 Right-Turn Lane 910-32 January 2005 910-14 Acceleration Lane 910-33 January 2005 910-15a Traffic Island Designs 910-3 4 January 2005 910-15b Traffic Island Designs (Compound Curve) 910-3 5 January 2005 910-15c Traffic Island Designs 910-3 6 January 2005 910-16 U-Turn Locations 910-37 January 2005 910-17a Sight Distance at Intersections 910-38 May 2006 910-17b Sight Distance at Intersections 910-39 January 2005 910-18 Interchange Ramp Details 910-40 January 2005 915-1 Roundabout Elements 915-3 May 2004 915-2 Entry Angle 915-4 May 2004 915-3 Turning Radius (R) 915-5 May 2004 Contents Design Manual M 22-01 Page 22 May 2006 > Figure Number Title Page Last Date 915-4 Approach Leg Alignment 915-8 January 2005 915-5 Deflection 915-9 January 2005 915-6 Stopping Sight Distance for Roundabouts
|
{
"page_id": null,
"source": 7320,
"title": "from dpo"
}
|
915-11 May 2004 915-7 Roundabout Categories Design Characteristics 915-17 January 2005 915-8 Approximate Entry Capacity 915-18 January 2005 915-9a Deflection Path 915-19 May 2004 915-9b Deflection Path 915-20 May 2004 915-10 Deflection Path Radius 915-21 May 2004 915-11 Entry and Exit 915-22 January 2005 915-12 Path Overlap 915-23 May 2004 915-13 Roundabout Intersection Sight Distance 915-24 May 2004 915-14 Central Island 915-25 May 2004 915-15 Splitter Island 915-26 May 2004 915-16 Shared Use Sidewalk 915-27 May 2004 915-17 Roundabout Signing 915-28 May 2004 915-18 Roundabout Illumination 915-29 May 2004 920-1 Road Approach Design Templates 920-2 December 2003 920-2 Road Approach Access Category 920-2 December 2003 920-3 Road Approach Design Template A1 920-5 December 2003 920-4 Road Approach Design Templates B1 and C1 920-6 December 2003 920-5 Road Approach Design Template D1 920-7 December 2003 920-6 Road Approach Sight Distance 920-8 December 2003 930-1 Sight Distance at Railroad Crossing 930-3 January 2005 930-2 Sight Distance at Railroad Crossing 930-3 January 2005 930-3 Typical Pullout Lane at Railroad Crossing 930-5 January 2005 940-1 Ramp Design Speed 940-5 January 2005 940-2 Maximum Ramp Grade 940-5 January 2005 940-3 Ramp Widths (ft) 940-5 January 2005 940-4 Basic Interchange Patterns 940-12 September 2002 940-5 Minimum Ramp Connection Spacing 940-13 September 2002 940-6a Lane Balance 940-14 September 2002 940-6b Lane Balance 940-15 September 2002 940-7 Main Line Lane Reduction Alternatives 940-16 September 2002 940-8 Acceleration Lane Length 940-17 September 2002 940-9a On-Connection (Single-Lane, Taper Type) 940-18 September 2002 940-9b On-Connection (Single-Lane, Parallel Type) 940-19 September 2002 940-9c On-Connection (Two-Lane, Parallel Type) 940-20 September 2002 940-9d On-Connection (Two-Lane, Taper Type) 940-21 September 2002 940-10 Deceleration Lane Length 940-22 September 2002 940-11a Gore Area Characteristics 940-23 January 2005 940-11b Gore Area Characteristics 940-24 January 2005 940-12a Off-Connection (Single-Lane, Taper Type) 940-25 September 2002 940-12b Off-Connection (Single-Lane, Parallel Type)
|
{
"page_id": null,
"source": 7320,
"title": "from dpo"
}
|
940-26 September 2002 940-12c Off-Connection (Single-Lane, One-Lane Reduction) 940-27 September 2002 940-12d Off-Connection (Two-Lane, Taper Type) 940-28 January 2005 940-12e Off-Connection (Two-Lane, Parallel Type) 940-29 September 2002 940-13a Collector Distributor (Outer Separations) 940-30 September 2002 Design Manual M 22-01 Contents May 2006 Page 2 > Figure Number Title Page Last Date 940-13b Collector Distributor (Off-Connections) 940-31 September 2002 940-13c Collector Distributor (On-Connections) 940-32 September 2002 940-14 Loop Ramps Connections 940-33 September 2002 940-15 Length of Weaving Sections 940-34 September 2002 940-16 Temporary Ramps 940-35 September 2002 940-17 Interchange Plan 940-36 September 2002 1010-1 Rolling Resistance (R) 1010-5 May 2006 1010-2a Speed Reduction Warrant (Performance for Trucks) 1010-6 May 2006 1010-2b Speed Reduction Warrant (Example) 1010-7 May 2006 1010-3 Level of Service Warrant - Multilane 1010-8 May 2006 1010-4 Auxiliary Climbing Lane 1010-9 May 2006 1010-5 Warrant for Passing Lanes 1010-10 May 2006 1010-6 Auxiliary Passing Lane 1010-11 May 2006 1010-7 Slow-Moving Vehicle Turnout 1010-12 May 2006 1010-8 Typical Emergency Escape Ramp 1010-13 May 2006 1010-9 Chain Up/Chain Off Area 1010-1 4 May 2006 1020-1 Shared Use Path 1020-3 May 2001 1020-2 Bike Lane 1020-4 May 2001 1020-3 Shared Roadway 1020-4 May 2001 1020-4 Signed Shared Roadway (Designated Bike Route) 1020-5 May 2001 1020-5 Obstruction Marking 1020-8 May 2001 1020-6 Midblock Type Shared Use Path Crossing 1020-9 May 2001 1020-7 Typical Redesign of a Diagonal Midblock Crossing 1020-10 May 2001 1020-8 Adjacent Shared Use Path Intersection 1020-11 May 2001 1020-9 Railroad Crossing for Shared Used Path 1020-12 May 2001 1020-10 Bicycle Design Speeds 1020-13 May 2001 1020-11 Bikeway Curve Widening 1020-13 May 2001 1020-12 R Values and Subsurfacing Needs 1020-14 May 2001 1020-13 Two-Way Shared Use Path on Separate Right of Way 1020-18 May 2001 1020-14 Two-Way Shared Use Path Adjacent to Roadway 1020-19 May 2001 1020-15 Typical Bike Lane Cross
|
{
"page_id": null,
"source": 7320,
"title": "from dpo"
}
|
Sections 1020-20 May 2001 1020-16 Bikeways on Highway Bridges 1020-21 May 2001 1020-17 Refuge Area 1020-22 May 2001 1020-18 At-Grade Railroad Crossings 1020-23 May 2001 1020-19 Stopping Sight Distance 1020-24 May 2001 1020-20 Sight Distance for Crest Vertical Curves 1020-25 September 2002 1020-21 Lateral Clearance on Horizontal Curves 1020-26 September 2002 1020-22 Typical Bicycle/Auto Movements at Intersection of Multilane Streets 1020-27 May 2001 1020-23a Bicycle Crossing of Interchange Ramp 1020-28 May 2001 1020-23b Bicycle Crossing of Interchange Ramp 1020-29 May 2001 1020-24 Bike Lanes Approaching Motorists’ Right-Turn-Only Lanes 1020-30 May 2001 1020-25 Typical Pavement Marking for Bike Lane on Two-Way Street 1020-31 May 2001 1020-26 Typical Bike Lane Pavement Markings at T-Intersections 1020-32 May 2001 Contents Design Manual M 22-01 Page 2 May 2006 > Figure Number Title Page Last Date 1025-1 Walking Trail Guidelines 1025-6 May 2006 1025-2 ADA Requirements 1025-14 May 2006 1025-3a Pedestrian Walkways 1025-15 May 2006 1025-3b Pedestrian Walkways 1025-16 May 2006 1025-4 Sidewalk Recommendations 1025-17 May 2006 1025-5 Marked Crosswalk Recommendations at Unsignalized Crossings 1025-18 May 2006 1025-6 Crosswalk Locations 1025-19 May 2006 1025-7a Sight Distance at Intersections 1025-20 May 2006 1025-7b Sight Distance at Intersections 1025-21 May 2006 1025-8 Curb Extension 1025-22 May 2006 1025-9 Midblock Pedestrian Crossing 1025-23 May 2006 1025-10 Sidewalk Ramp Drainage 1025-24 May 2006 1030-1 Typical Truck Storage 1030-2 December 2003 1030-2 Typical Single RV Dump Station Layout 1030-3 December 2003 1030-3 Typical Two RV Dump Station Layout 1030-4 December 2003 1040-1 Truck Weigh Site (Multilane Highways) 1040-6 May 2004 1040-2 Truck Weigh Site (Two Lane Highways) 1040-7 May 2000 1040-3 Vehicle Inspection Installation 1040-8 May 2000 1040-4 Minor Portable Scale Site 1040-9 May 2000 1040-5 Major Portable Scale Site 1040-10 May 2000 1040-6 Small Shoulder Site 1040-11 May 2000 1040-7 Large Shoulder Site 1040-12 May 2000 1040-8a MOU Related
|
{
"page_id": null,
"source": 7320,
"title": "from dpo"
}
|
to Vehicle Weighing and Equipment Inspection Facilities on State Highways 1040-13 May 2000 1040-8b MOU Related to Vehicle Weighing and Equipment Inspection Facilities on State Highways 1040-14 May 2000 1040-8c MOU Related to Vehicle Weighing and Equipment Inspection Facilities on State Highways 1040-15 May 2000 1040-8d MOU Related to Vehicle Weighing and Equipment Inspection Facilities on State Highways 1040-16 May 2000 1040-8e MOU Related to Vehicle Weighing and Equipment Inspection Facilities on State Highways 1040-17 May 2000 1050-1 Minimum Traveled Way Widths for Articulated Buses 1050-8 May 2003 1050-2 Typical HOV Lane Sections 1050-11 May 2003 1050-3 Roadway Widths for Two-Lane Ramps with an HOV Lane 1050-12 January 2005 1050-4a Single-Lane Ramp Meter With HOV Bypass 1050-13 January 2005 1050-4b Two-Lane Ramp Meter With HOV Bypass 1050-14 January 2005 1050-5a Enforcement Area (One Direction Only) 1050-15 May 2003 1050-5b Enforcement Area (Median) 1050-16 May 2003 1055-1 Minimum Ramp Widths for Articulated Buses 1055-6 June 2005 1055-2 Gap Acceptance Length for Parallel On-Connections 1055-7 June 2005 1055-3 Drop Ramp 1055-11 June 2005 1055-4 T Ramp 1055-12 June 2005 1055-5 Flyover Ramp 1055-13 June 2005 1055-6 Side Platform Flyer Stop 1055-14 June 2005 1055-7 At-Grade Crossing Flyer Stop 1055-15 June 2005 1055-8 Transit Stops at Ramps 1055-16 June 2005 Design Manual M 22-01 Contents May 2006 Page 2 > Figure Number Title Page Last Date 1055-9 Other Transit Stops 1055-17 June 2005 1055-10 Single Lane Parallel On-Connection 1055-18 June 2005 1055-11 HOV Direct Access Acceleration Lane Length 1055-19 June 2005 1055-12 Single Lane Parallel Off-Connection 1055-20 June 2005 1055-13 Drop Ramp Gore Area Characteristics 1055-21 June 2005 1055-14 Deceleration Lane Length for Buses 1055-22 June 2005 1055-15 T Ramp Design 1055-23 June 2005 1055-16 Flyer Stop Signing 1055-24 June 2005 1055-17a HOV Direct Access Signing 1055-25 June 2005 1055-17b HOV Direct Access
|
{
"page_id": null,
"source": 7320,
"title": "from dpo"
}
|
Signing 1055-26 June 2005 1060-1 M Bus Berth Designs 1060-14 March 1994 1060-2 Transit Center Sawtooth Bus Berth Design Example 1060-15 December 1991 1060-3 M Bus Turnout Transfer Center 1060-16 March 1994 1060-4 M Off-Street Transfer Center 1060-17 March 1994 1060-5 M Minimum Bus Zone Dimensions 1060-18 March 1994 1060-6 M Bus Stop Pullouts, Arterial Streets 1060-19 May 2004 1060-7 M Minimum Bus Zone and Pullout after Right Turn Dimensions 1060-20 March 1994 1060-8 M Shelter Siting 1060-21 March 1994 1060-9 M Typical Bus Shelter Design 1060-22 March 1994 1060-10 M Design Vehicle Turning Movements 1060-23 July 1994 1060-11 M Turning Template for Articulated Bus 1060-24 July 1994 1060-12 M Intersection Design 1060-25 March 1994 1060-13 M Cross-Street Width Occupied by Turning Vehicle for Various Angles of Intersection and Curb Radii 1060-26 March 1994 1060-1 Bus Berth Designs 1060-27 March 1994 1060-3 Bus Turnout Transfer Center 1060-28 March 1994 1060-4 Off-Street Transfer Center 1060-29 March 1994 1060-5 Minimum Bus Zone Dimensions 1060-30 March 1994 1060-6 Bus Stop Pullouts, Arterial Streets 1060-31 March 1994 1060-7 Minimum Bus Zone and Pullout after Right Turn Dimensions 1060-32 March 1994 1060-8 Shelter Siting 1060-33 March 1994 1060-9 Typical Bus Shelter Design 1060-34 March 1994 1060-10 Design Vehicle Turning Movements 1060-35 July 1994 1060-11 Turning Template for Articulated Bus 1060-36 July 1994 1060-12 Intersection Design 1060-37 March 1994 1060-13 Cross-Street Width Occupied by Turning Vehicle for Various Angles of Intersection and Curb Radii 1060-38 March 1994 1110-1 Bridge Site Data Check List 1110-5 December 2003 1120-1 Bridge Vertical Clearances 1120-4 January 2005 1120-2a Railroad Vertical Clearance for New Bridge Construction 1120-6 January 2005 1120-2b Railroad Vertical Clearance for Existing Bridge Modifications 1120-7 January 2005 1120-3 Embankment Slope at Bridge Ends 1120-8 January 2005 1130-1a Typical Mechanically Stabilized Earth Gravity Walls 1130-22 December 1998 1130-1b Typical
|
{
"page_id": null,
"source": 7320,
"title": "from dpo"
}
|
Prefabricated Modular Gravity Walls 1130-23 December 1998 Contents Design Manual M 22-01 Page 26 May 2006 > Figure Number Title Page Last Date 1130-1c Typical Rigid Gravity, Semigravity Cantilever, Nongravity Cantilever, and Anchored Walls 1130-24 May 2003 1130-1d Typical Rockery and Reinforced Slope 1130-25 May 2003 1130-2 MSE Wall Drainage Detail 1130-26 May 2003 1130-3 Retaining Walls With Traffic Barriers 1130-27 May 2003 1130-4a Retaining Wall Design Process 1130-28 May 2003 1130-4b Retaining Wall Design Process — Proprietary 1130-29 May 2003 1130-5 Retaining Wall Bearing Pressure 1130-30 December 1998 1140-1 Standard Noise Wall Types 1140-3 May 2003 1300-1 Funding Source Determines Extent of Restoration 1300-1 January 2005 1350-1 Soil Bioengineering Design 1350-3 December 2003 1410-1 Appraisal and Acquisition 1410-6 May 2006 1425-1 Interstate Routes – Interchange Justification Report Content and Review Levels 1425-12 May 2006 1425-2 Non-Interstate – Interchange Justification Report Content and Review Levels 1425-13 May 2006 1425-3 Interchange Justification Report Possibly Not Required 1425-1 4 May 2006 1425-4 Interchange Justification Report Process Flow Chart 1425-1 5 May 2006 1430-1a Full Access Control Limits - Interchange 1430-15 December 2003 1430-1b Full Access Control Limits - Interchange 1430-16 December 2003 1430-1c Full Access Control Limits - Interchange 1430-17 December 2003 1430-2 Full Access Control Limits - Ramp Terminal With Transition Taper 1430-18 December 2003 1430-3 Full Access Control Limits - Single Point Urban Interchange 1430-19 December 2003 1430-4 Partial Access Control Limits - At-Grade Intersections 1430-20 December 2003 1430-5 Partial and Modified Access Control Limits - Roundabout Intersections 1430-21 December 2003 1430-6 Modified Access Control Limits - Intersections 1430-22 December 2003 1435-1 Minimum Corner Clearance 1435-6 December 2003 1435-2 Minimum Corner Clearance: Distance From Access Connection to Intersections 1435-7 December 2003 1435-3 Managed Access Highway Class Description 1435-14 December 2003 1440-1a Interagency Agreement 1440-4 May 2006 1440-1b Interagency Agreement 1440-5
|
{
"page_id": null,
"source": 7320,
"title": "from dpo"
}
|
May 2006 1440-2 Report of Survey Mark 1440-6 May 2006 1450-1 Monument Documentation Summary 1450-5 May 2006 1450-2a DNR Permit Application 1450-6 May 2006 1450-2b DNR Completion Record Form 1450-7 May 2006 1450-3a Land Corner Record 1450-8 May 2006 1450-3b Land Corner Record 1450-9 May 2006 Design Manual M 22-01 Project Development Roles and Responsibilities for Projects with Structures May 2006 Page 141-1 Project Development Roles and Responsibilities Chapter 141 for Projects with Structures ## 141.02 Procedures The flow diagram, Figures 141-1a and 141-1 b,begins at the left with the initial approval and funding of the project and ends at the right with the start of the project delivery process. After a project is programmed, WSDOT is tasked with confirming the project scope and defining the structural team’s level of involvement in design and construction. If a consultant is not used, all bridge design work will be performed by the Bridge and Structures Office. If a consultant is used, the WSDOT Region and Bridge and Structures Office will determine the level of involvement and responsibility for the design. Agreements defining the level of involvement and responsibility will be developed and executed between the appropriate Regional office responsible for project development and the Bridge and Structures Office and the appropriate project delivery process will be implemented. More information on this process and the desired outcomes is available on the Bridge and Structures Office’s homepage at: 141.01 General 141.02 Procedures ## 141.01 General This chapter presents the project development process used by Washington State Department of Transportation (WSDOT), the Regions and the Bridge and Structures Office together, to determine the roles and responsibilities for projects with structures during the project development phase of a project. This chapter complements the Project Management On-Line Guide which is located at: Process.htm#PMOG See Division 11
|
{
"page_id": null,
"source": 7320,
"title": "from dpo"
}
|
chapters and the Bridge Design Manual for design procedures. The primary objective of this process is to provide a consistent means of selecting a bridge design team to perform all or part of the structural design work, whether it be a consultant or the WSDOT Bridge and Structures Office. If the Local Agency will be requesting any services from WSDOT, the Local Agency will contact WSDOT’s Local Program Engineer. The Local Program Engineer will help define the level of WSDOT’s involvement in design and construction. Project Development Roles and Responsibilities for Projects with Structures Design Manual M 22-01 Page 141-2 May 2006 Determination of the Roles and Responsibilities for Projects with Structures (Project Development Phase) Figure 141-1a Approved & Initially Funded Projects Obtain Structural and Other Technical Assistance and Guidance for Project Scoping Confirm Project Delivery Process > Construction Contracting (DB, DBB) > Phasing > Schedule > Environmental > On/Off State System > In/Out State ROW > Funding Sourc e Considerations FHWA - Federal Highway Administration WSDOT - Washington State Department of Transportation DB - Design Build No DBB - Design Bid Build B&SO - Bridge & Structures Office ROW - Right of way Provide Consultants an Unofficial List (prepared by B&SO) of Programmed Projects on WSDOT Website Yes Confirm Project Definition - Prospectus [Negotiation Flow Chart -Step 1] Consultant To Be Used? Obtain Written Letter or Agreement on B&SO Level of Involvement, (Responsibility & Availability) for Design & Construction [ Project Management On-Line Guide] WSDOT Region Identify Owner, Design Lead, and Key Players Local Agency Tribal Private Entity > Administrator > Designer > Technical Review > Advise > Specific Tasks > Portions of Projects > None Potential B&SO Level of Involvement Design Manual M 22-01 Project Development Roles and Responsibilities for Projects with Structures May 2006 Page 141-3 Work
|
{
"page_id": null,
"source": 7320,
"title": "from dpo"
}
|
Programmed for B&SO Revisit & Revise Written Letter or Agreement Legend No Is written letter or agreement on B&SO Level of Involvement Valid? Consultant Selection [Negotiation Flow Chart - Step 2] Proceed with Project Management On-Line Guide Yes No Consultant To Be Used? Yes Determine Consultant Level of Project Responsibilities [Project Management On-Line Guide] Preliminary List of Projects Programmed for the use of Consultants on WSDOT Website (Prepared by B&SO) Beginning/ End Task Input Decision Product/ Separate Process Considerations Continue with WSDOT’s “Negotiation Flow Chart” and proceed with Project Management On-Line Guide > Total Project Done by Consultant-Region Administrators Bridge and Structures Office Technical Review and Consultant Selection > Bridge Work by Consultant Other Work by Region-Bridge and Structures Office Administrators, Technical Review and Consultant Selection > Some Bridge Work by Consultant > Consultant Responsibilities During Construction Determination of the Roles and Responsibilities for Projects with Structures (Project Development Phase) Figure 141-1b Design Manual M 22-01 Value Engineering May 2006 Page 315-1 Chapter 315 Value Engineering ## 315.03 Definitions Value Engineering (VE) A systematic application of recognized techniques by a multi-disiplined team to identify the function of a product or service, establish a worth for that function, generate alternatives through the use of creative thinking, and provide the needed functions to accomplish the original purpose; thus assuring the lowest life cycle cost without sacrificing safety, necessary quality, or environmental attributes. Value Engineering is sometimes referred to as Value Analysis (VA) or Value Management (VM). project The portion of a transportation facility that WSDOT proposes to construct, reconstruct, or improve, as described in the State Highway System Plan or applicable environmental documents. A project may consist of several contracts or phases over several years that are studied together as one project . ## 315.04 Procedure The VE process uses the Eight-Phase
|
{
"page_id": null,
"source": 7320,
"title": "from dpo"
}
|
Job Plan in Figure 315-1. Only the phases 1 and 7 are discussed in this chapter. A detailed discussion of phases 2 through 6 can be found in the VE training manual entitled Introduction To Value Engineering Principles and Practices . (1) Selection Phase (a) Project Selection Projects for VE studies may be selected from any of the categories identified in the Highway Construction Program, including Preservation or Improvement projects, depending on the size and/or complexity of the project. In addition to the cost, other issues adding to the complexity of the project design are considered in the selection process. These complexities include: critical constraints, difficult technical issues, expensive solutions, external influences, and complicated functional requirements. 315.01 General 315.02 References 315.03 Definitions 315.04 Procedure 315.05 Documentation ## 315.01 General Value Engineering is a systematic process designed to focus on the major issues of a complex project or process. It uses a multi-disciplined team to develop recommendations for the important decisions that must be made. The primary objective of a Value Engineering study is Value Improvement. For projects, the value improvements might be improvements in scope definition, functional design, constructibility, coordination (both internal and external), or the schedule for project development. Other possible value improvements are reduced environmental impact, reduced public (traffic) inconvenience, or reduced project cost. The Value Engineering process incorporates, to the extent possible, the values of the design engineer, construction engineer, maintenance engineer, contractor, state and federal approval agencies, local agencies, other stakeholders, and the public. Important design decisions are formulated from the recommendations of the Value Engineering team. ## 315.02 References CFR 23 Part 627 Value Engineering Value Engineering for Highways , Study Workbook, U. S. Department of Transportation, FHWA Introduction To Value Engineering Principles and Practices, Transportation Partnership in Engineering Education Development (TRANSPEED), University of Washington.
|
{
"page_id": null,
"source": 7320,
"title": "from dpo"
}
|
Value Engineering Design Manual M 22-01 Page 315-2 May 2006 A VE study is required for any federally funded NHS project with an estimated cost of $25 million or more (CFR 23 Part 627). Other types of projects that usually provide the highest potential for value improvement have a preliminary estimate exceeding $ 5 million and include one or more of the following: • Projects with alternative solutions that vary the scope and cost • New alignment or bypass sections • Capacity improvements that widen an existing highway • Major structures • Interchanges on multilane facilities • Projects with extensive or expensive environmental or geotechnical requirements • Materials that are difficult to acquire or require special efforts • Inferior materials sources • Major reconstruction • Projects requiring major traffic control • Projects with multiple stages (b) Statewide VE Study Plan On a biennial basis, the state VE manager coordinates with the region VE coordinators to prepare the T wo-Year VE Study Plan with specific projects scheduled by quarter. The VE Study Plan is the basis for determining the projected VE program needs, including team members, team leaders, and training. The Statewide VE Study Plan is a working document and close coordination is necessary between HQ and the regions to keep it current. The regional VE coordinator: • Identifies potential projects for VE studies from the Project Summaries and the available planning documents for future work. • Makes recommendations for the VE study timing. • Presents a list of the identified projects to regional management to prioritize into a regional Two-Year VE Study Plan. (VE studies other than projects are also included in the plan.) The State Design Engineer: • Reviews the regional Two-Year VE Study Plan regarding the content and schedule of the plan. The state VE Manager: • Incorporates
|
{
"page_id": null,
"source": 7320,
"title": "from dpo"
}
|
the regional Two-Year VE Study Plans and the HQ Study Plans to create the Statewide VE Study Plan. (c) VE Study Timing Selecting the project at the appropriate stage of development (the timing of the study) is very important to the success of the VE program. Value can be added by performing a VE study any time during project development; however, the WSDOT VE program identifies three windows of opportunity for performing a VE study. 1. Problem Definition Stage As soon as preliminary engineering information is available and the specific deficiencies or “drivers” are identified, the project scope and preliminary cost are under consideration. This is the best time to consider the various alternatives or design solutions and there is the highest potential that the related recommendations of the VE team can be implemented. At the conclusion of the VE study, the project scope, preliminary cost, and major design decisions can be based on the recommendations. When conducting a study in the problem definition stage, the VE study focuses on issues affecting project “drivers.” This stage often provides an opportunity for building consensus with stakeholders. 2. Conceptual Design Stage At the conceptual design stage, the project scope and preliminary cost have already been established and the major design decisions have been made. Some PS&E activities might have begun and coordination has been initiated with the various service units that will be involved with the design. At this stage, the established project scope, preliminary cost, and schedule will define the limits of the VE study. There is still opportunity for a VE study to focus on the technical issues for each of the specific design elements. Design Manual M 22-01 Value Engineering May 2006 Page 315-3 3. 30 % Development Stage At the 30% stage, most of the important project decisions
|
{
"page_id": null,
"source": 7320,
"title": "from dpo"
}
|
have been made and the opportunity to affect the project design is limited. The VE study focuses on constructibility, construction sequencing, staging, traffic control elements, and any significant design issues that have been identified during design development. (d) Study Preparation To initiate a VE study, the project manager submits a Request for Value Engineering Study form (shown in Figure 315-2) to the region VE coordinator at least one month before the proposed study date. The regional VE coordinator then works with the state VE Manager to determine the team leader and team members. The design team prepares a study package that includes project information for each of the team members. A list of potential items is shown in Figure 315-3. The region provides a facility and the equipment for the study (Figure 315-3). (e) Team Leader The quality of the VE study is dependent on the skills of the VE team leader. This individual guides the team efforts and is responsible for its actions during the study. The best VE team leader is knowledgeable and proficient in transportation design and construction, and in the VE study process for transportation projects. For best results, the team leader should be certified by the Society of American Value Engineers (SAVE) as a Certified Value Specialist (CVS) or as a Value Methodology Practitioner (VMP). Team leadership can be supplied from within the region or from other regions, HQ , consultants, or other qualified leaders outside the department. The state VE Manager coordinates with the regional VE coordinator to select the team leader. A statewide pool of qualified team leaders is maintained by the state VE Manager. (f) Team Members The VE team is usually composed of five to eight persons with diverse backgrounds that are relevant to the specific study. The team members may
|
{
"page_id": null,
"source": 7320,
"title": "from dpo"
}
|
be selected from the regions, HQ , other state and federal agencies, local agencies, and the private sector. The team members are selected on the basis of the kinds of expertise needed to address the major functional areas and critical high-cost issues of the study. All team members must be committed to the time required for the study. For best results, the team members have had VE training before participating in a VE study. (g) VE Study Requirements The time required to conduct a VE study varies with the complexity and size of the project, but typically ranges from three to five days. The VE study Final Report and Workbook include a narrative description of project input information, background and history, constraints and drivers, VE team focus areas, and a discussion of the team speculation, evaluation, and recommendations. All of the team’s evaluation documentation (including sketches, calculations, analyses, and rationale for recommendations) is included in the Workbook as part of the Final Report. Include a copy of the Final Report and Workbook in the Project File. The number of copies of the Final Report and Workbook is specified by the project manager. Value Engineering Design Manual M 22-01 Page 315-4 May 2006 (2) Implementation Phase The VE team’s recommendations are included in the Final Report and Workbook. The project manager reviews and evaluates the recommendations and prepares a VE Decision Document. This document has a specific response for each of the VE team recommendations and a summary statement containing the managers’ decisions and schedule for implementation regarding further project development. The VE Decision Document also includes estimated costs or savings of the recommendations, as well as the estimated cost to implement the recommendations. A copy of this document is sent to the state VE Manager so the results can be
|
{
"page_id": null,
"source": 7320,
"title": "from dpo"
}
|
included in the annual VE report to FHWA. The VE Decision Document is submitted to the State Design Engineer and a copy becomes a vital element in the design file for the project. Project development then continues based on the decisions developed from the preliminary engineering and the VE study recommendations (barring participation agreements funded by other agencies, utilities, developers, and so forth). ## 315.05 Documentation The documents required to be preserved in the Design Documentation Package (DDP) or the Project File (PF) is on the following web site: Design Manual M 22-01 Value Engineering May 2006 Page 315-5 Eight-Phase Job Plan for VE Studies > Figure 315-1 1. Selection Phase 315.04(1) Select the right projects, timing, team, and project processes and elements. 2. Investigation Phase Investigate the background information, technical input reports, field data, function analysis, and team focus and objectives. 3. Speculation Phase Be creative and brainstorm alternative proposals and solutions. 4. Evaluation Phase Analyze design alternatives, technical processes, life cycle costs, documentation of logic, and rationale. 5. Development Phase Develop technical and economic supporting data to prove the feasibility of the desirable concepts. Develop team recommendations. Recommend long-term as well as interim solutions. 6. Presentation Phase Present the recommendations of the VE team in an oral presentation, and in a written report and workbook. 7. Implementation Phase 315.04(2) Evaluate the recommendations. Prepare an implementation plan (VE Decision Document) including the response of the managers and a schedule for accomplishing the decisions based on the recommendations. 8. Audit Phase Maintain a records system to track the results and accomplishments of the VE program on a statewide basis. Compile appropriate statistical analyses as requested. Steps 2-6 are performed during the study, see Introduction To Value Engineering Principles and Practices for procedures during these steps. Value Engineering Design Manual
|
{
"page_id": null,
"source": 7320,
"title": "from dpo"
}
|
M 22-01 Page 315-6 May 2006 Request for Value Engineering Study Figure 315-2 Project Title: SR No. MP to MP Length Subprogram PIN WIN Assigned Project Engineer Proposed Advertising Date Estimated Right of Way Costs Estimated Construction Costs Design Speed Projected ADT Route Conditions/Geometry: Adjacent Segments Overall Route Major Project Elements Environmental Issues Construction Issues Suggested Value Team Composition: Architecture Hydraulics Bridge Landscape Architecture Construction Maintenance Design Planning/Programming Environmental Traffic Other _____________ Real Estate Services Region Contact Person Dates requested for VE study Design Manual M 22-01 Value Engineering May 2006 Page 315-7 Project-Related Input* (Study Package) Study-Related Facilities and Equipment Design File Room w/large table Quantities Phone Estimates Photo/Video log access/SRView R/W Plans Van for Field Trip ** Geotechnical Reports Easel(s) Plan Sheets Large Tablet Paper (2x2 squares) Environmental Documents Colored Marking Pens X-sections and Profiles Masking and Clear Adhesive Tape Land Use Maps Workbook(s) Contour Maps Polaroid Camera Quadrant Maps Design Manual Accident Data “Green Book” Traffic Data Standard Plans Up-to-Date Large-Scale Aerial Photographs Standard Specifications Vicinity Map M.P. Log Hydraulics Report Bridge List Aerial Photos WSDOT Phone Book Existing As-Built Plans Scales and Straight Edge Red Book - Field Tables Unit Bid Prices Calculators Scissors * Not all information listed may be available to the team depending on the stage of the project. ** If field trip is not possible, provide video of project. VE Study Team Tools > Figure 315-3 Design Manual M 22-01 Design Documentation, Approval, and Process Review May 2006 Page 330-1 ## 330.02 References Code of Federal Regulations (CFR) 23 CFR 635.111 “Tied bids” 23 CFR 635.411 “Material or product selection” Revised Code of Washington (RCW) 47.28.030 Contracts -- State forces -- Monetary limits -- Small businesses, minority, and women contractors -- Rules. RCW 47.28.035 Cost of project, defined. Washington Federal-Aid Stewardship Agreement,
|
{
"page_id": null,
"source": 7320,
"title": "from dpo"
}
|
as implemented in the design matrices (Chapter 325) Executive Order E 1010.00, “Certification of Documents by Licensed Professionals,” WSDOT Directional Documents Index, D 00-00, WSDOT Advertisement and Award Manual, M 27-02, WSDOT Hydraulics Manual , M 23-03, WSDOT Master Plan for Limited Access Highways, WSDOT Plans Preparation Manual , M 22-31, WSDOT Route Development Plan , WSDOT Washington State Highway System Plan , WSDOT ## 330.03 Definitions Design Approval Documented approval of the Design Documentation Package through signature of a designated representative of the approving organization as shown in Figures 330-2a and 330-2b. This documentation becomes part of the Design Documentation Package. If federal funds are involved, Design Approval is required in order to begin right of way acquisition. 330.01 General 330.02 References 330.03 Definitions 330.04 Design Documentation 330.05 Project Development 330.06 Scoping Phase 330.07 FHWA Approval 330.08 Design Approval 330.09 Process Review ## 330.01 General The project file contains the documentation of planning, scoping, programming, design, approvals, contract assembly, utility relocation, needed right of way, advertisement, award, construction, and maintenance review comments for a project. A project file is completed for all projects and is retained by the region office responsible for the project. Responsibility for the project will shift from one office to another during the life of a project. The project file follows the project, as the project responsibility shifts from office to office. Portions of the project file that are not designated as components of the Design Documentation Package may be purged when retention of the construction records is no longer necessary. The Design Documentation Package is a part of the project file. It documents and justifies design decisions and the design process followed. The Design Documentation Package is retained in a permanent, retrievable file for a period of 75 years, in accordance with WSDOT records
|
{
"page_id": null,
"source": 7320,
"title": "from dpo"
}
|
retention policy. For operational changes and developer projects, design documentation is required and is retained by the region office responsible for the project, in accordance with WSDOT records retention policy. All participants in the design process must provide the appropriate documentation for their decisions. # Design Documentation, Chapter 330 Approval, and Process Review Design Documentation, Approval, and Process Review Design Manual M 22-01 Page 330-2 May 2006 Design Concurrence An incremental Design Approval by the designated representative of the approving organization shown in Figures 330-2a and 330-2b. The Project Summary documents must be submitted to the designated approval authority before Design Concurrence can be granted. The primary purpose of Design Concurrence is for work order authorization to establish funding for preliminary engineering. DE A design exception. Preauthorization to omit correction of an existing design element for various types of projects, as designated in the design matrices. See Chapter 325. A DE designation indicates that the design element is normally outside the scope of the Project Type. See Figure 330-1. design variance A recorded decision to differ from the design level specified in the Design Manual , such as an Evaluate Upgrade (EU) not upgraded, a DE, or a deviation. EUs leading to an upgrade are documented but are not considered to be variances. A project or corridor analysis may also constitute a design variance if that analysis leads to a decision to use a design level or design classification that differs from what the Design Manual specifies for the project type. Design Variance Inventory (DVI) A list of design elements that will not be improved in accordance with the Design Manual criteria designated for the project. Design Variance Inventory System (DVIS) A database application developed to generate the DVI form. The DVIS also provides query functions providing designers an opportunity
|
{
"page_id": null,
"source": 7320,
"title": "from dpo"
}
|
to search for previously granted variances. The DVIS application can be accessed at: deviation A documented decision granting approval at project specific locations to differ from the design level specified in the Design Manual . See Figure 330-1. environmental documents: NEPA National Environmental Policy Act SEPA [Washington] State Environmental Policy Act CE NEPA: Categorical Exclusion CE SEPA: Categorical Exception EA Environmental Assessment ECS Environmental Classification Summary EIS Environmental Impact Statement ERS Environmental Review Summary FONSI Finding Of No Significant Impact ROD Record of Decision EU An evaluate upgrade. A decision making process, requiring evaluation and documentation of whether or not to correct an existing design element as designated in the design matrices. See Figure 330-1. FHWA Federal Highway Administration HQ The Washington State Department of Transportation headquarters organization Project Control Form A form used to document and approve revisions to project scope, schedule, or budget, from a previously approved Project Definition. There are two versions of the Project Control Form. One version of the form is specifically for projects included in the Nickel Funding Package enacted by the 2003 legislature. The other version of the form is for projects that are not included in the Nickel Funding Package. The form is available at: project file A file containing all documentation and data for all activities related to a project. See 330.01 and 330.04. Design Documentation Package (DDP) The portion of the project file, including required project approvals, that will be retained long-term, in accordance with the WSDOT document retention policies. Depending on the scope of the project, it contains the Project Summary and some or all of the other documents discussed in this chapter plus technical reports, calculations (quantity calculations are part of the project file, but are not designated as components of the DDP), estimates, justifications for
|
{
"page_id": null,
"source": 7320,
"title": "from dpo"
}
|
decisions made, and any applicable documents listed in the Design Documentation Check List on the web. Design Manual M 22-01 Design Documentation, Approval, and Process Review May 2006 Page 330-3 See 330.04(2). The Design Documentation Package explains how and why the design was chosen, and documents approvals. See 330.01. Project Summary A set of electronic documents consisting of the Environmental Review Summary (ERS), Design Decisions Summary (DDS), and Project Definition (PD). The Project Summary is part of the design documentation required to obtain Design Concurrence and ultimately is part of the design documentation required for Design Approval. See 330.06. Environmental Review Summary (ERS) An electronic document that records the environmental requirements and considerations for a specific project. Design Decisions Summary (DDS) An electronic document that records major design decisions regarding roadway geometrics, roadway and roadside features, and other issues that influence the project scope and budget. Project Definition (PD) An electronic document that records the purpose and need of the project, along with program level and design constraints. scoping phase The first phase of project development for a specific project. It follows identification of the need for a project and precedes detailed project design. This is the process of identifying the work to be done and developing a cost estimate for completing the design and construction. The Project Summary, engineering and construction estimates, and several technical reports (such as geotechnical, surfacing, bridge condition, etc.) are developed during this phase. ## 330.04 Design Documentation (1) Purpose Design documentation is prepared to record the evaluations by the various disciplines that result in design recommendations. Design assumptions and decisions made prior to and during the scoping phase are included. Changes that occur throughout project development are documented. Justifications and approvals, if required, are also included. The Design Documentation Package identifies the purpose and
|
{
"page_id": null,
"source": 7320,
"title": "from dpo"
}
|
need of the project and documents how the project addresses the purpose and need. The required content of the Design Documentation Package is identified in the Design Documentation Check List at: (2) Design Documents The Design Documentation Package portion of the project file preserves the decision documents generated during the design process. In each package, a summary (list) of the documents is recommended. The design documents commonly included in the project file and Design Documentation Package for all but the simplest projects are listed in Figure 330-5. For project-specific components, provide documentation in the project file and Design Documentation Package as detailed in the Design Documentation Check List at: Documentation is not required for components not related to the project. The Design Variance Inventory is required for all projects on NHS highways having design variances and is recommended for all projects having design variances. This form lists all evaluate upgrades (EU) not upgraded to the applicable design level, design exceptions (DE), and deviations as indicated by the design matrices. Also, record variances resulting from a project or corridor analysis in the DVI. Use the Design Variance Inventory System (DVIS) database application to record and manage design variances. The DVIS is available at: The Project Definition (PD) and Environmental Review Summary (ERS) are required for most projects. Exceptions will be identified by the Project Control and Reporting office. Design Documentation, Approval, and Process Review Design Manual M 22-01 Page 330-4 May 2006 The Design Decisions Summary (DDS) is not required for the following project types unless they involve reconstructing the lanes, shoulders, or fill slopes. Since these and some other project types are not included in the design matrices, evaluate them with respect to modified design level (M) for non-NHS routes and full design level (F) for NHS
|
{
"page_id": null,
"source": 7320,
"title": "from dpo"
}
|
routes. Include, in the evaluation, only those design elements specifically impacted by the project. Although the following list illustrates some of the project types that do not require a DDS, the list is not intended to be a complete accounting of all such projects. Consult with the Project Control and Reporting office for projects not included in the list. • Bridge painting • Crushing and stockpiling • Pit site reclamation • Lane marker replacement • Guide post replacement • Signal rephasing • Signal upgrade • Seismic retrofit • Bridge joint repair • Navigation light replacement • Signing upgrade • Illumination upgrade • Rumble strips • Electrical upgrades • Major drainage • Bridge scour • Fish passage • Other projects as approved by the HQ Design Office (3) Certification of Documents by Licensed Professionals All original technical documents must bear the certification of the responsible licensee. See Executive Order E 1010.00. (4) Design Exception, Evaluate Upgrade, and Deviation Documentation See Figure 330-1 for design matrices documentation requirements. In special cases, projects may need to address design elements, which are shown as blank cells in a design matrix. These special cases must be coordinated with the appropriate Assistant State Design Engineer, and the HQ Project Control and Reporting office. When this is necessary, document the reasons for inclusion of that work in your project. When the design matrices specify a DE for a design element, the DE documentation must specify the matrix and row, the design element, and the limits of the exception. When a Design Variance Inventory is required for the project, the DE locations must be recorded in the inventory. All EU decisions must be documented. The EU process determines if an item of work will or will not be done, through analysis of factors such as benefit/cost, route continuity,
|
{
"page_id": null,
"source": 7320,
"title": "from dpo"
}
|
accident reduction potential, environmental impact, and economic development. Documentation requirements for an EU decision are similar to, but less demanding than, documentation requirements for a deviation. The cost of the improvement must always be considered when making EU decisions. EU examples on the Internet can serve as models for development of EU documentation. The appropriate approval authority for EUs is designated in Figures 330-2a and 330-2b. Deviation requests are stand-alone documents requiring enough information and project description for an approving authority to make an informed decision of approval or denial. Documentation of a deviation must contain justification and must be approved at the appropriate administrative level as shown in Figures 330-2a and 330-2b. Submit the request as early as possible because approved deviations are needed prior to Design Approval or Intersection/Interchange Plan approval. Design Manual M 22-01 Design Documentation, Approval, and Process Review May 2006 Page 330-5 When applying for deviation approval, it is necessary to provide two explanations. The first identifies the design element and explains why the design level specified in the design matrices was not or cannot be used. The second provides the justification for the design that is proposed. Justification for a deviation must be supported by at least two of the following: • Accident history and accident analysis • Benefit/cost analysis • Engineering judgment • Environmental issues • Route continuity An element of engineering judgment might be a reference to another publication, with an explanation of why that reference is applicable to the situation encountered on the project. If the element you wish to deviate from, meets the AASHTO Policy on Geometric Design of Highways and Streets, but not the Design Manual criteria, the only documentation and justification required to support the deviation request is to; • Identify the design element • Explain why the
|
{
"page_id": null,
"source": 7320,
"title": "from dpo"
}
|
design level specified in the design matrices was not used • Explain which reference to the AASHTO Policy on Geometric Design of Highways and Streets was used (including the publication date, chapter, and page number of the policy) Approval is at the appropriate administrative level, as shown in Figures 330-2a and 330-2b. Reference a corridor or project analysis as supporting justification for design deviations dealing with route continuity issues. See Chapter 325. Matrix Cell Content Project corrects design elements that do not conform to specified design level Document to file Record in DVIS Blank cell in design matrix No No Blank cell in design matrix DDP No Cell Entry Full (F), Modified (M), Basic (B) (with no DE or EU qualifiers) Yes No No No Yes Yes Design Exception (DE) Yes DDP No No DDP Yes Evaluate Upgrade (EU) Yes DDP No No DDP Yes DDP = Document to Design Documentation Package Notes: See 330.04(3) See 330.04(2) May be included in the project in special cases, if identified in the Project Summary or Project Control Form Nonconformance with specified design level (Chapter 325) requires an approved deviation Requires supporting justification (See 330-04(4).) Design Matrix Documentation Requirements > Figure 330-1 Design Documentation, Approval, and Process Review Design Manual M 22-01 Page 330-6 May 2006 Once a deviation is approved, it applies to that project only. When a new project is programmed at the same location, the subject design element must be reevaluated and either (1) the subject design element is rebuilt to conform with the applicable design level, or (2) a new deviation is developed, approved, and preserved in the Design Documentation Package for the new project. Check the Design Variance Inventory System for help in identifying previously granted
|
{
"page_id": null,
"source": 7320,
"title": "from dpo"
}
|
deviations. A change in a design level resulting from an approved Route Development Plan or corridor or project analysis, as specified in design matrix notes, is documented similar to an EU. Design elements that do not comply with the design level specified in an approved corridor or project analysis are documented as deviations. To prepare a deviation request, or to document an EU decision, use the list in Figure 330-6 as a general guide for the sequence of the content. The list is not all-inclusive of potential content and it might include suggested topics that do not apply to a particular project. Design deviation examples are on the Internet at: ## 330.05 Project Development In general, the region initiates the development of a specific project by preparing the Project Summary. Some project types may be initiated by other WSDOT groups such as the Bridge Office or the Traffic Office, rather than the region. The project coordination with other disciplines (such as Real Estate Services, Utilities, and Environmental) is started in the project scoping phase and continues throughout the project’s development. The region coordinates with state and federal resource agencies and local governments to provide and obtain information to assist in developing the project. The project is developed in accordance with all applicable Directives, Instructional Letters, Supplements, and manuals as listed in D 00-00; the Master Plan for Limited Access Highways; Washington State Highway System Plan; Route Development Plan ; Washington Federal-Aid Stewardship Agreement as implemented in the design matrices (Chapter 325); and the Project Summary. The region develops and maintains documentation for each project. The project file includes documentation of project work including planning, scoping, public involvement, environmental action, design decisions, right of way acquisition, PS&E development, project advertisement, and construction. Refer to the Plans Preparation Manual for PS&E
|
{
"page_id": null,
"source": 7320,
"title": "from dpo"
}
|
documentation. All projects involving FHWA action require NEPA clearance. Environmental action is determined through the Environmental Classification Summary (ECS) form. The environmental approval levels are shown in Figures 330-3a and 3b. Upon receipt of the ECS approval, for projects requiring an EA or EIS under NEPA, the region proceeds with environmental documentation, including instituting public involvement methods that are appropriate to the magnitude and type of the project. (See Chapter 210.) The Assistant State Design Engineers work with the regions on project development and conduct process reviews on projects as described in 330.09. ## 330.06 Scoping Phase Development of the project scope is the initial phase of project development for a specific project. This effort is prompted by the Washington State Highway System Plan . The project scoping phase consists of determining a project description, schedule, and cost estimate. The intent is to make design decisions early in the project development process that focus the scope of the project. During the project scoping phase, the Project Summary documents are produced. Project Summary provides information on the results of the scoping phase; links the project to the Washington State Highway System Plan and the Capital Improvement and Preservation Program (CIPP); and documents the design decisions, the environmental classification, and agency coordination. The Project Summary is developed and Design Concurrence is granted before the project is funded for design and construction. The Project Summary consists of ERS, DDS, and PD documents, which are Design Manual M 22-01 Design Documentation, Approval, and Process Review May 2006 Page 330-7 electronic forms. Specific on-line instructions for filling them out are contained in the Project Summary database. Environmental Review Summary (ERS) lists the environmental permits and approvals that will be required, environmental classifications, and environmental considerations. This form lists requirements by environmental and permitting agencies. If
|
{
"page_id": null,
"source": 7320,
"title": "from dpo"
}
|
there is a change in the Project Summary, the information in the ERS must be reviewed and revised to match the new Project Summary. The ERS is prepared during the scoping phase and is approved by the region. Design Decisions Summary (DDS) states the design matrix used to develop the project, the roadway geometrics, design deviations, evaluate upgrades (EUs), other roadway features, and any design decisions made during scoping of a project. The information contained in this form is compiled from various databases of departmental information, field data collection, and evaluations made in development of the Project Definition and the ERS. Design decisions may be revised throughout the project development process based on continuing evaluations. The DDS is approved by the appropriate Assistant State Design Engineer for new construction and reconstruction projects on the Interstate System before submittal to FHWA. See 330.07. The regional design authority approves the DDS for all other types of projects. To approve the Design Decisions Summary, the region must be comfortable that there will be no significant change in the Project Definition or estimated cost. If, however, there is a change to the PD or a significant change in the cost estimate, the DDS is to be revised or supplemented and reapproved. Significant cost changes require a Project Control Form to be submitted and approved by the appropriate designee. Project Definition (PD) identifies the various disciplines and design elements that will be encountered in project development. The PD states the needs, the purpose of the project, program categories, and the recommendations for project phasing.This information determines the level of documentation and evaluation that is needed for Design Approval. The PD is completed early in the scoping phase to provide a basis for full development of the ERS, DDS, schedule, and estimate. If circumstances necessitate a
|
{
"page_id": null,
"source": 7320,
"title": "from dpo"
}
|
change to an approved PD, process a Project Control Form for approval by the appropriate designee, revise the original PD form, and obtain approval of the revisions. ## 330.07 FHWA Approval For all NHS projects, the level of FHWA oversight varies according to the type of project, the agency doing the work, and the funding source as shown in Figures 330-2a and 330-2b. Oversight and funding do not affect the level of design documentation required for a project. An FHWA determination of engineering and operational acceptance is required for any new or revised access point (including interchanges, temporary access breaks, and locked gate access points) on the Interstate System, regardless of funding. (See Chapter 1425.) Documents for projects requiring FHWA review and Design Approval are submitted through the Headquarters (HQ) Design Office. Include applicable project documents as specified in Figure 330-5. ## 330.08 Design Approval When the Project Summary documents are complete, and the region is confident that the proposed design adequately addresses the purpose and need for the project, a Design Concurrence may be entered into the Project File. (See Design Concurrence definition for purpose.) When the Design Documentation Package is complete, Design Approval is granted by the approval authority designated in Figures 330-2a and 330-2b. The Design Approval becomes part of the DDP. See 330.04 and Figure 330-5 for design documents that may lead to Design Approval. Figures 330-2a through 330-4 present approval levels for project design and PS&E documents. Design Documentation, Approval, and Process Review Design Manual M 22-01 Page 330-8 May 2006 The following items must be approved prior to Design Approval: • Required Environmental Documents • Project Summary Documents • Design Variance Inventory as required • Cost Estimate At the time of Design Approval, the Design Documentation Package addresses all guidance currently implemented in the
|
{
"page_id": null,
"source": 7320,
"title": "from dpo"
}
|
Design Manual .If a project is delayed but is advertised within three years of the Design Approval, discuss Design Manual revisions with your Project Development Engineer, who will discuss the revisions with the appropriate Assistant State Design Engineer (ASDE) to determine if there is a need to redesign any portion of the project. If the ASDE determines that a redesign is not necessary, the ASDE will confirm with an e-mail. Place a copy of the e-mail confirmation in the Design Documentation Package to document that the current design criteria was evaluated and the ASDE agreed that a redesign is unnecessary. Address new design policy for projects to be advertised more than three years after Design Approval, redesign as appropriate, and update the Design Documentation Package and the Design Approval to reflect the revisions. For an overview of design policy changes, consult the Detailed Chronology of Design Policy Changes Affecting Shelved Projects at: designpolicy.htm ## 330.09 Process Review The process review is done to provide reasonable assurance that projects are prepared in compliance with established policies and procedures and that adequate records exist to show compliance with state and federal requirements. Process reviews are conducted by WSDOT, FHWA, or a combination of both. The design and PS&E process review is performed in each region at least once each year by the HQ Project Development Branch. The documents used in the review process are: the Design Documentation Check List, PS&E Review Check List, and PS&E Review Summary. These are generic forms used for all project reviews. Copies of these working documents are available for reference when assembling project documentation. HQ Design Office, Project Development Branch maintains current copies on the Internet at: Each project selected for review is examined completely and systematically beginning with the scoping phase (including planning documents)
|
{
"page_id": null,
"source": 7320,
"title": "from dpo"
}
|
and continuing through contract plans and (when available) construction records and change orders. Projects are normally selected after contract award. For projects having major traffic design elements, the Maintenance and Operations Programs’ Traffic Operations personnel are involved in the review. The WSDOT process reviews may be held in conjunction with FHWA process reviews. The HQ Project Development Branch schedules the process review and coordinates it with the region and FHWA. A process review follows this general agenda: 1. Review team meets with regional personnel to discuss the object of the review. 2. Review team reviews the design and PS&E documents, and the construction documents and change orders if available, using the check lists. 3. Review team meets with regional personnel to ask questions and clarify issues of concern. 4. Review team meets with regional personnel to discuss findings. 5. Review team submits a draft report to the region for comments and input. 6. If the review of a project shows a serious discrepancy, the regional design authority is asked to report the steps that will be taken to correct the deficiency. 7. The process review summary forms are completed. 8. The summary forms and check lists are evaluated by the State Design Engineer. 9. The findings and recommendations of the State Design Engineer are forwarded to the regional design authority, for action and/or information, within 30 days of the review. Design Manual M 22-01 Design Documentation, Approval, and Process Review May 2006 Page 330-9 Project Design FHWA Oversight Level Deviation and Corridor/Project Approval(a)(b) EU Approval(b) Design Approval Interstate New/Reconstruction (c) • Federal funds • No federal funds (d) (e) FHWA Region FHWA Intelligent Transportation Systems (ITS) over $1 million (f) HQ Design Region HQ Design All Other (g) • Federal funds • State funds • Local agency funds (f) (f)
|
{
"page_id": null,
"source": 7320,
"title": "from dpo"
}
|
(e) HQ Design Region Region National Highway System (NHS) Managed access highway outside incorporated cities and towns, or inside unincorporated cities and towns, or on a limited access highway (f) HQ Design Region Region Managed access highway within incorporated cities and towns (h) • Inside curb or EPS (i) • Outside curb or EPS (f) (f) HQ Design HQ H&LP Region N/A Region City/Town FHWA = Federal Highway Administration HQ = WSDOT Headquarters H&LP = WSDOT Highways and Local Programs Office EPS = Edge of paved shoulder where curbs do not exist (a) These approval levels also apply to deviation processing for local agency work on a state highway. (b) See 330.04(4). (c) See Chapter 325 for definition. (d) Requires FHWA review and approval (full oversight) of design and PS&E submitted by HQ Design. (e) To determine the appropriate oversight level, FHWA reviews the Project Summary (or other programming document) submitted by HQ Design, or by WSDOT Highways and Local Programs through HQ Design. (f) FHWA oversight is accomplished by process review. (See 330.09) (g) Reduction of through lane or shoulder widths (regardless of funding) requires FHWA review and approval of the proposal. (h) Applies to the area within the incorporated limits of cities and towns. (i) Includes raised medians. Design Approval Level > Figure 330-2a Design Documentation, Approval, and Process Review Design Manual M 22-01 Page 330-10 May 2006 Project Design FHWA Oversight Level Deviation and Corridor/Project Approval (a)(b) EU Approval (b) Design Approval Non-National Highway System (Non-NHS) Improvement project on managed access highway outside incorporated cities and towns, or within unincorporated cities and towns, or on a limited access highway, (Matrix lines 5-8 through 5-26) N/A HQ Design Region Region Improvement project on managed access highway within incorporated cities and towns(h) • Inside curb or EPS (i) •
|
{
"page_id": null,
"source": 7320,
"title": "from dpo"
}
|
Outside curb or EPS (Matrix lines 5-8 through 5-26) N/A N/A HQ Design HQ H&LP Region N/A Region City/Town Preservation project on managed access highway outside incorporated cities and towns, or within unincorporated cities and towns, or on a limited access highway (j) (Matrix lines 5-1 through 5-7) N/A Region (k) Region Region Preservation project on managed access highway within incorporated cities and towns (h)(j) • Inside curb or EPS (i) • Outside curb or EPS (Matrix lines 5-1 through 5-7) N/A N/A Region HQ H&LP Region N/A Region City/Town FHWA = Federal Highway Administration HQ = WSDOT Headquarters H&LP = WSDOT Highways and Local Programs Office EPS = Edge of paved shoulder where curbs do not exist (a) These approval levels also apply to deviation processing for local agency work on a state highway. (b) See 330.04(4). (h) Applies to the area within the incorporated limits of cities and towns. (i) Includes raised medians. (j) For Bridge Replacement projects in the preservation program, follow the approval level specified for improvement projects. (k) See Chapters 1430 and 1435 for guidance on access deviations. Design Approval Level > Figure 330-2b Design Manual M 22-01 Design Documentation, Approval, and Process Review May 2006 Page 330-11 Item Approval Authority Region HQ FHWA Program Development Work Order Authorization X X Public Hearings Corridor Hearing Summary X Design Summary X Access Hearing Plan X Access Findings and Order X Environmental By Classification Summary (ECS) NEPA XClass l NEPA (EIS) XClass l SEPA (EIS) XClass ll NEPA *Programmatical Categorical Exclusion (CE) XClass II NEPA — Documented Categorical Exclusion (CE) XClass ll SEPA — Categorical Exemption (CE) XClass lll NEPA — Environmental Assessment (EA) XSEPA Check List X Design Design Deviations Experimental Features X X
|
{
"page_id": null,
"source": 7320,
"title": "from dpo"
}
|
Environmental Review Summary X Final Design Decisions Summary X X Final Project Definition X Access Point Decision Report X Non-Interstate Interchange Access Point Report X Interchange Plans X X Intersection Plans X X Right of Way Plans X Monumentation Map X Materials Source Report X Pavement Determination Report X Project Design Approval Approvals > Figure 330-3a Design Documentation, Approval, and Process Review Design Manual M 22-01 Page 330-12 May 2006 Item Approval Authority Region HQ FHWA Design Resurfacing Report X Signal Permits X Geotechnical Report X Tied Bids X X Bridge Design Plans (Bridge Layout) X X Hydraulic Report X X Preliminary Signalization Plans X Rest Area Plans X Roadside Restoration Plans X X Structures Requiring TS&L’s X X Wetland Mitigation Plans X X Wetland Mitigation Planting Plans X X Grading Plans X X Continuous Illumination – Main Line X Project Control Form X X X Normal procedure * If on the preapproved list Notes: Federal aid projects only. Environmental and Engineering Programs Director approval. State Design Engineer approval. Right of Way Plans Engineer approval. Refer to Chapter 210 for approval requirements. Final review & concurrence required at the region prior to submittal to approving authority. Final review & concurrence required at HQ prior to submittal to approving authority. Refer to Figures 330-2a & 330-2b for design approval level. Applies to new/reconstruction projects on Interstate routes. HQ Project Control & Reporting approval. Include channelization details. Certified by the responsible professional licensee. Submit to HQ Mateirals Branch for review and approval. Approved by region’s Administrator. See
|
{
"page_id": null,
"source": 7320,
"title": "from dpo"
}
|
23 CFR 635.111. See M 23-03, Hydraulics Manual for additional guidance. Region to submit Hydraulic Report. Refer to Hydraulics Manual . Applies only to regions with a Landscape Architect. Applies only to regions without a Landscape Architect. Approved by State Traffic Engineer. Consult HQ Project Control & Reporting for clarification on approval authority. Approvals > Figure 330-3b Design Manual M 22-01 Design Documentation, Approval, and Process Review May 2006 Page 330-13 Item New/ Reconstruction (Interstate only) NHS and Non-NHS DBE/training goals* ** (a) (a) Right of way certification for federal aid projects FHWA (b) FHWA (b) Right of way certification for state funded projects Region (b) Region (b) Railroad agreements (c) (c) Work performed for public or private entities* Region State force work* FHWA 3 3(d) Use of state furnished stockpiled materials* FHWA Region Stockpiling materials for future projects* FHWA Region Work order authorization 5 5 Ultimate reclamation plan approval through DNR Region Region Proprietary item use* FHWA 4 Mandatory material sources and/or waste sites* FHWA Region Nonstandard bid item use* Region Region Incentive provisions FHWA (e) Nonstandard time for completion liquidated damages* FHWA (e) (e) Interim liquidated damages* (f) (f) Notes: This work requires a written agreement. Region approval subject to $250,000 limitation. Use of state forces is subject to $50,000 limitation as stipulated in RCWs 47.28.030 and 47.28.035. Applies only to federal aid projects. However, document for all projects. Prior FHWA funding approval required for federal aid projects. Regional or Headquarters approval authority: (a) Office of Equal Opportunity (b) Real Estate Services (c) Design Office (d) Project Control & Reporting Office (e) Construction Office (f) Transportation Data Office References: **Advertisement and Award Manual *Plans Preparation Manual PS&E Process
|
{
"page_id": null,
"source": 7320,
"title": "from dpo"
}
|
Approvals > Figure 330-4 Design Documentation, Approval, and Process Review Design Manual M 22-01 Page 330-14 May 2006 Document Required for FHWA Oversight Project Definition X Design Decisions Summary X Environmental Review Summary X Design Variance Inventory (and supporting information for DEs, EUs not upgraded, and deviations) X Cost Estimate X SEPA & NEPA documentation X Design Clear Zone Inventory (see Chapter 700) X Interchange plans, profiles, roadway sections X Access Point Decision Report (if requesting new or revised access points) X Corridor or Project analysis (see Chapter 325) X Traffic projections and analysis Accident analysis Right of Way plans Work zone traffic control strategy Record of Survey or Monumentation Map Documentation of decisions to differ from WSDOT design guidance Documentation of decisions for project components for which there is no WSDOT design guidance Paths and Trails Calculations Notes: See Design Documentation Check List at for a complete list of project documentation requirements. Required for NHS highways, recommended for all highways. See Plans Preparation Manual. Common Components of Design Documentation Package > Figure 330-5 Design Manual M 22-01 Design Documentation, Approval, and Process Review May 2006 Page 330-15 1. Overview (a) The safety or improvement need that the project is to meet (b) Description of the project as a whole (c) Highway classification and applicable design matrix (d) Funding sources (e) Evidence of deviations approved for previous projects (same location) 2. Design Alternatives in Question (a) Existing Conditions and Design Data • Location in question • Rural, urban, or developing • Route development plan • Environmental issues • Right of way issues • Number of lanes and existing geometrics • Present and 20 year projected ADT • Design speed, posted speed and operating speed • Percentage of trucks • Terrain designation • Managed
|
{
"page_id": null,
"source": 7320,
"title": "from dpo"
}
|
Access or Limited Access (b) Accident Summary and Analysis (c) Design Using the Design Manual criteria • Description • Cost estimate • B/C ratio • Advantages and disadvantages • Reasons for considering other designs (d) Other Alternatives (may include “No-build” alternative) • Description • Cost estimate • B/C ratio • Advantages and disadvantages • Reasons for rejection (e) Selected design requiring justification or documentation to file • Description • Cost estimate • B/C ratio • Advantages and disadvantages 3. Concurrences, Approvals, and Professional Seals Deviation and Evaluate Upgrade Request/Documentation Content List > Figure 330-6 Design Manual M 22-01 Basic Design Level May 2006 Page 410-1 # Chapter 410 Basic Design Level 410.01 General 410.02 Required Basic Safety Items of Work 410.03 Minor Safety and Minor Preservation Work ## 410.01 General Basic design level (B) preserves pavement structures, extends pavement service life, and maintains safe operations of the highway. The basic design level includes restoring the roadway for safe operations and, where needed, may include safety enhancement. Flexibility is provided so that other conditions can be enhanced while remaining within the scope of pavement preservation work. The required safety items of work listed below may be programmed under a separate project from the paving project as long as there is some benefit to the delay, the safety features remain functional, and the work is completed within two years after the completion of the paving project. If some of the required items are separated from the paving project, maintain a separate documentation file that addresses the separation of work during the two‑year time period. For bituminous surface treatment projects on non‑NHS routes, the separation of required safety items is not limited to the two years stated above. The safety work can be accomplished separately using a corridor‑by‑corridor approach. ## 410.02 Required Basic
|
{
"page_id": null,
"source": 7320,
"title": "from dpo"
}
|
Safety Items of Work For basic design level (B), the following items of work are required: • Install and replace delineation in accordance with Chapter 830 • Install and replace rumble strips in accordance with the matrices and Chapter 700 • Adjust existing features that are affected by resurfacing, such as monuments, catch basins, and access covers • Adjust guardrail height in accordance with Chapter 710 • Replace deficient signing, as needed, using current standards. This does not include replacement of sign bridges or cantilever supports • Relocate, protect, or provide breakaway features for sign supports, luminaires, and WSDOT electrical service poles inside the design clear zone • Restore sight distance at public road intersections and the inside of curves through low cost measures if they are available such as removal or relocation of signs and other obstructions, and cutting of vegetative matter • Upgrade nonstandard bridge rail in accordance with the matrices and Chapter 710 • Upgrade barrier terminals and bridge end protection, including transitions, in accordance with Chapter 710 • Restore the cross slope to 1.5 percent when the existing cross slope is flatter than 1.5 percent and, in the engineer’s judgment, the steeper slope is needed to solve highway runoff problems in areas of intense rainfall ## 410.03 Minor Safety and Minor Preservation Work Consider the following items, where appropriate, within the limits of a pavement preservation project: • Spot safety enhancements. These are modifications to isolated roadway or roadside features that, in the engineer’s judgment, reduce potential accident frequency or severity • When recommended by the region Traffic Engineer, additional or improved channelization to address intersection related accident concerns, where sufficient pavement width and structural adequacy exist or can be obtained. With justification, channelization improvements may be implemented, with lane and shoulder widths no less than
|
{
"page_id": null,
"source": 7320,
"title": "from dpo"
}
|
the Basic Design Level Design Manual M 22-01 Page 410-2 May 2006 design criteria specified in the “Rechannelize Existing Pavement” projects presented in Chapter 340. Consider the impacts to all roadways users. Consider illumination of these improvements. Document decisions when full illumination is not provided, including an analysis of the frequency and severity of nighttime accidents. • Roadside safety hardware (such as guardrail, signposts, impact attenuators) • Addressing Location 1 Utility Objects in accordance with the Utilities Accommodation Policy , M 22‑86 Consider the following items when restoration, replacement, or completion is necessary to assure that an existing system can function as intended: • Right of way fencing • Drainage • Illumination • Electrical • Pedestrian and bicycle use Examples of the above include, but are not limited to, the following: installing short sections of fence needed to control access, replacing grates that are a hazard to bicycles, upgrading electrical system components that require excessive maintenance, and beveling culverts. Design Manual M 22-01 Modified Design Level > May 2006 Page 430-1 # Chapter 430 Modified Design Level ## 430.02 Design Speed When applying modified design level to a project, select a design speed for use in the design process that reflects the character of the terrain and the type of highway. The desirable design speed for modified design level is given in Figure 430-1.The minimum design speed is not less than the posted speed, or the proposed posted speed. (See Chapter 440 for additional information on design speed.) Document which speed was used, include any supporting studies and data. > Route Type Posted Speed Desirable Design Speed > Freeways All 10 mph over the posted speed non-Freeways 45 mph or less Not less than the posted speed Over 45 mph 5 mph over posted speed Desirable Design Speed > Figure
|
{
"page_id": null,
"source": 7320,
"title": "from dpo"
}
|
430-1 When the posted speed exceeds the design speed for existing geometric features that are to remain in place (curve radius, superelevation, sight distance, or other elements that the design speed controls) one of two choices must be made: When appropriate, work with the region Traffic Office to lower the posted speed to be consistent with the existing design speeds for the geometric features on the facility. A corridor analysis can be completed in order to leave the posted speed unchanged and identify all design elements that do not meet the criteria for the existing posted speed. Identify each appropriate location for cautionary signing (including road approach sight distance) and work with the region Traffic Office to install the cautionary signing as provided for in the MUTCD (either by contract or region sign personnel). Consult with and obtain guidance from Region Project Develpment leadership prior to progressing with the corridor analysis and the design. •• 430.01 General 430.02 Design Speed 430.03 Alignment 430.04 Roadway Widths 430.05 Cross Slope 430.06 Side Slopes 430.07 Bike and Pedestrian 430.08 Bridges 430.09 Intersections 430.10 Documentation ## 430.01 General Modified design level (M) preserves and improves existing roadway geometrics, safety, and operational elements. This chapter provides the design that is unique to the modified design level. The modified design level design criteria have been developed to apply to all applicable functional classes. As a result, for the lower volumes and urban highways modified design level design criteria might exceed full level design criteria. In these cases, full level design criteria may be used. Projects developed to correct a deficiency, must address all design elements contributing to that deficiency, even when those elements meet modified design level design criteria Design elements that do not have modified design level guidance include: Lane Transitions, Chapter 620 On and
|
{
"page_id": null,
"source": 7320,
"title": "from dpo"
}
|
off connections, Chapter 940 Access control, Chapter 1420 Clear zone, Chapter 700 Signing, delineation, and illumination, Chapters 820, 830, and 840 Basic safety, Chapter 410 Structural capacity, Chapter 1120 Vertical clearance, Chapter 1120 Intersection sight distance, Chapter 910 Traffic Barriers, Chapter 710 ••••••••••Modified Design Level Design Manual M 22-01 > Page 430-2 May 2006 ## 430.03 Alignment (1) Horizontal Alignment Consideration of horizontal alignment for modified design level is normally limited to curves. Curve design is controlled by the design speed [430.02], superelevation [430.03(4)], and stopping sight distance [430.03(3)]. Identify major modifications to horizontal alignment in the Project Summary. Total removal of pavement and reconstruction of the subgrade are examples of major modifications. (2) Vertical Alignment Vertical alignment consists of a series of profile grades connected by vertical curves. (a) Vertical curves. Stopping sight distance controls crest vertical curves. Figure 430-8 gives the minimum curve length for crest vertical curves to remain in place for modified design level stopping sight distance. See 430.03(3) for additional information on modified design level stopping sight distance. When modified design level is being applied, existing sag vertical curves are not normally addressed. When either a crest or a sag vertical curve is to be reconstructed, use full design level design criteria (see Chapters 630 and 650). (b) Profile Grades. When applying modified design level, profile grades generally are not flattened. However, corrective action may be justified for combinations of steep grades and restricted horizontal or vertical curvature. Identify major modifications to vertical alignment in the Project Summary. Total removal of pavement and reconstruction of the subgrade are examples of major modifications. When changing the profile grade, see Chapter 440 for the maximum grade for the functional class of the route. (3) Stopping Sight Distance Stopping sight distance is a controlling factor for both vertical
|
{
"page_id": null,
"source": 7320,
"title": "from dpo"
}
|
and horizontal alignment. A 2-foot object height is used for modified design level stopping sight distance evaluation. Figure 430-2 gives the minimum stopping sight distances allowed to remain in place. > Design Speed (mph) Design Stopping Sight Distance (ft) > 40 or less 155 45 200 50 250 55 305 60 360 65 425 70 495 75 570 80 645 Stopping Sight Distance, Modified Design Level > Figure 430-2 (a) Stopping Sight Distance for Horizontal Curves. For modified design level, use the existing lateral clearance to the sight obstruction and the curve radius to compare the existing condition to Figure 430-9 a. When reconstructing a horizontal curve, apply full design level criteria for sight distance. (See Chapter 650.) For Figure 430-9 a, an obstruction is any object with a height of greater than 2.75 feet above the roadway surface on the inside of a curve. Examples of possible obstructions are median barrier, guardrail, bridges, walls, cut slopes, wooded areas, and buildings. Objects between 2.75 feet and 2.00 feet above the roadway surface within the M distance might be a sight obstruction, depending on the distance from the roadway. See Figure 430-9b for guidance on determining if an object between 2.75 feet and 2.00 feet above the roadway surface is a sight obstruction. Design Manual M 22-01 Modified Design Level > May 2006 Page 430-3 (b) Stopping Sight Distance for Vertical Curves. For existing crest vertical curves use the algebraic difference in grades and the length of curve to compare the existing condition to the stopping sight distance requirements from Figure 430-2. Use the equations in Figure 430-3 or use Figure 430-8 to evaluate the existing curve. When a crest vertical curve is lengthened, the minimum sight distance is increased; however, the length of the roadway that has the minimum sight
|
{
"page_id": null,
"source": 7320,
"title": "from dpo"
}
|
distance is also increased. This results in a questionable benefit when the new sight distance is less than for full design level. Therefore, when the existing roadway is reconstructed to improve stopping sight distance, apply full design level criteria. (See Chapter 650.) > When sis less than L: > 2158 A2 > sL= > When sis greater than L: > A2158 > −=sL2 > Where: L = Length of vertical curve, ft > s= Sight distance, ft (Figure 430-2) A = Absolute value of the algebraic difference in grades, % Minimum Crest Vertical Curve Length, Modified Design Level > Figure 430-3 (4) Superelevation Evaluate existing superelevation using the equation in Figure 430-4. When the existing superelevation equals or exceeds the value from the equation, the modified design level design criteria is met. When modifying the superelevation of an existing curve where the existing pavement is to remain in place, use the equation in Figure 430-4 to determine the required superelevation. For curves on realigned roadways or where the roadway is to be rebuilt, provide full design level superelevation (See Chapter 642). > fe−=R6.69V 2Where: R = Existing curve radius in ft. V = Design speed in mph from 430.02. > e= Superelevation rate in %. > f= Side friction factor from Figure 430-5. Minimum Superelevation, Modified Design Level > Figure 430-4 > Design Speed (mph) Side Friction Factor ( f) > 15 17.5 20 17 25 16.5 30 16 35 15.5 40 15 45 14.5 50 14 55 13 60 12 65 11 70 10 75 980 8 Side Friction Factor > Figure 430-5 ## 430.04 Roadway Widths Review route continuity and roadway widths. Select widths on the tangents to be consistent throughout a given section of the route. Make any changes where the route characteristics change. The design of
|
{
"page_id": null,
"source": 7320,
"title": "from dpo"
}
|
a project must not decrease the existing roadway width. Modified Design Level Design Manual M 22-01 > Page 430-4 May 2006 (1) Lane and Shoulder Width Lane and shoulder widths are shown in Figures 430-10 and 11 . Consider joint use with other modes of transportation in shoulder design. Minimum ramp lane and shoulder widths are shown on Figure 430-14. Use full design level lane and shoulder widths (See Chapter 940) for new and rebuilt ramps. (2) Turning Roadway Widths It might be necessary to widen the roadway on curves to accommodate large vehicles. The proposed roadway width for a curve shall not be less than that of the adjacent tangent sections. Widening of the total roadway width of a curve by less than 2-feet is not required for existing two-lane roadways that are to remain in place. (a) The two-lane two-way roadway width of a curve may not be less than that shown in Figure 430-12 a or, if the internal angle (delta) is less than 90 degrees, Figure 430-12b. The minimum total roadway width from Figure 430-12 a or 12b may include the shoulder. When the shoulder is included, full-depth pavement is required. (b) One-way roadway and Ramp widths on a curve are shown in Figure 430-6 for existing roadways that are to remain in place. Use full design level width (See Chapters 641 and 940) for new and rebuilt ramps. (3) Median Width Minimum median widths are given in Figure 430-10. ## 430.05 Cross Slope On all tangent sections, the normal cross slopes of the traveled way are 2 percent. If a longitudinal contiguous section of pavement is to be removed or is on a reconstructed alignment, or if a top course is to be placed over existing pavement, design the restored pavement cross slope to full
|
{
"page_id": null,
"source": 7320,
"title": "from dpo"
}
|
design level criteria (See Chapter 640). The algebraic difference in cross slopes is an operational factor during a passing maneuver on a two-lane two-way roadway. Its influence increases when increased traffic volumes decrease the number and size of available passing opportunities. A somewhat steeper cross slope may be necessary to facilitate pavement drainage in areas of intense rainfall, even though this might be less desirable from the operational point of view. In such areas, the design cross slopes may be increased to 2.5 percent with an algebraic difference of 5 percent. For existing pavements, cross slopes within a range of 1 to 3 percent may remain if there are no operational or drainage problems and — on a two-lane two-way roadway — the following conditions are met: The algebraic difference is not greater than 4 percent where the ADT is greater than 2,000. The algebraic difference is not greater than 5 percent where the ADT is 2,000 or less. The algebraic difference is not greater than 6 percent and the road is striped or signed for no passing. > Curve > Radius (ft) One-Lane (1) Two-Lane (2) > Tangent to 1,001 20 24 500 21 25 400 21 25 300 22 25 200 22 26 150 23 26 100 25 28 75 27 29 50 30 31 (1) Includes the shoulder width. (2) Add shoulder widths from Figure 430-10 for highways and 10 ft for ramps. One-Way Roadway and Ramp Turning Roadway Widths, Modified Design Level > Figure 430-6 •••Design Manual M 22-01 Modified Design Level > May 2006 Page 430-5 For a two-lane two-way roadway, provide an algebraic difference to meet the appropriate conditions stated above, except when facilitating drainage in areas of intense rainfall. When applying modified design level to a road with bituminous surface treatment (BST), cross
|
{
"page_id": null,
"source": 7320,
"title": "from dpo"
}
|
slope correction is not required on the basis of algebraic differences alone. To maintain or restore curb height, consider lowering the existing pavement level and correcting cross slope by grinding before an asphalt overlay. The cross slope of the shoulder may be steepened to maximize curb height and minimize other related impacts. The shoulder may be up to 6 percent with a rollover between the traveled way and the shoulder of no more than 8 percent. See Chapter 640 for additional information. ## 430.06 Side Slopes (1) Fill/Ditch Slopes Foreslopes (fill slopes and ditch inslopes) and cut slopes are designed as shown in the Fill and Ditch Slope Selection Table on Figure 430-13 for modified design level main line roadway sections. After the foreslope has been determined, use the guidance in Chapter 700 to determine the need for a traffic barrier. When a crossroad or road approach has steep foreslopes, there is the possibility that an errant vehicle might become airborne. Therefore, flatten crossroad and road approach foreslopes to 6H:1V where practical and at least to 4H:1V. Provide smooth transitions between the main line foreslopes and the crossroad or road approach foreslopes. Where possible, move the crossroad or road approach drainage away from the main line. This can locate the pipe outside the design clear zone and reduce the length of pipe required. (2) Cut Slopes Existing stable backslopes (cut slopes) are to remain undisturbed unless disturbed by other work. When changes are required to a cut slope, design them as shown in the Cut Slope Selection Table on Figure 430-13. ## 430.07 Bike and Pedestrian Sidewalk ramps must be addressed for Americans with Disabilities Act of 1990 (ADA) compliance on projects that include hot mix asphalt (HMA) or Portland cement concrete pavement (PCCP) overlays or inlays. Evaluate existing sidewalk
|
{
"page_id": null,
"source": 7320,
"title": "from dpo"
}
|
ramps for compliance. Construct ADA compliant sidewalk ramps as required. On Interstate Pavement Rehab./Resurface projects (See Chapter 325) that include HMA or PCCP overlays, or inlays on ramps or crossroads, sidewalk ramps must be addressed for ADA compliance. Other bicycle or pedestrian elements are design exceptions on HMA or PCCP overlays or inlays on Interstate ramps or crossroads. Projects that widen the roadway, or change the traffic configuration by reducing the shoulders to add turn lanes are considered alterations of the roadway. Such alterations include a requirement to address ADA compliance for sidewalk ramps. See Chapter 1025 for guidance on pedestrian facilities. ## 430.08 Bridges Design all new and replacement bridges to full design level (See Chapter 440) unless a corridor or project analysis justifies the use of modified design level lane and shoulder widths. Evaluate bridges to remain in place using Figures 430-10 and 11 . Whenever possible, continue the roadway lane widths across the bridge and adjust the shoulder widths. Consider joint use with other modes of transportation in lane and shoulder design. See Chapters 1020, 1025, 1050, and 1060. Modified Design Level Design Manual M 22-01 > Page 430-6 May 2006 ## 430.09 Intersections Except as given below, design intersections to meet the requirements in Chapter 910. (1) Turn Radii The intersection turn radii (or right-turn corners) are controlled by the design vehicle. Figure 430-7 is a guide for determining the design vehicle for modified design level. Perform a field review to determine intersection type, types of vehicles that use the intersection, and adequacy of the existing geometrics. When the crossroad is a city street or county road, consider the requirements of the city or county when selecting a design vehicle. Design right turn corners to meet the requirements of Chapter 910 using the design vehicle selected
|
{
"page_id": null,
"source": 7320,
"title": "from dpo"
}
|
from Figure 430-7 or from the field review. (2) Angle The allowable angle between any two respective legs is between 60° and 120°. When realignment is required to meet this angle requirement, consider realigning to an angle between 75°and 105°. Intersection Type Design Vehicle Junction of Major Truck Routes WB-67 Junction of State Routes WB-40 Ramp Terminals WB-40 Other Rural SU (1) Urban Industrial SU (1) Urban Commercial P(1) Residential P(1) (1) When the intersection is on a transit or school bus route, use the BUS design vehicle. See Chapter 1060 for additional guidance for transit facilities and for the BUS turning path templates. Design Vehicles, Modified Design Level > Figure 430-7 ## 430.10 Documentation A list of the documents that are to be preserved [in the Design Documentation Package (DDP) or the Project File (PF)] is on the following web site: Design Manual M 22-01 Modified Design Level May 2006 Page 430-7 0 500 1000 1500 2000 0246810 Length of Vertical Curve (ft) > Algebraic Difference of Grade, A (%) > 40 mph 45 mph 50 mph 55 mph 60 mph 65 mph 70 mph 75 mph 80 mph When the intersection of the algebraic difference of grade with the length of vertical curve is below the selected design speed line, modified design level design criteria is met. Evaluation for Stopping Sight Distance for Crest Vertical Curves, Modified Design Level Figure 430-8 Modified Design Level Design Manual M 22-01 Page 430-8 May 2006 M is the distance in feet from the center line of the inside lane to the obstruction. Obstruction is a cut slope or other object 2.75 ft or more above the inside lane. Objects between 2.75 ft and 2.00 ft above the roadway surface within the M distance might be a sight obstruction, depending on
|
{
"page_id": null,
"source": 7320,
"title": "from dpo"
}
|
the distance from the roadway. See Figure 430-9b. > Lateral Clearance, M (ft) When the intersection of the lateral clearance (M) with the curve radius (R) falls above the curve for the selected design speed, modified design criteria is met. Evaluation for Stopping Sight Distance for Horizontal Curves, Modified Design Level Figure 430-9a Design Manual M 22-01 Modified Design Level > May 2006 Page 430-9 ML of lane CSight obstruction between 2.00' & 2.75' Line of sight 2.75' at the midpoint 2.00' 3.50' hXCs Edge of roadway When +≤ > s CXh 5.1 2 modified design criteria is met. Where: M = Lateral clearance for sight distance (ft) See Figure 430-9a Cs = Stopping sight distance chord (ft) X = Distance from the sight obstruction to the end of the sight distance chord (ft) h = Height of sight obstruction above the inside lane. Evaluation for Stopping Sight Distance Obstruction for Horizontal Curves , Modified Design Level > Figure 430-9b Modified Design Level Design Manual M 22-01 Page 430-10 May 2006 Multilane Divided Multilane Undivided Trucks Under 10% Trucks 10% and Over Trucks Under 10% Trucks 10% and Over Design Class MDL-1 MDL-2 MDL-3 MDL-4 MDL-5 MDL-6 MDL-7 MDL-8 Current ADT (1) Under 4000 Over 4000 Under 4000 Over 4000 Under 4000 Over 4000 Under 4000 Over 4000 Design Speed See Figure 430-1 Traffic Lanes Number Width 4 or more 11 ft 4 or more 11 ft 4 or more 11 ft 4 or more 12 ft 4 or more 11 ft 4 or more 11 ft 4 or more 11 ft 4 or more 12 ft Parking Lanes Urban None None None None 8 ft 8 ft (2) 8 ft 8 ft (2) Median Width Rural Urban Existing Existing Existing Existing Existing Existing Existing Existing 2 ft 2
|
{
"page_id": null,
"source": 7320,
"title": "from dpo"
}
|
ft 4 ft 2 ft 4 ft 2 ft 4 ft 2 ft Shoulder Width Right (3) Left (4) 4 ft 2 ft 6 ft 2 ft 4 ft 2 ft 6 ft 2 ft 4 ft 6 ft (5) 4 ft 6 ft (5) Minimum Width for Bridges to Remain in Place (6) (7) (8) 24 ft (9) 26 ft (9) 24 ft (9) 26 ft (10) 48 ft (9) 50 ft (9) (11) 50 ft (9) (11) 54 ft (10) (11) Minimum Width for Rehabilitation of Bridges to Remain in Place (6) (8) (12) 28 ft (9) 30 ft (9) 28 ft (9) 32 ft (10) 54 ft (9) 60 ft (9) (11) (13) 56 ft (9) (11) 64 ft (10) (11) (13) Minimum Width for Replacement Bridges Full Design Level Applies (14) Access Control See Chapters 1430 and 1435 and the Master Plan for Limited Access Highways, or WAC 468‑52 and the region’s Highway Access Management Classification Report Notes: (1) If current ADT is approaching a borderline condition, consider designing for the higher classification. (2) Parking restricted when ADT is over 15,000. (3) When curb section is used, the minimum shoulder width from the edge of traveled way to the face of curb is 4 feet. In urban areas, see Chapter 440. On a route identified as a local, state, or regional significant bicycle route the minimum shoulder width is 4 feet (See Chapter 1020). (4) When a curb section is used, the minimum shoulder width from the edge of traveled way to the face of the curb is 1 foot on the left. (5) May be reduced by 2 feet under urban conditions. (6) Width is the clear distance between curbs or rails, whichever is less. (7) Use these widths when a bridge within the project
|
{
"page_id": null,
"source": 7320,
"title": "from dpo"
}
|
limits requires deck treatment or thrie beam retrofit only. (8) For median widths 25 feet or less, see Chapter 1120. (9) Add 11 feet for each additional lane. (10) Add 12 feet for each additional lane. (11) Includes a 4-foot median, which may be reduced by 2 feet under urban conditions. (12) Use these widths when a bridge within the project limits requires any work beyond the treatment of the deck such as bridge rail replacement, deck replacement, or widening. (13) Includes 6-foot shoulders — may be reduced by 2 feet on each side under urban conditions. (14) Modified design level lane and shoulder widths may be used when justified with a corridor or project analysis. Multilane Highways and Bridges, Modified Design Level Figure 430-10 Design Manual M 22-01 Modified Design Level May 2006 Page 430-11 Two-Lane Highways Trucks Under 10% Trucks 10% and Over Design Class MDL-9 MDL-10 MDL-11 MDL-12 MDL-13 MDL-14 Current ADT (1) Under 1000 1000-4000 Over 4000 Under 1000 1000-4000 Over 4000 Design Speed See Figure 430-1 Traffic Lane Width (2) 11 ft 11 ft 11 ft 11 ft 11 ft 12 ft Parking Lanes Urban 8 ft 8 ft 8 ft (3) 8 ft 8 ft 8 ft (3) Shoulder Width (4) 2 ft 3 ft (5) 4 ft 2 ft 3 ft (5) 4 ft Minimum Width for Bridges to Remain in Place (6)(7) 22 ft (8) 24 ft 28 ft 22 ft (8) 24 ft 28 ft Minimum Width for Rehabilitation of Bridges to Remain in Place (7)(9) 28 ft (10) 32 ft 32 ft 28 ft (10) 32 ft 32 ft Minimum Width for Replacement Bridges Full Design Level Applies (11) Access Control See Chapters 1430 and 1435 and the Master Plan for Limited Access Highways, or WAC 468-52 and the region’s
|
{
"page_id": null,
"source": 7320,
"title": "from dpo"
}
|
Highway Management Classification Report. Notes: (1) If current ADT is approaching a borderline condition, consider designing for the higher classification. (2) See Figures 430-12a and 12b for turning roadways. (3) Parking restriction recommended when ADT exceeds 7,500. (4) When a curb section is used, the minimum shoulder width from the edge of traveled way to the face of curb is 4 feet. In urban areas, see Chapter 440. On a route identified as a local, state, or regional significant bicycle route the minimum shoulder width is 4 feet (See Chapter 1020). (5) For design speeds of 50 mph or less on roads of 2,000 ADT or less, width may be reduced by 1 foot, with justification. (6) Use these widths when a bridge within the project limits requires deck treatment or thrie beam retrofit only. (7) Width is the clear distance between curbs or rails, whichever is less. (8) 20 feet when ADT 250 or less. (9) Use these widths when a bridge within the project limits requires any work beyond the treatment of the deck such as bridge rail replacement, deck replacement, or widening. (10) 26 feet when ADT 250 or less. (11) Modified design level lane and shoulder widths may be used when justified with a corridor or project analysis. Two-Lane Highways and Bridges, Modified Design Level Figure 430-11 Modified Design Level Design Manual M 22-01 Page 430-12 May 2006 Radius of Center Line R (ft) Minimum Total Roadway Width W (ft) Minimum Lane Width L (ft) Tangent 26 11 900 26 11 800 27 12 700 27 12 600 28 12 500 28 12 400 29 12 350 30 12 300 31 12 250 33 13 200 35 13 150 39 13 Note: Also see minimums from Figure 430-11. If the minimum total roadway width is greater
|
{
"page_id": null,
"source": 7320,
"title": "from dpo"
}
|
than the sum of the shoulders and lane widths, apply the extra width to the inside of the curve. Minimum Total Roadway Widths for Two-Lane Two-Way Highway Curves, Modified Design Level Figure 430-12a Design Manual M 22-01 Modified Design Level May 2006 Page 430-13 Notes: May be used when the internal angle (delta) is less than 90 degrees. If result is less than the total roadway width from Figure 430-11, use the greater. Minimum Total Roadway Widths for Two-Lane Two-Way Highway Curves, Modified Design Level Figure 430-12b Modified Design Level Design Manual M 22-01 Page 430-14 May 2006 Height of Cut (ft) Slope not Steeper than (5) 0 - 5 4H:1V 5 - 20 3H:1V over 20 2H:1V Cut Slope Selection Table Height of Fill/Depth of Ditch (ft) Slope not Steeper than 0 - 20 4H:1V 20 - 30 3H:1V over 30 2H:1V (6)(7) Fill and Ditch Slope Selection Table Notes: (1) See Figures 430-10 and 11 for minimum roadway widths and Figures 430-12a and 12b for turning roadway widths. (2) Widen and round embankments steeper than 4H:1V. (3) See Chapter 640 for shoulder slope requirements. (4) Minimum ditch depth is 2 feet for design speeds over 40 mph and 1.5 feet for design speeds 40 mph or less. (5) Or as recommended by the soils or geothechnical report. Refer to Chapter 700 for clear zone and barrier requirements (6) Where practical, provide flatter slopes for the greater fill heights and ditch depths. (7) Fill slopes up to 1 1/2H:1V may be used where favorable soil conditions exist. Refer to Chapter 640 for additional details and Chapter 700 for clear zone and barrier requirements. Main Line Roadway Sections, Modified Design Level Figure 430-13 Design Manual M 22-01 Modified Design Level May 2006 Page 430-15 Notes: (1) See Fill and Ditch
|
{
"page_id": null,
"source": 7320,
"title": "from dpo"
}
|
Slope Selection Table on Figure 430-13. (2) See Cut Slope Selection Table on Figure 430-13 (3) Minimum ditch depth is 2 feet for design speeds over 40 mph and 1.5 feet for design speeds at and under 40 mph. (4) See 430.04(2)(b) and Figure 430-6 for minimum ramp width. (5) See Chapter 640 for shoulder slope requirements. (6) The median width of a two‑lane two‑way ramp shall not be less than that required for traffic control devices and their required shy distances. (7) Widen and round embankments steeper than 4H:1V. (8) Existing 6 feet may remain. When the roadway is to be widened, 8 feet is preferred. Ramp Roadway Sections, Modified Design Level Figure 430-14 Design Manual M 22-01 Design of Pavement Structure May 2006 Page 520-1 Chapter 520 Design of Pavement Structure 520.01 Introduction 520.02 Estimating Tables ## 520.01 Introduction Detailed criteria and methods that govern pavement design are in the following: WSDOT Pavement Guide – Interactive issued only on CD ROM. Pavement Type Selection Protocol (PTSP) including the Dowel Bar Type Selection Protocol (DBTSP) located online at: ## 520.02 Estimating Tables Figures 520-1 through 520-5h are to be used when detailed estimates are required. They are for pavement sections, shoulder sections, stockpiles, and asphalt distribution. Prime coats and fog seal are in Figure 520-2a. Design of Pavement Structure Design Manual M 22-01 Page 520-2 January 2005 Unit Dry Weight Type of Material Truck Measure Compacted on Roadway lb/cy T/cy lb/cy T/cy Ballast 3100 1.55 3900 1.95 Crushed Surfacing Top Course 2850 1.43 3700 1.85 Crushed Surfacing Base Course 2950 1.48 3700 1.85 Screened Gravel Surfacing 3700 1.85 **Gravel Base 3400 – 3800 1.70 – 1.90 Shoulder Ballast 2800 1.40 Maintenance Sand 3/8” – 0 2900 1.45 Mineral Aggregate 2” – 1” 2600 1.30 Mineral Aggregate 1 3/4”
|
{
"page_id": null,
"source": 7320,
"title": "from dpo"
}
|
– 3/4” 2600 1.30 Mineral Aggregate 1 1/2” – 3/4” 2550 1.28 Mineral Aggregate 1” – 3/4” 2500 1.25 Mineral Aggregate 3/4” – 1/2” 2400 1.20 Mineral Aggregate 1 1/4” – 1/4’” 2600 1.30 Mineral Aggregate 1” – 1/4” 2600 1.30 Mineral Aggregate 7/8” – 1/4” 2550 1.28 Mineral Aggregate 3/4” – 1/4” 2500 1.25 Mineral Aggregate 5/8” – 1/4” 2650 1.33 Mineral Aggregate 1/2” – 1/4” or #4 2600 1.30 Mineral Aggregate 1/4” or #4 – 0 2900 1.45 Concrete Aggr. No. 2 (1 1/4” - #4) 3000 1.50 Concrete Sand (Fine Aggregate) 2900 1.45 Crushed Cover Stone 2850 1.43 ** 3,700 lb/cy (1.85 tons/cy) is recommended as the most suitable factor; however, if the grading approaches the coarseness of ballast, the factor would approach 3,800 lb/cy (1.90 tons/cy), and if the grading contains more than 45% sand, the factor would decrease, approaching 3,400 lb/cy (1.70 tons/cy) for material that is essentially all sand. General Notes: Weights shown are dry weights and corrections are required for water contents. The tabulated weights for the materials are reasonably close; however, apply corrections in the following order: For specific gravity: Wt. = tabular wt. x specific gravity on surface report 2.65 For water content: Wt. = tabular wt. x (1 + free water % in decimals) If they are to be stockpiled, increase required quantities by 10 percent to allow for waste. Direct attention to the inclusion of crushed surfacing top course material that may be required for keystone when estimating quantities for projects having ballast course. Estimating – Miscellaneous Tables > Figure 520-1 Design Manual M 22-01 Traffic Analysis > May 2006 Page 610-1 # Chapter 610 Traffic Analysis 610.01 General 610.02 References 610.03 Design Year 610.04 Definitions 610.05 Travel Forecasting (Transportation Modeling) 610.06 Traffic Analysis 610.07 Scope of Traffic Impact
|
{
"page_id": null,
"source": 7320,
"title": "from dpo"
}
|
Analysis 610.08 Traffic Data 610.09 Traffic Impact Analysis Methodologies 610.10 Traffic Analysis Software 610.11 Mitigation Measures 610.12 Traffic Impact Analysis Report ## 610.01 General It is the Washington State Department of Transportation’s (WSDOT’s) responsibility to provide for an interconnected transportation system to ensure the mobility of people and goods. In order to achieve these objectives, traffic engineers determine whether the proposed improvements will satisfy future needs by comparing the forecast directional hourly volume with the traffic-handling capacity of an improved facility. Project traffic forecasts and capacity are used to establish the number of through lanes, the length of auxiliary lanes, signal timing, right of way requirements, and other characteristics, so that the facility can operate at an acceptable level of service through the design year. This chapter provides guidance and general requirements for traffic analyses. Specific requirements for a traffic analysis depend on a variety of factors. These include: • Project proponents (federal, state, local, and private sector). • Lead agency. • Legal requirements (laws, regulations, procedures, and contractual obligations). • Purpose of the traffic analysis. Along with these factors, examine capacity and safety needs, look at project benefits and costs, determine development impacts, and identify mitigation requirements. This Design Manual does not cover capacity analysis; see the latest version of the Highway Capacity Manual (HCM). ## 610.02 References Laws – Federal and state laws and codes that may pertain to this chapter include: Manual on Uniform Traffic Control Devices for Streets and Highways , USDOT, Federal Highway Administration (FHWA), National Advisory Committee on Uniform Traffic Control Devices, including the "Washington State Modifications to the MUTCD," Chapter 468-95 Washington Administrative Code (WAC), MUTCD > htm Revised Code of Washington (RCW), Chapter 43.21C, the State Environmental Policy Act (SEPA) The National Environmental Policy Act (NEPA) of 1969 Design Guidance –
|
{
"page_id": null,
"source": 7320,
"title": "from dpo"
}
|
Design guidance included by reference within the text includes: Highway Capacity Manual (HCM), latest edition, Transportation Research Board, National Research Council Roadway Delineation Practices Handbook ,FHWA report, Washington, DC, 1994 Sign Fabrication Manual , M 55-05, WSDOT Standard Plans for Road, Bridge, and Municipal Construction (Standard Plans), M 21-01, WSDOT “Trip Generation,” Institute of Transportation Engineers (ITE) Supporting Information – Other resources used or referenced in this chapter include: NCHRP Synthesis 306, Long-Term Pavement Practices , Transportation Research Board Development Services Manual, 3007.00, WSDOT Traffic Manual , M51-02, WSDOT Traffic Analysis Design Manual M 22-01 Page 610-2 May 2006 ## 610.03 Design Year Roadway geometric design must consider projected traffic for the opening year and the design year. The design year for new construction and reconstruction projects is given in Chapter 440. However, the design year for developer projects is often (but not always) the horizon year or build-out year. One early task for the traffic analyst is to determine the correct design year. ## 610.04 Definitions annual average daily traffic (AADT) The total volume of traffic passing a point or segment of a highway facility in both directions for one year divided by the number of days in the year. average daily traffic (ADT) The total volume during a given time period (in whole days): greater than one day and less than one year, divided by the number of days in that time period. capacity The maximum sustainable flow rate at which vehicles or persons can reasonably be expected to traverse a point or uniform segment of a lane or roadway during a specified time period under given roadway, geometric, traffic, environmental, and control conditions. Capacity is usually expressed as vehicles per hour (vph), passenger cars per hour (pcph), or persons per hour (pph). capture trips Trips that do
|
{
"page_id": null,
"source": 7320,
"title": "from dpo"
}
|
not enter or leave the traveled ways of a project’s boundary within a mixed-use development. design hourly volume (DHV) Computed by taking the annual average daily traffic times the K-factor. It can only be accurately determined in locations where there is a permanent traffic recording device active 365 days of the year. It correlates to the peak hour (see peak hour definition), but it is not equivalent. In some circumstances, it is necessary to use the peak hour data instead of DHV because peak hour can be collected using portable traffic recorders. directional design hour volume (DDHV) The traffic volume for the design hour in the peak direction of flow, in vehicles per hour. For example, if during the design hour, 60% of the vehicles traveled eastbound and 40% traveled westbound, then the DDHV for the eastbound direction would be the DHV x 0.60. K-factor The proportion of AADT occurring in the analysis hour is referred to as the K-factor, expressed as a decimal fraction (commonly called “K,” “K30,” or “K100”). The K30 is the thirtieth (K100 is the one-hundredth) highest peak hour divided by the annual average daily traffic. Normally, the K30 or K100 will be in the range of 0.09 to 0.10 for urban and rural areas. Average design hour factors are available on the web in the Transportation Data Office’s Annual Peak Hour Report. lead agency The public agency that has the principal responsibility for carrying out or approving a project. level of service (LOS) A qualitative measure describing operational conditions within a traffic stream, based on service measures such as speed, travel time, freedom to maneuver, traffic interruptions, comfort, and convenience. Six levels of service are defined for each type of facility that has analysis procedures available. Letters designate each level, from A to F, with
|
{
"page_id": null,
"source": 7320,
"title": "from dpo"
}
|
LOS A representing the best operating conditions and LOS F the worst. Each level of service represents a range of operating conditions and the driver’s perception of those conditions. Safety is not included in the measures that establish service levels. “pass-by” trips Pass-by trips are made as intermediate stops between an origin and a primary trip destination (for example, home to work, home to shopping). Design Manual M 22-01 Traffic Analysis > May 2006 Page 610-3 peak hour The 60-minute interval that contains the largest volume of traffic during a given time period. If a traffic count covers consecutive days, the peak hour can be an average of the highest hour across all of the days. An a .m . peak is simply the highest hour from the a .m ., and the p .m . peak is the highest from the p .m . Peak hour correlates to the DHV, but is not the same. However, it is close enough on items such as intersection plans for approval to be considered equivalent. project Activities directly undertaken by government, financed by government, or requiring a permit or other approval from government. “select zone” analysis A traffic model run, where the related project trips are distributed and assigned along a populated highway network. This analysis isolates the anticipated impact on the state highway network created by the project. ## 610.05 Travel Forecasting ## (Transportation Modeling) While regional models are available in most urban areas, they may not be the best tool for reviewing developments. Most regional models are macroscopic in nature and do not do a good job of identifying intersection-level development impacts without further refinement of the model. The task of refining the model can be substantial and is not warranted in many instances. The region makes the determination whether
|
{
"page_id": null,
"source": 7320,
"title": "from dpo"
}
|
a model or a trend line analysis can be used to take into account historical growth rates and background projects. This decision would be based on numerous factors including the type, scale, and location of the development. The regional model is generally more appropriate for larger projects that generate a substantial number of new trips. The Traffic Impact Analysis (TIA) clearly describes the methodology and process used in developing the forecast in support of the analysis of a proposed project. ## 610.06 Traffic Analysis The level of service (LOS) for operating state highway facilities is based upon measures of effectiveness (MOEs), per the latest version of the Highway Capacity Manual . These MOEs (see Figure 610-1) describe the measures best suited for analyzing state highway facilities, such as freeway segments, signalized intersections, on- or off-ramps, and others. Depending on the facility, WSDOT LOS thresholds are LOS C and LOS D on state highway facilities. The LOS threshold for developer projects is set differently. Refer to Chapter 4 of the Developer Services Manual . (1) Trip Generation Thresholds The following criteria are used as the starting point for determining when a TIA is needed: • When a project changes local circulation networks that impact a state highway facility involving direct access to the state highway facility; includes a nonstandard highway geometric design feature, and others. • The potential risk for a traffic incident is significantly increased due to congestion-related collisions, nonstandard sight distance considerations, increases in traffic conflict points, and others. • When a project affects state highway facilities experiencing significant delay; LOS “C” in rural areas or “D” in urban areas. Note: A traffic analysis can be as simple as providing a traffic count or as complex as a microscopic simulation. The appropriate level of analysis is determined by the
|
{
"page_id": null,
"source": 7320,
"title": "from dpo"
}
|
specifics of a project, the prevailing highway conditions, and the forecasted traffic. For developer projects, different thresholds may be used depending on local agency codes or interagency agreements (or both) between WSDOT and local agencies. For more information, refer to Chapter 4 of the Development Services Manual. Traffic Analysis Design Manual M 22-01 > Page 610-4 May 2006 > TYPE OF FACILITY MEASURE OF EFFECTIVENESS (MOE) > Basic Freeway Segments Density (pc/mi/ln) Ramps Density (pc/mi/ln) Ramp Terminals Delay (sec/veh) Multilane Highways Density (pc/mi/ln) Two-Lane Highways Percent-Time-Spent Following Average Travel Speed (mi/hr) Signalized Intersections Control Delay Per Vehicle (sec/veh) Unsignalized Intersections Average Control Delay Per Vehicle (sec/veh) Urban Streets Average Travel Speed (mi/hr) Measures of Effectiveness by Facility Type > Figure 610-1 (2) Updating an Existing Traffic Impact Analysis A TIA may require updating when the amount or character of traffic is significantly different from an earlier analysis. Generally, a TIA requires updating every two years. A TIA might require updating sooner in rapidly developing areas and not as often in slowly developing areas. In these cases, consultation with WSDOT is strongly recommended. ## 610.07 Scope of Traffic Impact Analysis Consultation between the lead agency, WSDOT, and those preparing the TIA is recommended before commencing work on the analysis to establish the appropriate scope. At a minimum, the TIA includes the following elements: (1) Boundaries of the Traffic Impact Analysis Boundaries are all state highway facilities impacted in accordance with the criteria in 610.06 . Traffic impacts of local streets and roads can impact intersections on state highway facilities. In these cases, include an analysis of adjacent local facilities, (driveways, intersections, and interchanges), upstream and downstream of the intersection with the state highway in the TIA. A “lesser analysis” may include obtaining traffic counts, preparing signal warrants, or a focused TIA.
|
{
"page_id": null,
"source": 7320,
"title": "from dpo"
}
|
For developer projects, the boundaries (such as the city limits) may be determined by the local agency. (2) Traffic Analysis Scenarios WSDOT is interested in the effects of plan updates and amendments, as well as the effects of specific project entitlements (including, but not limited to, site plans, conditional use permits, subdivisions, and rezoning) that have the potential to impact a state highway facility. The complexity and/or magnitude of the impacts of a project normally dictate the scenarios necessary to analyze the project. Consultation between the lead agency, WSDOT, and those preparing the TIA is recommended to determine the appropriate scenarios for the analysis and why they should be addressed. (a) When only a plan amendment or update is being sought in a TIA, the following scenarios are required: 1. Existing Conditions – Current year traffic volumes and peak hour LOS analysis of affected state highway facilities. 2. Proposed Project Only With Select Zone Analysis – Trip generation, distribution, and assignment in the year the project is anticipated to complete construction. 3. Plan Build-Out Only – Trip assignment and peak hour LOS analysis. Include current land uses and other pending plan amendments/anticipated developments. 4. Plan Build-Out Plus Proposed Project – Trip assignment and peak hour LOS analysis. Include proposed project and other pending plan amendments. Design Manual M 22-01 Traffic Analysis > May 2006 Page 610-5 (b) When a plan amendment is not proposed and a proposed project is seeking specific entitlements (such as site plans, conditional-use permits, subdivisions, rezoning, and others), the following scenarios are required to be analyzed in the TIAs: 1. Existing Conditions – Current year traffic volumes and peak hour LOS analysis of affected state highway facilities. 2. Proposed Project Only – Trip generation, distribution, and assignment in the year the project is anticipated to complete
|
{
"page_id": null,
"source": 7320,
"title": "from dpo"
}
|
construction. 3. Cumulative Conditions (Existing Conditions Plus Other Approved and Pending Projects Without Proposed Project) – Trip assignment and peak hour LOS analysis in the year the project is anticipated to complete construction. 4. Cumulative Conditions Plus Proposed Project (Existing Conditions Plus Other Approved and Pending Projects Plus Proposed Project) – Trip assignment and peak hour LOS analysis in the year the project is anticipated to complete construction. 5. Cumulative Conditions Plus Proposed Phases (Interim Years) – Trip assignment and peak hour LOS analysis in the years the project construction phases are anticipated to be completed. (c) In cases where the circulation element of the plan is not consistent with the land use element or the plan is outdated and not representative of current or future forecasted conditions, all scenarios from 610.07(2)(a) and (b) are to be utilized, with the exception of the duplication of (b) 1 and (b) 2. ## 610.08 Traffic Data Prior to any fieldwork, consultation between the lead agency, WSDOT, and those preparing the TIA is recommended to reach consensus on the data and assumptions necessary for the study. The following elements are a starting point in that consideration: (1) Trip Generation For trip generation forecasts, use the latest edition of the Institute of Transportation Engineers’ (ITE) publication, “Trip Generation.” Local trip generation rates are also acceptable if appropriate validation is provided to support them. (a) Trip Generation Rates – When the land use has a limited number of studies to support the trip generation rates or when the Coefficient of Determination (R2) is below 0.75, consultation between the lead agency, WSDOT, and those preparing the TIA is recommended. (b) Pass-by Trips – Pass-by trips are only considered for retail-oriented development. Reductions greater than 15% require consultation and acceptance by WSDOT. Include the justification for exceeding
|
{
"page_id": null,
"source": 7320,
"title": "from dpo"
}
|
a 15% reduction in the TIA. (c) Captured Trips – Captured trip reductions greater than 5% require consultation and acceptance by WSDOT. Include the justification for exceeding a 5% reduction in the TIA. (d) Transportation Demand Management (TDM) – Consultation between the lead agency and WSDOT is essential before applying trip reduction for TDM strategies. Note: Reasonable reductions to trip generation rates are considered when adjacent state highway volumes are sufficient (at least 5,000 ADT) to support reductions for the land use. (2) Traffic Counts Prior to field traffic counts, consultation between the lead agency, WSDOT, and those preparing the TIA is recommended to determine the level of detail (location, signal timing, travel speeds, turning movements, and so forth) required at each traffic count site. All state highway facilities within the boundaries of the TIA are to be considered. Common rules for counting vehicular traffic include, but are not limited to, the following: (a) Conduct vehicle counts to include at least one contiguous 24-hour period on Tuesdays, Wednesdays, or Thursdays during weeks not containing a holiday and in favorable weather conditions. Traffic Analysis Design Manual M 22-01 > Page 610-6 May 2006 (b) Conduct vehicle counts during the appropriate peak hours (see peak hour discussion below). (c) Consider seasonal and weekend variations in traffic where appropriate (recreational routes, tourist seasons, harvest season, and others). (3) Peak Hours To eliminate unnecessary analysis, consultation between the lead agency, WSDOT, and those preparing the TIA is recommended during the early planning stages of a project. In general, the TIA includes a morning ( a .m .) and an evening (p .m .) peak hour analysis. Other peak hours (such as 11:30 a .m . to 1:30 p .m ., weekends, and holidays) might also be required to determine the significance of the traffic
|
{
"page_id": null,
"source": 7320,
"title": "from dpo"
}
|
impacts generated by a project. (4) Accidents The following should be included in any discussion of the subject of accidents: (a) A listing of the location’s 3-year accident history. (For direct access points and/or intersections, the list covers an area 0.1 mile to either side of the main line or crossroad intersection). (b) A collision diagram illustrating the 3-year accident history at each location where the number of accidents at the location has been 15 or more in the last 3 years. (c) The predominant accident types and their locations, any accident patterns, and an assessment of and mitigation for the development’s traffic safety impacts. Also, include in the discussion the following: 1. Sight distance and any other pertinent roadway geometrics 2. Driver expectancy and accident potential (if necessary) 3. Special signing and illumination needs (if necessary) ## 610.09 Traffic Impact Analysis Methodologies Typically, the traffic analysis methodologies for the facility types indicated below are used by WSDOT and will be accepted without prior consultation. When a state highway has saturated flows, the use of a microsimulation model is encouraged for the analysis (note, however, that the microsimulation model must be calibrated and validated for reliable results). Other analysis methods may be accepted; however, consultation between the lead agency, WSDOT, and those preparing the TIA is recommended to agree on the data necessary for the analysis. The methodologies include: A. Freeway Segments – Highway Capacity Manual ( HCM), operational analysis B. Weaving Areas – WSDOT Design Manual (DM), (HCM), operational analysis C. Ramps and Ramp Junctions – HCM, operational analysis or WSDOT DM, WSDOT Ramp Metering Guidelines (most recent edition) D. Multilane Highways – HCM, operational analysis E. Two-Lane Highways – HCM, operational analysis F. Signalized Intersections – HCM, Highway Capacity Software,** operational analysis, Synchro G. Unsignalized Intersections – HCM,
|
{
"page_id": null,
"source": 7320,
"title": "from dpo"
}
|
(MUTCD), and WSDOT Design Manual ,Chapter 850.05, for signal warrants if a signal is being considered H. Transit – HCM, operational analysis I. Pedestrians – HCM J. Bicycles – HCM K. WSDOT Criteria/Warrants – MUTCD (stop signs), WSDOT Traffic Manual (school crossings), WSDOT Design Manual , Chapter 840 (freeway lighting, conventional highway lighting) Design Manual M 22-01 Traffic Analysis > May 2006 Page 610-7 L. Channelization – WSDOT Design Manual M. Roundabouts – WSDOT Design Manual **Note: WSDOT does not officially advocate the use of any special software. However, consistency with the HCM is advocated in most (but not all) cases. The WSDOT local development review units utilize the software mentioned above. If different software or analytical techniques are used for the TIA, then consultation between the lead agency, WSDOT, and those preparing the TIA is recommended. Challenge results that are significantly different than those produced with the analytical techniques above. The procedures in the Highway Capacity Manual do not explicitly address operations of closely spaced signalized intersections. Under such conditions, several unique characteristics must be considered, including spill-back potential from the downstream intersection to the upstream intersection; effects of downstream queues on upstream saturation flow rates; and unusual platoon dispersion or compression between intersections. An example of such closely spaced operations is signalized ramp terminals at urban interchanges. Queue interactions between closely spaced intersections can seriously distort the procedures in the HCM. ## 610.10 Traffic Analysis Software For applications that fall outside the limits of the HCM software, WSDOT makes use of the following software: (1) TRANSYT-7F TRANSYT-7F is a traffic signal timing optimization software package for traffic networks, arterial streets, or single intersections having complex or simple conditions. TRANSYT-7F capabilities other than signal timing programs include: • Lane-by-lane analysis • Direct CORSIM optimization • Multicycle and multiperiod optimization
|
{
"page_id": null,
"source": 7320,
"title": "from dpo"
}
|
• Detailed simulation of existing conditions • Detailed analysis of traffic-actuated control • Hill-climb and genetic algorithm optimization • Optimization based on a wide variety of objective functions • Optimization of cycle length, phasing sequence, splits, and offsets • Explicit simulation of platoon dispersion, queue spillback, and spillover • Full flexibility in modeling unusual lane configurations and timing plans (2) Trafficw are – Syn chro Synchro is a software application for optimizing traffic signal timing and performing capacity analyses. The software optimizes splits, offsets, and cycle lengths for individual intersections, an arterial, or a complete network. Synchro performs capacity analyses using both the Intersection Capacity Utilization (ICU) and HCM methods. Synchro provides detailed time space diagrams that can show vehicle paths or bandwidths. Synchro can be used for creating data files for SimTraffic and other third party traffic software packages. SimTraffic models signalized and unsignalized intersections, and freeway sections with cars, trucks, pedestrians, and buses. Synchro capabilities other than signal timing programs include: • Lane-by-lane analysis • Direct CORSIM optimization • Multicycle and multiperiod optimization • Detailed simulation of existing conditions • Detailed analysis of traffic-actuated control • Hill-climb and genetic algorithm optimization • Optimization based on a wide variety of objective functions • Optimization of cycle length, phasing sequence, splits, and offsets • Explicit simulation of platoon dispersion, queue spillback, and spillover • Full flexibility in modeling unusual lane configurations and timing plans Traffic Analysis Design Manual M 22-01 > Page 610-8 May 2006 (3) aaSIDRA aaSIDRA is a software product that can analyze signalized and unsignalized intersections, including roundabouts in one package. It is a microanalytical traffic evaluation tool that employs lane-by-lane and vehicle drive cycle models. aaSIDRA can perform signal timing optimization for actuated and pretimed (fixed-time) signals, with signal phasing schemes from the simplest to the
|
{
"page_id": null,
"source": 7320,
"title": "from dpo"
}
|
most sophisticated. aaSIDRA, or aaTraffic SIDRA (Signalized & unsignalized Intersection Design and Research Aid) software is for use as an aid for designing and evaluating of the following intersection types: • Signalized intersections (fixed-time, pretimed, and actuated) • Roundabouts • Two-way stop sign control • All-way stop sign control • Yield sign control (4) PTV America – Vissim Vissim is a microscopic, behavior-based multi-purpose traffic simulation program, for signal systems, freeway systems, or combined signal and freeway systems having complex or simple conditions. The program offers a wide variety of urban and highway applications, integrating public and private transportation. Even complex traffic conditions are visualized at an unprecedented level of detail providing realistic traffic models. Vissim capabilities include: • Dynamic Vehicle Assignment • Land use traffic impact studies and access management studies • Freeway and surface street interchanges • Signal timing, coordination, and pre-emption • Freeway weaving sections, lane adds and lane drops • Bus stations, bus routes, carpools, and taxis • Ramp metering and HOV lanes • Unsignalized intersections and signal warrants • Incident detection and management • Queuing studies involving turn pockets and queue blockage • Toll plazas and truck weigh stations • Origin-destination traffic flow patterns • Verification and validation of other software • Surrogate for field data collection • Public presentation and demonstration (5) TSIS – Corsim TSIS is a traffic simulation software package for signal systems, freeway systems, or combined signal and freeway systems having complex or simple conditions. Its strength lies in its ability to simulate traffic conditions at a level of detail beyond other simulation programs. TSIS capabilities include: • Land use traffic impact studies and access management studies • Freeway and surface street interchanges • Signal timing, coordination, and pre-emption • Freeway weaving sections, lane adds, and lane drops • Bus stations,
|
{
"page_id": null,
"source": 7320,
"title": "from dpo"
}
|
bus routes, carpools, and taxis • Ramp metering and HOV lanes • Unsignalized intersections and signal warrants • Incident detection and management • Queuing studies involving turn pockets and queue blockage • Toll plazas and truck weigh stations • Origin-destination traffic flow patterns • Verification and validation of other software • Surrogate for field data collection • Public presentation and demonstration Use the most current version of Traffic Analysis Software. Current software licenses may be obtained from the Traffic Analysis Engineer at the HQ Traffic Office: (360) 705-7297. Design Manual M 22-01 Traffic Analysis > May 2006 Page 610-9 ## 610.11 Mitigation Measures Consultation between the lead agency, WSDOT, and those preparing the TIA is recommended to reach consensus on the mitigation measures and who will be responsible. Mitigation measures must be included in the TIA, to determine if a project’s impacts can be eliminated or reduced to a level of insignificance. Eliminating or reducing impacts to a level of insignificance is the standard pursuant to SEPA and NEPA. The lead agency is responsible for administering the SEPA review process and has the principal authority for approving a local development proposal or land use change. WSDOT, as a lead agency, is responsible for reviewing the TIA for impacts that pertain to state highway facilities. However, the authority vested in the lead agency under SEPA does not take precedence over other authorities in law. If the mitigation measures require work in the state highway right of way, an encroachment permit from WSDOT is required. This work is also subject to WSDOT standards and specifications. Consultation between the lead agency, WSDOT, and those preparing the TIA early in the planning process is strongly recommended to expedite the review of local development proposals and to reduce conflicts and misunderstandings in both the local
|
{
"page_id": null,
"source": 7320,
"title": "from dpo"
}
|
agency SEPA review process as well as the WSDOT encroachment permit process. Additional mitigation recommendations necessary to help relieve impacts include the following: (a) Satisfy local agency guidelines and interlocal agreements (b) Correct any LOS deficiencies as per interlocal guidelines (c) Donation of right of way/frontage improvements/channelization changes (d) Installation of a traffic signal (warrant analysis per MUTCD is required) (e) Include current/future state projects (Sunshine Report) (f) Clear zone if widening the state highway (g) Any proposed changes to state highway channelization require submittal of a complete channelization plan, per channelization plan checklist, for state review and approval (h) Possible restrictions of turning movements (i) Sight distance (j) Traffic mitigation payment (pro-rata share contribution) to a programmed WSDOT project (see Chapter 4 of the Development Services Manual) ## 610.12 Traffic Impact Analysis Report The minimum contents of a TIA report are listed below. The amount of text required under each element will vary depending upon the scale of the project. I. EXECUTIVE SUMMARY II. TABLE OF CONTENTS A. List of Figures (Maps) B. List of Tables III. INTRODUCTION A. Description of the proposed project B. Location of the project C. Site plan including all access to state highways (site plan, map) D. Circulation network including all access to state highways (vicinity map) E. Land use and zoning F. Phasing plan including proposed dates of project (phase) completion G. Project sponsor and contact person(s) H. References to other traffic impact studies Traffic Analysis Design Manual M 22-01 > Page 610-10 May 2006 IV. TRAFFIC ANALYSIS A. Clearly stated assumptions B. Existing and projected traffic volumes (including turning movements), facility geometry (including storage lengths), and traffic controls (including signal phasing and multisignal progression where appropriate), (figure/s) C. Project trip generation (including references) (tables) D. Project-generated trip distribution and assignment (figure/s) E.
|
{
"page_id": null,
"source": 7320,
"title": "from dpo"
}
|
LOS and warrant analyses—existing conditions, cumulative conditions, and full-build of plan conditions with and without project V. CONCLUSIONS AND RECOMMENDATIONS A. LOS and appropriate MOE quantities of impacted facilities with and without mitigation measures B. Mitigation phasing plan including dates of proposed mitigation measures C. Define responsibilities for implementing mitigation measures D. Cost estimates for mitigation measures and financing plan VI. APPENDICES A. Description of traffic data and how data was collected B. Description of methodologies and assumptions used in analyses C. Worksheets used in analyses (for example, signal warrant, LOS, traffic count information) Design Manual M 21-01 Sight Distance May 2006 Page 650-1 Chapter 650 Sight Distance 650.01 General 650.02 References 650.03 Definitions 650.04 Stopping Sight Distance 650.05 Passing Sight Distance 650.06 Decision Sight Distance 650.07 Documentation ## 650.01 General It is essential that the driver of a vehicle be able to see far enough ahead to assess developing situations and take appropriate action. For purposes of design, the required sight distance is considered in terms of passing sight distance, stopping sight distance, and decision sight distance. For additional information, see the following chapters: Chapter Subject 910 sight distance at intersections at grade 915 sight distance at roundabouts 920 sight distance at road approaches 930 sight distance at railroad crossings 1020 sight distance for paths and trails ## 650.02 References Design Guidance Guidance included by reference within the text includes: Manual on Uniform Traffic Control Devices for Streets and Highways , USDOT, FHWA; including the Washington State Modifications to the MUTCD, Chapter 468-95 WAC, (MUTCD) > htm Supporting Information Other resources used or referenced in this chapter includes: A Policy on Geometric Design of Highways and Streets , AASHTO, 2001 ## 650.03 Definitions decision sight distance The distance required for a driver to detect an unexpected or difficult-to-perceive
|
{
"page_id": null,
"source": 7320,
"title": "from dpo"
}
|
information source or hazard, interpret the information, recognize the hazard, select an appropriate maneuver, and complete it safely and efficiently. design speed The speed used to determine the various geometric design features of the roadway. passing sight distance The distance (on a two-lane highway) required for a vehicle to execute a normal passing maneuver based on design conditions and design speed. roadside That area between the outside shoulder edge and the right of way limits. The median area between the edges the shoulders on a divided highway is also considered roadside. roadway The portion of a highway, including shoulders, for vehicular use. rural design area An area that meets none of the conditions to be an urban design area. sight distance The length of highway visible to the driver. stopping sight distance The distance required to safely stop a vehicle traveling at design speed. suburban area A term for the area at the boundary of an urban area. Suburban settings may combine the higher speeds common in rural areas with activities that are more similar to urban settings. urban area An area designated by WSDOT in cooperation with the Transportation Improvement Board and regional transportation planning organizations, subject to the approval of the FHWA. urban design area An area where urban design criteria is appropriate, that is defined by one or more of the following: • An urban area. • An area within the limits of an incorporated city or town. Sight Distance Design Manual M 21-01 Page 650-2 May 2006 • An area characterized by intensive use of the land for the location of structures and receiving such urban services as sewer, water, and other public utilities and services normally associated with an incorporated city or town. This may include an urban growth area defined under the Growth Management
|
{
"page_id": null,
"source": 7320,
"title": "from dpo"
}
|
Act (Chapter 36.70A RCW Growth management—planning by selected counties and cities), but outside the city limits. • An area with not more than 25% undeveloped land. ## 650.04 Stopping Sight Distance (1) Design Criteria Stopping sight distance is the sum of two distances: the distance traveled during perception and reaction time and the distance required to stop the vehicle. The perception and reaction time used in design is 2.5 seconds. The stopping distance is calculated using a constant deceleration rate of 11.2 feet/second 2. Provide design stopping sight distance (see Figure 650-1) at all points on all highways and on all intersecting roadways, except when evaluating an existing roadway, as provided in 650.04(7) . Available stopping sight distance is calculated for a passenger car using an eye height (h 1) of 3.50 feet and an object height (h 2) of 0.50 foot. Although AASHTO allows a 2-foot object height, a 0.5-foot object height is used because objects with a height between 0.5 foot and 2 feet may be perceived as hazards that would likely result in an erratic maneuver. In urban design areas, with justification, the object height (h 2) may be increased to 2.00 feet. Figure 650-1 gives the design stopping sight distances for grades less than 3%, the minimum curve length for a 1% grade change to provide the sight distance (using h 2=0.50 feet) for a crest (K C) and sag (K S) vertical curve, and the minimum length of vertical curve for the design speed (VCL m). (See 650.04(2) for sight distances when the grade is 3% or greater.) > Design Speed (mph) Design Stopping Sight Distance (ft) > KcKsVCL m > (ft) > 25 155 18 25 75 30 200 30 36 90 35 250 47 49 105 40 305 70 63 120 45 360
|
{
"page_id": null,
"source": 7320,
"title": "from dpo"
}
|
98 78 135 50 425 136 96 150 55 495 184 115 165 60 570 244 136 180 65 645 313 157 195 70 730 401 180 210 75 820 506 206 225 80 910 623 231 240 Design Stopping Sight Distance > Figure 650-1 (2) Effects of Grade The grade of the highway has an effect on the vehicle’s stopping sight distance. The stopping distance is increased on downgrades and decreased on upgrades. Figure 650-2 gives the stopping sight distances for grades of 3% and steeper. When evaluating sight distance with a changing grade, use the grade for which the longest sight distance is needed. > Design Speed (mph) Stopping Sight Distance (ft) Downgrade Upgrade > -3% -6% -9% 3% 6% 9% > 25 158 165 173 147 143 140 30 205 215 227 190 184 179 35 258 271 288 237 229 222 40 315 333 354 289 278 269 45 378 401 428 345 331 320 50 447 474 508 405 389 375 55 520 553 594 470 450 433 60 599 638 687 539 515 495 65 683 729 786 612 585 561 70 772 826 892 690 658 631 75 867 928 1004 773 736 705 80 966 1037 1123 860 818 782 Design Stopping Sight Distance on Grades > Figure 650-2 Design Manual M 21-01 Sight Distance May 2006 Page 650-3 For stopping sight distances on grades between those listed, interpolate between the values given or use the equation in Figure 650-3. > »¼º«¬ªr¸¹·¨©§ > 100 2.32 > 30 47 .12 > GVVSa > t > Where: S= Stopping sight distance on grade (ft) V= Design speed (mph) > t= Perception/reaction time (2.5 sec) > a= Deceleration rate (11.2 ft/sec 2)G = Grade (%) Stopping Sight Distance on Grades > Figure 650-3 Where: S
|
{
"page_id": null,
"source": 7320,
"title": "from dpo"
}
|
= Stopping sight distance on grade (ft) V = Design speed (mph) t = Perception/reaction time (2.5 sec) a = Deceleration rate (11.2 ft/sec 2 )G = Grade (%) Stopping Sight Distance on Grades Figure 650-3 (3) Crest Vertical Curves Use Figure 650-1 1 or the equations in Figure 650-4 to find the minimum crest vertical curve length to provide stopping sight distance when given the algebraic difference in grades. When using the equations in Figure 650-4, use h1=3.50 feet and h2=0.50 foot. Figure 650-1 1 does not use the sight distance greater than the length of curve equation. When the sight distance is greater than the length of curve and the length of curve is critical, the S>L equation given in Figure 650-4 may be used to find the minimum curve length. When a new crest vertical curve is built or an existing one is rebuilt with grades less than 3%, provide Design Stopping Sight Distance from Figure 650-1. When grades are 3% or greater, see 650.04(2) for required sight distance. In urban design areas, with justification, an object height ( h2) of 2.00 feet may be used with the equations in Figure 650-4. When evaluating an existing roadway, see 650.04(7) . When S>L When S>L ASL > 221 200 2 hh A 100 2LS2 > 21 hh > When S 2212200 hh > AS L > A200L S > 221hh > Where: L= Length of vertical curve (ft) S= Sight distance (ft) A= Algebraic difference in grades (%) > h1= Eye height (3.50 ft) > h2= Object height— see text (ft) Sight Distance, Crest Vertical Curve > Figure 650-4 > When S>L ASL > 221 200 2 hh A 100 2LS2 > 21 hh > When S 2212200 hh > AS L > A200L
|
{
"page_id": null,
"source": 7320,
"title": "from dpo"
}
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.