Hello and welcome to the Talking Operations web conference on Road Weather Management. My name is Jennifer Symoun. I will be giving a brief introduction to the web conferencing environment before turning the session over to Ben McKeever who we are very pleased to have as our moderator for today’s seminar. Today’s seminar will last approximately an hour and 30 minutes, with 60 minutes allocated for the presenters and the final 30 minutes for audience Question and Answer. During the presentations, if you think of a question, you can type it into the smaller text box in the chat area on the lower left side of your screen. Indicate who your question is directed toward, unless your question is intended for all presenters. Please make sure you are typing in the thin text box and not the large white area. lease also make sure that you send your question to Everyone rather than just the Presenters. The presenters will be able to answer your questions during the question and answer session in the last 30 minutes. A file containing the audio and the video will be posted within the next week. I will type that address into the chat box shortly. We encourage you to share it with your coworkers. The PowerPoints will be able within the next week on the site. Attendees will notified of the PowerPoints, recording and the closed captioning of the seminar. I would like to introduce Ben McKeever. Ben oversees the realtime traveling program and the Road Weather Management program. Prior to joining U.S. D.O.T. he worked at the melt transportation commission in Oakland, California. Prior to joining MTC he worked for eight years as a consultant on numerous projects with emphasize on ITS planning, design, and implementation. He is a registered civil engineer in California and Missouri. Thank you, Jennifer. Thank you for joining today for our webinar. I'm going to let Jennifer queue up the first presentation today, which is an overview of the Road Weather Management program. I want to give you a high-level overview before I turn it over to the others who will speak more indepth on their various projects. Okay. To provide backgrounds on the program, first we need to examine the problem. We know that from research that the 24% of all crashes are on slick pavement or under adverse weather conditions. About 25% nonrecurrent delay is caused by adverse weather. If we can do something to impact the impact of adverse weather we can make a big dent in the surface transportation problem. In addition, congestion impacts productivity. Weather-related delays at about $3. 4 billion to freight costs annually. It also has an impact on the environment. The congestion has an impact on air quality. Inefficient use of chemicals can affect our watersheds and infrastructure. Our vision of success is on your screen. The way we hope to do this is to achieve anymore, anywhere radio weather information. That's our tag line for the program. The Road Weather Management started at FHWA back in the '90s. It got started with SAFETEA-LU in 2005. Specifically SAFETEA-LU 5308 established the R&D program. Our program has been set up to follow the recommendations that come out of that report. We're directed to improve road weather information throughout the United States. The multidisciplinary stakeholder included NOAA, national science foundation and AASHTO. The weather enterprise are the ones that package the information, provide upcoming weather conditions and events. Fundingwise the SAFETEA-LU legislation allots $5 million per year for a four-year period dating back to 2005. Tomorrow we'll be starting the final fiscal year of our guaranteed funding. After we anticipate continued funding, either through new legislation or the ITS program. The program so far has been successful, we anticipate getting continued funding. Want to talk about the structure of the Road Weather Management program. Following the SAFETEA-LU guidelines we've organized it into four areas. The first is the stakeholder coordination. We have meetings every year in the summer. In addition we also have MDSS meetings. One of our major stakeholders is NOAA. Their business is also weather. NOAA has not really focused as much on the surface transportation aspects of weather. They've been working with the aviation and maritime industry. We're working hard to make sure that surface transportation is on their radar well. One of the other areas that the program focuses on is applied research. We do a lot of work, as far as developing decision support tools, and also weather response to traffic management is another area of applied research that we're starting to dive into. We'll do more work moving forward. The third area that we have is the technology transfer and training and education. We have a really good website on the FHWA operations, dedicated to Road Weather Management, you can use the research identification tool, we have best practices and various publications. We have courses online also. Of course, we have events such as the MDSS product demo showcases. We'll talk more about these, also, in some of the upcoming presentations. The final area is the performance measure and evaluation. We recognize the importance of showing that tax dollars are spent wisely and having a positive impact on the surface transportation system. We spend a good amount of our program dollars trying to do evaluations of the major projects. And also coming up with good performance measures to make sure we're able to capture the benefits of the work we're doing. Just a quick slide here. I mentioned the best practices. I wanted to highlight this. This is one of the top ten visited sites on the FHWA operations website. One of the most popular web pages I should say. This is over 30 case studies. You can get basically, information on what state D.O.T.s are doing from a wide range of topics. A lot of good information there, if you haven't listed that. A lot of people are finding a lot of good use out of that, it's a good tool. Now over to the rest of the agenda here today. We'll talk about the various programs, some of which I have talked about in the overview. Ray Murphy and Dean Kernan will talk about MDSS. Roemer Alfelor and David Yang will present the Weather-Responsive Traffic Management. I will give an overview of the Clarus Initiative. I will then turn it over to Brenda Boyce to talk about the system itself. Then some quick updates on VII. With that our next speaker is Ray Murphy. Ray provides technical assistance in support of the department's goals. Ray joined FHWA in 2001. Ray holds a bachelor of science degree in electrical engineering. He served as an officer for ten years in the U.S. Navy. Ray? Thank you, Ben. I appreciate that. Good morning, good afternoon, good day to everyone. As we know, we all know winter road maintenance is a challenging endeavor for any highway maintenance agency. Be it a state D.O.T. or county, or municipal. With highway snow and ice split second decisions have to be made as to when to offer traffic warnings, what de-icing materials to use, and how plowing will be routed. These decisions determine the safety and mobility of the driving public. In the '90s the program saw a gap between the transportation community and the weather forecasting community. It was decided at that time to invest in the development of the maintenance decision support system, the federal pro toe type, MDSS. The goals were to improve safety and mobility and improving productivity in a cost-effective manner. Through partnerships with state transportation agencies, national labs and stakeholder community of public transportation agencies, including the private sector MDSS has evolved from a concept to a functioning application. It is a computer-based tool that provides winter maintenance personnel with route specific weather forecast information and treatment recommendations. It's pretty well broken down into four different modules. And this first -- the top module is where your road weather information and different models are taken into. It's then fed into what they call an data fusion module. Road and weather information is fused, all of the data is ingested. That goes into the third module then, where the rules of practice for antiicing, de-icing, treatment recommendations is customizable for that specific agency. Then it's delivered into a graphical user interface display. Which should be noted this GUI was designed from practitioners from several state D.O.T.s. Here's an example of the display that you would see. It provides route specifically weather and road condition forecasts. It also optimizes treatment recommendations for treatment type, application rate, and timing. It provides more efficient use of salt and other de-icing materials. Pretty much in a nutshell it's a better use of man power and equipment, it offers near realtime road condition reporting. It has features where you can use for training for unseasoned maintenance personnel using historic playback . MDSS was not by any means developed in a vacuum. As this slide shows, we've been quite successful with stakeholder participation from a majority of state D.O.T.s throughout the country, along with the private sector and international participation. In addition to the great success we've had over the past eight years, our most recent meeting was last month in Nevada. 28 D.O.T.s were there, in addition to private sector representatives, academia and international participation. 33% of the attendees were first-time attendees. The focus was updates on development and deployment of new systems throughout the country and discuss the importance of cost-benefit analysis and shared experiences from last winter. As I noted already, we firmly believe that MDSS has been quite successful in building new markets, several have emerged. We now have a portion of the country that have MDSS provided by meridian and DTM, along with MDSS services provided by [ Indiscernible ] and also MSI corporation. What is new and updated? We're now using what they call the metro road temperature forecast model. We got that from Canada. We're also integrated fixed and mobile camera data, along with the new alerting system. We also now offer an archived playback for forecast and treatment recommendations. The federal prototype now has automatic vehicle location, and playback support. There's an improved GUI. We've made access to updated software via the web. It should be noted that the federal prototype is an open source, available to anyone. 5.1 will be available this fall. We completed developing the MDSS deployment guide recently. It focuses on helping transportation agencies prepare for MDSS deployment and maximize their benefits of the MDSS application. The guide was developed with the help of a panel comprised of state D.O.T.s, private sector representatives, and the FHWA division office. The primary audience are state and local personnel responsible for procuring, operating and evaluating MDSS tools, as well as for private sector vendors that provide MDSS services to transportation agencies. The guide describes general MDSS capabilities, benefits, and implementation challenges. It includes real world experiences of deployers, and documents lessons learned. It will soon be available as an electron document. Over the past year FHWA partnered with AASHTO and several other agencies, along with the private sector to develop three free regional support systems. The goal was to encourage implementation of this technology. It was created to be a neutral information exchange environment that provided an opportunity for transportation agency decision makers to gain practical, unbiased, well rounded, hands on experience with new improved products. The first was hosted by Nebraska Department of Roads back in May. The second by Pennsylvania D.O.T. just last month. The last was hosted by Idaho. Dean Kernan he was an active partner in all three product demonstration showcases. Each year there's over 1300 people killed on snowy, slushy and icy pavement. Annually we spend billions on snow and ice control. I wanted to take a moment to reemphasize the benefits on why transportation agencies should be encouraged in making a smart investment in their winter maintenance program by adding MDSS to their tool box. There's potential cost savings that can be achieved. Managers can more effectively employ resources and it will improve your consistency and material application rates. If you don't realize this, there may be a potential salt shortage this winter. We all should be stewards of the environment. MDSS maximizes transportation agency's responsiveness no customers' needs and expectations. Dean will now share with you why Illinois D.O.T. believes MDSS is a smart investment. This is Ben. I will introduce Dean first. He has worked with the Illinois dot supervising employees. He was selected as the 2007 district technician of the year. He is a member of the stated with snow and ice committee, serves as a chairman. Dean serves as the district with snow answer ice trainer. With that I will turn it over to Dean to give his presentation. Dean, are you there? I'm sorry, I was still on mute. [ Laughter ] Thanks, Ben and also Ray for the introduction. We spent 22 years behind the wheel of a snow plow. I got to see both ens of what we're talking about here. As a supervisor I'm allowed to make decisions in regard to man power and materials and the frequency of applications. Those are all primary components. Today we're going to discuss the cost-benefits of a storm that our weather provider, DTN, tracked across district 22. I live where you see the star there, in Henry county. The district is district 2, we had the storm there. Before I get started, I think you want to hear statics about Illinois to understand why the decisions we make are so important. These will come into play later. You will get to see the benefit costs of MDSS for my district and the state at large. We have 42,800,000 lane miles. As you can see by the little map on the side we have nine directs in five regions. They're divided into team sections. For the most part that makes up 165 garages. We also -- part of the decision making is our teamsters, we do have a contract, their fairly well paid, that also comes into play. We have 60 RWIS sites. Some of the practices here in Illinois, we've been employing antiicing methods for 15 years. Some of the garages are experimenting with some ag products. Right now we're using the treatment rules aligned with the FHWA. Some of the vision and direction that we see that Illinois is going to go into is sharing this information among our districts and surrounding states. We want to become more involved with MDSS. This was our first year of using MDSS through DTN. Also I would like to see us add AVL to the trucks. The storm that we'll talk about was our 31st event for the season. We had 1 to 3-inch predicted across the district. It was tracked on February 28 and 29 of this year. Like I said, it was in district 2 in northwest Illinois. You will see the decisions that we made and how our weather provider was used. Later on we will discuss the cost-benefits, and look at the state in general. To go into it, the day prior DTN predicted 1 to 2 inches. We really didn't have much to do to prepare for the day before on this event. We always hook up our trucks every night. In the morning the lead workers will assign the crews. The next slide shows us the forecast at 10:00 a.m. Here's the reason this becomes so important, at 10:00 a.m. is when we decide we will send our night shift home to rest up and be prepared for possible call-in that night. The time is important for us. We looked at our forecast and we did send our night shift home. They're instructed to be home, rest up, and be free of drugs and alcohol. We see that the radar is showing that the precipitation is showing up in the southwest part of the district, it's in the form of snow. The purple is snow advisory from the national weather service. Here comes some of our contract issues, our normal operating hours are 7:00 a.m. to 3:30 p.m. We have to make a decision to keep the day shift on or release them. Based on the information given to me by DTN and the weather forecasts and the pavement temperatures I sent the day shift home. Because the weather temperatures were so above freezing and not predicted to drop until 6:00 p.m. it was a good decision to make and a money saver. By this time I'm inspecting the roads and bridges. I sent the day shift home. I checked with the rest of the district, they had done the same thing. This shows so you can see better the road temperatures and the truck icon. You can see the treatment recommendations from the FHWA at this time. The little red truck denotes a change. That will come up here in a little bit. Our past practices would have been to keep the crews on and monitor the roads. You can save many dollars in fuel, materials by following this. I was able to go home, relax, have a little supper with my family, I would sneak into check the computer to look at what was happening. At 6:00 p.m. the temperatures were dropping. I did look out of the window. The ground was beginning to turn white. The roads were showing accumulation. I rechecked roads and bridges. I called in the crews at about 6:30. The direct called their crews in at about 9:30. I checked the weather again. I looked to see what they were recommending for our MDSS treatment recommendation. It shows we would be receiving less than half inch per hour. And that the recommendation was to use a light spread at 100-pounds per lane mile. As you can see now, we're going to skip through the night. By Friday morning the storm had gone through, it did leave a little earlier than originally forecasted. We did have a little bit of drifting, which is shown by the little arrows. Accumulations did range from 1 to 3 inches. The temperatures were up, we were able to use our material usage to just specific areas. In my area we just spread bridges and protected areas. We saved a lot there. Previously not knowing for we would probably have spread the whole route and just monitored it from there. We saved many for dollars in labor, equipment and in materials. Now, we'll get into the cost-benefits for district 2 in this storm. We improved our safety and service by not being out there in the way. Here's how we save costs. It shows like so -- we improved our callout precision by sending the day shift home at their regular time. That saved us $20,400. Some of the northern parts of the district saved more, they didn't have to activate their crew until 9:30 p.m. We avoided the one unneeded application. That was last year's prices there, this year we'll be spending about $53 per ton. We'll save a lot more. To continue on with the savings, we reduced our applications. We couldn't actually say what we saved in this particular case because some of the crews were able to adjust their rates to lower application rates. Some went to 100 pounds, some was at 300. Some of us only spread some bridges and overpasses. Our total savings for just this storm was over $92,000. As I said, this was a huge cost saving for us, just for this one little storm. Now to talk about the whole D.O.T. state wide. We'll improve our callout precision. For every hour we keep our crews home and not out on the roads we're saving 48 to $96,000 per hour. By avoiding unneeded applications , one application across the state will save us $710,000 in one application. We can also reduce our application rates. Now we're going to adjust the rate of spread depending on the forecast. We're going to be saving $150,000 to $350,000. These totals are in the millions if you wanted to add them all up. This shows what we spent in fiscal year '08. We did hit $90 million by the end of April. I thought it was high until we were out in Pennsylvania, they had spend $200 million. These costs were calculated at last year's labor, salt and equipment rates. Everybody has gone up, including salt and fuel. I think here we've come to the realization that MDSS is not just an option anymore, but it's an necessity. I would like to thank you at this time. We'll have some questions in a little bit. Thanks. Okay. Thanks, Dean. We're going to transition now into the next presentation, on Weather-Responsive Traffic Management. This will be presented by two FHWA employees, we have Rome Roemer Alfelor and David Yang. I will read their bios now. Roemer Alfelor works for the FHWA. He has a masters in transportation from MIT, and a HHD from Carnegie melon. David Yang leads traffic modeling simulation projects. He serves on the editorial board is a member of the transportation research boards user information systems. David received his bachelor, masters and doctoral from pursue. With that I will hand it over to Roemer and David. Thank you. Thank you. I'm going to talk -- David and I will talk about Weather-Responsive Traffic Management, which is one of the major program areas in Road Weather Management. Since our last meeting about two years ago we've had a lot of progress in this area. David and some of his colleagues have been providing a lot of support to us, to the headquarters, in this area. Before I get into the different initiatives we have, let me give a quick overview of the program area. I'm sure many of you already seen or heard this, but very quickly the Weather-Responsive Traffic Management program area's objectives are to develop strategies and tools to help agencies manage traffic and highway operations during bad weather. The strategies include advisory strategies, those that warn or inform travelers. Control strategies are those that direct, or regulate the flow. Treatment strategies are those that ensure that roads are free of obstruction. There are various types of strategies that agencies can use. We know that we are successful in the different activities we have in Weather-Responsive Traffic Management if we contribute, or help achieve the following measures of success. If transportation agencies are using both current and forecast road weather information for managing and controlling their traffic flow and highway operations. Weather impacts are not incorporated in models at this time. We intend to turn that around. We know that motorists receive various types of information from different sources. Our goal is to improve the quality and availability of that information so that they can respond more appropriately to the weather and traffic conditions. The work that we're doing in this area can be classified into three focus areas, or subareas. Weather response system, integration of weather in TMC/TOC, and weather and traffic flow studies. I will talk about the first two. The goals of our weather response system initiative are to bring together advance weather and road condition technologies. There's a lot of technologies out there available to the inspection agencies. We want to operationalize that. Specifically, we want to use that information for the types of strategies that I described earlier. A few years ago we worked, or partnered with Missouri . That effort was very successful. The system that was developed provides information on various types of road weather programs. That system used data from the national weather service digital forecast database, which is a high resolution data. That system was tested and evaluated in Kansas City for a period of three months. The general evaluation was pretty positive about the system. However, several recommendations for improvement were made as part of the evaluation. The most important recommendation was that a decision support capability was necessary for the system to be more useful for transportation agencies, which means that we need to incorporate rules of practice for transportation management for maintenance management and traffic management. That is when the idea of MODSS came about. To leverage the lessons we learned and the software we developed for MDSS and the prototype. And specifically we want to be able to expand the functionality of MDSS beyond the snow and ice control. We want to expand its functionality to other areas of maintenance and operations. This is a system that has several modules as part of it, including MDSS and the module beyond snow and ice control. The idea is for the system to use the data from various sources, including the environmental stations. As well as the data from VII sensors. To combine it information from with other types of information, such as those from traffic monitoring systems, traffic analysis tools, and the rules of practice for maintenance and traffic management. Those become the input for making, or coming up with appropriate strategies and guidance to aid the surface transportation diagnose mistakes about what to do to overcome the impacts of adverse weather. Last year we invited a number of state D.O.T. representatives, experts, to participate in a stakeholder meeting. Our goal is to gather requirements for MODSS in terms of the maintenance beyond snow and ice control and traffic management. We found after talking to this these experts there are some rules of practice that exist beyond snow and ice control, in terms of activities that will impacted by weather. For traffic management very little rules of practice exist. After this stakeholder meeting we synthesized the information we received from the experts, from the stakeholders, we developed a concept of operations document. We drafted the document last year. We'll be using, two use cases for traffic management, as well as maintenance beyond snow and ice control. Ben and Brenda will talk about Clarus Initiative after this presentation. The second focus area for Weather-Responsive Traffic Management is weather integration in TMC/TOC. We all know the benefit of integrating weather in traffic management. We want to document the existing practices, needs and opportunities. And to exist the TMC with the weather integration activities. Our general approach for achieving this objectives are first we want to be able to develop concepts and measures of integration to use to characterize the types and levels of integration that are currently being used by TMCs. Then we want to survey the TMCs to integrate their practices. Based on the survey we want to develop recommendations for improving their weather integrations. We've made a lot of progression in this area. We surveyed several TMCs across the country about their weather integration practices. We came up with some measures, or dimensions of integration. We characterize these in terms of their levels of integration. One of the recommendations was it's need to develop a weather integration self-evaluation guide to use to determine their needs. Earlier this year we completed a weather integration self-evaluation and planning guide. We worked with two TMCs in Sacramento and Milwaukee. The guide has a manual document and a electronic tool. It has six major sections that allow the TMC to evaluate their needs by identifying the weather conditions that affect their operations. And to get a better understanding on how the weather conditions impact their conditions. What types of weather information does the TMC need to improve their response to weather events? After that the electron version of the guide sorts through the information provided by the TMC and identifies strategies. The TMC looks at the storms and develops a weather integration plan. We are currently working with the Sacramento TMC on their plan. They're one of the two TMCs that conducted the self-evaluation, and came up with a weather integregation plan. We're also making sure that the TMCs that would benefit the most from weather integration are aware that the guide exists and is available to them. We also are going to identify and work with three of those TMCs to conduct a self-evaluation. Based on those working relationships with want to make the necessary changes, or updates, to the guide. Now I'm going to turn it over to David Yang who will talk about the third focus area, weather and traffic flow. Thank you. This is a focus area. I want to spend a little bit of time with you today to describe some of the studies we've got right now that falls under this area. Really the goal, as we have stated, our knowledge and understanding about how weather effects traffic flow is limited. What we want to do is we want to carry out a series of studies to better understand the impact of weather conditions on traffic flow, at macro and micro levels. A study in the past, we tried to develop the weather and traffic flow model using empirical data. We had a report published based from that study. That study served as our first step of future work we're doing right now. If you have interests to look into that report that report is available under FHWA's website. The title of the report "empirical studies on traffic flow in inclement weather." Right now we have three ongoing studies . We're working with some of the contractors right now. The first project is called the microscopic analysis of weather and traffic. We want to better understand when bad weather occur how does the driver behavior change. Everyone probably have the experience that when you are driving outside on the road that when you see snow on the ground, when you see the pavement is wet, most of the drivers are very cautious. We see a big change in terms of how the traffic volume, it will add up quickly, and impact the flow of the traffic. We want to better understand that. And hopefully incorporate the findings into the software. We have Cambridge systematics and Virginia Tech working with us. We're in the process right now, I'm sitting at my desk reviewing reports right now. This project has gathered all the literature that is out there right now related to driver behavior and some limited information on the impact of weather on driver behavior. I think the angle for this project is to try to yarn incorporate mathematical models, to incorporate this information so we can better understand and better predict the driver behavior when the weather out there is not at the ideal conditions. The next project we're looking into, we're working on right now, this got started a little earlier than the previous one. Incorporating weather impacts in traffic estimate and prediction system. What this project, unlike the other project, is really we're looking to the dynamic traffic assignment. What we want to try to do right now, the searcher at northwestern is using a tool called [ Indiscernible ], they want to use that software as a basis. Hopefully have findings that we can go in there to adjust certain factors within [ Indiscernible ]. We'll be able to model weather. Right now this project team has finished, they've completed their literature review, as well. We're in the process of reviewing the existing systems. We want to hopefully by the next time we have the presentation we'll have product that we'll be able to report to you, the audience. The first project in the series of this project that falls under weather and traffic flow is a project that just started this past summer. This project, unlike the previous two that focus on the dynamic traffic aspect, we're looking at the human factor component relating to what information that you should convey to driver and how do you convey this information to a driver. This is really a very important component, or important aspect of the entire focus on better understanding of driver behavior. Because you can have a very good detection system picking up the weather, you can have state of the art system to convey information, you can have very rich information to the driver. If the driver can't understand them or use them these information are of very, very little benefit. We're trying to review what has been done in other areas of user information. And try to take the lessons learned and recommend strategies to convey road weather information to drivers. We One of the end products we're hoping for is to try to get a research plan. So we can recommend improvements on how to send message, send message to the driver, and what method to use to convey this information to them. With that the last item right here is the contact information for Roemer and I. If you have any interest to find out what is going on with these three projects I have just described, feel free to contact us. That concludes our portion. Thank you, David. Thank you, Roemer and David. This is Ben again. I'm going to jump right in and kick off the Clarus Initiative discussion. I will give an overview and then I will hand it over to Brenda who is our contractor at Mixon Hill. She will walk through a demonstration of the system. She will show you what the system looks like and feels like. And walk through some of the functions. The Clarus Initiative . A system that would ingest data from multiple states and do checks and disseminate it out to whoever wants it for free. This slide here shows the basic milestones of Clarus. I will direct you to the bottom of the slide to the various high level phases. We started in 2003, and concluded the concept in 2005. We're right now in the middle of the multi state regional demonstration. The arrow shows where we are right now in 2009. The final phase is the transition to NOAA. We move Clarus into a production environment. We hope that NOAA will take on the functionality in the system that they're currently designing. We're working with NOAA to achieve that. This slide shows the environmental sites, deployments throughout the U.S. Basically, there's about 2500 ESS sites. A lot of municipalities out there that own and operate road information systems. We're getting some data from a few municipalities right now. At a minimum we hope to get ESS data from all of the states. This slide just shows the sideline design of the Clarus system. We have three servers. One does the data collection for us. It gathers data from the state D.O.T. servers. We get data from environment Canada. We're getting data from three different Canadian provinces. We're set up to receive data from mobile sources, such also your snow plows, or even a VII-type of system. Pat Kennedy will talk about the VII work that we're doing. The other server we have is a quality checking server. We check it against our sources of weather information and do a number of different checks on that. We have a web portal that disseminates the information out. Brenda will talk more about how that works. This map shows the current status of participation in Clarus. We've made a lot of progress over the past year. We have 18 states that are connected right now. Another 4 that are partially connected. And then the states this brown are penning connections. Those are ones we hope to get connected by the end of the fiscal year. We have other states that are considering connection as well. On the left I show local D.O.T. participation. As I mentioned, we have Canadian provinces in the northwest all feeding data into Clarus. The I mentioned we're in the middle. We completed phase 1. We asked states to submit ideas for concept operations. We received three different concept operation reports from three groups of states. We're pleased with what we received. We used that to develop a RFP. Which formed the basis of phase 3. That's where we're at right now. Phase 2 is basically getting the states connected. We have an incentive program to help fund that. We have some limiting funding for states if they're interested in connecting to offset some of the costs. We've made good progress in the last year. I showed the map in the last slide. 12 of the 18 states that I showed that are connected right now joined in the last 12 months. Phase 31 the request for proposals. We advertised for proposals. This week we hope to make an award to the winners of that solicitation. Once that award is made we have a two-year project. Go ahead and go to the next slide, please. We have a two-year project that will build out five different use cases. These are different applications that will use Clarus data in a multistate environment. Working with a private sector organization to help develop out these Claus enabled applications. We took the best ideas we got, worked with them, issued the RFP. I believe we'll be able to build out five of the scenarios we got. One of those is surface transportation meteorology. We We are also looking at roadway profiles files. As you enter into a thaw period they need to make seasonal weight restrictions. We have an application where subsurface and pavement temperature data will feed into that. That's one of our tools. The other is a maintenance support tool. Basely what Roemer talked about. It would be applied to summertime conditions, nonwinter. How can we use data to help agencies do a better job of planning summertime activities such as paving and striping and mowing? That's that one. The other control is a multistate tool, doing a better job of sharing information across state lines about road closures, et cetera. And enhanced weather information for traveler information systems, such as 511. This would be using Clarus data to give weather specific warnings, route specific warnings as well. We're really excited about this project. It will be starting in October. It's a two year project. Real, real excited about that. That concludes my presentation. I will now hand to over to Brenda. She will walk you through the details. Brenda is a project manager with Mixon Hill. She assists transportation agencies . She received her bachelors from Devry University. With that I will hand it off. Thank you. To get to the system you would type in the URL. Everyone needs to reconnect to the new URL. When you type in the URL you will get this screen. The screen takes you to different places. If you click on a state it will take you to a map of the United States. Up in the right-hand side is the reports and subscriptions. I selected Iowa on here. You have lots of little markers that are in pink or red. That tells you there's an ESS station there and there's information behind the station. If you look to the middle of the screen you will see some gray markers, they tell you there's a station there but with no information. On the left you can see the system that is everything in UTC time. We've marked, or given you the information of what time it is in UTC, you don't have to convert it. Where your cursor is it will tell you the information for that location. Can you look at locations in metric and English. Once you click on one of the ESS stations it brings you up the most current information we have collected from that site. You will see the name of the station, the lat, long, the time stamp, what the observation type is, also what the value is. Everything on the right, where you have the green and red markers is the results of the quality checking algorithms. Green means that it passed. Red means it it not pass that particular test. Just because you see a red X does not mean that the value is bad. You have to analyze the information and determine whether or not you want to consider this as a good observation. I will give you an example. Especially in the climate range. It's set up based on a month at a time. And what the average high and lows are for that particular month. As many of you know, a lot of time it's in the summer you can have record highs or lows. The test may come back as not passed, but actually it was a record so it passed our climate range. You would consider that data good, and not just throw it away. Again just a moment ago I said that you could select [ Indiscernible ] of observation. If I select air temperature and show you where you can mark in units in metric or English to see what the air temperatures are across the ESS that you have in your viewing window. Now reports and subscriptions, the top right hand corner of the GUI. You can view metadata for all of the existing sites. The first one we'll do is get observations by the contributor. It will list the contributors that you have available in the system. Then can you double click, or click once on the ones you want to see. You can pick multiple ones. Here we've selected -- once you pick who your selected contributors are it will come up with the stations that belong to that particular one. Can you select all of the stations, or you can pick just one. Here we've selected one. There's a drop down that says that all observations, or you can select just one observation for that station. Then you have a choice to either run a report or build a subscription. Here we will run the report. You go through the process to this point to subscribe to build a subscription that will fill every 20 minutes, or to get information for a point in time. If you run the report the next thing it asks you to do is how much data do I want? Here we picked six hours, we will bring it back into a format. You have three potential formats,CSV, you have an XML, or CML for those in Canada. This is what your data will look like. Lines and lines of text. We picked all of the observations. The list goes much further. If you look to the right you can see the quality flags. If you throw it into an Excel spreadsheet you can look at all of the data in line with your headings. The next page is about the subscriptions. If we had built a subscription your subscription will show up right here. Every subscription is numbered. The one we will look at is on the right-hand side, two up. This is a subscription from -- if you look towards the bottom, it's one particular station, the contributor is British Columbia. They've asked for all of the observations coming from British Columbia. This particular site we only get the information once an hour. We fulfill this every 20 minutes, but there's only data in it -- this particular one has asked for the information in XML. What I have done is shown you what the XML looks like. If you throw the information into an Excel you see that it lines up nicely for you to look at all of the data all at one time. We have many, many states that started sending their metadata to get them connected. We encourage not only state D.O.T. s, but local transportation agencies, the freeways, anyone would like to contribute their information. We encourage you to do so. I'm happy to help you with your metadata. We have a lot of things coming online between now and the end of the year. We encourage you to look at the data that is coming from sites near your states. Thank you. Thanks. Okay. We have about 15 minutes or so left. We want to finish on time. I will let Roemer kick it off. As Ben mentioned earlier there are four elements of the program. I'm going to give you a quick update on the performance measurements and the training and outreach elements of our program. As Ben said earlier, on safety, we received about $4 million a year, or $5 million a year for four years for the program. It's our responsibility to make sure to evaluate our success in achieving the goals of SAFETEA-LU. That's why we have underway performance measures project for Road Weather Management. The objective of that task is to come up with some performance measures we can use to evaluate the success of our program in achieving the goals of section 5308 of SAFETEA-LU. We have contracted with Battelle to help us identify and come up with performance measures. We completed a lot of work in this area already. We conducted a literature review of the documents that are relevant to performance measurements. We viewed about 130 documents. We came up with more than a hundred measures, potential measures, to use. We presented the measures to a group of stakeholders last year in a workshop. We refined, we tried to get feedback from the stakeholders about the measures. We refined them. After that we send the measures forward to more than 300 individuals. They gave us their feedback on the measures. Now, after all of that we narrowed down the performance measures to 11 that correspond to the three program goals from earlier. I will not go through all 11. They consist of output and outcome measures. Our next step for this task is implementation. We're in the process of defining clearly what the measures mean, what the scope and the balance of the measures are. As well as, looking into the different sources of data to use. Also, we're going to look at the different procedures to use to analyze and quantify the measures. Finally, to be able to determine how we're going to use this for evaluation and monitoring as well as for communicating our success to the public. In terms of the training and outreach we have several products that are available to Road Weather Management professionals. The NIH course is still available. It is a one-day course. We have delivered the course three times already. Then just this year we developed a blended version of the NIH course. This was done by the university of Maryland. We piloted it in April with about 26 participants. The feedback was partnership. We are planning to deliver it again sometime this fall. We completed and assessment of the weather elements in NIH courses. Also last year the ITS rocky mountain in partnership with the ITS Joint Program Office developed a course. It's a one and a half day course. The course was piloted in Denver last year, also delivered at the NRITS meeting in Michigan . I'm sure many of you are familiar with the AASHTO computer-based tool. The course provides scenario based exercises for equipment operators, middle managers, et cetera. It coffers a lot of topics including winter road hazards. AASHTO continues to update the course. They've updated it to include the guidance from the recent NCHRP studies. Ray talked about the MDSS product demonstrations. I will not talk about that again. Ray is the contact person for those. We have available cross training. The goal for this cross training is to educate the communities about each other. We have a course that informs transportation agencies about the products and services. The course is available from the website as shown here. The other one is also web-based. The objective is to inform the weather forecasters about transportation operations. I'm sure many of you are familiar with the road weather resource identification tool. It's a tool for road weather publications. Version 2 has about 650 documents. We'll be adding 250 documents to that database. We will create links to those documents. That's it. Thanks, Roemer. Okay. , Pat. You only have five minutes or so. Pat will bring you up to speed with the efforts on VII. He's been in his position since January 2006. Pat will take it over from here. What I was going to say has gotten shorter and shorter. I'm going to keep this short. The way I look at it you all have access to the PowerPoint presentation. You also have access to our contact information. To really sum up VII, it is for vehicle infrastructure. As far as the concept and how it connects to road weather. They look at the possibility of numerous sets of data elements that could be glean the off of a vehicle. We're looking at the idea that you could take that sensor data and translate it into weather observations. To give you a quick example, if you look at radar, it will show what appears to be precipitation. If you have a way of contacting somebody on the ground you find out it's not hitting the ground. The idea that you could have vehicles driving through that area, you get data that tell you if you the wipers are on on our off, headlines are on or off. That data could be married with information coming off of a sensor station. It would help fill in gaps of information that are critical to being able to improve the state of the art of predicting what is happening on the surface, or on a road surface. I had 16 slides which I thought I would have eight minutes to talk to, it was going to be fast to talk to start. I will not even bother to address some of these. Now they're not even moving forward. I'm clicking and nothing is happening. My computer is not going as quick as what I'm clicking. I left pictures, I went up to the proof of concept in Detroit. You had vehicles with onboard equipment, OBs. They were driving on a test bed in Detroit. They were transmitting data off of the vehicle into equipment processing back to a transportation operations center that is set up here in Virginia. They were able to capture information and send messages back to the vehicles. I was up there in Detroit in the command center to see real vehicles transmitting messages back and forth. We were able to get the temperature information and whether the brakes were being applied. It was really neat. The thing with VII right now is this initiative is morphing. I believe it will be rebranded. If you need more information I recommend that you talk to Ben. Looking at it from a weather stand point we're not sure what to get out of the initiative at this point. We're starting to explore the possibility of getting data from long haul trucks. The reason we're interested in that is you are seeing statistics showing up now. There's a lot of trucks out there. Nearly 500,000 of them are equipped are sensors that could be transmitting data that we might be interested in. Here's a graphic showing you that there's a lot of out there, it's projected to grow into the foreseeable future. Some things that are attract be is they operate 24 hours a day. We would be getting information. VII is more focused on passenger vehicles. This would focus on information from trucks that would be driving 24/7. They would be driving in all kinds of weather conditions, they drive for longer distances. The task is going to be performing the work with ATRI. They will find out what kind of data is available, what kind of data elements are available, you know, provide a report at the end of the task on how truck-based data can be used. We have a contract in place now to receiving the data once ATRI is up and running. NCAR was capturing the messaging generated during that POC, they were tasked to develop a prototype weather transmitter. The contract with ATRI is in the final stages of being finalized. It will have a period of nine months. I apologize for going through so quickly. You have our contact information. Thank you. Thanks, Pat. Not sure whose dog that is, sounds like he's getting hungry. That concludes the content portion of our webinar. I think we have just a couple of minutes, maybe, to answer some of the questions. We've gotten some answered along the way, some have not. Jennifer, how do you want to do this? I'll try to direct it to the right person. I think we only have time for a couple. Maybe we could get back in writing some of these others. Sure. The last two didn't get answered. Do you have a timetable for the quality checking enhancements and refinements and new variables? I can answer that one. Yes. We just recently kicked, just signed two contracts. We're going to kick them off later this month or next. One is with our contractor Mixon Hill, to develop -- the two contracts, one is with Mixon Hill, the other is with NCAR. One is checking the algorithms for the Clarus system. We're going to improve those and also four or five new algorithms. Brenda, you with probably correct me on the timeframe. When do we anticipate the new formulas? I believe you are right. Some may be implemented as we go along. That's a phased approach. Probably about a year from now we'll start bringing new algorithms into the system, some of the easy ones. Six months after that we should complete the whole process. Does that sound right? Yeah, it does. That answers that question. Was there another one? When Clarus Initiative be capable of automated reports? I do not believe we have any plans for the Clarus Initiative system that own and operate, we being FHWA, to be able to give out customized alerts. As part of a regional demonstration, one of the use case scenarios, the fifth one, that is where we hope to have an application that will do some of that. Either through a 511 signup system, or some type of private ISP service. The regional demonstration is where we hope to achieve that. Does that sound right? That is correct. All right. Anything else? An MDSS question that didn't get answered yet -- Um -- right. I probably can't answer this. Is Dean still on the line? Do you know if -- Go ahead. Can air pavement temperatures be entered? It's a closed system. The prototype might be able to do such a thing. That might be a question for Bill. They dropped off. I think the federal prototype can do that. The more input you put in the better outcome you get. Okay. Anything else on there? One more question just came in. How difficult is to set up so that it's usable? We're using DTN for our forecasting service. Anybody have input into this? Ben? Yes? I believe it was part of NCAR's new task order to give them technology transfer support. Yeah. I'm familiar with that. I think my understanding is that has been a little bit cumbersome in the past without any assistance. We're working on a task order to provide a little more support and hand holding to go through this process. I'm not sure of the timing on that. Some of these questions that I can't answer we'll have to take a note, we'll get you better answers in writing. Paul who is the FHWA team lead on Road Weather Management I'm sure would know the answers, he's out of the office this week. We'll be able if get back to you on these. I think we're out of time now. I want to thank everybody for joining us, and listening in. Hopefully this has been a good use of your time. We've enjoyed giving you this webinar. I encourage you to go to the website. In the next day or so the webinar and information will all be posted there. The site has a number of great other resources on it, a newsletter, discussion forum. I encourage you to look at it. For the questions, we'll make sure to get the answers to. Thank you everybody. Thank you. Thank you. (end)