Mug envy, everyone succumbs to it at least once in their lives. And Jim uses this mind manipulating technique to his advantage by distracting the poor unsuspecting Chad Jackson before nailing the coffin shut on the debate regarding PLM in the Embedded Software design space.
You don't use MCAD to write code or design a chip, so why use a PLM tool designed around managing physical hardware and the data definition to go with physical items? PLM, in its current state, is clearly not designed for managing software development.
Yet, embedded software gets shipped with (or within) the physical item. Shouldn't its definition and configuration be linked to the physical items the code is designed for? Of course it should, and that location is PLM.
Watch the action and vote for where you think the design definition for embedded software should reside. Me? I'm going to go out and buy a bigger mug.
This episode sponsored by Autodesk PLM 360 and PTC.