<?xml version="1.0"?>
<?xml-stylesheet type="text/css" href="https://www.designingbuildings.co.uk/skins/common/feed.css?301"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
		<id>https://www.designingbuildings.co.uk/w/index.php?feed=atom&amp;target=NXUS-BIM&amp;title=Special%3AContributions%2FNXUS-BIM</id>
		<title>Designing Buildings - User contributions [en]</title>
		<link rel="self" type="application/atom+xml" href="https://www.designingbuildings.co.uk/w/index.php?feed=atom&amp;target=NXUS-BIM&amp;title=Special%3AContributions%2FNXUS-BIM"/>
		<link rel="alternate" type="text/html" href="https://www.designingbuildings.co.uk/wiki/Special:Contributions/NXUS-BIM"/>
		<updated>2026-05-06T10:17:07Z</updated>
		<subtitle>From Designing Buildings</subtitle>
		<generator>MediaWiki 1.17.4</generator>

	<entry>
		<id>https://www.designingbuildings.co.uk/wiki/Exo-BIM</id>
		<title>Exo-BIM</title>
		<link rel="alternate" type="text/html" href="https://www.designingbuildings.co.uk/wiki/Exo-BIM"/>
				<updated>2023-01-27T09:35:55Z</updated>
		
		<summary type="html">&lt;p&gt;NXUS-BIM: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Exo-BIM describes a design or data authoring process conducted outside of the central collaborative BIM process and its federated model volumes. The method or process is external to the project team's agreed, live integrated and collaborative data set, and as such cannot respond and react to the developing conditions in a timely and effective way.&lt;br /&gt;
&lt;br /&gt;
In any circumstance where a project has implemented defined and managed BIM protocols for all consultants stakeholders and the supply chains for defined stages of the project.For a project contributor to develop their models, drawings or data outside of that system is considered exo-BIM.&lt;br /&gt;
&lt;br /&gt;
Exo-BIM may also be a process that uses drawings or data exported from a volume from within the central collaborative BIM process, and is then developed with in non-object based CAD software, or derived from sources other than the live 3D modelled building fabric and other modelled assets within it.&lt;br /&gt;
&lt;br /&gt;
In conclusion, exo-BIM is project data or information exchanged within a BIM protocol defined IM environment, but is not derived directly from one of the BIM Volumes listed in the volume strategy for that project.&lt;br /&gt;
&lt;br /&gt;
For comparison see: [https://www.designingbuildings.co.uk/wiki/Endo-BIM Endo-BIM - Designing Buildings]&lt;br /&gt;
&lt;br /&gt;
= Related articles on Designing Buildings =&lt;br /&gt;
&lt;br /&gt;
* BIM articles.&lt;br /&gt;
* BIM dimensions.&lt;br /&gt;
* BIM execution plan.&lt;br /&gt;
* BIM glossary of terms.&lt;br /&gt;
* BIM maturity levels.&lt;br /&gt;
* BIM resources.&lt;br /&gt;
* Construction Operations Building Information Exchange (COBie).&lt;br /&gt;
* Common data environment.&lt;br /&gt;
* Industry Foundation Classes.&lt;br /&gt;
* Information management.&lt;br /&gt;
* Level of detail.&lt;br /&gt;
* Revit.&lt;br /&gt;
* Soft landings.&lt;br /&gt;
* Uniclass.&lt;/div&gt;</summary>
		<author><name>NXUS-BIM</name></author>	</entry>

	<entry>
		<id>https://www.designingbuildings.co.uk/wiki/Endo-BIM</id>
		<title>Endo-BIM</title>
		<link rel="alternate" type="text/html" href="https://www.designingbuildings.co.uk/wiki/Endo-BIM"/>
				<updated>2023-01-27T09:34:58Z</updated>
		
		<summary type="html">&lt;p&gt;NXUS-BIM: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Endo-BIM =&lt;br /&gt;
&lt;br /&gt;
Endo-BIM describes a design or data authoring process derived and executed within the central collaborative BIMprocess and one of its federated model volumes. The method or processes are integrated with the current approved BIM volumes and as such responds and reacts to the developing conditions in a timely and effective way.&lt;br /&gt;
&lt;br /&gt;
Endo-BIM occurs in circumstance where a project has implemented, defined and managed BIM protocols for all consultants stakeholders and the supply chains for defined stages of the project. For a project contributor to develop their models, drawings or data within those defined constraints is considered Endo-BIM .&lt;br /&gt;
&lt;br /&gt;
Endo-BIM can never be a process that develops drawings or data exported from an exchaged BIM volume taken from the central collaborative BIM process, and is then developed within non-object based CAD software, or derived from sources other than the live 3D modelled building fabric and/or other modelled assets within it.&lt;br /&gt;
&lt;br /&gt;
In conclusion, Endo-BIM is a process that produces project data or information exchanged within a BIM protocol defined IM environment, which itself is derived directly from one of the BIM Volumes listed in the volume strategy for that project.&lt;br /&gt;
&lt;br /&gt;
For comparison see: [https://www.designingbuildings.co.uk/w/index.php?title=%3AExo-BIM&amp;amp;amp;action=edit Editing Exo-BIM - Designing Buildings]&lt;br /&gt;
&lt;br /&gt;
= Related articles on Designing Buildings =&lt;br /&gt;
&lt;br /&gt;
* BIM articles.&lt;br /&gt;
* BIM dimensions.&lt;br /&gt;
* BIM execution plan.&lt;br /&gt;
* BIM glossary of terms.&lt;br /&gt;
* BIM maturity levels.&lt;br /&gt;
* BIM resources.&lt;br /&gt;
* Construction Operations Building Information Exchange (COBie).&lt;br /&gt;
* Common data environment.&lt;br /&gt;
* Industry Foundation Classes.&lt;br /&gt;
* Information management.&lt;br /&gt;
* Level of detail.&lt;br /&gt;
* Revit.&lt;br /&gt;
* Soft landings.&lt;br /&gt;
* Uniclass.&lt;br /&gt;
&lt;br /&gt;
[[Category:DCN_Definition]] [[Category:DCN_Software]] [[Category:Definitions]] [[Category:Research_/_Innovation]]&lt;/div&gt;</summary>
		<author><name>NXUS-BIM</name></author>	</entry>

	<entry>
		<id>https://www.designingbuildings.co.uk/wiki/Exo-BIM</id>
		<title>Exo-BIM</title>
		<link rel="alternate" type="text/html" href="https://www.designingbuildings.co.uk/wiki/Exo-BIM"/>
				<updated>2023-01-27T09:34:25Z</updated>
		
		<summary type="html">&lt;p&gt;NXUS-BIM: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Exo-BIM describes a design or data authoring process conducted outside of the central collaborative BIM process and its federated model volumes. The method or process is external to the project team's agreed, live integrated and collaborative data set, and as such cannot respond and react to the developing conditions in a timely and effective way.&lt;br /&gt;
&lt;br /&gt;
In any circumstance where a project has implemented defined and managed BIM protocols for all consultants stakeholders and the supply chains for defined stages of the project.For a project contributor to develop their models, drawings or data outside of that system is considered exo-BIM.&lt;br /&gt;
&lt;br /&gt;
Exo-BIM may also be a process that uses drawings or data exported from a volume from within the central collaborative BIM process, and is then developed with in non-object based CAD software, or derived from sources other than the live 3D modelled building fabric and other modelled assets within it.&lt;br /&gt;
&lt;br /&gt;
In conclusion, exo-BIM is project data or information exchanged within a BIM protocol defined IM environment, but is not derived directly from one of the BIM Volumes listed in the volume strategy for that project.&lt;br /&gt;
&lt;br /&gt;
For comparison see: [https://www.designingbuildings.co.uk/wiki/Endo-BIM Endo-BIM - Designing Buildings]&lt;/div&gt;</summary>
		<author><name>NXUS-BIM</name></author>	</entry>

	<entry>
		<id>https://www.designingbuildings.co.uk/wiki/Information_Rejection</id>
		<title>Information Rejection</title>
		<link rel="alternate" type="text/html" href="https://www.designingbuildings.co.uk/wiki/Information_Rejection"/>
				<updated>2023-01-13T14:56:18Z</updated>
		
		<summary type="html">&lt;p&gt;NXUS-BIM: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Background =&lt;br /&gt;
&lt;br /&gt;
BIM protocols for an organisation or project may state that Appointed Parties must deliver the project information files in accordance those agreed BIM protocols. The industry sometimes finds that Appointed Parties agree to implement BIM processes as the source of their design, and that their deliverables will be derived, exported or 'cut' from their project BIM volume(s), but they fail to do so and instead implement exo-BIM processes. Due in some cases to lack of skills and competency with the designated design team.&lt;br /&gt;
&lt;br /&gt;
What is sometimes reported by Information Managers and BIM Coordinators are attempts by some consultants to develop their exo-BIM design based on 2D CAD files exported (by a third party in some cases) from the other consultants federated 3D model volumes. The resulting exo-BIM 2D design developed outside of the collaborative process will not adequately take in to account design issues including clashes with other consultants's design intent.&lt;br /&gt;
&lt;br /&gt;
A disparity and time shift between the live 3D federated models typically exchanged fortnightly on the CDE and the exo-BIM derived design occurs, this results in inacuracy, failure to collaborate effectively, delays on site and reduced overall value to the client.&lt;br /&gt;
&lt;br /&gt;
= Concept =&lt;br /&gt;
&lt;br /&gt;
&amp;amp;quot;Information Rejection&amp;amp;quot;. IR is the scenario whereby an Appointed Party or supplier attempts to exchange files on a CDE that are:&lt;br /&gt;
&lt;br /&gt;
* Not derived from the project team's 3D BIM volume(s)&lt;br /&gt;
* CAD files reverse-BIM'd in to 3D volumes by a third party&lt;br /&gt;
* Exo-BIM data not exported from the BIM volumes e.g. manually added to spreadsheets&lt;br /&gt;
* Non-compliant with project BIM protocols&lt;br /&gt;
* 2D Drawings not derived from the 3D BIM volume(s)&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br /&amp;gt;&lt;br /&gt;
The potential consequences for having exchange information rejected are:&lt;br /&gt;
&lt;br /&gt;
* Responsibility for causing delays&lt;br /&gt;
* Charges imposed for delays&lt;br /&gt;
* Percentage of fees withheld&lt;br /&gt;
* Termination of appointment&lt;br /&gt;
&lt;br /&gt;
= Detection =&lt;br /&gt;
&lt;br /&gt;
To detect the occurance of attempts to exchange drawings and data not derived from the required 'live' 3D BIM volume, the BIM protocols must state that any file exchanged on the CDE must have an associated 3D BIM Volume to verify as the source of that information.&lt;br /&gt;
&lt;br /&gt;
Where a clear disparity between the two occurs, or there is an absence of a 3D BIM Volume to verify the drawing or data against. That will be deemed a breach of the agreed rules and information Rejection will be the resulting action.&lt;br /&gt;
&lt;br /&gt;
= Action =&lt;br /&gt;
&lt;br /&gt;
In the BEP cite a reference to the UK BIM Framework's &amp;amp;quot;Information management according to BS EN ISO 19650 Guidance Part 2: Processes for Project Delivery&amp;amp;quot;.&lt;br /&gt;
&lt;br /&gt;
According to Table 12 in the aforementioned UK BIM Framework document, when exchanged information is audited and verified at Status S6, if rejected the status will be reduced to S0 &amp;amp;quot;Work in Progress and not yet suitable to be Shared outside the task team.&amp;amp;quot;.&lt;br /&gt;
&lt;br /&gt;
Read the references to information acceptance and rejection defined within the aforementioned reference and have the Information Manager and Document Controller implement it via the protocols. See Prevention.&lt;br /&gt;
&lt;br /&gt;
= Prevention =&lt;br /&gt;
&lt;br /&gt;
Create a BIM Services Agreement or similar, to be signed by each Appointed Party or Supplier in a Task Team prior to appointment to a project.&lt;br /&gt;
&lt;br /&gt;
Amongst the descriptions of how and why Appointed Party's must read and understand the BIM protocols, it will be neccessary to defne the resulting actions that will be applied to the responsible party when their exchanged information on the CDE is discovered to be derived from exo-BIM sources and methods.&lt;br /&gt;
&lt;br /&gt;
In the BIM ExecutionPlan under standards applied, cite the UK BIM Framework's &amp;amp;quot;Information management according to BS EN ISO 19650 Guidance Part 2: Processes for Project Delivery&amp;amp;quot;.&lt;br /&gt;
&lt;br /&gt;
= Exemplar =&lt;br /&gt;
&lt;br /&gt;
Below is a typical example of how to define the circumstances and outcomes to the Appointed Party(s) if they fail to apply BIM processes in their design and exchanged files:&lt;br /&gt;
&lt;br /&gt;
Information Rejection:&lt;br /&gt;
&lt;br /&gt;
Starting from the first file exchange uploaded to the CDE, all drawings, details, schedules and other data files exchanged will be verified against your 3D .RVT/.IFC model exchanged at the same cycle. Be aware that if the files are found not to be derived from this 3D file, all exchanged files will be rejected and notice given to you for deviating from this agreement. Rejection of your files will have negative consequences with regards to your fees and potential charges imposed for causing delays. Your appointment to this project may also be terminated for breaching this agreement. Refer to the contracts director for further details.&lt;br /&gt;
&lt;br /&gt;
= References =&lt;br /&gt;
&lt;br /&gt;
See Sections 1.3/1.4 and Table 12 in the UK BIM Framework: Information management according to BS EN ISO 19650 Guidance Part 2: Processes for Project Delivery below:&lt;br /&gt;
&lt;br /&gt;
[https://ukbimframework.org/wp-content/uploads/2019/11/ISO-19650-Guidance-Part-2-Single-Page-Print.pdf ISO-19650-Guidance-Part-2-Single-Page-Print.pdf (ukbimframework.org)]&lt;br /&gt;
&lt;br /&gt;
= Related articles on Designing Buildings =&lt;br /&gt;
&lt;br /&gt;
* Asset information requirements AIR.&lt;br /&gt;
* BIM articles.&lt;br /&gt;
* BIM dimensions.&lt;br /&gt;
* BIM execution plan.&lt;br /&gt;
* BIM glossary of terms.&lt;br /&gt;
* BIM maturity levels.&lt;br /&gt;
* BIM resources.&lt;br /&gt;
* Construction Operations Building Information Exchange (COBie).&lt;br /&gt;
* Common data environment.&lt;br /&gt;
* Data drops..&lt;br /&gt;
* Digital information.&lt;br /&gt;
* Digital model.&lt;br /&gt;
* Federated building information model.&lt;br /&gt;
* Government Soft Landings.&lt;br /&gt;
* Industry Foundation Classes.&lt;br /&gt;
* Information management.&lt;br /&gt;
* Revit.&lt;br /&gt;
* Uniclass.&lt;br /&gt;
&lt;br /&gt;
[[Category:DCN_Commentary]] [[Category:DCN_Software]] [[Category:Projects_and_case_studies]] [[Category:Products_/_components]]&lt;/div&gt;</summary>
		<author><name>NXUS-BIM</name></author>	</entry>

	<entry>
		<id>https://www.designingbuildings.co.uk/wiki/Golden_Matrix</id>
		<title>Golden Matrix</title>
		<link rel="alternate" type="text/html" href="https://www.designingbuildings.co.uk/wiki/Golden_Matrix"/>
				<updated>2023-01-13T14:54:40Z</updated>
		
		<summary type="html">&lt;p&gt;NXUS-BIM: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Background =&lt;br /&gt;
&lt;br /&gt;
The concept of the 'Golden Thread' was coined by Dame Judith Hackitt in her 'Golden Thread Report'. The term was utilised in many educational BIM seminars, and it's meaning has since evolved through interpretation within the BIM industry.&lt;br /&gt;
&lt;br /&gt;
For any project delivered using BIM software, standards and processes, there is a recognised need to 'weave' or integrate the processes and deliverables for each project data contributor's exchange data, across all project stages. This it the driver behind the development of a legible integrated and interactive multifaceted matrix.&lt;br /&gt;
&lt;br /&gt;
The resulting framework that supports this outcome is the 'Golden Matrix', which expands upon the original concept of the 'Golden Thread'. The term 'matrix' relates to the organised arrangement of interrelated processes and data deliverables, allowing for planning and monitoring of successful outcomes over the cycle from authoring to delivery.&lt;br /&gt;
&lt;br /&gt;
= [https://www.designingbuildings.co.uk/wiki/Concept Concept] =&lt;br /&gt;
&lt;br /&gt;
&amp;amp;quot;Golden Matrix&amp;amp;quot; describes the [https://www.designingbuildings.co.uk/wiki/Scenario scenario] whereby the process from inception at Tier 1/ultimate client, to occupying tenant or landlord, is planned and delivered via a proven agreed and managed system of protocols, standards, models and data derived from 'Endo-BIM sources, which is handed over at the operations phase. The handover data set is then integrated in to O&amp;amp;amp;M Manuals or CAFM software systems.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br /&amp;gt;&lt;br /&gt;
The handover data set is developed by each of the project contributors listed in the BIM Execution Plan. The project data contributors are typically:&lt;br /&gt;
&lt;br /&gt;
* Lead Designer&lt;br /&gt;
* Task Teams&lt;br /&gt;
* Professional consultants&lt;br /&gt;
* Suppliers&lt;br /&gt;
* Installing/commissioning personnel&lt;br /&gt;
* Operations phase maintenance personnel&lt;br /&gt;
&lt;br /&gt;
= Process =&lt;br /&gt;
&lt;br /&gt;
To successfully achieve an implementable handover data set for the operations phase of a project delivered using BIM software, there is a need for:&lt;br /&gt;
&lt;br /&gt;
* Proven precedent project studies&lt;br /&gt;
* Robust standards useable by all contributors&lt;br /&gt;
* Interim Information Management processes to confirm protocols are being implemented correctly&lt;br /&gt;
* BIM Coordination meetings to feedback to Project Data Contributors&lt;br /&gt;
* Knowledge of intended CAFM/O&amp;amp;amp;M system that will receive the handover data set&lt;br /&gt;
&lt;br /&gt;
= Principles =&lt;br /&gt;
&lt;br /&gt;
Expanding upon the principles for the 'Golden Thread' to a 'Golden Matrix' was necessary to accommodate the overall interconnected process that defines, manages and captures the whole handover project data in an organised and deliverable set of formatted and auditable volumes.&lt;br /&gt;
&lt;br /&gt;
The handover data-set must be developed within overarching protocols and processes to deliver data that is:&lt;br /&gt;
&lt;br /&gt;
* Derived from Endo-BIM sources&lt;br /&gt;
* From a single data source e.g. project CDE&lt;br /&gt;
* Accurate trusted truthful and verified&lt;br /&gt;
* Has an audit path back to the data author&lt;br /&gt;
* Authored in an Open File Format&lt;br /&gt;
* Compliant with standardised schemas&lt;br /&gt;
&lt;br /&gt;
= References =&lt;br /&gt;
&lt;br /&gt;
See below:&lt;br /&gt;
&lt;br /&gt;
[https://www.gov.uk/government/publications/building-regulations-advisory-committee-golden-thread-report/building-regulations-advisory-committee-golden-thread-report Building Regulations Advisory Committee: golden thread report - GOV.UK (www.gov.uk)]&lt;br /&gt;
&lt;br /&gt;
[https://www.thenbs.com/knowledge/what-is-the-golden-thread https://www.thenbs.com/knowledge/what-is-the-golden-thread]&lt;br /&gt;
&lt;br /&gt;
[https://www.net-ubiep.eu/standards-databases-10/ 3D Matrix | Net-UBIEP]&lt;br /&gt;
&lt;br /&gt;
[https://www.net-ubiep.eu/wp-content/uploads/2017/09/D30-D5.2-Second-Report-on-CEN-existing-standards.pdf D30-D5.2-Second-Report-on-CEN-existing-standards.pdf (net-ubiep.eu)]&lt;br /&gt;
&lt;br /&gt;
[https://www.net-ubiep.eu/wp-content/uploads/2017/09/D29-D5.1-First-report-on-CEN-existing-standards.pdf D29-D5.1-First-report-on-CEN-existing-standards.pdf (net-ubiep.eu)]&lt;br /&gt;
&lt;br /&gt;
[https://www.cencenelec.eu/about-cen/cen-and-iso-cooperation/ CEN and ISO Cooperation - CEN-CENELEC (cencenelec.eu)]&lt;/div&gt;</summary>
		<author><name>NXUS-BIM</name></author>	</entry>

	<entry>
		<id>https://www.designingbuildings.co.uk/wiki/Golden_Matrix</id>
		<title>Golden Matrix</title>
		<link rel="alternate" type="text/html" href="https://www.designingbuildings.co.uk/wiki/Golden_Matrix"/>
				<updated>2023-01-11T16:11:06Z</updated>
		
		<summary type="html">&lt;p&gt;NXUS-BIM: Created page with &amp;quot;= Background =  The concept of the 'Golden Thread' was coined by Dame Judith Hackitt in her 'Golden Thread Report'. The term was utilised in many educational BIM seminars, and it...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Background =&lt;br /&gt;
&lt;br /&gt;
The concept of the 'Golden Thread' was coined by Dame Judith Hackitt in her 'Golden Thread Report'. The term was utilised in many educational BIM seminars, and it's meaning has since evolved through interpretation within the BIM industry.&lt;br /&gt;
&lt;br /&gt;
For any project delivered using BIM software, standards and processes, there is a recognised need to weave or integrate the processes and deliverables for each Project Data Contributor's exchange data, across all project stages, to form a legible and interactive matrix.&lt;br /&gt;
&lt;br /&gt;
The framework that supports this outcome is the 'Golden Matrix', which expands upon the original concept of the 'Golden Thread'. The term 'matrix' relates to the organised arrangement of interelated processes and data deliverables, allowing for planning and monitoring of successful outcomes over the cycle from authoring to delivery.&lt;br /&gt;
&lt;br /&gt;
= [https://www.designingbuildings.co.uk/wiki/Concept Concept] =&lt;br /&gt;
&lt;br /&gt;
&amp;amp;quot;Golden Matrix&amp;amp;quot; described the [https://www.designingbuildings.co.uk/wiki/Scenario scenario] whereby the process from inception at Tier 1 ultimate client, to occupying tenant or landlord, is planned and delivered via a proven agreed and managed system of protocols, standards, models and data from 'Endo-BIM sources, which is handed over at the operations phase. The handover data set is then integrated in to O&amp;amp;amp;M Manuals or CAFM software systems.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br /&amp;gt;&lt;br /&gt;
The handover data set is developed by each of the project contributors listed in the BIM Execution Plan. Project Data Contributors are typically:&lt;br /&gt;
&lt;br /&gt;
- Lead Designer&lt;br /&gt;
&lt;br /&gt;
- Task Teams&amp;lt;br /&amp;gt;&lt;br /&gt;
- Professional consultants&amp;lt;br /&amp;gt;&lt;br /&gt;
- Suppliers&amp;lt;br /&amp;gt;&lt;br /&gt;
- Installing/commissioning personnel&amp;lt;br /&amp;gt;&lt;br /&gt;
- Operations phase maintenance personnel&lt;br /&gt;
&lt;br /&gt;
= Process =&lt;br /&gt;
&lt;br /&gt;
To successfully achieve an implementable handover data set for the operations phase of a project delivered using BIM software, there is a need for:&lt;br /&gt;
&lt;br /&gt;
- Proven precedent project studies&lt;br /&gt;
&lt;br /&gt;
- Robust standards useable by all contributors&lt;br /&gt;
&lt;br /&gt;
- Interim Information Management processes to confirm protocols are being implemented correctly&lt;br /&gt;
&lt;br /&gt;
- BIM Coordination meetings to feedback to Project Data Contributors&lt;br /&gt;
&lt;br /&gt;
- Knowledge of intended CAFM/O&amp;amp;amp;M system that will receive the handover data set&lt;br /&gt;
&lt;br /&gt;
= Principles =&lt;br /&gt;
&lt;br /&gt;
Expanding upon the principles for the 'Golden Thread' to a 'Golden Matrix' was necessary to accommodate the overall interconnected process that defines, manages and captures the whole handover project data in an organised and deliverable set of formatted and auditable volumes.&lt;br /&gt;
&lt;br /&gt;
The handover data-set must have overarching protocols and processes to deliver data that is:&lt;br /&gt;
&lt;br /&gt;
- Derived from Endo-BIM sources&amp;lt;br /&amp;gt;&lt;br /&gt;
- From a single data source e.g. project CDE&amp;lt;br /&amp;gt;&lt;br /&gt;
- Accurate trusted truthful and verified&amp;lt;br /&amp;gt;&lt;br /&gt;
- Has an audit path back to the data author&amp;lt;br /&amp;gt;&lt;br /&gt;
- Authored in an Open File Format&amp;lt;br /&amp;gt;&lt;br /&gt;
- Compliant with standardised schemas&lt;br /&gt;
&lt;br /&gt;
= References =&lt;br /&gt;
&lt;br /&gt;
See below:&lt;br /&gt;
&lt;br /&gt;
[https://www.gov.uk/government/publications/building-regulations-advisory-committee-golden-thread-report/building-regulations-advisory-committee-golden-thread-report Building Regulations Advisory Committee: golden thread report - GOV.UK (www.gov.uk)]&lt;br /&gt;
&lt;br /&gt;
[https://www.thenbs.com/knowledge/what-is-the-golden-thread https://www.thenbs.com/knowledge/what-is-the-golden-thread]&lt;br /&gt;
&lt;br /&gt;
[https://www.net-ubiep.eu/standards-databases-10/ 3D Matrix | Net-UBIEP]&lt;br /&gt;
&lt;br /&gt;
[https://www.net-ubiep.eu/wp-content/uploads/2017/09/D30-D5.2-Second-Report-on-CEN-existing-standards.pdf D30-D5.2-Second-Report-on-CEN-existing-standards.pdf (net-ubiep.eu)]&lt;br /&gt;
&lt;br /&gt;
[https://www.net-ubiep.eu/wp-content/uploads/2017/09/D29-D5.1-First-report-on-CEN-existing-standards.pdf D29-D5.1-First-report-on-CEN-existing-standards.pdf (net-ubiep.eu)]&lt;br /&gt;
&lt;br /&gt;
[https://www.cencenelec.eu/about-cen/cen-and-iso-cooperation/ CEN and ISO Cooperation - CEN-CENELEC (cencenelec.eu)]&lt;/div&gt;</summary>
		<author><name>NXUS-BIM</name></author>	</entry>

	<entry>
		<id>https://www.designingbuildings.co.uk/wiki/Information_Rejection</id>
		<title>Information Rejection</title>
		<link rel="alternate" type="text/html" href="https://www.designingbuildings.co.uk/wiki/Information_Rejection"/>
				<updated>2023-01-01T17:26:06Z</updated>
		
		<summary type="html">&lt;p&gt;NXUS-BIM: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Background =&lt;br /&gt;
&lt;br /&gt;
BIM protocols for an organisation or project may state that Appointed Parties must deliver the project information files in accordance those agreed BIM protocols. The industry sometimes finds that Appointed Parties agree to implement BIM processes as the source of their design, and that their deliverables will be derived, exported or 'cut' from their project BIM volume(s), but they fail to do so and instead implement exo-BIM processes. Due in some cases to lack of skills and competency with the designated design team.&lt;br /&gt;
&lt;br /&gt;
What is sometimes reported by Information Managers and BIM Coordinators are attempts by some consultants to develop their exo-BIM design based on 2D CAD files exported (by a third party in some cases) from the other consultants federated 3D model volumes. The resulting exo-BIM 2D design developed outside of the collaborative process will not adequately take in to account design issues including clashes with other consultants's design intent.&lt;br /&gt;
&lt;br /&gt;
A disparity and time shift between the live 3D federated models typically exchanged fortnightly on the CDE and the exo-BIM derived design occurs, this results in inacuracy, failure to collaborate effectively, delays on site and reduced overall value to the client.&lt;br /&gt;
&lt;br /&gt;
= Concept =&lt;br /&gt;
&lt;br /&gt;
&amp;amp;quot;Information Rejection&amp;amp;quot;. IR is the scenario whereby an Appointed Party or supplier attempts to exchange files on a CDE that are:&amp;lt;br /&amp;gt;&lt;br /&gt;
&amp;lt;br /&amp;gt;&lt;br /&gt;
- Not derived from the project team's 3D BIM volume(s)&amp;lt;br /&amp;gt;&lt;br /&gt;
- CAD files reverse-BIM'd in to 3D volumes by a third party&amp;lt;br /&amp;gt;&lt;br /&gt;
- Exo-BIM data not exported from the BIM volumes e.g. manually added to spreadsheets&amp;lt;br /&amp;gt;&lt;br /&gt;
- Non-compliant with project BIM protocols&amp;lt;br /&amp;gt;&lt;br /&gt;
- 2D Drawings not derived from the 3D BIM volume(s)&amp;lt;br /&amp;gt;&lt;br /&gt;
&amp;lt;br /&amp;gt;&lt;br /&gt;
The potential consequences for having exchange information rejected are:&amp;lt;br /&amp;gt;&lt;br /&gt;
&amp;lt;br /&amp;gt;&lt;br /&gt;
- Responsibility for causing delays&amp;lt;br /&amp;gt;&lt;br /&gt;
- Charges imposed for delays&amp;lt;br /&amp;gt;&lt;br /&gt;
- Percentage of fees withheld&amp;lt;br /&amp;gt;&lt;br /&gt;
- Termination of appointment&lt;br /&gt;
&lt;br /&gt;
= Detection =&lt;br /&gt;
&lt;br /&gt;
To detect the occurance of attempts to exchange drawings and data not derived from the required 'live' 3D BIM volume, the BIM protocols must state that any file exchanged on the CDE must have an associated 3D BIM Volume to verify as the source of that information.&lt;br /&gt;
&lt;br /&gt;
Where a clear disparity between the two occurs, or there is an absence of a 3D BIM Volume to verify the drawing or data against. That will be deemed a breach of the agreed rules and information Rejection will be the resulting action.&lt;br /&gt;
&lt;br /&gt;
= Action =&lt;br /&gt;
&lt;br /&gt;
In the BEP cite a reference to the UK BIM Framework's &amp;amp;quot;Information management according to BS EN ISO 19650 Guidance Part 2: Processes for Project Delivery&amp;amp;quot;.&lt;br /&gt;
&lt;br /&gt;
According to Table 12 in the aforementioned UK BIM Framework document, when exchanged information is audited and verified at Status S6, if rejected the status will be reduced to S0 &amp;amp;quot;Work in Progress and not yet suitable to be Shared outside the task team.&amp;amp;quot;.&lt;br /&gt;
&lt;br /&gt;
Read the references to information acceptance and rejection defined within the aforementioned reference and have the Information Manager and Document Controller implement it via the protocols. See Prevention.&lt;br /&gt;
&lt;br /&gt;
= Prevention =&lt;br /&gt;
&lt;br /&gt;
Create a BIM Services Agreement or similar, to be signed by each Appointed Party or Supplier in a Task Team prior to appointment to a project.&lt;br /&gt;
&lt;br /&gt;
Amongst the descriptions of how and why Appointed Party's must read and understand the BIM protocols, it will be neccessary to defne the resulting actions that will be applied to the responsible party when their exchanged information on the CDE is discovered to be derived from exo-BIM sources and methods.&lt;br /&gt;
&lt;br /&gt;
In the BIM ExecutionPlan under standards applied, cite the UK BIM Framework's &amp;amp;quot;Information management according to BS EN ISO 19650 Guidance Part 2: Processes for Project Delivery&amp;amp;quot;.&lt;br /&gt;
&lt;br /&gt;
= Exemplar =&lt;br /&gt;
&lt;br /&gt;
Below is a typical example of how to define the circumstances and outcomes to the Appointed Party(s) if they fail to apply BIM processes in their design and exchanged files:&lt;br /&gt;
&lt;br /&gt;
Information Rejection:&lt;br /&gt;
&lt;br /&gt;
Starting from the first file exchange uploaded to the CDE, all drawings, details, schedules and other data files exchanged will be verified against your 3D .RVT/.IFC model exchanged at the same cycle. Be aware that if the files are found not to be derived from this 3D file, all exchanged files will be rejected and notice given to you for deviating from this agreement. Rejection of your files will have negative consequences with regards to your fees and potential charges imposed for causing delays. Your appointment to this project may also be terminated for breaching this agreement. Refer to the contracts director for further details.&lt;br /&gt;
&lt;br /&gt;
= References =&lt;br /&gt;
&lt;br /&gt;
See Sections 1.3/1.4 and Table 12 in the UK BIM Framework: Information management according to BS EN ISO 19650 Guidance Part 2: Processes for Project Delivery below:&lt;br /&gt;
&lt;br /&gt;
[https://ukbimframework.org/wp-content/uploads/2019/11/ISO-19650-Guidance-Part-2-Single-Page-Print.pdf ISO-19650-Guidance-Part-2-Single-Page-Print.pdf (ukbimframework.org)]&lt;br /&gt;
&lt;br /&gt;
= Related articles on Designing Buildings =&lt;br /&gt;
&lt;br /&gt;
* Asset information requirements AIR.&lt;br /&gt;
* BIM articles.&lt;br /&gt;
* BIM dimensions.&lt;br /&gt;
* BIM execution plan.&lt;br /&gt;
* BIM glossary of terms.&lt;br /&gt;
* BIM maturity levels.&lt;br /&gt;
* BIM resources.&lt;br /&gt;
* Construction Operations Building Information Exchange (COBie).&lt;br /&gt;
* Common data environment.&lt;br /&gt;
* Data drops..&lt;br /&gt;
* Digital information.&lt;br /&gt;
* Digital model.&lt;br /&gt;
* Federated building information model.&lt;br /&gt;
* Government Soft Landings.&lt;br /&gt;
* Industry Foundation Classes.&lt;br /&gt;
* Information management.&lt;br /&gt;
* Revit.&lt;br /&gt;
* Uniclass.&lt;br /&gt;
&lt;br /&gt;
[[Category:DCN_Commentary]] [[Category:DCN_Software]] [[Category:Projects_and_case_studies]] [[Category:Products_/_components]]&lt;/div&gt;</summary>
		<author><name>NXUS-BIM</name></author>	</entry>

	<entry>
		<id>https://www.designingbuildings.co.uk/wiki/Information_Rejection</id>
		<title>Information Rejection</title>
		<link rel="alternate" type="text/html" href="https://www.designingbuildings.co.uk/wiki/Information_Rejection"/>
				<updated>2023-01-01T17:20:26Z</updated>
		
		<summary type="html">&lt;p&gt;NXUS-BIM: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Background =&lt;br /&gt;
&lt;br /&gt;
BIM protocols for an organisation or project may state that Appointed Parties must deliver the project information files in accordance those agreed BIM protocols. The industry sometimes finds that Appointed Parties agree to implement BIM processes as the source of their design, and that their deliverables will be derived, exported or 'cut' from their project BIM volume(s), but they fail to do so and instead implement exo-BIM processes. Due in some cases to lack of skills and competency with the designated design team.&lt;br /&gt;
&lt;br /&gt;
What is sometimes reported by Information Managers and BIM Coordinators are attempts by some consultants to develop their exo-BIM design based on 2D CAD files exported (by a third party in some cases) from the other consultants federated 3D model volumes. The resulting exo-BIM 2D design developed outside of the collaborative process will not adequately take in to account design issues including clashes with other consultants's design intent.&lt;br /&gt;
&lt;br /&gt;
A disparity and time shift between the live 3D federated models typically exchanged fortnightly on the CDE and the exo-BIM derived design occurs, this results in inacuracy, failure to collaborate effectively, delays on site and reduced overall value to the client.&lt;br /&gt;
&lt;br /&gt;
= Concept =&lt;br /&gt;
&lt;br /&gt;
&amp;amp;quot;Information Rejection&amp;amp;quot;. IR is the scenario whereby an Appointed Party or supplier attempts to exchange files on a CDE that are:&amp;lt;br /&amp;gt;&lt;br /&gt;
&amp;lt;br /&amp;gt;&lt;br /&gt;
- Not derived from the project team's 3D BIM volume(s)&amp;lt;br /&amp;gt;&lt;br /&gt;
- CAD files reverse-BIM'd in to 3D volumes by a third party&amp;lt;br /&amp;gt;&lt;br /&gt;
- Exo-BIM data not exported from the BIM volumes e.g. manually added to spreadsheets&amp;lt;br /&amp;gt;&lt;br /&gt;
- Non-compliant with project BIM protocols&amp;lt;br /&amp;gt;&lt;br /&gt;
- 2D Drawings not derived from the 3D BIM volume(s)&amp;lt;br /&amp;gt;&lt;br /&gt;
&amp;lt;br /&amp;gt;&lt;br /&gt;
The potential consequences for having exchange information rejected are:&amp;lt;br /&amp;gt;&lt;br /&gt;
&amp;lt;br /&amp;gt;&lt;br /&gt;
- Responsibility for causing delays&amp;lt;br /&amp;gt;&lt;br /&gt;
- Charges imposed for delays&amp;lt;br /&amp;gt;&lt;br /&gt;
- Percentage of fees withheld&amp;lt;br /&amp;gt;&lt;br /&gt;
- Termination of appointment&lt;br /&gt;
&lt;br /&gt;
= Detection =&lt;br /&gt;
&lt;br /&gt;
To detect the occurance of attempts to exchange drawings and data not derived from the required 'live' 3D BIM volume, the BIM protocols must state that any file exchanged on the CDE must have an associated 3D BIM Volume to verify as the source of that information.&lt;br /&gt;
&lt;br /&gt;
Where a clear disparity between the two occurs, or there is an absence of a 3D BIM Volume to verify the drawing or data against. That will be deemed a breach of the agreed rules and information Rejection will be the resulting action.&lt;br /&gt;
&lt;br /&gt;
= Action =&lt;br /&gt;
&lt;br /&gt;
In the BEP cite a reference to the UK BIM Framework's &amp;amp;quot;Information management according to BS EN ISO 19650 Guidance Part 2: Processes for Project Delivery&amp;amp;quot;.&lt;br /&gt;
&lt;br /&gt;
According to Table 12 in the aforementioned UK BIM Framework document, when exchanged information is audited and verified at Status S6, if rejected the status will be reduced to S0 &amp;amp;quot;Work in Progress and not yet suitable to be Shared outside the task team.&amp;amp;quot;.&lt;br /&gt;
&lt;br /&gt;
Read the references to information acceptance and rejection defined within the aforementioned reference and have the Information Manager and Document Controller implement it via the protocols. See Prevention.&lt;br /&gt;
&lt;br /&gt;
= Prevention =&lt;br /&gt;
&lt;br /&gt;
Create a BIM Services Agreement or similar, to be signed by each Appointed Party or Supplier in a Task Team prior to appointment to a project.&lt;br /&gt;
&lt;br /&gt;
Amongst the descriptions of how and why Appointed Party's must read and understand the BIM protocols, it will be neccessary to defne the resulting actions that will be applied to the responsible party when their exchanged information on the CDE is discovered to be derived from exo-BIM sources and methods.&lt;br /&gt;
&lt;br /&gt;
= Exemplar =&lt;br /&gt;
&lt;br /&gt;
Below as a typical example of how to define the circumstances and outcomes to Appointed Party if they fail to apply BIM processes in the design and exchanged files:&lt;br /&gt;
&lt;br /&gt;
Information Rejection:&lt;br /&gt;
&lt;br /&gt;
Starting from the first file exchange uploaded to the CDE, all drawings, details, schedules and other data file exchanged will be verified against your 3D .RVT/.IFC model exchanged at the same cycle. Be aware that if the files are found not to be derived from this 3D file, all exchanged files will be rejected and notice given to you for deviating from this agreement. Rejection of your files will have negative consequences with regards to your fees and potential charges imposed for causing delays. Your appointment to this project may also be terminated for breaching this agreement. Refer to the contracts director for further details.&lt;br /&gt;
&lt;br /&gt;
= References =&lt;br /&gt;
&lt;br /&gt;
See Sections 1.3/1.4 and Table 12 in the UK BIM Framework: Information management according to BS EN ISO 19650 Guidance Part 2: Processes for Project Delivery below:&lt;br /&gt;
&lt;br /&gt;
[https://ukbimframework.org/wp-content/uploads/2019/11/ISO-19650-Guidance-Part-2-Single-Page-Print.pdf ISO-19650-Guidance-Part-2-Single-Page-Print.pdf (ukbimframework.org)]&lt;br /&gt;
&lt;br /&gt;
= Related articles on Designing Buildings =&lt;br /&gt;
&lt;br /&gt;
* Asset information requirements AIR.&lt;br /&gt;
* BIM articles.&lt;br /&gt;
* BIM dimensions.&lt;br /&gt;
* BIM execution plan.&lt;br /&gt;
* BIM glossary of terms.&lt;br /&gt;
* BIM maturity levels.&lt;br /&gt;
* BIM resources.&lt;br /&gt;
* Construction Operations Building Information Exchange (COBie).&lt;br /&gt;
* Common data environment.&lt;br /&gt;
* Data drops..&lt;br /&gt;
* Digital information.&lt;br /&gt;
* Digital model.&lt;br /&gt;
* Federated building information model.&lt;br /&gt;
* Government Soft Landings.&lt;br /&gt;
* Industry Foundation Classes.&lt;br /&gt;
* Information management.&lt;br /&gt;
* Revit.&lt;br /&gt;
* Uniclass.&lt;br /&gt;
&lt;br /&gt;
[[Category:DCN_Commentary]] [[Category:DCN_Software]] [[Category:Projects_and_case_studies]] [[Category:Products_/_components]]&lt;/div&gt;</summary>
		<author><name>NXUS-BIM</name></author>	</entry>

	<entry>
		<id>https://www.designingbuildings.co.uk/wiki/Endo-BIM</id>
		<title>Endo-BIM</title>
		<link rel="alternate" type="text/html" href="https://www.designingbuildings.co.uk/wiki/Endo-BIM"/>
				<updated>2023-01-01T02:39:21Z</updated>
		
		<summary type="html">&lt;p&gt;NXUS-BIM: Created page with &amp;quot;= Endo-BIM =  Endo-[https://www.designingbuildings.co.uk/wiki/Bim BIM] describes a [https://www.designingbuildings.co.uk/wiki/Design design] or [https://www.designingbuildings.co...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Endo-BIM =&lt;br /&gt;
&lt;br /&gt;
Endo-[https://www.designingbuildings.co.uk/wiki/Bim BIM] describes a [https://www.designingbuildings.co.uk/wiki/Design design] or [https://www.designingbuildings.co.uk/wiki/Datum data] authoring process derived and executed within the central [https://www.designingbuildings.co.uk/wiki/Collaborative collaborative] [https://www.designingbuildings.co.uk/wiki/Bim BIM] process and one of its [https://www.designingbuildings.co.uk/wiki/Federated_model federated model] [https://www.designingbuildings.co.uk/wiki/Volume volumes]. The method or processes are integrated with the current approved BIM volumes and as such responds and reacts to the developing [https://www.designingbuildings.co.uk/wiki/Condition conditions] in a timely and effective way.&lt;br /&gt;
&lt;br /&gt;
Endo-[https://www.designingbuildings.co.uk/wiki/Bim BIM] occurs in circumstance where a [https://www.designingbuildings.co.uk/wiki/Project project] has implemented, defined and managed [https://www.designingbuildings.co.uk/wiki/BIM_protocol BIM protocols] for all [https://www.designingbuildings.co.uk/wiki/Consultants consultants] [https://www.designingbuildings.co.uk/wiki/Stakeholders stakeholders] and the [https://www.designingbuildings.co.uk/wiki/Supply_chain supply chains] for defined stages of the [https://www.designingbuildings.co.uk/wiki/Project project]. For a [https://www.designingbuildings.co.uk/wiki/Project project] contributor to develop their [https://www.designingbuildings.co.uk/wiki/Model models], [https://www.designingbuildings.co.uk/wiki/Drawings drawings] or [https://www.designingbuildings.co.uk/wiki/Datum data] within those defined constraints is considered Endo-[https://www.designingbuildings.co.uk/wiki/Bim BIM] .&lt;br /&gt;
&lt;br /&gt;
Endo-[https://www.designingbuildings.co.uk/wiki/Bim BIM] can never be a process that develops [https://www.designingbuildings.co.uk/wiki/Drawings drawings] or [https://www.designingbuildings.co.uk/wiki/Datum data] exported from an exchaged BIM [https://www.designingbuildings.co.uk/wiki/Volume volume] taken from the central [https://www.designingbuildings.co.uk/wiki/Collaborative collaborative] [https://www.designingbuildings.co.uk/wiki/Bim BIM] process, and is then developed within non-object based [https://www.designingbuildings.co.uk/wiki/CAD CAD] [https://www.designingbuildings.co.uk/wiki/Software software], or derived from sources other than the live [https://www.designingbuildings.co.uk/wiki/3D 3D] modelled [https://www.designingbuildings.co.uk/wiki/Building_fabric building fabric] and/or other modelled [https://www.designingbuildings.co.uk/wiki/Asset assets] within it.&lt;br /&gt;
&lt;br /&gt;
In conclusion, Endo-[https://www.designingbuildings.co.uk/wiki/Bim BIM] is a process that produces [https://www.designingbuildings.co.uk/wiki/Project project] [https://www.designingbuildings.co.uk/wiki/Datum data] or [https://www.designingbuildings.co.uk/wiki/Information information] exchanged within a [https://www.designingbuildings.co.uk/wiki/BIM_protocol BIM protocol] defined IM [https://www.designingbuildings.co.uk/wiki/Environment environment], which itself is derived directly from one of the [https://www.designingbuildings.co.uk/wiki/BIM_volume BIM Volumes] listed in the [https://www.designingbuildings.co.uk/wiki/Volume_strategy volume strategy] for that [https://www.designingbuildings.co.uk/wiki/Project project].&lt;/div&gt;</summary>
		<author><name>NXUS-BIM</name></author>	</entry>

	<entry>
		<id>https://www.designingbuildings.co.uk/wiki/Information_Rejection</id>
		<title>Information Rejection</title>
		<link rel="alternate" type="text/html" href="https://www.designingbuildings.co.uk/wiki/Information_Rejection"/>
				<updated>2022-12-18T18:46:19Z</updated>
		
		<summary type="html">&lt;p&gt;NXUS-BIM: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;BACKGROUND&lt;br /&gt;
&lt;br /&gt;
BIM protocols for an organization or project may state that Appointed Parties must deliver the project information files in accordance those agreed BIM protocols. The industry sometimes finds that Appointed Parties agree to implement BIM processes as the source of their design, and that their deliverables will be derived, exported or 'cut' from their project BIM volume(s), but they fail to do so and instead implement exo-BIM processes. Due in some cases to lack of skills and competency with the designated design team.&lt;br /&gt;
&lt;br /&gt;
What is sometimes reported by Information Managers and BIM Coordinators are attempts by some consultants to develop their exo-BIM design based on 2D CAD files exported (by a third party in some cases) from the other consultants federated 3D model volumes. The resulting exo-BIM 2D design developed outside of the colaborative process will not adequately take in to account design issues including clashes with other consultants's design intent.&lt;br /&gt;
&lt;br /&gt;
A disparity and time shift between the live 3D federated models typically exchanged fortnightly on the CDE and the exo-BIM derived design occurs, this results in innacuracy, failure to collaborate effectively, delays on site and reduced overall value to the client.&lt;br /&gt;
&lt;br /&gt;
CONCEPT&lt;br /&gt;
&lt;br /&gt;
&amp;amp;quot;Information Rejection&amp;amp;quot;. IR is the scenario whereby an Appointed Party or supplier attempts to exchange files on a CDE that are:&amp;lt;br /&amp;gt;&lt;br /&gt;
&amp;lt;br /&amp;gt;&lt;br /&gt;
- Not derived from the project team's 3D BIM volume(s)&amp;lt;br /&amp;gt;&lt;br /&gt;
- CAD files reverse-BIM'd in to 3D volumes by a third party&amp;lt;br /&amp;gt;&lt;br /&gt;
- Exo-BIM data not exported from the BIM volumes e.g. manually added to spreadsheets&amp;lt;br /&amp;gt;&lt;br /&gt;
- Non-compliant with project BIM protocols&amp;lt;br /&amp;gt;&lt;br /&gt;
- 2D Drawings not derived from the 3D BIM volume(s)&amp;lt;br /&amp;gt;&lt;br /&gt;
&amp;lt;br /&amp;gt;&lt;br /&gt;
The potential consequences for having exchange information rejected are:&amp;lt;br /&amp;gt;&lt;br /&gt;
&amp;lt;br /&amp;gt;&lt;br /&gt;
- Responsibility for causing delays&amp;lt;br /&amp;gt;&lt;br /&gt;
- Charges imposed for delays&amp;lt;br /&amp;gt;&lt;br /&gt;
- Percentage of fees withheld&amp;lt;br /&amp;gt;&lt;br /&gt;
- Termination of appointment&lt;br /&gt;
&lt;br /&gt;
DETECTION&lt;br /&gt;
&lt;br /&gt;
To detect the occurance of attempts to exchange drawings and data not derived from the required 'live' 3D BIM volume, the BIM protocols must state that any file exchanged on the CDE must have an associated 3D BIM Volume to verify as the source of that information.&lt;br /&gt;
&lt;br /&gt;
Where a clear dsparity between the two occurs, or there is an absence of a 3D BIM Volume to verify the drawing or data against. That will be deemed a breach of the agreed rules and information Rejection will be the resulting action.&lt;br /&gt;
&lt;br /&gt;
PREVENTION&lt;br /&gt;
&lt;br /&gt;
Create a BIM Services Agreement or similar, to be signed by each Appointed Party or Supplier in a Task Team prior to appointment to a project.&lt;br /&gt;
&lt;br /&gt;
Amongst the descriptions of how and why Appointed Party's must read and understand the BIM protocols, it will be neccessary to defne the resulting actions that will be applied to the responsible party when their exchanged information on the CDE is discovered to be derived from exo-BIM sources and methods.&lt;br /&gt;
&lt;br /&gt;
EXEMPLAR&lt;br /&gt;
&lt;br /&gt;
Below as a typical example of how to define the circumstances and outcomes to Appointed Party if they fail to apply BIM processes in the design and exchanged files:&lt;br /&gt;
&lt;br /&gt;
Information Rejection:&lt;br /&gt;
&lt;br /&gt;
Starting from the first file exchange uploaded to the CDE, all drawings, details, schedules and other data file exchanged will be verified against your 3D .RVT/.IFC model exchanged at the same cycle. Be aware that if the files are found not to be derived from this 3D file, all exchanged files will be rejected and notice given to you for deviating from this agreement. Rejection of your files will have negative consequences with regards to your fees and potential charges imposed for causing delays. Your appointment to this project may also be terminated for breaching this agreement. Refer to the contracts director for further details.&lt;/div&gt;</summary>
		<author><name>NXUS-BIM</name></author>	</entry>

	<entry>
		<id>https://www.designingbuildings.co.uk/wiki/Information_Rejection</id>
		<title>Information Rejection</title>
		<link rel="alternate" type="text/html" href="https://www.designingbuildings.co.uk/wiki/Information_Rejection"/>
				<updated>2022-12-18T18:45:21Z</updated>
		
		<summary type="html">&lt;p&gt;NXUS-BIM: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;BACKGROUND&lt;br /&gt;
&lt;br /&gt;
BIM protocols for an organization or project may state that Appointed Parties must deliver the project information files in accordance those agreed BIM protocols. The industry sometimes finds that Appointed Parties agree to implement BIM processes as the source of their design, and that their deliverables will be derived, exported or 'cut' from their project BIM volume(s), but they fail to do so and instead implement exo-BIM processes. Due in some cases to lack of skills and competency with the designated design team.&lt;br /&gt;
&lt;br /&gt;
What is sometimes reported by Information Managers and BIM Coordinators are attempts by some consultants to develop their exo-BIM design in 2D CAD files exported (by a third party in some cases) from the other consultants federated 3D model volumes. The resulting exo-BIM 2D design developed outside of the colaborative process will not adequately take in to account design issues including clashes with other consultants's design intent.&lt;br /&gt;
&lt;br /&gt;
A disparity and time shift between the live 3D federated models typically exchanged fortnightly on the CDE and the exo-BIM derived design occurs, this results in innacuracy, failure to collaborate effectively, delays on site and reduced overall value to the client.&lt;br /&gt;
&lt;br /&gt;
CONCEPT&lt;br /&gt;
&lt;br /&gt;
&amp;amp;quot;Information Rejection&amp;amp;quot;. IR is the scenario whereby an Appointed Party or supplier attempts to exchange files on a CDE that are:&amp;lt;br /&amp;gt;&lt;br /&gt;
&amp;lt;br /&amp;gt;&lt;br /&gt;
- Not derived from the project team's 3D BIM volume(s)&amp;lt;br /&amp;gt;&lt;br /&gt;
- CAD files reverse-BIM'd in to 3D volumes by a third party&amp;lt;br /&amp;gt;&lt;br /&gt;
- Exo-BIM data not exported from the BIM volumes e.g. manually added to spreadsheets&amp;lt;br /&amp;gt;&lt;br /&gt;
- Non-compliant with project BIM protocols&amp;lt;br /&amp;gt;&lt;br /&gt;
- 2D Drawings not derived from the 3D BIM volume(s)&amp;lt;br /&amp;gt;&lt;br /&gt;
&amp;lt;br /&amp;gt;&lt;br /&gt;
The potential consequences for having exchange information rejected are:&amp;lt;br /&amp;gt;&lt;br /&gt;
&amp;lt;br /&amp;gt;&lt;br /&gt;
- Responsibility for causing delays&amp;lt;br /&amp;gt;&lt;br /&gt;
- Charges imposed for delays&amp;lt;br /&amp;gt;&lt;br /&gt;
- Percentage of fees withheld&amp;lt;br /&amp;gt;&lt;br /&gt;
- Termination of appointment&lt;br /&gt;
&lt;br /&gt;
DETECTION&lt;br /&gt;
&lt;br /&gt;
To detect the occurance of attempts to exchange drawings and data not derived from the required 'live' 3D BIM volume, the BIM protocols must state that any file exchanged on the CDE must have an associated 3D BIM Volume to verify as the source of that information.&lt;br /&gt;
&lt;br /&gt;
Where a clear dsparity between the two occurs, or there is an absence of a 3D BIM Volume to verify the drawing or data against. That will be deemed a breach of the agreed rules and information Rejection will be the resulting action.&lt;br /&gt;
&lt;br /&gt;
PREVENTION&lt;br /&gt;
&lt;br /&gt;
Create a BIM Services Agreement or similar, to be signed by each Appointed Party or Supplier in a Task Team prior to appointment to a project.&lt;br /&gt;
&lt;br /&gt;
Amongst the descriptions of how and why Appointed Party's must read and understand the BIM protocols, it will be neccessary to defne the resulting actions that will be applied to the responsible party when their exchanged information on the CDE is discovered to be derived from exo-BIM sources and methods.&lt;br /&gt;
&lt;br /&gt;
EXEMPLAR&lt;br /&gt;
&lt;br /&gt;
Below as a typical example of how to define the circumstances and outcomes to Appointed Party if they fail to apply BIM processes in the design and exchanged files:&lt;br /&gt;
&lt;br /&gt;
Information Rejection:&lt;br /&gt;
&lt;br /&gt;
Starting from the first file exchange uploaded to the CDE, all drawings, details, schedules and other data file exchanged will be verified against your 3D .RVT/.IFC model exchanged at the same cycle. Be aware that if the files are found not to be derived from this 3D file, all exchanged files will be rejected and notice given to you for deviating from this agreement. Rejection of your files will have negative consequences with regards to your fees and potential charges imposed for causing delays. Your appointment to this project may also be terminated for breaching this agreement. Refer to the contracts director for further details.&lt;/div&gt;</summary>
		<author><name>NXUS-BIM</name></author>	</entry>

	<entry>
		<id>https://www.designingbuildings.co.uk/wiki/Information_Rejection</id>
		<title>Information Rejection</title>
		<link rel="alternate" type="text/html" href="https://www.designingbuildings.co.uk/wiki/Information_Rejection"/>
				<updated>2022-12-18T18:44:10Z</updated>
		
		<summary type="html">&lt;p&gt;NXUS-BIM: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;BACKGROUND&lt;br /&gt;
&lt;br /&gt;
BIM protocols for an organization or project may state that Appointed Parties must deliver the project information files in accordance those agreed BIM protocols. The industry sometimes finds that Appointed Parties agree to implement BIM processes as the source of their design, and that their deliverables will be derived, exported or 'cut' from their project BIM volume(s), but they fail to do so and instead implement exo-BIM processes. Due in some cases to lack of skills and competency with the designated design team.&lt;br /&gt;
&lt;br /&gt;
What is sometimes reported by Information Managers and BIM Coordinators are attempts by some consultants to develop their exo-BIM design in 2D CAD files exported (by a third party in some cases) from the other consultants federated 3D model volumes. The resulting exo-BIM 2D design developed outside of the colaborative process will not take in to account design issues including clashes with other consultants's design intent.&lt;br /&gt;
&lt;br /&gt;
A disparity and time shift between the live 3D federated models typically exchanged fortnightly on the CDE and the exo-BIM derived design occurs, this results in innacuracy, failure to collaborate effectively, delays on site and reduced overall value to the client.&lt;br /&gt;
&lt;br /&gt;
CONCEPT&lt;br /&gt;
&lt;br /&gt;
&amp;amp;quot;Information Rejection&amp;amp;quot;. IR is the scenario whereby an Appointed Party or supplier attempts to exchange files on a CDE that are:&amp;lt;br /&amp;gt;&lt;br /&gt;
&amp;lt;br /&amp;gt;&lt;br /&gt;
- Not derived from the project team's 3D BIM volume(s)&amp;lt;br /&amp;gt;&lt;br /&gt;
- CAD files reverse-BIM'd in to 3D volumes by a third party&amp;lt;br /&amp;gt;&lt;br /&gt;
- Exo-BIM data not exported from the BIM volumes e.g. manually added to spreadsheets&amp;lt;br /&amp;gt;&lt;br /&gt;
- Non-compliant with project BIM protocols&amp;lt;br /&amp;gt;&lt;br /&gt;
- 2D Drawings not derived from the 3D BIM volume(s)&amp;lt;br /&amp;gt;&lt;br /&gt;
&amp;lt;br /&amp;gt;&lt;br /&gt;
The potential consequences for having exchange information rejected are:&amp;lt;br /&amp;gt;&lt;br /&gt;
&amp;lt;br /&amp;gt;&lt;br /&gt;
- Responsibility for causing delays&amp;lt;br /&amp;gt;&lt;br /&gt;
- Charges imposed for delays&amp;lt;br /&amp;gt;&lt;br /&gt;
- Percentage of fees withheld&amp;lt;br /&amp;gt;&lt;br /&gt;
- Termination of appointment&lt;br /&gt;
&lt;br /&gt;
DETECTION&lt;br /&gt;
&lt;br /&gt;
To detect the occurance of attempts to exchange drawings and data not derived from the required 'live' 3D BIM volume, the BIM protocols must state that any file exchanged on the CDE must have an associated 3D BIM Volume to verify as the source of that information.&lt;br /&gt;
&lt;br /&gt;
Where a clear dsparity between the two occurs, or there is an absence of a 3D BIM Volume to verify the drawing or data against. That will be deemed a breach of the agreed rules and information Rejection will be the resulting action.&lt;br /&gt;
&lt;br /&gt;
PREVENTION&lt;br /&gt;
&lt;br /&gt;
Create a BIM Services Agreement or similar, to be signed by each Appointed Party or Supplier in a Task Team prior to appointment to a project.&lt;br /&gt;
&lt;br /&gt;
Amongst the descriptions of how and why Appointed Party's must read and understand the BIM protocols, it will be neccessary to defne the resulting actions that will be applied to the responsible party when their exchanged information on the CDE is discovered to be derived from exo-BIM sources and methods.&lt;br /&gt;
&lt;br /&gt;
EXEMPLAR&lt;br /&gt;
&lt;br /&gt;
Below as a typical example of how to define the circumstances and outcomes to Appointed Party if they fail to apply BIM processes in the design and exchanged files:&lt;br /&gt;
&lt;br /&gt;
Information Rejection:&lt;br /&gt;
&lt;br /&gt;
Starting from the first file exchange uploaded to the CDE, all drawings, details, schedules and other data file exchanged will be verified against your 3D .RVT/.IFC model exchanged at the same cycle. Be aware that if the files are found not to be derived from this 3D file, all exchanged files will be rejected and notice given to you for deviating from this agreement. Rejection of your files will have negative consequences with regards to your fees and potential charges imposed for causing delays. Your appointment to this project may also be terminated for breaching this agreement. Refer to the contracts director for further details.&lt;/div&gt;</summary>
		<author><name>NXUS-BIM</name></author>	</entry>

	<entry>
		<id>https://www.designingbuildings.co.uk/wiki/Information_Rejection</id>
		<title>Information Rejection</title>
		<link rel="alternate" type="text/html" href="https://www.designingbuildings.co.uk/wiki/Information_Rejection"/>
				<updated>2022-12-18T18:43:08Z</updated>
		
		<summary type="html">&lt;p&gt;NXUS-BIM: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;BACKGROUND&lt;br /&gt;
&lt;br /&gt;
BIM protocols for an organization or project may state that Appointed Parties must deliver the project information files in accordance those agreed BIM protocols. The industry sometimes finds that Appointed Parties agree to implement BIM processes as the source of their design, and that their deliverables will be derived, exported or 'cut' from the project BIM volumes, but they fail to do so and instead implement exo-BIM processes. Due in some cases to lack of skills and competency with the designated design team.&lt;br /&gt;
&lt;br /&gt;
What is sometimes reported by Information Managers and BIM Coordinators are attempts by some consultants to develop their exo-BIM design in 2D CAD files exported (by a third party in some cases) from the other consultants federated 3D model volumes. The resulting exo-BIM 2D design developed outside of the colaborative process will not take in to account design issues including clashes with other consultants's design intent.&lt;br /&gt;
&lt;br /&gt;
A disparity and time shift between the live 3D federated models typically exchanged fortnightly on the CDE and the exo-BIM derived design occurs, this results in innacuracy, failure to collaborate effectively, delays on site and reduced overall value to the client.&lt;br /&gt;
&lt;br /&gt;
CONCEPT&lt;br /&gt;
&lt;br /&gt;
&amp;amp;quot;Information Rejection&amp;amp;quot;. IR is the scenario whereby an Appointed Party or supplier attempts to exchange files on a CDE that are:&amp;lt;br /&amp;gt;&lt;br /&gt;
&amp;lt;br /&amp;gt;&lt;br /&gt;
- Not derived from the project team's 3D BIM volume(s)&amp;lt;br /&amp;gt;&lt;br /&gt;
- CAD files reverse-BIM'd in to 3D volumes by a third party&amp;lt;br /&amp;gt;&lt;br /&gt;
- Exo-BIM data not exported from the BIM volumes e.g. manually added to spreadsheets&amp;lt;br /&amp;gt;&lt;br /&gt;
- Non-compliant with project BIM protocols&amp;lt;br /&amp;gt;&lt;br /&gt;
- 2D Drawings not derived from the 3D BIM volume(s)&amp;lt;br /&amp;gt;&lt;br /&gt;
&amp;lt;br /&amp;gt;&lt;br /&gt;
The potential consequences for having exchange information rejected are:&amp;lt;br /&amp;gt;&lt;br /&gt;
&amp;lt;br /&amp;gt;&lt;br /&gt;
- Responsibility for causing delays&amp;lt;br /&amp;gt;&lt;br /&gt;
- Charges imposed for delays&amp;lt;br /&amp;gt;&lt;br /&gt;
- Percentage of fees withheld&amp;lt;br /&amp;gt;&lt;br /&gt;
- Termination of appointment&lt;br /&gt;
&lt;br /&gt;
DETECTION&lt;br /&gt;
&lt;br /&gt;
To detect the occurance of attempts to exchange drawings and data not derived from the required 'live' 3D BIM volume, the BIM protocols must state that any file exchanged on the CDE must have an associated 3D BIM Volume to verify as the source of that information.&lt;br /&gt;
&lt;br /&gt;
Where a clear dsparity between the two occurs, or there is an absence of a 3D BIM Volume to verify the drawing or data against. That will be deemed a breach of the agreed rules and information Rejection will be the resulting action.&lt;br /&gt;
&lt;br /&gt;
PREVENTION&lt;br /&gt;
&lt;br /&gt;
Create a BIM Services Agreement or similar, to be signed by each Appointed Party or Supplier in a Task Team prior to appointment to a project.&lt;br /&gt;
&lt;br /&gt;
Amongst the descriptions of how and why Appointed Party's must read and understand the BIM protocols, it will be neccessary to defne the resulting actions that will be applied to the responsible party when their exchanged information on the CDE is discovered to be derived from exo-BIM sources and methods.&lt;br /&gt;
&lt;br /&gt;
EXEMPLAR&lt;br /&gt;
&lt;br /&gt;
Below as a typical example of how to define the circumstances and outcomes to Appointed Party if they fail to apply BIM processes in the design and exchanged files:&lt;br /&gt;
&lt;br /&gt;
Information Rejection:&lt;br /&gt;
&lt;br /&gt;
Starting from the first file exchange uploaded to the CDE, all drawings, details, schedules and other data file exchanged will be verified against your 3D .RVT/.IFC model exchanged at the same cycle. Be aware that if the files are found not to be derived from this 3D file, all exchanged files will be rejected and notice given to you for deviating from this agreement. Rejection of your files will have negative consequences with regards to your fees and potential charges imposed for causing delays. Your appointment to this project may also be terminated for breaching this agreement. Refer to the contracts director for further details.&lt;/div&gt;</summary>
		<author><name>NXUS-BIM</name></author>	</entry>

	<entry>
		<id>https://www.designingbuildings.co.uk/wiki/Information_Rejection</id>
		<title>Information Rejection</title>
		<link rel="alternate" type="text/html" href="https://www.designingbuildings.co.uk/wiki/Information_Rejection"/>
				<updated>2022-12-18T18:42:35Z</updated>
		
		<summary type="html">&lt;p&gt;NXUS-BIM: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;BACKGROUND&lt;br /&gt;
&lt;br /&gt;
BIM protocols for an organization or project may state that Appointed Parties must deliver the project information files in accordance those agreed BIM protocols. The industry sometime finds that Appointed Parties agree to implement BIM processes as the source of their design, and that their deliverables will be derived, exported or 'cut' from the project BIM volumes, but they fail to do so and instead implement exo-BIM processes. Due in some cases to lack of skills and competency with the designated design team.&lt;br /&gt;
&lt;br /&gt;
What is sometimes reported by Information Managers and BIM Coordinators are attempts by some consultants to develop their exo-BIM design in 2D CAD files exported (by a third party in some cases) from the other consultants federated 3D model volumes. The resulting exo-BIM 2D design developed outside of the colaborative process will not take in to account design issues including clashes with other consultants's design intent.&lt;br /&gt;
&lt;br /&gt;
A disparity and time shift between the live 3D federated models typically exchanged fortnightly on the CDE and the exo-BIM derived design occurs, this results in innacuracy, failure to collaborate effectively, delays on site and reduced overall value to the client.&lt;br /&gt;
&lt;br /&gt;
CONCEPT&lt;br /&gt;
&lt;br /&gt;
&amp;amp;quot;Information Rejection&amp;amp;quot;. IR is the scenario whereby an Appointed Party or supplier attempts to exchange files on a CDE that are:&amp;lt;br /&amp;gt;&lt;br /&gt;
&amp;lt;br /&amp;gt;&lt;br /&gt;
- Not derived from the project team's 3D BIM volume(s)&amp;lt;br /&amp;gt;&lt;br /&gt;
- CAD files reverse-BIM'd in to 3D volumes by a third party&amp;lt;br /&amp;gt;&lt;br /&gt;
- Exo-BIM data not exported from the BIM volumes e.g. manually added to spreadsheets&amp;lt;br /&amp;gt;&lt;br /&gt;
- Non-compliant with project BIM protocols&amp;lt;br /&amp;gt;&lt;br /&gt;
- 2D Drawings not derived from the 3D BIM volume(s)&amp;lt;br /&amp;gt;&lt;br /&gt;
&amp;lt;br /&amp;gt;&lt;br /&gt;
The potential consequences for having exchange information rejected are:&amp;lt;br /&amp;gt;&lt;br /&gt;
&amp;lt;br /&amp;gt;&lt;br /&gt;
- Responsibility for causing delays&amp;lt;br /&amp;gt;&lt;br /&gt;
- Charges imposed for delays&amp;lt;br /&amp;gt;&lt;br /&gt;
- Percentage of fees withheld&amp;lt;br /&amp;gt;&lt;br /&gt;
- Termination of appointment&lt;br /&gt;
&lt;br /&gt;
DETECTION&lt;br /&gt;
&lt;br /&gt;
To detect the occurance of attempts to exchange drawings and data not derived from the required 'live' 3D BIM volume, the BIM protocols must state that any file exchanged on the CDE must have an associated 3D BIM Volume to verify as the source of that information.&lt;br /&gt;
&lt;br /&gt;
Where a clear dsparity between the two occurs, or there is an absence of a 3D BIM Volume to verify the drawing or data against. That will be deemed a breach of the agreed rules and information Rejection will be the resulting action.&lt;br /&gt;
&lt;br /&gt;
PREVENTION&lt;br /&gt;
&lt;br /&gt;
Create a BIM Services Agreement or similar, to be signed by each Appointed Party or Supplier in a Task Team prior to appointment to a project.&lt;br /&gt;
&lt;br /&gt;
Amongst the descriptions of how and why Appointed Party's must read and understand the BIM protocols, it will be neccessary to defne the resulting actions that will be applied to the responsible party when their exchanged information on the CDE is discovered to be derived from exo-BIM sources and methods.&lt;br /&gt;
&lt;br /&gt;
EXEMPLAR&lt;br /&gt;
&lt;br /&gt;
Below as a typical example of how to define the circumstances and outcomes to Appointed Party if they fail to apply BIM processes in the design and exchanged files:&lt;br /&gt;
&lt;br /&gt;
Information Rejection:&lt;br /&gt;
&lt;br /&gt;
Starting from the first file exchange uploaded to the CDE, all drawings, details, schedules and other data file exchanged will be verified against your 3D .RVT/.IFC model exchanged at the same cycle. Be aware that if the files are found not to be derived from this 3D file, all exchanged files will be rejected and notice given to you for deviating from this agreement. Rejection of your files will have negative consequences with regards to your fees and potential charges imposed for causing delays. Your appointment to this project may also be terminated for breaching this agreement. Refer to the contracts director for further details.&lt;/div&gt;</summary>
		<author><name>NXUS-BIM</name></author>	</entry>

	<entry>
		<id>https://www.designingbuildings.co.uk/wiki/Information_Rejection</id>
		<title>Information Rejection</title>
		<link rel="alternate" type="text/html" href="https://www.designingbuildings.co.uk/wiki/Information_Rejection"/>
				<updated>2022-12-18T18:40:56Z</updated>
		
		<summary type="html">&lt;p&gt;NXUS-BIM: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;BACKGROUND&lt;br /&gt;
&lt;br /&gt;
BIM protocols for an organization or project may state that Appointed Parties must deliver the project information files in accordance the agreed IM protocols. The industry sometime finds that Appointed Parties agree to implement BIM processes as the source of their design, and that their deliverables will be derived, exported or 'cut' from the project BIM volumes, but they fail to do so and instead implement exo-BIM processes. Due in some cases to lack of skills and competency with the designated design team.&lt;br /&gt;
&lt;br /&gt;
What is sometimes reported by Information Managers and BIM Coordinators are attempts by some consultants to develop their exo-BIM design in 2D CAD files exported (by a third party in some cases) from the other consultants federated 3D model volumes. The resulting exo-BIM 2D design developed outside of the colaborative process will not take in to account design issues including clashes with other consultants's design intent.&lt;br /&gt;
&lt;br /&gt;
A disparity and time shift between the live 3D federated models typically exchanged fortnightly on the CDE and the exo-BIM derived design occurs, this results in innacuracy, failure to collaborate effectively, delays on site and reduced overall value to the client.&lt;br /&gt;
&lt;br /&gt;
CONCEPT&lt;br /&gt;
&lt;br /&gt;
&amp;amp;quot;Information Rejection&amp;amp;quot;. IR is the scenario whereby an Appointed Party or supplier attempts to exchange files on a CDE that are:&amp;lt;br /&amp;gt;&lt;br /&gt;
&amp;lt;br /&amp;gt;&lt;br /&gt;
- Not derived from the project team's 3D BIM volume(s)&amp;lt;br /&amp;gt;&lt;br /&gt;
- CAD files reverse-BIM'd in to 3D volumes by a third party&amp;lt;br /&amp;gt;&lt;br /&gt;
- Exo-BIM data not exported from the BIM volumes e.g. manually added to spreadsheets&amp;lt;br /&amp;gt;&lt;br /&gt;
- Non-compliant with project BIM protocols&amp;lt;br /&amp;gt;&lt;br /&gt;
- 2D Drawings not derived from the 3D BIM volume(s)&amp;lt;br /&amp;gt;&lt;br /&gt;
&amp;lt;br /&amp;gt;&lt;br /&gt;
The potential consequences for having exchange information rejected are:&amp;lt;br /&amp;gt;&lt;br /&gt;
&amp;lt;br /&amp;gt;&lt;br /&gt;
- Responsibility for causing delays&amp;lt;br /&amp;gt;&lt;br /&gt;
- Charges imposed for delays&amp;lt;br /&amp;gt;&lt;br /&gt;
- Percentage of fees withheld&amp;lt;br /&amp;gt;&lt;br /&gt;
- Termination of appointment&lt;br /&gt;
&lt;br /&gt;
DETECTION&lt;br /&gt;
&lt;br /&gt;
To detect the occurance of attempts to exchange drawings and data not derived from the required 'live' 3D BIM volume, the BIM protocols must state that any file exchanged on the CDE must have an associated 3D BIM Volume to verify as the source of that information.&lt;br /&gt;
&lt;br /&gt;
Where a clear dsparity between the two occurs, or there is an absence of a 3D BIM Volume to verify the drawing or data against. That will be deemed a breach of the agreed rules and information Rejection will be the resulting action.&lt;br /&gt;
&lt;br /&gt;
PREVENTION&lt;br /&gt;
&lt;br /&gt;
Create a BIM Services Agreement or similar, to be signed by each Appointed Party or Supplier in a Task Team prior to appointment to a project.&lt;br /&gt;
&lt;br /&gt;
Amongst the descriptions of how and why Appointed Party's must read and understand the BIM protocols, it will be neccessary to defne the resulting actions that will be applied to the responsible party when their exchanged information on the CDE is discovered to be derived from exo-BIM sources and methods.&lt;br /&gt;
&lt;br /&gt;
EXEMPLAR&lt;br /&gt;
&lt;br /&gt;
Below as a typical example of how to define the circumstances and outcomes to Appointed Party if they fail to apply BIM processes in the design and exchanged files:&lt;br /&gt;
&lt;br /&gt;
Information Rejection:&lt;br /&gt;
&lt;br /&gt;
Starting from the first file exchange uploaded to the CDE, all drawings, details, schedules and other data file exchanged will be verified against your 3D .RVT/.IFC model exchanged at the same cycle. Be aware that if the files are found not to be derived from this 3D file, all exchanged files will be rejected and notice given to you for deviating from this agreement. Rejection of your files will have negative consequences with regards to your fees and potential charges imposed for causing delays. Your appointment to this project may also be terminated for breaching this agreement. Refer to the contracts director for further details.&lt;/div&gt;</summary>
		<author><name>NXUS-BIM</name></author>	</entry>

	<entry>
		<id>https://www.designingbuildings.co.uk/wiki/Exo-BIM</id>
		<title>Exo-BIM</title>
		<link rel="alternate" type="text/html" href="https://www.designingbuildings.co.uk/wiki/Exo-BIM"/>
				<updated>2022-12-18T18:20:00Z</updated>
		
		<summary type="html">&lt;p&gt;NXUS-BIM: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Exo-BIM describes a design or data authoring process conducted outside of the central collaborative BIM process and its federated model volumes. The method or process is external to the project team's agreed, live integrated and collaborative data set, and as such cannot respond and react to the developing conditions in a timely and effective way.&lt;br /&gt;
&lt;br /&gt;
In any circumstance where a project has implemented defined and managed BIM protocols for all consultants stakeholders and the supply chains for defined stages of the project.For a project contributor to develop their models, drawings or data outside of that system is considered exo-BIM.&lt;br /&gt;
&lt;br /&gt;
Exo-BIM may also be a process that uses drawings or data exported from a volume from within the central collaborative BIM process, and is then developed with in non-object based CAD software, or derived from sources other than the live 3D modelled building fabric and other modelled assets within it.&lt;br /&gt;
&lt;br /&gt;
In conclusion, exo-BIM is project data or information exchanged within a BIM protocol defined IM environment, but is not derived directly from one of the BIM Volumes listed in the volume strategy for that project.&lt;/div&gt;</summary>
		<author><name>NXUS-BIM</name></author>	</entry>

	<entry>
		<id>https://www.designingbuildings.co.uk/wiki/Exo-BIM</id>
		<title>Exo-BIM</title>
		<link rel="alternate" type="text/html" href="https://www.designingbuildings.co.uk/wiki/Exo-BIM"/>
				<updated>2022-12-18T18:14:57Z</updated>
		
		<summary type="html">&lt;p&gt;NXUS-BIM: Created page with &amp;quot;Exo-BIM describes a design or data authoring process conducted outside of the central collaborative BIM process and its federated model volumes. The method or process is external...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Exo-BIM describes a design or data authoring process conducted outside of the central collaborative BIM process and its federated model volumes. The method or process is external to the project team's agreed, live integrated and collaborative data set, and as such cannot respond and react to the developing conditions in a timely and effective way.&lt;br /&gt;
&lt;br /&gt;
In any circumstance where a project has implemented defined and managed BIM protocols for all consultants stakeholders and the supply chains for defined stages of the project.For a contributor to develop their models, drawings or data outside of that system is considered exo-BIM.&lt;br /&gt;
&lt;br /&gt;
Exo-BIM may also be a process that uses drawings or data exported from a volume from within the central collaborative BIM process and is developed or derived from sources other than the 3D modelled building fabric and other modelled assets within it.&lt;br /&gt;
&lt;br /&gt;
In conclusion, exo-BIM is project data or information exchanged within a BIM protocol defined IM environment, but is not derived directly from one of the BIM Volumes listed in the volume strategy for that project.&lt;/div&gt;</summary>
		<author><name>NXUS-BIM</name></author>	</entry>

	<entry>
		<id>https://www.designingbuildings.co.uk/wiki/Information_Rejection</id>
		<title>Information Rejection</title>
		<link rel="alternate" type="text/html" href="https://www.designingbuildings.co.uk/wiki/Information_Rejection"/>
				<updated>2022-12-12T16:59:46Z</updated>
		
		<summary type="html">&lt;p&gt;NXUS-BIM: Created page with &amp;quot;BACKGROUND  BIM protocols for an organization or project may state that Appointed Parties must deliver the project information files in accordance the agreed protocols. The indus...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;BACKGROUND&lt;br /&gt;
&lt;br /&gt;
BIM protocols for an organization or project may state that Appointed Parties must deliver the project information files in accordance the agreed protocols. The industry sometime finds that Appointed Parties agree to implement BIM process in their design, and that their deliverables will be derived exported or 'cut' from the project BIM volumes, but they fail to do so. Due in some cases to lack of skills and competency.&lt;br /&gt;
&lt;br /&gt;
What is sometimes reported by Information Managers and BIM Coordinators are attempts to develop the design in 2D CAD exported (by a third party in some cases) from the other consultants federated 3D models. The resulting 2D design developed outside of the colaborative process will not take in to account design issues including clashes with other consultants's design intent.&lt;br /&gt;
&lt;br /&gt;
A disparity and time shift between the 3D federated models typically exchanged fortnightly on the CDE and the non-BIM derived design occurs, this results in innacuracy, failure to colaborate effectively, delays on site and reduced value to the client.&lt;br /&gt;
&lt;br /&gt;
CONCEPT&lt;br /&gt;
&lt;br /&gt;
&amp;amp;quot;Information Rejection&amp;amp;quot;. IR is the scenario whereby an Appointed Party attempts to exchange files on a CDE that are not:&amp;lt;br /&amp;gt;&lt;br /&gt;
&amp;lt;br /&amp;gt;&lt;br /&gt;
- Derived from the 3D BIM volume(s)&amp;lt;br /&amp;gt;&lt;br /&gt;
- CAD files reverse-BIM'd in to 3D volumes&amp;lt;br /&amp;gt;&lt;br /&gt;
- Data not exported from the BIM volumes e.g. manually added to spreadsheets&amp;lt;br /&amp;gt;&lt;br /&gt;
- Non-compliance to project BIM protocols&amp;lt;br /&amp;gt;&lt;br /&gt;
- 2D Drawings not derived from the 3D BIM volume(s)&amp;lt;br /&amp;gt;&lt;br /&gt;
&amp;lt;br /&amp;gt;&lt;br /&gt;
The potential consequences for having exchange information rejected are:&amp;lt;br /&amp;gt;&lt;br /&gt;
&amp;lt;br /&amp;gt;&lt;br /&gt;
- Responsibility for causing delays&amp;lt;br /&amp;gt;&lt;br /&gt;
- Charges imposed for delays&amp;lt;br /&amp;gt;&lt;br /&gt;
- Percentage of fees withheld&amp;lt;br /&amp;gt;&lt;br /&gt;
- Termination of appointment&lt;br /&gt;
&lt;br /&gt;
ACTION&lt;br /&gt;
&lt;br /&gt;
Create a BIM Services Agreement or similar, to be signed by each Task Team prior to appointment to a project.&lt;br /&gt;
&lt;br /&gt;
Amongst the descriptions of how and why the Appointed Party must read and understand the BIM protocols, it will be neccessary to defne the actions that will be applied when non-BIM processes are wrongly be implemented.and discovered on the CDE.&lt;br /&gt;
&lt;br /&gt;
EXEMPLAR&lt;br /&gt;
&lt;br /&gt;
Below as a typical example of how to define the circumstances and outcomes to Appointed Party if they fail to apply BIM processes in the design and exchanged files:&lt;br /&gt;
&lt;br /&gt;
Information Rejection:&lt;br /&gt;
&lt;br /&gt;
Starting from the first file exchange uploaded to the CDE, all drawings, details, schedules and other data file exchanged will be verified against your 3D .RVT/.IFC model exchanged at the same cycle. Be aware that if the files are found not to be derived from this 3D file, all exchanged files will be rejected and notice given to you for deviating from this agreement. Rejection of your files will have negative consequences with regards to your fees and potential charges imposed for causing delays. Your appointment to this project may also be terminated for breaching this agreement. Refer to the contracts director for further details.&lt;/div&gt;</summary>
		<author><name>NXUS-BIM</name></author>	</entry>

	</feed>