Open corinastolz opened 2 weeks ago
Some hints from Release Management (@ther3sa) and Tractus-X Project Lead (@stephanbcbauer)
Hi @corinastolz, hi @tunacicek , this feature is q duplicat to https://github.com/eclipse-tractusx/sig-release/issues/934. Both aim to create a kit for ligistics and customs. I think, we have to delete an of them.
@all, please move the content from the already closed feature #934 to this one. I will set it to Backlog and add the milestone 25.03
@ALL, please move the content from the already closed feature #934 to this one. I will set it to Backlog and add the milestone 25.03
done
Overview
Releasing KIT for logistics, content so far: vision, mission and benefits, digital twin for transport unit and transport itself as well as matching aspect models like "PackingList" and "ShippingData". Seems to be as draft and transfer-vehicle to continue work on this topic in new setup in association.
What's the benefit?
Provide logistic and customs data in CX standardized way and cover the gap of data between supplier and customer
What are the Risks/Dependencies ?
Dependencies: Traceability + Industry Core, EG Digital Twins
Detailed explanation
Current implementation
no current implementation excisting, it's the first KIT for logstic and customs use case
Proposed improvements
KIT for logistics and customs are available
Feature Team
EG Traceability
Contributor
Committer
@tunacicek
@danielmiehle
User Stories
Acceptance Criteria
Logistic & Customs KIT is documentated and available
Ensure compability with Logistic Standard CX-0150 Initial PR Final PR
Test Cases
Not necessary, it is only a KIT documentation
Architectural Relevance
The following items are ensured (answer: yes) after this issue is implemented:
Justification: (Fill this out, if at least one of the checkboxes above cannot be ticked. Contact the Architecture Management Committee to get an approval for the justification)
Additional information