This document discusses knowledge management content processing in a Microsoft SharePoint environment. It outlines challenges with locating, organizing, and sharing knowledge across different areas and locations. A knowledge flow analysis identified gaps. The presentation introduces knowledge management principles and frameworks, and proposes a content processing system to classify historical documents using an automated taxonomy. This would centralize product technical knowledge in a single location, eliminating manual work and saving an estimated $2.4 million. The system would use Kapow software to automate content migration.

1. Knowledge Management Content Processing
in a Microsoft SharePoint Environment
May 21, 2014
#Kapownow

2. Our Speakers
Adam Duckworth
Associate Director, Business
Consulting, MMD Knowledge
Management COE
2
Douglas Arnold
Director, Account Manager of Pipeline and
Knowledge Management, MMD
Information Technology

3. Challenge - The Case for Change
Difficult to locate knowledge.
No common defined standards.
Organization of knowledge varies by area/location.
Technical packages can take weeks to months to assemble.
Inconsistent quality of information.
Difficult to identify current version.
No common repositories.
Knowledge stored locally.
Very limited access to key content.
Moving knowledge between repositories is low-value work.
Lack of context & rationale.
Knowledge Flow Analysis VOC
Identified gaps in the flow of
small molecule product
technical knowledge.
3
“In manufacturing, we make two products:
clinical/commercial supplies and knowledge”
Process Step
Knowledge
Needed
Created By
Used By
Explicit or
Tacit
Where is it
Flow
Impact
Gap /
Opportunity
Explicit
Document
Repository
None
Tacit
Partially
captured on RA
Rationale not
consistently
captured
B
Safe operating
conditions
Safety Eng API Engineering Explicit
Document
Repository
Not sure which is
latest version
C
Summary of lab
development
Analytical
Registration
Team
Explicit
Local team work
space
No standard
repository
D
Performance of
similar product
Manufacturing Development Tacit
Local, at
manufacturing
sites
Limited access to
SMEs and no
standard
expectations for
reporting
E
Knowledge on
powder processing
Pharm
Engineering,
Manufacturing
Manufacturing Tacit Unknown
No formal SME
listing identified
A
Early Risk
Assessment
API Engineering
Pharm
Engineering

4. Introduction to Knowledge Management
 What is Knowledge?
– Knowledge is what is known in a particular field, such as facts, truths,
principles and information. It is information in action.
 What is Knowledge Management (KM)?
– KM is the collection of systematic processes and approaches to enable
information and knowledge to grow, flow and create value.
 Why is KM important?
– Storing, organizing and sharing knowledge helps employees develop,
transfer and execute processes and methods, as well as enhance decision
making and strategic planning.
4
“The basic economic resource – the means of production –
is no longer capital, nor natural resources, nor labor. It is
and will be knowledge.”
‐ Peter Drucker

5. Principles & Frameworks
5
credit: APQC
credit: APQC

6. Product Sites
Knowledge Management Capability
Landing Page• Content mgmt. for Product
Technical Knowledge - primarily
Unstructured Content.
• SharePoint Enhanced (SPE),
long-term storage, advanced
search and filtering functionality.
• Documents, links, MIDAS
integration and non-document
knowledge
• Templates
• Broad, compliant access
• Sponsorship, stewardship and
governance
• TAXONOMY
• A single source for product
technical knowledge - if it's not
there, it doesn't exist
6

7. Align around taxonomy to classify small
molecule product technical knowledge
across the process lifecycle
Process Lifecycle Taxonomy
7

8. Content Processing System
 Characterize and process documents from repositories like SharePoint
Team spaces and file shares
• Highlights: duplicate file remediation, documents and links, PDF
source characterization, optional manual overrides.
 Based on a defined taxonomy, apply intelligent metadata tags (auto-
classification) which allow users to easily locate and search for knowledge
assets
8
 Enable the reclassification
of content as taxonomy and
classification rules evolve
over time
Classifying 2,000,000 historical documents manually . . .
10 knowledgeable people three years

9. 9
Content Processing System - Logical
Architecture and Process

10. Summary
 Authoritative “single source of truth” content centralized
 Knowledge workers no longer waste time finding or re-
creating information
 Eliminate intense manual resources for processing,
classifying and tagging historical content ($2.4M savings)
 Expected payback expected within one and a half years
 Recommendations:
– Team up business and IT
– A journey with multiple stages
– Don’t over engineer
– Automate
10
Combining manufacturing technical knowledge into a single
location will have far-reaching effects and significant
synergies for product development

11. Kapow for Automating Content Migration
11
Kapow

12. June 25, 2015 External © 2013 Kapow Software12
Simple, Visual,
Workflow Design
Access to Any Data
Source
Agile Deployment
Model
Built for the
Enterprise
Self-Service
Insight
Kapow Enterprise

13. Kapow
13
Organizations rely on our platform to make smarter decisions,
automate processes and drive better outcomes faster

14. Q + A
14

15. Thank you for your time during this
KapowNow! live webinar
Kapowsoftware.com/company/kapownow.php
15