Blog
Comment
vapats
WKetel
The time between a request for something and the time it must be in-place and ...
Silicon Valley Nation: Five engineering lessons from race teams
Brian Fuller
9/13/2012 5:07 PM EDT
Automotive engineers working for race car teams must have the greatest jobs in the world. Not only do you get to pursue your craft working on bleeding-edge cars, but the community is close and there are a lot of beautiful people milling about on race weekend.
Much can be learned from race engineers that can be applied to other engineering disciplines. And we'll learn more this weekend (Sept. 14-15) when we venture to Fontana for the MAVTV 500 and another in the Littelfuse Speed2Design racing events.
[Get a 10% discount on ARM TechCon 2012 conference passes by using promo code EDIT. Click here to learn about the show and register.]
[Learn more about the Indy 500 at the Littelfuse Speed2Design site.]
Here are five lessons we've gleaned from auto racing:
- Listen to the ecosystem: Some engineers work in leading-edge applications (racing, aerospace, consumer). But it's important to remember that no matter how sophisticated your technology, there's something more sophisticated somewhere else that may be relevant to your design today or trickle down (in cost) to you tomorrow. That's what we learned chatting with Rahal Letterman Lanigan Racing chief engineer Jay O'Connell.
- Facing barriers, don't give up: O'Connell's team,
racing BMW cars, is so good the American LeMans series leadership
penalized
them 5 percent during the 2011 season to give other
teams a fighting chance. The Rahal Letterman team still won the
season.

- Keep it simple: Often, the best solution is the simplest. Mechanical engineering Mike Held working with KV Racing recalled how he helped build a simple solution for racing legend Rick Mears.
- Think different: The best engineers pay attention to changing standards and regulations and leverage them faster than competitors who may be tradition- or hide-bound. Mechanical engineer Mario Illien, a legend in racing circles, regaled us with a tale of how he and Roger Penske teamed to shock speed freaks in the early 1990s.
- Get very close to your customer: Racing engineers, obviously, are almost literally attached at the hip to their driver-customer. That enables relentless learning and constant refinement, as we learned from Arie Luyendyk. It's easy to forget or to underestimate that feedback loop in engineering disciplines where the engineer-customer bond is looser.
Related stories:
--Dream engineering job?
--The racer's edge
--Limiting innovation
--Innovation in racing helmets
--Engineering mischief and a legendary racing shocker
-- To driver Arie Luyendyk, it's about engineering and racer's edge
--Littelfuse Speed2Design project
Navigate to related information


WKetel
9/16/2012 4:16 AM EDT
The time between a request for something and the time it must be in-place and functioning correctly is brutal and unforgiving in the racing field, because the race starts even if you are not ready. So if some need is found during the Friday warm-ups and the Saturday race, the time to engineer, design, build, debug, and install a product is sort of limited. But it is a thrill to be part of a winning team.
Sign in to Reply
vapats
9/19/2012 9:39 AM EDT
That's a darn good set of lessons.
Sign in to Reply