Ten steps to achieving success with your Guidelines for Data Migration Policy Center

For many carriers embarking on the implementation of a new policy governance system, data migration of their policy portfolios is the most risky and difficult part of the project. Regardless of how well the application is configured to meet the functional requirements of the organization, if the data migrate is problematic, it can easily lead to operational and reporting problems, affecting its customers and May damage user acceptance of new applications.

process and execution. In this blog we deal with data migration for the guideline policy maker and list ten best practice tips derived from successful guideline policy policy migration projects that can help in your own implementation for a smooth PAS data migration.

The most important thing is to keep it simple and perform an ‘on renewal’ migration,

it removes your new system from legacy applications and is the simplest and cheapest option. Certainly, the inconvenience and cost of your legacy application is in production for another 14 months, but in most cases benefits from the costs of ‘big-bang’ migration efforts. RenewalAPI, in the case of the Guidelines Policy Center for GX Models and Enhancements, provides an easy way to create entity graphs and populate properties.

Put together the right team –

The migration team will require quite a diverse skill set, perhaps more than any other project teams. On the technology side you will need legacy DB technical and application knowledge, an ETL person to extract and purge in a landing area or staging area, a BA in the data model of both systems for mapping, defining a business process person end for. A data architect, two-end process for future state data models as well as analysis and management of implications during the transition period. A integration specialist with renewal APIs, XML, entity models and product model skills will be required for the policymaker.

Agile clasp –

The two basics of Agility are collaboration and responsiveness to change, and there is no doubt that you will find unexpected challenges, often around data integrity and cleanliness. Keep your product owner informed, re-prioritize your backlog and don’t get bogged down in edge cases that involve very few policies. Create a manual work around for these, perhaps creating an underwriting issue on the changed policy in the Policy Center, marking it for manual review.

Work closely with the Policyketter team to ensure product models, unit models and ratings form. Common practice migration is considered as an integration for guideline implementation, but we have found an advantage in the migration team participating in the Policykator daily scam, knowing exactly what is happening in Policykart, and the data migration implications Have to call

Its heart data migration is a massive mapping effort,

so you would need a defined BA to extend the data element mapping, code value mapping to manage and agreed upon transform rules or default values ​​with underwriters and other SMEs is. Involve the policy team to assess the implications of the mapping, this is not a good default value that will generate excessive underwriter referrals or adverse impact ratings and undesired premium increases. Start outlining legacy data in the project installation phase or Sprint 0 and quickly understand how much cleaning is required, it will then feed into the mapping process.

Consider third-party standardization tools to purify names and addresses and assist with dedication. The best migration projects add business value by massaging and cleaning data during migration.Consider the impact of migration policies In your Policy Center Inception Workshop and Story Cards, the final sprints will be impacted by the Policy Center tenant to complete the policies that would otherwise come.

Do you need special typecodes such as ‘unknown’, which are valid only for migration policies?

When specifying validation, business rules or underwriting issues should specify whether they apply to migrated policies. How will ratings work on migrated policies, do we need special rating neutral values ​​for migrated policies? If the rating is changing, is there a need for premium capping and cupping. Always migrate the expiring premium over the new policy term for capping and cupping purposes or prepare a premium variance report so that unexpected premium movements can be analyzed in the stabilization phase.

User signoff can be difficult and controversial –

a good approach for the migration team is to first-cut data mapping, most of which are straight forward. The remaining issues and a recommendation were presented in a workshop for all stakeholders.

Leave a Reply

Your email address will not be published. Required fields are marked *