industry-core-hub

Industry Core Hub Architecture

Metadata

Version	Created at	Last Reviewed at
v0.1	Jan, 14th 2025	Jan, 14th 2025

Authors & Reviewers

Name	Company	GitHub	Role
Mathias Brunkow Moser	Catena-X e.V.	@matbmoser	Chief Software Architect & Eclipse Tractus-X Project Lead

Index

• Metadata
  • Authors \& Reviewers
• Index
• ICH Services
• Requirements
  • Functional Requirements, Prio 1
    • Data Provisioning
    • Data Consumption
    • EDC and DTR
  • Functional requirements, Prio 2
  • Non functional requirements
• Context
  • Scope
  • Name
  • Objectives
• High Level Architecture
  • Abstraction Phases
• MVP Definition
• Architecture View
  • Logical View
  • Process View
  • Development View
  • Interfaces
  • NOTICE

ICH Services

• Provide Digital Twin Registry as EDC Asset
• Consume Digital Twin Registry as EDC Asset
• Digital Twin Provisioning (CRUD)
• Digital Twin Consumption
• Submodel Provisioning (CRUD)
• Submodel Consumption
• EDC Asset Provisioning (CRUD)
• EDC Asset Consumption
• EDC Policy Offering
• EDC Policy Acceptance
• Notification Send
• Notification Receive

Requirements

Functional Requirements, Prio 1

Based on the services described above the following capabilities should be provided for data providers and data consumers in the dataspace.

Data Provisioning

• Provide a user interface for excel upload and manual data input. This can be generic (json) in the beginning
• Create a Digital Twin for a given PartType / PartInstance.
• Read, Update, Delete that Digital Twin

• Display the Digital Twin

• Attach a simple submodel to that Digital Twin. This must be generic. Any submodel can be added.
• Create an EDC asset for that (generic) submodel with policies of choice
• Create a backend service to provide the data for that submodel
• Read, Update, Delete the submodel, EDC asset and backend data

• Display the submodel, EDC asset and backend data (generic, Json is sufficient)

• Attach a BOM submodel by retrieving the supplier’s Digital Twin(s) with EDC asset, policies, backend service and CRUD capabilities
• Display the BOM submodel

Data Consumption

• Search, retrieve and display a Digital Twin from a Business Partner with all associated submodels and their data in a generic way.

EDC and DTR

An EDC and DTR service should be part of the application, but it should also be possible to use one’s own EDC / DTR

Functional requirements, Prio 2

• Send and receive notifications with standardized header and generic notification content
• Attach a Usage submodel upon receiving the corresponding notification with EDC asset, policies, backend service and CRUD capabilities
• Read, Update, Delete the Usage submodel

Non functional requirements

• The UI should be simple and hide away the complexity of the data exchange
• It should be really fast and simple to use
• It should be scalable for multiple applications scenarios
• It should be keepen generic for any data retrival

Context

Scope

Name

Industry Core Hub - A plug and play application that allows you to manage your data and infrastructure. Provide and consume data according to the industry core standards, and build your open source and business use cases as fast as possible, with a powerful motor.

Objectives

• 1000 Users using Catena-X
• Quicker & Easier adoption of the dataspace for use cases

High Level Architecture

Following the structure that will be defined for the KITs a layered Architecture was selected:

Abstraction Phases

MVP Definition

Architecture View

Logical View

Process View

Development View

Interfaces

NOTICE

This work is licensed under the CC-BY-4.0.

• SPDX-License-Identifier: CC-BY-4.0
• SPDX-FileCopyrightText: 2025 Contributors to the Eclipse Foundation
• Source URL: https://github.com/eclipse-tractusx/industry-core-hub

This site is open source. Improve this page.