BIMe Initiative

44. Information Management Cycle


Information Management Cycle v0.5 (Full-size Image - Older version)

Updated Jan 21, 2018: This high-level conceptual model describes the Information Management Cycles that Structured Project Information pass through [1]. Each Cycle includes three Information Management States, separated by varied Information Management Activities conducted by specialised Information Management Actors:

Information Management States

The three states describe how Structured Project Information can be experienced as either:

[1] Information Requirements: project specifications, protocols or similar that identify what needs to be generated by project stakeholders. Information Requirements can be represented as a set of Document Uses, Model Uses and Data Uses.

[2] Digital Deliverables: digital simulations of physical objects and how/when they’ll be constructed or fabricated. Digital Deliverables can either be documents (in digital format -e.g. CAD drawings or a PDF furniture lists), models and/or data sets.

[3] Physical Assets: information embodied within real world objects similar to whole facilities, a building, mechanical system, heating unit, or a single pump.

Information Management Activities

The transitions between these Information Management States are represented as either forward or reverse activities. Forward Cycle Activities refer to the actions executed to cross from one state to the next; while Reverse Cycle Activities refer to the measurements made to examine one state against its preceding one. Sample activities [2] are provided below:

  • Forward Execution Activities from [1] to [2]: the activities typically conducted during a project’s Design Phase which includes the planning and specifications sub-phases (e.g. drafting, drawing, detailing, and modelling); and
  • Reverse Measurement Activities from [2] to [1]: the activities necessary to verify or validate digital deliverables against information requirements (e.g. checking floor areas in a BIModel against a client’s spatial requirements).
  • Forward Execution Activities from [2] to [3]: all the activities typically conducted during the Construction Phase which includes construction planning and commissioning (e.g. laying floors, mounting ceilings, and painting walls); and
  • Reverse Measurement Activities from [3] to [2]: the activities necessary to test and confirm physical outputs against digital deliverables (e.g. checking the placement of duct hangers on site against relevant models or mechanical shop drawings).
  • Forward Execution Activities from [3] to [1]: all the activities typically conducted during the Operation Phase which includes management, maintenance and decommissioning (e.g. cleaning rooms, repairing down-pipes, replacing roof tiles); and
  • Reverse Measurement Activities from [1] to [3]: the activities necessary to capture data pertaining to a physical asset or to monitor the performance of a physical system (e.g. data capture through laser scanning and data monitoring through sensors).

Note: the three Key Information Activities (Prepare [P], Manage [M], and Utilise [U]) will be explained in a future model.

Information Management Actors

The Information Management Activities separating Information Management States are conducted by actors which are either humans and/or computers. There are three main actors who operate throughout the Information Management Cycle:

  • Design Information Management Actors: executing the transition from Information Requirements to Digital Deliverables and measuring (e.g. verifying or validating) how well Digital Deliverables match with Information Requirements;
  • Construction Information Management Actors: executing the transition from Digital Deliverables to Physical Assets and measuring (e.g. testing or confirming) how well Physical Assets match with Digital Deliverables; and
  • Operation Information Management Actors: executing actions applied to Physical Assets (e.g. operating, maintaining and decommissioning). Also these actors can either (a) measure - e.g. capture or monitor - how well a Physical Asset matches with the Information Requirements covering the asset (within the same Information Management Cycle), or (b) measure one or more Physical Assets in order to generate new Information Requirements within a new Information Management Cycle.

Actors may overlap and replace each other. Depending on the current state of technologies, processes and policies within a market, two or even one Information Management Actor may be able to complete all execution and measurement activities across an Information Management Cycle [3].



The following colleagues have provided improvement suggestions to version 0.1 of this model: AProf. Sheryl Staub-French, AProf. Julie Jupp, Ms. Marzia Bolpagni, and Mr. Victor Roig Segura. Thank you to all.



[1] Each Information Management Cycle has a nominal start (e.g. information covering the design of a new physical asset) and a nominal end (e.g. information decimated through the demolition of an asset). However, it is possible and even probable that the same information would persist over a number of Cycles (e.g. through iterative renovation of the same physical asset).

[2] Activities are a subset of ‘Relations’ within the Conceptual BIM Ontology.

[3] This model is part of the BIMe Initiative Integrated Information Platform project

43. Product Development Diagram


BIMe Initiative Product Development Diagram (Updated Jan 21, 2018full size image)

This diagram illustrates the process of delivering a BIMe Initiative Product (a Published Guide or a Software Application): a Top-Level Project must be first launched. Each Top-Level Project typically includes both existing components (e.g. a taxonomy or a classification) and new components. Existing components are (a) selected from the Knowledge Object Library, a public resource available through New components (e.g. a framework or a software module) are (b) generated by BIMe Members through Micro Projects. Once completed and validated, all components are (c) packaged into a new BIMe Product. Once tested and verified, the new product is (d) released through the Product Library (a webpage on and all newly generated components are (e) added to the Knowledge Object Library for future reuse. As opposed to the Knowledge Object Library and the Product Library, which are both publicly available resources, the generation of new components and end products are conducted within the Project Space (wiki pages, chat rooms and physical meetings) which are accessible to BIMe Members and invited international collaborators.

To understand Conceptual Components (also referred to as Conceptual Constructs), please review the Conceptual Hierarchy and - as an example - how components populate the Research Continuum. Also, for more information about BIMe Initiative products, projects, and how they are managed, please refer to 103in BIMe Initiative Projects.

42. BIMe Initiative Knowledge Structure

image from www.bimframework.infoBIMe Initiative Knowledge Structure (full size image)

This model represents the Knowledge Structure which the BIMe Initiative ( is reliant upon to deliver interconnected software applications, guides, conceptual structures and learning materials. The Knowledge Structure is composed of five complementary Knowledge Sets:

  • KS1 Knowledge Foundations represents all the research supporting the BIMe Initiative;
  • KS2 Knowledge Blocks represents the modular language developed/used by the BIMe Initiative to define inputs, processes and outputs;
  • KS3 Knowledge Tools represents all the digital and analogue tools/templates used to conduct knowledge acquisition, engineering and sharing;
  • KS4 Knowledge Workflows represents all repeatable procedures for knowledge acquisition and service delivery; and
  • KS5 Knowledge Views identifies the varied ways the BIMe Initiative activities and deliverables can be represented and communicated.

The Knowledge Sets and their subsets form the bases for all BIMe Initiative Projects (refer to 103in); organise the activities of the BIMe Initiative Network (refer to 104in); and allow the development of an expansive Knowledge Object Library.