ISO 19650 Explained for Indian Civil Engineers

If you have just received your first BIM tender, ISO 19650 is the document everybody will keep referencing — and the document nobody will explain to you. Bid responses talk about "OIR", "AIR", "EIR", "BEP", "CDE" and "appointed parties". Tender clauses cite "Cl. 5.4 of Part 2" or "the ISO 19650-2 information delivery cycle". By page three of any BEP template, you wonder if you are reading the same language as the rest of the project.

This article walks through ISO 19650 in plain English for Indian civil engineers who have never used it before. We'll cover what each part of the series is for, the vocabulary you actually need, and the workflow that ties it all together. Read this once and you will be able to follow any ISO 19650 conversation, BEP, or tender from then on.

What ISO 19650 is — and what it isn't

ISO 19650 is the international standard for managing information through the entire lifecycle of a built asset using Building Information Modelling (BIM). It is a process standard — it tells you HOW to manage information, not WHAT BIM tool to use. The standard does not care whether you use Revit, ArchiCAD, Tekla, or Bentley. It cares about who produces what information, when, in what format, and how it gets accepted, exchanged, and archived.

ISO 19650 is the international successor to the UK's PAS 1192 series (2007–2014). It replaces the older "BIM Level 2" terminology with a more rigorous, internationally agreed framework. India has not published an Indian Standard on BIM as of early 2026, so Indian projects reference ISO 19650 directly when they want a BIM standard at all.

The series has five published parts, each addressing one phase or aspect of information management. We'll walk through each one.

Part 1 — Concepts and Principles (ISO 19650-1:2018)

Part 1 is the vocabulary and conceptual foundation document. Every other part of the series assumes you have read it. Read this one first. The most important concepts:

The information requirements hierarchy: OIR → AIR → PIR → EIR

This four-letter acronym chain is the spine of ISO 19650. Memorise it.

OIR (Organisational Information Requirements) — what the asset owner's BUSINESS needs to know. Top of the pyramid. Drives everything below. Example: a hospital owner needs to know energy consumption per square metre for ESG reporting.
AIR (Asset Information Requirements) — what information is needed to OPERATE and maintain the asset day-to-day. Derived from OIR. Example: equipment make, model, warranty dates, preventive maintenance frequency.
PIR (Project Information Requirements) — what information is needed to DELIVER the project. Derived from OIR + AIR. Time-bound to construction milestones. Example: cost forecast, design approval status at each gateway.
EIR (Exchange Information Requirements) — what each appointed party (contractor, consultant) must HAND OVER at each delivery milestone. The contractual deliverable list. Derived from PIR. Example: architect issues IFC + DWG + room schedule at Concept Design stage.

Each layer is derived from the one above. EIR is what an appointed party actually contracts to deliver. If you are a structural consultant being asked to write a BIM Execution Plan, the EIR is the document you respond to.

Three contractual roles

ISO 19650 defines exactly three roles in the information management process:

Appointing Party — the CLIENT who issues the appointment. This is the building owner, developer, government department, or anybody else paying for the work. (In old PAS 1192 vocabulary this was called "Employer".)
Lead Appointed Party — the principal contractor or lead consultant. Directly contracted to the appointing party. Owns the project's BIM execution overall and the post-appointment BEP.
Appointed Party — anybody (consultant, contractor, subcontractor, supplier) contracted directly or indirectly to deliver work. There can be many appointed parties on one project.

These are CONTRACTUAL roles, not job titles. A "BIM Manager" is a job title; an "Appointed Party" is a contractual relationship. Don't confuse them.

The Common Data Environment (CDE)

The CDE is the single trusted location where all project information lives during delivery and operation. Every information container — model file, drawing, schedule, report, RFI, clash issue — must live in the CDE. ISO 19650 does not specify which CDE platform to use — it is up to each project — but it does specify the workflow.

Every information container in the CDE must be in exactly one of four states at any time:

Work in Progress (WIP) — being authored. Author has full read/write; nobody else can touch it.
Shared — checked, suitability assigned, pushed for collaboration. Read-only to the rest of the project team.
Published — authorised by the appointing party as a contractual deliverable. Read-only.
Archived — preserved as a record of the project. Read-only forever.

Movement between states is one-way (with rejection exceptions). This four-state model is non-negotiable. If your "CDE" is just a Dropbox folder, you are not ISO 19650 compliant.

Part 2 — Delivery Phase (ISO 19650-2:2018)

Part 2 is the most-cited part of the series and the one you will work with day to day during a project. It specifies the eight activities of the information delivery cycle and the documents (BEP, MIDP, TIDP) you need to produce.

The 8 activities of the delivery cycle

Assessment and need — the appointing party identifies what information they actually need. Outputs: OIR, AIR, PIR drafts, project need statement.
Invitation to tender — the appointing party issues the tender pack with the EIR and the requirements for a pre-appointment BEP.
Tender response — the prospective lead appointed party submits a pre-appointment BEP demonstrating capability, plus a mobilisation plan.
Appointment — contracts are signed. The lead appointed party produces the post-appointment BEP and the first draft of the Master Information Delivery Plan (MIDP).
Mobilisation — the CDE is set up and TESTED with sample uploads. Training happens. Information production methods are confirmed. This step is the single most skipped step in the entire standard. Don't skip it.
Collaborative production of information — appointed parties produce information containers and move them through the WIP → Shared → Published states.
Information model delivery — at each milestone, information is verified against acceptance criteria and authorised by the appointing party.
Project close-out — the project information model is archived. The Asset Information Model is handed over to the operations team (Part 3 takes over).

Activities 5–7 RUN ITERATIVELY — they repeat once per project gateway. A typical project might go through this cycle four to six times (Concept, Schematic, Tech Design, Construction Documents, Construction, Close-out).

BEP, MIDP, TIDP — the three planning documents

BEP (BIM Execution Plan) — the contract document that says HOW BIM will be done on this specific project. Two versions: pre-appointment (in tender response, short, demonstrates capability) and post-appointment (signed after award, detailed, 30–50 pages).
MIDP (Master Information Delivery Plan) — the master schedule of all information deliverables across all appointed parties. Owned by the lead appointed party. A live spreadsheet, not a snapshot.
TIDP (Task Information Delivery Plan) — the schedule of deliverables for ONE appointed party / ONE task. Multiple TIDPs roll up into the MIDP.

If you are a structural consultant, you produce a TIDP for your scope. The lead appointed party aggregates your TIDP with the architect's TIDP, the MEP consultant's TIDP, etc., into the project MIDP.

Part 3 — Operational Phase (ISO 19650-3:2020)

Part 3 takes over where Part 2 leaves off. Once an asset is built and in operation, the Project Information Model (PIM) handed over from delivery becomes the Asset Information Model (AIM). Part 3 governs how the AIM is maintained, updated, and used during operations.

Part 3 mirrors the eight-activity structure of Part 2 but for the operational phase. The key new concepts are trigger events (planned or unplanned changes that require an information update — refurbishments, equipment replacement, regulatory changes) and the integration of the AIM with FM/CAFM/CMMS systems.

Part 3 is less widely adopted than Part 1 and Part 2 — most BIM projects in India still focus on the delivery phase and treat operations as out of scope. This is changing slowly as more clients realise the long-term value of BIM is in operations, not delivery.

Part 4 — Information Exchange (ISO 19650-4:2022)

Part 4 was published in 2022 to fill a gap left by Parts 1–3: how do you actually verify that an information container meets the agreed requirements? Part 4 specifies the quality criteria for information exchanges, the verification process, and the metadata required on every container for traceability.

The most important practical contribution of Part 4 is acceptance criteria. Every information delivery should have SMART acceptance criteria — specific, measurable, achievable, relevant, time-bound. Vague criteria like "delivered to high quality" are worthless and lead to disputes. Part 4 forces you to define exactly what "acceptable" means.

Part 4 is the most recent and least widely implemented part. If you can include Part 4 acceptance criteria in your BEP from day one, you are ahead of most Indian BIM projects.

Part 5 — Security-Minded Approach (ISO 19650-5:2020)

Part 5 is mandatory if your project involves sensitive information — defence, critical national infrastructure (power, water, transport, data centres), government facilities, or any asset where uncontrolled disclosure could enable attack or harm.

Part 5 introduces a structured sensitivity assessment process and two key documents: the Built Asset Security Strategy (BASS) and the Security Management Plan (SMP). It specifies vetting requirements for personnel, CDE access controls, and breach response procedures.

Many projects that should follow Part 5 don't, simply because the team assumes it doesn't apply. RUN A SENSITIVITY ASSESSMENT for any government, defence, or critical-infrastructure project before you decide. If your project is sensitive, treating Part 5 as optional is a serious risk.

Putting it together: a worked example

Let's walk through a simple worked example. Imagine you are a structural consultant in India bidding to deliver the structural BIM scope on a metro station project.

Activity 1 (Assessment and need) — the metro authority (appointing party) identifies that they need a BIM-enabled design to enable future digital twin applications.
Activity 2 (Invitation to tender) — they issue a tender pack with an EIR. The EIR specifies: ISO 19650-2:2018 process; IFC 4.3 Reference View export at each milestone; LOD 350 structural elements at Tech Design stage per BIMForum 2024; Uniclass 2015 classification; Autodesk Construction Cloud as the CDE.
Activity 3 (Tender response) — your firm prepares a pre-appointment BEP. It is short — 8 pages. It states how you will deliver each EIR clause, names your project BIM Manager and Information Manager, lists your software stack, summarises a recent comparable project, and outlines a mobilisation plan.
Activity 4 (Appointment) — your firm wins the structural scope. You produce a post-appointment BEP — 35 pages — covering federation strategy, naming convention, model authoring rules, clash protocol, software versions, and the structural TIDP.
Activity 5 (Mobilisation) — you spend two weeks setting up your Revit templates, joining the project CDE, configuring file naming, and uploading a sample model to confirm everything works. Mobilisation is signed off in a kick-off meeting before production starts.
Activity 6 (Collaborative production) — over three months, your team produces structural Revit models, exports IFC weekly to the CDE, attends bi-weekly federation/clash meetings.
Activity 7 (Information model delivery) — at the Tech Design milestone, your TIDP deliverables are uploaded as Shared, then verified against the EIR acceptance criteria, then authorised as Published. You move to the next iteration.
Activity 8 (Project close-out) — at handover, your final published containers are archived. The integrated PIM is handed to the operations team as the AIM under Part 3.

That's ISO 19650 in practice. The same eight activities apply on every project, regardless of scale or sector — what changes is the LOD, the software stack, the team size, and the milestones.

Common ISO 19650 mistakes on Indian projects

Skipping mobilisation (Activity 5) — the most common project killer. The CDE, naming, templates, and validation must be tested BEFORE production starts.
Vague EIR acceptance criteria — leads to disputed deliverables and missed milestones. Push back on any EIR with "delivered to high quality" type clauses.
Treating BEP as a tender annex — the post-appointment BEP is a LIVE document. Update it at every milestone.
Conflating Information Manager with BIM Coordinator — they are different ISO 19650 roles. The Information Manager enforces the BEP; the BIM Coordinator runs federation and clash.
Using "Dropbox CDE" — a shared folder is not a CDE. The CDE must enforce information container states (WIP/Shared/Published/Archived) and naming convention.
Skipping Part 3 — handover to operations is a contractual obligation under ISO 19650-2 Activity 8. Don't treat it as optional.
Skipping Part 5 — every government, defence, or critical-infrastructure project should run a sensitivity assessment before deciding.

Next steps

If you are new to ISO 19650, here is the practical learning path:

Read ISO 19650-1:2018 (Part 1) — concepts and principles. About 50 pages. Available from iso.org or BIS for purchase.
Read ISO 19650-2:2018 (Part 2) — delivery phase. About 90 pages.
Download a sample BEP template — UK BIM Framework (ukbimframework.org) publishes free templates that map directly to ISO 19650.
Practise on your next project — even on a non-mandated project, applying the WIP/Shared/Published/Archived workflow gives you the muscle memory.
Get certified — buildingSMART Professional Certification is internationally recognised and increasingly required for senior BIM roles in India.

ISO 19650 is not a magic spell. It is a structured way of managing information that prevents the chaos most BIM projects fall into. The Indian projects that follow it well are usually the ones with international consultants who insist on it. The Indian projects that don't are usually the ones that struggle with disputes, rework, and missed milestones.

If you take one thing from this article, take this: read Part 1 first. Until you have the vocabulary, every conversation about ISO 19650 will sound like a foreign language. Once you have the vocabulary, every BIM tender becomes much less mysterious.

Sources and further reading

ISO 19650-1:2018 catalog page: iso.org/standard/68078.html
ISO 19650-2:2018 catalog page: iso.org/standard/68080.html
UK BIM Framework templates and guidance: ukbimframework.org
buildingSMART International: buildingsmart.org
InfraLens BIM Handbook section — start with BIM Concepts & Terminology and walk through the ISO 19650 process at ISO 19650 Information Delivery Process