Anyone who has been in the business for more than five minutes understands that the rate of change in electronics hardware development can sometimes be overwhelming. Just this year at the University of Michigan, a team has developed the world’s smallest computer, measuring just 0.3mm to a side, smaller than a grain of rice.
Running production operations is a daunting task for manufacturers. You want your operations to be highly productive, flexible with the changing needs of customers, and to run efficiently. At the same time, you want to develop ways to reduce process costs without reducing the quality of works-in-progress (WIP) parts or finished contracted products.
Every year, post Labor Day, most of us are focusing on getting “back to work” and recovering from whatever the summer holidays brought our way. As the weather starts to cool, and the sports start to change, those of us who work in supply chain management, procurement, and shipping immediately turn our eyes to what has become the constant fourth quarter challenge: getting our companies through peak season with no delays or surcharges.
At Epec, engineers are expected to find innovative solutions to problems and develop them quickly and accurately so that customers can get quality product delivered on time. In this blog post, I will discuss how the 80-20 rule can be used in conjunction with our classic engineering design process to reach solutions faster.
Maybe you have heard of technical writing before, or maybe this is your first-time hearing about it. The chances are good, however, that you have seen or experienced technical writing already in your life. It is an established practice within the industrialized world, but what is it?
In my last blog post, I reviewed the 5 why problem-solving method. In this blog post, we will continue this discussion so if you have not seen Part 1, I suggest you read that post first and then come back here.
In my last blog post, Five Why Root Cause Analysis Starts with a Good Problem Statement, I recommended that problem-solving teams develop well-crafted problem statements. This blog post will discuss the best practices for the five why method of root cause analysis.
It's never a great sign of the times when you wake up every day and know you need to check the news before starting work to see what the newest challenges are you're going to have to deal with. Unfortunately, this trend became standard practice within our industry in 2018. Typically, most companies spend their time and money trying to find new ways to speed up service or new products to help their customers. But for most of this past year, it was about working closely with your customers on their existing business to minimize damage from all the new costs that were quickly being added to our industry.
The average American “holiday season” usually begins somewhere around Halloween and continues at a frantic pace through January 1st. For those of us who work in supply chain management, the holiday season has a completely different meaning.
Printed circuit board (PCB) designers often find themselves at odds with their purchasing and marketing departments after a design goes out for bids and comes back with a larger than expected price tag. Once the source of the high cost is identified, the questions fly, the fingers point, and the nerves fray.