TWIN-003c — Identify Eligible Twin Data Sources

Go to TWIN-003 — Configure a Twin Relationship

The DIDO-TE SHALL identify the Data Sources eligible to provide data for each Twin Relationship.

• [DTE1] U.S. Patent Application US20220237111A1, virtual and physical Twin Node concepts and comparison of Twin Node behavior
• [DTE2] Non-Traditional BAA Submission, Digital Twin concepts and F17, Twin Nodes Selection
• [DTE9] Distributed Immutable Data Object Reference Architecture (DIDO-RA), Digital Twin, DDS publish-subscribe, and DDS Quality of Service concepts

A Twin Relationship may receive applicable data from more than one Data Source.

Technical availability of data does not establish eligibility for use in a Twin Relationship. A Data Source may be discoverable, reachable, or compatible with the applicable communication mechanism without being permitted to contribute data to the relationship.

Explicit identification of eligible Data Sources separates semantic and governance decisions from implementation mechanisms such as network connectivity, DDS discovery, Topic matching, or Quality of Service matching.

Eligibility establishes the set of Data Sources from which a subsequent source-selection process operates. It does not determine which eligible Data Source is selected when more than one is available.

• DIDO-TE
• Data Source
• Twin Relationship
• Twin Realization
• Twin Data Mapping
• Configuration
• DDS

Verification confirms that:

1. Each Twin Relationship identifies its eligible Data Sources.
2. Each identified Data Source is distinguishable from other Data Sources.
3. A Data Source not identified as eligible is excluded from providing data used by the Twin Relationship.
4. Technical discovery, connectivity, Topic matching, datatype compatibility, or Quality of Service matching does not by itself establish Data Source eligibility.
5. More than one Data Source may be identified as eligible for the same Twin Relationship.
6. Data Source eligibility is distinguishable from selection of a Data Source for use.

Verification includes a Twin Relationship with at least two technically available Data Sources, where one Data Source is eligible and another is not eligible.

This requirement supports Configuration of the Data Sources permitted to contribute data to a Twin Relationship before source selection, state acquisition, synchronization, simulation, or comparison occurs.

TBD

Draft

{{section>dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-03-twin-node-requirements:twin-003-configure-a-twin-relationship:twin-003c-identify-eligible-twin-data-sources#Statement&noheader&nofooter&noeditbtn}}