Registration Landing Page (2)
Overcome Connected Vehicle Deployment Challenges to Enhance Road Safety

Webinar date: April 12, 2023

Learn more about how your state can take advantage of the latest connected vehicle technology.

To view in full screen, click "Watch on YouTube."

Contact Us

Video Transcript

This transcript was auto-generated by the webinar software. Please forgive typos.


Hello. My name is Amy Blyth and I'd like to welcome you to today's webinar, Overcome Connected vehicle deployment Challenges to enhance road Safety. We're excited to get started, but first I'd like to go over a couple of housekeeping items. All attendees are in listen only mode. If you have questions at any point throughout the webinar. Please use the question box in your goto Webinar Attendee panel will save a few minutes at the end of the webinar today for some Q&A.


If we don't get to your questions today and our time together, we'll answer them directly via e-mail after the webinar.


Additionally, you'll have the opportunity to answer a short survey when you exit the webinar, and we'll take just a minute of your time and your responses are very important to us and help us create valuable webinar experiences for you in the future. So, let me introduce our speakers. First off, I'd like to introduce Shane Zumpf, who has over 22 years of experience in the information technology field for the last seven years. He has focused on intelligent transportation systems are IT, yes, as well as mastering connected vehicle or CV applications and architecture, gathering, analysis, design, oh excuse me in design.


His experience and all software and application development life cycle phases, including recurrent requirements, gathering, analysis, design, coding, testing, and maintenance. Moreover, Mister Zumpf has pioneered architecture design for CV applications as the Technical Lead for the Wyoming Department of Transportation Connected Vehicle Pilot Project.


Second, I'd like to introduce Zorica Cvijovic ..., who is a PHD and a connected vehicle Strategist.


Dr. Cvijovic has 10 years of experience and traffic engineering, transportation, and logistics, including her doctoral degree in transportation engineering at the University of Wyoming, and a Master's Degree degree and traffic and transportation engineering from the University of Belgrade, Serbia. As a connected Vehicles strategy Chess. She focuses on the implementation and evaluation of operation and safety performances of various applications. In the C V environment, she also has a strong background in traffic signal operations and IT S So Rita, I will turn it over to you.


Thank you, Amy, and hi to everyone. So for the beginning, I want to give you a short, introduction about Trihydro for everyone who hasn't had a chance to meet us before.


Next slide, please.


You, so, Trihydro is an environmental engineering and consulting company, covering a wide range of expertise, including roadway design, traffic studies, in the deployment and development of transportation, New transportation technologies, such as connected vehicles, is part of technology, services, and solutions business unit. So, Trihydro started to work with connected vehicles in 20 15, between WY Connected, Vehicle Pilot Project, and, since then, we have, we have been focused on building of connected vehicle environments for different states and becoming a leading technology firm for rural connected vehicle technology.


Next slide, please.


So the reason why are we here is to speak about the broader connected vehicle deployment and how to help, to fight, to save lives in our roads. As I remember it is a reminder in 20 21 which is the first post pandemic here and it's still not totally ricotta. Traffic volume became the highest number of traffic fatalities for the last 15 years. Counting close to 43,000.


Based on data, this is available So far, ah, National Safety Council estimates that we could hit as high as 46,000 traffic fatalities in 20 22.


On average, yearly occurs about five point nine million crashes. They are about 1.2 of them is measure related.


If you're speaking about Work Zone traffic crashes during 2020, which is pandemic year low traffic volume, we actually saw an increase in traffic.


In work related traffic crashes and estimates from US. The US. Department of Transportation during 20 21 is emission increase. about 18%.


Next slide please.


So being transportation professionals, we need to use all available resources and tools to combat these numbers. So today, we definitely will speak about connected vehicle deployment and challenges that come with that.


We also will speak a little bit more about travel information messages, is a very important tool, connected vehicles to comment, and prevent, especially weather related traffic crashes. And we also will cover, in a few, CORVUS intelligent transportation system, which is our answer, in way, how we address those challenges.


During presentation, we also speak about the third party infrastructure and how we can use existing resources.


We also will give information about situation data exchange, and how situation data exchange and CORVUS can bring advantages in an address challenges for connected vehicle deployment. In the end we will do a little short overview of Architectural Design for both of those systems. Next slide please.


So, vehicle to everything, communication enables, enable us many safety and traffic operation, applications that could save lives and improve traffic efficiency, to exchanging data about road weather.


Um, traffic conditions, zones, timing, signal, timing, data, vehicle trajectory, data. And all studies that are conducted so far.


All those connected vehicle pilot project that we had.


show experience of about 38 states that had a chance to deploy connected vehicles, at least on some of their corridors.


We definitely can say that connected vehicles have been proven to save lives, and we need to start to deploy them, regardless of challenges that come with that.


So, today we definitely will speak about those challenges in our effort to address them.


In the first place, there is a very high cost to, to develop and deploy connected vehicles.


And that's additionally followed with a, lack of certainty in technology that is in your those.


So, we had to, speech from dedicated show change communication to CV two X.


We also experienced it used to benefit, so this will definitely affect many connected vehicle applications and messages.


And, I hope, we still actually don't really have a clear path interaction, that is, those issues. And I hope it to be, probably, we'll hear a little bit more, during ITs Conference, in ....


V2X Summit, that is coming in less than two weeks, but, besides that, there is also constant upgrades, updates, and changes in standards.


So, if you develop an application, you have to make sure that those applications are interoperable previous versions.


And having all those together, we have very low market penetration rate of connected vehicles on our roads and get in back in circle, a low market penetration rate, Again, additionally, slow down, further deployment of connected vehicles.


So, regardless of all of these challenges, we need to continue to work hard, and employ different approaches, to reach the goal of the broader connected vehicle deployment, and tried to change this direction. Which traffic crashes in traffic, both fatalities. And besides that, also, successful connected vehicle deployment is, is, is kind of foundation for automated driving.


Next slide, please.


So going in that direction, I want to stress a little bit more attention about travel information messages and the importance of travel information messages. Based on on the current CV two X application map policed that's developed by ITSM America.


Channel information messages or TIMS are on that list is a priority messages. And Department of Transportation recognized how important these messages are.


And the developed 5, 11 tool, just mostly even before connected vehicles and it's mostly used for cell phone applications.


It's also comes with some limitations.


one of them is that most of the drivers are actually not aware of that tool, and for drivers who are using 511. And if they're driving to different states, They actually have to log in a separate application every time, and if you don't have service, or if you're trying to do it to joining driving, lets me know very, very, distracted driving.


For drivers who are not even aware of that, they're relying only on lake GPS tools, which they are great in.


They are getting more and more accurate, but they are not providing travel information messages.


So, the development of connected vehicles, travel information messages, are becoming more available to our geo reference messages. It's, all right, tended. They're intended to inform connected vehicle drivers of station data.


And these TIMS are following all connected vehicle standards like J 2735, and they are encoded and decoded, based on international travel information systems. To ensure that all phrases remain interoperable between different, different type of user of user equipment.


Additional thing that is very important about TIMS is that they are following me at the senior standards.


And messages that we are, the drivers are getting in, vehicle, are already formatted in a, in A, in a way that is familiar to drivers you get used to see those signs around along the roads.


Next slide, please.


So, speaking about TIMS I want to draw a special attention about traveling environment in Traveler Information messages, the Field one drivers about changes in road conditions due to weather. Any changes any change can impact.


Driver capabilities can impact vehicle performances, such as stability in traction, videos, pavement frictions are similar, and especially here in Colorado and Wyoming, where we have a mentor about six months per year and we're here.


Road closures, snowing, blow, ice, snow, or similar daily events.


So having accurate in real-time channel information messages can help to reduce some of those one point two million pounds or 21% of total crashes.


They kind of happened because of the vendor, actually can save some of those 5000 lives that are lost in these type of crashes.


Next slide, please.




Now we have a question, how we can provide better, more comprehensive?


The Traveler information System is available statewide, that is not privileged, only, on our corridors that are selected for connected vehicle deployment.


How we can make it make TIMS available and accessible, accessible to drivers civic the minimum distraction during training and at the same time, affordable for states to deploy them.


Right now in how we can, it can use our existing infrastructure.


It is governed by the parties, how we can improve. The tool that's more more most drivers are found a lot like a GPS tools into get travel information messages.


Next slide, please.


So we recognize all those challenges and not only recognize they actually had to phase into and to our project, to try on being in other states.


And we developed, CORVUS intelligent transportation system.


In CORVUS reduces the crash, the deployment cost, and helps states to develop connected vehicle technology statewide using the existing infrastructure and engaging the power of third parties. while the same time.


It helps to create travel information messages by ingesting data from different sources, validating the data in creating, secure, and trusted TIMS.


Which is also important about Corvus, it is technology agnostic. So even now, ...


shutting down, and they're not operable, we actually have channel information messages along the entire WY state ....


Next slide, please.


What was the CORVUS and how it works?


Corvus is on interoperable cloud based system that supports vehicle to infrastructure communication.


It's capable to generate and create travel inflammation messages.


Information that corvus uses to generate teams originate from trusted infrastructure owners and operators. In corvus


It just simplifies connected vehicle messaging by formatting them encoding, in integrating with the existing security credential management system.


In corvus is seamlessly integrated in existing traffic management Software center software.


After messages get created, corvus delivers them to those type units network, and deposit them on Situation data exchange. We definitely will speak a little bit more about station data exchange later.


In Chrome SDX, All those messages are available to to third parties to disseminate them further additionally.


Corvus manages all locked in, messages by automatically removing them, updating or anything, TIMS on a given road segment.


Next slide, please.


What they're a major features of the CORVUS, corvus enables integration which will take units. It's also provide your units monitoring, They include network monitoring, different alerts and notifications at the display don't rotate units dashboard.


That CORVUS also have TIM management interface that support communication between TMC and CORVUS, and it's also support security. Security management system integration bit bigger Situation Data Exchange.


Next slide, please.


How is CORCUS integrated with Traffic Management Center.


CORVUS uses  client hosted, client hosted system that allows communication between the client. Client TMC and CORVUS was clouded. CORVUS cloud hosted an infrastructure that is controlled under under a consistent and sit and secure communication protocol and also support all requests to create, update or delete.


Channel inflammation messages in any moment is possible to obtain the status of, of all the current status of all active travel information messages.


Next slide, please.


Here we have an example of TIMS management. So it's possible to see active, active teams. Status of ..., status of integration bit is SDX.


In order to create message message, it's necessary to know type of message. In this example, is given adversary. The type of events, like here, it's a blowing snow. It's also necessary to have geo referenced area where the message will be broadcasted, as well as a timeline of bend, this message will be active. Next slide, please.


Roadside monitoring, or maybe better known as a CV manager, helps to track status of road side units. And even if they are receiving messages, or having any issue to each moment is possible to see if your roadside units working properly. If they're having any issue with network, if there have slow or failing failing connection, you didn't need to be rested, or maybe rested is already attempted, but still, something doesn't work.


However, in provide, very recent resources, before accrual has to go on the field and check those.


Next slide, please.


All right, Thank you very much Zorica.


So you just charge rates talk a lot about, then they fear that were, the reason why everybody's here days, obviously, trying to reduce the number of fatalities that we're having on our roads, and being able to learn how connected vehicle messaging could do that.


Um, I'm gonna really focus on first on the situation data exchange, what it is, and how it came about, then how it actually works to be able to not only be able to be a different source for distributing connected vehicle messages.


But also will reduce costs associated with connect a vehicle to climb.


How it also integrates with the CORVUS system that Zorica spoke about.


Um, first, I want to just give a little bit of background on what the situation data exchanges, and really, how it came about that, that started with, um, the Situation data warehouse, that was a system that was built out by the U S D O T.


That really supported a central data exchange, or a central repository, four connected autonomous vehicles to support a nationwide deployment.


Uh, while they use this to be able to distribute messages for satellite delivery of travel information messages onto its roadways for the, the Wyoming connected vehicle pilot project.


That project started with us being able to wanting to deploy connected vehicle messages for the entire stretch of I 80 that runs through Wyoming.


That's over 400 miles, we only had budget for about 76 RSUs.


Each of those ...


you use only has about a one kilometer range, so there was large gaps of coverage for our connected vehicle deployment.


In order to plug those gaps in coverage, we partnered with Sirius XM to be able to distribute those travel information messages over satellite using the situation data warehouse.


In 20 19, we're actually, U S D O T.


came to Y that, said, we don't want to support the situation Data Warehouse, uh, hosting, as well as development going forward.


So, try Hydro Stepped up.


Really a partnership with Wyoming, and later on, in partnership with the north-west Passage States, to be able to really build out and developed the situation, the exchange rate, really renamed the warehouse to the exchange, beef up the security at really look at extending the coverage for nationwide deployment.


Really, it is a central repository for CDB messages.


That includes works on data exchange, travel information message, the roadside safety message, as well as my passengers.


Or currently aggregating all of the WEC DX data feeds.


There are being that are currently available via the US DO Tea's website or Registry of WCBS feeds.


We're also being able to have distributors query and push vehicles.


So, Sirius XM is actually actively doing that.


Tom, Tom, some GPS map tools.


You can use any LTA communications, as well, satellite communications, to push these messages out.


What this allows us to do is to reach a much wider audience and address that market penetration rate that we're lacking right now, furred connect vehicles.


Uh, so, in addition to that, we try hydro really wanted to extend the coverage for our connected vehicle messages.


We approached Wyoming awhile back and asked them what were their thoughts on being able to get these connected vehicle messages out to the traveling public folks that are just on the road.


That don't have Adobe, you install it, as well as a display for these messages?


What was the best way that we could do right now to extend our coverage?


So we integrated and built out a Alexa traveler information skill and then deployed that out for essentially a nationwide deployment that integrates with U S DX.


Um, did that, mostly to support our traveling public, did that on try hydro's, um, we did not get funded through that for Wyoming or anything like that.


It was strictly because hydro sees the need, to be able to try to get this provision.


Next slide, please.


So, in addition to the situation data warehouse is, initial integration, or SD Access, international integration for the I 80 corridor.


We want it to be able to expand coverage statewide.


It worked so well on that I 80 corridor being able to distribute those messages that this Garcia came to us and said, is this possible to also get to all state Federal Highways in Wyoming?


So, we actually did that, and it didn't take us very long to do. So.


We went out and built out the road network for all of Wyoming, and then we're able to integrate with white dots TMC to be able to build our travel information messages and deploy those statewide.


So all of our connected vehicles for the pilot, we're able to receive messages on all state and Federal Highways, and that is something that any state can now do.


Given the SGX, and then the ease of use of building the tips through Corvus.


Next slide please.


In addition to being able to support those onboard units and the connected vehicles, we can now have third party applications like top top or sirius XM traffic.


Be able to use the same connect vehicle messages to display these messages to drivers in the roads, other online navigation systems.


We can also expand that to apps that can go through and retrieve this information.


Bill T.


Thanks, Theresa spoke to that a little bit earlier.


But so things like Google Maps or Siri, would be able to we built out proof proof of concepts for this.


Be able to build out messages so that drivers could see information on any roadmap.


Next slide, please.


I also wanted to touch on some current active development that we're working on for the CDX.


And the image that you see here is actually a problem that we've really recently run into with my dog where we're having GPS devices try to route drivers around road closures on Haiti and other interstate's, Wyoming.


This driver, there was a road closure between rawlins of rock springs.


This driver was routed around local roads, and as you can see, they did not successfully make it through those local roads.


So we're working with Wyoming to be and local counties in Wyoming to identify of cascading road closures for local roads and being able to communicate those local road closures, two, Google, as well as other GPS navigation devices, uh, that are routed these folks around the major inter-state road closures.


And then, we'll be able to build out connected vehicle messages, distributed those through the SDS to those drivers so that they are not routed around ID road closures or any inter-state group closure.


In addition to that, we're actually building out push notifications for that traveler information skill that I mentioned earlier.


So, any road closures, users can subscribe to push notifications so that it will I will essentially notify them then there is a road closure for a particular road segment, or they can also receive notifications when a road actually opens back up.


This just vacates the benefit to keep by hitting refresh the 511 applications website.


Next slide, please.


So, in addition to what we're actively developing on, we're also looking at additional capabilities for the SPX.


These include increasingly the search capabilities using graph q.l. support.


Graph q.l.


is a querying language that will be able to pull data, geographic, and otherwise, so that anybody wants to distribute messages, can query by message type.


They can query for specific geographic areas.


And it'll really be something that improves efficiency, as well as just our overall support for querying the SPX things.


Again, this is something that we see as, uh, something that we want to support nation wide, we believe that there is, really, a need for, a nationwide system for all, D O Ts, can push messages to add, we can pull support, prompt for a query.


It, also, we're looking for this, the SPX, as a communication hub for duties.


When I spoke earlier about the road closure or the Cascading road closures for road segments of Wyoming, that also affects other states.


So during that same IED road closure for Wyoming, we had some GPS navigation that would actually route users through local roads in Colorado.


So, there was also state rescue's for vehicles, Colorado, including freight vehicles.


I think I saw an Amazon truck getting pulled out of one snowdrift in Colorado.


Anyway, we want to be able to notify from state when, when a particular incident or road closure may affect other states, so that centredness of our communication so that, in the case of a ruck closure, then Colorado may want to do some other cascading road closures, as well.


We also look at are looking into being able to build out a Data Source lookup support for spam messages.


If you're not familiar, spot Messaging is essentially messaging dog at an intersection that will transmit information about intersections, friends, stay, and the timing for time to read time to grain, And the current state of the actual intersection, as well, as the plan for that.


Now, this can be very helpful to build, communicate out to drivers.


so that you can tell them of red light violation warnings, time to read type degreed, a lot of really cool applications that we can do there, But, it does require sub second latency.


So, got near real-time data, and being able to push that data up to the SGX, and then push it out to third parties.


We see it as being, probably, too much latency to be effective there.


So, we want to build a feature within the SPX, that allows drivers to be able to, or allows data distributors, to be able to look up, data sources forced back us.


So, if a particular intersection is broadcasting its data at a particular IP address, we can register that within the SGX, and then that driver can get pointed to the right direction to be able to retrieve that information and split it to the driver.


Next slide, please.


So, how does the ... system work?


Um, starting early with Wyoming, they wanted to build this support, building our traveler information messages, but do it in a way that didn't take any time from our TMC operators.


The TMC operators have a ton on their plate.


They don't have time to do additional tasks stood there.


So that connected vehicle, building out these connected vehicle that's just did. They could support another system or another task for their TMC operators to perform.


So we built out the API for those TMC applications to be able to integrate.


And I'll go into pretty much how the traveler information messages are built out, and how they're distributed here in the next few slides.


In addition to just traveler information messages, Corvus also supports the next gen of, uh, connected vehicle messages that are coming.


So roadside safety messages are pretty much the next generation of the traveler information message.


As that standard gets finalized, the support will be there for the court system.


Um, the Temp Management website to being able to actually go in, have a website where you can view all the traveler information messages or rotate safety messages in your state.


Having something in there to where you can review all of those as well as add new ones if you need to.


That's particularly helpful for static traveler information.


What I mean by static travel information passage would be something like a curve speed warning or a bridge height clearance.


So, you can actually add those into, are 10 management website for corvus, to be able to distribute that over the CDX, as well as your roadside units, and then integrate that for your overall quebecker vehicle messaging strategy.


In addition to the, what I've venture here, the corpus of the STA system both take into account security.


We, we believe that security is critical to the overall connected vehicle ecosystem.


Without it, you drivers will not trust the messages that come from this system.


And that is critical to the overall success of connected vehicle messaging and the deployments for that.


Um, so in addition to, when we took over the situation data warehouse, we built out additional security for the situation data exchange, only authorize dot Ts. And iOS are allowed to push data to the S DX.


Only correct, correctly coded and built out travel information messages are accepted.


And we also require the CMS integration as well, that CMS integration, so, for the security credential management system, we want to make sure that all the messages that are distributed from Florida's as well as through the S DX, our trust.


Next slide, please.


So, how do we build our tribal information message What, what goes into it. From the corbis side of things.


Well, we start off with location.


So that is your beginning and your endpoint for the path that you wish to be able to build out a message for your drivers for.


Next we look at timing. So, when is that message applicable?




What what are we actually going to?


When do you want those drivers to be able to receive it? How long do you want them to see it for?


So, in particular, the Some of those messages can be out there, persistent, like I talked about earlier.


So, you can have stuff that is consistently out there, or you might not know the end time for it.


So, you might want to be able to refresh that every extra minute.


Um, in addition to the timing for it, you also want to be able to convey what type of information. Right?


So in this instance that we're, we want to be able to push out a tab that has an accident, as well as traffic stopped, but this could be anything. It could be your road conditions.


It could be the road closure, it could be that there's an event, and you want to watch out for event, or heavy traffic, parking information, et cetera.


Building out the tab is what Corvus, it takes all of this information that the TMC application gives, it, builds out a roadway path.


And it does this, too, the smallest message size possible, because we need to have these messages, so they're super compact, they could travel over the air.


Next, we would, we want to look at building out the travel direction.


So that heading slice, that pie that you see there between the box at the bottom, really defines that the tribal direction that that traveler information messages applicable for.


And then, you also want to build out that message information that gets converted to ITIL codes.


The ITIL codes are really the heartbeat of what actually gets conveyed to the driver in the vehicle itself.


Then you put a start and end time on that traveler information message, you encode it into Uber coded J 27 35 standard.


And then from there, it gets signed by the security credential management system, and then to get distributed to either your roadside units, or the situation.


Next slide, please.


So the tip generation and delivery. So again, this is, this is just a different.


This is more or less the system diagram for the overall corvus, an SDA system, how it works with your drivers, vehicles on the roadways, two TMC applications, like your ATM SSD, a lane closure system.


So it could be any construction management system that you use any pretty much application, where it can phase critical information to drivers on the roadways.


We'll feed the data that I just spoke about previously, into Corvus.


So your start NetPath, um, the, the actual timing for it, as well as the message information, that gets pushed into Corvus corvus, that builds out those traveler information messages and distributes those, not only to the SPX, but also to the applicable roadside units, your network.


From there, the roadside units start broadcasting that information to any connected vehicles on the roadways.


And it also goes from the CDX side of things out to Sirius XM satellite.


Where we can broadcast those saved messages out of use that have satellite receivers are capable of receiving these messages through Sirius XM satellites.


Right now, compensate yet is actually building this out and integrating it, there will be use.


We hope that other ... manufacturers will also start integrating the satellite receivers in there to be able to receive the same messages split to those drivers and there will be use.


So in addition to that, we also have that third party application delivery, two drivers that have their sirius XM traffic in there, as well as the third parties, Like, here, your top Tom, an Amazon Alexa skill, I use that pretty much every day, especially in the wintertime, when the road conditions are bad.


There's a nice Amazon auto, Alexa Auto device that you can actually query to see road conditions between your location destination.


Next slide, please.


So, this slide goes into a little bit about the CMS integration.


It really is just talking to adding one extra layer here for the corvus that is talking out to the ISS, TMC authority, and that, that essentially signs are traveler information messages and distributes those.


So the previous slide goes over the overall process, this goes over, and adds that extra layer of security.


Alright, next slide, please.


So today's presentation really discussed a lot of different things, so went through quite a bit.


We talked about the CPU deployment challenges associated with that.


We reviewed what traveler information messages are, how they're used.


We also the crees, sorry, sorry, it spoke about the corbis Intelligent transportation System, what that is and how it's how it could be used to allow a deity to really rapidly come up to speed, with connected vehicle messaging technology.


We also spoke about the opportunities to leverage third party infrastructure.


And this is really important because it allows dot Ts like why not?


To be able to distribute these said, connected vehicle messages strivers on the world without having the burdensome investment, a lot of RSUs, especially in very rural areas.


Uh, so you can really benefit from that third party infrastructure system that's already in place being able to distribute your messages over satellite or LTE.


We also discussed the needs of benefits of the nationwide situation data exchange, having that one central source of truth that is trusted, and third parties can use to be able to pull that information, We see is critical for a nation or an infrastructure.


Then I finally spoke about, you know, sort of how that corvus system, the SD Access Parks.


Next slide, please.


So, what's nice.


I also wanted to touch on ... Vision.


We really do see that we want to improve the safety, security, and mobility of our communities through Advanced Connect and autonomous vehicle messaging systems.


It's one thing that I'm really proud of. Working with tri hydro.


They see a big investment and a commitment to our communities.


Safety is always key for us. Want to see all of our employees come home.


Well, at Wyoming is one of the worst places for road conditions and, uh, in the nation.


And I know there are other states out there that have a lot of really nasty Brode conditions.


So we want to be able to make this affordable, as well as support any state out there that wants to come up to speed on this technology.


So, we're looking for, sort of volunteers in here to be able to help us out with some pilot programs.


We'd like to evaluate your current TMC system and see how quickly we could bring the court system and integrated with those.


As well as, you know, integrate with the DSD system as well.


If you already have a system in place that's able to generate these secret messages, we can just, you know, keep straight up with going straight to the S DX.


Um, Let's see, Based on, I think the TRP conference put it really well.


When they would, they really wanted to push for 2023 as the year of deploying connected vehicle technology, um, we would really like to see more and more states deploy this as well as be able to support CVD technology as it becomes more available to vehicles on our roads today.


So, with that, I think if you go to the next slide. You know, thank you very much for attending.


We really appreciate it.


Be happy to answer any questions that you may have right now.


So, yeah, I'll hand it over to Amy Chicken to show a question to ....


Great. Thanks so much, Shannon Sarita. Now let's move on to that Q and A. We just referred to. remember, if you do have questions, make sure to put them in the questions panel in your goto Webinar Attendee panel. Shane, and sorry, that we did have a couple of questions. The first one is, Has there been co-ordination with OEMs to get the system integrated into vehicles?


So that's a, that's a great question.


So we have had discussions with the, with Chairman General, being able to support there, traveler information message systems.


And I know that GM has on their roadmap to be able to push tribal information messages and display travel information messages in their vehicles.


I believe don't quote me on this, but I believe starting 125, those models will be coming out with that Tim Support.


We have been actively working with them to be able to bring them up to speed on how to integrate with U S DX, and what benefits that provides, as well as being able to push those messages, not through just an Rs two but through that access.


OK, next question: How could a data consumer benefit from using SPX?


on the data consumption side of things?


Not having to aggregate all of the data out there, or having to look up and find out where to be able to aggregate information.


Instead just pulling all of that information from one trusted source is really what we see as the future for D S DX and being able to support those data consumers.


We also want to be able to integrate directly.


So if a data consumer hasn't need to hold data in their particular format.


The SPX also allows us to be able to do some of those tasks.


So, if a data, if a data consumer relies on, say, the WCAG version four point, no.


Um, and we have a bunch of different data sources for four, but some narrow 4.1.


Uh, we can actually, convert from one message format to another, and be able to support that for your, uh, for those data consumers.


She makes it easier for them.


Great. How can ... be applied in an urban network?


So that's a great question as well.


So corvus is, is not strictly for rural rural areas.


In particular, Wyoming is a very rural area, and it's being used for communications out, mostly for road conditions, but urban areas can really benefit from connected vehicle messaging and integrating with four of us.




Pushing out messages for current road conditions out on their roads, if there are wildfires out there, if there's flooding, and you need to inform a large amount of drivers, as quickly as possible, then, you know, that corvus system, along with the SDA Acts, really helps with that.


So it just, it just benefits not only the rural, but also the urban areas.


Um, I think we have time for maybe two more questions. Are there any limitations in the data quantity that could be ingested consumed by S DX?


I know that, I think, as I mentioned earlier, the HDX is built out to be massively robust.


We have built the system, so that's cloud hosted.


It's an Azure.


We have the ability to be able to query, as well as hold a massive amount of data.


So from that perspective, we have no limitations on how many messages we get. How many we actually get distributed.


OK, so looks like last question. Can any of these solutions be used for applications like red light, violation, warning, transit priority, or something similar?


So that's great question.


On the corpus side of things, it's really meant or connected vehicle messaging, including that traveler information message that can be used in conjunction with, so you essentially need to push out, vary or a speed limit, travel information message as part of the red light violation warning.


So you can calculate whether or not a driver is going to violate that red light based on the current vehicle speed, the speed limit, as well as when that light is going to turn.


So, from that perspective, it definitely supports red light violation warning.


For transit signal priority, not so much, that's really reliant on that spot messaging, as well as the SSM SRM, are signal Service Requests as laws, stigma, status, message, um, so, those, so, as far as the transit signal priority, no, but definitely for other applications, such as red light violation.


Right, well, I think that wraps up our questions, that have come in, and keep in mind, if you do have additional questions, please be sure to fill out our exit survey. There's an opportunity in there to request a one-on-one time with our experts to answer additional questions, and discuss your state team needs also. Please be aware that a recording of today's webinar, along with the PowerPoint slides, will be delivered to your inbox in the near future. Thanks so much for joining us, and have a great day.


Thanks, everyone.


Thank you.

Did you find this information useful? Click the icons below to share on your social channels.

facebook twitter linkedin
Other News


Receive the latest technical and regulatory updates in your inbox.