cancel
Showing results for 
Search instead for 
Did you mean: 

MDM Post-Implementation Support Model

Former Member
0 Kudos

Can any of you who have implemented MDM give a brief outline of how a typical MDM implementation is supported after go-live? Example: What organization(s) support daily monitoring of Imports and Syndications and how?

WHo/How supports the Console functions?

How are additional enhancements (in-house changes)to iViews, Import Maps and Syndications handled (by what in-house organization(s))?

Is any organization actually using the Data Manager for Harmonization/CMDM or iViews and the Portal.. how is this controlled?

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi Tom,

Here are the answers to your questions..

What organization(s) support daily monitoring of Imports and Syndications and how?

The import and the syndication process is automated in real scenario and also a workflow is established to notify the content manager to check n validate and confirm the change.

WHo/How supports the Console functions?

All u need is an administrator to take care of your console.

His job is includes creating new users, assigning roles etc.

Is any organization actually using the Data Manager for Harmonization/CMDM or iViews and the Portal.. how is this controlled?

There are many big organisations using the MDM namely:

General Electric

Rubbermaid

Whirpool

Kingfisher

Airgas

Hope that helps.

Regards,

Tanveer.

<b>Please mark helpful answers</b>

<b></b>

Answers (2)

Answers (2)

Former Member
0 Kudos

Well, I'm not sure what a typical MDM implementation is however I can tell you a little bit about how we've done things for the past 4 years.

MDM is the only SAP product we're using. We use it for rich product data management and harmonization across for 300,000 products from 300+ manufacturers. We have the DBA on our technical ops team maintain console functions such as adding fields, managing users, creating and managing slave catalogs. This has worked very well given the close ties between MDM and our other IT systems and the fact that the tech ops team handles all code deployments for us.

There are significant differences between various types of building products so we've divided our data factory staff into three groups, each one of which has responsibility for specific sections of the category hierarchy. Taxonomists and product data editors in the data factory are responsable for creation and management of Import Maps for the product categories assigned to their team.

We have found it useful to have at least one person with a high degree of technical apptitude in a Sr. role on the data factory staff (i.e. a power user.) This person can act as the goto person in the factory when there are questions about creating import maps or using the data management tools. Amongst other benefits, this will reduce need for your help desk staff to support these products.

We're not using iViews or Syndications.

-glenn

Former Member
0 Kudos

Hi,

Basic support after MDM implementation in a project is provided by iviews portals.But problem with portals are a few restrictions in gaining the complete control on data creation and modification as per SP03.So as of now (till SP04 is not released )we need Portals as well as Data Manager for the complete control and management of master data .Console is generally governed by administration side of the company defining roles and user rights.Master data maintenance after implementation is most likely to be done by company itself.

Regards

Vinay

Please mark helpful answers