<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/rss2titles.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemtitles.css"?><rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:openSearch="http://a9.com/-/spec/opensearch/1.1/" xmlns:georss="http://www.georss.org/georss" xmlns:gd="http://schemas.google.com/g/2005" xmlns:thr="http://purl.org/syndication/thread/1.0" version="2.0"><channel><atom:id>tag:blogger.com,1999:blog-6436196782988005609</atom:id><lastBuildDate>Thu, 24 Nov 2011 01:37:50 +0000</lastBuildDate><category>Construction Administration</category><category>Oops</category><category>Project Management</category><category>Gosh Darnit</category><category>Site Work</category><category>Concrete</category><category>Sights</category><category>Project Administration</category><category>Masonry</category><category>Codes</category><category>Practice Management</category><category>Design</category><category>Specifications</category><category>Roofing</category><category>Magic</category><title>Architectural Insight</title><description /><link>http://architecturalinsight.blogspot.com/</link><managingEditor>noreply@blogger.com (Albert R. Russell, AIA)</managingEditor><generator>Blogger</generator><openSearch:totalResults>73</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>25</openSearch:itemsPerPage><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/rss+xml" href="http://feeds.feedburner.com/ArchitecturalInsight" /><feedburner:info xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" uri="architecturalinsight" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com/" /><feedburner:feedFlare xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" href="http://add.my.yahoo.com/rss?url=http%3A%2F%2Ffeeds.feedburner.com%2FArchitecturalInsight" src="http://us.i1.yimg.com/us.yimg.com/i/us/my/addtomyyahoo4.gif">Subscribe with My Yahoo!</feedburner:feedFlare><feedburner:feedFlare xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" href="http://www.newsgator.com/ngs/subscriber/subext.aspx?url=http%3A%2F%2Ffeeds.feedburner.com%2FArchitecturalInsight" src="http://www.newsgator.com/images/ngsub1.gif">Subscribe with NewsGator</feedburner:feedFlare><feedburner:feedFlare xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" href="http://feeds.my.aol.com/add.jsp?url=http%3A%2F%2Ffeeds.feedburner.com%2FArchitecturalInsight" src="http://o.aolcdn.com/favorites.my.aol.com/webmaster/ffclient/webroot/locale/en-US/images/myAOLButtonSmall.gif">Subscribe with My AOL</feedburner:feedFlare><feedburner:feedFlare xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" href="http://www.bloglines.com/sub/http://feeds.feedburner.com/ArchitecturalInsight" src="http://www.bloglines.com/images/sub_modern11.gif">Subscribe with Bloglines</feedburner:feedFlare><feedburner:feedFlare xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" href="http://www.netvibes.com/subscribe.php?url=http%3A%2F%2Ffeeds.feedburner.com%2FArchitecturalInsight" src="http://www.netvibes.com/img/add2netvibes.gif">Subscribe with Netvibes</feedburner:feedFlare><feedburner:feedFlare xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" href="http://fusion.google.com/add?feedurl=http%3A%2F%2Ffeeds.feedburner.com%2FArchitecturalInsight" src="http://buttons.googlesyndication.com/fusion/add.gif">Subscribe with Google</feedburner:feedFlare><feedburner:feedFlare xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" href="http://www.pageflakes.com/subscribe.aspx?url=http%3A%2F%2Ffeeds.feedburner.com%2FArchitecturalInsight" src="http://www.pageflakes.com/ImageFile.ashx?instanceId=Static_4&amp;fileName=ATP_blu_91x17.gif">Subscribe with Pageflakes</feedburner:feedFlare><feedburner:feedFlare xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" href="http://www.plusmo.com/add?url=http%3A%2F%2Ffeeds.feedburner.com%2FArchitecturalInsight" src="http://plusmo.com/res/graphics/fbplusmo.gif">Subscribe with Plusmo</feedburner:feedFlare><feedburner:feedFlare xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" href="http://www.thefreedictionary.com/_/hp/AddRSS.aspx?http%3A%2F%2Ffeeds.feedburner.com%2FArchitecturalInsight" src="http://img.tfd.com/hp/addToTheFreeDictionary.gif">Subscribe with The Free Dictionary</feedburner:feedFlare><feedburner:feedFlare xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" href="http://www.bitty.com/manual/?contenttype=rssfeed&amp;contentvalue=http%3A%2F%2Ffeeds.feedburner.com%2FArchitecturalInsight" src="http://www.bitty.com/img/bittychicklet_91x17.gif">Subscribe with Bitty Browser</feedburner:feedFlare><feedburner:feedFlare xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" href="http://www.newsalloy.com/?rss=http%3A%2F%2Ffeeds.feedburner.com%2FArchitecturalInsight" src="http://www.newsalloy.com/subrss3.gif">Subscribe with NewsAlloy</feedburner:feedFlare><feedburner:feedFlare xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" href="http://www.live.com/?add=http%3A%2F%2Ffeeds.feedburner.com%2FArchitecturalInsight" src="http://tkfiles.storage.msn.com/x1piYkpqHC_35nIp1gLE68-wvzLZO8iXl_JMledmJQXP-XTBOLfmQv4zhj4MhcWEJh_GtoBIiAl1Mjh-ndp9k47If7hTaFno0mxW9_i3p_5qQw">Subscribe with Live.com</feedburner:feedFlare><feedburner:feedFlare xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" href="http://mix.excite.eu/add?feedurl=http%3A%2F%2Ffeeds.feedburner.com%2FArchitecturalInsight" src="http://image.excite.co.uk/mix/addtomix.gif">Subscribe with Excite MIX</feedburner:feedFlare><feedburner:feedFlare xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" href="http://www.yourminis.com/subscribe.aspx?u=http%3A%2F%2Ffeeds.feedburner.com%2FArchitecturalInsight" src="http://www.yourminis.com/images/addtoyourminisbadge.gif">Subscribe with Yourminis.com</feedburner:feedFlare><feedburner:feedFlare xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" href="http://download.attensa.com/app/get_attensa.html?feedurl=http%3A%2F%2Ffeeds.feedburner.com%2FArchitecturalInsight" src="http://www.attensa.com/blogs/attensa/WindowsLiveWriter/BadgeredintoBadges_10C02/attensa_feed_button5.gif">Subscribe with Attensa for Outlook</feedburner:feedFlare><feedburner:feedFlare xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" href="http://www.webwag.com/wwgthis.php?url=http%3A%2F%2Ffeeds.feedburner.com%2FArchitecturalInsight" src="http://www.webwag.com/images/wwgthis.gif">Subscribe with Webwag</feedburner:feedFlare><feedburner:feedFlare xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" href="http://hub.netomat.net/account/account.autoSubscribe.jspa?urls=http%3A%2F%2Ffeeds.feedburner.com%2FArchitecturalInsight" src="http://www.netomat.net/blogger/images/icon_netomat_feedbutton.gif">Subscribe with netomat Hub</feedburner:feedFlare><feedburner:feedFlare xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" href="http://www.podcastready.com/oneclick_bookmark.php?url=http%3A%2F%2Ffeeds.feedburner.com%2FArchitecturalInsight" src="http://www.podcastready.com/images/podcastready_button.gif">Subscribe with Podcast Ready</feedburner:feedFlare><feedburner:feedFlare xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" href="http://www.flurry.com/pushRssFeed.do?r=fb&amp;url=http%3A%2F%2Ffeeds.feedburner.com%2FArchitecturalInsight" src="http://www.flurry.com/images/flurry_rss_logo2.gif">Subscribe with Flurry</feedburner:feedFlare><feedburner:feedFlare xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" href="http://www.wikio.com/subscribe?url=http%3A%2F%2Ffeeds.feedburner.com%2FArchitecturalInsight" src="http://www.wikio.com/shared/img/add2wikio.gif">Subscribe with Wikio</feedburner:feedFlare><feedburner:feedFlare xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" href="http://www.dailyrotation.com/index.php?feed=http%3A%2F%2Ffeeds.feedburner.com%2FArchitecturalInsight" src="http://www.dailyrotation.com/rss-dr2.gif">Subscribe with Daily Rotation</feedburner:feedFlare><item><guid isPermaLink="false">tag:blogger.com,1999:blog-6436196782988005609.post-4746130939509800338</guid><pubDate>Thu, 24 Nov 2011 01:21:00 +0000</pubDate><atom:updated>2011-11-23T20:31:11.032-05:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Construction Administration</category><category domain="http://www.blogger.com/atom/ns#">Project Administration</category><category domain="http://www.blogger.com/atom/ns#">Practice Management</category><category domain="http://www.blogger.com/atom/ns#">Project Management</category><category domain="http://www.blogger.com/atom/ns#">Design</category><title>A Few Predictors of Building Failure in New Construction</title><description>&lt;!--[if gte mso 9]&gt;&lt;xml&gt;  &lt;w:worddocument&gt;   &lt;w:view&gt;Normal&lt;/w:View&gt;   &lt;w:zoom&gt;0&lt;/w:Zoom&gt;   &lt;w:trackmoves/&gt;   &lt;w:trackformatting/&gt;   &lt;w:punctuationkerning/&gt;   &lt;w:validateagainstschemas/&gt;   &lt;w:saveifxmlinvalid&gt;false&lt;/w:SaveIfXMLInvalid&gt;   &lt;w:ignoremixedcontent&gt;false&lt;/w:IgnoreMixedContent&gt;   &lt;w:alwaysshowplaceholdertext&gt;false&lt;/w:AlwaysShowPlaceholderText&gt;   &lt;w:donotpromoteqf/&gt;   &lt;w:lidthemeother&gt;EN-US&lt;/w:LidThemeOther&gt;   &lt;w:lidthemeasian&gt;X-NONE&lt;/w:LidThemeAsian&gt;   &lt;w:lidthemecomplexscript&gt;X-NONE&lt;/w:LidThemeComplexScript&gt;   &lt;w:compatibility&gt;    &lt;w:breakwrappedtables/&gt;    &lt;w:snaptogridincell/&gt;    &lt;w:wraptextwithpunct/&gt;    &lt;w:useasianbreakrules/&gt;    &lt;w:dontgrowautofit/&gt;    &lt;w:splitpgbreakandparamark/&gt;    &lt;w:dontvertaligncellwithsp/&gt;    &lt;w:dontbreakconstrainedforcedtables/&gt;    &lt;w:dontvertalignintxbx/&gt;    &lt;w:word11kerningpairs/&gt;    &lt;w:cachedcolbalance/&gt;   &lt;/w:Compatibility&gt;   &lt;m:mathpr&gt;    &lt;m:mathfont val="Cambria Math"&gt;    &lt;m:brkbin val="before"&gt;    &lt;m:brkbinsub val="&amp;#45;-"&gt;    &lt;m:smallfrac val="off"&gt;    &lt;m:dispdef/&gt;    &lt;m:lmargin val="0"&gt;    &lt;m:rmargin val="0"&gt;    &lt;m:defjc val="centerGroup"&gt;    &lt;m:wrapindent val="1440"&gt;    &lt;m:intlim val="subSup"&gt;    &lt;m:narylim val="undOvr"&gt;   &lt;/m:mathPr&gt;&lt;/w:WordDocument&gt; &lt;/xml&gt;&lt;![endif]--&gt;&lt;!--[if gte mso 9]&gt;&lt;xml&gt;  &lt;w:latentstyles deflockedstate="false" defunhidewhenused="true" defsemihidden="true" defqformat="false" defpriority="99" latentstylecount="267"&gt;   &lt;w:lsdexception locked="false" priority="0" semihidden="false" unhidewhenused="false" qformat="true" name="Normal"&gt;   &lt;w:lsdexception locked="false" priority="9" semihidden="false" unhidewhenused="false" qformat="true" name="heading 1"&gt;   &lt;w:lsdexception locked="false" priority="9" qformat="true" name="heading 2"&gt;   &lt;w:lsdexception locked="false" priority="9" qformat="true" name="heading 3"&gt;   &lt;w:lsdexception locked="false" priority="9" qformat="true" name="heading 4"&gt;   &lt;w:lsdexception locked="false" priority="9" qformat="true" name="heading 5"&gt;   &lt;w:lsdexception locked="false" priority="9" qformat="true" name="heading 6"&gt;   &lt;w:lsdexception locked="false" priority="9" qformat="true" name="heading 7"&gt;   &lt;w:lsdexception locked="false" priority="9" qformat="true" name="heading 8"&gt;   &lt;w:lsdexception locked="false" priority="9" qformat="true" name="heading 9"&gt;   &lt;w:lsdexception locked="false" priority="39" name="toc 1"&gt;   &lt;w:lsdexception locked="false" priority="39" name="toc 2"&gt;   &lt;w:lsdexception locked="false" priority="39" name="toc 3"&gt;   &lt;w:lsdexception locked="false" priority="39" name="toc 4"&gt;   &lt;w:lsdexception locked="false" priority="39" name="toc 5"&gt;   &lt;w:lsdexception locked="false" priority="39" name="toc 6"&gt;   &lt;w:lsdexception locked="false" priority="39" name="toc 7"&gt;   &lt;w:lsdexception locked="false" priority="39" name="toc 8"&gt;   &lt;w:lsdexception locked="false" priority="39" name="toc 9"&gt;   &lt;w:lsdexception locked="false" priority="35" qformat="true" name="caption"&gt;   &lt;w:lsdexception locked="false" priority="10" semihidden="false" unhidewhenused="false" qformat="true" name="Title"&gt;   &lt;w:lsdexception locked="false" priority="1" name="Default Paragraph Font"&gt;   &lt;w:lsdexception locked="false" priority="11" semihidden="false" unhidewhenused="false" qformat="true" name="Subtitle"&gt;   &lt;w:lsdexception locked="false" priority="22" semihidden="false" unhidewhenused="false" qformat="true" name="Strong"&gt;   &lt;w:lsdexception locked="false" priority="20" semihidden="false" unhidewhenused="false" qformat="true" name="Emphasis"&gt;   &lt;w:lsdexception locked="false" priority="59" semihidden="false" unhidewhenused="false" name="Table Grid"&gt;   &lt;w:lsdexception locked="false" unhidewhenused="false" name="Placeholder Text"&gt;   &lt;w:lsdexception locked="false" priority="1" semihidden="false" unhidewhenused="false" qformat="true" name="No Spacing"&gt;   &lt;w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading"&gt;   &lt;w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List"&gt;   &lt;w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid"&gt;   &lt;w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1"&gt;   &lt;w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2"&gt;   &lt;w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1"&gt;   &lt;w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2"&gt;   &lt;w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1"&gt;   &lt;w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2"&gt;   &lt;w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3"&gt;   &lt;w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List"&gt;   &lt;w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading"&gt;   &lt;w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List"&gt;   &lt;w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid"&gt;   &lt;w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading Accent 1"&gt;   &lt;w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List Accent 1"&gt;   &lt;w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid Accent 1"&gt;   &lt;w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1 Accent 1"&gt;   &lt;w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2 Accent 1"&gt;   &lt;w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1 Accent 1"&gt;   &lt;w:lsdexception locked="false" unhidewhenused="false" name="Revision"&gt;   &lt;w:lsdexception locked="false" priority="34" semihidden="false" unhidewhenused="false" qformat="true" name="List Paragraph"&gt;   &lt;w:lsdexception locked="false" priority="29" semihidden="false" unhidewhenused="false" qformat="true" name="Quote"&gt;   &lt;w:lsdexception locked="false" priority="30" semihidden="false" unhidewhenused="false" qformat="true" name="Intense Quote"&gt;   &lt;w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2 Accent 1"&gt;   &lt;w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1 Accent 1"&gt;   &lt;w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2 Accent 1"&gt;   &lt;w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3 Accent 1"&gt;   &lt;w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List Accent 1"&gt;   &lt;w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading Accent 1"&gt;   &lt;w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List Accent 1"&gt;   &lt;w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid Accent 1"&gt;   &lt;w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading Accent 2"&gt;   &lt;w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List Accent 2"&gt;   &lt;w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid Accent 2"&gt;   &lt;w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1 Accent 2"&gt;   &lt;w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2 Accent 2"&gt;   &lt;w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1 Accent 2"&gt;   &lt;w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2 Accent 2"&gt;   &lt;w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1 Accent 2"&gt;   &lt;w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2 Accent 2"&gt;   &lt;w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3 Accent 2"&gt;   &lt;w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List Accent 2"&gt;   &lt;w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading Accent 2"&gt;   &lt;w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List Accent 2"&gt;   &lt;w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid Accent 2"&gt;   &lt;w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading Accent 3"&gt;   &lt;w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List Accent 3"&gt;   &lt;w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid Accent 3"&gt;   &lt;w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1 Accent 3"&gt;   &lt;w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2 Accent 3"&gt;   &lt;w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1 Accent 3"&gt;   &lt;w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2 Accent 3"&gt;   &lt;w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1 Accent 3"&gt;   &lt;w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2 Accent 3"&gt;   &lt;w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3 Accent 3"&gt;   &lt;w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List Accent 3"&gt;   &lt;w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading Accent 3"&gt;   &lt;w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List Accent 3"&gt;   &lt;w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid Accent 3"&gt;   &lt;w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading Accent 4"&gt;   &lt;w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List Accent 4"&gt;   &lt;w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid Accent 4"&gt;   &lt;w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1 Accent 4"&gt;   &lt;w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2 Accent 4"&gt;   &lt;w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1 Accent 4"&gt;   &lt;w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2 Accent 4"&gt;   &lt;w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1 Accent 4"&gt;   &lt;w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2 Accent 4"&gt;   &lt;w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3 Accent 4"&gt;   &lt;w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List Accent 4"&gt;   &lt;w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading Accent 4"&gt;   &lt;w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List Accent 4"&gt;   &lt;w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid Accent 4"&gt;   &lt;w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading Accent 5"&gt;   &lt;w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List Accent 5"&gt;   &lt;w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid Accent 5"&gt;   &lt;w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1 Accent 5"&gt;   &lt;w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2 Accent 5"&gt;   &lt;w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1 Accent 5"&gt;   &lt;w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2 Accent 5"&gt;   &lt;w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1 Accent 5"&gt;   &lt;w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2 Accent 5"&gt;   &lt;w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3 Accent 5"&gt;   &lt;w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List Accent 5"&gt;   &lt;w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading Accent 5"&gt;   &lt;w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List Accent 5"&gt;   &lt;w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid Accent 5"&gt;   &lt;w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading Accent 6"&gt;   &lt;w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List Accent 6"&gt;   &lt;w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid Accent 6"&gt;   &lt;w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1 Accent 6"&gt;   &lt;w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2 Accent 6"&gt;   &lt;w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1 Accent 6"&gt;   &lt;w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2 Accent 6"&gt;   &lt;w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1 Accent 6"&gt;   &lt;w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2 Accent 6"&gt;   &lt;w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3 Accent 6"&gt;   &lt;w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List Accent 6"&gt;   &lt;w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading Accent 6"&gt;   &lt;w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List Accent 6"&gt;   &lt;w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid Accent 6"&gt;   &lt;w:lsdexception locked="false" priority="19" semihidden="false" unhidewhenused="false" qformat="true" name="Subtle Emphasis"&gt;   &lt;w:lsdexception locked="false" priority="21" semihidden="false" unhidewhenused="false" qformat="true" name="Intense Emphasis"&gt;   &lt;w:lsdexception locked="false" priority="31" semihidden="false" unhidewhenused="false" qformat="true" name="Subtle Reference"&gt;   &lt;w:lsdexception locked="false" priority="32" semihidden="false" unhidewhenused="false" qformat="true" name="Intense Reference"&gt;   &lt;w:lsdexception locked="false" priority="33" semihidden="false" unhidewhenused="false" qformat="true" name="Book Title"&gt;   &lt;w:lsdexception locked="false" priority="37" name="Bibliography"&gt;   &lt;w:lsdexception locked="false" priority="39" qformat="true" name="TOC Heading"&gt;  &lt;/w:LatentStyles&gt; &lt;/xml&gt;&lt;![endif]--&gt;&lt;!--[if gte mso 10]&gt; &lt;style&gt;  /* Style Definitions */  table.MsoNormalTable  {mso-style-name:"Table Normal";  mso-tstyle-rowband-size:0;  mso-tstyle-colband-size:0;  mso-style-noshow:yes;  mso-style-priority:99;  mso-style-qformat:yes;  mso-style-parent:"";  mso-padding-alt:0in 5.4pt 0in 5.4pt;  mso-para-margin-top:0in;  mso-para-margin-right:0in;  mso-para-margin-bottom:10.0pt;  mso-para-margin-left:0in;  line-height:115%;  mso-pagination:widow-orphan;  font-size:11.0pt;  font-family:"Arial","sans-serif";  mso-bidi-font-family:"Times New Roman";  mso-bidi-theme-font:minor-bidi;} &lt;/style&gt; &lt;![endif]--&gt;The following suggested predictors of building failure in new construction are based on years of experience tracing building failures to their causes. While the failures may express themselves as discrete detail flaws, underlying causes are often found in contractual decision making, project administration and management, and in conceptual design. The following predictors do not guarantee building failure, but they do indicate a heightened risk of failure.  &lt;ol&gt;&lt;li&gt;&lt;span style="font-family:Wingdings;mso-fareast-font-family:Wingdings;mso-bidi-font-family: Wingdings"&gt;&lt;span style="mso-list:Ignore"&gt;&lt;span style="font:7.0pt &amp;quot;Times New Roman&amp;quot;"&gt;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;b style="mso-bidi-font-weight:normal"&gt;Building from Schematic Design or other preliminary design documents&lt;/b&gt; – Schematic Design Drawings or other preliminary drawings that are prepared in CAD or a related computer program can appear quite precise, so it is possible to mistakenly expect such drawings to be sufficient for construction. Schematic Design Drawings typically lack sufficient detail for construction and may not be well conceived in terms of how materials and building components relate to one another. There is a high risk of building performance problems, including but not limited to building envelope leaks, when Schematic Drawings or other preliminary drawings are used as the basis of construction.&lt;/li&gt;&lt;li&gt;&lt;b style="mso-bidi-font-weight:normal"&gt;Eliminating or drastically limiting the Architect’s role during construction &lt;/b&gt;– If the Architect is dismissed from the construction phase of a project, or if the Architect’s services are reduced below the standard of practice in order to save cost or expedite construction, there is a heightened risk that changes and substitutions will be made without the review and scrutiny of the Architect, who would be expected to consider the compatibility of changes and substitutions with the design intent or even with code requirements and is expected to know more than contractors do about these matters. (Similar problems can occur if the Architect’s construction administration services are delegated to inexperienced staff, who may not have sufficient knowledge about the materials and systems they encounter on the construction site.)&lt;/li&gt;&lt;li&gt;&lt;b style="mso-bidi-font-weight:normal"&gt;Insufficient consideration of climate and weather&lt;/b&gt; – Success of building designs and design features in one climate are not good predictors of success in a different climate. This is true for building envelope designs in different geographic locations, and it is true for interior design features, materials, and details that are mistakenly used in exterior applications where they are inadequate for exposure to weather, including precipitation and exterior variations in temperature. It is also true for moisture sensitive interior materials that are subjected to high humidity related to building use (e.g., a swimming pool environment).&lt;/li&gt;&lt;li&gt;&lt;b style="mso-bidi-font-weight:normal"&gt;Assuming that the selection of an innovative, energy efficient product or system will, &lt;u&gt;on its own&lt;/u&gt;, lead to a durable, energy efficient building &lt;/b&gt;– Examples include rot failures related to SIP (structural insulated panel) construction where panel joints were not properly sized and sealed and where OSB facing material was exposed to moisture in the belief (espoused by the panel manufacturer) that OSB was a waterproof material that need not be protected from moisture.&lt;/li&gt;&lt;/ol&gt;  &lt;p class="MsoNormal"&gt;Certainly, there can be other predictors of building failure in new construction, and avoiding the predictors above may not lead to a trouble free building every time. Still, the issues above appear to be common enough to warrant their listing as predictors of building failure.&lt;/p&gt;&lt;div class="blogger-post-footer"&gt;Copyright Albert R. Russell 2009&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6436196782988005609-4746130939509800338?l=architecturalinsight.blogspot.com' alt='' /&gt;&lt;/div&gt;</description><link>http://architecturalinsight.blogspot.com/2011/11/few-predictors-of-building-failure-in.html</link><author>noreply@blogger.com (Albert R. Russell, AIA)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-6436196782988005609.post-6200013285243745723</guid><pubDate>Tue, 22 Nov 2011 16:15:00 +0000</pubDate><atom:updated>2011-11-22T11:21:18.655-05:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Construction Administration</category><category domain="http://www.blogger.com/atom/ns#">Site Work</category><category domain="http://www.blogger.com/atom/ns#">Project Administration</category><category domain="http://www.blogger.com/atom/ns#">Practice Management</category><category domain="http://www.blogger.com/atom/ns#">Project Management</category><title>Planning for Concealed Site Conditions</title><description>Discovery of concealed site conditions can raise havoc with a project, possibly disrupting the construction schedule and adversely impacting the project budget. Here's a link to an article I wrote a few years ago to share some of my experience with concealed site conditions: &lt;a href="https://docs.google.com/open?id=0BwcXdaHJ4h71YWY2Y2EyYjgtZTQ0Yy00Mzc3LTgxNjYtMDczNzE3MTc5ZmVh"&gt;Planning for Concealed Site Conditions&lt;/a&gt;&lt;div class="blogger-post-footer"&gt;Copyright Albert R. Russell 2009&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6436196782988005609-6200013285243745723?l=architecturalinsight.blogspot.com' alt='' /&gt;&lt;/div&gt;</description><link>http://architecturalinsight.blogspot.com/2011/11/planning-for-concealed-site-conditions.html</link><author>noreply@blogger.com (Albert R. Russell, AIA)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-6436196782988005609.post-1842553269995552342</guid><pubDate>Mon, 21 Nov 2011 14:14:00 +0000</pubDate><atom:updated>2011-11-21T09:55:43.845-05:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Project Administration</category><category domain="http://www.blogger.com/atom/ns#">Practice Management</category><category domain="http://www.blogger.com/atom/ns#">Project Management</category><category domain="http://www.blogger.com/atom/ns#">Design</category><title>Delegating for Architects</title><description>Project results are directly related to the effectiveness of project communications. Successful delegation of responsibilities and tasks depends on effective communication. Download "&lt;a href="https://docs.google.com/open?id=0BwcXdaHJ4h71MWJhMTZiZDgtZWIxOS00M2U2LWE3Y2UtMjU0YzlkYjQxY2U0"&gt;Delegating for Architects&lt;/a&gt;" to read more about this.&lt;div class="blogger-post-footer"&gt;Copyright Albert R. Russell 2009&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6436196782988005609-1842553269995552342?l=architecturalinsight.blogspot.com' alt='' /&gt;&lt;/div&gt;</description><link>http://architecturalinsight.blogspot.com/2011/11/delegating-for-architects.html</link><author>noreply@blogger.com (Albert R. Russell, AIA)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-6436196782988005609.post-8988464144317364371</guid><pubDate>Thu, 29 Sep 2011 13:33:00 +0000</pubDate><atom:updated>2011-09-29T09:55:25.968-04:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Construction Administration</category><category domain="http://www.blogger.com/atom/ns#">Project Administration</category><category domain="http://www.blogger.com/atom/ns#">Project Management</category><category domain="http://www.blogger.com/atom/ns#">Design</category><title>Value Engineering</title><description>Any discussion of value engineering (V.E.) is likely to produce a rush of criticisms of the process if you work in an architecture or engineering practice. The architects and engineers are likely to recall bad experiences when V.E. was started late, approaching or following the completion of construction documents, at a time when the project schedule did not allow sufficient time to fully consider consequences and implement V.E. changes in a comprehensive and well coordinated manner. They are likely to complain that "V.E. stripped the value out of the project."&lt;br /&gt;&lt;br /&gt;A better approach to V.E. is to start it earlier, when material and system decisions are being formulated and before a lot of time is invested in developing applicable details and specifications.&lt;br /&gt;&lt;br /&gt;The Whole Building Design Guide (http://www.wbdg.org/resources/value_engineering.php) offers an excellent synopsis of V.E. and a clear picture of the advantages of doing it earlier in the life of a project.&lt;div class="blogger-post-footer"&gt;Copyright Albert R. Russell 2009&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6436196782988005609-8988464144317364371?l=architecturalinsight.blogspot.com' alt='' /&gt;&lt;/div&gt;</description><link>http://architecturalinsight.blogspot.com/2011/09/value-engineering.html</link><author>noreply@blogger.com (Albert R. Russell, AIA)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-6436196782988005609.post-6796613898428444782</guid><pubDate>Tue, 01 Dec 2009 16:03:00 +0000</pubDate><atom:updated>2009-12-01T11:41:12.799-05:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Construction Administration</category><category domain="http://www.blogger.com/atom/ns#">Project Management</category><category domain="http://www.blogger.com/atom/ns#">Design</category><title>"By Others" and "N.I.C."</title><description>The terms "By Others" and "Not In Contract" (or "N.I.C.") can add confusion to construction documents if the intent of the terms is not well established within the documents. The note "By Others" on a drawing may be intended to indicate that an item is to be provided by a different trade under the same overall construction contract, and "N.I.C." may be intended similarly to indicate an item that is to be provided by a different trade. However, these notes may have different meanings for different readers. Without further clarification, a general contractor seeing a note "By Others" or "N.I.C." may take it at face value to mean the item is not part of the general contractor's scope at all, even if the intent of the note was to indicate its exclusion only from the work of a particular trade or subtrade or a particular bid package. It is better to develop and use terms that convey the intent more precisely. For example, if an item shown on a site plan is intended to be provided by an electrical contractor whose work scope is also established on other drawings, it may be appropriate for the site plan to include the term "By Electrical Contractor" in a note relating to the item. Alternatively, it may be practical for all items that are not intended to be part of the site work to be noted "Not by Site Work Contractor", provided the term does not contradict a general contractor's contractual authority to assign such work. Drawings which are specifically intended to describe the work of a particular trade or subtrade can benefit from a List of Abbreviations or a List of Terms which clarify the meaning of such notes in order to minimize confusion.&lt;div class="blogger-post-footer"&gt;Copyright Albert R. Russell 2009&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6436196782988005609-6796613898428444782?l=architecturalinsight.blogspot.com' alt='' /&gt;&lt;/div&gt;</description><link>http://architecturalinsight.blogspot.com/2009/12/by-others-and-nic.html</link><author>noreply@blogger.com (Albert R. Russell, AIA)</author><thr:total>1</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-6436196782988005609.post-6216122347491495401</guid><pubDate>Wed, 04 Nov 2009 13:39:00 +0000</pubDate><atom:updated>2009-11-04T10:41:05.548-05:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Construction Administration</category><category domain="http://www.blogger.com/atom/ns#">Project Management</category><title>Reviewing the Contractor's Application for Payment</title><description>On most public construction projects, the Architect reviews the Contractor's monthly Applications for Payment (a.k.a. "Requisitions") and certifies the amount to be paid to the Contractor for that month. If the Application is made on AIA Document G702, the front page includes the names of the Project, the Owner, the Contractor, and the Architect, an Application number, date(s) indicating the period covered by the Application, an overview accounting of the monetary status of the construction project, starting with the original contract sum and including a calculation of the Current Payment Due, considering change orders, the total amount completed and stored to date, Retainage to be withheld, and previous certificates for payment. The front page also includes a Change Order Summary, certification by the Contractor, conditions (terms) of certification by the Architect, and the amount certified. Continuation sheets should break down the contract sum and progress according to the approved Schedule of Values (see&lt;span style="font-size:100%;"&gt;&lt;a href="http://architecturalinsight.blogspot.com/2009/04/pay-close-attention-to-schedule-of.html"&gt;&lt;span style="font-weight: bold;"&gt; &lt;/span&gt;The Schedule of Values deserves close attention&lt;/a&gt;&lt;/span&gt;) and also include a detailed accounting of the status of work on approved Change Orders.&lt;br /&gt;&lt;br /&gt;The Architect should review even the basic information on the front page before looking at the detailed information on the continuation sheets. It helps to have a copy of the previous month's Application in hand for comparison. Once you determine that the current month's Application is for the appropriate project (seriously), check the Original Contract Sum. In more than one instance, a contractor has changed the Original Contract Sum on an Application for Payment, resulting in an increase in payment without an approved Change Order. The Original Contract Sum should remain the same for the life of the Contract. Before turning to the continuation sheets, the Architect should apply the same scrutiny to the rest of the front page calculations and the wording of the certification. Different certification language may carry different liability.&lt;br /&gt;&lt;br /&gt;Detailed information on the continuation sheets is typically generated as part of a "pencil requisition" process and in anticipation of work to be completed by the end of the month. The Architect needs to consider whether the final Application for the month represents work that was actually accomplished by the end of the month. If the Architect is aware that an anticipated material delivery did not occur, then the Architect should not certify payment for that. Likewise, if the Architect is aware that a specific work item was not completed, then the Architect should not certifiy payment as if the item had been completed. Necessary adjustments to the continuation sheets must be carried over to the front page and to the overall amount certified by the Architect for the period covered by the Application. It may be practical for the Contractor to make the necessary adjustments and then resubmit a corrected Application for the Architect's certification. If timely payment is an overriding concern, then the Architect may need to make the adjustments by annotating the Application, certifying a reduced amount, and notifying both the Owner and the Contractor of the reasons for the adjustments. (See also &lt;span style="font-size:100%;"&gt;&lt;a href="http://architecturalinsight.blogspot.com/2009/04/it-takes-timely-money-to-make-project.html"&gt;It takes timely money to make a project go&lt;/a&gt;&lt;/span&gt; )&lt;span style="font-size:100%;"&gt;&lt;a href="http://architecturalinsight.blogspot.com/2009/04/it-takes-timely-money-to-make-project.html"&gt;&lt;span style="font-weight: bold;"&gt; &lt;/span&gt;&lt;br /&gt;&lt;/a&gt;&lt;/span&gt;&lt;div class="blogger-post-footer"&gt;Copyright Albert R. Russell 2009&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6436196782988005609-6216122347491495401?l=architecturalinsight.blogspot.com' alt='' /&gt;&lt;/div&gt;</description><link>http://architecturalinsight.blogspot.com/2009/11/reviewing-contractors-application-for.html</link><author>noreply@blogger.com (Albert R. Russell, AIA)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-6436196782988005609.post-8736704986083533334</guid><pubDate>Sun, 01 Nov 2009 14:46:00 +0000</pubDate><atom:updated>2009-11-01T10:35:00.100-05:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Project Administration</category><category domain="http://www.blogger.com/atom/ns#">Project Management</category><title>Manage Design Costs with Early Project Overtime</title><description>One of Mike's PM tips for managing design costs on a project: "If you know you are going to have to work overtime on a project," he said, "do it in the beginning. It costs less to do overtime when there are only one or two people working on a project." (See &lt;a href="http://architecturalinsight.blogspot.com/2009/04/purposeful-chaos-2-minute-design.html"&gt;Purposeful chaos (the 2-minute design offense)&lt;/a&gt;)&lt;br /&gt;&lt;br /&gt;This makes a lot of sense when considering a project on a compressed time line. If you're trying to figure out how to get all the work done in a short period of time, the least attractive alternative is having an army of designers and drafters burning the midnight oil and generating design questions as the completion deadline approaches. Eleventh hour overtime can quickly burn through budgeted hours and fee dollars, and too many new or unanswered questions at that stage can lead to unplanned chaos.&lt;br /&gt;&lt;br /&gt;It's also interesting to consider how this principle of early overtime might benefit progress and labor costs on a construction site. Early trades - like earthwork, concrete, and steel - set the stage for a larger work force, and trades can multiply as the project becomes ready for their work.&lt;div class="blogger-post-footer"&gt;Copyright Albert R. Russell 2009&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6436196782988005609-8736704986083533334?l=architecturalinsight.blogspot.com' alt='' /&gt;&lt;/div&gt;</description><link>http://architecturalinsight.blogspot.com/2009/11/manage-design-costs-with-early-project.html</link><author>noreply@blogger.com (Albert R. Russell, AIA)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-6436196782988005609.post-912773779690839770</guid><pubDate>Sun, 01 Nov 2009 14:35:00 +0000</pubDate><atom:updated>2009-11-01T09:45:32.297-05:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Sights</category><category domain="http://www.blogger.com/atom/ns#">Masonry</category><category domain="http://www.blogger.com/atom/ns#">Design</category><title>Masonry Details, Toledo</title><description>&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://4.bp.blogspot.com/_bkNp6hieiJM/Su2eqYh3orI/AAAAAAAAAMs/gOz7kX9D5D8/s1600-h/IMG_6437.JPG"&gt;&lt;img style="float:left; margin:0 10px 10px 0;cursor:pointer; cursor:hand;width: 225px; height: 400px;" src="http://4.bp.blogspot.com/_bkNp6hieiJM/Su2eqYh3orI/AAAAAAAAAMs/gOz7kX9D5D8/s400/IMG_6437.JPG" border="0" alt=""id="BLOGGER_PHOTO_ID_5399145979263296178" /&gt;&lt;/a&gt;&lt;div class="blogger-post-footer"&gt;Copyright Albert R. Russell 2009&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6436196782988005609-912773779690839770?l=architecturalinsight.blogspot.com' alt='' /&gt;&lt;/div&gt;</description><link>http://architecturalinsight.blogspot.com/2009/11/masonry-details-toledo.html</link><author>noreply@blogger.com (Albert R. Russell, AIA)</author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://4.bp.blogspot.com/_bkNp6hieiJM/Su2eqYh3orI/AAAAAAAAAMs/gOz7kX9D5D8/s72-c/IMG_6437.JPG" height="72" width="72" /><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-6436196782988005609.post-2214855130053640304</guid><pubDate>Thu, 29 Oct 2009 22:25:00 +0000</pubDate><atom:updated>2009-10-29T18:51:24.053-04:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Construction Administration</category><title>Shop Drawing Review Comments</title><description>While it can be frustrating for an architect to review shop drawing submittals that appear to lack adequate preparation or attention to contract requirements, it is still important for the architect to maintain professional decorum in the review comments. This is equally true for the review of resubmitted shop drawings that do not include corrections noted by the architect on a previous submittal. An inadequate resubmittal may warrant separate correspondence from the architect to the contractor noting the repeated deficiencies and, if applicable, the possibility of adverse effects on the project schedule; but the review comments and correspondence should communicate clearly and without sarcasm or accusations. For example, "Why can't you get it?" is not a proper architect review comment on a shop drawing submittal.&lt;div class="blogger-post-footer"&gt;Copyright Albert R. Russell 2009&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6436196782988005609-2214855130053640304?l=architecturalinsight.blogspot.com' alt='' /&gt;&lt;/div&gt;</description><link>http://architecturalinsight.blogspot.com/2009/10/shop-drawing-review-comments.html</link><author>noreply@blogger.com (Albert R. Russell, AIA)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-6436196782988005609.post-1600145336045154389</guid><pubDate>Fri, 22 May 2009 12:56:00 +0000</pubDate><atom:updated>2009-07-18T21:35:56.769-04:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Specifications</category><category domain="http://www.blogger.com/atom/ns#">Project Administration</category><category domain="http://www.blogger.com/atom/ns#">Practice Management</category><category domain="http://www.blogger.com/atom/ns#">Project Management</category><category domain="http://www.blogger.com/atom/ns#">Design</category><title>Construction Documents Coordination Matrix</title><description>&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://2.bp.blogspot.com/_bkNp6hieiJM/ShajN7iiwYI/AAAAAAAAAMM/lr_2W9UQqpw/s1600-h/AE+Coordination+Matrix.JPG"&gt;&lt;img style="margin: 0pt 10px 10px 0pt; float: left; cursor: pointer; width: 392px; height: 400px;" src="http://2.bp.blogspot.com/_bkNp6hieiJM/ShajN7iiwYI/AAAAAAAAAMM/lr_2W9UQqpw/s400/AE+Coordination+Matrix.JPG" alt="" id="BLOGGER_PHOTO_ID_5338633868010504578" border="0" /&gt;&lt;/a&gt;&lt;span style="font-size:100%;"&gt;&lt;br /&gt;&lt;br /&gt;It may look a little "geeky", but this matrix can be an effective tool for considering interdisciplinary coordination needs. The design disciplines for a project are listed across the top and down one side. The intersection points represent coordination between disciplines (e.g., between Civil/Site and Electrical). Seeing the possibilities in this format can help to minimize coordination gaps. On a given project, the extent and specifics of coordination will differ from point to point, and the design displines may also differ. Still, seeing an intersection point can prompt thoughts about needed coordination between any two disciplines. For example, where Civil/Site meets Foodservice, it may bring to mind the need to coordinate the locations of exterior condensing units with site work. Etc. Etc. Etc&lt;/span&gt;.&lt;br /&gt;&lt;br /&gt;Looking at this coordination matrix, it is also easy to see how extensive coordination really is (and must be) on an architectural project. On some complex projects, coordination can be seen as a full time job in itself, from the coordination of consulting agreement scopes of work to the coordination of sub-trade scopes of work and the dotting of i's and crossing of t's in construction documents.&lt;div class="blogger-post-footer"&gt;Copyright Albert R. Russell 2009&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6436196782988005609-1600145336045154389?l=architecturalinsight.blogspot.com' alt='' /&gt;&lt;/div&gt;</description><link>http://architecturalinsight.blogspot.com/2009/05/design-coordination-matrix.html</link><author>noreply@blogger.com (Albert R. Russell, AIA)</author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://2.bp.blogspot.com/_bkNp6hieiJM/ShajN7iiwYI/AAAAAAAAAMM/lr_2W9UQqpw/s72-c/AE+Coordination+Matrix.JPG" height="72" width="72" /><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-6436196782988005609.post-4817787576776279160</guid><pubDate>Wed, 20 May 2009 14:07:00 +0000</pubDate><atom:updated>2009-07-18T21:38:14.029-04:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Practice Management</category><category domain="http://www.blogger.com/atom/ns#">Design</category><title>Construction Documents Peer Review</title><description>&lt;span style="font-size:100%;"&gt;&lt;span style="font-family:arial;"&gt;Joe Iano (see &lt;/span&gt;&lt;/span&gt;&lt;a href="http://www.ianosbackfill.com/" target="_blank"&gt;Iano's backfill&lt;/a&gt; &lt;span style="font-size:100%;"&gt;&lt;span style="font-family:arial;"&gt;) shared with me an approach to quality review of construction documents that is used by a prominent firm where he is employed in Seattle (see the AIA 2009 Honor Award Firm of the Year Olson Sundberg Kundig Allen Architects in the May 2009 issue of Architectural Record). Joe said the firm has senior non-project staff review construction documents together with staff who developed the documents for a given project. The issues, concerns, and comments that are raised during the review can go a long way toward mentoring less experienced staff.&lt;br /&gt;&lt;br /&gt;A similar approach could work in utilizing the services of an independent peer review architect who can review the construction documents together with the staff who developed the documents. Compared to a "redline only" mark-up of drawings and specifications, the interactive review process can include a substantive conversation that carries longer term value for the firm, while taking advantage of review expertise outside the firm.&lt;/span&gt;&lt;/span&gt;&lt;div class="blogger-post-footer"&gt;Copyright Albert R. Russell 2009&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6436196782988005609-4817787576776279160?l=architecturalinsight.blogspot.com' alt='' /&gt;&lt;/div&gt;</description><link>http://architecturalinsight.blogspot.com/2009/05/interactive-peer-review-of-construction.html</link><author>noreply@blogger.com (Albert R. Russell, AIA)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-6436196782988005609.post-3817010630557808846</guid><pubDate>Wed, 20 May 2009 13:13:00 +0000</pubDate><atom:updated>2009-05-20T09:43:03.234-04:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Specifications</category><category domain="http://www.blogger.com/atom/ns#">Practice Management</category><category domain="http://www.blogger.com/atom/ns#">Project Management</category><category domain="http://www.blogger.com/atom/ns#">Design</category><title>The 50-50 Rule</title><description>&lt;span style="font-size:100%;"&gt;&lt;span style="font-family: arial;"&gt;Jobs vary in the proportion of time required for technical work ("stuff") vs. people work (communication, cooperation, management, etc.). Some jobs may consist of less than 50% stuff, but most jobs done effectively require at least 50% people work. If you are doing a technical job in architecture (or most any other field), and you think that your job is 100% or near 100% "stuff" and 0% or near 0% "people", you are probably not doing your job effectively, and you are probably neglecting at least 50% (the "people" part) of your job.&lt;/span&gt;&lt;span style="font-family: arial;"&gt;&lt;br /&gt;&lt;br /&gt;When you develop drawings - plans, sections, elevations, details, etc. - and specifications, you depend on other people to understand and make effective use of those drawings and specifications to produce desirable results. Your work must effectively communicate with others, be they other designers, consultants, owners, users, permitting authorities, estimators, bidders, contractors, subcontractors, material suppliers, and others. And the value of your work - especially technical work - is diminished by the extent that it does not effectively communicate with others.&lt;/span&gt;&lt;span style="font-family: arial;"&gt;&lt;br /&gt;&lt;br /&gt;While jobs do vary in the actual proportion of "stuff" vs. "people", a good approach to a technical job is one based on a consideration that at least 50% of the job is people related. That's the 50-50 rule.&lt;/span&gt;&lt;/span&gt;&lt;div class="blogger-post-footer"&gt;Copyright Albert R. Russell 2009&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6436196782988005609-3817010630557808846?l=architecturalinsight.blogspot.com' alt='' /&gt;&lt;/div&gt;</description><link>http://architecturalinsight.blogspot.com/2009/05/50-50-rule.html</link><author>noreply@blogger.com (Albert R. Russell, AIA)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-6436196782988005609.post-5598210082142172706</guid><pubDate>Tue, 12 May 2009 23:45:00 +0000</pubDate><atom:updated>2009-05-14T20:08:05.408-04:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Sights</category><category domain="http://www.blogger.com/atom/ns#">Design</category><title>More Doors and Doorways (Spain)</title><description>&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://3.bp.blogspot.com/_bkNp6hieiJM/SgoKyP0m5HI/AAAAAAAAAL8/zYrWYGr96WU/s1600-h/IMG_6497.JPG"&gt;&lt;img style="margin: 0pt 10px 10px 0pt; float: left; cursor: pointer; width: 130px; height: 200px;" src="http://3.bp.blogspot.com/_bkNp6hieiJM/SgoKyP0m5HI/AAAAAAAAAL8/zYrWYGr96WU/s200/IMG_6497.JPG" alt="" id="BLOGGER_PHOTO_ID_5335088566930695282" border="0" /&gt;&lt;/a&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://4.bp.blogspot.com/_bkNp6hieiJM/SgoKx9LAGDI/AAAAAAAAAL0/YEULkY_nEkM/s1600-h/IMG_6484.JPG"&gt;&lt;img style="margin: 0pt 10px 10px 0pt; float: left; cursor: pointer; width: 125px; height: 200px;" src="http://4.bp.blogspot.com/_bkNp6hieiJM/SgoKx9LAGDI/AAAAAAAAAL0/YEULkY_nEkM/s200/IMG_6484.JPG" alt="" id="BLOGGER_PHOTO_ID_5335088561924347954" border="0" /&gt;&lt;/a&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://4.bp.blogspot.com/_bkNp6hieiJM/SgoKxp1twVI/AAAAAAAAALs/MSiFsCrbTNw/s1600-h/JQR+Spain+2+087.jpg"&gt;&lt;img style="margin: 0pt 10px 10px 0pt; float: left; cursor: pointer; width: 104px; height: 200px;" src="http://4.bp.blogspot.com/_bkNp6hieiJM/SgoKxp1twVI/AAAAAAAAALs/MSiFsCrbTNw/s200/JQR+Spain+2+087.jpg" alt="" id="BLOGGER_PHOTO_ID_5335088556734792018" border="0" /&gt;&lt;/a&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://3.bp.blogspot.com/_bkNp6hieiJM/SgoKxd3VR6I/AAAAAAAAALk/yoHqQHR5puE/s1600-h/JQR+Spain+051.jpg"&gt;&lt;img style="margin: 0pt 10px 10px 0pt; float: left; cursor: pointer; width: 113px; height: 200px;" src="http://3.bp.blogspot.com/_bkNp6hieiJM/SgoKxd3VR6I/AAAAAAAAALk/yoHqQHR5puE/s200/JQR+Spain+051.jpg" alt="" id="BLOGGER_PHOTO_ID_5335088553520351138" border="0" /&gt;&lt;/a&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://4.bp.blogspot.com/_bkNp6hieiJM/SgoKxVM2hUI/AAAAAAAAALc/OHkEmn75Ghg/s1600-h/Copy+of+JQR+Spain+074.jpg"&gt;&lt;img style="margin: 0pt 10px 10px 0pt; float: left; cursor: pointer; width: 160px; height: 200px;" src="http://4.bp.blogspot.com/_bkNp6hieiJM/SgoKxVM2hUI/AAAAAAAAALc/OHkEmn75Ghg/s200/Copy+of+JQR+Spain+074.jpg" alt="" id="BLOGGER_PHOTO_ID_5335088551194690882" border="0" /&gt;&lt;/a&gt;&lt;div class="blogger-post-footer"&gt;Copyright Albert R. Russell 2009&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6436196782988005609-5598210082142172706?l=architecturalinsight.blogspot.com' alt='' /&gt;&lt;/div&gt;</description><link>http://architecturalinsight.blogspot.com/2009/05/more-doors-and-doorways-spain.html</link><author>noreply@blogger.com (Albert R. Russell, AIA)</author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://3.bp.blogspot.com/_bkNp6hieiJM/SgoKyP0m5HI/AAAAAAAAAL8/zYrWYGr96WU/s72-c/IMG_6497.JPG" height="72" width="72" /><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-6436196782988005609.post-8012017616506319045</guid><pubDate>Tue, 12 May 2009 23:30:00 +0000</pubDate><atom:updated>2009-05-14T20:08:34.629-04:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Sights</category><category domain="http://www.blogger.com/atom/ns#">Design</category><title>Doors and Doorways (Spain)</title><description>&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://1.bp.blogspot.com/_bkNp6hieiJM/SgoJoTxXBYI/AAAAAAAAALU/ctOYXynp_Fo/s1600-h/IMG_6500.JPG"&gt;&lt;img style="margin: 0pt 10px 10px 0pt; float: left; cursor: pointer; width: 112px; height: 200px;" src="http://1.bp.blogspot.com/_bkNp6hieiJM/SgoJoTxXBYI/AAAAAAAAALU/ctOYXynp_Fo/s200/IMG_6500.JPG" alt="" id="BLOGGER_PHOTO_ID_5335087296680494466" border="0" /&gt;&lt;/a&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://2.bp.blogspot.com/_bkNp6hieiJM/SgoJoPFRrgI/AAAAAAAAALM/nOvO9wEUIDw/s1600-h/JQR+Spain+217.jpg"&gt;&lt;img style="margin: 0pt 10px 10px 0pt; float: left; cursor: pointer; width: 150px; height: 200px;" src="http://2.bp.blogspot.com/_bkNp6hieiJM/SgoJoPFRrgI/AAAAAAAAALM/nOvO9wEUIDw/s200/JQR+Spain+217.jpg" alt="" id="BLOGGER_PHOTO_ID_5335087295421853186" border="0" /&gt;&lt;/a&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://3.bp.blogspot.com/_bkNp6hieiJM/SgoJoJIeJhI/AAAAAAAAALE/D8CBJ0ECiA8/s1600-h/IMG_6750.JPG"&gt;&lt;img style="margin: 0pt 10px 10px 0pt; float: left; cursor: pointer; width: 112px; height: 200px;" src="http://3.bp.blogspot.com/_bkNp6hieiJM/SgoJoJIeJhI/AAAAAAAAALE/D8CBJ0ECiA8/s200/IMG_6750.JPG" alt="" id="BLOGGER_PHOTO_ID_5335087293824640530" border="0" /&gt;&lt;/a&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://4.bp.blogspot.com/_bkNp6hieiJM/SgoJnwhIS3I/AAAAAAAAAK8/oKiHjG_F96U/s1600-h/IMG_6884.JPG"&gt;&lt;img style="margin: 0pt 10px 10px 0pt; float: left; cursor: pointer; width: 128px; height: 200px;" src="http://4.bp.blogspot.com/_bkNp6hieiJM/SgoJnwhIS3I/AAAAAAAAAK8/oKiHjG_F96U/s200/IMG_6884.JPG" alt="" id="BLOGGER_PHOTO_ID_5335087287217179506" border="0" /&gt;&lt;/a&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://1.bp.blogspot.com/_bkNp6hieiJM/SgoJn4GhwiI/AAAAAAAAAK0/apZ9n6cky2A/s1600-h/IMG_6689.JPG"&gt;&lt;img style="margin: 0pt 10px 10px 0pt; float: left; cursor: pointer; width: 148px; height: 200px;" src="http://1.bp.blogspot.com/_bkNp6hieiJM/SgoJn4GhwiI/AAAAAAAAAK0/apZ9n6cky2A/s200/IMG_6689.JPG" alt="" id="BLOGGER_PHOTO_ID_5335087289253085730" border="0" /&gt;&lt;/a&gt;&lt;div class="blogger-post-footer"&gt;Copyright Albert R. Russell 2009&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6436196782988005609-8012017616506319045?l=architecturalinsight.blogspot.com' alt='' /&gt;&lt;/div&gt;</description><link>http://architecturalinsight.blogspot.com/2009/05/doors-and-doorways-spain.html</link><author>noreply@blogger.com (Albert R. Russell, AIA)</author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://1.bp.blogspot.com/_bkNp6hieiJM/SgoJoTxXBYI/AAAAAAAAALU/ctOYXynp_Fo/s72-c/IMG_6500.JPG" height="72" width="72" /><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-6436196782988005609.post-6122004429468794939</guid><pubDate>Sun, 10 May 2009 12:53:00 +0000</pubDate><atom:updated>2009-05-10T09:48:40.307-04:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Construction Administration</category><category domain="http://www.blogger.com/atom/ns#">Project Management</category><category domain="http://www.blogger.com/atom/ns#">Gosh Darnit</category><title>Dutchmen for a technical ground grid</title><description>&lt;span style="font-size:100%;"&gt;&lt;span style="font-family:arial;"&gt;Our fast-track, high-tech building project was nearly complete. The tenant's expensive computer equipment was rolling in, and the sophisticated equipment power system was being tested. Then the electrical contractor reported a problem. The technical ground grid did not test out as required. All the components were in place, but there was a widespread loss in the system. Investigation isolated the loss to the computer room raised floor system in nearly every room of the building. The grid of the raised floor system was an intended major component of the technical grounding system. Computer equipment would be grounded to the floor grid, and an electrical grounding conductor tied each room's floor grid to the technical ground rod system outside the building. Through further investigation, the contractor found that the perimeter of the raised floor system was in contact with drywall screws at the floor line, providing unplanned continuity between the raised floor system and the metal stud partition framing throughout the building. It seemed like a monumental problem, and the team had almost no time to correct it before the tenant's scheduled start-up date. An eleventh hour brainstorming session turned up a solution worth trying. Small pieces of thin plastic laminate were installed in one room to separate the raised floor perimeter frame from the drywall screws. The fix proved effective, so the plastic laminate "band-aids" were used throughout the building, and the tenant's start-up occurred on schedule. &lt;/span&gt;&lt;/span&gt;&lt;div class="blogger-post-footer"&gt;Copyright Albert R. Russell 2009&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6436196782988005609-6122004429468794939?l=architecturalinsight.blogspot.com' alt='' /&gt;&lt;/div&gt;</description><link>http://architecturalinsight.blogspot.com/2009/05/dutchmen-all-around.html</link><author>noreply@blogger.com (Albert R. Russell, AIA)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-6436196782988005609.post-5512199654465363633</guid><pubDate>Fri, 08 May 2009 16:02:00 +0000</pubDate><atom:updated>2009-05-09T12:54:47.812-04:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Construction Administration</category><category domain="http://www.blogger.com/atom/ns#">Project Management</category><title>The Architect's role at the construction site</title><description>&lt;span style="font-size:100%;"&gt;&lt;span style="font-family: arial;"&gt;As construction began on a building, the architect's field representative was approached by the electrical subcontractor. The subcontractor wanted the architect's approval to install all distribution conduit at a specific level and prior to construction of interior partitions and mechanical distribution systems. It sounded like a great idea, a really clean and efficient installation for the electrical subcontractor that also appeared to offer post-construction advantages for the owner. However, it did not consider other construction and schedule needs. Had the architect given the nod to the electrical subcontractor, it would have interfered with the general contractor's responsibility and authority for scheduling and coordinating the work of the subcontractors, and it would have interfered directly with the work of other sub-trades. Further, the owner had no interest in the advantages proposed by the electrical subcontractor. At best, it was a good idea for some other project.&lt;br /&gt;&lt;br /&gt;&lt;/span&gt;&lt;/span&gt;&lt;span style="font-family: arial;font-size:100%;" &gt;An architect visiting a construction site can feel a rush of power as construction personnel approach with questions. "Finally," you may hear them exclaim, "someone with answers!" This is an opportunity to show your knowledge of construction, the project, and the construction documents, and it is also an opportunity to make a complete fool of yourself. You have to be careful to stay within the limits of your contractual role*, which is normally to observe construction for consistency with the construction documents and to communicate with the contractor's superintendent. This can be challenging when workers are gushing with excitement to hear your opinion about what should or could be done. A question may be valid and may warrant a prompt response, but the architect's reply should be consistent with the requirements of the construction documents, and it should be made through proper channels. You have to observe construction, but you should do what you can to avoid a claim or the appearance that you personally directed a worker or subcontractor to make a change.&lt;/span&gt;&lt;span style="font-size:100%;"&gt;&lt;span style="font-family: arial;"&gt; One subcontractor can sound very convincing when presenting a question or a dilemma, but there may be other factors, interests, and requirements to consider.&lt;br /&gt;&lt;br /&gt;[*The architect's contractual role during construction is typically established by the General Conditions of the Contract such as AIA Document A-201 or by similar documents and/or amendments thereto.]&lt;br /&gt;&lt;/span&gt;&lt;/span&gt;&lt;div class="blogger-post-footer"&gt;Copyright Albert R. Russell 2009&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6436196782988005609-5512199654465363633?l=architecturalinsight.blogspot.com' alt='' /&gt;&lt;/div&gt;</description><link>http://architecturalinsight.blogspot.com/2009/05/architects-role-at-construction-site.html</link><author>noreply@blogger.com (Albert R. Russell, AIA)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-6436196782988005609.post-5470588072709510082</guid><pubDate>Thu, 07 May 2009 14:04:00 +0000</pubDate><atom:updated>2009-07-18T21:50:05.800-04:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Construction Administration</category><category domain="http://www.blogger.com/atom/ns#">Specifications</category><category domain="http://www.blogger.com/atom/ns#">Masonry</category><category domain="http://www.blogger.com/atom/ns#">Design</category><title>Masonry Design: Not-Quite-Through-Wall Flashing</title><description>&lt;span style="font-size:100%;"&gt;&lt;span style="font-family:arial;"&gt;Through-wall flashing is a common water management feature of masonry cavity wall and veneer construction. It is most effective if its outer edge is beyond the outer face of the wall and is turned down to form a drip edge and help water fall away from the joint under the flashing.  It can be ineffective and result in leaks into a building if the outer edge of the flashing is concealed within the wall. In at least one case, a leak was attributed to flashing that stopped above the core holes of extruded brick. The design relied on the through-wall flashing to protect the building interior, but water which was intended to be conveyed out of the wall by the through-wall flashing was instead allowed to re-enter the wall and subsequently find its way to the building interior. Apparently, someone did not want to see the edge of the flashing coming out through the wall. At the time of construction it was common for the flashing to be coated with asphalt, and the asphalt coating - not especially attractive in any case - would melt under sunlight and over time it would drip and stain the face of the wall below. More attractive materials are widely used today, including drip edges of proprietary compositions or even stainless steel. The more attractive materials are likely to be more expensive. However, stopping the flashing within the wall may be the most expensive option of all, considering the possible costs of leak remediation.&lt;/span&gt;&lt;/span&gt;&lt;div class="blogger-post-footer"&gt;Copyright Albert R. Russell 2009&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6436196782988005609-5470588072709510082?l=architecturalinsight.blogspot.com' alt='' /&gt;&lt;/div&gt;</description><link>http://architecturalinsight.blogspot.com/2009/05/not-quite-through-wall-flashing.html</link><author>noreply@blogger.com (Albert R. Russell, AIA)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-6436196782988005609.post-8031461507073898575</guid><pubDate>Wed, 06 May 2009 17:40:00 +0000</pubDate><atom:updated>2009-07-18T21:40:24.148-04:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Construction Administration</category><category domain="http://www.blogger.com/atom/ns#">Project Administration</category><category domain="http://www.blogger.com/atom/ns#">Project Management</category><title>Change Order Process Diagrams</title><description>&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://2.bp.blogspot.com/_bkNp6hieiJM/SgHMsvwsyRI/AAAAAAAAAKs/d7oECgMNkDs/s1600-h/Simplified+CO+Flowchart.jpg"&gt;&lt;img style="margin: 0pt 10px 10px 0pt; float: left; cursor: pointer; width: 400px; height: 236px;" src="http://2.bp.blogspot.com/_bkNp6hieiJM/SgHMsvwsyRI/AAAAAAAAAKs/d7oECgMNkDs/s400/Simplified+CO+Flowchart.jpg" alt="" id="BLOGGER_PHOTO_ID_5332768502890416402" border="0" /&gt;&lt;/a&gt;&lt;span style="font-family:arial;"&gt;Comment on this post to request a pdf copy of these process diagrams.&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://3.bp.blogspot.com/_bkNp6hieiJM/SgHMrxeoIxI/AAAAAAAAAKk/cZUHNMrTaHo/s1600-h/Copy+of+RFI,+Change+Process.jpg"&gt;&lt;img style="margin: 0pt 10px 10px 0pt; float: left; cursor: pointer; width: 356px; height: 400px;" src="http://3.bp.blogspot.com/_bkNp6hieiJM/SgHMrxeoIxI/AAAAAAAAAKk/cZUHNMrTaHo/s400/Copy+of+RFI,+Change+Process.jpg" alt="" id="BLOGGER_PHOTO_ID_5332768486171616018" border="0" /&gt;&lt;/a&gt;&lt;div class="blogger-post-footer"&gt;Copyright Albert R. Russell 2009&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6436196782988005609-8031461507073898575?l=architecturalinsight.blogspot.com' alt='' /&gt;&lt;/div&gt;</description><link>http://architecturalinsight.blogspot.com/2009/05/rfi-and-change-order-process-diagrams.html</link><author>noreply@blogger.com (Albert R. Russell, AIA)</author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://2.bp.blogspot.com/_bkNp6hieiJM/SgHMsvwsyRI/AAAAAAAAAKs/d7oECgMNkDs/s72-c/Simplified+CO+Flowchart.jpg" height="72" width="72" /><thr:total>1</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-6436196782988005609.post-4969305048923432169</guid><pubDate>Wed, 06 May 2009 12:42:00 +0000</pubDate><atom:updated>2009-05-06T21:51:05.786-04:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Construction Administration</category><category domain="http://www.blogger.com/atom/ns#">Project Administration</category><category domain="http://www.blogger.com/atom/ns#">Practice Management</category><category domain="http://www.blogger.com/atom/ns#">Project Management</category><category domain="http://www.blogger.com/atom/ns#">Design</category><title>Email is Snail Mail for some</title><description>&lt;span style=";font-family:arial;font-size:100%;"  &gt;We all have our preferred means of communication, and we are inclined in this digital age to think that faster is better. But, in some situations, exclusive use of lightning speed technology may actually delay communication. The growing popularity of email years ago gave rise to the derogatory term "snail mail" to describe older and slower postal service or even "express" systems for delivery of hard copy mail.&lt;br /&gt;&lt;br /&gt;But, for some, "snail mail" still beats email. In one situation an executive who touts his company's use of computer based technology remains reluctant to make personal use of it. Sending this CEO an email message actually guarantees as much as a 2-week communication delay. His orders to his assistant - who actually receives his email - is to print it all out once every two weeks and put it into his in-box in a neat stack. He may then read it along with letters, magazines, advertisements, and other mail.&lt;br /&gt;&lt;br /&gt;This may seem like an extreme case these days, but it illustrates the importance (and advantage) of utilizing several means of communication to deliver a message. Don't forget face to face conversation, the telephone, the postage stamp, arm waving, signing, the bullhorn, and other potentially effective ways to deliver a message.&lt;/span&gt;&lt;span style="font-family:arial;"&gt; (See also &lt;/span&gt;&lt;a style="font-family: arial;" href="http://architecturalinsight.blogspot.com/2009/03/hand-off.html"&gt;Practice the Hand-off&lt;/a&gt;&lt;span style="font-family:arial;"&gt;.)&lt;/span&gt;&lt;div class="blogger-post-footer"&gt;Copyright Albert R. Russell 2009&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6436196782988005609-4969305048923432169?l=architecturalinsight.blogspot.com' alt='' /&gt;&lt;/div&gt;</description><link>http://architecturalinsight.blogspot.com/2009/05/email-is-snail-mail-for-some.html</link><author>noreply@blogger.com (Albert R. Russell, AIA)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-6436196782988005609.post-4620326276348060294</guid><pubDate>Tue, 05 May 2009 13:18:00 +0000</pubDate><atom:updated>2009-05-05T11:42:31.295-04:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Practice Management</category><category domain="http://www.blogger.com/atom/ns#">Design</category><title>Can you recognize a flat tire?</title><description>&lt;span style="font-size:100%;"&gt;&lt;span style="font-family:arial;"&gt;One architect, when interviewing prospective employees, would typically say, "You may have to mow the lawn sometimes." There wasn't much lawn to mow around that office, but the statement was an effective way of saying that we all have to pay attention to practical matters, and that may mean doing a few things that are not on your personal career agenda. In the midst of rapidly advancing technologies, practical awareness and practical skills continue to be important and useful.&lt;/span&gt;&lt;span style="font-family:arial;"&gt;&lt;br /&gt;&lt;br /&gt;Specialization and automation risk some loss of practical awareness. As we come to rely more on technology and automatic systems, we can lose our internal ability to recognize a problem. The recent addition of a tire pressure monitoring system (TPMS) as a feature on automobiles exemplifies such a risk. While TPMS may signal a loss of tire pressure that is not obvious to an observer, the presence of TPMS is likely to lull a driver into thinking that it is not necessary to consider the condition of the tires before traveling. Then, if the TPMS malfunctions and does not signal the driver of a loss of tire pressure, there is a risk that the driver will continue to operate a car with an under-inflated or flat tire, possibly damaging or destroying the tire...or worse. "Hey! The TPMS didn't tell me there was a problem!" With or without TPMS, a driver needs to recognize the symptoms of a low or flat tire and to react appropriately. One of the long term effects of systems like TPMS may be TLOA (total lack of awareness).&lt;br /&gt;&lt;br /&gt;&lt;/span&gt;&lt;/span&gt;&lt;span style="font-size:100%;"&gt;&lt;span style="font-family:arial;"&gt;GPS, spell-checker, and CAD (see &lt;/span&gt;&lt;/span&gt;&lt;a href="http://architecturalinsight.blogspot.com/2009/04/cad-doesnt-care.html"&gt;CAD doesn't care&lt;/a&gt;&lt;span style="font-size:100%;"&gt;&lt;span style="font-family:arial;"&gt;) are &lt;/span&gt;&lt;/span&gt;&lt;span style="font-size:100%;"&gt;&lt;span style="font-family:arial;"&gt;other examples of helpful technologies that may, as a side effect, reduce our internal awareness of problems&lt;/span&gt;&lt;/span&gt;&lt;span style="font-size:100%;"&gt;&lt;span style="font-family:arial;"&gt;. In a similar way, BIM (Building Information Modeling) offers the promise of more ways to consider a building project in its formative stages, but it will still fall to the operator or viewer to recognize a problem that needs to be corrected (see &lt;/span&gt;&lt;/span&gt;&lt;a href="http://architecturalinsight.blogspot.com/2009/03/whats-wrong-with-this-picture.html"&gt;What's wrong with this picture?&lt;/a&gt;&lt;span style="font-size:100%;"&gt;&lt;span style="font-family:arial;"&gt;).&lt;/span&gt;&lt;/span&gt;&lt;div class="blogger-post-footer"&gt;Copyright Albert R. Russell 2009&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6436196782988005609-4620326276348060294?l=architecturalinsight.blogspot.com' alt='' /&gt;&lt;/div&gt;</description><link>http://architecturalinsight.blogspot.com/2009/05/can-you-recognize-flat-tire.html</link><author>noreply@blogger.com (Albert R. Russell, AIA)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-6436196782988005609.post-2513459208581764670</guid><pubDate>Thu, 30 Apr 2009 15:36:00 +0000</pubDate><atom:updated>2009-07-18T21:48:56.686-04:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Construction Administration</category><category domain="http://www.blogger.com/atom/ns#">Specifications</category><category domain="http://www.blogger.com/atom/ns#">Roofing</category><category domain="http://www.blogger.com/atom/ns#">Project Management</category><title>Metal Roofing Specifications: "No Visible Oil Canning" equals Mission Impossible.</title><description>&lt;span style="font-family:arial;"&gt;On my first visit to the job site after the roofing contractor had started installing standing seam metal roofing, the Clerk called me aside and said, "I think we've got oil canning."&lt;br /&gt;&lt;br /&gt;I looked at the newly installed metal. It looked fine.&lt;br /&gt;&lt;br /&gt;"Wait a while", he said. As the sky changed and the angle of the sunlight changed during the day, oil canning appeared, then disappeared, then reappeared differently. "The specs say 'no visible oil canning'," the Clerk accurately noted.&lt;br /&gt;&lt;br /&gt;The spec writer's best intentions, possibly influenced by the designer's best intentions, were that from Day One and under any and all light conditions the metal roofing would exhibit no visible distortion. Seeing the situation in the field, a part of my mental faculties that were still intact suggested we had a problem that was more perceived than real. Over the next few days I visited and photographed a number of other projects with metal roofing - from afar, up close, and under different light conditions. These appeared to be carefully crafted installations with little or no distortion related to the installation. Yet under some light conditions and viewing angles, they all exhibited 'visible oil canning'. I put the findings into a little presentation for the client, who had been alerted to the oil canning condition by the Clerk. Following the presentation, the client was satisfied that the metal roofing was normal in terms of visible oil canning. The spec writer? Well, that's another story.&lt;br /&gt;&lt;br /&gt;(Visit http://www.smacna.org for an October 2005 newsletter article on oil canning and information about how to minimize it.)&lt;/span&gt;&lt;div class="blogger-post-footer"&gt;Copyright Albert R. Russell 2009&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6436196782988005609-2513459208581764670?l=architecturalinsight.blogspot.com' alt='' /&gt;&lt;/div&gt;</description><link>http://architecturalinsight.blogspot.com/2009/04/mission-impossible-no-visible-oil.html</link><author>noreply@blogger.com (Albert R. Russell, AIA)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-6436196782988005609.post-4620371453446222547</guid><pubDate>Thu, 30 Apr 2009 14:33:00 +0000</pubDate><atom:updated>2009-07-18T21:43:13.464-04:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Concrete</category><category domain="http://www.blogger.com/atom/ns#">Codes</category><category domain="http://www.blogger.com/atom/ns#">Design</category><title>Construction Tolerance</title><description>&lt;span style="font-family:arial;"&gt;Where codes or regulations establish minimum or maximum values and allow no tolerance outside the limit, industry standard construction tolerance should be incorporated into the design. For example, concrete ramps that must comply with "zero tolerance" maximum slope requirements for wheelchair accessibility should be designed at less than the maximum slope, such that allowable construction tolerance for concrete surfaces will not result in a slope that exceeds the maximum for wheelchair accessibility. If the maximum slope for wheelchair accessibility is 1:12, a design slope of 1:13 (or 0.95:12) may provide sufficient tolerance for construction to meet the slope regulations.&lt;/span&gt;&lt;div class="blogger-post-footer"&gt;Copyright Albert R. Russell 2009&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6436196782988005609-4620371453446222547?l=architecturalinsight.blogspot.com' alt='' /&gt;&lt;/div&gt;</description><link>http://architecturalinsight.blogspot.com/2009/04/tolerance.html</link><author>noreply@blogger.com (Albert R. Russell, AIA)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-6436196782988005609.post-1877025641331579313</guid><pubDate>Wed, 29 Apr 2009 20:01:00 +0000</pubDate><atom:updated>2009-07-18T21:45:37.307-04:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Masonry</category><category domain="http://www.blogger.com/atom/ns#">Design</category><title>Masonry Design: Separate hung masonry from foundation-supported masonry</title><description>&lt;span style="font-family:arial;"&gt;When drawing up elevations for masonry walls, in addition to locating control joints (arguably "expansion joints") to accommodate expansion and contraction related to temperature and moisture, it is important to consider how masonry supported on lintels hung directly from deflecting structural steel will move differently from masonry that is supported directly by the building foundation. While "loose" lintels supporting masonry over openings usually rest on foundation-supported masonry at the ends of the spanned opening, hung lintels should be isolated from foundation-supported masonry in a way that allows for independent vertical movement related to deflection of structural steel. If the hung lintel overlaps the foundation-supported masonry, a soft joint similar to that below a relieving angle may be appropriate below the end of the hung lintel. And the control joint above the lintel should also be located to allow for independent movement of the two masonry conditions. Determining the location of the ends of the hung lintel is important for construction that will properly respect the different needs of the two conditions. It gets more complicated for hung lintel assemblies suspended from beams that are interrupted by columns. In any case, careful consideration should be given to the locations of control joints within the wall area that is supported by the hung lintels.&lt;br /&gt;&lt;br /&gt;In some cases the best control joint locations for wall performance will not be the best locations for aesthetic intent. But, then, cracks are not usually attractive in appearance.&lt;/span&gt;&lt;div class="blogger-post-footer"&gt;Copyright Albert R. Russell 2009&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6436196782988005609-1877025641331579313?l=architecturalinsight.blogspot.com' alt='' /&gt;&lt;/div&gt;</description><link>http://architecturalinsight.blogspot.com/2009/04/separate-hung-masonry-from-foundation.html</link><author>noreply@blogger.com (Albert R. Russell, AIA)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-6436196782988005609.post-4623056047080315012</guid><pubDate>Wed, 29 Apr 2009 15:18:00 +0000</pubDate><atom:updated>2009-07-18T21:51:13.315-04:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Roofing</category><category domain="http://www.blogger.com/atom/ns#">Design</category><category domain="http://www.blogger.com/atom/ns#">Gosh Darnit</category><title>Roof Drainage Design: Foresight or Afterthought?</title><description>&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://2.bp.blogspot.com/_bkNp6hieiJM/Sfh0DTH6bBI/AAAAAAAAAJ4/CIQbsEzM3CM/s1600-h/Copy+of+IMG_6464.JPG"&gt;&lt;img style="margin: 0pt 10px 10px 0pt; float: left; cursor: pointer; width: 193px; height: 200px;" src="http://2.bp.blogspot.com/_bkNp6hieiJM/Sfh0DTH6bBI/AAAAAAAAAJ4/CIQbsEzM3CM/s200/Copy+of+IMG_6464.JPG" alt="" id="BLOGGER_PHOTO_ID_5330137759014874130" border="0" /&gt;&lt;/a&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://3.bp.blogspot.com/_bkNp6hieiJM/Sfh0DaQzh0I/AAAAAAAAAJw/yL5fvOsOfK8/s1600-h/Copy+of+2009+04+04+North+Easton+015.jpg"&gt;&lt;img style="margin: 0pt 10px 10px 0pt; float: left; cursor: pointer; width: 200px; height: 144px;" src="http://3.bp.blogspot.com/_bkNp6hieiJM/Sfh0DaQzh0I/AAAAAAAAAJw/yL5fvOsOfK8/s200/Copy+of+2009+04+04+North+Easton+015.jpg" alt="" id="BLOGGER_PHOTO_ID_5330137760931219266" border="0" /&gt;&lt;/a&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://4.bp.blogspot.com/_bkNp6hieiJM/Sfh0DCKx9tI/AAAAAAAAAJo/8o3C6u1ShRc/s1600-h/JQR+Spain+2+062.jpg"&gt;&lt;img style="margin: 0pt 10px 10px 0pt; float: left; cursor: pointer; width: 200px; height: 150px;" src="http://4.bp.blogspot.com/_bkNp6hieiJM/Sfh0DCKx9tI/AAAAAAAAAJo/8o3C6u1ShRc/s200/JQR+Spain+2+062.jpg" alt="" id="BLOGGER_PHOTO_ID_5330137754463499986" border="0" /&gt;&lt;/a&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://4.bp.blogspot.com/_bkNp6hieiJM/Sfh0C8tChdI/AAAAAAAAAJg/4VNy4rTrcVA/s1600-h/IMG_3807.JPG"&gt;&lt;img style="margin: 0pt 10px 10px 0pt; float: left; cursor: pointer; width: 200px; height: 104px;" src="http://4.bp.blogspot.com/_bkNp6hieiJM/Sfh0C8tChdI/AAAAAAAAAJg/4VNy4rTrcVA/s200/IMG_3807.JPG" alt="" id="BLOGGER_PHOTO_ID_5330137752996578770" border="0" /&gt;&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;span style="font-style: italic;font-size:130%;" &gt;&lt;span style="font-family:arial;"&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;If we could just get it a little further away or get it to go over there, everything would be okay.&lt;/span&gt;&lt;/span&gt;&lt;div class="blogger-post-footer"&gt;Copyright Albert R. Russell 2009&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6436196782988005609-4623056047080315012?l=architecturalinsight.blogspot.com' alt='' /&gt;&lt;/div&gt;</description><link>http://architecturalinsight.blogspot.com/2009/04/foresight-or-afterthought.html</link><author>noreply@blogger.com (Albert R. Russell, AIA)</author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://2.bp.blogspot.com/_bkNp6hieiJM/Sfh0DTH6bBI/AAAAAAAAAJ4/CIQbsEzM3CM/s72-c/Copy+of+IMG_6464.JPG" height="72" width="72" /><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-6436196782988005609.post-996093628578511727</guid><pubDate>Sat, 25 Apr 2009 13:59:00 +0000</pubDate><atom:updated>2009-04-28T15:33:48.928-04:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Project Management</category><title>Purposeful chaos (the 2-minute design offense)</title><description>&lt;span style=";font-family:arial;font-size:100%;"  &gt;While throwing staff at a project at the last minute is likely to be counterproductive (see &lt;/span&gt;&lt;a style="font-family: arial;" href="http://architecturalinsight.blogspot.com/2009/04/staffing-design-project.html"&gt;Staffing a design project&lt;/a&gt;&lt;span style=";font-family:arial;font-size:100%;"  &gt;), an imminent project deadline can ignite productive and purposeful chaos that is otherwise hard to generate. Consider the possible accomplishments of the "2-minute offense" or "no huddle offense" that are so well known and widely used during the last minutes of a football game. A scripted sequence of plays may produce effective results in a short time. Deadlines and completion milestones are important for efficiency, because work tends to fill the time available, and it will likely take more hours (and therefore cost more for labor) to do a task without an imminent deadline. Interim or "partial completion" deadlines with well-defined scopes of work and timely, attentive reviews can be helpful in keeping a project on schedule and also on target in terms of design intent. Architecture is like other work when it comes to efficient production. &lt;/span&gt;&lt;span style=";font-family:arial;font-size:100%;"  &gt;&lt;br /&gt;&lt;br /&gt;Mike (see &lt;/span&gt;&lt;a style="font-family: arial;" href="http://architecturalinsight.blogspot.com/2009/03/paint-color-chip.html"&gt;Paint the Color Chip&lt;/a&gt;&lt;span style=";font-family:arial;font-size:100%;"  &gt; and &lt;/span&gt;&lt;a style="font-family: arial;" href="http://architecturalinsight.blogspot.com/2009/03/mikes-abridged-edition.html"&gt;Mike's Abridged Edition&lt;/a&gt;&lt;span style=";font-family:arial;font-size:100%;"  &gt;) offered another idea for managing labor costs on a design project. "If you know you are going to have to work overtime on a project," he said, "do it in the beginning. It costs less to do overtime when there are only one or two people working on a project."&lt;/span&gt;&lt;div class="blogger-post-footer"&gt;Copyright Albert R. Russell 2009&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6436196782988005609-996093628578511727?l=architecturalinsight.blogspot.com' alt='' /&gt;&lt;/div&gt;</description><link>http://architecturalinsight.blogspot.com/2009/04/purposeful-chaos-2-minute-design.html</link><author>noreply@blogger.com (Albert R. Russell, AIA)</author><thr:total>0</thr:total></item></channel></rss>

