data migration workshop findings document sample
DESCRIPTION
Data Migration Workshop Findings Document SampleTRANSCRIPT
DATA MIGRATION WORKSHOPFINDINGS DOCUMENT
ContentsStrategy and Vision........................................................................................................................................ 3Business Needs................................................................................................................................................ 4High Level Processes....................................................................................................................................... 4Go-Live Strategy............................................................................................................................................... 4Organization..................................................................................................................................................... 5Information Needs............................................................................................................................................ 5Enterprise Information Management Needs.....................................................................................................5Legacy System Mapping.................................................................................................................................. 5Data Governance............................................................................................................................................. 6Integration and Syncronization......................................................................................................................... 7Data Quality...................................................................................................................................................... 7Data Standards................................................................................................................................................. 9Demographics................................................................................................................................................ 10Information Strategy....................................................................................................................................... 11Current IM Plans............................................................................................................................................. 11Scope............................................................................................................................................................. 11Legacy Environment.................................................................................................................................... 13Legacy Systems............................................................................................................................................. 13Infrastructure................................................................................................................................................ 14Project Management..................................................................................................................................... 16Project Initiation.............................................................................................................................................. 16PM Processes................................................................................................................................................ 16Initial Project Plan........................................................................................................................................... 17Risk and Issues.............................................................................................................................................. 17Next Steps..................................................................................................................................................... 17According to our SAP Data Migration Solution Methodology there are 2 next steps in the path to AIM Company’s Data Migration project:.................................................................................................................17Data Migration Audit....................................................................................................................................... 19Data Migration Readiness Assessment..........................................................................................................20
Copyright/Trademark
STRATEGY AND VISION
The AIM Company Data Migration Project it’s intended for the EMEA region with more than 60 countries to
be migrated into one instance of SAP, the findings document contains the details from the APJ Data
Migration Project already concluded but it will the base to build the new one to maximize the use of the
current infrastructure and resources involved in it.
Copyright/Trademark
Business Needs
High Level Processes
AIM Company defined the high level business process which the new ERP implementation will support and
we explored how this will differ from the current business processes and practices.
Background:
AIM Company bought the ACME PC division in 2005, and the data of AIM Company’s international
business is in the ACME IBM legacy system. According to the contract, AIM Company will migrate the data
from ACME IBM legacy system to the SAP platform.
There are many systems in AIM Company to consolidate into ERP, such as ECC, CRM, SRM, ProM,
Vendavo, I2-planning, I2-Ecommerce and Windchill.
Go-Live Strategy
AIM Company’s overall preference for degree of risk may temper the overall strategy. If risk adverse, the
DM team can plan for a period of parallel running. Some risks identified:
1 Business Requirements/Function Spec Lock down yet
2 Some data sources like Japan are not clear, which may result in FS change
3 Too much time needed for correct data transformations during last release
4 About 10 times data Volume higher than Canada Release
5 Tight schedule: Only 18 days for Production Load
6 Data Harmonization & Validation: No time allocated for User Data Validation
Copyright/Trademark
7 MDR configuration not ready for dry run
Organization
AIM Company’s current and planned organizational structure may significantly affect many aspects of the
data migration including the overall strategy and the specific business rules for transformation. Example from
APJ:
Information Needs
Enterprise Information Management Needs.
A lot of the information discovered and defined on AIM Company’s Data Migration project can and should be
integrated into the current and future Information Management needs and requirements. This need covers
all aspects of business rules, organizational procedures and technology. The EIM domain will ensure that
the design of the Data Migration solution will support any broader initiatives.
The standard infrastructure for EIM in AIM Company is based an IBM Data Stage, which is used for their
integration and analytical applications.
Legacy System Mapping
The answers in the strategy and vision section will be used to identify the planned/required SAP modules
and the associated SAP Business Objects. This step is vital to set the scope for the migration project, will
lead to easier and more accurate planning in later phases and reduce the overall risks through a better and
wider understanding. In addition, these high level entities can be mapped to high level entities in the legacy
systems.
Copyright/Trademark
Data Governance.
Data Governance is the process of actively managing the quality of the data in the systems and covers all
aspects of people, processes and systems. It also covers areas such as Master Data Management,
commonality of terms and data quality at point of entry.
Below is a current definition of the Data Governance team and roles needed:
Copyright/Trademark
Integration and Syncronization.
AIM Company's expectations for ongoing integration and synch to systems outside of the newly implemented
SAP applications, now there are many systems in AIM Company consolidate into ERP, as ECC, CRM,
SRM, ProM, Vendavo, I2-planning, I2-Ecommerce, Windchill and so on.
For our team, we support ECC and CRM daily.
Data Quality
Data Quality refers to the quality of the data in the legacy source system. We explored the current
perception of data quality in the source systems so that future phases can be planned effectively.
For the data quality, we defined the integrated data validation process and method.
Copyright/Trademark
Data Standards
The Data Migration project must meet any and all existing standards within AIM Company and this is
especially true of the master data and metadata.
As in the previous Everest DM effort, the data consistency is maintained in the MDR landscape:
Copyright/Trademark
Demographics
As the new Data Migration effort is targeted for EMEA there are many demographics issues to be addressed,
similar to the ones encountered in APJ:
Copyright/Trademark
Information Strategy
Current IM Plans.
AIM Company’s Data Migration project has multiple touch points with on-going business and IT operations,
one key area is the AIM Company's existing and planned Information Management (IM) strategies.
Mostly are based on its current Information Management technology based on IBM Data Stage.
Scope
As in the previous Data Migration project the Scope could be the same as follows:
• Migrate AP business and processes to the new MySAP architecture.
• AP business processes to be modified to reflect the China business or appropriate WW model.
• Include consumer and SMB in deployment.
• Includes both Customer Relationship Management and Transactional Relationship Management.
• Migrate from legacy applications to MySAP or strategic 3rd party applications.
• Deploy e2e ERP applications.
• The new IT platform to be deployed will cover all AP sources.
• Onshore and offshore models including offshore no presence.
• Existing products will be migrated to new architecture under a fixed structure solution
• New product releases will support the current product types ; PCD Desktop , Thinkpad Products,
Monitors, Options, Software, Accessories & Supplies, Services, AIM Company 3000 Products,
Workstations and Servers. Standard and Custom Fixed solutions. Also CTO capability based on
new strategic BOM structure.
• Language requirements as per previous detail chart.
• Currency requirements as per previous detail chart.
Copyright/Trademark
LEGACY ENVIRONMENT
Legacy Systems
There are several Legacy Systems to be migrated but this effort is more focused on SAP ERP and CRM:
Copyright/Trademark
INFRASTRUCTURE
In different releases, AIM Company used different methods to implement data migration.
There are two approaches:
1 IBM transfers TXT flat files to IDoc via datastage
2 Our team uses IDoc, BDC, and BAPI to do data migration. IDoc and BDC are implemented by LSMW, we developed the program to call BAPI for fulfill user requirements.
Generally, these existing plans are successful. In most cases, these partners are able to fulfill their assigned
objects, but sometimes, they can’t anticipate the problem from the AIM Company business perspective, for
example, the program lacks the extensibility, we can’t use it in next release; the problems like that should be
improved in the future.
Copyright/Trademark
PROJECT MANAGEMENT
Project Initiation
PM Processes
Copyright/Trademark
Initial Project Plan
Risk and Issues
NEXT STEPS.
According to our SAP Data Migration Solution Methodology there are 2 next steps in the path to AIM Company’s Data Migration project:
Copyright/Trademark
Data Migration Readiness Assessment
Copyright/Trademark