Name: Closing the Loop from Engineering to Manufacturing Execution with DELMIA
Uploaded: 2025-02-04T19:30:04.992Z
Duration: 1 h 1 min 4 s
Description: Closing the Loop from Engineering to Manufacturing Execution with DELMIA

Transcript for "Closing the Loop from Engineering to Manufacturing Execution with DELMIA": Alright. Hello, and welcome, everyone. Thanks for joining our webinar today. My name is Jason Curtis. I'm the director of applications engineering at GoEngineer. My primary responsibilities are everything in the virtual world. I'm also joined by my colleague, Nurjan Jankalele, who is the director of our manufacturing execution system, the MES, and MOM, which is manufacturing operations management solutions. And he, is responsible for all of our solutions that manage the real world. So in this part one, part two webinar series, we're gonna cover this closing the loop between engineering and execution. So in part one, I'm gonna do the primary responsibilities of doing the presentation and the the live example. And then, in two weeks from now, Niranjan will take over for part two. So a little bit of housekeeping before we get started. If you will notice on the right hand side of your screen, there is both a chat area and a q and a area. We really wanna encourage you guys to be interactive with us. So, you know, so for comments or, things like that, please feel free to use the chat. I only ask that you keep it professional, and, we keep it kind. If you do have a question, I would prefer you try to use that questions and answer panel. That way we can document them all, and they don't get lost amongst the chat, so we can make sure to address those. So, so I'm gonna get started in our presentation today, and what we are going to be talking about are some of the things that you that probably drove you to this presentation in the first place. Those things that are in the back of your mind about how challenging this process can be to to go from an engineering, you know, design to something executable. Right? And the typical challenges happen to be around, you know, the manufacturing planning aspect of this where we're trying to collect a bunch of different data, bits from a bunch of different sources that are probably stored in different databases. These are different CAD files, you know, design teams using one set of tools, and they have their own, database or storage system and specs and, SOWs, you know, or SOPs. Operating procedures might be in a different format. And, you know, then we need the MBOM, and that's probably in another system, and we need to export some kind of Excel spreadsheet. So, it's really up to, some some really smart people working really, really hard to make order out of all of this chaos. And the challenge is this is all disconnected. So when we talk about, you know, some of the improvements that we're gonna look at today, some of it is speed in coordinating these activities between design and manufacturing engineering. Some of it is the accuracy in terms of making sure we've collected all of this data, and some of it is going to be just in the fact of being digitally connected allows us to create a much more rich and, mature plan that we can then send to the shop floor. So the challenge with the existing processes are, again, due to speed, we gotta get something to the floor. So we're really just collecting a bunch of documents and trying to put it in either a physical or virtual binder, that we have to flip through, and immediately that information is out of date the minute that we that we release it. Compound this with okay. Let's let's say we get really good at this one time. Right? We got a really good process. We got really good people. We can get something out to the shop floor. What happens when, you know, we wanna incorporate, improvements, enhancements, things that we notice could be better or something doesn't go quite as planned and now we gotta go back through this loop again. So these are really the typical challenges that we are looking to address with the solutions we're gonna present over the next couple of webinars in connecting all of these, actors, datasets, and processes under a single unified platform. And that is what Dassault Systemes is delivering. So we're gonna talk about digitally connecting our engineering and our manufacturing engineering under this operations engineering header. This is also the same platform and same data model where we can do the execution. So we're gonna talk about digital continuity with the execution system and shop floor operator and things like quality and time and labor and even down to the, maybe integrated equipment level as well on our next, webinar. So Dassault uses this two platform approach. Because we can have our engineering models, our manufacturing engineering data, and our execution system are sharing a common data model, there's no integration. There's no loss of data. The, pull what we plan to execute is exactly what we execute. What we capture on the shop floor, we can feed back into engineering if need be to make changes. Of course, there are points of time in which if you have an ERP, you may wanna communicate information to it. Of course, we can do that, whether it's the MBOM routing information or any execution status or the ERP being the master of what work orders we're actually going to release to the floor. So the reason that we have this unique ability to have this digital continuity is really in the three d experience platform. And if you haven't seen this before, don't worry. You're gonna you're gonna see a little bit of this, today to enough to, be comfortable with it. But I really encourage you to check out some of our other webinars where we go into this topic in more depth. But the main topic for today and what's relevant for today is the fact that we have an enterprise wide platform that covers all of the entire business and brings everyone together under a single, unified data model. So, of course, we can manage documents, revision control, life cycle control documents, but our key advantage here is the way that the platform turns our data into model based. So moving away from document based to model based, and I don't mean three d data. What I mean is a model. Some of that is engineering items. We consider these engineering items. This could be your SOLIDWORKS data, if you're in CATIA, if you're in CREO, what wherever the source is, if you're in Cadence, for, you know, electrical type of work, maybe this is software. What a model is is, you know, a breakdown or a decomposition of all of those elements into different objects that have parent child relationships. Right? So we're familiar with the, you know, CAD models having parent child relationships, and you can build those relationships between them. What we're gonna explore today is a new concept of model based manufacturing on the platform. So when we create, an MBOM, it is also a model based structure that has parent child relationships and can also consume that engineering data. So we're gonna see some things today about how we don't have to, recreate any information. We can reuse, you know, what happened upstream in the process in in engineering. Same is true for our model based processes we're gonna see and model based resources. The process is where we start to consume all of those manufacturing items and resources into a complete plan that is a complete recipe for how we're going to, execute, and and create this this particular, assembly or item. So that's what happens downstream. That's gonna be the focus of today. Just as a quick intro for three d experience, upstream is also model based in terms of model based systems engineering. So the capabilities to have a model based set of requirements or, systems architecture and functional and logical behavior and also to simulate all of this upfront. Now the requirements are interesting because this is when we start to get into some of the platform capabilities that cross all of the domains. Right? So not just engineering, but into manufacturing engineering as well. So that when we have individual, requirements, they can be associated or allocated to the individual item, whether in the process of the MBOM or the work instructions that is actually satisfying that requirement. And we'll start to see some of those relationships today. Other platform level components are how we can also introduce variant configurations and effectivities and manage all of these different models, model types on the platform, and a common governance change management and project management that kinda provides governance for the entire project over over all of these domains. So everything in green here, we're gonna take a look at today in terms of the manufacturing item structure, the process, you know, routing structure resources. And then the goal is that this strategic data model we use on the platform is also the data model that we use on the execution system. So without any duplication, as we are executing this, it is retrieving, you know, exactly the template that we, created on the three d experience platform. And, again, at some point, we may want to synchronize or exchange data with some, you know, fill in the blank ERP or some other business system, that, of course, is possible as well. But everything that you see here covered under the three d experience platform and all of these blue links is our digital continuity where we do not have to, change data format in order to convey that information. K. So document based to model based, very key point of today. The highlights of our series, we hope you walk away with some of these, key values in mind. One, once we start managing the data on the three d experience platform, we are physically digitally connected to it on the manufacturing side. So today, I'm going to go through a series of live examples showing how we turn that into an actionable MBOM, becomes our item master, a bill of process or, process plan for a process master, work instructions, and defining the sets of controls that we want to see exhibited on the shop floor. In, part two, that's where we're gonna do the controlled execution where we're gonna highlight how we use that, process template we defined as the the master control for the sequence as well as any data collection, item number tracking, time time tracking, any of that in terms of quality and process control on the shop floor. Of Of course, we'll look at a rich set of, dashboards and reporting capabilities for those of you who have strict genealogy or traceability requirements for any of the products that you're producing. And, again, one of the key things that you'll hear us, reiterate over and over again is this digital continuity. The fact that having this all on a unified data model opens up a ton of possibilities for reducing the time it takes to go from engineering to execution and to incorporate changes along the way. So what are we gonna see today? I'm about to jump into software. So we wanna start with the the who, what's, where's, and how's. So we're gonna start with the engineering items or the, you know, the the CAD design, turn that into an MBOM, and I'm gonna show you some visual tools that we have that we can leverage much like three d, you know, lean manufacturing principles on the shop floor. We are gonna have some visual dashboarding capabilities to ensure that we've consumed all of our items, to ensure that our our product is conforming to the plan. We'll use some of those color codes to perform some validations. So we have some, some system wide checks to ensure the the quality of the data that we are are creating on the manufacturing side. And then we are also going to use this to document our controls. So, any data collects, any, work instructions with visual aids that might need to go along with this will show how these are, you know, a natural extension and generated from from the work that we're performing. Now, of course, the point of all of this is to be to come up with an actionable template that defines everything that is necessary to drive the rest of the business, which is, you know, financials on the ERP side or on the execution side, which we we call it Apprezo. The this is what the, the recipe is for how we're gonna execute and and work that. And because we have this digital connection, if we have a change, something needs to be modified anywhere along the way, anywhere in this value stream. We can immediately understand the impacts and then, take appropriate actions to to update that. Okay. So without, further delay, we're gonna jump right into the software. So I am wearing the hat of the manufacturing engineer. And the first thing I wanna notice is that I have a three d design in front of me. So what am I doing with this three d design? I I'm not the designer, but because the, designers are storing and managing their data inside of the three d experience platform, I have access to that same set of data. It's not a duplication. It's not a translation. I have in real time access to that same data, same set of information that the designers have. Now, of course, I don't have, any rights to edit it, but I can start to understand and partake in very early, in the design, understand what is gonna be required. And, this is where we start to use some of our visual dashboards or visual overlays so that I can see in real time, the maturity of the design. So in green is everything that's currently in work. Yellow is something that's going through an approval process. Blue might be, something that is, released already in in the design. And I noticed a bunch of different levels of extra structure here. Maybe I need to understand a little bit better the designer's intent. So this gives you some tools to help understand and make decisions even outside of those kickoff meetings to very early this, take a look at what is being generated and how we're gonna plan to to start this. So this color code specifically here is just telling me that the designer's intention is that anything purple here was, was intended to be a phantom. It's not really meant to be produced. It just we needed that structure in the design, and that's okay. I don't have to go back to them and tell them to change it to make it manufacturable. I'm gonna show you how we can do this, right here in in three d experience. Okay? So we have a we have a very immature design where most of most of it is still being worked on. We do have some design intent, and that's okay. I'm gonna go ahead and get started on this because I know that I'm gonna be able to up keep this in sync and up to date as the design matures. So I'm gonna use a couple of tools here, a couple of different toolboxes that have these tools. I got manufactured item definition. This is my MBoM set of tools. We have process planning. We'll probably look at work instructions as well today. So let's start this journey in the manufactured item definition, toolset. This is where I am going to start to create a model based representation of an MBOM, and I'm going to consume that engineering data. So here's my engineering data preloaded into this into this structure, as a starting point. So, this might be taking those decisions of, you know, what should be in the MBAM. Right? So we have a top level node here that is, manufacturing assembly. Underneath this, there could be a provided part. There could be make parts. There could be continuous type of materials, you know, length, mass, volume, area types of things. Right? There is some business logic that can be configured on the back end and that, what's happening right now is we're taking a look at the structure and deciding which nodes we can ignore, if they're phantom or if they don't really belong, and what item types to create as part of this model based manufactured item structure. You can also put in some other logic there if we want to copy part numbers, copy any other attributes like the descriptions from engineering, or if we wanna just, create our own, attributes. So we'll take a look at this once it's finished computing. And, again, we're using our engineering as a seed for this. So now what I am going to be defining is, what we like to think of as the material or the item master. So instead of doing this in Excel spreadsheet, instead of doing it screen by screen, line by line in your ERP system, we are having a sandbox to create this item master here digitally connected to the engineering, and then we will definitely push it to ERP if it needs to go there. We'll definitely push it to any other format if it needs to go there. But this becomes our model based MBOM. So as you can tell, very flat m bomb. So remember those screws were in a couple of different structures. They're actually counted up. There's 24, here in this, in this assembly, and they're right directly underneath the top level. So I like to work in this graphical view, but I certainly, don't want to take away anybody's spreadsheets if they really love working in spreadsheets. This starts to bring into account the fact that we can work with the same data in multiple different viewpoints. So, here, I'm just gonna put these side by side real quick. On the left hand side is our engineering item structure. This is our, for for lack of a better term, our CAD structure. Right? On the right hand side is our MBOM. You can see completely different structures thanks to that, you know, business logic that I've configured. You can absolutely do this manually, but I saved some time for our presentation today by configuring some of that automatically. K? Now I'm gonna highlight an item on my MBOM side, the right hand side. I automatically see something on the left hand side highlighted from my CAD design. This is that digital traceability between my MBOM and my, my engineering item structure. So we can start to see these, these threads of digital continuity, this traceability, this understanding the system has between our manufacturing, model based structure, and our engineering model based structure. Same is also true if I actually, I wanna put these right in the same window here. Same is also true if I look at my three d window. So I can, select on the three d and, of course, in my, spreadsheet view, this highlights as well. So that cross highlighting, that, digital traceability, we're talking about, single, unified data model here that we can tie to other, data models. Alright. So, if this were a live demonstration, usually somebody has called me out on this already, but, I bet some of you noticed that some of my components so I just created this MBOM right in front of you live. So why are some of these components released? I certainly don't want them automatically released without me me knowing about it. Well, that's not what happened. Let me show you what happened. What happened was, the, screw, in this case, the the CAD item that was that was used to generate this, manufacturing item, this has gone through an approval process already. You can see it's in a release state. It was, what happened was this screw was used on a different project that's already gone through the whole MBOM process. It's already gone through the whole release process. And then this screw was actually reused on this project. So what happened is when I created the m bomb, the first thing that the system does and it goes it looks at those, relationships and it says, well, does this screw in my CAD model already have an an MBOM model associated with it? If yes, let's go ahead and reuse that. So we're seeing some, item reuse behavior here. And kind of the moral of the story here is that, you know, the more carryover parts you have or the more you use these these tools, the more advantage you're gonna be able to get out of this this data reuse. K? In this case, we've defined some, attributes on our MBOM item that are not on the EBOM. So our structure, is is what we want it for manufacturing. Now we're enriching it with some attributes that we need for manufacturing that maybe engineering doesn't care about. And we're also in introducing some behaviors. So I'll start to talk about behaviors as we go further into this. Some of those behaviors, how should the ERP system treat this item? Right? Do we need to indicate that, that we need to control it with a lot number or we need to control this part number by serialization or both or none. These are the attributes that we will be passing to those other business systems that need that that definition. For execution, when this gets to the shop floor, Apprizo is gonna look at this, And then when this part number is actually coming into the system, it's going to prompt the operator that they need to enter or scan, this particular item for for a lot number. So we're starting to not only define the attributes of these items, but some of the behaviors that we're gonna see in other systems. K. So other things, we'll take a look at some of our, digital traceability, that digital continuity. One of the double checks that I want to, often go back to is our product assignment status. In other words, have I consumed everything from my engineering items structure? So here we can see I've got a gray item. This is an item that was only in there for visual reference. It's been marked as non assignable, and it's not just that initial sync, that is controlling this behavior. Even if I forget, I make a mistake, you know, I'm this the software is saving me from myself, and it's actually telling me, this is actually ignored in the EBOM. We can't assign this. You know? You're welcome. We just we just saved you, from creating a new part number, errantly. Now as the design matures and parts get added, parts get removed, we'll be able to see that very quickly with those visual color codes and understand the impacts and act appropriately. So, right now, the only thing in my MBOM are those things which were in the engineering items, right, in the CAD structure. We know that there are often items that we need to add in addition and and could be things like consumables. Of course, we can certainly add these manually. We have a full set of authoring tools to create, you know, purchase parts, provided parts, make parts, continuous provided materials with different, magnitudes that we wanna track them by. Of course, we can also create libraries or catalogs of these, components that are commonly used or that maybe you wanna put through an approval process before you allow them to be used inside of your, your MBOMs. So in this instance, I've got maybe, since we're putting some screws in here, I know I'm gonna need some Loctite or some other type of adhesive. So I'm just going to, insert that into my structure from my, from the library that I've created ahead of time. Now I've put some ridiculous quantity in here to tell me that I need to update that. You'll also see that it has a picture definition. So this is not a three d object. I haven't tied it to my engineering, but I can give it some sort of picture pictorial reference if that's helpful. We can define the quantity as something either with a magnitude or just simply as required. Of course, we can add, discrete types of elements, like if I wanted to add, some kind of marking element, whether it was a sticker or in this case, a serial number tag or, you know, anything else that you would need to complete this MBOM and have it used as your item master. Okay? So so now we have, we'll call it a, a complete MBOM at this point. The next step of this is to move on into the process planning or the routing. So what sequence do these parts need to come together for our final assembly, and, what are the steps required, to do that? So for that operation, for that task, I'm gonna be using our process planning set of tools. Now with process planning, we talk about a, a work plan with operations and those operations may have steps and then we also may have work instructions that we're gonna hang off of this. Now this is also model based. So in this case, I have a top level assembly with a chassis subassembly. It might make sense for me to create a a a two level structure here where I have a work plan that I can, scope to my chassis assembly. Right? Scoping it kinda limits the available MBOM selection and helps me to do those balances and double checks. So this is my subassembly work plan. I can create operations, inside of these work plans. So say, you know, up 10 and give it some description. If I expand this, we'll start to see underneath, we say up 20 just to keep this thing somewhat simple. And I can create multiples at once. And then these operations, they can be reorganized. Right? This is just a a a an acyclical graph, but there's no sequence yet. The sequence is defined by me creating product flows. So we we start at the first one, go to the second, go go to the third. Now I have a sequence, and a skeleton of a process. So couple of things to note here. You know, these processes, these work work plans, these are meant to drive behavior on our execution system. So this is not just a pretty picture. This is not just a documentation of our process. This is how we're going to control it. So you'll see things that we can take advantage of, like total production time or cycle time if we wanted to do some, workload balancing of our processes underneath it. We'll show I'll show you how the times get added and rolled up. This happens to control things on the shop floor like our queuing mode, our sequence mode, and those types of things. So when we are defining these, the more information we put into the system, the more complete it is, the more that we can control, our process. If I look at a operation, for instance, it has a different set of properties where we're concerned with, you know, how long does this operation take? What What time are we using? Is it something we simulated or measured or estimated? Did we use some time studies? You know, those types of things. And then whether or not that that can be rolled up into the overall process. So, of course, once we sketch this out, if you have common processes, we do not have to keep doing this manually over and over and over again. Of course, just like we did with the MBOM items and having a library of items, we could also you could also create a library of your own processes that are typical. So here, I'm gonna do a final assembly process for, in this case, this is our radome assembly. So we'll just insert this. This creates a unique instance of this for me to to generate the process for how we're going to, do the final assembly of this this radium. So I am still wearing that manufacturing engineering hat or the industrial engineering hat where I am defining the template or the how do we want the process to flow? So here I've pulled in a, a process from, catalog that is not just a serial flow but also has a parallel flow. And before I get too far here, I do want to, tell the software that this work plan is actually meant to produce this, this overall assembly, this MBOM item. Now, you may not have seen it because it's a little light gray here, and it was kinda off the screen. But as soon as I did that, I got an implied precedence link. And that was just due to the fact that this system is managing a subassembly. This system is managing the overall assembly, and we know that there's a precedence that has to occur. This this item has to be available before we can go to the final assembly. So nice things there. We're starting to see some precedence links and some behaviors being endowed into this process plan. Back to this parallel operation. So my project flow arrows can define either serial processes or parallel processes just in how we connect them. So in this case, we're starting with, first assembling the bulkhead and the brackets, and, then we move into two parallel operations that can happen in at at the same time or, one before the other, but it doesn't matter which, where we attach the chassis and we attach our part marking elements, and then we go into a quality step. Now you'll notice there's a different color on this arrow. Our color code indicates yet another behavior of our process. Blue arrow actually indicates where we have a process templated out for a good path. That means if the previous operation completes and the operator marks it off, yep, everything went according to plan, good flow, we follow the blue arrows. But we can also build in if we know ahead of time we might have some failure paths, some rework paths, anything any alternate processes. So in this case, my green arrow is actually defining an alternate process with a specific reason code, and then I can see that reflected here. So you you may have, as your process plan templates mature, multiple different flows that go out to handle, you know, ahead of time all the things that you can plan for. Right? Anything you can plan for. Anything you can't plan for, we'll handle on the shop floor side as a nonconformance, and Niranjan will cover that. But, really, I'm talking about what is our desired template and our process, that we wanna use for execution here. Okay? So inside of these, operations, we have the steps that are required, and we can be very, explicit about this. Now so far, I only have this as a skeleton of the process. I haven't yet consumed or allocated any of my MBOM to this, and that's what I'm gonna do next. So this could be as easy as just dragging and dropping, but I I don't have a PhD in part numbers. And, again, I prefer to use my visual tools like the system's assignment assistant, where, on the left hand side, we see all of the parts that have not yet been assigned or not yet been allocated to my process plan. On the left hand side is empty because I I haven't allocated anything yet, but I can choose which step. So load bulkhead stuff. Let's, not do any reframing anymore. And I can choose either from the three d or from the parts list in the bottom here. We'll just take the bulkhead and we'll allocate it to that operational step. As you can see, we have cross highlighting. So, you know, not only do we see it reflected in my wizard here, but I also see it reflected in my, graph view. And you'll see it might be kinda hard to see, but you can see the part actually showing up here. Well, I assign my MBOM item to this step. My MBOM item is consuming my CAD item, which has a three d representation. So you can see that digital continuity being displayed here again. So in my next step where I assemble the primary brackets and fasteners, I'll just continue to complete this out a little bit. I'm actually going to drag and just drag a window around these, MBOM items and allocate those. I have some on the bottom that I'm also considering primaries, and we'll allocate those. And then we'll switch to our third step, which is to assemble the secondary brackets, and we're just gonna stop right there. I think you get the idea. Really simple, drag and drop or using this wizard to allocate, between the steps. So now an interesting thing has occurred here. We know exactly which step in which operation in which work plan, this particular item is being consumed. So now if anything along the way changes, we know exactly where to look. Side effect of this allocation is that I now have the ability to review the product buildup. Do you design for manufacturability, design for assembly kind of studies where, you know, I can see the parts, and I have a a color code enabled here. You can modify this. I use yellow for anything that's currently being assembled, blue for anything that was previous, and then you'll see maybe some orange, some parallel operations. So in step one, we're consuming this item. In step two, we're consuming a whole bunch of items and I have the product build up exactly as it is at that step. K? So we have our our items being added, and the blue is what's already been added. We go to the third step. We see our secondary brackets, and it might be hard to see with the shade of blue, for everybody there, but you can see the product build up. So the next step, which we haven't gotten to yet is, you know, work instructions. If we have an operation that needs some visual instructions, I don't go have to go back to the CAD designer, say, hey. Can you hide 90% of your assembly and rotate it just so so I can get that one image that I need? And then, by the way, the next time it changes, we need to do that again. No. The system is doing this for you. This is an added side benefit. We're getting that product build up as we're allocating, you know, our parts. So speaking of allocation, I have a very incomplete process plan, and I know that because when I use my item assignment status, I get my color coded display showing me anything in orange that has not been consumed from my bill of material. So I have a lot of fasteners consumed, but I still have, you know, the whole chassis. I have the part marking. I have the Loctite. You know? So I can very quickly, at a glance, check the maturity or the completeness of my routing, and has it consumed all of my mbong? And there are all the double checks that that you can use as well to check the quality here. Now one more thing that, might be interesting is we have defined the process flow and kind of the types of, of operations and steps. We've allocated our MBOM, but we haven't yet talked about resources and where this work is going to take place. And are there specific skill sets required, to perform specific operations? Because what we wanna do is control not only the flow of the assembly, but the access and where the instructions actually show up at any given time. So this particular work plan for the final assembly actually has a couple of resources allocated to it. I kept it simple. It could be work locations. It could be machines. It could be anything. I've got a couple of different skills. So these are technological resources that represent a skill or certification, and I do have a tool, like a tool class, a torque tool. So, when we look at any particular operation, say this operation one, I've already predefined that this operation should happen in, assembly Work Center 1. That means that no matter the status or the progress of this process plan, only this step and only this work instructions, and only these sequence these set sets of steps for one will only ever show up in this workstation. That's one way of controlling, you know, who gets what, at exactly the right time. The other way I could layer this on is to actually add a certification. So it doesn't matter if this shows up in workstation one. If I don't have at least an assembly level one skill, as I've just connected here, when I log in, I won't be able to see this either or if my certification expired. Right? I I need to go for recertification. Now I also know that some of these steps also are gonna require a, a torque tool, So I might also allocate that here. And you're starting to get the idea now of how we're going to also allocate tools, skills, work centers, work locations, or any other, item that we would wanna include as trackable, schedulable, resource or anything secondary like a fixture or, you know, anything else that would, that would just need to be handy, for the for completion of this operation. K? And then in, operation 20 here, step two, it's happening in a different work center. These, twenty and thirty are actually happening in the same work center. Maybe they're different skills. Maybe it's two different people. Maybe it's one person, but they could do them in either order. You know, it's really up to you to define what that that context is. And then, of course, we come back into our quality step, which is actually gonna happen in a different work location with a different set of skills here, you know, later on. So moving on in this equation, the next step is to maybe define some work instructions to describe what the operator actually needs to do to alert them of any situations that might be dangerous or important, to tie in other documentation that supports the process and, and the execution as well. So in this case, that is where I might be using my work instructions set of tools. So I'll switch over to that quick. At the top of the screen, we're gonna see kind of a film strip. Think of it like a film strip. These are those three steps that I had, defined and allocated our MBOM items to. We see them displayed here. You'll see an arrow at the top. That's indicating that we have, operations happening after the fact. Right? So we have, the step twenty, thirty, and so on. But this is where we start to define the different elements of work instructions, and this is also model based. So we have different model element types for different types of instructions. One type is an alert. An alert is meant to be a pop up or a dialogue box that we need to display to the operator. They need to read it, and they need to, you know, take some action on it either to track, their confirmation and acknowledge it, whether I want it shown once or shown every single time. Maybe I want it shown every single time like it's a safety alert. All of these editors are full text editors. I can create links, anchors. I can drag and drop images from desktops. I can create tables. I can type. This is not a test of how fast I can type. To keep things moving along, I've just predefined some things that I wanna put in these instructions. I'm gonna copy and paste them. You'll get the idea. Right? So this is the type of of information that we can support, in type inside of these rich text editors. So instead of having it all in one giant document and we print it out, we tell them go to page 327, section d, I'm presenting exactly this instruction, exactly for this step, exactly for this operation. We can also include things like links. So if I take a look at, if I hover over this, it probably shows better here. I actually have a specification document that's just stored on our SharePoint. You know, so you can link to any other documents, so you don't have to actually include them. Or it's a great way if you're, you know, thinking, you know, how do I get from where I am today to what you're showing, Jason? Yeah, great way is to just try to include those as links and and utilize them that way as you begin to decompose them into these model based elements like we see here. Of course, text instruction is the other type of of instruction that we have in a model based, environment here. That's just that. It's just the text. Do this, do that, do this. The you know, it's typically bullet item lists, numbered lists, maybe some images to go along with it. If I can highlight, we'll just copy and paste that in as well, save some time. And then if the operation is significantly challenging enough to warrant creating some graphics or if you just really like to have that visual for your shop floor, maybe it's a multilingual shop floor, we can then create supporting views to capture the state of, what is displayed and also to enrich it with some smart labels. So, again, we're taking advantage of that item reuse, that item consumption. In this case, I've got labels configured to automatically link to the part number and the description. You can enrich this with arrows and leaders and circles and, you know, all types of markup elements. And what's nice is these elements are sticky. So if at any point I decide I don't like the orientation or the model changes enough that I really need to reconfigure or move this, I'm not losing any of my effort. It just goes along for the ride. Alright. So now got a problem. I got a bulkhead with no holes in it because I started, you know, the manufacturing process probably a little early in the design process. Well, that's no problem. K? I actually wanted to show you the impacts of working in this unified data model in real time. So I'm gonna take my manufacturing engineering hat off. I'm gonna go back and do something as a design engineer. So this is not we're stepping out as the designer. You know, maybe the next day, maybe two days later, whatever, going in and, you know, finishing or completing this design. Say they need to go in and make sure that they have the holes. Right? So we go from a bulkhead that had no holes to a bulkhead that now has holes. Okay? Now the expected behavior here is because we are on this digitally connected platform, so just like if I were to edit this in SolidWorks and my SolidWorks drawing would update, I would hope to see that kind of behavior in my manufacturing data, that I've created. And that's exactly what I'm gonna show here. So let's walk through this. We'll walk through my MBOM. You know, if I didn't know about this change, I could do a couple different things like maybe the, item update status and all of my up item status is good. Well, why? Because, it wasn't a new revision. It wasn't swapped out. It wasn't removed. It wasn't something added. Everything's fine here. It just got a new, it has a new shape representation, and the system is smart enough to know that, hey. That's great. We'll just re consume that. And move on. If we go to our process plan and we take a look at our, our process, everything is still good here. If I look at the three d buildup, you know, I still see the item consumption at the right step, but now we see we have the new, three d representation because of that digital connection. I haven't lost any of that work. And then, of course, if I move on to our work constructions, I now see the holes represented, and I'm able to, you know, continue my work from here, you know, design design whatever else is necessary for my, for my instructions. So really powerful utilizing that digital connection between engineering and manufacturing, doing this all on the same platform. K. Moving on, there are other types of these model based instructions that I'm gonna take a look at. One of those is going to be a, data collect. So we are going to expect to collect some torque values. Right? So this could be a data collect plan is, you know, I've got some real values I wanna collect. I got some true false values. I got some text values. I wanna create a whole list of things that I wanna collect. A checklist is really just a yes, no, true, false, one, zero. So there's a quick button for that. Either one can can get the same result. So in a data collect plan, it's currently I have no rows, created. I'm gonna create a new row. And in this case, I'm going to collect some torque values. Now I do have some instructions that I have pretyped out, again, just to save some time here. So I'll include those as part of my instruction. I might give it a label, if it was something in the genealogy report that we wanted to make reference to. Number of measurements, I think there's something like 16 screws here, but, you know, just to make sure Naranjan doesn't pull his hair out when he gets the execution, I'm only gonna make him recollect two. You know? And then we can define, well, what is the actual magnitude we're collecting? Well, of course, it's torque, or I can choose from any of the other available magnitudes, that are very numerous. So we can cover every scenario of data that you might wanna collect, including the unit. And then I'll define my control values. If I have minimums and maximums, put those in place. Now this is where we start to put some quality conformance into the process. So nominal values plus the, the controls and the mins and maxes, This is where we start to define our quality controls. You know, we're actually requiring this will this will prompt the operator to have to enter or, collect this value from a digitally connected torque tool. So now we're getting connected into the equipment side of of things. But, again, this is our recipe. This is what we are requiring of, the execution system to perform. This is this data collect. K? And I can have one or more, lines here. We can move components, show exploded views, things like that. You know, I showed some labels. I showed some markups. If we did want to enhance this with things like, you know, center lines and holes and callouts and oh, I deselected everything. Try that again. You can see, you know, we can get some automatic center lines and, things to help support. So moving components, resetting them, changing the properties, all this is very, you know, very easy and meant to be intuitive for manufacturing engineer to use. K. We're getting close to the end of our time. So the other things that I wanted to show, were a, a sign off and a checklist. So in the interest of time, I am actually going to open up a completed process plan and illustrate couple last results here. And then I'll probably turn it over to Niranjan to give you a sneak peek into what this is going to look like in part two of our webinar series, where we actually look at the execution side or the, the shop floor operator view and and some of those tools and procedures for controlling the execution. So one final thing as we, as I complete the definition of my process plan is all of the data that I have created today is model based. And then since it's on the platform, it is subject to all the governance and controls, that everything else on the platform is as well. So there's revision schemes, so we can control the revisions. It can go through approval processes. It can go through and participate in in formal change processes if that's important to you. And then, of course, we have all of that digital traceability that I had already mentioned. So one final look at a couple of different instruction types here as we, bring this demonstration to its, completion is when I get to a quality step here, and this will be important for for part two as you, you know, you understand, you know, where we're headed with this. There is a quality checklist. So, I've defined that these should be yes, no values. I've also defined, you know, maybe I'm a quality engineer. Maybe this is a manufacturing engineering task, you know, that what is the value that we're looking for for it to be a conforming, answer? And then this is going again to drive the, the execution process and the collection of that data. And then if you have any in process buy offs or sign offs, you can define, what those instructions are and which roles. So the roles, again, are configurable. You make these dependent on what your roles in your organization are and who needs to have that sign off ability. Here, I have a quality manager and a production manager required for for this sign off. Okay? So that's great. Jason, fantastic. We're about to hand it over to Niranjan, but do we have a way of viewing all of this, in in a single view? Of course, we do. We could look at some of our, web based tools for you know, before we release this to the shop floor for for execution to review all of the the behaviors that we saw. You know? Here we see that alert behavior. Here we see on the right hand side the text. We also can view the parts list for the active step with cross highlighting. This is a fully three d view. So all the things that you would need to see this kind of in a what you see is what you get. Now the way that this looks on the shop floor is, you know, gonna be tailored to that operator experience or that work cell. But this is a great review tool for us on the engineering side to make sure that this is a complete definition exactly the way that we that we want it to be. So, as far as the model based and the traceability, we didn't get into requirements, but that's another aspect of the the platform that, again, I wanted to to bring this home with this digital continuity. We have this work plan that we started with. This work plan is actually responsible for producing this manufactured item and all of its children structure underneath it. That manufactured item is actually scoped to our engineering structure. Our engineering structure is, actually implementing a requirement specification, and so is that work plan as you can see that traceability link there. So all of these relationships are exposed because all of these verticals that have done this work, engineering, manufacturing, model based systems engineering, they're all model based structures, and these relationships are being built by the system in real time. So as we look at three specific requirements that we allocated to this very specific step of this very specific operation in this very specific work plan, all the way upstream and downstream, back and forth. We have exposure to these relations and, and can interrogate them and use them, to make informed decisions and to understand the impacts of change. So, to wrap this up, I'm gonna turn it over to Niranjan very quickly where he can, share a sneak peek of what this looks like inside of, our execution system. So, Goranjan. Alright. Thank you, Jason. And, I'm going to share my screen here. So what Jason showed is, is, you know, the design time or the manufacturing engineer's view of how they create process plans and and work instructions and the m bomb. Now, typically, in a in an environment in a customer environment, there is the ERP system that generates the work orders and then releases them to the shop floor. So most of what I'm gonna show today as a sneak peek for part two, that happens in the background. But say for some rare cases where there is no ERP, we don't have too many of those. But, if you don't have any ERP, then Appraisal can create work orders, on its own. So I'm gonna show you a quick, example of how I use Jason's processes to create a work order based on those processes. So I have a small screen here, and I can hit this create order button. And I select the order type I want. Again, this typically does not happen manually. This is happening in the background with the ERP system. But I select the part number, which is the data assembly that Jason was working on. I set a scheduled start date. Say, for example, I want to start this at, say, 11AM and end it again somewhere around 11AM of the next day or two days later. I set up a quantity. And now what I'm doing is I'm using the process plan, the work plan that Jason offered on the three d experience side to create this order. And I this is making a live connection to three d experience, and I select that process plan here. And, I hit this create button. That would create the order. Now, again, this happens in the background usually. So, the user does not interact with this system. What the users will see once the ERP has released the order to the floor is the user can go as an operator and look at the tasks that are assigned to that operator and work on those tasks. So that will be part of the part two of this webinar, which is coming up, around So I created this order here, as you can see. I'll quickly show you. There is the same structure that Jason created here. There is operation 10. All the information about that order is now in the system here in Appreaso. And there is the, parallel operations, then the quality operation, and then the, last operation here. So completely, taken the data from the manufacturing engineering side of things and created this order. So more of more to come, in part two, so stay tuned. That's great. Yeah. Thanks, Nirajan. So, yeah, go ahead and stop sharing your screen, and I'll finish up with just a couple of things. And, at this point, we will open up to q and a if, any additional q and a, or any questions need to be, asked. Let me go ahead and share my screen again. So in summary, what we showed today, part one was all about engineering, manufacturing engineering. Starting from that, SolidWorks, CATIA, ProE, Creo, Inventor, whatever whatever CAD data being managed on the platform, how we can have access to that, consume it, create our MBOM or items master, restructure it independently of the of the engineering, keeping those links and add things that are relevant to us, and maintaining that digital continuity. So we're that compliance that enforced compliance. We developed a process plan with flows. We consumed our MBOM into that process. I showed how we can, maintain and leverage that digital continuity with engineering to incorporate changes. We defined a complete executable recipe for the where, the who's, the what, the how, the when. We enriched it with some work instructions. And then as Narayan showed, we got a sneak peek here of, what we're gonna do in part two, which is execute that template. So for, any of you who have not yet signed up for part two, it is coming up on Feb. 19. I've got a handy QR code here for you. If you, are interested in that and you have not yet signed up, that'll take you right to the registration link. We appreciate, yeah, that we're right at the end of our time here, so, I don't see any questions that weren't already answered specifically in the chat. So with that, we will end our session today. Thank you very much for your time, and we hope to see you on part two. Goodbye. Thank you.