ASV recommends the ASAP methodology (Accelerated SAP implementation methodology) for SAP implementation at Client. The implementation will be carried out based on ASV’s proven onsite/offshore methodology. This methodology will cover the relevant deliverables/milestones and will build on the ASAP methodology. This encompasses the following ASAP phases – Preparation phase, Blueprint phase, Realization phase, Final Preparation phase, Go-live and Support phase. ASV directors have devised ready-made templates for Business Blueprint, Customization, testing and cut over. The templates gives added advantages in finalizing the processes and release them to production in shortest possible time without disturbing quality, stability and scalability. Typically, the template will help to complete the full-fledged implementation of standard SAP HCM modules, with minimum deviations, in 24 to 32 weeks including 4 weeks of Post Go live support. Thus, overall the savings in terms of Cost and Time because of templates is in the range of 10% to 25% based on 25% or greater deviations with standard SAP functionality.
ASV provides support for SAP modules is based on majorly three business models. These business models are designed to suit customer’s fundamental expectation to achieve ultimate satisfaction. First and most popular business model is based on dedicated support of ASV resource. The resource may be posted at customer location or at the ASV office. The second model and most recommended model is shared service model, which allows customer to use minimum hours per month. The bucket of hours can be used for support of various SAP modules. The customer has flexibility to use the bucket and thus utilized the bucket to fullest strength. Finally, the third model is to use resources on call basis with agreed terms and condition and rates. The second and most recommended model of support uses a bucket of agreed hours. ASV provides a methodology to calculate maximum hours of bucket. The implementation of the share service model has adopted strategies to track and control the support activities. The matrix, given below are suggesting the controls which can be adopted.
Support Categorisation and strategy
The world of support is based on Time of resolution and Cost of resolution, The Shared services methodology utilizes best of both worlds.
Adherence to the SLA
Optimization of Support cost
Shared services model is one of the most cost effective models which ASV is currently recommending to its clients. Some of the key features of the Shared service model are:
Time-tested shared services model serving various SAP clients
Pre-determined team for the client (but shared with other clients) to retain client specific knowledge
Named Single Point of Contact, named primary for every functional area and a named secondary for every functional area
Team leverages the competency leads for complex issues and for change requests.
Shared team provides fractional FTEs with predefined window of support period
Knowledge Repository to improve SLAs
ASV Shared service model is flexible to take care of the increased support resource requirement and hence for the client.
Shared team at offshore/Onsite will be scaled up to supplement project related needs that might come in
Capacity for the offshore Shared pool will be refined based on the ticket flow rate that will be collected during transition phase.
Capacity will be adjusted based on Quarterly review
Resource mix will be changed depending on nature and volume of issues and functional areas of enhancements
The existing SAP HCM implementation is not used to the fullest extent because of several reasons. The cost of such dormant implementation is generally high. Besides the cost, the important MIS reports are never generated in time or it might be taking long to generate. The report generation may include several manual steps and hence, the sanctity of MIS reports is hardly guaranteed. uses its expertise to suggest solutions at process level as well as at the SAP HCM level. The suggestions are always implementable and easy to use without severe divergence in functionality and operations.