digital twin

Webel Twin Pattern: The information and data in AssetSpecification leveraged for creation of a new ActualPhysicalAsset need not necessarily only be «digital».

Screencast: The Webel Digital Twin Pattern for SysML: Part 1: Simulating acquisition or creation of physical assets using Activities and StateMachines in Cameo Simulation Toolkit.

Keywords

Video style

This video accompanies the following online slide trail:

TRAIL: A SysML Pattern for Digital Twinning

It shows simulation of the acquisition and creation cases for the Webel Twin Pattern for SysML in Cameo Simulation Toolkit^®.

Read more about Screencast: The Webel Digital Twin Pattern for SysML: Part 1: Simulating acquisition or creation of physical assets using Activities and StateMachines in Cameo Simulation Toolkit.

Webel Twin Pattern: An ActualPhysicalAsset is an asset that is also a «physical» PhysicalEntity.

Webel Twin Pattern: A DigitalTwin and PhysicalEntity must both be 'attached' to Sensors and/or Actuators under management of the DigitalTwin before the twinning control loop is fully entered.

Webel Twin Pattern: Not every twinnable PhysicalEntity is worth treating as an asset.

'Origins of the Digital Twin Concept', August 2016, Dr Michael Grieves

Webel Twin Pattern: A DigitalTwin (even a "process twin" or "finance twin"), always, without exception, BY DEFINITION HERE either directly or indirectly involves at least one PhysicalEntity (even if only via another leveraged DigitalTwin)!

Today this process can occur in reverse, with the digital model developed first followed by the physical asset.

Source

ANZLIC 2019 - Principles for Spatially Enabled Digital Twins of the Built and Natural Environment in Australia

Traditionally, industry has created digital twins by retrospectively mapping, scanning, surveying, digitising or developing a digital copy of a real world object.

Source

ANZLIC 2019 - Principles for Spatially Enabled Digital Twins of the Built and Natural Environment in Australia

Webel Twin Pattern: A DigitalEntity (a.k.a. «digital» @Entity) used as a digital variant must not be bound to a «physical» PhysicalEntity.

Subscribe to digital twin