Scenarios can be used to model variations of a network simultaneously without the need to create separate branched networks.
For example, scenarios can be a very useful tool if used for the following : planning schedules, pipe repairs, alternative planning solutions, rehabilitation programs or cost estimations.
As scenarios are derived from a base network, they do not appear in the Explorer Window as separate entities but are saved within the base network and are viewed by opening the base network and selecting the scenario to be viewed from the Scenarios Toolbar.
Any changes made to the base network are copied to scenarios.
If changes are subsequently made to the same field in the scenario so that the value of the field in the scenario is set to the same as the base, the link between the objects in the base and scenario is re-established and changes made in the base will be visible in the scenario again.
Network objects present in the base network but not in the current scenario are displayed as a faded grey colour in the scenario GeoPlan window. Display of these 'object ghosts' can be turned on/off from the Visual Page of the GeoPlan Properties Dialog.
The InfoAsset Manager Scenarios toolbar contains functionality allowing users to:
A new housing estate is planned in the south-east of an existing town. A feasibility study is to be carried out to assess options for connecting the new estate to the existing sewer network.
The base network is the network in its current state. The background map shows the plans for the new estate, and currently there are no nodes or links serving it:
Scenarios can be used to model new estate connection options.
A scenario is created for each option to be assessed. An example is shown below:
Scenarios are not structured in the same way as most InfoAsset Manager objects therefore it is important to highlight the following points:
If we take the example below, where two scenarios, Scenario 1 and Scenario 2 have been generated from the base. Scenario 1 and Scenario 2 are independent from each other. However, changes made to the base will be cascaded down to both scenarios.
Scenario structure
Scenario 1_A and Scenario 1_B are duplicates of Scenario 1, and were obtained by copying Scenario 1. Scenario 1_A and Scenario 1_B are independent from each other. Making changes to Scenario 1_A will have no impact on Scenario 1_B and vice-versa. Similarly, editing or even deleting Scenario 1 will have no influence whatsoever on Scenario 1_A and Scenario 1_B. This is why the structure of scenarios can be represented by the image on the left (green tick) rather by than the one on the right (red cross).
OR
OR
OR
The scenario is deleted.
To compare a scenario with the base network
To compare two scenarios
It is possible to make a scenario the base. This is particularly useful if you have a scenario that you are happy with and that is the final result of your feasibility study.
It is possible to copy an existing scenario and make the new network the base. This is particularly useful if a particular scenario is favoured amongst other management options and that users wish to create a brand new network for this one scenario with a view of creating scenarios from it.
It is possible to add to or edit the notes for a scenario after the scenario has been created.