Emiliano Capasso

Years have passed since the first Revit Family have been made in our office, as of now we are handling around 500 families per year (for a total of 2277 requests and counting) and around 50% of those are Furniture. Autodesk never thought of building a content management for family libraries, but the software developers di and of course now there are tons of content management systems in the market, but all of them for us have a huge flaw, they are on THEIR cloud. Family Library is a core and key asset of our firm, it’s the basis of all our projects and we can’t afford on placing our asset on someone else cloud. So we created our internal system to help our user in navigating all of our families and comparing and selecting them with IFC.js, Electron and Node.js Key Message & Learning Outcomes: - Creating a Webapp in IFC.js mimicking a “Revit Showroom” (Revit file as a container a set of family) faster and platform-agnostic - Creating a Revit Addin in Electron of the Webapp and using Pipe Servers to send commands to Revit from outside the environment - Develop and design only one time the web application in Node.js, Typescript and IFC.js (so no more WPF and XAML) - optimisation and enhancing the user experience of the design team (Architects and Interior Designer) - Security by Design, our families are no longer exposed in the server, but loaded at request