ASAP Methodology in Implementing ERP

Loading...

Flash Player 9 (or above) is needed to view presentations.
We have detected that you do not have it on your computer. To install it, go here.

3 comments

Comments 1 - 3 of 3 previous next Post a comment

  • + harikiran515 harikiran515 3 months ago
    hello,will u plz send this slides to my mail harikiran515@gmail.com.i wil be waitng for ur reply nd ur mail.

    thnks hari
  • + prasadtv prasadtv 8 months ago
    this is downloaded By service site of sap
  • + guest93c3d guest93c3d 2 years ago
    Hi Arun

    I appreciate it. This excellent and very useful in all ascepts



    Thank You

    Regards

    Bala
Post a comment
Embed Video
Edit your comment Cancel

9 Favorites

ASAP Methodology in Implementing ERP - Presentation Transcript

  1. SAP Implementation Methodology
  2. Business Benefits of ERP
    • Improve alignment of strategies and operations
    • Standardize the business processes in the organization.
    • Achieve better efficiency of operation.
    • Adopt best practices, processes and systems
    • Set up and Implement an integrated and up to date IT SAP system
    • Rationalize multiple non-integrated systems into one common solution
    • Replace a high percentage of manual tasks with an automated solution through SAP
    • Provide immediate access to enterprise information
  3. Projects from another perspective
    • “ An estimated 68% of corporate IT projects are neither on time nor budget, and they don’t deliver the originally stated business goals. Some even claim that during the last two years, $100 billion to $150 billion of U.S. IT projects have failed altogether.”
    • Mark Jeffery and Ingmar Leliveld: Best Practices in IT Portfolio Management, MITSloan Management Review, Spring 2004
  4. Ingredients of Success
    • Adequate budget
      • including training, documentation and conversion.
    • Alignment with Business Goals:
      • The strategic objectives of the program should be in alignment with organization’s business goals.
    • Clear and concise Deliverables
    • End-User Involvement
      • People need to be involved from beginning to end. Top-down control without bottom-up involvement is a recipe for disaster.
    • Adequate Training:
      • Training is not an expense; it is investment in human resource.
    • Change Management:
      • When changes are prepared for and introduced gradually, it does not make people insecure and resentful; it turns them into advocates
  5. Typical questions when you starting the project How to best use selected solution capabilities? Do we have internal capabilities and capacity to staff the project? How and where do we start? Who does what in this project? How expensive will this project be? How do we keep the costs low? How to manage project and business risks involved? How do we assure success? How to build internal expertise?
  6. Delivering Successful Solutions AcceleratedSAP Methodology
    • Accelerated SAP (ASAP) is SAP's standard implementation methodology. It contains the Roadmap, a step-by-step guide that incorporates experience from many years of implementing R/3.
    • Accelerated SAP contains a multitude of tools, accelerators and useful information to assist all team members in implementing R/3. Quality checks are incorporated at the end of each phase to easily monitor deliverables and critical success factors.
    Leverage SAP implementation experience Description
  7. Phase 1 : Project Preparation Goal Setting Define project goals & objectives Implementation strategy 1.Clarify the scope of implementation 2.Establish the project organization and relevant committees and assign resources Implementation Sequence Define sequence in project has to be executed Team Core team+ project team+ consultant team Sign Off At the end of phase every above steps will be documented & will be signed off with the client During this phase the team goes through initial planning and preparation for SAP project.
  8. Project Preparation The purpose of this phase is to provide initial planning and preparation for your SAP project. Although each SAP project has its own unique objectives, scope, and priorities; the steps in Phase 1 help you to identify and plan the primary focus areas that need to be considered.
  9. Phase 2 : Business Blueprint SCOPE DOCUMENT This document will consists of questionnaire of entire business process AS IS 1.Understanding the business Process from the core team. 2.Based on the input ASIS document has to be created according to module wise TO BE 1.In this process will map the business process in SAP based on ASIS 2.Module wise TOBE document has to be created GAP ANALYSIS 1.The GAP b/w ASIS process & TOBE process is called GAP analysis ie., The inputs or the business process which can’t mapped into standard SAP will be analyzed here 2.GAP document has to be created SIGN OFF Each process above has to be taken sign off from client The purpose of this phase is to achieve a common understanding of how the company intends to run SAP to support their business . The result is the Business Blueprint, a detailed documentation of the results gathered during requirements workshops.
  10. Business Blueprint The purpose of this phase is to create the Business Blueprint, which is detailed documentation of the results gathered during requirements workshops. Furthermore, the Business Blueprint documents the business process requirements of the company. With this, you can better understand how the company intends to run its business within the SAP System
  11. Phase 3 : Realization Baseline Major scope Final Configuration Remaining scope SIGN OFF Each process above has to be taken sign off from client The purpose of this phase is to implement all the business process requirements based on the Business Blueprint. The system configuration methodology is provided in two work packages: Baseline (major scope); and Final configuration (remaining scope).
  12. Realization The purpose of this phase is to implement business and process requirements based on the Business Blueprint. The objectives are final implementation in the system, an overall test, and the release of the system for production (live) operation. In addition, the project team receives relevant knowledge.
  13. Phase 4 : Final Preparation Unit Testing Testing within each module Integration Testing Integrate testing of modules ie., combine testing of all the modules User Training The purpose of this phase is to complete the final preparation (including testing, end user training, system management and cutover activities) to finalize your readiness to go live. The Final Preparation phase also serves to resolve all critical open issues. On successful completion of this phase, you are ready to run your business in your live SAP System. Cut over Strategy legacy system will be migrated to SAP system. SIGN OFF Each process above has to be taken sign off from client
  14. Final Preparation The purpose of this phase is to complete the final preparation (including testing, end user training, system management and cut-over activities), to finalize your readiness to go live. The Final Preparation phase also serves to resolve all crucial open issues. On successful completion of this phase, you are ready to run your business in your live SAP System.
  15. Phase 5 : Go Live & Support Production Support Monitor System Transactions Optimize Performance The purpose of this phase is to move from a project-oriented, pre-production environment to live production operation. Help Desk & Competency Center
  16. Go Live and Support The purpose of this phase is to cut over to live productive operation and to continuously support and improve live operations
  17. NEW GlobalASAP Local Rollout Roadmap Final Preparation Project Preparation Business Blueprint Realization Project Mgt OCM + Training System Prep Processes Data Cutover Setup of Local Project Organization Adaption of Strategic Framework Establish OCM Procedures + Responsibles Infrastructure Requirements and Design Early Adoption of Best Business Practice Proceesses Training and Documentation Strategy Data Management Standards Implementation Data Cleansing and Data Preparation Completion Check & Prepare for Next Phase General Project Management Local Business Blueprint Documentation Security Requirements Infrastructure Planning System Operation Stategy Early Adoption of Best Business Practice Processes Training Planning Data Cleansing and Data Preparation Completion Check & Prepare for Next Phase OCM Organizational Alignment + Change Analysis General Project Management OCM Training Preparation Configuration & Development Unit / Process / Integration / Business Acceptance Testing Early Adoption of Best Business Practice Processes Infrastructure Implementation Data Preparation & Data Migration Simulation Completion Check & Prepare for Next Phase Cutover Planning & Preparation Business Transition Planning for Cutover General Project Management OCM End User Training End User Practice in the System Data Migration to Production Infrastructure Finalization Cutover Management Business Simulation Pre-Go-Live Operations Completion Check & Prepare for Next Phase Final Cutover and Controlled Process GoLive GoLive and Support General Project Management OCM Project Closing System Support Business Support
  18. Key components for success AcceleratedSAP - proven methodology Project Management expertise Management of the implementation project Aligned with industry standards and procedures (PMI PMBOK ® ) Specific to implementation of SAP solutions Aligns customer’s business requirements to SAP solutions SAP Solution Composer Offers AcceleratedSAP roadmap composed to fit specific project needs SAP Roadmaps Facilitates efficient solution design, documentation, configuration, testing and operations SAP Solution Manager AcceleratedSAP toolset
  19. Roadmap Adds Value to the Implementation What to do, and when to do it Who participates When used properly, a roadmap will provide guidance on the following: Knowledge Area Why and how you should do it Accelerators, Samples, Templates
  20. Implementation Roadmap - Structure
    • Phase
      • Deliverable Group 1
        • Deliverable
        • O: Output α .1
          • O: Output α .2
        • M: Activity 1.1
            • Task 1.1.1
            • Task 1.1.2
          • M: Activity 1.2
            • Task 1.2.1
      • Deliverable Group 2 Milestone A
    Deliverable consists of several outputs Methods (activities and tasks) that create or contribute to creation of the deliverable
  21. Hope we will not end up like this
    • THANK YOU

+ sharafsharaf, 2 years ago

custom

6060 views, 9 favs, 1 embeds more stats

More info about this document

© All Rights Reserved

Go to text version

  • Total Views 6060
    • 6059 on SlideShare
    • 1 from embeds
  • Comments 3
  • Favorites 9
  • Downloads 786
Most viewed embeds
  • 1 views on http://www.brijj.com

more

All embeds
  • 1 views on http://www.brijj.com

less

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate. If needed, use the feedback form to let us know more details.

Cancel
File a copyright complaint
Having problems? Go to our helpdesk?

Categories