CAx/engineering data management integration: Enabler for methodical benefits in the design process

Burr, Holger; Vielhaber, Michael; Deubel, Till; Weber, Christian; Haasis, Siegmar

doi:10.1080/09544820500131268

Cited by 21 publications

(10 citation statements)

References 5 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…This can lead to situations that are so contradictory that we might end up trying to solve a problem with no solution. Ultimately, when the actors of different professional fields exchange information or knowledge, some content is lost either by communication omission or by misinterpretation of this information as mentioned by (Burr et al 2005). The other possible consistency problem is less fundamental but equally important and consists in inter-domain consistency.…”

Section: Current Design Process At Renaultmentioning

confidence: 99%

See 1 more Smart Citation

11.2.2 Reducing the Gap Between Formal and Informal Worlds in Automotive Safety‐Critical Systems

Chalé

Taofifenua

Gaudré

et al. 2011

INCOSE International Symp

View full text Add to dashboard Cite

Abstract. The upcoming ISO26262 standard, which deals with the functional safety of road vehicles, will induce car manufacturers to adapt the way in which vehicle systems are usually developed. To achieve this, more rigorous development processes along with new tools and techniques will most certainly be necessary. This paper presents an overview of current initiatives at Renault dealing with the improvement of development processes for mechatronic systems to comply with ISO 26262. It focuses on introducing more formalization in the systems engineering design process via the definition of an ontology to formalize the concepts and knowledge of the systems engineering, functional safety and automotive specialty domains (e.g. braking, energy management). The ontology is at the heart of our improvement initiatives since it allows establishing logical consistency of the whole design process. A regenerative hybrid braking system integrated into a full electrical vehicle will serve as the case study for the evaluation of the improvements made possible by the approach.

show abstract

Section: Current Design Process At Renaultmentioning

confidence: 99%

“…We use the "Ontology Web language" (OWL 1.0 3 ), a formal language with mathematically defined syntax and semantics 4 . For instance, a Safety Goal is defined by a couple Feared System Event (FSE) and ASIL.…”

Section: Verify That Two Models Are Consistent: If We Had Defined a Mmentioning

confidence: 99%

11.2.2 Reducing the Gap Between Formal and Informal Worlds in Automotive Safety‐Critical Systems

Chalé

Taofifenua

Gaudré

et al. 2011

INCOSE International Symp

View full text Add to dashboard Cite

show abstract

“…Coordination among these specialists became difficult, and many errors resulted. The latest versions of some CAD applications are starting to allow 'inheritance' of some properties from one constructional part to another, and automated check assembly, see figure 1 [1]. …”

Section: Introductionmentioning

confidence: 99%

Engineering Design Education and Time Management

Eder¹

2011

PCEEA

View full text Add to dashboard Cite

show abstract

“…For a large scale company, 111 the management of relative positions of parts using positioning 112 matrices is implemented in PDM systems in order to be more 113 closely related to geometric models defined in CAD systems, and to 114 facilitate change management and part positioning [32]. Further-115 more, other authors [33,34] have proposed an advanced PDM 116 system based on a property-driven development/design (PDD) 117 approach by introducing the handling of predicted engineering 118 characteristics (i.e. structure, shape and material) and properties 119 (i.e.…”

mentioning

confidence: 99%

Product relationships management enabler for concurrent engineering and product lifecycle management

Demoly

Dutartre

Yan

et al. 2013

Computers in Industry

View full text Add to dashboard Cite

Application of a product relationships management approach in PLM. Approach enabling the concurrent product design and assembly sequence planning. Implementation of integrated product-process data management techniques in a PLM hub application. [5,4,6]. This is particularly right at the 18 beginning-of-life (BOL) phase where product designers, process 19 engineers, and assembly planners are still working separately 20 without any recovery, overlap or feedback loop facilities/features 21 in their tasks. Past research efforts have led to successful design 22 for X (DFX) and knowledge-based techniques in product design 23 in order to integrate all constraints of each life phases (i.e. 24 manufacturing, assembly, disassembly and recycling) [7,8], but 25 some gaps still exist in the management of the various technical 26 entities and the control of information/decision/rationale flow 27 through the product lifecycle [11]. This becomes a barrier for 28 applying an efficient concurrent engineering philosophy in BOL 29 and remains a huge challenge to be tackled [9,10]. 30 Previous work argued that companies required efficient concur-31 rent engineering (CE) [12] and PLM strategies [11] in order to 32 maintain their business competitive edge. One particular industrial 33 requirement is the need for concurrent considerations of lifecycle 34 issues for different life aspects into the early product design process 35 [13][14][15]. It is clear that current product geometry-based on 36 traditional part and feature oriented modelling approaches-only The current competitive industrial context requires more flexible, intelligent and compact product lifecycles, especially in the product development process where several lifecycle issues have to be considered, so as to deliver lifecycle oriented products. This paper describes the application of a novel product relationships management approach, in the context of product lifecycle management (PLM), enabling concurrent product design and assembly sequence planning. Previous work has provided a foundation through a theoretical framework, enhanced by the paradigm of product relational design and management. This statement therefore highlights the concurrent and proactive aspect of assembly oriented design vision. Central to this approach is the establishment and implementation of a complex and multiple viewpoints of product development addressing various stakeholders design and assembly planning points of view. By establishing such comprehensive relationships and identifying related relationships among several lifecycle phases, it is then possible to undertake the product design and assembly phases concurrently. Specifically, the proposed work and its application enable the management of product relationship information at the interface of product-process data management techniques. Based on the theory, models and techniques such as described in previous work, the implementation of a new hub application called PEGASUS is then described. Also based on web service technology, PEGASUS ca...

show abstract

CAx/engineering data management integration: Enabler for methodical benefits in the design process

Cited by 21 publications

References 5 publications

11.2.2 Reducing the Gap Between Formal and Informal Worlds in Automotive Safety‐Critical Systems

11.2.2 Reducing the Gap Between Formal and Informal Worlds in Automotive Safety‐Critical Systems

Engineering Design Education and Time Management

Product relationships management enabler for concurrent engineering and product lifecycle management

Contact Info

Product

Resources

About