Blog

The 80/20 principle, also known as the Pareto Principle, suggests that roughly 80% of the effects come from 20% of the causes. When it comes to hardware design, applying the 80/20 principle can help optimize efficiency and focus resources on the most critical aspects. Here are some ways to utilize the 80/20 principle in hardware design:

1. Identify Critical Features: Determine the key functionalities and features for the hardware design’s success. Focus on the 20% of features that will deliver 80% of the value to the end-users. This allows you to allocate resources effectively and prioritize the essential elements.
2. Design for Common Use Cases: Analyze the most common use cases and requirements for the hardware. By identifying the 20% of scenarios that cover 80% of user needs, you can streamline the design process and optimize performance for those primary use cases. This approach helps avoid overengineering and unnecessary complexity.
3. Prioritize Design Constraints: Identify the critical design constraints and factors that significantly impact the hardware’s overall performance, cost, and reliability. Allocate resources and effort to optimizing these key areas, ensuring they meet the required specifications while considering the trade-offs for less critical aspects.
4. Focus on Robustness and Reliability: Identify the 20% of components, subsystems, or functionalities that are most likely to fail or cause issues. By focusing on improving their robustness, reliability, and quality, you can enhance the overall performance and longevity of the hardware. This targeted approach allows for effective resource allocation and risk mitigation.
5. Iterative Design and Feedback: Adopt an iterative design process and collect feedback from users, stakeholders, and experts. This enables you to identify the most critical areas for improvement and refine the hardware design iteratively. You can improve substantially by addressing the 20% of user satisfaction issues.
6. Continuous Improvement: Continuously assess and evaluate the hardware design to identify areas of inefficiency, waste, or redundancy. By applying the 80/20 principle to ongoing improvement efforts, you can focus on the most impactful changes resulting in the most significant overall benefit.

Remember that the 80/20 principle is a guideline and may not always be exact. The specific percentages may vary depending on the project and context. The goal is to identify the vital few factors or aspects that significantly influence the hardware design’s success and allocate resources accordingly.

At PEG, we practice an integrative approach involving Simulation in the complete product development cycle. It is important to understand the role of simulation in every phase of the product development cycle. Below is a summary of how simulation can be used in each stage:

1.  Concept Phase: 

During this phase, use simulation tools to verify circuit operation. One must start small using ideal component models and build the system in stages. Each stage work should be saved. It is important to understand the theory and state of the art behind the circuit you are about to simulate. Without proper theoretical foundation, you will not be able to obtain useful information from simulation.

Also, for majority of the engineers, a process methodology or steps to design must include simulation. Simulation is most effective when the circuit behavior is not well understood and we can construct several what-if scenarios or use simulation to build a repertoire of questions to be answered about the design problem at hand. Simulation effectiveness improves with experience and time. An engineering department must be dedicated to it. As with any other skill, to yield simulation as a potent competitive weapon, one must spend significant time and resources to hone it. A frivolous relationship or experimental tinkering with simulation tools will not yield any fruitful results.

2. Design Phase: 

During design phase, as you begin to transform your work into schematics, one must pay careful attention to component selection and component models can be incorporated (especially in Spice based tools) one at a time.

Do not be too ambitious to incorporate a host of models at one time. Also realize that incorporating each component model is never required. One must be quite prudent in incorporating essential component models. Just remember Pareto’s principle – 20% or less determine 80% or more of the outcome. This must always be kept in mind

3. Prototype Phase: 

During this phase as prototypes are built, one must pay careful attention to collecting data during incoming inspection (mechanical variables) and testing (electrical variables). Here, we always recommend to use the  suppliers who would also build production units. It is important to do so to understand supplier capabilities and process variations.

4. First Article Phase: 

During this phase as First Articles are built, one must pay careful attention to collecting data during incoming inspection (mechanical variables) and testing (electrical variables). During this phase, we use statistics to understand variable distributions and correlation between various parameters. These correlations may change from the prototype stage.

It is important to start forming new hypothesis can tremendously expedite the whole product development cycle. During this phase, at PEG, we strongly recommend using statistics to understand variable distributions and correlation between various variables.  It is important to start forming hypothesis on what could be troublesome variables which are going to effect the performance. Those variations must be incorporated into Simulations to re-characterize  the system and understand overall performance variations.

5. Pre-Production/Production Phase: 

During this phase as Pre- Production or Production units are built, one again must pay careful attention to collecting data during incoming inspection (mechanical variables), in-process inspection (mechanical and electrical variables) and final testing (electrical variables). During this phase, we use statistics to understand variable distributions and correlation between various parameters.

These correlations may change from the earlier phases. It is important to start forming fresh hypothesis on what could be troublesome variables which are going to effect the system performance. Those variations must be incorporated into Simulations to re- characterize the system and understand overall performance variations. This is the process of continuous improvement and PEG’s integrated approach, if followed rigorously, yields not only superior products but also strong infrastructure capabilities.

There is always an “Edison approach” to design. With this approach, you will need to spend countless hours and follow rigorous and scientific method of design of experiments as well as truthful collection of data. “Edison approach” is simply too expensive and unaffordable in today’s world. Nevertheless, with enough money and time, such approach is always possible.

LTSpice and PSpice are great tools for Power Electronic circuits barring their annoying and most irritating convergence problems. These convergence problems are a great waste of time and a source of frustration. However, there has been a steady rise in the tools and techniques in the Spice arena, especially for the Power Electronics and Motor Control areas. Spice and other available tools expertise can be wielded effectively in launching new products through short product development cycles. By no means, we are claiming that Spice expertise in Power Electronics alone is sufficient to cut the time from concept to production.  However, it is an important tool to have in the bag.

For Power Electronics Circuits, PEG recommends the following approach to using Spice during  the Concept Phase only:

• Before you build your own circuit model, search to see if similar circuits are available in the public domain. A great engineer always builds her/his work on what is already available. Do not reinvent the wheel.
• Always start with the most ideal circuit model of components. Simplicity is the key. Sub-circuits are great in ensuring that small parts of circuits can be made to work first. It is always prudent to use simple, well-tested models.
• Now, transient analysis using ideal components will get you only so far. Small Signal modeling is an important step in being able to overcome convergence problems as well as understand the circuit behavior fully. This technique requires state space averaging and is most vital in simulating Power Electronic circuits. PEG specializes in small signal modeling of the Power Electronic circuits and if you run into hot waters using this technique, we are happy to help.
• Control loop compensation is not a  simple matter for most of the Power Electronic circuits. However, the compensator can be easily designed using the small signal modeling techniques.
• Once the above steps are followed and we have a working simulation, we can begin to run various what-if scenarios to understand the circuit behavior in time domain as well as frequency domain.