11: Example: Twinning a construction Pipe

Here the physical entity of a «twin» PipeDigitalTwin is a «physical» Pipe mapped by a «digital» @Pipe. The Pipe can be tilted, the orientation can be sensed, and the flow rate can be measured.

The defined parameters of the «physical» Pipe are only meaningful to the extent they can be measured, they are just a model of a real world entity. What happens if the Pipe gets on fire and melts completely? Does it still have a length or thickness?

Up next

12: Overview of 'pipe' package

Notes

[CONVENTION]{SUBJECT-TO-CHANGE} Webel: Convention: [MIGHT CHANGE]: An '@' prefix in a DigitalTwin model indicates a «digital» Block that maps a non-digital «mappable» Block.

[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.

[POLICY]{STRICT} Webel Twin Pattern: The primary aim of the digitalEntity:@Entity of a DigitalTwin is to replicate its physical:PhysicalEntity as closely as possible (not to explore variants).

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.