Deploy Simulation Apps Across a Larger Team

Build a custom application based on your mathematical models and let your colleagues and customers benefit from your expertise

1 min read
Build a custom application based on your mathematical models and let your colleagues and customers benefit from your expertise


The traditional use of numerical simulation in product development involves creating a mathematical model, identifying the range of parameters that will be used to simulate the device or process, performing the computations and preparing reports to communicate the results. Making any changes to the simulation requires going back to previous steps and making changes, which requires intimate knowledge of the original model.

With the Application Builder, the tool within COMSOL Multiphysics® that wraps the mathematical model in an easy-to-use app, the simulation expert is able to create apps that colleagues can use to run their own design ideas. This distributes the analysis capabilities throughout a team or company, and allows the simulation experts to spend more time adding complexity to the models or creating new ones.

Users of the app, such as the rest of the design team or colleagues in another department, can benefit from the simulation without being overwhelmed with complexity. Additionally, proprietary aspects of the simulation can be hidden, even as the app is used.

The author of the app can manage its deployment with COMSOL Server. Engineers other than the creator of the model can investigate the benefits of using different materials or geometries without having to master the intricacy of the complete simulation. Professionals who are not scientists or engineers can make use of apps to demonstrate the potential of a certain technology to new investors or collaborators.

With the COMSOL Multiphysics® Application Builder and COMSOL Server you can overcome the disconnect between simulation specialists and design engineers and leverage a larger workforce, reducing overall product-to-market time.

Learn More:

The Conversation (0)

Why Functional Programming Should Be the Future of Software Development

It’s hard to learn, but your code will produce fewer nasty surprises

11 min read
A plate of spaghetti made from code
Shira Inbar

You’d expectthe longest and most costly phase in the lifecycle of a software product to be the initial development of the system, when all those great features are first imagined and then created. In fact, the hardest part comes later, during the maintenance phase. That’s when programmers pay the price for the shortcuts they took during development.

So why did they take shortcuts? Maybe they didn’t realize that they were cutting any corners. Only when their code was deployed and exercised by a lot of users did its hidden flaws come to light. And maybe the developers were rushed. Time-to-market pressures would almost guarantee that their software will contain more bugs than it would otherwise.

Keep Reading ↓Show less