Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →ThatPainter is reader-supported. When you buy through links on our site, we may earn an affiliate commission. Learn More
dRofus is a planning and data-management environment used alongside BIM authoring software. Its job is to capture room requirements, equipment information and other project data in a structured database, then associate that information with elements in a building model. In the interview published by Architecture & Design on 2 October 2019, Adam Hetherington of BVN described the distinction by comparing dRofus with Revit: Revit represents the three-dimensional model, while dRofus holds a virtual information model connected to it.
As an Amazon Associate I earn from qualifying purchases.
That division matters when a project team must define rooms and equipment before every room has been modeled, keep requirements consistent as the design changes, and check whether the finished model reflects the brief. dRofus is not presented as a replacement for a BIM authoring tool. It is a structured planning and information layer that can work before, during and after modeling.
Recommended Free Tools
What dRofus is
dRofus is described in the 2019 interview as a planning, data-management and BIM-collaboration tool supporting building information across a project lifecycle. The central idea is to separate two kinds of work that are often mixed together:
#1 Best Overall
- Model authoring: creating and editing the geometric building model in software such as Revit.
- Information planning: recording requirements, room functions, equipment and associated documentation in a structured data environment.
A wall, door or piece of equipment can exist as a modeled object, but the project also needs information about why it is there, what it must do, which specification applies, and whether the required quantity has been provided. dRofus is intended to hold that wider brief and connect it to the objects that appear in the model.
That makes dRofus particularly relevant to projects where room-by-room requirements are extensive. Healthcare, transport, civic and other technically complex buildings may have thousands of spaces, each with its own functional, equipment and documentation requirements. Entering all of that information only after geometry is complete can make omissions difficult to find. A database-first workflow allows the team to define the brief while design options are still being developed.
How the dRofus workflow works
1. Define rooms and requirements before modeling is complete
Hetherington’s example starts with requirements rather than geometry. A team can define room functions, data fields and project requirements before every room has been placed in the authoring model. The database can therefore represent the intended building while the design is still being arranged.
This is useful when the client knows that a project needs, for example, consultation rooms, clean stores, staff areas or specialist treatment spaces, but the exact location and shape of those rooms are still changing. The requirement can be captured once and carried forward as the design develops.
2. Use templates to make repeated rooms consistent
Once the number of rooms is known, templates can populate the relevant data. A template might define the fields and expected contents for a room type, including functional requirements, equipment categories or other project-specific information. Repeated rooms can then start from the same baseline instead of being recreated manually with slightly different names and fields.
Templates do not remove the need for project decisions. They provide a controlled starting point; the team still has to decide which room types exist, which requirements are mandatory and which variations are legitimate.
3. Link information to modeled elements
As rooms and components are modeled, their records can be associated with the corresponding objects. The interview describes detailed item records that can include specifications, images and certificates. A model element can therefore be checked against a richer record than the geometric object alone normally contains.
Free tools Windows power users keep installed
One-click scans. No signup required.
The link is valuable only when identifiers, room names and object classifications are maintained consistently. If one team calls a space “Exam 01” and another calls it “Consultation Room 1,” matching and reporting become less reliable. Data governance is part of the technical workflow, not an administrative afterthought.
4. Compare the brief with the model
With requirements and modeled objects connected, the team can check what was requested against what appears in the model. Hetherington gave examples such as finding excess tables or power outlets. The same principle applies to missing items, incorrect room types or quantities that changed during design.
A discrepancy report does not by itself prove which side is correct. It identifies a difference for the project team to resolve: the brief may have changed, the model may be incomplete, or an item may have been intentionally removed and needs an approved variation.
Rank #3
dRofus, Revit and other authoring tools
The interview uses Revit to explain the division of responsibilities. Revit is the three-dimensional architectural model in that comparison; dRofus is the associated information model and planning database. The two can support one workflow without being the same type of application.
| Workflow question | dRofus | Revit in the interview’s comparison |
|---|---|---|
| Primary role | Planning, data management and BIM collaboration | Three-dimensional architectural model authoring |
| When it is useful | Before and during modeling, when requirements and room data are being defined and checked | When building geometry and modeled elements are created or edited |
| Typical information | Room functions, requirements, templates, equipment records, specifications, images and certificates | Modeled building elements and their model data |
| Relationship | Provides a structured information layer associated with model elements | Provides the geometric model that can be linked to planned information |
The current dRofus BIM Manager page, accessed 13 October 2026, lists integrations with Revit and ARCHICAD, along with model-data viewing, customizable reporting, and controls for user access and data responsibilities. Those are vendor-described capabilities; the page does not independently establish project outcomes or performance benchmarks.
In practical terms, an authoring tool remains necessary for designing and documenting geometry. dRofus adds a place to manage the brief and the detailed data that may exist before, beside or beyond that geometry.
Managing room data in detail
Room functions and requirements
A room record can express what a space is intended to do, not merely where its walls are. Functional information can be captured while the room schedule is still being developed. Requirements can then be reviewed at the room level and compared with the room represented in the model.
Equipment and item records
Equipment records can carry the detail needed for procurement, coordination or handover. The interview specifically mentions specifications, images and certificates attached to item information. Linking those records to modeled elements gives the team a way to inspect both the object and its supporting documentation.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Quantities and discrepancy checks
Structured data makes counting and comparison possible. A team can ask whether every room that requires a particular item has one, whether the model contains more items than the brief allows, or whether a change affected several repeated rooms. The examples of excess tables and power outlets illustrate a broader quality-control process: compare the planned requirement with the modeled provision, investigate differences, and record the decision.
Reporting
The vendor’s current BIM Manager description includes customizable reporting. Reports are most useful when their fields, definitions and ownership are agreed in advance. A report that mixes room names, equipment categories or status values from different conventions can create the appearance of precision without reliable comparisons.
Why governance is as important as customization
dRofus can be customized to suit a project, but Hetherington also warned that a highly customizable database can become inconsistent between teams. Different naming conventions, duplicated fields or competing room templates make information harder to search, compare and maintain.
A workable governance plan should establish:
- One naming standard: define room, equipment and status names before large-scale data entry.
- Field ownership: identify who creates, approves and changes each class of information.
- Template control: publish a controlled set of room and equipment templates, with a process for revisions.
- Identifier rules: maintain stable IDs so records can continue to match model elements after design changes.
- Access responsibilities: decide which users may edit requirements, approve changes or only view reports.
- Change records: retain the reason and approval for significant requirement or quantity changes.
These controls do not make the database inflexible. They make project-specific flexibility usable by ensuring that a custom field or template has a clear meaning and owner.
A practical implementation sequence
- Set the information brief. List the room types, equipment categories, documents and checks the project must manage. Separate mandatory information from optional detail.
- Design the data structure. Agree field names, value formats, room and equipment classifications, status values and identifiers before importing or entering a large dataset.
- Create approved templates. Build room and equipment templates for repeatable requirements. Record who owns each template and how revisions are approved.
- Load the early brief. Enter known rooms, functions and requirements even when the model is incomplete. This creates a baseline for later comparison.
- Connect the model. Associate database records with the corresponding model elements as rooms and equipment are placed. Resolve duplicate names or missing identifiers immediately.
- Run staged checks. Compare required and modeled quantities, review room-specific requirements, and investigate exceptions such as extra or missing items.
- Publish controlled reports. Give each audience a report suited to its responsibility, such as room compliance, equipment documentation or unresolved discrepancies.
- Maintain the information. Treat approved changes to the brief, templates and model as coordinated updates. Archive superseded values where the project’s records require an audit trail.
The exact screens and exchange settings depend on the project configuration and connected authoring tool. The important sequence is stable: define, structure, link, check and govern.
Best Value
Historical claims about adoption and mandates
The Architecture & Design interview says dRofus was mandated on some New South Wales health projects above a stated value threshold. It also refers to use in complex health, rail, stadium, airport and fish-market projects. These statements describe what Hetherington said in 2019. They should not be treated as a current NSW policy, a complete project inventory or proof that every project in those sectors uses dRofus without fresh confirmation.
Biographical material from BVN and dRofus places Hetherington at BVN in the 2019 context. His current role is not established by those sources. Likewise, no named independent statistic was identified that would justify quoting a current user count or market-share figure.
What the current vendor description establishes
As of the dRofus BIM Manager page accessed 13 October 2026, the vendor describes integrations with Revit and ARCHICAD, model-data viewing, customizable reports, and tools for managing user access and data responsibilities. This supports the conclusion that dRofus is positioned as a connected planning and information-management system rather than a standalone geometry editor.
Vendor documentation is appropriate for describing listed features, but it is not independent evidence that a project will achieve a particular saving, accuracy level or coordination result. Those outcomes depend on the project’s data standards, implementation quality, user participation and model discipline.
Where dRofus fits—and where it does not
Good fit
- Projects with many room types, repeated spaces or detailed equipment requirements.
- Teams that need to define and review a brief before the model is fully developed.
- Workflows requiring room-by-room checks against modeled quantities.
- Organizations willing to assign data owners and maintain shared naming standards.
Potential mismatch
- Small projects whose information needs are limited to basic geometry and a short room schedule.
- Teams seeking a tool that replaces architectural model authoring.
- Organizations that want unrestricted customization but have no process for approving fields, templates or naming conventions.
- Projects unable to maintain stable identifiers between the database and the model.
The decision should be based on information complexity, not on the label “BIM” alone. A project with modest geometry but demanding room and equipment data may benefit more than a visually complex project with few structured requirements.
Questions to ask before adoption
- Which requirements must be known before room geometry is fixed?
- Which room and equipment fields are mandatory for design, procurement, approval and handover?
- Who owns each data category, and who can approve a change?
- How will records remain linked when rooms are renumbered, split or combined?
- Which discrepancy reports will trigger a design decision rather than simply flagging a difference?
- How will the team prevent parallel templates or inconsistent naming across disciplines?
- Which integrations are required for the project’s chosen authoring tools, and what data exchange responsibilities will each team accept?
The central lesson from Hetherington’s interview
Hetherington summarized his view in the vendor article reproducing the interview: “I often said that if you control the data then you control the building. It is the future.” In context, the point is about structured project information, not a claim that software alone controls design quality. dRofus can make requirements visible, reusable and checkable, but the value comes from the combination of a clear brief, disciplined data governance and a reliable connection to the model.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
