Frequently Asked Questions
Common questions about the proposed ISO 19650 terminology changes and how they may affect information management practices.
Why is ISO 19650 terminology being reviewed?
Terminology is being reviewed to unify terms across ISO 19650 Parts 2 and 3, improve international translation, and reduce confusion for organizations implementing the standards.
Are these terminology changes final?
No. The terminology proposals form part of the Draft International Standards and remain subject to public consultation and international consensus.
Does this remove BIM from ISO 19650?
No. The proposed changes focus on clarifying terminology rather than removing BIM or its application.
Why replace “BIM execution plan”?
The proposed change to information production plan aims to avoid method-specific terminology and instead focus on the activity of producing information – whether BIM is used or not.
Who decides which terms are adopted?
Final decisions on terminology are made by the ISO subcommittee and national standards bodies following the consultation process.
Does “information production” mean creating new information only?
Not necessarily. In this context, “information production” is used to describe the set of activities that result in information being produced to meet requirements and milestones. These activities are included within step 8 of the proposed process.
Will ISO 19650 terminology changes affect templates and processes?
Potentially, yes. If terms like “BIM execution plan”, “delivery team”, and “information exchange requirements” are replaced in the final publication, organizations may want to update their document titles, role labels, and template wording to stay aligned – even if the underlying intent of the outputs remains similar.
What is the difference between an “information management strategy” and an “information management plan”?
In simple terms, a strategy is typically organizational and longer-term (setting direction and principles), while a plan is typically project-level and appointment-specific (setting out how information will be managed for that project, by whom, using which processes and resources).
Is “information production requirements” the same thing as EIR (Exchange Information Requirements)?
It’s broadly the same intent – defining what information needs to be produced, when, and to what level/format – but the proposed term aims to be clearer and more consistent with the unified process language (focusing on production rather than exchange).
Why change “delivery team” to “information production team”?
“Delivery team” can be interpreted as a contractual or construction-focused term. Information production team is intended to describe the function more precisely: the appointed parties responsible for producing information to meet the requirements and milestones.
What are “information production milestones” and how do they relate to delivery dates?
They are checkpoints by which information should be produced to support decisions and downstream activities. In practice they may align with (or sit ahead of) contractual delivery dates, but the wording emphasises that the milestone is about having the information ready – not just sending it.
How should I interpret “project” vs “asset-related project” in the proposed wording?
The idea is to avoid “project” being understood only as design/construction. An asset-related project is about creating, refurbishing, or maintaining an asset, while a project (in the information management sense) can exist at any stage to manage and produce information for that asset.
What should organizations do now if the terminology is still in draft?
Avoid rushing to rename everything. Instead, track the proposed changes, note which internal documents/templates would be affected, and prepare a light-touch mapping (old term → proposed term). That way you can update quickly if the wording is confirmed.
How can I comment on the ISO 19650 draft revisions?
Use the public consultation route provided by your national standards body (the mechanism varies by country). If you’re involved through an industry group, you can also coordinate comments so they reflect practical impacts on implementation, training, and international consistency.