Over the next few moments, we're going to take a look at the Tremec SolidWorks property tool. Once launched, I'm going to start by scanning folder of data. So I'll just direct it to a folder where I know there's some files I want to extract the metadata from. I can choose the filter based on file type. Choose the output format which could be Excel. In this case, we've also got XML or JSON and text files if we choose. And I'll generate that file as soon as that is finished. Didn't take very long. I can open that straight up and I can look at the results. You'll notice a number of column headers for each of these files, including the file name. File name also includes the full path. So I am working within a group a bunch of data where there may be duplicate file names. I can still update those files based on the full path. There's also internal SolidWorks properties and custom properties. You will notice some intentional gaps in my data here, which I'm going to populate. But whilst we're doing that, I'm just going to touch on the fact that you may notice under the weight column and the material column some syntax. So where there's some values, there's also just S.W. mass and S.W. material. That's because I chose the option to export the data not based on the evaluated value, but on the syntax itself. The benefit of that is that when I populate those files now based off that file, it it's ready to read the information from the Solr works physical properties of the file. Okay. So it doesn't take very long to populate the files. You'll notice there is another option on that form to delete custom properties. I actually did that as part of the updating of the properties in this case. So I didn't need to run that, but any fields I'd removed the metadata from it would have deleted that custom property as well. For me. As part of that, back in my PDM vault, I've created a project in my legacy folder area which I'm dragging those files into. The reason I've chosen legacy is I've got a bit more flex and control as to how I bring this data in, for example, overwriting the revision on the data card and not assigning a new part number as a default value on the data card, and so You can see in the example that where we've got things like S.W. material, S.W. mass, they're probably files that I've just generated that information into, but I still need to or may want to synchronize that data from the Solo works model. So I can just quickly open one of these files. And once opened, all I really need to do is just save that file. And if that file has a material assigned, then it's all In this case though, when we do look at the data card, we can see in the feature manager that actually isn't a material assigned at this stage. However, because the syntax is already being populated, I can go ahead, assign a material, hit save, and we're going to see that come through. Now on to the data card along with the mass. You also spot a drop list at the bottom of that page for status. That's something we're going to use as part of the lifecycle process. When we push the data that we've brought in through into the prime primary workflow within our system. Before that, let's just take a quick look at a drawing and just show how we can reinforce that in the same way. I've got a drawing which is a model linked to it. If the model had its properties not fully populated and they're used in the drawing border, then I may just want to synchronize everything back to the data card here as well. Coming back to that drop list, you'll see I've got two options I've got approved and I've got work in progress under And in this case I'm going to leave it as approved, which is actually the default on the data card. And what that means is I am assuming that when I bring in a folder into the legacy, into the legacy folder structure, and I push that into the workflow, the destination of those files will be approved. Now I can change that. As you saw there, I could choose that to be work in progress. the outcome would essentially be, let's say it had revision C on the data card. If it says approved, it's going to get stamped as revision C and be approved. If it says work in progress, it's actually stamped in the background has only been a revision B, then when it's subsequently approved because it's added work in progress, it gets released at revision C. Just completing this transition. Now we can see there's no errors as we would expect, because we just simply drag this data in to the vault. And when we expect the data card, there is the revision C that we were hoping to see based on what we've just discussed with the the legacy information and the ability to pre prepare that data or post-process that data after dragging it in. So there hopefully you can see how useful that would be in preparing your data prior to a data migration. Thank you.