Traffic Engineering Process and Report
 

This page defines the requirements and expectations for all parties throughout the Traffic Engineering Study Process. The outline below contains links to examples, forms and guides to illustrate specific parts of the study process. 
 

 

 

 

01. Scope and Man-hour Negotiations (if applicable)

A. Scope (DOTD)

1. Pre-scope Documentation

2. Scope checklist

3. Schedule​

B. Man-hour Spreadsheet​ with Project Schedule (Consultant)

C. Signed Contract (Consultant and DOTD)

D. Notice to Proceed Letter (DOTD)
​ 

02. Kick-Off Meeting (if applicable)

A. Agenda - submitted to DOTD one week prior to meeting

B. Possible Attendees: 

District Traffic Operations Engineer, Traffic Engineering Management, Consultant, Project Manager, District personnel, Safety section, Environmental section, Road Design section, Bridge Design section, LPA Responsible Charge, local stakeholders and other ​​a​pplicable personnel

C. Required Documents

1. Agenda

2. Sign In Sheet

3. Scope

4. Project Schedule

5. Scope checklist and all pre-scope documents

 

Deliverable:

Agenda - submitted to DOTD one week prior to meeting

Kickoff Meeting Minutes - submitted to Task Manager within 3 days

 

03. Initial Data Collection

​A. 7 day/24 hour Counts 

NOTE:  With prior approval, 48 hour counts with classifications may be used 

B. Peak Period Determination​ with chart and explanation

C​Initial Data Collection QA/QC Checklist

 

Deliverable: (Approval needed to begin Final Collection)

Appendix A – Initial Data Collection​

 

04. Final Data Collection ​ ​

A. Peak Period Counts  ​

B. Peak Period Observation

C. Growth Rate Determination​

D. Trip Generation (if applicable)

E. Speed Study Data (if applicable)

F. Geometric Field Review​

G. Travel Time Runs (if applicable)

H. Warrant Analysis (if applicable)

I.  Final Data Collection QA/QC Checklist​

  

Deliverable: (Approval needed to begin Existing and No Build Analysis)

Appendix B - Final Data Collection

Chapter 1 of Final Report​​

 

05. Existing Safety Analysis

​NOTE:  Submitted at the same time as Existing and No Build Analysis

A. CATScan Tool​

B. Collision Diagram

C. Crash Report Documentation​

D. Crash Analysis Summary

E. Existing Safety Analysis QA/QC Checklist​

 

Deliverable: (Approval needed to begin Alternative Analysis)

Appendix C - Existing Safety Analysis​

 

06. Existing and No Build A​nalysis​​​

NOTE:  Before Existing Analysis begins, software shall be approved.  Before No Build Analysis begins, a design year volume map shall be submitted and approved.  

 

 

     

OR

Vissim Option

 

 

 

 

Deliverable: (Approval needed to begin Alternative Analysis)

Appendix D - Existing and No Build Analysis​ (include​ electronic files of analyses)

​​Tier 1 Analysis (presented at Existing and No Build Results Meeting)

​Chapter 2

 

07. Existing and No Build Results Meeting

​​​​NOTE:  Results of the ENB Analysis determine if Tier 2 Analysis is needed, so feasibility studies and some findings may not move forward.  Results may be shared via a phone call if a meeting is unnecessary. ​

​A. Possible Attendees: 

District Traffic Operations Engineer, Traffic Engineering Management, Consultant, Project Manager, District personnel, Safety section, Environmental section, Road Design section, Bridge Design section, LPA Responsible Charge, local stakeholders and other ​​a​​pplicable personnel

B. Content: 

    1. Present and discuss Chapter 2: Existing and No Build, including any safety or capacity issues for the study area
    2. Present and discuss high-level alternatives that address issues found in Chapter 2 (Tier 1 results) 
    3. Discuss tool selection for Alternative Analysis


Deliverable: (Approval needed to begin Preliminary Tier 2 Alternative Analysis)

Meeting Minutes submitted to Task Manager within 3 days


 

08. Preliminary Tier 2 Analysis (if applicable)

A. High level analysis

B. Sketch layouts of the potential alternatives

C. Redistributed volumes

D. Meeting (Optional)

    1. Possible Attendees: 
​​​​District Traffic Operations Engineer, Traffic Engineering Management, Consultant, Project Manager, District personnel, Safety section, Environmental section, Road Design section, Bridge Design section, LPA Responsible Charge, local stakeholders and other ​​a​​pplicable personnel
​2. Content:

a. Present and discuss single line sketch layouts of the potential alternatives with redistributed volumes and high-level analysis

b. Recommend weight factors and ratings scale for the Alternative Comparative Evaluation Matrix

c. Discuss presentation of results

 

Deliverable: (Approval needed to begin Final Alternative Analysis)

Meeting Minutes submitted to Task Manager within 3 days

High Level Sketches and Analysis

Redistributed Volumes Map

Recommended Alternative Comparative Evaluation Matrix

 

09. Final Alternative A​nalysis​​

A. Tier 2 Analysis 

​1. If progressing to Tier 3, coordinate Tier 3 Analysis Meeting

2. When coordinating with Environmental, may use that matrix if it meets requirements

B. Tier 3 Analysis (if applicable)

C. Access Justification Report (AJR) (if applicable)

1. Requires the AJR Consultant Checklist

2. Must adhere to FHWA Policy on Changes in Access to the Interstate System and address FHWA Policy Points

D. Alternative Analysis QA/QC Checklist​​​

 

Deliverable: (Approval needed to begin Final Report)

Appendix E: Alternative Analysis

Introduction of Final Report​

Chapter 3 of Final Report

Executive Summary

 

10. Final Alternatives A​nalysis​​ Meeting

A. Possible Attendees: 

District Traffic Operations Engineer, Traffic Engineering Management, Consultant, Project Manager, District personnel, Safety section, Environmental section, Road Design section, Bridge Design section, LPA Responsible Charge, local stakeholders and other ​​a​​pplicable personnel

B. Content: Present and discuss Chapter 3 Final Alternatives

 

 Deliverable: (Approval needed to begin Final Report)

Meeting Minutes submitted to Task Manager within 3 days

 

11. Final Report

Deliverable:

1. Sealed Report (Draft must be approved before final submission)

2. Minimum 2 Hard Copies

3. Minimum 2 electronic copies

​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​

​​​​​​