Supply Chain Excellence [Electronic resources] : A Handbook for Dramatic Improvement Using the SCOR Model نسخه متنی

اینجــــا یک کتابخانه دیجیتالی است

با بیش از 100000 منبع الکترونیکی رایگان به زبان فارسی ، عربی و انگلیسی

Supply Chain Excellence [Electronic resources] : A Handbook for Dramatic Improvement Using the SCOR Model - نسخه متنی

Peter Bolstorff, Robert Rosenbaum

| نمايش فراداده ، افزودن یک نقد و بررسی
افزودن به کتابخانه شخصی
ارسال به دوستان
جستجو در متن کتاب
بیشتر
تنظیمات قلم

فونت

اندازه قلم

+ - پیش فرض

حالت نمایش

روز نیمروز شب
جستجو در لغت نامه
بیشتر
توضیحات
افزودن یادداشت جدید





Planning For Disconnect Analysis

The search for understanding of disconnects in material flow offers content value as well as an opportunity for important leaps in change management. The content value is the process of identifying and valuing supply chain improvement opportunities, using established problem-solving techniques. The change-management value is taking advantage of the opportunity to include more people in the design process. The brainstorming activities of this work can engage as many as fifty people. The agenda for Day Two focuses on finishing the material flow summary, updating the geographic maps, and planning for the disconnect analysis.

In planning for the disconnect analysis, first identify the brainstorming team—a group that includes design team members plus other experts in the various material flow locations and lanes who know where problems exist. Second, assemble the brainstorm meeting agenda and invitation letter.

Finally, assign owners to complete any remaining homework on the material flow performance summary.

The brainstorm meeting agenda should include:



A one-hour premeeting for those who have not participated in SCOR education, to familiarize them with SCORcard gap analysis, review of AS IS material flow maps, and review of the AS IS material flow performance summary



Brainstorming individual disconnects noting location and lane of impact



Arranging the disconnects into groups with similar causes and clearly defining problem statements for each group



Reviewing problem statements with entire team



Documenting



/ 135