We created our website. The web team is really smart and they created this thing called an API (application programming interface) that I didn't know exactly what it was. Ten years ago, the web team created an API for us. The API is a feed that is just a way that one computer programs talk to another computer program. Only in the last 5 years did I realize how wonderful that is and that is how some navigation providers work with us. If I was a navigation provider, I would not want to deal with 50 different state DOT APIs. You would want some kind of standard to work with. So that's where WZDx (Work Zone Data Exchange) comes in for the works on data exchange feeds. This feed is a standard way that people can pull our work zone data as well.

In the beginning, it was quite a bit of difference that Wejo was a bit slower, but what we found later is we did get it in quicker. The problem we had was getting it from Wejo to our cloud provider into the tolls and to us. So there's a little more latency there that we had not been able to address, but I will agree toward the end—the last few months—we had definitely seen an increase in speed from Wejo.

You can do this on any scale you want. And if I was a state that hadn't ventured into this yet, what I would do is just pick a couple of big ones like Google maps and Waze, and I would try to create connections with those companies. So, just make yourself a spreadsheet and keep those connections. And then, when you find out, like we had been emailing someone at Apple for a long time. This other person at Apple said, “Oh, I'm the new person.” And then somehow, things weren't getting there, etc. We have had to turn this into a self-service process. So, the whole DOT comes to us for help, and there's a lot that goes into it and it's never simple to just reach out. So we've really tried to make itself service and if you develop this process, you should write it down in a way that you can share it with other people within your DOT. You don't want to become the single funnel to these companies, because it is really a lot. You'd be surprised how much we work with these companies. Don't put it all on your own shoulders. Make it self-serve and here is the way you can navigate with these companies.

We do. We use it as validation. We have a human 511 system, a telephone system. When we get a caller that says “Hey, I'm sitting on I-40 at mile marker 200. There's a crash.” We say, “Do they really know where they are?” That's when we'll go to Waze or to our—like Ed was talking about—our probe speed data provider, and we'll say “Okay, are we seeing something consistent with this.” If we don't have cameras, we'd like to have two sources to verify an incident, so we'll use crowdsourcing as a second source for verification. And we're also experimenting with some push notifications. It has to be hard for an operator to just sit there and stare at the Waze map. We don't have an ATMS. To just look at the Waze map and say, ”Oh, there's something that seems inefficient to me,” so I like the idea of pushes. And there's a lot of services that we subscribe to that have these pushes like Waze, and various sources. So we're actually—right now—evaluating which of the push sources are effective and which actually help us instead of doing a bunch of them. We're actually studying which of the free services of push data is really the most valuable to us.

The answer is yes. It depends on the location. We're not publicly putting them out on the web right now. We are putting them out for our whole team and we typically bring in the responders based on project to project or on their geographic area. So we do give them logins to see that. But on project specific, I'll give you an example. We had a bridge issue that went out, and typically a new county in our northwest region. We actually put these out for all the local responders to see how the performance was, and we would have weekly meetings with them and go over for the first, probably three to four weeks, making sure they understood what they were seeing. As we got to the end of the project, we didn't need those anymore because they could read them as quickly and easily as I could. So I guess to answer the question—Yes. We are trying to do that with all the responding agencies near us. Have we got it all down? Absolutely not. But we are working to get better.

Well, as an operations person, I agree with you. I would think they'd be great, but I'm pretty sure the first few months they went into the circular file or the spam folders. Only because you know it's new. It was a change and it can be overwhelming. What we found—just so we did with the first responders—it really took some one-on-one conversations, and a few incidents of explained to him, “Here's what we're seeing. Here's why we're seeing this.” This is what we're sending to you and getting that information out of them and having the one-on-one conversations. Yeah, probably what sold the best for us for our overall construction staff is, we started being able to pick up anomalies and construction zones from these dashboards that we wouldn't have caught anywhere else. We had tapers that were wrong. An example is we had a lane with wrong—it was drawn perfectly on the plans. We drove it, it felt fine, but we just could not get traffic through, and really start to show up in our crowdsource data that we had a problem here. We ended up going out with a lighter if you could even get close to it since it's so busy and so congested. We found out when it was built the contractor actually built the lane at nine and a half feet instead of eleven. So, as trucks went through a taper where we had a nine-and-a-half-foot little bottleneck in there that we found the appropriate data and that was where we kind of sold it to construction. That, “Hey, look! We can find these things about you having to be in the road and measuring out there. We know there's something wrong. Let's figure out what it is.” So, I won't say it's completely adopted by any means, but we are definitely making progress and getting better in Indiana to using it.

To answer your question, yes, we will work with anyone that wants to. You know the local agencies we typically just we end up doing it and putting it toward a web page if we're already getting the data set. But for another agency, if they're interested in any of the tools we showed there, we'll have to just talk a little bit about what language you code in, and how you're running. It's not as easy as saying, “Here you go,” but we will absolutely work with you, and getting you the information to either help you develop it yourself or apply what we've done to your environment. We honestly, we share with every one of the providers. You know we're very open with them, and they turn them into tools for those groups that don't have the resources behind to. I'm lucky. I have my own IT department here that runs an entirely separate network off the DOT.gov side of the world. I know that's not the case, for most state agencies. That was a very long way to say “Yes. We will work with anybody who wants to know and we'll try to help them get to where they want to be.”