Home » Currently Reading:

CAI’s Legacy Application Support

MM_Work Flow

 

Application Support Work Event Process FlowsCAI Event Processes

 

        

Computer Aid’s (CAI) legacy application support service was designed and developed to closely align with ITIL V3 service management best practices. CAI’s process, metrics and data driven application support service provides our customers with an unprecedented level of performance and visibility through the use of Tracer, CAI’s IT service management tool.

CAI’s application support methodology and tools have  been continually updated for the past 20 years adding and updating to keep pace with the evolving ITIL Service Management standards:

These best practice elements are used to continually improve the CAI team’s service performance to our customers. CAI’s methodology and Tracer are designed to provide complete visibility and control for all the facets of support and development tasks so that they can be properly planned, managed and delivered in accordance with the priorities and mutually agreed to SLAs.

Using CAI’s service management tool Tracer we are able to gather the data necessary to analyze the root cause of system support issues, giving us the ability to diminish and streamline support and to identify areas for continuous improvement for our clients. Tracer enables the team to effectively manage the day-to-day work events of programmers, team leaders, and service managers.

Our Service Managers are ultimately responsible for enforcing workflow, monitoring support, and gathering the data required to report SLA compliance. Real-time process enforcement and data collection with Tracer enable our support team to know:

  • What everyone is doing
  • What they are supposed to be doing
  • How well they are doing it
  • What they will be working on next and
  • What the end-users thinks about their work

CAI’s Legacy Application Support offering and accompanying methodology enable IT executives to identify non-strategic work trends, provide real time comprehensive reports, and implement process-driven methods.  These measures result in improved productivity and customer satisfaction, the ability to redeploy knowledge workers to strategic tasks, an improved competitive advantage and reduced application support costs.  Today’s business and technical environment is changing faster than ever before.  As a result, Information Technology executives are faced with ever-growing challenges including:

  • Increasing Maintenance Costs
  • Implementing Strategic Initiatives
  • Replacing/Enhancing/Protecting Business Critical Applications
  • Decreasing Headcount
  • Finding and Retaining Skilled Resources
  • Maintaining Employee Morale
  • Replacing Missing or Outdated Documentation
  • Supplementing Declining Application Knowledge
  • Addressing Rapid Technology Changes

CAI’s Legacy Application Support offering was developed to provide application support services to clients, while addressing the impacts to application support resulting from these challenges.  CAI’s Legacy Application Support methodology is based on many years of experience, combining the disciplined software support approaches of the US military, IEEE, SEI, ITIL and ISO, with the best practices of CAI’s Fortune 1000 clients.  As a result, CAI is able to provide flexible, cost-efficient support services using repeatable processes and metrics – ultimately enabling clients to focus on their strategic objectives.

This solution addresses every phase of the outsourcing lifecycle; from the initial assessment and transition of responsibility, through the stabilization and optimization of the application support services.

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...