You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
jonbckr
changed the title
[Model Update]:
[Model Update]: BOMAsSpecified
Jan 23, 2023
Update Reason
Request from TC4S:
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
o @[email protected]: Habt ihr hier was abgestimmt mit der IDTA zu Hierachical Structures enabling Bills of Material Submodel?
o The catenaXIds can be added for self-explanation but the actual lookup should be focused on a combination of ownerPartNumber and ownerId (BPN)
o @[email protected]
o @[email protected]
MS1 Criteria
The text was updated successfully, but these errors were encountered: