Skip to content
Merged
Show file tree
Hide file tree
Changes from 20 commits
Commits
Show all changes
24 commits
Select commit Hold shift + click to select a range
b20d410
updated esds
Andrew96897 Jun 18, 2026
ba81ed7
feat: add eSDScom KIT category and navigation items
matbmoser Jun 18, 2026
b008ec0
Update docs-kits/kits/esdscom-kit/adoption-view/adoption-view.md
matbmoser Jun 22, 2026
edbb1d6
Update docs-kits/kits/esdscom-kit/development-view/development-view.md
matbmoser Jun 22, 2026
54c2dd4
Update docs-kits/kits/esdscom-kit/adoption-view/adoption-view.md
matbmoser Jun 22, 2026
5d7bc4f
feat: fixed typos and apply suggestions from code review
matbmoser Jun 23, 2026
79ec6ad
Changes made after attending KIT open office hour
Andrew96897 Jun 25, 2026
8121220
Fix typo in use case description for eSDScom
hillmer Jun 26, 2026
e1f4a6f
Update sidebarsDocsKits.js
A-KKunert Jun 26, 2026
01e4f11
Update adoption-view.md
A-KKunert Jul 10, 2026
397a1c2
Update docs-kits/kits/esdscom-kit/development-view/development-view.md
matbmoser Aug 6, 2026
b30292b
Update docs-kits/kits/esdscom-kit/development-view/development-view.md
matbmoser Aug 6, 2026
ff386a4
Merge branch 'main' into eSDS
matbmoser Aug 6, 2026
e2d460f
Update docs-kits/kits/esdscom-kit/development-view/development-view.md
matbmoser Aug 6, 2026
360a2d0
Update docs-kits/kits/esdscom-kit/development-view/development-view.md
matbmoser Aug 6, 2026
936c2e9
Update content hash in auto-generated kitNavItems.js
matbmoser Aug 6, 2026
ca80597
Update docs-kits/kits/esdscom-kit/resources/REUSE.toml
matbmoser Aug 6, 2026
4826189
Update docs-kits/kits/esdscom-kit/changelog.md
matbmoser Aug 6, 2026
d125198
Update adoption-view and development-view documentation for clarity a…
matbmoser Aug 6, 2026
406f04d
Update versioning and release date for eSDScom KIT in changelog and k…
matbmoser Aug 6, 2026
fbe8c5f
Update docs-kits/kits/esdscom-kit/development-view/development-view.md
matbmoser Aug 10, 2026
3de588b
Update docs-kits/kits/esdscom-kit/development-view/development-view.md
matbmoser Aug 10, 2026
2e38675
Apply suggestions from code review
matbmoser Aug 10, 2026
42c930b
Apply suggestions from code review
matbmoser Aug 10, 2026
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
33 changes: 33 additions & 0 deletions data/kitsData.js
Original file line number Diff line number Diff line change
Expand Up @@ -103,6 +103,7 @@ import GeometryKitLogo from "@site/static/img/kits/geometry/geometry-kit-logo.sv
import CCMKitLogo from "@site/static/img/kits/company-certificate-management/ccm-kit-raw-logo.svg";
import AiServiceKitLogo from "@site/static/img/kits/ai-service/ai-service-kit-raw-logo.svg";
import MaterialAccountingKitLogo from "@site/static/img/kits/material-accounting/material-accounting-kit-raw-logo.svg";
import EsdscomKitLogo from "@site/static/img/kits/esdscom-kit/esdscom-kit-raw-logo.svg";
import PcfDataAcquisitionKitLogo from "@site/static/img/kits/pcf-data-acquisition/pcf-data-acquisition-kit-raw-logo.svg";
// Import Material-UI icons for industries
import DirectionsCar from '@mui/icons-material/DirectionsCar';
Expand Down Expand Up @@ -470,6 +471,38 @@ export const kitsData = {
},
],
useCases: [
{
id: 'esdscom',
name: 'eSDS COMMUNICATION KIT',
logo: EsdscomKitLogo,
logoLicencse: {
type: 'CC-BY-4.0',
authors: '2026 eSDScom Workgroup and contributors; 2026 Catena-X Automotive Network e.V.; 2026 Contributors to the Eclipse Foundation',
licenseUrl: 'https://github.com/eclipse-tractusx/eclipse-tractusx.github.io/blob/main/static/img/kits/esdscom-kit/esdscom-kit-raw-logo.svg.license',
sourceUrl: 'https://github.com/eclipse-tractusx/eclipse-tractusx.github.io/blob/main/static/img/kits/esdscom-kit/esdscom-kit-raw-logo.svg'
Comment on lines +478 to +482
},
logoHeight: 90,
logoWidth: 90,
route: '/docs-kits/next/kits/esdscom-kit/adoption-view',
colors: {
primary: '#E8730C',
gradient: 'linear-gradient(135deg, #F5A623 0%, #E8730C 100%)'
},
maturity: {
currentLevel: 'Sandbox',
graduationStatus: 'draft'
},
deprecated: false,
domain: 'Supply Chain',
industries: ['chemical','automotive'],
description: 'Standardized exchange of safety data sheets, exposure scenarios and compliance information in the global chemical supply chain.',
metadata: {
created: '2025-09-01',
lastUpdated: '2026-08-06',
latestVersion: '0.0.1',
new: true
}
},
{
id: 'ess',
name: 'ESS KIT',
Expand Down
160 changes: 160 additions & 0 deletions docs-kits/kits/esdscom-kit/adoption-view/adoption-view.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,160 @@
---
id: adoption-view
title: Adoption View
description: Data Model of the eSDScom KIT
sidebar_position: 2
---

<!--
Copyright(c) 2026 Contributors to the Eclipse Foundation

See the NOTICE file(s) distributed with this work for additional
information regarding copyright ownership.

This work is made available under the terms of the
Creative Commons Attribution 4.0 International (CC-BY-4.0) license,
which is available at
https://creativecommons.org/licenses/by/4.0/legalcode.

SPDX-License-Identifier: CC-BY-4.0
-->

import Kit3DLogo from '@site/src/components/2.0/Kit3DLogo';

<Kit3DLogo kitId="esdscom" />

Welcome to the eSDScom KIT Adoption View. This view provides a high level business view on the eSDScom KIT with its vision, mission, benefits, and business value.

## Vision & Mission

### Vision

All global chemical regulations have a high impact on company chemical compliance. Registration and notification requirements, communication with suppliers and customers and authorities all sum up to a significant level of bureaucracy that must be handled by every actor in chemical supply chains.
To lower administrative cost it’s highly recommended to exchange those data via a digital twin technology.
The eSDScom standard/KIT within the Catena-X framework embodies a transformative approach to fortify supply chains. This approach holds significant relevance beyond the automotive supply chain and can be effectively applied to other industries characterized. By establishing a standardized, rapid communication for a products safety data information, this empowers stakeholders across the value chain to act swiftly and effectively in the face of challenges. Enhanced transparency and timely information exchange enable members to manage supply chain disruptions, streamline decision-making processes, and mitigate potential regulatory impacts. This proactive and collaborative framework not only elevates operational resilience but also drives cost efficiencies, reduces product approval time, and promotes a more sustainable and responsive supply chain ecosystem. By fostering rapid information flow, the eSDScom is a significant step toward a more interconnected and resilient automotive industry.

### Mission

#### Description / Challenge / Initial Situation

Safety data sheets affect all actors in the supply-chain who purchase/sell, use or contain chemicals in components/systems. Data management of these legally required documents is only possible with a high level of administrative effort.
In an increasingly environmentally conscious world, the standardized exchange of SDS data is of great importance to reduce administrative costs along the supply chain and to ease the way of automated validation of the incoming data.

### Legal Background in a nutshell

Safety data sheets (SDSs) provide information on hazards and deviated risk management measures. Economic operators, such as manufacturers, importers and downstream users frequently need to send or receive SDSs, as required under regulations across the globe which all implement the UN Globally Harmonized System GHS. In the EU, the main regulations are REACH (registration, evaluation, authorisation and restriction of chemicals), and CLP (classification, labelling and packaging of chemicals).
All global chemical regulations have a high impact on company chemical compliance. Registration and notification requirements, communication with suppliers and customers and authorities all sum up to a significant level of bureaucracy that must be handled by every actor in chemical supply chain.
Through the standardized maintenance of chemical safety information and the seamless integration of information exchange, stakeholders gain a dynamic view of the supply chain, facilitating rapid adaptation to both imminent and potential supply chain or regulatory changes.

#### The eSDScom project in a nutshell

eSDScom is the industry standard for sending safety data sheets, exposure scenarios and relevant compliance information in the global chemical supply chain. It is a comprehensive and efficient solution saving money and time, covering the following:
• Safety Data Sheets to assist with occupational safety and health
• Notification data to help customers with their legal obligations
• for Europe: Exposure Scenarios and ENES achievements for downstream users
For more information, please consult the History section in the Development View of this KIT.

## Business Value

### One Open Data Model

eSDScom is a standardized exchange format defined by industry. It currently covers the regulatory regions of the EU, USA, China, Argentina, Mexico, and more.
The data model covers:

- Information for Safety Data Sheets and to work with management systems for hazardous chemicals
- Notification data to help customers with their legal obligations
- for Europe: Exposure Scenarios (for communication, as an annex to safety data sheets)

### Easy to read and maintain

Developers don't read manuals, at least usually. Thus eSDScom is implicitly designed to be educational and to avoid implementations that misinterpret data.

### Low Cost

Compared to IUCLID and proprietary solutions, eSDSCom is most likely the comprehensive model with the lowest implementation cost. Its maintenance by an expert group assures compliance, helping internal software to stay up to date.

### Value Proposition

SDS sending, inhouse collection and processing

#### Benefit

Easily send new/revised SDSs to multiple recipients. Replace multiple methods (email/mail/customer portals/etc.) with just one IT solution.

#### Target Stakeholders

OEMs | SMEs | Chemical Supplier | IT Solution Providers | etc.

#### Measurable Outcomes

Increase SDS quality as suppliers respond to recipient comments, less manual human errors, decreased administrative burden (time and cost saving).
Increase in SDS data quality due to potential for built-in data validity checks and accumulated recipient comments.

## Access & Usage Policies

### Example Access Policy

To decide which company can use the data asset under specific conditions, usage policies (also referred to as contract policies) are used. Therefore, they are more specific than access policies and only used just after access is granted. Currently, the usage policies aren't technically enforced but based on a legal framework agreements. Signing of framework agreements can be enforced during contract negotiation depending on the connector implementation.
Policies are defined based on the W3C ODRL format. This allows a standardized way of formulating policy payloads. It further allows to stack different constraints with the odrl:and operator. Therefore, every data provider can decide on his or her own under which conditions their data assets are shared in the network. It is recommended to restrict the data usage for all exchanged data standards. An example of one usage policy containing three different constraints is shown and described in the following:

```json
{
"@context": {
"@vocab": "https://w3id.org/edc/v0.0.1/ns/"
},
"@type": "PolicyDefinition",
"@id": "esdscom",
"policy": {
"@type": "Set",
"@context": [
"https://w3id.org/catenax/2025/9/policy/odrl.jsonld",
"https://w3id.org/catenax/2025/9/policy/context.jsonld"
Comment on lines +110 to +111

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is where I meant. @jSchuetz88 is possible to use 2026 here?

],
"permission": [
{
"action": "use",
"constraint": [
{
"and": [
{
"leftOperand": "UsagePurpose",
"operator": "isAnyOf",
"rightOperand": [
"cx.esdscom.base:1"

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is this aligned with the Expert Group from data sovereignty? @DanielaWuensch

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure if this is how we should reference.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

was already checked.

@A-KKunert A-KKunert Jun 26, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Was aligned with Daniela Wuensch.

Mail von Freitag, 10. April 2026:
"Hallo Dirk, hallo Anita,

Die Änderung in CX-0152 zum eSDScom purpose sind in diesem PR an dieser Stelle:

https://github.com/catenax-eV/product-standardization-prod/pull/597/changes#diff-b809678ec8be329cbfeb3079b29409b6338f87cce75bab0075355a9931e0b6a9R221

bereit für den Review. Darauf könnt ihr euch dann mit dem rightOperand cx.esdscom.base:1 des Usage Purpose beziehen.

Viele Grüße,
Daniela"

]
},
{
"leftOperand": "FrameworkAgreement",
"operator": "eq",
"rightOperand": "DataExchangeGovernance:1.0"
}
]
}
]
}
],
"obligation": [],
"prohibition": []
}
}
```

More information can be found in the Policies in Catena-X of the Connector KIT.

## Semantic Models

The eSDScom ontology is based on the eSDScom XML schema definition version 5.6, available at [esdscom.eu](https://esdscom.eu) and converted to SAMM by a script to ensure consistency.

The original eSDScom XML model, represented in several XML schema definitions (XSD files), is too large to be represented here. Please use the [eSDScom version 5 downloads](https://www.esdscom.eu/downloads/version-5) or [sdscom-xml releases](https://github.com/esdscom/sdscom-xml/releases/) to download the schema definition.

## 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: 2026 [eSDScom Workgroup](https://esdscom.eu) and contributors
- SPDX-FileCopyrightText: 2026 [Qualisys GmbH](https://qualisys.eu)
- SPDX-FileCopyrightText: 2026 [Volkswagen AG](https://www.volkswagen.de)
- SPDX-FileCopyrightText: 2026 Catena-X Automotive Network e.V.
- SPDX-FileCopyrightText: 2026 Contributors to the Eclipse Foundation
- Source URL: [https://github.com/eclipse-tractusx/eclipse-tractusx.github.io](https://github.com/eclipse-tractusx/eclipse-tractusx.github.io)
56 changes: 56 additions & 0 deletions docs-kits/kits/esdscom-kit/changelog.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,56 @@
---
id: changelog
title: Change Log
description: Release Notes of the eSDScom KIT
sidebar_position: 1
---

<!--
Copyright(c) 2025 Contributors to the Eclipse Foundation

See the NOTICE file(s) distributed with this work for additional
information regarding copyright ownership.

This work is made available under the terms of the
Creative Commons Attribution 4.0 International (CC-BY-4.0) license,
which is available at
https://creativecommons.org/licenses/by/4.0/legalcode.

SPDX-License-Identifier: CC-BY-4.0
-->

import Kit3DLogo from '@site/src/components/2.0/Kit3DLogo';

<Kit3DLogo kitId="esdscom" />

All notable changes to this KIT will be documented in this file.

The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/), and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).

## [0.0.1] - 2026-08-06

### Added

- Initial release of the eSDScom KIT
- Complete adoption view documentation:
- Vision and mission statement
- Business value propositions
- Use case documentation
- Business process descriptions
- Semantic models
- Standards compliance documentation
- Added development view documentation:
- Architecture overview and diagrams
- Data model and semantic model references
- Added architecture diagrams and resources in `resources/`

## 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: 2026 [eSDScom Workgroup](https://esdscom.eu) and contributors
- SPDX-FileCopyrightText: 2026 [Qualisys GmbH](https://qualisys.eu)
- SPDX-FileCopyrightText: 2026 [Volkswagen AG](https://www.volkswagen.de)
- SPDX-FileCopyrightText: 2026 Contributors to the [Eclipse Foundation](https://eclipse.org)
- Source URL: [https://github.com/eclipse-tractusx/eclipse-tractusx.github.io](https://github.com/eclipse-tractusx/eclipse-tractusx.github.io)
Comment thread
matbmoser marked this conversation as resolved.
Loading
Loading