Comprehensive Collection of Industrial JT Use Cases - JT Recommendation Comprehensive Collection of Industrial JT Use Cases - prostep ivip
←
→
Page content transcription
If your browser does not render page correctly, please read the page content below
Recommendation
Comprehensive Collection
of Industrial JT Use Cases
Titel
prostep ivipder Publikation
PSI 14-2 Recommendation V2
JT Recommendation
Comprehensive Collection of Industrial JT Use Cases
ABSTRACT / DISCLAIMER / COPYRIGHT prostep IVIP Recommendation
Abstract
The JT data format (ISO 14306:2017) enables the creation and utilization of high-performance 3D models for all life
stages of the product lifecycle. The compressible data format contains a CAD-neutral description of product data and
acts as a key factor in the integration of multiple CAD and PDM systems.
This Recommendation gives an overview about JT, the lightweight format for 3D data. After a short introduction a look in
the brief history is given. Within the JT Workflow Forum project group, use cases for the application of JT in the context
of virtual product engineering were specified. These are presented in this document.
Disclaimer
This document is a Prostep ivip Documentation (PSI Documentation), referring to PSI Reference Number. Those are
freely available for all prostep ivip e.V. members. Anyone using these recommendations is responsible for ensuring
that they are used correctly.
This PSI Documentation gives due consideration to the prevailing state-of-the-art at the time of publication. Anyone
using PSI Documentations must assume responsibility for his or her actions and acts at their own risk. The prostep ivip
Association and the parties involved in drawing up the PSI Documentation assume no liability whatsoever.
We request that anyone encountering an error or the possibility of an incorrect interpretation when using the
PSI Documentations contact the prostep ivip Association immediately so that any errors can be rectified.
Copyright
I. All rights on this PSI Documentation, in particular the copyright rights of use and sale such as the right to duplicate,
distribute or publish the Documentation remain exclusively with the prostep ivip Association and its members.
II. The PSI Documentation may be duplicated and distributed unchanged, for instance for use in the context of
creating software or services.
III. It is not permitted to change or edit this PSI Documentation.
IV. A suitable notice indicating the copyright owner and the restrictions on use must always appear.
II Industrial JT Use Cases 2021-6 / V 2.0
prostep IVIP Recommendation CONTENTS
Table of Contents
1 Introduction 2
1.1 Brief history: from proprietary format to ISO standard 2
1.2 Collaboration with other communities 3
1.3 Many good reasons for neutral format – and more 5
1.4 Data model 8
2 Use Cases 9
2.1 Structure of the use case descriptions 10
2.2 JT for 3D Measurement and –Analysis and Reverse engineering 10
2.3 JT for Archiving 11
2.4 JT for Bidding and Inquiry 12
2.5 JT for Digital Factory Building Planning 13
2.6 JT for Digital Factory Manufacturing Planning 14
2.7 JT for Digital Factory Material Handling 15
2.8 JT for Digital Factory Plant development 16
2.9 JT for Drawingless Manufacturing 17
2.10 JT for ECAD/MCAD Collaboration 17
2.11 JT for Factory DMU 18
2.12 JT for Finite Element Analysis (FEA) 19
2.13 JT for high-end Visualization 20
2.14 JT for hybrid Design in Context 21
2.15 JT for Identification of Location Based Viewing 22
2.16 JT for Identification of Part/Assembly 23
2.17 JT for Installation Feasibility 24
2.18 JT for Material Specification 25
2.19 JT for Multibody Simulation (MBS) 26
2.20 JT for Multimedia Annotations 27
2.21 JT for non-hybrid Design in Context 28
2.22 JT for Packaging 29
2.23 JT for Pre-Series Aeroacoustics Modeling 30
2.24 JT for Pressline Simulation 32
2.25 JT for Supplier Integration (Customer to Supplier) 33
2.26 JT for Supplier Integration (Supplier to Customer) Sub UC1: Early phases 34
2.27 JT for Supplier Integration (Supplier to OEM) Sub UC2: Project phases 35
2.28 JT for Systems Engineering 37
2.29 JT for Tolerance Studies (VSA) 37
2.30 JT for Viewing 38
2.31 JT for viewing on mobile devices in the pre-series 39
2.32 JT for CAE Data Visualization 40
2.33 Maintenance of manufacturing machines and products 41
2.34 Simultaneous development of product and production facilities 42
2.35 JT and AP242 XML providing PMI to the product development process 43
2.36 AP242 XML kinematics for internal viewing 45
2.37 Validation for JT product data quality (PDQ) enhancement 45
2.38 JT in MBSE 46
2.39 JT for AR/VR 47
2.40 Additive Manufacturing 2.1 Structure of the use case descriptions 48
3 Final remarks 49
2021-6 / V 2.0 Industrial JT Use Cases III
TABLE OF CONTENT / FIGURES prostep IVIP Recommendation Annex A: The role of the prostep ivip Association and the VDA 50 Annex B: Quality assurance for JT 53 Annex C: Software tools for JT 58 Figures Figure 1: ISO JT is a mature Standard 3 Figure 2: Joint activities of different boards 4 Figure 3: Interaction of JT with AP242 XML 4 Figure 4: JT & STEP AP242 XML fits together 5 Figure 5: Proportion of creators/consumers of visualization data 6 Figure 6: JT is proven by industry (12/2015) 7 Figure 7: JT covers engineering use cases 7 Figure 8: Geometry in JT 9 Figure 9: Use cases in categories 10 Figure 10: Use case diagram "JT for 3D Measurement and -Analysis and Reverse engineering" 11 Figure 11: Use case diagram "JT for Archiving" 12 Figure 12: Use case diagram "JT for Bidding and Inquiry" 12 Figure 13: Use case diagram "JT for Digital Factory Building Planning" 13 Figure 14: Use case diagram "JT for Digital Factory Manufacturing Planning" 14 Figure 15: Use case diagram "JT for Digital Factory Material Handling" 15 Figure 16: Use case diagram "JT for Digital Factory Plant Development" 16 Figure 17: Use case diagram "JT for Drawingless Manufacturing" 17 Figure 18: Use case diagram "JT for ECAD/MCAD Collaboration" 18 Figure 19: Use case diagram "JT for Factory DMU" 19 Figure 20: Use case diagram "JT for Finite Element Analysis (FEA)" 20 Figure 21: Use case diagram "JT for high-end Visualization" 21 IV Industrial JT Use Cases 2021-6 / V 2.0
Figure 22: Use case diagram "JT for hybrid Design in Context" 22
Figure 23: Use case diagram "JT for Identification of location Based Viewing" 23
Figure 24: Use case diagram "JT for Identification of Part/Assembly" 24
Figure 25: Use case diagram "JT for Installation Feasibility" 25
Figure 26: Use case diagram "JT for Material Specification" 26
Figure 27: Use case diagram "JT for Multibody Simulation (MBS)" 27
Figure 28: Use case diagram "JT for Multimedia Annotations" 28
Figure 29: Use case diagram "JT for non-hybrid Design in Context" 29
Figure 30: Use case diagram "JT for Packaging" 30
Figure 31: Use case diagram "JT for Pre-series Aeroacoustics Modeling" 31
Figure 32: Use case diagram "JT for Pressline Simulation" 33
Figure 33: Use case diagram "JT for Supplier Integration (OEM to Supplier)" 34
Figure 34: U
se case diagram "JT for Supplier Integration (Supplier to Customer)"
35
Sub UC1: Early phases
Figure 35: Use case diagram "JT for Supplier Integration (Supplier to OEM)" Sub UC2: Project
36
phases
Figure 36: Use case diagram "JT for systems engineering" 37
Figure 37: Use case diagram "JT for tolerance studies" 38
Figure 38: Use case diagram "JT for Viewing" 39
Figure 39: Use case diagram "JT for viewing on mobile devices in the pre-series" 40
Figure 40: Use case diagram "JT for CAE Data Visualization" 41
Figure 41: Use case diagram "Maintenance of manufacturing machines and products" 42
Figure 42: Use case diagram “2.34 Simultaneous development of product and production
43
facilities”
Figure 43: U se case diagram “2.35 JT and AP242 XML providing PMI to the product
44
development process”
Figure 44: Use case diagram “2.36 AP242 XML kinematics for internal viewing” 45
Figure 45: U se case diagram “2.37 Validation for JT product data quality (PDQ)
46
enhancement”
Figure 46: Use case diagram “2.38 JT in MBSE” 47
2021-6 / V 2.0 Industrial JT Use Cases V
FIGURES / TABLES / REFERENCES prostep IVIP Recommendation Figure 47: Use case diagram “2.39 JT for AR/VR” 48 Figure 48: Sample file size (machine tool, 3584 BOM lines) 49 Figure 49: Process chains at Daimler before introducing JT 50 Figure 50: Process chains at Daimler after introducing JT 51 Figure 51: Links between the documents 52 Figure 52: Interaction of the VDA / prostep IVIP JT initiatives 53 Figure 53: Benchmark documentation 57 Tables Table 1 Benchmark history 54 Table 2 JT converter 58 References • JT Application Benchmarks 2009 to 2019, www.prostep.org • JT Communication Paper 05/2015, www.prostep.org • JT Content Harmonization Guideline, www.prostep.org • JT File Reference: JT ISO 14306:2017, www.iso.org • JT-IF Implementation Guidelines 12/2018, www.prostep.org • JT Industrial Application Package, 06/2021, www.prostep.org • JT Industrielles Anwendungspaket (JTIAP): DIN SPEC 91383:2021-07, www.beuth.de • White Paper Applying JT 12/2010, www.prostep.org • White Paper Fields of Application 04/2015, www.prostep.org • White Paper JT Digital Master 06/2018, www.prostep.org • White Paper JT Virtual Augmented Reality 06/2018, www.prostep.org • White Paper 3D Visualization in MBSE 01/2020, www.prostep.org VI Industrial JT Use Cases 2021-6 / V 2.0
1 INTRODUCTION prostep IVIP Recommendation 1 Introduction CAD has become what today is referred to as a “commodity”. It goes without saying that design engineering relies on authoring systems that enable a realistic model of the product being developed to be created on the screen – or on a power wall – that everybody understands. But the model is not only easier to understand. It also allows digital methods to be used for validation, testing and quality assurance where once physical prototypes were imperative. The benefits reaped have now whetted the appetite of completely new domains that had previously never shown any interest in technical details. While technical drawings could only be read by “insiders”, design engineers, people with specialist know-how and spatial visualization abilities, the 3D model can serve a wide variety of purposes for a wide variety of people. At the same time, an enormous demand for exploiting this potential has developed. Theoretically – and technically – there is hardly any task that cannot already be completed with the help of a virtual product model. Theoretically, therefore, there is hardly any department in a modern manufacturing enterprise or other enterprise that would not also benefit from access to the 3D models created in the product development department. In practical terms, however, there are still a number of obstacles to be overcome. If we want to put a name to the main obstacles involved, they are: CAD systems require too much specialist know-how to allow them to be used everywhere – they are simply too expensive for that; in its original format, the volume of data for the precise geometry and product structure is too big and the data is ill-suited for a number of tasks; its handling is too complicated and the overhead involved in converting it to the required format is too great. And in addition to the actual geometry, this data also contains know-how that should not be exchanged at all. On the one hand, these obstacles have meant that many of the benefits offered by CAx technologies have not yet been exploited to an extent that actually makes sense from the point of view of the processes, costs and quality of the work results. That is the negative aspect. On the other hand, they have also resulted in the creation of alternatives that allow industry to avoid these obstacles. That is the positive aspect. One of these alternatives is JT (Jupiter Tessellation). The reason why the VDA PLM working group, together with the prostep ivip Association, is working on JT activities is because this alternative enjoys both great popularity and widespread use within member companies. If the next stage of virtual product development is to be achieved and physical prototypes are to be rendered even more obsolete, it must be possible to display and use the data generated in the development departments with the required level of quality, regardless of its origin. And with the guarantee that, in this format, the data is based on internationally recognized standards and will therefore remain valid and processable for years to come. 1.1 Brief history: from proprietary format to ISO standard JT was originally developed by the US Company Engineering Animation, Inc. (EAI) under the name Direct-Model toolkit. EAI was founded in 1987 in Iowa with the aim of realizing the physically correct animation of technical systems. In court, the animated models were used to help illustrate technically complicated car accidents and other complex legal claims, for example. To do this, a data format had to be found for animation purposes that would allow the rapid representation of extremely large assemblies involving thousands of components. In 1999, the company was taken over by UGS and the data format was developed further as JT. The division of EAI that was involved in the visualization of technically complex legal claims was spun off at the beginning of 2001 and today goes by the name of Demonstratives, Inc. (DI). In 2003, UGS PLM Solutions established the JT Open initiative to encourage wider use of the technology. The initiative is financed by membership fees. The aim of the initiative is to improve the options available for using the format in downstream processes. The activities aimed at ISO standardization were also initiated by JT Open. The year 2003 also saw the founding of the JT User Group, which was initiated by specialists at Siemens and Bosch. The aim of the group is to provide a platform for sharing experience relating to the industrial application of JT based on day-to-day practice. The JT data format was published in December 2006 and is available to the general public. This was one of the key preconditions that allowed standardization of the format to be initiated. In April 2007, UGS PLM Solutions submitted 2 Industrial JT Use Cases 2021-6 / V 2.0
prostep IVIP Recommendation 2 GENERAL ASPECTS OF JT AND MBSE
an application for the standardization of JT to the International Organization for Standardization (ISO). In May 2007, the
company was acquired by Siemens Industry Automation and its name was changed to Siemens PLM Software. In early
summer 2009, the standardization organization decided to bring the evaluation of JT and other formats, including U3D
and Collada, to a close in that same year. JT 8.1c was published as a Publicly Available Specification (PAS) in September
2009. In December 2012, JT has been officially published as ISO 14306:2012.
Technically, ISO 14306:2012 is based on JT version 9.5. ISO 14306:2012 provides the description of the structure and
content for a binary file having the extension of .jt. A binary file with the .jt extension is generally referred to as a JT
file. All documents needed for the implementation are available royalty free. This includes patents formerly held by
Siemens PLM. The advantages for JT and its standardization are shown in Figure 1.
Figure 1: ISO JT is a mature Standard
In 2017, the standard has been revised by ISO 14306:2017 JT edition 2.
In addition, DIN SPEC 91383:2021-07 JT Industrial Application Package (JTIAP) has been standardized by DIN – the
German Institute for Standardization. This revision is based on the latest JT version 10.5 and will we publicly
available soon.
With all necessary information for implementation available in the ISO standard, the implementation and usage of JT
is not depending on a certain vendor. To ensure the interoperability between several JT implementations, guidelines
for implementation and usage of ISO 14306 are developed.
1.2 Collaboration with other communities
prostep ivip is accepted worldwide as the Single Point of Contact (SPOC) for JT and AP 242XML related requirements
and ISO-standardization of these data formats.
The activities of prostep ivip and VDA are approved by the GAAG (Global Automotive Advisory Group). The groups
also communicate with other JT-related workgroups, such as the JT Open program, and workgroups developing other
standardized engineering data formats, such as STEP AP242, Automation ML and PDF/E. Aim of this communication is
to avoid redundant work, to achieve common goals and to ensure interoperability between the different formats. The
cooperation of the individual instances is visualized in Figure 2.
2021-6 / V 2.0 Industrial JT Use Cases 3
1 INTRODUCTION prostep IVIP Recommendation Figure 2: Joint activities of different boards By using JT and STEP AP242 XML together, geometric data and information directly related to the geometry can be stored in JT files, while structure, kinematic and PDM-relevant metadata are stored in STEP AP242 XML, like displayed in Figure 3. Figure 3: Interaction of JT with AP242 XML The enhanced merger of AP 203 and AP 214, the standard for "managed model-based 3D engineering", is available as ISO 10303-242:2020. An integral part of the standard is the business object model, an XML representation of PDM- relevant information. To enhance the coverage of application scenarios, JT is often used together with STEP AP 242 XML as an accompanying format. The collaboration between the two formats is illustrated in Figure 4. 4 Industrial JT Use Cases 2021-6 / V 2.0
prostep IVIP Recommendation 2 GENERAL ASPECTS OF JT AND MBSE
Figure 4: JT & STEP AP242 XML fits together
The concept of combined usage of JT and STEP XML, e.g. for kinematic use cases, has already been proven by users
and software vendors. The groups in charge of the further development of STEP AP242 XML and JT are in constant
dialogue with each other.
1.3 Many good reasons for neutral format – and more
The path from proprietary format to ISO standard was not, of course, as straightforward as the brief history of JT
makes it sound. After all, more than ten years have passed since DirectModel, the forerunner of JT, was first used as a
neutral data format at Ford. The intervening years were characterized by a gradual and largely low-key, but nonetheless
considerable, increase in use. The reason for this was that, at the same time, the motivation for using neutral viewing
systems had also increased enormously.
Distributed development and manufacturing, which involves a more or less large number of partners working together
on the same project, has become the norm. The purchasing department has to be able to reference unambiguous,
up-to date and valid product data. The requirements according to which a supplier creates his specification should
also be based as closely as possible on the data and models from the development department. The time needed to
exchange development data during a project is time that is not available for actual team work. Testing and assessing the
results of partial developments, running through possible alternatives, virtually simulating and validating the assembly
of complex products – everywhere you look, the entire technical side of modern industry relies on the 3D model of the
product being developed. These are just some of the reasons that have led to the massive proliferation of neutral viewers.
The other reasons have to do with the overall processes. Access to product data and product models has also long been
a basic prerequisite for the economically efficient execution of numerous tasks unrelated to research and development.
Preparing for production, the planning and commissioning of production facilities, production control – without the
visualization of product and plant models, these would all be uneconomical. The creation of technical documentation
for installation and customer service, the publication of operating manuals for large facilities in 14 different languages,
preparing the market for a new product using various advertising measures – all would be cost intensive, ineffective and
not conducive to creating customer loyalty without the ready availability of data from the development department. In
relation, the 3D data are used of many more people and departments for visualization, as there are people generating
the data. This proportion is illustrated in Figure 5.
2021-6 / V 2.0 Industrial JT Use Cases 51 INTRODUCTION prostep IVIP Recommendation Figure 5: Proportion of creators/consumers of visualization data The CAD programs and other software tools used to generate the relevant data are special systems whose operation requires appropriate know-how that is not otherwise required outside of the respective specialist department. The spe- cialists themselves are unfamiliar with each other’s tools. The mechanical engineer does not understand the electrical engineering or electronics system, the SPS programmer knows nothing about MCAD, and the computational engineer is not a design engineer. It is, however, in the context of the digital factory that the different domains that use completely different tools for their work collide. Not to mention the fact that the various systems have their own formats that do not permit combined representation. And then there is the heterogeneous world within the domains, which themselves only too often make multi-CAD the order of the day. Even the availability of central data management systems has not remedied the problem. Although the files are stored in their respective valid version together with the product structure in question and, in principle, can be accessed from anywhere outside the department in which they were generated, they can still only be opened, viewed and utilized in other processes using the appropriate authoring system. Unless, of course, there is an option that allows data from completely different sources to be accessed and processed. Utilization of the original data from the engineering departments also harbors a grave risk: In addition to the actual geometry and graphics, the models also include a multitude of things that represent a company’s know-how. These parts of the data, e.g. the history of a 3D design or the specialized engineering know-how concealed in the design parameters – all part of the knowledge basis of the manufacturing company – are also what make the data too big and too heavy to be viewed and used easily in other departments. There are therefore many good reasons why JT in particular and neutral formats in general have become a veritable mega trend. The vendors of authoring systems have seen which way the wind is blowing and today provide appropriate technologies, to some extent free of charge. With over 5.000.000 users, JT is established in many industrial branches worldwide. More than 26.000.000 JT files exist in the PDM database of leading automotive OEMs Volkswagen, Daimler, Ford and BMW with num-bers rising every day, these numbers and relationships are illustrated in Figure 6. 6 Industrial JT Use Cases 2021-6 / V 2.0
prostep IVIP Recommendation 2 GENERAL ASPECTS OF JT AND MBSE
Figure 6: JT is proven by industry (12/2015)
There is a large amount of JT software available on the market. Starting with free viewers to high-end visualization and
engineering tools, available software covers many use cases. Translators are available for all major 3D-CAD formats.
The quality of the tools is proven in several benchmarks.
From simple visualization to advanced analysis, the JT format covers multiple engineering use cases and several topics.
Some of these use cases or topics are shown in Figure 7.
Figure 7: JT covers engineering use cases
2021-6 / V 2.0 Industrial JT Use Cases 71 INTRODUCTION prostep IVIP Recommendation
The prostep ivip/VDA JT Workflow Forum (JT-WF) has so far elaborated 40 use cases for the application of JT; these are
explained in detail in chapter 2. The use cases cover fields such as simulation, digital factory, drawing less processes,
engineering collaboration, supplier integration and the use on mobile devices. With the ability to store lightweight
visualization, exact geometry, PMI and metadata, JT fulfills all mandatory requirements.
The ability of available software to make use of the capabilities of JT is proven in several JT application benchmarks
and software demonstrations to the JT-WF.
1.4 Data model
Not all the elements which are today part of the JT data model were part of ISO/PAS version, which was the basis for
publication of the ISO standard in 2011 and the first JT translator benchmark in 2012.
The second edition of ISO 14306 cancels and replaced ISO 14306:2011, which has been technically revised. JT version
9.5, which includes several extensions and enhancements like JT ULP, for example, is now part of ISO 14306. Today, JT
version 10.5 is available and is part of most recent DIN SPEC 91383:2021.
The data model for JT includes more than just geometry models. On the one hand, it offers the option of displaying
the models in various degrees of precision and, on the other hand, other information that is important for product
development and downstream processes can be stored together with the model.
In addition to the ability to display geometry, it was the fact that product manufacturing information (PMI) such as
tolerances, tolerance dimensions and information about surface properties could be displayed together with the 3D
models and processed further that contributed to its fast proliferation.
Geometry:
• At one of the lowest levels, simple regular geometry such as cuboids, cylinders and pyramids – for the definition
of designed spaces for example – are located in what is referred to as the bounding box.
• Tessellated or faceted geometry allows the representation of solids and surfaces. JT offers the option of defining
different levels of detail (LOD), i.e. specifying how precisely something is to be represented. A very low LOD means
less precision and a smaller volume of data, a very high LOD means a level of precision approaching the exact
geometry and a larger volume of data.
• The latest form of compression is JT ULP (the working title was LIBRA), which was released in 2008 and allows the
volume of data to be reduced to almost one hundredth the size of the original data.
• BREP (boundary representation) geometry offers the highest level of precision. They are an exact representation of
the solids and surfaces that were generated in the CAD system, for example. The exact JT file is also only a fraction
of the size of the original file. In addition to the former used JT BREP, the newer XT BREP, which is based on the
PARASOLID kernel, is part of the standard since 2017. XT BREP features the representation of regular geometry,
among other things, and is supported by very many converters.
Other information:
• Product structure (assembly, part, instance)
• Lighting (point light, infinite light, light set)
• Textures
• Product manufacturing information (PMI) (dimensioning, surface properties, etc.)
• Attributes
The different configurations of JT files which have been described above are used in various fields. Due to the different
file contents different file sizes result. These relationships are illustrated in Figure 8.
8 Industrial JT Use Cases 2021-6 / V 2.0prostep IVIP Recommendation 2 GENERAL ASPECTS OF JT AND MBSE
Figure 8: Geometry in JT
2 Use Cases
A study conducted by the VPE has already clearly indicated that the use cases are too widely scattered to
reasonably allow them to be examined within the framework of a project group. The identified examples involve design
engineering itself, the validation of the design results with the help of digital mock-up and high-end visualization, various
types of simulation, cross-enterprise data exchange, the digital factory and production, purchasing, sales and marketing.
Certain things cannot be avoided when a new technology seeks a “natural” route for its application. Even within the
same field of application, use develops very differently from company to company. Some companies use only tessellated
data, others also use precise geometry; some companies use only geometry, others also metadata; some companies
always store the JT data together with the original data; others decide on a case-by-case basis.
Despite its great popularity and, to some extent, wide-spread use, it cannot by any means be said that JT has beco-
me widely established. JT is currently most frequently used for visualizing geometry. In this context, there is already
a wide range of examples from every branch of industry – primarily relating to the photo-realistic representations of
computer generated product models that are suitable for marketing purposes. Since standardization has been achieved,
utilization expands rapidly. This was also indicated by deliberations regarding key use cases in the JT Workflow Forum.
All the more reason, therefore, to determine which application areas require JT support most urgently.
There are a lot of possibilities to divide the use cases into different categories. One possible classification into categories
is shown in Figure 9.
2021-6 / V 2.0 Industrial JT Use Cases 92 USE CASES prostep IVIP Recommendation Figure 9: Use cases in categories The use cases are presented in detail in the following chapters in alphabetical order, first the structure is explained. 2.1 Structure of the use case descriptions The use cases are presented in the following chapters. Each use case has a uniform structure which is explained below. The use case description is divided into three sub-chapters: “Use Case”, “Description” and “Benefit”. In the sub-chapter “Use Case” the aim of the use case is described in form of a short sentence. After that the actors are listed. These are the main human and machine entities and their roles. Next the preconditions are explained. This is a description of anything being assumed to have happened before the activities described in the use case description. The sub-chapter “Description” contains a narrative description of the use case or usage scenario, followed by the postconditions where the final state is described. Afterwards a diagram in form of a simple illustration of the use case as sequence or activity diagram is shown. Finally, the benefits are described in the sub-chapter “Benefits” in form of a documentation of main benefits concerning the application of this use case for the actors. If there are any important decisions or open issues, they are explained at the end of this sub-chapter. 2.2 JT for 3D Measurement and –Analysis and Reverse engineering Use Case JT in combination with I++ can be used to store metrology surface data, tolerance information and features. These data could either be reference or analysis data. The actors of this use case are Metrology software, Measurement planning engineer, Measurement technician, Quality Engineer. The precondition of this use case is a JT file including geometric data and PMI with geometric tolerance information exists. Description The Design Engineer exports JT with PMI, structure and metadata (1). This information contains shape and positi- oning tolerances. The measurement planning engineer loads the JT file into his planning software and creates a measurement plan based on the JT data (2). The measurement plan is exported as an I++ file (3). Based on this information the measurement technician will create a measurement program for measurement (4). The measurement 10 Industrial JT Use Cases 2021-6 / V 2.0
program is also exported as I++ file (5). On a measurement system this program will create a set of points either by
tactile or optical means (6). These points will be transformed to a surface and/or feature set describing the geometric
features. These features will be stored in a JT file with geometric files and PMIs and/or are stored to an I++ file (7 abs).
A quality engineer will load this file and the original JT file from step 1 into a tool to compare geometric differences
and display PMIs related to measurement information (8, 9). A report is created to publish results (10).
Figure 10: Use case diagram "JT for 3D Measurement and -Analysis and Reverse engineering"
Benefit
JT in combination with I++ can be used for metrology process.
2.3 JT for Archiving
Use Case
The aim of this use case is that JT can be used for archiving. JT data can be extracted (automated or manual) out of IT
(CAD/PLM) systems and be used for archiving purpose. (Export from source system/later Import into target system if
necessary.) In this case Archiving means middle/long-term archiving (storage not in focus). The actors in this use case
are the release engineer the data requestor and possibly an archiving system. The preconditions for this use case are
that CAD/PLM/JT data are released and requested for archiving and an available archiving system. Additionally, it is
required that no geometric meta- and structure information is covered by PLM metadata container (PLM-Services-STEP/
PLM-XML …). The Archiving process for PLM metadata container exists in parallel to JT for Archiving process, and is
linked to it.
Description
Native data are available and released within a PLM system. Next the automated or manual archiving process starts
and the JT data is generated. The data will be stored in the archiving database (Storage/Tapes). On demand the JT
data will be restored by manual/automated processes and be transferred into the user environment. Possible variants
of this description are native data, Tiff, 3D-PDF, STEP or “microfiche” or paper based archiving.
The postcondition of this use case is that JT data are available for data requestor.
The process flow with all stakeholders and the individual process steps is shown in Figure 11.
2021-6 / V 2.0 Industrial JT Use Cases 112 USE CASES prostep IVIP Recommendation Figure 11: Use case diagram "JT for Archiving" Benefit The benefit of this use case is that the CAD/PLM archiving is independent from current and future IT infrastructure (CAD/PDM system). JT is the unique format for archiving and downstream processes. The requirements for restored data quality need to be defined. 2.4 JT for Bidding and Inquiry Use Case This use case describes using JT for bidding purposes. It does not address the bidding process itself, but much rather the preparation of it. The actors in this use case are the Procurement manager and the Data exchange engineer. The preconditions for this use case are that the PDM-tool allows neighborhood search for the assembly of components in context. Description The procurement manager sends a request to the data exchange engineer, outlining the required product data (1). Based on the procurement manager’s request, the data exchange engineer follows one of three sub-use cases: he assembles (possibly creating an assembly JT) the requested JT components (2a), if specific JT components are requested. Alternatively, he assembles JT components in context of specific product data (2b). Third, a combination of the above is possible. When the assembly of product data for the bidding process is complete, the data exchan- ge engineer or a batch-process selectively removes master data from the assem-bled data set (3). Possibly, specific materials must be prepared external of JT (4). The updated JT dataset is exported and uploaded to a business platform (5), to be acknowledged (6) for bidding. The postcondition is that a JT may be exported, storing new views and sections. The process flow with all stakeholders and the individual process steps is shown in Figure 12. Figure 12: Use case diagram "JT for Bidding and Inquiry" 12 Industrial JT Use Cases 2021-6 / V 2.0
Benefit
The benefits of this use case are that JT can be used to assemble product data and launch bidding. Thereby no
CAD-licenses are required for the assembly and no CAD-licenses are required by bidding partners.
Open issues to be detailed, in part for better understanding of the use case:
• What is the form (textual …) and content (version, configuration information …) of the procurement manager’s
request?
• How are components assembled, based on the procurement manager’s request (what are the underlying steps)?
Is this always a PDM-based procedure? How is context assembled (via bounding volumes …)? This plays a role,
because depending on the procedure, specific information is required in the JT files (certain properties and / or
bounding volumes in a specific form).
• Must kinematics be integrated as well?
• How must special materials be denoted, in order to be able to identify them and accordingly the need to separately
prepare further information thereon?
• Explain which master data must definitely remain in the JT dataset.
2.5 JT for Digital Factory Building Planning
Use Case
The aim of this use case is that JT can be used as layout data carrier and to support data exchange scenarios between
building planning and plant design. The actors in this use case are the Plant Design engineer, the Building Planner
and the Engineering Planner. The preconditions for this use case are that 3D Data for building exist and JT data and
metadata are quality checked.
Description
The Building Planner creates or updates the building layout and stores the geometry and metadata in the JT format. In
parallel the material handling equipment layout is created. The Plant Design Engineer uses the JT content and metadata
to display the plant in his CAD system. The Building Planner uses the analysis results from the Engineering Planner and
the design of the Plant Design Engineer to update the building layout.
The postcondition of this use case is that the building layout is updated with a material handling simulation and the
hull geometry of the Plant design.
The process flow with all stakeholders and the individual process steps is shown in Figure 13.
Figure 13: Use case diagram "JT for Digital Factory Building Planning"
Benefit
The benefit of this use case is that JT can reduce the size of the data amount.
2021-6 / V 2.0 Industrial JT Use Cases 132 USE CASES prostep IVIP Recommendation 2.6 JT for Digital Factory Manufacturing Planning Use Case This use case describes using JT for the development of plants or aggregates in the scope of Digital Factory (DF) activities, based on a product design. The actors of this use case are the Design engineer and the Plant development engineer. Description The design engineer creates product structure and geometry (1), and exports to JT (2). The plant or aggregate development engineer imports NF-contents into a standalone JT-viewer or a process planning tool (3), to judge producibility (4). If a product is considered not producible by in-house resources, partners are contracted. Underlying activities are out of this use case’s scope. In case the product is considered producible within a craft, a work sequence (route sheet) is defined or automatically generated (5). It represents a manufacturing strategy and includes a description of the product, as well as the materials, resources and steps (drill, mill, etc.) associated to the manufacturing process. Based thereon, a detailed production (manufacturing) concept is created (6a), possibly as a batch process based on various rules and digitalized manufacturing know-how. In order to do so, it may be required to recognize features within the product design. For example, a step within the production concept may be to drill a set of holes with certain drill-heads and constraints, for which companies typically cultivate internal guidelines depending on the type of holes, which are in turn defined as a feature by the design engineer. A detailed production concept gives insight into the way that product geometry is affected. For example, when integrating a Computerized Numerical Control (CNC)-mill into the manufacturing process, ejectors will collide with the product, possibly resulting in a mark. Such information is placed onto the JT’s geometry (6b), in addition to Reference Point System (RPS), which represent measurement positions to later verify the manufactured product against the digital product data. JT-files with affecters are imported by the design engineer (7) to be verified (8). The plant or aggregate develop-ment engineer exports different product states to JT (9), used by follow-up stakeholders, e.g. for bulk material handling. Also, with the production concept set, the detailed plant is designed, including, for example, cooling aggregates (10). When finished, its hull geometry is exported to JT (11), again for follow-up stakeholders, e.g. for updating building layouts. The postcondition for this use case is that the original JT-product data may be enhanced by manufacturing information. The process flow with all stakeholders and the individual process steps is shown in Figure 14. Figure 14: Use case diagram "JT for Digital Factory Manufacturing Planning" 14 Industrial JT Use Cases 2021-6 / V 2.0
Benefit
The benefits of this use case are that JT can be used for the derivation of a production concept and no CAD-interfaces
are required.
Open issues to be detailed, in part for better understanding of the use case:
• What are the detailed steps involved in checking for producibility?
• Generic examples of a work sequence and a production concept should be provided.
• Explain which affecters are possible and accordingly the information required in JT.
• Explain, at best by including images, how product states should be provided.
2.7 JT for Digital Factory Material Handling
Use Case
The aim of this use case is that JT can be used as the data carrier to integrate layout and product data into planning
and simulation of bulk material handling (material flow).
It is possible to provide and respectively retrieve a JT file holding as designed product structure, metadata and geometry.
The actors in this use case are the product design engineer, the building planner and the material handling planner.
The preconditions for this use case are that 3D data for building exist and JT data and metadata are quality checked.
Description
The Building Planner creates the building layout. The Material Handling Planner creates a conveyor layout. In the next
step the Material Handling Planner loads product data with structure, metadata and geometry which are created from
a Product Design Engineer and runs a material handling simulation. In the last step the simulation results are analyzed.
The postcondition of this use case is an analysis with material flow simulation results.
The process flow with all stakeholders and the individual process steps is shown in Figure 15.
Figure 15: Use case diagram "JT for Digital Factory Material Handling"
Benefit
The benefit of this use case is that JT can reduce the size of the data amount.
2021-6 / V 2.0 Industrial JT Use Cases 152 USE CASES prostep IVIP Recommendation
2.8 JT for Digital Factory Plant development
Use Case
This use case addresses JT for planning the logistical flow of a product in creation. Its aim is to identify working areas and
collisions, e.g. between aggregates (with product). The actors in this use case are the building planner, the bulk material
handling planner and the plant development engineer. The precondition for this use case is that the Building planner
communicates with plant development engineer, integrating plant hulls. This is not further detailed in this use case.
Description
The building planner creates a building layout (1), and exports it to JT (5).
The plant development engineer designs a plant (1), and exports its hull (outer geometry) to JT (3). Given components
of the plant can include kinematical connections, and accordingly information on mass, moment of inertia and center
of gravity. In designing the plant, he also derives and exports states to JT, for the product to be created (4).
The bulk material handling planner imports the building layout (6) and the plant hulls (7) to create a simulation layout.
Into this simulation layout, the different product states are imported (8). Based on the sum of this information, a detailed
simulation of the material flow is setup (9), run and analyzed for collisions.
The process flow with all stakeholders and the individual process steps is shown in Figure 16.
Figure 16: Use case diagram "JT for Digital Factory Plant Development"
Benefit
The benefits of this use case are that JT can be used to gather and combine a multitude of data and no CAD-licenses
are required.
Open issues to be detailed, in part for better understanding of the use case:
• How must product states be provided (layers within a JT file)?
• Which product states are required for the simulation? Presumably, entry and exit states to each plant suffice for
the material flow simulation.
16 Industrial JT Use Cases 2021-6 / V 2.02.9 JT for Drawingless Manufacturing
Use Case
For use in paperless manufacturing JT has to display dimensioning and PMI (Product manufacturing information).
A Complex assembly has got a high number of PMI, through that the reading of the dimensioning is getting complex.
The actors in this use case are the design engineer and the mechanical engineer. The preconditions for this use case are
a 3D CAD file with PMI information, a JT Translator which is capable of con-verting PMI from native CAD to JT. Moreover,
a viewing tool that can display PMI in JT as well as a training for end users who are used to use 2D drawings is needed.
Description
A 3D CAD file with PMI information has to be converted into JT. To improve clarity the PMI information in the JT file
are edited. Editing contains hiding, viewing and adding of annotations. Changing of annotations is not allowed. Last a
report with measurements and adaptions of the manufactured part will be created. The measurements will be stored
as annotations in the JT file. The postcondition for this use case is a JT file with PMI information.
The process flow with all stakeholders and the individual process steps is shown in Figure 17.
Figure 17: Use case diagram "JT for Drawingless Manufacturing"
Benefit
The benefit of this use case is that drawings are no longer necessary for dimensioning.
2.10 JT for ECAD/MCAD Collaboration
Use Case
The aim of this use case is that JT is used for ECAD/MCAD Collaboration between different companies, e.g. first and
second tier suppliers. Proprietary formats (e.g. IDF) are replaced in the data exchange.
The actors in this use case are the MCAD and the ECAD designer.
The preconditions for this use case are that a collaboration process is established and JT is supported by ECAD and
MCAD systems.
Description
The MCAD-Designer creates the geometry model of a part or assembly (ECU) that contains electronic components.
The ECAD-Designer creates the layout of the electronic components.
2021-6 / V 2.0 Industrial JT Use Cases 172 USE CASES prostep IVIP Recommendation Information about clearance in the mechanical design and restricted areas from the electrical design are exchanged via JT. The postcondition of this use case is that the needed geometric data is available to the ECAD and MCAD designer. The process flow with all stakeholders and the individual process steps is shown in Figure 18. Figure 18: Use case diagram "JT for ECAD/MCAD Collaboration" Benefit The benefit of this use case is enabling external ECAD/MCAD collaboration based on ISO standards. 2.11 JT for Factory DMU Use Case The aim of this use case is that JT can be used as a data carrier to exchange information between standard and high-end visualization DMU/VR-tools, and plant and building design-tools. The actors in this use case are the engineering planner, the DMU engineer, the building design engineer and the plant design engineer. The preconditions for this use are that factory and building layout have reached a certain project status and are available in JT. Description The Building Design Engineer creates und stores a certain project status of building design in CA-native format. The Plant Design Engineer creates und stores a certain project status of plant design in CA-native format. The DMU Engineer stores B-Rep geometry, structure and metadata in JT format and loads JT layout data into a DMU/VR application to present a certain project status on special visualization equipment such as power wall. He will operate model flythrough on advice of the Engineering planner. Engineering planner will lead through presentation and discuss the 3D-model in teamwork with building design engineer and plant design engineer. The team will check the complete 3D-model for intersection and clashes. In case of an incident a work sequence is created. There are analogies with certain process parts within JT for high-end visualizations and JT for Digital Factory Building Planning. The postcondition for this use case is that the data of a certain project status for the whole factory layout or the whole building and resource layout are available in JT. The process flow with all stakeholders and the individual process steps is shown in Figure 19. 18 Industrial JT Use Cases 2021-6 / V 2.0
Figure 19: Use case diagram "JT for Factory DMU"
Benefit
The benefit of this use case is that JT can reduce the size of the data amount, which enables planners and engineers
to navigate through a huge amount of Layout data.
2.12 JT for Finite Element Analysis (FEA)
Use Case
This use case describes using JT for FEA-scenarios, e.g. validating the robustness of a design based on applied forces
and materials. The actors in this use case are the design engineer and the FEM engineer. The preconditions of this
use case are that the FEA-tool is able to calculate a mesh using exact geometry provided in JT. Adaptive meshing can
be done automatically or region-driven by user-interaction. In the scope of loading simulation results (deformed and
colored JT-parts) into the CAD-system (Steps 9 and 10 to 11), there exists a mapping between JT-parts and the
respective native geometry. Accordingly, JT-parts are positioned correctly.
Description
The design engineer creates structure and geometry in a CAD-system (1). Within the design, kinematical bearings
are set up (2a), meaning mechanical connections between bodies with respective attributes or between a body and
ground. Additionally, information on fasteners, e.g. screws (2c), welds, e.g. points or seams (2d), and materials (2b) is
set. Welds are modernly provided via CAD-functionality on PMI. The design engineer exports structure, metadata and
geometry to JT (3).
The FEA engineer imports the JT-contents into the FEA-simulation tool (4), deriving a mesh from the B-Rep geometry,
automatically or semi-automatically (e.g. parameter-driven, region-driven or per-part). Specifying initial conditions
and constraints, the simulation is set up (6) and subsequently run (7). The details of the preparation phase are out of
this use case’s scope. Numerical results, e.g. a force field, are mapped to vertex data within JT, for example holding
color-encoded vertex deformations on parts with a respective color legend. By adding a respective layer (8), the de-
formed parts are integrated into the existing JT (9). Alternatively, a new JT is exported (10), holding only the deformed
and colored parts. In either case, the resulting JT-parts can be imported back into the design engineer’s CAD-system
(11), allowing an analysis therein. Based on the analysis, the existing design can be updated, defining an iterative cycle
of optimization to the analysis.
2021-6 / V 2.0 Industrial JT Use Cases 192 USE CASES prostep IVIP Recommendation
The postcondition for this use case is that the JT parts are deformed, color-encoded and displayed in the native
CAD system.
The process flow with all stakeholders and the individual process steps is shown in Figure 20.
Figure 20: Use case diagram "JT for Finite Element Analysis (FEA)"
Benefit
The benefits of this use case are that JT can be used to in part prepare FEM based simulations and there is no need
for a direct interface between the simulation tool and the CAD system.
Open issues to be detailed, in part for better understanding of the use case:
• Detail whether or not bearings can be provided by common kinematical joints, or if additional data is required
(feature technology)
2.13 JT for high-end Visualization
Use Case
The aim of this use case is that JT can be used to prepare and view high-end (photo realistically) product data. It is
possible to provide a JT file that contains structure, metadata and geometry. The actors in this use case are the design
engineer and the DMU engineer. The preconditions for this use case are that PMI’s and kinematics are included in the
metadata and JT data and metadata should be quality checked.
Description
The Design Engineer stores structure, metadata and B-Rep geometry, including material properties, in the JT files.
Alternatively, the materials and metadata can be imported from the PDM System. The DMU Engineer loads JT data into
a high-end viewer, in which he is able to associate textures and GPU shaders with parts. Additionally, he may change
further visual attributes, such as color or form of representation (e.g. wireframe or solids). The high-end viewer may be
coupled with a Virtual Reality system. Changed parts can be stored. (It is possible to import the data with or without
the B-Rep information; the PMI’s are handled correctly.)
The postcondition of this use case is that possibly changed JT parts are stored that include textures, GPU shaders and
changed visual attributes.
The process flow with all stakeholders and the individual process steps is shown in Figure 21.
20 Industrial JT Use Cases 2021-6 / V 2.0Figure 21: Use case diagram "JT for high-end Visualization"
Benefit
The benefit of this use case is that JT can be used to prepare and view high-end visualize product data.
The focus of this use case is photorealistic visualization, not DMU functionality, such as analyzing Installation Feasibility
or Packaging. This use case may, however, be seen in combination with such DMU related use cases. Accordingly:
• It is a requirement to include PMI data.
• It is a requirement to include kinematics for high-end VR scenarios.
2.14 JT for hybrid Design in Context
Use Case
This use case describes the course of using JT for design in context. The difference between non-hybrid and
hybrid display is that the context data based on JT can be loaded into the native CAD-environment, displaying native
CAD- and JT-data in parallel. JT-data is not converted to a CAD-internal format. Depending on a given set of parameters,
e.g. distance to viewer, JT-contents are visualized in respective quality via different LODs or exact geometry. The actor
in this use case is the design engineer.
Description
A design engineer creates particularly product structure and geometry (1), which is to be used as context by another
design engineer. He exports JT-files, including PMI, such as dimensions and tolerances (2). Selective features are
included as well, in order to be extracted by the receiving design engineer.
The receiving design engineer loads JT-geometry into the native CAD-system (3), which is then displayed hybrid to
native CAD-geometry, with the possibility to switch between different resolutions of tessellated geometry, or to exact
geometry (4e). This allows handling of large assemblies. Native CAD-geometry may continuously be modified, with the
addition of now being able to position CAD-data in relation to certain JT-content (4a), such as edges, vertices, faces, or
auxiliary geometry, e.g. point, axis or plane. Exact geometrical references, e.g. curves, are also possible. New PMI can
be added, associating native CAD and/or JT-based geometry (4c). Going beyond typical PMI (GD&T, surface finish,
etc.), selective advanced features, e.g. a drill hole with its parametric definition, are selected and its contents displayed
(4b). Optionally, the parametric definitions can be altered. When creating a technical drawing, new PMI and loaded
NF-content are included as well (6).
2021-6 / V 2.0 Industrial JT Use Cases 212 USE CASES prostep IVIP Recommendation If new PMI are provided based on JT, they are communicated back to the original CAD-model (5a), which is respectively updated. Likewise, if feature parameters were changed in the JT, they are communicated back to the original CAD-model (5b). The postcondition of this use case is that native CAD-geometry is positioned correctly in relation to JT-context geometry. New PMI and feature definitions are updated in the original CAD-model. Further, a technical drawing is created. The process flow with all stakeholders and the individual process steps is shown in Figure 22. Figure 22: Use case diagram "JT for hybrid Design in Context" Benefit The benefits of this use case are that JT can be used to design in the context of existing product data. Additionally, “real” Multi-CAD design is possible. Between multiple CAD systems no JT imports or direct interfaces are required. A protection of intellectual property by including only selective features is possible. A benefit is also the performant visualization (more effective work) due to lightweight JT integration. Open issues to be detailed, in part for better understanding of the use case: • Specify a subset or examples of features with parameters that are required • Specify list of assembly-level PMI types that are considered necessary 2.15 JT for Identification of Location Based Viewing Use Case The aim of the use case is the identification of location (for example molding press) dependent parts/assemblies. The actor is a worker who needs to view location dependent information (for example for evaluating of product quality). The preconditions for this use case are that the production line location information is attributed to parts and/or assemblies and that a QR-Code is locally attached. Description A worker walks to a location at production line to evaluate a certain situation (for example design vs. as-built comparison) (1). To identify the affected parts/assemblies he scans within the viewing application a QR-Code1 with the mobile device integrated camera. (2) 22 Industrial JT Use Cases 2021-6 / V 2.0
You can also read
