Keys to Successful Policy Administration System Upgrades
Celent will help qualify your requirements and introduce you to the vendor
Spotted a missing vendor? Use this form to alert a vendor to the Celent service
Create a vendor selection project & run comparison reports
Register to access this feature
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.
15 September 2014Karlyn Carnahan
All IT professionals have a horror story about a system upgrade gone wrong. Since most policy administration systems (PAS) have a 12 – 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 as compared with legacy environments. However, 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, Mike Fitzgerald and I surveyed 44 North American insurance carriers to provide answers to these questions as well as to understand major challenges faced and overcome. The report reviews carrier’s experiences in policy administration upgrades. It examines reasons for doing upgrades, staffing strategies, scope, time and budgets inherent in upgrades and provides advice from carriers on challenges to prepare for and advice to assure a smooth successful process. Here are some of the key findings from the report.
- 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.
Asia-Pacific, EMEA, LATAM, North America