ITIL and Business Musings. http://www.linkedin.com/in/dmular
Dawn Mular
« Reciprocal Value... | Main | Sun Tzu and IT Inspi... »
Thursday Apr 17, 2008
Metrics aid SLA and Operations Management-- As a Partnership, not as a weapon







Metrics and Reporting, done correctly, is a focus aid to SLA Management
– Business Service Health and Performance Capability Metrics.  Let
us stop using metrics as a defensive weapon-- you, not me.  The
real value transcends the indicator when the review and analaysis
reveals what is sufficient to an SLA being met or not. (Management, ITIL, COBIT, Service or Ops) Review of what's
changing, and what's history reports indicate how well we are
delivering on SLA requirements. Forecast reports tell you what change
or possible disruption is planned. Constructive Resolution Controls
provide additional data into the nature of an incident, and what
process action is necessary for resolution. Notification – what
capabilities provide a moment it time value to contain the information
needed for service or operational resolution.



It is REVIEW and Continuous Process Improvement that drives the notion
of Business Process (SLA) Improvement – By evaluating the elements of
performance, capacity, and historic metrics becomes a tangible source
of Business Intelligence data. Observing where we are, where we aspire
to go, and observing these metrics over time, will illustrate the
process improvements to be made, and when the changes are optimal.



1.  How do we know we are
managing the "right" data?
Business Services Performance
Metrics – The monitoring of the performance aspects of a service are
continually monitored and calculated. As Business Service performance
changes, so do the visual indicators users see. Users can specify what
the performance thresholds are, so they can chose when they want to be
alerted.



a.
Right Subject Matter Experts, plus data is an indicator of established
Business Services Health
– Define the elements of IT Business
Service,  reviewing capability, continually evaluated and
presented to users. As service health or capability is identified, the
results show in the metrics,  if the change being introduced fails
or degrades, you gain a complete view of the indicators affected by the
situation.



b. The Right Definition and Rules 
– produce complete and accurate data, with continuous subject matter
expertise evaluations being made to analyze and examine the performance
of the service. Determine the consistency, the service delivery style
and level of alerting that is required given the performance being
seen. Alerting can result in color changes on Status Maps, and if the
Business Service performance requires user intervention, a Problem of
appropriate severity is created, that should have a corresponding
business improvement activity for that feedback.




2. What is needed to produced the
"right metrics view" 
– Users of metrics have different
needs to monitor performance, capacity, and service delivery metrics
views create a flexible, yet common set to view the right cross-section
of Business Services the user needs.  The right view is flexible
enough to support service, operations, and project capacity, but
complete enough to present the data in a consistent and complete
fashion.



a. The
Right Presentation
– Standard coverage and calculation
consistency. Graphical and Tabular Status indicators. Maturity is found
in sourcing the systems for data completeness, not just the "not my
fault" simple Status Map that yields a pass or fail set of traffic
indicators Production and Systems Go – Change Caution – Stop the
business issue indications.  



b. The Right Structure: Who
Cares?  What is being done? Finding Out More – Business process
support personnel who can make use of more detailed information can
Drill Down to get more information about the state of the supporting
Applications.












 

Posted at 05:47AM Apr 17, 2008 by Dawn Mular in Personal  |  Comments[0]

Comments:

Post a Comment:
  • HTML Syntax: NOT allowed