aml takaful dm approachscope paper v1.0

RE: GP LAv4 to LAV7.7 Data MigrationMalapajo Mart Reinier to:Paner Julius Gerald, Thomas K Lim, Jonathan M Timkang, Jinkee M Guerrero, Dela Cruz Mercedes, Villanueva Nixon, Jardino Noemi Amor, Marcelo Rolando, Navarro Walter07/08/2014 02:25 PMCc:"Hornilla Antonio Feliciano"Hide Details From: "Malapajo Mart Reinier" <mramalapajo@Life Insurance.com.ph> Sort List...

To: "Paner Julius Gerald" <jghpaner@Life Insurance.com.ph>, Thomas K Lim/MYS/CSC@CSC, Jonathan M Timkang/SGP/CSC@CSC, Jinkee M Guerrero/PHL/CSC@CSC, "Dela Cruz Mercedes" <mmdelacruz@Life Insurance.com.ph>, "Villanueva Nixon" <nsvillanueva@Life Insurance.com.ph>, "Jardino Noemi Amor" <naujardino@Life Insurance.com.ph>, "Marcelo Rolando" <rcmarcelo@Life Insurance.com.ph>, "Navarro Walter" <wmnavarro@Life Insurance.com.ph>

Cc: "Hornilla Antonio Feliciano" <aahornilla@Life Insurance.com.ph>

3 Attachments

image001.png

image002.png

DATA MIGRATION APPROACH & SCOPE PAPER

AMMETLIFE TAKAFUL

Version : 1.00.6 (DraftFinal)

Creation Date : 16 July 2015

Last Updated : 103 August 2015

2 of 45 22/04/2023, 2:07:49 AM




3 Attachments

image001.png

image002.png

Document Sign-Off (Names may need to be reviewed prior to Sign-Off)

Name Position Comments Signature Date

Document Distribution

No. Recipient Name Program Role/ Work stream

Document Change Record

Version Author(s) Change Reference Date

0.1 Thomas Lim Initial version 16 July 2015

0.2 Wong Sing Fei Added some section 2.1 and minor changes 16 July 2015

0.3 Thomas LimRevised after business users meeting on 22 July 2015

28 July 2015

0.4Thomas Lim & Wong Sing Fei

Minor changes 28 July 2015

0.5 Wong Sing FeiUpdated based on Takaful Business Leads input

31 July 2015

0.6 Wong Sing Fei Minor update on product name 3 August 2015

0.7 Wong Sing FeiMinor update based on input from business leads

6 August 2015

1.0 Wong Sing Fei Update version for sign off 10 August 2015

4 of 45 22/04/2023, 2:07:49 AM




3 Attachments

image001.png

image002.png

1. INTRODUCTION..................................................................................................................................................4

1.1 PURPOSE............................................................................................................................................................4

1.2 OVERVIEW........................................................................................................................................................4

1.3 TAKAFUL TERMINOLOGIES.......................................................................................................................5

2. SCOPES OF DATA MIGRATION......................................................................................................................6

2.1 DATA SCOPES INCLUSION...........................................................................................................................6

2.2 DATA SCOPES EXCLUSION..........................................................................................................................8

3. DATA MIGRATION STRATEGY.......................................................................................................................9

3.1 AMPTS DATA MIGRATION TO INTEGRAL LIFE...................................................................................9

4. CUTOVER STRATEGY.....................................................................................................................................10

5. DATA CLEANSING............................................................................................................................................11

6. DATA MIGRATION ASSUMPTIONS..............................................................................................................12

7. DATA MIGRATION DELIVERABLES...........................................................................................................13

8. ROLES AND RESPONSIBILITIES...................................................................................................................14

9. DATA RECONCILIATION PROCESS............................................................................................................16

9.1. PROCEDURE.....................................................................................................................................................169.2. RECONCILIATION REPORTS.............................................................................................................................16

9.2.1. Client Reconciliation Report..................................................................................................................169.2.2. New Business Reconciliation Report......................................................................................................179.2.3. Underwriting Reconciliation Report......................................................................................................179.2.4. Policy Servicing Reconciliation Report..................................................................................................189.2.5. Actuarial Reconciliation Report.............................................................................................................189.2.6. Finance Reconciliation Report...............................................................................................................19

10. DATA MIGRATION RISK AND MITIGATION........................................................................................20

11. ACCEPTANCE CRITERIA............................................................................................................................22

12. CHANGE MANAGEMENT............................................................................................................................23

13. APPENDIXES...................................................................................................................................................24

APPENDIX 1A – CONTRACT TYPE MAPPING...................................................................................................24

APPENDIX 1B – COMPONENT TYPE MAPPING................................................................................................25

APPENDIX 2 – ISSUES & AGREED........................................................................................................................26

APPENDIX 3 – DATA CLEANING & SET-UP BEFORE CUT-OVER...............................................................27

APPENDIX 4 – LIST OF DATA MAPPING FILES................................................................................................28

6 of 45 22/04/2023, 2:07:49 AM




3 Attachments

image001.png

image002.png

1. Introduction

This document gives an overview on Data Migration approach, scope and activities for AmMetLife Takaful.

1.1 Purpose

The purpose of this document is to cover the Data Migration approach for migrating Takaful data residing in AMPTS (DB2 Unix based) life administration system and manual data files to Integral LIFE.

Limited Data Cleansing

AMPTS DM Team Clarify any issues

with AmMetLife for

business decisions

Data migration Testing

Develop Reconciliation

Procedures

AMPTS DM Team Maps

Fields Internally with

CSC

Data migration

Development and Testing

Final Data migration

Data migration

Files Fields Mapping

CSC Team Prepares Functions

Specification

Data migration

Data Analysis

Data migration Trial

Runs

CSC Team Walkthrough

functional Specifications

with AmMetLife (if

required)

Overall Data Migration Process Flow

However, Takaful business will be migrated first in Phase 1a while the rest Conventional business will be migrated in Phase 1b.

1.2 Overview

Data migration involves a set of activities that moves data from one or more systems (Source System), namely AMPTS, to a new system, i.e. Integral LIFE (Target System). The purpose of data migration is to preserve core business data and make it accessible from Integral LIFE system to allow business processing to continue on new systems.

Overall Data Migration activities are depicted in the following diagram flow:

8 of 45 22/04/2023, 2:07:49 AM




3 Attachments

image001.png

image002.png

1.3 Takaful Terminologies

CONVENTIONAL TAKAFUL TERMMaster Policy Master CertificateMaster Policy Holder Master Certificate HolderLife Insured/ Assured ParticipantLoan FinancingProposal/ Application ApplicationProposer/ Applicant ApplicantPolicy Owner Certificate Owner

Life Insured ParticipantName- Life Insured (1) Name- Participant (1)Name- Life Insured (2) Name- Participant (2)Account Holder Account HolderLife Assurance Premium Family Takaful ContributionLife Insurance/ Assurance Family TakafulPayee PayeeBasic Insurance/Assurance Basic CoverBasic Premium Basic ContributionCertificate of Insurance Certificate of TakafulCo-Insuranse Co-TakafulCompany Takaful OperatorFirst Premium Receipt First Contribution ReceiptInsurance TakafulCost of Insurance Tabarru'Interest Rate Profit RatePeriod of Insurance Period of TakafulPayor ContributorPolicy CertificatePolicy Document Certificate DocumentPremium ContributionPremium Due Contribution DueType of Assurance Type of TakafulPremium direction Contribution directionReinsurance/ Reassurance Re TakafulReinsurer Re takaful OperatorShariah ShariahStandard Life Standard PersonSubstandard Life Substandard PersonSum Assured Sum CoveredSum Reassured Sum RetakafulTotal Amount Due Total Contribution DueUnallocated Premium Wakalah FeesMaterial Fact Material Fact

10 of 45 22/04/2023, 2:07:49 AM




3 Attachments

image001.png

image002.png

2. Scopes of Data Migration

This section describes the scopes of the Data Migration.

2.1 Data scopes Inclusion

Product Scope in Phase 1a

SNo

Product Type Product NameSource System

1 Group ordinary family AutoSecure-I (HPRTT/AmAuto Life-i) AmPTS

2 Group ordinary family FinanceSecure-I (PFRTT) AmPTS

3 Group ordinary family HomeSecure-I (MRTT) AmPTS

4 Group ordinary family ProtectSecure-i ‘Ismah Manual

5 Group ordinary family GroupSecure-I (GTT) Manual

6Individual ordinary family - endowment

ProtectCare-I Shield (AmTakaful Shield)

AmPTS


ProtectCare-I Guard (AmTakaful Protector)

AmPTS


ProtectCare-I Prime AmPTS

9 Investment-linkedWealthCare-i Style (AmTakaful Lifestyle)

AmPTS

10 Investment-linkedWealthSecure-I Invest (AmLifestyle Invest-i)

AmPTS

11 Investment-linkedGoldenCare-I Style (AmTakaful Lifestyle Single)

AmPTS

12 Investment-linkedGoldenSecure-I Style (AmLifestyle Invest-i)

AmPTS

13 Investment-linkedEduCare-I Pendidikan (AmTakaful Pendidikan)

AmPTS

14Individual Invest-linked Riders Others

Contribution Waiver Rider AmPTS

15Individual Invest-linked Riders Others

Payor Waiver Rider AmPTS

16Individual Invest-linked Riders Medical and Health

Medical Cover Rider AmPTS

17Individual Invest-linked Riders Personal Accident / Disability

Personal Accident Rider AmPTS

18Individual Invest-linked Riders Medical and Health

Hospital Benefit Rider AmPTS

19Individual Invest-linked Riders Dread Disease Critical Illness Payor Waiver Rider AmPTS

20Individual Ordinary Family Riders Others

PrimeSaver Rider AmPTS

21Individual Ordinary Family Riders Dread diseases

Participant CI Rider AmPTS

22Individual Ordinary Family Riders Others

Contributor Rider AmPTS

23Individual Ordinary Family Riders Dread diseases

Contributor CI Rider AmPTS

Scopes of Data Migration 12 of 45 22/04/2023, 2:07:49 AM

*Active policies will be migrated into Integral/Life, where all future transactions will be performed in Integral/Life subsequent to the migration.Non-active policies will be migrated into Integral/Life for enquiry purpose only.

Pending proposals will be migrated into Integral/Life for future processing.Closed proposals (NTU, Postponed, Withdrawn, Declined, Cancelled) will be migrated into Integral/Life only for enquiry purpose only.

Note: *Active policies refer to policies under the status of In-force and lapsed within 3 years from the lapsed date.

Historical Data – Active Data Processing

The physical files that are categorized as active data processing will be migrated over using the data migration programs. Basically, this method will map all the fields in the AMPTS files to the Integral LIFE fields. These are files which will be migrated as an active data:

Policy related data- Client details- Client bank details- Proposal details- Contract/Certificate details- Life Assured/Participant details- Component/Benefit details- Unit link details (balances, prices) - Mortgage details- Vehicles details- Annual and life time limits for Hospital product- Waiver claim details- Future regular payments - LIAM sub-standard details- Unit prices and fund balances

Agency related data (Additional topics on data migration covered under PMACS implementation)

- Agent details- Agent commission and production data- ROC Indicator, certificate tag to agents

General ledger and financial related data- Sub-account balances- GST Invoices- Transaction details on unit movements for annual statements generation for

2016. Limited historical data (cannot be reversed, for enquiry only)

- Transaction history Transaction history data will only cover the summary level information such

as what transactions are performed on what date, by which user ID- Receipt & payments

Reinsurance data (Additional topics on data migration covered under RI system implementtion

- Existing policy level RI arrangement- Provision and payments (RI premium, recovery)


Historical Data – Static Data Enquiry

The physical files that are categorized for static data enquiry will be brought over also by data migration programs. There are 2 methods in doing this:

Map to the same active data file in Integral LIFE and then can be view automatically by Integral LIFE

Create a few new files to store static data for enquiry purposes with new special submenu.

2.2 Data Scopes Exclusion

1. Parameter files (parameter tables ie. products & rules) will not be migrated. It will be manually setup in Integral LIFE

2. Reinsurance will not be migrated since reinsurance will be handled outside Integral LIFE. Reinsurance data will be migrated into a new separate RI system.

3. Reports and Correspondences

4. For policy schedule reprint of AMPTS policies, Integral LIFE will have a function to create policy schedule letter group type for the user to choose from the PC Print submenu. The format of policy schedule will be used same format with the production format and with the current up-to-date data available in the system.

5. Claims details, except for H&S annual limit and life time limit and future regular claims. The implication of the closed/reopened claim effect on the annual and lifetime limit will be accounted as part of data mapping exercise.

6. Any other data not required by Integral LIFE.





3 Attachments

image001.png

image002.png

3. Data Migration Strategy

3.1 AMPTS Data Migration to Integral LIFE

The Data Migration strategy will be based on ‘file-to-file’ data migration approach. The extracted data will be stored in an intermediate staging database before the files are migrated to Integral LIFE.

File-to-file data migration approach is normally adopted due to its lower cost and less complexity. AmMetLife Takaful will provide extraction files from AMPTS system.

Extract ProgramAMPTS Intermediate

Library

Migration Process

Reconciliation Process

Integral LIFE

Manual files

The following diagrams show how the data migration process will take place.

AMPTS/Manual Files Extraction Processes


Policies/Certificates

Mapped into Integral LIFE Mapped into

Integral LIFE

Account Balances Mapping

Exception List

Client Detail

Reconciliation Process

Policy Coverage

/Rider Details

Account Balance

Integral LIFE Data migration


Data migration

Files




3 Attachments

image001.png

image002.png

4. Cutover Strategy

We will convert AMPTS data in a single data migration run during the cutover.

Single data migration run is proposed as it is in line with Integral LIFE base policy of not having co-existence. Incremental data migration approach is not recommended as it will take longer to complete, requires extended efforts of data migration and reconciliations putting unnecessary pressure on business users and technical resources.

We propose that a sufficient freeze period (if any, will try not to have this when possible) is imposed prior to the final cutover date to allow sufficient time for the whole of Data Migration exercises to complete.

During this freeze period, the processing of new applications will cease in the existing system and to continue again in the new system after the cutover. Any existing applications being processed must be completed by the date we start the freeze period.

At this juncture, the recommended time frame for freeze period is not yet known until the full data migration test is done. From experiences, there won’t be any freeze period since most of data migration program(s) have sufficient time to complete either during weekend or long weekend or public holidays.

On the final cutover date, it is recommended that the business be closed earlier, say half day, to allow ample time for finishing the end of day processing in the existing system before the final Data Migration takes place.

In the worst case scenario where the final data migration failed, the contingency plan is to revert to AMPTS and then re-plan another cut-over time.

It is also advisable to cut-over to the new system after the month end processing in the existing system.

The following scenario explains what may happen during the cutover:


P1 P3P2

CBA

A System freeze. No access to production systemB Data Migration and reconciliationC Cut-over to new system. Perform catch up since freeze period




3 Attachments

image001.png

image002.png

5. Data Cleansing

Data will be migrated based on “As-Is” basis.

We will perform common logical validation to ensure that migrated data values are the same in both source and target systems.

There will be no validation done during the data migration process itself and but there will be manual validations as part of reconciliation process such as thru query and excel comparison. The criteria for validation during reconciliation will be jointly identified by

Business Users and AmMetLife Takaful BA IT Team during the development of reconciliation procedures at section 9 of this document.

We will not re-calculate any values that are transferred across in the new system, unless AmMetLife Takaful requires this and this will be documented inside mapping document.

If there is any manual adjustment required currently due to some data errors, the process shall remain the same after AMPTS data are fully migrated to Integral LIFE.

Limited data cleansing will be performed on mandatory data to ensure continuing functions in Integral LIFE. Whenever possible, Data Migration Team will assist to write scripts to fix any mandatory data errors provided that Business Users can advise the Data migration Team on the business rules to fix such errors. After the script is run, Business Users is responsible to verify, check and confirm the correctness of the data cleansed in this manner.

If automated ways of fixing any mandatory data errors is not possible due to any reason, Business Users will have to perform the data cleansing manually. We won’t anticipate that many of such cases.





3 Attachments

image001.png

image002.png

6. Data Migration Assumptions

Following assumptions are made for Data Migration project:

Integral LIFE will not allow reversals since accounting transaction history is not migrated (unless for those transactions specifically identified for the need of reversal, which will be discussed further.

Historical Data Inquiry for Transaction History, Receipt and Payments will be available for enquiry purpose only.

AmPTS system will be kept online post migration for one year post cutover. Before the system is decommissioned, a full system image backup will be obtained. This image will be made available for restoration when the need arised.

Claims experience data extract for Actuarial analysis on historical data will be performed before the AmPTS is decommissioned.

Accounts with balances will be migrated and mapped to Integral LIFE account codes. Financial history is available for enquiry purpose only.

Based on data migration cut-off date, bill-to-date (BTD) will be defaulted to paid-to-date (PTD); all billing will be generated from Integral LIFE thereafter and reprinting of premium notices should be suppressed.

Additional table fields in Integral LIFE which are currently not available in AMPTS will be migrated as Blank if there is no validation required in Integral LIFE.

Product will be migrated based on product mapping requirement (which is attached in the Appendix 1a-c).

There won’t be any data migration for claims details except for H&S annual limit and life time limit. If any outstanding claims in legacy system should register again in Integral LIFE for processing.

Users are able to run queries on the static data that were brought over for inquiry

Prior to data migration all direct debit and credit card extracted billing has to be returned and processed.

Old certificate number will be migrated into Integral/Life. There will be functionality to search contract using old and new policy number.





3 Attachments

image001.png

image002.png

7. Data Migration Deliverables

The key deliverables of Data Migration phases are as follows:

No Phase Description of deliverables Main Responsibility

1 Data migration data analysis

Approach Paper CSC/AmMetLife AmReady Data migration Team

2 Data migration data files Data mapping documents CSC/AmMetLife

and fields mapping AmReady Data migration Team

3 Data migration development and testing

Functional specificationsTechnical specifications

CSC Team

4 Develop data migration reconciliation procedures

Data migration reconciliation proceduresData migration reports formats

CSC/AmMetLife AmReady Data migration Team

5 Data Cleansing Data cleansing strategy AmMetLife AmReady Data migration Team/ Users

6 Data migration testing Data migration SIT test planData migration SIT test reconciliation reports

AmMetLife AmReady Data migration Team

7 Data migration trial runs Data migration trial run planData migration trial run reconciliation reports


8 Final data migration Final data migration planFinal data migration reconciliation reportsFinal signoff






3 Attachments

image001.png

image002.png

8. Roles and Responsibilities

Data migration Team (made up of Technical and Business Representative Teams) comprises of various internal and vendor teams and shall be responsible for Data Migration activities based on scopes defined.

Technical Team (Data Migration, Infa-structure, Vendors)

Plan, manage, coordinate and involve in all Data Migration related activities.

Perform migration data analysis.

Perform migration data files and fields mapping.

Ensure all data and tables for both Integral LIFE and AMPTS, whether migrated or not migrated are documented. Justification is provided if data not migrated.

Manage Data Migration risks and appropriately highlight to management any risk that may have impact on project delivery schedule, quality and cost.

Prepare functional specifications & technical specifications (if any).

Perform data migration programs development and testing.

Perform development of data migration reconciliation procedures & reports.

Perform actual data migration and provide support for the data migration testing.

Perform actual data migration and provide support for the data migration trial runs.

Perform actual data migration and provide support for the final Data Migration.

Manage, track and resolve all Data Migration related issues throughout the project phases.

Ensure all documentations produced are adequate and of acceptable standards.

Prepare data migration development and testing environments as specified by Data Migration Team.

Ensure infrastructure availability to support Data Migration activities.

Assist in resolving infrastructure related issues that can impact Data Migration.

Roles and Responsibilities 27 of 45 22/04/2023, 2:07:50 AM

Business LeadsTeam

Jointly involve in data migration data analysis.

Jointly involve in data migration files and fields mapping, providing business knowledge support roles to the Technical Team.

Assist to check on all migrated and not migrated data related to business, highlight issues arise and provide impact analysis to the Technical Team.

Investigate and analyse data issues, assist Technical Team to identify data cleansing requirement.

Communicate any changes in Integral LIFE applications that may affect Data Migration to the Technical Team.

Review functional specifications and ensure all details are documented.

Walk-through functional specifications with Business Users.

Jointly involve in development of data migration reconciliation procedures and defining report formats.

Jointly involve in the data migration testing and trial runs and validating output (data and reports) of migrated data.

Jointly involve in the final Data Migration and validating output (data and reports) of migrated data.

Jointly provide post-production support for the agreed time frame.

Provide answers and decisions to clarification documents prepared by data migration team

Involve in the walkthrough of data migration functional specifications with data migration team

Involved in data cleansing activities (if required)

Jointly involve in the development of reconciliation procedures

Jointly involve in the reconciliation process during data migration testing (SIT and ST) and trial runs and validating output of migrated data.

Jointly involve in the final Data Migration and validating output of migrated data.

Roles and Responsibilities 28 of 45 22/04/2023, 2:07:50 AM




3 Attachments

image001.png

image002.png

9. Data Reconciliation Process

9.1. Procedure

AMPTS Production

Staging Files

Integral LIFE Production

CP1

CP3

CP2

CP1 – Reconciliation check between Integral LIFE Staging data and AMPTS Production (will be done by AmMetLife Takaful).CP2 – Balancing check between Integral LIFE Staging and Integral LIFE Production (will be done by CSC).CP3 – Verification check (will be done by AmMetLife Takaful).

9.2. Reconciliation ReportsThe following reconciliation reports are grouped by various functional areas; where each area a data owner from the business department is assigned for the purpose of data verification and reconciliation.

The following reconciliation reports are drafts and for reference purpose. Actual requirements on reconciliation reports will be covered as part of the Business Requirement Documentation process

9.2.1. Client Reconciliation Report (Draft)

These are summary of count for Client detailsData Ownership: Operations

No. Description Remark1 Client Total No. split by Client Type ( e.g. Personal Client, Despatch Client)2 Sex Total No. split by Sex (including unknown)3 Marital Status Total No. split by Status4 Race Total No. split by Race5 Country Code Total No. split by Code6 Nationality Total No. split by Nationality7 Email Address Total No.8 Contact No 1 - Home Total No.9 Contact No 2 – Office Total No.10 Contact No 3 – Mobile Total No.11 Occupation Total No. split by Occupation (including Blank)12 Old NRIC Total No.13 New NRIC Total No.14 Others NRIC Total No.15 Salutation Total No. split by Salution (including Blank)

Data Reconciliation Process 30 of 45 22/04/2023, 2:07:50 AM

9.2.2. New Business Reconciliation Report (Draft)

These are summary count by contract type/component codeData Ownership: New Business

No. Description Remark1 Life Assured Total No.2 Joint-Life Assured ( if any ) Total No.3 Life Assured's Gender Total No. split by Gender, including Unknown4 Joint-Life Assured's Gender ( if any ) Total No. split by Gender, including Unknown5 Basic Sum Assured Total Amount6 Premium Amount ( Basic Premium ) Total Amount excluding Loading Premium7 Premium Amount ( Loading Premium ) Total Amount8 Life Assured's Race Total No. split by Race9 Joint-Life Assured's Race ( if any ) Total No. split by Race

10 Inforce Policies Total No.11 Lapsed Policies LESS THAN or EQUAL 2

yearsTotal No.

9.2.3. Underwriting Reconciliation Report (Draft)

These are summary count by contract type/component codeData Ownership: Underwriting

No. Description Remark1 Standard Acceptance

WITH (standard premium)AND (without substandard reasons)AND (without LIAM codes)

Total No.

2 Standard AcceptanceWITH (standard premium)AND (substandard reasons OR LIAM codes)

Total No.

3 Sub-standard Acceptance with Basic Plan Total No.4 Sub-standard Acceptance with TPD Total No.5 Sub-standard Acceptance with CI Total No.6 Sub-standard Acceptance with CI Waiver Total No.7 Sub-standard Acceptance

WITH (loading premium OR exclusion)AND (without substandard reasons)AND (without LIAM codes)

Total No.

8 Sub-standard AcceptanceWITH (loading premium OR exclusion)AND (substandard reasons OR LIAM codes)

Total No.


9.2.4. Policy Servicing Reconciliation Report (Draft)

These are summary count by contract type/component codeData Ownership: Policy Admin

No. Description Remark1 Policy Number Total No.2 Policy Status Total No. split by Status3 Policy Expiry (YYYYMM) Total No. split by Expiry Year/Month4 Rider Expiry (YYYYMM) Total No. split by Expiry Year/Month5 Payment Method Total No. split by Method6 Payment Mode (Single Premium) Total No.7 Payment Mode (Regular Premium) Total No. split by Mode8 Premium-in-Suspense Total Amount9 APL Total Amount10 Policy Loan Total Amount

9.2.5. Actuarial Reconciliation Report (Draft)

These are summary count by contract type/component code

No. Description Remark1 Initial Sum Assured Total Amount2 Current Sum Assured Total Amount3 Entry Age 1) Total No.

2) By age range ( e.g. 1 ~ 10 year )3) Split by Life1 and Life2, if any

4 Entry Date Total No. split by entry year5 Policy Term 1) Total No.

2) By term range ( e.g. 1 ~ 5 year )

6 Maturity Date Total No. split by maturity year7 Premium Paying Term 1) Total No.

2) By term range ( e.g. 1 ~ 5 year )

8 Premium Cease Date Total No. split by Cease Year9 Sex 1) Total No

2) Split by sex (including unknown)3) Split by Life1 and Life2, if any

10 Modal Premium 1) Total Amount including Substandard Premium2) Split by Premium Mode ( including Single Premium )

11 Premium Mode Total No. split by Premium Mode ( including Single Premium )

12 Substandard Premium Total Amount split by Health Loadings and Occupational Loadings

13 PA Balance/Unit Balance(including accumulatedfund at start)

Total Amount

14 Accrued bonus (NA for Takaful) Total Amount15 Policy Status (e.g. IF, Paid Up ) Total No. split by status


16 Loan Interest (mortgage interest for credit term life)

Total No. split by interest

17 Defer Period (Mortgage Plans only)

Total No. by defer period

18 Smoker status Total No. split by smoker status

19 Occupational Class Total No. split by Occupational Class ( including Blank )

20 Unit Balance (UL product only) Total Unit

9.2.6. Finance Reconciliation Report (Draft)

These are summary account balances by sub-account code/type and component codeData Ownership: Finance reporting

No. Description Remark1 Contract Suspense (LP/S) Total Amount2 Premium income (LE/LP) Total Amount3 Commission Expense Total Amount

4 Commission Payable Total Amount5 Loan principal Total Amount (NA for Takaful)6 Loan interest Total Amount (NA for Takaful)7 Tabarru/COI Total Amount8 Wakalah/non-invest Total Amount9 Claim expense Total Amount





3 Attachments

image001.png

image002.png

10. Data Migration Risk and Mitigation

No. Risks Mitigations1 Single Release Data Migration

approach can pose some risks.1. Adopt proven file-to-file method of Data

Migration.2. Involve Business Representative Project

Team and Life Insurance users throughout project phases for decisions pertaining to Data Migration issues.

3. Comprehensive testing to ensure

migrated data readiness prior to UAT execution and performance testing.

2 Unavailability of key resources from different internal teams and/or Business Users due to other project and/or departmental responsibilities.

1. Distribute detailed data migration project plan to all Head of Teams in advance for resource allocation.

2. Communicate any changes in project plan as early as possible.

3. Escalate to management for additional resources if necessary.

4. Prepares action listing for the unavailable resources to act upon offline basis.

3 Slow decision-making from related project teams and Business Users.

1. Project open issues tracking.2. Escalate to higher management.

4 Lack/inability to identify backup resources to handle/resolve any sharp increase in data migration errors.

1. Prioritise errors and concentrate only on mandatory data error correction.


5 Changes in business requirements (resulting from change requests) or new enhancements impacted on Data Migration activities are not communicated clearly.

1. Establish clear project communication plan.

2. Establish cut-off point after which any changes affecting data migration will have to be addressed as change request.

6 Insufficient time in the final data migration window causing data migration failure or delay in going live.

1. Conduct comprehensive end-to-end data migration testing and trial runs to get more accurate estimation on the total time required to perform final data migration.

2. Plan for final cutover to happen during long weekend

7 Manual Data Migrations could take longer time to complete.

1. Track and analyse progress on weekly basis.


8 Inferior data quality may require data cleansing exercises to be carried out prior to final data migration. However, data cleansing is not included in the data migration budget.

1. Convert data ‘as-is’ and perform data cleansing only on mandatory data.

2. Initiate and execute data cleansing activities as early as possible.

3. Use script-based and automated data cleansing methods wherever possible, depending on the Data Migration budget.

9 New Product launches during Q3/Q4 2014 are not yet quantified in terms of likely volume of data migration required. A particularly successful product could have a major impact on data migration volumes.

1. Review product launch calendar, identify high volume product targets...

2. Review product targets for new products and identify high volume targets – plan on worst case scenario, i.e. highest volumes of data.

Data Migration Risk and Mitigation 35 of 45 22/04/2023, 2:07:50 AM




3 Attachments

image001.png

image002.png

11. Acceptance Criteria

No. Acceptance Criteria1. 100% of identified data is migrated successfully based on project scopes and time

line.

2. Migrated data passed the required output requirements and matched the reconciliation reports.

3. Data migration testing and trial runs are successfully conducted :

- The data migrations are run without errors- The flow of the test is clear- The migrated data shows proof of testing, i.e. migrated data can be used to

perform processes- Issues and defects are documented- Test results are documented- Testing stages are documented with status

4. No defects outstanding, other than those with Business and Life Insurance Data migration Team Lead approval (if any due to unforeseen reasons).

5. Agreed time frame and approach for the resolution of all outstanding defects.

6. Appropriate metrics are collected to show proof of Data Migration.

7. Data Migration Completion Report documented for sign off.





3 Attachments

image001.png

image002.png

12. Change Management

Any additional scope for Data Migration will be treated as change request and will be handled as per agreed Change Management process already established for AmMetLife AmReady project.




3 Attachments

image001.png

image002.png

13. Appendixes

Appendix 1a – Contract Type Mapping

AMPTS Integral LIFE

AutoSecure-i (HPRTT/AmAuto Life-i) C01

AutoSecure-i (HPRTT/AmAuto Life-i)

FinanceSecure-i (PFRTT) C02 FinanceSecure-i (PFRTT)HomeSecure-i (MRTT) C03 HomeSecure-i (MRTT)ProtectSecure-i ‘Ismah G01 ProtectSecure-i ‘Ismah

GroupSecure-i (GTT) G02 GroupSecure-i (GTT)Retakaful Accepted Retakaful AcceptedProtectCare-i Shield (AmTakaful Shield) E01

ProtectCare-i Shield (AmTakaful Shield)

ProtectCare-i Guard (AmTakaful Protector) E02

ProtectCare-i Guard (AmTakaful Protector)

ProtectCare-i Prime E03 ProtectCare-i PrimeWealthCare-i Style (AmTakaful Lifestyle) I01

WealthCare-i Style (AmTakaful Lifestyle)

WealthSecure-i Invest (AmLifestyle Invest-i) I02

WealthSecure-i Invest (AmLifestyle Invest-i)

GoldenCare-i Style (AmTakaful Lifestyle Single) I03

GoldenCare-i Style (AmTakaful Lifestyle Single)

GoldenSecure-i Style (AmLifestyle Invest-i) I04

GoldenSecure-i Style (AmLifestyle Invest-i)

EduCare-i Pendidikan (AmTakaful Pendidikan) I05

EduCare-i Pendidikan (AmTakaful Pendidikan)

Appendixes 41 of 45 22/04/2023, 2:07:50 AM

Appendix 1b – Component Type MappingAMPTS Integral LIFE

TBHPRT1 AutoSecure-i (HPRTT/AmAuto Life-i) OAS1 AutoSecure-i (HPRTT/AmAuto Life-i)TBHPRT2 AutoSecure-i (HPRTT/AmAuto Life-i) OAS2 AutoSecure-i (HPRTT/AmAuto Life-i)TBPF1 FinanceSecure-i (PFRTT) OFS1 FinanceSecure-i (PFRTT)TBPF78W FinanceSecure-i (PFRTT) OFS2 FinanceSecure-i (PFRTT)TBPF78M FinanceSecure-i (PFRTT) OFS3 FinanceSecure-i (PFRTT)TBPF78X FinanceSecure-i (PFRTT) OFS4 FinanceSecure-i (PFRTT)TBPF78Z FinanceSecure-i (PFRTT) OFS5 FinanceSecure-i (PFRTT)TBPF78BR FinanceSecure-i (PFRTT) FinanceSecure-i (PFRTT)TBMRT1 HomeSecure-i (MRTT) OHS1 HomeSecure-I (MRTT)AmIsmah ProtectSecure-i ‘Ismah OPI1 ProtectSecure-i ‘IsmahGTT GroupSecure-i (GTT) OGT1 GroupSecure-I (GTT)TAORAP1 - Plan 1

ProtectCare-i Shield (AmTakaful Shield) OPS1


TAORAP2 - Plan 2



TAORAP3 - Plan 3



TBORAP1 - Plan 1

ProtectCare-i Guard (AmTakaful Protector) OPG1


TBORAP2 - Plan 2



TBORAP3 - Plan 3



TAORPP1 ProtectCare-i Prime OPP1 ProtectCare-i Prime

TAULAL1WealthCare-i Style (AmLifestyle Invest-i) IWC1

WealthCare-i Style (AmLifestyle Invest-i)

TBULAL1WealthSecure-i Invest (AmLifestyle Invest-i) IWS1

WealthSecure-i Invest (AmLifestyle Invest-i)

TBULAL2GoldenSecure-i Style (AmLifestyle Invest-i) IGS1

GoldenSecure-i Style (AmLifestyle Invest-i)

TAULED1EduCare-i Pendidikan (AmTakaful Pendidikan) IEC1

EduCare-i Pendidikan (AmTakaful Pendidikan)

TAULAL2GoldenCare-i Style (AmTakaful Lifestyle Single) IGC1

GoldenCare-i Style (AmTakaful Lifestyle Single)

TSEC Contribution Waiver Rider ICW1 Contribution Waiver RiderTPSEC Payor Waiver Rider IPW1 Payor Waiver RiderTMED1 Medical Cover Rider 1 IMC1 Medical Cover Rider 1TMED2 Medical Cover Rider 2 IMC2 Medical Cover Rider 2TMED3 Medical Cover Rider 3 IMC3 Medical Cover Rider 3TMED4 Medical Cover Rider 4 IMC4 Medical Cover Rider 4TPA1 Personal Accident Rider IPA1 Personal Accident RiderTHBR1 Hospital Benefit Rider 1 IHB1 Hospital Benefit Rider 1THBR2 Hospital Benefit Rider 2 IHB2 Hospital Benefit Rider 2THBR3 Hospital Benefit Rider 3 IHB3 Hospital Benefit Rider 3THBR4 Hospital Benefit Rider 4 IHB4 Hospital Benefit Rider 4TPCI Critical Illness Payor Waiver Rider IDW1 Critical Illness Payor Waiver RiderTPSR1 PrimeSaver Rider OPR1 PrimeSaver RiderTPCIR1 Participant CI Rider OPD1 Participant CI RiderTCR1 Contributor Rider OCR1 Contributor RiderTCCIR1 Contributor CI Rider OCD1 Contributor CI RiderTFB1 Funeral Benefit OFB1 Funeral BenefitTCI+ Critical Illness Rider IDD1 Critical Illness RiderTPWC Payor Benefit Rider IPB1 Payor Benefit Rider

Appendixes 42 of 45 22/04/2023, 2:07:50 AM

THBA1 Accidental Hospital Benefit 1 OHB1 Accidental Hospital Benefit 1THBA2 Accidental Hospital Benefit 2 OHB2 Accidental Hospital Benefit 2THBA3 Accidental Hospital Benefit 3 OHB3 Accidental Hospital Benefit 3THBA4 Accidental Hospital Benefit 4 OHB4 Accidental Hospital Benefit 4

Appendix 2 – Issues & Agreed

File FieldDM File Not Match Default Resolution

Appendixes 43 of 45 22/04/2023, 2:07:50 AM

Appendix 3 – Data Cleaning & Set-up Before Cut-over***To be updated later

These are data cleaning and table set-up activities for AmMetLife Takaful before data migration batch job is run:

Appendixes 44 of 45 22/04/2023, 2:07:50 AM




3 Attachments

image001.png

image002.png

Appendix 4 – List of Data Mapping Files

aml takaful dm approachscope paper v1.0

Documents

lav4 data

data migration environment

lim jonathan

paner julius gerald

gp data migration references

gp lav4

cheds data analysis

timkang jinkee