📄Data Model - BIM document
In this video, we dive into the BIM Document table, a core part of the VIM data model. This table stores important metadata from Revit, Navisworks, or IFC files—like filenames, units, geographic info, save history, and more. Whether you're tracking model origins or auditing authoring habits, this table provides powerful insights.
⏱️ Chapters
00:01 Intro – What is the BIM Document table?
00:13 Where it connects in the data model
00:29 BIM Docs, VIMs, and Units
00:39 File names and linking status
00:59 File relationship status (linked or parent)
01:20 Counting BIM documents with keys
01:50 File name breakdown across VIMs
02:25 Active view column (pending fix)
02:41 Three file folders: Project Info, Location, and File
03:01 What each group of metadata means
03:12 File info (linked, metric, attached, workshared, etc.)
03:51 Save count – measure file activity or neglect
04:17 File paths and source product
04:38 Product version + user info
04:50 Friendly versions of source + unit info
05:14 Location data – Revit's site/geography settings
05:42 Project info tab – often inconsistent or empty
06:25 What to do if your BIM Execution Plan requires this info
06:56 VIM key and how it connects
07:08 Wrap-up – linking BIM Document to the rest of your data
📚 What You’ll Learn
✅ What metadata is stored in the BIM Document table
✅ How to distinguish parent vs. linked models
✅ Why file save count is a hidden gem for tracking team activity
✅ How the table connects to VIMs and your overall BIM data strategy
💡 Tip: If your team actually fills out Project Info in Revit, this table becomes incredibly valuable for QA/QC and BEP compliance. Otherwise, expect a bit of a mess—Power BI will still help you expose it.
🔗 Visit https://docs.vimaec.com for the full data model reference
📥 Like • 🔔 Subscribe • 💬 Questions in the comments!