From the Archives of a Common Sensei Volume 28: ENGINEERING CHANGE PROCEDURE FOR LOCAL PARTS (Domestically Purchased Parts)


During the early days (1990’s) of Toyota Industrial Equipment (TIEM) in the US, we had to give consideration to many different processes as we developed the manufacturing operations. In my previous blog postings, I have tried to describe in (short form) how we went about many of these operational developments.

This article is another example of an important (critical) process – Engineering Change for Local (Domestically Purchased Parts). In the next two blogs (Volume 29 and 30) I will present Engineering Change Procedure for Import Parts (Interchangeable) and (Not Interchangeable). Frankly, the handwritten original examples are too big to display at the same time, so I split them into three volumes. Some of you might be more concerned with an engineering change procedure for domestic parts and some might be more concerned with imported parts. The three articles in Blog 28, 29, and 30 might be of help by showing how we managed engineering changes at TIEM.

In the example supplied here for Domestically Purchased Parts, it is noted that during those early days of the TIEM startup (1989+) the engineering was done by the TIEM parent company (TAL) and delivered to the TIEM operation (Domestic Company) in Columbus, Indiana. From that point, the process example tracks through the Quality Section, Production Section, Material Control Section, Purchasing Section, and on to the Vendor. In the mid-1990’s a substantial portion of product engineering was a joint effort by the local facility and the parent company in Japan. In previous blogs, I have explained how we encouraged customer, plant associates, and managers to work with Engineering to create improvements in quality, cost, convenience, service needs, etc.

In the example provided here, it is obvious that even in the 1990’s much of the process involved manual or semi-manual operational steps, as well as integrated into the ordering system. To control product quality and waste while introducing changes, it did involve significant manual intervention! Again, this example and those in the next two blog postings are intended only as examples from which you may be able to gain some ideas.

For More Information or help with your transformation effort, contact us at http://www.per-strat.com

From the Archives of a Common Sensei Volume 25: PROBLEM SOLVING CONCEPT AS USED IN EARLY US TOYOTA OPERATIONS


In continuation of these blog postings (From the Archives of a Common Sensei), volume 25 discusses how we approached Problem Solving during those early days (early 1990’s) while developing Toyota Industrial Equipment. The documents included here are pre-computerization and clearly demonstrate we didn’t need everything computerized – especially problem solving!  The attached documents are in their rough condition but, are actual examples of a systematic method used for problem resolution, particularly in the following areas:

On the document entitled Procedure for Problem Solving, we have provided the procedural flow guideline for problem solving, especially for Managers and other Leaders (of course in conjunction with all those affected).  On the slide marked Problem Solving Activity, we provide a look at the process used to evaluate and resolve problems and advance opportunities.

Additional documents included provide examples of the Kaizen Activity Report (before and after changes), the Kaizen Report Format, The Bi-Weekly Report of Activity, and the Implementation Schedule for Policy Management.  The Implementation Schedule for Policy Management is used to track the various tasks against established policies of Cost, Quality, Delivery, Safety, and Morale. Additionally, it keeps track of the method, target dates, person/in charge, and lays it out in a schedule for tracking simplification.

The documents in this volume of From the Archives of a Common Sensei we feel it is essential to stress that although the documents included here are not the prettiest, they are valued examples that can show you the basics of value-added problem solving (resolution).  Standardized use of these documents (or similar) will aid in the development of a true problem solving (love those opportunities) culture.  As your organization matures, it will become stronger because of standardized problem solving as described here.

For More Information or help with your transformation effort, contact us at http://www.per-strat.com