<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Extreme Service Manager &#187; Alert</title>
	<atom:link href="http://www.smallcart.com/extremesm/tag/alert/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.smallcart.com/extremesm</link>
	<description>Staying Ahead of the Curve with SmallCart Systems</description>
	<lastBuildDate>Thu, 27 May 2010 07:57:04 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Service Level Agreement 101</title>
		<link>http://www.smallcart.com/extremesm/service-level-management/service-level-agreement-101/</link>
		<comments>http://www.smallcart.com/extremesm/service-level-management/service-level-agreement-101/#comments</comments>
		<pubDate>Sat, 25 Apr 2009 03:25:03 +0000</pubDate>
		<dc:creator>SmallCart Staff</dc:creator>
				<category><![CDATA[SLM]]></category>
		<category><![CDATA[Alert]]></category>
		<category><![CDATA[Help Desk]]></category>
		<category><![CDATA[Information Technology]]></category>
		<category><![CDATA[IT Service Management]]></category>
		<category><![CDATA[ITIL]]></category>
		<category><![CDATA[ITSM]]></category>
		<category><![CDATA[SLA]]></category>
		<category><![CDATA[Staged Alert]]></category>
		<category><![CDATA[Support Center]]></category>
		<category><![CDATA[Technology Management]]></category>

		<guid isPermaLink="false">http://www.smallcart.com/extremesm/?p=6</guid>
		<description><![CDATA[The official ITIL (IT Infrastructure Library) definition of Service Level Agreement, more commonly referred to as an SLA, is a formally negotiated agreement between an IT Service Provider and a Customer. The SLA describes the IT Service, documents Service Level Targets, and specifies the responsibilities of the IT Service Provider and the Customer. A single SLA may cover multiple IT Services or multiple Customers. ]]></description>
			<content:encoded><![CDATA[<div><span style="font-size: x-small;">The official ITIL (IT Infrastructure Library) definition of Service Level Agreement, more commonly referred to as an SLA, is a formally negotiated agreement between an IT Service Provider and a Customer. The SLA describes the IT Service, documents Service Level Targets, and specifies the responsibilities of the IT Service Provider and the Customer. A single SLA may cover multiple IT Services or multiple Customers.</span></div>
<p><span style="font-size: x-small;">While this is a good definition for someone who understands the vernacular of ITIL, it isn’t easily understood by the layman. Let’s dissect the definition and put it into terms the general population can understand. The IT Service provider is the organization that has been hired by the Customer to perform a service, for example, answer calls. The service level agreement is the document, which can be a few brief lines or it can be a hundreds of pages, which describes each service level target(s). These service targets are based on the customers business needs. For example, if Large Corp. sells their products worldwide, they may have a need to have a call center that is available 24&#215;7. This one business objective, call center available 24&#215;7, could produce multiple service level targets such as:</p>
<p>Call Center is available to take calls 99.99% of the time each month.</p>
<p>No more than 5% of calls will abandon each month.</p>
<p>99% of all incoming calls must be answered within 30 seconds.</p>
<p>All of the service level targets must be agreed upon by both parties. Once both parties agree to all of the service level targets, they are assembled into the Service Level Agreement document. The service level targets will each have a description that identifies the expectation, how it will be measured and penalties, if missed. For example:</p>
<p>Call center must answer all incoming calls within 30 seconds</p>
<p>Measurement period: 1 month</p>
<p>Report(s): ASA Report 101 – monthly</p>
<p>Penalty: $10,000</p>
<p>The SLA is a joint goal between the IT Service Provider and the Customer. Although penalties do reduce costs and they do send a strong signal to service providers to improve their service, neither you nor the service provider &#8220;win&#8221; if an SLA is missed. Think of an SLA as a shared goal.</p>
<p>It should be noted that the term Service Level Agreement is used in many companies when discussing agreements between two internal groups, such as the Procurement Department will process all purchase requests by the Engineering Department within 5 business days. Technically, per ITIL, this is not a Service Level Agreement, but instead an Operational Level Agreement.<br />
</span></p>
<p class="facebook"><a href="http://www.facebook.com/share.php?u=http://www.smallcart.com/extremesm/service-level-management/service-level-agreement-101/" target="_blank"><img src="http://www.smallcart.com/extremesm/wp-content/plugins/add-to-facebook-plugin/facebook_share_icon.gif" alt="Share on Facebook" title="Share on Facebook" /></a><a href="http://www.facebook.com/share.php?u=http://www.smallcart.com/extremesm/service-level-management/service-level-agreement-101/" target="_blank" title="Share on Facebook">Share on Facebook</a></p>]]></content:encoded>
			<wfw:commentRss>http://www.smallcart.com/extremesm/service-level-management/service-level-agreement-101/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Setting expectations with Service Level Objectives</title>
		<link>http://www.smallcart.com/extremesm/service-level-management/setting-expectations-with-service-level-objectives/</link>
		<comments>http://www.smallcart.com/extremesm/service-level-management/setting-expectations-with-service-level-objectives/#comments</comments>
		<pubDate>Sat, 18 Apr 2009 03:21:58 +0000</pubDate>
		<dc:creator>SmallCart Staff</dc:creator>
				<category><![CDATA[SLM]]></category>
		<category><![CDATA[Alert]]></category>
		<category><![CDATA[Help Desk Ticket]]></category>
		<category><![CDATA[IT Service Management]]></category>
		<category><![CDATA[ITIL]]></category>
		<category><![CDATA[ITSM]]></category>
		<category><![CDATA[Service Level Objectives]]></category>
		<category><![CDATA[SLA]]></category>
		<category><![CDATA[Staging]]></category>

		<guid isPermaLink="false">http://www.smallcart.com/extremesm/?p=4</guid>
		<description><![CDATA[Webster’s dictionary defines the word, "expectation" as the act or state of looking forward or anticipating the degree of probability that something will occur.  Setting a Service Level Objective with your Customer sets their expectation.]]></description>
			<content:encoded><![CDATA[<p>Webster’s dictionary defines the word, &#8220;expectation&#8221; as the act or state of looking forward or anticipating the degree of probability that something will occur. How does this relate to the ITIL standards? Not setting proper expectations with the customer can result in dialogs such as:</p>
<p><strong>CUSTOMER:</strong> I submitted a ticket to have someone map a new printer to my laptop, but nobody has come by or called me back.</p>
<p><strong>HELP DESK:</strong>  I am sorry to hear that but we are busy with a network outage, it may be awhile before somebody comes by to assist you in your request.</p>
<p><strong>CUSTOMER:</strong> Can you give me some timeframe on when to expect a visit from a technician?</p>
<p><strong>HELP DESK:</strong> It all depends on when we get the network outage repaired; it could be then next 5 minutes or the next 5 days.</p>
<p><strong>CUSTOMER: </strong>It is no wonder your area is referred to as the helpless desk. CLICK!</p>
<p>Unfortunately, the above conversation is all too familiar in many help desks across the world because expectations are never set with customer. One way of setting expectations with the customer, even before they call or write, is to establish Service Level Objectives, such as:</p>
<table border="1" cellspacing="1" cellpadding="7" width="300">
<tbody>
<tr>
<td width="25%" bgcolor="#c0c0c0"><strong><span style="font-size: x-small;">Service Level</span></strong></td>
<td width="26%" bgcolor="#c0c0c0"><strong><span style="font-size: x-small;">Description</span></strong></td>
<td width="26%" bgcolor="#c0c0c0"><strong><span style="font-size: x-small;">Business Need</span></strong></td>
<td width="23%" bgcolor="#c0c0c0"><strong><span style="font-size: x-small;">Resolution Time</span></strong></td>
</tr>
<tr>
<td width="25%"><span style="font-size: x-small;">Urgent</span></td>
<td width="26%"><span style="font-size: x-small;">Site or System Outage</span></td>
<td width="26%"><span style="font-size: x-small;">Major Impact</span></td>
<td width="23%"><span style="font-size: x-small;">1-4 hours</span></td>
</tr>
<tr>
<td width="25%"><span style="font-size: x-small;">High</span></td>
<td width="26%"><span style="font-size: x-small;">Site Impacted</span></td>
<td width="26%"><span style="font-size: x-small;">Pressing Business Need; No workarounds</span></td>
<td width="23%"><span style="font-size: x-small;">4-8 hours</span></td>
</tr>
<tr>
<td width="25%"><span style="font-size: x-small;">Moderate</span></td>
<td width="26%"><span style="font-size: x-small;">Individual Impacted</span></td>
<td width="26%"><span style="font-size: x-small;">Workarounds Available</span></td>
<td width="23%"><span style="font-size: x-small;">1-2 days</span></td>
</tr>
<tr>
<td width="25%"><span style="font-size: x-small;">Low</span></td>
<td width="26%"><span style="font-size: x-small;">Individual Requests</span></td>
<td width="26%"><span style="font-size: x-small;">Not Affecting Work</span></td>
<td width="23%"><span style="font-size: x-small;">3-5 days</span></td>
</tr>
</tbody>
</table>
<p>Ultimately, service level objectives will benefit the help desk in a number of ways such as: Less repeat callers/tickets – with service level objectives established, customers are less likely to repeatedly call in order to get a status of their issue.Less upset customers – if the objectives are &#8220;advertised&#8221; on websites and IVR/VRU’s, the customers are less likely to be irate when calling a help desk if they already know that their issue may not be resolved on first contact and may be considered a low priority.Potentially reduces staffing – less repeat calls and tickets to the help desk, lowers call and ticket volume, and potentially reduces the staff needed to perform the volume of work.Assists in priority setting for employees – with objectives in place, the help desk staff have a clear understanding of what issues should take precedent (i.e., individual outage should be worked prior to a individual new request).If your help desk has not established service level objectives, your next step should be to have a project approved to begin establishing the objectives to help you manage your customers.</p>
<p class="facebook"><a href="http://www.facebook.com/share.php?u=http://www.smallcart.com/extremesm/service-level-management/setting-expectations-with-service-level-objectives/" target="_blank"><img src="http://www.smallcart.com/extremesm/wp-content/plugins/add-to-facebook-plugin/facebook_share_icon.gif" alt="Share on Facebook" title="Share on Facebook" /></a><a href="http://www.facebook.com/share.php?u=http://www.smallcart.com/extremesm/service-level-management/setting-expectations-with-service-level-objectives/" target="_blank" title="Share on Facebook">Share on Facebook</a></p>]]></content:encoded>
			<wfw:commentRss>http://www.smallcart.com/extremesm/service-level-management/setting-expectations-with-service-level-objectives/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
	</channel>
</rss>
