1. Rule on Work Zone Safety and Mobility SHA’s Road to Compliance Maryland State Highway Administration Office of Traffic and Safety Talking OperationsJawad Paracha March 19, 2007jparacha@sha.state.md.us

2. 2 In the Beginning… Summer 2005 Wanted to review the way we do business, not just compliance with the RuleWanted to review the way we do business, not just compliance with the Rule Got a consultant on board to help with reviewGot a consultant on board to help with review Developed Work Zone Business PlanDeveloped Work Zone Business Plan –12 key focus areas –Goals -> Strategies -> Action items –Timetable for completion of milestones

3. 3

4. 4 Focus on the Rule… Fall 2005 Identified need for communication and coordination within and outside of SHAIdentified need for communication and coordination within and outside of SHA Developed Temporary Traffic Control Safety and Mobility CouncilDeveloped Temporary Traffic Control Safety and Mobility Council Met as needed to discuss major milestones (significant project, TMP process, etc.)Met as needed to discuss major milestones (significant project, TMP process, etc.) -Office of Highway Development - Maryland Highway Contractors Association - Office of Bridge Development - Districts (Traffic, Construction) - Office of Planning - Maryland State Police - Office of Traffic and Safety - Consultants - Office of Communications - University of Maryland - Office of Maintenance - FHWA, Vendors and more!

5. 5 Focus on the Rule… Winter 2006 – Fall 2006 Worked with a consultant to: 1)Identify Rule requirements (“shalls” vs. “shoulds”) 2)Review existing SHA policies/processes –Do they satisfy Rule requirements? 3)Research –What are other States doing that is working (or not working)? –How does SHA currently incorporate work zone considerations in the project development process? –FHWA Guidance 4)Propose and implement new strategies to meet Rule requirements –Policies, processes, guidance documents, etc.

6. 6 Focus on new processes… Winter 2006 – Fall 2006 Worked together with planning, highway, bridge, communications, and construction offices to: –Identify current processes for identifying and addressing work zone impacts –Identify the level of impact assessment that is completed at each stage project development –Discuss areas for improvement and how we can get consideration of work zone impacts moved earlier in the process –Incorporate new processes into existing project development process

7. 7 Focus on new processes… Winter 2006 – Fall 2006 What did we find? –Work zone impacts assessment is already a part of the process for what would be “significant projects”, just not a formal, documented process –Traffic analysis for work zones has been done on several projects, but not regularly –Overall consensus that work zone impacts should be looked at earlier in the process On a conceptual level in project planningOn a conceptual level in project planning On a detailed level during preliminary design (revised as needed as the design progresses to PS&E)On a detailed level during preliminary design (revised as needed as the design progresses to PS&E)

8. 8 Where did we run into resistance? Identifying responsible persons/ offices to take on additional work load associated with new processes –Everyone thinks looking at work zone impacts and developing TMPs are great ideas….BUT resources (man power and funding) to get them done are limited –Consensus that consultants will take on most of additional work load; however, there is still effort required on the part of SHA to provide input, review, approve, etc. Districts wanted Design offices to be responsibleDistricts wanted Design offices to be responsible Design offices wanted the Districts to be responsibleDesign offices wanted the Districts to be responsible Solution: Shared responsibilitySolution: Shared responsibility Transportation Management Plan Design Office (lead coordination) TMP Team (support) Transportation Operations (TO) Strategies District Traffic (lead & approval) Traffic Control Plan (TCP) Design Office (lead) District Traffic (approval) Public Information & Outreach (PI&O) Office of Communications (lead & approval)

9. 9 Lessons Learned Get buy-in from senior managementGet buy-in from senior management –Decision making and support on policy changes, responsibility distribution, etc. Get input from those who will be doing the workGet input from those who will be doing the work –If they are a part of the process, they will be more willing to accept the changes –Getting input helps to identify what is “reasonable” change For example, our proposed alternatives analysis process was modified to include two levels – a concept level during planning and a detailed level during design – based on input from an info session held with staff in the Office of PlanningFor example, our proposed alternatives analysis process was modified to include two levels – a concept level during planning and a detailed level during design – based on input from an info session held with staff in the Office of Planning

10. 10 Compliance! Notification of compliance received January 2007Notification of compliance received January 2007 Met with FHWA Maryland Division in November 2006 to request compliance and formally submit all documentationMet with FHWA Maryland Division in November 2006 to request compliance and formally submit all documentation

11. 11 Where are we headed? Implementation processImplementation process –Include TMPs with all significant projects that are advertised after October 2007 to the extent feasible –Provide training to design and District offices on new policies and processes –Develop “blanket exceptions” for projects that are classified as significant by FHWA’s more than 3 day lane closure requirement, but are not considered significant by SHA

12. 12 SHA’s TMP Process Planning, Preliminary Investigation and DesignPlanning, Preliminary Investigation and Design Step 1 – Create TMP Team Step 2 – Compile Project Material Step 3 – Maintenance of Traffic Red Flag Summary Step 4 – Identify Significant Projects Step 5 – Maintenance of Traffic Alternative Analysis (MOTAA) Step 6 – Determine TMP Needs Step 7 – Identify Stakeholders and Revise TMP Team Step 8 – Preliminary Design (Draft TMP) Step 9 – Detailed Design (Semi-final, final TMP)

13. 13 SHA’s TMP Process ConstructionConstruction Step 10 – Implement TMP Step 11 – Monitor TMP Step 12 – Update/Revise TMP Performance AssessmentPerformance Assessment Step 13 - Evaluation

14. 14 Defining Significant Projects 6+ months of discussion on Significant Projects6+ months of discussion on Significant Projects –Developed smaller working group with representatives from Districts, design and planning offices –Presented for comment several times with TTC Safety and Mobility Council Quantitative definition did not seem to fitQuantitative definition did not seem to fit –Smaller $ projects may still have significant work zone impacts or require additional coordination Qualitative approach seemed to work bestQualitative approach seemed to work best –Allows for engineering judgment to play a role

15. 15 Defining Significant Projects Developed 2 flow chartsDeveloped 2 flow charts –OPPE, OHD, OBD (Planning and Design Offices) –District and minor projects Major criteria includeMajor criteria include –Project location –Anticipated mobility and safety impacts –Project and/or work zone characteristics If the project is identified as a Significant Project, perform Maintenance of Traffic Alternatives Analysis (MOTAA) to try identify a solution to reduce impacts below thresholdsIf the project is identified as a Significant Project, perform Maintenance of Traffic Alternatives Analysis (MOTAA) to try identify a solution to reduce impacts below thresholds IF MOTAA does not identify a solution that reduces impacts, develop Transportation Management PlanIF MOTAA does not identify a solution that reduces impacts, develop Transportation Management Plan

16. 16 Is the project located on or over   The National Highway System?   An Urban Freeway/Expressway?   An Urban or Rural OPA? Not a significant project, but may still require transportation operations and/or public information strategies. NO Will the project have any of the following characteristics? Mobility   Increase in delay or travel time (ie, traffic volumes that will exceed roadway capacity in the work zone) Safety   Roadway section or intersection on the Candidate Safety Improvement Locations (CSIL) list   Special worker safety considerations (for example, worker exposure greater than 100 hours on high speed roadways; refer to Temporary Traffic Barrier Policy) Other Characteristics   High level of public interest   Road work strategies:   Full roadway closure   Two-way, one-lane operations   Reversible lane operations   Night work   Multiple stages/phases of construction   Significant impact on public/private access (e.g., businesses, communities, park & ride lots, schools, fire stations, etc.)   Project timing (e.g. special events, beach traffic, etc.) that will result in an increase in traffic volumes   Requirements in the Guidelines/Checklist for Bicycle and Pedestrian Access through Work Zones cannot be satisfied   Significant restrictions on emergency vehicle access Is the project an OPPE, OHD or OBD Project? Perform Maintenance of Traffic Alternatives Analysis (MOTAA) Significant Project - Prepare TMP Does the selected alternative still have significant work zone safety and mobility impacts? YESYES YESYES YESYES YESYES NO NONO Refer to District/Minor Projects Flow Chart Not a significant project, but may still require transportation operations and/or public information strategies. Planning and Design Offices Flow Chart 16

17. 17 District and Minor Projects Flow Chart 17 Will the work involve continuous or intermittent lane closures on a freeway/expressway for more than three days? Not a significant project. Proceed with project work. YES Is the project a District project or minor project? Will the project comply with the Work Zone Lane Closure Analysis Guidelines? Significant Project – Prepare Transportation Management Plan Does the project fall under the “Blanket Exceptions” category? Perform Maintenance of Traffic Alternatives Analysis (MOTAA) Will the selected alternative comply with the Work Zone Lane Closure Analysis Guidelines? NO YES NO YES NO YES Not a significant project. Submit exception request. YES Not a significant project. Submit exception request. Not a significant project. Proceed with project work.

18. 18 QUESTIONS? Contact: Jawad Paracha Email: jparacha@sha.state.md.us Phone: 410-787-5891 jparacha@sha.state.md.us