Sap Project Plan Template by wzx45739


More Info
									SAP Rollout Project

           Iskustva u vođenju globalnog projekta

           Opatija, June 4, 2002

                          Mirko Slovjak
Project Approach
   As a global company, we have a critical mission to
    undertake: we must successfully meet the rising
    challenges and complexities of business world.
   To get there, we need an integrated system that delivers
    the right blend of functionality, flexibility and
   Moreover , we need a comprehensive solution that
    optimises and supports all of our global business
   To achieve this goal we need:
     • a reliable strategy to analyse our business
       operations and new opportunities and
     • an integrated information system
Project approach
Case studies show that most of the successful SAP implementations are
business-driven from start to end
Differences between IT-driven and business-driven SAP implementations

    IT-driven implementations                            Business-driven implementations
                                                         • Reengineering of business
 • Replacement of old IT systems                           processes in alignment with
   that are difficult to maintain and                      corporate strategy
   support                               Rationale for   • SAP regarded as an enabler to
 • Increase accuracy of data              using SAP        change the way the business is
 • SAP regarded as an IT solution
   to all business problems                              • IT structure and business
                                                           processes are aligned

                                                         • CEO
 • CIO
                                         Key decision    • Senior management, including
 • IT department
                                         makers during     IT manager
 • Today’s IT users define system       implementation
                                                         • Requirements based on future
   requirements and architecture
                                                           business needs

 Successful companies realise from the start the importance of business-driven SAP
 implementation and secure that the business focus is never lost throughout the process.
  Project approach
         Complexity drivers for multi-site, multi-national SAP implementations

                                                              Complexity drivers
                                     • Global business issues
                                        – Global data standards
                                        – Global/standardised processes
                                        – Global products
Multi-site, multi-national
 SAP implementations
                                     • Geography and cultural issues
                                        –   Cultural differences between international sites
                                        –   Communication challenges and local acceptance (buy-in)

                                     • International team structure and project organisation
                                        – Internationally balanced teams
                                        – Distributed support over regions
                                        – Coordination of rollouts in multiple countries

                                     • Diversity within regional IT systems in use
                                        – More complex configuration management
                                        – Variations in regional IT infrastructures
                                        – Difficult definition process for standardisation through multiple

 The complexity increases significantly for global SAP implementations - putting many potential
 pitfalls and risks on the map to project success.
Project approach
   Characteristics of Global ASAP methodology
    Project complexity
                                                                        Global ASAP

                                                   • Provides Global Strategy definition before starting
                                                     implementation project
                                                   • Approach driven by global business process
                                                   • Opportunity to integrate business reengineering
                                                     and value chain improvements
                     ASAP                          • Opportunity to align business processes across
                                                     international borders and realisation of significant
                                                     cost reductions and enterprise-wide benefits
       • Clear local focus of SAP
         implementation                            • Opportunity for SAP programs across all enterprise
                                                     sites, product lines and international divisions
       • Process optimisation on local
         level                                     • Ideally fit for big multi-national enterprises to
                                                     prepare for the challenges of global markets
       • Benefits on local level
       • No business process
                                                                                              Size of company

Global ASAP is especially designed to fit the needs of multi-site, multi-national enterprises and to
help them implement global business operations, based on SAP.
Global ASAP
   Global ASAP methodology will not substitute experience and
   necessary skills, such as:

      • Business acumen

      • Project management

      • Business process know-how

      • SAP know-how

      • IT architecture know-how
Global ASAP

              Roll Out ASAP Roadmap
Global ASAP

  1                  2                     3                       4
Project Set-up   Business Blueprint    Realisation    Maintenance & Support

  Where we          How to get          processes
  want to go          there            into logical
                                          of R/3
       Global ASAP Phases

                                              Global                                    Global
                    Global Project                                 Global
                                             Business                                 Maintenance
                       Set-Up                                    Realisation
                                             Blueprint                                and Support

             • Define global         • Prepare template   • Configure and      • Support local sites,
               strategy              • Define global        confirm template     subsidiaries
             • Set up global           business process   • Define global      • Perform post-rollout
               template project        models               system               activities
                                     • Develop global       management         • Ensure continuous
                                       Business           • Perform final        improvements

                                       Blueprint            integration test
                                                          • Execute rollout

                                                  Project Management

                    Change Management (Training, communication, team building, motivation, and so on)

                                                   Quality Assurance
Project Set-up activities

                         Define                 Prepare project
                         global                                               Set up global
                                               (template/rollout            template project
                        strategy                   strategy)

             • Opportunity and        • Detailed project           • Global template project
               readiness assessment     planning                     charter
             • Strategy Study         • Project procedures         • Project scope
                                        and standards
             • Risk Assessment                                     • Project plan
                                      • CCC implementation
             • Business Case                                       • Project team

             • Review and sign-off    • Sign-off of high-level     • Template-specific
               of Global Strategy       project plan                 standards and
                                                                   • Review and sign-off
                                                                     of Project Charter
     Strategy Study
             Key deliverables of Strategy Study
                                                            Global Strategy for
                       Enterprise Scope                                                     Implementation Approach
                                                           System Architecture
                • Scope of sites, countries            • IT-system topology              • Implementation approach
                • Scope of processes                   • Network overview                • Outline of configuration strategy
                • Information and process flows        • Instances: number, locations,     (how, where, configuration
                  between enterprises                    relationship, and so on           access, and so on)

                • Graphical representations of         • Analyses of distributed         • Outline of development strategy
Content                                                                                    (how, where, development
                  each organisation and mapping          application alternatives
                  to SAP organisational hierarchy                                          access, and so on)

                • Listing of all high-level                                              • Overview of rollout strategy
                  functional gaps and potential                                          • Outline of CCC concept
                • Policy statement on how gaps
                  are to be resolved

                                        Project Management
                                                                                    Change Management
                                   • Overview on overall Project              • High-level Change
Project                              Management Approach                        Management Strategy
governance                             –   Organisation structure             • High-level training strategy
                                       –   Roles & Resposibilities
Business Expectation
   Enabling better PLIVA position
   To build an Integrated IS on group level
   To improve communication between PLIVA’s
   Real time and standardise reporting system
   To standardise and optimise business
   To increase level of efficiency
   To improve customer service
   Perform C&V activities according the Project
Project Benefits
   Cross application
    • Accuracy of data
    • Cross company data availability
    • Elimination of double work processes
   Finance & Controlling
    • Accurate Cash Management
    • Group credit limits monitoring
    • Shortened period of reporting
   Sales & Distribution
    • Increased inventory turnover
    • Reduction of Customer complaints
    • Better stock controlling and sales forecasting
Project Benefits
   Product Supply
    • Increased inventory turnover
    • Reduced planning cycles
    • Reduction of cycle time
    • Shortened order availability check

   Quality Assurance
    • Decreased GMP deficiencies
    • Standardisation of QA data, documents and
Project Assumption
   Key team members must be full-time on the project
   Scope must be controlled
   Where possible existing solution in PLIVA Zagreb will
    be sought
   Business change will be driven by SAP
   Complexity must be kept low
   Identification of master data must conform to global
   Team members are empowered to make decisions
   Core team will work closely with Country teams
   Organisational structure will be frozen
   Standard reporting will be utilised where possible
   Top management involvement and quick decisions
    making process
Project Organisation
Implementation Approach
   The term ”rollout project” refers to the process of
    repeated activation of one or more templates.

   The main effort during the Business Blueprint phase
    will be develop global template
   It’s possible that some business processes will be
    optimised during the project, due to better practice
    either in PLIVA Krakow or PLIVA Lachema

   One of the areas in which there can be no SAP
    standard is the motivation for collaboration between
    local and global levels
Implementation Approach


                Documentation     Country          Local
                                  Versions         developments

                                 Master Data
              IMG structures                       Local
              and settings                         processes

             Global                              Global and
            Developments                         integrated
Implementation Approach

   Global – A process is global when it is integrated
    throughout the enterprise

   Standard – A process is standardised if it must be
    executed in the same way in the enterprise

   Local – A process is local if it is not possible or it
    makes no sense to define as global or standardised
Timeline Impacts

                           Availibility of
                       resources to support       Number of sites and
                       the Project activities    business units involved

      Degree of readiness                                        Complexity of extended
  (preparation status, previous                                     requirements
      internal experience)           Duration of the
                                      SAP Roll-out
                 Existing SAP
                 installations                                Geographical scope
               (SAP know-how)
                                      Functional scope of

To top