The use of satisfy here is relatively straightforward. The diagram does, however, afford an opportunity to compare some of the finer aspects of representing performed actions.

There are roughly speaking two different ways of representing performed actions graphically (apart from just listing in compartments):

• Show the performed action within the symbol of each performing part. This has the advantage that you can also show other features of the part.
• Use performance swimlanes.

The performance swimlanes approach his nice from the perspective of functional analysis breakdown, but if you look closely you might notice that it is then showing the actual performed action element directly; you can't display the owned usage that performs that action.

For provide power within vehicle_c1 it makes little difference, because it just has a reference subsetting. But for the nested part engine_v1 it does make a difference, because it has a local redefinition as:

perform 'provide power'.'generate torque' :>> generateTorque;

The swimlane is displaying the target generate torque not the owned 'provide power'.'generate torque' .

ASIDE: In Cameo 2026xHF2 sometimes it won't always easily display the reference subsetting relationship symbol if you first show the target «action» as a nested symbol. In the view above it would initially not show the reference subsetting to «action» generate torque (it does however appear correctly as the target under the context menu item Go To > Performed Action).

The trick to get the reference subsetting to show is to delete (remove) the nested target action symbol (only), select the same «action» again in the model containment browser, drag it onto the diagram but NOT placed yet nested inside its owner's symbol, then use Display > Display Specializations to indeed create the reference subsetting, then drag the target «action» symbol into its owner symbol nested. Phew!