ISO 19650-4: Information Exchange
The standard that defines how information must be packaged, transmitted and received in BIM projects — from naming conventions and metadata to exchange formats and automated validation.
About ISO 19650-4
Published in 2022, ISO 19650-4 specifies the practical requirements for information exchange in BIM projects. The standard precisely defines how information must be packaged, transmitted and received between all parties involved.
It implements the information delivery cycle described in ISO 19650-1 and establishes concrete technical requirements: file naming conventions, mandatory metadata, accepted formats and the validation process.
What is an Information Container?
An information container is any discrete unit of information stored and managed in a CDE: files, models, documents or data sets.
Each container has: unique identifier, revision, status, complete metadata and classification according to the approved system.
Mandatory Metadata
ISO 19650-4 defines a minimum set of metadata that must accompany each information container to ensure traceability and interoperability.
| Metadata Field | Description | Required |
|---|---|---|
| Container ID | Unique identifier of the information container | YES |
| Revision Code | Document version (e.g.: P01, P02, C01) | YES |
| Status/Suitability Code | State and purpose of information (e.g.: S0, S2, S3) | YES |
| Description | Title or content description | YES |
| Author | Responsible person or team | YES |
| Date | Creation or last revision date | YES |
| Format / Type | File type (IFC, PDF, DWG, xlsx) | YES |
| Scale | Representation scale (if applicable) | Recommended |
| Project Code | Unique project identifier | YES |
| Classification Code | Classification according to approved system (Uniclass, etc.) | Recommended |
File Name Structure
Each file receives a standardized name composed of fields separated by hyphens.
Naming Convention Example
PROJ-HEX-ZZ-ZZ-M3-A-21-0001-S2-P01Project
Unique project code (max 8 characters)
Originator
Authoring team code (e.g.: HEXCLOUD → HEX)
Volume & System
Volume/system (ZZ = applicable to all)
Location
Location within the asset (ZZ = global)
Type
Container type (M3 = 3D model)
Role
Discipline (A=Architecture, S=Structural, M=MEP)
Classification
Uniclass 2015 classification code
Number
Unique sequential number (4 digits)
Status
Suitability code (S0–S7, A, B, C, D)
Revision
Revision (P=preliminary, C=contractual)
Exchange Formats
ISO 19650-4 promotes the use of open and interoperable formats to ensure independence from specific platforms.
IFC
Industry Foundation ClassesThe open standard format for BIM model exchange. ISO 16739. Supported by all major BIM platforms.
BCF
BIM Collaboration FormatFormat for communicating issues and comments in the context of BIM models. XML-based.
COBie
Construction Operations Building information exchangeStandard for delivering facilities management information in tabular format (xlsx/xml).
PDF/A
PDF for ArchivingISO 19005 format for long-term document archiving. Guarantees future readability.
GeoJSON
Geographic JSONStandard format for geospatial data. Used for integration with GIS systems and digital maps.
Exchange Process
Eight structured steps from defining requirements to archiving approved information.
Define EIR
Appointing Party issues precise exchange requirements: format, metadata, naming convention, deadline.
Information Production
Task Team creates information containers in the WIP area following all EIR requirements.
Internal Verification
Automated and manual verification: naming convention, formats, metadata completeness, clash detection.
Upload to CDE
Verified containers are uploaded to CDE 19650 Cloud in WIP → Shared state.
Status Change
Lead Appointed Party reviews and changes the status. Information becomes visible to recipients.
Recipient Notification
Recipients receive automatic notification that new information is available for review.
Accept / Reject
Appointing Party evaluates and accepts (Published) or rejects with comments (back to WIP).
Archiving
Previous versions are automatically archived. Approved information becomes the official reference.
Automated Validation
CDE 19650 Cloud automatically validates each information container upon upload, eliminating human errors before information is shared.
Naming Convention
Automated verification of all naming convention fields — project, originator, type, revision.
File Formats
Validation that the file type matches the Type field in the naming convention and EIR requirements.
Metadata Completeness
All mandatory fields must be completed before transition from the WIP area.
Clash Detection
Automated verification of geometric conflicts between IFC models from different disciplines.
Information Exchange Compliant with ISO 19650-4
CDE 19650 Cloud automates naming conventions, validates metadata and manages the entire information exchange cycle in compliance with ISO 19650-4.