Lets have a look at how PerformanceGuard supports decision making on all levels of an IT organization:

Susan – End User

Susan calls Service Desk to report that her computer is slow this morning—again ...!

It's the busiest time of the month, and she really needs to be able to do her work without delays.

Greg – 1st Level Supporter

Greg takes the incoming call from Susan. He uses the Computer Overview dashboard in PerformanceGuard to look up Susan's computer. The dashboard shows that Susan's computer lives up to standard requirements for RAM, etc.

Greg asks some probing questions, and finds that Susan's computer is primarily slow when she works with a particular server-based finance application.

Greg now looks at the PerformanceGuard dashboard's Event Timeline: It confirms that Susan has recently had response time problems when she worked with the finance application. 

Greg thanks Susan for reporting the issue, and he tells her that he and his colleagues will look into the problem immediately. He then takes a snapshot of the PerformanceGuard dashboard and attaches it to the Service Desk ticket, when he escalates the issue to Danny, the Problem Manager, for further investigation.

Danny – Problem Manager

Danny uses the Application Status dashboard in PerformanceGuard to verify how many users have had response time problems when they worked with the server-based finance application.

He finds that 12 user's computers across three office locations have recently had response time events when they worked with the finance application.

Because computers at three separate locations have had the same type of events when they worked with the finance application, Danny reckons that the problem must be server-related rather than network-related.

In PerformanceGuard Danny creates a report with graphs that illustrate the problem. He attaches the report, when he escalates the issue to John, who manages the finance application server.