The Scenario transfer node (STN) handles the joining of two scenarios and conceptually, comprises of two components (as shown in Figure 1). The node links two scenarios and runs them together.
The STN operates in either a connected or disconnected mode. :
- When processing a connected execution, the pitcher passes all components of the pitcher scenario to the catcher, hence linking the two scenarios together
- ; and
- For a disconnected execution (ie. scenarios are run independent of each other), the pitcher acts like a minimum flow requirement node and the catcher models an inflow node.
Figure 1. Scenario Transfer node
With the STN, you can:
- Pass constituents from one scenario to another;
- Ordering is passed between linked scenarios;
- Expressions from one scenario point to the transfer node when expressions need to point to items in a different scenario.
Constituents
If constituents are defined in both the pitcher and catcher scenarios, you can choose which constituent in pitcher will match to which constituent in the catcher in map constituents between the two scenarios using the STN feature editor. Choose Connected > Constituent Mapping from the tree and click Add (as shown in Figure ).
Figure STN, Constituent mapping
Ownership
Ownership can be set up in linked scenarios using Connected > Ownership in the feature editor (as shown in Figure ).
Figure STN, Ownership