 It's a privilege and a real pleasure to participate in this and I'm, you know, of course saddened that there's no motor show to go enjoy and mingle with with folks on this and I'm, I'm glad to see the slide up here is being shown I just have one little slide to talk about. And that is to sort of set up perspective of the, the, the current situation, this is how standards are currently done, but it's is also modern as not too traditional. And I'm going to step through it briefly, and a bunch of probably overworked volunteers come together. And a lot of them as attendees here today have dedicated a tremendous amount of effort and technical capabilities to producing these standards, they get together in various topics. Sometimes the topics didn't even exist prior to when they come through them such as a field of micro mobility, didn't even want to call them but a group was formed. And they did it voluntarily based on some motivation, motivation in the beginning of SAE was on safety and productivity, and it's pretty much still the motivation in a non competitive manner. And inputs, you know whether they be a heavy goods vehicle manufacturer micro mobility bus coach, or or their specialist in certain cross cutting areas such as systems engineering or hardware in the loop, whatever. Or, or some groups came together come together as consortia or cooperative research or funded programs and work on a standard in an uncompetitive manner. And perhaps we can talk about the panel some more but with safety is highly competitive. So there's a balance in there, and then the standards. And this slide just shows that they go support various national local regulations, and they support the even WP 29 the ITC at WP one. They're paired with with ISO IEEE other SDOs, and they ultimately go into GTRs or regional North America rags or the 58 agreement, perhaps, and they get into product, of course. And I want to say that they're at their consensus, and they're voluntary. So not only is participation voluntary by by by the experts, the adoption is voluntary, however, it still is a very good practice to follow them. And I think that maybe another point in the panel discussion of what is a policy of a good practice versus something that may or may or not be in a regulation. The last thing I want to say is a time. And I, I think back to a very highly competitive project I was privileged to lead. She's 22 years ago and that was the heavy goods vehicle, and it was called role stability control, we actually took control of the driver away. That's the point when the vehicles on board technology considered that this combination heavy goods vehicle might roll over. And we took control over momentarily. It may have seemed like an attorney to a driver back then a second or two where where the machine to control over the driver ability to steer and deliver fuel and break all three functions. And on the tractor on the power unit and on the breaking of the trailer behind to put that in perspective that took about four years to develop that to validate it to use a term use in our be mad group to validate it there were no regulations in place other than the brilliant motor vehicle safety act that said regardless of what regulations are in place to product better be safe. It took about four years back then a gigabyte of data cost 1000 euros. That was about the timeframe I started when the year came into being put in perspective. Right now, from a metric perspective. And I say the I just looked Friday or the average time to from inception of work in progress to a published standard for the heavy truck group is about 13 months at SAE. And that's still an eternity. When I think of, I can probably can't even count the number of software updates I'm offered on my iPad in 13 months. I want to I want to close with that difference of a four year development from perhaps some people might consider something very trivial 20 years ago of stability control system. And with data costing me then 1000 euros a gig and my boss thinking I was out of my mind. What do you need that much data for data collection for doing developer. And then now. So thank you again for this privilege and I look forward to a lively discussion.