Hi There,
I was wondering if there is a way to analyze all of the loadable families in a project.
Ideally we are looking for -
In this case it is a file from a consultant, so we do not have I was thinking I would need to it using Snapshot, as we will not have the history of the families being loaded in to the project.
Hi Alex,
First off, welcome to the forum!
I will go through each item:
Family Size: This field is currently captured in the revit-event index when a family is loaded. Revit snapshot currently does not record the size of families in the file, but we can and should! We will add a field for family size into revit-snapshot in a future release.
Number of nested families: Similar to family size, this value is collected as family.nested.count in the revit-event index, but only when the family loaded. We can potentially add a feature to Revit Snapshot to go into each family to get this value. Can you elaborate on the use case for this field?
Purgeable Elements: This field is called project.purge.count. You can find it in the revit-event index. This field is collected Open, Synch, and Save events
What type of information are you looking to see for consultants’ models? Maybe there is an out-of-the-box dashboard relating to model health that can give you an overview of consultant models. You could potentially filter by file path to filter out in-house models.
The issue with the consultant models, is we only receive them, then we have to audit them. there is no history with the files of users opening, editing and loading in families. While the revit-event action.name:open is very good for overall project overwatch, there is no way of auditing the families, which can have a huge impact on model health.
Thanks, Alex, this is really helpful context.
We’ll work on adding a field to capture the size of individual families directly within the Revit Snapshot tool. That should make it easier to audit consultant models, especially since Snapshot allows you to include linked files when running the analysis.
As for the number of nested families, that one’s a bit trickier. We’d need Snapshot to open each family individually, which could significantly increase processing time. That said, we’ll explore what’s possible and see if there’s a feasible way to include it in a future release.
We appreciate the feedback! This is exactly the kind of input that helps us prioritize what to build next.