Manufacturing in the USA

A website devoted to that topic:  Reshoring Manufacturing

Before D-Day, There Was Dieppe

June 6 will mark the 75th anniversary of the Normandy Invasion.  Most Americans surely have at least  some  knowledge of this event…but relatively few are aware that there was an earlier amphibious assault on occupied Europe. The attack on the French port of  Dieppe  took place on August 19, 1942. The objectives were twofold. First, the attack was intended as kind of a “feasibility test” for the large-scale invasion which was to take place later. As stated by General Sir Alan Brooke, “If it was ever intended to invade France it was essential to launch a preliminary offensive on a divisional scale.” Second, the attack was intended to convince Hitler that an invasion was more imminent than it in fact was, thereby leading to the diversion of German forces from other areas.

The troops assigned to Dieppe were mostly Canadians5000 of them. There were also British commandos and a small number of American Rangers. Eight destroyers were assigned to the operation, along with 74 Allied air squadrons.

The attack was a disastrous failure. In the words of military historian John Keegan: “When the badly shocked survivors of that terrible morning were got home and heads counted, only 2,110 of the 4,963 Canadians who had set sail the day before could be found. It became known later that 1,874 were prisoners, but of these 568 were wounded and 72 were to die of their wounds, while 378 of those returning were also wounded. Sixty-five percent of the Canadians engaged had therefore become casualties, almost all of them from the six assaulting infantry battalions, a toll which compared with that of July 1st, 1916, first day of the Battle of the Somme and blackest in the British army’s history. The 2nd Canadian Division had, for practical purposes, been destroyed…Strategic as well as human criteria applied in measuring the scale of the disaster. All the tanks which had been landed had been lost…lost also were 5 of the 10 precious Landing Craft Tank. And, auguring worst of all for the future, the damage had been done not by hastily summoned reinforcements, but by the forces already present; the 3 Canadian battalions which had stormed the central beach had been opposed by a single German companyat odds, that is, of 12 to 1…” If one defending unit could stop an attacking force with 12 times the numbers, a successful invasion would be impossible. Keegan: “(the disparity between the power of the attack and the defense) clearly could not be overcome merely by increasing the numbers of those embarked for the assault. that would be to repeat the mistakes of the First World War, when the solution of greater numbers resulted arithmetically in greater casualties for no territorial gains.”

Captain (later Vice-Admiral) John Hughes-Hallett summarized the lessons of the failure in a report written shortly after the fact. To quote Keegan once again: “’The lesson of Greatest Importance,’ his report capitalized and italicized, “Is the need for overwhelming fire support, including close support, during the initial stages of the attack,’ It should be provided by ‘heavy and medium Naval bombardment, by air action, by special vessels or craft’ (which would have to be developed) ‘working close inshore, and by using the firepower of the assaulting troops while still seaborne.’”

The lessons of Dieppe were taken seriously. Keegan goes on to describe the naval firepower assigned to the actual D-day landings carried out by Canadians at Juno Beach: “Heaviest and furthest out were the two battleships  Ramillies  and  Warspite…They both mounted four 15-inch guns and there were two more in  Roberts, their accompanying monitor. Their chief task was to engage the large-calibre shore batteries between the Orne and the mouth of the Seine, but so great was their rangeover eighteen milesthat they could in emergency be talked in on any target in the British bridgeheads…Immediately port and starboard of the lowering position was disposed a line of twelve cruisers, the smallest, like  Diadem, mounting eight 5.25 inch guns, the largest, like  Belfast, twelve 6-inch. Both were covering the Canadian beaches…In front of the Canadian lowering position manoeuvred the supporting destroyers, eleven for the Juno sector…And immediately in ahead of the assault-wave infantry was deployed a small fleet of support landing-craft: eight Landing Craft Gun, a sort of small monitor mounting two 4.7 inch guns; four Landing Craft Support, bristling with automatic cannon; eight Landing Craft tank (Rocket), on each of which were racked the tubes of 1,100 5-inch rockets, to be discharged in a single salvo; and eighteen Landing Craft Assault (Hedgerow), which were to fire their loads of twenty-four 60-lb bombs into the beach obstacles and so explode as many as possible of the mines attached to them.”

In addition to the need for very heavy naval firepower, the D-day planners learned another lesson from Dieppe: rather than immediately seizing a port, or landing in close proximity to one, they avoided ports altogether, landing supplies initially over an open beach and leaving the capture of a port for a later phase in the operation.

Keegan quotes are from his book,  Six Armies in Normandy.

There is much talk in management and consulting circles these days about the need for organizations to “embrace failure”…much of this talk is fairly glib and does not always consider that certain kinds of failures are truly catastrophic from a human/strategic/economic point of view and are indeed worthy of stringent efforts to prevent their occurrence.  When failurescatastrophic or otherwisedo occur, it is incumbent on responsible leadership to seriously analyze the lessons to be learned and to apply that knowledge diligently.  In the case of Dieppe, that work does indeed appear to have been done.

Book Review: The Caine Mutiny

The Caine Mutiny by Herman Wouk

—-

(reposted in honor of Herman Wouk, who died yesterday at the age of 103)

Just about everyone has seen the movie based on this book, featuring Humphrey Bogart’s famous performance as Captain Queeg.  The movie is indeed excellentthe book is even better, and contains a lot that is absent from the film.  And while the film ends basically after the court-martial scene, the book continues to follow the USS Caine and  key characters for the duration of the war.  In this review, I won’t worry about spoilers re plot elements that were included in the movie, but will try to minimize them as far as other aspects of the book are concerned. After summarizing the story, I’ll comment on some of the issue raised by the book. (A 2005 article, referencing The Caine Mutiny, refers to Wouk as “the first neoconservative.”)

Lieutenant Commander Philip Queeg, a rigid and insecure man, is appointed during WWII to the command of Caine, a decrepit old destroyer-minesweeper…the ship and its slovenly-appearing crew are described as being part of the  “hoodlum navy.”  This is Queeg’s first command, and he is desperately concerned to make it a success, deeply afraid of making a mistake which will lead to his failure.  Ironically, it is specifically this fear of failure and perceived need for perfection which is responsible for many, perhaps most, of his troubles. When Caine runs aground the first time Queeg takes her out, he fails to submit the required grounding report for fear of higher authority’s reaction. When the ship cuts her own towline while assigned to target-towing duty, Queeg cannot make up him mind whether or not to attempt recovery of the drifting targetand radios in for instructions.  Incidents like these do not inspire confidence in Queeg on the part of his superiors.

The officers and crew of Caine also lose confidence in the captain as his obsessive-compulsive behavior becomes increasingly problematic.  As a result of several incidents during combat, there are also concerns about Queeg’s personal courage. While no one aboard Caine likes Queeg once they get to know him, the captain’s most vocal critic is an officer named Thomas Keefer, an intellectual who is an aspiring novelist. Keefer  has a cynical attitude toward the Navy, which he refers to as “a master plan designed by geniuses for execution by idiots,” and advises Willie Keith, a young officer who is his subordinate,  that “If you’re not an idiot, but find yourself in the Navy, you can only operate well by pretending to be one.”

The ship’s executive officer is Steve Maryk. In civilian life a commercial fisherman, Maryk now hopes to make the Navy his career. Maryk is a fine seaman and a good leader, but not a highly-educated manhe is somewhat in awe of Tom Keefer’s intellectual attainments.

In repeated conversations, Keefer tells Maryk that the captain must be mentally ill, using psychological jargon and concepts that Maryk does not pretend to understand. Maryk is concerned enough about Queeg’s behavior that he begins keeping a “medical log” on Queeg, with the idea of presenting this to higher authority if necessary and possible.  The time seems right when Caine shares an anchorage with the battleship carrying Admiral Halsey:  Maryk takes his log, takes Keefer in tow, and heads over to the New Jersey to see if they can speak with the Admiral.  But Keefer, at the last moment, chickens out, asserting that Halsey, with his experience aboard large well-managed ships, would never be able to understand the state of things aboard a hoodlum-navy ship like  Caine, and that raising the issue with him would only get the two of them in trouble.  Feeling unable to make the case without support, Maryk gives up on talking to Halsey and the two officers return to Caine.

But soon thereafter, the old ship encounters a typhooon. Fleet course is 180 degrees, due southaway from the windand Queeg refuses to adopt the safer course of heading into the wind even though communication with other ships, as well as radar contact, has been lost.

An unbelievably big gray wave loomed on the port side, high over the bridge. It came smashing down. Water spouted into the wheelhouse from the open wing, flooding to Willie’s knees. The water felt surprisingly warm and sticky, like blood. “Sir, we’re shipping water on the goddamn bridge!” said Maryk shrilly. “We’ve got to come around into the wind!”

“Heading 245, sir.” Stilwell’s voice was sobbing. “She ain’t answering to the engines at all, sir!”

The  Caine  rolled almost completely over on its port side.  Everybody in the wheelhouse except Stilwell went sliding across the streaming deck and piled up against the windows.  The sea was under their noses, dashing up against the glass.  “Mr Maryk, the light on this gyro just went out!” screamed Stilwell, clinging desperately to the wheel.  The wind howled and shrieked in Willie’s ears.  He lay on his face on the deck, tumbling around in salt water, flailing for a grip at something solid.

Read more

A Truly Courageous Business Decision

Today marks the 55th anniversary of IBM’s announcement of the System/360 line…which made obsolete virtually all of its then-existing products.  The 360 line established a common architecture for machines of widely-differing price and performance characteristics, with the individual product implementations of this architecture differing considerably.  The goal was compatibility, so that customers could upgrade without extensive rewriting of programs.  Consolidating IBM’s diverse computer systems into this single system architecture was a bold decision; truly, a bet-the-company decision: in the end, it paid off, with devastating consequences for the ‘Seven Dwarfs’ who were IBM’s competitors at the time…but the implementation was frighteningly stressful.  A good article on the project recently appeared in IEEE Spectrum.

Tom Watson Jr, who ran IBM during this time period, discusses the 360 project extensively in his superb memoir, Father, Son, and Co.  I reviewed it here–highly recommended.

The 737 MAX and the Death of MIL-STD-499A SYSTEM ENGINEERING MANAGEMENT

One of the life experiences that comes with being a three decade veteran of military procurement is you have been around long enough to know where all the important bodies are buried — case in point, the Boeing 737 MAX.   What we are seeing in the two recent 737 MAX crashes is the the 20 year accumulation of professional toxic waste and decay in Boeing management that came with the first Clinton Administration’s cancellation of MIL-STD-499A SYSTEM ENGINEERING MANAGEMENT.

737 MAX Jetliner in South West Airline Colors.

I was e-mailed a link today to this Daily Kos post on the 737 MAX :

Did Boeing ignore basic SW engineering principles?
Thursday March 21, 2019 · 8:34 AM CDT

and this passage just jumped out:

A few software engineering principles:

  • Software engineering 101: validate your inputs.
  • Software engineering 201: when something goes wrong, provide useful data to the human.
  • Software engineering 301: for life-critical decisions, avoid single point of failure.

Until today, I had thought that aviation was *good* at software engineering. But my faith is shaken by the New York Times description today of what went wrong with the Boeing 737 MAX.

The above passes my professional “Bozo Test” of whether the poster knows what he is taking about regards software development.   He does.

This is where that “military procurement life experience” I mentioned comes in.   The timing of the development of the 737 MAX MCAS software was roughly 20 years after the Clinton Administration cancelled the majority of Mil-Specs in the mid-1990’s and in particular the one for system engineering management.

See:

MIL-STD-499A (NOTICE 1), MILITARY STANDARD: SYSTEM ENGINEERING MANAGEMENT (27 FEB 1995) [NO S/S DOCUMENT]., MIL-STD-499A (USAF), dated 1 May 1974, is hereby canceled without replacement.

Read more