F. Glossary

Appendix F: Glossary The following terms are used in this user guide. Assembly An NX assembly is a file that contains components. The term assembly also refers to the product structure, as displayed in the Assembly Navigator in NX. Assembly Component An assembly component in NX is a link to another file. When the assembly file is opened, NX opens the component files, down the product structure. A component file can contain a part model, and/or a subassembly containing other components. Assembly Constraint NX assemblies can optionally contain assembly constraints, which are used to position assembly components. If a component part is edited and its size changes, the position of mating components are adjusted by the assembly constraints. Baseline Snapshot created of a specific item revision in Teamcenter. Body Term referring to a topological container of a solid body. NX refers to a closed volume as a solid body and an open quilt of surfaces as a sheet body. B-Rep Boundary representation of a solid body or sheet body. CMM Content Migration Manager A set of applications used to perform the migration from various CAD formats (I-deas, Pro/ENGINEER, CATIA) to NX. Data General term referring to parts, assemblies, and drawings to be migrated. Data is also used to refer to information inside the parts. For example, data about the migration process and fidelity data are stored in the NX dataset containing the part model. Data Access Feature (DAF) Feature in the migrated part that provides data about the parameters of a feature that could not be migrated. There may be enough information in this node to either rebuild the feature or to understand if the feature can be safely ignored. Dataset File stored in Teamcenter containing CAD-specific or other data. The term dataset is used somewhat interchangeably with file. When stored in a folder in the operating system, we generally refer to file. When stored in Teamcenter, we refer to dataset. Feature Parametric modeling steps listed in the NX Part Navigator. Features can be edited to change the resulting part. Replaying the features re-creates the part model.

Appendix F: Glossary Fidelity Check done on migrated parts. A grid of points calculated from the original part model is stored on each surface of the model. This data is stored inside the NX dataset. Glob CATIA V4 uses a concept of a glob to store multiple models in one file for the purpose of representing an assembly. These glob files are migrated into NX as NX assemblies. The type of each component is identified by attributes in CATIA. For example, routing components represent wiring and piping components. Space reservation, insulation, and shock components represent specific types of components used in CATIA to reserve clearance volume around other components. CMM recognizes these component types during the migration. GUID Globally unique identifier. An attribute associated with CAD data files to give each model a unique identifier. Internationalization Process of designing an application so that it can be adapted to various languages and regions without coding changes. Interoperability Process of associatively transferring a CAD model into NX. The master model remains in the originating CAD system. Interoperability transfers the boundary representation of the model without features, but when the master model is modified in the originating CAD system, the changes can propagate to NX. CMM does not support an interoperability process as defined here. Item Container in the data management system for a specific part number. Item revision Container within the item container in the data management system which stores all the datasets to describe a specific revision of an item. JT Proprietary Siemens PLM Software CAD data file containing a lightweight faceted boundary representation and a high fidelity boundary representation. Localization Process of adapting software for a specific region or language by translating user interface text. managed data environment CAD system connected with a data management system such as Teamcenter. Master model CAD model which is associatively used for other applications, or in other CAD systems. The features are kept and modified in the master model. When the master model is modified, the changes propagate to the other applications. For example, when a CAD model is migrated with features to NX using CMM, the model in NX becomes the master model. For another example, the master model is normally kept in one file, and a drawing in another. When the master model is modified, the drawing views can be updated to reflect the changes. metadata Attributes about each item stored by the data management system. This includes part name and number, and any other attributes assigned to the item. Appendix F: Glossary

Glossary Migration Process of transferring a CAD model with features into NX using CMM. The master model is transferred to NX in this process. This is typically a process that is done only once for each model, but CMM supports a remigration option. As much of the following information as possible is transferred:

• Part features (history)
• Item metadata
• Relationships between parts, assemblies, and drawings Model General term referring to parts, assemblies, or drawings. MultiCAD Process of using models from multiple CAD systems together in one system. The mechanism to do this in NX and Teamcenter is to use JT files to display models from the other CAD system. Native (NX) Term referring to running NX in an unmanaged data environment where files are stored directly in operating system folders. (CMM) Drawing objects migrated to an identical associative object type in NX. For example, a linear dimension migrated to an associative linear NX dimension is reported as migrated to a native object type. A drawing notation migrated into a group of lines may be migrated, but the output report will indicate that it was not migrated to a native object type. Parent (Modeling) Feature that is used in a child feature. For example, a sketch is the parent of an extrude feature. Body, geometry, or sketch from one file which is used associatively in another file. (Assemblies) Hierarchy level in an assembly that contains components. Phased migration Migration process where the lowest level data is migrated first. Assemblies and drawings are not migrated until all referenced parts have been successfully migrated. Precise Term used in NX and Teamcenter referring to an assembly where each component references a specific item revision. Revision rules Teamcenter rules used to define the behavior when new item revisions are created. Success criteria Options that control what quality of migration is considered a success in reports. These options do not have any effect on the migration. They only modify the output reports. Success criteria can also be used as part of a data management workflow. These values can be used to decide if a migrated item should be approved for use by designers. Translation Term referring to transferring CAD data between systems where the part boundary representation is transferred, but no features, relationships, or metadata. Common translation formats are IGES or STEP. Glossary

Appendix F: Glossary unmanaged data environment CAD system is not tied to a data management system such as Teamcenter. Users store files in operating system folders. No relationships between files or metadata about files are stored. Version Backup copy of a dataset. By default, Teamcenter stores three versions within each item revision for each NX dataset. Appendix F: Glossary

Index A Assembly . . . . . . . . . . . . . . . . . . . . . . F-1 B B-Rep . . . . . . . . . . . . . . . . . . . . . . . . . F-1 baseline . . . . . . . . . . . . . . . . . . . . . . . F-1 Best practices . . . . . . . . . . . . . . . . . . . 7-1 body . . . . . . . . . . . . . . . . . . . . . . . . . . F-1 C Check-mate . . . . . . . . . . . . . . . . . . . . 7-14 Check-mate testing . . . . . . . . . . . . . . . 7-14 CMM . . . . . . . . . . . . . . . . . . . 4-1–5-1, F-1 Installation . . . . . . . . . . . . . . . . . . . . 3-1 Software versions supported . . . . . . . . 3-1 CMM (Content Migration Manager) . . . . . 12 CMM Menu . . . . . . . . . . . . . . 5-6–5-7, 5-9, 5-11–5-12, 5-14–5-15 CMM Native . . . . . . . . . . . . . . . . . . . . E-2 CMM Solo . . . . . . . . . . . . . . . . . . . 6-1, A-1 Command line . . . . . . . . A-13, B-1–B-4, D-1 Component . . . . . . . . . . . . . . . . . . . . . F-1 Configuration guide . . . . . . . . . . . . . . . 3-1 Configuration options Application . . . . 9-8, 11-8, 13-4, 14-9, 16-8 Content migration . . . . . . . . . . . . . . . 9-2, 11-2, 13-1, 14-2, 16-2 Dialog box . . . . 9-1, 11-1, 13-1, 14-1, 16-1 Services . . . . . . 9-19–9-20, 11-18–11-19, 13-14, 13-16, 14-21–14-22, 16-18–16-19 Constraint . . . . . . . . . . . . . . . . . . . . . . F-1 Customization . . . . . . . . . . . . . . . . . . . D-1 D data . . . . . . . . . . . . . . . . . . . . . . . F-1, F-3 Data migration process . . . . . . . . . . . . . 6-1 dataset . . . . . . . . . . . . . . . . . . . . . . . . F-1 datasets . . . . . . . . . . . . . . . . . . . . . . . 5-4 Deep copy rules . . . . . . . . . . . . . . . . . . 3-4 Dispatcher Client . . . . . . . . . . . . . . . . . 3-5 Drawing repair . . . . . . . . . . . . . . . . . . 7-12 E Error messages . . . . . . . . . . . . . . . . . . 7-8 F Family table . . . . . . . . . . . . . . . . . 1-4, 10-4 feature . . . . . . . . . . . . . . . . . . . . . . . . F-1 Feature repair . . . . . . . . . . . . . . . . . . fidelity . . . . . . . . . . . . . . . . . . . . . . . . . F-2 G Glob . . . . . . . . . . . . . . . . . . . . . . . . . . F-2 I Installation . . . . . . . . . . . . . . . . . . . . . 3-1 Item . . . . . . . . . . . . . . . . . . . . . . . . . . F-2 Item revision . . . . . . . . . . . . . . . . . . . . F-2 Items . . . . . . . . . . . . . . . . . . . . . . . . . 5-4 J JT . . . . . . . . . . . . . . . . . . . . . . . . . . . F-2 L Linked Body . . . . . . . . . . . . . . . . . . . 6-10 M managed data environment . . . . . . . . . . F-2 Menu About . . . . . . . . . . . . . . . . . . . . . . 5-15 Clean up scratch area . . . . . . . . . . . Create CMM attributes . . . . . . . . . . . 5-12 Options . . . . . . . . . . . . . . . . . . . . . . 5-7 Release notes . . . . . . . . . . . . . . . . 5-15 Save selection . . . . . . . . . . . . . . . . . 5-7 View report . . . . . . . . . . . . . . . . . . . . 5-9 metadata . . . . . . . . . . . . . . . . . . . . . . F-2 migration . . . . . . . . . . . . . . . . . . . . . . . F-3 Index-1

Index Migration CATIA . . . . . . . . . . . . . . . . . . . . . . . 20 I-deas . . . . . . . . . . . . . . . . . . . . . . . 14 Pro/ENGINEER . . . . . . . . . . . . . . . . 22 SolidWorks . . . . . . . . . . . . . . . . . . . . 24 migration box . . . . . . . . . . . . . . . . . . . . 6-1 Migration definition . . . . . . . . . . . . . . . . 5-1 Migration prerequisites . . . . . . . . . . . . . 3-1 Migration process . . . . . . . . . . . . . . . . . 6-1 A. Identify . . . . . . . . . . . . . . . . . . . . 6-2 B. Migrate . . . . . . . . . . . . . . . . . . . . 6-4 C. Approve . . . . . . . . . . . . . . . . . . . Process mode . . . . . . . . . . . . . . . . . 7-4 Migration report . . . . . . . . . . . . . . . . . . 6-8 Migration status dialog box . . . . . . . . . . 6-6 My Teamcenter . . . . . . . . . . . . . . . . . . 5-3 N native . . . . . . . . . . . . . . . . . . . . . . . . . F-3 New features . . . . . . . . . . . . . . . . . . . . 1-1 NXM Solo . . . . . . . . . . . . . . . . . . . . . . A-1 O Options . . . . . 5-7, 9-1, 11-1, 13-1, 14-1, 16-1 CATIA . . . . . . . . . . . . . . . . . . 13-1, 14-1 I-deas . . . . . . . . . . . . . . . . . . . . . . . 9-1 Pro/ENGINEER . . . . . . . . . . . . . . . SolidWorks . . . . . . . . . . . . . . . . . . . 16-1 P Phased migration . . . . . . . . . . . . . . 7-5, F-3 PMI . . . . . . . . . . . . . . . . . . . . . . . . . 7-13 PMI repair . . . . . . . . . . . . . . . . . . . . . 7-13 Prerequisites Software versions . . . . . . . . . . . . . . . 3-1 Process mode . . . . . . . . . . . . . . . . . . . 7-4 Process Mode . . . . . . 9-9, 11-8, 14-10, 16-8 Projects . . . . . . . . . . . . . . . . . . . . . . . 5-5 R Remigration . . . . . . . . . . . . . . . . . . . . . 7-6 Report . . . . . . . . . . . . . . . . . . . . . . . . 6-8 Reporting . . . . . . . . . . . . . . . . . . . 1-1–1-2 S Scan . . . . . . . . . . . . . . . . . . . . . . . . . 5-9 Software products . . . . . . . . . . . . . . . . 4-1 Software versions supported . . . . . . . . . 3-1 Status . . . . . . . . . . . . . . . . . . . . . . . . . 5-5 success criteria . . . . . . . . . . . . . . . . . . F-3 T Task bar . . . . . . . . . . . . . . . . . . . . . . . 6-7 Teamcenter data management . . . . . . . . 5-1 translation . . . . . . . . . . . . . . . . . . . . . . F-3 Troubleshooting . . . . . . . . . . . . . . . . . . 7-8 U unmanaged data environment . . . . . . . . F-4 Index-2 Index

Siemens Industry Software Headquarters Granite Park One 5800 Granite Parkway Suite 600 Plano, TX 75024 USA +1 972 987 3000 Americas Granite Park One 5800 Granite Parkway Suite 600 Plano, TX 75024 USA +1 314 264 8499 Europe Stephenson House Sir William Siemens Square Frimley, Camberley Surrey, GU16 8QD +44 (0) 1276 413200 Asia-Pacific Suites 4301-4302, 43/F AIA Kowloon Tower, Landmark East 100 How Ming Street Kwun Tong, Kowloon Hong Kong +852 2230 3308 About Siemens Digital Industries Software Siemens Digital Industries Software is driving transformation to enable a digital enterprise where engineering, manufacturing, and electronics design meet tomorrow. Our solutions help companies of all sizes create and leverage digital twins that provide organizations with new insights, opportunities, and levels of automation to drive innovation. For more information on Siemens Digital Industries Software products and services, visit siemens.com/software or follow us on LinkedIn, Twitter, Facebook, and Instagram. Siemens Digital Industries Software — Where today meets tomorrow. © 2019 Siemens. A list of relevant trademarks can be found here. All other trademarks belong to their respective owners.