FAZ news about KITs

blog/2023-11-30-faz-news.mdx

@@ -0,0 +1,24 @@
+---
+title: Dataspace instead of black box
+description: The centerpiece of the data space are the so-called „KIT"-blocks
+slug: news-faz
+date: 2023-11-30T09:00
+hide_table_of_contents: false
+authors:
+  - name: Maximilian Ong
+    title: Business Domain Architect Catena-X
+    url: https://github.com/maximilianong
+    image_url: https://avatars.githubusercontent.com/u/83761111?v=4
+    email: [email protected]
+---
+
+![eclipse tractus x logo](@site/static/img/23-11-29_OliverGanser-KITs.png)
+
+Oliver Ganser talks what can be learned about digital, sustainable, and resilient corporate development through Catena-X. He also mentions Tractus-X and specifically our KITs.
+
+Thats why we tried to translate this part for the community:
+
+
+"The centerpiece of the data space are the so-called „KIT"-blocks ("Keep it together": https://eclipse-tractusx.github.io/ ). KITs are the booster elements for every use case, providing an ecosystem with countless solution providers for a problem: collaborative, interoperable, and sovereign in their offerings. The necessary standards, data models, legal frameworks, installation scripts, etc. for the development of industrial solutions are summarized in the "KITs" and made available to all partners via open source."
+<!--truncate-->
+You can find the full article here: [FAZ.net article](https://www.faz.net/pro/d-economy/transformation/datenraum-statt-blackbox-19344753.html).

docs/release/trg-0/trg-8-01.md

@@ -0,0 +1,46 @@
+---
+title: TRG 8.01 - KIT General
+sidebar_position: 1
+---
+
+:::caution
+Proposed release date: "mandatory after": 19th of May 2023
+:::
+
+| Status     | Created      | Post-History                           |
+|------------|--------------|----------------------------------------|
+| Draft      | 26-Oct-2023  | Initial contribution                   |
+
+## Why
+
+KIT means Keep It Together. A KIT contains all the artefacts that are relevant to participate in the Catena-X data space as an operator, data provider or solution / app provider. These stakeholders have one place with all the information they need. For example an explaination of an API, the specification of it and the deployment instructions. The target of a KIT should be that you have no need to visit any other information source.
+
+A detailed explaination can be found here:
+https://eclipse-tractusx.github.io/developer
+
+This TRG serves to maintain a **consistent structure** and ensure content **quality** for the stakeholders.
+
+## Description
+
+For providing a KIT to the Eclipse project Tractus-X please be aware of the "getting started" as a contributor.
+
+Prerequisites:
+https://eclipse-tractusx.github.io/docs/oss/getting-started
+
+- **TRG 8.02 KIT Graduation** : A KIT is always structured the same way and follows three graduation stages
+- **TRG 8.03 KIT Artefacts** : Each of the artefacts in a KIT are explained with examples
+- **TRG 8.04 KIT Structure** : The project structure inside the repository and the adjustments that are needed for Docusaurus 
+
+
+
+Describe the TRG on how to do the TRG. Provide a golden path: In best case with code example or/and step by step guide.
+
+00 = general introduction
+01 = Graduation w. Versioning
+- Repository not needed - just when .. 
+
+02 = Artefacts
+- Reference implementation would reference to Trg 2.04
+- API via Swagger UI
+- 
+03 = Structure 

docs/release/trg-0/trg-8-03.md

@@ -0,0 +1,244 @@
+---
+title: TRG 8.03 - KIT Artefacts
+sidebar_position: 1
+---
+
+:::caution
+Proposed release date: "mandatory after": 19th of May 2023
+:::
+
+| Status     | Created      | Post-History                           |
+|------------|--------------|----------------------------------------|
+| Draft      | 26-Oct-2023  | Initial contribution                   |
+
+
+This explains each artefacts a KIT can or must follow - depending on the graduation stage (TRG 8.02)
+
+## ADOPTION VIEW
+
+The adoption view gives a general introduction to the KIT. Provide an understanding to an OEM, a solution provider or data provider whats the main purpose, which industry problem is this KIT solving.
+
+### Vision & Mission
+
+**| Mandatory for every KIT and all graduation stages |**
+
+The vision describes the strategic objectives of a KIT and how it aims to inspire solution providers.
+
+Deliverables:
+
+- Vision catch phrase + context
+- Mission catch phrase
+- Context to the use case
+
+Starting with the **vision of the KIT** (one or two catching phrases)
+
+`Example from BPDM:`
+Unique business partner data sets for the whole data space. Basis for integration value-adding services in the area of business partner data management.
+
+#### The missions of the KIT
+
+**| Mandatory for every KIT and all graduation stages |**
+
+The mission explains why we are providing the KIT describing a concrete industry problem.
+
+`Example from BPDM:` “The Kit provides a homogenous semantic with an open data model, high data quality and one access point to the business partner data sets.”
+
+#### Giving more context with explaining the connection to the use case
+
+`Example from BPDM:`
+The BusinessPartner Kit provides high-quality data records of business partners called golden record, including a unique identifier, the business partner number (BPN).
+…
+
+### Business Value
+
+**| Mandatory for every KIT that is related to a use case and all graduation stages |**
+
+The business value describes the benefits for an service provider by using a KIT in order to create a commercial or non-profit solution for the Catena-X marketplaces.
+
+Deliverable:
+About 3 to 5 top business values (title + description)
+
+`Example from BPDM:`
+
+One open data model: Application and Service provider can reduce investments to integrate due to one data model / API specification and open interface. The pool API enables the integration and offering of value-added services and innovation based on high-quality master data.
+
+Access to new market potentials: Potential to scale customer group and access new market potentials via Catena-X marketplace and shared service network. The BP Kit enables an interoperable foundation for value-added services.
+
+The unique identifier: BPN is the unique number to identify and find partners in the Catena-X network. It will also provide high quality data sets from business partners, their legal unit, sites and addresses.
+
+### Use Case / Domain explanation
+
+**| Mandatory for every KIT that is related to a use case and all graduation stages |**
+
+This gives more insights into the use case or domain itself.
+
+- Todays challenge
+- Values for taking the challenge
+- Benefits for OEM, SME, Solution Provider
+
+Deliverable: Status quo, challenge and the benefits from different perspectives
+
+`Example from BPDM:`
+Business Partner KIT comes from the use case Business Partner Data Management.
+
+Status Quo / Todays challenge:  
+Most of today’s automotive companies have to invest a significant amount to keep their individual partner master data updated and correct, since outdated or incorrect data records result in federal fines and wrong claims / billing processes. The industry spends a vast amount into an area that is non differentiating, regulated and executed redundantly across the partners.
+
+For this, cutting individual company costs by offering the golden master data record as a shared service and proactively reduce Business Partner risk via collaborative value-add services.
+
+This will become the industry’s largest golden record collection as a shared and cost-optimized service (quality tested by the biggest players).
+
+OEMs and small-medium enterprises can:
+
+- Reduce today’s individual investments in master data mgt.
+- Re-allocate freed-up resources to differentiating / critical tasks
+- Time to value within 6 months, due to standard interfaces and mapping tools (e.g. SAP)
+- Increase data quality and use industry collective wisdom to act pro-actively (e.g. fraud alerts)
+
+Solution Provider:
+
+- Reduce investments to integrate due to one Data Model and open interface.
+- The Kit enables the offering of value-add services and innovation based on golden record and collective wisdom.
+- Potential to scale customer group and access new market potentials via marketplace and shared service network.
+
+### Tutorials
+
+**| Mandatory for the 'gratuated' stage. Optional for 'sandbox' and 'incubating' |**
+
+A tutorial provides educational resources that provides step-by-step guidance on how to use a KIT. Tutorials can be delivered in various formats, such as videos or written text. It may also provide additional resources for further exploration of the topic.
+
+Deliverables:
+
+- Description
+- Tutorial video or screenshot documentation
+
+### Whitepaper
+
+**| Optional |**
+
+A whitepaper outlines the overall objectives of a KIT regarding a specific business problem. It provides readers with background information on the topic, identifies key challenges and solutions to those challenges, evaluates alternative approaches to solving the business problem at hand, and offers recommendations for action.
+
+Deliverable:
+
+- Description
+- Link to the whitepaper
+
+### Semantic Models
+
+**| Mandatory for every KIT that is related to a use case + for the 'incubating' stage |**
+
+The semantic data models are a method of structuring data that includes semantic information that adds a basic meaning to the data and the relationships that lie between them to enable interoperability.
+
+Deliverables:
+
+- Description
+- Link to the semantic data models (GitHub)
+
+`Example from Traceability:`
+https://eclipse-tractusx.github.io/docs-kits/kits/Traceability%20Kit/Adoption%20View%20Traceability%20Kit#semantic-models
+
+
+### Logic / Schema
+
+**| Mandatory for every KIT that is related to a use case + for the 'incubating' stage |**
+
+Logic / schemas provides a definition of the minimum viable business process that must be implemented to enable interoperability.
+
+Deliverables: Description
+
+### Business Process
+
+**| Mandatory for every KIT that is related to a use case + for the 'incubating' stage |**
+
+Data sovereignity is one of the main principles of Catena-X and a major topic for the participants in the data space. This part should help to understand how the business process works and provides a blue print on how access & usage policies **could** look like. 
+
+- Business Architecture
+- Access & Usage Policies
+
+### Standards
+
+**| Mandatory for every KIT that wants to go to the 'incubating' stage |**
+
+Links to the relevant standards (Association Library). Add the relevant number of the standard, the name and version of the standard.
+
+`Example:`
+CX - 001 Standardname (Version 2.0)
+
+### Notice
+
+**| Mandatory for every KIT and all graduation stages |**
+
+KIT documentation works under the CC-BY-4.0 license. Therefore you need to add the "notice" part to make transparent which companies worked on this KIT.
+
+`Example:`
+
+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: 2023,2023 ZF Friedrichshafen AG
+- SPDX-FileCopyrightText: 2023,2023 Bayerische Motoren Werke Aktiengesellschaft (BMW AG)
+- SPDX-FileCopyrightText: 2023,2023 SAP SE
+- SPDX-FileCopyrightText: 2023,2023 Volkswagen AG
+- SPDX-FileCopyrightText: 2023,2023 Robert Bosch GmbH
+- SPDX-FileCopyrightText: 2023,2023 Mercedes Benz Group
+- SPDX-FileCopyrightText: 2023,2023 BASF SE
+- SPDX-FileCopyrightText: 2023,2023 Schaeffler AG
+- SPDX-FileCopyrightText: 2023,2023 Contributors to the Eclipse Foundation
+- Source URL: https://github.com/eclipse-tractusx/bpdm
+
+## Development View
+
+The development view provides developers with resources to accelerate the development of apps and services.
+
+### API Specifications
+
+**| Mandatory for every KIT that wants to go to the 'incubating' stage |**
+
+Deliverables:
+
+- Introduction to the API / specification of the API
+- Whats the main focus of the API
+- Integration of the OpenAPI file
+- Use case examples for the API endpoints and how to use them
+
+`Example from DataChain KIT:` The API of the Item Relationship Service (IRS) for retrieving item graphs along the value chain of CATENA-X partners.
+
+[`Example for OpenAPI integration:`](/docs-kits/kits/Business%20Partner%20Kit/Software%20Development%20View/Pool%20Api/business-partner-data-management-pool)
+
+### Sample Data
+
+
+
+Deliverable:
+
+- Description on how to use the sample data
+- File with sample data
+
+### Reference Implementation
+
+Deliverable:
+
+- Description
+- Link to repository
+
+### Documentation in the context of development
+
+Deliverable:
+
+- Arch42
+- Usage examples
+- More explaination on how to use the API in different scenarios
+
+## Operations View
+
+... provides resources to deploy and operate centralized & decentralized Catena-X offerings in your IT environment (e.g., on-prem, cloud).
+
+Deliverables:
+**Quick Setup Guide / Installation Instructions**
+
+- Prerequisites (if they exist)
+- Authorization information
+- Deployment
+  **Deployment Scripts**
+
+

utils/newsTitles.js

@@ -1,4 +1,9 @@
 export const newsTitles = [
+  {
+    date: "30.11.2023",
+    title: "The centerpiece of the data space are the so-called KIT-blocks",
+    blogLink: "/blog/news-faz"
+  },
   {
     date: "28.11.2023",
     title: "New launch of tutorials section / First E2E adopter Journey tutorial",