-
The world of ‘Digital Twin Uses’ delivered in standard terms
The idea of a Digital Twin [DT] needs to advance in a standardized and formal manner. As @DRossiter87 pointed out, this is necessary to “support the consistent adoption of, and interoperability between, digital twins for the built environment within the UK”
To aid in this endeavour, it is useful to delineate the difference between the following terms:
“DT General Use Case” [GUC]: a very short sentence, possibly consisting of two or three words – ideally a verb followed by a noun – ultimately concerned with the brief and blunt statement of the central business aim that is motivating the use and implementation of a DT, e.g., ‘optimize traffic’.
“DT Use Case Scenario” [UCS]: a documentation of the sequence of actions, or in other words, DT-user interactions executed through a particular DT case study or an actual DT real-world project.
“DT Use”: a typical technical function or action executed by any DT throughout the course of any UCS. Accordingly, the DT uses are seen as the standard building blocks by which a standard common language can be founded. Such a standard language, which can possibly be machine-readable as well, can be used in documenting and detailing the DT-user interactions in a standard format to facilitate their publishing and sharing of knowledge.
Below is a figure of a “DT uses taxonomy”. It is made up of three distinct hierarchical levels, these are respectively:
- ‘Included Uses’ containing four high-level cornerstone uses that are, besides rare exceptional cases, included in and executed by almost every DT throughout any UCS (i.e. Mirror, Analyse, Communicate and Control);
- ‘Specialized Uses’ including special forms of the Included Uses, where each specialized use enjoys unique strengths suitable for specific purposes; and
- “Specialized Sub-Uses” at the lowest hierarchical level of the taxonomy, which further differentiates between variant types within a Specialized Use at the higher level by virtue of very fine inherent variations that distinguish one type from another and thus, enhances the DT’s practical adequacy in dealing with alternative contexts and user specifically defined purposes.
-
0 Replies
Sorry, there were no replies found.
Log in to reply.