Revit Tip: Revit Model Preparation for Owner-Ready COBie Export

Today’s tip: prepare your Revit model for a clean, owner-ready COBie export with fewer surprises and less rework.

Core setup

• Install Autodesk’s BIM Interoperability Tools (includes COBie Extension, Model Checker, Classification Manager). If you need Revit licensing or guidance, contact NOVEDGE for Autodesk Revit.
• Confirm Project Information is complete and correct (Project Name, Site, Address, Client, Phase) — this feeds COBie.Facility.
• Use Levels deliberately; Level names become COBie.Floor entries. Standardize naming (e.g., L01 – Ground, L02 – Typical).
• Model enclosed Rooms/Spaces and create Zones for departments/tenancy. Spaces are preferred for MEP-centric COBie handovers.
• Define a company-wide Asset ID policy. Use a consistent, unique instance parameter (e.g., Asset_ID) for maintainable assets.
• Lock down Type vs Instance strategy: Type Name carries COBie.Type; instance identifiers carry COBie.Component.

Parameter mapping that works

• Facility: Project Information fields map directly; add Owner, Project Number, and Site Contact.
• Floor: Level Name → Floor.Name; Elevation → Floor.Height (if required by owner).
• Space: Space Number → Space.Name (unique); Space Name → Space.Description; Level → Space.FloorName; Department → Space.Category/Zone.
• Type: Family Type Name → Type.Name; Manufacturer, Model, Warranty Description, ExpectedLife, ReplacementCost as shared parameters on Type.
• Component: Asset_ID (preferred) or Mark → Component.Name (unique); SerialNumber, InstallationDate, WarrantyStartDate/EndDate on instance.
• System: Use native Revit MEP Systems; System Name and Category will populate COBie.System.
• Classification: Apply Uniclass/OmniClass using Classification Manager so Type.Category and Component.Category are standardized.
• Documents: Track O&M, cutsheets, and photos via URL/File parameters; the COBie Extension can bundle these into Document and Attribute tabs.
• Contacts: Maintain a clean Contact register (Designer, Constructor, Maintainer). The COBie Extension’s Contacts tool helps.

Model hygiene to prevent COBie pain

• Eliminate duplicate type names; keep Type Names stable and human-readable.
• Audit warnings; fix room/space not enclosed, duplicate Marks, and unconnected systems.
• Purge unused types carefully; obsolete types create noisy COBie.Type rows.
• Normalize units and date formats (ISO 8601 for dates is safest).

Export and QA workflow

• Run the COBie Extension “Setup” to bind your shared parameters to the correct COBie fields.
• Generate the COBie spreadsheet and review key tabs first: Facility, Floor, Space, Type, Component, System.
• Use Model Checker with a COBie ruleset to catch missing required fields (e.g., empty Asset_IDs, orphaned components).
• Iterate: correct data in Revit, re-export, and re-check until pass rates meet your QA standard.

Owner requirements first

• Clarify the owner’s Data Drop scope early (which categories are “maintainable,” which attributes are required).
• Agree on classification system, room numbering standard, and naming policy.
• Confirm whether Spares, Resources, Jobs, and warranty documents are in or out of scope.

Speed it up

• Use Dynamo to copy values at scale (e.g., push Room Number into Space Number; push Type parameters down to instances).
• Create COBie-ready View/Schedule sets for ongoing QA during the project, not just at handover.

Need help selecting the right Revit version or add-ins to streamline COBie? Talk to NOVEDGE for licensing, implementation advice, and training.