1. technology and computing
2. software
3. databases

Validata Connectivity (V-Conn)
Achieve full control of the migration process, reducing risk on go-live
Agenda
1
Challenges with T24 Migration
2
Validata Approach
3
Validata Methodology
4
V-Conn Overview
5
ABN AMRO Bank Migration Project
6
Benefits
Challenges with T24 Migration
Implementation is extremely
complex and business critical
Data migration is not agile based and
doesn't support Business-IT
collaboration
Mapping multiple core
banking legacy systems into
a single platform system
Challenges data profiling, data
quality & data governance
impacting go-live timelines
No formal migration methodology or
methodology integrated with the implementation
& delivery methodology of T24
Financial loss in the accounting book
due to inaccurate data mapping and
extract specification
Maintenance of delta logs
(data) while conducting
multiple mocks
Unscheduled downtime to
Legacy Services and semiautomated procedures
Engagement from Legacy & T24,
Business & IT subject matter
experts (SMEs), impact time &
cost to engage related resources
Migration is usually seen as one-off activity
leading to a scripted approach with limited
reusability, high risks, longer implementation
plans
Validata Approach
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 data
o When doing the import, V-Conn can do the cleansing and validation of the
imported data
o 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 jobs
o Following to the migration, a reconciliation of the migrated data in all ETL
processes can be achieved
Sample ETL Steps methodology
Automatic validation
of data mapping prerequisite worksheet
Extraction Source 1
Task
Validata
Adapter
Validata
Engine
Stage 1
Extracted data and
Validation Log
Data migration
risks and
mitigation plan
Transformation
Task
Data mapping
templates and
tables
Transformation
Engine
Reporting
Adapter
Stage 2
Transformation Data
and Transformation
Log
Data migration
risks and
mitigation plan
Load in T24
Task
Validata
Adapter
Stage 3
Transformation Data
and Transformation
Log
Load Data
Data migration
risks and
mitigation plan
Target System
V-Conn Features
Data Extraction & Loading
Online & offline data extraction and loading from multiple applications
within the same framework
Data Transformation
Validata Mapping Schemas define the mapping and transformation rules.
Data Profiling
Key item for archiving is to identify and understand all relationships in
data
Creates and replicates tables from the legacy systems, storing the data
information accordingly and providing reporting on top of them.
Data Archiving
Prebuilt Migration Mappings forT24
Validation
Scheduling & Job Sequencing
Pre built business mapping knowledge for T24
Field and Data Validation for completeness, proper context, rules
validation and attributes value validation
The migration jobs can be scheduled for single or a repetitive execution
at specified date and time.
Synchronization Service
Real time synchronization of data between two systems
Process Control & Audit
Full audit trail and control over the migration process
Consolidation Reporting
Data import and consolidation from heterogeneous data sources and
from many different applications and platforms
Reconciliation Reporting
Generation of automated reconciliation reports
T24 Reporting Testing
CRF reporting testing and Balance sheet revaluation testing
Validata ETL Migration Process
Control and Audit Mechanism
Validata
Adapter
Validation
and Data
Cleansing
Engine
Mapping
Schemas
Validata
Adapter
Mapping
Schemas
Validata Staging
Area & Data
Warehouse
Report ,
Warnings,
Rejections
Legacy
Mapping
Schemas
Reconciliation
Engine
Business
Model
Report ,
Warnings,
Rejections
T24
Reconciliation
Engine
Mapping
Schemas
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.
Transaction
Monitor
Adapter
80% reduction
in current time
to test
T24 Adapter
50% faster time
to market
80% reduction
in current spend
on testing
30% increase in
productivity
Data Base
Adapters
Generic
Adapters
T24 Java API
Adapter
(CSV, xml, flat files)
Validata Migration Project Steps
Analysis
(scoping)
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
Design
Activities

Review BRDs, FSDs & T24
Build

Design Workshop


ETL Design

Migration Versions
Design


Migration Strategy

Reconciliation Strategy

Tracker with open issues
& challenges
Reconciliation Design
Deliverables


Project Plan
Detailed Mapping Tracker

Deliverables

Identify T24 Gaps
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)
Build
Activities
Testing
Activities
Go Live
Activities

Development

Functional Testing.

Perform Data Migration

Migration testing

UAT.

ETL Support

Functional Testing
scoping and test cases
preparation.

Dress Rehearsals

Auto Reconciliation

Recovery Plan preparation


Go Live Plan preparation
Business Reconciliation
Support.
Deliverables
Deliverables
Deliverables

Updated DMSs

ETL scripts

Functional Test Logs

Reconciliation scripts

UAT Logs

Migration Versions

Dress Rehearsals Summary
Reports

Unit test cases and Test
Logs

Defect Logs

Recovery & Go Live Plans

Test cases for Functional
Testing.

Auto reconciled T24
system
• Define the source
• Define the filtering
criteria
• Select the extraction
process
• Select the pre-created
mapping rules
• Execute the extraction
process
• Review and reject or
accept the results
Benefits
• Continuous and online
extraction from
multiple sources
through Online High
Performance Staging
Area
• On line extraction:
connecting directly on
the source using the
pre-built adapters
• Off line extraction:
using extracted file
formats
• The delta migration is
extracting only the
changed and new
records from the
source system
• Live synchronization
process for data
extraction
Process
Multi Level Data Extraction
Data Extraction Engine
• Fully automated
extraction process,
results in reducing
the total effort of the
extraction process
• The pre-built Validata
integration with the
legacy systems
reduces the total cost
of investment of the
whole migration
project
• Through the
synchronization and
incremental update
processes the
extraction of accurate
data during are
ensured
• Business Rules setup
at File level and Field
level
• Mandatory/Optional
setup
• Critical/Non Critical
Rules setup
• Field/File Format
restrictions setup
• Threshold setup for
warning and rejection
mechanism
• Reject records
populated into Audit
Tables with
justifications
• Reject records fixed
and Partial File can be
reprocessed
Benefits
• File validation
• Check for Availability of
required files by Modules
• Check for Source data file
format In expected
Standard format
• Check for Total record
count as Specified in
Controller
• Check for Duplicate
records
• Field validation
• Check for mandatory and
Optional Data
• Check for source Field
correctness based on
Available business rules
• Populate Default Values
wherever not available
and Possible based on
Business Rules
• Dependency validation
• Check for Source data
referential Integrity
across Files
Process
Multi Level Data Validation
Data Validation Engine
• Configurable Thru
Control Tables and
Files
• Customization
based on required
Legacy Source
system and target
T24 Version
• Framework for
Automated Import of
Associated Data
Objects
• Target Format
definitions setup at
File level and Field
level
• Load data to the T24
in validate mode for
migration testing
• Load data to T24 using
T24 migration versions
• Reconciliation
reporting of the data
transformation and
load phases
Benefits
• Field level reformat as
required by T24
• Minimum and Maximum
Field lengths
• Regeneration of required
T24 IDs
• Multi-value Field Setups
• Check for Duplicate
records
• File level Formats
• Structure files as required
by T24 Data Migration
Tool
• Breakup into Multiple
files wherever required
• File Split and parallel files
for performance
• Support for Data Migration
Tool (optional)
• Pre-created Data
Mapping definitions for
standard file formats as
required by DMT
Process
T24 Specific Re-Formatting
Data Transformation and Load Engine
• Configurable Thru
Control Tables and
Files
• Customization
based on required
Legacy Source
system and target
T24 Version
• Customize Existing
T24 Data
Migration tool
definitions
• Predefined formats
of reconciliation Files
by module
• Comparison utility to
reconcile Source and
T24 Data
• Predefined
Reconciliation
reports by Module
• Internal T24 Audit log
reports to
additionally validate
correctness of loaded
information
Benefits
• Nature of reconciliation
• Qualitative reconciliation
• Quantitative reconciliation
• Reconciliation Data
Extraction Process
• Identified set of
reconciliation data needs
by Module.
• Generation of Standard
reconciliation files from
Legacy Source and Target
Temenos T24
• Reconciliation Reports
• Predefined Set of recon
reports by Module to
validate success of
Migration
• File comparison Utility to
reconcile Source extracted
data with T24 Loaded
Data.
• T24 Audit log reports
Process
Reconciliation
Reconciliation Engine
• Provides a portfolio of predefined reconciliation
reports for every migration
step
• Multistage (Extraction,
transformation etc)
Reconciliation, for both
technical and business level.
• It is bundled with a number
of financial reconciliation
reports that could be used
for financial reconciliation
as well (e.g Contingent/Non
Contingent entries, Total
debit/Total credit).
• A reconciliation engine and
reconciliation report writer
enables business and IT to
define new reports without
coding
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
• Priority definition of
Various Modules
• Defining dependencies in
the Migration execution
process
• Multiphase
Implementation
definitions
• Dependencies
• Audit Information
• Threshold definitions
controls
• Start – Stop mechanisms,
Hard and Soft Restart
• Monitoring Start and Stop
times
• Notification to concerned
Groups depending on
success or failures
• Controls at
granularity of Module
level as well as
Individual File level
• Setup done in files or
tables to define the
entire sequence and
mandatory
dependencies
• Notification process
setup based on need
• Scheduled migration
tasks are created to
follow the migration
process
automatically.
Benefits
• End to end Process
Sequence
Process
Control Mechanisms
Process Control Engine
• Customizable
based on
Implementation
needs
• Configurable for
Big bang or Phased
implementations
V-Conn IT Audit Support
Key Issues








Data misfeeds
Lack of data / transaction
integrity
Loss of critical data
Unencrypted sensitive
information
Data variances between sources
and target system
Invalid, incompleteness and
inadequate interfaces and their
related controls
Lack of Business / IT alignment
Non compliance to regulatory
requirements
Data Validation &
Integrity
Application
Security
Configuration
Review
IT General
Controls
Post Data
Conversation
Review
Transaction
Integrity Review
Reporting
Accuracy
Interface Control
Testing
V-Conn IT Audit Support
Methodology













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
Benefits






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
Key Differentiators





Data Validation and Integrity
Transaction Integrity
Data Flow Validation
Interface Controls
Data Conversation Review
Benefits
Save up to 60% of
the time for all
migration stages
Time reduction of the
migration setup and
preparation by 70%
Avoid costs for
additional archiving
storage and software
90% reduction of time and
cost for establishing the
connectivity to the legacy
system
50% faster time
to Market
30% increase in
productivity
20% increase in
project success
Save up to 50% time
for the reports
preparation
Up to 5 times
faster creation
of mappings
Automatic Vs Semi -Automatic Migration
0%
Reusability
67% Cut
Down Cost
due to
Reusability
Roll Out
Reconciliation
Test
Development
Analysis
Engagement
C
O
S
T
$$$
Roll Out -50%
Reconciliation -60%
Test -75%
Development -70%
Analysis -65%
Engagement -65%
Semi- Automatic Migration
Automatic Migration
C
O
S
T
$$
Data source –
Transaction data
Extracted data
Load data
Target System
Validata adapters
Transformed
data
Validata Staging Area
Validata adapters
Reconcile data
Data source –
Static data
Reconcile data
Reconciliation Diagram
Data source –
Transaction data
Stage1 – Extraction
Reconciliation
Validata adapters
Target System
Stage2-Transformation
Reconciliation
Load data
Transformed
data
Extracted data
Validata Staging Area
Validata adapters
Data source –
Static data
Reconciliation Framework
Stage3 – Load
Reconciliation
Reconciliation for this stage is
populating report based on
comparison between extracted Legacy
data. Also all mismatches as per
business validation rules.
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.
Direct Migration
Extract
Transform
Load
Reconciliation Diagram
Reconciliation Framework static Data
Stage1 – Extraction
Reconciliation
500.000 Customers
Stage2-Transformation
Reconciliation 500.000
Customer
Stage3 – Load
Reconciliation
500.000 Customer
Stage4 - Reconcile
500.000 Customer
Reconciliation for this stage will be
based Data cleansing rules on
Sector(Integer and in between specific
range), Address( Specific Length).
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.
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
Stage2-Transformation
Reconciliation 750.000
FUNDS TRANSFER
Stage3 – Load
Reconciliation
750.000
FUNDS.TRANSFER
Stage4 - Reconcile
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)
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.
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
78% Cut
Down cost
0%
Reusability
Roll Out
Reconciliation
Test
Development
Analysis
Engagement
Migration Phase 1
Roll Out -60%
Reconciliation -80%
Test -85%
Development -75%
Analysis -80%
Engagement -85%
Migration Phase 2
*Scenario where the same legacy system across locations is used