We often use modules to place buildings onto a site. This gives us a lot of flexibility and freedom to position and locate the building(s) within the terrain, without the need to use excessive grouping or difficult selections. It also allows buildings to be documented orthogonal to each other, regardless of final positioning on the site.
If, however, a single building or orthogonal cluster of buildings is the final design, it is almost always easier to avoid modules, and simply reposition the site around the buildings to make adjustments.
Here is a chart to help determine wether modules should or shouldn’t be used to place buildings onto the terrain. In the case of this chart, we can assume “Maybe” is understood as “probably not”. The important thing to note is , if the project entails a single building on a fixed position (infill lot), modules are never used, and if a project is to be a multi-building design of non-orthogonal or non-interconnected buildings, modules should always be used.
Often times, we document buildings and place their hot links into the same file. For smaller projects and sites with few modules, this is a quick and easy way to start with no need for attribute coordination. It is important to note, this does not work on most WWA projects, the sites tend to be too large, or have too much vegetation (polygon warning), or have too many buildings resulting in slow building/site file. Typically for these projects, we break the building and site into separate teamwork files.
But, for the cases where we do not need to model the building and site in separate files, and still want to use hotlink modules, we need to control how elements schedule. If an entire building is hotlinked into it’s own file, the content is technically duplicated. So how do we show one instance of the element in the schedules? It is one simple criteria that needs to be added to the schedule.
Set a new criteria that says Hotlinked Module is not Any Hotlink. This will restrict the schedule’s content to only elements in the primary model, and exclude any item located with in an HLM.