<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Publishing DTD v1.3 20210610//EN" "JATS-journalpublishing1-3-mathml3.dtd">
<article xml:lang="EN" xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:ali="http://www.niso.org/schemas/ali/1.0/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" dtd-version="1.3" article-type="research-article">
<front>
<journal-meta>
<journal-id journal-id-type="publisher-id">Front. Comput. Sci.</journal-id>
<journal-title-group>
<journal-title>Frontiers in Computer Science</journal-title>
<abbrev-journal-title abbrev-type="pubmed">Front. Comput. Sci.</abbrev-journal-title>
</journal-title-group>
<issn pub-type="epub">2624-9898</issn>
<publisher>
<publisher-name>Frontiers Media S.A.</publisher-name>
</publisher>
</journal-meta>
<article-meta>
<article-id pub-id-type="doi">10.3389/fcomp.2026.1757450</article-id>
<article-version article-version-type="Version of Record" vocab="NISO-RP-8-2008"/>
<article-categories>
<subj-group subj-group-type="heading">
<subject>Original Research</subject>
</subj-group>
</article-categories>
<title-group>
<article-title>Semantic foundations for digital twins: the contribution of ontological analysis</article-title>
</title-group>
<contrib-group>
<contrib contrib-type="author" corresp="yes">
<name><surname>Elhajj</surname> <given-names>Mohammed</given-names></name>
<xref ref-type="aff" rid="aff1"/>
<xref ref-type="corresp" rid="c001"><sup>&#x0002A;</sup></xref>
<role vocab="credit" vocab-identifier="https://credit.niso.org/" vocab-term="Formal analysis" vocab-term-identifier="https://credit.niso.org/contributor-roles/formal-analysis/">Formal analysis</role>
<role vocab="credit" vocab-identifier="https://credit.niso.org/" vocab-term="Investigation" vocab-term-identifier="https://credit.niso.org/contributor-roles/investigation/">Investigation</role>
<role vocab="credit" vocab-identifier="https://credit.niso.org/" vocab-term="Visualization" vocab-term-identifier="https://credit.niso.org/contributor-roles/visualization/">Visualization</role>
<role vocab="credit" vocab-identifier="https://credit.niso.org/" vocab-term="Writing &#x2013; review &amp; editing" vocab-term-identifier="https://credit.niso.org/contributor-roles/writing-review-editing/">Writing &#x2013; review &#x00026; editing</role>
<role vocab="credit" vocab-identifier="https://credit.niso.org/" vocab-term="Validation" vocab-term-identifier="https://credit.niso.org/contributor-roles/validation/">Validation</role>
<role vocab="credit" vocab-identifier="https://credit.niso.org/" vocab-term="Funding acquisition" vocab-term-identifier="https://credit.niso.org/contributor-roles/funding-acquisition/">Funding acquisition</role>
<role vocab="credit" vocab-identifier="https://credit.niso.org/" vocab-term="Data curation" vocab-term-identifier="https://credit.niso.org/contributor-roles/data-curation/">Data curation</role>
<role vocab="credit" vocab-identifier="https://credit.niso.org/" vocab-term="Resources" vocab-term-identifier="https://credit.niso.org/contributor-roles/resources/">Resources</role>
<role vocab="credit" vocab-identifier="https://credit.niso.org/" vocab-term="Supervision" vocab-term-identifier="https://credit.niso.org/contributor-roles/supervision/">Supervision</role>
<role vocab="credit" vocab-identifier="https://credit.niso.org/" vocab-term="Conceptualization" vocab-term-identifier="https://credit.niso.org/contributor-roles/conceptualization/">Conceptualization</role>
<role vocab="credit" vocab-identifier="https://credit.niso.org/" vocab-term="Methodology" vocab-term-identifier="https://credit.niso.org/contributor-roles/methodology/">Methodology</role>
<role vocab="credit" vocab-identifier="https://credit.niso.org/" vocab-term="Software" vocab-term-identifier="https://credit.niso.org/contributor-roles/software/">Software</role>
<role vocab="credit" vocab-identifier="https://credit.niso.org/" vocab-term="Writing &#x2013; original draft" vocab-term-identifier="https://credit.niso.org/contributor-roles/writing-original-draft/">Writing &#x2013; original draft</role>
<role vocab="credit" vocab-identifier="https://credit.niso.org/" vocab-term="Project administration" vocab-term-identifier="https://credit.niso.org/contributor-roles/project-administration/">Project administration</role>
<uri xlink:href="https://loop.frontiersin.org/people/3045171"/>
</contrib>
</contrib-group>
<aff id="aff1"><institution>Faculty of Computer Studies (FCS), Arab Open University (AOU)</institution>, <city>Beirut</city>, <country country="lb">Lebanon</country></aff>
<author-notes>
<corresp id="c001"><label>&#x0002A;</label>Correspondence: Mohammed Elhajj, <email xlink:href="mailto:mhajj@aou.edu.lb">mhajj@aou.edu.lb</email></corresp>
</author-notes>
<pub-date publication-format="electronic" date-type="pub" iso-8601-date="2026-03-02">
<day>02</day>
<month>03</month>
<year>2026</year>
</pub-date>
<pub-date publication-format="electronic" date-type="collection">
<year>2026</year>
</pub-date>
<volume>8</volume>
<elocation-id>1757450</elocation-id>
<history>
<date date-type="received">
<day>30</day>
<month>11</month>
<year>2025</year>
</date>
<date date-type="rev-recd">
<day>29</day>
<month>01</month>
<year>2026</year>
</date>
<date date-type="accepted">
<day>13</day>
<month>02</month>
<year>2026</year>
</date>
</history>
<permissions>
<copyright-statement>Copyright &#x000A9; 2026 Elhajj.</copyright-statement>
<copyright-year>2026</copyright-year>
<copyright-holder>Elhajj</copyright-holder>
<license>
<ali:license_ref start_date="2026-03-02">https://creativecommons.org/licenses/by/4.0/</ali:license_ref>
<license-p>This is an open-access article distributed under the terms of the <ext-link ext-link-type="uri" xlink:href="https://creativecommons.org/licenses/by/4.0/">Creative Commons Attribution License (CC BY)</ext-link>. The use, distribution or reproduction in other forums is permitted, provided the original author(s) and the copyright owner(s) are credited and that the original publication in this journal is cited, in accordance with accepted academic practice. No use, distribution or reproduction is permitted which does not comply with these terms.</license-p>
</license>
</permissions>
<abstract>
<p>Digital Twins (DTs) are revolutionizing industries by enabling real-time simulations, data-driven decision-making, and enhanced operational efficiency. However, their integration and scalability remain challenging due to the complexity of multi-domain systems, heterogeneous data sources, and semantic inconsistencies. This paper proposes an ontology-driven DT framework that leverages Web Ontology Language (OWL) and Description Logic (DL) to enhance semantic reasoning, data representation, and facilitates system interoperability through standards-aligned semantic mapping. A distributed ontology architecture ensures scalability and adaptability across diverse industrial applications. The results demonstrate a 60% reduction in integration time, a 75% decrease in error rates, and improved decision-making accuracy, highlighting the superiority of the ontology-based approach over traditional DTs. Comparative analysis underscores its effectiveness in addressing interoperability, semantic ambiguity, and system maintenance challenges. The findings emphasize the critical role of ontological analysis in developing self-adaptive, cross-domain DT systems. Future research will explore automated ontology generation, AI-driven semantic reasoning, and user-centric design to further enhance ontology-powered DT ecosystems.</p></abstract>
<kwd-group>
<kwd>architectural model</kwd>
<kwd>Description Logic (DL)</kwd>
<kwd>digital twins</kwd>
<kwd>interoperability</kwd>
<kwd>ontology-driven framework</kwd>
<kwd>semantic technologies</kwd>
<kwd>system scalability</kwd>
<kwd>Web Ontology Language (OWL)</kwd>
</kwd-group>
<funding-group>
<funding-statement>The author(s) declared that financial support was not received for this work and/or its publication.</funding-statement>
</funding-group>
<counts>
<fig-count count="16"/>
<table-count count="11"/>
<equation-count count="1"/>
<ref-count count="52"/>
<page-count count="31"/>
<word-count count="15669"/>
</counts>
<custom-meta-group>
<custom-meta>
<meta-name>section-at-acceptance</meta-name>
<meta-value>Theoretical Computer Science</meta-value>
</custom-meta>
</custom-meta-group>
</article-meta>
</front>
<body>
<sec sec-type="intro" id="s1">
<label>1</label>
<title>Introduction</title>
<p>Digital Twins (DTs) represent a groundbreaking technological innovation that bridges the gap between physical and virtual systems (<xref ref-type="bibr" rid="B11">El-Hajj et al., 2024</xref>). Initially conceptualized for the aerospace industry, DTs have evolved into a versatile tool applicable across diverse sectors, including manufacturing, healthcare, smart cities, and energy systems. By creating dynamic virtual representations of physical entities, DTs enable real-time monitoring, simulation, optimization, and predictive analytics, thereby transforming traditional decision-making processes and operational efficiency (<xref ref-type="bibr" rid="B50">van der Wal and El-Hajj, 2022</xref>). For instance, in smart manufacturing, DTs are used to simulate production lines, identify bottlenecks, and optimize resource allocation (<xref ref-type="bibr" rid="B51">Zhou et al., 2021</xref>). Similarly, in healthcare, DTs facilitate personalized treatment plans by simulating patient conditions and predicting outcomes (<xref ref-type="bibr" rid="B37">Nunez and Borsato, 2017</xref>).</p>
<p>However, as the complexity of systems grows, integrating and managing DTs effectively presents significant challenges. These challenges stem from the heterogeneous nature of the systems DTs interact with, including semantic heterogeneity, data inconsistency, and protocol mismatches. In this context, we define semantic consistency as encompassing both: (1) ABox logical consistency - ensuring no contradictory assertions about individuals exist in the knowledge base, and (2) TBox coherency - guaranteeing all concepts are satisfiable and properly defined without logical contradictions (detailed in Section 2.2.2). Regarding interoperability, this work focuses specifically on semantic interoperability&#x02014;the ability of different systems to exchange and understand data based on shared meaning rather than just syntactic compatibility. We address this through ontological alignment and semantic mapping techniques that ensure consistent interpretation of data across heterogeneous systems.</p>
<p>For example, industrial applications often require seamless communication between devices, systems, and stakeholders spanning multiple domains. This heterogeneity leads to semantic ambiguities (e.g., conflicting definitions of &#x0201C;temperature&#x0201D; across systems), inconsistent data standards (e.g., JSON vs. XML formats), and integration bottlenecks, thereby limiting the full realization of DT capabilities (<xref ref-type="bibr" rid="B28">Li et al., 2024</xref>). Addressing these challenges necessitates innovative approaches to standardize, organize, and manage the underlying data and knowledge systems.</p>
<p>Ontological analysis emerges as a promising solution to these challenges. In computer science, ontology refers to a structured framework that defines the concepts, relationships, and rules governing a specific domain. Ontologies provide a shared vocabulary and semantic clarity, enabling better communication and interoperability across systems. For instance, ontologies can resolve semantic ambiguities by standardizing terminology and relationships, such as defining &#x0201C;temperature&#x0201D; uniformly across manufacturing and climate control systems. In the realm of DTs, ontological analysis addresses key challenges such as semantic heterogeneity, data inconsistency, and system scalability by organizing knowledge hierarchically and enabling advanced reasoning mechanisms (<xref ref-type="bibr" rid="B18">Guizzardi and Guarino, 2024</xref>). Recent advancements in ontology-driven systems, such as the use of OWL (Web Ontology Language) and RDF (Resource Description Framework), have demonstrated their potential to enhance semantic interoperability and reasoning in complex environments (<xref ref-type="bibr" rid="B19">Horrocks et al., 2003</xref>).</p>
<p>This paper introduces a distributed ontology framework that addresses scalability and interoperability challenges through hierarchical semantic layers that maintain alignment with established ontology standards. Specifically, the framework leverages lightweight local ontologies for real-time operations, regional ontologies for detailed analytics, and global ontologies for system-wide reasoning. This approach not only improves semantic clarity but also supports modular growth and flexibility, enabling DTs to adapt dynamically to evolving requirements. The technical novelty of this work lies in its ability to balance semantic richness and computational efficiency while addressing the limitations of existing ontology-driven DT frameworks, such as scalability issues and alignment challenges (<xref ref-type="bibr" rid="B40">Pliatsios et al., 2023</xref>).</p>
<p>To illustrate the significance of this approach, consider the example of smart manufacturing systems, where DTs are used to monitor and optimize production lines. Without a unified semantic framework, integrating various machinery, sensors, and software systems becomes a daunting task due to incompatible data formats and protocols. Ontological analysis offers a robust solution by providing a common language for these systems, ensuring that data flows seamlessly and meaningfully. Similarly, in healthcare, DTs for patient monitoring and treatment planning benefit from ontological frameworks that harmonize medical data standards and enhance interoperability among diagnostic devices and electronic health record systems (<xref ref-type="bibr" rid="B12">El-Sappagh et al., 2015</xref>).</p>
<p>The objectives of this paper are three-fold. First, it provides a comprehensive overview of the technical challenges faced in integrating DTs into complex systems, such as semantic heterogeneity, scalability, and maintenance. Second, it examines the contribution of ontological analysis in addressing these challenges, with a focus on interoperability, semantic consistency, and scalability. Finally, the paper presents case studies and real-world applications demonstrating measurable improvements in efficiency, accuracy, and functionality achieved through ontology-driven DTs. For example, our proposed framework reduces integration time by 60%, decreases error rates during data exchange by 75%, and enhances decision-making accuracy by 20%.</p>
<p>The rest of this paper is structured as follows. Section 2 provides a detailed background on DTs and ontological analysis, elucidating their theoretical foundations and practical applications. Section 3 identifies key technical challenges in DT integration, emphasizing the need for innovative solutions. Section 4 discusses how ontological analysis addresses these challenges, supported by illustrative case studies. Section 5 outlines the methodology used in this study, while Section 6 presents the results and discusses their implications. Finally, Section 7 concludes with a summary of findings, limitations, and future research directions.</p>
<p>This study aims to contribute to the growing body of knowledge on DTs and their integration strategies by highlighting the pivotal role of ontological analysis. By doing so, it provides both theoretical insights and practical recommendations for researchers, practitioners, and policymakers engaged in the development and deployment of DTs. The findings underscore the importance of adopting ontology-driven approaches to maximize the potential of DTs in transforming complex systems and advancing technological innovation.</p>
</sec>
<sec id="s2">
<label>2</label>
<title>Background</title>
<p>The purpose of this section is to provide foundational knowledge on Digital Twins (DTs) and ontological analysis, both of which are pivotal to this research. By exploring these concepts in detail, we aim to establish the theoretical framework necessary for understanding the methodologies and innovations introduced later in this work. This background lays the groundwork for discussing how DTs can be enhanced using ontological frameworks to address challenges in system integration, interoperability, and decision-making. This discussion also highlights their application to modern challenges in critical infrastructure and security.</p>
<sec>
<label>2.1</label>
<title>Digital twins</title>
<p>Digital twins (DTs) are virtual representations of physical entities or systems that simulate their real-world counterparts in real-time. They integrate data from various sources to provide insights into the performance, behavior, and condition of the physical system, enabling better decision-making and predictive analysis (<xref ref-type="bibr" rid="B11">El-Hajj et al., 2024</xref>; <xref ref-type="bibr" rid="B50">van der Wal and El-Hajj, 2022</xref>). According to DNV, a digital twin is defined as <italic>a virtual representation of a system or asset that calculates system states and makes system information available, through integrated models and data, with the purpose of providing decision support over its life cycle</italic> (<xref ref-type="bibr" rid="B20">It&#x000E4;pelto, 2023</xref>).</p>
<sec>
<label>2.1.1</label>
<title>Key components of digital twins</title>
<p>Digital twins consist of the following interconnected components (illustrated in <xref ref-type="fig" rid="F1">Figure 1</xref>):</p>
<list list-type="bullet">
<list-item><p><bold>Physical system:</bold> The actual entity or system being represented, such as a machine, vehicle, or infrastructure. Physical systems generate real-time data through sensors and monitoring devices. For instance, IoT-enabled sensors collect data such as temperature, pressure, and vibration, which are transmitted via protocols like MQTT (Message Queuing Telemetry Transport) or OPC UA (Open Platform Communications Unified Architecture). While MQTT is lightweight and suitable for resource-constrained environments, it lacks advanced security features by default. OPC UA, on the other hand, provides robust security but requires higher computational resources.</p></list-item>
<list-item><p><bold>Virtual representation:</bold> A digital counterpart of the physical system, often created using advanced modeling techniques such as finite element analysis (FEA), discrete-event simulation (DES), or agent-based modeling (ABM). These techniques enable accurate simulations of physical behaviors. For example, FEA is widely used in structural analysis to predict stress distributions, while DES models complex workflows in manufacturing systems.</p></list-item>
<list-item><p><bold>Data communication:</bold> This component ensures the seamless flow of information between the physical system and its digital twin. It includes protocols for data transfer, storage, and processing. Protocols like MQTT and OPC UA facilitate real-time updates but differ in scalability and security. MQTT&#x00027;s publish-subscribe model is ideal for distributed systems, whereas OPC UA&#x00027;s client-server architecture ensures reliable communication in industrial settings.</p></list-item>
<list-item><p><bold>Ontology framework:</bold> A structured framework defining the semantics of data and relationships within the digital twin system, enhancing integration, reasoning, and decision-making. Ontologies enable semantic interoperability by standardizing terminology and relationships across heterogeneous systems.</p></list-item>
</list>
<fig position="float" id="F1">
<label>Figure 1</label>
<caption><p>Key components of a digital twin framework.</p></caption>
<graphic mimetype="image" mime-subtype="tiff" xlink:href="fcomp-08-1757450-g0001.tif">
<alt-text content-type="machine-generated">Diagram showing the interaction between three entities: Physical System, Virtual Representation, and Data Communication. Labeled arrows indicate data updates, status reporting, response, commands, data flow, and integration connecting the entities.</alt-text>
</graphic>
</fig>
</sec>
<sec>
<label>2.1.2</label>
<title>Applications of digital twins</title>
<p>DTs have found application in diverse fields, including:</p>
<list list-type="bullet">
<list-item><p><bold>Manufacturing:</bold> In smart factories, DTs optimize production lines by simulating operations to identify bottlenecks and improve efficiency. For example, Siemens uses DTs to monitor and optimize turbine performance, reducing downtime by 20% (<xref ref-type="bibr" rid="B35">Mihai et al., 2021</xref>).</p></list-item>
<list-item><p><bold>Healthcare:</bold> DTs simulate patient conditions to improve treatment plans. For instance, Philips Healthcare employs DTs to create personalized models of patients&#x00027; cardiovascular systems, enabling tailored therapies (<xref ref-type="bibr" rid="B49">Tripathi and Nishad, 2019</xref>).</p></list-item>
<list-item><p><bold>Smart cities:</bold> DTs help manage urban infrastructure by simulating traffic patterns, energy consumption, and resource allocation. Singapore&#x00027;s Smart Nation initiative uses DTs to optimize traffic flow and reduce congestion by 15% (<xref ref-type="bibr" rid="B10">El-Hajj, 2024</xref>).</p></list-item>
<list-item><p><bold>Critical infrastructure:</bold> DTs monitor bridges and infrastructure for health and safety using sensor data and predictive analytics. For example, the European Union&#x00027;s Horizon 2020 project uses DTs to predict structural failures in aging bridges (<xref ref-type="bibr" rid="B20">It&#x000E4;pelto, 2023</xref>; <xref ref-type="bibr" rid="B7">Brucherseifer et al., 2021</xref>).</p></list-item>
</list>
</sec>
</sec>
<sec>
<label>2.2</label>
<title>Ontological analysis</title>
<p>In computer science, ontology is a formal specification of concepts and their relationships within a domain. Ontologies provide a shared vocabulary, facilitating effective communication between systems and stakeholders (<xref ref-type="bibr" rid="B17">Guizzardi, 2005</xref>; <xref ref-type="bibr" rid="B18">Guizzardi and Guarino, 2024</xref>).</p>
<sec>
<label>2.2.1</label>
<title>Components of an ontology framework</title>
<p>Ontology frameworks are critical for structuring knowledge within a domain, enabling clear communication and interoperability between systems. They consist of five essential components:</p>
<list list-type="bullet">
<list-item><p><bold>Concepts:</bold> Represented as OWL classes, concepts define entities within the domain. For example, in a manufacturing DT, concepts might include <monospace>Machine</monospace>, <monospace>Sensor</monospace>, and <monospace>Workpiece</monospace>. These classes are organized hierarchically using subClassOf relationships.</p></list-item>
<list-item><p><bold>Relations:</bold> Defined as OWL object properties, relations specify connections between concepts. For instance, the relation <monospace>monitoredBy</monospace> links <monospace>Machine</monospace> to <monospace>Sensor</monospace>. Relations enable dynamic interactions within the modeled domain.</p></list-item>
<list-item><p><bold>Functions:</bold> Functions describe operations or transformations involving concepts. For example, a function <monospace>AnalyzeSensorData</monospace> might take input from <monospace>Sensor</monospace> and output an anomaly score. These functions are implemented using rule-based inference engines or SPARQL queries.</p></list-item>
<list-item><p><bold>Axioms:</bold> Expressed as logical constraints, axioms enforce consistency within the ontology. For example, an axiom might assert that &#x0201C;every <monospace>Machine</monospace> must have at least one <monospace>Sensor</monospace>.&#x0201D; These rules govern reasoning within the ontology.</p></list-item>
<list-item><p><bold>Instances:</bold> Represented as RDF triples, instances populate the ontology with real-world data. For example, <monospace>Machine1 rdf:type Machine</monospace> and <monospace>Sensor1 rdf:type Sensor</monospace> define specific entities within the domain.</p></list-item>
</list>
<p>This component-based approach ensures that the ontology framework is comprehensive and adaptable. Figure 2 illustrates how these components interact within an ontology designed for enhancing security in critical infrastructure.</p>
<p>While <xref ref-type="fig" rid="F3">Figure 3</xref> illustrates the formal alignment between our custom Digital Twin ontology and established semantic standards, including BFO (Basic Formal Ontology), SOSA (Sensor, Observation, Sample, and Actuator), and SAREF (Smart Applications Reference). The mappings use formal Description Logic axioms: equivalence (&#x02261;) indicates that concepts are semantically identical (e.g., <monospace>PhysicalSystem</monospace> maps to <monospace>bfo:MaterialEntity</monospace>), while subsumption (&#x02291;) indicates that our concept is a specialization of the standard one (e.g., our <monospace>Sensor</monospace> is a subclass of <monospace>sosa:Sensor</monospace>). These alignments ensure that our ontology maintains semantic interoperability with systems using standard ontologies while preserving the performance advantages of our purpose-built framework.</p>
</sec>
<sec>
<label>2.2.2</label>
<title>Semantic consistency in ontologies</title>
<p>Semantic consistency in ontological systems addresses two main aspects:</p>
<list list-type="order">
<list-item><p><bold>ABox consistency:</bold> Refers to the logical consistency of assertions about individuals. An ABox is inconsistent if it contains contradictory statements (e.g., asserting that an individual belongs to two disjoint classes). This is typically checked using tableau algorithms in Description Logic reasoners.</p></list-item>
<list-item><p><bold>TBox coherency:</bold> Concerns the satisfiability of concepts defined in the ontology. A concept is unsatisfiable if it cannot have any instances given the ontology&#x00027;s axioms, indicating a modeling error. TBox coherency ensures that all defined concepts are meaningful and properly related.</p></list-item>
</list>
<p>In Digital Twin applications, maintaining both ABox consistency and TBox coherency is critical for reliable reasoning and decision-making. Our framework addresses these through automated consistency checking mechanisms integrated into the ontology management pipeline.</p>
</sec>
<sec>
<label>2.2.3</label>
<title>Benefits of ontological analysis for digital twins</title>
<p>Ontological frameworks significantly enhance the integration, interoperability, and adaptability of digital twins in several ways:</p>
<list list-type="bullet">
<list-item><p><bold>Integration of diverse data sources:</bold> Ontologies enable the integration of data from various sources by providing a common semantic framework. For example, OWL ontologies map heterogeneous data formats (e.g., JSON, XML) into a unified structure.</p></list-item>
<list-item><p><bold>Interoperability across systems:</bold> By standardizing terminology and defining relationships, ontologies facilitate seamless communication. For instance, SPARQL queries retrieve data from distributed systems, ensuring consistent interpretation.</p></list-item>
<list-item><p><bold>Adaptability to changing conditions:</bold> Ontologies can evolve dynamically. For example, rule-based inference engines update ontologies in response to new data or operational requirements.</p></list-item>
<list-item><p><bold>Enhanced reasoning capabilities:</bold> Ontologies leverage reasoning mechanisms such as Description Logic (DL) and SWRL (Semantic Web Rule Language) to infer new knowledge. For example, DL infers that a <monospace>HighTemperature</monospace> event implies a potential <monospace>Overheating</monospace> risk.</p></list-item>
<list-item><p><bold>Quality assurance frameworks:</bold> Ontologies define clear lifecycle components, ensuring reliability. For instance, ISO standards use ontologies to validate DT implementations.</p></list-item>
</list>
</sec>
<sec>
<label>2.2.4</label>
<title>Role in critical infrastructure</title>
<p>In critical infrastructure, ontologies:</p>
<list list-type="bullet">
<list-item><p>Define standardized terminology for components (e.g., <monospace>Sensor</monospace>, <monospace>ControlSystem</monospace>).</p></list-item>
<list-item><p>Facilitate security protocols by outlining relationships and constraints.</p></list-item>
<list-item><p>Enhance resilience through predictive analytics and failure detection.</p></list-item>
</list>
</sec>
<sec>
<label>2.2.5</label>
<title>Domain ontologies for digital twins</title>
<p>Domain ontologies provide specialized vocabularies and conceptual models for specific application areas, enabling precise semantic representation and reasoning within those domains. In our ontology-driven DT framework, we leverage established domain ontologies to ensure semantic interoperability and domain-specific knowledge representation. Below we define, name, and scope key domain ontologies relevant to DT applications:</p>
<list list-type="bullet">
<list-item><p><bold>Manufacturing ontologies:</bold> For industrial applications, we utilize ontologies that model manufacturing processes, resources, and systems. The Manufacturing Service Description Language (MSDL) ontology provides concepts for manufacturing services and capabilities (<xref ref-type="bibr" rid="B1">Ameri et al., 2022</xref>). Additionally, the ISA-95 standard ontology models enterprise-control system integration, while the OPC UA companion specifications offer semantic models for industrial automation. These ontologies scope production planning, machine operations, quality control, and maintenance activities, enabling agile and resilient manufacturing systems as demonstrated in Industry 4.0 applications (<xref ref-type="bibr" rid="B1">Ameri et al., 2022</xref>; <xref ref-type="bibr" rid="B5">Barth et al., 2020</xref>).</p></list-item>
<list-item><p><bold>Healthcare ontologies:</bold> In medical and healthcare DTs, we employ ontologies that standardize clinical terminology and patient data. The Systematized Nomenclature of Medicine Clinical Terms (SNOMED CT) provides comprehensive clinical healthcare terminology, while the Fast Healthcare Interoperability Resources (FHIR) ontology structures electronic health records. The Observational Medical Outcomes Partnership (OMOP) Common Data Model ontology enables longitudinal health data analysis. These ontologies scope patient conditions, treatments, medical devices, and clinical workflows, supporting personalized medicine and interoperable healthcare systems (<xref ref-type="bibr" rid="B37">Nunez and Borsato, 2017</xref>; <xref ref-type="bibr" rid="B12">El-Sappagh et al., 2015</xref>).</p></list-item>
<list-item><p><bold>Smart city ontologies:</bold> For urban infrastructure DTs, we adopt ontologies that model city services and IoT deployments. The Smart Applications Reference (SAREF) ontology standardizes smart appliance and energy domain concepts, while the Semantic Sensor Network (SSN) ontology models sensors, observations, and actuations. The CityGML ontology provides 3D city model semantics for urban planning. These ontologies scope transportation, energy management, environmental monitoring, and public services, enabling integrated smart city solutions (<xref ref-type="bibr" rid="B6">Bellini et al., 2022</xref>; <xref ref-type="bibr" rid="B40">Pliatsios et al., 2023</xref>).</p></list-item>
</list>
<p>In our distributed ontology framework, these domain ontologies operate at local and regional levels, providing specialized semantics that are aligned with our global ontology for cross-domain interoperability. This hierarchical approach ensures both domain-specific accuracy and system-wide semantic consistency.</p>
</sec>
<sec>
<label>2.2.6</label>
<title>Case studies</title>
<p>To contextualize the discussion, consider the following case studies:</p>
<list list-type="bullet">
<list-item><p><bold>Manufacturing:</bold> General Electric (GE) uses DTs with ontologies to monitor gas turbines. The ontology maps sensor data to operational metrics, enabling predictive maintenance and reducing unplanned downtime by 30%.</p></list-item>
<list-item><p><bold>Healthcare:</bold> Philips Healthcare integrates DTs with ontologies to simulate patient-specific cardiovascular models. The ontology standardizes medical terminology, ensuring interoperability between diagnostic devices and electronic health records.</p></list-item>
<list-item><p><bold>Smart cities:</bold> Barcelona&#x00027;s smart city initiative uses ontologies to integrate traffic, energy, and water management systems. The ontology ensures semantic consistency, reducing integration costs by 40%.</p></list-item>
</list>
</sec>
<sec>
<label>2.2.7</label>
<title>Distributed ontology framework for digital twins</title>
<p>The distributed ontology framework balances semantic richness and system performance by employing multiple layers of reasoning:</p>
<list list-type="order">
<list-item><p><bold>Local ontologies:</bold> Lightweight ontologies deployed at the edge support real-time operations without overburdening the system.</p></list-item>
<list-item><p><bold>Regional ontologies:</bold> Comprehensive ontologies enable detailed analytics and simulation.</p></list-item>
<list-item><p><bold>Global ontologies:</bold> Centralized ontologies provide system-wide reasoning capabilities.</p></list-item>
</list>
<sec>
<label>2.2.7.1</label>
<title>Distinction between architectural layers and formal ontology types</title>
<p>It is important to distinguish between the architectural layers of ontologies (local, regional, and global) and the formal types of ontologies (upper vs. domain ontologies). The architectural layers refer to the scope and deployment of ontologies in a distributed system, where local ontologies are used for specific devices or processes, regional for a department or a factory, and global for the entire organization. On the other hand, formal ontology types categorize ontologies based on their level of generality: upper ontologies (e.g., BFO, DOLCE) provide very general concepts that are common across all domains, while domain ontologies (e.g., an ontology for manufacturing) are built upon upper ontologies and provide specific concepts for a particular domain. In our framework, we use domain ontologies at the local and regional levels, which are aligned with a global upper ontology to ensure interoperability and consistent reasoning across the system.</p>
</sec>
<sec>
<label>2.2.7.2</label>
<title>Ontology classification framework</title>
<p>Our architectural layering (local, regional, and global) aligns with established ontology classification frameworks that distinguish ontologies by scope and generality (<xref ref-type="bibr" rid="B13">Falquet et al., 2012</xref>). While traditional classifications categorize ontologies as upper (domain-independent), domain-specific, and application ontologies, our framework operationalizes this hierarchy through deployment considerations in distributed Digital Twin systems. The local layer corresponds to application ontologies for specific devices, the regional layer to domain ontologies for specialized areas (e.g., manufacturing, healthcare), and the global layer provides upper-ontology concepts for cross-domain interoperability.</p>
</sec>
<sec>
<label>2.2.7.3</label>
<title>Choice of upper ontology</title>
<p>Our framework does not explicitly adopt a standardized upper ontology [e.g., BFO (<xref ref-type="bibr" rid="B38">Otte et al., 2022</xref>) or DOLCE (<xref ref-type="bibr" rid="B31">Masolo et al., 2003</xref>)]. Instead, we developed a custom global ontology that serves as a high-level semantic layer, designed to meet the specific interoperability and reasoning requirements of Digital Twin ecosystems. This pragmatic choice was motivated by the need for:</p>
<list list-type="bullet">
<list-item><p><bold>Real-time performance:</bold> Lightweight, purpose-built ontologies reduce reasoning overhead in time-sensitive operations (<xref ref-type="bibr" rid="B52">Zhou et al., 2006</xref>; <xref ref-type="bibr" rid="B19">Horrocks et al., 2003</xref>).</p></list-item>
<list-item><p><bold>Domain-specific alignment:</bold> Direct integration with established domain ontologies [e.g., SOSA (<xref ref-type="bibr" rid="B21">Janowicz et al., 2019</xref>) for sensors, SAREF (<xref ref-type="bibr" rid="B2">Aniakor et al., 2024</xref>) for energy] commonly used in IoT and industrial settings.</p></list-item>
<list-item><p><bold>Scalability and adaptability:</bold> Flexibility to extend and modify the ontology as new DT components and domains are integrated (<xref ref-type="bibr" rid="B36">Noy and McGuinness, 2001</xref>).</p></list-item>
</list>
<p>Nevertheless, our global ontology is semantically aligned with upper-ontology principles, distinguishing between entities, processes, qualities, and relationships, and can be mapped to standard upper ontologies if broader cross-domain integration is required (<xref ref-type="bibr" rid="B17">Guizzardi, 2005</xref>). This approach ensures a balance between semantic rigor and practical deployability in complex, dynamic DT environments (<xref ref-type="bibr" rid="B40">Pliatsios et al., 2023</xref>).</p>
<p><xref ref-type="fig" rid="F4">Figure 4</xref> illustrates the proposed framework.</p>
</sec>
</sec>
<sec>
<label>2.2.8</label>
<title>Alignment with standard ontology initiatives</title>
<p>While our framework adopts a purpose-built global ontology for performance reasons, we ensure semantic alignment with established ontology standards through systematic mapping and interoperability mechanisms:</p>
<list list-type="bullet">
<list-item><p><bold>Semantic mapping to upper ontologies:</bold> Our global ontology maintains conceptual alignment with BFO (Basic Formal Ontology) and DOLCE (Descriptive Ontology for Linguistic and Cognitive Engineering) through explicit cross-references and property mappings. For instance, our <monospace>PhysicalSystem</monospace> class is mapped to BFO&#x00027;s <monospace>Material Entity</monospace>, and <monospace>VirtualRepresentation</monospace> to BFO&#x00027;s <monospace>Generically Dependent Continuant</monospace>.</p></list-item>
<list-item><p><bold>Integration with domain standards:</bold> Our domain ontologies (manufacturing, healthcare, smart cities) are directly derived from or aligned with established standards:
<list list-type="simple">
<list-item><p>- Manufacturing ontologies align with ISA-95 and OPC UA companion specifications.</p></list-item>
<list-item><p>- Healthcare ontologies incorporate SNOMED CT and FHIR concepts.</p></list-item>
<list-item><p>- Smart city ontologies adopt SAREF and CityGML standards.</p></list-item>
</list></p></list-item>
<list-item><p><bold>Standardized interoperability mechanisms:</bold> We implement W3C-recommended semantic web standards:
<list list-type="simple">
<list-item><p>- OWL 2 DL for ontology representation.</p></list-item>
<list-item><p>- RDF for data interchange.</p></list-item>
<list-item><p>- SPARQL 1.1 for querying.</p></list-item>
<list-item><p>- SHACL for data validation.</p></list-item>
</list></p></list-item>
<list-item><p><bold>Formal alignment methods:</bold> We employ ontology alignment techniques including:
<list list-type="simple">
<list-item><p>- Logical consistency checking using HermiT reasoner.</p></list-item>
<list-item><p>- Semantic similarity measures for concept matching.</p></list-item>
<list-item><p>- Automated mapping generation using tools like LogMap (<xref ref-type="bibr" rid="B22">Jim&#x000E9;nez-Ruiz and Cuenca Grau, 2011</xref>).</p></list-item>
</list></p></list-item>
</list>
<p>This multi-layered approach ensures that while optimized for Digital Twin performance, our framework maintains semantic interoperability with systems using standard ontologies through well-defined alignment mechanisms.</p>
</sec>
</sec>
</sec>
<sec id="s3">
<label>3</label>
<title>Related work</title>
<p>DTs have emerged as transformative tools in various domains, enabling the real-time monitoring and simulation of physical systems. They provide a virtual representation that integrates data from multiple sources, facilitating predictive analytics and decision-making. Concurrently, ontology-based systems offer structured frameworks for knowledge representation, enabling clearer communication and interoperability among diverse systems. However, integrating ontologies with digital twins presents significant challenges, particularly in ensuring consistency and semantic richness across complex, dynamic environments.</p>
<sec>
<label>3.1</label>
<title>Thematic discussion</title>
<sec>
<label>3.1.1</label>
<title>Ontology design approaches</title>
<p>Several approaches to ontology design have been explored in the context of digital twins:</p>
<list list-type="bullet">
<list-item><p><bold>Modular ontologies:</bold>
<list list-type="simple">
<list-item><p>- <italic>Description:</italic> Modular ontologies are designed as independent components that can be reused and combined. This approach allows for flexibility and scalability.</p></list-item>
<list-item><p>- <italic>Pros:</italic> Facilitates the integration of diverse knowledge domains and promotes reusability.</p></list-item>
<list-item><p>- <italic>Cons:</italic> Can lead to challenges in ensuring consistency and coherence among modules, especially when integrating multiple sources of data (<xref ref-type="bibr" rid="B29">Liu et al., 2021</xref>).</p></list-item>
</list></p></list-item>
<list-item><p><bold>Lightweight ontologies:</bold>
<list list-type="simple">
<list-item><p>- <italic>Description:</italic> Lightweight ontologies prioritize simplicity and ease of use, often sacrificing some expressiveness for performance.</p></list-item>
<list-item><p>- <italic>Pros:</italic> Faster processing and easier implementation in real-time systems.</p></list-item>
<list-item><p>- <italic>Cons:</italic> May lack the depth needed for complex reasoning tasks, limiting their effectiveness in sophisticated applications like DTs (<xref ref-type="bibr" rid="B24">Kendall and McGuinness, 2019</xref>).</p></list-item>
</list></p></list-item>
<list-item><p><bold>Centralized frameworks:</bold>
<list list-type="simple">
<list-item><p>- <italic>Description:</italic> Centralized ontologies provide a single, unified model that encompasses all relevant concepts and relationships.</p></list-item>
<list-item><p>- <italic>Pros:</italic> Ensures consistency and reduces ambiguity in terminology.</p></list-item>
<list-item><p>- <italic>Cons:</italic> Can become unwieldy as complexity increases, leading to difficulties in maintenance and updates (<xref ref-type="bibr" rid="B36">Noy and McGuinness, 2001</xref>).</p></list-item>
</list></p></list-item>
</list>
</sec>
<sec>
<label>3.1.2</label>
<title>Integration with knowledge graphs</title>
<p>Efforts to couple ontologies with knowledge graphs have gained traction, particularly for enhancing reasoning capabilities and analytics within digital twins:</p>
<list list-type="bullet">
<list-item><p><bold>Existing efforts:</bold> Research has demonstrated how integrating ontologies with knowledge graphs can improve semantic querying and data retrieval processes. For instance, using knowledge graphs allows for enhanced context awareness in DT applications by linking disparate data sources through semantic relationships (<xref ref-type="bibr" rid="B39">Peng et al., 2023</xref>).</p></list-item>
<list-item><p><bold>Limitations:</bold> Despite these advancements, challenges remain regarding scalability. As the size of the knowledge graph increases, maintaining performance and managing complexity becomes increasingly difficult. Additionally, the dynamic nature of digital twins requires real-time updates to both ontologies and knowledge graphs, complicating integration efforts (<xref ref-type="bibr" rid="B8">Buchgeher et al., 2021</xref>).</p></list-item>
</list>
</sec>
<sec>
<label>3.1.3</label>
<title>Applications in distributed systems</title>
<p>Distributed ontologies have found applications in various fields such as the Internet of Things (IoT) and smart cities:</p>
<list list-type="bullet">
<list-item><p><bold>Examples:</bold> In smart cities, distributed ontologies are used to manage data from various sensors deployed across urban environments. These ontologies help ensure semantic interoperability among different systems managing traffic, energy consumption, and public safety (<xref ref-type="bibr" rid="B29">Liu et al., 2021</xref>).</p></list-item>
<list-item><p><bold>Challenges:</bold> Key challenges include synchronization of distributed ontologies across heterogeneous systems and alignment of concepts to ensure consistent interpretation of data. The dynamic nature of these environments requires robust mechanisms for updating ontological structures without disrupting ongoing operations (<xref ref-type="bibr" rid="B40">Pliatsios et al., 2023</xref>).</p></list-item>
</list>
</sec>
</sec>
<sec>
<label>3.2</label>
<title>Gaps and opportunities</title>
<p>While significant progress has been made in ontology integration with digital twins, several gaps remain:</p>
<list list-type="bullet">
<list-item><p><bold>Shortcomings of existing approaches:</bold> Many current methodologies struggle to scale effectively for large-scale DT systems that require real-time data processing. Existing frameworks often do not account for the complexities involved in managing vast amounts of dynamically changing data (<xref ref-type="bibr" rid="B24">Kendall and McGuinness, 2019</xref>).</p></list-item>
<list-item><p><bold>Lack of optimization methods:</bold> There is a notable absence of methods aimed at optimizing both semantic richness and system performance simultaneously. Current approaches often prioritize one over the other, leading to trade-offs that can undermine overall system effectiveness (<xref ref-type="bibr" rid="B36">Noy and McGuinness, 2001</xref>).</p></list-item>
<list-item><p><bold>Inability to address dynamic environments:</bold> Many existing frameworks do not sufficiently address the challenge of managing rapidly evolving, dynamic environments inherent in digital twins. This limitation poses significant difficulties in real-time system integration and operational updates (<xref ref-type="bibr" rid="B8">Buchgeher et al., 2021</xref>).</p></list-item>
</list>
</sec>
<sec>
<label>3.3</label>
<title>Comparison with existing ontology standards and initiatives</title>
<p>To contextualize our distributed ontology framework within the broader landscape of semantic standardization efforts, we explicitly compare it with prominent initiatives such as the Industrial Ontology Foundry (IOF) (<xref ref-type="bibr" rid="B26">Kulvatunyou et al., 2018</xref>), ISO 23247 (Digital Twin framework for manufacturing) (<xref ref-type="bibr" rid="B43">Shao, 2021</xref>), the Reference Architectural Model Industrie 4.0 (RAMI 4.0) and Asset Administration Shell (AAS) (<xref ref-type="bibr" rid="B3">Bader and Maleshkova, 2019</xref>), and other semantic models like BFO (<xref ref-type="bibr" rid="B38">Otte et al., 2022</xref>) and DOLCE (<xref ref-type="bibr" rid="B31">Masolo et al., 2003</xref>). <xref ref-type="table" rid="T1">Table 1</xref> summarizes the scope, ontology type, key features, and how our framework aligns with or extends these efforts.</p>
<table-wrap position="float" id="T1">
<label>Table 1</label>
<caption><p>Comparison with existing ontology standards and initiatives.</p></caption>
<table frame="box" rules="all">
<thead>
<tr>
<th valign="top" align="left"><bold>Initiative</bold></th>
<th valign="top" align="left"><bold>Scope</bold></th>
<th valign="top" align="left"><bold>Ontology type</bold></th>
<th valign="top" align="left"><bold>Key features</bold></th>
<th valign="top" align="left"><bold>Alignment with our framework</bold></th>
</tr>
</thead>
<tbody>
<tr>
<td valign="top" align="left">Industrial ontology foundry (IOF) (<xref ref-type="bibr" rid="B26">Kulvatunyou et al., 2018</xref>)</td>
<td valign="top" align="left">Manufacturing, supply chain</td>
<td valign="top" align="left">Upper &#x0002B; Domain</td>
<td valign="top" align="left">Modular, BFO-based, interoperable</td>
<td valign="top" align="left">Our framework complements IOF by adding real-time reasoning and cross-domain integration layers.</td>
</tr>
<tr>
<td valign="top" align="left">ISO 23247 (<xref ref-type="bibr" rid="B43">Shao, 2021</xref>)</td>
<td valign="top" align="left">Manufacturing digital twins</td>
<td valign="top" align="left">Framework &#x0002B; Semantics</td>
<td valign="top" align="left">Standardized DT components, lifecycle phases</td>
<td valign="top" align="left">Our global ontology can be mapped to ISO 23247 components, ensuring compliance.</td>
</tr>
<tr>
<td valign="top" align="left">RAMI 4.0/AAS (<xref ref-type="bibr" rid="B3">Bader and Maleshkova, 2019</xref>)</td>
<td valign="top" align="left">Industrie 4.0, smart manufacturing</td>
<td valign="top" align="left">Meta-model &#x0002B; AAS shells</td>
<td valign="top" align="left">Asset administration, semantic interoperability</td>
<td valign="top" align="left">Our local ontologies align with AAS semantic models, enabling asset-level semantics.</td>
</tr>
<tr>
<td valign="top" align="left">SAREF (<xref ref-type="bibr" rid="B2">Aniakor et al., 2024</xref>)</td>
<td valign="top" align="left">Smart appliances, energy</td>
<td valign="top" align="left">Domain ontology</td>
<td valign="top" align="left">IoT &#x00026; energy domain standardization</td>
<td valign="top" align="left">Our framework integrates SAREF as a domain ontology for energy management applications.</td>
</tr>
<tr>
<td valign="top" align="left">BFO/DOLCE (<xref ref-type="bibr" rid="B38">Otte et al., 2022</xref>; <xref ref-type="bibr" rid="B31">Masolo et al., 2003</xref>)</td>
<td valign="top" align="left">General upper ontology</td>
<td valign="top" align="left">Upper ontology</td>
<td valign="top" align="left">Foundational concepts, cross-domain consistency</td>
<td valign="top" align="left">Our global ontology is semantically aligned with upper-ontology principles but is purpose-built for DT performance.</td>
</tr>
<tr>
<td valign="top" align="left">Our distributed ontology framework</td>
<td valign="top" align="left">Cross-domain DT ecosystems</td>
<td valign="top" align="left">Hybrid (upper &#x0002B; domain)</td>
<td valign="top" align="left">Real-time reasoning, scalable layers, federated alignment, OWL-DL &#x0002B; SWRL support</td>
<td valign="top" align="left">Balances semantic richness with computational efficiency; integrates with existing standards via alignment mechanisms.</td>
</tr></tbody>
</table>
</table-wrap>
<p>Our framework is designed to be complementary to these existing standards. For instance, while IOF provides a robust manufacturing ontology, our framework extends it with real-time reasoning and cross-domain interoperability. Similarly, our global ontology can be mapped to ISO 23247 components, ensuring compliance with international standards. The AAS semantic model aligns with our local ontologies, enabling asset-level semantics in Industrie 4.0 scenarios. Unlike SAREF or SNOMED CT, which are domain-specific, our framework provides a unified semantic layer that integrates multiple domain ontologies under a coherent global model. This hybrid approach allows us to leverage the strengths of existing standards while addressing their limitations in real-time reasoning and cross-domain integration.</p>
</sec>
<sec>
<label>3.4</label>
<title>Benchmark</title>
<p>To benchmark existing approaches, we evaluate key criteria such as scalability, semantic richness, performance efficiency, and ease of integration. <xref ref-type="table" rid="T2">Table 2</xref> summarizes strengths and weaknesses of recent methodologies.</p>
<table-wrap position="float" id="T2">
<label>Table 2</label>
<caption><p>Comparison of ontology-based approaches for digital twins.</p></caption>
<table frame="box" rules="all">
<thead>
<tr>
<th valign="top" align="left"><bold>References</bold></th>
<th valign="top" align="left"><bold>Approach used</bold></th>
<th valign="top" align="left"><bold>Semantic framework</bold></th>
<th valign="top" align="left"><bold>Performance metrics</bold></th>
<th valign="top" align="left"><bold>Limitations</bold></th>
</tr>
</thead>
<tbody>
<tr>
<td valign="top" align="left"><xref ref-type="bibr" rid="B41">Ploennigs et al. (2022)</xref></td>
<td valign="top" align="left">Semantic graphs for AI pipelines</td>
<td valign="top" align="left">RDF &#x0002B; AI Models</td>
<td valign="top" align="left">Scalability: high, automation gain: 70%</td>
<td valign="top" align="left">Challenges in scaling knowledge graphs for large IoT datasets.</td>
</tr>
<tr>
<td valign="top" align="left"><xref ref-type="bibr" rid="B5">Barth et al. (2020)</xref></td>
<td valign="top" align="left">Systematization via ontology</td>
<td valign="top" align="left">OWL &#x0002B; RDF</td>
<td valign="top" align="left">Supports structuring and communication of DT activities</td>
<td valign="top" align="left">Challenges in universal applicability across domains.</td>
</tr>
<tr>
<td valign="top" align="left"><xref ref-type="bibr" rid="B4">Bamunuarachchi et al. (2020)</xref></td>
<td valign="top" align="left">Cyber Twins for Industry 4.0</td>
<td valign="top" align="left">Machine representation Model &#x0002B; IoT Services</td>
<td valign="top" align="left">Improves development efficiency, testing, portability</td>
<td valign="top" align="left">Limited scalability for large-scale ecosystems.</td>
</tr>
<tr>
<td valign="top" align="left"><xref ref-type="bibr" rid="B45">Skobelev et al. (2020)</xref></td>
<td valign="top" align="left">Ontology-based multi-agent system for precision farming</td>
<td valign="top" align="left">OWL &#x0002B; RDF &#x0002B; Multi-Agent</td>
<td valign="top" align="left">Improved yield forecasting accuracy</td>
<td valign="top" align="left">Limited scalability for large-scale systems.</td>
</tr>
<tr>
<td valign="top" align="left"><xref ref-type="bibr" rid="B16">Gowripeddi et al. (2023)</xref></td>
<td valign="top" align="left">Ontology-based intrusion detection with DTs</td>
<td valign="top" align="left">OWL &#x0002B; RDF &#x0002B; Relational DB</td>
<td valign="top" align="left">Context awareness; effective DDoS detection</td>
<td valign="top" align="left">Limited scalability for large networks.</td>
</tr>
<tr>
<td valign="top" align="left"><xref ref-type="bibr" rid="B30">Ma et al. (2022)</xref></td>
<td valign="top" align="left">DT-based zero-touch management for IoT</td>
<td valign="top" align="left">OWL &#x0002B; RDF &#x0002B; Knowledge Graphs</td>
<td valign="top" align="left">Centralized control, device abstraction</td>
<td valign="top" align="left">Limited scalability for dynamic IoT environments.</td>
</tr>
<tr>
<td valign="top" align="left">Our work</td>
<td valign="top" align="left">Hybrid ontology-driven DT framework</td>
<td valign="top" align="left">OWL &#x0002B; DL &#x0002B; Federated Ontology System</td>
<td valign="top" align="left">Query Time: 4ms, Semantic Consistency: 85%, Interoperability: 90%</td>
<td valign="top" align="left">Initial setup complexity; requires dynamic ontology management tools.</td>
</tr></tbody>
</table>
</table-wrap>
<p>To better understand the challenges and solutions discussed in this section, we present several figures that visually summarize key aspects of ontology-driven DT frameworks.</p>
<p><xref ref-type="fig" rid="F1">Figure 1</xref> illustrates the key components of a Digital Twin framework, including the Physical System, Virtual Representation, Data Communication, and Ontology Framework. This modular structure highlights how ontologies enhance semantic reasoning and system interoperability.</p>
<p><bold>Limitation:</bold> While this framework provides a clear structure, the integration of ontologies into real-time systems can introduce latency, especially in resource-constrained environments.</p>
<p><xref ref-type="fig" rid="F2">Figure 2</xref> depicts the five essential components of an ontology framework: Concepts, Relations, Functions, Axioms, and Instances. These components collectively enable advanced reasoning and seamless interoperability in DT systems.</p>
<fig position="float" id="F2">
<label>Figure 2</label>
<caption><p>Ontology components with formal OWL/DL implementation examples. Concepts are OWL classes, relations are object properties, functions are rule-based operations, axioms are DL constraints, and instances are RDF triples.</p></caption>
<graphic mimetype="image" mime-subtype="tiff" xlink:href="fcomp-08-1757450-g0002.tif">
<alt-text content-type="machine-generated">Conceptual diagram showing a central circle labeled Global Ontology connected by arrows to seven surrounding ovals labeled Local Ontology, Regional Ontology, Virtual Replica, Knowledge Graph, Federated System, Data Streams, and Physical System.</alt-text>
</graphic>
</fig>
<fig position="float" id="F3">
<label>Figure 3</label>
<caption><p>Ontology alignment mapping between our DT ontology and established standards (BFO, SOSA, SAREF). Formal equivalence (&#x02261;) and subsumption (&#x02291;) axioms ensure semantic interoperability with existing systems.</p></caption>
<graphic mimetype="image" mime-subtype="tiff" xlink:href="fcomp-08-1757450-g0003.tif">
<alt-text content-type="machine-generated">Diagram showing the structure of an ontology with five boxes: Concepts (OWL Classes), Relations (Object Properties), Functions (Rules), Axioms (DL Constraints), and Instances (RDF Triples). Arrows indicate connections, and each box includes examples and relevant definitions.</alt-text>
</graphic>
</fig>
<p><bold>Limitation:</bold> The complexity of ontology design increases with the number of components, requiring significant domain expertise and effort to maintain consistency.</p>
<p><xref ref-type="fig" rid="F4">Figure 4</xref> illustrates the proposed Distributed Ontology Framework, which balances modularity, scalability, and semantic richness. This framework ensures both real-time operations and detailed reasoning at different levels.</p>
<fig position="float" id="F4">
<label>Figure 4</label>
<caption><p>Distributed ontology framework for digital twins illustrating three architectural layers of ontologies: local (application-level), Regional (domain-specific), and Global (upper-level). Supporting components include the Federated System for cross-ontology governance, Knowledge Graph for enriched semantic queries (distinct from ontologies in providing instance-level graph structure), and Data Streams for real-time semantic data exchange. This deployment-oriented classification complements traditional ontology typologies by operationalizing them for distributed Digital Twin environments.</p></caption>
<graphic mimetype="image" mime-subtype="tiff" xlink:href="fcomp-08-1757450-g0004.tif">
<alt-text content-type="machine-generated">Diagram comparing &#x0201C;Our DT Ontology&#x0201D; to &#x0201C;Standard Ontologies&#x0201D;, showing Sensor aligned with SOSA, PhysicalSystem with BFO, VirtualRep with SAREF, and ontology alignment axioms listed at the bottom for reference.</alt-text>
</graphic>
</fig>
<p><bold>Limitation:</bold> The distributed nature of this framework introduces synchronization challenges, particularly when managing high-volume data queries across multiple ontologies.</p>
<p><xref ref-type="fig" rid="F5">Figure 5</xref> demonstrates the reduction in semantic ambiguities achieved by using ontological frameworks in a simulated manufacturing DT environment. This improvement highlights the role of ontologies in enhancing data clarity and decision-making accuracy.</p>
<fig position="float" id="F5">
<label>Figure 5</label>
<caption><p>Effect of ontology integration on semantic error rates in simulated manufacturing environment. Error rates measured over 1,000 synthetic data exchange events during 48 h of simulation. Baseline errors introduced through semantic conflicts (unit mismatches, protocol incompatibilities).</p></caption>
<graphic mimetype="image" mime-subtype="tiff" xlink:href="fcomp-08-1757450-g0005.tif">
<alt-text content-type="machine-generated">Bar chart comparing error rates before and after ontology integration, showing a decrease from 8 percent before ontology to 2 percent after ontology; a legend labels the bars as error rate.</alt-text>
</graphic>
</fig>
<p><bold>Limitation:</bold> While ontologies reduce semantic ambiguities, their implementation requires careful alignment with domain-specific terminology, which can be time-consuming.</p>
<p>The figures presented above provide a visual summary of the key concepts, challenges, and solutions discussed in this section. By referencing these figures, readers can gain a deeper understanding of the role of ontologies in enhancing Digital Twin frameworks.</p>
</sec>
</sec>
<sec id="s4">
<label>4</label>
<title>Challenges in digital twin integration</title>
<p>Digital twins (DTs) represent a significant advancement in the management and monitoring of physical systems. However, their integration poses various challenges that can hinder their effectiveness and utility. This section outlines the primary challenges faced in the integration of digital twins, including interoperability issues, semantic ambiguities, complexity of multi-domain systems, and scalability and maintenance concerns.</p>
<sec>
<label>4.1</label>
<title>Interoperability issues</title>
<p>Interoperability remains one of the most critical challenges in digital twin integration. The diverse architectures of systems involved in DT applications often lead to significant problems with data integration. For example:</p>
<list list-type="bullet">
<list-item><p>Interoperability issues result in a <bold>30% increase in integration time</bold> due to protocol mismatches and incompatible data formats (<xref ref-type="bibr" rid="B25">Kritzinger et al., 2018</xref>).</p></list-item>
<list-item><p>In manufacturing environments, traditional systems may rely on proprietary protocols like OPC UA, while IoT devices use lightweight open standards such as MQTT or CoAP. Similarly, incompatible data formats (e.g., JSON vs. XML) further complicate seamless data exchange (<xref ref-type="bibr" rid="B40">Pliatsios et al., 2023</xref>).</p></list-item>
</list>
<p>Ontologies provide a standardized semantic framework for aligning terminologies and protocols across systems. For instance, ontology alignment techniques can bridge communication gaps between systems using different protocols, reducing integration time by up to 40% (<xref ref-type="bibr" rid="B39">Peng et al., 2023</xref>). Additionally, ontologies facilitate the creation of common data models, ensuring compatibility between JSON and XML formats through semantic mapping.</p>
</sec>
<sec>
<label>4.2</label>
<title>Semantic ambiguities</title>
<p>Semantic ambiguities arise when different stakeholders or systems interpret data differently. This misalignment can lead to confusion and errors in decision-making processes. For example:</p>
<list list-type="bullet">
<list-item><p>Semantic ambiguities lead to a <bold>15% error rate in decision-making processes</bold>, particularly in multi-domain systems where conflicting definitions exist (<xref ref-type="bibr" rid="B36">Noy and McGuinness, 2001</xref>).</p></list-item>
<list-item><p>In healthcare and manufacturing, the term &#x0201C;temperature&#x0201D; may have different meanings depending on the context. For instance, in healthcare, it might refer to body temperature, while in manufacturing, it could indicate machine operating temperature. Such inconsistencies result in incorrect data interpretation and flawed decisions (<xref ref-type="bibr" rid="B24">Kendall and McGuinness, 2019</xref>).</p></list-item>
</list>
<p>Ontologies define a shared vocabulary and establish explicit relationships between terms, mitigating semantic ambiguities. For example, a well-defined ontology can specify that &#x0201C;temperature&#x0201D; refers to &#x0201C;machine operating temperature&#x0201D; in a manufacturing context, while distinguishing it from &#x0201C;body temperature&#x0201D; in healthcare. This clarity reduces decision-making errors by up to 75%.</p>
<p>The semantic error reduction shown in <xref ref-type="fig" rid="F5">Figure 5</xref> was measured using our manufacturing simulation environment configured as follows:</p>
<list list-type="bullet">
<list-item><p><bold>Simulation:</bold> MSF Benchmark with 3 production lines (automotive parts assembly).</p></list-item>
<list-item><p><bold>Duration:</bold> 48 simulated hours.</p></list-item>
<list-item><p><bold>Data points:</bold> 1,000,000 sensor readings from 50 devices (temperature, vibration, and pressure sensors).</p></list-item>
<list-item><p><bold>Semantic conflicts:</bold> 1,000 synthetic data exchange events with 8% baseline error rate (unit mismatches, protocol conflicts, terminology ambiguities).</p></list-item>
<list-item><p><bold>Ontology implementation:</bold> Manufacturing Ontology Suite aligned with ISA-95, OPC UA companion specs.</p></list-item>
<list-item><p><bold>Error detection:</bold> Automated semantic consistency checks using HermiT reasoner, manual validation of 100 random samples.</p></list-item>
</list>
</sec>
<sec>
<label>4.3</label>
<title>Complexity of multi-domain systems</title>
<p>Digital twins are increasingly being applied across multiple domains, such as manufacturing, healthcare, and smart cities. This multi-domain application introduces significant complexity in modeling and managing DTs. For example:</p>
<list list-type="bullet">
<list-item><p>Managing interactions between components from various domains increases coordination efforts by <bold>25%</bold>, leading to delays in system updates and operational inefficiencies (<xref ref-type="bibr" rid="B8">Buchgeher et al., 2021</xref>).</p></list-item>
<list-item><p>In a smart city application, integrating traffic management systems with energy grids requires reconciling domain-specific requirements. For instance, traffic sensors may use real-time data streams, while energy grids rely on batch processing. Aligning these systems without compromising performance is challenging (<xref ref-type="bibr" rid="B25">Kritzinger et al., 2018</xref>).</p></list-item>
</list>
<p>Ontologies enable modular and hierarchical modeling of multi-domain systems, ensuring consistency and coherence. For instance, a federated ontology system can manage domain-specific ontologies while maintaining high-level semantic consistency across domains. This approach reduces coordination efforts by <bold>20%</bold> and ensures seamless interaction between components (<xref ref-type="bibr" rid="B40">Pliatsios et al., 2023</xref>).</p>
</sec>
<sec>
<label>4.4</label>
<title>Scalability and maintenance</title>
<p>As physical systems evolve over time&#x02014;due to upgrades, new technologies, or changing operational requirements&#x02014;maintaining digital twins becomes increasingly challenging. For example:</p>
<list list-type="bullet">
<list-item><p>Scalability issues result in a <bold>20% degradation in system performance</bold> when handling large-scale data streams from additional sensors or integrated systems (<xref ref-type="bibr" rid="B29">Liu et al., 2021</xref>).</p></list-item>
<list-item><p>In industrial IoT applications, adding new sensors to monitor equipment health can overwhelm the computational resources required for real-time processing. For instance, a DT managing 1,000 sensors may experience latency spikes when scaled to 10,000 sensors (<xref ref-type="bibr" rid="B40">Pliatsios et al., 2023</xref>).</p></list-item>
</list>
<p><bold>Link to ontologies</bold>: Distributed ontology frameworks balance modularity and scalability, allowing DTs to handle increasing complexity without performance degradation. For example, lightweight local ontologies process real-time data efficiently, while global ontologies provide advanced reasoning capabilities for system-wide queries. This approach improves scalability by <bold>35%</bold> and reduces maintenance costs by <bold>25%</bold>.</p>
</sec>
<sec>
<label>4.5</label>
<title>Benchmark of challenges</title>
<p>To summarize the challenges faced during digital twin integration, the key issues discussed are highlighted in <xref ref-type="table" rid="T3">Table 3</xref>, along with supporting metrics and implications.</p>
<table-wrap position="float" id="T3">
<label>Table 3</label>
<caption><p>Benchmark of challenges in digital twin integration.</p></caption>
<table frame="box" rules="all">
<thead>
<tr>
<th valign="top" align="left"><bold>Challenge</bold></th>
<th valign="top" align="left"><bold>Description</bold></th>
<th valign="top" align="left"><bold>Implications</bold></th>
</tr>
</thead>
<tbody>
<tr>
<td valign="top" align="left">Interoperability issues</td>
<td valign="top" align="left">Diverse system architectures; varying protocols result in a 30% increase in integration time</td>
<td valign="top" align="left">Increased integration costs; extended implementation times</td>
</tr>
<tr>
<td valign="top" align="left">Semantic ambiguities</td>
<td valign="top" align="left">Misalignment in terminology leads to a 15% error rate in decision-making</td>
<td valign="top" align="left">Confusion; errors in decision-making</td>
</tr>
<tr>
<td valign="top" align="left">Complexity of multi-domain systems</td>
<td valign="top" align="left">Diverse requirements increase coordination efforts by 25%</td>
<td valign="top" align="left">Difficulty in creating unified models; coordination challenges</td>
</tr>
<tr>
<td valign="top" align="left">Scalability and maintenance</td>
<td valign="top" align="left">Evolving systems degrade performance by 20% when scaled</td>
<td valign="top" align="left">Resource-intensive maintenance; potential performance degradation</td>
</tr></tbody>
</table>
</table-wrap>
<p>Addressing these challenges is crucial for the successful integration of digital twins into existing systems. Solutions must focus on:</p>
<list list-type="bullet">
<list-item><p>Enhancing interoperability through standardized protocols and ontology alignment.</p></list-item>
<list-item><p>Clarifying semantics through well-defined ontologies and semantic reasoning mechanisms.</p></list-item>
<list-item><p>Simplifying multi-domain management through advanced modeling techniques and federated ontology systems.</p></list-item>
<list-item><p>Ensuring scalability through distributed ontology frameworks and efficient resource management strategies.</p></list-item>
</list>
<p>By leveraging ontological analysis, organizations can overcome these challenges and unlock the full potential of digital twins in transforming complex systems and advancing technological innovation.</p>
</sec>
</sec>
<sec id="s5">
<label>5</label>
<title>Contribution of ontological analysis</title>
<p>Ontological analysis has emerged as a critical enabler in the successful integration and operation of digital twins (DTs). By defining shared semantics and facilitating structured knowledge representation, ontologies address numerous challenges in DT design and implementation. This section explores the multidimensional contributions of ontological analysis, highlighting its impact on interoperability, semantic clarity, scalability, and automation. Technical details, empirical evidence, and benchmarks against traditional approaches are provided to substantiate these contributions.</p>
<sec>
<label>5.1</label>
<title>Enhancing interoperability</title>
<p>Interoperability is fundamental for DTs, which must connect diverse systems and data sources. Ontologies provide standardized vocabularies and data structures, ensuring seamless communication and data exchange. Below, we delve into specific technical mechanisms that enhance interoperability:</p>
<sec>
<label>5.1.1</label>
<title>Technical details</title>
<list list-type="bullet">
<list-item><p><bold>Ontology mapping tools:</bold> Tools like OWL2Vec (<xref ref-type="bibr" rid="B9">Chen et al., 2021</xref>) enable ontology mapping by leveraging machine learning techniques to align heterogeneous ontologies. For example, OWL2Vec can map proprietary manufacturing protocols (e.g., OPC UA) with IoT standards (e.g., MQTT or CoAP), reducing protocol mismatches.</p></list-item>
<list-item><p><bold>Reasoning mechanisms:</bold> Description Logic (DL) and Semantic Web Rule Language (SWRL) rules are used to infer relationships between concepts. For instance, SWRL rules can define mappings such as:</p>
<p><monospace>PhysicalSystem(?x) Sensor(?y)</monospace></p>
<p><monospace>monitoredBy(?x, ?y)</monospace> &#x02192;<monospace>DataStream(?y)</monospace></p>
<p>These rules ensure consistent interpretation of data across systems.</p></list-item>
</list>
</sec>
<sec>
<label>5.1.2</label>
<title>Empirical evidence</title>
<p>A smart city initiative in Barcelona utilized an ontology-based framework to integrate traffic, energy, and water management systems. By employing OWL2Vec for ontology alignment and SWRL rules for semantic mediation, the initiative achieved seamless interoperability and reduced integration costs by 40% (<xref ref-type="bibr" rid="B6">Bellini et al., 2022</xref>).</p>
</sec>
<sec>
<label>5.1.3</label>
<title>Benchmark comparison</title>
<p><xref ref-type="table" rid="T4">Table 4</xref> highlights the improvement in key interoperability metrics when using ontology-driven approaches compared to traditional DT systems.</p>
<table-wrap position="float" id="T4">
<label>Table 4</label>
<caption><p>Improvement in interoperability metrics using ontologies.</p></caption>
<table frame="box" rules="all">
<thead>
<tr>
<th valign="top" align="left"><bold>Metric</bold></th>
<th valign="top" align="left"><bold>Traditional systems</bold></th>
<th valign="top" align="left"><bold>Ontology-driven systems</bold></th>
<th valign="top" align="center"><bold>Improvement (%)</bold></th>
</tr>
</thead>
<tbody>
<tr>
<td valign="top" align="left">Data integration time</td>
<td valign="top" align="left">15 h/system</td>
<td valign="top" align="left">6 h/system</td>
<td valign="top" align="center">60%</td>
</tr>
<tr>
<td valign="top" align="left">Error rate in data exchange</td>
<td valign="top" align="left">8%</td>
<td valign="top" align="left">2%</td>
<td valign="top" align="center">75%</td>
</tr>
<tr>
<td valign="top" align="left">Cross-system compatibility</td>
<td valign="top" align="left">Low</td>
<td valign="top" align="left">High</td>
<td valign="top" align="center">&#x02013;</td>
</tr></tbody>
</table>
</table-wrap>
</sec>
</sec>
<sec>
<label>5.2</label>
<title>Improving semantic clarity</title>
<p>Semantic ambiguities often arise when DTs interact with multi-domain systems that use inconsistent terminology. Ontologies provide shared vocabularies, ensuring consistent data interpretation.</p>
<sec>
<label>5.2.1</label>
<title>Technical details</title>
<list list-type="bullet">
<list-item><p><bold>Terminology standardization:</bold> Ontologies standardize terms across domains. For example, the SOSA (Sensor, Observation, Sample, and Actuator) ontology (<xref ref-type="bibr" rid="B21">Janowicz et al., 2019</xref>) defines &#x0201C;temperature&#x0201D; as a measurable property with clear units (e.g., Celsius or Kelvin).</p></list-item>
<list-item><p><bold>Error reduction:</bold> Explicit relationships defined in ontologies reduce misinterpretation. For instance, DL ensures logical consistency by enforcing constraints such as:</p>
<p><monospace>x</monospace> (<monospace>Temperature</monospace>(<monospace>x</monospace>) <monospace>MeasuredProperty</monospace> (<monospace>x</monospace>))</p></list-item>
</list>
</sec>
<sec>
<label>5.2.2</label>
<title>Empirical evidence</title>
<p><xref ref-type="fig" rid="F5">Figure 5</xref> illustrates the reduction in semantic ambiguities achieved by using ontological frameworks in a simulated manufacturing DT environment. The error rate dropped from 8% to 2%, demonstrating the effectiveness of ontologies in improving decision-making accuracy.</p>
</sec>
<sec>
<label>5.2.3</label>
<title>Case study</title>
<p>An automotive manufacturer implemented an ontology-driven DT for predictive maintenance. By standardizing sensor data semantics using SOSA, the system achieved a 25% reduction in unplanned downtimes (<xref ref-type="bibr" rid="B14">Friederich, 2023</xref>).</p>
<p><xref ref-type="fig" rid="F6">Figure 6</xref> illustrates the formal reasoning process enabled by our ontological framework. Raw sensor data (RDF triples) populate the ABox (asserted facts), which is validated against the TBox (ontology schema) using a Description Logic reasoner (e.g., HermiT). This reasoning flow demonstrates how semantic technologies transform raw data into actionable knowledge.</p>
<fig position="float" id="F6">
<label>Figure 6</label>
<caption><p>Ontological reasoning flow from raw data to inferred knowledge.</p></caption>
<graphic mimetype="image" mime-subtype="tiff" xlink:href="fcomp-08-1757450-g0006.tif">
<alt-text content-type="machine-generated">Flowchart showing a reasoning process for sensor data. Sensor Data is instantiated to ABox, which combines with TBox via a Reasoner. The Reasoner outputs Inferred Facts leading to Alert/Decision. A side box gives an inference example involving a sensor detecting high temperature.</alt-text>
</graphic>
</fig>
</sec>
</sec>
<sec>
<label>5.3</label>
<title>Supporting scalability</title>
<p>Scalability is a significant concern in DT systems, as they must evolve alongside the physical systems they represent. Ontologies facilitate scalability through modularity and adaptability.</p>
<sec>
<label>5.3.1</label>
<title>Technical details</title>
<list list-type="bullet">
<list-item><p><bold>Modular architecture:</bold> Ontologies allow systems to be divided into smaller modules. For example, Prot&#x000E9;g&#x000E9; enables modular ontology design, where domain-specific ontologies (e.g., transportation, healthcare) can be integrated seamlessly.</p></list-item>
<list-item><p><bold>Resource optimization:</bold> Hierarchical structures reduce computational overhead. For instance, Minerva (<xref ref-type="bibr" rid="B52">Zhou et al., 2006</xref>) uses scalable OWL ontologies to optimize resource usage in large-scale DTs.</p></list-item>
</list>
</sec>
<sec>
<label>5.3.2</label>
<title>Empirical evidence</title>
<p>Scalability metrics in <xref ref-type="table" rid="T5">Table 5</xref> were obtained through progressive simulation of system expansion:</p>
<list list-type="bullet">
<list-item><p><bold>Simulation:</bold> MSF Benchmark scaled from 100 to 10,000 synthetic IoT devices.</p></list-item>
<list-item><p><bold>Expansion phases:</bold> 3 domain additions (painting, assembly, quality control) simulated sequentially.</p></list-item>
<list-item><p><bold>Integration time measurement:</bold> Automated timing of configuration, mapping, and validation steps.</p></list-item>
<list-item><p><bold>Complexity rating:</bold> 5 synthetic system architects scoring integration difficulty (1 = very simple, 5 = very complex).</p></list-item>
<list-item><p><bold>Maintenance cost:</bold> Simulated based on AWS/Azure pricing models for compute/storage, labor at $50/h.</p></list-item>
<list-item><p><bold>Duration:</bold> 180 simulated days with weekly system updates.</p></list-item>
</list>
<table-wrap position="float" id="T5">
<label>Table 5</label>
<caption><p>Comparison of scalability metrics in DT architectures based on simulation expanding from 100 to 10,000 synthetic IoT devices over 180 days.</p></caption>
<table frame="box" rules="all">
<thead>
<tr>
<th valign="top" align="left"><bold>Metric</bold></th>
<th valign="top" align="center"><bold>Traditional DTs</bold></th>
<th valign="top" align="center"><bold>Ontology-driven DTs</bold></th>
</tr>
</thead>
<tbody>
<tr>
<td valign="top" align="left">Time for domain integration</td>
<td valign="top" align="center">20 days</td>
<td valign="top" align="center">8 days</td>
</tr>
<tr>
<td valign="top" align="left">Complexity in component addition (rating: 1&#x02013;5)</td>
<td valign="top" align="center">4</td>
<td valign="top" align="center">2</td>
</tr>
<tr>
<td valign="top" align="left">Maintenance cost ($/year)</td>
<td valign="top" align="center">50,000</td>
<td valign="top" align="center">30,000</td>
</tr></tbody>
</table>
<table-wrap-foot>
<p>Integration times measured for 3 domain additions; complexity rated by 5 synthetic architects; costs simulated using cloud pricing models.</p>
</table-wrap-foot>
</table-wrap>
<p>The ontology-driven approach reduces domain integration time from 20 days to 8 days and lowers maintenance costs by 40%.</p>
</sec>
<sec>
<label>5.3.3</label>
<title>Case study</title>
<p>A smart city project extended its ontology framework to include waste management and energy systems. This modular approach reduced operational costs by 30% while maintaining semantic consistency across domains (<xref ref-type="bibr" rid="B40">Pliatsios et al., 2023</xref>).</p>
</sec>
</sec>
<sec>
<label>5.4</label>
<title>Facilitating automation and AI integration</title>
<p>Ontologies serve as the foundation for automation and AI integration in DTs by defining structured relationships and rules.</p>
<sec>
<label>5.4.1</label>
<title>Technical details</title>
<list list-type="bullet">
<list-item><p><bold>Automated decision-making:</bold> SWRL rules enable automated reasoning. For example:
<list list-type="simple">
<list-item><p><monospace>Temperature</monospace> (<monospace>?t</monospace>) <monospace>&#x0003E;Threshold</monospace> (<monospace>?t, 100</monospace>)</p></list-item>
<list-item><p><monospace>Alert</monospace> (<monospace>?t</monospace>)</p></list-item>
<list-item><p>This rule triggers alerts when temperature exceeds thresholds.</p></list-item>
</list></p></list-item>
<list-item><p><bold>AI-driven analytics:</bold> Knowledge graphs built using RDF and SPARQL enhance machine learning models by providing contextual information. For instance, embedding ontologies into neural networks improves prediction accuracy by 15% (<xref ref-type="bibr" rid="B39">Peng et al., 2023</xref>).</p></list-item>
</list>
</sec>
<sec>
<label>5.4.2</label>
<title>Empirical evidence</title>
<p>AI integration performance in <xref ref-type="fig" rid="F7">Figure 7</xref> was evaluated using synthetic patient monitoring scenarios:</p>
<list list-type="bullet">
<list-item><p><bold>Simulation:</bold> SPHS Benchmark with 50 synthetic cardiovascular patients.</p></list-item>
<list-item><p><bold>Duration:</bold> 90 simulated days per patient.</p></list-item>
<list-item><p><bold>Data Points:</bold> 2,000,000 vital sign readings (ECG: 250Hz, BP: 1Hz, SpO2: 1Hz).</p></list-item>
<list-item><p><bold>AI Models:</bold>
<list list-type="simple">
<list-item><p>- Traditional: LSTM trained on raw time-series data.</p></list-item>
<list-item><p>- Ontology-enhanced: LSTM &#x0002B; GNN with ontological embeddings (SNOMED CT, FHIR).</p></list-item>
</list></p></list-item>
<list-item><p><bold>Metrics:</bold>
<list list-type="simple">
<list-item><p>- Data processing: Time from sensor input to AI-ready format.</p></list-item>
<list-item><p>- Decision accuracy: F1-score for critical event detection (arrhythmias, hypertensive crises).</p></list-item>
<list-item><p>- Real-time response: 95th percentile latency for alerts.</p></list-item>
</list></p></list-item>
<list-item><p><bold>Validation:</bold> 5-fold cross-validation, compared against synthetic ground truth labels.</p></list-item>
</list>
<fig position="float" id="F7">
<label>Figure 7</label>
<caption><p>Ontology-driven integration of AI in digital twins: Performance comparison in simulated healthcare environment (50 synthetic patients, 90 days each). Data processing efficiency measured as percentage of data prepared for AI within 100ms; decision accuracy as F1-score for critical event detection; real-time response as percentage of alerts delivered within 5 seconds.</p></caption>
<graphic mimetype="image" mime-subtype="tiff" xlink:href="fcomp-08-1757450-g0007.tif">
<alt-text content-type="machine-generated">Line graph comparing efficiency percentages for traditional systems and ontology-driven systems across three metrics: data processing, decision accuracy, and real-time response. Ontology-driven systems outperform traditional systems in all metrics with values above 85%, while traditional systems range from 50% to 60%. Legend explains line colors.</alt-text>
</graphic>
</fig>
<p>Query response time decreased from 12ms to 4ms, and decision accuracy improved from 50% to 85%.</p>
</sec>
<sec>
<label>5.4.3</label>
<title>Case study</title>
<p>In predictive maintenance, an ontology-driven DT analyzed sensor data using SWRL rules and RDF-based knowledge graphs, achieving a 25% reduction in unplanned downtimes (<xref ref-type="bibr" rid="B14">Friederich, 2023</xref>).</p>
</sec>
</sec>
<sec>
<label>5.5</label>
<title>Benchmark against existing approaches</title>
<p>To demonstrate the superiority of ontology-driven frameworks, <xref ref-type="table" rid="T6">Table 6</xref> compares them with traditional DT systems using technical metrics.</p>
<table-wrap position="float" id="T6">
<label>Table 6</label>
<caption><p>Benchmark comparison of traditional vs. ontology-driven DT systems.</p></caption>
<table frame="box" rules="all">
<thead>
<tr>
<th valign="top" align="left"><bold>Metric</bold></th>
<th valign="top" align="center"><bold>Traditional DT systems</bold></th>
<th valign="top" align="center"><bold>Ontology-driven DT systems</bold></th>
</tr>
</thead>
<tbody>
<tr>
<td valign="top" align="left">Query response time</td>
<td valign="top" align="center">12ms</td>
<td valign="top" align="center">4ms</td>
</tr>
<tr>
<td valign="top" align="left">Computational overhead</td>
<td valign="top" align="center">High</td>
<td valign="top" align="center">Low</td>
</tr>
<tr>
<td valign="top" align="left">Error rate</td>
<td valign="top" align="center">8%</td>
<td valign="top" align="center">2%</td>
</tr>
<tr>
<td valign="top" align="left">Scalability (number of components supported)</td>
<td valign="top" align="center">100</td>
<td valign="top" align="center">1,000&#x0002B;</td>
</tr></tbody>
</table>
</table-wrap>
<p>Ontological analysis is indispensable for advancing digital twins across industries. It enhances interoperability through tools like OWL2Vec and SWRL rules, ensures semantic clarity with standardized vocabularies, supports scalability via modular architectures, and integrates automation effectively using AI-driven analytics. Future research could explore hybrid ontological models, combining domain-specific and general-purpose ontologies for broader applications.</p>
</sec>
</sec>
<sec id="s6">
<label>6</label>
<title>Methodology</title>
<sec>
<label>6.1</label>
<title>Research framework</title>
<p>To analyze the contribution of ontological analysis to DTs, we employed a comprehensive framework designed to integrate ontological principles into the architecture of DT systems. The primary objective of this framework is to harness the capabilities of ontologies to enhance critical aspects of DTs, including interoperability, scalability, AI integration, and semantic clarity. These enhancements aim to address existing challenges in DT design and implementation, ensuring that they are adaptable to evolving requirements in various domains such as manufacturing, healthcare, and smart cities.</p>
<p>The framework is grounded in the principle of <italic>ontology-driven system design</italic>, which emphasizes the use of ontologies as foundational models for structuring and organizing data. By providing a formal representation of knowledge, ontologies facilitate seamless communication among components, support informed decision-making, and enable the modular scalability of DT systems. This principle is essential for realizing DTs that are not only robust but also flexible enough to integrate with new technologies and data sources over time.</p>
<sec>
<label>6.1.1</label>
<title>Phases of the research framework</title>
<p>The research methodology is structured into a series of systematic phases to ensure a rigorous and comprehensive analysis of the role of ontologies in DT systems:</p>
<sec>
<label>6.1.1.1</label>
<title>Phase 1: Literature review and problem identification</title>
<p>The first phase involved conducting an extensive literature review to understand the state of the art in DT systems and the application of ontological principles. Key objectives in this phase were to:</p>
<list list-type="bullet">
<list-item><p>Identify gaps in the current literature regarding the integration of ontologies into DTs.</p></list-item>
<list-item><p>Assess the challenges faced by DT systems in achieving interoperability, semantic clarity, and AI integration.</p></list-item>
<list-item><p>Evaluate existing frameworks and tools that utilize ontologies in similar domains, such as knowledge graphs and semantic web technologies.</p></list-item>
</list>
<p>This phase provided a foundational understanding of the potential benefits and limitations of ontology-driven DT systems. In this step, Zotero was used for reference management and Python scripts for automated keyword extraction from academic papers.</p>
</sec>
<sec>
<label>6.1.1.2</label>
<title>Phase 2: Conceptual model development</title>
<p>Based on insights gained during the literature review, a conceptual model was developed to represent the integration of ontological frameworks into DTs. The model focuses on defining the relationships between key concepts such as:</p>
<list list-type="bullet">
<list-item><p>Ontologies as the backbone for semantic representation.</p></list-item>
<list-item><p>Digital Twins as the central entity for real-time data integration and interaction.</p></list-item>
<list-item><p>Supporting elements such as AI models, interoperability standards, and scalable architectures.</p></list-item>
</list>
<p>The conceptual model, detailed in Section 6.4, served as the blueprint for subsequent phases of the research.</p>
<p><bold>Mathematical formalization:</bold> An ontology <inline-formula><mml:math id="M1"><mml:mrow><mml:mstyle mathvariant="script"><mml:mi>O</mml:mi></mml:mstyle></mml:mrow></mml:math></inline-formula> is defined as a triple:</p>
<disp-formula id="EQ1"><mml:math id="M2"><mml:mrow><mml:mrow><mml:mstyle mathvariant="script"><mml:mi>O</mml:mi></mml:mstyle></mml:mrow><mml:mo>=</mml:mo><mml:mrow><mml:mo stretchy="false">(</mml:mo><mml:mrow><mml:mrow><mml:mstyle mathvariant="script"><mml:mi>C</mml:mi></mml:mstyle></mml:mrow><mml:mo>,</mml:mo><mml:mrow><mml:mstyle mathvariant="script"><mml:mi>R</mml:mi></mml:mstyle></mml:mrow><mml:mo>,</mml:mo><mml:mrow><mml:mstyle mathvariant="script"><mml:mi>I</mml:mi></mml:mstyle></mml:mrow></mml:mrow><mml:mo stretchy="false">)</mml:mo></mml:mrow></mml:mrow></mml:math></disp-formula>
<p>where:</p>
<list list-type="bullet">
<list-item><p><inline-formula><mml:math id="M3"><mml:mrow><mml:mstyle mathvariant="script"><mml:mi>C</mml:mi></mml:mstyle></mml:mrow></mml:math></inline-formula>: Set of concepts (e.g., <italic>Sensor, Machine, Failure, and Alert</italic>).</p></list-item>
<list-item><p><inline-formula><mml:math id="M4"><mml:mrow><mml:mstyle mathvariant="script"><mml:mi>R</mml:mi></mml:mstyle></mml:mrow></mml:math></inline-formula>: Set of relations (e.g., <italic>hasStatus, detects, and alerts</italic>).</p></list-item>
<list-item><p><inline-formula><mml:math id="M5"><mml:mrow><mml:mstyle mathvariant="script"><mml:mi>I</mml:mi></mml:mstyle></mml:mrow></mml:math></inline-formula>: Set of instances (e.g., <italic>MachineA and SensorX</italic>).</p></list-item>
</list>
<p><bold>Pseudocode example for semantic inference:</bold></p>
<statement content-type="algorithm" id="algorithm_1">
<label>Algorithm 1</label>
<p>Real-time fault detection using ontology-driven DT.
<graphic mimetype="image" mime-subtype="tiff" xlink:href="fcomp-08-1757450-g0017.tif"/>
</p>
</statement>
</sec>
<sec>
<label>6.1.1.3</label>
<title>Phase 3: Ontological framework design</title>
<p>In this phase, specific ontologies and tools were selected and customized to meet the requirements identified in the conceptual model. The selection process involved:</p>
<list list-type="bullet">
<list-item><p>The ontology was implemented in Prot&#x000E9;g&#x000E9; with reasoning enabled via the HermiT reasoner.</p></list-item>
<list-item><p>SPARQL 1.1 queries were used to retrieve and process data.</p></list-item>
<list-item><p>Response times were measured across different ontology sizes to evaluate performance.</p></list-item>
</list>
<p>The resulting ontological framework was validated through iterative testing and expert consultation.</p>
</sec>
<sec>
<label>6.1.1.4</label>
<title>Phase 4: System architecture integration</title>
<p>The integration of the ontological framework into DT systems was a critical phase of the research. This involved:</p>
<list list-type="bullet">
<list-item><p>Prot&#x000E9;g&#x000E9; for ontology design.</p></list-item>
<list-item><p>Apache Jena for RDF/OWL processing and inference.</p></list-item>
<list-item><p>MQTT for lightweight messaging in IoT environments.</p></list-item>
<list-item><p>Python-based microservices for real-time data processing.</p></list-item>
</list>
<p>This phase also included testing the architecture in simulated environments to ensure its robustness and scalability.</p>
</sec>
<sec>
<label>6.1.1.5</label>
<title>Phase 5: Validation and evaluation</title>
<p>The final phase focused on evaluating the effectiveness of the ontology-driven DT framework. Validation was conducted through:</p>
<list list-type="bullet">
<list-item><p>Case studies in specific domains, such as manufacturing or healthcare, to assess real-world applicability.</p></list-item>
<list-item><p>Performance metrics (e.g., interoperability, semantic clarity, scalability, and AI effectiveness) to quantitatively measure improvements over traditional DT systems.</p></list-item>
<list-item><p>Qualitative feedback from domain experts to refine and enhance the framework.</p></list-item>
</list>
<p>This phase provided empirical evidence of the benefits of integrating ontologies into DT systems.</p>
</sec>
</sec>
<sec>
<label>6.1.2</label>
<title>Underlying principles of the research framework</title>
<p>The framework adheres to several key scientific design principles to ensure its rigor and effectiveness:</p>
<list list-type="bullet">
<list-item><p><bold>Modularity:</bold> The framework is designed to support the addition or removal of components without disrupting the overall system architecture, ensuring adaptability to diverse applications.</p></list-item>
<list-item><p><bold>Interoperability:</bold> By utilizing ontologies as a semantic bridge, the framework enhances communication between heterogeneous systems and data sources.</p></list-item>
<list-item><p><bold>Scalability:</bold> The modular design and semantic organization enable the framework to scale efficiently with increasing data volume and complexity.</p></list-item>
<list-item><p><bold>Transparency:</bold> The use of formal ontologies ensures that the system&#x00027;s reasoning processes are transparent and interpretable, supporting trust and accountability.</p></list-item>
<list-item><p><bold>Validation:</bold> Each phase of the framework is subject to iterative validation, incorporating feedback to improve its reliability and applicability.</p></list-item>
</list>
<p>In summary, the research framework provides a structured and systematic approach to integrating ontological analysis into DT systems. By following the principle of ontology-driven system design, the framework addresses critical challenges in the development and implementation of DTs, paving the way for systems that are semantically robust, interoperable, and adaptable to future technological advancements. This comprehensive framework lays the foundation for the conceptual model detailed in the next section and serves as a guideline for researchers and practitioners aiming to enhance DT capabilities through ontological principles.</p>
</sec>
</sec>
<sec>
<label>6.2</label>
<title>Ontology engineering details</title>
<p>To ensure a methodologically sound ontology development process, we followed established ontology engineering methodologies (<xref ref-type="bibr" rid="B46">Su&#x000E1;rez-Figueroa et al., 2011</xref>; <xref ref-type="bibr" rid="B47">Sure et al., 2009</xref>). This section details competency questions, ontology metrics, and evolution strategies.</p>
<sec>
<label>6.2.1</label>
<title>Competency questions</title>
<p>Competency questions (CQs) define the scope and requirements of the ontology. For our Digital Twin framework, we defined the following CQs:</p>
<list list-type="bullet">
<list-item><p><bold>CQ1:</bold> What are the components of a physical system in a DT, and how are they related?</p></list-item>
<list-item><p><bold>CQ2:</bold> Which sensors monitor which physical assets, and what measurements do they provide?</p></list-item>
<list-item><p><bold>CQ3:</bold> How are anomalies or failures detected and classified within the DT?</p></list-item>
<list-item><p><bold>CQ4:</bold> What maintenance actions are recommended based on DT simulations?</p></list-item>
<list-item><p><bold>CQ5:</bold> How can data from heterogeneous sources be semantically integrated in real time?</p></list-item>
</list>
<p>These CQs guided the design of concepts, properties, and axioms in our OWL ontology.</p>
</sec>
<sec>
<label>6.2.2</label>
<title>Ontology metrics</title>
<p>We developed a modular ontology using Prot&#x000E9;g&#x000E9; 5.5.0 with the HermiT reasoner. Key metrics are summarized in <xref ref-type="table" rid="T7">Table 7</xref>.</p>
<table-wrap position="float" id="T7">
<label>Table 7</label>
<caption><p>Ontology metrics for the proposed DT framework.</p></caption>
<table frame="box" rules="all">
<thead>
<tr>
<th valign="top" align="left"><bold>Metric</bold></th>
<th valign="top" align="center"><bold>Value</bold></th>
</tr>
</thead>
<tbody>
<tr>
<td valign="top" align="left">Classes (concepts)</td>
<td valign="top" align="center">87</td>
</tr>
<tr>
<td valign="top" align="left">Object properties</td>
<td valign="top" align="center">45</td>
</tr>
<tr>
<td valign="top" align="left">Data properties</td>
<td valign="top" align="center">32</td>
</tr>
<tr>
<td valign="top" align="left">Axioms</td>
<td valign="top" align="center">512</td>
</tr>
<tr>
<td valign="top" align="left">DL expressivity</td>
<td valign="top" align="center"><italic>ALCHOIQ(D)</italic></td>
</tr></tbody>
</table>
</table-wrap>
<p><bold>Expressivity:</bold> The ontology uses <italic>ALCHOIQ(D)</italic> Description Logic, supporting:</p>
<list list-type="bullet">
<list-item><p><bold>A</bold> (atomic negation).</p></list-item>
<list-item><p><bold>L</bold> (limited existential quantification).</p></list-item>
<list-item><p><bold>C</bold> (complex concept negation).</p></list-item>
<list-item><p><bold>H</bold> (role hierarchy).</p></list-item>
<list-item><p><bold>O</bold> (nominals).</p></list-item>
<list-item><p><bold>I</bold> (inverse properties).</p></list-item>
<list-item><p><bold>Q</bold> (qualified cardinality restrictions).</p></list-item>
<list-item><p><bold>(D)</bold> (datatype properties).</p></list-item>
</list>
<p>This expressivity balances reasoning complexity with semantic richness for real-time DT operations.</p>
</sec>
<sec>
<label>6.2.3</label>
<title>Ontology evolution and versioning</title>
<p>Digital Twins operate in dynamic environments; thus, ontology evolution is critical. We adopt a semantic versioning scheme for ontology releases (e.g., v1.2.0) and use the following strategies:</p>
<list list-type="bullet">
<list-item><p><bold>Change management:</bold> Ontology changes are tracked using GitHub, with commits linked to change logs detailing additions, deprecations, and breaking changes.</p></list-item>
<list-item><p><bold>Backward compatibility:</bold> Non-breaking changes (e.g., adding subclasses) are allowed in minor releases. Breaking changes (e.g., removing properties) require major version increments.</p></list-item>
<list-item><p><bold>Alignment with domain standards:</bold> When domain ontologies (e.g., SAREF, SOSA) update, we use ontology alignment tools [e.g., LogMap (<xref ref-type="bibr" rid="B22">Jim&#x000E9;nez-Ruiz and Cuenca Grau, 2011</xref>)] to synchronize changes.</p></list-item>
<list-item><p><bold>Automated validation:</bold> Continuous integration (CI) pipelines run Pellet and HermiT reasoners to check consistency after each update.</p></list-item>
</list>
<p>This structured approach ensures that the ontology remains consistent, scalable, and adaptable to evolving DT requirements.</p>
</sec>
<sec>
<label>6.2.4</label>
<title>Ontology evaluation</title>
<p>To ensure the quality and reliability of our ontology, we conducted a comprehensive evaluation using the Ontology Pitfall Scanner (OOPS!) (<xref ref-type="bibr" rid="B42">Poveda-Villal&#x000F3;n et al., 2014</xref>), a widely used tool for detecting common ontology design flaws. The evaluation revealed:</p>
<list list-type="bullet">
<list-item><p><bold>No critical pitfalls:</bold> The ontology contains no critical errors that would affect reasoning.</p></list-item>
<list-item><p><bold>Minor warnings:</bold> Two minor warnings were identified (missing domain/range for some properties), which were subsequently addressed.</p></list-item>
<list-item><p><bold>Best practices compliance:</bold> The ontology scored 92% on OOPS!&#x00027;s best practices checklist.</p></list-item>
</list>
<p>Additionally, we performed logical consistency checking using the HermiT reasoner and competency query testing via SPARQL (see <xref ref-type="supplementary-material" rid="SM1">Appendix A4</xref> for examples).</p>
</sec>
</sec>
<sec>
<label>6.3</label>
<title>Semantic consistency verification methods</title>
<p>To ensure both ABox logical consistency and TBox coherency in our ontology-driven DT framework, we implemented a multi-layered verification approach:</p>
<sec>
<label>6.3.1</label>
<title>Logical consistency checking (ABox)</title>
<list list-type="bullet">
<list-item><p><bold>Reasoner-based validation:</bold> We employed HermiT and Pellet OWL-DL reasoners to detect logical contradictions in the ABox. These reasoners perform consistency checking by verifying that no individual can be inferred to belong to mutually exclusive classes.</p></list-item>
<list-item><p><bold>Instance validation:</bold> Using SHACL (Shapes Constraint Language), we defined constraints on instance data to ensure ABox assertions comply with TBox definitions.</p></list-item>
<list-item><p><bold>Real-time monitoring:</bold> For streaming data in DTs, we implemented incremental reasoning to detect inconsistencies as new data arrives.</p></list-item>
</list>
</sec>
<sec>
<label>6.3.2</label>
<title>Conceptual coherency verification (TBox)</title>
<list list-type="bullet">
<list-item><p><bold>Unsatisfiability detection:</bold> Using Description Logic classifiers, we identified unsatisfiable concepts (concepts that cannot have any instances) which indicate modeling errors.</p></list-item>
<list-item><p><bold>Cycle detection:</bold> We implemented algorithms to detect circular dependencies in subclass relationships.</p></list-item>
<list-item><p><bold>Modularity checking:</bold> The distributed ontology framework includes consistency checks between local, regional, and global ontologies using ontology alignment techniques.</p></list-item>
</list>
</sec>
<sec>
<label>6.3.3</label>
<title>Implementation details</title>
<p>The consistency verification was implemented using:</p>
<list list-type="bullet">
<list-item><p><bold>OWL API</bold> for programmatic ontology manipulation and reasoning.</p></list-item>
<list-item><p><bold>SPARQL queries</bold> for runtime consistency checks on instance data.</p></list-item>
<list-item><p><bold>Automated test suites</bold> that run consistency checks during ontology development.</p></list-item>
<list-item><p><bold>Continuous integration pipeline</bold> that validates all ontology commits against consistency requirements.</p></list-item>
</list>
<p><xref ref-type="table" rid="T8">Table 8</xref> shows the consistency metrics achieved in our framework compared to traditional approaches.</p>
<table-wrap position="float" id="T8">
<label>Table 8</label>
<caption><p>Semantic consistency metrics comparison.</p></caption>
<table frame="box" rules="all">
<thead>
<tr>
<th valign="top" align="left"><bold>Metric</bold></th>
<th valign="top" align="center"><bold>Traditional DTs</bold></th>
<th valign="top" align="center"><bold>Our framework</bold></th>
<th valign="top" align="center"><bold>Improvement</bold></th>
</tr>
</thead>
<tbody>
<tr>
<td valign="top" align="left">ABox consistency violations</td>
<td valign="top" align="center">12%</td>
<td valign="top" align="center">2%</td>
<td valign="top" align="center">83%</td>
</tr>
<tr>
<td valign="top" align="left">TBox unsatisfiable concepts</td>
<td valign="top" align="center">8%</td>
<td valign="top" align="center">1%</td>
<td valign="top" align="center">88%</td>
</tr>
<tr>
<td valign="top" align="left">Cross-ontology conflicts</td>
<td valign="top" align="center">15%</td>
<td valign="top" align="center">3%</td>
<td valign="top" align="center">80%</td>
</tr></tbody>
</table>
</table-wrap>
</sec>
</sec>
<sec>
<label>6.4</label>
<title>Conceptual model development</title>
<p>Based on insights gained from the literature, we developed a conceptual model that illustrates how ontological frameworks can enhance the capabilities of Digital Twins. The development process of the conceptual model involved the following key steps:</p>
<list list-type="order">
<list-item><p><bold>Identify core concepts:</bold> The primary concepts identified for the conceptual model include:
<list list-type="bullet">
<list-item><p><italic>Ontology:</italic> A formal representation of knowledge, including entities, relationships, and rules.</p></list-item>
<list-item><p><italic>Digital Twin:</italic> A digital replica of a physical system, with real-time data integration and interaction.</p></list-item>
<list-item><p><italic>Interoperability:</italic> The ability of various systems and components to communicate seamlessly.</p></list-item>
<list-item><p><italic>Scalability:</italic> The ability of the system to handle an increasing amount of data or users.</p></list-item>
<list-item><p><italic>AI Integration:</italic> The incorporation of artificial intelligence for advanced decision-making and prediction.</p></list-item>
</list></p></list-item>
<list-item><p><bold>Ontology selection and formalization:</bold> Based on the identified concepts, we selected and developed domain-specific ontological models to provide the necessary structure and semantics for data in Digital Twins. These models are formally represented using the standard Web Ontology Language (OWL) for expressive knowledge representation and logical axioms, and serialized using the Resource Description Framework (RDF) syntax for data interchange and integration.</p></list-item>
<list-item><p><bold>Define relationships:</bold> We defined the relationships between the key concepts to structure the conceptual model. This included defining how ontologies can improve interoperability between different components of a Digital Twin, how they can enhance data flow for AI models, and how ontologies enable scalability through modular structures.</p></list-item>
<list-item><p><bold>Model validation:</bold> After developing the conceptual model, we validated it by consulting with domain experts and analyzing case studies to ensure that the model represents a realistic and effective integration of ontologies into DTs.</p></list-item>
<list-item><p><bold>Refinement:</bold> Based on the feedback and validation, the model was refined to ensure clarity and practical applicability in real-world scenarios, particularly in industries such as manufacturing, healthcare, and smart cities.</p></list-item>
</list>
<p>The resulting conceptual model represents a modular, ontology-driven architecture for DTs, where ontologies are used to ensure semantic clarity, improve interoperability, and enable AI-driven automation. This conceptual model is shown in <xref ref-type="fig" rid="F8">Figure 8</xref>.</p>
<fig position="float" id="F8">
<label>Figure 8</label>
<caption><p>Conceptual model of ontology-enhanced digital twin.</p></caption>
<graphic mimetype="image" mime-subtype="tiff" xlink:href="fcomp-08-1757450-g0008.tif">
<alt-text content-type="machine-generated">Flowchart with a central blue rectangle labeled &#x0201C;Ontology&#x0201D; linked by arrows to three elements: &#x0201C;Digital Twin&#x0201D; (green rectangle), &#x0201C;AI Integration&#x0201D; (orange oval), and &#x0201C;Scalability&#x0201D; (purple rectangle). &#x0201C;Digital Twin&#x0201D; connects downward to &#x0201C;Interoperability&#x0201D; (yellow rectangle).</alt-text>
</graphic>
</fig>
</sec>
<sec>
<label>6.5</label>
<title>Data sources</title>
<p>The data for this research was obtained through both primary and secondary sources:</p>
<list list-type="bullet">
<list-item><p><bold>Primary data:</bold> This includes case studies of existing Digital Twin systems in industries such as manufacturing, healthcare, and smart cities. Interviews and consultations with domain experts were also conducted to gather qualitative insights on the application of ontologies in DTs.</p></list-item>
<list-item><p><bold>Secondary data:</bold> This consists of a comprehensive literature review of academic papers, reports, and industry case studies on the use of ontologies in Digital Twin systems. Previous studies focusing on interoperability, semantic clarity, AI integration, and scalability were analyzed to inform the development of the conceptual model.</p></list-item>
</list>
</sec>
<sec>
<label>6.6</label>
<title>Ontological tools</title>
<p>For ontological analysis, we employed the following tools and frameworks:</p>
<list list-type="bullet">
<list-item><p><bold>Prot&#x000E9;g&#x000E9;:</bold> A widely used open-source ontology editor, which was used to design and visualize ontologies for the conceptual model.</p></list-item>
<list-item><p><bold>OWL (Web Ontology Language):</bold> A formal ontology language used to represent the concepts, relationships, and rules in the conceptual model.</p></list-item>
<list-item><p><bold>RDF (Resource Description Framework):</bold> A framework for representing structured information, used to describe the relationships between different entities in the Digital Twin ecosystem.</p></list-item>
</list>
<p>These tools allowed for the formalization of knowledge, ensuring that the digital twin systems and their components were accurately represented and that their interactions were semantically clear.</p>
</sec>
<sec>
<label>6.7</label>
<title>Motivation view for the ontology-driven digital twin framework</title>
<p>The Motivation View provides insight into why your ontology-driven Digital Twin framework is being developed and implemented within the context of IoT applications using MQTT on Raspberry Pi. As illustrated in <xref ref-type="fig" rid="F9">Figure 9</xref>, this view captures stakeholder interests, aligns them with strategic goals, outlines actionable initiatives necessary for successful implementation, and emphasizes the role of semantic components.</p>
<list list-type="bullet">
<list-item><p>Stakeholders&#x00027; interests: Each stakeholder group has unique interests that influence their expectations from the Digital Twin framework. For instance, business executives may prioritize cost reduction and ROI, while operational managers may focus on improving efficiency through better data insights derived from semantic integration.</p></list-item>
<list-item><p>Goals alignment: The defined goals serve as guiding principles for the project, ensuring that all efforts are directed toward achieving measurable outcomes that benefit the organization as a whole. For example, enhancing data accuracy through ontological analysis directly impacts operational efficiency.</p></list-item>
<list-item><p>Drivers as motivators: Understanding external drivers helps contextualize why certain goals are prioritized over others. For example, increasing demand for real-time data insights may necessitate adopting an ontology-driven approach to maintain competitiveness in an evolving market.</p></list-item>
<list-item><p>Strategic approaches: The strategies outlined provide actionable pathways to achieve set goals. They offer a roadmap for how resources will be allocated and what initiatives will be pursued&#x02014;such as leveraging MQTT for efficient communication between devices.</p></list-item>
<list-item><p>Initiatives for implementation: Initiatives represent concrete steps taken to realize strategies. By detailing these projects within your motivation view, you can ensure that all team members understand their roles in achieving broader organizational objectives.</p></list-item>
<list-item><p>Semantic component importance: The inclusion of an ontology as a semantic component is crucial as it enhances interoperability among devices and systems by providing a shared understanding of data semantics. This leads to improved data consistency and more informed decision-making based on contextual information.</p></list-item>
</list>
<fig position="float" id="F9">
<label>Figure 9</label>
<caption><p>Motivation view for the ontology-driven digital twin framework.</p></caption>
<graphic mimetype="image" mime-subtype="tiff" xlink:href="fcomp-08-1757450-g0009.tif">
<alt-text content-type="machine-generated">Flowchart illustrating the role of semantic technologies for business executives and operational managers, detailing enhanced data accuracy, reduced integration time, semantic integration impact evaluation, ontology for structured knowledge, and improved interoperability and contextual data understanding.</alt-text>
</graphic>
</fig>
<p>The Motivation View created provides a structured representation of how various components interact within your ontology-driven Digital Twin framework focused on IoT applications using MQTT on Raspberry Pi. It highlights stakeholder interests, aligns them with strategic goals, outlines actionable initiatives necessary for successful implementation, and emphasizes the critical role of semantic technologies in enhancing system performance.</p>
</sec>
<sec>
<label>6.8</label>
<title>Security and risk view for the ontology-driven digital twin framework</title>
<p>The Security &#x00026; Risk View for the ontology-driven Digital Twin framework highlights the critical aspects of managing risks and ensuring security within IoT applications utilizing MQTT on Raspberry Pi. This view emphasizes the importance of achieving goals such as ensuring data security, mitigating risks associated with IoT deployments, and enhancing system reliability. As illustrated in <xref ref-type="fig" rid="F10">Figure 10</xref>, the view captures the interplay between stakeholders, their interests, and the associated risks, drivers, and requirements that guide security measures. By identifying potential threats like data breaches and unauthorized access, this framework enables proactive strategies to address these vulnerabilities, ensuring that the Digital Twin system operates securely and effectively in dynamic environments. The integration of semantic technologies further supports these efforts by enhancing data interoperability and contextual understanding, ultimately contributing to a robust security posture for the system.</p>
<fig position="float" id="F10">
<label>Figure 10</label>
<caption><p>Security and risk view for the ontology-driven digital twin framework.</p></caption>
<graphic mimetype="image" mime-subtype="tiff" xlink:href="fcomp-08-1757450-g0010.tif">
<alt-text content-type="machine-generated">Flowchart illustration showing business executives and operational managers at the top as stakeholders, leading to a central objective to ensure data security, mitigate IoT deployment risks, and enhance reliability, branching into risks such as data breaches and solutions like implementing robust security protocols.</alt-text>
</graphic>
</fig>
</sec>
<sec>
<label>6.9</label>
<title>Infrastructure view for the ontology-driven digital twin framework</title>
<p>The Infrastructure View for the ontology-driven Digital Twin framework outlines the essential technological components and architecture that support the system&#x00027;s functionality. This view highlights the User Interface/Application, which allows users to monitor and interact with data from hardware such as Raspberry Pi and IoT devices. The infrastructure includes the Raspberry Pi 4 Model B, serving as the primary hardware platform, alongside various IoT devices that collect and transmit data. Key software components, such as the MQTT broker for efficient messaging and an ontology management system for semantic data processing, are also integral to this framework. The use of protocols like MQTT and HTTP/HTTPS facilitates communication between devices, while methods such as M2M communication and cloud services enhance data processing capabilities. As illustrated in <xref ref-type="fig" rid="F11">Figure 11</xref>, this comprehensive structure ensures that the Digital Twin system operates effectively, enabling real-time monitoring and decision-making in dynamic environments.</p>
<fig position="float" id="F11">
<label>Figure 11</label>
<caption><p>Infrastructure view for the ontology-driven digital twin framework.</p></caption>
<graphic mimetype="image" mime-subtype="tiff" xlink:href="fcomp-08-1757450-g0011.tif">
<alt-text content-type="machine-generated">Flowchart showing an IoT architecture. User Interface/App connects to both Raspberry Pi and IoT Devices (sensors/actuators), which then link to an MQTT Broker Ontology Management System. This system connects to a Protocols block listing MQTT messaging and HTTP/HTTPS, leading to a final block listing communication methods, machine-to-machine (M2M) communication, and cloud services.</alt-text>
</graphic>
</fig>
</sec>
<sec>
<label>6.10</label>
<title>Simulation framework and synthetic data generation</title>
<p>To ensure reproducibility and address the challenges of accessing proprietary industrial data, we developed a comprehensive simulation framework that generates synthetic Digital Twin environments for manufacturing, healthcare, and smart city applications. All experimental results presented in this paper are based on controlled simulations using established benchmarks.</p>
<sec>
<label>6.10.1</label>
<title>Simulation architecture</title>
<p>Our simulation framework consists of three interconnected layers:</p>
<list list-type="bullet">
<list-item><p><bold>Physical system simulator:</bold> Generates synthetic sensor data (IoT devices, medical sensors, and environmental monitors) with configurable noise, sampling rates, and failure modes.</p></list-item>
<list-item><p><bold>Semantic layer:</bold> Implements ontological reasoning using Prot&#x000E9;g&#x000E9;/OWL API, with configurable complexity levels matching real-world Digital Twin deployments.</p></list-item>
<list-item><p><bold>Performance monitoring:</bold> Collects metrics (latency, accuracy, and resource usage) through embedded agents that log to a time-series database.</p></list-item>
</list>
</sec>
<sec>
<label>6.10.2</label>
<title>Manufacturing simulation environment</title>
<list list-type="bullet">
<list-item><p><bold>Benchmark:</bold> Extended Manufacturing Simulation Framework (MSF) (<xref ref-type="bibr" rid="B15">Furrer et al., 2016</xref>).</p></list-item>
<list-item><p><bold>Components:</bold>
<list list-type="simple">
<list-item><p>- 10&#x02013;100 synthetic production lines with robotic arms, conveyor belts, quality control stations.</p></list-item>
<list-item><p>- 5&#x02013;50 sensor types per line (temperature: 20&#x02013;80&#x000B0;C &#x000B1;0.5&#x000B0;C, vibration: 0&#x02013;10mm/s &#x000B1;0.1mm/s, pressure: 0&#x02013;100psi &#x000B1;1psi).</p></list-item>
<list-item><p>- Synthetic anomalies: 1%&#x02013;10% random failures (stuck valves, overheating, and misalignment).</p></list-item>
</list></p></list-item>
<list-item><p><bold>Data generation:</bold> Python-based generator using normal distributions for normal operation, Poisson for anomalies.</p></list-item>
<list-item><p><bold>Duration:</bold> 24&#x02013;720 simulated hours per experiment.</p></list-item>
<list-item><p><bold>Validation:</bold> Compared against Kaggle&#x00027;s Manufacturing Predictive Maintenance dataset (<xref ref-type="bibr" rid="B44">Shivamb, 2025</xref>) for statistical similarity.</p></list-item>
</list>
</sec>
<sec>
<label>6.10.3</label>
<title>Healthcare simulation environment</title>
<list list-type="bullet">
<list-item><p><bold>Benchmark:</bold> Synthetic Patient Health Simulator (SPHS) (<xref ref-type="bibr" rid="B48">The MITRE Corporation, 2025</xref>).</p></list-item>
<list-item><p><bold>Components:</bold>
<list list-type="simple">
<list-item><p>- 50&#x02013;500 synthetic patients with configurable demographics and comorbidities.</p></list-item>
<list-item><p>- Vital signs generators: ECG (60&#x02013;100 bpm &#x000B1;5bpm), blood pressure (90&#x02013;140/60&#x02013;90 mmHg &#x000B1;3mmHg), SpO2 (95%&#x02013;100% &#x000B1;1%), respiration (12&#x02013;20 bpm &#x000B1;2bpm).</p></list-item>
<list-item><p>- Synthetic medical events: arrhythmias (1%&#x02013;5%), hypertensive crises (0.5%&#x02013;2%), desaturation events (2%&#x02013;8%).</p></list-item>
</list></p></list-item>
<list-item><p><bold>Data Standards:</bold> FHIR R4 profiles for patient data, HL7 v2 for device communication.</p></list-item>
<list-item><p><bold>Validation:</bold> Statistical validation against MIMIC-III dataset distributions (<xref ref-type="bibr" rid="B23">Johnson et al., 2016</xref>).</p></list-item>
</list>
</sec>
<sec>
<label>6.10.4</label>
<title>Smart city simulation environment</title>
<p>Our smart city simulations are architected and deployed on the <bold>Microsoft Azure Digital Twins (ADT)</bold> platform (<xref ref-type="bibr" rid="B33">Microsoft Azure, 2023b</xref>), providing a scalable, cloud-native environment for building and testing our ontological framework.</p>
<list list-type="bullet">
<list-item><p><bold>Platform foundation:</bold> We utilize <bold>Azure Digital Twins</bold> as the core service for creating a comprehensive digital model of an urban environment. The graph-based architecture of ADT, defined using the <bold>Digital Twins Definition Language (DTDL)</bold> (<xref ref-type="bibr" rid="B32">Microsoft Azure, 2023a</xref>), serves as the primary deployment target for validating our custom urban ontology.</p></list-item>
<list-item><p><bold>Components &#x00026; data generation:</bold>
<list list-type="simple">
<list-item><p>- A synthetic city grid is modeled within ADT, comprising 10&#x02013;100 intersections (modeled as digital twins) with 5&#x02013;20 associated virtual sensor twins per intersection.</p></list-item>
<list-item><p>- Environmental sensor data (air quality: PM2.5 0&#x02013;50 &#x003BC;g/m<sup>3</sup> &#x000B1;2&#x003BC;g/m<sup>3</sup>, noise: 40&#x02013;80 dB &#x000B1;3dB, temperature, humidity) is generated by our custom Python simulators.</p></list-item>
<list-item><p>- Traffic flow is simulated by integrating the open-source <bold>SUMO (Simulation of Urban MObility)</bold> traffic simulator (<xref ref-type="bibr" rid="B27">L&#x000E4;mmel, 2017</xref>). SUMO generates vehicle counts (0&#x02013;100 vehicles/min &#x000B1;5vehicles) with realistic rush hour patterns, and the output is streamed into the corresponding Azure Digital Twins.</p></list-item>
</list></p></list-item>
<list-item><p><bold>Integration &#x00026; orchestration:</bold> Synthetic data streams from the Python generators and SUMO are ingested into the Azure Digital Twins graph via <bold>Azure IoT Hub</bold> (<xref ref-type="bibr" rid="B34">Microsoft Azure, 2023c</xref>), simulating real-time telemetry from thousands of IoT devices. The performance and semantics of our ontology are tested within this integrated Azure environment.</p></list-item>
</list>
</sec>
<sec>
<label>6.10.5</label>
<title>Simulation control parameters</title>
<p><xref ref-type="table" rid="T9">Table 9</xref> summarizes the configurable parameters for each simulation environment.</p>
<table-wrap position="float" id="T9">
<label>Table 9</label>
<caption><p>Simulation environment parameters.</p></caption>
<table frame="box" rules="all">
<thead>
<tr>
<th valign="top" align="left"><bold>Parameter</bold></th>
<th valign="top" align="center"><bold>Manufacturing</bold></th>
<th valign="top" align="center"><bold>Healthcare</bold></th>
<th valign="top" align="center"><bold>Smart city</bold></th>
</tr>
</thead>
<tbody>
<tr>
<td valign="top" align="left">Duration</td>
<td valign="top" align="center">24&#x02013;720 h</td>
<td valign="top" align="center">1&#x02013;30 days</td>
<td valign="top" align="center">1&#x02013;14 days</td>
</tr>
<tr>
<td valign="top" align="left">Data points</td>
<td valign="top" align="center">1M&#x02013;100M</td>
<td valign="top" align="center">500K&#x02013;5M</td>
<td valign="top" align="center">2M&#x02013;20M</td>
</tr>
<tr>
<td valign="top" align="left">Sensors/devices</td>
<td valign="top" align="center">100&#x02013;10,000</td>
<td valign="top" align="center">50&#x02013;500</td>
<td valign="top" align="center">200&#x02013;2,000</td>
</tr>
<tr>
<td valign="top" align="left">Data rate</td>
<td valign="top" align="center">1&#x02013;100 Hz</td>
<td valign="top" align="center">0.1&#x02013;100 Hz</td>
<td valign="top" align="center">0.01&#x02013;10 Hz</td>
</tr>
<tr>
<td valign="top" align="left">Anomaly rate</td>
<td valign="top" align="center">1%&#x02013;10%</td>
<td valign="top" align="center">0.5%&#x02013;5%</td>
<td valign="top" align="center">2%&#x02013;15%</td>
</tr>
<tr>
<td valign="top" align="left">Format variety</td>
<td valign="top" align="center">5&#x02013;15</td>
<td valign="top" align="center">3&#x02013;10</td>
<td valign="top" align="center">8&#x02013;20</td>
</tr></tbody>
</table>
</table-wrap>
</sec>
</sec>
<sec>
<label>6.11</label>
<title>Evaluation metrics</title>
<p>The effectiveness of the ontology-enhanced Digital Twins was evaluated using the following metrics:</p>
<list list-type="bullet">
<list-item><p><bold>Interoperability:</bold> Measured by the ability of the system to seamlessly integrate data from diverse sources and systems. This was assessed by examining the time taken for data integration, the error rate in data exchange, and the compatibility between cross-system components. A significant improvement in interoperability was expected by reducing integration time and minimizing errors.</p></list-item>
<list-item><p><bold>Semantic clarity:</bold> Measured by the reduction in errors related to semantic ambiguity. The effectiveness of ontologies in clarifying terms and concepts used across different systems was assessed by tracking the accuracy of data flow and decision-making processes before and after applying ontologies.</p></list-item>
<list-item><p><bold>Scalability:</bold> Evaluated by the system&#x00027;s ability to scale to handle increasing data and complexity. We measured the system&#x00027;s ability to incorporate new components, such as sensors or external systems, and evaluated the system&#x00027;s performance as the number of components increased.</p></list-item>
<list-item><p><bold>AI integration:</bold> Evaluated by the performance of AI algorithms (e.g., machine learning models) integrated within the Digital Twin framework. Key metrics included the accuracy of predictions, the decision-making speed, and the system&#x00027;s ability to adapt to new data in real-time.</p></list-item>
</list>
<p>Each of these metrics was measured quantitatively and qualitatively by comparing the performance of traditional Digital Twin systems with those enhanced by ontological frameworks.</p>
</sec>
<sec>
<label>6.12</label>
<title>Scientific design principles</title>
<p>The scientific design applied in the development of this framework is rooted in principles of systems theory, semantic web technologies, and AI-driven automation:</p>
<list list-type="bullet">
<list-item><p><bold>Modularity:</bold> The conceptual model is designed to be modular, allowing for flexible integration of new components into the Digital Twin system without disrupting the overall architecture.</p></list-item>
<list-item><p><bold>Scalability:</bold> The model ensures that Digital Twin systems can scale by using ontologies to represent data in a way that allows for the easy addition of new sensors, components, and external systems.</p></list-item>
<list-item><p><bold>Interoperability:</bold> The use of ontologies allows for a standardized way of representing data, improving communication between different components and systems.</p></list-item>
<list-item><p><bold>Adaptability:</bold> The system is designed to be adaptable, supporting the integration of AI for dynamic decision-making and prediction, ensuring that the system can adjust to changing conditions in real-time.</p></list-item>
<list-item><p><bold>Validation and refinement:</bold> The iterative process of validation and refinement ensured that the framework developed was practical, effective, and applicable to real-world Digital Twin implementations.</p></list-item>
</list>
</sec>
<sec>
<label>6.13</label>
<title>Application viewpoint in the architectural conceptual model</title>
<p>The <bold>Application viewpoint</bold> serves as the central hub in the architectural conceptual model, orchestrating advanced functionalities through its core components. These components&#x02014;Ontology, Digital Twin, AI Decision Support, and Interoperability Service&#x02014;collaborate to provide semantic reasoning, real-time simulations, AI-driven insights, and seamless system integration. A summary of the interactions and relationships between these components is detailed in <xref ref-type="table" rid="T10">Table 10</xref>.</p>
<table-wrap position="float" id="T10">
<label>Table 10</label>
<caption><p>Summary of relationships in the application viewpoint.</p></caption>
<table frame="box" rules="all">
<thead>
<tr>
<th valign="top" align="left"><bold>Source component</bold></th>
<th valign="top" align="left"><bold>Target component</bold></th>
<th valign="top" align="left"><bold>Relationship type</bold></th>
<th valign="top" align="left"><bold>Label description</bold></th>
</tr>
</thead>
<tbody>
<tr>
<td valign="top" align="left">Ontology component</td>
<td valign="top" align="left">Function: semantic reasoning</td>
<td valign="top" align="left">Realizes</td>
<td valign="top" align="left">Provides functionality for semantic reasoning</td>
</tr>
<tr>
<td valign="top" align="left">Ontology component</td>
<td valign="top" align="left">Service: semantic integration</td>
<td valign="top" align="left">Provides</td>
<td valign="top" align="left">Offers semantic integration service</td>
</tr>
<tr>
<td valign="top" align="left">Function: semantic reasoning</td>
<td valign="top" align="left">Service: semantic integration</td>
<td valign="top" align="left">Triggers</td>
<td valign="top" align="left">Activates semantic integration</td>
</tr>
<tr>
<td valign="top" align="left">Digital Twin component</td>
<td valign="top" align="left">Event: real-time update</td>
<td valign="top" align="left">Realizes</td>
<td valign="top" align="left">Embodies real-time update functionality</td>
</tr>
<tr>
<td valign="top" align="left">Digital Twin component</td>
<td valign="top" align="left">Module: simulation engine</td>
<td valign="top" align="left">Triggers</td>
<td valign="top" align="left">Initiates simulation processes</td>
</tr>
<tr>
<td valign="top" align="left">Digital Twin component</td>
<td valign="top" align="left">Service: semantic integration</td>
<td valign="top" align="left">Uses</td>
<td valign="top" align="left">Utilizes semantic integration</td>
</tr>
<tr>
<td valign="top" align="left">AI decision support</td>
<td valign="top" align="left">Function: predictive analytics</td>
<td valign="top" align="left">Realizes</td>
<td valign="top" align="left">Implements predictive analytics functionality</td>
</tr>
<tr>
<td valign="top" align="left">AI decision support</td>
<td valign="top" align="left">Service: AI-driven insights</td>
<td valign="top" align="left">Provides</td>
<td valign="top" align="left">Offers AI-driven insights</td>
</tr>
<tr>
<td valign="top" align="left">Interoperability service</td>
<td valign="top" align="left">All components</td>
<td valign="top" align="left">Provides</td>
<td valign="top" align="left">Ensures communication among components</td>
</tr>
<tr>
<td valign="top" align="left">Process: data integration</td>
<td valign="top" align="left">Interoperability service</td>
<td valign="top" align="left">Used By</td>
<td valign="top" align="left">Managed by interoperability service</td>
</tr></tbody>
</table>
</table-wrap>
</sec>
<sec>
<label>6.14</label>
<title>Components of the application viewpoint</title>
<list list-type="bullet">
<list-item><p><bold>Ontology component:</bold>
<list list-type="simple">
<list-item><p>- <bold>Type:</bold> Application component.</p></list-item>
<list-item><p>- <bold>Description:</bold> Provides semantic reasoning capabilities to ensure contextual understanding across the system.</p></list-item>
<list-item><p>- <bold>Functions:</bold>
<list list-type="simple">
<list-item><p>&#x0002A; <bold>Semantic reasoning:</bold> Implements reasoning over structured knowledge.</p></list-item>
<list-item><p>&#x0002A; <bold>Semantic integration:</bold> Offers a service to ensure semantic coherence between components.</p></list-item>
</list></p></list-item>
<list-item><p>- <bold>Interactions:</bold> As summarized in <xref ref-type="table" rid="T10">Table 10</xref>, the Ontology Component provides semantic reasoning functionality and triggers integration services to support both <bold>AI Decision Support</bold> and the <bold>Digital Twin</bold>.</p></list-item>
</list></p></list-item>
<list-item><p><bold>Digital Twin component:</bold>
<list list-type="simple">
<list-item><p>- <bold>Type:</bold> Application component.</p></list-item>
<list-item><p>- <bold>Description:</bold> Simulates physical assets and processes real-time updates.</p></list-item>
<list-item><p>- <bold>Functions:</bold>
<list list-type="simple">
<list-item><p>&#x0002A; <bold>Real-time update:</bold> Captures events and triggers simulations.</p></list-item>
<list-item><p>&#x0002A; <bold>Simulation engine:</bold> A module dedicated to executing simulation tasks.</p></list-item>
</list></p></list-item>
<list-item><p>- <bold>Interactions:</bold> <xref ref-type="table" rid="T10">Table 10</xref> illustrates how the Digital Twin Component feeds real-time data to <bold>AI decision support</bold> for predictive analytics and uses semantic reasoning capabilities from the <bold>Ontology component</bold>.</p></list-item>
</list></p></list-item>
<list-item><p><bold>AI decision support:</bold>
<list list-type="simple">
<list-item><p>- <bold>Type:</bold> Application component.</p></list-item>
<list-item><p>- <bold>Description:</bold> Employs AI techniques for decision-making, predictive analytics, and actionable insights.</p></list-item>
<list-item><p>- <bold>Functions:</bold>
<list list-type="simple">
<list-item><p>&#x0002A; <bold>Predictive analytics:</bold> Analyzes data to forecast outcomes and optimize operations.</p></list-item>
<list-item><p>&#x0002A; <bold>AI-driven insights:</bold> Provides recommendations and actionable insights in real-time.</p></list-item>
</list></p></list-item>
<list-item><p>- <bold>Interactions:</bold> As highlighted in <xref ref-type="table" rid="T10">Table 10</xref>, AI Decision Support integrates real-time data from the Digital Twin and structured knowledge from the Ontology component.</p></list-item>
</list></p></list-item>
<list-item><p><bold>Interoperability service:</bold>
<list list-type="simple">
<list-item><p>- <bold>Type:</bold> Application service.</p></list-item>
<list-item><p>- <bold>Description:</bold> Ensures seamless communication and data integration across components.</p></list-item>
<list-item><p>- <bold>Functions:</bold>
<list list-type="simple">
<list-item><p>&#x0002A; <bold>Data integration:</bold> Manages activities ensuring consistency and coherence across systems.</p></list-item>
</list></p></list-item>
<list-item><p>- <bold>Interactions:</bold> Facilitates interoperability between all core components, as detailed in <xref ref-type="table" rid="T10">Table 10</xref>.</p></list-item>
</list></p></list-item>
</list>
</sec>
<sec>
<label>6.15</label>
<title>Summary of relationships in ArchiMate terms</title>
<p>The relationships and interactions among the components from the point of view of the application are presented in <xref ref-type="table" rid="T10">Table 10</xref>. These relationships define how components such as the Ontology, Digital Twin, and AI Decision Support collaborate to achieve cohesive functionality.</p>
</sec>
<sec>
<label>6.16</label>
<title>AI decision support: role and importance</title>
<p><bold>AI decision support</bold> utilizes advanced data analysis, predictive modeling, and automated reasoning to enhance decision-making processes. It integrates seamlessly with other components to ensure informed and actionable insights. Key features include:</p>
<list list-type="bullet">
<list-item><p><bold>Data analysis:</bold> Analyzes large data sets from sensors, historical records, and external sources.</p></list-item>
<list-item><p><bold>Predictive analytics:</bold> Forecasts outcomes like equipment failures or operational inefficiencies.</p></list-item>
<list-item><p><bold>Automated reasoning:</bold> Simulates scenarios to evaluate potential decisions.</p></list-item>
<list-item><p><bold>Real-time insights:</bold> Delivers immediate and actionable recommendations.</p></list-item>
<list-item><p><bold>Integration with other systems:</bold> Ensures cohesive functionality with the <bold>Digital Twin</bold> and <bold>Ontology</bold>.</p></list-item>
</list>
</sec>
<sec>
<label>6.17</label>
<title>Benefits of the application viewpoint</title>
<p>The Application viewpoint unifies semantic reasoning, real-time simulations, and AI-driven insights through its tightly integrated components. This enables comprehensive decision-making, enhanced operational efficiency, and robust data integration across diverse applications.</p>
<p><xref ref-type="fig" rid="F12">Figure 12</xref> illustrates the overall structure of the Application viewpoint within the conceptual model, highlighting the interactions between its core components.</p>
<fig position="float" id="F12">
<label>Figure 12</label>
<caption><p>Conceptual model of the application viewpoint.</p></caption>
<graphic mimetype="image" mime-subtype="tiff" xlink:href="fcomp-08-1757450-g0012.tif">
<alt-text content-type="machine-generated">Conceptual diagram with four main sections: Ontology, Interoperability, Digital Twin, and AI Support. Each section contains color-coded components linked by arrows, illustrating relationships like providing, implementing, employing, activating, and generating among services such as Semantic Integration, Interoperability Service, Real-time Update, AI-Driven Insights, and Predictive Analytics, with descriptive labels on each connection.</alt-text>
</graphic>
</fig>
<p>In summary, the methodology followed a structured approach starting with a comprehensive literature review, followed by the development and validation of a conceptual model. The model was then refined and applied to the integration of ontologies into Digital Twin systems. The effectiveness of the model was evaluated using metrics such as interoperability, semantic clarity, scalability, and AI integration. These steps ensure that the framework is both scientifically grounded and practically applicable to real-world Digital Twin systems.</p>
</sec>
</sec>
<sec id="s7">
<label>7</label>
<title>Results and discussion</title>
<p>In this section, we present a detailed analysis of the results, comparing our ontology-driven Digital Twin (DT) framework to traditional systems and other existing approaches. The significance of integrating semantic technologies into Digital Twin systems is emphasized through various performance metrics, such as error rate, integration time, scalability, and decision-making accuracy. Our contributions in terms of improving these key aspects are highlighted below, followed by a deeper discussion of the figures presented.</p>
<sec>
<label>7.1</label>
<title>Core findings and system performance</title>
<p>The integration of semantic ontologies into Digital Twin systems has shown substantial improvements in several critical aspects. <xref ref-type="table" rid="T11">Table 11</xref> provides a structured comparison of our method against existing approaches.</p>
<list list-type="bullet">
<list-item><p><bold>Error rate reduction (semantic consistency):</bold> As illustrated in <xref ref-type="fig" rid="F13">Figure 13</xref>, our ontology-driven framework significantly reduces the semantic error rate compared to traditional DT systems. This metric, detailed in Section 5.2, specifically measures the percentage of data exchange events (e.g., between IoT sensors and control systems) that fail due to semantic conflicts such as unit mismatches, protocol incompatibilities, or terminology ambiguities within the simulated manufacturing environment. While the error rate in conventional DT systems is approximately 8%, our approach achieves a reduction to 2%. This reduction in error rate implies that the semantic integration improves data accuracy and system consistency. In practical terms, lower error rates mean better decision-making, fewer operational mistakes, and a more reliable system for real-time applications.</p></list-item>
<list-item><p><bold>Integration time efficiency:</bold> <xref ref-type="fig" rid="F14">Figure 14</xref> shows that our system dramatically reduces integration time. While traditional DT systems require around 15 hours for full integration, our ontology-driven framework completes the same process in just 6 h. This significant reduction in time speaks to the efficiency gains that semantic integration provides. Faster integration allows for quicker deployment of Digital Twin systems, which is especially crucial in time-sensitive industries such as manufacturing and healthcare.</p></list-item>
<list-item><p><bold>Scalability performance:</bold> The scalability of our semantic Digital Twin system is evident from <xref ref-type="fig" rid="F15">Figure 15</xref>. As the number of devices in the system increases, traditional systems experience significant delays in integration, with time increasing almost linearly. In contrast, our system exhibits stable performance, maintaining low integration times even as the number of devices grows. This demonstrates that our ontology-driven framework can scale efficiently and remains effective as the complexity of the system increases. Scalability is a critical factor for industries looking to deploy Digital Twin systems across large, distributed infrastructures.</p></list-item>
<list-item><p><bold>Improved decision-making accuracy:</bold> Our approach also leads to better decision-making accuracy, as shown in <xref ref-type="fig" rid="F16">Figure 16</xref>. The decision-making accuracy of our ontology-driven system reaches 90%, compared to 70% for traditional DT systems. This significant improvement highlights the role of semantic technologies in enhancing the decision-making process by providing a deeper understanding of the system&#x00027;s context and relationships between components. A higher decision-making accuracy translates to more informed and optimal decisions, which are particularly valuable in environments where real-time responses are crucial.</p></list-item>
</list>
<table-wrap position="float" id="T11">
<label>Table 11</label>
<caption><p>Performance comparison of ontology-driven DT approaches based on simulated benchmarks.</p></caption>
<table frame="box" rules="all">
<thead>
<tr>
<th valign="top" align="left"><bold>Approach</bold></th>
<th valign="top" align="center"><bold>Error rate (%)</bold></th>
<th valign="top" align="center"><bold>Integration time (hrs)</bold></th>
<th valign="top" align="center"><bold>Scalability (query time)</bold></th>
<th valign="top" align="center"><bold>Decision accuracy (%)</bold></th>
<th valign="top" align="center"><bold>Computational overhead (ms/query)</bold></th>
</tr>
</thead>
<tbody>
<tr>
<td valign="top" align="left">Traditional DT</td>
<td valign="top" align="center">8.0</td>
<td valign="top" align="center">15</td>
<td valign="top" align="center">25ms per query</td>
<td valign="top" align="center">70</td>
<td valign="top" align="center">5.5</td>
</tr>
<tr>
<td valign="top" align="left">Ontology-based DT (baseline)</td>
<td valign="top" align="center">5.0</td>
<td valign="top" align="center">12</td>
<td valign="top" align="center">18ms per query</td>
<td valign="top" align="center">80</td>
<td valign="top" align="center">9.2</td>
</tr>
<tr>
<td valign="top" align="left"><bold>Our work (proposed)</bold></td>
<td valign="top" align="center"><bold>2.0</bold></td>
<td valign="top" align="center"><bold>6</bold></td>
<td valign="top" align="center"><bold>10ms per query</bold></td>
<td valign="top" align="center"><bold>90</bold></td>
<td valign="top" align="center"><bold>12.8</bold></td>
</tr></tbody>
</table>
<table-wrap-foot>
<p>Error Rate refers to semantic inconsistencies in data exchange; Integration Time is for system expansion; Scalability is measured via query latency; Decision Accuracy is the F1-score for event detection; Computational Overhead is the added reasoning time per query. Bold values indicate the ontology-driven Digital Twin framework proposed in this study, evaluated using the same simulated industrial environment and benchmark conditions as the baseline methods.</p>
</table-wrap-foot>
</table-wrap>
<fig position="float" id="F13">
<label>Figure 13</label>
<caption><p>Comparison of error rates between traditional, ontology-based, and proposed ontology-driven DT systems. The proposed system demonstrates a significant reduction in error rates.</p></caption>
<graphic mimetype="image" mime-subtype="tiff" xlink:href="fcomp-08-1757450-g0013.tif">
<alt-text content-type="machine-generated">Bar chart comparing error rates for three decision tree methods: Traditional DT shows 8 percent, Ontology-based Framework shows 5 percent, and Proposed Ontology-driven DT shows 2 percent, illustrating improvement in accuracy.</alt-text>
</graphic>
</fig>
<fig position="float" id="F14">
<label>Figure 14</label>
<caption><p>Integration time comparison: Traditional DT systems vs. ontology-driven DT systems. The semantic approach significantly reduces integration time.</p></caption>
<graphic mimetype="image" mime-subtype="tiff" xlink:href="fcomp-08-1757450-g0014.tif">
<alt-text content-type="machine-generated">Bar chart comparing integration time in hours for three methods: Traditional DT at fifteen hours, Ontology-based Framework at twelve hours, and Proposed Ontology-driven DT at six hours.</alt-text>
</graphic>
</fig>
<fig position="float" id="F15">
<label>Figure 15</label>
<caption><p>Scalability performance comparison: Time taken for domain integration as system complexity increases. Our semantic system maintains its efficiency even with added devices.</p></caption>
<graphic mimetype="image" mime-subtype="tiff" xlink:href="fcomp-08-1757450-g0015.tif">
<alt-text content-type="machine-generated">Line graph comparing scalability performance; x-axis shows number of devices from five to twenty, y-axis shows integration time in hours. Proposed ontology-driven DT has lower integration times than traditional DT as device count increases.</alt-text>
</graphic>
</fig>
<fig position="float" id="F16">
<label>Figure 16</label>
<caption><p>Decision-making accuracy comparison: The ontology-driven framework significantly improves decision-making accuracy.</p></caption>
<graphic mimetype="image" mime-subtype="tiff" xlink:href="fcomp-08-1757450-g0016.tif">
<alt-text content-type="machine-generated">Bar chart comparing decision-making accuracy for three methods: Traditional DT at seventy percent, Ontology-based Framework at eighty percent, and Proposed Ontology-driven DT at ninety percent, with increasing accuracy across the methods.</alt-text>
</graphic>
</fig>
<sec>
<label>7.1.1</label>
<title>Explanation and implications of error rate comparison</title>
<p><xref ref-type="fig" rid="F13">Figure 13</xref> demonstrates the comparison of error rates between the traditional Digital Twin system, the ontology-based framework, and our proposed ontology-driven Digital Twin system. The traditional system has an error rate of approximately 8%, which reflects challenges in achieving accurate data integration and analysis. The ontology-based framework shows improvement with a 5% error rate, showcasing the advantages of semantic reasoning in reducing errors. However, the most notable reduction is seen in our proposed ontology-driven system, which achieves an error rate of only 2%.</p>
<p>This low error rate is significant because it directly enhances the system&#x00027;s reliability. Lower errors mean that data fed into the Digital Twin is more accurate, leading to better simulation results, predictions, and decision-making. In industrial applications, this reduction can result in improved predictive maintenance, optimized resources, and minimized operational disruptions.</p>
</sec>
<sec>
<label>7.1.2</label>
<title>Explanation and implications of integration time comparison</title>
<p><xref ref-type="fig" rid="F14">Figure 14</xref> compares the integration times of traditional Digital Twin systems with those utilizing our ontology-driven approach. The traditional system requires approximately 15 h to integrate all components; this delay can hinder time-sensitive processes such as monitoring and maintenance in operational environments. The ontology-based framework reduces this time to 12 h but still lags behind our proposed solution.</p>
<p>In contrast, our ontology-driven system requires only 6 h for complete integration&#x02014;a dramatic reduction that is critical for industries where deployment speed is essential. This faster integration allows for quicker adjustments and updates to the system leading to better adaptability and responsiveness in dynamic environments such as manufacturing or smart cities.</p>
</sec>
<sec>
<label>7.1.3</label>
<title>Explanation and implications of scalability comparison</title>
<p><xref ref-type="fig" rid="F15">Figure 15</xref> illustrates the scalability performance for both traditional Digital Twin systems and our ontology-driven approach. As the number of devices increases within the system: - Traditional systems experience linear growth in integration time. - In contrast, our ontology-driven framework maintains stable performance with minimal increases in integration time despite adding more devices.</p>
<p>This indicates that our semantic approach can handle increasing complexity without significant degradation in performance&#x02014;a major concern for industries like smart cities or large-scale industrial IoT networks where connected devices can number in thousands.</p>
</sec>
<sec>
<label>7.1.4</label>
<title>Explanation and implications of decision-making accuracy comparison</title>
<p><xref ref-type="fig" rid="F16">Figure 16</xref> compares decision-making accuracy across different frameworks. The traditional system achieves an accuracy level of 70%, while the ontology-based framework improves this to 80%. However; our proposed ontology-driven solution achieves an impressive accuracy rate of 90%.</p>
<p>The enhanced accuracy allows for more informed decisions based on contextual information provided by semantic technologies&#x02014;an invaluable asset particularly valuable in predictive maintenance scenarios where accurate predictions are essential to prevent costly downtimes or failures.</p>
<p>While our proposed ontology-driven framework offers substantial advantages over traditional methods; challenges remain including addressing extensive domain knowledge requirements for customizing ontologies specific to industries; managing computational overhead associated with semantic reasoning processes; and integrating seamlessly into existing legacy infrastructures.</p>
<p>In conclusion; the proposed ontology-driven Digital Twin framework represents a significant advancement in Digital Twin technology with marked improvements across key performance metrics such as error rate reduction; efficient integration times; scalability capabilities; and enhanced decision-making accuracy. By leveraging semantic technologies effectively; our system achieves superior data consistency; faster deployment times; and more informed decision-making&#x02014;making it a valuable tool for industries aiming to implement Digital Twin solutions in complex dynamic environments.</p>
</sec>
<sec>
<label>7.1.5</label>
<title>Interoperability validation</title>
<p>To validate our interoperability claims, we conducted systematic testing against systems using standard ontologies:</p>
<list list-type="bullet">
<list-item><p><bold>Cross-ontology query success rate:</bold> Our framework achieved 92% success rate in querying systems using BFO-aligned ontologies, demonstrating effective semantic mapping.</p></list-item>
<list-item><p><bold>Data exchange compatibility:</bold> When interfacing with systems using OPC UA semantic models, our framework maintained 88% data consistency without manual intervention.</p></list-item>
<list-item><p><bold>Standard alignment overhead:</bold> The computational overhead for maintaining alignment with standard ontologies was measured at 15% additional reasoning time, which we consider acceptable given the interoperability benefits.</p></list-item>
</list>
<p>These results demonstrate that while our framework uses a custom global ontology for performance optimization, it effectively maintains interoperability with systems using standardized ontological approaches through well-designed mapping mechanisms.</p>
</sec>
</sec>
<sec>
<label>7.2</label>
<title>Limitations</title>
<p>While our framework demonstrates strong performance in ontology-driven Digital Twin applications, we acknowledge several limitations:</p>
<list list-type="bullet">
<list-item><p><bold>Standard ontology alignment:</bold> Although our framework maintains semantic alignment with standard ontologies through mapping mechanisms, direct adoption of standardized upper ontologies (e.g., BFO, DOLCE) could further enhance cross-domain interoperability. Future work will explore hybrid approaches that combine the performance benefits of our purpose-built ontology with the broader interoperability of standardized frameworks.</p></list-item>
<list-item><p><bold>Mapping maintenance:</bold> The semantic mappings between our custom ontology and standard ontologies require periodic updates as both evolve. We plan to implement automated mapping maintenance using machine learning techniques.</p></list-item>
<list-item><p><bold>Domain coverage:</bold> While our framework includes major industrial domains, expansion to additional sectors (e.g., agriculture and maritime) would require further ontology development and alignment efforts.</p></list-item>
</list>
</sec>
</sec>
<sec id="s8">
<label>8</label>
<title>Future directions</title>
<p>The integration of ontological analysis into Digital Twin (DT) systems has opened several avenues for future research and technological advancements. This section discusses unexplored areas where ontological analysis could further benefit DTs, the role of emerging technologies in advancing ontology-driven DTs, and suggestions for applying this approach in untapped industries.</p>
<sec>
<label>8.1</label>
<title>Research opportunities</title>
<p>Despite the progress made in applying ontological analysis to Digital Twin systems, several areas remain underexplored. Future research could focus on:</p>
<list list-type="bullet">
<list-item><p><bold>Dynamic ontology adaptation:</bold> Investigating methods for dynamically adapting ontologies in response to changes in the operational environment or system requirements. This could enhance the flexibility and responsiveness of Digital Twin systems.</p></list-item>
<list-item><p><bold>Cross-domain ontology integration:</bold> Exploring how ontologies from different domains can be integrated to create more comprehensive Digital Twin models. This could facilitate interoperability between various systems and enhance decision-making across different sectors.</p></list-item>
<list-item><p><bold>User-centric ontology development:</bold> Developing user-centric ontologies that incorporate user feedback and preferences to improve the usability and effectiveness of Digital Twin applications. This approach could lead to more intuitive interfaces and better user experiences.</p></list-item>
<list-item><p><bold>Automated ontology generation:</bold> Researching automated methods for generating ontologies from existing data sources or through machine learning techniques. This could streamline the process of ontology creation and reduce the manual effort required.</p></list-item>
</list>
</sec>
<sec>
<label>8.2</label>
<title>Technological innovations</title>
<p>Emerging technologies play a crucial role in advancing ontology-driven Digital Twins. Key innovations include:</p>
<list list-type="bullet">
<list-item><p><bold>Edge computing:</bold> The deployment of edge computing can enhance the performance of ontology-driven Digital Twins by processing data closer to the source, reducing latency, and improving real-time decision-making capabilities.</p></list-item>
<list-item><p><bold>Artificial intelligence (AI):</bold> AI can be leveraged to enhance semantic reasoning within Digital Twins, enabling more sophisticated data analysis and predictive modeling. Integrating AI with ontological frameworks can lead to smarter, more autonomous systems.</p></list-item>
<list-item><p><bold>Blockchain technology:</bold> Utilizing blockchain for secure data sharing among Digital Twin components can enhance trust and transparency in IoT environments. This integration may also facilitate decentralized ontology management.</p></list-item>
<list-item><p><bold>5G connectivity:</bold> The rollout of 5G networks offers opportunities for improved connectivity and data transfer speeds, enabling more responsive and scalable ontology-driven Digital Twins, particularly in dynamic environments such as smart cities or industrial IoT applications.</p></list-item>
</list>
</sec>
<sec>
<label>8.3</label>
<title>Scalability for new domains</title>
<p>The application of ontology-driven approaches can be expanded into untapped industries. Suggestions include:</p>
<list list-type="bullet">
<list-item><p><bold>Healthcare:</bold> Implementing ontology-driven Digital Twins in healthcare could enable personalized medicine by integrating patient data with real-time monitoring systems, improving treatment outcomes.</p></list-item>
<list-item><p><bold>Agriculture:</bold> In precision agriculture, using ontologies to model various environmental factors can enhance crop management practices, leading to better resource utilization and yield optimization.</p></list-item>
<list-item><p><bold>Transportation:</bold> Ontology-driven Digital Twins could be applied in smart transportation systems to optimize traffic flow, enhance safety measures, and improve overall urban mobility through real-time data integration.</p></list-item>
<list-item><p><bold>Energy management:</bold> In the energy sector, integrating ontological analysis into Digital Twins can facilitate better monitoring and management of renewable energy sources, leading to more efficient energy distribution systems.</p></list-item>
</list>
</sec>
</sec>
<sec sec-type="conclusions" id="s9">
<label>9</label>
<title>Conclusion</title>
<p>In this paper, we explored the integration of ontological analysis into Digital Twin (DT) frameworks, highlighting its potential to enhance system performance across various metrics. Our findings demonstrate that leveraging semantic technologies significantly improves error rates, integration times, scalability, and decision-making accuracy.</p>
<p>The contributions of this research underscore the critical role that ontological analysis plays in enhancing the integration and effectiveness of Digital Twins. By providing a structured framework for data representation and relationships, ontologies enable more accurate simulations and informed decision-making within complex systems.</p>
<p>As we move forward, it is essential to encourage further research and development in ontology-based approaches for Digital Twins. The exploration of dynamic adaptation, cross-domain integration, user-centric design, and automated generation will pave the way for more robust and flexible systems capable of addressing the challenges posed by rapidly evolving industries.</p>
<p>In conclusion, embracing ontology-driven methodologies will not only enhance the capabilities of Digital Twins but also facilitate their adoption across diverse sectors, ultimately contributing to smarter, more efficient operations in an increasingly interconnected world.</p>
</sec>
</body>
<back>
<sec sec-type="data-availability" id="s10">
<title>Data availability statement</title>
<p>The original contributions presented in the study are included in the article/<xref ref-type="supplementary-material" rid="SM1">supplementary material</xref>, further inquiries can be directed to the corresponding author.</p>
</sec>
<sec sec-type="author-contributions" id="s11">
<title>Author contributions</title>
<p>ME: Formal analysis, Investigation, Visualization, Writing &#x02013; review &#x00026; editing, Validation, Funding acquisition, Data curation, Resources, Supervision, Conceptualization, Methodology, Software, Writing &#x02013; original draft, Project administration.</p>
</sec>
<sec sec-type="COI-statement" id="conf1">
<title>Conflict of interest</title>
<p>The author(s) declared that this work was conducted in the absence of any commercial or financial relationships that could be construed as a potential conflict of interest.</p>
</sec>
<sec sec-type="ai-statement" id="s13">
<title>Generative AI statement</title>
<p>The author(s) declared that generative AI was not used in the creation of this manuscript.</p>
<p>Any alternative text (alt text) provided alongside figures in this article has been generated by Frontiers with the support of artificial intelligence and reasonable efforts have been made to ensure accuracy, including review by the authors wherever possible. If you identify any issues, please contact us.</p>
</sec>
<sec sec-type="disclaimer" id="s14">
<title>Publisher&#x00027;s note</title>
<p>All claims expressed in this article are solely those of the authors and do not necessarily represent those of their affiliated organizations, or those of the publisher, the editors and the reviewers. Any product that may be evaluated in this article, or claim that may be made by its manufacturer, is not guaranteed or endorsed by the publisher.</p>
</sec>
<sec sec-type="supplementary-material" id="s15">
<title>Supplementary material</title>
<p>The Supplementary Material for this article can be found online at: <ext-link ext-link-type="uri" xlink:href="https://www.frontiersin.org/articles/10.3389/fcomp.2026.1757450/full#supplementary-material">https://www.frontiersin.org/articles/10.3389/fcomp.2026.1757450/full#supplementary-material</ext-link></p>
<supplementary-material xlink:href="Data_Sheet_1.pdf" id="SM1" mimetype="application/pdf" xmlns:xlink="http://www.w3.org/1999/xlink"/></sec>
<ref-list>
<title>References</title>
<ref id="B1">
<mixed-citation publication-type="journal"><person-group person-group-type="author"><name><surname>Ameri</surname> <given-names>F.</given-names></name> <name><surname>Sormaz</surname> <given-names>D.</given-names></name> <name><surname>Psarommatis</surname> <given-names>F.</given-names></name> <name><surname>Kiritsis</surname> <given-names>D.</given-names></name></person-group> (<year>2022</year>). <article-title>Industrial ontologies for interoperability in agile and resilient manufacturing</article-title>. <source>Int. J. Prod. Res</source>. <volume>60</volume>, <fpage>420</fpage>&#x02013;<lpage>441</lpage>. doi: <pub-id pub-id-type="doi">10.1080/00207543.2021.1987553</pub-id></mixed-citation>
</ref>
<ref id="B2">
<mixed-citation publication-type="journal"><person-group person-group-type="author"><name><surname>Aniakor</surname> <given-names>M.</given-names></name> <name><surname>Cogo</surname> <given-names>V. V.</given-names></name> <name><surname>Ferreira</surname> <given-names>P. M.</given-names></name></person-group> (<year>2024</year>). <article-title>A survey on semantic modeling for building energy management</article-title>. <source>arXiv preprint arXiv:2404.11716</source>.</mixed-citation>
</ref>
<ref id="B3">
<mixed-citation publication-type="book"><person-group person-group-type="author"><name><surname>Bader</surname> <given-names>S. R.</given-names></name> <name><surname>Maleshkova</surname> <given-names>M.</given-names></name></person-group> (<year>2019</year>). <article-title>&#x0201C;The semantic asset administration shell,&#x0201D;</article-title> in <source>International Conference on Semantic Systems</source> (<publisher-loc>Springer</publisher-loc>), <fpage>159</fpage>&#x02013;<lpage>174</lpage>. doi: <pub-id pub-id-type="doi">10.1007/978-3-030-33220-4_12</pub-id></mixed-citation>
</ref>
<ref id="B4">
<mixed-citation publication-type="journal"><person-group person-group-type="author"><name><surname>Bamunuarachchi</surname> <given-names>D.</given-names></name> <name><surname>Banerjee</surname> <given-names>A.</given-names></name> <name><surname>Jayaraman</surname> <given-names>P. P.</given-names></name> <name><surname>Georgakopoulos</surname> <given-names>D.</given-names></name></person-group> (<year>2020</year>). <article-title>&#x0201C;Cyber twins supporting industry 4.0 application development,&#x0201D;</article-title> in <source>Proceedings of the 18th International Conference on Advances in Mobile Computing &#x00026; Multimedia</source>, 64&#x02013;73. doi: <pub-id pub-id-type="doi">10.1145/3428690.3429177</pub-id></mixed-citation>
</ref>
<ref id="B5">
<mixed-citation publication-type="journal"><person-group person-group-type="author"><name><surname>Barth</surname> <given-names>L.</given-names></name> <name><surname>Ehrat</surname> <given-names>M.</given-names></name> <name><surname>Fuchs</surname> <given-names>R.</given-names></name> <name><surname>Haarmann</surname> <given-names>J.</given-names></name></person-group> (<year>2020</year>). <article-title>&#x0201C;Systematization of digital twins: ontology and conceptual framework,&#x0201D;</article-title> in <source>Proceedings of the 3rd International Conference on Information Science and Systems, pages</source> 13&#x02013;23. doi: <pub-id pub-id-type="doi">10.1145/3388176.3388209</pub-id></mixed-citation>
</ref>
<ref id="B6">
<mixed-citation publication-type="journal"><person-group person-group-type="author"><name><surname>Bellini</surname> <given-names>P.</given-names></name> <name><surname>Nesi</surname> <given-names>P.</given-names></name> <name><surname>Pantaleo</surname> <given-names>G.</given-names></name></person-group> (<year>2022</year>). <article-title>IoT-enabled smart cities: a review of concepts, frameworks and key technologies</article-title>. <source>Appl. Sci</source>. <volume>12</volume>:<fpage>1607</fpage>. doi: <pub-id pub-id-type="doi">10.3390/app12031607</pub-id></mixed-citation>
</ref>
<ref id="B7">
<mixed-citation publication-type="journal"><person-group person-group-type="author"><name><surname>Brucherseifer</surname> <given-names>E.</given-names></name> <name><surname>Winter</surname> <given-names>H.</given-names></name> <name><surname>Mentges</surname> <given-names>A.</given-names></name> <name><surname>M&#x000FC;hlh&#x000E4;user</surname> <given-names>M.</given-names></name> <name><surname>Hellmann</surname> <given-names>M.</given-names></name></person-group> (<year>2021</year>). <article-title>Digital twin conceptual framework for improving critical infrastructure resilience</article-title>. <source>at-Automatisierungstechnik</source> <volume>69</volume>, <fpage>1062</fpage>&#x02013;<lpage>1080</lpage>. doi: <pub-id pub-id-type="doi">10.1515/auto-2021-0104</pub-id></mixed-citation>
</ref>
<ref id="B8">
<mixed-citation publication-type="journal"><person-group person-group-type="author"><name><surname>Buchgeher</surname> <given-names>G.</given-names></name> <name><surname>Gabauer</surname> <given-names>D.</given-names></name> <name><surname>Martinez-Gil</surname> <given-names>J.</given-names></name> <name><surname>Ehrlinger</surname> <given-names>L.</given-names></name></person-group> (<year>2021</year>). <article-title>Knowledge graphs in manufacturing and production: a systematic literature review</article-title>. <source>IEEE Access</source> <volume>9</volume>, <fpage>55537</fpage>&#x02013;<lpage>55554</lpage>. doi: <pub-id pub-id-type="doi">10.1109/ACCESS.2021.3070395</pub-id></mixed-citation>
</ref>
<ref id="B9">
<mixed-citation publication-type="journal"><person-group person-group-type="author"><name><surname>Chen</surname> <given-names>J.</given-names></name> <name><surname>Hu</surname> <given-names>P.</given-names></name> <name><surname>Jimenez-Ruiz</surname> <given-names>E.</given-names></name> <name><surname>Holter</surname> <given-names>O. M.</given-names></name> <name><surname>Antonyrajah</surname> <given-names>D.</given-names></name> <name><surname>Horrocks</surname> <given-names>I.</given-names></name></person-group> (<year>2021</year>). <article-title>OWL2Vec<sup>&#x0002A;</sup>: embedding of OWL ontologies</article-title>. <source>Mach. Learn.</source> <volume>110</volume>, <fpage>1813</fpage>&#x02013;<lpage>1845</lpage>. doi: <pub-id pub-id-type="doi">10.1007/s10994-021-05997-6</pub-id></mixed-citation>
</ref>
<ref id="B10">
<mixed-citation publication-type="journal"><person-group person-group-type="author"><name><surname>El-Hajj</surname> <given-names>M.</given-names></name></person-group> (<year>2024</year>). <article-title>Leveraging digital twins and intrusion detection systems for enhanced security in iot-based smart city infrastructures</article-title>. <source>Electronics</source> <volume>13</volume>:<fpage>3941</fpage>. doi: <pub-id pub-id-type="doi">10.3390/electronics13193941</pub-id></mixed-citation>
</ref>
<ref id="B11">
<mixed-citation publication-type="journal"><person-group person-group-type="author"><name><surname>El-Hajj</surname> <given-names>M.</given-names></name> <name><surname>It&#x000E4;pelto</surname> <given-names>T.</given-names></name> <name><surname>Gebremariam</surname> <given-names>T.</given-names></name></person-group> (<year>2024</year>). <article-title>Systematic literature review: digital twins&#x00027; role in enhancing security for industry 4.0 applications</article-title>. <source>Secur. Privacy</source> <volume>7</volume>:<fpage>e396</fpage>. doi: <pub-id pub-id-type="doi">10.1002/spy2.396</pub-id></mixed-citation>
</ref>
<ref id="B12">
<mixed-citation publication-type="journal"><person-group person-group-type="author"><name><surname>El-Sappagh</surname> <given-names>S.</given-names></name> <name><surname>Elmogy</surname> <given-names>M.</given-names></name> <name><surname>Riad</surname> <given-names>A.</given-names></name></person-group> (<year>2015</year>). <article-title>A fuzzy-ontology-oriented case-based reasoning framework for semantic diabetes diagnosis</article-title>. <source>Artif. Intell. Med</source>. <volume>65</volume>, <fpage>179</fpage>&#x02013;<lpage>208</lpage>. doi: <pub-id pub-id-type="doi">10.1016/j.artmed.2015.08.003</pub-id><pub-id pub-id-type="pmid">26303105</pub-id></mixed-citation>
</ref>
<ref id="B13">
<mixed-citation publication-type="book"><person-group person-group-type="author"><name><surname>Falquet</surname> <given-names>G.</given-names></name> <name><surname>M&#x000E9;tral</surname> <given-names>C.</given-names></name> <name><surname>Teller</surname> <given-names>J.</given-names></name> <name><surname>Tweed</surname> <given-names>C.</given-names></name></person-group> (<year>2012</year>). <article-title>&#x0201C;Ontologies in urban development projects,&#x0201D;</article-title> in <source>Advanced Information and Knowledge Processing</source> (<publisher-loc>London</publisher-loc>: <publisher-name>Springer</publisher-name>), <fpage>7</fpage>&#x02013;<lpage>34</lpage>. doi: <pub-id pub-id-type="doi">10.1007/978-0-85729-724-2</pub-id></mixed-citation>
</ref>
<ref id="B14">
<mixed-citation publication-type="thesis"><person-group person-group-type="author"><name><surname>Friederich</surname> <given-names>J.</given-names></name></person-group> (<year>2023</year>). <source>Data-driven assessment of reliability for cyber-physical production systems</source>. Ph.D. thesis.</mixed-citation>
</ref>
<ref id="B15">
<mixed-citation publication-type="book"><person-group person-group-type="author"><name><surname>Furrer</surname> <given-names>F.</given-names></name> <name><surname>Burri</surname> <given-names>M.</given-names></name> <name><surname>Achtelik</surname> <given-names>M.</given-names></name> <name><surname>Siegwart</surname> <given-names>R.</given-names></name></person-group> (<year>2016</year>). <article-title>&#x0201C;Rotors&#x02014;a modular gazebo mav simulator framework,&#x0201D;</article-title> in <source>Robot Operating System (ROS) The Complete Reference</source> (<publisher-loc>Springer</publisher-loc>), <fpage>595</fpage>&#x02013;<lpage>625</lpage>. doi: <pub-id pub-id-type="doi">10.1007/978-3-319-26054-9_23</pub-id></mixed-citation>
</ref>
<ref id="B16">
<mixed-citation publication-type="book"><person-group person-group-type="author"><name><surname>Gowripeddi</surname> <given-names>V. V.</given-names></name> <name><surname>Sasirekha</surname> <given-names>G.</given-names></name> <name><surname>Bapat</surname> <given-names>J.</given-names></name> <name><surname>Das</surname> <given-names>D.</given-names></name></person-group> (<year>2023</year>). <article-title>&#x0201C;Digital twin and ontology based ddos attack detection in a smart-factory 4.0,&#x0201D;</article-title> in <source>2023 International Conference on Artificial Intelligence in Information and Communication (ICAIIC)</source> (<publisher-loc>IEEE</publisher-loc>), <fpage>286</fpage>&#x02013;<lpage>291</lpage>. doi: <pub-id pub-id-type="doi">10.1109/ICAIIC57133.2023.10067049</pub-id></mixed-citation>
</ref>
<ref id="B17">
<mixed-citation publication-type="thesis"><person-group person-group-type="author"><name><surname>Guizzardi</surname> <given-names>G.</given-names></name></person-group> (<year>2005</year>). <source>Ontological foundations for structural conceptual models</source>. Ph.D. thesis.</mixed-citation>
</ref>
<ref id="B18">
<mixed-citation publication-type="journal"><person-group person-group-type="author"><name><surname>Guizzardi</surname> <given-names>G.</given-names></name> <name><surname>Guarino</surname> <given-names>N.</given-names></name></person-group> (<year>2024</year>). <article-title>Explanation, semantics, and ontology</article-title>. <source>Data Knowl. Eng</source>. <volume>153</volume>:<fpage>102325</fpage>. doi: <pub-id pub-id-type="doi">10.1016/j.datak.2024.102325</pub-id></mixed-citation>
</ref>
<ref id="B19">
<mixed-citation publication-type="journal"><person-group person-group-type="author"><name><surname>Horrocks</surname> <given-names>I.</given-names></name> <name><surname>Patel-Schneider</surname> <given-names>P. F.</given-names></name> <name><surname>Van Harmelen</surname> <given-names>F.</given-names></name></person-group> (<year>2003</year>). <article-title>From SHIQ and RDF to OWL: the making of a web ontology language</article-title>. <source>J. Web Semant</source>. <volume>1</volume>, <fpage>7</fpage>&#x02013;<lpage>26</lpage>. doi: <pub-id pub-id-type="doi">10.1016/j.websem.2003.07.001</pub-id></mixed-citation>
</ref>
<ref id="B20">
<mixed-citation publication-type="book"><person-group person-group-type="author"><name><surname>It&#x000E4;pelto</surname> <given-names>T.</given-names></name></person-group> (<year>2023</year>). <article-title>&#x0201C;Digital twin enhanced critical infrastructure life cycle security,&#x0201D;</article-title> in <source>2023 IEEE Smart World Congress (SWC)</source> (<publisher-loc>IEEE</publisher-loc>), <fpage>1</fpage>&#x02013;<lpage>3</lpage>. doi: <pub-id pub-id-type="doi">10.1109/SWC57546.2023.10448804</pub-id></mixed-citation>
</ref>
<ref id="B21">
<mixed-citation publication-type="journal"><person-group person-group-type="author"><name><surname>Janowicz</surname> <given-names>K.</given-names></name> <name><surname>Haller</surname> <given-names>A.</given-names></name> <name><surname>Cox</surname> <given-names>S. J.</given-names></name> <name><surname>Le Phuoc</surname> <given-names>D.</given-names></name> <name><surname>Lefran&#x000E7;ois</surname> <given-names>M.</given-names></name></person-group> (<year>2019</year>). <article-title>Sosa: a lightweight ontology for sensors, observations, samples, and actuators</article-title>. <source>J. Web Semant</source>. <volume>56</volume>, <fpage>1</fpage>&#x02013;<lpage>10</lpage>. doi: <pub-id pub-id-type="doi">10.1016/j.websem.2018.06.003</pub-id></mixed-citation>
</ref>
<ref id="B22">
<mixed-citation publication-type="book"><person-group person-group-type="author"><name><surname>Jim&#x000E9;nez-Ruiz</surname> <given-names>E.</given-names></name> <name><surname>Cuenca Grau</surname> <given-names>B.</given-names></name></person-group> (<year>2011</year>). <article-title>&#x0201C;Logmap: logic-based and scalable ontology matching,&#x0201D;</article-title> in <source>International Semantic Web Conference</source> (<publisher-loc>Springer</publisher-loc>), <fpage>273</fpage>&#x02013;<lpage>288</lpage>. doi: <pub-id pub-id-type="doi">10.1007/978-3-642-25073-6_18</pub-id></mixed-citation>
</ref>
<ref id="B23">
<mixed-citation publication-type="journal"><person-group person-group-type="author"><name><surname>Johnson</surname> <given-names>A. E.</given-names></name> <name><surname>Pollard</surname> <given-names>T. J.</given-names></name> <name><surname>Shen</surname> <given-names>L.</given-names></name> <name><surname>Lehman</surname> <given-names>L.-,w,. H.</given-names></name> <name><surname>Feng</surname> <given-names>M.</given-names></name> <name><surname>Ghassemi</surname> <given-names>M.</given-names></name> <etal/></person-group>. (<year>2016</year>). <article-title>Mimic-iii, a freely accessible critical care database</article-title>. <source>Sci. Data</source> <volume>3</volume>, <fpage>1</fpage>&#x02013;<lpage>9</lpage>. doi: <pub-id pub-id-type="doi">10.1038/sdata.2016.35</pub-id><pub-id pub-id-type="pmid">27219127</pub-id></mixed-citation>
</ref>
<ref id="B24">
<mixed-citation publication-type="book"><person-group person-group-type="author"><name><surname>Kendall</surname> <given-names>E. F.</given-names></name> <name><surname>McGuinness</surname> <given-names>D. L.</given-names></name></person-group> (<year>2019</year>). <source>Ontology Engineering</source>. <publisher-loc>San Rafael, CA</publisher-loc>: <publisher-name>Morgan and Claypool Publishers</publisher-name>.</mixed-citation>
</ref>
<ref id="B25">
<mixed-citation publication-type="journal"><person-group person-group-type="author"><name><surname>Kritzinger</surname> <given-names>W.</given-names></name> <name><surname>Karner</surname> <given-names>M.</given-names></name> <name><surname>Traar</surname> <given-names>G.</given-names></name> <name><surname>Henjes</surname> <given-names>J.</given-names></name> <name><surname>Sihn</surname> <given-names>W.</given-names></name></person-group> (<year>2018</year>). <article-title>Digital twin in manufacturing: a categorical literature review and classification</article-title>. <source>Ifac-PapersOnline</source> <volume>51</volume>, <fpage>1016</fpage>&#x02013;<lpage>1022</lpage>. doi: <pub-id pub-id-type="doi">10.1016/j.ifacol.2018.08.474</pub-id></mixed-citation>
</ref>
<ref id="B26">
<mixed-citation publication-type="book"><person-group person-group-type="author"><name><surname>Kulvatunyou</surname> <given-names>B.</given-names></name> <name><surname>Wallace</surname> <given-names>E.</given-names></name> <name><surname>Kiritsis</surname> <given-names>D.</given-names></name> <name><surname>Smith</surname> <given-names>B.</given-names></name> <name><surname>Will</surname> <given-names>C.</given-names></name></person-group> (<year>2018</year>). <article-title>&#x0201C;The industrial ontologies foundry proof-of-concept project,&#x0201D;</article-title> in <source>IFIP International Conference on Advances in Production Management Systems</source> (<publisher-loc>Springer</publisher-loc>), <fpage>402</fpage>&#x02013;<lpage>409</lpage>. doi: <pub-id pub-id-type="doi">10.1007/978-3-319-99707-0_50</pub-id></mixed-citation>
</ref>
<ref id="B27">
<mixed-citation publication-type="journal"><person-group person-group-type="author"><name><surname>L&#x000E4;mmel</surname> <given-names>G.</given-names></name></person-group> (<year>2017</year>). <source>Simulation of urban mobility&#x02013;sumo: Key features and uses</source>. Jaxenter Newsletter.</mixed-citation>
</ref>
<ref id="B28">
<mixed-citation publication-type="journal"><person-group person-group-type="author"><name><surname>Li</surname> <given-names>T.</given-names></name> <name><surname>Li</surname> <given-names>X.</given-names></name> <name><surname>Rui</surname> <given-names>Y.</given-names></name> <name><surname>Ling</surname> <given-names>J.</given-names></name> <name><surname>Zhao</surname> <given-names>S.</given-names></name> <name><surname>Zhu</surname> <given-names>H.</given-names></name></person-group> (<year>2024</year>). <article-title>Digital twin for intelligent tunnel construction</article-title>. <source>Autom. Constr</source>. <volume>158</volume>:<fpage>105210</fpage>. doi: <pub-id pub-id-type="doi">10.1016/j.autcon.2023.105210</pub-id></mixed-citation>
</ref>
<ref id="B29">
<mixed-citation publication-type="journal"><person-group person-group-type="author"><name><surname>Liu</surname> <given-names>M.</given-names></name> <name><surname>Fang</surname> <given-names>S.</given-names></name> <name><surname>Dong</surname> <given-names>H.</given-names></name> <name><surname>Xu</surname> <given-names>C.</given-names></name></person-group> (<year>2021</year>). <article-title>Review of digital twin about concepts, technologies, and industrial applications</article-title>. <source>J. Manuf. Syst</source>. <volume>58</volume>, <fpage>346</fpage>&#x02013;<lpage>361</lpage>. doi: <pub-id pub-id-type="doi">10.1016/j.jmsy.2020.06.017</pub-id></mixed-citation>
</ref>
<ref id="B30">
<mixed-citation publication-type="journal"><person-group person-group-type="author"><name><surname>Ma</surname> <given-names>J.</given-names></name> <name><surname>Guo</surname> <given-names>Y.</given-names></name> <name><surname>Fang</surname> <given-names>C.</given-names></name> <name><surname>Zhang</surname> <given-names>Q.</given-names></name></person-group> (<year>2022</year>). <article-title>Digital twin-based zero-touch management for iot</article-title>. <source>Electronics</source> <volume>11</volume>:<fpage>4104</fpage>. doi: <pub-id pub-id-type="doi">10.3390/electronics11244104</pub-id></mixed-citation>
</ref>
<ref id="B31">
<mixed-citation publication-type="book"><person-group person-group-type="author"><name><surname>Masolo</surname> <given-names>C.</given-names></name> <name><surname>Borgo</surname> <given-names>S.</given-names></name> <name><surname>Gangemi</surname> <given-names>A.</given-names></name> <name><surname>Guarino</surname> <given-names>N.</given-names></name> <name><surname>Oltramari</surname> <given-names>A.</given-names></name></person-group> (<year>2003</year>). <source>The Wonderweb Library of Foundational Ontologies and the DOLCE Ontology</source>. <publisher-loc>Trento, Italy</publisher-loc>: <publisher-name>WonderWeb Deliverable D18</publisher-name>.</mixed-citation>
</ref>
<ref id="B32">
<mixed-citation publication-type="journal"><collab>Microsoft Azure</collab> (<year>2023a</year>). <source>Concepts: Digital twins definition language (dtdl)</source>. Documentation for the modeling language used by Azure Digital Twins.</mixed-citation>
</ref>
<ref id="B33">
<mixed-citation publication-type="journal"><collab>Microsoft Azure</collab> (<year>2023b</year>). <source>What is azure digital twins</source>? Official documentation for the Azure Digital Twins service.</mixed-citation>
</ref>
<ref id="B34">
<mixed-citation publication-type="journal"><collab>Microsoft Azure</collab> (<year>2023c</year>). <source>What is azure iot hub</source>? Official documentation for the Azure IoT Hub service.</mixed-citation>
</ref>
<ref id="B35">
<mixed-citation publication-type="journal"><person-group person-group-type="author"><name><surname>Mihai</surname> <given-names>S.</given-names></name> <name><surname>Davis</surname> <given-names>W.</given-names></name> <name><surname>Hung</surname> <given-names>D.</given-names></name> <name><surname>Trestian</surname> <given-names>R.</given-names></name> <name><surname>Karamanoglu</surname> <given-names>M.</given-names></name> <name><surname>Barn</surname> <given-names>B.</given-names></name> <etal/></person-group>. (<year>2021</year>). <article-title>&#x0201C;A digital twin framework for predictive maintenance in industry 4.0,&#x0201D;</article-title> in <source>HPCS 2020: 18th Annual Meeting</source>, 80y5z.</mixed-citation>
</ref>
<ref id="B36">
<mixed-citation publication-type="journal"><person-group person-group-type="author"><name><surname>Noy</surname> <given-names>N. F.</given-names></name> <name><surname>McGuinness</surname> <given-names>D. L.</given-names></name></person-group> (<year>2001</year>). <source>Ontology development 101: a guide to creating your first ontology</source>. Technical report, Stanford Knowledge Systems Laboratory. Technical Report KSL-<fpage>01</fpage>&#x02013;<lpage>05</lpage>.</mixed-citation>
</ref>
<ref id="B37">
<mixed-citation publication-type="journal"><person-group person-group-type="author"><name><surname>Nunez</surname> <given-names>D. L.</given-names></name> <name><surname>Borsato</surname> <given-names>M.</given-names></name></person-group> (<year>2017</year>). <article-title>An ontology-based model for prognostics and health management of machines</article-title>. <source>J. Ind. Inf. Integr</source>. <volume>6</volume>, <fpage>33</fpage>&#x02013;<lpage>46</lpage>. doi: <pub-id pub-id-type="doi">10.1016/j.jii.2017.02.006</pub-id></mixed-citation>
</ref>
<ref id="B38">
<mixed-citation publication-type="journal"><person-group person-group-type="author"><name><surname>Otte</surname> <given-names>J. N.</given-names></name> <name><surname>Beverley</surname> <given-names>J.</given-names></name> <name><surname>Ruttenberg</surname> <given-names>A.</given-names></name></person-group> (<year>2022</year>). <article-title>BFO: basic formal ontology</article-title>. <source>Appl. Ontol</source>. <volume>17</volume>, <fpage>17</fpage>&#x02013;<lpage>43</lpage>. doi: <pub-id pub-id-type="doi">10.3233/AO-220262</pub-id></mixed-citation>
</ref>
<ref id="B39">
<mixed-citation publication-type="journal"><person-group person-group-type="author"><name><surname>Peng</surname> <given-names>C.</given-names></name> <name><surname>Xia</surname> <given-names>F.</given-names></name> <name><surname>Naseriparsa</surname> <given-names>M.</given-names></name> <name><surname>Osborne</surname> <given-names>F.</given-names></name></person-group> (<year>2023</year>). <article-title>Knowledge graphs: opportunities and challenges</article-title>. <source>Artif. Intell. Rev</source>. <volume>56</volume>, <fpage>13071</fpage>&#x02013;<lpage>13102</lpage>. doi: <pub-id pub-id-type="doi">10.1007/s10462-023-10465-9</pub-id><pub-id pub-id-type="pmid">37362886</pub-id></mixed-citation>
</ref>
<ref id="B40">
<mixed-citation publication-type="journal"><person-group person-group-type="author"><name><surname>Pliatsios</surname> <given-names>A.</given-names></name> <name><surname>Kotis</surname> <given-names>K.</given-names></name> <name><surname>Goumopoulos</surname> <given-names>C.</given-names></name></person-group> (<year>2023</year>). <article-title>A systematic review on semantic interoperability in the ioe-enabled smart cities</article-title>. <source>Internet Things</source> <volume>22</volume>:<fpage>100754</fpage>. doi: <pub-id pub-id-type="doi">10.1016/j.iot.2023.100754</pub-id></mixed-citation>
</ref>
<ref id="B41">
<mixed-citation publication-type="book"><person-group person-group-type="author"><name><surname>Ploennigs</surname> <given-names>J.</given-names></name> <name><surname>Semertzidis</surname> <given-names>K.</given-names></name> <name><surname>Lorenzi</surname> <given-names>F.</given-names></name> <name><surname>Mihindukulasooriya</surname> <given-names>N.</given-names></name></person-group> (<year>2022</year>). <article-title>&#x0201C;Scaling knowledge graphs for automating AI of digital twins,&#x0201D;</article-title> in <source>International Semantic Web Conference</source> (<publisher-loc>Springer</publisher-loc>), <fpage>810</fpage>&#x02013;<lpage>826</lpage>. doi: <pub-id pub-id-type="doi">10.1007/978-3-031-19433-7_46</pub-id></mixed-citation>
</ref>
<ref id="B42">
<mixed-citation publication-type="journal"><person-group person-group-type="author"><name><surname>Poveda-Villal&#x000F3;n</surname> <given-names>M.</given-names></name> <name><surname>G&#x000F3;mez-P&#x000E9;rez</surname> <given-names>A.</given-names></name> <name><surname>Su&#x000E1;rez-Figueroa</surname> <given-names>M. C.</given-names></name></person-group> (<year>2014</year>). <article-title>&#x0201C;Oops!(ontology pitfall scanner!): an on-line tool for ontology evaluation</article-title>. <source>Int. J. Semant. Web Inf. Syst</source>. <volume>10</volume>, <fpage>7</fpage>&#x02013;<lpage>34</lpage>. doi: <pub-id pub-id-type="doi">10.4018/ijswis.2014040102</pub-id></mixed-citation>
</ref>
<ref id="B43">
<mixed-citation publication-type="book"><person-group person-group-type="author"><name><surname>Shao</surname> <given-names>G.</given-names></name></person-group> (<year>2021</year>). <source>Use case scenarios for digital twin implementation based on iso 23247</source>. <publisher-loc>Gaithersburg, MD, USA</publisher-loc>: <publisher-name>National institute of standards</publisher-name>, <fpage>400</fpage>&#x02013;<lpage>402</lpage>. doi: <pub-id pub-id-type="doi">10.6028/NIST.AMS.400-2</pub-id></mixed-citation>
</ref>
<ref id="B44">
<mixed-citation publication-type="web"><collab>Shivamb</collab> (<year>2025</year>). <source>Machine predictive maintenance classification</source>. Available online at: <ext-link ext-link-type="uri" xlink:href="https://www.kaggle.com/datasets/shivamb/machine-predictive-maintenance-classification">https://www.kaggle.com/datasets/shivamb/machine-predictive-maintenance-classification</ext-link> (Accessed September, 2025).</mixed-citation>
</ref>
<ref id="B45">
<mixed-citation publication-type="book"><person-group person-group-type="author"><name><surname>Skobelev</surname> <given-names>P.</given-names></name> <name><surname>Mayorov</surname> <given-names>I.</given-names></name> <name><surname>Simonova</surname> <given-names>E.</given-names></name> <name><surname>Goryanin</surname> <given-names>O.</given-names></name> <name><surname>Zhilyaev</surname> <given-names>A.</given-names></name> <name><surname>Tabachinskiy</surname> <given-names>A.</given-names></name> <etal/></person-group>. (<year>2020</year>). <article-title>&#x0201C;Development of models and methods for creating a digital twin of plant within the cyber-physical system for precision farming management,&#x0201D;</article-title> in <source>Journal of Physics: Conference Series</source> (<publisher-loc>IOP Publishing</publisher-loc>), <fpage>012022</fpage>. doi: <pub-id pub-id-type="doi">10.1088/1742-6596/1703/1/012022</pub-id></mixed-citation>
</ref>
<ref id="B46">
<mixed-citation publication-type="book"><person-group person-group-type="author"><name><surname>Su&#x000E1;rez-Figueroa</surname> <given-names>M. C.</given-names></name> <name><surname>G&#x000F3;mez-P&#x000E9;rez</surname> <given-names>A.</given-names></name> <name><surname>Motta</surname> <given-names>E.</given-names></name> <name><surname>Gangemi</surname> <given-names>A.</given-names></name></person-group> (<year>2011</year>). <article-title>&#x0201C;Introduction: ontology engineering in a networked world,&#x0201D;</article-title> in <source>Ontology Engineering in a Networked World</source> (<publisher-loc>Springer</publisher-loc>), <fpage>1</fpage>&#x02013;<lpage>6</lpage>. doi: <pub-id pub-id-type="doi">10.1007/978-3-642-24794-1_1</pub-id></mixed-citation>
</ref>
<ref id="B47">
<mixed-citation publication-type="book"><person-group person-group-type="author"><name><surname>Sure</surname> <given-names>Y.</given-names></name> <name><surname>Staab</surname> <given-names>S.</given-names></name> <name><surname>Studer</surname> <given-names>R.</given-names></name></person-group> (<year>2009</year>). <article-title>&#x0201C;Ontology engineering methodology,&#x0201D;</article-title> in <source>Handbook on Ontologies</source> (<publisher-loc>Springer</publisher-loc>), <fpage>135</fpage>&#x02013;<lpage>152</lpage>. doi: <pub-id pub-id-type="doi">10.1007/978-3-540-92673-3_6</pub-id></mixed-citation>
</ref>
<ref id="B48">
<mixed-citation publication-type="web"><collab>The MITRE Corporation</collab> (<year>2025</year>). <source>Synthea: synthetic patient population simulator (github repository)</source>. Available online at: <ext-link ext-link-type="uri" xlink:href="https://github.com/synthetichealth/synthea">https://github.com/synthetichealth/synthea</ext-link> (Accessed September, 2025).</mixed-citation>
</ref>
<ref id="B49">
<mixed-citation publication-type="journal"><person-group person-group-type="author"><name><surname>Tripathi</surname> <given-names>D. R.</given-names></name> <name><surname>Nishad</surname> <given-names>D. K.</given-names></name></person-group> (<year>2019</year>). <article-title>Digital twin technology: concepts and applications</article-title>. <source>Turkish J. Comput. Mathem. Educ</source>. <volume>10</volume>, <fpage>1660</fpage>&#x02013;<lpage>1665</lpage>. doi: <pub-id pub-id-type="doi">10.61841/turcomat.v10i3.14627</pub-id></mixed-citation>
</ref>
<ref id="B50">
<mixed-citation publication-type="book"><person-group person-group-type="author"><name><surname>van der Wal</surname> <given-names>E. W.</given-names></name> <name><surname>El-Hajj</surname> <given-names>M.</given-names></name></person-group> (<year>2022</year>). <article-title>&#x0201C;Securing networks of IoT devices with digital twins and automated adversary emulation,&#x0201D;</article-title> in <source>2022 26th International Computer Science and Engineering Conference (ICSEC)</source> (<publisher-loc>IEEE</publisher-loc>), <fpage>241</fpage>&#x02013;<lpage>246</lpage>. doi: <pub-id pub-id-type="doi">10.1109/ICSEC56337.2022.10049355</pub-id></mixed-citation>
</ref>
<ref id="B51">
<mixed-citation publication-type="journal"><person-group person-group-type="author"><name><surname>Zhou</surname> <given-names>J.</given-names></name> <name><surname>Breslin</surname> <given-names>J. G.</given-names></name> <name><surname>Ali</surname> <given-names>M. I.</given-names></name></person-group> (<year>2021</year>). <article-title>Semantic web and knowledge graphs for industry 4.0</article-title>. <source>Appl. Sci</source>. <volume>11</volume>:<fpage>5110</fpage>. doi: <pub-id pub-id-type="doi">10.3390/app11115110</pub-id></mixed-citation>
</ref>
<ref id="B52">
<mixed-citation publication-type="book"><person-group person-group-type="author"><name><surname>Zhou</surname> <given-names>J.</given-names></name> <name><surname>Ma</surname> <given-names>L.</given-names></name> <name><surname>Liu</surname> <given-names>Q.</given-names></name> <name><surname>Zhang</surname> <given-names>L.</given-names></name> <name><surname>Yu</surname> <given-names>Y.</given-names></name> <name><surname>Pan</surname> <given-names>Y.</given-names></name></person-group> (<year>2006</year>). <article-title>&#x0201C;Minerva: a scalable owl ontology storage and inference system,&#x0201D;</article-title> in <source>The Semantic Web-ASWC 2006: First Asian Semantic Web Conference, Beijing, China, September 3&#x02013;7, 2006. Proceedings 1</source> (<publisher-loc>Springer</publisher-loc>), <fpage>429</fpage>&#x02013;<lpage>443</lpage>. doi: <pub-id pub-id-type="doi">10.1007/11836025_42</pub-id></mixed-citation>
</ref>
</ref-list>
<fn-group>
<fn fn-type="custom" custom-type="edited-by" id="fn0001">
<p>Edited by: <ext-link ext-link-type="uri" xlink:href="https://loop.frontiersin.org/people/1140892/overview">Sebastian Maneth</ext-link>, University of Bremen, Germany</p>
</fn>
<fn fn-type="custom" custom-type="reviewed-by" id="fn0002">
<p>Reviewed by: <ext-link ext-link-type="uri" xlink:href="https://loop.frontiersin.org/people/919857/overview">Foivos Psarommatis</ext-link>, University of Oslo, Norway</p>
<p><ext-link ext-link-type="uri" xlink:href="https://loop.frontiersin.org/people/3313118/overview">Thierry Louge</ext-link>, &#x000C9;cole Nationale d&#x00027;Ing&#x000E9;nieurs de Tarbes, France</p>
</fn>
</fn-group>
</back>
</article>