Authoring software is used to create and edit models: placing walls, beams, ducts and roads, and producing drawings and schedules from them. Each discipline has its own common tools. This entry describes the families neutrally; BIMpedia does not recommend one product over another.
At a glance
| Discipline | Commonly used tools (examples) |
|---|---|
| Architecture | Autodesk Revit, Graphisoft ArchiCAD, Vectorworks Architect, Nemetschek Allplan |
| Structure | Revit, Tekla Structures, Allplan Engineering, Bentley OpenBuildings / ProStructures |
| Building services (MEP) | Revit, MagiCAD, Trimble design tools, DDS-CAD |
| Civil and infrastructure | Autodesk Civil 3D, Bentley OpenRoads / OpenRail, Trimble Novapoint |
| Fabrication and detailing | Tekla Structures (steel, precast), fabrication add-ons for MEP |
| Landscape and site | Vectorworks Landmark, Civil 3D, specialised add-ons |
Many tools are extended by add-ins and scripting (for example Dynamo and Grasshopper) for automation.
What authoring tools have in common
- Objects, not lines: elements with types, properties and relationships.
- Types and instances: shared definitions reused across the model.
- Views from one model: plans, sections and schedules are generated, so they stay consistent.
- Collaboration features: work sharing between several people on one model.
- Export to IFC and other formats for exchange.
What to agree when teams use different tools
- The exchange format and version, usually IFC with a named version and MVD, and export settings per tool.
- Coordinates: each tool's base point and survey point set up to the same georeference.
- Units and precision.
- Classification and property mapping, so information arrives where others expect it.
- Element ownership: who models what, to avoid duplicates.
- Software versions: native files often cannot be opened by older versions.
Native or IFC exchange
Teams using the same tool often exchange native files, which keeps full fidelity. Mixed teams exchange IFC. Even on single-vendor projects, IFC is useful for checking, archiving and handover, because it is open and readable in the long term.
Common mistakes
- Choosing software by what a team knows rather than what the deliverables need.
- Upgrading software versions mid-project without agreement, so others cannot open files.
- Relying on default exports with no mapping.
Where to read more
The project's BEP lists the software, versions and exchange formats for each task team. buildingSMART lists software certified for IFC export and import.