Level 3 Information Manager – ISO 19650 Expert

This video explains how open BIM principles and tools support ISO 19650 information management across different software platforms. The written guide below covers what open BIM means in practice, how IFC and BCF improve model sharing and issue coordination, how the buildingSMART Data Dictionary (bSDD) and Information Delivery Specification (IDS) standardise requirements in a machine-readable format, and how COBie workflows streamline structured asset information handover at every project milestone.

Why open BIM standards make ISO 19650 information management practical

One of the most persistent challenges in BIM project delivery is interoperability. Teams use different software platforms, and when information has to move between those platforms, data gets lost, formats break, and people end up recreating work that should have transferred cleanly. This is the core problem that open BIM is designed to solve. Rather than locking teams into proprietary ecosystems where data exchange is tedious and error-prone, open BIM uses shared standards that allow information to flow between any tools that support them. Under ISO 19650, where multiple organisations collaborate on the same information model across the full project lifecycle, this interoperability is not a nice-to-have. It is a practical requirement for making the standard work in real delivery environments.

The open BIM ecosystem is built on a set of connected standards that each address a different part of the information workflow. Industry Foundation Classes (IFC) provide the open format for sharing model geometry and data between different authoring tools, meaning architects, engineers, and contractors can all work in their preferred software while still exchanging models that any other compliant tool can read. The BIM Collaboration Format (BCF) complements IFC by providing a standardised way to report and coordinate issues. When exceptions arise during coordination, such as clashes, missing data, or deliverables that do not meet requirements, BCF ensures that every team member sees the issue in the same way within their own native environment, making resolution faster and more reliable than email chains or ad hoc spreadsheets.

Behind these exchange formats sit two standards that address the definition and verification of information requirements themselves. The buildingSMART Data Dictionary (bSDD) is an online service that stores standardised terms, properties, units, translations, and relations for the construction industry. It acts as a central reference point so that everyone on a project uses consistent definitions when specifying what information is needed. The Information Delivery Specification (IDS) builds on this by providing a machine-readable format for defining information requirements. Instead of scattering requirements across static PDFs and Excel files where interpretation varies from person to person, IDS creates structured specifications that define exactly what information is needed, when it is needed, and how it should be delivered. In Plannerly’s Scope module, creating an IDS is straightforward: select a data dictionary such as Uniclass 2015, search for the element you need, assign classification codes and entity types automatically, define requirements against specific milestones, and export the IDS file with a single click.

The final piece of this workflow is COBie, the Construction Operations Building Information Exchange. COBie provides a structured format for organising and delivering asset information at handover. Many teams find COBie overwhelming because the output looks like a massive, complex spreadsheet. But the process does not have to be complicated if it is built into the workflow from the start rather than assembled manually at the end. By defining information requirements early, verifying models against those requirements automatically, and then exporting only the data that has been requested, teams can produce accurate COBie deliverables with far less effort. The BIM verification and COBie handover workflow in Plannerly connects these three steps — requirements, verification, and export — into a single integrated process that can be repeated at every milestone.

How to implement open BIM standards in your ISO 19650 workflow

  1. Select a data dictionary for your project – Go to the project settings and choose the buildingSMART Data Dictionary that matches your project’s classification system, such as Uniclass 2015. This ensures that all element definitions, properties, and classification codes are drawn from a consistent, standardised source.
  2. Define information requirements using IDS – Use the Scope module to search the dictionary, select elements, and create structured requirements with classification codes and IFC entity types assigned automatically. Assign requirements to specific milestones so that expectations are clear at every delivery stage.
  3. Export the IDS file – Once requirements are defined, export the IDS file so that every team has a machine-readable specification they can use to configure their authoring tools and validate their own deliverables before submission.
  4. Use IFC for model exchange – Require teams to share models in IFC format so that information can be read and checked regardless of which authoring software was used. This removes the dependency on proprietary formats and ensures that the appointing party can verify deliverables independently.
  5. Coordinate issues using BCF – When exceptions arise during review or quality checks, use the BIM Collaboration Format to report issues in a standardised way. Each team member sees the issue in their native environment, reducing miscommunication and accelerating resolution.
  6. Verify models against requirements – Use the Verify module to check models automatically against the defined requirements. The system flags anything that is missing or incomplete, giving teams a clear view of what needs to be corrected before formal submission.
  7. Export COBie data at each milestone – Once verification is complete, export the handover data automatically, filtered for just the requirements that were requested. This produces structured COBie deliverables without the manual effort of assembling spreadsheets from scratch.
  8. Iterate throughout the project lifecycle – Repeat the requirements, verification, and export cycle at every milestone. This approach builds confidence incrementally rather than leaving handover data assembly to the final stages of the project when errors are most expensive to correct.

What you’ll learn

  • Open BIM principles – Why using open standards like IFC and BCF removes interoperability barriers, allowing teams to collaborate across different software platforms without data loss or format conversion issues.
  • The buildingSMART Data Dictionary – How bSDD provides a centralised, standardised reference for construction terminology, properties, and classification codes, ensuring that every team on a project speaks the same language when defining information requirements.
  • Information Delivery Specification (IDS) – How IDS transforms information requirements from ambiguous PDFs and spreadsheets into machine-readable specifications that can be used to configure authoring tools and automate verification.
  • BCF for issue coordination – How the BIM Collaboration Format provides a reactive safety net for reporting and resolving exceptions when proactive quality checks identify issues that need attention.
  • COBie handover workflows – How defining requirements early, verifying models against them automatically, and exporting filtered data at each milestone transforms COBie from an overwhelming manual task into a streamlined, repeatable process.
  • Integrated requirements-to-handover workflow – How connecting requirements definition, automated model verification, and structured data export into a single process reduces manual effort, improves accuracy, and delivers better handover information at every project stage.

Common questions

What is the difference between open BIM and closed BIM?

Closed BIM workflows rely on proprietary file formats that only work within specific software ecosystems. When teams use different tools, data exchange becomes difficult, error-prone, and often requires manual recreation of information. Open BIM uses vendor-neutral standards like IFC, BCF, and IDS so that information can be shared, read, and verified regardless of which software was used to create it. This is particularly important under ISO 19650, where multiple organisations must collaborate on the same information model.

How does IDS differ from traditional requirements documents?

Traditional requirements are typically defined in PDFs, Word documents, or Excel spreadsheets, which are static and open to interpretation. The Information Delivery Specification (IDS) is a machine-readable standard that defines exactly what data is needed, which elements it applies to, and how it should be structured. Because machines can read IDS files, authoring tools can be configured to produce compliant information, and verification tools can check deliverables automatically against the specification.

Does COBie have to be a massive, confusing spreadsheet?

COBie data only feels overwhelming when it is assembled manually at the end of a project. When requirements are defined at the start, models are verified against those requirements throughout delivery, and the export is filtered to include only the data that was actually requested, the result is a clean, structured handover dataset. Plannerly automates this workflow so that components, systems, and zones are compiled into a single export with the values pulled directly from verified model elements.

Can I create an IDS file in Plannerly?

Yes. In the Scope module, select a data dictionary such as Uniclass 2015, search for the elements you need, and Plannerly automatically assigns classification codes and IFC entity types. Define requirements against milestones, then export the IDS file with a single click. This gives every team a machine-readable specification they can use to validate their own work before submission.

Explore further

0% Complete

Pin It on Pinterest