Scenario Transfer Node
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
Note the following when working with linked scenarios:
- Constituents are passed from one scenario to another;
- Orders are passed between linked scenarios;
- Off allocation does not operate over scenarios. In this mode, the STN operates like an off allocation boundary - similar to the transfer ownership node;
- Ownership is passed across boundaries.
Constituents
A model will operate even if the constituent processing methodology (lumped or marker) is different for each scenario. For example, consider the pitcher scenario is configured with lumped routing and the catcher scenario with marker routing. Constituents will be passed from the pitcher to the catcher even though the methodology is not the same.
Once constituents are defined in both the pitcher and catcher scenarios, you can 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 2).
Figure 2. STN, Constituent mapping
Ownership
Ownership can be set up in linked scenarios using Connected > Ownership in the feature editor (as shown in Figure 3). Configuration of ownership is similar to the Transfer ownership node (when set up as a boundary node).
Figure 3. STN, Ownership
