Page 228 -

Chapter 7
In the Realization phase (the third phase), the project team members work with
consultants to configure the ERP software in the development system. In an SAP
implementation, a company uses three separate SAP systems over the course of the
implementation process—a development system for configuring the SAP software to match
the Business Blueprint, a test (or quality assurance) system for evaluating the software
configuration, and a production system, on which the company runs the final software.
The team also develops any necessary ABAP code or other tools (such as third-party
software packages) and creates the required connections to the legacy systems.
The fourth phase, Final Preparation, is critical to the success of the implementation
project. Tasks in this phase include:
208
• Testing the system throughput for critical business processes (determining
whether it can handle the volume of transactions) in the quality assurance
system
• Setting up the help desk where end users can get support
• Setting up operation of the production system and transferring data from
legacy systems
• Conducting end-user training
• Setting the Go Live date
When scope creep occurs in a project, it is commonly not discovered until well into
the Realization phase, when the team begins to miss deadlines, and the costs begin to
exceed the budget. By the time the scope creep is discovered and its impact is understood,
there is often little management can do to correct the problem, as most of the time and
budget have been spent. In some cases, management chooses to shorten or omit the Final
Preparation phase, which means that testing of the system and training of employees are
reduced or eliminated. Unfortunately, with reduced testing, errors in configuring the
system may not be discovered until it is put into use. Likewise, with reduced training,
employees may not know how to use the system properly, which can create a complicated
chain of problems, due to the integrated nature of the system. Any cost savings gained by
shortening the Final Preparation phase are often overshadowed by productivity losses and
consulting fees in the Go Live and Support phase.
In the fifth and final phase, Go Live and Support, the company begins using the new
ERP system. Wise managers try to schedule the Go Live date for a period when the
company is least busy. A properly staffed help desk is critical for the success of the Go
Live phase because users have the most questions during the first few weeks of working
with a new system. The SAP ERP project team members and consultants should be
scheduled to work the help desk during the first few weeks of the Go Live period.
Although significant testing of the system and settings should have been done
throughout the project, it is not possible to test all the settings and thoroughly evaluate
the throughput of the system. Therefore, monitoring of the system during the Go Live and
Support phase is critical so changes can be made quickly if the performance of the system
is not satisfactory. Finally, it is important to set a completion date for the project. Any
enhancements or extensions to the system should be managed as separate projects, not as
extensions of the original implementation project.

Copyright 2012 Cengage Learning. All Rights Reserved. May not be copied, scanned, or duplicated, in whole or in part. Due to electronic rights, some third party content may be suppressed from the eBook and/or eChapter(s).
Editorial review has deemed that any suppressed content does not materially affect the overall learning experience. Cengage Learning reserves the right to remove additional content at any time if subsequent rights restrictions require it.