ASAP Methodology
ASAP Methodology
Each business blueprint document essentially outlines your future business processes
and business requirements. The kinds of questions asked are germane to the particular
business function, as seen in the following sample questions:
1) Your SAP consulting team helps you configure your baseline system, called the
baseline configuration.
2) Your implementation project team fine-tunes that system to meet all your
business and process requirements as part of the fine tuning configuration.
The initial configuration completed during the baseline configuration is based on the
information that you provided in your blueprint document. The remaining
approximately 20% of your configuration that was not tackled during the baseline
configuration is completed during the fine tuning configuration. Fine tuning usually
deals with the exceptions that are not covered in baseline configuration.
Configuration Testing-
With the help of your SAP consulting team, you segregate your business processes into
cycles of related business flows. The cycles serve as independent units that enable you to
test specific parts of the business process. You can also work through configuring the
SAP implementation guide (IMG). A tool used to assist you in configuring your SAP
system in a step by step manner.
Knowledge transfer to the configuration team tasked with system maintenance (that is,
maintenance of the business processes after Go-live) needs to be time. In addition, the
end users tasked with actually using the system for day-to-day business purposes
must be trained.
> Phase 4 – Final Preparation:
- As phase 3 merges into phase 4, you should find yourselves not only in the midst
of SAP training, but also in the midst of rigorous functional and stress testing.
- Phase 4 also concentrates on the fine tuning of your configuration before Go-live
and more importantly, the migration of data from your old system or systems to
SAP.
- Workload testing (including peak volume, daily load, and other forms of stress
testing), and integration or functional testing are conducted to ensure the
accuracy of your data and the stability of your SAP system. Because you should
have begun testing back in phase 2, you do not have too far to go until Go-live.
- Now is an important time to perform preventative maintenance checks to ensure
optimal performance at your SAP system. At the conclusion of phase 4, take time
to plan and document a Go-live strategy. Preparation for Go-live means
preparing for your end-users questions as they start actively working on the new
SAP system.
> Phase 5 – Go-live and Support: The Go-live milestone in itself is easy to
achieve; a smooth and uneventful Go-live is another matter altogether.
Preparation is the key, including attention to what-if scenarios related not only to
the individual business processes deployed but also to the functioning of
technology underpinning these business processes and preparation for ongoing
support, including maintenance contracts and documented processes and
procedures are essential.