Hi,
I'm trying to undertake high level FF modelling for high level optioneering (we can undertake detailed FF modelling if associated options are deemed potentially viable to proceed after assessment).
The problem is the junctions in the existing models do not currently have any identifier as to the FF requirements.
For a high level pass we figure it would be adequate to simply running two FF scenario checks, one for residential and one for non-residential. But again we don't have an immediate way to identify which Junction is associated with res or non-res.
We can't use the Demand Centre as Demands are assigned to the model via Customer Meters, which means each junction's demands are assigned as "Associated Customer Meter Unit Demands".
Is it possible to somehow identify which Junctions have a specific type of "Unit Demand" or "Pattern (Unit Demand)" assigned via the "Associated Customer Meter Unit Demands"?
This way we could create a selection set for all junctions with an associated non-residential demand assigned to them.
Thank you,
Ryan Catling
I don't think there is an easy way of doing this. You could select the customer meters of a specific type (for example residential), run a "Find Elements Associated with Customer Meters" query, from the results, select all junctions and hydrants, add these to a selection set (residential nodes), then from the query results select all pipes (make sure no nodes are selected) and run a "Find adjacent Nodes" query, and add the nodes in the results from this second query to the selection set (residential nodes). Repeat for each demand type.
An alternate way would be to use loadbuilder in a temporary scenario (with a new demand alternative) to move the demand from the customer meters to the junctions/hydrants:
1. Export all customer meters with their base demand & pattern data to a shapefile (using a flextable export)
2. Create a temporary scenario (with a new temporary demand alternative)
3. Open loadbuilder
4. Select External Data -> Point Load Data -> Nearest Pipe
5. Make sure to pick "Equal Distribution" or "Distance Weighted" for the Pipe Layer on the "Nearest Pipe" screen to make sure demand is moved to both nodes connected to the pipe
6. For Billing Meter Data, pick the shapefile you exported in step 1, make sure to pick the pattern field of the shapefile in the Load Type Field
7. On the "Calculation Summary" screen assign the correct pattern to each load type (res -> res, nonres -> nonres, etc)
8. On the "Completing the LoadBuild process" screen, make sure "Override an Existing Alternative" is selected, and pick the new temporary demand alternative that was assigned to the temporary scenario
9. Finish
The demands of each customer meter should now be assigned to the 2 nodes of the pipe nearest to each customer meter. You can now use the demand control center to filter the junctions and/or hydrants on pattern type and create selection sets for each. These selection sets can then be used in the FF alternatives to run separate FF analysis for each pattern/demand type. After the selection sets have been created, you can delete the temporary scenario & temporary demand alternative.
For a small amount of different demand types the first method would be quickest, for a larger variation in demand types the second method would probably be quicker.
Hi Ryan,
This might get you in the ballpark..
Rob.
Answer Verified By: Ryan Catling
I have created a new wiki article with details for Rob's suggested method: Selecting junctions based on type of associated Customer Meters
Regards,
Jesse DringoliTechnical Support Manager, OpenFlowsBentley Communities Site AdministratorBentley Systems, Inc.
Thanks Everyone,
Answers worked like a charm with the "Find Elements Associated with Customer Meters" network trace