Mobile // Mobile Applications
01:30 PM
Connect Directly

Top-Notch Application Performance

Keep users happy with service-level agreements and application performance management.

Defining and Delivering SLAs Through APM

Lots of IT organizations use an informal metric for measuring how satisfied employees are with application performance: If they aren't calling the help desk, things must be OK. But this is less a strategy than an avoidance tactic. Proactive organizations will work with business units to create internal service-level agreements that define acceptable performance metrics. An SLA provides a formal mechanism for CIOs to report on progress in meeting performance goals--and to demonstrate to business leaders the very valuable services that IT provides.

Of course, if we're going to offer SLAs, we must measure service levels with some kind of quantifiable metric. This is where application performance management comes in. APM tools are a vital source of information about the components that support an application, including software, server hardware, and network systems.

There are three basic steps to formalizing an internal SLA.

First, you need to define the metrics that will be used to calculate meaningful performance to the business; a promise of less than 10% packet loss is meaningless to the national sales manager. Focus on simple, yet telling, metrics such as user response time, the average time for a business unit to order IT services, or other customer-centric measures. Behind the scenes, these metrics will comprise a mix of transaction response times, CPU utilization, I/O responses, and so on.

3 Steps To Create Internal SLAS
1. Define Your Terms IT and business units should identify the critical applications that will be monitored, and work together to define service-level measurements that actually mean something to business users.
2. Plan For Reviews The organization must decide how and when internal SLA performance will be reviewed. For example, IT can deliver regular reports on SLA targets or build a portal that provides real-time metrics.
3. Pay The Penalty The IT group and business units must agree on appropriate consequences if IT fails to hit its service levels. For example, a system of chargebacks could be implemented to reimburse business units. Another approach is to structure IT bonuses or other incentives around meeting or exceeding promised service levels.

Second, determine how you'll enable business units to review SLA-related metrics. Will IT create regular reports to send to business leaders, or will information be provided via other means, such as an intranet? If you already have a corporate portal with scorecard metrics, you should be able to disseminate APM data there. If not, you may need to use a third-party management portal or an external reporting tool. In addition, many enterprise APM systems, including those from vendors such as BMC, CA, Compuware, and IBM, can present application service data to management.

Third, the IT group and business units must discuss how violations or potential violations will be reported and agree on consequences if IT fails to meet its agreements. For example, if a user phones the service desk to complain that an application is slow, should this kick off a process to investigate whether an SLA has been violated? Or should IT and business units meet regularly to examine performance numbers?

Behind the scenes, IT organizations that implement internal SLAs have to grapple with new technologies, such as cloud computing and virtualization. When it comes to public cloud services, including applications delivered in a software-as-a-service model, IT can't get complete visibility into the provider's infrastructure, complicating SLA measurement. As for virtualization, you need to ensure that your team can properly monitor and measure virtual environments. If IT can't see performance issues in a virtual machine, it risks violating SLAs.

IT's ultimate objective is top-notch application performance. SLAs and APM systems work in tandem to help achieve this goal.

InformationWeek: Aug. 9, 2010 Issue
Download a free PDF of InformationWeek magazine
(registration required)

Comment  | 
Print  | 
More Insights
Building A Mobile Business Mindset
Building A Mobile Business Mindset
Among 688 respondents, 46% have deployed mobile apps, with an additional 24% planning to in the next year. Soon all apps will look like mobile apps and it's past time for those with no plans to get cracking.
Register for InformationWeek Newsletters
White Papers
Current Issue
Increasing IT Agility and Speed To Drive Business Growth
Learn about the steps you'll need to take to transform your IT operation and culture into an agile organization that supports business-driving initiatives.
Twitter Feed
InformationWeek Radio
Sponsored Live Streaming Video
Everything You've Been Told About Mobility Is Wrong
Attend this video symposium with Sean Wisdom, Global Director of Mobility Solutions, and learn about how you can harness powerful new products to mobilize your business potential.