Core concepts
High-level overview of the core concepts to understand when using Night Runner.
Last updated
High-level overview of the core concepts to understand when using Night Runner.
Last updated
In a typical Revit Project, designers work on their section of the model and occasionally these changes are federated into a Federated Model. This makes it very difficult to manage the consistency and quality of families, types, parameters, materials and more, between different Project Files.
Designers can sync whatever and whenever they like into the Type File. This can include geometric changes (i.e. the user has modelled a new door in a wall) or can be non-geometric changes to the data within the model (i.e. the user changed the Door Finish from Natural to Painted).
However, this freedom comes at a cost. Even on small projects it becomes very difficult to track which families, types and parameters have been edited, and by who. And on larger projects, it becomes almost impossible.
Night Runner provides a solution to these problems.
Night Runner provides greater control over the process of syncing new data into the Type File, and it allows owners of a sub-section of the model to understand which families, types, parameters (and more) are not consistent with those in the Type File.
In Night Runner, designers can Push, Pull, and Compare (explained below).
This section provided a brief overview of the core concepts of Night Runner. In the next sections, we'll explain in more detail some of this core functionality, starting with the Push & Pull.