1 / 17

Knowledge Management ver. 2.0

Knowledge Management ver. 2.0. Presented by Jon Wright, Manager ResNet Services. The background info. A bit about myself and Purdue…. 38,712 student enrollment (West Laff.) 69,098 system wide enrollment ~11,300 ResNet subscribers ~ 95% Windows users ResNet Desk staffed by ~30 students.

rusti
Download Presentation

Knowledge Management ver. 2.0

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Knowledge Management ver. 2.0 Presented by Jon Wright, Manager ResNet Services

  2. The background info A bit about myself and Purdue… 38,712 student enrollment (West Laff.) 69,098 system wide enrollment ~11,300 ResNet subscribers ~ 95% Windows users ResNet Desk staffed by ~30 students

  3. Responsibilities PURDUE UNIVERSITY RESIDENCES

  4. Objectives for today • Discuss the thought process of redesigning your Knowledge Base • Share some of the issues that were encountered along the way • Demonstration of key components and functionality

  5. Knowledge Management Our situation… Our current solution… Our task…

  6. Overview Old KB vs. new KB • What was wrong with the old KB? • What items/functionality did we want to keep? • How could we benefit other groups/departments?

  7. Old Knowledge Base

  8. New Knowledge Base

  9. How did we get there? • Continual meeting of the minds • Feature requests keep on coming • Deliverables, test accounts

  10. New ideas • Concept of roles, services, owners, and groups • KB user accounts have associated service memberships and groups • Role development helps in providing parent/child group permissions

  11. Image management • Images stored internally on server • Uploaded to KB, categorized • Image must be approved before use

  12. Maintaining the Knowledge • Article reviewing policy • Constant ongoing process • Can’t set it and forget it.

  13. Some Stats

  14. Demonstration

  15. Conclusion • Revising KB requires planning • In our case, total costs were low • Continually improve content and features • Promote and gather support

  16. Questions Questions? Links: ResNet KB http://kb.resnet.purdue.edu ITaP KB http://help.itap.purdue.edu

  17. Contact info/evaluations Contact info: jdwright@purdue.edu Evaluate me and this presentation at: www.resnetsymposium.org/resnet2007 Thanks to: Thomas Bunton, Paula Mezo, Matthew Rogers, Ty Shuff, and Aaron Capriglione 17

More Related