Good afternoon. At this time all participants are in listen-only. If you would like to ask a question at the question and answer period, you can press star 1 to ask a question. I turn it over to Jocelyn Bauer. Welcome to the May version of the Talking Operations Webinar, hosted by the National Transportation Operations Coalition, NTOC. The title of today's Webinar is Regional Traffic Signal Operations Programs – Planning and Funding. I’ll be giving be giving a brief introduction to the web-conferencing environment prior to turning the session over to Darren Buck from the Federal Highway Administration who will serve as the moderator for today's seminar. Today's seminar will last approximately an hour allocated for the presenters and a half hour for audience questions and answers. Please be advised that this webinar is being recorded. During the presentation, if you think of a question, you can type it into the smaller text box in the chat area on the left side of your screen. Send your question to everyone rather than just the presenters. The presenters will be unable to answer questions during the presentation, but Darryl will use the questions for the last 30 minutes of the seminar. A file containing the audio and video portion of the seminar will be on the website. Attendees will be notified of the availability of the seminar. We encourage you to direct others not able to attend the seminar to access that seminar online. The presentations are available in the download screen, click on the name of the file you would like to download and the button at the bottom of the download box that says save to my computer. Darren Buck, our presenter for today, overseeing outreach activities of the national transportation Coalition -- Darren worked in similar roles in the [indiscernible] community and small federal program creating jobs for people with disabilities. Received MA from University of Maryland in College Park and is currently [indiscernible] durn things over to Darren to start us off. Thank you very much. This month's edition will explore and regional traffic systems. We have a great line of speakers from the federal highway office of planning, who will provide an overview of how the planning process can be engaged to identify common objectives to sustain resources needed for effective regional traffic operations programs. We will have examples of how this process has been implemented successfully from some of our key stakeholders from the Portland, Oregon, and Fargo, North Dakota areas. First speaker is Laurie Law, transportation planner, been with federal highways over 25 years, involved in transportation planning, the last three transportation authorizations. Her expertise includes administration of metropolitan and state-wide transportation planning, transportation safety planning and federal aid grant management. From the Portland Oregon area, Dina Plattman, coordinates development, implementation and planning. Served as Metro's regional freight planner, Portland freight master man, and numerous corridor studies, received masters in regional planning from political science from UCLA. Finally, Mr. Wade Cline, executive director of the Fargo Moorehead metro -- the capacity, works with implementation of the 2008 Fargo-Moore head metro be -- implementation of the 2008 FHWA workshop in Fargo, resulted in the assessment of the Fargo-Moorehead -- adoption of traffic operations action plan in 2009, and in eight-year tenure involves in all facets of the planning program in the area. Graduate of St. Cloud state university in Minnesota, degree in local and urban affairs. I will pass it to my colleague Mr. Eddie Curtis. Thanks, Darren. I wanted to say thank you to the participants on the line and extend a thank you to the folks that helped put this Webinar together in addition to the speakers who graciously agreed to join us today. First two, regional transition system management and TRB signal system committee, and FHWA office of operations collaboratively worked to put this Webinar together. This is the first of a series we will present on the topic. I wanted to quickly give you an overview of what regional traffic signal programs are all about. A fair amount of resources have been invested into evaluating the state of the practice for traffic signal operations. There have been two traffic signal report cards, and a very telling report by the government accountability office in 1994. Each report really points to institutional issues as the primary barrier keeping us from improving and sustaining improvements in traffic signal operations. The Federal Highway Administration resource center, in response to requests from agencies after the traffic signal report card in 2005 and 2007 put in requests for technical assistance. How do we improve signal operations? These started as reviews, peer exchanges with individual agencies, a process where we go in, conduct surveys, field studies to, get an idea of what's going on in an agency, region, and a report comes out with a list of recommendations. We found as we conducted these reviews the list of observation and recommendations tended to be very similar as we went from region to region. I have highlighted some of the key observations and you can see regional consistency and signal management and operations was high on the list. Looking at number 3, consistently saw complaints, as opposed to outcome measures looking at how the system operated. A big one we saw leads to why we are having this Webinar today, most regions were not capitalizing on all the available funding source. We will look at each of these issues and today specifically funding and planning issues. There's a document available now, download it, the regional traffic operations program, an overview, an amalgamation of planning operations, regional concept of traffic operations, signal reviews we have done, operation green light, looking at some of the more prominent regional will signal systems in the nation. We saw a variety of activities that these regional systems are engaged in. This report is a synopsis of all the information. It's a good look into what regional signal programs can accomplish. This approach is based on what I will call an objectives and performance measures driven approach. Something identified in the planning for operations program within the office of operations. And ultimately, this approach will produce sustainable improvements in funding sources for traffic signal operations. I will quickly put up a link to where you can find these documents, my contact information. If that's something that piqued your interest, I am the point of contact, we will try to organize a review if you are region. I will turn it back over to Darren. Thank you. Darren: I am sorry, I just gave a wonderful introduction with my mute button on. I will turn it over to the office of planning and miss Laurie Lao. I am in San Francisco, still morning for me. I will talk a little about funding and planning, transportation planning process. Although it sounds like a simple subjects it's very complicated and convoluted. Every time I talk to a traffic engineer I get frustrated, I don't think they understand what I am talking about and I don't understand what they are talking about. It's a two-way street. Traffic engineers ask me: How do I get projects implemented? Part of my presentation will be, as we talk about it, developed. These are interesting questions because not only do I hear this from traffic engineers, but these are the rules of how the federal aid program works. A lot of the questions, always asked about, why is planning process that important? Where do I get information about it? Why do I care? When do I need to get involved and who is responsible for these things? As I parse it out, it is about funding, the eligibility, the process, the whys and the where, who is required to do this, and the federal aid and transportation process, if you are not familiar with them, it is going to be the road block in how you get your projects into the system. Scheduling is also the when of scheduling is really important. The MPOs in the state have processes that are on a certain schedule, and if you miss certain schedules you have to wait for it to come back around or use amendment processes that take a lot more effort. This is my favorite, gatekeepers, that's us, planners, always accused of speaking our own language, having our own little clique, but there are roles and responsibilities. One thing is that if we all understand what the roles and responsibilities are it makes the process go that much faster. Once you understand the ins and outs of the planning process and federal aid process you will be better are able to navigate your projects, and getting them advanced. These are my symbols of what we are talking about on the bottom here. Let's talk about funding up front. In aid there are pots of money, and eligible to fund traffic signal operations. I will talk a little about them. Seedy Mac, I am sure you are familiar W the congestion mitigation air quality fund. This pot of money is to alleviate congestion and air quality issues. If your region is a non-attainment or maintenance area, you will most likely have these funds, but every state will have some of these, but a very limited amount in that it is intentionally for those non-attainment and maintenance area. For projects to improve transportation system management and operation that mitigate congestion and air quality, these are usually 80% federal and 20 match. There's also the highway bridge program, used to be the HBRR program. These are for projects to rehabilitate rehab rehabilitate or replace bridges. They are eligible if the TOC is to take care of bridges, that is also 80-20 program. A new or revised program under SAFETEA-LU is the highway safety improvement program. This is a -- even though it's safety, it is funds to be used on projects on any public road or publicly owned bicycle pathway or trail. Really, a good match; if you have operation or strategic highway safety plan, this is also where you could access lots of safety funds for the operations side. This fund is a 90-20, in some cases, rural high-risk road, 100% funding. The next group is the IM, interstate maintenance. Any projects on the interstate system is eligible, also 90-20. The other group is NHS, really for anything on the national highway system, a higher category of roads, usually the principle arterial systems, and it is a very flexible, in that 50% of the funds can be flexed on the STP group. I will talk a little about that. This pot, really for anything NHS, ramp, data collection, all eligible. I add on here, you may not know much about the SPR, the state planning and research program part 2, a research program. Certain features, equipment, elements that are experimental can be funded with this, however, usually the state, because this funding group is controlled by the state, requires that there's a research report or evaluation that has to be done. This is also an 80-20 program. The last I want to talk about is surface transportation program, probably the most flexible of all the category of funds, can be used anywhere in the state. One thing I did notice, under SAFETEA-LU, elements added was project related to intersections that have disproportionately high accident rates or high congestion and located on federal aid highways, eligible for funding. This is going very well with traffic signal management projects. This fund is 80/20 and a good bulk of the federal aid program is in the STP area. Let's talk about why. What is the transportation planning and programming process? This is what I have on the slide, really the basis of the applying process. With the process required, in place since 1960. A three C process, comprehensive, looks at the whole transportation surface system, intermodal system, also looks at land use, interconnectives between certain programs, and is cooperative. So, it means that we work with the local agencies, member agencies, citizens and cooperate together and share information, but it is also a continuing process so that when we develop a plan as a result of a process it doesn't sit on the shelf. We are constantly updating it, and the process continues on. Once you do it, it's done. Let's talk a little about regional vision and goal. Usually, within the planning process we expect the MPOs to have a vision goal and there are planning factors that are in legislation, eight of them. One is on operation and mitigating congestion, so if nothing else I would anticipate most, if not all, MPOs have very similar goals, but if you notice, there are certain -- three arrows on the side here. This is where the traffic engineers and [indiscernible] pay most attention to in the planning process employ . Once you have the goals you start looking at the operations available and start designing the needs of the system and strategies in which to address the needs. That's when we start talking about the improvement strategies. Once those are identified, then we evaluate and prioritize these strategies so there is correlation -- not the sequential, but definitely a lot of these elements are going on together. Once we have developed, evaluated, prioritized to develop which strategies, projects are going to be funded in the future, we kind of package this up into a long-range plan. The long-range plan is a 20-year plan. This is when I would think the traffic engineers, management folks need to pay attention. Are your projects in the long-range plan? Why does it need to be in the long-range plan? Who do I need to talk to about these issues? From the long-range plan we get the dip and tip, the funding document, list of projects funded in the near future, usually the next three to four years. From there we get to project development, operation and monitoring system data and go back to the beginning one more time. It's the continuous loop. There are certain planning products. I don't expect everybody to remember all these things, but these are the most important ones. The first three, the UPWP, the unified planning work program, and the metropolitan transportation plan, and the TIPSs, for metropolitan planning organization. The last two are for the state, rural areas. What I want to talk a little about the [indiscernible] concerns on how the planning funds will be used, the MTP is a 20-year document, the TIP is four-year investment project on the state side. A long range plan also. That plan is [indiscernible] nor does that have projects in it, and the [indiscernible] is the final overall document programming for the state. So the tip includes all the metropolitan tips. What should you care about? These points, when you develop projects, be very clear about your purpose and need, how well they fit regional goals, the vision and goal. Build them into the corridor studies the MPO is doing, make sure it's consistent and doing performance-based planning, make sure the data and performance measures you have for traffic operations are built into the planning process and you identify them, share with the transportation planner. If it serves one purpose, then those projects have a better chance of competing. This is the real key, you have a firm reasonable cost estimate, we are seeing a lot of projects deferred because they don't have a good cost estimate and once we find out the real cost of the project a lot have to be deferred. 50,000 population TMA -- anything 200,000, we split them, because TMAs have control over STP attributal funds they get, and could award those to projects, have a little more authority than the regular MPO. The MPO relies on the state to give the budget. The attainment, non-attainment we talked about, C Mac allocation and those in the rural area, there may be state that's require you to do planning because of the regional transportation planning agencies. These are considered RTPOs, you might be doing similar things, but those are state, and not federal requirements. How long does a programming process take? This is the Oregon one, it's a three-year process, even most states update the stip or tip annually it's a four-year cycle, four years of projects, you can tell this would be in 2008, when O DOT would be deciding to budget, priorities, getting comments, where to put the money, and approving the revenue forecast and money in the program. This is year one; a 2010 document, they started in 2008, occurred in 2009, and identifying projects doing prioritization, going out to public review. 2010 they go to public review, consolidating much of this with the metropolitan TIPS. Approval comes in 2010, 2011, you will have to start early. I will highlight the key points here you may consider to get involved. The gatekeeper, these are questions Eddie asked, what kind of relationship do we have, common objectives, to communicate and coordinate with your transportation planner are. That's the most important element. If you could communicate, coordinate know who they are, half the problem is solved. I am going to sum up here, get to know who your MPOs and state planners are, where they are located, what they are doing. What is their planning and programming cycles? Where are they at right now? If there's an application process, what is it, how do you get involved, what are the project selection criteria. Timing is everything. If it doesn't work out, you need the project right now, you have funding, then there's also the possibility of amending it, but it's a somewhat arduous process. In final, resources, if you don't know who they are, I would say these are the people to contact if you are local MPO, state planning, programming section or FHWA division. Just for your information I added a slide with the fact sheet on what the funding groups are if you want additional information, and also, a website for the office of planning located here. With that, I will turn this back over to Darren. Thank you very much, Laurie. Two quick administrative notes, be if you have more than one person sitting at a work station viewing this Webinar we would really appreciate it if you would put in the chat box the number of viewers you have besides yourself. A quick reminder, we will take questions when we are through with the presentations. Feel free to write questions in the chat pod and we will pick them up, answer as many as we can after the presentations are complete. With that, I introduce Dina Plattman, with Portland, Oregon's TPMO. I am looking at the clock, it's darn near 10:30. Laurie did a great job of setting me up to be able to share Portland's experience with planning and funding our regional traffic signal operations. I am going to talk to you about our regional coordination framework, key achievements, and plans for the future as it relates to improving signal operations. Quick introduction to the Portland, Oregon region. Our metropolitan area comprises three counties, 25 cities, we have a strong bi-state with neighbors to the North, Vancouver, Washington, considered part of our larger region although they have their own MPO. What's important to know about us, we're a growing region, expecting to add over a million residents over the next 20 years. With that, growth we anticipate the usual challenges, increased demand on services, more congestion on road ways. Portland is well-known for its work over the last decades to [indiscernible] using transportation planning to grow compactly and sustainably. Our regional culture is one of cooperation on issues big and small. Our approach to the management of our transportation systems really reflects that norm of cooperation. You will see as I weave the story of the Portland region and our work on system management. The management of our regional traffic signal system is spread across many operating agencies. We don't have a regional traffic system controlled by a single entity, but we have an effective regional strategy for system management and the signal system. I have to say this is due to the tremendous level of coordination we have between our traffic operation staff across the region and the transition into the planners. The glue is really the group transport, regional advisory committee on operations. This slide show ons the collection of agencies actively participating in the group. Transport first emerged in 1993. ODOT, our state transportation agency was developing a regional management system, a plan for the region, and they formed an advisory committee. What the operations staff found was that these regularly scheduled meetings were really valuable opportunity to coordinate across agency issues and they just kept meeting, for the last two decades. In 2004, metro, the agency I represent formalized transport as the region's operations committee and the [indiscernible] JPAC. I want to talk a little about where we've been regarding advancing our traffic signal management. Over the last decade we have been slowly creating a fiber optic network as a commune communication background for the intelligent transportation network. To coordinate traffic management, travel and incident management, all activities identified in that regional ATMF plan created in the mid90s. In 1997 the cooperative telecommunication committee, CTECs, was established as a managing body for fiber sharing. The founding members, regional transit agency, decided pooling resources maximized efficiency and was in the best interest of the public. Since 1997 we had other agencies join and contribute their fiber on to the nets work. CTEC is focused on the collective well-being of the communications system, each agency sharing responsibility. These arrangements are in place, shared arrangements, used to define roles, responsibilities for the network. It's important to note no funding exchanged hands, all the agencies contributed their portion to the network without worry about who is getting more and regarding the funding. The graphic on the side shows the architecture of the network. We are still working to complete the network. There's still gaps. Right now we are focusing on connecting Vancouver, Washington agencies into the ITS network. Another significant transportation initiative is centralized traffic signal systems for the region. In 1988 the city of Portland put in place a centralized system within their jurisdiction. An update in early 2000 was an opportunity for transport to expand the system to include all signals in the region. The goal was to have better overall management and maintenance of the signal system and be able to manage progression across agencies. So transport committee got together, worked on the specifications, developed the requirements they wanted for the region, and the city of Portland took lead on securing a software license that allows partner agencies to participate in using the software package, using transsuite software, I am sure some of you will recognize that. The city of Portland maintains a central server, [indiscernible] responsible for remote servers within their agencies and agencies are connected into the ITS fiber optic or communications network I just spoke about. The transport established uniform standards for traffic controllers and servers and I understand the communication equipment, there's a little more flexibility on that one. An example of the way the transport has come together to pool resources for the common good. There was no exchange of funding, but rather a commitment to shoulder their piece of the system. In the future, transport is looking to realize traffic management operations center to center-shared control. Right now we don't have a centralized traffic management operations center in the region. Operating agencies have developed their own TMLCs. The goal is to link those toy create a virtual centralized TMLC. I will touch a little on planning by operations folks. Since the first ATMS plan ODOT led, continued, early 2000s local transportation agencies and [indiscernible] developed ITMS plans, many efforts supported by NTIP funding, metropolitan funds. Collaborated on creating and updating our region ALI TS architecture document. Now I am going to shift over, talk about where we are right now. Transport's efforts, past efforts and today, have really shaped regional transportation planning. This is where we come into talking about, providing example of what Laurie was talking about and talking with planners to integrate operations. By the mid2000s, transport was a very well-established committee, leveraging operation funds to advance their regional initiatives. The group's leaders recognized the need to better integrate into regional transportation planning, developing our long-range plan, as well as MTIP to be able to secure funding to advance initiatives more quickly. We found operations-focused projects did not compete well for funding against traditional, roads, sidewalks, infrastructure. In the same time frame the Portland region was selected for an FHWA regional coordination demonstration. We were charged with creating region concept of -- this turned out to have really transformative benefits. There was a I strong education, outreach component, to share what the region had been doing around operation and explain the benefits of it. The ARTO redefined the approach, we were beginning an update, 2035 update of the plan, and the timing was perfect to integrate. There is a core emphasis on system management. We will see final adoption this year of the RTP. Lastly, it led to the creation of an MPO program called the regional mobility program, which has dedicated to integrating operations into our planning. I am currently leading that group. So the regional mobility program has taken over the management of Transport, and its subcommittees. We are managing our congestion management process and providing leadership on management initiatives. First activity was development of regional -- 10-year investment strategy integrated into 2035 RTP. Where are we today? I said the plan was completed last fall and accepted by our MPO board, metro council in December 2009. I included a link to the plan at the end of this presentation, builds on the previous work done by transport and developing ITS plans for the region. We were able to bring in a transportation demand management component, build what they had a five-year plan to a 10-year strategy. This shows the four investment areas in the plan, multimodal traffic management, travel information and TDMs. Under each investment area we identified region-wide, corridor-specific investments. With regard specifically to regional traffic system, the plan is supporting completing and maintaining our ITS network and signal system deployment. We are aggressively deploying update of equipment to support the next generation of traffic management tools like adaptive signal systems. We currently have one adaptive corridor in place, in the process of designing several more. We are looking to expand transit signal priority corridors across the region. We are advancing our integrate corridor management program. Right now we have a single corridor outfitted as ICM corridor. We identified several more we are going to advance over the next several years. We have been actively installing pedestrian count down -- really popular with our citizens. And we are installing bike signals at key trail crossings. Another thing, when we talk about, particularly performance measurement, we are experimenting with data collection techniques, we have quite a bit of data on the freeway system, but arterials, most places we are challenged with being able to get good operations data. We are interested in having this data to support operation and travel information, and established close relationship with the university transportation center at Portland State university, they have ITS lab portal -- researchers to store, share data. With regard to funding, art owe was helpful to be able to -- regional N tip funds to operations. In previous funding cycles, projects didn't compete well against recognizable projects. Our MPO board's increased awareness of lower cost operations solutions and transport's quiet success led them to carve out about $6 million in MTIP funds. Transport was charged with identifying projects. We established a list of projects to be funded under the $6 million, taking the list to our council, board, this May, using the plan set us up for future program allocations. We are in the process of starting our next regional flexible fund allocation and looking for the years 2014 to 2015 and are fully expecting to have another programmatic allocation to support operations. People have been very pleased so far. During the development of the plan we had two other funding opportunities that allowed us to jump-start implementation. One was ODOT offered an $8 million grant for innovation -- working through Trandz Transport, able to secure half of that funding, active traffic management funding, variable speed sign in the location. Other funding opportunity that arose during this time was our federal stimulus dollars, able to respond very quickly to the opportunity, with a project on signal timing on 10% of signal system across the region. Right now, with our plan in hand we are looking ahead to the opportunities arising from the federal transportation bill coming up. Grove to wrap up, I would say the Portland region is in a great space for advancing traffic signal management. We created a supportive political environment, focused policy in place, and have the clear investment strategy. The one challenge we are facing right now, transport's been active about two decade and a lot of the folks that are leaders in the group are reaching retirement age. It's really grooming a fresh staff of operations staff to assume leadership. This slide includes the link to the plan, and my contact information, and I thank you very much. Thank you, Dina. We are very lucky to have you here. We will move to the final presenter, Mr. Wade Cline, from Fargo Moorehead Council of Governments. I appreciate the opportunity to be part of the Webinar. The first slide gives a sense of existing continue in the area. We are a bi-state MPO. Where we're at is really a process deeply rooted in the ITS system. We have an IST plan A don'ted in 2008 and architecture in 2007 for the metropolitan area. Our operations plan, strategies we developed locally simply build off of both the plan and architecture with the premise being interoperability and regional model. As a by-state metropolitan area, the public doesn't much care whose road they are on or whose signal they go through, they just want them coordinated so traffic moves as efficiently as possible. The other focus is to make sure as we deploy things, they are coordinate the deployments. Our mentality shifted, we started thinking about ITS's, less about stuff and what we wanted to accomplish with the stuff. We overall had a reinvigoration in the late 90s, adopted an ITS plan, then it went away, single community, single DOT efforts. Now we are entering an era of multi-state and jurisdictional interest. We were fortunate to have federal highways here in December of 2008, did an assessment, produced a report. That was a very important point in our evolution here in this metropolitan area in terms of starting to see the bigger picture where traffic operations were concerned and our existing condition is based on enthusiasm from the stakeholders, two state DOTs and other city signal operators, everybody generally has a good relationship and they all want to do something. They sat in enough meetings, looked at enough charts and are ready to start deploying a coordinated system that operates, improves operations in the area, and we are fortunate our policy board, MPO, locked on to these things and set as a priority that we begin to look at implementing a more coordinated operations program. For those not familiar with the Fargo-Moore are head area, this gives a sense of the area, about 600 square miles, the colored areas are the cities or urbanized area. We are a bi-state MPO, two interstates, a lot of interaction between DOTs. We have a population in the metropolitan planning area of about 180,000 people. We will continue to grow, recently adopted long-range plan points, if we continue at the pace we are on we would actually be a transportation management area by the 2020 census if the current rules hold. If we keep growing there will be additional responsibilities placed on the planning organization and our partners as far as traffic planning and operations in general. Based on our long-range transportation plan, while compared to places like Portland, large urban areas, we don't expect a lot of congestion, but know overall travel will increase by 40% and vehicle delay by 35%. We are not predicting staggering congestion, but for our size we see these numbers as alarming and want to begin to identify initiatives beyond adding new capacity to assist to manage this. We are really looking for the quantifiable benefits, to increase operability and the other thing, our recently adopted long-term transportation plan, akin to that you have within a TMA, begins to get the MPO process looking more holistically about how traffic operations is handled through the program. We were fortunate in November of 2008, Eddie Curtis and Paul Olson from federal highways came in, conducted a multi-day workshop looking at signal operations in the Fargo-Moorehead area. It was a start for us, they did one-on-ones, three primary signal operators, getting a sense of systems, limitations. A kick-off session aimed at technical staff and policy makers, so people on the MPO board, local city commissions and councils could get a sense of opportunity for trying enthusiasm -- it's more than detection, a camera, signal cabinet. We have been so focused on just let's deploy a bunch of stuff, but we also need to think about what that stuff will do, what's our objective out of that stuff? How do we want the system to improve if we put cameras here, do detection there. Our policy board responded, said let's start doing these, identify specific tasks to address traffic operations in the Fargo-Moorehead area. One thing our policy board felt strongly about when they adopted this, the federal highway report, our board wasn't as interested, or stakeholders. They wanted a specific action plan looking less at specific target areas, look more generally at what specific action steps we need to take as a region to begin to develop a more coordinated plan. plan. Four areas, signal systems, system performance, performance measures. If we're going to do these great things, enter connect signals, deploy things, how will we go about measuring, make sure what we are doing is having an impact. And two, INS management, centralized protocol. The planning, programming process, tips, STIPs, MT parking The other issue we adopt regional architecture [inaudible] the action plan to interrelate within the program so it's guiding the it ITs deployment plan, elements, most important role to work with the tips, STIPs, CIPs, local budgeting to be sure we're cognizant of opportunities available to get things budgeted, begin to implement actions we think are so important within the region. Over all the action plan sits right in the middle of the MPO. About 80% of the operations plan deals specifically with the [indiscernible] systems, signal systems interconnected, coordinated. It's broken down into four areas where signal systems are concerned. System coordination, getting the system connected, agreements in place, system design, operation, what are policies, procedures for operations. We have 275 signals controlled by five groups. There's a lot of typical engineering, design, the same regardless, but a lot of nuances concerning timing, operation we needs to begin to address from a common standpoint. The third element, signal operations are concerned, operational capacity building. Five signal operators, support staff, they all have differing levels of -- building capacity within the individuals, commonality in hardware, software, looking from more of a cost sharing basis, innovative deployments in the future. Specifically the system signal coordination, sub-area within the action plan, looking at three very easily identifiable action steps. One is to interconnect the city of Fargo with the Department of Transportation. The city of Fargo, largest in the area, controls 60% of the signal systems here, very good relationship with North Dakota DOT, but they control the signals on the interstate, looking at having better coordination on interstate system, increasing that interconnecting those system and putting under common protocol, procedure. Connecting with other cities on the North Dakota side, West Fargo. The second is the Minnesota side, consolidating the 45 or 50-odd signals that exist on the Minnesota Department of Transportation or city of Moorehead system, common system, platform and a big part of that since the plan is adopted, carry $2.9 million to upgrade an interconnect about 45 to 50% of the system, a huge win. Now we will be able to, ready to begin to interconnect, we will have 45 to 50% of the Minnesota system upgraded, interconnected like the North Dakota partners are. Those are the primary items we were talking about, system coordination, looking at what this means from a diagram factor. We have five signal operators, gives a general sense of the systems out there. Fields signals, number of entities, PTZs, video, the actual control stuff and starting to figure out the dotted lines need to be made solid lines to connect, communicate with one another. A key part in all of this u local North Dakota state university, collecting data, warehousing data and analyzing data so when it's all done we can go back to the politician and say see, we did what we said we would do, the money for projects have actually done something to improve the system. Unless we check the and warehouse data, and look at it, we are not able to demonstrate much efficiency. The next slide looks at the existing condition, you can see we already have a tremendous amount of fiber in the ground. A number of devices deployed along the fiber are interconnected. The areas you don't see as much on the left side of the map, currently implementing a project over the next two years to create a huge 2350EUB fiber network, upgrading the signals 24R. Some of these hurdles really aren't that high, has more to do with political agreements, less about physical connections. Generally, when you lock at signal operations, system coordination, where the plan point is, actions identified really look at initiating the -- beginning to queue off of largest signal, bring in other signal operators, different cities, darker color box, you see the North Dakota Department of Transportation, data warehouse, and the triple RDC is regional dispatch center, by state regional dispatch center. Want to make sure they are plugged in, can view the many cameras around the area. The other element within the system, sub-area, this idea of signal system deployment, trying to develop a protocol for hardware and software. Within different policy and practices, so we're all working from the same platform in times of timing, phasing, same settings for peak, and other programming so as the community moves from system to system they are being treated equally as an automobile. Trying to make sure there's a uniform level for expertise, at the loam level and -- trying to spread knowledge out among smaller operators, ensuring everybody has the same kind of information, come from working with the UWPW and developing cooperative learning, other signal operators learn from one another, tour other communities, regions that are doing interesting and exciting things. The other part is [indiscernible] we need a process for hardware and software, we have 275 deployed traffic signals, unfortunately mot all operated by the same hardware, we need to transition to ensure z as future deployments go out they are the same can be operated on a common software platform. In some cases it's a challenge, certain operators made decisions, investments. But we recognize to meet the regional goal we have to start working in that area. Portland, we learned establishing project priorities, seeking innovative, creative funding. we will want to look at surface dollars to see if our leaders are interested in using funds to move this program forward. Trying to really support multi-jurisdictional priorities, so every operator looks from a common standpoint. The system performance, measures, getting away from the signals now is really talking about making sure we have the ability to observe, analyze the system using the deployments there in terms of cameras, detection devices so we are actually able to see, gee, we changed the timing, went to coordinating timing, making a difference? Collecting and distributing data among the partners so they have the opportunity to view, watch it. This idea of system performance was left very hard, implanted by federal highways to focus on data collection, monitoring, using that to set and meet goals and objectives. Simply sharing how the system is doing, monitoring, reporting. A little of a restep from the prior slide, focus of action plan where data is concerned to develop a regional program. Everybody collects data on their own schedule. We are moving toward a coordinate the schedule. Trying to look at a more formalized process, our reporting documents to begin to report out to the public what sorts of things are going on, where traffic operations are concerned. Thesis next couple slides just demonstrate the ITS plan, a sense of where we have detection, high priority detection. The action plan remains cognizant of these kind of documents and plans to say okay, these are the priorities we set, let's make sure as we implement projects, do design, corridor studies, we are not forgetting a specific corridor was a high priority for detection, get those things involved in the plan so the funding is there. I highlighted a number of critical corridors where the tools are there. We have the wires in the ground, cameras on the high mast arms, everything there. The action plan is about putting more of that stuff out but we want to make sure the stuff there is being set back into, fed back into something to better [indiscernible] the whole system. The final elements of the program are INS management, SAFETEA-LU talked about transportation, security, a requirement couple years ago, specific recommendations as far as trying to strengthen relationships with regional dispatch, incident managers, we have formalized communication, develop protocols among agencies, how you address special events, incidents. Each group has a unique set of strengths. We want them maximized. The system maintains operations, protects the traveling public. This is another graphic a bit dated, but you can see a number of deployed or soon to be deployed CC TV devices. Most of the green dots are deployed or have been this summer. We are able to watch our transportation system in real-time. When it comes to trying to respond to incidents, manage traffic in real time, we request do it with the action plan is doing to give direction to tell us we need agreement with these folks, these folks, so the technology is used more effectively to manage our transportation system. The final piece of all that is the evolution to a traffic operation center. We are in phase 1. Moving to a hybrid system, communicating among centers, no one location, the transition is ongoing, will happen over the next couple years. In the long term the politics of the situation will dictate there's a real demand for a traffic brakes -- operations sorry. We have a working group implementing these things, a concept of operation, architecture nearing completion. The legal agreements are basically starting to get those looking from a concept standpoint to say what we need to do. To keep us on time I will glaze over, what the traffic operation center will do for us, system coordination, safety, technical capacity, being the focal point for regional operations. As we see these things growing over time, our vision, cooperative vision, we want to build a combined emergency response traffic operation center able to interact with signals, sensors, CC TV, data we collect through this is appropriately warehoused in the future. The backbone of this, a ton of experience mere here in the area, to come up with a operation board or technical committee so as we move down the road they will oversee how all of this works, developing the master agreements, managing the system, providing the planning, programming oversight so this whole thing jeel gels, stays together. That's it in a little bit more than a nutshell. I do provide my e-mail address there. Our action plan is available on the web page. It's not real exciting, a lot of bullet points, not many interesting graphics, more of a workplan. Thank you. Thank you very much, Wade. With that, I will invite folks, if you have questions, to write them down in the chat pod. But for now we will hit the ones we have. First, we had a comment with a recommendation for folks to take advantage of the federal highway and federal transit administration's joint [indiscernible] I put the web link up for the program site. I will throw in a plug for the Webinar we did several weeks back regarding planning for operations, and deliverables coming out of that program. A model plan template that provides a template for plans to use to integrate operations more fully into the process. At the end of the Webinar Jocelyn will put up a link. Our first question was directed for Dina, with regards to the CTIC. Are there now transportation users or owners of the fiber network, public safety, emergency management, et cetera, and are there any general purpose users of the network such as the city of Portland overall IT department and if so are there any special stipulations that govern their use of the fiber network? This is Dina. I am not an expert at CTIC, but I can tell you my understanding is fiber sharing agreements are largely isolated to the transportation agencies. I believe within the city of Portland they have a bureau structure. There may be some connection with the public safety folks and office of emergency management. I understand the fiber sharing element primarily from the ITS network perspective and within that framework it's isolated to transportation agencies and actually working with Portland State University. universe its. Portland university. There's no participation in non-government agencies. Next question regarding cost and revenue sharing, how [indiscernible] respective participating jurisdictions, and are there any shared costs? This is Dina again. As I indicated, our role, model has really been not about cost sharing. We've been focused more on sharing of resources and relying on individual agencies' operations budget to step in and provide coverage. More recently, especially with -- particularly the last couple projects, our signal upgrades, we relied on ODOT, the grantee receiving the funding, and they ran the contract. We had IGAs developed with the local averages agencies doing work in their right of ways, allocated out to work that was done in local jurisdictions right away. It isn't so much a cost-sharing thing, more about roles and responsibilities for us. Do you have a similar A arrangement in Fargo? Hasn't been a opportunity to split costs yet, but in places like for example Minnesota, the city of Moorehead, we looked, wanted to treat as common property. Each entity would share the cost, whatever they are going to get out of them. If you are dropping in a signal, that signal were to be on the Minnesota Department of Transportation system, they pay the Moorehead system, the costs [indiscernible] evenly, have to be cost-sharing as you get into hiring staff for maintenance activities, something talked about here, trying to share maintenance costs. There would be things you would have to prorate, maybe based on number of signals. But definitely something worth thinking seriously about, how you begin to split that specific to sub-areas. It can be different. Software, that would be shared among the partners. The agreements will be specific to the various sub-areas. Here's a novel question. Many metropolitan areas have a regional transit authority, do you know of anyone who ever considered a traffic management authority manage regional traffic systems and police stations, traffic management? So much of the transit agency, a little different, TMA certification review, you don't see much of those type of activities just because they serve two different masters and the funding, may be different, transit -- [indiscernible] can be a little different, capacity building, different from our funds, a lot of times, sometimes different agencies -- the only people that -- if the MPOs responsible for transit, maybe the only one who consider, maybe Nevada, if there was anybody. Mr. Rick Denny chimed in with that, example, the Las Vegas traffic system is managed by a consortium. The only one with multi MPOs responsible for traffic. I could add in, this is Jocelyn. In early 2000, federal highway was, the regional operations community was looking at something called regional operating organization, otherwise known as BREWSs. I know that idea died. May have had to do with political conflicts. But yes. That idea came up, had some esteem in early 2000. Dan? 24 This is Eddie, I managed to hang up by reaching for the mute button. I am not really familiar other than what Jocelyn and Laurie mentioned, say authority for traffic signal operations, that's the direction we may be headed in with these signal programs. Next question, probably the age-ole question of regional coordination, how you approach the challenge of building a consensus and cooperation and participation, multi infrastructure agency and entity arrangements? This is Wade in Fargo. I can tackle that. There's always issues of trying to deal with multiple jurisdictions. The success we had, something we did early in the process was identify what the commonalities are, common needs. Everybody wants to accomplish something. Once we had done that, put everybody's needs into separate silos we were able to see the commonality across, to say, the city this, the DOT this, and our action plan is really just the regurgitation of everybody's desires. People get red in the face, may require some arm-twisting, but that's public affairs. If you start from addressing common needs, common opportunities -- Dina: I would support what Wade said about looking at common objectives and goals. I would say here in Portland because we have such a long history with transport, as an entity that has really shown its ability to implement and get things done, that's really, we are more challenged with keeping the interest of and people coming to the table over this long period of time. I would again say it's all about, so long as they feel like they're actually getting something out of it, achieving -- that's for us, whether an opportunity to share resources, technical resources they are able to share, joint trainings, workshops, a lot of ways to keep the interest and keep people coming back to the table, constantly looking out ahead to new projects we can work on together that will benefit the entire region. That's been our strategy in trying to maintain this long-term relationship we have had in 24 this region. We had a question about performance measures. If [indiscernible] briefly say what arterial performance measures you collect, how you collect them generally. This is Wade. That's part of the whole thing. We really don't and recognize we have to. Our long-range plan we adopted this winter, in December, points in that direction. We need to start developing specific performance measures, gets further refined in the action plan, starting to look at more regionally significant arterials, figure out how to operate, inter accesses operate, once we get there we will have a better understanding of what data we need to collect. We have all kinds of data now, but the problem is how are we using it to measure performance. We are in the discovery stage, objective-setting stage, at the -- just beyond the start line where some of that is concerned. To follow-up on that, we are in the same position, with the work we have done on our regional plan, focus on outcomes, performance measures, finishing up the system management plan we are looking lad ahead to out how to work identify the challenge. We identified a couple projects remember developed in [indiscernible], pilots for being able to collect data. Some areas we have been exploring, for example travel time, changes over time of day, day of week, been a big challenge. Experimented with Portland State on data from the agency, experiment being with Bluetooth technology, access card readers to grab the signals off of enabled devices and track travel time. Still a long way taking to be able to go to be able to bring in travel time. Upgrading controller equipment we are hoping we will be able to actually pull more data out of the controllers and not just top it. This is Laurie. Do you coordinate in performance measure with CMP to congestion management process? Yes, that's the idea. What we will be doing over the next two years, really working to use the CMP our framework for being able to monitor. Our transportation system management plan is the implementation vehicle for getting the CMP monitor and data. All right, our last question was how would you go about identifying a traffic operations management structure in terms of entity and personnel? Like whether or not you would utilize existing multiple agency personnel, integrate into a single traffic signal management structure. This is Eddie. Maybe I can address that. I think it varies among each region. We have seen regions that organize around a centralized management structure. Good example might be operation green light in Kansas City. Others tend to maybe maintain a distributed consortium. Dr. Cog in Denver might be a good example of that. There are hybrids depends on the relationships in your region, that's a decision, structure that forms based on your history and objectives within the region . I just looked at the clock and I think we have run a little over. Perhaps we should wrap things up. That sounds good. Thanks, Darren. I will go through some of the closing slides here. You see the member organization of the national transportation operations coalition or NTOC. The website is listed on the slide to find out more about the organizations. Contains information about upcoming webcasts, and previous webcasts. Probably about the last four years or so. We have the slides from today's presentations up in about a week, along with the recording. NTOC has two discussions forums, high-level or strategic issues and ITS deployment and lessons learned. You can seen sign up for the newsletter sent out twice monthly with announcements of the upcoming Talking Operations Webinars like this. Will you like to close us out? the slide is up for the next seminar. May 13. Please go to the website to sign up. Other topics are in the hopper. presentation on on the new, revised [indiscernible] 2009, (end)