Twin Realization Type
Discussion
A Twin Realization Type classifies a Twin Realization according to the nature of the realization rather than according to its implementation technology, deployment location, or resource identifier.
The source material distinguishes virtual Twin Nodes from physical or real-world Twin Nodes. DIDO-TE uses Twin Realization Type to preserve this distinction while allowing additional governed realization types where required by the applicable architecture or Configuration.
A Twin Realization Type belongs to a controlled vocabulary so that Test Definitions, Test Executions, comparison activities, and Traceability use consistent realization classifications.
The classification identifies what kind of realization participates in a Twin Identity. It does not identify the individual realization. The Twin Realization Identifier performs that function.
Definition
a classification assigned to a Twin Realization that identifies the nature of the realization
Source
-
[DTE1] U.S. Patent Application US20220237111A1, virtual and physical Twin Node concepts
-
[DTE2] Non-Traditional BAA Submission, F17, Twin Nodes Selection
-
[DTE9] Distributed Immutable Data Object Reference Architecture (DIDO-RA), Appendix A, Digital Twin
-
DIDO-TE normalization of the source concepts
Note
The controlled vocabulary includes, at minimum, realization types that distinguish:
-
Virtual
-
Physical or real-world
Additional realization types require explicit definition within the applicable governed vocabulary.
A Twin Realization Type does not identify:
-
The Twin Identity
-
The Twin Identifier
-
The individual Twin Realization
-
A particular container, process, host, platform, DDS entity, or deployment mechanism
Example
A Twin Identity has two Twin Realizations:
-
TR-101, classified asVirtual -
TR-102, classified asPhysical
Both realizations represent the same Twin Identity while their Twin Realization Types distinguish the nature of each realization.
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.