Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [tractusx-dev] Request Semantic Layer & Digital Twin Team
  • From: "Weiss, Arno" <arno.weiss@xxxxxxx>
  • Date: Thu, 29 Jun 2023 07:50:44 +0000
  • Accept-language: en-US
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=sap.com; dmarc=pass action=none header.from=sap.com; dkim=pass header.d=sap.com; arc=none
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=soLZJaYmJetMbH0qfw/OaxnQ2hv368m+ZwAQmoG+G0k=; b=eAxnZUbE8x75carNeN3NlszUK60k/CKdz4goblRqFZLoo1yCYvIVeegnwiv5UefXl2T2Vz48Cd8pKODefrdv0Sp6Ca4RCnTYfPiNkZ2mLDtC87uV+HJSadpph5QU04Xz1v3p4XCVnzbcZBpZ2xRPaufdMh0rJRd/dnUPZNzm87ZG30SIxLj4saAqFaCh8P7XUOTbt58ZlpsgnicwSx1vGn+LTVjSmFt5kRVHjJIoLlIjrne6DFDJktNdgEa5cioTdYAeUQYz8ayvONodexiAUM1CgzvSMnlMzlPdIgnqcBFwzV5FgXKC8eeWWcNyUMGzCG2xAHK0nJAxplupZ8BCIA==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=hjGXbVIfK3voVWvIfeF+s98UgVRqA8EoDf9u2T+N8TFd0/j6N0NBd+Lz5vAqcesgQYK64cAbPx6Xt0tFEXsiacbKmkC+zPHWJRmKLxW2081Ey75U1UGvD5fT0eotjgt417FCto8wggaXir5HHvaCDZaE1E4H6UHe6WcBJf/CVD1zIIbe9lTHN+Emks3DKVfcuzUd2sbob7FMw801bSLqoLS662DsdYtbiSIzaaVEZTcv0duvtQ5eLUIgH5fp6+yqBW4fZA3m6kizp+6/oTrYdpRrM111jq+Ht/tUVAPsXe8H79B3VWr6at7UYi93z7xjYl6DX1QzMAfPixmFpf+ixg==
  • Delivered-to: tractusx-dev@xxxxxxxxxxx
  • List-archive: <https://www.eclipse.org/mailman/private/tractusx-dev/>
  • List-help: <mailto:tractusx-dev-request@eclipse.org?subject=help>
  • List-subscribe: <https://www.eclipse.org/mailman/listinfo/tractusx-dev>, <mailto:tractusx-dev-request@eclipse.org?subject=subscribe>
  • List-unsubscribe: <https://www.eclipse.org/mailman/options/tractusx-dev>, <mailto:tractusx-dev-request@eclipse.org?subject=unsubscribe>
  • Msip_labels: MSIP_Label_76122db4-a595-414e-9ece-6adfb473e1a0_ActionId=7d00ef03-bfdb-46d7-8bf5-acc2f80f1507; MSIP_Label_76122db4-a595-414e-9ece-6adfb473e1a0_ContentBits=0; MSIP_Label_76122db4-a595-414e-9ece-6adfb473e1a0_Enabled=true; MSIP_Label_76122db4-a595-414e-9ece-6adfb473e1a0_Method=Standard; MSIP_Label_76122db4-a595-414e-9ece-6adfb473e1a0_Name=Internal; MSIP_Label_76122db4-a595-414e-9ece-6adfb473e1a0_SetDate=2023-06-28T20:52:39Z; MSIP_Label_76122db4-a595-414e-9ece-6adfb473e1a0_SiteId=87ba1f9a-44cd-43a6-b008-6fdb45a5204e;
  • Thread-index: AdmqAox9waDdV++AR/yU9589t6d0RAAVh9XQ
  • Thread-topic: Request Semantic Layer & Digital Twin Team

Hi Brian,

 

general remarks first:

 

The data about an Asset is provisioned and registered by the data owner (like a Tier 1). Catena-X moreover follows the 1-up-1-down principle. Each Data Provider only has information on what components his own asset is made of (see Aspect Model [1] SingleLevelBomAsBuilt, 1-down) and in which asset it is assembled (SingleLevelUsageAsBuilt, 1-up, for instance an OEM’s vehicle). That means that the data that a Tier 1 wants to offer CANNOT directly be linked to the twin of the OEM’s vehicle but rather to its own component. This component must in turn be referenced in the BoM of a vehicle.

 

Thus:

  1. The Tier x does not add data to the Digital Twin of a vehicle but to the Digital Twin of his own component. He does so by POSTing to the API of the Digital Twin Registry (DTR) [2]. Please bear in mind that (starting with Catena-X Release 3.2) there will be no central DTR anymore. Data Providers will be responsible for operating their own DTR and registering it in their EDC. If the Assets shall be discoverable, the Assets’ IDs must be registered with a (probably at first network-central) instance of BPN-Discovery [3].
  2. If the Tier 1 is not part of the network or does not setup his Digital Twins properly, the chain between the Tier 2 and OEM breaks. One could theorize about matching a Tier 2’s SingleLevelUsageAsBuilt with an OEM’s SingleLevelBomAsBuilt.

 

Currently, all this info is available only in the standards and components’ docs. We will aggregate it into a KIT [4] soon.

 

Hope that helps,

Arno

 

[1] eclipse-tractusx/sldt-semantic-models: sldt-semantic-models (github.com)

[2] DTR Swagger UI (catena-x.net)

[3] BPN-Discovery Swagger UI (catena-x.net)

[4] KITs Adoption View | Eclipse Tractus-X (eclipse-tractusx.github.io)

 

From: tractusx-dev <tractusx-dev-bounces@xxxxxxxxxxx> On Behalf Of Brian Burgin
Sent: Wednesday, 28 June 2023 22:54
To: tractusx-dev@xxxxxxxxxxx
Subject: [tractusx-dev] Request Semantic Layer & Digital Twin Team

 

Some people who received this message don't often get email from brian.burgin@xxxxxx. Learn why this is important

Hello Digital Twin Team,

 

I have questions about how Catena-X / Tractus-X handles supply chain workflows:

 

  1. How does a Tier 1 or Tier 2 supplier add info to a vehicle in the digital twin registry?
    1. I found mention of submodels in the doc: sldt-digital-twin-registry/docs at main · eclipse-tractusx/sldt-digital-twin-registry (github.com)
    2. But it was not clear if the vehicle OEM has to add all these or if the suppliers can directly add them and how.
  1. Can a Tier 2 supplier add info to a vehicle if there is no corresponding Tier 1 supplier above it?
    1. In other words, how does Catena-X / Tractus-X handle gaps in the supply chain?
    2. If this is supported, where and how would the Tier 2 supplier add the info to the vehicle?

 

Can you provide me answers / guidance on these questions?

 

Thank you,

 

Brian Burgin 

Principal Software Engineer - NI 

brian.burgin@xxxxxx

 

INTERNAL - NI CONFIDENTIAL

Back to the top