Extending ETL Tools

Overview
Key Features
Why MDX?

ETL tools are not well-suited to the iterative nature of ERP data migration projects.

Developing ETL code is more suited to traditional systems development lifecycle and a “waterfall” approach to design, build, test and deploy.

In an ERP project, gaps in master data specifications and inaccurate assumptions of data quality/availability, combine with other changes to business requirements to create a “moving target” and a constant stream of specification changes.

ETL code does not provide the flexibility to react quickly enough to the changes and the project becomes at risk.

MDX provides a collaborative environment, process management, integrated specifications repository and a staging database to compliment leading ETL platforms from SAP BusinessObjects, Informatica and IBM

The use of MDX saves significant time and cost that would otherwise be required to develop capabilities to reduce project risk, deliver additional flexibility and improve quality.

Configuring ETL tools for ERP data migration is often under-estimated for a number of reasons:

Gap between Functional Requirements and Master Data Specifications – Prior to implementing ERP, much of the logic that define business processes is found in documentation, embedded in program code or only exists in people’s heads. In ERP, these processing rules are held as Master Data. ERP has enormous flexibility to change this Master Data to meet evolving business requirements. However, initially translating business process requirements into Master Data specifications is extremely challenging and typically results in incomplete and/or inaccurate specifications.

Lack of Data Knowledge – Documentation of existing systems is typically inaccurate, incomplete or missing entirely. An organization rarely has the people with the time and knowledge of existing data to fill these knowledge gaps at the design stage of the project, so the specification “evolves” as decisions are made throughout the project.

Data Quality Problems – Even organizations that are aware that they have data quality challenges fail to understand the effort required to fix all that is incomplete, inaccurate or inconsistent in their information.

Transformation Complexity - The master data required by the ERP may not exist in current systems in a form that is easily transformed. Much of the ERP data will require extensive transformation logic that is far beyond the “drag and drop” mapping typically associated with ETL tools.

MDX enhances flexibility, minimizes risk and preserves integrity through a portfolio of capabilities that would otherwise need to be designed and developed as part of the ERP data migration project.

A few of the key features that extend ETL products for data migration projects are:

SharePoint Portal

Preparing Master Data requires the coordinated efforts of multiple stakeholders. MDX provides an integrated collaboration portal based on Microsoft SharePoint to manage the exchange of information across the project team.

Indirect costs attributed to the allocation of internal time is reduced through the use of a familiar platform and close integration with Microsoft productivity tools and network security.

Minimal Shut Down at Go-Live

Minimizing the period that the business is “frozen” before go-live is critical to many businesses. MDX provides delta-detection and impact analysis capabilities so that, during the period required to initially load and validate ERP, the enterprise can continued to operate it’s existing systems without any restrictions on new data entry. Once the data is validated in the new ERP system, the Master Data from legacy systems can be refreshed and only the records that result in ERP updates are passed on to ERP by MDX. This limited update to ERP can be completed in a fraction of the time required for a full load and business down-time is minimized.

Single Point of Audit

Master Data is typically drawn from multiple systems that span organizational and geographic boundaries. Data is touched many times by many people over the course of a project. MDX provides a single repository that tracks “Who”, “When” and “Why” changes are made to Master Data. This audit trail is critical during testing and validation to maintain user confidence and understanding of the resulting business data.

Integrated Repository

As a result of changes to the ongoing legacy process, refinements to the ERP design and newly discovered exceptions in the data, an ERP specification continues to evolve throughout a project. Indeed, it is not unusual for an ERP specification to undergo hundreds of changes over the course of an implementation. The MDX platform manages all changes to specifications, meta-data and business data within a single repository. The MDX repository is version controlled so that the customer can understand the impact of any change.

Event Manager

MDX includes an event tracking system for managing all queries and user inputs raised during the migration project. IFA events are linked to the specification and audit trail of the business data and become a key part of the migration process.

IFA’s are tracked in a variety of ways including, the person it is assigned to, the due date, the data element involved and the processing step. SharePoint workflows may be attached to the IFA’s to generate email or task notifications, escalate outstanding IFA’s or alert stakeholders on progress.

Intelligent Back Out

MDX provides the ability to isolate unwanted updates and to remove the impact of bad data from the master data staging area without the need to rebuild the entire staging database. This backout facility minimizes the disruption to the business data while keeping the integrity of the audit trail intact.

MDX provides best-in-class data migration support when you need it, for as long as you need it.

	Reduce Cost – MDX enhances flexibility, minimizes risk and preserves integrity through a portfolio of capabilities that would otherwise need to be designed and developed as part of the ERP data migration project.
	Reduce Time – All of the risk management, process management and automation capabilities to extend ETL tools are available on the first day of the project without any need for additional development time.
	Increase Quality – Data quality is a factor of time. MDX capabilities reduce the time required from business users to validate data, provide input and request specification changes.
	Increase Trust - Trust comes from visibility; MDX ensures that every change to business data or specification is tracked and completely auditable. The same level of auditability would consume hundreds of hours of additional ETL development time.
	Increase Control – Control of specifications, meta-data and business data is managed by MDX in a version controlled repository. Impact analysis is automated and integrated with an Issue Management system. These features are absent in most popular ETL tools.