TWIN-005a — Identify Twin State

Go to TWIN-005 — Access Twin State

The DIDO-TE SHALL identify the Twin State represented by each Twin Realization participating in a Twin Relationship.

• [DTE1] U.S. Patent Application US20220237111A1, virtual and physical Twin Node concepts, baseline results, and comparison of Twin Node behavior
• [DTE2] Non-Traditional BAA Submission, Digital Twin concepts, monitoring, scenario testing, and Twin Nodes Selection
• [DTE9] Distributed Immutable Data Object Reference Architecture (DIDO-RA), Digital Twin and distributed data concepts

A Twin Realization may expose or contain information beyond the state represented within a Twin Relationship.

Identification of Twin State establishes which represented state participates in monitoring, synchronization, simulation, comparison, Validation, or Test Execution.

The identified Twin State derives from the represented characteristics and Twin Data Mappings established for the Twin Relationship.

Information that is technically observable does not become Twin State solely because it is available from a Twin Realization.

• DIDO-TE
• Twin State
• Twin Relationship
• Twin Realization
• Twin Data Mapping
• Configuration

Verification confirms that:

1. Each participating Twin Realization has identified Twin State.
2. The identified Twin State corresponds to characteristics represented by the Twin Relationship.
3. The identified Twin State is distinguishable from information outside the represented scope of the Twin Relationship.
4. The identified Twin State is traceable to the governing Configuration or Twin Data Mapping.
5. Availability of additional information from a Twin Realization does not add that information to the identified Twin State.

Verification includes a Twin Realization that exposes both represented and non-represented information and confirms that only represented state is identified as Twin State.

This requirement establishes the Twin State subject to subsequent value access, source identification, temporal association, provenance preservation, synchronization, simulation, comparison, and Validation.

TBD

Draft

{{section>dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-03-twin-node-requirements:twin-005-acquire-twin-state:twin-005a-identify-twin-state#Statement&noheader&nofooter&noeditbtn}}