null

AI, Digital Threads, and the Future of Product Innovation

July 10, 2026
Industry leaders explore how AI, data governance, and digital threads can help organizations improve decision-making, scale innovation, and manage complexity.

00:00 In this discussion we're going to dive deeper into some of the topics that we went through in today's presentations. We're going to look at the state of AI today. We want to see whether AI is delivering the value that it's been promising, and see how AI and digital threads work together. We also want to explore how Configuration Lifecycle Management plays into all of this. So I'd like to introduce our panelists for today. First of all, I'm joined by Dr. Wil Bielert,

00:32 CDO and Senior VP at Premier Tech. Peter à Porta, Product Owner, Configuration Management Systems at Vestas. Rüdiger Stern, Managing Director at Accenture Industry X and Rene Zoelfl, Senior Director, Global Industry MedTech at PTC. Thank you for joining me today, and I'm looking forward to hearing your perspectives. So, Wil, AI is everywhere, but what is the current state of AI in manufacturing, in configuration?

01:07 Where is it genuinely delivering value today? And what are the expectations that we can expect in in reality? So first, I have to say, it's really an evolution. So what we see right now are the first steps of a bigger transformation. So we see a lot of, so we, in particular see a lot of suppliers stepping into different ecosystems, especially stepping into Omniverse, creating digital twins of existing equipment, having first clients asking for it.

01:38 And we see already relatively small gains, like for example, we can now create code which we need to do by hand or programmers in a virtual environment. And then we can validate the code, that's a good example. But I think we all have to admit that it's an ongoing transformation. And then as I showed in my presentation, it will go step by step over the next years, really aligning a lot of different elements. So right now already a lot of different signs, especially in coding,

02:08 especially in taking control or pattern detection. And step by step everything will be an evolution about I would say 4 to 5 years. Sounds good. Peter, what about you in configuration? What your perspective is especially around configuration. How do you see AI playing there? Well, we’re not applying it yet, but of course we are looking into how we could apply it. And configuration, as I also alluded to in my presentation is very much about trust. So we don't want to jeopardize that.

02:39 So having Agentic AI in the core process of handling configuration, I think that lies very far ahead and because it it would be too risky to do. That said, there can be a lot of use cases of analyzing existing configuration data to identify patterns or these are or other things that would be relevant and it can not be found today. It would be relevant to apply AI on that, absolutely.

03:13 Do you have any perspective on when it will be ready? Also, any other panelists what would be a criteria for, okay, now it's actually ready. Through our discussion, we will probably touch upon the data foundation that has to fuel all of this. And so and I know from many years in the industry that data quality doesn't come overnight. Lack of quality can come overnight, but quality? And I think we've all heard that before.

03:44 Yeah. I will not make any promises then. Rüdiger, what's your perspective? So as Peter said, so data quality and trust, is, definitely a thing. What I see and I believe will give it a push is the talent shortage. So that may drive adoption quicker than we think. So pushback or resistance is less of a topic than the talent shortage

04:16 and make sure that it has been overcome. So it's interesting you say that in terms of the pushback. And isn't that just a normal human reaction to push back? And why would it be different now versus, anything else? It is a human aspect and it's not unusual. So as we said, with regards to overall Configuration Lifecycle Management, it is a people topic. So it's a change aspect.

04:46 It needs, proper education, communication. And the people need to be brought along. That's good. Rene, what's your perspective? I mean, just just to add to this, right. I think that broker shortage, skills shortage will be a driver for adopting AI, but also to your point earlier, I think we also need to be careful when we talk about AI because there are so many buzzwords and so many things. What is AI? You know is it machine learning? Is it Agentic AI? Is it Generative AI?

05:17 And we need to distinguish where each of those tools, which are in the end just tools. And we need to make sure that they can be applied. But this requires data, right? It also requires that the people are willing to adopt, and to your question about the impact, I think the important part is that this technology I think, has the potential to disrupt more people in the workforce than other technologies that we had in the past. Because it's also now affecting you mentioned

05:47 programmers, right? Programmers where people that always thought, hey, we are on the safe side because we are doing what is needed to drive transformation. Now we can create code much faster. So and this, you know, the effect on the people in the workforce is much bigger than it has with other technologies. And you might even have it on a society level and effect. Because resistance is is one thing, if you're just asked to do things differently or have a

06:18 an Agentic AI helping you, but if it's it turns out, well, you can leave because now you are substituted by AI, Or thousand AI's, as i promised. Yeah. Yeah, exactly. So yeah. You brought up two very interesting points and the question is will we stay in the future like we’ve been in the past? And you mentioned it in your presentation as well. So now imagine, and you made a very valid point, that AI is really hallucinating,

06:50 wouldn't it be our obligation to really create restrictions so it is probably governed like with CLM. So we can use Agentic AI to create a wonderful fancy Windchill, but at the end of the day, CLM would tell us, oh no, that's not possible. Or it's only possible if you extend the solution space. So I think it's more the collaboration between different systems, which we have to learn. And then we have also to imagine a lot of the topics we have like data. Data is the biggest AI problem since it is synthesization of data is a big, big story. And also there's now a lot of technology to make the data clean up.

07:23 So maybe we should also ask ourselves to have a different perspective and to find ways to overcome the bottlenecks, which are right now the bottlenecks for AI like having proper data, having to do the cleanup or the wonderful topic about processes. There are tools now, a lot of tools mapping the the processes, matching these processes, and then AI agents are helping to improve the processes. So I think we will see step by step we discover problems. And then also we use different sorts of artificial intelligence to solve them.

07:59 So Rüdiger in your experience where do initiatives like this stall? What are the problems or what are the causes of some of the friction that happens in these types of rollouts. I'm not sure if I want to answer the where, it's more the why. The observation I would like to share is, when it all started, there were budgets available and companies started POCs. Proof of concepts.

08:33 And there's a, my clients call it a POC-eritis. So everyone who had a few dollars left to start a POC with no business cases associated to that. And at the end, it was from a technology perspective, it might have been successful, but, the “so what” question was not answered. And that's why, many of these initiatives failed. Rene, do you see the same thing? Absolutely. And it is maybe it's also the kind of maturity

09:05 that we are seeing now that's coming. And I remember having discussions with clients that say, hey, can you help us and tell us what we can do with AI? And I said, what do you want to achieve? What is the business outcome they want? If they say, well, for now, it's my management that tells me I need to apply my processes. They also don't have a have a clue on what to do, but they, you know, they need to report to them to the street. They need to report to their stakeholders. Say we are on the forefront, we are doing something with AI, but everyone was questioning and we had to.

09:37 It came to my mind we had the similar situation. Everyone talked about IoT a couple of years ago. You know, we had this kind of purgatory, you know? Yeah, exactly like say the same, the same way everyone was now this pilot purgatory. And that was defined as something from the, I think from the World Economic Forum where they said, you know, to really get point, we need to have a business case. We need to understand what the real business impact of applying AI in a certain process would be for the organization. And that's really the critical point

10:07 where also some initiatives die today as people realize, well, just putting AI on the problem doesn't solve the problem. Maybe it's good that those things die if they're not viable technically, because it's exactly. It can never be the the goal itself to have AI. It serves a purpose, and if the purpose is not clear and aligned, that makes no sense to spend resources. It absolutely. On the other end, I think a conference like this one a really helpful tool to understand what's possible, what's not possible.

10:37 Because what I also see is we often repeat the same mistakes, but we often don't don't just read what what is successful and what's not successful. And very often in a in a domain which is evolving, we we try to apply the new technology to our current legacy, which is really difficult because we just don't know what is possible. And then if we try to run a POC repairing, like you said before, a legacy process, that doesn't make any sense, then we should really educate ourselves and really move on to maybe redesign a little bit more.

11:08 So that is finally working. But often is exactly as you said, we ask, oh, what what can we do with AI, I learned about ChatGPT. So why do we apply ChatGPT. And then it doesn't make any sense. But it's not to blame on the AI is to blame on on ourself because we have to educate ourselves. Yeah, yeah. But I feel like I feel like this has been said like a hundred times before, as you said, with IoT, with SaaS, probably with personal computers. And, and on the one hand, you say we never learn, but I would also postulate that you kind of need to explore your way

11:42 anyways, it's that same pattern of like, trying and failing and doing what you did before, and then somebody comes and thinks a little bit radically, and then you need to move on from there. But, you know, with two other people, I wrote exactly a book about this topic because we were really frustrated that the same mistakes are done over and over again, like we're here today. So if there's no change management, there will be no change is as simple as it. But if you if you buy a piece of software and you think it will change your organization on its own, it will fail. It's simple, but I don't know why.

12:12 For whatever reason, these mistakes are repeated since decades and it seems to be no evolution. And it's it's in most cases, not only a financial waste, it is wholly a waste of focus. So in the time where the organization is, is jumping on the latest and greatest, maybe not qualified, good enough so it will fail. They take time away from, from the stuff that would be really value adding that that's and that's a very valid point because the question for us

12:42 is, for example, shall we maybe create a business enablement team. So we have like people in the business really trying to keep the lights on. And if we have major disruptions like AI, it's maybe better to give it to teams who have more room to breathe. And we understand it and to try to just put it on the day to day operations makes sense. So let's switch gears a little bit. Peter. Yeah, lately we've seen a lot of, PLM experts and other commentators stressing the need for product memory. Oh, yeah. Data foundation for building end to end digital threads.

13:16 What's your take on that? That is very important, but not only for AI. At Vestas, we have a clear strategy on, on on making curated data sets available to the business. So, so data reside in many, many different business systems and often what you need is a combination of data points, maybe some extracted inter from that forming a data set on which the, the business can operate.

13:47 And we have a clear strategy on that. The data, they are owned by it by line of business. And if we should make the switch to AI, that would be a very, very nice starting point to start training AI because you don't get anywhere without quality data set that are governed and curated because they represent what, what good looks like. So, so I think that can go hand in hand. And I would dare to say that when you start up a, a,

14:20 an initiative on an AI, you should have that consideration at the same time. So maybe you want to build up a curated data set, not only but basically you can you can have benefit of it if the AI fails. Yes or no, but you still have benefit. But it would also be a prerequisite for for scaling up and and making that AI success. So that's that's really important I think. Sure, sure. So what kind of organizational changes needed to be in place to, you need to assign ownership of it.

14:50 So those are data points. They reside in the various business systems wherever these data points are owned. But the creation and sometimes the the work with the data set, you need these in these data points. If that's true then we need to set this data point like this. Yeah. This kind of work needs to to live somewhere. And someone needs to be accountable for it. And it it's very valid and it's a profession so, so very often in engineering driven companies

15:20 you have very good, knowledge in let's say civil engineering or electrical engineering, but data science is a different subject. So you have to have, you, you have if you have a very professional knowledge on the, the product, you need to have the same professional knowledge on the handling of data. Yes. Because what you say is exactly right. But but if you just don't have if you have a blind spot, nothing will happen. Yeah, sure. Yeah. How about you go. Do you have any, any thoughts on that in terms of things we've seen with respect to organizational change and, and friction in getting that that happening?

15:53 Because one thing is to say, it needs to be owned by somebody. But how do you figure out who that should be? Where that should be is especially if if some general ownership is decentralized, how are you going to do that? And what kind of process would you think would be a good way to approach this? I think the the ownership is twofold. One is the data itself. Yeah. So that's been generated by engineering operations by the product itself. Yeah. So they need ownership. And then the, the, the the AI roadmap or the AI governance

16:26 needs to be owned as well. So there needs to be an organization if not yet there that owns the AI roadmap and facilitates the AI adoption. All right. So I'm going to ask you guys a very quick gut reaction question. Right. Should I, governance be centralized or educate people enough and spread it out? What do you say? Well, spread it out. Yeah. What do you say? Where the.

16:56 You need the the rules of the game. You need to define centralized. Okay. Yeah. Otherwise you will face the next problem around the corner. So so you might want to engage everyone decentralized but but not on their own. That will lead to disaster. So you you prefer the center of excellence approach. Well not for defining them but but you know like just imagine if everyone makes up their own way of defining a business case. Yeah. And one of these business cases making it to the same decision makers

17:27 that would be quite frustrated that oh this team comes with a proposal. They describe it in one way or the others. And they have different metrics of evaluating if it's feasible or not. So. So what do you say. Yeah. Centralized centralized governance. Yeah. Yeah. But then spread out the enabled. Yeah. Yeah. Enablement the enabling the enabled capabilities and governance that. Yeah. So use the swarm intelligence in the teams to come up with ideas. But curated. Yeah. What do you say hybrid.

17:58 Hybrid. Right. Hybrid. Yeah. Having a hybrid approach, having central governance especially I mean working a lot of MedTech companies. Yeah. Especially in industries where you have regulated processes, you need to have that governance body that is looking into what is also the impact of applying AI in regulated processes. It's a different thing if you just to maybe apply AI on a kind of procurement process compared to a process that has an impact on the quality or on patient safety. So right. But you also need to empower the people that work in the process

18:28 to apply and apply AI and come up with ideas. Yeah. It must be a central governance. Yeah. Yeah, yeah. Because I think so I, I was going to say in my experience what, what could happen with centralized governance is, is stifling of innovation, because the, the governance body has determined that this is the right way to do it, and they tend to be a little bit less open for, for innovation. Or you need to have some very, very open minded people sitting there to be able to say my purview lies here

18:59 in terms of setting guardrails, but everything else is in there. So this is just my take on it. But, maybe, maybe it's in some cases it could actually be the opposite. Because if you imagine you could like scaling up AI really takes, takes space when you can start reusing things in the right. So now if you would build up a library of ad agents that you make available to the organization, so you basically centralized your governance,

19:29 it makes sure that they work, they're created. And now you say to your business, okay, guys, you have all these standard building blocks. Go ahead, combine them. Use that. Then you can you can have both. Yeah I think they are also topics that call for central governance. And I would just to mention a few I would say like stuff like security. Yeah. Yeah. Cost. Yeah. Because yeah this one, it's just that everyone right hook up with some vendor. And the third one I would say is sovereignty, because the

20:01 if we become more and more reliant on AI, the models, who owns those models. And if you can't take them and put them somewhere else, you don't own them. Yeah, yeah. And then you're locked in. And then the problem is around the corner, cost wise, politically, whoever, I mean, you're just you're living on the grace of others. Yeah, that puts you in a tight spot. Yeah. So. Yeah. So so my comment, I think. Yeah. Really good things. So my comment was more really on the first step because what we discovered was that AI is still a topic of big fears.

20:36 People have a lot of us and symmetric knowledge. And then the question is who likes pulls my knowledge because my knowledge is maybe the guarantee of me having a job. Yes. So and then the first step in and we've, we've done a kind of hybrid model. So we basically selected different models and said, okay, don't use the normal ChatGPT version to create an example. Here's a landing page. All the models on the page are safe with you. Don't run into, kind of a cost risk, so you just can try it out for your work and you see how they will help you.

21:08 And we were really astonished of the now, let's say, both one and off years, 30% of the team members have adopted to it. They're trying it for different things. They know it's safe. You know, now the culture really has changed. So no, no, we we perceive a much higher openness to go the next step and have a curiosity to try this out instead of the possible, we saw huge, huge fear. And no, I don't want to do it. I will replace my job. Now we are more like, okay, if we grow, we are more safe

21:39 and then I will support the growth. So finally it will secure my job. So that's a totally different perspective. Yeah, yeah I do agree with the three points Peter mentioned. I would like to add two. It depends a bit on the business model and the type of company you are, but it's IP protection, especially if you work and then it's ecosystem. Yeah. And the other one is commercialization. I mean there is there. So yeah, if you're used to let's say hours by times time, dollar then.

22:15 Yeah. So how do you deal with that? In a business context? So, these two topics I would add, right? Yeah. That need to be centrally governed. Yeah. Yeah, exactly. Exactly. Yeah. Right. Yeah, exactly. Sounds very good. Good. Implicitly with all of the regulation that is also coming, like, cyber resilience or the AI act, all the regulations in other read in other regions. Right. You need that. You need to have that, governance governing body. Yeah. In the organization. Sure. And of course, these are boring topics because, oh, they're holding me back.

22:45 Why can't we just. Yeah, but yeah, you need to have them. Yeah. Exactly. To succeed in the long run as well. Yeah. So rename how would, how do companies, balance the focus on near-term versus mid to long term? Opportunities when it comes to spending and how they sort of allocate their portfolio. Do you have any any thoughts on that? Well, you know, I mean we may have a little I have maybe a very specific, view on that because coming from a software vendor. Yeah. Right.

23:16 We are currently also investigating on what the typical and the good use cases are, and we are also doing it step by step as every organization is trying to apply. We also apply AI with the domain knowledge that we have and with based on the solutions that we are providing to our to our clients. Right. So and I think there will be there are already, use cases implemented leveraging AI that are more, more easier to implement. Yeah. But also generating value already. But then we are also thinking about use cases,

23:48 especially when you think about the complete architecture process or I.T architecture, use cases that span multiple systems. When we think about a genetic right, I mean, it's easy from a solutions provider to say, hey, let's apply some use cases on the solutions that you are providing. But what if you need to integrate with an ERP system or with a CRM system or with, Cpq system. Right. So there are different, different domains. And I think to start with and this I think that's also the maybe a bit of the

24:19 the advice is to start with the steps that you really can completely influence and then think. But thinking on the in the long run, on what this would mean when you think about the holistic picture is, yeah, do you see it as being any different than any other type of technology investment? It's kind of the same, right? It's start small, think big, because the usual is here. Again, for me, I think AI is a tool. It is a technology. Right. And we we need to see how we can implement that into, into our processes, into our organizations.

24:49 And I think it all goes back and we touched it a bit earlier. People process technology. That's does triangle needs to be somehow in balance and the need to think about all the three dimensions, even in that even with that technology and data and data and data. Yes. Yeah. That underpins that's the fuel. Yeah. Yes. It's very good. Do we need to change processes to work more effectively with this? With this strategy, would you go do you have any any comment?

25:20 Yes, I think so. Yes, definitely. So it's I mean, the processes these days are either driven by I.T systems or by common practices now. And if we want to if we want to adopt AI to its, to its value, then I think processes need to be rethought. And and another one to me is looking at processes as they exist today. Look at, look at it from an, an artifact perspective,

25:52 from a result perspective rather than a process perspective. Yeah. And look, an end to end integration rather than point solutions for AI. That's where I see the value. And so it's I mean enabling an engineers saving ten minutes a day. That's good. Yeah. But you know, if you think of, you know, engaging procurement and manufacturing and look at the entire value chain and take out time and frustration there, that's the real value of automation and I.

26:25 And do you guys disagree or I think, I think just, just that I mean the other way to look at it is that maybe it's one of the first biggest use case of AI because there is, there are a lot of startups helping companies to align their processes to, as you said in your presentation to the standard software, what we often see is an evolution. So a company exist for a hundred years, no one ever thought about a specific, process. It just works since decades. And all of a sudden we discover, oh, it's really legacy. What we do does not represent, let's say ERP, plain vanilla process.

26:59 So there's a lot of, AI solutions really discovering the gap between the supported process and the reality and helping them through agents to really adapt it. Because, I mean, I think it's obvious if you have legacy processes, but no one ever thought about it doesn't make any sense. So. But but this is normally the old times. A big project, a lot of resistance, a lot of whiteboards around the world. But now you can monitor processes in real time. So I think that that that's maybe good use case just okay. Makes sense.

27:33 So I think last one of our last questions, many initiatives, AI initiatives start strong but fail to scale. What does it really take to move from pilot to enterprise wide, wide impact? Anybody have any any thoughts on that or any experiences with that. So I think the the first thing that is really sticks so that it's a use case, which can get a dynamic on its own, where the AI can really provide the, the pathway. So if, let's say the typical frustration comes, okay, we have no this little pilot

28:08 now we need to find 20,000 men hours to clean the data to make it happen. And then just nothing will happen. So if you have something you should, you should be aware that there should be some angle that the AI can scale, and it can be with external data. Maybe you can. You need weather data or you do pattern recognition, or you need market potential. You buy the data for the whole globe and you can just use it for easy. But but if you block that, that humans need to do an a big amount of work

28:39 just to make it happen. My experience, it will always fail. So find something which has a dynamic on its own. That would be my advice, you know, from any other perspectives so that, it is kind of that start small, think big, approach. Right. But then maybe it's also that we don't have that. I mean, I started my career by implementing SAP systems, right? So and maybe it's also a complete different approach to, to this and maybe the also the life cycle of an agent, right.

29:09 Or an AI application is much, much shorter then like an ERP system, for instance. Maybe that's also something we need to consider when we think about, applying the AI. But again, it goes back to start small, but then also make a decision and monitor the performance of the agent and have maybe also a governing process in place that says, hey, if the performance of that agents is degrading, what can we do? Do we need to updated? Do we need to improve the performance? Or is there maybe another another solution that we should apply to that.

29:39 So there's maybe a much more agile way of thinking within the organization. On how we use the technology. Exactly. But think about this form of agents where the agents put these, you put each other on the pressure. Yeah. It's yeah. There's a lot of change now. Yeah, yeah, yeah. Exactly. Great. Yeah. Maybe a follow up question for you. I provides a lot of opportunities. A lot of ideas are going to come and go. What's going to decide the winners and losers in the next, 15 to 20 years?

30:12 Who is going to be the disruptors? Who's going to be disrupted? Doesn't need to be specific companies, but areas, industries. Where do you see the, the big winners and losers? I think the from a company perspective, I would say those those companies that really start now by experimenting. And giving also their employees empower their employees to do so to, to play around with that, you know, put away the anxiety that is there in the, in the, in the, in the, in the society

30:42 and giving them the playground to experiment and really start it, start now with applying AI in the processes and then continue and evolve. But having a governance framework in place and, and an orchestration in place that helps them to really steer the development of the AI into the right direction for the benefit of the organization. Okay, who are the big winners and losers? I'm not sure. I mean, to ten years, ten, 20 years is a long time.

31:13 Yeah, yeah. So it's the those who adopt quickly, but are nimble enough to rethink and readjust. And I think that is I mean, as you pointed out, right? It's overrated, for what happens in one year, but underrated what happened in ten years. So I think the nimble organizations will be the winner. Yeah. Sure. Yeah. How I yeah, I would say the, I think the organizations

31:43 that avoid wasting time on what I would call like random acts of AI, like because experimenting is good. But if you if you spend too much time on just playing around, not having a clear strategy or purpose of of what you're doing and why and how, I think you will, you will lose a lot of time. So, so the companies that that approach it diligently and find the right balance between a, a framework that makes sure that the direction and the approach is correct,

32:16 but still gives enough of freedom to and to let loose the. Yeah. So I think they, they will they will have a good chance. I bet you will. Well I think that's all perfectly correct. I would just add something. What I feel always very comfortable with is a kind of no regret, approach. So there's things we heard them today completely. Which are must you need to have good data. You need to you need to put different things in place in the organization to be ready for AI. If you just if you only experiment and you don't,

32:46 do data governance, for example, you lose in the it's that's obvious. There's no discussion. There's no doubt that regardless how the development will will be, you always need good data, and you need people who, let's say, as you said, experiments. And then also you need to have a way. And I think that's relatively new for an organization. You need to have top management, inputs to really say, okay, that's a good use case. That's good. So now let's let's really scale it up.

33:16 Yeah. Because experimentation is is good. You may have good people, you may have good data, but if no one at your management level is taking it and really scales it up with the discipline needed to do so, it's a fail. Yet anyway. So I think, and I totally agree, it's this kind of combination with putting things in place to be ready, discovering new things and as you said, not wasting too much time, being having a culture of saying, no problem. It's not your personal mistake. We failed. It's good.

33:46 So let's let's do the next one and then we'll say, okay, no, these are the two bets we take. Let's roll it out. Yeah. And and maybe I'd like to add also the, the management also needs to acknowledge that scaling up going from experimental stage to roll out in a company. It requires a lot of funding focus attention and and team leadership and leadership and it it costs, it costs really. Yeah. And and the business case. That better be good. Yeah.

34:17 Because it's it's not only the wins of the AI. It comes with a, with a huge cost and necessary cost because you. Well yeah. Yeah. Running business. So it's that's very true. And also except the office like it's very tough to get a, get an ROI on the first steps of, of a data governance. That's impossible. So there's no point discussing it. It just sleekness terms. Good. So let's wrap it up. Data quality will get sexy again. That's great. Yeah. So what should what was it ever not. Yeah.

34:49 Let's wrap it up with a quick fire round. So, in a short, short response, one capability, companies must build in the next 12 months. And one mistake to avoid, which is, say, capability is really, innovation. Experimentation with AI that's really important. And avoid is, is a kind of, hectic experimentation without without reflecting and without purpose. Yeah, sure. About you, Peter. Yeah, I would say that, one thing they should build up is the capability of, of

35:22 of of qualifying the right projects, funding them, but also being willing to kill them. Yeah, if they are not delivering business value. And so that would be a good capability to have the other one to avoid, I would say is to, to treat AI as a shortcut. So if your processes do not align or if your quality is poor, if your data, it's not a shortcut to, to solve these kind of things. It's very good. So yeah. Yeah. Ruediger, what do you say? So I think the, thinking about the so the capability to build is, connecting,

35:59 legacy systems and data sources. Yeah. So it does not necessarily require a, a new IT system, but how to connect, how to make data available. And the mistake to avoid is, to forget about the people. Yeah. Very good. Yes. Yeah. Exactly. I mean it's, it's success is empower your people. But also have your, your digital data, in order. Right. And I think, things to avoid is

36:32 don't treat it as the tool for everything. Right. You cannot use AI for some problems. You need to be very cautious and careful on where to apply. It's like, you know, you won't use a screwdriver to remove the nail from the wall. So that's you had a good example in your presentation where the the calculation was extended over to a calculator, because that's the right tool for doing it. Exactly. Yeah. And sometimes a, a RPA bot is better. Okay.

37:02 Yeah. Machine learning the thing is, is better to solve the that. Yeah. If the problem is. Yeah. Good. On that note, I will thank you for some very insightful comments. It was a pleasure to hear your perspectives. Thank you for participating. Thank you, thank you, thank you.

Understanding Configuration Management in Windchill

Scale AI From Pilot to Value

Talk to a PTC MedTech expert

Connect with PTC to see how you can improve performance across the product lifecycle. From compliance and quality to cost and innovation. Contact Us
Related Videos
Watch the video PTC Orbit for MedTech: AI-Powered Post-Market Intelligence Watch the video How to Balance Core Business with Disruptive Innovation Watch the video Regain Control of Your Supply Chain with PLM Watch the video AI in Defense: How Digital Engineering Powers the Next Era Watch the video AI in Electronics Manufacturing Driving the Future of Supply Chain Watch the video Data Comes First with Hitachi Energy Watch the video PLM, AI, and the Road to 2030 at Infineon Technologies