Need help working from home with your Bentley software? We're here to help - click here
After running the Skelebrator Skeletonizer tool for Branch Collapsing, the customer meters (associated with junctions that were removed) are automatically reassigned to the node that the demands were moved to. However, Skelebrator will only run against the active scenario and won't update the customer meter associated element fields for all scenarios.How can I apply the updated customer meter associated element fields to the other scenarios?
Option 1: Use ModelBuilder to update the other scenarios.For models with multiple scenarios, skeletonize the base, so that the updated associated elements will be inherited by child scenarios.
Running Skelebrator on the base scenario won't update customer meters that don’t inherit demands from the demand alternative used by the Base scenario.
To update other scenarios to match the base scenario's customer meter associated element field, do the following.
1. Run Skelebrator on the Base scenario.2. Export customer meter labels and associated element labels to a shapefile.3. Switch to another scenario (that doesn't have the updated associated elements).4. Use ModelBuilder to import the associated element labels from that shapefile.
After you run ModelBuilder the first time, that run is saved to the Modelbuilder Connections Manager dialog. You can switch to another scenario (that doesn't have the updated associated elements), open the ModelBuilder Connections Manager, select that ModelBuilder run, and then click the icon "Sync-In To Model".
Option 2: Use LoadBuilder to re-associate the customer meters.See: Using LoadBuilder to assign Customer Meters to the nearest pipe using taps and laterals
This option may not be as accurate as option 1. When the associated elements are updated with Skelebrator, customer meters that were associated with the deleted elements will be reassigned to the node the demand is moved to. LoadBuilder uses different criteria to assign customer meters to elements which may reduce model accuracy and consistency across scenarios.
Note: It is best to use Skelebrator after building the model in the Base scenario, and before creating any additional scenarios.
If Skelebrator branch collapsing is run on the base scenario when there are other scenarios in the model, then the customer meters will not necessarily update the other scenarios.
Suppose Skelebrator branch collapsing is used on the Base Scenario, which uses the Base Demand Alternative.
Any other scenario, using a demand alternative that is a child of that Base Demand alternative, will only inherit the updated customer meter associated elements if the customer meter is not set to use local data. It is common for child demand alternatives to use local data, as the point of creating an child demand alternative is to adjust the demand based on the parent demand alternative.
Exporting model elements to Shapefiles
Using ModelBuilder to Import External Data