The objective of this issue is to ensure that the Trace-X application complies with IndustryCore 2.0.0 standards by including the specialAssetId "digitalTwinType" in its data provisioning. This will enable Trace-X to manage digital twins in a manner aligned with industry standards for interoperability and data exchange.
What's the benefit?
Introducing the "digitalTwinType" specialAssetId ensures that the Trace-X application is fully compatible with IndustryCore 2.0.0 standards, promoting better interoperability and streamlined data management for digital twins. This upgrade will make the system more aligned with the latest industry guidelines, improving its ability to participate in broader data ecosystems.
What are the Risks/Dependencies ?
One potential risk is ensuring backward compatibility with existing dtrs that might not yet support or require the "digitalTwinType" specialAssetId. Additionally, dependencies on other systems or data sources need to be assessed to ensure that they can handle this new field correctly without disrupting current workflows or causing integration issues.
Detailed explanation
Current implementation
Currently, the Trace-X system does not incorporate the specialAssetId "digitalTwinType" into its data provisioning process. This omission means it is not fully compliant with IndustryCore 2.0.0 standards, which require this field for proper digital twin identification and handling.
Proposed improvements
The proposed enhancement involves adding the "digitalTwinType" specialAssetId to the data provisioning process in Trace-X, ensuring compliance with IndustryCore 2.0.0. This change will ensure that digital twins are correctly tagged with this identifier, allowing for better alignment with industry-standard practices.
Feature Team
Contributor
Cofinity-X @rogocof
Cofinity-X @mkanal
Committer
@ds-jhartmann
@ds-mwesener
@ds-lcapellino
User Story
As a product with indents to be IndustryCore 2.0.0 conform
I want to provide the specialAssetId “digitalTwinType”
so that the data provisioning is industry core compatible
Acceptance Critiera
specialAssetId “digitalTwinType” is set in data provisioning of Trace-X
Test Cases
Test Case 1
Steps
Do something
Click something
Add something
Expected Result
Expectation
Expectation
Expectation
Architectural Relevance
The following items are ensured (answer: yes) after this issue is implemented:
[ ] This feature aligns with our current architectural guidelines
[ ] The impact on the overall system architecture has been assessed. The Feature does not require changes to the architecture or any existing standard? Please have a look here on the overarching architecture
[ ] Potential risks or conflicts with existing architecture has been assessed
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
[x] I am aware that my request may not be developed if no developer can be found for it. I'll try to contribute a developer (bring your own developer)
Overview
Explain the topic in 2 sentences
The objective of this issue is to ensure that the Trace-X application complies with IndustryCore 2.0.0 standards by including the specialAssetId "digitalTwinType" in its data provisioning. This will enable Trace-X to manage digital twins in a manner aligned with industry standards for interoperability and data exchange.
What's the benefit?
Introducing the "digitalTwinType" specialAssetId ensures that the Trace-X application is fully compatible with IndustryCore 2.0.0 standards, promoting better interoperability and streamlined data management for digital twins. This upgrade will make the system more aligned with the latest industry guidelines, improving its ability to participate in broader data ecosystems.
What are the Risks/Dependencies ?
One potential risk is ensuring backward compatibility with existing dtrs that might not yet support or require the "digitalTwinType" specialAssetId. Additionally, dependencies on other systems or data sources need to be assessed to ensure that they can handle this new field correctly without disrupting current workflows or causing integration issues.
Detailed explanation
Current implementation
Currently, the Trace-X system does not incorporate the specialAssetId "digitalTwinType" into its data provisioning process. This omission means it is not fully compliant with IndustryCore 2.0.0 standards, which require this field for proper digital twin identification and handling.
Proposed improvements
The proposed enhancement involves adding the "digitalTwinType" specialAssetId to the data provisioning process in Trace-X, ensuring compliance with IndustryCore 2.0.0. This change will ensure that digital twins are correctly tagged with this identifier, allowing for better alignment with industry-standard practices.
Feature Team
Contributor
Committer
User Story
As a product with indents to be IndustryCore 2.0.0 conform I want to provide the specialAssetId “digitalTwinType” so that the data provisioning is industry core compatible
Acceptance Critiera
Test Cases
Test Case 1
Steps
Expected Result
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