Home » Featured » Currently Reading:

Tracer – CAI’s IT Service Management Tool

November 3, 2011 Featured No Comments

“CLICK ON THE LINK ABOVE”

Tracer, CAI’s Application Support Service Management tool is the single point of integration for all IT Service Management (ITSM) processes, SLA performance goals, operational data and service operations reporting.

 Tracer enables IT service delivery professionals to track all work throughout the complete process lifecycle. Tracer insures that relevant work and performance data are captured real-time as work is being performed. These features of Tracer provide an unprecedented level application support visibility, control, performance improvement and cost reduction capability.

 Only Tracer has these critical IT service management capabilities:

  •  Defined work processes aligned with ITIL V3 / ISO 20000  standards and specifically designed for the application support service environment
  • Work, resource, SLA performance and time data collection integrated within work processes
  • Service Level Agreement (SLA) tracking and performance reporting

 All these components function seamlessly within a single integrated operating environment and data repository.

 Tracer was designed for the day-to-day operating environment of IT application support service management professional with a minimum of data interaction and distraction from their real work..

 The flexibility of Tracer’s configuration tables allows for easy adaptability to virtually any IT service environment. Tracer’s real-time customizable dashboard display the status of ll work assignments with color coding (red, yellow, green) that highlighting any work assignments jeopardizing service level goals

Comment on this Article:

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 :
Hi Bob, Since I have make a control of doubts from our dealers questions, that uses our SW, is possible to see evaluation of our intern SLA. Me question is: I find only three metrics using to compare months to months our evolaution: error programs, legislation, improvem...
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 :
In your answer to "Question : bugs, known errors and kb articles". You refer to CMMI-DEV and talk about defects and say that CMMI-DEV is for software development and does not deal with operations. So, is that another way of saying that CMMI-DEV ignores operations? Isn't...
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 :
Hi Bob, Continuing on the question i posted yesterday. I understand your comment and we have actually done that. It is a reactive approach and we now want to move to a praoctive approach and want to understand if these activities should be managed under the change proce...
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 :
The chaos in applicaiton support in my company is in part due to the limited resources assigned to aging applications and very little documentation. How do I suggest that we need help?
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 :
If a customer is powering down equipment at his site and it will bring down the services during that time, should this be recorded as a change. You will not have any control over this activity and this activity is managed by the customer himself. These activities may ha...
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...

Popular Content