Design and Implementation of the Reactive Asset Administration Shell using JSON-based Database

Abstract

In 2021, the document Details of the Asset Administration Shell - Part 2 was released, which forms the standard for the REST API interface of the AAS technology. The standard contains a prescription of functions and their parameters for working with AAS of the passive part in a standardized way. Design and implementation of the passive part, or the use of OPC UA is still the subject of discussions and solutions to partial problems. In this article, we designed and implemented AAS using an internal database as a model provider and a basic set of REST API functions according to the standard. The implementation took place in the Python environment, building on the open source Python BasyxSDK. The mentioned proposal enables work with standard AAS data types, or the format using JSON technology was used, which is also mentioned as one of the possible ways of securing the passive part in the form of a file. The result is a standalone version of AAS that can be deployed on individual devices in isolation in accordance with the principles of Industry 4.0.In 2021, the document Details of the Asset Administration Shell - Part 2 was released, which forms the standard for the REST API interface of the AAS technology. The standard contains a prescription of functions and their parameters for working with AAS of the passive part in a standardized way. Design and implementation of the passive part, or the use of OPC UA is still the subject of discussions and solutions to partial problems. In this article, we designed and implemented AAS using an internal database as a model provider and a basic set of REST API functions according to the standard. The implementation took place in the Python environment, building on the open source Python BasyxSDK. The mentioned proposal enables work with standard AAS data types, or the format using JSON technology was used, which is also mentioned as one of the possible ways of securing the passive part in the form of a file. The result is a standalone version of AAS that can be deployed on individual devices in isolation in accordance with the principles of Industry 4.0.