Transcript

2:00 AM. And I was like taking an inventory of yesterday. I was thinking about all the cool things. Flow actually absolutely slated, like really slayed. Konoa their MES software is pretty crazy. The fact that they're able to do as much as they can in eight weeks. It though, like some of the workflows, I think the learning curve is going to be pretty steep for new people because of some of the work flows, especially on the that quality module they have. But it was definitely impressive. They did like a whole plant in eight weeks. Yeah, it was a long day. We're going to get a little more technical this morning. We're going to talk about distributed systems and containerization and yes, we will talk about AI. So let's get into it. We got a lot to cover this morning. Of course, it starts with ignition in this case. It also continues with Ignition. It is incredible to see the journey of inductive automation from where we were at the very beginning to where we are today. I came in, luckily, the very beginning of the company back in 2004 and when we were just a few people and you know, our mission was simply to, to break down barriers and to ultimately solve challenges for innovators, right, and make their lives better. And it's that that mission, that belief has really. Transformed over the years and it's great to be here at the Safe Credit Union Convention Center where we've really expanded ICC to a bigger new venue with doubling the amount of people that have come here and just see the impact that ignitions had around the world. Because all we want to do is help make customers journeys better and easier and to give them the right tools they need backed by a good company that could support them. And one of the things that you everyone should be thinking about, as ridiculous as this sounds, you know, I was telling inductive automation the other day, inductive automation has something no other platform. Has like literally 0 platforms have and that is at least 17 years of experiential knowledge in in in industry 4. With the same team. Like it's unheard of. Like Coby, Karl, Travis, Vanessa, Bobby, all that whole team Steve, They've been here forever. People come here and they die here. Like and that and that's a good thing, not a bad thing. And inductive automation should sell that. And what is it? What is it they're selling? They're they're selling knowledge. They're selling data is knowledge. I absolutely loved to see Walker in person. I've been following him for a few years. I finally did one of their mini sessions, their twelve week sessions, but I was honored to be there and learn from all these different software and hardware suppliers what they're doing to completely. Digitally transform our industries and his mission in life to, you know, transform manufacturing and build middle class jobs. I love that, right? Become more competitive than we've ever been. Something that I really appreciate that Walker does is he's been doing digital transformation engineering honestly for a while. And so what's cool with the sessions is he can go up and add technical commentary, like, OK, I know the problem you're solving. I remember when I used to do it. And I can contrast it to how you're doing it now and kind of explain to the audience, This is why what you're seeing today is so innovative and so groundbreaking. And I think that he adds a lot of value to the audience members in these sessions. So that's been really cool. One thing that that I have seen here, I like to see maybe more of is integrators getting involved with the vendors to kind of build bigger and better solutions. And I think we had a couple of sessions, approved sessions where we as integrators help build the build those solutions this year. But ultimately, it would be pretty cool to be able to see an architecture. You know, built out from scratch, right with, with all the different tools and layers and see the benefit that it brings all the way through, right? So you can see it full circle. So there were three major announcements in the technical keynote. And basically distills down into three items. So composable architectures #1 composable is is like going to a text editor and then writing out a composition that instructs the software how to build itself. Composable projects is number 2. So composable projects is not just building the architecture through text, but being able to manipulate projects through composition. Third piece obviously was the announcement of the MCP module. That is an enormous deal.