Presentation is loading. Please wait.

Presentation is loading. Please wait.

How To Manage Engineering Know-How Jeff Moffa Emergent Systems.

Similar presentations


Presentation on theme: "How To Manage Engineering Know-How Jeff Moffa Emergent Systems."— Presentation transcript:

1 How To Manage Engineering Know-How Jeff Moffa Emergent Systems

2 Agenda ‘Strategic’ Five Keys Case Study Active ‘Packet’ Integration ‘Top of the Mountain’ ‘Working the Earth’

3

4 Tactical KM vs. Strategic KM Tactical KM LL and BP DBs XLS driven process Online Single Dedicated Web Repositories Document Vaulting (PDM approach) Strategic KM Create, Retain and Deploy Technical Know-How Globally All Know-How/ Common Approach / All Organizations Culture of Knowledge Management

5 Tacit Training Rules / Heuristics Lean Knowledge Processes Templates Value Quantity

6 Five Keys to Managing Know-How 1. Knowledge Reconstitution 2. High Signal to Noise 3. Context Ambiguity 4. Orthogonality of Engineering Knowledge 5. The KM Virtuous Cycle

7 Key 1: Reconstitution Dynamic Checklists Any Application Single Knowledge Representation eLearning Multi-CAD Direct Web

8 Structure Promotes Connectivity to the engineering process and, therefore, Re-Use Tacit Explicit Un-Structured Structured Value Potential More Less Experience Document Data Base Structured ‘Packet of Know-How’

9 Key 2: Signal To Noise Traditional Bucket Approach: S:N of KM Must Be Very High! LL, BP, Template

10 Key 3: Context Ambiguity Knowledge Will Conflict Context will introduce ambiguity KM solutions: Priority / Severity– rationalize conflicts Cross Reference and relational sequences across static conflicts. Meta management of references. Context Discussion linked to Know-How Context Histories linked to Know-How

11 Key 4: Organizational Orthogonality Product/Function Specific Knowledge Process/Domain Specific Knowledge Hood Fender Stamping Materials Assembly Dynamic cross linking of knowledge!

12 Key 5: The EKM Virtuous Cycle Typical Roles played in EKM Expert Engineer Manager (process and technology– process becomes transparent, but is imperative) Metcalfe’s Law: v=xn2 Virtuous Cycle- is achieved when all perspectives see positive net present value. The sum is irrelevant. Culture of Knowledge Management is a byproduct of the Virtuous Cycle; not a goal in itself

13 Case Study- US Automotive OEM Manufacturing Previous State- 2 Years Ago Highly Fragmented ‘Knowledge’ Repositories Doc Vaults PDFs (manuals, rules) Dedicated Websites Duplicated XLS based tracking No Process for Managing Know-How Current State- Today Highly Structured Packets of Know-How Highly Integrated into Business Processes Virtuous Cycle Achieved Emerging Culture of Knowledge Management

14 Universal Knowledge Bus: Standards, Requirements, Lessons Learned, Methods Application X Lean Knowledge Processes Multi-Person, Multi-Location, Real-time Dynamic Checklists Other Digital Verifications Design, Process Guides/Publication Conformance Status Reports CAD/Product Manufacturing Sim/Planning

15 Communities of Practice WE B Structured Packets of Know-How MDSErgonomics FastenerFinal PaintBody StampingOthers WE B ‘CoP Authors’ ‘Leads’ Manage Packets of Know-How OEM Process Overview

16 WE B MDSErgonomics FastenerFinal Assy PaintBody StampingOthers… Communities of Practice WE B ‘CoP Authors’ ‘Leads’ Add/Modify Content eM Pl Virtual Evaluation eM Pl Confm / CL Requirements ‘Simulation Engineer’ Structured Packets of Know-How Real Time Status eM Pl

17 Virtual Evaluation eM Pl Real Time Status Conformance Requirements ‘Simulation Engineer ’ eM Pl SBOP WE B SBoP Requirements ‘SBoP Authors’ SBoP ‘PD, VO Engineers’ SBoP WE B MDSErgonomics FastenerFinal Assy PaintBody StampingOthers… Communities of Practice WE B ‘CoP Authors’ ‘Leads’ Add/Modify Content Structured Packets of Know-How

18 eM Pl Virtual Evaluation eM Pl Real Time Status Conformance Requirements ‘Simulation Engineer’ eM Pl SBOP WE B SBoP Requirements ‘SBoP Authors’ ‘PD, VO Engineers’ SBoP WE B MDSErgonomics FastenerFinal Assy PaintBody StampingOthers… Communities of Practice WE B ‘CoP Authors’ ‘Leads’ Add/Modify Content Program Tracking - Actual WE B ‘CL Creator’ WE B ‘CL Editor’ ‘Egr/Mgr’ Structured Packets of Know-How Requirements

19 Current State Metrics 1 Strategic Process for Collecting and Refining Packets of Know-How Unique Packets of Know-How and Growing Single Program with 20,000+ discrete ‘trackable’ application of Packets of Know-How unique engineering users 4 Distinct Business Processes Reusing Content

20 Power of the ‘Packet’ - Structure allows Active and Dynamic Integration

21 CAD Connection Dynamic Knowledge Base- Dynamic Knowledge Base- Formalization & Acquisition Design & Report Catia, KW Auto-Created Dynamic Parameters /Expressions Auto-Created Dynamic Rule Checks/Relations Auto-Created Dynamic Rule Checks/Relations

22 Manufacturing App Mfg Planning & Simulation Structured Packets of Know-How Structured Packets of Know-How Formalization & Acquisition Design & Report Auto-Created Dynamic Checklists at Each Process Lean Requirements Conformance Information Feedback- Closeloop

23 Demo– Catia Know-How Packet Integration

24 Managed Know-How: Current Know-How locked in documents/templates Know-How lost as employees leave Know-How confined to individuals Know-How applied is dependent on individual and inconsistent Know-How is ‘Searched For’– Ad Hoc Process Future Managed Structured Packets of Know-How Know-How Captured, Retained Know-How Shared across organizations Know-How applied is independent of the individual and is consistent Know-How is ‘Delivered’, ‘Integrated’ – Lean Knowledge Process

25 Thank You Please feel free to contact me: Jeff Moffa


Download ppt "How To Manage Engineering Know-How Jeff Moffa Emergent Systems."

Similar presentations


Ads by Google