Planning for MDM 5.5 Implementation

Amelia Lo, NetWeaver RIG USSAP Labs, LLC

Stanley Levin, MDM Development, SAP Labs, Israel

May 19th, 2005

Amelia Lo, NetWeaver RIG USSAP Labs, LLC

Stanley Levin, MDM Development, SAP Labs, Israel

May 19th, 2005

© SAP AG 2005

Purpose and Goal of this document

Purpose of this document:This document is to be used by MDM 5.5 implementation consultants, partners and customers as a straw-man document to facilitate the discussion of MDM 5.5 implementation planning It is essential to tailor your discussion based on your specificcustomer requirements

Goals of this Presentation:Describe a high-level RoadmapKey steps to preparing for implementation Review the Implementation processDiscuss best practices for successful Implementation

© SAP AG 2005

MDM 5.5 Product Overview and Roadmap

Platform and Landscape Considerations

Project Organization and Training

Implementation Methodology Review

Best Practices

Agenda

© SAP AG 2005

SAP MDM – A Key Capability of SAP NetWeaver™04

SAP MDMDelivers a single version of the truth for customer, supplier, products, employees and user designated objects

Provides capabilities to share this single version of the truth internally and externally with partners.

Leverages existing IT investments in business-critical data

Accelerates and improves the execution of business processes

SAP NETWEAVER™ONE PLATFORM – ONE PRODUCT

SAP NetWeaver™

Com

posi

te A

pplic

atio

n Fr

amew

ork

PEOPLE INTEGRATION

Multi channel access

Portal Collaboration

INFORMATION INTEGRATION

Bus. Intelligence

Master Data Mgmt/ MDM 5.5

Knowledge Mgmt

PROCESS INTEGRATION

Integration Broker

BusinessProcess Mgmt

APPLICATION PLATFORM

J2EE

DB and OS Abstraction

ABAPLife C

ycle Mgm

t

SAP MDM/MDM 5.5 Facilitates: “Data Unification”

© SAP AG 2005

Introduction to Rich Product Content Management

Targets the requirements of rich product content management and cross-media catalog publishing. It allows you to consolidate, centrally manage, and publish disparate product data across the enterprise and between trading partners.

Based on SAP Master Data Management Extension (MDM 5.5).

High-performing load, aggregation and search of product dataMultidimensional searchFlexible taxonomyIntelligent imaging and Web/print publishing APIs for seamless, multi-platform integrationScalability (up to millions of products)Publish to Web or Printed Catalog

Definition

Key capabilities/use case

© SAP AG 2005

SAP NetWeaver

Exchange Infrastructure

Application Platform

Master Data Management Extension

Rich Product Content Management

ERP 1 ERP 2 ERP 3 Excel/XML JDBC

File Adapter ~~~~~~~~XML

Catalog

Value Mapping

~~~~~~~~

Importing Product Data

Re-categorizationand enriching

~ ~ ~ 1. ~ ~ ~~ ~ ~ 2. ~ ~ ~~ ~ ~ 1. ~ ~ ~~ ~ ~ 2. ~ ~ ~~ ~ ~ 1. ~ ~ ~~ ~ ~ 2. ~ ~ ~

ProvidingCatalogContent

ComposingProductCatalog

EnablingWebCatalog

ProvidingPrintedCatalog

© SAP AG 2005

Providing Printed

Catalogs

Importing Product Data

Re-categorizing

and Enriching Product Data

Providing Catalog Content

Composing Product Catalog

Enabling Web Catalog

Rich Product Content Management

MDM 5.5Client

MDM 5.5ImportManager

(1) Map and consolidate fields

MDM 5.5Plug-into DTPApplication

(2) System updates and creates new objects

(3) Add images/PDF’s etc. to catalog

(4) Review taxonomy results

(5) Update and correct product data

MDM 5.5ImageManager

(6) System creates image variants

(7) Connect image variants to products

(8) Enter additional information to products

(9) System validates data and informs on errors

(10) Set catalog partition

(11) Assign catalog default values for publication

(12) Arrange product family layout

(13) Add products to mask (14) Publish to DTP

(17) Create Index

(15) Finalize layout

(16) Record finalized layout structure to MDM 5.5

© SAP AG 2005

Consolidation and Harmonization with SAP MDM 5.5

Alternate way of Master Data Harmonization:Based on Master Data Management Extension (SAP MDM 5.5)Particularly focusing on interactive cleansing and distribution of Material, Supplier, Customer, Employee* master data within (SAP R/3 based) ERP environment. Rather intended for periodical and interactive harmonization than for high frequent changes with automatic distribution and matching processes

Team of (central) specialists to consolidate and distribute Material, Supplier, Customer, Employee master data within R/3 / ERP environment interactively; match data of 3rd-party systems against R/3.Periodic consolidation of content and ad-hoc distribution into one or more ERP (SAP R/3) clients, e.g. monthly synchronization of customer data between different sales offices.

Attractive for easy start of a central team with small budget and pressure on time-to-benefitAttractive for a first phase to be enhanced through future MDM capabilitiesDue to easy deployment also suitable for mid-size companies

Definition

Key capabilities/use case

Target Customers/Segment

*available as of MDM 5.5 Feature Pack SP01

© SAP AG 2005

SAP NetWeaver

Exchange Infrastructure

Application Platform

Master Data Management Extension

Consolidation and Harmonization with SAP MDM 5.5

Description of a master data object:Globally relevant Data(Client) specific Data

ERP 1 ERP 2 ERP 3 Legacy 3rd Party Legacy

FTP Server ~~~~~~~~XML

~~~~~~~~XML

Extracting Master Data

ID Mapping

=

Consolidating Master Data

~~~~~~~~XML

Exporting Master Data

Enriching Master Data

Distributing Master Data

Repository

Importing Master Data

Value Mapping

© SAP AG 2005

Distributing Master Data

Extracting Master Data

Importing Master Data

Consolidating Master Data

Enriching Master Data

Exporting Master Data

Consolidation and Harmonization with SAP MDM 5.5

Source system (SAP R/3)

(1) Trigger extraction on R/3

(3) System transforms message into XML

(4) System routes and sends messages to file system

XI

(2) System sends extracted objects to XI

MDM 5.5Syndicator

MDM 5.5Client

MDM 5.5ImportManager

(5) Load objects from File Adapter

(6) Transform, map, and match objects

(7) Search and merge identical objects interactively

(8) Change or add object data

(9) Map, transform and save objects in the file system

(10) File adapter: System loads and sends objects to XI

(11) System routes messages to MDC

(12) Check IDOC inbound

(13) Change and add object data

(14) Send created objects back to MDM 5.5 to create key mappings (repeat steps 1 – 6)

© SAP AG 2005

Product Update: MDM 5.5 Feature Pack

SAP MDM 5.5 Feature PackIncludes former xCat 5.0 features (multilingual support, syndication, …)Lean, R/3-iDoc-based model for supplier, customer, material, and employeeAd-hoc consolidation and distribution into one or more R/3 clients(e.g. monthly sync of customer data between different sales offices) Interactive data quality analysis as well as matching and merging

Exchange Infrastructure

SAP MDM 5.5MDM 5.5 Import Manager

SAP R/3ApplicationBO Persistence

WAS

Partner SolutionApplicationBO Persistence

Legacy SystemApplicationBO Persistence

SAP R/3ApplicationBO Persistence

WAS

MDM 5.5 Client

MDM 5.5 Console

MDM 5.5 Syndicator

Available today

© SAP AG 2005

SAP NetWeaver MDMnext major releaseInroad into ESA

architecture

Key enhancement areas:Advanced Object

Modeling CapabilitiesExtensions for central

master data managementAdditional support for

Business Partner, Product models

Extended business scenarios

(GDS-Retail)

Product Update: SAP NetWeaver MDM Roadmap 2005

20062005

MDM 5.5 SP2 – July 05Extended user

productivity

Key enhancement areas:Enterprise Portal

Enablement(search/read access)Improved

Inbound/Outbound Communication with R/3

BI export of key-mappingExtended platform

supportGDS-CP Transora

MDM 5.5 SP3 –Mid Q4/05Integrated interactive and

automated processes

Key enhancement areas:Extended Enterprise Portal

ContentEnhanced de-duplication

Automated Load/Distribution via XI

BI integration for global reporting

Enterprise Services Retail Article enhancementsInfrastructure enhancements

MDM 5.5 FP- Available in RU

GA planned for end June

Key enhancement areas:Multilingual supportPre-defined R/3 objects

for Customer, Vendor, Material, lean Employee*

Interactive consolidation and distribution; syndication

Additional language support** (SP1 – e. March 05)

This document contains intended strategies, developments and/or functionality and is not intended to be binding upon SAP to any particular course of business, product strategy and/or development. Please note, that this document is subject to change and may be changed by SAP at any time without notice.

2006/2007July 05 Mid Q4/05June 05

© SAP AG 2005

MDM 5.5 Product Overview and Roadmap

Platform and Landscape Considerations

Project Organization and Training

Implementation Methodology Review

Best Practices

Agenda

© SAP AG 2005

SAP MDM 5.5 Cross – Platform Compatibility

MDM 5.5 supports the industry-standard platforms

Windows XP, 2000, 2003 - All versions

QuarkXPress (Windows and Macintosh)Adobe InDesign (Windows and Macintosh)

DBMS

COM Java

Microsoft Windows 2000/2003/XPLinux* - Kernel version 2.4 or higher with the following: -libstdc++.so.5 or higher -glibc 2.2 or higher (2.3.2 or higher recommended)

Sun Solaris** 8 - SunOS 5.8 rev. 02/02 or later

Desktop Publishing

MDM 5.5 Console/Clients

MDM 5.5 Server

* Available for MDM 4.0. Will be released for MDM 5.5 SP1 in mid May 2005

** Not available for MDM 4.0. Will be released for MDM 5.5 SP1 in mid May 2005

MDM 5.5 APIs

Microsoft SQL Server 2000 (Version 8.0 SP-3) Oracle 9.2IBM DB2* (Version 8.1)

© SAP AG 2005

MDM 5.5 Topology

All in One Scenario: all components can be installed on one machine for demo purposes or when the repository is very small.Distributed Scenario: MDM 5.5 Server and DBMS Server should be installed on different systems to improve overall performance. Suitable for most production scenarios.

MDM 5.5Clients

DBMSSever

MDM 5.5Server

MDM 5.5Console

© SAP AG 2005

Example of Hardware (support 30+ users)

Database ServerCPU * Quad XEON 2.8-3.0GHz with 400/533MHz FSBMemory * 4GB RAMStorage * Three 72GB disks in RAID 5 configurationNetwork Topology * 2nd network card for direct connection to SQL

Server

MDM 5.5 ServerCPU * Quad XEON 2.8-3.0GHz with 400/533MHz FSBMemory * 4GB RAMStorage * Two 18GB disks in RAID 1 configurationNetwork Topology * 2nd network card for direct connection to SQL

Server

Client WorkstationCPU * Single XEON 2.0GHz with 533MHz FSBMemory * 2GB RAMStorage * 20GBNetwork Topology * TCP/IP based network

© SAP AG 2005

MDM 5.5 Product Overview and Roadmap

Platform and Landscape Considerations

Project Organization and Training

Implementation Methodology Review

Best Practices

Agenda

© SAP AG 2005

Project Organization and Staffing – an informal draft

Project management office:Executive sponsor & steering committeeProject manager Cross organizational team: consists of Business owners from marketing, product management, production & manufacturing, customer Services, purchasing & vendor management.. plus IT

Project staffing:MDM 5.5 functional staff System and DBAProduct domain experts and taxonomy ownersAPI Developer (Java or COM)Web Designer & Portal SpecialistXI Specialist (for Master Data Consolidation/Harmonization Scenario)Print Publishing specialist (for Print Publishing)

© SAP AG 2005

Project Organization and Staffing – an informal draft

On going support:Product domain experts and taxonomy ownersProduct content update/data entry staffSystem administrationOperational support

© SAP AG 2005

Overview of MDM 5.5 Training

Project Preparation

MDM 5.5 Functional

MDM 5.5 TechnicalMDM 5.5 Technical

Other Optional

Workshops

MDM 5.5 Overview for Planning

What: Implementation methodology and key milestones

By: Typical workshop provided by onsite consultants

Who: Project management office

MDM 5.5 RKT Workshop RADME1

What: A 5-day hands-on workshop

By: Training offered via SAP RKT Office

Who: Project ManagerProject staffOperational support staff

XI Fundamental TBIT40

What: A 5-day hands-on workshop

By: SAP TrainingWho: XI Specialists who

will implement Master Data Consolidation scenario

MDM 5.5 Taxonomy Workshop

What: Taxonomy DesignBy: Specialty partnerWho: Product domain

experts and taxonomy owners

MDM 5.5 Print Publishing

What: In-depth training for print publishing implementation

By: SAP RIG/PM & Specialty partner

Who: Print publishing specialist

MDM 5.5 Data Modeling

What: MDM 5.5 Data Modeling consideration and design

By: TBDWho: Project Manager

Project staffSystem and DBA

MDM 5.5 API WorkshopWhat: A 2-day hands-on

workshop By: Training offered via SAP

RKT OfficeWho: API Developers

Web DesignersXI Technical

Implementation TBIT50 & 51

What: In-depth XI training for Implementation and Operation

By: SAP Training Who: XI Technical staff &

Consultants who will implement and do operational support

© SAP AG 2005

MDM 5.5 Product Overview and Roadmap

Platform and Landscape Considerations

Project Organization and Training

Implementation Methodology Review

Best Practices

Agenda

© SAP AG 2005

Project Phases

MDM 5.5 Implementation – ASAP MethodologyProject Preparation – Strategic PlanningBusiness Blueprint – Requirements GatheringRealization – Development and TestingFinal PreparationGo Live and Support

© SAP AG 2005

MDM 5.5 Implementation Overview – Project Phases

Project Preparation

Blue Print Phase

RealizationPhase

RealizationPhase

Final Preparation

Go-Live

• Define Project Team and Roles

• Objectives, Scope, KPIs

• Implementation Strategy

• Cost Estimate & Budget

• Identify Team Training

• Landscape & HW/SW

• Develop Project Plan

• Deliverables signoff

• Define Requirements based on Business, catalog and data analysis• Repository Schema/Data Model• Workflow Process• Web Deployment design• Security • System Management Strategy• Communication Strategy• BP Documents Signoff

• Hardware configuration• Configure Repository Schema per Blue Print• Data Mapping• Data Conversion

• Cleansing• Normalizing• Aggregation• Filtering etc.

• Data Import• Data loads• Detailing Attributes• Image Handling

• Web Solution Develop’nt• Syndication Solution• Enterprise App Integt‘n• Interface Develop‘t• Testing (unit, integ.)• Performance Testing• End User Training•

• Taxonomy Analysis

• Master Data Consolidation & Harmonization Analysis

Master Data C/H • SAP delivered• Customize to close Gaps

• Production system Management Process• Prepare Help desk support • Production Cutover

• Swat Team Baby sitting• Problem Resolution• Post implementation Review

Optional Activities based on project scope & requirements

• Print Publishing analysis

• Prepare Layout for print

Note: This is a general template to aid project start up. You may customize based on customer’s business requirements.

© SAP AG 2005

The HowTo Documents to Support Implementation

Where are these documents published :www.service.sap.com/NetWeaver> Media Library > How To Guide > MDM

Project Preparation

Blue Print Phase

RealizationPhase

RealizationPhase Final

PreparationGo-Live

1. Planning for MDM 5.5 Implementation (PPT)

2. MDM 5.5 Project Cost Estimation Template

3. Generic MDM 5.5 Implementation Project Plan

1. Step by Step Guide or How-To Guide for Modeling

2. From Business requirements to MDM 5.5 Design

3. HowToconnect MDM 5.5 to R/3 using the XI

4. HowTo define a good MDM 5.5 taxonomy -tips & tricks

1. Troubleshooting MDMe(traces, log files)

2. How to apply a enterprise level back-up strategy for MDM 5.5

Go-Live

1. TBD1. HowTo: Conversion of Attributes

2. HowTo: Splitting Fields into Lookup tables

3. HowTo: Load Qualified Tables

4. MDMeLandscape and System Management

© SAP AG 2005

MDM 5.5 Product Roadmap

Platform and Landscape Considerations

Project Organization and Training

Implementation Process Review

Best Practices

Agenda

© SAP AG 2005

Best Practices – Strategic Planning Team Selection

Corporate Product Classification and Taxonomy Design is a Business Owned Project

Cross Functional Team from all organizations have stakes in Corporate Product Taxonomy.

Example of Team composition:Product Engineering / Product DevelopmentPurchasingProduct ManagementMarketing / SalesCustomer Support

© SAP AG 2005

Best Practices – Strategic Planning Team Selection

Preferred team member profileLong-term knowledge of your product management process

Responsibility for organizing productsManage data flow in and out of his/her departmentKnow the bottlenecks

Experience in other departments/divisionsUnderstands enterprise-wide product workflow / product life cycle

Good rapport with other members in their departmentMust be able to influence culture change

Team members must be willing to explore every process and recognize opportunities for improvement

Should have a background in change management

Understand corporate vision and strategic initiatives

© SAP AG 2005

Best Practice – Strategic Planning

Product management involves many people and systems throughout the enterprise

MDM 5.5 Implementation will take all of these into account

Users and data sourcesProduct Engineering / Product Development

Specifications (in Excel), CAD drawings (on network drive)

PurchasingTransactional data (in ERP)

Product ManagementSpecifications (in Excel, in Word, on paper)

Marketing/SalesFeatures/Benefits copy, images (in Word, in PowerPoint, many graphics files stored on many computers, outside design firms)

Customer SupportUsage issues, quality (on paper, in “mind”, homegrown FAQ database)

Seize Opportunity to Reduce Complexity

© SAP AG 2005

Reduce Complexity

The sum of all interactions reveals extreme redundancyExpensive, time-consuming, and error-prone

CREATOR/OWNERUSER

CREATOR/OWNERUSER

CREATOR/OWNERUSER

CREATOR/OWNERUSER

© SAP AG 2005

MDM 5.5 will Reduce Complexity

MDM 5.5 removes redundant interactions, reduces errorCreators and owners: Store data in the same place, in the same wayUsers: Retrieve data from the same place, in the same way

CREATOR/OWNERUSER

MDM 5.5

CREATOR/OWNERUSER

CREATOR/OWNERUSER

CREATOR/OWNERUSER

retrieve data

store data

© SAP AG 2005

Best Practices – Strategic Planning

Plan QuicklyHave the team bring examples of data that is input into their systems (forms, spreadsheets), as well as examples of output (reports, file format instructions); less theory, more practicalityDiscuss what comes to mind quickly – a majority of major issues and needs can be identified in a few meetingsPrioritize issues – not all data problems need to be fixed initially, don’t overscope; find projects with measurable costsGain cross-departmental support for the implementation – find a high-profile issue that is collaborative and “win-win”, and has measurable success factors

Use Diagrams and Simple ExplanationsTo gain organizational buy-in and support, you will need to clearly communicate the project value

“Before and After” process flow diagrams will quickly illustrate this, and will be greatly expanded upon during Requirements Gathering

© SAP AG 2005

Best Practices – Requirements Gathering

User-centered focusPeople and processes are the focus, not technologyDo not add complexity, simplify and eliminate processes (duplicate forms, unnecessary reports)Consider existing processes that don’t “make sense”, use your team’s instinctsThe person who knows the most about a “field” may not be the person who manages it today, let the team decide what makes sense

Major risk factorsOverall data quality will greatly affect project time; spend time to know what you’re dealing with throughout the product life cycleInitial product categorization (taxonomy) needs to be designed properly; a large portion of the project will work on getting it right

Future sub projects will build on and augment the taxonomy, but should never cause a major overhaul

© SAP AG 2005

Best Practice – Realization & Final Preparation

Launch PlanningMarketing/Sales plans for announcing new product catalogCommunication plan for announcing availability/process changes to employees, customers and suppliers

Final Data LoadIncremental load vs. full reloadData verificationCoordinate archival of previous data sources no longer needed

Verify Operations SupportTest backup and restore for accuracy and completenessVerify batch processing is scheduled and running without errors

© SAP AG 2005

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, and Informix are trademarks or registered trademarks of IBM Corporation in the United States and/or other countries.Oracle is a registered trademark of Oracle Corporation.UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology. Java is a registered trademark of Sun Microsystems, Inc.JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. MaxDB is a trademark of MySQL AB, Sweden.SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

Copyright 2004 SAP AG. All Rights Reserved