Guidelines for Information MigrationInformation Migration

Basavaraj Hooli

September 2010

Mobile Data & Enterprise Applications

While the Communications Industry in India is bracing itself for a major investment cycle for 3G and Broadband Wireless Access (BWA) services

over the coming years, the operators will need to develop new capabilities and take on new non-traditional competitors including IT

service providers and players like Google and Skype who are threatening to make inroads into revenue pools hitherto the exclusive domain of

Telecom operators

Metadata Management Maturity Curve

Business View

ProcessMigration

Systems View

Converging IT and Business

Applications Migration

Requirements for Information Migration

New Best Practices for Data Migration ?

Gartner, Standish Group and Bloor Research all say that 67% of all data migration projects cause

implementation delays, large overruns or fail outright

The reality is very different

67% of all data migration projects cause implementation delays, large overruns, or fail outright.

Gartner, Standish Group and Bloor Research

The reality is very different

Why do so many data migration projects fail?

All legacy data Legacy data Transformations Migration is an easysources are quality is will be simple project with limited scopeidentified acceptable

Legacy data All required data Data integration ETL and/or SQL areformats are exists in the skills can easily effective tools forunderstood legacy system handle data data migration

migration needs

Many new legacy Legacy data Transformations Problems are founddata sources are quality is much are extremely piecemeal, so migrationdiscovered worse than complex becomes a moving targetthroughout the expected with huge, increasing scopeproject

Legacy system Legacy data is documentation is not adequate to out-of-date & operate the new assumptions are system incorrect

Migration is an ETL and/or SQL are order of magnitude too sluggish to more difficult than handle the huge integration volume of changes

Simply put, data migration is the largest area of risk

in most software implementations

MNP Impact on the OSS/BSS

ESBESB

CRMCRM MDMMDMMSCMSC

MSCMSC

WGWWGW

AAAAAA--LDAPLDAP

Postpaid CRM

Mobile quota check

OSS/BSSGateway

HLRHLR

HLRHLR

BillingBillingSystemSystem

NMSNMS EPOSEPOS ERPERPProvisioningProvisioning

ETLETL

MMSC MMSC

WINWIN

Product & Enabling

CRMCRM

PaymentCredit Note

Postpaid BillingPrepaid CRMNumbering Mgmt

MediationMediation

RARABOBO

ReportReport

EPACTL

• Extract: legacy data from disparate source systems

• Profile: legacy data (produce statistics on data content)

• Analyze: legacy data to identify data quality issuesdata quality issues

• Cleanse: legacy data to eliminate data quality problems

• Transform: data content and data structure as needed

• Load: transformed data into target system

Strategy, Infrastructure &Product

Operations

Market/Sales, Product and Customer

Service

Resource(Application, Computing and Network)

SID Domain

SID Domain

SID Domain

SID Domain

SID Domains

TM Forum Information Model

Domains are the aggregations of Aggregated Business Entities (ABE) and ABEs are aggregation of Individual Entities. ABEs are nothing but Logical Business Components.

DOMAIN

ABE(Logical Business Components)

Individual ENTITIES

Enterprise

Supplier/Partner

SID level 0 is divided into eight domains: Market andSales, Product, Customer, Service, Resources,Suppliers and Partners, Enterprise, and CommonTasks. Each domain is a hierarchy of levels of detail inthe form of business entities.

Business Components.

Action plan for next steps

• A study group to work on data models and migration strategies

• Bring it to TM Forum?

© 2009 MphasiSThe information contained herein is subject to change without notice.