Table of Contents

Appendix A: Example Next Steps

Example: Collecting Work Zone (WZ) Crash Report Data from Law Enforcement Agencies
Critical Step Responsible Party Key Decision(s) Associated with Step Decision-maker Required Preparation Estimated Timeframe to Complete Step
(time from when activity begins)
1. Identify objective of collecting this information. Work Zone Engineer, State DOT How will we use these data? Work Zone Engineer, State DOT Meet with group to discuss. 1 month
2. Choose a pilot work zone and law enforcement (LE) agency. Work Zone Engineer, District Resident Engineers Choose sites and LE agencies for deployment. Resident Engineers, Work Zone Engineer Contact LE agencies to request their cooperation. 3 months
3. Visit pilot LE agency weekly to collect WZ crash reports. District Resident Engineers, District WZ Engineers, Inspectors Who will visit the LE agency to collect the reports? District Resident Engineer, LE agency Call ahead weekly before collecting reports. 6 months
4. Analyze reports to determine if real-time changes are necessary. Traffic/Safety Engineer, Work Zone Engineer, Who will analyze data? Work ZoneEngineer, District Resident Engineers Get reports from the previous step to the analyst(s). 6-9 months
5. Evaluate the usefulness and benefits of collecting this data. Work Zone Engineer, Traffic Engineer, District Resident Engineers Determine benefits of having the data available. Has it been used to make WZs safer? Work Zone Engineer Understand data analysis reports. Log changes made based on crash data. 9-12 months
6. If successful, expand beyond the pilot work zone to additional projects and LE agencies. Work Zone Engineer, Resident Engineers Choose sites for additional deployment. Resident Engineers, Work Zone Engineer Contact LE agencies to ask for their cooperation. 12-18 months
7. Institutionalize crash report collection on appropriate projects. Work Zone Engineer, Resident Engineers Identify criteria for choosing when data is collected regularly from LE agencies. Work Zone Engineer, Resident Engineers Report on use to date. 18+ months
8. Identify desired data that are missing from crash reports and explore ways of addressing gaps. Work Zone Engineer, State Safety Engineer, Traffic Records Coordinating Committee When can the crash report form be amended? Keeper of the State crash report form (varies) Develop proposal to add/modify crash report form content. Varies based on crash report form renewal cycle.


Example: Implement Portable Traffic Monitoring Devices (PTMDs) for Speed and Queue Data Collection
Critical Step Responsible Party Key Decision(s) Associated with Step Decision-maker Required Preparation Estimated Timeframe to Complete Step
(time from when activity begins)
1. Further evaluate current deployments of PTMDs in your State and other States. Work Zone Engineer, State DOT Should we deploy this strategy on our work zones? Work Zone Engineer, State DOT Prepare literature review report on current applications. 3 months
2. Determine most applicable sites/ project types in our jurisdiction for deployment. Work Zone Engineer, District Resident Engineers Choose sites for deployment. Resident Engineers, Work Zone Engineer Review temporary traffic control (TTC) plans. 6 months
3. Secure funding source and purchase PTMDs. Work Zone Engineer, Management Determine funding source and authorize purchase. DOT Management Analyze purchase options (e.g., lease vs. buy) and other costs. 9 months
4. Deploy PTMDs and collect data. Resident Engineers, Construction Inspectors Identify responsible party for data collection. Resident Engineers Identify process for data collection and archival. 10-12 months
5. Examine effects of the treatment where implemented. Resident Engineers, Construction Inspectors, Work Zone Engineer Determine what effect this treatment has on the safety and mobility of the work zone. Work Zone Engineer, Resident Engineers Identify objectives and performance measures. 12-15 months
6. Analyze data and evaluate effectiveness. Work Zone Engineer, Traffic Engineer Determine performance measures and desired metrics. Work Zone Engineer Understand data output. 12-15 months
7. If evaluation supports additional deployment, identify applicable sites. Work Zone Engineer, Resident Engineers, Construction Inspectors Choose sites for additional deployment. Resident Engineers, Work Zone Engineer Review TTC plans and TMP. 12-24 months
8. Institutionalize PTMD use in appropriate work zones based on most important criteria. Work Zone Engineer, Resident Engineers Identify criteria for choosing deployments. Develop special provisions for use of PTMDs on projects. Work Zone Engineer, Resident Engineers Determine most appropriate type of document (e.g., standard plan/drawing, special provision, specification). 24+ months


Example: Implement Bluetooth Technology to Obtain Travel Times
Critical Step Responsible Party Key Decision(s) Associated with Step Decision-maker Required Preparation Estimated Timeframe to Complete Step
(time from when activity begins)
1. Further evaluate current deployments of Bluetooth technology in your State and other States. Work Zone Engineer, State DOT Should we deploy this strategy on our work zones? Work Zone Engineer, State DOT Prepare literature review report on current applications. 3 months
2. Determine most applicable sites/project types in our jurisdiction for deployment. Work Zone Engineer, District Resident Engineers Choose sites for deployment. Resident Engineers, Work Zone Engineer Review temporary traffic control (TTC) plans. 6 months
3. Secure funding source and purchase devices. Work Zone Engineer, Management Determine funding source and authorize purchase. DOT Management Analyze purchase options (e.g., lease vs. buy) and other costs. 9 months
4. Deploy Bluetooth reading devices and collect data. Resident Engineers, Construction Inspectors Identify responsible party for data collection. Resident Engineers Identify process for data collection and archival. 10-12 months
5. Examine effects of the treatment where implemented. Resident Engineers, Construction Inspectors, Work Zone Engineer Determine what effect this treatment has on the safety and mobility of the work zone. Work Zone Engineer, Resident Engineers Identify objectives and performance measures. 12-15 months
6. Analyze data, evaluate effectiveness, and identify benefits. Work Zone Engineer, Traffic Engineer Determine performance and benefits of having the data available. Work Zone Engineer Understand data output. 12-15 months
7. If evaluation supports additional deployment, identify applicable sites. Work Zone Engineer, Resident Engineers, Construction Inspectors Choose sites for additional deployment. Resident Engineers, Work Zone Engineer Review TTC) plans and TMP. 12-24 months
8. Institutionalize Bluetooth reading device use in appropriate work zones based on most important criteria. Work Zone Engineer, Resident Engineers Identify criteria for choosing deployments. Develop special provisions for use of Bluetooth data collection on projects. Work Zone Engineer, Resident Engineers Determine most appropriate type of document (e.g., standard plan/drawing, special provision, specification). 24+ months


Example: Periodic Crash Data Review
Critical Step Responsible Party Key Decision(s) Associated with Step Decision-maker Required Preparation Estimated Timeframe to Complete Step
(time from when activity begins)
1. Examine and identify the current work zone modeling capacity of the agency. Work Zone Engineer, Traffic Engineer Determine if the entire agency will be examined, or only those directly involved with work zones. Work Zone Engineer Identify objectives and performance measures. 3 months
2. Fill gaps identified in Step1 by purchasing modeling software and receiving training. Work Zone Engineer, Choose most applicable modeling software for the majority of agency needs. Work Zone Engineer, IT staff Determine options and examine costs and benefits. 6 months
3. Determine project goals for safety and mobility aspects of the work zone. Work Zone Engineer, State DOT What goals are feasible for type and location of project? Work Zone Engineer, State DOT Review DOT policies and goals. 8 months
4. Determine which simulation model best suits the needs of the project. Work Zone Engineer, District Design Engineers Match project type with relevant simulation tool. District Design Engineers Understand available simulation models and what level of information they provide. 10 months
5. Based on the simulation model's required inputs, collect relevant data. Work Zone Engineer, Traffic Engineer Identify responsible party for data collection and define data to be collected. Traffic Engineer Identify process for data collection and archival. 14 months
6. Iteratively model work zone characteristics until desired safety and mobility goals are met. Design Engineer, Traffic Engineer Determine the desired outcomes of the simulation. Work Zone Engineer, State DOT Understand the simulation output. 16 months
7. Select strategies, temporary traffic control (TTC) devices, and construction methods to incorporate in the design plans, TTC Plan, and TMP that adhere to goals for the work zone. Work Zone Engineer, Traffic Engineer, Design Engineer Identify potential strategies that meet project goals for safety and mobility. Work Zone Engineer, Traffic Engineer Research and discuss applicable mitigation strategies and TTC devices. 18 months


Example: Work Zone Safety and Mobility Monitoring using Crash Curves
Critical Step Responsible Party Key Decision(s) Associated with Step Decision-maker Required Preparation Estimated Timeframe to Complete Step
(time from when activity begins)
1. Determine work zone segment length, AADT, and crash rate under normal operation conditions. Work Zone Engineer, Traffic Engineer How many years of data should be used to determine AADT and crash rate? How should segment lengths be determined? Work Zone Engineer, Traffic Engineer Review data and determine logical segment breakpoints. 2 months
2. Apply to appropriate crash curve and determine the recommended frequency of crash data collection. Work Zone Engineer, Traffic Engineer Which crash curve is most applicable? Traffic Engineer Conduct analysis of crash rate under normal circumstances. 3 months
3. Collect crash data. Work Zone Engineer, Traffic Engineer How will data be collected? Work Zone Engineer, Traffic Engineer Determine data elements to be collected. 5 months
4. Analyze data to determine effectiveness as related to work zone safety and mobility goals. Traffic Engineer Identify responsible party for data collection and analysis. Traffic Engineer Identify process for data collection and archival and select appropriate evaluation means. 7 months


Example: Review of Historic Work Zone Traffic Crash Data
Critical Step Responsible Party Key Decision(s) Associated with Step Decision-maker Required Preparation Estimated Timeframe to Complete Step
(time from when activity begins)
1. Determine if work zone crash data is available. State DOT Data Manager Is work zone data housed at Statewide or Regional level? State DOT and District level Data Manager Seek understanding about the types of data available and the limitations of the data. 2 months
2. Assess the level of detail the crash data exhibits (i.e., crash reports vs. general summaries. Statewide vs. work zone specific). State DOT Data Manager Determine the combinations in which data could be segregated to drill down to the appropriate level of detail. State DOT Data Manager, Traffic Engineer, Work Zone Engineer Determine what level of data is relevant for analysis. 4 months
3. Organize data into like categories (i.e., urban/rural, AADT, etc.). Data can also be left organized at a Statewide level. State DOT Data Manager How should data be organized in order to make comparisons that are meaningful? Traffic Engineer, Work Zone Engineer Decide under which categories the data should reside. 6 months
4. Compare work zone crash data and crash data under normal circumstances to find similarities and disparities. State DOT Data Manager What threshold should serve as a basis for determining likeness? State DOT Data Manager, Traffic Engineer, Work Zone Engineer Compile database to easily cross reference and compare data across multiple categories. 10-12 months
5. Review comparison data to establish trends or potential improvement areas within identified categories. State DOT Data Manager Define what constitutes a trend and the threshold for when a work zone characteristic could be improved. Work Zone Engineer, Traffic Engineer Identify safety and mobility goals for work zones. Compare with trends and potential improvement areas. 16-18 months


Example: Analyze Crash Risks Associated with Nighttime and Daytime Work Zone Operations
Critical Step Responsible Party Key Decision(s) Associated with Step Decision-maker Required Preparation Estimated Timeframe to Complete Step
(time from when activity begins)
1. Define the types of data to collect with respect to daytime and nighttime work zone operations (e.g., project type, temporary traffic control devices used, presence of adjacent equipment or barrier, etc.). Define a segment length for each work zone. Work Zone Engineer, State DOT Determine work zone features that may play a role in increased crash frequency and severity. Work Zone Engineer Identify performance measures. 2 months
2. Collect data as determined in Step 1. Traffic Engineers, Resident Engineers, Construction Inspectors Who will collect this data? Define the methods used to collect data (i.e., construction journals, crash forms, etc.). Traffic Engineers, Resident Engineers Define data collection and documentation methods. 6 months
3. Retrieve comparative historic crash data for identified segment. Data Manager Determine the log points of the beginning and end of the work zone. Work Zone Engineer, Data Manager Submit detailed request to the Data Manager. 9 months
4. Analyze data and identify crash disparities with respect to type, frequency and severity. State DOT Data Manager, Traffic Engineer Ensure accurate data analysis and effective reporting mechanisms. Work Zone Engineer Previous steps. 12 months


Example: Periodic Crash Data Review
Critical Step Responsible Party Key Decision(s) Associated with Step Decision-maker Required Preparation Estimated Timeframe to Complete Step
(time from when activity begins)
1. Determine the value of the Periodic Crash Data Review; decide on frequency and scope for the review; gain acceptance of the process. Work Zone Engineer,Traffic Engineer What benefit will this review provide our State? Senior Management Develop presentation materials to share with managers. 3 months
2. Develop agenda and invitees. Work Zone Engineer Ensure key players can attend. Work Zone Engineer Begin thinking about performance measures to drive the agenda. 4 months
3. Schedule event (consider scheduling with biannual Work Zone Process Review). Work Zone Engineer, District Traffic Engineers, FHWA Ensure key players can attend. Work Zone Engineer Set up meeting space and logistics. Send pre-meeting read-ahead materials. 5 months
4. Compile crash data and other supporting information for review. Work Zone Engineer, Traffic Engineer What are the objectives and performance measures for discussion? Work Zone Engineer Determine which information is the most applicable for review. 6 months
5. Conduct Event: Identify performance measures. Work Zone Engineer What is the outcome we're looking for? Work Zone Engineer, Senior Management Use the initial performance measure discussed from the previous task. 7 months
6. Conduct Event: Review crash data. Data Manager Define work zone crashes. Identify when the work zone was a contributing factor. Data Manager Become knowledgeable on work zone crash definitions. 7 months
7. Conduct Event: Identify strategies to improve data collection and analysis. Work Zone Engineer, Data Manager Ensure strategies are feasible. Data Manager, Work Zone Engineer Determine relative cost of various strategies. 7 months
8. Post-event: Develop strategy-specific action plans to improve data collection and analysis. Work Zone Engineer, Data Manager Develop a step-by-step process. Work Zone Engineer Use these tables to develop a critical step process for each strategy. 10 months
9. Schedule follow-up to assess progress on completing the action plan. Work Zone Engineer Identify objectives and performance measures. Work Zone Engineer, Senior Management Populate strategy-specific action plan tables to track progress 18-24 months


Table of Contents | Appendix B