01: Digital twin «snippet» text extracts from ANZLIC 2019

Gallery

Tutorial

TRAIL: A SysML Pattern for Digital Twinning

Section

Tags and keywords

Topic level

INTERMEDIATE

SysML keywords

SysML Package Diagram

Keywords

Slide kind

SysML Block Definition Diagram (BDD)

To get us started we are going to map some text from ANZLIC 2019 as a target domain source document to SysML traceably via «snippet» elements (custom Webel extensions of the SysML ElementGroup):

ANZLIC2019: 'Digital twins are dynamic, data driven, multi-dimensional digital replicas of a physical entity. They encompass potential or actual physical assets, processes, people, places, systems, devices and the natural environment.'

ANZLIC2019: 'In contrast to traditional digital models, digital twins can connect with the physical ‘twin’ they model, changing alongside the physical system via real-time sensors and actuators.'

Click on the image to view it full size

Unlike in the main tutorials for the Webel Parsing Analysis recipe for SysML^®, in this trail we're only going to show the elicited elements in the main model (not the «pa» Parsing Analysis "scratchpad" diagrams where new elements are elicited).

Two of the snippets are contested as contradicting each other, which claim can be recorded using the custom tagged values contradicts and contradictedBy and/or via an editorial «!CONTRADICTS» comment:

A process is not a physical entity

This may in this case be overly pedantic, and it depends on how one interprets 'encompasses', but it is included here for the sake of demonstration, and because in the Webel Twin Pattern for SysML the following policies are important and work together:

Webel Twin Pattern: A «digital» DigitalEntity (a.k.a. @Entity) encapsulates strictly geometrical, spatial, and material aspects of a «physical» PhysicalEntity only. BY DEFINITION of this pattern it DOES NOT encapsulate processes!

Webel Twin Pattern: It is a DigitalEntity (a.k.a. @Entity) - not the DigitalTwin that owns it - that directly «replicates» geometrical, spatial, and material aspects (only) of a single PhysicalEntity.

We'll learn next how these concept are defined in the SysML model.

Up next

02: Overview of Package 'twin' and notations

Notes

[POLICY]{STRICT} Webel Twin Pattern: A «digital» DigitalEntity (a.k.a. @Entity) encapsulates strictly geometrical, spatial, and material aspects of a «physical» PhysicalEntity only. BY DEFINITION of this pattern it DOES NOT encapsulate processes!

[POLICY]{STRICT} Webel Twin Pattern: It is a DigitalEntity (a.k.a. @Entity) - not the DigitalTwin that owns it - that directly «replicates» geometrical, spatial, and material aspects (only) of a single PhysicalEntity.

Snippets (quotes/extracts)

Digital twins are dynamic, data driven, multi-dimensional digital replicas of a physical entity.

They encompass potential or actual physical assets, processes, people, places, systems, devices and the natural environment.

In contrast to traditional digital models, digital twins can connect with the physical ‘twin’ they model, changing alongside the physical system via real-time sensors and actuators.