Okay, can you see the screen? Yeah. Perfect. So I wanna give you some insights about our global initiative in automotive. So how we fostering trust in supply chains and global supply chains, and also in value chains with decentralized identity on server awareness identity. I'm Matthias working as product lead at Finity X,
Working as a society advisory at Accenture, supporting finity X and the advisory role for decentralized identities
A couple of years, a perfect stone for suppliers and also OEMs happening these resiliency issues around the world.
Then also su sustainability regulations like supply chain, due diligence act, but also geopolitical and innovations and the need for innovations. So, and the cost raising quite, quite a lot in this area. So we decided to come together with 28 companies building the Katina X network. So companies like Bosch, Microsoft, B-M-W-S-A-P Telecom comes together and creating a network.
Now the three years are over from Katina X comes to the end and now we, we go from, from a consortia, a closed consortia to a open source ecosystem and we have now more than 200 companies working together worldwide with JA Japan, Japan with Nissan Fujitsu, with, with Sweden, with Volvo, with Magna in in us. So that's really a global initiative, but it's not the end. So what we are doing now, Katina X come to the end as a funding project, but now manufacturing X stepping in.
So the, the first one is factory X. So all the things, all the learnings of the last three years come together and we started transfer X to bring our learning into the other projects. Now that's process X, robot X, semiconductor X, aerospace X and energy data X. And also we will have international manufacturing explan. So as you can see we have a common play base, a regulatory framework, then a technical base layer and a shared services. And we are live, we are live since October, 2023. So everything is based on open source. We are the largest eclipse structures X project.
So of the few 450 projects of Eclipse Foundation. So we created an operating environment. Finity X is the operating company. So we operate that on on the international side, but we also plan other operational companies in other regions. For example in Japan and US and Switzerland and others.
So we created now hubs and looking for other operation companies.
Okay, what we are doing, we are very concrete use cases as you can see, for example, certification management. So for example, automotive companies have have the hassle that they have certifications like TT or ISO 2 7 0 0 1 and if they have a supply chain and one part is not sufficient or not certified, the whole car is not certified anymore. So this is very important to take a look when the certification will be expired. And as you can see there are other use cases like circularity, this recycling. Another thing is data chain kits.
This digital twins product carbon footprint is PCF, the calculation in scope three. So we have a re regulations how to measure the emissions through the whole supply chain. Demand and capacity is very important. The battery pass, maybe someone who heard about battery pass or product passes, okay, that's a very important thing as well.
So it's mandatory in one or two years. So we have already the semantic models, the API specifications for the automotive sector and we will extend that as well in the manufacturing as well.
Okay, here it's very complicated but I tried to explain a little bit On the top you see the Katina X association. So this, this is like creating the architecture RA guardrails, the standards and they have also the conformity assessment framework. So we work in expert groups and committees, so all the the members.
So this, and as you can see on the left side, this is a open source development environment in the ECL structure X project, we are now more than 300 developers developing as well the core services as well. The decentralized services like wallets, connectors, digital twin registries. And we as Cox, we are the first operating company to operate this open source in, in the cloud as a sales service.
So you, everyone can use this open source can start to be operating company, but you have to certify by CarX. So as you can see on the right side, we have also some dependencies to other standardization bodies. For example, Gaia xx, who heard about Gaia XX from here, some of you, great. Then another thing is the trust and identity framework. Another thing is that the IDSA International Data Space Association. So who heard about IDSA? Not so many.
Okay, so they are the people they started with data spaces and the Eclipse foundation. So we started some projects and working groups. So we started at first with the eclipse data space connector that becomes a data eclipse data space components. Who heard about this project?
Ah one, okay. And then we start with Eccles structures X. Then we started a data space working group. We creating a data space protocol together with IDSA and now we created an initiative in eclipse the data space, decentralized claims protocol that will focus on B2B, all the semantic layers.
We speak with IDTA for digital twins and who heard about asset administration? Shell not too many. Okay? So that defines for the industry, the semantic models. We also work with world Business console and about a PCF rule book.
So as you can see we have many dependencies to other institutions, but we are not done yet. So what you can see now, we we it's like evolution from from the left to a funnel, centralized components to federated distributed components and now more and more services over the time becomes decentralized. But that brings also some challenges.
So you, you get ign resilience in the network and a kind of scalability but it getting, you will lose simplicity, you lose also some control with decentralization and it's also very hard to discover for example the DITs in the network. So we also have to think about how we do that.
I spoke a little bit about the new project, what we have now in the Eclipse Foundation called data space decentralized claims protocol. The problem what we hear or I would say the challenge we hear the last days, all the the, the wallet initiatives.
They're very much human wallets but we need, we need machine to machine communication and wallets for B2B. And that mean means we also have some protocol flows we want to follow. So we created like an interoperability overlay for the upcoming protocols there will come. So we are not there yet. We have for example base identity protocol. That's a format for self issuing identity tokens. Then another one, another protocol is verifiable presentation protocol that pre presents the VPs and also the credential issuing protocol that store the the VCs.
So we want to support multi trusts anchors because we know in different regions there are also different trusts anchors.
Here in Europe it's more Gaia, Gaia X in Japan is anos for example. So we will see you will have multiple trust anchors all, all over the world. And another one it's very, I would say special here. We want to verify presentations without one central verifier. So we want don't want to have a third party system. So the connectors will do this job and we have already two implementations.
One of the implementation you'll find in eclipse structures X called managed identity wallet and another one is eclipse data space components, the identity hub. And as you can see here, this is the now a proposal and that wa this is approved now and now we are looking for, people want to work with us on machine to machine wallets or B2B wallets that make the machine to machine communication available. And then I think, ah, no, so as you can see this one here that's identity related services.
And as you can see we have these core services. They are centralized now like the identity providers.
So we have one for users and for clients so shared and also so you can bring your own identity. Everything is based on business partner numbers. So we are issued these partner numbers globally like live or the dance number. So we have this managed identity wallet. So it's now still a centralized wallet but it becomes more decentralized one. So we are using also clearing house, this Gaia X clearing house. They verify all the onboarding participants and the self description factory create the self description for our clients.
And then as you can see, this decentralized services we called enablement services and the connector, they make the identity check. But now I take over to you Haan.
Thanks Mattias. So we are going to go a bit deeper now into the identity and trust and data spaces and especially in kaena X context. Just gonna try if the clicker is working.
Nope, it's not. Alright, so since this is the data data of EIC, I'm assuming you have seen this kind of depiction of decentralized identities so far. We do have instead of identity providers in decentralized identities, we have issuers because the credentials themselves are not stored within the IDP, but they are in the possession of the holders over there. So they store it in their wallet applications and in a certain later stage they can use these verifiable cred credentials, make a proof out of it and send it as a verifiable presentation to verifiers to get access to the goods and services.
And in our case, in QX context, it is about exchange of data and authentication.
Here in QX context, we do have as issuers two types of issuers. One of them is the Finity X as the first operating company and Kax network. They're responsible for onboarding organizations into the network in a trustful manner so they can interact with each other securely. And the second one is the Gaia X federation services because this is the trust anchor and they're also responsible for the regulatory framework that is coming from the EU itself.
So here on the holder side, we do have more than 80, 80 companies that are already onboarded in the network and they store their credentials and they also validate each other's credentials. So when we are making a data exchange, for example, the holder is the one who's the data consumer and the verifier is the one who's the data provider. So they verify first who they're communicating with so that they can actually grant access to this data.
On the verifiable data registry site, we do have three we we have three different verifiable data registries.
One of them is from the KA X association itself. Since they're the standardization for the KA X, we do store the credential schemas within the KA X repositories and in the finity X, the issue that are stored and also the holder dates are stored. Which brings me to the topic of the differentiation between what we are seeing in the EID and human credentials and credentials in the context of CX and the B2B context because there are two distinctive differences here.
One of them is in the human credentials you would not see that the human holder, the IDs and the ID documents being stored in a verifiable data registry due to the GDPR. So data protection laws and right to be forgotten.
However, in the context of automotive data spaces, the organizations DDS and the documents are actually stored in the verifiable data registry.
So they can also be discovered by other entities who are participating in the network. And the second thing, what what Mattias was mentioning about also is during the issuance of the credentials and the presentation of the proofs, no human interaction happens. All of this is happening in a machine to machine context.
And therefore the predominant exchange protocols like open ID for verifiable credential is not very suitable because you need a human consent and a human that is giving the consent in that area. Instead, the decentralized claims protocol is being developed right now in the ACT data space.
All right, so now we're going to be talking a bit about like how the onboarding process goes. Any company who wants to be a part of KANA X network has to go through the same process. And first and foremost what happens is that the registration services from Finity X sends an imitation email to the onboarding company.
And from here on we are going to call them as company B and they do add the company data and accept the regulatory framework. Once this is done, a business partner number is being allocated for this organization.
And this is a very important step because this business partner number is a unique identifier within the KAENA X network. And any other process that happens from here here on may it be the creation of a wallet or a creation of the di ds. And the documents occur with the context of this BPN. So once a unique VPN is being created, yeah, the company B wallet is being created with the BPN number that is allocated for that company in the managed identity wallet. So as Mathias mentioned, we are on a journey of being a centralized components to the decentralized components.
And managed identity wallet is a custodial decentralized identity wallet hosted by Finity X to bridge the gap between movie being in the centralized world to the decentralized world.
So it is hosted by Finity X, but in the future from here, like from six months to a year, every other company will be able to bring their own wallets and they can connect it as well. Once these wallets are created, the Finity X issuer issues A BPN credential, which makes that BPN number that has been allocated for that organization cryptographically verifiable and temper evident.
And in the next step the registration services sends the data that has been put in the second step the company data including the VAT number, to the compliance service of IX Digital Clearinghouse where they validate the company information, including looking into the VAT registries of different unions and countries. And once this data is validated, the self description factory sends a nons signed credential, basically a credential template to the not authorization service to be signed.
And here with that signature, the company that is being onboarded is also conformed with the GA Ex trust framework and therefore with the EU regulations, once this is also stored in the company B'S wallet.
As a last step for the onboarding, a membership credential is being issued, which says this company is now a part of the KAX network and actually interact with other actors here.
However, this is only the onboarding part. And in, in order to be able to communicate with other parties, they do also need some components or like some applications like data space connector, they can host it on the by themselves or Finity X also offers it as an enablement service. So optionally it is possible to get the EDC also being run on behalf of the company on the Finity X and they can do all bunch of other stuff as well, like purchasing and managing businesses or using business partner functions. So once wrap it up wrapped, we need to wrap it up.
Alright, two minutes maybe in the data exchange flow in order to be able to exchange any data in the CarX, these are all divided into use cases.
We either have product carbon footprint, we have sustainability quality use case, and therefore there needs to be a verifiable credential that has to be issued again. And this time it is called a use case participant verifiable credential. Once this is issued, the EDC component of the company B can ask the EDC component of another company, which is the data provider in that case for catalog request, including the verifiable presentation.
And the verifiable presentation includes three credentials in minimum. First one is the BPN credentials, we talked about this, this is who the company is about. The second one is a membership credential, whether they're an active member of KA X or not. And the last one is the use case participant credential, whether they can participate in a specific use case or not. And after the validation by the company A, they send a catalog response to company B again, where they can choose like what kind of data they want to exchange with.
And a contract negotiation happens for the, if they're interacting with with each other for the first time or after the expire of the contract that happens between only those, these two parties. And all of this happens in an automated manner based on the policies and after the contract closure, the data transfer occurs. So I hope we were able to give you a brief overview about the KA X and how it works. Thank you very much. And if you have any questions, please we don't thank.
