[R25.03] Knowledge Agents: KIT Maintenance

[obalandi]

Overview

Explain the topic in 2 sentences

The Knowledge Agents KIT will be upgraded to the new ECD release so that the Behavioural Twin use case continues to work.

What's the benefit?

Version Upgrade of the KIT

What are the Risks/Dependencies ?

No significant changes are planned. Therefore there are no known risks.

Detailed explanation

Upgrade to the latest version of EDC.

Current implementation

The latest KA is compatible with EDC 0.7.3.

Proposed improvements

Upgrade to the latest version of EDC.

Feature Team

Contributor

• @obalandi
• @drcgjung

Committer

• @almadigabor

User Stories

• Behavioural Twin

Acceptance Criteria

• Ensured compatibility with depending components based on integration/E2E tests
• Security issues are solved
• Quality Gate has to be passed

Test Cases

The test cases from the previous release are used: eclipse-tractusx/knowledge-agents#168

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]

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

[ma3u]

Please consider T-X EDC v0.7.6 or later. There are an important bugfix:

+eclipse-tractusx/tractusx-edc#1618

[ma3u]

Any change in the relevant standards required?

• CX-0059 Use Case Behaviour Twin Endurance Predictor v2.0.0
• CX-0138 Use Case Behaviour Twin Endurance Estimator v1.0.1
• CX-0141 Use Case Behaviour Twin Health Indicator v1.0.0

[obalandi]

Any change in the relevant standards required?

• CX-0059 Use Case Behaviour Twin Endurance Predictor v2.0.0
• CX-0138 Use Case Behaviour Twin Endurance Estimator v1.0.1
• CX-0141 Use Case Behaviour Twin Health Indicator v1.0.0

@ma3u, no changes are required.