Bernhard Westfechtel. Integrated product and process management for engineering design applications. Integrated Computer-Aided Engineering, 3(1):20-35, January 1996.  Home/Search   Document Details and Download   Summary   Related Articles   Check

.... provided by PDM systems for communicating between applications and personnel, for transporting data among distributed locations, for translating data between applications, for scanning and viewing images, and for configuring and monitoring the PDM system [42] In his description of CIM Manager [62], Westfechtel provides a more detailed look at some of the issues associated with product and process management for engineering design applications. CIM Manager is conceptual PDM infrastructure for which Westfechtel has implemented a limited prototype. CIM Manager, as well as most other PDM ....

....be automatically propagated to the alternative. The granularity of the changes is exactly that necessary to completely capture the additional bearing no data objects other than the connector need to be included in the specification of the alternative version. In product data management systems [4, 40, 42, 62], designers create structural links to classify alternative versions of a design model. Alternatives are created as complete design models, either by copying and modifying an existing model, or by developing a completely new model. The alternative version of the spindlehousing interface object, as ....

[Article contains additional citation context not shown here]

Bernhard Westfechtel. Integrated product and process management for engineering design applications. Integrated Computer-Aided Engineering, 3(1):20-- 35, 1996. 138

....environment prototypes as well as the meta environment itself. Examples include an extensive MIL environment [4] a requirements engineering environment featuring integrated data flow and EER diagrams [12] and an administrative environment for the management of products, processes, and resources [22]. Rather recently added extensions for generating complex context sensitive editing operations, incrementally working type checkers, and execution tools are still under development. They rely heavily on the existence of the PROGRES environment. An EBNF translator takes a context free grammar ....

B.Westfechtel: "Integrated Product and Process Management for Engineering Design Applications", in Integrated Computer --Aided Engineering 3,1, John Wiley & Sons, 1996, pp. 20--35

....the art and future work Figure 10: Control flow view in prototype Although we have only presented the task management model in this paper, we have formalized a computational model for resource management, as well. Out of another project we can reuse a model for version and configuration management [28]. These models have common characteristics: ffl All models are domain independent. ffl The different models provide operations for construction, analysis and enactment. ffl All models can individually adapted to an application domain or certain project. ffl Since all models deal with many ....

B. Westfechtel. Integrated Product and Process Management for Engineering Design Applications. Integrated Computer-Aided Engineering, 3(1), 1996.

....net does not contain cycles. 7 State of the art and future work Although we have only presented the task management model in this paper, we have formalized a computational model for resource management, as well. Out of another project we can reuse a model for version and configuration management [28]. These models have common characteristics: ffl All models are domain independent. ffl The different models provide operations for construction, analysis and enactment. ffl All models can individually adapted to an application domain or certain project. 154 Carl Arndt Krapp Figure 12. Control ....

B. Westfechtel. Integrated Product and Process Management for Engineering Design Applications. Integrated Computer-Aided Engineering, 3(1), 1996.

.... formalism which hides the low level event trigger definitions (e.g. AdeleTempo [1] Most SCM systems fall into this class, e.g. ClearCase [14] 4) Product structure centered: In this approach, the product structure is used to determine tasks and their data flow dependencies as proposed in CoMa [16]. A task is associated with every component (placeholder for a version of a specific document) of a complex document and the component dependencies are interpreted as data flow dependencies. The goal of the task is to produce a version of the corresponding document using versions of the master ....

....component has several limitations as a general approach since no independent process space exists. On the other hand, this approach enhances product management systems with some process management services on a high level of abstraction and can be enhanced to support simultaneous engineering (cf. [16]) 5) Object based: The object based approach is adapted from object oriented modeling techniques which are applied for process and product management (e.g. ESCAPE [13] SOCCA [6, Chap. 4] In this approach, objects documents are the building blocks of the model which define the structure of ....

Westfechtel, B.: "Integrated Product and Process Management for Engineering Design Applications", Integrated Computer-Aided Engineering, 3(1), 1996; pp. 20-35.

.... formal specification, parts of which have been published previously [14,15] Our main intent is to demonstrate that graph rewriting is in fact well suited for the specification of management tools (as one important application domain) For further information on SUKITS, the reader is referred to [13,16,17,18]. In Section 1.2, we give a brief overview of the SUKITS project. Sections 1.3 and 1.4 present the SUKITS management model at an informal and at a formal level, respectively. Section 1.5 summarizes our contributions and gives an outlook on future work. 4 1.2 The SUKITS Project SUKITS focuses ....

Bernhard Westfechtel. Integrated product and process management for engineering design applications. Integrated Computer-Aided Engineering, 3(1):20-35, January 1996.

.... formal specification, parts of which have been published previously [14,15] Our main intent is to demonstrate that graph rewriting is in fact well suited for the specification of management tools (as one important application domain) For further information on SUKITS, the reader is referred to [13,16,17,18]. In Section 1.2, we give a brief overview of the SUKITS project. Sections 1.3 and 1.4 present the SUKITS management model at an informal and at a formal level, respectively. Section 1.5 summarizes our contributions and gives an outlook on future work. 4 1.2 The SUKITS Project SUKITS focuses ....

Bernhard Westfechtel. Integrated product and process management for engineering design applications. Integrated Computer-Aided Engineering, 3(1):20-35, January 1996.

....of the raw part to start with, of the positions of the work piece, etc. manufacturing plans (CAP) NC programs (CAM) material requirements definitions, results of FEM simulations (CAE) etc. TheCoMa tools play a central role in the SUKITS system; for further details, the reader is referred to [60]. 5. Relation to Other Work In the following, we relate our approach to other work in the field of configuration management. The comparison is carried out from two perspectives and refers to the functionality as well as to the specification of the CoMa system (subsections 5.1 and 5.2, ....

B. Westfechtel, "Integrated Product and Process Management for Engineering Design Applications", Integrated Computer--Aided Engineering 4--1 (1996), to appear.

....previous work has not addressed these problems in a satisfactory way. On the other hand, empirical evidence of the usefulness of our approach is still missing. DYNAMITE is a successor to CoMa (Configuration Manager) a version and configuration management system for engineering design documents [21, 23]. The CoMa system primarily supports product management, but it also provides support for process management. CoMa follows a product centered approach to process management (for the sake of flexibility, DYNAMITE separates between products and processes, see section 3) The CoMa process model is ....

B. Westfechtel. Integrated Product and Process Management for Engineering Design Applications. Integrated Computer-Aided Engineering, 3(1), 1996.

....is eliminated. In our work, we intend to support the modeling and execution of dynamic software processes, taking e.g. product evolution, feedback, and concurrent engineering into account. In addition to software processes, we have been studying other domains as well (mechanical engineering [24] and only recently chemical engineering) Our experiences in all of these domains have shown that processes exhibit quite similar characteristics, and that dynamic task nets are quite universal with respect to their application domain. Before having switched to UML as a process modeling ....

B. Westfechtel. Integrated product and process management for engineering design applications. Integrated Computer-Aided Engineering, 3(1):20--35, Jan. 1996.

....or how to structure the version space. Our comparison is mainly based on an analysis of approaches presented in the scientific literature. We cover both research prototypes and commercial systems. Our expertise refers primarily to the SCM domain, but we have also gathered some experience in EDM [43]. Section 2 illustrates the parallels between EDM and SCM by a couple of examples. Section 3 compares both domains more systematically with respect to the product space (the objects to be managed) and the version space (the concepts for maintaining versions of evolving objects) Looking at EDM and ....

....e.g. Clearcase allows Unix and NT users to transparently access the repository through their native file systems. In many EDM settings, however, such facilities are not offered. For instance, the informatics and mechanical engineering department in Aachen jointly performed the SUKITS project [43], where we had to integrate tools running under MS DOS, VMS, and different Unix versions. Many of these tools were also based on proprietary data formats and home grown database systems. As a consequence, a virtual file system was simply not viable, at least on present operating systems. Since ....

B. Westfechtel. Integrated Product and Process Management for Engineering Design Applications. Integrated Computer-Aided Engineering, 3(1):20--35, Jan. 1996.

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC