<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.3.3" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: KPAs and Configuration Management: How Does Your Organization Stack Up?</title>
	<link>http://blog.evergreensys.com/2007/09/05/kpas-and-configuration-management-how-does-your-organization-stack-up/</link>
	<description>News and notes about ITIL®, CMDB and "real world" IT solutions.  ITIL® is a Registered Trade Mark and a Registered Community Trade Mark of the Office of Government Commerce and is Registered in the U.S. Patent and Trade Mark Office.</description>
	<pubDate>Thu, 20 Nov 2008 17:24:49 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.3</generator>
		<item>
		<title>By: Colin Bartram</title>
		<link>http://blog.evergreensys.com/2007/09/05/kpas-and-configuration-management-how-does-your-organization-stack-up/#comment-6895</link>
		<dc:creator>Colin Bartram</dc:creator>
		<pubDate>Fri, 18 Jul 2008 16:14:45 +0000</pubDate>
		<guid>http://blog.evergreensys.com/2007/09/05/kpas-and-configuration-management-how-does-your-organization-stack-up/#comment-6895</guid>
		<description>Hi Don

For a company like mine, keeping pace with the evolution of ITIL and all it encompasses is a necessary task, so we can ensure that the IT Asset, Service and Security Management tools that we develop can at least fulfill ITIL's requirements when in the right hands. So your post here was very useful, and the comments about the 'federated' nature of an organization's CMDB much appreciated.

There is one aspect of Configuration information which I feel is very often missed from these schemas, in relation to the application software installed across an organization. That is, there is usually no information on the profile of usage of the application, at either the individual desktop level, or indeed across the organization as a whole. Once an application has been rolled out, it tends to get accepted as simply 'there', and there is no information as to whether it is actually used, by who and how much.

We sometimes get pulled into discussion of the introduction of application streaming, which is great and exciting technology, but we usually have to start by pulling people back to the basics, installing our Application Usage Monitoring component, and finding out more about just what software the organization is really using.  

I see the CMDB as the natural default repository for this information, but would appreciate your comments on that idea.</description>
		<content:encoded><![CDATA[<p>Hi Don</p>
<p>For a company like mine, keeping pace with the evolution of ITIL and all it encompasses is a necessary task, so we can ensure that the IT Asset, Service and Security Management tools that we develop can at least fulfill ITIL&#8217;s requirements when in the right hands. So your post here was very useful, and the comments about the &#8216;federated&#8217; nature of an organization&#8217;s CMDB much appreciated.</p>
<p>There is one aspect of Configuration information which I feel is very often missed from these schemas, in relation to the application software installed across an organization. That is, there is usually no information on the profile of usage of the application, at either the individual desktop level, or indeed across the organization as a whole. Once an application has been rolled out, it tends to get accepted as simply &#8216;there&#8217;, and there is no information as to whether it is actually used, by who and how much.</p>
<p>We sometimes get pulled into discussion of the introduction of application streaming, which is great and exciting technology, but we usually have to start by pulling people back to the basics, installing our Application Usage Monitoring component, and finding out more about just what software the organization is really using.  </p>
<p>I see the CMDB as the natural default repository for this information, but would appreciate your comments on that idea.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
