Circuit Modular Reuse Best Practices

Circuit Modular Reuse Best Practices

Menu

In my previous post in this series about effectively reusing design modules to increase product quality and decease development time, I challenged you to think about how well you’re making use of existing design modules and why getting better at this could be a competitive differentiator. I looked at some of the design challenges circuit designers are facing, such as miniaturization, proliferation of electrical constraints and high speed design requirements, as well as some of the potholes it’s easy to fall into when working with modular design.

Today I’m going to take a step-by-step look at some circuit module reuse best practices, along with an example. The answers that I’ve kept you waiting for in part 1.

Managing modular circuit blocks

An increasingly popular and effective way of dealing with human errors creeping in when reusing designs (such as inadvertently using older block prior to an issue being resolved) is by using data management software that stores reusable circuitry as modular blocks. This greatly simplifies the process of reusing existing PCB schematics, parts lists and layouts.

The new generation of data management software controls access to circuit blocks, so only authorized editors can make changes. Editors need to check out the modular block and other users can’t make any changes to it until it’s checked back in, to ensure the design integrity. The software can also be configured to require approval when a change is made to a modular block.

Reusable modular blocks can be created in two different ways:

Top-down approach

  1. Partition the design early on in the design process.
  2. Create the block diagram, then add circuitry to each block.
  3. Validate blocks and complete the design.
  4. Register the parts list, schematic and layout of each block in the data management system, along with its metadata containing detail such as which products the block is used in, engineers involved in its design, and the approval chain.

Bottom-up approach

  1. Create and validate the circuitry .
  2. Partition the design into blocks.

You can see  how much more effort the top-down approach takes (four stages rather than two), and it requires more planning time. But the payoff is huge in that blocks produced this way are usually much more suitable for reuse, so you save lots of time later on when you reuse the blocks in variant designs. Put the work in at the start to reap the benefits later on down the line.

Streamlining the design process – cell phone example

Let’s look at how the modular design approach can substantially help streamline the design process for the cell phone example mentioned in part 1. We’ll assume that the design has been partitioned into blocks representing the RF, baseband, Wi-Fi, Bluetooth and other sections.

The engineer working on the new variant follows this simple process:

  1. Call up the modules by searching the data management system for the product name.
  2. Check the documentation stored in the system for each module they want to use, to ensure it is a good fit for the new design.
  3. Drop the modular blocks into the new design. The parts list, schematic and layout of each modular block will all be incorporated into the new design.
  4. Design the new RF block and any other new blocks needed, either from scratch or by modifying existing blocks.
  5. Connect sections together and route new areas of the design.
  6. Check the design
    1. Check for issues such as signal integrity and thermal management, focusing on the newly-routed areas.
    2. Do a basic simulation of the complete design; even though checked modules are used, there’s a small possibility combining them could cause an issue.

By designing this way, regulatory compliance time can be reduced by using proven design blocks. This reduction in design time means it’s possible to bring products to market faster, which helps increase revenue and enables new products to gain market share before they face serious competition. Modular circuit reuse also reduces errors by allowing designers to use proven designs wherever possible.

Is now a good time for you to make best use of modular design to help your team develop and release boards faster?

Learn more about engineering data management here, and view our webinars.

Craig Armenti
Craig Armenti
wp-header-1920x844-integration-1-510x310
  • Blog
March 13, 2025
How ECAD and PLM Integration with Zuken DS-CR and Dassault’s 3DEXPERIENCE Enhances Collaboration

The integration of Zuken DS-CR with Dassault’s 3DEXPERIENCE Platform provides a scalable and future-proof solution to bridge the gap between mechanical, electronic, and software engineering.

Read now
wp-header-1920x844-data-management-6-510x310
  • Blog
November 21, 2024
Engineering Data Management Strategies for Successful Projects

Project design data management strategy is pivotal for successful cross-functional project development process. Engineering data management helps teams operate more efficiently by reducing data access administration time and ensuring accessibility to up-to-date data for all team members. Learn more about the Key Aspects of Engineering Data Management on our blog.

Read now
A satellite in orbit around the moon, depicting advanced space technology and exploration, measuring Earth through innovative aerospace equipment and missions
  • Blog
January 24, 2022
Measuring the Earth

EREMS, a French enterprise specializing in the design and realization of high-tech electronic equipment and of associated software for Space, Defense, and Aeronautics uses CR-8000 and DS-CR from Zuken for the design and lifecycle management of flight electronics, ground electronic equipment, and test benches.

Read now
Digital continuity for product development
  • Blog
September 06, 2021
Digital Continuity for Product Development

Today's smart and connected products require the interaction of different components and systems. Their elements are developed in different engineering disciplines and departments. These disciplines speak different engineering languages and require unique views of the same product. The storage of these different versions in the respective departments leads to disconnected silos in terms of processes and data - but digital continuity is here to help!

Read now