<?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: COTS Thoughts</title>
	<atom:link href="http://selenianboondocks.com/2009/02/cots-thoughts/feed/" rel="self" type="application/rss+xml" />
	<link>http://selenianboondocks.com/2009/02/cots-thoughts/</link>
	<description>Random Musings from the Warped Minds of Jonathan Goff, Ken Murphy, John Hare, and Kirk Sorensen</description>
	<lastBuildDate>Sat, 05 May 2012 20:53:30 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: How to Improve COTS &#171; The Four Part Land</title>
		<link>http://selenianboondocks.com/2009/02/cots-thoughts/comment-page-1/#comment-4415</link>
		<dc:creator>How to Improve COTS &#171; The Four Part Land</dc:creator>
		<pubDate>Fri, 06 Mar 2009 16:09:09 +0000</pubDate>
		<guid isPermaLink="false">http://selenianboondocks.com/?p=917#comment-4415</guid>
		<description>[...] How to Improve&#160;COTS  Selenian Boondocks » Blog Archive » COTS Thoughts [...]</description>
		<content:encoded><![CDATA[<p>[...] How to Improve&nbsp;COTS  Selenian Boondocks » Blog Archive » COTS Thoughts [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jonathan Goff</title>
		<link>http://selenianboondocks.com/2009/02/cots-thoughts/comment-page-1/#comment-4402</link>
		<dc:creator>Jonathan Goff</dc:creator>
		<pubDate>Fri, 27 Feb 2009 16:08:41 +0000</pubDate>
		<guid isPermaLink="false">http://selenianboondocks.com/?p=917#comment-4402</guid>
		<description>Steve,
Having hardware-based milestones doesn&#039;t necessarily imply having no milestones for a long time and then a big rush at the end.  Especially if you don&#039;t have an Elon Musk funding you, you &lt;i&gt;have&lt;/i&gt; to find a way to spread the milestones out more evenly.  I think this can be done, it just requires a more incremental development process than the &quot;we&#039;ll design everything, review everything, then build everything, and then we&#039;ll demonstrate how smart we are&quot; approach that NASA prefers...

~Jon</description>
		<content:encoded><![CDATA[<p>Steve,<br />
Having hardware-based milestones doesn&#8217;t necessarily imply having no milestones for a long time and then a big rush at the end.  Especially if you don&#8217;t have an Elon Musk funding you, you <i>have</i> to find a way to spread the milestones out more evenly.  I think this can be done, it just requires a more incremental development process than the &#8220;we&#8217;ll design everything, review everything, then build everything, and then we&#8217;ll demonstrate how smart we are&#8221; approach that NASA prefers&#8230;</p>
<p>~Jon</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steve Allen</title>
		<link>http://selenianboondocks.com/2009/02/cots-thoughts/comment-page-1/#comment-4401</link>
		<dc:creator>Steve Allen</dc:creator>
		<pubDate>Fri, 27 Feb 2009 12:08:14 +0000</pubDate>
		<guid isPermaLink="false">http://selenianboondocks.com/?p=917#comment-4401</guid>
		<description>I think that one reason for the watering down is that NASA staff in are focussed primarily on spending their budget, and hopefully increasing it in the following years. 
High-risk and long term COTS contracts represent a lot of personal career risk for such individuals working in NASA. What happens if SpaceX negotiates a true (un-watered down) COTS contract, spends a couple of years developing paper designs and technologies, then changes their mind and pulls out, not pursuing the expensive and difficult developments parts of the contract. Would this not lead to a mad rush where NASA tries to spend this budget somewhere else, quite possibily in a non-COTS program, managed by a competiting bureaucrat in NASA?</description>
		<content:encoded><![CDATA[<p>I think that one reason for the watering down is that NASA staff in are focussed primarily on spending their budget, and hopefully increasing it in the following years.<br />
High-risk and long term COTS contracts represent a lot of personal career risk for such individuals working in NASA. What happens if SpaceX negotiates a true (un-watered down) COTS contract, spends a couple of years developing paper designs and technologies, then changes their mind and pulls out, not pursuing the expensive and difficult developments parts of the contract. Would this not lead to a mad rush where NASA tries to spend this budget somewhere else, quite possibily in a non-COTS program, managed by a competiting bureaucrat in NASA?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: What&#8217;s Working - and Not Working - in NASA&#8217;s COTS Program at Parabolic Arc</title>
		<link>http://selenianboondocks.com/2009/02/cots-thoughts/comment-page-1/#comment-4399</link>
		<dc:creator>What&#8217;s Working - and Not Working - in NASA&#8217;s COTS Program at Parabolic Arc</dc:creator>
		<pubDate>Fri, 27 Feb 2009 00:29:20 +0000</pubDate>
		<guid isPermaLink="false">http://selenianboondocks.com/?p=917#comment-4399</guid>
		<description>[...] post is rather lengthy and nuanced, so it&#8217;s difficult to summarize. I personally think we [...]</description>
		<content:encoded><![CDATA[<p>[...] post is rather lengthy and nuanced, so it&#8217;s difficult to summarize. I personally think we [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jonathan Goff</title>
		<link>http://selenianboondocks.com/2009/02/cots-thoughts/comment-page-1/#comment-4398</link>
		<dc:creator>Jonathan Goff</dc:creator>
		<pubDate>Thu, 26 Feb 2009 20:29:05 +0000</pubDate>
		<guid isPermaLink="false">http://selenianboondocks.com/?p=917#comment-4398</guid>
		<description>Vladislaw,

1. Not sure how much would be needed, but somewhere in the $500M-1B range should get you enough to fund at least 2 main efforts, and maybe one or two backup study efforts (in case one of the main efforts hits snags early on).  Might be doable with less, but I&#039;m not really sure.

2. I&#039;d like to see two or three primary ones, and maybe some small ~$10-20M secondary ones (especially if the secondary ones have some high-risk/high-payoff approaches they would be maturing as part of that $10-20M).  But at least two teams.  This is higher risk, and part of the way of mitigating that risk is by having redundancy.  And unlike the &quot;cargo to space station&quot; market, the people to orbit market has a lot more potential room for growth.  Bigelow for instance would really like to have two options, and quite frankly I think NASA ought to as well.   That way, if a) something goes wrong with one supplier&#039;s launch vehicle or capsule, there&#039;s still at least one backup that can be leaned on while the problem is getting sorted out, b) it&#039;s much easier to on-ramp new providers.  If you&#039;re already buying services from two providers, it&#039;s much easier to bring on a third if they&#039;re better than it is if you have a sole-provider.

3. Making the rules/incentives such that it doesn&#039;t disincentivize using existing launch vehicles would be a good idea.  Just making a crew capsule that can fly on an existing LV is a lot lower risk than building a whole new launch system.  But we shouldn&#039;t bias it away from innovative approaches either.  If someone wants to propose a small 2-person RLV, they should still have a fair shot at it.

~Jon</description>
		<content:encoded><![CDATA[<p>Vladislaw,</p>
<p>1. Not sure how much would be needed, but somewhere in the $500M-1B range should get you enough to fund at least 2 main efforts, and maybe one or two backup study efforts (in case one of the main efforts hits snags early on).  Might be doable with less, but I&#8217;m not really sure.</p>
<p>2. I&#8217;d like to see two or three primary ones, and maybe some small ~$10-20M secondary ones (especially if the secondary ones have some high-risk/high-payoff approaches they would be maturing as part of that $10-20M).  But at least two teams.  This is higher risk, and part of the way of mitigating that risk is by having redundancy.  And unlike the &#8220;cargo to space station&#8221; market, the people to orbit market has a lot more potential room for growth.  Bigelow for instance would really like to have two options, and quite frankly I think NASA ought to as well.   That way, if a) something goes wrong with one supplier&#8217;s launch vehicle or capsule, there&#8217;s still at least one backup that can be leaned on while the problem is getting sorted out, b) it&#8217;s much easier to on-ramp new providers.  If you&#8217;re already buying services from two providers, it&#8217;s much easier to bring on a third if they&#8217;re better than it is if you have a sole-provider.</p>
<p>3. Making the rules/incentives such that it doesn&#8217;t disincentivize using existing launch vehicles would be a good idea.  Just making a crew capsule that can fly on an existing LV is a lot lower risk than building a whole new launch system.  But we shouldn&#8217;t bias it away from innovative approaches either.  If someone wants to propose a small 2-person RLV, they should still have a fair shot at it.</p>
<p>~Jon</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Vladislaw</title>
		<link>http://selenianboondocks.com/2009/02/cots-thoughts/comment-page-1/#comment-4397</link>
		<dc:creator>Vladislaw</dc:creator>
		<pubDate>Thu, 26 Feb 2009 20:06:07 +0000</pubDate>
		<guid isPermaLink="false">http://selenianboondocks.com/?p=917#comment-4397</guid>
		<description>Jon, 

For a fully funded COTS-D program, what kind of numbers do you think would be needed?

How many teams would you believe would be needed to make it competitive? Personally I would like to see a bigger field of companies and more ideas then just one or two.

Should COTS-D allow someone to just design the crew capsule and buy and off the shelf launcher, like building a capsule then using  the Falcon 9?</description>
		<content:encoded><![CDATA[<p>Jon, </p>
<p>For a fully funded COTS-D program, what kind of numbers do you think would be needed?</p>
<p>How many teams would you believe would be needed to make it competitive? Personally I would like to see a bigger field of companies and more ideas then just one or two.</p>
<p>Should COTS-D allow someone to just design the crew capsule and buy and off the shelf launcher, like building a capsule then using  the Falcon 9?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bob Steinke</title>
		<link>http://selenianboondocks.com/2009/02/cots-thoughts/comment-page-1/#comment-4394</link>
		<dc:creator>Bob Steinke</dc:creator>
		<pubDate>Wed, 25 Feb 2009 16:16:14 +0000</pubDate>
		<guid isPermaLink="false">http://selenianboondocks.com/?p=917#comment-4394</guid>
		<description>I think the main point of #2 was that skin-in-the-game requirements need to be well matched to the risk-adjusted net present value of potential revenue sources.  If the contract payment for reaching the hard technical milestone is enough to pay for the technical development all by itself then there&#039;s no conflict between #2 and #3.

It&#039;s only when you expect companies to pay for part of the development by raising money based on potential revenue from other markets, and those markets are insufficient, that you crowd new players out of the competition.  And that&#039;s true whether the milestones are hard or soft.</description>
		<content:encoded><![CDATA[<p>I think the main point of #2 was that skin-in-the-game requirements need to be well matched to the risk-adjusted net present value of potential revenue sources.  If the contract payment for reaching the hard technical milestone is enough to pay for the technical development all by itself then there&#8217;s no conflict between #2 and #3.</p>
<p>It&#8217;s only when you expect companies to pay for part of the development by raising money based on potential revenue from other markets, and those markets are insufficient, that you crowd new players out of the competition.  And that&#8217;s true whether the milestones are hard or soft.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rick Boozer</title>
		<link>http://selenianboondocks.com/2009/02/cots-thoughts/comment-page-1/#comment-4393</link>
		<dc:creator>Rick Boozer</dc:creator>
		<pubDate>Wed, 25 Feb 2009 16:14:48 +0000</pubDate>
		<guid isPermaLink="false">http://selenianboondocks.com/?p=917#comment-4393</guid>
		<description>Jon,
Your points all make sense to me.  What I want to know now is:
1) How do we go about getting these ideas to the right people in government who can make a difference?
2) How do we go about convincing said government officials of the validity of these concepts against the entrenched influence of NASA vested interests?</description>
		<content:encoded><![CDATA[<p>Jon,<br />
Your points all make sense to me.  What I want to know now is:<br />
1) How do we go about getting these ideas to the right people in government who can make a difference?<br />
2) How do we go about convincing said government officials of the validity of these concepts against the entrenched influence of NASA vested interests?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jonathan Goff</title>
		<link>http://selenianboondocks.com/2009/02/cots-thoughts/comment-page-1/#comment-4392</link>
		<dc:creator>Jonathan Goff</dc:creator>
		<pubDate>Wed, 25 Feb 2009 15:17:14 +0000</pubDate>
		<guid isPermaLink="false">http://selenianboondocks.com/?p=917#comment-4392</guid>
		<description>Eric,
Oh, I agree that paying only on technical milestones (after a first kickoff payment to &quot;prime the pump&quot;) does put some sort of skin-in-the-game requirements.  The difference is that you&#039;re raising much smaller chunks of money, and instead of raising it to meet some currently unproven market, you&#039;re raising it to make it to the next milestone of a firmly negotiated contract.  It&#039;s a lot easier to get a &quot;line of credit&quot; setup to help keep cash reserves while carrying out a government or commercial contract than it is to raise enough equity to do a full development program on speculation.

I wasn&#039;t saying skin-in-the-game was entirely evil, I was just pointing out that it was taken overboard in a dangerous way.

~Jon</description>
		<content:encoded><![CDATA[<p>Eric,<br />
Oh, I agree that paying only on technical milestones (after a first kickoff payment to &#8220;prime the pump&#8221;) does put some sort of skin-in-the-game requirements.  The difference is that you&#8217;re raising much smaller chunks of money, and instead of raising it to meet some currently unproven market, you&#8217;re raising it to make it to the next milestone of a firmly negotiated contract.  It&#8217;s a lot easier to get a &#8220;line of credit&#8221; setup to help keep cash reserves while carrying out a government or commercial contract than it is to raise enough equity to do a full development program on speculation.</p>
<p>I wasn&#8217;t saying skin-in-the-game was entirely evil, I was just pointing out that it was taken overboard in a dangerous way.</p>
<p>~Jon</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric Collins</title>
		<link>http://selenianboondocks.com/2009/02/cots-thoughts/comment-page-1/#comment-4390</link>
		<dc:creator>Eric Collins</dc:creator>
		<pubDate>Wed, 25 Feb 2009 12:11:56 +0000</pubDate>
		<guid isPermaLink="false">http://selenianboondocks.com/?p=917#comment-4390</guid>
		<description>In a way, your comments on #2 and #3 seem a little at odds.  First you say that the &quot;skin in the game&quot; provision kept out a number of competitors because they couldn&#039;t raise sufficient private capital, but then you also claim that NASA shouldn&#039;t even give up it&#039;s matching funds until the company has achieved nearly all of it&#039;s design, review, development, and manufacturing milestones.  How exactly does this latter situation encourage more companies to take on the risk of developing new systems, especially if many of them can&#039;t even raise enough money up front to match NASA&#039;s eventual contribution?</description>
		<content:encoded><![CDATA[<p>In a way, your comments on #2 and #3 seem a little at odds.  First you say that the &#8220;skin in the game&#8221; provision kept out a number of competitors because they couldn&#8217;t raise sufficient private capital, but then you also claim that NASA shouldn&#8217;t even give up it&#8217;s matching funds until the company has achieved nearly all of it&#8217;s design, review, development, and manufacturing milestones.  How exactly does this latter situation encourage more companies to take on the risk of developing new systems, especially if many of them can&#8217;t even raise enough money up front to match NASA&#8217;s eventual contribution?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

