Home » Currently Reading:

What is Application Knowledge Capture?

Overview

Senior executive business man

Institutionalizing Business and Operational Knowledge are critical components of any business organization.  The capture and easy deployment of organizational knowledge improves employee productivity regardless of whether they are a senior marketing executive or a customer service representative.  Knowledge is a business asset. The value of capturing and maintaining a businesses critical operational knowledge is no different for an IT organization.  In fact, in an environment that is considered less mature and more volatile by industry experts, the importance of institutionalized application knowledge and documentation is significantly increased.

The need for capturing critical application knowledge is exacerbated given the current industry trends of outsourcing, mergers and acquisitions, and a retiring workforce.  In many IT organizations, key workers personally hold critical application knowledge that is undocumented and unavailable to other team members or others within the business organization.  In addition, many applications are complex and include countless modifications that have been made overtime.  In many cases the application knowledge (such as business functionality, sample reports, screen flows, and problem resolution techniques) is inconsistent, unavailable, or out of date.

Protecting this information (which ultimately reflects the organization’s IT investment) involves developing, managing, and maintaining application knowledge repository.  The institutionalized application knowledge needs to be available to the entire IT organization anywhere in the world using a standard web browser interface that requires no additional software.  Without the investment of capturing this critical application knowledge, business and government IT organizations may face such situations as decreased service levels, business disruption, costly re-creation of information, and expensive training requirements.

CAI has addressed the need of its clients for capturing critical application knowledge through the Application Knowledge Capture (AKC) service offering.  Through a field-proven structured process, CAI gathers, formats, and distributes application knowledge components using standard web technologies.

1 - Structured Approach

To ensure that all data is collected and converted into valuable information, CAI employs a four phase process. This process focuses on identifying data collection from existing sources, program and object library reviews, and structured interviews with key knowledge workers.

4 - Four Phase Life-cycle Approach

Using a customized category structure, structured interview questionnaires, data capture templates, web browser-based templates, and one-step publishing. In this way critical application knowledge is made available to the entire business organization anywhere in the world.

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