<?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: Long-term planning</title>
	<atom:link href="http://www.spacepolitics.com/2007/11/29/long-term-planning/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.spacepolitics.com/2007/11/29/long-term-planning/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=long-term-planning</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: Space Politics &#187; Hutchison followup</title>
		<link>http://www.spacepolitics.com/2007/11/29/long-term-planning/#comment-29404</link>
		<dc:creator><![CDATA[Space Politics &#187; Hutchison followup]]></dc:creator>
		<pubDate>Tue, 04 Dec 2007 19:09:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.spacepolitics.com/2007/11/29/long-term-planning/#comment-29404</guid>
		<description><![CDATA[[...] follow up on a note last week about Sen. Kay Bailey Hutchison&#8217;s long-term plans, the newspaper The Politico reported today that Hutchison will not seek the No. 3 position among [...]]]></description>
		<content:encoded><![CDATA[<p>[&#8230;] follow up on a note last week about Sen. Kay Bailey Hutchison&#8217;s long-term plans, the newspaper The Politico reported today that Hutchison will not seek the No. 3 position among [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: itchy scratchy</title>
		<link>http://www.spacepolitics.com/2007/11/29/long-term-planning/#comment-29004</link>
		<dc:creator><![CDATA[itchy scratchy]]></dc:creator>
		<pubDate>Fri, 30 Nov 2007 16:38:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.spacepolitics.com/2007/11/29/long-term-planning/#comment-29004</guid>
		<description><![CDATA[&lt;i&gt;Ickâ€¦&lt;/i&gt;

Whatever you say. You can ban the messengers, but you can&#039;t ban the truth.

It&#039;s going to be some very expensive entertainment watching this drag on for yet another year, with two years of this nonsense already under our belts.

You are a latecomer to the party Miss Anonymous Space, and you are saying nothing that most of us haven&#039;t already known for over two full years here.]]></description>
		<content:encoded><![CDATA[<p><i>Ickâ€¦</i></p>
<p>Whatever you say. You can ban the messengers, but you can&#8217;t ban the truth.</p>
<p>It&#8217;s going to be some very expensive entertainment watching this drag on for yet another year, with two years of this nonsense already under our belts.</p>
<p>You are a latecomer to the party Miss Anonymous Space, and you are saying nothing that most of us haven&#8217;t already known for over two full years here.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: anonymous.space</title>
		<link>http://www.spacepolitics.com/2007/11/29/long-term-planning/#comment-29001</link>
		<dc:creator><![CDATA[anonymous.space]]></dc:creator>
		<pubDate>Fri, 30 Nov 2007 16:03:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.spacepolitics.com/2007/11/29/long-term-planning/#comment-29001</guid>
		<description><![CDATA[&quot;But it didnâ€™t boggle your mind much back in late September of 2005, did it.&quot;

I think you have me confused with a certain Mike Griffin.  Or one of the members of Congress that voted for the NASA authorization bill that was passed that month.

I hate to disappoint your delusions of my grandeur, but I&#039;m neither.

&quot;You really are a one trick pony. Well, better late than never, or so they say.&quot;

Just keep trolling and throwing those insults with provocation.  Eventually you&#039;ll forget your meds long enough to start with the epithets and get banned again.

Actually, maybe throwing insults at other posters without provocation is  enough to get banned again, especially for a repeat offender.

Tuning out of this conversation, too.

Ick...]]></description>
		<content:encoded><![CDATA[<p>&#8220;But it didnâ€™t boggle your mind much back in late September of 2005, did it.&#8221;</p>
<p>I think you have me confused with a certain Mike Griffin.  Or one of the members of Congress that voted for the NASA authorization bill that was passed that month.</p>
<p>I hate to disappoint your delusions of my grandeur, but I&#8217;m neither.</p>
<p>&#8220;You really are a one trick pony. Well, better late than never, or so they say.&#8221;</p>
<p>Just keep trolling and throwing those insults with provocation.  Eventually you&#8217;ll forget your meds long enough to start with the epithets and get banned again.</p>
<p>Actually, maybe throwing insults at other posters without provocation is  enough to get banned again, especially for a repeat offender.</p>
<p>Tuning out of this conversation, too.</p>
<p>Ick&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: thinking ahead</title>
		<link>http://www.spacepolitics.com/2007/11/29/long-term-planning/#comment-29000</link>
		<dc:creator><![CDATA[thinking ahead]]></dc:creator>
		<pubDate>Fri, 30 Nov 2007 15:49:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.spacepolitics.com/2007/11/29/long-term-planning/#comment-29000</guid>
		<description><![CDATA[&lt;i&gt;It boggles the mind that weâ€™re still chasing our tails on Ares I when the U.S. has working launch vehicles in that weight class in the existing fleet.&lt;/i&gt;

But it didn&#039;t boggle your mind much back in late September of 2005, did it.

You really are a one trick pony. Well, better late than never, or so they say.]]></description>
		<content:encoded><![CDATA[<p><i>It boggles the mind that weâ€™re still chasing our tails on Ares I when the U.S. has working launch vehicles in that weight class in the existing fleet.</i></p>
<p>But it didn&#8217;t boggle your mind much back in late September of 2005, did it.</p>
<p>You really are a one trick pony. Well, better late than never, or so they say.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: anonymous.space</title>
		<link>http://www.spacepolitics.com/2007/11/29/long-term-planning/#comment-28857</link>
		<dc:creator><![CDATA[anonymous.space]]></dc:creator>
		<pubDate>Thu, 29 Nov 2007 17:12:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.spacepolitics.com/2007/11/29/long-term-planning/#comment-28857</guid>
		<description><![CDATA[&quot;advocating either more taxpayer dollars for Ares I/Orion projects that are drowning in technical problems and slipping schedules&quot;

Just to follow up on this thought, GAO released a fairly damaging report on Ares I today (add http://):

democrats.science.house.gov/Media/File/Reports/Ares1_GAOrep_2007nov29.pdf

Among the observations:

&quot;NASA has not yet established firm requirements or developed mature technologies, a preliminary design, or realistic cost estimates, or determined the ultimate time and money needed to complete the program [Ares I] and so is not in a position to make informed investment decisions.&quot;

&quot;While NASA still has 10 months to close [the aforementioned] gaps in knowledge, it will be challenged to do so.&quot;

&quot;For the Ares I program, 14 of the projectâ€™s self-identified risk factors are tied to unstable requirementsâ€”many of which are interrelated between Ares I and Orion projects.&quot;

&quot;Both the Orion and Ares I vehicles have a history of weight and mass growth, and NASA is still defining the mass, loads, and weight requirements for both vehicles.&quot;

&quot;a design analysis cycle completed in May 2007 revealed an unexpected increase in ascent loads (the physical strain on the spacecraft during launch) that could result in increases to the weight of the Orion vehicle and both stages of the Ares I.&quot;

&quot;Requirements instability is also increasing risk for the individual elements of the Ares I.&quot;

&quot;NASA has not yet matured guidance, navigation, and control requirements for the upper stage subsystems. According to an agency official, these requirements cannot be finalized until mass, loads and weight requirements are finalized. Since these requirements are not expected to be provided until just 2 Â½ months prior to the upper stage preliminary design review process start, there is a possibility that the system requirements review design concepts will be highly affected once requirements are received.&quot;

&quot;Requirements instability also contributed to NASAâ€™s inability to definitize design, development, and test and evaluation contracts for both the first stage and upper stage engine until August and July 2007 respectivelyâ€”more than a year after the contracts were awarded.&quot;

&quot;Adding the fifth segment and the frustum has increased the length and flexibility of the reusable solid rocket booster. It is currently unclear how the modification will affect the flight characteristics of the reusable solid rocket booster. Failure to completely understand the flight characteristic of the modified booster could create a risk of hardware failure and loss of vehicle control.&quot;

&quot;there is also a possibility that the reusable solid rocket booster heritage hardware may not meet qualification requirements given the new ascent and re-entry loads and vibration and acoustic environments associated with the Ares I. This could result in cost and schedule impacts due to redesign and requalification efforts.&quot;

&quot;the added weight of the fifth segment to the boosters is forcing the contractor to push the state of the art in developing a parachute recovery system.&quot;

&quot;In January 2007, an independent review of the first stage development questioned the cost-effectiveness of continuing with a reusable booster design... NASA may need to consider expendable first stage options given the weight issues associated with both the Ares I and Orion vehicles. If NASA opts to pursue an expendable solution for the first stage, the overall Ares I design and requirements could change dramatically.&quot;

&quot;NASAâ€™s development effort for the Ares I upper stage has resulted in the redesign of its propellant tanks from two completely separate tanks to two tanks with one shared, or common, bulkhead. While the prior two-tank configuration was a simpler design with a lower manufacturing cost, it did not meet mass requirements. The current common bulkhead design involves a complex and problematic manufacturing process that plagued earlier development efforts on the Apollo program. In fact, IRMA indicates that one of the lessons learned from the Apollo program was to not use common bulkheads because they are complex and difficult to manufacture.&quot;

&quot;there is a possibility that upper stage subsystems will not meet the Constellation programâ€™s requirements for human rating unless the Constellation program grants waivers to failure tolerance requirements. NASAâ€™s human rating directive generally requires that human spaceflight hardware be â€œtwo-failure tolerant,â€ that is, the system should be designed to tolerate two component failures or inadvertent actions without resulting in permanent disability or loss of life. According to Ares I project officials, NASAâ€™s directive allows the use of ascent abort in response to a second failure during launch; however, Constellation program requirements do not allow abort and require Ares I to reach orbit even if there are two failures.&quot;

&quot;Although the J-2X is based on the J-2 and J-2S engines used on the Saturn V, and leverages knowledge from the X-33 and RS-68, the extent of planned changes is such that both the ESAS and Ares I standing review boards reported that the effort essentially represents a new engine development. The scope of required changes is so broad, the contractor estimates that it will need nearly 5 million hours to complete design, development, test, and evaluation activities for the J-2X upper stage engine... According to Pratt and Whitney Rocketdyne representatives, these design changes will result in the replacement and/or modification of virtually every part derived from the J-2 or J-2S designs.&quot;

&quot;Pratt and Whitney Rocketdyne is also redesigning turbo-pumps from the X-33 program that feed fuel and oxidizer into a newly configured main combustion chamber, to increase engine thrust to 294,000 poundsâ€”the J-2S had 265,000 pounds of thrust. The element also faces significant schedule risks in developing and manufacturing a carbon composite nozzle extension in order to satisfy these thrust requirements. According to contractor officials, the extension is more than 2 feetâ€”i.e., about one-thirdâ€”wider in diameter than existing nozzles.&quot;

&quot;the J-2X development effort is accorded less than 7 years from development start to first flight. In comparison, the Space Shuttle main engine, the only other human-rated liquid-fuel engine NASA has successfully flown since the Apollo program, development required 9 years... If the engine does not complete development as scheduled, subsequent flight testing might be delayed. The J-2X development effort represents a critical path for the Ares I project. Subsequently, delays in the J-2X schedule for design, development, test, and evaluation would have a ripple effect throughout the entire Ares I project.&quot;

These are the things that folks like Hutchison on NASA oversight committees should be paying attention to and forcing the agency to  find alternatives for.  It boggles the mind that we&#039;re still chasing our tails on Ares I when the U.S. has working launch vehicles in that weight class in the existing fleet.

FWIW...]]></description>
		<content:encoded><![CDATA[<p>&#8220;advocating either more taxpayer dollars for Ares I/Orion projects that are drowning in technical problems and slipping schedules&#8221;</p>
<p>Just to follow up on this thought, GAO released a fairly damaging report on Ares I today (add <a href="http://" rel="nofollow">http://</a>):</p>
<p>democrats.science.house.gov/Media/File/Reports/Ares1_GAOrep_2007nov29.pdf</p>
<p>Among the observations:</p>
<p>&#8220;NASA has not yet established firm requirements or developed mature technologies, a preliminary design, or realistic cost estimates, or determined the ultimate time and money needed to complete the program [Ares I] and so is not in a position to make informed investment decisions.&#8221;</p>
<p>&#8220;While NASA still has 10 months to close [the aforementioned] gaps in knowledge, it will be challenged to do so.&#8221;</p>
<p>&#8220;For the Ares I program, 14 of the projectâ€™s self-identified risk factors are tied to unstable requirementsâ€”many of which are interrelated between Ares I and Orion projects.&#8221;</p>
<p>&#8220;Both the Orion and Ares I vehicles have a history of weight and mass growth, and NASA is still defining the mass, loads, and weight requirements for both vehicles.&#8221;</p>
<p>&#8220;a design analysis cycle completed in May 2007 revealed an unexpected increase in ascent loads (the physical strain on the spacecraft during launch) that could result in increases to the weight of the Orion vehicle and both stages of the Ares I.&#8221;</p>
<p>&#8220;Requirements instability is also increasing risk for the individual elements of the Ares I.&#8221;</p>
<p>&#8220;NASA has not yet matured guidance, navigation, and control requirements for the upper stage subsystems. According to an agency official, these requirements cannot be finalized until mass, loads and weight requirements are finalized. Since these requirements are not expected to be provided until just 2 Â½ months prior to the upper stage preliminary design review process start, there is a possibility that the system requirements review design concepts will be highly affected once requirements are received.&#8221;</p>
<p>&#8220;Requirements instability also contributed to NASAâ€™s inability to definitize design, development, and test and evaluation contracts for both the first stage and upper stage engine until August and July 2007 respectivelyâ€”more than a year after the contracts were awarded.&#8221;</p>
<p>&#8220;Adding the fifth segment and the frustum has increased the length and flexibility of the reusable solid rocket booster. It is currently unclear how the modification will affect the flight characteristics of the reusable solid rocket booster. Failure to completely understand the flight characteristic of the modified booster could create a risk of hardware failure and loss of vehicle control.&#8221;</p>
<p>&#8220;there is also a possibility that the reusable solid rocket booster heritage hardware may not meet qualification requirements given the new ascent and re-entry loads and vibration and acoustic environments associated with the Ares I. This could result in cost and schedule impacts due to redesign and requalification efforts.&#8221;</p>
<p>&#8220;the added weight of the fifth segment to the boosters is forcing the contractor to push the state of the art in developing a parachute recovery system.&#8221;</p>
<p>&#8220;In January 2007, an independent review of the first stage development questioned the cost-effectiveness of continuing with a reusable booster design&#8230; NASA may need to consider expendable first stage options given the weight issues associated with both the Ares I and Orion vehicles. If NASA opts to pursue an expendable solution for the first stage, the overall Ares I design and requirements could change dramatically.&#8221;</p>
<p>&#8220;NASAâ€™s development effort for the Ares I upper stage has resulted in the redesign of its propellant tanks from two completely separate tanks to two tanks with one shared, or common, bulkhead. While the prior two-tank configuration was a simpler design with a lower manufacturing cost, it did not meet mass requirements. The current common bulkhead design involves a complex and problematic manufacturing process that plagued earlier development efforts on the Apollo program. In fact, IRMA indicates that one of the lessons learned from the Apollo program was to not use common bulkheads because they are complex and difficult to manufacture.&#8221;</p>
<p>&#8220;there is a possibility that upper stage subsystems will not meet the Constellation programâ€™s requirements for human rating unless the Constellation program grants waivers to failure tolerance requirements. NASAâ€™s human rating directive generally requires that human spaceflight hardware be â€œtwo-failure tolerant,â€ that is, the system should be designed to tolerate two component failures or inadvertent actions without resulting in permanent disability or loss of life. According to Ares I project officials, NASAâ€™s directive allows the use of ascent abort in response to a second failure during launch; however, Constellation program requirements do not allow abort and require Ares I to reach orbit even if there are two failures.&#8221;</p>
<p>&#8220;Although the J-2X is based on the J-2 and J-2S engines used on the Saturn V, and leverages knowledge from the X-33 and RS-68, the extent of planned changes is such that both the ESAS and Ares I standing review boards reported that the effort essentially represents a new engine development. The scope of required changes is so broad, the contractor estimates that it will need nearly 5 million hours to complete design, development, test, and evaluation activities for the J-2X upper stage engine&#8230; According to Pratt and Whitney Rocketdyne representatives, these design changes will result in the replacement and/or modification of virtually every part derived from the J-2 or J-2S designs.&#8221;</p>
<p>&#8220;Pratt and Whitney Rocketdyne is also redesigning turbo-pumps from the X-33 program that feed fuel and oxidizer into a newly configured main combustion chamber, to increase engine thrust to 294,000 poundsâ€”the J-2S had 265,000 pounds of thrust. The element also faces significant schedule risks in developing and manufacturing a carbon composite nozzle extension in order to satisfy these thrust requirements. According to contractor officials, the extension is more than 2 feetâ€”i.e., about one-thirdâ€”wider in diameter than existing nozzles.&#8221;</p>
<p>&#8220;the J-2X development effort is accorded less than 7 years from development start to first flight. In comparison, the Space Shuttle main engine, the only other human-rated liquid-fuel engine NASA has successfully flown since the Apollo program, development required 9 years&#8230; If the engine does not complete development as scheduled, subsequent flight testing might be delayed. The J-2X development effort represents a critical path for the Ares I project. Subsequently, delays in the J-2X schedule for design, development, test, and evaluation would have a ripple effect throughout the entire Ares I project.&#8221;</p>
<p>These are the things that folks like Hutchison on NASA oversight committees should be paying attention to and forcing the agency to  find alternatives for.  It boggles the mind that we&#8217;re still chasing our tails on Ares I when the U.S. has working launch vehicles in that weight class in the existing fleet.</p>
<p>FWIW&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Al Fansome</title>
		<link>http://www.spacepolitics.com/2007/11/29/long-term-planning/#comment-28853</link>
		<dc:creator><![CDATA[Al Fansome]]></dc:creator>
		<pubDate>Thu, 29 Nov 2007 16:24:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.spacepolitics.com/2007/11/29/long-term-planning/#comment-28853</guid>
		<description><![CDATA[Anon,

I agree.

My impression of Hutchison is that she is a light-weight, and mostly talk.  Which is the normal state of being for most Members of Congress.  I can&#039;t point to anything that demonstrates that she has been effective at producing results for Texas&#039; positions on space.

Texas at least has a chance to do better with a different person sitting in her seat.

- Al]]></description>
		<content:encoded><![CDATA[<p>Anon,</p>
<p>I agree.</p>
<p>My impression of Hutchison is that she is a light-weight, and mostly talk.  Which is the normal state of being for most Members of Congress.  I can&#8217;t point to anything that demonstrates that she has been effective at producing results for Texas&#8217; positions on space.</p>
<p>Texas at least has a chance to do better with a different person sitting in her seat.</p>
<p>&#8211; Al</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: anonymous.space</title>
		<link>http://www.spacepolitics.com/2007/11/29/long-term-planning/#comment-28845</link>
		<dc:creator><![CDATA[anonymous.space]]></dc:creator>
		<pubDate>Thu, 29 Nov 2007 15:08:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.spacepolitics.com/2007/11/29/long-term-planning/#comment-28845</guid>
		<description><![CDATA[I don&#039;t think much would change for NASA if Hutchison gave up her seat on NASA&#039;s oversight subcommittee in the Senate.  In fact, the agency might have a shot at getting a better, more effective advocate.

Even with the help of a powerful appropriator in Mikulski, Hutchison&#039;s support of a $1 billion increase for NASA has been wasted on an ineffectual, ill-conceived legislative effort for two years in a row now.  And Hutchison&#039;s own signature legislation to designate the ISS as a &quot;national lab&quot; has turned out to be little more than a name change, with no accompanying funding commitments from other federal research agencies and a thin, limp-wristed report that only promises to explore a few potential future agreements.  And Hutchison&#039;s strategy for addressing the gap is just plain unimaginative and wrong, advocating either more taxpayer dollars for Ares I/Orion projects that are drowning in technical problems and slipping schedules, or extending dangerous Shuttle operations that would only push out the gap and risk more astronaut lives.  Maybe someone else will remember something that I&#039;m forgetting, but I&#039;m at a loss to point to anything substantively positive that Hutchison has achieved for NASA.

No doubt Hutchison&#039;s seat would be filled by another Senator representing a NASA field center.  I don&#039;t know the likely candidates off hand, but NASA appears to have nothing to lose if Hutchison leaves, and might wind up better off with a different, more effective minority lead on that subcommittee.

FWIW...]]></description>
		<content:encoded><![CDATA[<p>I don&#8217;t think much would change for NASA if Hutchison gave up her seat on NASA&#8217;s oversight subcommittee in the Senate.  In fact, the agency might have a shot at getting a better, more effective advocate.</p>
<p>Even with the help of a powerful appropriator in Mikulski, Hutchison&#8217;s support of a $1 billion increase for NASA has been wasted on an ineffectual, ill-conceived legislative effort for two years in a row now.  And Hutchison&#8217;s own signature legislation to designate the ISS as a &#8220;national lab&#8221; has turned out to be little more than a name change, with no accompanying funding commitments from other federal research agencies and a thin, limp-wristed report that only promises to explore a few potential future agreements.  And Hutchison&#8217;s strategy for addressing the gap is just plain unimaginative and wrong, advocating either more taxpayer dollars for Ares I/Orion projects that are drowning in technical problems and slipping schedules, or extending dangerous Shuttle operations that would only push out the gap and risk more astronaut lives.  Maybe someone else will remember something that I&#8217;m forgetting, but I&#8217;m at a loss to point to anything substantively positive that Hutchison has achieved for NASA.</p>
<p>No doubt Hutchison&#8217;s seat would be filled by another Senator representing a NASA field center.  I don&#8217;t know the likely candidates off hand, but NASA appears to have nothing to lose if Hutchison leaves, and might wind up better off with a different, more effective minority lead on that subcommittee.</p>
<p>FWIW&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
