TWIN-002 — Associate Twin Realizations [Dido Solutions, Inc Wiki]

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== TWIN-002 — Associate Twin Realizations ======

[[dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-03-twin-node-requirements:start|Go to C.3.3 Twin Node Requirements]]

TWIN-002 is a non-leaf requirement group governing the association of one or more [[dido:99_annexes:annex-b-terms-and-definitions:t:twin_realization|Twin Realizations]] with a common [[dido:99_annexes:annex-b-terms-and-definitions:t:twin_identity|Twin Identity]].

The association establishes which individual realizations participate in the same logical twin while preserving the distinction between the logical Twin Identity and each realization.

A Twin Identity may be associated with more than one Twin Realization, including virtual and physical or real-world realizations.

Conformance is assessed against the individual leaf requirements listed below. TWIN-002 does not establish a separate conformance obligation.

===== Requirements =====

^ Requirement ID ^ Requirement Title ^ Purpose ^
| TWIN-002a | Associate a Twin Realization with a Twin Identity | Establish the relationship between an individual Twin Realization and its Twin Identity. |
| TWIN-002b | Support Multiple Twin Realizations | Permit more than one Twin Realization to be associated with the same Twin Identity. |
| TWIN-002c | Preserve Twin Realization Association | Preserve the association between a Twin Realization and its Twin Identity throughout the applicable lifecycle. |
| TWIN-002d | Remove a Twin Realization Association | Remove an association without changing the identity of the remaining Twin Realizations or the Twin Identity. |

===== Contents =====

{{indexmenu>dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-03-twin-node-requirements:twin-002-associate-twin-realizations#1|js navbar nocookie maxjs#1 id#dido_te_twin_002_requirements_nav}}

===== Source =====

  * [[dido:03-dido-te:99-annexes:annex-b-references:dte-001|[DTE1] U.S. Patent Application US20220237111A1]], virtual and physical Twin Node concepts and identifiers shared among Twin Nodes
  * [[dido:03-dido-te:99-annexes:annex-b-references:dte-002|[DTE2] Non-Traditional BAA Submission]], F17, //Twin Nodes Selection//
  * [[dido:03-dido-te:99-annexes:annex-b-references:dte-009|[DTE9] Distributed Immutable Data Object Reference Architecture (DIDO-RA)]], Appendix A, //Digital Twin//

===== Rationale =====

A [[dido:99_annexes:annex-b-terms-and-definitions:t:twin_identity|Twin Identity]] represents the logical twin independently of any particular [[dido:99_annexes:annex-b-terms-and-definitions:t:twin_realization|Twin Realization]].

Associating individual Twin Realizations with that Twin Identity allows the [[dido:99_annexes:annex-b-terms-and-definitions:d:dido-te|DIDO-TE]] to identify which realizations represent the same logical twin while preserving each realization as a distinct object.

The association supports selection between virtual and physical or real-world Twin Realizations during [[dido:99_annexes:annex-b-terms-and-definitions:t:test_execution|Test Execution]] without changing the Twin Identity.

===== Applies To =====

  * [[dido:99_annexes:annex-b-terms-and-definitions:d:dido-te|DIDO-TE]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:t:twin_identity|Twin Identity]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:t:twin_identifier|Twin Identifier]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:t:twin_realization|Twin Realization]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:t:twin_realization_identifier|Twin Realization Identifier]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:t:twin_node|Twin Node]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:t:test_execution|Test Execution]]

===== Traceability =====

{{backlinks>.}}

===== ConOps Relationship =====

This requirement group supports ConOps activities that register Twin Realizations, associate them with a Twin Identity, select among alternative realizations, and retire associations without changing the identity of the logical twin.

===== Delivery Phase =====

TBD

===== Requirement Status =====

Draft

----

===== Notes for Editors =====

TWIN-002 is a non-leaf requirement group and does not contain an independent normative Statement or Verification section.

The explicit links under Contents remain while the subordinate requirement pages are being created and reviewed. After all child pages exist, the explicit links may be removed because the ''indexmenu'' automatically discovers them.

The association between a Twin Identity and a Twin Realization is a semantic relationship. Do not define the relationship solely through container membership, network addressing, DDS discovery, Topic matching, or another realization-specific mechanism.

----

<WRAP centeralign>
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
</WRAP>