This paper addresses the general issue of software tool support for designers, helping them to structure, to communicate and to document activities of generation, evaluation and decision. Here the focus is on detailed consideration of desired and undesired behavioural relationships among elements of complex design artefacts and with end users. This is an area that has recently been under discussion by proponents and critics of Affordance Based Design methods. Our solution approach is to extend an existing graph based software tool for design rationale capture that has been in widespread use in an international aerospace company for several years. We are integrating its Issue Based Information System (IBIS) based design argumentation with hierarchical Functional Analysis Diagrams (FAD), a form of Concept Map. The resulting software is being tested by practical application on pilot projects in the company, and initial experiences have been very favourable. The new graph element types, bidirectional relationship types between graphs, and supporting navigational facilities are described. Their use is illustrated by example of an integrated hierarchical FAD and assembly geometry model of a gas turbine engine.

The subject of this paper is the Design Rationale editor (DRed). This is a simple and unobtrusive software tool that allows engineering designers to record their rationale as the design proceeds. DRed is one of the latest of many derivatives of the venerable IBIS concept. Thus it allows the issues addressed, options considered, plus associated pro and con arguments, to be captured in the form of a directed graph of dependencies. The research was conducted in close collaboration with, deployed, and tested in a major multinational aerospace company. The paper describes the main features of the tool, by means of a real design example from the company. It then examines the methodology and process by which the tool was researched, implemented and introduced into industrial practice. Finally, DRed is compared with other IBIS-based software, to identify and explain how it addresses problems that seem to have made earlier tools unsuitable for routine use by designers. Simplicity seems to be a key factor for real world acceptance of such tools.

The Designers' Workbench is a system, developed to support designers in large organizations, such as Rolls-Royce, to ensure that the design is consistent with the specification for the particular design as well as with the company's design rule book(s). The evolving design is described against a jet engine ontology. Design rules are expressed as constraints over the domain ontology. To capture the constraint information, a domain expert (design engineer) has to work with a knowledge engineer to identify the constraints, and it is then the task of the knowledge engineer to encode these into the Workbench's knowledge base. This is an error prone and time consuming task. It is highly desirable to relieve the knowledge engineer of this task, and so we have developed a tool, ConEditor+ that enables domain experts themselves to capture and maintain these constraints. The tool allows the user to combine selected entities from the domain ontology with keywords and operators of a constraint language to form a constraint expression. In order to appropriately apply, maintain and reuse constraints, we believe that it is important to understand the assumptions and context in which each constraint is applicable; we refer to these as “application conditions”. We hypothesise that an explicit representation of constraints together with the corresponding application conditions and the appropriate domain ontology could be used by a system to support the maintenance of constraints. In this paper, we focus on the important role that the domain ontology plays in supporting the maintenance of constraints in engineering design.

This paper examines the effectiveness of human factors initiatives and addresses some difficulties reported in calculating the value of such interventions. Company representatives and researchers applied a novel probabilistic assessment tool to estimate the financial impact of two macro-ergonomic projects. Key benefits of the company intranet project include reduced administrative and operational costs compared to a paper-based system; time savings for users asking for, providing and receiving information; and improved system usability and higher levels of usage. The communities of practice project demonstrates value through more efficient distribution and retrieval of information; reduced duplication by re-using technical knowledge to solve similar problems and improved sharing of good working practices, lessons and resources. The strengths of the tool include transparency, being quick and easy to learn and the collaborative workshop format, involving researches and key representatives from the organization. It makes a useful contribution to the challenge of assessing the financial value of ergonomic interventions, and, by exploiting its diagnostic and planning capabilities, could be extended to other domains.

The Designers' Workbench is a system developed by the Advanced Knowledge Technologies Consortium to support designers in large organizations, such as Rolls-Royce, to ensure that the design is consistent with the specification for the particular design as well as with the company's design rule book(s). In the principal application discussed here, the evolving design is described using a jet engine ontology. Design rules are expressed as constraints over the domain ontology. Currently, to capture the constraint information, a domain expert (design engineer) has to work with a knowledge engineer to identify the constraints, and it is then the task of the knowledge engineer to encode these into the Workbench's knowledge base. This is an error-prone and time-consuming task. It is highly desirable to relieve the knowledge engineer of this task, so we have developed a system, ConEditor+, that enables domain experts themselves to capture and maintain these constraints. Further, we hypothesize that to appropriately apply, maintain, and reuse constraints, it is necessary to understand the underlying assumptions and context in which each constraint is applicable. We refer to them as “application conditions,” and these form a part of the rationale associated with the constraint. We propose a methodology to capture the application conditions associated with a constraint and demonstrate that an explicit representation (machine interpretable format) of application conditions (rationales) together with the corresponding constraints and the domain ontology can be used by a machine to support maintenance of constraints. Support for the maintenance of constraints includes detecting inconsistencies, subsumption, redundancy, fusion between constraints, and suggesting appropriate refinements. The proposed methodology provides immediate benefits to the designers, and hence, should encourage them to input the application conditions (rationales).

The Designers' Workbench is a system, developed by the Advanced Knowledge Technologies (AKT) consortium to support designers in large organizations, such as Rolls- Royce, by making sure that a design is consistent with the specification for the particular design as well as with the company's design rule book(s). Currently, to capture the constraint information, a domain expert (design engineer) has to work with a knowledge engineer to identify the constraints, and it is then the task of the knowledge engineer to encode these into the Workbench's knowledge base (KB). This is an error prone and time consuming task. It is highly desirable to relieve the knowledge engineer of this task, and so we have developed a tool, ConEditor, that enables domain experts themselves to capture and maintain these constraints. The tool allows the user to combine selected entities from the domain ontology with keywords and operators of a constraint language to form a constraint expression. We hypothesize that to apply constraints appropriately, it is necessary to understand the context in which each constraint is applicable. We refer to this as "application conditions". We plan to make these application conditions machine interpretable and investigate how they, together with a domain ontology, can be used to support the verification and maintenance of constraints.

The Designers' Workbench is a system, developed to support designers in large organizations, such as Rolls-Royce, by making sure that the design is consistent with the specification for the particular design as well as with the company’s design rule book(s). Currently, to capture the constraint information, a domain expert (design engineer) has to work with a knowledge engineer to identify the constraints, and it is then the task of the knowledge engineer to encode these into the Workbench's knowledge base (KB). This is an error prone and time consuming task. It is highly desirable to relieve the knowledge engineer of this task, and so we have developed a tool, ConEditor+ that enables domain experts themselves to capture and maintain these constraints. The tool allows the user to combine selected entities from the domain ontology with keywords and operators of a constraint language to form a constraint expression. Further, we hypothesize that to apply constraints appropriately, it is necessary to understand the context in which each constraint is applicable. We refer to this as conditions. We show that an explicit representation of application conditions, in a machine interpretable format, along with the constraints and the domain ontology can be used to support the verification and maintenance of constraints.

Typically, complex engineering artifacts are designed by teams who may not all be located in the same building or even city. Additionally, besides having to design a part of an artifact to be consistent with the specification, it must also be consistent with the company’s design standards.The Designers’ Workbench supports designers by checking that their configurations satisfy both physical and organisational constraints. The system uses an ontology to describe the available elements in a configuration task. Configurations are composed of features, which can be geometric or nongeometric, physical or abstract. Designers can select a class of feature (e.g. Bolt) from the ontology, and add an instance of that class (e.g. a particular bolt) to their configuration. Properties of the instance can express the parameters of the feature (e.g. the size of the bolt), and also describe connections to other features (e.g. what parts the bolt is used to hold together).

We present a tool which helps domain experts capture and maintain constraints. The tool displays parts of an ontology (as classes, sub-classes and properties) in the form of a tree. A number of keywords and operators from a constraint language are also listed. The tool helps a user to create a constraint expression. Additionally, the tool has a facility which allows the user to input tabular data. The expressed constraints can be converted into a standard format, making them portable. It is planned to integrate this tool, ConEditor, with Designers’ Workbench, a system that supports human designers.

In many large engineering design organizations the information systems have developed over time into a set of heterogeneous resources. This makes it difficult for engineers to follow a trail through the resources. This situation becomes particular difficult when the Engineer is new to a company; unfamiliar with the systems and unaware of the history of the designs. This paper presents a demonstrator system developed with a major aerospace company to aid engineers, through the use of knowledge technologies, to locate the documentation they require. The paper presents the systems and lessons learnt to enable the organisation to move towards a more semantically enriched document repository.

This paper presents a future vision for the working practices of designers within a manufacturing organisation. By its very nature the engineering design environment is highly distributed in nature and is characterised by a large number of information sources, which together with the designers forms a complex sociotechnical system. In discussions with designers it is apparent that changes are required to this environment to reflect the changes in the design process and organisations. We have developed a scenario that incorporates many of the features requested by designers and managers to improve the design environment. The scenario sets out a route map for the development of technical and social tools that aid the designer.

Design is key to a project’s profitability and therefore increased PROFIT by DESIGN is the goal of improvements to the design process. Business requirements can be summarised as Better, Faster, Cheaper and considerable investment has been made in technology and methods for the design process to enable this. There is evidence to suggest that these investments have resulted in products themselves getting better but not necessarily produced faster or cheaper. A model of the design process has been developed which makes explicit its key elements. The six key elements or dimensions of the design process are: Analyse; Understand; Decide; Create; Capture; and Know. Investments in design technology may not be reaching their full potential due to a mismatch between the relative importance of the attributes of a good designer and the areas where investments have been made, leading to a potential loss of balance in the design process. This is compounded by failure to take a holistic view of changes to the process including mitigation of any downside. In particular the Create dimension, which is seen as the most important attribute of a good designer, has had the least investment and also is the most vulnerable because it is optional. In recognition of this fact, Rolls-Royce is using the TRIZ methodology to provide designers with an improved capability. However it also is recognised that providing capability alone is not enough. The right motivation and opportunity are also needed, and this requires the appropriate organisational and cultural features to be in place. What is needed is a people centred process that is business driven and product focused.