by anon

Slides
26 slides

Validata_Connectivity_Product_Presentaion_(V Conn).ppt

Published Mar 26, 2013 in Business & Management
Direct Link :

Validata_Connectivity_Product_Presentaion_(V Conn).ppt... Read more

Read less


Comments

comments powered by Disqus

Presentation Slides & Transcript

Presentation Slides & Transcript

Validata Connectivity (V-Conn)
Achieve full control of the migration process, reducing risk on go-live

Agenda
Validata Approach
Validata Methodology
V-Conn Overview
ABN AMRO Bank Migration Project
1
2
3
4
5
Benefits
6
Challenges with T24 Migration

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

Validata Approach

Sample ETL Steps methodology
Validata
Adapter
Validata
Engine
Source 1
Stage 1
Extracted data and Validation Log
Stage 2
Transformation Data and Transformation Log
Stage 3
Transformation Data and Transformation Log
Transformation
Engine
Validata
Adapter
Reporting
Adapter
Target System
Load Data
Load in T24 Task
Transformation Task
Extraction Task

V-Conn Features

Control and Audit Mechanism
Validata ETL Migration Process
Legacy
Validata Staging Area & Data Warehouse
T24

V-Conn Prebuilt Adapters
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
Validata Migration Project Steps

Data Extraction Engine

Data Validation Engine

Data Transformation and Load Engine

Reconciliation Engine

Reconciliation Reports

View details for task Extract and Validate Customers

View details clicked for task Transform Customers Case 1 – details when there is no error

Process Control Engine

V-Conn IT Audit Support

V-Conn IT Audit Support

Benefits
30% increase in productivity
20% increase in project success
50% faster time to Market
Up to 5 times faster creation of mappings
Save up to 60% of the time for all migration stages
Avoid costs for additional archiving storage and software
90% reduction of time and cost for establishing the connectivity to the legacy system
Save up to 50% time for the reports preparation
Time reduction of the migration setup and preparation by 70%

Automatic Vs Semi-Automatic Migration
Semi- Automatic Migration
C O S
T
$$$
COS
T

$$

Data source –Static data
Data source – Transaction data
Validata adapters
Target System
Validata adapters

Reconciliation Diagram
Data source –Static data
Data source – Transaction data
Validata adapters
Target System
Extract
Transform
Load




Direct Migration
Validata adapters
Reconciliation Framework
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 - Reconcile
Reconciliation 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.

ROI based on Reusability for Migration Projects
*Scenario where the same legacy system across locations is used