dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-03-twin-node-requirements:twin-005-acquire-twin-state:twin-005c-identify-twin-state-source

This is an old revision of the document!


TWIN-005c — Identify Twin State Source

The DIDO-TE SHALL identify the Data Source of each accessed Twin State value.

A Twin Relationship may obtain values for the same represented characteristic from multiple eligible Data Sources.

Identification of the Data Source preserves the origin of each accessed Twin State value and prevents values from different sources from becoming indistinguishable after access.

Source identification is distinct from source eligibility and Source Selection. Eligibility determines which Data Sources are permitted to provide data, Source Selection determines which eligible source supplies data for a defined purpose, and this requirement identifies the source that produced the accessed value.

A communication endpoint, DDS DataWriter, network address, or other transport identifier does not replace Data Source identity unless the governing Configuration explicitly establishes that correspondence.

Verification confirms that:

  1. Each accessed Twin State value has an identifiable Data Source.
  2. The identified Data Source is distinguishable from other Data Sources capable of supplying the represented characteristic.
  3. The source associated with an accessed value corresponds to the source from which that value originated.
  4. Values obtained from different Data Sources remain distinguishable by source.
  5. A transport endpoint or communication entity does not replace Data Source identity unless the governing Configuration establishes that correspondence.
  6. The identified Data Source is traceable to the accessed Twin State value.

Verification includes access to values for the same represented characteristic from at least two Data Sources and confirms that the source of each value remains identifiable.

This requirement preserves the origin of accessed Twin State values for subsequent synchronization, comparison, Validation, evidence generation, and Test Execution analysis.

TBD

Draft

{{section>dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-03-twin-node-requirements:twin-005-acquire-twin-state:twin-005c-identify-twin-state-source#Statement&noheader&nofooter&noeditbtn}}

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

  • dido/03-dido-te/99-annexes/annex-c-requirements/03-functional-requirements/03-03-twin-node-requirements/twin-005-acquire-twin-state/twin-005c-identify-twin-state-source.1787270109.txt.gz
  • Last modified: 2026/08/20 16:55
  • by nick_dido