Dealing with Policy Administration Systems: New, Conversions and Acquisitions 29 June 2010 

Introduction • Policy Administration Systems • New legacy system / data integration over time • Acquisition integration across systems / data • Conversions integration over time – Maybe partial or full by functionality – How much history is included in the conversion? – Second order impacts – Updates can be equally disruptive 

Session Outline • Actuarial Issues • Selecting a New PAS / conversion strategy • Data Management Strategies – Enterprise DW – Surround Strategy 

Selecting a New PAS / conversion strategy Kevin Pledge 

Selecting a New PAS / conversion strategy • Reason for Change • Actuarial Role in PAS • Environment 

Reason for Change • Acquisition – Keep both systems – Convert to one system – Something in between • Need for new functionality – Product / Operational – Scope of conversion? 

Actuarial Role • Actuarial data requirements • Support in the decision process – Product support analysis – Risk / cost analysis – Business expert • Implementation support • Impacts 

PAS Conversion Decision • How much history to convert? • Is it really necessary to convert the whole system? • Plancode and other legacy carry forward 

IT Infrastructure – an ongoing project 

Changes Impact Multiple Processes Claim Sys 1 Run off Claim Sys 2 PAS 1 PAS 2 converted data PAS 1 PAS 2 Time • Claim system run off for existing claims, but what about admin changes, reopened claims? • Data consistency not as expected, for example changed attribute fields not consistent during conversion period. 

DW as a buffer to changing backend Asset PAS Agency Accounting Pol Service Reins POSv CRM GL Valuation Pricing Claims POS Agency Data Store Data Warehouse 

DW as a buffer to changing backend Asset PAS Agency Accounting Pol Service Reins POSv CRM GL Valuation Pricing Claims POS Agency Data Store Data Warehouse 

Case Studies