CSTEE- -00( ) (If Assigned; Delete Line If CSTEE Project Numbernot Assigned)

GDOT PI: #######, ####### County

CSTEE-####-00(###) (if assigned; delete line if CSTEE project numbernot assigned)

Design Variance/Exception

(Replace all items in italics or symbols with appropriate information in non-italic font)

(Email a PDF and Microsoft Word file of the completed request to )

Revised January 25, 2018

PLACE ON CONSULTANT LETTERHEAD

GDOT PI: #######, ####### County

CSTEE-####-00(###) (if assigned;delete line if CSTEE project numbernot assigned)

GDOT project description (match GDOT’s program project name)

DATE: Current date of request submittal

FROM:Consultant/Engineer of Record

Consultant firm name

TO:Brent Story, P.E.

State Design Policy Engineer

SUBJECT / Request for Design Variance/Exceptionfor (list criteria here; ex: Lateral Offset, ADA Requirement in PROWAG, etc.)

Approval of a Design Variance/Exception is requested for this project.

(Note: The request can include more than one existing or proposed feature but provide separate rural and urban design criteria references and tables as required. Separate signature blocks for each existing and proposed features are required.)

PROJECT DESCRIPTION

Provide a general description of the project including the length of the project, the general location of the project including any city and county limits or proximity thereto, city and street location, speed design, posted speed limit,scope of work, and existing/proposed typical sections, amount of TE funds awarded, and other improvements to be constructed. Recommend using approved concept report location and description.

FEATURE(S) REQUIRING A DESIGN VARIANC/EXCEPTION

Describe the feature(s) requiring a design variance or a design exception. Give the values of the current standard criteria and the values that are proposed to be used. For example, “based on the GDOT Design Policy Manual, Chapter 5, Section xx, Table xx, ## mph speed limit, page ## or AASHTO Roadside Design Guide, 4th Edition, 2011, Chapter 10, the minimum lateral offset is ##. The item is/are located less than the required minimum lateral offset from face of curb to the face of pole/center of tree.”

Include the value of the beginning and the ending stationing for the design feature. Add a statement describing what kind of utilities are on the pole: Cable, T.V., Phone, etc. Include the value of the beginning and the ending mile point stationing for the design feature that has a linear length.

The existingfeatures to remain in place and/or the proposed features are located at the following stations: (list all features requiring a design variance/exception in separate tablesfor each existing feature and each proposed feature.)

Include a chart such as:

Item Number / Station / Side / Distance from Face of Curb to Face of Pole
or Center of Tree / Required
Offset
1 / ##+## / X / ## / ##
2 / ##+## / X / ## / ##

Chart to include Required Offset column. Distance may change within the table if different features included in the table.

CURRENT AND FUTURE TRAFFIC DATA

Describe current and future traffic volumes with any other pertinent traffic data, i.e., truck percentage, transit route, etc. For example: Current Average Daily Traffic (ADT) is XXX. Future traffic volume is expected to increase by X%. Future traffic volume analysis is beyond the scope of this project.

CRASH DATA

Describe the crash history within the project limits for the most recent three years available. In particular, address and summarize the crash history related to the feature requiring a design variance request.This should include the types of crashes (i.e. head-on, angle, side swipe, rear end, run-off-road, cross median, cross centerline, etc.) and crash severity (i.e. number of fatalities & injuries). Access the GEARS - Georgia Electronic Accident Reporting System site or the GDOT Crash, Road & Traffic Data site for this information. Include Statewide the Statewide Mileage, Travel & Accident Data for the same years as those provided in the crash history for comparison (Contact Office of Traffic Safety and Design Personnel for this information).

Include a chart such as:

Year / Angle / Rear End / Side Swipe / Run-off Road / Total
201# / # / # / # / # / #
201# / # / # / # / # / #
201# / # / # / # / # / #
Total / # / # / # / # / #

ALTERNATIVES CONSIDERED/RISK ASSESSMENT

Summarize and compare the alternatives considered, including the alternative that meets the full criteria and evaluate the risk associated with the design variance/exception. Use the Highway Safety Manual (HSM) and HSM Spreadsheets to predict the impact of proposed alternatives on safety, if applicable. For existing substandard conditions to be retained and where adequate crash data is provided for years where that condition existed, no HSM analysis is required. Explain why the HSM cannot be applied if it is determined that no analysis is available.

In cases where the HSM is not applicable, the Office of Design Policy and Support may request additional information on similar facilities.

Example of text used in previous DVs for existing features

The only alternatives considered were to move the poles outside the minimum lateral distances and to remove the tree. Because existing substandard conditions are to be retained and because adequate crash data is being provided (for years where that condition existed), no Highway Safety Manual analysis to predict the impact of proposed alternatives on safety is required.

COST TO MEET STANDARD CRITERIA

Summarize the cost estimate for construction and right-of-way and other associated costsfor constructing or reconstructing the design feature to meet current standards.

WHY THE CURRENT STANDARD CRITERIA CANNOT BE MET

Summarize why the current AASHTO Standard Criteria)/GDOT Standard Criteria(Design Variance/Exception) cannot be met.For example, low traffic volume, cost of relocation or ROW acquisition is beyond the scope of this work, community plan for aesthetic appearance of downtown area with trees or lighting, or citizens enjoy old trees and shade provide by the trees, etc.

MITIGATION PROPOSED

Describe any mitigation proposed to lessen the impact of not meeting current standard criteria. The FHWA publication Mitigation Strategies for DesignExceptions is a good reference. It is available at should be reviewed and, as a minimum, the strategies presented in the report are to be considered and discussed in the Design Variance/Exception request.If mitigation or other additional enhancement costs aresignificant, summarize these costs at this point.

Other resources providing mitigation ideas or traffic safety-related accident countermeasure or accident pattern countermeasure ideas include the American Association of State Highway and Transportation Officials (AASHTO) May 2004 “A Guide for Achieving Flexibility in Highway Design” and the Institute of Transportation Engineers (ITE) “Traffic Engineering Handbook”.

RECOMMENDATION

The Engineer/Designer of Record must make a recommendation to the approving authority for action. Any conditions to the approval of this exception should be clearly stated. Include name and contact number. For example add “Based on the information presented herein, I, as the Engineerof Record recommend approval of the design variance/exception for the referenced project. Should you have any questions please feel free to contact me at (contact information - email address and telephone number).”

The signature block for approval will take one or the other of the following forms. Typically TE projects are NOT classified as Full Oversight or Project of Division Interest (PoDI).

Separate signature blocks for each Design Variance/Exception for existing and proposed features are required.

For projects NOT classified as Full Oversight (FOS) or Project of Division Interest (PoDI):

Recommend: / (must be registered Georgia PE)
Engineerof Record / Date
Concur:
GDOT Director of Engineering / Date
Approve:
GDOT Chief Engineer / Date

For projects classified as Full Oversight (FOS) or Project of Division Interest (PoDI):

Recommend: / (must be registered Georgia PE)
Engineerof Record / Date
Concur:
GDOT Director of Engineering / Date
Approve:
GDOT Chief Engineer / Date
Approve:
FHWA Division Administrator / Date

Attachments:

Project Location Map (Clearly indicate project location. Include PI#, county, programmed name on the page.)
Typical Sections (Clearly indicate each item which requires design variance/exception approval. Range of widths or offsets is acceptable. Include PI#, county, programmed name on the page.)
Project Layouts/plan/profile sheets (Indicate each item in plan view with item number, offset, and side, which requires design variance approval corresponding to stations. Include PI#, county, and programmed name on page.)
Photo image of item location(Include item description as appropriate,PI#, county, and programmed name on page.)
Any other documentation pertinent to request.(Include PI#, county, and programmed name on page.)