SBV Data Migration

Analysis & Design

Information in this document is subject to change without notice.

No part of this document may be reproduced or transmitted in any form or by any means, for any purpose,
without the express written permission of TEMENOS HEADQUARTERS SA.

COPYRIGHT 2007 - 2008 TEMENOS HEADQUARTERS SA. All rights reserved.

 TABLE OF CONTENTS

ABOUT THIS DOCUMENT .......................................................................................................................................................3

DOCUMENT HISTORY .............................................................................................................................................................3

DOCUMENT SIGNOFF ..............................................................................................................................................................3

KEY CONTACTS ........................................................................................................................................................................3

1. Introduction ..........................................................................................................................................................................4

2. Data Migration Process ........................................................................................................................................................4

3. Data Migration Approach....................................................................................................................................................5

3.1. Generic T24 Migration Approach ...................................................................................................................................5

3.2. Target system based Approach .......................................................................................................................................5

3.3. Cut/Switch over and data migration time window ........................................................................................................5

4. T24 system readiness ............................................................................................................................................................6

5. Data Migration Methodology ..............................................................................................................................................7

6. Data Migration Scope...........................................................................................................................................................8

6.1. Out of Scope ......................................................................................................................................................................8

7. Data Mapping Process .........................................................................................................................................................8

8. Other project aspects ...........................................................................................................................................................8

9. Deliverables ...........................................................................................................................................................................8

TEMENOS Confidential Page 2 of 8 5/20/2015

ABOUT THIS DOCUMENT

PURPOSE

The purpose of this document is to detail data migration Approach, Process, Methodology which will be adopted by
FPT in SBV Data migration to T24.

SCOPE

The scope of this document is limited to the activities specific for Data Migration only.

DOCUMENT HISTORY

Whenever there is a change in the requirement, record the changes by assigning a SUB SECTION.

Date Version Author Sub Section Section’s Amended

Name
5-5-2015 1.0 Karthik Initial Version

DOCUMENT SIGNOFF

The requirement sign off details should be updated in the below table.

Date Version Client Name Temenos

KEY CONTACTS

Fill in the Business/Technical Key contacts from your side for the proposed Interface

Name Business/Technical Email Phone

Karthik Project Manager rkarthik@temenos.com

TEMENOS Confidential Page 3 of 8 5/20/2015

1. Introduction
This document outlines the Data migration Approach, Process and Methodology that would be adopted by FPT
in SBV Client System to T24 R14. The define approach is achieved in a smooth and accurate manner with
minimal upheaval to the business. This document is prepared by Temenos based on the discussing the best
practices with FPT.

2. Data Migration Process

Temenos Data Migration (TDM) follows industry standard process of Extraction, Transformation and loading
process for migrating data from client system to T24. The industry standard processes are perfected based on
TDM past experience and best practice from other implementation sites to meets the migration requirement for
T24.

Fig.1

TDM ETL process is divided into three stages namely

1. Preparation - focusing on mapping client system information and T24 and developing Data Extraction
Program

2. Execution – Creating staging area, Data Transformation and cleansing

3. Control – Loading data into T24.

TEMENOS Confidential Page 4 of 8 5/20/2015

3. Data Migration Approach
3.1. Generic T24 Migration Approach

The generic rule or approach of load is derived based on the usage of standard migration process and on
the experience and know-how out of the repeated execution of the best practices.

The Generic approach is derived considering the below few listed facts, this would get modified during the
life span.

 Big-Bang or Phased migration possibility

 Cut/Switch over and data migration time window
 T24 System readiness
 Extract Transform Load (ETL) logic – Single/Multi Cutover Window
 Multi-company & Multi-book approaches of migration
 Multiple table migration in a single load
 Migration of past financial transaction from Client System
 Migration of future dated financial transaction from Client System
 Handling the interest accruals for the live contracts
 T24 load dependency
 Business unit wise approach and rule
 Stages in data transition
 Data File for Load

3.2. Target system based Approach

FPT will follow a Target base approach of mapping all client system information against T24. This
approach will bring all mandatory information required for T24 and Exterminating unwanted client system
data during system transformation process.

Based on the mapped information client system extraction logic, creating staging area, applying
transformation rules should be taken care. All data should be prepared in form of a flat file (data file) as per
T24 require format.

3.3. Cut/Switch over and data migration time window

It is the defined time for achieving the data migration during the Cutover or Go-Live. The entire cutover
process starting from closing the bank business on last working day (in Client T24 system, mostly a
weekend day) and till the opening of bank business (in target T24, on the working day following the
weekend) should happen within the limited and agreed time-window accurately. This include the roll back
operation and hence the go or no go live in T24 on Cut-over day and business decision need to be taken
on the previous working day.

TEMENOS Confidential Page 5 of 8 5/20/2015

4. T24 system readiness
The environments setup has to be determined earlier to decide the following,

 Software and data base used

o The target T24 system needs to be identified and prepared with all the required
parameters.

o A separate environment will be used for the T24 system for the migration activities, which
will be cloned as on the bank date decided for the migration testing or the cutover bank
date for T24. This is due to the less volume of data and can be handle the backup and
restore without affect the cutover time line.

o To allocate the respective disk space or archival of client data to load huge volume of data.

 Number of CPU in the T24 system

o To determine the maximum number of agents to be used in multi thread processing

o The production infrastructure will be used for the migration activities and no specific
requirement is foreseen now and will be revisited after the migration testing

 The environment pre requisite document would be prepared by client data migration team and
would be the first task to check the pre requisite in the migration environment; therefore the area
should be setup with those pre requisites. The T24 parameter pre requisite and migration specific
pre requisite would be check by client business and data migration team. Below are listed few area
pre requisites

o Full rights to Migration user to the area (Read & Write)

o No exceptions in the target environment

This would be taken care by the bank while creating the environments

 With respect to environment management a pre-production area (with same or latest software
level) can be maintained and the migration environment can be a copy of the same.

The target T24 system date for migration is Saturday as the technical working day.

TEMENOS Confidential Page 6 of 8 5/20/2015

5. Data Migration Methodology
FPT will follow below TDM recommended Data Migration Methodology.

TEMENOS Confidential Page 7 of 8 5/20/2015

6. Data Migration Scope
Based on the discussion with FPT IT and business team, following are T24 modules and tables identified as
part of migration scope.

TDM SBV R14

Migration Module List.xlsx

6.1. Out of Scope

The following items are out of scope of this document:

 Data Extraction
 Data cleansing
 Data transformation
 Decommissioning of legacy systems
 All other interfacing systems

7. Data Mapping Process

Mapping of client system information will be carried out in stages

1. Mapping all core fields R13 for above modules

2. Local development application and fields will be mapped based on FSD and TSD availability.

3. Mapping verification and correction for all local development and fields on R14 system build delivery.

8. Other project aspects

1. A manual migration approach will be adopted where volumes are too low.
2. Based on discussion with respective business user no historic data migration will be migrated.
3. Migration testing will take place on T24 Initial System Build (ISB) until build is delivered.

9. Deliverables
Following analysis and design document are delivered to SBV
Analysis
1. Temenos Data Migration Approach, Process, Methodology.
2. Temenos Data Migration Practice handbook.
Design
3. SBV Migration table scope
4. R14 Data Mapping Sheets (DMS) for table scope.

TEMENOS Confidential Page 8 of 8 5/20/2015