BENEFITS OF A SAP LANDSCAPE IN THE CLOUD

BENEFITS OF A SAP LANDSCAPE IN THE CLOUD

oXya Corporation 2011 ©

Agenda

Introduction

SAP Landscape overview

Moving into the Cloud

Benefits of moving to the cloud

Questions

Introduction

“We run SAP for you”

oXya is a market leader in SAP BC Services & SAP Outsourcing Solutions.

We help midsize and global organizations increase the efficiency and flexibility of their SAP infrastructure

and support operations.

Today, oXya provides technical services and hosting solutions for more than 148 customers across all

industries including manufacturing, retail, chemicals, administration, energy, transportation, and high-tech.

Agenda

Introduction




Questions

Cloud Computing for SAP: Cloud infrastructure

Computing Network Storage Services

VIRTUALIZATION

SAP ADAPTATIVE COMPUTING CONTROLLER

SAP INSTANCE SAP INSTANCE SAP INSTANCE

DEV

DEV

DEV

SAP ECC 6.0

SAP BI 7.0

SAP APO

SAP Landscape: instances overview

QAS PRD

QAS PRD

QAS PRD

SAP SOLUTION MANAGER 7.1

SAP SOLUTION MANAGER 7.1

SAP ECC

SAP BI

SAP APO

AS #1 AS #2

Livecache Livecache Optimizer

Livecache Livecache

DEV

DEV

DEV QAS PRD

QAS PRD

QAS PRD

DATACENTER

SAP Landscape: infrastructure overview

Agenda

Introduction




Questions

Public Cloud Available publicly Cloud Resources mutualized

for many customers

Partner Cloud Cloud services offered by a

provider Cloud resources available for a

defined number of customers

Private Cloud Cloud infrastructure accessible

for only one customer within a private network

Cloud Computing for SAP: several types of clouds

The infrastructure supporting a SAP system should provide:

Choosing a Cloud Solution: Key Evaluation Criteria

SERVICE

LEVEL

AGREEMENT

PUBLIC

CLOUD

PRIVATE

CLOUD

PARTNER

CLOUD

Choosing the right cloud: distribute the SAP systems

DEV QAS PRD

DEV QAS PRD

DEV QAS PRD

Change Management in a cloud based SAP landscape

DEV QAS PRD

DEV QAS PRD

DEV QAS PRD

Change Management in a cloud based SAP landscape

PRD DEV QAS

DEV

Development Test / QA

QAS

Production

PRD

TMS - Gatekeeper

Exceptions via QA Requirements - Paper

ChaRM is a tool delivered by Solution

Manager to Improve efficiency and

transparency of change management.

It allows organizations to control and manage

changes in complex environments and

guarantee standard process flows with :

• Workflow

• Project management

• Track categorize and monitor changes

• Transport scheduling

Change and Transport System (CTS+)

Connect Java Systems to standard CTS

Manage transport of ABAP and non-ABAP-

objects centrally

Allows combined transports for mixed

objects (ABAP, JAVA, …)

Allows synchronized changes to business

processes which run in ABAP and JAVA

Agenda

Introduction




Questions

Moving a SAP landscape to the cloud brings:


FLEXIBILITY

A SAP landscape is not a “frozen” landscape

The SAP landscape evolves constantly:

Support Packages, Enhancement Packages (EHP)

Unicode conversion, SAP Upgrade

Implementation of new components

These changes require additional SAP instances:

Sandboxes (for new components, EHP tests)

Project landscape (for Unicode conversion and SAP Upgrades)

Production copies (for a country roll out)

These additional SAP instances have a limited lifetime

Benefits of moving to the cloud: Flexibility

FLEXIBILITY

Example: Implementing new functionalities in CRM 7.0

The project team want to test new functionalities in CRM 7.0:

Implementation of EHP 1

Implementation of a Trex instance

Implementation of a Portal instance


DEV QAS PRD

SAP CRM 7.0

FLEXIBILITY



DEV QAS PRD

SAP CRM 7.0

FLEXIBILITY



DEV QAS PRD

SAP CRM 7.0

SBX

FLEXIBILITY



DEV QAS PRD

SAP CRM 7.0

SBX

EHP 1 implementation

Technical operation timing

FLEXIBILITY



DEV QAS PRD

SAP CRM 7.0

SBX Portal

TRex

FLEXIBILITY



DEV QAS PRD

SAP CRM 7.0

SBX Portal

TRex

FLEXIBILITY



DEV QAS PRD

SAP CRM 7.0

SBX Portal

TRex

TRex TRex

FLEXIBILITY



DEV QAS PRD

SAP CRM 7.0

TRex TRex

Testing and selecting the right component with cloud based sandboxes systems

Evaluating downtimes for EHP implementation

REACTIVITY

In addition to the flexibility, SAP projects require reactivity

Project teams need new environments to be quickly available

The time needed to acquire hardware in a classic non-cloud architecture is often long


REACTIVITY

Example: providing a project landscape for a SAP Upgrade (4.6C to ECC 6.0)

According to SAP’s standard Upgrade scenario, a dedicated 2 instances project

landscape is required

This project landscape will be used to create and test the corrections needed for the new SAP software version (ECC 6.0)

It will allow to create these corrections without impacting the productive landscape

The project landscape lifetime is limited: it will become useless once the upgrade project is finished


DEV QAS PRD

SAP 4.6C

REACTIVITY



DEV QAS PRD

SAP 4.6C

SAP Systems copies

REACTIVITY



DEV QAS PRD

SAP 4.6C

DEV’ QAS’

SAP Systems upgrades

REACTIVITY



DEV QAS PRD

SAP 4.6C

DEV’ QAS’ DEV’ QAS’

ECC 6.0 (project)

REACTIVITY



DEV QAS PRD

SAP 4.6C


ECC 6.0 (project)

SAP Systems upgrades

REACTIVITY



DEV QAS PRD

SAP ECC 6.0


ECC 6.0 (project)

Upgrade finished

REACTIVITY



DEV QAS PRD

SAP ECC 6.0


ECC 6.0 (project)

REACTIVITY



DEV QAS PRD

SAP ECC 6.0

The cloud architecture allows to quickly provide the SAP instances for the upgrade

project

Cloud resources for the upgrade landscape are dismissed right after the project

REACTIVITY



DEV QAS PRD

SAP ECC 6.0

If the productive landscape is part of a Cloud, additional computing resources (CPU,

Memory, Application Server) and storage can easily be added to the existing

configuration to meet the new SAP version resources requirements

Computing Storage

COST CONTROL

Pricing model based on a cost per user

Customers no longer need to deal with hardware architecture

Through the cloud, the required resources are provided to support end users activity

A cloud architecture allows a more “business oriented” costing: costs follow the business activity (more or less end users)

not the hardware needs.

Possibility to “pay per use” for a temporary resources addition

For known peak activities occurrences, additional resources for the SAP system can be provided

The hosting provider is committed to deliver the suitable infrastructure to meet SLA.

Benefits of moving to the cloud: Cost control

Example #1: Roll Out of new countries

COST CONTROL


BI

ECC 700 ECC 6.0 users

250 BI 7.0 users

150 ECC 6.0 users

50 BI 7.0 users

100 ECC 6.0 users

70 BI 7.0 users

Total users

ECC 6.0 :

BI 7.0 :

700

250

850

300

950

370


COST CONTROL


150 ECC 6.0 users

50 BI 7.0 users

100 ECC 6.0 users

70 BI 7.0 users

Total users

ECC 6.0 : 950

370 BI 7.0 :

BI


250 BI 7.0 users


COST CONTROL


150 ECC 6.0 users

50 BI 7.0 users

100 ECC 6.0 users

70 BI 7.0 users

Total users

ECC 6.0 : 950

370 BI 7.0 :

BI


250 BI 7.0 users

COST CONTROL

Example #2: additional resources


Daily consumption

Peak consumption

SAP production instance SAPS consumption

Monthly temporary high resources

consumption for FI/CO

COST CONTROL

Example #2: additional resources


Daily consumption

Extra resources

SAP production instance SAPS consumption

Agenda

Introduction




Questions

Questions

Thank You for your participation!

We will now answer your questions

Contact

Find more about us! www.oxya.com

Documents

BENEFITS OF A SAP LANDSCAPE IN THE CLOUD