Tools encyclopedia · choose stack from purpose
BIM software
BIM software should follow information requirements: authoring, cloud registration, coordination, scheduling, and estimating tools only earn their seat if they serve a defined exchange. Revit-centric stacks dominate buildings; infrastructure and industrial plants differ.
Layers of a practical stack
- Reality capture & registration
- BIM authoring
- Federation & clash
- 4D / 5D specialised tools
- CDE / document control
Buying tip
Budget training and standards time equal to licenses. Empty seats with no BEP produce empty models.
Authoring vs coordination vs CDE
Pick tools by information exchange, not brand loyalty. Authoring (Revit/Tekla) creates objects; coordination (Navisworks/Solibri) federates and checks; the CDE governs status. Scan-to-BIM adds registration/ReCap-class tools upstream. Buying licenses without a BEP produces empty seats.
Cost reality for studios
Software cost is rarely the binding constraint versus trained modellers and QA time. Ask vendors which versions they freeze per project so your federations do not break mid-flight.
Open formats and longevity
IFC and careful native-file discipline matter for owners who outlive a single contractor. For Scan-to-BIM renovations, native Revit plus documented coordinates usually dominates short-term delivery; plan exports deliberately.
Buyer decision guide
BIM software should be selected from the required exchange, authoring and review workflow. Revit, Civil 3D, Tekla, Archicad and specialist tools solve different problems; an IFC viewer is not an authoring tool, and a point-cloud registration package is not a model QA system.
Inputs to request before a quote
- The client’s native-format and version requirements
- Required disciplines, object types and drawing outputs
- Point-cloud size, coordinate system and segmentation strategy
- Exchange partners, IFC requirements and long-term archive needs
Acceptance framework
Put acceptance criteria into the scope before production. The following checks are a practical starting point and should be adjusted to the project’s risks and intended model use.
| Control | What “good” means | How to verify it |
|---|---|---|
| Authoring | Create and maintain discipline geometry and information | Native model opens without missing references |
| Reality capture | Register, clean, classify or view source observations | Control and registration report reviewed |
| Coordination | Federate models, run rules and manage viewpoints/issues | Repeatable test set and issue export |
| Exchange | Preserve agreed geometry, properties and classification | Round-trip sample in the receiving application |
Limitations and common procurement errors
A tool badge does not prove workflow competence. Version incompatibility, coordinate shifts, unsupported objects and lost parameters are more expensive than the license price. Web viewers improve access but may simplify geometry or omit native relationships, so they should not become the sole contractual record without testing.
What the handover should contain
Record software name and exact release, plug-ins, linked-file paths, coordinate basis, export settings and required viewers. For long-lived assets, keep an open exchange deliverable where practical, but verify it against the use case rather than assuming every IFC export is equivalent.
Primary reference: buildingSMART IFC overview. This studio guide explains procurement and QA application; it does not reproduce or replace a standard, contract or software manual.
Frequently asked questions
What is the best BIM software?
There is no universal best. For building Scan-to-BIM, Revit + ReCap-class workflows are the common core; coordination often adds Navisworks or Solibri.
Need this delivered — not just explained?
Scan to BIM Studios is both an encyclopedia and a delivery studio. If you came here to understand BIM software and now need a model, a pilot, or a scoped quote, talk to the same people who write for depth.