Manually assigning customer meters to pipes.

You could also first run an "Orphaned Customer Meters" query and create a selection set of customer meters based on this result, then use this selection set in the loadbuilder to re-assign the customer meters that lost their association to pipes. 

I agree with Joeri's suggestion. Here is an article with more information on running the orphaned customer meters query: Using Network Navigator 

The selection set can be selected in the "customer meter layer" field in LoadBuilder.

Note that a customer meter's associated pipe should be automatically changed if the original pipe is split. There is however a known issue (reference # 1004540) where splitting a pipe in some cases may break the "associated element" for customer meters, in a child alternative/scenario. Is this perhaps what happened in your case?

Thanks for the quick response Mark, Joeri and Jesse. 

Jesse - When you say "a customer meter's associated pipe should be automatically changed if the original pipe is split," I am guessing this should trickle down to all child scenarios as well, correct?  Also, that is not what I am experiencing here, I immediately lose the associations between my customer meters and pipes when I split pipes.  Yes, it appears that this (reference # 1004540) is the problem I am having, I lost associations between my pipes and customer meters after splitting one of the pipes, and now I have customer meters (>100) that are not associated to any pipes in all my scenarios (>10).  Is there a way to resolve this issue (reference # 1004540)?

I hope to hear back from you soon.

Regards,

Youssef

Hi Youssef,

What version of WaterGEMS are you using? You can find this under File > Help > About. The latest is 10.02.01.06. 

Are you saying that the customer meter pipe association is lost right away, in the same scenario where you split the pipe? In other words, are you choosing to split the pipe and immediately afterwards seeing that the association is lost? (without changing scenarios). I believe the defect in question would only impact child alternatives/scenarios but there might be some variations in the steps that cause this to happen. If needed, please provide an example model with specific steps that we can follow to observe the issue.

Regardless, defect # 1004540 is not yet resolved; our developers will look into that for a future release. In the meantime, please try the workaround of re-assigning the customer meters with the query/selection set + LoadBuilder.

Hello,

Yes, I'm having the same problem with customer meters.  Sushma has submitted a defect with Bentley regarding Item 2 below.  Customer meter association seems to be lost when any of the following four actions is carried out:

1. Skeletonisation - all customer meters associated with pipes effected by the skeletonisation process lose their association to the model.  eg. two pipes joined in series creates one new pipe and deletes the old pipes.  The process doesn't move the customer meters, laterals and taps to the new pipe.

2. Manually re-assigning taps, laterals (and therefore customer meters) to a different pipe in a different zone.  The customer meter remains on the original zone after the "Pressure zone" tool is run.    

3. Pipe splitting - I find this only happens sometimes 

4. Merging nodes in close proximity  - depending on which node/s merges 

I thought I'd mention these issues as I think the errors might all be linked to one bug.

Meanwhile I'm using the workaround Jesse suggested - thanks 

Thanks for looking into it, 

Tracey  

I am using Connection Edition Update 1 10.01.01.04 64-bit.  Local Mott MacDonald IT pushed update 2 a few months ago, however, I had problems working one of our client's models using update 2 and we were on a deadline so I chose to switch back to update 1. 

So the problem is exactly as you described above, the scenario where I split the pipes automatically reassigns the customer meters after splitting the pipes, however, this is not the case for child scenarios (all child scenarios lose customer meter associations due to splitting an element in the parent scenario). 

I have been using your work around with the infant customer meters query and then running load builder, which seems to be the quickest solution for now.  Thank you. 

Regards,

Youssef

I am using Connection Edition Update 1 10.01.01.04 64-bit.  Local Mott MacDonald IT pushed update 2 a few months ago, however, I had problems working one of our client's models using update 2 and we were on a deadline so I chose to switch back to update 1. 

So the problem is exactly as you described above, the scenario where I split the pipes automatically reassigns the customer meters after splitting the pipes, however, this is not the case for child scenarios (all child scenarios lose customer meter associations due to splitting an element in the parent scenario). 

I have been using your work around with the infant customer meters query and then running load builder, which seems to be the quickest solution for now.  Thank you. 

Regards,

Youssef