SAP S/4HANA – consulting and implementation

From the roadmap through the business blueprint to stable operation. We guide companies through the move to SAP S/4HANA without bringing daily business to a halt.

Maintenance for SAP ECC is running out, which puts the question of when and how to move to SAP S/4HANA on the table. The technical conversion is rarely the hard part. It gets demanding when processes that have grown over the years, hundreds of custom developments and a daily business that cannot stand still all have to be handled at once.

We start by looking at where you are. Which processes run on the standard, which custom developments are still in use at all, which data has to come along? Out of that comes a roadmap you can put in front of your management, with effort, sequence and risks.

Why clients get in touch

  • End of maintenance is approachingYou need a defensible date and a budget figure before the discussion reaches the management board.
  • The last estimate is a guessA system house named a number nobody can reconstruct. You want an independent second view.
  • The project is already runningThe blueprint is done, the dates are slipping, and the team is missing someone who has done a conversion before.
  • Several plants, one templateYou do not want to start from scratch at every site and need a rollout logic that still holds at the fourth plant.
Scope

What we take on

Individual building blocks or continuous support, depending on the project phase.

Current state and readiness

We review the system, the custom code and the data quality, and show what should be cleaned up before the conversion.

Roadmap and business case

Sequence, effort and benefit in a form that is also understood outside the IT department.

Greenfield or brownfield

We assess both routes against your processes rather than a rule of thumb, and explain the recommendation.

Business blueprint

Target processes in logistics, production and procurement, agreed with the departments and documented for implementation.

Data migration

Migration concept, mapping rules and test migrations, so that no surprises turn up on the go-live weekend.

Go-live and hypercare

Cut-over planning, test coordination, key user training and support during the critical first weeks.

How we work

How an SAP S/4HANA implementation runs with us

  • Step 1
    Assessment
    System analysis, interviews with the departments and an evaluation of the custom developments. Two to four weeks, depending on size.
  • Step 2
    Roadmap and decision
    Scenarios with effort and risk, a reasoned recommendation and a decision paper that can go to management.
  • Step 3
    Blueprint and build
    Target processes, customising, development of the remaining gaps, migration concept and integration tests.
  • Step 4
    Cut-over and operation
    Dress rehearsal, go-live weekend, hypercare and an orderly handover to your support organisation.
What you get

How you can tell it is working

Decisions backed by numbers

You get effort estimates based on objects counted in your system, not on experience from someone else's project.

Departments on board

We bring production, purchasing and logistics in early. People who helped shape a process will also carry it later.

One point of contact

You talk to the person who is also in the project, not to an account manager.

Questions

Frequently asked

Greenfield or brownfield, which is better?

It depends on how well your current processes fit the standard and how much legacy sits in the system. For heavily customised systems with a lot of unused custom code, a rebuild often pays off. Where processes are clean, conversion is faster and cheaper. We assess both against your system before making a recommendation.

How long does an SAP S/4HANA implementation take?

For a mid-sized company, typical projects run between nine and eighteen months. The decisive factors are the number of sites, the state of the master data and how many custom developments have to come along.

Can we do this with our own team?

Often yes, if someone with project experience takes the lead and the departments really get the time. In that case we take on project management or architecture, and the knowledge stays in the house.