Tech4PD: The Modular Platforms Episode

Mass customization rocks. It’s the reason my computer is just like yours, but with a different graphics card. It’s why our cars look the same on the outside, but yours has a manual transmission. And it’s why I can finally eat candy that has the Green Bay Packers logo.

Vive la variant!

Of course, if you design products, you may have a different perspective. You start with a design, and anticipating demand for different configurations, you think modularly and platforms. You add variants. For example, if you want to sell on a global market, you may need a dozen variants to comply with regulations in a dozen different countries.

But with each variant, your possible combinations of products explodes. So, how do you test it all? How do you manage it?

Some engineers use the BOM in their CAD system, tucking variants and modules under subassembly trees that can be hidden, shown, expanded, and tested as needed. Others let their data management system and the BOM there do all the work. So then, which approach is best?

In this episode of Tech4PD, our experts, Chad Jackson and Jim Brown, debate this very question.  See if they change your mind.

And then, keep watching to the end to see the wrong CAD pundit get a head shave.


This entry was posted in Creo reactions, What's in Creo 2.0 and tagged , , , , , . Bookmark the permalink. Trackbacks are closed, but you can post a comment.

Post a Comment

Your email is never published nor shared. Required fields are marked *

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

You may use these HTML tags and attributes: <a href="" title="" rel=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <pre> <q cite=""> <s> <strike> <strong>

  • Archives

  • Connect with PTC Creo