Efficiently detect and avoid time and budget overruns

When businesses purchase enterprise resource planning (ERP) and business management software, they typically end up spending as much for implementation and consulting services as they do for the software licenses. Knowing this should serve as important motivation for customers to inform themselves of the key factors contributing to successful software implementations and the pitfalls they must avoid.

The 2006 CHAOS survey by The Standish Group reveals that across all industries only 35% of software implementations are considered successful, 19% are considered failures, and 46% are considered to be challenged.1 Why? Inadequate project planning and requirements gathering, unclear roles and respon sibilities, and unreasonable customer expectations are the primary reasons why so many implementation projects fail.

Too often projects turn out to be more costly than foreseen or take longer than anticipated. Furthermore, the software implemented frequently does not meet the unique business requirements of an organization and customer expectations in terms of functionality and usability. SAP knows that in today’s business environment, companies simply cannot afford to spend a long time implementing software solutions. Not only will a lengthy implementation reduce staff productivity and lower customer service, it can also make your market position vulnerable to threats from your competitors.

Accelerated Implementation Methodology for SAP Business One

Implementations need not morph into ordeals. Well-planned, customer-focused implementations that follow a structured framework are likely candidates for success, with straightforward migrations and integration, few interruptions, and low user stress to yield a rapid ROI.

With that in mind, SAP developed an accelerated implementation methodology for the SAP® Business One application to provide a clear, proven framework to manage the project and customer expectations and provide guidelines for communication and documentation.

SAP created the accelerated implementation methodology (formerly known as SAP AIP) in conjunction with our active implementation partners, thus tapping into their years of experience in the field. Since its release, the methodology has been used in several thousand implementations worldwide and has become the standard for best-practice implementations of SAP Business One.

The objective of this document is to acquaint you with the major stages of the accelerated implementation methodology and give you a better understanding of how SAP goes about implementing your ERP investment. For each phase in the implementation, we describe the major milestones and relevant components. We also estimate resource requirements and suggest the best practices customers should be prepared to follow before implementing SAP Business One.

Five-Phase Implementation


The accelerated implementation methodology divides the implementation projects into phases. It starts when the customer signs the contract – the time when the sales organization hands the project over to the consulting and implementation organization. It goes on to cover the entire implementation process and the concluding review and optimization conference, which takes place several weeks after the project is handed over to the customer.

The fives phase of the methodology are described below.

Project Preparation

The purpose of this phase is to provide initial planning and preparation for the SAP Business One implementation. Although each SAP Business One implementation has its own unique objectives, scope, and priorities, the steps in the project preparation phase help identify and plan the primary focus areas that need to be considered. This includes technical issues as well as project management topics. With the kickoff meeting, the SAP implementation team communicates the project plan along with the expected commitment your organization will have to make in terms of time and resources. Roles and responsibilities of the various participants in the project are identified. In addition, the SAP Business One software is delivered and the preliminary installation of a test system is completed. This phase is usually performed within five days.

Major Milestones

  •     The major milestones of the project preparation phase are:
  •     Project handover to implementation
  •     Customer kickoff meeting
  •     Delivery and installation of test system for the SAP Business One software
  •     Project phase review and sign-off from customer Best-Practice Recommendations The best-practice recommendations for the project preparation phase include:
  •     Make sure the SAP sales team is present at the kickoff meeting to recap your expectations – informed during the sales phase – and clearly align them with the product functionality
  •     Explicitly confirm hardware, software, and resource availability with your project manager or IT administrator during the kickoff meeting
  •     Present a high-level demonstration of SAP Business One as part of the kickoff meeting in order to acquaint your team members with the product
  •     Discuss when and how your staff will be available
  •     Create an executive steering committee in order to tie executive management support in with the implementation
  •     Have your project manager perform a final review of the project preparation phase and sign the “Project Phase Sign-Off” document provided by the SAP implementation team

Business Blueprint

In this crucial phase, which typically takes about four days, how you would like to run SAP Business One to support your business is examined. One or more workshops for gathering your requirements are conducted during which business processes and individual functional requirements of your organization are identified and analyzed. The workshops provide the opportunity to fine-tune the original project goals and objectives as well as to revise the overall project schedule, if necessary. The result is the business blueprint, which documents in detail the results gathered during the requirements workshops. The business blueprint serves as a technical and functional guide during the subsequent phases of the implementation project.

Major Milestones

    The major milestones of the business blueprint phase are:

  •     Workshops to gather business requirements with the customer’s functional leads
  •     Creation of the detailed business blueprint document
  •     Determination of changes to initial project scope and time schedule (if applicable)
  •     Project phase review and sign-off from customer Best-Practice Recommendations The best-practice recommendations for the business blueprint phase include:
  •     Ask your implementation partner to have SAP Business One available during the workshops to allow you to see the product in action in order to evaluate how it addresses specific business requirements
  •     Suggest using your own chart of accounts instead of creating a new one, as this will significantly reduce effort for data migration and openbalance reconciliation
  •     Communicate right away if you would like to migrate the historical transaction data of your business to SAP Business One
  •     Make sure all requirements of your business are discussed and documented in the business blueprint as even seemingly small changes to initial scope or requirements can have a significant impact on the cost, resources, and timeline of the project

Project Realization

This is the most significant phase of the accelerated implementation methodology and usually takes about a week and a half. The goal of project realization is to implement all the business process and technical requirements gathered during the previous phases and documented in the business blueprint. The consultants validate and update the configuration and demonstrate processes while your project team updates the work instructions (business process procedures, for example) and performs unit and integration tests.

Major Milestones

    The major milestones of the project realization phase are:

  •     Software installation and customization based on the business blueprint
  •     Data migration (if applicable)
  •     Validation of system setup
  •     System testing
  •     Definition of training and cutover plan
  •     Project phase review and sign-off from customer

Best-Practice Recommendations

The best-practice recommendations for the project realization phase include:

  •     Minimize the number of changes to setup and scope as such changes significantly affect testing and training
  •     Communicate clearly that your project and IT teams will be responsible for ensuring data quality and integrity of data migration
  •     Ensure your project leads are present during all or large parts of system validation and acceptance testing
  •     Review all output documents – for example, invoices, purchase orders, and reports as well as financial statements – before sign-off

Final Preparation

This phase focuses on preparing both SAP Business One and the customer for going live. Key activities during this phase include completing user and administrator training as well as final fine-tuning of SAP Business One. As part of final system tests, necessary adjustments are made to resolve all remaining critical open issues. This phase usually takes about five or six days.

Major Milestones

The major milestones of the final preparation phase are:

  •     Key-user and administrator training
  •     System readiness for going live
  •     Completion of cutover activities
  •     Project phase review and sign-off from customer

Best-Practice Recommendations

The best-practice recommendations for the final preparation phase include:

  •    Officially announce to all stakeholders the training and cutover plan and the schedule
  •    Make sure each user participates in the relevant training and works directly with SAP Business  One during that training

Going Live and Support

Completing this phase is the ultimate goal and the most exciting step of the implementation project. This is when your organization goes live with the SAP Business One software and starts managing all daily activities independently. The going-live and support phase consists of two distinct subphases. First, the project is completed with a formal project closing. During this time, the software is used productively in day-to-day operations, all issues and problems are resolved, transition to the production support team is finalized, knowledge transfer is completed, and the project is signed off. Subsequently, the continuous improvement subphase begins during which the production support team monitors the software and resolves live business process issues. Proper change management procedures are established and ongoing end-user training is conducted. Plans are made to continuously review and improve business processes. The review and optimization conference is scheduled and conducted. This phase is usually completed in four days.

Major Milestones

The major milestones of the going-live and support phase are:

  •     Full production implementation of SAP Business One
  •     Project phase review and sign-off from customer for going live and support as well as for final project completion
  •     Review and optimization conference

Best-Practice Recommendations

The best-practice recommendations for the going-live and support phase include:

  •     Involve your executive steering committee in the project closing meeting for final project acceptance
  •     Schedule a review and optimization conference four to six weeks after the project closing meeting and make sure your entire project team participates
  •     Make sure your functional leads of the project: – Monitor how end users work with SAP Business One to ensure correct and consistent use of the software – Record all issues and required enhancements to performance, functionality, and usability to be discussed during the review and optimization conference
  •     Request initial on-site going-live support with at least one consultant with expertise in SAP Business One

Benefits for Customers

The accelerated implementation methodology as applied to the implementation of SAP Business One brings many benefits to SAP customers. It provides customers with a clear understanding of the scope, structure, and duration of implementing SAP Business One at the outset of the project to eliminate surprises and over runs in time or budget. In addition, the methodology brings customers peace of mind because they know the partners using the methodology will provide best-practice implementation services according to the standards set by SAP.

Copyright © Grenville Systems Development. All Rights Reserved