Become an incredible engineering leader with a free subscription to Engineering Leadership Weekly

Engineering Design Integration

Engineering and Leadership - Engineering Design Integration

Photo credit: Tambako the Jaguar

Engineering design is something I don’t write about nearly enough. Today, I’m going to buck the trend and cover something I feel is really important: designing with the outside world in mind. In engineering, it’s a common problem to design a sub-system, plop it down into the bigger whole system, just to find it doesn’t play nicely with others. Bad times. My goal today is to convince you, dear reader, of how big a problem this is and how to avoid making engineering design integration mistakes in your designs.

Epic Engineering Design Integration Fail

Let me set the scene for you: imagine your boss comes to you and says “Hey, junior engineer! Design me a widget that does these 15 amazing things.” Now, besides the fact that it’s odd that your boss calls you “junior engineer” (your boss really should know your name by now, I would think), this is a totally normal thing to have happen. That’s what engineers do – they design stuff.

So, you run off to your tiny little part of the engineering cubicle farm, and you start plugging away. Life is good. You’re in the zone. You’re deriving equations using Laplace transforms by hand just because you’re awesome. You forget to stop to eat lunch. Simply put, you’re crushing it. Everything you do is pure gold, and you know it.

Finally, you complete your design. You take it to your boss, proud because you’ve delivered each of the 15 features that were asked for. You expect nothing short of an instant promotion and a company car and casual dress code for the rest of your life.

But alas, your boss is not pleased. Not at all.

“This’ll never work!” she says, “How will this fit into the 4 cubic centimetre space we have allocated? Do it again.”

Brutal. Your design does everything it needs to do functionally, but doesn’t meet the constraints imposed on it by the real world and the other systems it needs to interact with. Unfortunately, that means your design is exactly useless.

Engineer fail.

How to Make Sure Your Design Will Integrate

Here are some ideas to help guide your design efforts and to make sure that your awesome designs will actually work in the context of the “bigger picture”.

  1. Decide what the “Bigger Picture” is – Unless you fully understand where your system will be implemented and with what other systems it must interact, you’re pooched. Your system, like any other, must take information/ material/ energy in, and spit information/ material/ energy out. You need to know what format your input will take, and what format your output must be.
  2. Electrical interfaces – are there power or communications interfaces with other gear? What kinds of connectors might you need? What voltage/ current/ power considerations should you be making?
  3. Mechanical interfaces – is your system driving or being driven by another system? Have you chosen the appropriate hardware to mate to this other equipment? Have you considered how your system will mount to whatever it’s being mounted on?
  4. Space envelope– Is there physical room for your system to be placed where it needs to go? If your system isn’t stationary with respect to where it’s mounted (i.e. it “swings”), will there be any fouling up against other stuff in the vicinity? Are your cables and hoses long enough to accommodate this?
  5. Environmental Interfaces – Will your system get hot as it operates? How will that affect the other systems nearby? What about noise and vibration? Will that throw anything else off-kilter? Are there any emissions or waste products that might gunk up nearby systems?
  6. Get Buy-in – You need to work in collaboration with the other people on the greater design team – especially on the interface. Once you and the other relevant designers have come together to decide how your systems will integrate together, you must abide by the 1st commandment of engineering integration: Thou shalt no make changes to the way you interface with other subsystems. Why? Because that’ll screw up the other people’s systems, which is timely, expensive, and grounds for evil glares.

Take Action

Now that I’ve shared this with you, I challenge you to dig deep in your next design project and think hard about how you can design your system to play well with others.

If you have other tips, like what you read, or hate what you read and really want to tell me, please do! Just use the comments section below. I promise to respond to every comment.

Have your say

2 Comments

  1. Erica Lee Garcia

    Awesome post, Pat! Especially #6 on your list is something that engineers do not do nearly enough of. I know that when I first starting working I thought that if I just did my work (i.e. covered #1-5) as perfectly as possible that everything would be all right! hahahaha So funny!

    In the real world, people change their minds, they forget to tell you things and they don’t care how long it took you. So it’s best to get input early and often as you go, much as your pride might like to unveil a perfectly finished design without anyone’s help.

    I’d also add useability/Human Factors (if applicable) and maintenance/replacement requirements as two more design parameters that tend to get overlooked.

    Figure out how to cost-model these parameters and communicate the tradeoffs effectively and you’ll have your boss’ job in no time! :)

    Reply
    • Pat Sweet

      Hey Erica!

      Really glad you enjoyed! I had a design prof who used to hammer #6 home at least once a week – totally critical stuff for sure.

      Also, great additions! Really appreciate your input. Maybe I’ll write another article tackling those ;-)

      Thanks again! Glad to see your site is up and running too!

      Talk soon,
      Pat

      Reply

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

October 24, 2012

By Pat Sweet

Pat is the president of The Engineering & Leadership Project. He's a recognized expert in leadership, project management, systems engineering and productivity.

Free Leadership eBook

Engineering Leadership 101

Practical Insights for Becoming an Engineering Leader at Any Stage

Free Subscription

Engineering Leadership Weekly

Become a next-level engineering leader

You may also like…

Why Clarity is the Secret to Great Communications and Stronger Teams

Why Clarity is the Secret to Great Communications and Stronger Teams

Dolores Hirschmann believes that clarity of message is critical to effective leadership. A leader’s team can’t buy in to a vision without first understanding it. In today’s episode, Dolores helps engineering leaders understand the importance of clarity of message, how to tell if your messaging is clear, and provides practical steps on how to improve your communications.

read more
EL040 – How to instantly make your meetings shorter, more productive, and less painful

EL040 – How to instantly make your meetings shorter, more productive, and less painful

Meetings are a fact of organizational life. The fact that so few of us have ever been trained to run excellent meetings is a bit of a shock. We all know they’re needed, and we all know they’re mostly painful and wasteful. If you follow even a few of the ideas in this episode, you and your team will be more engaged, efficient, and effective in your work.

read more

Pin It on Pinterest

Shares
Share This