1. Agenda SAP BW Project Experiences Key Success Factors
SAP BW Implementation Methodology
Using ASAP for SAP BW implementation

2. Understanding SAP BW implementations
Internal BW & CRM systems
Customer, project and Installation data
Analyze SAP BW projects
Project profiles (sample out of 115 live customers)
profiles
Discuss projects with customers, consultants, implementation partners, ASUG Participants, FCS program participants
Identify and assess key areas
Project Focus, Scope, Length, Team
Identify and share best practice
Working with Universities, SAP Labs
Implementation Analysis Projects
ROI, TCO studies
Methodology & Site Visits
Questionnaires (sample size: 35 live customers)

3. Worldwide BW Installations (June 2000)

4. Extracted Data 1st Going Live*
All SAP modules + non R/3 data
non R/3
80%
70% SD
60%
50%
40% MM
CO-CCA
CO-PA
30%
FI-AP
Others
20%
EC-PCA
FI-GL
FI-AR
FI-SL
CO-OPA
10% HR
CO-PC
CO-OM QM PP 0%
* Data from 50 live customers in November 1999)

5. Project Averages Project Team Effort Sap Consultants 1 Customer Team 4
Non SAP Consult. 2
Project Team 7
Effort
Impl. Time 4 months
First live users 45 users
Targeted Users users
live Cubes (Target end of ’99) 4.5(12)
Queries (Target end of ‘99) 35 (80)

6. Project Team and Implementation Time
Project teams increase
Implementation times decrease

7. Implementation Effort
Customer: Implementation Team
Implementation Time
Consultants:

8. Reasons for Business Information Warehouse
Flexible business analysis and reporting
R/3 extractors
Business know-how is built in
Data management tools
Single-point-of-entry
Single-point-of-administration
Leverage of R/3 knowledge
Relief of R/3-System and of IT-Organisation
Open for 3rd parties
Loading of external data
Trennung von Datenbank, Applikation und Frontend auf separaten Servern (1)
Durch eigenständiges Warehouse-System wird das OLTP entlastet, da die performanceintensiven Reporting-Aktivitäten nicht mehr im OLTP selbst, sondern im BW und seinen eigenen Servern abläuft. Weiterhin wird die IT-Organisaton entlastet, da sie nur noch ein Warehouse-System verwalten muß. (2, 9)
Die Reports können auf die Anforderungen der verschiedenen Benutzer bzw. Benutzergruppen abgestimmt und definiert werden. Dabei ist man nicht auf den Excel-basierten Analyzer des BW gebunden, sondern kann über die OLE DB for OLAP-Schnittstelle auch Third-Party-Tools anbinden, sofern die zugehörige Schnittstelle zertifiziert ist. (3, 4)
Das von der SAP im R/3 gesammelte Wissen hinsichtlich der Geschäftsprozesse ist in das BW integriert worden. Bei anbindung des BW an die R/3-Welt werden die im R73 vorhandenen Strukturen und Objekte adaptiert, so daß deren doppelte Pflege entfällt, was eine erhebliche Arbeitserleichterung darstellt. (5, 10)
Das BW ermöglicht das Laden und Weiterverarbeiten von Daten aus Sourcesystemen jeglicher Art, d.h. die Informationen könne aus R/3-, Non-R/3-OLTP-Systemen oder aber aus File-Systemen geladen und zur Weiterverarbeitung zur Verfügung gestellt werden.
Der Endanwender hat innerhalb eines Systems Zugriff auf alle unternehmensrelevante Informationen.

9. BW Implementation: Motivation & Goals
Business motivation for implementing SAP BW
43 % Advanced Reporting & Analysis
28 % Consolidation of information
15 % Improve OLTP Performance
10 % mySAP.com Applications
4 % other
Overall goals of BW projects
36 % Standard Reporting
32 % Enterprise-wide Repository
27% Decision Support
1% Data Mining
4% other
Performance
Reporting/
Analysis
Consolidation
Enterprise-
wide
Repository
Decision
Support
Standard
Reporting
n=37

10. Methodological Experience
Implementation Partners
SAP 30%
Other 30%
None 40%
Used Implementation Method
ASAP 50%
Other 25%
Unknown 25%
SAP
None
Other
ASAP Other Unknown

11. Business Requirements
Requirements Analysis
Customer 45%
SAP Consultants 40%
Management Consultants 10%
Other 5%
Information gathering techniques
Interviews/Business 40%
Workshop 37%
Interviews/IT 23%
Customer
SAP
Workshop
Interview/
Business
Interview/ IT

12. Business Content Acceptance
Business Content Use
Yes %
No %
How well could you use the Business Content? (1 = very well)
Yes No
AVG
2,2

13. ASAP for BW Toolkit Tools & Accelerators
Documentation Enhancements 44%
Online Accelerators 41%
Reporting made Easy Guidebooks 8%
ASAP CD %
None %
Accelerators
Docu
Guidebooks CD
None

14. Typical SAP BW project Prototype/ Pilot 1st Live Implementation
time
Prototype/ Pilot
1st Live Implementation
Strategy
SAP BW Roll out
Enterprise-wide Implementation

15. A Typical SAP BW Project Lifecycle...
Continuous Business Information Reengineering
Implementation Cycle 3
Implementation Cycle 2
Roll-Out
...
Prototyping
Implementation Cycle 1 5 4
Planning & Strategy: Concept for Rollout
and Further Planning 1 2 3
Pilot
Implementation
Evaluation &
Feasibility
Go Live
& Support

16. Agenda SAP BW Project Experiences Key Success Factors
SAP BW Implementation Methodology
Using ASAP for SAP BW implementation

17. Key Success Factors Findings
Prepare information engineering in your organization
SAP BW is more than a SAP module
Use the power of SAP BW for your enterprise
90-day rule
Finish within 90 days and demonstrate!
Use Business Content
Consider the business processes
Understand the process - understand the data
Define scope and stay with scope
Discuss and nail down real user requirements
Implement in cycles

18. Key Success Factors Findings
You need project skills
Committed management, good core SAP BW team in-house!
Manage expectations and communicate
Let the projects be reviewed by SAP BW experts
You need business skills
Involve the business (end user) from day one!
You need BW skills
technical skills

19. Primary Factors Impacting BW Project Length
In General, a BW Project Will Be of Shorter Duration and Will More Likely Be Successful if:
The Project Uses Delivered Business Content
Minor Modifications in R/3
The BW Team is Skilled and committed
The Team Consists of End Users that Understand the Business Process and their Data
There is a Clear, Valuable Objective of the Project
Executive Level Support is Strong
The R/3 Environment is Stable
The Technical Support Team is Strong (Data Modeling and Basis)
The Organization has a Long-Term, Strategic Commitment to SAP

20. Agenda SAP BW Project Experiences Key Success Factors
SAP BW Implementation Methodology
Using ASAP for SAP BW implementation

21. Why use a the specific SAP BW Implementation method?
Pre-configured Business Content
SAP BW is not just a Data Warehouse…
It requires a specific methodology to benefit from Business Content
SAP BW uses a very specific data model
SAP BW speaks “business language”
Early Success is possible
Iterative Approach – Implement in cycles
SAP recommends a three layer model (see next foil)
1st layer: BW Strategic Planning
2nd layer: BW implementation
3rd layer: BW Project Mgmt.
Project plans, Skill descriptions, Tools and Accelerators available online
on -> Service&Support/BW ASAP
BW ASAP Implementation Assistant can be used as a project management tool

22. Iterative BW Implementations

23. BW Strategy PROJECT PREPARATION Project Management Kick-Off
STRATEGY BLUEPRINT
First Analysis of situation and preparation for Workshops
Executive Workshops (Requirements & Commitment)
Scope of implementation
PROGRAM DEFINITION
Further Analyses Sessions
Information Model: Global structures: Information Requirements & Info Supply Chain
SAP BW System Landscape
Implementation Approach
Communication Strategy
Program Management Approach & Risk Assessment
PROGRAM CHARTER
Timetable of BW projects
Staffing of Coordination Teams
Requirements for Implementation Teams

24. Phase 1: Project Preparation
INITIAL PROJECT PLANNING
Project start up session
Project charter
Team working environment
Project organization (roles)
Implementation strategy
Project plan
PROJECT PROCEDURES
Management standards
Implementation standards
System configuration
Post-Implementation service and support strategy
System problem standards and error handling
System enhancement and modification approval process
Naming standards
Data administration
ESTABLISH SYSTEM LANDSCAPE STRATEGY
TRAINING PROJECT PLANNING
Project team training plan
End user training & documentation strategy
PROJECT KICKOFF
TECHNICAL REQUIREMENTS PLANNING
Identify requirements
Procure initial hardware (optional)
BW REVIEW - PROJECT PREPARATION PHASE

25. Phase 2: Business Blueprint
TRAINING
Conduct project team training
Prototype end user deliverables
BUSINESS REQUIREMENTS ANALYSIS
Requirements workshops
Assess current data warehouse and information access environments
BUSINESS CONTENT CHECK
Assess requirements
SAP & non-SAP sources
Master data
Data Access
Identify data requirements for each end user category
BW DESIGN
Data design
Data access design (BEX and Non-SAP)
Authorization design
System landscape strategy
Technical design
Procure technical components for Dev/QA/Prod (optional)
ESTABLISH DEVELOPMENT ENVIRONMENT
Prototype
DEFINE SYSTEM ADMINISTRATION
BW REVIEW - BUSINESS BLUEPRINT PHASE

26. Phase 3: Realization DEVELOPMENT CONFIGURATION
Configure development environment
Configure data access environment (BEX & Non-SAP)
Implement & validate authorization concept (Dev)
Test BW environment
DEVELOPMENT CONFIGURATION WORKSHOPS
Prototyping solutions
TRAINING
Define/develop/finalize end user training & documentation
TEST PLANS
Define system test plans
Define data test plans
Define data access test plans
Define authorizations test plan
DEFINE SYSTEM PROCEDURES
Service level commitment
BW administration procedures
BW REVIEW – REALIZATION PHASE

27. Phase 4: Final Preparation
TUNING
Mass Tests
Database Tuning
BW Tuning
TRAINING
Conduct pre-go-live end user training
SYSTEM MANAGEMENT
Establish production system administration
Conduct system tests
DETAILED PROJECT PLANNING
Refine cutover
Refine production support plan
CUTOVER
Cutover
Final approval for going live
BW REVIEW - FINAL PREPARATION PHASE

28. Phase 5: Go Live and Support
PRODUCTION SUPPORT
Go live Checks
Support review
Provide production support
Validate live business process results
Conduct post-go-live end user training
STRATEGIC BW PLANNING
PROJECT END

29. Proposed BW Implementation Approach
Cycle1: 1-3 Months
Rapid Implementation
Option 1: Add Externally Purchased Data
Delivered InfoSources
Delivered InfoCube
Delivered Queries
Limited Number of Users
Stable Technical Environment
Option 2: Extend Standard InfoCube or
In contrast to other data warehouse solutions BW offers the BW Business Content. The BW Content makes it possible to go life in a short period of time. If BW is connected to an R/3 OLTP, the BW Content includes the data extraction, staging and reporting.
In the first stage of a data warehouse project you should pick a limited subject area and use exclusively the BW content (extraction, infoobjects, sources and cubes) that are delivered with the standard BW and go for a life start in a period of only 4-8 weeks. The advantage of this approach is to feed back very fast to the report owners and work from the experiences gained in this short time frame.
In the next stages you can add to the BW content info cubes, either bring in external data, legacy data or extend the infocubes. The time periods of the subsequent projects can differ in intensity and duration.
Option 3 : Integrate Legacy Data or
3-6 Months

30. SAP BW specific Skills (Roles)
Five BW specific roles have been identified for a successful implementation
BW Data Extraction
BW Data Access (Frontend, Web)
BW Data Architect, Administrator
BW Application
BW Basis
BW Project Team member can have one or more roles

31. Business Information Warehouse Project Roles
BW Data Extraction
Responsible for identifying and obtaining the data required to satisfy the requirements of the BW project.
SAP R/3 Data
New Dimension Product Data
Data external to SAP within the organization (legacy data)
Data external to SAP from outside the organization (provider data - D&B, Nielson)

32. Business Information Warehouse Project Roles
BW Data Access
Responsible for assessing the business requirements, and designing and developing a data access solution for the BW project.
BW’s Business Explorer
Certified ODBO clients: Non-SAP data access tools
Visual Basic development
Web development
Consumer
70%
Analyst
20 %
Author
10%

33. Business Information Warehouse Project Roles
SAP BW Data Architect
Responsible for the overall design of the BW project
BW InfoCubes
Logical models
BW process models
BW enterprise models
Responsible for Administration

34. Business Information Warehouse Project Roles
BW Application
Responsible for utilizing BW to satisfy the business requirements identified for the project
If the scope of the BW project is tightly controlled and can use standard BW Business Content, InfoCubes, and Queries, the BW Application Consultant may assume the responsibility to perform several roles concurrently to include

35. Business Information Warehouse Project Roles
BW Basis
Responsible for the the BW infrastructure and Tuning
BW Installation and Basis Parameters, Patches, Support Packages
BW Landscape, Correction and Transportation Settings
BW Sizing
BW Performance & Tuning
BW Authorizations

36. Project Organisation Project Mgmt. Information owner (business users)
Info Owners
Information owner (business users)
Data
Architecture
& Adminis-
tration
Team
Frontend
Team
Steering
Commitee
Project
Mgmt.
Data
Extraction
Team
Executive
Sposors
BW Basis
Team
Parallel work is possible in a BW project.
Contacts: source systems

37. AcceleratedSAP Accelerators
Examples of Accelerators
Project Plan
Workshop Agenda
Questionnaires
End User Procedures
Technical Procedures
Made Easy guide Books
Written by experienced SAP BW consultants
Fill in the Blank
versus
Start from Scratch 8

38. The SAP BW 2.0B Accelerators
Phase 1 Project Preparation
BW Methodology Overview
Project Start Up (Workshop Template)
Roles & Skills in SAP BW Projects
Project Charter for SAP BW Projects
Project Plan
Phase 2 Business Blueprint
Business Blueprint Methodology (Information Requirements Analysis)
Multidimensional Data Modeling with SAP BW
Templates Business Blueprint
Sizing Tool
SAP BW Hardware Sizing
SAP BW System Lanscape & Transport
Authorizations in SAP BW
Documentation Templates for SAP BW Authorizations
ODS-Whitepaper
Phase 3 Realization
BW Excel Features
Issue log database (QADB)
Frequently asked questions
Hierarchies in BW
Phase 4 Final Preparation
SAP BW Performance / Tuning
Phase 5 Going Live
BW Operational Support
BW Strategy Phase
BW Strategy (Global Rollout)
BW SEM
BW APO

39. SAP BW Documentation Enhancements
…several enhancements to the Online Documentation
…will be incorporated in Online Documentation of next release
Can be found on the SAP Service Marketplace ( background/Documentation Enhancements)

40. BW Project Reviews should occur Periodically Throughout a BW Project
Project Preparation
Final Preparation
Realization
Go Live & Support
Business Blueprint
Continuous Improvement
Project Start Up
Performance Review
In Final Preparation
End of phase 1
Conceptual Review
Configuration Review
During cycle configuration
Design Review
After Data Design

41. BW Project Reviews Independent and objective reviews by BW experts
Scheduled visits with agenda and timetable
One or two days on site
Interviews with project team, management and end users
Study project documentation
Present findings and recommended solutions to management
Plan them into your budget and timelines

42. Obtaining an SAP BW Review
How can you order the Reviews?
At your local SAP subsidiaries
Order by for Europe:
Order by for US:
service.sap.com/BW->Service&Support/Project Review

43. SAP BW information in the SAP Service Marketplace
service.sap.com/BW

44. Agenda SAP BW Project Experiences Key Success Factors
SAP BW Implementation Methodology
Using ASAP for SAP BW implementation

45. ASAP : Comprehensive Solution
Roadmap
Step-by-step project plan and explanations of tasks and activities
Foundation of project plans (Microsoft project)
Tools and accelerators
Attached to the roadmap
For project estimation and to set expectations (scope, time, resources)
For project management: method/roadmap, spreadsheets, documentation templates
For the BW consultant and customer: questionnaires,check lists, tools
Implementation Assistant
Project Management Tool: combines project management with SAP BW specific accelerators and how-to’s. 6

46. AcceleratedSAP Tools Approach: offline
The Implementation Assistant is the primary tool and framework in ASAP
Welcome to AcceleratedSAP
Version
Project Preparation
Business Blueprint
Realization
Final
Preparation
Go Live & Support
Continuous
Change
What’s New
Roadmap
Implementation Accelerators
Project Plan
Question and Answer Database
Issues Database
Business Process Procedures
Knowledge Corner
Glossary
Help
Contents
Search
Back
Hide
Forward
Refresh
Print
Options
Home Page
The Implementation Assistant is:
A PC tool that can run completely independently of the BW System
The one-stop collection of all tools and methods developed for the ASAP methodology
Network- capable
Implementation Assistant contains
Roadmap, QADB, Knowledge Corner

47. ASAP Roadmap Phase Work Packages Activities Accelerators Tasks
The ASAP Roadmap, regardless of the method of access, is divided into four types of organizational folders:
Phase - The major organizational steps of the ASAP Roadmap.
Work package - A group of activities designed to accomplish a major portion of a Roadmap phase. A work package is assigned to a project team for completion.
Activity - A group of tasks. The results of an activity can produce certain deliverables and can be accomplished by one or more project team members. Several activities comprise a work package.
Task - A specific event to be performed by a project team member. Tasks contain the important How To instructions needed for task completion and provide access to the accelerators:
- How-To - Explanation of how to perform a process, activity , or task.
- Accelerator - Documents, templates, tips and tricks used to accelerate task completion.
Tasks

48. Phase 5: Go Live and Support
ASAP Knowledge Corner
What’s New
Roadmap
Phase 1: Project Preparation
Phase 2: Business Blueprint
Phase 3: Realization
Phase 4: Final Preparation
Phase 5: Go Live and Support
Implementation Accelerators
Project Plan
Knowledge Corner
Glossary
Contents
Search
Home Page
Help
Sizing Estimators
BW Prototyping
BW Presentations
Best Practice Examples
The Knowledge Corner will contain a number of Consulting Guides written by consultants
The Knowledge Corner contains many consulting guides.

49. BW on ASAP CD
CD includes implementation roadmaps for all mySAP.com applications
You can choose mySAP.com application BW as a flavor when installing ASAPactivities -> create a BW specific roadmap
Allows to choose more than one flavor
The methodology will be provided to trained BW Consultants. They can use AcceleratedBW to plan and discuss with customers

50. ASAP for SAP BW Rollout Strategy
ASAP for SAP BW is included on ASAP 4.6b
Last Release: December 1999
Next Release: online August/ offline: December 2000
Online
Accelerators, Documentation Enhancements
August 2000
service.sap.com/BW ->Service&Support/BW ASAP
ASAP CD
Implementation Assistant, Roadmap, Accelerators, Documentation enhancements

51. Copyright 2000 SAP AG (All rights reserved)
Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.
Microsoft®, WINDOWS®, NT®, EXCEL®, Word® and SQL-Server® are registered trademarks of Microsoft Corporation.
IBM®, DB2®, OS/2®, DB2/6000®, Parallel Sysplex®, MVS/ESA®, RS/6000®, AIX®, S/390®, AS/400®, OS/390®, and OS/400® are registered trademarks of IBM Corporation.
OSF/Motif® is a registered trademark of Open Software Foundation.
ORACLE® is a registered trademark of ORACLE Corporation, California, USA.
INFORMIX®-OnLine for SAP is a registered trademark of Informix Software Incorporated.
UNIX®, X/Open®, OSF/1®, and Motif® are registered trademarks of The Open Group.
ADABAS® is a registered trademark of Software AG.
SAP, SAP-Logo, mySAP.com, R/2, R/3, RIVA, ABAP, SAP-EDI, SAP Business Workflow, SAP EarlyWatch, SAP ArchiveLink, ALE/WEB, BAPI, SAPPHIRE, Management Cockpit, SEM, are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other products mentioned are trademarks or registered trademarks of their respective companies.