What I like most about Leo AI is that it helps turn a lot of slow, manual engineering work into a much faster and more efficient process. It is especially valuable when engineers need quick access to relevant knowledge without digging through endless files or relying on memory. The product feels purpose-built for technical teams, and that makes a big difference in how useful it is day to day.

My background is clinical. I understand mechanical design well enough to contribute, but I am not a senior mechanical engineer and I know it. When I joined the device development team at Clalit, one of my biggest frustrations was how much institutional knowledge was effectively invisible. Documents from previous product lines existed somewhere, but finding the right one for the decision in front of you was a project in itself. Leo changed that completely. I describe what I need, and it surfaces the relevant internal material, previous design decisions, past calculations, and backs everything with a cited source I can actually click on and verify. For someone at my level of mechanical experience, having that kind of depth available instantly is the difference between a confident decision and a guess

The search in Teamcenter has always been a weak point for us. If you don't know the exact part number or file name, you're basically not finding it. Leo changed that. I can describe a part geometrically or by function and it finds relevant parts from our own history, not just from an external catalog. For a team our size with years of legacy NX data, that's a significant time saver. We've started reusing parts we didn't even know we had, and that has real downstream impact on procurement and BOM costs.