BIM Concepts, Terminology and Information Structures

Introduction and Context

Building Information Modelling (BIM) is a managed method for creating, organising, exchanging and using information about a built asset throughout its life cycle. Although BIM commonly involves three-dimensional digital models, it is not simply computer-aided drafting or visualisation. Its central concern is the reliability, structure, ownership and use of information by people and organisations involved in planning, design, construction, operation, maintenance and eventual decommissioning.

A BIM-enabled project links graphical information—such as walls, doors, beams and mechanical equipment—with non-graphical information, including classification codes, specifications, performance data, manufacturer details, maintenance requirements and approval status. The value of BIM therefore depends not only on model geometry but also on information quality, information governance and the suitability of information for a defined decision.

For construction professionals, understanding BIM terminology and information structures is foundational. Poorly defined information requirements can produce models that appear sophisticated but fail to support estimating, coordination, procurement, construction planning or facility management. Conversely, a relatively simple model can be highly valuable when its information is accurate, appropriately detailed and delivered at the correct time.

Learning Objectives

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

1. Explain the purpose and structure of a federated BIM model.
2. Distinguish information containers, model uses, geometry, attributes and classification.
3. Apply the concept of level of information need to project deliverables.
4. Explain model progression and information quality across project stages.
5. Analyse an applied BIM information-management problem and recommend suitable controls.
6. Recognise professional, contractual, ethical and governance implications of BIM information.

1. BIM as an Information Management Approach

BIM can be understood through three connected dimensions:

• Representation: how an asset is described, including geometry and properties.
• Process: how information is created, reviewed, approved, exchanged and used.
• Governance: how responsibility, permissions, standards, security and accountability are managed.

A model element is not merely a shape. A door object, for example, may contain width, height, fire rating, acoustic rating, hardware set, manufacturer, cost code, installation date and maintenance instructions. These properties allow the same information to support design review, quantity extraction, compliance checking, procurement and facilities management.

BIM is therefore best treated as an information system embedded within project workflows. Software is necessary in many BIM processes, but software alone does not create BIM. A project may use advanced software and still have weak BIM practice if information requirements are unclear, data are duplicated, naming is inconsistent or responsibility is not assigned.

2. Essential BIM Terminology

Model

A model is a structured digital representation of an asset or part of an asset. It may contain geometry, properties, relationships, classifications and documentation. A model can represent existing conditions, proposed design, construction status or operational conditions.

Information

Information is processed and contextualised data that supports understanding or decision-making. A value such as “90” is ambiguous without a property name, unit and context. “Door leaf width = 900 mm” is more useful because its meaning is defined.

Data

Data are recorded facts, observations or values. Data may be graphical, numerical, textual, spatial or relational. BIM practice converts data into usable information through structure, context and validation.

Element and object

An element is a component or system of an asset, such as a slab, pipe, luminaire or air-handling unit. An object is a digital representation of an element, normally containing geometry and properties.

Metadata

Metadata is information about information. Examples include author, creation date, revision, approval status, source, classification, security level and intended use.

Attribute or property

An attribute is a characteristic associated with an object. Attributes may be numerical, textual, Boolean, categorical or date-based. Examples include thermal transmittance, fire resistance, material, supplier and inspection status.

Relationship

A relationship connects information objects. A door may be related to a wall, a room, a fire compartment, a specification section and a maintenance task. Relationships often provide more value than isolated property values because they support analysis and traceability.

Information requirement

An information requirement states what information is needed, by whom, when, in what format and for what purpose. Common levels include organisational information requirements, project information requirements and exchange information requirements, depending on the adopted standard and contractual arrangement.

Common Data Environment

A Common Data Environment (CDE) is an agreed system and workflow for collecting, managing, reviewing, sharing and distributing project information. It is not simply a file-sharing folder. A CDE should provide controlled states, revision history, permissions, audit trails and agreed naming and status conventions.

Information container

An information container is a named, persistent set of information that can be retrieved from a file, database or other system. It may be a model, drawing, schedule, specification, point cloud, photograph, report or spreadsheet. The concept is important because BIM information is broader than a single three-dimensional file.

Federated model

A federated model is a coordinated combination of separate discipline or purpose-specific models that remain individually authored and managed. Architectural, structural, civil, mechanical, electrical and plumbing models may be linked or aggregated for coordination without being permanently merged into one authoring file.

Interoperability

Interoperability is the ability of systems, organisations and processes to exchange information and use it meaningfully. It includes technical compatibility, semantic consistency and organisational agreement. A file may be technically transferable but still not interoperable if classifications, units or property meanings are inconsistent.

3. Federated Models and Model Coordination

Large projects are usually divided among organisations and disciplines. A single integrated authoring model would create problems of file size, responsibility, permissions, software compatibility and commercial ownership. Federation addresses these problems by keeping discipline models separate while allowing them to be reviewed together.

A typical federated arrangement includes:

Federation does not eliminate coordination responsibility. The project team must establish coordinate systems, levels, grids, units, file naming, model origin, exchange frequency, clash tolerances and approval procedures. Each author remains responsible for the content of their model, while the coordination team is responsible for identifying and managing interfaces.

A federated model supports several forms of coordination:

1. Geometric coordination: identifying physical conflicts, such as a duct intersecting a beam.
2. Spatial coordination: checking access zones, plant-room clearances and circulation.
3. Systems coordination: examining how structural, architectural and services systems interact.
4. Temporal coordination: linking components to construction activities and sequences.
5. Information coordination: checking whether required attributes, classifications and documents are present.

A clash detection report does not automatically identify a construction problem. Some intersections are intentional, such as a pipe entering a tank. Others may be geometrically separate but operationally incompatible, such as an electrical panel located where its door cannot open. Human judgement and discipline knowledge remain essential.

4. Information Containers and the Common Data Environment

An information container must have an identifiable purpose and controlled status. Typical status categories distinguish work in progress, shared information, published information and archived information. The exact labels vary by project standard, but the principle is constant: users must know whether information is being developed, issued for coordination, approved for a defined purpose or retained for record.

A robust information-container convention normally addresses:

• unique identifier and project code;
• originator and discipline;
• location or system reference;
• type and role of the container;
• revision and version;
• status or suitability code;
• security classification;
• author, checker and approver;
• issue date and intended recipient.

For example, a structural model issued for coordination should not be mistaken for an approved construction model. A model’s status is as important as its content.

The CDE also supports a controlled information lifecycle:

1. Information is authored in a work-in-progress environment.
2. It is checked internally for completeness and technical correctness.
3. It is shared for interdisciplinary coordination.
4. Comments and issues are recorded and resolved.
5. Approved information is published for an authorised purpose.
6. Superseded information is archived without being silently deleted.

This process improves traceability and reduces the risk that teams construct from obsolete information.

5. BIM Model Uses

A model use is a planned method of applying BIM to achieve a defined project or operational outcome. Model uses should be described by purpose, responsible party, required inputs, process, output and acceptance criteria.

Common model uses include:

• existing-condition modelling;
• design visualisation;
• design authoring;
• spatial coordination and clash detection;
• code and regulatory checking;
• quantity take-off and cost planning;
• construction sequencing and 4D planning;
• fabrication and installation planning;
• site logistics and temporary works planning;
• energy or environmental analysis;
• asset handover;
• facilities management and maintenance planning.

A model use should not be selected merely because software can perform it. For example, automated quantity take-off may be unsuitable if model objects are incomplete, duplicated or incorrectly classified. A model use is successful only when its outputs are sufficiently reliable for the decision being made.

The information needed for a model use can be expressed as an input-output relationship:

Model use = purpose + required information + responsible process + usable output + acceptance criteria

This is a conceptual framework rather than a mathematical equation. It reminds the team that a model use is a managed activity, not a software feature.

6. Geometry, Attributes and Classification

Geometry

Geometry describes form, size, position, orientation and spatial relationships. It may include two-dimensional lines, three-dimensional solids, surfaces, point clouds or parametric representations. Geometry is necessary for visualisation, spatial coordination and some quantity calculations, but geometric detail should be proportionate to the intended use.

A highly detailed object can create large files and slow performance without improving decisions. Conversely, insufficient geometry may prevent coordination or installation planning. Geometry should therefore be specified by its purpose rather than by an assumption that “more detail is always better.”

Attributes

Attributes describe non-geometric characteristics. They may include:

• material and product type;
• dimensions and performance values;
• classification and coding;
• manufacturer and supplier;
• cost and procurement information;
• fire, acoustic and environmental properties;
• installation and commissioning data;
• warranty and replacement information;
• inspection and maintenance requirements.

Attributes require definitions. “Fire rating” should identify whether it refers to integrity, insulation, smoke control or another criterion. Units, permissible values and evidence sources should also be stated.

Classification

Classification organises objects, systems, spaces or activities into defined categories. It improves searching, quantity aggregation, reporting, cost planning and interoperability. Classification systems may be based on elements, systems, products, spaces, work results or functions.

Classification is not the same as naming. A name may describe an object informally, while a classification assigns it to a controlled category with a defined meaning. A project should select a classification system appropriate to its jurisdiction, sector and information requirements. Mixing systems without a mapping strategy can produce duplicate or contradictory codes.

Geometry–attribute–classification relationship

Consider a fire door. Its geometry may represent its position, swing and dimensions. Its attributes may record fire resistance, acoustic performance, hardware and supplier. Its classification may place it within a door, opening or fire-protection category. A complete information object combines these dimensions and links them to documents and responsibilities.

7. Level of Information Need

The level of information need defines the amount and quality of information required for a particular purpose at a particular time. It replaces vague instructions such as “provide a detailed model.” The level should be sufficient for the intended decision, but not excessive.

It is useful to distinguish three components:

1. Geometrical information: size, shape, position, orientation and spatial relationships.
2. Alphanumerical information: properties, classifications, identifiers and performance data.
3. Documentation: specifications, certificates, manuals, photographs, warranties and other linked records.

The required level varies by stage and use. During early concept design, approximate massing and functional information may be sufficient. During fabrication, exact dimensions, connection details, tolerances and product data may be required. During operations, geometry may be less important than asset identifiers, locations, maintenance intervals and warranty information.

The level of information need should be defined through measurable criteria, such as:

• required properties and units;
• acceptable accuracy or tolerance;
• required classification codes;
• expected model scale or geometric representation;
• evidence or source required for an attribute;
• delivery date and responsible party;
• permitted omissions and assumptions.

More information is not automatically better. Unused information increases authoring effort, storage, checking requirements and the risk of inconsistency. The professional objective is “enough reliable information for the intended use.”

8. Model Progression and Information Quality

Model progression describes how information develops from early assumptions to verified design, construction and operational records. It should not be interpreted as a universal ladder in which every object must pass through identical levels. Different objects progress at different rates according to decisions, procurement and construction sequencing.

A practical progression may be described as:

• Concept: approximate form, location and system intent.
• Developed design: coordinated dimensions, systems and principal properties.
• Technical design: information suitable for procurement, approvals and construction planning.
• Fabrication or installation: specialist detail, interfaces, tolerances and sequencing.
• As-constructed: verified record of what was installed.
• Operation: information linked to inspection, maintenance, performance and change management.

Model progression is not merely adding detail. It includes replacing assumptions with verified information, resolving interfaces, recording decisions and maintaining consistent relationships.

Information quality can be assessed through several dimensions:

Quality assurance should combine automated checks and professional review. Automated checks can identify missing properties, invalid values, duplicate identifiers and spatial conflicts. Human review is needed for design intent, constructability, safety, contextual meaning and unusual conditions.

9. Applied Case: Federated BIM for a University Laboratory Building

This is an illustrative case.

Background

A university commissions a four-storey laboratory building. The project includes complex ventilation, specialist gases, high electrical demand and strict maintenance requirements. The architect, structural engineer, services engineer, laboratory specialist and main contractor use different authoring systems.

Problem

Early coordination meetings reveal that the services model contains ducts with inconsistent sizes and incomplete fire-stopping information. The architect’s room names do not match the facilities team’s room database. Several equipment items appear in the model but have no manufacturer, maintenance or commissioning data. The client is concerned that the final handover will be visually impressive but operationally unusable.

Analysis

The project team identifies three related problems:

1. Federation is occurring, but model responsibilities and exchange requirements are unclear.
2. The model contains geometry without the attributes required for procurement and operations.
3. Different naming and classification practices prevent reliable information exchange.

The team maps each intended model use to information requirements. Coordination requires geometry, system identity and clearance zones. Procurement requires product identifiers, performance data and quantities. Facilities management requires asset identifiers, location, warranty, maintenance intervals and linked documentation.

Approach and solution

The team establishes a CDE workflow and appoints information managers for each discipline. A responsibility matrix identifies who creates, checks and approves each information field. The project adopts a common room and asset naming convention and defines permitted units and classification codes.

The federated review is divided into discipline coordination, services-access review, fire and life-safety review, and operational information review. Automated rules identify missing asset identifiers and invalid property values. The facilities team reviews representative equipment records before the project proceeds to full population of the data.

The team also defines the level of information need by stage. Early design uses approximate equipment zones; procurement requires selected product data; handover requires verified installed assets and commissioning records. This prevents the project from demanding operational information before products are selected.

Outcome

The revised process reduces duplicate modelling, improves issue tracking and allows the client to receive a structured asset register linked to locations and documents. More importantly, the project team can distinguish coordination information from approved construction information and from verified as-constructed information.

Learning points

• Federation requires governance, not merely model aggregation.
• Model uses determine the information that must be created.
• Attributes and classifications are as important as geometry.
• Operational information should be planned early but verified at the appropriate stage.
• Quality checks must combine rules-based validation with expert judgement.

10. Professional, Ethical and Governance Considerations

BIM information can affect safety, cost, legal responsibility and public use of buildings. Professionals must not present unverified model content as fact. A model should communicate assumptions, limitations and status clearly.

Important governance issues include:

• responsibility for authoring and checking information;
• contractual reliance on models and linked documents;
• intellectual property and permitted reuse;
• protection of personal, security-sensitive or critical-infrastructure data;
• retention and auditability of decisions;
• cyber-security of CDE platforms and connected building systems;
• accessibility for users with different technical capabilities;
• responsible use of automated checking and artificial intelligence.

Artificial intelligence can assist with classification, object recognition, anomaly detection, document search and predictive maintenance. However, AI-generated outputs may contain errors, embedded bias or unsupported assumptions. Human professionals remain responsible for verifying outputs, preserving source evidence and determining whether an automated recommendation is suitable for safety-critical or contractual decisions.

11. Best-Practice Principles

1. Begin with decisions and model uses, not software capabilities.
2. Define information requirements before authoring begins.
3. Specify geometry, attributes, classifications and documents separately.
4. Use a federated structure where discipline responsibility and file control matter.
5. Establish a CDE with clear status, revision and approval workflows.
6. Use consistent coordinates, units, naming and classification.
7. Apply the minimum sufficient level of information need.
8. Validate information throughout the project rather than only at handover.
9. Record assumptions, approvals, issues and changes.
10. Make operational requirements visible during design but demand verified data at the correct stage.
11. Combine automated checks with professional judgement.
12. Protect information according to its sensitivity and intended use.

Chapter Summary

BIM is an information-management approach that connects digital representation, project processes and governance. A BIM model includes geometry, attributes, classifications, relationships and linked documents. Federated models allow separate discipline models to remain under their authors’ control while supporting coordinated review. Information containers provide a controlled way to manage models, drawings, specifications, schedules and other records within a Common Data Environment.

Model uses define why information is created and what outputs are required. Geometry describes form and location; attributes describe characteristics and performance; classification organises information into consistent categories. The level of information need specifies the amount and quality of geometry, alphanumeric data and documentation required for a particular purpose and time. Model progression involves increasing certainty, coordination and verification rather than simply adding visual detail.

Information quality depends on accuracy, completeness, consistency, timeliness, validity, traceability, accessibility and security. Effective BIM practice therefore requires clear requirements, disciplined exchange processes, technical validation and professional judgement. These concepts provide the foundation for later study of BIM execution planning, interoperability, coordination, 4D and 5D applications, asset information and digital delivery.

Key Terms

BIM: A managed approach to creating, exchanging and using information about built assets.

Federated model: A coordinated combination of separate discipline or purpose-specific models.

Information container: A named, persistent set of project or asset information.

Common Data Environment: An agreed system and workflow for managing project information.

Model use: A planned application of BIM to achieve a defined outcome.

Geometry: Digital description of form, size, position and spatial relationships.

Attribute: A characteristic or property associated with an object.

Classification: Organisation of objects or information into controlled categories.

Metadata: Information describing the origin, status, author or characteristics of information.

Interoperability: The ability of systems and organisations to exchange and meaningfully use information.

Information requirement: A statement of information needed, by whom, when and for what purpose.

Level of information need: The amount and quality of information required for a defined use and stage.

Model progression: Development of model information from assumptions toward coordinated and verified records.

Information quality: The degree to which information is accurate, complete, valid, consistent and usable.

Clash detection: Identification of potential conflicts between model elements or systems.

Work in progress: Information being developed by its author and not yet shared as an authorised project deliverable.

As-constructed information: Verified information representing what was actually installed or built.

Asset information: Information needed to operate, maintain and manage an asset.

Review Questions

Short Answer Questions

1. What is a federated model, and why is it useful on multidisciplinary projects?
2. Distinguish between geometry, attributes and classification.
3. What is the purpose of a Common Data Environment?
4. Define level of information need.
5. Name four dimensions of information quality.

Long Answer Questions

1. Explain how a federated BIM structure supports coordination while preserving discipline responsibility.
2. Discuss the relationship between model uses and information requirements, using two examples.
3. Explain why more geometric detail does not necessarily produce a more useful BIM model.
4. Describe a controlled information lifecycle within a Common Data Environment.
5. Discuss the importance of classification and consistent attributes for procurement and facilities management.

Analytical / Application Questions

1. A contractor receives architectural, structural and services models with different origins, units and naming conventions. Analyse the risks and propose an information-management response.
2. A client requests “a highly detailed handover model” but has not defined operational uses. Develop a set of questions and requirements that would establish an appropriate level of information need.
3. During coordination, an automated clash tool reports 300 intersections. Explain how the project team should classify, investigate and prioritise these issues rather than treating every report as an equivalent construction defect.

Multiple Choice Questions with Answers

Question 1

Which statement best defines a federated model?

A. A single file permanently merged from all disciplines

B. A coordinated combination of separate discipline models

C. A model containing only construction cost data

D. A two-dimensional drawing archive

Correct Answer: B. A coordinated combination of separate discipline models

Question 2

Which item is an example of an attribute?

A. The spatial position of a wall

B. The three-dimensional shape of a beam

C. The fire-resistance rating of a door

D. The coordinate origin of a project

Correct Answer: C. The fire-resistance rating of a door

Question 3

What is the primary purpose of a Common Data Environment?

A. To replace all professional design decisions

B. To provide controlled management and exchange of information

C. To ensure every discipline uses identical software

D. To eliminate the need for model checking

Correct Answer: B. To provide controlled management and exchange of information

Question 4

Which combination best describes the level of information need?

A. Only the number of model elements

B. The required geometry, alphanumeric information and documentation

C. The maximum possible model detail

D. The software version used to author a model

Correct Answer: B. The required geometry, alphanumeric information and documentation

Question 5

Which quality dimension asks whether information can be traced to its source and revision?

A. Traceability

B. Geometry

C. Visualisation

D. Parametricity

Correct Answer: A. Traceability

Question 6

Why should model uses be defined before extensive modelling begins?

A. To determine the information required for the intended outcome

B. To ensure that all models contain identical objects

C. To prevent the use of classifications

D. To make every model visually realistic

Correct Answer: A. To determine the information required for the intended outcome

Question 7

Which activity is most directly associated with information federation?

A. Combining discipline models for coordinated review

B. Deleting all discipline-specific files

C. Converting every object into a photograph

D. Removing non-graphical information

Correct Answer: A. Combining discipline models for coordinated review

Question 8

Which statement about model progression is correct?

A. It only means adding more geometric detail

B. It involves increasing certainty, coordination and verification

C. It ends when the design model is first created

D. It requires every object to progress at exactly the same rate

Correct Answer: B. It involves increasing certainty, coordination and verification

Question 9

A door has geometry, a fire-rating property and a classification code. What does this illustrate?

A. The separation of BIM from information management

B. The combination of representation, attributes and classification

C. A model containing geometry only

D. A CDE approval workflow

Correct Answer: B. The combination of representation, attributes and classification

Question 10

Which approach is most appropriate when an automated clash tool reports an intersection?

A. Treat every intersection as a construction error

B. Ignore all reported intersections

C. Review the intersection in context and determine whether it is intentional or problematic

D. Delete the objects involved

Correct Answer: C. Review the intersection in context and determine whether it is intentional or problematic