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.

Icon class
icon_class
far fa-sticky-note
icon_class_computed
far fa-sticky-note
Note kind
POLICY
Policy level
STRICT
Specification keywords
SysML-1.6
SysML-1.7
SysMLv2
Keywords
A Webel «twin» DigitalTwin does much more! It can also handle process-related aspects, which by definition here the Webel «digital» @Entity (a.k.a. "digital entity") does not:
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!
Relates to
02: Overview of Package 'twin' and notations
03: Focus BDD for the DigitalTwin block
05: Twin instances
06: Focus BDD for EntityRepresentation
07: BDD of twin control loop Blocks
08: IBD of basic twin control loop
09: IBD of DigitalTwin
11: Example: Twinning a construction Pipe
12: Overview of 'pipe' package
13: PipeDigitalTwin instances
14: IBD for PipeDigitalTwin flow control
01: Digital twin «snippet» text extracts from ANZLIC 2019
16: Overview of 'building' package
17: Staging BDD for working environment temperature vs building energy consumption control loop
18: IBD for working environment temperature vs building energy consumption control loop
04: Composite DigitalTwin
Related 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!
[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.
Related notes (backlinks)
Related snippets (extracts)
Visit also
Visit also (backlinks)