Flinker Data Connector for Power BI — Load Complete openBIM Data

IFC Validation and Guided Correction in Practice: A Use Case for BIM Teams

The IFC Quality Problem Every BIM Team Knows

IFC files are the primary exchange format across the AECO industry — but a file that opens correctly in one tool regularly carries issues that cause silent failures when used downstream. Structural hierarchy problems, schema violations, and missing representations often go undetected until another application fails to import the model, a coordination platform flags unexpected gaps, or a handover package is rejected at quality review.

IFC Model Data in Excel: Using Copilot for IFC to Track Construction Progress

The Progress Reporting Problem in Construction

Construction projects track hundreds or thousands of individual work packages across multiple floors, trades, and delivery phases. The data that would let a site manager, BIM coordinator, or project controller answer “what has been installed on floor 1 this week?” typically lives in two disconnected places: the BIM model — which contains every element, its type, its storey, and its properties — and a separate spreadsheet or site diary, which has status updates but no reliable link back to model elements.

ISO 19650 on SharePoint: Why a Policy-Driven App Beats Power Automate-Only

ISO 19650 on SharePoint: Why a Policy-Driven App Beats a “Power Automate-Only” Approach

Many construction and infrastructure organizations want an ISO 19650–aligned Common Data Environment (CDE) while keeping data inside Microsoft 365. SharePoint provides the underlying document management platform, and Power Automate is often used to stitch processes together. In practice, however, an ISO 19650 CDE requires more than automation steps: it requires governance, repeatability, enforceable rules, and predictable user experience at scale.

ISO 19650 App for SharePoint

ISO 19650 and SharePoint: Making Your Project Data Room Compliant

ISO 19650 is becoming a baseline requirement in construction and infrastructure contracts. Many organizations already have Microsoft 365 and SharePoint in place—often underutilized for project document control. The question: can SharePoint serve as a fully ISO 19650-compliant Common Data Environment (CDE)?

Yes—but only with the right controls, workflows, and governance layered on top. Native SharePoint provides foundational capabilities but lacks the discipline ISO 19650 demands.

What is ISO 19650?

ISO 19650 is the international standard (originating from the UK’s PAS/BS 1192 lineage) for information management using BIM across the lifecycle of a built asset. It covers how information is exchanged, approved, stored, and retrieved, and defines the Common Data Environment (CDE)—the single agreed source of truth for all project information.

Flinker IFC Viewer for Power BI — Overview & Pricing

Leveraging SharePoint as a Common Data Environment (CDE) for Large Construction Projects

A Common Data Environment (CDE) centralizes project documents, drawings, models, and coordination data in a single accessible location. For organizations using Microsoft 365, SharePoint provides the underlying infrastructure: document libraries, metadata, version control, and permissions.

This guide covers the technical implementation of SharePoint as a CDE for construction projects.

SharePoint capabilities relevant to CDE

Data storage and organization

SharePoint document libraries support:

• Folder hierarchies for organizing by discipline, zone, or work package
• Metadata columns for classification (document type, status, revision, originator)
• Content types for applying consistent metadata schemas across libraries
• Views for filtering and sorting based on metadata values

Version control

• Automatic version history with configurable major/minor versioning
• Check-in/check-out to prevent concurrent editing conflicts
• Version comments and restore capability

Permissions and access

• Site-level, library-level, folder-level, and item-level permissions
• SharePoint groups for role-based access (e.g., design team, contractor, client)
• External sharing with configurable link expiration and password protection
• Conditional access policies through Azure AD

Integration with Microsoft 365

• Teams: Channels linked to SharePoint folders for collaboration context
• Power BI: Reports and dashboards connected to SharePoint lists and libraries
• Power Automate: Workflow automation for notifications, approvals, metadata updates
• Outlook: Email alerts and document sharing

Example CDE folder structure

A typical SharePoint CDE for construction might use this hierarchy:

How Leading Construction Companies Use SharePoint as a Common Data Environment (CDE)

Construction projects generate large volumes of documents, drawings, models, and coordination data. Traditional tools—shared drives, email attachments, siloed platforms—create fragmentation that leads to version conflicts, access issues, and coordination errors.

Many construction firms already have Microsoft 365 licenses. SharePoint, as part of that ecosystem, provides a foundation for a Common Data Environment (CDE): centralized storage, version control, granular permissions, and integration with Teams, Power BI, and other Microsoft tools.

Why SharePoint as a CDE?

SharePoint offers several characteristics relevant to construction project data management:

IFC Viewer for Power BI: Visualize BIM Models in Your Dashboards

Power BI is the standard for business intelligence across many organizations. But when it comes to construction and facility data, something is missing: the 3D model. IFC files contain rich geometry and attributes, yet Power BI shows only tables and charts—no spatial context.

The Flinker IFC Viewer solves this. It renders IFC models directly inside Power BI reports, enabling interactive 3D visualization alongside your existing dashboards. No external software, no data uploads, no extra licenses.