(feat): add Unit-Process-as-a-Service (UPaaS) KIT

[linus3976]

Description

Adds the initial Sandbox release of the Unit Process-as-a-Service (UPaaS) KIT, introducing semiconductor unit processes as tradeable marketplace services using wafer testing as the reference scenario.

This PR introduces:

• Adoption View and Development View documentation for the UPaaS KIT
• UPaaS semantic data model (RDF), structured across three levels (supply chain, production planning, production execution), based on the Digital Reference (DR), SEMIKONG, and the PPR/CSS modeling lines
• BPMN 2.0 business process diagram for the requester-provider interaction lifecycle
• Wafer Testing AAS submodel (Metadata + Electrical Testing)
• Qualified Synthetic Data (QSD) pipeline description for non-confidential wafer-testing data
• Protocols section documenting the Dataspace Protocol / HTTPS / ODRL / AAS REST API stack used for exchange
• KIT logo (two variants: color, and white/icon-only) and changelog

Note: The KIT logo was created with AI assistance. Is a regular copyright notice like for the other files sufficient or do I need to create a more specific/special one?

Fixes or Updates #1667

Pre-review checks

Please ensure to do as many of the following checks as possible, before asking for committer review:

• DEPENDENCIES are up-to-date. Dash license tool. Committers can open IP issues for restricted libs.
• Copyright and license header are present on all affected files

[matbmoser]

asked review from copilot

[Copilot]

Pull request overview

This PR adds a new Sandbox KIT (“Unit Process-as-a-Service (UPaaS)”) to the docs-kits site, including initial Adoption/Development documentation, resources/sample data, and registering the KIT so it appears in navigation and the KIT library.

Changes:

• Added the UPaaS KIT documentation set (Adoption View, Development View, Changelog) plus supporting resources/sample data with REUSE metadata.
• Added the UPaaS KIT logo (SVG) with a .license sidecar.
• Registered the KIT in data/kitsData.js, sidebarsDocsKits.js, and regenerated utils/generated/kitNavItems.js.

Reviewed changes

Copilot reviewed 9 out of 25 changed files in this pull request and generated 5 comments.

Show a summary per file

File	Description
utils/generated/kitNavItems.js	Adds the UPaaS KIT to the auto-generated nav items for the Semiconductor category.
static/img/kits/unit-process-as-a-service/unit-process-as-a-service-kit-raw-logo.svg	New UPaaS KIT raw logo asset.
static/img/kits/unit-process-as-a-service/unit-process-as-a-service-kit-raw-logo.svg.license	License sidecar for the new logo.
sidebarsDocsKits.js	Adds a sidebar category for the UPaaS KIT docs.
docs-kits/kits/unit-process-as-a-service-kit/sample-data/REUSE.toml	Declares licensing for sample data assets.
docs-kits/kits/unit-process-as-a-service-kit/sample-data/edc-exchange-log.md	Adds sample EDC exchange log documentation and NOTICE.
docs-kits/kits/unit-process-as-a-service-kit/resources/REUSE.toml	Declares licensing for resources (images/diagrams).
docs-kits/kits/unit-process-as-a-service-kit/resources/architecture_overview.svg	Adds an architecture overview diagram as SVG.
docs-kits/kits/unit-process-as-a-service-kit/development-view/development-view.md	Adds Development View documentation for the KIT.
docs-kits/kits/unit-process-as-a-service-kit/changelog.md	Adds KIT changelog with initial version entry and NOTICE.
docs-kits/kits/unit-process-as-a-service-kit/adoption-view/adoption-view.md	Adds Adoption View documentation for the KIT.
data/kitsData.js	Registers the KIT master data (logo, route, metadata, industry inclusion).

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[linus3976]

Hi Mathias,

I wanted to ask if any action on my part is required (like fixing the conflicts pointed out by the copilot review).
If not are you taking care of them and is everything in line for the September release?

Thanks for your help!

Best,
Linus

[matbmoser]

Hi @linus3976,

Some comments from my side,

Great kit by the way, looks cool the structure and there are some things which need to be fix:

Please define a usage policy here also maybe?? Since this one is just access policy.

if you use the shema from Catena-x you can create your own usage purpose, is allowed by the schema (which would make sense to reuse) adding a key like using a key like sx.upaas.core:1 or cx.semiconductor.upaas:1

example https://eclipse-tractusx.github.io/docs-kits/next/kits/esdscom-kit/adoption-view#example-access-policy

{
  "@context": {
    "@vocab": "https://w3id.org/edc/v0.0.1/ns/"
  },
  "@type": "PolicyDefinition",
  "@id": "policy-id-placeholder",
  "policy": {
    "@type": "Set",
    "@context": [
      "https://w3id.org/catenax/2025/9/policy/odrl.jsonld",
      "https://w3id.org/catenax/2025/9/policy/context.jsonld"
    ],
    "permission": [
      {
        "action": "use",
        "constraint": [
          {
            "and": [
              {
                "leftOperand": "UsagePurpose",
                "operator": "isAnyOf",
                "rightOperand": [
                  "sx.upaas.core:1"
                ]
              },
              {
                "leftOperand": "FrameworkAgreement",
                "operator": "eq",
                "rightOperand": "DataExchangeGovernance:1.0"
              }
            ]
          }
        ]
      }
    ],
    "obligation": [],
    "prohibition": []
  }
}

something like this feel free to add :)

Another thing I will change the directory from sample-data to "Documentation" which is the normal module for including sample data :)

The notice is also wrong need to be like this without the [] in the template it was only a placeholder:

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: 2026 Infineon Technologies AG
SPDX-FileCopyrightText: 2026 Fraunhofer-Gesellschaft zur Förderung der angewandten Forschung e.V. (Fraunhofer-Institut für Werkzeugmaschinen und Umformtechnik IWU)
SPDX-FileCopyrightText: 2026 EXPO21XX GmbH
SPDX-FileCopyrightText: 2026 Contributors to the Eclipse Foundation
Source URL: https://github.com/eclipse-tractusx/eclipse-tractusx.github.io

[matbmoser]

I have added some updates you were forgetting completely the DCP protocol, which is used by every EDC connector and the decentralized identity wallets. Additionally you were forgetting to mention the Eclipse Tractus-X EDC and to cross reference to the Connector KIT which contains the documentation on how it works. I have done that for your now.

Also important I have fixed the notice copyright declaration it was failing.

[matbmoser]

@linus3976 tell me your feedback regarding the policy, add it if you want and then I can approve and merge it :)

[matbmoser]

@linus3976 do you want to be added as contributor in tractusx?

[linus3976]

Hi @matbmoser , thanks for all your help and the feedback!! Really appreciate it :))

I've added the usage policy you suggested, let me know if everything is fine.
You can also add me as a contributor :)

[matbmoser]

Great Job!!! Thank you @linus3976 !

[matbmoser]

Building did not worked, I cant merge it now...

[Copilot]

Pull request overview

Copilot reviewed 10 out of 26 changed files in this pull request and generated no new comments.

Suppressed comments (3)

docs-kits/kits/unit-process-as-a-service-kit/development-view/development-view.md:273

• Typo in the protocols table: “particiapant” should be “participant” (otherwise the rendered docs will show the misspelling).

| Dataspace Claims Protocol (DCP) | Used by the EDC control plane and the Decentralized Identity wallet to enable authentication and trust in between dataspace particiapant identities. | [Decentralized Claims Protocol](https://eclipse-dataspace-dcp.github.io/decentralized-claims-protocol/v1.0.1/) |

docs-kits/kits/unit-process-as-a-service-kit/documentation/edc-exchange-log.md:6

• Frontmatter id is set to documentation, which makes this page’s doc id/URL misleading (and typically results in a duplicated path segment like .../documentation/documentation). It would be clearer to use an id that matches the page purpose/file name (or omit id entirely).

---
id: documentation
title: Documentation - Exchange Log
description: 'EDC Data Exchange Logs from Unit Process as a Service KIT'
sidebar_position: 3

docs-kits/kits/unit-process-as-a-service-kit/documentation/edc-exchange-log.md:107

• This exchange log includes multiple environment-specific hostnames (e.g. edc-2-dsp.opaix.semix-int3.kubernetes.htw-dresden.de). If this is meant as reusable documentation, consider replacing these with stable placeholders (e.g. https://<provider-dsp-host>/api/v1/dsp) to avoid link rot and unintentionally publishing internal environment details.

                    "@id": "0794daa4-0e53-4217-b4f9-b341ce217863",
                    "@type": "dcat:DataService",
                    "dcat:endpointDescription": "dspace:connector",
                    "dcat:endpointUrl": "https://edc-2-dsp.opaix.semix-int3.kubernetes.htw-dresden.de/api/v1/dsp",
                    "dcat:endpointURL": "https://edc-2-dsp.opaix.semix-int3.kubernetes.htw-dresden.de/api/v1/dsp"

[matbmoser]

Now we can merge!