KIT Getting started
| Status | Created | Post-History |
|---|---|---|
| Draft | 04-Apr-2024 | Initial contribution |
| Active | 07-Nov-2025 | Extended Contribution to KITs 2.0 |
Welcome to the Eclipse Tractus-X KITs Getting Started Guide! This guide is designed to help you understand what KITs are, how to get started with them, and how to create your own KITs for the Eclipse Tractus-X ecosystem.
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, support the compliance with industrial standards from standarization organizations (Catena-X e.V., IDTA, ISO/DIN, EDWG, Manufacturing-X, etc.) and in some use cases enable also regulatory compliance.
First Steps
Take your first steps on creating your KIT by following this guide. Here you will find detailed step by step explanations from ZERO TO KIT. More information can be found in other pages:
Prerequisites
You need to have a Github Account and to fulfill the requirements from the Developer Hub Getting Started Guide.
Contact & Support
Get informed about what are the KITs and how to contribute by reaching out to the KITs Program Manager or attending our KIT community office hours:
Community Channels
| Channel | Purpose | Link |
|---|---|---|
| KIT Community Office Hours | Weekly alignment meetings | Join Meeting |
| KIT Office Hour Kanban | Development items tracking | Github Project |
| Matrix Chat | Daily discussions & support | #tractusx-kits:matrix.eclipse.org |
| GitHub Issues | Technical issues & bugs | Create Issue |
| SIG-Release | Official KIT Release Tracking | eclipse-tractusx/sig-release |
| KIT Discussions | Offical KIT Proposal and Discussion Location | KIT Discussions |
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.
How to Create a KIT
Quick Overview
Detailed Step by Step Process (click to expand)
Step 1: Create/Discuss Idea
Talk to the community about your KIT concept.
- KIT Community Office Hours: Tuesdays at 10:00 AM CET - Join here
- Matrix Chat: #tractusx-kits:matrix.eclipse.org
What to bring: Brief description of your use case and target audience.
Step 2: Create SIG-Release Ticket
Create an official tracking ticket.
- Go to eclipse-tractusx/sig-release
- Create new issue using "Propose KIT" template
- Fill in your KIT description and team members
Step 3: Build Your KIT
Create your KIT following the standard structure.
Follow this structure:
| Views | Stakeholders | Content |
|---|---|---|
| Adoption View | Business | Business Value, Motivation, Vision, Mission, Whitepapers, Semantic Models, Standards, Tutorials, Explanations why this use case is important, Context |
| Development View | DevelopersArchitects | Overall Architecture, Reference Implementations, API specifications, Policies, Algorithms, Functional Requirements, Sequence Diagrams, Process, Architecture Guidelines |
| Operator View | OperatorsService Providers | Non-Functional Requirements, Security Requirements, Recommendations, Restrictions |
| Documentation | Any Stakeholder | Extra Documentation and Links |
| Success Stories | OperatorsService ProvidersBusiness | Success Stories from Reference Implementations that used this KIT. Open Source and COTS. |
| Industry Extensions | Dataspace Adopters | One Folder per Industry. Extends the contents from the other views with regards to a specific industry and affiliated dataspace standards/requirements |
In addition to the view-specific content above, every KIT must include:
- Copyright Notice - Mandatory CC-BY-4.0 licensing information and contributor copyright statements at every file
- Changelog - Version history file following semantic versioning
The views above are organized in "folders" so that its sections are harmonized and the content from each view remains flexible.
Step 4: Submit for Review
Submit your completed KIT for community review.
- Fork eclipse-tractusx.github.io
- Add your KIT to the master data
- Add your KIT in this file by updating the sidebar configuration in '/sidebarsDocsKits.js' at the root folder (a template will be provided).
- Update the docusaurus.config.js file to include your new KIT at the navbar, search for
navbar: { items: [{type: 'dropdown', label: 'KITs', position: 'left', to: '/Kits', items: [...] } - Update the changelog with what was added
- Create a pull request to
eclipse-tractusx.github.iomainbranch - Request the committer assigned in the SIG-Release ticket to review, approve and merge your PR
Timeline: Typically 2-3 weeks from submission to approval.
Step 5: Release your KIT (Committers)
- The committer MUST create a release check issue at sig-release based on the KIT Release template
- The committer MUST ensure all TRGs metadata is checked in the release check issue.
- Changelog is included in the Project Release Notes of the target release
- KIT will be listed as part of the release notes on the Eclipse Tractus-X Website
Congratulations! Your KIT is now part of the Eclipse Tractus-X ecosystem!
Additional Resources
KIT Documentation
- KIT Framework - Complete guide to KIT structure, artifacts, and requirements
- KIT Lifecycle - KIT maturity levels, graduation, and maintenance processes
- KIT Master Data Overview - Complete KIT metadata, statistics, and data structure
- 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
