Copyright © 2003 Americas’ SAP Users’ Group Tips for planning and completing a successful SEM implementation Paul Halley Director, SEM Consulting Business.

Slides:



Advertisements
Similar presentations
ERP Applications Selection in a Changing Marketplace Evaluation of Software Providers for Midsize Institutions Bill Reed Director, Special Projects Northern.
Advertisements

Business Information Warehouse Business Information Warehouse.
Chapter 8: Evaluating Alternatives for Requirements, Environment, and Implementation.
Planning for Enterprise Systems
Chapter 10 Schedule Your Schedule. Copyright 2004 by Pearson Education, Inc. Identifying And Scheduling Tasks The schedule from the Software Development.
Migration MIGR-02. David Cervelli Managing Consultant Strategic Systems Group (SSG) June 2007 Preparing for an Implementation.
Copyright © 2003 Americas’ SAP Users’ Group SAP EC-CS / BCS vs. Hyperion Marty Krist Manager, Corporate Systems Team W. R. Grace & Co.
Enterprise Web Content Management Path to developing a Competency Center Presented To: Presented By: Gilbane ConferenceBrian VanDeventer IT Manager, Web.
Creating & Maintaining an Effective SAP CCC (On A Budget!)
Modern Systems Analysis and Design Third Edition Chapter 11 Selecting the Best Alternative Design Strategy 11.1.
University of Southern California Enterprise Wide Information Systems Instructor: Richard W. Vawter.
Accelerated Access to BW Al Weedman Idea Integration.
Copyright © 2003 Americas’ SAP Users’ Group How to Implement Supplier Performance Management Using BW, SEM, and SRM Paul Halley Director, SEM Consulting.
BPS Group SAP Consulting Services
Information Technology Challenges in ERP - Duke University 1 IT Challenges in ERP Chris Meyer Duke University.
1 Components of A Successful Data Warehouse Chris Wheaton, Co-Founder, Client Advocate.
Sitefinity Performance and Architecture
Privileged and Confidential Strategic Approach to Asset Management Presented to October Urban Water Council Regional Seminar.
Software Evolution Planning CIS 376 Bruce R. Maxim UM-Dearborn.
Change Management. Why change management  For many change practitioners, there is no doubt that change management must be used on projects that impact.
Greater Profits and Business Value
GLOCO Enterprise Measurement System Team 4 John Armstrong Ananthkumar Balasubramanian Emily James Lucas Suh May 5, 2012.
Solution Overview for NIPDEC- CDAP July 15, 2005.
1 Building and Maintaining Information Systems. 2 Opening Case: Yahoo! Store Allows small businesses to create their own online store – No programming.
© VESP International Pty Limited To Contents Slide CLICK to advance slides/ bullet points within slides Integrated Master Planner An Overview.
Moving into Design SYSTEMS ANALYSIS AND DESIGN, 6 TH EDITION DENNIS, WIXOM, AND ROTH © 2015 JOHN WILEY & SONS. ALL RIGHTS RESERVED. 1 Roberta M. Roth.
Best Practices: Aligning Process, Culture and Tools Michael Jordan Senior Project Manager - Microsoft Consulting Services
1 ISA&D7‏/8‏/ ISA&D7‏/8‏/2013 Systems Development Life Cycle Phases and Activities in the SDLC Variations of the SDLC models.
GBA IT Project Management Final Project - Establishment of a Project Management Management Office 10 July, 2003.
MyITgroup.com, Ltd. ©2002 All Rights Reserved. Contains Confidential and Proprietary Information of MyITgroup and may not be disclosed to any third party.
Creator: ACSession No: 16 Slide No: 1Reviewer: SS CSE300Advanced Software EngineeringFebruary 2006 (Software Quality) Configuration Management CSE300 Advanced.
© 2006 Cisco Systems, Inc. All rights reserved.Cisco Public 1 Version 4.0 Gathering Network Requirements Designing and Supporting Computer Networks – Chapter.
1 ETM 5121 Project Proposal Determination of How to Handle Contract Craftsmen Employees in the SAP Plant Maintenance Module of ABC, Inc.’s Illinois Refinery.
Bjarne Berg and Ben Perego March 20 th, 2006 Decision Support - What is new? An overview presentation University of North Carolina at Charlotte.
SAP Decision Support Environments in Higher Education
Accounting Information System By Rizwan Waheed M.Com 710.
Microsoft Office Project 2003: Selling EPM in your Organization Matt Wilson Business Solutions Specialist LMR Solutions.
Planning with Use Cases Extracts from the Lamri Use Case Survival Guide™ Mark Aked Managing Consultant For more information visit or .
Washington State Office of Insurance Commissioner State Insurance Management & Business Application Project Recap November 2007.
Copyright © The OWASP Foundation Permission is granted to copy, distribute and/or modify this document under the terms of the OWASP License. The OWASP.
Special Topics in Vendor- Specific Systems EHR Go-Live Strategies This material (Comp14_Unit8) was developed by Columbia University, funded by the Department.
Rational Unified Process (RUP) Process Meta-model Inception Phase These notes adopted and slightly modified from “RUP Made Easy”, provided by the IBM Academic.
BSBPMG501A Manage Project Integrative Processes Manage Project Integrative Processes Project Integration Processes – Part 1 Diploma of Project Management.
SYSTEMS DEVELOPMENT IN PERSPECTIVE
Page 1 JUSTIFY define and validate REQUIRE- MENTS define initial management DOCUMENTS define INFRA- STRUCTURE allocated maintenance changes management.
Installation and Maintenance of Health IT Systems Unit 8b Troubleshooting; Maintenance and Upgrades; and Interaction with Vendors, Developers, and Users.
Copyright 2002 Prentice-Hall, Inc. Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 11 Selecting.
CS223: Software Engineering Lecture 16: The Agile Methodology.
RUP RATIONAL UNIFIED PROCESS Behnam Akbari 06 Oct
ISIS Project Status Report May 18, 2006 Prepared by MAXIMUS, Inc Education Systems Division for the ABT Committee.
1 Data Warehouse Assessments What, Why, and How Noah Subrin Technical Lead SRA International April 24, 2010.
Plan for Application Consolidation. Successful application consolidation relies on assessment of the application portfolio to determine the best candidates.
Accounting systems design & evaluation 9434SB 18 March 2002.
IS&T Project Reviews September 9, Project Review Overview Facilitative approach that actively engages a number of key project staff and senior IS&T.
Office 365 What Is The Right Fit For You? Andrew Riley, MCTS, MCTIP, ITIL v3.
P U B L I C S E R V I C E S State of South Carolina Enterprise Information System Business Case Study SCEIS User Group Briefing Wednesday July 10, 2002.
Pragmatics 4 Hours.
The Marshall University Experience with Implementing Project Server 2003 August 9, 2005 Presented by: Chuck Elliott, M.S. Associate Director, Customer.
BANKING INFORMATION SYSTEMS
Enterprise Resource Planning Systems
Driving Digital Business with SAP Digital Business Services
Systems analysis and design, 6th edition Dennis, wixom, and roth
Software Testing and Maintenance Maintenance and Evolution Overview
C.U.SHAH COLLEGE OF ENG. & TECH.
Systems analysis and design, 6th edition Dennis, wixom, and roth
System Review – The Forgotten Implementation Step
Chapter 11 Selecting the Best Alternative Design Strategy
SDLC (Software Development Life Cycle)
Chapter 11 Selecting the Best Alternative Design Strategy
Modern Systems Analysis and Design Third Edition
Presentation transcript:

Copyright © 2003 Americas’ SAP Users’ Group Tips for planning and completing a successful SEM implementation Paul Halley Director, SEM Consulting Business Information Solutions (BIS)

What We’ll Cover  SEM architecture & landscape options  Determining how to choose the best SEM implementation strategy for your organization  Staffing  Twelve practical tips for planning your future SEM implementation  Performance implications

The Architecture of SEM Extraction Retraction OLAP SAP BW Reporting SAP BW SAP SEM Non-SAP Systems

Landscape: Single or Multiple Servers? Option 1) SEM Data MartOption 2) SEM Application on BW SEM- BPS SEM- BIC SEM- BCS SEM- CPM SEM- SRM SAP BW OLAP engine External SEM sources SEM- BPS SEM- BIC SEM- BCS SEM- CPM SEM- SRM External SEM sources Third party OLTP SEM System BW Data Warehouse System SEM Application BW Data Warehouse System

Pros/Cons of Single or Multiple Servers  Option 1 - SEM Data Mart Pro - Allows main BW system to be upgraded at different schedule than SEM system. Helpful if business and IT do not often work harmoniously. Con – Performance is decreased slightly due to RFC between two BW systems Con – Extra servers are required (3 if using 3-tier landscape)  Option 2 - SEM Application on BW Pro – Less maintenance on basis side due to three fewer BW servers to maintain. Pro – Three fewer BW servers to purchase than Option 1 Con – Version dependency between BW and SEM requires users of Option 2 to upgrade BW and SEM at same time (no exceptions!)

What We’ll Cover  SEM architecture & landscape options  Determining how to choose the best SEM implementation strategy for your organization  Staffing  Twelve practical tips for planning your future SEM implementation  Performance implications

In What Order Should You Implement?  Why You Should Care  An SEM implementation can sometimes involve considerable BW configuration. Choose the wrong implementation order and you’ll either spend too much or not enough time on the BW “side” of an SEM implementation. Spend too much time:  SEM project will be delayed  BW development costs can spiral Spend too little time:  BW rework increases, SEM project delayed  Choose the right implementation order and you’ll find the right balance between implementing quickly and minimizing BW rework.

In What Order Should You Implement?  BW then SEM  Pros – Less rework once SEM project begins, standards have already been established, understanding of BW design is critical to SEM performance  Cons – SEM implementation is delayed, possible rework as SEM needs are unknown at this point, usually have technical BW staff implementing functional SEM  SEM then BW  Pros – SEM implemented fastest, excitement generated by SEM draws out more BW requirements  Cons – Highest amount of BW rework, as strategic BW design hasn’t been developed yet  Concurrent  Pros – Least amount of rework as BW design and SEM needs are developed at same time, functional staff work on SEM, technical BW staff work on BW  Cons – Slightly slower implementation time as strategic BW design is being determined during project

Decision Matrix BW First SEM First Concurrent SEM Critical to Operations (Cost Center Planning, Budget Prep, etc.) XX SEM Replacing Existing Tools in Satisfactory Condition X Many different data sources for SEM X Most data will be input via SEM-BPS X Critical for SEM to be live ASAP X SEM-BCS Implementation X Only use for SEM is Balanced Scorecard X BW to be Main Reporting Tool, Unsure of SEM’s Use XX

What We’ll Cover  SEM architecture & landscape options  Determining how to choose the best SEM implementation strategy for your organization  Staffing  Twelve practical tips for planning your future SEM implementation  Performance implications

Project Staffing  While SEM is technically a BW add-on, it is its own application. Furthermore, it is a business application, not a technical data warehousing application. Therefore, BW team members should be different from SEM team members. They should be different people with different skills (functional vs. technical)!  Resources in a typical first SEM project  40% Business users  20% IT (technical BW)  40% Consulting  Resources in a typical follow-on SEM project  70% Business power users  20% IT (technical BW)  10% Consulting (for support with new functionality)

What We’ll Cover  SEM architecture & landscape options  Determining how to choose the best SEM implementation strategy for your organization  Staffing  Twelve practical tips for planning your future SEM implementation  Performance implications

SEM Overall  Tip 1: Find out if you own SEM software (SEM is included in mySAP licenses). If you don’t own it, you’ll need to purchase a BW and SEM license (or one mySAP license) for each user.  Tip 2: Define end-user group.  Options: Small end user rollout Pilot projects Big bang  Recommendation: Consider a pilot project (for non- SEM-BCS projects). They have proven to be a successful option to rolling out SEM. Recommend one organizational unit/business unit with limited targets, limited users  Tip 3: If using consultants, use SEM consultants for SEM, BW consultants for BW. Interview them well, as configuring SEM infocubes is not the same as implementing SEM!

SEM-BPS  Tip 4: Decide well in advance on what will be planned/budgeted (document and be as specific as possible). SEM-BPS is a completely flexible and customizable set of tools…many implementations are delayed because scope plans aren’t specific enough.  Tip 4.5: Minimize Fox code and user exits as much as possible, as they are a maintenance headache!  Tip 5: Consider delivered planning applications (sales planning, financial planning, headcount planning, etc.). Are great examples of integrated planning that can be achieved via BPS. And if usable by you, they can speed up implementation.  Tip 6: Decide whether your existing planning/budgeting processes are to be left as-is or improved. During a software implementation is a good time to introduce new business processes, but doing so will slow down the implementation while “to be” processes are determined.

SEM-SM  Tip 7: Find out how closely your existing Balanced Scorecards fit the Kaplan/Norton model. The SAP BSC was built for this model, but slight variations can be accommodated. If you need new Scorecard content, you’ll want to start working on it before the SEM project begins.  Tip 8: If you already have BSC content, for your first BSC project I recommend choosing a business unit or highest level of organization and building less than 10 BSCs (preferably 3-5) for senior and executive management

SEM-PM & SEM-BCS  Tip 9: I recommend implementing MC via pilot project or phased rollout. User acceptance is terrific, so prepare to be bombarded with requests after the pilot’s go-live.  Tip 10: For Value Driver Trees, I recommend limiting your project to less than 20. The KPIs should be strategic in nature. If they’re not, you can be overrun by requests to build VDTs for all KPIs within your organization.  Tip 11: Decide what version of software to implement (BCS- R/3 based or BCS-BW based?) Your decision should take into account the timing of the start of your project. Implementing soon? Recommend BCS-R/3 based. Implementing late 2003+? Recommend BCS-BW.

What We’ll Cover  SEM architecture & landscape options  Determining how to choose the best SEM implementation strategy for your organization  Staffing  Eleven practical tips for planning your future SEM implementation  Performance implications

SEM- BPS  Performance considerations critical when you use BPS.  Be critical of use of Excel macros in planning layout  ABAP vs. Fox coding can operate up to 26 times faster!  Application design highly correlates with performance  See notes: (overview), , , ,

SEM- SM/PM  Highly correlated to performance of BW  Queries and calculations behind scorecards and cockpits determine performance of SM/PM.  Caching available since SEM 3.0b

7 Key Points to Take Home!  Limit scope for first project  You need function skills for SEM, technical for BW  An SEM-BPS project is a great opportunity to improve existing planning/budgeting processes  SEM performance = BW performance  SEM is quite possibly the only SAP application your executives will ever use  Building SEM infocubes does not equal implementing SEM  SEM is your best salesperson for increasing BW throughout your organization