Harmonization across Aspect Models

[jSchuetz88]

This issue collects issues related to single properties which should be harmnoized across aspect models.

Property Name	Property definition	Domain	Note
assetSerialNumber		N/A
batchId		Production / Shopfloor	Refers to an ID, but is characerized as samm-c:Text. Not standardized
catenaXClaimPartId		Production / Shopfloor	Standardized in CX-0123, CX-0131
catenaXId		Industry Core	Used in various CX-Standard within around 20 Aspect Models. Issue: Defined, characterizations and types and spelled in different ways in different models.
catenaXPartId		Industry Core	Used in various CX-Standard within around 20 Aspect Models. Issue: Defined, characterizations and types and spelled in different ways in different models.
catenaXQualityTaskId		Indusry Core / Quality	Used in various CX-Standard within around 20 Aspect Models. Issue: Defined, characterizations and types and spelled in different ways in different models.
catenaXsiteId			see
catenaXSparePartId		Quality / Circularity	Make sure, the definition is correct.
✅ catenaXVehicleId		Quality / Circularity	Harmonized within io.catenax.shared.quality_core
✅ claimId		Quality / Circularity
customerPartId		Industry Core	Different definitions between Models are used. Check for renaming. to Customer part Number? eclipse-tractusx/sldt-digital-twin-registry#502
cxBPN			Defined, characterizations and types and spelled in different ways in different models. Should use the shared aspect model io.catenax.shared.business_partner_number
cxBusinessPartnerNumber			Defined, characterizations and types and spelled in different ways in different models. Should use the shared aspect model io.catenax.shared.business_partner_number
demandCategory		DCM	For the purpose of harmonization this property should be moved to a shared model as this is described 4 different times individually.
demandSeries			DCM
localIdentifiers		Industry Core	For the purpose of harmonization this property should be moved to a shared model as this is described multiple times individually
manufacturerIdentification		Sustaintability (DPP)	Property is characterized as a BPN, this may be right, but the name manufacturerIdentification is misleading on a semantical level.
manufacturerSerialNumber		Quality / Circularity	For the purpose of harmonization this property should be moved to a shared model as this is described multiple times individually
materialDemandId		DCM	For the purpose of harmonization this property should be moved to a shared model as this is described multiple times individually
materialGlobalAssetId		DCM / PURIS	For the purpose of harmonization this property should be moved to a shared model as this is described multiple times individually + defined with different types in different models
materialNumberCustomer		DCM	For the purpose of harmonization this property should be moved to a shared model as this is described multiple times individually + defined with different types in different models
materialNumberSupplier		DCM	For the purpose of harmonization this property should be moved to a shared model as this is described multiple times individually + defined with different types in different models
oem		Circularity	Unclear on a semantic level. Maybe this should switch to the BPN instead?
oemSerialNumber
originalEquipmentNumber
parentPartNumber		Industry Core	see PartId or customerPartId
parentSerialNumber		Industry Core	see property naming changes required:customerPartInstanceId or parentPartInstanceId
partSitesInformationAsPlanned		Industry Core	For the purpose of harmonization this property should be moved to a shared model as this is described multiple times individually
partTypeInformation		Industry Core	For the purpose of harmonization this property should be moved to a shared model as this is described multiple times individually + defined with different types in different models
plantCatenaXId		Quality / Circularity	For the purpose of harmonization this property should be moved to a shared model as this is described multiple times individually + CatenaXId usually refers to parts, here it is a plant (misleading on a semantical level)
shipmentId		N/A	Should be checked and maybe should be a UUID? A more comprehensible semantic description is required. No CX-Standards
sparePartNumber
sparePartSerialNumber
sparePartSupplierId
supplierId
van
vehicleCatenaXId
anonymizedVIN
assemblyPartNumberVersion
equipmentIdentifier
manufacturerPartId			eclipse-tractusx/sldt-digital-twin-registry#502 manufacturerPartNumber
manufacturerPartNumber
materialGlobalAssetId
serialNumber			see partInstanceId
transmissionId

[agg3fe]

Currently library is being created for the aspect models that belongs to Industry core. That library contains all the common vocabulary/properties that are used repeatedly in Industry core models. A reference to the above table can be taken while creating the library, making sure that atleast the properties mentioned in the above table (which belongs to industry core) are addresses.
FYI, @jSchuetz88 @Grand-Thibault