Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consume PartTypeInformation when creating a digital twin on customer side #279

Closed
tom-rm-meyer-ISST opened this issue Feb 28, 2024 · 0 comments · Fixed by #296
Closed

Consume PartTypeInformation when creating a digital twin on customer side #279

tom-rm-meyer-ISST opened this issue Feb 28, 2024 · 0 comments · Fixed by #296

Comments

@tom-rm-meyer-ISST
Copy link
Contributor

tom-rm-meyer-ISST commented Feb 28, 2024

As a customer ,
I want to consume the PartTypeInformation ,
so that I can reuse the catena-x id in my supplier-specific twin .

Hints / Details

  • As a customer I need to create a twin for each supplier who supplies a material (materialPartnerRelationship)
  • When creating a twin, I need to lookup the supplier's twin for the materialNumberSupplier / manufacturerPartId and get the PartTypeInformation submodel so that I can save the catena-x id for the supplier's twin
    • save id in MaterialPartnerRelationship
    • set Catena-X ID in globalAssetId during creation of own twin
  • If no twin exists on supplier side, don't create a twin, as the missing supplier-specific catena-x id would lead to an error when e.g. the supplier later gets the submodel.

Outcome / Acceptance Criteria

Outcome

  • customer and supplier twin have the same catena-x id

Acceptance Criteria

  • catena-x id of a supplier partner is taken over into materialPartnerRelationship
  • supplier-specific twin created by customer, has same catena-x id as the supplier's twin

Out of Scope

  • Concept to retrigger creation of missing twins
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant