23: Mini StateMachine for DigitalTwin and DoAttach effect Activity

The mini StateMachine at the top shows how a «twin» DigitalTwin transitions from UnAttached to Attached when it and its «physical» PhysicalEntity are connected to any «sensor» Sensor and/or «actuator»

Actuator:

Click on the image to view it full size

Not every task in Activity Diagrams is well-suited to graphical modelling; consider using Action Language Helper (ALH) or Action Language for Foundational UML (Alf)

The lower Activity Diagram shows the effect Behavior for making the connections. Yes, it's a bit tedious, but is made slightly easier by this:

UML/SysML: When you use an AddStructuralFeatureValueAction to set one end of a bi-directional Association it also sets the other end.

Up next

24: Case: Acquisition: Twin a pre-existing physical asset

Notes

[POLICY]{STRICT} Webel Twin Pattern: A DigitalTwin and PhysicalEntity must both be 'attached' to Sensors and/or Actuators under management of the DigitalTwin before the twinning control loop is fully entered.

[POLICY]{STRICT} Webel Twin Pattern: An ActualPhysicalAsset is an asset that is also a «physical» PhysicalEntity.

[TIP]{OPTION} Not every task in Activity Diagrams is well-suited to graphical modelling; consider using Action Language Helper (ALH) or Action Language for Foundational UML (Alf)

[TIP]{INFORMATIVE} UML/SysML: When you use an AddStructuralFeatureValueAction to set one end of a bi-directional Association it also sets the other end.

[POLICY]{STRICT} UML/SysML: If you have a Boolean "state flag" attribute corresponding to a State you MUST set it on an 'entry' of the State, not on the 'effect' of a Transition into the State (otherwise with multiple incoming Transitions it could be WET and breaks SSoT).

[MODELLING, TIP]{SUGGESTED} UML/SysML: A Boolean "state flag" attribute corresponding to a State can be useful for indicating states in some diagram types (but must be synchronised with Transitions to States carefully).

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.

Today this process can occur in reverse, with the digital model developed first followed by the physical asset.

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)

Flags