Video: Closing the Loop from Engineering to Manufacturing Execution with DELMIA - Part 2 | Duration: 3318s | Summary: Closing the Loop from Engineering to Manufacturing Execution with DELMIA - Part 2 | Chapters: Welcome and Recap (0.2799997000000003s), Aprizo Portal Login (426.39000000000004s), Reporting Quality Issues (829.1650300000001s), Machine Integrator Functionality (1186.6899s), Parallel Operations Workflow (1543s), Quality Control Process (1836.6799s), Manufacturing Record Review (2262.625s), Dashboards and Visualization (2500.61s), Conclusion and Q&A (2938.91s)
Transcript for "Closing the Loop from Engineering to Manufacturing Execution with DELMIA - Part 2": Hello, everyone, and welcome to our webinar today. Thanks for joining. I'm Jason Curtis, director of engineering for GoEngineer. I'm joined by Niranjan Kalele, who is the director of our MES, MOM and advanced production scheduling systems. Quick bit of housekeeping. If you would like to engage with us, feel free to use the chat panel on the right hand side of the screen as well as the q and a panel for any questions that you would like us to address, answer for you, or follow-up on after today's presentation. So this is part two of a two part series. So we've come to coming to the conclusion of our, message that we want to share with you. In part one, we covered the engineering, definition of the manufacturing plan, the MBOM, and the work instructions. And today, we're going to cover what that looks like in the execution system. Now for those of you who may not have, seen part one, let me do just a quick recap for you, because this is going to feed into our demonstration today, which is how we're going to execute that which we have authored. So we showed last time the values of, storing your engineering item definition. In this case, it could be a SolidWorks model. It could be a CATIA model. It could be any any three d CAD, storing it in the three d experience platform. The main point here being that in manufacturing engineering domain, we have access to all of this same information in real time, no duplicates of this information, so that we can begin to do things like make our own model based structures from this. So we we showed the values and the the, significance of being able to create a model based manufactured item structure, more commonly known as the MBOM, but also maintain digital continuity back to the EBOM or the engineering item structure. Once we define this either from the items that were in the, CAD design or including items that did not, exist in the CAD design to complete our bill of material definition, we turn that into an actionable process where we consume these items along with some resources, whether those are tools, skills, work center locations, whatever is necessary to define the recipe that we want to execute and the behaviors that we wanna see, exhibited on the shop floor to control the process. And not just control the process, but control the quality of the execution. So, in our example, we created a simple, system or work plan where we're starting in a, in a single operation. Once that is completed, it will split into a parallel operation. And once both of those are completed, then we will, come back down to a single quality step. We also allocated work centers and skills to these so that you can see how on the shop floor we can make sure that the right information gets to exactly the right place and only that place at exactly the right time, and other filtering mechanisms such as if you don't have the right skill to work on it, then you won't be able to participate in that, just to help control quality and the on the shop floor. With the quality steps, we also are going to need some instructions or some other behaviors that might help the operator understand what they need to do, the quality controls that they need to, adhere to, and any other notifications. So, very quickly, you're going to see today us processing through this, this work plan. You'll see the same steps and data that I have authored here, same behaviors such as things like, an alert message that, you'll see that, we've we showed the ability to include things like links to external documents, and, you know, rich text type of instructions with images or, you know, instructions for how to perform the work as well as the graphical images if, if an operation, requires that to help, describe the work that's to be done. You'll also see some data collection, attributes where we are requesting from the operator or from a digitally connected torque tool in this case, some values to collect and what we can do with that data, as well as if we jump forward, you'll see some things like data quality checklists and, sign off steps, that are meant to, again, control the quality, help us to define what what it is in fact that we, want to control, and, again, to have this recipe by which we are going to execute. So all of this was done in part one. If that is of interest, if you wanna see more detail, you can watch that recording. But today, we're gonna focus specifically on the execution side, being digitally connected to this, consuming this, reusing this information to drive execution on the shop floor. So at this point, Niranjan, I'm gonna turn it over to you, and you can begin our presentation for today. Alright. Thank you, Jason. Alright. So welcome, everyone. Jason gave a quick recap of, what we discussed in, part one of this, series webinar series, where he, authored the process plan to manufacture the radome assembly. What I am going to show actually, at the end of the part one, I also showed how we created an a work order in Aprizo based on that, process plan that Jason offered. In part two, what I'm gonna show is how we execute that order, in Aprizo. So in part one, you saw the engineering view, the manufacturing engineering view of the process plan. What I'm gonna show you today is the operator's view of the execution of that, work order. So, I have a browser screen here. Aprizo, is basically accessed the portal is accessed through a browser. It also has mobile apps. If you have a mobile device on the shop floor, it has the iOS and the Android apps, which you can download from the respective app store and access Aprizo through them through them. Right now, I have a Chrome browser, and it's just a URL to access it. So I'm going to log in into the portal, the Aprizo portal. I have a few options here. I can have a standard login, which is basically a username and password. I can also configure, an RFID badge for operators. If they use a badge to get into the building, we can have an RFID scanner attached to the computer, and we can actually configure that badge so that they can just swipe in and get in. There is equipment login, which is mainly used by warehouse operators where they constantly operate a forklift or something. Then you can log in with that equipment. Of course, there is integrated Windows authentication. So once they log in into Windows, you can log in into Aprizo as well. In fact, it supports, a lot of LDAP, login app applications. And, also, we have a three d passport login. So if you have users common between three d experience and Aprizo, they can just use their three d experience login ID. I am today going to just log in using a user ID and password. So I am going in as operator one. So as soon as I get in here, the screen I see is catered to who I am, what access I have, what skill sets I have, and what works look work center or work location I'm working in. So right now, I'm operator one with a certain set of skills, the assembly operator level one skill. And, I see this order that we created, in part one. I see an order to be executed, operation 10 to be executed. The display or the information that is rendered to the user is configurable. The, you know, the layout of the screen, the kind of information that is shown on this tile, the layout of the tile itself, it can be a horizontal tile, or horizontal rows in instead of a vertical tile. All the information showed on the tile, everything is configurable. So you can add or remove information that, you know, to to suit your needs. So right now, I see this work order here, 143006Operation10, and I'm going to click on it. Now I get into this, screen which we call execution cockpit where, at the top, I see all the header information about this operation. On the left hand side, I see, some tabs, which I'll get into later. And the main area is the content of my work. I also have on the right hand top corner here, the start operation button. Now when I click the start operation button, I can start the operation. Now this operation has one, two, and three steps. So I have to do those steps in in sequence. As soon as I click the start operation button, Aprizo can optionally start labor in my name against this operation against this work order operation. I said optionally because Aprizo has a lot of functionality, and you don't necessarily have to implement everything all at once. But if you do implement, labor, it's, it can optionally start labor, in the background. Just, this is gonna be the theme, for the operator here that there are a lot of things that can happen in the background without the operator physically moving away from the screen so that the operator can focus on what they need to do and not worry about doing transactions in the system. So right now, I started this, operation, and now I'm gonna start step one. As soon as I start step one, I am being shown this alert. And, this is basically an, foreign object debris's, required PPE, information that the manufacturing engineer, Jason, wanted me to see and acknowledge before I do anything else. Right? And he has certain docs attached to it so that I can actually click on it and read up on it if I need to. Same thing here. I can read up read up on these PDFs. So I get up to date information based on what the manufacturing engineer has offered. I I know this. I have now I I understand what this, alert is about, so I can acknowledge that. And until I acknowledge, I cannot proceed. So I acknowledge this alert. And now I see my work content. What I can see here is there is a component that I need to issue and then there are some work instructions. So I can look through the work instructions here. So say prepare the work area for assembly, load the bulkhead, and then clean the mounting face. So I see this component. I need to issue this component. So what I'm going to do is I'm going to issue this. But to issue this component, I have to enter a serial number because this is a serialized part. So I can actually enter the serial number manually here, but I have fat fingers, so I can make a mistake. Wherever I can enter manually, I can also scan. So I have a barcode printed here with the serial numbers. So I and I have a barcode web scanner attached to my laptop. So I can just scan the barcode, and that's what I'm going to do so not so as to not make any mistakes. So let's see here. This is the power cord for that part. I am just gonna scan that one. And there it is. As soon as I scan this serial number, a few things happen in the background again. You know? There is this part that is getting issued to the work order. So there is a work order issue transaction that happens. If you have, AppEEZO warehouse enabled, it can also deplete inventory from, the location the inventory location, the line side location. And it can also send interface records to external systems. Say you have implemented warehousing and external warehousing system, then it can send an interface to that. It can send an interface to ERP that this part number has been issued. So, a whole bunch of transactions can happen in the background by the operator just scanning, the serial number of that part. So I scan this serial number, and, I'm looking at it and it's I'm trying to follow these instructions. And it says, you know, clean the mounting surface. So while I'm cleaning this mounting surface, I see some sort of a problem, because I'm not able to clean a particular area of this bulkhead. So right here, what I can do is I can hit this exclamation icon, and I can report nonconformance. So right here, I can actually say what the severity of the defect is. Right? I can enter my comments. I can choose a reason code. If I have a mobile device with a camera on it, I can even take a picture and attach it to this defect. The component part number and the revision is already entered for me, so I don't have to enter that. So I can report this nonconformance by adding all this text. But I can do one better as well. You know, there is a tab here called visual quality defects. So I can actually go in here, and I see an image of the bulkhead. And what I can do here is I can select the severity. Say, for example, I want to report a minor defect and, say there was a let's say there is a scratch here. So I can select the reason called scratched, and I can just point and click. And that creates a defect in the database at that location of the bulkhead that there is a scratch. Right? And I'm trying to clean it with, you know, a piece of cloth or anything, and it it's not going away. So that's why I want to report this defect. So maybe, you know, the depending on the severity of the defect, what I can do is I can actually, call the engineer, or call my supervisor and say, what do I need to do here? Can I proceed? Or call the quality guys, you know? Or, you know, if it is not a bigger issue, I can say, okay. This is a minor issue. I can maybe proceed. Depending on whatever business rule you want to implement, you can implement that business rule, in Aprizo. It's configurable in that, extent. So what I can do here is, okay, I called the engineer and I said, you know, this is not going away to scratch. And then the engineer told me that, hey. Use isopropyl alcohol, and you can remove it. So I did that, but then I went back again here. And, I see that in the instructions, it says clean the mounting face of the bulkhead. It does not say how I should clean it, whether I can use alcohol or no. It doesn't say that. So maybe I want to even, you know, report a defect on the work instructions. So I can actually hit this icon again next to the work instruction, and I can report that. Now the the component is NA, but the work instruction object on the engineering side is selected. So I can, report a defect against the work instruction saying, hey. This work instruction is not clear. If you had mentioned that I can clean with isopropyl alcohol, maybe I would not need to call you. So I can report a defect here, and then it can actually follow a closed loop where it gets sent to engineering, and then engineering can fix the work instruction and come back to Aprize. So all this functionality is available. As you can see here, there is a defect that I have already reported, which is the scratch. I can resolve that, in the quality module, or I can actually have somebody sign off on it. Whatever workflow I want to follow there, I can follow. So moving on, this this defect I could, I could remove. So I will move on. I can use this, as is. And so I'm gonna complete this particular step. And now I am here on the second step. Let's look at the work instructions here. Oh, it has some work instructions, but it also has a video. So in this is a video that is embedded by the, manufacturing engineer, Jason, in this case. And he is basically showing me how to do this through a video. So I can click on it. It's a YouTube video. I can click on it and watch the video. If I'm familiar enough with this, I can just do it. So for that, first thing I need is I need a talk tool. Now I have a set of talk tools with me, so I can select them from the drop down, or I can actually if there are more talk tools and I it and and drop down would be too big, I can actually scan the tool signal number as well. So right now, I just have two, so I'm gonna select that and report that I'm using that tool. And then I have to, issue out these parts, screw, support bracket, and washer. And these are not serial control, but they are lot controls. So I need to scan the lot numbers. So, again, I have bar codes for each of these, so I'm gonna scan those. So starting with 1115, which is right here, and then 19O1, which is right here, and then 1117, which is right here. Alright. So I issued all these lot numbers in these quantities, and that's, I I did I I issued all these parts. And now what I need to do here is I need to torque this to 15 newton meters. So, the manufacturing engineer has asked me to collect how many readings, you know. Here he has asked me to collect two readings. He has been kind to me and not asked me to collect all 16 or 32, whatever that number is. So I'm just gonna show you token of how I can collect, top ratings. I can actually enter the value manually here, but Appreizio has a module called Machine Integrator. What it does is it can if the top tool is a smart tool, it can connect to that tool using OPC server and read off the torque readings from that tool directly, automatically, so that the operator doesn't have to enter those. Machine integrator does support two way communications. So not only can it read readings from tools and machines, but it can also send commands, programs to those machines to to execute. So it supports two way communication and it is machine vendor agnostic. So as long as your machine or tool can connect to an OPC server, it doesn't matter where you buy that machine or tool. You know, Aprizo can connect to it. So, very powerful, machine integrator functionality here. I can also I need to collect one more value, so I'm gonna enter that manually again. And now I have collected all the values that the manufacturing engineer wants me to. And so now I can finish step two and then move on to step three. Now in step three again, I have to issue a few more components here, screws and brackets. And, I need to collect some data collect values as well. So let's look at that. And I'm gonna scan the lot number for that, which is right here. And few more. 19O2, which is right here. And 1117, which is again right here. So I issued all these parts. Again, this is the secondary bracket. And here, I have to torque it to 10 newton meters. So I torque it. I can actually also see how I'm doing. So the lower and upper control limits are nine and eleven. So anything between nine and eleven, I would have been fine. Anything beyond that, I would have had to get some quality people to approve of that or maybe remove and retalk. But that's the information that you can choose to show to the operator, or you can have him do the blind, reading so that they don't get influenced. They just they are just told the target value and then they talk the, based on that target value. So I have now done all the instructions that, were shown here. And so now I'm completed. I've completed step three, so I can complete that. And, now all the three steps in this operation are complete. So then I can actually complete the entire operation here. As soon as I complete that, I have, a few options here. I can complete good so that it can move to the next operation. If something failed, I can actually stop this, work order by just reporting failed, or reporting scrap. Maybe I just dropped it and broke it. So maybe I have to report scrap. Or if there is an alternate path that has been predefined by the manufacturing engineer, I can use that path with the reason code and follow that path. Right now, I'm just going to report good, but just wanted to show that these are the options available to the operator. So right now, I'm going to report good. As soon as I click this button here, I'm going to close this operation report this operation complete. At the same time, optionally, if I had started labor on the operation, I can also stop labor. That way, you know, the actual time the exact actual time, real time of what the operator spent on the operation is captured by Appreaser. So, again, all these transactions are being done without me leaving the operator screen. As you can see, I did not log in into a separate warehouse system to do inventory transactions, a separate time tracking system or labor tracking system to do labor transactions. I'm doing everything in one system. And and the back in the background, Aprizo is one unified database where all these, you know, all these data is stored in one database. It's not set although there are licenses for production and and, quality and, time and labor and all that, the data is all stored in one database. So I complete this operation, and operation 10 is complete. I should see the next operation, but I don't. The reason why I don't see that operation is because either I don't have the skill set to work on those operation or I'm not in the right location to work on that operation. In either case, I don't have access to those next operations, so I am going to log out and log in as operator two. And now as soon as I log in as operator two, I see not one but two operations. The reason I see both these operations is because these are designated as parallel operations by the manufacturing engineer, Jason. So he showed you the diagram at the top here where one operation then moves to the set of parallel operations, operation twenty and thirty. So I see those two operations here. And because they are parallel, I can actually work them in any order. It doesn't matter. Right? So, I have access and skill set to perform both of these. So I can just pick one and start working on that. So here again, I see operation 20, and I can start that operation. Look at these work instructions here. So this is basically the chassis assembly instruction here, and I have very detailed instructions as to how I should do this. So I can actually first thing I need to do is I need to issue this chassis. So it is a serial control part. I need to scan the serial number. So I'm gonna scan this number here, barcode. And as soon as I scan this, all this information about who am I, now I'm operator two, what time I'm in Pacific time zone. So what time did I scan it, and what was the serial number of this part? All this inform and the quantity. Because it's a serial control, it's always one. All this information is captured in the system. And in the background, it is building a relationship between parent serial number and the child serial number. So we will see that at the end how that relationship is built, the whole genealogy and the traceability of this manufacturing, of this assembly. So I have issued this serial number. So I now follow these instructions to assemble it all the way down. And once I'm done, I'm ready to complete this particular operation. So I complete. And complete good. Now I completed option 20, but until I complete option 30, I cannot see the next operation because both these parallel operations have to be completed before I can move on to the next one. So now I'm going into operation 30. Here, again, I start the operation. Every time I start the operation, again, it can optionally start a label record. And here, all I need to do is attach this serial number label. So I have a label that I can print out or maybe it's a stock item. And this serial number tag, I just have to, you know, paste it in at this location here. It's telling me what location I need to paste that tag. Now, this tag is not neither serial nor lot control. I just need one tag. So, I basically say, okay, I picked up a tag and I have pasted it here. Once I complete that, I can complete this operation. And once I complete that, now I have both twenty and thirty complete. Now I should see operation 40, but I don't see it. Again, the same reason because operation 40, I had probably don't have the skill set to do it, and maybe I'm not even in the right work center. So either of those reasons, I don't see the operation. So this is poke yoke. This is, manufacturing engineer controlling and governing what operations can be performed by whom and what skill set is required. So I if I don't have the skill set, I don't even see the operation. So I don't accidentally work on it. Right? It's completely, eliminating any errors right at the beginning. So I'm gonna log out from here and log in as operator three. And I see operation 40 right here. So now this is basically a quality assurance operation. So I click on it. Operator three is a quality person. So I can start here, this operation. And as soon as I start it, I see there is a checklist. So, Jason authored this checklist, and then when when he authored it, he actually said what is the conforming value and what is the nonconforming value. So he was kind to me and he basically said, okay. All yeses will be the conforming values. So I I'm basically reading these assembly is free of visual defects. Yes. Is free of FOD. Yes. Support brackets are installed correctly. Yes. Chassis has been installed correctly. Yes. And serial number tag is, secured correctly. Yes. But in real life, it would be good practice to have these answers jumbled up so that yes is not the conforming answer all the time so that people actually have to read and go through the checklist. They just can't do yes. Yes. Yes. And click. Okay. So, I have gone through all of these, and then I can actually complete this checklist here. And now I have to I have to do in I have to do the quality check. And I'm doing the visual quality, doing a visual inspection on it. And once I do the visual inspection, if there is a quality issue, okay, I can, call the quality people. I also have an option here that I can send an alert to, either my supervisor or to a quality person, and these can be preconfigured. So for the operator, you can actually configure that who the alert goes to, and you can actually send it to a group of people as well. So Aprizo has an alerting framework where an alert that I type in here, I see quality defects, quality issues, whatever. You know? They can type in, whatever message they want to type in, and that message can be delivered through the alerting framework on their supervisor or quality people's screens, quality engineer screens. So there is an alerting framework within Aprizo. You can also send an email. So if you configure an email server, and email addresses for every employee, you can actually have these sent as emails to those employees. You can also configure text messaging. You have you have to work with the carrier, and you'll have to have mobile phone numbers for everyone. But you can actually configure text messaging to send messages on their phones. So lot of options here. I can actually, use this alerting framework to send messages. Right now, I am, okay with it. I don't have I don't see any major visual defects. So what I'm going to do is I'm gonna proceed. And for proceeding, I need a sign off. So let's see here. I need a sign a signature from a quality manager and a production manager. Now these this is what, manufacturing engineer, Jason in this case, has configured for me to do. So I have to take a sign off from these two roles before I can complete this operation. So now I look for a quality manager and a production manager. And if the one person has both these roles, I can just invite that person, and they can sign off for both these roles. And that also can be controlled by, the manufacturing engineer. So say right now I call the quality manager, and they come in, and they have to scan their badge or they have to basically type in their user ID and password. So so I have a quality manager here. And as soon as I put in my user ID and badge, now this is the quality manager. It says, you know, this is the sign off that is required, and I'm looking at whatever roles I have. So if I even if I have multiple roles, if I don't want to sign off multiple roles, I can just pick that I'm signing as a quality manager, and you have to get another signature from a production manager. I can do that. Or I can say all available, which means everything that I have, I'm gonna approve. So right now, I only have quality managers, so nothing it doesn't really matter. So I'm just gonna approve this. So you can see here that quality manager has approved, but I still need a signature from production manager. So I call the production manager. They come in. Then they see the exact same screen. They can then sign off. And now I have both the signatures. I have a signature from production manager. I have a signature from quality manager. So now I'm ready to complete this operation. And I complete this operation. Good. And this, not only does it complete the operation, it also completes the work order. So all the operations are complete. It sends the req required interface records to the ERP, saying that work order is complete. You know, for each operation it sends at operation completion, it sends, operation completion messages to the ERP. All this is happening in the background. Aprizo has a module called business integrator, which will basically send messages to external systems. And it it it supports a lot of, a variety of adapters. So it supports, the very legacy adapter, which is flat file or positional, data in a file, all the way to the latest modern adapters, which is web services, rest APIs, and anything in between, you know, message queues, HTTPS, FTP, SFTP. All these protocols are, or even a direct database connection. All these protocols are available. So, a variety of, systems we can connect to using the business integrator. So these transactions can be sent to more than one systems at a time. And, you know, whatever systems need that transaction, it happens, in the background without the operator doing anything specific in that regard. So I have completed this particular order. Now I'm gonna show you the supervisor view of this. So I logged in as a supervisor now, and the first thing I want to see is that genealogy. So I created this assembly. Let's look at its genealogy. So this is the radome assembly. This is the product, and these are all the components that were issued. It's actually a two pager. So these are all the components that were issued to this assembly. And you can actually see it in a tree structure as well. So say, for example, this particular serial number, the bulkhead, and there were a bunch of lot numbers of this screw and then the bracket and then the washer and then again support bracket. And then the chassis was a serial control part. And then this was also a serial number, which is there is nothing. There is no serial or lot control. This is just a regular, part. So most importantly here, all the information regarding this traceability. So this serial number was issued by operator one, then there was other serial number that was issued by operator two. So whatever was done by what operator, at what time, against what work order operation, all this information is, captured here. And then all the inventory information. So say, for example, this particular serial number. This serial number was taken from this location. This was the container, and this is the serial number, obviously. So any inventory information is also captured in the system. So the database has all the information about what was issued and by whom and when. So complete traceability. Later on, if you have to, trace back as to where was this serial number or where was this lot number used, then you can actually as you can see here, this lot number, these are all the parent serial numbers that this lot number has gone into. So you can actually trace reverse as, okay, this particular, screw, this particular lot, maybe was faulty. So then you can actually trace back to what parents has it gone into, and then you can actually, recall them. So, complete traceability and genealogy. It also has genealogy history. So if later on, if you remove this part and then put a new one, it will capture that in the genealogy history as well. So complete genealogy and traceability. Let me show you the manufacturing record report electronic manufacturing record. So this is the order that we executed. It creates a comprehensive report of all the steps that we did, including the work instructions. So this is the order number. This was the the, alert that was shown to me. So it captures the at a detailed level what exactly happened during the manufacturing process. These are the work instructions, and, these were the, you know, the video was shown. These these were the components that were issued, and it's a comprehensive, report of what happened on the manufacturing floor. And this can get as detailed as you want. There is information like I showed you in the database, and you can actually make it as comprehensive as you want, on the electronic manufacturing record. So that is that. And then I wanna show you a few dashboards here. So, say, let's start with the the quality analysis dashboard. So I have here a dashboard which is built using the dashboard builder tool. So Aprizo has a dashboard builder where you can build your own dashboards. So all these data elements, are available to you, and then you can display them in context and in the widget that you want. So you can see here a few widgets here. There is a bar chart. There is a pie chart. There is a gauge, then there is a tabular data here. You can also have filters. You can actually select a product filter. Each of these panels, you can actually maximize to to have full screen, and then you can actually export these panels to a PDF file, say, to an image to be put on a PowerPoint for a presentation, or you can export it to Excel and then further slice and dice that data. So all these, options are available. And these options are available not just at the panel level, but maybe at the entire report level as well. So you can actually export the entire report. As you can see here, I put my logo here, our company logo. So you can customize these, the way you want them. So you can actually in the position of the panels, the gauges they use, I mean, the data that is displayed. You can also have cross filtering. So if you select one, here, then it filters data on the other panels. All kinds of options are there in the dashboard builder. So this is one dashboard. I'll show you another one that can be it can get as busy as you want. So you can see here, there are so many more panels. And then within that, there are more tabs here as well. And then there is tabular data underneath. So you can make this panel as busy as you want, and you can actually also have these displayed on the shop floor, if there are certain KPIs that everybody needs to know as motivation, maybe, that we are doing good or we're you know, we need to catch up, whatever. You can show these in the floor as well. Some more dashboards here. We have a module called MPI Lite. So with using that, you can actually have some of these, say, for example, the issue analysis, whatever issues were reported. You can have multiple colors. You know? You can have, you know, derived data like average resolution time, issue closed issue count, and so on. So and then also filter criteria. This is one. Let's see another one. Order analysis as well. So here again, multiple panels, different types of widgets, and multiple filters as well. So very comprehensive dashboarding tool that you can use to display your data. As you can see here, quality analysis, different types of quality metrics you could show, within your organization. And, also, we have some executive dashboards. So for I mean, these can be used by executives as well, but, say, you have a high level executive who wants to see what's going on in the facility. So you can actually have all your facilities put on a world map like this or whatever area you have the facilities in. You can put them on a map, and then the executives can drill down into, say, for example, the entire plant layout of that plant. And then you can have multiple lines or departments or however you want to divide that plant into. And you can have each individual, line or plant have those key performance indicators shown on this widget. So you can see at a glance how that particular department or line is doing. And then you can click on that, and you can drill down further into different, work centers, within that line or within that department. And you can have the key performance indicator that you want to see for those work centers. And then within that, if you click again, it further drifts down into that particular equipment. Or if there are many equipments and you or subequipment, it will show you all those in here. So you can see how it is using, say, for example, the energy or, you know, any kind of production, downtime, quality. All this information you can show at that equipment level. And then you can actually zoom that out. So from the equipment level to, say, that particular workstation level, these are the KPIs. And then at the entire facility level, at the department level, all the way up. So very comprehensive dashboards you can build using dashboard builder, and you can give this kind of, picture to your executives as well. So that is pretty much what I wanted to show. I am going to now open this for questions, and, you can ask questions, for both parts. If you remember what, or if you attended what Jason showed in part one, and the completion of the story in part two, You can actually ask any of those questions if you have them. Yeah. Thanks, Niranjan, for a great presentation. I will just briefly share, a closing summary of the key messages of our webinar series. If we had mentioned, we started part one by showing how we can reuse that engineering data once it's stored on a three d experience platform to leverage that existing informational asset that you're already creating to generate more model based structures on the platform, model based bill of material, model based bill of process, some model based work instructions. And as Narayanjan showed today in part two, how we use that to drive and control the execution and the quality of the production process. So as you were watching today, you noted that the operator interacted with time and labor, with MES execution, with, data collection, with warehouse, with quality. They never left the screen. So they were free to do their job to, be led in a, logical and controlled, way to make sure that they were achieving first time right or, you know, the quality metrics and contributing to the overall business, without ever having to leave their screen, without having to engage with a different tool set. So very efficient process. All of this with zero data loss, moving from engineering through to execution, through to these others business systems, and being able to provide that oversight at an executive level, at a supervisor level, and at engineering level, through monitoring real time dashboards and up to date results. So all of this, I hope you take took away, these key messages that, we have this digital continuity, this closed loop, and a very strong system and solution for integrating engineering all the way through execution. So thank you very much. With that, we're gonna take a look at some questions. First question, Naranjan, how can we create those dashboards? Does a can a user do it, or does it require an admin and a developer? Yeah. So, it does not require a developer, but it does require some level of understanding of data, as to what data you're showing or showing in the dashboard or what you want to show on the dashboard. So you need to probably understand, you know, what relationship that data is with, you know, with each other. So, like, say, for example, you are doing work order level data or you're doing operation level data or you're doing operator level data, how it relates to the other, other data in the system. You if you know that, then you can actually create those. So I would say super users can create those dashboards. It does not require, technical resources is what I want to say. And, also, you know, there is an MPI module which actually shows you some of these, gives you some of these, built in, facts and, you know, KPI terms already created for you, so you can use them in creating those dashboards as well. Fantastic. Thank you. Another question. And I may paraphrase this a little bit, so I hope I get the spirit of the question. But how would Aprizo or would Aprizo be able to interface with a complex legacy, data acquisition system or software data acquisition system? Could the data be accessed? Could that be leveraged inside of Aprizo? Yes. So, if you have, say, for example, a test stand or if you have some test equipment that creates a lot of data a lot of test data, you can actually connect to that, depending on if it has its own database or if it's just creating, that data or getting that data through a sensor. If it's getting the data through a sensor, you can actually use machine integrator to capture that data and store it on Prizo. If it has its own database, because there are some machines that actually have an Oracle database on it. If you have that, then you can actually use business integrator and connect to that system and get that data from there. So both those options are available. Business integrator and machine integrator are very powerful tools to acquire data from machines. Alright. And that looks like we maybe have one final question, but we will leave the questions open if there are any others that come in as we are answering this one. But, today, Niranjan, you showed how an operator interfaces with Aprizo. What if you have operations that are purely, machine centric. Can appraisal handle that as well? Yes. So, the machine events can be captured using machine integrators. So say you have a conveyor or you have, like, like, an assembly line moving automatically, then the event, that, makes you know, that that indicates the entry of that assembly into that work center, Aviso can capture that event. And then any kind of information that needs to be captured within that particular work center that can also be captured using machine integrator. When the assembly leaves that work center, a a place you can capture that event without user entering interacting in it, and then, send an operation completion message to the ERP. So all of this happening triggered by the machine events without the user actually doing anything on the keyboard. So please, you can do that using machine integrator. Fantastic. Alright. And one more came in. Today, we saw an example of an assembly process. Does Apprisio and three d experience also support, fabrication processes or, batch type of Absolutely. Absolutely. So, we definitely do support fabrication and various type of manufacturing, philosophies or manufacturing methods. We have a different fabrication console, which was not part of today's webinar, but, we have a fabrication console where you can actually, you know, report fabrication information. So if you have, if you're reporting quantities, and, you know, issuing material, you can actually capture all of that using the fabrication console. You can also do batch production, repetitive, manufacturing. All kinds of manufacturing is supported by Appreasil. Fantastic. Well, that looks like that is the end of our questions. We wanna thank you for your time. Appreciate you joining us, especially those who were able to join us for both sessions. Niranjan, great presentation. Thank you for joining us today as well. This will conclude our webinar. Please feel free to follow-up with us directly. Jason Curtis, and Naranjan Kalele from GoEngineer. And if you have any further questions, we'd be happy to help you with that. Otherwise, everyone have a great afternoon, great evening, and we will conclude the webinar now. Goodbye. Thank you very much, everyone. Thank you.