Repository: eclipse-tractusx/tractus-x-umbrella
Pull request #241: docs: Solution design for the "Hausanschluss" Bundle
Author: login: ds-jhartmann
Created: 2025-03-28T12:02:19Z | Merged: 2025-04-08T13:47:44Z

<!-- 
Thanks for your contribution! 
Please follow the instructions on your PRs title and description.
aligned title description: '(feat|fix|chore|doc): _description of introduced change_'
Important: Contributing Guidelines can be found here: https://eclipse-tractusx.github.io/docs/oss/how-to-contribute
Info: <!- text comments ->  will be hidden from the rendered preview of your PR.
-->

## Description
<!-- 
Please describe your PR: 
- What does this PR introduce? 
- Does it fix a bug? 
- Does it add a new feature?
- Is it enhancing documentation?
-->

- add solution design for the working package "Hausanschluss" Bundle

<!-- Please tag the related issue `Fixes or Updates #issue_number`, if applicable. -->

## Pre-review checks

Please ensure to do as many of the following checks as possible, before asking for committer review:

- [x] DEPENDENCIES are up-to-date. [Dash license tool](https://github.com/eclipse/dash-licenses). Committers can open IP issues for restricted libs.
- [x] [Copyright and license header](https://eclipse-tractusx.github.io/docs/release/trg-7/trg-7-02) are present on all affected files



Diff:
diff --git a/.github/workflows/trufflehog.yml b/.github/workflows/trufflehog.yml
index f13830f4..c994ed8f 100644
--- a/.github/workflows/trufflehog.yml
+++ b/.github/workflows/trufflehog.yml
@@ -53,7 +53,7 @@ jobs:
         with:
           path: ./  # Scan the entire repository
           base: "${{ github.event.repository.default_branch }}"  # Set base branch for comparison (pull requests)
-          extra_args: --filter-entropy=4 --results=verified,unknown --debug
+          extra_args: --filter-entropy=4 --results=verified,unknown --debug --only-verified
       
       - name: Scan Results Status
         if: steps.trufflehog.outcome == 'failure'
diff --git a/docs/concept/TAP7.1-solution-design.md b/docs/concept/TAP7.1-solution-design.md
new file mode 100644
index 00000000..d6b11b7d
--- /dev/null
+++ b/docs/concept/TAP7.1-solution-design.md
@@ -0,0 +1,591 @@
+# Solution Design "Hausanschluss" Bundle Concept
+
+<!-- TOC -->
+* [Solution Design "Hausanschluss" Bundle Concept](#solution-design-hausanschluss-bundle-concept)
+* [1 Business Case](#1-business-case)
+  * [1.1 Executive Summary](#11-executive-summary)
+  * [1.2 Business Need](#12-business-need)
+  * [1.3 Objectives](#13-objectives)
+  * [1.4 Expected Deliverables](#14-expected-deliverables)
+  * [1.5 Benefits](#15-benefits)
+  * [1.6. Dependencies](#16-dependencies)
+  * [1.7. Success Criteria](#17-success-criteria)
+  * [1.8. Out of Scope](#18-out-of-scope)
+* [2 Requirements Analysis](#2-requirements-analysis)
+  * [2.1 Assumptions](#21-assumptions)
+  * [2.2 Requirements Catalog](#22-requirements-catalog)
+* [3 AS-IS Analysis](#3-as-is-analysis)
+  * [3.1 People](#31-people)
+    * [3.1.1 Target Group Analysis](#311-target-group-analysis)
+  * [3.2 Process](#32-process)
+    * [3.2.1 Use Case View (high-level)](#321-use-case-view-high-level)
+  * [3.4 System](#34-system)
+    * [3.4.1 Context Delimitation](#341-context-delimitation)
+      * [Existing Umbrella Chart Structure](#existing-umbrella-chart-structure)
+* [4 TO-BE Design](#4-to-be-design)
+  * [4.1 People](#41-people)
+    * [4.1.1 Target Group Analysis](#411-target-group-analysis)
+  * [4.2 Process](#42-process)
+    * [4.2.1 Use Case View (high-level)](#421-use-case-view-high-level)
+      * [Group 1: Product developer](#group-1-product-developer)
+      * [Group 2: Product Tester](#group-2-product-tester)
+      * [Group 3: Product Manager](#group-3-product-manager)
+      * [Use Case diagram](#use-case-diagram)
+    * [4.2.2 Business Process (SCC Artifact)](#422-business-process-scc-artifact)
+      * [Chart Release Process](#chart-release-process)
+      * [Capability Bundle Structure](#capability-bundle-structure)
+      * [Deployment strategies](#deployment-strategies)
+        * [Role: Data Provider](#role-data-provider)
+        * [Role: Data Consumer](#role-data-consumer)
+        * [Role: Enablement Provider](#role-enablement-provider)
+      * [Bring your own](#bring-your-own)
+      * [Scalability](#scalability)
+      * [Interoperability](#interoperability)
+  * [4.4 System](#44-system)
+    * [4.4.1 Context Delimitation / 4.4.2 Interface Documentation](#441-context-delimitation--442-interface-documentation)
+* [5 Build](#5-build)
+  * [5.1 DevOps Setup Definition](#51-devops-setup-definition)
+    * [5.1.1 Tool Chain Definition](#511-tool-chain-definition)
+        * [Version Control & Source Code Management](#version-control--source-code-management)
+        * [Build and CI/CD Tools](#build-and-cicd-tools)
+        * [Testing and Validation Tools](#testing-and-validation-tools)
+        * [Release Management & Deployment](#release-management--deployment)
+* [NOTICE](#notice)
+<!-- TOC -->
+
+# 1 Business Case
+
+## 1.1 Executive Summary
+
+The "Hausanschluss" Bundle aims to simplify the installation of the enablement services Eclipse Dataspace
+Connector (EDC), Digital Twin Registry (DTR), and their supporting components. By developing a flexible, parameterizable
+installation package, the project seeks to reduce deployment complexity and lower barriers to participation in the
+Catena‑X data space. This bundle will enable independent component updates and support a modular "bring your own"
+approach, ultimately fostering a more efficient and accessible ecosystem for diverse participants—such as testers,
+external product developers, product testers, and small and medium-sized enterprises.
+
+## 1.2 Business Need
+
+Current deployment methods for data space integration are complex and require significant manual effort. This PoC
+addresses the need to:
+
+- **Reduce Complexity:** Simplify the deployment topology by bundling components into capabilities.
+- **Automate Deployment:** Provide an automated installation package using Kubernetes and HELM.
+- **Minimize Configuration Overhead:** Streamline the integration process by providing pre-configured bundles that require only minimal manual parameter adjustments.
+- **Extend Documentation:** Provide a detailed documentation tailored to the target groups.
+- **Enable Extension:** Design the system to allow the seamless addition of new components or capabilities.
+
+## 1.3 Objectives
+
+- **Simplify Deployment and Maintenance:** Develop an installation package that minimizes manual configuration through
+  automation.
+- **Ensure Modularity:** Structure the bundle so that components can be independently installed, updated, or replaced
+  without affecting other services.
+- **Facilitate Flexibility:** Implement a "bring your own" model for key components, such as EDC, PostgreSQL, and HashiCorp
+  Vault, to allow tailored deployments that meet specific needs.
+- **Increase Accessibility**: Lower entry barriers for new participants by reducing technical complexity and operational
+  dependencies.
+- **Scalability:** Structure the bundles so that they can be deployed multiple times.
+
+## 1.4 Expected Deliverables
+
+- **PoC Documentation:** A concept and architecture overview highlighting the modular design.
+- **Modular Installation Package:** A set of HELM charts for deploying the enablement service bundles:
+    - **Dataspace Connector:** Including the Eclipse Dataspace Connector, EDC PostgreSQL, and HashiCorp Vault.
+    - **Digital Twin Bundle:** Featuring components such as the Decentral DT Registry (with “bring your own” PostgreSQL)
+    - **Data Persistence Layer Bundle:** Including a simple Submodel Server to store semantic data.
+    - **Identity Wallet Bundle:** Covering the Identity Wallet functionality.
+- **Demonstration Environment:** A test deployment showcasing reduced complexity and improved efficiency.
+- **Basic User Guide:** Instructions on how to deploy and update the PoC bundle.
+
+## 1.5 Benefits
+
+- **Operational Efficiency:** Faster and more reliable deployments with less manual work.
+- **Scalability:** A modular design that can be scaled or adapted for future full-scale deployments.
+- **Ease of Adoption:** Simplified deployment processes make it easier for testers and external developers to engage.
+
+## 1.6. Dependencies
+
+- **Interoperability** with the CATENA‑X standards.
+
+## 1.7. Success Criteria
+
+- **Technology Readiness Level:** Achievement of a Technology Readiness Level (TRL) of 3, as specified in the requirements.
+- **Functional PoC Deployment:** Demonstrated automated, modular installation with reduced manual steps.
+- **Simplified Configuration:** Clear evidence of reduced configuration complexity.
+- **Positive Feedback:** End-user validation from a select group of demo participants and the Tractus-X community.
+- **Documentation Completeness:** Availability of concise deployment and user guides.
+
+## 1.8. Out of Scope
+
+- **Full Production Readiness:** This PoC is not intended to be a production-ready solution.
+- **Core Services Exclusion:** Core services are not part of the Hausanschluss Bundles.
+- **App Provider Role:** The role of App Provider is considered out of scope for this deployment.
+- **Alternative Deployment Techniques:** While the evaluation of alternative deployment methods is acknowledged, the primary
+  focus remains on Kubernetes and HELM-based deployment.
+
+# 2 Requirements Analysis
+
+## 2.1 Assumptions
+
+## 2.2 Requirements Catalog
+
+| ID             | Requirement                                                                                                                                                                                                                                                                                                                                          | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | Deliverables / Acceptance Criteria                                                                                                                                                                                                                                                                                                                                                                                   |
+|----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| [WP-7.1.-D001] | The Hausanschluss Bundle aims to simplify the installation and maintenance of the EDC and other components that together ensure a “Hausanschluss”. A flexible, parameterizable installation package is intended to reduce complexity and make integration more efficient, thereby simplifying participation in Catena‑X for additional participants. | Specification and development of a flexible, parameterizable installation package that reduces the complexity of installing and maintaining the required components for seamless integration into the Catena‑X data space. This package should facilitate updates and new versions, making participation in Catena‑X more efficient and accessible. In doing so, SMEs shall be enabled to participate without high costs or dependency on SaaS providers while maintaining control over their IT infrastructure. | [WP-7.1.-D001] Concept for the Hausanschluss is created                                                                                                                                                                                                                                                                                                                                                              |
+| 7.1.1.1        | The solution concept must define the Capability Bundles structures to be implemented. For each Capability Bundle, the included bundles and their versions are mapped.                                                                                                                                                                                | The following Capability Bundle structure is implemented:                                                                                                                                                                                                                                                                                                                                                                                                                                                        | The structure of the Capability Bundles for the Enablement Services has been specified. For version R24.12 it is clearly defined which Tractus‑X services and components are assigned to each Capability Bundle                                                                                                                                                                                                      |
+| 7.1.1.2        | Definition of Data Space Roles                                                                                                                                                                                                                                                                                                                       | Data Consumer, Data Provider, Enablement Service Provider                                                                                                                                                                                                                                                                                                                                                                                                                                                        | As part of the target group analysis, the target groups are defined and aligned with the data space roles. <br>Mapping from data space role to target group has been completed. <br>Mapping from target group to data space role has been completed. <br>An assignment of data space roles to Capability Bundles has been made.                                                                                      |
+| 7.1.1.4        | Modularity & Maintainability: Components and services must be assigned to a single Capability Bundle.                                                                                                                                                                                                                                                | Assignment of components and services to a defined Capability Bundle. <br>Each component and service should be assigned to only one Capability Bundle. <br>Dependencies between Capability Bundles are allowed.                                                                                                                                                                                                                                                                                                  | Components and Services should only be part of one bundle. <br>Each bundle must be deployable in isolation and can be installed, updated, or removed independently. <br>Capability Bundles must be organized in separate HELM sub‑charts. <br>Circular dependencies between bundles must be avoided.                                                                                                                 |
+| 7.1.1.5        | Modularity & Maintainability: Concept for reducing deployment complexity                                                                                                                                                                                                                                                                             | The system deployment should be optimized to reduce the existing complexity. The goal is to make the provisioning process more efficient, robust, and easier to maintain.                                                                                                                                                                                                                                                                                                                                        | **Simplification of deployment processes:** A reduction of manual configuration steps has been achieved. <br>**Transparency and traceability:** Clearly documented deployment steps are provided. <br>**Improvements of Chart configuration by:** <br>usage of template  <br>reducing configuration options <br>reducing manual steps in the setup                                                                   |
+| 7.1.1.6        | Modularity & Maintainability                                                                                                                                                                                                                                                                                                                         | Charts are published automatically.                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | Charts are published via a publicly accessible charts repository.                                                                                                                                                                                                                                                                                                                                                    |
+| 7.1.1.13       | Solution Concept                                                                                                                                                                                                                                                                                                                                     | Creation of a solution design for the “Hausanschluss” Bundle.                                                                                                                                                                                                                                                                                                                                                                                                                                                    | The solution design for the "Hausanschluss" Bundle is created. <br>The solution design for the "Hausanschluss" Bundle is published in the repository: https://github.com/eclipse-tractusx/tractus-x-umbrella.                                                                                                                                                                                                        |
+| 7.1.1.14       | Scalability of Enablement Services                                                                                                                                                                                                                                                                                                                   | Scalability of Enablement Services                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | Developers should be able to deploy an arbitrary number of Enablement Services. <br>Example: Up to 3 EDCs can be provided.                                                                                                                                                                                                                                                                                           |
+| 7.1.1.16       | Interoperability                                                                                                                                                                                                                                                                                                                                     | Interoperability                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | Interoperability with the CATENA‑X standards. <br>This interoperability is documented and traceable.                                                                                                                                                                                                                                                                                                                 |
+| [WP-7.1.-D002] | [WP-7.1.-D002] Target group for the specification is defined.                                                                                                                                                                                                                                                                                        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | [WP-7.1.-D002] Target group for the specification is defined.                                                                                                                                                                                                                                                                                                                                                        |
+| 7.1.2.1        | Target Group Analysis                                                                                                                                                                                                                                                                                                                                | The target group analysis for the "Hausanschluss Bundle"is defined.                                                                                                                                                                                                                                                                                                                                                                                                                                              | The analysis has been conducted. <br>The target group is included in the solution concept <br>To be clarified: What is included in the Hausanschluss and who can operate it in which scenario (OEM, SME, service provider, etc.).                                                                                                                                                                                    |
+| [WP-7.1.-D003] | [WP-7.1.-D003] Decentralized components and services defined                                                                                                                                                                                                                                                                                         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | [WP-7.1.-D003] Decentralized components and services have been defined.                                                                                                                                                                                                                                                                                                                                              |
+| 7.1.3.1        | See [WP-7.1.-D001-AC001]                                                                                                                                                                                                                                                                                                                             |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | See [WP-7.1.-D001-AC001]                                                                                                                                                                                                                                                                                                                                                                                             |
+| [WP-7.1.-D004] | [WP-7.1.-D004] Documentation of the Hausanschluss Bundle is completed                                                                                                                                                                                                                                                                                |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | [WP-7.1.-D004] Documentation of the Hausanschluss Bundle is completed                                                                                                                                                                                                                                                                                                                                                |
+| 7.1.4.1        | Documentation of the Hausanschluss-Bundles                                                                                                                                                                                                                                                                                                           | Usability                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | Documentation is provided that enables an experienced product developer - with knowledge of Helm Charts, Docker, and Vaults - to deploy the chart independently without external help. <br>A troubleshooting and FAQ section is included to support the developer. <br>Prerequisites, skills, and technology requirements are outlined, detailing what a developer must know to perform the deployment autonomously. |
+| 7.1.4.2        | Documentation of the Hausanschluss-Bundles                                                                                                                                                                                                                                                                                                           | Documentation of the Hausanschluss-Bundles is completed.                                                                                                                                                                                                                                                                                                                                                                                                                                                         | Documentation is provided for: <br>Configuration of the defined bundles according to the specified requirements and parameters. <br>Integration of the documentation into the Umbrella HELM Charts. <br>Integration into the Umbrella HELM Chart to ensure consistent deployment.                                                                                                                                    |
+| [WP-7.1.-D005] | [WP-7.1.-D005] Umbrella HELM Charts for the Hausanschluss developed, tested, and documented                                                                                                                                                                                                                                                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | [WP-7.1.-D005] Umbrella HELM Charts for the Hausanschluss have been developed, tested, and documented.                                                                                                                                                                                                                                                                                                               |
+| 7.1.5.1        | Re-activate Umbrella HELM Charts to the latest release state                                                                                                                                                                                                                                                                                         | The Enablement Services components of the Umbrella HELM Charts must be updated to version R24.12. This includes the following upgrades: <br> Upgrade DTR to version R24.12 (#188) <br>Upgrade EDCs to version R24.12 (#193) <br>Update SSI-DIM-Wallet-Stub to version 0.1.8 (#206)                                                                                                                                                                                                                               | The HELM Chart will then contain the updated versions of the components. <br>After the upgrade, the components (DTR, EDCs, SSI‑DIM‑Wallet‑Stub) run stably without functional impairments. <br>The deployment pipeline for the HELM Chart executes successfully. <br>Relevant tests & smoke tests (e.g., integration tests) confirm the migration.                                                                   |
+| 7.1.5.2        | Hierarchical structuring and bundling of Enablement Service components in the Umbrella HELM Chart                                                                                                                                                                                                                                                    | The Umbrella HELM Chart should be structured hierarchically so that related Enablement Service components are grouped into bundles. <br>The Umbrella HELM Chart must have a clear hierarchical structure. <br> Each Enablement Service component must be assigned to a unique bundle.<br>No circular dependencies between bundles are allowed.                                                                                                                                                                   | The chart is modular and divided into defined bundles. <br>Each bundle can be deployed and maintained independently.                                                                                                                                                                                                                                                                                                 |
+| 7.1.5.3        | Interchangeability of bundle components via “Bring-Your-Own” components                                                                                                                                                                                                                                                                              | Bundle components should be interchangeable through “Bring-Your-Own” components. <br>“Bring your own” is available for every component and means that these components do not have to be delivered by default with the Umbrella Chart but can be provided by the respective users.                                                                                                                                                                                                                               | Bundle components can be interchanged by “Bring-Your-Own” components.                                                                                                                                                                                                                                                                                                                                                |
+| [WP-7.1.-D006] | [WP-7.1.-D006] Product developed according to a Technology Readiness Level (TRL) of 3                                                                                                                                                                                                                                                                |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | [WP-7.1.-D006] The product is developed according to a Technology Readiness Level (TRL) of 3                                                                                                                                                                                                                                                                                                                         |
+| 7.1.6.1        | POC                                                                                                                                                                                                                                                                                                                                                  | Creation of a POC for the "Hausanschluss" Bundle                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | POC implementation is completed. <br>POC has been presented in a demo.                                                                                                                                                                                                                                                                                                                                               |
+| 7.1.6.2        | Deployment Strategy                                                                                                                                                                                                                                                                                                                                  | The provisioning of bundles is carried out independently. <br>There must be an option to selectively activate or deactivate bundles.                                                                                                                                                                                                                                                                                                                                                                             | Configuration is managed via HELM values, allowing flexible adaptation according to the environment.                                                                                                                                                                                                                                                                                                                 |
+
+# 3 AS-IS Analysis
+
+## 3.1 People
+
+### 3.1.1 Target Group Analysis
+
+See "4.1.1 To-be Target Group Analysis" below. No deviations between As-is and To-be target groups have been identified.
+
+## 3.2 Process
+
+### 3.2.1 Use Case View (high-level)
+
+Umbrella Chart is intended for the following Use Cases:
+
+| Actor             | Use case                                                                                             |
+|-------------------|------------------------------------------------------------------------------------------------------|
+| Product Developer | Sandbox Environments: Create local environments to evaluate and experiment with Catena-X components. |
+| Product Developer | Development: Provide a unified setup for contributors and developers working on Tractus-X projects.  |
+| Product Tester    | Testing: Run end-to-end tests for Catena-X services.                                                 |
+| Product Manager   | Evaluate the dataspace to assess if their product can be used within Catena-X.                       |
+
+## 3.4 System
+
+### 3.4.1 Context Delimitation
+
+#### Existing Umbrella Chart Structure
+
+````mermaid
+flowchart
+    subgraph "Umbrella Chart"
+        ChartYaml["Chart.yaml"]
+        subgraph charts
+            Portal["Portal"]
+            CentralIdp["CentralIdp"]
+            SharedIdp["SharedIdp"]
+            DiscoveryFinder["Discovery Finder"]
+            SDFactory["SD-Factory"]
+            SSICredentialIssuer["SSI Credential Issuer"]
+            SemanticHub["Semantic Hub"]
+            BPDM["BPDM"]
+            DataConsumer["Data Consumer"]
+            DataProvider["Data Provider"]
+            BDRS["BDRS"]
+            SSIWalletStub["SSI Wallet Stub"]
+        end
+        subgraph "tx-data-provider"
+            EDC["EDC"]
+            DTR["DTR"]
+            SubmodelServer["Submodel Server"]
+        end
+    end
+
+    ChartYaml --> Portal
+    ChartYaml --> CentralIdp
+    ChartYaml --> SharedIdp
+    ChartYaml --> DiscoveryFinder
+    ChartYaml --> SDFactory
+    ChartYaml --> SSICredentialIssuer
+    ChartYaml --> SemanticHub
+    ChartYaml --> BPDM
+    ChartYaml --> DataConsumer
+    ChartYaml --> DataProvider
+    ChartYaml --> BDRS
+    ChartYaml --> SSIWalletStub
+    DataConsumer --> EDC
+    DataProvider --> EDC
+    DataProvider --> DTR
+    DataProvider --> SubmodelServer
+````
+
+# 4 TO-BE Design
+
+## 4.1 People
+
+### 4.1.1 Target Group Analysis
+
+Overall data space roles:
+- [Collaboration & Roles](https://catena-x.net/ecosystem/collaboration-roles/)
+- [Who: Roles in the Catena-X ecosystem](https://catenax-ev.github.io/docs/operating-model/who-roles-in-the-catena-x-ecosystem)
+
+The relevant data space roles are:
+
+- Data Consumer
+- Data Provider
+- Enablement Service Provider
+
+Scope: Umbrella HELM Charts
+
+- Enablement Services: These services are included under the umbrella of HELM charts, focusing on enabling
+  functionalities.
+
+Out of Scope: Core services such as Portal or BPDM are not considered within this scope.
+
+Primary target groups:
+
+| No. | Target group                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | Data space roles                                                    | Target group differentiation                                                                                                                                                                                                                                                                            | Behaviour, Needs, Pains & Usage                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+|-----|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| 1   | Developers<ul><li>External Developers (not Tractus-X developers): Utilize the chart for demonstration or evaluation purposes.</li><li>Experienced software and product developers who are developing a business app for a CATENA-X data space. They need to develop the app against the interfaces of the data space and integrate them accordingly.</li><li>They emphasize efficient and cost-effective implementation:<ul><li>Cost Efficiency: They do not want to use expensive SaaS solutions.</li><li>Technical Independence: They lack the knowledge and capacity to deploy the enablement and core services of the data space themselves.</li><li>Focus on Development: They concentrate on application development without delving deeply into the deployment and operation of the underlying infrastructure.</li></ul></li><li>Out of Scope: Developers running tests in test runners are not considered within this scope.</li></ul> | Data Consumer <br/> Data Provider <br/> Enablement Service Provider |                                                                                                                                                                                                                                                                                                         | <ul><li>Needs / sources of information<ul><li><a href="https://eclipse-tractusx.github.io/Kits/">Kit documentation tractus-x</a> for interaction purposes</li><li><a href="https://catenax-ev.github.io/">Catena-X documentation</a> for standards and regulations</li><li><a href="https://github.com/eclipse-tractusx/tractus-x-umbrella">Umbrella documentation</a> for umbrella component information</li></ul></li><li>Challenges → Solution<ul><li>Decentralization e.g. Where are other systems? How to interact with them? → Solution: Umbrella charts and bundles for deployment</li><li>Complex setup → Solution: delivery of small capability bundles</li></ul></li></ul> |
+| 2   | Tester requiring a test system                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | Data Consumer <br/> Data Provider <br/> Enablement Service Provider | <ul><li>Developer (1) tests their feature.</li><li>Tester (2) performs end-to-end testing.</li><li>For the tester, the modular structure is less relevant since they focus on E2E testing, whereas the developer selects the required components.</li><li>The testbed must be easy to deploy.</li></ul> | Same as above from an End-to-end testing perspective.<br/> Typically a tester has less technical know-how than a developer and therefore needs a "one-size-fits-all" (e.g.  Testbed) chart for easier testing.                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+| 3   | SMEs                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | Data Consumer <br/> Data Provider <br/> Enablement Service Provider |                                                                                                                                                                                                                                                                                                         | Need: SMEs developing a service within the Catena-X Data space want an environment to develop and test their service against without the need for expensive SaaS solutions.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+
+## 4.2 Process
+
+### 4.2.1 Use Case View (high-level)
+
+#### Group 1: Product developer
+
+| ID  | Name                                    | Actor             | Description                                                                                                        |
+|-----|-----------------------------------------|-------------------|--------------------------------------------------------------------------------------------------------------------|
+| UC1 | Configure HELM Chart                    | Product Developer | The product developer configures the HELM Chart for the specific environment.                                      |
+| UC2 | Configure Secrets                       | Product Developer | The product developer manages and configures secrets.                                                              |
+| UC3 | Execute Deployment Pipeline             | Product Developer | The product developer successfully executes the deployment pipeline for the HELM Chart.                            |
+| UC4 | Integrate EDC, DTR, and Identity Wallet | Product Developer | The actors integrate the components EDC, Digital Twin Registry, and Identity Wallet for seamless interoperability. |
+| UC5 | Set Up Connection Infrastructure        | Product Developer | The actor sets up the connection infrastructure for linking to the central data space infrastructure.              |
+| UC6 | Maintain Infrastructure Module          | Product Developer | The product developer maintains the modular architecture of the HELM Chart.                                        |
+| UC7 | Ensure Scalability                      | Product Developer | The product developer ensures scalability to support growing numbers of users and data volumes.                    |
+| UC8 | Sandbox Environments                    | Product Developer | The product developer creates local environments to evaluate and experiment with Catena-X components.              |
+
+#### Group 2: Product Tester
+
+| ID  | Name        | Actor          | Description                                                     |
+|-----|-------------|----------------|-----------------------------------------------------------------|
+| UC9 | E2E Testing | Product Tester | The product tester runs end-to-end tests for Catena-X services. |
+
+#### Group 3: Product Manager
+
+| ID   | Name                 | Actor           | Description                                                                                         |
+|------|----------------------|-----------------|-----------------------------------------------------------------------------------------------------|
+| UC10 | Dataspace Evaluation | Product Manager | The Product manager evaluates the dataspace to assess if their product can be used within Catena-X. |
+
+#### Use Case diagram
+
+````mermaid
+flowchart LR
+    PD[Product Developer]
+    PT[Product Tester]
+    PM[Product Manager]
+    UC1[Configure HELM Chart]
+    UC2[Configure Secrets]
+    UC3[Execute Deployment Pipeline]
+    UC4[Integrate EDC, DTR, and Identity Wallet]
+    UC5[Set Up Connection Infrastructure]
+    UC6[Maintain Infrastructure Module]
+    UC7[Ensure Scalability]
+    UC8[Sandbox Environments]
+    UC9[E2E Testing]
+    UC10[Dataspace Evaluation]
+    PD --> UC1
+    PD --> UC2
+    PD --> UC3
+    PD --> UC4
+    PD --> UC5
+    PD --> UC6
+    PD --> UC7
+    PD --> UC8
+    PT --> UC9
+    PM --> UC10
+````
+
+### 4.2.2 Business Process (SCC Artifact)
+
+#### Chart Release Process
+
+Charts will be released using the already existing workflow in the Umbrella Chart repository. The workflow will
+automatically release a Chart, once it is pushed to the "charts/" directory with a new Chart version.
+
+Chart versions should follow [Semantic Versioning](https://semver.org/)
+
+#### Capability Bundle Structure
+
+Capability bundle modularization for the Tractus-X Umbrella Helm chart is a sound architectural and operational design.
+It aligns with both the domain-driven architecture of Catena-X (data exchange, digital twin, identity, semantics are
+distinct domains) and with Kubernetes best practices for managing complex applications (using an umbrella chart to
+bundle related microservices).
+
+Each bundle is self-sufficient, which improves isolation (failures or changes in one domain have minimal impact on
+others) and allows scaling and upgrading along domain lines. It simplifies deployment by allowing “plug-and-play”
+capabilities: an Enablement Service Provider can decide which bundles to operate based on its role e.g., include the
+Digital Twin and Semantic bundles if offering an asset-rich service, or omit them if not. The approach is consistent
+with how other OSS projects deliver multi-component systems, providing one-step installation without sacrificing the
+ability to tweak individual parts.
+
+Why this structure was proposed:
+
+1. **Clear Separation of Concerns**  
+   Each capability bundle (e.g. EDC Data Transfer, Digital Twin, Identity & Trust, Semantic Model) aligns with a
+   specific functional domain. This separation makes it easier to understand the role of each service (e.g., the EDC
+   connector vs. the digital twin registry), reduces coupling between unrelated components, and ultimately makes
+   maintenance and troubleshooting more straightforward.
+2. **Modular Deployment**  
+   Some participants in Catena-X may not need all services (e.g., some might not use the Digital Twin bundle). By
+   structuring the umbrella chart into bundles, a user can enable just those needed capabilities. This leads to leaner
+   installs and avoids unnecessary resource usage.
+3. **Best Practices with Helm**  
+   Using an umbrella chart with subcharts/bundles is a well-recognized Helm best practice for complex applications. It
+   allows a single helm install to set up multiple microservices while still allowing each service to have its own
+   lifecycle, configuration, and version.
+4. **Alignment with Domain-Driven Approach**  
+   Catena-X is organized around distinct, loosely-coupled “building blocks.” Bundling services by domain matches this
+   architectural vision. It’s clear which domain each set of microservices belongs to (EDC for data exchange, identity
+   for credential management, etc.). This clarity also helps new adopters navigate the ecosystem.
+
+| **Capability Bundle**     | **Default Components**                               | **Comments / Possible Replacements**                                             |
+|---------------------------|------------------------------------------------------|-----------------------------------------------------------------------------------|
+| **Identity Trust Bundle** | - ssi-dim-wallet-stub                                | Can be replaced by your own Identity Wallet.                                     |
+| **EDC Bundle**            | - tractusx-connector<br/>- PostgreSQL <br/>- Vault   | Vault can be replaced if you “bring your own” vault or secrets-manager solution.  |
+| **Digital Twin Bundle**   | - Digital Twin Registry (DTR)<br/>- PostgreSQL <br/> | DB can be replaced by your own DB solution.   |
+| **Semantic Model Bundle** | - Simple Submodel Server (aka simple-data-backend)   |   |
+
+````mermaid
+%%{init: {"flowchart": {"subGraphTitleMargin": { "bottom": 10}}}}%%
+flowchart LR
+    subgraph A["Core Services"]
+        Vault["Vault"]
+    end
+
+    subgraph B["Capability Bundle: Identity & Trust"]
+        SSIWalletStub["SSI Wallet Stub"]
+    end
+
+    subgraph C["Capability Bundle: Dataspace Connector"]
+        EDC["EDC"]
+        EDCDB["EDC DB"]
+        EDC .-> EDCDB
+    end
+
+    subgraph "Capability Bundle: Digital Twin"
+        DTR["DTR"]
+        DTRDB["DTR DB"]
+        DTR .-> DTRDB
+    end
+
+    subgraph "Capability Bundle: Data Persistence Layer"
+        SimpleSubmodelServer["Simple Submodel Server"]
+    end
+
+    subgraph "Hausanschluss Actors"
+        subgraph "Data Provider"
+            DataProvider["Data Provider"]
+        end
+        subgraph "Data Consumer"
+            DataConsumer["Data Consumer"]
+        end
+        subgraph "Enablement Provider"
+            EnablementProvider["Enablement Provider"]
+        end
+    end
+
+    EDC -..-> SSIWalletStub
+    EDC -..-> Vault
+    DataProvider --> EDC
+    DataProvider --> DTR
+    DataProvider --> SimpleSubmodelServer
+    DataConsumer --> EDC
+    EnablementProvider --> DataConsumer
+    EnablementProvider --> DataProvider
+````
+
+#### Deployment strategies
+
+##### Role: Data Provider
+
+The standard data provider role consists of an EDC, DTR and Submodel Server Bundles. EDC uses the Identity Wallet Bundle.
+
+````mermaid
+flowchart BT
+    A["Capability Bundle: Identity & Trust"]
+    B["Capability Bundle: Data Persistence Layer"]
+    C["Capability Bundle: Dataspace Connector"]
+    D["Capability Bundle: Digital Twin"]
+    E("Application to be tested/developed")
+    style E fill:#afafaf,color:black
+    F{{"Developer/Tester"}}
+    E --> B
+    E --> C
+    E --> D
+    C --> A
+    F --> E
+````
+
+##### Role: Data Consumer
+
+The standard data consumer role consists of only the EDC Bundle and the Identity Wallet Bundle.
+
+````mermaid
+flowchart BT
+    A["Capability Bundle: Identity & Trust"]
+    B["Capability Bundle: Dataspace Connector"]
+    C("Application to be tested/developed")
+    style C fill:#afafaf,color:black
+    D{{"Developer/Tester"}}
+    C --> B
+    B --> A
+    D --> C
+````
+
+##### Role: Enablement Provider
+
+The Enablement Provider role consists of both the Data Consumer and Data Provider bundles. This allows provisioning of
+data and the consumption of the provisioned data by a application.
+
+````mermaid
+flowchart BT
+    A["Capability Bundle: Identity & Trust"]
+    B["Capability Bundle: Data Persistence Layer"]
+    C("Application to be tested/developed")
+    style C fill:#afafaf,color:black
+    D["Capability Bundle: Digital Twin"]
+    E["Capability Bundle: Dataspace Connector (Provider)"]
+    F["Capability Bundle: Dataspace Connector (Consumer)"]
+    G{{"Developer/Tester"}}
+    C --> B
+    C --> D
+    C --> E
+    C --> F
+    E --> A
+    F --> A
+    G --> C
+````
+
+#### Bring your own
+
+Each Bundle can be deactivated to use your own component. This requires configuration of the component specific
+parameters in the other components.
+
+In this example this would be the configuration of the Identity Wallet within the EDC.
+
+````mermaid
+flowchart BT
+    A("Application to be tested/developed")
+    style A fill:#afafaf,color:black
+    B["Capability Bundle: Dataspace Connector"]
+    C["
Capability Bundle: Identity & Trust
"]
+    D["Own Identity Wallet"]
+    E{{"Developer/Tester"}}
+    A --> B
+    B -- identitywallet - bundle . enabled = false --> C
+    B -- configure --> D
+    E --> A
+````
+
+Using a "bring-your-own" component requires additional configuration. In this case, the identity wallet has to be configured in the EDC configuration section.
+
+Replacing existing Charts with your own solution is not limited to the direct components of the Capability Bundles.  
+This also applies to the dependencies of the bundles which e.g. allows the user to choose another way of provisioning a database.
+
+Components which can be replaced are:
+
+- Capability Bundle: Dataspace Connector
+    - postgresql
+    - vault
+- Capability Bundle: Digital Twin
+    - postgresql
+    - keycloak
+- Capability Bundle: Identity & Trust
+    - ssi-dim-wallet-stub
+- Capability Bundle: Data Persistence Layer
+    - simple-data-backend
+
+To make configuration of "bring-your-own" components easier, the bundle config has to highlight which values are 
+related to which dependency and what to change, if the components should be replaced:
+
+```yaml
+digital-twin-registry:
+  registry:
+    dataSource:
+      # replace this when using your own database
+      # url: 
+      # user: 
+      # password: 
+```
+
+#### Scalability
+
+It is essential that the deployment of each bundle is entirely independent, allowing the same bundle to be deployed multiple times.
+Every instance must maintain its own unique set of Kubernetes resources, ensuring there is no overlap or shared dependencies between different deployments.
+
+#### Interoperability
+
+To ensure interoperability, the [Tractus-X Release Guidelines](https://eclipse-tractusx.github.io/docs/release/) are followed and [Catena-X standards](https://catenax-ev.github.io/docs/standards/overview) are understood and applied.  
+Additionally, the existing functionality of the Umbrella Chart must be kept and verified to work.
+
+## 4.4 System
+
+### 4.4.1 Context Delimitation / 4.4.2 Interface Documentation
+
+Interactions between an Application acting as Dataprovider or Dataconsumer and the Services which are part of the different Capability Bundles.
+
+````mermaid
+flowchart LR
+    Dataprovider["Dataprovider"] -->|stores data| SubmodelServer["Submodel Server"]
+    Dataprovider -->|creates twins| DTR["DTR"]
+    Dataprovider -->|creates contracts| EDC["EDC"]
+    EDC["EDC"] -->|needs| EdcPosgtres["PostgreSQL Database"]
+    Dataconsumer["Dataconsumer"] -->|negotiate contracts| EDC
+    DTR -->|needs| DtrPostgres["PostgreSQL Database"]
+    EDC["EDC"] -->|needs| IdentityWallet["Identity Wallet"]
+````
+
+# 5 Build
+
+## 5.1 DevOps Setup Definition
+
+### 5.1.1 Tool Chain Definition
+
+##### Version Control & Source Code Management
+
+- **Git & GitHub**: Management of the source code, the Helm Charts, and associated documentation in a centralized
+  repository.
+
+##### Build and CI/CD Tools
+
+- **GitHub Actions**: Automated workflows for linting, testing, packaging, and releasing the Helm Charts.
+- **Helm CLI**: For validating, packaging, and deploying the charts.
+- **Helm Lint**: Performing static analyses to ensure compliance with chart standards.
+
+##### Testing and Validation Tools
+
+- **Chart-testing Tool**: Validation of the Helm Charts based on Kubernetes schemas.
+- **Local Cluster Tests**: Use of tools such as Kind or Minikube to perform integration tests in a test environment.
+
+##### Release Management & Deployment
+
+- **Chart Releaser**: Automated creation and publication of chart releases.
+- **Helm Chart Repository / GitHub Packages**: Hosting and provisioning of the finalized charts.
+
+# NOTICE
+
+This work is licensed under the [CC-BY-4.0](https://creativecommons.org/licenses/by/4.0/legalcode).
+
+* SPDX-License-Identifier: CC-BY-4.0
+* SPDX-FileCopyrightText: 2025 Contributors to the Eclipse Foundation
+* Source URL: <https://github.com/eclipse-tractusx/tractus-x-umbrella>
\ No newline at end of file


Reviews:
user: login: mkanal
state: CHANGES_REQUESTED
author_association: CONTRIBUTOR
submitted_at: 2025-03-28T12:24:04Z
user: login: mkanal
state: CHANGES_REQUESTED
author_association: CONTRIBUTOR
submitted_at: 2025-03-28T12:30:39Z
user: login: mkanal
state: CHANGES_REQUESTED
author_association: CONTRIBUTOR
submitted_at: 2025-03-28T12:37:26Z
user: login: ds-jhartmann
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-03-28T12:50:35Z
user: login: ds-jhartmann
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-03-28T12:51:37Z
user: login: ds-jhartmann
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-03-28T12:52:26Z
user: login: ds-jhartmann
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-03-28T12:53:31Z
user: login: ds-jhartmann
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-03-28T12:55:53Z
user: login: ds-jhartmann
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-03-28T12:58:45Z
user: login: mkanal
state: CHANGES_REQUESTED
author_association: CONTRIBUTOR
submitted_at: 2025-03-28T13:42:41Z
user: login: ds-jhartmann
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-03-31T07:31:16Z
user: login: ds-jhartmann
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-03-31T07:32:10Z
user: login: ds-jhartmann
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-03-31T08:00:14Z
user: login: ds-jhartmann
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-03-31T08:00:16Z
user: login: ds-jhartmann
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-03-31T08:50:43Z
user: login: ds-jhartmann
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-03-31T08:51:57Z
user: login: ds-jhartmann
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-03-31T09:39:33Z
user: login: ds-jhartmann
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-03-31T12:17:05Z
user: login: ds-jhartmann
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-03-31T12:17:20Z
user: login: ds-jhartmann
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-03-31T12:17:36Z
user: login: ds-jhartmann
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-03-31T12:21:03Z
user: login: mkanal
body: LGFM
state: APPROVED
author_association: CONTRIBUTOR
submitted_at: 2025-04-01T05:50:46Z
user: login: mgarciaLKS
body: The PR is incredible, extensive and a great contribution. I have proposed some minor changes. :rocket: :+1: 
state: CHANGES_REQUESTED
author_association: CONTRIBUTOR
submitted_at: 2025-04-03T10:19:59Z
user: login: CDiezRodriguez
body: Looks amazing! I've added some comments that I believe will improve readability.
state: CHANGES_REQUESTED
author_association: CONTRIBUTOR
submitted_at: 2025-04-03T10:20:35Z
user: login: mgarciaLKS
body: LGTM :rocket: 
state: APPROVED
author_association: CONTRIBUTOR
submitted_at: 2025-04-03T10:41:42Z
user: login: ds-jhartmann
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-04-03T12:10:12Z
user: login: ds-jhartmann
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-04-03T12:10:42Z
user: login: ds-jhartmann
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-04-03T12:11:01Z
user: login: CDiezRodriguez
body: LGTM
state: APPROVED
author_association: CONTRIBUTOR
submitted_at: 2025-04-03T13:15:12Z
user: login: evegufy
body: LGTM in general
state: CHANGES_REQUESTED
author_association: CONTRIBUTOR
submitted_at: 2025-04-07T08:03:13Z
user: login: evegufy
state: APPROVED
author_association: CONTRIBUTOR
submitted_at: 2025-04-07T09:47:00Z
user: login: evegufy
body: Please **squash** when merging
state: APPROVED
author_association: CONTRIBUTOR
submitted_at: 2025-04-08T13:00:28Z

Review comments:
diff_hunk: @@ -0,0 +1,425 @@
+# [TAP 7.1] Solution Design Hausanschluss Bundle Konzept
path: docs/concept/TAP7.1-solution-design.md
user: login: mkanal
body: @ds-jhartmann 
unique naming EDC "Hausanschluss" Bundle or Hausanschluss Bundle (in the whole doument)
created_at: 2025-03-28T12:14:45Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,425 @@
+# [TAP 7.1] Solution Design Hausanschluss Bundle Konzept
+
+# 1 Business Case
+
+## 1.1 Executive Summary
+
+The EDC "Hausanschluss" Bundle aims to simplify the installation of the enablement services Eclipse Dataspace
path: docs/concept/TAP7.1-solution-design.md
user: login: mkanal
body: \n\r seems not to be correct? 
created_at: 2025-03-28T12:15:34Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,425 @@
+# [TAP 7.1] Solution Design Hausanschluss Bundle Konzept
+
+# 1 Business Case
+
+## 1.1 Executive Summary
+
+The EDC "Hausanschluss" Bundle aims to simplify the installation of the enablement services Eclipse Dataspace
+Connector (EDC), Digital Twin Registry (DTR), and their supporting components. By developing a flexible, parameterizable
+installation package, the project seeks to reduce deployment complexity and lower barriers to participation in the
+Catena‑X data space. This bundle will enable independent component updates and support a modular "bring your own"
+approach, ultimately fostering a more efficient and accessible ecosystem for diverse participants—such as testers,
+external developers, and small and medium-sized enterprises.
path: docs/concept/TAP7.1-solution-design.md
user: login: mkanal
body: product 
```suggestion
external product developers, product testers, and small and medium-sized enterprises.
```
created_at: 2025-03-28T12:16:38Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,425 @@
+# [TAP 7.1] Solution Design Hausanschluss Bundle Konzept
+
+# 1 Business Case
+
+## 1.1 Executive Summary
+
+The EDC "Hausanschluss" Bundle aims to simplify the installation of the enablement services Eclipse Dataspace
+Connector (EDC), Digital Twin Registry (DTR), and their supporting components. By developing a flexible, parameterizable
+installation package, the project seeks to reduce deployment complexity and lower barriers to participation in the
+Catena‑X data space. This bundle will enable independent component updates and support a modular "bring your own"
+approach, ultimately fostering a more efficient and accessible ecosystem for diverse participants—such as testers,
+external developers, and small and medium-sized enterprises.
+
+## 1.2 Business Need
+
+Current deployment methods for data space integration are complex and require significant manual effort. This PoC
+addresses the need to:
+
+- Reduce Complexity: Simplify the deployment topology by bundling components into capabilities.
+- Automate Deployment: Provide an automated installation package using Kubernetes and HELM.
+- Reduce Configuration Efforts: Streamline and reduce the number of configuration steps required for integration.
path: docs/concept/TAP7.1-solution-design.md
user: login: mkanal
body: could you please quantify the reduction in a qualitative apporach
created_at: 2025-03-28T12:17:27Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,425 @@
+# [TAP 7.1] Solution Design Hausanschluss Bundle Konzept
+
+# 1 Business Case
+
+## 1.1 Executive Summary
+
+The EDC "Hausanschluss" Bundle aims to simplify the installation of the enablement services Eclipse Dataspace
+Connector (EDC), Digital Twin Registry (DTR), and their supporting components. By developing a flexible, parameterizable
+installation package, the project seeks to reduce deployment complexity and lower barriers to participation in the
+Catena‑X data space. This bundle will enable independent component updates and support a modular "bring your own"
+approach, ultimately fostering a more efficient and accessible ecosystem for diverse participants—such as testers,
+external developers, and small and medium-sized enterprises.
+
+## 1.2 Business Need
+
+Current deployment methods for data space integration are complex and require significant manual effort. This PoC
+addresses the need to:
+
+- Reduce Complexity: Simplify the deployment topology by bundling components into capabilities.
+- Automate Deployment: Provide an automated installation package using Kubernetes and HELM.
+- Reduce Configuration Efforts: Streamline and reduce the number of configuration steps required for integration.
+- Extend Documentation: Provide a detailed documentation tailored to the target groups.
+- Enable Extension: Design the system to allow the seamless addition of new components or capabilities.
+
+## 1.3 Objectives
+
+- Simplify Deployment and Maintenance: Develop an installation package that minimizes manual configuration through
+  automation.
+- Ensure Modularity: Structure the bundle so that components can be independently installed, updated, or replaced
+  without
+  affecting other services.
+- Facilitate Flexibility: Implement a "bring your own" model for key components, such as EDC, PostgreSQL, and HashiCorp
path: docs/concept/TAP7.1-solution-design.md
user: login: mkanal
body: ```suggestion
- Facilitate Flexibility: Implement a "bring your own" model for key components, such as EDC, PostgreSQL, and HashiCorp Vault
```
created_at: 2025-03-28T12:18:11Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,425 @@
+# [TAP 7.1] Solution Design Hausanschluss Bundle Konzept
+
+# 1 Business Case
+
+## 1.1 Executive Summary
+
+The EDC "Hausanschluss" Bundle aims to simplify the installation of the enablement services Eclipse Dataspace
+Connector (EDC), Digital Twin Registry (DTR), and their supporting components. By developing a flexible, parameterizable
+installation package, the project seeks to reduce deployment complexity and lower barriers to participation in the
+Catena‑X data space. This bundle will enable independent component updates and support a modular "bring your own"
+approach, ultimately fostering a more efficient and accessible ecosystem for diverse participants—such as testers,
+external developers, and small and medium-sized enterprises.
+
+## 1.2 Business Need
+
+Current deployment methods for data space integration are complex and require significant manual effort. This PoC
+addresses the need to:
+
+- Reduce Complexity: Simplify the deployment topology by bundling components into capabilities.
+- Automate Deployment: Provide an automated installation package using Kubernetes and HELM.
+- Reduce Configuration Efforts: Streamline and reduce the number of configuration steps required for integration.
+- Extend Documentation: Provide a detailed documentation tailored to the target groups.
+- Enable Extension: Design the system to allow the seamless addition of new components or capabilities.
+
+## 1.3 Objectives
+
+- Simplify Deployment and Maintenance: Develop an installation package that minimizes manual configuration through
+  automation.
+- Ensure Modularity: Structure the bundle so that components can be independently installed, updated, or replaced
+  without
+  affecting other services.
+- Facilitate Flexibility: Implement a "bring your own" model for key components, such as EDC, PostgreSQL, and HashiCorp
path: docs/concept/TAP7.1-solution-design.md
user: login: mkanal
body: Are we convinced to deliver a Vault integration? 
created_at: 2025-03-28T12:18:29Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,425 @@
+# [TAP 7.1] Solution Design Hausanschluss Bundle Konzept
+
+# 1 Business Case
+
+## 1.1 Executive Summary
+
+The EDC "Hausanschluss" Bundle aims to simplify the installation of the enablement services Eclipse Dataspace
+Connector (EDC), Digital Twin Registry (DTR), and their supporting components. By developing a flexible, parameterizable
+installation package, the project seeks to reduce deployment complexity and lower barriers to participation in the
+Catena‑X data space. This bundle will enable independent component updates and support a modular "bring your own"
+approach, ultimately fostering a more efficient and accessible ecosystem for diverse participants—such as testers,
+external developers, and small and medium-sized enterprises.
+
+## 1.2 Business Need
+
+Current deployment methods for data space integration are complex and require significant manual effort. This PoC
+addresses the need to:
+
+- Reduce Complexity: Simplify the deployment topology by bundling components into capabilities.
+- Automate Deployment: Provide an automated installation package using Kubernetes and HELM.
+- Reduce Configuration Efforts: Streamline and reduce the number of configuration steps required for integration.
+- Extend Documentation: Provide a detailed documentation tailored to the target groups.
+- Enable Extension: Design the system to allow the seamless addition of new components or capabilities.
+
+## 1.3 Objectives
+
+- Simplify Deployment and Maintenance: Develop an installation package that minimizes manual configuration through
path: docs/concept/TAP7.1-solution-design.md
user: login: mkanal
body: Are all these objectives covered in the concept? 
created_at: 2025-03-28T12:19:07Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,425 @@
+# [TAP 7.1] Solution Design Hausanschluss Bundle Konzept
+
+# 1 Business Case
+
+## 1.1 Executive Summary
+
+The EDC "Hausanschluss" Bundle aims to simplify the installation of the enablement services Eclipse Dataspace
+Connector (EDC), Digital Twin Registry (DTR), and their supporting components. By developing a flexible, parameterizable
+installation package, the project seeks to reduce deployment complexity and lower barriers to participation in the
+Catena‑X data space. This bundle will enable independent component updates and support a modular "bring your own"
+approach, ultimately fostering a more efficient and accessible ecosystem for diverse participants—such as testers,
+external developers, and small and medium-sized enterprises.
+
+## 1.2 Business Need
+
+Current deployment methods for data space integration are complex and require significant manual effort. This PoC
+addresses the need to:
+
+- Reduce Complexity: Simplify the deployment topology by bundling components into capabilities.
+- Automate Deployment: Provide an automated installation package using Kubernetes and HELM.
+- Reduce Configuration Efforts: Streamline and reduce the number of configuration steps required for integration.
+- Extend Documentation: Provide a detailed documentation tailored to the target groups.
+- Enable Extension: Design the system to allow the seamless addition of new components or capabilities.
+
+## 1.3 Objectives
+
+- Simplify Deployment and Maintenance: Develop an installation package that minimizes manual configuration through
+  automation.
+- Ensure Modularity: Structure the bundle so that components can be independently installed, updated, or replaced
+  without
+  affecting other services.
+- Facilitate Flexibility: Implement a "bring your own" model for key components, such as EDC, PostgreSQL, and HashiCorp
+  Vault, to allow tailored deployments that meet specific needs.
+- Increase Accessibility: Lower entry barriers for new participants by reducing technical complexity and operational
+  dependencies.
+- Scalability: Structure the bundle so that it can be deployed multiple times.
+
+## 1.4 Expected Deliverables
+
+- PoC Documentation: A concept and architecture overview highlighting the modular design.
+- Modular Installation Package: A set of HELM charts for deploying the enablement service bundles:
+    - EDC Bundle: Including the Eclipse Dataspace Connector, EDC PostgreSQL, and HashiCorp Vault.
+    - Digital Twin Bundle: Featuring components such as the Decentral DT Registry (with “bring your own” PostgreSQL) and
+      a Submodel Server Bundle.
+    - Identity Wallet Bundle: Covering the Identity Wallet functionality.
+- Demonstration Environment: A test deployment showcasing reduced complexity and improved efficiency.
+- Basic User Guide: Instructions on how to deploy and update the PoC bundle.
+
+## 1.5 Benefits
+
+- Operational Efficiency: Faster and more reliable deployments with less manual work.
+- Scalability: A modular design that can be scaled or adapted for future full-scale deployments.
+- Ease of Adoption: Simplified deployment processes make it easier for testers and external developers to engage.
+
+## 1.6. Dependencies
+
+- Interoperability with the CATENA‑X standards.
+
+## 1.7. Success Criteria
+
+- Technology Readiness Level: Achievement of a Technology Readiness Level (TRL) of 3, as specified in the requirements.
+- Functional PoC Deployment: Demonstrated automated, modular installation with reduced manual steps.
+- Simplified Configuration: Clear evidence of reduced configuration complexity.
+- Positive Feedback: End-user validation from a select group of demo participants and the Tractus-X community.
+- Documentation Completeness: Availability of concise deployment and user guides.
+
+## 1.8. Out of Scope
+
+- Full Production Readiness: This PoC is not intended to be a production-ready solution.
+- Core Services Exclusion: Core services are not part of the Hausanschluss Bundles.
+- App Provider Role: The role of App Provider is considered out of scope for this deployment.
+- Alternative Deployment Techniques: While the evaluation of alternative deployment methods is acknowledged, the primary
+  focus remains on Kubernetes and HELM-based deployment.
+
+# 2 Requirements Analysis
+
+## 2.1 Assumptions
+
+## 2.2 Requirements Catalog
+
+| ID             | Requirement                                                                                                                                                                                                                                                                                                                                               | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | Deliverables / Acceptance Criteria                                                                                                           |
+|----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------|
+| [WP-7.1.-D001] | TAP7.1 Hausanschluss Bundle aims to simplify the installation and maintenance of the EDC and other components that together ensure a “home connection”. A flexible, parameterizable installation package is intended to reduce complexity and make integration more efficient, thereby simplifying participation in Catena‑X for additional participants. | Specification and development of a flexible, parameterizable installation package that reduces the complexity of installing and maintaining the required components for seamless integration into the Catena‑X data space. This package should facilitate updates and new versions, making participation in Catena‑X more efficient and accessible. In doing so, SMEs shall be enabled to participate without high costs or dependency on SaaS providers while maintaining control over their IT infrastructure. | [WP-7.1.-D001] Concept for the Hausanschluss is created                                                                                      |
+| 7.1.1.1        | The solution concept must define the Capability Bundles structures to be implemented. For each Capability Bundle, the included bundles and their versions are mapped.                                                                                                                                                                                     | "The following Capability Bundle structure is implemented:                                                                                                                                                                                                                                                                                                                                                                                                                                                       | "The structure of the Capability Bundles for the Enablement Services has been specified.                                                     |
+| 7.1.1.2        | Definition of Data Space Roles                                                                                                                                                                                                                                                                                                                            | Capability EDC (Data Transfer) Bundle                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | For version R24.12 it is clearly defined which Tractus‑X services and components are assigned to each Capability Bundle"                     |
+| 7.1.1.4        | Modularity & Maintainability: No dependencies between Capability Bundles                                                                                                                                                                                                                                                                                  | Eclipse Dataspace Connector (EDC) v0.9.0                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | "As part of the target group analysis, the target groups are defined and aligned with the data space roles.                                  |
+| 7.1.1.5        | Modularity & Maintainability: Concept for reducing deployment complexity                                                                                                                                                                                                                                                                                  | EDC PostgresSQL                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | Mapping from data space role to target group has been completed.                                                                             |
+| 7.1.1.6        | Modularity & Maintainability                                                                                                                                                                                                                                                                                                                              | HashiCorp Vault                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | Mapping from target group to data space role has been completed.                                                                             |
+| 7.1.1.13       | Solution Concept                                                                                                                                                                                                                                                                                                                                          | Capability Digital Twin Bundle                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | An assignment of data space roles to Capability Bundles has been made."                                                                      |
+| 7.1.1.14       | Scalability of Enablement Services                                                                                                                                                                                                                                                                                                                        | Decentral DT Registry                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | "Components and Services should obly be part of one bundle.                                                                                  |
+| 7.1.1.16       | Interoperability                                                                                                                                                                                                                                                                                                                                          | PostgresSQL                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | Each bundle must be deployable in isolation and can be installed, updated, or removed independently.                                         |
+| [WP-7.1.-D002] | [WP-7.1.-D002] Target group for the specification is defined.                                                                                                                                                                                                                                                                                             | Capability Identity & Trust (Identity Wallet Bundle)                                                                                                                                                                                                                                                                                                                                                                                                                                                             | Capability Bundles must be organized in separate HELM sub‑charts.                                                                            |
+| 7.1.2.1        | Target Group Analysis                                                                                                                                                                                                                                                                                                                                     | Identity Wallet Mock                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | Circular dependencies between bundles must be avoided."                                                                                      |
+| [WP-7.1.-D003] | [WP-7.1.-D003] Decentralized components and services defined                                                                                                                                                                                                                                                                                              | Capability Semantic Model Bundle                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | "Simplification of deployment processes                                                                                                      |
+| 7.1.3.1        | See [WP-7.1.-D001-AC001]                                                                                                                                                                                                                                                                                                                                  | Submodel Mock (aus Umbrella HELM Chart)"                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | A reduction of manual configuration steps has been achieved.                                                                                 |
+| [WP-7.1.-D004] | [WP-7.1.-D004] Documentation of the Hausanschluss Bundle is completed                                                                                                                                                                                                                                                                                     | "Data Consumer                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | Transparency and traceability                                                                                                                |
+| 7.1.4.1        | Documentation of the Hausanschluss-Bundles                                                                                                                                                                                                                                                                                                                | Data Provider                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | Clearly documented deployment steps are provided.                                                                                            |
+| 7.1.4.2        | Documentation of the Hausanschluss-Bundles                                                                                                                                                                                                                                                                                                                | Enablement Service Provider"                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | Improvements of Chart configuration by                                                                                                       |
+| [WP-7.1.-D005] | [WP-7.1.-D005] Umbrella HELM Charts for the Hausanschluss developed, tested, and documented                                                                                                                                                                                                                                                               | "Unique assignment of components and services to a defined Capability Bundle.                                                                                                                                                                                                                                                                                                                                                                                                                                    | usage of template                                                                                                                            |
+| 7.1.5.1        | Re-activate Umbrella HELM Charts to the latest release state                                                                                                                                                                                                                                                                                              | Each component and service should be assigned to only one Capability Bundle.                                                                                                                                                                                                                                                                                                                                                                                                                                     | reducing configuration options                                                                                                               |
+| 7.1.5.2        | Hierarchical structuring and bundling of Enablement Service components in the Umbrella HELM Chart                                                                                                                                                                                                                                                         | Dependencies between Capability Bundles are allowed."                                                                                                                                                                                                                                                                                                                                                                                                                                                            | reducing manual steps in the setup"                                                                                                          |
+| 7.1.5.3        | Interchangeability of bundle components via “Bring-Your-Own” components                                                                                                                                                                                                                                                                                   | The system deployment should be optimized to reduce the existing complexity. The goal is to make the provisioning process more efficient, robust, and easier to maintain.                                                                                                                                                                                                                                                                                                                                        | Charts are published via a publicly accessible charts repository.                                                                            |
+| [WP-7.1.-D006] | [WP-7.1.-D006] Product developed according to a Technology Readiness Level (TRL) of 3                                                                                                                                                                                                                                                                     | Charts are published automatically.                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | "The solution design for the ""Hausanschluss"" Bundle is created.                                                                            |
+| 7.1.6.1        | POC                                                                                                                                                                                                                                                                                                                                                       | Creation of a solution design for the “Hausanschluss” Bundle.                                                                                                                                                                                                                                                                                                                                                                                                                                                    | The solution design for the ""Hausanschluss"" Bundle ispublished in the repository: https://github.com/eclipse-tractusx/tractus-x-umbrella." |
+| 7.1.6.2        | Deployment Strategy                                                                                                                                                                                                                                                                                                                                       | Scalability of Enablement Services                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | "Developers should be able to deploy an arbitrary number of Enablement Services.                                                             |
+
+# 3 AS-IS Analysis
+
+## 3.1 People
+
+### 3.1.1 Target Group Analysis
+
+See "4.1.1 To-be Target Group Analysis" below. No deviations between As-is and To-be target groups have been identified.
+
+## 3.2 Process
+
+### 3.2.1 Use Case View (high-level)
+
+Umbrella Chart is intended for the following Use Cases:
+
+| Actor             | Use case                                                                                             |
+|-------------------|------------------------------------------------------------------------------------------------------|
+| Product Developer | Sandbox Environments: Create local environments to evaluate and experiment with Catena-X components. |
+| Product Developer | Development: Provide a unified setup for contributors and developers working on Tractus-X projects.  |
+| Product Tester    | Testing: Run end-to-end tests for Catena-X services.                                                 |
+
+## 3.4 System
+
+### 3.4.1 Context Delimitation
+
+````mermaid
+flowchart
+    subgraph "Umbrella Chart"
+        ChartYaml["Chart.yaml"]
+        subgraph charts
+            Portal["Portal"]
+            CentralIdp["CentralIdp"]
+            DiscoveryFinder["Discovery Finder"]
+            SDFactory["SD-Factory"]
+            SSICredentialIssuer["SSI Credential Issuer"]
+            SemanticHub["Semantic Hub"]
+            BPDM["BPDM"]
+            DataConsumer["Data Consumer"]
+            DataProvider["Data Provider"]
+            BDRS["BDRS"]
+            SSIWalletStub["SSI Wallet Stub"]
+        end
+        subgraph "tx-data-provider"
+            EDC["EDC"]
+            DTR["DTR"]
+            SubmodelServer["Submodel Server"]
+        end
+    end
+
+    ChartYaml --> Portal
+    ChartYaml --> CentralIdp
+    ChartYaml --> DiscoveryFinder
+    ChartYaml --> SDFactory
+    ChartYaml --> SSICredentialIssuer
+    ChartYaml --> SemanticHub
+    ChartYaml --> BPDM
+    ChartYaml --> DataConsumer
+    ChartYaml --> DataProvider
+    ChartYaml --> BDRS
+    ChartYaml --> SSIWalletStub
+    DataConsumer --> EDC
+    DataProvider --> EDC
+    DataProvider --> DTR
+    DataProvider --> SubmodelServer
+````
+
+#### Existing Umbrella Chart Structure
+
+# 4 TO-BE Design
+
+## 4.1 People
+
+### 4.1.1 Target Group Analysis
+
+Overall data space roles: https://catena-x.net/en/1/catena-x-introduce-implement/how-to-operate-catena-x
+
+The relevant data space roles for us under requirement 7.1.1.1 are:
+
+- Data Consumer
+- Data Provider
+- Enablement Service Provider
+
+Scope: Umbrella HELM Charts
+
+- Enablement Services: These services are included under the umbrella of HELM charts, focusing on enabling
+  functionalities.
+- Out of Scope: Core services such as Portal or BPDM are not considered within this scope.
+
+Primary target groups:
+
+| No. | Target group                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | Data space roles                                                    | Target group differentiation                                                                                                                                                                                                                                                                            | Behaviour, Needs, Pains & Usage                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+|-----|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| 1   | Developers<ul><li>External Developers (not Tractus-X developers): Utilize the chart for demonstration or evaluation purposes.</li><li>Experienced software and product developers who are developing a business app for a CATENA-X data space. They need to develop the app against the interfaces of the data space and integrate them accordingly.</li><li>They emphasize efficient and cost-effective implementation:<ul><li>Cost Efficiency: They do not want to use expensive SaaS solutions.</li><li>Technical Independence: They lack the knowledge and capacity to deploy the enablement and core services of the data space themselves.</li><li>Focus on Development: They concentrate on application development without delving deeply into the deployment and operation of the underlying infrastructure.</li></ul></li><li>Out of Scope: Developers running tests in test runners are not considered within this scope.</li></ul> | Data Consumer <br/> Data Provider <br/> Enablement Service Provider |                                                                                                                                                                                                                                                                                                         | <ul><li>Needs / sources of information<ul><li><a href="https://eclipse-tractusx.github.io/Kits/">Kit documentation tractus-x</a> for interaction purposes</li><li><a href="https://catenax-ev.github.io/">Catena-X doucmentation</a> for standards and regulations</li><li><a href="https://github.com/eclipse-tractusx/tractus-x-umbrella">Umbrella documentation</a> for umbrella component information</li></ul></li><li>Challenges → Solution<ul><li>Decentralization e.g. Where are other systems? How to interact with them? → Solution: Umbrella charts and bundles for deployment</li><li>Complex setup → Solution: delivery of small capability bundles</li></ul></li></ul> |
+| 2   | <ul><li>Tester requiring a test system (Testmanagement e.V.)</li><li>Requirement: Testbed</li></ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | Data Consumer <br/> Data Provider <br/> Enablement Service Provider | <ul><li>Developer (1) tests their feature.</li><li>Tester (2) performs end-to-end testing.</li><li>For the tester, the modular structure is less relevant since they focus on E2E testing, whereas the developer selects the required components.</li><li>The testbed must be easy to deploy.</li></ul> | <ul><li>Same as above from an End-to-end testing perspective</li><li>Typically a tester has less technical know-how than a developer and therefore needs a "one-size-fits-all" chart for easier testing</li></ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+
+## 4.2 Process
+
+### 4.2.1 Use Case View (high-level)
+
+| Use Case                                | Description                                                                                                       | Actors            |
+|-----------------------------------------|-------------------------------------------------------------------------------------------------------------------|-------------------|
+| Configure HELM Chart                    | The product developer configures the HELM Chart for the specific environment.                                     | Product Developer |
+| Configure Secrets                       | The product developer manages and configures secrets.                                                             | Product Developer |
+| Execute Deployment Pipeline             | The product developer successfully executes the deployment pipeline for the HELM Chart.                           | Product Developer |
+| Integrate EDC, DTR, and Identity Wallet | The actors integrate the components EDC, Digital Twin Registry, and Identity Wallet for seamless interoperability | Product Developer |
+| Set Up Connection Infrastructure        | The actor sets up the connection infrastructure for linking to the central data space infrastructure.             | Product Developer |
+| Maintain Infrastructure Module          | The product developer maintains the modular architecture of the HELM Chart.                                       | Product Developer |
+| Ensure Scalability                      | The product developer ensures scalability to support growing numbers of users and data volumes.                   | Product Developer |
+| Sandbox Environments                    | The product developer creates local environments to evaluate and experiment with Catena-X components.             | Product Developer |
+| E2E Testing                             | The product tester runs end-to-end tests for Catena-X services.                                                   | Product Tester    |
+
+### 4.2.2 Business Process (SCC Artifact)
+
+#### Chart Release Process
+
+Charts will be released using the already existing workflow in the Umbrella Chart repository. The workflow will
+automatically release a Chart, once it is pushed to the "charts/" directory with a new Chart version.
+
+#### Capability Bundle Structure
+
+Capability bundle modularization for the Tractus-X Umbrella Helm chart is a sound architectural and operational design.
+It aligns with both the domain-driven architecture of Catena-X (data exchange, digital twin, identity, semantics are
+distinct domains) and with Kubernetes best practices for managing complex applications (using an umbrella chart to
+bundle related microservices).
+
+Each bundle is self-sufficient, which improves isolation (failures or changes in one domain have minimal impact on
+others) and allows scaling and upgrading along domain lines. It simplifies deployment by allowing “plug-and-play”
+capabilities: an Enablement Service Provider can decide which bundles to operate based on its role e.g., include the
+Digital Twin and Semantic bundles if offering an asset-rich service, or omit them if not. The approach is consistent
+with how other OSS projects deliver multi-component systems, providing one-step installation without sacrificing the
+ability to tweak individual parts.
+
+Why this structure was proposed:
+
+1. **Clear Separation of Concerns**  
+   Each capability bundle (e.g. EDC Data Transfer, Digital Twin, Identity & Trust, Semantic Model) aligns with a
+   specific functional domain. This separation makes it easier to understand the role of each service (e.g., the EDC
+   connector vs. the digital twin registry), reduces coupling between unrelated components, and ultimately makes
+   maintenance and troubleshooting more straightforward.
+2. **Modular Deployment**  
+   Some participants in Catena-X may not need all services (e.g., some might not use the Digital Twin bundle). By
+   structuring the umbrella chart into bundles, a user can enable just those needed capabilities. This leads to leaner
+   installs and avoids unnecessary resource usage.
+3. **Best Practices with Helm**  
+   Using an umbrella chart with subcharts/bundles is a well-recognized Helm best practice for complex applications. It
+   allows a single helm install to set up multiple microservices while still allowing each service to have its own
+   lifecycle, configuration, and version.
+4. **Alignment with Domain-Driven Approach**  
+   Catena-X is organized around distinct, loosely-coupled “building blocks.” Bundling services by domain matches this
+   architectural vision. It’s clear which domain each set of microservices belongs to (EDC for data exchange, identity
+   for credential management, etc.). This clarity also helps new adopters navigate the ecosystem.
+
+````mermaid
+flowchart LR
+    subgraph "Core Services"
+        Vault["Vault"]
+    end
+
+    subgraph "Capability Bundle: Identity & Trust"
+        SSIWalletStub["SSI Wallet Stub"]
+    end
+
+    subgraph "Capability Bundle: Dataspace Connector"
+        EDC["EDC"]
+        EDCDB["EDC DB"]
+    end
+
+    subgraph "Capability Bundle: Digital Twin"
+        DTR["DTR"]
+        DTRDB["DTR DB"]
+    end
+
+    subgraph "Capability Bundle: Data Persitence Layer"
+        SimpleSubmodelServer["Simple Submodel Server"]
+    end
+
+    subgraph "Hausanschluss Bundles"
+        subgraph "Data Provider"
+            DataProvider["Data Provider"]
+        end
+        subgraph "Data Consumer"
+            DataConsumer["Data Consumer"]
+        end
+        subgraph "Enablement Provider"
+            EnablementProvider["Enablement Provider"]
+        end
+    end
+
+    EDC -.-> SSIWalletStub
+    EDC -.-> Vault
+    DataProvider --> EDC
+    DataProvider --> DTR
+    DataProvider --> SimpleSubmodelServer
+    DataConsumer --> EDC
+    EnablementProvider --> DataConsumer
+    EnablementProvider --> DataProvider
+
+````
+
+#### Deployment strategies
+
+##### Role: Data Provider
+
+The standard data provider role consists of a EDC, DTR and Submodel Server Bundles. EDC uses the Identity Wallet Bundle.
+
+````mermaid
+flowchart BT
+    A["Capability Bundle: Identity & Trust"]
+    B["Capability Bundle: Data Persistence Layer"]
+    C["Capability Bundle: Dataspace Connector"]
+    D["Capability Bundle: Digital Twin"]
+    E["Application to be tested/developed"]
+    E --> B
+    E --> C
+    E --> D
+    C --> A
+````
+
+##### Role: Data Consumer
+
+The standard data consumer role consists of only the EDC Bundle and the Identity Wallet Bundle.
+
+````mermaid
+flowchart BT
+    A["Capability Bundle: Identity & Trust"]
+    B["Capability Bundle: Dataspace Connector"]
+    C["Application to be tested/developed"]
+    C --> B
+    B --> A
+
+````
+
+##### Role: Enablement Provider
+
+The Enablement Provider roles consists of both the Data Consumer and Data Provider bundles. This allows provisioning of
+data and the consumtion of the provisioned data by a application.
+
+````mermaid
+flowchart BT
+    A["Capability Bundle: Identity & Trust"]
+    B["Capability Bundle: Data Persitance Layer"]
+    C["Application to be tested/developed"]
+    D["Capability Bundle: Digital Twin"]
+    E["Capability Bundle: Dataspace Connector (Provider)"]
+    F["Capability Bundle: Dataspace Connector (Consumer)"]
+    C --> B
+    C --> D
+    C --> E
+    C --> F
+    E --> A
+    F --> A
+````
+
+##### Bring you own
+
+Each Bundle can be deactivated to use your own component. This requires configuration of the component specific
+parameters in the other components.
+
+In this example this would be the configuration of the Identity Wallet within the EDC.
+
+````mermaid
+flowchart BT
+    A["Application to be tested/developed"]
+    B["Capability Bundle: Dataspace Connector"]
+    C["
Capability Bundle: Identity & Trust
"]
+    D["Own Identity Wallet"]
+    A --> B
+    B -- identitywallet - bundle . enabled = false --> C
+    B -- configure --> D
+
+````
+
+## 4.4 System
+
+### 4.4.1 Context Delimitation / 4.4.2 Interface Documentation
+
+````mermaid
+flowchart LR
+    Dataprovider["Dataprovider"] -->|stores data| SubmodelServer["Submodel Server"]
+    Dataprovider -->|creates twins| DTR["DTR"]
+    Dataprovider -->|creates contracts| EDC["EDC"]
+    Dataconsumer["Dataconsumer"] -->|negotiate contracts| EDC
+    DTR -->|needs| IdentityWallet["Identity Wallet"]
+    IdentityWallet -->|needs| Postgres["PostgreSQL Database"]
+````
+
+# 5 Build
+
+## 5.1 DevOps Setup Definition
+
+### 5.1.1 Tool Chain Definition
+
+##### Version Control & Source Code Management
+
+- **Git & GitHub**: Management of the source code, the Helm Charts, and associated documentation in a centralized
+  repository.
+
+##### Build and CI/CD Tools
+
+- **GitHub Actions**: Automated workflows for linting, testing, packaging, and releasing the Helm Charts.
+- **Helm CLI**: For validating, packaging, and deploying the charts.
+- **Helm Lint**: Performing static analyses to ensure compliance with chart standards.
+
+##### Testing and Validation Tools
+
+- **chart-testing Tool**: Validation of the Helm Charts based on Kubernetes schemas.
path: docs/concept/TAP7.1-solution-design.md
user: login: mkanal
body: ```suggestion
- **Chart-testing Tool**: Validation of the Helm Charts based on Kubernetes schemas.
```
created_at: 2025-03-28T12:21:06Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,425 @@
+# [TAP 7.1] Solution Design Hausanschluss Bundle Konzept
+
+# 1 Business Case
+
+## 1.1 Executive Summary
+
+The EDC "Hausanschluss" Bundle aims to simplify the installation of the enablement services Eclipse Dataspace
+Connector (EDC), Digital Twin Registry (DTR), and their supporting components. By developing a flexible, parameterizable
+installation package, the project seeks to reduce deployment complexity and lower barriers to participation in the
+Catena‑X data space. This bundle will enable independent component updates and support a modular "bring your own"
+approach, ultimately fostering a more efficient and accessible ecosystem for diverse participants—such as testers,
+external developers, and small and medium-sized enterprises.
+
+## 1.2 Business Need
+
+Current deployment methods for data space integration are complex and require significant manual effort. This PoC
+addresses the need to:
+
+- Reduce Complexity: Simplify the deployment topology by bundling components into capabilities.
+- Automate Deployment: Provide an automated installation package using Kubernetes and HELM.
+- Reduce Configuration Efforts: Streamline and reduce the number of configuration steps required for integration.
+- Extend Documentation: Provide a detailed documentation tailored to the target groups.
+- Enable Extension: Design the system to allow the seamless addition of new components or capabilities.
+
+## 1.3 Objectives
+
+- Simplify Deployment and Maintenance: Develop an installation package that minimizes manual configuration through
+  automation.
+- Ensure Modularity: Structure the bundle so that components can be independently installed, updated, or replaced
+  without
+  affecting other services.
+- Facilitate Flexibility: Implement a "bring your own" model for key components, such as EDC, PostgreSQL, and HashiCorp
+  Vault, to allow tailored deployments that meet specific needs.
+- Increase Accessibility: Lower entry barriers for new participants by reducing technical complexity and operational
+  dependencies.
+- Scalability: Structure the bundle so that it can be deployed multiple times.
+
+## 1.4 Expected Deliverables
+
+- PoC Documentation: A concept and architecture overview highlighting the modular design.
+- Modular Installation Package: A set of HELM charts for deploying the enablement service bundles:
+    - EDC Bundle: Including the Eclipse Dataspace Connector, EDC PostgreSQL, and HashiCorp Vault.
+    - Digital Twin Bundle: Featuring components such as the Decentral DT Registry (with “bring your own” PostgreSQL) and
+      a Submodel Server Bundle.
+    - Identity Wallet Bundle: Covering the Identity Wallet functionality.
+- Demonstration Environment: A test deployment showcasing reduced complexity and improved efficiency.
+- Basic User Guide: Instructions on how to deploy and update the PoC bundle.
+
+## 1.5 Benefits
+
+- Operational Efficiency: Faster and more reliable deployments with less manual work.
+- Scalability: A modular design that can be scaled or adapted for future full-scale deployments.
+- Ease of Adoption: Simplified deployment processes make it easier for testers and external developers to engage.
+
+## 1.6. Dependencies
+
+- Interoperability with the CATENA‑X standards.
+
+## 1.7. Success Criteria
+
+- Technology Readiness Level: Achievement of a Technology Readiness Level (TRL) of 3, as specified in the requirements.
+- Functional PoC Deployment: Demonstrated automated, modular installation with reduced manual steps.
+- Simplified Configuration: Clear evidence of reduced configuration complexity.
+- Positive Feedback: End-user validation from a select group of demo participants and the Tractus-X community.
+- Documentation Completeness: Availability of concise deployment and user guides.
+
+## 1.8. Out of Scope
+
+- Full Production Readiness: This PoC is not intended to be a production-ready solution.
+- Core Services Exclusion: Core services are not part of the Hausanschluss Bundles.
+- App Provider Role: The role of App Provider is considered out of scope for this deployment.
+- Alternative Deployment Techniques: While the evaluation of alternative deployment methods is acknowledged, the primary
+  focus remains on Kubernetes and HELM-based deployment.
+
+# 2 Requirements Analysis
+
+## 2.1 Assumptions
+
+## 2.2 Requirements Catalog
+
+| ID             | Requirement                                                                                                                                                                                                                                                                                                                                               | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | Deliverables / Acceptance Criteria                                                                                                           |
+|----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------|
+| [WP-7.1.-D001] | TAP7.1 Hausanschluss Bundle aims to simplify the installation and maintenance of the EDC and other components that together ensure a “home connection”. A flexible, parameterizable installation package is intended to reduce complexity and make integration more efficient, thereby simplifying participation in Catena‑X for additional participants. | Specification and development of a flexible, parameterizable installation package that reduces the complexity of installing and maintaining the required components for seamless integration into the Catena‑X data space. This package should facilitate updates and new versions, making participation in Catena‑X more efficient and accessible. In doing so, SMEs shall be enabled to participate without high costs or dependency on SaaS providers while maintaining control over their IT infrastructure. | [WP-7.1.-D001] Concept for the Hausanschluss is created                                                                                      |
+| 7.1.1.1        | The solution concept must define the Capability Bundles structures to be implemented. For each Capability Bundle, the included bundles and their versions are mapped.                                                                                                                                                                                     | "The following Capability Bundle structure is implemented:                                                                                                                                                                                                                                                                                                                                                                                                                                                       | "The structure of the Capability Bundles for the Enablement Services has been specified.                                                     |
+| 7.1.1.2        | Definition of Data Space Roles                                                                                                                                                                                                                                                                                                                            | Capability EDC (Data Transfer) Bundle                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | For version R24.12 it is clearly defined which Tractus‑X services and components are assigned to each Capability Bundle"                     |
+| 7.1.1.4        | Modularity & Maintainability: No dependencies between Capability Bundles                                                                                                                                                                                                                                                                                  | Eclipse Dataspace Connector (EDC) v0.9.0                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | "As part of the target group analysis, the target groups are defined and aligned with the data space roles.                                  |
+| 7.1.1.5        | Modularity & Maintainability: Concept for reducing deployment complexity                                                                                                                                                                                                                                                                                  | EDC PostgresSQL                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | Mapping from data space role to target group has been completed.                                                                             |
+| 7.1.1.6        | Modularity & Maintainability                                                                                                                                                                                                                                                                                                                              | HashiCorp Vault                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | Mapping from target group to data space role has been completed.                                                                             |
+| 7.1.1.13       | Solution Concept                                                                                                                                                                                                                                                                                                                                          | Capability Digital Twin Bundle                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | An assignment of data space roles to Capability Bundles has been made."                                                                      |
+| 7.1.1.14       | Scalability of Enablement Services                                                                                                                                                                                                                                                                                                                        | Decentral DT Registry                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | "Components and Services should obly be part of one bundle.                                                                                  |
+| 7.1.1.16       | Interoperability                                                                                                                                                                                                                                                                                                                                          | PostgresSQL                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | Each bundle must be deployable in isolation and can be installed, updated, or removed independently.                                         |
+| [WP-7.1.-D002] | [WP-7.1.-D002] Target group for the specification is defined.                                                                                                                                                                                                                                                                                             | Capability Identity & Trust (Identity Wallet Bundle)                                                                                                                                                                                                                                                                                                                                                                                                                                                             | Capability Bundles must be organized in separate HELM sub‑charts.                                                                            |
+| 7.1.2.1        | Target Group Analysis                                                                                                                                                                                                                                                                                                                                     | Identity Wallet Mock                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | Circular dependencies between bundles must be avoided."                                                                                      |
+| [WP-7.1.-D003] | [WP-7.1.-D003] Decentralized components and services defined                                                                                                                                                                                                                                                                                              | Capability Semantic Model Bundle                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | "Simplification of deployment processes                                                                                                      |
+| 7.1.3.1        | See [WP-7.1.-D001-AC001]                                                                                                                                                                                                                                                                                                                                  | Submodel Mock (aus Umbrella HELM Chart)"                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | A reduction of manual configuration steps has been achieved.                                                                                 |
+| [WP-7.1.-D004] | [WP-7.1.-D004] Documentation of the Hausanschluss Bundle is completed                                                                                                                                                                                                                                                                                     | "Data Consumer                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | Transparency and traceability                                                                                                                |
+| 7.1.4.1        | Documentation of the Hausanschluss-Bundles                                                                                                                                                                                                                                                                                                                | Data Provider                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | Clearly documented deployment steps are provided.                                                                                            |
+| 7.1.4.2        | Documentation of the Hausanschluss-Bundles                                                                                                                                                                                                                                                                                                                | Enablement Service Provider"                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | Improvements of Chart configuration by                                                                                                       |
+| [WP-7.1.-D005] | [WP-7.1.-D005] Umbrella HELM Charts for the Hausanschluss developed, tested, and documented                                                                                                                                                                                                                                                               | "Unique assignment of components and services to a defined Capability Bundle.                                                                                                                                                                                                                                                                                                                                                                                                                                    | usage of template                                                                                                                            |
+| 7.1.5.1        | Re-activate Umbrella HELM Charts to the latest release state                                                                                                                                                                                                                                                                                              | Each component and service should be assigned to only one Capability Bundle.                                                                                                                                                                                                                                                                                                                                                                                                                                     | reducing configuration options                                                                                                               |
+| 7.1.5.2        | Hierarchical structuring and bundling of Enablement Service components in the Umbrella HELM Chart                                                                                                                                                                                                                                                         | Dependencies between Capability Bundles are allowed."                                                                                                                                                                                                                                                                                                                                                                                                                                                            | reducing manual steps in the setup"                                                                                                          |
+| 7.1.5.3        | Interchangeability of bundle components via “Bring-Your-Own” components                                                                                                                                                                                                                                                                                   | The system deployment should be optimized to reduce the existing complexity. The goal is to make the provisioning process more efficient, robust, and easier to maintain.                                                                                                                                                                                                                                                                                                                                        | Charts are published via a publicly accessible charts repository.                                                                            |
+| [WP-7.1.-D006] | [WP-7.1.-D006] Product developed according to a Technology Readiness Level (TRL) of 3                                                                                                                                                                                                                                                                     | Charts are published automatically.                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | "The solution design for the ""Hausanschluss"" Bundle is created.                                                                            |
+| 7.1.6.1        | POC                                                                                                                                                                                                                                                                                                                                                       | Creation of a solution design for the “Hausanschluss” Bundle.                                                                                                                                                                                                                                                                                                                                                                                                                                                    | The solution design for the ""Hausanschluss"" Bundle ispublished in the repository: https://github.com/eclipse-tractusx/tractus-x-umbrella." |
+| 7.1.6.2        | Deployment Strategy                                                                                                                                                                                                                                                                                                                                       | Scalability of Enablement Services                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | "Developers should be able to deploy an arbitrary number of Enablement Services.                                                             |
+
+# 3 AS-IS Analysis
+
+## 3.1 People
+
+### 3.1.1 Target Group Analysis
+
+See "4.1.1 To-be Target Group Analysis" below. No deviations between As-is and To-be target groups have been identified.
+
+## 3.2 Process
+
+### 3.2.1 Use Case View (high-level)
+
+Umbrella Chart is intended for the following Use Cases:
+
+| Actor             | Use case                                                                                             |
+|-------------------|------------------------------------------------------------------------------------------------------|
+| Product Developer | Sandbox Environments: Create local environments to evaluate and experiment with Catena-X components. |
+| Product Developer | Development: Provide a unified setup for contributors and developers working on Tractus-X projects.  |
+| Product Tester    | Testing: Run end-to-end tests for Catena-X services.                                                 |
+
+## 3.4 System
+
+### 3.4.1 Context Delimitation
+
+````mermaid
+flowchart
+    subgraph "Umbrella Chart"
+        ChartYaml["Chart.yaml"]
+        subgraph charts
+            Portal["Portal"]
+            CentralIdp["CentralIdp"]
+            DiscoveryFinder["Discovery Finder"]
+            SDFactory["SD-Factory"]
+            SSICredentialIssuer["SSI Credential Issuer"]
+            SemanticHub["Semantic Hub"]
+            BPDM["BPDM"]
+            DataConsumer["Data Consumer"]
+            DataProvider["Data Provider"]
+            BDRS["BDRS"]
+            SSIWalletStub["SSI Wallet Stub"]
+        end
+        subgraph "tx-data-provider"
+            EDC["EDC"]
+            DTR["DTR"]
+            SubmodelServer["Submodel Server"]
+        end
+    end
+
+    ChartYaml --> Portal
+    ChartYaml --> CentralIdp
+    ChartYaml --> DiscoveryFinder
+    ChartYaml --> SDFactory
+    ChartYaml --> SSICredentialIssuer
+    ChartYaml --> SemanticHub
+    ChartYaml --> BPDM
+    ChartYaml --> DataConsumer
+    ChartYaml --> DataProvider
+    ChartYaml --> BDRS
+    ChartYaml --> SSIWalletStub
+    DataConsumer --> EDC
+    DataProvider --> EDC
+    DataProvider --> DTR
+    DataProvider --> SubmodelServer
+````
+
+#### Existing Umbrella Chart Structure
+
+# 4 TO-BE Design
+
+## 4.1 People
+
+### 4.1.1 Target Group Analysis
+
+Overall data space roles: https://catena-x.net/en/1/catena-x-introduce-implement/how-to-operate-catena-x
+
+The relevant data space roles for us under requirement 7.1.1.1 are:
+
+- Data Consumer
+- Data Provider
+- Enablement Service Provider
+
+Scope: Umbrella HELM Charts
+
+- Enablement Services: These services are included under the umbrella of HELM charts, focusing on enabling
+  functionalities.
+- Out of Scope: Core services such as Portal or BPDM are not considered within this scope.
+
+Primary target groups:
+
+| No. | Target group                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | Data space roles                                                    | Target group differentiation                                                                                                                                                                                                                                                                            | Behaviour, Needs, Pains & Usage                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+|-----|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| 1   | Developers<ul><li>External Developers (not Tractus-X developers): Utilize the chart for demonstration or evaluation purposes.</li><li>Experienced software and product developers who are developing a business app for a CATENA-X data space. They need to develop the app against the interfaces of the data space and integrate them accordingly.</li><li>They emphasize efficient and cost-effective implementation:<ul><li>Cost Efficiency: They do not want to use expensive SaaS solutions.</li><li>Technical Independence: They lack the knowledge and capacity to deploy the enablement and core services of the data space themselves.</li><li>Focus on Development: They concentrate on application development without delving deeply into the deployment and operation of the underlying infrastructure.</li></ul></li><li>Out of Scope: Developers running tests in test runners are not considered within this scope.</li></ul> | Data Consumer <br/> Data Provider <br/> Enablement Service Provider |                                                                                                                                                                                                                                                                                                         | <ul><li>Needs / sources of information<ul><li><a href="https://eclipse-tractusx.github.io/Kits/">Kit documentation tractus-x</a> for interaction purposes</li><li><a href="https://catenax-ev.github.io/">Catena-X doucmentation</a> for standards and regulations</li><li><a href="https://github.com/eclipse-tractusx/tractus-x-umbrella">Umbrella documentation</a> for umbrella component information</li></ul></li><li>Challenges → Solution<ul><li>Decentralization e.g. Where are other systems? How to interact with them? → Solution: Umbrella charts and bundles for deployment</li><li>Complex setup → Solution: delivery of small capability bundles</li></ul></li></ul> |
+| 2   | <ul><li>Tester requiring a test system (Testmanagement e.V.)</li><li>Requirement: Testbed</li></ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | Data Consumer <br/> Data Provider <br/> Enablement Service Provider | <ul><li>Developer (1) tests their feature.</li><li>Tester (2) performs end-to-end testing.</li><li>For the tester, the modular structure is less relevant since they focus on E2E testing, whereas the developer selects the required components.</li><li>The testbed must be easy to deploy.</li></ul> | <ul><li>Same as above from an End-to-end testing perspective</li><li>Typically a tester has less technical know-how than a developer and therefore needs a "one-size-fits-all" chart for easier testing</li></ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+
+## 4.2 Process
+
+### 4.2.1 Use Case View (high-level)
+
+| Use Case                                | Description                                                                                                       | Actors            |
+|-----------------------------------------|-------------------------------------------------------------------------------------------------------------------|-------------------|
+| Configure HELM Chart                    | The product developer configures the HELM Chart for the specific environment.                                     | Product Developer |
+| Configure Secrets                       | The product developer manages and configures secrets.                                                             | Product Developer |
+| Execute Deployment Pipeline             | The product developer successfully executes the deployment pipeline for the HELM Chart.                           | Product Developer |
+| Integrate EDC, DTR, and Identity Wallet | The actors integrate the components EDC, Digital Twin Registry, and Identity Wallet for seamless interoperability | Product Developer |
+| Set Up Connection Infrastructure        | The actor sets up the connection infrastructure for linking to the central data space infrastructure.             | Product Developer |
+| Maintain Infrastructure Module          | The product developer maintains the modular architecture of the HELM Chart.                                       | Product Developer |
+| Ensure Scalability                      | The product developer ensures scalability to support growing numbers of users and data volumes.                   | Product Developer |
+| Sandbox Environments                    | The product developer creates local environments to evaluate and experiment with Catena-X components.             | Product Developer |
+| E2E Testing                             | The product tester runs end-to-end tests for Catena-X services.                                                   | Product Tester    |
+
+### 4.2.2 Business Process (SCC Artifact)
+
+#### Chart Release Process
+
+Charts will be released using the already existing workflow in the Umbrella Chart repository. The workflow will
+automatically release a Chart, once it is pushed to the "charts/" directory with a new Chart version.
+
+#### Capability Bundle Structure
+
+Capability bundle modularization for the Tractus-X Umbrella Helm chart is a sound architectural and operational design.
+It aligns with both the domain-driven architecture of Catena-X (data exchange, digital twin, identity, semantics are
+distinct domains) and with Kubernetes best practices for managing complex applications (using an umbrella chart to
+bundle related microservices).
+
+Each bundle is self-sufficient, which improves isolation (failures or changes in one domain have minimal impact on
+others) and allows scaling and upgrading along domain lines. It simplifies deployment by allowing “plug-and-play”
+capabilities: an Enablement Service Provider can decide which bundles to operate based on its role e.g., include the
+Digital Twin and Semantic bundles if offering an asset-rich service, or omit them if not. The approach is consistent
+with how other OSS projects deliver multi-component systems, providing one-step installation without sacrificing the
+ability to tweak individual parts.
+
+Why this structure was proposed:
+
+1. **Clear Separation of Concerns**  
+   Each capability bundle (e.g. EDC Data Transfer, Digital Twin, Identity & Trust, Semantic Model) aligns with a
+   specific functional domain. This separation makes it easier to understand the role of each service (e.g., the EDC
+   connector vs. the digital twin registry), reduces coupling between unrelated components, and ultimately makes
+   maintenance and troubleshooting more straightforward.
+2. **Modular Deployment**  
+   Some participants in Catena-X may not need all services (e.g., some might not use the Digital Twin bundle). By
+   structuring the umbrella chart into bundles, a user can enable just those needed capabilities. This leads to leaner
+   installs and avoids unnecessary resource usage.
+3. **Best Practices with Helm**  
+   Using an umbrella chart with subcharts/bundles is a well-recognized Helm best practice for complex applications. It
+   allows a single helm install to set up multiple microservices while still allowing each service to have its own
+   lifecycle, configuration, and version.
+4. **Alignment with Domain-Driven Approach**  
+   Catena-X is organized around distinct, loosely-coupled “building blocks.” Bundling services by domain matches this
+   architectural vision. It’s clear which domain each set of microservices belongs to (EDC for data exchange, identity
+   for credential management, etc.). This clarity also helps new adopters navigate the ecosystem.
+
+````mermaid
+flowchart LR
+    subgraph "Core Services"
+        Vault["Vault"]
+    end
+
+    subgraph "Capability Bundle: Identity & Trust"
+        SSIWalletStub["SSI Wallet Stub"]
+    end
+
+    subgraph "Capability Bundle: Dataspace Connector"
+        EDC["EDC"]
+        EDCDB["EDC DB"]
+    end
+
+    subgraph "Capability Bundle: Digital Twin"
+        DTR["DTR"]
+        DTRDB["DTR DB"]
+    end
+
+    subgraph "Capability Bundle: Data Persitence Layer"
+        SimpleSubmodelServer["Simple Submodel Server"]
+    end
+
+    subgraph "Hausanschluss Bundles"
+        subgraph "Data Provider"
+            DataProvider["Data Provider"]
+        end
+        subgraph "Data Consumer"
+            DataConsumer["Data Consumer"]
+        end
+        subgraph "Enablement Provider"
+            EnablementProvider["Enablement Provider"]
+        end
+    end
+
+    EDC -.-> SSIWalletStub
+    EDC -.-> Vault
+    DataProvider --> EDC
+    DataProvider --> DTR
+    DataProvider --> SimpleSubmodelServer
+    DataConsumer --> EDC
+    EnablementProvider --> DataConsumer
+    EnablementProvider --> DataProvider
+
+````
+
+#### Deployment strategies
+
+##### Role: Data Provider
+
+The standard data provider role consists of a EDC, DTR and Submodel Server Bundles. EDC uses the Identity Wallet Bundle.
+
+````mermaid
+flowchart BT
+    A["Capability Bundle: Identity & Trust"]
+    B["Capability Bundle: Data Persistence Layer"]
+    C["Capability Bundle: Dataspace Connector"]
+    D["Capability Bundle: Digital Twin"]
+    E["Application to be tested/developed"]
+    E --> B
+    E --> C
+    E --> D
+    C --> A
+````
+
+##### Role: Data Consumer
+
+The standard data consumer role consists of only the EDC Bundle and the Identity Wallet Bundle.
+
+````mermaid
+flowchart BT
+    A["Capability Bundle: Identity & Trust"]
+    B["Capability Bundle: Dataspace Connector"]
+    C["Application to be tested/developed"]
+    C --> B
+    B --> A
+
+````
+
+##### Role: Enablement Provider
+
+The Enablement Provider roles consists of both the Data Consumer and Data Provider bundles. This allows provisioning of
+data and the consumtion of the provisioned data by a application.
+
+````mermaid
+flowchart BT
+    A["Capability Bundle: Identity & Trust"]
+    B["Capability Bundle: Data Persitance Layer"]
+    C["Application to be tested/developed"]
+    D["Capability Bundle: Digital Twin"]
+    E["Capability Bundle: Dataspace Connector (Provider)"]
+    F["Capability Bundle: Dataspace Connector (Consumer)"]
+    C --> B
+    C --> D
+    C --> E
+    C --> F
+    E --> A
+    F --> A
+````
+
+##### Bring you own
+
+Each Bundle can be deactivated to use your own component. This requires configuration of the component specific
+parameters in the other components.
+
+In this example this would be the configuration of the Identity Wallet within the EDC.
+
+````mermaid
+flowchart BT
+    A["Application to be tested/developed"]
+    B["Capability Bundle: Dataspace Connector"]
+    C["
Capability Bundle: Identity & Trust
"]
+    D["Own Identity Wallet"]
+    A --> B
+    B -- identitywallet - bundle . enabled = false --> C
+    B -- configure --> D
+
+````
+
+## 4.4 System
+
+### 4.4.1 Context Delimitation / 4.4.2 Interface Documentation
+
+````mermaid
+flowchart LR
+    Dataprovider["Dataprovider"] -->|stores data| SubmodelServer["Submodel Server"]
+    Dataprovider -->|creates twins| DTR["DTR"]
+    Dataprovider -->|creates contracts| EDC["EDC"]
+    Dataconsumer["Dataconsumer"] -->|negotiate contracts| EDC
+    DTR -->|needs| IdentityWallet["Identity Wallet"]
+    IdentityWallet -->|needs| Postgres["PostgreSQL Database"]
+````
+
+# 5 Build
+
+## 5.1 DevOps Setup Definition
+
+### 5.1.1 Tool Chain Definition
path: docs/concept/TAP7.1-solution-design.md
user: login: mkanal
body: Are we sure to deliver all of this? Is this mentioned in the requirements or do we extend the scope? 
created_at: 2025-03-28T12:21:34Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,425 @@
+# [TAP 7.1] Solution Design Hausanschluss Bundle Konzept
+
+# 1 Business Case
+
+## 1.1 Executive Summary
+
+The EDC "Hausanschluss" Bundle aims to simplify the installation of the enablement services Eclipse Dataspace
+Connector (EDC), Digital Twin Registry (DTR), and their supporting components. By developing a flexible, parameterizable
+installation package, the project seeks to reduce deployment complexity and lower barriers to participation in the
+Catena‑X data space. This bundle will enable independent component updates and support a modular "bring your own"
+approach, ultimately fostering a more efficient and accessible ecosystem for diverse participants—such as testers,
+external developers, and small and medium-sized enterprises.
+
+## 1.2 Business Need
+
+Current deployment methods for data space integration are complex and require significant manual effort. This PoC
+addresses the need to:
+
+- Reduce Complexity: Simplify the deployment topology by bundling components into capabilities.
+- Automate Deployment: Provide an automated installation package using Kubernetes and HELM.
+- Reduce Configuration Efforts: Streamline and reduce the number of configuration steps required for integration.
+- Extend Documentation: Provide a detailed documentation tailored to the target groups.
+- Enable Extension: Design the system to allow the seamless addition of new components or capabilities.
+
+## 1.3 Objectives
+
+- Simplify Deployment and Maintenance: Develop an installation package that minimizes manual configuration through
+  automation.
+- Ensure Modularity: Structure the bundle so that components can be independently installed, updated, or replaced
+  without
+  affecting other services.
+- Facilitate Flexibility: Implement a "bring your own" model for key components, such as EDC, PostgreSQL, and HashiCorp
+  Vault, to allow tailored deployments that meet specific needs.
+- Increase Accessibility: Lower entry barriers for new participants by reducing technical complexity and operational
+  dependencies.
+- Scalability: Structure the bundle so that it can be deployed multiple times.
+
+## 1.4 Expected Deliverables
+
+- PoC Documentation: A concept and architecture overview highlighting the modular design.
+- Modular Installation Package: A set of HELM charts for deploying the enablement service bundles:
+    - EDC Bundle: Including the Eclipse Dataspace Connector, EDC PostgreSQL, and HashiCorp Vault.
+    - Digital Twin Bundle: Featuring components such as the Decentral DT Registry (with “bring your own” PostgreSQL) and
+      a Submodel Server Bundle.
+    - Identity Wallet Bundle: Covering the Identity Wallet functionality.
+- Demonstration Environment: A test deployment showcasing reduced complexity and improved efficiency.
+- Basic User Guide: Instructions on how to deploy and update the PoC bundle.
+
+## 1.5 Benefits
+
+- Operational Efficiency: Faster and more reliable deployments with less manual work.
+- Scalability: A modular design that can be scaled or adapted for future full-scale deployments.
+- Ease of Adoption: Simplified deployment processes make it easier for testers and external developers to engage.
+
+## 1.6. Dependencies
+
+- Interoperability with the CATENA‑X standards.
+
+## 1.7. Success Criteria
+
+- Technology Readiness Level: Achievement of a Technology Readiness Level (TRL) of 3, as specified in the requirements.
+- Functional PoC Deployment: Demonstrated automated, modular installation with reduced manual steps.
+- Simplified Configuration: Clear evidence of reduced configuration complexity.
+- Positive Feedback: End-user validation from a select group of demo participants and the Tractus-X community.
+- Documentation Completeness: Availability of concise deployment and user guides.
+
+## 1.8. Out of Scope
+
+- Full Production Readiness: This PoC is not intended to be a production-ready solution.
+- Core Services Exclusion: Core services are not part of the Hausanschluss Bundles.
+- App Provider Role: The role of App Provider is considered out of scope for this deployment.
+- Alternative Deployment Techniques: While the evaluation of alternative deployment methods is acknowledged, the primary
+  focus remains on Kubernetes and HELM-based deployment.
+
+# 2 Requirements Analysis
+
+## 2.1 Assumptions
+
+## 2.2 Requirements Catalog
+
+| ID             | Requirement                                                                                                                                                                                                                                                                                                                                               | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | Deliverables / Acceptance Criteria                                                                                                           |
+|----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------|
+| [WP-7.1.-D001] | TAP7.1 Hausanschluss Bundle aims to simplify the installation and maintenance of the EDC and other components that together ensure a “home connection”. A flexible, parameterizable installation package is intended to reduce complexity and make integration more efficient, thereby simplifying participation in Catena‑X for additional participants. | Specification and development of a flexible, parameterizable installation package that reduces the complexity of installing and maintaining the required components for seamless integration into the Catena‑X data space. This package should facilitate updates and new versions, making participation in Catena‑X more efficient and accessible. In doing so, SMEs shall be enabled to participate without high costs or dependency on SaaS providers while maintaining control over their IT infrastructure. | [WP-7.1.-D001] Concept for the Hausanschluss is created                                                                                      |
+| 7.1.1.1        | The solution concept must define the Capability Bundles structures to be implemented. For each Capability Bundle, the included bundles and their versions are mapped.                                                                                                                                                                                     | "The following Capability Bundle structure is implemented:                                                                                                                                                                                                                                                                                                                                                                                                                                                       | "The structure of the Capability Bundles for the Enablement Services has been specified.                                                     |
+| 7.1.1.2        | Definition of Data Space Roles                                                                                                                                                                                                                                                                                                                            | Capability EDC (Data Transfer) Bundle                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | For version R24.12 it is clearly defined which Tractus‑X services and components are assigned to each Capability Bundle"                     |
+| 7.1.1.4        | Modularity & Maintainability: No dependencies between Capability Bundles                                                                                                                                                                                                                                                                                  | Eclipse Dataspace Connector (EDC) v0.9.0                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | "As part of the target group analysis, the target groups are defined and aligned with the data space roles.                                  |
+| 7.1.1.5        | Modularity & Maintainability: Concept for reducing deployment complexity                                                                                                                                                                                                                                                                                  | EDC PostgresSQL                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | Mapping from data space role to target group has been completed.                                                                             |
+| 7.1.1.6        | Modularity & Maintainability                                                                                                                                                                                                                                                                                                                              | HashiCorp Vault                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | Mapping from target group to data space role has been completed.                                                                             |
+| 7.1.1.13       | Solution Concept                                                                                                                                                                                                                                                                                                                                          | Capability Digital Twin Bundle                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | An assignment of data space roles to Capability Bundles has been made."                                                                      |
+| 7.1.1.14       | Scalability of Enablement Services                                                                                                                                                                                                                                                                                                                        | Decentral DT Registry                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | "Components and Services should obly be part of one bundle.                                                                                  |
+| 7.1.1.16       | Interoperability                                                                                                                                                                                                                                                                                                                                          | PostgresSQL                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | Each bundle must be deployable in isolation and can be installed, updated, or removed independently.                                         |
+| [WP-7.1.-D002] | [WP-7.1.-D002] Target group for the specification is defined.                                                                                                                                                                                                                                                                                             | Capability Identity & Trust (Identity Wallet Bundle)                                                                                                                                                                                                                                                                                                                                                                                                                                                             | Capability Bundles must be organized in separate HELM sub‑charts.                                                                            |
+| 7.1.2.1        | Target Group Analysis                                                                                                                                                                                                                                                                                                                                     | Identity Wallet Mock                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | Circular dependencies between bundles must be avoided."                                                                                      |
+| [WP-7.1.-D003] | [WP-7.1.-D003] Decentralized components and services defined                                                                                                                                                                                                                                                                                              | Capability Semantic Model Bundle                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | "Simplification of deployment processes                                                                                                      |
+| 7.1.3.1        | See [WP-7.1.-D001-AC001]                                                                                                                                                                                                                                                                                                                                  | Submodel Mock (aus Umbrella HELM Chart)"                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | A reduction of manual configuration steps has been achieved.                                                                                 |
+| [WP-7.1.-D004] | [WP-7.1.-D004] Documentation of the Hausanschluss Bundle is completed                                                                                                                                                                                                                                                                                     | "Data Consumer                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | Transparency and traceability                                                                                                                |
+| 7.1.4.1        | Documentation of the Hausanschluss-Bundles                                                                                                                                                                                                                                                                                                                | Data Provider                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | Clearly documented deployment steps are provided.                                                                                            |
+| 7.1.4.2        | Documentation of the Hausanschluss-Bundles                                                                                                                                                                                                                                                                                                                | Enablement Service Provider"                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | Improvements of Chart configuration by                                                                                                       |
+| [WP-7.1.-D005] | [WP-7.1.-D005] Umbrella HELM Charts for the Hausanschluss developed, tested, and documented                                                                                                                                                                                                                                                               | "Unique assignment of components and services to a defined Capability Bundle.                                                                                                                                                                                                                                                                                                                                                                                                                                    | usage of template                                                                                                                            |
+| 7.1.5.1        | Re-activate Umbrella HELM Charts to the latest release state                                                                                                                                                                                                                                                                                              | Each component and service should be assigned to only one Capability Bundle.                                                                                                                                                                                                                                                                                                                                                                                                                                     | reducing configuration options                                                                                                               |
+| 7.1.5.2        | Hierarchical structuring and bundling of Enablement Service components in the Umbrella HELM Chart                                                                                                                                                                                                                                                         | Dependencies between Capability Bundles are allowed."                                                                                                                                                                                                                                                                                                                                                                                                                                                            | reducing manual steps in the setup"                                                                                                          |
+| 7.1.5.3        | Interchangeability of bundle components via “Bring-Your-Own” components                                                                                                                                                                                                                                                                                   | The system deployment should be optimized to reduce the existing complexity. The goal is to make the provisioning process more efficient, robust, and easier to maintain.                                                                                                                                                                                                                                                                                                                                        | Charts are published via a publicly accessible charts repository.                                                                            |
+| [WP-7.1.-D006] | [WP-7.1.-D006] Product developed according to a Technology Readiness Level (TRL) of 3                                                                                                                                                                                                                                                                     | Charts are published automatically.                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | "The solution design for the ""Hausanschluss"" Bundle is created.                                                                            |
+| 7.1.6.1        | POC                                                                                                                                                                                                                                                                                                                                                       | Creation of a solution design for the “Hausanschluss” Bundle.                                                                                                                                                                                                                                                                                                                                                                                                                                                    | The solution design for the ""Hausanschluss"" Bundle ispublished in the repository: https://github.com/eclipse-tractusx/tractus-x-umbrella." |
+| 7.1.6.2        | Deployment Strategy                                                                                                                                                                                                                                                                                                                                       | Scalability of Enablement Services                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | "Developers should be able to deploy an arbitrary number of Enablement Services.                                                             |
+
+# 3 AS-IS Analysis
+
+## 3.1 People
+
+### 3.1.1 Target Group Analysis
+
+See "4.1.1 To-be Target Group Analysis" below. No deviations between As-is and To-be target groups have been identified.
+
+## 3.2 Process
+
+### 3.2.1 Use Case View (high-level)
+
+Umbrella Chart is intended for the following Use Cases:
+
+| Actor             | Use case                                                                                             |
+|-------------------|------------------------------------------------------------------------------------------------------|
+| Product Developer | Sandbox Environments: Create local environments to evaluate and experiment with Catena-X components. |
+| Product Developer | Development: Provide a unified setup for contributors and developers working on Tractus-X projects.  |
+| Product Tester    | Testing: Run end-to-end tests for Catena-X services.                                                 |
+
+## 3.4 System
+
+### 3.4.1 Context Delimitation
+
+````mermaid
+flowchart
+    subgraph "Umbrella Chart"
+        ChartYaml["Chart.yaml"]
+        subgraph charts
+            Portal["Portal"]
+            CentralIdp["CentralIdp"]
+            DiscoveryFinder["Discovery Finder"]
+            SDFactory["SD-Factory"]
+            SSICredentialIssuer["SSI Credential Issuer"]
+            SemanticHub["Semantic Hub"]
+            BPDM["BPDM"]
+            DataConsumer["Data Consumer"]
+            DataProvider["Data Provider"]
+            BDRS["BDRS"]
+            SSIWalletStub["SSI Wallet Stub"]
+        end
+        subgraph "tx-data-provider"
+            EDC["EDC"]
+            DTR["DTR"]
+            SubmodelServer["Submodel Server"]
+        end
+    end
+
+    ChartYaml --> Portal
+    ChartYaml --> CentralIdp
+    ChartYaml --> DiscoveryFinder
+    ChartYaml --> SDFactory
+    ChartYaml --> SSICredentialIssuer
+    ChartYaml --> SemanticHub
+    ChartYaml --> BPDM
+    ChartYaml --> DataConsumer
+    ChartYaml --> DataProvider
+    ChartYaml --> BDRS
+    ChartYaml --> SSIWalletStub
+    DataConsumer --> EDC
+    DataProvider --> EDC
+    DataProvider --> DTR
+    DataProvider --> SubmodelServer
+````
+
+#### Existing Umbrella Chart Structure
+
+# 4 TO-BE Design
+
+## 4.1 People
+
+### 4.1.1 Target Group Analysis
+
+Overall data space roles: https://catena-x.net/en/1/catena-x-introduce-implement/how-to-operate-catena-x
+
+The relevant data space roles for us under requirement 7.1.1.1 are:
+
+- Data Consumer
+- Data Provider
+- Enablement Service Provider
+
+Scope: Umbrella HELM Charts
+
+- Enablement Services: These services are included under the umbrella of HELM charts, focusing on enabling
+  functionalities.
+- Out of Scope: Core services such as Portal or BPDM are not considered within this scope.
+
+Primary target groups:
+
+| No. | Target group                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | Data space roles                                                    | Target group differentiation                                                                                                                                                                                                                                                                            | Behaviour, Needs, Pains & Usage                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+|-----|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| 1   | Developers<ul><li>External Developers (not Tractus-X developers): Utilize the chart for demonstration or evaluation purposes.</li><li>Experienced software and product developers who are developing a business app for a CATENA-X data space. They need to develop the app against the interfaces of the data space and integrate them accordingly.</li><li>They emphasize efficient and cost-effective implementation:<ul><li>Cost Efficiency: They do not want to use expensive SaaS solutions.</li><li>Technical Independence: They lack the knowledge and capacity to deploy the enablement and core services of the data space themselves.</li><li>Focus on Development: They concentrate on application development without delving deeply into the deployment and operation of the underlying infrastructure.</li></ul></li><li>Out of Scope: Developers running tests in test runners are not considered within this scope.</li></ul> | Data Consumer <br/> Data Provider <br/> Enablement Service Provider |                                                                                                                                                                                                                                                                                                         | <ul><li>Needs / sources of information<ul><li><a href="https://eclipse-tractusx.github.io/Kits/">Kit documentation tractus-x</a> for interaction purposes</li><li><a href="https://catenax-ev.github.io/">Catena-X doucmentation</a> for standards and regulations</li><li><a href="https://github.com/eclipse-tractusx/tractus-x-umbrella">Umbrella documentation</a> for umbrella component information</li></ul></li><li>Challenges → Solution<ul><li>Decentralization e.g. Where are other systems? How to interact with them? → Solution: Umbrella charts and bundles for deployment</li><li>Complex setup → Solution: delivery of small capability bundles</li></ul></li></ul> |
+| 2   | <ul><li>Tester requiring a test system (Testmanagement e.V.)</li><li>Requirement: Testbed</li></ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | Data Consumer <br/> Data Provider <br/> Enablement Service Provider | <ul><li>Developer (1) tests their feature.</li><li>Tester (2) performs end-to-end testing.</li><li>For the tester, the modular structure is less relevant since they focus on E2E testing, whereas the developer selects the required components.</li><li>The testbed must be easy to deploy.</li></ul> | <ul><li>Same as above from an End-to-end testing perspective</li><li>Typically a tester has less technical know-how than a developer and therefore needs a "one-size-fits-all" chart for easier testing</li></ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+
+## 4.2 Process
+
+### 4.2.1 Use Case View (high-level)
+
+| Use Case                                | Description                                                                                                       | Actors            |
+|-----------------------------------------|-------------------------------------------------------------------------------------------------------------------|-------------------|
+| Configure HELM Chart                    | The product developer configures the HELM Chart for the specific environment.                                     | Product Developer |
+| Configure Secrets                       | The product developer manages and configures secrets.                                                             | Product Developer |
+| Execute Deployment Pipeline             | The product developer successfully executes the deployment pipeline for the HELM Chart.                           | Product Developer |
+| Integrate EDC, DTR, and Identity Wallet | The actors integrate the components EDC, Digital Twin Registry, and Identity Wallet for seamless interoperability | Product Developer |
+| Set Up Connection Infrastructure        | The actor sets up the connection infrastructure for linking to the central data space infrastructure.             | Product Developer |
+| Maintain Infrastructure Module          | The product developer maintains the modular architecture of the HELM Chart.                                       | Product Developer |
+| Ensure Scalability                      | The product developer ensures scalability to support growing numbers of users and data volumes.                   | Product Developer |
+| Sandbox Environments                    | The product developer creates local environments to evaluate and experiment with Catena-X components.             | Product Developer |
+| E2E Testing                             | The product tester runs end-to-end tests for Catena-X services.                                                   | Product Tester    |
+
+### 4.2.2 Business Process (SCC Artifact)
+
+#### Chart Release Process
+
+Charts will be released using the already existing workflow in the Umbrella Chart repository. The workflow will
+automatically release a Chart, once it is pushed to the "charts/" directory with a new Chart version.
+
+#### Capability Bundle Structure
+
+Capability bundle modularization for the Tractus-X Umbrella Helm chart is a sound architectural and operational design.
+It aligns with both the domain-driven architecture of Catena-X (data exchange, digital twin, identity, semantics are
+distinct domains) and with Kubernetes best practices for managing complex applications (using an umbrella chart to
+bundle related microservices).
+
+Each bundle is self-sufficient, which improves isolation (failures or changes in one domain have minimal impact on
+others) and allows scaling and upgrading along domain lines. It simplifies deployment by allowing “plug-and-play”
+capabilities: an Enablement Service Provider can decide which bundles to operate based on its role e.g., include the
+Digital Twin and Semantic bundles if offering an asset-rich service, or omit them if not. The approach is consistent
+with how other OSS projects deliver multi-component systems, providing one-step installation without sacrificing the
+ability to tweak individual parts.
+
+Why this structure was proposed:
+
+1. **Clear Separation of Concerns**  
+   Each capability bundle (e.g. EDC Data Transfer, Digital Twin, Identity & Trust, Semantic Model) aligns with a
+   specific functional domain. This separation makes it easier to understand the role of each service (e.g., the EDC
+   connector vs. the digital twin registry), reduces coupling between unrelated components, and ultimately makes
+   maintenance and troubleshooting more straightforward.
+2. **Modular Deployment**  
+   Some participants in Catena-X may not need all services (e.g., some might not use the Digital Twin bundle). By
+   structuring the umbrella chart into bundles, a user can enable just those needed capabilities. This leads to leaner
+   installs and avoids unnecessary resource usage.
+3. **Best Practices with Helm**  
+   Using an umbrella chart with subcharts/bundles is a well-recognized Helm best practice for complex applications. It
+   allows a single helm install to set up multiple microservices while still allowing each service to have its own
+   lifecycle, configuration, and version.
+4. **Alignment with Domain-Driven Approach**  
+   Catena-X is organized around distinct, loosely-coupled “building blocks.” Bundling services by domain matches this
+   architectural vision. It’s clear which domain each set of microservices belongs to (EDC for data exchange, identity
+   for credential management, etc.). This clarity also helps new adopters navigate the ecosystem.
+
+````mermaid
+flowchart LR
+    subgraph "Core Services"
+        Vault["Vault"]
+    end
+
+    subgraph "Capability Bundle: Identity & Trust"
+        SSIWalletStub["SSI Wallet Stub"]
+    end
+
+    subgraph "Capability Bundle: Dataspace Connector"
+        EDC["EDC"]
+        EDCDB["EDC DB"]
+    end
+
+    subgraph "Capability Bundle: Digital Twin"
+        DTR["DTR"]
+        DTRDB["DTR DB"]
+    end
+
+    subgraph "Capability Bundle: Data Persitence Layer"
+        SimpleSubmodelServer["Simple Submodel Server"]
+    end
+
+    subgraph "Hausanschluss Bundles"
+        subgraph "Data Provider"
+            DataProvider["Data Provider"]
+        end
+        subgraph "Data Consumer"
+            DataConsumer["Data Consumer"]
+        end
+        subgraph "Enablement Provider"
+            EnablementProvider["Enablement Provider"]
+        end
+    end
+
+    EDC -.-> SSIWalletStub
+    EDC -.-> Vault
+    DataProvider --> EDC
+    DataProvider --> DTR
+    DataProvider --> SimpleSubmodelServer
+    DataConsumer --> EDC
+    EnablementProvider --> DataConsumer
+    EnablementProvider --> DataProvider
+
+````
+
+#### Deployment strategies
+
+##### Role: Data Provider
+
+The standard data provider role consists of a EDC, DTR and Submodel Server Bundles. EDC uses the Identity Wallet Bundle.
+
+````mermaid
+flowchart BT
+    A["Capability Bundle: Identity & Trust"]
+    B["Capability Bundle: Data Persistence Layer"]
+    C["Capability Bundle: Dataspace Connector"]
+    D["Capability Bundle: Digital Twin"]
+    E["Application to be tested/developed"]
+    E --> B
+    E --> C
+    E --> D
+    C --> A
+````
+
+##### Role: Data Consumer
+
+The standard data consumer role consists of only the EDC Bundle and the Identity Wallet Bundle.
+
+````mermaid
+flowchart BT
+    A["Capability Bundle: Identity & Trust"]
+    B["Capability Bundle: Dataspace Connector"]
+    C["Application to be tested/developed"]
+    C --> B
+    B --> A
+
+````
+
+##### Role: Enablement Provider
+
+The Enablement Provider roles consists of both the Data Consumer and Data Provider bundles. This allows provisioning of
+data and the consumtion of the provisioned data by a application.
+
+````mermaid
+flowchart BT
+    A["Capability Bundle: Identity & Trust"]
+    B["Capability Bundle: Data Persitance Layer"]
+    C["Application to be tested/developed"]
+    D["Capability Bundle: Digital Twin"]
+    E["Capability Bundle: Dataspace Connector (Provider)"]
+    F["Capability Bundle: Dataspace Connector (Consumer)"]
+    C --> B
+    C --> D
+    C --> E
+    C --> F
+    E --> A
+    F --> A
+````
+
+##### Bring you own
+
+Each Bundle can be deactivated to use your own component. This requires configuration of the component specific
+parameters in the other components.
+
+In this example this would be the configuration of the Identity Wallet within the EDC.
+
+````mermaid
+flowchart BT
+    A["Application to be tested/developed"]
+    B["Capability Bundle: Dataspace Connector"]
+    C["
Capability Bundle: Identity & Trust
"]
+    D["Own Identity Wallet"]
+    A --> B
+    B -- identitywallet - bundle . enabled = false --> C
+    B -- configure --> D
+
+````
+
+## 4.4 System
+
+### 4.4.1 Context Delimitation / 4.4.2 Interface Documentation
+
+````mermaid
+flowchart LR
+    Dataprovider["Dataprovider"] -->|stores data| SubmodelServer["Submodel Server"]
+    Dataprovider -->|creates twins| DTR["DTR"]
+    Dataprovider -->|creates contracts| EDC["EDC"]
+    Dataconsumer["Dataconsumer"] -->|negotiate contracts| EDC
+    DTR -->|needs| IdentityWallet["Identity Wallet"]
+    IdentityWallet -->|needs| Postgres["PostgreSQL Database"]
+````
+
+# 5 Build
+
+## 5.1 DevOps Setup Definition
+
+### 5.1.1 Tool Chain Definition
+
+##### Version Control & Source Code Management
+
+- **Git & GitHub**: Management of the source code, the Helm Charts, and associated documentation in a centralized
+  repository.
+
+##### Build and CI/CD Tools
+
+- **GitHub Actions**: Automated workflows for linting, testing, packaging, and releasing the Helm Charts.
+- **Helm CLI**: For validating, packaging, and deploying the charts.
+- **Helm Lint**: Performing static analyses to ensure compliance with chart standards.
+
+##### Testing and Validation Tools
+
+- **chart-testing Tool**: Validation of the Helm Charts based on Kubernetes schemas.
path: docs/concept/TAP7.1-solution-design.md
user: login: mkanal
body: Is this KICS and Trivy or do we extend the scope? 
created_at: 2025-03-28T12:21:57Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,425 @@
+# [TAP 7.1] Solution Design Hausanschluss Bundle Konzept
+
+# 1 Business Case
+
+## 1.1 Executive Summary
+
+The EDC "Hausanschluss" Bundle aims to simplify the installation of the enablement services Eclipse Dataspace
+Connector (EDC), Digital Twin Registry (DTR), and their supporting components. By developing a flexible, parameterizable
+installation package, the project seeks to reduce deployment complexity and lower barriers to participation in the
+Catena‑X data space. This bundle will enable independent component updates and support a modular "bring your own"
+approach, ultimately fostering a more efficient and accessible ecosystem for diverse participants—such as testers,
+external developers, and small and medium-sized enterprises.
+
+## 1.2 Business Need
+
+Current deployment methods for data space integration are complex and require significant manual effort. This PoC
+addresses the need to:
+
+- Reduce Complexity: Simplify the deployment topology by bundling components into capabilities.
+- Automate Deployment: Provide an automated installation package using Kubernetes and HELM.
+- Reduce Configuration Efforts: Streamline and reduce the number of configuration steps required for integration.
+- Extend Documentation: Provide a detailed documentation tailored to the target groups.
+- Enable Extension: Design the system to allow the seamless addition of new components or capabilities.
+
+## 1.3 Objectives
+
+- Simplify Deployment and Maintenance: Develop an installation package that minimizes manual configuration through
+  automation.
+- Ensure Modularity: Structure the bundle so that components can be independently installed, updated, or replaced
+  without
+  affecting other services.
+- Facilitate Flexibility: Implement a "bring your own" model for key components, such as EDC, PostgreSQL, and HashiCorp
+  Vault, to allow tailored deployments that meet specific needs.
+- Increase Accessibility: Lower entry barriers for new participants by reducing technical complexity and operational
+  dependencies.
+- Scalability: Structure the bundle so that it can be deployed multiple times.
+
+## 1.4 Expected Deliverables
+
+- PoC Documentation: A concept and architecture overview highlighting the modular design.
+- Modular Installation Package: A set of HELM charts for deploying the enablement service bundles:
+    - EDC Bundle: Including the Eclipse Dataspace Connector, EDC PostgreSQL, and HashiCorp Vault.
+    - Digital Twin Bundle: Featuring components such as the Decentral DT Registry (with “bring your own” PostgreSQL) and
+      a Submodel Server Bundle.
+    - Identity Wallet Bundle: Covering the Identity Wallet functionality.
+- Demonstration Environment: A test deployment showcasing reduced complexity and improved efficiency.
+- Basic User Guide: Instructions on how to deploy and update the PoC bundle.
+
+## 1.5 Benefits
+
+- Operational Efficiency: Faster and more reliable deployments with less manual work.
+- Scalability: A modular design that can be scaled or adapted for future full-scale deployments.
+- Ease of Adoption: Simplified deployment processes make it easier for testers and external developers to engage.
+
+## 1.6. Dependencies
+
+- Interoperability with the CATENA‑X standards.
+
+## 1.7. Success Criteria
+
+- Technology Readiness Level: Achievement of a Technology Readiness Level (TRL) of 3, as specified in the requirements.
+- Functional PoC Deployment: Demonstrated automated, modular installation with reduced manual steps.
+- Simplified Configuration: Clear evidence of reduced configuration complexity.
+- Positive Feedback: End-user validation from a select group of demo participants and the Tractus-X community.
+- Documentation Completeness: Availability of concise deployment and user guides.
+
+## 1.8. Out of Scope
+
+- Full Production Readiness: This PoC is not intended to be a production-ready solution.
+- Core Services Exclusion: Core services are not part of the Hausanschluss Bundles.
+- App Provider Role: The role of App Provider is considered out of scope for this deployment.
+- Alternative Deployment Techniques: While the evaluation of alternative deployment methods is acknowledged, the primary
+  focus remains on Kubernetes and HELM-based deployment.
+
+# 2 Requirements Analysis
+
+## 2.1 Assumptions
+
+## 2.2 Requirements Catalog
+
+| ID             | Requirement                                                                                                                                                                                                                                                                                                                                               | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | Deliverables / Acceptance Criteria                                                                                                           |
+|----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------|
+| [WP-7.1.-D001] | TAP7.1 Hausanschluss Bundle aims to simplify the installation and maintenance of the EDC and other components that together ensure a “home connection”. A flexible, parameterizable installation package is intended to reduce complexity and make integration more efficient, thereby simplifying participation in Catena‑X for additional participants. | Specification and development of a flexible, parameterizable installation package that reduces the complexity of installing and maintaining the required components for seamless integration into the Catena‑X data space. This package should facilitate updates and new versions, making participation in Catena‑X more efficient and accessible. In doing so, SMEs shall be enabled to participate without high costs or dependency on SaaS providers while maintaining control over their IT infrastructure. | [WP-7.1.-D001] Concept for the Hausanschluss is created                                                                                      |
+| 7.1.1.1        | The solution concept must define the Capability Bundles structures to be implemented. For each Capability Bundle, the included bundles and their versions are mapped.                                                                                                                                                                                     | "The following Capability Bundle structure is implemented:                                                                                                                                                                                                                                                                                                                                                                                                                                                       | "The structure of the Capability Bundles for the Enablement Services has been specified.                                                     |
+| 7.1.1.2        | Definition of Data Space Roles                                                                                                                                                                                                                                                                                                                            | Capability EDC (Data Transfer) Bundle                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | For version R24.12 it is clearly defined which Tractus‑X services and components are assigned to each Capability Bundle"                     |
+| 7.1.1.4        | Modularity & Maintainability: No dependencies between Capability Bundles                                                                                                                                                                                                                                                                                  | Eclipse Dataspace Connector (EDC) v0.9.0                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | "As part of the target group analysis, the target groups are defined and aligned with the data space roles.                                  |
+| 7.1.1.5        | Modularity & Maintainability: Concept for reducing deployment complexity                                                                                                                                                                                                                                                                                  | EDC PostgresSQL                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | Mapping from data space role to target group has been completed.                                                                             |
+| 7.1.1.6        | Modularity & Maintainability                                                                                                                                                                                                                                                                                                                              | HashiCorp Vault                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | Mapping from target group to data space role has been completed.                                                                             |
+| 7.1.1.13       | Solution Concept                                                                                                                                                                                                                                                                                                                                          | Capability Digital Twin Bundle                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | An assignment of data space roles to Capability Bundles has been made."                                                                      |
+| 7.1.1.14       | Scalability of Enablement Services                                                                                                                                                                                                                                                                                                                        | Decentral DT Registry                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | "Components and Services should obly be part of one bundle.                                                                                  |
+| 7.1.1.16       | Interoperability                                                                                                                                                                                                                                                                                                                                          | PostgresSQL                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | Each bundle must be deployable in isolation and can be installed, updated, or removed independently.                                         |
+| [WP-7.1.-D002] | [WP-7.1.-D002] Target group for the specification is defined.                                                                                                                                                                                                                                                                                             | Capability Identity & Trust (Identity Wallet Bundle)                                                                                                                                                                                                                                                                                                                                                                                                                                                             | Capability Bundles must be organized in separate HELM sub‑charts.                                                                            |
+| 7.1.2.1        | Target Group Analysis                                                                                                                                                                                                                                                                                                                                     | Identity Wallet Mock                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | Circular dependencies between bundles must be avoided."                                                                                      |
+| [WP-7.1.-D003] | [WP-7.1.-D003] Decentralized components and services defined                                                                                                                                                                                                                                                                                              | Capability Semantic Model Bundle                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | "Simplification of deployment processes                                                                                                      |
+| 7.1.3.1        | See [WP-7.1.-D001-AC001]                                                                                                                                                                                                                                                                                                                                  | Submodel Mock (aus Umbrella HELM Chart)"                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | A reduction of manual configuration steps has been achieved.                                                                                 |
+| [WP-7.1.-D004] | [WP-7.1.-D004] Documentation of the Hausanschluss Bundle is completed                                                                                                                                                                                                                                                                                     | "Data Consumer                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | Transparency and traceability                                                                                                                |
+| 7.1.4.1        | Documentation of the Hausanschluss-Bundles                                                                                                                                                                                                                                                                                                                | Data Provider                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | Clearly documented deployment steps are provided.                                                                                            |
+| 7.1.4.2        | Documentation of the Hausanschluss-Bundles                                                                                                                                                                                                                                                                                                                | Enablement Service Provider"                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | Improvements of Chart configuration by                                                                                                       |
+| [WP-7.1.-D005] | [WP-7.1.-D005] Umbrella HELM Charts for the Hausanschluss developed, tested, and documented                                                                                                                                                                                                                                                               | "Unique assignment of components and services to a defined Capability Bundle.                                                                                                                                                                                                                                                                                                                                                                                                                                    | usage of template                                                                                                                            |
+| 7.1.5.1        | Re-activate Umbrella HELM Charts to the latest release state                                                                                                                                                                                                                                                                                              | Each component and service should be assigned to only one Capability Bundle.                                                                                                                                                                                                                                                                                                                                                                                                                                     | reducing configuration options                                                                                                               |
+| 7.1.5.2        | Hierarchical structuring and bundling of Enablement Service components in the Umbrella HELM Chart                                                                                                                                                                                                                                                         | Dependencies between Capability Bundles are allowed."                                                                                                                                                                                                                                                                                                                                                                                                                                                            | reducing manual steps in the setup"                                                                                                          |
+| 7.1.5.3        | Interchangeability of bundle components via “Bring-Your-Own” components                                                                                                                                                                                                                                                                                   | The system deployment should be optimized to reduce the existing complexity. The goal is to make the provisioning process more efficient, robust, and easier to maintain.                                                                                                                                                                                                                                                                                                                                        | Charts are published via a publicly accessible charts repository.                                                                            |
+| [WP-7.1.-D006] | [WP-7.1.-D006] Product developed according to a Technology Readiness Level (TRL) of 3                                                                                                                                                                                                                                                                     | Charts are published automatically.                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | "The solution design for the ""Hausanschluss"" Bundle is created.                                                                            |
+| 7.1.6.1        | POC                                                                                                                                                                                                                                                                                                                                                       | Creation of a solution design for the “Hausanschluss” Bundle.                                                                                                                                                                                                                                                                                                                                                                                                                                                    | The solution design for the ""Hausanschluss"" Bundle ispublished in the repository: https://github.com/eclipse-tractusx/tractus-x-umbrella." |
+| 7.1.6.2        | Deployment Strategy                                                                                                                                                                                                                                                                                                                                       | Scalability of Enablement Services                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | "Developers should be able to deploy an arbitrary number of Enablement Services.                                                             |
+
+# 3 AS-IS Analysis
+
+## 3.1 People
+
+### 3.1.1 Target Group Analysis
+
+See "4.1.1 To-be Target Group Analysis" below. No deviations between As-is and To-be target groups have been identified.
+
+## 3.2 Process
+
+### 3.2.1 Use Case View (high-level)
+
+Umbrella Chart is intended for the following Use Cases:
+
+| Actor             | Use case                                                                                             |
+|-------------------|------------------------------------------------------------------------------------------------------|
+| Product Developer | Sandbox Environments: Create local environments to evaluate and experiment with Catena-X components. |
+| Product Developer | Development: Provide a unified setup for contributors and developers working on Tractus-X projects.  |
+| Product Tester    | Testing: Run end-to-end tests for Catena-X services.                                                 |
+
+## 3.4 System
+
+### 3.4.1 Context Delimitation
+
+````mermaid
+flowchart
+    subgraph "Umbrella Chart"
+        ChartYaml["Chart.yaml"]
+        subgraph charts
+            Portal["Portal"]
+            CentralIdp["CentralIdp"]
+            DiscoveryFinder["Discovery Finder"]
+            SDFactory["SD-Factory"]
+            SSICredentialIssuer["SSI Credential Issuer"]
+            SemanticHub["Semantic Hub"]
+            BPDM["BPDM"]
+            DataConsumer["Data Consumer"]
+            DataProvider["Data Provider"]
+            BDRS["BDRS"]
+            SSIWalletStub["SSI Wallet Stub"]
+        end
+        subgraph "tx-data-provider"
+            EDC["EDC"]
+            DTR["DTR"]
+            SubmodelServer["Submodel Server"]
+        end
+    end
+
+    ChartYaml --> Portal
+    ChartYaml --> CentralIdp
+    ChartYaml --> DiscoveryFinder
+    ChartYaml --> SDFactory
+    ChartYaml --> SSICredentialIssuer
+    ChartYaml --> SemanticHub
+    ChartYaml --> BPDM
+    ChartYaml --> DataConsumer
+    ChartYaml --> DataProvider
+    ChartYaml --> BDRS
+    ChartYaml --> SSIWalletStub
+    DataConsumer --> EDC
+    DataProvider --> EDC
+    DataProvider --> DTR
+    DataProvider --> SubmodelServer
+````
+
+#### Existing Umbrella Chart Structure
+
+# 4 TO-BE Design
+
+## 4.1 People
+
+### 4.1.1 Target Group Analysis
+
+Overall data space roles: https://catena-x.net/en/1/catena-x-introduce-implement/how-to-operate-catena-x
+
+The relevant data space roles for us under requirement 7.1.1.1 are:
+
+- Data Consumer
+- Data Provider
+- Enablement Service Provider
+
+Scope: Umbrella HELM Charts
+
+- Enablement Services: These services are included under the umbrella of HELM charts, focusing on enabling
+  functionalities.
+- Out of Scope: Core services such as Portal or BPDM are not considered within this scope.
+
+Primary target groups:
+
+| No. | Target group                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | Data space roles                                                    | Target group differentiation                                                                                                                                                                                                                                                                            | Behaviour, Needs, Pains & Usage                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+|-----|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| 1   | Developers<ul><li>External Developers (not Tractus-X developers): Utilize the chart for demonstration or evaluation purposes.</li><li>Experienced software and product developers who are developing a business app for a CATENA-X data space. They need to develop the app against the interfaces of the data space and integrate them accordingly.</li><li>They emphasize efficient and cost-effective implementation:<ul><li>Cost Efficiency: They do not want to use expensive SaaS solutions.</li><li>Technical Independence: They lack the knowledge and capacity to deploy the enablement and core services of the data space themselves.</li><li>Focus on Development: They concentrate on application development without delving deeply into the deployment and operation of the underlying infrastructure.</li></ul></li><li>Out of Scope: Developers running tests in test runners are not considered within this scope.</li></ul> | Data Consumer <br/> Data Provider <br/> Enablement Service Provider |                                                                                                                                                                                                                                                                                                         | <ul><li>Needs / sources of information<ul><li><a href="https://eclipse-tractusx.github.io/Kits/">Kit documentation tractus-x</a> for interaction purposes</li><li><a href="https://catenax-ev.github.io/">Catena-X doucmentation</a> for standards and regulations</li><li><a href="https://github.com/eclipse-tractusx/tractus-x-umbrella">Umbrella documentation</a> for umbrella component information</li></ul></li><li>Challenges → Solution<ul><li>Decentralization e.g. Where are other systems? How to interact with them? → Solution: Umbrella charts and bundles for deployment</li><li>Complex setup → Solution: delivery of small capability bundles</li></ul></li></ul> |
+| 2   | <ul><li>Tester requiring a test system (Testmanagement e.V.)</li><li>Requirement: Testbed</li></ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | Data Consumer <br/> Data Provider <br/> Enablement Service Provider | <ul><li>Developer (1) tests their feature.</li><li>Tester (2) performs end-to-end testing.</li><li>For the tester, the modular structure is less relevant since they focus on E2E testing, whereas the developer selects the required components.</li><li>The testbed must be easy to deploy.</li></ul> | <ul><li>Same as above from an End-to-end testing perspective</li><li>Typically a tester has less technical know-how than a developer and therefore needs a "one-size-fits-all" chart for easier testing</li></ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+
+## 4.2 Process
+
+### 4.2.1 Use Case View (high-level)
+
+| Use Case                                | Description                                                                                                       | Actors            |
+|-----------------------------------------|-------------------------------------------------------------------------------------------------------------------|-------------------|
+| Configure HELM Chart                    | The product developer configures the HELM Chart for the specific environment.                                     | Product Developer |
+| Configure Secrets                       | The product developer manages and configures secrets.                                                             | Product Developer |
+| Execute Deployment Pipeline             | The product developer successfully executes the deployment pipeline for the HELM Chart.                           | Product Developer |
+| Integrate EDC, DTR, and Identity Wallet | The actors integrate the components EDC, Digital Twin Registry, and Identity Wallet for seamless interoperability | Product Developer |
+| Set Up Connection Infrastructure        | The actor sets up the connection infrastructure for linking to the central data space infrastructure.             | Product Developer |
+| Maintain Infrastructure Module          | The product developer maintains the modular architecture of the HELM Chart.                                       | Product Developer |
+| Ensure Scalability                      | The product developer ensures scalability to support growing numbers of users and data volumes.                   | Product Developer |
+| Sandbox Environments                    | The product developer creates local environments to evaluate and experiment with Catena-X components.             | Product Developer |
+| E2E Testing                             | The product tester runs end-to-end tests for Catena-X services.                                                   | Product Tester    |
+
+### 4.2.2 Business Process (SCC Artifact)
+
+#### Chart Release Process
+
+Charts will be released using the already existing workflow in the Umbrella Chart repository. The workflow will
+automatically release a Chart, once it is pushed to the "charts/" directory with a new Chart version.
+
+#### Capability Bundle Structure
+
+Capability bundle modularization for the Tractus-X Umbrella Helm chart is a sound architectural and operational design.
+It aligns with both the domain-driven architecture of Catena-X (data exchange, digital twin, identity, semantics are
+distinct domains) and with Kubernetes best practices for managing complex applications (using an umbrella chart to
+bundle related microservices).
+
+Each bundle is self-sufficient, which improves isolation (failures or changes in one domain have minimal impact on
+others) and allows scaling and upgrading along domain lines. It simplifies deployment by allowing “plug-and-play”
+capabilities: an Enablement Service Provider can decide which bundles to operate based on its role e.g., include the
+Digital Twin and Semantic bundles if offering an asset-rich service, or omit them if not. The approach is consistent
+with how other OSS projects deliver multi-component systems, providing one-step installation without sacrificing the
+ability to tweak individual parts.
+
+Why this structure was proposed:
+
+1. **Clear Separation of Concerns**  
+   Each capability bundle (e.g. EDC Data Transfer, Digital Twin, Identity & Trust, Semantic Model) aligns with a
+   specific functional domain. This separation makes it easier to understand the role of each service (e.g., the EDC
+   connector vs. the digital twin registry), reduces coupling between unrelated components, and ultimately makes
+   maintenance and troubleshooting more straightforward.
+2. **Modular Deployment**  
+   Some participants in Catena-X may not need all services (e.g., some might not use the Digital Twin bundle). By
+   structuring the umbrella chart into bundles, a user can enable just those needed capabilities. This leads to leaner
+   installs and avoids unnecessary resource usage.
+3. **Best Practices with Helm**  
+   Using an umbrella chart with subcharts/bundles is a well-recognized Helm best practice for complex applications. It
+   allows a single helm install to set up multiple microservices while still allowing each service to have its own
+   lifecycle, configuration, and version.
+4. **Alignment with Domain-Driven Approach**  
+   Catena-X is organized around distinct, loosely-coupled “building blocks.” Bundling services by domain matches this
+   architectural vision. It’s clear which domain each set of microservices belongs to (EDC for data exchange, identity
+   for credential management, etc.). This clarity also helps new adopters navigate the ecosystem.
+
+````mermaid
+flowchart LR
+    subgraph "Core Services"
+        Vault["Vault"]
+    end
+
+    subgraph "Capability Bundle: Identity & Trust"
+        SSIWalletStub["SSI Wallet Stub"]
+    end
+
+    subgraph "Capability Bundle: Dataspace Connector"
+        EDC["EDC"]
+        EDCDB["EDC DB"]
+    end
+
+    subgraph "Capability Bundle: Digital Twin"
+        DTR["DTR"]
+        DTRDB["DTR DB"]
+    end
+
+    subgraph "Capability Bundle: Data Persitence Layer"
+        SimpleSubmodelServer["Simple Submodel Server"]
+    end
+
+    subgraph "Hausanschluss Bundles"
+        subgraph "Data Provider"
+            DataProvider["Data Provider"]
+        end
+        subgraph "Data Consumer"
+            DataConsumer["Data Consumer"]
+        end
+        subgraph "Enablement Provider"
+            EnablementProvider["Enablement Provider"]
+        end
+    end
+
+    EDC -.-> SSIWalletStub
+    EDC -.-> Vault
+    DataProvider --> EDC
+    DataProvider --> DTR
+    DataProvider --> SimpleSubmodelServer
+    DataConsumer --> EDC
+    EnablementProvider --> DataConsumer
+    EnablementProvider --> DataProvider
+
+````
+
+#### Deployment strategies
+
+##### Role: Data Provider
+
+The standard data provider role consists of a EDC, DTR and Submodel Server Bundles. EDC uses the Identity Wallet Bundle.
+
+````mermaid
+flowchart BT
+    A["Capability Bundle: Identity & Trust"]
+    B["Capability Bundle: Data Persistence Layer"]
+    C["Capability Bundle: Dataspace Connector"]
+    D["Capability Bundle: Digital Twin"]
+    E["Application to be tested/developed"]
+    E --> B
+    E --> C
+    E --> D
+    C --> A
+````
+
+##### Role: Data Consumer
+
+The standard data consumer role consists of only the EDC Bundle and the Identity Wallet Bundle.
+
+````mermaid
+flowchart BT
+    A["Capability Bundle: Identity & Trust"]
+    B["Capability Bundle: Dataspace Connector"]
+    C["Application to be tested/developed"]
+    C --> B
+    B --> A
+
+````
+
+##### Role: Enablement Provider
+
+The Enablement Provider roles consists of both the Data Consumer and Data Provider bundles. This allows provisioning of
+data and the consumtion of the provisioned data by a application.
+
+````mermaid
+flowchart BT
+    A["Capability Bundle: Identity & Trust"]
+    B["Capability Bundle: Data Persitance Layer"]
+    C["Application to be tested/developed"]
+    D["Capability Bundle: Digital Twin"]
+    E["Capability Bundle: Dataspace Connector (Provider)"]
+    F["Capability Bundle: Dataspace Connector (Consumer)"]
+    C --> B
+    C --> D
+    C --> E
+    C --> F
+    E --> A
+    F --> A
+````
+
+##### Bring you own
+
+Each Bundle can be deactivated to use your own component. This requires configuration of the component specific
+parameters in the other components.
+
+In this example this would be the configuration of the Identity Wallet within the EDC.
+
+````mermaid
+flowchart BT
+    A["Application to be tested/developed"]
+    B["Capability Bundle: Dataspace Connector"]
+    C["
Capability Bundle: Identity & Trust
"]
+    D["Own Identity Wallet"]
+    A --> B
+    B -- identitywallet - bundle . enabled = false --> C
+    B -- configure --> D
+
+````
+
+## 4.4 System
+
+### 4.4.1 Context Delimitation / 4.4.2 Interface Documentation
+
path: docs/concept/TAP7.1-solution-design.md
user: login: mkanal
body: Any kind of prosa documentation to the chart? Explaining the chart and what we will change here? 
created_at: 2025-03-28T12:22:55Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,425 @@
+# [TAP 7.1] Solution Design Hausanschluss Bundle Konzept
+
+# 1 Business Case
+
+## 1.1 Executive Summary
+
+The EDC "Hausanschluss" Bundle aims to simplify the installation of the enablement services Eclipse Dataspace
+Connector (EDC), Digital Twin Registry (DTR), and their supporting components. By developing a flexible, parameterizable
+installation package, the project seeks to reduce deployment complexity and lower barriers to participation in the
+Catena‑X data space. This bundle will enable independent component updates and support a modular "bring your own"
+approach, ultimately fostering a more efficient and accessible ecosystem for diverse participants—such as testers,
+external developers, and small and medium-sized enterprises.
+
+## 1.2 Business Need
+
+Current deployment methods for data space integration are complex and require significant manual effort. This PoC
+addresses the need to:
+
+- Reduce Complexity: Simplify the deployment topology by bundling components into capabilities.
+- Automate Deployment: Provide an automated installation package using Kubernetes and HELM.
+- Reduce Configuration Efforts: Streamline and reduce the number of configuration steps required for integration.
+- Extend Documentation: Provide a detailed documentation tailored to the target groups.
+- Enable Extension: Design the system to allow the seamless addition of new components or capabilities.
+
+## 1.3 Objectives
+
+- Simplify Deployment and Maintenance: Develop an installation package that minimizes manual configuration through
+  automation.
+- Ensure Modularity: Structure the bundle so that components can be independently installed, updated, or replaced
+  without
+  affecting other services.
+- Facilitate Flexibility: Implement a "bring your own" model for key components, such as EDC, PostgreSQL, and HashiCorp
+  Vault, to allow tailored deployments that meet specific needs.
+- Increase Accessibility: Lower entry barriers for new participants by reducing technical complexity and operational
+  dependencies.
+- Scalability: Structure the bundle so that it can be deployed multiple times.
+
+## 1.4 Expected Deliverables
+
+- PoC Documentation: A concept and architecture overview highlighting the modular design.
+- Modular Installation Package: A set of HELM charts for deploying the enablement service bundles:
+    - EDC Bundle: Including the Eclipse Dataspace Connector, EDC PostgreSQL, and HashiCorp Vault.
+    - Digital Twin Bundle: Featuring components such as the Decentral DT Registry (with “bring your own” PostgreSQL) and
+      a Submodel Server Bundle.
+    - Identity Wallet Bundle: Covering the Identity Wallet functionality.
+- Demonstration Environment: A test deployment showcasing reduced complexity and improved efficiency.
+- Basic User Guide: Instructions on how to deploy and update the PoC bundle.
+
+## 1.5 Benefits
+
+- Operational Efficiency: Faster and more reliable deployments with less manual work.
+- Scalability: A modular design that can be scaled or adapted for future full-scale deployments.
+- Ease of Adoption: Simplified deployment processes make it easier for testers and external developers to engage.
+
+## 1.6. Dependencies
+
+- Interoperability with the CATENA‑X standards.
+
+## 1.7. Success Criteria
+
+- Technology Readiness Level: Achievement of a Technology Readiness Level (TRL) of 3, as specified in the requirements.
+- Functional PoC Deployment: Demonstrated automated, modular installation with reduced manual steps.
+- Simplified Configuration: Clear evidence of reduced configuration complexity.
+- Positive Feedback: End-user validation from a select group of demo participants and the Tractus-X community.
+- Documentation Completeness: Availability of concise deployment and user guides.
+
+## 1.8. Out of Scope
+
+- Full Production Readiness: This PoC is not intended to be a production-ready solution.
+- Core Services Exclusion: Core services are not part of the Hausanschluss Bundles.
+- App Provider Role: The role of App Provider is considered out of scope for this deployment.
+- Alternative Deployment Techniques: While the evaluation of alternative deployment methods is acknowledged, the primary
+  focus remains on Kubernetes and HELM-based deployment.
+
+# 2 Requirements Analysis
+
+## 2.1 Assumptions
+
+## 2.2 Requirements Catalog
+
+| ID             | Requirement                                                                                                                                                                                                                                                                                                                                               | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | Deliverables / Acceptance Criteria                                                                                                           |
path: docs/concept/TAP7.1-solution-design.md
user: login: mkanal
body: Is this confirmed that ONLY MUST criterias are listed here?
created_at: 2025-03-28T12:23:54Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,425 @@
+# [TAP 7.1] Solution Design Hausanschluss Bundle Konzept
+
+# 1 Business Case
+
+## 1.1 Executive Summary
+
+The EDC "Hausanschluss" Bundle aims to simplify the installation of the enablement services Eclipse Dataspace
+Connector (EDC), Digital Twin Registry (DTR), and their supporting components. By developing a flexible, parameterizable
+installation package, the project seeks to reduce deployment complexity and lower barriers to participation in the
+Catena‑X data space. This bundle will enable independent component updates and support a modular "bring your own"
+approach, ultimately fostering a more efficient and accessible ecosystem for diverse participants—such as testers,
+external developers, and small and medium-sized enterprises.
+
+## 1.2 Business Need
+
+Current deployment methods for data space integration are complex and require significant manual effort. This PoC
+addresses the need to:
+
+- Reduce Complexity: Simplify the deployment topology by bundling components into capabilities.
+- Automate Deployment: Provide an automated installation package using Kubernetes and HELM.
+- Reduce Configuration Efforts: Streamline and reduce the number of configuration steps required for integration.
+- Extend Documentation: Provide a detailed documentation tailored to the target groups.
+- Enable Extension: Design the system to allow the seamless addition of new components or capabilities.
+
+## 1.3 Objectives
+
+- Simplify Deployment and Maintenance: Develop an installation package that minimizes manual configuration through
+  automation.
+- Ensure Modularity: Structure the bundle so that components can be independently installed, updated, or replaced
+  without
+  affecting other services.
+- Facilitate Flexibility: Implement a "bring your own" model for key components, such as EDC, PostgreSQL, and HashiCorp
+  Vault, to allow tailored deployments that meet specific needs.
+- Increase Accessibility: Lower entry barriers for new participants by reducing technical complexity and operational
+  dependencies.
+- Scalability: Structure the bundle so that it can be deployed multiple times.
+
+## 1.4 Expected Deliverables
+
+- PoC Documentation: A concept and architecture overview highlighting the modular design.
path: docs/concept/TAP7.1-solution-design.md
user: login: mkanal
body: I think user or developer documentation would be more clear. 
created_at: 2025-03-28T12:25:06Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,425 @@
+# [TAP 7.1] Solution Design Hausanschluss Bundle Konzept
+
+# 1 Business Case
+
+## 1.1 Executive Summary
+
+The EDC "Hausanschluss" Bundle aims to simplify the installation of the enablement services Eclipse Dataspace
+Connector (EDC), Digital Twin Registry (DTR), and their supporting components. By developing a flexible, parameterizable
+installation package, the project seeks to reduce deployment complexity and lower barriers to participation in the
+Catena‑X data space. This bundle will enable independent component updates and support a modular "bring your own"
+approach, ultimately fostering a more efficient and accessible ecosystem for diverse participants—such as testers,
+external developers, and small and medium-sized enterprises.
+
+## 1.2 Business Need
+
+Current deployment methods for data space integration are complex and require significant manual effort. This PoC
+addresses the need to:
+
+- Reduce Complexity: Simplify the deployment topology by bundling components into capabilities.
+- Automate Deployment: Provide an automated installation package using Kubernetes and HELM.
+- Reduce Configuration Efforts: Streamline and reduce the number of configuration steps required for integration.
+- Extend Documentation: Provide a detailed documentation tailored to the target groups.
+- Enable Extension: Design the system to allow the seamless addition of new components or capabilities.
+
+## 1.3 Objectives
+
+- Simplify Deployment and Maintenance: Develop an installation package that minimizes manual configuration through
+  automation.
+- Ensure Modularity: Structure the bundle so that components can be independently installed, updated, or replaced
+  without
+  affecting other services.
+- Facilitate Flexibility: Implement a "bring your own" model for key components, such as EDC, PostgreSQL, and HashiCorp
+  Vault, to allow tailored deployments that meet specific needs.
+- Increase Accessibility: Lower entry barriers for new participants by reducing technical complexity and operational
+  dependencies.
+- Scalability: Structure the bundle so that it can be deployed multiple times.
+
+## 1.4 Expected Deliverables
+
+- PoC Documentation: A concept and architecture overview highlighting the modular design.
path: docs/concept/TAP7.1-solution-design.md
user: login: mkanal
body: -> Is this document providing this service? "architecture overview highlighting the modular design"

created_at: 2025-03-28T12:25:30Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,425 @@
+# [TAP 7.1] Solution Design Hausanschluss Bundle Konzept
+
+# 1 Business Case
+
+## 1.1 Executive Summary
+
+The EDC "Hausanschluss" Bundle aims to simplify the installation of the enablement services Eclipse Dataspace
+Connector (EDC), Digital Twin Registry (DTR), and their supporting components. By developing a flexible, parameterizable
+installation package, the project seeks to reduce deployment complexity and lower barriers to participation in the
+Catena‑X data space. This bundle will enable independent component updates and support a modular "bring your own"
+approach, ultimately fostering a more efficient and accessible ecosystem for diverse participants—such as testers,
+external developers, and small and medium-sized enterprises.
+
+## 1.2 Business Need
+
+Current deployment methods for data space integration are complex and require significant manual effort. This PoC
+addresses the need to:
+
+- Reduce Complexity: Simplify the deployment topology by bundling components into capabilities.
+- Automate Deployment: Provide an automated installation package using Kubernetes and HELM.
+- Reduce Configuration Efforts: Streamline and reduce the number of configuration steps required for integration.
+- Extend Documentation: Provide a detailed documentation tailored to the target groups.
+- Enable Extension: Design the system to allow the seamless addition of new components or capabilities.
+
+## 1.3 Objectives
+
+- Simplify Deployment and Maintenance: Develop an installation package that minimizes manual configuration through
+  automation.
+- Ensure Modularity: Structure the bundle so that components can be independently installed, updated, or replaced
+  without
+  affecting other services.
+- Facilitate Flexibility: Implement a "bring your own" model for key components, such as EDC, PostgreSQL, and HashiCorp
+  Vault, to allow tailored deployments that meet specific needs.
+- Increase Accessibility: Lower entry barriers for new participants by reducing technical complexity and operational
+  dependencies.
+- Scalability: Structure the bundle so that it can be deployed multiple times.
+
+## 1.4 Expected Deliverables
+
+- PoC Documentation: A concept and architecture overview highlighting the modular design.
+- Modular Installation Package: A set of HELM charts for deploying the enablement service bundles:
+    - EDC Bundle: Including the Eclipse Dataspace Connector, EDC PostgreSQL, and HashiCorp Vault.
path: docs/concept/TAP7.1-solution-design.md
user: login: mkanal
body: Are we willing to create a HELM for the HashiCorp Vault

created_at: 2025-03-28T12:26:52Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,425 @@
+# [TAP 7.1] Solution Design Hausanschluss Bundle Konzept
+
+# 1 Business Case
+
+## 1.1 Executive Summary
+
+The EDC "Hausanschluss" Bundle aims to simplify the installation of the enablement services Eclipse Dataspace
+Connector (EDC), Digital Twin Registry (DTR), and their supporting components. By developing a flexible, parameterizable
+installation package, the project seeks to reduce deployment complexity and lower barriers to participation in the
+Catena‑X data space. This bundle will enable independent component updates and support a modular "bring your own"
+approach, ultimately fostering a more efficient and accessible ecosystem for diverse participants—such as testers,
+external developers, and small and medium-sized enterprises.
+
+## 1.2 Business Need
+
+Current deployment methods for data space integration are complex and require significant manual effort. This PoC
+addresses the need to:
+
+- Reduce Complexity: Simplify the deployment topology by bundling components into capabilities.
+- Automate Deployment: Provide an automated installation package using Kubernetes and HELM.
+- Reduce Configuration Efforts: Streamline and reduce the number of configuration steps required for integration.
+- Extend Documentation: Provide a detailed documentation tailored to the target groups.
+- Enable Extension: Design the system to allow the seamless addition of new components or capabilities.
+
+## 1.3 Objectives
+
+- Simplify Deployment and Maintenance: Develop an installation package that minimizes manual configuration through
+  automation.
+- Ensure Modularity: Structure the bundle so that components can be independently installed, updated, or replaced
+  without
+  affecting other services.
+- Facilitate Flexibility: Implement a "bring your own" model for key components, such as EDC, PostgreSQL, and HashiCorp
+  Vault, to allow tailored deployments that meet specific needs.
+- Increase Accessibility: Lower entry barriers for new participants by reducing technical complexity and operational
+  dependencies.
+- Scalability: Structure the bundle so that it can be deployed multiple times.
+
+## 1.4 Expected Deliverables
+
+- PoC Documentation: A concept and architecture overview highlighting the modular design.
+- Modular Installation Package: A set of HELM charts for deploying the enablement service bundles:
+    - EDC Bundle: Including the Eclipse Dataspace Connector, EDC PostgreSQL, and HashiCorp Vault.
+    - Digital Twin Bundle: Featuring components such as the Decentral DT Registry (with “bring your own” PostgreSQL) and
+      a Submodel Server Bundle.
+    - Identity Wallet Bundle: Covering the Identity Wallet functionality.
+- Demonstration Environment: A test deployment showcasing reduced complexity and improved efficiency.
+- Basic User Guide: Instructions on how to deploy and update the PoC bundle.
+
+## 1.5 Benefits
+
+- Operational Efficiency: Faster and more reliable deployments with less manual work.
+- Scalability: A modular design that can be scaled or adapted for future full-scale deployments.
+- Ease of Adoption: Simplified deployment processes make it easier for testers and external developers to engage.
+
+## 1.6. Dependencies
+
+- Interoperability with the CATENA‑X standards.
+
+## 1.7. Success Criteria
+
+- Technology Readiness Level: Achievement of a Technology Readiness Level (TRL) of 3, as specified in the requirements.
+- Functional PoC Deployment: Demonstrated automated, modular installation with reduced manual steps.
+- Simplified Configuration: Clear evidence of reduced configuration complexity.
+- Positive Feedback: End-user validation from a select group of demo participants and the Tractus-X community.
+- Documentation Completeness: Availability of concise deployment and user guides.
+
+## 1.8. Out of Scope
+
+- Full Production Readiness: This PoC is not intended to be a production-ready solution.
+- Core Services Exclusion: Core services are not part of the Hausanschluss Bundles.
+- App Provider Role: The role of App Provider is considered out of scope for this deployment.
+- Alternative Deployment Techniques: While the evaluation of alternative deployment methods is acknowledged, the primary
+  focus remains on Kubernetes and HELM-based deployment.
+
+# 2 Requirements Analysis
+
+## 2.1 Assumptions
+
+## 2.2 Requirements Catalog
+
+| ID             | Requirement                                                                                                                                                                                                                                                                                                                                               | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | Deliverables / Acceptance Criteria                                                                                                           |
+|----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------|
+| [WP-7.1.-D001] | TAP7.1 Hausanschluss Bundle aims to simplify the installation and maintenance of the EDC and other components that together ensure a “home connection”. A flexible, parameterizable installation package is intended to reduce complexity and make integration more efficient, thereby simplifying participation in Catena‑X for additional participants. | Specification and development of a flexible, parameterizable installation package that reduces the complexity of installing and maintaining the required components for seamless integration into the Catena‑X data space. This package should facilitate updates and new versions, making participation in Catena‑X more efficient and accessible. In doing so, SMEs shall be enabled to participate without high costs or dependency on SaaS providers while maintaining control over their IT infrastructure. | [WP-7.1.-D001] Concept for the Hausanschluss is created                                                                                      |
+| 7.1.1.1        | The solution concept must define the Capability Bundles structures to be implemented. For each Capability Bundle, the included bundles and their versions are mapped.                                                                                                                                                                                     | "The following Capability Bundle structure is implemented:                                                                                                                                                                                                                                                                                                                                                                                                                                                       | "The structure of the Capability Bundles for the Enablement Services has been specified.                                                     |
+| 7.1.1.2        | Definition of Data Space Roles                                                                                                                                                                                                                                                                                                                            | Capability EDC (Data Transfer) Bundle                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | For version R24.12 it is clearly defined which Tractus‑X services and components are assigned to each Capability Bundle"                     |
+| 7.1.1.4        | Modularity & Maintainability: No dependencies between Capability Bundles                                                                                                                                                                                                                                                                                  | Eclipse Dataspace Connector (EDC) v0.9.0                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | "As part of the target group analysis, the target groups are defined and aligned with the data space roles.                                  |
+| 7.1.1.5        | Modularity & Maintainability: Concept for reducing deployment complexity                                                                                                                                                                                                                                                                                  | EDC PostgresSQL                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | Mapping from data space role to target group has been completed.                                                                             |
+| 7.1.1.6        | Modularity & Maintainability                                                                                                                                                                                                                                                                                                                              | HashiCorp Vault                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | Mapping from target group to data space role has been completed.                                                                             |
+| 7.1.1.13       | Solution Concept                                                                                                                                                                                                                                                                                                                                          | Capability Digital Twin Bundle                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | An assignment of data space roles to Capability Bundles has been made."                                                                      |
+| 7.1.1.14       | Scalability of Enablement Services                                                                                                                                                                                                                                                                                                                        | Decentral DT Registry                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | "Components and Services should obly be part of one bundle.                                                                                  |
+| 7.1.1.16       | Interoperability                                                                                                                                                                                                                                                                                                                                          | PostgresSQL                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | Each bundle must be deployable in isolation and can be installed, updated, or removed independently.                                         |
+| [WP-7.1.-D002] | [WP-7.1.-D002] Target group for the specification is defined.                                                                                                                                                                                                                                                                                             | Capability Identity & Trust (Identity Wallet Bundle)                                                                                                                                                                                                                                                                                                                                                                                                                                                             | Capability Bundles must be organized in separate HELM sub‑charts.                                                                            |
+| 7.1.2.1        | Target Group Analysis                                                                                                                                                                                                                                                                                                                                     | Identity Wallet Mock                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | Circular dependencies between bundles must be avoided."                                                                                      |
+| [WP-7.1.-D003] | [WP-7.1.-D003] Decentralized components and services defined                                                                                                                                                                                                                                                                                              | Capability Semantic Model Bundle                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | "Simplification of deployment processes                                                                                                      |
+| 7.1.3.1        | See [WP-7.1.-D001-AC001]                                                                                                                                                                                                                                                                                                                                  | Submodel Mock (aus Umbrella HELM Chart)"                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | A reduction of manual configuration steps has been achieved.                                                                                 |
+| [WP-7.1.-D004] | [WP-7.1.-D004] Documentation of the Hausanschluss Bundle is completed                                                                                                                                                                                                                                                                                     | "Data Consumer                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | Transparency and traceability                                                                                                                |
+| 7.1.4.1        | Documentation of the Hausanschluss-Bundles                                                                                                                                                                                                                                                                                                                | Data Provider                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | Clearly documented deployment steps are provided.                                                                                            |
+| 7.1.4.2        | Documentation of the Hausanschluss-Bundles                                                                                                                                                                                                                                                                                                                | Enablement Service Provider"                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | Improvements of Chart configuration by                                                                                                       |
+| [WP-7.1.-D005] | [WP-7.1.-D005] Umbrella HELM Charts for the Hausanschluss developed, tested, and documented                                                                                                                                                                                                                                                               | "Unique assignment of components and services to a defined Capability Bundle.                                                                                                                                                                                                                                                                                                                                                                                                                                    | usage of template                                                                                                                            |
+| 7.1.5.1        | Re-activate Umbrella HELM Charts to the latest release state                                                                                                                                                                                                                                                                                              | Each component and service should be assigned to only one Capability Bundle.                                                                                                                                                                                                                                                                                                                                                                                                                                     | reducing configuration options                                                                                                               |
+| 7.1.5.2        | Hierarchical structuring and bundling of Enablement Service components in the Umbrella HELM Chart                                                                                                                                                                                                                                                         | Dependencies between Capability Bundles are allowed."                                                                                                                                                                                                                                                                                                                                                                                                                                                            | reducing manual steps in the setup"                                                                                                          |
+| 7.1.5.3        | Interchangeability of bundle components via “Bring-Your-Own” components                                                                                                                                                                                                                                                                                   | The system deployment should be optimized to reduce the existing complexity. The goal is to make the provisioning process more efficient, robust, and easier to maintain.                                                                                                                                                                                                                                                                                                                                        | Charts are published via a publicly accessible charts repository.                                                                            |
+| [WP-7.1.-D006] | [WP-7.1.-D006] Product developed according to a Technology Readiness Level (TRL) of 3                                                                                                                                                                                                                                                                     | Charts are published automatically.                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | "The solution design for the ""Hausanschluss"" Bundle is created.                                                                            |
+| 7.1.6.1        | POC                                                                                                                                                                                                                                                                                                                                                       | Creation of a solution design for the “Hausanschluss” Bundle.                                                                                                                                                                                                                                                                                                                                                                                                                                                    | The solution design for the ""Hausanschluss"" Bundle ispublished in the repository: https://github.com/eclipse-tractusx/tractus-x-umbrella." |
+| 7.1.6.2        | Deployment Strategy                                                                                                                                                                                                                                                                                                                                       | Scalability of Enablement Services                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | "Developers should be able to deploy an arbitrary number of Enablement Services.                                                             |
+
+# 3 AS-IS Analysis
+
+## 3.1 People
+
+### 3.1.1 Target Group Analysis
+
+See "4.1.1 To-be Target Group Analysis" below. No deviations between As-is and To-be target groups have been identified.
+
+## 3.2 Process
+
+### 3.2.1 Use Case View (high-level)
+
+Umbrella Chart is intended for the following Use Cases:
+
+| Actor             | Use case                                                                                             |
+|-------------------|------------------------------------------------------------------------------------------------------|
+| Product Developer | Sandbox Environments: Create local environments to evaluate and experiment with Catena-X components. |
+| Product Developer | Development: Provide a unified setup for contributors and developers working on Tractus-X projects.  |
+| Product Tester    | Testing: Run end-to-end tests for Catena-X services.                                                 |
path: docs/concept/TAP7.1-solution-design.md
user: login: mkanal
body: Product Manager is one more important Target Group we should add. Evaluating the data space .... This could be added later....
created_at: 2025-03-28T12:28:58Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,425 @@
+# [TAP 7.1] Solution Design Hausanschluss Bundle Konzept
+
+# 1 Business Case
+
+## 1.1 Executive Summary
+
+The EDC "Hausanschluss" Bundle aims to simplify the installation of the enablement services Eclipse Dataspace
+Connector (EDC), Digital Twin Registry (DTR), and their supporting components. By developing a flexible, parameterizable
+installation package, the project seeks to reduce deployment complexity and lower barriers to participation in the
+Catena‑X data space. This bundle will enable independent component updates and support a modular "bring your own"
+approach, ultimately fostering a more efficient and accessible ecosystem for diverse participants—such as testers,
+external developers, and small and medium-sized enterprises.
+
+## 1.2 Business Need
+
+Current deployment methods for data space integration are complex and require significant manual effort. This PoC
+addresses the need to:
+
+- Reduce Complexity: Simplify the deployment topology by bundling components into capabilities.
+- Automate Deployment: Provide an automated installation package using Kubernetes and HELM.
+- Reduce Configuration Efforts: Streamline and reduce the number of configuration steps required for integration.
+- Extend Documentation: Provide a detailed documentation tailored to the target groups.
+- Enable Extension: Design the system to allow the seamless addition of new components or capabilities.
+
+## 1.3 Objectives
+
+- Simplify Deployment and Maintenance: Develop an installation package that minimizes manual configuration through
+  automation.
+- Ensure Modularity: Structure the bundle so that components can be independently installed, updated, or replaced
+  without
+  affecting other services.
+- Facilitate Flexibility: Implement a "bring your own" model for key components, such as EDC, PostgreSQL, and HashiCorp
+  Vault, to allow tailored deployments that meet specific needs.
+- Increase Accessibility: Lower entry barriers for new participants by reducing technical complexity and operational
+  dependencies.
+- Scalability: Structure the bundle so that it can be deployed multiple times.
+
+## 1.4 Expected Deliverables
+
+- PoC Documentation: A concept and architecture overview highlighting the modular design.
+- Modular Installation Package: A set of HELM charts for deploying the enablement service bundles:
+    - EDC Bundle: Including the Eclipse Dataspace Connector, EDC PostgreSQL, and HashiCorp Vault.
+    - Digital Twin Bundle: Featuring components such as the Decentral DT Registry (with “bring your own” PostgreSQL) and
+      a Submodel Server Bundle.
+    - Identity Wallet Bundle: Covering the Identity Wallet functionality.
+- Demonstration Environment: A test deployment showcasing reduced complexity and improved efficiency.
+- Basic User Guide: Instructions on how to deploy and update the PoC bundle.
+
+## 1.5 Benefits
+
+- Operational Efficiency: Faster and more reliable deployments with less manual work.
+- Scalability: A modular design that can be scaled or adapted for future full-scale deployments.
+- Ease of Adoption: Simplified deployment processes make it easier for testers and external developers to engage.
+
+## 1.6. Dependencies
+
+- Interoperability with the CATENA‑X standards.
+
+## 1.7. Success Criteria
+
+- Technology Readiness Level: Achievement of a Technology Readiness Level (TRL) of 3, as specified in the requirements.
+- Functional PoC Deployment: Demonstrated automated, modular installation with reduced manual steps.
+- Simplified Configuration: Clear evidence of reduced configuration complexity.
+- Positive Feedback: End-user validation from a select group of demo participants and the Tractus-X community.
+- Documentation Completeness: Availability of concise deployment and user guides.
+
+## 1.8. Out of Scope
+
+- Full Production Readiness: This PoC is not intended to be a production-ready solution.
+- Core Services Exclusion: Core services are not part of the Hausanschluss Bundles.
+- App Provider Role: The role of App Provider is considered out of scope for this deployment.
+- Alternative Deployment Techniques: While the evaluation of alternative deployment methods is acknowledged, the primary
+  focus remains on Kubernetes and HELM-based deployment.
+
+# 2 Requirements Analysis
+
+## 2.1 Assumptions
+
+## 2.2 Requirements Catalog
+
+| ID             | Requirement                                                                                                                                                                                                                                                                                                                                               | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | Deliverables / Acceptance Criteria                                                                                                           |
+|----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------|
+| [WP-7.1.-D001] | TAP7.1 Hausanschluss Bundle aims to simplify the installation and maintenance of the EDC and other components that together ensure a “home connection”. A flexible, parameterizable installation package is intended to reduce complexity and make integration more efficient, thereby simplifying participation in Catena‑X for additional participants. | Specification and development of a flexible, parameterizable installation package that reduces the complexity of installing and maintaining the required components for seamless integration into the Catena‑X data space. This package should facilitate updates and new versions, making participation in Catena‑X more efficient and accessible. In doing so, SMEs shall be enabled to participate without high costs or dependency on SaaS providers while maintaining control over their IT infrastructure. | [WP-7.1.-D001] Concept for the Hausanschluss is created                                                                                      |
+| 7.1.1.1        | The solution concept must define the Capability Bundles structures to be implemented. For each Capability Bundle, the included bundles and their versions are mapped.                                                                                                                                                                                     | "The following Capability Bundle structure is implemented:                                                                                                                                                                                                                                                                                                                                                                                                                                                       | "The structure of the Capability Bundles for the Enablement Services has been specified.                                                     |
+| 7.1.1.2        | Definition of Data Space Roles                                                                                                                                                                                                                                                                                                                            | Capability EDC (Data Transfer) Bundle                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | For version R24.12 it is clearly defined which Tractus‑X services and components are assigned to each Capability Bundle"                     |
+| 7.1.1.4        | Modularity & Maintainability: No dependencies between Capability Bundles                                                                                                                                                                                                                                                                                  | Eclipse Dataspace Connector (EDC) v0.9.0                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | "As part of the target group analysis, the target groups are defined and aligned with the data space roles.                                  |
+| 7.1.1.5        | Modularity & Maintainability: Concept for reducing deployment complexity                                                                                                                                                                                                                                                                                  | EDC PostgresSQL                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | Mapping from data space role to target group has been completed.                                                                             |
+| 7.1.1.6        | Modularity & Maintainability                                                                                                                                                                                                                                                                                                                              | HashiCorp Vault                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | Mapping from target group to data space role has been completed.                                                                             |
+| 7.1.1.13       | Solution Concept                                                                                                                                                                                                                                                                                                                                          | Capability Digital Twin Bundle                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | An assignment of data space roles to Capability Bundles has been made."                                                                      |
+| 7.1.1.14       | Scalability of Enablement Services                                                                                                                                                                                                                                                                                                                        | Decentral DT Registry                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | "Components and Services should obly be part of one bundle.                                                                                  |
+| 7.1.1.16       | Interoperability                                                                                                                                                                                                                                                                                                                                          | PostgresSQL                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | Each bundle must be deployable in isolation and can be installed, updated, or removed independently.                                         |
+| [WP-7.1.-D002] | [WP-7.1.-D002] Target group for the specification is defined.                                                                                                                                                                                                                                                                                             | Capability Identity & Trust (Identity Wallet Bundle)                                                                                                                                                                                                                                                                                                                                                                                                                                                             | Capability Bundles must be organized in separate HELM sub‑charts.                                                                            |
+| 7.1.2.1        | Target Group Analysis                                                                                                                                                                                                                                                                                                                                     | Identity Wallet Mock                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | Circular dependencies between bundles must be avoided."                                                                                      |
+| [WP-7.1.-D003] | [WP-7.1.-D003] Decentralized components and services defined                                                                                                                                                                                                                                                                                              | Capability Semantic Model Bundle                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | "Simplification of deployment processes                                                                                                      |
+| 7.1.3.1        | See [WP-7.1.-D001-AC001]                                                                                                                                                                                                                                                                                                                                  | Submodel Mock (aus Umbrella HELM Chart)"                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | A reduction of manual configuration steps has been achieved.                                                                                 |
+| [WP-7.1.-D004] | [WP-7.1.-D004] Documentation of the Hausanschluss Bundle is completed                                                                                                                                                                                                                                                                                     | "Data Consumer                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | Transparency and traceability                                                                                                                |
+| 7.1.4.1        | Documentation of the Hausanschluss-Bundles                                                                                                                                                                                                                                                                                                                | Data Provider                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | Clearly documented deployment steps are provided.                                                                                            |
+| 7.1.4.2        | Documentation of the Hausanschluss-Bundles                                                                                                                                                                                                                                                                                                                | Enablement Service Provider"                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | Improvements of Chart configuration by                                                                                                       |
+| [WP-7.1.-D005] | [WP-7.1.-D005] Umbrella HELM Charts for the Hausanschluss developed, tested, and documented                                                                                                                                                                                                                                                               | "Unique assignment of components and services to a defined Capability Bundle.                                                                                                                                                                                                                                                                                                                                                                                                                                    | usage of template                                                                                                                            |
+| 7.1.5.1        | Re-activate Umbrella HELM Charts to the latest release state                                                                                                                                                                                                                                                                                              | Each component and service should be assigned to only one Capability Bundle.                                                                                                                                                                                                                                                                                                                                                                                                                                     | reducing configuration options                                                                                                               |
+| 7.1.5.2        | Hierarchical structuring and bundling of Enablement Service components in the Umbrella HELM Chart                                                                                                                                                                                                                                                         | Dependencies between Capability Bundles are allowed."                                                                                                                                                                                                                                                                                                                                                                                                                                                            | reducing manual steps in the setup"                                                                                                          |
+| 7.1.5.3        | Interchangeability of bundle components via “Bring-Your-Own” components                                                                                                                                                                                                                                                                                   | The system deployment should be optimized to reduce the existing complexity. The goal is to make the provisioning process more efficient, robust, and easier to maintain.                                                                                                                                                                                                                                                                                                                                        | Charts are published via a publicly accessible charts repository.                                                                            |
+| [WP-7.1.-D006] | [WP-7.1.-D006] Product developed according to a Technology Readiness Level (TRL) of 3                                                                                                                                                                                                                                                                     | Charts are published automatically.                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | "The solution design for the ""Hausanschluss"" Bundle is created.                                                                            |
+| 7.1.6.1        | POC                                                                                                                                                                                                                                                                                                                                                       | Creation of a solution design for the “Hausanschluss” Bundle.                                                                                                                                                                                                                                                                                                                                                                                                                                                    | The solution design for the ""Hausanschluss"" Bundle ispublished in the repository: https://github.com/eclipse-tractusx/tractus-x-umbrella." |
+| 7.1.6.2        | Deployment Strategy                                                                                                                                                                                                                                                                                                                                       | Scalability of Enablement Services                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | "Developers should be able to deploy an arbitrary number of Enablement Services.                                                             |
+
+# 3 AS-IS Analysis
+
+## 3.1 People
+
+### 3.1.1 Target Group Analysis
+
+See "4.1.1 To-be Target Group Analysis" below. No deviations between As-is and To-be target groups have been identified.
+
+## 3.2 Process
+
+### 3.2.1 Use Case View (high-level)
+
+Umbrella Chart is intended for the following Use Cases:
+
+| Actor             | Use case                                                                                             |
+|-------------------|------------------------------------------------------------------------------------------------------|
+| Product Developer | Sandbox Environments: Create local environments to evaluate and experiment with Catena-X components. |
+| Product Developer | Development: Provide a unified setup for contributors and developers working on Tractus-X projects.  |
+| Product Tester    | Testing: Run end-to-end tests for Catena-X services.                                                 |
+
+## 3.4 System
+
+### 3.4.1 Context Delimitation
+
+````mermaid
+flowchart
+    subgraph "Umbrella Chart"
+        ChartYaml["Chart.yaml"]
+        subgraph charts
+            Portal["Portal"]
+            CentralIdp["CentralIdp"]
+            DiscoveryFinder["Discovery Finder"]
+            SDFactory["SD-Factory"]
+            SSICredentialIssuer["SSI Credential Issuer"]
+            SemanticHub["Semantic Hub"]
+            BPDM["BPDM"]
+            DataConsumer["Data Consumer"]
+            DataProvider["Data Provider"]
+            BDRS["BDRS"]
+            SSIWalletStub["SSI Wallet Stub"]
+        end
+        subgraph "tx-data-provider"
+            EDC["EDC"]
+            DTR["DTR"]
+            SubmodelServer["Submodel Server"]
+        end
+    end
+
+    ChartYaml --> Portal
+    ChartYaml --> CentralIdp
+    ChartYaml --> DiscoveryFinder
+    ChartYaml --> SDFactory
+    ChartYaml --> SSICredentialIssuer
+    ChartYaml --> SemanticHub
+    ChartYaml --> BPDM
+    ChartYaml --> DataConsumer
+    ChartYaml --> DataProvider
+    ChartYaml --> BDRS
+    ChartYaml --> SSIWalletStub
+    DataConsumer --> EDC
+    DataProvider --> EDC
+    DataProvider --> DTR
+    DataProvider --> SubmodelServer
+````
+
+#### Existing Umbrella Chart Structure
+
+# 4 TO-BE Design
+
+## 4.1 People
+
+### 4.1.1 Target Group Analysis
+
+Overall data space roles: https://catena-x.net/en/1/catena-x-introduce-implement/how-to-operate-catena-x
+
+The relevant data space roles for us under requirement 7.1.1.1 are:
path: docs/concept/TAP7.1-solution-design.md
user: login: mkanal
body: ```suggestion
The relevant data space roles for us under requirement 7.1.1.1 are:
```
```suggestion
The relevant data space roles for TAP 7.1 are:
```
created_at: 2025-03-28T12:29:24Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,425 @@
+# [TAP 7.1] Solution Design Hausanschluss Bundle Konzept
+
+# 1 Business Case
+
+## 1.1 Executive Summary
+
+The EDC "Hausanschluss" Bundle aims to simplify the installation of the enablement services Eclipse Dataspace
+Connector (EDC), Digital Twin Registry (DTR), and their supporting components. By developing a flexible, parameterizable
+installation package, the project seeks to reduce deployment complexity and lower barriers to participation in the
+Catena‑X data space. This bundle will enable independent component updates and support a modular "bring your own"
+approach, ultimately fostering a more efficient and accessible ecosystem for diverse participants—such as testers,
+external developers, and small and medium-sized enterprises.
+
+## 1.2 Business Need
+
+Current deployment methods for data space integration are complex and require significant manual effort. This PoC
+addresses the need to:
+
+- Reduce Complexity: Simplify the deployment topology by bundling components into capabilities.
+- Automate Deployment: Provide an automated installation package using Kubernetes and HELM.
+- Reduce Configuration Efforts: Streamline and reduce the number of configuration steps required for integration.
+- Extend Documentation: Provide a detailed documentation tailored to the target groups.
+- Enable Extension: Design the system to allow the seamless addition of new components or capabilities.
+
+## 1.3 Objectives
+
+- Simplify Deployment and Maintenance: Develop an installation package that minimizes manual configuration through
+  automation.
+- Ensure Modularity: Structure the bundle so that components can be independently installed, updated, or replaced
+  without
+  affecting other services.
+- Facilitate Flexibility: Implement a "bring your own" model for key components, such as EDC, PostgreSQL, and HashiCorp
+  Vault, to allow tailored deployments that meet specific needs.
+- Increase Accessibility: Lower entry barriers for new participants by reducing technical complexity and operational
+  dependencies.
+- Scalability: Structure the bundle so that it can be deployed multiple times.
+
+## 1.4 Expected Deliverables
+
+- PoC Documentation: A concept and architecture overview highlighting the modular design.
+- Modular Installation Package: A set of HELM charts for deploying the enablement service bundles:
+    - EDC Bundle: Including the Eclipse Dataspace Connector, EDC PostgreSQL, and HashiCorp Vault.
+    - Digital Twin Bundle: Featuring components such as the Decentral DT Registry (with “bring your own” PostgreSQL) and
+      a Submodel Server Bundle.
+    - Identity Wallet Bundle: Covering the Identity Wallet functionality.
+- Demonstration Environment: A test deployment showcasing reduced complexity and improved efficiency.
+- Basic User Guide: Instructions on how to deploy and update the PoC bundle.
+
+## 1.5 Benefits
+
+- Operational Efficiency: Faster and more reliable deployments with less manual work.
+- Scalability: A modular design that can be scaled or adapted for future full-scale deployments.
+- Ease of Adoption: Simplified deployment processes make it easier for testers and external developers to engage.
+
+## 1.6. Dependencies
+
+- Interoperability with the CATENA‑X standards.
+
+## 1.7. Success Criteria
+
+- Technology Readiness Level: Achievement of a Technology Readiness Level (TRL) of 3, as specified in the requirements.
+- Functional PoC Deployment: Demonstrated automated, modular installation with reduced manual steps.
+- Simplified Configuration: Clear evidence of reduced configuration complexity.
+- Positive Feedback: End-user validation from a select group of demo participants and the Tractus-X community.
+- Documentation Completeness: Availability of concise deployment and user guides.
+
+## 1.8. Out of Scope
+
+- Full Production Readiness: This PoC is not intended to be a production-ready solution.
+- Core Services Exclusion: Core services are not part of the Hausanschluss Bundles.
+- App Provider Role: The role of App Provider is considered out of scope for this deployment.
+- Alternative Deployment Techniques: While the evaluation of alternative deployment methods is acknowledged, the primary
+  focus remains on Kubernetes and HELM-based deployment.
+
+# 2 Requirements Analysis
+
+## 2.1 Assumptions
+
+## 2.2 Requirements Catalog
+
+| ID             | Requirement                                                                                                                                                                                                                                                                                                                                               | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | Deliverables / Acceptance Criteria                                                                                                           |
+|----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------|
+| [WP-7.1.-D001] | TAP7.1 Hausanschluss Bundle aims to simplify the installation and maintenance of the EDC and other components that together ensure a “home connection”. A flexible, parameterizable installation package is intended to reduce complexity and make integration more efficient, thereby simplifying participation in Catena‑X for additional participants. | Specification and development of a flexible, parameterizable installation package that reduces the complexity of installing and maintaining the required components for seamless integration into the Catena‑X data space. This package should facilitate updates and new versions, making participation in Catena‑X more efficient and accessible. In doing so, SMEs shall be enabled to participate without high costs or dependency on SaaS providers while maintaining control over their IT infrastructure. | [WP-7.1.-D001] Concept for the Hausanschluss is created                                                                                      |
+| 7.1.1.1        | The solution concept must define the Capability Bundles structures to be implemented. For each Capability Bundle, the included bundles and their versions are mapped.                                                                                                                                                                                     | "The following Capability Bundle structure is implemented:                                                                                                                                                                                                                                                                                                                                                                                                                                                       | "The structure of the Capability Bundles for the Enablement Services has been specified.                                                     |
+| 7.1.1.2        | Definition of Data Space Roles                                                                                                                                                                                                                                                                                                                            | Capability EDC (Data Transfer) Bundle                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | For version R24.12 it is clearly defined which Tractus‑X services and components are assigned to each Capability Bundle"                     |
+| 7.1.1.4        | Modularity & Maintainability: No dependencies between Capability Bundles                                                                                                                                                                                                                                                                                  | Eclipse Dataspace Connector (EDC) v0.9.0                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | "As part of the target group analysis, the target groups are defined and aligned with the data space roles.                                  |
+| 7.1.1.5        | Modularity & Maintainability: Concept for reducing deployment complexity                                                                                                                                                                                                                                                                                  | EDC PostgresSQL                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | Mapping from data space role to target group has been completed.                                                                             |
+| 7.1.1.6        | Modularity & Maintainability                                                                                                                                                                                                                                                                                                                              | HashiCorp Vault                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | Mapping from target group to data space role has been completed.                                                                             |
+| 7.1.1.13       | Solution Concept                                                                                                                                                                                                                                                                                                                                          | Capability Digital Twin Bundle                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | An assignment of data space roles to Capability Bundles has been made."                                                                      |
+| 7.1.1.14       | Scalability of Enablement Services                                                                                                                                                                                                                                                                                                                        | Decentral DT Registry                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | "Components and Services should obly be part of one bundle.                                                                                  |
+| 7.1.1.16       | Interoperability                                                                                                                                                                                                                                                                                                                                          | PostgresSQL                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | Each bundle must be deployable in isolation and can be installed, updated, or removed independently.                                         |
+| [WP-7.1.-D002] | [WP-7.1.-D002] Target group for the specification is defined.                                                                                                                                                                                                                                                                                             | Capability Identity & Trust (Identity Wallet Bundle)                                                                                                                                                                                                                                                                                                                                                                                                                                                             | Capability Bundles must be organized in separate HELM sub‑charts.                                                                            |
+| 7.1.2.1        | Target Group Analysis                                                                                                                                                                                                                                                                                                                                     | Identity Wallet Mock                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | Circular dependencies between bundles must be avoided."                                                                                      |
+| [WP-7.1.-D003] | [WP-7.1.-D003] Decentralized components and services defined                                                                                                                                                                                                                                                                                              | Capability Semantic Model Bundle                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | "Simplification of deployment processes                                                                                                      |
+| 7.1.3.1        | See [WP-7.1.-D001-AC001]                                                                                                                                                                                                                                                                                                                                  | Submodel Mock (aus Umbrella HELM Chart)"                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | A reduction of manual configuration steps has been achieved.                                                                                 |
+| [WP-7.1.-D004] | [WP-7.1.-D004] Documentation of the Hausanschluss Bundle is completed                                                                                                                                                                                                                                                                                     | "Data Consumer                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | Transparency and traceability                                                                                                                |
+| 7.1.4.1        | Documentation of the Hausanschluss-Bundles                                                                                                                                                                                                                                                                                                                | Data Provider                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | Clearly documented deployment steps are provided.                                                                                            |
+| 7.1.4.2        | Documentation of the Hausanschluss-Bundles                                                                                                                                                                                                                                                                                                                | Enablement Service Provider"                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | Improvements of Chart configuration by                                                                                                       |
+| [WP-7.1.-D005] | [WP-7.1.-D005] Umbrella HELM Charts for the Hausanschluss developed, tested, and documented                                                                                                                                                                                                                                                               | "Unique assignment of components and services to a defined Capability Bundle.                                                                                                                                                                                                                                                                                                                                                                                                                                    | usage of template                                                                                                                            |
+| 7.1.5.1        | Re-activate Umbrella HELM Charts to the latest release state                                                                                                                                                                                                                                                                                              | Each component and service should be assigned to only one Capability Bundle.                                                                                                                                                                                                                                                                                                                                                                                                                                     | reducing configuration options                                                                                                               |
+| 7.1.5.2        | Hierarchical structuring and bundling of Enablement Service components in the Umbrella HELM Chart                                                                                                                                                                                                                                                         | Dependencies between Capability Bundles are allowed."                                                                                                                                                                                                                                                                                                                                                                                                                                                            | reducing manual steps in the setup"                                                                                                          |
+| 7.1.5.3        | Interchangeability of bundle components via “Bring-Your-Own” components                                                                                                                                                                                                                                                                                   | The system deployment should be optimized to reduce the existing complexity. The goal is to make the provisioning process more efficient, robust, and easier to maintain.                                                                                                                                                                                                                                                                                                                                        | Charts are published via a publicly accessible charts repository.                                                                            |
+| [WP-7.1.-D006] | [WP-7.1.-D006] Product developed according to a Technology Readiness Level (TRL) of 3                                                                                                                                                                                                                                                                     | Charts are published automatically.                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | "The solution design for the ""Hausanschluss"" Bundle is created.                                                                            |
+| 7.1.6.1        | POC                                                                                                                                                                                                                                                                                                                                                       | Creation of a solution design for the “Hausanschluss” Bundle.                                                                                                                                                                                                                                                                                                                                                                                                                                                    | The solution design for the ""Hausanschluss"" Bundle ispublished in the repository: https://github.com/eclipse-tractusx/tractus-x-umbrella." |
+| 7.1.6.2        | Deployment Strategy                                                                                                                                                                                                                                                                                                                                       | Scalability of Enablement Services                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | "Developers should be able to deploy an arbitrary number of Enablement Services.                                                             |
+
+# 3 AS-IS Analysis
+
+## 3.1 People
+
+### 3.1.1 Target Group Analysis
+
+See "4.1.1 To-be Target Group Analysis" below. No deviations between As-is and To-be target groups have been identified.
+
+## 3.2 Process
+
+### 3.2.1 Use Case View (high-level)
+
+Umbrella Chart is intended for the following Use Cases:
+
+| Actor             | Use case                                                                                             |
+|-------------------|------------------------------------------------------------------------------------------------------|
+| Product Developer | Sandbox Environments: Create local environments to evaluate and experiment with Catena-X components. |
+| Product Developer | Development: Provide a unified setup for contributors and developers working on Tractus-X projects.  |
+| Product Tester    | Testing: Run end-to-end tests for Catena-X services.                                                 |
+
+## 3.4 System
+
+### 3.4.1 Context Delimitation
+
+````mermaid
+flowchart
+    subgraph "Umbrella Chart"
+        ChartYaml["Chart.yaml"]
+        subgraph charts
+            Portal["Portal"]
+            CentralIdp["CentralIdp"]
+            DiscoveryFinder["Discovery Finder"]
+            SDFactory["SD-Factory"]
+            SSICredentialIssuer["SSI Credential Issuer"]
+            SemanticHub["Semantic Hub"]
+            BPDM["BPDM"]
+            DataConsumer["Data Consumer"]
+            DataProvider["Data Provider"]
+            BDRS["BDRS"]
+            SSIWalletStub["SSI Wallet Stub"]
+        end
+        subgraph "tx-data-provider"
+            EDC["EDC"]
+            DTR["DTR"]
+            SubmodelServer["Submodel Server"]
+        end
+    end
+
+    ChartYaml --> Portal
+    ChartYaml --> CentralIdp
+    ChartYaml --> DiscoveryFinder
+    ChartYaml --> SDFactory
+    ChartYaml --> SSICredentialIssuer
+    ChartYaml --> SemanticHub
+    ChartYaml --> BPDM
+    ChartYaml --> DataConsumer
+    ChartYaml --> DataProvider
+    ChartYaml --> BDRS
+    ChartYaml --> SSIWalletStub
+    DataConsumer --> EDC
+    DataProvider --> EDC
+    DataProvider --> DTR
+    DataProvider --> SubmodelServer
+````
+
+#### Existing Umbrella Chart Structure
+
+# 4 TO-BE Design
+
+## 4.1 People
+
+### 4.1.1 Target Group Analysis
+
+Overall data space roles: https://catena-x.net/en/1/catena-x-introduce-implement/how-to-operate-catena-x
+
+The relevant data space roles for us under requirement 7.1.1.1 are:
+
+- Data Consumer
+- Data Provider
+- Enablement Service Provider
+
+Scope: Umbrella HELM Charts
+
+- Enablement Services: These services are included under the umbrella of HELM charts, focusing on enabling
path: docs/concept/TAP7.1-solution-design.md
user: login: mkanal
body: This is still a mixup between in scope and out of scope. I have already addressed this with a comment.
created_at: 2025-03-28T12:30:01Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,425 @@
+# [TAP 7.1] Solution Design Hausanschluss Bundle Konzept
+
+# 1 Business Case
+
+## 1.1 Executive Summary
+
+The EDC "Hausanschluss" Bundle aims to simplify the installation of the enablement services Eclipse Dataspace
+Connector (EDC), Digital Twin Registry (DTR), and their supporting components. By developing a flexible, parameterizable
+installation package, the project seeks to reduce deployment complexity and lower barriers to participation in the
+Catena‑X data space. This bundle will enable independent component updates and support a modular "bring your own"
+approach, ultimately fostering a more efficient and accessible ecosystem for diverse participants—such as testers,
+external developers, and small and medium-sized enterprises.
+
+## 1.2 Business Need
+
+Current deployment methods for data space integration are complex and require significant manual effort. This PoC
+addresses the need to:
+
+- Reduce Complexity: Simplify the deployment topology by bundling components into capabilities.
+- Automate Deployment: Provide an automated installation package using Kubernetes and HELM.
+- Reduce Configuration Efforts: Streamline and reduce the number of configuration steps required for integration.
+- Extend Documentation: Provide a detailed documentation tailored to the target groups.
+- Enable Extension: Design the system to allow the seamless addition of new components or capabilities.
+
+## 1.3 Objectives
+
+- Simplify Deployment and Maintenance: Develop an installation package that minimizes manual configuration through
+  automation.
+- Ensure Modularity: Structure the bundle so that components can be independently installed, updated, or replaced
+  without
+  affecting other services.
+- Facilitate Flexibility: Implement a "bring your own" model for key components, such as EDC, PostgreSQL, and HashiCorp
+  Vault, to allow tailored deployments that meet specific needs.
+- Increase Accessibility: Lower entry barriers for new participants by reducing technical complexity and operational
+  dependencies.
+- Scalability: Structure the bundle so that it can be deployed multiple times.
+
+## 1.4 Expected Deliverables
+
+- PoC Documentation: A concept and architecture overview highlighting the modular design.
+- Modular Installation Package: A set of HELM charts for deploying the enablement service bundles:
+    - EDC Bundle: Including the Eclipse Dataspace Connector, EDC PostgreSQL, and HashiCorp Vault.
+    - Digital Twin Bundle: Featuring components such as the Decentral DT Registry (with “bring your own” PostgreSQL) and
+      a Submodel Server Bundle.
+    - Identity Wallet Bundle: Covering the Identity Wallet functionality.
+- Demonstration Environment: A test deployment showcasing reduced complexity and improved efficiency.
+- Basic User Guide: Instructions on how to deploy and update the PoC bundle.
+
+## 1.5 Benefits
+
+- Operational Efficiency: Faster and more reliable deployments with less manual work.
+- Scalability: A modular design that can be scaled or adapted for future full-scale deployments.
+- Ease of Adoption: Simplified deployment processes make it easier for testers and external developers to engage.
+
+## 1.6. Dependencies
+
+- Interoperability with the CATENA‑X standards.
+
+## 1.7. Success Criteria
+
+- Technology Readiness Level: Achievement of a Technology Readiness Level (TRL) of 3, as specified in the requirements.
+- Functional PoC Deployment: Demonstrated automated, modular installation with reduced manual steps.
+- Simplified Configuration: Clear evidence of reduced configuration complexity.
+- Positive Feedback: End-user validation from a select group of demo participants and the Tractus-X community.
+- Documentation Completeness: Availability of concise deployment and user guides.
+
+## 1.8. Out of Scope
+
+- Full Production Readiness: This PoC is not intended to be a production-ready solution.
+- Core Services Exclusion: Core services are not part of the Hausanschluss Bundles.
+- App Provider Role: The role of App Provider is considered out of scope for this deployment.
+- Alternative Deployment Techniques: While the evaluation of alternative deployment methods is acknowledged, the primary
+  focus remains on Kubernetes and HELM-based deployment.
+
+# 2 Requirements Analysis
+
+## 2.1 Assumptions
+
+## 2.2 Requirements Catalog
+
+| ID             | Requirement                                                                                                                                                                                                                                                                                                                                               | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | Deliverables / Acceptance Criteria                                                                                                           |
+|----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------|
+| [WP-7.1.-D001] | TAP7.1 Hausanschluss Bundle aims to simplify the installation and maintenance of the EDC and other components that together ensure a “home connection”. A flexible, parameterizable installation package is intended to reduce complexity and make integration more efficient, thereby simplifying participation in Catena‑X for additional participants. | Specification and development of a flexible, parameterizable installation package that reduces the complexity of installing and maintaining the required components for seamless integration into the Catena‑X data space. This package should facilitate updates and new versions, making participation in Catena‑X more efficient and accessible. In doing so, SMEs shall be enabled to participate without high costs or dependency on SaaS providers while maintaining control over their IT infrastructure. | [WP-7.1.-D001] Concept for the Hausanschluss is created                                                                                      |
+| 7.1.1.1        | The solution concept must define the Capability Bundles structures to be implemented. For each Capability Bundle, the included bundles and their versions are mapped.                                                                                                                                                                                     | "The following Capability Bundle structure is implemented:                                                                                                                                                                                                                                                                                                                                                                                                                                                       | "The structure of the Capability Bundles for the Enablement Services has been specified.                                                     |
+| 7.1.1.2        | Definition of Data Space Roles                                                                                                                                                                                                                                                                                                                            | Capability EDC (Data Transfer) Bundle                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | For version R24.12 it is clearly defined which Tractus‑X services and components are assigned to each Capability Bundle"                     |
+| 7.1.1.4        | Modularity & Maintainability: No dependencies between Capability Bundles                                                                                                                                                                                                                                                                                  | Eclipse Dataspace Connector (EDC) v0.9.0                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | "As part of the target group analysis, the target groups are defined and aligned with the data space roles.                                  |
+| 7.1.1.5        | Modularity & Maintainability: Concept for reducing deployment complexity                                                                                                                                                                                                                                                                                  | EDC PostgresSQL                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | Mapping from data space role to target group has been completed.                                                                             |
+| 7.1.1.6        | Modularity & Maintainability                                                                                                                                                                                                                                                                                                                              | HashiCorp Vault                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | Mapping from target group to data space role has been completed.                                                                             |
+| 7.1.1.13       | Solution Concept                                                                                                                                                                                                                                                                                                                                          | Capability Digital Twin Bundle                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | An assignment of data space roles to Capability Bundles has been made."                                                                      |
+| 7.1.1.14       | Scalability of Enablement Services                                                                                                                                                                                                                                                                                                                        | Decentral DT Registry                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | "Components and Services should obly be part of one bundle.                                                                                  |
+| 7.1.1.16       | Interoperability                                                                                                                                                                                                                                                                                                                                          | PostgresSQL                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | Each bundle must be deployable in isolation and can be installed, updated, or removed independently.                                         |
+| [WP-7.1.-D002] | [WP-7.1.-D002] Target group for the specification is defined.                                                                                                                                                                                                                                                                                             | Capability Identity & Trust (Identity Wallet Bundle)                                                                                                                                                                                                                                                                                                                                                                                                                                                             | Capability Bundles must be organized in separate HELM sub‑charts.                                                                            |
+| 7.1.2.1        | Target Group Analysis                                                                                                                                                                                                                                                                                                                                     | Identity Wallet Mock                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | Circular dependencies between bundles must be avoided."                                                                                      |
+| [WP-7.1.-D003] | [WP-7.1.-D003] Decentralized components and services defined                                                                                                                                                                                                                                                                                              | Capability Semantic Model Bundle                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | "Simplification of deployment processes                                                                                                      |
+| 7.1.3.1        | See [WP-7.1.-D001-AC001]                                                                                                                                                                                                                                                                                                                                  | Submodel Mock (aus Umbrella HELM Chart)"                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | A reduction of manual configuration steps has been achieved.                                                                                 |
+| [WP-7.1.-D004] | [WP-7.1.-D004] Documentation of the Hausanschluss Bundle is completed                                                                                                                                                                                                                                                                                     | "Data Consumer                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | Transparency and traceability                                                                                                                |
+| 7.1.4.1        | Documentation of the Hausanschluss-Bundles                                                                                                                                                                                                                                                                                                                | Data Provider                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | Clearly documented deployment steps are provided.                                                                                            |
+| 7.1.4.2        | Documentation of the Hausanschluss-Bundles                                                                                                                                                                                                                                                                                                                | Enablement Service Provider"                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | Improvements of Chart configuration by                                                                                                       |
+| [WP-7.1.-D005] | [WP-7.1.-D005] Umbrella HELM Charts for the Hausanschluss developed, tested, and documented                                                                                                                                                                                                                                                               | "Unique assignment of components and services to a defined Capability Bundle.                                                                                                                                                                                                                                                                                                                                                                                                                                    | usage of template                                                                                                                            |
+| 7.1.5.1        | Re-activate Umbrella HELM Charts to the latest release state                                                                                                                                                                                                                                                                                              | Each component and service should be assigned to only one Capability Bundle.                                                                                                                                                                                                                                                                                                                                                                                                                                     | reducing configuration options                                                                                                               |
+| 7.1.5.2        | Hierarchical structuring and bundling of Enablement Service components in the Umbrella HELM Chart                                                                                                                                                                                                                                                         | Dependencies between Capability Bundles are allowed."                                                                                                                                                                                                                                                                                                                                                                                                                                                            | reducing manual steps in the setup"                                                                                                          |
+| 7.1.5.3        | Interchangeability of bundle components via “Bring-Your-Own” components                                                                                                                                                                                                                                                                                   | The system deployment should be optimized to reduce the existing complexity. The goal is to make the provisioning process more efficient, robust, and easier to maintain.                                                                                                                                                                                                                                                                                                                                        | Charts are published via a publicly accessible charts repository.                                                                            |
+| [WP-7.1.-D006] | [WP-7.1.-D006] Product developed according to a Technology Readiness Level (TRL) of 3                                                                                                                                                                                                                                                                     | Charts are published automatically.                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | "The solution design for the ""Hausanschluss"" Bundle is created.                                                                            |
+| 7.1.6.1        | POC                                                                                                                                                                                                                                                                                                                                                       | Creation of a solution design for the “Hausanschluss” Bundle.                                                                                                                                                                                                                                                                                                                                                                                                                                                    | The solution design for the ""Hausanschluss"" Bundle ispublished in the repository: https://github.com/eclipse-tractusx/tractus-x-umbrella." |
+| 7.1.6.2        | Deployment Strategy                                                                                                                                                                                                                                                                                                                                       | Scalability of Enablement Services                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | "Developers should be able to deploy an arbitrary number of Enablement Services.                                                             |
+
+# 3 AS-IS Analysis
+
+## 3.1 People
+
+### 3.1.1 Target Group Analysis
+
+See "4.1.1 To-be Target Group Analysis" below. No deviations between As-is and To-be target groups have been identified.
+
+## 3.2 Process
+
+### 3.2.1 Use Case View (high-level)
+
+Umbrella Chart is intended for the following Use Cases:
+
+| Actor             | Use case                                                                                             |
+|-------------------|------------------------------------------------------------------------------------------------------|
+| Product Developer | Sandbox Environments: Create local environments to evaluate and experiment with Catena-X components. |
+| Product Developer | Development: Provide a unified setup for contributors and developers working on Tractus-X projects.  |
+| Product Tester    | Testing: Run end-to-end tests for Catena-X services.                                                 |
+
+## 3.4 System
+
+### 3.4.1 Context Delimitation
+
+````mermaid
+flowchart
+    subgraph "Umbrella Chart"
+        ChartYaml["Chart.yaml"]
+        subgraph charts
+            Portal["Portal"]
+            CentralIdp["CentralIdp"]
+            DiscoveryFinder["Discovery Finder"]
+            SDFactory["SD-Factory"]
+            SSICredentialIssuer["SSI Credential Issuer"]
+            SemanticHub["Semantic Hub"]
+            BPDM["BPDM"]
+            DataConsumer["Data Consumer"]
+            DataProvider["Data Provider"]
+            BDRS["BDRS"]
+            SSIWalletStub["SSI Wallet Stub"]
+        end
+        subgraph "tx-data-provider"
+            EDC["EDC"]
+            DTR["DTR"]
+            SubmodelServer["Submodel Server"]
+        end
+    end
+
+    ChartYaml --> Portal
+    ChartYaml --> CentralIdp
+    ChartYaml --> DiscoveryFinder
+    ChartYaml --> SDFactory
+    ChartYaml --> SSICredentialIssuer
+    ChartYaml --> SemanticHub
+    ChartYaml --> BPDM
+    ChartYaml --> DataConsumer
+    ChartYaml --> DataProvider
+    ChartYaml --> BDRS
+    ChartYaml --> SSIWalletStub
+    DataConsumer --> EDC
+    DataProvider --> EDC
+    DataProvider --> DTR
+    DataProvider --> SubmodelServer
+````
+
+#### Existing Umbrella Chart Structure
+
+# 4 TO-BE Design
+
+## 4.1 People
+
+### 4.1.1 Target Group Analysis
+
+Overall data space roles: https://catena-x.net/en/1/catena-x-introduce-implement/how-to-operate-catena-x
+
+The relevant data space roles for us under requirement 7.1.1.1 are:
+
+- Data Consumer
+- Data Provider
+- Enablement Service Provider
+
+Scope: Umbrella HELM Charts
+
+- Enablement Services: These services are included under the umbrella of HELM charts, focusing on enabling
+  functionalities.
+- Out of Scope: Core services such as Portal or BPDM are not considered within this scope.
+
+Primary target groups:
+
+| No. | Target group                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | Data space roles                                                    | Target group differentiation                                                                                                                                                                                                                                                                            | Behaviour, Needs, Pains & Usage                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+|-----|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| 1   | Developers<ul><li>External Developers (not Tractus-X developers): Utilize the chart for demonstration or evaluation purposes.</li><li>Experienced software and product developers who are developing a business app for a CATENA-X data space. They need to develop the app against the interfaces of the data space and integrate them accordingly.</li><li>They emphasize efficient and cost-effective implementation:<ul><li>Cost Efficiency: They do not want to use expensive SaaS solutions.</li><li>Technical Independence: They lack the knowledge and capacity to deploy the enablement and core services of the data space themselves.</li><li>Focus on Development: They concentrate on application development without delving deeply into the deployment and operation of the underlying infrastructure.</li></ul></li><li>Out of Scope: Developers running tests in test runners are not considered within this scope.</li></ul> | Data Consumer <br/> Data Provider <br/> Enablement Service Provider |                                                                                                                                                                                                                                                                                                         | <ul><li>Needs / sources of information<ul><li><a href="https://eclipse-tractusx.github.io/Kits/">Kit documentation tractus-x</a> for interaction purposes</li><li><a href="https://catenax-ev.github.io/">Catena-X doucmentation</a> for standards and regulations</li><li><a href="https://github.com/eclipse-tractusx/tractus-x-umbrella">Umbrella documentation</a> for umbrella component information</li></ul></li><li>Challenges → Solution<ul><li>Decentralization e.g. Where are other systems? How to interact with them? → Solution: Umbrella charts and bundles for deployment</li><li>Complex setup → Solution: delivery of small capability bundles</li></ul></li></ul> |
path: docs/concept/TAP7.1-solution-design.md
user: login: mkanal
body: Please avoid HTML Tags as these are not TRG conform
created_at: 2025-03-28T12:30:33Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,425 @@
+# [TAP 7.1] Solution Design Hausanschluss Bundle Konzept
+
+# 1 Business Case
+
+## 1.1 Executive Summary
+
+The EDC "Hausanschluss" Bundle aims to simplify the installation of the enablement services Eclipse Dataspace
+Connector (EDC), Digital Twin Registry (DTR), and their supporting components. By developing a flexible, parameterizable
+installation package, the project seeks to reduce deployment complexity and lower barriers to participation in the
+Catena‑X data space. This bundle will enable independent component updates and support a modular "bring your own"
+approach, ultimately fostering a more efficient and accessible ecosystem for diverse participants—such as testers,
+external developers, and small and medium-sized enterprises.
+
+## 1.2 Business Need
+
+Current deployment methods for data space integration are complex and require significant manual effort. This PoC
+addresses the need to:
+
+- Reduce Complexity: Simplify the deployment topology by bundling components into capabilities.
+- Automate Deployment: Provide an automated installation package using Kubernetes and HELM.
+- Reduce Configuration Efforts: Streamline and reduce the number of configuration steps required for integration.
+- Extend Documentation: Provide a detailed documentation tailored to the target groups.
+- Enable Extension: Design the system to allow the seamless addition of new components or capabilities.
+
+## 1.3 Objectives
+
+- Simplify Deployment and Maintenance: Develop an installation package that minimizes manual configuration through
+  automation.
+- Ensure Modularity: Structure the bundle so that components can be independently installed, updated, or replaced
+  without
+  affecting other services.
+- Facilitate Flexibility: Implement a "bring your own" model for key components, such as EDC, PostgreSQL, and HashiCorp
+  Vault, to allow tailored deployments that meet specific needs.
+- Increase Accessibility: Lower entry barriers for new participants by reducing technical complexity and operational
+  dependencies.
+- Scalability: Structure the bundle so that it can be deployed multiple times.
+
+## 1.4 Expected Deliverables
+
+- PoC Documentation: A concept and architecture overview highlighting the modular design.
+- Modular Installation Package: A set of HELM charts for deploying the enablement service bundles:
+    - EDC Bundle: Including the Eclipse Dataspace Connector, EDC PostgreSQL, and HashiCorp Vault.
+    - Digital Twin Bundle: Featuring components such as the Decentral DT Registry (with “bring your own” PostgreSQL) and
+      a Submodel Server Bundle.
+    - Identity Wallet Bundle: Covering the Identity Wallet functionality.
+- Demonstration Environment: A test deployment showcasing reduced complexity and improved efficiency.
+- Basic User Guide: Instructions on how to deploy and update the PoC bundle.
+
+## 1.5 Benefits
+
+- Operational Efficiency: Faster and more reliable deployments with less manual work.
+- Scalability: A modular design that can be scaled or adapted for future full-scale deployments.
+- Ease of Adoption: Simplified deployment processes make it easier for testers and external developers to engage.
+
+## 1.6. Dependencies
+
+- Interoperability with the CATENA‑X standards.
+
+## 1.7. Success Criteria
+
+- Technology Readiness Level: Achievement of a Technology Readiness Level (TRL) of 3, as specified in the requirements.
+- Functional PoC Deployment: Demonstrated automated, modular installation with reduced manual steps.
+- Simplified Configuration: Clear evidence of reduced configuration complexity.
+- Positive Feedback: End-user validation from a select group of demo participants and the Tractus-X community.
+- Documentation Completeness: Availability of concise deployment and user guides.
+
+## 1.8. Out of Scope
+
+- Full Production Readiness: This PoC is not intended to be a production-ready solution.
+- Core Services Exclusion: Core services are not part of the Hausanschluss Bundles.
+- App Provider Role: The role of App Provider is considered out of scope for this deployment.
+- Alternative Deployment Techniques: While the evaluation of alternative deployment methods is acknowledged, the primary
+  focus remains on Kubernetes and HELM-based deployment.
+
+# 2 Requirements Analysis
+
+## 2.1 Assumptions
+
+## 2.2 Requirements Catalog
+
+| ID             | Requirement                                                                                                                                                                                                                                                                                                                                               | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | Deliverables / Acceptance Criteria                                                                                                           |
+|----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------|
+| [WP-7.1.-D001] | TAP7.1 Hausanschluss Bundle aims to simplify the installation and maintenance of the EDC and other components that together ensure a “home connection”. A flexible, parameterizable installation package is intended to reduce complexity and make integration more efficient, thereby simplifying participation in Catena‑X for additional participants. | Specification and development of a flexible, parameterizable installation package that reduces the complexity of installing and maintaining the required components for seamless integration into the Catena‑X data space. This package should facilitate updates and new versions, making participation in Catena‑X more efficient and accessible. In doing so, SMEs shall be enabled to participate without high costs or dependency on SaaS providers while maintaining control over their IT infrastructure. | [WP-7.1.-D001] Concept for the Hausanschluss is created                                                                                      |
+| 7.1.1.1        | The solution concept must define the Capability Bundles structures to be implemented. For each Capability Bundle, the included bundles and their versions are mapped.                                                                                                                                                                                     | "The following Capability Bundle structure is implemented:                                                                                                                                                                                                                                                                                                                                                                                                                                                       | "The structure of the Capability Bundles for the Enablement Services has been specified.                                                     |
+| 7.1.1.2        | Definition of Data Space Roles                                                                                                                                                                                                                                                                                                                            | Capability EDC (Data Transfer) Bundle                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | For version R24.12 it is clearly defined which Tractus‑X services and components are assigned to each Capability Bundle"                     |
+| 7.1.1.4        | Modularity & Maintainability: No dependencies between Capability Bundles                                                                                                                                                                                                                                                                                  | Eclipse Dataspace Connector (EDC) v0.9.0                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | "As part of the target group analysis, the target groups are defined and aligned with the data space roles.                                  |
+| 7.1.1.5        | Modularity & Maintainability: Concept for reducing deployment complexity                                                                                                                                                                                                                                                                                  | EDC PostgresSQL                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | Mapping from data space role to target group has been completed.                                                                             |
+| 7.1.1.6        | Modularity & Maintainability                                                                                                                                                                                                                                                                                                                              | HashiCorp Vault                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | Mapping from target group to data space role has been completed.                                                                             |
+| 7.1.1.13       | Solution Concept                                                                                                                                                                                                                                                                                                                                          | Capability Digital Twin Bundle                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | An assignment of data space roles to Capability Bundles has been made."                                                                      |
+| 7.1.1.14       | Scalability of Enablement Services                                                                                                                                                                                                                                                                                                                        | Decentral DT Registry                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | "Components and Services should obly be part of one bundle.                                                                                  |
+| 7.1.1.16       | Interoperability                                                                                                                                                                                                                                                                                                                                          | PostgresSQL                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | Each bundle must be deployable in isolation and can be installed, updated, or removed independently.                                         |
+| [WP-7.1.-D002] | [WP-7.1.-D002] Target group for the specification is defined.                                                                                                                                                                                                                                                                                             | Capability Identity & Trust (Identity Wallet Bundle)                                                                                                                                                                                                                                                                                                                                                                                                                                                             | Capability Bundles must be organized in separate HELM sub‑charts.                                                                            |
+| 7.1.2.1        | Target Group Analysis                                                                                                                                                                                                                                                                                                                                     | Identity Wallet Mock                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | Circular dependencies between bundles must be avoided."                                                                                      |
+| [WP-7.1.-D003] | [WP-7.1.-D003] Decentralized components and services defined                                                                                                                                                                                                                                                                                              | Capability Semantic Model Bundle                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | "Simplification of deployment processes                                                                                                      |
+| 7.1.3.1        | See [WP-7.1.-D001-AC001]                                                                                                                                                                                                                                                                                                                                  | Submodel Mock (aus Umbrella HELM Chart)"                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | A reduction of manual configuration steps has been achieved.                                                                                 |
+| [WP-7.1.-D004] | [WP-7.1.-D004] Documentation of the Hausanschluss Bundle is completed                                                                                                                                                                                                                                                                                     | "Data Consumer                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | Transparency and traceability                                                                                                                |
+| 7.1.4.1        | Documentation of the Hausanschluss-Bundles                                                                                                                                                                                                                                                                                                                | Data Provider                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | Clearly documented deployment steps are provided.                                                                                            |
+| 7.1.4.2        | Documentation of the Hausanschluss-Bundles                                                                                                                                                                                                                                                                                                                | Enablement Service Provider"                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | Improvements of Chart configuration by                                                                                                       |
+| [WP-7.1.-D005] | [WP-7.1.-D005] Umbrella HELM Charts for the Hausanschluss developed, tested, and documented                                                                                                                                                                                                                                                               | "Unique assignment of components and services to a defined Capability Bundle.                                                                                                                                                                                                                                                                                                                                                                                                                                    | usage of template                                                                                                                            |
+| 7.1.5.1        | Re-activate Umbrella HELM Charts to the latest release state                                                                                                                                                                                                                                                                                              | Each component and service should be assigned to only one Capability Bundle.                                                                                                                                                                                                                                                                                                                                                                                                                                     | reducing configuration options                                                                                                               |
+| 7.1.5.2        | Hierarchical structuring and bundling of Enablement Service components in the Umbrella HELM Chart                                                                                                                                                                                                                                                         | Dependencies between Capability Bundles are allowed."                                                                                                                                                                                                                                                                                                                                                                                                                                                            | reducing manual steps in the setup"                                                                                                          |
+| 7.1.5.3        | Interchangeability of bundle components via “Bring-Your-Own” components                                                                                                                                                                                                                                                                                   | The system deployment should be optimized to reduce the existing complexity. The goal is to make the provisioning process more efficient, robust, and easier to maintain.                                                                                                                                                                                                                                                                                                                                        | Charts are published via a publicly accessible charts repository.                                                                            |
+| [WP-7.1.-D006] | [WP-7.1.-D006] Product developed according to a Technology Readiness Level (TRL) of 3                                                                                                                                                                                                                                                                     | Charts are published automatically.                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | "The solution design for the ""Hausanschluss"" Bundle is created.                                                                            |
+| 7.1.6.1        | POC                                                                                                                                                                                                                                                                                                                                                       | Creation of a solution design for the “Hausanschluss” Bundle.                                                                                                                                                                                                                                                                                                                                                                                                                                                    | The solution design for the ""Hausanschluss"" Bundle ispublished in the repository: https://github.com/eclipse-tractusx/tractus-x-umbrella." |
+| 7.1.6.2        | Deployment Strategy                                                                                                                                                                                                                                                                                                                                       | Scalability of Enablement Services                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | "Developers should be able to deploy an arbitrary number of Enablement Services.                                                             |
+
+# 3 AS-IS Analysis
+
+## 3.1 People
+
+### 3.1.1 Target Group Analysis
+
+See "4.1.1 To-be Target Group Analysis" below. No deviations between As-is and To-be target groups have been identified.
+
+## 3.2 Process
+
+### 3.2.1 Use Case View (high-level)
+
+Umbrella Chart is intended for the following Use Cases:
+
+| Actor             | Use case                                                                                             |
+|-------------------|------------------------------------------------------------------------------------------------------|
+| Product Developer | Sandbox Environments: Create local environments to evaluate and experiment with Catena-X components. |
+| Product Developer | Development: Provide a unified setup for contributors and developers working on Tractus-X projects.  |
+| Product Tester    | Testing: Run end-to-end tests for Catena-X services.                                                 |
+
+## 3.4 System
+
+### 3.4.1 Context Delimitation
+
+````mermaid
+flowchart
+    subgraph "Umbrella Chart"
+        ChartYaml["Chart.yaml"]
+        subgraph charts
+            Portal["Portal"]
+            CentralIdp["CentralIdp"]
+            DiscoveryFinder["Discovery Finder"]
+            SDFactory["SD-Factory"]
+            SSICredentialIssuer["SSI Credential Issuer"]
+            SemanticHub["Semantic Hub"]
+            BPDM["BPDM"]
+            DataConsumer["Data Consumer"]
+            DataProvider["Data Provider"]
+            BDRS["BDRS"]
+            SSIWalletStub["SSI Wallet Stub"]
+        end
+        subgraph "tx-data-provider"
+            EDC["EDC"]
+            DTR["DTR"]
+            SubmodelServer["Submodel Server"]
+        end
+    end
+
+    ChartYaml --> Portal
+    ChartYaml --> CentralIdp
+    ChartYaml --> DiscoveryFinder
+    ChartYaml --> SDFactory
+    ChartYaml --> SSICredentialIssuer
+    ChartYaml --> SemanticHub
+    ChartYaml --> BPDM
+    ChartYaml --> DataConsumer
+    ChartYaml --> DataProvider
+    ChartYaml --> BDRS
+    ChartYaml --> SSIWalletStub
+    DataConsumer --> EDC
+    DataProvider --> EDC
+    DataProvider --> DTR
+    DataProvider --> SubmodelServer
+````
+
+#### Existing Umbrella Chart Structure
+
+# 4 TO-BE Design
+
+## 4.1 People
+
+### 4.1.1 Target Group Analysis
+
+Overall data space roles: https://catena-x.net/en/1/catena-x-introduce-implement/how-to-operate-catena-x
+
+The relevant data space roles for us under requirement 7.1.1.1 are:
+
+- Data Consumer
+- Data Provider
+- Enablement Service Provider
+
+Scope: Umbrella HELM Charts
+
+- Enablement Services: These services are included under the umbrella of HELM charts, focusing on enabling
+  functionalities.
+- Out of Scope: Core services such as Portal or BPDM are not considered within this scope.
+
+Primary target groups:
+
+| No. | Target group                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | Data space roles                                                    | Target group differentiation                                                                                                                                                                                                                                                                            | Behaviour, Needs, Pains & Usage                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+|-----|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| 1   | Developers<ul><li>External Developers (not Tractus-X developers): Utilize the chart for demonstration or evaluation purposes.</li><li>Experienced software and product developers who are developing a business app for a CATENA-X data space. They need to develop the app against the interfaces of the data space and integrate them accordingly.</li><li>They emphasize efficient and cost-effective implementation:<ul><li>Cost Efficiency: They do not want to use expensive SaaS solutions.</li><li>Technical Independence: They lack the knowledge and capacity to deploy the enablement and core services of the data space themselves.</li><li>Focus on Development: They concentrate on application development without delving deeply into the deployment and operation of the underlying infrastructure.</li></ul></li><li>Out of Scope: Developers running tests in test runners are not considered within this scope.</li></ul> | Data Consumer <br/> Data Provider <br/> Enablement Service Provider |                                                                                                                                                                                                                                                                                                         | <ul><li>Needs / sources of information<ul><li><a href="https://eclipse-tractusx.github.io/Kits/">Kit documentation tractus-x</a> for interaction purposes</li><li><a href="https://catenax-ev.github.io/">Catena-X doucmentation</a> for standards and regulations</li><li><a href="https://github.com/eclipse-tractusx/tractus-x-umbrella">Umbrella documentation</a> for umbrella component information</li></ul></li><li>Challenges → Solution<ul><li>Decentralization e.g. Where are other systems? How to interact with them? → Solution: Umbrella charts and bundles for deployment</li><li>Complex setup → Solution: delivery of small capability bundles</li></ul></li></ul> |
+| 2   | <ul><li>Tester requiring a test system (Testmanagement e.V.)</li><li>Requirement: Testbed</li></ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | Data Consumer <br/> Data Provider <br/> Enablement Service Provider | <ul><li>Developer (1) tests their feature.</li><li>Tester (2) performs end-to-end testing.</li><li>For the tester, the modular structure is less relevant since they focus on E2E testing, whereas the developer selects the required components.</li><li>The testbed must be easy to deploy.</li></ul> | <ul><li>Same as above from an End-to-end testing perspective</li><li>Typically a tester has less technical know-how than a developer and therefore needs a "one-size-fits-all" chart for easier testing</li></ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+
+## 4.2 Process
+
+### 4.2.1 Use Case View (high-level)
+
+| Use Case                                | Description                                                                                                       | Actors            |
+|-----------------------------------------|-------------------------------------------------------------------------------------------------------------------|-------------------|
+| Configure HELM Chart                    | The product developer configures the HELM Chart for the specific environment.                                     | Product Developer |
+| Configure Secrets                       | The product developer manages and configures secrets.                                                             | Product Developer |
+| Execute Deployment Pipeline             | The product developer successfully executes the deployment pipeline for the HELM Chart.                           | Product Developer |
+| Integrate EDC, DTR, and Identity Wallet | The actors integrate the components EDC, Digital Twin Registry, and Identity Wallet for seamless interoperability | Product Developer |
+| Set Up Connection Infrastructure        | The actor sets up the connection infrastructure for linking to the central data space infrastructure.             | Product Developer |
+| Maintain Infrastructure Module          | The product developer maintains the modular architecture of the HELM Chart.                                       | Product Developer |
+| Ensure Scalability                      | The product developer ensures scalability to support growing numbers of users and data volumes.                   | Product Developer |
+| Sandbox Environments                    | The product developer creates local environments to evaluate and experiment with Catena-X components.             | Product Developer |
+| E2E Testing                             | The product tester runs end-to-end tests for Catena-X services.                                                   | Product Tester    |
+
+### 4.2.2 Business Process (SCC Artifact)
+
+#### Chart Release Process
+
+Charts will be released using the already existing workflow in the Umbrella Chart repository. The workflow will
+automatically release a Chart, once it is pushed to the "charts/" directory with a new Chart version.
path: docs/concept/TAP7.1-solution-design.md
user: login: mkanal
body: Any more detail info how this is versioned or why. 
created_at: 2025-03-28T12:31:57Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,425 @@
+# [TAP 7.1] Solution Design Hausanschluss Bundle Konzept
+
+# 1 Business Case
+
+## 1.1 Executive Summary
+
+The EDC "Hausanschluss" Bundle aims to simplify the installation of the enablement services Eclipse Dataspace
+Connector (EDC), Digital Twin Registry (DTR), and their supporting components. By developing a flexible, parameterizable
+installation package, the project seeks to reduce deployment complexity and lower barriers to participation in the
+Catena‑X data space. This bundle will enable independent component updates and support a modular "bring your own"
+approach, ultimately fostering a more efficient and accessible ecosystem for diverse participants—such as testers,
+external developers, and small and medium-sized enterprises.
+
+## 1.2 Business Need
+
+Current deployment methods for data space integration are complex and require significant manual effort. This PoC
+addresses the need to:
+
+- Reduce Complexity: Simplify the deployment topology by bundling components into capabilities.
+- Automate Deployment: Provide an automated installation package using Kubernetes and HELM.
+- Reduce Configuration Efforts: Streamline and reduce the number of configuration steps required for integration.
+- Extend Documentation: Provide a detailed documentation tailored to the target groups.
+- Enable Extension: Design the system to allow the seamless addition of new components or capabilities.
+
+## 1.3 Objectives
+
+- Simplify Deployment and Maintenance: Develop an installation package that minimizes manual configuration through
+  automation.
+- Ensure Modularity: Structure the bundle so that components can be independently installed, updated, or replaced
+  without
+  affecting other services.
+- Facilitate Flexibility: Implement a "bring your own" model for key components, such as EDC, PostgreSQL, and HashiCorp
+  Vault, to allow tailored deployments that meet specific needs.
+- Increase Accessibility: Lower entry barriers for new participants by reducing technical complexity and operational
+  dependencies.
+- Scalability: Structure the bundle so that it can be deployed multiple times.
+
+## 1.4 Expected Deliverables
+
+- PoC Documentation: A concept and architecture overview highlighting the modular design.
+- Modular Installation Package: A set of HELM charts for deploying the enablement service bundles:
+    - EDC Bundle: Including the Eclipse Dataspace Connector, EDC PostgreSQL, and HashiCorp Vault.
+    - Digital Twin Bundle: Featuring components such as the Decentral DT Registry (with “bring your own” PostgreSQL) and
+      a Submodel Server Bundle.
+    - Identity Wallet Bundle: Covering the Identity Wallet functionality.
+- Demonstration Environment: A test deployment showcasing reduced complexity and improved efficiency.
+- Basic User Guide: Instructions on how to deploy and update the PoC bundle.
+
+## 1.5 Benefits
+
+- Operational Efficiency: Faster and more reliable deployments with less manual work.
+- Scalability: A modular design that can be scaled or adapted for future full-scale deployments.
+- Ease of Adoption: Simplified deployment processes make it easier for testers and external developers to engage.
+
+## 1.6. Dependencies
+
+- Interoperability with the CATENA‑X standards.
+
+## 1.7. Success Criteria
+
+- Technology Readiness Level: Achievement of a Technology Readiness Level (TRL) of 3, as specified in the requirements.
+- Functional PoC Deployment: Demonstrated automated, modular installation with reduced manual steps.
+- Simplified Configuration: Clear evidence of reduced configuration complexity.
+- Positive Feedback: End-user validation from a select group of demo participants and the Tractus-X community.
+- Documentation Completeness: Availability of concise deployment and user guides.
+
+## 1.8. Out of Scope
+
+- Full Production Readiness: This PoC is not intended to be a production-ready solution.
+- Core Services Exclusion: Core services are not part of the Hausanschluss Bundles.
+- App Provider Role: The role of App Provider is considered out of scope for this deployment.
+- Alternative Deployment Techniques: While the evaluation of alternative deployment methods is acknowledged, the primary
+  focus remains on Kubernetes and HELM-based deployment.
+
+# 2 Requirements Analysis
+
+## 2.1 Assumptions
+
+## 2.2 Requirements Catalog
+
+| ID             | Requirement                                                                                                                                                                                                                                                                                                                                               | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | Deliverables / Acceptance Criteria                                                                                                           |
+|----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------|
+| [WP-7.1.-D001] | TAP7.1 Hausanschluss Bundle aims to simplify the installation and maintenance of the EDC and other components that together ensure a “home connection”. A flexible, parameterizable installation package is intended to reduce complexity and make integration more efficient, thereby simplifying participation in Catena‑X for additional participants. | Specification and development of a flexible, parameterizable installation package that reduces the complexity of installing and maintaining the required components for seamless integration into the Catena‑X data space. This package should facilitate updates and new versions, making participation in Catena‑X more efficient and accessible. In doing so, SMEs shall be enabled to participate without high costs or dependency on SaaS providers while maintaining control over their IT infrastructure. | [WP-7.1.-D001] Concept for the Hausanschluss is created                                                                                      |
+| 7.1.1.1        | The solution concept must define the Capability Bundles structures to be implemented. For each Capability Bundle, the included bundles and their versions are mapped.                                                                                                                                                                                     | "The following Capability Bundle structure is implemented:                                                                                                                                                                                                                                                                                                                                                                                                                                                       | "The structure of the Capability Bundles for the Enablement Services has been specified.                                                     |
+| 7.1.1.2        | Definition of Data Space Roles                                                                                                                                                                                                                                                                                                                            | Capability EDC (Data Transfer) Bundle                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | For version R24.12 it is clearly defined which Tractus‑X services and components are assigned to each Capability Bundle"                     |
+| 7.1.1.4        | Modularity & Maintainability: No dependencies between Capability Bundles                                                                                                                                                                                                                                                                                  | Eclipse Dataspace Connector (EDC) v0.9.0                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | "As part of the target group analysis, the target groups are defined and aligned with the data space roles.                                  |
+| 7.1.1.5        | Modularity & Maintainability: Concept for reducing deployment complexity                                                                                                                                                                                                                                                                                  | EDC PostgresSQL                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | Mapping from data space role to target group has been completed.                                                                             |
+| 7.1.1.6        | Modularity & Maintainability                                                                                                                                                                                                                                                                                                                              | HashiCorp Vault                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | Mapping from target group to data space role has been completed.                                                                             |
+| 7.1.1.13       | Solution Concept                                                                                                                                                                                                                                                                                                                                          | Capability Digital Twin Bundle                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | An assignment of data space roles to Capability Bundles has been made."                                                                      |
+| 7.1.1.14       | Scalability of Enablement Services                                                                                                                                                                                                                                                                                                                        | Decentral DT Registry                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | "Components and Services should obly be part of one bundle.                                                                                  |
+| 7.1.1.16       | Interoperability                                                                                                                                                                                                                                                                                                                                          | PostgresSQL                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | Each bundle must be deployable in isolation and can be installed, updated, or removed independently.                                         |
+| [WP-7.1.-D002] | [WP-7.1.-D002] Target group for the specification is defined.                                                                                                                                                                                                                                                                                             | Capability Identity & Trust (Identity Wallet Bundle)                                                                                                                                                                                                                                                                                                                                                                                                                                                             | Capability Bundles must be organized in separate HELM sub‑charts.                                                                            |
+| 7.1.2.1        | Target Group Analysis                                                                                                                                                                                                                                                                                                                                     | Identity Wallet Mock                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | Circular dependencies between bundles must be avoided."                                                                                      |
+| [WP-7.1.-D003] | [WP-7.1.-D003] Decentralized components and services defined                                                                                                                                                                                                                                                                                              | Capability Semantic Model Bundle                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | "Simplification of deployment processes                                                                                                      |
+| 7.1.3.1        | See [WP-7.1.-D001-AC001]                                                                                                                                                                                                                                                                                                                                  | Submodel Mock (aus Umbrella HELM Chart)"                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | A reduction of manual configuration steps has been achieved.                                                                                 |
+| [WP-7.1.-D004] | [WP-7.1.-D004] Documentation of the Hausanschluss Bundle is completed                                                                                                                                                                                                                                                                                     | "Data Consumer                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | Transparency and traceability                                                                                                                |
+| 7.1.4.1        | Documentation of the Hausanschluss-Bundles                                                                                                                                                                                                                                                                                                                | Data Provider                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | Clearly documented deployment steps are provided.                                                                                            |
+| 7.1.4.2        | Documentation of the Hausanschluss-Bundles                                                                                                                                                                                                                                                                                                                | Enablement Service Provider"                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | Improvements of Chart configuration by                                                                                                       |
+| [WP-7.1.-D005] | [WP-7.1.-D005] Umbrella HELM Charts for the Hausanschluss developed, tested, and documented                                                                                                                                                                                                                                                               | "Unique assignment of components and services to a defined Capability Bundle.                                                                                                                                                                                                                                                                                                                                                                                                                                    | usage of template                                                                                                                            |
+| 7.1.5.1        | Re-activate Umbrella HELM Charts to the latest release state                                                                                                                                                                                                                                                                                              | Each component and service should be assigned to only one Capability Bundle.                                                                                                                                                                                                                                                                                                                                                                                                                                     | reducing configuration options                                                                                                               |
+| 7.1.5.2        | Hierarchical structuring and bundling of Enablement Service components in the Umbrella HELM Chart                                                                                                                                                                                                                                                         | Dependencies between Capability Bundles are allowed."                                                                                                                                                                                                                                                                                                                                                                                                                                                            | reducing manual steps in the setup"                                                                                                          |
+| 7.1.5.3        | Interchangeability of bundle components via “Bring-Your-Own” components                                                                                                                                                                                                                                                                                   | The system deployment should be optimized to reduce the existing complexity. The goal is to make the provisioning process more efficient, robust, and easier to maintain.                                                                                                                                                                                                                                                                                                                                        | Charts are published via a publicly accessible charts repository.                                                                            |
+| [WP-7.1.-D006] | [WP-7.1.-D006] Product developed according to a Technology Readiness Level (TRL) of 3                                                                                                                                                                                                                                                                     | Charts are published automatically.                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | "The solution design for the ""Hausanschluss"" Bundle is created.                                                                            |
+| 7.1.6.1        | POC                                                                                                                                                                                                                                                                                                                                                       | Creation of a solution design for the “Hausanschluss” Bundle.                                                                                                                                                                                                                                                                                                                                                                                                                                                    | The solution design for the ""Hausanschluss"" Bundle ispublished in the repository: https://github.com/eclipse-tractusx/tractus-x-umbrella." |
+| 7.1.6.2        | Deployment Strategy                                                                                                                                                                                                                                                                                                                                       | Scalability of Enablement Services                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | "Developers should be able to deploy an arbitrary number of Enablement Services.                                                             |
+
+# 3 AS-IS Analysis
+
+## 3.1 People
+
+### 3.1.1 Target Group Analysis
+
+See "4.1.1 To-be Target Group Analysis" below. No deviations between As-is and To-be target groups have been identified.
+
+## 3.2 Process
+
+### 3.2.1 Use Case View (high-level)
+
+Umbrella Chart is intended for the following Use Cases:
+
+| Actor             | Use case                                                                                             |
+|-------------------|------------------------------------------------------------------------------------------------------|
+| Product Developer | Sandbox Environments: Create local environments to evaluate and experiment with Catena-X components. |
+| Product Developer | Development: Provide a unified setup for contributors and developers working on Tractus-X projects.  |
+| Product Tester    | Testing: Run end-to-end tests for Catena-X services.                                                 |
+
+## 3.4 System
+
+### 3.4.1 Context Delimitation
+
+````mermaid
+flowchart
+    subgraph "Umbrella Chart"
+        ChartYaml["Chart.yaml"]
+        subgraph charts
+            Portal["Portal"]
+            CentralIdp["CentralIdp"]
+            DiscoveryFinder["Discovery Finder"]
+            SDFactory["SD-Factory"]
+            SSICredentialIssuer["SSI Credential Issuer"]
+            SemanticHub["Semantic Hub"]
+            BPDM["BPDM"]
+            DataConsumer["Data Consumer"]
+            DataProvider["Data Provider"]
+            BDRS["BDRS"]
+            SSIWalletStub["SSI Wallet Stub"]
+        end
+        subgraph "tx-data-provider"
+            EDC["EDC"]
+            DTR["DTR"]
+            SubmodelServer["Submodel Server"]
+        end
+    end
+
+    ChartYaml --> Portal
+    ChartYaml --> CentralIdp
+    ChartYaml --> DiscoveryFinder
+    ChartYaml --> SDFactory
+    ChartYaml --> SSICredentialIssuer
+    ChartYaml --> SemanticHub
+    ChartYaml --> BPDM
+    ChartYaml --> DataConsumer
+    ChartYaml --> DataProvider
+    ChartYaml --> BDRS
+    ChartYaml --> SSIWalletStub
+    DataConsumer --> EDC
+    DataProvider --> EDC
+    DataProvider --> DTR
+    DataProvider --> SubmodelServer
+````
+
+#### Existing Umbrella Chart Structure
+
+# 4 TO-BE Design
+
+## 4.1 People
+
+### 4.1.1 Target Group Analysis
+
+Overall data space roles: https://catena-x.net/en/1/catena-x-introduce-implement/how-to-operate-catena-x
+
+The relevant data space roles for us under requirement 7.1.1.1 are:
+
+- Data Consumer
+- Data Provider
+- Enablement Service Provider
+
+Scope: Umbrella HELM Charts
+
+- Enablement Services: These services are included under the umbrella of HELM charts, focusing on enabling
+  functionalities.
+- Out of Scope: Core services such as Portal or BPDM are not considered within this scope.
+
+Primary target groups:
+
+| No. | Target group                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | Data space roles                                                    | Target group differentiation                                                                                                                                                                                                                                                                            | Behaviour, Needs, Pains & Usage                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+|-----|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| 1   | Developers<ul><li>External Developers (not Tractus-X developers): Utilize the chart for demonstration or evaluation purposes.</li><li>Experienced software and product developers who are developing a business app for a CATENA-X data space. They need to develop the app against the interfaces of the data space and integrate them accordingly.</li><li>They emphasize efficient and cost-effective implementation:<ul><li>Cost Efficiency: They do not want to use expensive SaaS solutions.</li><li>Technical Independence: They lack the knowledge and capacity to deploy the enablement and core services of the data space themselves.</li><li>Focus on Development: They concentrate on application development without delving deeply into the deployment and operation of the underlying infrastructure.</li></ul></li><li>Out of Scope: Developers running tests in test runners are not considered within this scope.</li></ul> | Data Consumer <br/> Data Provider <br/> Enablement Service Provider |                                                                                                                                                                                                                                                                                                         | <ul><li>Needs / sources of information<ul><li><a href="https://eclipse-tractusx.github.io/Kits/">Kit documentation tractus-x</a> for interaction purposes</li><li><a href="https://catenax-ev.github.io/">Catena-X doucmentation</a> for standards and regulations</li><li><a href="https://github.com/eclipse-tractusx/tractus-x-umbrella">Umbrella documentation</a> for umbrella component information</li></ul></li><li>Challenges → Solution<ul><li>Decentralization e.g. Where are other systems? How to interact with them? → Solution: Umbrella charts and bundles for deployment</li><li>Complex setup → Solution: delivery of small capability bundles</li></ul></li></ul> |
+| 2   | <ul><li>Tester requiring a test system (Testmanagement e.V.)</li><li>Requirement: Testbed</li></ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | Data Consumer <br/> Data Provider <br/> Enablement Service Provider | <ul><li>Developer (1) tests their feature.</li><li>Tester (2) performs end-to-end testing.</li><li>For the tester, the modular structure is less relevant since they focus on E2E testing, whereas the developer selects the required components.</li><li>The testbed must be easy to deploy.</li></ul> | <ul><li>Same as above from an End-to-end testing perspective</li><li>Typically a tester has less technical know-how than a developer and therefore needs a "one-size-fits-all" chart for easier testing</li></ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+
+## 4.2 Process
+
+### 4.2.1 Use Case View (high-level)
+
+| Use Case                                | Description                                                                                                       | Actors            |
path: docs/concept/TAP7.1-solution-design.md
user: login: mkanal
body: ## Gruppe 1: Produktentwickler

| ID  | Name                                      | Akteur            | Beschreibung |
|-----|-------------------------------------------|-------------------|--------------|
| UC1 | Configure HELM Chart                      | Product Developer | The product developer configures the HELM Chart for the specific environment. |
| UC2 | Configure Secrets                         | Product Developer | The product developer manages and configures secrets. |
| UC3 | Execute Deployment Pipeline               | Product Developer | The product developer successfully executes the deployment pipeline for the HELM Chart. |
| UC4 | Integrate EDC, DTR, and Identity Wallet   | Product Developer | The actors integrate the components EDC, Digital Twin Registry, and Identity Wallet for seamless interoperability. |
| UC5 | Set Up Connection Infrastructure         | Product Developer | The actor sets up the connection infrastructure for linking to the central data space infrastructure. |
| UC6 | Maintain Infrastructure Module            | Product Developer | The product developer maintains the modular architecture of the HELM Chart. |
| UC7 | Ensure Scalability                        | Product Developer | The product developer ensures scalability to support growing numbers of users and data volumes. |
| UC8 | Sandbox Environments                      | Product Developer | The product developer creates local environments to evaluate and experiment with Catena-X components. |

## Gruppe 2: Produkttester

| ID  | Name          | Actor         | Description|
|-----|--------------|---------------|--------------|
| UC9 | E2E Testing | Product Tester | The product tester runs end-to-end tests for Catena-X services. |

created_at: 2025-03-28T12:35:21Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,425 @@
+# [TAP 7.1] Solution Design Hausanschluss Bundle Konzept
+
+# 1 Business Case
+
+## 1.1 Executive Summary
+
+The EDC "Hausanschluss" Bundle aims to simplify the installation of the enablement services Eclipse Dataspace
+Connector (EDC), Digital Twin Registry (DTR), and their supporting components. By developing a flexible, parameterizable
+installation package, the project seeks to reduce deployment complexity and lower barriers to participation in the
+Catena‑X data space. This bundle will enable independent component updates and support a modular "bring your own"
+approach, ultimately fostering a more efficient and accessible ecosystem for diverse participants—such as testers,
+external developers, and small and medium-sized enterprises.
+
+## 1.2 Business Need
+
+Current deployment methods for data space integration are complex and require significant manual effort. This PoC
+addresses the need to:
+
+- Reduce Complexity: Simplify the deployment topology by bundling components into capabilities.
+- Automate Deployment: Provide an automated installation package using Kubernetes and HELM.
+- Reduce Configuration Efforts: Streamline and reduce the number of configuration steps required for integration.
+- Extend Documentation: Provide a detailed documentation tailored to the target groups.
+- Enable Extension: Design the system to allow the seamless addition of new components or capabilities.
+
+## 1.3 Objectives
+
+- Simplify Deployment and Maintenance: Develop an installation package that minimizes manual configuration through
+  automation.
+- Ensure Modularity: Structure the bundle so that components can be independently installed, updated, or replaced
+  without
+  affecting other services.
+- Facilitate Flexibility: Implement a "bring your own" model for key components, such as EDC, PostgreSQL, and HashiCorp
+  Vault, to allow tailored deployments that meet specific needs.
+- Increase Accessibility: Lower entry barriers for new participants by reducing technical complexity and operational
+  dependencies.
+- Scalability: Structure the bundle so that it can be deployed multiple times.
+
+## 1.4 Expected Deliverables
+
+- PoC Documentation: A concept and architecture overview highlighting the modular design.
+- Modular Installation Package: A set of HELM charts for deploying the enablement service bundles:
+    - EDC Bundle: Including the Eclipse Dataspace Connector, EDC PostgreSQL, and HashiCorp Vault.
+    - Digital Twin Bundle: Featuring components such as the Decentral DT Registry (with “bring your own” PostgreSQL) and
+      a Submodel Server Bundle.
+    - Identity Wallet Bundle: Covering the Identity Wallet functionality.
+- Demonstration Environment: A test deployment showcasing reduced complexity and improved efficiency.
+- Basic User Guide: Instructions on how to deploy and update the PoC bundle.
+
+## 1.5 Benefits
+
+- Operational Efficiency: Faster and more reliable deployments with less manual work.
+- Scalability: A modular design that can be scaled or adapted for future full-scale deployments.
+- Ease of Adoption: Simplified deployment processes make it easier for testers and external developers to engage.
+
+## 1.6. Dependencies
+
+- Interoperability with the CATENA‑X standards.
+
+## 1.7. Success Criteria
+
+- Technology Readiness Level: Achievement of a Technology Readiness Level (TRL) of 3, as specified in the requirements.
+- Functional PoC Deployment: Demonstrated automated, modular installation with reduced manual steps.
+- Simplified Configuration: Clear evidence of reduced configuration complexity.
+- Positive Feedback: End-user validation from a select group of demo participants and the Tractus-X community.
+- Documentation Completeness: Availability of concise deployment and user guides.
+
+## 1.8. Out of Scope
+
+- Full Production Readiness: This PoC is not intended to be a production-ready solution.
+- Core Services Exclusion: Core services are not part of the Hausanschluss Bundles.
+- App Provider Role: The role of App Provider is considered out of scope for this deployment.
+- Alternative Deployment Techniques: While the evaluation of alternative deployment methods is acknowledged, the primary
+  focus remains on Kubernetes and HELM-based deployment.
+
+# 2 Requirements Analysis
+
+## 2.1 Assumptions
+
+## 2.2 Requirements Catalog
+
+| ID             | Requirement                                                                                                                                                                                                                                                                                                                                               | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | Deliverables / Acceptance Criteria                                                                                                           |
+|----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------|
+| [WP-7.1.-D001] | TAP7.1 Hausanschluss Bundle aims to simplify the installation and maintenance of the EDC and other components that together ensure a “home connection”. A flexible, parameterizable installation package is intended to reduce complexity and make integration more efficient, thereby simplifying participation in Catena‑X for additional participants. | Specification and development of a flexible, parameterizable installation package that reduces the complexity of installing and maintaining the required components for seamless integration into the Catena‑X data space. This package should facilitate updates and new versions, making participation in Catena‑X more efficient and accessible. In doing so, SMEs shall be enabled to participate without high costs or dependency on SaaS providers while maintaining control over their IT infrastructure. | [WP-7.1.-D001] Concept for the Hausanschluss is created                                                                                      |
+| 7.1.1.1        | The solution concept must define the Capability Bundles structures to be implemented. For each Capability Bundle, the included bundles and their versions are mapped.                                                                                                                                                                                     | "The following Capability Bundle structure is implemented:                                                                                                                                                                                                                                                                                                                                                                                                                                                       | "The structure of the Capability Bundles for the Enablement Services has been specified.                                                     |
+| 7.1.1.2        | Definition of Data Space Roles                                                                                                                                                                                                                                                                                                                            | Capability EDC (Data Transfer) Bundle                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | For version R24.12 it is clearly defined which Tractus‑X services and components are assigned to each Capability Bundle"                     |
+| 7.1.1.4        | Modularity & Maintainability: No dependencies between Capability Bundles                                                                                                                                                                                                                                                                                  | Eclipse Dataspace Connector (EDC) v0.9.0                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | "As part of the target group analysis, the target groups are defined and aligned with the data space roles.                                  |
+| 7.1.1.5        | Modularity & Maintainability: Concept for reducing deployment complexity                                                                                                                                                                                                                                                                                  | EDC PostgresSQL                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | Mapping from data space role to target group has been completed.                                                                             |
+| 7.1.1.6        | Modularity & Maintainability                                                                                                                                                                                                                                                                                                                              | HashiCorp Vault                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | Mapping from target group to data space role has been completed.                                                                             |
+| 7.1.1.13       | Solution Concept                                                                                                                                                                                                                                                                                                                                          | Capability Digital Twin Bundle                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | An assignment of data space roles to Capability Bundles has been made."                                                                      |
+| 7.1.1.14       | Scalability of Enablement Services                                                                                                                                                                                                                                                                                                                        | Decentral DT Registry                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | "Components and Services should obly be part of one bundle.                                                                                  |
+| 7.1.1.16       | Interoperability                                                                                                                                                                                                                                                                                                                                          | PostgresSQL                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | Each bundle must be deployable in isolation and can be installed, updated, or removed independently.                                         |
+| [WP-7.1.-D002] | [WP-7.1.-D002] Target group for the specification is defined.                                                                                                                                                                                                                                                                                             | Capability Identity & Trust (Identity Wallet Bundle)                                                                                                                                                                                                                                                                                                                                                                                                                                                             | Capability Bundles must be organized in separate HELM sub‑charts.                                                                            |
+| 7.1.2.1        | Target Group Analysis                                                                                                                                                                                                                                                                                                                                     | Identity Wallet Mock                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | Circular dependencies between bundles must be avoided."                                                                                      |
+| [WP-7.1.-D003] | [WP-7.1.-D003] Decentralized components and services defined                                                                                                                                                                                                                                                                                              | Capability Semantic Model Bundle                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | "Simplification of deployment processes                                                                                                      |
+| 7.1.3.1        | See [WP-7.1.-D001-AC001]                                                                                                                                                                                                                                                                                                                                  | Submodel Mock (aus Umbrella HELM Chart)"                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | A reduction of manual configuration steps has been achieved.                                                                                 |
+| [WP-7.1.-D004] | [WP-7.1.-D004] Documentation of the Hausanschluss Bundle is completed                                                                                                                                                                                                                                                                                     | "Data Consumer                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | Transparency and traceability                                                                                                                |
+| 7.1.4.1        | Documentation of the Hausanschluss-Bundles                                                                                                                                                                                                                                                                                                                | Data Provider                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | Clearly documented deployment steps are provided.                                                                                            |
+| 7.1.4.2        | Documentation of the Hausanschluss-Bundles                                                                                                                                                                                                                                                                                                                | Enablement Service Provider"                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | Improvements of Chart configuration by                                                                                                       |
+| [WP-7.1.-D005] | [WP-7.1.-D005] Umbrella HELM Charts for the Hausanschluss developed, tested, and documented                                                                                                                                                                                                                                                               | "Unique assignment of components and services to a defined Capability Bundle.                                                                                                                                                                                                                                                                                                                                                                                                                                    | usage of template                                                                                                                            |
+| 7.1.5.1        | Re-activate Umbrella HELM Charts to the latest release state                                                                                                                                                                                                                                                                                              | Each component and service should be assigned to only one Capability Bundle.                                                                                                                                                                                                                                                                                                                                                                                                                                     | reducing configuration options                                                                                                               |
+| 7.1.5.2        | Hierarchical structuring and bundling of Enablement Service components in the Umbrella HELM Chart                                                                                                                                                                                                                                                         | Dependencies between Capability Bundles are allowed."                                                                                                                                                                                                                                                                                                                                                                                                                                                            | reducing manual steps in the setup"                                                                                                          |
+| 7.1.5.3        | Interchangeability of bundle components via “Bring-Your-Own” components                                                                                                                                                                                                                                                                                   | The system deployment should be optimized to reduce the existing complexity. The goal is to make the provisioning process more efficient, robust, and easier to maintain.                                                                                                                                                                                                                                                                                                                                        | Charts are published via a publicly accessible charts repository.                                                                            |
+| [WP-7.1.-D006] | [WP-7.1.-D006] Product developed according to a Technology Readiness Level (TRL) of 3                                                                                                                                                                                                                                                                     | Charts are published automatically.                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | "The solution design for the ""Hausanschluss"" Bundle is created.                                                                            |
+| 7.1.6.1        | POC                                                                                                                                                                                                                                                                                                                                                       | Creation of a solution design for the “Hausanschluss” Bundle.                                                                                                                                                                                                                                                                                                                                                                                                                                                    | The solution design for the ""Hausanschluss"" Bundle ispublished in the repository: https://github.com/eclipse-tractusx/tractus-x-umbrella." |
+| 7.1.6.2        | Deployment Strategy                                                                                                                                                                                                                                                                                                                                       | Scalability of Enablement Services                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | "Developers should be able to deploy an arbitrary number of Enablement Services.                                                             |
+
+# 3 AS-IS Analysis
+
+## 3.1 People
+
+### 3.1.1 Target Group Analysis
+
+See "4.1.1 To-be Target Group Analysis" below. No deviations between As-is and To-be target groups have been identified.
+
+## 3.2 Process
+
+### 3.2.1 Use Case View (high-level)
+
+Umbrella Chart is intended for the following Use Cases:
+
+| Actor             | Use case                                                                                             |
+|-------------------|------------------------------------------------------------------------------------------------------|
+| Product Developer | Sandbox Environments: Create local environments to evaluate and experiment with Catena-X components. |
+| Product Developer | Development: Provide a unified setup for contributors and developers working on Tractus-X projects.  |
+| Product Tester    | Testing: Run end-to-end tests for Catena-X services.                                                 |
+
+## 3.4 System
+
+### 3.4.1 Context Delimitation
+
+````mermaid
+flowchart
+    subgraph "Umbrella Chart"
+        ChartYaml["Chart.yaml"]
+        subgraph charts
+            Portal["Portal"]
+            CentralIdp["CentralIdp"]
+            DiscoveryFinder["Discovery Finder"]
+            SDFactory["SD-Factory"]
+            SSICredentialIssuer["SSI Credential Issuer"]
+            SemanticHub["Semantic Hub"]
+            BPDM["BPDM"]
+            DataConsumer["Data Consumer"]
+            DataProvider["Data Provider"]
+            BDRS["BDRS"]
+            SSIWalletStub["SSI Wallet Stub"]
+        end
+        subgraph "tx-data-provider"
+            EDC["EDC"]
+            DTR["DTR"]
+            SubmodelServer["Submodel Server"]
+        end
+    end
+
+    ChartYaml --> Portal
+    ChartYaml --> CentralIdp
+    ChartYaml --> DiscoveryFinder
+    ChartYaml --> SDFactory
+    ChartYaml --> SSICredentialIssuer
+    ChartYaml --> SemanticHub
+    ChartYaml --> BPDM
+    ChartYaml --> DataConsumer
+    ChartYaml --> DataProvider
+    ChartYaml --> BDRS
+    ChartYaml --> SSIWalletStub
+    DataConsumer --> EDC
+    DataProvider --> EDC
+    DataProvider --> DTR
+    DataProvider --> SubmodelServer
+````
+
+#### Existing Umbrella Chart Structure
+
+# 4 TO-BE Design
+
+## 4.1 People
+
+### 4.1.1 Target Group Analysis
+
+Overall data space roles: https://catena-x.net/en/1/catena-x-introduce-implement/how-to-operate-catena-x
+
+The relevant data space roles for us under requirement 7.1.1.1 are:
+
+- Data Consumer
+- Data Provider
+- Enablement Service Provider
+
+Scope: Umbrella HELM Charts
+
+- Enablement Services: These services are included under the umbrella of HELM charts, focusing on enabling
+  functionalities.
+- Out of Scope: Core services such as Portal or BPDM are not considered within this scope.
+
+Primary target groups:
+
+| No. | Target group                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | Data space roles                                                    | Target group differentiation                                                                                                                                                                                                                                                                            | Behaviour, Needs, Pains & Usage                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+|-----|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| 1   | Developers<ul><li>External Developers (not Tractus-X developers): Utilize the chart for demonstration or evaluation purposes.</li><li>Experienced software and product developers who are developing a business app for a CATENA-X data space. They need to develop the app against the interfaces of the data space and integrate them accordingly.</li><li>They emphasize efficient and cost-effective implementation:<ul><li>Cost Efficiency: They do not want to use expensive SaaS solutions.</li><li>Technical Independence: They lack the knowledge and capacity to deploy the enablement and core services of the data space themselves.</li><li>Focus on Development: They concentrate on application development without delving deeply into the deployment and operation of the underlying infrastructure.</li></ul></li><li>Out of Scope: Developers running tests in test runners are not considered within this scope.</li></ul> | Data Consumer <br/> Data Provider <br/> Enablement Service Provider |                                                                                                                                                                                                                                                                                                         | <ul><li>Needs / sources of information<ul><li><a href="https://eclipse-tractusx.github.io/Kits/">Kit documentation tractus-x</a> for interaction purposes</li><li><a href="https://catenax-ev.github.io/">Catena-X doucmentation</a> for standards and regulations</li><li><a href="https://github.com/eclipse-tractusx/tractus-x-umbrella">Umbrella documentation</a> for umbrella component information</li></ul></li><li>Challenges → Solution<ul><li>Decentralization e.g. Where are other systems? How to interact with them? → Solution: Umbrella charts and bundles for deployment</li><li>Complex setup → Solution: delivery of small capability bundles</li></ul></li></ul> |
+| 2   | <ul><li>Tester requiring a test system (Testmanagement e.V.)</li><li>Requirement: Testbed</li></ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | Data Consumer <br/> Data Provider <br/> Enablement Service Provider | <ul><li>Developer (1) tests their feature.</li><li>Tester (2) performs end-to-end testing.</li><li>For the tester, the modular structure is less relevant since they focus on E2E testing, whereas the developer selects the required components.</li><li>The testbed must be easy to deploy.</li></ul> | <ul><li>Same as above from an End-to-end testing perspective</li><li>Typically a tester has less technical know-how than a developer and therefore needs a "one-size-fits-all" chart for easier testing</li></ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+
+## 4.2 Process
+
+### 4.2.1 Use Case View (high-level)
+
+| Use Case                                | Description                                                                                                       | Actors            |
+|-----------------------------------------|-------------------------------------------------------------------------------------------------------------------|-------------------|
+| Configure HELM Chart                    | The product developer configures the HELM Chart for the specific environment.                                     | Product Developer |
+| Configure Secrets                       | The product developer manages and configures secrets.                                                             | Product Developer |
+| Execute Deployment Pipeline             | The product developer successfully executes the deployment pipeline for the HELM Chart.                           | Product Developer |
+| Integrate EDC, DTR, and Identity Wallet | The actors integrate the components EDC, Digital Twin Registry, and Identity Wallet for seamless interoperability | Product Developer |
+| Set Up Connection Infrastructure        | The actor sets up the connection infrastructure for linking to the central data space infrastructure.             | Product Developer |
+| Maintain Infrastructure Module          | The product developer maintains the modular architecture of the HELM Chart.                                       | Product Developer |
+| Ensure Scalability                      | The product developer ensures scalability to support growing numbers of users and data volumes.                   | Product Developer |
+| Sandbox Environments                    | The product developer creates local environments to evaluate and experiment with Catena-X components.             | Product Developer |
+| E2E Testing                             | The product tester runs end-to-end tests for Catena-X services.                                                   | Product Tester    |
+
path: docs/concept/TAP7.1-solution-design.md
user: login: mkanal
body: %%{init: {'theme': 'base', 'themeVariables': {'actorBorder':'#C6C6C6', 'actorBkg':'#C6C6C6', 'actorTextColor': '#000', 'primaryTextColor': '#000', 'edgeLabelBackground':'#f5f5f5', 'tertiaryColor': '#D7E9F4', 'tertiaryBorderColor': '#181818', 'tertiaryTextColor': '#000'}}}%%
usecaseDiagram
    actor "Product Developer" as PD
    actor "Product Tester" as PT

    rectangle UC {
        usecase UC1 as "Configure HELM Chart"
        usecase UC2 as "Configure Secrets"
        usecase UC3 as "Execute Deployment Pipeline"
        usecase UC4 as "Integrate EDC, DTR, and Identity Wallet"
        usecase UC5 as "Set Up Connection Infrastructure"
        usecase UC6 as "Maintain Infrastructure Module"
        usecase UC7 as "Ensure Scalability"
        usecase UC8 as "Sandbox Environments"
        usecase UC9 as "E2E Testing"
    }

    PD --> UC1
    PD --> UC2
    PD --> UC3
    PD --> UC4
    PD --> UC5
    PD --> UC6
    PD --> UC7
    PD --> UC8
    PT --> UC9
created_at: 2025-03-28T12:36:13Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,425 @@
+# [TAP 7.1] Solution Design Hausanschluss Bundle Konzept
+
+# 1 Business Case
+
+## 1.1 Executive Summary
+
+The EDC "Hausanschluss" Bundle aims to simplify the installation of the enablement services Eclipse Dataspace
path: docs/concept/TAP7.1-solution-design.md
user: login: ds-jhartmann
body: thats the usual markdown formatting
created_at: 2025-03-28T12:50:35Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,425 @@
+# [TAP 7.1] Solution Design Hausanschluss Bundle Konzept
+
+# 1 Business Case
+
+## 1.1 Executive Summary
+
+The EDC "Hausanschluss" Bundle aims to simplify the installation of the enablement services Eclipse Dataspace
+Connector (EDC), Digital Twin Registry (DTR), and their supporting components. By developing a flexible, parameterizable
+installation package, the project seeks to reduce deployment complexity and lower barriers to participation in the
+Catena‑X data space. This bundle will enable independent component updates and support a modular "bring your own"
+approach, ultimately fostering a more efficient and accessible ecosystem for diverse participants—such as testers,
+external developers, and small and medium-sized enterprises.
+
+## 1.2 Business Need
+
+Current deployment methods for data space integration are complex and require significant manual effort. This PoC
+addresses the need to:
+
+- Reduce Complexity: Simplify the deployment topology by bundling components into capabilities.
+- Automate Deployment: Provide an automated installation package using Kubernetes and HELM.
+- Reduce Configuration Efforts: Streamline and reduce the number of configuration steps required for integration.
+- Extend Documentation: Provide a detailed documentation tailored to the target groups.
+- Enable Extension: Design the system to allow the seamless addition of new components or capabilities.
+
+## 1.3 Objectives
+
+- Simplify Deployment and Maintenance: Develop an installation package that minimizes manual configuration through
+  automation.
+- Ensure Modularity: Structure the bundle so that components can be independently installed, updated, or replaced
+  without
+  affecting other services.
+- Facilitate Flexibility: Implement a "bring your own" model for key components, such as EDC, PostgreSQL, and HashiCorp
path: docs/concept/TAP7.1-solution-design.md
user: login: ds-jhartmann
body: thats in the next line
created_at: 2025-03-28T12:51:37Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,425 @@
+# [TAP 7.1] Solution Design Hausanschluss Bundle Konzept
+
+# 1 Business Case
+
+## 1.1 Executive Summary
+
+The EDC "Hausanschluss" Bundle aims to simplify the installation of the enablement services Eclipse Dataspace
+Connector (EDC), Digital Twin Registry (DTR), and their supporting components. By developing a flexible, parameterizable
+installation package, the project seeks to reduce deployment complexity and lower barriers to participation in the
+Catena‑X data space. This bundle will enable independent component updates and support a modular "bring your own"
+approach, ultimately fostering a more efficient and accessible ecosystem for diverse participants—such as testers,
+external developers, and small and medium-sized enterprises.
+
+## 1.2 Business Need
+
+Current deployment methods for data space integration are complex and require significant manual effort. This PoC
+addresses the need to:
+
+- Reduce Complexity: Simplify the deployment topology by bundling components into capabilities.
+- Automate Deployment: Provide an automated installation package using Kubernetes and HELM.
+- Reduce Configuration Efforts: Streamline and reduce the number of configuration steps required for integration.
+- Extend Documentation: Provide a detailed documentation tailored to the target groups.
+- Enable Extension: Design the system to allow the seamless addition of new components or capabilities.
+
+## 1.3 Objectives
+
+- Simplify Deployment and Maintenance: Develop an installation package that minimizes manual configuration through
+  automation.
+- Ensure Modularity: Structure the bundle so that components can be independently installed, updated, or replaced
+  without
+  affecting other services.
+- Facilitate Flexibility: Implement a "bring your own" model for key components, such as EDC, PostgreSQL, and HashiCorp
+  Vault, to allow tailored deployments that meet specific needs.
+- Increase Accessibility: Lower entry barriers for new participants by reducing technical complexity and operational
+  dependencies.
+- Scalability: Structure the bundle so that it can be deployed multiple times.
+
+## 1.4 Expected Deliverables
+
+- PoC Documentation: A concept and architecture overview highlighting the modular design.
+- Modular Installation Package: A set of HELM charts for deploying the enablement service bundles:
+    - EDC Bundle: Including the Eclipse Dataspace Connector, EDC PostgreSQL, and HashiCorp Vault.
+    - Digital Twin Bundle: Featuring components such as the Decentral DT Registry (with “bring your own” PostgreSQL) and
+      a Submodel Server Bundle.
+    - Identity Wallet Bundle: Covering the Identity Wallet functionality.
+- Demonstration Environment: A test deployment showcasing reduced complexity and improved efficiency.
+- Basic User Guide: Instructions on how to deploy and update the PoC bundle.
+
+## 1.5 Benefits
+
+- Operational Efficiency: Faster and more reliable deployments with less manual work.
+- Scalability: A modular design that can be scaled or adapted for future full-scale deployments.
+- Ease of Adoption: Simplified deployment processes make it easier for testers and external developers to engage.
+
+## 1.6. Dependencies
+
+- Interoperability with the CATENA‑X standards.
+
+## 1.7. Success Criteria
+
+- Technology Readiness Level: Achievement of a Technology Readiness Level (TRL) of 3, as specified in the requirements.
+- Functional PoC Deployment: Demonstrated automated, modular installation with reduced manual steps.
+- Simplified Configuration: Clear evidence of reduced configuration complexity.
+- Positive Feedback: End-user validation from a select group of demo participants and the Tractus-X community.
+- Documentation Completeness: Availability of concise deployment and user guides.
+
+## 1.8. Out of Scope
+
+- Full Production Readiness: This PoC is not intended to be a production-ready solution.
+- Core Services Exclusion: Core services are not part of the Hausanschluss Bundles.
+- App Provider Role: The role of App Provider is considered out of scope for this deployment.
+- Alternative Deployment Techniques: While the evaluation of alternative deployment methods is acknowledged, the primary
+  focus remains on Kubernetes and HELM-based deployment.
+
+# 2 Requirements Analysis
+
+## 2.1 Assumptions
+
+## 2.2 Requirements Catalog
+
+| ID             | Requirement                                                                                                                                                                                                                                                                                                                                               | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | Deliverables / Acceptance Criteria                                                                                                           |
path: docs/concept/TAP7.1-solution-design.md
user: login: ds-jhartmann
body: yes, these are all the must criterias
created_at: 2025-03-28T12:52:26Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,425 @@
+# [TAP 7.1] Solution Design Hausanschluss Bundle Konzept
+
+# 1 Business Case
+
+## 1.1 Executive Summary
+
+The EDC "Hausanschluss" Bundle aims to simplify the installation of the enablement services Eclipse Dataspace
+Connector (EDC), Digital Twin Registry (DTR), and their supporting components. By developing a flexible, parameterizable
+installation package, the project seeks to reduce deployment complexity and lower barriers to participation in the
+Catena‑X data space. This bundle will enable independent component updates and support a modular "bring your own"
+approach, ultimately fostering a more efficient and accessible ecosystem for diverse participants—such as testers,
+external developers, and small and medium-sized enterprises.
+
+## 1.2 Business Need
+
+Current deployment methods for data space integration are complex and require significant manual effort. This PoC
+addresses the need to:
+
+- Reduce Complexity: Simplify the deployment topology by bundling components into capabilities.
+- Automate Deployment: Provide an automated installation package using Kubernetes and HELM.
+- Reduce Configuration Efforts: Streamline and reduce the number of configuration steps required for integration.
+- Extend Documentation: Provide a detailed documentation tailored to the target groups.
+- Enable Extension: Design the system to allow the seamless addition of new components or capabilities.
+
+## 1.3 Objectives
+
+- Simplify Deployment and Maintenance: Develop an installation package that minimizes manual configuration through
+  automation.
+- Ensure Modularity: Structure the bundle so that components can be independently installed, updated, or replaced
+  without
+  affecting other services.
+- Facilitate Flexibility: Implement a "bring your own" model for key components, such as EDC, PostgreSQL, and HashiCorp
+  Vault, to allow tailored deployments that meet specific needs.
+- Increase Accessibility: Lower entry barriers for new participants by reducing technical complexity and operational
+  dependencies.
+- Scalability: Structure the bundle so that it can be deployed multiple times.
+
+## 1.4 Expected Deliverables
+
+- PoC Documentation: A concept and architecture overview highlighting the modular design.
+- Modular Installation Package: A set of HELM charts for deploying the enablement service bundles:
+    - EDC Bundle: Including the Eclipse Dataspace Connector, EDC PostgreSQL, and HashiCorp Vault.
path: docs/concept/TAP7.1-solution-design.md
user: login: ds-jhartmann
body: no, there is no need for that. The table was not migrated correctly which lead to some missleading content. This is now fixed
created_at: 2025-03-28T12:53:31Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,425 @@
+# [TAP 7.1] Solution Design Hausanschluss Bundle Konzept
+
+# 1 Business Case
+
+## 1.1 Executive Summary
+
+The EDC "Hausanschluss" Bundle aims to simplify the installation of the enablement services Eclipse Dataspace
+Connector (EDC), Digital Twin Registry (DTR), and their supporting components. By developing a flexible, parameterizable
+installation package, the project seeks to reduce deployment complexity and lower barriers to participation in the
+Catena‑X data space. This bundle will enable independent component updates and support a modular "bring your own"
+approach, ultimately fostering a more efficient and accessible ecosystem for diverse participants—such as testers,
+external developers, and small and medium-sized enterprises.
+
+## 1.2 Business Need
+
+Current deployment methods for data space integration are complex and require significant manual effort. This PoC
+addresses the need to:
+
+- Reduce Complexity: Simplify the deployment topology by bundling components into capabilities.
+- Automate Deployment: Provide an automated installation package using Kubernetes and HELM.
+- Reduce Configuration Efforts: Streamline and reduce the number of configuration steps required for integration.
+- Extend Documentation: Provide a detailed documentation tailored to the target groups.
+- Enable Extension: Design the system to allow the seamless addition of new components or capabilities.
+
+## 1.3 Objectives
+
+- Simplify Deployment and Maintenance: Develop an installation package that minimizes manual configuration through
+  automation.
+- Ensure Modularity: Structure the bundle so that components can be independently installed, updated, or replaced
+  without
+  affecting other services.
+- Facilitate Flexibility: Implement a "bring your own" model for key components, such as EDC, PostgreSQL, and HashiCorp
+  Vault, to allow tailored deployments that meet specific needs.
+- Increase Accessibility: Lower entry barriers for new participants by reducing technical complexity and operational
+  dependencies.
+- Scalability: Structure the bundle so that it can be deployed multiple times.
+
+## 1.4 Expected Deliverables
+
+- PoC Documentation: A concept and architecture overview highlighting the modular design.
+- Modular Installation Package: A set of HELM charts for deploying the enablement service bundles:
+    - EDC Bundle: Including the Eclipse Dataspace Connector, EDC PostgreSQL, and HashiCorp Vault.
+    - Digital Twin Bundle: Featuring components such as the Decentral DT Registry (with “bring your own” PostgreSQL) and
+      a Submodel Server Bundle.
+    - Identity Wallet Bundle: Covering the Identity Wallet functionality.
+- Demonstration Environment: A test deployment showcasing reduced complexity and improved efficiency.
+- Basic User Guide: Instructions on how to deploy and update the PoC bundle.
+
+## 1.5 Benefits
+
+- Operational Efficiency: Faster and more reliable deployments with less manual work.
+- Scalability: A modular design that can be scaled or adapted for future full-scale deployments.
+- Ease of Adoption: Simplified deployment processes make it easier for testers and external developers to engage.
+
+## 1.6. Dependencies
+
+- Interoperability with the CATENA‑X standards.
+
+## 1.7. Success Criteria
+
+- Technology Readiness Level: Achievement of a Technology Readiness Level (TRL) of 3, as specified in the requirements.
+- Functional PoC Deployment: Demonstrated automated, modular installation with reduced manual steps.
+- Simplified Configuration: Clear evidence of reduced configuration complexity.
+- Positive Feedback: End-user validation from a select group of demo participants and the Tractus-X community.
+- Documentation Completeness: Availability of concise deployment and user guides.
+
+## 1.8. Out of Scope
+
+- Full Production Readiness: This PoC is not intended to be a production-ready solution.
+- Core Services Exclusion: Core services are not part of the Hausanschluss Bundles.
+- App Provider Role: The role of App Provider is considered out of scope for this deployment.
+- Alternative Deployment Techniques: While the evaluation of alternative deployment methods is acknowledged, the primary
+  focus remains on Kubernetes and HELM-based deployment.
+
+# 2 Requirements Analysis
+
+## 2.1 Assumptions
+
+## 2.2 Requirements Catalog
+
+| ID             | Requirement                                                                                                                                                                                                                                                                                                                                               | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | Deliverables / Acceptance Criteria                                                                                                           |
+|----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------|
+| [WP-7.1.-D001] | TAP7.1 Hausanschluss Bundle aims to simplify the installation and maintenance of the EDC and other components that together ensure a “home connection”. A flexible, parameterizable installation package is intended to reduce complexity and make integration more efficient, thereby simplifying participation in Catena‑X for additional participants. | Specification and development of a flexible, parameterizable installation package that reduces the complexity of installing and maintaining the required components for seamless integration into the Catena‑X data space. This package should facilitate updates and new versions, making participation in Catena‑X more efficient and accessible. In doing so, SMEs shall be enabled to participate without high costs or dependency on SaaS providers while maintaining control over their IT infrastructure. | [WP-7.1.-D001] Concept for the Hausanschluss is created                                                                                      |
+| 7.1.1.1        | The solution concept must define the Capability Bundles structures to be implemented. For each Capability Bundle, the included bundles and their versions are mapped.                                                                                                                                                                                     | "The following Capability Bundle structure is implemented:                                                                                                                                                                                                                                                                                                                                                                                                                                                       | "The structure of the Capability Bundles for the Enablement Services has been specified.                                                     |
+| 7.1.1.2        | Definition of Data Space Roles                                                                                                                                                                                                                                                                                                                            | Capability EDC (Data Transfer) Bundle                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | For version R24.12 it is clearly defined which Tractus‑X services and components are assigned to each Capability Bundle"                     |
+| 7.1.1.4        | Modularity & Maintainability: No dependencies between Capability Bundles                                                                                                                                                                                                                                                                                  | Eclipse Dataspace Connector (EDC) v0.9.0                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | "As part of the target group analysis, the target groups are defined and aligned with the data space roles.                                  |
+| 7.1.1.5        | Modularity & Maintainability: Concept for reducing deployment complexity                                                                                                                                                                                                                                                                                  | EDC PostgresSQL                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | Mapping from data space role to target group has been completed.                                                                             |
+| 7.1.1.6        | Modularity & Maintainability                                                                                                                                                                                                                                                                                                                              | HashiCorp Vault                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | Mapping from target group to data space role has been completed.                                                                             |
+| 7.1.1.13       | Solution Concept                                                                                                                                                                                                                                                                                                                                          | Capability Digital Twin Bundle                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | An assignment of data space roles to Capability Bundles has been made."                                                                      |
+| 7.1.1.14       | Scalability of Enablement Services                                                                                                                                                                                                                                                                                                                        | Decentral DT Registry                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | "Components and Services should obly be part of one bundle.                                                                                  |
+| 7.1.1.16       | Interoperability                                                                                                                                                                                                                                                                                                                                          | PostgresSQL                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | Each bundle must be deployable in isolation and can be installed, updated, or removed independently.                                         |
+| [WP-7.1.-D002] | [WP-7.1.-D002] Target group for the specification is defined.                                                                                                                                                                                                                                                                                             | Capability Identity & Trust (Identity Wallet Bundle)                                                                                                                                                                                                                                                                                                                                                                                                                                                             | Capability Bundles must be organized in separate HELM sub‑charts.                                                                            |
+| 7.1.2.1        | Target Group Analysis                                                                                                                                                                                                                                                                                                                                     | Identity Wallet Mock                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | Circular dependencies between bundles must be avoided."                                                                                      |
+| [WP-7.1.-D003] | [WP-7.1.-D003] Decentralized components and services defined                                                                                                                                                                                                                                                                                              | Capability Semantic Model Bundle                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | "Simplification of deployment processes                                                                                                      |
+| 7.1.3.1        | See [WP-7.1.-D001-AC001]                                                                                                                                                                                                                                                                                                                                  | Submodel Mock (aus Umbrella HELM Chart)"                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | A reduction of manual configuration steps has been achieved.                                                                                 |
+| [WP-7.1.-D004] | [WP-7.1.-D004] Documentation of the Hausanschluss Bundle is completed                                                                                                                                                                                                                                                                                     | "Data Consumer                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | Transparency and traceability                                                                                                                |
+| 7.1.4.1        | Documentation of the Hausanschluss-Bundles                                                                                                                                                                                                                                                                                                                | Data Provider                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | Clearly documented deployment steps are provided.                                                                                            |
+| 7.1.4.2        | Documentation of the Hausanschluss-Bundles                                                                                                                                                                                                                                                                                                                | Enablement Service Provider"                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | Improvements of Chart configuration by                                                                                                       |
+| [WP-7.1.-D005] | [WP-7.1.-D005] Umbrella HELM Charts for the Hausanschluss developed, tested, and documented                                                                                                                                                                                                                                                               | "Unique assignment of components and services to a defined Capability Bundle.                                                                                                                                                                                                                                                                                                                                                                                                                                    | usage of template                                                                                                                            |
+| 7.1.5.1        | Re-activate Umbrella HELM Charts to the latest release state                                                                                                                                                                                                                                                                                              | Each component and service should be assigned to only one Capability Bundle.                                                                                                                                                                                                                                                                                                                                                                                                                                     | reducing configuration options                                                                                                               |
+| 7.1.5.2        | Hierarchical structuring and bundling of Enablement Service components in the Umbrella HELM Chart                                                                                                                                                                                                                                                         | Dependencies between Capability Bundles are allowed."                                                                                                                                                                                                                                                                                                                                                                                                                                                            | reducing manual steps in the setup"                                                                                                          |
+| 7.1.5.3        | Interchangeability of bundle components via “Bring-Your-Own” components                                                                                                                                                                                                                                                                                   | The system deployment should be optimized to reduce the existing complexity. The goal is to make the provisioning process more efficient, robust, and easier to maintain.                                                                                                                                                                                                                                                                                                                                        | Charts are published via a publicly accessible charts repository.                                                                            |
+| [WP-7.1.-D006] | [WP-7.1.-D006] Product developed according to a Technology Readiness Level (TRL) of 3                                                                                                                                                                                                                                                                     | Charts are published automatically.                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | "The solution design for the ""Hausanschluss"" Bundle is created.                                                                            |
+| 7.1.6.1        | POC                                                                                                                                                                                                                                                                                                                                                       | Creation of a solution design for the “Hausanschluss” Bundle.                                                                                                                                                                                                                                                                                                                                                                                                                                                    | The solution design for the ""Hausanschluss"" Bundle ispublished in the repository: https://github.com/eclipse-tractusx/tractus-x-umbrella." |
+| 7.1.6.2        | Deployment Strategy                                                                                                                                                                                                                                                                                                                                       | Scalability of Enablement Services                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | "Developers should be able to deploy an arbitrary number of Enablement Services.                                                             |
+
+# 3 AS-IS Analysis
+
+## 3.1 People
+
+### 3.1.1 Target Group Analysis
+
+See "4.1.1 To-be Target Group Analysis" below. No deviations between As-is and To-be target groups have been identified.
+
+## 3.2 Process
+
+### 3.2.1 Use Case View (high-level)
+
+Umbrella Chart is intended for the following Use Cases:
+
+| Actor             | Use case                                                                                             |
+|-------------------|------------------------------------------------------------------------------------------------------|
+| Product Developer | Sandbox Environments: Create local environments to evaluate and experiment with Catena-X components. |
+| Product Developer | Development: Provide a unified setup for contributors and developers working on Tractus-X projects.  |
+| Product Tester    | Testing: Run end-to-end tests for Catena-X services.                                                 |
+
+## 3.4 System
+
+### 3.4.1 Context Delimitation
+
+````mermaid
+flowchart
+    subgraph "Umbrella Chart"
+        ChartYaml["Chart.yaml"]
+        subgraph charts
+            Portal["Portal"]
+            CentralIdp["CentralIdp"]
+            DiscoveryFinder["Discovery Finder"]
+            SDFactory["SD-Factory"]
+            SSICredentialIssuer["SSI Credential Issuer"]
+            SemanticHub["Semantic Hub"]
+            BPDM["BPDM"]
+            DataConsumer["Data Consumer"]
+            DataProvider["Data Provider"]
+            BDRS["BDRS"]
+            SSIWalletStub["SSI Wallet Stub"]
+        end
+        subgraph "tx-data-provider"
+            EDC["EDC"]
+            DTR["DTR"]
+            SubmodelServer["Submodel Server"]
+        end
+    end
+
+    ChartYaml --> Portal
+    ChartYaml --> CentralIdp
+    ChartYaml --> DiscoveryFinder
+    ChartYaml --> SDFactory
+    ChartYaml --> SSICredentialIssuer
+    ChartYaml --> SemanticHub
+    ChartYaml --> BPDM
+    ChartYaml --> DataConsumer
+    ChartYaml --> DataProvider
+    ChartYaml --> BDRS
+    ChartYaml --> SSIWalletStub
+    DataConsumer --> EDC
+    DataProvider --> EDC
+    DataProvider --> DTR
+    DataProvider --> SubmodelServer
+````
+
+#### Existing Umbrella Chart Structure
+
+# 4 TO-BE Design
+
+## 4.1 People
+
+### 4.1.1 Target Group Analysis
+
+Overall data space roles: https://catena-x.net/en/1/catena-x-introduce-implement/how-to-operate-catena-x
+
+The relevant data space roles for us under requirement 7.1.1.1 are:
+
+- Data Consumer
+- Data Provider
+- Enablement Service Provider
+
+Scope: Umbrella HELM Charts
+
+- Enablement Services: These services are included under the umbrella of HELM charts, focusing on enabling
+  functionalities.
+- Out of Scope: Core services such as Portal or BPDM are not considered within this scope.
+
+Primary target groups:
+
+| No. | Target group                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | Data space roles                                                    | Target group differentiation                                                                                                                                                                                                                                                                            | Behaviour, Needs, Pains & Usage                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+|-----|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| 1   | Developers<ul><li>External Developers (not Tractus-X developers): Utilize the chart for demonstration or evaluation purposes.</li><li>Experienced software and product developers who are developing a business app for a CATENA-X data space. They need to develop the app against the interfaces of the data space and integrate them accordingly.</li><li>They emphasize efficient and cost-effective implementation:<ul><li>Cost Efficiency: They do not want to use expensive SaaS solutions.</li><li>Technical Independence: They lack the knowledge and capacity to deploy the enablement and core services of the data space themselves.</li><li>Focus on Development: They concentrate on application development without delving deeply into the deployment and operation of the underlying infrastructure.</li></ul></li><li>Out of Scope: Developers running tests in test runners are not considered within this scope.</li></ul> | Data Consumer <br/> Data Provider <br/> Enablement Service Provider |                                                                                                                                                                                                                                                                                                         | <ul><li>Needs / sources of information<ul><li><a href="https://eclipse-tractusx.github.io/Kits/">Kit documentation tractus-x</a> for interaction purposes</li><li><a href="https://catenax-ev.github.io/">Catena-X doucmentation</a> for standards and regulations</li><li><a href="https://github.com/eclipse-tractusx/tractus-x-umbrella">Umbrella documentation</a> for umbrella component information</li></ul></li><li>Challenges → Solution<ul><li>Decentralization e.g. Where are other systems? How to interact with them? → Solution: Umbrella charts and bundles for deployment</li><li>Complex setup → Solution: delivery of small capability bundles</li></ul></li></ul> |
+| 2   | <ul><li>Tester requiring a test system (Testmanagement e.V.)</li><li>Requirement: Testbed</li></ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | Data Consumer <br/> Data Provider <br/> Enablement Service Provider | <ul><li>Developer (1) tests their feature.</li><li>Tester (2) performs end-to-end testing.</li><li>For the tester, the modular structure is less relevant since they focus on E2E testing, whereas the developer selects the required components.</li><li>The testbed must be easy to deploy.</li></ul> | <ul><li>Same as above from an End-to-end testing perspective</li><li>Typically a tester has less technical know-how than a developer and therefore needs a "one-size-fits-all" chart for easier testing</li></ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+
+## 4.2 Process
+
+### 4.2.1 Use Case View (high-level)
+
+| Use Case                                | Description                                                                                                       | Actors            |
+|-----------------------------------------|-------------------------------------------------------------------------------------------------------------------|-------------------|
+| Configure HELM Chart                    | The product developer configures the HELM Chart for the specific environment.                                     | Product Developer |
+| Configure Secrets                       | The product developer manages and configures secrets.                                                             | Product Developer |
+| Execute Deployment Pipeline             | The product developer successfully executes the deployment pipeline for the HELM Chart.                           | Product Developer |
+| Integrate EDC, DTR, and Identity Wallet | The actors integrate the components EDC, Digital Twin Registry, and Identity Wallet for seamless interoperability | Product Developer |
+| Set Up Connection Infrastructure        | The actor sets up the connection infrastructure for linking to the central data space infrastructure.             | Product Developer |
+| Maintain Infrastructure Module          | The product developer maintains the modular architecture of the HELM Chart.                                       | Product Developer |
+| Ensure Scalability                      | The product developer ensures scalability to support growing numbers of users and data volumes.                   | Product Developer |
+| Sandbox Environments                    | The product developer creates local environments to evaluate and experiment with Catena-X components.             | Product Developer |
+| E2E Testing                             | The product tester runs end-to-end tests for Catena-X services.                                                   | Product Tester    |
+
+### 4.2.2 Business Process (SCC Artifact)
+
+#### Chart Release Process
+
+Charts will be released using the already existing workflow in the Umbrella Chart repository. The workflow will
+automatically release a Chart, once it is pushed to the "charts/" directory with a new Chart version.
+
+#### Capability Bundle Structure
+
+Capability bundle modularization for the Tractus-X Umbrella Helm chart is a sound architectural and operational design.
+It aligns with both the domain-driven architecture of Catena-X (data exchange, digital twin, identity, semantics are
+distinct domains) and with Kubernetes best practices for managing complex applications (using an umbrella chart to
+bundle related microservices).
+
+Each bundle is self-sufficient, which improves isolation (failures or changes in one domain have minimal impact on
+others) and allows scaling and upgrading along domain lines. It simplifies deployment by allowing “plug-and-play”
+capabilities: an Enablement Service Provider can decide which bundles to operate based on its role e.g., include the
+Digital Twin and Semantic bundles if offering an asset-rich service, or omit them if not. The approach is consistent
+with how other OSS projects deliver multi-component systems, providing one-step installation without sacrificing the
+ability to tweak individual parts.
+
+Why this structure was proposed:
+
+1. **Clear Separation of Concerns**  
+   Each capability bundle (e.g. EDC Data Transfer, Digital Twin, Identity & Trust, Semantic Model) aligns with a
+   specific functional domain. This separation makes it easier to understand the role of each service (e.g., the EDC
+   connector vs. the digital twin registry), reduces coupling between unrelated components, and ultimately makes
+   maintenance and troubleshooting more straightforward.
+2. **Modular Deployment**  
+   Some participants in Catena-X may not need all services (e.g., some might not use the Digital Twin bundle). By
+   structuring the umbrella chart into bundles, a user can enable just those needed capabilities. This leads to leaner
+   installs and avoids unnecessary resource usage.
+3. **Best Practices with Helm**  
+   Using an umbrella chart with subcharts/bundles is a well-recognized Helm best practice for complex applications. It
+   allows a single helm install to set up multiple microservices while still allowing each service to have its own
+   lifecycle, configuration, and version.
+4. **Alignment with Domain-Driven Approach**  
+   Catena-X is organized around distinct, loosely-coupled “building blocks.” Bundling services by domain matches this
+   architectural vision. It’s clear which domain each set of microservices belongs to (EDC for data exchange, identity
+   for credential management, etc.). This clarity also helps new adopters navigate the ecosystem.
+
+````mermaid
+flowchart LR
+    subgraph "Core Services"
+        Vault["Vault"]
+    end
+
+    subgraph "Capability Bundle: Identity & Trust"
+        SSIWalletStub["SSI Wallet Stub"]
+    end
+
+    subgraph "Capability Bundle: Dataspace Connector"
+        EDC["EDC"]
+        EDCDB["EDC DB"]
+    end
+
+    subgraph "Capability Bundle: Digital Twin"
+        DTR["DTR"]
+        DTRDB["DTR DB"]
+    end
+
+    subgraph "Capability Bundle: Data Persitence Layer"
+        SimpleSubmodelServer["Simple Submodel Server"]
+    end
+
+    subgraph "Hausanschluss Bundles"
+        subgraph "Data Provider"
+            DataProvider["Data Provider"]
+        end
+        subgraph "Data Consumer"
+            DataConsumer["Data Consumer"]
+        end
+        subgraph "Enablement Provider"
+            EnablementProvider["Enablement Provider"]
+        end
+    end
+
+    EDC -.-> SSIWalletStub
+    EDC -.-> Vault
+    DataProvider --> EDC
+    DataProvider --> DTR
+    DataProvider --> SimpleSubmodelServer
+    DataConsumer --> EDC
+    EnablementProvider --> DataConsumer
+    EnablementProvider --> DataProvider
+
+````
+
+#### Deployment strategies
+
+##### Role: Data Provider
+
+The standard data provider role consists of a EDC, DTR and Submodel Server Bundles. EDC uses the Identity Wallet Bundle.
+
+````mermaid
+flowchart BT
+    A["Capability Bundle: Identity & Trust"]
+    B["Capability Bundle: Data Persistence Layer"]
+    C["Capability Bundle: Dataspace Connector"]
+    D["Capability Bundle: Digital Twin"]
+    E["Application to be tested/developed"]
+    E --> B
+    E --> C
+    E --> D
+    C --> A
+````
+
+##### Role: Data Consumer
+
+The standard data consumer role consists of only the EDC Bundle and the Identity Wallet Bundle.
+
+````mermaid
+flowchart BT
+    A["Capability Bundle: Identity & Trust"]
+    B["Capability Bundle: Dataspace Connector"]
+    C["Application to be tested/developed"]
+    C --> B
+    B --> A
+
+````
+
+##### Role: Enablement Provider
+
+The Enablement Provider roles consists of both the Data Consumer and Data Provider bundles. This allows provisioning of
+data and the consumtion of the provisioned data by a application.
+
+````mermaid
+flowchart BT
+    A["Capability Bundle: Identity & Trust"]
+    B["Capability Bundle: Data Persitance Layer"]
+    C["Application to be tested/developed"]
+    D["Capability Bundle: Digital Twin"]
+    E["Capability Bundle: Dataspace Connector (Provider)"]
+    F["Capability Bundle: Dataspace Connector (Consumer)"]
+    C --> B
+    C --> D
+    C --> E
+    C --> F
+    E --> A
+    F --> A
+````
+
+##### Bring you own
+
+Each Bundle can be deactivated to use your own component. This requires configuration of the component specific
+parameters in the other components.
+
+In this example this would be the configuration of the Identity Wallet within the EDC.
+
+````mermaid
+flowchart BT
+    A["Application to be tested/developed"]
+    B["Capability Bundle: Dataspace Connector"]
+    C["
Capability Bundle: Identity & Trust
"]
+    D["Own Identity Wallet"]
+    A --> B
+    B -- identitywallet - bundle . enabled = false --> C
+    B -- configure --> D
+
+````
+
+## 4.4 System
+
+### 4.4.1 Context Delimitation / 4.4.2 Interface Documentation
+
path: docs/concept/TAP7.1-solution-design.md
user: login: ds-jhartmann
body: added
created_at: 2025-03-28T12:55:53Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,425 @@
+# [TAP 7.1] Solution Design Hausanschluss Bundle Konzept
+
+# 1 Business Case
+
+## 1.1 Executive Summary
+
+The EDC "Hausanschluss" Bundle aims to simplify the installation of the enablement services Eclipse Dataspace
+Connector (EDC), Digital Twin Registry (DTR), and their supporting components. By developing a flexible, parameterizable
+installation package, the project seeks to reduce deployment complexity and lower barriers to participation in the
+Catena‑X data space. This bundle will enable independent component updates and support a modular "bring your own"
+approach, ultimately fostering a more efficient and accessible ecosystem for diverse participants—such as testers,
+external developers, and small and medium-sized enterprises.
+
+## 1.2 Business Need
+
+Current deployment methods for data space integration are complex and require significant manual effort. This PoC
+addresses the need to:
+
+- Reduce Complexity: Simplify the deployment topology by bundling components into capabilities.
+- Automate Deployment: Provide an automated installation package using Kubernetes and HELM.
+- Reduce Configuration Efforts: Streamline and reduce the number of configuration steps required for integration.
+- Extend Documentation: Provide a detailed documentation tailored to the target groups.
+- Enable Extension: Design the system to allow the seamless addition of new components or capabilities.
+
+## 1.3 Objectives
+
+- Simplify Deployment and Maintenance: Develop an installation package that minimizes manual configuration through
+  automation.
+- Ensure Modularity: Structure the bundle so that components can be independently installed, updated, or replaced
+  without
+  affecting other services.
+- Facilitate Flexibility: Implement a "bring your own" model for key components, such as EDC, PostgreSQL, and HashiCorp
+  Vault, to allow tailored deployments that meet specific needs.
+- Increase Accessibility: Lower entry barriers for new participants by reducing technical complexity and operational
+  dependencies.
+- Scalability: Structure the bundle so that it can be deployed multiple times.
+
+## 1.4 Expected Deliverables
+
+- PoC Documentation: A concept and architecture overview highlighting the modular design.
+- Modular Installation Package: A set of HELM charts for deploying the enablement service bundles:
+    - EDC Bundle: Including the Eclipse Dataspace Connector, EDC PostgreSQL, and HashiCorp Vault.
+    - Digital Twin Bundle: Featuring components such as the Decentral DT Registry (with “bring your own” PostgreSQL) and
+      a Submodel Server Bundle.
+    - Identity Wallet Bundle: Covering the Identity Wallet functionality.
+- Demonstration Environment: A test deployment showcasing reduced complexity and improved efficiency.
+- Basic User Guide: Instructions on how to deploy and update the PoC bundle.
+
+## 1.5 Benefits
+
+- Operational Efficiency: Faster and more reliable deployments with less manual work.
+- Scalability: A modular design that can be scaled or adapted for future full-scale deployments.
+- Ease of Adoption: Simplified deployment processes make it easier for testers and external developers to engage.
+
+## 1.6. Dependencies
+
+- Interoperability with the CATENA‑X standards.
+
+## 1.7. Success Criteria
+
+- Technology Readiness Level: Achievement of a Technology Readiness Level (TRL) of 3, as specified in the requirements.
+- Functional PoC Deployment: Demonstrated automated, modular installation with reduced manual steps.
+- Simplified Configuration: Clear evidence of reduced configuration complexity.
+- Positive Feedback: End-user validation from a select group of demo participants and the Tractus-X community.
+- Documentation Completeness: Availability of concise deployment and user guides.
+
+## 1.8. Out of Scope
+
+- Full Production Readiness: This PoC is not intended to be a production-ready solution.
+- Core Services Exclusion: Core services are not part of the Hausanschluss Bundles.
+- App Provider Role: The role of App Provider is considered out of scope for this deployment.
+- Alternative Deployment Techniques: While the evaluation of alternative deployment methods is acknowledged, the primary
+  focus remains on Kubernetes and HELM-based deployment.
+
+# 2 Requirements Analysis
+
+## 2.1 Assumptions
+
+## 2.2 Requirements Catalog
+
+| ID             | Requirement                                                                                                                                                                                                                                                                                                                                               | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | Deliverables / Acceptance Criteria                                                                                                           |
+|----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------|
+| [WP-7.1.-D001] | TAP7.1 Hausanschluss Bundle aims to simplify the installation and maintenance of the EDC and other components that together ensure a “home connection”. A flexible, parameterizable installation package is intended to reduce complexity and make integration more efficient, thereby simplifying participation in Catena‑X for additional participants. | Specification and development of a flexible, parameterizable installation package that reduces the complexity of installing and maintaining the required components for seamless integration into the Catena‑X data space. This package should facilitate updates and new versions, making participation in Catena‑X more efficient and accessible. In doing so, SMEs shall be enabled to participate without high costs or dependency on SaaS providers while maintaining control over their IT infrastructure. | [WP-7.1.-D001] Concept for the Hausanschluss is created                                                                                      |
+| 7.1.1.1        | The solution concept must define the Capability Bundles structures to be implemented. For each Capability Bundle, the included bundles and their versions are mapped.                                                                                                                                                                                     | "The following Capability Bundle structure is implemented:                                                                                                                                                                                                                                                                                                                                                                                                                                                       | "The structure of the Capability Bundles for the Enablement Services has been specified.                                                     |
+| 7.1.1.2        | Definition of Data Space Roles                                                                                                                                                                                                                                                                                                                            | Capability EDC (Data Transfer) Bundle                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | For version R24.12 it is clearly defined which Tractus‑X services and components are assigned to each Capability Bundle"                     |
+| 7.1.1.4        | Modularity & Maintainability: No dependencies between Capability Bundles                                                                                                                                                                                                                                                                                  | Eclipse Dataspace Connector (EDC) v0.9.0                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | "As part of the target group analysis, the target groups are defined and aligned with the data space roles.                                  |
+| 7.1.1.5        | Modularity & Maintainability: Concept for reducing deployment complexity                                                                                                                                                                                                                                                                                  | EDC PostgresSQL                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | Mapping from data space role to target group has been completed.                                                                             |
+| 7.1.1.6        | Modularity & Maintainability                                                                                                                                                                                                                                                                                                                              | HashiCorp Vault                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | Mapping from target group to data space role has been completed.                                                                             |
+| 7.1.1.13       | Solution Concept                                                                                                                                                                                                                                                                                                                                          | Capability Digital Twin Bundle                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | An assignment of data space roles to Capability Bundles has been made."                                                                      |
+| 7.1.1.14       | Scalability of Enablement Services                                                                                                                                                                                                                                                                                                                        | Decentral DT Registry                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | "Components and Services should obly be part of one bundle.                                                                                  |
+| 7.1.1.16       | Interoperability                                                                                                                                                                                                                                                                                                                                          | PostgresSQL                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | Each bundle must be deployable in isolation and can be installed, updated, or removed independently.                                         |
+| [WP-7.1.-D002] | [WP-7.1.-D002] Target group for the specification is defined.                                                                                                                                                                                                                                                                                             | Capability Identity & Trust (Identity Wallet Bundle)                                                                                                                                                                                                                                                                                                                                                                                                                                                             | Capability Bundles must be organized in separate HELM sub‑charts.                                                                            |
+| 7.1.2.1        | Target Group Analysis                                                                                                                                                                                                                                                                                                                                     | Identity Wallet Mock                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | Circular dependencies between bundles must be avoided."                                                                                      |
+| [WP-7.1.-D003] | [WP-7.1.-D003] Decentralized components and services defined                                                                                                                                                                                                                                                                                              | Capability Semantic Model Bundle                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | "Simplification of deployment processes                                                                                                      |
+| 7.1.3.1        | See [WP-7.1.-D001-AC001]                                                                                                                                                                                                                                                                                                                                  | Submodel Mock (aus Umbrella HELM Chart)"                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | A reduction of manual configuration steps has been achieved.                                                                                 |
+| [WP-7.1.-D004] | [WP-7.1.-D004] Documentation of the Hausanschluss Bundle is completed                                                                                                                                                                                                                                                                                     | "Data Consumer                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | Transparency and traceability                                                                                                                |
+| 7.1.4.1        | Documentation of the Hausanschluss-Bundles                                                                                                                                                                                                                                                                                                                | Data Provider                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | Clearly documented deployment steps are provided.                                                                                            |
+| 7.1.4.2        | Documentation of the Hausanschluss-Bundles                                                                                                                                                                                                                                                                                                                | Enablement Service Provider"                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | Improvements of Chart configuration by                                                                                                       |
+| [WP-7.1.-D005] | [WP-7.1.-D005] Umbrella HELM Charts for the Hausanschluss developed, tested, and documented                                                                                                                                                                                                                                                               | "Unique assignment of components and services to a defined Capability Bundle.                                                                                                                                                                                                                                                                                                                                                                                                                                    | usage of template                                                                                                                            |
+| 7.1.5.1        | Re-activate Umbrella HELM Charts to the latest release state                                                                                                                                                                                                                                                                                              | Each component and service should be assigned to only one Capability Bundle.                                                                                                                                                                                                                                                                                                                                                                                                                                     | reducing configuration options                                                                                                               |
+| 7.1.5.2        | Hierarchical structuring and bundling of Enablement Service components in the Umbrella HELM Chart                                                                                                                                                                                                                                                         | Dependencies between Capability Bundles are allowed."                                                                                                                                                                                                                                                                                                                                                                                                                                                            | reducing manual steps in the setup"                                                                                                          |
+| 7.1.5.3        | Interchangeability of bundle components via “Bring-Your-Own” components                                                                                                                                                                                                                                                                                   | The system deployment should be optimized to reduce the existing complexity. The goal is to make the provisioning process more efficient, robust, and easier to maintain.                                                                                                                                                                                                                                                                                                                                        | Charts are published via a publicly accessible charts repository.                                                                            |
+| [WP-7.1.-D006] | [WP-7.1.-D006] Product developed according to a Technology Readiness Level (TRL) of 3                                                                                                                                                                                                                                                                     | Charts are published automatically.                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | "The solution design for the ""Hausanschluss"" Bundle is created.                                                                            |
+| 7.1.6.1        | POC                                                                                                                                                                                                                                                                                                                                                       | Creation of a solution design for the “Hausanschluss” Bundle.                                                                                                                                                                                                                                                                                                                                                                                                                                                    | The solution design for the ""Hausanschluss"" Bundle ispublished in the repository: https://github.com/eclipse-tractusx/tractus-x-umbrella." |
+| 7.1.6.2        | Deployment Strategy                                                                                                                                                                                                                                                                                                                                       | Scalability of Enablement Services                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | "Developers should be able to deploy an arbitrary number of Enablement Services.                                                             |
+
+# 3 AS-IS Analysis
+
+## 3.1 People
+
+### 3.1.1 Target Group Analysis
+
+See "4.1.1 To-be Target Group Analysis" below. No deviations between As-is and To-be target groups have been identified.
+
+## 3.2 Process
+
+### 3.2.1 Use Case View (high-level)
+
+Umbrella Chart is intended for the following Use Cases:
+
+| Actor             | Use case                                                                                             |
+|-------------------|------------------------------------------------------------------------------------------------------|
+| Product Developer | Sandbox Environments: Create local environments to evaluate and experiment with Catena-X components. |
+| Product Developer | Development: Provide a unified setup for contributors and developers working on Tractus-X projects.  |
+| Product Tester    | Testing: Run end-to-end tests for Catena-X services.                                                 |
+
+## 3.4 System
+
+### 3.4.1 Context Delimitation
+
+````mermaid
+flowchart
+    subgraph "Umbrella Chart"
+        ChartYaml["Chart.yaml"]
+        subgraph charts
+            Portal["Portal"]
+            CentralIdp["CentralIdp"]
+            DiscoveryFinder["Discovery Finder"]
+            SDFactory["SD-Factory"]
+            SSICredentialIssuer["SSI Credential Issuer"]
+            SemanticHub["Semantic Hub"]
+            BPDM["BPDM"]
+            DataConsumer["Data Consumer"]
+            DataProvider["Data Provider"]
+            BDRS["BDRS"]
+            SSIWalletStub["SSI Wallet Stub"]
+        end
+        subgraph "tx-data-provider"
+            EDC["EDC"]
+            DTR["DTR"]
+            SubmodelServer["Submodel Server"]
+        end
+    end
+
+    ChartYaml --> Portal
+    ChartYaml --> CentralIdp
+    ChartYaml --> DiscoveryFinder
+    ChartYaml --> SDFactory
+    ChartYaml --> SSICredentialIssuer
+    ChartYaml --> SemanticHub
+    ChartYaml --> BPDM
+    ChartYaml --> DataConsumer
+    ChartYaml --> DataProvider
+    ChartYaml --> BDRS
+    ChartYaml --> SSIWalletStub
+    DataConsumer --> EDC
+    DataProvider --> EDC
+    DataProvider --> DTR
+    DataProvider --> SubmodelServer
+````
+
+#### Existing Umbrella Chart Structure
+
+# 4 TO-BE Design
+
+## 4.1 People
+
+### 4.1.1 Target Group Analysis
+
+Overall data space roles: https://catena-x.net/en/1/catena-x-introduce-implement/how-to-operate-catena-x
+
+The relevant data space roles for us under requirement 7.1.1.1 are:
+
+- Data Consumer
+- Data Provider
+- Enablement Service Provider
+
+Scope: Umbrella HELM Charts
+
+- Enablement Services: These services are included under the umbrella of HELM charts, focusing on enabling
+  functionalities.
+- Out of Scope: Core services such as Portal or BPDM are not considered within this scope.
+
+Primary target groups:
+
+| No. | Target group                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | Data space roles                                                    | Target group differentiation                                                                                                                                                                                                                                                                            | Behaviour, Needs, Pains & Usage                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+|-----|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| 1   | Developers<ul><li>External Developers (not Tractus-X developers): Utilize the chart for demonstration or evaluation purposes.</li><li>Experienced software and product developers who are developing a business app for a CATENA-X data space. They need to develop the app against the interfaces of the data space and integrate them accordingly.</li><li>They emphasize efficient and cost-effective implementation:<ul><li>Cost Efficiency: They do not want to use expensive SaaS solutions.</li><li>Technical Independence: They lack the knowledge and capacity to deploy the enablement and core services of the data space themselves.</li><li>Focus on Development: They concentrate on application development without delving deeply into the deployment and operation of the underlying infrastructure.</li></ul></li><li>Out of Scope: Developers running tests in test runners are not considered within this scope.</li></ul> | Data Consumer <br/> Data Provider <br/> Enablement Service Provider |                                                                                                                                                                                                                                                                                                         | <ul><li>Needs / sources of information<ul><li><a href="https://eclipse-tractusx.github.io/Kits/">Kit documentation tractus-x</a> for interaction purposes</li><li><a href="https://catenax-ev.github.io/">Catena-X doucmentation</a> for standards and regulations</li><li><a href="https://github.com/eclipse-tractusx/tractus-x-umbrella">Umbrella documentation</a> for umbrella component information</li></ul></li><li>Challenges → Solution<ul><li>Decentralization e.g. Where are other systems? How to interact with them? → Solution: Umbrella charts and bundles for deployment</li><li>Complex setup → Solution: delivery of small capability bundles</li></ul></li></ul> |
+| 2   | <ul><li>Tester requiring a test system (Testmanagement e.V.)</li><li>Requirement: Testbed</li></ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | Data Consumer <br/> Data Provider <br/> Enablement Service Provider | <ul><li>Developer (1) tests their feature.</li><li>Tester (2) performs end-to-end testing.</li><li>For the tester, the modular structure is less relevant since they focus on E2E testing, whereas the developer selects the required components.</li><li>The testbed must be easy to deploy.</li></ul> | <ul><li>Same as above from an End-to-end testing perspective</li><li>Typically a tester has less technical know-how than a developer and therefore needs a "one-size-fits-all" chart for easier testing</li></ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+
+## 4.2 Process
+
+### 4.2.1 Use Case View (high-level)
+
+| Use Case                                | Description                                                                                                       | Actors            |
path: docs/concept/TAP7.1-solution-design.md
user: login: ds-jhartmann
body: added
created_at: 2025-03-28T12:58:45Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,424 @@
+# [TAP 7.1] Solution Design Hausanschluss Bundle Konzept
+
+# 1 Business Case
+
+## 1.1 Executive Summary
+
+The EDC "Hausanschluss" Bundle aims to simplify the installation of the enablement services Eclipse Dataspace
+Connector (EDC), Digital Twin Registry (DTR), and their supporting components. By developing a flexible, parameterizable
+installation package, the project seeks to reduce deployment complexity and lower barriers to participation in the
+Catena‑X data space. This bundle will enable independent component updates and support a modular "bring your own"
+approach, ultimately fostering a more efficient and accessible ecosystem for diverse participants—such as testers,
+external developers, and small and medium-sized enterprises.
+
+## 1.2 Business Need
+
+Current deployment methods for data space integration are complex and require significant manual effort. This PoC
+addresses the need to:
+
+- **Reduce Complexity:** Simplify the deployment topology by bundling components into capabilities.
+- **Automate Deployment:** Provide an automated installation package using Kubernetes and HELM.
+- **Reduce Configuration Efforts:** Streamline and reduce the number of configuration steps required for integration.
+- **Extend Documentation:** Provide a detailed documentation tailored to the target groups.
+- **Enable Extension:** Design the system to allow the seamless addition of new components or capabilities.
+
+## 1.3 Objectives
+
+- **Simplify Deployment and Maintenance:** Develop an installation package that minimizes manual configuration through
+  automation.
+- **Ensure Modularity:** Structure the bundle so that components can be independently installed, updated, or replaced
+  without affecting other services.
+- **Facilitate Flexibility:** Implement a "bring your own" model for key components, such as EDC, PostgreSQL, and HashiCorp
+  Vault, to allow tailored deployments that meet specific needs.
+- **Increase Accessibility**: Lower entry barriers for new participants by reducing technical complexity and operational
+  dependencies.
+- **Scalability:** Structure the bundles so that they can be deployed multiple times.
+
+## 1.4 Expected Deliverables
+
+- **PoC Documentation:** A concept and architecture overview highlighting the modular design.
+- **Modular Installation Package:** A set of HELM charts for deploying the enablement service bundles:
+    - **Dataspace Connector:** Including the Eclipse Dataspace Connector, EDC PostgreSQL, and HashiCorp Vault.
+    - **Digital Twin Bundle:** Featuring components such as the Decentral DT Registry (with “bring your own” PostgreSQL)
+    - **Data Persitence Layer Bundle:** Including a simple Submodel Server to store semantic data.
+    - **Identity Wallet Bundle:** Covering the Identity Wallet functionality.
+- **Demonstration Environment:** A test deployment showcasing reduced complexity and improved efficiency.
+- **Basic User Guide:** Instructions on how to deploy and update the PoC bundle.
+
+## 1.5 Benefits
+
+- **Operational Efficiency:** Faster and more reliable deployments with less manual work.
+- **Scalability:** A modular design that can be scaled or adapted for future full-scale deployments.
+- **Ease of Adoption:** Simplified deployment processes make it easier for testers and external developers to engage.
+
+## 1.6. Dependencies
+
+- **Interoperability** with the CATENA‑X standards.
+
+## 1.7. Success Criteria
+
+- **Technology Readiness Level:** Achievement of a Technology Readiness Level (TRL) of 3, as specified in the requirements.
+- **Functional PoC Deployment:** Demonstrated automated, modular installation with reduced manual steps.
+- **Simplified Configuration:** Clear evidence of reduced configuration complexity.
+- **Positive Feedback:** End-user validation from a select group of demo participants and the Tractus-X community.
+- **Documentation Completeness:** Availability of concise deployment and user guides.
+
+## 1.8. Out of Scope
+
+- **Full Production Readiness:** This PoC is not intended to be a production-ready solution.
+- **Core Services Exclusion:** Core services are not part of the Hausanschluss Bundles.
+- **App Provider Role:** The role of App Provider is considered out of scope for this deployment.
+- **Alternative Deployment Techniques:** While the evaluation of alternative deployment methods is acknowledged, the primary
+  focus remains on Kubernetes and HELM-based deployment.
+
+# 2 Requirements Analysis
+
+## 2.1 Assumptions
+
+## 2.2 Requirements Catalog
+
+| ID             | Requirement                                                                                                                                                                                                                                                                                                                                               | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | Deliverables / Acceptance Criteria                                                                                                                                                                                                                                                                                                                                                                                   |
+|----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| [WP-7.1.-D001] | TAP7.1 Hausanschluss Bundle aims to simplify the installation and maintenance of the EDC and other components that together ensure a “home connection”. A flexible, parameterizable installation package is intended to reduce complexity and make integration more efficient, thereby simplifying participation in Catena‑X for additional participants. | Specification and development of a flexible, parameterizable installation package that reduces the complexity of installing and maintaining the required components for seamless integration into the Catena‑X data space. This package should facilitate updates and new versions, making participation in Catena‑X more efficient and accessible. In doing so, SMEs shall be enabled to participate without high costs or dependency on SaaS providers while maintaining control over their IT infrastructure. | [WP-7.1.-D001] Concept for the Hausanschluss is created                                                                                                                                                                                                                                                                                                                                                              |
+| 7.1.1.1        | The solution concept must define the Capability Bundles structures to be implemented. For each Capability Bundle, the included bundles and their versions are mapped.                                                                                                                                                                                     | "The following Capability Bundle structure is implemented:                                                                                                                                                                                                                                                                                                                                                                                                                                                       | The structure of the Capability Bundles for the Enablement Services has been specified. For version R24.12 it is clearly defined which Tractus‑X services and components are assigned to each Capability Bundle                                                                                                                                                                                                      |
+| 7.1.1.2        | Definition of Data Space Roles                                                                                                                                                                                                                                                                                                                            | Data Consumer, Data Provider, Enablement Service Provider                                                                                                                                                                                                                                                                                                                                                                                                                                                        | As part of the target group analysis, the target groups are defined and aligned with the data space roles. <br>Mapping from data space role to target group has been completed. <br>Mapping from target group to data space role has been completed. <br>An assignment of data space roles to Capability Bundles has been made.                                                                                      |
+| 7.1.1.4        | Modularity & Maintainability: No dependencies between Capability Bundles                                                                                                                                                                                                                                                                                  | Unique assignment of components and services to a defined Capability Bundle. <br>Each component and service should be assigned to only one Capability Bundle. <br>Dependencies between Capability Bundles are allowed.                                                                                                                                                                                                                                                                                           | Components and Services should obly be part of one bundle. <br>Each bundle must be deployable in isolation and can be installed, updated, or removed independently. <br>Capability Bundles must be organized in separate HELM sub‑charts. <br>Circular dependencies between bundles must be avoided.                                                                                                                 |
+| 7.1.1.5        | Modularity & Maintainability: Concept for reducing deployment complexity                                                                                                                                                                                                                                                                                  | The system deployment should be optimized to reduce the existing complexity. The goal is to make the provisioning process more efficient, robust, and easier to maintain.                                                                                                                                                                                                                                                                                                                                        | **Simplification of deployment processes:** A reduction of manual configuration steps has been achieved. <br>**Transparency and traceability:** Clearly documented deployment steps are provided. <br>**Improvements of Chart configuration by:** <br>usage of template  <br>reducing configuration options <br>reducing manual steps in the setup                                                                   |
+| 7.1.1.6        | Modularity & Maintainability                                                                                                                                                                                                                                                                                                                              | Charts are published automatically.                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | Charts are published via a publicly accessible charts repository.                                                                                                                                                                                                                                                                                                                                                    |
+| 7.1.1.13       | Solution Concept                                                                                                                                                                                                                                                                                                                                          | Creation of a solution design for the “Hausanschluss” Bundle.                                                                                                                                                                                                                                                                                                                                                                                                                                                    | The solution design for the "Hausanschluss" Bundle is created. <br>The solution design for the "Hausanschluss" Bundle ispublished in the repository: https://github.com/eclipse-tractusx/tractus-x-umbrella.                                                                                                                                                                                                         |
+| 7.1.1.14       | Scalability of Enablement Services                                                                                                                                                                                                                                                                                                                        | Scalability of Enablement Services                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | Developers should be able to deploy an arbitrary number of Enablement Services. <br>Example: Up to 3 EDCs can be provided.                                                                                                                                                                                                                                                                                           |
+| 7.1.1.16       | Interoperability                                                                                                                                                                                                                                                                                                                                          | Interoperability                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | Interoperability with the CATENA‑X standards. <br>This interoperability is documented and traceable.                                                                                                                                                                                                                                                                                                                 |
+| [WP-7.1.-D002] | [WP-7.1.-D002] Target group for the specification is defined.                                                                                                                                                                                                                                                                                             |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | [WP-7.1.-D002] Target group for the specification is defined.                                                                                                                                                                                                                                                                                                                                                        |
+| 7.1.2.1        | Target Group Analysis                                                                                                                                                                                                                                                                                                                                     | The target group analysis for the "Hausanschluss Bundle"is defined.                                                                                                                                                                                                                                                                                                                                                                                                                                              | The analysis has been conducted. <br>The target group is included in the solution concept <br>To be clarified: What is included in the Hausanschluss and who can operate it in which scenario (OEM, SME, service provider, etc.).                                                                                                                                                                                    |
+| [WP-7.1.-D003] | [WP-7.1.-D003] Decentralized components and services defined                                                                                                                                                                                                                                                                                              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | [WP-7.1.-D003] Decentralized components and services have been defined.                                                                                                                                                                                                                                                                                                                                              |
+| 7.1.3.1        | See [WP-7.1.-D001-AC001]                                                                                                                                                                                                                                                                                                                                  |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | See [WP-7.1.-D001-AC001]                                                                                                                                                                                                                                                                                                                                                                                             |
+| [WP-7.1.-D004] | [WP-7.1.-D004] Documentation of the Hausanschluss Bundle is completed                                                                                                                                                                                                                                                                                     |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | [WP-7.1.-D004] Documentation of the Hausanschluss Bundle is completed                                                                                                                                                                                                                                                                                                                                                |
+| 7.1.4.1        | Documentation of the Hausanschluss-Bundles                                                                                                                                                                                                                                                                                                                | Usability                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | Documentation is provided that enables an experienced product developer - with knowledge of Helm Charts, Docker, and Vaults - to deploy the chart independently without external help. <br>A troubleshooting and FAQ section is included to support the developer. <br>Prerequisites, skills, and technology requirements are outlined, detailing what a developer must know to perform the deployment autonomously. |
+| 7.1.4.2        | Documentation of the Hausanschluss-Bundles                                                                                                                                                                                                                                                                                                                | Documentation of the Hausanschluss-Bundles is completed.                                                                                                                                                                                                                                                                                                                                                                                                                                                         | Documentation is provided for: <br>Configuration of the defined bundles according to the specified requirements and parameters <br>Integration of the documentation into the Umbrella HELM Charts <br>Integration into the Umbrella HELM Chart to ensure consistent deployment                                                                                                                                       |
+| [WP-7.1.-D005] | [WP-7.1.-D005] Umbrella HELM Charts for the Hausanschluss developed, tested, and documented                                                                                                                                                                                                                                                               |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | [WP-7.1.-D005] Umbrella HELM Charts for the Hausanschluss have been developed, tested, and documented.                                                                                                                                                                                                                                                                                                               |
+| 7.1.5.1        | Re-activate Umbrella HELM Charts to the latest release state                                                                                                                                                                                                                                                                                              | The Enablement Services components of the Umbrella HELM Charts must be updated to version R24.12. This includes the following upgrades: <br> Upgrade DTR to version R24.12 (#188) <br>Upgrade EDCs to version R24.12 (#193) <br>Update SSI-DIM-Wallet-Stub to version 0.1.8 (#206)                                                                                                                                                                                                                               | The HELM Chart will then contain the updated versions of the components. <br>After the upgrade, the components (DTR, EDCs, SSI‑DIM‑Wallet‑Stub) run stably without functional impairments. <br>The deployment pipeline for the HELM Chart executes successfully <br>Relevant tests & smoke tests (e.g., integration tests) confirm the migration.                                                                    |
+| 7.1.5.2        | Hierarchical structuring and bundling of Enablement Service components in the Umbrella HELM Chart                                                                                                                                                                                                                                                         | The Umbrella HELM Chart should be structured hierarchically so that related Enablement Service components are grouped into bundles. <br>The Umbrella HELM Chart must have a clear hierarchical structure <br> Each Enablement Service component must be assigned to a unique bundle.<br>No circular dependencies between bundles are allowed.                                                                                                                                                                    | The chart is modular and divided into defined bundles. <br>Each bunde can be deployed and maintained independently.                                                                                                                                                                                                                                                                                                  |
+| 7.1.5.3        | Interchangeability of bundle components via “Bring-Your-Own” components                                                                                                                                                                                                                                                                                   | Bundle components should be interchangeable through “Bring-Your-Own” components. <br>“Bring your own” is available for every component and means that these components do not have to be delivered by default with the Umbrella Chart but can be provided by the respective users.                                                                                                                                                                                                                               | Bundle components can be interchanged by “Bring-Your-Own” components.                                                                                                                                                                                                                                                                                                                                                |
+| [WP-7.1.-D006] | [WP-7.1.-D006] Product developed according to a Technology Readiness Level (TRL) of 3                                                                                                                                                                                                                                                                     |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | [WP-7.1.-D006] The product is developed according to a Technology Readiness Level (TRL) of 3                                                                                                                                                                                                                                                                                                                         |
+| 7.1.6.1        | POC                                                                                                                                                                                                                                                                                                                                                       | Creation of a POC for the "Hausanschluss" Bundle                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | POC implementation is completed. <br>POC has been presented in a demo                                                                                                                                                                                                                                                                                                                                                |
+| 7.1.6.2        | Deployment Strategy                                                                                                                                                                                                                                                                                                                                       | The provisioning of bundles is carried out independently. <br>There must be an option to selectively activate or deactivate bundles.                                                                                                                                                                                                                                                                                                                                                                             | Configuration is managed via HELM values, allowing flexible adaptation according to the environment.                                                                                                                                                                                                                                                                                                                 |
+
+# 3 AS-IS Analysis
+
+## 3.1 People
+
+### 3.1.1 Target Group Analysis
+
+See "4.1.1 To-be Target Group Analysis" below. No deviations between As-is and To-be target groups have been identified.
+
+## 3.2 Process
+
+### 3.2.1 Use Case View (high-level)
+
+Umbrella Chart is intended for the following Use Cases:
+
+| Actor             | Use case                                                                                             |
+|-------------------|------------------------------------------------------------------------------------------------------|
+| Product Developer | Sandbox Environments: Create local environments to evaluate and experiment with Catena-X components. |
+| Product Developer | Development: Provide a unified setup for contributors and developers working on Tractus-X projects.  |
+| Product Tester    | Testing: Run end-to-end tests for Catena-X services.                                                 |
+
+## 3.4 System
+
+### 3.4.1 Context Delimitation
+
+````mermaid
+flowchart
+    subgraph "Umbrella Chart"
+        ChartYaml["Chart.yaml"]
+        subgraph charts
+            Portal["Portal"]
+            CentralIdp["CentralIdp"]
+            DiscoveryFinder["Discovery Finder"]
+            SDFactory["SD-Factory"]
+            SSICredentialIssuer["SSI Credential Issuer"]
+            SemanticHub["Semantic Hub"]
+            BPDM["BPDM"]
+            DataConsumer["Data Consumer"]
+            DataProvider["Data Provider"]
+            BDRS["BDRS"]
+            SSIWalletStub["SSI Wallet Stub"]
+        end
+        subgraph "tx-data-provider"
+            EDC["EDC"]
+            DTR["DTR"]
+            SubmodelServer["Submodel Server"]
+        end
+    end
+
+    ChartYaml --> Portal
+    ChartYaml --> CentralIdp
+    ChartYaml --> DiscoveryFinder
+    ChartYaml --> SDFactory
+    ChartYaml --> SSICredentialIssuer
+    ChartYaml --> SemanticHub
+    ChartYaml --> BPDM
+    ChartYaml --> DataConsumer
+    ChartYaml --> DataProvider
+    ChartYaml --> BDRS
+    ChartYaml --> SSIWalletStub
+    DataConsumer --> EDC
+    DataProvider --> EDC
+    DataProvider --> DTR
+    DataProvider --> SubmodelServer
+````
+
+#### Existing Umbrella Chart Structure
+
+# 4 TO-BE Design
+
+## 4.1 People
+
+### 4.1.1 Target Group Analysis
+
+Overall data space roles: https://catena-x.net/en/1/catena-x-introduce-implement/how-to-operate-catena-x
+
+The relevant data space roles for us under requirement 7.1.1.1 are:
+
+- Data Consumer
+- Data Provider
+- Enablement Service Provider
+
+Scope: Umbrella HELM Charts
+
+- Enablement Services: These services are included under the umbrella of HELM charts, focusing on enabling
+  functionalities.
+- Out of Scope: Core services such as Portal or BPDM are not considered within this scope.
+
+Primary target groups:
+
+| No. | Target group                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | Data space roles                                                    | Target group differentiation                                                                                                                                                                                                                                                                            | Behaviour, Needs, Pains & Usage                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+|-----|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| 1   | Developers<ul><li>External Developers (not Tractus-X developers): Utilize the chart for demonstration or evaluation purposes.</li><li>Experienced software and product developers who are developing a business app for a CATENA-X data space. They need to develop the app against the interfaces of the data space and integrate them accordingly.</li><li>They emphasize efficient and cost-effective implementation:<ul><li>Cost Efficiency: They do not want to use expensive SaaS solutions.</li><li>Technical Independence: They lack the knowledge and capacity to deploy the enablement and core services of the data space themselves.</li><li>Focus on Development: They concentrate on application development without delving deeply into the deployment and operation of the underlying infrastructure.</li></ul></li><li>Out of Scope: Developers running tests in test runners are not considered within this scope.</li></ul> | Data Consumer <br/> Data Provider <br/> Enablement Service Provider |                                                                                                                                                                                                                                                                                                         | <ul><li>Needs / sources of information<ul><li><a href="https://eclipse-tractusx.github.io/Kits/">Kit documentation tractus-x</a> for interaction purposes</li><li><a href="https://catenax-ev.github.io/">Catena-X doucmentation</a> for standards and regulations</li><li><a href="https://github.com/eclipse-tractusx/tractus-x-umbrella">Umbrella documentation</a> for umbrella component information</li></ul></li><li>Challenges → Solution<ul><li>Decentralization e.g. Where are other systems? How to interact with them? → Solution: Umbrella charts and bundles for deployment</li><li>Complex setup → Solution: delivery of small capability bundles</li></ul></li></ul> |
+| 2   | <ul><li>Tester requiring a test system (Testmanagement e.V.)</li><li>Requirement: Testbed</li></ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | Data Consumer <br/> Data Provider <br/> Enablement Service Provider | <ul><li>Developer (1) tests their feature.</li><li>Tester (2) performs end-to-end testing.</li><li>For the tester, the modular structure is less relevant since they focus on E2E testing, whereas the developer selects the required components.</li><li>The testbed must be easy to deploy.</li></ul> | <ul><li>Same as above from an End-to-end testing perspective</li><li>Typically a tester has less technical know-how than a developer and therefore needs a "one-size-fits-all" chart for easier testing</li></ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+
+## 4.2 Process
+
+### 4.2.1 Use Case View (high-level)
+
+| Use Case                                | Description                                                                                                       | Actors            |
+|-----------------------------------------|-------------------------------------------------------------------------------------------------------------------|-------------------|
+| Configure HELM Chart                    | The product developer configures the HELM Chart for the specific environment.                                     | Product Developer |
+| Configure Secrets                       | The product developer manages and configures secrets.                                                             | Product Developer |
+| Execute Deployment Pipeline             | The product developer successfully executes the deployment pipeline for the HELM Chart.                           | Product Developer |
+| Integrate EDC, DTR, and Identity Wallet | The actors integrate the components EDC, Digital Twin Registry, and Identity Wallet for seamless interoperability | Product Developer |
+| Set Up Connection Infrastructure        | The actor sets up the connection infrastructure for linking to the central data space infrastructure.             | Product Developer |
+| Maintain Infrastructure Module          | The product developer maintains the modular architecture of the HELM Chart.                                       | Product Developer |
+| Ensure Scalability                      | The product developer ensures scalability to support growing numbers of users and data volumes.                   | Product Developer |
+| Sandbox Environments                    | The product developer creates local environments to evaluate and experiment with Catena-X components.             | Product Developer |
+| E2E Testing                             | The product tester runs end-to-end tests for Catena-X services.                                                   | Product Tester    |
+
+### 4.2.2 Business Process (SCC Artifact)
+
+#### Chart Release Process
+
+Charts will be released using the already existing workflow in the Umbrella Chart repository. The workflow will
+automatically release a Chart, once it is pushed to the "charts/" directory with a new Chart version.
+
+#### Capability Bundle Structure
+
+Capability bundle modularization for the Tractus-X Umbrella Helm chart is a sound architectural and operational design.
+It aligns with both the domain-driven architecture of Catena-X (data exchange, digital twin, identity, semantics are
+distinct domains) and with Kubernetes best practices for managing complex applications (using an umbrella chart to
+bundle related microservices).
+
+Each bundle is self-sufficient, which improves isolation (failures or changes in one domain have minimal impact on
+others) and allows scaling and upgrading along domain lines. It simplifies deployment by allowing “plug-and-play”
+capabilities: an Enablement Service Provider can decide which bundles to operate based on its role e.g., include the
+Digital Twin and Semantic bundles if offering an asset-rich service, or omit them if not. The approach is consistent
+with how other OSS projects deliver multi-component systems, providing one-step installation without sacrificing the
+ability to tweak individual parts.
+
+Why this structure was proposed:
+
+1. **Clear Separation of Concerns**  
+   Each capability bundle (e.g. EDC Data Transfer, Digital Twin, Identity & Trust, Semantic Model) aligns with a
+   specific functional domain. This separation makes it easier to understand the role of each service (e.g., the EDC
+   connector vs. the digital twin registry), reduces coupling between unrelated components, and ultimately makes
+   maintenance and troubleshooting more straightforward.
+2. **Modular Deployment**  
+   Some participants in Catena-X may not need all services (e.g., some might not use the Digital Twin bundle). By
+   structuring the umbrella chart into bundles, a user can enable just those needed capabilities. This leads to leaner
+   installs and avoids unnecessary resource usage.
+3. **Best Practices with Helm**  
+   Using an umbrella chart with subcharts/bundles is a well-recognized Helm best practice for complex applications. It
+   allows a single helm install to set up multiple microservices while still allowing each service to have its own
+   lifecycle, configuration, and version.
+4. **Alignment with Domain-Driven Approach**  
+   Catena-X is organized around distinct, loosely-coupled “building blocks.” Bundling services by domain matches this
+   architectural vision. It’s clear which domain each set of microservices belongs to (EDC for data exchange, identity
+   for credential management, etc.). This clarity also helps new adopters navigate the ecosystem.
+
+````mermaid
+flowchart LR
+    subgraph "Core Services"
+        Vault["Vault"]
+    end
+
+    subgraph "Capability Bundle: Identity & Trust"
+        SSIWalletStub["SSI Wallet Stub"]
+    end
+
+    subgraph "Capability Bundle: Dataspace Connector"
+        EDC["EDC"]
+        EDCDB["EDC DB"]
+    end
+
+    subgraph "Capability Bundle: Digital Twin"
+        DTR["DTR"]
+        DTRDB["DTR DB"]
+    end
+
+    subgraph "Capability Bundle: Data Persitence Layer"
+        SimpleSubmodelServer["Simple Submodel Server"]
+    end
+
+    subgraph "Hausanschluss Bundles"
+        subgraph "Data Provider"
+            DataProvider["Data Provider"]
+        end
+        subgraph "Data Consumer"
+            DataConsumer["Data Consumer"]
+        end
+        subgraph "Enablement Provider"
+            EnablementProvider["Enablement Provider"]
+        end
+    end
+
+    EDC -.-> SSIWalletStub
+    EDC -.-> Vault
+    DataProvider --> EDC
+    DataProvider --> DTR
+    DataProvider --> SimpleSubmodelServer
+    DataConsumer --> EDC
+    EnablementProvider --> DataConsumer
+    EnablementProvider --> DataProvider
+
+````
+
+#### Deployment strategies
+
+##### Role: Data Provider
+
+The standard data provider role consists of a EDC, DTR and Submodel Server Bundles. EDC uses the Identity Wallet Bundle.
+
+````mermaid
+flowchart BT
+    A["Capability Bundle: Identity & Trust"]
+    B["Capability Bundle: Data Persistence Layer"]
+    C["Capability Bundle: Dataspace Connector"]
+    D["Capability Bundle: Digital Twin"]
+    E["Application to be tested/developed"]
+    E --> B
+    E --> C
+    E --> D
+    C --> A
+````
+
+##### Role: Data Consumer
+
+The standard data consumer role consists of only the EDC Bundle and the Identity Wallet Bundle.
+
+````mermaid
+flowchart BT
+    A["Capability Bundle: Identity & Trust"]
+    B["Capability Bundle: Dataspace Connector"]
+    C["Application to be tested/developed"]
+    C --> B
+    B --> A
+
+````
+
+##### Role: Enablement Provider
+
+The Enablement Provider roles consists of both the Data Consumer and Data Provider bundles. This allows provisioning of
+data and the consumtion of the provisioned data by a application.
+
+````mermaid
+flowchart BT
+    A["Capability Bundle: Identity & Trust"]
path: docs/concept/TAP7.1-solution-design.md
user: login: mkanal
body: Please Add Actors to visualize the roles data consumer, data provier and enablement provider
created_at: 2025-03-28T13:42:38Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,425 @@
+# [TAP 7.1] Solution Design Hausanschluss Bundle Konzept
+
+# 1 Business Case
+
+## 1.1 Executive Summary
+
+The EDC "Hausanschluss" Bundle aims to simplify the installation of the enablement services Eclipse Dataspace
+Connector (EDC), Digital Twin Registry (DTR), and their supporting components. By developing a flexible, parameterizable
+installation package, the project seeks to reduce deployment complexity and lower barriers to participation in the
+Catena‑X data space. This bundle will enable independent component updates and support a modular "bring your own"
+approach, ultimately fostering a more efficient and accessible ecosystem for diverse participants—such as testers,
+external developers, and small and medium-sized enterprises.
+
+## 1.2 Business Need
+
+Current deployment methods for data space integration are complex and require significant manual effort. This PoC
+addresses the need to:
+
+- Reduce Complexity: Simplify the deployment topology by bundling components into capabilities.
+- Automate Deployment: Provide an automated installation package using Kubernetes and HELM.
+- Reduce Configuration Efforts: Streamline and reduce the number of configuration steps required for integration.
+- Extend Documentation: Provide a detailed documentation tailored to the target groups.
+- Enable Extension: Design the system to allow the seamless addition of new components or capabilities.
+
+## 1.3 Objectives
+
+- Simplify Deployment and Maintenance: Develop an installation package that minimizes manual configuration through
+  automation.
+- Ensure Modularity: Structure the bundle so that components can be independently installed, updated, or replaced
+  without
+  affecting other services.
+- Facilitate Flexibility: Implement a "bring your own" model for key components, such as EDC, PostgreSQL, and HashiCorp
+  Vault, to allow tailored deployments that meet specific needs.
+- Increase Accessibility: Lower entry barriers for new participants by reducing technical complexity and operational
+  dependencies.
+- Scalability: Structure the bundle so that it can be deployed multiple times.
+
+## 1.4 Expected Deliverables
+
+- PoC Documentation: A concept and architecture overview highlighting the modular design.
+- Modular Installation Package: A set of HELM charts for deploying the enablement service bundles:
+    - EDC Bundle: Including the Eclipse Dataspace Connector, EDC PostgreSQL, and HashiCorp Vault.
+    - Digital Twin Bundle: Featuring components such as the Decentral DT Registry (with “bring your own” PostgreSQL) and
+      a Submodel Server Bundle.
+    - Identity Wallet Bundle: Covering the Identity Wallet functionality.
+- Demonstration Environment: A test deployment showcasing reduced complexity and improved efficiency.
+- Basic User Guide: Instructions on how to deploy and update the PoC bundle.
+
+## 1.5 Benefits
+
+- Operational Efficiency: Faster and more reliable deployments with less manual work.
+- Scalability: A modular design that can be scaled or adapted for future full-scale deployments.
+- Ease of Adoption: Simplified deployment processes make it easier for testers and external developers to engage.
+
+## 1.6. Dependencies
+
+- Interoperability with the CATENA‑X standards.
+
+## 1.7. Success Criteria
+
+- Technology Readiness Level: Achievement of a Technology Readiness Level (TRL) of 3, as specified in the requirements.
+- Functional PoC Deployment: Demonstrated automated, modular installation with reduced manual steps.
+- Simplified Configuration: Clear evidence of reduced configuration complexity.
+- Positive Feedback: End-user validation from a select group of demo participants and the Tractus-X community.
+- Documentation Completeness: Availability of concise deployment and user guides.
+
+## 1.8. Out of Scope
+
+- Full Production Readiness: This PoC is not intended to be a production-ready solution.
+- Core Services Exclusion: Core services are not part of the Hausanschluss Bundles.
+- App Provider Role: The role of App Provider is considered out of scope for this deployment.
+- Alternative Deployment Techniques: While the evaluation of alternative deployment methods is acknowledged, the primary
+  focus remains on Kubernetes and HELM-based deployment.
+
+# 2 Requirements Analysis
+
+## 2.1 Assumptions
+
+## 2.2 Requirements Catalog
+
+| ID             | Requirement                                                                                                                                                                                                                                                                                                                                               | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | Deliverables / Acceptance Criteria                                                                                                           |
+|----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------|
+| [WP-7.1.-D001] | TAP7.1 Hausanschluss Bundle aims to simplify the installation and maintenance of the EDC and other components that together ensure a “home connection”. A flexible, parameterizable installation package is intended to reduce complexity and make integration more efficient, thereby simplifying participation in Catena‑X for additional participants. | Specification and development of a flexible, parameterizable installation package that reduces the complexity of installing and maintaining the required components for seamless integration into the Catena‑X data space. This package should facilitate updates and new versions, making participation in Catena‑X more efficient and accessible. In doing so, SMEs shall be enabled to participate without high costs or dependency on SaaS providers while maintaining control over their IT infrastructure. | [WP-7.1.-D001] Concept for the Hausanschluss is created                                                                                      |
+| 7.1.1.1        | The solution concept must define the Capability Bundles structures to be implemented. For each Capability Bundle, the included bundles and their versions are mapped.                                                                                                                                                                                     | "The following Capability Bundle structure is implemented:                                                                                                                                                                                                                                                                                                                                                                                                                                                       | "The structure of the Capability Bundles for the Enablement Services has been specified.                                                     |
+| 7.1.1.2        | Definition of Data Space Roles                                                                                                                                                                                                                                                                                                                            | Capability EDC (Data Transfer) Bundle                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | For version R24.12 it is clearly defined which Tractus‑X services and components are assigned to each Capability Bundle"                     |
+| 7.1.1.4        | Modularity & Maintainability: No dependencies between Capability Bundles                                                                                                                                                                                                                                                                                  | Eclipse Dataspace Connector (EDC) v0.9.0                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | "As part of the target group analysis, the target groups are defined and aligned with the data space roles.                                  |
+| 7.1.1.5        | Modularity & Maintainability: Concept for reducing deployment complexity                                                                                                                                                                                                                                                                                  | EDC PostgresSQL                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | Mapping from data space role to target group has been completed.                                                                             |
+| 7.1.1.6        | Modularity & Maintainability                                                                                                                                                                                                                                                                                                                              | HashiCorp Vault                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | Mapping from target group to data space role has been completed.                                                                             |
+| 7.1.1.13       | Solution Concept                                                                                                                                                                                                                                                                                                                                          | Capability Digital Twin Bundle                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | An assignment of data space roles to Capability Bundles has been made."                                                                      |
+| 7.1.1.14       | Scalability of Enablement Services                                                                                                                                                                                                                                                                                                                        | Decentral DT Registry                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | "Components and Services should obly be part of one bundle.                                                                                  |
+| 7.1.1.16       | Interoperability                                                                                                                                                                                                                                                                                                                                          | PostgresSQL                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | Each bundle must be deployable in isolation and can be installed, updated, or removed independently.                                         |
+| [WP-7.1.-D002] | [WP-7.1.-D002] Target group for the specification is defined.                                                                                                                                                                                                                                                                                             | Capability Identity & Trust (Identity Wallet Bundle)                                                                                                                                                                                                                                                                                                                                                                                                                                                             | Capability Bundles must be organized in separate HELM sub‑charts.                                                                            |
+| 7.1.2.1        | Target Group Analysis                                                                                                                                                                                                                                                                                                                                     | Identity Wallet Mock                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | Circular dependencies between bundles must be avoided."                                                                                      |
+| [WP-7.1.-D003] | [WP-7.1.-D003] Decentralized components and services defined                                                                                                                                                                                                                                                                                              | Capability Semantic Model Bundle                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | "Simplification of deployment processes                                                                                                      |
+| 7.1.3.1        | See [WP-7.1.-D001-AC001]                                                                                                                                                                                                                                                                                                                                  | Submodel Mock (aus Umbrella HELM Chart)"                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | A reduction of manual configuration steps has been achieved.                                                                                 |
+| [WP-7.1.-D004] | [WP-7.1.-D004] Documentation of the Hausanschluss Bundle is completed                                                                                                                                                                                                                                                                                     | "Data Consumer                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | Transparency and traceability                                                                                                                |
+| 7.1.4.1        | Documentation of the Hausanschluss-Bundles                                                                                                                                                                                                                                                                                                                | Data Provider                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | Clearly documented deployment steps are provided.                                                                                            |
+| 7.1.4.2        | Documentation of the Hausanschluss-Bundles                                                                                                                                                                                                                                                                                                                | Enablement Service Provider"                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | Improvements of Chart configuration by                                                                                                       |
+| [WP-7.1.-D005] | [WP-7.1.-D005] Umbrella HELM Charts for the Hausanschluss developed, tested, and documented                                                                                                                                                                                                                                                               | "Unique assignment of components and services to a defined Capability Bundle.                                                                                                                                                                                                                                                                                                                                                                                                                                    | usage of template                                                                                                                            |
+| 7.1.5.1        | Re-activate Umbrella HELM Charts to the latest release state                                                                                                                                                                                                                                                                                              | Each component and service should be assigned to only one Capability Bundle.                                                                                                                                                                                                                                                                                                                                                                                                                                     | reducing configuration options                                                                                                               |
+| 7.1.5.2        | Hierarchical structuring and bundling of Enablement Service components in the Umbrella HELM Chart                                                                                                                                                                                                                                                         | Dependencies between Capability Bundles are allowed."                                                                                                                                                                                                                                                                                                                                                                                                                                                            | reducing manual steps in the setup"                                                                                                          |
+| 7.1.5.3        | Interchangeability of bundle components via “Bring-Your-Own” components                                                                                                                                                                                                                                                                                   | The system deployment should be optimized to reduce the existing complexity. The goal is to make the provisioning process more efficient, robust, and easier to maintain.                                                                                                                                                                                                                                                                                                                                        | Charts are published via a publicly accessible charts repository.                                                                            |
+| [WP-7.1.-D006] | [WP-7.1.-D006] Product developed according to a Technology Readiness Level (TRL) of 3                                                                                                                                                                                                                                                                     | Charts are published automatically.                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | "The solution design for the ""Hausanschluss"" Bundle is created.                                                                            |
+| 7.1.6.1        | POC                                                                                                                                                                                                                                                                                                                                                       | Creation of a solution design for the “Hausanschluss” Bundle.                                                                                                                                                                                                                                                                                                                                                                                                                                                    | The solution design for the ""Hausanschluss"" Bundle ispublished in the repository: https://github.com/eclipse-tractusx/tractus-x-umbrella." |
+| 7.1.6.2        | Deployment Strategy                                                                                                                                                                                                                                                                                                                                       | Scalability of Enablement Services                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | "Developers should be able to deploy an arbitrary number of Enablement Services.                                                             |
+
+# 3 AS-IS Analysis
+
+## 3.1 People
+
+### 3.1.1 Target Group Analysis
+
+See "4.1.1 To-be Target Group Analysis" below. No deviations between As-is and To-be target groups have been identified.
+
+## 3.2 Process
+
+### 3.2.1 Use Case View (high-level)
+
+Umbrella Chart is intended for the following Use Cases:
+
+| Actor             | Use case                                                                                             |
+|-------------------|------------------------------------------------------------------------------------------------------|
+| Product Developer | Sandbox Environments: Create local environments to evaluate and experiment with Catena-X components. |
+| Product Developer | Development: Provide a unified setup for contributors and developers working on Tractus-X projects.  |
+| Product Tester    | Testing: Run end-to-end tests for Catena-X services.                                                 |
+
+## 3.4 System
+
+### 3.4.1 Context Delimitation
+
+````mermaid
+flowchart
+    subgraph "Umbrella Chart"
+        ChartYaml["Chart.yaml"]
+        subgraph charts
+            Portal["Portal"]
+            CentralIdp["CentralIdp"]
+            DiscoveryFinder["Discovery Finder"]
+            SDFactory["SD-Factory"]
+            SSICredentialIssuer["SSI Credential Issuer"]
+            SemanticHub["Semantic Hub"]
+            BPDM["BPDM"]
+            DataConsumer["Data Consumer"]
+            DataProvider["Data Provider"]
+            BDRS["BDRS"]
+            SSIWalletStub["SSI Wallet Stub"]
+        end
+        subgraph "tx-data-provider"
+            EDC["EDC"]
+            DTR["DTR"]
+            SubmodelServer["Submodel Server"]
+        end
+    end
+
+    ChartYaml --> Portal
+    ChartYaml --> CentralIdp
+    ChartYaml --> DiscoveryFinder
+    ChartYaml --> SDFactory
+    ChartYaml --> SSICredentialIssuer
+    ChartYaml --> SemanticHub
+    ChartYaml --> BPDM
+    ChartYaml --> DataConsumer
+    ChartYaml --> DataProvider
+    ChartYaml --> BDRS
+    ChartYaml --> SSIWalletStub
+    DataConsumer --> EDC
+    DataProvider --> EDC
+    DataProvider --> DTR
+    DataProvider --> SubmodelServer
+````
+
+#### Existing Umbrella Chart Structure
+
+# 4 TO-BE Design
+
+## 4.1 People
+
+### 4.1.1 Target Group Analysis
+
+Overall data space roles: https://catena-x.net/en/1/catena-x-introduce-implement/how-to-operate-catena-x
+
+The relevant data space roles for us under requirement 7.1.1.1 are:
+
+- Data Consumer
+- Data Provider
+- Enablement Service Provider
+
+Scope: Umbrella HELM Charts
+
+- Enablement Services: These services are included under the umbrella of HELM charts, focusing on enabling
+  functionalities.
+- Out of Scope: Core services such as Portal or BPDM are not considered within this scope.
+
+Primary target groups:
+
+| No. | Target group                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | Data space roles                                                    | Target group differentiation                                                                                                                                                                                                                                                                            | Behaviour, Needs, Pains & Usage                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+|-----|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| 1   | Developers<ul><li>External Developers (not Tractus-X developers): Utilize the chart for demonstration or evaluation purposes.</li><li>Experienced software and product developers who are developing a business app for a CATENA-X data space. They need to develop the app against the interfaces of the data space and integrate them accordingly.</li><li>They emphasize efficient and cost-effective implementation:<ul><li>Cost Efficiency: They do not want to use expensive SaaS solutions.</li><li>Technical Independence: They lack the knowledge and capacity to deploy the enablement and core services of the data space themselves.</li><li>Focus on Development: They concentrate on application development without delving deeply into the deployment and operation of the underlying infrastructure.</li></ul></li><li>Out of Scope: Developers running tests in test runners are not considered within this scope.</li></ul> | Data Consumer <br/> Data Provider <br/> Enablement Service Provider |                                                                                                                                                                                                                                                                                                         | <ul><li>Needs / sources of information<ul><li><a href="https://eclipse-tractusx.github.io/Kits/">Kit documentation tractus-x</a> for interaction purposes</li><li><a href="https://catenax-ev.github.io/">Catena-X doucmentation</a> for standards and regulations</li><li><a href="https://github.com/eclipse-tractusx/tractus-x-umbrella">Umbrella documentation</a> for umbrella component information</li></ul></li><li>Challenges → Solution<ul><li>Decentralization e.g. Where are other systems? How to interact with them? → Solution: Umbrella charts and bundles for deployment</li><li>Complex setup → Solution: delivery of small capability bundles</li></ul></li></ul> |
path: docs/concept/TAP7.1-solution-design.md
user: login: ds-jhartmann
body: Unfortunately, that is the only possibility to include a list in the table. 
created_at: 2025-03-31T07:31:16Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,425 @@
+# [TAP 7.1] Solution Design Hausanschluss Bundle Konzept
+
+# 1 Business Case
+
+## 1.1 Executive Summary
+
+The EDC "Hausanschluss" Bundle aims to simplify the installation of the enablement services Eclipse Dataspace
+Connector (EDC), Digital Twin Registry (DTR), and their supporting components. By developing a flexible, parameterizable
+installation package, the project seeks to reduce deployment complexity and lower barriers to participation in the
+Catena‑X data space. This bundle will enable independent component updates and support a modular "bring your own"
+approach, ultimately fostering a more efficient and accessible ecosystem for diverse participants—such as testers,
+external developers, and small and medium-sized enterprises.
+
+## 1.2 Business Need
+
+Current deployment methods for data space integration are complex and require significant manual effort. This PoC
+addresses the need to:
+
+- Reduce Complexity: Simplify the deployment topology by bundling components into capabilities.
+- Automate Deployment: Provide an automated installation package using Kubernetes and HELM.
+- Reduce Configuration Efforts: Streamline and reduce the number of configuration steps required for integration.
+- Extend Documentation: Provide a detailed documentation tailored to the target groups.
+- Enable Extension: Design the system to allow the seamless addition of new components or capabilities.
+
+## 1.3 Objectives
+
+- Simplify Deployment and Maintenance: Develop an installation package that minimizes manual configuration through
+  automation.
+- Ensure Modularity: Structure the bundle so that components can be independently installed, updated, or replaced
+  without
+  affecting other services.
+- Facilitate Flexibility: Implement a "bring your own" model for key components, such as EDC, PostgreSQL, and HashiCorp
+  Vault, to allow tailored deployments that meet specific needs.
+- Increase Accessibility: Lower entry barriers for new participants by reducing technical complexity and operational
+  dependencies.
+- Scalability: Structure the bundle so that it can be deployed multiple times.
+
+## 1.4 Expected Deliverables
+
+- PoC Documentation: A concept and architecture overview highlighting the modular design.
+- Modular Installation Package: A set of HELM charts for deploying the enablement service bundles:
+    - EDC Bundle: Including the Eclipse Dataspace Connector, EDC PostgreSQL, and HashiCorp Vault.
+    - Digital Twin Bundle: Featuring components such as the Decentral DT Registry (with “bring your own” PostgreSQL) and
+      a Submodel Server Bundle.
+    - Identity Wallet Bundle: Covering the Identity Wallet functionality.
+- Demonstration Environment: A test deployment showcasing reduced complexity and improved efficiency.
+- Basic User Guide: Instructions on how to deploy and update the PoC bundle.
+
+## 1.5 Benefits
+
+- Operational Efficiency: Faster and more reliable deployments with less manual work.
+- Scalability: A modular design that can be scaled or adapted for future full-scale deployments.
+- Ease of Adoption: Simplified deployment processes make it easier for testers and external developers to engage.
+
+## 1.6. Dependencies
+
+- Interoperability with the CATENA‑X standards.
+
+## 1.7. Success Criteria
+
+- Technology Readiness Level: Achievement of a Technology Readiness Level (TRL) of 3, as specified in the requirements.
+- Functional PoC Deployment: Demonstrated automated, modular installation with reduced manual steps.
+- Simplified Configuration: Clear evidence of reduced configuration complexity.
+- Positive Feedback: End-user validation from a select group of demo participants and the Tractus-X community.
+- Documentation Completeness: Availability of concise deployment and user guides.
+
+## 1.8. Out of Scope
+
+- Full Production Readiness: This PoC is not intended to be a production-ready solution.
+- Core Services Exclusion: Core services are not part of the Hausanschluss Bundles.
+- App Provider Role: The role of App Provider is considered out of scope for this deployment.
+- Alternative Deployment Techniques: While the evaluation of alternative deployment methods is acknowledged, the primary
+  focus remains on Kubernetes and HELM-based deployment.
+
+# 2 Requirements Analysis
+
+## 2.1 Assumptions
+
+## 2.2 Requirements Catalog
+
+| ID             | Requirement                                                                                                                                                                                                                                                                                                                                               | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | Deliverables / Acceptance Criteria                                                                                                           |
+|----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------|
+| [WP-7.1.-D001] | TAP7.1 Hausanschluss Bundle aims to simplify the installation and maintenance of the EDC and other components that together ensure a “home connection”. A flexible, parameterizable installation package is intended to reduce complexity and make integration more efficient, thereby simplifying participation in Catena‑X for additional participants. | Specification and development of a flexible, parameterizable installation package that reduces the complexity of installing and maintaining the required components for seamless integration into the Catena‑X data space. This package should facilitate updates and new versions, making participation in Catena‑X more efficient and accessible. In doing so, SMEs shall be enabled to participate without high costs or dependency on SaaS providers while maintaining control over their IT infrastructure. | [WP-7.1.-D001] Concept for the Hausanschluss is created                                                                                      |
+| 7.1.1.1        | The solution concept must define the Capability Bundles structures to be implemented. For each Capability Bundle, the included bundles and their versions are mapped.                                                                                                                                                                                     | "The following Capability Bundle structure is implemented:                                                                                                                                                                                                                                                                                                                                                                                                                                                       | "The structure of the Capability Bundles for the Enablement Services has been specified.                                                     |
+| 7.1.1.2        | Definition of Data Space Roles                                                                                                                                                                                                                                                                                                                            | Capability EDC (Data Transfer) Bundle                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | For version R24.12 it is clearly defined which Tractus‑X services and components are assigned to each Capability Bundle"                     |
+| 7.1.1.4        | Modularity & Maintainability: No dependencies between Capability Bundles                                                                                                                                                                                                                                                                                  | Eclipse Dataspace Connector (EDC) v0.9.0                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | "As part of the target group analysis, the target groups are defined and aligned with the data space roles.                                  |
+| 7.1.1.5        | Modularity & Maintainability: Concept for reducing deployment complexity                                                                                                                                                                                                                                                                                  | EDC PostgresSQL                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | Mapping from data space role to target group has been completed.                                                                             |
+| 7.1.1.6        | Modularity & Maintainability                                                                                                                                                                                                                                                                                                                              | HashiCorp Vault                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | Mapping from target group to data space role has been completed.                                                                             |
+| 7.1.1.13       | Solution Concept                                                                                                                                                                                                                                                                                                                                          | Capability Digital Twin Bundle                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | An assignment of data space roles to Capability Bundles has been made."                                                                      |
+| 7.1.1.14       | Scalability of Enablement Services                                                                                                                                                                                                                                                                                                                        | Decentral DT Registry                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | "Components and Services should obly be part of one bundle.                                                                                  |
+| 7.1.1.16       | Interoperability                                                                                                                                                                                                                                                                                                                                          | PostgresSQL                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | Each bundle must be deployable in isolation and can be installed, updated, or removed independently.                                         |
+| [WP-7.1.-D002] | [WP-7.1.-D002] Target group for the specification is defined.                                                                                                                                                                                                                                                                                             | Capability Identity & Trust (Identity Wallet Bundle)                                                                                                                                                                                                                                                                                                                                                                                                                                                             | Capability Bundles must be organized in separate HELM sub‑charts.                                                                            |
+| 7.1.2.1        | Target Group Analysis                                                                                                                                                                                                                                                                                                                                     | Identity Wallet Mock                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | Circular dependencies between bundles must be avoided."                                                                                      |
+| [WP-7.1.-D003] | [WP-7.1.-D003] Decentralized components and services defined                                                                                                                                                                                                                                                                                              | Capability Semantic Model Bundle                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | "Simplification of deployment processes                                                                                                      |
+| 7.1.3.1        | See [WP-7.1.-D001-AC001]                                                                                                                                                                                                                                                                                                                                  | Submodel Mock (aus Umbrella HELM Chart)"                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | A reduction of manual configuration steps has been achieved.                                                                                 |
+| [WP-7.1.-D004] | [WP-7.1.-D004] Documentation of the Hausanschluss Bundle is completed                                                                                                                                                                                                                                                                                     | "Data Consumer                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | Transparency and traceability                                                                                                                |
+| 7.1.4.1        | Documentation of the Hausanschluss-Bundles                                                                                                                                                                                                                                                                                                                | Data Provider                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | Clearly documented deployment steps are provided.                                                                                            |
+| 7.1.4.2        | Documentation of the Hausanschluss-Bundles                                                                                                                                                                                                                                                                                                                | Enablement Service Provider"                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | Improvements of Chart configuration by                                                                                                       |
+| [WP-7.1.-D005] | [WP-7.1.-D005] Umbrella HELM Charts for the Hausanschluss developed, tested, and documented                                                                                                                                                                                                                                                               | "Unique assignment of components and services to a defined Capability Bundle.                                                                                                                                                                                                                                                                                                                                                                                                                                    | usage of template                                                                                                                            |
+| 7.1.5.1        | Re-activate Umbrella HELM Charts to the latest release state                                                                                                                                                                                                                                                                                              | Each component and service should be assigned to only one Capability Bundle.                                                                                                                                                                                                                                                                                                                                                                                                                                     | reducing configuration options                                                                                                               |
+| 7.1.5.2        | Hierarchical structuring and bundling of Enablement Service components in the Umbrella HELM Chart                                                                                                                                                                                                                                                         | Dependencies between Capability Bundles are allowed."                                                                                                                                                                                                                                                                                                                                                                                                                                                            | reducing manual steps in the setup"                                                                                                          |
+| 7.1.5.3        | Interchangeability of bundle components via “Bring-Your-Own” components                                                                                                                                                                                                                                                                                   | The system deployment should be optimized to reduce the existing complexity. The goal is to make the provisioning process more efficient, robust, and easier to maintain.                                                                                                                                                                                                                                                                                                                                        | Charts are published via a publicly accessible charts repository.                                                                            |
+| [WP-7.1.-D006] | [WP-7.1.-D006] Product developed according to a Technology Readiness Level (TRL) of 3                                                                                                                                                                                                                                                                     | Charts are published automatically.                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | "The solution design for the ""Hausanschluss"" Bundle is created.                                                                            |
+| 7.1.6.1        | POC                                                                                                                                                                                                                                                                                                                                                       | Creation of a solution design for the “Hausanschluss” Bundle.                                                                                                                                                                                                                                                                                                                                                                                                                                                    | The solution design for the ""Hausanschluss"" Bundle ispublished in the repository: https://github.com/eclipse-tractusx/tractus-x-umbrella." |
+| 7.1.6.2        | Deployment Strategy                                                                                                                                                                                                                                                                                                                                       | Scalability of Enablement Services                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | "Developers should be able to deploy an arbitrary number of Enablement Services.                                                             |
+
+# 3 AS-IS Analysis
+
+## 3.1 People
+
+### 3.1.1 Target Group Analysis
+
+See "4.1.1 To-be Target Group Analysis" below. No deviations between As-is and To-be target groups have been identified.
+
+## 3.2 Process
+
+### 3.2.1 Use Case View (high-level)
+
+Umbrella Chart is intended for the following Use Cases:
+
+| Actor             | Use case                                                                                             |
+|-------------------|------------------------------------------------------------------------------------------------------|
+| Product Developer | Sandbox Environments: Create local environments to evaluate and experiment with Catena-X components. |
+| Product Developer | Development: Provide a unified setup for contributors and developers working on Tractus-X projects.  |
+| Product Tester    | Testing: Run end-to-end tests for Catena-X services.                                                 |
+
+## 3.4 System
+
+### 3.4.1 Context Delimitation
+
+````mermaid
+flowchart
+    subgraph "Umbrella Chart"
+        ChartYaml["Chart.yaml"]
+        subgraph charts
+            Portal["Portal"]
+            CentralIdp["CentralIdp"]
+            DiscoveryFinder["Discovery Finder"]
+            SDFactory["SD-Factory"]
+            SSICredentialIssuer["SSI Credential Issuer"]
+            SemanticHub["Semantic Hub"]
+            BPDM["BPDM"]
+            DataConsumer["Data Consumer"]
+            DataProvider["Data Provider"]
+            BDRS["BDRS"]
+            SSIWalletStub["SSI Wallet Stub"]
+        end
+        subgraph "tx-data-provider"
+            EDC["EDC"]
+            DTR["DTR"]
+            SubmodelServer["Submodel Server"]
+        end
+    end
+
+    ChartYaml --> Portal
+    ChartYaml --> CentralIdp
+    ChartYaml --> DiscoveryFinder
+    ChartYaml --> SDFactory
+    ChartYaml --> SSICredentialIssuer
+    ChartYaml --> SemanticHub
+    ChartYaml --> BPDM
+    ChartYaml --> DataConsumer
+    ChartYaml --> DataProvider
+    ChartYaml --> BDRS
+    ChartYaml --> SSIWalletStub
+    DataConsumer --> EDC
+    DataProvider --> EDC
+    DataProvider --> DTR
+    DataProvider --> SubmodelServer
+````
+
+#### Existing Umbrella Chart Structure
+
+# 4 TO-BE Design
+
+## 4.1 People
+
+### 4.1.1 Target Group Analysis
+
+Overall data space roles: https://catena-x.net/en/1/catena-x-introduce-implement/how-to-operate-catena-x
+
+The relevant data space roles for us under requirement 7.1.1.1 are:
+
+- Data Consumer
+- Data Provider
+- Enablement Service Provider
+
+Scope: Umbrella HELM Charts
+
+- Enablement Services: These services are included under the umbrella of HELM charts, focusing on enabling
+  functionalities.
+- Out of Scope: Core services such as Portal or BPDM are not considered within this scope.
+
+Primary target groups:
+
+| No. | Target group                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | Data space roles                                                    | Target group differentiation                                                                                                                                                                                                                                                                            | Behaviour, Needs, Pains & Usage                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+|-----|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| 1   | Developers<ul><li>External Developers (not Tractus-X developers): Utilize the chart for demonstration or evaluation purposes.</li><li>Experienced software and product developers who are developing a business app for a CATENA-X data space. They need to develop the app against the interfaces of the data space and integrate them accordingly.</li><li>They emphasize efficient and cost-effective implementation:<ul><li>Cost Efficiency: They do not want to use expensive SaaS solutions.</li><li>Technical Independence: They lack the knowledge and capacity to deploy the enablement and core services of the data space themselves.</li><li>Focus on Development: They concentrate on application development without delving deeply into the deployment and operation of the underlying infrastructure.</li></ul></li><li>Out of Scope: Developers running tests in test runners are not considered within this scope.</li></ul> | Data Consumer <br/> Data Provider <br/> Enablement Service Provider |                                                                                                                                                                                                                                                                                                         | <ul><li>Needs / sources of information<ul><li><a href="https://eclipse-tractusx.github.io/Kits/">Kit documentation tractus-x</a> for interaction purposes</li><li><a href="https://catenax-ev.github.io/">Catena-X doucmentation</a> for standards and regulations</li><li><a href="https://github.com/eclipse-tractusx/tractus-x-umbrella">Umbrella documentation</a> for umbrella component information</li></ul></li><li>Challenges → Solution<ul><li>Decentralization e.g. Where are other systems? How to interact with them? → Solution: Umbrella charts and bundles for deployment</li><li>Complex setup → Solution: delivery of small capability bundles</li></ul></li></ul> |
+| 2   | <ul><li>Tester requiring a test system (Testmanagement e.V.)</li><li>Requirement: Testbed</li></ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | Data Consumer <br/> Data Provider <br/> Enablement Service Provider | <ul><li>Developer (1) tests their feature.</li><li>Tester (2) performs end-to-end testing.</li><li>For the tester, the modular structure is less relevant since they focus on E2E testing, whereas the developer selects the required components.</li><li>The testbed must be easy to deploy.</li></ul> | <ul><li>Same as above from an End-to-end testing perspective</li><li>Typically a tester has less technical know-how than a developer and therefore needs a "one-size-fits-all" chart for easier testing</li></ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+
+## 4.2 Process
+
+### 4.2.1 Use Case View (high-level)
+
+| Use Case                                | Description                                                                                                       | Actors            |
+|-----------------------------------------|-------------------------------------------------------------------------------------------------------------------|-------------------|
+| Configure HELM Chart                    | The product developer configures the HELM Chart for the specific environment.                                     | Product Developer |
+| Configure Secrets                       | The product developer manages and configures secrets.                                                             | Product Developer |
+| Execute Deployment Pipeline             | The product developer successfully executes the deployment pipeline for the HELM Chart.                           | Product Developer |
+| Integrate EDC, DTR, and Identity Wallet | The actors integrate the components EDC, Digital Twin Registry, and Identity Wallet for seamless interoperability | Product Developer |
+| Set Up Connection Infrastructure        | The actor sets up the connection infrastructure for linking to the central data space infrastructure.             | Product Developer |
+| Maintain Infrastructure Module          | The product developer maintains the modular architecture of the HELM Chart.                                       | Product Developer |
+| Ensure Scalability                      | The product developer ensures scalability to support growing numbers of users and data volumes.                   | Product Developer |
+| Sandbox Environments                    | The product developer creates local environments to evaluate and experiment with Catena-X components.             | Product Developer |
+| E2E Testing                             | The product tester runs end-to-end tests for Catena-X services.                                                   | Product Tester    |
+
+### 4.2.2 Business Process (SCC Artifact)
+
+#### Chart Release Process
+
+Charts will be released using the already existing workflow in the Umbrella Chart repository. The workflow will
+automatically release a Chart, once it is pushed to the "charts/" directory with a new Chart version.
+
+#### Capability Bundle Structure
+
+Capability bundle modularization for the Tractus-X Umbrella Helm chart is a sound architectural and operational design.
+It aligns with both the domain-driven architecture of Catena-X (data exchange, digital twin, identity, semantics are
+distinct domains) and with Kubernetes best practices for managing complex applications (using an umbrella chart to
+bundle related microservices).
+
+Each bundle is self-sufficient, which improves isolation (failures or changes in one domain have minimal impact on
+others) and allows scaling and upgrading along domain lines. It simplifies deployment by allowing “plug-and-play”
+capabilities: an Enablement Service Provider can decide which bundles to operate based on its role e.g., include the
+Digital Twin and Semantic bundles if offering an asset-rich service, or omit them if not. The approach is consistent
+with how other OSS projects deliver multi-component systems, providing one-step installation without sacrificing the
+ability to tweak individual parts.
+
+Why this structure was proposed:
+
+1. **Clear Separation of Concerns**  
+   Each capability bundle (e.g. EDC Data Transfer, Digital Twin, Identity & Trust, Semantic Model) aligns with a
+   specific functional domain. This separation makes it easier to understand the role of each service (e.g., the EDC
+   connector vs. the digital twin registry), reduces coupling between unrelated components, and ultimately makes
+   maintenance and troubleshooting more straightforward.
+2. **Modular Deployment**  
+   Some participants in Catena-X may not need all services (e.g., some might not use the Digital Twin bundle). By
+   structuring the umbrella chart into bundles, a user can enable just those needed capabilities. This leads to leaner
+   installs and avoids unnecessary resource usage.
+3. **Best Practices with Helm**  
+   Using an umbrella chart with subcharts/bundles is a well-recognized Helm best practice for complex applications. It
+   allows a single helm install to set up multiple microservices while still allowing each service to have its own
+   lifecycle, configuration, and version.
+4. **Alignment with Domain-Driven Approach**  
+   Catena-X is organized around distinct, loosely-coupled “building blocks.” Bundling services by domain matches this
+   architectural vision. It’s clear which domain each set of microservices belongs to (EDC for data exchange, identity
+   for credential management, etc.). This clarity also helps new adopters navigate the ecosystem.
+
+````mermaid
+flowchart LR
+    subgraph "Core Services"
+        Vault["Vault"]
+    end
+
+    subgraph "Capability Bundle: Identity & Trust"
+        SSIWalletStub["SSI Wallet Stub"]
+    end
+
+    subgraph "Capability Bundle: Dataspace Connector"
+        EDC["EDC"]
+        EDCDB["EDC DB"]
+    end
+
+    subgraph "Capability Bundle: Digital Twin"
+        DTR["DTR"]
+        DTRDB["DTR DB"]
+    end
+
+    subgraph "Capability Bundle: Data Persitence Layer"
+        SimpleSubmodelServer["Simple Submodel Server"]
+    end
+
+    subgraph "Hausanschluss Bundles"
+        subgraph "Data Provider"
+            DataProvider["Data Provider"]
+        end
+        subgraph "Data Consumer"
+            DataConsumer["Data Consumer"]
+        end
+        subgraph "Enablement Provider"
+            EnablementProvider["Enablement Provider"]
+        end
+    end
+
+    EDC -.-> SSIWalletStub
+    EDC -.-> Vault
+    DataProvider --> EDC
+    DataProvider --> DTR
+    DataProvider --> SimpleSubmodelServer
+    DataConsumer --> EDC
+    EnablementProvider --> DataConsumer
+    EnablementProvider --> DataProvider
+
+````
+
+#### Deployment strategies
+
+##### Role: Data Provider
+
+The standard data provider role consists of a EDC, DTR and Submodel Server Bundles. EDC uses the Identity Wallet Bundle.
+
+````mermaid
+flowchart BT
+    A["Capability Bundle: Identity & Trust"]
+    B["Capability Bundle: Data Persistence Layer"]
+    C["Capability Bundle: Dataspace Connector"]
+    D["Capability Bundle: Digital Twin"]
+    E["Application to be tested/developed"]
+    E --> B
+    E --> C
+    E --> D
+    C --> A
+````
+
+##### Role: Data Consumer
+
+The standard data consumer role consists of only the EDC Bundle and the Identity Wallet Bundle.
+
+````mermaid
+flowchart BT
+    A["Capability Bundle: Identity & Trust"]
+    B["Capability Bundle: Dataspace Connector"]
+    C["Application to be tested/developed"]
+    C --> B
+    B --> A
+
+````
+
+##### Role: Enablement Provider
+
+The Enablement Provider roles consists of both the Data Consumer and Data Provider bundles. This allows provisioning of
+data and the consumtion of the provisioned data by a application.
+
+````mermaid
+flowchart BT
+    A["Capability Bundle: Identity & Trust"]
+    B["Capability Bundle: Data Persitance Layer"]
+    C["Application to be tested/developed"]
+    D["Capability Bundle: Digital Twin"]
+    E["Capability Bundle: Dataspace Connector (Provider)"]
+    F["Capability Bundle: Dataspace Connector (Consumer)"]
+    C --> B
+    C --> D
+    C --> E
+    C --> F
+    E --> A
+    F --> A
+````
+
+##### Bring you own
+
+Each Bundle can be deactivated to use your own component. This requires configuration of the component specific
+parameters in the other components.
+
+In this example this would be the configuration of the Identity Wallet within the EDC.
+
+````mermaid
+flowchart BT
+    A["Application to be tested/developed"]
+    B["Capability Bundle: Dataspace Connector"]
+    C["
Capability Bundle: Identity & Trust
"]
+    D["Own Identity Wallet"]
+    A --> B
+    B -- identitywallet - bundle . enabled = false --> C
+    B -- configure --> D
+
+````
+
+## 4.4 System
+
+### 4.4.1 Context Delimitation / 4.4.2 Interface Documentation
+
+````mermaid
+flowchart LR
+    Dataprovider["Dataprovider"] -->|stores data| SubmodelServer["Submodel Server"]
+    Dataprovider -->|creates twins| DTR["DTR"]
+    Dataprovider -->|creates contracts| EDC["EDC"]
+    Dataconsumer["Dataconsumer"] -->|negotiate contracts| EDC
+    DTR -->|needs| IdentityWallet["Identity Wallet"]
+    IdentityWallet -->|needs| Postgres["PostgreSQL Database"]
+````
+
+# 5 Build
+
+## 5.1 DevOps Setup Definition
+
+### 5.1.1 Tool Chain Definition
path: docs/concept/TAP7.1-solution-design.md
user: login: ds-jhartmann
body: Those are the tools we need to build and publish helm charts. Most of it is already there
created_at: 2025-03-31T07:32:10Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,425 @@
+# [TAP 7.1] Solution Design Hausanschluss Bundle Konzept
+
+# 1 Business Case
+
+## 1.1 Executive Summary
+
+The EDC "Hausanschluss" Bundle aims to simplify the installation of the enablement services Eclipse Dataspace
+Connector (EDC), Digital Twin Registry (DTR), and their supporting components. By developing a flexible, parameterizable
+installation package, the project seeks to reduce deployment complexity and lower barriers to participation in the
+Catena‑X data space. This bundle will enable independent component updates and support a modular "bring your own"
+approach, ultimately fostering a more efficient and accessible ecosystem for diverse participants—such as testers,
+external developers, and small and medium-sized enterprises.
+
+## 1.2 Business Need
+
+Current deployment methods for data space integration are complex and require significant manual effort. This PoC
+addresses the need to:
+
+- Reduce Complexity: Simplify the deployment topology by bundling components into capabilities.
+- Automate Deployment: Provide an automated installation package using Kubernetes and HELM.
+- Reduce Configuration Efforts: Streamline and reduce the number of configuration steps required for integration.
+- Extend Documentation: Provide a detailed documentation tailored to the target groups.
+- Enable Extension: Design the system to allow the seamless addition of new components or capabilities.
+
+## 1.3 Objectives
+
+- Simplify Deployment and Maintenance: Develop an installation package that minimizes manual configuration through
+  automation.
+- Ensure Modularity: Structure the bundle so that components can be independently installed, updated, or replaced
+  without
+  affecting other services.
+- Facilitate Flexibility: Implement a "bring your own" model for key components, such as EDC, PostgreSQL, and HashiCorp
+  Vault, to allow tailored deployments that meet specific needs.
+- Increase Accessibility: Lower entry barriers for new participants by reducing technical complexity and operational
+  dependencies.
+- Scalability: Structure the bundle so that it can be deployed multiple times.
+
+## 1.4 Expected Deliverables
+
+- PoC Documentation: A concept and architecture overview highlighting the modular design.
path: docs/concept/TAP7.1-solution-design.md
user: login: ds-jhartmann
body: User documentation is the last point in this list already
created_at: 2025-03-31T08:00:14Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,425 @@
+# [TAP 7.1] Solution Design Hausanschluss Bundle Konzept
+
+# 1 Business Case
+
+## 1.1 Executive Summary
+
+The EDC "Hausanschluss" Bundle aims to simplify the installation of the enablement services Eclipse Dataspace
+Connector (EDC), Digital Twin Registry (DTR), and their supporting components. By developing a flexible, parameterizable
+installation package, the project seeks to reduce deployment complexity and lower barriers to participation in the
+Catena‑X data space. This bundle will enable independent component updates and support a modular "bring your own"
+approach, ultimately fostering a more efficient and accessible ecosystem for diverse participants—such as testers,
+external developers, and small and medium-sized enterprises.
+
+## 1.2 Business Need
+
+Current deployment methods for data space integration are complex and require significant manual effort. This PoC
+addresses the need to:
+
+- Reduce Complexity: Simplify the deployment topology by bundling components into capabilities.
+- Automate Deployment: Provide an automated installation package using Kubernetes and HELM.
+- Reduce Configuration Efforts: Streamline and reduce the number of configuration steps required for integration.
+- Extend Documentation: Provide a detailed documentation tailored to the target groups.
+- Enable Extension: Design the system to allow the seamless addition of new components or capabilities.
+
+## 1.3 Objectives
+
+- Simplify Deployment and Maintenance: Develop an installation package that minimizes manual configuration through
+  automation.
+- Ensure Modularity: Structure the bundle so that components can be independently installed, updated, or replaced
+  without
+  affecting other services.
+- Facilitate Flexibility: Implement a "bring your own" model for key components, such as EDC, PostgreSQL, and HashiCorp
+  Vault, to allow tailored deployments that meet specific needs.
+- Increase Accessibility: Lower entry barriers for new participants by reducing technical complexity and operational
+  dependencies.
+- Scalability: Structure the bundle so that it can be deployed multiple times.
+
+## 1.4 Expected Deliverables
+
+- PoC Documentation: A concept and architecture overview highlighting the modular design.
path: docs/concept/TAP7.1-solution-design.md
user: login: ds-jhartmann
body: yes, this document it supposed to be the first deliverable
created_at: 2025-03-31T08:00:16Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,425 @@
+# [TAP 7.1] Solution Design Hausanschluss Bundle Konzept
+
+# 1 Business Case
+
+## 1.1 Executive Summary
+
+The EDC "Hausanschluss" Bundle aims to simplify the installation of the enablement services Eclipse Dataspace
+Connector (EDC), Digital Twin Registry (DTR), and their supporting components. By developing a flexible, parameterizable
+installation package, the project seeks to reduce deployment complexity and lower barriers to participation in the
+Catena‑X data space. This bundle will enable independent component updates and support a modular "bring your own"
+approach, ultimately fostering a more efficient and accessible ecosystem for diverse participants—such as testers,
+external developers, and small and medium-sized enterprises.
+
+## 1.2 Business Need
+
+Current deployment methods for data space integration are complex and require significant manual effort. This PoC
+addresses the need to:
+
+- Reduce Complexity: Simplify the deployment topology by bundling components into capabilities.
+- Automate Deployment: Provide an automated installation package using Kubernetes and HELM.
+- Reduce Configuration Efforts: Streamline and reduce the number of configuration steps required for integration.
+- Extend Documentation: Provide a detailed documentation tailored to the target groups.
+- Enable Extension: Design the system to allow the seamless addition of new components or capabilities.
+
+## 1.3 Objectives
+
+- Simplify Deployment and Maintenance: Develop an installation package that minimizes manual configuration through
+  automation.
+- Ensure Modularity: Structure the bundle so that components can be independently installed, updated, or replaced
+  without
+  affecting other services.
+- Facilitate Flexibility: Implement a "bring your own" model for key components, such as EDC, PostgreSQL, and HashiCorp
+  Vault, to allow tailored deployments that meet specific needs.
+- Increase Accessibility: Lower entry barriers for new participants by reducing technical complexity and operational
+  dependencies.
+- Scalability: Structure the bundle so that it can be deployed multiple times.
+
+## 1.4 Expected Deliverables
+
+- PoC Documentation: A concept and architecture overview highlighting the modular design.
+- Modular Installation Package: A set of HELM charts for deploying the enablement service bundles:
+    - EDC Bundle: Including the Eclipse Dataspace Connector, EDC PostgreSQL, and HashiCorp Vault.
+    - Digital Twin Bundle: Featuring components such as the Decentral DT Registry (with “bring your own” PostgreSQL) and
+      a Submodel Server Bundle.
+    - Identity Wallet Bundle: Covering the Identity Wallet functionality.
+- Demonstration Environment: A test deployment showcasing reduced complexity and improved efficiency.
+- Basic User Guide: Instructions on how to deploy and update the PoC bundle.
+
+## 1.5 Benefits
+
+- Operational Efficiency: Faster and more reliable deployments with less manual work.
+- Scalability: A modular design that can be scaled or adapted for future full-scale deployments.
+- Ease of Adoption: Simplified deployment processes make it easier for testers and external developers to engage.
+
+## 1.6. Dependencies
+
+- Interoperability with the CATENA‑X standards.
+
+## 1.7. Success Criteria
+
+- Technology Readiness Level: Achievement of a Technology Readiness Level (TRL) of 3, as specified in the requirements.
+- Functional PoC Deployment: Demonstrated automated, modular installation with reduced manual steps.
+- Simplified Configuration: Clear evidence of reduced configuration complexity.
+- Positive Feedback: End-user validation from a select group of demo participants and the Tractus-X community.
+- Documentation Completeness: Availability of concise deployment and user guides.
+
+## 1.8. Out of Scope
+
+- Full Production Readiness: This PoC is not intended to be a production-ready solution.
+- Core Services Exclusion: Core services are not part of the Hausanschluss Bundles.
+- App Provider Role: The role of App Provider is considered out of scope for this deployment.
+- Alternative Deployment Techniques: While the evaluation of alternative deployment methods is acknowledged, the primary
+  focus remains on Kubernetes and HELM-based deployment.
+
+# 2 Requirements Analysis
+
+## 2.1 Assumptions
+
+## 2.2 Requirements Catalog
+
+| ID             | Requirement                                                                                                                                                                                                                                                                                                                                               | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | Deliverables / Acceptance Criteria                                                                                                           |
+|----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------|
+| [WP-7.1.-D001] | TAP7.1 Hausanschluss Bundle aims to simplify the installation and maintenance of the EDC and other components that together ensure a “home connection”. A flexible, parameterizable installation package is intended to reduce complexity and make integration more efficient, thereby simplifying participation in Catena‑X for additional participants. | Specification and development of a flexible, parameterizable installation package that reduces the complexity of installing and maintaining the required components for seamless integration into the Catena‑X data space. This package should facilitate updates and new versions, making participation in Catena‑X more efficient and accessible. In doing so, SMEs shall be enabled to participate without high costs or dependency on SaaS providers while maintaining control over their IT infrastructure. | [WP-7.1.-D001] Concept for the Hausanschluss is created                                                                                      |
+| 7.1.1.1        | The solution concept must define the Capability Bundles structures to be implemented. For each Capability Bundle, the included bundles and their versions are mapped.                                                                                                                                                                                     | "The following Capability Bundle structure is implemented:                                                                                                                                                                                                                                                                                                                                                                                                                                                       | "The structure of the Capability Bundles for the Enablement Services has been specified.                                                     |
+| 7.1.1.2        | Definition of Data Space Roles                                                                                                                                                                                                                                                                                                                            | Capability EDC (Data Transfer) Bundle                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | For version R24.12 it is clearly defined which Tractus‑X services and components are assigned to each Capability Bundle"                     |
+| 7.1.1.4        | Modularity & Maintainability: No dependencies between Capability Bundles                                                                                                                                                                                                                                                                                  | Eclipse Dataspace Connector (EDC) v0.9.0                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | "As part of the target group analysis, the target groups are defined and aligned with the data space roles.                                  |
+| 7.1.1.5        | Modularity & Maintainability: Concept for reducing deployment complexity                                                                                                                                                                                                                                                                                  | EDC PostgresSQL                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | Mapping from data space role to target group has been completed.                                                                             |
+| 7.1.1.6        | Modularity & Maintainability                                                                                                                                                                                                                                                                                                                              | HashiCorp Vault                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | Mapping from target group to data space role has been completed.                                                                             |
+| 7.1.1.13       | Solution Concept                                                                                                                                                                                                                                                                                                                                          | Capability Digital Twin Bundle                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | An assignment of data space roles to Capability Bundles has been made."                                                                      |
+| 7.1.1.14       | Scalability of Enablement Services                                                                                                                                                                                                                                                                                                                        | Decentral DT Registry                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | "Components and Services should obly be part of one bundle.                                                                                  |
+| 7.1.1.16       | Interoperability                                                                                                                                                                                                                                                                                                                                          | PostgresSQL                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | Each bundle must be deployable in isolation and can be installed, updated, or removed independently.                                         |
+| [WP-7.1.-D002] | [WP-7.1.-D002] Target group for the specification is defined.                                                                                                                                                                                                                                                                                             | Capability Identity & Trust (Identity Wallet Bundle)                                                                                                                                                                                                                                                                                                                                                                                                                                                             | Capability Bundles must be organized in separate HELM sub‑charts.                                                                            |
+| 7.1.2.1        | Target Group Analysis                                                                                                                                                                                                                                                                                                                                     | Identity Wallet Mock                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | Circular dependencies between bundles must be avoided."                                                                                      |
+| [WP-7.1.-D003] | [WP-7.1.-D003] Decentralized components and services defined                                                                                                                                                                                                                                                                                              | Capability Semantic Model Bundle                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | "Simplification of deployment processes                                                                                                      |
+| 7.1.3.1        | See [WP-7.1.-D001-AC001]                                                                                                                                                                                                                                                                                                                                  | Submodel Mock (aus Umbrella HELM Chart)"                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | A reduction of manual configuration steps has been achieved.                                                                                 |
+| [WP-7.1.-D004] | [WP-7.1.-D004] Documentation of the Hausanschluss Bundle is completed                                                                                                                                                                                                                                                                                     | "Data Consumer                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | Transparency and traceability                                                                                                                |
+| 7.1.4.1        | Documentation of the Hausanschluss-Bundles                                                                                                                                                                                                                                                                                                                | Data Provider                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | Clearly documented deployment steps are provided.                                                                                            |
+| 7.1.4.2        | Documentation of the Hausanschluss-Bundles                                                                                                                                                                                                                                                                                                                | Enablement Service Provider"                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | Improvements of Chart configuration by                                                                                                       |
+| [WP-7.1.-D005] | [WP-7.1.-D005] Umbrella HELM Charts for the Hausanschluss developed, tested, and documented                                                                                                                                                                                                                                                               | "Unique assignment of components and services to a defined Capability Bundle.                                                                                                                                                                                                                                                                                                                                                                                                                                    | usage of template                                                                                                                            |
+| 7.1.5.1        | Re-activate Umbrella HELM Charts to the latest release state                                                                                                                                                                                                                                                                                              | Each component and service should be assigned to only one Capability Bundle.                                                                                                                                                                                                                                                                                                                                                                                                                                     | reducing configuration options                                                                                                               |
+| 7.1.5.2        | Hierarchical structuring and bundling of Enablement Service components in the Umbrella HELM Chart                                                                                                                                                                                                                                                         | Dependencies between Capability Bundles are allowed."                                                                                                                                                                                                                                                                                                                                                                                                                                                            | reducing manual steps in the setup"                                                                                                          |
+| 7.1.5.3        | Interchangeability of bundle components via “Bring-Your-Own” components                                                                                                                                                                                                                                                                                   | The system deployment should be optimized to reduce the existing complexity. The goal is to make the provisioning process more efficient, robust, and easier to maintain.                                                                                                                                                                                                                                                                                                                                        | Charts are published via a publicly accessible charts repository.                                                                            |
+| [WP-7.1.-D006] | [WP-7.1.-D006] Product developed according to a Technology Readiness Level (TRL) of 3                                                                                                                                                                                                                                                                     | Charts are published automatically.                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | "The solution design for the ""Hausanschluss"" Bundle is created.                                                                            |
+| 7.1.6.1        | POC                                                                                                                                                                                                                                                                                                                                                       | Creation of a solution design for the “Hausanschluss” Bundle.                                                                                                                                                                                                                                                                                                                                                                                                                                                    | The solution design for the ""Hausanschluss"" Bundle ispublished in the repository: https://github.com/eclipse-tractusx/tractus-x-umbrella." |
+| 7.1.6.2        | Deployment Strategy                                                                                                                                                                                                                                                                                                                                       | Scalability of Enablement Services                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | "Developers should be able to deploy an arbitrary number of Enablement Services.                                                             |
+
+# 3 AS-IS Analysis
+
+## 3.1 People
+
+### 3.1.1 Target Group Analysis
+
+See "4.1.1 To-be Target Group Analysis" below. No deviations between As-is and To-be target groups have been identified.
+
+## 3.2 Process
+
+### 3.2.1 Use Case View (high-level)
+
+Umbrella Chart is intended for the following Use Cases:
+
+| Actor             | Use case                                                                                             |
+|-------------------|------------------------------------------------------------------------------------------------------|
+| Product Developer | Sandbox Environments: Create local environments to evaluate and experiment with Catena-X components. |
+| Product Developer | Development: Provide a unified setup for contributors and developers working on Tractus-X projects.  |
+| Product Tester    | Testing: Run end-to-end tests for Catena-X services.                                                 |
+
+## 3.4 System
+
+### 3.4.1 Context Delimitation
+
+````mermaid
+flowchart
+    subgraph "Umbrella Chart"
+        ChartYaml["Chart.yaml"]
+        subgraph charts
+            Portal["Portal"]
+            CentralIdp["CentralIdp"]
+            DiscoveryFinder["Discovery Finder"]
+            SDFactory["SD-Factory"]
+            SSICredentialIssuer["SSI Credential Issuer"]
+            SemanticHub["Semantic Hub"]
+            BPDM["BPDM"]
+            DataConsumer["Data Consumer"]
+            DataProvider["Data Provider"]
+            BDRS["BDRS"]
+            SSIWalletStub["SSI Wallet Stub"]
+        end
+        subgraph "tx-data-provider"
+            EDC["EDC"]
+            DTR["DTR"]
+            SubmodelServer["Submodel Server"]
+        end
+    end
+
+    ChartYaml --> Portal
+    ChartYaml --> CentralIdp
+    ChartYaml --> DiscoveryFinder
+    ChartYaml --> SDFactory
+    ChartYaml --> SSICredentialIssuer
+    ChartYaml --> SemanticHub
+    ChartYaml --> BPDM
+    ChartYaml --> DataConsumer
+    ChartYaml --> DataProvider
+    ChartYaml --> BDRS
+    ChartYaml --> SSIWalletStub
+    DataConsumer --> EDC
+    DataProvider --> EDC
+    DataProvider --> DTR
+    DataProvider --> SubmodelServer
+````
+
+#### Existing Umbrella Chart Structure
+
+# 4 TO-BE Design
+
+## 4.1 People
+
+### 4.1.1 Target Group Analysis
+
+Overall data space roles: https://catena-x.net/en/1/catena-x-introduce-implement/how-to-operate-catena-x
+
+The relevant data space roles for us under requirement 7.1.1.1 are:
+
+- Data Consumer
+- Data Provider
+- Enablement Service Provider
+
+Scope: Umbrella HELM Charts
+
+- Enablement Services: These services are included under the umbrella of HELM charts, focusing on enabling
+  functionalities.
+- Out of Scope: Core services such as Portal or BPDM are not considered within this scope.
+
+Primary target groups:
+
+| No. | Target group                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | Data space roles                                                    | Target group differentiation                                                                                                                                                                                                                                                                            | Behaviour, Needs, Pains & Usage                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+|-----|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| 1   | Developers<ul><li>External Developers (not Tractus-X developers): Utilize the chart for demonstration or evaluation purposes.</li><li>Experienced software and product developers who are developing a business app for a CATENA-X data space. They need to develop the app against the interfaces of the data space and integrate them accordingly.</li><li>They emphasize efficient and cost-effective implementation:<ul><li>Cost Efficiency: They do not want to use expensive SaaS solutions.</li><li>Technical Independence: They lack the knowledge and capacity to deploy the enablement and core services of the data space themselves.</li><li>Focus on Development: They concentrate on application development without delving deeply into the deployment and operation of the underlying infrastructure.</li></ul></li><li>Out of Scope: Developers running tests in test runners are not considered within this scope.</li></ul> | Data Consumer <br/> Data Provider <br/> Enablement Service Provider |                                                                                                                                                                                                                                                                                                         | <ul><li>Needs / sources of information<ul><li><a href="https://eclipse-tractusx.github.io/Kits/">Kit documentation tractus-x</a> for interaction purposes</li><li><a href="https://catenax-ev.github.io/">Catena-X doucmentation</a> for standards and regulations</li><li><a href="https://github.com/eclipse-tractusx/tractus-x-umbrella">Umbrella documentation</a> for umbrella component information</li></ul></li><li>Challenges → Solution<ul><li>Decentralization e.g. Where are other systems? How to interact with them? → Solution: Umbrella charts and bundles for deployment</li><li>Complex setup → Solution: delivery of small capability bundles</li></ul></li></ul> |
+| 2   | <ul><li>Tester requiring a test system (Testmanagement e.V.)</li><li>Requirement: Testbed</li></ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | Data Consumer <br/> Data Provider <br/> Enablement Service Provider | <ul><li>Developer (1) tests their feature.</li><li>Tester (2) performs end-to-end testing.</li><li>For the tester, the modular structure is less relevant since they focus on E2E testing, whereas the developer selects the required components.</li><li>The testbed must be easy to deploy.</li></ul> | <ul><li>Same as above from an End-to-end testing perspective</li><li>Typically a tester has less technical know-how than a developer and therefore needs a "one-size-fits-all" chart for easier testing</li></ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+
+## 4.2 Process
+
+### 4.2.1 Use Case View (high-level)
+
+| Use Case                                | Description                                                                                                       | Actors            |
+|-----------------------------------------|-------------------------------------------------------------------------------------------------------------------|-------------------|
+| Configure HELM Chart                    | The product developer configures the HELM Chart for the specific environment.                                     | Product Developer |
+| Configure Secrets                       | The product developer manages and configures secrets.                                                             | Product Developer |
+| Execute Deployment Pipeline             | The product developer successfully executes the deployment pipeline for the HELM Chart.                           | Product Developer |
+| Integrate EDC, DTR, and Identity Wallet | The actors integrate the components EDC, Digital Twin Registry, and Identity Wallet for seamless interoperability | Product Developer |
+| Set Up Connection Infrastructure        | The actor sets up the connection infrastructure for linking to the central data space infrastructure.             | Product Developer |
+| Maintain Infrastructure Module          | The product developer maintains the modular architecture of the HELM Chart.                                       | Product Developer |
+| Ensure Scalability                      | The product developer ensures scalability to support growing numbers of users and data volumes.                   | Product Developer |
+| Sandbox Environments                    | The product developer creates local environments to evaluate and experiment with Catena-X components.             | Product Developer |
+| E2E Testing                             | The product tester runs end-to-end tests for Catena-X services.                                                   | Product Tester    |
+
path: docs/concept/TAP7.1-solution-design.md
user: login: ds-jhartmann
body: Diagram does not render like this. I added a slightly adjusted version
created_at: 2025-03-31T08:50:43Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,425 @@
+# [TAP 7.1] Solution Design Hausanschluss Bundle Konzept
+
+# 1 Business Case
+
+## 1.1 Executive Summary
+
+The EDC "Hausanschluss" Bundle aims to simplify the installation of the enablement services Eclipse Dataspace
+Connector (EDC), Digital Twin Registry (DTR), and their supporting components. By developing a flexible, parameterizable
+installation package, the project seeks to reduce deployment complexity and lower barriers to participation in the
+Catena‑X data space. This bundle will enable independent component updates and support a modular "bring your own"
+approach, ultimately fostering a more efficient and accessible ecosystem for diverse participants—such as testers,
+external developers, and small and medium-sized enterprises.
+
+## 1.2 Business Need
+
+Current deployment methods for data space integration are complex and require significant manual effort. This PoC
+addresses the need to:
+
+- Reduce Complexity: Simplify the deployment topology by bundling components into capabilities.
+- Automate Deployment: Provide an automated installation package using Kubernetes and HELM.
+- Reduce Configuration Efforts: Streamline and reduce the number of configuration steps required for integration.
+- Extend Documentation: Provide a detailed documentation tailored to the target groups.
+- Enable Extension: Design the system to allow the seamless addition of new components or capabilities.
+
+## 1.3 Objectives
+
+- Simplify Deployment and Maintenance: Develop an installation package that minimizes manual configuration through
+  automation.
+- Ensure Modularity: Structure the bundle so that components can be independently installed, updated, or replaced
+  without
+  affecting other services.
+- Facilitate Flexibility: Implement a "bring your own" model for key components, such as EDC, PostgreSQL, and HashiCorp
+  Vault, to allow tailored deployments that meet specific needs.
+- Increase Accessibility: Lower entry barriers for new participants by reducing technical complexity and operational
+  dependencies.
+- Scalability: Structure the bundle so that it can be deployed multiple times.
+
+## 1.4 Expected Deliverables
+
+- PoC Documentation: A concept and architecture overview highlighting the modular design.
+- Modular Installation Package: A set of HELM charts for deploying the enablement service bundles:
+    - EDC Bundle: Including the Eclipse Dataspace Connector, EDC PostgreSQL, and HashiCorp Vault.
+    - Digital Twin Bundle: Featuring components such as the Decentral DT Registry (with “bring your own” PostgreSQL) and
+      a Submodel Server Bundle.
+    - Identity Wallet Bundle: Covering the Identity Wallet functionality.
+- Demonstration Environment: A test deployment showcasing reduced complexity and improved efficiency.
+- Basic User Guide: Instructions on how to deploy and update the PoC bundle.
+
+## 1.5 Benefits
+
+- Operational Efficiency: Faster and more reliable deployments with less manual work.
+- Scalability: A modular design that can be scaled or adapted for future full-scale deployments.
+- Ease of Adoption: Simplified deployment processes make it easier for testers and external developers to engage.
+
+## 1.6. Dependencies
+
+- Interoperability with the CATENA‑X standards.
+
+## 1.7. Success Criteria
+
+- Technology Readiness Level: Achievement of a Technology Readiness Level (TRL) of 3, as specified in the requirements.
+- Functional PoC Deployment: Demonstrated automated, modular installation with reduced manual steps.
+- Simplified Configuration: Clear evidence of reduced configuration complexity.
+- Positive Feedback: End-user validation from a select group of demo participants and the Tractus-X community.
+- Documentation Completeness: Availability of concise deployment and user guides.
+
+## 1.8. Out of Scope
+
+- Full Production Readiness: This PoC is not intended to be a production-ready solution.
+- Core Services Exclusion: Core services are not part of the Hausanschluss Bundles.
+- App Provider Role: The role of App Provider is considered out of scope for this deployment.
+- Alternative Deployment Techniques: While the evaluation of alternative deployment methods is acknowledged, the primary
+  focus remains on Kubernetes and HELM-based deployment.
+
+# 2 Requirements Analysis
+
+## 2.1 Assumptions
+
+## 2.2 Requirements Catalog
+
+| ID             | Requirement                                                                                                                                                                                                                                                                                                                                               | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | Deliverables / Acceptance Criteria                                                                                                           |
+|----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------|
+| [WP-7.1.-D001] | TAP7.1 Hausanschluss Bundle aims to simplify the installation and maintenance of the EDC and other components that together ensure a “home connection”. A flexible, parameterizable installation package is intended to reduce complexity and make integration more efficient, thereby simplifying participation in Catena‑X for additional participants. | Specification and development of a flexible, parameterizable installation package that reduces the complexity of installing and maintaining the required components for seamless integration into the Catena‑X data space. This package should facilitate updates and new versions, making participation in Catena‑X more efficient and accessible. In doing so, SMEs shall be enabled to participate without high costs or dependency on SaaS providers while maintaining control over their IT infrastructure. | [WP-7.1.-D001] Concept for the Hausanschluss is created                                                                                      |
+| 7.1.1.1        | The solution concept must define the Capability Bundles structures to be implemented. For each Capability Bundle, the included bundles and their versions are mapped.                                                                                                                                                                                     | "The following Capability Bundle structure is implemented:                                                                                                                                                                                                                                                                                                                                                                                                                                                       | "The structure of the Capability Bundles for the Enablement Services has been specified.                                                     |
+| 7.1.1.2        | Definition of Data Space Roles                                                                                                                                                                                                                                                                                                                            | Capability EDC (Data Transfer) Bundle                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | For version R24.12 it is clearly defined which Tractus‑X services and components are assigned to each Capability Bundle"                     |
+| 7.1.1.4        | Modularity & Maintainability: No dependencies between Capability Bundles                                                                                                                                                                                                                                                                                  | Eclipse Dataspace Connector (EDC) v0.9.0                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | "As part of the target group analysis, the target groups are defined and aligned with the data space roles.                                  |
+| 7.1.1.5        | Modularity & Maintainability: Concept for reducing deployment complexity                                                                                                                                                                                                                                                                                  | EDC PostgresSQL                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | Mapping from data space role to target group has been completed.                                                                             |
+| 7.1.1.6        | Modularity & Maintainability                                                                                                                                                                                                                                                                                                                              | HashiCorp Vault                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | Mapping from target group to data space role has been completed.                                                                             |
+| 7.1.1.13       | Solution Concept                                                                                                                                                                                                                                                                                                                                          | Capability Digital Twin Bundle                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | An assignment of data space roles to Capability Bundles has been made."                                                                      |
+| 7.1.1.14       | Scalability of Enablement Services                                                                                                                                                                                                                                                                                                                        | Decentral DT Registry                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | "Components and Services should obly be part of one bundle.                                                                                  |
+| 7.1.1.16       | Interoperability                                                                                                                                                                                                                                                                                                                                          | PostgresSQL                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | Each bundle must be deployable in isolation and can be installed, updated, or removed independently.                                         |
+| [WP-7.1.-D002] | [WP-7.1.-D002] Target group for the specification is defined.                                                                                                                                                                                                                                                                                             | Capability Identity & Trust (Identity Wallet Bundle)                                                                                                                                                                                                                                                                                                                                                                                                                                                             | Capability Bundles must be organized in separate HELM sub‑charts.                                                                            |
+| 7.1.2.1        | Target Group Analysis                                                                                                                                                                                                                                                                                                                                     | Identity Wallet Mock                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | Circular dependencies between bundles must be avoided."                                                                                      |
+| [WP-7.1.-D003] | [WP-7.1.-D003] Decentralized components and services defined                                                                                                                                                                                                                                                                                              | Capability Semantic Model Bundle                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | "Simplification of deployment processes                                                                                                      |
+| 7.1.3.1        | See [WP-7.1.-D001-AC001]                                                                                                                                                                                                                                                                                                                                  | Submodel Mock (aus Umbrella HELM Chart)"                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | A reduction of manual configuration steps has been achieved.                                                                                 |
+| [WP-7.1.-D004] | [WP-7.1.-D004] Documentation of the Hausanschluss Bundle is completed                                                                                                                                                                                                                                                                                     | "Data Consumer                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | Transparency and traceability                                                                                                                |
+| 7.1.4.1        | Documentation of the Hausanschluss-Bundles                                                                                                                                                                                                                                                                                                                | Data Provider                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | Clearly documented deployment steps are provided.                                                                                            |
+| 7.1.4.2        | Documentation of the Hausanschluss-Bundles                                                                                                                                                                                                                                                                                                                | Enablement Service Provider"                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | Improvements of Chart configuration by                                                                                                       |
+| [WP-7.1.-D005] | [WP-7.1.-D005] Umbrella HELM Charts for the Hausanschluss developed, tested, and documented                                                                                                                                                                                                                                                               | "Unique assignment of components and services to a defined Capability Bundle.                                                                                                                                                                                                                                                                                                                                                                                                                                    | usage of template                                                                                                                            |
+| 7.1.5.1        | Re-activate Umbrella HELM Charts to the latest release state                                                                                                                                                                                                                                                                                              | Each component and service should be assigned to only one Capability Bundle.                                                                                                                                                                                                                                                                                                                                                                                                                                     | reducing configuration options                                                                                                               |
+| 7.1.5.2        | Hierarchical structuring and bundling of Enablement Service components in the Umbrella HELM Chart                                                                                                                                                                                                                                                         | Dependencies between Capability Bundles are allowed."                                                                                                                                                                                                                                                                                                                                                                                                                                                            | reducing manual steps in the setup"                                                                                                          |
+| 7.1.5.3        | Interchangeability of bundle components via “Bring-Your-Own” components                                                                                                                                                                                                                                                                                   | The system deployment should be optimized to reduce the existing complexity. The goal is to make the provisioning process more efficient, robust, and easier to maintain.                                                                                                                                                                                                                                                                                                                                        | Charts are published via a publicly accessible charts repository.                                                                            |
+| [WP-7.1.-D006] | [WP-7.1.-D006] Product developed according to a Technology Readiness Level (TRL) of 3                                                                                                                                                                                                                                                                     | Charts are published automatically.                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | "The solution design for the ""Hausanschluss"" Bundle is created.                                                                            |
+| 7.1.6.1        | POC                                                                                                                                                                                                                                                                                                                                                       | Creation of a solution design for the “Hausanschluss” Bundle.                                                                                                                                                                                                                                                                                                                                                                                                                                                    | The solution design for the ""Hausanschluss"" Bundle ispublished in the repository: https://github.com/eclipse-tractusx/tractus-x-umbrella." |
+| 7.1.6.2        | Deployment Strategy                                                                                                                                                                                                                                                                                                                                       | Scalability of Enablement Services                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | "Developers should be able to deploy an arbitrary number of Enablement Services.                                                             |
+
+# 3 AS-IS Analysis
+
+## 3.1 People
+
+### 3.1.1 Target Group Analysis
+
+See "4.1.1 To-be Target Group Analysis" below. No deviations between As-is and To-be target groups have been identified.
+
+## 3.2 Process
+
+### 3.2.1 Use Case View (high-level)
+
+Umbrella Chart is intended for the following Use Cases:
+
+| Actor             | Use case                                                                                             |
+|-------------------|------------------------------------------------------------------------------------------------------|
+| Product Developer | Sandbox Environments: Create local environments to evaluate and experiment with Catena-X components. |
+| Product Developer | Development: Provide a unified setup for contributors and developers working on Tractus-X projects.  |
+| Product Tester    | Testing: Run end-to-end tests for Catena-X services.                                                 |
+
+## 3.4 System
+
+### 3.4.1 Context Delimitation
+
+````mermaid
+flowchart
+    subgraph "Umbrella Chart"
+        ChartYaml["Chart.yaml"]
+        subgraph charts
+            Portal["Portal"]
+            CentralIdp["CentralIdp"]
+            DiscoveryFinder["Discovery Finder"]
+            SDFactory["SD-Factory"]
+            SSICredentialIssuer["SSI Credential Issuer"]
+            SemanticHub["Semantic Hub"]
+            BPDM["BPDM"]
+            DataConsumer["Data Consumer"]
+            DataProvider["Data Provider"]
+            BDRS["BDRS"]
+            SSIWalletStub["SSI Wallet Stub"]
+        end
+        subgraph "tx-data-provider"
+            EDC["EDC"]
+            DTR["DTR"]
+            SubmodelServer["Submodel Server"]
+        end
+    end
+
+    ChartYaml --> Portal
+    ChartYaml --> CentralIdp
+    ChartYaml --> DiscoveryFinder
+    ChartYaml --> SDFactory
+    ChartYaml --> SSICredentialIssuer
+    ChartYaml --> SemanticHub
+    ChartYaml --> BPDM
+    ChartYaml --> DataConsumer
+    ChartYaml --> DataProvider
+    ChartYaml --> BDRS
+    ChartYaml --> SSIWalletStub
+    DataConsumer --> EDC
+    DataProvider --> EDC
+    DataProvider --> DTR
+    DataProvider --> SubmodelServer
+````
+
+#### Existing Umbrella Chart Structure
+
+# 4 TO-BE Design
+
+## 4.1 People
+
+### 4.1.1 Target Group Analysis
+
+Overall data space roles: https://catena-x.net/en/1/catena-x-introduce-implement/how-to-operate-catena-x
+
+The relevant data space roles for us under requirement 7.1.1.1 are:
+
+- Data Consumer
+- Data Provider
+- Enablement Service Provider
+
+Scope: Umbrella HELM Charts
+
+- Enablement Services: These services are included under the umbrella of HELM charts, focusing on enabling
+  functionalities.
+- Out of Scope: Core services such as Portal or BPDM are not considered within this scope.
+
+Primary target groups:
+
+| No. | Target group                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | Data space roles                                                    | Target group differentiation                                                                                                                                                                                                                                                                            | Behaviour, Needs, Pains & Usage                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+|-----|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| 1   | Developers<ul><li>External Developers (not Tractus-X developers): Utilize the chart for demonstration or evaluation purposes.</li><li>Experienced software and product developers who are developing a business app for a CATENA-X data space. They need to develop the app against the interfaces of the data space and integrate them accordingly.</li><li>They emphasize efficient and cost-effective implementation:<ul><li>Cost Efficiency: They do not want to use expensive SaaS solutions.</li><li>Technical Independence: They lack the knowledge and capacity to deploy the enablement and core services of the data space themselves.</li><li>Focus on Development: They concentrate on application development without delving deeply into the deployment and operation of the underlying infrastructure.</li></ul></li><li>Out of Scope: Developers running tests in test runners are not considered within this scope.</li></ul> | Data Consumer <br/> Data Provider <br/> Enablement Service Provider |                                                                                                                                                                                                                                                                                                         | <ul><li>Needs / sources of information<ul><li><a href="https://eclipse-tractusx.github.io/Kits/">Kit documentation tractus-x</a> for interaction purposes</li><li><a href="https://catenax-ev.github.io/">Catena-X doucmentation</a> for standards and regulations</li><li><a href="https://github.com/eclipse-tractusx/tractus-x-umbrella">Umbrella documentation</a> for umbrella component information</li></ul></li><li>Challenges → Solution<ul><li>Decentralization e.g. Where are other systems? How to interact with them? → Solution: Umbrella charts and bundles for deployment</li><li>Complex setup → Solution: delivery of small capability bundles</li></ul></li></ul> |
+| 2   | <ul><li>Tester requiring a test system (Testmanagement e.V.)</li><li>Requirement: Testbed</li></ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | Data Consumer <br/> Data Provider <br/> Enablement Service Provider | <ul><li>Developer (1) tests their feature.</li><li>Tester (2) performs end-to-end testing.</li><li>For the tester, the modular structure is less relevant since they focus on E2E testing, whereas the developer selects the required components.</li><li>The testbed must be easy to deploy.</li></ul> | <ul><li>Same as above from an End-to-end testing perspective</li><li>Typically a tester has less technical know-how than a developer and therefore needs a "one-size-fits-all" chart for easier testing</li></ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+
+## 4.2 Process
+
+### 4.2.1 Use Case View (high-level)
+
+| Use Case                                | Description                                                                                                       | Actors            |
+|-----------------------------------------|-------------------------------------------------------------------------------------------------------------------|-------------------|
+| Configure HELM Chart                    | The product developer configures the HELM Chart for the specific environment.                                     | Product Developer |
+| Configure Secrets                       | The product developer manages and configures secrets.                                                             | Product Developer |
+| Execute Deployment Pipeline             | The product developer successfully executes the deployment pipeline for the HELM Chart.                           | Product Developer |
+| Integrate EDC, DTR, and Identity Wallet | The actors integrate the components EDC, Digital Twin Registry, and Identity Wallet for seamless interoperability | Product Developer |
+| Set Up Connection Infrastructure        | The actor sets up the connection infrastructure for linking to the central data space infrastructure.             | Product Developer |
+| Maintain Infrastructure Module          | The product developer maintains the modular architecture of the HELM Chart.                                       | Product Developer |
+| Ensure Scalability                      | The product developer ensures scalability to support growing numbers of users and data volumes.                   | Product Developer |
+| Sandbox Environments                    | The product developer creates local environments to evaluate and experiment with Catena-X components.             | Product Developer |
+| E2E Testing                             | The product tester runs end-to-end tests for Catena-X services.                                                   | Product Tester    |
+
+### 4.2.2 Business Process (SCC Artifact)
+
+#### Chart Release Process
+
+Charts will be released using the already existing workflow in the Umbrella Chart repository. The workflow will
+automatically release a Chart, once it is pushed to the "charts/" directory with a new Chart version.
+
+#### Capability Bundle Structure
+
+Capability bundle modularization for the Tractus-X Umbrella Helm chart is a sound architectural and operational design.
+It aligns with both the domain-driven architecture of Catena-X (data exchange, digital twin, identity, semantics are
+distinct domains) and with Kubernetes best practices for managing complex applications (using an umbrella chart to
+bundle related microservices).
+
+Each bundle is self-sufficient, which improves isolation (failures or changes in one domain have minimal impact on
+others) and allows scaling and upgrading along domain lines. It simplifies deployment by allowing “plug-and-play”
+capabilities: an Enablement Service Provider can decide which bundles to operate based on its role e.g., include the
+Digital Twin and Semantic bundles if offering an asset-rich service, or omit them if not. The approach is consistent
+with how other OSS projects deliver multi-component systems, providing one-step installation without sacrificing the
+ability to tweak individual parts.
+
+Why this structure was proposed:
+
+1. **Clear Separation of Concerns**  
+   Each capability bundle (e.g. EDC Data Transfer, Digital Twin, Identity & Trust, Semantic Model) aligns with a
+   specific functional domain. This separation makes it easier to understand the role of each service (e.g., the EDC
+   connector vs. the digital twin registry), reduces coupling between unrelated components, and ultimately makes
+   maintenance and troubleshooting more straightforward.
+2. **Modular Deployment**  
+   Some participants in Catena-X may not need all services (e.g., some might not use the Digital Twin bundle). By
+   structuring the umbrella chart into bundles, a user can enable just those needed capabilities. This leads to leaner
+   installs and avoids unnecessary resource usage.
+3. **Best Practices with Helm**  
+   Using an umbrella chart with subcharts/bundles is a well-recognized Helm best practice for complex applications. It
+   allows a single helm install to set up multiple microservices while still allowing each service to have its own
+   lifecycle, configuration, and version.
+4. **Alignment with Domain-Driven Approach**  
+   Catena-X is organized around distinct, loosely-coupled “building blocks.” Bundling services by domain matches this
+   architectural vision. It’s clear which domain each set of microservices belongs to (EDC for data exchange, identity
+   for credential management, etc.). This clarity also helps new adopters navigate the ecosystem.
+
+````mermaid
+flowchart LR
+    subgraph "Core Services"
+        Vault["Vault"]
+    end
+
+    subgraph "Capability Bundle: Identity & Trust"
+        SSIWalletStub["SSI Wallet Stub"]
+    end
+
+    subgraph "Capability Bundle: Dataspace Connector"
+        EDC["EDC"]
+        EDCDB["EDC DB"]
+    end
+
+    subgraph "Capability Bundle: Digital Twin"
+        DTR["DTR"]
+        DTRDB["DTR DB"]
+    end
+
+    subgraph "Capability Bundle: Data Persitence Layer"
+        SimpleSubmodelServer["Simple Submodel Server"]
+    end
+
+    subgraph "Hausanschluss Bundles"
+        subgraph "Data Provider"
+            DataProvider["Data Provider"]
+        end
+        subgraph "Data Consumer"
+            DataConsumer["Data Consumer"]
+        end
+        subgraph "Enablement Provider"
+            EnablementProvider["Enablement Provider"]
+        end
+    end
+
+    EDC -.-> SSIWalletStub
+    EDC -.-> Vault
+    DataProvider --> EDC
+    DataProvider --> DTR
+    DataProvider --> SimpleSubmodelServer
+    DataConsumer --> EDC
+    EnablementProvider --> DataConsumer
+    EnablementProvider --> DataProvider
+
+````
+
+#### Deployment strategies
+
+##### Role: Data Provider
+
+The standard data provider role consists of a EDC, DTR and Submodel Server Bundles. EDC uses the Identity Wallet Bundle.
+
+````mermaid
+flowchart BT
+    A["Capability Bundle: Identity & Trust"]
+    B["Capability Bundle: Data Persistence Layer"]
+    C["Capability Bundle: Dataspace Connector"]
+    D["Capability Bundle: Digital Twin"]
+    E["Application to be tested/developed"]
+    E --> B
+    E --> C
+    E --> D
+    C --> A
+````
+
+##### Role: Data Consumer
+
+The standard data consumer role consists of only the EDC Bundle and the Identity Wallet Bundle.
+
+````mermaid
+flowchart BT
+    A["Capability Bundle: Identity & Trust"]
+    B["Capability Bundle: Dataspace Connector"]
+    C["Application to be tested/developed"]
+    C --> B
+    B --> A
+
+````
+
+##### Role: Enablement Provider
+
+The Enablement Provider roles consists of both the Data Consumer and Data Provider bundles. This allows provisioning of
+data and the consumtion of the provisioned data by a application.
+
+````mermaid
+flowchart BT
+    A["Capability Bundle: Identity & Trust"]
+    B["Capability Bundle: Data Persitance Layer"]
+    C["Application to be tested/developed"]
+    D["Capability Bundle: Digital Twin"]
+    E["Capability Bundle: Dataspace Connector (Provider)"]
+    F["Capability Bundle: Dataspace Connector (Consumer)"]
+    C --> B
+    C --> D
+    C --> E
+    C --> F
+    E --> A
+    F --> A
+````
+
+##### Bring you own
+
+Each Bundle can be deactivated to use your own component. This requires configuration of the component specific
+parameters in the other components.
+
+In this example this would be the configuration of the Identity Wallet within the EDC.
+
+````mermaid
+flowchart BT
+    A["Application to be tested/developed"]
+    B["Capability Bundle: Dataspace Connector"]
+    C["
Capability Bundle: Identity & Trust
"]
+    D["Own Identity Wallet"]
+    A --> B
+    B -- identitywallet - bundle . enabled = false --> C
+    B -- configure --> D
+
+````
+
+## 4.4 System
+
+### 4.4.1 Context Delimitation / 4.4.2 Interface Documentation
+
+````mermaid
+flowchart LR
+    Dataprovider["Dataprovider"] -->|stores data| SubmodelServer["Submodel Server"]
+    Dataprovider -->|creates twins| DTR["DTR"]
+    Dataprovider -->|creates contracts| EDC["EDC"]
+    Dataconsumer["Dataconsumer"] -->|negotiate contracts| EDC
+    DTR -->|needs| IdentityWallet["Identity Wallet"]
+    IdentityWallet -->|needs| Postgres["PostgreSQL Database"]
+````
+
+# 5 Build
+
+## 5.1 DevOps Setup Definition
+
+### 5.1.1 Tool Chain Definition
+
+##### Version Control & Source Code Management
+
+- **Git & GitHub**: Management of the source code, the Helm Charts, and associated documentation in a centralized
+  repository.
+
+##### Build and CI/CD Tools
+
+- **GitHub Actions**: Automated workflows for linting, testing, packaging, and releasing the Helm Charts.
+- **Helm CLI**: For validating, packaging, and deploying the charts.
+- **Helm Lint**: Performing static analyses to ensure compliance with chart standards.
+
+##### Testing and Validation Tools
+
+- **chart-testing Tool**: Validation of the Helm Charts based on Kubernetes schemas.
path: docs/concept/TAP7.1-solution-design.md
user: login: ds-jhartmann
body: This is not KICS nor Trivy. This tool is just for testing helm charts
created_at: 2025-03-31T08:51:57Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,425 @@
+# [TAP 7.1] Solution Design Hausanschluss Bundle Konzept
+
+# 1 Business Case
+
+## 1.1 Executive Summary
+
+The EDC "Hausanschluss" Bundle aims to simplify the installation of the enablement services Eclipse Dataspace
+Connector (EDC), Digital Twin Registry (DTR), and their supporting components. By developing a flexible, parameterizable
+installation package, the project seeks to reduce deployment complexity and lower barriers to participation in the
+Catena‑X data space. This bundle will enable independent component updates and support a modular "bring your own"
+approach, ultimately fostering a more efficient and accessible ecosystem for diverse participants—such as testers,
+external developers, and small and medium-sized enterprises.
+
+## 1.2 Business Need
+
+Current deployment methods for data space integration are complex and require significant manual effort. This PoC
+addresses the need to:
+
+- Reduce Complexity: Simplify the deployment topology by bundling components into capabilities.
+- Automate Deployment: Provide an automated installation package using Kubernetes and HELM.
+- Reduce Configuration Efforts: Streamline and reduce the number of configuration steps required for integration.
+- Extend Documentation: Provide a detailed documentation tailored to the target groups.
+- Enable Extension: Design the system to allow the seamless addition of new components or capabilities.
+
+## 1.3 Objectives
+
+- Simplify Deployment and Maintenance: Develop an installation package that minimizes manual configuration through
+  automation.
+- Ensure Modularity: Structure the bundle so that components can be independently installed, updated, or replaced
+  without
+  affecting other services.
+- Facilitate Flexibility: Implement a "bring your own" model for key components, such as EDC, PostgreSQL, and HashiCorp
+  Vault, to allow tailored deployments that meet specific needs.
+- Increase Accessibility: Lower entry barriers for new participants by reducing technical complexity and operational
+  dependencies.
+- Scalability: Structure the bundle so that it can be deployed multiple times.
+
+## 1.4 Expected Deliverables
+
+- PoC Documentation: A concept and architecture overview highlighting the modular design.
+- Modular Installation Package: A set of HELM charts for deploying the enablement service bundles:
+    - EDC Bundle: Including the Eclipse Dataspace Connector, EDC PostgreSQL, and HashiCorp Vault.
+    - Digital Twin Bundle: Featuring components such as the Decentral DT Registry (with “bring your own” PostgreSQL) and
+      a Submodel Server Bundle.
+    - Identity Wallet Bundle: Covering the Identity Wallet functionality.
+- Demonstration Environment: A test deployment showcasing reduced complexity and improved efficiency.
+- Basic User Guide: Instructions on how to deploy and update the PoC bundle.
+
+## 1.5 Benefits
+
+- Operational Efficiency: Faster and more reliable deployments with less manual work.
+- Scalability: A modular design that can be scaled or adapted for future full-scale deployments.
+- Ease of Adoption: Simplified deployment processes make it easier for testers and external developers to engage.
+
+## 1.6. Dependencies
+
+- Interoperability with the CATENA‑X standards.
+
+## 1.7. Success Criteria
+
+- Technology Readiness Level: Achievement of a Technology Readiness Level (TRL) of 3, as specified in the requirements.
+- Functional PoC Deployment: Demonstrated automated, modular installation with reduced manual steps.
+- Simplified Configuration: Clear evidence of reduced configuration complexity.
+- Positive Feedback: End-user validation from a select group of demo participants and the Tractus-X community.
+- Documentation Completeness: Availability of concise deployment and user guides.
+
+## 1.8. Out of Scope
+
+- Full Production Readiness: This PoC is not intended to be a production-ready solution.
+- Core Services Exclusion: Core services are not part of the Hausanschluss Bundles.
+- App Provider Role: The role of App Provider is considered out of scope for this deployment.
+- Alternative Deployment Techniques: While the evaluation of alternative deployment methods is acknowledged, the primary
+  focus remains on Kubernetes and HELM-based deployment.
+
+# 2 Requirements Analysis
+
+## 2.1 Assumptions
+
+## 2.2 Requirements Catalog
+
+| ID             | Requirement                                                                                                                                                                                                                                                                                                                                               | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | Deliverables / Acceptance Criteria                                                                                                           |
+|----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------|
+| [WP-7.1.-D001] | TAP7.1 Hausanschluss Bundle aims to simplify the installation and maintenance of the EDC and other components that together ensure a “home connection”. A flexible, parameterizable installation package is intended to reduce complexity and make integration more efficient, thereby simplifying participation in Catena‑X for additional participants. | Specification and development of a flexible, parameterizable installation package that reduces the complexity of installing and maintaining the required components for seamless integration into the Catena‑X data space. This package should facilitate updates and new versions, making participation in Catena‑X more efficient and accessible. In doing so, SMEs shall be enabled to participate without high costs or dependency on SaaS providers while maintaining control over their IT infrastructure. | [WP-7.1.-D001] Concept for the Hausanschluss is created                                                                                      |
+| 7.1.1.1        | The solution concept must define the Capability Bundles structures to be implemented. For each Capability Bundle, the included bundles and their versions are mapped.                                                                                                                                                                                     | "The following Capability Bundle structure is implemented:                                                                                                                                                                                                                                                                                                                                                                                                                                                       | "The structure of the Capability Bundles for the Enablement Services has been specified.                                                     |
+| 7.1.1.2        | Definition of Data Space Roles                                                                                                                                                                                                                                                                                                                            | Capability EDC (Data Transfer) Bundle                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | For version R24.12 it is clearly defined which Tractus‑X services and components are assigned to each Capability Bundle"                     |
+| 7.1.1.4        | Modularity & Maintainability: No dependencies between Capability Bundles                                                                                                                                                                                                                                                                                  | Eclipse Dataspace Connector (EDC) v0.9.0                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | "As part of the target group analysis, the target groups are defined and aligned with the data space roles.                                  |
+| 7.1.1.5        | Modularity & Maintainability: Concept for reducing deployment complexity                                                                                                                                                                                                                                                                                  | EDC PostgresSQL                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | Mapping from data space role to target group has been completed.                                                                             |
+| 7.1.1.6        | Modularity & Maintainability                                                                                                                                                                                                                                                                                                                              | HashiCorp Vault                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | Mapping from target group to data space role has been completed.                                                                             |
+| 7.1.1.13       | Solution Concept                                                                                                                                                                                                                                                                                                                                          | Capability Digital Twin Bundle                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | An assignment of data space roles to Capability Bundles has been made."                                                                      |
+| 7.1.1.14       | Scalability of Enablement Services                                                                                                                                                                                                                                                                                                                        | Decentral DT Registry                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | "Components and Services should obly be part of one bundle.                                                                                  |
+| 7.1.1.16       | Interoperability                                                                                                                                                                                                                                                                                                                                          | PostgresSQL                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | Each bundle must be deployable in isolation and can be installed, updated, or removed independently.                                         |
+| [WP-7.1.-D002] | [WP-7.1.-D002] Target group for the specification is defined.                                                                                                                                                                                                                                                                                             | Capability Identity & Trust (Identity Wallet Bundle)                                                                                                                                                                                                                                                                                                                                                                                                                                                             | Capability Bundles must be organized in separate HELM sub‑charts.                                                                            |
+| 7.1.2.1        | Target Group Analysis                                                                                                                                                                                                                                                                                                                                     | Identity Wallet Mock                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | Circular dependencies between bundles must be avoided."                                                                                      |
+| [WP-7.1.-D003] | [WP-7.1.-D003] Decentralized components and services defined                                                                                                                                                                                                                                                                                              | Capability Semantic Model Bundle                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | "Simplification of deployment processes                                                                                                      |
+| 7.1.3.1        | See [WP-7.1.-D001-AC001]                                                                                                                                                                                                                                                                                                                                  | Submodel Mock (aus Umbrella HELM Chart)"                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | A reduction of manual configuration steps has been achieved.                                                                                 |
+| [WP-7.1.-D004] | [WP-7.1.-D004] Documentation of the Hausanschluss Bundle is completed                                                                                                                                                                                                                                                                                     | "Data Consumer                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | Transparency and traceability                                                                                                                |
+| 7.1.4.1        | Documentation of the Hausanschluss-Bundles                                                                                                                                                                                                                                                                                                                | Data Provider                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | Clearly documented deployment steps are provided.                                                                                            |
+| 7.1.4.2        | Documentation of the Hausanschluss-Bundles                                                                                                                                                                                                                                                                                                                | Enablement Service Provider"                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | Improvements of Chart configuration by                                                                                                       |
+| [WP-7.1.-D005] | [WP-7.1.-D005] Umbrella HELM Charts for the Hausanschluss developed, tested, and documented                                                                                                                                                                                                                                                               | "Unique assignment of components and services to a defined Capability Bundle.                                                                                                                                                                                                                                                                                                                                                                                                                                    | usage of template                                                                                                                            |
+| 7.1.5.1        | Re-activate Umbrella HELM Charts to the latest release state                                                                                                                                                                                                                                                                                              | Each component and service should be assigned to only one Capability Bundle.                                                                                                                                                                                                                                                                                                                                                                                                                                     | reducing configuration options                                                                                                               |
+| 7.1.5.2        | Hierarchical structuring and bundling of Enablement Service components in the Umbrella HELM Chart                                                                                                                                                                                                                                                         | Dependencies between Capability Bundles are allowed."                                                                                                                                                                                                                                                                                                                                                                                                                                                            | reducing manual steps in the setup"                                                                                                          |
+| 7.1.5.3        | Interchangeability of bundle components via “Bring-Your-Own” components                                                                                                                                                                                                                                                                                   | The system deployment should be optimized to reduce the existing complexity. The goal is to make the provisioning process more efficient, robust, and easier to maintain.                                                                                                                                                                                                                                                                                                                                        | Charts are published via a publicly accessible charts repository.                                                                            |
+| [WP-7.1.-D006] | [WP-7.1.-D006] Product developed according to a Technology Readiness Level (TRL) of 3                                                                                                                                                                                                                                                                     | Charts are published automatically.                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | "The solution design for the ""Hausanschluss"" Bundle is created.                                                                            |
+| 7.1.6.1        | POC                                                                                                                                                                                                                                                                                                                                                       | Creation of a solution design for the “Hausanschluss” Bundle.                                                                                                                                                                                                                                                                                                                                                                                                                                                    | The solution design for the ""Hausanschluss"" Bundle ispublished in the repository: https://github.com/eclipse-tractusx/tractus-x-umbrella." |
+| 7.1.6.2        | Deployment Strategy                                                                                                                                                                                                                                                                                                                                       | Scalability of Enablement Services                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | "Developers should be able to deploy an arbitrary number of Enablement Services.                                                             |
+
+# 3 AS-IS Analysis
+
+## 3.1 People
+
+### 3.1.1 Target Group Analysis
+
+See "4.1.1 To-be Target Group Analysis" below. No deviations between As-is and To-be target groups have been identified.
+
+## 3.2 Process
+
+### 3.2.1 Use Case View (high-level)
+
+Umbrella Chart is intended for the following Use Cases:
+
+| Actor             | Use case                                                                                             |
+|-------------------|------------------------------------------------------------------------------------------------------|
+| Product Developer | Sandbox Environments: Create local environments to evaluate and experiment with Catena-X components. |
+| Product Developer | Development: Provide a unified setup for contributors and developers working on Tractus-X projects.  |
+| Product Tester    | Testing: Run end-to-end tests for Catena-X services.                                                 |
path: docs/concept/TAP7.1-solution-design.md
user: login: ds-jhartmann
body: added the PM to use cases
created_at: 2025-03-31T09:39:33Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,425 @@
+# [TAP 7.1] Solution Design Hausanschluss Bundle Konzept
+
+# 1 Business Case
+
+## 1.1 Executive Summary
+
+The EDC "Hausanschluss" Bundle aims to simplify the installation of the enablement services Eclipse Dataspace
+Connector (EDC), Digital Twin Registry (DTR), and their supporting components. By developing a flexible, parameterizable
+installation package, the project seeks to reduce deployment complexity and lower barriers to participation in the
+Catena‑X data space. This bundle will enable independent component updates and support a modular "bring your own"
+approach, ultimately fostering a more efficient and accessible ecosystem for diverse participants—such as testers,
+external developers, and small and medium-sized enterprises.
+
+## 1.2 Business Need
+
+Current deployment methods for data space integration are complex and require significant manual effort. This PoC
+addresses the need to:
+
+- Reduce Complexity: Simplify the deployment topology by bundling components into capabilities.
+- Automate Deployment: Provide an automated installation package using Kubernetes and HELM.
+- Reduce Configuration Efforts: Streamline and reduce the number of configuration steps required for integration.
+- Extend Documentation: Provide a detailed documentation tailored to the target groups.
+- Enable Extension: Design the system to allow the seamless addition of new components or capabilities.
+
+## 1.3 Objectives
+
+- Simplify Deployment and Maintenance: Develop an installation package that minimizes manual configuration through
+  automation.
+- Ensure Modularity: Structure the bundle so that components can be independently installed, updated, or replaced
+  without
+  affecting other services.
+- Facilitate Flexibility: Implement a "bring your own" model for key components, such as EDC, PostgreSQL, and HashiCorp
+  Vault, to allow tailored deployments that meet specific needs.
+- Increase Accessibility: Lower entry barriers for new participants by reducing technical complexity and operational
+  dependencies.
+- Scalability: Structure the bundle so that it can be deployed multiple times.
+
+## 1.4 Expected Deliverables
+
+- PoC Documentation: A concept and architecture overview highlighting the modular design.
+- Modular Installation Package: A set of HELM charts for deploying the enablement service bundles:
+    - EDC Bundle: Including the Eclipse Dataspace Connector, EDC PostgreSQL, and HashiCorp Vault.
+    - Digital Twin Bundle: Featuring components such as the Decentral DT Registry (with “bring your own” PostgreSQL) and
+      a Submodel Server Bundle.
+    - Identity Wallet Bundle: Covering the Identity Wallet functionality.
+- Demonstration Environment: A test deployment showcasing reduced complexity and improved efficiency.
+- Basic User Guide: Instructions on how to deploy and update the PoC bundle.
+
+## 1.5 Benefits
+
+- Operational Efficiency: Faster and more reliable deployments with less manual work.
+- Scalability: A modular design that can be scaled or adapted for future full-scale deployments.
+- Ease of Adoption: Simplified deployment processes make it easier for testers and external developers to engage.
+
+## 1.6. Dependencies
+
+- Interoperability with the CATENA‑X standards.
+
+## 1.7. Success Criteria
+
+- Technology Readiness Level: Achievement of a Technology Readiness Level (TRL) of 3, as specified in the requirements.
+- Functional PoC Deployment: Demonstrated automated, modular installation with reduced manual steps.
+- Simplified Configuration: Clear evidence of reduced configuration complexity.
+- Positive Feedback: End-user validation from a select group of demo participants and the Tractus-X community.
+- Documentation Completeness: Availability of concise deployment and user guides.
+
+## 1.8. Out of Scope
+
+- Full Production Readiness: This PoC is not intended to be a production-ready solution.
+- Core Services Exclusion: Core services are not part of the Hausanschluss Bundles.
+- App Provider Role: The role of App Provider is considered out of scope for this deployment.
+- Alternative Deployment Techniques: While the evaluation of alternative deployment methods is acknowledged, the primary
+  focus remains on Kubernetes and HELM-based deployment.
+
+# 2 Requirements Analysis
+
+## 2.1 Assumptions
+
+## 2.2 Requirements Catalog
+
+| ID             | Requirement                                                                                                                                                                                                                                                                                                                                               | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | Deliverables / Acceptance Criteria                                                                                                           |
+|----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------|
+| [WP-7.1.-D001] | TAP7.1 Hausanschluss Bundle aims to simplify the installation and maintenance of the EDC and other components that together ensure a “home connection”. A flexible, parameterizable installation package is intended to reduce complexity and make integration more efficient, thereby simplifying participation in Catena‑X for additional participants. | Specification and development of a flexible, parameterizable installation package that reduces the complexity of installing and maintaining the required components for seamless integration into the Catena‑X data space. This package should facilitate updates and new versions, making participation in Catena‑X more efficient and accessible. In doing so, SMEs shall be enabled to participate without high costs or dependency on SaaS providers while maintaining control over their IT infrastructure. | [WP-7.1.-D001] Concept for the Hausanschluss is created                                                                                      |
+| 7.1.1.1        | The solution concept must define the Capability Bundles structures to be implemented. For each Capability Bundle, the included bundles and their versions are mapped.                                                                                                                                                                                     | "The following Capability Bundle structure is implemented:                                                                                                                                                                                                                                                                                                                                                                                                                                                       | "The structure of the Capability Bundles for the Enablement Services has been specified.                                                     |
+| 7.1.1.2        | Definition of Data Space Roles                                                                                                                                                                                                                                                                                                                            | Capability EDC (Data Transfer) Bundle                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | For version R24.12 it is clearly defined which Tractus‑X services and components are assigned to each Capability Bundle"                     |
+| 7.1.1.4        | Modularity & Maintainability: No dependencies between Capability Bundles                                                                                                                                                                                                                                                                                  | Eclipse Dataspace Connector (EDC) v0.9.0                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | "As part of the target group analysis, the target groups are defined and aligned with the data space roles.                                  |
+| 7.1.1.5        | Modularity & Maintainability: Concept for reducing deployment complexity                                                                                                                                                                                                                                                                                  | EDC PostgresSQL                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | Mapping from data space role to target group has been completed.                                                                             |
+| 7.1.1.6        | Modularity & Maintainability                                                                                                                                                                                                                                                                                                                              | HashiCorp Vault                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | Mapping from target group to data space role has been completed.                                                                             |
+| 7.1.1.13       | Solution Concept                                                                                                                                                                                                                                                                                                                                          | Capability Digital Twin Bundle                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | An assignment of data space roles to Capability Bundles has been made."                                                                      |
+| 7.1.1.14       | Scalability of Enablement Services                                                                                                                                                                                                                                                                                                                        | Decentral DT Registry                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | "Components and Services should obly be part of one bundle.                                                                                  |
+| 7.1.1.16       | Interoperability                                                                                                                                                                                                                                                                                                                                          | PostgresSQL                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | Each bundle must be deployable in isolation and can be installed, updated, or removed independently.                                         |
+| [WP-7.1.-D002] | [WP-7.1.-D002] Target group for the specification is defined.                                                                                                                                                                                                                                                                                             | Capability Identity & Trust (Identity Wallet Bundle)                                                                                                                                                                                                                                                                                                                                                                                                                                                             | Capability Bundles must be organized in separate HELM sub‑charts.                                                                            |
+| 7.1.2.1        | Target Group Analysis                                                                                                                                                                                                                                                                                                                                     | Identity Wallet Mock                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | Circular dependencies between bundles must be avoided."                                                                                      |
+| [WP-7.1.-D003] | [WP-7.1.-D003] Decentralized components and services defined                                                                                                                                                                                                                                                                                              | Capability Semantic Model Bundle                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | "Simplification of deployment processes                                                                                                      |
+| 7.1.3.1        | See [WP-7.1.-D001-AC001]                                                                                                                                                                                                                                                                                                                                  | Submodel Mock (aus Umbrella HELM Chart)"                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | A reduction of manual configuration steps has been achieved.                                                                                 |
+| [WP-7.1.-D004] | [WP-7.1.-D004] Documentation of the Hausanschluss Bundle is completed                                                                                                                                                                                                                                                                                     | "Data Consumer                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | Transparency and traceability                                                                                                                |
+| 7.1.4.1        | Documentation of the Hausanschluss-Bundles                                                                                                                                                                                                                                                                                                                | Data Provider                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | Clearly documented deployment steps are provided.                                                                                            |
+| 7.1.4.2        | Documentation of the Hausanschluss-Bundles                                                                                                                                                                                                                                                                                                                | Enablement Service Provider"                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | Improvements of Chart configuration by                                                                                                       |
+| [WP-7.1.-D005] | [WP-7.1.-D005] Umbrella HELM Charts for the Hausanschluss developed, tested, and documented                                                                                                                                                                                                                                                               | "Unique assignment of components and services to a defined Capability Bundle.                                                                                                                                                                                                                                                                                                                                                                                                                                    | usage of template                                                                                                                            |
+| 7.1.5.1        | Re-activate Umbrella HELM Charts to the latest release state                                                                                                                                                                                                                                                                                              | Each component and service should be assigned to only one Capability Bundle.                                                                                                                                                                                                                                                                                                                                                                                                                                     | reducing configuration options                                                                                                               |
+| 7.1.5.2        | Hierarchical structuring and bundling of Enablement Service components in the Umbrella HELM Chart                                                                                                                                                                                                                                                         | Dependencies between Capability Bundles are allowed."                                                                                                                                                                                                                                                                                                                                                                                                                                                            | reducing manual steps in the setup"                                                                                                          |
+| 7.1.5.3        | Interchangeability of bundle components via “Bring-Your-Own” components                                                                                                                                                                                                                                                                                   | The system deployment should be optimized to reduce the existing complexity. The goal is to make the provisioning process more efficient, robust, and easier to maintain.                                                                                                                                                                                                                                                                                                                                        | Charts are published via a publicly accessible charts repository.                                                                            |
+| [WP-7.1.-D006] | [WP-7.1.-D006] Product developed according to a Technology Readiness Level (TRL) of 3                                                                                                                                                                                                                                                                     | Charts are published automatically.                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | "The solution design for the ""Hausanschluss"" Bundle is created.                                                                            |
+| 7.1.6.1        | POC                                                                                                                                                                                                                                                                                                                                                       | Creation of a solution design for the “Hausanschluss” Bundle.                                                                                                                                                                                                                                                                                                                                                                                                                                                    | The solution design for the ""Hausanschluss"" Bundle ispublished in the repository: https://github.com/eclipse-tractusx/tractus-x-umbrella." |
+| 7.1.6.2        | Deployment Strategy                                                                                                                                                                                                                                                                                                                                       | Scalability of Enablement Services                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | "Developers should be able to deploy an arbitrary number of Enablement Services.                                                             |
+
+# 3 AS-IS Analysis
+
+## 3.1 People
+
+### 3.1.1 Target Group Analysis
+
+See "4.1.1 To-be Target Group Analysis" below. No deviations between As-is and To-be target groups have been identified.
+
+## 3.2 Process
+
+### 3.2.1 Use Case View (high-level)
+
+Umbrella Chart is intended for the following Use Cases:
+
+| Actor             | Use case                                                                                             |
+|-------------------|------------------------------------------------------------------------------------------------------|
+| Product Developer | Sandbox Environments: Create local environments to evaluate and experiment with Catena-X components. |
+| Product Developer | Development: Provide a unified setup for contributors and developers working on Tractus-X projects.  |
+| Product Tester    | Testing: Run end-to-end tests for Catena-X services.                                                 |
+
+## 3.4 System
+
+### 3.4.1 Context Delimitation
+
+````mermaid
+flowchart
+    subgraph "Umbrella Chart"
+        ChartYaml["Chart.yaml"]
+        subgraph charts
+            Portal["Portal"]
+            CentralIdp["CentralIdp"]
+            DiscoveryFinder["Discovery Finder"]
+            SDFactory["SD-Factory"]
+            SSICredentialIssuer["SSI Credential Issuer"]
+            SemanticHub["Semantic Hub"]
+            BPDM["BPDM"]
+            DataConsumer["Data Consumer"]
+            DataProvider["Data Provider"]
+            BDRS["BDRS"]
+            SSIWalletStub["SSI Wallet Stub"]
+        end
+        subgraph "tx-data-provider"
+            EDC["EDC"]
+            DTR["DTR"]
+            SubmodelServer["Submodel Server"]
+        end
+    end
+
+    ChartYaml --> Portal
+    ChartYaml --> CentralIdp
+    ChartYaml --> DiscoveryFinder
+    ChartYaml --> SDFactory
+    ChartYaml --> SSICredentialIssuer
+    ChartYaml --> SemanticHub
+    ChartYaml --> BPDM
+    ChartYaml --> DataConsumer
+    ChartYaml --> DataProvider
+    ChartYaml --> BDRS
+    ChartYaml --> SSIWalletStub
+    DataConsumer --> EDC
+    DataProvider --> EDC
+    DataProvider --> DTR
+    DataProvider --> SubmodelServer
+````
+
+#### Existing Umbrella Chart Structure
+
+# 4 TO-BE Design
+
+## 4.1 People
+
+### 4.1.1 Target Group Analysis
+
+Overall data space roles: https://catena-x.net/en/1/catena-x-introduce-implement/how-to-operate-catena-x
+
+The relevant data space roles for us under requirement 7.1.1.1 are:
+
+- Data Consumer
+- Data Provider
+- Enablement Service Provider
+
+Scope: Umbrella HELM Charts
+
+- Enablement Services: These services are included under the umbrella of HELM charts, focusing on enabling
+  functionalities.
+- Out of Scope: Core services such as Portal or BPDM are not considered within this scope.
+
+Primary target groups:
+
+| No. | Target group                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | Data space roles                                                    | Target group differentiation                                                                                                                                                                                                                                                                            | Behaviour, Needs, Pains & Usage                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+|-----|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| 1   | Developers<ul><li>External Developers (not Tractus-X developers): Utilize the chart for demonstration or evaluation purposes.</li><li>Experienced software and product developers who are developing a business app for a CATENA-X data space. They need to develop the app against the interfaces of the data space and integrate them accordingly.</li><li>They emphasize efficient and cost-effective implementation:<ul><li>Cost Efficiency: They do not want to use expensive SaaS solutions.</li><li>Technical Independence: They lack the knowledge and capacity to deploy the enablement and core services of the data space themselves.</li><li>Focus on Development: They concentrate on application development without delving deeply into the deployment and operation of the underlying infrastructure.</li></ul></li><li>Out of Scope: Developers running tests in test runners are not considered within this scope.</li></ul> | Data Consumer <br/> Data Provider <br/> Enablement Service Provider |                                                                                                                                                                                                                                                                                                         | <ul><li>Needs / sources of information<ul><li><a href="https://eclipse-tractusx.github.io/Kits/">Kit documentation tractus-x</a> for interaction purposes</li><li><a href="https://catenax-ev.github.io/">Catena-X doucmentation</a> for standards and regulations</li><li><a href="https://github.com/eclipse-tractusx/tractus-x-umbrella">Umbrella documentation</a> for umbrella component information</li></ul></li><li>Challenges → Solution<ul><li>Decentralization e.g. Where are other systems? How to interact with them? → Solution: Umbrella charts and bundles for deployment</li><li>Complex setup → Solution: delivery of small capability bundles</li></ul></li></ul> |
+| 2   | <ul><li>Tester requiring a test system (Testmanagement e.V.)</li><li>Requirement: Testbed</li></ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | Data Consumer <br/> Data Provider <br/> Enablement Service Provider | <ul><li>Developer (1) tests their feature.</li><li>Tester (2) performs end-to-end testing.</li><li>For the tester, the modular structure is less relevant since they focus on E2E testing, whereas the developer selects the required components.</li><li>The testbed must be easy to deploy.</li></ul> | <ul><li>Same as above from an End-to-end testing perspective</li><li>Typically a tester has less technical know-how than a developer and therefore needs a "one-size-fits-all" chart for easier testing</li></ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+
+## 4.2 Process
+
+### 4.2.1 Use Case View (high-level)
+
+| Use Case                                | Description                                                                                                       | Actors            |
+|-----------------------------------------|-------------------------------------------------------------------------------------------------------------------|-------------------|
+| Configure HELM Chart                    | The product developer configures the HELM Chart for the specific environment.                                     | Product Developer |
+| Configure Secrets                       | The product developer manages and configures secrets.                                                             | Product Developer |
+| Execute Deployment Pipeline             | The product developer successfully executes the deployment pipeline for the HELM Chart.                           | Product Developer |
+| Integrate EDC, DTR, and Identity Wallet | The actors integrate the components EDC, Digital Twin Registry, and Identity Wallet for seamless interoperability | Product Developer |
+| Set Up Connection Infrastructure        | The actor sets up the connection infrastructure for linking to the central data space infrastructure.             | Product Developer |
+| Maintain Infrastructure Module          | The product developer maintains the modular architecture of the HELM Chart.                                       | Product Developer |
+| Ensure Scalability                      | The product developer ensures scalability to support growing numbers of users and data volumes.                   | Product Developer |
+| Sandbox Environments                    | The product developer creates local environments to evaluate and experiment with Catena-X components.             | Product Developer |
+| E2E Testing                             | The product tester runs end-to-end tests for Catena-X services.                                                   | Product Tester    |
+
+### 4.2.2 Business Process (SCC Artifact)
+
+#### Chart Release Process
+
+Charts will be released using the already existing workflow in the Umbrella Chart repository. The workflow will
+automatically release a Chart, once it is pushed to the "charts/" directory with a new Chart version.
path: docs/concept/TAP7.1-solution-design.md
user: login: ds-jhartmann
body: added a remark to semantic versioning
created_at: 2025-03-31T12:17:04Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,425 @@
+# [TAP 7.1] Solution Design Hausanschluss Bundle Konzept
+
+# 1 Business Case
+
+## 1.1 Executive Summary
+
+The EDC "Hausanschluss" Bundle aims to simplify the installation of the enablement services Eclipse Dataspace
+Connector (EDC), Digital Twin Registry (DTR), and their supporting components. By developing a flexible, parameterizable
+installation package, the project seeks to reduce deployment complexity and lower barriers to participation in the
+Catena‑X data space. This bundle will enable independent component updates and support a modular "bring your own"
+approach, ultimately fostering a more efficient and accessible ecosystem for diverse participants—such as testers,
+external developers, and small and medium-sized enterprises.
+
+## 1.2 Business Need
+
+Current deployment methods for data space integration are complex and require significant manual effort. This PoC
+addresses the need to:
+
+- Reduce Complexity: Simplify the deployment topology by bundling components into capabilities.
+- Automate Deployment: Provide an automated installation package using Kubernetes and HELM.
+- Reduce Configuration Efforts: Streamline and reduce the number of configuration steps required for integration.
+- Extend Documentation: Provide a detailed documentation tailored to the target groups.
+- Enable Extension: Design the system to allow the seamless addition of new components or capabilities.
+
+## 1.3 Objectives
+
+- Simplify Deployment and Maintenance: Develop an installation package that minimizes manual configuration through
+  automation.
+- Ensure Modularity: Structure the bundle so that components can be independently installed, updated, or replaced
+  without
+  affecting other services.
+- Facilitate Flexibility: Implement a "bring your own" model for key components, such as EDC, PostgreSQL, and HashiCorp
+  Vault, to allow tailored deployments that meet specific needs.
+- Increase Accessibility: Lower entry barriers for new participants by reducing technical complexity and operational
+  dependencies.
+- Scalability: Structure the bundle so that it can be deployed multiple times.
+
+## 1.4 Expected Deliverables
+
+- PoC Documentation: A concept and architecture overview highlighting the modular design.
+- Modular Installation Package: A set of HELM charts for deploying the enablement service bundles:
+    - EDC Bundle: Including the Eclipse Dataspace Connector, EDC PostgreSQL, and HashiCorp Vault.
+    - Digital Twin Bundle: Featuring components such as the Decentral DT Registry (with “bring your own” PostgreSQL) and
+      a Submodel Server Bundle.
+    - Identity Wallet Bundle: Covering the Identity Wallet functionality.
+- Demonstration Environment: A test deployment showcasing reduced complexity and improved efficiency.
+- Basic User Guide: Instructions on how to deploy and update the PoC bundle.
+
+## 1.5 Benefits
+
+- Operational Efficiency: Faster and more reliable deployments with less manual work.
+- Scalability: A modular design that can be scaled or adapted for future full-scale deployments.
+- Ease of Adoption: Simplified deployment processes make it easier for testers and external developers to engage.
+
+## 1.6. Dependencies
+
+- Interoperability with the CATENA‑X standards.
+
+## 1.7. Success Criteria
+
+- Technology Readiness Level: Achievement of a Technology Readiness Level (TRL) of 3, as specified in the requirements.
+- Functional PoC Deployment: Demonstrated automated, modular installation with reduced manual steps.
+- Simplified Configuration: Clear evidence of reduced configuration complexity.
+- Positive Feedback: End-user validation from a select group of demo participants and the Tractus-X community.
+- Documentation Completeness: Availability of concise deployment and user guides.
+
+## 1.8. Out of Scope
+
+- Full Production Readiness: This PoC is not intended to be a production-ready solution.
+- Core Services Exclusion: Core services are not part of the Hausanschluss Bundles.
+- App Provider Role: The role of App Provider is considered out of scope for this deployment.
+- Alternative Deployment Techniques: While the evaluation of alternative deployment methods is acknowledged, the primary
+  focus remains on Kubernetes and HELM-based deployment.
+
+# 2 Requirements Analysis
+
+## 2.1 Assumptions
+
+## 2.2 Requirements Catalog
+
+| ID             | Requirement                                                                                                                                                                                                                                                                                                                                               | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | Deliverables / Acceptance Criteria                                                                                                           |
+|----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------|
+| [WP-7.1.-D001] | TAP7.1 Hausanschluss Bundle aims to simplify the installation and maintenance of the EDC and other components that together ensure a “home connection”. A flexible, parameterizable installation package is intended to reduce complexity and make integration more efficient, thereby simplifying participation in Catena‑X for additional participants. | Specification and development of a flexible, parameterizable installation package that reduces the complexity of installing and maintaining the required components for seamless integration into the Catena‑X data space. This package should facilitate updates and new versions, making participation in Catena‑X more efficient and accessible. In doing so, SMEs shall be enabled to participate without high costs or dependency on SaaS providers while maintaining control over their IT infrastructure. | [WP-7.1.-D001] Concept for the Hausanschluss is created                                                                                      |
+| 7.1.1.1        | The solution concept must define the Capability Bundles structures to be implemented. For each Capability Bundle, the included bundles and their versions are mapped.                                                                                                                                                                                     | "The following Capability Bundle structure is implemented:                                                                                                                                                                                                                                                                                                                                                                                                                                                       | "The structure of the Capability Bundles for the Enablement Services has been specified.                                                     |
+| 7.1.1.2        | Definition of Data Space Roles                                                                                                                                                                                                                                                                                                                            | Capability EDC (Data Transfer) Bundle                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | For version R24.12 it is clearly defined which Tractus‑X services and components are assigned to each Capability Bundle"                     |
+| 7.1.1.4        | Modularity & Maintainability: No dependencies between Capability Bundles                                                                                                                                                                                                                                                                                  | Eclipse Dataspace Connector (EDC) v0.9.0                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | "As part of the target group analysis, the target groups are defined and aligned with the data space roles.                                  |
+| 7.1.1.5        | Modularity & Maintainability: Concept for reducing deployment complexity                                                                                                                                                                                                                                                                                  | EDC PostgresSQL                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | Mapping from data space role to target group has been completed.                                                                             |
+| 7.1.1.6        | Modularity & Maintainability                                                                                                                                                                                                                                                                                                                              | HashiCorp Vault                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | Mapping from target group to data space role has been completed.                                                                             |
+| 7.1.1.13       | Solution Concept                                                                                                                                                                                                                                                                                                                                          | Capability Digital Twin Bundle                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | An assignment of data space roles to Capability Bundles has been made."                                                                      |
+| 7.1.1.14       | Scalability of Enablement Services                                                                                                                                                                                                                                                                                                                        | Decentral DT Registry                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | "Components and Services should obly be part of one bundle.                                                                                  |
+| 7.1.1.16       | Interoperability                                                                                                                                                                                                                                                                                                                                          | PostgresSQL                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | Each bundle must be deployable in isolation and can be installed, updated, or removed independently.                                         |
+| [WP-7.1.-D002] | [WP-7.1.-D002] Target group for the specification is defined.                                                                                                                                                                                                                                                                                             | Capability Identity & Trust (Identity Wallet Bundle)                                                                                                                                                                                                                                                                                                                                                                                                                                                             | Capability Bundles must be organized in separate HELM sub‑charts.                                                                            |
+| 7.1.2.1        | Target Group Analysis                                                                                                                                                                                                                                                                                                                                     | Identity Wallet Mock                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | Circular dependencies between bundles must be avoided."                                                                                      |
+| [WP-7.1.-D003] | [WP-7.1.-D003] Decentralized components and services defined                                                                                                                                                                                                                                                                                              | Capability Semantic Model Bundle                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | "Simplification of deployment processes                                                                                                      |
+| 7.1.3.1        | See [WP-7.1.-D001-AC001]                                                                                                                                                                                                                                                                                                                                  | Submodel Mock (aus Umbrella HELM Chart)"                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | A reduction of manual configuration steps has been achieved.                                                                                 |
+| [WP-7.1.-D004] | [WP-7.1.-D004] Documentation of the Hausanschluss Bundle is completed                                                                                                                                                                                                                                                                                     | "Data Consumer                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | Transparency and traceability                                                                                                                |
+| 7.1.4.1        | Documentation of the Hausanschluss-Bundles                                                                                                                                                                                                                                                                                                                | Data Provider                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | Clearly documented deployment steps are provided.                                                                                            |
+| 7.1.4.2        | Documentation of the Hausanschluss-Bundles                                                                                                                                                                                                                                                                                                                | Enablement Service Provider"                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | Improvements of Chart configuration by                                                                                                       |
+| [WP-7.1.-D005] | [WP-7.1.-D005] Umbrella HELM Charts for the Hausanschluss developed, tested, and documented                                                                                                                                                                                                                                                               | "Unique assignment of components and services to a defined Capability Bundle.                                                                                                                                                                                                                                                                                                                                                                                                                                    | usage of template                                                                                                                            |
+| 7.1.5.1        | Re-activate Umbrella HELM Charts to the latest release state                                                                                                                                                                                                                                                                                              | Each component and service should be assigned to only one Capability Bundle.                                                                                                                                                                                                                                                                                                                                                                                                                                     | reducing configuration options                                                                                                               |
+| 7.1.5.2        | Hierarchical structuring and bundling of Enablement Service components in the Umbrella HELM Chart                                                                                                                                                                                                                                                         | Dependencies between Capability Bundles are allowed."                                                                                                                                                                                                                                                                                                                                                                                                                                                            | reducing manual steps in the setup"                                                                                                          |
+| 7.1.5.3        | Interchangeability of bundle components via “Bring-Your-Own” components                                                                                                                                                                                                                                                                                   | The system deployment should be optimized to reduce the existing complexity. The goal is to make the provisioning process more efficient, robust, and easier to maintain.                                                                                                                                                                                                                                                                                                                                        | Charts are published via a publicly accessible charts repository.                                                                            |
+| [WP-7.1.-D006] | [WP-7.1.-D006] Product developed according to a Technology Readiness Level (TRL) of 3                                                                                                                                                                                                                                                                     | Charts are published automatically.                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | "The solution design for the ""Hausanschluss"" Bundle is created.                                                                            |
+| 7.1.6.1        | POC                                                                                                                                                                                                                                                                                                                                                       | Creation of a solution design for the “Hausanschluss” Bundle.                                                                                                                                                                                                                                                                                                                                                                                                                                                    | The solution design for the ""Hausanschluss"" Bundle ispublished in the repository: https://github.com/eclipse-tractusx/tractus-x-umbrella." |
+| 7.1.6.2        | Deployment Strategy                                                                                                                                                                                                                                                                                                                                       | Scalability of Enablement Services                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | "Developers should be able to deploy an arbitrary number of Enablement Services.                                                             |
+
+# 3 AS-IS Analysis
+
+## 3.1 People
+
+### 3.1.1 Target Group Analysis
+
+See "4.1.1 To-be Target Group Analysis" below. No deviations between As-is and To-be target groups have been identified.
+
+## 3.2 Process
+
+### 3.2.1 Use Case View (high-level)
+
+Umbrella Chart is intended for the following Use Cases:
+
+| Actor             | Use case                                                                                             |
+|-------------------|------------------------------------------------------------------------------------------------------|
+| Product Developer | Sandbox Environments: Create local environments to evaluate and experiment with Catena-X components. |
+| Product Developer | Development: Provide a unified setup for contributors and developers working on Tractus-X projects.  |
+| Product Tester    | Testing: Run end-to-end tests for Catena-X services.                                                 |
+
+## 3.4 System
+
+### 3.4.1 Context Delimitation
+
+````mermaid
+flowchart
+    subgraph "Umbrella Chart"
+        ChartYaml["Chart.yaml"]
+        subgraph charts
+            Portal["Portal"]
+            CentralIdp["CentralIdp"]
+            DiscoveryFinder["Discovery Finder"]
+            SDFactory["SD-Factory"]
+            SSICredentialIssuer["SSI Credential Issuer"]
+            SemanticHub["Semantic Hub"]
+            BPDM["BPDM"]
+            DataConsumer["Data Consumer"]
+            DataProvider["Data Provider"]
+            BDRS["BDRS"]
+            SSIWalletStub["SSI Wallet Stub"]
+        end
+        subgraph "tx-data-provider"
+            EDC["EDC"]
+            DTR["DTR"]
+            SubmodelServer["Submodel Server"]
+        end
+    end
+
+    ChartYaml --> Portal
+    ChartYaml --> CentralIdp
+    ChartYaml --> DiscoveryFinder
+    ChartYaml --> SDFactory
+    ChartYaml --> SSICredentialIssuer
+    ChartYaml --> SemanticHub
+    ChartYaml --> BPDM
+    ChartYaml --> DataConsumer
+    ChartYaml --> DataProvider
+    ChartYaml --> BDRS
+    ChartYaml --> SSIWalletStub
+    DataConsumer --> EDC
+    DataProvider --> EDC
+    DataProvider --> DTR
+    DataProvider --> SubmodelServer
+````
+
+#### Existing Umbrella Chart Structure
+
+# 4 TO-BE Design
+
+## 4.1 People
+
+### 4.1.1 Target Group Analysis
+
+Overall data space roles: https://catena-x.net/en/1/catena-x-introduce-implement/how-to-operate-catena-x
+
+The relevant data space roles for us under requirement 7.1.1.1 are:
+
+- Data Consumer
+- Data Provider
+- Enablement Service Provider
+
+Scope: Umbrella HELM Charts
+
+- Enablement Services: These services are included under the umbrella of HELM charts, focusing on enabling
path: docs/concept/TAP7.1-solution-design.md
user: login: ds-jhartmann
body: moved out of scope out of the list
created_at: 2025-03-31T12:17:20Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,425 @@
+# [TAP 7.1] Solution Design Hausanschluss Bundle Konzept
+
+# 1 Business Case
+
+## 1.1 Executive Summary
+
+The EDC "Hausanschluss" Bundle aims to simplify the installation of the enablement services Eclipse Dataspace
+Connector (EDC), Digital Twin Registry (DTR), and their supporting components. By developing a flexible, parameterizable
+installation package, the project seeks to reduce deployment complexity and lower barriers to participation in the
+Catena‑X data space. This bundle will enable independent component updates and support a modular "bring your own"
+approach, ultimately fostering a more efficient and accessible ecosystem for diverse participants—such as testers,
+external developers, and small and medium-sized enterprises.
+
+## 1.2 Business Need
+
+Current deployment methods for data space integration are complex and require significant manual effort. This PoC
+addresses the need to:
+
+- Reduce Complexity: Simplify the deployment topology by bundling components into capabilities.
+- Automate Deployment: Provide an automated installation package using Kubernetes and HELM.
+- Reduce Configuration Efforts: Streamline and reduce the number of configuration steps required for integration.
path: docs/concept/TAP7.1-solution-design.md
user: login: ds-jhartmann
body: rephrased to a more qualitative description
created_at: 2025-03-31T12:17:35Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,424 @@
+# [TAP 7.1] Solution Design Hausanschluss Bundle Konzept
+
+# 1 Business Case
+
+## 1.1 Executive Summary
+
+The EDC "Hausanschluss" Bundle aims to simplify the installation of the enablement services Eclipse Dataspace
+Connector (EDC), Digital Twin Registry (DTR), and their supporting components. By developing a flexible, parameterizable
+installation package, the project seeks to reduce deployment complexity and lower barriers to participation in the
+Catena‑X data space. This bundle will enable independent component updates and support a modular "bring your own"
+approach, ultimately fostering a more efficient and accessible ecosystem for diverse participants—such as testers,
+external developers, and small and medium-sized enterprises.
+
+## 1.2 Business Need
+
+Current deployment methods for data space integration are complex and require significant manual effort. This PoC
+addresses the need to:
+
+- **Reduce Complexity:** Simplify the deployment topology by bundling components into capabilities.
+- **Automate Deployment:** Provide an automated installation package using Kubernetes and HELM.
+- **Reduce Configuration Efforts:** Streamline and reduce the number of configuration steps required for integration.
+- **Extend Documentation:** Provide a detailed documentation tailored to the target groups.
+- **Enable Extension:** Design the system to allow the seamless addition of new components or capabilities.
+
+## 1.3 Objectives
+
+- **Simplify Deployment and Maintenance:** Develop an installation package that minimizes manual configuration through
+  automation.
+- **Ensure Modularity:** Structure the bundle so that components can be independently installed, updated, or replaced
+  without affecting other services.
+- **Facilitate Flexibility:** Implement a "bring your own" model for key components, such as EDC, PostgreSQL, and HashiCorp
+  Vault, to allow tailored deployments that meet specific needs.
+- **Increase Accessibility**: Lower entry barriers for new participants by reducing technical complexity and operational
+  dependencies.
+- **Scalability:** Structure the bundles so that they can be deployed multiple times.
+
+## 1.4 Expected Deliverables
+
+- **PoC Documentation:** A concept and architecture overview highlighting the modular design.
+- **Modular Installation Package:** A set of HELM charts for deploying the enablement service bundles:
+    - **Dataspace Connector:** Including the Eclipse Dataspace Connector, EDC PostgreSQL, and HashiCorp Vault.
+    - **Digital Twin Bundle:** Featuring components such as the Decentral DT Registry (with “bring your own” PostgreSQL)
+    - **Data Persitence Layer Bundle:** Including a simple Submodel Server to store semantic data.
+    - **Identity Wallet Bundle:** Covering the Identity Wallet functionality.
+- **Demonstration Environment:** A test deployment showcasing reduced complexity and improved efficiency.
+- **Basic User Guide:** Instructions on how to deploy and update the PoC bundle.
+
+## 1.5 Benefits
+
+- **Operational Efficiency:** Faster and more reliable deployments with less manual work.
+- **Scalability:** A modular design that can be scaled or adapted for future full-scale deployments.
+- **Ease of Adoption:** Simplified deployment processes make it easier for testers and external developers to engage.
+
+## 1.6. Dependencies
+
+- **Interoperability** with the CATENA‑X standards.
+
+## 1.7. Success Criteria
+
+- **Technology Readiness Level:** Achievement of a Technology Readiness Level (TRL) of 3, as specified in the requirements.
+- **Functional PoC Deployment:** Demonstrated automated, modular installation with reduced manual steps.
+- **Simplified Configuration:** Clear evidence of reduced configuration complexity.
+- **Positive Feedback:** End-user validation from a select group of demo participants and the Tractus-X community.
+- **Documentation Completeness:** Availability of concise deployment and user guides.
+
+## 1.8. Out of Scope
+
+- **Full Production Readiness:** This PoC is not intended to be a production-ready solution.
+- **Core Services Exclusion:** Core services are not part of the Hausanschluss Bundles.
+- **App Provider Role:** The role of App Provider is considered out of scope for this deployment.
+- **Alternative Deployment Techniques:** While the evaluation of alternative deployment methods is acknowledged, the primary
+  focus remains on Kubernetes and HELM-based deployment.
+
+# 2 Requirements Analysis
+
+## 2.1 Assumptions
+
+## 2.2 Requirements Catalog
+
+| ID             | Requirement                                                                                                                                                                                                                                                                                                                                               | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | Deliverables / Acceptance Criteria                                                                                                                                                                                                                                                                                                                                                                                   |
+|----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| [WP-7.1.-D001] | TAP7.1 Hausanschluss Bundle aims to simplify the installation and maintenance of the EDC and other components that together ensure a “home connection”. A flexible, parameterizable installation package is intended to reduce complexity and make integration more efficient, thereby simplifying participation in Catena‑X for additional participants. | Specification and development of a flexible, parameterizable installation package that reduces the complexity of installing and maintaining the required components for seamless integration into the Catena‑X data space. This package should facilitate updates and new versions, making participation in Catena‑X more efficient and accessible. In doing so, SMEs shall be enabled to participate without high costs or dependency on SaaS providers while maintaining control over their IT infrastructure. | [WP-7.1.-D001] Concept for the Hausanschluss is created                                                                                                                                                                                                                                                                                                                                                              |
+| 7.1.1.1        | The solution concept must define the Capability Bundles structures to be implemented. For each Capability Bundle, the included bundles and their versions are mapped.                                                                                                                                                                                     | "The following Capability Bundle structure is implemented:                                                                                                                                                                                                                                                                                                                                                                                                                                                       | The structure of the Capability Bundles for the Enablement Services has been specified. For version R24.12 it is clearly defined which Tractus‑X services and components are assigned to each Capability Bundle                                                                                                                                                                                                      |
+| 7.1.1.2        | Definition of Data Space Roles                                                                                                                                                                                                                                                                                                                            | Data Consumer, Data Provider, Enablement Service Provider                                                                                                                                                                                                                                                                                                                                                                                                                                                        | As part of the target group analysis, the target groups are defined and aligned with the data space roles. <br>Mapping from data space role to target group has been completed. <br>Mapping from target group to data space role has been completed. <br>An assignment of data space roles to Capability Bundles has been made.                                                                                      |
+| 7.1.1.4        | Modularity & Maintainability: No dependencies between Capability Bundles                                                                                                                                                                                                                                                                                  | Unique assignment of components and services to a defined Capability Bundle. <br>Each component and service should be assigned to only one Capability Bundle. <br>Dependencies between Capability Bundles are allowed.                                                                                                                                                                                                                                                                                           | Components and Services should obly be part of one bundle. <br>Each bundle must be deployable in isolation and can be installed, updated, or removed independently. <br>Capability Bundles must be organized in separate HELM sub‑charts. <br>Circular dependencies between bundles must be avoided.                                                                                                                 |
+| 7.1.1.5        | Modularity & Maintainability: Concept for reducing deployment complexity                                                                                                                                                                                                                                                                                  | The system deployment should be optimized to reduce the existing complexity. The goal is to make the provisioning process more efficient, robust, and easier to maintain.                                                                                                                                                                                                                                                                                                                                        | **Simplification of deployment processes:** A reduction of manual configuration steps has been achieved. <br>**Transparency and traceability:** Clearly documented deployment steps are provided. <br>**Improvements of Chart configuration by:** <br>usage of template  <br>reducing configuration options <br>reducing manual steps in the setup                                                                   |
+| 7.1.1.6        | Modularity & Maintainability                                                                                                                                                                                                                                                                                                                              | Charts are published automatically.                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | Charts are published via a publicly accessible charts repository.                                                                                                                                                                                                                                                                                                                                                    |
+| 7.1.1.13       | Solution Concept                                                                                                                                                                                                                                                                                                                                          | Creation of a solution design for the “Hausanschluss” Bundle.                                                                                                                                                                                                                                                                                                                                                                                                                                                    | The solution design for the "Hausanschluss" Bundle is created. <br>The solution design for the "Hausanschluss" Bundle ispublished in the repository: https://github.com/eclipse-tractusx/tractus-x-umbrella.                                                                                                                                                                                                         |
+| 7.1.1.14       | Scalability of Enablement Services                                                                                                                                                                                                                                                                                                                        | Scalability of Enablement Services                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | Developers should be able to deploy an arbitrary number of Enablement Services. <br>Example: Up to 3 EDCs can be provided.                                                                                                                                                                                                                                                                                           |
+| 7.1.1.16       | Interoperability                                                                                                                                                                                                                                                                                                                                          | Interoperability                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | Interoperability with the CATENA‑X standards. <br>This interoperability is documented and traceable.                                                                                                                                                                                                                                                                                                                 |
+| [WP-7.1.-D002] | [WP-7.1.-D002] Target group for the specification is defined.                                                                                                                                                                                                                                                                                             |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | [WP-7.1.-D002] Target group for the specification is defined.                                                                                                                                                                                                                                                                                                                                                        |
+| 7.1.2.1        | Target Group Analysis                                                                                                                                                                                                                                                                                                                                     | The target group analysis for the "Hausanschluss Bundle"is defined.                                                                                                                                                                                                                                                                                                                                                                                                                                              | The analysis has been conducted. <br>The target group is included in the solution concept <br>To be clarified: What is included in the Hausanschluss and who can operate it in which scenario (OEM, SME, service provider, etc.).                                                                                                                                                                                    |
+| [WP-7.1.-D003] | [WP-7.1.-D003] Decentralized components and services defined                                                                                                                                                                                                                                                                                              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | [WP-7.1.-D003] Decentralized components and services have been defined.                                                                                                                                                                                                                                                                                                                                              |
+| 7.1.3.1        | See [WP-7.1.-D001-AC001]                                                                                                                                                                                                                                                                                                                                  |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | See [WP-7.1.-D001-AC001]                                                                                                                                                                                                                                                                                                                                                                                             |
+| [WP-7.1.-D004] | [WP-7.1.-D004] Documentation of the Hausanschluss Bundle is completed                                                                                                                                                                                                                                                                                     |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | [WP-7.1.-D004] Documentation of the Hausanschluss Bundle is completed                                                                                                                                                                                                                                                                                                                                                |
+| 7.1.4.1        | Documentation of the Hausanschluss-Bundles                                                                                                                                                                                                                                                                                                                | Usability                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | Documentation is provided that enables an experienced product developer - with knowledge of Helm Charts, Docker, and Vaults - to deploy the chart independently without external help. <br>A troubleshooting and FAQ section is included to support the developer. <br>Prerequisites, skills, and technology requirements are outlined, detailing what a developer must know to perform the deployment autonomously. |
+| 7.1.4.2        | Documentation of the Hausanschluss-Bundles                                                                                                                                                                                                                                                                                                                | Documentation of the Hausanschluss-Bundles is completed.                                                                                                                                                                                                                                                                                                                                                                                                                                                         | Documentation is provided for: <br>Configuration of the defined bundles according to the specified requirements and parameters <br>Integration of the documentation into the Umbrella HELM Charts <br>Integration into the Umbrella HELM Chart to ensure consistent deployment                                                                                                                                       |
+| [WP-7.1.-D005] | [WP-7.1.-D005] Umbrella HELM Charts for the Hausanschluss developed, tested, and documented                                                                                                                                                                                                                                                               |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | [WP-7.1.-D005] Umbrella HELM Charts for the Hausanschluss have been developed, tested, and documented.                                                                                                                                                                                                                                                                                                               |
+| 7.1.5.1        | Re-activate Umbrella HELM Charts to the latest release state                                                                                                                                                                                                                                                                                              | The Enablement Services components of the Umbrella HELM Charts must be updated to version R24.12. This includes the following upgrades: <br> Upgrade DTR to version R24.12 (#188) <br>Upgrade EDCs to version R24.12 (#193) <br>Update SSI-DIM-Wallet-Stub to version 0.1.8 (#206)                                                                                                                                                                                                                               | The HELM Chart will then contain the updated versions of the components. <br>After the upgrade, the components (DTR, EDCs, SSI‑DIM‑Wallet‑Stub) run stably without functional impairments. <br>The deployment pipeline for the HELM Chart executes successfully <br>Relevant tests & smoke tests (e.g., integration tests) confirm the migration.                                                                    |
+| 7.1.5.2        | Hierarchical structuring and bundling of Enablement Service components in the Umbrella HELM Chart                                                                                                                                                                                                                                                         | The Umbrella HELM Chart should be structured hierarchically so that related Enablement Service components are grouped into bundles. <br>The Umbrella HELM Chart must have a clear hierarchical structure <br> Each Enablement Service component must be assigned to a unique bundle.<br>No circular dependencies between bundles are allowed.                                                                                                                                                                    | The chart is modular and divided into defined bundles. <br>Each bunde can be deployed and maintained independently.                                                                                                                                                                                                                                                                                                  |
+| 7.1.5.3        | Interchangeability of bundle components via “Bring-Your-Own” components                                                                                                                                                                                                                                                                                   | Bundle components should be interchangeable through “Bring-Your-Own” components. <br>“Bring your own” is available for every component and means that these components do not have to be delivered by default with the Umbrella Chart but can be provided by the respective users.                                                                                                                                                                                                                               | Bundle components can be interchanged by “Bring-Your-Own” components.                                                                                                                                                                                                                                                                                                                                                |
+| [WP-7.1.-D006] | [WP-7.1.-D006] Product developed according to a Technology Readiness Level (TRL) of 3                                                                                                                                                                                                                                                                     |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | [WP-7.1.-D006] The product is developed according to a Technology Readiness Level (TRL) of 3                                                                                                                                                                                                                                                                                                                         |
+| 7.1.6.1        | POC                                                                                                                                                                                                                                                                                                                                                       | Creation of a POC for the "Hausanschluss" Bundle                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | POC implementation is completed. <br>POC has been presented in a demo                                                                                                                                                                                                                                                                                                                                                |
+| 7.1.6.2        | Deployment Strategy                                                                                                                                                                                                                                                                                                                                       | The provisioning of bundles is carried out independently. <br>There must be an option to selectively activate or deactivate bundles.                                                                                                                                                                                                                                                                                                                                                                             | Configuration is managed via HELM values, allowing flexible adaptation according to the environment.                                                                                                                                                                                                                                                                                                                 |
+
+# 3 AS-IS Analysis
+
+## 3.1 People
+
+### 3.1.1 Target Group Analysis
+
+See "4.1.1 To-be Target Group Analysis" below. No deviations between As-is and To-be target groups have been identified.
+
+## 3.2 Process
+
+### 3.2.1 Use Case View (high-level)
+
+Umbrella Chart is intended for the following Use Cases:
+
+| Actor             | Use case                                                                                             |
+|-------------------|------------------------------------------------------------------------------------------------------|
+| Product Developer | Sandbox Environments: Create local environments to evaluate and experiment with Catena-X components. |
+| Product Developer | Development: Provide a unified setup for contributors and developers working on Tractus-X projects.  |
+| Product Tester    | Testing: Run end-to-end tests for Catena-X services.                                                 |
+
+## 3.4 System
+
+### 3.4.1 Context Delimitation
+
+````mermaid
+flowchart
+    subgraph "Umbrella Chart"
+        ChartYaml["Chart.yaml"]
+        subgraph charts
+            Portal["Portal"]
+            CentralIdp["CentralIdp"]
+            DiscoveryFinder["Discovery Finder"]
+            SDFactory["SD-Factory"]
+            SSICredentialIssuer["SSI Credential Issuer"]
+            SemanticHub["Semantic Hub"]
+            BPDM["BPDM"]
+            DataConsumer["Data Consumer"]
+            DataProvider["Data Provider"]
+            BDRS["BDRS"]
+            SSIWalletStub["SSI Wallet Stub"]
+        end
+        subgraph "tx-data-provider"
+            EDC["EDC"]
+            DTR["DTR"]
+            SubmodelServer["Submodel Server"]
+        end
+    end
+
+    ChartYaml --> Portal
+    ChartYaml --> CentralIdp
+    ChartYaml --> DiscoveryFinder
+    ChartYaml --> SDFactory
+    ChartYaml --> SSICredentialIssuer
+    ChartYaml --> SemanticHub
+    ChartYaml --> BPDM
+    ChartYaml --> DataConsumer
+    ChartYaml --> DataProvider
+    ChartYaml --> BDRS
+    ChartYaml --> SSIWalletStub
+    DataConsumer --> EDC
+    DataProvider --> EDC
+    DataProvider --> DTR
+    DataProvider --> SubmodelServer
+````
+
+#### Existing Umbrella Chart Structure
+
+# 4 TO-BE Design
+
+## 4.1 People
+
+### 4.1.1 Target Group Analysis
+
+Overall data space roles: https://catena-x.net/en/1/catena-x-introduce-implement/how-to-operate-catena-x
+
+The relevant data space roles for us under requirement 7.1.1.1 are:
+
+- Data Consumer
+- Data Provider
+- Enablement Service Provider
+
+Scope: Umbrella HELM Charts
+
+- Enablement Services: These services are included under the umbrella of HELM charts, focusing on enabling
+  functionalities.
+- Out of Scope: Core services such as Portal or BPDM are not considered within this scope.
+
+Primary target groups:
+
+| No. | Target group                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | Data space roles                                                    | Target group differentiation                                                                                                                                                                                                                                                                            | Behaviour, Needs, Pains & Usage                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+|-----|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| 1   | Developers<ul><li>External Developers (not Tractus-X developers): Utilize the chart for demonstration or evaluation purposes.</li><li>Experienced software and product developers who are developing a business app for a CATENA-X data space. They need to develop the app against the interfaces of the data space and integrate them accordingly.</li><li>They emphasize efficient and cost-effective implementation:<ul><li>Cost Efficiency: They do not want to use expensive SaaS solutions.</li><li>Technical Independence: They lack the knowledge and capacity to deploy the enablement and core services of the data space themselves.</li><li>Focus on Development: They concentrate on application development without delving deeply into the deployment and operation of the underlying infrastructure.</li></ul></li><li>Out of Scope: Developers running tests in test runners are not considered within this scope.</li></ul> | Data Consumer <br/> Data Provider <br/> Enablement Service Provider |                                                                                                                                                                                                                                                                                                         | <ul><li>Needs / sources of information<ul><li><a href="https://eclipse-tractusx.github.io/Kits/">Kit documentation tractus-x</a> for interaction purposes</li><li><a href="https://catenax-ev.github.io/">Catena-X doucmentation</a> for standards and regulations</li><li><a href="https://github.com/eclipse-tractusx/tractus-x-umbrella">Umbrella documentation</a> for umbrella component information</li></ul></li><li>Challenges → Solution<ul><li>Decentralization e.g. Where are other systems? How to interact with them? → Solution: Umbrella charts and bundles for deployment</li><li>Complex setup → Solution: delivery of small capability bundles</li></ul></li></ul> |
+| 2   | <ul><li>Tester requiring a test system (Testmanagement e.V.)</li><li>Requirement: Testbed</li></ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | Data Consumer <br/> Data Provider <br/> Enablement Service Provider | <ul><li>Developer (1) tests their feature.</li><li>Tester (2) performs end-to-end testing.</li><li>For the tester, the modular structure is less relevant since they focus on E2E testing, whereas the developer selects the required components.</li><li>The testbed must be easy to deploy.</li></ul> | <ul><li>Same as above from an End-to-end testing perspective</li><li>Typically a tester has less technical know-how than a developer and therefore needs a "one-size-fits-all" chart for easier testing</li></ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+
+## 4.2 Process
+
+### 4.2.1 Use Case View (high-level)
+
+| Use Case                                | Description                                                                                                       | Actors            |
+|-----------------------------------------|-------------------------------------------------------------------------------------------------------------------|-------------------|
+| Configure HELM Chart                    | The product developer configures the HELM Chart for the specific environment.                                     | Product Developer |
+| Configure Secrets                       | The product developer manages and configures secrets.                                                             | Product Developer |
+| Execute Deployment Pipeline             | The product developer successfully executes the deployment pipeline for the HELM Chart.                           | Product Developer |
+| Integrate EDC, DTR, and Identity Wallet | The actors integrate the components EDC, Digital Twin Registry, and Identity Wallet for seamless interoperability | Product Developer |
+| Set Up Connection Infrastructure        | The actor sets up the connection infrastructure for linking to the central data space infrastructure.             | Product Developer |
+| Maintain Infrastructure Module          | The product developer maintains the modular architecture of the HELM Chart.                                       | Product Developer |
+| Ensure Scalability                      | The product developer ensures scalability to support growing numbers of users and data volumes.                   | Product Developer |
+| Sandbox Environments                    | The product developer creates local environments to evaluate and experiment with Catena-X components.             | Product Developer |
+| E2E Testing                             | The product tester runs end-to-end tests for Catena-X services.                                                   | Product Tester    |
+
+### 4.2.2 Business Process (SCC Artifact)
+
+#### Chart Release Process
+
+Charts will be released using the already existing workflow in the Umbrella Chart repository. The workflow will
+automatically release a Chart, once it is pushed to the "charts/" directory with a new Chart version.
+
+#### Capability Bundle Structure
+
+Capability bundle modularization for the Tractus-X Umbrella Helm chart is a sound architectural and operational design.
+It aligns with both the domain-driven architecture of Catena-X (data exchange, digital twin, identity, semantics are
+distinct domains) and with Kubernetes best practices for managing complex applications (using an umbrella chart to
+bundle related microservices).
+
+Each bundle is self-sufficient, which improves isolation (failures or changes in one domain have minimal impact on
+others) and allows scaling and upgrading along domain lines. It simplifies deployment by allowing “plug-and-play”
+capabilities: an Enablement Service Provider can decide which bundles to operate based on its role e.g., include the
+Digital Twin and Semantic bundles if offering an asset-rich service, or omit them if not. The approach is consistent
+with how other OSS projects deliver multi-component systems, providing one-step installation without sacrificing the
+ability to tweak individual parts.
+
+Why this structure was proposed:
+
+1. **Clear Separation of Concerns**  
+   Each capability bundle (e.g. EDC Data Transfer, Digital Twin, Identity & Trust, Semantic Model) aligns with a
+   specific functional domain. This separation makes it easier to understand the role of each service (e.g., the EDC
+   connector vs. the digital twin registry), reduces coupling between unrelated components, and ultimately makes
+   maintenance and troubleshooting more straightforward.
+2. **Modular Deployment**  
+   Some participants in Catena-X may not need all services (e.g., some might not use the Digital Twin bundle). By
+   structuring the umbrella chart into bundles, a user can enable just those needed capabilities. This leads to leaner
+   installs and avoids unnecessary resource usage.
+3. **Best Practices with Helm**  
+   Using an umbrella chart with subcharts/bundles is a well-recognized Helm best practice for complex applications. It
+   allows a single helm install to set up multiple microservices while still allowing each service to have its own
+   lifecycle, configuration, and version.
+4. **Alignment with Domain-Driven Approach**  
+   Catena-X is organized around distinct, loosely-coupled “building blocks.” Bundling services by domain matches this
+   architectural vision. It’s clear which domain each set of microservices belongs to (EDC for data exchange, identity
+   for credential management, etc.). This clarity also helps new adopters navigate the ecosystem.
+
+````mermaid
+flowchart LR
+    subgraph "Core Services"
+        Vault["Vault"]
+    end
+
+    subgraph "Capability Bundle: Identity & Trust"
+        SSIWalletStub["SSI Wallet Stub"]
+    end
+
+    subgraph "Capability Bundle: Dataspace Connector"
+        EDC["EDC"]
+        EDCDB["EDC DB"]
+    end
+
+    subgraph "Capability Bundle: Digital Twin"
+        DTR["DTR"]
+        DTRDB["DTR DB"]
+    end
+
+    subgraph "Capability Bundle: Data Persitence Layer"
+        SimpleSubmodelServer["Simple Submodel Server"]
+    end
+
+    subgraph "Hausanschluss Bundles"
+        subgraph "Data Provider"
+            DataProvider["Data Provider"]
+        end
+        subgraph "Data Consumer"
+            DataConsumer["Data Consumer"]
+        end
+        subgraph "Enablement Provider"
+            EnablementProvider["Enablement Provider"]
+        end
+    end
+
+    EDC -.-> SSIWalletStub
+    EDC -.-> Vault
+    DataProvider --> EDC
+    DataProvider --> DTR
+    DataProvider --> SimpleSubmodelServer
+    DataConsumer --> EDC
+    EnablementProvider --> DataConsumer
+    EnablementProvider --> DataProvider
+
+````
+
+#### Deployment strategies
+
+##### Role: Data Provider
+
+The standard data provider role consists of a EDC, DTR and Submodel Server Bundles. EDC uses the Identity Wallet Bundle.
+
+````mermaid
+flowchart BT
+    A["Capability Bundle: Identity & Trust"]
+    B["Capability Bundle: Data Persistence Layer"]
+    C["Capability Bundle: Dataspace Connector"]
+    D["Capability Bundle: Digital Twin"]
+    E["Application to be tested/developed"]
+    E --> B
+    E --> C
+    E --> D
+    C --> A
+````
+
+##### Role: Data Consumer
+
+The standard data consumer role consists of only the EDC Bundle and the Identity Wallet Bundle.
+
+````mermaid
+flowchart BT
+    A["Capability Bundle: Identity & Trust"]
+    B["Capability Bundle: Dataspace Connector"]
+    C["Application to be tested/developed"]
+    C --> B
+    B --> A
+
+````
+
+##### Role: Enablement Provider
+
+The Enablement Provider roles consists of both the Data Consumer and Data Provider bundles. This allows provisioning of
+data and the consumtion of the provisioned data by a application.
+
+````mermaid
+flowchart BT
+    A["Capability Bundle: Identity & Trust"]
path: docs/concept/TAP7.1-solution-design.md
user: login: ds-jhartmann
body: added the actors
created_at: 2025-03-31T12:21:03Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,516 @@
+# Solution Design "Hausanschluss" Bundle Concept
+
+# 1 Business Case
+
+## 1.1 Executive Summary
+
+The "Hausanschluss" Bundle aims to simplify the installation of the enablement services Eclipse Dataspace
+Connector (EDC), Digital Twin Registry (DTR), and their supporting components. By developing a flexible, parameterizable
+installation package, the project seeks to reduce deployment complexity and lower barriers to participation in the
+Catena‑X data space. This bundle will enable independent component updates and support a modular "bring your own"
+approach, ultimately fostering a more efficient and accessible ecosystem for diverse participants—such as testers,
+external product developers, product testers, and small and medium-sized enterprises.
+
+## 1.2 Business Need
+
+Current deployment methods for data space integration are complex and require significant manual effort. This PoC
+addresses the need to:
+
+- **Reduce Complexity:** Simplify the deployment topology by bundling components into capabilities.
+- **Automate Deployment:** Provide an automated installation package using Kubernetes and HELM.
+- **Minimize Configuration Overhead:** Streamline the integration process by providing pre-configured bundles that require only minimal manual parameter adjustments.
+- **Extend Documentation:** Provide a detailed documentation tailored to the target groups.
+- **Enable Extension:** Design the system to allow the seamless addition of new components or capabilities.
+
+## 1.3 Objectives
+
+- **Simplify Deployment and Maintenance:** Develop an installation package that minimizes manual configuration through
+  automation.
+- **Ensure Modularity:** Structure the bundle so that components can be independently installed, updated, or replaced
+  without affecting other services.
+- **Facilitate Flexibility:** Implement a "bring your own" model for key components, such as EDC, PostgreSQL, and HashiCorp
+  Vault, to allow tailored deployments that meet specific needs.
+- **Increase Accessibility**: Lower entry barriers for new participants by reducing technical complexity and operational
+  dependencies.
+- **Scalability:** Structure the bundles so that they can be deployed multiple times.
+
+## 1.4 Expected Deliverables
+
+- **PoC Documentation:** A concept and architecture overview highlighting the modular design.
+- **Modular Installation Package:** A set of HELM charts for deploying the enablement service bundles:
+    - **Dataspace Connector:** Including the Eclipse Dataspace Connector, EDC PostgreSQL, and HashiCorp Vault.
+    - **Digital Twin Bundle:** Featuring components such as the Decentral DT Registry (with “bring your own” PostgreSQL)
+    - **Data Persitence Layer Bundle:** Including a simple Submodel Server to store semantic data.
+    - **Identity Wallet Bundle:** Covering the Identity Wallet functionality.
+- **Demonstration Environment:** A test deployment showcasing reduced complexity and improved efficiency.
+- **Basic User Guide:** Instructions on how to deploy and update the PoC bundle.
+
+## 1.5 Benefits
+
+- **Operational Efficiency:** Faster and more reliable deployments with less manual work.
+- **Scalability:** A modular design that can be scaled or adapted for future full-scale deployments.
+- **Ease of Adoption:** Simplified deployment processes make it easier for testers and external developers to engage.
+
+## 1.6. Dependencies
+
+- **Interoperability** with the CATENA‑X standards.
+
+## 1.7. Success Criteria
+
+- **Technology Readiness Level:** Achievement of a Technology Readiness Level (TRL) of 3, as specified in the requirements.
+- **Functional PoC Deployment:** Demonstrated automated, modular installation with reduced manual steps.
+- **Simplified Configuration:** Clear evidence of reduced configuration complexity.
+- **Positive Feedback:** End-user validation from a select group of demo participants and the Tractus-X community.
+- **Documentation Completeness:** Availability of concise deployment and user guides.
+
+## 1.8. Out of Scope
+
+- **Full Production Readiness:** This PoC is not intended to be a production-ready solution.
+- **Core Services Exclusion:** Core services are not part of the Hausanschluss Bundles.
+- **App Provider Role:** The role of App Provider is considered out of scope for this deployment.
+- **Alternative Deployment Techniques:** While the evaluation of alternative deployment methods is acknowledged, the primary
+  focus remains on Kubernetes and HELM-based deployment.
+
+# 2 Requirements Analysis
+
+## 2.1 Assumptions
+
+## 2.2 Requirements Catalog
+
+| ID             | Requirement                                                                                                                                                                                                                                                                                                                                          | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | Deliverables / Acceptance Criteria                                                                                                                                                                                                                                                                                                                                                                                   |
+|----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| [WP-7.1.-D001] | The Hausanschluss Bundle aims to simplify the installation and maintenance of the EDC and other components that together ensure a “Hausanschluss”. A flexible, parameterizable installation package is intended to reduce complexity and make integration more efficient, thereby simplifying participation in Catena‑X for additional participants. | Specification and development of a flexible, parameterizable installation package that reduces the complexity of installing and maintaining the required components for seamless integration into the Catena‑X data space. This package should facilitate updates and new versions, making participation in Catena‑X more efficient and accessible. In doing so, SMEs shall be enabled to participate without high costs or dependency on SaaS providers while maintaining control over their IT infrastructure. | [WP-7.1.-D001] Concept for the Hausanschluss is created                                                                                                                                                                                                                                                                                                                                                              |
+| 7.1.1.1        | The solution concept must define the Capability Bundles structures to be implemented. For each Capability Bundle, the included bundles and their versions are mapped.                                                                                                                                                                                | "The following Capability Bundle structure is implemented:                                                                                                                                                                                                                                                                                                                                                                                                                                                       | The structure of the Capability Bundles for the Enablement Services has been specified. For version R24.12 it is clearly defined which Tractus‑X services and components are assigned to each Capability Bundle                                                                                                                                                                                                      |
path: docs/concept/TAP7.1-solution-design.md
user: login: CDiezRodriguez
body: ```suggestion
| 7.1.1.1        | The solution concept must define the Capability Bundles structures to be implemented. For each Capability Bundle, the included bundles and their versions are mapped.                                                                                                                                                                                | The following Capability Bundle structure is implemented:                                                                                                                                                                                                                                                                                                                                                                                                                                                       | The structure of the Capability Bundles for the Enablement Services has been specified. For version R24.12 it is clearly defined which Tractus‑X services and components are assigned to each Capability Bundle                                                                                                                                                                                                      |
```
created_at: 2025-04-03T09:41:07Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,516 @@
+# Solution Design "Hausanschluss" Bundle Concept
+
+# 1 Business Case
+
+## 1.1 Executive Summary
+
+The "Hausanschluss" Bundle aims to simplify the installation of the enablement services Eclipse Dataspace
+Connector (EDC), Digital Twin Registry (DTR), and their supporting components. By developing a flexible, parameterizable
+installation package, the project seeks to reduce deployment complexity and lower barriers to participation in the
+Catena‑X data space. This bundle will enable independent component updates and support a modular "bring your own"
+approach, ultimately fostering a more efficient and accessible ecosystem for diverse participants—such as testers,
+external product developers, product testers, and small and medium-sized enterprises.
+
+## 1.2 Business Need
+
+Current deployment methods for data space integration are complex and require significant manual effort. This PoC
+addresses the need to:
+
+- **Reduce Complexity:** Simplify the deployment topology by bundling components into capabilities.
+- **Automate Deployment:** Provide an automated installation package using Kubernetes and HELM.
+- **Minimize Configuration Overhead:** Streamline the integration process by providing pre-configured bundles that require only minimal manual parameter adjustments.
+- **Extend Documentation:** Provide a detailed documentation tailored to the target groups.
+- **Enable Extension:** Design the system to allow the seamless addition of new components or capabilities.
+
+## 1.3 Objectives
+
+- **Simplify Deployment and Maintenance:** Develop an installation package that minimizes manual configuration through
+  automation.
+- **Ensure Modularity:** Structure the bundle so that components can be independently installed, updated, or replaced
+  without affecting other services.
+- **Facilitate Flexibility:** Implement a "bring your own" model for key components, such as EDC, PostgreSQL, and HashiCorp
+  Vault, to allow tailored deployments that meet specific needs.
+- **Increase Accessibility**: Lower entry barriers for new participants by reducing technical complexity and operational
+  dependencies.
+- **Scalability:** Structure the bundles so that they can be deployed multiple times.
+
+## 1.4 Expected Deliverables
+
+- **PoC Documentation:** A concept and architecture overview highlighting the modular design.
+- **Modular Installation Package:** A set of HELM charts for deploying the enablement service bundles:
+    - **Dataspace Connector:** Including the Eclipse Dataspace Connector, EDC PostgreSQL, and HashiCorp Vault.
+    - **Digital Twin Bundle:** Featuring components such as the Decentral DT Registry (with “bring your own” PostgreSQL)
+    - **Data Persitence Layer Bundle:** Including a simple Submodel Server to store semantic data.
+    - **Identity Wallet Bundle:** Covering the Identity Wallet functionality.
+- **Demonstration Environment:** A test deployment showcasing reduced complexity and improved efficiency.
+- **Basic User Guide:** Instructions on how to deploy and update the PoC bundle.
+
+## 1.5 Benefits
+
+- **Operational Efficiency:** Faster and more reliable deployments with less manual work.
+- **Scalability:** A modular design that can be scaled or adapted for future full-scale deployments.
+- **Ease of Adoption:** Simplified deployment processes make it easier for testers and external developers to engage.
+
+## 1.6. Dependencies
+
+- **Interoperability** with the CATENA‑X standards.
+
+## 1.7. Success Criteria
+
+- **Technology Readiness Level:** Achievement of a Technology Readiness Level (TRL) of 3, as specified in the requirements.
+- **Functional PoC Deployment:** Demonstrated automated, modular installation with reduced manual steps.
+- **Simplified Configuration:** Clear evidence of reduced configuration complexity.
+- **Positive Feedback:** End-user validation from a select group of demo participants and the Tractus-X community.
+- **Documentation Completeness:** Availability of concise deployment and user guides.
+
+## 1.8. Out of Scope
+
+- **Full Production Readiness:** This PoC is not intended to be a production-ready solution.
+- **Core Services Exclusion:** Core services are not part of the Hausanschluss Bundles.
+- **App Provider Role:** The role of App Provider is considered out of scope for this deployment.
+- **Alternative Deployment Techniques:** While the evaluation of alternative deployment methods is acknowledged, the primary
+  focus remains on Kubernetes and HELM-based deployment.
+
+# 2 Requirements Analysis
+
+## 2.1 Assumptions
+
+## 2.2 Requirements Catalog
+
+| ID             | Requirement                                                                                                                                                                                                                                                                                                                                          | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | Deliverables / Acceptance Criteria                                                                                                                                                                                                                                                                                                                                                                                   |
+|----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| [WP-7.1.-D001] | The Hausanschluss Bundle aims to simplify the installation and maintenance of the EDC and other components that together ensure a “Hausanschluss”. A flexible, parameterizable installation package is intended to reduce complexity and make integration more efficient, thereby simplifying participation in Catena‑X for additional participants. | Specification and development of a flexible, parameterizable installation package that reduces the complexity of installing and maintaining the required components for seamless integration into the Catena‑X data space. This package should facilitate updates and new versions, making participation in Catena‑X more efficient and accessible. In doing so, SMEs shall be enabled to participate without high costs or dependency on SaaS providers while maintaining control over their IT infrastructure. | [WP-7.1.-D001] Concept for the Hausanschluss is created                                                                                                                                                                                                                                                                                                                                                              |
+| 7.1.1.1        | The solution concept must define the Capability Bundles structures to be implemented. For each Capability Bundle, the included bundles and their versions are mapped.                                                                                                                                                                                | "The following Capability Bundle structure is implemented:                                                                                                                                                                                                                                                                                                                                                                                                                                                       | The structure of the Capability Bundles for the Enablement Services has been specified. For version R24.12 it is clearly defined which Tractus‑X services and components are assigned to each Capability Bundle                                                                                                                                                                                                      |
+| 7.1.1.2        | Definition of Data Space Roles                                                                                                                                                                                                                                                                                                                       | Data Consumer, Data Provider, Enablement Service Provider                                                                                                                                                                                                                                                                                                                                                                                                                                                        | As part of the target group analysis, the target groups are defined and aligned with the data space roles. <br>Mapping from data space role to target group has been completed. <br>Mapping from target group to data space role has been completed. <br>An assignment of data space roles to Capability Bundles has been made.                                                                                      |
+| 7.1.1.4        | Modularity & Maintainability: No dependencies between Capability Bundles                                                                                                                                                                                                                                                                             | Unique assignment of components and services to a defined Capability Bundle. <br>Each component and service should be assigned to only one Capability Bundle. <br>Dependencies between Capability Bundles are allowed.                                                                                                                                                                                                                                                                                           | Components and Services should only be part of one bundle. <br>Each bundle must be deployable in isolation and can be installed, updated, or removed independently. <br>Capability Bundles must be organized in separate HELM sub‑charts. <br>Circular dependencies between bundles must be avoided.                                                                                                                 |
+| 7.1.1.5        | Modularity & Maintainability: Concept for reducing deployment complexity                                                                                                                                                                                                                                                                             | The system deployment should be optimized to reduce the existing complexity. The goal is to make the provisioning process more efficient, robust, and easier to maintain.                                                                                                                                                                                                                                                                                                                                        | **Simplification of deployment processes:** A reduction of manual configuration steps has been achieved. <br>**Transparency and traceability:** Clearly documented deployment steps are provided. <br>**Improvements of Chart configuration by:** <br>usage of template  <br>reducing configuration options <br>reducing manual steps in the setup                                                                   |
+| 7.1.1.6        | Modularity & Maintainability                                                                                                                                                                                                                                                                                                                         | Charts are published automatically.                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | Charts are published via a publicly accessible charts repository.                                                                                                                                                                                                                                                                                                                                                    |
+| 7.1.1.13       | Solution Concept                                                                                                                                                                                                                                                                                                                                     | Creation of a solution design for the “Hausanschluss” Bundle.                                                                                                                                                                                                                                                                                                                                                                                                                                                    | The solution design for the "Hausanschluss" Bundle is created. <br>The solution design for the "Hausanschluss" Bundle ispublished in the repository: https://github.com/eclipse-tractusx/tractus-x-umbrella.                                                                                                                                                                                                         |
path: docs/concept/TAP7.1-solution-design.md
user: login: CDiezRodriguez
body: ```suggestion
| 7.1.1.13       | Solution Concept                                                                                                                                                                                                                                                                                                                                     | Creation of a solution design for the “Hausanschluss” Bundle.                                                                                                                                                                                                                                                                                                                                                                                                                                                    | The solution design for the "Hausanschluss" Bundle is created. <br>The solution design for the "Hausanschluss" Bundle is published in the repository: https://github.com/eclipse-tractusx/tractus-x-umbrella.                                                                                                                                                                                                         |
```
created_at: 2025-04-03T09:46:09Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,516 @@
+# Solution Design "Hausanschluss" Bundle Concept
+
+# 1 Business Case
+
+## 1.1 Executive Summary
+
+The "Hausanschluss" Bundle aims to simplify the installation of the enablement services Eclipse Dataspace
+Connector (EDC), Digital Twin Registry (DTR), and their supporting components. By developing a flexible, parameterizable
+installation package, the project seeks to reduce deployment complexity and lower barriers to participation in the
+Catena‑X data space. This bundle will enable independent component updates and support a modular "bring your own"
+approach, ultimately fostering a more efficient and accessible ecosystem for diverse participants—such as testers,
+external product developers, product testers, and small and medium-sized enterprises.
+
+## 1.2 Business Need
+
+Current deployment methods for data space integration are complex and require significant manual effort. This PoC
+addresses the need to:
+
+- **Reduce Complexity:** Simplify the deployment topology by bundling components into capabilities.
+- **Automate Deployment:** Provide an automated installation package using Kubernetes and HELM.
+- **Minimize Configuration Overhead:** Streamline the integration process by providing pre-configured bundles that require only minimal manual parameter adjustments.
+- **Extend Documentation:** Provide a detailed documentation tailored to the target groups.
+- **Enable Extension:** Design the system to allow the seamless addition of new components or capabilities.
+
+## 1.3 Objectives
+
+- **Simplify Deployment and Maintenance:** Develop an installation package that minimizes manual configuration through
+  automation.
+- **Ensure Modularity:** Structure the bundle so that components can be independently installed, updated, or replaced
+  without affecting other services.
+- **Facilitate Flexibility:** Implement a "bring your own" model for key components, such as EDC, PostgreSQL, and HashiCorp
+  Vault, to allow tailored deployments that meet specific needs.
+- **Increase Accessibility**: Lower entry barriers for new participants by reducing technical complexity and operational
+  dependencies.
+- **Scalability:** Structure the bundles so that they can be deployed multiple times.
+
+## 1.4 Expected Deliverables
+
+- **PoC Documentation:** A concept and architecture overview highlighting the modular design.
+- **Modular Installation Package:** A set of HELM charts for deploying the enablement service bundles:
+    - **Dataspace Connector:** Including the Eclipse Dataspace Connector, EDC PostgreSQL, and HashiCorp Vault.
+    - **Digital Twin Bundle:** Featuring components such as the Decentral DT Registry (with “bring your own” PostgreSQL)
+    - **Data Persitence Layer Bundle:** Including a simple Submodel Server to store semantic data.
+    - **Identity Wallet Bundle:** Covering the Identity Wallet functionality.
+- **Demonstration Environment:** A test deployment showcasing reduced complexity and improved efficiency.
+- **Basic User Guide:** Instructions on how to deploy and update the PoC bundle.
+
+## 1.5 Benefits
+
+- **Operational Efficiency:** Faster and more reliable deployments with less manual work.
+- **Scalability:** A modular design that can be scaled or adapted for future full-scale deployments.
+- **Ease of Adoption:** Simplified deployment processes make it easier for testers and external developers to engage.
+
+## 1.6. Dependencies
+
+- **Interoperability** with the CATENA‑X standards.
+
+## 1.7. Success Criteria
+
+- **Technology Readiness Level:** Achievement of a Technology Readiness Level (TRL) of 3, as specified in the requirements.
+- **Functional PoC Deployment:** Demonstrated automated, modular installation with reduced manual steps.
+- **Simplified Configuration:** Clear evidence of reduced configuration complexity.
+- **Positive Feedback:** End-user validation from a select group of demo participants and the Tractus-X community.
+- **Documentation Completeness:** Availability of concise deployment and user guides.
+
+## 1.8. Out of Scope
+
+- **Full Production Readiness:** This PoC is not intended to be a production-ready solution.
+- **Core Services Exclusion:** Core services are not part of the Hausanschluss Bundles.
+- **App Provider Role:** The role of App Provider is considered out of scope for this deployment.
+- **Alternative Deployment Techniques:** While the evaluation of alternative deployment methods is acknowledged, the primary
+  focus remains on Kubernetes and HELM-based deployment.
+
+# 2 Requirements Analysis
+
+## 2.1 Assumptions
+
+## 2.2 Requirements Catalog
+
+| ID             | Requirement                                                                                                                                                                                                                                                                                                                                          | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | Deliverables / Acceptance Criteria                                                                                                                                                                                                                                                                                                                                                                                   |
+|----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| [WP-7.1.-D001] | The Hausanschluss Bundle aims to simplify the installation and maintenance of the EDC and other components that together ensure a “Hausanschluss”. A flexible, parameterizable installation package is intended to reduce complexity and make integration more efficient, thereby simplifying participation in Catena‑X for additional participants. | Specification and development of a flexible, parameterizable installation package that reduces the complexity of installing and maintaining the required components for seamless integration into the Catena‑X data space. This package should facilitate updates and new versions, making participation in Catena‑X more efficient and accessible. In doing so, SMEs shall be enabled to participate without high costs or dependency on SaaS providers while maintaining control over their IT infrastructure. | [WP-7.1.-D001] Concept for the Hausanschluss is created                                                                                                                                                                                                                                                                                                                                                              |
+| 7.1.1.1        | The solution concept must define the Capability Bundles structures to be implemented. For each Capability Bundle, the included bundles and their versions are mapped.                                                                                                                                                                                | "The following Capability Bundle structure is implemented:                                                                                                                                                                                                                                                                                                                                                                                                                                                       | The structure of the Capability Bundles for the Enablement Services has been specified. For version R24.12 it is clearly defined which Tractus‑X services and components are assigned to each Capability Bundle                                                                                                                                                                                                      |
+| 7.1.1.2        | Definition of Data Space Roles                                                                                                                                                                                                                                                                                                                       | Data Consumer, Data Provider, Enablement Service Provider                                                                                                                                                                                                                                                                                                                                                                                                                                                        | As part of the target group analysis, the target groups are defined and aligned with the data space roles. <br>Mapping from data space role to target group has been completed. <br>Mapping from target group to data space role has been completed. <br>An assignment of data space roles to Capability Bundles has been made.                                                                                      |
+| 7.1.1.4        | Modularity & Maintainability: No dependencies between Capability Bundles                                                                                                                                                                                                                                                                             | Unique assignment of components and services to a defined Capability Bundle. <br>Each component and service should be assigned to only one Capability Bundle. <br>Dependencies between Capability Bundles are allowed.                                                                                                                                                                                                                                                                                           | Components and Services should only be part of one bundle. <br>Each bundle must be deployable in isolation and can be installed, updated, or removed independently. <br>Capability Bundles must be organized in separate HELM sub‑charts. <br>Circular dependencies between bundles must be avoided.                                                                                                                 |
+| 7.1.1.5        | Modularity & Maintainability: Concept for reducing deployment complexity                                                                                                                                                                                                                                                                             | The system deployment should be optimized to reduce the existing complexity. The goal is to make the provisioning process more efficient, robust, and easier to maintain.                                                                                                                                                                                                                                                                                                                                        | **Simplification of deployment processes:** A reduction of manual configuration steps has been achieved. <br>**Transparency and traceability:** Clearly documented deployment steps are provided. <br>**Improvements of Chart configuration by:** <br>usage of template  <br>reducing configuration options <br>reducing manual steps in the setup                                                                   |
+| 7.1.1.6        | Modularity & Maintainability                                                                                                                                                                                                                                                                                                                         | Charts are published automatically.                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | Charts are published via a publicly accessible charts repository.                                                                                                                                                                                                                                                                                                                                                    |
+| 7.1.1.13       | Solution Concept                                                                                                                                                                                                                                                                                                                                     | Creation of a solution design for the “Hausanschluss” Bundle.                                                                                                                                                                                                                                                                                                                                                                                                                                                    | The solution design for the "Hausanschluss" Bundle is created. <br>The solution design for the "Hausanschluss" Bundle ispublished in the repository: https://github.com/eclipse-tractusx/tractus-x-umbrella.                                                                                                                                                                                                         |
+| 7.1.1.14       | Scalability of Enablement Services                                                                                                                                                                                                                                                                                                                   | Scalability of Enablement Services                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | Developers should be able to deploy an arbitrary number of Enablement Services. <br>Example: Up to 3 EDCs can be provided.                                                                                                                                                                                                                                                                                           |
+| 7.1.1.16       | Interoperability                                                                                                                                                                                                                                                                                                                                     | Interoperability                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | Interoperability with the CATENA‑X standards. <br>This interoperability is documented and traceable.                                                                                                                                                                                                                                                                                                                 |
+| [WP-7.1.-D002] | [WP-7.1.-D002] Target group for the specification is defined.                                                                                                                                                                                                                                                                                        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | [WP-7.1.-D002] Target group for the specification is defined.                                                                                                                                                                                                                                                                                                                                                        |
+| 7.1.2.1        | Target Group Analysis                                                                                                                                                                                                                                                                                                                                | The target group analysis for the "Hausanschluss Bundle"is defined.                                                                                                                                                                                                                                                                                                                                                                                                                                              | The analysis has been conducted. <br>The target group is included in the solution concept <br>To be clarified: What is included in the Hausanschluss and who can operate it in which scenario (OEM, SME, service provider, etc.).                                                                                                                                                                                    |
+| [WP-7.1.-D003] | [WP-7.1.-D003] Decentralized components and services defined                                                                                                                                                                                                                                                                                         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | [WP-7.1.-D003] Decentralized components and services have been defined.                                                                                                                                                                                                                                                                                                                                              |
+| 7.1.3.1        | See [WP-7.1.-D001-AC001]                                                                                                                                                                                                                                                                                                                             |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | See [WP-7.1.-D001-AC001]                                                                                                                                                                                                                                                                                                                                                                                             |
+| [WP-7.1.-D004] | [WP-7.1.-D004] Documentation of the Hausanschluss Bundle is completed                                                                                                                                                                                                                                                                                |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | [WP-7.1.-D004] Documentation of the Hausanschluss Bundle is completed                                                                                                                                                                                                                                                                                                                                                |
+| 7.1.4.1        | Documentation of the Hausanschluss-Bundles                                                                                                                                                                                                                                                                                                           | Usability                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | Documentation is provided that enables an experienced product developer - with knowledge of Helm Charts, Docker, and Vaults - to deploy the chart independently without external help. <br>A troubleshooting and FAQ section is included to support the developer. <br>Prerequisites, skills, and technology requirements are outlined, detailing what a developer must know to perform the deployment autonomously. |
+| 7.1.4.2        | Documentation of the Hausanschluss-Bundles                                                                                                                                                                                                                                                                                                           | Documentation of the Hausanschluss-Bundles is completed.                                                                                                                                                                                                                                                                                                                                                                                                                                                         | Documentation is provided for: <br>Configuration of the defined bundles according to the specified requirements and parameters <br>Integration of the documentation into the Umbrella HELM Charts <br>Integration into the Umbrella HELM Chart to ensure consistent deployment                                                                                                                                       |
path: docs/concept/TAP7.1-solution-design.md
user: login: CDiezRodriguez
body: ```suggestion
| 7.1.4.2        | Documentation of the Hausanschluss-Bundles                                                                                                                                                                                                                                                                                                           | Documentation of the Hausanschluss-Bundles is completed.                                                                                                                                                                                                                                                                                                                                                                                                                                                         | Documentation is provided for: <br>Configuration of the defined bundles according to the specified requirements and parameters. <br>Integration of the documentation into the Umbrella HELM Charts. <br>Integration into the Umbrella HELM Chart to ensure consistent deployment.                                                                                                                                       |
```
created_at: 2025-04-03T09:55:00Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,516 @@
+# Solution Design "Hausanschluss" Bundle Concept
+
+# 1 Business Case
+
+## 1.1 Executive Summary
+
+The "Hausanschluss" Bundle aims to simplify the installation of the enablement services Eclipse Dataspace
+Connector (EDC), Digital Twin Registry (DTR), and their supporting components. By developing a flexible, parameterizable
+installation package, the project seeks to reduce deployment complexity and lower barriers to participation in the
+Catena‑X data space. This bundle will enable independent component updates and support a modular "bring your own"
+approach, ultimately fostering a more efficient and accessible ecosystem for diverse participants—such as testers,
+external product developers, product testers, and small and medium-sized enterprises.
+
+## 1.2 Business Need
+
+Current deployment methods for data space integration are complex and require significant manual effort. This PoC
+addresses the need to:
+
+- **Reduce Complexity:** Simplify the deployment topology by bundling components into capabilities.
+- **Automate Deployment:** Provide an automated installation package using Kubernetes and HELM.
+- **Minimize Configuration Overhead:** Streamline the integration process by providing pre-configured bundles that require only minimal manual parameter adjustments.
+- **Extend Documentation:** Provide a detailed documentation tailored to the target groups.
+- **Enable Extension:** Design the system to allow the seamless addition of new components or capabilities.
+
+## 1.3 Objectives
+
+- **Simplify Deployment and Maintenance:** Develop an installation package that minimizes manual configuration through
+  automation.
+- **Ensure Modularity:** Structure the bundle so that components can be independently installed, updated, or replaced
+  without affecting other services.
+- **Facilitate Flexibility:** Implement a "bring your own" model for key components, such as EDC, PostgreSQL, and HashiCorp
+  Vault, to allow tailored deployments that meet specific needs.
+- **Increase Accessibility**: Lower entry barriers for new participants by reducing technical complexity and operational
+  dependencies.
+- **Scalability:** Structure the bundles so that they can be deployed multiple times.
+
+## 1.4 Expected Deliverables
+
+- **PoC Documentation:** A concept and architecture overview highlighting the modular design.
+- **Modular Installation Package:** A set of HELM charts for deploying the enablement service bundles:
+    - **Dataspace Connector:** Including the Eclipse Dataspace Connector, EDC PostgreSQL, and HashiCorp Vault.
+    - **Digital Twin Bundle:** Featuring components such as the Decentral DT Registry (with “bring your own” PostgreSQL)
+    - **Data Persitence Layer Bundle:** Including a simple Submodel Server to store semantic data.
+    - **Identity Wallet Bundle:** Covering the Identity Wallet functionality.
+- **Demonstration Environment:** A test deployment showcasing reduced complexity and improved efficiency.
+- **Basic User Guide:** Instructions on how to deploy and update the PoC bundle.
+
+## 1.5 Benefits
+
+- **Operational Efficiency:** Faster and more reliable deployments with less manual work.
+- **Scalability:** A modular design that can be scaled or adapted for future full-scale deployments.
+- **Ease of Adoption:** Simplified deployment processes make it easier for testers and external developers to engage.
+
+## 1.6. Dependencies
+
+- **Interoperability** with the CATENA‑X standards.
+
+## 1.7. Success Criteria
+
+- **Technology Readiness Level:** Achievement of a Technology Readiness Level (TRL) of 3, as specified in the requirements.
+- **Functional PoC Deployment:** Demonstrated automated, modular installation with reduced manual steps.
+- **Simplified Configuration:** Clear evidence of reduced configuration complexity.
+- **Positive Feedback:** End-user validation from a select group of demo participants and the Tractus-X community.
+- **Documentation Completeness:** Availability of concise deployment and user guides.
+
+## 1.8. Out of Scope
+
+- **Full Production Readiness:** This PoC is not intended to be a production-ready solution.
+- **Core Services Exclusion:** Core services are not part of the Hausanschluss Bundles.
+- **App Provider Role:** The role of App Provider is considered out of scope for this deployment.
+- **Alternative Deployment Techniques:** While the evaluation of alternative deployment methods is acknowledged, the primary
+  focus remains on Kubernetes and HELM-based deployment.
+
+# 2 Requirements Analysis
+
+## 2.1 Assumptions
+
+## 2.2 Requirements Catalog
+
+| ID             | Requirement                                                                                                                                                                                                                                                                                                                                          | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | Deliverables / Acceptance Criteria                                                                                                                                                                                                                                                                                                                                                                                   |
+|----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| [WP-7.1.-D001] | The Hausanschluss Bundle aims to simplify the installation and maintenance of the EDC and other components that together ensure a “Hausanschluss”. A flexible, parameterizable installation package is intended to reduce complexity and make integration more efficient, thereby simplifying participation in Catena‑X for additional participants. | Specification and development of a flexible, parameterizable installation package that reduces the complexity of installing and maintaining the required components for seamless integration into the Catena‑X data space. This package should facilitate updates and new versions, making participation in Catena‑X more efficient and accessible. In doing so, SMEs shall be enabled to participate without high costs or dependency on SaaS providers while maintaining control over their IT infrastructure. | [WP-7.1.-D001] Concept for the Hausanschluss is created                                                                                                                                                                                                                                                                                                                                                              |
+| 7.1.1.1        | The solution concept must define the Capability Bundles structures to be implemented. For each Capability Bundle, the included bundles and their versions are mapped.                                                                                                                                                                                | "The following Capability Bundle structure is implemented:                                                                                                                                                                                                                                                                                                                                                                                                                                                       | The structure of the Capability Bundles for the Enablement Services has been specified. For version R24.12 it is clearly defined which Tractus‑X services and components are assigned to each Capability Bundle                                                                                                                                                                                                      |
+| 7.1.1.2        | Definition of Data Space Roles                                                                                                                                                                                                                                                                                                                       | Data Consumer, Data Provider, Enablement Service Provider                                                                                                                                                                                                                                                                                                                                                                                                                                                        | As part of the target group analysis, the target groups are defined and aligned with the data space roles. <br>Mapping from data space role to target group has been completed. <br>Mapping from target group to data space role has been completed. <br>An assignment of data space roles to Capability Bundles has been made.                                                                                      |
+| 7.1.1.4        | Modularity & Maintainability: No dependencies between Capability Bundles                                                                                                                                                                                                                                                                             | Unique assignment of components and services to a defined Capability Bundle. <br>Each component and service should be assigned to only one Capability Bundle. <br>Dependencies between Capability Bundles are allowed.                                                                                                                                                                                                                                                                                           | Components and Services should only be part of one bundle. <br>Each bundle must be deployable in isolation and can be installed, updated, or removed independently. <br>Capability Bundles must be organized in separate HELM sub‑charts. <br>Circular dependencies between bundles must be avoided.                                                                                                                 |
+| 7.1.1.5        | Modularity & Maintainability: Concept for reducing deployment complexity                                                                                                                                                                                                                                                                             | The system deployment should be optimized to reduce the existing complexity. The goal is to make the provisioning process more efficient, robust, and easier to maintain.                                                                                                                                                                                                                                                                                                                                        | **Simplification of deployment processes:** A reduction of manual configuration steps has been achieved. <br>**Transparency and traceability:** Clearly documented deployment steps are provided. <br>**Improvements of Chart configuration by:** <br>usage of template  <br>reducing configuration options <br>reducing manual steps in the setup                                                                   |
+| 7.1.1.6        | Modularity & Maintainability                                                                                                                                                                                                                                                                                                                         | Charts are published automatically.                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | Charts are published via a publicly accessible charts repository.                                                                                                                                                                                                                                                                                                                                                    |
+| 7.1.1.13       | Solution Concept                                                                                                                                                                                                                                                                                                                                     | Creation of a solution design for the “Hausanschluss” Bundle.                                                                                                                                                                                                                                                                                                                                                                                                                                                    | The solution design for the "Hausanschluss" Bundle is created. <br>The solution design for the "Hausanschluss" Bundle ispublished in the repository: https://github.com/eclipse-tractusx/tractus-x-umbrella.                                                                                                                                                                                                         |
+| 7.1.1.14       | Scalability of Enablement Services                                                                                                                                                                                                                                                                                                                   | Scalability of Enablement Services                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | Developers should be able to deploy an arbitrary number of Enablement Services. <br>Example: Up to 3 EDCs can be provided.                                                                                                                                                                                                                                                                                           |
+| 7.1.1.16       | Interoperability                                                                                                                                                                                                                                                                                                                                     | Interoperability                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | Interoperability with the CATENA‑X standards. <br>This interoperability is documented and traceable.                                                                                                                                                                                                                                                                                                                 |
+| [WP-7.1.-D002] | [WP-7.1.-D002] Target group for the specification is defined.                                                                                                                                                                                                                                                                                        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | [WP-7.1.-D002] Target group for the specification is defined.                                                                                                                                                                                                                                                                                                                                                        |
+| 7.1.2.1        | Target Group Analysis                                                                                                                                                                                                                                                                                                                                | The target group analysis for the "Hausanschluss Bundle"is defined.                                                                                                                                                                                                                                                                                                                                                                                                                                              | The analysis has been conducted. <br>The target group is included in the solution concept <br>To be clarified: What is included in the Hausanschluss and who can operate it in which scenario (OEM, SME, service provider, etc.).                                                                                                                                                                                    |
+| [WP-7.1.-D003] | [WP-7.1.-D003] Decentralized components and services defined                                                                                                                                                                                                                                                                                         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | [WP-7.1.-D003] Decentralized components and services have been defined.                                                                                                                                                                                                                                                                                                                                              |
+| 7.1.3.1        | See [WP-7.1.-D001-AC001]                                                                                                                                                                                                                                                                                                                             |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | See [WP-7.1.-D001-AC001]                                                                                                                                                                                                                                                                                                                                                                                             |
+| [WP-7.1.-D004] | [WP-7.1.-D004] Documentation of the Hausanschluss Bundle is completed                                                                                                                                                                                                                                                                                |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | [WP-7.1.-D004] Documentation of the Hausanschluss Bundle is completed                                                                                                                                                                                                                                                                                                                                                |
+| 7.1.4.1        | Documentation of the Hausanschluss-Bundles                                                                                                                                                                                                                                                                                                           | Usability                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | Documentation is provided that enables an experienced product developer - with knowledge of Helm Charts, Docker, and Vaults - to deploy the chart independently without external help. <br>A troubleshooting and FAQ section is included to support the developer. <br>Prerequisites, skills, and technology requirements are outlined, detailing what a developer must know to perform the deployment autonomously. |
+| 7.1.4.2        | Documentation of the Hausanschluss-Bundles                                                                                                                                                                                                                                                                                                           | Documentation of the Hausanschluss-Bundles is completed.                                                                                                                                                                                                                                                                                                                                                                                                                                                         | Documentation is provided for: <br>Configuration of the defined bundles according to the specified requirements and parameters <br>Integration of the documentation into the Umbrella HELM Charts <br>Integration into the Umbrella HELM Chart to ensure consistent deployment                                                                                                                                       |
+| [WP-7.1.-D005] | [WP-7.1.-D005] Umbrella HELM Charts for the Hausanschluss developed, tested, and documented                                                                                                                                                                                                                                                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | [WP-7.1.-D005] Umbrella HELM Charts for the Hausanschluss have been developed, tested, and documented.                                                                                                                                                                                                                                                                                                               |
+| 7.1.5.1        | Re-activate Umbrella HELM Charts to the latest release state                                                                                                                                                                                                                                                                                         | The Enablement Services components of the Umbrella HELM Charts must be updated to version R24.12. This includes the following upgrades: <br> Upgrade DTR to version R24.12 (#188) <br>Upgrade EDCs to version R24.12 (#193) <br>Update SSI-DIM-Wallet-Stub to version 0.1.8 (#206)                                                                                                                                                                                                                               | The HELM Chart will then contain the updated versions of the components. <br>After the upgrade, the components (DTR, EDCs, SSI‑DIM‑Wallet‑Stub) run stably without functional impairments. <br>The deployment pipeline for the HELM Chart executes successfully <br>Relevant tests & smoke tests (e.g., integration tests) confirm the migration.                                                                    |
path: docs/concept/TAP7.1-solution-design.md
user: login: CDiezRodriguez
body: ```suggestion
| 7.1.5.1        | Re-activate Umbrella HELM Charts to the latest release state                                                                                                                                                                                                                                                                                         | The Enablement Services components of the Umbrella HELM Charts must be updated to version R24.12. This includes the following upgrades: <br> Upgrade DTR to version R24.12 (#188) <br>Upgrade EDCs to version R24.12 (#193) <br>Update SSI-DIM-Wallet-Stub to version 0.1.8 (#206)                                                                                                                                                                                                                               | The HELM Chart will then contain the updated versions of the components. <br>After the upgrade, the components (DTR, EDCs, SSI‑DIM‑Wallet‑Stub) run stably without functional impairments. <br>The deployment pipeline for the HELM Chart executes successfully. <br>Relevant tests & smoke tests (e.g., integration tests) confirm the migration.                                                                    |
```
created_at: 2025-04-03T10:01:19Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,516 @@
+# Solution Design "Hausanschluss" Bundle Concept
+
+# 1 Business Case
+
+## 1.1 Executive Summary
+
+The "Hausanschluss" Bundle aims to simplify the installation of the enablement services Eclipse Dataspace
+Connector (EDC), Digital Twin Registry (DTR), and their supporting components. By developing a flexible, parameterizable
+installation package, the project seeks to reduce deployment complexity and lower barriers to participation in the
+Catena‑X data space. This bundle will enable independent component updates and support a modular "bring your own"
+approach, ultimately fostering a more efficient and accessible ecosystem for diverse participants—such as testers,
+external product developers, product testers, and small and medium-sized enterprises.
+
+## 1.2 Business Need
+
+Current deployment methods for data space integration are complex and require significant manual effort. This PoC
+addresses the need to:
+
+- **Reduce Complexity:** Simplify the deployment topology by bundling components into capabilities.
+- **Automate Deployment:** Provide an automated installation package using Kubernetes and HELM.
+- **Minimize Configuration Overhead:** Streamline the integration process by providing pre-configured bundles that require only minimal manual parameter adjustments.
+- **Extend Documentation:** Provide a detailed documentation tailored to the target groups.
+- **Enable Extension:** Design the system to allow the seamless addition of new components or capabilities.
+
+## 1.3 Objectives
+
+- **Simplify Deployment and Maintenance:** Develop an installation package that minimizes manual configuration through
+  automation.
+- **Ensure Modularity:** Structure the bundle so that components can be independently installed, updated, or replaced
+  without affecting other services.
+- **Facilitate Flexibility:** Implement a "bring your own" model for key components, such as EDC, PostgreSQL, and HashiCorp
+  Vault, to allow tailored deployments that meet specific needs.
+- **Increase Accessibility**: Lower entry barriers for new participants by reducing technical complexity and operational
+  dependencies.
+- **Scalability:** Structure the bundles so that they can be deployed multiple times.
+
+## 1.4 Expected Deliverables
+
+- **PoC Documentation:** A concept and architecture overview highlighting the modular design.
+- **Modular Installation Package:** A set of HELM charts for deploying the enablement service bundles:
+    - **Dataspace Connector:** Including the Eclipse Dataspace Connector, EDC PostgreSQL, and HashiCorp Vault.
+    - **Digital Twin Bundle:** Featuring components such as the Decentral DT Registry (with “bring your own” PostgreSQL)
+    - **Data Persitence Layer Bundle:** Including a simple Submodel Server to store semantic data.
+    - **Identity Wallet Bundle:** Covering the Identity Wallet functionality.
+- **Demonstration Environment:** A test deployment showcasing reduced complexity and improved efficiency.
+- **Basic User Guide:** Instructions on how to deploy and update the PoC bundle.
+
+## 1.5 Benefits
+
+- **Operational Efficiency:** Faster and more reliable deployments with less manual work.
+- **Scalability:** A modular design that can be scaled or adapted for future full-scale deployments.
+- **Ease of Adoption:** Simplified deployment processes make it easier for testers and external developers to engage.
+
+## 1.6. Dependencies
+
+- **Interoperability** with the CATENA‑X standards.
+
+## 1.7. Success Criteria
+
+- **Technology Readiness Level:** Achievement of a Technology Readiness Level (TRL) of 3, as specified in the requirements.
+- **Functional PoC Deployment:** Demonstrated automated, modular installation with reduced manual steps.
+- **Simplified Configuration:** Clear evidence of reduced configuration complexity.
+- **Positive Feedback:** End-user validation from a select group of demo participants and the Tractus-X community.
+- **Documentation Completeness:** Availability of concise deployment and user guides.
+
+## 1.8. Out of Scope
+
+- **Full Production Readiness:** This PoC is not intended to be a production-ready solution.
+- **Core Services Exclusion:** Core services are not part of the Hausanschluss Bundles.
+- **App Provider Role:** The role of App Provider is considered out of scope for this deployment.
+- **Alternative Deployment Techniques:** While the evaluation of alternative deployment methods is acknowledged, the primary
+  focus remains on Kubernetes and HELM-based deployment.
+
+# 2 Requirements Analysis
+
+## 2.1 Assumptions
+
+## 2.2 Requirements Catalog
+
+| ID             | Requirement                                                                                                                                                                                                                                                                                                                                          | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | Deliverables / Acceptance Criteria                                                                                                                                                                                                                                                                                                                                                                                   |
+|----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| [WP-7.1.-D001] | The Hausanschluss Bundle aims to simplify the installation and maintenance of the EDC and other components that together ensure a “Hausanschluss”. A flexible, parameterizable installation package is intended to reduce complexity and make integration more efficient, thereby simplifying participation in Catena‑X for additional participants. | Specification and development of a flexible, parameterizable installation package that reduces the complexity of installing and maintaining the required components for seamless integration into the Catena‑X data space. This package should facilitate updates and new versions, making participation in Catena‑X more efficient and accessible. In doing so, SMEs shall be enabled to participate without high costs or dependency on SaaS providers while maintaining control over their IT infrastructure. | [WP-7.1.-D001] Concept for the Hausanschluss is created                                                                                                                                                                                                                                                                                                                                                              |
+| 7.1.1.1        | The solution concept must define the Capability Bundles structures to be implemented. For each Capability Bundle, the included bundles and their versions are mapped.                                                                                                                                                                                | "The following Capability Bundle structure is implemented:                                                                                                                                                                                                                                                                                                                                                                                                                                                       | The structure of the Capability Bundles for the Enablement Services has been specified. For version R24.12 it is clearly defined which Tractus‑X services and components are assigned to each Capability Bundle                                                                                                                                                                                                      |
+| 7.1.1.2        | Definition of Data Space Roles                                                                                                                                                                                                                                                                                                                       | Data Consumer, Data Provider, Enablement Service Provider                                                                                                                                                                                                                                                                                                                                                                                                                                                        | As part of the target group analysis, the target groups are defined and aligned with the data space roles. <br>Mapping from data space role to target group has been completed. <br>Mapping from target group to data space role has been completed. <br>An assignment of data space roles to Capability Bundles has been made.                                                                                      |
+| 7.1.1.4        | Modularity & Maintainability: No dependencies between Capability Bundles                                                                                                                                                                                                                                                                             | Unique assignment of components and services to a defined Capability Bundle. <br>Each component and service should be assigned to only one Capability Bundle. <br>Dependencies between Capability Bundles are allowed.                                                                                                                                                                                                                                                                                           | Components and Services should only be part of one bundle. <br>Each bundle must be deployable in isolation and can be installed, updated, or removed independently. <br>Capability Bundles must be organized in separate HELM sub‑charts. <br>Circular dependencies between bundles must be avoided.                                                                                                                 |
+| 7.1.1.5        | Modularity & Maintainability: Concept for reducing deployment complexity                                                                                                                                                                                                                                                                             | The system deployment should be optimized to reduce the existing complexity. The goal is to make the provisioning process more efficient, robust, and easier to maintain.                                                                                                                                                                                                                                                                                                                                        | **Simplification of deployment processes:** A reduction of manual configuration steps has been achieved. <br>**Transparency and traceability:** Clearly documented deployment steps are provided. <br>**Improvements of Chart configuration by:** <br>usage of template  <br>reducing configuration options <br>reducing manual steps in the setup                                                                   |
+| 7.1.1.6        | Modularity & Maintainability                                                                                                                                                                                                                                                                                                                         | Charts are published automatically.                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | Charts are published via a publicly accessible charts repository.                                                                                                                                                                                                                                                                                                                                                    |
+| 7.1.1.13       | Solution Concept                                                                                                                                                                                                                                                                                                                                     | Creation of a solution design for the “Hausanschluss” Bundle.                                                                                                                                                                                                                                                                                                                                                                                                                                                    | The solution design for the "Hausanschluss" Bundle is created. <br>The solution design for the "Hausanschluss" Bundle ispublished in the repository: https://github.com/eclipse-tractusx/tractus-x-umbrella.                                                                                                                                                                                                         |
+| 7.1.1.14       | Scalability of Enablement Services                                                                                                                                                                                                                                                                                                                   | Scalability of Enablement Services                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | Developers should be able to deploy an arbitrary number of Enablement Services. <br>Example: Up to 3 EDCs can be provided.                                                                                                                                                                                                                                                                                           |
+| 7.1.1.16       | Interoperability                                                                                                                                                                                                                                                                                                                                     | Interoperability                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | Interoperability with the CATENA‑X standards. <br>This interoperability is documented and traceable.                                                                                                                                                                                                                                                                                                                 |
+| [WP-7.1.-D002] | [WP-7.1.-D002] Target group for the specification is defined.                                                                                                                                                                                                                                                                                        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | [WP-7.1.-D002] Target group for the specification is defined.                                                                                                                                                                                                                                                                                                                                                        |
+| 7.1.2.1        | Target Group Analysis                                                                                                                                                                                                                                                                                                                                | The target group analysis for the "Hausanschluss Bundle"is defined.                                                                                                                                                                                                                                                                                                                                                                                                                                              | The analysis has been conducted. <br>The target group is included in the solution concept <br>To be clarified: What is included in the Hausanschluss and who can operate it in which scenario (OEM, SME, service provider, etc.).                                                                                                                                                                                    |
+| [WP-7.1.-D003] | [WP-7.1.-D003] Decentralized components and services defined                                                                                                                                                                                                                                                                                         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | [WP-7.1.-D003] Decentralized components and services have been defined.                                                                                                                                                                                                                                                                                                                                              |
+| 7.1.3.1        | See [WP-7.1.-D001-AC001]                                                                                                                                                                                                                                                                                                                             |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | See [WP-7.1.-D001-AC001]                                                                                                                                                                                                                                                                                                                                                                                             |
+| [WP-7.1.-D004] | [WP-7.1.-D004] Documentation of the Hausanschluss Bundle is completed                                                                                                                                                                                                                                                                                |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | [WP-7.1.-D004] Documentation of the Hausanschluss Bundle is completed                                                                                                                                                                                                                                                                                                                                                |
+| 7.1.4.1        | Documentation of the Hausanschluss-Bundles                                                                                                                                                                                                                                                                                                           | Usability                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | Documentation is provided that enables an experienced product developer - with knowledge of Helm Charts, Docker, and Vaults - to deploy the chart independently without external help. <br>A troubleshooting and FAQ section is included to support the developer. <br>Prerequisites, skills, and technology requirements are outlined, detailing what a developer must know to perform the deployment autonomously. |
+| 7.1.4.2        | Documentation of the Hausanschluss-Bundles                                                                                                                                                                                                                                                                                                           | Documentation of the Hausanschluss-Bundles is completed.                                                                                                                                                                                                                                                                                                                                                                                                                                                         | Documentation is provided for: <br>Configuration of the defined bundles according to the specified requirements and parameters <br>Integration of the documentation into the Umbrella HELM Charts <br>Integration into the Umbrella HELM Chart to ensure consistent deployment                                                                                                                                       |
+| [WP-7.1.-D005] | [WP-7.1.-D005] Umbrella HELM Charts for the Hausanschluss developed, tested, and documented                                                                                                                                                                                                                                                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | [WP-7.1.-D005] Umbrella HELM Charts for the Hausanschluss have been developed, tested, and documented.                                                                                                                                                                                                                                                                                                               |
+| 7.1.5.1        | Re-activate Umbrella HELM Charts to the latest release state                                                                                                                                                                                                                                                                                         | The Enablement Services components of the Umbrella HELM Charts must be updated to version R24.12. This includes the following upgrades: <br> Upgrade DTR to version R24.12 (#188) <br>Upgrade EDCs to version R24.12 (#193) <br>Update SSI-DIM-Wallet-Stub to version 0.1.8 (#206)                                                                                                                                                                                                                               | The HELM Chart will then contain the updated versions of the components. <br>After the upgrade, the components (DTR, EDCs, SSI‑DIM‑Wallet‑Stub) run stably without functional impairments. <br>The deployment pipeline for the HELM Chart executes successfully <br>Relevant tests & smoke tests (e.g., integration tests) confirm the migration.                                                                    |
+| 7.1.5.2        | Hierarchical structuring and bundling of Enablement Service components in the Umbrella HELM Chart                                                                                                                                                                                                                                                    | The Umbrella HELM Chart should be structured hierarchically so that related Enablement Service components are grouped into bundles. <br>The Umbrella HELM Chart must have a clear hierarchical structure <br> Each Enablement Service component must be assigned to a unique bundle.<br>No circular dependencies between bundles are allowed.                                                                                                                                                                    | The chart is modular and divided into defined bundles. <br>Each bundle can be deployed and maintained independently.                                                                                                                                                                                                                                                                                                 |
path: docs/concept/TAP7.1-solution-design.md
user: login: CDiezRodriguez
body: ```suggestion
| 7.1.5.2        | Hierarchical structuring and bundling of Enablement Service components in the Umbrella HELM Chart                                                                                                                                                                                                                                                    | The Umbrella HELM Chart should be structured hierarchically so that related Enablement Service components are grouped into bundles. <br>The Umbrella HELM Chart must have a clear hierarchical structure. <br> Each Enablement Service component must be assigned to a unique bundle.<br>No circular dependencies between bundles are allowed.                                                                                                                                                                    | The chart is modular and divided into defined bundles. <br>Each bundle can be deployed and maintained independently.                                                                                                                                                                                                                                                                                                 |
```
created_at: 2025-04-03T10:04:01Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,516 @@
+# Solution Design "Hausanschluss" Bundle Concept
+
+# 1 Business Case
+
+## 1.1 Executive Summary
+
+The "Hausanschluss" Bundle aims to simplify the installation of the enablement services Eclipse Dataspace
+Connector (EDC), Digital Twin Registry (DTR), and their supporting components. By developing a flexible, parameterizable
+installation package, the project seeks to reduce deployment complexity and lower barriers to participation in the
+Catena‑X data space. This bundle will enable independent component updates and support a modular "bring your own"
+approach, ultimately fostering a more efficient and accessible ecosystem for diverse participants—such as testers,
+external product developers, product testers, and small and medium-sized enterprises.
+
+## 1.2 Business Need
+
+Current deployment methods for data space integration are complex and require significant manual effort. This PoC
+addresses the need to:
+
+- **Reduce Complexity:** Simplify the deployment topology by bundling components into capabilities.
+- **Automate Deployment:** Provide an automated installation package using Kubernetes and HELM.
+- **Minimize Configuration Overhead:** Streamline the integration process by providing pre-configured bundles that require only minimal manual parameter adjustments.
+- **Extend Documentation:** Provide a detailed documentation tailored to the target groups.
+- **Enable Extension:** Design the system to allow the seamless addition of new components or capabilities.
+
+## 1.3 Objectives
+
+- **Simplify Deployment and Maintenance:** Develop an installation package that minimizes manual configuration through
+  automation.
+- **Ensure Modularity:** Structure the bundle so that components can be independently installed, updated, or replaced
+  without affecting other services.
+- **Facilitate Flexibility:** Implement a "bring your own" model for key components, such as EDC, PostgreSQL, and HashiCorp
+  Vault, to allow tailored deployments that meet specific needs.
+- **Increase Accessibility**: Lower entry barriers for new participants by reducing technical complexity and operational
+  dependencies.
+- **Scalability:** Structure the bundles so that they can be deployed multiple times.
+
+## 1.4 Expected Deliverables
+
+- **PoC Documentation:** A concept and architecture overview highlighting the modular design.
+- **Modular Installation Package:** A set of HELM charts for deploying the enablement service bundles:
+    - **Dataspace Connector:** Including the Eclipse Dataspace Connector, EDC PostgreSQL, and HashiCorp Vault.
+    - **Digital Twin Bundle:** Featuring components such as the Decentral DT Registry (with “bring your own” PostgreSQL)
+    - **Data Persitence Layer Bundle:** Including a simple Submodel Server to store semantic data.
path: docs/concept/TAP7.1-solution-design.md
user: login: mgarciaLKS
body: ```suggestion
    - **Data Persistence Layer Bundle:** Including a simple Submodel Server to store semantic data.
```
created_at: 2025-04-03T10:04:12Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,516 @@
+# Solution Design "Hausanschluss" Bundle Concept
+
+# 1 Business Case
+
+## 1.1 Executive Summary
+
+The "Hausanschluss" Bundle aims to simplify the installation of the enablement services Eclipse Dataspace
+Connector (EDC), Digital Twin Registry (DTR), and their supporting components. By developing a flexible, parameterizable
+installation package, the project seeks to reduce deployment complexity and lower barriers to participation in the
+Catena‑X data space. This bundle will enable independent component updates and support a modular "bring your own"
+approach, ultimately fostering a more efficient and accessible ecosystem for diverse participants—such as testers,
+external product developers, product testers, and small and medium-sized enterprises.
+
+## 1.2 Business Need
+
+Current deployment methods for data space integration are complex and require significant manual effort. This PoC
+addresses the need to:
+
+- **Reduce Complexity:** Simplify the deployment topology by bundling components into capabilities.
+- **Automate Deployment:** Provide an automated installation package using Kubernetes and HELM.
+- **Minimize Configuration Overhead:** Streamline the integration process by providing pre-configured bundles that require only minimal manual parameter adjustments.
+- **Extend Documentation:** Provide a detailed documentation tailored to the target groups.
+- **Enable Extension:** Design the system to allow the seamless addition of new components or capabilities.
+
+## 1.3 Objectives
+
+- **Simplify Deployment and Maintenance:** Develop an installation package that minimizes manual configuration through
+  automation.
+- **Ensure Modularity:** Structure the bundle so that components can be independently installed, updated, or replaced
+  without affecting other services.
+- **Facilitate Flexibility:** Implement a "bring your own" model for key components, such as EDC, PostgreSQL, and HashiCorp
+  Vault, to allow tailored deployments that meet specific needs.
+- **Increase Accessibility**: Lower entry barriers for new participants by reducing technical complexity and operational
+  dependencies.
+- **Scalability:** Structure the bundles so that they can be deployed multiple times.
+
+## 1.4 Expected Deliverables
+
+- **PoC Documentation:** A concept and architecture overview highlighting the modular design.
+- **Modular Installation Package:** A set of HELM charts for deploying the enablement service bundles:
+    - **Dataspace Connector:** Including the Eclipse Dataspace Connector, EDC PostgreSQL, and HashiCorp Vault.
+    - **Digital Twin Bundle:** Featuring components such as the Decentral DT Registry (with “bring your own” PostgreSQL)
+    - **Data Persitence Layer Bundle:** Including a simple Submodel Server to store semantic data.
+    - **Identity Wallet Bundle:** Covering the Identity Wallet functionality.
+- **Demonstration Environment:** A test deployment showcasing reduced complexity and improved efficiency.
+- **Basic User Guide:** Instructions on how to deploy and update the PoC bundle.
+
+## 1.5 Benefits
+
+- **Operational Efficiency:** Faster and more reliable deployments with less manual work.
+- **Scalability:** A modular design that can be scaled or adapted for future full-scale deployments.
+- **Ease of Adoption:** Simplified deployment processes make it easier for testers and external developers to engage.
+
+## 1.6. Dependencies
+
+- **Interoperability** with the CATENA‑X standards.
+
+## 1.7. Success Criteria
+
+- **Technology Readiness Level:** Achievement of a Technology Readiness Level (TRL) of 3, as specified in the requirements.
+- **Functional PoC Deployment:** Demonstrated automated, modular installation with reduced manual steps.
+- **Simplified Configuration:** Clear evidence of reduced configuration complexity.
+- **Positive Feedback:** End-user validation from a select group of demo participants and the Tractus-X community.
+- **Documentation Completeness:** Availability of concise deployment and user guides.
+
+## 1.8. Out of Scope
+
+- **Full Production Readiness:** This PoC is not intended to be a production-ready solution.
+- **Core Services Exclusion:** Core services are not part of the Hausanschluss Bundles.
+- **App Provider Role:** The role of App Provider is considered out of scope for this deployment.
+- **Alternative Deployment Techniques:** While the evaluation of alternative deployment methods is acknowledged, the primary
+  focus remains on Kubernetes and HELM-based deployment.
+
+# 2 Requirements Analysis
+
+## 2.1 Assumptions
+
+## 2.2 Requirements Catalog
+
+| ID             | Requirement                                                                                                                                                                                                                                                                                                                                          | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | Deliverables / Acceptance Criteria                                                                                                                                                                                                                                                                                                                                                                                   |
+|----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| [WP-7.1.-D001] | The Hausanschluss Bundle aims to simplify the installation and maintenance of the EDC and other components that together ensure a “Hausanschluss”. A flexible, parameterizable installation package is intended to reduce complexity and make integration more efficient, thereby simplifying participation in Catena‑X for additional participants. | Specification and development of a flexible, parameterizable installation package that reduces the complexity of installing and maintaining the required components for seamless integration into the Catena‑X data space. This package should facilitate updates and new versions, making participation in Catena‑X more efficient and accessible. In doing so, SMEs shall be enabled to participate without high costs or dependency on SaaS providers while maintaining control over their IT infrastructure. | [WP-7.1.-D001] Concept for the Hausanschluss is created                                                                                                                                                                                                                                                                                                                                                              |
+| 7.1.1.1        | The solution concept must define the Capability Bundles structures to be implemented. For each Capability Bundle, the included bundles and their versions are mapped.                                                                                                                                                                                | "The following Capability Bundle structure is implemented:                                                                                                                                                                                                                                                                                                                                                                                                                                                       | The structure of the Capability Bundles for the Enablement Services has been specified. For version R24.12 it is clearly defined which Tractus‑X services and components are assigned to each Capability Bundle                                                                                                                                                                                                      |
+| 7.1.1.2        | Definition of Data Space Roles                                                                                                                                                                                                                                                                                                                       | Data Consumer, Data Provider, Enablement Service Provider                                                                                                                                                                                                                                                                                                                                                                                                                                                        | As part of the target group analysis, the target groups are defined and aligned with the data space roles. <br>Mapping from data space role to target group has been completed. <br>Mapping from target group to data space role has been completed. <br>An assignment of data space roles to Capability Bundles has been made.                                                                                      |
+| 7.1.1.4        | Modularity & Maintainability: No dependencies between Capability Bundles                                                                                                                                                                                                                                                                             | Unique assignment of components and services to a defined Capability Bundle. <br>Each component and service should be assigned to only one Capability Bundle. <br>Dependencies between Capability Bundles are allowed.                                                                                                                                                                                                                                                                                           | Components and Services should only be part of one bundle. <br>Each bundle must be deployable in isolation and can be installed, updated, or removed independently. <br>Capability Bundles must be organized in separate HELM sub‑charts. <br>Circular dependencies between bundles must be avoided.                                                                                                                 |
+| 7.1.1.5        | Modularity & Maintainability: Concept for reducing deployment complexity                                                                                                                                                                                                                                                                             | The system deployment should be optimized to reduce the existing complexity. The goal is to make the provisioning process more efficient, robust, and easier to maintain.                                                                                                                                                                                                                                                                                                                                        | **Simplification of deployment processes:** A reduction of manual configuration steps has been achieved. <br>**Transparency and traceability:** Clearly documented deployment steps are provided. <br>**Improvements of Chart configuration by:** <br>usage of template  <br>reducing configuration options <br>reducing manual steps in the setup                                                                   |
+| 7.1.1.6        | Modularity & Maintainability                                                                                                                                                                                                                                                                                                                         | Charts are published automatically.                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | Charts are published via a publicly accessible charts repository.                                                                                                                                                                                                                                                                                                                                                    |
+| 7.1.1.13       | Solution Concept                                                                                                                                                                                                                                                                                                                                     | Creation of a solution design for the “Hausanschluss” Bundle.                                                                                                                                                                                                                                                                                                                                                                                                                                                    | The solution design for the "Hausanschluss" Bundle is created. <br>The solution design for the "Hausanschluss" Bundle ispublished in the repository: https://github.com/eclipse-tractusx/tractus-x-umbrella.                                                                                                                                                                                                         |
+| 7.1.1.14       | Scalability of Enablement Services                                                                                                                                                                                                                                                                                                                   | Scalability of Enablement Services                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | Developers should be able to deploy an arbitrary number of Enablement Services. <br>Example: Up to 3 EDCs can be provided.                                                                                                                                                                                                                                                                                           |
+| 7.1.1.16       | Interoperability                                                                                                                                                                                                                                                                                                                                     | Interoperability                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | Interoperability with the CATENA‑X standards. <br>This interoperability is documented and traceable.                                                                                                                                                                                                                                                                                                                 |
+| [WP-7.1.-D002] | [WP-7.1.-D002] Target group for the specification is defined.                                                                                                                                                                                                                                                                                        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | [WP-7.1.-D002] Target group for the specification is defined.                                                                                                                                                                                                                                                                                                                                                        |
+| 7.1.2.1        | Target Group Analysis                                                                                                                                                                                                                                                                                                                                | The target group analysis for the "Hausanschluss Bundle"is defined.                                                                                                                                                                                                                                                                                                                                                                                                                                              | The analysis has been conducted. <br>The target group is included in the solution concept <br>To be clarified: What is included in the Hausanschluss and who can operate it in which scenario (OEM, SME, service provider, etc.).                                                                                                                                                                                    |
+| [WP-7.1.-D003] | [WP-7.1.-D003] Decentralized components and services defined                                                                                                                                                                                                                                                                                         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | [WP-7.1.-D003] Decentralized components and services have been defined.                                                                                                                                                                                                                                                                                                                                              |
+| 7.1.3.1        | See [WP-7.1.-D001-AC001]                                                                                                                                                                                                                                                                                                                             |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | See [WP-7.1.-D001-AC001]                                                                                                                                                                                                                                                                                                                                                                                             |
+| [WP-7.1.-D004] | [WP-7.1.-D004] Documentation of the Hausanschluss Bundle is completed                                                                                                                                                                                                                                                                                |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | [WP-7.1.-D004] Documentation of the Hausanschluss Bundle is completed                                                                                                                                                                                                                                                                                                                                                |
+| 7.1.4.1        | Documentation of the Hausanschluss-Bundles                                                                                                                                                                                                                                                                                                           | Usability                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | Documentation is provided that enables an experienced product developer - with knowledge of Helm Charts, Docker, and Vaults - to deploy the chart independently without external help. <br>A troubleshooting and FAQ section is included to support the developer. <br>Prerequisites, skills, and technology requirements are outlined, detailing what a developer must know to perform the deployment autonomously. |
+| 7.1.4.2        | Documentation of the Hausanschluss-Bundles                                                                                                                                                                                                                                                                                                           | Documentation of the Hausanschluss-Bundles is completed.                                                                                                                                                                                                                                                                                                                                                                                                                                                         | Documentation is provided for: <br>Configuration of the defined bundles according to the specified requirements and parameters <br>Integration of the documentation into the Umbrella HELM Charts <br>Integration into the Umbrella HELM Chart to ensure consistent deployment                                                                                                                                       |
+| [WP-7.1.-D005] | [WP-7.1.-D005] Umbrella HELM Charts for the Hausanschluss developed, tested, and documented                                                                                                                                                                                                                                                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | [WP-7.1.-D005] Umbrella HELM Charts for the Hausanschluss have been developed, tested, and documented.                                                                                                                                                                                                                                                                                                               |
+| 7.1.5.1        | Re-activate Umbrella HELM Charts to the latest release state                                                                                                                                                                                                                                                                                         | The Enablement Services components of the Umbrella HELM Charts must be updated to version R24.12. This includes the following upgrades: <br> Upgrade DTR to version R24.12 (#188) <br>Upgrade EDCs to version R24.12 (#193) <br>Update SSI-DIM-Wallet-Stub to version 0.1.8 (#206)                                                                                                                                                                                                                               | The HELM Chart will then contain the updated versions of the components. <br>After the upgrade, the components (DTR, EDCs, SSI‑DIM‑Wallet‑Stub) run stably without functional impairments. <br>The deployment pipeline for the HELM Chart executes successfully <br>Relevant tests & smoke tests (e.g., integration tests) confirm the migration.                                                                    |
+| 7.1.5.2        | Hierarchical structuring and bundling of Enablement Service components in the Umbrella HELM Chart                                                                                                                                                                                                                                                    | The Umbrella HELM Chart should be structured hierarchically so that related Enablement Service components are grouped into bundles. <br>The Umbrella HELM Chart must have a clear hierarchical structure <br> Each Enablement Service component must be assigned to a unique bundle.<br>No circular dependencies between bundles are allowed.                                                                                                                                                                    | The chart is modular and divided into defined bundles. <br>Each bundle can be deployed and maintained independently.                                                                                                                                                                                                                                                                                                 |
+| 7.1.5.3        | Interchangeability of bundle components via “Bring-Your-Own” components                                                                                                                                                                                                                                                                              | Bundle components should be interchangeable through “Bring-Your-Own” components. <br>“Bring your own” is available for every component and means that these components do not have to be delivered by default with the Umbrella Chart but can be provided by the respective users.                                                                                                                                                                                                                               | Bundle components can be interchanged by “Bring-Your-Own” components.                                                                                                                                                                                                                                                                                                                                                |
+| [WP-7.1.-D006] | [WP-7.1.-D006] Product developed according to a Technology Readiness Level (TRL) of 3                                                                                                                                                                                                                                                                |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | [WP-7.1.-D006] The product is developed according to a Technology Readiness Level (TRL) of 3                                                                                                                                                                                                                                                                                                                         |
+| 7.1.6.1        | POC                                                                                                                                                                                                                                                                                                                                                  | Creation of a POC for the "Hausanschluss" Bundle                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | POC implementation is completed. <br>POC has been presented in a demo                                                                                                                                                                                                                                                                                                                                                |
path: docs/concept/TAP7.1-solution-design.md
user: login: CDiezRodriguez
body: ```suggestion
| 7.1.6.1        | POC                                                                                                                                                                                                                                                                                                                                                  | Creation of a POC for the "Hausanschluss" Bundle                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | POC implementation is completed. <br>POC has been presented in a demo.                                                                                                                                                                                                                                                                                                                                                |
```
created_at: 2025-04-03T10:04:44Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,516 @@
+# Solution Design "Hausanschluss" Bundle Concept
+
+# 1 Business Case
+
+## 1.1 Executive Summary
+
+The "Hausanschluss" Bundle aims to simplify the installation of the enablement services Eclipse Dataspace
+Connector (EDC), Digital Twin Registry (DTR), and their supporting components. By developing a flexible, parameterizable
+installation package, the project seeks to reduce deployment complexity and lower barriers to participation in the
+Catena‑X data space. This bundle will enable independent component updates and support a modular "bring your own"
+approach, ultimately fostering a more efficient and accessible ecosystem for diverse participants—such as testers,
+external product developers, product testers, and small and medium-sized enterprises.
+
+## 1.2 Business Need
+
+Current deployment methods for data space integration are complex and require significant manual effort. This PoC
+addresses the need to:
+
+- **Reduce Complexity:** Simplify the deployment topology by bundling components into capabilities.
+- **Automate Deployment:** Provide an automated installation package using Kubernetes and HELM.
+- **Minimize Configuration Overhead:** Streamline the integration process by providing pre-configured bundles that require only minimal manual parameter adjustments.
+- **Extend Documentation:** Provide a detailed documentation tailored to the target groups.
+- **Enable Extension:** Design the system to allow the seamless addition of new components or capabilities.
+
+## 1.3 Objectives
+
+- **Simplify Deployment and Maintenance:** Develop an installation package that minimizes manual configuration through
+  automation.
+- **Ensure Modularity:** Structure the bundle so that components can be independently installed, updated, or replaced
+  without affecting other services.
+- **Facilitate Flexibility:** Implement a "bring your own" model for key components, such as EDC, PostgreSQL, and HashiCorp
+  Vault, to allow tailored deployments that meet specific needs.
+- **Increase Accessibility**: Lower entry barriers for new participants by reducing technical complexity and operational
+  dependencies.
+- **Scalability:** Structure the bundles so that they can be deployed multiple times.
+
+## 1.4 Expected Deliverables
+
+- **PoC Documentation:** A concept and architecture overview highlighting the modular design.
+- **Modular Installation Package:** A set of HELM charts for deploying the enablement service bundles:
+    - **Dataspace Connector:** Including the Eclipse Dataspace Connector, EDC PostgreSQL, and HashiCorp Vault.
+    - **Digital Twin Bundle:** Featuring components such as the Decentral DT Registry (with “bring your own” PostgreSQL)
+    - **Data Persitence Layer Bundle:** Including a simple Submodel Server to store semantic data.
+    - **Identity Wallet Bundle:** Covering the Identity Wallet functionality.
+- **Demonstration Environment:** A test deployment showcasing reduced complexity and improved efficiency.
+- **Basic User Guide:** Instructions on how to deploy and update the PoC bundle.
+
+## 1.5 Benefits
+
+- **Operational Efficiency:** Faster and more reliable deployments with less manual work.
+- **Scalability:** A modular design that can be scaled or adapted for future full-scale deployments.
+- **Ease of Adoption:** Simplified deployment processes make it easier for testers and external developers to engage.
+
+## 1.6. Dependencies
+
+- **Interoperability** with the CATENA‑X standards.
+
+## 1.7. Success Criteria
+
+- **Technology Readiness Level:** Achievement of a Technology Readiness Level (TRL) of 3, as specified in the requirements.
+- **Functional PoC Deployment:** Demonstrated automated, modular installation with reduced manual steps.
+- **Simplified Configuration:** Clear evidence of reduced configuration complexity.
+- **Positive Feedback:** End-user validation from a select group of demo participants and the Tractus-X community.
+- **Documentation Completeness:** Availability of concise deployment and user guides.
+
+## 1.8. Out of Scope
+
+- **Full Production Readiness:** This PoC is not intended to be a production-ready solution.
+- **Core Services Exclusion:** Core services are not part of the Hausanschluss Bundles.
+- **App Provider Role:** The role of App Provider is considered out of scope for this deployment.
+- **Alternative Deployment Techniques:** While the evaluation of alternative deployment methods is acknowledged, the primary
+  focus remains on Kubernetes and HELM-based deployment.
+
+# 2 Requirements Analysis
+
+## 2.1 Assumptions
+
+## 2.2 Requirements Catalog
+
+| ID             | Requirement                                                                                                                                                                                                                                                                                                                                          | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | Deliverables / Acceptance Criteria                                                                                                                                                                                                                                                                                                                                                                                   |
+|----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| [WP-7.1.-D001] | The Hausanschluss Bundle aims to simplify the installation and maintenance of the EDC and other components that together ensure a “Hausanschluss”. A flexible, parameterizable installation package is intended to reduce complexity and make integration more efficient, thereby simplifying participation in Catena‑X for additional participants. | Specification and development of a flexible, parameterizable installation package that reduces the complexity of installing and maintaining the required components for seamless integration into the Catena‑X data space. This package should facilitate updates and new versions, making participation in Catena‑X more efficient and accessible. In doing so, SMEs shall be enabled to participate without high costs or dependency on SaaS providers while maintaining control over their IT infrastructure. | [WP-7.1.-D001] Concept for the Hausanschluss is created                                                                                                                                                                                                                                                                                                                                                              |
+| 7.1.1.1        | The solution concept must define the Capability Bundles structures to be implemented. For each Capability Bundle, the included bundles and their versions are mapped.                                                                                                                                                                                | "The following Capability Bundle structure is implemented:                                                                                                                                                                                                                                                                                                                                                                                                                                                       | The structure of the Capability Bundles for the Enablement Services has been specified. For version R24.12 it is clearly defined which Tractus‑X services and components are assigned to each Capability Bundle                                                                                                                                                                                                      |
+| 7.1.1.2        | Definition of Data Space Roles                                                                                                                                                                                                                                                                                                                       | Data Consumer, Data Provider, Enablement Service Provider                                                                                                                                                                                                                                                                                                                                                                                                                                                        | As part of the target group analysis, the target groups are defined and aligned with the data space roles. <br>Mapping from data space role to target group has been completed. <br>Mapping from target group to data space role has been completed. <br>An assignment of data space roles to Capability Bundles has been made.                                                                                      |
+| 7.1.1.4        | Modularity & Maintainability: No dependencies between Capability Bundles                                                                                                                                                                                                                                                                             | Unique assignment of components and services to a defined Capability Bundle. <br>Each component and service should be assigned to only one Capability Bundle. <br>Dependencies between Capability Bundles are allowed.                                                                                                                                                                                                                                                                                           | Components and Services should only be part of one bundle. <br>Each bundle must be deployable in isolation and can be installed, updated, or removed independently. <br>Capability Bundles must be organized in separate HELM sub‑charts. <br>Circular dependencies between bundles must be avoided.                                                                                                                 |
+| 7.1.1.5        | Modularity & Maintainability: Concept for reducing deployment complexity                                                                                                                                                                                                                                                                             | The system deployment should be optimized to reduce the existing complexity. The goal is to make the provisioning process more efficient, robust, and easier to maintain.                                                                                                                                                                                                                                                                                                                                        | **Simplification of deployment processes:** A reduction of manual configuration steps has been achieved. <br>**Transparency and traceability:** Clearly documented deployment steps are provided. <br>**Improvements of Chart configuration by:** <br>usage of template  <br>reducing configuration options <br>reducing manual steps in the setup                                                                   |
+| 7.1.1.6        | Modularity & Maintainability                                                                                                                                                                                                                                                                                                                         | Charts are published automatically.                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | Charts are published via a publicly accessible charts repository.                                                                                                                                                                                                                                                                                                                                                    |
+| 7.1.1.13       | Solution Concept                                                                                                                                                                                                                                                                                                                                     | Creation of a solution design for the “Hausanschluss” Bundle.                                                                                                                                                                                                                                                                                                                                                                                                                                                    | The solution design for the "Hausanschluss" Bundle is created. <br>The solution design for the "Hausanschluss" Bundle ispublished in the repository: https://github.com/eclipse-tractusx/tractus-x-umbrella.                                                                                                                                                                                                         |
+| 7.1.1.14       | Scalability of Enablement Services                                                                                                                                                                                                                                                                                                                   | Scalability of Enablement Services                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | Developers should be able to deploy an arbitrary number of Enablement Services. <br>Example: Up to 3 EDCs can be provided.                                                                                                                                                                                                                                                                                           |
+| 7.1.1.16       | Interoperability                                                                                                                                                                                                                                                                                                                                     | Interoperability                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | Interoperability with the CATENA‑X standards. <br>This interoperability is documented and traceable.                                                                                                                                                                                                                                                                                                                 |
+| [WP-7.1.-D002] | [WP-7.1.-D002] Target group for the specification is defined.                                                                                                                                                                                                                                                                                        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | [WP-7.1.-D002] Target group for the specification is defined.                                                                                                                                                                                                                                                                                                                                                        |
+| 7.1.2.1        | Target Group Analysis                                                                                                                                                                                                                                                                                                                                | The target group analysis for the "Hausanschluss Bundle"is defined.                                                                                                                                                                                                                                                                                                                                                                                                                                              | The analysis has been conducted. <br>The target group is included in the solution concept <br>To be clarified: What is included in the Hausanschluss and who can operate it in which scenario (OEM, SME, service provider, etc.).                                                                                                                                                                                    |
+| [WP-7.1.-D003] | [WP-7.1.-D003] Decentralized components and services defined                                                                                                                                                                                                                                                                                         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | [WP-7.1.-D003] Decentralized components and services have been defined.                                                                                                                                                                                                                                                                                                                                              |
+| 7.1.3.1        | See [WP-7.1.-D001-AC001]                                                                                                                                                                                                                                                                                                                             |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | See [WP-7.1.-D001-AC001]                                                                                                                                                                                                                                                                                                                                                                                             |
+| [WP-7.1.-D004] | [WP-7.1.-D004] Documentation of the Hausanschluss Bundle is completed                                                                                                                                                                                                                                                                                |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | [WP-7.1.-D004] Documentation of the Hausanschluss Bundle is completed                                                                                                                                                                                                                                                                                                                                                |
+| 7.1.4.1        | Documentation of the Hausanschluss-Bundles                                                                                                                                                                                                                                                                                                           | Usability                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | Documentation is provided that enables an experienced product developer - with knowledge of Helm Charts, Docker, and Vaults - to deploy the chart independently without external help. <br>A troubleshooting and FAQ section is included to support the developer. <br>Prerequisites, skills, and technology requirements are outlined, detailing what a developer must know to perform the deployment autonomously. |
+| 7.1.4.2        | Documentation of the Hausanschluss-Bundles                                                                                                                                                                                                                                                                                                           | Documentation of the Hausanschluss-Bundles is completed.                                                                                                                                                                                                                                                                                                                                                                                                                                                         | Documentation is provided for: <br>Configuration of the defined bundles according to the specified requirements and parameters <br>Integration of the documentation into the Umbrella HELM Charts <br>Integration into the Umbrella HELM Chart to ensure consistent deployment                                                                                                                                       |
+| [WP-7.1.-D005] | [WP-7.1.-D005] Umbrella HELM Charts for the Hausanschluss developed, tested, and documented                                                                                                                                                                                                                                                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | [WP-7.1.-D005] Umbrella HELM Charts for the Hausanschluss have been developed, tested, and documented.                                                                                                                                                                                                                                                                                                               |
+| 7.1.5.1        | Re-activate Umbrella HELM Charts to the latest release state                                                                                                                                                                                                                                                                                         | The Enablement Services components of the Umbrella HELM Charts must be updated to version R24.12. This includes the following upgrades: <br> Upgrade DTR to version R24.12 (#188) <br>Upgrade EDCs to version R24.12 (#193) <br>Update SSI-DIM-Wallet-Stub to version 0.1.8 (#206)                                                                                                                                                                                                                               | The HELM Chart will then contain the updated versions of the components. <br>After the upgrade, the components (DTR, EDCs, SSI‑DIM‑Wallet‑Stub) run stably without functional impairments. <br>The deployment pipeline for the HELM Chart executes successfully <br>Relevant tests & smoke tests (e.g., integration tests) confirm the migration.                                                                    |
+| 7.1.5.2        | Hierarchical structuring and bundling of Enablement Service components in the Umbrella HELM Chart                                                                                                                                                                                                                                                    | The Umbrella HELM Chart should be structured hierarchically so that related Enablement Service components are grouped into bundles. <br>The Umbrella HELM Chart must have a clear hierarchical structure <br> Each Enablement Service component must be assigned to a unique bundle.<br>No circular dependencies between bundles are allowed.                                                                                                                                                                    | The chart is modular and divided into defined bundles. <br>Each bundle can be deployed and maintained independently.                                                                                                                                                                                                                                                                                                 |
+| 7.1.5.3        | Interchangeability of bundle components via “Bring-Your-Own” components                                                                                                                                                                                                                                                                              | Bundle components should be interchangeable through “Bring-Your-Own” components. <br>“Bring your own” is available for every component and means that these components do not have to be delivered by default with the Umbrella Chart but can be provided by the respective users.                                                                                                                                                                                                                               | Bundle components can be interchanged by “Bring-Your-Own” components.                                                                                                                                                                                                                                                                                                                                                |
+| [WP-7.1.-D006] | [WP-7.1.-D006] Product developed according to a Technology Readiness Level (TRL) of 3                                                                                                                                                                                                                                                                |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | [WP-7.1.-D006] The product is developed according to a Technology Readiness Level (TRL) of 3                                                                                                                                                                                                                                                                                                                         |
+| 7.1.6.1        | POC                                                                                                                                                                                                                                                                                                                                                  | Creation of a POC for the "Hausanschluss" Bundle                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | POC implementation is completed. <br>POC has been presented in a demo                                                                                                                                                                                                                                                                                                                                                |
+| 7.1.6.2        | Deployment Strategy                                                                                                                                                                                                                                                                                                                                  | The provisioning of bundles is carried out independently. <br>There must be an option to selectively activate or deactivate bundles.                                                                                                                                                                                                                                                                                                                                                                             | Configuration is managed via HELM values, allowing flexible adaptation according to the environment.                                                                                                                                                                                                                                                                                                                 |
+
+# 3 AS-IS Analysis
+
+## 3.1 People
+
+### 3.1.1 Target Group Analysis
+
+See "4.1.1 To-be Target Group Analysis" below. No deviations between As-is and To-be target groups have been identified.
+
+## 3.2 Process
+
+### 3.2.1 Use Case View (high-level)
+
+Umbrella Chart is intended for the following Use Cases:
+
+| Actor             | Use case                                                                                             |
+|-------------------|------------------------------------------------------------------------------------------------------|
+| Product Developer | Sandbox Environments: Create local environments to evaluate and experiment with Catena-X components. |
+| Product Developer | Development: Provide a unified setup for contributors and developers working on Tractus-X projects.  |
+| Product Tester    | Testing: Run end-to-end tests for Catena-X services.                                                 |
+| Product Manager   | Evaluate the dataspace to assess if their product can be used within Catena-X.                       |
+
+## 3.4 System
+
+### 3.4.1 Context Delimitation
+
+#### Existing Umbrella Chart Structure
+
+````mermaid
+flowchart
+    subgraph "Umbrella Chart"
+        ChartYaml["Chart.yaml"]
+        subgraph charts
+            Portal["Portal"]
+            CentralIdp["CentralIdp"]
path: docs/concept/TAP7.1-solution-design.md
user: login: CDiezRodriguez
body: ```suggestion
            CentralIdp["CentralIdp"]
            SharedIdp["SharedIdp"]
```
created_at: 2025-04-03T10:06:09Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,516 @@
+# Solution Design "Hausanschluss" Bundle Concept
+
+# 1 Business Case
+
+## 1.1 Executive Summary
+
+The "Hausanschluss" Bundle aims to simplify the installation of the enablement services Eclipse Dataspace
+Connector (EDC), Digital Twin Registry (DTR), and their supporting components. By developing a flexible, parameterizable
+installation package, the project seeks to reduce deployment complexity and lower barriers to participation in the
+Catena‑X data space. This bundle will enable independent component updates and support a modular "bring your own"
+approach, ultimately fostering a more efficient and accessible ecosystem for diverse participants—such as testers,
+external product developers, product testers, and small and medium-sized enterprises.
+
+## 1.2 Business Need
+
+Current deployment methods for data space integration are complex and require significant manual effort. This PoC
+addresses the need to:
+
+- **Reduce Complexity:** Simplify the deployment topology by bundling components into capabilities.
+- **Automate Deployment:** Provide an automated installation package using Kubernetes and HELM.
+- **Minimize Configuration Overhead:** Streamline the integration process by providing pre-configured bundles that require only minimal manual parameter adjustments.
+- **Extend Documentation:** Provide a detailed documentation tailored to the target groups.
+- **Enable Extension:** Design the system to allow the seamless addition of new components or capabilities.
+
+## 1.3 Objectives
+
+- **Simplify Deployment and Maintenance:** Develop an installation package that minimizes manual configuration through
+  automation.
+- **Ensure Modularity:** Structure the bundle so that components can be independently installed, updated, or replaced
+  without affecting other services.
+- **Facilitate Flexibility:** Implement a "bring your own" model for key components, such as EDC, PostgreSQL, and HashiCorp
+  Vault, to allow tailored deployments that meet specific needs.
+- **Increase Accessibility**: Lower entry barriers for new participants by reducing technical complexity and operational
+  dependencies.
+- **Scalability:** Structure the bundles so that they can be deployed multiple times.
+
+## 1.4 Expected Deliverables
+
+- **PoC Documentation:** A concept and architecture overview highlighting the modular design.
+- **Modular Installation Package:** A set of HELM charts for deploying the enablement service bundles:
+    - **Dataspace Connector:** Including the Eclipse Dataspace Connector, EDC PostgreSQL, and HashiCorp Vault.
+    - **Digital Twin Bundle:** Featuring components such as the Decentral DT Registry (with “bring your own” PostgreSQL)
+    - **Data Persitence Layer Bundle:** Including a simple Submodel Server to store semantic data.
+    - **Identity Wallet Bundle:** Covering the Identity Wallet functionality.
+- **Demonstration Environment:** A test deployment showcasing reduced complexity and improved efficiency.
+- **Basic User Guide:** Instructions on how to deploy and update the PoC bundle.
+
+## 1.5 Benefits
+
+- **Operational Efficiency:** Faster and more reliable deployments with less manual work.
+- **Scalability:** A modular design that can be scaled or adapted for future full-scale deployments.
+- **Ease of Adoption:** Simplified deployment processes make it easier for testers and external developers to engage.
+
+## 1.6. Dependencies
+
+- **Interoperability** with the CATENA‑X standards.
+
+## 1.7. Success Criteria
+
+- **Technology Readiness Level:** Achievement of a Technology Readiness Level (TRL) of 3, as specified in the requirements.
+- **Functional PoC Deployment:** Demonstrated automated, modular installation with reduced manual steps.
+- **Simplified Configuration:** Clear evidence of reduced configuration complexity.
+- **Positive Feedback:** End-user validation from a select group of demo participants and the Tractus-X community.
+- **Documentation Completeness:** Availability of concise deployment and user guides.
+
+## 1.8. Out of Scope
+
+- **Full Production Readiness:** This PoC is not intended to be a production-ready solution.
+- **Core Services Exclusion:** Core services are not part of the Hausanschluss Bundles.
+- **App Provider Role:** The role of App Provider is considered out of scope for this deployment.
+- **Alternative Deployment Techniques:** While the evaluation of alternative deployment methods is acknowledged, the primary
+  focus remains on Kubernetes and HELM-based deployment.
+
+# 2 Requirements Analysis
+
+## 2.1 Assumptions
+
+## 2.2 Requirements Catalog
+
+| ID             | Requirement                                                                                                                                                                                                                                                                                                                                          | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | Deliverables / Acceptance Criteria                                                                                                                                                                                                                                                                                                                                                                                   |
+|----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| [WP-7.1.-D001] | The Hausanschluss Bundle aims to simplify the installation and maintenance of the EDC and other components that together ensure a “Hausanschluss”. A flexible, parameterizable installation package is intended to reduce complexity and make integration more efficient, thereby simplifying participation in Catena‑X for additional participants. | Specification and development of a flexible, parameterizable installation package that reduces the complexity of installing and maintaining the required components for seamless integration into the Catena‑X data space. This package should facilitate updates and new versions, making participation in Catena‑X more efficient and accessible. In doing so, SMEs shall be enabled to participate without high costs or dependency on SaaS providers while maintaining control over their IT infrastructure. | [WP-7.1.-D001] Concept for the Hausanschluss is created                                                                                                                                                                                                                                                                                                                                                              |
+| 7.1.1.1        | The solution concept must define the Capability Bundles structures to be implemented. For each Capability Bundle, the included bundles and their versions are mapped.                                                                                                                                                                                | "The following Capability Bundle structure is implemented:                                                                                                                                                                                                                                                                                                                                                                                                                                                       | The structure of the Capability Bundles for the Enablement Services has been specified. For version R24.12 it is clearly defined which Tractus‑X services and components are assigned to each Capability Bundle                                                                                                                                                                                                      |
+| 7.1.1.2        | Definition of Data Space Roles                                                                                                                                                                                                                                                                                                                       | Data Consumer, Data Provider, Enablement Service Provider                                                                                                                                                                                                                                                                                                                                                                                                                                                        | As part of the target group analysis, the target groups are defined and aligned with the data space roles. <br>Mapping from data space role to target group has been completed. <br>Mapping from target group to data space role has been completed. <br>An assignment of data space roles to Capability Bundles has been made.                                                                                      |
+| 7.1.1.4        | Modularity & Maintainability: No dependencies between Capability Bundles                                                                                                                                                                                                                                                                             | Unique assignment of components and services to a defined Capability Bundle. <br>Each component and service should be assigned to only one Capability Bundle. <br>Dependencies between Capability Bundles are allowed.                                                                                                                                                                                                                                                                                           | Components and Services should only be part of one bundle. <br>Each bundle must be deployable in isolation and can be installed, updated, or removed independently. <br>Capability Bundles must be organized in separate HELM sub‑charts. <br>Circular dependencies between bundles must be avoided.                                                                                                                 |
+| 7.1.1.5        | Modularity & Maintainability: Concept for reducing deployment complexity                                                                                                                                                                                                                                                                             | The system deployment should be optimized to reduce the existing complexity. The goal is to make the provisioning process more efficient, robust, and easier to maintain.                                                                                                                                                                                                                                                                                                                                        | **Simplification of deployment processes:** A reduction of manual configuration steps has been achieved. <br>**Transparency and traceability:** Clearly documented deployment steps are provided. <br>**Improvements of Chart configuration by:** <br>usage of template  <br>reducing configuration options <br>reducing manual steps in the setup                                                                   |
+| 7.1.1.6        | Modularity & Maintainability                                                                                                                                                                                                                                                                                                                         | Charts are published automatically.                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | Charts are published via a publicly accessible charts repository.                                                                                                                                                                                                                                                                                                                                                    |
+| 7.1.1.13       | Solution Concept                                                                                                                                                                                                                                                                                                                                     | Creation of a solution design for the “Hausanschluss” Bundle.                                                                                                                                                                                                                                                                                                                                                                                                                                                    | The solution design for the "Hausanschluss" Bundle is created. <br>The solution design for the "Hausanschluss" Bundle ispublished in the repository: https://github.com/eclipse-tractusx/tractus-x-umbrella.                                                                                                                                                                                                         |
+| 7.1.1.14       | Scalability of Enablement Services                                                                                                                                                                                                                                                                                                                   | Scalability of Enablement Services                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | Developers should be able to deploy an arbitrary number of Enablement Services. <br>Example: Up to 3 EDCs can be provided.                                                                                                                                                                                                                                                                                           |
+| 7.1.1.16       | Interoperability                                                                                                                                                                                                                                                                                                                                     | Interoperability                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | Interoperability with the CATENA‑X standards. <br>This interoperability is documented and traceable.                                                                                                                                                                                                                                                                                                                 |
+| [WP-7.1.-D002] | [WP-7.1.-D002] Target group for the specification is defined.                                                                                                                                                                                                                                                                                        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | [WP-7.1.-D002] Target group for the specification is defined.                                                                                                                                                                                                                                                                                                                                                        |
+| 7.1.2.1        | Target Group Analysis                                                                                                                                                                                                                                                                                                                                | The target group analysis for the "Hausanschluss Bundle"is defined.                                                                                                                                                                                                                                                                                                                                                                                                                                              | The analysis has been conducted. <br>The target group is included in the solution concept <br>To be clarified: What is included in the Hausanschluss and who can operate it in which scenario (OEM, SME, service provider, etc.).                                                                                                                                                                                    |
+| [WP-7.1.-D003] | [WP-7.1.-D003] Decentralized components and services defined                                                                                                                                                                                                                                                                                         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | [WP-7.1.-D003] Decentralized components and services have been defined.                                                                                                                                                                                                                                                                                                                                              |
+| 7.1.3.1        | See [WP-7.1.-D001-AC001]                                                                                                                                                                                                                                                                                                                             |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | See [WP-7.1.-D001-AC001]                                                                                                                                                                                                                                                                                                                                                                                             |
+| [WP-7.1.-D004] | [WP-7.1.-D004] Documentation of the Hausanschluss Bundle is completed                                                                                                                                                                                                                                                                                |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | [WP-7.1.-D004] Documentation of the Hausanschluss Bundle is completed                                                                                                                                                                                                                                                                                                                                                |
+| 7.1.4.1        | Documentation of the Hausanschluss-Bundles                                                                                                                                                                                                                                                                                                           | Usability                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | Documentation is provided that enables an experienced product developer - with knowledge of Helm Charts, Docker, and Vaults - to deploy the chart independently without external help. <br>A troubleshooting and FAQ section is included to support the developer. <br>Prerequisites, skills, and technology requirements are outlined, detailing what a developer must know to perform the deployment autonomously. |
+| 7.1.4.2        | Documentation of the Hausanschluss-Bundles                                                                                                                                                                                                                                                                                                           | Documentation of the Hausanschluss-Bundles is completed.                                                                                                                                                                                                                                                                                                                                                                                                                                                         | Documentation is provided for: <br>Configuration of the defined bundles according to the specified requirements and parameters <br>Integration of the documentation into the Umbrella HELM Charts <br>Integration into the Umbrella HELM Chart to ensure consistent deployment                                                                                                                                       |
+| [WP-7.1.-D005] | [WP-7.1.-D005] Umbrella HELM Charts for the Hausanschluss developed, tested, and documented                                                                                                                                                                                                                                                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | [WP-7.1.-D005] Umbrella HELM Charts for the Hausanschluss have been developed, tested, and documented.                                                                                                                                                                                                                                                                                                               |
+| 7.1.5.1        | Re-activate Umbrella HELM Charts to the latest release state                                                                                                                                                                                                                                                                                         | The Enablement Services components of the Umbrella HELM Charts must be updated to version R24.12. This includes the following upgrades: <br> Upgrade DTR to version R24.12 (#188) <br>Upgrade EDCs to version R24.12 (#193) <br>Update SSI-DIM-Wallet-Stub to version 0.1.8 (#206)                                                                                                                                                                                                                               | The HELM Chart will then contain the updated versions of the components. <br>After the upgrade, the components (DTR, EDCs, SSI‑DIM‑Wallet‑Stub) run stably without functional impairments. <br>The deployment pipeline for the HELM Chart executes successfully <br>Relevant tests & smoke tests (e.g., integration tests) confirm the migration.                                                                    |
+| 7.1.5.2        | Hierarchical structuring and bundling of Enablement Service components in the Umbrella HELM Chart                                                                                                                                                                                                                                                    | The Umbrella HELM Chart should be structured hierarchically so that related Enablement Service components are grouped into bundles. <br>The Umbrella HELM Chart must have a clear hierarchical structure <br> Each Enablement Service component must be assigned to a unique bundle.<br>No circular dependencies between bundles are allowed.                                                                                                                                                                    | The chart is modular and divided into defined bundles. <br>Each bundle can be deployed and maintained independently.                                                                                                                                                                                                                                                                                                 |
+| 7.1.5.3        | Interchangeability of bundle components via “Bring-Your-Own” components                                                                                                                                                                                                                                                                              | Bundle components should be interchangeable through “Bring-Your-Own” components. <br>“Bring your own” is available for every component and means that these components do not have to be delivered by default with the Umbrella Chart but can be provided by the respective users.                                                                                                                                                                                                                               | Bundle components can be interchanged by “Bring-Your-Own” components.                                                                                                                                                                                                                                                                                                                                                |
+| [WP-7.1.-D006] | [WP-7.1.-D006] Product developed according to a Technology Readiness Level (TRL) of 3                                                                                                                                                                                                                                                                |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | [WP-7.1.-D006] The product is developed according to a Technology Readiness Level (TRL) of 3                                                                                                                                                                                                                                                                                                                         |
+| 7.1.6.1        | POC                                                                                                                                                                                                                                                                                                                                                  | Creation of a POC for the "Hausanschluss" Bundle                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | POC implementation is completed. <br>POC has been presented in a demo                                                                                                                                                                                                                                                                                                                                                |
+| 7.1.6.2        | Deployment Strategy                                                                                                                                                                                                                                                                                                                                  | The provisioning of bundles is carried out independently. <br>There must be an option to selectively activate or deactivate bundles.                                                                                                                                                                                                                                                                                                                                                                             | Configuration is managed via HELM values, allowing flexible adaptation according to the environment.                                                                                                                                                                                                                                                                                                                 |
+
+# 3 AS-IS Analysis
+
+## 3.1 People
+
+### 3.1.1 Target Group Analysis
+
+See "4.1.1 To-be Target Group Analysis" below. No deviations between As-is and To-be target groups have been identified.
+
+## 3.2 Process
+
+### 3.2.1 Use Case View (high-level)
+
+Umbrella Chart is intended for the following Use Cases:
+
+| Actor             | Use case                                                                                             |
+|-------------------|------------------------------------------------------------------------------------------------------|
+| Product Developer | Sandbox Environments: Create local environments to evaluate and experiment with Catena-X components. |
+| Product Developer | Development: Provide a unified setup for contributors and developers working on Tractus-X projects.  |
+| Product Tester    | Testing: Run end-to-end tests for Catena-X services.                                                 |
+| Product Manager   | Evaluate the dataspace to assess if their product can be used within Catena-X.                       |
+
+## 3.4 System
+
+### 3.4.1 Context Delimitation
+
+#### Existing Umbrella Chart Structure
+
+````mermaid
+flowchart
+    subgraph "Umbrella Chart"
+        ChartYaml["Chart.yaml"]
+        subgraph charts
+            Portal["Portal"]
+            CentralIdp["CentralIdp"]
+            DiscoveryFinder["Discovery Finder"]
+            SDFactory["SD-Factory"]
+            SSICredentialIssuer["SSI Credential Issuer"]
+            SemanticHub["Semantic Hub"]
+            BPDM["BPDM"]
+            DataConsumer["Data Consumer"]
+            DataProvider["Data Provider"]
+            BDRS["BDRS"]
+            SSIWalletStub["SSI Wallet Stub"]
+        end
+        subgraph "tx-data-provider"
+            EDC["EDC"]
+            DTR["DTR"]
+            SubmodelServer["Submodel Server"]
+        end
+    end
+
+    ChartYaml --> Portal
+    ChartYaml --> CentralIdp
path: docs/concept/TAP7.1-solution-design.md
user: login: CDiezRodriguez
body: ```suggestion
    ChartYaml --> CentralIdp
    ChartYaml --> SharedIdp
```
created_at: 2025-04-03T10:06:33Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,516 @@
+# Solution Design "Hausanschluss" Bundle Concept
+
+# 1 Business Case
+
+## 1.1 Executive Summary
+
+The "Hausanschluss" Bundle aims to simplify the installation of the enablement services Eclipse Dataspace
+Connector (EDC), Digital Twin Registry (DTR), and their supporting components. By developing a flexible, parameterizable
+installation package, the project seeks to reduce deployment complexity and lower barriers to participation in the
+Catena‑X data space. This bundle will enable independent component updates and support a modular "bring your own"
+approach, ultimately fostering a more efficient and accessible ecosystem for diverse participants—such as testers,
+external product developers, product testers, and small and medium-sized enterprises.
+
+## 1.2 Business Need
+
+Current deployment methods for data space integration are complex and require significant manual effort. This PoC
+addresses the need to:
+
+- **Reduce Complexity:** Simplify the deployment topology by bundling components into capabilities.
+- **Automate Deployment:** Provide an automated installation package using Kubernetes and HELM.
+- **Minimize Configuration Overhead:** Streamline the integration process by providing pre-configured bundles that require only minimal manual parameter adjustments.
+- **Extend Documentation:** Provide a detailed documentation tailored to the target groups.
+- **Enable Extension:** Design the system to allow the seamless addition of new components or capabilities.
+
+## 1.3 Objectives
+
+- **Simplify Deployment and Maintenance:** Develop an installation package that minimizes manual configuration through
+  automation.
+- **Ensure Modularity:** Structure the bundle so that components can be independently installed, updated, or replaced
+  without affecting other services.
+- **Facilitate Flexibility:** Implement a "bring your own" model for key components, such as EDC, PostgreSQL, and HashiCorp
+  Vault, to allow tailored deployments that meet specific needs.
+- **Increase Accessibility**: Lower entry barriers for new participants by reducing technical complexity and operational
+  dependencies.
+- **Scalability:** Structure the bundles so that they can be deployed multiple times.
+
+## 1.4 Expected Deliverables
+
+- **PoC Documentation:** A concept and architecture overview highlighting the modular design.
+- **Modular Installation Package:** A set of HELM charts for deploying the enablement service bundles:
+    - **Dataspace Connector:** Including the Eclipse Dataspace Connector, EDC PostgreSQL, and HashiCorp Vault.
+    - **Digital Twin Bundle:** Featuring components such as the Decentral DT Registry (with “bring your own” PostgreSQL)
+    - **Data Persitence Layer Bundle:** Including a simple Submodel Server to store semantic data.
+    - **Identity Wallet Bundle:** Covering the Identity Wallet functionality.
+- **Demonstration Environment:** A test deployment showcasing reduced complexity and improved efficiency.
+- **Basic User Guide:** Instructions on how to deploy and update the PoC bundle.
+
+## 1.5 Benefits
+
+- **Operational Efficiency:** Faster and more reliable deployments with less manual work.
+- **Scalability:** A modular design that can be scaled or adapted for future full-scale deployments.
+- **Ease of Adoption:** Simplified deployment processes make it easier for testers and external developers to engage.
+
+## 1.6. Dependencies
+
+- **Interoperability** with the CATENA‑X standards.
+
+## 1.7. Success Criteria
+
+- **Technology Readiness Level:** Achievement of a Technology Readiness Level (TRL) of 3, as specified in the requirements.
+- **Functional PoC Deployment:** Demonstrated automated, modular installation with reduced manual steps.
+- **Simplified Configuration:** Clear evidence of reduced configuration complexity.
+- **Positive Feedback:** End-user validation from a select group of demo participants and the Tractus-X community.
+- **Documentation Completeness:** Availability of concise deployment and user guides.
+
+## 1.8. Out of Scope
+
+- **Full Production Readiness:** This PoC is not intended to be a production-ready solution.
+- **Core Services Exclusion:** Core services are not part of the Hausanschluss Bundles.
+- **App Provider Role:** The role of App Provider is considered out of scope for this deployment.
+- **Alternative Deployment Techniques:** While the evaluation of alternative deployment methods is acknowledged, the primary
+  focus remains on Kubernetes and HELM-based deployment.
+
+# 2 Requirements Analysis
+
+## 2.1 Assumptions
+
+## 2.2 Requirements Catalog
+
+| ID             | Requirement                                                                                                                                                                                                                                                                                                                                          | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | Deliverables / Acceptance Criteria                                                                                                                                                                                                                                                                                                                                                                                   |
+|----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| [WP-7.1.-D001] | The Hausanschluss Bundle aims to simplify the installation and maintenance of the EDC and other components that together ensure a “Hausanschluss”. A flexible, parameterizable installation package is intended to reduce complexity and make integration more efficient, thereby simplifying participation in Catena‑X for additional participants. | Specification and development of a flexible, parameterizable installation package that reduces the complexity of installing and maintaining the required components for seamless integration into the Catena‑X data space. This package should facilitate updates and new versions, making participation in Catena‑X more efficient and accessible. In doing so, SMEs shall be enabled to participate without high costs or dependency on SaaS providers while maintaining control over their IT infrastructure. | [WP-7.1.-D001] Concept for the Hausanschluss is created                                                                                                                                                                                                                                                                                                                                                              |
+| 7.1.1.1        | The solution concept must define the Capability Bundles structures to be implemented. For each Capability Bundle, the included bundles and their versions are mapped.                                                                                                                                                                                | "The following Capability Bundle structure is implemented:                                                                                                                                                                                                                                                                                                                                                                                                                                                       | The structure of the Capability Bundles for the Enablement Services has been specified. For version R24.12 it is clearly defined which Tractus‑X services and components are assigned to each Capability Bundle                                                                                                                                                                                                      |
+| 7.1.1.2        | Definition of Data Space Roles                                                                                                                                                                                                                                                                                                                       | Data Consumer, Data Provider, Enablement Service Provider                                                                                                                                                                                                                                                                                                                                                                                                                                                        | As part of the target group analysis, the target groups are defined and aligned with the data space roles. <br>Mapping from data space role to target group has been completed. <br>Mapping from target group to data space role has been completed. <br>An assignment of data space roles to Capability Bundles has been made.                                                                                      |
+| 7.1.1.4        | Modularity & Maintainability: No dependencies between Capability Bundles                                                                                                                                                                                                                                                                             | Unique assignment of components and services to a defined Capability Bundle. <br>Each component and service should be assigned to only one Capability Bundle. <br>Dependencies between Capability Bundles are allowed.                                                                                                                                                                                                                                                                                           | Components and Services should only be part of one bundle. <br>Each bundle must be deployable in isolation and can be installed, updated, or removed independently. <br>Capability Bundles must be organized in separate HELM sub‑charts. <br>Circular dependencies between bundles must be avoided.                                                                                                                 |
path: docs/concept/TAP7.1-solution-design.md
user: login: mgarciaLKS
body: Maybe I'm getting it wrong but, the description states that each component should be uniquely assigned to one bundle; however, the text later notes “Dependencies between Capability Bundles are allowed.” Is it correct?
created_at: 2025-04-03T10:08:33Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,516 @@
+# Solution Design "Hausanschluss" Bundle Concept
+
+# 1 Business Case
+
+## 1.1 Executive Summary
+
+The "Hausanschluss" Bundle aims to simplify the installation of the enablement services Eclipse Dataspace
+Connector (EDC), Digital Twin Registry (DTR), and their supporting components. By developing a flexible, parameterizable
+installation package, the project seeks to reduce deployment complexity and lower barriers to participation in the
+Catena‑X data space. This bundle will enable independent component updates and support a modular "bring your own"
+approach, ultimately fostering a more efficient and accessible ecosystem for diverse participants—such as testers,
+external product developers, product testers, and small and medium-sized enterprises.
+
+## 1.2 Business Need
+
+Current deployment methods for data space integration are complex and require significant manual effort. This PoC
+addresses the need to:
+
+- **Reduce Complexity:** Simplify the deployment topology by bundling components into capabilities.
+- **Automate Deployment:** Provide an automated installation package using Kubernetes and HELM.
+- **Minimize Configuration Overhead:** Streamline the integration process by providing pre-configured bundles that require only minimal manual parameter adjustments.
+- **Extend Documentation:** Provide a detailed documentation tailored to the target groups.
+- **Enable Extension:** Design the system to allow the seamless addition of new components or capabilities.
+
+## 1.3 Objectives
+
+- **Simplify Deployment and Maintenance:** Develop an installation package that minimizes manual configuration through
+  automation.
+- **Ensure Modularity:** Structure the bundle so that components can be independently installed, updated, or replaced
+  without affecting other services.
+- **Facilitate Flexibility:** Implement a "bring your own" model for key components, such as EDC, PostgreSQL, and HashiCorp
+  Vault, to allow tailored deployments that meet specific needs.
+- **Increase Accessibility**: Lower entry barriers for new participants by reducing technical complexity and operational
+  dependencies.
+- **Scalability:** Structure the bundles so that they can be deployed multiple times.
+
+## 1.4 Expected Deliverables
+
+- **PoC Documentation:** A concept and architecture overview highlighting the modular design.
+- **Modular Installation Package:** A set of HELM charts for deploying the enablement service bundles:
+    - **Dataspace Connector:** Including the Eclipse Dataspace Connector, EDC PostgreSQL, and HashiCorp Vault.
+    - **Digital Twin Bundle:** Featuring components such as the Decentral DT Registry (with “bring your own” PostgreSQL)
+    - **Data Persitence Layer Bundle:** Including a simple Submodel Server to store semantic data.
+    - **Identity Wallet Bundle:** Covering the Identity Wallet functionality.
+- **Demonstration Environment:** A test deployment showcasing reduced complexity and improved efficiency.
+- **Basic User Guide:** Instructions on how to deploy and update the PoC bundle.
+
+## 1.5 Benefits
+
+- **Operational Efficiency:** Faster and more reliable deployments with less manual work.
+- **Scalability:** A modular design that can be scaled or adapted for future full-scale deployments.
+- **Ease of Adoption:** Simplified deployment processes make it easier for testers and external developers to engage.
+
+## 1.6. Dependencies
+
+- **Interoperability** with the CATENA‑X standards.
+
+## 1.7. Success Criteria
+
+- **Technology Readiness Level:** Achievement of a Technology Readiness Level (TRL) of 3, as specified in the requirements.
+- **Functional PoC Deployment:** Demonstrated automated, modular installation with reduced manual steps.
+- **Simplified Configuration:** Clear evidence of reduced configuration complexity.
+- **Positive Feedback:** End-user validation from a select group of demo participants and the Tractus-X community.
+- **Documentation Completeness:** Availability of concise deployment and user guides.
+
+## 1.8. Out of Scope
+
+- **Full Production Readiness:** This PoC is not intended to be a production-ready solution.
+- **Core Services Exclusion:** Core services are not part of the Hausanschluss Bundles.
+- **App Provider Role:** The role of App Provider is considered out of scope for this deployment.
+- **Alternative Deployment Techniques:** While the evaluation of alternative deployment methods is acknowledged, the primary
+  focus remains on Kubernetes and HELM-based deployment.
+
+# 2 Requirements Analysis
+
+## 2.1 Assumptions
+
+## 2.2 Requirements Catalog
+
+| ID             | Requirement                                                                                                                                                                                                                                                                                                                                          | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | Deliverables / Acceptance Criteria                                                                                                                                                                                                                                                                                                                                                                                   |
+|----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| [WP-7.1.-D001] | The Hausanschluss Bundle aims to simplify the installation and maintenance of the EDC and other components that together ensure a “Hausanschluss”. A flexible, parameterizable installation package is intended to reduce complexity and make integration more efficient, thereby simplifying participation in Catena‑X for additional participants. | Specification and development of a flexible, parameterizable installation package that reduces the complexity of installing and maintaining the required components for seamless integration into the Catena‑X data space. This package should facilitate updates and new versions, making participation in Catena‑X more efficient and accessible. In doing so, SMEs shall be enabled to participate without high costs or dependency on SaaS providers while maintaining control over their IT infrastructure. | [WP-7.1.-D001] Concept for the Hausanschluss is created                                                                                                                                                                                                                                                                                                                                                              |
+| 7.1.1.1        | The solution concept must define the Capability Bundles structures to be implemented. For each Capability Bundle, the included bundles and their versions are mapped.                                                                                                                                                                                | "The following Capability Bundle structure is implemented:                                                                                                                                                                                                                                                                                                                                                                                                                                                       | The structure of the Capability Bundles for the Enablement Services has been specified. For version R24.12 it is clearly defined which Tractus‑X services and components are assigned to each Capability Bundle                                                                                                                                                                                                      |
+| 7.1.1.2        | Definition of Data Space Roles                                                                                                                                                                                                                                                                                                                       | Data Consumer, Data Provider, Enablement Service Provider                                                                                                                                                                                                                                                                                                                                                                                                                                                        | As part of the target group analysis, the target groups are defined and aligned with the data space roles. <br>Mapping from data space role to target group has been completed. <br>Mapping from target group to data space role has been completed. <br>An assignment of data space roles to Capability Bundles has been made.                                                                                      |
+| 7.1.1.4        | Modularity & Maintainability: No dependencies between Capability Bundles                                                                                                                                                                                                                                                                             | Unique assignment of components and services to a defined Capability Bundle. <br>Each component and service should be assigned to only one Capability Bundle. <br>Dependencies between Capability Bundles are allowed.                                                                                                                                                                                                                                                                                           | Components and Services should only be part of one bundle. <br>Each bundle must be deployable in isolation and can be installed, updated, or removed independently. <br>Capability Bundles must be organized in separate HELM sub‑charts. <br>Circular dependencies between bundles must be avoided.                                                                                                                 |
+| 7.1.1.5        | Modularity & Maintainability: Concept for reducing deployment complexity                                                                                                                                                                                                                                                                             | The system deployment should be optimized to reduce the existing complexity. The goal is to make the provisioning process more efficient, robust, and easier to maintain.                                                                                                                                                                                                                                                                                                                                        | **Simplification of deployment processes:** A reduction of manual configuration steps has been achieved. <br>**Transparency and traceability:** Clearly documented deployment steps are provided. <br>**Improvements of Chart configuration by:** <br>usage of template  <br>reducing configuration options <br>reducing manual steps in the setup                                                                   |
+| 7.1.1.6        | Modularity & Maintainability                                                                                                                                                                                                                                                                                                                         | Charts are published automatically.                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | Charts are published via a publicly accessible charts repository.                                                                                                                                                                                                                                                                                                                                                    |
+| 7.1.1.13       | Solution Concept                                                                                                                                                                                                                                                                                                                                     | Creation of a solution design for the “Hausanschluss” Bundle.                                                                                                                                                                                                                                                                                                                                                                                                                                                    | The solution design for the "Hausanschluss" Bundle is created. <br>The solution design for the "Hausanschluss" Bundle ispublished in the repository: https://github.com/eclipse-tractusx/tractus-x-umbrella.                                                                                                                                                                                                         |
+| 7.1.1.14       | Scalability of Enablement Services                                                                                                                                                                                                                                                                                                                   | Scalability of Enablement Services                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | Developers should be able to deploy an arbitrary number of Enablement Services. <br>Example: Up to 3 EDCs can be provided.                                                                                                                                                                                                                                                                                           |
+| 7.1.1.16       | Interoperability                                                                                                                                                                                                                                                                                                                                     | Interoperability                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | Interoperability with the CATENA‑X standards. <br>This interoperability is documented and traceable.                                                                                                                                                                                                                                                                                                                 |
+| [WP-7.1.-D002] | [WP-7.1.-D002] Target group for the specification is defined.                                                                                                                                                                                                                                                                                        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | [WP-7.1.-D002] Target group for the specification is defined.                                                                                                                                                                                                                                                                                                                                                        |
+| 7.1.2.1        | Target Group Analysis                                                                                                                                                                                                                                                                                                                                | The target group analysis for the "Hausanschluss Bundle"is defined.                                                                                                                                                                                                                                                                                                                                                                                                                                              | The analysis has been conducted. <br>The target group is included in the solution concept <br>To be clarified: What is included in the Hausanschluss and who can operate it in which scenario (OEM, SME, service provider, etc.).                                                                                                                                                                                    |
+| [WP-7.1.-D003] | [WP-7.1.-D003] Decentralized components and services defined                                                                                                                                                                                                                                                                                         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | [WP-7.1.-D003] Decentralized components and services have been defined.                                                                                                                                                                                                                                                                                                                                              |
+| 7.1.3.1        | See [WP-7.1.-D001-AC001]                                                                                                                                                                                                                                                                                                                             |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | See [WP-7.1.-D001-AC001]                                                                                                                                                                                                                                                                                                                                                                                             |
+| [WP-7.1.-D004] | [WP-7.1.-D004] Documentation of the Hausanschluss Bundle is completed                                                                                                                                                                                                                                                                                |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | [WP-7.1.-D004] Documentation of the Hausanschluss Bundle is completed                                                                                                                                                                                                                                                                                                                                                |
+| 7.1.4.1        | Documentation of the Hausanschluss-Bundles                                                                                                                                                                                                                                                                                                           | Usability                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | Documentation is provided that enables an experienced product developer - with knowledge of Helm Charts, Docker, and Vaults - to deploy the chart independently without external help. <br>A troubleshooting and FAQ section is included to support the developer. <br>Prerequisites, skills, and technology requirements are outlined, detailing what a developer must know to perform the deployment autonomously. |
+| 7.1.4.2        | Documentation of the Hausanschluss-Bundles                                                                                                                                                                                                                                                                                                           | Documentation of the Hausanschluss-Bundles is completed.                                                                                                                                                                                                                                                                                                                                                                                                                                                         | Documentation is provided for: <br>Configuration of the defined bundles according to the specified requirements and parameters <br>Integration of the documentation into the Umbrella HELM Charts <br>Integration into the Umbrella HELM Chart to ensure consistent deployment                                                                                                                                       |
+| [WP-7.1.-D005] | [WP-7.1.-D005] Umbrella HELM Charts for the Hausanschluss developed, tested, and documented                                                                                                                                                                                                                                                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | [WP-7.1.-D005] Umbrella HELM Charts for the Hausanschluss have been developed, tested, and documented.                                                                                                                                                                                                                                                                                                               |
+| 7.1.5.1        | Re-activate Umbrella HELM Charts to the latest release state                                                                                                                                                                                                                                                                                         | The Enablement Services components of the Umbrella HELM Charts must be updated to version R24.12. This includes the following upgrades: <br> Upgrade DTR to version R24.12 (#188) <br>Upgrade EDCs to version R24.12 (#193) <br>Update SSI-DIM-Wallet-Stub to version 0.1.8 (#206)                                                                                                                                                                                                                               | The HELM Chart will then contain the updated versions of the components. <br>After the upgrade, the components (DTR, EDCs, SSI‑DIM‑Wallet‑Stub) run stably without functional impairments. <br>The deployment pipeline for the HELM Chart executes successfully <br>Relevant tests & smoke tests (e.g., integration tests) confirm the migration.                                                                    |
+| 7.1.5.2        | Hierarchical structuring and bundling of Enablement Service components in the Umbrella HELM Chart                                                                                                                                                                                                                                                    | The Umbrella HELM Chart should be structured hierarchically so that related Enablement Service components are grouped into bundles. <br>The Umbrella HELM Chart must have a clear hierarchical structure <br> Each Enablement Service component must be assigned to a unique bundle.<br>No circular dependencies between bundles are allowed.                                                                                                                                                                    | The chart is modular and divided into defined bundles. <br>Each bundle can be deployed and maintained independently.                                                                                                                                                                                                                                                                                                 |
+| 7.1.5.3        | Interchangeability of bundle components via “Bring-Your-Own” components                                                                                                                                                                                                                                                                              | Bundle components should be interchangeable through “Bring-Your-Own” components. <br>“Bring your own” is available for every component and means that these components do not have to be delivered by default with the Umbrella Chart but can be provided by the respective users.                                                                                                                                                                                                                               | Bundle components can be interchanged by “Bring-Your-Own” components.                                                                                                                                                                                                                                                                                                                                                |
+| [WP-7.1.-D006] | [WP-7.1.-D006] Product developed according to a Technology Readiness Level (TRL) of 3                                                                                                                                                                                                                                                                |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | [WP-7.1.-D006] The product is developed according to a Technology Readiness Level (TRL) of 3                                                                                                                                                                                                                                                                                                                         |
+| 7.1.6.1        | POC                                                                                                                                                                                                                                                                                                                                                  | Creation of a POC for the "Hausanschluss" Bundle                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | POC implementation is completed. <br>POC has been presented in a demo                                                                                                                                                                                                                                                                                                                                                |
+| 7.1.6.2        | Deployment Strategy                                                                                                                                                                                                                                                                                                                                  | The provisioning of bundles is carried out independently. <br>There must be an option to selectively activate or deactivate bundles.                                                                                                                                                                                                                                                                                                                                                                             | Configuration is managed via HELM values, allowing flexible adaptation according to the environment.                                                                                                                                                                                                                                                                                                                 |
+
+# 3 AS-IS Analysis
+
+## 3.1 People
+
+### 3.1.1 Target Group Analysis
+
+See "4.1.1 To-be Target Group Analysis" below. No deviations between As-is and To-be target groups have been identified.
+
+## 3.2 Process
+
+### 3.2.1 Use Case View (high-level)
+
+Umbrella Chart is intended for the following Use Cases:
+
+| Actor             | Use case                                                                                             |
+|-------------------|------------------------------------------------------------------------------------------------------|
+| Product Developer | Sandbox Environments: Create local environments to evaluate and experiment with Catena-X components. |
+| Product Developer | Development: Provide a unified setup for contributors and developers working on Tractus-X projects.  |
+| Product Tester    | Testing: Run end-to-end tests for Catena-X services.                                                 |
+| Product Manager   | Evaluate the dataspace to assess if their product can be used within Catena-X.                       |
+
+## 3.4 System
+
+### 3.4.1 Context Delimitation
+
+#### Existing Umbrella Chart Structure
+
+````mermaid
+flowchart
+    subgraph "Umbrella Chart"
+        ChartYaml["Chart.yaml"]
+        subgraph charts
+            Portal["Portal"]
+            CentralIdp["CentralIdp"]
+            DiscoveryFinder["Discovery Finder"]
+            SDFactory["SD-Factory"]
+            SSICredentialIssuer["SSI Credential Issuer"]
+            SemanticHub["Semantic Hub"]
+            BPDM["BPDM"]
+            DataConsumer["Data Consumer"]
+            DataProvider["Data Provider"]
+            BDRS["BDRS"]
+            SSIWalletStub["SSI Wallet Stub"]
+        end
+        subgraph "tx-data-provider"
+            EDC["EDC"]
+            DTR["DTR"]
+            SubmodelServer["Submodel Server"]
+        end
+    end
+
+    ChartYaml --> Portal
+    ChartYaml --> CentralIdp
+    ChartYaml --> DiscoveryFinder
+    ChartYaml --> SDFactory
+    ChartYaml --> SSICredentialIssuer
+    ChartYaml --> SemanticHub
+    ChartYaml --> BPDM
+    ChartYaml --> DataConsumer
+    ChartYaml --> DataProvider
+    ChartYaml --> BDRS
+    ChartYaml --> SSIWalletStub
+    DataConsumer --> EDC
+    DataProvider --> EDC
+    DataProvider --> DTR
+    DataProvider --> SubmodelServer
+````
+
+# 4 TO-BE Design
+
+## 4.1 People
+
+### 4.1.1 Target Group Analysis
+
+Overall data space roles: https://catena-x.net/en/1/catena-x-introduce-implement/how-to-operate-catena-x
path: docs/concept/TAP7.1-solution-design.md
user: login: CDiezRodriguez
body: Currently, the URL directs to a 404 Not Found page.
![image](https://github.com/user-attachments/assets/aa84a6a2-7e7d-4fcb-a1cc-d02705034ac8)

created_at: 2025-04-03T10:08:48Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,516 @@
+# Solution Design "Hausanschluss" Bundle Concept
+
+# 1 Business Case
+
+## 1.1 Executive Summary
+
+The "Hausanschluss" Bundle aims to simplify the installation of the enablement services Eclipse Dataspace
+Connector (EDC), Digital Twin Registry (DTR), and their supporting components. By developing a flexible, parameterizable
+installation package, the project seeks to reduce deployment complexity and lower barriers to participation in the
+Catena‑X data space. This bundle will enable independent component updates and support a modular "bring your own"
+approach, ultimately fostering a more efficient and accessible ecosystem for diverse participants—such as testers,
+external product developers, product testers, and small and medium-sized enterprises.
+
+## 1.2 Business Need
+
+Current deployment methods for data space integration are complex and require significant manual effort. This PoC
+addresses the need to:
+
+- **Reduce Complexity:** Simplify the deployment topology by bundling components into capabilities.
+- **Automate Deployment:** Provide an automated installation package using Kubernetes and HELM.
+- **Minimize Configuration Overhead:** Streamline the integration process by providing pre-configured bundles that require only minimal manual parameter adjustments.
+- **Extend Documentation:** Provide a detailed documentation tailored to the target groups.
+- **Enable Extension:** Design the system to allow the seamless addition of new components or capabilities.
+
+## 1.3 Objectives
+
+- **Simplify Deployment and Maintenance:** Develop an installation package that minimizes manual configuration through
+  automation.
+- **Ensure Modularity:** Structure the bundle so that components can be independently installed, updated, or replaced
+  without affecting other services.
+- **Facilitate Flexibility:** Implement a "bring your own" model for key components, such as EDC, PostgreSQL, and HashiCorp
+  Vault, to allow tailored deployments that meet specific needs.
+- **Increase Accessibility**: Lower entry barriers for new participants by reducing technical complexity and operational
+  dependencies.
+- **Scalability:** Structure the bundles so that they can be deployed multiple times.
+
+## 1.4 Expected Deliverables
+
+- **PoC Documentation:** A concept and architecture overview highlighting the modular design.
+- **Modular Installation Package:** A set of HELM charts for deploying the enablement service bundles:
+    - **Dataspace Connector:** Including the Eclipse Dataspace Connector, EDC PostgreSQL, and HashiCorp Vault.
+    - **Digital Twin Bundle:** Featuring components such as the Decentral DT Registry (with “bring your own” PostgreSQL)
+    - **Data Persitence Layer Bundle:** Including a simple Submodel Server to store semantic data.
+    - **Identity Wallet Bundle:** Covering the Identity Wallet functionality.
+- **Demonstration Environment:** A test deployment showcasing reduced complexity and improved efficiency.
+- **Basic User Guide:** Instructions on how to deploy and update the PoC bundle.
+
+## 1.5 Benefits
+
+- **Operational Efficiency:** Faster and more reliable deployments with less manual work.
+- **Scalability:** A modular design that can be scaled or adapted for future full-scale deployments.
+- **Ease of Adoption:** Simplified deployment processes make it easier for testers and external developers to engage.
+
+## 1.6. Dependencies
+
+- **Interoperability** with the CATENA‑X standards.
+
+## 1.7. Success Criteria
+
+- **Technology Readiness Level:** Achievement of a Technology Readiness Level (TRL) of 3, as specified in the requirements.
+- **Functional PoC Deployment:** Demonstrated automated, modular installation with reduced manual steps.
+- **Simplified Configuration:** Clear evidence of reduced configuration complexity.
+- **Positive Feedback:** End-user validation from a select group of demo participants and the Tractus-X community.
+- **Documentation Completeness:** Availability of concise deployment and user guides.
+
+## 1.8. Out of Scope
+
+- **Full Production Readiness:** This PoC is not intended to be a production-ready solution.
+- **Core Services Exclusion:** Core services are not part of the Hausanschluss Bundles.
+- **App Provider Role:** The role of App Provider is considered out of scope for this deployment.
+- **Alternative Deployment Techniques:** While the evaluation of alternative deployment methods is acknowledged, the primary
+  focus remains on Kubernetes and HELM-based deployment.
+
+# 2 Requirements Analysis
+
+## 2.1 Assumptions
+
+## 2.2 Requirements Catalog
+
+| ID             | Requirement                                                                                                                                                                                                                                                                                                                                          | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | Deliverables / Acceptance Criteria                                                                                                                                                                                                                                                                                                                                                                                   |
+|----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| [WP-7.1.-D001] | The Hausanschluss Bundle aims to simplify the installation and maintenance of the EDC and other components that together ensure a “Hausanschluss”. A flexible, parameterizable installation package is intended to reduce complexity and make integration more efficient, thereby simplifying participation in Catena‑X for additional participants. | Specification and development of a flexible, parameterizable installation package that reduces the complexity of installing and maintaining the required components for seamless integration into the Catena‑X data space. This package should facilitate updates and new versions, making participation in Catena‑X more efficient and accessible. In doing so, SMEs shall be enabled to participate without high costs or dependency on SaaS providers while maintaining control over their IT infrastructure. | [WP-7.1.-D001] Concept for the Hausanschluss is created                                                                                                                                                                                                                                                                                                                                                              |
+| 7.1.1.1        | The solution concept must define the Capability Bundles structures to be implemented. For each Capability Bundle, the included bundles and their versions are mapped.                                                                                                                                                                                | "The following Capability Bundle structure is implemented:                                                                                                                                                                                                                                                                                                                                                                                                                                                       | The structure of the Capability Bundles for the Enablement Services has been specified. For version R24.12 it is clearly defined which Tractus‑X services and components are assigned to each Capability Bundle                                                                                                                                                                                                      |
+| 7.1.1.2        | Definition of Data Space Roles                                                                                                                                                                                                                                                                                                                       | Data Consumer, Data Provider, Enablement Service Provider                                                                                                                                                                                                                                                                                                                                                                                                                                                        | As part of the target group analysis, the target groups are defined and aligned with the data space roles. <br>Mapping from data space role to target group has been completed. <br>Mapping from target group to data space role has been completed. <br>An assignment of data space roles to Capability Bundles has been made.                                                                                      |
+| 7.1.1.4        | Modularity & Maintainability: No dependencies between Capability Bundles                                                                                                                                                                                                                                                                             | Unique assignment of components and services to a defined Capability Bundle. <br>Each component and service should be assigned to only one Capability Bundle. <br>Dependencies between Capability Bundles are allowed.                                                                                                                                                                                                                                                                                           | Components and Services should only be part of one bundle. <br>Each bundle must be deployable in isolation and can be installed, updated, or removed independently. <br>Capability Bundles must be organized in separate HELM sub‑charts. <br>Circular dependencies between bundles must be avoided.                                                                                                                 |
+| 7.1.1.5        | Modularity & Maintainability: Concept for reducing deployment complexity                                                                                                                                                                                                                                                                             | The system deployment should be optimized to reduce the existing complexity. The goal is to make the provisioning process more efficient, robust, and easier to maintain.                                                                                                                                                                                                                                                                                                                                        | **Simplification of deployment processes:** A reduction of manual configuration steps has been achieved. <br>**Transparency and traceability:** Clearly documented deployment steps are provided. <br>**Improvements of Chart configuration by:** <br>usage of template  <br>reducing configuration options <br>reducing manual steps in the setup                                                                   |
+| 7.1.1.6        | Modularity & Maintainability                                                                                                                                                                                                                                                                                                                         | Charts are published automatically.                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | Charts are published via a publicly accessible charts repository.                                                                                                                                                                                                                                                                                                                                                    |
+| 7.1.1.13       | Solution Concept                                                                                                                                                                                                                                                                                                                                     | Creation of a solution design for the “Hausanschluss” Bundle.                                                                                                                                                                                                                                                                                                                                                                                                                                                    | The solution design for the "Hausanschluss" Bundle is created. <br>The solution design for the "Hausanschluss" Bundle ispublished in the repository: https://github.com/eclipse-tractusx/tractus-x-umbrella.                                                                                                                                                                                                         |
+| 7.1.1.14       | Scalability of Enablement Services                                                                                                                                                                                                                                                                                                                   | Scalability of Enablement Services                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | Developers should be able to deploy an arbitrary number of Enablement Services. <br>Example: Up to 3 EDCs can be provided.                                                                                                                                                                                                                                                                                           |
+| 7.1.1.16       | Interoperability                                                                                                                                                                                                                                                                                                                                     | Interoperability                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | Interoperability with the CATENA‑X standards. <br>This interoperability is documented and traceable.                                                                                                                                                                                                                                                                                                                 |
+| [WP-7.1.-D002] | [WP-7.1.-D002] Target group for the specification is defined.                                                                                                                                                                                                                                                                                        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | [WP-7.1.-D002] Target group for the specification is defined.                                                                                                                                                                                                                                                                                                                                                        |
+| 7.1.2.1        | Target Group Analysis                                                                                                                                                                                                                                                                                                                                | The target group analysis for the "Hausanschluss Bundle"is defined.                                                                                                                                                                                                                                                                                                                                                                                                                                              | The analysis has been conducted. <br>The target group is included in the solution concept <br>To be clarified: What is included in the Hausanschluss and who can operate it in which scenario (OEM, SME, service provider, etc.).                                                                                                                                                                                    |
+| [WP-7.1.-D003] | [WP-7.1.-D003] Decentralized components and services defined                                                                                                                                                                                                                                                                                         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | [WP-7.1.-D003] Decentralized components and services have been defined.                                                                                                                                                                                                                                                                                                                                              |
+| 7.1.3.1        | See [WP-7.1.-D001-AC001]                                                                                                                                                                                                                                                                                                                             |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | See [WP-7.1.-D001-AC001]                                                                                                                                                                                                                                                                                                                                                                                             |
+| [WP-7.1.-D004] | [WP-7.1.-D004] Documentation of the Hausanschluss Bundle is completed                                                                                                                                                                                                                                                                                |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | [WP-7.1.-D004] Documentation of the Hausanschluss Bundle is completed                                                                                                                                                                                                                                                                                                                                                |
+| 7.1.4.1        | Documentation of the Hausanschluss-Bundles                                                                                                                                                                                                                                                                                                           | Usability                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | Documentation is provided that enables an experienced product developer - with knowledge of Helm Charts, Docker, and Vaults - to deploy the chart independently without external help. <br>A troubleshooting and FAQ section is included to support the developer. <br>Prerequisites, skills, and technology requirements are outlined, detailing what a developer must know to perform the deployment autonomously. |
+| 7.1.4.2        | Documentation of the Hausanschluss-Bundles                                                                                                                                                                                                                                                                                                           | Documentation of the Hausanschluss-Bundles is completed.                                                                                                                                                                                                                                                                                                                                                                                                                                                         | Documentation is provided for: <br>Configuration of the defined bundles according to the specified requirements and parameters <br>Integration of the documentation into the Umbrella HELM Charts <br>Integration into the Umbrella HELM Chart to ensure consistent deployment                                                                                                                                       |
+| [WP-7.1.-D005] | [WP-7.1.-D005] Umbrella HELM Charts for the Hausanschluss developed, tested, and documented                                                                                                                                                                                                                                                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | [WP-7.1.-D005] Umbrella HELM Charts for the Hausanschluss have been developed, tested, and documented.                                                                                                                                                                                                                                                                                                               |
+| 7.1.5.1        | Re-activate Umbrella HELM Charts to the latest release state                                                                                                                                                                                                                                                                                         | The Enablement Services components of the Umbrella HELM Charts must be updated to version R24.12. This includes the following upgrades: <br> Upgrade DTR to version R24.12 (#188) <br>Upgrade EDCs to version R24.12 (#193) <br>Update SSI-DIM-Wallet-Stub to version 0.1.8 (#206)                                                                                                                                                                                                                               | The HELM Chart will then contain the updated versions of the components. <br>After the upgrade, the components (DTR, EDCs, SSI‑DIM‑Wallet‑Stub) run stably without functional impairments. <br>The deployment pipeline for the HELM Chart executes successfully <br>Relevant tests & smoke tests (e.g., integration tests) confirm the migration.                                                                    |
+| 7.1.5.2        | Hierarchical structuring and bundling of Enablement Service components in the Umbrella HELM Chart                                                                                                                                                                                                                                                    | The Umbrella HELM Chart should be structured hierarchically so that related Enablement Service components are grouped into bundles. <br>The Umbrella HELM Chart must have a clear hierarchical structure <br> Each Enablement Service component must be assigned to a unique bundle.<br>No circular dependencies between bundles are allowed.                                                                                                                                                                    | The chart is modular and divided into defined bundles. <br>Each bundle can be deployed and maintained independently.                                                                                                                                                                                                                                                                                                 |
+| 7.1.5.3        | Interchangeability of bundle components via “Bring-Your-Own” components                                                                                                                                                                                                                                                                              | Bundle components should be interchangeable through “Bring-Your-Own” components. <br>“Bring your own” is available for every component and means that these components do not have to be delivered by default with the Umbrella Chart but can be provided by the respective users.                                                                                                                                                                                                                               | Bundle components can be interchanged by “Bring-Your-Own” components.                                                                                                                                                                                                                                                                                                                                                |
+| [WP-7.1.-D006] | [WP-7.1.-D006] Product developed according to a Technology Readiness Level (TRL) of 3                                                                                                                                                                                                                                                                |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | [WP-7.1.-D006] The product is developed according to a Technology Readiness Level (TRL) of 3                                                                                                                                                                                                                                                                                                                         |
+| 7.1.6.1        | POC                                                                                                                                                                                                                                                                                                                                                  | Creation of a POC for the "Hausanschluss" Bundle                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | POC implementation is completed. <br>POC has been presented in a demo                                                                                                                                                                                                                                                                                                                                                |
+| 7.1.6.2        | Deployment Strategy                                                                                                                                                                                                                                                                                                                                  | The provisioning of bundles is carried out independently. <br>There must be an option to selectively activate or deactivate bundles.                                                                                                                                                                                                                                                                                                                                                                             | Configuration is managed via HELM values, allowing flexible adaptation according to the environment.                                                                                                                                                                                                                                                                                                                 |
+
+# 3 AS-IS Analysis
+
+## 3.1 People
+
+### 3.1.1 Target Group Analysis
+
+See "4.1.1 To-be Target Group Analysis" below. No deviations between As-is and To-be target groups have been identified.
+
+## 3.2 Process
+
+### 3.2.1 Use Case View (high-level)
+
+Umbrella Chart is intended for the following Use Cases:
+
+| Actor             | Use case                                                                                             |
+|-------------------|------------------------------------------------------------------------------------------------------|
+| Product Developer | Sandbox Environments: Create local environments to evaluate and experiment with Catena-X components. |
+| Product Developer | Development: Provide a unified setup for contributors and developers working on Tractus-X projects.  |
+| Product Tester    | Testing: Run end-to-end tests for Catena-X services.                                                 |
+| Product Manager   | Evaluate the dataspace to assess if their product can be used within Catena-X.                       |
+
+## 3.4 System
+
+### 3.4.1 Context Delimitation
+
+#### Existing Umbrella Chart Structure
+
+````mermaid
+flowchart
+    subgraph "Umbrella Chart"
+        ChartYaml["Chart.yaml"]
+        subgraph charts
+            Portal["Portal"]
+            CentralIdp["CentralIdp"]
+            DiscoveryFinder["Discovery Finder"]
+            SDFactory["SD-Factory"]
+            SSICredentialIssuer["SSI Credential Issuer"]
+            SemanticHub["Semantic Hub"]
+            BPDM["BPDM"]
+            DataConsumer["Data Consumer"]
+            DataProvider["Data Provider"]
+            BDRS["BDRS"]
+            SSIWalletStub["SSI Wallet Stub"]
+        end
+        subgraph "tx-data-provider"
+            EDC["EDC"]
+            DTR["DTR"]
+            SubmodelServer["Submodel Server"]
+        end
+    end
+
+    ChartYaml --> Portal
+    ChartYaml --> CentralIdp
+    ChartYaml --> DiscoveryFinder
+    ChartYaml --> SDFactory
+    ChartYaml --> SSICredentialIssuer
+    ChartYaml --> SemanticHub
+    ChartYaml --> BPDM
+    ChartYaml --> DataConsumer
+    ChartYaml --> DataProvider
+    ChartYaml --> BDRS
+    ChartYaml --> SSIWalletStub
+    DataConsumer --> EDC
+    DataProvider --> EDC
+    DataProvider --> DTR
+    DataProvider --> SubmodelServer
+````
+
+# 4 TO-BE Design
+
+## 4.1 People
+
+### 4.1.1 Target Group Analysis
+
+Overall data space roles: https://catena-x.net/en/1/catena-x-introduce-implement/how-to-operate-catena-x
+
+The relevant data space roles are:
+
+- Data Consumer
+- Data Provider
+- Enablement Service Provider
+
+Scope: Umbrella HELM Charts
+
+- Enablement Services: These services are included under the umbrella of HELM charts, focusing on enabling
+  functionalities.
+
+Out of Scope: Core services such as Portal or BPDM are not considered within this scope.
+
+Primary target groups:
+
+| No. | Target group                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | Data space roles                                                    | Target group differentiation                                                                                                                                                                                                                                                                            | Behaviour, Needs, Pains & Usage                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+|-----|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| 1   | Developers<ul><li>External Developers (not Tractus-X developers): Utilize the chart for demonstration or evaluation purposes.</li><li>Experienced software and product developers who are developing a business app for a CATENA-X data space. They need to develop the app against the interfaces of the data space and integrate them accordingly.</li><li>They emphasize efficient and cost-effective implementation:<ul><li>Cost Efficiency: They do not want to use expensive SaaS solutions.</li><li>Technical Independence: They lack the knowledge and capacity to deploy the enablement and core services of the data space themselves.</li><li>Focus on Development: They concentrate on application development without delving deeply into the deployment and operation of the underlying infrastructure.</li></ul></li><li>Out of Scope: Developers running tests in test runners are not considered within this scope.</li></ul> | Data Consumer <br/> Data Provider <br/> Enablement Service Provider |                                                                                                                                                                                                                                                                                                         | <ul><li>Needs / sources of information<ul><li><a href="https://eclipse-tractusx.github.io/Kits/">Kit documentation tractus-x</a> for interaction purposes</li><li><a href="https://catenax-ev.github.io/">Catena-X documentation</a> for standards and regulations</li><li><a href="https://github.com/eclipse-tractusx/tractus-x-umbrella">Umbrella documentation</a> for umbrella component information</li></ul></li><li>Challenges → Solution<ul><li>Decentralization e.g. Where are other systems? How to interact with them? → Solution: Umbrella charts and bundles for deployment</li><li>Complex setup → Solution: delivery of small capability bundles</li></ul></li></ul> |
+| 2   | Tester requiring a test system                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | Data Consumer <br/> Data Provider <br/> Enablement Service Provider | <ul><li>Developer (1) tests their feature.</li><li>Tester (2) performs end-to-end testing.</li><li>For the tester, the modular structure is less relevant since they focus on E2E testing, whereas the developer selects the required components.</li><li>The testbed must be easy to deploy.</li></ul> | Same as above from an End-to-end testing perspective.<br/> Typically a tester has less technical know-how than a developer and therefore needs a "one-size-fits-all" (e.g.  Testbed) chart for easier testing.                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+| 3   | SMEs                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | Data Consumer <br/> Data Provider <br/> Enablement Service Provider |                                                                                                                                                                                                                                                                                                         | Need: SMEs developing a service within the Catena-X Data space want an environment to develop and test their service against without the need for expensive SaaS solutions.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+
+## 4.2 Process
+
+### 4.2.1 Use Case View (high-level)
+
+#### Group 1: Product developer
+
+| ID  | Name                                    | Actor             | Description                                                                                                        |
+|-----|-----------------------------------------|-------------------|--------------------------------------------------------------------------------------------------------------------|
+| UC1 | Configure HELM Chart                    | Product Developer | The product developer configures the HELM Chart for the specific environment.                                      |
+| UC2 | Configure Secrets                       | Product Developer | The product developer manages and configures secrets.                                                              |
+| UC3 | Execute Deployment Pipeline             | Product Developer | The product developer successfully executes the deployment pipeline for the HELM Chart.                            |
+| UC4 | Integrate EDC, DTR, and Identity Wallet | Product Developer | The actors integrate the components EDC, Digital Twin Registry, and Identity Wallet for seamless interoperability. |
+| UC5 | Set Up Connection Infrastructure        | Product Developer | The actor sets up the connection infrastructure for linking to the central data space infrastructure.              |
+| UC6 | Maintain Infrastructure Module          | Product Developer | The product developer maintains the modular architecture of the HELM Chart.                                        |
+| UC7 | Ensure Scalability                      | Product Developer | The product developer ensures scalability to support growing numbers of users and data volumes.                    |
+| UC8 | Sandbox Environments                    | Product Developer | The product developer creates local environments to evaluate and experiment with Catena-X components.              |
+
+#### Group 2: Product Tester
+
+| ID  | Name        | Actor          | Description                                                     |
+|-----|-------------|----------------|-----------------------------------------------------------------|
+| UC9 | E2E Testing | Product Tester | The product tester runs end-to-end tests for Catena-X services. |
+
+#### Group 3: Product Manager
+
+| ID   | Name                 | Actor           | Description                                                                                         |
+|------|----------------------|-----------------|-----------------------------------------------------------------------------------------------------|
+| UC10 | Dataspace Evaluation | Product Manager | The Product manager evaluates the dataspace to assess if their product can be used within Catena-X. |
+
+#### Use Case diagram
+
+````mermaid
+flowchart LR
+    PD[Product Developer]
+    PT[Product Tester]
+    PM[Product Manager]
+    UC1[Configure HELM Chart]
+    UC2[Configure Secrets]
+    UC3[Execute Deployment Pipeline]
+    UC4[Integrate EDC, DTR, and Identity Wallet]
+    UC5[Set Up Connection Infrastructure]
+    UC6[Maintain Infrastructure Module]
+    UC7[Ensure Scalability]
+    UC8[Sandbox Environments]
+    UC9[E2E Testing]
+    UC10[Dataspace Evaluation]
+    PD --> UC1
+    PD --> UC2
+    PD --> UC3
+    PD --> UC4
+    PD --> UC5
+    PD --> UC6
+    PD --> UC7
+    PD --> UC8
+    PT --> UC9
+    PM --> UC10
+````
+
+### 4.2.2 Business Process (SCC Artifact)
+
+#### Chart Release Process
+
+Charts will be released using the already existing workflow in the Umbrella Chart repository. The workflow will
+automatically release a Chart, once it is pushed to the "charts/" directory with a new Chart version.
+
+Chart versions should follow [Semantic Versioning](https://semver.org/)
+
+#### Capability Bundle Structure
+
+Capability bundle modularization for the Tractus-X Umbrella Helm chart is a sound architectural and operational design.
+It aligns with both the domain-driven architecture of Catena-X (data exchange, digital twin, identity, semantics are
+distinct domains) and with Kubernetes best practices for managing complex applications (using an umbrella chart to
+bundle related microservices).
+
+Each bundle is self-sufficient, which improves isolation (failures or changes in one domain have minimal impact on
+others) and allows scaling and upgrading along domain lines. It simplifies deployment by allowing “plug-and-play”
+capabilities: an Enablement Service Provider can decide which bundles to operate based on its role e.g., include the
+Digital Twin and Semantic bundles if offering an asset-rich service, or omit them if not. The approach is consistent
+with how other OSS projects deliver multi-component systems, providing one-step installation without sacrificing the
+ability to tweak individual parts.
+
+Why this structure was proposed:
+
+1. **Clear Separation of Concerns**  
+   Each capability bundle (e.g. EDC Data Transfer, Digital Twin, Identity & Trust, Semantic Model) aligns with a
+   specific functional domain. This separation makes it easier to understand the role of each service (e.g., the EDC
+   connector vs. the digital twin registry), reduces coupling between unrelated components, and ultimately makes
+   maintenance and troubleshooting more straightforward.
+2. **Modular Deployment**  
+   Some participants in Catena-X may not need all services (e.g., some might not use the Digital Twin bundle). By
+   structuring the umbrella chart into bundles, a user can enable just those needed capabilities. This leads to leaner
+   installs and avoids unnecessary resource usage.
+3. **Best Practices with Helm**  
+   Using an umbrella chart with subcharts/bundles is a well-recognized Helm best practice for complex applications. It
+   allows a single helm install to set up multiple microservices while still allowing each service to have its own
+   lifecycle, configuration, and version.
+4. **Alignment with Domain-Driven Approach**  
+   Catena-X is organized around distinct, loosely-coupled “building blocks.” Bundling services by domain matches this
+   architectural vision. It’s clear which domain each set of microservices belongs to (EDC for data exchange, identity
+   for credential management, etc.). This clarity also helps new adopters navigate the ecosystem.
+
+````mermaid
+%%{init: {"flowchart": {"subGraphTitleMargin": { "bottom": 10}}}}%%
+flowchart LR
+    subgraph A["Core Services"]
+        Vault["Vault"]
+    end
+
+    subgraph B["Capability Bundle: Identity & Trust"]
+        SSIWalletStub["SSI Wallet Stub"]
+    end
+
+    subgraph C["Capability Bundle: Dataspace Connector"]
+        EDC["EDC"]
+        EDCDB["EDC DB"]
+        EDC .-> EDCDB
+    end
+
+    subgraph "Capability Bundle: Digital Twin"
+        DTR["DTR"]
+        DTRDB["DTR DB"]
+        DTR .-> DTRDB
+    end
+
+    subgraph "Capability Bundle: Data Persistence Layer"
+        SimpleSubmodelServer["Simple Submodel Server"]
+    end
+
+    subgraph "Hausanschluss Actors"
+        subgraph "Data Provider"
+            DataProvider["Data Provider"]
+        end
+        subgraph "Data Consumer"
+            DataConsumer["Data Consumer"]
+        end
+        subgraph "Enablement Provider"
+            EnablementProvider["Enablement Provider"]
+        end
+    end
+
+    EDC -..-> SSIWalletStub
+    EDC -..-> Vault
+    DataProvider --> EDC
+    DataProvider --> DTR
+    DataProvider --> SimpleSubmodelServer
+    DataConsumer --> EDC
+    EnablementProvider --> DataConsumer
+    EnablementProvider --> DataProvider
+````
+
+#### Deployment strategies
+
+##### Role: Data Provider
+
+The standard data provider role consists of a EDC, DTR and Submodel Server Bundles. EDC uses the Identity Wallet Bundle.
path: docs/concept/TAP7.1-solution-design.md
user: login: mgarciaLKS
body: ```suggestion
The standard data provider role consists of an EDC, DTR and Submodel Server Bundles. EDC uses the Identity Wallet Bundle.
```
created_at: 2025-04-03T10:11:56Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,516 @@
+# Solution Design "Hausanschluss" Bundle Concept
+
+# 1 Business Case
+
+## 1.1 Executive Summary
+
+The "Hausanschluss" Bundle aims to simplify the installation of the enablement services Eclipse Dataspace
+Connector (EDC), Digital Twin Registry (DTR), and their supporting components. By developing a flexible, parameterizable
+installation package, the project seeks to reduce deployment complexity and lower barriers to participation in the
+Catena‑X data space. This bundle will enable independent component updates and support a modular "bring your own"
+approach, ultimately fostering a more efficient and accessible ecosystem for diverse participants—such as testers,
+external product developers, product testers, and small and medium-sized enterprises.
+
+## 1.2 Business Need
+
+Current deployment methods for data space integration are complex and require significant manual effort. This PoC
+addresses the need to:
+
+- **Reduce Complexity:** Simplify the deployment topology by bundling components into capabilities.
+- **Automate Deployment:** Provide an automated installation package using Kubernetes and HELM.
+- **Minimize Configuration Overhead:** Streamline the integration process by providing pre-configured bundles that require only minimal manual parameter adjustments.
+- **Extend Documentation:** Provide a detailed documentation tailored to the target groups.
+- **Enable Extension:** Design the system to allow the seamless addition of new components or capabilities.
+
+## 1.3 Objectives
+
+- **Simplify Deployment and Maintenance:** Develop an installation package that minimizes manual configuration through
+  automation.
+- **Ensure Modularity:** Structure the bundle so that components can be independently installed, updated, or replaced
+  without affecting other services.
+- **Facilitate Flexibility:** Implement a "bring your own" model for key components, such as EDC, PostgreSQL, and HashiCorp
+  Vault, to allow tailored deployments that meet specific needs.
+- **Increase Accessibility**: Lower entry barriers for new participants by reducing technical complexity and operational
+  dependencies.
+- **Scalability:** Structure the bundles so that they can be deployed multiple times.
+
+## 1.4 Expected Deliverables
+
+- **PoC Documentation:** A concept and architecture overview highlighting the modular design.
+- **Modular Installation Package:** A set of HELM charts for deploying the enablement service bundles:
+    - **Dataspace Connector:** Including the Eclipse Dataspace Connector, EDC PostgreSQL, and HashiCorp Vault.
+    - **Digital Twin Bundle:** Featuring components such as the Decentral DT Registry (with “bring your own” PostgreSQL)
+    - **Data Persitence Layer Bundle:** Including a simple Submodel Server to store semantic data.
+    - **Identity Wallet Bundle:** Covering the Identity Wallet functionality.
+- **Demonstration Environment:** A test deployment showcasing reduced complexity and improved efficiency.
+- **Basic User Guide:** Instructions on how to deploy and update the PoC bundle.
+
+## 1.5 Benefits
+
+- **Operational Efficiency:** Faster and more reliable deployments with less manual work.
+- **Scalability:** A modular design that can be scaled or adapted for future full-scale deployments.
+- **Ease of Adoption:** Simplified deployment processes make it easier for testers and external developers to engage.
+
+## 1.6. Dependencies
+
+- **Interoperability** with the CATENA‑X standards.
+
+## 1.7. Success Criteria
+
+- **Technology Readiness Level:** Achievement of a Technology Readiness Level (TRL) of 3, as specified in the requirements.
+- **Functional PoC Deployment:** Demonstrated automated, modular installation with reduced manual steps.
+- **Simplified Configuration:** Clear evidence of reduced configuration complexity.
+- **Positive Feedback:** End-user validation from a select group of demo participants and the Tractus-X community.
+- **Documentation Completeness:** Availability of concise deployment and user guides.
+
+## 1.8. Out of Scope
+
+- **Full Production Readiness:** This PoC is not intended to be a production-ready solution.
+- **Core Services Exclusion:** Core services are not part of the Hausanschluss Bundles.
+- **App Provider Role:** The role of App Provider is considered out of scope for this deployment.
+- **Alternative Deployment Techniques:** While the evaluation of alternative deployment methods is acknowledged, the primary
+  focus remains on Kubernetes and HELM-based deployment.
+
+# 2 Requirements Analysis
+
+## 2.1 Assumptions
+
+## 2.2 Requirements Catalog
+
+| ID             | Requirement                                                                                                                                                                                                                                                                                                                                          | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | Deliverables / Acceptance Criteria                                                                                                                                                                                                                                                                                                                                                                                   |
+|----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| [WP-7.1.-D001] | The Hausanschluss Bundle aims to simplify the installation and maintenance of the EDC and other components that together ensure a “Hausanschluss”. A flexible, parameterizable installation package is intended to reduce complexity and make integration more efficient, thereby simplifying participation in Catena‑X for additional participants. | Specification and development of a flexible, parameterizable installation package that reduces the complexity of installing and maintaining the required components for seamless integration into the Catena‑X data space. This package should facilitate updates and new versions, making participation in Catena‑X more efficient and accessible. In doing so, SMEs shall be enabled to participate without high costs or dependency on SaaS providers while maintaining control over their IT infrastructure. | [WP-7.1.-D001] Concept for the Hausanschluss is created                                                                                                                                                                                                                                                                                                                                                              |
+| 7.1.1.1        | The solution concept must define the Capability Bundles structures to be implemented. For each Capability Bundle, the included bundles and their versions are mapped.                                                                                                                                                                                | "The following Capability Bundle structure is implemented:                                                                                                                                                                                                                                                                                                                                                                                                                                                       | The structure of the Capability Bundles for the Enablement Services has been specified. For version R24.12 it is clearly defined which Tractus‑X services and components are assigned to each Capability Bundle                                                                                                                                                                                                      |
+| 7.1.1.2        | Definition of Data Space Roles                                                                                                                                                                                                                                                                                                                       | Data Consumer, Data Provider, Enablement Service Provider                                                                                                                                                                                                                                                                                                                                                                                                                                                        | As part of the target group analysis, the target groups are defined and aligned with the data space roles. <br>Mapping from data space role to target group has been completed. <br>Mapping from target group to data space role has been completed. <br>An assignment of data space roles to Capability Bundles has been made.                                                                                      |
+| 7.1.1.4        | Modularity & Maintainability: No dependencies between Capability Bundles                                                                                                                                                                                                                                                                             | Unique assignment of components and services to a defined Capability Bundle. <br>Each component and service should be assigned to only one Capability Bundle. <br>Dependencies between Capability Bundles are allowed.                                                                                                                                                                                                                                                                                           | Components and Services should only be part of one bundle. <br>Each bundle must be deployable in isolation and can be installed, updated, or removed independently. <br>Capability Bundles must be organized in separate HELM sub‑charts. <br>Circular dependencies between bundles must be avoided.                                                                                                                 |
+| 7.1.1.5        | Modularity & Maintainability: Concept for reducing deployment complexity                                                                                                                                                                                                                                                                             | The system deployment should be optimized to reduce the existing complexity. The goal is to make the provisioning process more efficient, robust, and easier to maintain.                                                                                                                                                                                                                                                                                                                                        | **Simplification of deployment processes:** A reduction of manual configuration steps has been achieved. <br>**Transparency and traceability:** Clearly documented deployment steps are provided. <br>**Improvements of Chart configuration by:** <br>usage of template  <br>reducing configuration options <br>reducing manual steps in the setup                                                                   |
+| 7.1.1.6        | Modularity & Maintainability                                                                                                                                                                                                                                                                                                                         | Charts are published automatically.                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | Charts are published via a publicly accessible charts repository.                                                                                                                                                                                                                                                                                                                                                    |
+| 7.1.1.13       | Solution Concept                                                                                                                                                                                                                                                                                                                                     | Creation of a solution design for the “Hausanschluss” Bundle.                                                                                                                                                                                                                                                                                                                                                                                                                                                    | The solution design for the "Hausanschluss" Bundle is created. <br>The solution design for the "Hausanschluss" Bundle ispublished in the repository: https://github.com/eclipse-tractusx/tractus-x-umbrella.                                                                                                                                                                                                         |
+| 7.1.1.14       | Scalability of Enablement Services                                                                                                                                                                                                                                                                                                                   | Scalability of Enablement Services                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | Developers should be able to deploy an arbitrary number of Enablement Services. <br>Example: Up to 3 EDCs can be provided.                                                                                                                                                                                                                                                                                           |
+| 7.1.1.16       | Interoperability                                                                                                                                                                                                                                                                                                                                     | Interoperability                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | Interoperability with the CATENA‑X standards. <br>This interoperability is documented and traceable.                                                                                                                                                                                                                                                                                                                 |
+| [WP-7.1.-D002] | [WP-7.1.-D002] Target group for the specification is defined.                                                                                                                                                                                                                                                                                        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | [WP-7.1.-D002] Target group for the specification is defined.                                                                                                                                                                                                                                                                                                                                                        |
+| 7.1.2.1        | Target Group Analysis                                                                                                                                                                                                                                                                                                                                | The target group analysis for the "Hausanschluss Bundle"is defined.                                                                                                                                                                                                                                                                                                                                                                                                                                              | The analysis has been conducted. <br>The target group is included in the solution concept <br>To be clarified: What is included in the Hausanschluss and who can operate it in which scenario (OEM, SME, service provider, etc.).                                                                                                                                                                                    |
+| [WP-7.1.-D003] | [WP-7.1.-D003] Decentralized components and services defined                                                                                                                                                                                                                                                                                         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | [WP-7.1.-D003] Decentralized components and services have been defined.                                                                                                                                                                                                                                                                                                                                              |
+| 7.1.3.1        | See [WP-7.1.-D001-AC001]                                                                                                                                                                                                                                                                                                                             |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | See [WP-7.1.-D001-AC001]                                                                                                                                                                                                                                                                                                                                                                                             |
+| [WP-7.1.-D004] | [WP-7.1.-D004] Documentation of the Hausanschluss Bundle is completed                                                                                                                                                                                                                                                                                |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | [WP-7.1.-D004] Documentation of the Hausanschluss Bundle is completed                                                                                                                                                                                                                                                                                                                                                |
+| 7.1.4.1        | Documentation of the Hausanschluss-Bundles                                                                                                                                                                                                                                                                                                           | Usability                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | Documentation is provided that enables an experienced product developer - with knowledge of Helm Charts, Docker, and Vaults - to deploy the chart independently without external help. <br>A troubleshooting and FAQ section is included to support the developer. <br>Prerequisites, skills, and technology requirements are outlined, detailing what a developer must know to perform the deployment autonomously. |
+| 7.1.4.2        | Documentation of the Hausanschluss-Bundles                                                                                                                                                                                                                                                                                                           | Documentation of the Hausanschluss-Bundles is completed.                                                                                                                                                                                                                                                                                                                                                                                                                                                         | Documentation is provided for: <br>Configuration of the defined bundles according to the specified requirements and parameters <br>Integration of the documentation into the Umbrella HELM Charts <br>Integration into the Umbrella HELM Chart to ensure consistent deployment                                                                                                                                       |
+| [WP-7.1.-D005] | [WP-7.1.-D005] Umbrella HELM Charts for the Hausanschluss developed, tested, and documented                                                                                                                                                                                                                                                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | [WP-7.1.-D005] Umbrella HELM Charts for the Hausanschluss have been developed, tested, and documented.                                                                                                                                                                                                                                                                                                               |
+| 7.1.5.1        | Re-activate Umbrella HELM Charts to the latest release state                                                                                                                                                                                                                                                                                         | The Enablement Services components of the Umbrella HELM Charts must be updated to version R24.12. This includes the following upgrades: <br> Upgrade DTR to version R24.12 (#188) <br>Upgrade EDCs to version R24.12 (#193) <br>Update SSI-DIM-Wallet-Stub to version 0.1.8 (#206)                                                                                                                                                                                                                               | The HELM Chart will then contain the updated versions of the components. <br>After the upgrade, the components (DTR, EDCs, SSI‑DIM‑Wallet‑Stub) run stably without functional impairments. <br>The deployment pipeline for the HELM Chart executes successfully <br>Relevant tests & smoke tests (e.g., integration tests) confirm the migration.                                                                    |
+| 7.1.5.2        | Hierarchical structuring and bundling of Enablement Service components in the Umbrella HELM Chart                                                                                                                                                                                                                                                    | The Umbrella HELM Chart should be structured hierarchically so that related Enablement Service components are grouped into bundles. <br>The Umbrella HELM Chart must have a clear hierarchical structure <br> Each Enablement Service component must be assigned to a unique bundle.<br>No circular dependencies between bundles are allowed.                                                                                                                                                                    | The chart is modular and divided into defined bundles. <br>Each bundle can be deployed and maintained independently.                                                                                                                                                                                                                                                                                                 |
+| 7.1.5.3        | Interchangeability of bundle components via “Bring-Your-Own” components                                                                                                                                                                                                                                                                              | Bundle components should be interchangeable through “Bring-Your-Own” components. <br>“Bring your own” is available for every component and means that these components do not have to be delivered by default with the Umbrella Chart but can be provided by the respective users.                                                                                                                                                                                                                               | Bundle components can be interchanged by “Bring-Your-Own” components.                                                                                                                                                                                                                                                                                                                                                |
+| [WP-7.1.-D006] | [WP-7.1.-D006] Product developed according to a Technology Readiness Level (TRL) of 3                                                                                                                                                                                                                                                                |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | [WP-7.1.-D006] The product is developed according to a Technology Readiness Level (TRL) of 3                                                                                                                                                                                                                                                                                                                         |
+| 7.1.6.1        | POC                                                                                                                                                                                                                                                                                                                                                  | Creation of a POC for the "Hausanschluss" Bundle                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | POC implementation is completed. <br>POC has been presented in a demo                                                                                                                                                                                                                                                                                                                                                |
+| 7.1.6.2        | Deployment Strategy                                                                                                                                                                                                                                                                                                                                  | The provisioning of bundles is carried out independently. <br>There must be an option to selectively activate or deactivate bundles.                                                                                                                                                                                                                                                                                                                                                                             | Configuration is managed via HELM values, allowing flexible adaptation according to the environment.                                                                                                                                                                                                                                                                                                                 |
+
+# 3 AS-IS Analysis
+
+## 3.1 People
+
+### 3.1.1 Target Group Analysis
+
+See "4.1.1 To-be Target Group Analysis" below. No deviations between As-is and To-be target groups have been identified.
+
+## 3.2 Process
+
+### 3.2.1 Use Case View (high-level)
+
+Umbrella Chart is intended for the following Use Cases:
+
+| Actor             | Use case                                                                                             |
+|-------------------|------------------------------------------------------------------------------------------------------|
+| Product Developer | Sandbox Environments: Create local environments to evaluate and experiment with Catena-X components. |
+| Product Developer | Development: Provide a unified setup for contributors and developers working on Tractus-X projects.  |
+| Product Tester    | Testing: Run end-to-end tests for Catena-X services.                                                 |
+| Product Manager   | Evaluate the dataspace to assess if their product can be used within Catena-X.                       |
+
+## 3.4 System
+
+### 3.4.1 Context Delimitation
+
+#### Existing Umbrella Chart Structure
+
+````mermaid
+flowchart
+    subgraph "Umbrella Chart"
+        ChartYaml["Chart.yaml"]
+        subgraph charts
+            Portal["Portal"]
+            CentralIdp["CentralIdp"]
+            DiscoveryFinder["Discovery Finder"]
+            SDFactory["SD-Factory"]
+            SSICredentialIssuer["SSI Credential Issuer"]
+            SemanticHub["Semantic Hub"]
+            BPDM["BPDM"]
+            DataConsumer["Data Consumer"]
+            DataProvider["Data Provider"]
+            BDRS["BDRS"]
+            SSIWalletStub["SSI Wallet Stub"]
+        end
+        subgraph "tx-data-provider"
+            EDC["EDC"]
+            DTR["DTR"]
+            SubmodelServer["Submodel Server"]
+        end
+    end
+
+    ChartYaml --> Portal
+    ChartYaml --> CentralIdp
+    ChartYaml --> DiscoveryFinder
+    ChartYaml --> SDFactory
+    ChartYaml --> SSICredentialIssuer
+    ChartYaml --> SemanticHub
+    ChartYaml --> BPDM
+    ChartYaml --> DataConsumer
+    ChartYaml --> DataProvider
+    ChartYaml --> BDRS
+    ChartYaml --> SSIWalletStub
+    DataConsumer --> EDC
+    DataProvider --> EDC
+    DataProvider --> DTR
+    DataProvider --> SubmodelServer
+````
+
+# 4 TO-BE Design
+
+## 4.1 People
+
+### 4.1.1 Target Group Analysis
+
+Overall data space roles: https://catena-x.net/en/1/catena-x-introduce-implement/how-to-operate-catena-x
+
+The relevant data space roles are:
+
+- Data Consumer
+- Data Provider
+- Enablement Service Provider
+
+Scope: Umbrella HELM Charts
+
+- Enablement Services: These services are included under the umbrella of HELM charts, focusing on enabling
+  functionalities.
+
+Out of Scope: Core services such as Portal or BPDM are not considered within this scope.
+
+Primary target groups:
+
+| No. | Target group                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | Data space roles                                                    | Target group differentiation                                                                                                                                                                                                                                                                            | Behaviour, Needs, Pains & Usage                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+|-----|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| 1   | Developers<ul><li>External Developers (not Tractus-X developers): Utilize the chart for demonstration or evaluation purposes.</li><li>Experienced software and product developers who are developing a business app for a CATENA-X data space. They need to develop the app against the interfaces of the data space and integrate them accordingly.</li><li>They emphasize efficient and cost-effective implementation:<ul><li>Cost Efficiency: They do not want to use expensive SaaS solutions.</li><li>Technical Independence: They lack the knowledge and capacity to deploy the enablement and core services of the data space themselves.</li><li>Focus on Development: They concentrate on application development without delving deeply into the deployment and operation of the underlying infrastructure.</li></ul></li><li>Out of Scope: Developers running tests in test runners are not considered within this scope.</li></ul> | Data Consumer <br/> Data Provider <br/> Enablement Service Provider |                                                                                                                                                                                                                                                                                                         | <ul><li>Needs / sources of information<ul><li><a href="https://eclipse-tractusx.github.io/Kits/">Kit documentation tractus-x</a> for interaction purposes</li><li><a href="https://catenax-ev.github.io/">Catena-X documentation</a> for standards and regulations</li><li><a href="https://github.com/eclipse-tractusx/tractus-x-umbrella">Umbrella documentation</a> for umbrella component information</li></ul></li><li>Challenges → Solution<ul><li>Decentralization e.g. Where are other systems? How to interact with them? → Solution: Umbrella charts and bundles for deployment</li><li>Complex setup → Solution: delivery of small capability bundles</li></ul></li></ul> |
+| 2   | Tester requiring a test system                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | Data Consumer <br/> Data Provider <br/> Enablement Service Provider | <ul><li>Developer (1) tests their feature.</li><li>Tester (2) performs end-to-end testing.</li><li>For the tester, the modular structure is less relevant since they focus on E2E testing, whereas the developer selects the required components.</li><li>The testbed must be easy to deploy.</li></ul> | Same as above from an End-to-end testing perspective.<br/> Typically a tester has less technical know-how than a developer and therefore needs a "one-size-fits-all" (e.g.  Testbed) chart for easier testing.                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+| 3   | SMEs                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | Data Consumer <br/> Data Provider <br/> Enablement Service Provider |                                                                                                                                                                                                                                                                                                         | Need: SMEs developing a service within the Catena-X Data space want an environment to develop and test their service against without the need for expensive SaaS solutions.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+
+## 4.2 Process
+
+### 4.2.1 Use Case View (high-level)
+
+#### Group 1: Product developer
+
+| ID  | Name                                    | Actor             | Description                                                                                                        |
+|-----|-----------------------------------------|-------------------|--------------------------------------------------------------------------------------------------------------------|
+| UC1 | Configure HELM Chart                    | Product Developer | The product developer configures the HELM Chart for the specific environment.                                      |
+| UC2 | Configure Secrets                       | Product Developer | The product developer manages and configures secrets.                                                              |
+| UC3 | Execute Deployment Pipeline             | Product Developer | The product developer successfully executes the deployment pipeline for the HELM Chart.                            |
+| UC4 | Integrate EDC, DTR, and Identity Wallet | Product Developer | The actors integrate the components EDC, Digital Twin Registry, and Identity Wallet for seamless interoperability. |
+| UC5 | Set Up Connection Infrastructure        | Product Developer | The actor sets up the connection infrastructure for linking to the central data space infrastructure.              |
+| UC6 | Maintain Infrastructure Module          | Product Developer | The product developer maintains the modular architecture of the HELM Chart.                                        |
+| UC7 | Ensure Scalability                      | Product Developer | The product developer ensures scalability to support growing numbers of users and data volumes.                    |
+| UC8 | Sandbox Environments                    | Product Developer | The product developer creates local environments to evaluate and experiment with Catena-X components.              |
+
+#### Group 2: Product Tester
+
+| ID  | Name        | Actor          | Description                                                     |
+|-----|-------------|----------------|-----------------------------------------------------------------|
+| UC9 | E2E Testing | Product Tester | The product tester runs end-to-end tests for Catena-X services. |
+
+#### Group 3: Product Manager
+
+| ID   | Name                 | Actor           | Description                                                                                         |
+|------|----------------------|-----------------|-----------------------------------------------------------------------------------------------------|
+| UC10 | Dataspace Evaluation | Product Manager | The Product manager evaluates the dataspace to assess if their product can be used within Catena-X. |
+
+#### Use Case diagram
+
+````mermaid
+flowchart LR
+    PD[Product Developer]
+    PT[Product Tester]
+    PM[Product Manager]
+    UC1[Configure HELM Chart]
+    UC2[Configure Secrets]
+    UC3[Execute Deployment Pipeline]
+    UC4[Integrate EDC, DTR, and Identity Wallet]
+    UC5[Set Up Connection Infrastructure]
+    UC6[Maintain Infrastructure Module]
+    UC7[Ensure Scalability]
+    UC8[Sandbox Environments]
+    UC9[E2E Testing]
+    UC10[Dataspace Evaluation]
+    PD --> UC1
+    PD --> UC2
+    PD --> UC3
+    PD --> UC4
+    PD --> UC5
+    PD --> UC6
+    PD --> UC7
+    PD --> UC8
+    PT --> UC9
+    PM --> UC10
+````
+
+### 4.2.2 Business Process (SCC Artifact)
+
+#### Chart Release Process
+
+Charts will be released using the already existing workflow in the Umbrella Chart repository. The workflow will
+automatically release a Chart, once it is pushed to the "charts/" directory with a new Chart version.
+
+Chart versions should follow [Semantic Versioning](https://semver.org/)
+
+#### Capability Bundle Structure
+
+Capability bundle modularization for the Tractus-X Umbrella Helm chart is a sound architectural and operational design.
+It aligns with both the domain-driven architecture of Catena-X (data exchange, digital twin, identity, semantics are
+distinct domains) and with Kubernetes best practices for managing complex applications (using an umbrella chart to
+bundle related microservices).
+
+Each bundle is self-sufficient, which improves isolation (failures or changes in one domain have minimal impact on
+others) and allows scaling and upgrading along domain lines. It simplifies deployment by allowing “plug-and-play”
+capabilities: an Enablement Service Provider can decide which bundles to operate based on its role e.g., include the
+Digital Twin and Semantic bundles if offering an asset-rich service, or omit them if not. The approach is consistent
+with how other OSS projects deliver multi-component systems, providing one-step installation without sacrificing the
+ability to tweak individual parts.
+
+Why this structure was proposed:
+
+1. **Clear Separation of Concerns**  
+   Each capability bundle (e.g. EDC Data Transfer, Digital Twin, Identity & Trust, Semantic Model) aligns with a
+   specific functional domain. This separation makes it easier to understand the role of each service (e.g., the EDC
+   connector vs. the digital twin registry), reduces coupling between unrelated components, and ultimately makes
+   maintenance and troubleshooting more straightforward.
+2. **Modular Deployment**  
+   Some participants in Catena-X may not need all services (e.g., some might not use the Digital Twin bundle). By
+   structuring the umbrella chart into bundles, a user can enable just those needed capabilities. This leads to leaner
+   installs and avoids unnecessary resource usage.
+3. **Best Practices with Helm**  
+   Using an umbrella chart with subcharts/bundles is a well-recognized Helm best practice for complex applications. It
+   allows a single helm install to set up multiple microservices while still allowing each service to have its own
+   lifecycle, configuration, and version.
+4. **Alignment with Domain-Driven Approach**  
+   Catena-X is organized around distinct, loosely-coupled “building blocks.” Bundling services by domain matches this
+   architectural vision. It’s clear which domain each set of microservices belongs to (EDC for data exchange, identity
+   for credential management, etc.). This clarity also helps new adopters navigate the ecosystem.
+
+````mermaid
+%%{init: {"flowchart": {"subGraphTitleMargin": { "bottom": 10}}}}%%
+flowchart LR
+    subgraph A["Core Services"]
+        Vault["Vault"]
+    end
+
+    subgraph B["Capability Bundle: Identity & Trust"]
+        SSIWalletStub["SSI Wallet Stub"]
+    end
+
+    subgraph C["Capability Bundle: Dataspace Connector"]
+        EDC["EDC"]
+        EDCDB["EDC DB"]
+        EDC .-> EDCDB
+    end
+
+    subgraph "Capability Bundle: Digital Twin"
+        DTR["DTR"]
+        DTRDB["DTR DB"]
+        DTR .-> DTRDB
+    end
+
+    subgraph "Capability Bundle: Data Persistence Layer"
+        SimpleSubmodelServer["Simple Submodel Server"]
+    end
+
+    subgraph "Hausanschluss Actors"
+        subgraph "Data Provider"
+            DataProvider["Data Provider"]
+        end
+        subgraph "Data Consumer"
+            DataConsumer["Data Consumer"]
+        end
+        subgraph "Enablement Provider"
+            EnablementProvider["Enablement Provider"]
+        end
+    end
+
+    EDC -..-> SSIWalletStub
+    EDC -..-> Vault
+    DataProvider --> EDC
+    DataProvider --> DTR
+    DataProvider --> SimpleSubmodelServer
+    DataConsumer --> EDC
+    EnablementProvider --> DataConsumer
+    EnablementProvider --> DataProvider
+````
+
+#### Deployment strategies
+
+##### Role: Data Provider
+
+The standard data provider role consists of a EDC, DTR and Submodel Server Bundles. EDC uses the Identity Wallet Bundle.
+
+````mermaid
+flowchart BT
+    A["Capability Bundle: Identity & Trust"]
+    B["Capability Bundle: Data Persistence Layer"]
+    C["Capability Bundle: Dataspace Connector"]
+    D["Capability Bundle: Digital Twin"]
+    E("Application to be tested/developed")
+    style E fill:#afafaf,color:black
+    F{{"Developer/Tester"}}
+    E --> B
+    E --> C
+    E --> D
+    C --> A
+    F --> E
+````
+
+##### Role: Data Consumer
+
+The standard data consumer role consists of only the EDC Bundle and the Identity Wallet Bundle.
+
+````mermaid
+flowchart BT
+    A["Capability Bundle: Identity & Trust"]
+    B["Capability Bundle: Dataspace Connector"]
+    C("Application to be tested/developed")
+    style C fill:#afafaf,color:black
+    D{{"Developer/Tester"}}
+    C --> B
+    B --> A
+    D --> C
+````
+
+##### Role: Enablement Provider
+
+The Enablement Provider roles consists of both the Data Consumer and Data Provider bundles. This allows provisioning of
path: docs/concept/TAP7.1-solution-design.md
user: login: mgarciaLKS
body: ```suggestion
The Enablement Provider role consists of both the Data Consumer and Data Provider bundles. This allows provisioning of
```
created_at: 2025-04-03T10:12:26Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,516 @@
+# Solution Design "Hausanschluss" Bundle Concept
+
+# 1 Business Case
+
+## 1.1 Executive Summary
+
+The "Hausanschluss" Bundle aims to simplify the installation of the enablement services Eclipse Dataspace
+Connector (EDC), Digital Twin Registry (DTR), and their supporting components. By developing a flexible, parameterizable
+installation package, the project seeks to reduce deployment complexity and lower barriers to participation in the
+Catena‑X data space. This bundle will enable independent component updates and support a modular "bring your own"
+approach, ultimately fostering a more efficient and accessible ecosystem for diverse participants—such as testers,
+external product developers, product testers, and small and medium-sized enterprises.
+
+## 1.2 Business Need
+
+Current deployment methods for data space integration are complex and require significant manual effort. This PoC
+addresses the need to:
+
+- **Reduce Complexity:** Simplify the deployment topology by bundling components into capabilities.
+- **Automate Deployment:** Provide an automated installation package using Kubernetes and HELM.
+- **Minimize Configuration Overhead:** Streamline the integration process by providing pre-configured bundles that require only minimal manual parameter adjustments.
+- **Extend Documentation:** Provide a detailed documentation tailored to the target groups.
+- **Enable Extension:** Design the system to allow the seamless addition of new components or capabilities.
+
+## 1.3 Objectives
+
+- **Simplify Deployment and Maintenance:** Develop an installation package that minimizes manual configuration through
+  automation.
+- **Ensure Modularity:** Structure the bundle so that components can be independently installed, updated, or replaced
+  without affecting other services.
+- **Facilitate Flexibility:** Implement a "bring your own" model for key components, such as EDC, PostgreSQL, and HashiCorp
+  Vault, to allow tailored deployments that meet specific needs.
+- **Increase Accessibility**: Lower entry barriers for new participants by reducing technical complexity and operational
+  dependencies.
+- **Scalability:** Structure the bundles so that they can be deployed multiple times.
+
+## 1.4 Expected Deliverables
+
+- **PoC Documentation:** A concept and architecture overview highlighting the modular design.
+- **Modular Installation Package:** A set of HELM charts for deploying the enablement service bundles:
+    - **Dataspace Connector:** Including the Eclipse Dataspace Connector, EDC PostgreSQL, and HashiCorp Vault.
+    - **Digital Twin Bundle:** Featuring components such as the Decentral DT Registry (with “bring your own” PostgreSQL)
+    - **Data Persitence Layer Bundle:** Including a simple Submodel Server to store semantic data.
+    - **Identity Wallet Bundle:** Covering the Identity Wallet functionality.
+- **Demonstration Environment:** A test deployment showcasing reduced complexity and improved efficiency.
+- **Basic User Guide:** Instructions on how to deploy and update the PoC bundle.
+
+## 1.5 Benefits
+
+- **Operational Efficiency:** Faster and more reliable deployments with less manual work.
+- **Scalability:** A modular design that can be scaled or adapted for future full-scale deployments.
+- **Ease of Adoption:** Simplified deployment processes make it easier for testers and external developers to engage.
+
+## 1.6. Dependencies
+
+- **Interoperability** with the CATENA‑X standards.
+
+## 1.7. Success Criteria
+
+- **Technology Readiness Level:** Achievement of a Technology Readiness Level (TRL) of 3, as specified in the requirements.
+- **Functional PoC Deployment:** Demonstrated automated, modular installation with reduced manual steps.
+- **Simplified Configuration:** Clear evidence of reduced configuration complexity.
+- **Positive Feedback:** End-user validation from a select group of demo participants and the Tractus-X community.
+- **Documentation Completeness:** Availability of concise deployment and user guides.
+
+## 1.8. Out of Scope
+
+- **Full Production Readiness:** This PoC is not intended to be a production-ready solution.
+- **Core Services Exclusion:** Core services are not part of the Hausanschluss Bundles.
+- **App Provider Role:** The role of App Provider is considered out of scope for this deployment.
+- **Alternative Deployment Techniques:** While the evaluation of alternative deployment methods is acknowledged, the primary
+  focus remains on Kubernetes and HELM-based deployment.
+
+# 2 Requirements Analysis
+
+## 2.1 Assumptions
+
+## 2.2 Requirements Catalog
+
+| ID             | Requirement                                                                                                                                                                                                                                                                                                                                          | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | Deliverables / Acceptance Criteria                                                                                                                                                                                                                                                                                                                                                                                   |
+|----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| [WP-7.1.-D001] | The Hausanschluss Bundle aims to simplify the installation and maintenance of the EDC and other components that together ensure a “Hausanschluss”. A flexible, parameterizable installation package is intended to reduce complexity and make integration more efficient, thereby simplifying participation in Catena‑X for additional participants. | Specification and development of a flexible, parameterizable installation package that reduces the complexity of installing and maintaining the required components for seamless integration into the Catena‑X data space. This package should facilitate updates and new versions, making participation in Catena‑X more efficient and accessible. In doing so, SMEs shall be enabled to participate without high costs or dependency on SaaS providers while maintaining control over their IT infrastructure. | [WP-7.1.-D001] Concept for the Hausanschluss is created                                                                                                                                                                                                                                                                                                                                                              |
+| 7.1.1.1        | The solution concept must define the Capability Bundles structures to be implemented. For each Capability Bundle, the included bundles and their versions are mapped.                                                                                                                                                                                | "The following Capability Bundle structure is implemented:                                                                                                                                                                                                                                                                                                                                                                                                                                                       | The structure of the Capability Bundles for the Enablement Services has been specified. For version R24.12 it is clearly defined which Tractus‑X services and components are assigned to each Capability Bundle                                                                                                                                                                                                      |
+| 7.1.1.2        | Definition of Data Space Roles                                                                                                                                                                                                                                                                                                                       | Data Consumer, Data Provider, Enablement Service Provider                                                                                                                                                                                                                                                                                                                                                                                                                                                        | As part of the target group analysis, the target groups are defined and aligned with the data space roles. <br>Mapping from data space role to target group has been completed. <br>Mapping from target group to data space role has been completed. <br>An assignment of data space roles to Capability Bundles has been made.                                                                                      |
+| 7.1.1.4        | Modularity & Maintainability: No dependencies between Capability Bundles                                                                                                                                                                                                                                                                             | Unique assignment of components and services to a defined Capability Bundle. <br>Each component and service should be assigned to only one Capability Bundle. <br>Dependencies between Capability Bundles are allowed.                                                                                                                                                                                                                                                                                           | Components and Services should only be part of one bundle. <br>Each bundle must be deployable in isolation and can be installed, updated, or removed independently. <br>Capability Bundles must be organized in separate HELM sub‑charts. <br>Circular dependencies between bundles must be avoided.                                                                                                                 |
+| 7.1.1.5        | Modularity & Maintainability: Concept for reducing deployment complexity                                                                                                                                                                                                                                                                             | The system deployment should be optimized to reduce the existing complexity. The goal is to make the provisioning process more efficient, robust, and easier to maintain.                                                                                                                                                                                                                                                                                                                                        | **Simplification of deployment processes:** A reduction of manual configuration steps has been achieved. <br>**Transparency and traceability:** Clearly documented deployment steps are provided. <br>**Improvements of Chart configuration by:** <br>usage of template  <br>reducing configuration options <br>reducing manual steps in the setup                                                                   |
+| 7.1.1.6        | Modularity & Maintainability                                                                                                                                                                                                                                                                                                                         | Charts are published automatically.                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | Charts are published via a publicly accessible charts repository.                                                                                                                                                                                                                                                                                                                                                    |
+| 7.1.1.13       | Solution Concept                                                                                                                                                                                                                                                                                                                                     | Creation of a solution design for the “Hausanschluss” Bundle.                                                                                                                                                                                                                                                                                                                                                                                                                                                    | The solution design for the "Hausanschluss" Bundle is created. <br>The solution design for the "Hausanschluss" Bundle ispublished in the repository: https://github.com/eclipse-tractusx/tractus-x-umbrella.                                                                                                                                                                                                         |
+| 7.1.1.14       | Scalability of Enablement Services                                                                                                                                                                                                                                                                                                                   | Scalability of Enablement Services                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | Developers should be able to deploy an arbitrary number of Enablement Services. <br>Example: Up to 3 EDCs can be provided.                                                                                                                                                                                                                                                                                           |
+| 7.1.1.16       | Interoperability                                                                                                                                                                                                                                                                                                                                     | Interoperability                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | Interoperability with the CATENA‑X standards. <br>This interoperability is documented and traceable.                                                                                                                                                                                                                                                                                                                 |
+| [WP-7.1.-D002] | [WP-7.1.-D002] Target group for the specification is defined.                                                                                                                                                                                                                                                                                        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | [WP-7.1.-D002] Target group for the specification is defined.                                                                                                                                                                                                                                                                                                                                                        |
+| 7.1.2.1        | Target Group Analysis                                                                                                                                                                                                                                                                                                                                | The target group analysis for the "Hausanschluss Bundle"is defined.                                                                                                                                                                                                                                                                                                                                                                                                                                              | The analysis has been conducted. <br>The target group is included in the solution concept <br>To be clarified: What is included in the Hausanschluss and who can operate it in which scenario (OEM, SME, service provider, etc.).                                                                                                                                                                                    |
+| [WP-7.1.-D003] | [WP-7.1.-D003] Decentralized components and services defined                                                                                                                                                                                                                                                                                         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | [WP-7.1.-D003] Decentralized components and services have been defined.                                                                                                                                                                                                                                                                                                                                              |
+| 7.1.3.1        | See [WP-7.1.-D001-AC001]                                                                                                                                                                                                                                                                                                                             |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | See [WP-7.1.-D001-AC001]                                                                                                                                                                                                                                                                                                                                                                                             |
+| [WP-7.1.-D004] | [WP-7.1.-D004] Documentation of the Hausanschluss Bundle is completed                                                                                                                                                                                                                                                                                |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | [WP-7.1.-D004] Documentation of the Hausanschluss Bundle is completed                                                                                                                                                                                                                                                                                                                                                |
+| 7.1.4.1        | Documentation of the Hausanschluss-Bundles                                                                                                                                                                                                                                                                                                           | Usability                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | Documentation is provided that enables an experienced product developer - with knowledge of Helm Charts, Docker, and Vaults - to deploy the chart independently without external help. <br>A troubleshooting and FAQ section is included to support the developer. <br>Prerequisites, skills, and technology requirements are outlined, detailing what a developer must know to perform the deployment autonomously. |
+| 7.1.4.2        | Documentation of the Hausanschluss-Bundles                                                                                                                                                                                                                                                                                                           | Documentation of the Hausanschluss-Bundles is completed.                                                                                                                                                                                                                                                                                                                                                                                                                                                         | Documentation is provided for: <br>Configuration of the defined bundles according to the specified requirements and parameters <br>Integration of the documentation into the Umbrella HELM Charts <br>Integration into the Umbrella HELM Chart to ensure consistent deployment                                                                                                                                       |
+| [WP-7.1.-D005] | [WP-7.1.-D005] Umbrella HELM Charts for the Hausanschluss developed, tested, and documented                                                                                                                                                                                                                                                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | [WP-7.1.-D005] Umbrella HELM Charts for the Hausanschluss have been developed, tested, and documented.                                                                                                                                                                                                                                                                                                               |
+| 7.1.5.1        | Re-activate Umbrella HELM Charts to the latest release state                                                                                                                                                                                                                                                                                         | The Enablement Services components of the Umbrella HELM Charts must be updated to version R24.12. This includes the following upgrades: <br> Upgrade DTR to version R24.12 (#188) <br>Upgrade EDCs to version R24.12 (#193) <br>Update SSI-DIM-Wallet-Stub to version 0.1.8 (#206)                                                                                                                                                                                                                               | The HELM Chart will then contain the updated versions of the components. <br>After the upgrade, the components (DTR, EDCs, SSI‑DIM‑Wallet‑Stub) run stably without functional impairments. <br>The deployment pipeline for the HELM Chart executes successfully <br>Relevant tests & smoke tests (e.g., integration tests) confirm the migration.                                                                    |
+| 7.1.5.2        | Hierarchical structuring and bundling of Enablement Service components in the Umbrella HELM Chart                                                                                                                                                                                                                                                    | The Umbrella HELM Chart should be structured hierarchically so that related Enablement Service components are grouped into bundles. <br>The Umbrella HELM Chart must have a clear hierarchical structure <br> Each Enablement Service component must be assigned to a unique bundle.<br>No circular dependencies between bundles are allowed.                                                                                                                                                                    | The chart is modular and divided into defined bundles. <br>Each bundle can be deployed and maintained independently.                                                                                                                                                                                                                                                                                                 |
+| 7.1.5.3        | Interchangeability of bundle components via “Bring-Your-Own” components                                                                                                                                                                                                                                                                              | Bundle components should be interchangeable through “Bring-Your-Own” components. <br>“Bring your own” is available for every component and means that these components do not have to be delivered by default with the Umbrella Chart but can be provided by the respective users.                                                                                                                                                                                                                               | Bundle components can be interchanged by “Bring-Your-Own” components.                                                                                                                                                                                                                                                                                                                                                |
+| [WP-7.1.-D006] | [WP-7.1.-D006] Product developed according to a Technology Readiness Level (TRL) of 3                                                                                                                                                                                                                                                                |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | [WP-7.1.-D006] The product is developed according to a Technology Readiness Level (TRL) of 3                                                                                                                                                                                                                                                                                                                         |
+| 7.1.6.1        | POC                                                                                                                                                                                                                                                                                                                                                  | Creation of a POC for the "Hausanschluss" Bundle                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | POC implementation is completed. <br>POC has been presented in a demo                                                                                                                                                                                                                                                                                                                                                |
+| 7.1.6.2        | Deployment Strategy                                                                                                                                                                                                                                                                                                                                  | The provisioning of bundles is carried out independently. <br>There must be an option to selectively activate or deactivate bundles.                                                                                                                                                                                                                                                                                                                                                                             | Configuration is managed via HELM values, allowing flexible adaptation according to the environment.                                                                                                                                                                                                                                                                                                                 |
+
+# 3 AS-IS Analysis
+
+## 3.1 People
+
+### 3.1.1 Target Group Analysis
+
+See "4.1.1 To-be Target Group Analysis" below. No deviations between As-is and To-be target groups have been identified.
+
+## 3.2 Process
+
+### 3.2.1 Use Case View (high-level)
+
+Umbrella Chart is intended for the following Use Cases:
+
+| Actor             | Use case                                                                                             |
+|-------------------|------------------------------------------------------------------------------------------------------|
+| Product Developer | Sandbox Environments: Create local environments to evaluate and experiment with Catena-X components. |
+| Product Developer | Development: Provide a unified setup for contributors and developers working on Tractus-X projects.  |
+| Product Tester    | Testing: Run end-to-end tests for Catena-X services.                                                 |
+| Product Manager   | Evaluate the dataspace to assess if their product can be used within Catena-X.                       |
+
+## 3.4 System
+
+### 3.4.1 Context Delimitation
+
+#### Existing Umbrella Chart Structure
+
+````mermaid
+flowchart
+    subgraph "Umbrella Chart"
+        ChartYaml["Chart.yaml"]
+        subgraph charts
+            Portal["Portal"]
+            CentralIdp["CentralIdp"]
+            DiscoveryFinder["Discovery Finder"]
+            SDFactory["SD-Factory"]
+            SSICredentialIssuer["SSI Credential Issuer"]
+            SemanticHub["Semantic Hub"]
+            BPDM["BPDM"]
+            DataConsumer["Data Consumer"]
+            DataProvider["Data Provider"]
+            BDRS["BDRS"]
+            SSIWalletStub["SSI Wallet Stub"]
+        end
+        subgraph "tx-data-provider"
+            EDC["EDC"]
+            DTR["DTR"]
+            SubmodelServer["Submodel Server"]
+        end
+    end
+
+    ChartYaml --> Portal
+    ChartYaml --> CentralIdp
+    ChartYaml --> DiscoveryFinder
+    ChartYaml --> SDFactory
+    ChartYaml --> SSICredentialIssuer
+    ChartYaml --> SemanticHub
+    ChartYaml --> BPDM
+    ChartYaml --> DataConsumer
+    ChartYaml --> DataProvider
+    ChartYaml --> BDRS
+    ChartYaml --> SSIWalletStub
+    DataConsumer --> EDC
+    DataProvider --> EDC
+    DataProvider --> DTR
+    DataProvider --> SubmodelServer
+````
+
+# 4 TO-BE Design
+
+## 4.1 People
+
+### 4.1.1 Target Group Analysis
+
+Overall data space roles: https://catena-x.net/en/1/catena-x-introduce-implement/how-to-operate-catena-x
+
+The relevant data space roles are:
+
+- Data Consumer
+- Data Provider
+- Enablement Service Provider
+
+Scope: Umbrella HELM Charts
+
+- Enablement Services: These services are included under the umbrella of HELM charts, focusing on enabling
+  functionalities.
+
+Out of Scope: Core services such as Portal or BPDM are not considered within this scope.
+
+Primary target groups:
+
+| No. | Target group                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | Data space roles                                                    | Target group differentiation                                                                                                                                                                                                                                                                            | Behaviour, Needs, Pains & Usage                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+|-----|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| 1   | Developers<ul><li>External Developers (not Tractus-X developers): Utilize the chart for demonstration or evaluation purposes.</li><li>Experienced software and product developers who are developing a business app for a CATENA-X data space. They need to develop the app against the interfaces of the data space and integrate them accordingly.</li><li>They emphasize efficient and cost-effective implementation:<ul><li>Cost Efficiency: They do not want to use expensive SaaS solutions.</li><li>Technical Independence: They lack the knowledge and capacity to deploy the enablement and core services of the data space themselves.</li><li>Focus on Development: They concentrate on application development without delving deeply into the deployment and operation of the underlying infrastructure.</li></ul></li><li>Out of Scope: Developers running tests in test runners are not considered within this scope.</li></ul> | Data Consumer <br/> Data Provider <br/> Enablement Service Provider |                                                                                                                                                                                                                                                                                                         | <ul><li>Needs / sources of information<ul><li><a href="https://eclipse-tractusx.github.io/Kits/">Kit documentation tractus-x</a> for interaction purposes</li><li><a href="https://catenax-ev.github.io/">Catena-X documentation</a> for standards and regulations</li><li><a href="https://github.com/eclipse-tractusx/tractus-x-umbrella">Umbrella documentation</a> for umbrella component information</li></ul></li><li>Challenges → Solution<ul><li>Decentralization e.g. Where are other systems? How to interact with them? → Solution: Umbrella charts and bundles for deployment</li><li>Complex setup → Solution: delivery of small capability bundles</li></ul></li></ul> |
+| 2   | Tester requiring a test system                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | Data Consumer <br/> Data Provider <br/> Enablement Service Provider | <ul><li>Developer (1) tests their feature.</li><li>Tester (2) performs end-to-end testing.</li><li>For the tester, the modular structure is less relevant since they focus on E2E testing, whereas the developer selects the required components.</li><li>The testbed must be easy to deploy.</li></ul> | Same as above from an End-to-end testing perspective.<br/> Typically a tester has less technical know-how than a developer and therefore needs a "one-size-fits-all" (e.g.  Testbed) chart for easier testing.                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+| 3   | SMEs                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | Data Consumer <br/> Data Provider <br/> Enablement Service Provider |                                                                                                                                                                                                                                                                                                         | Need: SMEs developing a service within the Catena-X Data space want an environment to develop and test their service against without the need for expensive SaaS solutions.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+
+## 4.2 Process
+
+### 4.2.1 Use Case View (high-level)
+
+#### Group 1: Product developer
+
+| ID  | Name                                    | Actor             | Description                                                                                                        |
+|-----|-----------------------------------------|-------------------|--------------------------------------------------------------------------------------------------------------------|
+| UC1 | Configure HELM Chart                    | Product Developer | The product developer configures the HELM Chart for the specific environment.                                      |
+| UC2 | Configure Secrets                       | Product Developer | The product developer manages and configures secrets.                                                              |
+| UC3 | Execute Deployment Pipeline             | Product Developer | The product developer successfully executes the deployment pipeline for the HELM Chart.                            |
+| UC4 | Integrate EDC, DTR, and Identity Wallet | Product Developer | The actors integrate the components EDC, Digital Twin Registry, and Identity Wallet for seamless interoperability. |
+| UC5 | Set Up Connection Infrastructure        | Product Developer | The actor sets up the connection infrastructure for linking to the central data space infrastructure.              |
+| UC6 | Maintain Infrastructure Module          | Product Developer | The product developer maintains the modular architecture of the HELM Chart.                                        |
+| UC7 | Ensure Scalability                      | Product Developer | The product developer ensures scalability to support growing numbers of users and data volumes.                    |
+| UC8 | Sandbox Environments                    | Product Developer | The product developer creates local environments to evaluate and experiment with Catena-X components.              |
+
+#### Group 2: Product Tester
+
+| ID  | Name        | Actor          | Description                                                     |
+|-----|-------------|----------------|-----------------------------------------------------------------|
+| UC9 | E2E Testing | Product Tester | The product tester runs end-to-end tests for Catena-X services. |
+
+#### Group 3: Product Manager
+
+| ID   | Name                 | Actor           | Description                                                                                         |
+|------|----------------------|-----------------|-----------------------------------------------------------------------------------------------------|
+| UC10 | Dataspace Evaluation | Product Manager | The Product manager evaluates the dataspace to assess if their product can be used within Catena-X. |
+
+#### Use Case diagram
+
+````mermaid
+flowchart LR
+    PD[Product Developer]
+    PT[Product Tester]
+    PM[Product Manager]
+    UC1[Configure HELM Chart]
+    UC2[Configure Secrets]
+    UC3[Execute Deployment Pipeline]
+    UC4[Integrate EDC, DTR, and Identity Wallet]
+    UC5[Set Up Connection Infrastructure]
+    UC6[Maintain Infrastructure Module]
+    UC7[Ensure Scalability]
+    UC8[Sandbox Environments]
+    UC9[E2E Testing]
+    UC10[Dataspace Evaluation]
+    PD --> UC1
+    PD --> UC2
+    PD --> UC3
+    PD --> UC4
+    PD --> UC5
+    PD --> UC6
+    PD --> UC7
+    PD --> UC8
+    PT --> UC9
+    PM --> UC10
+````
+
+### 4.2.2 Business Process (SCC Artifact)
+
+#### Chart Release Process
+
+Charts will be released using the already existing workflow in the Umbrella Chart repository. The workflow will
+automatically release a Chart, once it is pushed to the "charts/" directory with a new Chart version.
+
+Chart versions should follow [Semantic Versioning](https://semver.org/)
+
+#### Capability Bundle Structure
+
+Capability bundle modularization for the Tractus-X Umbrella Helm chart is a sound architectural and operational design.
+It aligns with both the domain-driven architecture of Catena-X (data exchange, digital twin, identity, semantics are
+distinct domains) and with Kubernetes best practices for managing complex applications (using an umbrella chart to
+bundle related microservices).
+
+Each bundle is self-sufficient, which improves isolation (failures or changes in one domain have minimal impact on
+others) and allows scaling and upgrading along domain lines. It simplifies deployment by allowing “plug-and-play”
+capabilities: an Enablement Service Provider can decide which bundles to operate based on its role e.g., include the
+Digital Twin and Semantic bundles if offering an asset-rich service, or omit them if not. The approach is consistent
+with how other OSS projects deliver multi-component systems, providing one-step installation without sacrificing the
+ability to tweak individual parts.
+
+Why this structure was proposed:
+
+1. **Clear Separation of Concerns**  
+   Each capability bundle (e.g. EDC Data Transfer, Digital Twin, Identity & Trust, Semantic Model) aligns with a
+   specific functional domain. This separation makes it easier to understand the role of each service (e.g., the EDC
+   connector vs. the digital twin registry), reduces coupling between unrelated components, and ultimately makes
+   maintenance and troubleshooting more straightforward.
+2. **Modular Deployment**  
+   Some participants in Catena-X may not need all services (e.g., some might not use the Digital Twin bundle). By
+   structuring the umbrella chart into bundles, a user can enable just those needed capabilities. This leads to leaner
+   installs and avoids unnecessary resource usage.
+3. **Best Practices with Helm**  
+   Using an umbrella chart with subcharts/bundles is a well-recognized Helm best practice for complex applications. It
+   allows a single helm install to set up multiple microservices while still allowing each service to have its own
+   lifecycle, configuration, and version.
+4. **Alignment with Domain-Driven Approach**  
+   Catena-X is organized around distinct, loosely-coupled “building blocks.” Bundling services by domain matches this
+   architectural vision. It’s clear which domain each set of microservices belongs to (EDC for data exchange, identity
+   for credential management, etc.). This clarity also helps new adopters navigate the ecosystem.
+
+````mermaid
+%%{init: {"flowchart": {"subGraphTitleMargin": { "bottom": 10}}}}%%
+flowchart LR
+    subgraph A["Core Services"]
+        Vault["Vault"]
+    end
+
+    subgraph B["Capability Bundle: Identity & Trust"]
+        SSIWalletStub["SSI Wallet Stub"]
+    end
+
+    subgraph C["Capability Bundle: Dataspace Connector"]
+        EDC["EDC"]
+        EDCDB["EDC DB"]
+        EDC .-> EDCDB
+    end
+
+    subgraph "Capability Bundle: Digital Twin"
+        DTR["DTR"]
+        DTRDB["DTR DB"]
+        DTR .-> DTRDB
+    end
+
+    subgraph "Capability Bundle: Data Persistence Layer"
+        SimpleSubmodelServer["Simple Submodel Server"]
+    end
+
+    subgraph "Hausanschluss Actors"
+        subgraph "Data Provider"
+            DataProvider["Data Provider"]
+        end
+        subgraph "Data Consumer"
+            DataConsumer["Data Consumer"]
+        end
+        subgraph "Enablement Provider"
+            EnablementProvider["Enablement Provider"]
+        end
+    end
+
+    EDC -..-> SSIWalletStub
+    EDC -..-> Vault
+    DataProvider --> EDC
+    DataProvider --> DTR
+    DataProvider --> SimpleSubmodelServer
+    DataConsumer --> EDC
+    EnablementProvider --> DataConsumer
+    EnablementProvider --> DataProvider
+````
+
+#### Deployment strategies
+
+##### Role: Data Provider
+
+The standard data provider role consists of a EDC, DTR and Submodel Server Bundles. EDC uses the Identity Wallet Bundle.
+
+````mermaid
+flowchart BT
+    A["Capability Bundle: Identity & Trust"]
+    B["Capability Bundle: Data Persistence Layer"]
+    C["Capability Bundle: Dataspace Connector"]
+    D["Capability Bundle: Digital Twin"]
+    E("Application to be tested/developed")
+    style E fill:#afafaf,color:black
+    F{{"Developer/Tester"}}
+    E --> B
+    E --> C
+    E --> D
+    C --> A
+    F --> E
+````
+
+##### Role: Data Consumer
+
+The standard data consumer role consists of only the EDC Bundle and the Identity Wallet Bundle.
+
+````mermaid
+flowchart BT
+    A["Capability Bundle: Identity & Trust"]
+    B["Capability Bundle: Dataspace Connector"]
+    C("Application to be tested/developed")
+    style C fill:#afafaf,color:black
+    D{{"Developer/Tester"}}
+    C --> B
+    B --> A
+    D --> C
+````
+
+##### Role: Enablement Provider
+
+The Enablement Provider roles consists of both the Data Consumer and Data Provider bundles. This allows provisioning of
+data and the consumption of the provisioned data by a application.
+
+````mermaid
+flowchart BT
+    A["Capability Bundle: Identity & Trust"]
+    B["Capability Bundle: Data Persistence Layer"]
+    C("Application to be tested/developed")
+    style C fill:#afafaf,color:black
+    D["Capability Bundle: Digital Twin"]
+    E["Capability Bundle: Dataspace Connector (Provider)"]
+    F["Capability Bundle: Dataspace Connector (Consumer)"]
+    G{{"Developer/Tester"}}
+    C --> B
+    C --> D
+    C --> E
+    C --> F
+    E --> A
+    F --> A
+    G --> C
+````
+
+##### Bring you own
path: docs/concept/TAP7.1-solution-design.md
user: login: mgarciaLKS
body: ```suggestion
##### Bring your own
```
created_at: 2025-04-03T10:13:09Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,516 @@
+# Solution Design "Hausanschluss" Bundle Concept
+
+# 1 Business Case
+
+## 1.1 Executive Summary
+
+The "Hausanschluss" Bundle aims to simplify the installation of the enablement services Eclipse Dataspace
+Connector (EDC), Digital Twin Registry (DTR), and their supporting components. By developing a flexible, parameterizable
+installation package, the project seeks to reduce deployment complexity and lower barriers to participation in the
+Catena‑X data space. This bundle will enable independent component updates and support a modular "bring your own"
+approach, ultimately fostering a more efficient and accessible ecosystem for diverse participants—such as testers,
+external product developers, product testers, and small and medium-sized enterprises.
+
+## 1.2 Business Need
+
+Current deployment methods for data space integration are complex and require significant manual effort. This PoC
+addresses the need to:
+
+- **Reduce Complexity:** Simplify the deployment topology by bundling components into capabilities.
+- **Automate Deployment:** Provide an automated installation package using Kubernetes and HELM.
+- **Minimize Configuration Overhead:** Streamline the integration process by providing pre-configured bundles that require only minimal manual parameter adjustments.
+- **Extend Documentation:** Provide a detailed documentation tailored to the target groups.
+- **Enable Extension:** Design the system to allow the seamless addition of new components or capabilities.
+
+## 1.3 Objectives
+
+- **Simplify Deployment and Maintenance:** Develop an installation package that minimizes manual configuration through
+  automation.
+- **Ensure Modularity:** Structure the bundle so that components can be independently installed, updated, or replaced
+  without affecting other services.
+- **Facilitate Flexibility:** Implement a "bring your own" model for key components, such as EDC, PostgreSQL, and HashiCorp
+  Vault, to allow tailored deployments that meet specific needs.
+- **Increase Accessibility**: Lower entry barriers for new participants by reducing technical complexity and operational
+  dependencies.
+- **Scalability:** Structure the bundles so that they can be deployed multiple times.
+
+## 1.4 Expected Deliverables
+
+- **PoC Documentation:** A concept and architecture overview highlighting the modular design.
+- **Modular Installation Package:** A set of HELM charts for deploying the enablement service bundles:
+    - **Dataspace Connector:** Including the Eclipse Dataspace Connector, EDC PostgreSQL, and HashiCorp Vault.
+    - **Digital Twin Bundle:** Featuring components such as the Decentral DT Registry (with “bring your own” PostgreSQL)
+    - **Data Persitence Layer Bundle:** Including a simple Submodel Server to store semantic data.
+    - **Identity Wallet Bundle:** Covering the Identity Wallet functionality.
+- **Demonstration Environment:** A test deployment showcasing reduced complexity and improved efficiency.
+- **Basic User Guide:** Instructions on how to deploy and update the PoC bundle.
+
+## 1.5 Benefits
+
+- **Operational Efficiency:** Faster and more reliable deployments with less manual work.
+- **Scalability:** A modular design that can be scaled or adapted for future full-scale deployments.
+- **Ease of Adoption:** Simplified deployment processes make it easier for testers and external developers to engage.
+
+## 1.6. Dependencies
+
+- **Interoperability** with the CATENA‑X standards.
+
+## 1.7. Success Criteria
+
+- **Technology Readiness Level:** Achievement of a Technology Readiness Level (TRL) of 3, as specified in the requirements.
+- **Functional PoC Deployment:** Demonstrated automated, modular installation with reduced manual steps.
+- **Simplified Configuration:** Clear evidence of reduced configuration complexity.
+- **Positive Feedback:** End-user validation from a select group of demo participants and the Tractus-X community.
+- **Documentation Completeness:** Availability of concise deployment and user guides.
+
+## 1.8. Out of Scope
+
+- **Full Production Readiness:** This PoC is not intended to be a production-ready solution.
+- **Core Services Exclusion:** Core services are not part of the Hausanschluss Bundles.
+- **App Provider Role:** The role of App Provider is considered out of scope for this deployment.
+- **Alternative Deployment Techniques:** While the evaluation of alternative deployment methods is acknowledged, the primary
+  focus remains on Kubernetes and HELM-based deployment.
+
+# 2 Requirements Analysis
+
+## 2.1 Assumptions
+
+## 2.2 Requirements Catalog
+
+| ID             | Requirement                                                                                                                                                                                                                                                                                                                                          | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | Deliverables / Acceptance Criteria                                                                                                                                                                                                                                                                                                                                                                                   |
+|----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| [WP-7.1.-D001] | The Hausanschluss Bundle aims to simplify the installation and maintenance of the EDC and other components that together ensure a “Hausanschluss”. A flexible, parameterizable installation package is intended to reduce complexity and make integration more efficient, thereby simplifying participation in Catena‑X for additional participants. | Specification and development of a flexible, parameterizable installation package that reduces the complexity of installing and maintaining the required components for seamless integration into the Catena‑X data space. This package should facilitate updates and new versions, making participation in Catena‑X more efficient and accessible. In doing so, SMEs shall be enabled to participate without high costs or dependency on SaaS providers while maintaining control over their IT infrastructure. | [WP-7.1.-D001] Concept for the Hausanschluss is created                                                                                                                                                                                                                                                                                                                                                              |
+| 7.1.1.1        | The solution concept must define the Capability Bundles structures to be implemented. For each Capability Bundle, the included bundles and their versions are mapped.                                                                                                                                                                                | "The following Capability Bundle structure is implemented:                                                                                                                                                                                                                                                                                                                                                                                                                                                       | The structure of the Capability Bundles for the Enablement Services has been specified. For version R24.12 it is clearly defined which Tractus‑X services and components are assigned to each Capability Bundle                                                                                                                                                                                                      |
+| 7.1.1.2        | Definition of Data Space Roles                                                                                                                                                                                                                                                                                                                       | Data Consumer, Data Provider, Enablement Service Provider                                                                                                                                                                                                                                                                                                                                                                                                                                                        | As part of the target group analysis, the target groups are defined and aligned with the data space roles. <br>Mapping from data space role to target group has been completed. <br>Mapping from target group to data space role has been completed. <br>An assignment of data space roles to Capability Bundles has been made.                                                                                      |
+| 7.1.1.4        | Modularity & Maintainability: No dependencies between Capability Bundles                                                                                                                                                                                                                                                                             | Unique assignment of components and services to a defined Capability Bundle. <br>Each component and service should be assigned to only one Capability Bundle. <br>Dependencies between Capability Bundles are allowed.                                                                                                                                                                                                                                                                                           | Components and Services should only be part of one bundle. <br>Each bundle must be deployable in isolation and can be installed, updated, or removed independently. <br>Capability Bundles must be organized in separate HELM sub‑charts. <br>Circular dependencies between bundles must be avoided.                                                                                                                 |
+| 7.1.1.5        | Modularity & Maintainability: Concept for reducing deployment complexity                                                                                                                                                                                                                                                                             | The system deployment should be optimized to reduce the existing complexity. The goal is to make the provisioning process more efficient, robust, and easier to maintain.                                                                                                                                                                                                                                                                                                                                        | **Simplification of deployment processes:** A reduction of manual configuration steps has been achieved. <br>**Transparency and traceability:** Clearly documented deployment steps are provided. <br>**Improvements of Chart configuration by:** <br>usage of template  <br>reducing configuration options <br>reducing manual steps in the setup                                                                   |
+| 7.1.1.6        | Modularity & Maintainability                                                                                                                                                                                                                                                                                                                         | Charts are published automatically.                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | Charts are published via a publicly accessible charts repository.                                                                                                                                                                                                                                                                                                                                                    |
+| 7.1.1.13       | Solution Concept                                                                                                                                                                                                                                                                                                                                     | Creation of a solution design for the “Hausanschluss” Bundle.                                                                                                                                                                                                                                                                                                                                                                                                                                                    | The solution design for the "Hausanschluss" Bundle is created. <br>The solution design for the "Hausanschluss" Bundle ispublished in the repository: https://github.com/eclipse-tractusx/tractus-x-umbrella.                                                                                                                                                                                                         |
+| 7.1.1.14       | Scalability of Enablement Services                                                                                                                                                                                                                                                                                                                   | Scalability of Enablement Services                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | Developers should be able to deploy an arbitrary number of Enablement Services. <br>Example: Up to 3 EDCs can be provided.                                                                                                                                                                                                                                                                                           |
+| 7.1.1.16       | Interoperability                                                                                                                                                                                                                                                                                                                                     | Interoperability                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | Interoperability with the CATENA‑X standards. <br>This interoperability is documented and traceable.                                                                                                                                                                                                                                                                                                                 |
+| [WP-7.1.-D002] | [WP-7.1.-D002] Target group for the specification is defined.                                                                                                                                                                                                                                                                                        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | [WP-7.1.-D002] Target group for the specification is defined.                                                                                                                                                                                                                                                                                                                                                        |
+| 7.1.2.1        | Target Group Analysis                                                                                                                                                                                                                                                                                                                                | The target group analysis for the "Hausanschluss Bundle"is defined.                                                                                                                                                                                                                                                                                                                                                                                                                                              | The analysis has been conducted. <br>The target group is included in the solution concept <br>To be clarified: What is included in the Hausanschluss and who can operate it in which scenario (OEM, SME, service provider, etc.).                                                                                                                                                                                    |
+| [WP-7.1.-D003] | [WP-7.1.-D003] Decentralized components and services defined                                                                                                                                                                                                                                                                                         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | [WP-7.1.-D003] Decentralized components and services have been defined.                                                                                                                                                                                                                                                                                                                                              |
+| 7.1.3.1        | See [WP-7.1.-D001-AC001]                                                                                                                                                                                                                                                                                                                             |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | See [WP-7.1.-D001-AC001]                                                                                                                                                                                                                                                                                                                                                                                             |
+| [WP-7.1.-D004] | [WP-7.1.-D004] Documentation of the Hausanschluss Bundle is completed                                                                                                                                                                                                                                                                                |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | [WP-7.1.-D004] Documentation of the Hausanschluss Bundle is completed                                                                                                                                                                                                                                                                                                                                                |
+| 7.1.4.1        | Documentation of the Hausanschluss-Bundles                                                                                                                                                                                                                                                                                                           | Usability                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | Documentation is provided that enables an experienced product developer - with knowledge of Helm Charts, Docker, and Vaults - to deploy the chart independently without external help. <br>A troubleshooting and FAQ section is included to support the developer. <br>Prerequisites, skills, and technology requirements are outlined, detailing what a developer must know to perform the deployment autonomously. |
+| 7.1.4.2        | Documentation of the Hausanschluss-Bundles                                                                                                                                                                                                                                                                                                           | Documentation of the Hausanschluss-Bundles is completed.                                                                                                                                                                                                                                                                                                                                                                                                                                                         | Documentation is provided for: <br>Configuration of the defined bundles according to the specified requirements and parameters <br>Integration of the documentation into the Umbrella HELM Charts <br>Integration into the Umbrella HELM Chart to ensure consistent deployment                                                                                                                                       |
+| [WP-7.1.-D005] | [WP-7.1.-D005] Umbrella HELM Charts for the Hausanschluss developed, tested, and documented                                                                                                                                                                                                                                                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | [WP-7.1.-D005] Umbrella HELM Charts for the Hausanschluss have been developed, tested, and documented.                                                                                                                                                                                                                                                                                                               |
+| 7.1.5.1        | Re-activate Umbrella HELM Charts to the latest release state                                                                                                                                                                                                                                                                                         | The Enablement Services components of the Umbrella HELM Charts must be updated to version R24.12. This includes the following upgrades: <br> Upgrade DTR to version R24.12 (#188) <br>Upgrade EDCs to version R24.12 (#193) <br>Update SSI-DIM-Wallet-Stub to version 0.1.8 (#206)                                                                                                                                                                                                                               | The HELM Chart will then contain the updated versions of the components. <br>After the upgrade, the components (DTR, EDCs, SSI‑DIM‑Wallet‑Stub) run stably without functional impairments. <br>The deployment pipeline for the HELM Chart executes successfully <br>Relevant tests & smoke tests (e.g., integration tests) confirm the migration.                                                                    |
+| 7.1.5.2        | Hierarchical structuring and bundling of Enablement Service components in the Umbrella HELM Chart                                                                                                                                                                                                                                                    | The Umbrella HELM Chart should be structured hierarchically so that related Enablement Service components are grouped into bundles. <br>The Umbrella HELM Chart must have a clear hierarchical structure <br> Each Enablement Service component must be assigned to a unique bundle.<br>No circular dependencies between bundles are allowed.                                                                                                                                                                    | The chart is modular and divided into defined bundles. <br>Each bundle can be deployed and maintained independently.                                                                                                                                                                                                                                                                                                 |
+| 7.1.5.3        | Interchangeability of bundle components via “Bring-Your-Own” components                                                                                                                                                                                                                                                                              | Bundle components should be interchangeable through “Bring-Your-Own” components. <br>“Bring your own” is available for every component and means that these components do not have to be delivered by default with the Umbrella Chart but can be provided by the respective users.                                                                                                                                                                                                                               | Bundle components can be interchanged by “Bring-Your-Own” components.                                                                                                                                                                                                                                                                                                                                                |
+| [WP-7.1.-D006] | [WP-7.1.-D006] Product developed according to a Technology Readiness Level (TRL) of 3                                                                                                                                                                                                                                                                |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | [WP-7.1.-D006] The product is developed according to a Technology Readiness Level (TRL) of 3                                                                                                                                                                                                                                                                                                                         |
+| 7.1.6.1        | POC                                                                                                                                                                                                                                                                                                                                                  | Creation of a POC for the "Hausanschluss" Bundle                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | POC implementation is completed. <br>POC has been presented in a demo                                                                                                                                                                                                                                                                                                                                                |
+| 7.1.6.2        | Deployment Strategy                                                                                                                                                                                                                                                                                                                                  | The provisioning of bundles is carried out independently. <br>There must be an option to selectively activate or deactivate bundles.                                                                                                                                                                                                                                                                                                                                                                             | Configuration is managed via HELM values, allowing flexible adaptation according to the environment.                                                                                                                                                                                                                                                                                                                 |
+
+# 3 AS-IS Analysis
+
+## 3.1 People
+
+### 3.1.1 Target Group Analysis
+
+See "4.1.1 To-be Target Group Analysis" below. No deviations between As-is and To-be target groups have been identified.
+
+## 3.2 Process
+
+### 3.2.1 Use Case View (high-level)
+
+Umbrella Chart is intended for the following Use Cases:
+
+| Actor             | Use case                                                                                             |
+|-------------------|------------------------------------------------------------------------------------------------------|
+| Product Developer | Sandbox Environments: Create local environments to evaluate and experiment with Catena-X components. |
+| Product Developer | Development: Provide a unified setup for contributors and developers working on Tractus-X projects.  |
+| Product Tester    | Testing: Run end-to-end tests for Catena-X services.                                                 |
+| Product Manager   | Evaluate the dataspace to assess if their product can be used within Catena-X.                       |
+
+## 3.4 System
+
+### 3.4.1 Context Delimitation
+
+#### Existing Umbrella Chart Structure
+
+````mermaid
+flowchart
+    subgraph "Umbrella Chart"
+        ChartYaml["Chart.yaml"]
+        subgraph charts
+            Portal["Portal"]
+            CentralIdp["CentralIdp"]
+            DiscoveryFinder["Discovery Finder"]
+            SDFactory["SD-Factory"]
+            SSICredentialIssuer["SSI Credential Issuer"]
+            SemanticHub["Semantic Hub"]
+            BPDM["BPDM"]
+            DataConsumer["Data Consumer"]
+            DataProvider["Data Provider"]
+            BDRS["BDRS"]
+            SSIWalletStub["SSI Wallet Stub"]
+        end
+        subgraph "tx-data-provider"
+            EDC["EDC"]
+            DTR["DTR"]
+            SubmodelServer["Submodel Server"]
+        end
+    end
+
+    ChartYaml --> Portal
+    ChartYaml --> CentralIdp
+    ChartYaml --> DiscoveryFinder
+    ChartYaml --> SDFactory
+    ChartYaml --> SSICredentialIssuer
+    ChartYaml --> SemanticHub
+    ChartYaml --> BPDM
+    ChartYaml --> DataConsumer
+    ChartYaml --> DataProvider
+    ChartYaml --> BDRS
+    ChartYaml --> SSIWalletStub
+    DataConsumer --> EDC
+    DataProvider --> EDC
+    DataProvider --> DTR
+    DataProvider --> SubmodelServer
+````
+
+# 4 TO-BE Design
+
+## 4.1 People
+
+### 4.1.1 Target Group Analysis
+
+Overall data space roles: https://catena-x.net/en/1/catena-x-introduce-implement/how-to-operate-catena-x
path: docs/concept/TAP7.1-solution-design.md
user: login: mgarciaLKS
body: Link not working
created_at: 2025-04-03T10:14:23Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,516 @@
+# Solution Design "Hausanschluss" Bundle Concept
+
+# 1 Business Case
+
+## 1.1 Executive Summary
+
+The "Hausanschluss" Bundle aims to simplify the installation of the enablement services Eclipse Dataspace
+Connector (EDC), Digital Twin Registry (DTR), and their supporting components. By developing a flexible, parameterizable
+installation package, the project seeks to reduce deployment complexity and lower barriers to participation in the
+Catena‑X data space. This bundle will enable independent component updates and support a modular "bring your own"
+approach, ultimately fostering a more efficient and accessible ecosystem for diverse participants—such as testers,
+external product developers, product testers, and small and medium-sized enterprises.
+
+## 1.2 Business Need
+
+Current deployment methods for data space integration are complex and require significant manual effort. This PoC
+addresses the need to:
+
+- **Reduce Complexity:** Simplify the deployment topology by bundling components into capabilities.
+- **Automate Deployment:** Provide an automated installation package using Kubernetes and HELM.
+- **Minimize Configuration Overhead:** Streamline the integration process by providing pre-configured bundles that require only minimal manual parameter adjustments.
+- **Extend Documentation:** Provide a detailed documentation tailored to the target groups.
+- **Enable Extension:** Design the system to allow the seamless addition of new components or capabilities.
+
+## 1.3 Objectives
+
+- **Simplify Deployment and Maintenance:** Develop an installation package that minimizes manual configuration through
+  automation.
+- **Ensure Modularity:** Structure the bundle so that components can be independently installed, updated, or replaced
+  without affecting other services.
+- **Facilitate Flexibility:** Implement a "bring your own" model for key components, such as EDC, PostgreSQL, and HashiCorp
+  Vault, to allow tailored deployments that meet specific needs.
+- **Increase Accessibility**: Lower entry barriers for new participants by reducing technical complexity and operational
+  dependencies.
+- **Scalability:** Structure the bundles so that they can be deployed multiple times.
+
+## 1.4 Expected Deliverables
+
+- **PoC Documentation:** A concept and architecture overview highlighting the modular design.
+- **Modular Installation Package:** A set of HELM charts for deploying the enablement service bundles:
+    - **Dataspace Connector:** Including the Eclipse Dataspace Connector, EDC PostgreSQL, and HashiCorp Vault.
+    - **Digital Twin Bundle:** Featuring components such as the Decentral DT Registry (with “bring your own” PostgreSQL)
+    - **Data Persitence Layer Bundle:** Including a simple Submodel Server to store semantic data.
+    - **Identity Wallet Bundle:** Covering the Identity Wallet functionality.
+- **Demonstration Environment:** A test deployment showcasing reduced complexity and improved efficiency.
+- **Basic User Guide:** Instructions on how to deploy and update the PoC bundle.
+
+## 1.5 Benefits
+
+- **Operational Efficiency:** Faster and more reliable deployments with less manual work.
+- **Scalability:** A modular design that can be scaled or adapted for future full-scale deployments.
+- **Ease of Adoption:** Simplified deployment processes make it easier for testers and external developers to engage.
+
+## 1.6. Dependencies
+
+- **Interoperability** with the CATENA‑X standards.
+
+## 1.7. Success Criteria
+
+- **Technology Readiness Level:** Achievement of a Technology Readiness Level (TRL) of 3, as specified in the requirements.
+- **Functional PoC Deployment:** Demonstrated automated, modular installation with reduced manual steps.
+- **Simplified Configuration:** Clear evidence of reduced configuration complexity.
+- **Positive Feedback:** End-user validation from a select group of demo participants and the Tractus-X community.
+- **Documentation Completeness:** Availability of concise deployment and user guides.
+
+## 1.8. Out of Scope
+
+- **Full Production Readiness:** This PoC is not intended to be a production-ready solution.
+- **Core Services Exclusion:** Core services are not part of the Hausanschluss Bundles.
+- **App Provider Role:** The role of App Provider is considered out of scope for this deployment.
+- **Alternative Deployment Techniques:** While the evaluation of alternative deployment methods is acknowledged, the primary
+  focus remains on Kubernetes and HELM-based deployment.
+
+# 2 Requirements Analysis
+
+## 2.1 Assumptions
+
+## 2.2 Requirements Catalog
+
+| ID             | Requirement                                                                                                                                                                                                                                                                                                                                          | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | Deliverables / Acceptance Criteria                                                                                                                                                                                                                                                                                                                                                                                   |
+|----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| [WP-7.1.-D001] | The Hausanschluss Bundle aims to simplify the installation and maintenance of the EDC and other components that together ensure a “Hausanschluss”. A flexible, parameterizable installation package is intended to reduce complexity and make integration more efficient, thereby simplifying participation in Catena‑X for additional participants. | Specification and development of a flexible, parameterizable installation package that reduces the complexity of installing and maintaining the required components for seamless integration into the Catena‑X data space. This package should facilitate updates and new versions, making participation in Catena‑X more efficient and accessible. In doing so, SMEs shall be enabled to participate without high costs or dependency on SaaS providers while maintaining control over their IT infrastructure. | [WP-7.1.-D001] Concept for the Hausanschluss is created                                                                                                                                                                                                                                                                                                                                                              |
+| 7.1.1.1        | The solution concept must define the Capability Bundles structures to be implemented. For each Capability Bundle, the included bundles and their versions are mapped.                                                                                                                                                                                | "The following Capability Bundle structure is implemented:                                                                                                                                                                                                                                                                                                                                                                                                                                                       | The structure of the Capability Bundles for the Enablement Services has been specified. For version R24.12 it is clearly defined which Tractus‑X services and components are assigned to each Capability Bundle                                                                                                                                                                                                      |
+| 7.1.1.2        | Definition of Data Space Roles                                                                                                                                                                                                                                                                                                                       | Data Consumer, Data Provider, Enablement Service Provider                                                                                                                                                                                                                                                                                                                                                                                                                                                        | As part of the target group analysis, the target groups are defined and aligned with the data space roles. <br>Mapping from data space role to target group has been completed. <br>Mapping from target group to data space role has been completed. <br>An assignment of data space roles to Capability Bundles has been made.                                                                                      |
+| 7.1.1.4        | Modularity & Maintainability: No dependencies between Capability Bundles                                                                                                                                                                                                                                                                             | Unique assignment of components and services to a defined Capability Bundle. <br>Each component and service should be assigned to only one Capability Bundle. <br>Dependencies between Capability Bundles are allowed.                                                                                                                                                                                                                                                                                           | Components and Services should only be part of one bundle. <br>Each bundle must be deployable in isolation and can be installed, updated, or removed independently. <br>Capability Bundles must be organized in separate HELM sub‑charts. <br>Circular dependencies between bundles must be avoided.                                                                                                                 |
path: docs/concept/TAP7.1-solution-design.md
user: login: ds-jhartmann
body: Thanks for the hint. You're right, this description contradicts itself. I added a updated version
created_at: 2025-04-03T12:10:12Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,516 @@
+# Solution Design "Hausanschluss" Bundle Concept
+
+# 1 Business Case
+
+## 1.1 Executive Summary
+
+The "Hausanschluss" Bundle aims to simplify the installation of the enablement services Eclipse Dataspace
+Connector (EDC), Digital Twin Registry (DTR), and their supporting components. By developing a flexible, parameterizable
+installation package, the project seeks to reduce deployment complexity and lower barriers to participation in the
+Catena‑X data space. This bundle will enable independent component updates and support a modular "bring your own"
+approach, ultimately fostering a more efficient and accessible ecosystem for diverse participants—such as testers,
+external product developers, product testers, and small and medium-sized enterprises.
+
+## 1.2 Business Need
+
+Current deployment methods for data space integration are complex and require significant manual effort. This PoC
+addresses the need to:
+
+- **Reduce Complexity:** Simplify the deployment topology by bundling components into capabilities.
+- **Automate Deployment:** Provide an automated installation package using Kubernetes and HELM.
+- **Minimize Configuration Overhead:** Streamline the integration process by providing pre-configured bundles that require only minimal manual parameter adjustments.
+- **Extend Documentation:** Provide a detailed documentation tailored to the target groups.
+- **Enable Extension:** Design the system to allow the seamless addition of new components or capabilities.
+
+## 1.3 Objectives
+
+- **Simplify Deployment and Maintenance:** Develop an installation package that minimizes manual configuration through
+  automation.
+- **Ensure Modularity:** Structure the bundle so that components can be independently installed, updated, or replaced
+  without affecting other services.
+- **Facilitate Flexibility:** Implement a "bring your own" model for key components, such as EDC, PostgreSQL, and HashiCorp
+  Vault, to allow tailored deployments that meet specific needs.
+- **Increase Accessibility**: Lower entry barriers for new participants by reducing technical complexity and operational
+  dependencies.
+- **Scalability:** Structure the bundles so that they can be deployed multiple times.
+
+## 1.4 Expected Deliverables
+
+- **PoC Documentation:** A concept and architecture overview highlighting the modular design.
+- **Modular Installation Package:** A set of HELM charts for deploying the enablement service bundles:
+    - **Dataspace Connector:** Including the Eclipse Dataspace Connector, EDC PostgreSQL, and HashiCorp Vault.
+    - **Digital Twin Bundle:** Featuring components such as the Decentral DT Registry (with “bring your own” PostgreSQL)
+    - **Data Persitence Layer Bundle:** Including a simple Submodel Server to store semantic data.
+    - **Identity Wallet Bundle:** Covering the Identity Wallet functionality.
+- **Demonstration Environment:** A test deployment showcasing reduced complexity and improved efficiency.
+- **Basic User Guide:** Instructions on how to deploy and update the PoC bundle.
+
+## 1.5 Benefits
+
+- **Operational Efficiency:** Faster and more reliable deployments with less manual work.
+- **Scalability:** A modular design that can be scaled or adapted for future full-scale deployments.
+- **Ease of Adoption:** Simplified deployment processes make it easier for testers and external developers to engage.
+
+## 1.6. Dependencies
+
+- **Interoperability** with the CATENA‑X standards.
+
+## 1.7. Success Criteria
+
+- **Technology Readiness Level:** Achievement of a Technology Readiness Level (TRL) of 3, as specified in the requirements.
+- **Functional PoC Deployment:** Demonstrated automated, modular installation with reduced manual steps.
+- **Simplified Configuration:** Clear evidence of reduced configuration complexity.
+- **Positive Feedback:** End-user validation from a select group of demo participants and the Tractus-X community.
+- **Documentation Completeness:** Availability of concise deployment and user guides.
+
+## 1.8. Out of Scope
+
+- **Full Production Readiness:** This PoC is not intended to be a production-ready solution.
+- **Core Services Exclusion:** Core services are not part of the Hausanschluss Bundles.
+- **App Provider Role:** The role of App Provider is considered out of scope for this deployment.
+- **Alternative Deployment Techniques:** While the evaluation of alternative deployment methods is acknowledged, the primary
+  focus remains on Kubernetes and HELM-based deployment.
+
+# 2 Requirements Analysis
+
+## 2.1 Assumptions
+
+## 2.2 Requirements Catalog
+
+| ID             | Requirement                                                                                                                                                                                                                                                                                                                                          | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | Deliverables / Acceptance Criteria                                                                                                                                                                                                                                                                                                                                                                                   |
+|----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| [WP-7.1.-D001] | The Hausanschluss Bundle aims to simplify the installation and maintenance of the EDC and other components that together ensure a “Hausanschluss”. A flexible, parameterizable installation package is intended to reduce complexity and make integration more efficient, thereby simplifying participation in Catena‑X for additional participants. | Specification and development of a flexible, parameterizable installation package that reduces the complexity of installing and maintaining the required components for seamless integration into the Catena‑X data space. This package should facilitate updates and new versions, making participation in Catena‑X more efficient and accessible. In doing so, SMEs shall be enabled to participate without high costs or dependency on SaaS providers while maintaining control over their IT infrastructure. | [WP-7.1.-D001] Concept for the Hausanschluss is created                                                                                                                                                                                                                                                                                                                                                              |
+| 7.1.1.1        | The solution concept must define the Capability Bundles structures to be implemented. For each Capability Bundle, the included bundles and their versions are mapped.                                                                                                                                                                                | "The following Capability Bundle structure is implemented:                                                                                                                                                                                                                                                                                                                                                                                                                                                       | The structure of the Capability Bundles for the Enablement Services has been specified. For version R24.12 it is clearly defined which Tractus‑X services and components are assigned to each Capability Bundle                                                                                                                                                                                                      |
+| 7.1.1.2        | Definition of Data Space Roles                                                                                                                                                                                                                                                                                                                       | Data Consumer, Data Provider, Enablement Service Provider                                                                                                                                                                                                                                                                                                                                                                                                                                                        | As part of the target group analysis, the target groups are defined and aligned with the data space roles. <br>Mapping from data space role to target group has been completed. <br>Mapping from target group to data space role has been completed. <br>An assignment of data space roles to Capability Bundles has been made.                                                                                      |
+| 7.1.1.4        | Modularity & Maintainability: No dependencies between Capability Bundles                                                                                                                                                                                                                                                                             | Unique assignment of components and services to a defined Capability Bundle. <br>Each component and service should be assigned to only one Capability Bundle. <br>Dependencies between Capability Bundles are allowed.                                                                                                                                                                                                                                                                                           | Components and Services should only be part of one bundle. <br>Each bundle must be deployable in isolation and can be installed, updated, or removed independently. <br>Capability Bundles must be organized in separate HELM sub‑charts. <br>Circular dependencies between bundles must be avoided.                                                                                                                 |
+| 7.1.1.5        | Modularity & Maintainability: Concept for reducing deployment complexity                                                                                                                                                                                                                                                                             | The system deployment should be optimized to reduce the existing complexity. The goal is to make the provisioning process more efficient, robust, and easier to maintain.                                                                                                                                                                                                                                                                                                                                        | **Simplification of deployment processes:** A reduction of manual configuration steps has been achieved. <br>**Transparency and traceability:** Clearly documented deployment steps are provided. <br>**Improvements of Chart configuration by:** <br>usage of template  <br>reducing configuration options <br>reducing manual steps in the setup                                                                   |
+| 7.1.1.6        | Modularity & Maintainability                                                                                                                                                                                                                                                                                                                         | Charts are published automatically.                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | Charts are published via a publicly accessible charts repository.                                                                                                                                                                                                                                                                                                                                                    |
+| 7.1.1.13       | Solution Concept                                                                                                                                                                                                                                                                                                                                     | Creation of a solution design for the “Hausanschluss” Bundle.                                                                                                                                                                                                                                                                                                                                                                                                                                                    | The solution design for the "Hausanschluss" Bundle is created. <br>The solution design for the "Hausanschluss" Bundle ispublished in the repository: https://github.com/eclipse-tractusx/tractus-x-umbrella.                                                                                                                                                                                                         |
+| 7.1.1.14       | Scalability of Enablement Services                                                                                                                                                                                                                                                                                                                   | Scalability of Enablement Services                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | Developers should be able to deploy an arbitrary number of Enablement Services. <br>Example: Up to 3 EDCs can be provided.                                                                                                                                                                                                                                                                                           |
+| 7.1.1.16       | Interoperability                                                                                                                                                                                                                                                                                                                                     | Interoperability                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | Interoperability with the CATENA‑X standards. <br>This interoperability is documented and traceable.                                                                                                                                                                                                                                                                                                                 |
+| [WP-7.1.-D002] | [WP-7.1.-D002] Target group for the specification is defined.                                                                                                                                                                                                                                                                                        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | [WP-7.1.-D002] Target group for the specification is defined.                                                                                                                                                                                                                                                                                                                                                        |
+| 7.1.2.1        | Target Group Analysis                                                                                                                                                                                                                                                                                                                                | The target group analysis for the "Hausanschluss Bundle"is defined.                                                                                                                                                                                                                                                                                                                                                                                                                                              | The analysis has been conducted. <br>The target group is included in the solution concept <br>To be clarified: What is included in the Hausanschluss and who can operate it in which scenario (OEM, SME, service provider, etc.).                                                                                                                                                                                    |
+| [WP-7.1.-D003] | [WP-7.1.-D003] Decentralized components and services defined                                                                                                                                                                                                                                                                                         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | [WP-7.1.-D003] Decentralized components and services have been defined.                                                                                                                                                                                                                                                                                                                                              |
+| 7.1.3.1        | See [WP-7.1.-D001-AC001]                                                                                                                                                                                                                                                                                                                             |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | See [WP-7.1.-D001-AC001]                                                                                                                                                                                                                                                                                                                                                                                             |
+| [WP-7.1.-D004] | [WP-7.1.-D004] Documentation of the Hausanschluss Bundle is completed                                                                                                                                                                                                                                                                                |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | [WP-7.1.-D004] Documentation of the Hausanschluss Bundle is completed                                                                                                                                                                                                                                                                                                                                                |
+| 7.1.4.1        | Documentation of the Hausanschluss-Bundles                                                                                                                                                                                                                                                                                                           | Usability                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | Documentation is provided that enables an experienced product developer - with knowledge of Helm Charts, Docker, and Vaults - to deploy the chart independently without external help. <br>A troubleshooting and FAQ section is included to support the developer. <br>Prerequisites, skills, and technology requirements are outlined, detailing what a developer must know to perform the deployment autonomously. |
+| 7.1.4.2        | Documentation of the Hausanschluss-Bundles                                                                                                                                                                                                                                                                                                           | Documentation of the Hausanschluss-Bundles is completed.                                                                                                                                                                                                                                                                                                                                                                                                                                                         | Documentation is provided for: <br>Configuration of the defined bundles according to the specified requirements and parameters <br>Integration of the documentation into the Umbrella HELM Charts <br>Integration into the Umbrella HELM Chart to ensure consistent deployment                                                                                                                                       |
+| [WP-7.1.-D005] | [WP-7.1.-D005] Umbrella HELM Charts for the Hausanschluss developed, tested, and documented                                                                                                                                                                                                                                                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | [WP-7.1.-D005] Umbrella HELM Charts for the Hausanschluss have been developed, tested, and documented.                                                                                                                                                                                                                                                                                                               |
+| 7.1.5.1        | Re-activate Umbrella HELM Charts to the latest release state                                                                                                                                                                                                                                                                                         | The Enablement Services components of the Umbrella HELM Charts must be updated to version R24.12. This includes the following upgrades: <br> Upgrade DTR to version R24.12 (#188) <br>Upgrade EDCs to version R24.12 (#193) <br>Update SSI-DIM-Wallet-Stub to version 0.1.8 (#206)                                                                                                                                                                                                                               | The HELM Chart will then contain the updated versions of the components. <br>After the upgrade, the components (DTR, EDCs, SSI‑DIM‑Wallet‑Stub) run stably without functional impairments. <br>The deployment pipeline for the HELM Chart executes successfully <br>Relevant tests & smoke tests (e.g., integration tests) confirm the migration.                                                                    |
+| 7.1.5.2        | Hierarchical structuring and bundling of Enablement Service components in the Umbrella HELM Chart                                                                                                                                                                                                                                                    | The Umbrella HELM Chart should be structured hierarchically so that related Enablement Service components are grouped into bundles. <br>The Umbrella HELM Chart must have a clear hierarchical structure <br> Each Enablement Service component must be assigned to a unique bundle.<br>No circular dependencies between bundles are allowed.                                                                                                                                                                    | The chart is modular and divided into defined bundles. <br>Each bundle can be deployed and maintained independently.                                                                                                                                                                                                                                                                                                 |
+| 7.1.5.3        | Interchangeability of bundle components via “Bring-Your-Own” components                                                                                                                                                                                                                                                                              | Bundle components should be interchangeable through “Bring-Your-Own” components. <br>“Bring your own” is available for every component and means that these components do not have to be delivered by default with the Umbrella Chart but can be provided by the respective users.                                                                                                                                                                                                                               | Bundle components can be interchanged by “Bring-Your-Own” components.                                                                                                                                                                                                                                                                                                                                                |
+| [WP-7.1.-D006] | [WP-7.1.-D006] Product developed according to a Technology Readiness Level (TRL) of 3                                                                                                                                                                                                                                                                |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | [WP-7.1.-D006] The product is developed according to a Technology Readiness Level (TRL) of 3                                                                                                                                                                                                                                                                                                                         |
+| 7.1.6.1        | POC                                                                                                                                                                                                                                                                                                                                                  | Creation of a POC for the "Hausanschluss" Bundle                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | POC implementation is completed. <br>POC has been presented in a demo                                                                                                                                                                                                                                                                                                                                                |
+| 7.1.6.2        | Deployment Strategy                                                                                                                                                                                                                                                                                                                                  | The provisioning of bundles is carried out independently. <br>There must be an option to selectively activate or deactivate bundles.                                                                                                                                                                                                                                                                                                                                                                             | Configuration is managed via HELM values, allowing flexible adaptation according to the environment.                                                                                                                                                                                                                                                                                                                 |
+
+# 3 AS-IS Analysis
+
+## 3.1 People
+
+### 3.1.1 Target Group Analysis
+
+See "4.1.1 To-be Target Group Analysis" below. No deviations between As-is and To-be target groups have been identified.
+
+## 3.2 Process
+
+### 3.2.1 Use Case View (high-level)
+
+Umbrella Chart is intended for the following Use Cases:
+
+| Actor             | Use case                                                                                             |
+|-------------------|------------------------------------------------------------------------------------------------------|
+| Product Developer | Sandbox Environments: Create local environments to evaluate and experiment with Catena-X components. |
+| Product Developer | Development: Provide a unified setup for contributors and developers working on Tractus-X projects.  |
+| Product Tester    | Testing: Run end-to-end tests for Catena-X services.                                                 |
+| Product Manager   | Evaluate the dataspace to assess if their product can be used within Catena-X.                       |
+
+## 3.4 System
+
+### 3.4.1 Context Delimitation
+
+#### Existing Umbrella Chart Structure
+
+````mermaid
+flowchart
+    subgraph "Umbrella Chart"
+        ChartYaml["Chart.yaml"]
+        subgraph charts
+            Portal["Portal"]
+            CentralIdp["CentralIdp"]
+            DiscoveryFinder["Discovery Finder"]
+            SDFactory["SD-Factory"]
+            SSICredentialIssuer["SSI Credential Issuer"]
+            SemanticHub["Semantic Hub"]
+            BPDM["BPDM"]
+            DataConsumer["Data Consumer"]
+            DataProvider["Data Provider"]
+            BDRS["BDRS"]
+            SSIWalletStub["SSI Wallet Stub"]
+        end
+        subgraph "tx-data-provider"
+            EDC["EDC"]
+            DTR["DTR"]
+            SubmodelServer["Submodel Server"]
+        end
+    end
+
+    ChartYaml --> Portal
+    ChartYaml --> CentralIdp
+    ChartYaml --> DiscoveryFinder
+    ChartYaml --> SDFactory
+    ChartYaml --> SSICredentialIssuer
+    ChartYaml --> SemanticHub
+    ChartYaml --> BPDM
+    ChartYaml --> DataConsumer
+    ChartYaml --> DataProvider
+    ChartYaml --> BDRS
+    ChartYaml --> SSIWalletStub
+    DataConsumer --> EDC
+    DataProvider --> EDC
+    DataProvider --> DTR
+    DataProvider --> SubmodelServer
+````
+
+# 4 TO-BE Design
+
+## 4.1 People
+
+### 4.1.1 Target Group Analysis
+
+Overall data space roles: https://catena-x.net/en/1/catena-x-introduce-implement/how-to-operate-catena-x
path: docs/concept/TAP7.1-solution-design.md
user: login: ds-jhartmann
body: fixed
created_at: 2025-04-03T12:10:42Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,516 @@
+# Solution Design "Hausanschluss" Bundle Concept
+
+# 1 Business Case
+
+## 1.1 Executive Summary
+
+The "Hausanschluss" Bundle aims to simplify the installation of the enablement services Eclipse Dataspace
+Connector (EDC), Digital Twin Registry (DTR), and their supporting components. By developing a flexible, parameterizable
+installation package, the project seeks to reduce deployment complexity and lower barriers to participation in the
+Catena‑X data space. This bundle will enable independent component updates and support a modular "bring your own"
+approach, ultimately fostering a more efficient and accessible ecosystem for diverse participants—such as testers,
+external product developers, product testers, and small and medium-sized enterprises.
+
+## 1.2 Business Need
+
+Current deployment methods for data space integration are complex and require significant manual effort. This PoC
+addresses the need to:
+
+- **Reduce Complexity:** Simplify the deployment topology by bundling components into capabilities.
+- **Automate Deployment:** Provide an automated installation package using Kubernetes and HELM.
+- **Minimize Configuration Overhead:** Streamline the integration process by providing pre-configured bundles that require only minimal manual parameter adjustments.
+- **Extend Documentation:** Provide a detailed documentation tailored to the target groups.
+- **Enable Extension:** Design the system to allow the seamless addition of new components or capabilities.
+
+## 1.3 Objectives
+
+- **Simplify Deployment and Maintenance:** Develop an installation package that minimizes manual configuration through
+  automation.
+- **Ensure Modularity:** Structure the bundle so that components can be independently installed, updated, or replaced
+  without affecting other services.
+- **Facilitate Flexibility:** Implement a "bring your own" model for key components, such as EDC, PostgreSQL, and HashiCorp
+  Vault, to allow tailored deployments that meet specific needs.
+- **Increase Accessibility**: Lower entry barriers for new participants by reducing technical complexity and operational
+  dependencies.
+- **Scalability:** Structure the bundles so that they can be deployed multiple times.
+
+## 1.4 Expected Deliverables
+
+- **PoC Documentation:** A concept and architecture overview highlighting the modular design.
+- **Modular Installation Package:** A set of HELM charts for deploying the enablement service bundles:
+    - **Dataspace Connector:** Including the Eclipse Dataspace Connector, EDC PostgreSQL, and HashiCorp Vault.
+    - **Digital Twin Bundle:** Featuring components such as the Decentral DT Registry (with “bring your own” PostgreSQL)
+    - **Data Persitence Layer Bundle:** Including a simple Submodel Server to store semantic data.
+    - **Identity Wallet Bundle:** Covering the Identity Wallet functionality.
+- **Demonstration Environment:** A test deployment showcasing reduced complexity and improved efficiency.
+- **Basic User Guide:** Instructions on how to deploy and update the PoC bundle.
+
+## 1.5 Benefits
+
+- **Operational Efficiency:** Faster and more reliable deployments with less manual work.
+- **Scalability:** A modular design that can be scaled or adapted for future full-scale deployments.
+- **Ease of Adoption:** Simplified deployment processes make it easier for testers and external developers to engage.
+
+## 1.6. Dependencies
+
+- **Interoperability** with the CATENA‑X standards.
+
+## 1.7. Success Criteria
+
+- **Technology Readiness Level:** Achievement of a Technology Readiness Level (TRL) of 3, as specified in the requirements.
+- **Functional PoC Deployment:** Demonstrated automated, modular installation with reduced manual steps.
+- **Simplified Configuration:** Clear evidence of reduced configuration complexity.
+- **Positive Feedback:** End-user validation from a select group of demo participants and the Tractus-X community.
+- **Documentation Completeness:** Availability of concise deployment and user guides.
+
+## 1.8. Out of Scope
+
+- **Full Production Readiness:** This PoC is not intended to be a production-ready solution.
+- **Core Services Exclusion:** Core services are not part of the Hausanschluss Bundles.
+- **App Provider Role:** The role of App Provider is considered out of scope for this deployment.
+- **Alternative Deployment Techniques:** While the evaluation of alternative deployment methods is acknowledged, the primary
+  focus remains on Kubernetes and HELM-based deployment.
+
+# 2 Requirements Analysis
+
+## 2.1 Assumptions
+
+## 2.2 Requirements Catalog
+
+| ID             | Requirement                                                                                                                                                                                                                                                                                                                                          | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | Deliverables / Acceptance Criteria                                                                                                                                                                                                                                                                                                                                                                                   |
+|----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| [WP-7.1.-D001] | The Hausanschluss Bundle aims to simplify the installation and maintenance of the EDC and other components that together ensure a “Hausanschluss”. A flexible, parameterizable installation package is intended to reduce complexity and make integration more efficient, thereby simplifying participation in Catena‑X for additional participants. | Specification and development of a flexible, parameterizable installation package that reduces the complexity of installing and maintaining the required components for seamless integration into the Catena‑X data space. This package should facilitate updates and new versions, making participation in Catena‑X more efficient and accessible. In doing so, SMEs shall be enabled to participate without high costs or dependency on SaaS providers while maintaining control over their IT infrastructure. | [WP-7.1.-D001] Concept for the Hausanschluss is created                                                                                                                                                                                                                                                                                                                                                              |
+| 7.1.1.1        | The solution concept must define the Capability Bundles structures to be implemented. For each Capability Bundle, the included bundles and their versions are mapped.                                                                                                                                                                                | "The following Capability Bundle structure is implemented:                                                                                                                                                                                                                                                                                                                                                                                                                                                       | The structure of the Capability Bundles for the Enablement Services has been specified. For version R24.12 it is clearly defined which Tractus‑X services and components are assigned to each Capability Bundle                                                                                                                                                                                                      |
+| 7.1.1.2        | Definition of Data Space Roles                                                                                                                                                                                                                                                                                                                       | Data Consumer, Data Provider, Enablement Service Provider                                                                                                                                                                                                                                                                                                                                                                                                                                                        | As part of the target group analysis, the target groups are defined and aligned with the data space roles. <br>Mapping from data space role to target group has been completed. <br>Mapping from target group to data space role has been completed. <br>An assignment of data space roles to Capability Bundles has been made.                                                                                      |
+| 7.1.1.4        | Modularity & Maintainability: No dependencies between Capability Bundles                                                                                                                                                                                                                                                                             | Unique assignment of components and services to a defined Capability Bundle. <br>Each component and service should be assigned to only one Capability Bundle. <br>Dependencies between Capability Bundles are allowed.                                                                                                                                                                                                                                                                                           | Components and Services should only be part of one bundle. <br>Each bundle must be deployable in isolation and can be installed, updated, or removed independently. <br>Capability Bundles must be organized in separate HELM sub‑charts. <br>Circular dependencies between bundles must be avoided.                                                                                                                 |
+| 7.1.1.5        | Modularity & Maintainability: Concept for reducing deployment complexity                                                                                                                                                                                                                                                                             | The system deployment should be optimized to reduce the existing complexity. The goal is to make the provisioning process more efficient, robust, and easier to maintain.                                                                                                                                                                                                                                                                                                                                        | **Simplification of deployment processes:** A reduction of manual configuration steps has been achieved. <br>**Transparency and traceability:** Clearly documented deployment steps are provided. <br>**Improvements of Chart configuration by:** <br>usage of template  <br>reducing configuration options <br>reducing manual steps in the setup                                                                   |
+| 7.1.1.6        | Modularity & Maintainability                                                                                                                                                                                                                                                                                                                         | Charts are published automatically.                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | Charts are published via a publicly accessible charts repository.                                                                                                                                                                                                                                                                                                                                                    |
+| 7.1.1.13       | Solution Concept                                                                                                                                                                                                                                                                                                                                     | Creation of a solution design for the “Hausanschluss” Bundle.                                                                                                                                                                                                                                                                                                                                                                                                                                                    | The solution design for the "Hausanschluss" Bundle is created. <br>The solution design for the "Hausanschluss" Bundle ispublished in the repository: https://github.com/eclipse-tractusx/tractus-x-umbrella.                                                                                                                                                                                                         |
+| 7.1.1.14       | Scalability of Enablement Services                                                                                                                                                                                                                                                                                                                   | Scalability of Enablement Services                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | Developers should be able to deploy an arbitrary number of Enablement Services. <br>Example: Up to 3 EDCs can be provided.                                                                                                                                                                                                                                                                                           |
+| 7.1.1.16       | Interoperability                                                                                                                                                                                                                                                                                                                                     | Interoperability                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | Interoperability with the CATENA‑X standards. <br>This interoperability is documented and traceable.                                                                                                                                                                                                                                                                                                                 |
+| [WP-7.1.-D002] | [WP-7.1.-D002] Target group for the specification is defined.                                                                                                                                                                                                                                                                                        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | [WP-7.1.-D002] Target group for the specification is defined.                                                                                                                                                                                                                                                                                                                                                        |
+| 7.1.2.1        | Target Group Analysis                                                                                                                                                                                                                                                                                                                                | The target group analysis for the "Hausanschluss Bundle"is defined.                                                                                                                                                                                                                                                                                                                                                                                                                                              | The analysis has been conducted. <br>The target group is included in the solution concept <br>To be clarified: What is included in the Hausanschluss and who can operate it in which scenario (OEM, SME, service provider, etc.).                                                                                                                                                                                    |
+| [WP-7.1.-D003] | [WP-7.1.-D003] Decentralized components and services defined                                                                                                                                                                                                                                                                                         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | [WP-7.1.-D003] Decentralized components and services have been defined.                                                                                                                                                                                                                                                                                                                                              |
+| 7.1.3.1        | See [WP-7.1.-D001-AC001]                                                                                                                                                                                                                                                                                                                             |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | See [WP-7.1.-D001-AC001]                                                                                                                                                                                                                                                                                                                                                                                             |
+| [WP-7.1.-D004] | [WP-7.1.-D004] Documentation of the Hausanschluss Bundle is completed                                                                                                                                                                                                                                                                                |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | [WP-7.1.-D004] Documentation of the Hausanschluss Bundle is completed                                                                                                                                                                                                                                                                                                                                                |
+| 7.1.4.1        | Documentation of the Hausanschluss-Bundles                                                                                                                                                                                                                                                                                                           | Usability                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | Documentation is provided that enables an experienced product developer - with knowledge of Helm Charts, Docker, and Vaults - to deploy the chart independently without external help. <br>A troubleshooting and FAQ section is included to support the developer. <br>Prerequisites, skills, and technology requirements are outlined, detailing what a developer must know to perform the deployment autonomously. |
+| 7.1.4.2        | Documentation of the Hausanschluss-Bundles                                                                                                                                                                                                                                                                                                           | Documentation of the Hausanschluss-Bundles is completed.                                                                                                                                                                                                                                                                                                                                                                                                                                                         | Documentation is provided for: <br>Configuration of the defined bundles according to the specified requirements and parameters <br>Integration of the documentation into the Umbrella HELM Charts <br>Integration into the Umbrella HELM Chart to ensure consistent deployment                                                                                                                                       |
+| [WP-7.1.-D005] | [WP-7.1.-D005] Umbrella HELM Charts for the Hausanschluss developed, tested, and documented                                                                                                                                                                                                                                                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | [WP-7.1.-D005] Umbrella HELM Charts for the Hausanschluss have been developed, tested, and documented.                                                                                                                                                                                                                                                                                                               |
+| 7.1.5.1        | Re-activate Umbrella HELM Charts to the latest release state                                                                                                                                                                                                                                                                                         | The Enablement Services components of the Umbrella HELM Charts must be updated to version R24.12. This includes the following upgrades: <br> Upgrade DTR to version R24.12 (#188) <br>Upgrade EDCs to version R24.12 (#193) <br>Update SSI-DIM-Wallet-Stub to version 0.1.8 (#206)                                                                                                                                                                                                                               | The HELM Chart will then contain the updated versions of the components. <br>After the upgrade, the components (DTR, EDCs, SSI‑DIM‑Wallet‑Stub) run stably without functional impairments. <br>The deployment pipeline for the HELM Chart executes successfully <br>Relevant tests & smoke tests (e.g., integration tests) confirm the migration.                                                                    |
+| 7.1.5.2        | Hierarchical structuring and bundling of Enablement Service components in the Umbrella HELM Chart                                                                                                                                                                                                                                                    | The Umbrella HELM Chart should be structured hierarchically so that related Enablement Service components are grouped into bundles. <br>The Umbrella HELM Chart must have a clear hierarchical structure <br> Each Enablement Service component must be assigned to a unique bundle.<br>No circular dependencies between bundles are allowed.                                                                                                                                                                    | The chart is modular and divided into defined bundles. <br>Each bundle can be deployed and maintained independently.                                                                                                                                                                                                                                                                                                 |
+| 7.1.5.3        | Interchangeability of bundle components via “Bring-Your-Own” components                                                                                                                                                                                                                                                                              | Bundle components should be interchangeable through “Bring-Your-Own” components. <br>“Bring your own” is available for every component and means that these components do not have to be delivered by default with the Umbrella Chart but can be provided by the respective users.                                                                                                                                                                                                                               | Bundle components can be interchanged by “Bring-Your-Own” components.                                                                                                                                                                                                                                                                                                                                                |
+| [WP-7.1.-D006] | [WP-7.1.-D006] Product developed according to a Technology Readiness Level (TRL) of 3                                                                                                                                                                                                                                                                |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | [WP-7.1.-D006] The product is developed according to a Technology Readiness Level (TRL) of 3                                                                                                                                                                                                                                                                                                                         |
+| 7.1.6.1        | POC                                                                                                                                                                                                                                                                                                                                                  | Creation of a POC for the "Hausanschluss" Bundle                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | POC implementation is completed. <br>POC has been presented in a demo                                                                                                                                                                                                                                                                                                                                                |
+| 7.1.6.2        | Deployment Strategy                                                                                                                                                                                                                                                                                                                                  | The provisioning of bundles is carried out independently. <br>There must be an option to selectively activate or deactivate bundles.                                                                                                                                                                                                                                                                                                                                                                             | Configuration is managed via HELM values, allowing flexible adaptation according to the environment.                                                                                                                                                                                                                                                                                                                 |
+
+# 3 AS-IS Analysis
+
+## 3.1 People
+
+### 3.1.1 Target Group Analysis
+
+See "4.1.1 To-be Target Group Analysis" below. No deviations between As-is and To-be target groups have been identified.
+
+## 3.2 Process
+
+### 3.2.1 Use Case View (high-level)
+
+Umbrella Chart is intended for the following Use Cases:
+
+| Actor             | Use case                                                                                             |
+|-------------------|------------------------------------------------------------------------------------------------------|
+| Product Developer | Sandbox Environments: Create local environments to evaluate and experiment with Catena-X components. |
+| Product Developer | Development: Provide a unified setup for contributors and developers working on Tractus-X projects.  |
+| Product Tester    | Testing: Run end-to-end tests for Catena-X services.                                                 |
+| Product Manager   | Evaluate the dataspace to assess if their product can be used within Catena-X.                       |
+
+## 3.4 System
+
+### 3.4.1 Context Delimitation
+
+#### Existing Umbrella Chart Structure
+
+````mermaid
+flowchart
+    subgraph "Umbrella Chart"
+        ChartYaml["Chart.yaml"]
+        subgraph charts
+            Portal["Portal"]
+            CentralIdp["CentralIdp"]
+            DiscoveryFinder["Discovery Finder"]
+            SDFactory["SD-Factory"]
+            SSICredentialIssuer["SSI Credential Issuer"]
+            SemanticHub["Semantic Hub"]
+            BPDM["BPDM"]
+            DataConsumer["Data Consumer"]
+            DataProvider["Data Provider"]
+            BDRS["BDRS"]
+            SSIWalletStub["SSI Wallet Stub"]
+        end
+        subgraph "tx-data-provider"
+            EDC["EDC"]
+            DTR["DTR"]
+            SubmodelServer["Submodel Server"]
+        end
+    end
+
+    ChartYaml --> Portal
+    ChartYaml --> CentralIdp
+    ChartYaml --> DiscoveryFinder
+    ChartYaml --> SDFactory
+    ChartYaml --> SSICredentialIssuer
+    ChartYaml --> SemanticHub
+    ChartYaml --> BPDM
+    ChartYaml --> DataConsumer
+    ChartYaml --> DataProvider
+    ChartYaml --> BDRS
+    ChartYaml --> SSIWalletStub
+    DataConsumer --> EDC
+    DataProvider --> EDC
+    DataProvider --> DTR
+    DataProvider --> SubmodelServer
+````
+
+# 4 TO-BE Design
+
+## 4.1 People
+
+### 4.1.1 Target Group Analysis
+
+Overall data space roles: https://catena-x.net/en/1/catena-x-introduce-implement/how-to-operate-catena-x
path: docs/concept/TAP7.1-solution-design.md
user: login: ds-jhartmann
body: fixed
created_at: 2025-04-03T12:11:00Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,584 @@
+# Solution Design "Hausanschluss" Bundle Concept
+
+<!-- TOC -->
+* [Solution Design "Hausanschluss" Bundle Concept](#solution-design-hausanschluss-bundle-concept)
+* [1 Business Case](#1-business-case)
+  * [1.1 Executive Summary](#11-executive-summary)
+  * [1.2 Business Need](#12-business-need)
+  * [1.3 Objectives](#13-objectives)
+  * [1.4 Expected Deliverables](#14-expected-deliverables)
+  * [1.5 Benefits](#15-benefits)
+  * [1.6. Dependencies](#16-dependencies)
+  * [1.7. Success Criteria](#17-success-criteria)
+  * [1.8. Out of Scope](#18-out-of-scope)
+* [2 Requirements Analysis](#2-requirements-analysis)
+  * [2.1 Assumptions](#21-assumptions)
+  * [2.2 Requirements Catalog](#22-requirements-catalog)
+* [3 AS-IS Analysis](#3-as-is-analysis)
+  * [3.1 People](#31-people)
+    * [3.1.1 Target Group Analysis](#311-target-group-analysis)
+  * [3.2 Process](#32-process)
+    * [3.2.1 Use Case View (high-level)](#321-use-case-view-high-level)
+  * [3.4 System](#34-system)
+    * [3.4.1 Context Delimitation](#341-context-delimitation)
+      * [Existing Umbrella Chart Structure](#existing-umbrella-chart-structure)
+* [4 TO-BE Design](#4-to-be-design)
+  * [4.1 People](#41-people)
+    * [4.1.1 Target Group Analysis](#411-target-group-analysis)
+  * [4.2 Process](#42-process)
+    * [4.2.1 Use Case View (high-level)](#421-use-case-view-high-level)
+      * [Group 1: Product developer](#group-1-product-developer)
+      * [Group 2: Product Tester](#group-2-product-tester)
+      * [Group 3: Product Manager](#group-3-product-manager)
+      * [Use Case diagram](#use-case-diagram)
+    * [4.2.2 Business Process (SCC Artifact)](#422-business-process-scc-artifact)
+      * [Chart Release Process](#chart-release-process)
+      * [Capability Bundle Structure](#capability-bundle-structure)
+      * [Deployment strategies](#deployment-strategies)
+        * [Role: Data Provider](#role-data-provider)
+        * [Role: Data Consumer](#role-data-consumer)
+        * [Role: Enablement Provider](#role-enablement-provider)
+      * [Bring your own](#bring-your-own)
+      * [Scalability](#scalability)
+      * [Interoperability](#interoperability)
+  * [4.4 System](#44-system)
+    * [4.4.1 Context Delimitation / 4.4.2 Interface Documentation](#441-context-delimitation--442-interface-documentation)
+* [5 Build](#5-build)
+  * [5.1 DevOps Setup Definition](#51-devops-setup-definition)
+    * [5.1.1 Tool Chain Definition](#511-tool-chain-definition)
+        * [Version Control & Source Code Management](#version-control--source-code-management)
+        * [Build and CI/CD Tools](#build-and-cicd-tools)
+        * [Testing and Validation Tools](#testing-and-validation-tools)
+        * [Release Management & Deployment](#release-management--deployment)
+* [NOTICE](#notice)
+<!-- TOC -->
+
+# 1 Business Case
+
+## 1.1 Executive Summary
+
+The "Hausanschluss" Bundle aims to simplify the installation of the enablement services Eclipse Dataspace
+Connector (EDC), Digital Twin Registry (DTR), and their supporting components. By developing a flexible, parameterizable
+installation package, the project seeks to reduce deployment complexity and lower barriers to participation in the
+Catena‑X data space. This bundle will enable independent component updates and support a modular "bring your own"
+approach, ultimately fostering a more efficient and accessible ecosystem for diverse participants—such as testers,
+external product developers, product testers, and small and medium-sized enterprises.
+
+## 1.2 Business Need
+
+Current deployment methods for data space integration are complex and require significant manual effort. This PoC
+addresses the need to:
+
+- **Reduce Complexity:** Simplify the deployment topology by bundling components into capabilities.
+- **Automate Deployment:** Provide an automated installation package using Kubernetes and HELM.
+- **Minimize Configuration Overhead:** Streamline the integration process by providing pre-configured bundles that require only minimal manual parameter adjustments.
+- **Extend Documentation:** Provide a detailed documentation tailored to the target groups.
+- **Enable Extension:** Design the system to allow the seamless addition of new components or capabilities.
+
+## 1.3 Objectives
+
+- **Simplify Deployment and Maintenance:** Develop an installation package that minimizes manual configuration through
+  automation.
+- **Ensure Modularity:** Structure the bundle so that components can be independently installed, updated, or replaced
+  without affecting other services.
+- **Facilitate Flexibility:** Implement a "bring your own" model for key components, such as EDC, PostgreSQL, and HashiCorp
+  Vault, to allow tailored deployments that meet specific needs.
+- **Increase Accessibility**: Lower entry barriers for new participants by reducing technical complexity and operational
+  dependencies.
+- **Scalability:** Structure the bundles so that they can be deployed multiple times.
+
+## 1.4 Expected Deliverables
+
+- **PoC Documentation:** A concept and architecture overview highlighting the modular design.
+- **Modular Installation Package:** A set of HELM charts for deploying the enablement service bundles:
+    - **Dataspace Connector:** Including the Eclipse Dataspace Connector, EDC PostgreSQL, and HashiCorp Vault.
+    - **Digital Twin Bundle:** Featuring components such as the Decentral DT Registry (with “bring your own” PostgreSQL)
+    - **Data Persistence Layer Bundle:** Including a simple Submodel Server to store semantic data.
+    - **Identity Wallet Bundle:** Covering the Identity Wallet functionality.
+- **Demonstration Environment:** A test deployment showcasing reduced complexity and improved efficiency.
+- **Basic User Guide:** Instructions on how to deploy and update the PoC bundle.
+
+## 1.5 Benefits
+
+- **Operational Efficiency:** Faster and more reliable deployments with less manual work.
+- **Scalability:** A modular design that can be scaled or adapted for future full-scale deployments.
+- **Ease of Adoption:** Simplified deployment processes make it easier for testers and external developers to engage.
+
+## 1.6. Dependencies
+
+- **Interoperability** with the CATENA‑X standards.
+
+## 1.7. Success Criteria
+
+- **Technology Readiness Level:** Achievement of a Technology Readiness Level (TRL) of 3, as specified in the requirements.
+- **Functional PoC Deployment:** Demonstrated automated, modular installation with reduced manual steps.
+- **Simplified Configuration:** Clear evidence of reduced configuration complexity.
+- **Positive Feedback:** End-user validation from a select group of demo participants and the Tractus-X community.
+- **Documentation Completeness:** Availability of concise deployment and user guides.
+
+## 1.8. Out of Scope
+
+- **Full Production Readiness:** This PoC is not intended to be a production-ready solution.
+- **Core Services Exclusion:** Core services are not part of the Hausanschluss Bundles.
+- **App Provider Role:** The role of App Provider is considered out of scope for this deployment.
+- **Alternative Deployment Techniques:** While the evaluation of alternative deployment methods is acknowledged, the primary
+  focus remains on Kubernetes and HELM-based deployment.
+
+# 2 Requirements Analysis
+
+## 2.1 Assumptions
+
+## 2.2 Requirements Catalog
+
+| ID             | Requirement                                                                                                                                                                                                                                                                                                                                          | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | Deliverables / Acceptance Criteria                                                                                                                                                                                                                                                                                                                                                                                   |
+|----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| [WP-7.1.-D001] | The Hausanschluss Bundle aims to simplify the installation and maintenance of the EDC and other components that together ensure a “Hausanschluss”. A flexible, parameterizable installation package is intended to reduce complexity and make integration more efficient, thereby simplifying participation in Catena‑X for additional participants. | Specification and development of a flexible, parameterizable installation package that reduces the complexity of installing and maintaining the required components for seamless integration into the Catena‑X data space. This package should facilitate updates and new versions, making participation in Catena‑X more efficient and accessible. In doing so, SMEs shall be enabled to participate without high costs or dependency on SaaS providers while maintaining control over their IT infrastructure. | [WP-7.1.-D001] Concept for the Hausanschluss is created                                                                                                                                                                                                                                                                                                                                                              |
+| 7.1.1.1        | The solution concept must define the Capability Bundles structures to be implemented. For each Capability Bundle, the included bundles and their versions are mapped.                                                                                                                                                                                | The following Capability Bundle structure is implemented:                                                                                                                                                                                                                                                                                                                                                                                                                                                        | The structure of the Capability Bundles for the Enablement Services has been specified. For version R24.12 it is clearly defined which Tractus‑X services and components are assigned to each Capability Bundle                                                                                                                                                                                                      |
+| 7.1.1.2        | Definition of Data Space Roles                                                                                                                                                                                                                                                                                                                       | Data Consumer, Data Provider, Enablement Service Provider                                                                                                                                                                                                                                                                                                                                                                                                                                                        | As part of the target group analysis, the target groups are defined and aligned with the data space roles. <br>Mapping from data space role to target group has been completed. <br>Mapping from target group to data space role has been completed. <br>An assignment of data space roles to Capability Bundles has been made.                                                                                      |
+| 7.1.1.4        | Modularity & Maintainability: Components and services must be assigned to a single Capability Bundle.                                                                                                                                                                                                                                                | Assignment of components and services to a defined Capability Bundle. <br>Each component and service should be assigned to only one Capability Bundle. <br>Dependencies between Capability Bundles are allowed.                                                                                                                                                                                                                                                                                                  | Components and Services should only be part of one bundle. <br>Each bundle must be deployable in isolation and can be installed, updated, or removed independently. <br>Capability Bundles must be organized in separate HELM sub‑charts. <br>Circular dependencies between bundles must be avoided.                                                                                                                 |
+| 7.1.1.5        | Modularity & Maintainability: Concept for reducing deployment complexity                                                                                                                                                                                                                                                                             | The system deployment should be optimized to reduce the existing complexity. The goal is to make the provisioning process more efficient, robust, and easier to maintain.                                                                                                                                                                                                                                                                                                                                        | **Simplification of deployment processes:** A reduction of manual configuration steps has been achieved. <br>**Transparency and traceability:** Clearly documented deployment steps are provided. <br>**Improvements of Chart configuration by:** <br>usage of template  <br>reducing configuration options <br>reducing manual steps in the setup                                                                   |
+| 7.1.1.6        | Modularity & Maintainability                                                                                                                                                                                                                                                                                                                         | Charts are published automatically.                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | Charts are published via a publicly accessible charts repository.                                                                                                                                                                                                                                                                                                                                                    |
+| 7.1.1.13       | Solution Concept                                                                                                                                                                                                                                                                                                                                     | Creation of a solution design for the “Hausanschluss” Bundle.                                                                                                                                                                                                                                                                                                                                                                                                                                                    | The solution design for the "Hausanschluss" Bundle is created. <br>The solution design for the "Hausanschluss" Bundle is published in the repository: https://github.com/eclipse-tractusx/tractus-x-umbrella.                                                                                                                                                                                                        |
+| 7.1.1.14       | Scalability of Enablement Services                                                                                                                                                                                                                                                                                                                   | Scalability of Enablement Services                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | Developers should be able to deploy an arbitrary number of Enablement Services. <br>Example: Up to 3 EDCs can be provided.                                                                                                                                                                                                                                                                                           |
+| 7.1.1.16       | Interoperability                                                                                                                                                                                                                                                                                                                                     | Interoperability                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | Interoperability with the CATENA‑X standards. <br>This interoperability is documented and traceable.                                                                                                                                                                                                                                                                                                                 |
+| [WP-7.1.-D002] | [WP-7.1.-D002] Target group for the specification is defined.                                                                                                                                                                                                                                                                                        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | [WP-7.1.-D002] Target group for the specification is defined.                                                                                                                                                                                                                                                                                                                                                        |
+| 7.1.2.1        | Target Group Analysis                                                                                                                                                                                                                                                                                                                                | The target group analysis for the "Hausanschluss Bundle"is defined.                                                                                                                                                                                                                                                                                                                                                                                                                                              | The analysis has been conducted. <br>The target group is included in the solution concept <br>To be clarified: What is included in the Hausanschluss and who can operate it in which scenario (OEM, SME, service provider, etc.).                                                                                                                                                                                    |
+| [WP-7.1.-D003] | [WP-7.1.-D003] Decentralized components and services defined                                                                                                                                                                                                                                                                                         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | [WP-7.1.-D003] Decentralized components and services have been defined.                                                                                                                                                                                                                                                                                                                                              |
+| 7.1.3.1        | See [WP-7.1.-D001-AC001]                                                                                                                                                                                                                                                                                                                             |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | See [WP-7.1.-D001-AC001]                                                                                                                                                                                                                                                                                                                                                                                             |
+| [WP-7.1.-D004] | [WP-7.1.-D004] Documentation of the Hausanschluss Bundle is completed                                                                                                                                                                                                                                                                                |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | [WP-7.1.-D004] Documentation of the Hausanschluss Bundle is completed                                                                                                                                                                                                                                                                                                                                                |
+| 7.1.4.1        | Documentation of the Hausanschluss-Bundles                                                                                                                                                                                                                                                                                                           | Usability                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | Documentation is provided that enables an experienced product developer - with knowledge of Helm Charts, Docker, and Vaults - to deploy the chart independently without external help. <br>A troubleshooting and FAQ section is included to support the developer. <br>Prerequisites, skills, and technology requirements are outlined, detailing what a developer must know to perform the deployment autonomously. |
+| 7.1.4.2        | Documentation of the Hausanschluss-Bundles                                                                                                                                                                                                                                                                                                           | Documentation of the Hausanschluss-Bundles is completed.                                                                                                                                                                                                                                                                                                                                                                                                                                                         | Documentation is provided for: <br>Configuration of the defined bundles according to the specified requirements and parameters. <br>Integration of the documentation into the Umbrella HELM Charts. <br>Integration into the Umbrella HELM Chart to ensure consistent deployment.                                                                                                                                    |
+| [WP-7.1.-D005] | [WP-7.1.-D005] Umbrella HELM Charts for the Hausanschluss developed, tested, and documented                                                                                                                                                                                                                                                          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | [WP-7.1.-D005] Umbrella HELM Charts for the Hausanschluss have been developed, tested, and documented.                                                                                                                                                                                                                                                                                                               |
+| 7.1.5.1        | Re-activate Umbrella HELM Charts to the latest release state                                                                                                                                                                                                                                                                                         | The Enablement Services components of the Umbrella HELM Charts must be updated to version R24.12. This includes the following upgrades: <br> Upgrade DTR to version R24.12 (#188) <br>Upgrade EDCs to version R24.12 (#193) <br>Update SSI-DIM-Wallet-Stub to version 0.1.8 (#206)                                                                                                                                                                                                                               | The HELM Chart will then contain the updated versions of the components. <br>After the upgrade, the components (DTR, EDCs, SSI‑DIM‑Wallet‑Stub) run stably without functional impairments. <br>The deployment pipeline for the HELM Chart executes successfully. <br>Relevant tests & smoke tests (e.g., integration tests) confirm the migration.                                                                   |
+| 7.1.5.2        | Hierarchical structuring and bundling of Enablement Service components in the Umbrella HELM Chart                                                                                                                                                                                                                                                    | The Umbrella HELM Chart should be structured hierarchically so that related Enablement Service components are grouped into bundles. <br>The Umbrella HELM Chart must have a clear hierarchical structure. <br> Each Enablement Service component must be assigned to a unique bundle.<br>No circular dependencies between bundles are allowed.                                                                                                                                                                   | The chart is modular and divided into defined bundles. <br>Each bundle can be deployed and maintained independently.                                                                                                                                                                                                                                                                                                 |
+| 7.1.5.3        | Interchangeability of bundle components via “Bring-Your-Own” components                                                                                                                                                                                                                                                                              | Bundle components should be interchangeable through “Bring-Your-Own” components. <br>“Bring your own” is available for every component and means that these components do not have to be delivered by default with the Umbrella Chart but can be provided by the respective users.                                                                                                                                                                                                                               | Bundle components can be interchanged by “Bring-Your-Own” components.                                                                                                                                                                                                                                                                                                                                                |
+| [WP-7.1.-D006] | [WP-7.1.-D006] Product developed according to a Technology Readiness Level (TRL) of 3                                                                                                                                                                                                                                                                |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | [WP-7.1.-D006] The product is developed according to a Technology Readiness Level (TRL) of 3                                                                                                                                                                                                                                                                                                                         |
+| 7.1.6.1        | POC                                                                                                                                                                                                                                                                                                                                                  | Creation of a POC for the "Hausanschluss" Bundle                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | POC implementation is completed. <br>POC has been presented in a demo.                                                                                                                                                                                                                                                                                                                                               |
+| 7.1.6.2        | Deployment Strategy                                                                                                                                                                                                                                                                                                                                  | The provisioning of bundles is carried out independently. <br>There must be an option to selectively activate or deactivate bundles.                                                                                                                                                                                                                                                                                                                                                                             | Configuration is managed via HELM values, allowing flexible adaptation according to the environment.                                                                                                                                                                                                                                                                                                                 |
+
+# 3 AS-IS Analysis
+
+## 3.1 People
+
+### 3.1.1 Target Group Analysis
+
+See "4.1.1 To-be Target Group Analysis" below. No deviations between As-is and To-be target groups have been identified.
+
+## 3.2 Process
+
+### 3.2.1 Use Case View (high-level)
+
+Umbrella Chart is intended for the following Use Cases:
+
+| Actor             | Use case                                                                                             |
+|-------------------|------------------------------------------------------------------------------------------------------|
+| Product Developer | Sandbox Environments: Create local environments to evaluate and experiment with Catena-X components. |
+| Product Developer | Development: Provide a unified setup for contributors and developers working on Tractus-X projects.  |
+| Product Tester    | Testing: Run end-to-end tests for Catena-X services.                                                 |
+| Product Manager   | Evaluate the dataspace to assess if their product can be used within Catena-X.                       |
+
+## 3.4 System
+
+### 3.4.1 Context Delimitation
+
+#### Existing Umbrella Chart Structure
+
+````mermaid
+flowchart
+    subgraph "Umbrella Chart"
+        ChartYaml["Chart.yaml"]
+        subgraph charts
+            Portal["Portal"]
+            CentralIdp["CentralIdp"]
+            SharedIdp["SharedIdp"]
+            DiscoveryFinder["Discovery Finder"]
+            SDFactory["SD-Factory"]
+            SSICredentialIssuer["SSI Credential Issuer"]
+            SemanticHub["Semantic Hub"]
+            BPDM["BPDM"]
+            DataConsumer["Data Consumer"]
+            DataProvider["Data Provider"]
+            BDRS["BDRS"]
+            SSIWalletStub["SSI Wallet Stub"]
+        end
+        subgraph "tx-data-provider"
+            EDC["EDC"]
+            DTR["DTR"]
+            SubmodelServer["Submodel Server"]
+        end
+    end
+
+    ChartYaml --> Portal
+    ChartYaml --> CentralIdp
+    ChartYaml --> SharedIdp
+    ChartYaml --> DiscoveryFinder
+    ChartYaml --> SDFactory
+    ChartYaml --> SSICredentialIssuer
+    ChartYaml --> SemanticHub
+    ChartYaml --> BPDM
+    ChartYaml --> DataConsumer
+    ChartYaml --> DataProvider
+    ChartYaml --> BDRS
+    ChartYaml --> SSIWalletStub
+    DataConsumer --> EDC
+    DataProvider --> EDC
+    DataProvider --> DTR
+    DataProvider --> SubmodelServer
+````
+
+# 4 TO-BE Design
+
+## 4.1 People
+
+### 4.1.1 Target Group Analysis
+
+Overall data space roles:
+- [Collaboration & Roles](https://catena-x.net/ecosystem/collaboration-roles/)
+- [Who: Roles in the Catena-X ecosystem](https://catenax-ev.github.io/docs/operating-model/who-roles-in-the-catena-x-ecosystem)
+
+The relevant data space roles are:
+
+- Data Consumer
+- Data Provider
+- Enablement Service Provider
+
+Scope: Umbrella HELM Charts
+
+- Enablement Services: These services are included under the umbrella of HELM charts, focusing on enabling
+  functionalities.
+
+Out of Scope: Core services such as Portal or BPDM are not considered within this scope.
+
+Primary target groups:
+
+| No. | Target group                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | Data space roles                                                    | Target group differentiation                                                                                                                                                                                                                                                                            | Behaviour, Needs, Pains & Usage                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+|-----|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| 1   | Developers<ul><li>External Developers (not Tractus-X developers): Utilize the chart for demonstration or evaluation purposes.</li><li>Experienced software and product developers who are developing a business app for a CATENA-X data space. They need to develop the app against the interfaces of the data space and integrate them accordingly.</li><li>They emphasize efficient and cost-effective implementation:<ul><li>Cost Efficiency: They do not want to use expensive SaaS solutions.</li><li>Technical Independence: They lack the knowledge and capacity to deploy the enablement and core services of the data space themselves.</li><li>Focus on Development: They concentrate on application development without delving deeply into the deployment and operation of the underlying infrastructure.</li></ul></li><li>Out of Scope: Developers running tests in test runners are not considered within this scope.</li></ul> | Data Consumer <br/> Data Provider <br/> Enablement Service Provider |                                                                                                                                                                                                                                                                                                         | <ul><li>Needs / sources of information<ul><li><a href="https://eclipse-tractusx.github.io/Kits/">Kit documentation tractus-x</a> for interaction purposes</li><li><a href="https://catenax-ev.github.io/">Catena-X documentation</a> for standards and regulations</li><li><a href="https://github.com/eclipse-tractusx/tractus-x-umbrella">Umbrella documentation</a> for umbrella component information</li></ul></li><li>Challenges → Solution<ul><li>Decentralization e.g. Where are other systems? How to interact with them? → Solution: Umbrella charts and bundles for deployment</li><li>Complex setup → Solution: delivery of small capability bundles</li></ul></li></ul> |
+| 2   | Tester requiring a test system                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | Data Consumer <br/> Data Provider <br/> Enablement Service Provider | <ul><li>Developer (1) tests their feature.</li><li>Tester (2) performs end-to-end testing.</li><li>For the tester, the modular structure is less relevant since they focus on E2E testing, whereas the developer selects the required components.</li><li>The testbed must be easy to deploy.</li></ul> | Same as above from an End-to-end testing perspective.<br/> Typically a tester has less technical know-how than a developer and therefore needs a "one-size-fits-all" (e.g.  Testbed) chart for easier testing.                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+| 3   | SMEs                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | Data Consumer <br/> Data Provider <br/> Enablement Service Provider |                                                                                                                                                                                                                                                                                                         | Need: SMEs developing a service within the Catena-X Data space want an environment to develop and test their service against without the need for expensive SaaS solutions.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+
+## 4.2 Process
+
+### 4.2.1 Use Case View (high-level)
+
+#### Group 1: Product developer
+
+| ID  | Name                                    | Actor             | Description                                                                                                        |
+|-----|-----------------------------------------|-------------------|--------------------------------------------------------------------------------------------------------------------|
+| UC1 | Configure HELM Chart                    | Product Developer | The product developer configures the HELM Chart for the specific environment.                                      |
+| UC2 | Configure Secrets                       | Product Developer | The product developer manages and configures secrets.                                                              |
+| UC3 | Execute Deployment Pipeline             | Product Developer | The product developer successfully executes the deployment pipeline for the HELM Chart.                            |
+| UC4 | Integrate EDC, DTR, and Identity Wallet | Product Developer | The actors integrate the components EDC, Digital Twin Registry, and Identity Wallet for seamless interoperability. |
+| UC5 | Set Up Connection Infrastructure        | Product Developer | The actor sets up the connection infrastructure for linking to the central data space infrastructure.              |
+| UC6 | Maintain Infrastructure Module          | Product Developer | The product developer maintains the modular architecture of the HELM Chart.                                        |
+| UC7 | Ensure Scalability                      | Product Developer | The product developer ensures scalability to support growing numbers of users and data volumes.                    |
+| UC8 | Sandbox Environments                    | Product Developer | The product developer creates local environments to evaluate and experiment with Catena-X components.              |
+
+#### Group 2: Product Tester
+
+| ID  | Name        | Actor          | Description                                                     |
+|-----|-------------|----------------|-----------------------------------------------------------------|
+| UC9 | E2E Testing | Product Tester | The product tester runs end-to-end tests for Catena-X services. |
+
+#### Group 3: Product Manager
+
+| ID   | Name                 | Actor           | Description                                                                                         |
+|------|----------------------|-----------------|-----------------------------------------------------------------------------------------------------|
+| UC10 | Dataspace Evaluation | Product Manager | The Product manager evaluates the dataspace to assess if their product can be used within Catena-X. |
+
+#### Use Case diagram
+
+````mermaid
+flowchart LR
+    PD[Product Developer]
+    PT[Product Tester]
+    PM[Product Manager]
+    UC1[Configure HELM Chart]
+    UC2[Configure Secrets]
+    UC3[Execute Deployment Pipeline]
+    UC4[Integrate EDC, DTR, and Identity Wallet]
+    UC5[Set Up Connection Infrastructure]
+    UC6[Maintain Infrastructure Module]
+    UC7[Ensure Scalability]
+    UC8[Sandbox Environments]
+    UC9[E2E Testing]
+    UC10[Dataspace Evaluation]
+    PD --> UC1
+    PD --> UC2
+    PD --> UC3
+    PD --> UC4
+    PD --> UC5
+    PD --> UC6
+    PD --> UC7
+    PD --> UC8
+    PT --> UC9
+    PM --> UC10
+````
+
+### 4.2.2 Business Process (SCC Artifact)
+
+#### Chart Release Process
+
+Charts will be released using the already existing workflow in the Umbrella Chart repository. The workflow will
+automatically release a Chart, once it is pushed to the "charts/" directory with a new Chart version.
+
+Chart versions should follow [Semantic Versioning](https://semver.org/)
+
+#### Capability Bundle Structure
+
+Capability bundle modularization for the Tractus-X Umbrella Helm chart is a sound architectural and operational design.
+It aligns with both the domain-driven architecture of Catena-X (data exchange, digital twin, identity, semantics are
+distinct domains) and with Kubernetes best practices for managing complex applications (using an umbrella chart to
+bundle related microservices).
+
+Each bundle is self-sufficient, which improves isolation (failures or changes in one domain have minimal impact on
+others) and allows scaling and upgrading along domain lines. It simplifies deployment by allowing “plug-and-play”
+capabilities: an Enablement Service Provider can decide which bundles to operate based on its role e.g., include the
+Digital Twin and Semantic bundles if offering an asset-rich service, or omit them if not. The approach is consistent
+with how other OSS projects deliver multi-component systems, providing one-step installation without sacrificing the
+ability to tweak individual parts.
+
+Why this structure was proposed:
+
+1. **Clear Separation of Concerns**  
+   Each capability bundle (e.g. EDC Data Transfer, Digital Twin, Identity & Trust, Semantic Model) aligns with a
+   specific functional domain. This separation makes it easier to understand the role of each service (e.g., the EDC
+   connector vs. the digital twin registry), reduces coupling between unrelated components, and ultimately makes
+   maintenance and troubleshooting more straightforward.
+2. **Modular Deployment**  
+   Some participants in Catena-X may not need all services (e.g., some might not use the Digital Twin bundle). By
+   structuring the umbrella chart into bundles, a user can enable just those needed capabilities. This leads to leaner
+   installs and avoids unnecessary resource usage.
+3. **Best Practices with Helm**  
+   Using an umbrella chart with subcharts/bundles is a well-recognized Helm best practice for complex applications. It
+   allows a single helm install to set up multiple microservices while still allowing each service to have its own
+   lifecycle, configuration, and version.
+4. **Alignment with Domain-Driven Approach**  
+   Catena-X is organized around distinct, loosely-coupled “building blocks.” Bundling services by domain matches this
+   architectural vision. It’s clear which domain each set of microservices belongs to (EDC for data exchange, identity
+   for credential management, etc.). This clarity also helps new adopters navigate the ecosystem.
+
+````mermaid
+%%{init: {"flowchart": {"subGraphTitleMargin": { "bottom": 10}}}}%%
+flowchart LR
+    subgraph A["Core Services"]
+        Vault["Vault"]
+    end
+
+    subgraph B["Capability Bundle: Identity & Trust"]
+        SSIWalletStub["SSI Wallet Stub"]
+    end
+
+    subgraph C["Capability Bundle: Dataspace Connector"]
+        EDC["EDC"]
+        EDCDB["EDC DB"]
+        EDC .-> EDCDB
+    end
+
+    subgraph "Capability Bundle: Digital Twin"
+        DTR["DTR"]
+        DTRDB["DTR DB"]
+        DTR .-> DTRDB
+    end
+
+    subgraph "Capability Bundle: Data Persistence Layer"
+        SimpleSubmodelServer["Simple Submodel Server"]
+    end
+
+    subgraph "Hausanschluss Actors"
+        subgraph "Data Provider"
+            DataProvider["Data Provider"]
+        end
+        subgraph "Data Consumer"
+            DataConsumer["Data Consumer"]
+        end
+        subgraph "Enablement Provider"
+            EnablementProvider["Enablement Provider"]
+        end
+    end
+
+    EDC -..-> SSIWalletStub
+    EDC -..-> Vault
+    DataProvider --> EDC
+    DataProvider --> DTR
+    DataProvider --> SimpleSubmodelServer
+    DataConsumer --> EDC
+    EnablementProvider --> DataConsumer
+    EnablementProvider --> DataProvider
+````
+
+#### Deployment strategies
+
+##### Role: Data Provider
+
+The standard data provider role consists of an EDC, DTR and Submodel Server Bundles. EDC uses the Identity Wallet Bundle.
+
+````mermaid
+flowchart BT
+    A["Capability Bundle: Identity & Trust"]
+    B["Capability Bundle: Data Persistence Layer"]
+    C["Capability Bundle: Dataspace Connector"]
+    D["Capability Bundle: Digital Twin"]
+    E("Application to be tested/developed")
+    style E fill:#afafaf,color:black
+    F{{"Developer/Tester"}}
+    E --> B
+    E --> C
+    E --> D
+    C --> A
+    F --> E
+````
+
+##### Role: Data Consumer
+
+The standard data consumer role consists of only the EDC Bundle and the Identity Wallet Bundle.
+
+````mermaid
+flowchart BT
+    A["Capability Bundle: Identity & Trust"]
+    B["Capability Bundle: Dataspace Connector"]
+    C("Application to be tested/developed")
+    style C fill:#afafaf,color:black
+    D{{"Developer/Tester"}}
+    C --> B
+    B --> A
+    D --> C
+````
+
+##### Role: Enablement Provider
+
+The Enablement Provider role consists of both the Data Consumer and Data Provider bundles. This allows provisioning of
+data and the consumption of the provisioned data by a application.
+
+````mermaid
+flowchart BT
+    A["Capability Bundle: Identity & Trust"]
+    B["Capability Bundle: Data Persistence Layer"]
+    C("Application to be tested/developed")
+    style C fill:#afafaf,color:black
+    D["Capability Bundle: Digital Twin"]
+    E["Capability Bundle: Dataspace Connector (Provider)"]
+    F["Capability Bundle: Dataspace Connector (Consumer)"]
+    G{{"Developer/Tester"}}
+    C --> B
+    C --> D
+    C --> E
+    C --> F
+    E --> A
+    F --> A
+    G --> C
+````
+
+#### Bring your own
+
+Each Bundle can be deactivated to use your own component. This requires configuration of the component specific
+parameters in the other components.
+
+In this example this would be the configuration of the Identity Wallet within the EDC.
+
+````mermaid
+flowchart BT
+    A("Application to be tested/developed")
+    style A fill:#afafaf,color:black
+    B["Capability Bundle: Dataspace Connector"]
+    C["
Capability Bundle: Identity & Trust
"]
+    D["Own Identity Wallet"]
+    E{{"Developer/Tester"}}
+    A --> B
+    B -- identitywallet - bundle . enabled = false --> C
+    B -- configure --> D
+    E --> A
+````
+
+Using a "bring-your-own" component requires additional configuration. In this case, the identity wallet has to be configured in the EDC configuration section.
+
+Replacing existing Charts with your own solution is not limited to the direct components of the Capability Bundles.  
+This also applies to the dependencies of the bundles which e.g. allows the user to choose another way of provisioning a database.
+
+Components which can be replaced are:
+
+- Capability Bundle: Dataspace Connector
+    - postgresql
+    - vault
+- Capability Bundle: Digital Twin
+    - postgresql
+    - keycloak
+- Capability Bundle: Identity & Trust
+    - ssi-dim-wallet-stub
+- Capability Bundle: Data Persistence Layer
+    - simple-data-backend
+
+To make configuration of "bring-your-own" components easier, the bundle config has to highlight which values are 
+related to which dependency and what to change, if the components should be replaced:
+
+```yaml
+digital-twin-registry:
+  registry:
+    dataSource:
+      # replace this when using your own database
+      # url: jdbc:postgresql://database:5432
+      # user: 
+      # password: 
+```
+
+#### Scalability
+
+It is essential that the deployment of each bundle is entirely independent, allowing the same bundle to be deployed multiple times.
+Every instance must maintain its own unique set of Kubernetes resources, ensuring there is no overlap or shared dependencies between different deployments.
+
+#### Interoperability
+
+To ensure interoperability, the [Tractus-X Release Guidelines](https://eclipse-tractusx.github.io/docs/release/) are followed and [Catena-X standards](https://catenax-ev.github.io/docs/standards/overview) are understood and applied.  
+Additionally, the existing functionality of the Umbrella Chart must be kept and verified to work.
+
+## 4.4 System
+
+### 4.4.1 Context Delimitation / 4.4.2 Interface Documentation
+
+Interactions between an Application acting as Dataprovider or Dataconsumer and the Services which are part of the different Capability Bundles.
+
+````mermaid
+flowchart LR
+    Dataprovider["Dataprovider"] -->|stores data| SubmodelServer["Submodel Server"]
+    Dataprovider -->|creates twins| DTR["DTR"]
+    Dataprovider -->|creates contracts| EDC["EDC"]
+    EDC["EDC"] -->|needs| EdcPosgtres["PostgreSQL Database"]
+    Dataconsumer["Dataconsumer"] -->|negotiate contracts| EDC
+    DTR -->|needs| DtrPostgres["PostgreSQL Database"]
+    EDC["EDC"] -->|needs| IdentityWallet["Identity Wallet"]
+````
+
+# 5 Build
+
+## 5.1 DevOps Setup Definition
+
+### 5.1.1 Tool Chain Definition
+
+##### Version Control & Source Code Management
+
+- **Git & GitHub**: Management of the source code, the Helm Charts, and associated documentation in a centralized
+  repository.
+
+##### Build and CI/CD Tools
+
+- **GitHub Actions**: Automated workflows for linting, testing, packaging, and releasing the Helm Charts.
+- **Helm CLI**: For validating, packaging, and deploying the charts.
+- **Helm Lint**: Performing static analyses to ensure compliance with chart standards.
+
+##### Testing and Validation Tools
+
+- **Chart-testing Tool**: Validation of the Helm Charts based on Kubernetes schemas.
+- **Local Cluster Tests**: Use of tools such as Kind or Minikube to perform integration tests in a test environment.
+
+##### Release Management & Deployment
+
+- **Chart Releaser**: Automated creation and publication of chart releases.
+- **Helm Chart Repository / GitHub Packages**: Hosting and provisioning of the finalized charts.
+
+# NOTICE
+
+This work is licensed under the [CC-BY-4.0](https://creativecommons.org/licenses/by/4.0/legalcode).
+
+* SPDX-License-Identifier: CC-BY-4.0
+* SPDX-FileCopyrightText: 2024 Contributors to the Eclipse Foundation
path: docs/concept/TAP7.1-solution-design.md
user: login: evegufy
body: ```suggestion
* SPDX-FileCopyrightText: 2025 Contributors to the Eclipse Foundation
```
created_at: 2025-04-05T09:44:53Z
author_association: CONTRIBUTOR

PR comments:
user: login: mkanal
created_at: 2025-04-03T09:42:55Z
body: https://github.com/ThomasObermeyer Kindly ask you for a review. 
author_association: CONTRIBUTOR
user: login: evegufy
created_at: 2025-04-07T09:49:03Z
body: @ds-jhartmann please still have look at the failing trufflehog scan, not that it fails on main after you merge this https://github.com/eclipse-tractusx/tractus-x-umbrella/actions/runs/14304777672/job/40086137547?pr=241
author_association: CONTRIBUTOR
user: login: ds-jhartmann
created_at: 2025-04-07T15:19:17Z
body: > @ds-jhartmann please still have look at the failing trufflehog scan, not that it fails on main after you merge this https://github.com/eclipse-tractusx/tractus-x-umbrella/actions/runs/14304777672/job/40086137547?pr=241

Not sure why the workflow is failing. There is no secret present. I'm not that familiar with trufflehog usage. Is there a way to ignore a finding?
author_association: CONTRIBUTOR
user: login: evegufy
created_at: 2025-04-08T11:47:35Z
body: > > @ds-jhartmann please still have look at the failing trufflehog scan, not that it fails on main after you merge this https://github.com/eclipse-tractusx/tractus-x-umbrella/actions/runs/14304777672/job/40086137547?pr=241
> 
> Not sure why the workflow is failing. There is no secret present. I'm not that familiar with trufflehog usage. Is there a way to ignore a finding?

@ds-jhartmann no, I don't think we can just ignore it, I'm afraid that trufflehog will continuously fail then. Also, I noticed that the merge presence of this open PR appears leads to the failure of the trufflehog scan in another open PR: https://github.com/eclipse-tractusx/tractus-x-umbrella/pull/240 https://github.com/eclipse-tractusx/tractus-x-umbrella/actions/runs/14327043264?pr=240
my guess is that this behaviour might be connected to some trugglehog bug, which might already be fixed, if we'd upgrade the github action, unfortunately in this repo nobody took care of enabling dependabot up to now.
I created this issue for introducing dependabot https://github.com/eclipse-tractusx/tractus-x-umbrella/issues/248, if that doesn't work, maybe excluding the docs directory would be an option, I found this https://github.com/trufflesecurity/trufflehog/issues/675
author_association: CONTRIBUTOR
user: login: ds-jhartmann
created_at: 2025-04-08T12:10:40Z
body: Thanks for the quick investigation @evegufy. I noticed that the trufflehog config slightly differs from the TRG https://eclipse-tractusx.github.io/docs/release/trg-8/trg-8-03/, so I just updated it. It seems to be fixed now. 
author_association: CONTRIBUTOR