Tuesday, September 02, 2008

Open source for underwriting

Suncorp's CIO, (Suncorp are a large Australian insurance and finance company), has committed to moving to open source platforms. This is being publicised as a cost cutting measure (which no doubt it is), but I (obviously) think that its just a sensible decision.

Lets make the assumption that all software, once its deployed, becomes legacy. Isn't it nicer to have that legacy not beholden to the whims of whatever company owns the source code? For the software to have a chance to evolve (open source development models encourage a more evolutionary approach) and also to be supported (regardless of any commercial organisations providing support, long term open source has a fighting chance that someone else can support it, regardless of what happens).

Its interesting that this sort of shift to open source is now happening at the CIO level (I guess it is inevitable over time - stuff that was bleeding edge and "risky" often becomes mainstream). Obviously people are seeing that at least for horizontal software, open source is the best bet to avoid black-box legacy applications which at some point no one will know how to maintain.

An interesting quote mentioning drools:

"Even for our underwriting service, we are going to be using Drools." ... "It is simpler, it is cheaper and it is actually easier to manage if we standardise it on one platform."



  1. You would be surprised how many mortgage / underwriting products are switching to Drools from other proprietary engines like Blaze.

    If only they come out and admit...

  2. I know, it's depressing. I can say now that most of the top banks use Drools, I just can't say who :(

  3. We are developing insurance products for top insurance companies in the UK(like Legal and General etc). We have had to switch to Drools for underwriting and almost all the business logic. Earlier, we were using QuickRules, however with SAP taking it over and deciding not to publish any more production licenses , Drools seemed to be the automatic candidate as it seems to provide the best of both worlds according to our client needs. They can purchase support if they are risk averse, or they could just use it as is and rely on open-source support to solve their problems. Drools rock!!

  4. Excellent - well there is interest in creating a Drools insurance vertical "starter knowledge base" - feel free to ping me if you are interested in getting involved.

  5. Great information thanks for sharing this with us.In fact in all posts of this blog their is something to learn . your work is very good and i appreciate your work and hopping for some more informative posts . Again thanks