Search

Although standards and specifications for digital twins aim to create interoperability in Industry 4.0, each standard has its own goals, focuses and representations for digital twins. This paper examines an approach to increasing interoperability between established digital twin specifications by transformation. Accordingly, several specifications are presented and requirements for transformation are examined. Following the feasibility analysis, a mapping between the Digital Twin Definition Language (DTDL) and Asset Administration Shell (AAS) was created. To examine the feasibility of this approach, the transformation was implemented and tested for a physical asset. This paper demonstrates that a generic mapping between DTDL and AAS can be applied for transformation in use cases where DTDL models are provided while AAS is required. [ABSTRACT FROM AUTHOR]

Industry 4.0 supports the vision of networked machines in decentralized production plants across the value chain. Hence, it requires highly connected partners exchanging relevant data about products, processes, and production resources. This paper proposes the usage of data spaces and digital twins to enable this Industry 4.0 vision and investigates the building blocks to realize a data space for Industry 4.0, e.g., the integration of digital twins inside the data space based upon the latest specification of the Industry 4.0 Asset Administration Shell. A prototypical implementation shows the feasibility of storing product carbon footprints inside a digital twin and sharing it over a data space with other partners. [ABSTRACT FROM AUTHOR]

The use of open-source software is crucial for the digitalization of manufacturing, including the implementation of Digital Twins as envisioned in Industry 4.0. This research paper provides a comprehensive comparison of free and open-source implementations of the reactive Asset Administration Shell (AAS) for creating Digital Twins. A structured search on GitHub and Google Scholar was conducted, leading to the selection of four implementations for detailed analysis. Objective evaluation criteria were defined, and a testing framework was created to test support for the most common AAS model elements and API calls. The results show that all implementations support at least a minimal set of required features while none implement the specification in all details, which highlights the challenges of implementing the AAS specification and the incompatibility between different implementations. This paper is therefore the first attempt at a comprehensive comparison of AAS implementations and identifies potential areas for improvement in future implementations. It also provides valuable insights for software developers and researchers in the field of AAS-based Digital Twins. [ABSTRACT FROM AUTHOR]