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!

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
Amongst other things, this policy helps leverage the separation of structure/value and Behavior in Systems Modeling Language v1 (SysML®), but there are also fundamental conceptual reasons for it.
Relates to
02: Overview of Package 'twin' and notations
03: Focus BDD for the DigitalTwin block
05: Twin instances
06: Focus BDD for EntityRepresentation
08: IBD of basic twin control loop
09: IBD of DigitalTwin
10: Process overview
12: Overview of 'pipe' package
13: PipeDigitalTwin instances
01: Digital twin «snippet» text extracts from ANZLIC 2019
20: Package Diagram overview of 'asset'
22: Mini StateMachines for @Entity, PotentialPhysicalAsset, ActualPhysicalAsset
21: Example instances for 'asset'
24: Case: Acquisition: Twin a pre-existing physical asset
26: Activity IdentifyAcquireAttachPhysical
27: Activity CreateDigitalEntityFromPhysicalEntity
28: Activity «stub» PopulateDigitalEntity
29: Acquisition case: «STUB» Activities for initial model data and information mapping
30: Activity UpdateDigitalFromPhysical
31: Case: Create a new physical asset using a «digital» @Entity initially as a digital "template"
32: Activity CreatePhysicalEntityFromDigitalEntity
33: Activity «STUB» PopulateDigitalWithDesignModels
Related notes
Related notes (backlinks)
Related snippets (extracts)
Visit also
Visit also (backlinks)