Scenario management is used to manage variants of a version file. These variants are organized within the project as scenarios including modifications (Fundamentals: Managing scenarios).
A project is ideally carried out in the following steps:
1. Creating a base version
2. Creating a new project and selecting the appropriate base version
4. Defining scenarios based on modifications
5. Specifying the procedure sequence
6. Calculating scenarios
7. Comparing calculation results
In the ideal case, you start by creating a single base version and then define its modifications step by step. However, you might already have several scenarios, either in form of a version file and several model transfer files or in form of several version files that only slightly differ. In this case, you can convert your data for scenario management during step 3: Defining modifications as follows:
- Apply your model transfer files and complete the modification (Creating modifications). Visum then saves the modification to the project, as a new model transfer file (with the same content).
- If you have a second version file that only slightly differs from the base version, load the second file during step 3: Defining modifications (Creating modifications). Then complete the modification. Visum then saves the differences between the base version and the newly opened version to the project as a model transfer file. You then create a scenario and assign the modification to it. The scenario now corresponds to your second version file.
In scenario management, you also have the option of assigning different global layouts to individual scenarios(Specifying global layouts).
