For small-to-mid-sized engineering and architecture firms, delivering successful projects hinges on streamlined information management. While standards like ISO 19650 offer a robust framework, simply knowing the standard isn’t enough. Many firms struggle to translate these principles into a practical, reliable system, especially when leveraging platforms like SharePoint. This post explores common pitfalls encountered when implementing document management standards and how to build a lightweight, ISO 19650-aligned Common Data Environment (CDE) on SharePoint to overcome them.

The Promise of a Common Data Environment (CDE)

A Common Data Environment (CDE) is a single, authoritative source of information for all project stakeholders. It’s a digital workspace where all project documents are stored, managed, and accessed, ensuring everyone works from the latest, approved information. Crucially, a CDE isn’t just a file repository; it’s a system that manages the entire lifecycle of information, from creation to archive. Information management according to BS EN ISO 19650 Guidance ... provides further detail on this process. This controlled environment minimizes errors, reduces rework, and fosters collaboration. As Understanding ISO 19650: Guide for BIM Management in Construction highlights, ISO 19650 emphasizes starting with well-defined information requirements to drive every process within the CDE.

Common Pitfalls

Implementing a CDE, even on a familiar platform like SharePoint, isn’t without its challenges. Here are some common pitfalls we’ve observed:

The “Wild West” Folder Structure: Many firms start with a basic SharePoint setup, quickly descending into a chaotic mess of nested folders. Imagine a scenario: a structural engineer needs the latest foundation drawings, but they’re buried six folders deep, named with ambiguous codes like “FND_RevA_Draft2_Final.” This wastes valuable time and increases the risk of using outdated information. Proper file naming conventions, like those suggested in Version Control for BIM Projects: Best Practices, are crucial to avoid this.
Permission Pandemonium: SharePoint’s permission system, while powerful, can become unmanageable. We’ve seen projects where access is granted on a person-by-person basis, leading to inconsistencies and security vulnerabilities. For example, a contractor might have access to sensitive design documents they shouldn’t, or a key team member is locked out of critical files. 8 Best Practices When Using SharePoint Permissions - NENS and Top SharePoint permission management practices - ShareGate both emphasize managing permissions at the site level and utilizing SharePoint groups effectively.
Version Control Chaos: Relying on manual versioning (“_v1”, “_v2”, etc.) is a recipe for disaster. It’s easy to overwrite changes, lose track of revisions, and struggle to identify the correct version for a specific task. Consider a clash detection report: multiple iterations are created, but it’s unclear which one reflects the final coordinated model. BIM Model Version Control: Best Practices For Project Success stresses the importance of a CDE for robust version control.
Unreliable CAD/BIM Workflows: Traditional file-based CAD/BIM workflows are prone to errors and inefficiencies. Checking files in and out can be cumbersome, and ensuring everyone is working with the latest models is a constant struggle. This often leads to costly rework and delays.
SharePoint as a Digital Dumping Ground: Without clear governance and processes, SharePoint can quickly become a repository for everything, making it difficult to find critical project information. This defeats the purpose of a CDE and undermines trust in the system.

Beyond File Management: The Benefits of a Purpose-Built CDE

Moving beyond basic file storage unlocks significant benefits for your engineering and architecture firm. Here’s how a well-implemented CDE transforms your workflows:

Single Source of Truth: Eliminate confusion and ensure everyone is working with the latest, approved information. This reduces errors and minimizes the risk of costly rework.
Reduced Rework: By providing a clear audit trail and controlled access to information, a CDE helps prevent mistakes and facilitates faster issue resolution.
Stop the Digital Clutter: A CDE enforces consistent naming conventions, metadata tagging, and folder structures, preventing SharePoint from becoming a disorganized mess.
QA/QC Without Overhead: Automated workflows and status tracking streamline the quality assurance process, reducing manual effort and improving accuracy.
Stabilized CAD/BIM Workflows: Integrated workflows and version control ensure seamless collaboration and minimize errors in your CAD/BIM processes.
Scalable Project Delivery: A CDE provides a robust foundation for managing projects of any size, enabling you to scale your operations without sacrificing control or efficiency.

A CDE built on SharePoint doesn’t have to be complex or expensive. By focusing on clear processes, consistent metadata, and automated workflows, you can transform your existing SharePoint investment into a powerful tool for project success. ISO 19650: Essential Insights for Information Management emphasizes the importance of setting up a CDE as a core principle of the standard.

Loading...