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)!
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:
