AAS Twin Engine
The AAS Twin Engine by M&M Software generates the Asset Administration Shells (AAS) for the Digital Product Passport from the data that was fed into it.
AAS-Suite
The AAS-Suite by Meta-Level Software AG provides the frontend, including a template editor and a viewer to display the AAS.
Eclipse BaSyx
Eclipse BaSyx forms the technical foundation as the AAS server and provides the IDTA-compliant API for accessing the Asset Administration Shells.
GitHub: eclipse-basyx
GitHub: basyx-go-components
BaSyx wiki
How does this all fit together?
In the AAS-Suite you create and edit templates. The corresponding data is fed into the AAS Twin Engine's database. When accessed via the IDTA-compliant API, the Twin Engine generates the matching Asset Administration Shells from it, which are served by BaSyx as the AAS server. These AAS are then displayed in the AAS-Suite viewer.
Impressions
