RE: GP LAv4 to LAV7.

7 Data Migration
Malapajo 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
Walter
07/08/2014 02:25 PM
Cc:
"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

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

Name

Position

Comments

2 of 29
a11/p11

Signature

Date

25/11/2015, 14:13:54

Document Distribution
No.

Recipient Name

Program Role/ Work stream

Document Change Record

Version

1.

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 Lim

Revised after business users meeting on 22

July 2015

28 July 2015

0.4

Thomas Lim & Wong

Sing Fei

Minor changes

28 July 2015

0.5

Wong Sing Fei

Updated 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 Fei

Minor update based on input from business

leads

6 August 2015

1.0

Wong Sing Fei

Update version for sign off

10 August 2015

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.....................................................................................................................................................16
3 of 29 25/11/2015,

14:13:54 a11/p11

9.2.
RECONCILIATION REPORTS..............................................................................................................................16
9.2.1.
Client Reconciliation Report..................................................................................................................16
9.2.2.
New Business Reconciliation Report......................................................................................................17
9.2.3.
Underwriting Reconciliation Report......................................................................................................17
9.2.4.
Policy Servicing Reconciliation Report.................................................................................................18
9.2.5.
Actuarial Reconciliation Report.............................................................................................................18
9.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

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.
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:

4 of 29 25/11/2015,
14:13:54 a11/p11

Overall Data Migration Process Flow

5 of 29 25/11/2015,
14:13:54 a11/p11

1.3

Takaful Terminologies
CONVENTIONAL
Master Policy
Master Policy Holder
Life Insured/ Assured
Loan
Proposal/ Application
Proposer/ Applicant
Policy Owner
Life Insured
Name- Life Insured (1)
Name- Life Insured (2)
Account Holder
Life Assurance Premium
Life Insurance/ Assurance
Payee
Basic Insurance/Assurance
Basic Premium
Certificate of Insurance
Co-Insuranse
Company
First Premium Receipt
Insurance
Cost of Insurance
Interest Rate
Period of Insurance
Payor
Policy
Policy Document
Premium
Premium Due
Type of Assurance
Premium direction
Reinsurance/ Reassurance
Reinsurer
Shariah
Standard Life
Substandard Life
Sum Assured
Sum Reassured
Total Amount Due
Unallocated Premium
Material Fact

2.

TAKAFUL TERM
Master Certificate
Master Certificate Holder
Participant
Financing
Application
Applicant
Certificate Owner
Participant
Name- Participant (1)
Name- Participant (2)
Account Holder
Family Takaful Contribution
Family Takaful
Payee
Basic Cover
Basic Contribution
Certificate of Takaful
Co-Takaful
Takaful Operator
First Contribution Receipt
Takaful
Tabarru'
Profit Rate
Period of Takaful
Contributor
Certificate
Certificate Document
Contribution
Contribution Due
Type of Takaful
Contribution direction
Re Takaful
Re takaful Operator
Shariah
Standard Person
Substandard Person
Sum Covered
Sum Retakaful
Total Contribution Due
Wakalah Fees
Material Fact

Scopes of Data Migration

This section describes the scopes of the Data Migration.

6 of 29 25/11/2015,
14:13:54 a11/p11

2.1

Data scopes Inclusion

Product Scope in Phase 1a
SN
o

Product Type

Product Name

Source
System

Group ordinary family

AutoSecure-I (HPRTT/AmAuto Life-i)

AmPTS

Group ordinary family

FinanceSecure-I (PFRTT)

AmPTS

Group ordinary family

HomeSecure-I (MRTT)

AmPTS

Group ordinary family

ProtectSecure-i Ismah

Manual

Group ordinary family

GroupSecure-I (GTT)

Manual

Individual ordinary family endowment

ProtectCare-I Shield (AmTakaful

Shield)

AmPTS

Individual ordinary family endowment

ProtectCare-I Guard (AmTakaful

Protector)

AmPTS

Individual ordinary family endowment

ProtectCare-I Prime

AmPTS

Investment-linked

WealthCare-i Style (AmTakaful

Lifestyle)

AmPTS

10

Investment-linked

WealthSecure-I Invest (AmLifestyle

Invest-i)

AmPTS

11

Investment-linked

GoldenCare-I Style (AmTakaful

Lifestyle Single)

AmPTS

12

Investment-linked

GoldenSecure-I Style (AmLifestyle

Invest-i)

AmPTS

13

Investment-linked

EduCare-I Pendidikan (AmTakaful

Pendidikan)

AmPTS

14

Individual Invest-linked Riders

Others

Contribution Waiver Rider

AmPTS

15

Individual Invest-linked Riders

Others

Payor Waiver Rider

AmPTS

16

Individual Invest-linked Riders

Medical and Health

Medical Cover Rider

AmPTS

17

Individual Invest-linked Riders

Personal Accident / Disability

Personal Accident Rider

AmPTS

18

Individual Invest-linked Riders

Medical and Health

Hospital Benefit Rider

AmPTS

19

Individual Invest-linked Riders

Dread Disease

Critical Illness Payor Waiver Rider

AmPTS

20

Individual Ordinary Family Riders

Others

PrimeSaver Rider

AmPTS

21

Individual Ordinary Family Riders

Dread diseases

Participant CI Rider

AmPTS

22

Individual Ordinary Family Riders

Others

Contributor Rider

AmPTS
7 of 29 25/11/2015,

14:13:54 a11/p11

23

Individual Ordinary Family Riders

Dread diseases

Contributor CI Rider

AmPTS

*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

8 of 29 25/11/2015,
14:13:54 a11/p11

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.
3.1

Data Migration Strategy

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.
9 of 29 25/11/2015,

14:13:54 a11/p11

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.
The following diagrams show how the data migration process will take place.
AMPTS/Manual Files Extraction Processes

10 of 29 25/11/2015,
14:13:54 a11/p11

Integral LIFE Data migration

Data
migration
Files

4.

Cutover Strategy
We will convert AMPTS data in a single data migration run during the cutover.
11 of 29 25/11/2015,

14:13:54 a11/p11

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 wont 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

P2

P3

A System freeze. No access to production system

B Data Migration and reconciliation
C Cut-over to new system. Perform catch up since freeze period

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.
12 of 29 25/11/2015,

14:13:55 a11/p11

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 wont anticipate that many of such cases.

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.

13 of 29 25/11/2015,
14:13:55 a11/p11

7.

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 wont 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.

Data Migration Deliverables

The key deliverables of Data Migration phases are as follows:
No

Phase

Description of deliverables

Data migration data

analysis

Approach Paper

Data migration data files

and fields mapping

Data mapping documents

Data migration
development and testing
Develop data migration
reconciliation procedures

Functional specifications
Technical specifications
Data migration reconciliation
procedures
Data migration reports formats

Data Cleansing

Data cleansing strategy

Data migration testing

Data migration SIT test plan

Data migration SIT test
reconciliation reports

Data migration trial runs

Data migration trial run plan

Main
Responsibility
CSC/AmMetLife
AmReady Data
migration Team
CSC/AmMetLife
AmReady Data
migration Team
CSC Team
CSC/AmMetLife
AmReady Data
migration Team
AmMetLife
AmReady Data
migration Team/
Users
AmMetLife
AmReady Data
migration Team
CSC/AmMetLife
14 of 29 25/11/2015,

14:13:55 a11/p11

8.

Final data migration

Data migration trial run

reconciliation reports
Final data migration plan
Final data migration reconciliation
reports
Final signoff

AmReady Data
migration Team
CSC/AmMetLife
AmReady Data
migration Team

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.
15 of 29 25/11/2015,

14:13:55 a11/p11

Ensure infrastructure availability to support Data Migration activities.

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

16 of 29 25/11/2015,
14:13:55 a11/p11

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.

17 of 29 25/11/2015,
14:13:55 a11/p11

9.

Data Reconciliation Process

9.1. Procedure

CP3

CP2
CP1

AMPTS Production

Staging Files

Integral LIFE Production

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 Reports

The 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

18 of 29 25/11/2015,
14:13:55 a11/p11

9.2.1. Client Reconciliation Report (Draft)

These are summary of count for Client details

Data Ownership: Operations
No
.
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15

Description

Remark

Client
Sex
Marital Status
Race
Country Code
Nationality
Email Address
Contact No 1 - Home
Contact No 2 Office
Contact No 3 Mobile
Occupation
Old NRIC
New NRIC
Others NRIC
Salutation

Total No. split by Client Type ( e.g. Personal Client, Despatch Client)
Total No. split by Sex (including unknown)
Total No. split by Status
Total No. split by Race
Total No. split by Code
Total No. split by Nationality
Total No.
Total No.
Total No.
Total No.
Total No. split by Occupation (including Blank)
Total No.
Total No.
Total No.
Total No. split by Salution (including Blank)

9.2.2. New Business Reconciliation Report (Draft)

These are summary count by contract type/component code

Data Ownership: New Business
No
.
1
2
3
4
5
6
7
8
9
10
11

Description

Remark

Life Assured
Joint-Life Assured ( if any )
Life Assured's Gender
Joint-Life Assured's Gender ( if any )
Basic Sum Assured
Premium Amount ( Basic Premium )
Premium Amount ( Loading Premium )
Life Assured's Race
Joint-Life Assured's Race ( if any )
Inforce Policies
Lapsed Policies LESS THAN or EQUAL 2
years

Total No.
Total No.
Total No. split by Gender, including Unknown
Total No. split by Gender, including Unknown
Total Amount
Total Amount excluding Loading Premium
Total Amount
Total No. split by Race
Total No. split by Race
Total No.
Total No.

9.2.3. Underwriting Reconciliation Report (Draft)

These are summary count by contract type/component code

Data Ownership: Underwriting
No.

Description

Remark

19 of 29 25/11/2015,
14:13:55 a11/p11

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

Total No.

Standard Acceptance
WITH (standard premium)
AND (substandard reasons OR LIAM codes)
Sub-standard Acceptance with Basic Plan
Sub-standard Acceptance with TPD
Sub-standard Acceptance with CI
Sub-standard Acceptance with CI Waiver
Sub-standard Acceptance
WITH (loading premium OR exclusion)
AND (without substandard reasons)
AND (without LIAM codes)

Total No.

Sub-standard Acceptance
WITH (loading premium OR exclusion)
AND (substandard reasons OR LIAM codes)

Total No.

3
4
5
6
7

Total No.
Total No.
Total No.
Total No.
Total No.

20 of 29 25/11/2015,
14:13:55 a11/p11

9.2.4. Policy Servicing Reconciliation Report (Draft)

These are summary count by contract type/component code

Data Ownership: Policy Admin
No
.
1
2
3
4
5
6
7
8
9
10

Description

Remark

Policy Number
Policy Status
Policy Expiry (YYYYMM)
Rider Expiry (YYYYMM)
Payment Method
Payment Mode (Single Premium)
Payment Mode (Regular Premium)
Premium-in-Suspense
APL
Policy Loan

Total No.
Total No. split by Status
Total No. split by Expiry Year/Month
Total No. split by Expiry Year/Month
Total No. split by Method
Total No.
Total No. split by Mode
Total Amount
Total Amount
Total Amount

9.2.5. Actuarial Reconciliation Report (Draft)

These are summary count by contract type/component code

No.
1
2
3

Description
Initial Sum Assured
Current Sum Assured
Entry Age

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

4
5

Entry Date
Policy Term

6
7

Maturity Date
Premium Paying Term

8
9

Premium Cease Date

Sex

Total No. split by entry year

1) Total No.
2) By term range ( e.g. 1 ~ 5 year )
Total No. split by maturity year
1) Total No.
2) By term range ( e.g. 1 ~ 5 year )
Total No. split by Cease Year
1) Total No
2) Split by sex (including unknown)
3) Split by Life1 and Life2, if any

10

Modal Premium

11

Premium Mode

12

Substandard Premium

13

PA Balance/Unit Balance
(including accumulated
fund at start)
Accrued bonus (NA for Takaful)
Policy Status (e.g. IF, Paid Up )

14
15

1) Total Amount including Substandard Premium

2) Split by Premium Mode ( including Single Premium )
Total No. split by Premium Mode ( including Single
Premium )
Total Amount split by Health Loadings and Occupational
Loadings
Total Amount
Total Amount
Total No. split by status
21 of 29 25/11/2015,

14:13:55 a11/p11

16

Total No. split by interest

18

Loan Interest (mortgage interest

for credit term life)
Defer Period (Mortgage Plans
only)
Smoker status

19

Occupational Class

Total No. split by Occupational Class ( including Blank )

20

Unit Balance (UL product only)

Total Unit

17

Total No. by defer period

Total No. split by smoker status

9.2.6. Finance Reconciliation Report (Draft)

These are summary account balances by sub-account code/type and component code
Data Ownership: Finance reporting
No.
1
2
3
4
5
6
7
8
9

Description
Contract Suspense (LP/S)
Premium income (LE/LP)
Commission Expense

Remark
Total Amount
Total Amount
Total Amount

Commission Payable
Loan principal
Loan interest
Tabarru/COI
Wakalah/non-invest
Claim expense

Total Amount
Total Amount (NA for Takaful)
Total Amount (NA for Takaful)
Total Amount
Total Amount
Total Amount

10. Data Migration Risk and Mitigation

No.
1

Risks
Single Release Data Migration
approach can pose some risks.

Mitigations
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.

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.

Slow decision-making from related

1. Project open issues tracking.

22 of 29 25/11/2015,

14:13:55 a11/p11

project teams and Business Users.

2. Escalate to higher management.

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.
2. Escalate to management for additional
resources if necessary.

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.

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

Manual Data Migrations could take

longer time to complete.

1. Track and analyse progress on weekly

basis.
2. Escalate to management for additional
resources if necessary.

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.

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.

11. Acceptance Criteria

No.
1.

Acceptance Criteria
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
23 of 29 25/11/2015,

14:13:55 a11/p11

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.

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.

13. Appendixes
Appendix 1a Contract Type Mapping
AMPTS
AutoSecure-i (HPRTT/AmAuto Lifei)
FinanceSecure-i (PFRTT)
HomeSecure-i (MRTT)
ProtectSecure-i Ismah
GroupSecure-i (GTT)
Retakaful Accepted
ProtectCare-i Shield (AmTakaful
Shield)
ProtectCare-i Guard (AmTakaful
Protector)
ProtectCare-i Prime
WealthCare-i Style (AmTakaful
Lifestyle)
WealthSecure-i Invest (AmLifestyle
Invest-i)
GoldenCare-i Style (AmTakaful

C01
C02
C03
G01
G02

E01
E02
E03
I01
I02
I03

Integral LIFE
AutoSecure-i (HPRTT/AmAuto Lifei)
FinanceSecure-i (PFRTT)
HomeSecure-i (MRTT)
ProtectSecure-i Ismah
GroupSecure-i (GTT)
Retakaful Accepted
ProtectCare-i Shield (AmTakaful
Shield)
ProtectCare-i Guard (AmTakaful
Protector)
ProtectCare-i Prime
WealthCare-i Style (AmTakaful
Lifestyle)
WealthSecure-i Invest (AmLifestyle
Invest-i)
GoldenCare-i Style (AmTakaful
24 of 29 25/11/2015,

14:13:55 a11/p11

Lifestyle Single)
GoldenSecure-i Style (AmLifestyle
Invest-i)
EduCare-i Pendidikan (AmTakaful
Pendidikan)

I04
I05

Lifestyle Single)
GoldenSecure-i Style (AmLifestyle
Invest-i)
EduCare-i Pendidikan (AmTakaful
Pendidikan)

25 of 29 25/11/2015,
14:13:55 a11/p11

Appendix 1b Component Type Mapping

TBHPRT1
TBHPRT2
TBPF1
TBPF78W
TBPF78M
TBPF78X
TBPF78Z
TBPF78BR
TBMRT1
AmIsmah
GTT
TAORAP1 Plan 1
TAORAP2 Plan 2
TAORAP3 Plan 3
TBORAP1
- Plan 1
TBORAP2
- Plan 2
TBORAP3
- Plan 3
TAORPP1
TAULAL1
TBULAL1
TBULAL2
TAULED1
TAULAL2
TSEC
TPSEC
TMED1
TMED2
TMED3
TMED4
TPA1
THBR1
THBR2
THBR3
THBR4
TPCI
TPSR1
TPCIR1
TCR1
TCCIR1
TFB1
TCI+
TPWC

AMPTS
AutoSecure-i (HPRTT/AmAuto Life-i)
AutoSecure-i (HPRTT/AmAuto Life-i)
FinanceSecure-i (PFRTT)
FinanceSecure-i (PFRTT)
FinanceSecure-i (PFRTT)
FinanceSecure-i (PFRTT)
FinanceSecure-i (PFRTT)
FinanceSecure-i (PFRTT)
HomeSecure-i (MRTT)
ProtectSecure-i Ismah
GroupSecure-i (GTT)
ProtectCare-i Shield (AmTakaful
Shield)
ProtectCare-i Shield (AmTakaful
Shield)
ProtectCare-i Shield (AmTakaful
Shield)
ProtectCare-i Guard (AmTakaful
Protector)
ProtectCare-i Guard (AmTakaful
Protector)
ProtectCare-i Guard (AmTakaful
Protector)
ProtectCare-i Prime
WealthCare-i Style (AmLifestyle
Invest-i)
WealthSecure-i Invest (AmLifestyle
Invest-i)
GoldenSecure-i Style (AmLifestyle
Invest-i)
EduCare-i Pendidikan (AmTakaful
Pendidikan)
GoldenCare-i Style (AmTakaful
Lifestyle Single)
Contribution Waiver Rider
Payor Waiver Rider
Medical Cover Rider 1
Medical Cover Rider 2
Medical Cover Rider 3
Medical Cover Rider 4
Personal Accident Rider
Hospital Benefit Rider 1
Hospital Benefit Rider 2
Hospital Benefit Rider 3
Hospital Benefit Rider 4
Critical Illness Payor Waiver Rider
PrimeSaver Rider
Participant CI Rider
Contributor Rider
Contributor CI Rider
Funeral Benefit
Critical Illness Rider
Payor Benefit Rider

OAS1
OAS2
OFS1
OFS2
OFS3
OFS4
OFS5
OHS1
OPI1
OGT1
OPS1
OPS2
OPS3
OPG1
OPG2
OPG3
OPP1
IWC1
IWS1
IGS1
IEC1
IGC1
ICW1
IPW1
IMC1
IMC2
IMC3
IMC4
IPA1
IHB1
IHB2
IHB3
IHB4
IDW1
OPR1
OPD1
OCR1
OCD1
OFB1
IDD1
IPB1

Integral LIFE
AutoSecure-i (HPRTT/AmAuto Life-i)
AutoSecure-i (HPRTT/AmAuto Life-i)
FinanceSecure-i (PFRTT)
FinanceSecure-i (PFRTT)
FinanceSecure-i (PFRTT)
FinanceSecure-i (PFRTT)
FinanceSecure-i (PFRTT)
FinanceSecure-i (PFRTT)
HomeSecure-I (MRTT)
ProtectSecure-i Ismah
GroupSecure-I (GTT)
ProtectCare-i Shield (AmTakaful Shield)
ProtectCare-i Shield (AmTakaful Shield)
ProtectCare-i Shield (AmTakaful Shield)
ProtectCare-i Guard (AmTakaful
Protector)
ProtectCare-i Guard (AmTakaful
Protector)
ProtectCare-i Guard (AmTakaful
Protector)
ProtectCare-i Prime
WealthCare-i Style (AmLifestyle Investi)
WealthSecure-i Invest (AmLifestyle
Invest-i)
GoldenSecure-i Style (AmLifestyle
Invest-i)
EduCare-i Pendidikan (AmTakaful
Pendidikan)
GoldenCare-i Style (AmTakaful Lifestyle
Single)
Contribution Waiver Rider
Payor Waiver Rider
Medical Cover Rider 1
Medical Cover Rider 2
Medical Cover Rider 3
Medical Cover Rider 4
Personal Accident Rider
Hospital Benefit Rider 1
Hospital Benefit Rider 2
Hospital Benefit Rider 3
Hospital Benefit Rider 4
Critical Illness Payor Waiver Rider
PrimeSaver Rider
Participant CI Rider
Contributor Rider
Contributor CI Rider
Funeral Benefit
Critical Illness Rider
Payor Benefit Rider
26 of 29 25/11/2015,

14:13:55 a11/p11

Accidental Hospital Benefit 1

Accidental Hospital Benefit 2
Accidental Hospital Benefit 3
Accidental Hospital Benefit 4

THBA1
THBA2
THBA3
THBA4

OHB1
OHB2
OHB3
OHB4

Accidental Hospital Benefit 1

Accidental Hospital Benefit 2
Accidental Hospital Benefit 3
Accidental Hospital Benefit 4

Appendix 2 Issues & Agreed

File

Field

DM
File

Not Match

Defaul
t

Resolution

27 of 29 25/11/2015,
14:13:55 a11/p11

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:

28 of 29 25/11/2015,
14:13:55 a11/p11

Appendix 4 List of Data Mapping Files

AmMetLife MY
Migration Data Sets - 20150729.xlsx

29 of 29 25/11/2015,
14:13:55 a11/p11