Search
Topics
  Create an account Home  ·  Topics  ·  Downloads  ·  Your Account  ·  Submit News  ·  Top 10  
Modules
· Home
· Content
· FAQ
· Feedback
· Forums
· Search
· Statistics
· Surveys
· Top
· Topics
· Web Links
· Your_Account

Current Membership

Latest: KMcRobert
New Today: 5
New Yesterday: 67
Overall: 148466

People Online:
Visitors: 59
Members: 3
Total: 62 .

Languages
Select Interface Language:


Major ITIL Portals
For general information and resources, ITIL and ITSM World is the most well known for both ITIL and ITIL Books. A shorter snapshot approach can be found at ITIL Zone

Related Resources
Service related resources
Service Level Agreement
Outsourcing

Note: ITIL is a registered trademark of OGC. This portal is totally independent and is in no way related to them. See our Feedback Page for more information.


The Itil Community Forum: Forums

ITIL :: View topic - KB process question.
 Forum FAQForum FAQ   SearchSearch   UsergroupsUsergroups   ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

KB process question.

 
Post new topic   Reply to topic    ITIL Forum Index -> Problem Management
View previous topic :: View next topic  
Author Message
Berto
Newbie
Newbie


Joined: Jun 14, 2007
Posts: 3
Location: Buenos Aires, ARGENTINA

PostPosted: Fri Jun 15, 2007 1:22 am    Post subject: KB process question. Reply with quote

Hi everyone!
I'm developing a Knowledge Base Creation and Maintenance process from scratch, I just identify some key points like Acquisition/Creation, Management, Reuse, Publishing/Reporting, Maintenance, etc., etc.
I got to this point but I'm stuck now. Could somebody give me a guide or recommendation? Embarassed

Thanks in advance!!!!

Diego
Back to top
View user's profile Visit poster's website
Guerino1
Senior Itiler


Joined: Jan 01, 2006
Posts: 500
Location: New Jersey

PostPosted: Sat Jun 16, 2007 4:38 am    Post subject: Reply with quote

Hello Diego,

What kind of things are you categorizing as knowledge?

- Related FAQs?
- Related Notes?
- Related Documents?
- Related Glossary Terms?
- Related Content?
- Related Incidents?
- Related Problems?
- Related Changes?
- Related Risks?
- Related Projects?
- Related Tasks?
- Related Phone Calls?
- Related Products?
- Related Releases?
- Related Services?
- Etc.

Technically, your KB should have a great deal of highly categorized and easy to find information that covers many different things. Is there something specific you're trying to accomplish?

My Best,

Frank Guerino, CEO
TraverseIT
On-Demand ITIL
Back to top
View user's profile Send e-mail Visit poster's website
Berto
Newbie
Newbie


Joined: Jun 14, 2007
Posts: 3
Location: Buenos Aires, ARGENTINA

PostPosted: Thu Jun 21, 2007 12:22 am    Post subject: Reply with quote

Frank,
I'm trying to create a process related to Problem Management. in a future stage this process should be used by the Problem Administrator, Coordinators, etc.

This should be a guide....

Thanks !!

Diego
Back to top
View user's profile Visit poster's website
Guerino1
Senior Itiler


Joined: Jan 01, 2006
Posts: 500
Location: New Jersey

PostPosted: Thu Jun 21, 2007 1:25 am    Post subject: Reply with quote

Hello Diego,

One thing to keep in mind is that you want to capture any and all data associated with a Problem, throughout its entire lifecycle (from its inception to the day it's closed). This will build a tremendous amount of knowledge around the given Problem, itself.

Another thing is to ensure that you do the same, consistently, for all other Problems. This will allow you to build up metrics around key attributes and data associated with your Problem inventory.

Another thing is to ensure that all Problem related data is in one place/system, so that you can look across all Problem knowledge.

A solid way to build out your KB is to simply ensure a solid process that fills in all key data points for each and every Problem ticket that is entered. Over time, you will find that there will be a great deal of useful information that you will capture. Your KB content will build up, organically.

However, you will also need to capture data/information that is not directly associated with attributes on the Problem ticket, itself, such as Documentation, FAQs, Content, Product Information, Release Information, Change Information, Configuration Item Information, Project Information, and much, much more. The only way you will be able to accomplish this, successfully, is through couplings/integrations to and from other systems or by having a single system that collapses all such information into one database, where all relationships between such data are automatically maintained. The former is expensive and time consuming. The latter will change how your enterprise works together.

Anyhow, I hope this helps.

My Best,

Frank Guerino, CEO
TraverseIT
On-Demand ITIL
Back to top
View user's profile Send e-mail Visit poster's website
Berto
Newbie
Newbie


Joined: Jun 14, 2007
Posts: 3
Location: Buenos Aires, ARGENTINA

PostPosted: Tue Jul 03, 2007 1:27 am    Post subject: Reply with quote

Frank, thank you for your answers.
Maybe i should be focused in a basic workflow. From A to B, from B to C or D, etc.. There are so many approaches to do it.

Thank you!

Diego.
Back to top
View user's profile Visit poster's website
Guerino1
Senior Itiler


Joined: Jan 01, 2006
Posts: 500
Location: New Jersey

PostPosted: Sat Jul 14, 2007 11:51 am    Post subject: Reply with quote

Hi Berto,

You're right, there are many different approaches. I personally like the "lifecycle" approach. The more details you capture about a trackable entity's lifecycle, the better knowledge you will built, about that item, over time. For example, I can track details about "one specific Problem", from the time it is logged until the time it is deleted from the tracking system (you may never delete it to keep history for knowledge retention).

The more consistent your processes are about tracking the same details on every "like" trackable item, the more knowledge you will build on the entire repository of that trackable item type. For example, the more consistent you are about how you track details about "every Problem", the more powerful your knowledge base will become, across all records of that specific type (Problems in this case).

Anyhow, I'm glad I could be of assistance.

Best of luck in your efforts.

Frank Guerino, CEO
TraverseIT
On-Demand ITIL
Back to top
View user's profile Send e-mail Visit poster's website
Display posts from previous:   
Post new topic   Reply to topic    ITIL Forum Index -> Problem Management All times are GMT + 10 Hours
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum

Powered by phpBB 2.0.8 © 2001 phpBB Group
phpBB port v2.1 based on Tom Nitzschner's phpbb2.0.6 upgraded to phpBB 2.0.4 standalone was developed and tested by:
ArtificialIntel, ChatServ, mikem,
sixonetonoffun and Paul Laudanski (aka Zhen-Xjell).

Version 2.1 by Nuke Cops 2003 http://www.nukecops.com

Forums ©

 

Logos/trademarks property of respective owner. Comments property of poster. Rest 2004 Itil Community for Service Management & Foundation Certification. SV
Site source copyright (c)2003, and is Free Software under the GNU / GPL licence. All Rights Are Reserved.