<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:sy="http://purl.org/rss/1.0/modules/syndication/" > <channel><title>Comments on: Badly Installed Sensor Shut F136</title> <atom:link href="http://www.dodbuzz.com/2009/09/04/badly-installed-sensor-shut-f-136/feed/" rel="self" type="application/rss+xml" /><link>http://www.dodbuzz.com/2009/09/04/badly-installed-sensor-shut-f-136/</link> <description>Online Defense and Acquisition Journal</description> <lastBuildDate>Thu, 09 Feb 2012 15:21:26 +0000</lastBuildDate> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <generator>http://wordpress.org/?v=3.3.1</generator> <item><title>By: DensityDuck</title><link>http://www.dodbuzz.com/2009/09/04/badly-installed-sensor-shut-f-136/#comment-13903</link> <dc:creator>DensityDuck</dc:creator> <pubDate>Tue, 08 Sep 2009 15:42:44 +0000</pubDate> <guid isPermaLink="false">http://www.dodbuzz.com/?p=9478#comment-13903</guid> <description>Also, hindsight is 20/20.  While the F136 hasn&#039;t seen any cost growth, is that because it was budgeted properly from the get-go?The article quotes a Pratt source describing percentage increases in &quot;engine procurement costs&quot;, but the source doesn&#039;t cite any actual figures.  I&#039;d also question the comparison of &quot;development costs&quot; to &quot;procurement costs&quot;, because the latter includes a lot of bureaucratic nincompoopery.For example, if the customer decides halfway through that they have a completely new risk-tracking software that they want to use, then the costs of switching over the entire book-keeping system go into &quot;procurement cost increase&quot;.  A new contractor who was told to use that software from the get-go wouldn&#039;t have to switch anything, resulting in a &quot;cost savings&quot; that&#039;s entirely on paper.</description> <content:encoded><![CDATA[<p>Also, hindsight is 20/20.  While the F136 hasn’t seen any cost growth, is that because it was budgeted properly from the get-go?</p><p>The article quotes a Pratt source describing percentage increases in “engine procurement costs”, but the source doesn’t cite any actual figures.  I’d also question the comparison of “development costs” to “procurement costs”, because the latter includes a lot of bureaucratic nincompoopery.</p><p>For example, if the customer decides halfway through that they have a completely new risk-tracking software that they want to use, then the costs of switching over the entire book-keeping system go into “procurement cost increase”.  A new contractor who was told to use that software from the get-go wouldn’t have to switch anything, resulting in a “cost savings” that’s entirely on paper.</p> ]]></content:encoded> </item> <item><title>By: ReconTeam</title><link>http://www.dodbuzz.com/2009/09/04/badly-installed-sensor-shut-f-136/#comment-13883</link> <dc:creator>ReconTeam</dc:creator> <pubDate>Mon, 07 Sep 2009 00:15:08 +0000</pubDate> <guid isPermaLink="false">http://www.dodbuzz.com/?p=9478#comment-13883</guid> <description>The F120 developed for the ATF program by GE was by most accounts an excellent engine even if it was thirstier than the P&amp;W F119. With such a basis, why is GE having so many complications with the F136?</description> <content:encoded><![CDATA[<p>The F120 developed for the ATF program by GE was by most accounts an excellent engine even if it was thirstier than the P&amp;W F119. With such a basis, why is GE having so many complications with the F136?</p> ]]></content:encoded> </item> <item><title>By: Colin Clark</title><link>http://www.dodbuzz.com/2009/09/04/badly-installed-sensor-shut-f-136/#comment-13859</link> <dc:creator>Colin Clark</dc:creator> <pubDate>Sat, 05 Sep 2009 01:11:16 +0000</pubDate> <guid isPermaLink="false">http://www.dodbuzz.com/?p=9478#comment-13859</guid> <description>irtusk,Thanks. Too many airplane stories... Fixed.</description> <content:encoded><![CDATA[<p>irtusk,</p><p>Thanks. Too many airplane stories… Fixed.</p> ]]></content:encoded> </item> <item><title>By: irtusk</title><link>http://www.dodbuzz.com/2009/09/04/badly-installed-sensor-shut-f-136/#comment-13857</link> <dc:creator>irtusk</dc:creator> <pubDate>Fri, 04 Sep 2009 22:23:49 +0000</pubDate> <guid isPermaLink="false">http://www.dodbuzz.com/?p=9478#comment-13857</guid> <description>F135 and F136 (no dashes)</description> <content:encoded><![CDATA[<p>F135 and F136 (no dashes)</p> ]]></content:encoded> </item> </channel> </rss>
<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Minified using apc
Page Caching using apc (User agent is rejected)
Database Caching 1/5 queries in 0.006 seconds using apc
Object Caching 640/641 objects using apc
Content Delivery Network via images.dodbuzz.com

Served from: dodbuzz.com @ 2012-02-09 10:32:24 -->
