Vendors
日本語

Benchmarking Policy Administration Upgrades: Advice from Those Who Have Gone Before

Create a vendor selection project
Click to express your interest in this report
Indication of coverage against your requirements
A subscription is required to activate this feature. Contact us for more info.
Celent have reviewed this profile and believe it to be accurate.
We are waiting for the vendor to publish their solution profile. Contact us or request the RFX.
Projects allow you to export Registered Vendor details and survey responses for analysis outside of Marsh CND. Please refer to the Marsh CND User Guide for detailed instructions.
Download Registered Vendor Survey responses as PDF
Contact vendor directly with specific questions (ie. pricing, capacity, etc)
2 September 2014

Abstract

All IT professionals have a horror story about a system upgrade gone wrong. Since most policy administration systems (PAS) have a 12 to 18 month upgrade cycle for major releases, there are plenty of opportunities to misstep. To address this dynamic, a consistent claim of modern PAS vendors is that multi-tiered architectures and other technical designs ease the pain of upgrades.

Up to now, objective data concerning upgrade metrics was difficult to collect. How long does it really take to upgrade a PAS? Do modern systems live up to the levels of ease that vendors cite? Historically, have insurers experienced any difference in outcomes when using vendor or third party system integrator staff versus internal staff to execute the upgrade?

In order to close this gap, Celent surveyed 44 North American insurance carriers to provide answers to these questions as well as to understand major challenges faced and overcome.

Key Findings

  • Most carriers doing upgrades do a point upgrade, and generally these are successful.
  • All upgrades to modern systems in the survey group were successful, supporting the expectation that these platforms reduce the pain related to ongoing updates.
  • The most frequently reported reason for taking an upgrade is “to gain new functionality” and the second most common driver is “current version no longer supported.”
  • Only 10.7% of insurer respondents used their own employees without assistance from vendors or third party companies. The most common uses of vendor services for upgrades are for coding, configuration, and testing.
  • Most upgrade projects (64.3%) meet their delivery deadline.
  • Some carriers actually came in below budget on their upgrade, but the vast majority, 60.7%, came in on budget.

“Many carriers report that they have not upgraded their PAS either because they’re homegrown, or, more frequently, because these are new installations,” says Mike Fitzgerald, Senior Analyst with Celent’s research practice and coauthor of the report. “This places a particular importance on the lessons that can be learned from other carriers’ experiences as the new installations prepare for their first upgrades.”

“For many carriers upgrades are a big deal,” says Karlyn Carnahan, Director with Celent’s Insurance Group and coauthor of the report. “They take months of effort, tie up a lot of staff, and can frustrate business partners. But done well, they go smoothly and can add functionality, upgrade configuration tools, and deliver significant benefits.”

This report focuses on carriers’ experiences in policy administration upgrades. It examines reasons for doing upgrades, staffing strategies, and scope, time, and budgets inherent in upgrades. It also provides advice from carriers on challenges to prepare for and ways to assure a smooth, successful process.