CAE / Computer-Aided Engineering in the Cloud: Emotions
Starting with the first day of the development of the SimScale platform and even more since the official launch of it in July, I often talked with engineers, journalists and other people in the CAE / Computer-aided Engineering field about “the challenges of the cloud”. Plenty of interesting articles have been written, and many discussions appeared about that topic such that I do not think there is a need for another long essay on it. But maybe it’s time to draw a first small conclusion about my experiences so far: Emotions.
I often had the impression that the discussions I witnessed about using remote computing capacity and both the pros and cons on it were very emotional and driven by deep beliefs.
There were harsh opinions on both ends – from “I will never put my data somewhere else than on my computer” to “within a short time, everything will be in the cloud”. As in many discussions, probably the truth is somewhere in the middle.
I think that when putting the emotions aside, what stays is an individual consideration of the risks a user takes on with using a cloud solution and the added value it brings. Switching to a new software and implementing new processes for it always implies certain risks for a company.
In the case of a SaaS solution, the dependency on an internet connection is added. However with SaaS, gaining scalability through on-demand computing power, efficiency through new ways of collaboration and flexibility through pay-as-you-go pricing can generate a competitive advantage. Whether these added values overweigh the challenges of using the new software depends on the individual project or the company it shall be used in.
Probably this way of putting it is a bit dry – but what I believe is not dry is our mission at SimScale to make the aforementioned added values larger and more convincing week by week such that this new way of accessing simulation capacity becomes compelling to more and more engineers.
Is there a specific reason that would be critical for you for the adoption of an engineering SaaS solution? It would be great if you share it with us!