<?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: FLASH: NO Tanker RFP Til Next Admin</title>
	<atom:link href="http://defensetech.org/2008/09/10/flash-no-tanker-rfp-til-next-admin/feed/" rel="self" type="application/rss+xml" />
	<link>http://defensetech.org/2008/09/10/flash-no-tanker-rfp-til-next-admin/</link>
	<description>The Future of the Military, Law Enforcement and National Security</description>
	<lastBuildDate>Fri, 25 May 2012 23:07:16 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: angel</title>
		<link>http://defensetech.org/2008/09/10/flash-no-tanker-rfp-til-next-admin/#comment-184811</link>
		<dc:creator>angel</dc:creator>
		<pubDate>Wed, 22 Oct 2008 01:28:30 +0000</pubDate>
		<guid isPermaLink="false">http://deftech.usmilblog.com/?p=4064#comment-184811</guid>
		<description>That&#039;s OK!But take a closer look following link,It&#039;s great to DVD and PSP converter for mac!
DVD Ripper for Mac,
Mac DVD Ripper Suite,
Mac DVD Converter Ultimate Suite,
Mac DVD Copy,
Mac DVD Creator,
Mac DVD to iPod Converter,
Mac DVD to iPhone Converter,
Mac DVD to MP4 Converter,
Mac DVD to Apple TV Converter,
Mac DVD to PSP Converter,
Mac DVD to BlackBerry Converter,
Mac DVD Audio Ripper,
Edit DVD,
Vob Converter for Mac,
VOB to iPod Converter for Mac,
VOB to Apple TV Converter for Mac,
VOB to PSP Converter for Mac,
VOB to MPEG4 Converter for Mac,
VOB to M4V Converter for Mac,
VOB to 3GP Converter for Mac,
VOB to MPG Converter for Mac,
VOB to AVI Converter for Mac
</description>
		<content:encoded><![CDATA[<p>That’s OK!But take a closer look following link,It’s great to DVD and PSP converter for mac!<br />
DVD Ripper for Mac,<br />
Mac DVD Ripper Suite,<br />
Mac DVD Converter Ultimate Suite,<br />
Mac DVD Copy,<br />
Mac DVD Creator,<br />
Mac DVD to iPod Converter,<br />
Mac DVD to iPhone Converter,<br />
Mac DVD to MP4 Converter,<br />
Mac DVD to Apple TV Converter,<br />
Mac DVD to PSP Converter,<br />
Mac DVD to BlackBerry Converter,<br />
Mac DVD Audio Ripper,<br />
Edit DVD,<br />
Vob Converter for Mac,<br />
VOB to iPod Converter for Mac,<br />
VOB to Apple TV Converter for Mac,<br />
VOB to PSP Converter for Mac,<br />
VOB to MPEG4 Converter for Mac,<br />
VOB to M4V Converter for Mac,<br />
VOB to 3GP Converter for Mac,<br />
VOB to MPG Converter for Mac,<br />
VOB to AVI Converter for Mac</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: pfcem</title>
		<link>http://defensetech.org/2008/09/10/flash-no-tanker-rfp-til-next-admin/#comment-184809</link>
		<dc:creator>pfcem</dc:creator>
		<pubDate>Sat, 13 Sep 2008 02:28:33 +0000</pubDate>
		<guid isPermaLink="false">http://deftech.usmilblog.com/?p=4064#comment-184809</guid>
		<description>SMSgt Mac,
Thanks once again for proving my point correct.
</description>
		<content:encoded><![CDATA[<p>SMSgt Mac,<br />
Thanks once again for proving my point correct.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: pfcem</title>
		<link>http://defensetech.org/2008/09/10/flash-no-tanker-rfp-til-next-admin/#comment-184807</link>
		<dc:creator>pfcem</dc:creator>
		<pubDate>Fri, 12 Sep 2008 04:00:56 +0000</pubDate>
		<guid isPermaLink="false">http://deftech.usmilblog.com/?p=4064#comment-184807</guid>
		<description>SMSgt Mac,
As usuall you are FOS. Deliberately misrepresenting the facts &amp; blaiming Boeing for everything that went wrong.
What &quot;caused&quot; the &#039;highly charged&#039; environment was Congress in its infinate wisdome (not) thinking it could fix the problems that occured during the tanker lease program by FORCING the USAF to conduct a &quot;full &amp; thorough competition&quot; under INTENSE Congressional &amp; DOD oversight when the USAF had already rejected the the A330 platform for not meeting its needs, being too risky, too expensive &amp; TOO BIG.  Everything which transpired was a direct result of that boneheaded act &amp; Boeing not bending over backwards to take the blaim &amp; be penalized more than it already had for the mistakes of the USAF &amp; the DOD.
The USAF then had the uneviable job of conducting a soliciation (under INTENSE Congressional &amp; DOD oversight) in which both Boeing &amp; EADS (partnered with NG) would compete.  The NG/EADS team took full advantage of the DEMAND for a competition &amp; knowing that it could not win under the criteria the USAF established got the criteria changed to accomodate their otherwise noncompetative KC-30, then threatened to pull its bid unless &quot;further elaboration&quot; was made.
It wasn&#039;t bad enough that the KC-X source selection team (NOT the USAF) did not assess the relative merits of the proposals in accordance with the evaluation criteria identified in the solicitation in selecting the KC-30, conducted misleading and unequal discussions with Boeing, et cetera but &quot;leaked&quot; that it was not even close.  Then it delayed a week before debriefing Boeing on &quot;why&quot; the KC-30 had been selected &amp; in that breifing it became clear.  Boeing protested the selection of the KC-30 sighting prejudicial errors made by the KC-X source selection team.  In one of, if not THE harshest rulings anyone can remember the GAO sustained the protest.  The result being such a loss of confidence in the USAF that its selection authority was taken away &amp; given directly to the ONE man who was responsible for ensuring that what did happen did not happen...
What about all the changes made to &amp; from the previous RFPs without significant technical or user need rationale to support them?
</description>
		<content:encoded><![CDATA[<p>SMSgt Mac,<br />
As usuall you are FOS. Deliberately misrepresenting the facts &amp; blaiming Boeing for everything that went wrong.<br />
What “caused” the ‘highly charged’ environment was Congress in its infinate wisdome (not) thinking it could fix the problems that occured during the tanker lease program by FORCING the USAF to conduct a “full &amp; thorough competition” under INTENSE Congressional &amp; DOD oversight when the USAF had already rejected the the A330 platform for not meeting its needs, being too risky, too expensive &amp; TOO BIG.  Everything which transpired was a direct result of that boneheaded act &amp; Boeing not bending over backwards to take the blaim &amp; be penalized more than it already had for the mistakes of the USAF &amp; the DOD.<br />
The USAF then had the uneviable job of conducting a soliciation (under INTENSE Congressional &amp; DOD oversight) in which both Boeing &amp; EADS (partnered with NG) would compete.  The NG/EADS team took full advantage of the DEMAND for a competition &amp; knowing that it could not win under the criteria the USAF established got the criteria changed to accomodate their otherwise noncompetative KC-30, then threatened to pull its bid unless “further elaboration” was made.<br />
It wasn’t bad enough that the KC-X source selection team (NOT the USAF) did not assess the relative merits of the proposals in accordance with the evaluation criteria identified in the solicitation in selecting the KC-30, conducted misleading and unequal discussions with Boeing, et cetera but “leaked” that it was not even close.  Then it delayed a week before debriefing Boeing on “why” the KC-30 had been selected &amp; in that breifing it became clear.  Boeing protested the selection of the KC-30 sighting prejudicial errors made by the KC-X source selection team.  In one of, if not THE harshest rulings anyone can remember the GAO sustained the protest.  The result being such a loss of confidence in the USAF that its selection authority was taken away &amp; given directly to the ONE man who was responsible for ensuring that what did happen did not happen…<br />
What about all the changes made to &amp; from the previous RFPs without significant technical or user need rationale to support them?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: SMSgt Mac</title>
		<link>http://defensetech.org/2008/09/10/flash-no-tanker-rfp-til-next-admin/#comment-184806</link>
		<dc:creator>SMSgt Mac</dc:creator>
		<pubDate>Thu, 11 Sep 2008 03:08:19 +0000</pubDate>
		<guid isPermaLink="false">http://deftech.usmilblog.com/?p=4064#comment-184806</guid>
		<description>You don&#039;t even have to read between the lines: just read to the end of the lines. The key point in today&#039;s announcement concerning the inability to proceed is the point that the contract is trying to go forward &quot;in this highly charged environment&quot;.
So dear fellows, we must ask ourselves what made it a &#039;highly charged&#039; environment? You can look at anything that transpired on the government side after the issuance of the final RFP and you won&#039;t find anything to &#039;highly charge&#039; the situation. You can go down the litany of missteps the aquisition folks are alleged to have stumbled through and you won&#039;t find anything that caused things to be &#039;highly charged&#039;. Similarly the mere filing of a protest by Boeing wouldn&#039;t have neccessarily &#039;highly charge&#039; anything.
No, I submit the only thing that pulled the trigger that &#039;highly charged&#039; the situation was the manner in which Boeing pursued its protest, and how Boeing brought the full weight of their political machine to bear from day one. (The speed at which Boeing moved in this direction still suggests premeditation to me: perhaps a plan B alternative for them as early as when they first  anticipated or understood the essence of the final RFP.)
As to whether this is merely more political cowardice on the part of the DoD or not, I will await the next RFP before passing judgement. If there are certain changes made from the previous one without significant technical or user need rationale to support them, we will KNOW that Boeing will have cowed the DoD and successfully subjugated the entire acquisition system just to ensure the taxpayers will keep subsidizing their business case.
The possibility of good coming from this is extremely remote.
</description>
		<content:encoded><![CDATA[<p>You don’t even have to read between the lines: just read to the end of the lines. The key point in today’s announcement concerning the inability to proceed is the point that the contract is trying to go forward “in this highly charged environment”.<br />
So dear fellows, we must ask ourselves what made it a ‘highly charged’ environment? You can look at anything that transpired on the government side after the issuance of the final RFP and you won’t find anything to ‘highly charge’ the situation. You can go down the litany of missteps the aquisition folks are alleged to have stumbled through and you won’t find anything that caused things to be ‘highly charged’. Similarly the mere filing of a protest by Boeing wouldn’t have neccessarily ‘highly charge’ anything.<br />
No, I submit the only thing that pulled the trigger that ‘highly charged’ the situation was the manner in which Boeing pursued its protest, and how Boeing brought the full weight of their political machine to bear from day one. (The speed at which Boeing moved in this direction still suggests premeditation to me: perhaps a plan B alternative for them as early as when they first  anticipated or understood the essence of the final RFP.)<br />
As to whether this is merely more political cowardice on the part of the DoD or not, I will await the next RFP before passing judgement. If there are certain changes made from the previous one without significant technical or user need rationale to support them, we will KNOW that Boeing will have cowed the DoD and successfully subjugated the entire acquisition system just to ensure the taxpayers will keep subsidizing their business case.<br />
The possibility of good coming from this is extremely remote.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: George Hanshaw</title>
		<link>http://defensetech.org/2008/09/10/flash-no-tanker-rfp-til-next-admin/#comment-184805</link>
		<dc:creator>George Hanshaw</dc:creator>
		<pubDate>Thu, 11 Sep 2008 00:56:32 +0000</pubDate>
		<guid isPermaLink="false">http://deftech.usmilblog.com/?p=4064#comment-184805</guid>
		<description>The problem here is with DOD procurement:
1.  USAF procurement officer extorts retirement job from Boeing as a condition of doing business with them.
2.  USAF procurement people do &#039;bait and switch&#039; by using source selection criteria that were in direct conflict with RFP.
3.  DOD procurement tries to bluff their way past the reality that their changed RFP restarts the whole program.
Finally, even Gates saw the writing on the wall.  As a former USAF procurement offical I can tell you that DOD PROCUREMENT HAS NEVER PAID ANY ATTENTION TO PROCUREMENT LAW, buying off wronged contractors with future fat contracts so they didn&#039;t protest.
But when the USAF procurement official who was extorting a job from Boeing got caught and both she and Boeing were punished, the rules changed.  If the federal government is going to send people to jail for using the good old boy system, the contractors aren&#039;t going to use it, they are going to use their legal departments.
If DOD want procurement actions to go smoothly it&#039;s actually quite easy.  They can follow procurement law.  Only problem is they have very little experience in working that way.
</description>
		<content:encoded><![CDATA[<p>The problem here is with DOD procurement:<br />
1.  USAF procurement officer extorts retirement job from Boeing as a condition of doing business with them.<br />
2.  USAF procurement people do ‘bait and switch’ by using source selection criteria that were in direct conflict with RFP.<br />
3.  DOD procurement tries to bluff their way past the reality that their changed RFP restarts the whole program.<br />
Finally, even Gates saw the writing on the wall.  As a former USAF procurement offical I can tell you that DOD PROCUREMENT HAS NEVER PAID ANY ATTENTION TO PROCUREMENT LAW, buying off wronged contractors with future fat contracts so they didn’t protest.<br />
But when the USAF procurement official who was extorting a job from Boeing got caught and both she and Boeing were punished, the rules changed.  If the federal government is going to send people to jail for using the good old boy system, the contractors aren’t going to use it, they are going to use their legal departments.<br />
If DOD want procurement actions to go smoothly it’s actually quite easy.  They can follow procurement law.  Only problem is they have very little experience in working that way.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: reshtet</title>
		<link>http://defensetech.org/2008/09/10/flash-no-tanker-rfp-til-next-admin/#comment-184804</link>
		<dc:creator>reshtet</dc:creator>
		<pubDate>Thu, 11 Sep 2008 00:26:05 +0000</pubDate>
		<guid isPermaLink="false">http://deftech.usmilblog.com/?p=4064#comment-184804</guid>
		<description>Man,if they can&#039;t get a needed Tanker going what
lies are they covering up in Iraq/Afghan???? And the tan fill color is back,from a site I order music from???
</description>
		<content:encoded><![CDATA[<p>Man,if they can’t get a needed Tanker going what<br />
lies are they covering up in Iraq/Afghan???? And the tan fill color is back,from a site I order music from???</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Trent Telenko</title>
		<link>http://defensetech.org/2008/09/10/flash-no-tanker-rfp-til-next-admin/#comment-184803</link>
		<dc:creator>Trent Telenko</dc:creator>
		<pubDate>Wed, 10 Sep 2008 21:00:42 +0000</pubDate>
		<guid isPermaLink="false">http://deftech.usmilblog.com/?p=4064#comment-184803</guid>
		<description>&gt;Someone at the very highest levels should be
&gt;fired for allowing this whole debacle to get to
&gt;this point.
IIRC, the USAF CoS and Civilian Secretary were canned for a lot of reasons, some stated, most not.
This seems to have been one of the unstated ones.
</description>
		<content:encoded><![CDATA[<p>&gt;Someone at the very highest levels should be<br />
&gt;fired for allowing this whole debacle to get to<br />
&gt;this point.<br />
IIRC, the USAF CoS and Civilian Secretary were canned for a lot of reasons, some stated, most not.<br />
This seems to have been one of the unstated ones.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John</title>
		<link>http://defensetech.org/2008/09/10/flash-no-tanker-rfp-til-next-admin/#comment-184802</link>
		<dc:creator>John</dc:creator>
		<pubDate>Wed, 10 Sep 2008 20:59:12 +0000</pubDate>
		<guid isPermaLink="false">http://deftech.usmilblog.com/?p=4064#comment-184802</guid>
		<description>Same old  military procurement process, designed to be as expensive as humanly possible.
So what&#039;s the criteria now?  We just keep bidding until Boeing wins?
I hope whoever takes over the next administration fires every AF employee connected with this.  Then bans Boeing from bidding on govt work for a decade.
</description>
		<content:encoded><![CDATA[<p>Same old  military procurement process, designed to be as expensive as humanly possible.<br />
So what’s the criteria now?  We just keep bidding until Boeing wins?<br />
I hope whoever takes over the next administration fires every AF employee connected with this.  Then bans Boeing from bidding on govt work for a decade.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eduardo</title>
		<link>http://defensetech.org/2008/09/10/flash-no-tanker-rfp-til-next-admin/#comment-76130</link>
		<dc:creator>Eduardo</dc:creator>
		<pubDate>Wed, 10 Sep 2008 20:40:50 +0000</pubDate>
		<guid isPermaLink="false">http://deftech.usmilblog.com/?p=4064#comment-76130</guid>
		<description>Someone won this round. And it was not Northrop Grumman.
</description>
		<content:encoded><![CDATA[<p>Someone won this round. And it was not Northrop Grumman.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tartan69</title>
		<link>http://defensetech.org/2008/09/10/flash-no-tanker-rfp-til-next-admin/#comment-76129</link>
		<dc:creator>Tartan69</dc:creator>
		<pubDate>Wed, 10 Sep 2008 19:57:52 +0000</pubDate>
		<guid isPermaLink="false">http://deftech.usmilblog.com/?p=4064#comment-76129</guid>
		<description>Someone at the very highest levels should be fired for allowing this whole debacle to get to this point.
</description>
		<content:encoded><![CDATA[<p>Someone at the very highest levels should be fired for allowing this whole debacle to get to this point.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

