This page contains a Flash digital edition of a book.
Figure 2: File Sizes with JT.


• JT Simplified Geometry is used for significantly improving performance


storing an arbitrary number of faceted representations with varying LODs.


• Ultra-Lightweight Precise (ULP) format provides a lighter weight surface


in large assemblies. It provides for every assembly and sub-assembly to be represented by its external surfaces only rather than the full detail of all the individual part surfaces. The assembly loads initially in as little as 1/10th the time for the full assembly. The individual part JT files are then loaded either on demand at the request of the user, or when needed for operations like measurement or cross sectioning. Simplified Geometry is ideal for shipbuilding where very large assemblies need to be loaded before users can navigate to the area where they need to work.


representation of the 3D geometry with file sizes significantly smaller (Figure 2). ULP has built in IP protection as it is accurate enough for most supplier interaction use cases but does not provide the exact surface definition (like BREP) and therefore can not be used for reverse engineering. Te ULP format makes it easier to share data across low bandwidth connections. Small file size is important as the shipbuilding collaboration network extends to countries with inadequate telecom infrastructure. JT data can be contained in a single or multiple files. Each file can contain any relevant JT information. By properly managing the allocation of information to a given physical file, if source data changes, only the JT file corresponding to that information would need to be recreated or updated. PLM solutions like Teamcenter can manage the JT files relative to their CAD originals and synchronise the creation of a new JT for every CAD revision.


PLM XML PLM XML is a XML based PLM format. PLM XML schema describes a model’s geometry, structure, features, ownership, and visualisation. PLM XML allows for


The Naval Architect January 2012


Figure 3: Use Cases


a single logical product model to have several different geometric representations, tailored to different purposes. Metadata of several different types like mass, material, PMI, application specific data, etc. can be attached to logical parts of the model or specific geometric representations. File sizes can be reduced using a reference-instance mechanism and by splitting out various sections of data into separate files (so that data not needed for a particular purpose need not be transmitted). As well as approximating and separating data, PLM XML also supports mechanisms for restricting access to parts of the model data on the basis of person, organisation or place.


Use Cases


• Visualisation & Digital Mock-up (DMU): JT is primarily used for 3D viewing by any


stakeholder who does not need to edit the geometry (Figure 3). Once a ship model is converted to JT, a JT viewer can display the product structure, perform measurements, conduct interference/clearance analysis, display properties (metadata), etc. A JT viewer can be coupled with a Virtual


• Documentation & Archiving: The most important requirement relating


Reality (VR) system that projects the image in stereo so that the user with the aid of stereo glasses can see the model in real-time 3D. It is possible to create JT files that contain structure, metadata and geometry, or alternatively the material and metadata can be imported from a PLM system. In DMU, collision checks for assembly/ disassembly and design space checks are carried out.


to the documentation and archiving of engineering data is that all relevant information be stored in a standardised format that can be read irrespective of a specific IT infrastructure and aſter a long period of time. Since the life cycle of ships can vary from 20+ years to 40+ years depending on whether they are commercial or naval, long-term data retention (LTDR) of ship product information is a serious issue. With continuous improvements in CAD technology and end of life for some of the CAD soſtware traditionally


43


Feature 4


Page 1  |  Page 2  |  Page 3  |  Page 4  |  Page 5  |  Page 6  |  Page 7  |  Page 8  |  Page 9  |  Page 10  |  Page 11  |  Page 12  |  Page 13  |  Page 14  |  Page 15  |  Page 16  |  Page 17  |  Page 18  |  Page 19  |  Page 20  |  Page 21  |  Page 22  |  Page 23  |  Page 24  |  Page 25  |  Page 26  |  Page 27  |  Page 28  |  Page 29  |  Page 30  |  Page 31  |  Page 32  |  Page 33  |  Page 34  |  Page 35  |  Page 36  |  Page 37  |  Page 38  |  Page 39  |  Page 40  |  Page 41  |  Page 42  |  Page 43  |  Page 44  |  Page 45  |  Page 46  |  Page 47  |  Page 48  |  Page 49  |  Page 50  |  Page 51  |  Page 52  |  Page 53  |  Page 54  |  Page 55  |  Page 56  |  Page 57  |  Page 58  |  Page 59  |  Page 60