Validata Connectivity (V-Conn)

Achieve full control of the migration process, reducing risk on go-live

Validata Approach

Validata Methodology

V-Conn Overview

ABN AMRO Bank Migration Project

1

2

3

4

5

Benefits6

Challenges with T24 Migration

Migration is usually seen as one-off activity leading to a scripted approach with limited reusability, high risks, longer implementation plans

Engagement from Legacy & T24, Business & IT subject matter

experts (SMEs), impact time & cost to engage related resources

Implementation is extremely complex and business critical

Challenges data profiling, data quality & data governance impacting go-live timelines

Data migration is not agile based and doesn't support Business-IT collaboration

Unscheduled downtime to Legacy Services and semi-

automated procedures

No formal migration methodology or methodology integrated with the implementation & delivery methodology of T24

Mapping multiple core banking legacy systems into a single platform system

Maintenance of delta logs (data) while conducting

multiple mocks

Financial loss in the accounting book due to inaccurate data mapping and extract specification

Big Bang Approach

o V-Conn will migrate all records (bulk import) from the legacy to the T24 tables or to the DWH

o Validata DB will be used as staging area for the static datao When doing the import, V-Conn can do the cleansing and validation of the

imported datao Validata will generate a reconciliation report after the migration

Phased Approach

o Special adapters will be used to extract the new and modified records and mitigate them to DWH on a daily basis

o This incremental migration will happen automatically through scheduled jobso Following to the migration, a reconciliation of the migrated data in all ETL

processes can be achieved

Automatic validation of data mapping pre-requisite worksheet

Validata Adapter

Validata EngineSource 1

Stage 1Extracted data and

Validation Log

Stage 2Transformation Data and Transformation

Log

Stage 3Transformation Data and Transformation

Log

TransformationEngine

Validata Adapter

ReportingAdapter

Target System

Load Data

Load in T24 Task

Transformation Task

Extraction Task

Data mapping templates and

tables

Data migration risks and

mitigation plan

Data migration risks and

mitigation plan

Data migration risks and

mitigation plan

Data Extraction & Loading

Data Transformation

Validation

Data Archiving

Consolidation Reporting

Reconciliation Reporting

Scheduling & Job Sequencing

Synchronization Service

Online & offline data extraction and loading from multiple applications within the same framework

Validata Mapping Schemas define the mapping and transformation rules.

Field and Data Validation for completeness, proper context, rules validation and attributes value validation

Creates and replicates tables from the legacy systems, storing the data information accordingly and providing reporting on top of them.

Data import and consolidation from heterogeneous data sources and from many different applications and platforms

Generation of automated reconciliation reports

The migration jobs can be scheduled for single or a repetitive execution at specified date and time.

Real time synchronization of data between two systems

Data Profiling

Process Control & Audit

Prebuilt Migration Mappings forT24

T24 Reporting Testing

Key item for archiving is to identify and understand all relationships in data

Pre built business mapping knowledge for T24

Full audit trail and control over the migration process

CRF reporting testing and Balance sheet revaluation testing

Control and Audit MechanismControl and Audit Mechanism

Legacy

ValidataAdapter

Mapping Schemas

Validation and Data Cleansing

Engine

Validata Staging Area & Data Warehouse

Mapping Schemas

ValidataAdapter

T24

Report , Warnings, Rejections

Report , Warnings, Rejections

Mapping Schemas

Reconciliation Engine

Reconciliation Engine

Mapping Schemas

Business Model

A cornerstone of V-Conn architecture is its system integration and interoperability features. V-Conn design is based upon the concept of a generic core that can communicate freely and

flexibly with other systems using components called adapters.

T24 Adapter

Transaction Monitor Adapter

Data Base Adapters

Generic Adapters

(CSV, xml, flat files)

50% faster time to market

30% increase in productivity

80% reduction in current spend

on testing

80% reduction in current time to

test

T24 Java API Adapter

Activities Review TAABS

Identify T24 modules

Scoping Workshop

Volume Analysis

Migration Approach

Reconciliation Approach

ETL activities agreed

Issues & challenges identified.

Tracker with open issues to be addressed prior to design workshops

Deliverables

Project Plan

Migration Strategy

Reconciliation Strategy

Tracker with open issues & challenges

Activities Review BRDs, FSDs & T24

Build

Design Workshop

Identify T24 Gaps

Detailed Mapping Tracker

ETL Design

Migration Versions Design

Reconciliation Design

Deliverables Detailed Migration

Requirements Document & Data Migration Sheets (DMSs)

Detailed Reconciliation Requirements Document

Migration Versions Requirements Document

Tracker with T24 Gaps Testing Strategy Updated Project Plan

(optional, if necessary)

Activities

Development

Migration testing

Functional Testing scoping and test cases preparation.

Deliverables

Updated DMSs

ETL scripts

Reconciliation scripts

Migration Versions

Unit test cases and Test Logs

Test cases for Functional Testing.

Activities

Perform Data Migration

ETL Support

Auto Reconciliation

Business Reconciliation Support.

Deliverables

Auto reconciled T24 system

Activities

Functional Testing.

UAT.

Dress Rehearsals

Recovery Plan preparation

Go Live Plan preparation

Deliverables

Functional Test Logs

UAT Logs

Dress Rehearsals Summary Reports

Defect Logs

Recovery & Go Live Plans

Identification of the upgrades and changes through the change management capability

Alignment of the business requirements and system design documentation to achieve effective and timely upgrade

Risk assessment and mitigation planning Check the availability and

appropriateness of business and technical operating procedures and standards

Disaster recovery and business continuity arrangements

Logical access controls Configuration Management Interfaces adapters Compliance with technical security

standards for T24 platform and database Adequacy and effectiveness of the testing

strategy and environment Service level agreements Monitoring Legal and regulatory aspects

Methodology

Proper use of IT applications and supporting systems

Increased business process efficiency and controls alignment

Check the effectiveness of business and IT risks

Check on inappropriate access granted to sensitive transactions, data and configurations

Verification of incorrect data mapping results in inaccurate processing of data or misclassification of data /accounts

Reduction of the number of manual controls and enhance reliance on automated controls

Benefits

Data Validation and Integrity Transaction Integrity Data Flow Validation Interface Controls Data Conversation Review

Key Differentiators

Semi- Automatic Migration

Engagement

Analysis

Automatic Migration

C O ST

$$$

COST

$$

Development

Test

Reconciliation

Roll Out

Engagement -65%

Analysis -65%

Development -70%

Test -75%

Reconciliation -60%Roll Out -50%

Data source –Static data

Data source – Transaction data

Valid

ata

adapte

rs

Targ

et

Syst

em

Valid

ata

adapte

rs

Valid

ata

Sta

gin

g A

rea

Extr

acte

d d

ata

Tra

nsfo

rmed

d

ata

Load

data

R

econ

cile d

ata

Reconciliation Diagram

Data source –Static data

Data source – Transaction data

Valid

ata

adapte

rs

Targ

et

Syst

em

ExtractTransformLoad

Direct Migration

Valid

ata

adapte

rs

Reconciliation Framework

Valid

ata

Sta

gin

g A

rea

Extr

acte

d d

ata

Tra

nsfo

rmed

d

ata

Load

data

R

econ

cile d

ata

Stage1 – Extraction Reconciliation

Reconciliation for this stage is populating report based on comparison between extracted Legacy data. Also all mismatches as per business validation rules.

Stage2-Transformation Reconciliation

Stage3 – Load Reconciliation

Reconciliation for this stage is populating report based on extracted transformed data. The process is using the defined business transformation rules.

Reconciliation for this stage is populating report based on data that should be loaded against data actually loaded in T24.

Stage4 - ReconcileReconciliation for this stage is populating report based extracted data from T24 against data that should have been loaded.

Reconciliation Diagram

Reconciliation Framework static Data

Stage1 – Extraction Reconciliation 500.000 Customers

Reconciliation for this stage will be based Data cleansing rules on Sector(Integer and in between specific range), Address( Specific Length).

Stage2-Transformation Reconciliation 500.000 Customer

Stage3 – Load Reconciliation 500.000 Customer

Reconciliation for this stage is populating report based on >100 business transformation rules .

Reconciliation for this stage is populating report based on Transformed data to be loaded in Target System against actual volume of data loaded.

Stage4 - Reconcile 500.000 Customer

Reconciliation for this stage is populating report based on Extraction of all Customer in T24 against the Customers that should have been loaded.

•Failover policy , the process can be done unattended.•Validation Rules easy to be maintained.•Extraction requires approximately 3 minutes.•Generation of the report plus excel export takes 10 minutes

•Failover policy , the process can be done unattended.•Transformation business rules easy to be defined and maintained.•Transformation requires approximately 2 minutes •Generation of the report plus excel export takes 10 minutes

•Failover policy , the process can be done unattended.•The expect number of loaded data is a result of previous stage outcome.•Loading requires approximately 12 minutes •Generation of the report plus excel export takes 10 minutes

•Failover policy , the process can be done unattended.•Comparison ruler(field level) are easy to be created and maintained.•Extraction of the Data takes approximately 8 minutes.•Generation of the report plus excel export takes 10 minutes•Overall time is 18 minutes fully automated process.

Reconciliation Diagram

Reconciliation Framework Dynamic Data

Stage1 – Extraction Reconciliation 750.000 FUNDS.TRANSFER

Reconciliation for this stage will be based Data cleansing rules on AMMOUNT( to be above 0),ACCOUNT ( belongs in the list of migrated acc)

Stage2-Transformation Reconciliation 750.000 FUNDS TRANSFER

Stage3 – Load Reconciliation 750.000 FUNDS.TRANSFER

Reconciliation for this stage is populating report based on >30 business transformation rules .

Reconciliation for this stage is populating report based on Transformed data to be loaded in Target System against actual volume of data loaded.

Stage4 - Reconcile 750.000 FUNDS.TRANSFER

Reconciliation for this stage is populating report based on Extraction of all Funds transfer in T24 against the Funds transfer that should have been loaded.

•Failover policy , the process can be done unattended.•Validation Rules easy to be maintained.•Extraction requires approximately 3 minutes.•Generation of the report plus excel export takes 10 minutes

•Failover policy , the process can be done unattended.•Transformation business rules easy to be defined and maintained.•Transformation requires approximately 2 minutes •Generation of the report plus excel export takes 10 minutes

•Failover policy , the process can be done unattended.•The expect number of loaded data is a result of previous stage outcome.•Loading requires approximately 15 minutes •Generation of the report plus excel export takes 10 minutes

•Failover policy , the process can be done unattended.•Comparison ruler(field level) are easy to be created and maintained.•Extraction of the Data takes approximately 15 minutes.•Generation of the report plus excel export takes 10 minutes•Overall time is 25 minutes fully automated process.

Engagement

Analysis

Development

Test

Reconciliation

Roll Out

Engagement -85%Analysis -80%Development -75%Test -85%Reconciliation -80%Roll Out -60%

Migration Phase 1 Migration Phase 2

*Scenario where the same legacy system across locations is used