The basic building block of our product is, of course, functionality - you click a button and something occurs based on one or a number of parameters. This was a fundamental driver of development spanning the ENOVIA portfolio for some time back into its "Matrix days." This has resulted in a system that is extremely strong functionally today.

But now, customers are not looking to us for just functionality, but the best approach or process to complete an activity on the Platform. This has come upon us, in part, from the introduction of the Platform into smaller and smaller companies that lack the experience and/or history of working in the PLM space.This shift, however, has given us the added benefit of more effectively improving the quality of the product and the user experience (UX) for the end-user. By defining and validating the best method to complete any specific activity on the Platform, we can use that same "best practice" to drive the testing procedures for QA in confirming the systems' operation. In the past, QA would test individual functions or small groups of functions in multiple combinations, since we did not define a specific process to the customer to use the product. With a best practice promoted outward to the customer and inward to QA, the validation and supporting UX can be more easily confirmed and improved.

Quality_and_Certification  ​​​​​​​

Cloud ​​​​​​​