Okay. Well, welcome to another TrakSYS solution series video. I'm Ryan. I'm the director of product marketing here at Parsec. And today, we are discussing the TrakSYS solution studio and specifically the template transfer, template creation, all things templates functionality inside of TrakSYS. So I've got some slideware that we'll go over, and then I've got a little demo of some template stuff to show you. So let's let's jump into it. So first, you know, what is TrakSYS Solution Studio? And to boil it all down, it's basically a licensed instance of TrakSYS MES that is specifically used for template solution management and development. Okay? So you as a customer would buy TrakSYS, and you could then add a solution studio license to your to your subscription. And this would give you access to another instance of TrakSYS where you do this development for template development stuff. It's a little unique, this environment, where it's got unlimited features. So let's say you bought the bronze level or kind of the entry level version of TrakSYS. In the solution studio, you'd have access all the features of TrakSYS so you can play around with and develop templates and test out new functionality as it becomes available. That's pretty attractive. I will note one feature. Some of the AI features are not included in solution studio because it really is just meant for template development, but more on that at a different time. So users are included usually at the pay per user cost, the Solution Studio comes with twenty five concurrent users. There are also testing licenses included. So you're developing a template, you need to go test this template against different dataset before pushing down to your site, you can do that. There's licenses available to do that. And then you have access to the template transfer tooling inside of TrakSYS. That's what this video is really about today. What that means is that you can build, you can configure template content, you can then create, manage, and view the template definition, what is included in a definition of a template. We'll get into that in a little bit too. And then, really, the the the main thing here is how are you gonna export, import, develop, branch, merge changes of these templates back into the main main template or down to other sites? And that's what that's what we're gonna show you today. Okay. So first, why does templatization matter for manufacturers? Why are we even talking about this topic? Well, it allows you to deploy faster across multiple sites. Right? You can create a solution once and then use that in multiple areas and manage that in one location. Right? So it helps with just that solution development and rolling out across lines, across sites, that sort of thing, which we all start small, expand. Right? We're ensuring that every plant, every area follows the same process. Right? We can build the solution. We can iterate on that solution. And that's really the way you wanna go. You don't wanna create these ad hoc changes all over the place. It'll be become a nightmare to manage. And so you build a solution. You export that out. Of course, we allow for tweaks. It's kind of part of the process, but we try to manage that as a package as as much as we can. You know, we're by doing this, manufacturers are reducing risk, reducing cost. They don't have implementations, because they don't have to skyrocket. We can build a template. We can push it down to sites. And then sites have the ability to kinda tweak things at that endpoint as needed. So do the do the the brunt of the work up front, allow some tweaking down downstream, and then, of course, you know, manage manage that tweaking. Yeah. So we can you know, keeping all sites up to date is important. How do you know what version a site is on? What template version they're on? Right? We want we want to create a process where distributing changes as needed is governed, is visual, is Everyone is staying on the same page here. So that's one of the main points here. And then, of course, you may have an organization that's large enough to have multiple developers for your MES solution. Maybe one developer's working on-site A, maybe one's working on-site B, Maybe one's working on a batching area. Maybe one's working on a packaging area, developing screens for that. We wanna support that process that you have where each developer can kinda do their own thing in their own branch of the software and then merge their changes back into the main branch. Alright? So that's why templatization matters. Helps with scale, helps, mostly just scale and implement quicker. Alright? So the TrakSYS template transfer tool, and what that does is it allows you to package up certain pages, certain scripts inside of TrakSYS. It lets you then version each time you do that or each time you export a package. That package is gonna be versioned, you can always roll back and then, of course, see what's what's changed. And then it allows you to take that and deploy that specific version, that package version to a site, to multiple sites, that sort of thing. So we're managing that process inside of TrakSYS now. So I've got some screenshots of what this looks like. So I'll go through those, and then, of course, we will we'll dive into this in the demo in a little bit. But alright. So we can create inversion solution templates. What does that mean? You can build reasonable template configuration pages, logic, anything. Inside, you can kinda see in the background here, inside of every data entity inside of TrakSYS, there's a field called template data. So you put a string of sites, keys, you know, whatever in there, and that defines that this particular part of the TrakSYS solution is associated with this particular site. Okay. When you create your template definition, similar looking little dialog here, you're putting in that definition what keys it should look for. So you could create a template definition for site a. You say, hey. Only go look at the site a stuff inside of my development environment. And so you get the idea. You can build different templates. Sorry, definitions of templates. So you're using one TrakSYS system, creating multiple template definitions. Those definitions are pulling specific pieces out of that system to be deployed some other place, right? You're very easily, right, I mean, just kind of going off what I just said, being able to select what to mark and package for reuse, right? And you can easily see that. So inside of TrakSYS, there are screens that help you see what's been marked as a particular key. Right? So if I go into my TrakSYS into my definitions for templates inside of TrakSYS, I say, okay, show me all the site A stuff. I get a nice list view of what's included in site a, you know, what what particular parts, pages, event categories, what whatever, what have you. The way templates are exported, they get exported to a file. Okay? So I'm in my source template development system. I go into my template screen. I hit export. What it does is it runs a report for me, it tells me what's been exported. It versions the template up and it creates a file for me with an extension TTT, Template Transfer Tool. And so now I can take that file and move it over to, a system that's running a site, whatever site I want, and then import that into that site, import those changes. Okay? Now what's really cool is when I do that import process, I can now see what I've changed. All right? So developers will expect this, right, because they're used to change control and seeing the changes compared in real time. So TrakSYS is now doing the same thing where I bring that template over to my site and I can there's a report that tells me what entities have changed so I don't have to look through everything. I can just quickly go to, oh, look. Hey. The four entities were updated. One was deleted. A hundred and thirty nine entities had no change. And then I can click on each of these entities and basically get a compare, a a compare screen so I can validate and say, oh, okay. Look at this. I changed I changed an icon on this one from a cog to a to a TrakSYS icon, a batch. Okay? Like I said, because we have a file, we can now easily take that file and load it into whatever site we want. And, yeah, just makes it makes it pretty easy to to transfer this stuff around. Something that's also related to this, which I don't know if we'll get into this video, but I wanted to mention at least at a high level is that you can mark certain sections in TrakSYS. Remember a section in TrakSYS is what's under kind of the is is the top level version of a page. Okay? We call them sections. And anyway, can create deployable sections. So if I let's say I have a a section of pages that are associated with my packaging area, but it's directly related to how I want my batching or tableting or, you know, staging area to look, I can take that page. I can basically deploy it and duplicate it and, set a couple configuration keys on it, and there I go. I've I've basically, converted my my packaging area into a templating area, least from a screen perspective. And so anyway, that's something more. We'll we'll touch on that more in the future. And then like I said, each site has some control. If they go in and change a page and they don't want the template to overwrite it when they import, there's kind of a safeguard here on every page where it's called a template bypass. So if this is marked as true, any template coming in that is gonna reference that page that wants to overwrite it, it will just ignore ignore the overwrite and won't get overwritten. So so anyway, local sites have that control. Okay. So we'll demo all that in a little bit. I just want to get through kind of what are some supported scenarios for this. And these are basically the three main ones. So you might have new site expansion. You need to modify your template to meet some needs in that new site that are other that your other sites didn't have. So that's one scenario. You wanna do some version testing. Right? Maybe you've updated the version of your template you wanna test it. Maybe TrakSYS has a new version out and you wanna make sure your templates work with a new version of of TrakSYS. There's a scenario for that. And then one kinda new ish one that that we've we've kind of adopted here or supported is the ability to have individual developers working on different branches of the TrakSYS template and then being able to merge and select what what goes back into the main branch. Okay? Now, I won't get too much into this today, but there are different licenses required to do some of these different scenarios. They're called template, test, branch, solo. You'll get the idea when we go through the next couple of slides, but just know that templating, the template core licenses is the main solution studio license that's needed. Alright. So here's some basic template architecture. Right? I'll kind of orient you here. Let me see if I can turn on my laser pointer. So up here is our development our development server, template development server. It's got our core license. I said at the beginning that every core solution studio license comes with a test license. So you'd be able to take your template changes, export them, import them into a different environment for testing purposes. Totally fine. A lot of our customers do that today. So this is kind of the the main structure. And then, of course, from that main template development instance, you're then porting down to your different sites. Once your templates get down to your sites, you're using a different tool that we have called our database transfer tool to kind of move those changes through, some non production environments at the sites down to the production instance. Okay? That's the general idea of how this works. And let's talk about some different scenarios. So with new set expansion, you probably want to let me hide my video here if I can take my teleprompter. Well, I don't know how to do that. So we won't worry about it. I'm kinda hiding the site down here, but I'll just I'll I'll kinda tell you what it is. So yeah. So you have your main development area. You might wanna take a branch of that code, copy that code so that other developers can work on that. It's called a branch license. Right? A branch development area. So that's another type of license there. You create the branch. A different implementation team over here will be building that template to meet to to satisfy the need at the site that new site. When they're done, I mean, they can kinda export import as needed to that new site. When they're done their changes, they can merge that back into the into the main trunk, and then that can go down to the other production sites. Right? So that is supported with with this new architecture here. Of course, if you're very similar, if you're testing a new version of TrakSYS, you just wanna kinda develop some stuff to use some new features inside of a new version of TrakSYS, you can do that as well. Take a branch, modify, merge it back in, do some do some versioning updates there, and you're ready to go. And then the last one I'll just present here is if we needed to have multiple developers working on different pieces of the TrakSYS template. Now remember, most of the licenses come with twenty five users, but if you wanna segment those users out specifically so they're not stepping on each other, then you can do it this way where you create multiple branches of the core, of the of the template development area. Each, you'd have multiple development, servers, each with a solo license or combination of branch solo license, they're doing updates. They're merging back into the core core template as well. So that is also supported. There's some there's some branch and merge functionality that I won't demo today, but, you know, essentially, you import your template in back into the main branch, it's gonna let you kinda pick and choose, you know, do you wanna go with the change? Do you not wanna go with the change? You know, for each of those changed entities and let you review that. So that's the idea. Okay. Let's get into a little bit of a demonstration here, and let's jump over to my demo machine. Okay. So let's move this over just so my face doesn't get in the way. So just to orient you here, we've got a TrakSYS two TrakSYS instances set up here. I've got them separated at the top here. I wanna go full screen as much as I can, but there's a source TrakSYS, so this is where my template development area is. And there's a target TrakSYS. This is where I'm going to move my template to this target. Okay? So inside my template development area, under the development, set of pages, there's a new templates area, and I can click on definitions. This is where I've come and I've defined my template. Now let's open this up and just kinda get a view of that screen. This is the screen you saw on the PowerPoint. So what this is doing, it says, okay. I've defined a template for Orange County vitamin. This is my site. And I'm saying, look at entities inside of TrakSYS that match these values. Alright? Every remember, every entity inside of TrakSYS, you're able to basically write out a key. So it's looking for these keys. There's some other settings and stuff like that, but that's essentially all you have to do. And now what you can do is you can you can now well, first, you can look at the contents of this template. So if I click on content here, it's gonna show me all of the entities that are included or that match that template key. Okay? And you'll see here that it was matching an OCV and OEE. And so this is basically a report that says, hey. Look. What's in your template? I can come down here to this event category. I can view it and say, oh, look at this. Wow. All this stuff is gonna be included in my template that matches. And so it gives you, like, a verification step of when you're, you know, when you're setting up your template. Hey. Did I miss did I miss adding this entity? Okay. Let's go back and add it. Right? Alright. Let's export this template. So I'm ready to, basically bump the version up. I'm gonna do an export export template. Let's call it Ryan's export. And let's hit it. And so now it's going through and it's building, essentially building a file in the background. So here's a result. Says the template export is completed. It's you know, lets me kinda review the logs of what it did so I can always go and see if there's any errors and what I need to do to fix it. And okay. I'm happy with that. It's all it versioned up to version nine. I'm gonna download that content. Right? So this is where it creates that file for me. So there's the t t t file. Okay. Alright. So it's in my downloads. Let's go to my target system. Let's import this template and check out some of the changes. So I guess I should have prefaced this. I I made some changes in the template that are not included on the target system, and you'll see that here because on my target system, I'm still on version six. So I versioned that template up to version nine on the source system, on the development server, and I'm I'm going in number six here. So let's import that template. And of course, I can, yeah. Well, we'll check that out later, the the the history of imports. But let's import this template. It says select template file. Great. I'll go do that. Go to my downloads, and there's my Orange County vitamin template. Let's open that up. Alright. Let's import it. And what's nice here is I don't really have to worry about, you know, overwriting anything at this point. Essentially, there's a preview step that's happening, which is so cool. So it says importing this template will merge the contents. Before import importing, ensure that the template preview settings version and content are correct. So let's go compare the template content. So I can come into this screen now, and this screen is now showing me what has changed. Okay? So here's all the entities that could be updated in my template. A hundred and thirty nine of them are not changing. Great. I feel good about that. Nothing was inserted. One, something was deleted. So let's go here. We can check out this bottom. It's got, a nested tree of the, entity. Come back down to the bottom. DB event category managers was deleted. If I click on that, it'll just show me that, yep, all this all this stuff was deleted out. So template's not gonna have anything in it. Let's go back. Let's look at what was updated. Let's take a look at this script. So this database script, let's see, some usings were taken out. So I okay. I'm okay with that. Oh, look. Some different logic, some if statements were added. Those look good to me. Right? And so this is what you would basically do, go through and see what's changed and if if you agree with all those changes. Alright? If we're good, then we're gonna import. So before I do that, let me show you what some of the things that I'm changing. And so if I go back to my site, let's go here, Orange County vitamin. Okay. Here's my area. So notice and I'll go back to let's import this. Before it's gonna make any changes, I have to recompile, so this will be this will be okay. Let's actually, you know what? Let's cancel it. I'll reimport I'll reimport to show you. So let's go to my batching area here. So you'll notice on my source area, I'm changing the icon to a filter icon. Right now, it's a cog icon. I'm changing some of the shading on this to basically look solid like this. Right now, it's it's got this little sidebar on it, so it looks a little different. Right? So some very minor changes, but, you'll you'll see them work. Okay. So let's go back to the template area. Let's do the import. Select my file again. Import that. We've already kind of verified everything. Let's run the import. K. Import has completed successfully. I'm just gonna bump open this tab right now. Okay. And then I'm gonna go, and I have to recompile. There's some code in there that just needs to be recompiled, so we'll do that. This just takes a few moments here. K. Code has been compiled. So I'll come back to my batching, and I'll refresh this page, and we should see the filter icon and some other things that have changed here. Texas takes a second to load this page after it compiles. Okay. And there you have it. My icon's changed and, you know, this, this cell, looks a little different. If I go back to my template, it looks exactly the same as the template now. Pretty neat. So, you know, simple changes, obviously, in this demo, but it's pretty cool how you can take all this work that you've done inside of TrakSYS and package it up, version it. You know, I didn't show you, but you can go back and look at old imports and see what was different so you can keep a history of that. But, yeah, so that is, you know, I'll wrap it up there. We've we've been talking long enough. But that's the template transfer tooling, that's part of the TrakSYS Solutions Studio. And any questions, reach out. Hope you enjoyed the video. Talk to you next time. Thanks.