Teamcenter

We provisioned new application servers for the new Kubernetes cluster, right? which allowed us to have the new infrastructure stood up well in advance while the old infrastructure was still live in production.

But then we later performed in-place operating system upgrades for the ActiveMQ and reverse proxy servers because those are the servers that... broker the connections to the end users and to the external systems like SAP and Teamcenter.

And so with having the new set of application servers stood up and provisioned and Kubernetes installed, all the images already preloaded and such.

That made cutover procedure just as simple as stopping the I70 solumina deployment so that no one was working in I70.

So switching in between I-110 and I-70 is all controlled by the configuration of that reverse proxy server, what that URL rewrite was defined as.

So again, because we replaced the application servers, and kept the ActiveMQ and Apache Reverse Proxy servers as is.

That allowed for minimal changes to external interfaces like the Teamcenter and SAP interfaces because we did not change the IP address or host name of those servers.

And with the Reverse Proxy, The DNS that people were using to access, the URL that people were using to access the application did not change because DNS changes can take a while to propagate.

[laughs]

Ideally, there, there is a tool I really like using from Siemens called Teamcenter-

Mm

... which they're bundling into a larger product called Xcelerator now.

So they're always going to spend most of the time focused on supporting the MCAD tool.

So whatever enhancements go into Creo or into NX have to be reflected in Teamcenter and Windchill to be able to make that work properly.

There are also I mean, architecturally and philosophically, though, they're locked into a way of working that pretty much no longer exists.

And we can we'll probably talk about this more later.

The 3D design is happening in our NX tool, our NX CAD tool.

They're doing the data management in the Teamcenter PLM tool.

They are doing their manufacturing process planning in the Opcenter tool.

These are three different users.

So there's co-pilots, there is agents, and then there is things that are inherently built as AI capabilities in our tools that we also call them as in-app AI.

Things such as there were requirements that are standard requirements or regulatory requirements when a particular type of product like an EV battery is being built.

How do you validate that the design that you have performed is in compliance with this standard? Our Teamcenter requirements product, for example, has embedded AI in its process where all a user can simply do is go click a button and say, can you please verify this with my standards? And it will do that.

When we are working in our 3D design tool and a user is building geometry, we have a capability that predicts what is the next most likely command for geometry creation that this user will need to do to perform this.