Keysight’s own ENOVIA upgrade validation used to take 192 hours. It now takes 30.
That’s not a product claim. It’s what our IT and test automation team measured on our own digital thread environment, and this session is the account of how they got there, including the parts that didn’t work.
Most engineering organizations know the trade-off. Stay current and absorb weeks of manual re-validation after every release, or defer the upgrade and let technical debt, security gaps and vendor pressure build. The upgrade waits a quarter, then a year.
Mahavir Rathi, Global IT Operating Manager at Keysight, walks through what the team automated, what they deliberately left alone, and the one decision that made the rest possible. Sandeepak Natu of CIMdata joins to set it against what he sees across PLM programs more broadly.
What you’ll take away:
Who should attend:
Engineering and digital thread leaders, PLM and CAE system owners, and the QA and validation teams responsible for keeping PLM current, anyone who’s ever postponed an upgrade because of what validation would cost.