Cylindo vs. DriveWorks

I would recommend DriveWorks to a college if they have similar needs to those I am personally experiencing at my university. Above all, I would not recommend it if the user needs to allow simultaneous access to a very high number of users (as is my case) since the software does not give this possibility. On the contrary, I would recommend it if a colleague needs to use software that works in the background and generates stand-alone models and prints for time reasons.

Incentivized

• Integration with other systems.
• Ease of use.
• Automation potential.
• Program UI.

Incentivized

• In some cases, the exchange of documentation between different users is not so automatic. Some operations still have to be done manually.
• All the variables and design parameters introduced by the user are not always visible and can be analyzed simultaneously. Sometimes changing the parameters related to the characteristics of the products is not so easy.
• DriveWorks allows access to a limited number of users at the same time. This issue sometimes makes the use of the software difficult for many of our students.

Incentivized

DriveWorks is similar to some of its competitors but there are areas where it excels in comparison. For example, DriveWorks has an easier integration with other systems in terms of automation. However, some of its competitors have an easier learning curve than opposed to DriveWorks. If a skilled user has knowledge of DriveWorks then it will not be an issue.

Incentivized

• DriveWorks helped us to increase the efficiency of our work thanks to the possibility to work remotely.
• The easy-to-understand graphical interface has allowed us to increase the interaction between our students.
• The impossibility of having many active users during the same session forced us to work at different times with multiple workgroups.

Incentivized