FAST Diagrams and Value Engineering - Tips...

• Little is known about the value contribution of each component / subassembly / element of a system 

• After the team working on the project has had time to study the system / product / service 

• Start with the overall system objective to the far left

• List the inputs to the system at the far right

Integrated 
Solutions

Call Today:
1-877-HOWNWHY

• Ask "How" questions proceeding from right to left, continue until you hit a point where you have to take a physical action - such as turn on a switch.  This will indicate you have gone deep enough.  All functions need to be described using a Verb and a Noun.  Sometimes a qualifying / clarifying word may be required - but Verb Noun arrangement should be strictly followed. 

• Once "How" questions are completed, start from the right and begin asking "Why" questions.  You may find there are disconnects on a given path, as you ask the how and why questions.  These disconnects need to be fixed, then your FAST Diagram is a sound one. 

• You may find some functions being performed all the time, put them on the side lines

• As you study the system, you may find some functions cannot be identified with anything on a given path.  These may be unwanted functions being performed as part of system operation - and represent the first opportunity (lowest hanging fruit!) for cost avoidance

• Classify the functions as Primary, Secondary, Required Secondary, or Unwanted

• Avoid the temptation to rationalize every function 

• Transfer functions to the Cost Function Value Matrix

• Identify the lowest Value Elements, and also compute the $ being spent on Unwanted, and
  Secondary Functions.  These become candidates for cost avoidance

• Eliminate or combine functions on certain elements to improve value proposition 

• How soon does your manager / boss need it done 

TEAM 2000

Call:
1-877-HOWNWHY

• Make a quick assessment of how much savings can you generate - working on a $100,000 product and saving just 10% will yield more than working on a $10,000 project and saving 50%

• The one time savings may be a misleading way to think of savings - better utilize savings over the anticipated lifetime of the product / system

• Make sure Management is committed and will support you in deployment of changes you may recommend.  Else it becomes an academic exercise. 

• When building FAST and CFV Matrix early during the design phases, it is easy to get carried away with infatuation of the product, or keep adding features and functions to the product.  One way to prevent this is to bench mark what the customer has used in the past, that will provide for a baseline - this is the minimum you will need to deliver.