scholarly journals The Open Assembly Model for the Exchange of Assembly and Tolerance Information: Overview and Example

Author(s):  
M. M. Baysal ◽  
U. Roy ◽  
R. Sudarsan ◽  
R. D. Sriram ◽  
K. W. Lyons

In early design phases an effective information exchange among CAD (Computer Aided Design) tools depends on a standardized representation for the product data in all PLM (Product Lifecycle Management) tools. The NIST Core Product Model (CPM) and its extension are proposed to provide the required base-level product model that is open, non-proprietary, generic, extensible, independent of any one product development process and capable of capturing the full engineering context commonly shared in product development [1,2]. The Open Assembly Model (OAM) Model extends CPM to provide a standard representation and exchange protocol for assembly. The assembly information model emphasizes the nature and information requirements for part features and assembly relationships. The model includes both assembly as a concept and assembly as a data structure. For the latter it uses the model data structures of ISO 10303, informally known as the Standard for the Exchange of Product model data (STEP)[3]. The objective of the paper is to show how the OAM can be used to realize seamless integration of product information, with an emphasis on assembly, throughout all phases of a product design. A gearbox design example is used to illustrate the process.

Author(s):  
Mehmet Murat Baysal ◽  
Utpal Roy

In this work, NIST’s Core Product Model (CPM) and the Open Assembly Model (OAM) are extended to integrate product information including function and behavior, with an emphasis on assembly, throughout all phases of product development. The consistency validation of product information, and the verification of modified product information are discussed. These processes ensure that the product information has no contradictions and allows tracing through associations without any deficiency or disconnection. In other words, the information model has to be complete in terms of traceability of function, behavior, spatial relationships, etc., in order to support all information exchange activities. The product information representation provides a mechanism for capturing product information and storing it in a database. This representation schema also provides necessary information for any future decision making activities at the End_Of_Life (EOL) environment, such as the replacement or reuse of any part or subassembly. When there is a need to replace one artifact with another, one must consider all of the associations of the existing artifact with other artifacts and the environment, not just functional and space requirements, and the relevant modification(s) of the associated objects has to be verified. So one can manage product lifecycle activities in different perspectives by knowing how the product information is interconnected in various domains and how its characteristics affect each other.


2013 ◽  
Vol 135 (09) ◽  
pp. 46-49 ◽  
Author(s):  
Dick Bourke

This article focuses on different software tools that give engineers a quick access to product information. Software tools help access data generated during the product development process. Known as a search-based application or as unified information access, these tools use elements of semantic technology—machine-based recognition of meanings and relationships in text—to find information stored throughout a company’s multiple sources of data, including computer-aided design files and product lifecycle management systems. These software tools perform three functions: search, discover, and analyze. Search applications reduce the risks of using incomplete information when making product development decisions. Another type of search technology to consider is geometric-based search that pinpoints relevant parts based on shape. A company’s software selection criteria must encompass the informational needs of all product development activities throughout the enterprise. These activities include design engineering, manufacturing process planning, and quality control.


Author(s):  
Mehmet Murat Baysal ◽  
Utpal Roy ◽  
Rachuri Sudarsan ◽  
Ram D. Sriram ◽  
Kevin W. Lyons

The objective of this paper is to discuss the main issues for product information exchange through the Open Assembly Model (OAM). The OAM model provides a base level product model that is open, simple, generic, expandable, independent of any vendor software and product development process, and capable of engineering context that is shared throughout the product lifecycle. Two of the main issues in the OAM model are the representation of geometric information of the artifacts (and assembly features) and maintenance of the consistency of the product information among relevant classes based on geometry information. This paper considers the geometry information at three levels: 1) basic geometric information of artifact with position and orientation information, 2) assembly features and their interrelations, and 3) detailed geometric information of all features in the artifact. In addition to geometric information, other relations/associations between the classes in the Unified Modeling Language (UML) based OAM model are maintained by constraints written in Object Constraint Language (OCL). This information structure in the UML and OCL is then mapped into the Extensible Markup Language (XML) for easy information exchange. XML is commonly used and supported by many softwares. Therefore, integration of XML with UML will provide an excellent tool for internet based collaboration.


Author(s):  
Victor B. Gerdes

Discrete manufacturing companies practicing distributed product development encounter challenges creating digital products, collaborating cross functionally in an organization and throughout the value chain, and controlling and managing product information and product development processes throughout the product’s lifecycle. This paper investigates the critical capabilities of a product development system for distributed product lifecycle management (PLM). A comprehensive product development system consisting of PTC’s Windchill PDMLink (control), Windchill ProjectLink (collaborate), and Pro/ENGINEER Wildfire (create - mechanical computer-aided design - MCAD) is presented in this paper with use cases and examples as a software solution for enabling distributed collaborative product development.


Author(s):  
Boris Toche ◽  
Greg Huet ◽  
Grant McSorley ◽  
Cle´ment Fortin

The modern perspective on product life cycle and the rapid evolution of Information and Communication Technologies in general have opened a new era in product representation and product information sharing between participants, both inside and outside the enterprise and throughout the product life. In particular, the Product Development Process relies on cross-functional activities involving different domains of expertise that each have their own dedicated tools. This has generated new challenges in terms of collaboration and dissemination of information at large between companies or even within the same organization. Within this context, the work reported in this paper focuses on a specific stakeholder within product development activities — the testing department. Its business is typically related to the planning and building of prototypes in order to perform specific tests on the future product or one of its sub-assemblies. This research project aims at investigating how results from testing activities can efficiently interface with other departments, in particular to offer relevant information feedback to designers. As a first step, a study based on an open source initiative is described to show how two natively disparate PLM tools can dialogue to merge information in a central environment. The principles applied in the study are then transposed to introduce a framework where information from prototyping and testing activities could be mapped and merged with design activities to match needs in a cross-functional setting.


The current manufacturing scenario feature technology which supports the integration of various systems of CAD with CAM then CAM with CAPP or any other computer aided systems. The most important function supported by feature technology the transfer of product and process data. Product model data is the standard for exchange of product information from one CAD system to different systems for seamless integration with CAM. Most of the CAD systems are developing the software’s are using STEP AP-214 product model data. AP-214 is a systematic neutral data format for developing a feature-based process planning. In this paper, collection of STEP AP-214 based product model data as stated by ISO 10303 to identify the features of the product for manufacturing of prismatic part and generating a standard process plan. Further, this process planning is used to generate computer numerical control (NC) codes for CAM system to complete the manufacturing of part.


2020 ◽  
Vol 7 (5) ◽  
pp. 603-614 ◽  
Author(s):  
Mutahar Safdar ◽  
Tahir Abbas Jauhar ◽  
Youngki Kim ◽  
Hanra Lee ◽  
Chiho Noh ◽  
...  

Abstract Feature-based translation of computer-aided design (CAD) models allows designers to preserve the modeling history as a series of modeling operations. Modeling operations or features contain information that is required to modify CAD models to create different variants. Conventional formats, including the standard for the exchange of product model data or the initial graphics exchange specification, cannot preserve design intent and only geometric models can be exchanged. As a result, it is not possible to modify these models after their exchange. Macro-parametric approach (MPA) is a method for exchanging feature-based CAD models among heterogeneous CAD systems. TransCAD, a CAD system for inter-CAD translation, is based on this approach. Translators based on MPA were implemented and tested for exchange between two commercial CAD systems. The issues found during the test rallies are reported and analyzed in this work. MPA can be further extended to remaining features and constraints for exchange between commercial CAD systems.


Author(s):  
Aditya Balu ◽  
Sambit Ghadai ◽  
Gavin Young ◽  
Soumik Sarkar ◽  
Adarsh Krishnamurthy

The widespread adoption of computer-aided design (CAD) and manufacturing (CAM) tools has resulted in the acceleration of the product development process, reducing the time taken to design a product [46]. However, the product development process, for the most part, is still decentralized with the design and manufacturing reviews being performed independently, leading to differences between as-designed and as-manufactured component. A successful product needs to meet its specifications, while also being manufacturable. In general, the design engineer ensures that the product is able to function according to the specified requirements, while the manufacturing engineer gives feedback to the design engineer about its manufacturability. This iterative process is often time consuming, leading to longer product development times and higher costs. Recent researches in integrating design and manufacturing [24, 28, 46] have tried to reduce these differences and making the product development process easier and accessible to designers, who may not be manufacturing experts. In addition, there have been different efforts to enable a collaborative product development process and reduce the number of design iterations [8, 10, 41]. However, with the increase in complexity of designs, integrating the manufacturability analysis within the design environment provides an ideal solution to improve the product design process.


Author(s):  
Joshua Lubell ◽  
Russell S. Peak ◽  
Vijay Srinivasan ◽  
Stephen C. Waterbury

One important aspect of product lifecycle management (PLM) is the computer-sensible representation of product information. Over the past fifteen years or so, several languages and technologies have emerged that vary in their emphasis and applicability for such usage. ISO 10303, informally known as the Standard for the Exchange of Product Model Data (STEP), contains the high-quality product information models needed for electronic business solutions based on the Extensible Markup Language (XML). However, traditional STEP-based model information is represented using languages that are unfamiliar to most application developers. This paper discusses efforts underway to make STEP information models available in universal formats familiar to most business application developers: specifically XML and the Unified Modeling Language™ (UML®). We also present a vision and roadmap for future STEP integration with XML and UML to enable enhanced PLM interoperability.


Author(s):  
Francesco Ferrise ◽  
Monica Bordegoni ◽  
Umberto Cugini

For more than 40 years the development of Computer Aided Design (CAD) tools has been focused on the description of the geometry of products. More recently, CAD tools have evolved in tools to support the Product Lifecycle Management (PLM), which are more oriented to support the management aspects of the product development process than the design process itself. Recently, it has been introduced a new design method that adopts a top-down approach, which starts from the definition of a Functional MockUp (FMU) allowing to simulate the overall behavior and the use of the concept level before the detailed design. This method is closer to the typical logical sequence of design, where the designer has at first an overall view of a system and of its sub-components, and then he takes care of the details. This method is supported by commercial tools, as the LMS-Amesim suite, or by open-source software tools based on the Modelica language. This is an open-source language allowing designers to integrate and describe at functional level several aspects of a system, including mechanical, electrical, thermal, hydraulic, control and others allowing to simulate all together. The paper analyses this methodological approach and presents some applications where some systems are designed using a functional modeling approach.


Sign in / Sign up

Export Citation Format

Share Document