<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	
	>
<channel>
	<title>
	Comments on: A Primer on CDEs (Common Data Environments) for Architects	</title>
	<atom:link href="https://architosh.com/2018/01/a-primer-on-cdes-common-data-environments-for-architects/feed/" rel="self" type="application/rss+xml" />
	<link>https://architosh.com/2018/01/a-primer-on-cdes-common-data-environments-for-architects/</link>
	<description>architosh™ — a global-leading CAD / 3D / AEC industry technology publication and #1 source for Mac and iOS users in these segments.</description>
	<lastBuildDate>Fri, 17 Nov 2023 23:20:28 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.0.2</generator>
	<item>
		<title>
		By: Anthony Frausto-Robledo AIA, LEED AP		</title>
		<link>https://architosh.com/2018/01/a-primer-on-cdes-common-data-environments-for-architects/#comment-55558</link>

		<dc:creator><![CDATA[Anthony Frausto-Robledo AIA, LEED AP]]></dc:creator>
		<pubDate>Sun, 25 Feb 2018 17:36:49 +0000</pubDate>
		<guid isPermaLink="false">https://architosh.com/?p=25641#comment-55558</guid>

					<description><![CDATA[m68k, I agree with many of your points, particularly the ability for small firms to manage the whole process of the standard. In our small practice, we are determined to implement the best part of the  BS/PAS 1192 standard—the clear process of WIP, Shared, Published, Archived. From the POV of architecture, I see the implementation of the four primary container model highly useful IF:

- cloud-based CDE tools can support wip, share, published, archived division of data flow,
- cloud based CDE tools can publish APIs so desktop BIMs/CADs can plug into the data model.

General contractors are using CDE&#039;s primarily to increase &quot;wrench time&quot; in the process by accelerating and automating data exchange workflows. The proposed standard can be highly conducive to that goal, not just for contractors but A and E professionals in the process. The &quot;shared&quot; status/workflow method of data today is pathetically slow and fragmented. Emailing documents only after creating PDFs from 2Ds only after producing 2Ds from 3D BIMs is a long trail solution to a destination that can be so much faster. The iteration between architect and consultants can be intensive and these loops must be recorded for record so that there is accountability. 

In our office were developing a file (data) directory structure that echoes the four-container 1192 model in an intelligent manner in preparation for the eventual API-based connections between desktop and cloud CDEs. We need to record the workflows into the CDE cloud and our directories simultaneously and as automated as possible.]]></description>
			<content:encoded><![CDATA[<p>m68k, I agree with many of your points, particularly the ability for small firms to manage the whole process of the standard. In our small practice, we are determined to implement the best part of the  BS/PAS 1192 standard—the clear process of WIP, Shared, Published, Archived. From the POV of architecture, I see the implementation of the four primary container model highly useful IF:</p>
<p>&#8211; cloud-based CDE tools can support wip, share, published, archived division of data flow,<br />
&#8211; cloud based CDE tools can publish APIs so desktop BIMs/CADs can plug into the data model.</p>
<p>General contractors are using CDE&#8217;s primarily to increase &#8220;wrench time&#8221; in the process by accelerating and automating data exchange workflows. The proposed standard can be highly conducive to that goal, not just for contractors but A and E professionals in the process. The &#8220;shared&#8221; status/workflow method of data today is pathetically slow and fragmented. Emailing documents only after creating PDFs from 2Ds only after producing 2Ds from 3D BIMs is a long trail solution to a destination that can be so much faster. The iteration between architect and consultants can be intensive and these loops must be recorded for record so that there is accountability. </p>
<p>In our office were developing a file (data) directory structure that echoes the four-container 1192 model in an intelligent manner in preparation for the eventual API-based connections between desktop and cloud CDEs. We need to record the workflows into the CDE cloud and our directories simultaneously and as automated as possible.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: m68k		</title>
		<link>https://architosh.com/2018/01/a-primer-on-cdes-common-data-environments-for-architects/#comment-56380</link>

		<dc:creator><![CDATA[m68k]]></dc:creator>
		<pubDate>Sun, 25 Feb 2018 13:08:56 +0000</pubDate>
		<guid isPermaLink="false">https://architosh.com/?p=25641#comment-56380</guid>

					<description><![CDATA[Why is the bsi pushing so hard for iso 19650?
The solution of cabinet is only dealing with ordinary 2D-drawing files, but not with data of the building information model. 
What we need first is a reliable DataDictionary and a Database with all necessary properties for all buildingelement classes.]]></description>
			<content:encoded><![CDATA[<p>Why is the bsi pushing so hard for iso 19650?<br />
The solution of cabinet is only dealing with ordinary 2D-drawing files, but not with data of the building information model.<br />
What we need first is a reliable DataDictionary and a Database with all necessary properties for all buildingelement classes.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: m68k		</title>
		<link>https://architosh.com/2018/01/a-primer-on-cdes-common-data-environments-for-architects/#comment-55557</link>

		<dc:creator><![CDATA[m68k]]></dc:creator>
		<pubDate>Sun, 25 Feb 2018 13:08:56 +0000</pubDate>
		<guid isPermaLink="false">https://architosh.com/?p=25641#comment-55557</guid>

					<description><![CDATA[Why is the bsi pushing so hard for iso 19650?
The solution of cabinet is only dealing with ordinary 2D-drawing files, but not with data of the building information model. 
What we need first is a reliable DataDictionary and a Database with all necessary properties for all buildingelement classes.]]></description>
			<content:encoded><![CDATA[<p>Why is the bsi pushing so hard for iso 19650?<br />
The solution of cabinet is only dealing with ordinary 2D-drawing files, but not with data of the building information model.<br />
What we need first is a reliable DataDictionary and a Database with all necessary properties for all buildingelement classes.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: m68k		</title>
		<link>https://architosh.com/2018/01/a-primer-on-cdes-common-data-environments-for-architects/#comment-58295</link>

		<dc:creator><![CDATA[m68k]]></dc:creator>
		<pubDate>Sun, 25 Feb 2018 12:49:58 +0000</pubDate>
		<guid isPermaLink="false">https://architosh.com/?p=25641#comment-58295</guid>

					<description><![CDATA[Reading the proposal for the iso 19650 my impression is, that as long the CDE is only projectwise instead of general (GDE) it needs a lot of effort to be established. So it is not lean as long as there are no general data environments. The only bonus might be a clear process of wip, shared, published and archived. 
I think the whole process is not manageable for small firms. Mayby that&#039;s why the iso is talking about lead appointing parties.]]></description>
			<content:encoded><![CDATA[<p>Reading the proposal for the iso 19650 my impression is, that as long the CDE is only projectwise instead of general (GDE) it needs a lot of effort to be established. So it is not lean as long as there are no general data environments. The only bonus might be a clear process of wip, shared, published and archived.<br />
I think the whole process is not manageable for small firms. Mayby that&#8217;s why the iso is talking about lead appointing parties.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: m68k		</title>
		<link>https://architosh.com/2018/01/a-primer-on-cdes-common-data-environments-for-architects/#comment-55556</link>

		<dc:creator><![CDATA[m68k]]></dc:creator>
		<pubDate>Sun, 25 Feb 2018 12:49:58 +0000</pubDate>
		<guid isPermaLink="false">https://architosh.com/?p=25641#comment-55556</guid>

					<description><![CDATA[Reading the proposal for the iso 19650 my impression is, that as long the CDE is only projectwise instead of general (GDE) it needs a lot of effort to be established. So it is not lean as long as there are no general data environments. The only bonus might be a clear process of wip, shared, published and archived. 
I think the whole process is not manageable for small firms. Mayby that‘s why the iso is talking about lead appointing parties.]]></description>
			<content:encoded><![CDATA[<p>Reading the proposal for the iso 19650 my impression is, that as long the CDE is only projectwise instead of general (GDE) it needs a lot of effort to be established. So it is not lean as long as there are no general data environments. The only bonus might be a clear process of wip, shared, published and archived.<br />
I think the whole process is not manageable for small firms. Mayby that‘s why the iso is talking about lead appointing parties.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Anthony Frausto-Robledo AIA, L		</title>
		<link>https://architosh.com/2018/01/a-primer-on-cdes-common-data-environments-for-architects/#comment-60128</link>

		<dc:creator><![CDATA[Anthony Frausto-Robledo AIA, L]]></dc:creator>
		<pubDate>Sun, 25 Feb 2018 12:36:49 +0000</pubDate>
		<guid isPermaLink="false">https://architosh.com/?p=25641#comment-60128</guid>

					<description><![CDATA[m68k, I agree with many of your points, particularly the ability for small firms to manage the whole process of the standard. In our small practice, we are determined to implement the best part of the  BS/PAS 1192 standard&#8212;the clear process of WIP, Shared, Published, Archived. From the POV of architecture, I see the implementation of the four primary container model highly useful IF:

- cloud-based CDE tools can support wip, share, published, archived division of data flow,
- cloud based CDE tools can publish APIs so desktop BIMs/CADs can plug into the data model.

General contractors are using CDE&#039;s primarily to increase &quot;wrench time&quot; in the process by accelerating and automating data exchange workflows. The proposed standard can be highly conducive to that goal, not just for contractors but A and E professionals in the process. The &quot;shared&quot; status/workflow method of data today is pathetically slow and fragmented. Emailing documents only after creating PDFs from 2Ds only after producing 2Ds from 3D BIMs is a long trail solution to a destination that can be so much faster. The iteration between architect and consultants can be intensive and these loops must be recorded for record so that there is accountability. 

In our office were developing a file (data) directory structure that echoes the four-container 1192 model in an intelligent manner in preparation for the eventual API-based connections between desktop and cloud CDEs. We need to record the workflows into the CDE cloud and our directories simultaneously and as automated as possible.]]></description>
			<content:encoded><![CDATA[<p>m68k, I agree with many of your points, particularly the ability for small firms to manage the whole process of the standard. In our small practice, we are determined to implement the best part of the  BS/PAS 1192 standard&#8212;the clear process of WIP, Shared, Published, Archived. From the POV of architecture, I see the implementation of the four primary container model highly useful IF:</p>
<p>&#8211; cloud-based CDE tools can support wip, share, published, archived division of data flow,<br />
&#8211; cloud based CDE tools can publish APIs so desktop BIMs/CADs can plug into the data model.</p>
<p>General contractors are using CDE&#8217;s primarily to increase &#8220;wrench time&#8221; in the process by accelerating and automating data exchange workflows. The proposed standard can be highly conducive to that goal, not just for contractors but A and E professionals in the process. The &#8220;shared&#8221; status/workflow method of data today is pathetically slow and fragmented. Emailing documents only after creating PDFs from 2Ds only after producing 2Ds from 3D BIMs is a long trail solution to a destination that can be so much faster. The iteration between architect and consultants can be intensive and these loops must be recorded for record so that there is accountability. </p>
<p>In our office were developing a file (data) directory structure that echoes the four-container 1192 model in an intelligent manner in preparation for the eventual API-based connections between desktop and cloud CDEs. We need to record the workflows into the CDE cloud and our directories simultaneously and as automated as possible.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: pcholakis		</title>
		<link>https://architosh.com/2018/01/a-primer-on-cdes-common-data-environments-for-architects/#comment-55547</link>

		<dc:creator><![CDATA[pcholakis]]></dc:creator>
		<pubDate>Fri, 26 Jan 2018 17:07:15 +0000</pubDate>
		<guid isPermaLink="false">https://architosh.com/?p=25641#comment-55547</guid>

					<description><![CDATA[&quot;A common data environment (CDE) for architects&quot; is the WRONG way to approach this core, industry-wide AECOO problem (architects, engineers, contractors, owners. operators).   

A CDE is REQUIRED for all facilities/built environment participants and stakeholders....  designers, engineers, builders, facilities owners, facilities management, building users, procurement, technical teams, oversight groups....    

This requires a LEAN asset life-cycle management approach and associated model.  https://www.4bt.us/wp-content/uploads/2016/02/Asset-Total-Cost-of-Ownership-Efficient-Life-cycle-Management-Model.pdf
https://www.4bt.us/wp-content/uploads/2016/02/BIM-LEAN-Construction-and-a-Common-Data-Environment-CDE.pdf
https://www.wbdg.org/facilities-operations-maintenance/operation-maintenance-planning

Central to the above is a detailed line item listing of construction tasks and cost organized via a standard data architecture... (i.e. Masterformat).  Each task providing a description of the task in plain English and labor, material, and equipment details.   This aspect is critical to Scope of Work definition and communication among all parties.

Technology, while an enabler with respect to lowering deployment costs and driving consistency should NEVER be the primary focus.  LEAN collaborative construction project delivery should be the primary focus.

A focus upon digital aspects will do little to improve AECOO outcomes, rather a focus upon CHANGE MANAGEMENT and LEAN methods, such as Integrated Project Delivery, IPD, for major new construction, and Job Order Contracting, JOC for repair, renovation, and minor new construction enables consistent 90%+ on-time, on-budget, and satisfactory results.   

A major focus of LEAN methods such as IPD and JOC is providing the ability for owner, builder, AE, user teams  to communicate, re-use, and share ACTIONABLE and CURRENT INFORMATION efficiently without loss, contradiction, or misinterpretation.

Remember...
1. Have a WRITTEN IPD/JOC Operations Manual and/or Execution Plan defining ALL roles, responsibilities, desired outcomes, for all participants and stakeholders, including... defining CDE requirements (common unit price book of locally researched construction tasks organized by MasterFormat (TM).
2. Mandatory Training -  Initial and Ongoing Multi-level (Intro, Advanced...) and Multi-format (on-site, regional, virtual).
3. Mandatory Collaboration
4. Mutual Trust/Respect
5. Shared Risk/Reward
6. Supporting Cloud Technology
7. Continuous Improvement
8. Long Term Relationships
9. Best Value Procurement
10. Key Performance Indicators (KPIs) and regular independent Audits

www.4bt.us]]></description>
			<content:encoded><![CDATA[<p>&#8220;A common data environment (CDE) for architects&#8221; is the WRONG way to approach this core, industry-wide AECOO problem (architects, engineers, contractors, owners. operators).   </p>
<p>A CDE is REQUIRED for all facilities/built environment participants and stakeholders&#8230;.  designers, engineers, builders, facilities owners, facilities management, building users, procurement, technical teams, oversight groups&#8230;.    </p>
<p>This requires a LEAN asset life-cycle management approach and associated model.  <a href="https://www.4bt.us/wp-content/uploads/2016/02/Asset-Total-Cost-of-Ownership-Efficient-Life-cycle-Management-Model.pdf" rel="nofollow ugc">https://www.4bt.us/wp-content/uploads/2016/02/Asset-Total-Cost-of-Ownership-Efficient-Life-cycle-Management-Model.pdf</a><br />
<a href="https://www.4bt.us/wp-content/uploads/2016/02/BIM-LEAN-Construction-and-a-Common-Data-Environment-CDE.pdf" rel="nofollow ugc">https://www.4bt.us/wp-content/uploads/2016/02/BIM-LEAN-Construction-and-a-Common-Data-Environment-CDE.pdf</a><br />
<a href="https://www.wbdg.org/facilities-operations-maintenance/operation-maintenance-planning" rel="nofollow ugc">https://www.wbdg.org/facilities-operations-maintenance/operation-maintenance-planning</a></p>
<p>Central to the above is a detailed line item listing of construction tasks and cost organized via a standard data architecture&#8230; (i.e. Masterformat).  Each task providing a description of the task in plain English and labor, material, and equipment details.   This aspect is critical to Scope of Work definition and communication among all parties.</p>
<p>Technology, while an enabler with respect to lowering deployment costs and driving consistency should NEVER be the primary focus.  LEAN collaborative construction project delivery should be the primary focus.</p>
<p>A focus upon digital aspects will do little to improve AECOO outcomes, rather a focus upon CHANGE MANAGEMENT and LEAN methods, such as Integrated Project Delivery, IPD, for major new construction, and Job Order Contracting, JOC for repair, renovation, and minor new construction enables consistent 90%+ on-time, on-budget, and satisfactory results.   </p>
<p>A major focus of LEAN methods such as IPD and JOC is providing the ability for owner, builder, AE, user teams  to communicate, re-use, and share ACTIONABLE and CURRENT INFORMATION efficiently without loss, contradiction, or misinterpretation.</p>
<p>Remember&#8230;<br />
1. Have a WRITTEN IPD/JOC Operations Manual and/or Execution Plan defining ALL roles, responsibilities, desired outcomes, for all participants and stakeholders, including&#8230; defining CDE requirements (common unit price book of locally researched construction tasks organized by MasterFormat (TM).<br />
2. Mandatory Training &#8211;  Initial and Ongoing Multi-level (Intro, Advanced&#8230;) and Multi-format (on-site, regional, virtual).<br />
3. Mandatory Collaboration<br />
4. Mutual Trust/Respect<br />
5. Shared Risk/Reward<br />
6. Supporting Cloud Technology<br />
7. Continuous Improvement<br />
8. Long Term Relationships<br />
9. Best Value Procurement<br />
10. Key Performance Indicators (KPIs) and regular independent Audits</p>
<p><a href="http://www.4bt.us" rel="nofollow ugc">http://www.4bt.us</a></p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: pcholakis		</title>
		<link>https://architosh.com/2018/01/a-primer-on-cdes-common-data-environments-for-architects/#comment-58293</link>

		<dc:creator><![CDATA[pcholakis]]></dc:creator>
		<pubDate>Fri, 26 Jan 2018 17:07:15 +0000</pubDate>
		<guid isPermaLink="false">https://architosh.com/?p=25641#comment-58293</guid>

					<description><![CDATA[&quot;A common data environment (CDE) for architects&quot; is the WRONG way to approach this core, industry-wide AECOO problem (architects, engineers, contractors, owners. operators).   

A CDE is REQUIRED for all facilities/built environment participants and stakeholders....  designers, engineers, builders, facilities owners, facilities management, building users, procurement, technical teams, oversight groups....    

This requires a LEAN asset life-cycle management approach and associated model.  https://www.4bt.us/wp-content/uploads/2016/02/Asset-Total-Cost-of-Ownership-Efficient-Life-cycle-Management-Model.pdf
https://www.4bt.us/wp-content/uploads/2016/02/BIM-LEAN-Construction-and-a-Common-Data-Environment-CDE.pdf
https://www.wbdg.org/facilities-operations-maintenance/operation-maintenance-planning

Central to the above is a detailed line item listing of construction tasks and cost organized via a standard data architecture... (i.e. Masterformat).  Each task providing a description of the task in plain English and labor, material, and equipment details.   This aspect is critical to Scope of Work definition and communication among all parties.

Technology, while an enabler with respect to lowering deployment costs and driving consistency should NEVER be the primary focus.  LEAN collaborative construction project delivery should be the primary focus.

A focus upon digital aspects will do little to improve AECOO outcomes, rather a focus upon CHANGE MANAGEMENT and LEAN methods, such as Integrated Project Delivery, IPD, for major new construction, and Job Order Contracting, JOC for repair, renovation, and minor new construction enables consistent 90%+ on-time, on-budget, and satisfactory results.   

A major focus of LEAN methods such as IPD and JOC is providing the ability for owner, builder, AE, user teams  to communicate, re-use, and share ACTIONABLE and CURRENT INFORMATION efficiently without loss, contradiction, or misinterpretation.

Remember...
1. Have a WRITTEN IPD/JOC Operations Manual and/or Execution Plan defining ALL roles, responsibilities, desired outcomes, for all participants and stakeholders, including... defining CDE requirements (common unit price book of locally researched construction tasks organized by MasterFormat (TM).
2. Mandatory Training -  Initial and Ongoing Multi-level (Intro, Advanced...) and Multi-format (on-site, regional, virtual).
3. Mandatory Collaboration
4. Mutual Trust/Respect
5. Shared Risk/Reward
6. Supporting Cloud Technology
7. Continuous Improvement
8. Long Term Relationships
9. Best Value Procurement
10. Key Performance Indicators (KPIs) and regular independent Audits

www.4bt.us]]></description>
			<content:encoded><![CDATA[<p>&#8220;A common data environment (CDE) for architects&#8221; is the WRONG way to approach this core, industry-wide AECOO problem (architects, engineers, contractors, owners. operators).   </p>
<p>A CDE is REQUIRED for all facilities/built environment participants and stakeholders&#8230;.  designers, engineers, builders, facilities owners, facilities management, building users, procurement, technical teams, oversight groups&#8230;.    </p>
<p>This requires a LEAN asset life-cycle management approach and associated model.  <a href="https://www.4bt.us/wp-content/uploads/2016/02/Asset-Total-Cost-of-Ownership-Efficient-Life-cycle-Management-Model.pdf" rel="nofollow ugc">https://www.4bt.us/wp-content/uploads/2016/02/Asset-Total-Cost-of-Ownership-Efficient-Life-cycle-Management-Model.pdf</a><br />
<a href="https://www.4bt.us/wp-content/uploads/2016/02/BIM-LEAN-Construction-and-a-Common-Data-Environment-CDE.pdf" rel="nofollow ugc">https://www.4bt.us/wp-content/uploads/2016/02/BIM-LEAN-Construction-and-a-Common-Data-Environment-CDE.pdf</a><br />
<a href="https://www.wbdg.org/facilities-operations-maintenance/operation-maintenance-planning" rel="nofollow ugc">https://www.wbdg.org/facilities-operations-maintenance/operation-maintenance-planning</a></p>
<p>Central to the above is a detailed line item listing of construction tasks and cost organized via a standard data architecture&#8230; (i.e. Masterformat).  Each task providing a description of the task in plain English and labor, material, and equipment details.   This aspect is critical to Scope of Work definition and communication among all parties.</p>
<p>Technology, while an enabler with respect to lowering deployment costs and driving consistency should NEVER be the primary focus.  LEAN collaborative construction project delivery should be the primary focus.</p>
<p>A focus upon digital aspects will do little to improve AECOO outcomes, rather a focus upon CHANGE MANAGEMENT and LEAN methods, such as Integrated Project Delivery, IPD, for major new construction, and Job Order Contracting, JOC for repair, renovation, and minor new construction enables consistent 90%+ on-time, on-budget, and satisfactory results.   </p>
<p>A major focus of LEAN methods such as IPD and JOC is providing the ability for owner, builder, AE, user teams  to communicate, re-use, and share ACTIONABLE and CURRENT INFORMATION efficiently without loss, contradiction, or misinterpretation.</p>
<p>Remember&#8230;<br />
1. Have a WRITTEN IPD/JOC Operations Manual and/or Execution Plan defining ALL roles, responsibilities, desired outcomes, for all participants and stakeholders, including&#8230; defining CDE requirements (common unit price book of locally researched construction tasks organized by MasterFormat (TM).<br />
2. Mandatory Training &#8211;  Initial and Ongoing Multi-level (Intro, Advanced&#8230;) and Multi-format (on-site, regional, virtual).<br />
3. Mandatory Collaboration<br />
4. Mutual Trust/Respect<br />
5. Shared Risk/Reward<br />
6. Supporting Cloud Technology<br />
7. Continuous Improvement<br />
8. Long Term Relationships<br />
9. Best Value Procurement<br />
10. Key Performance Indicators (KPIs) and regular independent Audits</p>
<p><a href="http://www.4bt.us" rel="nofollow ugc">http://www.4bt.us</a></p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: pcholakis		</title>
		<link>https://architosh.com/2018/01/a-primer-on-cdes-common-data-environments-for-architects/#comment-55546</link>

		<dc:creator><![CDATA[pcholakis]]></dc:creator>
		<pubDate>Fri, 26 Jan 2018 16:44:55 +0000</pubDate>
		<guid isPermaLink="false">https://architosh.com/?p=25641#comment-55546</guid>

					<description><![CDATA[No....  not just DMS for BIM...   so much more..  https://www.4bt.us/wp-content/uploads/2016/02/Asset-Total-Cost-of-Ownership-Efficient-Life-cycle-Management-Model.pdf
https://www.4bt.us/wp-content/uploads/2016/02/BIM-LEAN-Construction-and-a-Common-Data-Environment-CDE.pdf
https://www.wbdg.org/facilities-operations-maintenance/operation-maintenance-planning]]></description>
			<content:encoded><![CDATA[<p>No&#8230;.  not just DMS for BIM&#8230;   so much more..  <a href="https://www.4bt.us/wp-content/uploads/2016/02/Asset-Total-Cost-of-Ownership-Efficient-Life-cycle-Management-Model.pdf" rel="nofollow ugc">https://www.4bt.us/wp-content/uploads/2016/02/Asset-Total-Cost-of-Ownership-Efficient-Life-cycle-Management-Model.pdf</a><br />
<a href="https://www.4bt.us/wp-content/uploads/2016/02/BIM-LEAN-Construction-and-a-Common-Data-Environment-CDE.pdf" rel="nofollow ugc">https://www.4bt.us/wp-content/uploads/2016/02/BIM-LEAN-Construction-and-a-Common-Data-Environment-CDE.pdf</a><br />
<a href="https://www.wbdg.org/facilities-operations-maintenance/operation-maintenance-planning" rel="nofollow ugc">https://www.wbdg.org/facilities-operations-maintenance/operation-maintenance-planning</a></p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: pcholakis		</title>
		<link>https://architosh.com/2018/01/a-primer-on-cdes-common-data-environments-for-architects/#comment-60123</link>

		<dc:creator><![CDATA[pcholakis]]></dc:creator>
		<pubDate>Fri, 26 Jan 2018 11:44:55 +0000</pubDate>
		<guid isPermaLink="false">https://architosh.com/?p=25641#comment-60123</guid>

					<description><![CDATA[No....  not just DMS for BIM...   so much more..  https://www.4bt.us/wp-content/uploads/2016/02/Asset-Total-Cost-of-Ownership-Efficient-Life-cycle-Management-Model.pdf
https://www.4bt.us/wp-content/uploads/2016/02/BIM-LEAN-Construction-and-a-Common-Data-Environment-CDE.pdf
https://www.wbdg.org/facilities-operations-maintenance/operation-maintenance-planning]]></description>
			<content:encoded><![CDATA[<p>No&#8230;.  not just DMS for BIM&#8230;   so much more..  <a href="https://www.4bt.us/wp-content/uploads/2016/02/Asset-Total-Cost-of-Ownership-Efficient-Life-cycle-Management-Model.pdf" rel="nofollow ugc">https://www.4bt.us/wp-content/uploads/2016/02/Asset-Total-Cost-of-Ownership-Efficient-Life-cycle-Management-Model.pdf</a><br />
<a href="https://www.4bt.us/wp-content/uploads/2016/02/BIM-LEAN-Construction-and-a-Common-Data-Environment-CDE.pdf" rel="nofollow ugc">https://www.4bt.us/wp-content/uploads/2016/02/BIM-LEAN-Construction-and-a-Common-Data-Environment-CDE.pdf</a><br />
<a href="https://www.wbdg.org/facilities-operations-maintenance/operation-maintenance-planning" rel="nofollow ugc">https://www.wbdg.org/facilities-operations-maintenance/operation-maintenance-planning</a></p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: m68k		</title>
		<link>https://architosh.com/2018/01/a-primer-on-cdes-common-data-environments-for-architects/#comment-55545</link>

		<dc:creator><![CDATA[m68k]]></dc:creator>
		<pubDate>Thu, 25 Jan 2018 18:41:30 +0000</pubDate>
		<guid isPermaLink="false">https://architosh.com/?p=25641#comment-55545</guid>

					<description><![CDATA[So CDE should be DMS for BIM?
Cabinet stores for each published DWG/PDF the corresponding Projectfile (e.g. 500MB .rvt file) ?
That would produce a massive amount of files and needs ridiculous amounts of storage. 
How to use that kind of workflow for a teamwork project ?
What happens if you are not handing over the whole set of plans at once, but peace by peace?
Will every publishing create a new projectfile everyone has to sign in then?]]></description>
			<content:encoded><![CDATA[<p>So CDE should be DMS for BIM?<br />
Cabinet stores for each published DWG/PDF the corresponding Projectfile (e.g. 500MB .rvt file) ?<br />
That would produce a massive amount of files and needs ridiculous amounts of storage.<br />
How to use that kind of workflow for a teamwork project ?<br />
What happens if you are not handing over the whole set of plans at once, but peace by peace?<br />
Will every publishing create a new projectfile everyone has to sign in then?</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: m68k		</title>
		<link>https://architosh.com/2018/01/a-primer-on-cdes-common-data-environments-for-architects/#comment-56381</link>

		<dc:creator><![CDATA[m68k]]></dc:creator>
		<pubDate>Thu, 25 Jan 2018 18:41:30 +0000</pubDate>
		<guid isPermaLink="false">https://architosh.com/?p=25641#comment-56381</guid>

					<description><![CDATA[So CDE should be DMS for BIM?
Cabinet stores for each published DWG/PDF the corresponding Projectfile (e.g. 500MB .rvt file) ?
That would produce a massive amount of files and needs ridiculous amounts of storage. 
How to use that kind of workflow for a teamwork project ?
What happens if you are not handing over the whole set of plans at once, but peace by peace?
Will every publishing create a new projectfile everyone has to sign in then?]]></description>
			<content:encoded><![CDATA[<p>So CDE should be DMS for BIM?<br />
Cabinet stores for each published DWG/PDF the corresponding Projectfile (e.g. 500MB .rvt file) ?<br />
That would produce a massive amount of files and needs ridiculous amounts of storage.<br />
How to use that kind of workflow for a teamwork project ?<br />
What happens if you are not handing over the whole set of plans at once, but peace by peace?<br />
Will every publishing create a new projectfile everyone has to sign in then?</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: pcholakis		</title>
		<link>https://architosh.com/2018/01/a-primer-on-cdes-common-data-environments-for-architects/#comment-55535</link>

		<dc:creator><![CDATA[pcholakis]]></dc:creator>
		<pubDate>Mon, 15 Jan 2018 15:10:48 +0000</pubDate>
		<guid isPermaLink="false">https://architosh.com/?p=25641#comment-55535</guid>

					<description><![CDATA[A good start... but a CDE is IMPOSSIBLE without a common glossary of terms, definitions, and a LEAN life-cycle asset management approach.... learn more...  PAS, ISO are far too high level, etc.  A full understanding of requisite competencies, technologies, etc. is REQUIRED.  Learn more?  https://www.4bt.us/wp-content/uploads/2016/02/Asset-Total-Cost-of-Ownership-Efficient-Life-cycle-Management-Model.pdf
https://www.4bt.us/wp-content/uploads/2016/02/BIM-LEAN-Construction-and-a-Common-Data-Environment-CDE.pdf
https://www.wbdg.org/facilities-operations-maintenance/operation-maintenance-planning]]></description>
			<content:encoded><![CDATA[<p>A good start&#8230; but a CDE is IMPOSSIBLE without a common glossary of terms, definitions, and a LEAN life-cycle asset management approach&#8230;. learn more&#8230;  PAS, ISO are far too high level, etc.  A full understanding of requisite competencies, technologies, etc. is REQUIRED.  Learn more?  <a href="https://www.4bt.us/wp-content/uploads/2016/02/Asset-Total-Cost-of-Ownership-Efficient-Life-cycle-Management-Model.pdf" rel="nofollow ugc">https://www.4bt.us/wp-content/uploads/2016/02/Asset-Total-Cost-of-Ownership-Efficient-Life-cycle-Management-Model.pdf</a><br />
<a href="https://www.4bt.us/wp-content/uploads/2016/02/BIM-LEAN-Construction-and-a-Common-Data-Environment-CDE.pdf" rel="nofollow ugc">https://www.4bt.us/wp-content/uploads/2016/02/BIM-LEAN-Construction-and-a-Common-Data-Environment-CDE.pdf</a><br />
<a href="https://www.wbdg.org/facilities-operations-maintenance/operation-maintenance-planning" rel="nofollow ugc">https://www.wbdg.org/facilities-operations-maintenance/operation-maintenance-planning</a></p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: pcholakis		</title>
		<link>https://architosh.com/2018/01/a-primer-on-cdes-common-data-environments-for-architects/#comment-56369</link>

		<dc:creator><![CDATA[pcholakis]]></dc:creator>
		<pubDate>Mon, 15 Jan 2018 10:10:48 +0000</pubDate>
		<guid isPermaLink="false">https://architosh.com/?p=25641#comment-56369</guid>

					<description><![CDATA[A good start... but a CDE is IMPOSSIBLE without a common glossary of terms, definitions, and a LEAN life-cycle asset management approach.... learn more...  PAS, ISO are far too high level, etc.  A full understanding of requisite competencies, technologies, etc. is REQUIRED.  Learn more?  https://www.4bt.us/wp-content/uploads/2016/02/Asset-Total-Cost-of-Ownership-Efficient-Life-cycle-Management-Model.pdf
https://www.4bt.us/wp-content/uploads/2016/02/BIM-LEAN-Construction-and-a-Common-Data-Environment-CDE.pdf
https://www.wbdg.org/facilities-operations-maintenance/operation-maintenance-planning]]></description>
			<content:encoded><![CDATA[<p>A good start&#8230; but a CDE is IMPOSSIBLE without a common glossary of terms, definitions, and a LEAN life-cycle asset management approach&#8230;. learn more&#8230;  PAS, ISO are far too high level, etc.  A full understanding of requisite competencies, technologies, etc. is REQUIRED.  Learn more?  <a href="https://www.4bt.us/wp-content/uploads/2016/02/Asset-Total-Cost-of-Ownership-Efficient-Life-cycle-Management-Model.pdf" rel="nofollow ugc">https://www.4bt.us/wp-content/uploads/2016/02/Asset-Total-Cost-of-Ownership-Efficient-Life-cycle-Management-Model.pdf</a><br />
<a href="https://www.4bt.us/wp-content/uploads/2016/02/BIM-LEAN-Construction-and-a-Common-Data-Environment-CDE.pdf" rel="nofollow ugc">https://www.4bt.us/wp-content/uploads/2016/02/BIM-LEAN-Construction-and-a-Common-Data-Environment-CDE.pdf</a><br />
<a href="https://www.wbdg.org/facilities-operations-maintenance/operation-maintenance-planning" rel="nofollow ugc">https://www.wbdg.org/facilities-operations-maintenance/operation-maintenance-planning</a></p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
