====== TWIN-003b — Configure Twin Data Mappings ======

[[dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-03-twin-node-requirements:twin-003-configure-a-twin-relationship:start|Go to TWIN-003 — Configure a Twin Relationship]]

===== Statement =====

The [[dido:99_annexes:annex-b-terms-and-definitions:d:dido-te|DIDO-TE]] SHALL configure a [[dido:99_annexes:annex-b-terms-and-definitions:t:twin_data_mapping|Twin Data Mapping]] for each represented characteristic requiring correspondence among participating [[dido:99_annexes:annex-b-terms-and-definitions:t:twin_realization|Twin Realizations]].

===== 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 comparison of Twin Node behavior
  * [[dido:03-dido-te:99-annexes:annex-b-references:dte-002|[DTE2] Non-Traditional BAA Submission]], Digital Twin concepts and 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//, and DDS data-distribution concepts

===== Rationale =====

A [[dido:99_annexes:annex-b-terms-and-definitions:t:twin_relationship|Twin Relationship]] identifies the characteristics represented across its [[dido:99_annexes:annex-b-terms-and-definitions:t:twin_realization|Twin Realizations]]. The participating realizations need not represent those characteristics using identical data structures, names, types, units, encodings, or communication mechanisms.

A [[dido:99_annexes:annex-b-terms-and-definitions:t:twin_data_mapping|Twin Data Mapping]] identifies the correspondence between a represented characteristic and the data used to represent that characteristic in the participating Twin Realizations.

Explicit data mappings prevent implementation-specific names, DDS Topics, field names, data types, units, or encodings from implicitly determining semantic correspondence.

The mapping also provides a controlled basis for state acquisition, synchronization, simulation, comparison, and [[dido:99_annexes:annex-b-terms-and-definitions:v:validation|Validation]] across heterogeneous Twin Realizations.

===== 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_relationship|Twin Relationship]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:t:twin_realization|Twin Realization]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:t:twin_data_mapping|Twin Data Mapping]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:c:configuration|Configuration]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:d:dds|DDS]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:t:test_definition|Test Definition]]

===== Verification =====

Verification confirms that:

  - Each represented characteristic requiring correspondence has a Twin Data Mapping.
  - Each Twin Data Mapping identifies the represented characteristic to which it applies.
  - Each Twin Data Mapping identifies the corresponding data used by the participating Twin Realizations.
  - Different names, data structures, types, units, or encodings remain distinguishable within the mapping.
  - A communication mechanism or technically compatible data representation does not establish semantic correspondence in the absence of an applicable Twin Data Mapping.
  - Each Twin Data Mapping is traceable to the applicable Twin Relationship Configuration.

Verification includes a Twin Relationship in which at least two Twin Realizations represent the same characteristic using different data representations.

===== Traceability =====

{{backlinks>.}}

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

This requirement supports Configuration of semantic correspondence among Twin Realizations before state acquisition, synchronization, simulation, comparison, or Validation occurs.

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

TBD

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

Draft

===== Statement Reference =====

<code dokuwiki>
{{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-003b-configure-twin-data-mappings#Statement&noheader&nofooter&noeditbtn}}
</code>

----

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