Prodcut as realized

I have started on the capability “representing_product_as_realized” and have made a first stab at the introduction and business context.

Comments welcome

Whilst doing this I took a look at the introduction for the DEX “product_as_individual”

The first observation was that it reads as if the DEX is encompassing the “design” of the product (i.e. the CAD, specs, support breakdowns etc) as well as the actual product.

Is that the case? If so I am a bit surprised as I thought that the DEX was exclusively about the product as individual – not the design. The design should be covered in DEX1. If you need both the design and the individual then use both DEX1 and DEX8

The second observation was perhaps we have the names of the capabilities wrong.

The term product as individual refers to an existing or potential future artefact whose properties can only be known by observation or by derivation from observations. I.e the product_as_planned and the product_as_realized.

Should the capability therefore be called “representing_product_as_individual” and deal with the product as planned as well as the product as realized?

Or should we have two capabilities: “representing_product_as_realized” and “representing_product_as_planned”

Regards
Rob

-------------------------------------------
Rob Bodington
Eurostep Limited
Web Page: http://www.eurostep.com http://www.share-a-space.com
Email: Rob.Bodington@eurostep.com
Phone: +44 (0)1454 270030
Mobile: +44 (0)7796 176 401
Fax: +44 (0)1454 270031

plcs-dex message