Requests
Request a BIM tool
The tools here exist because the job they do is one people actually repeat. If yours is missing, describing it is the fastest way to get it built.
The most useful request is not a feature name. It is the job you keep doing by hand: what you do today, how often, and what the result has to look like when you are finished. That tells us whether a tool can genuinely replace the work or would only replace part of it.
A request that says "IFC to Excel but keeping the storey grouping, because I rebuild that pivot every Monday" is worth ten that say "better exports".
This opens an email with a short template already filled in. There is no form here on purpose: a form would mean storing your details, and this site has no database and no accounts.
Categories
- IFC
- Reading, converting or checking IFC data.
- Revit
- Anything needing Revit itself, which becomes an add-in.
- BCF
- Issue exchange between coordination tools.
- IDS
- Information Delivery Specification, authoring or validating.
- COBie
- Handover and asset data deliverables.
- ACC
- Autodesk Construction Cloud workflows.
- Solibri
- Rulesets, results and reporting.
- Power BI
- Getting model data into dashboards.
- Something else
- If it does not fit above, it is still worth sending.
What happens to a request
It gets read. If several people describe the same job, it moves up. If it needs Revit itself, it goes on the Revit add-in list rather than being forced into the browser, because a browser cannot open an .rvt honestly.
Requests are not a queue with a promised date. The tools page shows what is planned, and anything listed as coming soon is a real intention rather than a placeholder.