Chief Stoker said:The Canada class SSN's came close with the RCN even sending personnel on nuclear engineering coursing but opposition from our own country and surprisingly the United Sates killed the deal.
Oldgateboatdriver said:In any event, and even though all of the above is a very interesting topic, have we not strayed far from the thread's original purpose?
suffolkowner said:the Canadian Naval Review article suggested that operating costs for modern subs should be 30% of say a Halifax class ship but I didn't see any supporting documentation
Dimsum said:Would the requirements mesh well though (e.g. Aussies generally in warm-ish waters, us in cold-ish waters, etc.) ?
Oldgateboatdriver said:....There is just no real big savings to be had by building small OPV's as opposed to large one, other than some people's fixation on size (or on always carrying soldiers onboard, right Chris ).
From technical specifications to functional demands.
• Use of Flex concept in all ships design since the millennium.
• Use of DNV, NAVAL standards.
• Reuse design elements between different ship classes.
• Use of civilian standards whenever possible especially with
IT.
• Redundant passive fiber network for multi purposes.
• Same Combat Management System in all lager units.
• Standard Racks for all weapon, sensor, communication and
IT systems in all lager units.
• Same Integrated Platform Management System in Frigates
and Flexible Support Ships.
I doubt it would be that difficult to put 1-2 mk41 launchers on something like the Holland, even if one has to lengthen the hull by 20ft and at the same time increase the fuel load for the helo, increasing capability. Most of the ships these days are designed to carry the mission modules, so it wouldn't take much tweaking to add a 2-3 spots for the systems. None of this should be that difficult, given the Holland is a good sized platform.Chris Pook said:Stop trying to pick a fight OGBD. [Xp
I happen to agree with you across the board. And I like big cheap hulls precisely because there is more room for muddy boots, (or to accommodate Churchill's Naval Traditions).
That being said - on the Software side of things - why can't the FELEX system be ported holus bolus to the AOPS and the CSC and maybe an OPV? Or at least used as the basis of a CMS/IPMS system that can be ported. Again, just as my buddies the Danes decided with their fleet.
http://www.ndia.org/Divisions/Divisions/International/Documents/U.S.-Denmark%20Defense%20Industry%20Seminar/Danish%20frigate%20program%20visit%20USN%20May%202014.pdf
And this one.
http://www.aspistrategist.org.au/wp-content/uploads/2014/11/OMT-Dansh-Frigate-Programme-April-2014.pdf
Why do we keep paying to re-invent wheels?
And further to your last - if you are going to be stuck with all that top hamper you might find some self-loading ballast useful.
What the U.S. Navy Could Learn from Danish Frigate Design
By: Megan Eckstein
March 5, 2015 5:47 PM
As the U.S. Navy’s requirements and engineering communities look at upcoming ship classes and attempt to build in flexibility, they first need to decide what it means to be a “flexible ship” and how much to prioritize that flexibility, one admiral said.
During a panel at the American Society of Naval Engineers’ ASNE Day 2015, Rear Adm. Bryant Fuller, chief engineer for Naval Sea Systems Command (NAVSEA), said it is important to decide what flexibility means to each program early on, and how much of it is needed – is there a core capability that ship class revolves around, or should it strive for ultimate flexibility, like the Danish Navy’s StanFlex system and its Iver Huitfeldt-class frigate?
Several panelists compared American ships to the Danish frigates, including panel moderator retired Vice Adm. Paul Sullivan. He said he had the chance to see the ships up close last fall and was impressed.
The Danish navy took its Absalon-class support ship hull design and reconfigured it to include a 76mm gun. Both the support ship and the frigate subscribe to the Danish navy’s StanFlex modular mission payload system, which Sullivan said allowed the navy to put legacy weapons systems on the Iver Huitfeldt-class instead of having to develop new systems right away, like the Navy did with the Littoral Combat Ship.
“The StanFlex buzz was you could put the new gun in and 24 hours later you’re ready to go to sea,” he added.
This ultra-flexible system may not sound like it would be relevant to some American ship classes, such as cruisers and destroyers, but Capt. Thomas Halvorson, deputy director of the Navy’s surface warfare directorate for Ballistic Missile Defense, Aegis and Destroyers, said there were still lessons to be drawn for future surface combatants.
Halvorson said the Aegis Baseline 9 upgrade effort had been a great accomplishment for the Navy’s cruiser fleet, but it was also a work-intensive accomplishment. A more flexible ship design could allow the Navy to upgrade the computers on a future surface combatant more routinely, rather than having to wait for a massive midlife upgrade.
“One of the other ideas I heard [the Danes] talk about, Adm. Sullivan, was they can change out the computer program completely in 90 days,” Halvorson said. “We all have a little bit of a part to play in the two-year upgrade that involves ripping out pieces massive pieces of ship infrastructure to change out every server in the room. We need to get closer to that Dane mentality.”
Also during the panel, Program Executive Officer for Ships Rear Adm. David Gale explained the importance of building in enough flexibility from the beginning of a program. With the Mobile Landing Platform design being used as the basis of the Afloat Forward Staging Base design, the latter ship only has as much flexibility in it as the former – which in this case is a lot of flexibility. Gale praised the AFSB team for achieving “80 percent of the requirement for 50 percent of the cost by just going to MLP and adding an aviation capability to the ship.”
In fact, the ship design has so much flexibility and extra margins built into it that Gale said, “in aviation and in [special operations] warfare areas, we’re already writing change documents to improve these ships.”
The first one has definite benefits; is the other something that we should really be running our ships up and down the coasts to support? Or is CARIBBE more of a training opportunity than anything?E.R. Campbell said:...for FishPats and not for Op CARIBBE and not for a lot of other tasks.
Zuko wrote:
Just saying US ships cost 3x as much as comparable Dutch ships is a simplistic and inaccurate thing to say. Without detailed information which usually isn't easy to determine by public sources it is very difficult to compare costs of ships because you never know if you are comparing apples to apples. There are tons of variables in how the numbers are calculated and what is "included" in a cost that is given to a ship. You also seldom know if you are comparing the same years dollars to the same years dollars. That's the case even when comparing ships within the US Navy, and even more so when comparing to other countries. I would also differ with the idea that the ships are comparable.
I'm not saying the US naval shipbuilding program doesn't have inefficiencies, it obviously does. But the slides and the arguments made by the Damon rep are misleading and inaccurate.
1) Hein van Ameijden made it clear in his speech that while his data may not be absolutely correct and/or directly comparable, he does, however stand behind his main conclusions that the US Navy is paying far too much for its vessels.
2) Given his pedigree (see his biography here), it is safe to assume Hein van Ameijden to have a solid business insight and his conclusions to be based on much more than mere *public sources*.
3) Because of your excessive focus on costs (probably), you may not have noticed that yard hours were provided for both the DDG-51s and the LCFs in the slide posted earlier :
DDG-51 : 4.4 million manhours
LCF : 1.5 million manhours
4) The manhours mentioned above are very consistent wit those published in a 1995 NSWC comparative study of US & Japan shipbuilding :
Design manhours :
DDG-51 : 6.0 million
DDG-173 : 1.2 million
Construction manhours :
DDG-51 : 5.0 million
DDG-173 : 2.0 million
5) And finally, a 2004 NATO study found the shipyard recurring cost accounting methods used by the Netherlands on the one hand and the USCG on the other hand to be very consistent each other for SWBS groups 100 to 700, i.e. :
SWBS 100 : Structure
SWBS 200 : Propulsion
SWBS 300 : Electrical
SWBS 400 : Electronics
SWBS 500 : Auxiliaries
SWBS 600 : Outfitting
SWBS 700 : Armament
Unsurprisingly, the shipyard administrative costs (SWBS Group 900) were found to be considerably higher in the US shipbuilding, reflecting, among other things, the infuence of commercial practices in the Dutch shipbuilding industry, as opposed to US shipyards which primarily produce naval or coast guard vessels.