One post tagged with "kit"

Hello Tractus-X community,

We are excited to announce the launch of KIT 2.0 Architecture - a major redesign of how we visualize and organize our KIT ecosystem. This update brings a fresh perspective to understanding the layered architecture of Eclipse Tractus-X, making it easier than ever to explore and navigate our comprehensive collection of KITs.

What is a KIT?​

KIT, short for Keep It Together, is an open-source toolbox with comprehensive documentation that enables multiple stakeholders (Business, Solution Providers, Developers) to build interoperable applications compatible with the Eclipse Tractus-X dataspace technologies, and support the compliance with industrial standards from standarization organizations (Catena-X e.V., IDTA, ISO/DIN, EDWG, Manufacturing-X, etc.) and in some cases enable regulatory compliance.

A KIT provides everything needed to implement and deploy specific business scenarios within a dataspace environment - from architectural guidance and API specifications to reference implementations and operational procedures. Each KIT serves as a complete, self-contained package that enables developers, operators, and business stakeholders to understand, build, and run solutions that are interoperable across the dataspace network.

What's New in KIT 2.0 Architecture?​

The KIT framework has evolved significantly from version 1.0 to 2.0 to support the growing needs of multiple dataspaces and industries. This transition represents a fundamental shift in how we approach dataspace interoperability - moving from a single-industry focus to enabling multiple industries to leverage the same foundational technologies while maintaining the flexibility to address industry-specific requirements through modular extensions.

Interactive Hexagonal Design​

The new architecture features a beautiful hexagonal layout that visually represents the four main layers of our KIT ecosystem:

Modular Reusable Architecture​

Here is a detailed explana of the diagram above, and how this architecture improves reusability:

Standardized KIT Development Process​

With KIT 2.0, we've established a comprehensive framework and clear guidelines for creating and maintaining KITs. Our Tractus-X Release Guidelines (TRGs) provide a structured approach to KIT development, ensuring consistency, quality, and interoperability across all KITs.

TRG 10 - Keep it Together (KIT)​

The TRG 10 series defines the complete lifecycle and requirements for KIT development:

Active TRGs (Necessary for the new Webpage Structure)​

• TRG 10.01 - KIT Architecture: Defines the architectural categories and layered classification of KITs within the Eclipse Tractus-X ecosystem
• TRG 10.02 - KIT Structure: Specifies the required folder structure, documentation organization, and content requirements for each KIT
• TRG 10.03 - KIT Lifecycle: Outlines the maturity levels (Incubating, Stable, Deprecated) and the progression criteria for KITs

Draft TRGs (Coming Soon)​

• TRG 10.04 - KIT Graduation Process (Draft): Details the process for KITs to move from incubating to graduated status
• TRG 10.05 - KIT Deprecation Process (Draft): Describes the deprecation process for KITs that are no longer maintained or relevant

KIT Master Data - Single Source of Truth​

All KIT metadata is centralized in a single source of truth - the KIT Master Data Overview. This comprehensive registry contains:

• Metadata: Version numbers, last updated dates, maturity levels, and graduation dates
• Architecture Classification: Which layer each KIT belongs to (Dataspace Foundation, Industry Core, etc.)
• Dataspace Assignments: Which dataspaces each KIT supports (Catena-X, Manufacturing-X, etc.)
• Links & Resources: Routes to documentation, repositories, and related materials
• Lifecycle Status: Current state (Incubating, Graduated, Deprecated) and progression history

File Location is at the /data folder:

/data/kitsData.js

In this way, the development, creation and usage of KITs is streamlined, transparent and easier to maintain.

KIT Datamodel​

There is a metadata datamodel for every KIT defined as follows:

{
  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
  }
}

Additionally, there is a Datamodel for Industries and for Dataspaces defined in a similar manner, more information can be found clicking on the button below!

KIT Statistics - Insights into the KIT Ecosystem​

Thanks to the master data, now we can also provide detailed KIT Statistics that give insights into the current state of the KIT ecosystem:

Key Statistics Preview​

Architecture Distribution & Growth Trends​

Thanks to this we can now monitor the growth and evolution of the KIT ecosystem over time, providing valuable insights into adoption trends and areas of focus. And knowing how is the state of life from the KITs evolving during each release.

KIT 2.0 Content Structure and Artifacts​

Now it is defined a clear structure for the content and the views

And depending from what is available a KIT will position itself in one or another lifecycle level:

KIT Lifecycle​

Understanding the KIT lifecycle is crucial for contributors and users alike. Each KIT in the Tractus-X ecosystem follows a structured maturity progression that ensures quality, completeness, and real-world validation before reaching production readiness.

The Three Maturity Levels​

KITs progress through three distinct lifecycle stages, each with specific requirements and validation criteria:

Lifecycle Management​

All lifecycle transitions are tracked in the KIT Master Data and validated according to the TRG 10.03 - KIT Lifecycle guidelines. This ensures transparency and consistency across the entire KIT ecosystem.

Artifact Requirements by Maturity Level​

Each maturity level has specific artifact requirements that must be fulfilled for a KIT to progress. The table below shows the comprehensive list of required artifacts for each lifecycle stage:

KIT Template​

Follow the KIT template to have an example of folder structure that can be followed following the KIT Framework Guide and the needed content for each view in order to achieve all requirements from the KIT Lifecycle.

KIT Office Hours - Get Expert Support​

Need help developing your KIT or have questions about the KIT framework? Join our KIT Office Hours - a dedicated time for the community to get direct support from the KIT development team.

What are KIT Office Hours?​

KIT Office Hours are regular community sessions where you can:

• Get guidance on KIT development and lifecycle progression
• Ask questions about TRG compliance and best practices
• Discuss your KIT architecture and implementation approach
• Receive feedback on your KIT graduation readiness
• Connect with other KIT developers and maintainers

How to Participate​

Office hours are held regularly and open to all community members. Whether you're just starting with KIT development or preparing for graduation review, the team is here to help.

Learn More​

Want to dive deeper into the KIT framework? Explore our comprehensive documentation to understand the complete structure, artifacts, and requirements for building your own KITs.

All KITs are licensed under the non-code CC-BY-4.0 License.

All industry logos and trademarks are property of their respective organizations.