Home » Currently Reading:

AKC17: User and Support Contacts

Description:

Identifies the main user organizations and the primary user contacts for the application. Includes their office locations, mail stops, job titles and telephone numbers. There is also a separate section containing all of the contacts needed for supporting the application such as internal support personnel, suppliers, third party vendors, external support organizations, external interface contacts, EDI contacts, etc. Identifies the main application or power users of the application. These are key contacts for specific user application functions or individuals responsible for interface with the IT support group. Typically these key users help in functional acceptance testing or various approval levels for enhancement requests. They may be the contact person when changes are made to the application production.

Provides understanding of individuals who may need to be notified if system problems arise or when changes are being made to the application.

Provides information such as:

  • Internal or External Location of the contact person
  • Name of the contact person
  • Position or Job Title of the contact person
  • Phone and/or pager number of the contact person
  • Fax number Address of the contact person
  • E-Mail address of the contact person
  • Mailing Address of the contact person

How is it used?

Who are the main application or power users of the application. These are key contacts for specific user application functions or individuals responsible for interface with the IT support group. Typically these key users help in functional acceptance testing or various approval levels for enhancement requests. They may be the contact person when changes are made to the application production.

Why is it important?

(1) Identifies key applicaiton users and their contact information;
(2) Provides a list of  individuals who may need to be notified if system problems arises or changes are made;
(3) Identifies application support personnel and their contact information in case they need to be contacted if issues areise from recent changes they made and what they did;

(4) Provides information such as:

  • Internal or External Location of the contact person
  • Name of the contact person
  • Position or Job Title of the contact person
  • Phone and/or pager number of the contact person
  • Fax number Address of the contact person
  • E-Mail address of the contact person
  • Mailing Address of the contact person

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