Angondje Community, Libreville, Gabon: A new modular paradigm in Building Information Modeling

As powerful as Building Information Modeling (BIM) tools are in modeling the built environment, current BIM strategies limit the size of facilities that can be modeled while increasing the time needed for modeling and the quality of BIM models produced.

In the same way that prefabricated modular construction techniques are improving the speed and quality of construction delivery, a modular approach to BIM modeling substantially increases the scale of facilities that can be modeled while decreasing modeling time and increasing model quality. As a case study of this new approach we will look at Bechtel’s design for a new community in Angondje, Libreville, Gabon where 6,000 dwelling units using 21 different building types for a population of 30,000 people were produced.

Background

Great strides are being made in prefabricated modular construction technology such as Bechtel’s use of ModSpace’s workforce housing in remote Labrador City, Canada and the erection of the 30 story T30 hotel in China in only 15 days. These impressive improvements in speed and quality of construction have not been matched on the design side. As Building Information Modeling (BIM) technology has matured and organizations have brought ever larger buildings and facilities into the BIM workflow, the traditional BIM approach of capturing almost all of a facility in a few linked models has caused increasing difficulties. These very large model files cause serious issues:

  • for collaborating with others in file transfer times,
  • for quality of the model where tens of thousands of modeling errors are not uncommon,
  • for easily reusing updated components across a portfolio of projects,
  • and for working efficiently on the model where ever more powerful workstations are unable to keep up with the strains of growing model size.
Figure 1. Rendering of Angondje, Libreville, GabonFigure 1. Rendering of Angondje, Libreville, Gabon

As a case study for this paper, we will look at Bechtel’s design for a new community in Angondje, Libreville, Gabon. The development comprises a range of housing options for all income levels as part of neighborhood development that will include hospitals, green areas, roads and schools together with infrastructure to support it for a total population of over 200,000 people.

What is BIM?

Building Information Modeling (BIM), according to the US National Institute of Building Sciences, is “horizontally integrated building information that is gathered and applied throughout the entire facility lifecycle, preserved and interchanged efficiently using open and interoperable technology for business, functional and physical modeling, and process support and operations.”[1]

Traditional Computer Aided Design (CAD) systems deal with two dimensional representations composed of lines and arcs and other entities that have no “awareness” of their role with respect to adjacent lines and arcs or in the system of the facility as a whole. BIM, on the other hand, allows the creation of models using “intelligent” three dimensional objects that are “aware” of other objects they connect to and how they need to interact. For example, a door “knows” that it cuts a hole in the wall, and the wall “knows” that if it moves, the door must move with it, and the dimension linked to the wall “knows” it must change accordingly as must all the data tags associated with the wall. Additionally, these objects can be instances of classes of objects that can be defined with complex relationship logic and interference requirements with embedded parameters allowing use in a wide variety of specific cases.

In the case of Revit, the model is captured in the form of a database where all information is stored within three distinct environments, the underlying model itself, the views looking at the model, and the sheets containing the views. View objects are used to gain a real-time view of the model and define whether, for example, the desired view should be a two-dimensional slice through the model at a particular place, a three-dimensional view using particular camera settings, or a schedule listing out data about the model. All annotations in the view and graphic settings are stored within the View object and are not a part of the model environment itself. These view objects can be placed on sheets and then additional annotations and parameters added in the sheet environment. Similar to a wall, a sheet “knows” the views that are on it and automatically coordinates all annotation references within the views with the proper parametric sheet information.

Standard industry practice and the current trend is to have as few BIM models as possible in a project, usually split between disciplines. Large projects, such as SOM’s Freedom Tower, are produced with as few as 5 linked models. Strategies for breaking up BIM models revolve around staffing issues rather than the underlying facility structure.[2]

The problems with massive BIM models are numerous, including serious difficulty in collaborating with remote locations given large file sizes. Even with a BIM solution like Revit, where element level permissions within a model are used allowing a team of people to work on the same model at the same time, whenever a team member saves their changes to the central model, all others are prevented from saving or loading the latest changes until the save is complete. In a very large file with many people working on it, this intermittent locking can truly bring progress to a halt, especially during intense deadline periods when productivity is needed most.

As these BIM models increase in size, ever more powerful workstations are needed to process them leading to a strategy of breaking up models based on what a workstation can process.[2] Additionally, because of the massive amount of data in one model, it becomes increasingly difficult to maintain and correct the errors that conflict-detection systems find between various elements.

The most serious problems with large models, however, are the inability to easily reuse and maintain a library of well engineered components captured from earlier completed work and updated through time, and the inability to scale projects successfully to ever larger facilities and ever greater numbers of buildings with increasing levels of productivity.

Project aims and objectives

Figure 2. Rendering of Phase 1 of Angondje
Figure 2. Rendering of Phase 1 of Angondje

In phase 1 of Angondje, where the Bechtel team was faced with designing over 6,000 dwelling units using 21 different building types for a population of 30,000 people, a traditional BIM approach with a few massive files would simply not have worked. Instead, a modular BIM approach was developed and deployed.

Our goal was to produce the highest quality design and production documentation possible in a short time with a small team of three people while at the same time being able to make design changes rapidly. Additionally, the intent was to extend the use of the BIM model from design through construction and beyond.

Project Approach: The Modular BIM Paradigm

Figure 3. Rendering of Parcel 1, Phase 1, Angondje
Figure 3. Rendering of Parcel 1, Phase 1, Angondje

Our design program called for buildings that could be easily prefabricated, and this modular approach to the design naturally led to a modular approach to BIM modeling.

Figure 4. 2APT-3 Building Type
Figure 4. 2APT-3 Building Type

As we continued to design different building types, it quickly became evident when parts of buildings could be shared that separate models could then be linked to both types. This process led to the principle that modules should always be created if the building sub assembly is used more than once within any building or across different buildings. This modularity allowed a very high level of quality in the models and drawings as all information only needed to be drawn once and revised and corrected in one place with automated updating of all affected sheets in the various building models and drawing sets.

An example of the modularity is the level 2 quality three bedroom six unit apartment building (2APT-3) shown in Figure 4 and expanded in Figure 5.

Figure 5. Expanded View of 2APT-3 Building Type
Figure 5. Expanded View of 2APT-3 Building Type

Figure 6. 2APT-3 Module Hierarchy
Figure 6. 2APT-3 Module Hierarchy

This building is assembled using a total of 14 separate modules with 5 separate Revit model links at the top level in the main building model as shown in Figure 6. Only one model link is used for the typical three bedroom apartment (2APT-3-A) and copied and mirrored in addition to the ground level apartment (2APT-3-A0) to give the building six units. The roof link is used in a 2 story version of this building. The apartment unit links are used in both a 2 story version of this building and a mixed use building which has commercial at the ground floor.

These 5 module links of the main building are further broken down into modules as shown in the typical 3 bedroom unit model (2APT-3-A) in Figure 7 made up of a total of four modules. The rear module (2APT-3-BDRM) varies based on the bedroom count of the unit, and the façade (2APT-FCDE-A) varies among buildings.

Figure 7.  Modular Components of 2APT-3-A Unit Type
Figure 7. Modular Components of 2APT-3-A Unit Type

The 2APT and 2MIX building types shown in Figure 8 are made from a total of 49 modules. Similar building types, such as 2APT-4 and 2APT-2, share 78% of their modules. The graph in Figure 9 shows the model link structure for the seven total 2APT and 2 MIX building types.

Figure 8. 2APT and 2MIX building Types
Figure 8. 2APT and 2MIX building Types

Figure 9. 2APT & 2MIX Module Link Structure
Figure 9. 2APT & 2MIX Module Link Structure

Production Drawings

For the Angondje housing, our task was to document 30% complete preliminary engineering drawings which resulted in a set of roughly 200 A1 size drawing sheets for the 21 building types. Revit allows hierarchical inheritance of view settings and all their associated annotations from linked Revit models. The views for any module reside in that module’s model file, thus linking together modules to create various building types automatically results in complete detailed and annotated drawings. As an example, Figure 10 shows the complete Level 2 Floor Plan for the 2APT-3 building type.

Figure 10. Sheet 25608-PL00-A-2APT-3303 – Floor Plan Level 2 for the 2APT-3 Building TypeFigure 10. Sheet 25608-PL00-A-2APT-3303 – Floor Plan Level 2 for the 2APT-3 Building Type

Figures 12 through 16 show the views from the various modules which are linked together to form the Sheet shown in Figure 10.

Figure 11. Example Material ScheduleFigure 11. Example Material Schedule
Figure 12. APT-FCDE-2
 
Figure 13. 2APT-3-BDRMFigure 13. 2APT-3-BDRM
Figure 14. 2APT-BATH
Figure 14. 2APT-BATH
 
Figure 15. 2APT-LVNGFigure 15. 2APT-LVNG
Figure 16. 2APT-FCDE-A
Figure 16. 2APT-FCDE-A
 

Figure 17. 1MFA, 2APT, 2MIX & 3MIX Plotting Hierarchy
Figure 17. 1MFA, 2APT, 2MIX & 3MIX Plotting Hierarchy

Separate model files were created for plotting each building type and then linked to sub and master index files for plotting the sub and master index sheets as shown in Figure 17.

Scaling to Thousands of Buildings

Figure 18. Parcel 1 Module Hierarchy
Figure 18. Parcel 1 Module Hierarchy

As buildings were added to the parcels, the performance degraded to the extent that an alternative solution had to be found even after turning off the visibility of all non-needed elements. A separate model was created for each of the 10 parcels in phase 1 and further broken down into separate street blocks with buildings linked as needed into the blocks as shown in Figure 18.

Because access was needed in the parcel model to many parameters about the various buildings such as quality level and bedroom count as well as building areas, we embedded all the parameters in the unit area objects and referenced those into the roof modules. The roof modules were then linked directly into the parcel blocks bypassing the rest of the modules that make up the buildings dramatically improving performance. Figure 19 shows a typical Parcel plan with shadowed roof objects.

In addition to using the SmartCode for master planning the community, many requirements were added by ANGT to design certain quantity percentages based on quality level of buildings as well as constraints about adjacency of various quality buildings on the site. As the schedules are real-time views into the database, we were able to use the schedules as design tools to maintain conformance with all requirements. A sample of the Parcel metrics is shown in Figure 20.

Figure 19. Parcel 1 Housing Site Plan
Figure 19. Parcel 1 Housing Site Plan

Figure 20. Example Parcel Metrics
Figure 20. Example Parcel Metrics

Master Planning - SmartCode

The SmartCode, a model form-based unified land development ordinance designed to create walkable neighborhoods across the full spectrum of human settlement, was used as the key master planning design guide for Angondje.

The SmartCode uses complex formulas and relationships which were captured with parameters in the zoning areas. These parameters automatically controlled color and were reported in schedules capturing the various zoning algorithms allowing real-time design and analysis as shown in Figure 22 with an example of metrics shown in Figure 21.

Figure 21. Example SmartCode Metrics
Figure 21. Example SmartCode Metrics

Figure 22. SmartCode Community Zoning Plan – West
Figure 22. SmartCode Community Zoning Plan – West

The SmartCode includes strict parking requirements that potentially limit the area of development. Parking compliance was confirmed using lot and unit based parameters as well as parking element parameters. Each lot object has parameters that describe the zoning and other parking factors, and each unit has parameters describing the building type and quality level of the unit. This information is then used in Revit schedules to compute parking requirements based on the lot characteristics. For example, in the case of a Mixed-used building, Revit will automatically compute parking requirements for each of the dwelling units as well as separate parking requirements for the commercial space. However, in the case of a single family house, Revit will only compute a residential parking requirement.

Figure 23. Parcel 3 SmartCode Parking Analysis
Figure 23. Parcel 3 SmartCode Parking Analysis

Unique Unit Identification

The construction management team in Gabon required a unique identifier for each unit in Phase 1 as well as parameters to track the progress of construction on each unit. Unfortunately, Revit does not treat model links as objects to which parameters can be attached, nor is there a way to create a relationship between a Revit model link and another object. The only option until these missing features exist was to create new objects that would represent each individual unit.

A case where Revit is able to “sense” a relationship is when an object of furniture is within a room volume. The furniture object can inherit all the parameters of the room in which it resides. With that relationship in mind, we created a special furniture object (unit-object) with all of the many parameters being tracked and turned the lots into rooms in the block models such that the lot rooms contained all of the parameters about the lot such as zoning, unique lot id and area.

Consequently, whenever a unit-object was moved into a lot, it would automatically inherit all of the lot information from the lot-room which was then used in automatically forming the unique unit identification tag. Given the quantity of units, we developed several schedules to check for and correct any errors.
Figure 24. Unique Unit Identification Tags
Figure 24. Unique Unit Identification Tags


Figure 25. Construction Progress Parameters
Figure 25. Construction Progress Parameters

Project Outputs and Outcomes

A new modular approach to BIM requires less time for design and modeling while increasing the quality and scale of facilities modeled. This new approach can also lead to an increasing portfolio of well engineered BIM modules that open new opportunities in modular construction delivery.

Key Learning Points

The exercise of creating unique dwelling unit object references for construction management inside Revit was very time consuming and prone to human error. Data contained parametrically in other parts of the model was duplicated, making high data quality very difficult. Additionally, maintaining the data requires Revit use which is not necessarily easy on a project site. Rather than trying to capture extended data in the BIM model itself, the better strategy is to have the BIM model 10 serve as the master index for external data using global unique identifiers for each BIM object (GUID)[3]. In future cases of extended data, this technique will be used to connect to external databases with the potential for a cloud solution providing the platform for full building lifecycle collaboration.

References

[1] “United States National Building Information Modeling Standard”, National Institute of Building Sciences, Version 1 – Part 1 : Overview, Principles, and Methodologies, December 2007.
http://www.wbdg.org/pdfs/NBIMSv1_p1.pdf

[2] “Managing Large Projects in Revit Architecture”, Lonnie Cumpton, Autodesk University, AB100-1P,
http://forums.autodesk.com/autodesk/attachments/autodesk/
133/39138/1/managing%20large%20projects%20in%20RAC.pdf

[3] BuildingSmart Alliance’s IFC (Industry Foundation Class) 2x3g and upcoming 2x4 BIM file format support global unique identifiers (GUID).