SharePoint can provide the document management foundation for a common data environment (CDE). A project still needs agreed information requirements, assigned responsibilities, and a controlled process for reviewing and issuing information. Installing software or creating four folders does not establish ISO 19650 compliance.
Start with the information management requirements
ISO 19650 addresses information management using BIM across the asset lifecycle. Part 1 sets out concepts and principles, Part 2 covers the delivery phase, and Part 3 covers the operational phase. The series also includes other subjects; the later parts are not simply extensions of operational asset management. See the ISO 19650-2 overview for its delivery-phase scope.
Before configuring SharePoint, establish what each delivery team must provide, the agreed information standard, review responsibilities, and acceptance criteria. Record which national provisions and client requirements apply to the appointment.
Map the workflow to the platform
The CDE workflow distinguishes Work in Progress, Shared, Published, and Archive. These describe how information is managed and used. Archive preserves the history of information and its transactions; it should not be treated only as a folder for obsolete files. The UK BIM Framework CDE guidance explains the relationship between the workflow and its technical solutions.
SharePoint supplies libraries, metadata, permissions, version history, and content approval. Configure those capabilities around the project process. A library column can hold a suitability code, but assigning that value does not prove that the required review occurred.
- Define the identifier, classification, suitability, and revision information required for each deliverable.
- Assign who can create, review, authorize, accept, and issue information.
- Associate decisions with the file version that was reviewed.
- Set retention and access rules for the evidence the project must preserve.
Configure access around responsibilities
Access should follow each participant’s role and appointment. Being external to your organization does not, by itself, determine which CDE state that person may access. Test the permissions needed by designers, reviewers, contractors, and client representatives using representative accounts.
Where you add Flinker applications or custom automation, document the controls each component implements. Verify where validation runs and whether users can bypass a release process through another upload or editing route.
Verify the process before rollout
Use a representative package to test submission, rejection, correction, authorization, and issue. Include a file changed during review and an attempt to publish without permission. The resulting records should show what was issued, by whom, and on which basis.
Use the SharePoint CDE rollout guide to turn these requirements into a pilot and an operating procedure.