Storefront/Curtain Wall

[Anonymous]

I am working on a project that has glazed partions(interior storefront) with doors in them, when I generate the door schedule I want the storefront size to be displayed in the door schedule, does anyone know how or even if this can be done?  If not what is everyone's solution around this?

[barthbradley]

What do you mean by "storefront size to be displayed in the door schedule"? Are you wanting the Door itself to report it's host wall's properties (i.e. length, height,etc.)? 

Or, your you asking how to GROUP/SORT doors by their host wall.  If this is what you are asking, then one approach would be to give the doors Mark values that identify their host wall, and then Sort/Group by Mark.  

[cbcarch]

I think he's asking for the door schedule to report the thickness/depth of the storefront--i.e. 4.5", 6" etc.

I think a reporting parameter in the cw door can do it?

[barthbradley]

 A reporting parameter for wall thickness in a CW Door family?  Can you do that? 

[Anonymous]

What I am looking for is say for instance the storefront is 8’x7’ I want that to report in my door schedule

[ToanDN]

Let's say if the curtain wall (storefront) is 8'x7' and the curtain wall door is 3'x7'.  There is no live connection between the two.  Workarounds:

- add new parameters to the door schedule and manually enter the value of the storefront

- built the door family with the sidelites/transoms included and use reporting parameters to report them in the schedule (it will drastically change how you create the curtain walls and grids)

- add a few reference planes/lines in the door family and associate them with instance shared parameters, upon inserting the door in the curtain wall, manually match them to the overall size of the curtain wall using align or grip stretching, then you can report them in the schedule

[barthbradley]

Revit doesn't have Wall Aware families. You'll need to manually enter that information into a reportable Parameter field in the Door Instance Properties.  You could you the existing "Comments" field for example.