<?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: Huge Cost Overrun for AEHF</title> <atom:link href="http://www.dodbuzz.com/2008/09/08/huge-cost-overrun-for-aehf/feed/" rel="self" type="application/rss+xml" /><link>http://www.dodbuzz.com/2008/09/08/huge-cost-overrun-for-aehf/</link> <description>Online Defense and Acquisition Journal</description> <lastBuildDate>Thu, 09 Feb 2012 11:49:43 +0000</lastBuildDate> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <generator>http://wordpress.org/?v=3.3.1</generator> <item><title>By: Brownsugar</title><link>http://www.dodbuzz.com/2008/09/08/huge-cost-overrun-for-aehf/#comment-1446</link> <dc:creator>Brownsugar</dc:creator> <pubDate>Fri, 12 Sep 2008 13:13:40 +0000</pubDate> <guid isPermaLink="false">http://www.dodbuzz.com/?p=967#comment-1446</guid> <description>I have suggest for this problem, why not set a charge of 100.00 for each Frequency used?  This way frequencies would incorporated in estimates for each components that the Army uses.  (e,g Radio - 32000 freq)  This way the services have to add frequency charges to their estimates to cover any usages.  Also, this way to service pick-up the extra charges.</description> <content:encoded><![CDATA[<p>I have suggest for this problem, why not set a charge of 100.00 for each Frequency used?  This way frequencies would incorporated in estimates for each components that the Army uses.  (e,g Radio — 32000 freq)  This way the services have to add frequency charges to their estimates to cover any usages.  Also, this way to service pick-up the extra charges.</p> ]]></content:encoded> </item> <item><title>By: DensityDuck</title><link>http://www.dodbuzz.com/2008/09/08/huge-cost-overrun-for-aehf/#comment-1430</link> <dc:creator>DensityDuck</dc:creator> <pubDate>Thu, 11 Sep 2008 21:23:22 +0000</pubDate> <guid isPermaLink="false">http://www.dodbuzz.com/?p=967#comment-1430</guid> <description>Describing this as a &quot;cost overrun&quot; is not entirely correct, as the cost increase is due to the addition of a fourth satellite which wasn&#039;t in the original contract.Brownshoe: &quot;5. They (the contractors) don’t listen to the customers&quot;Oh, please.  If we didn&#039;t listen to the customers, then things would be LESS expensive, because we&#039;d build to the original contract!</description> <content:encoded><![CDATA[<p>Describing this as a “cost overrun” is not entirely correct, as the cost increase is due to the addition of a fourth satellite which wasn’t in the original contract.</p><p>Brownshoe: “5. They (the contractors) don’t listen to the customers”</p><p>Oh, please.  If we didn’t listen to the customers, then things would be LESS expensive, because we’d build to the original contract!</p> ]]></content:encoded> </item> <item><title>By: VAPOR_ONE_NINE</title><link>http://www.dodbuzz.com/2008/09/08/huge-cost-overrun-for-aehf/#comment-1410</link> <dc:creator>VAPOR_ONE_NINE</dc:creator> <pubDate>Thu, 11 Sep 2008 17:28:05 +0000</pubDate> <guid isPermaLink="false">http://www.dodbuzz.com/?p=967#comment-1410</guid> <description>LC, Agreed.  I found in my time with the A/F acquisition community that AFMC did a much better job.  Any time a major program was handled by the &quot;dreamers&quot; the requirements were way beyond what could be built economically.  Usually what they came up with was better handled through a technology demonstration program, not a full production effort.</description> <content:encoded><![CDATA[<p>LC,<br /> Agreed.  I found in my time with the A/F acquisition community that AFMC did a much better job.  Any time a major program was handled by the “dreamers” the requirements were way beyond what could be built economically.  Usually what they came up with was better handled through a technology demonstration program, not a full production effort.</p> ]]></content:encoded> </item> <item><title>By: LC</title><link>http://www.dodbuzz.com/2008/09/08/huge-cost-overrun-for-aehf/#comment-1357</link> <dc:creator>LC</dc:creator> <pubDate>Wed, 10 Sep 2008 02:21:57 +0000</pubDate> <guid isPermaLink="false">http://www.dodbuzz.com/?p=967#comment-1357</guid> <description>Space acquisition needs to be put back under AFMC and taken away from Space Command. There is zero reason why they should be following a different course.</description> <content:encoded><![CDATA[<p>Space acquisition needs to be put back under AFMC and taken away from Space Command. There is zero reason why they should be following a different course.</p> ]]></content:encoded> </item> <item><title>By: Brownshoe</title><link>http://www.dodbuzz.com/2008/09/08/huge-cost-overrun-for-aehf/#comment-1337</link> <dc:creator>Brownshoe</dc:creator> <pubDate>Tue, 09 Sep 2008 07:14:53 +0000</pubDate> <guid isPermaLink="false">http://www.dodbuzz.com/?p=967#comment-1337</guid> <description>This is a mistake that is is consistently repeated both on the government a commercial side.  I see it in my company, both on the commercial and military programs and especially on NASA programs.  As a project manager, I’ve done several post-mortem analyses on projects that were in trouble or failed outright. It boils down to a series of very basic issues.  The main reasons programs have cost overruns are:1. The broken practice of requiring cost estimates for new system before any of the systems engineering work is completed. 2. The cost estimation process itself is outdated and broken. 3. Lack of honest and aggressive risk management. 4. Not enough or any focus on process optimization such as lean, Six Sigma and Theory of Constraints. 5. They (the contractors) don’t listen to the customers 6. Unrealistic assertions of budget versus required capabilitiesWhen will we ever learn?  These are not new issues and to this day I am baffled as to why we still can’t get this done right.</description> <content:encoded><![CDATA[<p>This is a mistake that is is consistently repeated both on the government a commercial side.  I see it in my company, both on the commercial and military programs and especially on NASA programs.  As a project manager, I’ve done several post-mortem analyses on projects that were in trouble or failed outright. It boils down to a series of very basic issues.  The main reasons programs have cost overruns are:</p><p>1. The broken practice of requiring cost estimates for new system before any of the systems engineering work is completed.<br /> 2. The cost estimation process itself is outdated and broken.<br /> 3. Lack of honest and aggressive risk management.<br /> 4. Not enough or any focus on process optimization such as lean, Six Sigma and Theory of Constraints.<br /> 5. They (the contractors) don’t listen to the customers<br /> 6. Unrealistic assertions of budget versus required capabilities</p><p>When will we ever learn?  These are not new issues and to this day I am baffled as to why we still can’t get this done right.</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.004 seconds using apc
Object Caching 651/652 objects using apc
Content Delivery Network via images.dodbuzz.com

Served from: dodbuzz.com @ 2012-02-09 07:24:21 -->
