Overview

This Roadmap is intended for SAP cloud solutions that do not have solution specific roadmaps. The purpose is to guide the
implementation team through the cloud implementation. It is comprised of Phases, Deliverable and Tasks in accordance with the SAP Activate
methodology. In addition, accelerators are linked to the relevant deliverables and tasks making them easy to consume when they are needed.

The Deliverables and Tasks are listed in sequential order based on the activity start. However, parallelization is necessary to expedite the
implementation.

The Roadmap covers the implementation of the cloud solution. Projects that include integrations to other cloud solutions may alter the
procedures.

Please Note: This roadmap is a general roadmap that can be used in various cloud implementations. Solution specific roadmaps are
available for SAP S/4HANA Cloud as well as SuccessFactors.

 Please login to access additional content. (Top left drop-down)

 The accelerator overview is available using the Accelerators link above.

 Always check for Solution Specific roadmaps prior to using this general cloud version.

Favorite (0)

Phases
Clear All

Discover(8)

Prepare(48)

Explore(67)

Realize(65)

Deploy(18)
 

Run(4)

Workstreams

Application: Solution Adoption(4)

Application: Customer Team Enablement(0)

Application: Design & Configuration(0)

Technical Architecture & Infrastructure(0)

Analytics(0)
 

Application: Integration(0)

Custom Code Extensions(0)

Project Management(0)

System & Data Migration(0)

Application: Testing(0)

Transition to Operations(0)

Services
 

Build Design Support(0)

Analytics Design Support(0)

Platform Execution(0)
1. Discover

The purpose of the Discover phase is for the customer to understand the breath, depth and functionality of SAP Cloud solution and learn about
the benefits it can bring to customers’ business.

Key Discover activities are:

 Stakeholder identification

 Value Discovery using a trial system

  Scoping, or Discovery, assessment

At the end of this phase the customer and the sales team come to a jointly agreed description of the implementation scope, overall project
timelines and target solution model.

Link to Content
2. Prepare

The purpose of this phase is to provide the initial planning and preparation for the project. In this phase, the project is started, plans are finalized,
project team is assigned, and work is under way to start the project optimally.
Link to Content
3. Explore

The purpose of this phase is to perform a fit/gap analysis to validate the solution functionality included in the project scope and to confirm that the
business requirements can be satisfied. Identified gaps and configuration values are added to the backlog for use in the next phase.

Link to Content
4. Realize
The purpose of this phase is to use a series of iterations to incrementally build and test an integrated business and system environment that is
based on the business scenarios and process requirements identified in the previous phase. During this phase, data is loaded, adoption activities
occur, and operations are planned.

Realize Activities:

 Establish the solution landscape

 Implement the solution in the development environment using incremental build in time-boxed iterations
  Conduct overall end-to-end testing of the solution within the QA environment

 Setup production environment

 Prepare for data migration and data archiving

 Conduct performance testing

 Conduct project team and key user training

 Finalize end user training materials and documentation

 Track and report on value delivery

During Realize phase, the project team uses a series of iterations to incrementally configure, test, confirm, and document the entire end-to-end
solution and to create legacy data conversion programs. The project team actively works with business representatives to ensure good fit of the
built solution to the requirements from the backlog. Project Team releases results of multiple iterations to the business users to accelerate time to
value and provide early access to finalized functionality. Each release is thoroughly tested in end-to-end integration test and user acceptance
test.

The project team documents the configuration decisions and solution in the SAP Solution Manager tool. They also document all development –
including interfaces, integration points, data conversion programs, reports, and any required enhancements – in SAP Solution Manager. Once
these activities are complete for particular release and the team has obtained business approval, they make the release available in the
production environment.

Link to Content
5. Deploy

The purpose of this phase is to setup the production system, confirm customer organization readiness, and to switch business operations to the
new system.
Deploy Activities:

 Finalize the solution and its supporting tools and processes for production go-live

 Resolve all crucial open issues

- Conduct system tests

 - Check that system management is in place
- Proceed with cut-over activities, including data migration

 Execute transition and cutover plans including organizational change management (OCM) plans

 Complete all scheduled end user training

 Identify and document all issues encountered in the transition to the new solution

 Monitor business process results and the production environment

 Establish OCC** or a "extra-care" center of excellence for support that provides:

- Production support processes

- Exceptional business monitoring processes
- Extraordinary technical support
- System enhancements

 Track and report on value delivery

Link to Content
6. Run

The purpose of this phase is to further optimize and automate the operability of the solution. Operability is the ability to maintain IT systems in a
functioning and operating condition, guaranteeing systems availability and required performance levels to support the execution of the
enterprise’s business operations.