Tag: constraints management

  • When Manufacturing Improvements Have Too High a Price

    When Manufacturing Improvements Have Too High a Price

    key in door lock

     

     

     

     

     

     

     

     

     

     

    Engineering design fiascos – spending thousands to save pennies

    This is a true story. The names have been changed to protect the innocent. It’s meant to illustrate how using constraints-based thinking can uncover the hidden price of cost-cutting projects.

    Several years ago, a friend of mine was working in the quality group at a large automotive company.  We will call my friend Harry for the story.  Harry’s position was to use statistical analysis to determine design flaws from a large data warehouse containing warranty data, recall data and state-by-state accident information collected about the products the company manufactured. This data was used to identify areas where leading indicators could prevent major recalls and point out where engineering might improve products.  Although this effort was important to the organization, Harry thought that there were better ways to move the company ahead faster than looking at data from the past, which in many cases, was a byproduct of compromises in the design process.

    After many years of working in the quality group, Harry decided to contact the CEO of the company.  Harry felt that if they were to look at the issues and conflicts in new product development and in product design engineering, the company would be able to eliminate the design compromises, which led to the negative effects of recalls and warranty costs.

    To Harry’s surprise, he received a response from corporate leadership and from an engineer named Edwin.  Edwin was the Director of Engineering and Competitive Practices for the organization and was responsible for identifying methods or systems that competitors were using, and determine which should be adapted to benefit the company.  Edwin wanted to know if Harry’s recommendation was possible, and arranged a meeting.

    A fateful meeting

    Another colleague with the company and I were lucky enough to be invited to the meeting with Edwin and Harry. The conversation started with questions and answers about the current process for new vehicle design.   We were all interested in learning how new improvements to current models came about in the company.

    Edwin told us that during a new design, his group had little influence on the timeline, which would be handled by some other part of the organization.    So, we asked for an example of how engineers were introduced to this process. Since Harry and I are Theory of Constraints Jonahs (A Jonah is someone who uses the socratic approach to problem resolution), we wanted to understand the baseline for the process and find out what they considered to be a successful project.  We also wanted to learn how they chose products and measured performance.  Edwin told us that the number one measurement was cost savings on an assigned project.

    We were told that the group manager’s annual goal was to reduce component costs on each vehicle, for example, by $0.04/vehicle on a vehicle platform.  In one case, the engineer looked at reducing the cost of the door locking system by $0.01 to $0.02.  If the car is a 4-door, they would hit their cost-savings target over the total of vehicles they made that year.  These goals are typically in the $400,000 to $5,000,000 range across the entire vehicle line.

    An engineer redesigned the door-locking mechanism to reduce the cost of the components in the car — and sold the group’s idea to management.  After some back and forth between various levels of the organization, the project was approved, and design money and resources were budgeted.

    We asked several questions to determine if this was, indeed, a cost savings. Here’s what we learned from Edwin:

    Q: How many door locking mechanisms does the company currently use?

    A: Seven.

    Q: If there is a new design, is one taken out of service?

    A: Not usually; not until it is determined to be obsolete.  Warranty and Service have a large influence on the determination of obsolescence.

    Q: Since this is a door-locking mechanism, will the vehicles that use this new design have to be sent through crash testing to determine if the new device meets safety standards?

    A: Yes.

    Q: More than just the normal yearly testing?

    A: Yes, since it was a change to a safety device, extra testing will be required to ensure the design meets or exceeds standards.

    Q: Do the suppliers of the mechanisms need to fill the supply chain with parts so the new design can be used in production?

    A: Yes, the suppliers would have been working with the design team during the process, so they would know what the supply chain needs to be prepared for production. They are very good about keeping up with the design process.

    Q: With a new design, how often is it ready on time for assembly to begin the new model year?

    A: There are frequent delays for the new model year, and there will have to be some work to change over the new mechanism.

    “I’m sorry, but I do not see how there is any cost savings in the method you described,” I said.

    They answered, “Of course there is, the company saved $0.02 per vehicle!”

    I explained that because the process described added a new assembly, each step represented new inventory to support the new assembly.  Since the old design wasn’t discontinued, the inventory for the old design would not be removed from the system, so no savings there.  If the new design is not ready for the model year changeover, the delay to production can be quite costly, the old parts would have to be used until the new parts are available, and then the old inventory would need to be removed, new inventory added and the assembly line would need training. In addition, the dealership network would have to be notified about when the old style was changed and in which vehicles.  The dealership technicians would also need training on the new mechanism.

    Every step costs

    Every step they took added cost.  Their $0.02 savings was eaten up before they began. In reviewing the entire process, we quickly realized that no one at the company had a holistic view of the process.  Further, they didn’t have any comprehensive information to fully judge the impact of a change upon the system due to the silos and structure of the organization.

    Edwin maintained that because they were measured for the $0.02 cost savings, they only needed to concentrate on that– they did not have any knowledge or responsibility for what the rest of the company was doing.

    I simply said, “I think you are using the wrong measurements.”

    On my way back from the meeting, Harry said, “What do you think is the number one warranty cost for the company?”

    “I don’t know, please tell me,” I said.

    “Door locking mechanisms,” he answered.  “How about in the 1990s?”

    “The same?” I asked.

    “Yes,” he added. “In fact, the number one warranty item since the 1960s has been door locking mechanisms.”

    He went on to tell me that in the late 1980s, the company did a study between its door lock mechanisms and another car manufacturer’s design.  At that time, Harry’s company’s door lock had 13 parts in the design compared to 7 parts in the competitor’s lock mechanism.  Fewer parts are often more cost-effective—as there is less time to assembly them, fewer parts in the supply chain, and simplicity is its own form of effectiveness.

    The company they used for the study was well known for their impressive reputation for quality.  Keep in mind, he said– each new engineer goes through a required training course that uses this comparative study to show the differences between Harry’s company design and the premier competitor’s design.  The objective is to reduce complexity and still provide world class quality.  And, these engineers need to demonstrate that they understand the study and its implications for the company before they are allowed to do any design work.

    “We have been teaching this class for 15 years. Do you know how many parts our current design has?” Harry asked me.

    “I would guess eight or nine?” I looked at him hopefully.

    “No,” Harry sighed. “We have 12 parts in our design and the competitor’s mechanism is now using 6 parts.”

    I didn’t know what to say to that, other than shake my head in dismay.

    Epilogue

    That was 10 years ago.  Since then, there have been several senior leadership changes at the company. And even though that company, like many others, further fractured into a flatter organization, it maintains many of the traditional silos.

    This company eliminated or sold many vehicle lines to preserve cash to strengthen the parent company.  And, after a long and hard struggle, they are again profitable.  The company is making a better quality vehicle today, but the number of recalls is still higher than the global average for the same type of organization.

    Many organizations still focus on cost savings to the detriment of a holistic view of constraints. They base design and engineering decisions on what looks like it will save money rather than the costs of instituting these changes. Next time, we will talk a bit about why erroneous metrics make projects like the $0.02 -savings door lock look good.   Let me know about your experiences with constraints management—or share a story like this one. I’d love to hear from you.

    – Rick Denison

    6.0-Rick How TOC Can Move Your World – and World View                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              

    Rick is the “Dr. Who” of manufacturing operations and logistics. And while Rick doesn’t travel through time, he is adept at leading change – and saving time – in a diverse range of manufacturing environments through Lean manufacturing, Six Sigma, and TOC techniques. Rick’s posts address how demand-driven matters and draws from his background in process improvement, change management, project management, information systems implementation, and profitability analysis.

  • How TOC Can Move Your World – and World View

    How TOC Can Move Your World – and World View

    archimedes lever

    Archimedes once said, “Give me a lever long enough,
    a fulcrum, and a place to stand, and I shall move the world.”
    Learn how production professionals use Constraints Management to meet negativity head – on to manage meaningful change

     

    Here’s the last part of our three-part series about the Theory of Constraints (TOC). In the next couple of postings I’m going to dig right in to looking at what actually happens when I’ve used TOC at client companies. But there’s more gold to be mined from this topic—and I wanted to make sure I included in this series some common “fulcrums” –or common organizational assumptions that might sound familiar to you.

    I also want to clear up some of what you might think. A common notion about constraints as they are viewed as a “negative.” However, constraints are neither good nor bad; they are just part of any organization. To clarify, try and picture an organization that has no constraints. What would you expect to see from this type of organization? The organization would produce with unlimited growth. In nature and in business, there aren’t any systems that produce at unlimited capacity and exhibit unlimited growth.   So if there are no systems that produce at unlimited growth, then all systems have constraints.

    As people working in systems, we can either acknowledge or deny that constraints exist. Regardless of the choice, constraints will have an effect upon the organization. If we want to grow our organization, then we might as well pay attention, right?

    Too Many Places at Once

    In my last blog posting, (Which Systems is More Complex?) I discussed the complex view of organizations, with the belief that change is incremental. Many changes will equal organizational improvement.

    For contrast, I also discussed that with TOC in that there is only one or very few true constraints within any system. Improve the constraint, and you will make a significant impact upon the system.

    What if you do not have a method to find the weakest link? Random chance allows that every once in a while, one of these actions will touch an organizational constraint and generate an impressive single-event, a growth-oriented action. The opposite might also happen: The same random choice may damage a constraint and produce a single, one-time negative result. If you think about the last 20 years of organizational history, I’m sure you can find a few such cases of one or the other, but more likely the latter. These events will be on the scale of urban legends within the organization. Like New Coke in the 1980’s, a disastrous merger like Daimler/Chrysler, or spinning off acquisitions to conserve cash.

    The Cost Conundrum

    Traditionally, most improvements are efforts to save cost. People think that if cost is removed from the delivery of a product or a service, it will result in higher profits. The vast majority of the U.S. Economy believes this to be true, and that, in conjunction with the high affinity for innovation, creates a compelling mix. But when we compare TOC with other improvement methods, its speed and accuracy bring about significant change – faster. We find our constraints and then we can react.

    The TOC View of Problems

    Traditional view: “A problem is something I don’t like”, or “Something that bothers me”, or the classic “Something that keeps me up at night.”

    TOC view: “A problem is a conflict that prevents a system from reaching its desired objective.”  With this definition, there is a second fundamental belief in physics that “There are no conflicts in reality.”  There are only invalid assumptions about the conflict.

    Assume Control

    TOC translates conflicts as follows: If there is a conflict, then there must be an underlying assumption about that system that created the conflict.  The solution comes from identifying the assumptions about the conflict, validating the existence of the assumptions, and eliminating the negative assumption about the conflict so that a solution can be built that will allow the system to reach its desired objective.

    In every organization, managers face many issues on a daily basis. Typically, most of these issues stem from a single core problem (conflict) that the organization hasn’t been able to previously identify. Many managers are aware that these conflicts exist, however, these type of conflicts are very difficult to solve as most have conflicting objectives that result in compromises.

    Does this sound like you?

    The existence of conflict can be validated by looking back in time for periodic shifts in organizational philosophy. As an example, if in the past, your organization was emphasizing centralized management and now it is emphasizing profit-center autonomy, then these switches indicate the existence of an unresolved core problem. Efficiency is another example of an unresolved core problem. If at the beginning of any reporting period, organizational efficiency is emphasized, and then at the end of the month, all the rules are broken (forgotten) to achieve shipments and revenue targets. This again is a sure sign of an unresolved core problem.

    TOC has a number of system tools that tackle the “new normal” head on. Next time, we’ll look at these tools as they applied to an automotive manufacturer—we’ll uncover their core assumptions and watch how their teams took control with TOC.

    – Rick Denison

    6.0-Rick Which System is More Complex? The Answer is Simpler than You Think                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              

    Rick is the “Dr. Who” of manufacturing operations and logistics. And while Rick doesn’t travel through time, he is adept at leading change – and saving time – in a diverse range of manufacturing environments through Lean manufacturing, Six Sigma, and TOC techniques. Rick’s posts address how demand-driven matters and draws from his background in process improvement, change management, project management, information systems implementation, and profitability analysis.

  • Demand-Driven Matters

    Demand-Driven Matters

    Welcome to the Demand-Driven Matters blog. During our conversation in this space, I hope to bring you additional insights on demand-driven manufacturing and/or help in your quest to become a demand-driven, factory of the future. I call this blog a conversation for a reason—your input will enrich what we are trying to do here, which is provide ideas about how you can become more demand-driven, each and every day.

    When I first began instituting demand-driven practices in the late 90s, we were into creating pull, eliminating waste, and getting on a path of continuous improvement. Technology at the time was seen as an inhibitor rather than an enabler. Most people active in Constraints Management and Lean Manufacturing were abandoning their technology and going to purely manual solutions.  I always believed that technology was important to get the most out of the system and to make it scalable, however, in the late 90s, the lack of technologies that enabled pull made manual the only logical choice.

    Convergence

    One of the more fascinating developments in demand-driven enablement has been the shift of demand-driven manufacturing back to technology as an enabler rather than an inhibitor. There is recognition today that technology has to play a significant role in eliminating waste and synchronizing operations and extended supply chains.  Along with this trend, the creation of open ERP systems that are easily integrated with service-oriented architecture allows companies to leverage the system they already have and benefit from today’s best-of-breed, demand-driven solutions through seamless, real-time integration. Finally, the web-based, SaaS revolution has made this process more cost effective, with expensive internal services now “downloaded” to the software provider, freeing up IT and manufacturing teams to focus on what matters. The digitization of demand-driven practices has, in effect, opened up companies’ ability to manage inventory and constraints more effectively; free up capacity; control operating expenses; drive flow; dampen variability; and create innovations to meet customer demand.

    You will see me often weigh in on what’s valuable and not-so-valuable—and you can do the same by commenting or perhaps even writing a rebuttal, just to keep me on my toes! We’ll look at the classic hallmarks of a demand-driven culture and see what kinds of leadership, change management, and employee communications keep such systems alive.  We’ll delve into the challenges and benefits of a demand-driven environment as well as what really happens on the shop floor – for example: what happens when you “choke the release” of inventory. I’ll also invite people from my team to weigh in about their areas of expertise—from implementation to integration to constraints management to new sales and marketing opportunities for a demand-driven business— and I hope you will tune in to hear their proven and exciting ideas.

    Based on decades in this business, I have found that demand-driven manufacturers realize the most benefit when they keep their eyes on the prize: Each day, they stay focused on demand-driven behaviors and remain disciplined in their efforts. It can be a difficult road. But it is my hope that this conversation will validate why demand-driven matters and inspire you on your journey each day. Until next time, keep it Lean!

    – John Maher

     

    John Maher                                                                                                                                                                                                                                                                                                           John’s passion for demand-driven manufacturing is equal to his interest in how this method improves the lives of employees within these environments. “I’m here to help, not to judge” comments John whose posts reflect why demand-driven matters and are based on his experience working in manufacturing environments and expertise in ERP, MRP, APS, supply chain, manufacturing planning and scheduling systems and constraints management.
     

“test”