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

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-03-twin-node-requirements:twin-005-acquire-twin-state:twin-005d-identify-the-twin-state-data-source [2026/08/20 17:14] – removed nick_didodido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-03-twin-node-requirements:twin-005-acquire-twin-state:twin-005d-identify-the-twin-state-data-source [2026/08/20 17:14] (current) – created nick_dido
Line 1: Line 1:
 +====== TWIN-005d — Identify the State Data Source ======
  
 +[[dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-03-twin-node-requirements:twin-005-acquire-twin-state:start|Go to TWIN-005 — Access Twin Realization State]]
 +
 +===== Statement =====
 +
 +The [[dido:99_annexes:annex-b-terms-and-definitions:d:dido-te|DIDO-TE]] SHALL identify the [[dido:99_annexes:annex-b-terms-and-definitions:d:data_source|Data Source]] from which each accessed state value of a [[dido:99_annexes:annex-b-terms-and-definitions:t:twin_realization|Twin Realization]] originated.
 +
 +===== Source =====
 +
 +  * [[dido:03-dido-te:99-annexes:annex-b-references:dte-001|[DTE1] U.S. Patent Application US20220237111A1]], virtual and physical Twin Node concepts, baseline results, and comparison of results
 +  * [[dido:03-dido-te:99-annexes:annex-b-references:dte-002|[DTE2] Non-Traditional BAA Submission]], Digital Twin concepts, monitoring, and Twin Nodes Selection
 +  * [[dido:03-dido-te:99-annexes:annex-b-references:dte-009|[DTE9] Distributed Immutable Data Object Reference Architecture (DIDO-RA)]], distributed data and DDS publish-subscribe concepts
 +
 +===== Rationale =====
 +
 +A [[dido:99_annexes:annex-b-terms-and-definitions:t:twin_relationship|Twin Relationship]] may use more than one eligible [[dido:99_annexes:annex-b-terms-and-definitions:d:data_source|Data Source]] for the same represented characteristic.
 +
 +Identification of the Data Source preserves the origin of each accessed state value and prevents values from different sources from becoming indistinguishable after access.
 +
 +Data Source identification remains distinct from source eligibility and [[dido:99_annexes:annex-b-terms-and-definitions:s:source_selection|Source Selection]]. Eligibility defines the permitted set of Data Sources. Source Selection determines which eligible source supplies data for a defined purpose. This requirement identifies the source from which a particular accessed state value originated.
 +
 +A communication endpoint, DDS DataWriter, network address, or other transport identifier does not replace Data Source identity unless the governing [[dido:99_annexes:annex-b-terms-and-definitions:c:configuration|Configuration]] establishes that correspondence.
 +
 +===== Applies To =====
 +
 +  * [[dido:99_annexes:annex-b-terms-and-definitions:d:dido-te|DIDO-TE]]
 +  * [[dido:99_annexes:annex-b-terms-and-definitions:d:data_source|Data Source]]
 +  * [[dido:99_annexes:annex-b-terms-and-definitions:s:source_selection|Source Selection]]
 +  * [[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]]
 +
 +===== Verification =====
 +
 +Verification confirms that:
 +
 +  - Each accessed state value has an identifiable Data Source.
 +  - The identified Data Source corresponds to the origin of the accessed state value.
 +  - Data Sources supplying values for the same represented characteristic remain distinguishable.
 +  - The Data Source identity remains associated with the accessed state value.
 +  - A transport endpoint or communication entity does not replace Data Source identity unless the governing Configuration establishes that correspondence.
 +  - Identification of the Data Source remains distinguishable from Data Source eligibility and Source Selection.
 +
 +Verification includes state values for the same represented characteristic obtained from at least two Data Sources and confirms that the originating Data Source of each value remains identifiable.
 +
 +===== Traceability =====
 +
 +{{backlinks>.}}
 +
 +===== ConOps Relationship =====
 +
 +This requirement preserves the origin of accessed state values for subsequent synchronization, comparison, Validation, evidence generation, and Test Execution analysis.
 +
 +===== 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-005-acquire-twin-state:twin-005d-identify-the-twin-state-data-source#Statement&noheader&nofooter&noeditbtn}}
 +</code>
 +
 +----
 +
 +<WRAP centeralign>
 +© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
 +</WRAP>
  • dido/03-dido-te/99-annexes/annex-c-requirements/03-functional-requirements/03-03-twin-node-requirements/twin-005-acquire-twin-state/twin-005d-identify-the-twin-state-data-source.1787271243.txt.gz
  • Last modified: 2026/08/20 17:14
  • by nick_dido