Engineering data re-use at JPL: promise and perils

Previously, a new approach to sharing engineering data using a JPL developed Product Attribute Database (PAD) was described. Since its development the PAD has been used on several projects at JPL with mixed results. The lessons learned in its implementation have wider implications for engineering processes and the associated data that is produced and consumed during a project´s life cycle. In addition to the normal resistance of personnel to adopt a new tool who´s benefits are not yet quantified in practice, the need to spend substantial effort early on to establish and promulgate a common understanding of the data has impeded acceptance and use of the PAD. The limitations of the original user interface and the lack of existing project data (either in template or detailed form) has also played a role in delaying widespread user acceptance. Despite these drawbacks, the initial use of the PAD has highlighted misunderstandings regarding definition of engineering data and has led to numerous fruitful discussions among engineering disciplines. Even apparently intuitively obvious data such as the total flight system mass or the spacecraft mechanical configuration coordinate system have required refinement to eliminate the natural ambiguity that engineers routinely accommodate, but that leads to confusion when automated modeling tools are the creators and consumers of the data. These discussions have led to increased insight into engineering processes, particularly those using the model based design approach that is now being implemented at JPL