Twitter
YouTube
Instagram

Author Archives: Ben

How to Develop a Project Scope

We are often approached by companies who are looking for assistance in developing a list of requirements for a current project.  While we are always happy to assist with such activities we recognize some companies would like to have a format for their internal use.  Usually smaller projects find a traditional scope of requirements to be bureaucratic and burdensome.  When this is the case there are always a couple of basic techniques which can be utilized to develop an outline for a project. First are the five Why’s and two H’s.  Who, What, When, Where, Why, How, and How Many The second technique is a listing of the Conditions of Satisfaction. Simply list all the conditions of satisfaction for the project.  Some of the items that you list may be duplicates of the five Why’s and two H’s but you will notice new requirements will become apparent as well. These two simple techniques will allow the development of criteria for a project when there is no established corporate format.

Standardized Work

Recently we received a question about Standardized Work.  What exactly is Standardized Work?  In a nutshell Standardized Work is like work instructions on steroids.  It includes very specific details on how the work is performed, and it is usually developed with takt times and an understanding of machines and tooling capacity all rolled together.  Standardized Work is commonly used in Toyoda production systems.  They are an excellent tool for planning, load balancing,  and insuring smooth product launches.  Their weakness would show in highly dynamic and changing processes due to the necessary resources to properly develop these tools.  When they are utilized properly they offer a systematic approach to many industrial engineering philosophies which are often otherwise overlooked.

3D Printing Parts

The Value of Budgetary Numbers

When looking at machine improvements we often ask as to whether the customer has developed any budgetary numbers for the project at hand.  Sometimes customers are hesitant to provide any numbers as there may be a perception that somehow this will provide unbiased quotes or provide a competitive advantage.

The problem with this train of thought is the multitude of solutions which are often present with technology today.  If a customer is thinking they can solve a problem for $200 yet asking for the best solution possible, it is conceivable the supplier is thinking $20,000, and that is a problem.

Recently a customer asked for a range of solutions as a starting point of discussion.  The results were solutions ranging from $2,000 to $50,000.  The starting point covered all the customer’s basic requirements and a full range of solutions from relatively simple to highly automated.

One of the problems of not having the budgetary number is customers rarely anticipate the multitude of ways their particular issues may be addressed.  When confronted with these options paralysis can set in.  Further the customer is inadvertently driving up cost through the increased workload required when suppliers then develop a myriad of options for the customer.

The Deception of Process Capability Numbers

bell curveDuring a product launch or product quality planning process, it’s often quite common to look at process capability numbers and roll those into relevant corresponding documents.

The intent in this process is genuine; however it’s frequent that a failure to comply with product specifications after the launch process will occur regardless, especially with new designs or processes.

Manufacturers with low process capability numbers in given areas are typically very attuned to those numbers and inherently develop compensating improvements to ensure nonconforming product does not get out the door.

The greater deception actually occurs around the areas where the process shows high levels of capability.  Frequently some failure mode occurs which is adjacent to these highly capable processes.

For example let’s say a grinding process has very high CPK values.  This is a great, however the unanticipated concerns which are often not defined on process documents are typically the failure modes seen by the customer.  It’s usually the items that are difficult to anticipate which often rear their head as the source of a concern. And because they are difficult to anticipate they never end up on the product quality planning documents, nor design FMEA’s, or any other proactive format utilized to eliminate these concerns.  This becomes a vicious circle in organizations that dump excessive resources into the planning process with the hopes of creating the perfect launch.  To make matters worse these companies tend to ignore the potential of downstream problems because they proactively and diligently applied resources at the front of the development cycle.

So next you might ask what is the solution?

Shift the less productive time and resources spent at the front of the process to a higher frequency of inspections and auditing.

Let’s be clear.  I am not endorsing the elimination of a proactive planning and development process.  However as these planning and statistical concepts have matured many have assumed inspections and audits could be eliminated and there lies a problem.

Let me give you an example.  During plant visits to automotive assembly plants I have noticed distinct differences in the levels of inspection and auditing directed where no apparent quality concerns existed. Other companies plants however would take a high tech approach based upon capabilities and statistics to insure their product quality.

The clear winner in terms of product quality was the plant with the added layer of low tech inspections and audits.  Ironically this plant had all the same advanced analysis and statistical technologies but they did not depend on these techniques to insure product quality.  When a failure eventually appeared this company caught the problem in their plant before it got to their customer.