Typical Implementation Timelines for EHSM Implementation

[former_member51634]

Dear Experts,

We are looking for implementing SAP EHSM module in our ECC 6.0 EHP7 SP12 (NW 7.4 SP15).

I wanted to understand what would be the typical implementation timelines we should be keeping in our mind assuming components to be implemented are Foundation, Incident Mgt, Risk Assessment, Env Mgt and Product Compliance. Integrating with HCM and/or SuccessFactors.

Looking for a typical implementation timeline as per your experience.

Best Regards,

Mandeepak

[Ralph_P]

Hello Mandeepak,

There is no such thing as a typical implementation. There are so many factors to be considered that will have impact on the implmentation time. So your question cannot be answered.

Best regards,

Ralph

[johnwmartin]

Hi mandeepak_grover

I want to clarify, as Chris mentioned earlier, I would caution all that a 'standard' implementation can be affected by many factors dictating the time and cost to implement, and therefore must be discussed specifically within the context of the customer's requirements, current-state factors, etc.

. Point of fact; there are many engineered solutions from both SAP Services as well as SAP EHS Partners alike which aim to control implementation costs/timelines by standardizing the scope and initial capabilities.

While these engineered solutions, accelerator packages, fixed-scope implementations go by many names, there are a number of options available for various EHS solutions, many of which specifically target rapid deployment, a specific scope, specific enhancements or functionality, etc. It is quite possible however to implement many of these in far less than the 4-5 months cited by others on this thread.

Again, there are a myriad of factors going into one's implementation of any solution but additional comment would be that, with the right resource model, multiple solutions could be implemented simultaneously with a few caveats. I strongly urge organizations considering new EHS/EMIS solutions to make sure you do your due diligence on the multitude of approaches (and opinions) out there to find the best fit of SAP EHS solutions for your organization.

[christoph_bergemann]

Dear John

I love your feedback... it lists (or try to list) the many factors to consider to handle/manage such a project.

I would like only to add some further hints to your story:

If the company acting has no experience in the implementation of EHSM then the next potential best step might be:

check the market to find a "solution provider" which lists success stories for "EHSM" implementation projects.

These success stories do not have (in most case) the "details" to be really useful without getting in touch with the solution provider and asking for the details.

Anyhow: It will be a time consuming challenge to check all the potential "solution providers" and to find then one "which really" fits (considering "costs", "Timelines", Experience of the provider (how many similar projects have been managed", Challenges in IT infrastructure etc.).

And there is always a story to consider like: "Access part" (access concept) and similar stuff which sometimes is not really on the radar if such projects are considered; same might be true for topics like. Is there the need to "migrate" data and if so: can this be managed?

Keep in mind: you just install some software: If nobody acts i the copany; then there is no "master data present" and the systen is "empty" and if you are an chemical company: this is in most cases not the real situation because of legislation part. So there is always some "similar" data existing

C.B.

[mzahid0071]

Hello,

If you are going with the standard solution , to implement Incident Management it will take 4-5 months for Risk management again 4-5 months and for Environment Management 3-4 months.

Once HCM is implemented ( or at least mini master data is present ) you can start your implementation /configuration the system.

You have to check - 1. Number of reports generating 2. number of workflows ( org. structure ) based on that +- the duration .

When we say 4-5 months it include ( 5-6 reports ( enhanc. and standard ) and standard workflows

Later you can start with role assginment etc.

[satya11719]

Hello Mandeepak Grover

It is completely depends upon your business like are you a global player are restricted to some regions and how many plants and locations are you going to implement.

What are the integrations you are going for ? Based on that we need to project planning we can't judge based the Module you choose.

The latest EHSM version i heard about is plug and play. SAP did all integrations include BI dash boards and all.

Thanks

Satya

[former_member51634]

Thanks much for your response Chris.

Yes, I need to come up with Project Life Time which will include Initiation, Planning, Implementation, Post Go-live.

In my query, I am looking for particularly 'Typical Implementation Period' in very typical scenario as mentioned in my post above.

Thanks again for your response and looking forward for your guidance.

Best Regards,

M.G

[christoph_bergemann]

Hello

first: we should differentiate between "project life" and "implementation" time. In your cases. You start from scratch. Here once again the "project content" is important and projects conten can change during project life time.

So please first specify. do you talk about "projekt life time" or "implementation period" only? (we assume: No extension need to be programmed etc.; so nothing special to look at?)

You topic of "project life time" and "time for implementation" was addressed often, but not in reference to EHSM.

C.B .

[former_member51634]

Thanks much for your response Chris.

Yes, I need to come up with Project Life Time which will include Initiation, Planning, Implementation, Post Go-live.

In my query, I am looking for particularly 'Typical Implementation Period' in very typical scenario as mentioned in my post above.

Thanks again for your response and looking forward for your guidance.

Best Regards,

M.G.