What is TrakSYS Cloud?
TrakSYS Cloud is Parsec’s SaaS for overseeing and managing distributed TrakSYS environments; it provides centralized visibility and lifecycle tools while keeping plant execution unchanged.
The plant floor stays the same: production systems operate locally, machinery communicates within the facility network, and operators interact with TrakSYS as they always have. What TrakSYS Cloud changes is the management layer above execution. The cloud provides a secure, centralized way to monitor environments, manage access, and coordinate deployments across sites.
Rather than relocating execution to a cloud, TrakSYS Cloud introduces a structured control plane over existing deployments—ideal for smarter scaling, better governance, and furthering digital transformation.
Learn more and see TrakSYS cloud in action:
Okay. Welcome everybody to another TrakSYS video short solution series here. Today, we are talking about TrakSYS Cloud. So this is the latest offering from from Parsec and in the TrakSYS suite. TrakSYS Cloud will get into what it is and why it's valuable, and we'll take a look at it. So let's jump into it. So a couple slides to start, and then we will I'll show you the product. So TrakSYS Cloud. Alright. Bunch of topics on cloud today, but let's get into kinda what it is. So I'll read this because I think it's important. But TrakSYS Cloud is Parsec Automation's SaaS offering that provides centralized management, visibility, and services for TrakSYS MES environments. It acts as a secure cloud layer that simplifies how customers and partners deploy, manage, and support TrakSYS without changing how TraxSYS MES runs on the plant floor. So think of it as this kind of command layer over your TraxSYS installs. Alright? So from an architecture point of view, what does that really mean? So I'll try to orient you here, but you've got kinda the customer site down at the bottom here. So your site where you've got TrakSYS installed, maybe you've got production environments, nonproduction environments. Doesn't matter how many environments you have. You know, your machines, your users are talking to TrakSYS locally, that sort of thing. TrakSYS cloud sits in the cloud where you'll have a portal portal. You'll you'll log in. And what we do is we install an agent down in all of your environments that basically communicates back to TrakSYS Cloud. That helps with things like taking database backups, you know, viewing license configurations, any cloud libraries that we have, notifications, that sort of thing. We'll get into what that looks like, but this is the basic structure here. So TrakSYS Cloud should know about all the environments of TrakSYS that you have in your ecosystem. The structure inside of TrakSYS Cloud looks something like this, where we've got the organization level. That's typically the customer that's doing business with Parsec. And so then underneath that is the deployment. So you can think of it as a deployment. You'll see this all a bit, but you can think of a deployment as kind of the production instance of TrakSYS. So, you know, you're buying TrakSYS to install at a particular site. That site may have different environments of TrakSYS. It might have a production server, might have a QA server, might have a development server, but that's kind of considered one deployment. So you'll see that structure. Of course, there's user management here at the organization level. You're setting up users for access to the cloud. So if you've got implementers that need access to do database transfer and all that sort of thing or or just for visibility, you can add users there and invite users. And then, of course, you can then assign users to different deployments. So some users might have access to one deployment, but not others, there's some permissions around that. Then, of course, we have kinda licenses as the as the next layer down. These are really these really equate to the actual TrakSYS installs that you have. Right? If you've got a, like I said, a production server, a development server, a QA server, those are all gonna be represented here, and you'll see kinda what version the servers are running and and what license capabilities and features they'll have. We spoke a little bit about the agent level, so that's kinda the next level down. Agents can kinda be per license can you'd have multiple agents. Right? A lot of our customers separate different pieces of TrakSYS on different servers. Right? You might run you might run TrakSYS web with one server. You might run the logic service for TrakSYS on another server to kinda distribute load, that sort of thing. So an agent will be installed wherever TrakSYS services are running from, and you'd be able to see all those under licenses. And then, of course, the agents are really telling TrakSYS Cloud about the health of your system. Right? For now, it's talking we're talking about TrakSYS services. Are they running? Are they healthy? Are there any errors associated with those services? And we're able to track that. So that's the basic kinda hierarchy of data being being managed and being viewed in TrakSYS Cloud. Alright. So I'll walk through a couple screens here, and then I think we'll just jump into the to the demo. But right out of the box here, we've got secure authentication. So, you know, we're using industry standard SSO in the background. You know, you when you sign up for TrakSYS, you're essentially invited to this. You do not need to have a Microsoft account. It works with all sorts of different accounts of that nature. And so, anyway, there's a guided process for setting that up. Once you're in, you'd be able to invite different users to your TrakSYS cloud instance. Once you're inside, like I said, you're able to see kind of the the organizations. Here, I'm in the Parsec automation corporation organization, but you'd be able to switch between different organizations, view the deployments, view the users. Just some simple screens we'll walk through in a second, but managing users, managing which deployments those users are associated to, and then managing the permissions of those users. Underneath deployments, you know, we're seeing the licenses, the actual installs, where things are being installed, have there been any database exports or imports into those instances. And, of course, you then have user permissions at that level as well and notifications. And you hear here you see an example of kind of the notification settings. Hey. Look. Do I want some license expiration notifications? At this point, there'll be more notification settings to come. Agents. Right? So underneath the license, we're seeing agents. We're seeing the status of the agent, which version the agent is running, when it's last updated, what host is it running on. So you'd be able to keep track of where everything in your TrakSYS ecosystem is installed. Right? That's pretty important. And then one layer underneath that is looking at your service health. Right? Where's my logic service? Where is that installed? Oh, it stopped. I can go look at the operation history and see see some see some information related to how that service is is performing. And then last but not least, and and we'll kinda jump around in here, but this cloud is now an area where you can initiate database transfer. So this is useful if you're not familiar when you need to kind of clone an environment. So you've been, you know, working in your dev environment and you now need to push your changes to your QA environment or to production, you're able to specify, you know, am I exporting all my configuration? Am I just exporting UI changes? And then am I exporting all my sites in this instance or just a particular site's data? So you're able to export that and import that using this cloud interface. So with that, let's take a look at it. So here is I've got cloud opened up to the main page here. You see I'm the user logged in, Ryan McMartin. There's a little gear sign up here. Can log off. I can view the organizations that I'm associated with here, so Parsec automation and the Umbrella Corporation. So we'll stay in Parsec for now. I'm able to see users associated with this organization here. Again, we can remove users. We can invite users. We can see deployments. We can view permissions of those users. We can change the details of our organization a little bit. If we want to rename some things, we can do that. Let's jump into the deployment. So I'll go to Parsec QA here. So this would be like us think of this as kind of like a site and and that sort of thing. So and, yeah, and we could see all the licenses associated. We could see the users associated with with those deployments. We can manage permissions at this level and see notification settings at this level. Then we'll just jump down a couple more levels here. So let's go to licenses, active, jump into QA testing here. We'll see some agents. This one stopped at the moment, and no services running here. But you I think you get the idea that we can kinda jump through these different areas and kinda see see our whole ecosystem at this kind of command layer view. So more to come on TrakSYS Cloud. It's kinda just the start of this whole thing, but we're excited to have this offering in our arsenal now. And, yeah, looking forward to showing you more to come in the future. So thanks for watching today, and talk to you next time.
Why Centralized MES Governance Matters for Modern Manufacturers
As Manufacturing Execution System (MES) programs expand, operational complexity increases: new plants introduce production instances, development and QA environments multiply, and server roles evolve independently. To manage it all, governance requirements must expand. Without a unified management layer, visibility can fragment, version tracking gets difficult, and environment promotion relies on local coordination rather than structured oversight.
TrakSYS Cloud addresses these challenges by consolidating control across distributed environments. It provides a structured view of deployments, users, licenses, and service health, helping manufacturers maintain discipline as their MES program scales.
TrakSYS Cloud Architecture
TrakSYS Cloud introduces a secure portal and lightweight agents while leaving plant-floor execution as-is.
Each site continues running TrakSYS locally, including production, QA, and development instances. A secure cloud portal provides centralized access for administrators and authorized users. Lightweight agents installed within each TrakSYS environment communicate system status and enable services such as database transfers and health reporting.
And that’s it. No disruption to operations. No forced migration. No change to how your production systems execute. TrakSYS Cloud enhances oversight without altering how the MES performs at the process level.
How TrakSYS Cloud is Structured
To support enterprise-scale deployments, TrakSYS Cloud follows a clear hierarchy:
- Organization Level
This level represents the enterprise as a whole. It governs user accounts, role-based permissions, and global settings. This is where administrators control which TrakSYS instances are accessible to which users, and it is particularly useful when coordinating access for IT teams, system integrators, support personnel, and operations leaders.
- Deployment Level
A deployment represents a production instance of TrakSYS. Within a deployment, the cloud tracks associated development, QA, and production environments. This grouping provides clarity around which servers belong together and how they relate to one another. TrakSYS Cloud’s structured deployment views simplify lifecycle coordination and reduce ambiguity during updates and audits.
- License Level
This level encompasses all licenses associated with a deployment, each typically corresponding to one TrakSYS installation. This is where administrators can view version information, enabled capabilities, environment details, and associated agents. This visibility helps answer common governance questions: which version is running, where it is running, and which services are enabled.
- Agent Level & Service Health
Agents can be installed on any server running a TrakSYS service. They allow TrakSYS installations to communicate with the cloud about service health: which services are running or not, whether they're healthy, and whether they're encountering errors. Instead of manually checking individual servers, TrakSYS Cloud gives manufacturers a unified view of service health.
Simple, Disciplined Database Transfers
In mature MES programs, database transfers are common. Teams may need to export configurations, promote development changes, clone environments for testing, and more.
TrakSYS Cloud can centralize such transfer processes. Authorized users can initiate exports, define configuration scope, and promote changes into target environments. Transfers can include complete environments or specific configuration elements, such as workflows, state models, UI assets, or equipment definitions.
This unified transfer management reduces manual coordination and strengthens release discipline, especially in multi-environment strategies.
Centralized Ecosystem Visibility
As organizations scale, operational questions become harder to answer:
- Which TrakSYS version is active at each plant?
- Are logic services healthy?
- When was the last environment update?
- Who has administrative access?
With TrakSYS Cloud, these answers are consolidated into a single command view. Instead of piecing together data from individual servers and administrators, stakeholders gain structured insight across the entire MES ecosystem. This clarity supports audit readiness, lifecycle control, and long-term scalability.
Cloud for Scalability Without Compromise
TrakSYS cloud is more than a static feature—it’s a foundation for growth. Centralized monitoring, lifecycle management, and deployment coordination create opportunities for expanded capabilities over time.
As MES programs mature and scale across more sites, users, and integrations, structured governance becomes essential. A cloud layer can support that growth while preserving the operational resilience of local execution.
Conclusion
Manufacturers today face a complex balancing act. They need to maintain stable, reliable plant-floor systems while modernizing and scaling them globally.
This is where TrakSYS Cloud comes in. It provides the centralized oversight, lifecycle control, and governance modern MES programs need—without disrupting the environments that keep production running.
For manufacturers looking to scale smarter, govern better, and prepare for the next phase of digital transformation, TrakSYS Cloud offers a practical and future-ready path forward. To learn more about how a scalable MES strategy fits into your operations, contact us today.