Aller au contenu principal
DocumentMS

Glossary

Common data environment

Also called: CDE

A common data environment is the agreed single source of information for a project, through which all information is collected, managed and shared. ISO 19650 defines it for construction, along with the status codes that indicate whether information may be relied upon.

Common data environment explained

What it is for

On a project involving a client, designers, contractors and a chain of subcontractors, information is produced by many organisations and consumed by all of them. A common data environment is the agreement that there is one place it lives, so that "the latest drawing" has a single meaning across organisational boundaries.

Suitability status

The mechanism that makes it work. Information carries a status code — work in progress, shared, published, archived — indicating what it may be used for. Something at shared status may be reviewed and coordinated against; only published information may be built from.

This maps closely onto approval state in a document management system, and it is the part that prevents construction from a drawing that was never approved.

Naming

ISO 19650 prescribes a naming convention encoding project, originator, volume or system, level, type and number. It looks bureaucratic and exists because a drawing must be identifiable by someone in another organisation with no access to your folder structure.

Why it generalises

The underlying idea — one agreed source, explicit status indicating fitness for use, and naming that survives leaving the system — applies to any multi-party information exchange. Legal transactions, clinical referral pathways and regulatory submissions all have the same problem.

FAQ

Common data environment: common questions

Does a document management system count as a CDE?

For document-based information, it can, provided it enforces the naming convention and status codes. Projects with significant model coordination usually pair it with a model environment rather than replacing one.

Who owns the CDE on a project?

Normally the client or the party appointed to manage information, and it should be settled at appointment. A CDE with unclear ownership becomes several CDEs.

Une session de 30 minutes avec un ingénieur avant-vente, sur une arborescence et une chaîne d'approbation proches des vôtres — pas un environnement de démonstration générique.