🌟🚀[IRS] Efficient orchestration of edc negotations

[mkanal]

Overview

Efficiently orchestrating EDC negotiations for job and order handling can reduce redundancy by minimizing unnecessary contract negotiations. This optimization enhances processing efficiency, reducing overhead, especially for IRS job handling.

Explain the topic in 2 sentences

Efficiently orchestrating EDC negotiations for job and order handling can reduce redundancy by minimizing unnecessary contract negotiations. This optimization enhances processing efficiency, reducing overhead, especially for IRS job handling.

What's the benefit?

Streamlining EDC negotiations can improve overall processing efficiency by avoiding redundant contract negotiations, lowering operational overhead, and providing a faster, more resource-efficient system for handling IRS-related jobs.

What are the Risks/Dependencies ?

Detailed explanation

Currently, each initiated job functions in isolation, leading to multiple, redundant contract negotiations when accessing the same DT Registry Asset in the EDC catalog. This isolated job execution results in non-performant outcomes and inefficiencies due to the repetitive negotiation processes involved. The proposed concept aims to create a streamlined orchestration approach that can handle EDC negotiations in a more cohesive, efficient way, thus minimizing redundant contract processes across different job requests that require the same catalog offer

Current implementation

Each job initiates independently, leading to redundant and isolated contract negotiations.
Multiple requests for the same DTR or SubmodelServer or catalog offer in different jobs trigger separate, repeated contract negotiations.
This results in inefficient processing with a higher than necessary overhead and execution time, as each job redundantly verifies and secures access.

Proposed improvements

Consolidates negotiations for same assets, reducing the frequency and redundancy of individual negotiations.
Introduces a job grouping mechanism that identifies and manages catalog offers requested by multiple jobs simultaneously.
Add ADRs (Architecture Decision Records) to document this streamlined approach, ensuring all dependencies are noted for efficient implementation.

Feature Team

Contributor

• Cofinity-X @rogocof
• Cofinity-X @mkanal

Committer

• @ds-jhartmann
• @ds-mwesener
• @ds-lcapellino

User Stories

• Issue 1, linked to specific repository
• Issue 2, linked to another specific repository

Acceptance Criteria

• 🌟🚀[CONCEPT] Efficient orchestration of edc negotations item-relationship-service#894

Test Cases

Test Case 1

Steps

1. Do something
2. Click something
3. Add something

Expected Result

1. Expectation
2. Expectation
3. Expectation

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 Backlog -> Since for Backlog some requirements are missing ... please update them
• Please add missing sections from the feature template, or fill them out
• Please add assignee (overall responsible person who drives the feature)