Characterising the requirements of engineering information systems

Well-organised information is vital in gaining a competitive advantage within engineering companies. Increasingly, computer systems are used for managing this information, but for systems to be successful they need to be built on an understanding of how engineers work. This paper contributes to this understanding by reporting on how 10 engineers, from two aerospace companies, organise and use information. Information profiles have been proposed as a means of identifying the requirements of engineers who are working in different design situations (characterised by the stage of the design life cycle and also the social environment in which the engineers work). The results indicate important differences in the extent to which personal, local group and company-wide information is used. In particular, clear differences are identified between engineers who can be considered as company 'experts' and those involved in mainstream design activities. These differences manifest themselves in the extent to which personal and local group information collections are used, the content and also the strategies used for storing and updating the material within these stores.

[1]  Klaus Ehrlenspiel,et al.  Comparing designers from practice and designers with systematic design education , 1999 .

[2]  Michael J. D. Sutton.  Document Management for the Enterprise: Principles, Techniques, and Applications , 1996 .

[3]  David G. Ullman,et al.  The Mechanical Design Process , 1992 .

[4]  Chris A McMahon,et al.  Information Access Diagrams: A Technique for Analyzing the Usage of Design Information , 1996 .

[5]  David G. Ullman,et al.  A comparison of the results of empirical studies into the mechanical design process , 1988 .

[6]  Petra Badke-Schaub,et al.  Analysis of design projects , 1999 .

[7]  T. A. Stewart.  Intellectual Capital: The New Wealth of Organizations , 1997 .

[8]  P. Drucker.  Post-Capitalist Society , 1993 .

[9]  I. Nonaka,et al.  The Knowledge Creating Company , 2008 .

[10]  Chris A McMahon.  Engineering Design: management of information and uncertainty , 1999 .

[11]  Jami J. Shah,et al.  Database infrastructure for supporting engineering design histories , 1996, Comput. Aided Des..

[12]  Ken M. Wallace,et al.  The relationship between data, information and knowledge based on a preliminary study of engineering designers , 1999 .

[13]  Robert P. Smith,et al.  An Observational Study of Design Team Process: A Comparison of Student and Professional Engineers , 1998 .

[14]  Jami J. Shah,et al.  Engineering data management: achieving integration through database technology , 1993 .

[15]  Ann Langley,et al.  Between 'Paralysis by Analysis' and 'Extinction by Instinct' , 1995 .

[16]  Steven L. Salzberg,et al.  Managing information for concurrent engineering: Challenges and barriers , 1990 .

[17]  Walter Eversheim,et al.  Information management for concurrent engineering , 1997, Eur. J. Oper. Res..

[18]  Eswaran Subrahmanian,et al.  Shared memory in design: A unifying theme for research and practice , 1992 .

[19]  Biren Prasad,et al.  Information Management for Concurrent Engineering: Research Issues , 1993 .

[20]  Yoram Reich,et al.  THE N-DIM APPROACH TO CREATING DESIGN SUPPORT SYSTEMS , 1997 .

[21]  Eswaran Subrahmanian,et al.  Concurrent design happens at the interfaces , 1995, Artificial Intelligence for Engineering Design, Analysis and Manufacturing.