| Next 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:13] – 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-005d-identify-the-twin-state-data-source [2026/08/20 17:14] (current) – created nick_dido |
|---|
| ====== TWIN-005c — Access Twin Realization State Values ====== | ====== 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]] | [[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 ===== | ===== Statement ===== |
| |
| The [[dido:99_annexes:annex-b-terms-and-definitions:d:dido-te|DIDO-TE]] SHALL provide access to the values that constitute the determined state of each [[dido:99_annexes:annex-b-terms-and-definitions:t:twin_realization|Twin Realization]] participating in [[dido:99_annexes:annex-b-terms-and-definitions:t:test_execution|Test Execution]]. | 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 ===== | ===== Source ===== |
| |
| * [[dido:03-dido-te:99-annexes:annex-b-references:dte-001|[DTE1] U.S. Patent Application US20220237111A1]], virtual and physical Twin Node concepts, observation of Twin Node behavior, baseline results, and comparison of results | * [[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, real-time monitoring, scenario testing, and Twin Nodes Selection | * [[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)]], Digital Twin and distributed data concepts | * [[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 ===== | ===== Rationale ===== |
| |
| Determination of the state of a [[dido:99_annexes:annex-b-terms-and-definitions:t:twin_realization|Twin Realization]] identifies its current condition. Test Execution, synchronization, simulation, comparison, and Validation also require access to the values from which that state is determined. | 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. |
| |
| The [[dido:99_annexes:annex-b-terms-and-definitions:t:twin_data_mapping|Twin Data Mapping]] establishes the semantic correspondence between represented characteristics and their data representations. This requirement ensures that the resulting state values remain accessible independently of the mechanism used to obtain or transport them. | Identification of the Data Source preserves the origin of each accessed state value and prevents values from different sources from becoming indistinguishable after access. |
| |
| Access to a state value does not, by itself, establish its [[dido:99_annexes:annex-b-terms-and-definitions:d:data_source|Data Source]], temporal context, provenance, eligibility, or authority. Those concerns are governed separately. | 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 ===== | ===== Applies To ===== |
| |
| * [[dido:99_annexes:annex-b-terms-and-definitions:d:dido-te|DIDO-TE]] | * [[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_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_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:t:twin_data_mapping|Twin Data Mapping]] |
| * [[dido:99_annexes:annex-b-terms-and-definitions:d:data_source|Data Source]] | |
| * [[dido:99_annexes:annex-b-terms-and-definitions:c:configuration|Configuration]] | * [[dido:99_annexes:annex-b-terms-and-definitions:c:configuration|Configuration]] |
| * [[dido:99_annexes:annex-b-terms-and-definitions:t:test_execution|Test Execution]] | * [[dido:99_annexes:annex-b-terms-and-definitions:d:dds|DDS]] |
| |
| ===== Verification ===== | ===== Verification ===== |
| Verification confirms that: | Verification confirms that: |
| |
| - The values that constitute the determined state of each participating Twin Realization can be accessed. | - Each accessed state value has an identifiable Data Source. |
| - Each accessed value corresponds to a represented characteristic of the governing Twin Relationship. | - The identified Data Source corresponds to the origin of the accessed state value. |
| - Each accessed value conforms to the governing Twin Data Mapping. | - Data Sources supplying values for the same represented characteristic remain distinguishable. |
| - Values outside the represented scope of the Twin Relationship are not treated as state values solely because they are technically accessible. | - The Data Source identity remains associated with the accessed state value. |
| - Access to state values remains independent of the implementation-specific communication mechanism used to obtain those values. | - A transport endpoint or communication entity does not replace Data Source identity unless the governing Configuration establishes that correspondence. |
| - Each accessed state value remains associated with the Twin Realization whose state it represents. | - Identification of the Data Source remains distinguishable from Data Source eligibility and Source Selection. |
| |
| Verification includes access to the values constituting the determined state of at least one Twin Realization during Test Execution. | 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 ===== | ===== Traceability ===== |
| ===== ConOps Relationship ===== | ===== ConOps Relationship ===== |
| |
| This requirement provides access to the values that constitute the determined state of a Twin Realization for synchronization, simulation, comparison, Validation, monitoring, and evidence generation. | This requirement preserves the origin of accessed state values for subsequent synchronization, comparison, Validation, evidence generation, and Test Execution analysis. |
| |
| ===== Delivery Phase ===== | ===== Delivery Phase ===== |
| |
| <code dokuwiki> | <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-access-twin-state-values#Statement&noheader&nofooter&noeditbtn}} | {{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> | </code> |
| |