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 existing or anticipated PhysicalEntity (even if only via another DigitalTwin)!

Icon class
icon_class
far fa-sticky-note
icon_class_computed
far fa-sticky-note
Note kind
ASSERTION
POLICY
Policy level
STRICT
Specification keywords
SysML-1.6
SysML-1.7
SysMLv2
Keywords
Please note that bit about BY DEFINITION HERE. You are welcome to define the term "digital twin" otherwise, but then you won't be using the Webel Twin Pattern for SysML, which is physics-driven:

Or you may wish to do things that don't affect the real world instead.
As explained in this trail, process-related and other cases are covered, they are just handled separately:
TRAIL: A SysML Pattern for Digital Twinning
Relates to
04: Composite DigitalTwin
Related notes
[POLICY]{STRICT} Webel Twin Pattern: A DigitalTwin must model processes and the entities they act on separately.
[POLICY]{STRICT} Webel Twin Pattern: A LogicalProcess may only act on a PhysicalEntity via a PhysicalProcess
[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!
Related notes (backlinks)
Related snippets (extracts)
Visit also
Visit also (backlinks)