Size and duration of a MDM Project

[Former Member]

Hello,

I have a difficult question (because I know that the answer depends on the situation), but I would appreciate to have some ideas based on real experience :

1) what is the man-month effort for a typical MDM project? Say to put in place a repository for products + customers, so that at the end, we are able :

- to maintain them centrally and distribute them to sevaral systems

- to use the unduplication fonctionality

The project should have the following steps : requirements gathering, specifications, customizing, tests, data migration and cutover.

2) What profiles do we need for such a project ?

3) Is it realistic to plan a MDM project in less than 6 months ?

Thank you in advance for your answers.

Best regards,

Christophe.

[Former Member · Accepted solution]

Hi,

Go to

https://websmp107.sap-ag.de/support

Search for

<b> MDM 5.5 Implementation Plan.mpp</b>

In the search results click the Documents tab.

This Project plan might give you a better idea.

Note: You need to have Service Market place id to access the above information.

Thanks and Regards

Subbu

[Former Member · Accepted solution]

Thank you Subbu.

The template planning gives me an good idea about the tasks required.

Best regards,

Christophe

[Former Member]

Hi Christoper,

My experience of MDM Project for Resource estimation is as below.

The most important thing to look at MDM project is to know what are the interfacing issues from source systems. What are the final Attributes that need to be mapped in MDM. what are the total no of mapping profiles that need to be build for Importing and Sysdicating. what are the taxonomy, lookup or hirearchy that are required to customer? Does RPCM is a required scenario? What are ports that need to be required? how many client systems are required for inbound/outbound and so on?

Note: MDM implementation is driven more by architecture and its integration to other systems. It is not a worry to know the no of records in MDM. MDM Attribute list is something that shows the impact on the load of the project.

Hope i gave you little insight.

If you any futher queries you can write back here or can talk to me.

Regards

Verea

[Former Member]

Thank you Verea.

Your recommandations help a lot.

Best regards,

Christophe.

[Former Member]

Certain points:

1. Duration of project is directly proportional to few of the elements like the number of Master data clients and the number (and type) of interfaces, Portal development, type of scenario (IT Vs Business) etc.

2. For the case you have mentioned, project duration will vary from 8 o 10 months.

3. You will need various profiles

a. MDM Solution Architect

a.1. About 3 or 4 MDM consultants

b. Technical Architect

b.1. XI - 2 or 3 resources

b.2 EP - 3 or 4 resources based on scope of development

b.3 Java / XML specialist.

c. Basis Administrator

Please note that in typical MDM project, increasing no. of consultants really does not help.

It will be a challenge to complete such a project in 6 months if number of MDCs are more than 2 or 3 and development complexity is medium or high.

Hope this helps.

[Former Member]

Thank you Rajesh.

This is very helpful.

Best regards,

Christophe.