Glossary for Part I
1. General and interdisciplinary concepts
1. Information Management in Construction (IMC)
author-defined
the coordinated management of information needs, requirements, production, delivery, assessment and use to support the management of built assets throughout their life cycle.
2. Asset
ISO-aligned
an item, thing or entity that has potential or actual value to an organisation.
Note. In this book, built assets include buildings, infrastructure, facilities, sites and other physical assets within the built environment.
3. Asset Life Cycle
established concept
the sequence of stages in the life of an asset, from its conception through development, operation and eventual end of life.
4. Party
established concept
an organisation, part of an organisation, or other actor that participates in an information-management relationship, process or transaction.
5. Building Information Modelling (BIM)
established concept
the collaborative use of digital information about built assets to support their design, construction, operation and management.
Distinction. BIM provides methods and technologies for working with digital information; IMC provides the management framework governing why, what, when, by whom and how information is required, produced, delivered and used.
6. Management Activity
author-defined
a purposeful activity undertaken to manage an asset, project or organisation and which may create a need for information.
Note. Management activities related to built assets may include investment planning, design management, procurement, construction management, commissioning, operation, maintenance, inspection, compliance management, asset performance assessment, refurbishment, change management and decommissioning.
7. Organisational Management System
established concept
the overall system of organisational governance, responsibilities, processes and management activities within which Information Management is performed as an integrated function.
Note. Information Management contributes to the wider Organisational Management System by establishing and coordinating Information Needs, Requirements, responsibilities, Information Production Standards, Methods and Procedures, relevant information resources, assessments, Decisions, technical enablement and Actual Use.
Distinction. This book does not establish OSIMC or an Organisational Information Framework as a separate canonical methodological entity. A CDE platform or software stack provides technical capabilities, not the entirety of organisational Information Management.
2. Information and the Information Model
8. Information Model
ISO-aligned, extended
a managed federated composition of interrelated Information Containers representing information about a built asset, project or related management context.
Note. An Information Model may comprise Information Containers stored in different systems or locations. Its integrity depends on the persistent identity of its Containers, governed relationships between them, and the controlled composition of their Container Revisions.
9. Project Information Model (PIM)
ISO-aligned, extended
an Information Model that supports the Management Activities of a project. Its scope is shaped primarily by the applicable Project Information Requirements (PIR).
10. Asset Information Model (AIM)
ISO-aligned, extended
an Information Model that supports the continuing management of a built asset. Its scope is shaped primarily by the applicable Asset Information Requirements (AIR).
Note. The PIM and the AIM are distinguished by the Management Activities they support. Project and asset-management activities may overlap in time.
11. Information Container
ISO-aligned, extended
a named set of persistent information with a stable identity, managed as a unit within an Information Model and retrievable from a file, system or application. Its identity persists while its information evolves through governed Working Versions and Container Revisions.
Note 1. Persistent information exists for long enough to require managed identification, governance, versioning or retention. Transient information, such as the immediate result of a search or query, is not an Information Container unless it is deliberately captured and subsequently managed as a persistent information set.
Note 2. An Information Container does not have to correspond to a file. It may be a document, model, dataset, database record, defined part of a file, data point or another persistently retrievable set of information.
Note 3. The persistent Information Container identity is distinct from Revision identity, Working Version and CDE State. Changes in Working Version, Revision, State, Status Code, permitted use, assessment result or Decision do not create a new Information Container identity.
12. Container Revision
author-defined
a controlled governed edition of an Information Container representing its content and governed metadata at a defined point in its evolution.
Note 1. A Container Revision may have multiple governed Working Versions, especially while information is being developed in the In Work state. A Working Version and a Container Revision are both distinct from the persistent Information Container identity.
Note 2. Once formally issued, a Container Revision provides a stable historical reference to the information as it existed at that point. Earlier Revisions are not overwritten or reinterpreted when a later Revision is issued; they remain historically traceable.
Note 3. Revision numbering or coding is defined by the applicable Information Production Standard and is not hard-coded by this methodology.
13. Working Version
author-defined
a governed intermediate version of information within a Container Revision, used to represent controlled development of that Revision before or between formal issue points.
Note 1. Multiple Working Versions may exist within one Container Revision. Not every technical save, autosave or transient edit is a governed Working Version.
Note 2. Working Version numbering or coding is defined by the applicable Information Production Standard. Examples such as P01.05 are illustrative rather than universal.
14. CDE State
ISO-aligned, extended
a defined governance condition applying to an exact governed Working Version or Container Revision and determining relevant conditions of access, permitted use and progression within the CDE Process.
Note 1. CDE State is not a folder, storage location or persistent Container identity. State ≠ Status Code ≠ Decision ≠ State Transition.
Note 2. Published information remains available for its permitted use while current. Archived is not the automatic next state after Published; superseded, withdrawn or otherwise historical governed information may be placed in Archived according to the applicable Information Production Standard and CDE Process.
15. Interoperability
established concept
the ability of different systems, organisations and information resources to exchange, interpret and use information while preserving its meaning and management context.
Note. In IMC, interoperability includes both technical compatibility and semantic continuity. Successful transfer of data does not by itself ensure interoperability if the information loses its identity, relationships, requirements or governance context.
16. Metadata
established concept
structured information used to describe, identify and govern an Information Container.
Note. Metadata may include identifiers, classification, revision, status, relationships, access conditions and other attributes required to manage an Information Container throughout its life.
3. Information Needs and Requirements
17. Information Receiver
established concept
a Party, team or role that requires, receives and uses information for a defined purpose.
Note. The role of Information Receiver is contextual. A Party may act as a Receiver in one information relationship and as a Provider in another.
18. Information Provider
established concept
a Party, team or role responsible for producing and providing information to an Information Receiver in response to an Information Requirement or other defined information need.
Note. The role of Information Provider is contextual. A Party may act as a Provider in one information relationship and as a Receiver in another.
19. Information Need
author-defined
a structured statement of why information is needed, what information is required, who needs it, and when it is needed.
Note. An Information Need expresses a management need for information. It does not yet define the technical or contractual specification for producing that information; this is the role of the Information Requirement.
20. Information Requirement
author-defined
an atomic, versioned and verifiable specification of information to be produced, including the conditions, criteria and constraints that apply to its production and delivery.
Note. An Information Requirement is derived from an Information Need. Individual Information Requirements may be organised into typed Requirement Set Versions, including OIR, AIR and PIR, and may be applied and refined through the Information Production Requirements (IPR) for a particular Appointment.
21. Organisational Information Requirements (OIR)
ISO-aligned, extended
a typed Requirement Set Version containing Information Requirements arising from an organisation’s strategic, tactical, operational and other management information needs.
Note. OIR organise requirements in an organisation-level management context. They may inform asset, project or appointment-specific requirements but are not a mandatory first stage in a fixed OIR → AIR → PIR → IPR sequence.
22. Asset Information Requirements (AIR)
ISO-aligned, extended
a typed Requirement Set Version containing Information Requirements applicable to the management, operation and use of a built asset.
Note. AIR refine relevant organisational requirements in relation to the asset and the Management Activities, decisions and uses that the asset must support.
23. Project Information Requirements (PIR)
ISO-aligned, extended
a typed Requirement Set Version containing Information Requirements applicable to the management of a project and the Management Activities and decisions associated with it.
Note. PIR refine relevant organisational requirements in relation to the project and provide a source for appointment-specific Information Production Requirements.
24. Information Production Requirements (IPR)
author-defined
an appointment-specific specification, represented as a Requirement Set Version, that applies and organises relevant Information Requirements for a particular Appointer–Appointee relationship and establishes the conditions governing their production, delivery and assessment.
Note 1. IPR may define or reference applicable Information Requirements, Level of Information Need, Acceptance Criteria, Reference Information, Shared Resources, delivery timing or frequency, and other relevant production conditions.
Note 2. Requirements may be refined where necessary for a particular production scope. Their individual identity and provenance remain distinct from the IPR in which they are applied.
Note 3. IPR are prepared before the relevant Appointment is agreed and are subsequently reconciled and established through the Appointment process. Different Appointments may require different IPR.
Terminology note. ISO 19650-1:2018, Clause 3.3.6, uses the term Exchange Information Requirements (EIR) for appointment-related information requirements. Information Deliverable remains descriptive, non-canonical terminology.
25. Information Exchange
ISO-aligned, extended
the governed process through which an Information Provider makes information available to an Information Receiver for a defined purpose.
Note 1. During collaborative production, Information Exchanges may support coordination, checking or the use of Reference Information. The applicable CDE Process governs how information is made available and used.
Note 2. Where an Exchange fulfils a formal delivery obligation under an Appointment, the Provider presents the required information through a Submission. Acceptance completes the formal delivery for the accepted scope. Rejection may lead to corrective action and Resubmission.
Note 3. Governed access to exact Container Revisions across Connected Information Systems may be sufficient for an Information Exchange.
26. Level of Information Need (LoIN)
ISO-aligned
a framework for specifying the extent, granularity and quality of information required to satisfy a defined Information Need.
Note 1. The purpose, delivery timing, participants and objects concerned inform the LoIN Specification. The Information Need identifies the Receiver. The specification also takes account of the relevant Providers once they are known.
Note 2. The specification may address geometrical information, alphanumerical information and documentation. The applicable framework may be established for an IMC Cycle as part of the Information Production Standard so that Information Requirements are specified consistently across the information supply chain.
27. Requirement Cascade
author-defined
the controlled derivation and propagation of Information Requirements from higher-level management needs and requirements through successive levels of the information supply chain.
Note. Cascading may refine, decompose or allocate requirements for a more specific scope or Appointment, while preserving traceability to their originating Information Need and higher-level requirements.
28. Information Production Request
author-defined
a documented request issued by an Appointer to one or more prospective Information Providers, specifying the applicable Information Production Requirements, supporting information, production conditions and expectations for the Provider’s proposal.
Note 1. An Information Production Request may be used in competitive procurement, direct engagement or internal Appointment arrangements.
Note 2. The request may establish Proposal Evaluation Criteria, the required structure of the preliminary Information Production Plan and other information needed to assess the prospective Provider’s competence, capability, capacity and proposed arrangements.
Note 3. Issuing an Information Production Request does not establish an agreed Appointment. The prospective Provider develops its proposal in response, and the applicable arrangements are subsequently reconciled and formalised.
29. Proposal Evaluation Criteria
author-defined
predefined criteria used to assess a prospective Information Provider’s proposal, including its proposed information-production arrangements, competence, capability, capacity, risk management and ability to fulfil the applicable Information Production Requirements.
Note. Proposal Evaluation Criteria are established before proposals are assessed and provide the basis for comparing and selecting prospective Providers. They are distinct from Acceptance Criteria, which govern assessment of information results produced and delivered under an Appointment.
4. Roles, Appointments and Tasks
30. Appointment
ISO-aligned, extended
a formal relationship through which an Appointer assigns defined responsibilities, requirements and scope to an Appointee.
Note. An Appointment may be established through a contract, agreement, internal assignment or other formal organisational arrangement. It defines the governance context within which information-production responsibilities and obligations apply.
31. Responsibility
established concept
the governed obligation of a Party, role, team or person to ensure that a defined outcome, function, activity, Requirement, Information Task, assessment or other assigned matter is properly addressed within its context.
Note. Responsibility is always relative to a defined object or outcome. It does not by itself imply that the responsible actor performs all work personally or holds the Authority to make every related Decision.
32. Authority
established concept
the formally governed right to make or permit a Decision, approval, authorisation, acceptance, rejection, change or other governance-significant action within a defined scope.
Note. Authority must be established explicitly through governance. Technical access or system capability does not by itself create Authority.
33. Assignment
established concept
the allocation of a defined activity or unit of work to a Party, team, role or person for execution.
Note. Assignment identifies who is expected to perform work. It should be distinguished from Responsibility for the outcome, Authority to make governance Decisions, and Access to information or system functions.
34. Access
established concept
the governed permission that determines what information or system functions a participant may view, retrieve, create, modify or otherwise use within a defined context.
Note. Access implements governance through technical permissions. Access does not by itself establish Assignment, Responsibility or Authority.
35. Appointing Party
ISO-aligned
the single Party that initiates the IMC Cycle and acts as the principal client of the Information Model, defining the overarching management context, information needs and requirements for its production and use.
Note 1. The Appointing Party is not simply any Party that makes an Appointment. Lower-level Parties may act as Appointers in particular Appointments, but they do not become the Appointing Party of the IMC Cycle.
Note 2. Information Delivery Milestones and Trigger Events are defined at the management level of the Appointing Party.
36. Appointer
established concept
the Party that establishes a particular Appointment and assigns its scope, requirements and responsibilities to another Party.
Note. The role of Appointer is contextual. The Appointing Party is the Appointer in its upper-level Appointment, while a Lead Appointed Party or another Appointed Party may act as an Appointer in a downstream Appointment without becoming the Appointing Party of the IMC Cycle.
37. Appointee
established concept
the Party that accepts a particular Appointment and is responsible for fulfilling its assigned scope, requirements and responsibilities.
Note. The role of Appointee is contextual. A Lead Appointed Party or Appointed Party may be an Appointee in one Appointment and an Appointer in another.
38. Appointed Party
ISO-aligned
a Party appointed within the IMC Cycle to fulfil a defined scope and to contribute to the production of information.
Note. An Appointed Party is an Appointee in the Appointment through which it is engaged. It may also act as an Appointer in a separate downstream Appointment.
39. Lead Appointed Party
ISO-aligned
an Appointed Party appointed directly by the Appointing Party to lead and coordinate an Information Production Team and to be accountable for the coordinated production and delivery of its information scope.
Note. A Lead Appointed Party is an Appointee in its Appointment with the Appointing Party. It may also act as an Appointer when establishing downstream Appointments with other Appointed Parties.
40. Information Production Team
ISO-aligned
a group of Parties and roles coordinated to produce and deliver information within a defined scope of the IMC Cycle.
Note. An Information Production Team may include one Lead Appointed Party together with one or more Appointed Parties and supporting roles. Its composition may span organisational boundaries.
41. Task Group
author-defined
a group of people organised to perform one or more Information Tasks within a defined production scope.
Note. A Task Group forms part of an Information Production Team. An Information Production Team may contain one or more Task Groups, depending on the scale and complexity of the information-production scope.
42. Information Task
author-defined
a planned unit of work undertaken to produce defined information in response to applicable Information Requirements.
Note. An Information Task is derived from applicable Information Requirements and is assigned within an Appointment or production plan. It defines the work to be performed; the resulting information is realized through one or more produced Container Revisions.
43. Information Manager
ISO-aligned, extended
a formally assigned role responsible for coordinating and supporting information-management activities within a defined organisational or appointment context.
Note. The Information Manager does not own or perform all information-management activities. Managers across the organisation remain responsible for the information needed to perform, control and improve their own work; the Information Manager provides dedicated coordination, governance and support within the assigned context.
5. Common Data Environment and Governance
44. Common Data Environment (CDE)
ISO-aligned
the governed arrangement for collaborative information production and management, implemented through a CDE Process supported by appropriate technologies and information locations.
Note. The CDE Process is not a software application or repository. A CDE arrangement may involve multiple Connected Information Systems while preserving Information Container identity, governed information instances, applicable conditions, access, traceability and continuity of management context.
45. CDE Process
ISO-aligned
the governed management process coordinating controlled production, progression, exchange, assessment, authorisation and use of Information Containers across participating Parties, organised on the basis of documented CDE Procedures and applicable responsibilities, conditions, CDE States, permissions, assessments and management Decisions.
Note 1. The CDE Process does not imply that a persistent Information Container itself moves through CDE States or that one unchanged Container Revision necessarily follows all four States. CDE States apply to relevant exact Working Versions or Container Revisions. Persistent Container identity remains stable across distributed technical environments.
Note 2. Published information remains available for permitted use while current. Archived primarily records superseded, withdrawn or otherwise historical governed information; Published → Archived is therefore not an automatic sequence.
Note 3. A State Transition changes the governed condition associated with an exact Working Version or Container Revision. Approval, Authorisation or Acceptance are Decisions that may permit or trigger a transition but are not themselves States or State Transitions.
Terminology note. The CDE Process is distinct from a software application and from any individual documented CDE Procedure.
46. Connected Information System
author-defined
an Information System that participates in a distributed CDE or metaCDE environment by supporting, executing or exposing part of the common governed CDE Process.
Note. Inclusion is functional and governance-based rather than a claim of physical containment or common ownership. A Connected Information System may remain technically and organisationally distinct while participating in shared information-management governance.
47. Status Code
ISO-aligned
a controlled metadata value indicating the permitted use of the content represented by an exact governed Working Version or Container Revision within the CDE Process.
Note. A Status Code does not itself define the workflow state of an Information Container. It expresses the permitted application or use of its content and is governed by the applicable Information Production Standard.
6. Governance and Information-Production Planning Artifacts
48. Information Protocol Template
ISO-aligned, extended
a reusable legal and information-management governance template established for an IMC Cycle and intended to provide a consistent basis for Information Protocols incorporated into contracts between separate organisations.
Note. Typically, one Information Protocol Template is established for an IMC Cycle and reused across relevant external contracts. It is not an instrument for regulating internal Appointments within one organisation.
49. Information Particular / Information Particulars
ISO-aligned, extended
an Information Particular is a contract-specific item of information used to complete the Information Protocol for a particular external contract within an IMC Cycle; Information Particulars are the set of contract-specific identifiers, values, conditions and references used to instantiate that Protocol.
Note. Information Particulars do not replace the common governance provisions defined in the Information Protocol Template; they provide the specific contractual context in which those provisions apply.
50. Information Protocol
ISO-aligned, extended
a contract-specific legal document forming part of, or incorporated into, an agreement between separate organisations and establishing the information-management rights, obligations, responsibilities and governance provisions applicable to that contractual relationship.
Note 1. An Information Protocol is developed from the applicable Information Protocol Template and contract-specific Information Particulars.
Note 2. Information Protocols govern external contractual relationships. Internal Appointments between organisational units of the same organisation are governed by applicable internal policies, regulations, procedures, assignments and other organisational management documents rather than by an Information Protocol.
51. Information Production Plan (IPP)
author-defined
a controlled management document establishing how collaborative information production is to be organised, coordinated and governed within the scope of an Information Production Team contributing to the Information Model.
Note 1. A Preliminary IPP is prepared during Process 3 — Information Provider’s Proposal. It describes the prospective Provider’s proposed approach, including Information Management functions, production and federation strategies, preliminary responsibility allocation, Methods and Procedures, and technologies.
Note 2. The preliminary IPP is reconciled and developed into an Agreed IPP during Process 4 — Appointment and Information Production Planning. The agreed plan provides the management framework for coordinating information production and is maintained under controlled change.
Note 3. Although named Information Production Plan, the IPP addresses both Information Management and Information Production arrangements. Its functions should not be confused with those of an Information Production Schedule.
52. Information Production Schedule (IPS)
ISO-aligned, extended
a controlled schedule defining the Information Tasks, planned information results, delivery dates, sequence and dependencies within a defined production scope.
Note. An IPS identifies the planned production activities and deliveries of the relevant Task Groups and their relationship to applicable Information Delivery Milestones. It must remain consistent with the agreed Information Production Plan, responsibility allocation and Information Production Requirements.
53. Master Information Production Schedule (MIPS)
author-defined
a consolidated schedule integrating the Information Production Schedules of an Information Production Team into a coordinated view of planned information production, exchanges, dependencies and delivery.
Note. The MIPS is coordinated by the Lead Appointed Party. It supports the identification of interdependencies, scheduling conflicts and delivery risks, and aligns the activities of participating Task Groups with the applicable Information Delivery Milestones. It does not replace the individual IPS or the Information Production Plan.
54. High-Level Information Production Responsibility Matrix
author-defined
a preliminary planning instrument identifying the Task Groups expected to be responsible for major information-production scopes or planned information results within an Information Production Team.
Note. The matrix is developed as part of the Preliminary IPP and is coordinated with the Federation Strategy. It provides the initial allocation of production responsibilities and is subsequently developed into the Detailed Information Production Responsibility Matrix.
55. Detailed Information Production Responsibility Matrix
author-defined
a controlled planning instrument establishing the allocation of responsibility for defined information-production scopes, planned information results and associated Information Tasks among the participating Task Groups.
Note. The matrix develops the preliminary allocation established during proposal preparation and must remain consistent with the agreed Federation Strategy, applicable IPR and Information Production Schedules. It establishes responsibility for information production, not the assignment of Information Management functions or the Authority to make governance Decisions.
56. Information Production Standard
ISO-aligned
a controlled set of requirements and rules governing how information is structured, identified, classified, described, produced, exchanged and managed within an IMC Cycle.
Note. The Information Production Standard may define naming and identification rules, metadata requirements, classification systems, coding conventions, revision and status rules, information formats, validation requirements and other provisions needed to ensure consistent information production and management.
57. Information Production Methods and Procedures
ISO-aligned, extended
governed approaches and documented arrangements specifying how information-production work may be performed and how activities are to be carried out consistently within an Information Management Cycle.
Note. Methods describe available production approaches; Procedures prescribe governed ways of performing activities. CDE Procedures are specialised Information Management Procedures that provide the procedural basis for organising the CDE Process. An Information Task, Method, Procedure and Process are distinct concepts.
58. Information Production Team Assessment Report
author-defined
a documented assessment of the proposed Information Production Team’s competence, capability and capacity to fulfil the applicable Information Production Requirements and perform the planned information-production activities.
Note. The report identifies existing capabilities, deficiencies, dependencies and areas requiring preparation or improvement. It supports the Provider’s Proposal and subsequent Mobilisation Planning but does not itself demonstrate operational readiness.
59. Mobilisation Plan
author-defined
a documented plan defining the actions, resources, preparations and tests required to establish and demonstrate the operational readiness of an Information Production Team for its agreed information-production responsibilities.
Note. The Mobilisation Plan is prepared during the proposal stage and implemented and tested during Mobilisation. It may address personnel, technologies, Reference Information, Shared Resources, Information Production Methods and Procedures, the CDE Process and readiness for relevant Trigger Events.
7. Collaborative Production, Assessment and Delivery
60. Collaborative Information Production
ISO-aligned, extended
the coordinated production of information by multiple Parties, teams or roles working within common governance arrangements to fulfil related Information Requirements and contribute to an Information Model.
Note. Collaborative Information Production depends on agreed responsibilities, shared rules, coordinated Information Tasks, controlled Sharing and coordination, and formal Information Exchanges where Provider–Receiver delivery is required. Contributions from different participants are governed as parts of the Information Model.
61. Federation Strategy
author-defined
a planned approach defining how the Information Model is to be structured as a coordinated composition of Information Containers produced by different parts of the Information Production Team.
Note. The Federation Strategy may define the planned breakdown of the Information Model, the allocation of Information Containers to Task Groups or other production scopes, the relationships between those Containers, and the principles used to coordinate their integration.
62. Information Container Breakdown Structure
author-defined
a structured representation of how the Information Model is divided into planned Information Containers for production, coordination and management.
Note. The Information Container Breakdown Structure may organise planned Containers by production scope, discipline, system, spatial zone, asset breakdown, Task Group or other agreed criteria. It provides a practical basis for assigning responsibility, planning Information Tasks and coordinating the production of the Information Model.
63. Information Verification
ISO-aligned, extended
a formal check that an exact applicable Container Revision complies with specified technical, structural and information-management requirements.
Note. Information Verification may include checks of identifiers, metadata, file or data structure, required attributes, naming conventions, status, classification, completeness and other objectively testable requirements. Verification establishes conformance; it does not determine whether the information is fit for its intended purpose.
64. Information Validation
ISO-aligned, extended
an assessment of whether information is suitable and adequate for its intended purpose and management context.
Note. Information Validation considers the relevance, sufficiency, usability and fitness of the information for the purpose for which it was required. Validation may therefore involve professional or managerial judgement and cannot always be reduced to automated checks.
65. Acceptance Criteria
ISO-aligned
predefined conditions against which produced or submitted information is assessed to determine whether it satisfies the applicable Information Requirements and is suitable for the intended governance decision.
Note 1. Acceptance Criteria may address completeness, accuracy, required attributes, conformity with the Information Production Standard, Level of Information Need, relevant assessment results and other applicable conditions.
Note 2. Acceptance Criteria establish the basis for assessment; they do not themselves constitute Information Verification, Information Validation or an Acceptance Decision.
Note 3. Acceptance Criteria for information results must be distinguished from Proposal Evaluation Criteria, which concern the suitability of a prospective Information Provider’s proposed approach, competence, capability, capacity and arrangements.
66. Approval
established concept
a formal decision that an exact applicable Container Revision is suitable to be made available for shared use within the CDE Process.
Note. Approval is made before information is released for shared use. It should be distinguished from Authorisation, which permits an Information Model or defined information set to be submitted to the Appointing Party, and from Acceptance, which is the Appointing Party’s decision on the information received.
67. Authorisation
established concept
a formal decision by the Lead Appointed Party that an Information Model or defined set of Container Revisions is ready and permitted to be submitted to the Appointing Party.
Note. Authorisation follows the Lead Appointed Party’s review of the information against the applicable production schedule, Information Requirements, Acceptance Criteria and Level of Information Need. It should be distinguished from Approval for shared use and from Acceptance by the Appointing Party.
68. Information Acceptance
ISO-aligned, extended
a formal decision by the Appointing Party that the exact submitted Container Revision(s) satisfy the applicable Acceptance Criteria and are accepted for their intended use within the IMC Cycle.
Note 1. Information Acceptance follows the Appointing Party’s review of the submitted Information Model or defined information set. It should be distinguished from Verification and Validation, which are assessments, and from Approval and Authorisation, which are earlier governance decisions within the CDE Process.
Note 2. Information Acceptance does not mean Actual Use. Accepted information may subsequently be used in Management Activities, decisions or actions, but Acceptance itself is the formal governance decision.
Note 3. Information Acceptance completes formal delivery for the accepted Submission scope.
69. Rejection
established concept
a formal decision by the Information Receiver that submitted information does not satisfy the applicable Acceptance Criteria or other governed conditions required for Acceptance.
Note. Rejection preserves the historical Submission record. It may lead to corrective action, new Container Revision(s), renewed assessment or Authorisation where required, and Resubmission.
70. Submission
ISO-aligned, extended
a formal information-management transaction through which a defined set of Container Revisions is presented by an Information Provider to an Information Receiver for a defined formal review or governance decision.
Note 1. A Submission identifies the exact information being presented, the Parties involved, the purpose of the transaction and the applicable governance context.
Note 2. A Submission does not necessarily involve copying or physically transferring files. It may instead provide controlled access to the exact Container Revisions held in one or more connected information systems.
Note 3. Within formal delivery, Submission presents the information for Receiver review and the applicable governance decision.
Note 4. Submission is the domain transaction; a Transmittal may be used as a manifest or representation of that transaction.
71. Information Supply Chain
author-defined
the sequence of connected Appointments and information-production relationships through which Information Requirements, responsibilities and planned information production are progressively allocated and fulfilled across the IMC Cycle.
Note. An Information Supply Chain may include several levels of Appointments. A Party may act as an Appointee in one Appointment and as an Appointer in a downstream Appointment, while the Appointing Party remains the single upper-level Party governing the IMC Cycle.
8. IMC Cycle, Events and Use
72. IMC Cycle (Information Management Cycle)
author-defined
a governed, recurring system of eight interrelated processes through which an Appointing Party establishes common information-management conditions, organises Information Appointments, coordinates information production, delivery and acceptance, and maintains the continuity of a federated Information Model.
Note 1. The IMC Cycle comprises eight processes: (1) Preparing the IMC Cycle; (2) Preparing an Information Appointment; (3) Information Provider’s Proposal; (4) Appointment and Information Production Planning; (5) Mobilisation; (6) Collaborative Information Production; (7) Information Delivery and Acceptance; (8) Information Model Incorporation and Continuity.
Note 2. The processes are not a rigid sequence. They may overlap, recur or be revisited as Information Appointments and information-production activities develop.
Note 3. Actual Use is not a separate process within the eight-process IMC Cycle. The Cycle maintains governed information for subsequent Management Activities. Actual Use may create further Information Needs and lead to additional production or changes within the continuing IMC Cycle.
73. Information Delivery Milestone
ISO-aligned
a defined point in the IMC Cycle at which the Appointing Party is scheduled to receive and assess a specified information delivery from the Information Production Team.
Note. Information Delivery Milestones are established at the management level of the Appointing Party and are linked to significant management events, decisions or stages in the Asset Life Cycle. They should be distinguished from ordinary due dates, deadlines or exchange dates used within lower-level Appointments.
74. Trigger Event
author-defined
a defined or recognised event within the IMC Cycle that creates the need for a specified information delivery or other governed information-management response by the Information Production Team.
Note 1. Trigger Events are established or recognised at the management level of the Appointing Party and are associated with Management Activities, decisions, changes or conditions that require information to be produced, updated, reviewed or delivered.
Note 2. Trigger Events may be foreseen or unforeseen. Foreseen Trigger Events can be anticipated and planned in advance, for example scheduled inspections, maintenance activities, statutory reviews, lease events, planned refurbishments or periodic asset-performance assessments. Unforeseen Trigger Events arise in response to events or conditions that were not planned in advance, for example equipment failure, damage, emergency intervention, unexpected performance deterioration or a significant change in regulatory or operational conditions.
75. IMC Use
author-defined
a defined application of information to support a particular Management Activity, Decision, Action or other organisational purpose within the wider Information Management in Construction context.
Note 1. An IMC Use describes how information is intended to be applied in a defined management context. It may establish or inform the Information Needs and Requirements that govern subsequent information production.
Note 2. IMC Use is distinct from the eight processes of the IMC Cycle, which govern information production, delivery, acceptance and Information Model continuity.
Distinction. Intended Purpose explains why information is needed; IMC Use describes how it is expected to support a particular Management Activity; Actual Use records how the information was actually applied.
76. Actual Use
author-defined
the recorded use of exact governed information, including the applicable Container Revision(s), in a real Management Activity, decision, action or other organisational purpose.
Note. Actual Use may follow formal Acceptance or occur under another governed condition that permits use. It records how exact governed information was applied in practice and may differ from its Intended Purpose or planned IMC Use. Actual Use does not itself imply Acceptance. The record should preserve the exact Revision(s) on which the use was based. Capturing Actual Use provides evidence of whether governed information created practical value for the organisation.
77. Golden Thread of Information
established concept
the continuity of relevant, trustworthy, traceable and usable information as Management Activities and contexts change over the life cycle of a built asset.
Note. In IMC, this continuity is maintained by preserving the purpose and provenance of information that retains management value and tracing its relationship to the Information Need, the Information Requirement and its Actual Use.
78. CDE Procedure
ISO-aligned, extended
a documented, governed way of performing an activity involving Information Containers under defined responsibilities, execution conditions, required actions, assessments and permitted outcomes.
Note. CDE Procedures are specialised Information Management Procedures and provide the procedural basis for organising the CDE Process. Procedure ≠ CDE State ≠ Decision ≠ State Transition.
79. Reference Information
ISO-aligned, extended
existing information made available to support planning, production, assessment or use of new information.
Note. Its source, provenance, currency, completeness, reliability, applicability and permitted use must be considered. Reference Information is defined by its function in the work, not by a particular file format or repository.
Note. Examples include templates, libraries, data dictionaries and reusable information structures. Shared access does not confer ownership or unrestricted reuse rights. Shared Resources support application of Standards and Procedures but are not themselves another category of governance rule.