A Contribution to CAE System Integration in Ship Design

2005 ◽  
Author(s):  
Robert Bronsart ◽  
Ulf Cantow ◽  
Wiegand Grafe ◽  
Thomas Koch ◽  
Bryan J. Miller

The integration of software tools used in design and production of commercial ships is regarded a key issue with respect to product optimization and overall business success. To overcome this problem CAE-systems are integrated with help of adapters to a networked information infrastructure. The overall system architecture is outlined and the underlying ERM is discussed to show the complexity of a product model suitable to support ship design and production. Data exchange scenarios are described which demonstrate the integration of different shipbuilding specific systems: e.g. NAPA Steel and the analysis tool POSEIDON by Germanischer Lloyd. The implementation of an adapter supporting the STEP protocol AP214 (Core data for automotive mechanical design processes) serves to show the potential of this well supported protocol in the shipbuilding context.

2005 ◽  
Vol 21 (02) ◽  
pp. 73-80
Author(s):  
Gregory F. Morea

The design and construction of any marine vessel designed on a computer-assisted design (CAD) system, from a nuclear aircraft carrier to the smallest work boat, requires the interaction of many electronic databases, all of which must be continually updated for the work to proceed. The exchange of this information, especially geometry, in digital format is accomplished using many different tools and techniques. Much has been presented to the marine community about the tools used, such as the Initial Graphics Exchange Specification (IGES) and the Standard for the Exchange of Product Model Data (STEP), and how these tools might be used for exchanges in the future, but little has been presented on how production data exchanges actually occur. At Electric Boat, current submarine programs cannot wait for future data transfer solutions. Design and construction data must be exchanged among various activities, internal and external, with such volume as to make manual reentry of data an unrealistic solution. Because of the complexities associated with the electronic exchange of these data, the General Dynamics (GD) Marine organization of Electric Boat has a dedicated group that both performs production data exchanges and researches and implements new methods of electronic transfer. This paper discusses the rationale for and the formation of the data exchange group at Electric Boat, along with its place within GD Marine. It then presents an overview of the tools used by the group and how production transfers occur, both routine and unique. Notable transfers provide examples of how the group works to solve transfer problems. Importantly, this paper shows how many of the exchange standards developed for the marine industry actually work in production. Special emphasis will be placed on the exchange of solid models in a day-to-day environment. The paper concludes with a look at the future of production data exchanges for Electric Boat and the larger marine industry.


Author(s):  
Adarsh Venkiteswaran ◽  
Sayed Mohammad Hejazi ◽  
Deepanjan Biswas ◽  
Jami J. Shah ◽  
Joseph K. Davidson

Industries are continuously trying to improve the time to market through automation and optimization of existing product development processes. Large companies vow to save significant time and resources through seamless communication of data between design, manufacturing, supply chain and quality assurance teams. In this context, Model Based Definition/Engineering (MBD) / (MBE) has gained popularity, particularly in its effort to replace traditional engineering drawings and documentations with a unified digital product model in a multi-disciplinary environment. Widely used 3D data exchange models (STEP AP 203, 214) contains mere shape information, which does not provide much value for reuse in downstream manufacturing applications. However, the latest STEP AP 242 (ISO 10303-242) “Managed model based 3D engineering” aims to support smart manufacturing by capturing semantic Product Manufacturing Information (PMI) within the 3D model and also helping with long-term archival. As a primary, for interoperability of Geometric Dimensions & Tolerances (GD&T) through AP 242, CAx Implementor Forum has published a set of recommended practices for the implementation of a translator. In line with these recommendations, this paper discusses the implementation of an AP 203 to AP 242 translator by attaching semantic GD&T available in an in-house Constraint Tolerance Graph (CTF) file. Further, semantic GD&T data can be automatically consumed by downstream applications such as Computer Aided Process Planning (CAPP), Computer Aided Inspection (CAI), Computer Aided Tolerance Systems (CATS) and Coordinate Measuring Machines (CMM). Also, this paper will briefly touch base on the important elements that will constitute a comprehensive product data model for model-based interoperability.


Author(s):  
Stefan Wo¨lkl ◽  
Kristina Shea

The importance of the concept development phase in product development is contradictory to the level and amount of current computer-based support for it, especially with regards to mechanical design. Paper-based methods for conceptual design offer a far greater level of maturity and familiarity than current computational methods. Engineers usually work with software designed to address only a single stage of the concept design phase, such as requirements management tools. Integration with software covering other stages, e.g. functional modeling, is generally poor. Using the requirements for concept models outlined in the VDI 2221 guideline for systematic product development as a starting point, the authors propose an integrated product model constructed using the Systems Modeling Language (SysML) that moves beyond geometry to integrate all necessary aspects for conceptual design. These include requirements, functions and function structures, working principles and their structures as well as physical effects. In order to explore the applicability of SysML for mechanical design, a case study on the design of a passenger car’s luggage compartment cover is presented. The case study shows that many different SysML diagram types are suitable for formal modeling in mechanical concept design, though they were originally defined for software and control system development. It is then proposed that the creation and use of libraries defining generic as well as more complicated templates raises efficiency in modeling. The use of diagrams and their semantics for conceptual modeling make SysML a strong candidate for integrated product modeling of mechanical as well as mechatronic systems.


2013 ◽  
Author(s):  
R Bencic ◽  
◽  
M Milanovic ◽  
G Sikic ◽  
M Bistricic ◽  
...  

Author(s):  
Bernie Bettig ◽  
Jami Shah

Abstract This paper describes the derivation of a consistent and comprehensive set of geometrical constraints for shape definition in Computer-Aided Design. These are needed to enable compatibility in parametric data exchange and to promote both standard capabilities and predictable solutions from constraint solving software kernels. The paper look at the mathematical basis for constraints present in the literature and elaborates about all types of constraints that can be described by the same mathematical basis. The approach considers all combinations of distance and angle constraints, on one point or all points of curves and surfaces, as well as transformations and mappings that are required in mechanical design.


1986 ◽  
Vol 2 (03) ◽  
pp. 185-195
Author(s):  
B. F. Tibbitts ◽  
P. A. Gale

The paper discusses, from a ship designer's perspective, some of the current topics and issues relating to the interface between naval ship design and production. The current environment within which naval ship design activity is taking place is described. Notable current views on Navy ship design and how it might be improved are summarized. Navy design topics pertinent to improving ship producibility, operability, maintainability and survivability are discussed and examples from recent ship designs are. presented. Issues which result from apparent conflicts in current design initiatives and critiques of the Navy ship design process are highlighted and discussed. Finally, some general conclusions are drawn.


1994 ◽  
Vol 10 (04) ◽  
pp. 281-296
Author(s):  
James T. Higney ◽  
Joanne J. Ouillette

Draft STEP (Standard for the Exchange of Product Model Data) application protocols, developed by the Navy Industry Digital Data Exchange Standards Committee (NIDDESC), have been issued to define the information content of a product model for a ship. The work reported in this paper combines the existing CAD models of the DDG51 Class design with a newly developed non-graphic database so that the overall information content complies with the STEP protocols. This work represents the first-time implementation of the application protocols and is a significant step in the Navy's plan to do the design of variants of the DDG51 Class totally in computer-aided design (CAD). The combined graphic/non-graphic database is referred to as the DDG51 engineering product model. Emphasis has been placed on populating the non-graphic database with the information necessary to perform all required engineering analyses. The basic schema described in this paper may be extended to support other areas of interest, such as logistics support.


Author(s):  
Fei Gao ◽  
Dieter Roller

Abstract Capturing design process is becoming an important topic of feature-based modeling, as well as in product data exchange, concurrent design, and cooperative design. Three critical issues on the modeling of design process are considered in this paper, namely, feature concepts, feature evolution, and the semantic consistencies of the states of product models. A semantics-based product model is introduced to facilitate the description of both conceptual and detailed models, and to maintain the semantic consistencies of product states. The process is represented by feature states and their evolution records. Feature type variation and prototype-based design are proposed to support feature evolution. A conceptual description of the design process and an example are given.


Sign in / Sign up

Export Citation Format

Share Document