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.
[ ] 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
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
Committer
User Stories
Acceptance Criteria
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