Differences

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

--- 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 [2026/08/20 16:55] – created nick_dido
+++ 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 [2026/08/20 16:59] (current) – removed nick_dido
@@ Line 1: / Line 1: @@
-====== TWIN-005c — Identify Twin State 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 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]] of each accessed [[dido:99_annexes:annex-b-terms-and-definitions:t:twin_state|Twin State]] value.
-===== 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 results
-  * [[dido:03-dido-te:99-annexes:annex-b-references:dte-002|[DTE2] Non-Traditional BAA Submission]], Digital Twin concepts, real-time 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 obtain values for the same represented characteristic from multiple eligible [[dido:99_annexes:annex-b-terms-and-definitions:d:data_source|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 [[dido:99_annexes:annex-b-terms-and-definitions:s:source_selection|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.
-===== 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_state|Twin State]]
-  * [[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:c:configuration|Configuration]]
-  * [[dido:99_annexes:annex-b-terms-and-definitions:d:dds|DDS]]
-===== Verification =====
-Verification confirms that:
-  - Each accessed Twin State value has an identifiable Data Source.
-  - The identified Data Source is distinguishable from other Data Sources capable of supplying the represented characteristic.
-  - The source associated with an accessed value corresponds to the source from which that value originated.
-  - Values obtained from different Data Sources remain distinguishable by source.
-  - A transport endpoint or communication entity does not replace Data Source identity unless the governing Configuration establishes that correspondence.
-  - 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.
-===== Traceability =====
-{{backlinks>.}}
-===== ConOps Relationship =====
-This requirement preserves the origin of accessed Twin 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-005c-identify-twin-state-source#Statement&noheader&nofooter&noeditbtn}}
-</code>
-----
-<WRAP centeralign>
-© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
-</WRAP>