TWIN-003a — Identify Represented Twin Characteristics

Go to TWIN-003 — Configure a Twin Relationship

Statement

The DIDO-TE SHALL identify the characteristics of each Twin Realization that participate in the applicable Twin Relationship.

Source

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

Rationale

A Digital Twin does not necessarily represent every characteristic of its referent.

A twin relationship therefore requires an explicit identification of the characteristics that participate in that relationship. These characteristics establish the scope within which a Twin Realization is observed, synchronized, simulated, selected, or compared.

Represented characteristics may include selected state, behavior, Configuration, communication, timing, resource, or lifecycle characteristics when those characteristics are applicable to the purpose of the twin relationship.

Explicit identification prevents characteristics that happen to be observable or technically available from becoming part of the twin relationship without architectural intent.

Applies To

Verification

Verification confirms that:

Each configured twin relationship identifies the characteristics that participate in the relationship.An identified characteristic is associated with the applicable Twin Identity or Twin Realization.A characteristic not identified as participating in the twin relationship is not treated as a required basis for synchronization, simulation, comparison, or validation.The identified characteristics remain distinguishable from implementation-specific mechanisms used to observe or exchange their values.The identified characteristics can be traced to the applicable Configuration, Test Definition, requirement, or other governing source.Verification includes inspection of a twin relationship in which only a subset of the available characteristics of a Twin Realization participates in the relationship.

Traceability

ConOps Relationship

This requirement supports configuration of the scope of a twin relationship before data mappings, source eligibility, source selection, synchronization, simulation, or comparison are established.

Delivery Phase

TBD

Requirement Status

Draft

Statement Reference

{{section>dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-03-twin-node-requirements:twin-003-configure-a-twin-relationship:twin-003a-identify-represented-twin-characteristics#Statement&noheader&nofooter&noeditbtn}}

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