Custom Revit integration
Appfront builds integrations with Autodesk Revit, the BIM software that many architects, structural engineers and MEP consultants model in. Elements, properties and quantities flow from the model into your estimating, planning or custom software, and data from your systems flows back into the model. This can be done as an add-in inside Revit itself, or via the cloud without Revit needing to be open.
What is a Revit integration?
Autodesk Revit is a widely used program for modelling buildings in BIM. A Revit model contains more than geometry: elements such as walls, doors and pipes have properties, and quantities can be extracted from the model. Revit has an API that allows add-ins to work inside the program itself, and models can also be processed in the cloud via Autodesk Platform Services.
In practice, data from a Revit model is exported to Excel, edited by hand and entered into the estimate. A change in the model means exporting again. Codes from your own system, such as an article number or a budget item, are entered manually as a parameter. And whether the model complies with the agreements on parameters only becomes clear when something goes wrong.
We build custom because firms and companies differ: which data you need from the model, which data has to go back, which software it ends up in, and how your models are set up. For exchange with other BIM software there is the open IFC format; a Revit integration is for those who work directly with Revit models, in both directions.
From the model
Elements, properties and quantities from Revit in your estimating, planning or custom software.
Back into the model
Codes and properties from your systems as parameters in the model, without manual work.
Add-in or cloud
A button in Revit itself, or processing in the cloud without Revit needing to be open.
How we build your Revit integration
We start with your models: how they are set up, which data is needed, which software it has to end up in, and what needs to go back. It often turns out that parameters are used differently in different models. We document those agreements, so the integration works reliably and any deviation in a model is spotted immediately.
Your models, parameters, data and the software they need to go to.
An add-in in Revit or processing in the cloud.
Data from the model and back, with checks against the agreements.
Go-live, monitoring, and maintenance for new Revit versions.
What a Revit integration does in practice
The components below appear in almost every Revit integration. Which ones you need depends on your models.
Retrieval
Elements and parameters from the model.
Quantities
Quantities, lengths and areas.
Write-back
Codes and properties in the model.
Families
Products from your own catalogue.
Validation
Parameter agreements checked.
Changes
Differences between versions of a model.
Who we build a Revit integration for
The integration is intended for anyone who works with Revit models.
Architects
Models for many parties. Checking is the core.
MEP consultancy
Pipes and ducts. Quantities matter most.
Contractors
Estimating from the model. Changes are what you need.
Manufacturers
Products as families. The catalogue is the core.
Technology and integrations
This page is about Revit integrations. For the open exchange format, see our page on an IFC integration; for BIM in general, our page on BIM software; and for estimating, our page on estimating software. You can read about our approach at building custom software.
If your drafters work in BricsCAD rather than Revit and you want to use data from the drawing without retyping it, read more about our Bricsys BricsCAD integration.
If you work with Archicad rather than Revit, take a look at our Archicad integration.
Why Appfront for your Revit integration?
An Excel export is out of date as soon as the model changes. That's what we build on: data from the model without exporting, properties written back without manual work, and agreements that are checked.
Always up to date
Data from the latest model.
No manual work
Codes appear in the model automatically.
Reliable
Deviations stand out immediately.
Security and privacy in a Revit integration
The integration works with clients' designs and project data. Access to models follows the permissions in your own environment or in the Autodesk cloud, and every exchange is logged.
Where the integration runs outside Revit, it does so in a European data centre or in your own environment, with encrypted storage and daily backups.
Frequently asked questions about a Revit integration
Questions that firms and companies ask before they get started.
It pulls elements, properties and quantities from a Revit model into your own software, writes codes and properties back into the model, and checks whether the model meets your agreements. It can run as an add-in in Revit or via the cloud.
IFC is an open format that many BIM programs can export. An IFC integration works with that export. A Revit integration works directly with the Revit model, can also write data back, and has access to everything in Revit. If you work with several programs, you often need both.
With an add-in it does: the user works in Revit and clicks a button. Via Autodesk Platform Services, models can also be processed in the cloud without Revit being open. Which route suits you depends on who uses the integration and when.
Yes. Codes, article numbers or properties from your systems can be added to the model as parameters. That way they live in the model and others can use them.
Autodesk regularly releases a new version of Revit. An add-in has to be tested against it and sometimes adjusted. We include that in maintenance, so the integration keeps working when you upgrade.
Yes. Products from your catalogue can be offered as Revit families, with the properties from your own system. If a product changes, the family is updated.
For firms and companies that frequently need data from Revit models, for manufacturers with products in Revit, and for software vendors who want to connect their product directly to Revit.
Data from Revit without exporting?
Tell us which data you need from your models, where it needs to go and what should be written back into the model. We'll show you what the integration looks like.