This section will guide you through the steps to replicate our study using the same methodology we applied. We provide detailed instructions, along with key resources to help you complete each step successfully. While some steps may be challenging or impractical to fully replicate, we have included a comprehensive replication package containing critical artifacts (such as the intial query results) to assist you.
If you encounter any issues or need clarification at any point, do not hesitate to contact us.
We adopted the design science methodology, a structured process comprising three primary phases: context awareness, solution synthesis, and solution validation. Our iterative process was organized into three cycles, each encompassing the design science phases to understand the problem context, devise a solution, and validate it.
Figure 1: Design Science Process.
The first research cycle aimed to explore the current state of Digital Twin architectures. A Systematic Literature Review (SLR) was conducted to identify key architectural elements and pinpoint limitations in existing approaches.
We used the search string to perform a systematic literature review to understand the studies discussing DT architectures. The SLR followed the activities shown in Figure 2.
Figure 2: Systematic Literature Review Process.
The detailed descriptions of each activity is available in the SLR report.
In short, we performed the search using Scopus and retrieved 5508 studies. We then applied the inclusion and exclusion criteria (IC/EC) from Table 1 below to filter the relevant studies, executed forward and backward snowballing, obtaining the final set of 45 primary studies. The results of Scopus query and the selection process based on the IC/EC criteria are available in the ScopusQueryResults.xlsx available in the replicationpackage.zip
ID | Description | Rationale |
---|---|---|
IC1 | The study is related to defining and documenting Digital Twin architectures. | Ensures relevance to the topic under investigation. |
IC2 | The study is written in English. | Ensures all reviewers can analyze the work. |
IC3 | The study is peer-reviewed. | Guarantees quality and reliability of the source. |
IC4 | The study is a primary study. | Avoids secondary sources that do not contribute original findings. |
IC5 | The study has been published after 2019. | Publications on DT architectures significantly increased after 2019. |
IC6 | The study was published in journals or conference proceedings. | Ensures that only studies from these two types of publications are included. |
IC7 | The study was published in high-ranking venues. | Improves the credibility of included studies. |
EC1 | The study is an earlier version of a more recent or complete version. | Avoids redundancy in reviewed studies. |
EC2 | The study treats Digital Twins solely as simulated models. | Ensures the Digital Twin is not mixed with simple simulation. |
EC3 | The study conflates Digital Twins with the Metaverse. | Avoids that Digital Twins are confused with immersive environments. |
EC4 | The study confuses Digital Twins with AI models. | Distinguishes between proper Digital Twin and isolated AI-based models. |
Table 1: Inclusion and Exclusion Criteria.
Finally, we extracted key information from the selected primary studies using a defined classification scheme. The detailed analysis can be found in the SelectedPaperAnalysis.xlsx file, which is included in the replicationpackage.zip.
In the second research cycle, the architectural elements (internally validated) were used to create the first draft of the Digital Twin Reference Architecture. The initial version of TwinArch was documented using the Software Engineering Institute Views & Beyond methodology. The draft was presented to five practitioners, including academic experts and industry professionals, participating to one of the project supporting this work. Their feedback guided further improvements that lead to the refinement of TwinArch.
The third research cycle focused on refining TwinArch based on feedback from practitioners, which highlighted the importance of incorporating existing Digital Twin platforms into the TwinArch design. To address this, a specific search of Digital Twin platforms and frameworks was conducted.
The search process involved three primary channels: (1) the Google search engine, to gain a broad overview of available platforms; (2) Google Scholar, to examine academic literature and analyses of Digital Twin technologies; and (3) GitHub repositories and official websites, to identify open-source projects with active development and community engagement.
Among the available solutions, the final selected platforms—Eclipse Ditto, Azure Digital Twins, and FIWARE— ensure representation across different categories of Digital Twin solutions, balancing openness, functionality, and cross-domain applicability. This in-depth examination provided a detailed understanding of each platform’s specific characteristics, enabling us to refine the architectural elements to better align with existing Digital Twin solutions and include practical examples.
The final validation involved an online survey of 20 Digital Twin experts from academia and industry. Details about the survey and the obtained results can be found on the dedicated webpage: evaluation.