{"type":"term","total":68,"page":1,"items":[{"iri":"https://w3id.org/bimei/term/data","slug":"data","label":"Data","description":"A reinterpretable representation of [[Information]] which can be collected/parsed with or without the human actor. Data is either statically embedded within [[Document]]s and [[Model]]s or drive their dynamic generation/modification [Adapted from ISO/IEC 2382-1:1993]","altLabels":[],"status":"canonical","register":"canonical","grounding":"pending"},{"iri":"https://w3id.org/bimei/term/data-and-network-support","slug":"data-and-network-support","label":"Data and Network Support","description":"BIMe Topic under [[Supportive Competency]]: Managing and maintaining the storage of data, documents, [[2D Drawing]]s and [[BIModel]]s","altLabels":[],"status":"canonical","register":"canonical","grounding":"pending"},{"iri":"https://w3id.org/bimei/term/data-exchange-protocol","slug":"data-exchange-protocol","label":"Data Exchange Protocol","description":"The formal agreement between [[Project Participant]]s covering file formats and [[Data]] specifications to be used when exchanging [[Model]]s, [[Document]]s and other types of [[Structured Project Information]]","altLabels":[],"status":"canonical","register":"canonical","grounding":"pending"},{"iri":"https://w3id.org/bimei/term/data-management","slug":"data-management","label":"Data Management","description":"The activities concerned with controlling the delivery and enhancing the value of data and information assets. Data Management (as a discipline) includes a number of specialties including Data Analysis, Data Security, Data Warehousing and Database Management","altLabels":[],"status":"canonical","register":"canonical","grounding":"pending"},{"iri":"https://w3id.org/bimei/term/data-model","slug":"data-model","label":"Data Model","description":"The \"graphical and/or lexical representation of [[Data]], specifying their properties, structure and inter-relationships\" (Source: ISO/IEC 11179-1:2015, 3.2.7). [[Industry Foundation Classes]] is an example of a Data Model ","altLabels":[],"status":"canonical","register":"canonical","grounding":"pending"},{"iri":"https://w3id.org/bimei/term/data-richness","slug":"data-richness","label":"Data Richness","description":"The extent of data/information embedded within a [[BIModel]], [[Model Component]], [[2D Drawing]], spreadsheet or similar. As an example, a 3D Door element which includes (encapsulates) data about its location, size, door hardware, manufacturer, construction material, fire properties, etc. is considered to be 'data-rich'","altLabels":[],"status":"canonical","register":"canonical","grounding":"pending"},{"iri":"https://w3id.org/bimei/term/data-use","slug":"data-use","label":"Data Use","description":"The intended or expected [[Project Deliverable]] from using code to connect project tasks (e.g. a design task and a fabrication task). An example Data Use (DU) is Fabrication Scripting, the ability/desire to drive a cutting, milling or sintering equipment using scripts triggered from within the [[BIM Software Tool]]","altLabels":["DU"],"status":"canonical","register":"canonical","grounding":"pending"},{"iri":"https://w3id.org/bimei/term/data-view","slug":"data-view","label":"Data View","description":"A view representing one or more [[Data Use]]s. A Data View (DV) can be a spreadsheet, a chart, a code snippet, a [[Computer Numerical Control]] (CNC) file, an XML file or similar. An If This Then That (IFTTT) recipe and a visual script in Autodesk Dynamo are examples of Data Views","altLabels":["DV"],"status":"canonical","register":"canonical","grounding":"pending"},{"iri":"https://w3id.org/bimei/term/data-view-definition","slug":"data-view-definition","label":"Data View Definition","description":"A specification which identifies the properties and specifies the [[Exchange Requirement]]s of [[Data View]]s. Data View Definition (DVD)s are generated by [[Project Participant]]s to formalise their data exchange scenarios","altLabels":["DVD"],"status":"canonical","register":"canonical","grounding":"pending"},{"iri":"https://w3id.org/bimei/term/data-viewer","slug":"data-viewer","label":"Data Viewer","description":"A software application allowing users to inspect and manipulate data according to pre-set [[Data View Definition]]s. An example of a Data Viewer (DVR) is an online project dashboard merging data from several sources","altLabels":["DVR"],"status":"canonical","register":"canonical","grounding":"pending"},{"iri":"https://w3id.org/bimei/term/decision-support-system","slug":"decision-support-system","label":"Decision Support System","description":"A knowledge tool (a software, a checklist or a decision tree) intended to assist users to make an informed decision based on criteria they enter into the tool/system ","altLabels":[],"status":"canonical","register":"canonical","grounding":"pending"},{"iri":"https://w3id.org/bimei/term/defined-deliverable","slug":"defined-deliverable","label":"Defined Deliverable","description":"The [[Expected Physical Deliverable]]s and [[Targeted Digital Deliverable]]s defined at the start of the project according to [[Defined Purpose]]s. A Defined Deliverable is one of three [[Information State]]s within the [[LITE framework]]","altLabels":[],"status":"canonical","register":"canonical","grounding":"pending"},{"iri":"https://w3id.org/bimei/term/defined-method","slug":"defined-method","label":"Defined Method","description":"Defined Methods represents a variety of methods that need to be deployed - alongside [[Defined Resource]]s - to deliver a [[Digital Asset]] or a [[Physical Asset]]. Defined Methods include Procurement Methods - e.g. Cost Plus or [[Target Value Design]], Scheduling Methods - e.g. [[Critical Path Method]] or [[Location Based Scheduling]], [[Project Management]] Methods - e.g. PRINCE2 or PMBOK, Production Methods - e.g. [[Lean Construction]], Six Sigma, or Concurrent Engineering, [[Information Management]] Methods, and Maintenance Methods","altLabels":[],"status":"canonical","register":"canonical","grounding":"pending"},{"iri":"https://w3id.org/bimei/term/defined-purpose","slug":"defined-purpose","label":"Defined Purpose","description":"The explicit reasons behind, the functions needed, and the value sought (commercial, social, and/or environmental value) from procuring a new [[Physical Asset]] or operating/reusing an existing one. While purposes can be Ad-hoc (ill-defined), Defined, Managed, Integrated, or continuously Optimised throughout the Asset lifecycle, for purposes to be reflected in [[Defined Deliverable]]s, they must be well defined. A Defined Purpose is one of three [[Information State]]s within the [[LITE framework]]","altLabels":[],"status":"canonical","register":"canonical","grounding":"pending"},{"iri":"https://w3id.org/bimei/term/defined-resource","slug":"defined-resource","label":"Defined Resource","description":"Defined Resources refer to the human/machine [[actors]], and the physical, technical, financial, and other resources that need to be deployed - alongside [[Defined Method]]s - to transform an [[Expected Physical Deliverable]] into an actual [[Physical Asset]], and a [[Targeted Digital Deliverable]] into an actual [[Digital Asset]]","altLabels":[],"status":"canonical","register":"canonical","grounding":"pending"},{"iri":"https://w3id.org/bimei/term/defined-resources-and-methods","slug":"defined-resources-and-methods","label":"Defined Resources and Methods","description":"A compilation of [[Defined Resource]]s and [[Defined Method]]s. Defined Resources and Methods is one of three [[Information State]]s within the [[LITE framework]]","altLabels":[],"status":"canonical","register":"canonical","grounding":"pending"},{"iri":"https://w3id.org/bimei/term/defined-role","slug":"defined-role","label":"Defined Role","description":"A role with predefined responsibilities established through four Role Taxonomies - Role Class, Role Scale, Role Discipline and Role Location. A Defined Role is one type of [[Knowledge Block]]s and is populated by varied [[Competency Item]]s","altLabels":[],"status":"canonical","register":"canonical","grounding":"pending"},{"iri":"https://w3id.org/bimei/term/definition-of-done","slug":"definition-of-done","label":"Definition of Done","description":"The set of conditions an [[Activity Unit]] in the [[LITE framework]] must satisfy before its [[Activity State]] changes from Completed to Done. An Activity Unit is Done when its [[Execution Action]] is Completed, its coupled [[Measurement Action]] has verified the result against what was targeted, its [[Capturing Action]] has recorded both the result and its verification in the asset's record and, where the unit includes one, its [[Sharing Action]] has released them to the Information Actors who need them; and when no activity, task or step beneath those Actions remains incomplete. The check is made at the [[Activity Gate]]. Done describes the state of the work, not the decision of the [[Information Gate]] receiving it, nor the [[Information Container State]] of the artefacts produced","altLabels":["DoD"],"status":"canonical","register":"canonical","grounding":"pending"},{"iri":"https://w3id.org/bimei/term/degree-of-autonomy","slug":"degree-of-autonomy","label":"Degree of Autonomy","description":"A [[BIMe Metric]] that establishes how automated is the delivery of [[Digital Asset]]s and [[Physical Asset]]s within an [[Information Cycle]]. There are five Degrees of Automation (DoA): [0] Manual; [1] Assisted; [2] Automated; [3] Automatic; and [4] Autonomous [Extended Description to be included]","altLabels":["DoA","Degree of Automation"],"status":"canonical","register":"canonical","grounding":"pending"},{"iri":"https://w3id.org/bimei/term/degree-of-certainty","slug":"degree-of-certainty","label":"Degree of Certainty","description":"A [[BIMe Metric]] that establishes whether an element (or group of elements) has been finalised or is still subject to modification, replacement or removal. Also refer to [[Degree of Specification]]","altLabels":["DoC"],"status":"canonical","register":"canonical","grounding":"pending"},{"iri":"https://w3id.org/bimei/term/degree-of-integration","slug":"degree-of-integration","label":"Degree of Integration","description":"A [[BIMe Metric]] that establishes how integrated a set of information is. There are five Degrees of Integration (DoI): [0] Referenced Information; [1] Defined Information; [2] Managed Information; [3] Integrated Information; and [4] Optimised Information [Extended Description to be included]","altLabels":["DoI"],"status":"canonical","register":"canonical","grounding":"pending"},{"iri":"https://w3id.org/bimei/term/degree-of-specification","slug":"degree-of-specification","label":"Degree of Specification","description":"A [[BIMe Metric]] that establishes how specific is the information included within any requirement or deliverable. As opposed to [[Level of Development]] and [[Level of Model Definition]], which apply exclusively to [[Model Component]]s, the Degree of Specification (DoS) applies to [[Model]]s, [[Document]]s, [[Data]], [[Information Use]]s, and [[Information View]]s. Also refer to [[Degree of Certainty]]","altLabels":["DoS"],"status":"canonical","register":"canonical","grounding":"pending"},{"iri":"https://w3id.org/bimei/term/degrees-of-freedom","slug":"degrees-of-freedom","label":"Degrees of Freedom","description":"The number of basic ways an object can move through physical space. There are six total Degrees of Freedom (DoF): the first three correspond to rotational movement around the x, y, and z axes, commonly termed pitch, yaw, and roll; the other three correspond to translational movement along those axes: moving forwardd or backwardd, moving left or right, and moving up or down. 3 Degrees of Freedom (3DoF) refers to tracking rotational motion but not translational. For example, a Head Mounted Device may allows tracking if users have turned their heads left or right, tilted them up or down, or pivoted left and right. While 6 Degrees of Freedom (6DoF) allows further tracking of translational motion, whether users have moved their heads forwards, backwards, laterally, or vertically","altLabels":["DoF"],"status":"canonical","register":"canonical","grounding":"pending"},{"iri":"https://w3id.org/bimei/term/deliverables-couple","slug":"deliverables-couple","label":"Deliverables Couple","description":"The horizontal [[Milestone Couple]] that pairs [[Expected Physical Deliverable]]s at [[Information Milestone]] 2 with [[Targeted Digital Deliverable]]s at Information Milestone 3, so that the digital deliverables defined are adequate for designing, delivering and using the physical ones. It is the targeted half of the [[Digital-Physical Couple]]","altLabels":[],"status":"canonical","register":"canonical","grounding":"pending"},{"iri":"https://w3id.org/bimei/term/delivery","slug":"delivery","label":"Delivery","description":"The carrying out of planned work to produce, provide, or change an intended asset, service, or outcome.","altLabels":["Project delivery"],"status":"canonical","register":"canonical","grounding":"pending"},{"iri":"https://w3id.org/bimei/term/delivery-phase","slug":"delivery-phase","label":"Delivery Phase","description":"This phase is one \"part of the [[Life Cycle]] during which an [[Asset]] is designed, constructed and commissioned\"[[ISO 19650-1]] (3.2.11)","altLabels":[],"status":"canonical","register":"canonical","grounding":"pending"},{"iri":"https://w3id.org/bimei/term/delivery-specification","slug":"delivery-specification","label":"Delivery Specification","description":"A document identifying the properties of [[BIM Deliverable]]s at the practical completion of a [[BIM Project]]. These properties may include [[Level of Development]], metadata to be embedded (e.g. [[COBie]], [[2D Drawings]]) to be submitted, etc.","altLabels":[],"status":"canonical","register":"canonical","grounding":"pending"},{"iri":"https://w3id.org/bimei/term/delivery-team","slug":"delivery-team","label":"Delivery Team","description":"The “[[Lead Appointed Party]] and their [[Appointed Parties]]” [[ISO 19650-1]] (3.2.6) tasked with delivering a product or a service on a project. A Delivery Team is a subpart of the overall [[Project Team]] and can be of any size, from one person carrying out all the necessary functions through to complex, multi-layered [[Task Team]]s. An example of a [[Delivery Team]] is a structural works contractor, its concrete subcontractors, and their concrete suppliers","altLabels":[],"status":"canonical","register":"canonical","grounding":"pending"},{"iri":"https://w3id.org/bimei/term/demand-entity","slug":"demand-entity","label":"Demand Entity","description":"A Demand Entity is an Information Actor that has the need, authority, and means to require the [[Design, Delivery, and Utilisation]] of a [[Digital Asset]] or [[Physical Asset]]. A Demand Entity can be an organisation, an individual, or a cyber/physical [[Actor]]","altLabels":[],"status":"canonical","register":"canonical","grounding":"pending"},{"iri":"https://w3id.org/bimei/term/demolition-planning","slug":"demolition-planning","label":"Demolition Planning","description":"A [[Model Use]] where 3D models are used to plan or monitor demolition activities of existing structures (or parts of existing structures)","altLabels":["Deconstruction Planning"],"status":"canonical","register":"canonical","grounding":"pending"},{"iri":"https://w3id.org/bimei/term/depth-of-analysis","slug":"depth-of-analysis","label":"Depth of Analysis","description":"The amount of detail that needs to be analysed before the assessment is considered satisfactory. This can be translated in the number of [[Competency Item]]s and the [[Level of Evidence]] used to establish current competency","altLabels":[],"status":"canonical","register":"canonical","grounding":"pending"},{"iri":"https://w3id.org/bimei/term/design-and-construct","slug":"design-and-construct","label":"Design and Construct","description":"A project procurement method in which a client contracts a single organization (a Builder) for the design and construction of a building project","altLabels":["Design and Build"],"status":"canonical","register":"canonical","grounding":"pending"},{"iri":"https://w3id.org/bimei/term/design-authoring","slug":"design-authoring","label":"Design Authoring","description":"A [[Model Use]] representing the process of developing [[Generative Model]]s or [[Parametric Model]]s for design exploration, design communication and design iteration purposes. Design authoring is a key BIM activity leading to model-based [[2D Documentation]], [[3D Detailing]] and other model-based deliverables","altLabels":["Design Optioneering","Design Iteration"],"status":"canonical","register":"canonical","grounding":"pending"},{"iri":"https://w3id.org/bimei/term/design-bid-build","slug":"design-bid-build","label":"Design-Bid-Build","description":"A project procurement method in which a client enters into separate contracts for the design and construction of a building project. The process is as follows: the client contracts a design consultancy for the provision of design documentation which are then used to solicit bids (tendering process) and the successful bidder (a Construction Company) is then contracted separately by the client to build the project","altLabels":[],"status":"canonical","register":"canonical","grounding":"pending"},{"iri":"https://w3id.org/bimei/term/design-construction-and-operation","slug":"design-construction-and-operation","label":"Design, Construction and Operation","description":"A generic term representing all planning-to-demolition activities within the construction industry","altLabels":["DCO","AEC","AECO","AEC/FM"],"status":"canonical","register":"canonical","grounding":"pending"},{"iri":"https://w3id.org/bimei/term/design-consultant","slug":"design-consultant","label":"Design Consultant","description":"The term mainly refers to architects, interior designers,  landscape designers and all types of engineers (e.g. mechanical, structural and electrical) operating with the [[Design Phase]]","altLabels":["Design-Phase Consultant"],"status":"canonical","register":"canonical","grounding":"pending"},{"iri":"https://w3id.org/bimei/term/design-delivery-and-utilisation","slug":"design-delivery-and-utilisation","label":"Design, Delivery, and Utilisation","description":"A generic term representing all information activities to be conducted across an [[Asset]]\\'s [[Information Lifecycle]] (covers both [[Digital Asset]]s and [[Physical Asset]]s). When applied to [[Physical Asset]]s, the term \\'Delivery\\' refers to a variety of onsite/offsite construction, manufacturing, 3D printing, assembly, and installation activities","altLabels":[],"status":"canonical","register":"canonical","grounding":"pending"},{"iri":"https://w3id.org/bimei/term/design-development","slug":"design-development","label":"Design Development","description":"Design Development is part of the [[Design Phase]] and typically occurs after the conclusion of [[Conceptual Design]]. As a project milestone, Design Development is marked by the finalisation of spatial programmes and the detailed resolution of major design elements, their dimensions and material allocations","altLabels":["DD","Design Application (DA)"],"status":"canonical","register":"canonical","grounding":"pending"},{"iri":"https://w3id.org/bimei/term/design-lead","slug":"design-lead","label":"Design Lead","description":"The Design Lead (or Lead Consultant) is the role played by a consultant organisation within a [[Project Team]] to coordinate all design work and act as the main point of contact between the client and the consultant team","altLabels":[],"status":"canonical","register":"canonical","grounding":"pending"},{"iri":"https://w3id.org/bimei/term/design-model","slug":"design-model","label":"Design Model","description":"Design Model (DModel) is an object-based 3D model generated by the Design Team (individually or as a group) for the purposes of design analysis, [[Clash Detection]] and documentation","altLabels":["DModel"],"status":"canonical","register":"canonical","grounding":"pending"},{"iri":"https://w3id.org/bimei/term/design-phase","slug":"design-phase","label":"Design Phase","description":"The Design Phase is the first of three [[Project Lifecycle Phase]]s and includes all pre-construction activities. The Design Phase typically consists of space programming, design coordination and design specification","altLabels":["Design Lifecycle Phase"],"status":"canonical","register":"canonical","grounding":"pending"},{"iri":"https://w3id.org/bimei/term/design-specification","slug":"design-specification","label":"Design Specification","description":"A document identifying spatial, design and/or [[Building Performance]] metrics expected from a [[Project Participant]]. Design Specifications typically detail expectations/requirements which can be later compared to actual deliverables","altLabels":["Design Brief","Program for Design (NATSPEC)"],"status":"canonical","register":"canonical","grounding":"pending"},{"iri":"https://w3id.org/bimei/term/detailed-responsibility-matrix","slug":"detailed-responsibility-matrix","label":"Detailed Responsibility Matrix","description":"An updated or refined version of the [[High Level Responsibility Matrix]]. This type of [[Responsibility Matrix]] identifies (i) what information to be produced; (ii) when and with whom the [[Information]] will be exchanged; and (iii) which [[Task Team]] will be responsible for its production. The Detailed Responsibility Matrix is generated by the [[Lead Appointed Party]] during the establishment of the appointment [[BIM Execution Plan]] then later updated and maintained throughout project [[Life Cycle]]","altLabels":["Detailed Responsibility Matrices"],"status":"canonical","register":"canonical","grounding":"pending"},{"iri":"https://w3id.org/bimei/term/dictionary-item","slug":"dictionary-item","label":"Dictionary Item","description":"A term with its description(s), abbreviation and synonym(s). As a [[Knowledge Block]], the Dictionary Item is connected to other blocks (e.g. [[Competency Item]]s, [[Model Use]]s and [[Defined Role]]s)","altLabels":[],"status":"canonical","register":"canonical","grounding":"pending"},{"iri":"https://w3id.org/bimei/term/diffusion-areas-model","slug":"diffusion-areas-model","label":"Diffusion Areas Model","description":"A [[Macro Adoption Model]] for establishing which specific diffusion area (e.g. Modelling Policies or Collaboration Processes) to be assessed","altLabels":[],"status":"canonical","register":"canonical","grounding":"pending"},{"iri":"https://w3id.org/bimei/term/digital-asset","slug":"digital-asset","label":"Digital Asset","description":"A 3D model, document, or data set that simulates or replicates a [[Physical Asset]]. A Digital Asset may enable the delivery of a Physical Asset or may be generated out of a Physical Asset","altLabels":[],"status":"canonical","register":"canonical","grounding":"pending"},{"iri":"https://w3id.org/bimei/term/digital-asset-management","slug":"digital-asset-management","label":"Digital Asset Management","description":"Digital Asset Management (DAM) is a software solution for storing and retrieving digital assets within an organization. DAM differs from [[Content Management System]]s and [[Document Management System]]s in its focus on multimedia resources such as audio, video, and still images","altLabels":["DAM"],"status":"canonical","register":"canonical","grounding":"pending"},{"iri":"https://w3id.org/bimei/term/digital-couple","slug":"digital-couple","label":"Digital Couple","description":"The vertical [[Milestone Couple]] that pairs [[Targeted Digital Deliverable]]s at [[Information Milestone]] 3 with the actual [[Digital Asset]]s at Information Milestone 6, so that delivered models, documents and data sets can be checked against what was targeted","altLabels":[],"status":"canonical","register":"canonical","grounding":"pending"},{"iri":"https://w3id.org/bimei/term/digital-physical-couple","slug":"digital-physical-couple","label":"Digital-Physical Couple","description":"The pairing of [[Digital Asset]]s with the [[Physical Asset]]s they define or represent throughout the [[Asset Life Cycle]], from the [[Deliverables Couple]] (targeted digital and expected physical deliverables) to the [[Assets Couple]] (actual digital and physical assets). Changes in one are reflected in the other through [[Asset Coupling]], at a given [[Coupling Level]]. A [[Digital Twin]] is a reduced form of this couple, usually limited to the Assets Couple after delivery","altLabels":[],"status":"canonical","register":"canonical","grounding":"pending"},{"iri":"https://w3id.org/bimei/term/digital-plan-of-work","slug":"digital-plan-of-work","label":"Digital Plan of Work","description":"A historic UK concept: a generic schedule of phases, roles, responsibilities, assets and attributes, made available in a computable form to complement the Employer's Information Requirements (see [[BS 1192-4]]). The NBS BIM Toolkit implemented a Digital Plan of Work (dPoW)","altLabels":[],"status":"canonical","register":"canonical","grounding":"pending"}]}