BIM Standards and Information Management Frameworks

Introduction and context

Building Information Modelling (BIM) is not simply the production of three-dimensional models. It is a managed method for creating, exchanging, approving, using and preserving information about a built asset. The value of BIM depends on whether the right information reaches the right person, in the right form, at the right time, with an appropriate level of reliability and security.

Standards and information management frameworks provide the rules that make this possible. They define responsibilities, information requirements, approval processes, naming conventions, exchange formats, security controls and lifecycle procedures. Without such rules, project participants may create technically impressive models that are inconsistent, duplicated, difficult to exchange or unsuitable for construction and operations.

The ISO 19650 series is the principal international framework for managing information over the life cycle of a built asset using BIM. It does not prescribe one software package, one modelling method or one national classification system. Instead, it establishes principles and processes that organisations adapt to their contractual, legal, technical and national context.

This chapter explains the main principles of ISO 19650, the relationship between international and national requirements, openBIM guidance, information management functions, naming and status conventions, and the movement of information through the asset life cycle.

Learning objectives

By the end of this chapter, a student should be able to:

1. Explain the purpose and scope of the ISO 19650 information management framework.
2. Distinguish organisational, project and asset information requirements.
3. Describe the functions of appointing party, lead appointed party and appointed parties.
4. Explain the role of the common data environment (CDE).
5. Interpret naming conventions, metadata and status or suitability codes.
6. Compare proprietary workflows with openBIM approaches.
7. Relate information management processes to design, construction, handover and operation.
8. Identify governance, security, legal and quality risks in BIM information management.

1. Information management as a construction discipline

Information management is the controlled handling of information so that it is identifiable, accessible, trustworthy, secure and useful. In construction, information may include drawings, specifications, schedules, models, asset registers, geospatial data, photographs, inspection records, commissioning certificates and operation manuals.

A BIM model is therefore one information container among several. A model may represent geometry and relationships, but it does not automatically prove that an object is approved, installed, tested or suitable for operation. Those meanings must be established through requirements, metadata, approvals and documented processes.

A useful distinction is between:

• Data: recorded values, such as a door width of 900 mm.
• Information: data interpreted in a context, such as a 900 mm fire-rated door serving an escape route.
• Knowledge: understanding that supports a decision, such as selecting a door that satisfies accessibility, fire and maintenance requirements.

BIM information management concerns the whole chain from requirement to decision. It includes information definition, production, checking, authorisation, exchange, storage, security and eventual disposal or retention.

Information quality dimensions

Information quality is multidimensional. Important dimensions include:

Quality is not equivalent to having a highly detailed model. Excessive detail can increase production cost, obscure important information and create false confidence. The appropriate information is determined by the information requirements and the decisions that the information must support.

2. The ISO 19650 framework

ISO 19650 is an international series for information management using BIM. Its central idea is that information should be managed according to clearly stated requirements and a defined delivery process.

The principal parts include:

National standards may adopt or supplement these parts. For example, a country may publish a national annex, implementation guidance, terminology guidance or procurement requirements. Students must therefore distinguish the international framework from the national documents and contractual protocols that apply on a particular project.

Core principles

The ISO 19650 approach is based on several connected principles:

1. Information requirements drive production. Information is produced because it supports a business, project, operational or regulatory need.
2. Responsibilities are allocated. Each information requirement has an owner, producer, reviewer and approval route.
3. Information is produced collaboratively. Teams coordinate their work rather than treating models as isolated deliverables.
4. Information is exchanged through controlled processes. A file is not necessarily an approved deliverable merely because it has been uploaded.
5. Information states are explicit. Work in progress, shared, published and archived information must be distinguishable.
6. Security is considered throughout the life cycle. Sensitive information is managed according to assessed risks.
7. The framework is technology-neutral. It specifies outcomes and processes rather than requiring a particular vendor or platform.

The information requirement hierarchy

The framework uses a hierarchy of requirements. Terminology may vary slightly in national guidance, but the logic is consistent.

Organisational information requirements (OIR) express the information needed to support an organisation’s strategic and operational objectives. Examples include information needed for a facilities management system, capital investment decisions, statutory reporting or portfolio performance.

Project information requirements (PIR) describe information needed to make decisions during a particular project. Examples include planning submissions, design coordination, cost planning, construction sequencing, safety reviews and commissioning.

Asset information requirements (AIR) specify information needed to operate and maintain an asset. Examples include equipment identifiers, maintenance intervals, warranties, manufacturers, replacement parts and inspection records.

These requirements inform the appointment and production processes. The appointing party may translate requirements into an exchange information requirement (EIR) or equivalent project information specification. The EIR defines what is required, when it is required, in what format, at what level of information need, and subject to which acceptance criteria.

The phrase level of information need is preferable to treating “level of development” as a universal measure. It considers the required geometric, alphanumeric and documentary information for a specific purpose. A construction trade may need fabrication-level geometry for one component, while an operator may need reliable maintenance data but not detailed fabrication geometry.

Roles and appointments

ISO 19650 describes information management responsibilities in relation to appointments:

• Appointing party: the organisation requiring information, often the client, owner or asset operator.
• Lead appointed party: the organisation appointed to lead and coordinate information delivery for a defined scope, such as a main contractor or design consultant.
• Appointed party: an organisation delivering information under an appointment, such as an architect, structural engineer, specialist contractor or supplier.
• Task team: individuals or groups carrying out a defined information production activity.

The lead appointed party does not necessarily create all information. Its important function is to coordinate the delivery team, establish the delivery plan, review capability and manage information exchanges within its scope.

3. Information management during the delivery process

A typical delivery process begins before appointment and continues through mobilisation, collaborative production, information exchange and close-out.

Figure: A simplified information delivery sequence with feedback from exchanges into later requirements and decisions.

Pre-appointment and tender

The appointing party identifies information requirements, appoints information management responsibilities and defines exchange milestones. Tenderers demonstrate capability, capacity, experience, proposed methods, software competence and ability to meet the requirements. The proposed delivery approach should be assessed as a management and technical response, not merely as a promise to provide a 3D model.

Mobilisation

After appointment, the parties confirm the detailed information delivery strategy. The team establishes:

• the master information delivery plan and task information delivery plans;
• responsibility matrices;
• software versions and exchange procedures;
• coordinate systems and measurement units;
• model federation and clash review procedures;
• naming conventions and metadata requirements;
• review, approval and acceptance criteria;
• security controls and access permissions;
• the CDE workflow and file retention rules.

Collaborative production

Each task team develops information in a controlled work-in-progress environment. The team checks its own work before sharing it. Coordination then occurs between relevant disciplines. Issues should be recorded with a clear description, location, responsible party, priority and required response. A coordination meeting should not be the only record of an issue.

Exchange, acceptance and archive

At an exchange milestone, information is checked against defined requirements. Acceptance is not simply a technical upload. It may involve validation of file structure, naming, geometry, data fields, spatial coordination, regulatory compliance and contractual deliverables. Accepted information is published for the intended use. Superseded or final information is archived according to the project and organisational retention rules.

4. The common data environment

A common data environment is an agreed source of information for a project or asset. It may be implemented through one platform or through interoperable systems connected by controlled procedures. The term describes a managed process and information state model, not just a cloud folder.

A commonly used CDE workflow contains four states:

1. Work in progress (WIP): information being developed by its authoring team and not yet available for general project use.
2. Shared: information made available to other authorised teams for coordination or review.
3. Published or authorised: information approved for a defined purpose, such as construction, procurement or operation.
4. Archive: a record of superseded, final or historically significant information retained for traceability.

Movement between states should require defined checks and permissions. A shared model may be suitable for coordination but unsuitable for construction. Similarly, a published drawing may be authorised for a particular activity while still subject to revision for another purpose.

A CDE should support version control, revision history, access permissions, audit trails, metadata, issue management, transmittals or exchange records, and recovery procedures. It should also define who can create, review, approve, supersede and delete information.

5. Naming conventions, metadata and classification

Naming conventions make information findable and reduce ambiguity. A project should publish a naming standard before significant production begins. It should specify permitted characters, field order, separators, abbreviations, codes, revision rules and examples.

A typical structured file name might contain fields such as:

Project-Originator-Volume-Level-Type-Role-Number-Status-Revision

For example:

RIV-ARC-B01-02-M3-A-0105-S1-P02

The meaning of each field must be defined by the project. In this illustrative example, RIV may identify the project, ARC the originator, B01 a building or volume, 02 a level, M3 a model or information type, A an architectural role, 0105 a unique number, S1 a status or suitability code, and P02 a revision. These interpretations are not universal and must not be assumed without the project standard.

Good naming conventions should be:

• unique enough to distinguish information containers;
• predictable and machine-readable;
• short enough to use consistently;
• based on controlled code lists;
• aligned with folder structures and metadata;
• tested against real project examples.

Naming alone is not a substitute for metadata. Metadata can record author, date, discipline, location, security classification, status, revision, related asset identifier and approval history. Classification systems can group elements by function, construction type, work breakdown or asset management purpose. A national classification system may be required by a client or public authority.

6. Status, suitability and revision codes

Status codes communicate how information may be used. Suitability codes communicate the intended purpose or permitted use of an information container. Common codes in some UK-derived workflows include S0 for work in progress, S1 for suitable for coordination, S2 for suitable for information, S3 for suitable for review and comment, and S4 for suitable for stage approval. Codes such as A, B, C and D may then be used for authorised construction, manufacture or record purposes in particular project systems.

These codes are not a universal ISO list. A project must define its own code set or adopt the applicable national convention. The critical principle is that every code has one documented meaning, one permitted use and one accountable approval route.

A revision code identifies a change to an information container. For example, a project may use P01, P02 for preliminary revisions and C01, C02 for contractual or construction revisions. Again, the exact convention is project-specific.

A status code should not be confused with:

• a revision identifier;
• a model maturity or level of detail;
• a document approval signature;
• a construction progress percentage;
• a legal acceptance of design responsibility.

Clear separation of these meanings prevents a common risk: users treating a file as approved merely because it has a high revision number or has been placed in a shared folder.

7. OpenBIM and interoperability

OpenBIM is a collaborative approach based on open standards and vendor-neutral workflows. It seeks to reduce dependence on a single software ecosystem and allow information to remain usable when participants use different applications.

Important openBIM technologies and guidance include:

• IFC (Industry Foundation Classes): an open data schema and exchange format for representing built-asset information.
• BCF (BIM Collaboration Format): a method for exchanging coordination issues, viewpoints, comments and status without necessarily exchanging the whole model.
• IDS (Information Delivery Specification): a machine-readable approach for defining and checking information requirements for IFC-based exchanges.
• buildingSMART Data Dictionary: a service intended to support common terminology and classification across systems.
• COBie: a structured approach to delivering asset and facilities information, often used for handover, although its implementation must follow project requirements.

Open standards do not guarantee perfect interoperability. Translating information between systems may cause loss of object properties, relationships, classifications, parametric behaviour or appearance. IFC exports should therefore be tested using representative project objects, not accepted solely because an export file exists.

Interoperability has at least three dimensions:

1. Technical interoperability: systems can exchange and read data.
2. Semantic interoperability: exchanged terms and properties have the same meaning.
3. Process interoperability: organisations agree when, why and how information is exchanged.

The third dimension is often overlooked. A technically valid IFC file is not useful if the receiving party does not know its purpose, approval status, coordinate system or required checks.

8. National BIM requirements and procurement

National BIM requirements translate broad principles into local practice. They may be expressed through government mandates, public procurement rules, national standards, implementation guides, classification systems, information security regulations or contract amendments.

A project team should identify, before production:

• which national standards are contractually incorporated;
• whether public-sector information requirements apply;
• the required classification and measurement conventions;
• language, units and coordinate reference systems;
• planning, building-control and safety obligations;
• records, privacy and cybersecurity requirements;
• permitted software and open exchange formats;
• handover and facilities-management data requirements.

National requirements should not be copied mechanically from another country. A naming system, status code or procurement template developed for one jurisdiction may conflict with local law, terminology or contractual practice. The correct approach is to map national requirements to the project’s information requirements and appointments.

9. Lifecycle information processes

Information changes in purpose as the asset moves through its life cycle.

Strategic definition and briefing

The owner identifies business objectives, performance outcomes, operational constraints, site information and initial information requirements. Decisions at this stage influence later information cost and quality. Poorly defined requirements can result in either missing information or unnecessary modelling.

Design and procurement

Design information supports option evaluation, coordination, planning approval, cost estimation and procurement. Information must be sufficiently reliable for its intended decision. A conceptual massing model should not be presented as fabrication information.

Construction

Construction information supports sequencing, temporary works coordination, logistics, procurement, fabrication, installation, inspection and change management. Field changes must be recorded and incorporated into appropriate as-installed or record information. A model is not “as-built” merely because construction has finished.

Handover and commissioning

Handover information may include equipment registers, serial numbers, warranties, commissioning results, certificates, operation manuals, maintenance schedules, spaces, systems and responsible parties. The acceptance criteria should be defined early so that data is collected during delivery rather than reconstructed at the end.

Operation and maintenance

Operational information supports maintenance, energy management, space management, compliance, refurbishment and emergency response. The operational information model should contain information that facilities personnel can use, not simply a copy of every design file. Information should be linked to work-order, building-management and asset-management systems where appropriate.

Alteration, refurbishment and disposal

During alteration, existing information is surveyed, verified and updated. At disposal, the organisation may need records of hazardous materials, demolition sequencing, recycling, waste documentation and legal retention. Security-sensitive information may require controlled destruction rather than indefinite storage.

10. Governance, security and responsibility

BIM governance establishes who makes information decisions, how compliance is measured and how disputes are resolved. Governance should address information ownership, intellectual property, liability, data protection, cyber risk, retention and auditability.

Security-minded information management is especially important for critical infrastructure, hospitals, transport facilities, schools and high-profile buildings. Threats may include unauthorised disclosure of security layouts, malicious alteration, ransomware, loss of personal data and uncontrolled access by former project participants.

Practical controls include:

• risk-based information classification;
• least-privilege access;
• multi-factor authentication;
• secure sharing and encryption where appropriate;
• controlled removal of users;
• backup and recovery testing;
• logging and audit review;
• incident reporting;
• supplier and platform due diligence;
• separation of public, operational and security-sensitive information.

Ethically, information managers should avoid overstating model accuracy, concealing known coordination issues or using automated outputs without verification. Responsibility remains with competent professionals even when checking tools, generative AI or automated rule systems are used.

11. Technology and AI in information management

Cloud CDE platforms, model-checking software, laser scanning, mobile field applications, digital twins and AI-assisted classification can improve information workflows. AI may help identify missing properties, detect apparent clashes, classify photographs or search large document collections.

However, automated results are probabilistic or rule-dependent. They may produce false positives, miss context, reproduce bias in training data or expose confidential information through inappropriate external services. Any AI-assisted workflow should define the approved tool, data boundaries, human review, evidence trail and accountability. AI should support, not replace, professional judgement and contractual approval.

12. Illustrative case: municipal library project

This is a fictional illustrative case.

Background

A municipality commissions a new public library containing reading rooms, a digital learning centre and a small archive. The client intends to operate the building with a computer-aided facilities-management system. The architect, structural engineer, services engineer, contractor and specialist suppliers use different software platforms.

Problem

The tender documents request “a BIM model at handover” but do not define asset data, naming conventions, exchange formats or approval states. During construction, the client receives several models with inconsistent room names and equipment identifiers. The facilities team cannot reliably link air-handling units to warranties and maintenance intervals.

Analysis

The problem is not primarily a lack of modelling skill. It is a failure to define information requirements and acceptance criteria. The project has no agreed AIR, no data dictionary, no responsibility matrix and no controlled CDE workflow. A final file upload is being confused with a useful operational information deliverable.

Approach and solution

The client develops an AIR specifying required fields for maintainable assets, including unique identifier, location, system, manufacturer, model, serial number, warranty expiry, maintenance interval and commissioning status. The team defines a project naming standard, a classification approach and an open exchange requirement using IFC for selected exchanges. A responsibility matrix identifies which supplier provides each field and who verifies it.

The CDE is configured with WIP, shared, published and archive states. Asset data is checked at procurement, installation and commissioning milestones rather than only at handover. BCF issues are used to record missing or conflicting data. The facilities manager participates in review meetings to confirm that the information supports actual maintenance activities.

Outcome

At handover, the client receives an accepted operational information set linked to the facilities-management system. The geometry is not identical across every authoring platform, but the required asset identifiers and relationships are consistent. Missing data is visible through an exception report rather than being hidden in a visually attractive model.

Learning points

1. Information requirements should be defined before detailed production.
2. Operational users must influence handover requirements.
3. Open formats are useful only when semantics and processes are also agreed.
4. Data validation should occur progressively.
5. A CDE controls states and responsibilities; it is not merely file storage.

13. Challenges and limitations

Standards improve consistency but do not remove professional judgement. Common challenges include:

• organisations interpreting the same terms differently;
• excessive or poorly prioritised information requirements;
• inconsistent software exports;
• weak ownership of data fields;
• late appointment of the facilities team;
• inadequate training and role clarity;
• contractual ambiguity about model reliance and liability;
• duplicated data entry between models and business systems;
• resistance to new workflows;
• cyber threats and platform outages.

A mature implementation therefore begins with business outcomes, defines proportionate requirements, tests workflows on realistic examples and measures whether information supports decisions. Compliance should not become a paperwork exercise disconnected from project value.

Best-practice checklist

Before information production begins, the project team should be able to answer:

• What decisions will each information exchange support?
• Who requires the information and who is accountable for producing it?
• What geometric, alphanumeric and documentary information is necessary?
• Which national standards and contractual protocols apply?
• How will information be named, classified, reviewed and approved?
• What do each status, suitability and revision code mean?
• Which open formats are required and how will they be tested?
• How will information be secured, retained and archived?
• How will operational users verify the handover data?
• How will changes, issues and rejected information be recorded?

Chapter Summary

BIM standards convert modelling activity into a controlled information management process. ISO 19650 provides an international framework based on requirements, allocated responsibilities, collaborative production, controlled exchanges and lifecycle use. Organisational, project and asset information requirements establish why information is needed; appointments and delivery plans establish who produces and manages it.

The common data environment provides managed information states, version control, permissions, review and traceability. Naming conventions, metadata, classification and status codes make information identifiable and usable, but their meanings must be defined by the applicable project or national standard. OpenBIM approaches, including IFC, BCF and IDS, support interoperability, although technical exchange must be accompanied by semantic and process agreement.

National BIM requirements influence procurement, classification, security, data protection and handover. Information must be managed from strategic definition through design, construction, commissioning, operation, alteration and disposal. Effective governance protects information quality, security and professional accountability. The central lesson is that a BIM deliverable is valuable only when it satisfies a defined need, has a known status, can be trusted and can be used by its intended recipient.

Key Terms

Appointed party: Organisation delivering information under an appointment.

Appointing party: Organisation requiring information from other parties.

Asset information requirements (AIR): Requirements for information needed to operate and maintain an asset.

BCF: OpenBIM format for exchanging coordination issues and related viewpoints.

Common data environment (CDE): Agreed source and managed process for collecting, controlling and distributing project or asset information.

Exchange information requirement (EIR): Specification of information required for a defined exchange, including purpose, format, timing and acceptance criteria.

IFC: Open, vendor-neutral schema and exchange format for built-asset information.

Information management: Controlled creation, checking, exchange, storage, use and disposal of information.

Information requirement: Statement of information needed to support a decision, activity or objective.

Level of information need: Proportionate definition of required geometric, alphanumeric and documentary information.

Lead appointed party: Organisation coordinating information delivery for an appointed scope.

Metadata: Data describing an information container, object or document.

OpenBIM: Collaborative approach using open standards and vendor-neutral workflows.

Organisational information requirements (OIR): Information needed to support organisational objectives and operations.

Project information requirements (PIR): Information needed to support decisions during a project.

Status or suitability code: Code indicating the intended use or state of an information container.

Task team: Group carrying out a defined information production activity.

Work in progress (WIP): Information being developed by its authoring team and not yet generally shared.

Review Questions

5 Short Answer Questions

1. What is the purpose of ISO 19650 in a BIM project?
2. Distinguish between OIR, PIR and AIR.
3. What is the function of a common data environment?
4. Why must status codes be defined by the project or applicable national standard?
5. Name two openBIM technologies and state their principal uses.

5 Long Answer Questions

1. Explain the ISO 19650 information delivery process from requirements definition through acceptance and archive.
2. Discuss how naming conventions, metadata and classification contribute to information quality.
3. Compare technical, semantic and process interoperability, using a construction example.
4. Explain how information requirements change between design, construction, handover and operation.
5. Discuss governance and security responsibilities in a CDE-based BIM workflow.

3 Analytical / Application Questions

1. A contractor receives architectural, structural and services models with different coordinate systems, file names and revision labels. Propose a mobilisation and CDE strategy to resolve the problem.
2. A hospital client requests “a complete BIM model” for facilities management. Analyse why this requirement is inadequate and formulate a more useful AIR and acceptance approach.
3. A project team plans to use an AI tool to identify missing equipment data in handover models. Evaluate the technical, ethical and governance controls required before deployment.

Multiple Choice Questions with Answers

Question 1

Which ISO 19650 information requirement primarily concerns information needed to operate and maintain an asset?

A. Organisational information requirement

B. Project information requirement

C. Asset information requirement

D. Task information requirement

Correct Answer: C. Asset information requirement

Question 2

Which CDE state normally contains information being developed by its authoring team and not yet generally shared?

A. Work in progress

B. Published

C. Archive

D. Authorised construction

Correct Answer: A. Work in progress

Question 3

What is the principal purpose of BCF?

A. To store structural calculations

B. To exchange coordination issues and viewpoints

C. To replace all IFC geometry

D. To calculate project cash flow

Correct Answer: B. To exchange coordination issues and viewpoints

Question 4

Which statement about status or suitability codes is correct?

A. Their meanings are universally fixed by ISO 19650

B. They always indicate the percentage of construction complete

C. They should have documented meanings and permitted uses for the project

D. They are identical to revision identifiers

Correct Answer: C. They should have documented meanings and permitted uses for the project

Question 5

Which of the following best describes IFC?

A. A vendor-neutral schema and exchange format for built-asset information

B. A project payment certification procedure

C. A security password standard

D. A construction site safety permit

Correct Answer: A. A vendor-neutral schema and exchange format for built-asset information

Question 6

A file has been uploaded to a shared folder but has not passed the project’s review criteria. What is the most appropriate conclusion?

A. It is automatically approved for construction

B. Its high revision number makes it authoritative

C. It may be available for coordination but is not necessarily authorised

D. It must be archived immediately

Correct Answer: C. It may be available for coordination but is not necessarily authorised

Question 7

Which interoperability dimension concerns whether exchanged terms have the same meaning?

A. Technical interoperability

B. Semantic interoperability

C. Physical interoperability

D. Financial interoperability

Correct Answer: B. Semantic interoperability

Question 8

Why should operational information requirements be defined before handover?

A. To ensure every design object has maximum geometric detail

B. To allow required asset data to be collected and checked progressively

C. To eliminate the need for commissioning

D. To prevent the use of open formats

Correct Answer: B. To allow required asset data to be collected and checked progressively

Question 9

Which control best supports least-privilege information security?

A. Giving every project participant administrator access

B. Allowing former users to retain access until project close

C. Providing users only the permissions required for their role

D. Removing all audit logs after each exchange

Correct Answer: C. Providing users only the permissions required for their role

Question 10

What is the main risk of treating a visually detailed model as automatically suitable for facilities management?

A. The model may contain insufficient or unreliable operational data

B. The model will always have too many correct asset identifiers

C. The model cannot contain geometry

D. The model will necessarily be in an open format

Correct Answer: A. The model may contain insufficient or unreliable operational data