Home » Currently Reading:

Application Support: Performance Measurement

The collection, analysis, and reporting of performance metrics are fundamental components of CAI’s Legacy Application Support methodology.  Metrics enable CAI to effectively measure performance, identify opportunities for process improvements and reduce maintenance costs.  The key areas for measurement are determined during the Transition Phase and are continually re-evaluated during the life of the engagement. Maintaining service levels, quality of support, and user communication are integral to success.  Initially, CAI reviews service level requirements with the client and delivers a service level agreement.  Service level metrics data is captured using CAI’s proprietary process and tracking tool, Tracer®.  Examples of metrics that are tracked include:

  • Number of events within service level guidelines
  • Application downtime
  • Rework trend
  • Time to resolve production problems
  • Failure frequency
  • Number of outstanding work requests
  • Client satisfaction survey ratings

The following graphic depicts the methodological process support and interfaces provided through the use of Tracer®.

Tracer Process Image

Productivity, as it relates to programming and quality, is a critical success factor.  Actual programming hours are tracked against estimated programming hours to determine an efficiency ratio for each programmer.  These efficiency ratios are provided to the programmers, and individual scores are compared to team averages to assess individual contribution to the overall effort.

CAI’s expertise in performance measurement allows performance issues to be addressed proactively.  As the client and CAI continue working together to improve the support partnership, additional and/or different metrics may be developed and tracked.

Status Reporting

Status reporting is an integral component of CAI’s Legacy Application Support offering.  Information pertaining to unresolved issues, estimated time to completion, and outstanding assignments will be documented and reviewed through status reports.

CAI provides status reporting for each of the teams, to the appropriate support oversight person.  These reports will be presented on a regularly scheduled basis at the status meetings. The status reports include:

  • List of all open items by event type
  • List of completed service events by event type
  • Status report of the development phase for all work
  • Exception reports highlighting potential problem areas
  • Personnel changes
  • Open issues

Issue Management

Another key component of CAI’s Legacy Application Support offering is the management and tracking of issues.  An issue is anything that delays the completion of a work event.  CAI uses Tracer® to track and manage issues. This allows for systematic reporting and querying of issue status and issue assignment.  This virtually guarantees that issues are not lost or forgotten.

Our Sponsors

IT Support Services Comments

  • Bob Anderson: Daniel, from a certain point of view you are correct. CMMI- DEV deals primarily with software development best practices, the old CMM Level-5 dealt a great deal with defects. However, as you know the ...
  • Bob Anderson: Gunter, there are many possible SLA components and metrics that can be defined for any application software support. First I would recommend that you read this article which I had published in Compute...
  • Bob Anderson: Amiet, I would put it under the "Incident" process and track dates, number of occurrences, how much lost time, cause (who did it). You will need data for management if the practice has to stop. If you...
  • Bob Anderson: Amit, first of all why is the customer powering down the equipment? This should be brought to the attention of management and a very strong note sent to whoever is doing this.  If they are doing it on...
  • Bob Anderson: Mark, it is doubtful that you can fix the problem, it is mainly a management issue. The best you can do is to gather statistics on the backlog of enhancements, the number and severity of incidents, an...

ITIL V3 Application Support Q & A

If you have any question on the blog content or have some specific question on how ITSM & ITIL can dramatically improve performance and reduce the cost of your Application Support service "Ask Bob"
Question :
Answer :
Gunter, there are many possible SLA components and metrics that can be defined for any application software support. First I would recommend that you read this article which I had published in Computer World on "How to create Meaningful IT Support SLA's"  use this link...
Question :
Answer :
Daniel, from a certain point of view you are correct. CMMI- DEV deals primarily with software development best practices, the old CMM Level-5 dealt a great deal with defects. However, as you know the folks who developed the original CMM  were not really initially inter...
Question :
Answer :
Amiet, I would put it under the "Incident" process and track dates, number of occurrences, how much lost time, cause (who did it). You will need data for management if the practice has to stop. If you want to be "proactive" in stopping this practice" you must capture bu...
Question :
Answer :
Mark, it is doubtful that you can fix the problem, it is mainly a management issue. The best you can do is to gather statistics on the backlog of enhancements, the number and severity of incidents, and how many technical support calls from users you get and the average...
Question :
Answer :
Amit, first of all why is the customer powering down the equipment? This should be brought to the attention of management and a very strong note sent to whoever is doing this.  If they are doing it on their own without any instruction to do so and it affects other user...