Free Republic
Browse · Search
News/Activism
Topics · Post Article

Skip to comments.

U.S. Navy Discovers That Sailors Need Sleep (LCS Troubles)
War is Boring ^ | 07/11/2014 | Michael Peck

Posted on 07/11/2014 10:51:02 PM PDT by sukhoi-30mki

click here to read article


Navigation: use the links below to view more comments.
first previous 1-2021-4041-49 last
To: NonValueAdded

Data is data


41 posted on 07/12/2014 5:45:12 PM PDT by Ready4Freddy
[ Post Reply | Private Reply | To 39 | View Replies]

To: Slings and Arrows

Not really a fighting machine, more of a drop them off quick and get out of the way.

Survivability is low in both LCS models, sacrificed for speed (in the mid to high 40s kn). Considerably slower when at dock for repairs, of course.


42 posted on 07/12/2014 6:24:37 PM PDT by Ready4Freddy
[ Post Reply | Private Reply | To 14 | View Replies]

To: Ready4Freddy

I’m starting to get the impression that this ship was not a good idea.


43 posted on 07/12/2014 6:33:37 PM PDT by Slings and Arrows (You can't have Ingsoc without an Emmanuel Goldstein.)
[ Post Reply | Private Reply | To 42 | View Replies]

To: sukhoi-30mki; All
As a former ship driver I am concerned about the number of people available to stand watch while underway with only 8 officers and 32 enlisted for a crew.

Since the CO and XO aren't going to be standing watch, that leaves 2 officers per watch. Are they both on the bridge? I hope so. If they are, who is in CIC (Combat Information Center) and Engineering? No officers available if they are both on the bridge.

Now we get to the enlisted watch standers. You need at least one each for Quartermaster, Helmsman, and Boatswains-mate. You also need 2 lookouts (fore and aft), two in Combat Information Center, and two in engineering. Times 3 watch sections gets you to 27 enlisted. That leaves only 5 non-watch standers such as TWO Culinary Specialists (cooks), ONE Corpsman, ONE Logistics Specialist (storekeeper), and ONE other.

Now try keeping this up with half on and half off watch just for wartime steaming. If the ship takes damage and/or casualties you can forget about fighting it. There will barely be enough manpower to get it back to port.

In that case, you are worse off than if you had NEVER BUILT IT because it has sucked up other scarce resources that could have been better used elsewhere.

Garde la Foi, mes amis! Nous nous sommes les sauveurs de la République! Maintenant et Toujours!
(Keep the Faith, my friends! We are the saviors of the Republic! Now and Forever!)

LonePalm, le Républicain du verre cassé (The Broken Glass Republican)

44 posted on 07/12/2014 6:35:39 PM PDT by LonePalm (Commander and Chef)
[ Post Reply | Private Reply | To 1 | View Replies]

To: sukhoi-30mki

“Mechanical problems were so common that the Freedom lost 55 days at sea, which in turn limited the amount of useful data that the Navy could collect about how reliable the LCS is in the first place.”

I’d say they got their data.


45 posted on 07/12/2014 6:36:30 PM PDT by Lurker (Violence is rarely the answer. But when it is it is the only answer.)
[ Post Reply | Private Reply | To 1 | View Replies]

To: sukhoi-30mki

Humans need sleep?

Huh!


46 posted on 07/12/2014 6:40:26 PM PDT by AFreeBird
[ Post Reply | Private Reply | To 1 | View Replies]

To: PieterCasparzen

A lot of the ideas as far as software goes, on this project are being decided on now. The first submarine won’t be completed until 2026. It is estimated that the last one will be in service till 2078. So you can only imagine how that software will contrast to what will be in 2078.

I am not a software guy, but I always found it interesting how the computing technology on a submarine such as a LOS ANGELES Class compared to what we have now.

I will ad that the radio room was always refitted with the best the military could find.


47 posted on 07/13/2014 4:08:31 AM PDT by castlegreyskull
[ Post Reply | Private Reply | To 27 | View Replies]

To: sukhoi-30mki

Kill it dead. Kill the whole project, walk away, take the loss and hopefully learn some valuable lessons in how NOT to design a combat vessel. The Little Crappy Ship has been a failure but too many egos in Big Navy are involved to admit it.


48 posted on 07/13/2014 10:24:06 AM PDT by GATOR NAVY
[ Post Reply | Private Reply | To 1 | View Replies]

To: castlegreyskull

Good “old-fashioned” principles of modularity.

In the sofware design, hardware handling is separated out in an abstraction layer, i.e., a library of routines/classes/etc.

The rest of the sofware is built on that.

For hardware, at the lowest level, it “should” be just that - hardware.

Then their is “firmware” on top of that, controller devices that are actually small computers running sofware. Like a disk drive controller.

Any of those three layers should be able to be replaced, and as long as the new one supports the old interface, and works “as advertised”, the other layers need no changes. Meanwhile, it can have a new interface that it also supports. When the other layers get to supporting the new interface, which is typically required to use new features, new features can be used.

It becomes like the 150-year-old axe that was my great-grandaddy’s - it’s had 3 new heads and 4 new handles.


49 posted on 07/13/2014 1:21:22 PM PDT by PieterCasparzen (We have to fix things ourselves)
[ Post Reply | Private Reply | To 47 | View Replies]


Navigation: use the links below to view more comments.
first previous 1-2021-4041-49 last

Disclaimer: Opinions posted on Free Republic are those of the individual posters and do not necessarily represent the opinion of Free Republic or its management. All materials posted herein are protected by copyright law and the exemption for fair use of copyrighted works.

Free Republic
Browse · Search
News/Activism
Topics · Post Article

FreeRepublic, LLC, PO BOX 9771, FRESNO, CA 93794
FreeRepublic.com is powered by software copyright 2000-2008 John Robinson