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

[Model Update]: BOMAsSpecified #36

Closed
5 of 6 tasks
jonbckr opened this issue Jan 23, 2023 · 4 comments
Closed
5 of 6 tasks

[Model Update]: BOMAsSpecified #36

jonbckr opened this issue Jan 23, 2023 · 4 comments
Labels
MS1_Approved Checklist "MS1 Request for Model Developement" is approved.

Comments

@jonbckr
Copy link
Contributor

jonbckr commented Jan 23, 2023

Update Reason

Request from TC4S:

  • BoMAsSpecified describes top down View from a OEM (Producer) of the vehicle. How is this releated to other BOM View (e.g. in Traceability)? As we using common data elements? Shouldn’t we rather have a standardization document on BoM in general and describe, when to use which view (irrespective of a use case)?
    o related to other BOM view in that sense, that they both depict the structure of the specified/buit/etc. asset. In contrast to Traceability, this BOM addresses the full asset how it should be set-up and that an OEM is responsible for. It is not affected by missing supplier as it is in the traceabilty BOMs, where a component cannot be provided as soon as the respective supplier is not part of Catena-X. The BOMAsSpecified tries to cope with the BOM approaches, but cannot be addressed by the same structure and therefor is an own data model
  • Which other standards have been looked at before we created our own BoM view? IDTA is currently in the specification phase of a BoM model in Industry4.0 context – has there been any alignment between Catena-X and IDTA?
    o @[email protected]: Habt ihr hier was abgestimmt mit der IDTA zu Hierachical Structures enabling Bills of Material Submodel?
  • Why do we create only a BOM without references to other DT?
    o The catenaXIds can be added for self-explanation but the actual lookup should be focused on a combination of ownerPartNumber and ownerId (BPN)
  • Description & item category description are 100% identical (copy paste)  does not make sense
    o @[email protected]
  • Part: Description is TBD  This is not adequate for public release
    o @[email protected]

MS1 Criteria

  • The model that should be updated exists
  • The referenced use case exists
  • The potential updates are discussed with all stakeholders
  • The potential update will be either
    • backward compatible or
    • a (chain of) migration strategy(-ies) from all non-deprecated previous versions to the new model will be developed
@jonbckr jonbckr changed the title [Model Update]: [Model Update]: BOMAsSpecified Jan 23, 2023
@mthiers
Copy link
Contributor

mthiers commented Jan 23, 2023

core team:
all points can be omitted according to @tram Kevin except for part description

@Kevinataccenture Kevin tram: will deliver description until 23.01.2023 EOB
MS1 approval given
(@bs-jokri will do post documentation)

@bs-jokri bs-jokri added the MS1_Approved Checklist "MS1 Request for Model Developement" is approved. label Jan 23, 2023
@Kevinataccenture
Copy link

TBD should be replaced with:
The description of the part in the primary language of the production facility of the product owner.

@mthiers
Copy link
Contributor

mthiers commented Jan 27, 2023

The description of the part in the primary language of the production facility of the product owner. -> Done

@bs-jokri
Copy link
Contributor

bs-jokri commented Feb 8, 2023

closed by #48

@bs-jokri bs-jokri closed this as completed Feb 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
MS1_Approved Checklist "MS1 Request for Model Developement" is approved.
Projects
None yet
Development

No branches or pull requests

4 participants