| Next revision | Previous revision |
| dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-03-twin-node-requirements:twin-003-configure-a-twin-relationship:twin-003a-identify-represented-twin-characteristics [2026/08/20 11:56] – created nick_dido | dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-03-twin-node-requirements:twin-003-configure-a-twin-relationship:twin-003a-identify-represented-twin-characteristics [2026/08/20 12:33] (current) – nick_dido |
|---|
| ===== Statement ===== | ===== Statement ===== |
| |
| The [[dido:99_annexes:annex-b-terms-and-definitions:d:dido-te|DIDO-TE]] SHALL identify the characteristics of each [[dido:99_annexes:annex-b-terms-and-definitions:t:twin_realization|Twin Realization]] that participate in the applicable twin relationship. | The [[dido:99_annexes:annex-b-terms-and-definitions:d:dido-te|DIDO-TE]] SHALL identify the characteristics of each [[dido:99_annexes:annex-b-terms-and-definitions:t:twin_realization|Twin Realization]] that participate in the applicable [[dido:99_annexes:annex-b-terms-and-definitions:t:twin_relationship|Twin Relationship]]. |
| |
| ===== Source ===== | ===== Source ===== |
| ===== Rationale ===== | ===== Rationale ===== |
| |
| A [[dido:99_annexes:annex-b-terms-and-definitions:d:digital_twin|Digital Twin]] does not necessarily represent every characteristic of its referent. | A [[dido:99_annexes:annex-b-terms-and-definitions:d:digital_twin|Digital Twin]] does not represent every characteristic of its referent. |
| |
| A twin relationship therefore requires an explicit identification of the characteristics that participate in that relationship. These characteristics establish the scope within which a [[dido:99_annexes:annex-b-terms-and-definitions:t:twin_realization|Twin Realization]] is observed, synchronized, simulated, selected, or compared. | A [[dido:99_annexes:annex-b-terms-and-definitions:t:twin_relationship|Twin Relationship]] therefore requires identification of the characteristics that participate in that relationship. These characteristics establish the scope within which a [[dido:99_annexes:annex-b-terms-and-definitions:t:twin_realization|Twin Realization]] is observed, synchronized, simulated, selected, or compared. |
| |
| Represented characteristics may include selected state, behavior, [[dido:99_annexes:annex-b-terms-and-definitions:c:configuration|Configuration]], communication, timing, resource, or lifecycle characteristics when those characteristics are applicable to the purpose of the twin relationship. | Represented characteristics may include selected state, behavior, [[dido:99_annexes:annex-b-terms-and-definitions:c:configuration|Configuration]], communication, timing, resource, or lifecycle characteristics applicable to the purpose of the Twin Relationship. |
| |
| Explicit identification prevents characteristics that happen to be observable or technically available from becoming part of the twin relationship without architectural intent. | Identification of the represented characteristics prevents observable or technically available characteristics from becoming part of the Twin Relationship without architectural intent. |
| |
| ===== Applies To ===== | ===== Applies To ===== |
| * [[dido:99_annexes:annex-b-terms-and-definitions:d:digital_twin|Digital Twin]] | * [[dido:99_annexes:annex-b-terms-and-definitions:d:digital_twin|Digital Twin]] |
| * [[dido:99_annexes:annex-b-terms-and-definitions:t:twin_identity|Twin Identity]] | * [[dido:99_annexes:annex-b-terms-and-definitions:t:twin_identity|Twin Identity]] |
| | * [[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_node|Twin Node]] | * [[dido:99_annexes:annex-b-terms-and-definitions:t:twin_node|Twin Node]] |
| Verification confirms that: | Verification confirms that: |
| |
| - Each configured twin relationship identifies the characteristics that participate in the relationship. | - Each configured Twin Relationship identifies the characteristics that participate in the relationship. |
| - An identified characteristic is associated with the applicable Twin Identity or Twin Realization. | - Each identified characteristic is associated with the applicable Twin Identity or Twin Realization. |
| - A characteristic not identified as participating in the twin relationship is not treated as a required basis for synchronization, simulation, comparison, or validation. | - A characteristic not identified as participating in the Twin Relationship is excluded from the required scope of synchronization, simulation, comparison, or validation. |
| - The identified characteristics remain distinguishable from implementation-specific mechanisms used to observe or exchange their values. | - The identified characteristics remain distinguishable from implementation-specific mechanisms used to observe, transport, or exchange their values. |
| - The identified characteristics can be traced to the applicable Configuration, Test Definition, requirement, or other governing source. | - Each identified characteristic is traceable to the applicable Configuration, Test Definition, requirement, or other governing source. |
| |
| Verification includes inspection of a twin relationship in which only a subset of the available characteristics of a Twin Realization participates in the relationship. | Verification includes inspection of a Twin Relationship in which only a subset of the available characteristics of a Twin Realization participates in the relationship. |
| |
| ===== Traceability ===== | ===== Traceability ===== |
| ===== ConOps Relationship ===== | ===== ConOps Relationship ===== |
| |
| This requirement supports configuration of the scope of a twin relationship before data mappings, source eligibility, source selection, synchronization, simulation, or comparison are established. | This requirement supports Configuration of the scope of a Twin Relationship before data mappings, source eligibility, source selection, synchronization, simulation, or comparison are established. |
| |
| ===== Delivery Phase ===== | ===== Delivery Phase ===== |