{"iri":"https://w3id.org/bimei/term/federation-strategy","type":"term","register":"canonical","status":"canonical","grounding":"pending","liveVersion":2,"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":"Federation Strategy","description":"The planned approach for dividing an [[Information Model]] into sets of [[Information Container]]s, and for recombining them through [[Federation]], so that [[Task Team]]s can produce information in parallel without overwriting each other's work. According to [[ISO 19650-1]] (10.4), a federation strategy explains how and why the model is divided, whether by discipline, zone, level, system or security requirement, and is refined into information container breakdown structures showing how individual containers relate. The prospective [[Lead Appointed Party]] proposes it in the pre-appointment [[BIM Execution Plan]] under [[ISO 19650-2]] (5.3.2); it is then agreed collaboratively and updated as new task teams join or the work changes. Each container is normally allocated to a single task team, making responsibility for its content clear. Well-drawn boundaries help avoid spatial and functional conflicts during production rather than detecting them afterwards, and should reflect the [[Level of Information Need]] of each container. Because the strategy reveals how an asset is organised, its circulation may need to be restricted. The result is a [[Federated Model]] that links, rather than merges, the work of each task team","altLabels":["Federation Strategies"]},"labels":{"en":{"*":{"prefLabel":"Federation Strategy","description":"The planned approach for dividing an [[Information Model]] into sets of [[Information Container]]s, and for recombining them through [[Federation]], so that [[Task Team]]s can produce information in parallel without overwriting each other's work. According to [[ISO 19650-1]] (10.4), a federation strategy explains how and why the model is divided, whether by discipline, zone, level, system or security requirement, and is refined into information container breakdown structures showing how individual containers relate. The prospective [[Lead Appointed Party]] proposes it in the pre-appointment [[BIM Execution Plan]] under [[ISO 19650-2]] (5.3.2); it is then agreed collaboratively and updated as new task teams join or the work changes. Each container is normally allocated to a single task team, making responsibility for its content clear. Well-drawn boundaries help avoid spatial and functional conflicts during production rather than detecting them afterwards, and should reflect the [[Level of Information Need]] of each container. Because the strategy reveals how an asset is organised, its circulation may need to be restricted. The result is a [[Federated Model]] that links, rather than merges, the work of each task team","altLabels":["Federation Strategies"]}}},"seeAlso":["https://w3id.org/bimei/term/bim-execution-plan","https://w3id.org/bimei/term/clash-avoidance","https://w3id.org/bimei/term/detailed-responsibility-matrix","https://w3id.org/bimei/term/element-ownership","https://w3id.org/bimei/term/federated-model","https://w3id.org/bimei/term/federation","https://w3id.org/bimei/term/high-level-responsibility-matrix","https://w3id.org/bimei/term/information-container","https://w3id.org/bimei/term/information-security","https://w3id.org/bimei/term/integrated-model","https://w3id.org/bimei/term/task-team"]}