Modelling as a Query

Author: Guy Shepherd

One thing that I’m frequently asked is how client models can be better integrated with database or data warehouse environments.  While many of our customers have successfully integrated their pricing, reserving, and servicing models with various operational databases, they are keen to understand what else might be possible. 

Obviously, storing model inputs, parameters, and results in a central repository has a number of control, access and performance benefits over traditional file & folder-based solutions.  However, the end-to-end modelling processes usually still require data to be extracted from the database and transformed ready for model consumption.

One of the many advantages of the Financial Modelling Platform over traditional / legacy modelling systems is its service-oriented architecture (“SOA”). This mature architectural paradigm allows enterprise systems to be developed using a set of reusable, loosely coupled components, rather than the tightly coupled bespoke and potentially brittle elements typically found within the financial modelling arena.

A recent extension of this paradigm is the ability to consume any model directly from within the database itself – something we have termed “modelling as a query”.  While the significance of this capability might not be immediately obvious, there are numerous potential applications and benefits.

For example, having the ability to place a value against each new business policy the second it appears on the books might be interesting from a total customer value perspective.  Similarly, triggering the calculation of a change in value of an entire book of policies ahead of a prospective assumption change might help a business make quicker and more informed decisions, all without any risk of compromising data security. 

While this is all possible using the existing database integration capability of, “modelling as a query” enables this to be done without having to leave the database environment, without manual intervention (i.e. unattended operation via triggers or scheduled tasks), and without having to extract from and transform the data from the database. 

What could your organisation do with the ability to call a model or calculation directly from a query – something like this?

SELECT Result from [ Model]

You can check out a white paper that covers Modelling as a Query in more detail here.

If you want a live demonstration of this new functionality, please drop us a line and we’ll be very happy to show you and understand any potential use cases you might have.

Additional Resources

Was this article helpful?

Comments are closed.