dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-03-twin-node-requirements:twin-010-maintain-twin-traceability:start

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-010-maintain-twin-traceability:start [2026/08/22 14:31] – removed - external edit (Unknown date) 127.0.0.1dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-03-twin-node-requirements:twin-010-maintain-twin-traceability:start [2026/08/22 14:31] (current) – ↷ Page moved and renamed from dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-03-twin-node-requirements:twin-010-maintain-twin-traceability to dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-03-t nick_dido
Line 1: Line 1:
 +====== TWIN-010 — Maintain Twin Traceability ======
  
 +[[dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-03-twin-node-requirements:start|Go to C.3.3 Twin Node Requirements]]
 +
 +===== Statement =====
 +
 +The [[dido:99_annexes:annex-b-terms-and-definitions:d:dido-te|DIDO-TE]] SHALL maintain [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] among each [[dido:99_annexes:annex-b-terms-and-definitions:t:twin_identity|Twin Identity]], its associated [[dido:99_annexes:annex-b-terms-and-definitions:t:twin_realization|Twin Realizations]], and the [[dido:99_annexes:annex-b-terms-and-definitions:t:test_result|Test Results]] produced using those Twin Realizations.
 +
 +===== Source =====
 +
 +  * [[dido:03-dido-te:99-annexes:annex-b-references:dte-001|[DTE1] U.S. Patent Application US20220237111A1]], virtual and physical Twin Node concepts, shared identifiers, test-result comparison, and validation
 +  * [[dido:03-dido-te:99-annexes:annex-b-references:dte-002|[DTE2] Non-Traditional BAA Submission]], Digital Twin concepts, Twin Nodes Selection, monitoring, scenario testing, and comparison testing
 +  * DIDO-TE Traceability requirements
 +
 +===== Rationale =====
 +
 +A [[dido:99_annexes:annex-b-terms-and-definitions:t:twin_identity|Twin Identity]] may be represented by more than one [[dido:99_annexes:annex-b-terms-and-definitions:t:twin_realization|Twin Realization]] during different Test Executions or different portions of a Test Execution.
 +
 +Meaningful comparison, reproduction, validation, and audit therefore require the DIDO-TE to retain the relationship between the logical Twin Identity and the particular Twin Realization that participated in a test.
 +
 +The resulting [[dido:99_annexes:annex-b-terms-and-definitions:t:test_result|Test Results]] must remain attributable to the Twin Realization that produced them and to the Twin Identity represented by that realization.
 +
 +Traceability remains independent of whether the Twin Realization is virtual, physical, simulated, or otherwise realized.
 +
 +===== 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_identity|Twin Identity]]
 +  * [[dido:99_annexes:annex-b-terms-and-definitions:t:twin_identifier|Twin Identifier]]
 +  * [[dido:99_annexes:annex-b-terms-and-definitions:t:twin_realization|Twin Realization]]
 +  * [[dido:99_annexes:annex-b-terms-and-definitions:t:twin_realization_identifier|Twin Realization Identifier]]
 +  * [[dido:99_annexes:annex-b-terms-and-definitions:t:twin_realization_type|Twin Realization Type]]
 +  * [[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:t:test_result|Test Result]]
 +  * [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]]
 +
 +===== Verification =====
 +
 +Verification confirms that:
 +
 +  - Each Twin Realization used during Test Execution is traceable to its Twin Identity.
 +  - Each Twin Realization used during Test Execution is identifiable by its Twin Realization Identifier.
 +  - Each Test Result produced using a Twin Realization is traceable to that Twin Realization.
 +  - Each Test Result produced using a Twin Realization is traceable through that realization to the corresponding Twin Identity.
 +  - Traceability distinguishes Test Results produced by different Twin Realizations associated with the same Twin Identity.
 +  - Traceability is preserved when different Twin Realizations of the same Twin Identity are selected for different Test Executions.
 +
 +Verification includes at least two Twin Realizations associated with the same Twin Identity, uses the realizations in separate Test Executions, and confirms that the resulting Test Results remain attributable to the correct Twin Realization and Twin Identity.
 +
 +===== Traceability =====
 +
 +{{backlinks>.}}
 +
 +===== ConOps Relationship =====
 +
 +This requirement supports reproducibility, comparison, validation, evidence generation, and audit by preserving the relationship among Twin Identity, Twin Realization, Test Execution, and Test Result.
 +
 +===== 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-010-maintain-twin-traceability#Statement&noheader&nofooter&noeditbtn}}
 +</code>
 +
 +----
 +
 +<WRAP centeralign>
 +© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
 +</WRAP>