Motion Design* and Mechanical Systems Experience** Apps appear to offer very similar capabilities when dealing with kinematics and dynamics simulations, aside from some differences in the user interface. However, there are many differences that I would like to explain to you.

Mechanical Systems Experience is perfect for Kinematics. However, for Dynamics, its data model is not optimal and its solver is too limited. That’s why Motion Design has been created with a new data model and solver in order to perform Dynamics simulations efficiently and also to get a scalable offer from the CATIA App to the advanced SIMULIA Apps.

The new CATIA App. covers kinematics and "simple" rigid multibody dynamics simulations (MBS) when the SIMULIA Apps (Motion Engineer & Motion Analyst) cover advanced MBS like flexible MBS, event-based motion, advanced machine elements, co-simulation, etc. 

In order to ensure a seamless path from one App to the advanced Apps, a same data model and the same Simpack solver is used. Only the components (like machine elements, advanced joints, etc) and functionalities (like flexible bodies) are available upon the App used in a cumulative approach.

In fact, there is a period when both Apps will co-exist but Mechanical Systems Experience will be deprecated in the future.

* included in Motion Designer role (MKM)

** included in Mechanical Motion Designer role (MMO)