Take a walk in the engineer’s shoes: I need an 80 MHZ network controller for my new project and I found one in the PLM/PDM system. That was easy. Now a quick check in the procurement database to do a price and availability check. So far so good, now on to the component engineering system to see if there are any possible lifecycle issues with a 10-year minimum requirement. It’s my lucky day, no issues and it’s a company-preferred part with an ECAD library instance.
This is one pretty scary world we live in. Every day there are stories about data breaches, network hacks and even possible spying by foreign software and hardware suppliers. Every individual has become hyper-aware of the security issues revolving around their personal data. A company’s need to protect its design IP is actually more critical than an individual’s need to protect their personal data.
Have you ever finished generating the manufacturing release package for the latest product design and then it occurred to you that something may be wrong? Imagine, it’s Thursday night and you just finished a nice dinner with the family. Your daughter’s soccer team won and the Broncos are playing the Chiefs tonight. It will be great to relax and enjoy the game.
Defining initial hardware architecture requires many decisions, most of which impact a variety of different stakeholders and requirements – including multiple design tools – circuit design, PCB layout, mechanical design, spreadsheets, etc. that are used to track different elements of the design.
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.