What Is an IPD Shared Data Environment?
In this article, an IPD shared data environment refers to a controlled digital environment where owners, architects, engineers, contractors and trade partners work from aligned project information. It brings together room requirements, asset data, BIM-linked information, responsibilities, changes and validation results so teams can make decisions from reliable data.
Why IPD projects need shared data
Integrated Project Delivery brings key project participants together earlier and more closely than traditional delivery models. The Lean Construction Institute describes IPD as an approach that aligns people, systems, business structures and practices to improve collaboration and project outcomes.
When room requirements, asset specifications and BIM information are managed separately, teams can quickly lose alignment. Different versions of the same requirement may circulate at once. Room data sheets may not reflect the latest decision. Equipment can be modelled without being checked against agreed performance or space requirements.
A shared data environment reduces this fragmentation by giving teams a controlled way to manage and review information across disciplines.
What does “shared source of truth” mean?
A shared source of truth does not mean storing every file and dataset in one enormous system. It means establishing which information is authoritative, who owns it and how connected systems should reference it.
IBM distinguishes between a system of record and a source of truth. A system of record maintains authoritative information within a particular domain, while a source of truth creates a consistent view across systems and data sources.
For an IPD project, room and asset information may be maintained in a structured database connected with BIM authoring tools, document platforms and reporting systems.
The goal is not simply centralized storage. It is consistent, traceable and reusable information that supports decisions throughout the project.
What should an IPD shared data environment contain?
The exact structure varies by project, but it usually includes several connected information types.
Room requirements
Room requirements describe what each space must support, including dimensions, finishes, accessibility, technical services and functional needs. They should be structured so they can be compared, updated and validated.
Room data sheets
Room Data Sheets provide a systematic way to record the architectural, engineering, furniture, equipment and functional requirements associated with a space.
They are valuable communication tools, but static PDF exports should not become the primary source of information. Ideally, Room Data Sheets should be generated from current structured data so that project teams do not have to determine which document is the latest version.
Learn more about how Room Data Sheets support data-driven design.
Asset and equipment information
A shared environment should connect assets and equipment with the rooms, systems or locations in which they are required. Relevant information can include:
- Asset type and classification
- Quantity and location
- Dimensions and clearance requirements
- Electrical and mechanical services
- Performance requirements
- Installation and commissioning status
- Documentation and handover requirements
This helps project teams verify that the design provides the space, services and conditions required by each asset.
Structured asset information can also support procurement, cost tracking and reliable handover to operational systems. Explore how dRofus manages room, equipment and asset information.
BIM-linked information
BIM provides important spatial and geometric information, but the model should not become another disconnected source.
Room identifiers, asset properties and agreed requirements should be connected with the corresponding spaces and objects in the model. This allows teams to compare what was requested with what has been designed.
It also helps identify missing rooms, incomplete asset data, mismatched parameters and other inconsistencies earlier in the project.
dRofus supports bidirectional integrations with Revit, Archicad and IFC, enabling structured project data to remain connected with the developing design.
Responsibilities and change history
Shared access does not mean everyone should be able to change everything.
A strong information environment should make it clear who owns each type of information, who can approve changes, what changed, why it changed and which teams are affected.
This creates accountability and reduces reliance on email chains and meeting notes.
Validation and reporting
Validation should take place throughout the project rather than being treated as a final exercise before handover.
Teams should be able to compare model information with agreed requirements, identify incomplete records and report directly from current project data.
Room Data Sheets, equipment lists, dashboards and status reports should all reflect the same underlying information. This supports continuous design validation and helps teams identify discrepancies while there is still time to resolve them.
How does an IPD shared data environment work?
A practical workflow can be built around five principles.
1. Structure requirements early
Room, asset and system requirements should be recorded as structured data from the start. This makes the information easier to search, compare, validate and report.
2. Assign clear ownership
Each information type needs an owner and a controlled process for making changes. A room requirement may be proposed by the owner, developed with consultants and approved through an agreed workflow.
3. Connect requirements with BIM
Room and asset records should be linked with the corresponding spaces and objects in the model. This gives teams a practical way to compare the developing design against the project brief.
4. Update the primary record once
When an approved requirement changes, the authoritative record should be updated rather than copied into another spreadsheet. Connected reports and room data sheets can then use the revised information.
5. Validate continuously
Design and asset information should be checked throughout the project. Continuous validation helps teams resolve gaps before construction, commissioning or handover.
A shared data environment is more than a shared folder
A shared drive can make files accessible, but access alone does not create a source of truth.
A project may still contain several versions of the same room information, even when they are stored in the same folder.
A true shared data environment should provide:
- Structured information rather than document-only content
- Unique identifiers for rooms and assets
- Controlled permissions and responsibilities
- Change history and traceability
- Connections with BIM and other project systems
- Validation against agreed requirements
- Reporting from current data
- Defined handover requirements
The key question is not simply, “Can everyone open the file?” It is, “Can everyone rely on the information?”
Shared data environment and CDE: what is the difference?
The terms overlap and should not be treated as completely separate concepts.
Under ISO 19650, a Common Data Environment, or CDE, is the agreed source of information for a project or asset and the managed process used to collect, manage and distribute project information. This information can include documents, models, schedules and structured databases.
A specialist room and asset data platform can operate as part of, or alongside, the broader CDE workflow. Its particular role is to manage granular information such as room requirements, asset specifications, identifiers, model properties and validation status.
The two approaches are therefore complementary. A project may use a broader CDE for information exchange and approvals while using a specialist platform to manage detailed room, requirement and asset data.
How dRofus supports shared data in IPD projects
dRofus is a planning, data management and BIM collaboration platform that helps owners and project teams manage room requirements, asset information and BIM-linked data in one controlled environment.
Teams can use dRofus to:
- Centralize room and space requirements
- Maintain room data sheets from structured information
- Connect rooms and assets with BIM workflows
- Validate model data against agreed requirements
- Manage equipment and asset information
- Track changes throughout the project
- Generate reports from current data
- Preserve structured information for handover
By connecting requirements, rooms, assets, BIM information and reporting, dRofus helps IPD teams work from aligned information while continuing to use specialist applications.
Building the information foundation for integrated delivery
IPD brings project participants together around shared objectives. A shared data environment gives them a reliable information foundation for making decisions.
It reduces dependence on disconnected spreadsheets and manual reconciliation while creating a clear link between the owner’s requirements, the developing design and the assets eventually delivered.
Learn why IPD projects need a shared source of truth for room and asset data.
FAQs
What is an IPD shared data environment?
In this context, it is a controlled digital environment that allows owners, designers, contractors and trade partners to work from aligned project information, including room requirements, asset data, BIM information and validation results.
Is it the same as a shared drive?
No. A shared drive stores files, while a shared data environment also provides structure, ownership, permissions, traceability and connections between related information.
What is the difference between a CDE and a shared source of truth?
A CDE is an agreed source and managed workflow for collecting, managing and distributing project or asset information. A shared source of truth describes the goal of giving stakeholders a reliable and consistent view of authoritative data. A specialist room and asset data platform can contribute to both.
When should it be established?
Ideally during early planning and briefing, so room, asset and handover requirements can develop alongside the design rather than being reconstructed later.