<?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: Just when you thought it was safe for milspace procurement</title>
	<atom:link href="http://www.spacepolitics.com/2007/10/02/just-when-you-thought-it-was-safe-for-milspace-procurement/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.spacepolitics.com/2007/10/02/just-when-you-thought-it-was-safe-for-milspace-procurement/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=just-when-you-thought-it-was-safe-for-milspace-procurement</link>
	<description>Because sometimes the most important orbit is the Beltway...</description>
	<lastBuildDate>Wed, 17 Sep 2014 13:35:41 +0000</lastBuildDate>
		<sy:updatePeriod>hourly</sy:updatePeriod>
		<sy:updateFrequency>1</sy:updateFrequency>
	<generator>https://wordpress.org/?v=4.0.38</generator>
	<item>
		<title>By: Bob Bokros</title>
		<link>http://www.spacepolitics.com/2007/10/02/just-when-you-thought-it-was-safe-for-milspace-procurement/#comment-46212</link>
		<dc:creator><![CDATA[Bob Bokros]]></dc:creator>
		<pubDate>Tue, 29 Apr 2008 20:06:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.spacepolitics.com/2007/10/02/just-when-you-thought-it-was-safe-for-milspace-procurement/#comment-46212</guid>
		<description><![CDATA[With increasing labor costs, here is a product that can reduce your maintenance costs and offer a safe alternative to out sourced scaffolding. 
it is used by EADS and NASA for satellite production.]]></description>
		<content:encoded><![CDATA[<p>With increasing labor costs, here is a product that can reduce your maintenance costs and offer a safe alternative to out sourced scaffolding.<br />
it is used by EADS and NASA for satellite production.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ray</title>
		<link>http://www.spacepolitics.com/2007/10/02/just-when-you-thought-it-was-safe-for-milspace-procurement/#comment-23429</link>
		<dc:creator><![CDATA[Ray]]></dc:creator>
		<pubDate>Thu, 04 Oct 2007 11:52:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.spacepolitics.com/2007/10/02/just-when-you-thought-it-was-safe-for-milspace-procurement/#comment-23429</guid>
		<description><![CDATA[I probably shouldn&#039;t bring NASA into this thread, but the first thing that strikes me is that there are a whole lot of things they could be doing, or doing more of, than they are to make it easier to get things like SBIRS done right, on time, and on budget.  Unfortunately building Ares I/V and Orion don&#039;t strike me as being useful in that regard - and they take up the funds that could be helping.  It would be nice if that ESAS stuff could be delayed until Shuttle retirement.  They could go ahead after Shuttle retirement, restricting themselves to Shuttle retirement funds, and pick a Shuttle-derived architecture do go to the Moon - or whatever.  For the Moon, they might have to make some decisions they&#039;re so against now - 2 crew instead of 4, commercial components in the architecture, international components in the architecture (mercy!  none of those!) ... but I think they&#039;d get it done anyway.  In fact I think they&#039;d have a better chance that way.  If not ... well, I&#039;d place my priorities on helping DOD, NOAA, etc ahead of the Moon program anyway.

In the meantime, they could be investing seriously in flying small suborbital missions with existing launchers, and giving incentives for new, cheap (and lower altitude) launchers to be offered.  This would give lots (I mean LOTS) of chances to fly small missions, which would give university students and new aerospace employees experience with the full mission cycle.  That&#039;s key to developing the engineering, systems engineering, and procurement expertise that allows bigger missions like SBIRS to succeed.

They could also be doing much more COTS to make sure cheaper launchers are developed that DOD could also benefit from.  In the meantime they could be using EELVs for satellites and probes - again helping DOD (and NOAA, even non-satellite agencies that need commercial satellite technology like FEMA, etc).

They could also be launching more satellites with payloads with communication and remote sensing instruments of the sort other agencies use - sharing costs with, or improving, the same satellite technologies that the DOD (and NOAA, etc) need.  If they emphasized smaller missions, they could give those industry systems engineers and procurement people another step in the ladder (after suborbital) to being able to handle the big &quot;life or death of the country&quot; missions like SBIRS.

I don&#039;t see much need at these other agencies with critical missions for Ares V ... DOD even got rid of Titan.  I don&#039;t see much need there for Orion either.]]></description>
		<content:encoded><![CDATA[<p>I probably shouldn&#8217;t bring NASA into this thread, but the first thing that strikes me is that there are a whole lot of things they could be doing, or doing more of, than they are to make it easier to get things like SBIRS done right, on time, and on budget.  Unfortunately building Ares I/V and Orion don&#8217;t strike me as being useful in that regard &#8211; and they take up the funds that could be helping.  It would be nice if that ESAS stuff could be delayed until Shuttle retirement.  They could go ahead after Shuttle retirement, restricting themselves to Shuttle retirement funds, and pick a Shuttle-derived architecture do go to the Moon &#8211; or whatever.  For the Moon, they might have to make some decisions they&#8217;re so against now &#8211; 2 crew instead of 4, commercial components in the architecture, international components in the architecture (mercy!  none of those!) &#8230; but I think they&#8217;d get it done anyway.  In fact I think they&#8217;d have a better chance that way.  If not &#8230; well, I&#8217;d place my priorities on helping DOD, NOAA, etc ahead of the Moon program anyway.</p>
<p>In the meantime, they could be investing seriously in flying small suborbital missions with existing launchers, and giving incentives for new, cheap (and lower altitude) launchers to be offered.  This would give lots (I mean LOTS) of chances to fly small missions, which would give university students and new aerospace employees experience with the full mission cycle.  That&#8217;s key to developing the engineering, systems engineering, and procurement expertise that allows bigger missions like SBIRS to succeed.</p>
<p>They could also be doing much more COTS to make sure cheaper launchers are developed that DOD could also benefit from.  In the meantime they could be using EELVs for satellites and probes &#8211; again helping DOD (and NOAA, even non-satellite agencies that need commercial satellite technology like FEMA, etc).</p>
<p>They could also be launching more satellites with payloads with communication and remote sensing instruments of the sort other agencies use &#8211; sharing costs with, or improving, the same satellite technologies that the DOD (and NOAA, etc) need.  If they emphasized smaller missions, they could give those industry systems engineers and procurement people another step in the ladder (after suborbital) to being able to handle the big &#8220;life or death of the country&#8221; missions like SBIRS.</p>
<p>I don&#8217;t see much need at these other agencies with critical missions for Ares V &#8230; DOD even got rid of Titan.  I don&#8217;t see much need there for Orion either.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
