IFC, COBie and ISO 19650: BIM Deliverables Explained

IFC, COBie, and ISO 19650 come up in almost every BIM deliverables conversation, but the three terms get mixed together more often than they should. IFC is a file format. COBie is a data schema built for facility handover. ISO 19650 is a management standard, not a file format at all. Understanding what each one actually does, and doesn’t do, makes it much easier to specify what you actually need from a Scan-to-BIM deliverable.

What Is IFC, and Why It Matters for BIM Delivery

IFC (Industry Foundation Classes) is an open, vendor-neutral file format designed so BIM models can move between different software platforms such as Revit, Archicad, Allplan and Vectorworks, without everyone needing to use the same tool. It is maintained by buildingSMART International and is the closest thing the industry has to a universal BIM exchange format.

That interoperability is genuinely useful for specific tasks: clash detection between disciplines, model review in a lightweight viewer, or handing off geometry and data to a platform that doesn’t need to edit it. IFC is an exchange format, and it does that job well.

IFC vs. Native Files: What You Can and Cannot Do

Where IFC runs into trouble is when it’s treated as a modeling format instead of an exchange format. A common but costly assumption is that a model can simply be exported to IFC, imported into a different BIM platform, and edited there as if it had been modeled natively.

The practical takeaway: IFC is well suited for interoperability tasks like coordination and clash detection. If your team needs to keep editing the model, whether for renovation planning, ongoing design changes or permit revisions, a native file (Revit, Archicad, Allplan, or Vectorworks) is what actually stays editable. IFC should be requested alongside the native file, not instead of it. Our Point Cloud to Revit workflow guide walks through what a native, LOD-defined deliverable looks like in practice.

COBie: Structured Data for Facility Handover

COBie (Construction Operations Building Information Exchange) is a different kind of format entirely. It is not primarily about geometry. COBie packages the non-graphical asset data a facility management team actually needs to operate a building: equipment lists, spaces, manufacturer and model information, and other attributes, structured so they can be imported directly into a CMMS or CAFM platform.

A geometry-only model, even a well-modeled native file, doesn’t automatically give a facility team anything they can query. Without a structured export like COBie, that same asset data usually has to be re-entered manually into the FM system, which defeats much of the purpose of having a digital model in the first place. COBie matters specifically at the handover point from construction and documentation to operations.

ISO 19650: A Management Standard, Not a File Format

ISO 19650 is an international standard for managing information over the lifecycle of a built asset using BIM. It is easy to confuse with a file format because it is so often mentioned alongside IFC and COBie, but ISO 19650 doesn’t specify any particular software or exchange format at all. Instead, it standardizes things like:

• Common Data Environment (CDE) workflows: how information moves between “Work in Progress,” “Shared,” “Published,” and “Archived” states
• Information requirements: defining what information is needed, by whom, and at what stage of a project
• Naming conventions and metadata: consistent structure so files and data can be found and trusted across a project team

In practice, ISO 19650 compliance is a project-level and organizational commitment. It involves a formal accreditation process, not something a single deliverable can claim on its own. What a Scan-to-BIM provider can do is deliver in a way that’s compatible with an ISO 19650 workflow: consistent naming, a documented QC process, and both native and IFC formats available for whichever CDE or coordination platform the project uses.

What VMTS Delivers as Standard

Every VMTS Scan-to-BIM project is modeled natively first, in Revit, Archicad, Allplan, or Vectorworks, so the deliverable stays fully editable for whoever needs to keep working on it. From there:

• Native BIM file at the agreed LOD, the primary editable deliverable
• IFC export on request, for coordination, clash detection, or handoff to platforms that don’t need to edit the model
• COBie export on request, for projects handing structured asset data to a CMMS/CAFM system
• A documented QC report checking the model against the source point cloud

IFC and COBie exports are typically add-ons on top of the native file rather than a separate cost driver on their own. For a full breakdown of what actually determines the price of a Scan-to-BIM project, see our Scan-to-BIM Cost Guide 2026.

These native-first deliverables are also central to evaluating an overseas partner in the first place. See why European firms outsource Scan-to-BIM to Vietnam for how quality, data security and communication safeguards fit around a deliverable like this.

“You scan. We support all downstream services, from point clouds to native BIM models, plus whatever exchange format your workflow needs on top.”

Frequently Asked Questions