Technology
Microsoft Approvals and the Approvals Kit orchestrate decisions (approve/reject). They do not provide ISO 19650 governance primitives: information states, release gates, naming/metadata enforcement, or repeatable project blueprints. A policy-driven ISO layer treats approvals as one step inside a gated state transition—not the governance engine itself.
The terminology problem
In Microsoft 365 environments, “approval” conflates two distinct concepts: a workflow task (approve/reject an item) and a release authorization (transition information into a contractually binding state). Treating Power Automate approval flows as ISO 19650 publication governance produces fragile implementations, incomplete audit trails, and operational complexity at scale.
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.
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:
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:
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.