Alftek delivers ISO 19650-aligned information management on Qatar BIM projects — standardised naming, a common data environment (CDE) workflow, and clear production/approval responsibilities, so every deliverable is consistent, traceable and audit-ready from LOD 100 through LOD 500.
Get a Free ISO 19650 ConsultationGovernment-linked developments, mega-projects and increasingly private developments across Qatar now expect information management aligned to ISO 19650 — the international standard for managing BIM information across a project's lifecycle. That means a defined BIM Execution Plan (BEP), consistent file and container naming, a controlled common data environment (CDE), and clear approval workflows between all disciplines.
Headquartered at Alfardan Centre on Grand Hamad Street in Doha and operating since 2018, Alftek builds ISO 19650 alignment into every project from day one, rather than retrofitting it — so your information stays consistent, auditable and ready for handover to the client or facility owner.
Information management built into the project, not bolted on afterward.
Project-specific BEPs defining roles, responsibilities, standards and the information delivery plan before modeling starts.
Structured CDE processes for work-in-progress, shared, published and archived information states.
Consistent file, container and model-element naming so information stays findable and unambiguous across teams.
Architecture, structure and MEP delivered on the same information-management standard, ready for clash detection and coordination.
Explore BIM Services →ISO 19650 is a multi-part standard, and most confusion about it comes from treating it as one document. Each part governs a different stage of an asset's life, and on a live project you are usually working to one or two of them at a time.
| Part | Covers | When it applies |
|---|---|---|
| Part 1 | Concepts and principles — the vocabulary and framework the rest builds on | Reference throughout; not itself a set of requirements |
| Part 2 | Delivery phase of assets — the information-management process during design and construction | The part most project teams work to day to day |
| Part 3 | Operational phase — managing asset information once the building is in use | Handover onward; the bridge into CAFM and FM |
| Part 4 | Information exchange — checking and assuring the quality of what is exchanged | At every defined exchange point |
| Part 5 | Security-minded approach to information management | Sensitive, government-linked or critical-infrastructure assets |
The mechanism at the centre of ISO 19650 is a chain of requirements running from what the client ultimately needs, down to what each delivery team actually produces. Most projects that describe themselves as "ISO 19650 aligned" but struggle in practice have broken this chain somewhere — usually by never writing the requirements down at the top.
What the owning organisation needs to know to run its business. This sits above any single project and is the reason the rest of the chain exists.
What information is needed to operate and maintain the asset once it is handed over. Defining this early is what prevents the familiar situation where a project produces beautiful models that the FM team cannot use.
What the client needs from this specific project to make its decisions at each key stage — the link between business need and project deliverable.
The precise specification issued to the delivery team: what information, in what format, to what standard, at which exchange points. The EIR is where ISO 19650 becomes contractually real.
The delivery team's answer to the EIR — how they will meet it, with what resources, software, standards and responsibility matrix. Submitted pre-appointment, then confirmed and maintained once appointed.
The single agreed source of project information, with a defined workflow moving containers through Work in Progress, Shared, Published and Archive states. The CDE is where the standard stops being theory and starts governing daily work.
The CDE workflow is the most practically useful part of the standard, and the easiest to get wrong. Its purpose is to make it unambiguous, at any moment, whether a piece of information can be relied on — and who is responsible for it.
| State | Meaning | Who can rely on it |
|---|---|---|
| Work in Progress | Being developed by one task team; not checked or approved | The authoring team only |
| Shared | Checked, reviewed and approved for use by other task teams | Other delivery teams, for coordination |
| Published | Authorised by the client for a defined purpose | Everyone, for construction or decision-making |
| Archive | Superseded records retained as an audit trail | Reference and dispute resolution only |
Consistent information container naming underpins all of this. Every model, drawing and document carries a structured identifier — project, originator, volume, level, type, discipline and number — so that any file can be located and understood without opening it. It looks bureaucratic on day one and becomes indispensable by the thousandth file.
Full standard adoption on a live project rarely succeeds as a single step. The pragmatic route is to establish the parts that prevent the most rework first, then extend.
Alignment is also a competitive matter. As more Qatar clients — particularly government-linked developers and major contractors — write ISO 19650 requirements into tender documents, the ability to evidence a working information-management process increasingly affects whether a firm is eligible to bid at all.
Information-management discipline applied consistently, from early design through facility handover.
ISO 19650 alignment is designed into the BEP and CDE at project start, not added later.
Design → BIM → FM/CAFM under one roof, so information standards carry through to handover.
Consistent, traceable information that clients and authorities can review with confidence.
Metro & rail, aviation, healthcare, hospitality, high-rise, education and infrastructure.
ISO 19650 is the international standard for managing information over the whole lifecycle of a built asset using BIM. It defines consistent naming conventions, a common data environment (CDE) workflow, and clear responsibilities for producing and approving information.
Yes. Alftek follows ISO 19650-aligned information-management workflows on Qatar projects to ensure consistent, audit-ready BIM deliverables from LOD 100 to LOD 500.
Many Qatar developers, consultants and contractors now require ISO 19650-aligned workflows for design coordination, quantity certainty and facility handover, particularly on mega-projects and government-linked developments. Increasingly it also affects tender eligibility: where the standard is written into tender documents, a firm that cannot evidence a working information-management process may not be able to bid at all.
The CDE is the single agreed source of project information. Information containers move through four defined states — Work in Progress (authoring team only), Shared (checked and available to other task teams), Published (client-authorised for a defined purpose) and Archive (superseded records kept as an audit trail). Its purpose is to make it unambiguous at any moment whether a piece of information can be relied on, and who is responsible for it.
The Exchange Information Requirements (EIR) is issued by the client and specifies what information is needed, in what format, to what standard, and at which exchange points. The BIM Execution Plan (BEP) is the delivery team's response, setting out how they will meet those requirements — with what resources, software, standards and responsibility matrix. The EIR asks; the BEP answers.
They are the upper links in the information requirements chain. Organisational Information Requirements (OIR) are what the owning organisation needs to run its business. Asset Information Requirements (AIR) are what is needed to operate and maintain the asset after handover. Project Information Requirements (PIR) are what the client needs from a specific project to make decisions at each stage. Together they inform the EIR.
The parts most commonly encountered are Part 1 (concepts and principles), Part 2 (delivery phase — the part most project teams work to daily), Part 3 (operational phase), Part 4 (information exchange and quality assurance) and Part 5 (security-minded information management). On a live project you are usually working to one or two at a time.
Yes, though rarely as a single step. The pragmatic route is to establish the elements that prevent the most rework first — a working CDE and a consistent information container naming convention — then extend to the fuller framework. Attempting complete adoption at once on a live project tends to stall delivery.
Alftek is headquartered at Alfardan Centre, 2nd Floor, Grand Hamad Street, Doha, Qatar, and delivers BIM services nationwide including Doha, Lusail, Al Khor and Al Wakrah.
Talk to Alftek's Doha-based BIM team about setting up an ISO 19650-aligned BEP and CDE for your next project. Get a free consultation and a tailored scope and quote.
Request a Free Quote