The amount of embedded software in today's products is only increasing. What role should PLM play in that context?
Me? I’m just trying to be practical. Fundamentally, the system engineering process is about breaking down requirements, assigning them to functions and then assigning those functions to items in the product structure or Bill of Material. What’s critical about that process is being able to allocate functions to items regardless of engineering discipline, whether that be mechanical, electrical or software components. In fact, you might have one functions allocated to a mechanical component and software item. Furthermore, many functions need to be allocated not to the compiled software, but to the raw code and even software library components. Yet if those items are managed in a separate system, then that sort of traceability can never come to fruition. That’s a natural reason why embedded software components need to be managed in PLM systems alongside items from mechanical and electrical teams.
Despite getting whipped in the comments section (yes… you should read them…), I won the vote.
Yes. I lost the last debate. So I decided to go for the mummy’s revenge. Two whole rolls of duct tape.
And yes. That is my daughter who pushed me over and proceeded to laugh maniacally.
Egads. I need to stop this slide.
Tech4PD is a web show hosted by Chad Jackson of Lifecycle Insights and Jim Brown of Tech-Clarity that covers the most important issues in technologies used for product development. The shows include a debate. The loser of each debate must fulfill a painful or embarassing consequence shown on the next show.
Our favorite duelling analysts are back. In this episode Jim Brown and Chad Jackson disagree about the size of Jim’s coffee cup and whether software development for mechatronic devices should be managed within PLM systems. Watch the loser of the last debate suffer the Mummy’s Revenge, and vote for a new winner (or loser). You can watch below or at this episode's page on ENGINEERING.com.