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

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 NO DB – 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 ------------------------- Stage 1 Area Transform Source Data into format as reqd. by Target System --------------------------- Target Schema Tables (Stage 2 Area) Reconciliation ------------------------- Data Upload ------------------------- Upload Team - Infosys Pre-staging Area Data Profiling Report Reconciliation Report Sign-off -------------- PMU – IP (PLI) McCamish Staging Area Data Migration Process Flow…Contd.

Data Migration Process Flow…Contd. From previous phase Trial Run ------------------------ DM Team - Infosys One-time activity for the selected offices Sign-off -------------- PMU – IP (PLI) SIT Report System Integration Testing --------------------------- DM Team - Infosys UAT Report Mock Run ------------------------ DM Team - Infosys User Acceptance Testing --------------------------- Zonal PMs – Infosys & End User IP (PLI) Bug Fixing YES Is SIT successful? NO Bug Fixing Is UAT successful? NO Data Uploading - Final ------------------------ DM Team - Infosys YES End McCamish Tables

Data Migration Process Description Identifying source tables from PLI/RPLI system Identifying source tables from McCamish system Perform data mapping exercise Data 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 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

PLI Schema S.No. Table Name Description 1 Agent sanction detail It Stores the detail of agent Incentive with circle and division wise 2 Agent sanction master It stores the agent code and admissibility no and sanction no for agent incentive 3 Agent seq Used for agent sequence no generation 4 APP_DET Appointee details 5 ASSIGN_SEQ Used for sequence no in policy assignment 6 CHILD Child Policy Details 7 CON_TAB Conversion for sum assured before 2008 8 DOCTOR Doctor Master Details 9 DO_DATA Development Officer Details 10 FILE_INFO CSV File uploading details from HPO(in posting mofule) 11 FUND_FLOW_STATUS Store fund flow entry from HPO 12 FUND_FLOW_STATUS_HIST Updation stores in history 13 HPO HPO Schedule Data 14 HPO_UA Store UA settlement CSV file uploading through UA offline Software 15 INDREG Indexing Information 16 INDREG_HIST Index Register History

PLI Schema S.No. Table Name Description 17 INTEREST_TAB Temporary table used for interest calculation 18 IN_TAB Used for interest calculation storage 19 IRREG_DET Round of value or excess amount stored 20 KLC_DET Premium Ledger Data 21 KLC_DET_HIST Store KLC updation history 22 LAST_DATE Last Premium Detail 23 LOAN_DET Detail of first loan transaction 24 LOAN_DET_HIST Loan detail history 25 LOAN_DET_S Detail of second loan transaction 26 LOAN_LEDGER Loan Repayment Detail 27 LOAN_LEDGER_HIST Loan ledger updation history 28 MEDICAL_PAYMENT Medical payment entry by Division. to DPLI 29 MISC_RECEIPT Misc receipt entry by Division to DPLI 30 MLOG$_POL_DET1 Log table for customer portal materialized view data 31 MLOG$_POL_DET2

PLI Schema S.No. Table Name Description 32 MV_LOG_DTL For error tracking of customer portal (MV) 33 MV_SUMMARY_CLAIM Used for MIS purpose claim (MV) 34 MV_SUMMARY_POL Materialized view for MIS reports at directorate level 35 MV_SUMMARY_SURVIVAL_LOAN Table used for survival & loan MIS reports at directorate level(MV) 36 NEWPOL_DET Policy Details Master Data - 3 37 NEWSEQ Key_id Sequence Number 38 NE_TAB Exit Policy Details 39 NE_TAB_HIST Store deleted / updated data 40 NOMINEE_DETAIL Nominee Details 41 NOMINEE_DETAIL_HIST Store updation in nominee details 42 PAO_DET Postal Account Office Master Data 43 POL_ASSIGN_DTL Store policy assignment details 44 POL_CONVERSION Store policy conversion details 45 POL_DET1 Policy Details Master Data - 1 46 POL_DET2 Policy Details Master Data - 2 47 POL_DET_HIST Keep track of key fields date updation 48 POST_IRREG_DTL Store irregular amount at schedule posting

PLI Schema S.No. Table Name Description 49 POST_LOG_DTL Keep track of CSV file mismatch while uploading by HPO 50 PO_DET Post office details - cash recovery 51 REFUND_DTL Excess Premium Refund details 52 REVIVAL_DTL Revival sanction entry 53 REVIVAL_DTL_HIST History of revival detail 54 SCHEDULE cash/pay schedule ment)(Receipt & Pay 55 SCHEDULE_DEL Policy deletion by HO for wrong schedule uploading 56 SCH_HIST Consolidated schedule history monthly 57 SEQNO_CHILD Sequence Number for child policy 58 SEQNO_GEN Sequence Number for general policy 59 SPOUSE Yougal surksha Spouse details 60 UA_DET Unadjusted Policy Information 61 SUMMARY_V MIS Purpose ( Materialized View) 62 UA_SETTL_DTL Store settled policy details

McCamish Modules PMACS - Agency Management and compensation System NBF – New Business Fulfillment VPAS – Customer, Policy, Billing and other financial details