AAS Design Challenge Clause Samples

AAS Design Challenge. The main challenge when designing an AAS Information model lies in the fact that there are very few existing models which can be used. Currently there are no general repositories or specific established patterns that can be followed when creating a new shell. This is even a bigger challenge when trying to model non-physical assets, which the agents are, as the predominant focus of the AAS modelling up until now is on modelling physical elements from a factory. Considering this challenge, the iterative design approach by ▇▇▇▇▇▇▇▇ et al. ([Bout21]). served the modelling well so far. The approach supported quick interaction with use case owners without getting bogged down in finding and aligning with existing models before starting the modelling work. This has prevented the AAS modelling from becoming a bottleneck in the project and provides structure to continue work in the second half of the MAS4AI project. Furthermore, the methodology supported quickly developing small submodels which can be iterated and expended upon as needed. This ended up creating highly reusable submodels which can be shared between AAS models. Another challenge within the design of the models was providing a clear and understandable way for the different involved parties to comprehend the created structure. The current asset administration shell tooling is not intuitive to everyone, especially those, who do not have extensive semantic modelling experience. Therefore, the choice was made to create high level visuals, which helped significantly with the communication with different stakeholders and allowed the gathering of feedback early in the process. To further work on this issue, the MAS4AI project is collaborating with the HORIZON DIMOFAC project [DIMO22] to develop a web application which makes AAS models and model templates more accessible to a wider audience.