Landscape Architecture BIM: Why IFC Matters More Than the Software You Use
BIM isn't about using the same software. It's about exchanging reliable information.
If you've worked on multidisciplinary projects for any length of time, you've probably heard some variation of the phrase:
"Can you work in Revit?"
It's an understandable question.
As Building Information Modelling (BIM) becomes increasingly common across Australia's design and construction industry, many consultants assume the key to successful collaboration is everyone using the same software.
In my experience, that's rarely the case.
The real value of BIM isn't that every consultant uses the same program.
It's that every consultant can exchange accurate, coordinated information.
That's where Industry Foundation Classes (IFC) become far more important than the software itself.
BIM Is a Process, Not a Program
BIM is often misunderstood as a piece of software.
In reality, BIM is a process for creating, managing and exchanging coordinated project information throughout the life of a project.
Whether a landscape architect is using Vectorworks Landmark, an architect is working in Revit, a structural engineer is using Tekla or a civil consultant is modelling in Civil 3D, the objective is the same:
Everyone should be working from coordinated information.
Good BIM isn't achieved because everyone owns the same software licence.
It's achieved because information can move accurately between consultants.
The Problem With Software-Centric Thinking
I've occasionally encountered projects where BIM coordination becomes less about information exchange and more about software preference.
Questions like:
"Can you work in Revit?"
"Do you have an Archicad licence?"
"Can you just model it in our software?"
often miss the bigger picture.
Landscape architects have specialist workflows that differ significantly from architects or engineers.
Plant scheduling, grading, site modelling, hardscape detailing and landscape documentation all benefit from software developed specifically for landscape practice.
The objective shouldn't be forcing every consultant into the same application.
The objective should be producing coordinated information that works for the entire project team.
Why IFC Matters
Industry Foundation Classes (IFC) provide an open format for exchanging BIM information between different software platforms.
Rather than asking every consultant to work inside the same ecosystem, IFC allows each discipline to continue using the tools best suited to their work while still contributing to a coordinated project model.
For landscape architecture, this means site models, hardscape elements, planting, levels and other landscape information can be shared with architects, engineers and builders without recreating geometry from scratch.
The result is better coordination and fewer opportunities for information being lost between disciplines.
Landscape Architecture Has Different BIM Requirements
Landscape architecture isn't simply architecture without walls.
Our projects involve dynamic landforms, drainage, planting systems, retaining structures, irrigation, paving, streetscapes and public spaces.
Many of these elements continue to evolve throughout design development and construction documentation.
Landscape BIM workflows therefore need to support:
site modelling
grading analysis
cut and fill calculations
planting schedules
hardscape assemblies
irrigation coordination
consultant coordination
documentation outputs
These are specialist requirements that deserve specialist tools.
My Workflow
For my own projects and consulting work through Place Supply, I use Vectorworks Landmark as my primary BIM platform.
It provides an efficient workflow for landscape architecture while allowing coordinated information to be exchanged with the broader consultant team through IFC and other common industry formats.
That means I'm able to collaborate with architects, planners, civil engineers and structural consultants regardless of the software they choose to use.
The software itself is only part of the equation.
Reliable information exchange is what ultimately supports better project outcomes.
BIM Improves More Than Coordination
Good BIM workflows don't simply reduce clashes.
They improve the quality of landscape documentation itself.
Working within a coordinated model allows landscape architecture to respond more effectively to architectural changes, engineering revisions and site constraints as projects evolve.
This creates more reliable documentation for development applications, construction certificates and construction documentation.
Ultimately, better coordinated information benefits everyone involved in the project—from designers and consultants through to contractors and clients.
BIM Is Becoming Increasingly Important in Australia
As projects become larger and more complex, coordinated digital workflows are becoming increasingly common across both public and private sector developments.
For landscape architects, this presents an opportunity.
Rather than viewing BIM as an architectural requirement, we can embrace it as a tool that improves design coordination, documentation quality and long-term project delivery.
Open standards such as IFC make that possible without requiring every consultant to abandon the software best suited to their discipline.
Looking Beyond Software
Software will continue to evolve.
New platforms will emerge, existing programs will improve and project teams will continue to adopt different digital workflows.
What shouldn't change is the ability to exchange reliable information.
In my view, successful BIM coordination isn't determined by whether every consultant uses the same software.
It's determined by whether every consultant can contribute accurate, coordinated information that helps the project move forward.
For landscape architecture, that's where IFC becomes more important than the software itself.
Final Thoughts
Landscape architecture has always been about coordination.
We work between architecture, civil engineering, structural design, planning, ecology and construction.
BIM simply provides another tool to strengthen those relationships.
The software we use matters.
But the information we share matters far more.
Comments