Professional Documents
Culture Documents
PM Engineers
PM Engineers
1.0 Introduction
The engineering design process is a series of steps that engineers follow to come up with a
solution to a problem. While designing a simple two gear gearbox may be easily accomplished
by an engineer and may not require as much planning more complex engineering problems
may require a more systematic approach.
For you are asked to design a variable speed gearbox for a client. Your boss asks you to oversee
construction and take up technicians and junior engineers in your team as well and you have a
very short time to do all this. You may be a good engineer but if you try to do everything
yourself you will find it difficult to complete a design project.
Just like any other project, engineering design projects require carefully planning and continuous
monitoring. In this topic, we will learn:
Lets look at some projects which failed due to mishaps during design stages. Remember in most
design cases many innovative components are new and untested. There is a large scope to get
things wrong. We have a lot to learn from failed projects.
"The 'root cause' of the loss of the spacecraft was the failed translation of English units into
metric units in a segment of ground-based, navigation-related mission software, as NASA has
previously announced," said Arthur Stephenson, chairman of the Mars Climate Orbiter Mission
Failure Investigation Board. "The failure review board has identified other significant factors
that allowed this error to be born, and then let it linger and propagate to the point where it
resulted in a major error in our understanding of the spacecraft's path as it approached Mars.
2.) VW Emission Software: Emission regulation project went wrong when lab tests did not
account for real scenarios and cost VW as much as $18Billion in losses.
3.) Sinclair C5 car: Roofless car designed for rainy English weather lead to eventual closure
of the company.
There are many design failures. These failures have ended up in costing money, time and even
lives.
Is it that the brilliant engineers in this project made a mistake?. Why was such a failure caused?.
How can a basic error have been overlooked in the Mars Orbiter case ( and that too by rocket
scientists ). Has any of your projects ever failed? (Lets be very honest).
Take the example of the Variable Speed Gearbox project . Suppose your manager asks you to tell
him how long the project will take? How do you determine the length of the project? Do you just
take a guess?
While it is useful to look at the different stages in a project first, we will skip that for now and go
straight to the project planning stage. Once your project is initiated, a project scope document is
made. The scope document or charter defines the scope of the project and marks a boundary
around what has to be done. It also notifies stakeholders of what is not part of the project.
The project scope contains the objectives or deliverables of the project. The deliverables are
what the project must deliver. Once you have listed the key deliverables of the project then you
have to work downwards to determine what all sub level deliverables are needed to achieve the
key deliverables.
Remember a task can be further divided into subtasks. Each piece of work in the project needs to
be broken down into smaller pieces all the way to the most basic level in order to determine the
number of tasks as well as the time for the project. This is useful because while it may be hard to
determine the duration of a complex project, it is easy to determine the duration of subtasks that
make up the project.
This breakdown of tasks into smaller components is technically termed as Work Breakdown
Structure (WBS).
Using WBS we can break down a project deliverable into tasks, the tasks into subtasks and
further on until we reach the basic level of the tasks.