28
Downtime Minimization Services SAP Consulting

SAP-Downtime-Minimization-Services-201012.pdf

Embed Size (px)

Citation preview

  • Downtime Minimization Services

    SAP Consulting

  • 2010 SAP AG. All rights reserved. / Page 2

    Agenda

    1. Introduction SAP Business Technology Factory

    2. Why Minimizing System Downtime ?

    Business Impacts and challenges

    Customer examples

    3. Service Approach of Downtime Minimization

    Use Cases

    Service Options

    4. Appendix

    Customer References

    Available Technologies

  • 2010 SAP AG. All rights reserved. / Page 3

    Fixed price and fixed scope service offerings

    offered by SAP Business Technology Factory

    Standardization / Productization

    Remote Delivery

    Guarantee / Fixed Price / One SAP

    Qualified Project Management

    An experienced SAP consultant from the SAP

    Business Technology Factory supports you

    throughout the project. He or she helps you plan

    and coordinate your technical changeover and

    functions as your main contact person for all

    project-related questions.

    Because you know in advance what our technical

    services cost, you can plan your project with

    confidence.

    The close cooperation with the SAP Product

    development ensures the overall success of the

    project and short reaction time for any problems.

    Standardized, repeatable processes, developed

    and proven through hundreds of successful

    implementations reduce risk and accelerate

    execution.

    You benefit from constant access to the wealth of

    technical experience available from SAP

    Consulting as well as from SAPs offshoreresources. Due to cost advantages of the SAP

    Factory we can offer very attractive prices to the

    market.

    SAP

    Business

    Technology

    Factory

    SAP Business Technology Factory is a strategic part of SAP Consulting to

    support you in your technical changeover.

    Experience &

    Best Practices

    When youve done something over 500 times before, you learn how to do it well.

    Thats the number of successful delivered standardized projects within

    more than three years..

    Maximum

    Planning Security

  • 2010 SAP AG. All rights reserved. / Page 4

    Business Technology Factory Service Portfolio

    Business

    Technology

    Factory

    Unicode

    Migration

    Planning &

    Implementation

    SCM Upgrade

    Planning &

    Implementation

    Enhancement

    Package

    Planning &

    Implementation

    Installation

    Services for

    Business Suite

    PI Mapping

    Planning &

    Implementation

    Downtime

    Minimization

    Services

    BI Upgrade

    Planning &

    Implementation

    ERP Upgrade

    Planning &

    Implementation

    Pure Technical

    Installation

    Test Factory

    Adobe

    Interactive

    Forms Migration

    BI Authorization

    More than 25 standardized Services are

    available, more than 500 customers did use

    the services from BTF.

  • 2010 SAP AG. All rights reserved. / Page 5

    Agenda

    1. Introduction SAP Business Technology Factory

    2. Why Minimizing System Downtime ?

    Business Impacts and challenges

    Customer examples

    3. Service Approach of Downtime Minimization

    Use Cases

    Service Options

    4. Appendix

    Customer References

    Available Technologies

  • 2010 SAP AG. All rights reserved. / Page 6

    Costs of downtime vs. cost of availability

    General Cost view on downtime

    Downtime costs are usually not linear over the

    time of system outage

    They depend on the business impact!

    For longer downtimes costs can increase

    progressively

    Example: when Order-to-Cash processes are

    stuck longer than 6h the whole production will

    be stuck and cause even higher costs

    Availability Cost Curve

    Co

    st

    95% 98% 99,5% 99,9%

    Availability

    (Source: Gartner Group)

    Costs

    Redundant components

    Disaster recovery site

    System management tools

    IT staff

    Capacity planning

    Guaranteed SLA

    Proactive services

    downtime

    Co

    sts

    Financial impact because of Downtime

  • 2010 SAP AG. All rights reserved. / Page 7

    Management of planned Business Downtimes

    Typical Customer Maintenance Schedule

    2010

    Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4

    Upgrade Netweaver based application

    Customer Release Upgrade

    Major functional System Changes

    Apply Legal Changes HCM

    Enhancement Package Installation

    Rollout project

    Data Center relocation / OS-Change

    Unicode Conversion

    Portal and PI-Update (NoN persistent)

    BI -UC

    todayLegend: Duration Downtime

    2011 2012

    Version 7

    CRMERP BI

    Version 8 Version 9 Version 10

    Minimize your planned business downtime via SAP Technologies and Service Offerings

    Scheduled outages due to maintenance events managed with minimal business impact

    Efficient downtime management and cost control tailored to your requirements

    Planned downtime with maximum security for your business

  • 2010 SAP AG. All rights reserved. / Page 8

    Business Challenge meet downtime requirements

    Requirement on continuous business availability, IT supports revenue stream

    Reduce costs for IT-Operations (Maintenance, Platform, )

    Simplify customer system landscape

    Update to date SAP release to enable further business growth

    Business / customers / partners can not be productive

    Well known financial impacts because of revenue loss or interrupted supply chain

    High effort on organization of downtime slot

    Extension of planned Downtime of a companys IT system can create high costs

    Downtime Minimization

    24 h max

  • 2010 SAP AG. All rights reserved. / Page 9

    Agenda

    1. Introduction SAP Business Technology Factory

    2. Why Minimizing System Downtime ?

    Business Impacts and challenges

    Customer examples

    3. Service Approach of Downtime Minimization

    Use Cases

    Service Options

    4. Appendix

    Customer References

    Available Technologies

  • 2010 SAP AG. All rights reserved. / Page 10

    Portfolio of Downtime Minimization Services

    Incremental Migration (IMIG)

    Near Zero Downtime approach for SAP ERP (NZDT ERP)

    Near Zero Downtime approach for SAP NetWeaver PI (NZDT PI)

    Near Zero Downtime approach for SAP NetWeaver Portal (NZDT EP)

    Incremental Conversion (ICNV)

    Combination of best practices, proven technologies, support and expert consulting

    Significant downtime reduction via online data transfer

    Planning security for your business

    Maximizing performance during downtime

    Individual Services

    Several methodologies to achieve

    different downtime requirements

    IT scope

    SAP Business Suite

    SAP

    ERP

    SAP

    CRM

    SAP

    SCM

    SAP

    SRM

    SAP

    PLM

    SAP Business Intelligence (BI)

    SAP Netweaver Process Integration (PI)

    Delivered or Pilot In Planning

    Available for SAP Business Suite and SAP

    NetWeaver components

    save downtime

    save money

    create value

  • 2010 SAP AG. All rights reserved. / Page 11

    Example for proven technology

    Near Zero Downtime approach for ERP

    Preparation

    Upgrade / Import / SLO activities

    on parallel clone system

    De

    lta re

    pla

    y

    RecordingPRDR/3 4.71

    hostA

    clo

    ne

    downtime

    La

    st D

    elta

    rep

    lay

    Fin

    al-V

    alid

    atio

    n

    Infra

    stru

    ctu

    re

    Ch

    an

    ge

    Clone

    R/3 4.71

    hostB

    PRD

    ECC 6.00

    hostB

    Migration

    Workbench

    Re-Sync Clone with

    Prod-System

    Clone becomes

    new Prod System

  • 2010 SAP AG. All rights reserved. / Page 12

    Text

    Upgrade

    SLO

    Conversion

    Enhancement

    Packages

    Support

    Packages

    System

    Consolidation

    Datacenter

    Relocation

    DB/OS

    Migration

    Unicode

    Conversion

    Downtime Minimization Services

    Combine what YOU want

  • 2010 SAP AG. All rights reserved. / Page 13

    Downtime Minimization Service Portfolio Uses Cases to optimize downtime

    Individual Service

    Use Case

    ERPIMIG

    BI SCM ERPNZDT

    CRM ERPICNV

    PI EP

    Upgrade

    Unicode Conversion

    alone or in combination with Upgrade

    Enhancement Packages

    SLO (e.g. Currency Conv.)

    System Consolidation

    Support Packages

    Datacenter Relocation

    OS/DB Migration

    Downtime < 24h < 24h < 12h < 8h < 8h < 8h < 1h < 1h

  • 2010 SAP AG. All rights reserved. / Page 14

    Typical Use Cases

    Upgrade or Unicode Conversion or combination of both

    OS/DB Migration

    Price depends on complexity (e.g. downtime

    threshold, DB size, use case etc.)

    approx. 150.000 up to 300.000 over 300.000

    Typical Use Case

    EHP Installation together with Customer Transport

    Wave

    Functional reorganizations

    Price depends on number of events

    Model 1: BUILD Service for a huge single

    maintenance event

    Model 2: BUILD Service for the execution of

    a maintenance calendar

    Performance oriented pricing models

    S M L

    Number of executionsP

    rice

    pe

    r e

    xe

    cu

    tio

    n

    Event 1 e.g. Upgrade

    Event 2 e.g. Layout Change

    Event 3 e.g. EhP

    The pricing model could based on a performance related pricing scheme related to the

    contracted and achieved downtime

    The downtime threshold become part of the contract.

    The actual achieved downtime defines the final service fee.

    Optional for

    both models

  • 2010 SAP AG. All rights reserved. / Page 15

    2-Day Onsite Workshop

    Identify Customers requirements

    System Landscape

    Relevance for maintenance events

    Required System Downtime

    Plan Implementation project

    Choose the methodology which has

    the best fit to customers requirements

    Identify the relevant maintenance

    events

    High Level Business Case

    Formal Quotation and Pricing

    Execute the proposed individual service

    Full Service model with a general project

    duration of 4-5 months (single maintenance

    events)

    Downtime Minimization for SAP ERP

    Downtime Minimization for SAP CRM

    Downtime Minimization for SAP SCM

    Downtime Minimization for SAP

    NetWeaver BI

    Enablement model

    Downtime Minimization for SAP

    NetWeaver PI

    Downtime Minimization for SAP

    NetWeaver Portal

    Downtime Minimization PLAN Service Downtime Minimization BUILD Service

    Two-step approach to reduce downtime and

    create value

  • 2010 SAP AG. All rights reserved. / Page 16

    Fact Sheet

    Downtime Minimization Planning

    Requirements

    Service Description

    Customer Benefit

    Price / Price Model

    Prerequisites

    MDS-Questionnaire to make preliminary feasibility check

    Rough estimates on downtime requirements and project timeline

    Information about possible dependencies of other projects or initiatives

    Project Leads, infrastructure reprehensive and Basis team members required

    Get familiar with MDS Technologies

    Make right technology decisions

    Be prepared for future strategically upgrade & implementation project decisions

    SAP Expert onsite, to get latest information, best practices and experience

    It is recommended to start early the Planning Service

    (several weeks before MDS Delivery phase starts)

    Explanation of the possible technologies and the

    MDS-Service approach

    Discuss and mitigate risks (workload, restricted

    transports, etc.)

    Check dependencies to other projects or work

    streams Unicode (scans, vocabulary , reprocess)

    Hardware requirements for each phase

    6.000 fixed price excl. travel cost

    Approach / Content Deliverables

    Fix timeline and project plan aligned with the

    customer

    Define the approach, roles and assignment of

    resources

    Requirements for all project parties are defined

    Definition of customer involvement (e.g. basis

    activities like backups)

    Understanding of main downtime blocks and relevant

    actions to reduce them

    Fill out Questionnaire Form

    PLAN BUILD

  • 2010 SAP AG. All rights reserved. / Page 17

    Fact Sheet

    Downtime Minimization Implementation

    Requirements

    Service Description

    Customer Benefit

    Price / Price Model

    Prerequisites

    Remote access possibilities to involved systems (VPN access or WTS-Connections)

    Hardware for specific phase (Additional Server, SAN), depending on the used technology

    Customer Basis Consultant

    Guaranteed Downtime for business critical applications

    Minimal business disruption

    Proven methodology, developed by SAP Labs

    Other SAP services (e.g. Unicode Conversion or Upgrades) might be integrated

    Minimized Downtime will be executed and

    guaranteed

    Several involved technologies like Incremental

    Migration or Near Zero Downtime according to

    chosen and appropriate use case

    Depends on Complexity (Use Case, Downtime Threshold, Database Size, etc.)

    Approach / Content Deliverables

    Project Management

    Project Plan

    Cutover Plan

    Technical Concept

    Planning Service

    PLAN BUILD

  • 2010 SAP AG. All rights reserved. / Page 18

    Maturity of service portfolio will focus on SAP

    component applicability and customer usability

    Stage 1Focus on selected

    Use Cases

    Incremental Migration

    Methodology

    Logging 90% of

    database volume in

    uptime

    Copy rest in downtime

    Use Cases:

    Unicode Conversion

    OS/DB Migration

    Stage 2Focus on use case

    applicability

    Stage 3aFocus on SAP

    component applicability

    Stage 3bFocus on

    standardization and productization

    Up 2006 2007 2009 2011+

    Near Zero Downtime

    Methodology (NZDT)

    Create Clone of PROD

    and execute

    Maintenance on Clone

    Parallel logging of all

    DB changes

    Clone becomes new

    PROD after data reply

    Applicable for :

    SAP ERP

    all maintenance use

    cases

    Classic

    Methodologies

    T

    Optimize Customer

    usability and price

    model

    Deliver projects in

    Factory mode (Full

    Service Model)

    Introduce full

    Service model for

    regular maintenance

    events

    Introduce Customer

    Enablement model

    Ach

    ieva

    ble

    Do

    wn

    tim

    e

    Use NZDT for SAP

    Business Suite and

    SAP Netweaver

    Applicable for

    SAP ERP

    SAP CRM

    SAP BI

    SAP SCM

    SAP PI

    SAP Enterprise

    Portal

    .

  • Appendix References

  • 2010 SAP AG. All rights reserved. / Page 20

    Success Story P&G

  • 2010 SAP AG. All rights reserved. / Page 21

    VALUE DELIVERED! Company in Consumer Industry

    Customer DetailsWorlds leading nutrition, health, wellness company

    280,000 employees worldwide

    Sales of110 Bio USD in 2008

    160,000 SAP users

    ERP Upgrade with minimal business

    disruption

    Customer Value and Benefit

    Customer upgraded their ERP systems from SAP R/3 Enterprise 4.7 to SAP ERP 6.0

    and EHP 3 including 20,000 customer transports

    Elements of the global core solution were upgraded to the next version, to ensure

    opportunities for future functions and integration accelerated access to innovation

    SAP Services reduced the technical downtime during the upgrade from five days to two

    hours; in total the system had a business downtime of only 20 hours which is a

    significant improvement compared to former upgrade methods.

    Contribution of SAP

    Expert knowledge and guidance in the upgrade project and great confidence in the

    promised results; major system upgrade performed with the least achievable risk

    Unique SAP service offering providing a minimal disruption to the running critical

    business during the upgrade strongly improved business continuity

    Modernization of the existing ERP solution through the upgrade to the state-of-the-art

    version of the SAP software

    Collaboration

    Excellent alignment between the customer development and operations teams and

    SAP execution and development teams around the World: Europe, America, Australia,

    Walldorf

    Project management team as a crucial success factor great collaboration of customer, partner and SAP

    Project Scope and Timeline

    Technical Upgrade of ERP systems

    3 regions (Europe, America, Asia) with a

    split architecture

    Systems size between 8 to 25TB

    System landscape includes many SAP

    components, e.g. ERP, SCM, CRM, EP

    Project Duration 9 months

    SAP Teams

    Consulting

    Active Global Support

    System Landscape Optimization

    SAP NetWeaver Development

    The NZDT approach was instrumental in ensuring a risk mitigated upgrade consuming as little downtime as possible. Achieving this milestone without any major production issue in these early days is the direct result of a great team effort between the entire

    organization and our partners especially SAP.

    Vice-President - Head of Business Technology Centre

  • 2010 SAP AG. All rights reserved. / Page 22

    Customer References

    Customers who met the 24 hours threshold

    system downtime with SAP Downtime Minimization Service

    Upgrade, Unicode

    Conversion

    and Datacenter

    relocation

    Datacenter relocation Unicode Conversion

    Unicode Conversion Unicode Conversion

    Datacenter

    relocation

    Platform Migration Platform Migration

    Upgrade and Unicode

    Upgrade and Unicode NZDT Upgrade

    Unicode

    conversion

  • Appendix Methodologies

  • 2010 SAP AG. All rights reserved. / Page 24

    Downtime Minimization for ERP

    Incremental Migration Technology (IMIG)

    Unicode conversion and Postprocessing of big tables in uptime (e.g. TOP 100 tables)

    Unicode conversion of other tables in downtime

    Synchronization of the changes between the main system and target system

    Delta

    rep

    lay

    R3 lo

    ad

    TO

    P 1

    00

    Ta

    ble

    s

    UC

    Po

    stp

    rocessin

    g

    TO

    P 1

    00 T

    ab

    les

    RecordingTOP 100 tables

    PRD

    non Unicode

    hostA

    downtime

    Unicode Preprocessing

    Last D

    elta

    rep

    lay

    UC

    Po

    stp

    roc

    es

    sin

    g

    Ins

    tall S

    AP

    Kern

    el

    Tra

    ns

    po

    rt of U

    C

    Ad

    jus

    tmen

    ts

    Fin

    al-V

    alid

    atio

    n

    Infra

    stru

    ctu

    re

    ad

    just. -

    inte

    rfaces

    R3

    loa

    do

    ther T

    ab

    les

    Unicode Downtime I Delta TransferInfra

    structure

    PRD

    Unicode

    PRD

    Unicode

    hostB

    Validation

    Install DB

    Unicode

    Downtime II

    System

    Setup

  • 2010 SAP AG. All rights reserved. / Page 25

    Downtime Minimization for ERP

    Near Zero Downtime Technology

    Consistent system copy (clone) with the logging of database changes

    Normal Upgrade / Unicode conversion

    Synchronization of the changes between the main system and the copy delta replay

    Transports, Pre-Validation while Uptime

    Delta

    rep

    lay

    Recording

    PRD

    R/3 4.6C nUC

    hostA

    clo

    ne

    downtime

    Prepare + Upgrade Uptime

    Upgrade

    and Unicode conversion

    + Transports

    + Add Ons

    + Pre-Testing

    Last D

    elta

    rep

    lay

    Fin

    al-V

    alid

    atio

    n

    Infra

    stru

    ctu

    re

    ad

    just. -

    inte

    rfaces

    Upgrade + UC Downtime Post ProcessingDelta

    Transfer

    Infra

    structure

    PRD

    R/3 4.6C nUC

    hostB

    PRD

    ECC 6.00 UC

    hostB

    hostA

    Vali

    dation

    MWB

  • 2010 SAP AG. All rights reserved. / Page 26

    Downtime Minimization for ERP

    Incremental Conversion (ICNV)

    SAP

  • 2010 SAP AG. All rights reserved. / Page 27

    Normal production No restrictions

    Downtime Minimization for PI

    Mirror update with back copy

    Customer System Mirror System

    Copied Customer System

    Clone productive systemexcept PI processing data

    SP n

    SP n+m

    SP n

    SP n

    SP n+m

    Normal production No restrictions

    Business Only Mode Only allow PI

    processing(all scenarios)

    No non-PI changeoperations

    No config changes/design time changes

    Standard update Apply SP on mirror

    system PI processing data

    is not affected

    System down Stop production Switch shadow tables

    Back copy Copy back DB tables

    not containing PIprocessing data

    Use shadow tablesas copy target

    Copy back DBexcept PI processing data

    t

  • 2010 SAP AG. All rights reserved. / Page 28

    record

    changes

    Downtime Minimization for NetWeaver Portal

    Mirror update with switch over

    Customer System Mirror System

    Copied Customer System

    Clone productive system

    SP n

    SP n+m

    Switch to mirror system

    SP n

    SP n

    SP n+m

    Normal production No restrictions

    Record changes Applications can run

    in record mode or in read only mode

    Standard update Apply SP on mirror

    system

    System down Switch to mirror

    system, log off users Stop production

    Normal production Users log on to new

    system No restrictions

    Change

    Recorder

    transfer

    changes

    Transfer changes Transfer recorded

    changes and adaptto target SP level

    t