Comments by "Tony Wilson" (@tonywilson4713) on "What's Going on With Shipping?"
channel.
-
49
-
30
-
27
-
24
-
15
-
14
-
11
-
10
-
10
-
7
-
7
-
6
-
5
-
5
-
5
-
ENGINEER HERE: And I would love to come on your channel and discuss the issue of LESSONS LEARNED because across the entire world of engineering that is a monster issue that is NOT BEING ADDRESSED.
FYI - I started with a degree in aerospace engineering but landed in industrial control systems and automation. That's a highly transportable skill set as almost every industry has computers with sensor connected to them and they run software to read those sensors and control things - power stations, manufacturing plants, mine sites, water treatment plants, traffic lights,...... and many other things. I have mostly worked in manufacturing and mining, but also have experience in water treatment, waste processing, oil & gas and power stations.
Time and time again I have watched people make the same mistakes on projects after projects. Lessons are NOT being learned anywhere. Maybe on of the few times I saw it done well was when Colin Powell and others decided NOT to repeat Vietnam. Out of that came the Powell Doctrine, which I first heard about on a PBS Frontline documentary called "Rumsfeld's War." In it a General summarised it as having 4 key questions.
What is the task?
What are the required in manpower and machinery?
Do we have the absolute support of the American people?
When the job has to be done by?
When that was used there was Gulf War 1 it was over in a month with its main objectives achieved - get the Iraqis out of Kuwait and make sure they can't come back. They pushed the Iraqis out of Kuwait and they had that famous battle where the Americans shot up all their trucks as they fled. By destroying all the trucks they removed the Iraqi capability to move anything around and armies have to move.
When I first heard the Powell Doctrine explained it struck because it applies to ALL ENGINEERING PROJECTS.
You have to start with a clear specification.
You have to resource the project properly with money, men and machinery.
You have to be in agreement that the solution is going to work.
You have to have a firm date on when it has to be done and what it means to be done.
If you look at the Apollo Program easily the most successful engineering project in history it had all those 4 things in place from the start.
Land a Man on the moon and safety return him to the Earth.
You have all the money, men and machinery needed.
The American people said they agreed.
The date was set -> end of the decade.
Note that by the end of the 1960s Americans had been to the Moon 4 times (Apollo 8, 10, 11 & 12) and landed twice (Apollo 11 & 12). Further the technologies developed and then made available to American industry had paid via taxes back to the American people around $9.50 for every dollar spent on Apollo by the late 80s. That was the conclusion of an independent report commissioned by the AIAA during the aftermath of the Challenger disaster as people tried to get NASA abolished.
This is NOT taught to engineers at all and EVERY project I have ever been on has missed at least 1 of those things. You'd all be amazed that engineers are NOT taught anything about project management in college. Yet this concept that Colin Powell came up with is so simple and it was based on LESSONS LEARNED from Powell's experience in Vietnam.
AND YES when they threw it away as Rumsfeld and others did for the Invasions of Iraq and Afghanistan they both went tragically wrong and the effects of which we'll have to deal with for decades to come.
AND YES when NASA has had projects with a lack of specific goals they have had issues like the Space Shuttle, like the Space Station and like the Launch systems meant to replace the Space Shuttle.
So when you talk about LESSONS LEARNED its a much bigger issue than a broken wharf in Gaza.
5
-
4
-
4
-
3
-
3
-
3
-
3
-
3
-
3
-
3
-
3
-
3
-
3
-
2
-
2
-
2
-
2
-
2
-
2
-
2
-
2
-
2
-
2
-
2
-
1
-
1
-
1
-
1
-
1
-
1
-
1
-
1
-
1
-
1
-
1