Run SAP like a Factory Best Practice Process Document ALM Process: Technical Operations Service Level Reporting Process Health Service Level Reporting
ALM Process Technical Operations Process Health Service Level Reporting Problem Description: How to technically monitor critical Business Processes of the customer solution landscape? Monitoring business processes should be available for Business Process Steps as well as for Interfaces between process steps The Monitoring Capabilities have to cover application- and technical related monitoring objects, which are crucial for the smooth and reliable flow of the Business Process. Best Practice Process Solution: Business Process Analytics Analyzing consistent Business Process Execution Operation centric Business Process Monitoring Define Solution based discrete Core Business Processes dedicated to Business Process Monitoring ( ->Manually integrated Solution Documentation ) Business Process Monitoring, Interface Monitoring, Data Volume/Consistency Management, Business Process Job Management, End-User Experience Monitoring as proactive Monitoring ( Service Level Reporting ) and re-active Monitoring ( Application Incident Management ) Lifecycle centric Process Management Business Process Management from Requirement to Design including Operational Process KPI s to Operation ( -> System integrated Solution Documentation ) Process Health Service Level Reporting SAP Standards Exception Handling and Business Process & Interface Monitoring Proactive Business Process Health Service Level Reporting allowing pro-active analysis of critical system health tendencies and potential technical SLA/KPI violations 2012 SAP AG. All rights reserved. 2
Y axis 2nd Y axis Process Health Service Level Reporting Avg. Dialog Response Time Avg. Database Response Time Database Growth System Availablity Database Size Hardware Availability Service Level Management means to measure specific system parameters in accordance with Service Level Agreements between two parties, organizational units, or organizations involved in the management and operation of a customer s SAP solution. The results should be reported on a regular basis: Service Level Reporting. 12 10 8 6 4 2 0 10 30% 8 40% 5 65% 70% 60% 50% 40% 30% 20% 10% 0% Label 1 Label 2 Label 3 Column 1 Line 2 2012 SAP AG. All rights reserved. 3
System 1 EWA Data SAP Solution Manager Collected EWA Data EWA EWA Reports Reports Availability Reporting 1 2 SAP NetWeaver BI 5 BW Content (e.g. SMD Data) System 2 Service Level Reporting EWA Data BPMon Data 3a BI queries 3b System n CCMS Monitoring Infrastructure EWA Data Central Performance History 4 BW Content 2012 SAP AG. All rights reserved. 4
EarlyWatch Alert (EWA) Incl. Java specific content Availability Reporting System Availability (ABAP / Java stack) Instance Availability Instance Logon Availability Logon Group Availability Business Process Monitoring (BPMon) Direct Datafeed: Direct transfer of aggregated BPMon Alerts to Service Level Reporting, or Indirect Datafeed: Extraction of aggregated BPMon Alerts to BI. Re-Integration of BI-evaluations based on BPMon data into Service Level Reporting Central Performance History (CPH): Response time related evaluations from CPH can be integrated in Service Level Reporting as well Evaluation of BI-related Data (standardized regarding BI-Data related to Solution Manager Diagnostics as well as evaluation of any BI) 2012 SAP AG. All rights reserved. 5
The Option (BPMon Alert Statics) activates the evaluation of aggregated alert information from BPMon within Service Level Reporting 2012 SAP AG. All rights reserved. 6
BPMon Trend Analysis embeds the BI-Reporting for BPMon into Service Level Reporting. 2012 SAP AG. All rights reserved. 7
Graphical as well as a Tabular BPMon Trend Analysis can be embedded in Service Level Reporting. The data is taken from SAP BW. 2012 SAP AG. All rights reserved. 8
Best Practice Process - Detail Process Description Service Level Reporting (SLR) is designed as a periodic Management Report, evaluating different areas of Solution Monitoring. Process Health Service Level Reporting, in particular, is focusing on the evaluation of aggregated alert information from Business Process Monitoring (BPMon). Hereby thresholds for Yellow and Red Alerts, which have been defined by the customer in the Setup of Business Process Monitoring, serve as Service Level Agreements (SLAs). The evaluations in Service Level Reporting check, if these SLAs have been met and can be carried out in two alternative ways: BPMon Alert Statistics : Direct evaluation of aggregated alert data from Business Process Monitoring within SLR. This option provides the number of raised as well as the number of confirmed alerts per Alert Type and selected timeframe (week or month), or BPMon Trend Analysis : The BPMon Trend Analysis, which is available in SAP BW, can be embedded into Service Level Reporting as well. For the selected Alert Types, Service Level Reporting will then display the Trend Analysis in graphical and tabular view. Hereby the Trend Analysis can be launched for a weeks, months, or 6-months time frame Both options can be used alternatively or in combination. However SAP highly recommends to make use of the BPMon Trend Analysis in any case. The information, a customer can get from the BPMon Trend Analysis, is the basis for subsequent decisions and further activities. 2012 SAP AG. All rights reserved. 9
Best Practice Process Advantage / Integration Advantages Quick Setup of SLR SAP BW Trend Analysis for Business Process Monitoring makes the evolution of specific KPIs visible and transparent at a glance. This is the basis for all further decisions and activities Disadvantages Service Level Reporting has a clear focus on the evaluation of the Solution Monitoring area. The report does not address reporting and evaluation for other SAP Solution Manager Scenarios, like Implementation and Upgrade, Test Management or SAP Solution Manager Service Desk. Integrated with the Business Process Operations process* Business Process & Interface Monitoring: Lifecycle centric Process Management Operation centric Business Process Monitoring Business Process Interface Monitoring * In the Business Process Repository, ALM processes are reflected in scenarios, Business Process Operations processes are reflected in processes 2012 SAP AG. All rights reserved. 10
2012 SAP AG. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iseries, pseries, xseries, zseries, eserver, z/vm, z/os, i5/os, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation. Linux is the registered trademark of Linus Torvalds in the U.S. and other countries. Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries. Oracle and Java are registered trademarks of Oracle and/or its affiliates. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc. HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C, World Wide Web Consortium, Massachusetts Institute of Technology. SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, StreamWork, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries. Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd. Business Objects is an SAP company. Sybase and Adaptive Server, ianywhere, Sybase 365, SQL Anywhere, and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase, Inc. Sybase is an SAP company. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary. The information in this document is proprietary to SAP. No part of this document may be reproduced, copied, or transmitted in any form or for any purpose without the express prior written permission of SAP AG. 2012 SAP AG. All rights reserved. 11