A platform is commonly used as a basis for generating a number of derivative products, after which it is replaced by a new platform. For some companies, a more viable approach is to adopt a continuous platform that is sustained and expanded over time. This applies to companies that have to provide highly customized products while not in control of interfaces, suppliers in the aerospace industry, for example. For them, the traditional part-based generation of platforms is not sufficient, and more flexibility must be built into the platform. This article proposes an approach for continuous platform development, based on an integrated artifact model and connected development processes. The processes apply set-based concurrent engineering to develop derivative products and to extend the bandwidth of the platform. The artifact model serves as a basis for development and connects products and manufacturing systems to enable informed design decisions that span across the lifecycle. The proposed approach incorporates two modes of platform use. Mode I is applied for configuring products to order within the bandwidth of the platform. This includes automatic concept evaluation using a pallet of computer-aided engineering tools and supporting tools. Mode II is applied when the bandwidth does not suffice to cover the required functionality and therefore needs to be expanded. This article exemplifies the approach through a case from a supplier in the aerospace industry.

Platforms may enable offering a variety of products to the market while keeping the development cost down. Reusing design knowledge is a key concept, whether manifested as reusing parts, ideas, concepts, or technologies. This article describes processes and information technology solutions for holistically working with both technology platforms and product platforms. A platform framework was developed for managing information and to support the processes. The use of the framework is illustrated through a case study performed at a subsupplier in the aerospace industry focusing on technology development, platform-based product development, and platform configuration. A wiki system supports the technology platform, containing electronic guidelines, methods, and information about the technologies. To support the product platform, a product lifecycle management architecture is created. A turbine rear structure from a turbofan engine is used as an example, requiring several different analysis technologies to be used and coordinated when creating a variant. The solution is a product lifecycle management architecture created based on the technology platform. It integrates a product data management system, a computer-aided design tool, two computer-aided engineering tools, and a configurator.

No abstract

This paper presents a new object-oriented generic model that, together with a new method, supports speci cation of product needs and mapping of in uencing surrounding factors. The goal of the method is that individuals involved shall be able to handle and view more information related to concept selection and thereby be able to make more accurate decisions. A direct link to downstream product testing and the possibility to highlight con icting criteria at an early stage is also desirable. The model is applicable both for new design and re-design tasks. It has, however, so far only been tested in re-design of an existing product, and it has been developed while collecting information about that particular problem. Speci cation handling of today often results in large and 'hard-to-grasp' quantities of paper documents. The research goal in this work has been to create a speci cation model for the future, which will be handled by computer tools and provides relevant information to the right user at the right time. Its has been implemented using the commercial METIS Software (NCR Metis, 1995).

The seamless co-development of products and production systems is still an unresolved challenge. Undoubtedly, progress has been made through the proposal and application of new methodologies in the collective of concurrent engineering. Still, there is a gap between modeling approaches in product development and in production system design. This gap is an obstacle, especially if many interdependencies exist among the constituents of products and production systems. This article aims at closing this gap by modeling these constituents in an integrated model. This model represents the product and the production plant as co-equal systems with subsystems, interactions, and behavior. It allows modeling every subsystem in all its lifecycle phases together with the rationale behind its design. A class model is refined for purpose of laying a structured basis for modeling that can be implemented in computer-based support. A real-life example from the automotive industry illustrates the application of an integrated model and highlights its benefits for co-development.