Siemens Xcelerator, interoperability and scalable solutions - With Gerhard Kress

Trend Detection Podcast ·

Show notes

Welcome to the Trend Detection podcast, brought to you by Senseye Predictive Maintenance – the platform which enables predictive maintenance at scale across all of your assets, across all of your plants.For this session, we were joined by Gerhard Kress to discuss Siemens Xcelerator, interoperability and scalable solutions.

In this episode we discuss:

Siemens Xcelerator: Revolutionizing Business Efficiency: Explore how Siemens Xcelerator is transforming businesses with its innovative approach to interoperability and scalability in technology solutions.

Driving Collaboration and Growth: Discover how Siemens Xcelerator fosters collaboration among teams and facilitates scalable solutions to meet the evolving needs of businesses across industries.

Securing the Future of Digital Transformation: Learn how Siemens Xcelerator prioritizes data security while embracing emerging technologies, providing businesses with the tools they need to thrive in today's dynamic technological landscape.

You can find out more about Siemens Xcelerator below:

https://xcelerator.siemens.com/global/en.html

Please subscribe via your selected podcast provider to be notified about future episodes.

You can find out more about how Senseye Predictive Maintenance can reduce unplanned downtime and contribute towards improved sustainability within your manufacturing plants, by visiting: www.siemens.com/senseye-predictive-maintenance

Transcript

Welcome to the trend detection podcast powered by Siemens. Hello, um, and welcome to this episode of the trend detection podcast. Um, I'm really pleased to have, um, one of my colleagues on today, um, Gerhard Kress, um, who's very, very knowledgeable, as we'll find out today about, um, this really fantastic initiative from Siemens called the Siemens Accelerator, um, and it really fits in with, um, a lot of the stuff we're doing with Sensi Predictive maintenance as well. So I'm really excited to sort of learn more, um, for Gerard to share his, um, expertise with us, so. I guess before we start, I'll hand over to you, Gerhard just to introduce yourself to the audience, if that's OK. All right, thank you very much. So, um, glad to be here, um, on this podcast. My name is Gay Cress. I'm heading Siemens Accelerator, the portfolio and technical topics around that. So my team is making sure that Siemens Accelerator delivers to customers all the promises that we, we made to them and that they get outstanding offer, uh, outstanding offerings and solutions that really solve their, their problems. And I have a background for like at least 15 years in leveraging data to provide. Data enabled services and offerings across the industrial areas. Fantastic, yeah, and again, great to have you on board as well on the podcasts first appearance as well. Um, so I guess just for people who may not have heard of Siemens accelerator, maybe you could just start and just explain uh what it is and you know, what, what, what's it trying to achieve, etc. Yeah, so Siemens is actually maybe rather unknown, but very large software company, which the 2nd biggest uh software company in Europe. And we we were contemplating very much how, how can we bring Software for better to our customers and helping them in their digital transformation we've seen that all across the place so transformation being an issue and so we created see the accelerator as what we call the open digital business platform to help our customers in the industrial and infrastructural areas on the the transformation, um, and basically that is a couple of of topics in there we modernize our portfolio, provide uh an advanced augmented portfolio to our customers that's. Um, coming from Siemens, but also we actively invite partners and sellers, uh, into our environment to provide an even better and larger offerings to our customers. And we try to make it all accessible um in a different way through a central marketplace that's not only there to actually consume such applications, but also to learn about how others have solved business problems, to create a community of people who get the benefit of these digital solutions and hopefully and of course um make them enthusiastic to become uh customers of Simans Accelerator. And on that comment about open, so an open ecosystem, what's the, you know, how important is that? So it's not just, not just talking about Siemens products here at all, are we? We're, we're talking much more than that, absolutely. So I, I, I personally think that the time of closed platforms should have been. Uh, gone like at least 10 years ago, maybe not everybody heard that that part of the story, um, but I can only believe if we really, so if our mission is to help our customers in the digital transformation, this is not possible by one company alone, completely impossible. What we need to do is, is a variety of topics and openness has different facets in there. The very first thing is the different offerings in that, um, business platform need to be open themselves. Because every customer has in some enterprise IT environment, process driving software, uh, an existing brownfield environment. If you can't integrate into that structure, you're probably not helpful. So it's openness of the components. Second part is, of course, in order to provide the right. Solutions to business problems our customers are having, so to provide the right value to our customers to bring something that they need. This will in many cases mean that we need to provide. Expertise, capabilities, software from various ecosystem players. Because every question we're trying to answer is a very specific vertical or regional question. If you want to produce that answer, let's say, um, pharmaceuticals, the regulations to bring them quickly to market and in various parts of the world are different. You need to have a player that helps you to, for example, do that right, reporting to the authorities. So, there will be many partners involved and therefore we actively, really actively pursue partners and sellers to be on board. And internally, we even have targets of um that we want to have a very sizable portion of our offerings not coming from Siemens. And then of course openness means also that uh in the way how do we allow others to work with software from us and from partners. This means that we we provide functional modules in their functionalities as well as their data in such a way that people can deal with that. And this means, for example, not just. Having an API that that um opens up data stream but also providing the semantics or ontologies to that so that you know what the data actually means, because that will allow others, be it our customers, be it integrators, be it partners, To leverage that information in a much better way. That, that's so interesting that, yeah, like I said it's um there's actually targets placed on that as well. I mean that's really showing the customer sort of centric approach, um, approach of all this. Um, was there, I know, when, when, when that was discussed, was it, was it always the plan to include partners and external parties as well, or was it sort of evolved, just naturally evolved that way? Well, I mean, it's, it's not the first time we're thinking about these topics. And in my history, I've created myself an open platform before in the real space, that really brought in uh partially even competitors on the same platform. And uh our CEO Roland-Busch is very, very clear on that. He is a very clear believer of ecosystems and of Open platforms and bringing in partners on board. So, he gave us very clear guidance, but it's a, it's a mental change in the organization when you are very successful in in your current business. Providing hardware and software products to to to customers, um, suddenly opening up to a partner, giving up, giving away pieces of that cake because we know the cake is going to be bigger for all of us in the end. That is a cultural change and one of these things was that, um, our CEO. Almost forced our top 200 managers to go through an ecosystem training with Marsha van Alstein, uh, and we have another, I think 5000 or 6000 people that, uh, went through an online version of that internally for a training. So it was made very clear from the tone from the top, the future is in open business platforms. Only then you can start that internal change and I mean just just providing this platform to our customers one thing, but getting ready internally that we believe that that we approach it the right way and that we give these opportunities also to our partners and sellers, uh, it's it's a mental change, a culture change and that. Needed to be started from the top. So therefore these targets are important because if we don't take it serious. It's not going to happen. No, exactly, I like that ethos that it sort of benefits all, doesn't it, it benefits the customer, it benefits Siemens, it benefits the part, so the whole ecosystem, it's not about one. Over the other anymore, and, and we have to sort of work together on that, I guess another uh part of this as well, a big word that we use in the Sensai world as well is all about scalability and how, you know, not just deploying technologies but scaling that, you know, across plants and across the enterprise as well, how does sort of Siemens ccelerator, you know, enable that as well. So, I mean, Siemens comes from a product world, which in itself scales a lot because we you you sell the same component, the same piece of hardware, the same piece of software to to many people. So, we're looking really into the the case that we're seeing. In, in, in the accelerator, we try to provide a solution to, to a business problem because we're looking at business problems that many customers are having in a similar way. Um, we are not neither set up nor are we. Um, also pursuing one-off things that happen only once that, that, that's, there are other companies who can do it really much better and we're happily providing those bringing those fun in as partners, but we're looking at what are cases we're seeing with many customers that we need that where we have a capability to change that. So give an example, the whole question of um predictive maintenance on machinery, that's what Sensei has been doing um for a long time, making sure that. On systems in production lines, we can guarantee uh that we see things up up from before they fail, that we can actually in in the end increase up time. That's a question everybody's having. In the production side. Another thing that we could be we're focusing on, for example, is a topic where say the specific production processes, we have simulation tools and therefore, for let's say a spray dryer, we can actually um change the way it's it's engineered and automated, so we can do the same. Uh, output at better reliability and much lower energy consumption, but you provide a simulation together with the expertise and how you actually, um, automate and, and manage that system. So these are questions we see they are happening for many of our customers, um, or what I did myself in the rail space, can we make sure that, um, failures don't happen. Uh, out on the tracks that you can actually pre-plan them and change your complete maintenance process structure. Uh, because you, you basically take these maintenance activities when your train comes to the depot and you treat them like backlog items, uh, and therefore you can guarantee up time and availability, which means the customer needs less trains to do the same journeys. So these are things that we see all across the place, similar problems, and those ones we're focusing our R&D on. And, but of course, still, every customer needs some uniqueness in their solution because they have their own process, that they, they have a different philosophy, how they, they produce or operate or whatever. And for that we also actively search for partners that do these. Adaptation that needs to be done at the end, but we are not the best ones for that, um, and therefore we actively also dare engage partners. And what we see today is from our uh use cases we have on the marketplace. Uh, more than 25% have more than one partner involved already. Yeah, I said, yeah, is there, yeah, so I was thinking, is there, is the majority of the projects involving the accelerator, that was a good question actually, how many, you know, how many partners in Siemens products are generally involved? Is it, you know, is it 5? Is it 10? Is it, it's hard to say exactly if you're if, if I'm taking this as a, as a, as a Siemens product, uh, um. Team Center, yeah, Team Center is an application Sweden itself. So that's probably a whole PLM processing very different than NSA have, let's say the robotic library, uh, that we have on automation. So it's a bit difficult, but, um, we, we see usually between 2 and 6 or 7 components in there. That's sort of what I'm. Roughly seeing Um, and we're seeing very often content partners are providing extra application functionalities, um, or certain logic elements, and we're seeing a lot of integration and deployment partners because you must not forget, whenever you have a software and industrial space, all our customers have an existing landscape. It's not that they, they build a factory completely from scratch. They, they will have machinery that might be anything from brand new to 2025 years old. They have electrical systems that provide power to those machineries that might have been built, I don't know, a decade ago. They have a building environment with, let's say, air conditioning, temperature control that can be anything from brand new to old and any, any. Type of Vendor that provides equipment in those OT networks that integration needs to take place. Someone needs to do that and also for that we're actively engaging not only ourselves but also partners and we're providing for partners what I would call the recipes or or guidelines. OK, if you want to integrate this, that's the best way to do that because we want our partners to be successful. Exactly, and I guess you, I think you've touched upon it there, Ger Hub, but, um, how does this work in practice, because I guess if I think of the outside, if, if someone was considering 6 or 7 different partners and Siemens and others all working together, how does that actually work in practice and getting everyone singing off the same hymn sheet? Well, well, it's, it's a little bit like, like herding cats, of course, and the problem is, is the same way with partners as big as it's actually the pro the the the problem internally, yeah, and, and of course, I mean, the, the thing is, of course, also partners are competing with each other. Just let's say we have um um a specialized integration partner that focuses on food and beverage industry somewhere in Central Europe. Well, there might be more than one of those. And of course the question is, um, we will never choose just one. And the reality is the customer might have yet another partner they like to work with, and then the question is, can we onboard them quickly? So the way we're doing that is. Um, on one hand side, we make clear what the expectations are that we have towards partners, and we also make clear that there will never be only one partner for one topic. We cannot guarantee this. It's, it's impossible. Uh, the, the, the second thing is that we, um, and we say this upfront. I mean, partners will be also competing as we are competing with some of their offers or with other competitors in the market. That is the, the rule of the game. We, we are providing them. Uh, let's say a frame contractual thing that's not. Too much uh uh uh closing them in somewhere and we're providing them the information on, uh, tooling and open way on, on deployment scenarios. So a big part of that is now we, we just launched it, was it 5-6 months ago, or 5 months ago, the developer portal, developer Siemenscom, where all the information is accessible. We provide them even um spaces where they can test out APIs and things like this because if that information is open and available. Then we have. A, a, a good. Area where they can all do their best and nobody feels like that that they're somebody has preferred access to information, something like this. No, we don't. We we try to help them. Additionally, what we of course do in certain areas, um, we select some partners to create. Installations or or projects that can then be be marketed from our side as well to showcase how successful you can be in certain markets where we don't have yet that presence, we are actually trying to to make a partner especially successful so that we can actually have that that beacon out there uh and showcase to others that this is really something cool. Mm So we have, for example, uh um in talk about pharmaceutical industry, we're working with an an an APC EPC they're now also creating software environments. It's a company in Austria called uh ZETA, and they have now enabled um a a common customerloba biochemical production facility to to produce in a new way and a lot more efficient than before, leveraging software from us, but also from our competitors. And yes, this is something we even put in our Own success stories because we made the customer more successful by providing an open level playing field. And we, we, we needed this this partner at CETA because without their expertise in pharmaceutical companies, we could not have provided that element. And we learned from that collaboration, what do we need to change on our software side to make it actually easier so that in the end it's not just Loba out there being being successful, but we might, we want to have 100 customers that leverage such capabilities and can be successful. Yeah, and, you know, it just brings to mind to me, like, thinking about, you know, for, for a Sensai lens as well, because all these things we're saying about, you know, fitting in with it within existing structures. It's like products like Sensai, you know, it's almost designed to do that, right? We're not saying you need to rip out everything you've done and install lots of new things. It's actually Leveraging existing investments, but a lot, what I really like about accelerator, it's taken that step further. It's, you know, it's, it's actually collaborating, you know, is that what you're saying, I guess, collaborating with your competitors in certain situations to deliver the value. Absolutely. So for me, the, the only really important question is, can we provide customer value? If customers perceive value, then this is good. Collaborating with anybody and not creating customer value. Is never good if it's. A good friend or a competitor doesn't make any sense in that regard anyway. So if there is, I mean, in the end, customers are having. Or all our customers are competing on on their own grounds. They are usually great companies because otherwise they wouldn't be around anymore. Uh, all our customers are trying to solve their, their main problems, and the world got a lot more complex over the last couple of years, and we, we're seeing that, especially the production world. So everything we can do to help our customers being successful is a a good move for business for them. As well as for our partners and for us, so therefore, if we can provide jointly with a partner, business value to a customer, that is good. If that business value is replicable, so we can do this for many of our customers, that's even better. Absolutely, absolutely, and in terms of, um, cos what again what I really like is it's, um, you know, you're not restricting, you know, you, you're not having one preferred supplier for each, you know, for one for deployment, one for, you know, integration, etc. it's, it's much more open for that. But what's sort of the criteria for, uh, if there's a, you know, companies out there who want to be part of this ecosys. System, I can see why they would. Is it, you know, is there, you know, rules and I'm sure that I'm sure there's guidelines of, you know, who, you know, who would fit in better than others. But can you share some of that? Yeah, I mean, I mean, of course, so basically there, there, there's some, some rules and requirements around the the companies and about the the offerings they bring there. So, but in the end, it really boils down to, um, are you, uh or is is the partner company that we would be willing to do business with? So this means basic things around uh um legal compliances and and uh we of course want to protect ourselves from reputational damages we don't wanna have people where we are sure are not gonna deliver something to customs properly so I would say. Is our partner a trustworthy company to work with? That's, that's the, the first question, um, the, the, and of course one thing we do impose is do they take cybersecurity, um, as, as an important topic because the single biggest threat on digital transformation for our customers is cybersecurity. So if somebody says I have no cybersecurity policy. Uh, that we'll have a couple of discussions following afterwards because that is not a good starting ground. But I think that that should be sort of standard. On the offering, of course, then we say it needs to be integratable with the other offerings, so we move a lot of stuff to the cloud or to edge devices. …

Full transcript (WebVTT)