Curtain Systems

[Anonymous]

Hi all,

I'm working on a project at present with a large number of curtain walls. We are producing a schedule for costing and need to read off the height and width of each curtain wall system individually.

For the purpose of scheduling and to mitigate the number of lines in said schedule we are trying to treat corner pieces as one element. Here is where the issue arises.

We can obviously schedule all the walls fine but we cannot schedule the corner pieces as one element. I have created a curtain system (as opposed to a wall) from a mesh mass which works as a single system but obviously will not appear within the schedule of curtain walls. To add to the issues, once you have created a curtain system you cannot schedule the height/length.

Has anybody encountered a similar problem before?

Ta

[XXalessio.amodioXX]

try to use Shared parameters

[Anonymous]

Hi Alessio, I don't think using shared parameters will help.

I cannot create a schedule for BOTH curtain walls AND curtain systems, you can only create these as two separate schedules.

The only thing I can think to do is model everything as curtain walls and create an instance project parameter for length. This should then allow me to manually add the length and effectively dictate that the curtain wall is longer than it is. If I then only include one of the walls and not the other it should get me the output I want.

This is however very messy and I wondered if anybody had found a way around this in the past.

[Anonymous · Accepted solution]

Can you not create a parameter that can include something like 'Corner wall' and then have a condition that states If parameter = Corner wall, Length + Additional Length, Length. Then, most CWs would not contain corner wall, so their length is returned, but if a CW is a corner unit then add the additional length, also an added parameter.