Your SlideShare is downloading. ×
Knowledge management as a support to enterprise solution - EPS
Upcoming SlideShare
Loading in...5

Thanks for flagging this SlideShare!

Oops! An error has occurred.


Saving this for later?

Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime - even offline.

Text the download link to your phone

Standard text messaging rates apply

Knowledge management as a support to enterprise solution - EPS


Published on

Knowledge management as a support to enterprise solution - Enterprise Planning System

Knowledge management as a support to enterprise solution - Enterprise Planning System

Published in: Education, Business

  • Be the first to comment

  • Be the first to like this

No Downloads
Total Views
On Slideshare
From Embeds
Number of Embeds
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

No notes for slide


  • 1. Knowledge Management as a support to enterprise solution Presented by: Neha Kumar (A029) Rashi Kapur (A039) Sonal Rajadhyax (A050) Tarannoom Rehmani (A053) Yuvraj Tandon (A059)
  • 2. Types of Knowledge Tacit Knowledge – Knowledge that is available with people. It is not recorded or available as a hard copy. It is developed out of personal and professional experience.  Explicit Knowledge – Knowledge that is available in a recorded format. Egs.) Company guidebooks, policy documentations etc. 
  • 3. What is KMS? It is an ERP system that helps to collect, collate and present knowledge in an appropriate manner  It is an ERP2 implementation  KMS assists organizations to intelligibly management knowledge that is generated, using the right technology 
  • 4. Why KMS? Provides strategic advantage  Helps to reduce investment in time and money to find solutions  Provides a value addition for customer by delivering faster and better outcomes in same price  Ensures higher efficiency, better insights and improvement in products and services 
  • 5. Company Profile MNC providing information technology, consulting and BPO services  Customers include banking, insurance, healthcare, educa tion, product engineering services, energy and utilities and independent software vendors. 
  • 6. Need for KMS in Company Company is an IT service based company  Success of organization depends upon effective and efficient delivery of customer expectations  Different technologies used in different projects should be leveraged across the organization  Best practices and management techniques used across projects should be leveraged 
  • 7. Requirement Analysis AS IS Scenario:  Basic Structure in the organization – Organization -> Business Unit ->Accounts >Individual project(s) Current information flow is only limited to within Accounts (SILOS effect)  Technologies, best practices and knowledge used in other projects was not available throughout the organization 
  • 8. Requirement Analysis TO BE Scenario:  Removal of SILOS effect  Free flow of knowledge within the organization
  • 9. Business Solutions Internally developed software to support KMS  Teams were associated with development and maintenance of KMS database, user interface and to manage scalability and flexibility. 
  • 10. Implementation and Feasibility Strategy  Understanding the company’s structure i.e. Organization -> Business Unit ->Accounts >Individual project(s) Understanding potential knowledge from each link in the structure  Determining the required resources to be applied in the KMS implementation  Change Management 
  • 11. Planning for Implementation Adopted Parallel and Big Bang approach  Change Management to be achieved through heavy branding and advertising of new look and feel  Implementation to be released through Big Bang  Parallel Approach adopted for easier transition of employees to use new KMS 
  • 12. Roles and Responsibilities of Stakeholders Major stakeholders in organization KMS – Employees  Employees responsible to create CoP (Communities of Practice)  Different Roles and Responsibilities in CoP:   Owner – Identification of team members, SPOC for CoP, Drives CoP’s activity plan  Sponsor – Member of Senior Leadership, Forms vision of CoP, taps into knowledge pool of CoP for wealth creation  Web Researchers – Search for relevant criteria, Create knowledge repositories for CoP  Content Creators – Create and Synthesize content for CoP to be shared with organization  Members – Participants in all CoP activities, Active contributors
  • 13. Management Challenges Management wished to implement a KMS  Challenges faced by Management:  Convincing BU heads to share knowledge Convince clients of their data integrity
  • 14. Technical Challenges Authorization and Authentication to use KMS  Data and Knowledge access controls  Hardware requirements – number of dedicated servers, network considerations, scalability etc  Constant changes to support new features and maintenance activities 
  • 15. People Challenges Acceptance of new culture of knowledge sharing  Changing outlook of employees to understand benefits of sharing knowledge across the whole organization 
  • 16. IT Infrastructure Dedicated KMS Servers  KMS data entry servers  Authentication and Authorization Controls  Access Level controls within the CoP 
  • 17. SWOT Analysis STRENGTHS - Builds Talent - Essential Business Asset - Combining of Tacit and Explicit knowledge OPPORTUNITIES - Quality Maximization and Cost Minimization - Application of unique knowledge to obtain market advantage WEAKNESS - Knowledge is abstract - Knowledge cannot be measured - Difficult to assess THREATS - Creation of shield to protect knowledge database -Improvisation on techniques to share information - Knowledge Security
  • 18. PEST Analysis POLITICAL - Customer Legalities, Rules and Regulations w.r.t knowledge sharing SOCIAL - Co-operation of management, customers and employees - Change in outlook to use KMS ECONOMIC - Monetary value attached to knowledge by customer - Knowledge is a valued asset TECHNICAL - Sustenance of knowledge in different formats - Scalability - Real time knowledge sharing - Usability should be easy
  • 19. Future Scope Access through different mediums like mobile phones  Stringent and effective checks so irrelevant data is not uploaded  Streamlined and Easier process to upload knowledge  Complete removal of BU and Account SILOS  Removal of Data Redundancy  Implementation of interesting ways to keep employees enthused to use KMS 
  • 20. Conclusion KMS implementation bridged gaps of knowledge in organization at BU, account and individual project level  Information about new technologies and techniques now shared more effectively  Not full blown implementation, but current KMS implementation is already successful 
  • 21. References ntroduction_to_Knowledge_Managem ent.html  ws/pdfs/A%20Knowledge%20Manage ment%20System%20%20A%20Discourse.pdf  Organization’s intranet: 