About Us  |  Services  |  Solutions  |  Careers  |  Contacts
 |  Home  |  Investors  |  Sitemap
  
 
Case Study
 





 

Implementation Methodology

R Systems domain expertise coupled with ASAP™ implementation methodology provides solution mapping and consulting services resulting in reduction in the overall efforts and rework.

The ASAP™ methodology is designed to support project teams during their effort to plan, manage, and deliver effective SAP implementation across multiple sites and geographies. ASAP™ allows to utilize the value of the SAP System and also lays the foundation for continuous improvement.

ASAP toolset comprises of the following powerful tools used for successful planning and implementation

  • SAP Solution Manager: Facilitates proficient solution design, documentation, configuration, testing and operations of SAP solutions.
  • SAP Solution Composer: Helps to integrate people, data, and business processes. It can be used to visualize, plan and implement customer’s business requirements to SAP solutions.
  • SAP Road maps: Sequence of modules that a single company should follow to assure the best outcome. ASAP roadmaps are composed to fit specific project needs.

The Accelerated SAP consists of the following five phases. The actions to be carried out in each of these phases will change according to the nature of the implementation and the choice of technology.

The phases are as follows:

Phase 1: Project Preparation
During this phase of project preparation; the team goes through initial planning and preparation for SAP project. During this phase preliminary preparations are made that includes setting up the plan of approach, formulating a detailed project schedule, budget plan, finalize the project organization and initiation of training programs for core team members. The preparation generally starts with a kick off meeting during which the project team and process owners become aware of the project charter & objectives and are allocated their responsibilities, lasting throughout the project.

Phase 2: Business Blueprint
The key objective of business blueprint phase is to achieve a common understanding of - How company intend to run the business & Which SAP business processes and components are necessary to support the same?

The outcome of this phase is the Business Blueprint - a detailed documentation of the results gathered during requirements workshop. After customer approval, business blueprint serve as a basis for system configuration and accepted throughout the project.

Phase 3: Realization
During Realization phase SAP consultants configure all the business process requirements based on the Business Blueprint. The system configuration in this phase is carried out in two steps, baseline and final configuration. The baseline system configuration reflects organizational structure, daily business transactions, and all of master data.

The final configuration is done in process oriented cycles. During this phase confirmation is done on all requirements being met in the SAP system. Final configuration is the transportation process that expands base line solution.

Other key focal areas of this phase are conducting integration tests and drawing up end user documentation.

Phase 4: Final Preparation
The purpose of this phase is to run a final technical system test, provide key user training and to migrate data and system to production environment.

During this phase the key users go through comprehensive training, as per “Train-the-Trainer” concept. After migration of data and user trainings the final step before turning the ignition key "ON", the new system is to check whether the system and the user organization are ready to go live.

Phase 5: Go Live and Support
The purpose of Go-live & Support is to move from a project-oriented, pre-production environment to live production operation. After production start-up, the system must be checked again and fine tuned whereever necessary to guarantee that all facets of business environment are represented in the system.

During Support phase, the consultant team supports the management organization and an operational helpdesk is also formed to which users can report their problems.

In final step of this phase, the system is transferred to the organization and the project is formally closed.