Dear Ameer,
<b>ASAP Methodology</b>
Forward Media has adopted ASAP (Accelerated SAP) as its methodology of choice for SAP implementations, upgrades and module additions.
Our in-depth knowledge of ASAP allows us to customise and streamline ASAP to suit widely varying project requirements. For example - while ASAP was originally conceived as an implementation methodology, Forward Media has found ways to apply its strengths to the smaller tasks of SAP upgrades and new module additions. Innovations such as these have become part of standard and offically endorsed ASAP methodology.
Our involvement with the ASAP methodology began in 1996, when Forward Media Director Nadia Ward worked extensively with SAP America on the creation of the original ASAP methodology. Nadia led the technical component of the first commercial trial of ASAP in an implementation for CFS in New York - in the process contributing several operational templates to the ASAP toolkit.
ASAP Phases
The ASAP methodology structures the project lifecycle into five phases which run sequentially from project start to project completion. These standard ASAP phases are:
1. Project Preparation
2. Business Blueprint
3. Realisation
4. Final Preparation
5. Go-Live and Support
Concurrently with these ASAP phases, we also run a series of continuous processes which cover the types of activities which, by their nature, transcend individual phase boundaries (eg: Quality Assurance) or which require activity throughout the project lifecycle (eg: Knowledge Transfer).
These continuous processes identified as necessary for most SAP projects:
1. Quality Assurance
2. Data Migration
3. Basis
4. Knowledge Transfer
5. Cutover Planning
6. Project Accelerators
Together, the ASAP phases and our continuous processes define the broad outline of our approach for SAP projects.
Project Management Toolkit
Forward Media has a series of Project Management tools in addition to those sourced from ASAP that we make available to our clients. These include templates such as our:
• Project Plan Template (for SAP Implementations and Upgrades)
• Data Conversion Strategy
• Cutover Plan
• ABAP specifications
• Test Scripts
• Client Landscape
• Change Management Strategy
• Month End Schedule
• Issues Log
• Phase 1: Project Preparation
• Phase 2: Business Blueprint
• Phase 3: Realization
• Phase 4: Final Preparation
• Phase 5: Go Live & Support
<b>Phase 1: Project Preparation</b>
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): Available- QuickSizing Service: to be accessed via SAPNet
• 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.
<b>Phase 2: Business Blueprint</b>
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)
• R/3 Structure Modeler
• Business Navigator and external modeling tools
<b>Project Management:</b>
Activities nagement: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.
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
<b>Phase 3: Realization</b>
The purpose of Phase 3 is to configure the R/3 system. The configuration is carries out in two steps; baseline configuration & Final configuration.
Business Process Master List (BPML) is created in phase 2 as a report from Q&A database. It is used to identify, plan, schedule and monitor the configuration and testing of all R/3 scenarios and processes within the scope of an implementation. BPML is a representation of the R/3 business and transactions that are contained within the scope of the project. BPML is feeds all business information to all subsequent worksheets.
<b>Implementation Guide (IMG):</b>
It is the main tool for setting the parameters to configure or ‘Customize’ R/3 during the realization phase. IMG reflect the chronological order in which the customizing activities are carried out.
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, Project Manager must check the status of deliverables for completeness and accuracy. This internal quality check should be carried out in addition to an external, independent third party Quality Audit.
Preparation for end-user training needs to be gone through and approved at and of this phase.
<b>Phase 4: Final Preparation</b>
The purpose of this phase is to complete the final preparation of the R/3 system for going live. This includes testing, user training, system management and cutover activities, to finalize your readiness to go live.
In this phase the R/3 system is handed over to individual departments for productive operation. This includes preparation of end-user documentation and training the end-users. The technical environment is installed on production system & is tested. Project managers prepare plans for going live, transfer of legacy data and support at early stages.
End-user training is a critical activity for success of the project. InfoDB may be used to plan for the User Training activities. Computer Center Management System (CCMS) must be set at this time. Simulation of productive operation system & testing the same is of great important.
The test plan contains the following activities
• Testing conversion procedures and programs.
• Testing interface programs
• Conducting volume & stress testing
• Conducting final user acceptance testing
• Developing a final go-live strategy.
The Computer Aided Test Tool (CATT) can be used to automate test sequences for key business processes.
Phase 4 also provides for the testing of the disaster recovery plan for the productive environment. Disaster downtimes are verified and details on de-escalation.
<b>Phase 5: Go Live & Support</b>
This phase is concerned with supporting and optimizing the operative R/3 system.
Following activities are carried out
• Production support facilities are defined.
• Validation of business processes and their configuration.
• Follow-up training for users
• Signoffs etc.
During phase 5, the first EarlyWatch session should be held, where experts from SAP analyze the system’s technical infrastructure. The aim is to ensure the system functions as smooth as possible.
Version upgrades should be planned whenever found necessary. AcceleratedSAP contains a continuous roadmap, with standard activities necessary after implementation. The tasks in that structure provide solutions for all known types of continuous change: Business changes, technology changes or changes in user community.
with regards,
B.Ravindranath
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.