CR is principally a process that attempts to lower the costs of producing and supporting a product (a product is defined as all goods, services, processes and knowledge sold)1.  But, when you think about it… what it really means is that you want to maximize the revenue gap between the total cost of consumer ownership (i.e., the purchase price plus on-going related consumer and service costs that the consumer shells out over the product's useful life and end-of-life) and the total cost of producer outlay (i.e., the cost per unit that the producer incurs during defining, developing, testing, producing marketing, distributing and supporting the product over it's useful life and end-of-life).

Reducing the total cost of producer outlay would allow (1) an increase in revenue or (2) maintaining revenue while also lowering the consumer costs.  Sometimes increasing the revenue gap can be achieved by increasing the sales price or charging more for or increasing on-going service to the consumer.  However, let's assume the more conventional rationale of lowering total cost of producer outlay and/or the total cost of consumer ownership that is financed by the producer, as this is what seems to be on most peoples' minds when the term CR is used.

Since much of the producer's costs are unknown, or at best hypothesized on a running basis, during PD, CR from the point-of-view of a product development team is more of an ambiguous concept.  So how can it be couched in terms of what a product development team actually does?

Let's start with a view of CR from 30,000-feet (9144-meters).  Others have taken similar global views of product costs, e.g.:



1For complete definition of 'product''see page 6 in Quality vs. Reliability from a Product Development point-of-view and http://www.pdma.org/library/glossary.html)

 
JUMP TO PAGE
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36

2008, Richard M. Haney, CMT Group
© 1997-2012 TECHMAN/KANATA Legal Notice Site map