Video: Envision Builder Foundation Preview | Duration: 2992s | Summary: Envision Builder Foundation Preview | Chapters: Introduction and Welcome (0.16s), Interactive Poll Results (205.705s), Polling Time Insights (545.14s), AI-Assisted Authoring (711.44s), Assembly Sequence Creation (1378.42s), Multilingual Instructions Creation (1710.385s), CAD Updates (2078.45s), Foundation Program Launch (2416.185s), Pricing Editions (2676.78s), Application Process (2795.54s), Early Access Signup (2827.85s), Q&A and Closing (2905.74s)
Transcript for "Envision Builder Foundation Preview": Yeah. Maybe we can add some. I don't know. Alright. Looks like we're going live. There we are. Alright. Well, good afternoon, good morning, wherever you might be. My name is Garth, and I'm here with Alban. Say hello, Alban. Hello, Garth. Hello, everybody. So we've got a... An action packed agenda for you. So I'm gonna, let's see. Alban will will shuffle you off here, and I'm gonna go in and and share my screen here. What we're gonna do is we're gonna go through a a short introduction and then spend most of the time in our new product, which is called Builder, and it's not yet released. I'm gonna be running it on a a dev server. So, we you will see the performance, as as it is there, which is actually pretty good. And we'll go through a couple scenarios. So what I'm gonna do here is, this should work. I'd navigate my slide. Alright. Good. So we're gonna go through this. This is a prerelease product. It's not yet released. And then the question is, of course, why are we doing this and what is it useful for? And when you look at knowledge in your company, when you are trying to go from the people that have the expertise, taking the things out of their brain and their knowledge and know how, and getting it into a trusted format that can then be delivered to someone who needs to do the operations. That trusted format has its data, yes, its processes, yes, but it's also the work instruction. It's the thing that tells people what they need to do. And all too often, in fact, pretty much everywhere for decades, this is manual. How does it go together? What should you do first, second, third? All the information around that. It's a patchwork of tools. It's a lot of manual effort, which means, of course, when there's a change, you've gotta redo that effort, take screenshots, rebuild things, and so on. It is a colossal challenge, and then you think of larger companies that have multiple sites, multiple people, multiple authors, multiple operators. How how do you keep a standard, and and keep up with the pace of change and the pace of innovation? And, of course, a lot of those experts are getting scarcer and scarcer, and it's really two sides of the equation. One is the knowledge that needs to go in, and that's a scarce expert that you need to do lots of other things than copying and pasting into a document. And then you have the expertise on the other side on the floor, which is usually making up for the crappy instruction because of their expertise, their workarounds, their their their tribal knowledge, the things that they figured out how to do. And as they leave, what hasn't been captured that should actually be in the document of the instruction, but no one has time to do that. And this is really what we aim to solve, because this is days, weeks, months of effort using decades old methodologies. And here we are in the age of AI where so many things can happen. We have so much automation. We have so much, digital technology, model based technology, and yet you throw that all away and go down to squeeze it down into a pay... A paper or a PDF. This is insanity, but we have a new way to do this. We have we have a way that I'm gonna show you that we can solve this problem finally after decades. So just to see where everyone is at, I'm gonna open up a poll here. It should come up on the side of your screen. You have me over here, and if you kinda go that way... No. That way. I'm trying to look at my other screen. You go that way, there should be a button there that says poll. And if you take a look at that, it's just basically saying, like, what... What's your biggest challenge when it comes to work instruction? What what thing is it? Is it the build order? Because that that takes expertise to figure out how to build this thing. Is it keeping it up to date? Is it multiple things? You know, which which one or ones is it? So go ahead and and submit that in. I'm gonna take a look as I'm watching here. See some votes coming in. Alright. I will close that poll, and let's see what the results are. Not a lot here. I think we're we're kinda going fast and furious here, so maybe not everyone's in here yet. But, we can see here that there are some percentages, and it looks pretty even. That's not even showing. Looking at my other screen here. Alright. Build order is important. Writing is important. Keeping up the date is important. So there's... It's all important, basically. All these problems exist almost simultaneously, which makes it difficult. Right? Because now you have to think about what is it that you're going to do to solve these things, and can you solve more than one at a time? And with builder, you can. So what we're gonna show you today is how we close the gap with Builder. There's three modes in this product that, you can use. First one is if you're using three d CAD data, you can use that to build your sequence. And you can build that with the CAD structure. You can build that with the manufacturing bill of material. You can... If you already have some process plans, you can use that as well. If you have existing information that's being used, you can use that as context. And, of course, AI can also help you do this and automate this for you. Once you have the structure decided, and I'll show you how this works in an interface that's super easy to to to manipulate, then each step needs its corresponding instruction. And we've created a very modular architecture here in these steps, which has blocks on the page. So I can have a three d block, video block, text block, tables, note notices, all kinds of things that will basically give you what you need to convey that instruction. Of course, when you're using the three d, that is then tied to the build order, which is tied to the annotations you're doing. And if anything were to change, you can maintain that going through. And that's really where the power comes in when you stay model based, the ability to change and modify and update and revise or apply to a new configuration or a new product line and take all the work you've done and reuse that, reapply it, and use AI to do that and help you out. This is really what we can do. And it can run stand alone, but it gets even more powerful as you start to connect it. You can connect it upstream to PLM where that information resides and becomes your system of record and and the ability to connect and automate, be part of change orders, impact analysis for those instructions. You know, imagine today, you have a PDF with some screenshots. Where are you managing all that? When engineering changes, does anybody know what's impacted? When is it gonna roll out? When are you gonna publish? Did it get published? Which version of the CAD was used? With which version of the instruction was used? With which iteration on the floor and operation was done? Do you have that trace record? With builder, you can because you can connect all these things through, and now you can audit everything that's going on and keep things updated. So we can get to this fully connected solution. We can embed the instruction anywhere it needs to be embedded in your systems. So that way, the operators have a super easy way to work and stay connected, and you have the full digital thread going all the way through the floor. Naturally, what I call first mile to last mile. So the first mile is knowledge in. This is your expert, your manufacturing engineers, your people that know how things go together, that are figuring things out. We help make them be way more productive. But even beyond that, we allow you to capture that... Their knowledge, put it into context systems, put it into knowledge bases, and then allow the AI to be educated on how that works for you so that a less expert person can derive those build sequences, create those instructions with expert coauthoring assistance. So now you are not just making experts more productive, but you are multiplying their expertise into others. That's the first mile side. Of course, now you have a trusted, governed, high quality instruction that is configuration specific, version specific, delivered to the floor, and this is now something... Because it's a higher quality, it means you don't have to be as expert to get the knowledge out. So now you're having turnover, new people coming in, people that like to have digital instructions, people that like to engage, play a part of a video, go into the three d and look at it. You have all that capability now, to get that knowledge out. And this is really for us as a as a mission is helping you execute against that knowledge for your people that are doing that. So I wanna take another poll here, and let's just see this one. It should pop up again. This is really a question of how long does it take you when you have a release design? Now you gotta go into the work instruction, and create the build sequence and your build process and routings and create your instructions, put those somewhere, and begin to execute. How does it take you to do that? Just just out of curiosity, just to see, the time that it takes because there's massive opportunity here, I believe, to shrink that down and make it a higher fidelity thing, which then also helps with things like reduction of errors, reduction of scrap and waste, and and, you know, improving onboarding time and so on. So let's see, how those votes are coming in. Let's see. You have a couple minutes here. Alright. So let's see what we've got, a few days, nobody. So more than days. We're talking a week or so or longer. Okay. So there's something a little more complicated. Maybe it's gotta be broken down into several works... Work instructions or sub instructions, go to final assembly, and so on. That's a lot of work. So sometimes not even one instruction. It's many. It could be dozens, hundreds, thousands of instructions that need to be created across many, many people. So this, again, is where we try to help resolve that. Let me do one one more poll here. Just out of curiosity, if the best person on your team that is doing all the building of these instructions, of the sequences, and so on, if they left, they retired, or they left for greener pastures, wherever, how much of what they know is evaporated from your business? Is it not a big deal because it's well documented, or are you relying on them a lot? What's what's the impact, let's say, of not having that person? I'm not talking the operator side. That's a whole other impact we can talk about. I'm talking on the expert side of the authoring side. Okay. So this is, yeah, I don't know why that's not showing a full... Well, okay. About a third are saying we'd rather not know. Okay. And we've got a few that say, maybe not so bad. Okay. That's good. So in this case, it could be much more about time savings for those people. And, okay, some are half. That's a problem. We can help resolve that. So... Alright. Let's, let's move along and get into a couple of things here before I jump into the demo. So when you think of having a system that has built with AI at its heart, it can't just be all AI. You have to have capabilities for, an author to be able to do the authoring. But the AI is there as a as a authoring assistant, as a copilot, a coauthor, which you are guiding. You're letting them do all the mundane stuff you don't wanna do or take too long to do, like doing batch changes or figuring some things out or translating text, you know, that kind of stuff. So you really put the AI to work, but you are guiding it. It's a human guiding the AI. So let the AI do the work, look at all the existing documents, propose something, and then you go through and say this is good, change it, or you go ahead and change it. So you have to have an application stack that can be used by someone, and then you allow AI to help kinda augment that person. And that's really where you get a lot of really interesting, intelligence, let's say, in terms of applying your know how. You as a person can apply your know how, but you do it. But if you wanna replicate that, you capture your knowledge, and you you use that to guide the system. So instead of it becoming like envision builder, it becomes your company's builder because it gets a knowledge base. It gets context. It gets memories and skills and understanding of how it works for you. And then, of course, from all of that, you build the instruction. And here's now where we've got some secret sauce that allows you to go from the build order into an instruction, you know, exploding things, moving them, labeling them, having AI help you kinda build that out. That's really where we're using AI in kinda both those modes. So the idea is to convert that knowledge and expertise into execution through instruction. Okay. That's enough talking on slides. Let me go in and and and show you a, a demo. And where am I on my screen here? Okay. I'm actually going to hide myself so that, you can see the full screen. I'm just going to disappear. Okay. There we go. So what you're looking at here is Envision Builder. And when you start your build, you... I'm gonna do it from from three d, but maybe you don't have three d. Or maybe you have legacy videos that you've used for training or PDFs, SOPs, or previous work instructions. We can pull those into and have Evie, our AI assistant, read those things, watch those videos, and understand what's going on and convert it into a step by step instruction. Because videos are not instructions. Well, there are instructions, but who the heck wants to scrub through a ten minute video to find out that they missed something? Right? You need it to be step by step. Step one, do this, verify. Step two, do that, verify. So we can rip those videos up into the steps and sequences. We can take, you know, your your user guides, your manuals, your maintenance manuals, whatever they are, and repurpose them or find the things in those manuals and extract them out into the instruction. So we can do that and, of course, from three d. So I'm gonna start from three d CAD, and here, it's... This this is gonna be... It's a it's a fan assembly. Oops. If I could spell right. And here, I'm going to import the CAD file so we can support all kinds of CAD formats. I'm going to, this, I think, is a SOLIDWORKS, it's a SOLIDWORKS file. And what's gonna happen here is this file, we need to convert it because, obviously, we're not gonna go into SolidWorks or CATIA or NX or whatever tool. We're gonna convert it into a very lightweight secure format that is optimized for web. This is a web application. It's optimized for web. So what's gonna happen here is it... It's uploading it. It's going to do the conversion. It's gonna throw throw it away. We don't keep the cat. We just convert it. And then it's going to ask me, what do I wanna do? You just... You're just giving me some CAD data. What do you wanna do? So first, let's just decide which way is up and which way is front. That makes it easier as we build this to navigate, and we'll apply that. And now it's saying, alright. What do you wanna do, man? You wanna assemble, disassemble, maintenance mode, and so on. So I'm gonna do assembly, which is step one, do this. Step two, add this. Step three, add that. Disassembly is the other way. You're starting to take parts off. So click a part, and it moves off. Another step, it moves off. Maintenance is another interesting one. I'm not gonna show you that here because it takes a little bit longer to go through it all. But the idea of maintenance is there's a part down in... Inside this thing, and you gotta remove all this stuff in front of it. So we actually can use AI to to pull all the pieces off. Then you're gonna do something to that part, some operation you're gonna do, but then you gotta put all this stuff back. Right? And because we know what you took off, we can make sure that you're putting it all back. We can reverse the order. And if you were to say, actually, as I'm putting things back, I'm gonna replace this cover with a new cover, then we track this old cover is being discarded, new cover coming in, so you never lose any parts in that, and you have a proper, legit instruction. So that's maintenance, but I'll do assembly. And here we can have AI propose an order. In fact, if I do that, I'll... Actually, I'm gonna do this after. I don't do this right now. I'll do it after. I could build it by hand. I'm just gonna say do nothing. Because what I wanna do is I wanna just show you this screen here. This screen is the, canvas. It's the interface for you to work on. And I'm just gonna go here and say, you know, I could do text, three d images, videos, drawings, and so on, data capture. I'm gonna do three d, and there's the model that we just brought in. And, of course, I can do other things and text and notices, but I just wanted to show you this. And, of course, we can edit this three d. We can kinda zoom in. We can we can, you know, get all the properties of things, and we can change colors, and, you know, we can translate and label. We can do everything you need to do to to document what the heck this thing is and what what I'm gonna do. So that's just standard kind of three d editing type capability, but that's not the interesting thing just yet. What I really wanna do is propose an order. So if I go here into the build order, what you're gonna see is a whole bunch of parts here that are red. You say, why are these red? Because right now, these have not been sequenced into any steps. They're all unsequenced. There... None of these have been consumed into a sequence. So if you were to do this, let's say, manually, which we're not gonna do manually, but I'm gonna show you, you could say, you know what? These two parts here, that'll be in a step. These two parts here, that'll be in a step. These parts here, that'll be in a step. And I'm starting to build up the step. And you see it starts to colorize this for me, what... What's coming in and when. In fact, we can change the visibilities here. We can start to, let... Let's say, ghost things and hide and show and and all kinds of stuff. So now we can kinda see, like like, what's happening on these steps. If I wanna reorder them, I just reorder them, and so on. So, of course, I'm not gonna do this, and this will probably... We'll be here for we'll be here for a while as I try to consume all these parts or either say this isn't in scope for this build, take it out, and so on. I don't wanna do that. That's gonna take too long. What I do wanna do, though, is propose a sequence. So I'm gonna go here and say, hey. Propose an order. Let's just do it at the top level, and I'll just do it from the geometry. You know, whatever I got from CAD, go ahead and propose. Now as we know, CAD is really not suited for building. Right? The CAD is there, but it's it's really not the best structure for me. I would never build it this way. Maybe I get lucky. I I don't I don't wanna use the CAD one. So what I wanna do is, use the manufacturing bill material as a better step, as a as a better first pass on that. So I actually have that. So now when I do a proposed step, what I'm gonna do is I'm gonna use Eevee. And now I'm gonna, in this case, upload my, my bill of material, my m... My MBOM and the part information for that. And I'm just gonna say, recommend a step sequence based on the bill material that's attached here. K? And go ahead and propose. Now imagine if you were to do this yourself, how long would this take you to do this? It's how many parts? It's only 65 parts. It's not a big assembly, but even 65 parts, you're gonna create, what, 30 steps or so, depending on how you're building your fasteners and moving things around. Even with the stuff we have to make it easy, it's it's probably gonna take you twenty minutes, maybe, maybe ten minutes. Depends. You know? Why do that when... This is twenty twenty six. It's AI. Right? I can have EV look at all of this, look at all the part information, deduce what's going on here because it's looking at the at the CS Visa uploaded. It's looking at the CAD model that's in here, and then it's gonna go in and say, you know what? This should be the order. It may not get it right, but it's probably gonna get it 90%, 95 right, and it's only gonna take a minute. So just as I'm talking here, it's just finishing up. It's just grouping the parts into stages to make a logical build sequence, and then we can take a look and see what it did literally after a minute. I could have gone and got a coffee and come back and it'd be done. So once this is done, now we can... Basically, everything will be sequenced because I told it it's gonna put that all in in scope for the sequence. And when it's done, it's gonna do that. Now here's where it gets interesting. If you had more knowledge of, hey. Typically, we put this part on last. Or when this part comes in, we need to have a warning. Maybe there's an electrical hazard, and we wanna make sure that there's a there's a step in here about prepping, lockout tag out or something like that. You can put all that type of knowledge in, and EV will consider all of that as it's building out the sequence. So let's see what's happening. It's a dev server. So, normally, it's done by now, but we'll give it a couple more seconds here as it finishes up. And once we review that, then we'll go into the next step, which is building the instruction, which won't take long at all. So literally in less than half an hour, we're going to end here with a full work instruction ready to go. That's the goal. Anyway. So what's happening under the hood here is there are several AI agents working. There's the AI agent, which is... It's all Eevee, but Eevee is... AI agent has taken the instruction, interpreted my intent, turned that intent into a set of tasks to do. So those tasks are now saying, you know, you've gotta look at this. You've gotta do that. You gotta read this Excel or CSV. You've gotta look at the model. So it's kinda breaking that up into a bunch of different tasks, and then those tasks spawn actions to go do. And then they return back, and then sometimes it's like, okay. Now we gotta create steps. So it will use code inside of Envision Builder to create those steps. And, this is taking longer than it should, live demo effect. All about knows we did a demo this morning on this exact same model, and it literally took sixty seconds. So it's doing some checking here. Here we go. Now it's done. Alright. Live demo. Alright. Let's take a look. So, again, we can control how this how this views. So I could say parts not installed yet. We could ghost it if you really wanna see where they are, and... Or maybe that's getting a little messy, and I'll I'll hide them. So it's gonna start there. Then these parts come in. Then this piece comes in. Okay? Then it's putting these, these, I guess, cartridge heaters. Now it's wrapping them, and it's kinda adding more pieces. So far, so good. I don't mind this. Then it's putting these spacers or brushes here, then it's putting those in. Alright. This is a good order so far. Everything is kinda stacking up nicely. Putting in the spacers, that's good. Then the fans come in. At some point, we... It actually also brought... You know what? Let's let's put these, as their own step. So I can just pick those and say just create a new step for those. So then the the... These fasteners will come in kinda on their own, and then we'll continue continue. Okay. That... Maybe that's gonna be hard to do with this in the way. Right? So that probably is something I'm gonna wanna change. So we'll get to that one in a second. But... Okay. You know what? Pretty good. So I'm just gonna take this part and this part, and you say, okay. Where should it go? Well, what I can do is using just my keyboard, I'm just gonna scrub with a with a couple of keys, and I'm gonna... With these highlighted, I'm just gonna back up the assembly. There. I want them right there, and that's where they are. So now those are coming in in that step. In fact, I could move them maybe one step before that if I wanted to. We'll just move it. We'll move with that step. We'll put them with that step. There. We just moved them. So it's it's that easy to do stuff. Now, also, if, if these pieces... If I wanted to have them come way up here, which would be kinda dumb. Right? You know, they're sitting out in space. So you can easily just drag and drop. There's a bunch of different ways for you to go ahead and and make that work. So now we've got the build order that we want. Now you need to make an instruction. So the first part of the work is done, how to build it. Now we gotta explain to someone else how to build it. Now we're just gonna hit the done button here, and now we're gonna decide what layout do we want. I got ones that I've made. There's standard ones we can do. I'll just choose the standard one. And here for direction, do I wanna have an ISO view standard for every view, or do I want the the system to determine the best angle because some parts are behind, some parts are on top, some parts are in the front? So I'll let it decide. And then motion, I'm gonna have it actually explode the fasteners and the parts on each step and and make some offset lines. And here, I could have EV write the steps and sequences for me. I'm not gonna do that right now. I want you to see how this works without AI, and then I'll have EV do some extra work for us. So I'll hit continue, and you'll see it's just gonna build all those views on that layout already done. So now my work instruction has pieces in here. So you see the explodes have been done for me. Now this one, I'm like, that explode actually went in the wrong direction. So let's go ahead and do that. And I'm just gonna grab those guys and move them this way. Put them over here instead. There. Okay. That's fixed. And, actually, you know what? I kinda like the look where, these kinda go in like that. Alright. Good. The other thing too is I don't really like this style. This style is no good. I don't want this blue and all this kinda stuff. I don't want red leader lines and things like that. I don't want that. So we actually have different styles, and I actually have another style here where the the headers are different, the styles are different, and I'll just apply that and it'll redraw it all. And you'll see now it's getting more to the standard that I want for this one and so on. So it's it's gone in and done this, and it's like, you know, maybe it's good. Maybe I like it. Maybe these washers really aren't going the right way because, you know, that's technically correct, but it's not really the way I wanna do it. So we'll go ahead and and just change those guys just a little bit. Right? Piece of cake. So there's a little touch up I can do, but this is way easier to do than to do the whole darn thing. Right? And and let's go ahead and label one of these. So bottom line is that you're starting to do this type of authoring. Now what I'm gonna do is on this one, I wanted... There's miss... Something missing. Right? There's no there's no text. So I'm gonna ask Eevee to write the text for a technician, and it can do stuff. I'll say here, add a data capture step here, which it may or may not do that here because it's doing a whole bunch. Let's see if it does it. And now it's gonna go and look and say, what's happening here? You're adding a washer. You're you're doing some stuff here. I could actually have ED do some more labeling, change some colors. Whatever you would do as a person, you can ask AI to do for you. So it's gonna go in and decide what should that text be. And if you had other documents of instructions you've done in the past, it could use it as a reference. You can create a glossary of terminology that you'd wanna use. If there was a specific component and you had to put a warning, it could do that and automatically write the warning. This is really where now you can do a lot of AI intelligence to to make that work. So we can see that it's it's starting to... You'll fit this here, and it's it's creating links to the parts, and so on. And it will finish writing the step. In fact, you know what I really wanna do? I'm gonna say, can you add another text block that puts this in Spanish? So why not do a translation while we're at it? And, it will then add the the the Spanish text. Of course, I don't speak Spanish, so I would want to then take this and do a review workflow. Because up up in this top right, there's a review and publish button where I could say, send this for approval, pick who I want the reviewer to be, and they could go in and and do that approval. So now Eevee is saying, what do you wanna do? You wanna stack them on top? Do you want me to narrow the three d view to put the Spanish text beside the English, or should I move... I'm gonna move the parts table. And you can see how Eevee can even manipulate the page to to get things done the way you want. Of course, if that layout is good, I could save that layout for the future and say, hey. This is my bilingual layout that I wanna use, when I create my instruction. So Eevis now is just gonna go in and actually didn't even have to move it because it made it work. So I don't speak Spanish, but, hopefully, that's reasonably well or or close enough for someone to make a few minor adjustments. So that's just how we can quickly go in and start to annotate this to create the instruction. You'll notice also because I was using Eevee, there's a little icon here. This is basically telling me that I have to review this. Anytime AI is making a change, a person has to validate that change. Or if someone were to change the build sequence, we would need to verify, you know, if a part was moved, maybe I gotta change the text on this page. So pages get flagged for for update, for change, and whatnot. Of course, what's interesting now is, you know, let's say these bolts are being put here in this step. Well, again, if if I were to reorder this, obviously, those things aren't there. Actually, in that case, those things are, but not going anywhere. And then down here, we no longer... We have the bolts. So all of these all of these views understand what comes before, what comes after, and it's very easy for you to to manage and and manipulate that. One thing I wanna do here is... One last thing on this instruction is I wanna just put a data capture. And and here, all I'm gonna do is I just want it to be like a a pass fail of, you know, did the... I don't know. Did you drop these? Did you not... I don't know. Whatever the pass fail is gonna be. Did... Does it fit the spec? Does it have a torque value and so on? And you can do data capture here. Actually, you know what? Add some data capture to this step, please. And, what you're gonna see is how we can put rules in place for when the operator is working that we want to have some kind of verification. We wanna have some kind of data collection. We wanna have some information for them to to add things that will be captured to go to a system of record on execution. So here we go. It asked for the torque. It asked if the mounting bolts were fitted. Once it's finished, I'll remove my ridiculous one here. And the other thing we can do is then put a condition on it. It's almost done. So it's just cleaning it up. It's just making it look good. Okay. And I'll just get rid of that one. Okay. So now what I wanna do is on this one, I want to lock this step as long as, let's just say the, the bolt torque, is is less than, I don't know. I'll just say 15. I don't even know. 15 newton meters. I have no idea if that's the right number or not. Let's just say that. It has to be less than that or within a range or whatnot. And let's also say that the, both bolts, flag passed. Very good. So when you are done your instruction, you you either review it for approval or you publish it. This is what the instruction looks like. And right now, I'm just letting the user kind of freely go through whatever step they want. They can click on the the tables. They can they can see the things. They can get the cross highlighting. They're basically able to to dig in as they need. Right? And we can see the the instructions as we go through. Now I can't go through anymore. Say, well, why? Well, because we put a data capture step. So I'm gonna... If I fail this and say this is 25, the steps rules aren't met. I can't go. If I pass this, it's still not met. I can't go. Now let's just say it was five. Now it's met. Now I can continue and go on. Okay? So this is how we really deliver the instruction. Let me move into one other thing here as it relates to the updating. If I have an assembly already done, I've got this one I did before, and I've got a a a CAD update scenario. I've already built this instruction. It's it's already built for me. In fact, again, I'll show you. If I were to move this up here, you would see that, you know, obviously, there'd be no bar. This one then would have it generated. So, again, the idea that you're keeping things updated and up to date with the right information is there. But now let's say there's a CAD change. So what's gonna happen here is I'm gonna I'm gonna update my model and and put in, in this case, a new config. And I don't know what has changed. I just know I'm told to bring in the new config and rebuild my instruction for this new config. So what I'm gonna do is just bring in the new data. Here, I'm doing it manually, but we can connect this to PLM, and this can all be processed through through PLM integration and and management of that. It's gonna do like you saw before, convert the model. And once it's converted the model, it's going to do a comparison between the structure of the existing model in the document and the structure of the new model in the document. It's going to bring in any new geometry. So if part a was modified and part a has new geometry, you'll bring in the new geometry. Sometimes, though, there might be new parts. And the question is, is it a new part that I need to accommodate in the build order, or is it a new part that I need to connect to an old part because it was a config change or the geometry change in there? The the parts are different names. So am I doing one to do some kind of part matching? Well, then the new part will inherit everything on the old part. And that's really what this screen does. It's giving me the full model, and it's comparing. So everything in gray is matching. So if I click on this plate, the replaceable printing plate, I can look at the metadata. I can see if anything has changed here, and it's done a match. Same thing with this bar. I can see it's there, and I can compare everything looks good. But I see some things here in red. And it's like, what changed? Alright. This piece here, this 24 dash one, this support frame, there's a new support frame or different one because it's a three kilogram one. Okay. You know what? Let's match these things. And same with the, the spool holder here. Let's match those. So 43 becomes 44. Match those. So now everything is accounted for, and I'm gonna accept this. And it's gonna bring in the new geometry, but those matches are going to come through. Now it's bringing me to build order because maybe there was some new parts or the change requires me to make an accommodation to the build. But for my scenario, that's actually okay. I can keep it as is. And now we'll see how it incorporates that into the instruction. So the new geometry is there. The new part labels are there. Everything has been updated for me. I probably need to update the, the text so I could ask Evie, hey. Can you update the text for me based on the new parts in this step? And just have it go and do that. And while it's doing that, let's go in and add the description to the table so we've got a little more information we wanna use for, operator. So that is a very, very high level of of using three d CAD, CAD update, and so on. And I'm gonna show you one example that's finished of a video. So I have an issue, at my house. I I drive a a John Deere lawn tractor, and, I switch it from mowing grass mode to plowing the driveway mode. And I've got the user guides. I've got YouTube videos I look at to help me do that, but they don't really help me. So I had my son record me do this a couple years ago. And even then, I had, like, a five minute video, but I always had to scrub through it to find, like, that one thing that I needed help with. And I finally... When we added this video to instruction capability into, into our InVision software, I put the video in there. I put the video in there. EV went in and scrubbed it, made it into multiple steps for me, chunked up the video to those steps, but then they also uploaded the document, the PDF of the user guide, and said, go and extract out any relevant images from the user guide based on the per... Particular step that's there. And it went in and read the user guide and said, oh, you were talking about mower deck. Here's the here's the illustration of the mower deck and put it in there. So this was the end result of that. Now all of this, if I were to do this live, would take less than ten minutes, you know, five to ten minutes. That's kinda boring to have you sit there and watch AI think about it, but this is the result. So this was, you know, preparing the work area. In fact, let me also... I don't I don't like this style. Let me change the style again. I don't have a style in this doc. We can have global styles or doc styles. I'll just leave it at that. That's fine. So here, you're gonna need these things. How this works? This was me talking on the camera. You know, I'm I'm basically doing a little intro. You know what? I don't need the intro. I've done this a bunch of times. Attaching the front extension bar. See, it brought in the, the labeling here for me, put some text in there for me so I could see that if I really wanted to know. Here's me sliding the deck under. Well, I know how to do that. The lift arms and the butterfly clips. Yeah. I remember that. That's no problem. This... Oh, this drive belt. That's the big pain. There's the two minutes I wanna watch. Let's do that. And if I were to show this here in the operator, this is basically now where the difference between someone who's never done it before or someone who's done it before and just needs a reminder. Right? Here's my caution. You know, here's this. And, actually, it pulled a key frame of the video just to give me something that's close to relevant here. And and, you know, the the earlier ones, maybe I I don't need to watch the video. I don't need to watch that forty seconds. I don't need to watch that forty seconds. But what I really need is is, that one, then I can just hit play and watch that video. So the idea being whatever you have, video, PDF, three d data, whatever, you can turn that into a step by step instruction that can be executed by anybody, whatever their skill level might be. Okay? So that is the quick introduction of of that. Let me wrap up with a with a, with a couple of slides here, which I think is this here. Yes. I just finished the demo. Okay. So here is, again, reminding you, you saw three modes plus a fourth one, which is the operator mode. So we built the sequence. We did the authoring. We can do the update. Then we have the operation side with data capture and things like that. As I said, we can connect it on the upstream side to PLM, downstream to to MES. And, ultimately, this brings quite a few things to you. Doing this in minutes. You you don't need AI to do it in minutes, by the way, but with AI, it goes even faster. And more importantly, it starts to apply your standards. So your engineering hours are reduced or even multiplied because more people can do this work. Okay? Sorry. I'm gonna bring myself back. I forgot. Here we go. Hello. Very, very rapid changes, whether it's the build order, the geometry, the instruction itself, different languages, and so on. Getting that standardized view, it's digital. It's not a flat PDF. It's not a patchwork of content. It's one platform with everything that is fully connected to your engineering data and, you know, bringing it everywhere in the right way just by refreshing your browser screen and getting that latest one. So the idea here is you can look at systems, you can look at digital transformation, You can do all those really critical intelligent connected worker type things. But remember, the person on either end of that, the knowledge in and knowledge out are the people that this helps with the most. And it's very quick to implement and start reusing and using all your content to allow the maximization of of their time and effort and what you're doing. So that is a, a high level intro. I think that was my last slide. I'm gonna I'm gonna bring, Alban back here with me and have him introduce to you our foundation program because this software is not yet, released, but we are making it available to you through this program. So, Alban, do you wanna explain a couple slides here? Yeah. Thanks, Garth, for this demo. So foundation... Build a foundation, what this is. What Garth showed you, envision builder actually becomes GA in February 2027, so three months from now, basically. And we are opening the build a foundation to a very small group of companies to start working with it now alongside our team instead of waiting for the launch, in q one next year. And we are limiting it to 30 companies because we want to work closely with each founding company, and that only works with a very small group. And these 30 companies can... Actually, we cover the three editions. We have three editions of this program, and I'll talk about in a minute. So what we ask of these founders, founding companies, is that they actually can use their own product, the one they actually build, with your own CAD data, own CAD designs, and your own people. Because the point of that and the goal is to take it from the propose assembly sequence all the way to finish working instructions on your floor and a use case. So, actually, it is your own data, and you understand what you're doing. So what's in it for you? As a founder, you get access and a direct line to our product team. And everything that you find and I want something and you tell us what your operation is something and goes directly into what we build between now and GA and even after that. So the day to remember, that's there. Just before everybody goes for Thanksgiving, November 25 for the, this is when we close the enrollment to this foundation, build a foundation program. Next slide. So... Actually. Garth, if you can go to the, next slide. There it is. So we have three editions. One program, three editions. So which edition is right for you? So we decided to base it on the company revenue only. Under 10,000,000, 10 to, 500,000,000, and over $500,000,000, which makes sense in terms of company size. One... Something to understand, unlimited operators on every edition. So everyone on the shop floor who consumes the instruction is covered. No extra cost. So your team, they can load it out to the whole floor. No need to ask for budget for each new person. Everybody's included. So the first one, the starter edition, cost $1,700... $7,500, sorry, against a list price of 25,000, which is a yearly cost, covers one site up to five authors. And this is really the perfect stage for smaller manufacturing startup companies. They want to prove builder on a one single line. So you can... You you get started. Then the growth edition, foundation price, $15,000, against 50,000 list, so hefty discount, covers up to three sites. And we put 25 authors. We have to put the limit somewhere, but that should not be an issue. And that is perfect for midsize companies, and you may want to have a pilot and maybe more than one plan from the start. And finally, the enterprise. So large organizations cost is $45,000, covers three sites, unlimited offers. And also what it does, and Grant mentioned that it includes, EV Connect, EV Builder, and EV Operator SDKs. So your company's engineers, they can connect builder to UPLM, UMES, UARP, and you can actually build your own integrations. Part of the enterprise edition, extra bonus, you get a direct access to Gart and the product team. So, how do you apply? There's a link. Canvasenvision.com/builder-foundation. And then, you book a thirty minute call with our leadership team. We agree on the plan, the product that you bring, the people. We're gonna work together, and the start date, and then, basically, as simple as signing the order form. And the thing is, as a founder, you can actually start building within days of signing. So and, actually, I just I just put a link on the bottom there. You can, like, book a meeting right with Alban, right right away. If you wanna talk more, you wanna learn more, look at some of the other modes, look at some of how your data could work on that. So, we're definitely... Again, we're... We got a lot of excitement and interest in this. The the development's gonna close in December, which is why we were limiting the time period to to, connect with this. And then, we can only work with so many companies in that capacity before we go live. So we're absolutely, looking to see who wants to work with us to get the last few pieces in place to really allow it to to prosper in your organization as well as get a few extra months, free because the the the start date of the subscription isn't until it goes GA. So from now until then, you're basically getting it for for, extra few months to to, work with us. Now what I've been working here pre GA, it's, it's usable, and everything I just showed you, is is is... It's, like, 95% complete at this point. So we're pretty excited to get it in some people's hands to get the feedback on that and to really get this the the last little few inches to, to production. So with that, I'll keep the, I'll keep the the tracker up there on the bottom to book a meeting. And, I can just check if we have any questions. I didn't see any questions yet. Usually, this is the, the typical reaction. There's so much stuff we showed. Absolutely, you can send us a question at any time. I'll give a moment here if anybody wants to raise their hand or you can type into the q and a. It might actually not be showing. It might might be in blue, but it should be there. You can type in a question, and, we can answer that or, of course, book a meeting with Alban and and get all your questions answered. Sometimes there's a lot of specific company proprietary information and systems information and questions that maybe you don't wanna share, on a broad thing, and that happens all the time. So... But we said we've been about forty five minutes. We've been about forty nine minutes. So, what we'll do is we'll close this. Everyone who signed up for this, the recording should be live in another hour or so once it processes, and it's the same link. So the same link you use to register and get into the recording will turn into the on demand, and you can share this with your teams. And, again, connect with us, and we look forward to working with a lot of you. So thanks, Alban. Thanks, everybody, Thank you. and, we'll see you soon.