1 / 45

What We’ll Cover …

SAP Business Intelligence (BI) The Latest Tools, Technologies, and Benefits Penny Silvia & Dr. Bjarne Berg MyITgroup & Comerit Inc. What We’ll Cover …. “Selling” across your organization – what is your Business Case? Understanding your Technology Needs – what you REALLY need!

ann
Download Presentation

What We’ll Cover …

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. SAP Business Intelligence (BI) The Latest Tools, Technologies, and BenefitsPenny Silvia & Dr. Bjarne BergMyITgroup & Comerit Inc.

  2. What We’ll Cover … • “Selling” across your organization – what is your Business Case? • Understanding your Technology Needs – what you REALLY need! • Preparing for the Implementation – and the Future • Learn from our Experiences – good and bad! 2

  3. What We’ll Cover … • “Selling” across your organization – what is your Business Case? • Understanding your Technology Needs – what you REALLY need! • Preparing for the Implementation – and the Future • Learn from our Experiences – good and bad! 3

  4. What is the Business Case to upgrade SAP BI? • This is not a cut and dry answer … We’ve seen different answers for different customers – and for different business units. • The justification must be aligned with concrete business benefits • The best way to write it is to align it with one of these areas: • Money • Strategy • Reducing time & • effort of delivery Hint!! successful business cases are written around this Enterprise reasons Improved user functionality and speed for end users IT reasons 4

  5. Ex: Enterprise Benefits of SAP BI that Mgmt will support Area Area Observation Observation SAP BI BW Benefit Benefit Cost of Ownership Cost of Ownership Maintaining a custom developed SAP is responsible for Substantial maintenance cost savings BI solution is complex and maintenance of the expensive. product. Cost Avoidance Cost Avoidance BW – R/3 integration points are maintained and tested by SAP Substantial cost savings, by Enables retirement of legacy DW. Updating extract programs to not having to redevelop new custom DW when upgrading R/3 extract programs for each is expensive. SAP upgrade Web strategy Web strategy Web delivery requires rapid data SAP BI is closely integrated Enables web initiatives to get delivery of high consistency with with SAP Portal and can closer to the source data, the source system. deliver data that reflects both in time and consistency with simplified security setup. The source system at short time intervals. Reconciliation Effort Reconciliation Effort A substantial portion of the data BW is “ closer ” to the Users spend less time on warehouse effort is spent on source system, and more reconciling data, and more reconciling information accurately reflects data time analyzing it. Information Access Information Access Business users need a high Load times in BI are Users get earlier access to Availability solution less than traditional, information custom- developed data warehouses 5

  6. Example Enterprise Benefits of SAP BI (cont.) 6

  7. Example Enterprise Benefits of SAP BI (cont.) 7

  8. What are Businesses (aka: Users!) using to drive the upgrade? FUNCTIONALITY! FUNCTIONALITY! FUNCTIONALITY! • Business units are seeing huge gains in usability, as well as features & functions in SAP BI 7.0 • Business units are seeing opportunity for improving the solutions they have in SAP BW today – and making them more user friendly • What specific features? • Cockpits, Printing, Real-Time, BI Accelerator, Formatted Reports, Integrated Planning, Ad Hoc Queries But is this enough to justify an upgrade?

  9. What is IT using to drive the desire to upgrade? What is being pushed by IT departments as justification for upgrading? • TECHNOLOGY! TECHNOLOGY! TECHNOLOGY! • IT departments are seeing significant potential savings in TCO, maintenance, development time, support and more • More empowerment for end users = less requirements to IT • More flexibility and ability to change with the organization = less cost to make changes and more willingness TO make changes • Advanced features and capabilities = opportunities to sunset non-SAP BI solutions, tools and add-ons But is this enough to justify an upgrade? 9

  10. What’s the Right Answer? • The “right” answer is the one that is going to resonate within YOUR organization – and get you the funds that you need for the upgrade! • Some ideas: • Cost avoidance: Cost of developing BSPs is high and will have to be redone later.. • Unicode conversions are easier when system is small • Benefit of Java based development tools are great and users like the drag and drop better.. • Tool access (i.e. may not need Crystal, when you have report writer), broadcasting to printers, PDF, better bursting… • Better ETL interface, more content, cockpit tools …. 10

  11. Be Careful… • If you’re going to go with an IT and cost-savings approach to justify your upgrade … • Make sure all the technology works the way you expect it to before committing an ROI to it • Make sure you have a full understanding of the total cost of the solution (specifically BI Accelerator) and the benefits you will receive before committing an ROI to it • Look at the systems you propose to de-commission and confirm that SAP BI will deliver an acceptable alternative – and that the business will not “block” your plans for de-commissioning 11

  12. What We’ll Cover … • “Selling” across your organization – what is your Business Case? • Understanding your Technology Needs – what you REALLY need! • Preparing for the Implementation – and the Future • Learn from our Experiences – good and bad! 12

  13. What are your technology requirements for 2004s? • MANY of the tools and features of 2004s require the SAP Enterprise Portal tool • All Web-based tools • Report Designer • New BEx Web Application Designer (Unicode, Command Wizard, ...) • Exporting to PDF and Printing • BI Integrated Planning • “Drag & Drop” (Analysis Web Item) • Document Integration with Storage in Knowledge Management These may well be the tools that you are using to position the upgrade to your users – or for your business case … so what does that mean to your overall efforts and cost? 13

  14. Another common question: “When Will You Install AS-Java/Portal/BI-Java?” • BEx Web and BI Integrated Planning require Usage Types BI-Java, EP, and AS-Java as technical foundations • All 7.0 BEx front-end tools require BI-Java, EP, and AS-Java as technical foundations • BEx Analyzer • BEx Web Application Designer • BEx Analyzer • BEx Report Designer • BEx Query Designer • Therefore, the question becomes not if but when • With a “technical upgrade” project approach, Portal/Java/BI-Java are delayed until medium- or long-term phases Remember – you CAN continue to use the 3.X interface – and functionality – without the Portal / Java – until you are ready to install. The “cost” … you won’t get to use all the cool new functionality of 7.0 until you install Portal / Java 14

  15. What does this mean for your overall Portal strategy? You have choices … • Consolidated BI/enterprise portal • One portal, two uses (BI portal and enterprise portal) • Might require you to upgrade the Portal • Support Package synchronization between BI and the Portal • Standalone BI and enterprise portal systems • Several Portals if one Portal is for BI only and one “corporate” Portal • Several Portals could be integrated by Federated Portal Network • No Support Package synchronization between BI and “enterprise” portal • Multiple production BI systems drive architecture towards a distributed portal strategy 15

  16. Heads Up! Restriction with SAP NetWeaver 7.0 New technical architecture ... each SAP NetWeaver 7.0 Portal can connect to one and only one BI system • There can only be a 1:1 relationship between an SAP NetWeaver BI 7.0 instance and a Portal 7.0 instance • Either an existing SAP portal must be used for BI query runtime, or a new portal must be dedicated to support the BI query (BEx) runtime (running together with an existing portal) • Multiple production BI systems drives a more complex portal landscape (because of the 1:1 relationship) 16

  17. Federated Portal Strategy – Considerations • The consumer portal can integrate complete portal roles of a producer portal • You currently cannot combine roles from several producer portals • Use Remote URL iViews instead to create portal roles with content from several producer portals • Information Broadcasting is possible within one producer portal • Documents will be created within Knowledge Management (KM) of the producer portal • KM does not support Federated Portal Networks directly • Broadcasting between different producer portals is not possible • Several options are available to make documents created by Information Broadcasting visible: • Remote KM Navigation iView (recommended if no combined storage is required) • CM Repository Manager (recommended if combined storage is required) See http://service.sap.com/nw-fpn * and SAP Note 969040 for details * Requires login credentials to the SAP Service Marketplace 17

  18. What We’ll Cover … • “Selling” across your organization – what is your Business Case? • Understanding your Technology Needs – what you REALLY need! • Preparing for the Implementation – and the Future • Learn from our Experiences – good and bad! 18

  19. Decision #1 – What Is Your Technical Upgrade Path? • There are different upgrade paths which depend on your current version and the applications and scenarios used on your source version • Scenario 1: • SAP BW 3.5 w/ABAP only or BW 3.1C, 3.0B, 2.1C, or 2.0B Source: SAP 19

  20. More Upgrade Paths … Scenario 2: • BW 3.5 w/ABAP with BI Java Components on AS Java Source: SAP 20

  21. A Different View … Source: SAP 21

  22. Decision #2 – Technical or Functional Upgrade? • Quite honestly, it really all boils down to this question. Are you going to ONLY do a technical upgrade (and not release any new functionality) or are you going to do a technical AND functional upgrade and immediately roll-out the new capabilities of SAP NetWeaver BI 7.0? 22

  23. Our General Recommendation: Technical Upgrade First Most organizations (at least the ones we are dealing with) are opting for a technical upgrade – with functionality releases in phases in the future • This is the least risky approach, but it does lead to user expectation management • This also minimizes transition activities associated with objects that don’t convert automatically • This also minimizes risks against “undocumented features” But as an organization you have to make this decision for yourself … based on your requirements, business case and “tolerance for risk” 23

  24. How can you weigh the choices of Technical or Functional? 24

  25. Weighing Towards a Technical Upgrade • A technical upgrade is the “safest” way to proceed • It is also the fastest and the least expensive • Your user community will notice little to no change UNTIL you start rolling out the new functionality 25

  26. Weighing Towards a Functional Upgrade • A functional upgrade (which includes all the technical activities) will make the biggest impression on your user community • This will take longer – and cost more money • You will be able to sunset other solutions sooner • You will get the most benefits – from usability and management 26

  27. Three Key Considerations 27

  28. Additional Consideration: Resources and Technical Support 28

  29. What You’ll Need Resources For …. • BASIS • Critical that you have the technical resources who are familiar with installing SAP NetWeaver BI 7.0 and integrating all of the components (SAP Solution Manager, SAP NetWeaver Portal, etc.) • SAP NetWeaver Portal administration • Required for use of vast majority of new presentation functions – printing, report designer, all Web functions, Visual Composer • Experienced SAP NetWeaver BI 7.0 support • This is a MAJOR release – you don’t want someone “learning on your dime” • Your regular BI support/maintenance organization • Must familiarize themselves with the new tools 29

  30. What You’ll Need Resources For … (cont.) • You will also need support from the following groups: • Security and Authorizations • Convert to new authorizations objects • BI Web Specialists • Convert BI 3.x web templates to new formats • Business Analysts/Representatives • For testing 30

  31. Typical Training Requirements 31

  32. What We’ll Cover … • “Selling” across your organization – what is your Business Case? • Understanding your Technology Needs – what you REALLY need! • Preparing for the Implementation – and the Future • Learn from our Experiences – good and bad! 32

  33. A 2008 Real example Step -1: Hardware install and BWS Copy BWX BWD BWQ BWP In this real example, we are also installing new Hardware. This gives us lot of flexibility… 3 1 2 4 BWS BWX BWX BWX 33

  34. Step -1: BWS Unicode conversion, Java upgrade & test At this stage you should document and test all work that occurs. Some time has to be set aside for notes research and unforeseen issues. We want to creating a repeatable process, so no ad-hoc activities are allowed. BWX BWD BWQ BWP 3 1 2 4 BWS BWX BWX BWX

  35. Step -2: System copies BWX BWX BWX BWP You now freeze the development and can take copies of the BWD and BWQ system and prepare for upgrades. The old BWP is still running as the productive system.. 3 1 2 4 BWS BWD BWQ BWX 35

  36. Step -3: BWD upgrade We now repeat the process. Remember, you have already upgraded BWD once and should know the need for any post processing. Don't ignore the need for technical and functional testing. BWX BWX BWX BWP 3 1 2 4 BWS BWD BWQ BWX

  37. Step -4: The real test -- BWQ upgrade BWX BWX BWX BWP Notice, we refreshed the new BWQ from BWP, so this is really a BWP upgrade… Go/no-go decision on April 17th!! 3 1 2 4 BWS BWD BWQ BWX

  38. Step -5: The Big One: Cut-Over weekend…. BWX BWX BWX BWX Contingencies should be made. I.e. notice that is any showstoppers occur on 20th, the old BWP can be renamed back, or if the time becomes too short the Unicode can be done the next weekend. 3 1 2 4 BWS BWD BWQ BWP

  39. Top Challenges Cited by BI Upgrade Teams • What is actually REQUIRED from a technical perspective? • “How much” SAP NetWeaver Portal is necessary? • What do we do if we have another portal tool as our corporate portal? • How do I manage the user expectations – they hear about all this great functionality and they want to use it NOW – with the need to balance what we rollout? • How can I create an environment in which SOME people can use the new functionality and some people can’t? • There is so much … where do I start? 39

  40. Experiences of BI Upgrade Pioneers • The EARLY, EARLY pioneers (the people who did this during ramp-up) ran into some frustration • But the good news is that you get to learn from all their frustrations and deal with a product that is much more stable and dependable! • Others who have the system live already are finding … • Higher user acceptance of the system as they roll out new functionality • BI Accelerator can dramatically improve the performance of queries – but make sure you use it against the RIGHT queries (as we’ve already talked about) This might be the time for a complete re-install vs. an upgrade – and build all the “old” BW stuff over in the new solution 40

  41. Reminder: Be Careful How You Sell This Internally If you promote the functionality then you are committed to a functional upgrade – which is a BIG effort Managing user expectations is very important here There has been a LOT of marketing on the new features, many of which users (especially those coming from other BI tools) feel should have been there a long time ago If you are not rolling out all functionality right away, you are going to have to manage expectations and offer alternatives 41

  42. Reminder: Don’t Try to Go-It-Alone • Get support from the most experienced resources (internal and external) that you can find – and afford • There is so much going on in this upgrade – and so many new integration points – you will really want as much “been there, done that” as you can get 42

  43. Reminder: SAP NetWeaver Portal is a “Must-Have” If you don’t install SAP NetWeaver Portal you don’t get all the “good” functionality E.g., Printing, Formatted Reports, Ad Hoc Queries, etc. Many companies are struggling with this point as they have selected other portals tools as their corporate portal People are looking at having to own and maintain two portals solutions – and expose one through the other Organizations in this position (that I have been working with) are choosing to say that SAP Enterprise Portal PRODUCES content and their corporate portal DISTRIBUTES content 43

  44. Remember: Be Careful How You Access Your New System • Remember, if you go the technical upgrade route, be careful how you access the system! • You will have two access methods (via the 3.5 interface or via the 7.0 interface) • If you go in as if through 7.0 and save certain objects (like queries) then they are no longer accessible via the 3.5 interface! 44

  45. Time for YOUR questions! How to contact us: Penny Silvia: psilvia@myitgroup.com Dr. Bjarne Berg: bergb@comerit.net 45

More Related