GIIG Glossary

An individual or organisation who is commissioned by  an Appointing Party to undertake a specific task and,  in undertaking that task, to provide information relating to that task.

See also Lead Appointed Party

ISO 19650-1:2108 3.2.7 task team: individuals assembled to perform a specific task.

ISO 19650-1:2018 3.2.3 appointed party: provider of information concerning works, goods or services.

Note 1 to entry: A lead appointed party should be identified for each delivery team but this can be the same organization as one of the task teams. 

An individual or organisation – often referred to as the client – who commissions others (Appointed Parties) to undertake a specific task and, in undertaking that task, to provide information relating to that task.

ISO 19650-1:2018 3.2.5 client: actor responsible for initiating a project and approving the brief.

ISO 19650-1:2018 3.2.4 appointing party: receiver of information concerning works, goods or services from a lead appointed party.

An item, thing or entity that has potential or actual value to an organisation, including, for example, meeting statutory obligations.

ISO 19650-1:2018 3.2.8 asset: item, thing or entity that has potential or actual value to an organisation.

BS 1192-4:2014 3.1 assets: includes the overall Facility and the constituent aspects: Identified Space (location), Floor (region), Zone, manageable Components, Type and System.

An Information Model comprising Information Containers that support Organisational Information Requirements (OIR) and Asset Information Requirements (AIR), i.e.: the operational information that an organisation will need about its assets to support its business functions.

ISO 19650-1:2018 3.3.9 asset information model AIM: information model relating to the operational phase.

Information requirements relating to managerial, commercial and technical aspects of asset operation.

ISO 19650-1:2018 3.3.4 asset information requirements (AIR): information requirements in relation to the operation of an asset.

ISO 19650-1:2018 5.3 asset information requirements (AIR): AIR set out managerial, commercial and technical aspects of producing asset information.

The technical aspects of the AIR specify those detailed pieces of information needed to answer the asset-related OIR [organisational information requirements]. These requirements should be expressed in such a way that they can be incorporated into asset management appointments to support organisational decision-making.

A process in which activities, objects and information are systematically identified and arranged into categories according to logically structured conventions, methods, and procedural rules.

ISO 15489-1:2016 3.5 classification: systematic identification and/or arrangement of business activities and/or records into categories according to logically structured conventions, methods, and procedural rules.

BS ISO 12006-2:2015 defines a framework for construction-sector classification systems. It identifies a set of recommended classification table titles for a range of construction object classes according to particular views, e.g. by form or function, supported by definitions. It shows how the object classes classified in each table are related, as a series of systems and sub-systems, e.g. in a building information model.

ISO 19650-2:2018 5.1.7 requires that information containers be assigned classification metadata in accordance to ISO 12006-2. Uniclass 2015 is compliant with ISO 12006-2 and is the preferred classification system in the UK. It is referenced in the ISO 19650-2 National Annex. Uniclass 2015 contains multiple classification tables which can be used to classify different types of information containers.

UK BIM Framework Guidance Part 2: 2.4 Classification through metadata assignment footnote:

“ISO 19650-2 does not provide further details about classification, but it is important that classification is used beneficially to indicate the contents of the information container not the type of information container (as this is dealt with by the Type field in the information container unique ID – see ISO 19650-2 National Annex clauses NA.2.2 and NA.3.6).

It is also important to be aware that:

1. Uniclass 2015 is a developing resource, which is subject to regular updates. The granularity of classification available may not be consistent for all information containers and may change over the lifetime of a project
2. Uniclass 2015 comprises a number of classification tables. The classification used should be appropriate to the information container it is being assigned to” ¹

A person, organisation or organisational unit responsible for initiating a project and approving a project brief requiring works, goods or services in return for monetary or other valuable considerations.

See also Appointing Party

ISO 19650-1:2018 3.2.5 client: actor responsible for initiating a project and approving the brief.

ISO 19650-1:2018 3.2.4 appointing party: receiver of information concerning works, goods or services from a lead appointed party.

An information management process used to capture, manage and exchange whole-life information.

ISO 19650-1:2018 12.1 Principles: A CDE solution and workflow should be used for managing information during asset management and project delivery. During the delivery phase, the CDE solution and workflow support the information management processes in ISO 19650-2:2018, 5.6 and 5.7. At the end of a project, information containers required for asset management should be moved from the PIM to the AIM.

Properties or attributes (binary, qualitative or quantitative) of entities, typically represented by characters or symbols.

PAS 185:2017 3.1.14 data: series of marks, digital or analogue signals or encoded characters stored or transmitted electronically.

A set of references defining and classifying an organisation’s standard Asset Information Requirements (AIR), aligned to procurement gateways.

*IMP

A reference library of defined and classified asset and element objects, with data attribution requirements aligned to information purposes for each exchange event. To be delivered, assured and accepted as part of each contracted information exchange event and within the BS1192-4 transmittal container. The DRL defines the minimum asset objects and data container content required as part of the exchange event meeting the Appointed Party information requirements. The DRL is held in the Reference Data Library (RDL).

An automated means to achieve a secure and interoperable (see: Interoperability) system-to-system digital information exchange.

*IMP

A service discovery protocol is a network protocol that helps systems identify and connect to each other without (or with reduced) configuration efforts by users or system administrators. Service discovery requires a common language to allow software agents to make use of one another’s services without the need for continuous user intervention.

A large-scale software application used to manage fundamental aspects of an organisation’s business.

ISO 19650-3:2020 5.1.10 “(establish links to enterprise systems)”

UK BIM Framework Guidance Part 3: Section 8 ISO 19650-3 clause 5: insight

The primary party active within the clause: Appointing party Insight: It is likely that existing enterprise information systems will be used to store some of the information being collected in response to the information requirements. It may even be possible to store all the information in existing systems rather than creating new information systems from scratch to do this.

A pre-agreed and often contractual scheduled event involving an information exchange.

*IMP

An exchange event is a pre-agreed and often contractual scheduled event when an Exchange Information Model (EIM) is published by the Lead Appointed Party to the Appointing Party.

A set of information containers that meet the requirements of a particular exchange event.

*IMP

The collection of named file information containers and data meeting the Appointing Party exchange information requirements for a particular information exchange event, defined as a collection by a single BS1192-4 Construction Operations Building Information Exchange (COBie) transmittal file and its filename, ISO19650 status, version and metadata all in accordance with the information standard.

The EIM forms the basis for the automated verification and reporting aspect of the Information Management Platform (IMP), and for its storage to support presentation and exploitation.

Requirements relating to an appointment, usually specifying managerial, commercial and technical aspects concerning the production of project or contract information.

ISO 19650-1:2018 3.3.6 exchange information requirements (EIR): information requirements in relation to an appointment.

ISO 19650-1:2018 5.5 exchange information requirements (EIR): set out managerial, commercial and technical aspects of producing project information.

A named distinct operational built or geographic asset, typically a building or section of infrastructure along with details and extent of the geographic site and of the temporal project.

BS1192-4:2014 3.1.3: Facility: named distinct operational built or geographic asset, typically a building or section of infrastructure along with details and extent of the geographic site and of the temporal project.

Data endowed with meaning, purpose and context.

ISO 19650-1:2018 3.3.1 information: reinterpretable representation of data in a formalised manner suitable for communication, interpretation or processing.

PAS 185:2017 3.1.23 information: one or more data items that have a context and therefore convey a message or meaning.

A uniquely named container, often a file, which includes metadata and contains data which, by being included in the container, becomes information.

See also Classification

ISO 19650-1:2018 3.3.12 information container: named persistent set of information retrievable from within a file, system or application storage hierarchy.

ISO 19650-2:2018 5.1.7 requires that information containers be assigned classification metadata in accordance to ISO 12006-2.

A schedule of specified, procured and appointed outcome deliverables for each Project Information Requirements (PIR) exchange event.

*IMP

ISO 19650-1 6.3.1 General principles: Information delivery plans are made every time a lead appointed party is appointed in relation to asset management or project delivery activities. This includes the parallel appointments made by the Appointing Party in relation to design, construction or any other services, and the sequential appointments made to form a supply chain, for example, within a construction team.

See also ISO 19650-1:2018 Section ‘10 Information delivery planning’

Note: The IDP is a regularised and templated project- or contract-profiled schedule of specified, procured and appointed outcome deliverables for each Project Information Requirements exchange event. Deliverables are profiled to inform each event information purpose question with an appropriate level of information need in the context of the project or contract. Post-appointment, the lead appointed party aligns the proposed information container delivery through the Master Information Delivery Plan (MIDP) against each outcome deliverable.

A manual or automated exchange of information containers between two organisations’ systems across a contract line.

ISO 19650-1:2018 3.3.7 information exchange, verb: act of satisfying an information requirement or part thereof.

The process by which an organisation, with appropriate security controls, specifies (including provisions for data quality and provenance), procures, assures, stores, presents, and exploits its data to perform its core business.

ISO 9000 definitions cover quality, information and management. Combining these: information management is: Management (coordinated activities to direct and control) of information (a representation of something) with particular regard to quality (the degree to which a set of inherent characteristics of an object fulfils requirements – i.e.: needs or expectations that are stated, generally implied or obligatory).

The means by which consistent data and information can be communicated in a way that is effective, resilient and secure.

A process enabling the secure specification, procurement, assurance, storage, presentation and exploitation of information derived internally or from third parties, in the creation, maintenance, use and disposal of a client’s assets.

*IMP

An Information Management Platform (IMP) is a client operated and maintained process and best of breed technology suite. It enables the specification, procurement, assurance, storage, presentation and exploitation of information derived internally or from third parties, in the creation, maintenance, use and disposal of its managed and maintained infrastructure asset estate.

The IMP enables immutable storage, manual subject matter expert validation, automated verification assurance at the point of delivery, and direct visualisation and analytics in both the project and operational context, and automated transfer of assured published data into existing enterprise systems.

The IMP is unlikely to be formed from one system or by one supplier but from a modular best of breed technology set or stack. The functional requirements presented by the IMP reflects this modular approach.

A defined set of structured and/or unstructured information containers (NB: not necessarily a 3D model – a 3D model may form part of an information model)

ISO 19650-1:2018 3.3.8 information model: set of structured and unstructured information containers.

Deliverables which provide minimum levels of specified information to satisfy defined purposes.

*IMP

Crown Commercial Services, HM Treasury ‘Green Book’, Cabinet Office 2020 ‘Construction Playbook’, the CIH Value Toolkit, and the ‘TIP Roadmap’ all recommend that specifications take an ‘outcome-based approach’.

Information deliverables aligning to Uniclass 2015 Project Management table (see Classification) define the information required by the Appointing Party to be delivered by the Lead Appointed Party in the context of a project or contract at each exchange event and to support event decisions and achieve the project outcomes.

Information deliverables can also be aligned to individual minimum technical requirements and information standard in the Reference Data Library and form part of the project appointed contract scope as a method of procuring specific information in the context of each project. 

Information deliverables are delivered through specific deliverable container items proposed by the Lead Appointed Party in the Master Information Delivery Plan (MIDP) and subject to acceptance by the Appointing Party.

The IMP defines a unique reference for each required deliverable as an extended metadata component to align each MIDP file container with an information outcome deliverable. This maintains line of sight through the Information Delivery Plan (IDP) and exchange event to the information purpose questions, and also enables automated assurance at the point of delivery and mapping in the Asset Information Model (AIM), available to support whole life decision events.

The protection of information and information systems from unauthorised access, use, disclosure, disruption, modification, or destruction in order to provide confidentiality, integrity, and availability.

See also security-mindedness

Above definition used by the National Infrastructure Commission’s Data for the Public Good (2018) in its glossary (p.68), referencing NIST SP800-53 (“Security and Privacy Controls for. Federal Information Systems and Organizations”).

ISO/IEC 17788:2014 Information technology - Cloud computing - Overview and vocabulary 3.1.3: Preservation of confidentiality, integrity and availability of information (in addition, other properties, such as authenticity, accountability, non-repudiation, and reliability can also be involved).

The ability of two or more systems to exchange information securely and to use the information that has been exchanged.

(This exchange must not require additional processing, and must not be legally or technically restricted to specific software solutions.)

See also Openness

Definition adopted by BIM Interoperability Expert Group (BIEG), March 2020 report² (with addition of the word ‘securely’).

The individual or organisation appointed by the client / Appointing Party to be responsible for delivery of contracted information deliverables at defined exchange points.

ISO 19650-1:2018 3.2.3 Appointed Party - note 1: A Lead Appointed Party should be identified for each delivery team, but this can be the same organization as one of the task teams.

Acceptable levels of geometrical and alphanumerical content to meet the data requirements of particular information exchanges.

ISO 19650-1:2018 3.3.16 level of information need: framework which defines the extent and granularity of information. Note 1: One purpose of defining the level of information need is to prevent delivery of too much information.

ISO 19650-1:2018 11.2 Level of information need: ...The levels of information need should be determined by the minimum amount of information needed to answer each relevant requirement, including information required by other appointed parties, and no more.

Lasting records of objects of interest that exist in space-time such as assets, people, customers, suppliers.

See also Data

ISO 5127:2017, 3.1.10.06 master data: data that represent content features of their data objects which are the lasting base for certain recurrent processes, can be repeatedly used in a variety of operations and so remain stable for a longer time.

A schedule aggregating the task information deliverables to be completed by appointed parties through the Lead Appointed Party.

See also Task Information Delivery Plan

ISO 19650-2:2018 5.4.5 Establish the master information delivery plan. The Lead Appointed Party shall aggregate the TIDP from each task team to establish the delivery team’s master information delivery plan (MIDP).

Data about data - metadata provides additional information about a specific set of data (for example, an information container).

ISO 23081 2:2007 3.7: structured or semi-structured information, which enables the creation, management, and use of records through time and within and across domains.

ISO 19650-2:2018 UK Annex defines the scope of metadata to be used to name and define individual file containers. Further metadata may be carried in the BS1192-4 transmittal attached to both documents and asset objects.

Note: For example, the Dublin Core schema is used for sharing tabular data (CSV files and spreadsheets) between UK government departments.³ Geographic data is covered by the INSPIRE documentation,⁴ specifically the section on GEMINI (the UK standard for spatial metadata, based on ISO 19139). UK GEMINI (Geo-spatial Metadata Interoperability Initiative) is a set of metadata elements for describing geospatial data resources. An open standard, it is provided free of charge by the AGI for the benefit of the GI community, under a Creative Commons license.⁵

Capability to reliably and securely find, access, use and make available asset information in perpetuity without obstruction or restriction due to closed or proprietary software applications and/or data formats.

Government Construction Client Group (2011): “Government as a client can derive significant improvements in cost, value and carbon performance through the use of open shareable asset information.”⁶

Note: Openness is described in the Centre for Digital Built Britain’s Gemini Principles (2019) as one of three values underpinning ‘trust’, alongside security and quality. In describing the National Digital Twin (NDT) it says this “must be as open as possible, while remaining consistent with the principles of holistic security, so that it creates the most value for everyone.” … “Open data, open culture, open standards, open source and collaborative models build trust, reduce cost and create more value than other approaches.”⁷

Data that is made freely available by the data owners, can be reused without formal permission, and is not legally or technically restricted to specific software solutions.

Open data is digital data that is made available with the technical and legal characteristics necessary for it to be freely used, reused, and redistributed by anyone, anytime, anywhere.⁸

UK BIM Framework (September 2020: Edition 1) Guidance Part B Open data, buildingSMART and COBie - The formal requirements and recommendations around information management (the ISO 19650 series) were developed with open data at their centre. Organisations can derive significant improvements in cost, value and operational performance through the use of open shareable asset information. Examples of open data file formats include HTML, PDF, PPTX, MP3, and IFC.

A format for storing data, defined by a published specification or schema, and which can be accessed, used and implemented by anyone.

Open Knowledge Foundation: An open format is one which places no restrictions, monetary or otherwise, upon its use and can be fully processed with at least one free/libre/open-source software tool.⁹

Note: For example, the UK Government’s Open Standards Board has adopted the Open Document Format (ODF) standard, and recommends use of the ODF 1.2 standard for sharing and collaborating on documents in government.¹⁰ ODF-compatible software tools include Windows Office products and Google Docs.¹¹

Computer software that is released under a license in which the copyright holder grants users the rights to use, study, change, and distribute the software and its source code to anyone and for any purpose.

OpenSource.org Open Source definition:¹² Open source doesn’t just mean access to the source code. The distribution terms of open-source software must comply with 10 criteria, including that licences must not restrict other software, and must be technology-neutral.

A standard for which the specification or schema is publicly available, where the drafting and maintenance of the specification is open to all interested parties and is consensus-based, and where use of the resulting standard is royalty-free.

Cabinet Office Policy paper: Open Standards principles (updated 5 April 2018): Open standards give users permission to copy, distribute and use technology freely or at low cost.¹³ “Open standards are common rules that allow any user to create compatible and consistent products, processes and services. They are designed collaboratively, are publicly available, and free or low cost.”¹⁴

Note: For UK Government technology programmes, the technology code of practice (TCoP) requires (step 4) use of open standards to ensure “technology works and communicates with other technology, and can easily be upgraded and expanded”.¹⁵

The information needed by an organisation in order to satisfy its business objectives.

ISO 19650-1:2018 3.3.3 organisational information requirements (OIR): information requirements in relation to organizational objectives.

A structured information model of classified, immutable and federated file and object containers supporting the collaborative and coordinated delivery of a project or contract.

ISO 19650-1:2018 3.3.10 project information model (PIM): information model relating to the delivery phase.

Information requirements in relation to the delivery of a defined project.

ISO 19650-1:2018 3.3.5 project information requirements (PIR): information requirements in relation to the delivery of an asset

A system of rules that allows two or more entities of a communications system to transmit information.

*IMP

A protocol is a system of rules that allows two or more entities of a communications system to transmit information. The protocol defines the rules, syntax, semantics and synchronisation of communication and possible error recovery methods. Protocols may be implemented by hardware, software, or a combination of both.

Records of classes, properties, units of measure that help define the sets of values to be used to populate other data sets.

See also Data

ISO/TS 18101-1:2019 3.14 reference data: domain and sector standardized data sets that help define the set of values to be used to populate other data sets.

ISO 15926-1:2004, 3.1.18 reference data: process plant life-cycle data that represents information about classes or individuals which are common to many process plants or of interest to many users.

A curated and securely accessible collection of reference data standards and data sets required to be used for built environment information management throughout the organisation, whether externally or internally authored.

*IMP

ISO 15926-1:2004 3.1.19 reference data library (RDL): managed collection of reference data

An organisational pattern or structure describing categories of information and the relationships among them (for example, how relational databases are divided into database tables).

ISO 23081 1:2006 3.3 schema: logical plan showing the relationships between metadata elements, normally through establishing rules for the use and management of metadata specifically as regards the semantics, the syntax and the optionality (obligation level) of values.

Understanding and applying appropriate and proportionate security measures in any business situation so as to deter and/or disrupt hostile, malicious, fraudulent and criminal behaviours or activities.

See also Information security

ISO 19650-5:2020 3.10

ISO 19650-5:2020 is a specification for security-minded information management. It details and specifies the principles and requirements for security-minded management of sensitive information that is obtained, created, processed and stored as part of, or in relation to, an initiative, project, asset, product or service.

Note: Security-mindedness is about encouraging business leaders, managers and practitioners to consider security across their organisations, the assets they own and the services they deliver, as well as in their projects and programmes.

An organisation must first appreciate and recognise that security threats, vulnerabilities and the potential resultant risks are something it needs to consider and understand. Being security-minded is about then responding to these risks in a way that it appropriate and proportionate.

Security-mindedness is generally undertaken with the aim of deterring and disrupting hostile, malicious, fraudulent and criminal behaviours or activities. However, the approach can also be used by organisations to help to protect against loss of valuable commercial information, personal data and intellectual property.

A way of deploying software applications via the Internet as a service rather than as installed software.

ISO/IEC 17788:2014 3.2.5 cloud computing: Paradigm for enabling network access to a scalable and elastic pool of shareable physical or virtual resources with self-service provisioning and administration on-demand.

ISO/IEC 17788:2014 3.2.36 Software as a Service (SaaS): Cloud service category in which the cloud capabilities type provided to the cloud service customer is an application capabilities type.

Data where values and variables are organised and are addressable for computer interpretation and analysis.

See also unstructured data

ISO/IEC 20546:2019 3.1.35 structured data which are organized based on a pre-defined (applicable) set of rules. Note 1: The predefined set of rules governing the basis on which the data is structured needs to be clearly stated and made known.

A self-contained data model whose components or data objects relate to each other and conform to a particular schema context or namespace.

A structured data model is a self-contained data model whose components or data objects relate to each other and conform to a particular schema context or namespace.

The components, data objects and containers making up a structured data model must be individually addressable and related in the context of the model and its schema.

For interoperability, the structured data model must be fully self-describing and conform or be linked to a defined data schema or standard.

A collection of file containers on their own should not be considered as a structured data model unless they are individually named, classified (see Classification) and related or linked in the context of the model and its schema. For example, an Exchange Information Model is bound by a BS1192-4 transmittal file defining its identity and content.

Someone appointed to ensure the facts and details in an area of expertise are valid.

*IMP

A subject matter expert is someone appointed to ensure the information in an area of expertise is valid, and meets the scope of the appointment. For example, does information meet the needs of stakeholders, legislation, policies, standards, and best practices?

A named set of manageable components organised to provide a common function.

BS1192-4:2014 3.1.6: System: named set of manageable Components providing a common function.

An immutable and classified (see Classification) information storage system with effective governance so that it constitutes an authoritative information source.

ISO 15489-1:2016: 3.14 record(s) information created, received and maintained as evidence and as an asset by an organisation or person, in pursuit of legal obligations or in the transaction of business.

ISO 15489-1:2016: 3.16 records system information system which captures, manages and provides access to records over time.

The Attorney General’s Office (2013) Records Management Policy¹⁶ quotes the International Council on Archives (ICA) Committee on Electronic Records definition of a record as: “recorded information produced or received in the initiation, conduct or completion of an institutional or individual activity and that comprises content, context and structure sufficient to provide evidence of the activity.”

A schedule defining task-related information deliverables to be completed by appointed parties.

See also Master Information Delivery Plan

ISO 19650-2:2018 5.4.4 Establish the task information delivery plan(s): Each task team shall establish, and maintain throughout its appointment, a task information delivery plan (TIDP).

Records of business transactions, measurements and other events.

See also Data

ISO 8000-2:2020 3.10.2 transaction data: data representing a business transaction (completion of a business action or a course of action)

Data where content (values and variables) are not organised for computer interpretation and analysis.

See also structured data

ISO/IEC 20546:2019 3.1.37 Unstructured Data: data which are characterised by not having any structure apart from that record or file level. Note 1: On the whole unstructured data is not composed of data elements.

A named set of spaces (locations) sharing a specific attribute, such as activity, access, management or conditioning.

BS1192-4:2014 3.1.8 - A named set of spaces (locations) sharing a specific attribute, such as activity, access, management or conditioning.

A set of references defining and classifying an organisation’s standard Asset Information Requirements (AIR), aligned to procurement gateways.

An automated means to achieve a secure and interoperable (see: interoperability) system-to-system digital information exchange.

A pre-agreed and often contractual scheduled event involving an information exchange.

A set of Information Containers that meet the requirements of a particular exchange event.

A schedule of specified, procured and appointed outcome deliverables for each Project Information Requirements exchange event.

A process enabling the secure specification, procurement, assurance, storage, presentation and exploitation of information derived internally or from third parties, in the creation, maintenance, use and disposal of a client’s assets.

Deliverables which provide minimum levels of specified information to satisfy defined purposes.

A system of rules that allows two or more entities of a communications system to transmit information.

A curated and securely accessible collection of reference data standards and data sets required to be used for built environment information management throughout the organisation, whether externally or internally authored.

Someone appointed to ensure the facts and details in an area of expertise are valid.

A self-contained data model whose components or data objects relate to each other and conform to a particular schema context or namespace.