CA WILY APM

Quick View

Summary:

ASU has a substantial investment in business critical applications that serves its staff and customers. Whether the application is homegrown or provided by a vendor, it is important to understand that the availability of these applications is affected by many more factors then just the code. Effective management requires monitoring of the web environment: from the web server, to the application, to back-end systems, to the hardware and the network. While looking at each of these factors, it is necessary to act in a proactive manner to head off problems that can cause customer latency or downtime. This means having accurate root cause analysis.

The CA mission is to provide a way to track the quality of that experience (whether internal or external) so ASU’s business is not in the dark regarding the most fundamental dimension of its relationship with the service consumer. CA will show the value of this tool during a 30 day POC.

Start Date:

July 20, 2009

Go Live:

July 20, 2009

End Date:

August 20, 2009

Current Milestone:

July 20, 2009 – Start Wily Pilot in Test Environment

Stage:

On hold

People

Sponsor/Champion:

Adrian Sannier, Vice President and University Technology Officer

Lead Customer:

Terry Hinton

Lead Customer:

Jack Hsu

Project Manager:

Terry Hinton

Contact for more information:

Terry.Hinton@asu.edu

Associate VP University Technology:

Bob Nelson

University Technology Director:

Mary Covington

More Info

Source:

Executive

Priority:

High

Scope:

ASU Drivers:

* Improve system availability to 99.999% across the service (ASU goal is 5 9’s)
* 24 x 7 application monitoring support and 24 x 7 continuous operations
* Root cause investigation
* Escalation
* Interim / short term solutions

ASU Requirements:

* Proven Solution from a Trusted Partner
* Monitor end to end customer experience
* Reduce time to identify service degradation or failure
* Provide and automate a single “pane of glass” or dashboard that represents a business transaction and intergrates with ASU’s system health page.

CA Solution Summary:

* Provides end to end view of web transaction
* Improves Quality of Service through root cause analysis
* Reduces the impact of service disruptions
* Optimizes end user experience

The POC will show how CA Wily can perform on MYASU Application in production during peak time. There will an executive summary at the end of the POC so summarize findings and over value to MYASU.

All Milestones and Schedule:

Kick-off presentation July 20

* Optional - Introscope solution overview / demonstration – 30 minutes
* Proof-of-Concept schedule – 30 minutes

Installation and setup (Test Environment) July 20 AM

* Install Introscope Enterprise Manager
* Install Introscope Workstation
* Install Introscope Agents
* Install and configure CEM appliance
* Use out of the box dashboards to verify data acquisition
* Begin Installation of optional Introscope components
* Load Test and Verification

Installation and setup (Production Environment) July 20 PM

Build on First Day’s implementation (Order is Flexible) July 21 & 22

Begin Monitoring and Triage Process

* Develop metric groupings
* Knowledge Transfer and Training
* Starting developing additional dashboards
* Reports
* Knowledge Transfer and Training
* Illustration of custom-monitoring options: custom PBD, etc.

Wrap up presentation and demonstration – 90 minutes July 27

* Build wrap up presentation
* Review findings
* Present recommendations

Deliverables:

- Full APM-Wily product working in production environment

-Hierarchy of Dashboards for Service Delivery

-Instrument Custom Classes for MyASU

-Show support for custom fameworks

- Executive Summary of POC to be presented to Management and CIO

-Export of SmartStor Data into CSV

-Publish MYASU response time on ASU systemhealth web page.

Risk & Threats:

-Rack space and power for CEM Appliance

-Administrative access to all required servers

-Availability of Load Generation to stress-test install (LoadRunner or the like).

-ASU Personnel availability; both to refine requirements and answer any questions for the onsite team.

-Ideally we would like to have internet access for OnSite Teams Laptops.