By Samantha Sithalpersad, Mampai Sekhoane, Solange Mela and Maurice Nkabini
It is common knowledge that organisations that choose to “save” on their project budget by significantly reducing or even excluding the go-live support phase because they are certain their implementation is ready, face on-going “system” problems years after the SAP implementation. Post go-live SAP support is an integral part of a successful SAP implementation and its value should not be underestimated.
Of course it’s not just the go-live support that is important; the initiation, planning and execution phases of a SAP implementation play a significant role in determining the success rate of the go-live period. However, shortfalls in any of these phases typically present themselves during the go-live phase and it will be crucial to correct these shortcomings during the go-live. Fixing problems quickly and effectively with the right resources and being proactive in extrapolating possible other issues from a problem is essential to stave off any ill feeling building up towards the new system. The go-live support team suddenly takes on a far more important role that initially thought.
The success of the SAP implementation starts with the effectiveness of the business blueprint phase as it determines the redefined business process underpinned by the SAP solution, but people operate these new processes, and thus the change readiness assessment is another key factor which provides insight into the success of the go-live phase as it indicates the attitudes and alignment of the end users to the new system. It also determines whether a roll-out site is ready for the go-live phase. For example, a site readiness team is typically deployed to ensure the site is ready for the go- live. Based on the feedback received from the site readiness team, a decision will then be made by the project management to establish if there is additional work required or a phasing of the roll-out required to ensure success.
Consultants often experience numerous hurdles during the go-Live support period. Some of the more severe challenges are:
· When legacy programmes need to be interfaced to the SAP solution. It is essential to make certain that these legacy programmes integrate well with SAP. For example a manufacturing company implemented SAP ~ the organisation used a system called BASIS which integrated with a distribution planning system called FLO.The organisation then changed from BASIS to SAP, which now had to now integrate with FLO. It was imperative that SAP integrated well with the legacy system (FLO) because the sales and distribution planning is still done in FLO and exported back to SAP. Failure of a successful integration will lead to a massive delay in the distribution of stock and can have a huge impact on public perceptions. A good support team will be vital if integration problems occur and there is some form of roll-back required.
· End users often take time to adapt to new business processes, SAP support resources therefore need to play the role of a facilitator throughout the go-live phase, continually reminding uses of the new process and ensuring it is embedded.
· End users place the blame on the SAP system because it’s “not the same as before”. It has often been found that employees do not focus enough on new business processes. This brings about confusion of what duties or functions are allocated to which users.
· False expectations which are embedded in the minds of end users, this triggers the end users to be more resistant during the go-live phase. A good support team needs to reassure and build confidence in end-users
· A lack of training investment, knowledge transfer and refresher courses provided to both the end users and the support team can lead to frustrations.
Factors having a positive impact on the go-live
The following are a few things which can positively impact the success rate of the go- live phase:
· It is vital that users are aware of their new roles and revised job tasks. Continual awareness communication of this is essential during the go-live phase.
· Extensive support team training (if they were not part of the implementation) to ensure that they know and understand their roles as SAP support resources and likely issues they may come across.
· The SAP support resources and end users must have a clear understanding of the organisation’s new business processes. Process based SAP training is preferable to transactional based training.
· Pre go-live assessment periods to enable the support team to identify the end users, and to have an understanding of the end users’ daily tasks. Pre go-live sessions enable the support team to highlight obvious end-user authorisation and access errors, which minimises irritation during the go-live period.
· A clearly defined go-live issue resolution process assists in managing issues as they arise. This is different from the project issue process and should be geared to react immediately as well as extrapolate other possible issues arising out of any other issue.
· Make sure end-users know who to contact to avoid creating an impression that support is not readily available.
· Go out of your way to let end-users know how their issue resolution is progressing.
Patience as well as a positive attitude are the key elements in getting the end users excited about their imminent change.
What to avoid during the go-live phase
If done properly the go-live phase creates the opportunity for the support team and the end-users need to work together in harmony. There are several things that could disrupt the smooth running of this period:
· Recruiting additional support resources during the go-live phase. This has a negative impact on the success rate of the implementation as not enough time is available for the new recruits to fully understand the business process of the organisation and the “catch up”.
· Another key factor to bear in mind is that these recruits will not have enough time to build rapport with the end users. It is therefore vital to ensure that the project has sufficient resources for the various sites at the beginning of the go-live.
· Allowing a “sink or swim” period during the go-live phase that sees end users perform their SAP tasks without assistance from the SAP support resources.
· Support resources carrying out the end users’ daily tasks. The support team should be instructed not to perform transactions for the end users. The support resources SAP access should be limited to display only during the go-live to minimise the impact of “over helping” the end-user.
In conclusion
The go-live phase has its difficulties and the end users are bound to be anxious and fearful of the system. The first few weeks of the go-live period should be used to alleviate these anxieties and fears through constant communication and reassurances from the support resources.
The support team should take into consideration the imperative aspects of a SAP go-live and what to avoid during this phase. The success of the support phase therefore lies in the execution or avoidance of the above mentioned points.
The highlight of the go-live phase is when the support resources leave the sites with the confidence that the end user will be able to cope on their own and that the time spent at the sites has added value to the organisation as a whole.