Here is the second Trade-Off identified for 3DLean :

As a tool which supports Team Meetings and Collaboration embedded in the 3DEXPERIENCE Platform, has 3DLean to be simple and playfull for shopfloor users or has it to be fully connected and integrated to engineers tools which can trigger to more complexity?

​​​​​​​

The entire 3DLean solution has been built closely with UX/UI people right from the beginning. As being embedded in the 3DEXPERIENCE Platform, a Lean Team Player who uses 3DLean has also access to Swym, 3DDrive (on Cloud) and other solutions, according to its roles.

On the other hand, when presenting 3DLean, frequently asked questions are : How to do analytics with my E-note contents ? How to capitalize on the problem I met and I solved ? When assigning a person on the factory map, can it be linked to Apriso work orders ? Can I access my work instructions from 3DLean ? etc.

Making those interactions possible would be very interesting and would mean to increase 3DLean complexity by adding functionalities, buttons, options and customization. The questions is, is that what we want and does the Lean Team Player really need that ?

The floor is yours 

👉According to you, if we want to address multiple Teams, in multiple industries what to propose them ? A playfull experience embedded in 3DEXPERIENCE Platform with simple interactions or a tool connected as much as possible to other solutions, with associated complexity ?