The information manager on the project used Ares’ model to generate COBie (Construction Operations Building Information Exchange) data, another requirement for the project. The architects then pulled all models together in Solibri to check for clashes.

With the model in place, Ares used Vectorworks’ built-in IFC specifications to tag geometry for export. Bailey said they worked in 3D from the very start of the project because they knew they would need to deliver 3D models. The 3D model automatically generated 2D plans, not unlike the ones they used to produce in AutoCAD. This is all sounding painfully familiar, right?Īfter establishing such standards in their BIM Execution Plan, Ares modeled the site in 3D, using the architects’ building model for context.

That’s not to mention the cost of staffing when considering the large amounts of time spent working in multiple applications. It is not uncommon for these firms to use 3 or 4 separate applications to put together a concept, which inevitably leads to multiple payments that cost a bundle over time. To properly incorporate 3D modeling with embedded data, 2D-focused firms have to use separate software programs (note: “programs” is plural!). And it’s a dilemma more practitioners need to solve. Hanging on to 2D tools like AutoCAD for information modeling leaves landscape architecture firms in a dilemma. Even in places where there is no BIM mandate, there is some inherent pressure to deliver BIM files when working with consultants who have matured their workflows with BIM. The UK’s requirement for BIM level 2 framework on all government-procured projects is the most notable. The noticeable shift from 2D CAD in landscape architecture is in part due to external pressures.

Using revit for landscape architecture