The Creation of a Window
Featured in:
Join the Discussion!
- Login to post a comment
Print this Page
RSS Feed
We are often asked about the process for the creation of a SmartBIM Object. This article will take you through a detailed history of one window. The creation of a good SmartBIM Object is both a science and an art; there is not one fixed solution. To get the best results the process also involves considering both the needs of the manufacturer and the needs of the architect.
This article will follow the life of a double hung window with sidelights that was created for Kolbe.
Process
1. Customer — Kolbe asked for a proposal to create their doors and windows, they have an extensive offering that includes double-hung, casement, fixed windows, transoms, sidelights, French doors, sliding doors and more. Most lines are offered in both wood and aluminum clad. Windows have multiple trims, sill and molding options.
2. Background — In 25 years we have moved from hand drawing, to CAD and now to Revit (BIM). With hand drawing we would indicate a window in plan with three lines and in elevations with four to less than 20 lines. CAD allowed us to add a few more lines to make the objects look a bit more correct but the images were still fundamentally graphical representations, not accurate representations of the products, even when 3D versions of the products were created. With Revit you must have a 3D model (object) to insert into the project. We could take the approach of creating a simple object that would be a graphical representation of a window, with or without property data. When placed in a project anyone familiar with reading drawings would know that it was a window, early Revit projects most often used this approach and was certainly as good as the representations found in hand drawn and CAD created drawings. However, if you have a more sophisticated object to insert in the Revit project you get many advantages such as, 1) detailed product and model properties, 2) realistic representation of the size and shape of the object in plans and elevations, and 3) an object that will render correctly in perspective views and animations. Clearly if these sophisticated objects are available it is logical that they will be preferred.
3. Considerations — In the case of a window there is a long list of considerations such as:
- Sizes — The width and heights can be changed.
- Wall thickness — The window can be placed in any thickness wall. Will a jamb/sill extension be included to automatically resize for variable wall thicknesses.
- Glass and Screens — Glass can be simply shown as one thickness, or can be shown as the actual thickness and as single, double or triple glazed. Screens can be shown, but they will obscure the window.
- Casings/Trim — How many casings will be available and how will they be selected?
- Sill — How may sill conditions will be available and how will they be selected?
- Window Offset — Can the window be offset from the face of the wall toward the interior?
- Profiles — Will each unique profile for frame and sash be created for each product line?
- Divider Bars — Will they be available? Can the user set the number of vertical and horizontal bars, will cottage (prairie style) be included? Will divider bars be included between the glass, on the exterior, on the interior only or be selected by the user? If multiple profiles are available will they all be modeled?
- Renderings — Will the window render correctly? Can the user set different colors for the frame, sash, trim, and divider bars? Can the user do this on both the interior and the exterior?
- CAD details — Will they be associated with the window, included as an underlay, included as a collection of details on a “sheet”?
- Bays and Bows — Will they be included in the scope of work?
- Combinations and Transoms — Will combination windows be created or will the user assemble from individual windows?
4. Approach — There are no right or wrong answers to the considerations. It would be easy to say, yes we want everything, but there are problems with that answer, 1) costs 2) complexity and 3) file size. Kolbe decided that the best approach was to conduct a detailed study to look into each of these considerations so the advantages and disadvantages of different approaches could be evaluated. Based upon the results of this prototyping process the decision to proceed would be made by Kolbe.
5. Prototype — The prototype was created based upon discussions and experiments and it was decided to proceed. The decision was to create very sophisticated windows, windows that would have considerably more functionality, and hopefully more value, than anything available for Revit users.
6. Kick Off Meeting — A two day meeting took place at Kolbe plant in Wisconsin with the Reed modeling team. Discussions included a careful review of the scope, the availability of CAD drawings, degree of accuracy; degree of parametrics (is it better to create one highly parametric object or many less parametric objects). A plant tour took place so Sree (primary modeler and manager of modelers) would be able to see and understand how the windows go together. At this meeting several decisions were made. Kolbe wanted to pursue a very detailed and comprehensive set of Revit models to represent their window and door products to highlight their product features and also to differentiate them from their competitors. At the point of the kick off meeting, there were several features that were deemed very important to accommodate in Kolbe’s Revit models:
- A flexible number of lites in each window model. Rather than have a fixed number of lites, a parametric model would offer the architect a chance to reuse the model in many different designs and to have flexibility with an prominent design element
- Geometry that allowed the architect to see the Kolbe features, realized in the Revit model. Kolbe offers customers a chance to have different interior vs. exterior colors. As geometry in Revit can only be attached one material value, a common geometrical extrusion was broken into two more coordinated pieces so that each could potentially be given a different color.
- Although not a technical part of the window, brickmould and sill nosing are a significant design element and it was decided to accommodate the multiple options with a separate sill assembly tool that allowed the user to match certain sill nosings with certain brickmould. Moreover, every window comes with a standard brickmould and sill nosing pair that can be turned on and off to suit the situation.
7. The Creation Process — Models were created based upon both trial and error on the Revit modeling side as well as regular reviews with Kolbe to insure that we were representing their products correctly and to the level of detail that was important to them. To create excellent objects is a major effort, but the results are worth the effort. Following is a sampling of the concerns and results of the modeling process.
a. Grilles
A unique model feature we put into the Kolbe models were the parametric grilles. These permit the user to render a model that has no grilles to a more conventional 3x3 arrangement, without downloading a separate model to accommodate the two different situations. You can see from the image below that a user can select the number of Vertical and Horizontal Lites.

This feature required a significant amount of thought and experimentation to overcome the limitations of the array data structure. By its nature, an array is a grouping of objects that are two or greater and so there is not an option to have a one vertical mullion and/or one horizontal mullion setting. To accommodate this, the Grille assembly had to be built as a collection of different parts; the actual array of vertical and horizontal mullions as well as the 2x2 fixed lite assembly (composed of 1 vertical and 1 horizontal mullion member).
Having done this, the families now had to coordinate the visibility and manipulate the component pieces based on the number of lites selected by the user. So for example, if the user wanted a 2x3 lite arrangement, it would “turn on” the 1 vertical mullion (2 horizontal lites) and “turn on” the horizontal array and set it at 2 visible mullions (3 vertical lites).

b. Profiles
To insure optimum accuracy, Reed worked with Kolbe to gather the corresponding CAD details for every window and door model that was completed. Using these files, various geometric profiles were produced and then assembled to create the jambs, headers, sill nosings and so on.
However, to give the user the option to give separate color assignments to both interior and exterior geometries, the mull for example would have to be broken into two distinct geometries that had to be kept coordinated.

c. Brickmould
On every window model, Brickmould and sill nosing geometry was included and were also given specific visibility parameters to allow the user to turn them on and off as they required.

The implementation of this feature led to a cascade of other modifications that had to be done throughout the model. For example, all Kolbe models have a set of detail items — for plan view and elevation view for example. When the brickmould was turned “off”, these details also had to be coordinated so that they are not showing an inconsistency in the 2D representation when compared to the 3D model.

Lastly, there is the possibility that when the architect turns off the brickmould that he/she would maintain the visibility of the sill nosing. However, the sill nosing normally extends under the brick mould but if the brick mould is not present, it would not extend beyond the jambs. This additional level of detail had to be accommodated into the models as well that took into account whether the visibility parameter for the brick mould would be on or off, and then adjusting the length of the sill nosing accordingly.
d. Casing
One of the most challenging objects constructed for Kolbe was the Casing Sill Assembly tool. Essentially Kolbe offers its customers numerous Casing profiles as well as Sill nosing profiles to their customers. However, there are certain Casing profiles that do not go with certain Sill Nosing profiles. This family involved including profiles of all the possibilities, letting the user select the Casing profile as a driver, and then select the Sill Nosing thereafter. As they went through the Nosing options, certain options were available but others were not. This was implemented by accounting for all the options and use of the "and () and not ()" Revit functions.

e. Limiting Nested Families.
Revit families tend to get very large very quickly as there are more and more nested families loaded within it. For some of the more complicated models, for example Kolbe’s Window_Double-Hung-3-Wide-Traditional_Kolbe model, it was tempting to reuse the individual double hung windows that were already created and just group them together. However, this method generates enormous files (over 6MB depending on the complexity of the single unit family) that are also too demanding on the hardware.
This forced us to build our models in such a way that the nested families were limited as much as possible, and that we redrew and constrained the individual sweeps and extrusions as much as possible in the main family itself. Very complicated and redundant families were still used (Grille Assembly for example), but this helped in alleviating a good portion of the file size.

f. Detail Items
To accurately represent Kolbe windows — Reed utilized the CAD files given to us by Kolbe to create plan and elevation details for every object created. However, very early on we found that building exact details from the CAD files was a big contributor to file size, slow performance and a bad user experience. Although we’re only concerned with 2D lines, Revit has a hard time representing all the detailed curves and angles in a architecturally correctwindow down to very small file sizes. Most importantly, when an architect places many windows in plan and shows these objects — the details oftenget lost and are they are not clearly shown.
With details — it’s best to limit the RFAs to rough and simple line work and allow the architect to rely on individual CAD files or Detail Items using the Revit Call Out function to properly detail their Construction Documents.

g. File Size
A simple solution for too many files is using “Purge Unused” regularly prior to saving your file. This removes objects (and/or types) that are not being used within the RVT or RFA. More importantly, this should be done for all the nested families as well to insure that you are working with the bare minimum in file size.
Rename the file or save it in another location. This forces Revit to internally purge some contents within the family that Revit sometimes does not do by using the Purge Unused command. This often can reduce as much as 50% of file size in the model.
f. Build, Test, Rebuild
When working on such a detailed and involved project, we often tested the boundaries of what Revit would do and had to come up with new design methods to implement ideas that we wanted conveyed to Kolbe’s Revit models. In some cases however, we had to step back to work within Revit’s limitations for performance and file size.
Many of Kolbe’s original models required us to test a design idea and then sometimes take a new approach or at least modify it so that we could have a functional model. Especially regarding file size, there were a few factors that helped limit this from making these complexes overwhelming in their size.
8. Completed Windows and Doors — We have completed a collection of hundreds of doors and windows for Kolbe. These are the most complete collection of manufacture windows and doors available to Revit users.

9. Distribution — The Kolbe SmartBIM Objects are now widely distributed through
- Kolbe site
- SmartBIM Library (a Revit object management tool that sits on the architects desktop)
- Autodesk SEEK
- Reed SmartBuilding Index
- Reed SmartBIM.com
10. Reception and Use — The response has been excellent. Traffic has increased to the Kolbe website and the number of downloads of the Revit files are significant along with a lot of interest in the Kolbe monthly webinars about the Revit models. Architects are impressed with the models, they like the options and have confirmed Kolbe took the right approach with their models. Many architects are just beginning to learn Revit, but those that are using it tell Kolbe and Reed that Revit is definitely the future.
Member Comments
how bored are you Brian that you need to use this article as your soap box so that we can all be enlightened by your vast experience BIM?
learn to spell jackass
Brian,
I am one of the authors of the article. A bit of history on my experience, I started an architectural firm in 1970 so I have many years of hand drawing. In 1985 my software firm created and licensed to Autodesk the products AutoCAD AEC Architectural and AutoCAD AEC Mechanical. I have started and run several software companies dealing with CAD, BIM, automation of manufacturer’s information and automation of facilities management.
You are correct; I should have said “hand drawing, to CAD (AutoCAD) to BIM (Revit). Reed creates software and objects for BIM and we are not exclusive to any BIM application. However, Revit has captured about 80% of the market so our requests for objects from manufacturers have been for the Revit application; these requests are driven by the marketplace.
The focus of the article was not a “tour of BIM”, it was a detailed focus on the process of creating a Revit object and the expertise that is needed to create an excellent object, in our case a Reed SmartBIM Object. I have written several articles on BIM that are available on the Reed site, some BIM oriented and others Revit oriented depending upon the focus. I also gave a talk at the 2009 AIA convention on the future of BIM as related to analysis and simulation.
Thank you for taking some of your valuable time to respond to the article.
Thank you for the article. The process details the very constraints that most of us new to Revit are coming up against when trying to develop our own custom families. It’s a full time job for a trained staff, and not one to be undertaken by a novice. Thus, the monumental need for free content online so architects can do what we do best - design! Keep up the good work, and keep the content coming!
And to the guy who can’t spell: Read the title of the article and you get a pretty good idea of what it’s about.



I worry about the future of RCD in our office when it published a lead article written by amatuers: “In 25 years we have moved from hand drawing, to CAD and now to Revit (BIM).” Is it really necessary to spank these kids for their insensitivty ignorance or bias (whatever is going on with them) when they write “Revit (BIM)”. Revit is actually a latecomer in the BIM sense, and there are other (if not better) solutions that answer on the BIM concept. Stop right there. Time is valuable. Why read any further. In fact, the whole concept of the article is a silly waste of time if we are interested in a tour of BIM. Time to get some adults in the editorial (and writing) department Reed!. And give these kids a pep talk and some brain supplements. They can do better! Have them run around the block a few times. But don’t waste our attention spans with immaturity and pedestrian articles! (Otherwise RCD has some continuing promise).
is like sayon inapproprring in the objectivity police to explain to the young mins that there are solutions other than Revit which deliver on the BIM concept? At least they did not refer to the Dietzhand drawing as a Dietz
I was discoyuraged from reading further (time is valuable, I try to read authoritative sources only. RCD should not have allowed this level of industry slight to occur in a lead article. Either the authors are genuinely insensitive to the distinction between Revit as a brand and BIM as a concept - or they are foolishly biased. Is it really necessary to bring in the objectivity police to explain to the young mins that there are solutions other than Revit which deliver on the BIM concept? At least they did not refer to the Dietzhand drawing as a Dietz
Insensitivy on the distinction between Revit and BIM ian industry slight to pass