Hello and welcome to a Talking Operations webinar hosted by the National Transportation Operations Coalition – otherwise known as NTOC. The title of today’s webinar is Template for Submitting Dynamic Mobility Applications Using IntelliDrive. I will be giving a brief introduction to the web conferencing environment before turning the session over to Darren Buck from the Federal Highway Administration. Darren Buck will serve as the moderator for today’s seminar. Today’s seminar will last approximately an hour and a half, with an hour allocated for the presenters and the final 30 minutes for audience Question and Answer. Please be advised that our seminar is being recorded. If you have a question you can type it into the smaller text box on the left side of the screen. Send your question to everyone rather than just presenters. Presenters are unable to answer questions during their presentation, but Darren Buck will use some of the questions typed in the chat box for the Q&A session at the last 30 minutes of the Webinar. The Webinar will be posted on the website. Attendees will be notified of the availability of the presentation, recording and closed captioning of the seminar. We encourage you to advise others to -- to download a file click with your mouse on the name of the file you would like to download, and click at the bottom of the box that says save to my computer. I would like to introduce Darren Buck, marketing specialist for the federal highway office of operations duties include overseeing -- national transportation coalition. Darren worked in similar roles with the bicycle community and a small federal program creating jobs for people with disabilities Darren received an MBA from the University of Maryland in college park and -- is currently -- Darren Buck: Thank you very much, Jocelyn, today we will hear about the use of a new dynamic mobility applications template to provide input into the tell IntelliDrive program. We will get input from stakeholders, and walk you through that template tool for submitting your application for consideration for IntelliDrive. We will hear from two speakers. First, Katherine Hartman, worked for federal highway and federal motor carriers in the research and technology office, the freight office and currently on the project management team in the IT S joint program office, background as financial researcher, paralegal, serving in the peace Corps as a business adviser. Graded from the University of Virginia with -- and MBA from the University of South Dakota. After that we will hear from Bob Rupert, the information management team and technical coordinator in operations office of transportation management in the headquarters of FHWA. Mr. Rupert manages the traveler information, 511 traveler information program, and real-time system information management program, the FHWA lead for the dynamic are mobility applications program, and Steve Mortenson and [indiscernible] from FTA. With that, I will turn it over to Katherine. Thank you, Darren. Good afternoon everyone. I will talk about the IntelliDrive program. I hope it's a high enough level to get an understanding, not -- those who are familiar are not bored. IntelliDrive is a concept leveraging to -- connectivity, rich environment substantial opportunities, safer, smarter, more environmentally friendly. The presentation structure for today is for me to give IntelliDrive mobility application background and the template recently released. The purpose and intent behind the creation, the content, and the next steps the us USDOT plans to take. The next slide is a five-year program plan for the dynamic money mobility program. We are doing this through various program tracks including stakeholder engagement, some applications development which is where this template fits; some basic research, institutional policy work, standards work and then going through the usual testing, deployment and evaluation, and throughout the program we will continue to do outreach. But, the slide you are looking at now is the IntelliDrive network's environment which can be summed up in data in, actionable information out. We can pull data from a variety of source and it can be used in -- the guts of the Intel drive program. The next slide goes into more detail. -- the data will come from multiple source and types. The data captured, cleaned and -- used by multiple applications, enhanced weather applications, real-time transit signal priority, real-time traveler information systems, environmental applications such as echo drive, and then safety alert and Q warning systems. Real-time data capture management addresses the capture, cleaning and integration of the data in real-time. Dynamic mobility applications addresses the use of data in real-time to develop and deploy enhanced or something mobility applications, drawn from vision documents the USDOT has created. We will need feedback on the approach, especially when things are different than usual. Throughout the program we will continue to listen to the stakeholders and hopefully be able to address your needs and concerns as we move forward. What's the data environment and how's it any different from what we've done in the past? Data is pulled into the environment as shown in the orange globe, the data users can use it to extract data, can have multisource data which may be observed, simulated, interpreted, in? Cases the observe bed data may be flagged as erroneous, may be interpolated to help with assessment of applications if there isn't market penetration to help with technologies. The key issues in defining a data environment; may sound easy until you have to do it. There's a lot of data out there, what data do we capture? The easy answer is we can capture all of it, then figure out what to do with it. In some cases, not the best idea to capture every single data elements, the communications requirement. The other, why are we and how do we use the data, one size does not fit all. There isn't just one data environment that addressing all applications. One may support tactical and intersection, the other is national level freight movement. Supporting a specific or multiple application and there can be multiple data environments. The third issue, what data do we keep? We may not be able to keep all the data because of privacy issues, intellectual property rights issues, and the like. We have to make decisions about what data to keep and what to leave out. Finally, how do we structure the data? Do we need rules? What are the guideline and [indiscernible] right and privacy issues associated with them. Next we will look at the data source and data uses. You cut the orange globes into two, on the left are the source and on the right are the uses of data. Where do these data come from? Program will capital punishment and you are integrate from different sources. Well documented, a number pr infrastructure sources already. In addition to looking at the infrastructure as a source, IntelliDrive is also interested in vehicle and travelers as data sources. For vehicles we are interested in getting data from transit, freight and lite vehicles, not just the location and speed, but other data such as rine sensor status, wiper status, measured air temperature, exterior light status, and so on. For travelers we're are interested in not just the location of the consumer device, but to systemically acquire the -- what kind of decisions were made and what the outcomes of the trips were. This kind of data the research community has been asking for, for decades, and haven't been able to get outside of infrequently -- mobility applications, safety applications will show, that have been looked at in other ITS programs. The hard safety, crash avoidance, is not part of this program. The projected outcome of this first phase of the program is that we would like to establish one or more data environments so users can start to utilize the data and collaborate. We need the data management process set up to support multiple users from the beginning. There is a website that is being stood up, still under development, but captures data we have been acquiring and the website location is noted on the screen. If you have questions about that we can provide more information later, but do know it's still a temporary development site and we hope to grow it as the program continues. Next we will discuss the two mobility areas. Real-time data capture management and dynamic mobility applications. Location, data, weather data, vehicle status, infrastructure data are captured, cleaned and integrated into [indiscernible] data environment. The data is then used by multiple applications, enhanced weather, real-time transit signal priority, traveler information system, environmental applications such as eco drive, key warning systems. Real-time data capture management addresses the capture, cleaning and management of data in real-time. Dynamic mobility applications addresses in real-time to develop, deploy transformative mobility application. The material in the next slides were drawn from the vision documents the USDOT created. As mentioned previously, we don't collect the data for nothing. We need to do something useful with it, specifically developing application that's maximize enhanced system productivity and mobility of individuals within the system. We are not ruling out private sector application. To develop, access applications that show potential to improve dynamic decision-making, analyze the potential benefits to be realized by these applications, they will be prioritized based on potential benefits, deployment costs, risk and stakeholder acceptance. Only when we have proven in a smaller test I environment that it really works will we move to development phase. Leveraging multi-source data. We will fully leverage hie-quality, integrated multi-source data to support multiple applications. The dynamic mobility -- will coordinate closely with the management program to identify promising mobility applications with similar data needs. The figure on the screen illustrates how data from mobile and fixed sources are integrated and managed under the program. Data and information from this environment can be systemically extracted and used to support the identified set of applications. This may target specific modes, automated safety checks for commercial vehicles or multimodal in nature. For example, a traveler information service integrated tolling, transit and parking availability or costs. System management functions, coordinating control between modes and jurisdictions. A coordinated approach is needed to develop most specific or multi-modal applications. The open-source approach, which we intend to pursue in this program, will help us avoid duplication and is definitely more cost-effective. For example, if we have an algorithm that gives an expected time of arrival of a vehicle at an intersection it might be valuable for -- eco driving application, no reason to build that application or foundational element twice. Let's build it once and re-use it multiple times. Guiding principles. Some of the guiding principles that are taken directly from our vision documents include leverage multisource data, develop and test mode-specific and multimodal application, feature open-source application research and development, encourage collaborative -- program resources based on expected impact, enhanced analytical capabilities and practice long-term technology stewardship. Regarding the last bullet of practicing long-term technology stewardship, we plan to put in place mechanisms for doing this. For example, if early data environments weren't fully fledged or have limited amount of data due to low market penetration only a few may be supported, but as a market penetration increases, with additional data flowing in, the range of applications supported by the data -- looking at the combination that can be supported at each station as a program evolves from the current state to the end state. If the program works the way we envisioned it to there should be multiple stakeholders leveraging -- free of entanglement and patents or clear to anyone who decides to participate before they do. The eventually deployment of thesis will enable the transformational change we have been talking about as one of the overriding goals ever the IntelliDrive program. I want to emphasize the stakeholder participation. Stakeholders are invited and encouraged to provide input on these programs. Funding requests for data collection and applications research and development and for commercializing applications developed within the program. I am going to now turn it over to Bob Rupert to talk more specifically about the mobility application template we recently released. Bob? Thanks, Kate. Kate provided a lot of background on the mobility portion of the IntelliDrive program, and now we are getting interest into a phase we are really looking for stakeholder input, the use of the template. The near-term program objectives, again, one of our interests is to be able to assess the applications, look at full potential for exploiting IntelliDrive, showing benefits, identifying applications where we need to invest federal resources. The second bullet, certainly looking at applications that are really transformative. What we're doing now, doing better, but what we think with this rich, robust data Kate described, we think there's a lot of capability to do even more, differently, better, system performance, decision-making and better travel experiences for everyone. So this is, you get to the last bullet, inviting stakeholders to share your ideas with us. What do you think some of these applications would be? What would best exploit the IntelliDrive system, not just data, but communications, infrastructure, everything that goes with IntelliDrive. What are some of the applications you are thinking about, long-term, near-term or long term. That's our intent of this. The underlying purpose behind the template, we want a method to gather this information, make it easier for everybody to compare, contrast applications, examine the application and be able to help figure out the ones that are most useful, hold the most promise. That's again where we want to go at the end of this. As Kate mentioned, certainly other programs looking at the active safety applications, not necessarily what we are looking at here. We are looking at those primarily focus said on mobility, but not completely throwing safety out, but focus on those providing more the mobility applications. The innovative, transformative ideas that will help us all use the IntelliDrive system. A little more background, not starting from square zero, hopefully looking at a fresh like. That's where this Webinar, other stakeholder actions we've had lately, meetings, is good at broadening, bring ing in fresh eyes and minds. There were applications, use cases around the proof of concept testing a couple years ago in the Michigan area. Most of that information, called the Day 1 applications, someone turned on the IntelliDrive system, what would be useful now without necessarily having a lot of mobile devices implemented. That's what we meant by day 1, near-term penetration. The next slide, day 1 applications, fairly broad array of those, some more thought out than others The note in the bottom, transit, trucking, planning, not included in the initial go-around, to be added later. We are certainly looking for that outreach now, engaging the entire community in these. With this information, this is certainly on the table, examining as we look at the applications, but we want to get your ideas also. But so you know we are not necessarily starting at zero, didn't throw everything away, the previous work, but are looking for fresh ideas, as we move forward. Let's talk about the application template itself. It's not a request for proposals. Not a solicitation for projects. You are not going to submit a great idea and we say let's fund it. It's not a challenge opportunity. We are beating the bushes for those ideas. We want to engage the intellectual aspects of the community in providing those ideas to us. As Kate mentioned, we want to take these, help flesh out the program, provide the entire list, the suite of applications to look at, prioritize, figure out which work best. So what is it? It is an opportunity for you all to help shape the IntelliDrive dynamic mobility applications program, share your ideas about an innovative way to explore the data, infrastructure, whatever, really improve system performance, allow better decision-making, better travel for everyone across all the modes. A request from us to engage you all across the board, from all sources. Public, private, academic, we're figure for looking for thoughts from everybody. The idea of being able to use multi-mode, stretch thoughts, give ideas about those applications. We will be re-engaging stakeholders at a number of times. The next engagement will be to come back out for to you help us prioritize what these will be. We will deal more with that, process a little later, but right now we want to gather your ideas. Let's walk through the template quickly. It's relatively straightforward, we think. I won't necessarily say simple to fill out, but not overly complicated. We think we have gotten it to a point where it's not complicated, relatively easy, but provides enough information that people looking can make the decisions about what's a priority, worthwhile moving forward. The first part, obviously, contributor, who you are, how to get in touch with you in case we need more information, something to follow-up with. The name, purpose of the application itself. Fairly concisely state the problem the application is trying to address. There are a lot of cool things the people can do with the data, the system. We think what will make the applications, help people identify useful applications is what problem are we trying to address. Relatively concisely, not a lot of empirical data or well-researched, but thoughts about what the purpose of the application would be. Next slide is a series of check-boxes. The reason behind the check-box system to help us do categorization of the application when is they come in. Kate mentioned multiple data environments out there. Being able to look at where there are overlaps between applications will help us identify where applications can make use of common data environments. We can go through, check individual traveler benefits, system efficiency benefits, you see the broad range, from reduced cost of travel, environmental impacts, safety, security. A lot of things where the application may have multiple purposes. The next slide again highlights the idea we are looking at multimodes, the idea to really seek out ideas that would help, not only mode-specific, but multi-modal and cross-modal applications would be worthwhile. The next slide talks about the application description itself, brief description of the application, who would be the audience, the users. Again, this doesn't have to be exhaustive. How would you describe the application, who would use it? Who would benefit and how is it transformative? In your words what would make the application innovative and really be a good use, transformative use of the system. Next slide gets to some of the needs or benefits, sorry, impacts. Not looking for empirical data here. You don't need to run a lot of expensive modeling, but what in your words would be the near-term benefits, perhaps you don't have a lot of [indiscernible] also what would be the long-term if we had 100% of the devices enabled to do IntelliDrive. Some of the benefit and impacts we are looking at. You can include, but are not necessary. Maybe one way of really thinking about the information we are looking at, put yourself on the side of the reviewer, what information would you be looking for, the minimum level for somebody to fully understand where you want to go with the application, what makes sense in it, help people prioritize it. Doesn't have to be a whole lot, empirical, but enough to show the idea, more thought out than initial thought. Next couple slides get into into some of the hie-level -- other looking at does the data have to have specific characteristics. For for instance, if you need location of the device, how specific, how often, timely do they have to be? Can they be downloaded at end of day or you need every five minutes? What are the data needs themselves, latency, frequency. Does it really have to be secure? Could it be something relatively, public Wi-Fi or something like that. The type of communication needs. I will emphasize, in the instructions, if it's not known, you don't have specific communication needs, that's okay too. The next one talks about additional needs. IntelliDrive will have infrastructure involved with T some road side equipment, cabinet Ray, does your application require infrastructure needs? Then anything else you want to share to make is useful, deployable, not deplorable -- I want to get that right, make it most useful to the community and its intended audience. The opportunity for you to tell us, the reviewers in general what are the needs of the application itself. The next one really gets to the last part of the application itself. This asks the fairly fundamental question if building off previous search. We would like to know that. Gee, this sounds familiar, may build off an early basic research project, going on in university transportation center or something. We would like to know if it builds off anything, what it might be to follow-up with people. Not a lot of detail, just if it's a follow-up, good to know, just so we have a better idea of what's going on out there. That's walking through the template quickly, but don't think it has to be exhaustive, we are looking for a little more information than a paragraph. A little more thought out than that. The reason for the next steps. In addition to the broadcast announcement about the template's availability, targeted outreach for modal specific applications, reaching out to stakeholder groups, familiar with these on the highway, transit side, freight side, maybe walk through a little more one-on-one with the template to give a better level of comfort in what we are looking for. We know the private sector is a group we want to reach out to, have to get somewhat innovative in doing that. We had some questions come in already, not on this, but previous to this, if I would like to fund, just a way to get it in here. Probably not. Unless you can describe at a high enough level, we're not, again, looking at funding anything, but want to capture ideas somehow, make sure we're allowing the private sector to flourish, we have to do extra work with the private sector, to reach your idea and make sure you can best use IntelliDrive, all it has to offer. There will probably be other opportunities to reach out to the private sector we will work on, so stay turned for those, coming up in the next month or two. We will gather ideas, requested these initially by July 31, gives us a start to doing analysis, comparison to what's out there. There are opportunity coming up in the fall, early stakeholder engagement, start sharing some of the lists, applications with the stakeholders, with you all. That's why we drew the July 31 line for submitting. After July 31 we won't shut off the e-mail box at all, but that will be the time we start going through the list of application and looking for commonalities. Really looking for applications to make use of common data environments, where it makes sense to lump things together, perhaps if there's duplication. Rather have an application twice than not at all. We are doing the best we can at getting ideas from the community. We want to bounce it back to you, share the list with the community. We have to do more internal debate, whether we share this initial list without prioritization at all, figure out how to publish it so it doesn't look prioritized, certainly benefit in sharing the initial list and after prioritization with stakeholders we want to share that list. Because we don't have unlimited resources to handle development of really good applications, but there may be other good resources out there someone meant to draw on perhaps through university resources, private sector, who know what is, so the whole community has the knowledge we have as far as the prioritization what we think the highest priority application is. We will provide the list back to y'all. The next bullet I already talked about, reengaging stakeholders throughout the fall. The bottom line, identifying where best to invest federal resources. Going in, Kate alluded, our going in thought is probably not going to deal a lot with end-user applications. The private sector seems to be doing a good job with that. May not need our involvement, other than private sector can use the data. Anticipating to end up in the public sector applications, either the market is too small, industry can't afford to assume the risk necessary to development advanced applications, but those are the things we will look for as prioritizing applications. That's what the guiding principles are, our thoughts of what we are looking at to prioritize from the federal investment side, the transformative application that's make use of IntelliDrive data. And there is a stakeholder interest, apps to be used by the stakeholders, benefit, and agencies can use, the entire community. Also near term long term benefits. and Kate mentioned also we are, the once we will invest in the federal side, going to be coming out with open-source rules, open-source development portal to try to make sure the application and developers are more open source. Means a lot of things to a lot of people. Part of what we are putting out with open-source portal is rules of engagement, what we really mean by that. We are not necessarily looking at open-source , everything in the development chain, not sure how far down the development chain we will go. I can see for some applications our investment would be to the point of developing an interface perhaps, an API, if you will, others we would have to go to maybe prototyping applications, again on the public sector side we anticipate primarily just to show their viability and to show they can work. It will vary from application to application but we are looking at try to make as much as we can open-source and openly available. Again, we are looking across modal applications, really think there's a lot of benefit, not only from the individual traveler, but also getting best performance out of -- there is the contact information, and the last slide, just the generic IntelliDrive website where there's a bunch of information on IntelliDrive itself, link there to the template, to download. Back to the DOT website, library that will have information. So that's the end of the formal presentation. All right. Thank you very much. Let's -- we will just run through the questions in the order we received them. First one: The United States is a big place -- sorry, minor technical difficulty here. I'm sorry. Is this test program based on a corridor type environment or do the data elements overlap? I don't know if this -- not sure I exactly understand the question, whether it's related to the ICM program, and that model or if it's talking about using different types of data elements, integrating them -- I guess I would ask for clarity from the presenter, but in general, the more multi-modal, cross-modal, system-wide the application is, more than likely the higher priority it would be given. If that didn't address the question, let us know and we will try and answer. I guess -- I will take another stab. Looking at dynamic mobility applications program, the United States is a big place, why we may not be looking at national applications, although there may be some. Corridor applications? Certainly. Do they have to be? No. Certainly not. They could be metropolitan-wide, state-wide, anything. We are not constraining ourselves as to what would be the scope of the impact of the application and do the data elements overlap? In general the answer is yes. As we start developing, fleshing out environments we hopefully will be capable to help better define those so that people can see which environment can best be used by their application. Kate mentioned also in her presentation this is a very iterative process, so as we see some of the applications coming in, data needs, that will feedback into the date sai capture and management program to continue to flesh out and refine. There will be a lot of back and forth, if that helps answer. Next question raises the concern that -- certainly encountered with the private sector, if a company submits an idea, does that idea essentially become public information, available to potential market competitors, and to what extent are individual applications going to be shared? Yeah, as I mentioned, for this exercise the answer to the question is yes. Whatever comes into us will be shared in some form or fashion, why I tried to highlight we know there are challenges there in reaching out to private sector, to be able to get your ideas on the table. This may not be the best mechanism for that; because we're really not looking for protecting, if you will, anything that comes in. We are looking to make this as broadly available as possible. The suggestion might be, if you can describe at a high enough level to not give away market secrets, but we will find other avenues to reach out to the private sector to gets to those ideas, but this is not the exercise to do this. This is getting information and turning around and releasing to the community. Bob, can I also suggest, if you have questions, especially specific, you contact one of the folks listed, have a phone conversation, either myself, Bob Rupert or Randy butler. Steve Mortensen. We can try to address your concerns and like Bob said, this may turn out not to be the place, but don't think we're going to forget about you. We are just trying to figure out how to best engage. Next question, general question about IntelliDrive. The questioner asks whether or IntelliDrive is trying to explore more of a 3 gigs [indiscernible] is that a valid assumption?