Support Mass Data Files as Submodels of Digital Twins

[thomas-henn]

Overview

Introduction of a definition of digital twins, each of which forms an administration shell around mass data.

Software development for the reference implementation of the Tractus-X Open Source Digital Twin Registry, which supports aspects in the form of mass data in digital twins. In particular, the current use case “Live Quality Loops” is to be enabled with digital twins.

Explain the topic in 2 sentences

Create a concept/solution on how to defining the shell submodeldescriptors to represent mass Data (like parquet) reference.

What's the benefit?

Transfer larger files between participants.

What are the Risks/Dependencies ?

• Dependency to AAS APIs
• Clarify the possible file size -> AASX Fie support only files with max.size 100GB

Detailed explanation

Current implementation

Proposed improvements

Feature Team

Contributor

• @agg3fe
• @tunacicek

Committer

• @agg3fe
• @tunacicek

User Stories

• [New Model]: Asepct Model to Handle Parquet Files sldt-semantic-models#762
• Definition of submodelDescriptor to support parquet files eclipse-tractusx.github.io#942
• TBD// Standard request needed for aspect model, and "Quality KIT" for definition of use of digital twins

Acceptance Criteria

Test Cases

Expected Result

Architectural Relevance

The following items are ensured (answer: yes) after this issue is implemented:

• This feature aligns with our current architectural guidelines
  • Data Sovereignty: All data sharing activities across company boundaries follow the Catena-X Regulatory Framework, in particular the Data Exchange Governance, and the Dataspace Protocol via a compliant Connector (like the tractusx-edc or similar, see Connector KIT)
    • CX-0010 Business Partner Number
    • CX-0013 Identity of Member Companies
    • CX-0018 Data Space Connectivity (EDC)
    • CX-0049 DID Document Schema
    • CX-0050 Framework Agreement Credential
    • CX-0149 Verified Company Identity
  • Interoperability: Digital Twins are used (compliant to the Digital Twin KIT and the Industry Core KIT)
    • CX-0001 EDC Discovery API
    • CX-0002 Digital Twins in Catena-X
    • CX-0018 Data Space Connectivity (EDC)
  • Data Format:
    • The data model is based on a published Semantic Model
• 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

• 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)

[stephanbcbauer]

Presented in the DRAFT Feature Freeze → Committer is available
Unclear if code changes are needed, or if it's just an adaptation of descriptions

[stephanbcbauer]

@thomas-henn @agg3fe @tunacicek not sure about this feature. Is it planned to present it in tomorrow's planning? It was already presented in the DRAFT Feature Freeze, but the status is still Inbox. Did we miss something?

[stephanbcbauer]

Some hints from Release Management (@ther3sa) and Tractus-X Project Lead (@stephanbcbauer)

• Status currently in Inbox. ⇾ Only features with status backlog are considered in open planning
• Please add missing sections from the feature template, or fill them out

[tunacicek]

Some hints from Release Management (@ther3sa) and Tractus-X Project Lead (@stephanbcbauer)

• Status currently in Inbox. ⇾ Only features with status backlog are considered in open planning
• Please add missing sections from the feature template, or fill them out

Hi @stephanbcbauer ,
thanks for the hint. I change the status to backlog

[tom-rm-meyer-ISST]

During planning I had two questions answered by @tunacicek

1. Is this a concpetual feature only so that you perform gap analysis (what needs to be changed to support mass data files)? This means that the actual execution of needed changes comes after it - yes
2. Will you provide guidelines for e.g. quality use case? They currently use m:n quality tasks during transfers that are not organized in digital twins. - yes