Differences

This shows you the differences between two versions of the page.

--- dido:99_annexes:annex-b-terms-and-definitions:d:digital_twin [2026/08/19 18:36] – nick_dido
+++ dido:99_annexes:annex-b-terms-and-definitions:d:digital_twin [2026/08/19 18:51] (current) – nick_dido
@@ Line 5: / Line 5: @@
 ===== Discussion =====
-A Digital Twin provides a digital representation of a referent whose relevant state, behavior, configuration, and lifecycle characteristics are represented through controlled data.
+A Digital Twin provides a digital representation of a referent whose relevant state, behavior, [[dido:99_annexes:annex-b-terms-and-definitions:c:configuration|Configuration]], and lifecycle characteristics are represented through controlled data.
-The referent may be a physical asset, software component, process, system, or other identifiable subject. The relationship between the referent and its Digital Twin may support observation, simulation, comparison, prediction, synchronization, or controlled interaction.
+The referent may be a physical asset, software component, process, system, or other identifiable subject. The relationship between the referent and its Digital Twin supports observation, simulation, comparison, prediction, synchronization, or controlled interaction according to the applicable purpose and requirements.
-The DIDO Reference Architecture describes a Digital Twin in terms of a real-world item, a software representation, and the data linking the two. It also identifies simulation, predictive modeling, state monitoring, and response to observed state as Digital Twin uses. :contentReference[oaicite:1]{index=1}
+The DIDO Reference Architecture describes a Digital Twin in terms of a real-world item, a software representation, and the data linking the two. It also identifies simulation, predictive modeling, state monitoring, and response to observed state as Digital Twin uses. [[dido:03-dido-te:99-annexes:annex-b-references:dte-009|[DTE9]]], Appendix A, //Digital Twin//.
-Within DIDO Solutions architectures, the concept is applied more generally to permit the referent to be physical, virtual, logical, or software-defined.
+Within DIDO Solutions architectures, the concept is generalized so that the referent may be physical, virtual, logical, or software-defined.
 ===== Definition =====
@@ Line 19: / Line 19: @@
 ===== Source =====
-  * [[https://www.omgwiki.org/dido/doku.php?id=dido:public:ra:xapend:xapend.a_glossary:d:digital_twin|DIDO Reference Architecture — Digital Twin]]
+  * [[dido:03-dido-te:99-annexes:annex-b-references:dte-009|[DTE9]]], Appendix A, //Digital Twin//
   * DIDO Solutions normalization of the DIDO Reference Architecture concept for physical, virtual, logical, and software-defined referents
 ===== Note =====
-A Digital Twin does not require every characteristic of the referent to be represented. The applicable purpose, requirements, or configuration determine which characteristics participate in the twin relationship.
+A Digital Twin does not require representation of every characteristic of its referent. The applicable purpose, requirements, or Configuration identify the characteristics participating in the twin relationship.
-A Digital Twin also does not imply bidirectional control. Observation, synchronization, simulation, and control are separate capabilities and require explicit architectural treatment.
+A Digital Twin does not imply bidirectional control. Observation, synchronization, simulation, comparison, and control are distinct capabilities requiring explicit architectural treatment.
+The data relating a Digital Twin to its referent forms part of the twin relationship. Communication mechanisms transport this data but do not, by themselves, establish its semantic meaning, authority, or required fidelity.
 ===== Example =====
-A Digital Twin of a deployed service may represent the service's configuration, operational state, observed inputs and outputs, resource conditions, and selected behavior for comparison with expected or simulated behavior.
+A Digital Twin of a deployed service represents selected Configuration, operational state, observed inputs and outputs, resource conditions, and behavior for comparison with expected or simulated behavior.
 ----