====== TWIN-005e — Associate Twin Realization State with Time ====== [[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 associate each determined state of a [[dido:99_annexes:annex-b-terms-and-definitions:t:twin_realization|Twin Realization]] with the time information required to interpret that state. ===== 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 test results, modification of Twin Nodes, 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 scenario testing * [[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 ===== The state of a [[dido:99_annexes:annex-b-terms-and-definitions:t:twin_realization|Twin Realization]] represents the condition of its represented characteristics at a particular time. Without temporal context, two otherwise identical state values may represent different conditions in a Test Execution, and state changes may not be ordered or compared reliably. The required time information may include timestamps, sequence-related temporal information, synchronization references, or other time data established by the governing [[dido:99_annexes:annex-b-terms-and-definitions:c:configuration|Configuration]] or [[dido:99_annexes:annex-b-terms-and-definitions:t:test_definition|Test Definition]]. Temporal association remains distinct from communication latency, [[dido:99_annexes:annex-b-terms-and-definitions:q:qos|Quality of Service]], and [[dido:99_annexes:annex-b-terms-and-definitions:s:synchronization_parameter|Synchronization Parameters]], although those concepts may influence interpretation of time-related behavior. ===== 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_realization|Twin Realization]] * [[dido:99_annexes:annex-b-terms-and-definitions:t:twin_relationship|Twin Relationship]] * [[dido:99_annexes:annex-b-terms-and-definitions:c:configuration|Configuration]] * [[dido:99_annexes:annex-b-terms-and-definitions:t:test_definition|Test Definition]] * [[dido:99_annexes:annex-b-terms-and-definitions:t:test_execution|Test Execution]] * [[dido:99_annexes:annex-b-terms-and-definitions:s:synchronization_parameter|Synchronization Parameter]] * [[dido:99_annexes:annex-b-terms-and-definitions:q:qos|Quality of Service]] ===== Verification ===== Verification confirms that: - Each determined state of a Twin Realization has associated time information. - The associated time information is sufficient to place the determined state within the temporal context defined by the governing Configuration or Test Definition. - States determined at different times remain temporally distinguishable. - The temporal association remains linked to the Twin Realization whose state was determined. - Communication latency or middleware timing does not replace the required state time information unless the governing Configuration establishes that correspondence. - The associated time information supports ordering or comparison of determined states when such ordering or comparison is required. Verification includes at least two determined states of the same Twin Realization at different times and confirms that their temporal relationship is distinguishable. ===== Traceability ===== {{backlinks>.}} ===== ConOps Relationship ===== This requirement provides the temporal context required to interpret changes in the state of a Twin Realization during Test Execution, synchronization, comparison, Validation, monitoring, and evidence generation. ===== Delivery Phase ===== TBD ===== Requirement Status ===== Draft ===== Statement Reference ===== {{section>dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-03-twin-node-requirements:twin-005-acquire-twin-state:twin-005e-associate-twin-state-with-time#Statement&noheader&nofooter&noeditbtn}} ---- © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.