Bachelor thesis: How Data Space Connectors can be used to exchange Asset Administration Shells in industrial Data Spaces

Original title: Untersuchung von Data Space Connectoren für den Austausch von Verwaltungsschalen in industriellen Datenräumen

Author: Milo Franke

Mnestix Browser Data Space Fork

In the practical part of the thesis, Mnestix was extended to support requesting Asset Administration Shells (AAS) from a Data Space. The relevant code can be found in the following files:

• src/lib/api/dataspace-api/dataspace-api.ts - Die serverseitige Komponente für sämtliche Requests innerhalb des Data Space.
• src/app/[locale]/dataspace/page.tsx - The subpage for the Data Space Browser in Mnestix.
• src/app/[locale]/dataspace/_components/CatalogList.tsx - The server-side React Component for fetching and displaying catalogs.
• src/app/[locale]/dataspace/_components/DatasetItem.tsx - The server-side React Component for displaying datasets.
• src/app/[locale]/dataspace/_components/AssetItem.tsx - The server-side React Component for displaying an asset.
• src/app/[locale]/dataspace/_components/NegotiationButton.tsx - The client-side React Component for initiating a contract negotiation.

For development, the Minimum Viable Dataspace was used for development and has to be set up in order to make the prototype work. For Mnestix to be able to communicate to the MVD, the following environment variables have to be set:

Environment variable	Description
CATALOG_QUERY_URL	Address that will be used to access the own federated catalog.
CONNECTOR_CONTROL_PLANE_URL	Address that will be used to communicate with the own data space connector.
CONNECTOR_API_KEY	The API Key of the own connector.

The values are adjusted to the MVD by default.