OPSA_Demo and OPSA CAPs

Measuring business applications is never easy. IT Organization are facing new challenges when traditional IT moves to the new style of IT.

Chris is the Business Application Manager of the IT organization at ABC Inc. One of his main responsibility is to ensure that all business-related applications are monitored and that their performance is meeting expectations. Chris uses ITBA, a Business Intelligence solution that leverages the analytical functions to help him monitor all business applications and identify the insights in the system to faster resolve the root cause of failures.

1. During his daily work, he logs into ITBA and opens the OPSA Overview Dashboard page to first have an overall view on his measurements.
2. In the OPSA Overview Dashboard page, he checks his predefined Objectives in the Scorecard component.

3. When he clicks on the Improve Application Availability Objective, the KPI View component shows the Objective KPIs.

   • The Mean Time Between Failures of Applications KPI measures the average expected time between two failures for all the applications during the measurement period.
   • The Percentage of Applications Availability KPI measures the availability rate of the applications during the measurement period.
   • The Percentage of Failed Application Transactions KPI measures the failed rate of application transactions during the measurement period.
   • Additional KPIs show more information about application performance such as Percentage of Applications Meeting 1 Second Performance, Percentage of Applications Meeting 10 Seconds Performance, Percentage of Applications Meeting 1 Minute Performance.
4. The Metric View component shows the trends regarding the Number of Events, Alerts, Monitored Created Applications, and Average Application Transactions Response Time during the measurement period.
5. After checking the overall status on Business Application Management, Chris opens the Business Application Performance Dashboard page for further information.
6. The Business Application Performance Dashboard page is more specific as it measures the result of each KPI in the different layers.
7. Chris checks the KPI View component, and finds that the statuses of the Percentage of Applications Meeting 10 Seconds Performance and Percentage of Applications Meeting 1 Minute Performance KPIs are red, which means that the applications cannot meet the performance baseline and have big performance issues.
8. Meanwhile, Chris also finds that the Percentage of Available Applications KPI is also red, which means that the applications only recently became unavailable.
9. He think that there might be some strong correlations between low application performance and application unavailability.
10. In addition, in the Historical View component, he sees that the three KPIs trends have been decreasing for the last two weeks, so he decides that the team must return those abnormal states back to normal.
11. Further, by looking at the Number of Applications by Availability KPI in the Bar Chart View component, he understands that there are currently two unavailable applications.
12. He suspect that application unavailability might cause the problem. Looking at the Number of Failed Application Transactions by Applications KPI in the Cluster Bar Chart View component, he sees that two cloud-related applications have the top failed times. He decides to send an annotation to Richard, the owner of the Cloud System Application, requesting clarifications: "Richard – We have poor application performance, please provide insight and set a plan by EOW.
13. When Richard gets the annotation from Chris, he checks his report and starts the analysis of the problem.
14. Richard then replies to Chris that he will initiate a meeting with the team to address the issue by EOW.

User interface elements are described below (when relevant, unlabeled elements are shown in angle brackets):