{"id":38905,"date":"2026-09-09T11:24:40","date_gmt":"2026-09-09T04:24:40","guid":{"rendered":"https:\/\/vmts.ch\/?p=38905"},"modified":"2026-09-11T10:37:04","modified_gmt":"2026-09-11T03:37:04","slug":"ifc-cobie-iso19650-scan-to-bim-deliverables","status":"publish","type":"post","link":"https:\/\/vmts.ch\/en\/ifc-cobie-iso19650-scan-to-bim-deliverables\/","title":{"rendered":"IFC, COBie and ISO 19650: BIM Deliverables Explained"},"content":{"rendered":"\n<div style=\"background:#000000;padding:24px 28px;font-family:Arial,Helvetica,sans-serif;border-left:4px solid #C70100;margin:0 0 32px\">\n  <p style=\"font-size:10px;font-weight:700;letter-spacing:0.16em;text-transform:uppercase;color:#C70100;margin:0 0 14px\">TL;DR: 3 things to know<\/p>\n  <ul style=\"list-style:none;padding:0;margin:0\">\n    <li style=\"display:flex;gap:12px;padding:8px 0;border-bottom:0.5px solid #222222;align-items:flex-start\">\n      <span style=\"color:#C70100;font-weight:700;font-size:13px;flex-shrink:0;margin-top:1px;font-family:Arial,Helvetica,sans-serif\">01<\/span>\n      <p style=\"font-size:13px;color:#cccccc;line-height:1.55;margin:0;font-family:Arial,Helvetica,sans-serif\">IFC is an exchange format, not a modeling format. Imported IFC objects often behave as &#8220;dead objects&#8221; that cannot be edited the way native elements can.<\/p>\n    <\/li>\n    <li style=\"display:flex;gap:12px;padding:8px 0;border-bottom:0.5px solid #222222;align-items:flex-start\">\n      <span style=\"color:#C70100;font-weight:700;font-size:13px;flex-shrink:0;margin-top:1px;font-family:Arial,Helvetica,sans-serif\">02<\/span>\n      <p style=\"font-size:13px;color:#cccccc;line-height:1.55;margin:0;font-family:Arial,Helvetica,sans-serif\">COBie packages the non-graphical asset data a facility team actually needs, such as equipment, spaces and attributes, for handover into a CMMS\/CAFM system.<\/p>\n    <\/li>\n    <li style=\"display:flex;gap:12px;padding:8px 0;align-items:flex-start\">\n      <span style=\"color:#C70100;font-weight:700;font-size:13px;flex-shrink:0;margin-top:1px;font-family:Arial,Helvetica,sans-serif\">03<\/span>\n      <p style=\"font-size:13px;color:#cccccc;line-height:1.55;margin:0;font-family:Arial,Helvetica,sans-serif\">ISO 19650 does not mandate a specific software or format. It standardizes how BIM information is managed and exchanged across a project&#8217;s lifecycle.<\/p>\n    <\/li>\n  <\/ul>\n<\/div>\n\n\n\n<p class=\"wp-block-paragraph\" style=\"font-size:16px;line-height:1.7;color:#4A4A4A\">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&#8217;t do, makes it much easier to specify what you actually need from a Scan-to-BIM deliverable.<\/p>\n\n\n\n<figure class=\"wp-block-image size-large\"><img decoding=\"async\" width=\"1600\" height=\"900\" src=\"https:\/\/vmts.ch\/wp-content\/uploads\/2026\/09\/ifc-cobie-iso19650-bim-deliverables-v2.jpg\" data-orig-src=\"https:\/\/vmts.ch\/wp-content\/uploads\/2026\/09\/ifc-cobie-iso19650-bim-deliverables-v2.jpg\" alt=\"Three separate panels comparing IFC, COBie and ISO 19650: IFC as a file exchanged between software, COBie as asset data feeding a facility dashboard, ISO 19650 as an information management workflow\" class=\"lazyload wp-image-39213\" srcset=\"data:image\/svg+xml,%3Csvg%20xmlns%3D%27http%3A%2F%2Fwww.w3.org%2F2000%2Fsvg%27%20width%3D%271600%27%20height%3D%27900%27%20viewBox%3D%270%200%201600%20900%27%3E%3Crect%20width%3D%271600%27%20height%3D%27900%27%20fill-opacity%3D%220%22%2F%3E%3C%2Fsvg%3E\" data-srcset=\"https:\/\/vmts.ch\/wp-content\/uploads\/2026\/09\/ifc-cobie-iso19650-bim-deliverables-v2-200x113.jpg 200w, https:\/\/vmts.ch\/wp-content\/uploads\/2026\/09\/ifc-cobie-iso19650-bim-deliverables-v2-300x169.jpg 300w, https:\/\/vmts.ch\/wp-content\/uploads\/2026\/09\/ifc-cobie-iso19650-bim-deliverables-v2-400x225.jpg 400w, https:\/\/vmts.ch\/wp-content\/uploads\/2026\/09\/ifc-cobie-iso19650-bim-deliverables-v2-600x338.jpg 600w, https:\/\/vmts.ch\/wp-content\/uploads\/2026\/09\/ifc-cobie-iso19650-bim-deliverables-v2-768x432.jpg 768w, https:\/\/vmts.ch\/wp-content\/uploads\/2026\/09\/ifc-cobie-iso19650-bim-deliverables-v2-800x450.jpg 800w, https:\/\/vmts.ch\/wp-content\/uploads\/2026\/09\/ifc-cobie-iso19650-bim-deliverables-v2-1024x576.jpg 1024w, https:\/\/vmts.ch\/wp-content\/uploads\/2026\/09\/ifc-cobie-iso19650-bim-deliverables-v2-1200x675.jpg 1200w, https:\/\/vmts.ch\/wp-content\/uploads\/2026\/09\/ifc-cobie-iso19650-bim-deliverables-v2-1536x864.jpg 1536w, https:\/\/vmts.ch\/wp-content\/uploads\/2026\/09\/ifc-cobie-iso19650-bim-deliverables-v2.jpg 1600w\" data-sizes=\"auto\" data-orig-sizes=\"(max-width: 1600px) 100vw, 1600px\" \/><figcaption class=\"wp-element-caption\">IFC, COBie and ISO 19650 each do a different job in a BIM deliverable.<\/figcaption><\/figure>\n\n\n\n<figure class=\"wp-block-table\"><table><thead><tr><th><\/th><th>IFC<\/th><th>COBie<\/th><th>ISO 19650<\/th><\/tr><\/thead><tbody><tr><td><strong>What it is<\/strong><\/td><td>Open, vendor-neutral exchange file format (buildingSMART)<\/td><td>A data schema for non-graphical asset information<\/td><td>An international information-management standard<\/td><\/tr><tr><td><strong>What it is for<\/strong><\/td><td>Moving models between software; coordination and clash detection<\/td><td>Handing structured asset data to a CMMS\/CAFM system at FM handover<\/td><td>Defining how BIM information is produced, shared, and archived across a project<\/td><\/tr><tr><td><strong>What it is not<\/strong><\/td><td>Not a modeling format; imported objects often lose editability<\/td><td>Not a 3D model<\/td><td>Not a file format or software; not something a single deliverable can be certified for<\/td><\/tr><tr><td><strong>Delivered as<\/strong><\/td><td>An .ifc export alongside the native BIM file<\/td><td>A structured spreadsheet export, on request<\/td><td>Consistent naming, documented QC, and a CDE-compatible workflow<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<div id=\"ez-toc-container\" class=\"ez-toc-v2_0_87_1 counter-hierarchy ez-toc-counter ez-toc-grey ez-toc-container-direction\">\n<div class=\"ez-toc-title-container\">\n<p class=\"ez-toc-title ez-toc-toggle\" style=\"cursor:pointer\">Table of Contents<\/p>\n<span class=\"ez-toc-title-toggle\"><a href=\"#\" class=\"ez-toc-pull-right ez-toc-btn ez-toc-btn-xs ez-toc-btn-default ez-toc-toggle\" aria-label=\"Toggle Table of Content\"><span class=\"ez-toc-js-icon-con\"><span class=\"\"><span class=\"eztoc-hide\" style=\"display:none;\">Toggle<\/span><span class=\"ez-toc-icon-toggle-span\"><svg style=\"fill: #999;color:#999\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" class=\"list-377408\" width=\"20px\" height=\"20px\" viewBox=\"0 0 24 24\" fill=\"none\"><path d=\"M6 6H4v2h2V6zm14 0H8v2h12V6zM4 11h2v2H4v-2zm16 0H8v2h12v-2zM4 16h2v2H4v-2zm16 0H8v2h12v-2z\" fill=\"currentColor\"><\/path><\/svg><svg style=\"fill: #999;color:#999\" class=\"arrow-unsorted-368013\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" width=\"10px\" height=\"10px\" viewBox=\"0 0 24 24\" version=\"1.2\" baseProfile=\"tiny\"><path d=\"M18.2 9.3l-6.2-6.3-6.2 6.3c-.2.2-.3.4-.3.7s.1.5.3.7c.2.2.4.3.7.3h11c.3 0 .5-.1.7-.3.2-.2.3-.5.3-.7s-.1-.5-.3-.7zM5.8 14.7l6.2 6.3 6.2-6.3c.2-.2.3-.5.3-.7s-.1-.5-.3-.7c-.2-.2-.4-.3-.7-.3h-11c-.3 0-.5.1-.7.3-.2.2-.3.5-.3.7s.1.5.3.7z\"\/><\/svg><\/span><\/span><\/span><\/a><\/span><\/div>\n<nav><ul class='ez-toc-list ez-toc-list-level-1 eztoc-toggle-hide-by-default' ><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-1\" href=\"https:\/\/vmts.ch\/en\/ifc-cobie-iso19650-scan-to-bim-deliverables\/#What_Is_IFC_and_Why_It_Matters_for_BIM_Delivery\" >What Is IFC, and Why It Matters for BIM Delivery<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-2\" href=\"https:\/\/vmts.ch\/en\/ifc-cobie-iso19650-scan-to-bim-deliverables\/#IFC_vs_Native_Files_What_You_Can_and_Cannot_Do\" >IFC vs. Native Files: What You Can and Cannot Do<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-3\" href=\"https:\/\/vmts.ch\/en\/ifc-cobie-iso19650-scan-to-bim-deliverables\/#COBie_Structured_Data_for_Facility_Handover\" >COBie: Structured Data for Facility Handover<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-4\" href=\"https:\/\/vmts.ch\/en\/ifc-cobie-iso19650-scan-to-bim-deliverables\/#ISO_19650_A_Management_Standard_Not_a_File_Format\" >ISO 19650: A Management Standard, Not a File Format<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-5\" href=\"https:\/\/vmts.ch\/en\/ifc-cobie-iso19650-scan-to-bim-deliverables\/#What_VMTS_Delivers_as_Standard\" >What VMTS Delivers as Standard<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-6\" href=\"https:\/\/vmts.ch\/en\/ifc-cobie-iso19650-scan-to-bim-deliverables\/#Frequently_Asked_Questions\" >Frequently Asked Questions<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-7\" href=\"https:\/\/vmts.ch\/en\/ifc-cobie-iso19650-scan-to-bim-deliverables\/#Need_native_IFC_or_COBie_deliverables_or_all_three\" >Need native, IFC, or COBie deliverables, or all three?<\/a><\/li><\/ul><\/nav><\/div>\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"What_Is_IFC_and_Why_It_Matters_for_BIM_Delivery\"><\/span>What Is IFC, and Why It Matters for BIM Delivery<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>IFC (Industry Foundation Classes)<\/strong> 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 <a href=\"https:\/\/www.buildingsmart.org\/\" target=\"_blank\" rel=\"noopener nofollow\">buildingSMART International<\/a> and is the closest thing the industry has to a universal BIM exchange format.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">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&#8217;t need to edit it. IFC is an exchange format, and it does that job well.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"IFC_vs_Native_Files_What_You_Can_and_Cannot_Do\"><\/span>IFC vs. Native Files: What You Can and Cannot Do<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Where IFC runs into trouble is when it&#8217;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.<\/p>\n\n\n\n<div class=\"wp-block-group has-background\" style=\"background-color:#F5F5F5;border-left:3px solid #C70100;padding-top:20px;padding-right:24px;padding-bottom:20px;padding-left:24px\"><div class=\"wp-block-group__inner-container is-layout-flow wp-block-group-is-layout-flow\">\n\n<p class=\"wp-block-paragraph\" style=\"font-size:10px;font-style:normal;font-weight:700;letter-spacing:0.12em;text-transform:uppercase;color:#C70100\">A real example: the &#8220;dead object&#8221; problem<\/p>\n\n\n<p class=\"wp-block-paragraph\" style=\"color:#4A4A4A\">Most standard IFC elements such as walls and columns import cleanly and stay editable. But many other objects don&#8217;t survive the round-trip as intelligent, parametric elements. A window imported as IFC into a different platform can behave as a &#8220;dead object&#8221;: to change it, you often have to redraw it from scratch, and the smart wall-to-window relationship is lost in the process. Teams that discover this mid-project sometimes end up remodeling the entire building natively, after already paying for an IFC-based deliverable that could not actually be edited.<\/p>\n\n<\/div><\/div>\n\n\n\n<figure class=\"wp-block-image size-large\"><img decoding=\"async\" width=\"1600\" height=\"900\" src=\"https:\/\/vmts.ch\/wp-content\/uploads\/2026\/09\/ifc-dead-object-vs-native-editable.jpg\" data-orig-src=\"https:\/\/vmts.ch\/wp-content\/uploads\/2026\/09\/ifc-dead-object-vs-native-editable.jpg\" alt=\"Isometric BIM diagram: two windows stay editable parametric elements with grip handles while one window imported via IFC becomes a red dead object detached from the wall\" class=\"lazyload wp-image-39215\" srcset=\"data:image\/svg+xml,%3Csvg%20xmlns%3D%27http%3A%2F%2Fwww.w3.org%2F2000%2Fsvg%27%20width%3D%271600%27%20height%3D%27900%27%20viewBox%3D%270%200%201600%20900%27%3E%3Crect%20width%3D%271600%27%20height%3D%27900%27%20fill-opacity%3D%220%22%2F%3E%3C%2Fsvg%3E\" data-srcset=\"https:\/\/vmts.ch\/wp-content\/uploads\/2026\/09\/ifc-dead-object-vs-native-editable-200x113.jpg 200w, https:\/\/vmts.ch\/wp-content\/uploads\/2026\/09\/ifc-dead-object-vs-native-editable-300x169.jpg 300w, https:\/\/vmts.ch\/wp-content\/uploads\/2026\/09\/ifc-dead-object-vs-native-editable-400x225.jpg 400w, https:\/\/vmts.ch\/wp-content\/uploads\/2026\/09\/ifc-dead-object-vs-native-editable-600x338.jpg 600w, https:\/\/vmts.ch\/wp-content\/uploads\/2026\/09\/ifc-dead-object-vs-native-editable-768x432.jpg 768w, https:\/\/vmts.ch\/wp-content\/uploads\/2026\/09\/ifc-dead-object-vs-native-editable-800x450.jpg 800w, https:\/\/vmts.ch\/wp-content\/uploads\/2026\/09\/ifc-dead-object-vs-native-editable-1024x576.jpg 1024w, https:\/\/vmts.ch\/wp-content\/uploads\/2026\/09\/ifc-dead-object-vs-native-editable-1200x675.jpg 1200w, https:\/\/vmts.ch\/wp-content\/uploads\/2026\/09\/ifc-dead-object-vs-native-editable-1536x864.jpg 1536w, https:\/\/vmts.ch\/wp-content\/uploads\/2026\/09\/ifc-dead-object-vs-native-editable.jpg 1600w\" data-sizes=\"auto\" data-orig-sizes=\"(max-width: 1600px) 100vw, 1600px\" \/><figcaption class=\"wp-element-caption\">Native walls and windows stay editable; an IFC-imported window can lose its link to the wall and become a &#8220;dead object.&#8221;<\/figcaption><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">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 <a href=\"https:\/\/vmts.ch\/en\/point-cloud-to-revit\/\">Point Cloud to Revit workflow guide<\/a> walks through what a native, LOD-defined deliverable looks like in practice.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"COBie_Structured_Data_for_Facility_Handover\"><\/span>COBie: Structured Data for Facility Handover<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>COBie (Construction Operations Building Information Exchange)<\/strong> 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.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A geometry-only model, even a well-modeled native file, doesn&#8217;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.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"ISO_19650_A_Management_Standard_Not_a_File_Format\"><\/span>ISO 19650: A Management Standard, Not a File Format<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\"><strong><a href=\"https:\/\/www.iso.org\/standard\/68078.html\" target=\"_blank\" rel=\"noopener nofollow\">ISO 19650<\/a><\/strong> 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&#8217;t specify any particular software or exchange format at all. Instead, it standardizes things like:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Common Data Environment (CDE) workflows:<\/strong> how information moves between &#8220;Work in Progress,&#8221; &#8220;Shared,&#8221; &#8220;Published,&#8221; and &#8220;Archived&#8221; states<\/li>\n<li><strong>Information requirements:<\/strong> defining what information is needed, by whom, and at what stage of a project<\/li>\n<li><strong>Naming conventions and metadata:<\/strong> consistent structure so files and data can be found and trusted across a project team<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">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&#8217;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.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"What_VMTS_Delivers_as_Standard\"><\/span>What VMTS Delivers as Standard<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">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:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Native BIM file<\/strong> at the agreed LOD, the primary editable deliverable<\/li>\n<li><strong>IFC export<\/strong> on request, for coordination, clash detection, or handoff to platforms that don&#8217;t need to edit the model<\/li>\n<li><strong>COBie export<\/strong> on request, for projects handing structured asset data to a CMMS\/CAFM system<\/li>\n<li><strong>A documented QC report<\/strong> checking the model against the source point cloud<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">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 <a href=\"https:\/\/vmts.ch\/en\/scan-to-bim-cost\/\">Scan-to-BIM Cost Guide 2026<\/a>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">These native-first deliverables are also central to evaluating an overseas partner in the first place. See <a href=\"https:\/\/vmts.ch\/en\/bim-outsourcing-vietnam-dach-market\/\">why European firms outsource Scan-to-BIM to Vietnam<\/a> for how quality, data security and communication safeguards fit around a deliverable like this.<\/p>\n\n\n\n<blockquote class=\"wp-block-quote has-background is-layout-flow wp-block-quote-is-layout-flow\" style=\"background-color:#C70100;color:#ffffff;padding:22px 36px;border:none\">\n<p style=\"color:#ffffff;font-size:16px;font-weight:700;font-style:normal;margin:0;line-height:1.45\">&#8220;You scan. We support all downstream services, from point clouds to native BIM models, plus whatever exchange format your workflow needs on top.&#8221;<\/p>\n<\/blockquote>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Frequently_Asked_Questions\"><\/span>Frequently Asked Questions<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>What&#8217;s the difference between IFC and a native BIM file?<\/summary>\n\n<p class=\"wp-block-paragraph\">A native file (Revit, Archicad, Allplan, Vectorworks) is built with the software&#8217;s own parametric elements and stays fully editable. IFC is a vendor-neutral exchange format, good for interoperability and coordination, but many imported IFC objects lose their editable, parametric behavior.<\/p>\n\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>Do I need both a native file and an IFC export?<\/summary>\n\n<p class=\"wp-block-paragraph\">In most cases, yes. The native file is what you&#8217;d use for ongoing editing and design work; the IFC export is useful for coordination, clash detection, or sharing with parties using different software. VMTS delivers the native file as standard and IFC on request.<\/p>\n\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>What is COBie used for?<\/summary>\n\n<p class=\"wp-block-paragraph\">COBie packages non-graphical asset data such as equipment, spaces and attributes into a structured format designed for handover to facility management systems (CMMS\/CAFM). It&#8217;s most relevant at the point a project transitions from construction and documentation to operations.<\/p>\n\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>Is ISO 19650 a file format like IFC?<\/summary>\n\n<p class=\"wp-block-paragraph\">No. ISO 19650 is a management standard for how BIM information is organized and exchanged across a project&#8217;s lifecycle, covering Common Data Environment workflows, information requirements and naming conventions. It doesn&#8217;t specify a particular file format or software.<\/p>\n\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>Can a single BIM deliverable be &#8220;ISO 19650 compliant&#8221;?<\/summary>\n\n<p class=\"wp-block-paragraph\">Not really. ISO 19650 compliance applies at the project and organizational level, not to a single file. What a Scan-to-BIM provider can do is deliver in a way that&#8217;s compatible with an ISO 19650 workflow: consistent naming, documented QC, and native plus IFC formats.<\/p>\n\n<\/details>\n\n\n\n<div class=\"wp-block-group has-background\" style=\"background-color:#000000;padding:48px\"><div class=\"wp-block-group__inner-container is-layout-flow wp-block-group-is-layout-flow\">\n\n<p class=\"wp-block-paragraph\" style=\"font-size:10px;font-style:normal;font-weight:700;letter-spacing:0.16em;text-transform:uppercase;color:#C70100\">Work with VMTS<\/p>\n\n\n<h2 class=\"wp-block-heading\" style=\"color:#ffffff;font-size:24px;font-weight:400;line-height:1.3;border:none\"><span class=\"ez-toc-section\" id=\"Need_native_IFC_or_COBie_deliverables_or_all_three\"><\/span>Need native, IFC, or COBie deliverables, or all three?<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n<p class=\"wp-block-paragraph\" style=\"color:#888888;font-size:14px\">Tell us your project&#8217;s workflow and downstream systems, and we respond within one business day with an initial assessment.<\/p>\n\n\n<div class=\"wp-block-buttons is-layout-flex wp-block-buttons-is-layout-flex\">\n\n<div class=\"wp-block-button\"><a class=\"fusion-button button-flat button-large button-custom fusion-button-default fusion-button-default-span fusion-button-default-type\" style=\"--button_accent_color:var(--awb-color1);--button_accent_hover_color:var(--awb-color1);--button_border_hover_color:var(--awb-color1);--button_gradient_top_color:var(--awb-custom_color_1);--button_gradient_bottom_color:var(--awb-custom_color_1);--button_gradient_top_color_hover:hsla(var(--awb-custom_color_1-h),var(--awb-custom_color_1-s),calc(var(--awb-custom_color_1-l) - 12%),var(--awb-custom_color_1-a));--button_gradient_bottom_color_hover:hsla(var(--awb-custom_color_1-h),var(--awb-custom_color_1-s),calc(var(--awb-custom_color_1-l) - 12%),var(--awb-custom_color_1-a));--button_text_transform:uppercase;\" target=\"_self\" data-hover=\"icon_slide\" href=\"https:\/\/vmts.ch\/en\/contact-us\/\"><span class=\"fusion-button-text awb-button__text awb-button__text--default\">Request assessment<\/span><i class=\"fa-long-arrow-alt-right fas awb-button__icon awb-button__icon--default button-icon-right\" aria-hidden=\"true\"><\/i><\/a><\/div>\n\n<\/div>\n\n<\/div><\/div>\n\n\n\n<script type=\"application\/ld+json\">{\"@context\":\"https:\/\/schema.org\",\"@type\":\"FAQPage\",\"mainEntity\":[{\"@type\":\"Question\",\"name\":\"What's the difference between IFC and a native BIM file?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"A native file stays fully editable in its authoring software. IFC is a vendor-neutral exchange format, good for interoperability, but many imported IFC objects lose their editable, parametric behavior.\"}},{\"@type\":\"Question\",\"name\":\"Do I need both a native file and an IFC export?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"In most cases, yes. The native file supports ongoing editing; the IFC export supports coordination and clash detection with other platforms.\"}},{\"@type\":\"Question\",\"name\":\"What is COBie used for?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"COBie packages non-graphical asset data into a structured format designed for handover to facility management systems (CMMS\/CAFM).\"}},{\"@type\":\"Question\",\"name\":\"Is ISO 19650 a file format like IFC?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"No. ISO 19650 is a management standard for how BIM information is organized and exchanged across a project's lifecycle. It doesn't specify a particular file format.\"}},{\"@type\":\"Question\",\"name\":\"Can a single BIM deliverable be ISO 19650 compliant?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"Not really. ISO 19650 compliance applies at the project and organizational level. A provider can deliver in a way compatible with an ISO 19650 workflow.\"}}]}<\/script>\n\n\n","protected":false},"excerpt":{"rendered":"<p>TL;DR: 3 things to know 01 IFC is an exchange format, not a modeling format. Imported IFC objects often behave as &#8220;dead objects&#8221; that cannot be edited the way native elements can. 02 COBie packages [&#8230;]<\/p>\n","protected":false},"author":2,"featured_media":26875,"comment_status":"closed","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[],"tags":[],"class_list":["post-38905","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry"],"acf":[],"_links":{"self":[{"href":"https:\/\/vmts.ch\/en\/wp-json\/wp\/v2\/posts\/38905","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/vmts.ch\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/vmts.ch\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/vmts.ch\/en\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/vmts.ch\/en\/wp-json\/wp\/v2\/comments?post=38905"}],"version-history":[{"count":6,"href":"https:\/\/vmts.ch\/en\/wp-json\/wp\/v2\/posts\/38905\/revisions"}],"predecessor-version":[{"id":39223,"href":"https:\/\/vmts.ch\/en\/wp-json\/wp\/v2\/posts\/38905\/revisions\/39223"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/vmts.ch\/en\/wp-json\/wp\/v2\/media\/26875"}],"wp:attachment":[{"href":"https:\/\/vmts.ch\/en\/wp-json\/wp\/v2\/media?parent=38905"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/vmts.ch\/en\/wp-json\/wp\/v2\/categories?post=38905"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/vmts.ch\/en\/wp-json\/wp\/v2\/tags?post=38905"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}