35: Activity ActualisePhysicalAsset and «STUB» ManifestActualAssetFromPotentialAsset

The outer level ActualisePhysicalAsset is essentially a wrapper for managing the binding through a CallOperationAction for bind of the created (manifested) «physical» ActualPhysicalAsset to the «digital» @Entity , which transitions from state UnBound to state Bound. After this, the role of the «digital» @Entity as "template" ends, and it can take on a new role as part of the synchronisation loop.

The actual creation (building) of the «physical» ActualPhysicalAsset is represented by the «STUB» ManifestActualAssetFromPotentialAsset. In practice, information from the «digital» PotentialPhysicalAsset and the "template" or "prototype" «digital» @Entity it carries would be used to build or otherwise make the «physical» ActualPhysicalAsset as a «physical» PhysicalEntity in the real world, represented by the innermost StubMakePhysicalAsset. The CallOperationAction for manifest asserts that the «physical» ActualPhysicalAsset indeed now Exists (and has mass in the real world).

And now it's time to see it all running!

Screencast: The Webel Digital Twin Pattern for SysML: Part 1: Simulating acquisition or creation of physical assets using Activities and StateMachines in Cameo Simulation Toolkit.

— END OF TRAIL —

You may wish to visit one of these tutorials next:

HOWTO return chain on a CallBehaviorAction for an Operation trigger of a Transition with an effect

HOWTO simulate UML-2.5.1 'Figure 14.7 Composite State with two States' in Cameo Simulation Toolkit - Operation-driven Transition case study

TRAIL: Webel's ultimate guide to Systems Modeling Language (v1) with MagicDraw/Cameo

HOWTO invoke an operation as a Transition guard in Cameo Simulation Toolkit

Visit more Systems Modeling Language v1 (SysML^®) tutorial trails here.

Visit also these screencast tutorial videos

Please email or phone Webel IT Australia on +61 405 029 008 to arrange On-Site, Off-Site, or Live Online remote web training seminars and workshops.

Watch full video

Screencast: The Webel Digital Twin Pattern for SysML: Part 1: Simulating acquisition or creation of physical assets using Activities and StateMachines in Cameo Simulation Toolkit.

Up next

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.