Alternatively, Excel spreadsheets or Word documents can be embedded in CAD files. Changes in the spreadsheet or the document will automatically update the CAD file, and vice versa. A t first glance, this strategy seems extremely appealing because of the potential benefits of object oriented programming, particularly the reuse of component software. T he strategy also leverages the familiarity of Windows-based applications for the engineering desktop. Training requirements, a traditional headache in the technical environment, can be alleviated considerably.
Major concerns relate to the formative stage of development, performance and scalability.
T he current extensions allow users to select, reference, translate, and rotate objects. CAD companies can easily agree on such extensions since they involve a relatively uniform and obvious set of technical requirements. Changes in CAD designs can be automatically captured in associated documents. W hile this level of functionality supports the ability to insert objects into documents or even build assemblies with constraints, it falls dreadfully short of the functionality required to address the mechanical design arena. For example, users cannot change the geometry of parts without accessing functions of the CAD system that created them.