A BIM delivery is not one file. It is a Revit model, its linked models, IFC exports, exported sheets, schedules, clash reports and a stream of revisions across all of them — produced by several people, often across several organisations. Keeping that set coherent, and being able to say precisely which version of which container is current, is one of the least glamorous and most important parts of digital engineering. FileMuster is a lightweight tool our team built to make that manageable.
FileMuster
Every file, accounted for — a lightweight file registry, version tracker and drawing-identity platform for engineering teams.
Visit FileMusterWhere BIM Files Drift Apart
Model files multiply quietly over a project:
- A central model is detached for an issue, and now a detached copy lives alongside the live one.
- An IFC export is generated for a coordination round, then regenerated — and it is no longer obvious which export matches which model revision.
- A subconsultant returns an updated model with a slightly different file name, and it is not clear whether it supersedes the last one.
- Sheets are exported to PDF for issue, but the export and the model that produced it are no longer linked in any recorded way.
Each is minor. Collectively, they are why "is this the current model?" is such a common question on a live BIM project.
What FileMuster Is
FileMuster combines three roles in one lightweight application:
- A file registry — one place that knows every model, export and drawing that matters, instead of relying on folder structure alone.
- A version tracker — it records the history of each file, so supersession is explicit rather than inferred from timestamps.
- A drawing- and model-identity platform — every file carries a persistent identity, so a container stays recognisable even when renamed, detached or re-exported.
It does not replace your CDE, your Revit environment or your ISO 19650 procedures. It gives you a dependable answer to one question: what is the current, correct version of this information container, and how did it get here?
On a federated model, a coordination issue was traced back to an IFC export that had been regenerated but never re-linked to its source model revision. Giving each export a tracked identity tied to its source meant the mismatch was visible immediately, instead of being discovered in a clash meeting.
Supporting an ISO 19650 Mindset
The information-management principles behind ISO 19650 come down to discipline about information containers: each has an identity, a revision, a status and a clear owner. FileMuster reinforces that discipline at the file level:
- Identity — every container is registered and recognisable, not just a file in a folder.
- Revision — version history is recorded, so the current revision is unambiguous.
- Status and supersession — superseded models and exports are marked, so they are not reused by mistake.
- Audit trail — who changed what, and when, is captured for the record.
If a coordination or delivery problem could be caused by someone working from a superseded model, the model set needs a registry — not just a folder convention. A lightweight tracker usually pays for itself the first time it prevents a rework loop.
FileMuster and Custom BIM Automation
A registry is only as reliable as the data feeding it, and this is where FileMuster and custom Revit automation complement each other. A small Revit API or Dynamo routine can extract model metadata, revision parameters and sheet information directly from your models, so the registry reflects what is genuinely inside the models rather than what someone typed into a tracker. If you are already extracting model data for dashboards or reporting, feeding a file registry from the same pipeline closes the loop between producing BIM information and controlling it.
If you would like help wiring your Revit models to a registry — or building the data extraction that keeps it accurate — that is exactly the kind of work we do.
Keep your model set under control.
See FileMuster, or talk to us about automating your model register.
