34: Activity «STUB» PopulatePotentialWithProcessesAndTrackingData

Gallery
Tutorial
TRAIL: A SysML Pattern for Digital Twinning
Section
Topic level
ADVANCED
UML keywords
Activity
ObjectNode::inState
SysML keywords
SysML Activity Diagram
Keywords
Slide kind
SysML Activity Diagram
This content has been marked as discussing an ADVANCED topic!
This is merely a «STUB» Activity for population of a «digital» PotentialPhysicalAsset with process-related data and any auxiliary information from the AssetSpecification that is not already stored in the "template" «digital» @Entity . This might include, for example, manufacturing process information:
Click on the image to view it full size
Up next
35: Activity ActualisePhysicalAsset and «STUB» ManifestActualAssetFromPotentialAsset
Notes
[POLICY]{STRICT} Webel Twin Pattern: A PotentialPhysicalAsset is «digital», not «physical». It is used to acquire (an existing) or create (build, manifest, make) an «physical» ActualPhysicalAsset, which is a special case of «physical» PhysicalEntity.
[ASSERTION]{STRONG} Webel Twin Pattern: An AssetSpecification may contain ANY information or data of ANY kind in ANY format about how to acquire, manifest, build, or create a physical asset. This information may be distributed across an @Entity and a PotentialPhysicalAsset.
[POLICY]{STRONG} Webel Twin Pattern: The information and data in AssetSpecification leveraged for creation of a new ActualPhysicalAsset need not necessarily only be «digital».
Snippets (quotes/extracts)
 Today this process can occur in reverse, with the digital model developed first followed by the physical asset.
Visit also
Visit also (backlinks)
Related slides (includes other tutorials)
Related slides (backlinks, includes other tutorials)