Commit changes and use scenarios to save network variations

Step-by-step guide

Changes made to a version-controlled database object are continually and automatically saved locally in the working folder until they are committed. When changes are ready to be saved or shared, commit them to upload the changes to the database and merge them with changes from other users as a new version.

An uncommitted network has a red circle at the bottom of the network icon and needs to be committed before changes can be used in a model.

Best practice is to commit changes after any major editing or updating of the network, even when working alone.

To commit changes:

1. In the Explorer window, right-click the network and select Commit changes to database.
   

The Commit change to server dialog includes a summary of the changes being committed.

2. In the Comments section, add a comment about the changes, such as “2 nodes inserted in north east zone”.
3. Click OK.
   
4. Alternatively, on the File toolbar, click Save or use the Network > Version control menu to commit changes.
   

While committing changes is an easy way to save data, scenarios can be used for several reasons, such as:

• Modeling variations of a network simultaneously, without the need to create separate branch networks.
• Investigating the impact of different parameters, such as increasing pipe sizes.
• Performing quality assurance, allowing multiple users to work independently in their own scenario until the work has been checked and reviewed.

Once work has been reviewed and signed off, scenarios can be integrated into the Base network, making changes available to all users.

Because scenarios are derived from a Base network, they do not appear in the Explorer window as separate entities. Instead, they are saved within the Base network.

To view a scenario:

5. Open the Base network.
6. From the Scenarios toolbar, select the scenario.
   

To create a scenario:

7. On the Scenarios toolbar, click Create scenario.
   
8. Alternatively, in the Network menu, select Scenarios > Create scenario.
   
9. In the Create new scenario dialog, add a New Scenario Name, such as “NE Zone Update”.
10. Add any meaningful Notes, such as “Upsizing pipes in NE zone”.
11. Click OK to save the scenario.
    

Changes can be made to the elements in the scenario without affecting the Base network.

Each scenario is a copy of the Base network, unless a scenario is created as a copy of another. All changes made to a scenario are independent. Scenarios can be made to construct unique situations, which can then be analyzed and compared.

12. To Delete, Rename, or Manage scenarios, use the corresponding tools in the Scenarios toolbar.
    
13. Select Manage scenarios to open the Manage scenarios dialog and access additional tools, such as a tool to compare scenarios.