It is not uncommon for multiple model developers to want to work on the same project. Changes made by each developer need to be added in to a central codebase to ensure there is always one source of the truth. Another common requirement is to be able to carry out code reviews, to check how one version of a model differs from the previous version, or to peer review an individual’s model developments.
Back in January, I outlined an approach for sourcing model assumptions at run time using a web data source. This approach used some custom code and a third party DLL to connect to the data source endpoint and digest the response. Following the release of Mo.net 7.7 this has just become much more straightforward.
As the complexity of models used by insurance enterprises continues to escalate, and the reliance placed on such models continues to grow, the importance of ensuring that models operate as intended comes under increased scrutiny.
When trying to model any product there are various elements that it can be helpful to have to hand.One such element is a sample model for the specific product that shows how to model some of the possible features under one or more use cases. Within Mo.net Model Development Studio you will find several of these lightweight samples to help accelerate your modelling projects. The Funeral Plan project has just been added to the samples for the next release and is one of the more fully featured examples. This was developed in partnership with Insight Life Solutions.
Today, I’m excited to sit down with Pamela, Head of Insight Life Solutions to discuss her insights into the actuarial profession and her team’s experience with Mo.net.
In the rapidly evolving landscape of the insurance industry, efficient and secure communication between stakeholders is more critical than ever. The Origo Messaging Standard has emerged as a powerful solution to streamline these interactions, particularly for insurance contracts.
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.
Responding to a request from an existing client who wanted to connect their current Mo.net-based front office illustration platform with a new underwriting system, this blog article demonstrates how external API data sources can easily be used in a Mo.net model.
Drawing from our recent experiences in assisting clients with the design and implementation of pension dashboard solutions, this post outlines how we’ve supported them and provides valuable tips on becoming “dashboard ready”.
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.