KIT Master Data Overview

Status	Created	Post-History
Active	07-Nov-2025	Initial creation of master data overview

Master Data Overview

This page provides a comprehensive overview of all KITs, industries and dataspaces in the Eclipse Tractus-X ecosystem. The master data is maintained in the kitsData.js file and serves as the foundation for organizing KITs and dataspace implementations for the dynamic website generation. In this documentation you will find the different data models that are needed to be followed in order for the webpage to render correctly the different KITs, sections and industries.

KIT Master Data File Location

The master data is located at the kit master data file:

/data/kitsData.js

What is Master Data?

The master data includes two primary components that structure the entire ecosystem, it is there to automatizate the website visualization of the KITs and allows the tracking of the KIT Lifecycle on a single source of truth. It also allows to easily add new industries, dataspaces, and KITs without modifying the website codebase.

Industry Master Data

Core information about each industry vertical:

• Unique ID, name, and subtitle
• Icon component, colors, and gradient styling
• Description and purpose within the ecosystem
• Array of dataspace implementations within this industry (content is optional)

Dataspace Master Data

Essential information about each dataspace implementation:

• Unique ID, name, and subtitle
• Logo (SVG/PNG) (transparent background and no claims & MUST be hosted by the dataspace owner)
• Dataspace Layers colors, and gradient styling
• Detailed description and subtitle
• Official website URL for the dataspace
• Which industry vertical this dataspace belongs to

KIT Master Data

Includes the essential details for each KIT, such as:

• Unique identifier, name, logo, and route to documentation
• Branding colors and gradients
• Maturity level and status
• Domain categorization and deprecation status

Industry Data Model

To add an industry a object with the semantic described in this section must be added to the master data at the industries key.

Field Descriptions

Field	Type	Required	Description
id	string	Yes	Unique identifier for the industry (lowercase, hyphenated)
name	string	Yes	Display name of the industry
subtitle	string	Yes	Descriptive subtitle for the industry
description	string	Yes	Comprehensive description of the industry's scope and KIT applications
icon	Component	Yes	Material-UI icon component representing the industry
gradient	string	Yes	CSS gradient definition for visual branding
dataspaces	array	Yes (can be empty)	Array of dataspace objects associated with this industry

Structure

import MaterialUIIcon from '@mui/icons-material/MaterialUIIcon';

industries: [
  {
    id: 'industry-id',
    name: 'Industry Name',
    subtitle: 'Industry Subtitle',
    description: 'Detailed description of the industry...',
    icon: MaterialUIIcon,
    gradient: 'linear-gradient(135deg, #color1, #color2)',
    dataspaces: [
      // Array of dataspace objects (with the dataspace data model)
    ]
  },
  ...
]

Example: Automotive Industry

{
  id: 'automotive',
  name: 'Automotive',
  subtitle: 'Automotive Industry',
  description: 'Industry Specific KITs for the automotive industry, ...',
  icon: DirectionsCar,
  gradient: 'linear-gradient(135deg, #ffa600, #b3cb2d)',
  dataspaces: [
    {
      name: "Catena-X",
      url: "https://catena-x.net/",
      gradient: 'linear-gradient(135deg, #ffa600, #b3cb2d)',
      logo: {
        src: 'https://catena-x.net/wp-content/uploads/2025/10/CX_Figurative_mark_RGB_pos.png',
        alt: 'Catena-X Logo',
        width: 70,
        height: 70
      },
      colors: {
        layer1: 'rgb(110, 200, 105)',
        layer2: 'rgb(179, 203, 45)',
        layer3: 'rgb(230, 163, 38)',
        layer4: 'rgb(250, 160, 35)'
      },
      subtitle: 'Your Automotive Network',
      description: 'The first open and collaborative data ecosystem for the automotive industry...',
      kits: ['connector', 'data-governance', 'business-partner', /* ... */]
    }
  ]
}

Dataspace Data Model

To add an dataspace it must be added as an item in the dataspaces key at the indudstry master data.

Field Descriptions

Field	Type	Required	Description
name	string	Yes	Display name of the dataspace
url	string	Yes	Official website URL of the dataspace
gradient	string	Yes	CSS gradient definition for the dataspace's visual identity
logo.src	string	Yes	URL to the dataspace logo image
logo.alt	string	Yes	Alt text for the logo image (accessibility)
logo.width	number	Yes	Logo width in pixels
logo.height	number	Yes	Logo height in pixels
colors.layer1	string	Yes	First layer color for hover effects (hex or rgb)
colors.layer2	string	Yes	Second layer color for hover effects (hex or rgb)
colors.layer3	string	Yes	Third layer color for hover effects (hex or rgb)
colors.layer4	string	Yes	Fourth layer color for hover effects (hex or rgb)
subtitle	string	Yes	Short tagline for the dataspace
description	string	Yes	Comprehensive description of the dataspace's purpose and capabilities
kits	array	Yes	Array of KIT IDs that are available in this dataspace

Structure

{
  name: 'Dataspace Name',
  url: 'https://dataspace-website.com',
  gradient: 'linear-gradient(135deg, #color1, #color2)',
  logo: {
    src: 'https://example.com/logo.svg',
    alt: 'Logo Alt Text',
    width: 80,
    height: 80
  },
  colors: {
    layer1: '#color1',
    layer2: '#color2',
    layer3: '#color3',
    layer4: '#color4'
  },
  subtitle: 'Dataspace Tagline',
  description: 'Comprehensive description of the dataspace...',
  kits: ['kit-id-1', 'kit-id-2', 'kit-id-3']
}

Example: Catena-X Dataspace

{
  name: "Catena-X",
  url: "https://catena-x.net/",
  gradient: 'linear-gradient(135deg, #ffa600, #b3cb2d)',
  logo: {
    src: 'https://catena-x.net/wp-content/uploads/2025/10/CX_Figurative_mark_RGB_pos.png',
    alt: 'Catena-X Logo',
    width: 70,
    height: 70
  },
  colors: {
    layer1: 'rgb(110, 200, 105)',
    layer2: 'rgb(179, 203, 45)',
    layer3: 'rgb(230, 163, 38)',
    layer4: 'rgb(250, 160, 35)'
  },
  subtitle: 'Your Automotive Network',
  description: 'The first open and collaborative data ecosystem for the automotive industry...',
  kits: ['connector', 'data-governance', 'business-partner', ...]
}

Example: Semiconductor-X Dataspace

{
  name: "Semiconductor-X",
  url: "https://semiconductor-x.com/",
  gradient: 'linear-gradient(135deg, #c1cb01, #e67900)',
  logo: {
    src: 'https://www.semiconductor-x.com/wp-content/uploads/semicon-x_bildmarke.svg',
    alt: 'Semiconductor-X Logo',
    width: 100,
    height: 80
  },
  colors: {
    layer1: '#c1cb01',
    layer2: '#d4b501',
    layer3: '#e69f00',
    layer4: '#e67900'
  },
  subtitle: 'Semiconductor Network',
  description: 'Contributing to a cross-sector international dataspace...',
  kits: ['connector', 'digital-twin', 'industry-core', 'traceability', 'pcf', 'dcm']
}

Ecosystem Hierarchy

The master data follows this organizational hierarchy:

Dataspace Foundation
└── Industry Core KITs
  └── Cross-Dataspace Use Cases
  └── Industry-Specific KITs
    ├── Automotive Industry
    │   └── Dataspaces
    │       └── Catena-X
    ├── Shop Floor Industry
    │   └── Dataspaces
    │       └── <Future Implementations>
    └── ... (other industries)

The complete architecture of the KITs is documented at the KIT Framework page.

KIT Data Model

Field Descriptions

Field	Type	Required	Description
id	string	Yes	Unique identifier for the KIT (lowercase, hyphenated)
name	string	Yes	Display name of the KIT (UPPERCASE)
logo	Component	Yes	React SVG component for the KIT logo
logoHeight	number	Yes	Height of the logo in pixels
logoWidth	number	Yes	Width of the logo in pixels
route	string	Yes	Path to the KIT's adoption view documentation
colors.primary	string	Yes	Primary brand color in hex format
colors.gradient	string	Yes	CSS gradient definition for visual effects
maturity.currentLevel	string	Yes	Current maturity level: Sandbox, Incubating, or Graduated
maturity.graduationStatus	string	Conditional	Required for Incubating KITs: draft, in progress, or in review
maturity.graduatedAt	string	Conditional	Date when KIT graduated (YYYY-MM-DD format). Required for Graduated KITs
maturity.deprecatedAt	string	Conditional	Date when KIT was deprecated (YYYY-MM-DD format). Required if deprecated
deprecated	boolean	Yes	Indicates if the KIT is deprecated (true or false)
domain	string	Yes	Domain category (e.g., 'Sustainability', 'Engineering', 'Supply Chain', 'Enablement Service')
industries	array	No	Array of industry IDs where the KIT applies. Optional for foundation KITs
description	string	Yes	Short description of the KIT's purpose and functionality
metadata.created	string	Yes	Creation date of the KIT (YYYY-MM-DD format)
metadata.lastUpdated	string	Yes	Date of the last update (YYYY-MM-DD format)
metadata.latestVersion	string	Yes	Current version using semantic versioning (e.g., '3.0.0')
metadata.new	boolean	Yes	Indicates if the KIT is newly added (true or false)

Structure

Each KIT in the master data follows this structure:

{
  id: '<unique-kit-id>',                    // Unique identifier for the KIT
  name: '<KIT NAME IN UPPERCASE>',          // Display name
  logo: <KitLogoComponent>,                 // React SVG component
  logoHeight: <number>,                     // Logo height in pixels
  logoWidth: <number>,                      // Logo width in pixels
  route: '<route-to-kit-adoption-view>',    // Path to KIT documentation
  colors: {
    primary: '<hex-color>',                 // Primary brand color
    gradient: 'linear-gradient(...)'        // CSS gradient definition
  },
  maturity: {
    currentLevel: '<level>',                // 'Sandbox' | 'Incubating' | 'Graduated'
    graduationStatus: '<status>',           // 'draft' | 'in progress' | 'in review' (for Incubating only)
    graduatedAt: '<YYYY-MM-DD>',           // Date when graduated (only if Graduated)
    deprecatedAt: '<YYYY-MM-DD>'           // Date when deprecated (only if deprecated)
  },
  deprecated: <boolean>,                    // true | false
  domain: '<domain-category>',              // e.g., 'Sustainability', 'Engineering', 'Supply Chain'
  industries: ['<industry-id>', ...],       // Array of industry IDs (optional for foundation KITs)
  description: '<kit-description>',         // Short description of the KIT
  metadata: {
    created: '<YYYY-MM-DD>',               // Creation date
    lastUpdated: '<YYYY-MM-DD>',           // Last update date
    latestVersion: '<version>',            // Current version (semantic versioning)
    new: <boolean>                         // true if recently added
  }
}

Real Example: Connector KIT

Here's the actual master data for the Connector KIT:

{
  id: 'connector',
  name: 'CONNECTOR KIT',
  logo: ConnectorKitLogo,
  logoHeight: 80,
  logoWidth: 80,
  route: '/docs-kits/kits/connector-kit/adoption-view',
  colors: {
    primary: '#2316E3',
    gradient: 'linear-gradient(135deg, #3372CC 0%, #2316E3 100%)'
  },
  maturity: {
    currentLevel: 'Graduated',
    graduatedAt: '2024-06-07'
  },
  deprecated: false,
  domain: "Enablement Service",
  description: 'The EDC as a connector implements a framework agreement for sovereign, cross-organizational data exchange.',
  metadata: {
    created: '2022-08-01',
    lastUpdated: '2024-06-07',
    latestVersion: '3.0.0',
    new: false
  }
}

Example: Incubating KIT with Graduation Status

{
  id: 'data-trust-security',
  name: 'DATA TRUST & SECURITY KIT',
  logo: DataTrustSecurityLogo,
  logoHeight: 120,
  logoWidth: 120,
  route: '/docs-kits/kits/data-trust-and-security-kit/adoption-view',
  colors: {
    primary: '#2A1FB3',
    gradient: 'linear-gradient(135deg, #3372CC 0%, #2A1FB3 100%)'
  },
  maturity: {
    currentLevel: 'Incubating',
    graduationStatus: 'in progress'
  },
  deprecated: false,
  domain: "Security",
  description: 'Enable content validation, certification and verification for any use case semantic data.',
  metadata: {
    created: '2025-09-30',
    lastUpdated: '2025-09-30',
    latestVersion: '0.0.1',
    new: true
  }
}

Example: Deprecated KIT

{
  id: 'data-governance',
  name: 'DATA GOVERNANCE KIT',
  logo: DataGovernanceLogo,
  logoHeight: 90,
  logoWidth: 90,
  route: '/docs-kits/kits/data-governance-kit/adoption-view',
  colors: {
    primary: '#1E13C2',
    gradient: 'linear-gradient(135deg, #3372CC 0%, #1E13C2 100%)'
  },
  maturity: {
    currentLevel: 'Sandbox',
    graduationStatus: 'draft',
    deprecatedAt: '2025-11-13'
  },
  deprecated: true,
  domain: "Governance",
  description: 'Enable and simplify data governance.',
  metadata: {
    created: '2024-03-08',
    lastUpdated: '2024-03-08',
    latestVersion: '0.1.0',
    new: false
  }
}

Industry-Specific KITs

Industry-specific KITs are KITs that are tailored to meet the unique requirements and use cases of particular industries. Unlike foundation KITs that provide generic capabilities across all dataspaces, industry-specific KITs address specialized needs within a vertical market. They are not displayed in the cross-industry KITs section, but only in the industry specific view.

Organizing Industry-Specific KITs

Industry-specific KITs are organized in the master data under the industryKits object, grouped by industry (using the industry ids from the industry master data as keys):

industryKits: {
  "automotive": [
    // Automotive-specific KITs
  ],
  "shop-floor": [
    // Shopfloor-specific KITs
  ],
  // ... other industries
}

Adding an Industry-Specific KIT

Here is an example on how to add a industry specific KIT:

Example: Industry-Specific KIT Structure

// In kitsData.js
export const kitsData = {
  // ... other sections
  
  industryKits: {
    "automotive": [
      {
        id: 'industry-specific-kit',
        name: 'INDUSTRY SPECIFIC KIT',
        logo: IndustryKitLogo,
        logoHeight: 80,
        logoWidth: 80,
        route: '/docs-kits/kits/industry-specific-kit/adoption-view',
        colors: {
          primary: '#FF5733',
          gradient: 'linear-gradient(135deg, #FF5733 0%, #C70039 100%)'
        },
        maturity: {
          currentLevel: 'Incubating',
          graduationStatus: 'in progress'
        },
        deprecated: false,
        domain: 'Engineering',
        description: 'Specialized KIT for automotive industry processes...',
        metadata: {
          created: '2025-01-15',
          lastUpdated: '2025-01-15',
          latestVersion: '1.0.0',
          new: true
        }
      }
    ],
    "shop-floor": [
      // Shopfloor-specific KITs
    ]
  }
}

Relationship to Industries and Dataspaces

Industry-specific KITs create a hierarchical relationship:

Industry (e.g., Automotive)
  └── Dataspace (e.g., Catena-X)
      └── Industry-Specific KITs (e.g., Requirements KIT, MaaS KIT)

Each industry can have multiple dataspaces, and each dataspace can implement multiple industry-specific KITs that are relevant to their use cases.

Master Data

25

Total KITs

10

Graduated

7

Incubation

8

Sandbox

2

New KITs

4

Industries

Industries (5)

Automotive

INDUSTRY

Automotive Industry

Industry Specific KITs for the automotive industry, covering the entire value chain from suppliers to OEMs to aftermarket. Enable digital collaboration, supply chain transparency, quality management, and sustainable practices across automotive manufacturing and distribution.

Dataspaces in this Industry1

Catena-X

Your Automotive Network

The first open and collaborative data ecosystem for the automotive industry. Catena-X enables secure and standardized data exchange across the entire automotive value chain to drive innovation, sustainability, and transparency.

Visit Website

Shop Floor

INDUSTRY

Shop Floor Industry Use Cases

Industry Specific KITs for manufacturing and production environments, focusing on shop floor operations, industrial equipment integration, and production optimization. Enable smart manufacturing, flexible production networks, and real-time operational data exchange.

Semiconductor

INDUSTRY

Semiconductor Industry Use Cases

Industry Specific KITs for the semiconductor industry, addressing complex supply chains, manufacturing processes, and quality requirements. Enable traceability, capacity management, and digital collaboration across the global semiconductor value network.

Dataspaces in this Industry1

Semiconductor-X

Semiconductor Network

Contributing to a cross-sector international dataspace and digital twin standards for resilient semiconductor supply chains.

Visit Website

Construction

INDUSTRY

Construction Industry Use Cases

Industry Specific KITs in the construction and building industry, supporting project lifecycle management, material traceability, and sustainable building practices. Enable digital collaboration between architects, contractors, suppliers, and facility managers.

Dataspaces in this Industry1

Construct-X

Construction Network

An innovative dataspace revolutionizing the construction industry through digital collaboration and sustainable building practices. Construct-X connects architects, builders, and suppliers in a unified digital ecosystem.

Visit Website

Chemical

INDUSTRY

Chemical Industry Use Cases

Industry Specific KITs for the chemical industry, addressing product safety, regulatory compliance, and supply chain complexity. Enable secure data exchange, material traceability, sustainability reporting, and cross-industry standardization for chemical manufacturing and distribution.

Dataspace Foundation KITs (4)

CONNECTOR KIT

Graduated

The EDC as a connector implements a framework agreement for sovereign, cross-organizational data exchange.

Last Updated: 2024-06-07 | Version: 3.0.0| Graduated: 2024-06-07

DATA GOVERNANCE KIT

SandboxDeprecated

Enable and simplify data governance.

Last Updated: 2024-03-08 | Version: 0.1.0

DATA TRUST & SECURITY KIT

IncubatingNew

Enable content validation, certification and verification for any use case semantic data.

Last Updated: 2025-09-30 | Version: 0.0.1

BUSINESS PARTNER KIT

Graduated

Get high-quality data business partner data records including the unique identifier.

Last Updated: 2025-09-08 | Version: 10.0.0| Graduated: 2025-09-08

Industry Core Foundation KITs (6)

DIGITAL TWIN KIT

Graduated

Digital Twins enable data-level interoperability - even between parties previously unknown to each other.

Last Updated: 2024-08-01 | Version: 2.0.1| Graduated: 2024-08-01

INDUSTRY CORE KIT

Graduated

Connceting Use-Cases with Core Services

Last Updated: 2025-03-17 | Version: 1.4.0| Graduated: 2025-03-17

DATA CHAIN KIT

Graduated

Data Chain KIT is made for apps and services to access connected data distributed between organizations.

Last Updated: 2024-05-28 | Version: 3.0.1| Graduated: 2024-03-07

TRACEABILITY KIT

Graduated

Trace parts and materials across the entire value chain to enable data driven use cases over all n-tier levels.

Last Updated: 2025-08-07 | Version: 7.0.0| Graduated: 2024-12-01

SUPPLY CHAIN DISRUPTION NOTIFICATION KIT

Graduated

Inform partners about disruptions in the supply chain.

Last Updated: 2025-08-22 | Version: 2.0.0| Graduated: 2025-08-22

KNOWLEDGE AGENTS KIT

Incubating

Generate Knowledge from Data. Scalable & Efficient Semantic Dataspace Federation.

Last Updated: 2024-12-09 | Version: 1.3.0

Cross Dataspace Use Cases KITs (13)

ESS KIT

Sandbox

Environmental and Social Standards Incident Management in supply chains.

Last Updated: 2024-07-11 | Version: 0.3.0

PRODUCT CARBON FOOTPRINT KIT

Graduated

Product-specific CO2 footprint.

Last Updated: 2025-09-29 | Version: 1.3.0| Graduated: 2024-08-05

ECO PASS KIT

Incubating

Leverage the transparency of digital product passports to strengthen sustainability & compliance.

Last Updated: 2024-07-25 | Version: 1.5.0

CIRCULARITY KIT

Incubating

Enable circular economy business models with data exchange across company boundaries.

Last Updated: 2024-09-17 | Version: 1.3.0

DEMAND & CAPACITY MANAGEMENT KIT

Graduated

Quick build of solutions for companies of any size to engage a collaborative capacity management.

Last Updated: 2025-09-29 | Version: 1.4.0| Graduated: 2025-09-29

LOGISTICS KIT

Sandbox

Provide packing information, transport data and customs topics.

Last Updated: 2025-02-12 | Version: 1.0.0

CUSTOMS KIT

Sandbox

Basis for a more efficient customs process and ensure a robust preference calculation result.

Last Updated: 2025-05-16 | Version: 0.0.0

ONLINE SIMULATION KIT

Sandbox

Gain increased supply chain transparency through collaborative simulation across all stakeholders.

Last Updated: 2025-03-06 | Version: 3.1.0

PURIS KIT

Graduated

Predictive Unit Realtime Information Service

Last Updated: 2025-08-16 | Version: 0.4.0| Graduated: 2025-08-16

MODEL BASED PRODUCTION KIT

Sandbox

Federated simulation and data processing.

Last Updated: 2024-05-27 | Version: 1.0.0

BEHAVIOUR TWIN KIT

Incubating

Maximize the potential of usage data through calculation services and simulations.

Last Updated: 2024-05-21 | Version: 1.0.0

DATA DRIVEN QUALITY KIT

Incubating

Data driven quality management enables data provider and consumer to exchange and analyse existing data across company boundaries.

Last Updated: 2025-04-23 | Version: 2.0.0

REQUIREMENTS KIT

SandboxNew

Cross company requirements management to enable quick information access and multiple company collaboration.

Last Updated: 2025-09-29 | Version: 0.1.0

Industry Specifics

Shop-floor Specific KITs (2)

MANUFACTURING AS A SERVICE KIT

Sandbox

Create a federated network of networks to connect manufacturing supply and demand.

Last Updated: 2024-05-27 | Version: 1.0.0

MODULAR PRODUCTION KIT

Incubating

Enable customized production (batch size 1) without significant increase of costs.

Last Updated: 2024-05-10 | Version: 1.0.0

Additional Resources

KIT Documentation

• KIT Framework - Complete guide to KIT structure, artifacts, and requirements
• KIT Lifecycle - KIT maturity levels, graduation, and maintenance processes
• KIT Getting Started - How to create a KIT
• KIT Statistics - Analytics dashboard for KIT ecosystem metrics

Documentation References

KIT-Specific TRGs (Tractus-X Release Guidelines)

• TRG 10.01 - KIT Architecture - KIT framework categories and classification
• TRG 10.02 - KIT Content Structure - Required content and structure
• TRG 10.03 - KIT Lifecycle - Maturity levels and lifecycle management
• TRG 10.04 - KIT Graduation Process - Graduation requirements and process
• TRG 10.05 - KIT Deprecation Process - Deprecation criteria and procedures

Legal & Licensing

• TRG 7.07 - Legal notice for non-code - Image and media licensing requirements
• TRG 7.08 - Legal notice for KIT documentation (CC-BY-4.0) - Documentation licensing