Metalogic Data Migration Practice

(1)

www.metalogicsystems.com

Metalogic Data Migration Practice

Metalogic Systems

(2)

Automation of various phases and processes of software project lifecycle

Dedicated R&D team constantly improving upon Automation Techniques, Tools

and Products

Experience in implementing projects across the globe

ISO 9001:2000 Quality Certification

ISO 27001:2005 certification (BS 7799 ) for Information Security Management

Systems

TiE Best Entrepreneur award in 2006

Incorporated in July 1997

Head Office & Software

Factory at The Software

Technology Park, Salt Lake,

Calcutta, India

Metalogic Systems

(3)

Data Migration Market

(4)

Global DM budget forecast—leading 3 industry sectors in $m: 2007–2012

0 500 1000 1500 2007 2008 2009 2010 2011 2012 $ m

Banking Diversified Financials Utilities

Data Migration (DM) Market

†

The world wide Data Migration (DM) market is estimated as

†

$ 5 bn in 2007

†

$ 8 bn in 2012

†

The leading industry sectors where Data Migration(DM) budgets are maximum – Banking, Diversified Financial Services and Utility sectors

(5)

DM Market continued…

Estimated DM Budget in India: 2007-2012

134 122 111 101 92 83 0 20 40 60 80 100 120 140 160 2007 2008 2009 2010 2011 2012 $ m

†

India’s domestic IT/ITES market size is estimated to be INR 87020 Crores in 2007 (IDC India)

†

The DM budget in India is estimated by Bloor Research as

-

$ 83m in 2007

-

$ 134m in 2012

Source: Bloor Research, 2007

†

Regionally, most investment in DM projects is expected to take place in North America ahead of APAC and Western Europe

†

The leading spender countries are USA, Japan and UK

(6)

†

In 2007 alone 300,000 TB of

storage, whose lease will expire, will most likely be replaced with new storage by organizations across the world (IDC report)

†

38% of Salesforce users are planning to shift to other CRM packages (CRM Blog)

†

IDC estimates 115,000 oracle

databases ($1.1bn) will migrate over the period from 2006 – 2009.

†

A survey by the Yankee Group found that 17% of users are very likely and 30% are somewhat likely to replace PeopleSoft CRM

†

54% UNIX users reported platform migration activities in 2004 in a survey on server migration done by IDC

†

There are 40,000 application (ERP) migrations going on all the time (Bloor Research, 2006)

DM Market continued…

In most cases DM is taken up as part of a wider enterprise application project. The major types of enterprise applications which involve data migration are shown in the diagram below –

Average portion of applications budget spent on data migration is 8-12.5%

(7)

DM Market Drivers and Challenges

†

Overall, 47% of the migrations resulted from storage/server replacement or the ending of leases, while 26% were due to consolidation and migration. (Softek

survey, 2005)

Source: Softek’s 2005 Worldwide Data Migration Survey

DM Project Statistics:

83% exceed originally planned staff time 54% exceed originally planned budget

39% of IT managers have avoided taking on a data migration project specifically because of the perceived risks involved(Tech world , 2006 ).

User Perception: Data Migration Is problematic

Source: Softek’s 2005 Worldwide Data Migration Survey

†

The majority of users (75%) have experienced problems with data migrations

†

58% reporting extended or unexpected downtime

(8)

Metalogic Solution

(9)

Metalogic Value Proposition

• Solution for diverse

platforms

– Legacy data stores like Flat Files, IDS-II, IMS, ADABAS to any RDBMS (DB2, Oracle…)

– Any existing RDBMS to another (DB2 to Oracle, Oracle to MS SQL Server…

– DM due to applications

implementation or replacement (like ERP, Banking etc.)

• Lower project risk

–

High automation - minimal manual intervention

–

Consistent quality - high accuracy

• Faster delivery, Lower cost

–

30 – 40% reduction in time and effort

†

Tool based data

analysis, mapping and

transformation

†

Automated data

validation

†

Incremental

implementation in the

target environment

†

Seamless process to

support the tool based

migration

(10)

www.metalogicsystems.com Source Data Analysis Target Data Analysis Attribute Mapping Mapper Creation Repository Population

Data Download and Upload Generation Data Download and

Upload Testing Live Data Migration Source Data Target Database Tested Data Download and Upload Utilities Data Validation Routine Generation Error Reports Cataloging Transformation/ Validation Data Analysis Attribute mapping

Metalogic Tool set

Tool based process

†

Tool based data analysis, mapping and transformation

†

Automated data validation in target environment

†

Incremental implementation in the target environment

†

Seamless process to

support the tool based migration

(11)

Data Validation

Source Data Layouts Transformation Tool Data Validation Programs Target Data Table/ File Validation Reports Metadata Repository Mapper Files Customer Check Validated Table/File OK Not OK

†

Seamless process to

(12)

Incremental Implementation

†

Small chunks of datasets are introduced in the production environment at a time

†

A DB State Model directs the application to access data sets from the live data source.

Old data store New data store Application DB State Model Advantages: Advantages:

†

Non-disruptive

†

Minimum down time

†

Easy Rollback

†

Seamless process to

(13)

Metalogic process

†

Seamless process to

support the tool based migration Data Data Analysis Analysis Data Data Mapping Mapping Cataloging Cataloging Transformation Transformation Data Data Validation Validation Live Data Live Data Migration Migration • Data Layouts • Validation Rules • Mapping Document • Mapper Files • Populated Metadata Repository with Mapping Rules • Validation Reports • Data Migration Programs • Data Validation Programs

Usually this activity is done by the partner/ Metalogic onsite team

(14)

Customer Interaction Points

Data Data Analysis Analysis Data Data Mapping Mapping Cataloging Cataloging Transformation Transformation Data Data Validation Validation Live Data Live Data Migration Migration

•

Data source identification

•

Review and feedback on mapping document

•

Checking of validation report

•

Issue resolution support

•

Review of migration plan

•

Parallel run

•

Support in incremental implementation

•

Problem reporting

(15)

Project Management

Tools

-•

Monitoring and tracking – MS Project

•

Configuration management – CVS/SCCS/VSS

•

Issue tracking – Mantis/Jtrac

Methodologies –

•

Risk mitigation

•

Change management

Documentation –

•

Project Management Plan

•

Data Migration Plan

Communication –

•

Status reports

•

Joint Review MOM

•

Configuration management

•

Internal reviews and audits

•

Test/Validation plan and reports

•

Project metrics (defect, schedule)

(16)

Infrastructure and Security

†

Separate Data Migration Center (200 seat capacity)

†

Combination of Dial-up/Dedicated Leased lines/T1

links & Satellite Links for 100 % Connectivity

†

100% power back up

†

Physical access controls in DMC

†

Additional access control for location housing data

servers

†

Network access control mechanism

†

Business continuity plan for disaster management

and recovery

(17)

Case Studies and Customers

(18)

Case Study – Migration from IBM / MVS

mainframe to SUN/SOLARIS

Customer Profile

Leading Insurance Co. U.K The customer is a leading

insurance company in UK. The data migration project was

executed for one of its offices in Australia.

Source and Target Platforms

Source IBM / MVS mainframe with applications using IMS / VSAM Target SUN/SOLARIS / ORACLE 9i /

Challenges

Transformation of the complex hierarchical IMS database to Oracle

.

Achieving database performance levels and accuracy of the migrated data for the existing mission-critical application.

Solution Approach

Automated tool assisted migration of:

Recovering the legacy data model in IMS

and VSAM.

Finalize and generate the Oracle data

model.

Generate the data migration utilities

Utility program generation for data

consistency validation in the migrated environment

(19)

Case Study – Migration from ICL Trimetra LY

mainframe to SUN / Solaris

Customer Profile

Department in the Government of South Africa

Client had an ICL Trimetra LY mainframe for running their mission critical Claims & Benefits applications at Compensation Commission (CC) based on COBOL using Flat files .

Source and Target Platforms

Source

ICL Trimetra / VME / Flat Files Target SUN / Solaris ORACLE 9i / Oracle Pro*COBOL

Challenges

The application had very little

documentation and low technical inputs from the end users.

The deployment platform of the migrated application.

Solution Approach

A very high degree of automation was adopted to :

The COBOL based flat file data model was transformed to Oracle 9i.

Oracle table wise automated Oracle database access utilities in Pro* COBOL were generated

The data got transformed from flat files to Oracle 9i.

A major portion of the work was executed offshore at Kolkata resulting in further

(20)

Case Study – Data Migration from Dbase and

Flat Files (COBOL) to Oracle E-Business Suite

Customer Profile

A medium sized engineering company in India

Data migration due to ERP

implementation. The customer had a fair volume of existing data in Dbase and files which had to be migrated to the Oracle E-Business Suite database.

Source and Target Platforms

Source

Dbase/ COBOL Flat Files

Target

Oracle E-Business Suite data model

Challenges

the major challenges were in re-modeling the file layout to fit Oracle E-Business suite input requirement

This required to be completed in a tight time frame, as the new system Go Live date was fixed.

Solution Approach

Common input format as ASCII files were created from Dbase

Data mapping as per Oracle E-Business Suite requirement

Uploaded into temporary tables and validated

Data uploaded to base tables by using applications Interface or developed PL/SQL programs