Monday, March 31, 2008

The Cost of Wind Tunnel Testing vs. Upfront CFD

I have written many times that I am a huge fan of Desktop Engineering Magazine. There was an interesting article recently on Conceptual Design. It is my favorite type of article. They poll four different representatives from four different vendors (Rhino, SolidWorks, Siemens & Autodesk) and ask a variety of questions to see how each tool responds to demands of the market.

The article was near and dear to my heart. Conceptual design is something I live and breath everyday. Each rep from the various vendors had some really cool and unique views of where their products add value in the conceptual phase of design. I came across the following quote and almost fell out of my chair.

“For example,” he says, “wind tunnel or tank testing often is not all that expensive [when] compared to setting up and running CFD analysis. It is often easier to make the design iterations by playing around with a handful of clay and turn the wind tunnel back on, than it is to change the computer model and rerun the CFD analysis. But structural analysis of a large building design has to be done virtually. Physical analysis is economically impossible.”



It is interesting how many people share the same sentiment. The fact is there are only few instances where this may be the case. I was talking to an engineer at a very well-known valve manufacturer about this and he shared a few numbers with me.

He was designing a brand new line of poppet valves. He was responsible to ensure the pressure drop was within a certain range, as well as determining the spring needed to maintain stable flow over a wide range of flow rates. His ultimate goal was to have three prototypes (3 different sizes) ready to be outsourced for final physical testing. I asked how much were the outsourcing costs? $8k for three...whoa! Seemed steep to me, but I am all about virtual reality, I suppose.

So, let's say you didn't perform an Upfront simulation of the model and your three original designs were not up to snuff. So, you had to re-do the prototype testing. You have just justified the $$ for an Upfront CFD tool. But this is really just the tip of the iceberg. In reality if you had the simulation tool in place you could confidently pay for one round of validation testing at the end of the design cycle. But, more importantly, the simulation models would allow for innovative design that is not possible in the physical testing world. You aren't able to get in there and peel things away to see inside where the action is happening in a wind tunnel. You are limited on the data available and you induce inaccuracies with the measuring devices.

So, back to the article at hand. I think I understand where the guy was coming from. In the past, CFD was the big gorilla in the room. Everyone was afraid to go near it. It was too "expensive". Things have changed drastically over the years. More and more everyday. Whether its a wind tunnel, a flow bench or a thermal chamber or even a thermal camera, there are significant investments of time and materials required.

My friendly advice is to fire up Google and do a search for Upfront CFD.

Pre-Earth Day Field Trip in Philly

Philadelphia is a great urban setting with alot to offer. One of the greatest aspects of living in the city is having access to Fairmount Park. It gives us city dwellers a chance to step out and enjoy nature. Although today was a pretty miserable rainy day, the BRNI Philly Office took an early morning field trip. Below are my long time office mates.

After literally 100s if not 1000s of CFD conversations that they have endured, it's only fair to take them along. Entrance to the park is a few blocks from my house. Once you enter it is literally like walking into a different world. There are hiking and bike trails everywhere. They all border the Wissahickon Creek (pronounced "crick" in Philly). The main drag is called Forbidden Drive.

It is one of my favorite spots in the world. I keep meaning to take a camera along to snap some pics, but just can't seem to get it together. Now that the weather is breaking, I plan to spend a considerable amount of time exploring the trails with my crew. The plan is to start taking some pics and posting them here.

Thursday, March 27, 2008

SolidWorks Acquires CircuitWorks

It definitely took long enough. I started using SolidWorks about 10 years ago, SW98. They were the newest and hottest thing to hit the CAE market and they were a super aggressive sales machine. They could do 70-80% of what the big boys could do and everything else they signed up partners to complete the whole package.

Seemed like everyone scrambled to become a "gold partner" (fully integrated into the the SW GUI). It also seemed like a mad scramble to get "....Works" into your name before the next guy. So, there was CosmosWorks, PDMWorks, CAMWorks, DriveWorks, FloWorks etc.. Over the years, SW slowly just acquired the best (I guess) of the partners and offered them direct. Not exactly sure how the other Partners feel about that, but whatever.

So, low and behold there was CircuitWorks from PriWare. Cool little plug-in that can translate ECAD data to MCAD data with a click of a button. Worked pretty slick. You could even have much more sophisticated parts in a library and the actual capacitor would be called out etc.


I wonder if PTC's big fuss about ECAD integration in WF4 had anything to do with the motivation to acquire Priware? Not sure it matters.

As a current SW user and a guy that supports SW users, I am thrilled that they can now gain access to their ECAD data as part of the core license. Especially for people that are doing electronics cooling. You just made our lives easier. Thanks!

Saturday, March 22, 2008

Upfront CFD is Much More than Just a Pressure Drop

One of the major benefits of my job is visiting companies all over the world from various industries. Although I am excited about our product and services, my favorite part of the meeting is when I am granted a tour of their facility. It never gets old to walk around and get a view of the inner workings of a prospective customer. It's like being a kid in a candy shop. Fellow engineers are super proud of what they do and get really excited showing off their designs. I get to ask a 1000 questions and learn a great deal about the challenges that companies face. The challenges are all very similar from a fluid flow and heat transfer perspective, even though the industries are quite different.

We typically get back to the conference room and now its our turn to show off how we can help their business. I love showing off our software. It is super visual and we can create really cool images that show some valuable insight that is impossible to capture in a test facility. The audience is almost always super receptive to the demo and usually have some really interesting questions. So, we go through and  show all of the various ways to understand the fluid flow and thermal characteristics of a representative model.

After a round of high-fives (not really), we get down to business and discuss how to move forward and implement Upfront CFD into their current process. A common question I ask is, "if you had an Upfront CFD tool right now, what is the first thing that you would want to simulate?" More often than not, a common response is, "we have this new design and we would love to know the pressure drop (deltaP)". This is usually followed by an awkward silent pause. Hmm...all the cool stuff that I just showed and you want a deltaP. I think it has to do with a certain comfort level. The deltaP is a common thing they get from physical testing, so they can relate to that value. We can absolutely provide an accurate pressure drop on your device. 

But once you determine the deltaP, then what? There seems to be a disconnect between the fluid flow characteristics and the pressure drop. But in fact, these two are obviously dependent on one another. If you optimize the flow characteristics, you can optimize the pressure drop. So, what does that mean? If you eliminate recirculation regions, reduce separation points and control the impingement regions, you can reduce the pressure drop. How can you do this with physical testing alone? Once you compute the pressure drop, how do you know what to change?

Proof is in the pudding -let's look at an example. We'll keep it simple.

 

CAD

We take the model directly into CFdesign and apply "what we know", let the software automate the rest and click GO! Let's see how we can optimize the design.

cfd1

iso

cut1

Okay, so I am have a great time with Snag-It. But the point is that Upfront CFD gives you so much more insight to your designs than just a pressure drop value. The key to Upfront CFD is that you get the Pressure drop value, but more importantly you are now in a position to improve the design based on the knowledge that you have gained. Upfront CFD allows you to innovate, testing is there to validate. Based on what we have learned above, we need to reduce the pressure drop and attempt to "even out" the flow field in the area of the valve stem. The original design had 4 cut-outs, "what-if" we increased that to 8, 12, 16 - even 24? Let's make the change and find out.

design2

But what impact does the 24-slot design have on the overall Pressure Drop? Let's compare.

dp

We can plot the pressure drop and make an apples to apples comparison. We see that the final design satisfies all of our criteria. We were able to reduce the force on the valve, ensure that the flow is uniform in the vicinity of the valve stem and reduce the overall pressure drop of my system. I was able to do this in the course of a couple hours today. I ran 5 different "what-if" scenarios and compare. Upfront CFD not only gave me my pressure drop, but it allowed me to see from every angle what impact my design change was having on the performance.

Monday, March 17, 2008

My "defining moment" to Become an Engineer

Do you remember the point in your life where you decided that you wanted to be an engineer? Are you one of those guys that knew all along? I am amazed at how many fellow engineers knew all along that they would choose a career path in engineering. At least on the mechanical side, a good majority of folks start tinkering with cars in their teens so mechanical engineering is a likely path to choose. If you knew engineering school would be so difficult, would you choose it all over again?

I never in a million years thought I would be an engineer. I wasn't the stereotypical engineering kid. I'm not sure what that really means, but I think we all have a similar mental image. I always did fairly well in school, but never had the drive or the quest for knowledge that I have developed as an adult. I was never all that into cars, not really a hobby kind of person. So why choose engineering?

A great term was brought to my attention a few months ago by a co-worker. We were talking about a different topic and he was explaining a scenario where a customer of ours had a "defining moment". It was that point in time where something "clicks", you come to a conclusion or some sort of agreement. Great term, actually. So, my defining moment to become an engineer happened in my early twenties.

I came out of high school and wanted to enter the medical field. I attended a year of nursing school and quickly realized that school was not for me at the time. So, I picked up and joined the Navy. A very typical thing for me at the time to simply make a decision and act. I am not so much like that anymore. So, off I went to boot camp and later submarine school. Why submarines? Well, they paid more. No other rationale than that.




As with everything in my life, I am drawn to the people, not the project. Over the course of many months, I asked the engineers 1000s of questions. I learned more about the people than I did the job. All of the engineers that I worked under were either mechanical, electrical or nuclear. They all attended nuclear power school and were certified to monitor and operate the nuclear reactor on the sub. So, believe it or not, I had the idea that I would be a nuclear reactor operator when I got out of school. Way too many rules and regulations in that field for me. But, it kick started me off into a new world. As time went on, there was another defining moment that pushed me into the world of CFD, but that's for another time.

I am interested to hear other's stories about their journey into the world of engineering.

Friday, March 14, 2008

VOIP: Skype vs. Yahoo! Voice

I am a bit obsessed with being connected and being able to communicate with anyone and everyone. I prefer instant messaging (texting) over email. I tend to use email for longer term things, where it may take some thought or where I do not need an immediate answer. But let's face it, I can be an impatient person. Most of the time, I need (want) an answer immediately.

I have written in previous posts about using MS Communicator for work and using Yahoo Messenger for everything else. But, recently I started using Skype to communicate with some friends and co-workers outside of the US. So, it may seem insane to use three separate messaging programs. But, each has features I like and I tend to use them based on what the person on the other end is using.

I have been using VOIP quite a bit lately. I have always used Yahoo Voice to call home when I am traveling outside of the US. But, I have been using Skype now to communicate for work. It is really convenient. I would love to be able to ditch my office phone (landline) altogether. I am almost always connected to the internet and when I am not I can be reached on my mobile phone. It is just much easier to have it all in one place. Skype has some really cool tools where you can quickly make calls on the fly.

So, why can't I just ditch my landline? For starters, I use Webex quite a bit and there are some bandwidth issues when using Webex and VOIP. Things are improving but still not perfect. There are some other issues as well.

YAHOO

+'s of Yahoo Voice

  • $0.01/min to call the US & UK regardless of where you are calling from, this is half of Skype

  • A fraction of a cent more to call France and Germany

  • For $2.50/month I have a local (Philadelphia) phone number that anyone can call and will ring at my computer

  • If I am away from my computer and receive a voicemail, it emails me an audio file which I can check on my phone or laptop

  • I can forward my office phone to my Yahoo # when abroad. Otherwise, I would have to pay long distance to check voice mail or receive forwarded calls.

  • My Yahoo # appears as a Caller Identification when I am calling landlines or mobile phones.

-'s of Yahoo Voice

  • There is no unlimited US calling. So, even though calls are $0.01/min, I would like the option to pay a monthly flat rate to call unlimited in the US. So, pretty much a show stopper for ditching my office phone.

  • The interface is a bit awkward when dialing landlines and mobiles

  • Not as accepted as Skype internationally

skype

+'s of Skype

  • Solid interface

  • Really cool tools built in to identify phone numbers in emails and websites to call directly

  • You pay $3/month for unlimited calling to US/Canada

  • $0.02/min to call internationally (twice that of Yahoo, but still cheap)

  • You can get a phone number for non-skype people to call you for $20/year

  • Call forwarding capability

-'s of Skype

  • They do not have caller id in the US when calling landlines and mobiles. This is essentially a show stopper for replacing an existing landline for business as people rarely will answer from an "UNAVAILABLE"

  • AMEX is not an accepted form of payment

  • If you use a VISA credit card, you are limited to $30/month. You have to use other forms - Pay Pal etc to get more. Apparently, that changes the longer you use it.

  • Skype mobile is still in its infancy in the US

So, because I am a geek for this type of stuff, I use both. So far so good. I would love to find a product that would do it all. The two show stoppers above would make me a dedicated user and huge evangelist for their products. Not sure anyone from Yahoo or Skype is reading? If so, hook me up.

Tuesday, March 11, 2008

Big Moutains to Climb in Germany

I just returned from a trip to Garmisch-Partenkirchen, Germany. It is about an hour outside of Munich. Great little ski town. They take great pride in the fact that they were the host of the 1936 Olympics. Seems like along time ago to me, but nonetheless, they are proud.

I spent most of the time in meetings, but was fortunate enough to walk around for a bit. We also had some fantastic Bavarian meals in some of the authentic restaurants in town. I also snapped a few pics. Check out the image below. I was in awe of the shear size of the moutains. Sure, we have the Rockies in the US, but they seemed small in comparison. I found it interesting that some of the people in our meetings shared the same sentiment about the moutains, others seemed mildly impressed. I guess it all depends on what you are used to?

It is great to have the opportunity to meet German companies and understand their processes and challenges. They do business slightly different and definitely take great pride in their engineering. But many German engineers relate to the benefits of Upfront simulation. It is exciting to show people how to approach fluid flow and thermal challenges in an Upfront way. I am looking forward to my next trip to learn even more about this fascinating place.

Sunday, March 09, 2008

You Must be Committed to Implementing Upfront CFD

We in the vendor world are committed to our products and services. We take great pride in our capabilities and we strive to provide first class support and training to ensure that our users are successful. Let's face it, a major part of our day is focused on ensuring that our customers are gaining a return on their investment. I take full responsibility on transferring the knowledge it takes to implement Upfront CFD into your current process.




So, if we assume that all vendors have a similar passion in their products and services, why do so many engineers have so many CAE products sitting on their shelves? I live by the statement, that "the customer is always right". But I do expect that the customer is willing to first identify a problem and be open to working together to formulate an implementation plan, but most importantly, the customer has to be committed to the implementation of the plan. Seems like a simple concept, right?

It has been my experience that the customer and vendor have to have a solid relationship and absolutely have to be on the same page regarding the implementation. This is where selecting the correct vendor is essential. Ease of use and the laundry list of features are a given. But as you shop around, you will quickly see that everyone will claim to have essentially the same "laundry list".


What you need to ask yourself, "do I have confidence in the team that I am about to partner with"? Do they have the support infrastructure to help me when I am stuck? Do they understand my business? Do they understand my problem? But most importantly, do they know how to teach me to solve my problem?

Being committed to the implementation is your job. Formulating a clear implementation plan that teaches you to solve problems with our tool is our job. Don't be afraid to ask the tough questions. Whether or not a vendor can match your test data is really irrelevant. Given the correct inputs, every vendor will stick their "Ace" user on it and present really fancy images. The real question is how will the vendor transfer the knowledge to you the user so that you can seamlessly begin solving problems?