28: Activity «stub» PopulateDigitalEntity

Gallery
Tutorial
TRAIL: A SysML Pattern for Digital Twinning
Section
Topic level
ADVANCED
UML keywords
Activity
SysML keywords
SysML Activity Diagram
Keywords
Slide kind
SysML Activity Diagram
This content has been marked as discussing an ADVANCED topic!
ANZLIC-2019: 'Traditionally, industry has created digital twins by retrospectively mapping, scanning, surveying, digitising or developing a digital copy of a real world object.'
Click on the image to view it full size
This is also just a «stub». Relevant model data about the «physical» PhysicalEntity (EXCEPT process-related data) would be extracted from these various input data sets and written to the «digital» @Entity mapper in a standard internal format.
Up next
29: Acquisition case: «STUB» Activities for initial model data and information mapping
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!
[POLICY]{STRICT} Webel Twin Pattern: An ActualPhysicalAsset is an asset that is also a «physical» PhysicalEntity.
Snippets (quotes/extracts)
 Traditionally, industry has created digital twins by retrospectively mapping, scanning, surveying, digitising or developing a digital copy of a real world object.
Visit also
HOWTO return chain on a CallBehaviorAction for an Operation trigger of a Transition with an effect
Visit also (backlinks)
Related slides (includes other tutorials)
Chain on a CallBehaviorAction for an Operation trigger of a Transition with an effect
Related slides (backlinks, includes other tutorials)