Skip to content

Commit 091fdd4

Browse files
Merge pull request #1273 from seb-l0/main
Adapt KIT Traceability
2 parents a9313b1 + cc21fb8 commit 091fdd4

File tree

2 files changed

+149
-88
lines changed

2 files changed

+149
-88
lines changed

docs-kits/kits/traceability-kit/adoption-view.mdx

Lines changed: 6 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -79,35 +79,31 @@ Special characteristics are product or process characteristics that may have an
7979

8080
Special Characteristics are:
8181

82-
- suitable for communicating, product quality and securing in the supply chain.
83-
- Characteristics that require increased care in order to avoid production issues and ensure the quality of the products.
84-
- defined and recorded with the supplier during development.
82+
- suitable for securing and verifying product quality in the supply chain.
83+
- Characteristics that require increased care in order to avoid production issues.
84+
- defined with the supplier during development.
8585

8686
Special Characteristics are divided into three categories:
8787

8888
- Legal / relevant to legislation / homologation,
8989
- Safety
9090
- Function
9191

92-
> :raised_hand: All products with safety or legal relevant properties, markings or functions are traceability and compliance relevant. Special Characteristics are also mentioned on VDA organization. More details can be found on [VDA home page](https://www.vda.de/de).
92+
> :raised_hand: All products with safety or legal relevant properties, markings or functions are traceability and compliance relevant. Special Characteristics are also mentioned on VDA organization. More details can be found on [VDA home page](https://www.vda.de/en).
9393
9494
Data on the Special Characteristics are collected within the supply chain, but not systematically forwarded to the OEM. The aim is to improve data exchange and consistency for special characteristics.
9595

9696
- Data collection and provision for critical components
9797
- Data collection for a limited period of time, when required, in the event of quality problems or as part of industrialization.
9898

99-
The exchange between supplier and OEM is currently done on single data exchange with special data format accepted by the partners. That means every data exchange has its single implementation. The more interfaces there are, the more difficult it becomes to manage and operate.
100-
101-
Catena-X is to be used for data exchange within the supply chain. Since traceability must be ensured for special characteristics, it is advisable to supplement the Catena-X Use Cases Industry Core and Traceability with an additional functionality (additional aspect model) for the special characteristics. The special characteristics will be directly linked to the digital twin.
99+
The exchange between supplier and OEM is often done by ad-hoc data exchange without any standardization. Therefore, Catena-X should be used to standardize the data exchange. Since traceability must be ensured for special characteristics, we make use of the Industry Core (Part Instance) with an additional aspect model for the special characteristics: `SpecialCharacteristicMeasurement`. The special characteristics will be directly linked to the digital twin.
102100

103101
#### Processual Approach
104102
The target vision aims to enable an end-to-end (E2E) data exchange of special characteristics via Catena-X in three main steps:
105103

106104
- **Requesting Special Characteristics:** The customer should have the capability to request special characteristics from the supplier.
107105
- **Exchanging Specification Data:** The exchange of specification data for special characteristics should be possible at the part type level.
108-
- **Consuming Measured Data:** The customer should be able to consume the measured data (special characteristics) provided by the manufacturer.
109-
110-
In this development phase, both the consumer and the provider are responsible for defining a format for requesting and exchanging information on the specifications of the special characteristics. The consumption of the measurement results is based on the expansion of the digital twin to include the aspect of special characteristics as defined in the [Development View](https://eclipse-tractusx.github.io/docs-kits/kits/traceability-kit/software-development-view/data-provider-development-view#specialcharacteristics).
106+
- **Consuming Measured Data:** The customer should be able to consume the measured data `SpecialCharacteristicMeasurement` provided by the manufacturer.
111107

112108
### Benefits for OEM, SME and Solution Provider
113109
#### OEM

0 commit comments

Comments
 (0)