I do enjoy this blogging thing. Lots of you send me emails or comment in person that you enjoy reading my stuff… which is beyond gratifying! After a few years, though, I sometimes run out of something new to write. Luckily, I’ve just chiseled into a new vein of gold.
It’s never been my job to deeply understand the coding behind the engineering software I represent. I took exactly 1 masters level CFD course in the mid 90s. Yikes. I was pretty much done after struggling to write my own basic, ugly, hardly useful CFD solver. Pitiful.
My job is to look at a potential customer’s design challenge, relate that to some some sort of solution [hopefully, but not always, one I actually sell], and help to uncover the real business case that [hopefully] justifies the investment in said solution.
Most of the time, all of that information has to be packaged in such a way that the holder of the purse strings can understand. I guess that’s the other thing I’m pretty good at. Usually these people don’t (or shouldn’t) care about the deep details of the solution technology.
Most drivers can’t point out an alternator under the hood. Does that mean they aren’t qualified to make a car buying decision? Of course not. Explaining the high level benefits of CAE for non-experts has always been one of the guiding goals for my blog. Now that I’m digging more deeply into the rich world of structural analysis, I think it’s time for me to create a series of posts explaining the most common aspects of CAE in the simplest terms possible. I’ll try my best to come up with good “fat man” analogies.
When I first got into engineering simulation, I struggled to explain what I do for a living to civilians- er non-engineers. I’d be at a dinner party and someone would say, “Nice to meet you, what do you do?” To which I’d say, “I’m in engineering software.”
Now, I still recommend this approach at dinner parties…. because a deep discussion of FEA or CFD usually won’t create the desired social atmosphere. But, let’s say the person bites and wants to dig in, “Oh, what does that mean?” Don’t start talking about nodes, elements, boundary conditions, stress, and the like. Say something like this instead:
“Imagine you owned a company that makes plastic chairs. Maybe you want to use thinner plastic to cut costs and make more money. In our software, you could create a 3D virtual reality model of that chair, and simulate putting a big fat man on it. It’ll tell you if the chair will break or not… all before ever trying to build and test it in real life.”
image by zorilla