IC | IC-Hub Draft Requirements Collection

[eckardg]

The features are permanently refined. Please find here a first draft for a better understanding.

Requirements for Industry Core Reference Implementation IC-X:

The following services and capabilities will be provided by the reference implementation.

IC-X 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

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