2012
DOI: 10.1007/978-3-642-35758-9_38
|View full text |Cite
|
Sign up to set email alerts
|

A Framework for Evaluating Collaborative Product Representations in Product Lifecycle Workflows

Abstract: Product definition technology has evolved in such a way as to encourage the proliferation of data formats used within the product lifecycle for various use cases. One such product development framework being proposed in industry today is the model-based enterprise (MBE), which is operationally driven by the model-based definition (MBD) of products. This paper describes current models of the product development process and the nature of collaborative data. This paper will also suggest a framework for evaluating… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1

Citation Types

0
7
0

Year Published

2013
2013
2023
2023

Publication Types

Select...
2
2

Relationship

0
4

Authors

Journals

citations
Cited by 4 publications
(7 citation statements)
references
References 3 publications
0
7
0
Order By: Relevance
“…teams. For that reason, Hartman et al proposed a framework for the evaluation of different collaborative MBD product representations based on four different data formats [5]. This framework includes the necessary criteria of the workflows, which included in a product life cycle insight a Model-Based Enterprise (MBE) [7].…”
Section: Mbd Evolution and Research Overviewmentioning
confidence: 99%
See 2 more Smart Citations
“…teams. For that reason, Hartman et al proposed a framework for the evaluation of different collaborative MBD product representations based on four different data formats [5]. This framework includes the necessary criteria of the workflows, which included in a product life cycle insight a Model-Based Enterprise (MBE) [7].…”
Section: Mbd Evolution and Research Overviewmentioning
confidence: 99%
“…Native MBD files can only be shared between software (CAD, CAM, PDM, etc. ), which use the same methods for data management and storage, but they allow the user to make changes to the model directly from its design history [5]. Furthermore, neutral MBD files like STEP AP 242 "Managed Model-Based 3D Engineering" include data for inspection, manufacturing, engineering visualization, supplier information, etc., which enables the collaboration between different software (SOLIDWORKS, CATIA, AUTOCAD, etc.…”
Section: Efficiency In Collaborationmentioning
confidence: 99%
See 1 more Smart Citation
“…Specifically, use of high fidelity model images on demand at the point of maintenance (for example a 3D image of a wing tip fairing installation) has been noted to result in less rework or missed steps. By leveraging a model-based product definition, MRO technicians would have access to the most relevant product geometry and accompanying metadata [7,8,9,10]. Moreover, in an estimate of the financial cost of maintenance errors to industry, Markou & Kalimat [11] concluded the worldwide maintenance expenditure to be $45.2B in 2008.…”
Section: Introductionmentioning
confidence: 99%
“…Hartman, Rosche, and Fischer [31] differentiate the type of CAD files to be used in the following formats: native CAD formats, derivative data formats, lightweight collaborative files, and neutral files. This distinction is important because the product representations used across the lifecycle change with respect to the desired functionality at each stage, and the exclusive use of one class of representation over another could limit the flexibility of design tools.…”
mentioning
confidence: 99%