On this website I offer a number of customised add-ins for Revit, but you might be looking for some very specific needs for your company, after all: every company is unique and has its own way of using Revit. Companies using Revit in their primary process aren’t generally specialized in developing software, so it can be quite a challenge hiring a software developer and letting him do things you do not understand. But, when do you need an add-in? How does the development process of an add-in look like? And what are the benefits? On this page I will try to convince you to consider hiring a software developer (preferably me!), to develop your own Revit add-ins.
Application Programming Interface
First, how does an add-in work? Autodesk provides Revit with an Application Programming Interface (API), which means that Autodesk opens up specific parts of Revit to allow access to software developers. By executing queries on your Revit model elements like doors, windows and views can be retrieved. Once these elements are fetched, various operations can be performed and saved to the model.
What is possible?
Typical add-ins will focus on data consistency and data retrieval. These two tasks are very easy for a computer program to perform and very hard for a human to perform consistently, fast and frequently. The overall quality of the model can be taken to a higher level and you can be confident the quality of the data within the model is high. Some of this functionality can he handled by the schedules within Revit itself, if possible, you should use them. When you require more complex calculations or validations on the data, the use of an add-in is unavoidable. Many repeating tasks can also be automated by an add-in. This can save the designers a lot of time.
Real life example
For example: the idea for the ‘Angle Validation’ add-in started when in the final stages of a relatively large project in Revit a strange ‘snapping’ behaviour was noticed. Further investigation showed that some elements where positioned in a very small angle compared to the grid. Very small is less than 0.1 degree. The side effects of this deviation were that some of the sections where not displayed properly. This problem had to be resolved. As this is a large project it is not desirable to validate the alignment of every element by hand or even by add-in. It turned out that the walls were the root of the problem, doors and windows are hosted within the wall. If we align the walls properly, the doors and windows will be correctly aligned as well. This add-in solved the problem by identifying walls that were not in the same direction or perpendicular to the grid. After aligning the misaligned walls the sections where displaying the information correct, problem solved.
The first step is to determine the actual problem. In the next phase a prototype is made, typically this prototype has a very simple user interface to show that the right information can be retrieved from and written to the model using the Revit API. The customer will test the prototype and a design and quotation of the add-in are proposed. After the approval of the quotation the new add-in will be build and will be delivered with an installer. To get an idea how much time and money this will cost, the ‘Angle Validation’ add-in was built in less than a week and cost anywhere between € 1000 and € 1500. A brief overview of the steps involved in developing an add-in:
- Design and quotation
When you have your own add-in you can use it on all your projects and make it part of your own design process.
Before add-ins could be used, some tasks had to be done manually. This takes a lot of time and is very error-prone. Often these tasks are important when deadlines are close and time is running out. But with your own add-in you can run these tasks daily, whenever you want. Improving the overall quality of the model and detecting errors in an earlier stage.
If you are interested in your own add-in or have questions about the costs, please contact me (email@example.com).