Data Migration Process. Facilitation Skills Training Table of Contents Purpose and Prerequisites...

Data Migration Process

USER CHAMPION

Facilitation Skills Training

Table of Contents

Purpose and Prerequisites

Data Migration Data Flow

Data Migration Process Flow

Data Migration Process Description

Roles and Responsibilities

Premium Collection after Data Migration Roll-outs

PLI Data Cleansing

Data Mapping

McCamish Modules


Purpose, Inputs and Output for Data Migration Process

• The purpose of Data Migration Process is to ensure a smooth, accurate and timely migration of data from existing PLI/RPLI system to McCamish without impacting customer service and productivity of the customer.

• Forms part of content for Data Migration training to IP-PLI

Purpose

• Sign off on Data Migration Plan• Confirmation from IP-PLI on preparedness of office data to

be migrated.• LAN/WAN network readiness confirmation• Command Center should be ready• List of offices identified for Data Migration as per Rollout

Plan

Entry Criteria/ Inputs

• Data Migration from PLI/RPLI to McCamish• Sign off on Reconciliation Reports

Exit Criteria/Output

Facilitation Skills Training Slide 4

Data Migration Data Flow


Data Migration Process Flow

Sign-off from IP (PLI)

-----------------------PMU – IP (PLI)

PLI to run scripts and share the discrepancy report with the circles---------------------------

IP (PLI)

Data is clean or

not?

To next phase

Data Mapping (Source System v/s Target

System)---------------------------DM Team - Infosys

Share scripts of Data Cleansing rules with

NIC/PLI---------------------------

Infosys

Data Cleansing & Enrichment

---------------------------Sys Admin – IP (PLI)

YES

NODB – Converted and Cleansed data of all HOs

Sign-off on DM Plan-Finalise DM Process -DM Training-LAN/WAN Readiness


Data Migration Process Flow…Contd.

Data Validation & Correction

-------------------------Circle Officer –

Infosys & IP (PLI)

From previous phase

Transfer PLI/RPLI DB from NIC

-------------------------DM Team - Infosys

Extract Data-------------------------DM Team - Infosys

Stage 1 Area

Transform Source Data into format as

reqd. by Target System

---------------------------DM Team - Infosys

Target Schema Tables

(Stage 2 Area)

Reconciliation-------------------------DM Team - Infosys

Data Upload-------------------------

Upload Team - Infosys

Pre-staging Area

Data Profiling Report

Reconciliation Report

Reconciliation Report

Sign-off-------------

-PMU – IP

(PLI)

McCamish Staging Area


Data Migration Process Flow…Contd.

End

Sign-off-------------

-PMU – IP

(PLI)

UAT Report

System Integration Testing

---------------------------DM Team - Infosys

Bug Fixing

User Acceptance Testing

---------------------------Zonal PMs – Infosys &

End User IP (PLI)

Trial Run------------------------DM Team - Infosys

SIT Report

Is SIT successful?

YES

NO

Is UAT successful? Bug Fixing

NO

YES

One-time activity for the selected offices

Mock Run------------------------DM Team - Infosys

Data Uploading - Final

------------------------DM Team - Infosys

McCamish Tables

From previous phase


Data Migration Process Description

• Identifying source tables from PLI/RPLI system• Identifying source tables from McCamish system• Perform data mapping exerciseData Mapping

Data Cleansing

• Data will be extracted from the pre staging area. After validation and correction using validation engine the content of DB would be replicated to Stage 1 area for data transformation process

• Data Transformation is the process of applying a set of rules to bring PLI/RPLI data to the same format as the McCamish . After transformation the Data will be inserted to the Stage 2 area and thereafter uploading to McCamish Staging Area

Data Extraction, Transformation

and Loading

• Sharing of PLI/RPLI Data cleansing scripts to NIC by Infosys .NIC will share the discrepancy reports to Circle offices after executing the scripts

• Data will be cleansed and enriched with the help of Data Enrichment Cleansing Rules by DoP

• The cleansed DB will be transferred to the pre staging area


Data Migration Process Description…Contd.

• The reconciliation reports will be generated and validated before the uploading process

• In the Upload process data will be loaded to Stage 2 Area

• From Stage 2 area, data will be further migrated to production

• Trial migration will happen for selected offices

• Mock migration will happen across offices

Data Extraction,

Transformation and Loading (Cont.)

• After trial migration, system integration testing will be performed which will be followed by mock migration .After mock migration, user acceptance testing will be performed.

• After UAT, data will be further migrated to production

User Acceptance testing and Final Upload


Roles and Responsibilities

OWNERS RESPONSIBILITIES

INFOSYS Resource Management ,project planning and coordination with different teams

Perform Requirements Gathering and Data Mapping Exercise

Data Transformation , Loading to McCamish

Generation of Reconciliation reports and Data validation

Issue Analysis and Resolution

Participate in UAT

Provide Remote Support to PO's post Migration

DOP Data cleansing of electronic data - Based on business rules shared

Data Extraction from Legacy system for conversion to PLI/RPLI system

Data Validation , Reconciliation reports Signoff

Participate in UAT and Sign off

Confirmation on Office Readiness for migration

Sign off on Migrated Data


Premium Collection after Data Migration roll-outs

(Till entire circle gets migrated)


PLI – DATA CLEANSING


Data Discrepancy Report


Data Issues

Policy Status not known or is incorrect in system

Pay Mode is Null

Medical is Null or is Invalid

DO Code is Null

Spouse DOB is Null (YS)

Invalid Gender

Invalid Category

Difference between DOB and DOA is more than 45 years (CWLA Policies) .

Policies with loan amount less than 1000.


Data Cleansing

Infosys provided data cleansing scripts to DoP to generate policy wise data discrepancy report for Pilot offices

DoP to get those scripts run and share discrepancy report with respective offices

To run these scripts, appropriate access to database is required

Cleansing is to be done manually mostly by referring to case files and/or related ledger / table

Refer to data cleansing rules for more details in share point


DATA MAPPING


S.No. Table Name Description

1Agent sanction detailIt Stores the detail of agent Incentive with circle and division wise

2Agent sanction masterIt stores the agent code and admissibility no and sanction no for agent incentive

3Agent seq Used for agent sequence no generation4APP_DET Appointee details5ASSIGN_SEQ Used for sequence no in policy assignment6CHILD Child Policy Details

7CON_TAB Conversion for sum assured before 20088DOCTOR Doctor Master Details9DO_DATA Development Officer Details

10FILE_INFO CSV File uploading details from HPO(in posting mofule)11FUND_FLOW_STATUS Store fund flow entry from HPO

12FUND_FLOW_STATUS_HIST Updation stores in history13HPO HPO Schedule Data

14HPO_UAStore UA settlement CSV file uploading through UA offline Software

15INDREG Indexing Information16INDREG_HIST Index Register History

PLI Schema



17INTEREST_TAB Temporary table used for interest calculation

18IN_TAB Used for interest calculation storage

19IRREG_DET Round of value or excess amount stored

20KLC_DET Premium Ledger Data

21KLC_DET_HIST Store KLC updation history

22LAST_DATE Last Premium Detail

23LOAN_DET Detail of first loan transaction

24LOAN_DET_HIST Loan detail history

25LOAN_DET_S Detail of second loan transaction

26LOAN_LEDGER Loan Repayment Detail

27LOAN_LEDGER_HIST Loan ledger updation history

28MEDICAL_PAYMENT Medical payment entry by Division. to DPLI

29MISC_RECEIPT Misc receipt entry by Division to DPLI

30MLOG$_POL_DET1 Log table for customer portal materialized view data

31MLOG$_POL_DET2 Log table for customer portal materialized view data

PLI Schema



32MV_LOG_DTL For error tracking of customer portal (MV)33MV_SUMMARY_CLAIM Used for MIS purpose claim (MV)34MV_SUMMARY_POL Materialized view for MIS reports at directorate level

35MV_SUMMARY_SURVIVAL_LOAN

Table used for survival & loan MIS reports at directorate level(MV)

36NEWPOL_DET Policy Details Master Data - 337NEWSEQ Key_id Sequence Number38NE_TAB Exit Policy Details39NE_TAB_HIST Store deleted / updated data40NOMINEE_DETAIL Nominee Details41NOMINEE_DETAIL_HIST Store updation in nominee details42PAO_DET Postal Account Office Master Data43POL_ASSIGN_DTL Store policy assignment details44POL_CONVERSION Store policy conversion details45POL_DET1 Policy Details Master Data - 146POL_DET2 Policy Details Master Data - 247POL_DET_HIST Keep track of key fields date updation48POST_IRREG_DTL Store irregular amount at schedule posting

PLI Schema



49POST_LOG_DTL Keep track of CSV file mismatch while uploading by HPO

50PO_DET Post office details - cash recovery

51REFUND_DTL Excess Premium Refund details

52REVIVAL_DTL Revival sanction entry

53REVIVAL_DTL_HIST History of revival detail

54SCHEDULE cash/pay schedule ment)(Receipt & Pay

55SCHEDULE_DEL Policy deletion by HO for wrong schedule uploading

56SCH_HIST Consolidated schedule history monthly

57SEQNO_CHILD Sequence Number for child policy

58SEQNO_GEN Sequence Number for general policy

59SPOUSE Yougal surksha Spouse details

60UA_DET Unadjusted Policy Information

61SUMMARY_V MIS Purpose ( Materialized View)

62UA_SETTL_DTL Store settled policy details

PLI Schema


McCamish Modules

PMACS - Agency Management and compensation System

NBF – New Business Fulfillment

VPAS – Customer, Policy, Billing and other financial details


Questions

Data Migration Process. Facilitation Skills Training Table of Contents Purpose and Prerequisites...

Documents

Transcript of Data Migration Process. Facilitation Skills Training Table of Contents Purpose and Prerequisites...