Cost is more than an attribute
Understanding what the cost of a product is often does not mean you know what the product cost. Often when measuring cost, there is a misconception that having the cost of the product is enough. This assumption often leads to create cost as an attribute in a PLM system. This is a good start as it will give users in the PLM system some understanding of the cost, but usually leads to more questions. Just displaying the cost as an attribute gives no context to the cost. Was this cost from the ERP system? What ERP cost was used, standard cost, last purchased price, planned price, etc? What volumes were used to get that cost? What if the cost was an estimate, if so what estimation technique was used, with what confidence level?
To impact the cost of the product, more details of the cost are usually required. Cost breakdowns provide valuable information as to the cost of the process, materials, labor, and shipping for example. Pareto analysis can be used to understand where to focus any cost reduction efforts. Information of where and how the cost were created can be useful in understand the confidence and risk in the cost value. Alternate cost scenarios could also be used to understand different cost for the product based on different manufacturing techniques (casting vs. machining) or manufacturing locations.
Having a cost at the part level also requires being able to rollup the cost of a product. This seems simple at first. You would just multiple the quantity of the part in the assembly times the cost and add them up. Rarely is a product configuration this simple. To rollup of the cost effectively, you will need to understand the specific configuration, the product options, the impact of alternates and substitutes, and the suppliers in the approved manufacturers list. This complexity makes the use of a spreadsheet to do this difficult at best.
