An obvious step for a carrier when contemplating outsourcing is to make sure it is dealing with a vendor that has expertise in this area, Forte notes. There has to be synergy between the carrier and the vendor, he says. They both have to have a sense of the direction [toward which] the carrier wants to move. Service-level agreements are very important, and so is the decision whether to go offshore or nearshore. Dealing with offshore firms in India can present a special type of risk, particularly with the time difference and communication issues. Some domestic companies are offering services, as well.

Outsourcing has been more prevalent in the life space and mostly with closed books of business, he says. Thats starting to change a little bit, especially with IBMs acquisition of Liberty. Its definitely not a mature market by any means right now. Handing over the keys to your core systems to a third party is a pretty scary thought for most insurers. Theres nobody who is going to be diving headlong into this right now. But I think you definitely will see policy admin move over into the outsourcing space in the next few years. Youll see more carriers get more comfortable with that.

For those looking for new systems, Forte maintains carriers are aiming for more integration with their other systemssuch as CRM and claims systemsacross all platforms, so they can get a single view of their customer and to service clients, which is the number-one priority for any carrier.

What were seeing now and probably will see more of over the next couple of years is insurers taking a look at the core systems, asserts Forte. Traditionally, theyve run these systems in siloed approaches, but in order to bring in the idea of business process management across all the different processes, there really needs to be a linkage with all the disparate systems to get the single customer view within their database.

Many carriers are running on multiple policy administration systems for a variety of lines of business. A life carrier Forte spoke with has 13 different platforms. A lot of the languages these old systems were written in go back to assembler language, he says. There arent many people around who still can code this stuff. Anybody new coming up today is not learning this [assembler] language. They are either .NET or a Java shop.

If carriers have a large IT shop, they are going to continue with building out their own solutions or look to tool-based vendors, predicts Forte. The midmarket carrier is starting to examine consolidating multiple systems to get down to one platform, if thats possible. Theyre looking at Java vs. .NET, he says. There are a lot of new policy admin vendors out there that are .NET focused.