{"type":"term","total":88,"page":1,"items":[{"iri":"https://w3id.org/bimei/term/immersive-environment","slug":"immersive-environment","label":"Immersive Environment","description":"The technology used to allow users to experience [[Virtual Reality Simulation]] or [[Augmented Reality Simulation]]. Immersive Environments can be partially or fully immersive depending on tools used (specially-fitted rooms, wearables, etc…)","altLabels":[],"status":"canonical","register":"canonical","grounding":"pending"},{"iri":"https://w3id.org/bimei/term/immersive-technology","slug":"immersive-technology","label":"Immersive Technology","description":"The software tools and equipment needed to emulate the physical world by generating a digitally simulated world which enables a sense of immersion for the user, becoming deeply absorbed into the simulated evironment. Immersive technologies act as the user interface for [[Mixed Reality]]","altLabels":["Immersive Computing"],"status":"canonical","register":"canonical","grounding":"pending"},{"iri":"https://w3id.org/bimei/term/implementation-competency","slug":"implementation-competency","label":"Implementation Competency","description":"Implementation competencies and topics cover the activities required to introduce BIM concepts and tools into an organization. Implementation topics also focus on generating new information systems, delivery standards and workflow protocols as required for sustained BIM diffusion. Topics included [[Implementation Fundamentals]], [[Component Development]], [[Library Management]], [[Standardization and Templates]], [[Technical Training]], [[System and Process Testing]], and [[Guides and Manuals]]","altLabels":[],"status":"canonical","register":"canonical","grounding":"pending"},{"iri":"https://w3id.org/bimei/term/implementation-fundamentals","slug":"implementation-fundamentals","label":"Implementation Fundamentals","description":"BIMe Topic under [[Implementation Competency]]: Identifying and managing issues associated with [[BIM Implementation]]","altLabels":[],"status":"canonical","register":"canonical","grounding":"pending"},{"iri":"https://w3id.org/bimei/term/in-use","slug":"in-use","label":"In use","description":"The state or period in which an asset, system, or service is operated and used for its intended purpose.","altLabels":["Operation and maintenance"],"status":"canonical","register":"canonical","grounding":"pending"},{"iri":"https://w3id.org/bimei/term/inclusion-exclusion-variable","slug":"inclusion-exclusion-variable","label":"Inclusion/Exclusion Variable","description":"A [[BIMe Metric]] applicable in deciding which model elements will be included or excluded during data exchange","altLabels":["IEV"],"status":"canonical","register":"canonical","grounding":"pending"},{"iri":"https://w3id.org/bimei/term/individual-competency","slug":"individual-competency","label":"Individual Competency","description":"The combined skill, knowledge and experience of an individual representing his/her ability to perform an activity or a task. In BIM Excellence, the term 'Competency' is used generically and may refer to Individual Competency, [[Organizational Competency]] or [[Project Team Competency]] ","altLabels":[],"status":"canonical","register":"canonical","grounding":"pending"},{"iri":"https://w3id.org/bimei/term/individual-competency-index","slug":"individual-competency-index","label":"Individual Competency Index","description":"A [[BIMe Metric]] for measuring [[Individual Competency]]. The Individual Competency Index (ICI) measures both conceptual and procedural knowledge (skill) which are needed by individuals in order to perform a defined activity or deliver a measureable outcome. The ICI has five levels: [0] None, [1] Basic, [2] Intermediate, [3] Advanced, and [4] Expert","altLabels":["ICI"],"status":"canonical","register":"canonical","grounding":"pending"},{"iri":"https://w3id.org/bimei/term/industry-engagement-and-knowledge-sharing","slug":"industry-engagement-and-knowledge-sharing","label":"Industry Engagement and Knowledge Sharing","description":"BIMe Topic under [[Research and Development Competency]]: Sharing BIM knowledge and experience with the wider industry through formal/informal workshops, seminars and presentations","altLabels":[],"status":"canonical","register":"canonical","grounding":"pending"},{"iri":"https://w3id.org/bimei/term/industry-foundation-classes","slug":"industry-foundation-classes","label":"Industry Foundation Classes","description":"IFC refers to a neutral/open specification (schema) and a non-proprietary 'BIM file format' developed by buildingSMART. Major [[BIM Software Tool]]s support the import and export of IFC files (also refer to [[ISO 16739]])","altLabels":["IFC"],"status":"canonical","register":"canonical","grounding":"pending"},{"iri":"https://w3id.org/bimei/term/information","slug":"information","label":"Information","description":"The facts provided or learned about events, things, processes or concepts that has a particular meaning within a certain context [adapted from the Oxford Dictionary and ISO/IEC 2382-1:1993]","altLabels":[],"status":"canonical","register":"canonical","grounding":"pending"},{"iri":"https://w3id.org/bimei/term/information-action","slug":"information-action","label":"Information Action","description":"Information Actions are clusters of granular information activities needed to connect [[Defined Purpose]]s to [[Defined Deliverable]]s, and [[Defined Resources and Methods]]. In the [[LITE Framework]], there are four types of Information Actions: Execution Actions, Measurement Actions, Capturing Actions, and Sharing Actions","altLabels":[],"status":"canonical","register":"canonical","grounding":"pending"},{"iri":"https://w3id.org/bimei/term/information-container","slug":"information-container","label":"Information Container","description":"A \"named persistent set of [[Information]] retrievable from within a file, system or application storage hierarchy\" [[ISO 19650-1]] (3.3.12) related to one or more [[Information Requirement]]s. As a generic term, an information container can refer to a [[Model]], [[Document]], [[Data]] set or to any combination of [[Structured Information]] and [[Unstructured Information]]. Information containers are the units that make up an [[Information Model]]: a [[Project Information Model]], for example, is a set of them","altLabels":[],"status":"canonical","register":"canonical","grounding":"pending"},{"iri":"https://w3id.org/bimei/term/information-container-state","slug":"information-container-state","label":"Information Container State","description":"The state of [[Information Container]] exchanged through the [[Common Data Environment]]. There are four information container states: Work in Progress, Shared, Published, and Archive. The permissions and processes governing each state, and the transition from one state to another, are defined by the [[Appointing Party]] and are detailed in the [[BIM Execution Plan]], Information Delivery Plans, and related [[Appointment]] documents","altLabels":[],"status":"canonical","register":"canonical","grounding":"pending"},{"iri":"https://w3id.org/bimei/term/information-cycle","slug":"information-cycle","label":"Information Cycle","description":"A single revolution of [[Information]] along an [[Information Route]] back to the [[Information Milestone]] that it started from. For example, if an asset is reused three times, its information has completed three Information Cycles","altLabels":[],"status":"canonical","register":"canonical","grounding":"pending"},{"iri":"https://w3id.org/bimei/term/information-delivery-format","slug":"information-delivery-format","label":"Information Delivery Format","description":"How [[Information]] is (or need to be) delivered on a [[Project]]. There are three Information Delivery Formats: [[Documented Project Information]], [[Modelled Project Information]] and [[Structured Project Data]]","altLabels":[],"status":"canonical","register":"canonical","grounding":"pending"},{"iri":"https://w3id.org/bimei/term/information-delivery-manual","slug":"information-delivery-manual","label":"Information Delivery Manual","description":"The formal method developed and propagated by [[buildingSMART]] to establish [[Model View Definition]]s as a standard requirement for exchanging model data within the construction industry. IDM is an ISO standard intended to \"facilitate interoperability between software applications used in the construction process, to promote digital collaboration between actors in the construction process and to provide a basis for accurate, reliable, repeatable and high-quality information exchange\" (ISO 29481-1:2010)","altLabels":["IDM"],"status":"canonical","register":"canonical","grounding":"pending"},{"iri":"https://w3id.org/bimei/term/information-delivery-milestone","slug":"information-delivery-milestone","label":"Information Delivery Milestone","description":"A \"scheduled event for a predefined [[Information Exchange]]\" [[ISO 19650-2]] (3.1.3.2) established by the [[Appointing Party]]. An example of an Information Delivery Milestone is a deadline for submitting an [[Information Container]] (e.g. design drawings or a progress report) by a set date","altLabels":[],"status":"canonical","register":"canonical","grounding":"pending"},{"iri":"https://w3id.org/bimei/term/information-delivery-specification","slug":"information-delivery-specification","label":"Information Delivery Specification","description":"A computer-interpretable buildingSMART standard for specifying the information requirements that an IFC model must meet (e.g. required classes, properties, values and classifications), allowing a delivered model to be checked automatically. Also refer to [[Model View Definition]] and [[Delivery Specification]]","altLabels":["IDS"],"status":"canonical","register":"canonical","grounding":"pending"},{"iri":"https://w3id.org/bimei/term/information-environments","slug":"information-environments","label":"Information Environments","description":"The settings and systems in which information is created, managed, exchanged, accessed and retained across an asset or project lifecycle.","altLabels":[],"status":"canonical","register":"canonical","grounding":"pending"},{"iri":"https://w3id.org/bimei/term/information-exchange","slug":"information-exchange","label":"Information Exchange","description":"The \"act of satisfying an [[Information Requirement]] or part thereof\" [[ISO 19650-1]] (3.3.7) by exchanging [[Information]] between members of a [[Project Team]]. Exchange here refers to the sharing, coordination, and checking of information especially at [[Key Decision Point]]s and preferably (should be) through the [[Common Data Environment]]","altLabels":[],"status":"canonical","register":"canonical","grounding":"pending"},{"iri":"https://w3id.org/bimei/term/information-flow","slug":"information-flow","label":"Information Flow","description":"The movement of [[Information]] within and between [[Information Milestone]]s throughout the [[Asset Life Cycle]]. In the [[LITE framework]], information may flow in four directions: Forward Flow (counter-clockwise) representing Execution Actions; Reverse Flow (clockwise) representing Measurement Actions; Inward Flow (into the [[Information Pool]]) representing Capturing Actions; and Outward Flow representing Sharing Actions","altLabels":[],"status":"canonical","register":"canonical","grounding":"pending"},{"iri":"https://w3id.org/bimei/term/information-gate","slug":"information-gate","label":"Information Gate","description":"A mechanism for allowing/disallowing information flows along [[Information Route]]s and in/out from the [[Information Pool]]","altLabels":[],"status":"canonical","register":"canonical","grounding":"pending"},{"iri":"https://w3id.org/bimei/term/information-lifecycle","slug":"information-lifecycle","label":"Information Lifecycle","description":"The full duration that [[Information]] is usable. The Information Lifecycle may span a single or multiple [[Information Cycle]]s. An Information Cyle is different than an [[Asset Life Cycle]] as the [[Information]] about an [[Asset]] may persist even if the Asset is decommissioned, demolished, or no longer available","altLabels":[],"status":"canonical","register":"canonical","grounding":"pending"},{"iri":"https://w3id.org/bimei/term/information-loop","slug":"information-loop","label":"Information Loop","description":"The path that [[Information]] travels along due to an iteration. In the [[LITE framework]], there are three potential Information Loops: [a] Short Information Loop indicating a Design Iteration (a partial or complete re-design of an asset, or a variation in a [[Digital Asset]]'s Levels of X); [b] Long Information Loop indicating a re-construction, re-manufacturing, customisation, and/or a correction of a design, construction, fabrication, or installation error; and [c] Full Information Loop spanning the whole [[Information Lifecycle]] and indicating a partial or full reuse of an Existing [[Asset]]","altLabels":[],"status":"canonical","register":"canonical","grounding":"pending"},{"iri":"https://w3id.org/bimei/term/information-management","slug":"information-management","label":"Information Management","description":"The collection, classification, storage and redistribution of information in digital, audio-visual or paper form. Information Management also refers to the ability of an organization to harvest and make-use of information to drive its decision-making process","altLabels":[],"status":"canonical","register":"canonical","grounding":"pending"},{"iri":"https://w3id.org/bimei/term/information-management-policy","slug":"information-management-policy","label":"Information Management Policy","description":"A statement of an organisation's principles, commitments and rules for how information is created, shared, secured, retained and disposed of across its projects and assets. It guides the preparation of [[Organisational Information Requirements]] and project-level [[Information Management]] processes","altLabels":[],"status":"canonical","register":"canonical","grounding":"pending"},{"iri":"https://w3id.org/bimei/term/information-management-process","slug":"information-management-process","label":"Information Management Process","description":"The process covering all [[Information Management]] activities and tasks during the [[Operation Phase]] of a project. The Information Management Process (IMP)  covers the whole operational lifecycle of an asset including: handover from [[Design Phase]] and [[Construction Phase]]; daily operations and maintenance; minor and major works; and decommissioning/demolition","altLabels":[],"status":"canonical","register":"canonical","grounding":"pending"},{"iri":"https://w3id.org/bimei/term/information-management-responsibility-matrix","slug":"information-management-responsibility-matrix","label":"Information Management Responsibility Matrix","description":"Information Management Responsibility Matrix supports establishing the scope of efforts and services. This [[Responsibility Matrix]] is generated by the [[Appointing Party]] (or its representative) and includes assignments of [[Information Management]] activities to all parties using an 'assignment key' similar to the RACI system: [R] Responsible for undertaking the activity; [A] Accountable for activity completion; [C] Consulted during activity; and [I] Informed following activity completion","altLabels":["Information Management Responsibility Matrices"],"status":"canonical","register":"canonical","grounding":"pending"},{"iri":"https://w3id.org/bimei/term/information-manager","slug":"information-manager","label":"Information Manager","description":"A [[BIM Role]] responsible for managing information on behalf of a party, as distinct from producing it. The job title predates ISO 19650: [[ISO 19650-1]] (7.1) speaks instead of information management functions, and warns against confusing them with job titles or with design responsibility. Under [[ISO 19650-2]], the [[Appointing Party]] appoints individuals to undertake its information management function at the start of a project (5.1.1), and each prospective [[Lead Appointed Party]] nominates individuals for the same function within its [[Delivery Team]] (5.3.1). In practice, an information manager sets up or runs the [[Common Data Environment]], applies the project's [[Information Standard]] and information production methods and procedures, checks deliverables against the [[Exchange Information Requirements]], and helps to compile and track the delivery plans. On smaller projects the function may sit with project management, design leadership or construction leadership; on larger ones it may be split, for example by adding a separate information facilitation role. In every case the information manager is not responsible for the design content of models, which stays with the authors who produce them","altLabels":["IM"],"status":"canonical","register":"canonical","grounding":"pending"},{"iri":"https://w3id.org/bimei/term/information-milestone","slug":"information-milestone","label":"Information Milestone","description":"A marker along an [[Information Route]]. In the LITE framework, there are eight Information Milestones that [[Information]] may pass through: [1] Intent to Deliver New Assets; [2] [[Expected Physical Deliverable]]s; [3] [[Targeted Digital Deliverable]]s; [4] Needed Resources and Methods; [5] Available Resources and Methods; [6] Actual [[Digital Asset]]s; [7] Actual [[Physical Asset]]s; and [8] Intent to Reuse Existing Assets","altLabels":[],"status":"canonical","register":"canonical","grounding":"pending"},{"iri":"https://w3id.org/bimei/term/information-model","slug":"information-model","label":"Information Model","description":"A set of structured and unstructured [[Information Container]]s that together describe an asset or a project. [[ISO 19650-1]] (4.1) counts geometrical models, schedules and databases as structured information, and documents, video clips and sound recordings as unstructured; physical samples, such as soil or product samples, are brought in by cross-reference. An information model is therefore much broader than a 3D model: the drawings, reports, specifications and data that answer the [[Information Requirement]]s are as much part of it as the geometry. ISO 19650 distinguishes two kinds. The [[Project Information Model]] is built during the delivery phase, and the [[Asset Information Model]] supports the operational phase; information moves between them at the start and end of each project. An information model is rarely held in one file or one place. Each [[Task Team]] produces its own containers, which are combined through [[Federation]] and managed through the [[Common Data Environment]], so that responsibility for each container stays with the party that produced it. How the model is divided into containers, and why, is set out in the [[Federation Strategy]]","altLabels":[],"status":"canonical","register":"canonical","grounding":"pending"},{"iri":"https://w3id.org/bimei/term/information-packet","slug":"information-packet","label":"Information Packet","description":"The unit of information exchange in the [[LITE framework]]: a [[Document]], [[Model]] or [[Data]] set, or a digitised expression of a purpose, requirement, deliverable or activity, that flows between [[Information Milestone]]s along [[Information Route]]s and [[Information Loop]]s, serially or concurrently. Also refer to [[Information Container]]","altLabels":[],"status":"canonical","register":"canonical","grounding":"pending"},{"iri":"https://w3id.org/bimei/term/information-pool","slug":"information-pool","label":"Information Pool","description":"An online database for collating and integrating information throughout an [[Asset Life Cycle]]. A unified Information Pool is progressively populated by [[Information]] collated through [[Information Set]]s","altLabels":[],"status":"canonical","register":"canonical","grounding":"pending"},{"iri":"https://w3id.org/bimei/term/information-protocol","slug":"information-protocol","label":"Information Protocol","description":"The project-specific set of rights, obligations and licensing terms governing how information is produced, shared and used. Under [[ISO 19650-2]] (5.1.8), the [[Appointing Party]] establishes the information protocol at the start of a project and incorporates it into every [[Appointment]]; each [[Lead Appointed Party]] then passes it down to its own appointed parties. It typically covers each party's information management obligations, including use of the [[Common Data Environment]]; warranties and liabilities attached to the [[Project Information Model]]; intellectual property rights; licences to use information during the project and to re-use it after the appointment ends or is terminated; and the use of existing asset information and [[Shared Resource]]s. Where the [[Information Standard]] sets how information is produced, the information protocol sets the terms under which it is produced and used. Unlike a [[Protocol]] in the general sense, which is not binding by itself, the information protocol becomes part of each contract, so one adapted from another project needs legal review. For the operational phase, [[ISO 19650-3]] calls for an equivalent asset information protocol covering the [[Asset Information Model]]","altLabels":["Project Information Protocol","Information Protocols"],"status":"canonical","register":"canonical","grounding":"pending"},{"iri":"https://w3id.org/bimei/term/information-representation-type","slug":"information-representation-type","label":"Information Representation Type","description":"How [[Information]] is represented. There are three Information Representation Types: [[Document]]s, [[Model]]s and [[Data]]","altLabels":[],"status":"canonical","register":"canonical","grounding":"pending"},{"iri":"https://w3id.org/bimei/term/information-requirement","slug":"information-requirement","label":"Information Requirement","description":"The [[Information]] that needs to be collected or processed by an actor - a human and/or machine -  in order to (a) deliver a predefined outcome or to (b) satisfy the explicit demands of a client or authority","altLabels":["Information Specification"],"status":"canonical","register":"canonical","grounding":"pending"},{"iri":"https://w3id.org/bimei/term/information-route","slug":"information-route","label":"Information Route","description":"The path that [[Information]] travels along depending on the [[Degree of Automation]]. In the LITE framework, there are three potential Information Routes: [Route I] Assisted Flow (the longest route); [Route II] Automated and Automatic Flows (instigated by an [[Actor]] or Trigger Event respectively); and [Route III] Autonomous Flow (the shortest route)","altLabels":[],"status":"canonical","register":"canonical","grounding":"pending"},{"iri":"https://w3id.org/bimei/term/information-security","slug":"information-security","label":"Information Security","description":"The protection of information against unauthorised access, use, disclosure, alteration or destruction, preserving its confidentiality, integrity and availability. For built assets, it is addressed alongside physical and personnel measures by [[Security Management]]","altLabels":[],"status":"canonical","register":"canonical","grounding":"pending"},{"iri":"https://w3id.org/bimei/term/information-set","slug":"information-set","label":"Information Set","description":"A combination of [[Document]] or online modules for collecting [[Information]] covering what and why Digital Assets and [[Physical Asset]]s need to be delivered, and how, when, and by whom they need to be designed, delivered, operated, decommissioned, or reused. In the [[LITE framework]], Information Sets collate and integrate Information into a unified [[Information Pool]]","altLabels":[],"status":"canonical","register":"canonical","grounding":"pending"},{"iri":"https://w3id.org/bimei/term/information-shortcut","slug":"information-shortcut","label":"Information Shortcut","description":"Information Shortcuts are [[Information Flow]]s that bypass one or more [[Information Milestone]]s. Information Shortcuts either have a valid reason or represent a potential risk, a divergence from the normative routes. This divergence may cause a decrease in information clarity, an increase in waste, and may indicate wilful avoidance of checking mechanisms within [[Information Gate]]s","altLabels":[],"status":"canonical","register":"canonical","grounding":"pending"},{"iri":"https://w3id.org/bimei/term/information-standard","slug":"information-standard","label":"Information Standard","description":"The project-specific set of rules setting how information is structured, classified, named and exchanged, so that every [[Information Container]] produced by the [[Delivery Team]] is consistent and usable by others. Under [[ISO 19650-2]] (5.1.4), the [[Appointing Party]] establishes the information standard at the start of a project, issues it with the [[Exchange Information Requirements]] at tender, and incorporates it into every [[Appointment]]. It typically names the [[Classification System]] to apply, sets the [[Naming Protocol]] for information containers, lists the open formats for exchanging information, defines how the [[Level of Information Need]] is assigned, and states how information will be used during operation. The prospective [[Lead Appointed Party]] can propose amendments through its [[BIM Execution Plan]], which are agreed with the appointing party when the appointment is confirmed. Despite its name, an information standard is not a published [[Standard]]: it selects and configures published standards and specifications for one project. [[ISO 19650-3]] calls for an equivalent asset information standard for the operational phase, kept consistent with the project's information standard","altLabels":["Project Information Standard","Information Standards"],"status":"canonical","register":"canonical","grounding":"pending"},{"iri":"https://w3id.org/bimei/term/information-state","slug":"information-state","label":"Information State","description":"[[Information]] generated and exchanged throughout the [[Information Lifecycle]] has three Information States: [[Defined Purpose]]s, [[Defined Deliverable]]s, or [[Defined Resources and Methods]]","altLabels":["Information States"],"status":"canonical","register":"canonical","grounding":"pending"},{"iri":"https://w3id.org/bimei/term/information-status","slug":"information-status","label":"Information Status","description":"[[Information]] generated and exchanged throughout the [[Information Lifecycle]] has two Information Statuses: a Targeted Status representing what is intended, needed, or expected; or an Actual Status representing what is realised, available, or measured","altLabels":[],"status":"canonical","register":"canonical","grounding":"pending"},{"iri":"https://w3id.org/bimei/term/information-tier","slug":"information-tier","label":"Information Tier","description":"The the relative integration of [[Asset]] [[Information]] throughout the [[Asset Life Cycle]]. Corresponding to the [[Degree of Integration]], there are five Information Tiers: [0] Referenced Information reside in the overall Information Spectrum; [1] Defined Information are captured through the [[Common Information Environment]]; [2] Managed Infromation are collated into the unified [[Information Pool]]; [3] Integrated Information are populated into the Integrated Information Platform; and [4] Optimised Information are fed into the core Information Reactor","altLabels":[],"status":"canonical","register":"canonical","grounding":"pending"},{"iri":"https://w3id.org/bimei/term/information-use","slug":"information-use","label":"Information Use","description":"Defines what information is needed to deliver a specific project outcome. Information Uses include [[Document Use]]s, [[Model Use]]s and [[Data Use]]s","altLabels":[],"status":"canonical","register":"canonical","grounding":"pending"},{"iri":"https://w3id.org/bimei/term/information-view","slug":"information-view","label":"Information View","description":"How project information is represented to enable its use. There are three types of Information Views: [[Document View]], [[Model View]] and [[Data View]]","altLabels":[],"status":"canonical","register":"canonical","grounding":"pending"},{"iri":"https://w3id.org/bimei/term/information-view-definition","slug":"information-view-definition","label":"Information View Definition","description":"How [[Information View]]s are defined to enable the consistent use of [[Structured Project Information]]. There are three types of Information View Definitions: [[Document View Definition]], [[Model View Definition]] and [[Data View Definition]]","altLabels":[],"status":"canonical","register":"canonical","grounding":"pending"},{"iri":"https://w3id.org/bimei/term/information-viewer","slug":"information-viewer","label":"Information Viewer","description":"The software allowing access to [[Structured Project Information]] by a solitary user. There are three types of Information Viewers: [[Document Viewer]], [[Model Viewer]] and [[Data Viewer]]","altLabels":[],"status":"canonical","register":"canonical","grounding":"pending"},{"iri":"https://w3id.org/bimei/term/infrastructure-model","slug":"infrastructure-model","label":"Infrastructure Model","description":"A type of [[BIModel]] representing large civil projects similar to highways, railways and ports...Also refer to [[City Model]]s","altLabels":[],"status":"canonical","register":"canonical","grounding":"pending"}]}