I would like to introduce your host, Jocelyn Bauer. Good Day and welcome to the talking operations WorkZone implementation. I will be giving a brief introduction to the Web conferencing environment before turning the session over to Tracy Scriba, who we are very pleased to have as our moderator. Today's seminar is being recorded. It will last approximately one hours 45 minutes, the hour will be four questions. Indicate who your question is intended for. Make sure that you are typing into the small box and not the white area. Presenters will be unable to answer your questions during the presentation, but Tracy will use some of the questions for the question and answer sessions in the last part of the seminar. This session is being recorded. The National Transportation coalition website will have this posted in the next week. I will tie that into the chat box shortly. We would like you to direct others in your office to the recording. It will be available in the next week. Attendees will be notified a liability of the power point. At this time, I would like to introduce, Tracy, the moderator of this web cast. She is part of the FHWA team. She is leading the efforts for out reach and the recently published WorkZone rule. She is responsible for other federal highway WorkZone areas, best practices, performance measures and ITS work sounds. She has a degree from the University of Virginia. Now, I will turn this over to Tracy who will give a brief overview. Good morning or good afternoon, depending on where you are located. We certainly have a lot of interest in this Web cast. That is good to see. I know that the WorkZone is on a lot of people's minds as we approached the October 12th deadline for this year's role. We have three great speakers today, actually have three states and two speakers from Washington state that will be speaking to us today. You will hear a lot of great ideas from them as to what they have done so far to implement the rule. This is Maryland, Virginia and Washington state. They have all been in front of a lot of states as far as moving forward in this area of role implementation. We can get some good ideas and from these folks today as they share of what they have done in their states as far as their process for implementing the rule. Each will share with a particular area that they have worked on. I will introduce each speaker individually as we get to them. To start, I will give an overview, a little bit of a background to set the stage for what we will talk about for the rest of the webcast. It has more than two years since the rule has been implemented in the fall of 2004. We are about two-thirds of the way through the compliance. For implementing the rule. The rule itself establishes requirements and establishes requirements for addressing or understanding WorkZone safety impacts and developing strategies to manage those. It does apply to all federal a highway projects. That is primarily state DOT projects but also involves local projects that do receive federal a funding. To kind of a captured with the key concepts are, I try to boil it down into a field bullet point here. In a nutshell, we can be more effective in reducing the WorkZone mobility and safety impacts that we face on projects, if we better understand those projects, anticipate them and planned for them. We do not need to react in the moment to a particular situation. It might happen on a particular project, or if we can anticipate the safety concerns as we go through the planning and project development process. That kind of get at the second bullet is doing its early in the process. We have more options available at that point in time and can better take advantage of those as we look at the alternatives and come up with the alternatives for our project. What are the WorkZone impacts with those at and how can we address them? Another key principle is to consider solutions that go beyond the immediate location of the WorkZone. With this role, there is an update to the former rule. It focus primarily on the traffic control, at which is a key component to providing a safe WorkZone. What we are also finding that the issues in WorkZone are more complicated with ingestion, maintenance and rehabilitation work on existing roads. That involves more complex situations. If we can think of alternate routes and use them to the best degree possible just beyond immediate WorkZone area, we can have more options available to us to better manage our WorkZones. The last idea behind the rule is to integrate the thinking in the agency and DOT culture. Some of the components of the rule, the policy in particular. That brings me to what are the three key provisions in the rule? The course is, the policy area that I just mentioned that is a requirement for agencies to develop and implement a policy for WorkZone impact. That is a policy that drives the agency's approach to addressing WorkZone safety and mobility impact. Some policies and procedures that are more across the agency, they would affect all of the practices or larger practices in the agency. The project level, some procedures that would specifically get into the project area and address how to manage impact on individual projects. Let me get back to the right side here. Kind of breaking that down a little further, in the agency procedures area, the second box, there are four main areas that are addressed, one is to conduct-that is a recommendation in the rule but not a specific requirement. And then a requirement to have appropriate training for those involved in making decisions that affect WorkZones through preliminary engineering, design process, the construction process, the traffic engineering folks, law-enforcement, all of those that do have an impact on the implementation of WorkZones and how well they operate. The use of safety and operational data. Again, the trading in the safety and operational area were in the former rule, but it was not recovering operational data. We expanded that and used data that agencies have to better manage our WorkZones and the area of reviews of. Is used to be every one year. And the last box, there are two main areas to that. One is to identify significant projects. The projects that we think are likely to cause a relatively high level of destruction and need more attention. Develop plans to address the impact for the station WorkZone. The are required for all federal aide projects. The difference between that and the former traffic control plans is that they are a more comprehensive approach to WorkZone management. At a still contain a traffic control plan for all projects. For some projects there are none to other components that need to be there. That is the public information component and an operational strategies component. Operational strategies could be things like alternating the signal timing on alternate routes, using ITS to help manage the work song, using traffic incident management plans, those things are operational status trees. The operational strategies component is required for significant projects and are optional, but encouraged for other types of projects, or consideration of them is encouraged. That is the rule and a nutshell. That is covering a lot in just a few minutes here. Just to move to where we are at now, the efforts were first focused on our end at building some awareness of the rule and helping agencies that would be affected by the world to know what the rule is about. What I just did, but a little more detailed. We develop an implementation Guide and sponsored a series of regional workshops around the country. We had all states but one participate in those. We had six of them in locations that we try to make a little more feasible to have participants attend. They had an opportunity for a lot of discussion around a lot of DOTs. We are now in the mode of ongoing support for implementing the rule. I think the Web cast today is providing who have gone before and broken the ground and sharing what they have done. Just to show you briefly the implementation resources, there are four guides that are out now. These are an overall guide that implementing the role. That explains the provisions a bit and get some ideas for how an agency might implement them. There are three more technical guides that support specific aspects of the rule. There are public not out rate aspects. One is on conducting works on impact assessment. The-all of them are available electronically by our web site. We are awaiting the hard copies to come in from the printer on the impact Assessment guide. They should be here shortly. We also developed some frequently asked questions based on some topics that seemed to come up frequently. We are in the process of making some updates to those where you can access those. Some additional things that we are working on is a resource CD. You can see what it will look like. It will pull the resources into one place on the CD. That is the idea. It is not so much a lot of new material but pulling into one place where there is a handy way to access it. We are also working on a checklist that is almost completed and will be on the CD and web site. As far as training, there is an NHI course that is under development. Unfortunately, it is not done yet. We are wanting to have a pilot of that in late me, that is the hope for that. We hope it will be out this summer and available for other agencies to schedule it. This is just some of the type of ongoing implementation support that we have going. One aspect that I will point out to you is sharing examples. Today's webcast is not one way of doing that. We have been putting examples on our web site as we have been able to develop them. There are some examples of doing impact assessment, public information out reach examples, things like that that will hopefully give you more of a concrete idea of what some of these aspects might look like. All of this information is available on our web site. You can see the web site address there. If I cannot copy it down, it will be available on the slides later. We did a survey through our division offices in December and January on asking about progress and what challenges might be there. I will share with you the results of that. On the area of policy, you can see there that the top one is the states that were doing something prior to the rule. The purple color is the states that have completed it since then. They have completed their policy and got it approved as needed within their agency. Most it are in progress right now. There are only a few that have not started according to the survey. There were 38 respondents. We have about three quarters or so of folks responding. Eight in the impact assessment data use area, combining it together, we have a lot less completed in this area and a lot more not started yet. These are areas that will be evolving even after October as a disease get a better sense of what data they might be looking to use. In the process reviews area, we had some that were doing in prior rule. We have about five Total-the training area, about five total have in place what they need. There is still ongoing work at. Like the data area, that will continue to evolve for a period of time. There are certain steps and efforts that need to be made by October to be considered in the process as far as what the rule of compliance. There is an evolution that will happen with that over time. Process reviews, a number of agencies have been doing that and some need to adjust to address the additional aspects of the rule. That is on the way. Defining significant projects, we have had a lot of agencies make a lot of progress there and finish what they have been working on in that area. Identifying the projects will happen after the definitions are settled. Expect that to lag a little behind the definition aspect. In the area of TMP comment that is still in the earlier stages I think that it will be affecting projects more after October whether they come on line and the TMP is developed for those. A few of the areas are at the more challenging areas are the area of training, and determining what is appropriate training. Agencies are looking how to update their courses or some materials that we might provide such as the Advanced workshop that will help meet some of those needs. The data area, that is an area that will evolve over time. That is an area that we will be booking to put some more information out on, just a technical resource to help in that area. Process reviews, some agencies have moved forward and completed that. Others have looked at Traffic Control reviews that we already do, how do we expand that to address what is currently in the rule to meet the process review requirement? This is my last slide here, a lot of states have formed some type of work group. You will hear that in a few of the presentations coming up. The process of developing the policy, it might be a yearlong process to develop and get approvals and a policy in place. That is an approximate timeline. I would say that most states are well under way, almost all are. There are a few that are not in that category. A vast majority have moved ahead. I will introduce our next speaker. You will hear from some states that have moved ahead significantly and accomplished a lot, and in a large degree are barely completed with their efforts to implement the rule, or at least to get things in place to bring that implementation into action within the agency. Our first speakers are from Washington state. One is Frank Newboles from Washington state DOT and he will be a defined by Cathy necklace. Frank Newboles is the safety mobility Manager. He has served for 29 years, mostly in construction and traffic engineering. He has also been the state works on manager for the past seven years. He had previously held positions as a regional works on an engineer. He served as the technical and policy expert to the task force. He was on the technical committee and officers on the safety committee. Cathy Nicholas is currently in the Olympia Washington Federal Highway Division. She is the construction pavement engineer there as well as the division works on safety contact. She is a registered in the state of Washington where she has worked for the last 14 years. They will work together on giving us the next presentation. We will get started here I will start off with our lead portion here as we get into our implementation overview and then Cathy will join me throughout the presentation later on. Just to spend a little time where we are over all with implementing the rule. I wanted to mention that the concept and the intent of the rule matches pretty closely WashDOT's philosophy which this. We felt it was a good thing and could see no road blocks in moving this ahead. Part of that reason, the reasons behind that, we were already accomplishing some of this work, and we maybe we're not calling it the same thing or doing it on a consistent basis or an overall systematic level, but it is really where we want to be. I think that we have a pretty good and consensus internally that that was the direction to go. I think to help us get a little push in going in the right direction. We started early in the process, like a lot of states did would be advanced notice of proposed rulemaking and worked through that and participated in some of the ongoing national discussions through and other various conferences and tried to stay on board and learn from other states. The teams that we developed internally here were a combination of some WashDOT's teams and some partnerships with the FHWA as well. For us, the major elements that we had to tackle to accomplish the larger impacts from the rule were developing a new policy, which we will talk about in more detail here, and then updating our design manual to include a new WorkZone section and overhauling our training to accommodate the new rule. Just as a quick status, we have a few remaining items, probably the largest major element that we have left that we are working on is our WorkZone design. Overall, I think that we are pretty well on track to working through this spring and summer and getting all of those pieces of the puzzle together. Just briefly, our experience so far, it has been so far so good. We have been getting good feedback across the state. I think that we have tried to work on that concept of we are doing the good things, but we need to do them smarter. What we mean by that is to be more consistent. To it on a broader scale, looking at all of the WorkZone impacts and not just focusing on the project level. Some of our challenges are, we need to put a little more detailed guidance on their on TMP, which we are working on. We are also working on the elements of the rule, and a lot of the things that we have developed and integrating those into our existing processes. We have done quite a bit of that already. This is sort of a fluid thing. The more that you work on it, the more that you not see opportunities along the way. We are working on some WorkZone milestones in our process and that type of thing. We have some next steps, as I mentioned before, the training issue. We are also looking at establishing some performance measure for WorkZones. I think that we will be, especially later this summer and fall working pretty hard on that ongoing oversight and support to make sure that things move ahead regularly. Here is the main focus of today's discussion. That is, our new WorkZone policy it. This is just an outline of the next few slides. I wanted to talk briefly about our previous policy. We did have an existing policy. I wanted to talk about our new policy but also the concept that we used. We refer to it as an overarching concept. Talk a little bit about defining and managing the program responsibilities, using the policy to set the direction, but not really get bogged down in the details, at least not at the policy level, talk about our development team, we partnered with federal highways on that and talk about our WorkZone Safety Task Force and the role that they play. Our previous WorkZone policy dates back to 1994. This was developed through our web WorkZone Safety Task Force. Paul is prior to that we did not have a policy. I think the approach to establish that policy was well intended, but it was fairly generic. It did elevate works on safety to a more legitimate level by establishing policy, but it did not go into much detail, it did not set much direction. Is more or less had a vision and said WorkZone works safety as a priority but did not go further than that. It was a good start. In our new policy, we definitely build on that good start. I'd think that as far as looking at how our department is structured, our new policy fits that structure quite well and is a definite improvement over the old policy. As I said, we refer to our concept as an overarching concept. What we did was, we wanted to pull together all of the new programs that have WorkZone responsibilities, identified those and also identify those at major responsibilities within those programs and start to establish those roles and expectations where the previous policy it did not do that. The intent behind the policy was to blend our own needs with the requirements of the rule. I think it was a good fit, because that is basically where we wanted to be any way. Again, we did not want to focus on the details at the policy level. Those specific procedures, processes, standards, all those things are really accomplished within the program itself that those are related to. It tied very closely to, I think, our process of letting the Program Manager manage that program and work out the details as to how those elements are going to fit within that program. I probably should mention that working with the Program managers is an important step, new rules are something that can be difficult to deal with. In this case we work closely with the Program managers to integrate the rule requirements and our own needs within those existing programs. I think it was accepted at a much better level. Just to get into that a little bit, as far as defining and managing program responsibilities, we had to take a hard look at what are all of the impacts? We had to move away our old position of where we it primarily focused at the project level, those WorkZone safety and mobility impacts that existed at the project site that we expanded way beyond. We also felt it was a very important to take this management approach but work within our program structure. We tried to make it not so much as a new program or a new process, but built within the existing program structure. That was an important consideration in that it was accepted. I think it will be more of a natural fit. Probably another important keep within the policy was the primary WorkZone responsibilities. Who does what? Who is responsible for what WorkZone impacts and what is required? We also established some resources and support, where to go for some assistance, what resources are available in ways of training, that type of thing. Set the direction, not the details. We heard this over and over. Do not get bogged down with the details at the policy level. That is the approach we took. There are many ways to do this. I think this approach was the approach that seemed that the overall consensus was that this was the way to go and the correct step. We had the best overall support for this. I kind of mentioned this before. At the program level we wanted to establish those primary responsibilities, and what are those related issues and actions without going into a lot of detail? As an example, I included the one portion of this. Our communication office plays a role in depth through their program, they are going to support the public information component of this. They already have a good process in place, but, of course, there has been a lot of good information that comes out of the WorkZone rule. We just wanted to identify the communications office will play that role. Is essentially, they will use existing resources and conscience within that office. Where the detail comes and is outside of the policy level. That would be at the region or project level. Our public information officers will work at that level and use some of the new tools that are provided in the FHWA Guide on public information plans and are some of the things that we put into our new design manual section. For our development team, we began meeting in the early part of of-excuse me, at the end of 2005 and beginning of 2006. We knew that we wanted to get a good group together, federal highways and myself and safety and design engineers. We also wanted to include the local program people on the team, so that we have an one person on the team from programs. We have a design person or several design people. Of course, we wanted graphics. We started meeting on a quarterly basis, more often as needed. We knew that we needed to contact particular people. We met with them several times. We would have small meetings with them if necessary. We talked to project management people and talked about the final set rule. We informed different people about the final rule and how it might impact their programs to get their feedback. We started putting together a policy. We thought by getting all of this input we would have the best into our policy and they would know what to expect. We have been building support for the policy by doing it in this fashion. I just might add to cap these comments that I saw this as one of the real highlights of our work effort to implement the rule and that we have a great relationship with our division office here. If this was a great opportunity to pull this together. When you are trying to implement these new requirements and knowing that you have your partners from federal highway there. As you are working on this you are instantly building that support. It essentially, when you are done, you almost have that built-in approval when it goes in. It was a real benefit. This next slide, we wanted to mention briefly about our work and safety task force. They are probably the other main group that we have worked with to bring the WorkZone rule into implementation in Washington. This group has been together since the early '90s. It is a well respected group and a good cross-section of the members in this group from executives down to managers. We have project engineers, and technical people, and it really provides a good sounding board to take these issues and make sure that we stay on track and are headed in the right direction. We have some excellent feedback from this group. This group will also help us to provide the ongoing oversight and work as an advisory group and bring those issues back to this group as we see as we work through implementation. I might add that we wanted this group to feel that they have ownership of this policy, that they needed to know what was in the executive order in this policy and the familiar with it. In some sense, they needed to facilitate the implementation of this policy, if it would come to that. I want to talk briefly about the policy document itself just to give you an idea of what it contains. We have an existing process where we refer to this as the secretary's executive order. It is built into our normal policy making process, where we have a pretty comprehensive review and comment and so forth. The policy itself is a fairly simple four page document that describes the purpose, why we need this policy and what it is intended to do. The executive order itself is the direction to the Project managers and their responsibilities. We have a section that is the actual information to carry out the order. We broke that down into our five program areas that contain WorkZone responsibilities. That is where we go into the detail as far as establishing, not only of the direction, but the primary responsibilities, whether it is draining or strategy development or whatever that might be. Like the example I used before with our communications office assisting with public information plans. I think it is a great tool in that it pulls everyone together. We are on the same page and know what is expected and work to build those details into the related programs. This is our final slide here and some final thoughts. Looking at our policy, overall, it has been a positive experience. We have some challenges along the way and expect to have some challenges in the future to get everything implemented and flowing smoothly. Our planning and programming group, it is not one of those things where this is a relatively new step for us as I imagine it is for a lot of states not that we have not thought about WorkZone sides before. At that level you are looking at a lot of things that are on a conceptual level that might be difficult to grasp. We are going to be working with that group to make sure that we get some good benefit out of that. Another challenge that we have is to capture some performance measures. I think we have some good ideas on how we want to do that. We will keep working on that. The policy also provides, I probably mentioned it before, a good organizational tool that keeps everyone on the same page and the expectations are there. As far as the actual implementation, I think that we are moving ahead towards the compliance deadline and seem to be on track there. We do see this, I think, with our partners in federal highway, we see this as the date of October not be no magic other than we want to reach compliance. There will be an ongoing effort to pull this all together. Finally, not for anyone's benefit that wants to look, we have a WorkZone Web page. The address is listed there as the last bullet. Our policy document is contained there as well as a lot of other resources. That really brings us to the end of our presentation. Thank you Frank and Kathie for sharing all that you have been doing there in Washington and for the inside, particularly on how you work together. That is nice to hear that you are about presenting together on the webcast. We will move to Maryland and hear from Jawad Paracha. Jawad will talk about their process as well and give us some insight is to what they have been doing in significant projects. They have created some float charts. Jawad Paracha is currently working as the assistant division chief of traffic development at the Maryland State Highway Division, WorkZone areas managed by Jawad. He has his-of Arts and civil engineering and master's and--from the University of Maryland. He is a professional engineer. One Jawad? Thanks. To start with, my presentation will be in two main parts. The first part is dealing with the process to get into compliance. The second half will be about the significant projects and how we came up with the flow charts and what the flow charts are. We it started our process back in the summer of 2005. We looked at our current business as it related to WorkZone safety and mobility and it was decided by a senior management that we were going to look at the entire process, not just the root compliance details. We have a consultant on board, on site that helped us during the whole process. Our initial meetings were to come up with a WorkZone business plan and identified the areas and the timetable for completion. At that time, we set our compliance date to be at the end of 2006. These focus areas were not just focus on the federal rules at how we what look at our WorkZone safety processes. This is just a quick look or a snapshot of the focus areas that we looked at. This shows how we are going to be looking at it from this point onwards. Sorry to interrupt. Could you speak a little louder? Sure. Thanks. This slide says about how did we start after coming up with a business plan. The next step was to put together a draft to the safety and mobility council to serve as our guide during the whole process. This went to various FHWA offices, contracts, Maryland State Police, the University of Maryland, and we met only when it was needed. That means that we would prepare the draft plans or draft strategy about a certain aspect of our program and the present it to this group and get their advice. Even if we were not meeting, we would get their advice through e-mail's from smaller groups. The first step of actual work was after putting together at the safety and mobility Council was to [indiscernible]. This is rule specific, what we have made it to ensure that we are satisfied all of the rule requirements. We identified the areas that we already have the processes in and already meet the rule requirements and places where we can improve. We did a review and also contacted several states and Highway Administration's to find out more about what others are doing in those areas where we thought we needed more improvement. We identified some of the processes and strategies that we need to work on during 2006. This slight, again, basically, I will not go into detail. It emphasizes the same thing that we talked about in the last slide. We talked about various strategies and processes that needed to go into the existing development process to be in compliance and to improve our processes overall. Looking at the budget development process, we determined that in most of the cases, we are in compliance. We do go through most of the analyses and impact assessment and management plan and all of those kinds of things for bigger projects. We do not define them as a significant high project. We do not the fine-but we do go through the process. It was more of documenting what we already do. We had to revise a few of the processes and come up with a new processes, especially on our public information and communication side. And most of the cases, we were already doing best. It was a systematic approach to the problem. Briefly, what this slide is stating is that most of the offices that we contacted, and everyone thought that it is an excellent idea, we need to do more, but the question that everyone had was, who is going to do this additional work? How are we going to get these resources to get this work especially related to documentation? In most of the cases, especially the conflict was between the District and the design offices and who would be the lead? The solution was to share the responsibility. We got be solution for the board of senior management. In this case, where ever we would-we would try to address the concern of the individual offices, come up with some solutions and resolve the conflict or address everyone's concerns. But, if there was a problem, we would go and presented to senior management, our chief engineer and administrator and try to get a vinyl decision on how it will be done and who will do what. On this slide, we are showing the briefly what some of the flow charts for responsibilities are and detailed process these that we came up with. In this case it is a summary of who is going to serve not as a lead on the traditional strategies, traffic control plan, design and assemble is going to be in the lead while the district signed off on an it. The Office of Communications will be lead and sign off on the planned. This is a brief summary of who is going to be signing off on various stages of transportation management. Lessons learned. Basically, getting a buy in from the senior management and input from those doing the work. They helped us a lot. We had the by in during the process. Let's move on to the next one. Compliance, we met with our Highway Administration during November of 2006 and presented all of the information of what are the requirements and the response abilities and followed up with the actual memo and the necessary documentation related to our new process these. We received notification of compliance in the first week of January. The Business Plan approach worked very well. Where are we headed from this point onward? Our plan is to include transportation management plans with all significant projects that are advertised after October of 2007, provide training to the district offices on new policies and processes. We are indeed process of going to every district office and having a three hour session so that everyone is on board with us. We met their supervisors, but we wanted to make sure that all of the staff is aware of the policies and processes. Also, as part of our training, we are also looking at the updating of our basic, intermediate and advanced WorkZone courses, which is offered through the University of Maryland. They are already in place. We just need to make sure that they have the necessary information related to the new processes. We are also putting together a WorkZone analysis guide. So, we are maybe a month away from finalizing that analysis guide. The next step is to develop some the exemptions for projects that are identified as significant projects but we may not consider them within the state has a significant project. The next two slides to go through the plan process, the different steps. This is more of a project development process. We can skip that for the time being. If you need more information about these processes, please feel free to contact us. I am moving on to the significant projects the flow chart and how to define a significant projects and the actual flow chart. This started at the beginning in the first half of 2006. It took us a long time because of the approaches. We decided to go with the qualitative approach. The main reason was that, basically, smaller dollar projects may still have significant impact or require additional coronation. Similarly, there are some larger projects that might not be significant as far as the impact. We needed to look at safety and mobility and factors that affect these factors instead of just looking at the dollar numbers to define a significant project. We developed two flow charts. One was for projects that originated in the planning and design. These are major projects. And then projects that originate within the district and our minor projects. In this case, some of them that's for example, a guard rail repair are smaller projects might be a district function as opposed to a bridge construction. We are looking at both types of projects for our significant project definition. The major criteria includes vacation and safety mobility impact. I go into more detail in the flow chart. For the projects that originated in the design, you can see from the top left, the project's, aren't they can amend or worldwide? Senior management wanted to not just look at federal rules but the way that we do business. That is why we are including all of the state highways instead of just looking at federal projects. We are going to look at all of the projects on these highways. Then, we look at the next block. It is mostly mobility and safety impact. Mobility is, basically, an increase in the travel time. We have developed a mobility guidance where we look at queues for freeways and mobility on intersections. We have some specials and therefore mobility. For safety, we are mainly looking at ads and annual list of safety improvement locations. We are going to see if a project is already at an intersection which is on that list. Then, the assumption is that putting a WorkZone there is not going to improve safety. That is why we need to look at this and consider it a significant project and see what we can do to minimize the impact on the safety. Similarly, workers safety considerations are in there. We have a policy and place which is basically requires a barrier there where the it worker exposure is high. Looking at the policy and general, the first aspect is and safety. We look at several roadway characteristics, such as the type of work, is it the night work? We are anticipating--this kind of gives us an overall picture of what the project is and what the impact is going to be. If we see none of these impacts, we've been that it is not a significant project. If there are one or more conditions met then we go on to performing an analysis and select an alternative and go from there and develop a transportation management plan. This is self explanatory. Our highway design Office is already using this chart. They come up with a list of significant projects that have already been identified and come up with a team. At least 92 or three projects already have the team in place. We will see how this process goes and how our new process goes in the next year and we plan to perform an evaluation on these processes and see if we need to make any adjustments for next year. The chart is for the District and minor projects that I explained in the beginning. We have broken it down into major and design Office projects and district or a minor projects. This, basically, is related to the definition that the Federal Highway uses. It is the new federal rule, Robert that requires a lane closure on the end Express try for more than three days. For those types of conditions, either we are trying to come up with a blanket exception category where some projects will not be considered at significant at all. If the project is not one of those blanket exemptions then we need to go through the same process, looking at analysis guidelines and looking at the mobility threshold's and trying to minimize the impact. We do not expect a big transportation management plan coming out. We are looking at a consideration of mobility and packs and some of the strategies to improve transportation operations for some of these smaller. That ends my presentation. Okay. Thank you, Jawad. Thank you for walking us through those flow charts. It makes the process more concrete and shows a little bit about how you came to that point. I appreciate your showing those. We will move to our last speaker who is Paul Kelley. He is a safety coordinator for the Department of Transportation. His primary responsibility is to develop and implement the and said the ability to meet the requirements of the updated role. Prior to his current position with the it department, he spent 11 years in the engineering section of the location and design division where he managed the it Standards and special design work or. So, Paul is going to talk to us about VDOTs the process. Thank you, Tracy. What I am going to do is talk about some background work at the department did as far as getting prepared for coming up with a policy to meet the new rule. I will talk about what our current guidance is and then onward to our training or requirements, which we are finalizing right now to talk about our implementation status and some lessons that we learned when going through this process. In June of 2004, a group comprised from our design divisions, our traffic engineering divisions at both from central office and from the district's at that time as well as some Members from our research council out to gather and did a review of the vinyl roll and some of our processes and procedures and develop some recommendations to meet the final roll. In this instance, what they recommended, we parallel what we were currently doing along the lines that the design divisions would actually develop the plans with input from distant traffic sections, and residencies and other groups. They also recommended a joint memorandum between our location and design division and traffic division the written as far as policy, as well as the specifications but that would be developed by contractors to meet that new role. They also discussed training. In this instance, principally for the designers and gave us some new information as far as work to do based on the types of projects at. Date did that based on the complexity of the project and what information would be required in the transportation management plan for those of various levels of projects. From that, it was probably-hour work Research Council was doing a study of information from other states and put together a report as far as the recommendations for developing transportation plans and Virginia. It was an overview or survey of what other state DOT were doing. At the same time, another individual from the Research Council was serving our own districts at that time as to what they were doing. Primarily they weren't looking at what we were doing for traffic analysis. As you can see, there is a link that you can go out and access those reports that were developed by our research council. We try to, as out what the First two presenters talked about, as making this a part of our existing process. We deviated somewhat but rather than form another committee, we thought it would be prudent of us to go out and talk to the practitioners starting with those folks in the field, which we knew from our reviews that we do it periodically on an annual basis that we were getting some very good work out there. We were getting a public information campaigns on our larger projects and working with traffic operations, but we knew from our current policies that they were somewhat ambiguous and most of the planning started very late in our preliminary engineering process. What we did was we started out with, what do we need when we institute transportation management plans and work our way back from the implementation process at to the design. We started with a series of small meetings starting in November of 2005. We started with some regional meetings would district traffic and design and construction folks. Our local FHWA division and safety engineer participated in several of those as their schedule would allow. We also, at the same time, had two, or I guess semi-annual meetings with our work WorkZone plans. Www.found out what works well and what did not work well from design to implementing our transportation management plans. From that, when we started developing a policy with that information. What we did is we had a series of droughts. During that time we went from district operations and distant traffic engineers into a regional operations where we went from nine districts down to five regions. We went through a review process with the traffic engineers, our regional operators as well as the central office design unit, Public Affairs, and through that review process which came up with a draft and submitted it to our division offices safety engineers, FHWA it division office for review and comment. Once we got all of that information back, we went on and implemented this by getting both managers the of those at two divisions, and design and traffic to sign off on it. We started off as early as we could to start at the beginning of a preliminary engineering process that existed. In addition to that, while we were doing that, we also went on and conducted some other studies and information. The first one was to look at software for traffic analysis. Although our district traffic personnel were doing that, it was-it very a lot from district to district. What we wanted to do was come up with a little more consistency between the district and what they were using and when they were applying it. We also wanted to go ahead, as I stated, our colleagues from Washington State and Maryland and wanted to incorporate this as much as possible to our existing process as far as the design. We wanted to try to avoid coming up with a whole separate Johnnetta of charts to go through. The other is that it alleviate the concerns and apprehensions that people have as far as this being a giant new process that we wanted to avoid. We knew that we were doing a lot of things well. Win just needed to organize it and come up with a definitive process. At the same time we developed some provisions as it relates to the contractors proposed transportation plans. Www.again, this will give you an address to a website where we have this particular policy. We instituted in August of 2006, primarily because we wanted to get out from those traditional DOT projects, since they do need some lead time in developing designs along with the transportation management plan. What it does is provide guidance as far as managing those impacts to traffic. What we have done is to refer back to the Publications from federal highways, especially appendix B, guidelines that are already published that they could follow to traffic operation plans. We also became court decided or wrote down the actual responsibilities for Project teams in developing these comments the construction phases of the project also. What was basically having in these instances where a lot of these plans were being developed at the very late stages of the design process. What we tried to do using the existing system that we had an process that we had was to move this up so that at the milestones that we had at each phase, and I believe there are five or six phases, that we had guidelines out there as to who is responsible for tasks at that particular point in the design process and in the construction process. That gave them an automatic to request that they were comfortable with and were using at this particular time as we went through the development process and in the construction phase of this process. We also categorized projects on the complexity for the recommendations of that task force. What we did was we were limited to three, they sometimes went up to five. And some instances there is a big divisions of their complexity as far as time Groot and it had to deal with their complexity. Www.-category one. It is a very simple project. It is typically our maintenance project. It could be a permanent work by a developers. Typically, traffic would be maintained at all times by flagging or lane closures provided that they did fall within an hour when closure policy. The regions were a publishing and developing it at that time. Again, very quickly, we looked at those things that we would typically have with a traffic control plan. We also recommended Transportation Operations plants. It had to a typically deal with the volume of traffic or the length of any particular WorkZone. In this instance I believe one half mile was what we determined would require a traffic operations plan. Category two projects would be our typical roadway construction projects where we are adding capacity. We were looking at lane closures and possibly the tours. When we it did that, we look at traffic impact assessment. As the complexity of these projects increased, we went from looking at an impact from the standpoint of the delay time onto into doing a simulation using simulation software. All of these would have detailed plans and would require some sort of the public communications plan and transportation operation plan for distances greater than a half mile in length. Our category three projects are significant projects, again large-scale phase, multi-year construction projects. We did not limit them to the Interstate. We look at arterial roadways, especially within a transportation management area. We defined those. We have three areas and took an information and expanded it so that in the Northern Virginia area we are looking at starting at just west of the airport and swings down through the Fredericksburg area into the Richmond area. We have the surrounding the colony's. It was at everything east of Williamsburg. All of those projects would have to have a detailed traffic on impact assessment. They would require detailed plans as well as public communications plan and an operations plan. As far as the training requirements, we formed a WorkZone committee and December of 2006. We took a little different approach where we had members from at mean of an operation and representatives from residencies as well as, we have a specific group that deals with training in the it department and FHWA and representatives from the industry. We determined that training fell into one of three distinct areas. We tried to a parallel what you would do going on from designing and on throughout construction and finally to operations where you maintain the roadway itself. In that, we came up with three levels of training in. In this instance we paralleled what the Florida DOT was doing where we had a basic course that focused on a daily set ups. It lasted one the and intermediate courses that focused on long-term WorkZones. It was a two day class. The advanced focus on the design elements that was sort designers. The committee went through and identified positions with higher responsibilities that would require a WorkZone certification through a private vendor. What we were looking at is that we have a boiler plate or template training program that was developed on by the department for all three of those. We were going to allow private consulting firms to use that or developed their own base on an approval by the instructor or the course itself, depending on the approach by the private contractor to go ahead and deliver this training. This is nothing more than a table that shows that. We went from maintenance to construction inspectors. We have a group of senior inspectors whose primary responsibility is to work with WorkZones and how will they function. We have a series of regional safety coordinators'. That is their principal duty. Update the principally deal with WorkZones and reviewing them to ensure that they are in compliance with the plans and to provide advice and guidance not only to the design personnel but also to the contractors and field personnel as far as changes in order to make them more efficient and safer. We have a requirement in there for the contractor personnel, the difference between the basic one day class and the two date intermediate class is the traffic control supervisor would be on the larger more complex projects and that we have a separate provision set up for a contractor to establish and have a pay for a position as a traffic control supervisors to deal exclusively with the traffic control, and then a one day class for utility and permit personnel and a two day class for our roadway designers. Suit date, what we have is an ongoing program where we look at, basically, our VDOT Basic course. We do that for me nuts and construction as well as utility and permanent personnel. That is an ongoing thing, usually in the off-season as far as construction. We have an ongoing program were. With that, we have come up with 2A pilot courses. The first is for our Traffic Control Supervisor class. In November we did a class for the designers. Since then we have to finalize that or made some revisions to it and held our first designer class in February and our first specific supervisor class. We hope to have additional clauses and May. Along with that, we are in the process of developing a Web based course for the police. In this instance it would be an overview of what their requirements would be as far as having the principally state police or any state police within the WorkZone to monitor activities or for an enforcement. That would be a web based course. I think we are looking at between two and four hours. We have yet to acquire formal approval of our memorandum. We knew that when we issued this that we would end up having to make changes to it. We knew it would not be perfect coming out. We have some changes and will be adding those and submitting those in the next two months. With that, we wanted to add our final training requirements which are in the final approval process. We have some specifications, not only dealing with training and requirements that I noted as far as the contractor personnel, but also for, again, contractor proposed transportation management plans or alternate transportation management plans to. We are in our budgetary process as far as establishing the annual training schedule and the budgetary requirements that we would have. A couple of lessons learned, it be a smaller group of worked well. We had an informal discussion and worked out well and what did not work well. We have several large projects where things did go well, but as I said earlier, a lot of that process have been at the very end. In several instances, there was little specific guidance as far as the public information campaigns or communication plans. Also from the standpoint of traffic operations. We were able to learn a lot from that meeting from the individuals. The drawback to it is just to be able to logistically schedule all of that and get groups together was somewhat daunting. Other items along with that, we have a recommendation to get the training to proceed the implementation. Some of this is pretty much self inflicted on the standpoint that we have had a lot of turnover within our department as far as personnel, primarily dealing with retirement. We are an aging department here. We would have preferred to have a little more time to have our training completed prior to implementation. If the other is additional lead time. Just given what would be a standard process, although we had a lot of this in place. It would be preferable to have a little additional time to die of the i's as far as funding everything with a lot of exceptions. A lot of that was self-inflicted. One of the other problems with these statistics of the small group were disciplined meetings. It takes a lot of time to get that information together and go through a review process. I am trying to think of some other things. Like I said earlier, we did have a lot of good things going on. We did try to, as much as possible, to eliminate some apprehension with this by utilizing what we had out there and just adding to it. If you need any more information, as far as information on what we are doing, the previous links are there to show what the Virginia DOT is doing to implement the new rule. Okay. Thanks very much for the training information. It sounds like you have a good plan in the works there. We have seen a couple questions come in on that and will get back to that. We have had a number of questions come and browed the presentations. I will cycle back to the ones from Washington state and give them a chance to address a few of those and will then come back to some of the other questions as well. For Frank and Cathy, there were some questions that came and regarding your work WorkZone committee and WorkZone groups. I thank you had none to different groups, but perhaps you could clarify that. You talked to us about this a little bit. Who is actually on those groups of? -l went entities are represented as far as consultants, cities, counties, etc.. If you could address that a little bit. Short, I will start. It is basically two separate groups, primarily. The it WorkZone say the task force is our largest group that is a statewide group. There are approximately 30 members in that group. We do have a little bit of mixed representation on there from contractors, but it is mostly DOT focus when with additional resources members to brought in as needed. The other group that we have used a lot, not only to develop the policy, but other issues related it is our new rule team. That is the joint team with federal highways and WashDOT group. That group is smaller, probably about eight people. We try to bring in a representative from those of major groups that have responsibilities in that area. Each major group within the DOT? Right. Right. For example, as broad as we got in our smaller group was we had a representative from our local programs office where we did not bring in local agencies but used them as our representative to deal with those issues that might impact locals. That was just an example. Okay. That maybe ties into a question that got asked a little bit later on about, basically, addressing issues with the locals and what might need to be done regarding local projects and are more of the town or city level. That would be a question for all three states as to how have you, in this process, how have you involved locals or involved your-your policy it might apply to the locals, or it might be working on something separate. How are you handling the local projects where they might be the federal projects and some states like. Here in Washington state, we have had a local program person on our team. They are up today on what they need to do at the state level. I think they also need to be developing some guidance about how it is going to be implemented at the local level four Project specific responsibilities. We have not gotten that worked out yet here in Washington state. The process that we are using their is we have local agency guidelines manual. That group will be updating that manual with the applicable portions that apply. We have also done some outrage through various conferences and forums to bring local agencies up to speed about the role. Kepi is right. We have to work out some of those details. It will they be working within the larger framework of your policy but needing to work out how that specifically affects their only under an honest and responsibilities? That is exactly right. The details of that will go into the local agency guidelines manual. That will become part of that process when we do that. There is a review process. There are comment periods that go with that. Okay. Jawad, what about in Maryland cut is that something that you have looked at at this point? We have shared in the nation with them, but we have not really, at this point, look at if they are revising their processes to meet some of this criteria. But, at this point, we do with the counties and cities traffic engineers semiannually. We have shared all of our policies. We have been telling them exactly where Maryland is heading and the it requirements. We have made presentations at our conferences. To the extent that we know what their process is going to be, we have not yet approached them regarding that aspect. In Maryland, how much of the road system is under FHWA as opposed to the local jurisdictions? Do we have a sense of deep write-downs? Eight yes, in terms of of percentage, I am not sure. The state Highway is only state highway. I am not sure. If I am looking at only be a safety side, looking at the crash statistics and those kinds of things, it is more of a state highway system where we need more improvement than the counties, mostly because we need lower speed limits and things like that. I am not sure exactly what the breakdown is that of a percentage of the highway miles. Okay. Thanks. Paul, what about and Virginia? Have you had discussions or looked at the issue of any local areas that would receive federal funding cut. We have not looked at it specifically, primarily because of Virginia is a little different than the rest of the country from the standpoint that with the exception of two colonies, almost everything that deals with design and construction or actual governance over the roadways comes from the state level. Virginia is moving towards more local control, especially from the design and construction perspective. We have a separate division that handles that. But, given the current policy as it deals with those agreements that we have with the localities as far as doing their own design and construction, they are still required to meet our policies. Our local Federal highways office is a very specific in ensuring that the state DOT and Virginia and retained governance over that to make sure that they need those policies. We have done some things similar that Frank has talked about in Washington that we have several forms to provide that guidance and when we are going to come in compliance with those new rules. One of the earlier questions was asking, this is directed to Washington State at the time. In your state, which office is the actual lead Office for implementing the role? It is your office or a designated office as a lead like. And Washington, that would be the headquarters to epic office. That is where I work. I am the state WorkZone Manager. That was a pretty good fit that it fell to our office to take the lead on back. Okay. There is another question that came up later, I think it was more abroad, which was asking is, and general, did it seem like the DOT had a specific person handle the rule? The person who asked this question that there were problems trying to implement that through a committee process. I do not know if any of you have experience with that. How does that work with having a work group or a committee, yet trying to still have a lead office and how that interaction worked out? I can start. Quickly, I think that is a good comment and very realistic. Anytime you try to do something totally by committee, it can get bogged down. It does seem that you need one person or one office have the lead role to keep things moving. That is the role that I try to play where I would try to assemble information and kind of outline it or bring it to the group so that we had a more workable level, I guess, to start with instead of starting at the very beginning about what does this mean? It seemed to work for us, or was more efficient to keep this on the track. Call, Jawad, do you want to make any comments on that? Eight in Maryland, our committee we called it out [indiscernible], our committee and general was basically for us to use it as a guidance. We would go there and get their advice and try to come up with a consensus. If we think all the parties involved are agreeable, we would move on if not, we will go to senior management and get resolution and move on to the next task. We were following our plan and milestone dates as our driving force that we need to make a decision. If we cannot, it will go to senior management and get a decision and move on. Okay. Thank you. It is a very pragmatic approach there. Let's see, we had a question come in, Jawad, who did the notification of compliance come from? You said you receive that notification. Someone was a curious as to specifically issued that but. The Federal Highway and the station in Maryland. It was not a particular-what is your contact a division and Mr.? We contacted the division administrator. We are -she was actually involved with us during the whole process. She was aware of what was happening. We had met Federal Highway Administration before ascending the compliance requests minute memo. We met with them and presented all of information and followed up with the Administrator. Okay. Thank you. One of the earlier questions that came and was regarded Washington state. You made some mention of performance measures and working on that area. I do not know if you can answer this in a brief way. What are some of the ideas for performance measures that you have? From the perspective of Washington, I know that Cathy and I have had some discussion on this. One of the things that we have looked at is the process that is already in place, the WorkZone self assessment process. There are several elements in there that could probably be used as performance measures, at least in a broad sense, could we do better, did we do better this year than last year, those types of things. We are still looking at developing the more detailed performance measures that are specific to the numbers of WorkZone crashes and congestion. How can we measure that? That is a little tougher. We will have some of the broader performance measures to look at. Okay. For those that might be interested in finding out more about the WorkZone self assessment, that Frank just mentioned, we do have some information on our WorkZone web site at Federal Highway that can point you in that direction and show you what the questions are. We did have-We only have able to more time and then will shut down. There is a question about VDOT. You mentioned training contractor personnel. Do you train them? If so, how do you train them? We'd do some limited training for the contractor personnel. Primarily, it is just the one the, putting the information out, or primarily. We do that in conjunction with our local road builders, their groups, rather than working with individual contractors. As far as finding out, pretty much most of the cost as far as facilities and materials is covered by the road builders Association. We just typically supply one or more instructors. We take a team teaching approach when we do the classes. Okay. Thank you. We also had a question that was not directed at any one particular state but if you have any thoughts on how you will handing any training for law enforcement. Do you do that now? If not, do you have any plans to do that? Any thoughts on that aspect? In Washington we have had some discussions with our state patrol. They are very open to including WorkZone training in their training modules that they do at the State Patrol academy. We are looking at doing something along those lines. Right now, we are looking more at doing kind of less formal training at the level where our the attachment, hour shift sergeants will do a briefing on WorkZone safety. We have a pretty close relationship with our State Patrol, and they assist us to some extent an hour WorkZones. We have not actually implemented that yet. In this case, the training is not something that you have but are looking to start. That is correct. Jawad or Paul, any thoughts on that? In Maryland, right now, the troopers do come here, they come here for the entire day, but one hour of that is related to WorkZone safety. However, we are currently looking at federal highways cores Mandel that just came out. --course manual that just came out. As soon as the manual comes out, we are wanting to come up with a law enforcement course. Looking at all of these aspects, most probably we will sometime this year start a course. It would be given to our troopers. You mentioned that they come to the Maryland FHA. Did they come to the Academy? Is it if they got assigned to specific duties? It is part of their academy training. It is not just traffic and safety it. They look at various aspects from the incident management and those kinds of the things. They are looking at the big picture. One the hour is just on WorkZone. We did have a question, this is for anyone who wants to jump in and answer them as. A question came and about going through and looking at different strategies that can be used to mitigate the impact and sometimes those strategies get deleted later on, at least this has been the historic way, as the budget gets looked at more closely, something gets deleted. Have you seen any, do you think the rule will lead to any change on that, the need to formalize more than what they have then and are their cultural changes that might be needed? The it person was asking so that these things become implemented and not just discussed. Is that something that you will see a change in? What else might be needed to move that forward? I do not know if we can predict a change here in Washington. We have suffered through that. It is our hope that the TMP process, and managing that TMP process actively will legitimize some of those dings where those mitigating solutions will not be seen as extras or an enhancement or a legitimate part of the TMP. To do that, we need to make sure that we have a solid estimate of fraud and our accounting for the cost. In that sense, it is our hope that we will have more success with it. I think from the standpoint of Virginia, about the same thing. We will see some sort of a change. With doing this early on in our design process, we will be budgeting for it. The other thing is to legitimize it it has to do with the exceptions. Our current thoughts on that are simply that we have a memorandum on policies as far as design and exceptions. They will have to follow that same process. If they start debating things, they will have to justify it and get approval. Okay. Thanks, Paul. I think that we will have to draw it to a close here. I know there are a couple of questions that we have not been able to address. We will do our best to follow up on those after the Web cast here and get back with people. We have a project contact in formation. I will turn it back over to the Fort. To wrap up the webcast, let me give you some information on the coalition that put together the seminar series. On the first one here you will see the organization's. We encourage you to go to the web site and find out more information. From that site you can get to the link to register for upcoming weathercasts and participate in discussion forums to talk about information that were brought up on these webcasts. Additionally, you can sign up on that website for the newsletter. It will give you the latest in permission on what is happening in the operations world and give you information about upcoming seminars. Www.thank you for your participation and also especially think the Speaker's today for their time and valuable lessons that they have shared with us. Thank you. [Relay event has concluded.] (end)