Welcome to the docking operations seminar on Integrated Corridor management. My name is Eric and I will be your coordinator for today. At this time all participants are and a listen only mode. You may submit questions throughout the presentation at any time by using the question and answer tab at the lower corner of your window. If you require assistance, please press *0 and a quarter will be happy to assist you. Should you experience difficulty please contact Webex technical support at 866-229-3239. This conference is being recorded. I will now turn to the presentation over to our host. Good day and welcome to the talking operations Web Conference on integrated corridor management. I will be giving a brief introduction before turning this session over to Bill Anderson home we are very pleased to have as our moderator port today's seminar. Please be advised to this seminar is being recorded. I would like to now go over a few details. The seminar will last approximately 90 minutes with 60 minutes allocated for the presenters and the final 30 minutes for question and answer. During the presentation if you think of a question you can type it into the small text box underneath the tech area on the lower right hand side of your screen. Indicate who your question is directed towards unless your question is intended for all presenters. Please ensure you are tapping into the pen text box and not the large area and that you send your question to all participants rather than just the host or speaker. Presenters will be unable to answer your questions during their presentation, but Bill Anderson will use some of the questions type into the chat box for the question and answer session at the end. If you would like to zoom in on the slide being shown you can click on the some icon on the bottom left of your screen that looks like a magnifying glass with a plus sign. Finally this session is being recorded. A file containing audio and visual portions of this bob sled will be posted to our web site within the next week. Apple type that address into the text box for the period during -- due to the size of the file it cannot be said to your computer. We correct others in your office who might not have been able to attend this conference to access the recording. The presentations used during this reporting will also be available within the next week on the site. Attendees will be notified of the availability of the power point, according, and closed captioning of the seminar. At this time I would like to introduce Bill Anderson, the moderator of today's webcast. He served as technical lead in operation, development, maintenance and assessment for rural and regional ITS systems. Now I will turn things over to build who will introduce our first speaker. Hello, everybody. Thank you for participating in today's talking operations on Integrated Corridor management. People go through three particular presentations starting off with Jennifer Harding, and he will be introducing the topic today going over the concepts and actually the recent activity today. After that we will follow up with a briefing on the Pioneer sites from Brian, during -- sorry, from Brian Cronin. Then we will be going into a presentation for on the generic corridors and at the conference of operations. Our first speaker is John Harding, technical manager for the initiative out of Office of Operations or federal highways. Thanks. What I will do over in this part of they webcast is basically an introduction to Integrated Corridor management. We basically are communicating as a concept as we worked on it with stakeholders' so far. In the activities we have completed so far and are going to now also undertake. As we go to the next slide -- before I start talking about Integrated Corridor management let me talk about what led us to this concept. Many of you know and have experienced this, systems are made up of independent networks. And all the demand and capacity on each of these networks is independently operated and to one extent or another they up opposite to improve their performance. Each of these networks has also invested in the ITS to approved. We have all these different management systems. Now, when we look at these networks and we look at them when we configure them at Disney to each other when they form a corridor, that is when we can see there is different opportunities that we have. These corridors can serve the same trips different ways. Taking these opportunities and using ITS methodology is we can increase the effectiveness of the corridor by managing the total capacity. It gives you an idea of where we are going when we see we have so much done already. How can we better and more effectively use or corridors? This schematic reinforces what I was saying, the adjacent facilities. You can see here for a way, rail, bus, arterial. The goal is to take advantage of this configuration and provide travelers with information that allows them to make choices real time during the day. They have trusses on what to take depending upon the networks and their corridor, and this is complemented with integrated operations. The operator can -- whenever information is giving out to get people to ship to another network, that network is also ready to accommodate that demand. What we are doing is calling accurate mode independent performance information. We are cobbling the accurate mode confirmation and integrated operations so that we can find, identify, and use the on used or spare capacity and in the corridor. All this helps us move from that -- when I was talking about that network perspective, even travelers just looking at, hey, I use the for way all the time to more of a corridor perspective where you have options and you can use the whole corridor to your event to take trips. This gets us to, what is or does in here? What does this entail? And we see that each of the different networks in a corridor have assets and these are assets, personal assets, a physical assets. If we can use them together we can gain performance in especially where there is significant to -- congestion already. My approach to this is three areas of integrated core management, operational, technical, and [indiscernible]. This is kind of a concept of pictures and how you go in putting and up and strategies. The challenge here -- let me get to this, is to operate institutionally. Let me talk more about that. Operational integration, here is a way to do this as the petition of ball to agency transportation strategies. One of the examples we use is that if you have an adjacent signal and a red meter you can have those communicate and make sure they are coordinated with how they service the traffic and on of the freeway and through the intersection. That is just one example. You can combine different strategies like that among the networks to improve the capacity and demand of your corporate next is technical integration which provides the means for system interfaces and standards. It integrates all the information and system operation control so that you can -- so the operators have the function of control and you have the information among the networks of the travelers can make their choices during the day before or after their trip or whenever. The last area is an immigration. This brings a lot of this together where you are looking at how you distribute the specific operational responsibilities ensuring control. How do you kind of compliment what you are going institutionally and systemwide? The basics of this concept, now we have a program. How do we get there? They're is a high level to about we are trying to do the high level representation of what we are doing. The goal is to provide operational methods and institutional data, and what we want to do is compliment that without demonstrating that this can be done, showing there is performance benefits to be gained. We ought not just going to throw things out at you. Here is the tenants, go do it. We will complement it by saying, we can't demonstrate this. There are benefits that you can basically experience. If you implement ICM in corridors. That is the high level. We have this this diagram. Let me put this in perspective a little bit. You can go over and see on the top fiscal year 06 and 07. We are almost at the break of the fiscal year, and that is where we are in the program. We started way back you can see in fiscal years 04 it was a Phase I. In case one of the program we worked with British stakeholders to develop and establish a common understanding of what this case seven concept was and is. We worked on various aspects of it and I will talk more about the different aspects of that when I go to the next slide after this, but not yet. What we developed in that phase. Right now as you can see from that what we are transitioning into Phase II and three. Phase Two, we are just beginning this and it focuses on developing and announcing methodologies and technical integration to support the ICM implementation. Phase III, we selected a pioneer sides to apply concepts and a subset of that to demonstrate the concept. Ryan will talk more to that later after I am done. Phase IV, we are looking at the transfer. We have a lot of things coming out of Phase II and three, and we want to package that and a line that with various types and needs so that practitioners can basically a search for what is basically applicable to what they need in their corridor. We are working on that and trying to match the information with your need and what is available. Base five, ITS standard, it is not listed because it is not a phase in our program, but it is like that 12th man in a football game that stance. We are coordinating with the standard team and ITS and operations and looking at Standard readiness. What standards will support ICM? Can they support ICM at now or what is needed to further support ICM? How do we expand? It gives you an overview of the various phases we will go through. As we go through, what activities we will go through in the future. Now, to give you a little more detail, Phase I is by additional research. We worked with various stakeholders to establish and develop the concept. We did that by breaking down ICM into various aspects. What we have here, as you can see, is a series of a, what we call, technical memorandum. It is what we did to document or research what we have done so far. On the left you can see what we have posted on the Web site on the bottom of the screen there. You can go to that and find those documents already. On the right is the ones that are pending. We are working on those to get them up and posted. A couple highlights, one of the documents which we will be going over and a lot more to tell letter is the ICM concept of persons for generic corridor. This is high level concept operations for generic corridor we felt -- and fabricated. It provides a example of a ICM con ops that others can use, practitioners, as a basis for developing they're own common ops and some corridor they have in their area. ICM implementation Guide, this is kind of a higher level document that walking through the system engineering process highlights various aspects of ICM at what they mean at various steps in that system engineering process and also brings together a lot of the documents you see in the slide in various areas where you might want to access or reference those documents when you are going through the system engineering process. The last one I want to highlight is the document develop alternative definitions for corridor and integrated management. This document basically just documents what we just went through and comes up with these definitions working with stakeholders. What I will do is put these definitions up on the screen. We went through a long series of meetings and after a couple begins we thought we were done. But every time we put it up it changes a bit. We finally got to want consensus on this, and then it was documented. I want to read the whole thing. A court definition entails a linear geographic band. You are thinking of something along along some kind of area. It is defined by existing patterns and markets where you see people coming from and going to. It is kind of basic generators and attractors and because you have the different networks they can service the same trips a little differently, but there are alternatives to get from point A to Point B through that corridor. That gives you a sense of what we mean by corridor in this program. Now integrated core management definition, but just see how many we have a pretty long definition. You can see at the bottom and this will area, we wanted to make sure we work very well communicating what this was. So we listed a lot of activities so you could roughens those to get a better sense of what we mean by Integrated Corridor management. Integrated Corridor management is the integration of operations among the networks in a corridor to expect the use the whole capacity to improve mobility. And that is the shorthand I use, but there is the real definition that you can read and the activities that go on with Integrated Corridor management. That is based want to give you a taste. I busily invite you to log onto that Web site at the bottom of the screen. Look at some of the other documents that are there. We will be posted more in the near future. What are some of the new stuff we are starting to do is, we have faced to. We have two areas of face to, the first phase we have is what we call the analysis simulation. What we found through research in this one is that we have various analysis tools that help us evaluate different aspects and performance of all the different networks and a corridor, but hovered none of these pools really tell us or analyze how these networks interact in a corridor to be there. So through this activity billable find out a couple things. First we will need to identify what kind of data that we need for this analysis and modeling and then incorporate what that -- it is not just that kind of data and information we need, but that will help us determine what we need for ICM operations and evaluation and performance. Next we want to develop methodologies that will be able to help us test, select, identify different strategies that are effective for different corridors. One thing about this is that we can look at current analysis capabilities and our preliminary investigations show us that what we need to do is look at all the different areas of modeling analysis and transportation to really get a good handle on what we can get from ICM. We will take these methodologies that we develop for testing and analysis and test it basically in a test corridor and also apply it to actual corridors for Pioneer sides and the Rhine will talk more about that. In the future when we get to demonstrations we will not just to evaluate the demonstrations, we will also complement that evaluation activity but did we need to also determine how these tools are doing. We will basically modeled the demonstration site with these tools and look at reality and what the predicted model says and see how well our tools did or did not and see what we can do if we need to improve those tools. Hear what we want up with, as I said before, methodologies the practitioners can use it to test and validate effective ICM strategies for their corridors. The second part of Phase II is technical integration and we sat down with a panel of a transportation system experts and they basically told us to focus on these four different main areas. First, did find schemes and strategies 37 for protection. We have the best protection for the various networks. However, 47 you need more information on four specific troubled times on comparable segments. You have to have information so you can have trouble time for each one of those of the traveler can compare and determine what network they want to take. Also the network gentians, what is going on when we asked people to shift and how much shift are we seeing between, say, a freeway and a rail terminal. That will give us the permission to better figure out what we need to do up personally. Next when you have this coming together, how will you make decisions? From the transportation experts we talked to, they want support, but they also said that every application -- and this will be able to element in every corridor. From our perspective we can take what we will do is develop some requirements and architecture so they have the basics to then move from there and apply to their own situations and develop what they need for their corporate corridor. One aspect then -- there was kind of a split and the experts were we asked them about the vice to devise communication and control and will or won't it support ICM. There was a split on whether it would be useful or not. So what people do is adjust the usability of that. Where can it be used or where it might not be used or is it feasible at all? The last thing that is somewhat overlooked is that linkage between the institutional procedures and protocols and the system capabilities. I said this before. We are looking at this distortion of response abilities and control, and that is kind of getting into the institutional structure, but you also have to pay attention to your system capabilities. Are you doing something institutionally that can be supported by the system and vice versa can they complement each other? You have that nice link up the system and everything works together. That covers phase to and basically the major parts of some of the activities in the face one and Phase two. Now we will go on to the other Phase III which Ryan will talk about and later we will talk a lot some of the things I said about the more detailed concept of operation. Yes, and remember if you have any questions you can type them into that chat area there and we will address those at the last 30 minutes of the presentation of the seminar. Thank you, John. Our second speaker is Brian Cronin who is from the ITS joint office. He will be presenting on the Pioneer demonstration site. Thank you, bill. Thank you, everyone for turning as today. What I would like to do today is briefly remind everyone on the Pioneer side process and then get right to the chase on who our pioneer sites will be. A quick summary of some of their attributes and where we are going with the said demonstration phase of this program. In general and may be released up to eight sites to assess their ability to partner with us to develop and implement integrated core management. We had some basic model criteria that it must be a public sector agency and that we must include both freeway, material, and transit networks and the proposal in an urban area and finally that there should be real time or near real-time data collection available from all the works. We have evaluated the applications based on qualifications on what the corridor was, what the institutional technical and operational capabilities were for these different corridors and the partners within them and finally the technical approach. So besides that were selected arc cores represented in Seattle, Oakland, San Diego, Minneapolis, Dallas, San Antonio, Houston, and Montgomery County. First the Dulles corridor is done at US-75 with running north east out of the downtown Dallas area. Dallas area rapid Transit Authority is the lead with partners from the Texas Department of Transportation and the Texas Poll what authority and several cities within the Dallas area. Some highlights of the corridor were some of the good of real-time data availability and available transit capacity and the light rail system that parallels the highway corridor and arterial networks. The corridor includes both HOV, toll lane. The next is the U.S. tend however led by the Houston Transit Authority, Harris County, and the Houston and Galveston area of government. They're is a good mix of networks and corridors and this with tremendous existing partnerships an interagency cooperation between Houston Metro and TXDOT. It includes many applications along this corridor. The next corridor is in Minneapolis, the I8394 corridor coming out of downtown Minneapolis heading west. Minnesota Department of Transportation, Henderson County, and Metro transit and Minnesota are the project partners