Window Schedule Generator
Every window in the model as a schedule: mark, type, size, external flag and operation, grouped by type and ready for Excel.
Drop your IFC here
or
Large models work best on a desktop browser. Files above roughly 500.0 MB may exceed browser memory.
How it works
- 1Select an IFC file. It is read from your disk by your browser and goes no further.
- 2Every IfcWindow is read with its attributes and its property sets.
- 3Windows are grouped by type and size, so the counts are order quantities.
- 4Filter to one storey when you need a schedule per floor.
- 5Export as CSV, Excel or JSON.
About Window Schedule Generator
A window schedule is the same job as a door schedule and the same slow job by hand. The data is in the IFC already: every window carries a tag, a type, a nominal width and height, and, where the export was configured for it, an external flag and performance data.
The grouping is what turns a list into a schedule. Windows are grouped by type and size together, because that is how they are ordered. Two windows sharing a name but not a size stay apart.
Nothing is calculated. In particular, no glazing area is derived by multiplying width by height: the opening, the frame and the glass are three different rectangles, and a facade package priced on the wrong one is an expensive mistake to make quietly. Where the model states an area, the Quantity Extractor reports it.
Missing values appear as a dash and are counted at the top, so an export that dropped its dimensions is obvious before the schedule is issued rather than after someone tries to use it.
Questions
- Where does each column come from?
- The mark is the element's Tag, or its Name when there is no tag. The type is its ObjectType. Width and height come from the window's own OverallWidth and OverallHeight attributes, or from a quantity set when the attributes are absent, and the table marks which. The external flag, acoustic rating and thermal data come from Pset_WindowCommon. Panel operation comes from the entity, where IFC4 puts it.
- Why are two windows of the same type on separate lines?
- Because the grouping is by type and size together. Two windows sharing a type but built at different widths are two different products to order. If they should really be one line, the model records two sizes where it should record one, which is worth catching before a schedule goes out.
- Does it report glazing area?
- Only if the model states one. Where an exporter writes a window area into a quantity set it appears in the Quantity Extractor. What this tool will not do is multiply width by height and call the result a glazing area, because a frame is not glass and the difference is exactly what a facade package is priced on.
- What does a dash mean?
- That the model does not state the value, which is different from a zero or a No. The counters above the table say how many windows have no size recorded, so an incomplete export is visible before the schedule is issued rather than after.
- My windows have no sizes. Why?
- Some exporters leave OverallWidth and OverallHeight unset and rely on the geometry, and base quantities are frequently switched off too, so the numbers are not in the file at all. Enabling base quantities on export usually fixes it. Nothing here measures the geometry to fill the gap, because the opening, the frame and the glass are three different rectangles.
- Is my IFC file uploaded anywhere?
- No. The file is read by your own browser using a WebAssembly IFC parser. The model is never sent to FreeBIMTools or anywhere else, and there is no upload endpoint for it.
- Can it read a Revit .rvt file?
- No, and no browser tool honestly can. RVT is a proprietary format that needs Revit itself. Export an IFC from Revit and this tool will read it.
Was this useful, or is something missing? There is no rating widget here, because a thumbs up with nowhere to go is not feedback. Tell us what Window Schedule Generator should do, and describe the job rather than the feature.