<?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: Surface Warfare Still Searches for 21st Century Ideas</title>
	<atom:link href="http://blog.usni.org/2009/06/24/surface-warfare-still-searches-for-21st-century-ideas/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.usni.org/2009/06/24/surface-warfare-still-searches-for-21st-century-ideas/</link>
	<description>The Naval Institute’s taken its independent forum to a new level - with you in the middle of it.</description>
	<lastBuildDate>Sat, 11 Feb 2012 23:43:34 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: LCDR Luke Schmidt</title>
		<link>http://blog.usni.org/2009/06/24/surface-warfare-still-searches-for-21st-century-ideas/comment-page-4/#comment-244436</link>
		<dc:creator>LCDR Luke Schmidt</dc:creator>
		<pubDate>Sun, 14 Nov 2010 23:59:24 +0000</pubDate>
		<guid isPermaLink="false">http://blog.usni.org/?p=3434#comment-244436</guid>
		<description>Excellent data analysis, however your blog does not take into consideration future defense spending cutbacks, which are already being seen with the Secretary of Defense (SECDEF) proposing the closing of Joint Forces Command.  I understand your analysis was written before SECDEF warned all services to prepare for future cutbacks in defense spending.  With the budget in mind and only two surface combatant options, I think we will see many more LCS ships being built than DDGs.
	Agree that a FFG Service Life Extension Program (SLEP) would be a terrible option, despite any argument that the Florida congressional representatives can make in hopes of saving jobs in Mayport, FL.  As a former FFG Combat Systems Officer, I can assure you that the Oliver-Hazard Perry-Class frigate is an extremely outdated surface combatant with very limited and sometimes unreliable combat capability.  Additionally, the maintenance cost for an increased sustainment life would outweigh any possible benefit of maintaining these ships in the fleet.  We should be more concerned about having the right type of ships to meet the current and future mission demands and threats vice just trying to reach a 313-ship Navy on the books.
	I believe the current number of FFGs in USN service is 29.  I have not heard any plans to build 48 LCS ships in order to replace the current fleet of FFGs.  Latest plan, which has been proposed, to Congress is for authorization to build 20 additional LCS ships, 10 additional LCS per hull design.  This doesn’t even match the current number of FFGs in service.  
       For survivability in the littorals, the LCS is just as survivable if not more so than the FFG which also operates in the littorals to some extent.  With the FFG being replaced by the LCS that has minimal manning, I also question if the LCS is going to be capable of filling the same missions as the FFG such as Counter-Narco Terrorism (CNT) operations, piracy operations, and even just conducting a replenishment at sea due to manpower demands.  
       As far as utilizing the LCS as an unmanned mothership, that probably would not be feasible nor has there ever been a need for the Navy to operate motherships.  Therefore, your question concerning the use of LCS as an unmanned mothership is not exactly relevant.  
        Did the Navy get it right with the LCS design?  I believe they possibly did design a ship, which is capable of meeting the various mission demands.  I only question the minimal manning requirement since I have not personally seen nor heard how the FREEDOM and INDEPENDANCE have fared in day-to-day operations.

V/R,
LCDR Luke Schmidt</description>
		<content:encoded><![CDATA[<p>Excellent data analysis, however your blog does not take into consideration future defense spending cutbacks, which are already being seen with the Secretary of Defense (SECDEF) proposing the closing of Joint Forces Command.  I understand your analysis was written before SECDEF warned all services to prepare for future cutbacks in defense spending.  With the budget in mind and only two surface combatant options, I think we will see many more LCS ships being built than DDGs.<br />
	Agree that a FFG Service Life Extension Program (SLEP) would be a terrible option, despite any argument that the Florida congressional representatives can make in hopes of saving jobs in Mayport, FL.  As a former FFG Combat Systems Officer, I can assure you that the Oliver-Hazard Perry-Class frigate is an extremely outdated surface combatant with very limited and sometimes unreliable combat capability.  Additionally, the maintenance cost for an increased sustainment life would outweigh any possible benefit of maintaining these ships in the fleet.  We should be more concerned about having the right type of ships to meet the current and future mission demands and threats vice just trying to reach a 313-ship Navy on the books.<br />
	I believe the current number of FFGs in USN service is 29.  I have not heard any plans to build 48 LCS ships in order to replace the current fleet of FFGs.  Latest plan, which has been proposed, to Congress is for authorization to build 20 additional LCS ships, 10 additional LCS per hull design.  This doesn’t even match the current number of FFGs in service.<br />
       For survivability in the littorals, the LCS is just as survivable if not more so than the FFG which also operates in the littorals to some extent.  With the FFG being replaced by the LCS that has minimal manning, I also question if the LCS is going to be capable of filling the same missions as the FFG such as Counter-Narco Terrorism (CNT) operations, piracy operations, and even just conducting a replenishment at sea due to manpower demands.<br />
       As far as utilizing the LCS as an unmanned mothership, that probably would not be feasible nor has there ever been a need for the Navy to operate motherships.  Therefore, your question concerning the use of LCS as an unmanned mothership is not exactly relevant.<br />
        Did the Navy get it right with the LCS design?  I believe they possibly did design a ship, which is capable of meeting the various mission demands.  I only question the minimal manning requirement since I have not personally seen nor heard how the FREEDOM and INDEPENDANCE have fared in day-to-day operations.</p>
<p>V/R,<br />
LCDR Luke Schmidt</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Benjamin Walthrop</title>
		<link>http://blog.usni.org/2009/06/24/surface-warfare-still-searches-for-21st-century-ideas/comment-page-4/#comment-119546</link>
		<dc:creator>Benjamin Walthrop</dc:creator>
		<pubDate>Wed, 01 Jul 2009 12:09:01 +0000</pubDate>
		<guid isPermaLink="false">http://blog.usni.org/?p=3434#comment-119546</guid>
		<description>GBW,

It was a good rant and filled with great advice.  I think a blog post here at USNI on those historical lessons would be of value.  I do not believe in inevitable decay, and if you think about it you will realize that what I have been doing (fairly consistently now) regarding an FFG SLEP is pushing back on  what I believe is a foolish idea (SLEP for the FFGs). 

I am not happy with the LCS (for a number of reasons), but it is what the Navy has now, and I believe that there should be some mental capital spent on figuring out how to make it work for the USN.  That would be orders of magnitude more productive than the pages of ink spilled about the ship&#039;s shortcomings and wild-eyed ideas about how to return to the past (from a platform perspective).

The maintenance article would be good too.

V/R,</description>
		<content:encoded><![CDATA[<p>GBW,</p>
<p>It was a good rant and filled with great advice.  I think a blog post here at USNI on those historical lessons would be of value.  I do not believe in inevitable decay, and if you think about it you will realize that what I have been doing (fairly consistently now) regarding an FFG SLEP is pushing back on  what I believe is a foolish idea (SLEP for the FFGs). </p>
<p>I am not happy with the LCS (for a number of reasons), but it is what the Navy has now, and I believe that there should be some mental capital spent on figuring out how to make it work for the USN.  That would be orders of magnitude more productive than the pages of ink spilled about the ship&#8217;s shortcomings and wild-eyed ideas about how to return to the past (from a platform perspective).</p>
<p>The maintenance article would be good too.</p>
<p>V/R,</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Grampa Bluewater</title>
		<link>http://blog.usni.org/2009/06/24/surface-warfare-still-searches-for-21st-century-ideas/comment-page-4/#comment-119496</link>
		<dc:creator>Grampa Bluewater</dc:creator>
		<pubDate>Wed, 01 Jul 2009 05:51:31 +0000</pubDate>
		<guid isPermaLink="false">http://blog.usni.org/?p=3434#comment-119496</guid>
		<description>BW:
I am well aware things are not as one might wish. Put my little rant down as instruction for the young. Advice for the perplexed, if you wish.

You are just a little too accepting of the inevitability of decay and decline. Pushing back has its risks, but what&#039;s the point of making CNO of a 100 minus ship, no fleet auxiliaries, no viable escorts, four (maybe zero) carrier navy that can deploy (sort of) about three barely adequate battle groups.  Which is where the current crop of JO&#039;s will be in about two decades, at the current rate of decline. Faint heart and foolish policy did not win the cold war, or prepare (barely) the fleet for WWII.

Jefferson&#039;s Coastal Gunboat policy was folly made manifest.  While took the embarassment of a burnt out Capital to get the ball rolling, it got reversed. 

Besides this isn&#039;t a national problem, it&#039;s a Navy problem. We had  similar problems in the early seventies and fixed them. Most of what I digressed about in my little rant on good maintenence practice falls squarely on the shoulders of the CO/XO/Dept Heads. The rest is on the Commodore and his Material Officer and ultimately, the type commander. 

The first step to fixing a problem is documenting it, which is something any division officer can do. If he doesn&#039;t know how to inspect his own gear, she needs to pick the brain of his/her Chief/First Class. 

At the other end, command interest at the flag level is essential.  Fortunately, we pick new flag officers every year.
Sooner or later some of them will realize they are going to inherit the mess, and get more proactive about pushing back against the tide of poor decision making that is eating the ROV and OMN money, not to mention the Navy&#039;s credibility. 

If the Air Force can lose a Secretary and a Chief of Staff to failure to execute the fundamentals on nuclear weapons safety and security, the Navy had best clean its own house on basic maintenence and ship design. I hope the rot isn&#039;t deep enough to get higher than Navy involved, but if the top few rows of the stack of boxes poster think their good names aren&#039;t on the line, they will soon enough.

As far as the RAN SLEP or FRAM or whatever, at least we have an approximate upper bound on cost that has some foundation in reality. Don&#039;t forget it should be cheaper to use an existing solution than pay the upfront costs to develop one.

As an aside, there are tender hulls in the reserve fleet (I think, it&#039;s hard to keep up with the march of folly). There are lots of skills in the Ready Reserve.  Man one up, put it to work on breaking itself out. Then put her to work. Repeat.

Enough for now. Out of the loop old men need their rest, so they can rise and rant again.</description>
		<content:encoded><![CDATA[<p>BW:<br />
I am well aware things are not as one might wish. Put my little rant down as instruction for the young. Advice for the perplexed, if you wish.</p>
<p>You are just a little too accepting of the inevitability of decay and decline. Pushing back has its risks, but what&#8217;s the point of making CNO of a 100 minus ship, no fleet auxiliaries, no viable escorts, four (maybe zero) carrier navy that can deploy (sort of) about three barely adequate battle groups.  Which is where the current crop of JO&#8217;s will be in about two decades, at the current rate of decline. Faint heart and foolish policy did not win the cold war, or prepare (barely) the fleet for WWII.</p>
<p>Jefferson&#8217;s Coastal Gunboat policy was folly made manifest.  While took the embarassment of a burnt out Capital to get the ball rolling, it got reversed. </p>
<p>Besides this isn&#8217;t a national problem, it&#8217;s a Navy problem. We had  similar problems in the early seventies and fixed them. Most of what I digressed about in my little rant on good maintenence practice falls squarely on the shoulders of the CO/XO/Dept Heads. The rest is on the Commodore and his Material Officer and ultimately, the type commander. </p>
<p>The first step to fixing a problem is documenting it, which is something any division officer can do. If he doesn&#8217;t know how to inspect his own gear, she needs to pick the brain of his/her Chief/First Class. </p>
<p>At the other end, command interest at the flag level is essential.  Fortunately, we pick new flag officers every year.<br />
Sooner or later some of them will realize they are going to inherit the mess, and get more proactive about pushing back against the tide of poor decision making that is eating the ROV and OMN money, not to mention the Navy&#8217;s credibility. </p>
<p>If the Air Force can lose a Secretary and a Chief of Staff to failure to execute the fundamentals on nuclear weapons safety and security, the Navy had best clean its own house on basic maintenence and ship design. I hope the rot isn&#8217;t deep enough to get higher than Navy involved, but if the top few rows of the stack of boxes poster think their good names aren&#8217;t on the line, they will soon enough.</p>
<p>As far as the RAN SLEP or FRAM or whatever, at least we have an approximate upper bound on cost that has some foundation in reality. Don&#8217;t forget it should be cheaper to use an existing solution than pay the upfront costs to develop one.</p>
<p>As an aside, there are tender hulls in the reserve fleet (I think, it&#8217;s hard to keep up with the march of folly). There are lots of skills in the Ready Reserve.  Man one up, put it to work on breaking itself out. Then put her to work. Repeat.</p>
<p>Enough for now. Out of the loop old men need their rest, so they can rise and rant again.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Benjamin Walthrop</title>
		<link>http://blog.usni.org/2009/06/24/surface-warfare-still-searches-for-21st-century-ideas/comment-page-4/#comment-119401</link>
		<dc:creator>Benjamin Walthrop</dc:creator>
		<pubDate>Tue, 30 Jun 2009 22:20:23 +0000</pubDate>
		<guid isPermaLink="false">http://blog.usni.org/?p=3434#comment-119401</guid>
		<description>GBW,

I get your drift regarding basic maintenance.  I understand completely what a SLEP is intended to do.  I have recent experience with all of the above.

What you are describing is how you wish (and I wish) things to be.  That is a longer term problem that needs to be addressed, and I would dearly love to see someone offer some solutions to the maintenance disaster that is currently unfolding in the surface fleet.  Unfortunately, you are not describing the current reality.  

There are only two tenders left.  As much as we would like to reverse those decisions, that is water under the bridge.  There are zero SIMAs left.  Again, water under the bridge.  Sailors (in the surface force) do not really do deep maintenance, and the zone inspection program is failing if the INSURV results are any indication (and they are).  Beyond the ability to do maintenance, it appears that the surface force has largely lost the ability to even identify and diagnose MAJOR problems.

More to the point, a SLEP program for the FFG class would be throwing good money after bad at this point and is not a technically or economically viable alternative.  It cannot be done for $20M per hull as suggested, and the OQE for that are the costly RAN efforts to date.

V/R,</description>
		<content:encoded><![CDATA[<p>GBW,</p>
<p>I get your drift regarding basic maintenance.  I understand completely what a SLEP is intended to do.  I have recent experience with all of the above.</p>
<p>What you are describing is how you wish (and I wish) things to be.  That is a longer term problem that needs to be addressed, and I would dearly love to see someone offer some solutions to the maintenance disaster that is currently unfolding in the surface fleet.  Unfortunately, you are not describing the current reality.  </p>
<p>There are only two tenders left.  As much as we would like to reverse those decisions, that is water under the bridge.  There are zero SIMAs left.  Again, water under the bridge.  Sailors (in the surface force) do not really do deep maintenance, and the zone inspection program is failing if the INSURV results are any indication (and they are).  Beyond the ability to do maintenance, it appears that the surface force has largely lost the ability to even identify and diagnose MAJOR problems.</p>
<p>More to the point, a SLEP program for the FFG class would be throwing good money after bad at this point and is not a technically or economically viable alternative.  It cannot be done for $20M per hull as suggested, and the OQE for that are the costly RAN efforts to date.</p>
<p>V/R,</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Grampa Bluewater</title>
		<link>http://blog.usni.org/2009/06/24/surface-warfare-still-searches-for-21st-century-ideas/comment-page-4/#comment-119394</link>
		<dc:creator>Grampa Bluewater</dc:creator>
		<pubDate>Tue, 30 Jun 2009 21:25:44 +0000</pubDate>
		<guid isPermaLink="false">http://blog.usni.org/?p=3434#comment-119394</guid>
		<description>Perfection is the death of affordable adequacy.

One hates to reiterate, but HM&amp;E do not vanish like a soap bubble popping when a installed digital clock reaches an arbitrarily established design service life. Class B (repair to installation specs) or Class C (repair by replacement or repair of inoperative or worn beyond max spec components) overhauls may be accomplished comparatively economically by SIMA or (alas, foolishly deleted) Tender sailors and shops. Functional components can be stripped from inactive ships of the class. While failure to spend pennies on &quot;mothballing&quot; has had a repair opportunity cost of dollars or hundreds in terms of repair opportunity, H,M &amp; E components are robust. Most or much of it is still good, or less worn and cheaper to repair than equipment in service. Particularly if you can make one out of two.

Excuse the following digression into basic good practice that follows, but the postings that are up show that many don&#039;t understand that execution of the fundamentals is a key to long, effective ship life.

Preventative maintenence (clean, preserve, lubricate, test, analyze, align, adjust, calibrate) must be done. If filter housings, access panels, zirc fittings and the like don&#039;t have tool scars on the paint covering the bolts and nuts, it&#039;s not.

Minor corrective maintenence must be done promptly, lest it grow into a major repair. INSURV publishes (still, hopefully) a list of common and repetitive deficiencies for every ship class extant. The measure of state of repair is best measured by how much of a preponderance of minor items outweighs the show stoppers in the report.  Part I (serious) Safety and Mission Degrading items are more often than not correctable in short order given the increased command attention brought to bear and high level expertise freed up from NAVSEA&#039;s Engineering Centers.

The experienced and wise XO&#039;s send their wardroom and CPO&#039;s out looking for the common and repetitive deficiencies as part of an active zone inspection program,and then follow up. Every defect is logged with a job sequence number in the equipment deficiency log.  The Captain goes through that log with the Department Head once a week. Standard questions: Casrep needed?; drafted and sent?; Gear troubleshot, parts on order?; RQN Number and status?: Work Request submitted?; JSN/PRI?. (Suggested order of sequence: NavOps Monday; Engineering Tuesday; Weapons/Combat Systems Wednesday; Supply Thursday; Friday Field Day/PB for T, Zone inspection,Fish Dinner.)

XO checks a chunk of Heads &amp; Beds each day, Captain goes walkabout every day and looks at something, no notice, HARD. The EDL goes to every drill critique to log emergent items.

Timely and appropriate submission of &quot;minor&quot; CASREP&#039;s MUST be viewed as evidence of due diligence and engineering/technical competence by superiors in the chain of command. 

(Back on topic)

That&#039;s before SLEP.  SLEP gets the hard to reach, replaces/updates obsolete weapons and fire control, adds new countermeasures for new threats,installs major shipalts, A&amp;I&#039;s, Field changes, junks the headache hangar queen Mk 1 with a solid reliable Mk 4. SLEP uses proven systems being purchased, reducing per unit cost by purchasing additional units. Let the words &quot;redo the wardroom wallpaper and furnishings&quot; never be breathed aloud.

I could go on (and on, and on), but you get my drift.

This, while requiring very hard work and expertise by ship&#039;s force, in the long run, lowers maintenence costs and extends vessel life. A lot. Just don&#039;t cut the manning to minimum levels, it&#039;s a false economy for repair, training, and survivability.

But that&#039;s another post.</description>
		<content:encoded><![CDATA[<p>Perfection is the death of affordable adequacy.</p>
<p>One hates to reiterate, but HM&amp;E do not vanish like a soap bubble popping when a installed digital clock reaches an arbitrarily established design service life. Class B (repair to installation specs) or Class C (repair by replacement or repair of inoperative or worn beyond max spec components) overhauls may be accomplished comparatively economically by SIMA or (alas, foolishly deleted) Tender sailors and shops. Functional components can be stripped from inactive ships of the class. While failure to spend pennies on &#8220;mothballing&#8221; has had a repair opportunity cost of dollars or hundreds in terms of repair opportunity, H,M &amp; E components are robust. Most or much of it is still good, or less worn and cheaper to repair than equipment in service. Particularly if you can make one out of two.</p>
<p>Excuse the following digression into basic good practice that follows, but the postings that are up show that many don&#8217;t understand that execution of the fundamentals is a key to long, effective ship life.</p>
<p>Preventative maintenence (clean, preserve, lubricate, test, analyze, align, adjust, calibrate) must be done. If filter housings, access panels, zirc fittings and the like don&#8217;t have tool scars on the paint covering the bolts and nuts, it&#8217;s not.</p>
<p>Minor corrective maintenence must be done promptly, lest it grow into a major repair. INSURV publishes (still, hopefully) a list of common and repetitive deficiencies for every ship class extant. The measure of state of repair is best measured by how much of a preponderance of minor items outweighs the show stoppers in the report.  Part I (serious) Safety and Mission Degrading items are more often than not correctable in short order given the increased command attention brought to bear and high level expertise freed up from NAVSEA&#8217;s Engineering Centers.</p>
<p>The experienced and wise XO&#8217;s send their wardroom and CPO&#8217;s out looking for the common and repetitive deficiencies as part of an active zone inspection program,and then follow up. Every defect is logged with a job sequence number in the equipment deficiency log.  The Captain goes through that log with the Department Head once a week. Standard questions: Casrep needed?; drafted and sent?; Gear troubleshot, parts on order?; RQN Number and status?: Work Request submitted?; JSN/PRI?. (Suggested order of sequence: NavOps Monday; Engineering Tuesday; Weapons/Combat Systems Wednesday; Supply Thursday; Friday Field Day/PB for T, Zone inspection,Fish Dinner.)</p>
<p>XO checks a chunk of Heads &amp; Beds each day, Captain goes walkabout every day and looks at something, no notice, HARD. The EDL goes to every drill critique to log emergent items.</p>
<p>Timely and appropriate submission of &#8220;minor&#8221; CASREP&#8217;s MUST be viewed as evidence of due diligence and engineering/technical competence by superiors in the chain of command. </p>
<p>(Back on topic)</p>
<p>That&#8217;s before SLEP.  SLEP gets the hard to reach, replaces/updates obsolete weapons and fire control, adds new countermeasures for new threats,installs major shipalts, A&amp;I&#8217;s, Field changes, junks the headache hangar queen Mk 1 with a solid reliable Mk 4. SLEP uses proven systems being purchased, reducing per unit cost by purchasing additional units. Let the words &#8220;redo the wardroom wallpaper and furnishings&#8221; never be breathed aloud.</p>
<p>I could go on (and on, and on), but you get my drift.</p>
<p>This, while requiring very hard work and expertise by ship&#8217;s force, in the long run, lowers maintenence costs and extends vessel life. A lot. Just don&#8217;t cut the manning to minimum levels, it&#8217;s a false economy for repair, training, and survivability.</p>
<p>But that&#8217;s another post.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Benjamin Walthrop</title>
		<link>http://blog.usni.org/2009/06/24/surface-warfare-still-searches-for-21st-century-ideas/comment-page-4/#comment-119274</link>
		<dc:creator>Benjamin Walthrop</dc:creator>
		<pubDate>Tue, 30 Jun 2009 18:44:50 +0000</pubDate>
		<guid isPermaLink="false">http://blog.usni.org/?p=3434#comment-119274</guid>
		<description>&quot;Examples of 70’s technology that may still exist after a SLEP…

Well, at least that old stuff gets underway more often than not…&quot;

You are correct to an extent.  I interperet the recent INSURV results from active ships to indicate that many of the same problems probably exist in the mature technology and mature HM&amp;E systems fieled. They are just being ignored in order to support the OPTEMPO.  How&#039;s that gonna work out if the level of presumed survivability is not quite what has been advertised?

V/R,</description>
		<content:encoded><![CDATA[<p>&#8220;Examples of 70’s technology that may still exist after a SLEP…</p>
<p>Well, at least that old stuff gets underway more often than not…&#8221;</p>
<p>You are correct to an extent.  I interperet the recent INSURV results from active ships to indicate that many of the same problems probably exist in the mature technology and mature HM&amp;E systems fieled. They are just being ignored in order to support the OPTEMPO.  How&#8217;s that gonna work out if the level of presumed survivability is not quite what has been advertised?</p>
<p>V/R,</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: sid</title>
		<link>http://blog.usni.org/2009/06/24/surface-warfare-still-searches-for-21st-century-ideas/comment-page-4/#comment-119203</link>
		<dc:creator>sid</dc:creator>
		<pubDate>Tue, 30 Jun 2009 17:20:15 +0000</pubDate>
		<guid isPermaLink="false">http://blog.usni.org/?p=3434#comment-119203</guid>
		<description>&lt;i&gt;Examples of 70’s technology that may still exist after a SLEP...&lt;/i&gt;

Well, at least that old stuff &lt;a href=&quot;http://www.navytimes.com/news/2009/06/navy_lcs2_delay_062909w/&quot; rel=&quot;nofollow&quot;&gt;gets underway more often than not&lt;/a&gt;...</description>
		<content:encoded><![CDATA[<p><i>Examples of 70’s technology that may still exist after a SLEP&#8230;</i></p>
<p>Well, at least that old stuff <a href="http://www.navytimes.com/news/2009/06/navy_lcs2_delay_062909w/" rel="nofollow">gets underway more often than not</a>&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Benjamin Walthrop</title>
		<link>http://blog.usni.org/2009/06/24/surface-warfare-still-searches-for-21st-century-ideas/comment-page-4/#comment-119084</link>
		<dc:creator>Benjamin Walthrop</dc:creator>
		<pubDate>Tue, 30 Jun 2009 14:29:13 +0000</pubDate>
		<guid isPermaLink="false">http://blog.usni.org/?p=3434#comment-119084</guid>
		<description>&quot;Is not the point to put updated systems in the ship?&quot;

This is precisely why I asked the question about what a “bobtail SLEP” looks like to the advocates of this position.  I have not asked for a white paper or any other such non-sense.  I have only asked that the true believers regarding the efficacy and economy of SLEPing an FFG provide at least some level of detail as to what that would entail so those points can be rationally debated.  

Based on Byron&#039;s estimates of $20M per hull to execute his vision, I can tell you from experience that it will not buy a great deal more service life for the hull, electrical, and mechanical systems of the FFGs that are not really mid-life warships as you claim, but are actually coming very quickly to the end of their design service life. 

I also don&#039;t think that same $20M will be stretched to improve the legacy (and closed architecture) combat and C4ISR systems to a level that the advocates seem to believe.  The price for a docking selected restricted availability (far smaller in scope than any FRAM or SLEP as far as I can tell) is running in the $7M-$10M price range. 

Examples of 70&#039;s technology that may still exist after a SLEP are the machinery control consoles, the switchboards, the 400 Hz generators, the desalination systems, the internal communication system, etc.  I am left to guess because the advocates for such a course of action have simply refused to provide any level of detail regarding their vision.  A bullet list of systems that you envision to be modernized would be just fine.

The fact that the RAN effort ran $360M per hull should at least cause any serious participant in this debate some uncomfortable thoughts regarding the what the cost for a FFG SLEP would be and if the cost is worth the investment.  Ironically, this is the example that an advocate provided to educate me.

I have never advocated scrapping mid-life ships.  You seem to be the one defining 24 year FFGs as having the characteristics of a mid-life platform without any basis at all from a technical perspective for that claim.

V/R,</description>
		<content:encoded><![CDATA[<p>&#8220;Is not the point to put updated systems in the ship?&#8221;</p>
<p>This is precisely why I asked the question about what a “bobtail SLEP” looks like to the advocates of this position.  I have not asked for a white paper or any other such non-sense.  I have only asked that the true believers regarding the efficacy and economy of SLEPing an FFG provide at least some level of detail as to what that would entail so those points can be rationally debated.  </p>
<p>Based on Byron&#8217;s estimates of $20M per hull to execute his vision, I can tell you from experience that it will not buy a great deal more service life for the hull, electrical, and mechanical systems of the FFGs that are not really mid-life warships as you claim, but are actually coming very quickly to the end of their design service life. </p>
<p>I also don&#8217;t think that same $20M will be stretched to improve the legacy (and closed architecture) combat and C4ISR systems to a level that the advocates seem to believe.  The price for a docking selected restricted availability (far smaller in scope than any FRAM or SLEP as far as I can tell) is running in the $7M-$10M price range. </p>
<p>Examples of 70&#8242;s technology that may still exist after a SLEP are the machinery control consoles, the switchboards, the 400 Hz generators, the desalination systems, the internal communication system, etc.  I am left to guess because the advocates for such a course of action have simply refused to provide any level of detail regarding their vision.  A bullet list of systems that you envision to be modernized would be just fine.</p>
<p>The fact that the RAN effort ran $360M per hull should at least cause any serious participant in this debate some uncomfortable thoughts regarding the what the cost for a FFG SLEP would be and if the cost is worth the investment.  Ironically, this is the example that an advocate provided to educate me.</p>
<p>I have never advocated scrapping mid-life ships.  You seem to be the one defining 24 year FFGs as having the characteristics of a mid-life platform without any basis at all from a technical perspective for that claim.</p>
<p>V/R,</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: capospin</title>
		<link>http://blog.usni.org/2009/06/24/surface-warfare-still-searches-for-21st-century-ideas/comment-page-4/#comment-118975</link>
		<dc:creator>capospin</dc:creator>
		<pubDate>Mon, 29 Jun 2009 23:07:55 +0000</pubDate>
		<guid isPermaLink="false">http://blog.usni.org/?p=3434#comment-118975</guid>
		<description>Ok Ben so the LCS is a good deal? How can  a SLEP FFG be 70s technology? Is not the point to put updated systems in the ship?  So she would be on older ship with new or updated systems. The point is the LCS as she is today is a bad idea. Scrapping mid life warships to save operational money is not the way to build the combat fleet the navy needs to do the job. New ships in many more  numbers concurrent with  a SLEP/FRAM program is what we need.</description>
		<content:encoded><![CDATA[<p>Ok Ben so the LCS is a good deal? How can  a SLEP FFG be 70s technology? Is not the point to put updated systems in the ship?  So she would be on older ship with new or updated systems. The point is the LCS as she is today is a bad idea. Scrapping mid life warships to save operational money is not the way to build the combat fleet the navy needs to do the job. New ships in many more  numbers concurrent with  a SLEP/FRAM program is what we need.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Benjamin Walthrop</title>
		<link>http://blog.usni.org/2009/06/24/surface-warfare-still-searches-for-21st-century-ideas/comment-page-4/#comment-118969</link>
		<dc:creator>Benjamin Walthrop</dc:creator>
		<pubDate>Mon, 29 Jun 2009 21:46:26 +0000</pubDate>
		<guid isPermaLink="false">http://blog.usni.org/?p=3434#comment-118969</guid>
		<description>That last post should have read $360M per ship rather than $360B per ship.  My opinion that this is not a &quot;good deal&quot; remains unchanged by the typo.</description>
		<content:encoded><![CDATA[<p>That last post should have read $360M per ship rather than $360B per ship.  My opinion that this is not a &#8220;good deal&#8221; remains unchanged by the typo.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

