- Количество слайдов: 25
Engineering Change Management System for Lincoln Foodservice Products By Duane Yoder October 12, 2006 MSE 7000 Professor Steve Dusseau
Background Information • Educational background • • • BS Physics BS Electrical Engineering Work Experiences • • • Four years of engineering for Gen Tel of Indiana Twenty-three years of engineering experience in a manufacturing company (Lincoln FP) Seventeen years in engineering management
Why this project of Change Management? • • My current role on the QAD MFG/PRO ERP implementation team is the PCC Module and Item records I currently manage the CAD administration and PDMLink implementation It is one of the hottest issues at Lincoln The ECO process needs to become Lean
Product Lifecycle Management • • Every product goes through a lifecycle The primary phases of a lifecycle are • • Concept Design Release Between each phase is a gate • • Concept Approval Design Approval
Lifecycle Attributes and Operations Phase-Specific Operations Phase Attributes • Submit • Demote • Roles • Access Rules • Criteria for Promotion Detail Design Approval Gate Attributes Concept Approval Concept Development Release Gate-Specific Operations • Promote • Deny
Basic Lifecycle Affects and Effects Demote Submit Promote Deny Design Approval Concept Approval Detail Design Concept Development Release Promote
Typical Engineering Change Process
What is an Engineering Change?
What is an Engineering Change? • Change to the Product Structure (BOM) • • • Change to the Part Itself • • • Adding or deleting a part Changing the quantity of parts in an assembly Change of specifications Change of approved source Change of Routing (Steps of Assembly) • Change of processes or sequences
What does an Engineering Change Do? • Changes one or more of the four “F”s • • • Form Fit Function Fee The communication of the change is called an ECO, PCO, or ECN
What must the ECO Do? • • • Tell what to change Show to make the change Tell when to make the change (effectivity) Tell who makes the change (define tasks) Show where the change is at (documentation) Tell why the change is made (reasons)
Where is the biggest gap in the Process? • Effectivity of Change • • Engineering uses revision letters Operations and Manufacturing use dates • • Do not use before, do not use after Other methods • • Use to depletion Serial number Customer Number Lot Number
Where is Effectivity Managed at Lincoln? • Engineering - CAD PDMLink Database • • • Documentation revision control Check-in and Checkout Promote and Demote Operations and Manufacturing - MFG/PRO ERP Database • Implementation by dates • Balance inventory • Meet customer demands
One Database or Two? • Engineering - PDMLink • • • Supports more than just engineering documentation Change management meets CMII requirements Configurable workflow and roles for matrix organization Managed locally Operations/Manufacturing - MFG/PRO • • Operations based for date effectivity Strong support of operations and business
The Impact of the Gap • • • Engineering documentation remains in queue while new changes are being implemented. Fit becomes an issue when new changes are implemented before previous changes are in production. Historical Engineering records BOMs do not synchronize with production by dates.
The Solution - PDMLink for ECO Process
PCC for the EPR PCO Implementation
Bridge the Gap between PDMLink & PCC To be automated at a later date As Designed As Manufactured
MFG/PRO and PCC • • • The incorporation and implementation of changes meet operation needs Historical records of “As Manufactured” with revision history is always available Full ERP functionality is maintained with Corporate Office
Conclusion: • • • Where one database is preferred the ability to take advantage of the benefits of both is the next best solution. Work towards automation and data sharing between the Oracle and Progressive databases. Design the workflow of PDMLink to follow Lean principles.
Questions & Answers ?
References: • • • Windchill PDMLink Users Guide Donald N Frank, Configuration Mangement in Aerospace and Defense Microsoft Corporation