mkanal commented 7 months ago

As Business Owner I want to adjust to AAS and DTR so that IRS is conform with IndustryCore standard CX-0126 and CX-0127

Link

Discussion

the api parameter bomLifycle can thus become obsolete? We can determine the BomLifycle for an asset via the AAS and determine the traversal aspect from this determination
digitalTwinType MUST be used to detect correct BOMLifecylce to have a detemined determination of the BomLifycle in order to be able to give the caller a coherent error message.
As-Is: The Bomifecyle is assumed to be correct for a globalAssetId - In case the TraversalAspect for the BOMLifycle defined via the api parameter BOMLifycle does not exisits the irs provides a tombstone - In this case it is not proven if the requestor has defined the wrong BomLifecyle for the request or the BomLifecyle is correct and TraversalAspect does not exist. By using the digitalTwinType parameter, the detection would be more reliable.
[ ] Clarification for hasAlternatives with a BOMLifecycle switch in the supply chain from asPlanned to asBuilt

API parameter bomLifecycle is not required any more - detection of bomLifecyle could be managed by the AAS parameter digitalTwinType

In case batch api endpoint is called with different bomLifecyle would this lead to a valid jobResponse

[ ] AAS parameter 'digitalTwinType' is used to detect BOMLifecycle
[ ] In case a job is started with incorrect api parameter BomLifecyle a tombstone is created.
[ ] Configuration of parameter 'digitalTwinType' for all dDTR instances on * environments (Refer to concept)
[ ] registry.externalSubjectIdWildcardAllowedTypes = manufacturerPartId,digitalTwinType
[ ] Detection of BOMLifecycle in AAS according to concept
[ ] Adjust testdata script to set this parameter when creating aas

mkanal commented 6 months ago

@jzbmw Please let us have a short alignment on this topic.

mkanal commented 6 months ago

Prio was set to MEDIUM as this might not be relevant for implementation.