Course Content
Level 1 Information Manager – Basics

This video shows how to connect to the buildingSMART Data Dictionary and use it to standardize classifications, naming, and information requirements. The written guide below explains how to configure classification systems and property domains in project settings, then apply those standards directly when building scope.

Standardize project information with the buildingSMART Data Dictionary

Consistency is one of the hardest things to achieve across a project team. When different people name elements differently, use different classification codes, or define properties in their own way, the result is data that doesn’t connect properly between systems and teams that spend time resolving confusion instead of delivering. Adopting common standards solves this, and Plannerly connects directly to the buildingSMART Data Dictionary (bSDD) so your team can standardize without extra effort.

The connection is configured in project settings, where you choose two things: a classification system and a properties domain. For classification, you might select Uniclass, Uniformat, or any other system available through bSDD. For properties, you might choose the IFC properties domain. Once these are set, the Scope module uses them automatically whenever you create new items. Start typing a name and Plannerly searches the bSDD using your chosen classification structure, returning correctly named and correctly classified results with their codes already attached. There is no need to look up codes manually or worry about whether your team is following the right naming conventions.

The same applies to information requirements. When you create properties for your scope items, the bSDD connection means you can search for standardized property names like material type or material thickness, and the name and description come directly from the standard. This matters because descriptions from the standard add clarity that helps the whole team understand exactly what each property means, reducing the back-and-forth that happens when requirements are defined in vague or inconsistent terms.

For teams working under ISO 19650, this integration addresses a core challenge: making sure that information requirements are defined clearly enough to be verified later. When your scope items follow recognized BIM standards and your properties come from established domains, the data you produce is interoperable by default. It flows between authoring tools, checking systems, and asset management platforms without the translation problems that plague projects where every team invents their own naming conventions.

How to connect to the buildingSMART Data Dictionary

  1. Open project settings – Navigate to your project dashboard and open the settings panel where classification and property options are configured.
  2. Choose a classification system – Select a classification such as Uniclass from the available options in the bSDD. This determines how scope items will be classified and coded.
  3. Choose a properties domain – Select a properties domain such as IFC properties. This determines which standardized property names are available when defining information requirements.
  4. Create scope items – Go to the Scope module and start typing to add new items. The bSDD connection automatically suggests correctly named and classified entries.
  5. Apply classification codes – Select from the suggested results to apply both the standardized name and the correct classification code to each item.
  6. Define information requirements – When adding properties, search the bSDD for standardized property names and descriptions rather than creating custom ones from scratch.
  7. Review for consistency – Check that your scope items and properties follow the selected standards, ensuring the data will be interoperable across tools and teams.

What you’ll learn

  • bSDD connection – How to configure the buildingSMART Data Dictionary integration in project settings to enable standardized naming and classification.
  • Classification systems – How to choose and apply a classification system like Uniclass so that scope items are correctly coded from the moment they are created.
  • Property domains – How to select an IFC or other properties domain so that information requirements follow established naming conventions.
  • Standardized naming – How automatic bSDD lookups prevent inconsistent naming and remove the need to manually reference classification tables.
  • Interoperability – How adopting common standards through bSDD makes project data flow more smoothly between teams, tools, and delivery stages.

Common questions

Which classification systems are available through the bSDD connection?

The buildingSMART Data Dictionary includes a wide range of classification systems from around the globe, including Uniclass, Uniformat, and many regional standards. You select the one that applies to your project in the settings. If you don’t see the classification you expect, check the troubleshooting guide for bSDD classifications to resolve common configuration issues.

Can I use custom property names alongside bSDD standards?

Yes. The bSDD connection provides standardized suggestions, but you can also create custom properties when your project has specific requirements that aren’t covered by the standard domains. The key benefit is that for common properties like material type or thickness, using the standard version ensures consistency and interoperability across the AEC ecosystem.

How does this help with ISO 19650 compliance?

ISO 19650 requires that information requirements are defined clearly and consistently so they can be verified during delivery. When your scope items and properties follow bSDD standards, they meet this requirement by default. The standardized descriptions also help when creating asset information requirements (AIR) and other formal requirement documents.

Do the classification codes cascade through the scope hierarchy?

Yes. When you apply classification codes through the bSDD connection, they integrate with the scope hierarchy’s cascading code system. You can control whether codes concatenate through the levels in project settings, as covered in the creating and structuring scope documentation.

Explore further

0% Complete

Pin It on Pinterest