{"iri":"https://w3id.org/bimei/term/clash-detection-cycle","type":"term","register":"canonical","status":"canonical","grounding":"pending","liveVersion":1,"pinned":false,"version":null,"provenance":{"sourceApp":"bimd-curator","sourceId":null,"changeSource":"override","curator":"Bilal Succar","curatorRole":"Head Editor"},"language":"en","jurisdiction":null,"label":{"lang":"en","jurisdiction":null,"requestedJurisdiction":null,"fellBack":false,"prefLabel":"Clash Detection Cycle","description":"One round of [[Clash Detection]] on a project: discipline models are combined into a [[Federated Model]], tested against agreed rules, and the resulting clashes are grouped, reviewed, assigned and either resolved or recorded as accepted. Cycles repeat at an agreed frequency, such as weekly, or ahead of set [[Information Delivery Milestone]]s, until the open clashes meet the project's acceptance criteria. Defining the cycles sets who runs each test, which models and clash types it covers, which tolerances apply, and how issues are carried between rounds, usually through [[Issue Management]]","altLabels":[]},"labels":{"en":{"*":{"prefLabel":"Clash Detection Cycle","description":"One round of [[Clash Detection]] on a project: discipline models are combined into a [[Federated Model]], tested against agreed rules, and the resulting clashes are grouped, reviewed, assigned and either resolved or recorded as accepted. Cycles repeat at an agreed frequency, such as weekly, or ahead of set [[Information Delivery Milestone]]s, until the open clashes meet the project's acceptance criteria. Defining the cycles sets who runs each test, which models and clash types it covers, which tolerances apply, and how issues are carried between rounds, usually through [[Issue Management]]","altLabels":[]}}},"seeAlso":["https://w3id.org/bimei/term/bim-collaboration-format","https://w3id.org/bimei/term/clash-detection","https://w3id.org/bimei/term/hard-clash","https://w3id.org/bimei/term/issue-management","https://w3id.org/bimei/term/soft-clash"]}