ASAP Methodology in Detail

(ASAP) Roadmap, which originated in 1996, is still the backbone of more advanced and similarproject methodologies – it can be downloaded as a PDFHere Or referenced as an overview below: Phase 1: Project Preparation Phase 2: Business Blueprint Phase 3: Realization Phase 4: Final Preparation Phase 5: Go Live & Support Phase 1: Project Preparation In this phase of the ASAP Roadmap, decision-makers define clear project objectives and an efficient decision-making process. Here Project Organization and roles are defined and implementation scope is finalized. System landscape and Technical Requirement     Infrastructure need (Hardware/interfaces) System Landscape High level strategies for client Archiving strategy Issues Database: Issues must be resolved before phase completion ot before beginning of the next phase. The issues can be    Unanticipated tasks Normal tasks that can not be completed External factors that need to be dealt with. Issues database allows the project team to enter, track and report on project issues. Phase 2: Business Blueprint In this phase scope of the R/3 implementation is defined & Business Blueprint is created. Business Blueprint is a detailed documentation of company’s requirements. Various tools are used in this phase.    AcceleratedSAP Implementation Assistant Question & Answer Database (Q&Adb) Business Process Master List (BPML) It is used to identify. Implementation Guide (IMG): It is the main tool for setting the parameters to configure or ‘Customize’ . BPML is a representation of the R/3 business and transactions that are contained within the scope of the project. schedule and monitor the configuration and testing of all R/3 scenarios and processes within the scope of an implementation. The configuration is carries out in two steps. baseline configuration & Final configuration.  R/3 Structure Modeler Business Navigator and external modeling tools Project Management: Activities in this work package are:     Conducting Status meeting for project team Conducting steering committee meetings General project management Addressing organizational issues relating to organizational change management. BPML is feeds all business information to all subsequent worksheets. Other activities include:     Project Team Training Developing the System Environment Defining Organizational Structure Defining the Business processes R/3 reference model can be used for      Comparing the standard functionality with your companies own organizational requirements Creating documentation for the conceptual design Optimizing business processes Training the project team and users Writing user documentation Question and Answer Database can be used to determine    The Baseline Scope Cycle Plan Integration test Plan Phase 3: Realization The purpose of Phase 3 is to configure the R/3 system. Business Process Master List (BPML) is created in phase 2 as a report from Q&A database. plan. transfer of legacy data and support at early stages. InfoDB may be used to plan for the User Training activities. Phase 4: Final Preparation The purpose of this phase is to complete the final preparation of the R/3 system for going live. This includes preparation of end-user documentation and training the end-users. Simulation of productive operation system & testing the same is of great important. Preparation for end-user training needs to be gone through and approved at and of this phase. user training. In this phase the R/3 system is handed over to individual departments for productive operation. End-user training is a critical activity for success of the project. The test plan contains the following activities   Testing conversion procedures and programs. This includes testing. This internal quality check should be carried out in addition to an external. Project managers prepare plans for going live. IMG reflect the chronological order in which the customizing activities are carried out.R/3 during the realization phase. system management and cutover activities. Computer Center Management System (CCMS) must be set at this time. The following aspects of configuration are also to be considered:    Defining authorizations in the R/3 system Defining workflows Creating user documentation System Manager Procedures        Developing system test plans Defining service level commitment Establishing system administration functions Setting up Quality Assurance environment Defining the design of the productive system Defining system management procedures for the productive system Setting up the productive environment At the end of this phase. to finalize your readiness to go live. Project Manager must check the status of deliverables for completeness and accuracy. Testing interface programs . The technical environment is installed on production system & is tested. independent third party Quality Audit.        Post to Facebook Post to Twitter Add to LinkedIn Add to Google Bookmarks Send via E-mail program Post to Pinterest Post to StumbleUpon Tags:ASAP . During phase 5. SAP Tricks . where experts from SAP analyze the system’s technical infrastructure. Validation of business processes and their configuration.   Conducting volume & stress testing Conducting final user acceptance testing Developing a final go-live strategy. with standard activities necessary after implementation. Phase 5: Go Live & Support This phase is concerned with supporting and optimizing the operative R/3 system. technology changes or changes in user community. the first EarlyWatch session should be held. Project Methodology . Disaster downtimes are verified and details on de-escalation. Following activities are carried out     Production support facilities are defined. Phase 4 also provides for the testing of the disaster recovery plan for the productive environment. AcceleratedSAP contains a continuous roadmap. The tasks in that structure provide solutions for all known types of continuous change: Business changes. The aim is to ensure the system functions as smooth as possible. The Computer Aided Test Tool (CATT) can be used to automate test sequences for key business processes. Version upgrades should be planned whenever found necessary. Follow-up training for users Signoffs etc. ASAP empowers companies to exploit the power of the accelerated features and tools already built into SAP solutions. standards. The solution is tested in a number of cycle tests 2. The objectives of the project are validated. the baseline configuration. deliverable-oriented methodology that streamlines implementation projects. Business blueprint 3. and checklists. questionnaires. a series of structured process workshops are planned and executed to arrive at the “to-be delivered" SAP enterprise solution. the project procedures. are documented in the SAP Solution Manager application management solution. The methodology supports project teams with templates. the SAP software system is configured and tested in a number of cycles. and the project standards and organization are set up. At the same time. and all initiation activities are documented in the project charter. which represents the core business process settings. minimizes risk. Project preparation In the project preparation phase. Roles and responsibilities of the entire project team are agreed upon and documented. and other disciplines applied in the implementation of SAP solutions. During this business blueprint phase. tools. Executive sponsorship is secured. All available documentation for standard. including guidebooks and accelerators. organization. the project team defines project goals. thanks to proven tools. coupled with project issues and gaps. is performed.ASAP Methodology for Implementation Purpose The ASAP methodology for implementation is a phased. to implement the entire end-to-end solution. delivered support for SAP business scenarios and all relevant preconfigured support for best practices are reviewed and discussed with SAP experts. Realization . organizational change management. a high-level scope. tested. and best practices  Lower risk  More efficient use of resources  Reduced costs  Effective project management based on Project Management Institute standards Phases The ASAP methodology delivers the following phases: 1. Benefits of ASAP include:  Faster implementations with streamlined and focused methodology  More reliable projects. In the realization phase. Initially. solution management. ASAP takes a disciplined approach to project management. All functional and technical requirements. solution and technical designs are documented in the business blueprint. and staffing are finalized. accelerators. This is followed with a series of configuration and development cycles. The implementation strategy is defined and approved. and a project plan. and reduces total cost of implementation. and confirmed. Lead by solution and industry experts from the SAP Consulting organization. with the documented solution based on the transferred project documentation. The central operation platform is SAP Solution Manager. data conversion programs. Detailed transition and cutover plans are created. the production system is switched on and business operations start in the new environment.and in a focused end-to-end integration test. the methodology lists the number of deliverables that are to be produced in each phase of the project. . The customer support organization is put in place. 5. Go-live support 6. and any required enhancements are built and documented in SAP Solution Manager. Configuration is documented in SAP Solution Manager. At the end of this phase. all systems are known to function correctly following the approved integration test. For each work stream. but also for long-term support. The recommended starting point of the phase is an assessment of solution operation after the go-live support phase to identify the relevant SAP standards for solution operations to be established or improved in the phase. The primary goal of the run phase is to ensure the operability of the solution. The production system is set up with transports and customer data. all integration issues should now be resolved. Run Work Streams The ASAP methodology is structured around the key project work streams that are outlined in the picture below. The purpose of the go-live support phase is to move from a preproduction environment to live production operation. Legacy data conversion programs are created and tested. Operability is the ability to maintain IT solutions in a functioning and operating condition. The production system is installed during realization. Technically. reports. All development such as enterprise services. Final preparation Within the final preparation phase. 4. not just for the first critical days of production operations. An easily accessible production support organization must be in place to support the end-user community. guaranteeing systems availability and required performance levels to support the execution of the enterprise’s business operations. interfaces. GPFS. Massachusetts Institute of Technology. and MultiWin are trademarks or registered trademarks of Citrix Systems. Acrobat.The deliverables in later phases leverage or build upon deliverables completed in earlier stages. Netfinity. . Intelligent Miner. z/OS. OSF/1. AS/400. UNIX. Citrix. IBM. Windows. POWER5+. WinFrame. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.S. hierarchical manner and managing the project work to completion. MetaFrame. OS/2. DB2 Connect. samples. System z10.. Tivoli and Informix are trademarks or registered trademarks of IBM Corporation. the Adobe logo. The roadmap is structured as a work breakdown structure (WBS) that represents a complete list of deliverables that need to be completed by the project team. Redbooks. Clear Enterprise. POWER. i5/OS. JavaScript is a registered trademark of Sun Microsystems. POWER5. iSeries. System i5. Duet. S/390 Parallel Enterprise Server. DB2. The ASAP methodology for implementation projects represents a standardized work breakdown structure that provides the foundation for defining implementation project work in a deliverable-oriented. World Wide Web Consortium. XML. AIX. System x. Power Architecture. pSeries. and Motif are registered trademarks of the Open Group. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. HACMP. ICA. R/3. XHTML and W3C are trademarks or registered trademarks of W3C®. System z9. WebSphere. eServer. z9. Linux is the registered trademark of Linus Torvalds in the U. Inc. The information contained herein may be changed without prior notice. System z. BatchPipes. Outlook. VideoFrame. Program Neighborhood. zSeries. System i. z10. Excel. SAP NetWeaver. OS/390. PowerPC. HTML. DB2 Universal Database. SAP. ByDesign. PostScript. and other countries. and PowerPoint are registered trademarks of Microsoft Corporation. SAP – Copyrights and Trademarks © 2010 SAP AG. OpenPower. z/VM. ASAP methodology contains a standard set of templates. and checklists for use by project teams in effectively managing and completing SAP solution implementation projects. POWER6. Oracle is a registered trademark of Oracle Corporation. and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries. RETAIN. All rights reserved. Inc. SAP BusinessObjects Explorer and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries. System p5. RACF. X/Open. Parallel Sysplex. OS/400. guidelines. System Storage. Microsoft. Inc. POWER6+. MVS/ESA. accelerators. used under license for technology invented and implemented by Netscape. Java is a registered trademark of Sun Microsystems. System p. BladeCenter. PowerVM. Adobe. S/390. xSeries. PartnerEdge. if any. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services. These materials are subject to change without notice. National product specifications may vary. Crystal Reports. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only.Business Objects and the Business Objects logo. and SAP Group shall not be liable for errors or omissions with respect to the materials. Crystal Decisions. All other product and service names mentioned are the trademarks of their respective companies. Web Intelligence. . Nothing herein should be construed as constituting an additional warranty. Xcelsius. and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP France in the United States and in other countries. without representation or warranty of any kind. BusinessObjects. Data contained in this document serves informational purposes only.