Pipe schedule with room filter

[joel.lillie]

Hello,

I would want to do a pipe- and/or pipefitting schedule that can be filtered after rooms.

Because there isnt any "room field" to put in the schedule.

Is there any way I can add a "room field"?

[Anonymous]

it could be done by creating a shared parameter for pipes and you could use a dynamo to automatically fill that parameter.

[joel.lillie]

ok thank you.

Never tried Dynamo so I guess I have to learn that too!

[iainsavage]

I'm not sure that would work - the pipes would have to be completely contained within one room.

Anything passing through walls, floors, ceilings would be in more than one room so what would the parameter value be in that case?

Out of interest, why do you need this function?

[joel.lillie]

Its not that big of a problem if I know that could happen. I just put a weld joint at every point they go trough a wall.

I want this because we (our company) are also building our projects and often we do one room/Area at a time both at designing and building. and therefore we want to buy components by rooms/Areas (somethimes). because the next room aint always complete designed when we are building first room. (sorry bad english) 

So its much easier to control our material supply after rooms/ Areas. (Not always)

[iainsavage · Accepted solution]

That's a pretty unusual scenario.

Still not convinced the suggested solution will work for you unless you manually select the items in each room and apply the shared parameter value yourself. Using scope boxes or section boxes to visually break up the model might help with this selection process.

I think that even with Dynamo you'll struggle to get this to reliably work automatically. I'm pretty sure that pipes don't know which room/space they are in so I'm not sure how Dynamo would obtain that information from the pipe.

We often use the shared parameter method for splitting items by work package or work area but I've always populated it manually. 

I'd also maybe consider:

• individual models for each part of the project, linked into a master model (depends if you need to perform calculations on the overall systems) or
• individual phases for each part of the model - could be quite messy though and difficult to manage.

Hope this might be of some help.

[iainsavage]

....or different worksets.

[joel.lillie]

OK. I guess I manually give all components a shared parameter "Location".

It just feels strange that Revit cant separate components by room. I understand the problem with pipes that go through multiple rooms, but if you know that, its not a problem.

[RobDraw]

---

@joel.lillie wrote:

It just feels strange that Revit cant separate [pipes] by room. I understand the problem with pipes that go through multiple rooms, but if you know that, its not a problem.

---

In my world, pipes are almost always between the room bounding elements and not even in or passing through a (Revit) room. If you understand that, you will realize that this is a manual exercise that requires a non-programmatic solution or a different way of doing rooms along with additional functions not currently available for pipes.

[Mark.Friis]

This ist Importamt for Floor Hearing, since each pipe gives a certain amount of heat to the room

[iainsavage]

That is a bit different from the OP’s situation and in reality, although created from pipe, the floor heating is really a heat emitter element rather than “just” pipe.

I also don’t think that Revit would accurately give the correct heat output to the room from pipes modelled in the floor.

I would suggest then that you model your floor heating elements as a heat emitter (mechanical equipment) and then it can have parameters for pipe spacing, required pipe length (calculated from area etc, without needing to model the pipes), output, area, flow rate etc, and it can be tagged and scheduled etc. as mech equipment.

Unless you are actually a UFH designer or installer I wouldn’t bother modelling the actual UFH pipe coils and would just represent them with some form of simple geometry with a couple of connectors and the requisite parameters.

But that is getting off topic and there are other threads on this subject.