Home » Currently Reading:

Application Support: Work Flow

Through our Legacy Application Support service offering, we provide support processes for the fundamantal types of work events which support teams deal with in day-to-day support operations:

The process for addressing each of these events varies by event type.  The following diagram describes the flow of each work event and the interaction among the work events.  The activities to be supported during the engagement are defined in terms of these work events.

MM_Work Flow

Application Support Work Event Process Flows

CAI Event Processes

Maintenance & Enhancement Work Requests

Planned maintenance activities will be based on formal requests for service (work requests) encompassing the following types of work:

Corrective Maintenance:  Reactive modifications to an application performed to correct discovered faults.  These requests frequently result from application failures and problems reported by Operations, the Help Desk, or the user community.

Adaptive Maintenance:  Modifications to an application performed to accommodate a changed or changing environment.  These modifications typically add to or create new functionality in the application and its users are most often the sources of these requests.  All such requests must be approved and prioritized by steering committee.

Perfective Maintenance:  Modifications to an application performed to improve performance, or maintainability.  These requests originate with functional users.  These requests must be approved and prioritized by steering committee.

User Technical Support (call support)

The team responds to questions from the user community regarding systems operations and utilization.  This activity may involve 24 x 7 coverage, depending on the requirements of the user community.  Call support may include both level 1 and level 2 support.  This is based on the level of support provided by the Help Desk function.  Frequently, this activity may require extensive investigation and consume considerable time without any measurable deliverable.  Consequently, logging and tracking the time dedicated to this effort is essential to improving operational efficiency.

Incidents & Problem Management

Incidents typically involve unscheduled, corrective maintenance performed to keep an application operational.  Events such as abends, production errors, and emergency problems identified by Operations, Help Desk, or the user community will be reported to the support team.  The team provides the following emergency maintenance/production support:

  • Direct and immediate response to both critical and non-critical events occurring during normal working hours (weekdays 8:00 a.m. to 5:00 p.m.).
  • Off-hours response primarily limited to those critical events occurring after hours (weekdays 5:00 p.m. to 8:00 a.m., weekends, and holidays).  This after-hours support is provided through the use of an on-call rotating duty roster and beepers.

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