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-005a-identify-twin-state [2026/08/20 16:54] – 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-005a-identify-twin-state [2026/08/20 16:58] (current) – removed nick_dido
@@ Line 1: / Line 1: @@
-====== TWIN-005a — Identify Twin State ======
-[[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:t:twin_state|Twin State]] represented by each [[dido:99_annexes:annex-b-terms-and-definitions:t:twin_realization|Twin Realization]] participating in a [[dido:99_annexes:annex-b-terms-and-definitions:t:twin_relationship|Twin Relationship]].
-===== 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 Twin Node behavior
-  * [[dido:03-dido-te:99-annexes:annex-b-references:dte-002|[DTE2] Non-Traditional BAA Submission]], Digital Twin concepts, monitoring, scenario testing, and Twin Nodes Selection
-  * [[dido:03-dido-te:99-annexes:annex-b-references:dte-009|[DTE9] Distributed Immutable Data Object Reference Architecture (DIDO-RA)]], Digital Twin and distributed data concepts
-===== Rationale =====
-A [[dido:99_annexes:annex-b-terms-and-definitions:t:twin_realization|Twin Realization]] may expose or contain information beyond the state represented within a [[dido:99_annexes:annex-b-terms-and-definitions:t:twin_relationship|Twin Relationship]].
-Identification of [[dido:99_annexes:annex-b-terms-and-definitions:t:twin_state|Twin State]] establishes which represented state participates in monitoring, synchronization, simulation, comparison, Validation, or Test Execution.
-The identified Twin State derives from the represented characteristics and [[dido:99_annexes:annex-b-terms-and-definitions:t:twin_data_mapping|Twin Data Mappings]] established for the Twin Relationship.
-Information that is technically observable does not become Twin State solely because it is available from a Twin Realization.
-===== 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: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]]
-===== Verification =====
-Verification confirms that:
-  - Each participating Twin Realization has identified Twin State.
-  - The identified Twin State corresponds to characteristics represented by the Twin Relationship.
-  - The identified Twin State is distinguishable from information outside the represented scope of the Twin Relationship.
-  - The identified Twin State is traceable to the governing Configuration or Twin Data Mapping.
-  - Availability of additional information from a Twin Realization does not add that information to the identified Twin State.
-Verification includes a Twin Realization that exposes both represented and non-represented information and confirms that only represented state is identified as Twin State.
-===== Traceability =====
-{{backlinks>.}}
-===== ConOps Relationship =====
-This requirement establishes the Twin State subject to subsequent value access, source identification, temporal association, provenance preservation, synchronization, simulation, comparison, and Validation.
-===== 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-005a-identify-twin-state#Statement&noheader&nofooter&noeditbtn}}
-</code>
-----
-<WRAP centeralign>
-© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
-</WRAP>