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

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

3. Challenges with T24 Migration
Financial loss in the accounting book due to inaccurate data mapping and extract specification
Implementation is extremely complex and business critical
Data migration is not agile based and doesn't support Business-IT collaboration
Maintenance of delta logs (data) while conducting multiple mocks
Mapping multiple core banking legacy systems into a single platform system
Unscheduled downtime to Legacy Services and semi- automated procedures
Engagement from Legacy & T24, Business & IT subject matter experts (SMEs), impact time & cost to engage related resources
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
Migration is usually seen as one-off activity leading to a scripted approach with limited reusability, high risks, longer implementation plans

4. Validata Approach Big Bang Approach Phased Approach
V-Conn will migrate all records (bulk import) from the legacy to the T24 tables or to the DWH
Validata DB will be used as staging area for the static data
When doing the import, V-Conn can do the cleansing and validation of the imported data
Validata will generate a reconciliation report after the migration
Phased Approach
Special adapters will be used to extract the new and modified records and mitigate them to DWH on a daily basis
This incremental migration will happen automatically through scheduled jobs
Following to the migration, a reconciliation of the migrated data in all ETL processes can be achieved

5. Sample ETL Steps methodology
Automatic validation of data mapping pre-requisite worksheet
Validata Adapter
Validata Engine
Stage 1 Extracted data and Validation Log
Extraction Task
Source 1
Data migration risks and mitigation plan
Data mapping templates and tables
Transformation Engine
Stage 2 Transformation Data and Transformation Log
Transformation Task
Reporting Adapter
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

6. V-Conn Features Data Extraction & Loading Data Transformation
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
Data Archiving
Creates and replicates tables from the legacy systems, storing the data information accordingly and providing reporting on top of them.
Prebuilt Migration Mappings forT24
Pre built business mapping knowledge for T24
Validation
Field and Data Validation for completeness, proper context, rules validation and attributes value validation
Scheduling & Job Sequencing
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

7. Validata ETL Migration Process
Control and Audit Mechanism
Validata
Adapter
Mapping Schemas
Validation and Data Cleansing Engine
Mapping Schemas
Validata
Adapter
Validata Staging Area & Data Warehouse
Report , Warnings, Rejections
Report , Warnings, Rejections
Business Model
Legacy
T24
Mapping Schemas
Reconciliation Engine
Reconciliation Engine
Mapping Schemas

8. 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 (CSV, xml, flat files)
T24 Java API Adapter

9. Validata Migration Project Steps
Analysis (scoping)
Design
Build
Testing
Go Live
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
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
Activities
Perform Data Migration
ETL Support
Auto Reconciliation
Business Reconciliation Support.
Deliverables
Auto reconciled T24 system

10. Data Extraction Engine
Multi Level Data Extraction
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
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
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

11. Data Validation Engine
Multi Level Data Validation
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
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
Configurable Thru Control Tables and Files
Customization based on required Legacy Source system and target T24 Version

12. Data Transformation and Load Engine
T24 Specific Re-Formatting
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
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
Configurable Thru Control Tables and Files
Customization based on required Legacy Source system and target T24 Version
Customize Existing T24 Data Migration tool definitions

13. Reconciliation Engine
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
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
Provides a portfolio of pre-defined 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

14. Reconciliation Reports

15. View details for task Extract and Validate Customers

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

17. Process Control Engine
Control Mechanisms
End to end Process Sequence
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
Process
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
Customizable based on Implementation needs
Configurable for Big bang or Phased implementations

18. 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
Transaction Integrity Review
Interface Control Testing
Reporting Accuracy
Post Data Conversation Review
IT General Controls

19. V-Conn IT Audit Support
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

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

21. Automatic Vs Semi-Automatic Migration
0 % Reusability
67% Cut Down Cost due to Reusability
Roll Out
C O S T
$$$
Reconciliation
Test
Roll Out -50%
COS T $$
Reconciliation -60%
Development
Test -75%
Analysis
Development -70%
Analysis -65%
Engagement
Engagement -65%
Semi- Automatic Migration
Automatic Migration

22. Data source –Static data
Validata Staging Area
Extracted data
Transformed data
Load data
Reconcile data
Target System
Validata adapters
Validata adapters
Data source – Transaction data

23. Reconciliation Diagram
Reconciliation Framework
Data source –Static data
Reconciliation for this stage is populating report based on comparison between extracted Legacy data. Also all mismatches as per business validation rules.
Stage1 – Extraction Reconciliation
Stage2-Transformation Reconciliation
Reconciliation for this stage is populating report based on extracted transformed data. The process is using the defined business transformation rules.
Stage3 – Load Reconciliation
Reconciliation for this stage is populating report based on data that should be loaded against data actually loaded in T24.
Validata Staging Area
Extracted data
Transformed data
Load data
Reconcile data
Target System
Stage4 - Reconcile
Reconciliation for this stage is populating report based extracted data from T24 against data that should have been loaded.
Validata adapters
Validata adapters
Direct Migration
Extract
Transform
Load
Data source – Transaction data

24. Reconciliation Diagram
Reconciliation Framework static Data
Reconciliation for this stage will be based Data cleansing rules on Sector(Integer and in between specific range), Address( Specific Length).
Stage1 – Extraction Reconciliation Customers
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
Stage2-Transformation Reconciliation Customer
Reconciliation for this stage is populating report based on >100 business transformation rules .
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
Stage3 – Load Reconciliation Customer
Reconciliation for this stage is populating report based on Transformed data to be loaded in Target System against actual volume of data loaded.
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.
Stage4 - Reconcile Customer
Reconciliation for this stage is populating report based on Extraction of all Customer in T24 against the Customers that should have been loaded.

25. Reconciliation Diagram
Reconciliation Framework Dynamic Data
Reconciliation for this stage will be based Data cleansing rules on AMMOUNT( to be above 0),ACCOUNT ( belongs in the list of migrated acc)
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
Stage1 – Extraction Reconciliation FUNDS.TRANSFER
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
Stage2-Transformation Reconciliation
FUNDS TRANSFER
Reconciliation for this stage is populating report based on >30 business transformation rules .
Stage3 – Load Reconciliation FUNDS.TRANSFER
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
Reconciliation for this stage is populating report based on Transformed data to be loaded in Target System against actual volume of data loaded.
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.
Stage4 - Reconcile 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.

26. ROI based on Reusability for Migration Projects
78% Cut Down cost
Roll Out
Reconciliation
Test
Development
Roll Out -60%
Reconciliation -80%
Analysis
Test -85%
Development -75%
Engagement
Analysis -80%
Engagement -85%
Migration Phase 2
Migration Phase 1
*Scenario where the same legacy system across locations is used