1 / 25

How To Manage Engineering Know-How

How To Manage Engineering Know-How. Jeff Moffa Emergent Systems. Agenda. ‘Strategic’ Five Keys Case Study Active ‘Packet’ Integration. ‘Top of the Mountain’. ‘Working the Earth’. Tactical KM vs. Strategic KM. Tactical KM LL and BP DBs XLS driven process

booth
Télécharger la présentation

How To Manage Engineering Know-How

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. 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. 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

  4. Tacit Training Value Quantity Templates Rules / Heuristics Lean Knowledge Processes

  5. Five Keys to Managing Know-How • Knowledge Reconstitution • High Signal to Noise • Context Ambiguity • Orthogonality of Engineering Knowledge • The KM Virtuous Cycle

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

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

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

  9. 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

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

  11. Key 5: The EKM Virtuous Cycle • Typical Roles played in EKM • Expert • Engineer • Manager • Email (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

  12. 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

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

  14. ‘Leads’ Communities of Practice ‘CoPAuthors’ OEM Process Overview Manage Packets of Know-How Structured Packets of Know-How MDS Ergonomics Fastener Final WEB Paint Body Stamping Others WEB WEB

  15. Add/Modify Content ‘Leads’ Communities of Practice MDS Ergonomics Fastener Final Assy WEB Paint Body Stamping Others… WEB WEB ‘CoPAuthors’ Structured Packets of Know-How Virtual Evaluation Requirements eMPl Confm / CL eMPl eMPl ‘Simulation Engineer’ Real Time Status

  16. SBOP Add/Modify Content Virtual Evaluation ‘Leads’ Requirements Communities of Practice eMPl Conformance MDS Ergonomics eMPl Fastener Final Assy eMPl WEB Paint Body Stamping Others… ‘Simulation Engineer’ WEB WEB Real Time Status ‘CoPAuthors’ SBoP SBoP ‘SBoPAuthors’ WEB SBoP Requirements ‘PD, VO Engineers’ Structured Packets of Know-How

  17. SBOP Program Tracking - Actual SBoP SBoP ‘SBoPAuthors’ WEB WEB WEB Requirements ‘PD, VO Engineers’ Add/Modify Content Virtual Evaluation ‘Leads’ Requirements Communities of Practice eMPl Conformance MDS Ergonomics eMPl Fastener Final Assy eMPl WEB Paint Body Stamping Others… ‘Simulation Engineer’ WEB WEB Real Time Status ‘CoPAuthors’ ‘CL Creator’ WEB SBoP ‘CL Editor’ ‘Egr/Mgr’ Requirements Structured Packets of Know-How

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

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

  20. Catia, KW Auto-Created DynamicParameters/Expressions Auto-CreatedDynamic RuleChecks/Relations CAD Connection Dynamic Knowledge Base- Formalization & Acquisition Design & Report

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

  22. Demo– Catia Know-How Packet Integration

  23. 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

  24. Thank You Please feel free to contact me: Jeff Moffa jmoffa@emergentsys.com

More Related