PegaWorld 2025: Siemens: Accelerating Transformation with AI, Blueprint, & Constellation

PegaWorld 2025: Siemens: Accelerating Transformation with AI Blueprint and Constellation

What if the climate cooled? Tensions thawed and the sky was a clear blue. What if power outages were a thing of the past and our businesses were future ready? What if our digital footprints were no more dangerous than our physical ones? And the only limits to a better world were the limits of our own imagination.

What if this weren't just a pipe dream, but a possibility, even a promise? Because while prosperity is an ambition, not a guarantee. Progress awaits and technology is the most powerful tool humanity has with technology. We can build a digital blueprint for a better world, where AI enabled smart grids accelerate the energy transition, and the products we buy exceed our increasing expectations.

Where electrified transportation is not only sustainable, but also efficient, consistent, resilient, where buildings Self-optimize healthcare is personalized and the next big idea is just one leap away. This is what's possible when data combines with advanced technologies to reveal industrial insights, and those insights enable us to decarbonize our communities.

It's the promise of software defined machines that adapt to ever changing conditions and give us ever better goods. Robots that pick and pack with human like precision and copilots who understand and advise so humans are free to do the work that only humans can do. It's the power of industrial AI, fundamentally transforming the way we commute, consume, create, play, work.

It is the impact of Siemens our ecosystem of partners, our customers together using the best of digital innovation to create a better real world today and for every day that follows. This is technology to transform the everyday for everyone. Welcome everybody to our session about accelerating transformation using Blueprint, Constellation and AI.

My name is Juergen Schoenenborn. I'm heading the center of expertise for Pega and Siemens, and with me on stage is Antariksh Gain, who is leading one of our major programs using the Pega Platform. A word about Siemens. Siemens is a leading technology company with roughly 310,000 employees globally. And as you heard in the video, we create technology to transform the everyday for everyone.

And we do that by combining the real and the digital world in four areas with cutting edge technologies like digital twins and industrial AI, we enable our industry customers to accelerate their transformation to sustainable digital enterprises. Our technology transforms Infrastructure across buildings, electrification grids to accelerate our customers digital journey.

To become more competitive, more resilient and more sustainable. In the area of mobility. We bring together rolling stock, rail infrastructure, rail services and software to provide sustainable, comfortable and cost effective rail traffic. Last but not least, in healthcare, we enable healthcare professionals to innovate personalized care, achieve operational excellence and transform the system of care.

This is accompanied by consulting, financing and shared services. With this, Siemens empowers customers to accelerate their digital and sustainability transformations, making factories more efficient. Cities more livable. Transportation more sustainable. And to take the greatest challenges in Healthcare. While Siemens might be known for its hardware portfolio, software got more and more important in the last years, and we are quite convinced that we achieved the best value for our customers whenever we combine hardware and software into solutions and services. What does Pega mean in Siemens? It started about 13 years back when the first demands were identified for a new technology.

We figured out that case management was a blank spot in our architecture. We didn't have any solution for that. And in very different areas of Siemens not coupled or linked at all. Um, first POCs and projects were started and two years later we decided that we need to found the center of expertise to leverage synergies, but also to drive consolidation of legacy platforms, legacy platforms for workflows and for business process management.

Since then, this small plant has grown quite a bit. So today we are running seven platforms on Pega Cloud and with platforms I mean it's a production environment, plus a QA meaning test environment, plus probably development environments. So we have seven of those stacks. We are we have implemented and maintained today more than 30 applications serving more than 100,000 users, which is one third of the company.

Um and um. we are processing more than 25 million cases a year. So roughly 2 million a month. That's quite a nice volume. And, um, our operating model today is what I would call a hub and spoke model. So I'm heading the Center of Excellence, which is in the middle. And then we have our spokes, which can be application teams like analytics team who are taking care for their applications.

The center of expertise is focusing on managing the platforms. So that application teams have the right basis to build on. We support in all questions around integration architecture. IT compliance is a big topic for sure. Whatever we do, it needs to be compliant. Um, Siemens is very clear here. There is no discussion when it comes to compliance.

The center of expertise is the enterprise layer. I think that's a very important asset for us. So the enterprise layer includes reusable assets. It includes corporate standards like single sign on, connections to the mail infrastructure, um, corporate identity, things like this. On top we offer expert services.

So when our when our projects, our project teams need support for special questions, performance tuning, um, user experience or whatever, they can reach out to us, they can engage us and we support them. And we have partners where we as the Co are holding the contracts and are managing this delivery delivery with our partners.

The partners can implement applications, the partners can maintain applications, but that's an optional offering. So if teams have their own resources internally, or they come with their own partners, they can still use all the other services from us. So nobody is forced to use our partner network. Today we want to share with you how we use Blueprint, Constellation and AI to enhance efficiency, drive innovation at scale and we will look at those topics from a hub point of view and from a social point of view, so that you understand all the aspects.

Antariksh Gain can you tell us a little bit about your program, please? Of course. Okay. So first of all, again, good morning everyone. So my name is Antariksh Gain and I am the lead system architect for the Don program, which is a program turned from project to program. So we also call this as Digital operations management because when we started it was just focusing on the order management part. Later on, we switched from order management to completely operations management. So like transformation, transformation is a long journey. And as like they started as a CEO long back. We started our journey on 2015. So the drivers for us why we want to have this solution because it was full of chaos.

The way users used to work, I mean, they were getting all emails related to orders and they have to go through with all the emails, and then they try to turn those emails into some structured information so that the orders can be booked. So what we did is that was the first thing the concept of digitization has been started.

Then the immediate next step was let's let's start this concept and then convert this concept into a business case development. So we turned that concept into a business case development. And then as a part of it, we did requirement gathering. And we also decided which technology we should go with. Thanks to them, because they were very well set up by the time we were struggling with the technology.

Like he mentioned, they also provide the consulting. We got some consulting from them and they suggested Pega as a good fit for the for the solution, what we're looking for. And we kind of decided, yes, now it's a time for us to transform the processes into a digital process. Very. Next thing was for us is to build the framework like they have the enterprise layer framework.

We would also wanted to create our framework on the Dom layer, which can be used later on for other solutions. And that was the vision we thought at the time of creation of this framework layer, which we call as Dom Enterprise Layer or Dom Framework layer. So we created the Don framework over here. And then the first thing was to create one application, but never to forget that this one application may turn into different application.

Because we may have to go with many countries. We may have to have the local flavors of the countries looking at all those things. We just created this foundation of Dom framework. The first thing was to go launch our first product, which happened on 2018. So we gone with the first product, we gone live and it was very well accepted and very well accepted by all the users.

They liked the transformation. And then the next thing was more challenging because more acceptance, you have more challenges you will be getting. And that was the next thing post 2018. We have just super fast. I mean, we just run through around with the whole speed because if you see in 2018 we had just one application, but now we are running with 20 plus applications and the applications are getting used by 35 countries.

So that was the start. And now that was that's the that's the present. What helped us to grow faster is the framework. Because the framework was built with so much of reusable concepts, reusable things which we can scale, adopt and quickly transform. I remember the first story when we had to go live with one of the applications, and we got just a couple of weeks to prepare to go live because it was for healthiness and, you know, the health industry, how fast we need to go.

So this was the ask that we have two weeks. And by in this two weeks you need to go to UAT and this all these things. Yes we we did even in that time we made in two weeks. These all transformation and changes. And in a month period we gone live with the Healthineers first application. And the rest was kind of I mean, so far it's a history, whatever we created.

So as I mentioned the numbers a little bit, I will just mention it again. So we are not very big team. We are just a small team of 40 people where I'm heading the technical team with 15. And then we have this 3.5 millions of cases, which is getting created every year. So it's overall volume, which I see.

So challenges kind of didn't end yet. So we were doing very good with our traditional things. We were very fast because of our framework. So then the Constellation things came comes into the life and then 20, 40, 2024 we have been kind of exploring and then Constellation comes into life. Android Gain Constellation.

Um, I mean, I remember when this whole discussion started, everything was new. Everybody was asking, how will that work? How will it work for us? How do I get there? Can you share with us how you managed to bring your team into this new topic of Constellation, how to use it, how to understand it, and how to get rid of your legacy mindset?

Yes of course. So good thing about starting with the Constellation is we got a new opportunity and it works very well with a new opportunity is what we understood, because converting the tradition one into Constellation, at least in 2024, was not so easy. So it was a good match that we want to learn and adapt Constellation at the same time, we got our customer as well who also want to kind of do something new.

So we started. So initial approach was to first of all going with the traditional way of course. So we had a quick workshop that we can do it faster in a week time. We just created an application again with a traditional one, but the wow moment was missing. Wow moment was that we wanted to learn the Constellation and wanted to adopt Constellation as a part of new solution, because it was the opportunity for us to go with a new thing.

And then that was a turning point and it helped. I would say the collaboration with customer, plus the technical team as well as the functional team. So we all collaborated and we all decided together. So this is the time, this is the moment we should go for Constellation because this is the best match going for the Constellation decision has been made.

We decided let's go with the Constellation very first challenge is now the skill of skill for the Constellation, because changing the mindset from traditional to Constellation, it was a big thing for us. I mean the change management. I will not talk about the customer or the other teams, even the technical teams.

They were not very much kind of they were not accepting. They were not welcoming that we going with Constellation not tradition because of the challenges, because acceptance was not there in the team, within the team itself. Now the idea comes into the mind with a fresh technology. Let's come with the fresh minds.

So what I did is I had one person with a fresh mindset because he doesn't know anything about Pega tradition. He was fresh. We just gave him Constellation that this is the this is the place you need to play around with. And then that was that was a good trick because it worked well, because he doesn't know anything about what's going on with tradition.

And we were not very sure what's going on with the Constellation. So then it was a it was a mix, a mix of experience, traditional ones, plus Constellation and the fresh mind. It worked very well because he doesn't have any legacy, understanding and all these things we increased the number of people with two more with the same mindset. And then we had our team built. We had a very good kind of, uh, collaboration done with Pega as well, because they were supporting all the time, because the Pega consulting, they were supporting us with any kind of challenges, whatever we have related to technology they were supporting, they were just next to us.

So we can go and ask the questions, and they were giving us the solution about how we can go along with this. So that worked very well, the partnership along with them. So by this way, we overcome this all challenge what we thought it's going to be more and we went live with our first Constellation application last year.

So key success factors for here was the dedicated skill development which we tried in a different way. We developed the skill in a way that we trained a Fresh minds then strong partnership with Pega, because that helped a lot. Comprehensive learning strategy, because at the same time, new people or new fresh minds were learning Constellation we were training our existing ones also because it has to be the match, because it cannot be only Constellation or only tradition.

It has to be the mix which what we understood. So that's what the whole kind of Constellation journey we had. And that was the first one. And now I would be happy to mention that we again going with the new application, and that is again on the Constellation. And now we have a skill set mindset and we have good amount of experience as well.

How to go with. Okay cool. So the first team started to work with Constellation and we the Co, we asked ourselves what do we need. What do we need to do to better support them? And we recognized we missed something very important. We did not make our enterprise layer Constellation ready. So they had to build the application without our beloved enterprise components.

So the first task for us was to go through our enterprise layer, identify those components which have UI included, and see how we can bring them to Constellation. And we hit the limits of what you can and should do in Constellation. So we had to go into this topic of the components. That's the way how you can extend Constellation.

And we identified those four things that you can see on the screen. The first one is a rather easy one. It's our lookup component for the corporate directory. This is a little bit of a tricky one for sure. You can do most of it in Constellation out of the box, but what we needed to have on top is before this component fires any API calls to find people, we had to ensure that the user already entered a certain number of characters, and we had to implement a kind of a delay.

So you don't want to fire API calls every millisecond, right? So this was not possible in Constellation out of the box. That's why we had to create a DH component. The second one on the upper right side is the announcements component. On our main platform we are running more than 20 applications. And again and again there are situations where some information needs to be brought to the users as far as soon as possible, a new maintenance downtime or something like this.

That's why we have this announcements component. And you can see there is this this little icon with the counter. So this is added to the navigation. And whenever new messages are maintained the counter will increase. So people immediately recognize there is something. And then they can look at those messages.

Um. The tricky thing here was um, we had to add a new entry to the navigation, um, which you typically also do via the component, um, at least if it's going to be a little bit interactive with this counter. The things on the bottom of the slide. Terms of use. Um, that's one of our IT compliance topics.

Um, before a user is logging into an application for the very first time, we need to make sure that he accepts the terms of use. And, uh, the tricky thing here was not this kind of pop up. That's easy, but how do we achieve that? We have this kind of pop up or overlay, and the user has really no possibility to get around it.

So there are two buttons. That's all he can do. And he must not be allowed to do anything else. This again um, was implemented via a DD component. And the last topic is the settings dialog. Um people need to maintain certain attributes of their operator accounts like the time zone, the preferred language, the substitutes when they are on leave, and also here we had to implement a dx component because we directly we needed to update operator properties, which is not possible in Constellation out of the box.

It was very interesting for us to do that to see what does it really mean to build the X components? Which skills do you need? How does it work? And from this we derived certain standards how we want to deal with the X components on the way forward. The X components means you are writing code and the code is not in the Pega Platform.

So you need a code repository. So we defined what is our central code repository for components a component needs documentation. What does this component do? How does it work? How can it be customized. Probably how to embed it into an application. So we define certain standards, how to do this documentation and where to make the documentation available.

The next question was who should be allowed to create and publish components. And as this topic is quite new still we try to keep it very tight. So, um, our recommendation as of now is that only we as the CCO are publishing new components. Even better, only we develop components. We need to see how this works.

Um, I'm still waiting for the call from Antariksh saying, hey, Jürgen, this doesn't work. I need to do it on my own. Let's see. Um. The very interesting thing for us also was, um, what is our recommendation to teams like Antariksh team about using the X components, and I think we are very much in line with the recommendations that also Pega gives.

And the most important one is don't do it very easy. Try to avoid it. Consider the x components as the last line of defense. And one way to avoid the X components is your mindset. Don't expect a 1 to 1 replacement of what you were able to do in traditional UI. So don't think about the how should it look like?

Just focus on what do I want to achieve. And then the likelihood is really high that you find a solution in Constellation out of the box without implementing the X components. And in case you run into a situation that you think you really need a component, keep it simple, simple, and stupid. A component should exactly do one thing.

It should not be too complex, otherwise your implementation and maintenance efforts will drastically go up. What does it now mean for the way forward with Constellation? We give a clear recommendations to the application teams. Whenever you build something new, do it with Constellation. If you build a new application like Antariksh Gain and we'll also do tomorrow or the day after, do it in Constellation. If you're implementing a new case, type within an existing application. Even then, you can think about using Constellation. It might be a little bit tricky for us, because most of our applications are on an old UIKit versions, and if you then combine UIKit and Constellation, the user experience might be not the best.

If you are on cosmos already, then the combination works rather good. And you probably heard saying that he is running 25 applications now. We rather call it an application group. Most of them are based on one framework. So it's specializations. And in Pega we call that layers. And we were asking ourselves how do I deal with applications that have lots of layers.

Do I need to migrate them all at once? That's going to be a nightmare. Or can I do it different? And we figured out it is actually possible to migrate single layers, or to build a new layer on your framework using Constellation. This was very interesting for us to see. So this is how typically applications look like.

You have the enterprise layer. On top of that you have a framework layer with all your application standard functionality. And then you put an implementation or specialization layer on top. And if now, if you now are in that situation that you want to do a partial migration to Constellation, we figured out that it can work like this.

You add an additional framework layer which holds the Constellation specifics. And as you now have the old framework layer and the new Constellation framework layer in your application stack, your implementation layers can either use the old or the new UI. This was a good eye opener for us. So it is possible to do step by step migrations in multiple ways, and it even allows us to keep a very high level of inheritance, which is important because I mean, copy and paste is something everybody can do, but you don't want to maintain that, right?

So keeping the inheritance was very important for us. Nevertheless we have those 20 plus applications running on old UI, and we are still exploring additional possibilities how to deal with them in the future. The effort of migrating an application to Constellation is high. Yes, there are tools. They support you, but they don't do your job.

You need to understand those tools like the migration assistant. Um, but yeah, somehow we are still hoping on some additional ideas and probably tools that support us on the way forward. Let's go to Blueprint and Ryan White. Why not? I will just start Blueprint. Before that, I would like to mention what Jurgen said already about the Layer Cake thing.

So like they're doing in enterprise layer already, the Layer Cake thing to enable the Constellation for the applications who are using enterprise. We are also doing at our level where we created a Constellation framework so that we just shift the reusable things which we can do from the Constellation framework, and then tradition becomes also easier.

So that is also something we are also doing at the at our level, so that what support they're giving us, we can make best out of it. Now coming to the Blueprint topic, I think we heard a lot about the Blueprint today as well as with so many possibilities. But when we started, or rather when we started last year, we started to use Blueprint from the previous year itself.

And the first thing was just to do the hands on so that we can present, and then we be comfortable and then we can go for that. Now it gives a very good customer experience is what we witnessed. And nowadays what we do is when we go for elaboration, we do elaboration. At the same time, we start capturing something which we can do in Blueprint because we are not in the state so far where we completely engage customers and they are also doing Blueprint with us.

But yes, we started to use from our end where we can just have something created. And the recent experience, as I mentioned, the Constellation one. So what we did is we had a smart customer. They already had everything workflows and all designed in some tool. So we used that particular workflows. We converted that workflows and the content, whatever they have in a in a normalized way into a document via using some AI.

And then we had a content which we can go with Blueprint upload it and then we will have something. And yes, we did. We uploaded the document and we came out with a couple of processes. So they were very close to what we were discussing with them. And this all things they were not knowing that we just using the inputs they captured somewhere.

And we're going to use this particular input in this way out of this. This was a wow moment for the customers because they never expected this is something going to come out of this elaboration, because what we did is we created via Blueprint a whole process and all. And then we demonstrated we we just demonstrated that this is what the process you, I think looking for may not be 100%, but very close to what you're looking for.

Then the same thing we just executed. And then just try to show them some of the features and all. And it was again very well accepted. And they were very happy to see that. What we can do via Blueprint. Now, the next thing is they even asking that can we also contribute? And that was the change we were looking for, because what we understood is the new things, whatever we're doing with the Pega, we, along with the tool we supposed to get matured together, tool will get mature, same as us.

We also need to get mature with the tools, whatever we're doing. So that was the Blueprint journey and now it is kind of a practice. It is. We also set up a process. So I'm part of it where I set up a process that yes, you have to go with the, the Blueprint and engage customer and then that's the outcome you have to do.

So that's what I just communicate to all my team members that yes, that's what the future is and we have to go with it. Yeah, actually we love Blueprint in Siemens. Um, and uh, it didn't take us much effort to, on the one hand side, understand what Blueprint can do for us, but also to enable our teams to use it.

It started very easy. We had to do some security and data privacy clearance. Um, as always, I mentioned it compliance earlier. Um, but it was not not a tricky thing for Blueprint. Um, as I mean, process designs that we are discussing with Blueprint typically do not include any intellectual property or something like this, so it was easy.

Um, the next step was to provide just an environment where people can play around. So where they can import a Blueprint and see how does it really feel if I want to implement an application based on a Blueprint. And um. The Co is also very much engaged in, let's say, knowledge management informing all our stakeholders.

So we for example, did a lunch and learn session about Blueprint to spread the word, to make all the people in Siemens aware of what Blueprint is. How does it work? And um. The next step then was okay, now I understand how Blueprint works. Now I have probably played a little bit around on the sandbox, but now I want to implement a real application. And this real application should also have a Siemens corporate identity and smell. So Also, we provided a small guide how to turn a Blueprint based application into a Siemens application, how to integrate enterprise components, things like this. In the meanwhile, we have seen Blueprint in a number of workshops and activities.

I think Siemens employees have in the meanwhile created more than 100 blueprints. As far as I know, and especially for teams like Anterix team, it's a really, really an accelerator and sometimes an eye opener. It enables not only speed, it enables collaboration. It enables a lot. This morning we also heard about legacy transformation, right.

That's something we will also explore in Siemens as one of our next steps. We still have one, two, three, maybe more legacy applications somewhere in the Siemens universe. And we now want to figure out how can Blueprint really help us to modernize those or to bring those applications onto a modern technology stack?

The third big hype topic Antariksh Gain I know that you also were engaged in an in AI. So which kind of use cases did you implement? Okay. So I will add that what we're using for AI so far. So as I mentioned, if you remember the starting point of this whole story about the journey. So the emails, emails were the problems there and now as well.

So now the customers are asking for the next things. So now you have a process. Now let's read those emails and do the classification automatically. So that was the first thing we started with. So now when we receive an email we classify them. Which kind of case type supposed to be created out of this email.

And then we just create that kind of a case type. So at least one part of the classification which is manually done is automated. Likewise the next was the data extraction. That is like we're getting information over the email like the order information or some information related to the orders. The next task was let's extract this information so that we just automate and go to the next level where they didn't even need to put all the data.

Yes, they will be the verification, but at least the extraction will be done in a quick time. Summarization is very important for the emails because imagine there are a lot of back and forth emails were going on, and then at point of time, the actual order managers who are working, they just lost the summary of the whole discussion.

So that was the next thing we started with and we're doing. So what we do is we just summarize the whole emails and then present something to them, which they can make out of it quickly, that what exactly they need to do. So that was the summarization we do. Translation was very important for us because as I mentioned, we are having presence on 35 countries, which needs multiple language supports.

So what we started with is a simple translation of email. Sometimes, sometimes the whole content, what we what we need to use, we translate in the local languages and all. So that was again done. I'm not talking about the translation or the Pega translation of the local languages where we see the the dashboards, rather the content, what they provide, and the last but not the least, the tender management, because that was the first application we want we gone live with.

Now what they're looking for is they will receive a document of tender, and then they would like to have certain questions predefined ask to the documents, which is going to be accelerator for the bid managers to start with. So they will be predefined questions which again going to be a standard classified classified questions.

And we can change the questions and improve as well. So the document comes, we do the processing part. And those 20 questions what we're talking about which are very relevant for their processes. They will have the answers about those that okay these documents having these kind of answers for your questions.

So that's again an accelerator. And the next part is for this is to chat with the document. So they are going to chat with the document. They're going to talk with the document. And the documents are something they are not in Pega. They are in some SharePoint. We're getting the connection over there.

And the AI is going to read all those documents from the SharePoint, and then they will just chat with the document that okay, where is the respective documents, what we have. So this is what we have been doing and yes we implementing and we'll go along. As of now those AI use cases I have to admit they are not using Pega.

I, um, there are a number of preconditions that need to be fulfilled and we as a Co are working on them. So, um, the ones here who are familiar with Pega, GenAI and the Pega Cloud setup, they might know those topics. Um, we have finalized the externalization of services like SRS. We have done the update to 24.2.

And in the next weeks, we will focus on the migration to cloud three architecture. Then we are technically Pega GenAI ready. And I'm really looking forward to that. Um, we still need to do compliance for sure. I'm not mentioning it anymore. Um, but I think at the end of the day, one of the most interesting questions with AI and Chennai is when to use what.

There are so many tools and technologies on the market. Um, so and they all have their strengths and weaknesses and their specific scopes. So that's very important for us to develop a good understanding of when to use what. And here we are going to make use of our hub and spoke model. We as the Co are this kind of information hub.

Here. We are talking a lot to our spokes. What have you implemented? Which tools did you use. And we are distributing that information to to other stakeholders that nobody needs to reinvent the wheel. When I was preparing for today, I was thinking a little bit about our Pega journey and I know how it all started for me.

I was working for ten years in different roles in SAP projects waterfall driven client server, SAP Guy, Abap, interesting but not sexy. And then I was allowed to manage one of the very first Pega projects in Siemens, and this was a completely new world for me. I felt like the cool kid on the block. Modern technology, modern methodology, agile web Cloud all this stuff, right?

Um, a lot of things have happened since then. So technology is evolving. There's. So many cool things available these days. So low. Code is everywhere. Agile is everywhere. Cloud is everywhere. Um, nevertheless, I still believe that Pega offers a very, very strong package with its combination of technology, methodology, and tools.

So I think when when you work on Pega, you can still feel like the cool kid on the block. And the really good thing is it's not experimental or something like this. It's mature. It's enterprise. Ready. Right. So I am looking forward to explore what's next. We already heard a little bit about Atlantic today.

So a topic I'm really interested in and I'm already curious to see what will we discuss here in 1 or 2 years from now? It's going to be an interesting journey. That's what we have prepared for today. Thanks, everybody. We have a couple of minutes left for questions. Thank you. So whoever has a question, please make use of those microphones here and on the right and left side in the lane that everybody can hear you.

Feel free to just go to the microphone. To say that. GenAI is it okay for you to say or may I ask then what would So. Okay. So I'll take this question. So models we are not very much exposed with the models because again we are using services internal services from other departments. So they kind of providing those services to us and we just connecting with them.

But mostly those are uh I think the latest model, whatever we have they're using that. Do you have any idea about. I don't know which of the services you're using. Okay. We have too many. Yeah. No no no no no not in-house model build. They again connecting with the available models but again within the limit of Siemens because Siemens itself has their own layer.

Because if we need to connect, then we have to go to the Siemens layer. And then they will decide which model they allow us to use. So we are just using in between providers. Okay. A question about the situation Layer Cake that you mentioned. Right. So when you just. A second, can you turn up the volume or can you go closer to the microphone.

Closer. Okay. Okay. Is it okay now. Yeah. Yeah. So while you are building the Constellation application, so you built one, uh, framework layer for Constellation, right? So what about the data model? So in Constellation, data model drives the UI, right? So what you require to rebuild the data model or how did you manage that part.

Uh. We are we are building on the existing data model. But when you go to Constellation you might need to change some of the properties. You need to change the data types probably. Right. And this change of data type this is happening in the Constellation framework layer and also the mapping to the old property.

Um, the cool thing is that all your old reports and so on, they still work. They still see the data. Um, so, um, this additional layer that you squeeze in between does all the translation for you? No, but the challenge we see is that let's say if you create a text property in old traditional way so we can use it for the drop down.

Right. But it's not the case with Constellation. So we have to recreate almost every property. Right. So what is it depends. It depends. Um, so in our experience it was not almost every property. It was a number of. And what actually happens is that you kind of duplicate those properties. So you keep the old one, you create a new one.

The new one is Constellation ready with the Constellation ready data type. The old one keeps the old data type and you map them. Okay. And what exactly the Constellation framework layer host I mean, what is that layer exactly contains in your case? So the layer is just within the application stack, right.

And in this layer you, for example, define those new properties with the new data types. You define the mapping to the old ones. And so whatever you need to do to make your application in working in Constellation is happening in that layer. Okay. Perfect. One last question. So, uh, what do you did you create a new case type or did you migrate existing case type to Constellation?

Um. Um, we migrated an existing one. So how did you feel the I mean, how complex? Yeah. How complex was that with or without action set building the same functionality? Uh, without action. We are running out of time. Can we take it offline? So I'm inviting everybody who still has questions. We will be around, but I think we need to leave the room for the next session.

But just come to us and we can discuss your questions, okay? Okay. Thank you. Thanks again.