Use DataEngine

Who should use DataEngine?

DataEngine can be used by:

• UI applications such as AAS Viewers that need fully populated shells or submodels

• API consumers that want to retrieve AAS-compliant structures programmatically

• Platform integrators building AAS (Asset Administration Shell) solutions based on IDTA standards

Consumers do not need to understand template internals or plugin storage details to use DataEngine.

Setup overview

DataEngine is typically deployed as a containerized service and accessed via an API gateway.

High-level setup steps

1. Deploy DataEngine

2. Configure access to registries and template repositories

3. Configure one or more Plugin services

4. Expose DataEngine endpoints via an API gateway

Running DataEngine locally

The DataEngine repository provides an example folder that allows you to run DataEngine locally using container-based setups.

Steps

1. Clone the repository:

git clone https://github.com/AAS-TwinEngine/AAS.TwinEngine.DataEngine.git

2. Navigate to the repository example folder:

cd AAS.TwinEngine.DataEngine/example

3. Start the services using Docker Compose:

docker compose up -d

Included services

The Docker Compose setup includes:

• DataEngine

• Template registries (BaSyx AAS Registry and Submodel Registry)

• Template repositories (BaSyx AAS Environment used as a template repository)

• One Plugin service: DPP Plugin

For advanced configuration options and additional details, refer to the documentation inside the repository’s example folder