| Both sides previous revision Previous revision 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:start [2026/08/20 16:58] – nick_dido | dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-03-twin-node-requirements:twin-005-acquire-twin-state:start [2026/08/20 17:32] (current) – nick_dido |
|---|
| ====== TWIN-005 — Access Twin State ====== | ====== TWIN-005 — Access Twin Realization State ====== |
| |
| [[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]] | [[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]] |
| |
| TWIN-005 is a non-leaf requirement group governing establishment, determination, access, and contextualization of the [[dido:99_annexes:annex-b-terms-and-definitions:t:twin_state|Twin State]] of a [[dido:99_annexes:annex-b-terms-and-definitions:t:twin_realization|Twin Realization]] within a [[dido:99_annexes:annex-b-terms-and-definitions:t:twin_relationship|Twin Relationship]]. | TWIN-005 is a non-leaf requirement group governing establishment, determination, access, and contextualization of the state of a [[dido:99_annexes:annex-b-terms-and-definitions:t:twin_realization|Twin Realization]] within a [[dido:99_annexes:annex-b-terms-and-definitions:t:twin_relationship|Twin Relationship]]. |
| |
| Twin State represents the condition of the characteristics represented by a Twin Realization at a specified time. The Twin State therefore provides a controlled basis for synchronization, simulation, comparison, Validation, and Test Execution. | The state of a Twin Realization describes the condition of the characteristics represented by that Twin Realization at a specified time. That state provides a controlled basis for synchronization, simulation, comparison, [[dido:99_annexes:annex-b-terms-and-definitions:v:validation|Validation]], and [[dido:99_annexes:annex-b-terms-and-definitions:t:test_execution|Test Execution]]. |
| |
| Access to Twin State includes establishment of an initial state, determination of the current state, access to state values, identification of the originating [[dido:99_annexes:annex-b-terms-and-definitions:d:data_source|Data Source]], association of state with time, preservation of provenance, and detection of an invalid or unknown state. | Access to the state of a Twin Realization includes establishment of an initial state, determination of its current state, access to state values, identification of the originating [[dido:99_annexes:annex-b-terms-and-definitions:d:data_source|Data Source]], association of state with time, preservation of provenance, and detection of an invalid or unknown state. |
| |
| The communication mechanism used to obtain Twin State does not, by itself, establish the semantic meaning, validity, source eligibility, authority, or temporal context of that state. | The communication mechanism used to obtain state information does not, by itself, establish the semantic meaning, validity, source eligibility, authority, or temporal context of that state. |
| |
| Conformance is assessed against the individual leaf requirements listed below. TWIN-005 does not establish a separate conformance obligation. | Conformance is assessed against the individual leaf requirements listed below. TWIN-005 does not establish a separate conformance obligation. |
| |
| ^ Requirement ID ^ Requirement Title ^ Purpose ^ | ^ Requirement ID ^ Requirement Title ^ Purpose ^ |
| | TWIN-005a | Establish the Initial Twin State | Establish a controlled starting state for a Twin Realization before its use in Test Execution. | | | TWIN-005a | Establish the Initial State of a Twin Realization | Establish a controlled starting state for a Twin Realization before its use in Test Execution. | |
| | TWIN-005b | Determine the Current Twin State | Determine the current condition of the represented characteristics of a Twin Realization. | | | TWIN-005b | Determine the Current State of a Twin Realization | Determine the current condition of the represented characteristics of a Twin Realization. | |
| | TWIN-005c | Access Twin State Values | Provide access to the values that constitute the determined Twin State. | | | TWIN-005c | Access Twin Realization State Values | Provide access to the values that constitute the determined state of a Twin Realization. | |
| | TWIN-005d | Identify the Twin State Data Source | Identify the Data Source from which each Twin State value originated. | | | TWIN-005d | Identify the State Data Source | Identify the Data Source from which each accessed state value originated. | |
| | TWIN-005e | Associate Twin State with Time | Associate Twin State with the temporal information required to interpret that state. | | | TWIN-005e | Associate Twin Realization State with Time | Associate the state of a Twin Realization with the temporal information required to interpret that state. | |
| | TWIN-005f | Preserve Twin State Provenance | Preserve provenance associated with Twin State and its constituent values. | | | TWIN-005f | Preserve Twin Realization State Provenance | Preserve provenance associated with the state of a Twin Realization and its constituent values. | |
| | TWIN-005g | Detect an Invalid or Unknown Twin State | Detect when the state of a Twin Realization cannot be established as valid and known. | | | TWIN-005g | Detect an Invalid or Unknown Twin Realization State | Detect when the state of a Twin Realization cannot be established as valid and known. | |
| |
| ===== Contents ===== | ===== Contents ===== |
| |
| * [[dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-03-twin-node-requirements:twin-005-acquire-twin-state:twin-005a-establish-the-initial-twin-state|TWIN-005a — Establish the Initial Twin State]] | |
| * [[dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-03-twin-node-requirements:twin-005-acquire-twin-state:twin-005b-determine-the-current-twin-state|TWIN-005b — Determine the Current Twin State]] | |
| * [[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|TWIN-005c — Access Twin State Values]] | |
| * [[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|TWIN-005d — Identify the Twin 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:twin-005e-associate-twin-state-with-time|TWIN-005e — Associate Twin 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:twin-005f-preserve-twin-state-provenance|TWIN-005f — Preserve Twin State Provenance]] | |
| * [[dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-03-twin-node-requirements:twin-005-acquire-twin-state:twin-005g-detect-an-invalid-or-unknown-twin-state|TWIN-005g — Detect an Invalid or Unknown Twin State]] | |
| |
| {{indexmenu>dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-03-twin-node-requirements:twin-005-acquire-twin-state#1|js navbar nocookie maxjs#1 id#dido_te_twin_005_requirements_nav}} | {{indexmenu>dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-03-twin-node-requirements:twin-005-acquire-twin-state#1|js navbar nocookie maxjs#1 id#dido_te_twin_005_requirements_nav}} |
| ===== Rationale ===== | ===== Rationale ===== |
| |
| A [[dido:99_annexes:annex-b-terms-and-definitions:t:twin_relationship|Twin Relationship]] represents selected characteristics of a logical twin through one or more [[dido:99_annexes:annex-b-terms-and-definitions:t:twin_realization|Twin Realizations]]. Testing requires more than access to isolated values. The DIDO-TE requires a controlled understanding of the condition represented by those characteristics. | A [[dido:99_annexes:annex-b-terms-and-definitions:t:twin_relationship|Twin Relationship]] represents selected characteristics of a logical twin through one or more [[dido:99_annexes:annex-b-terms-and-definitions:t:twin_realization|Twin Realizations]]. Testing requires more than access to isolated values. The DIDO-TE requires a controlled understanding of each participating Twin Realization's state. |
| |
| 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. Twin State establishes the condition represented by those characteristics at a specified time. | 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. The state of a Twin Realization describes the condition represented by those characteristics at a specified time. |
| |
| Establishing an initial Twin State provides a controlled starting point for Test Execution. Determining the current Twin State provides the basis for observing subsequent changes and comparing actual state with expected or previously established state. | Establishing the initial state of a Twin Realization provides a controlled starting point for Test Execution. Determining its current state provides the basis for observing subsequent changes and comparing actual state with expected or previously established state. |
| |
| Twin State access remains distinct from Data Source eligibility and [[dido:99_annexes:annex-b-terms-and-definitions:s:source_selection|Source Selection]]. A technically available value does not establish valid Twin State solely because the value is reachable or received through a communication mechanism. | Access to state remains distinct from Data Source eligibility and [[dido:99_annexes:annex-b-terms-and-definitions:s:source_selection|Source Selection]]. A technically available value does not establish the state of a Twin Realization solely because the value is reachable or received through a communication mechanism. |
| |
| Interpretation of Twin State also depends on the origin, temporal context, and provenance of the values from which that state is determined. The architecture therefore preserves those relationships independently of the communication technology used to obtain the data. | Interpretation of state also depends on the origin, temporal context, and provenance of the values from which that state is determined. The architecture therefore preserves those relationships independently of the communication technology used to obtain the data. |
| |
| An invalid or unknown Twin State requires explicit detection because synchronization, simulation, comparison, Validation, or Test Execution performed from an indeterminate state can compromise reproducibility and the interpretation of results. | An invalid or unknown state requires detection because synchronization, simulation, comparison, Validation, or Test Execution performed from an indeterminate state can compromise reproducibility and interpretation of results. |
| |
| ===== Applies To ===== | ===== Applies To ===== |
| * [[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_state|Twin State]] | |
| * [[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:d:data_source|Data Source]] |
| ===== ConOps Relationship ===== | ===== ConOps Relationship ===== |
| |
| This requirement group supports establishment and determination of Twin State before and during Test Execution. | This requirement group supports establishment and determination of the state of a Twin Realization before and during Test Execution. |
| |
| The initial Twin State establishes the controlled starting condition for a Twin Realization. Subsequent determination of Twin State supports observation of state changes, synchronization among Twin Realizations, simulation, comparison, Validation, monitoring, and evidence-producing activities. | The initial state establishes the controlled starting condition for a Twin Realization. Subsequent determination of its state supports observation of state changes, synchronization among Twin Realizations, simulation, comparison, Validation, monitoring, and evidence-producing activities. |
| |
| The Data Source, temporal context, and provenance associated with Twin State support reproducibility and interpretation of Test Execution results. | The Data Source, temporal context, and provenance associated with the state of a Twin Realization support reproducibility and interpretation of Test Execution results. |
| |
| ===== Delivery Phase ===== | ===== Delivery Phase ===== |
| The explicit child links under Contents remain while the subordinate requirement pages are being created and reviewed. After all child pages exist, you may remove the explicit links because the ''indexmenu'' automatically discovers them. | The explicit child links under Contents remain while the subordinate requirement pages are being created and reviewed. After all child pages exist, you may remove the explicit links because the ''indexmenu'' automatically discovers them. |
| |
| The displayed title remains //Access Twin State// because the group covers establishment, determination, and access to Twin State. The existing namespace ''twin-005-acquire-twin-state'' remains unchanged to preserve the stable URI. | The displayed title is //Access Twin Realization State//. The existing namespace ''twin-005-acquire-twin-state'' remains unchanged to preserve the stable URI. |
| | |
| | The architecture does not define //Twin State// as a separate controlled term. State is treated as a characteristic of a Twin Realization, consistent with how the Node requirements treat state. |
| |
| The decomposition intentionally distinguishes: | The decomposition intentionally distinguishes: |
| |
| * establishment of the initial Twin State; | * establishment of the initial state of a Twin Realization; |
| * determination of the current Twin State; | * determination of its current state; |
| * access to the values constituting that state; | * access to the values constituting that state; |
| * identification of the originating Data Source; | * identification of the originating Data Source; |
| * detection of an invalid or unknown state. | * detection of an invalid or unknown state. |
| |
| Do not treat successful receipt of data as sufficient evidence that the data establishes valid Twin State. Twin Data Mapping, Data Source eligibility, Source Selection, temporal context, provenance, and governing Configuration remain separate architectural concerns. | Do not treat successful receipt of data as sufficient evidence that the data establishes the state of a Twin Realization. Twin Data Mapping, Data Source eligibility, Source Selection, temporal context, provenance, and governing Configuration remain separate architectural concerns. |
| |
| ---- | ---- |