Despite the importance of assumption management, many organisations still struggle to find a robust yet flexible solution to the problem and lack an effective assumption management framework.
For years, there has been discussion about the use of graphics processing units (GPUs) to enhance the performance of financial models. Can GPUs represent a significant leap forward in the performance of financial models, or do the challenges and overheads outweigh the benefits?
The demanding regulatory environment increasingly places challenging stipulations around the number of model runs required and the timeframe in which results are to be produced. Combined with the ever-increasing volume of data that most insurers wish to process this can drive the need for a scalable model solution.
Software Alliance’s Su Berry spends 5 minutes with Cornelius Franken of CJF Consulting to discuss his experience with Mo.net and the benefits it has brought to his actuarial modelling processes.
Despite the insurance industry’s historically slow adaptation to change, recent years have witnessed numerous efforts to modernise the actuarial function. Several of these initiatives have gained significant traction. However, many still fail to deliver on their anticipated benefits…
As part of Mo.net 7.6, we have extended the external interface to compiled Mo.net tasks so that it now accepts a Python list. This update allows a new array of inputs to be passed from Python to the compiled Mo.net task DLL without having to create an intermediate inputs file.
In today’s complex and uncertain world actuaries are spending less and less time focused on the tasks they were hired to do. So, how did we get here and how do we fix it?
We sat down with Software Alliance’s founder Stephen Curle to learn about the company’s highs and lows in the early days, and his thoughts on the future of financial modelling.
One thing that I’m frequently asked is how client models can be better integrated with database or data warehouse environments. This article explores what else might be possible with Mo.net…
Are actuaries and other “power users” of Excel using their ingenuity to solve solutions with a relatively limited set of functions… or are they ignorant of other functions that may be better suited to the particular use case?