Piping elements being deleted and disconnected when linked architectural model is updated.

[paul.eterovichY6MNN]

I have been encountering a problem with hydraulic/piping models and I am wondering if you have encountered it and if you have a solution or advice.

Every so often, when an architectural model gets updated and the hydraulic model is then opened this error occurs:

“The family is connected in a network and can no longer keep the connectivity. Disconnect the family from the network?”

The only option to move forward is to click “Disconnect”

Then the next set of errors is encountered:

Again the only option to move forward and get the model to load is to click “Delete Elements”

It is possible to avoid these errors temporarily by opening the model, specifying that the architectural workset is not loaded, so that the architectural model is also not loaded.

However, once you try to reload the architectural model  the error messages display again.

The only solutions anyone can give me are:

1.

• Open the model without loading the architectural model.
• Delete the link to the architectural model.
• Relink the architectural model into the model.

2.

• Open the file with the architectural workset turned off.
• Create a level at datum level that’s not associated with the architects level.
• Reassociate the pipes to the datum level. 

These solutions come with their own problems such as having to set linked background views again and elements not being associated with their intended levels.

Apparently Revit is trying to adjust or reroute the elements to satisfy any updated level or hosting information that has come from the updated architectural model.

By not loading the architectural model and then deleting it you remove the information from the hydraulic/piping elements and I gather they become unhosted/ unconstrained/ disassociated from the level they were modelled to

floating in space, so Revit no longer tries to move them around to suit the new architectural levels or other information.

If you have any insight on why this might be  happening with piping models and if there is another way of fixing it or avoiding it I would appreciate it.

[iainsavage · Accepted solution]

As you say the problem will be that levels are being changed in the architectural model, fixtures etc move, Revit tries to "stretch" pipework to adjust but can't find a solution so has to delete elements. Usually a pipe has been reduced in length to the point at which the pipe length becomes zero or negative and then Revit has no option but to delete it.

If, in your model, you are using copy/monitored levels from the architects model then you should get a coordination monitor alert when something changes and have then the option to ignore or postpone the change so that you can manually adjust your model, moving levels and elements in a controlled manner to avoid or minimise breaking connections. 

The bigger question though is why is the architect repeatedly changing levels?

Also make sure that you are only copy/monitoring the primary floor levels - I've seen architectural models with levels for everything conceivable such as slab level, floor finish level, top of skirting level, window sill level, window head level, cornice level, ceiling level etc etc - ignore all of those levels and just monitor the ones which corresponds to finished floor levels, roof and parapet etc. Help says "Create a level for each known story or other needed reference of the building (for example: first floor, top of wall, or bottom of foundation)." 

Apart from that, the other advice you've been given seems reasonable but maybe have a conversation with the architect to ask why they keep changing stuff and when their model is likely to be mature and settled enough to allow you to use it with confidence.

PS: I would suggest that you do NOT remove the architectural link and then re-attach it - that will mess up all of your visibility settings. Use the "Reload from..." option instead without unlinking.

[dajeme4940]

This can happen because Revit tries to adjust or reroute the elements to satisfy any updated level or hosting information from the updated architectural model. Here are a couple of solutions that might help:

Open the model without loading the architectural model: Delete the link to the architectural model and then relink the architectural model into the model. Adobe products available at ProCADIS. Work with the architectural workset turned off: Create a level at datum level that’s not associated with the architect’s level and reassociate the pipes to this new datum level. These methods can prevent Revit from trying to adjust your piping elements according to the updated architectural information. However, they come with their own challenges, such as having to set linked background views again and elements not being associated with their intended levels. Another recommended practice is to ensure that all users are out of Revit before updating any links. After updating and managing errors, users should open a new local file, reload from the updated models, sync, and relinquish

[paul.eterovichY6MNN]

Thanks. This solution is in the original post.

[valentina_stoyanova]

I have the same problem, although there is no change in the elevation of the levels, but just their names.

[RSomppi]

---

@valentina_stoyanova wrote:

I have the same problem, although there is no change in the elevation of the levels, but just their names.

---

Same symptoms, different problem. Names changing will not affect piping like this. Your problem lies with some other hosting element(s) getting changed causing Revit to rework your piping. I avoid this by using non-hosted families that will not move when other models change. I'd rather coordinate after an update than have an update break my model.

[valentina_stoyanova]

Totally agree with you, @RSomppi !

[iainsavage]

---

@valentina_stoyanova wrote:

I have the same problem, although there is no change in the elevation of the levels, but just their names.

---

Are you saying that a change in the name of a level is causing your pipework to be deleted?

That sounds unlikely.

Even when the hosting elements are deleted the hosted elements usually just become unhosted, not deleted.

Are you sure nothing has moved in the architectural model?

[valentina_stoyanova]

Not deleted, but disconnected.

[iainsavage]

---

@valentina_stoyanova wrote:

Not deleted, but disconnected.

---

I don't think that could be attributed to a change in the name of the level.

Something else must be going on here.