TWIN-002 — Associate Twin Realizations

Go to C.3.3 Twin Node Requirements

TWIN-002 is a non-leaf requirement group governing the association of one or more Twin Realizations with a common 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

Source

, virtual and physical Twin Node concepts and identifiers shared among Twin Nodes[DTE2] Non-Traditional BAA Submission, F17, Twin Nodes Selection[DTE9] Distributed Immutable Data Object Reference Architecture (DIDO-RA), Appendix A, Digital Twin

Rationale

A Twin Identity represents the logical twin independently of any particular Twin Realization.

Associating individual Twin Realizations with that Twin Identity allows the 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 Test Execution without changing the Twin Identity.

Applies To

Traceability

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.

© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.