This website requires certain cookies to work and uses other cookies to help you have the best experience. By visiting this website, certain cookies have already been set, which you may delete and block. By closing this message or continuing to use our site, you agree to the use of cookies. Visit our updated privacy and cookie policy to learn more.
This Website Uses Cookies By closing this message or continuing to use our site, you agree to our cookie policy. Learn MoreThis website requires certain cookies to work and uses other cookies to help you have the best experience. By visiting this website, certain cookies have already been set, which you may delete and block. By closing this message or continuing to use our site, you agree to the use of cookies. Visit our updated privacy and cookie policy to learn more.
The author of numerous books on project management, Jon has held engineering and management positions at Volvo Trucks, PACCAR and other companies. His quarterly column will appear in March, June, September and December. Email Jon at jon.quigley@valuetransform.com
I am fortunate to have had a lengthy career of more than 30 years. I have held a variety of product development positions, and these experiences have influenced my thinking about how best to get things done.
What is it about running in and saving the day, like in old Westerns, that individuals and companies enjoy? We may say that we would rather not have such drama on the shop floor, but all too often we set ourselves up for it in the end.
The story I am going to relate is true. However, since it is not very flattering, it has been sanitized to prevent finger-pointing. I’m telling this story because you may find yourself in the same circumstances when managing your supply chain, especially one distributed across the globe.
If you have been around for a while, you may recall the "Parts is Parts" commercial from the Wendy's fast-food chain. As bad as the "parts is parts" idea is for chicken sandwiches, it's equally bad for manufacturing.
In an earlier article, we dissected the project scope and explored the work breakdown structure (WBS). The WBS is the disaggregation of the scope into the work products that are required to meet the defined scope. Now, we are going explore setting about doing the work, from a schedule, or perhaps we will not even build a schedule.
Vehicles have become increasingly electrical over the years. This is not just power electronics, but also sensor data, communications and many other coordinated electrical signals. For aircraft or commercial vehicles, wire harnesses can be even more complex with hundreds of interconnection points.
The fundamental start of any project is a scope of work document, which specifies what we want the project to achieve. The project scope may start out broadly described based upon business objectives, but it will become increasingly detailed over time.
Raptor Performance in Concord, NC, designs and manufactures custom electronics for racing motorcycles and automobiles. The company's products are not for hobbyists, these are professional-grade parts.
When I first started my engineering career, I did not know much about configuration management. In fact, my introduction to configuration management was more about what happens when it is missing.