Skip to Content
avatar image
Former Member

SAP MDG Enterprise Asset Management - Implementation plan/strategy doubt

Hi Experts,

My team is starting a project in which we will implement SAP MDG EAM and MDG Customer master.

In MDG EAM we will do Equipment master, Functional location, Work Center and Linear Asset management. I was trying to chalk out the implementation strategy and timeline for build/development but there are a few dependencies on each sub-module( of EAM) for which I am a bit doubtful.

Now, my question is ,as EAM has only 1 data model, so will simultaneous build work for EAM? Shared data model, same feeder classes( for FPM UI ) etc. may cause a problem. Lets say someone working on Equipment master doing a data model enhancement will effect the guy working on Work center etc.

I would like your suggestion about what would be the best way to go about. Build one module and then move on to another would be the safest and ideal plan it seems, but the client wants to finish the project earlier. So we will have to merge the developments and somehow save some time.

Does going like - finalizing the data model first, then moving onto UI and workflows help?

Please share any suggestion whihc might help.

Many thanks in advance for your suggestions.


Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

0 Answers