Team Center Manufacturing User and Administrator Manual

Tecnomatix Teamcenter® Manufacturing User’s and Administrator’s ManualPublication Number ENG00025 D Tecnomatix Teamcenter® Manufacturing User’s and Administrator’s Manual This product is intended for use only described in this document. UGS cannot be responsible for the proper functioning of undescribed features and parameters. Publication Number ENG00025 D 2 Teamcenter Manufacturing User’s and Administrator’s Manual ENG00025 D . ©2006 UGS Corp. Produced in the United States of America.2.4 9.2.1.2 9.Manual History Manual Revision A B (Preliminary) B C D Teamcenter Engineering Version 9. All Rights Reserved.4 2005 (V10) 2005 SR1 Publication Date May 2004 November 2004 February 2005 September 2005 June 2006 This edition obsoletes all previous editions.1.1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2 ENG00025 D Teamcenter Manufacturing User’s and Administrator’s Manual 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Process Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Releasing a Manufacturing Process Incremental Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Process Structure . . . . . . . . . . . . Classification . . . . . . . . . . . . . . . . . . . . . . 1-2 Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . Resource Manager . . . . . . . . . . . . . . . . . 5 5 5 6 9 9 9 Purpose of Teamcenter Manufacturing . . . . . . . . . . . . . . . . . . . . . . . 1-1 Scope of Teamcenter Manufacturing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Contents Preface . . . . . . . . . . . . . Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Teamcenter Engineering Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Access Control and Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3 Basic Concepts . . . . . . . . . Managing Resources . . . . . . . . . . . . Submitting Comments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Software Copyright and Trademark Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Product Structure Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1 Occurrences in the Manufacturing Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1 Revisions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using Compositions . . . . . . . . . . . 2-1 Manufacturing Planning Model . . . . . . . Multiple View Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Technical Documentation . . . . . . . . . . . . . . . . . . Customizing Functionality . 1-1 Structures and Operations . . . . . . . . . . . . . . . . . . . . . . Report Generator . . . . . . . . 2-1 2-5 2-8 2-9 2-9 2-12 2-12 2-13 2-17 2-18 2-18 Product Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . Factory Structure Editor . . . . . . . . . . . . . . . . . . 3-2 3-3 3-4 3-5 3-5 3-6 3-7 3-7 3-8 3-8 3-9 3-9 Principles . . . . . . . . . . . . . . . . . . . . . . . . . . . . Collaboration Context . . Process Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Manufacturing Structure Editor Part Manufacturing Planner . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring Processes With Rules Absolute Occurrences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Enabling the GANTT Chart for Processes and Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a Bookmark . . . . . . . . . . . . . . Using NX CAM Integration Data in Teamcenter Manufacturing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Managing Process Design With the Thin Client Interface . . . . . . . . . . . . . . . . . . . . . Index-1 Figures 2-1. . . . . . . . . . . . . . . . Verifying the Manufacturing Process . . . . . . . . . . . 5-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1. . . . . . . . . Creating a Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating Templates for Publishing Manufacturing Data . . . . . . . . . . . . Typical Process Structure Template . . . . . . . . . . . Working With Flexible Components and NX . . . . Creating an Intermediate Data Capture . . . . . . . . . . Customizing the Data Tabs Display . . . . . . . . . . . . . . . . . . . . . . . . 6-6 Glossary . . . . . . . . . . . . . . . . . . . . . . 5-2 5-4 5-14 5-14 5-15 5-16 5-17 5-18 5-18 5-23 5-25 5-26 5-26 5-28 5-28 5-28 5-33 5-38 5-43 Integrations With Other Products . . . . . . . . . . . . Example of Fabrication Process . 5-4. . . . . . 4-6 4-7 4-8 4-8 Tasks and Use Cases . . . . . . . . . . . . . . . . . . . . . . . . . 2-2. . . . . . . . . . . . . 2-4 2-5 2-6 3-6 5-12 5-19 5-19 5-20 5-24 6-2 4 Teamcenter Manufacturing User’s and Administrator’s Manual ENG00025 D . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Designing a Fixture for Manufacturing . . . . . . . . . . . . . Design and Manufacturing Representations of the Same Product Storing Different Information on the Same Components . . . . . . . . 6-6 Collaboration Context and Tecnomatix Integration . . . . . . . . . . . . . . . . . . . . . . . . . Variants and Variant Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Working With Occurrences for In-Process Assemblies . . . . 6-1 FactoryCAD Integration . . . . . . . Typical Resource in Resource Manager . . . . . . . . . . . . . . . . . . . Precise and Imprecise Structures Feature Management . . . . . . . . . . . . . . . Creating Product Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1 Index . . 5-1 Understanding the User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring Incremental Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Typical Product Structure Template . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1. . . . . . . . . . . . . . . . . Process Structure Created from Template . . . . . . . . . . . 5-1. . . . . . . . . . . . . . . . . . . . Creating Reports in the Rich Client . . . Product. . . . . . . . Displaying GD&T Symbols and Rich Text in Forms . . . . . . . . . . . . . . . . . 6-1 NX CAM Integration . . . . . . . . . . . . . . . . . .Contents Searching for Appearances . . . . or Plant Structure From a Template Creating a Preliminary Data Indicator . . . . . Creating Reports in the Thin Client . . . . . . . . . . . Example of Operation Setup . . 5-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a Manufacturing Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . Example of Baselined Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tasks and Use Cases describes the main tasks you can perform with Teamcenter Manufacturing. You should understand the contents of this manual before you design a manufacturing process or any of its components. Organization This manual contains the following chapters: Chapter 1 Chapter 2 Purpose of Teamcenter Manufacturing contains an introduction to the design of a manufacturing process and its components. Chapter 3 Chapter 4 Chapter 5 Chapter 6 ENG00025 D Teamcenter Manufacturing User’s and Administrator’s Manual 5 . Integrations With Other Products describes how Teamcenter Manufacturing interacts with external products. Product Architecture provides an overview of each Teamcenter Manufacturing application and its purpose. Principles describes some of the basic principles that Teamcenter Manufacturing applies to the design and management of manufacturing processes. Audience This manual is for persons responsible for using or administering Teamcenter Manufacturing. Basic Concepts describes some of the basic concepts behind controlling manufacturing processes with Teamcenter Manufacturing.Preface This manual describes the basic concepts behind Teamcenter® Manufacturing and includes an introduction on how to use and administer it. Teamcenter Manufacturing belongs to the UGS® portfolio of digital product lifecycle management software and services. Italic Italic font represents text or numbers that vary. A caution icon identifies practices that can either produce results contrary to what you expect or result in damage to software or data. the name of the pom_schema_server-name_sid file may be: pom_schema_Blue5_f731 6 Teamcenter Manufacturing User’s and Administrator’s Manual ENG00025 D .Preface Conventions This manual uses the conventions described in the following sections. Note. text-text A hyphen separates two words that describe a single entry. In the preceding example. pom_schema_ identifies an unvarying portion of the name. and warning messages: A note icon identifies general instructions or comments that need to be emphasized. Caution. file names. and Warning Icons The following icons represent note. server-name and sid represent varying portions of the name. For example: The file name is pom_schema_server-name_sid. The characters in italic text describe the entry. but the varying text may include uppercase letters. For example. caution. server-name is a single value. and values in fonts that help you interpret the name or value. Revision Marks Technical changes are marked by a bar adjacent to the changed text. The conventions are: Bold Bold font represents unvarying text or numbers within a name or value. Letters are shown in lowercase. In the preceding example. A warning icon identifies practices that could result in permanent loss of data or software. In the preceding example. Capitalization is as it appears. Names and Values This manual represents system names. password. For example. Italic Italic font represents text or numbers that vary.Preface Command Line Entries. The words in italic text describe the entry. The following example is a correct entry for the preceding create_change_types command: create_change_types -u=infodba -p=KLH3b -g=dba -f=change_types. group. and Code This manual represents command line input and output. the following line represents a command entry: create_change_types -u=user-name -p=password -g=group -f=file-name The conventions are: Monospace Monospace font represents text or numbers you enter on a command line. but the varying text may include uppercase letters. In the preceding example. the contents of system files. the computer’s response. and computer code in fonts that help you understand how to enter text or to interpret displayed text. In the preceding example. File Contents. the contents of system files. text-text A hyphen separates two words that describe a single entry. The words are shown in lowercase letters. use the case required by the system. and computer code. When entering text. and file-name identify varying portions of the command. create_change_types identifies an unvarying portion of the command.dat ENG00025 D Teamcenter Manufacturing User’s and Administrator’s Manual 7 . Capitalization and spacing are shown exactly as you must enter the characters or as the computer displays the characters. In the preceding example. user-name. user-name is a single entry in the command. Following is a sample syntax format: harvester_jt. In the preceding example. you supply values for bookmark-file-name and directory-name. In the preceding example..] [directory-name directory-name .bkm harvester_jt. and properties.. functions. you enter harvester_jt. Brackets represent optional elements. In the preceding example.bkm assembly124. bookmark-file-name is a single value. Italic Italic text represents values that you supply.pl assembly123.pl assembly123.bkm harvester_jt.pl: command: harvester_jt..pl exactly as shown. An ellipsis indicates that you can repeat the preceding element..] The conventions are: Bold Bold text represents words and symbols you must enter exactly as shown.pl AssemblyBookmarks 8 Teamcenter Manufacturing User’s and Administrator’s Manual ENG00025 D .Preface Syntax Definitions This manual uses a set of conventions to define the syntax of Teamcenter commands.. text-text A hyphen separates two words that describe a single value.. Following are examples of correct syntax for the harvester_jt. [] .bkm assembly125.pl harvester_jt.pl [bookmark-file-name bookmark-file-name . UGS and Teamcenter are registered trademarks or trademarks of UGS Corp. Please feel free to give us your opinion of the usability of this manual.S. UGS grants permission for Teamcenter Engineering users to print.adobe. Java and all Java-based marks are trademarks or registered trademarks of Sun Microsystems. you can use the UGS GTAC online support tools at the following URL: http://support. or its subsidiaries in the United States and in other countries.. sections. Special agreements with these vendors require UGS to handle all problem reports concerning the software they provide. All other trademarks or registered trademarks belong to their respective holders. ENG00025 D Teamcenter Manufacturing User’s and Administrator’s Manual 9 . All Rights Reserved. and to report errors.A.ugs.Preface Teamcenter Engineering Documentation Teamcenter Engineering documentation is provided as online help and as printable manuals: • You can access online help by choosing Help from the menu bar of a Teamcenter Engineering rich client application or by clicking one of the links under the Help icon in the Teamcenter Engineering thin client user interface. downloadable free-of-charge from Adobe Systems Incorporated at the following URL: http://www. MN 55126-6198 U. This software and related documentation are proprietary to UGS Corp. Please submit all comments directly to UGS. in the United States and other countries. To view the PDF-formatted manuals. Suite 3290 Arden Hills.com Acrobat Reader allows you to view these manuals online and print selected pages. To submit an incident report. duplicate. • Submitting Comments Portions of Teamcenter software are provided by third-party vendors. You can access the printable manuals from the Teamcenter Engineering Documentation CD-ROM. use Adobe Acrobat Reader. and distribute this documentation. Mail your comments to: UGS Technical Communications 4233 Lexington Avenue N.com Software Copyright and Trademark Notices © 2006 UGS Corp. or the entire manual. to suggest specific improvements. Inc. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Chapter 1 Purpose of Teamcenter Manufacturing Scope of Teamcenter Manufacturing . . 1-2 Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3 ENG00025 D Teamcenter Manufacturing User’s and Administrator’s Manual . . . . . . . . . . . . . . . . 1-1 Structures and Operations . . . . . . . . . . . . . . . . . . . . . it may be simulated to verify the reliability of the process by completing activities such as NC tool path verification and weld point allocation. • Manufacturing planning In this stage.Chapter 1 Purpose of Teamcenter Manufacturing Teamcenter Manufacturing allows you to manage assembly and fabrication of products whose design process is managed by Teamcenter Engineering. for example. This includes a complete description of the individual components (for example. geometry and tolerances) and an assembly structure. This may include designing an overall plan for the manufacture of the product. the manufacturing planning team determines how the product is manufactured. stress analysis and thermal analysis. The structures and operations you can create and maintain. and the detailed design of each individual machining or assembly step. How to use resources as part of the manufacturing process. ENG00025 D Teamcenter Manufacturing User’s and Administrator’s Manual 1-1 . After the process design is complete. This chapter contains an introduction to the design of a manufacturing process and its components. The design may require several analysis processes to ensure it meets the design specifications. Scope of Teamcenter Manufacturing The product design and development lifecycle can be broken into the following stages: • Design The development team produces the information that defines the final product. This chapter describes the following topics: • • • The scope of the Teamcenter Manufacturing product. When manufacturing commences. where. It is created by the design engineers in a CAD system such as NX and managed by Teamcenter Engineering. It establishes links between the product. You can also vary the generic bill of process (BOP) by defining and applying variant or revision rules. using manufacturing orders or other criteria. These stages are not necessarily sequential. Structures and Operations Teamcenter Manufacturing allows you to define and manage preproduction planning information and its subsequent handoff to manufacturing. and with what resources the product is manufactured. the manufacturing processes that are performed in it. During the preproduction planning. perform inventory control. the manufacturing process may be designed before the product design is complete. Its definition is independent of. and schedule activities. Process structure The process structure is the model of the complete manufacturing plan.) Plant structure The plant structure is a description of the factory in which the product is manufactured. plant layout. Teamcenter Manufacturing allows you to manage manufacturing and execution. (Optionally. Operations and resources can be shared by several processes. For example. 1-2 Teamcenter Manufacturing User’s and Administrator’s Manual ENG00025 D . and the resources necessary to produce the product. You can define multiple views of a process to allow for different manufacturing requirements. The definitions of interest to Teamcenter Manufacturing users are as follows: Product structure The product structure defines the as-designed product. It contains information about which plant structure elements are used and where. Teamcenter Manufacturing allows you to take the as-designed product structure. manufacturing execution systems (MESs) collect and manage realtime manufacturing information. create alternative manufacturing views of the product and attach process definitions as necessary. the product structure may contain definitions of manufacturing features.Chapter 1 Purpose of Teamcenter Manufacturing • Execution You can now assign the individual steps in the manufacturing plan to specific resources. but related to. using information generated in the design stage. you define how. This allows the components of a process to be manufactured before the design of the entire product is released. and describes how and where the product is manufactured. a milling workstation. and you can further configure equipment that is needed to execute a specific process operation. A work area is defined by a location on the shop floor and the process capability it provides. Shop floor equipment is typically organized into groupings called work areas. a lathe workstation. and weld guns. a plant may include a welding line. the operator loads them on the machine when the particular process operation is executed.Purpose of Teamcenter Manufacturing Process operations A process operation represents one controlled step in the process and contains the work done in one work area. the process designer provides work instructions on how to configure the work area with the additional equipment. and the sequence in which they are performed comprise the process plan. it is a leaf node in the process structure. For example. ENG00025 D Teamcenter Manufacturing User’s and Administrator’s Manual 1-3 . technically. which describes how the product is manufactured. The welding line may contain a welding workstation and a welding work cell. you can: • • • Import manufacturing feature definitions through the NX CAM Integration Share process structure information with Tecnomatix manufacturing process planning systems. If additional equipment is needed. Optionally. Teamcenter Manufacturing provides interfaces to external systems. The process structure and operations. Export information to Visiprise SCE manufacturing execution systems (MES). an NC machining center may be preloaded with standard tools that are commonly used on the machine. Resources Resources are the equipment needed for the execution of manufacturing processes. The process designer tries to use as much standard equipment in the work area as possible. If a process operation requires tools that are not preloaded. you can break a process operation into steps called activities. robots. For example. allowing you to import and export manufacturing data. You configure each work area with standard equipment. and may include machine tools. For example. and an inspection workstation. your organization may define a hierarchy of work areas. To group resources further. . . . . . . . . . . . . . . . . . . 2-13 2-14 2-15 2-16 Managing Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Process Operation Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12 Access Control and Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8 Absolute Occurrences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12 Process Operations . . . . . . . . . . . . . Configuring With Intents Controlling Access . . . . . . . . . . . . . 2-18 2-19 2-19 2-20 2-20 ENG00025 D Teamcenter Manufacturing User’s and Administrator’s Manual . . . . . . . 2-1 Process Structure . . . . . . . . . . . . . . . . . . Defining an NC Machining Process Operation Assembly and Weld Process Operation . . . . . . . . . . . . . . . 2-17 Releasing a Manufacturing Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tracking Changes . . . . . . . . . . . . . . . . . . . . . . . . . .Chapter 2 Basic Concepts Manufacturing Planning Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5 Configuring Processes With Rules . . . . . . . . . . 2-9 Using Compositions . . . . . . . . . . . . . . . . . . . . . . . . . 2-9 Process Templates . . . . . . . . . . . . . . . . . 2-18 Incremental Changes . . . . . . . . . . . . . . . . . . . . . . . Detailed work instructions describe how the operator or machine resources execute the operation. Manufacturing Planning Model The manufacturing planning model includes several interrelated process and operation types. Examples of process operations include an NC machining operation on a single machine tool and an operation to assemble several components into a structure.Chapter 2 Basic Concepts This chapter describes some of the basic concepts behind controlling manufacturing processes with Teamcenter Manufacturing. The concept of a process structure. The components of a process operation. Using process templates to aid reuse. It also maintains constraints on the order of execution between subprocesses and process operations. Using incremental changes to control modifications to manufacturing processes. Managing resources to increase manufacturing efficiency. ENG00025 D Teamcenter Manufacturing User’s and Administrator’s Manual 2-1 . as follows: Manufacturing process A set of manufacturing process operations and other manufacturing processes that are closely related to each other. Process operation An operation that describes a controlled unit of work that is executed in a single work area with a specific configuration. Maintaining access control and workflow. It is a mechanism to group operations into logical groups. This chapter describes the following topics: • • • • • • • • • The model on which manufacturing planning is based. Releasing manufacturing processes. How to configure processes with rules and occurrences. section. Consumed items Components in the product definition that are consumed by a manufacturing operation. The total time of an operation is calculated from the start time and duration of each activity. In-process model The state of the product at some stage in the manufacturing process after an operation is executed. Consumed material Items that are consumed by a manufacturing operation but are not part of the product definition. Any subsequent in-process model is created by applying a work instruction to the in-process model. resources. for example. The raw material is the initial in-process model for the first process operation in the manufacturing process. It describes a hierarchical structure of assemblies and component parts (as defined in the bill of materials or BOM). Typically. line. glue or paint. Operation setup The model of an operation-specific configuration of an environment in which processes and operations are executed. a work area is assigned to one process operation. Product structure The definition of the product as it is designed. work cell. Raw material The initial in-process model before any manufacturing operation is performed.Chapter 2 Basic Concepts Operation activities A breakdown of manufacturing process operations into activities. a paint spraying booth. Plant A hierarchical structure of work areas in which operations and processes are executed. or station. It describes how consumed items. Workstation A unique location within the factory to which you can assign manufacturing operations. Work area Any element in the plant structure such as a factory. 2-2 Teamcenter Manufacturing User’s and Administrator’s Manual ENG00025 D . and the geometric relationship between them. Resource An item of equipment that performs an operation. and a standard work area are utilized to perform an operation. A single resource can be used in several operations and processes. each with an associated start time and duration. for example. Figure 2-1 shows a simplified representation of a product and the process to manufacture it. • Teamcenter Manufacturing allows you to define templates from which you can create work instructions. Product Architecture. a weld point and its normal comprise a feature that describes where two points may be welded together. so that operation Op 20 is assigned to Cell B and operation Op 30 is performed by Lathe 2 in the same cell. and operation Op 20 has two tools and a fixture assigned to it. Program files that include code for programming numerically controlled machines. The plant where the manufacturing process takes place is also managed in Teamcenter Manufacturing. Machine instructions. ENG00025 D Teamcenter Manufacturing User’s and Administrator’s Manual 2-3 .Basic Concepts Work instructions Documents that describe how work should be performed. All such features should be associated with a process. For example. or other equipment. Instructions may be printable or accessed from a Web page. The manufacturing process comprises five operations. allowing you to reuse them in other operations. A work instruction may be: • Human readable instructions. The product contains a component called Part I and the process for manufacturing this component is currently revised to Rev B. They document the procedure by which the operator should perform an activity. robots. Manufacturing feature A set of entities and parameters that define generic manufacturing data. These tools and the fixture are stored in a Resource Manager library (see Resource Manager in chapter 3. Example of Fabrication Process 2-4 Teamcenter Manufacturing User’s and Administrator’s Manual ENG00025 D . Preparation Shop Floor (95) NC 1 for Plant A Product Release Create Mfg. Lathe 2 Mill/Turn Figure 2-1.Cell B Op 30: Machining turning Lathe 1 Op 40: Move part to inspection Mill 1 Op 40: Ship part to assembly a. Plan NC 2 for Supplier Release Plan Transfer MRP Product Product Process Process Plant Layout + Rev A Rev A Building A .Section B Part I Assign tool 1 Resource + Cell A Part II Assign tool 2 Assign fixture Fixture Library Tool Library Tool A Tool B .Chapter 2 Basic Concepts Design (606) Process Sequence Technical Dep. NC Programmer Mfg.Assy B Op 20: Machining milling .Rev B Rev B Building B + Part A Op 10: Move part to machine + Section A . it appears in the front section of the car. However. It allows you to link defined processes to the product and provide constraints on the order of process execution. Design and Manufacturing Representations of the Same Product ENG00025 D Teamcenter Manufacturing User’s and Administrator’s Manual 2-5 . The design and manufacturing representations of a product structure may be configured differently. while the design view is structured functionally. The example in figure 2-2 shows the design representation of part of a car on the left side of the screen. middle and interior). rear. In the example. the left front wheel is part of the wheels subassembly in the design representation and the identity of its absolute occurrence is 29. while the manufacturing representation appears on the right side. the identity of each component remains the same in each view. in the manufacturing representation.Basic Concepts Process Structure Teamcenter Manufacturing provides a view of the manufacturing process that may be structured differently from the product structure. The manufacturing view is divided by areas of the car (front. Figure 2-2. but the absolute occurrence identity remains 29. The example shown in figure 2-3 contains part of a car. Storing Different Information on the Same Components 2-6 Teamcenter Manufacturing User’s and Administrator’s Manual ENG00025 D .Chapter 2 Basic Concepts However. each representation may contain information that is specific to design or manufacturing. in which the doors in the design representation are closed. Figure 2-3. and does not appear in the other representation. although the components and their absolute identities are unchanged. but in the manufacturing representation are open. Different information is stored against the same components. Raw material . End 1 [1] . End caps .a subprocess to manufacture cylinder 1. ENG00025 D Teamcenter Manufacturing User’s and Administrator’s Manual 2-7 . Inspection . availability of resources. in response to feedback from the shop floor personnel when executing the process. Piston . Assembly . Painting . Crankshaft .the part is machined to its final dimensions. The manufacturing process comprises assembly and manufacturing steps. Raw material .a subprocess to capture the manufacturing process of the rod.a subprocess to manufacture the crankshaft. Assembly Operation .the alternate process to manufacturing End 1.a process operation to cut the raw material.a subprocess to manufacture the piston. Crankshaft assembly Cylinder 1 . NC machining finish .an NC machining process for rough cut.a subprocess to manufacture assembly level 1.machining the part to its final shape.the rough part goes through heat treatment. Inspection .cutting the initial raw material. NC machining rough .inspecting the part. Machining .assembly process operation to assemble the rod and piston. Assembly level 1 . End 2 .an assembly process to assemble the four pistons to the crankshaft. and time.a subprocess to capture all activities of manufacturing the rod and piston.a subprocess to manufacture the end caps. Painting End 1 [2] . Processes may also be revised independently of the product. Processes may vary according to the location of their execution. which must be executed in the correct sequence. The hierarchy of the processes and operations is as follows: Crankshaft Assy Rod and Piston .the manufacturing process of End 2. Heat treatment .the manufacturing process of end 1.the part is painted. Rod .Basic Concepts The following example shows the process for manufacturing a crankshaft.the part is inspected. as described in Product Structure Editor Help. For example. 6. If the revision rule for the product configures Working revisions. 3. The manufacturing process for the dashboard mounting includes the following steps: 1. 5. For example. • Revision rules You can load appropriate revisions of processes by applying predefined revision rules. the configuration rules of the product may automatically configure the associated manufacturing processes. 4. processes 1. the product structure for a vehicle may include options for a CD or tape player. 7. 4. you can specify different process for the manufacture of item End 1 according to the process capabilities of the location. 2. you can use the rule to automatically configure the appropriate manufacturing process for building the working revision. 5. You can configure processes to accommodate variations in product structure in several ways: • Variant rules You can define options at the top level. Make the instrument panel. and 6 can be configured automatically in the process definition. For example. 3. When the CD player is selected. and the process definition is tightly integrated with the product definition. Working and Released. and 7 can be configured.Chapter 2 Basic Concepts Configuring Processes With Rules A manufacturing process is designed for a specific product. Assemble the molding and instrument panel together. the product includes occurrence A. Assemble the tape player into the vehicle. Buy or make the tape player. When the tape player is selected. Each revision has a different manufacturing process. 2-8 Teamcenter Manufacturing User’s and Administrator’s Manual ENG00025 D . You define and apply revision rules for the product in Product Structure Editor. 2. Make the molding. which has two revisions. Although the manufacturing process has configuration rules that are independent of the product configuration rules. processes 1. then define rules for each process derived from those options. Assemble the CD player into the vehicle. 3. 2. You can also use the product revision rules to control the process structure. Buy or make the CD. Technically. creation of absolute occurrences is not enabled and the user must select absolute occurrence editing mode to permit this. that is. ENG00025 D Teamcenter Manufacturing User’s and Administrator’s Manual 2-9 . However. In this case. You can also attach forms and datasets to an absolute occurrence. Instances of occurrences from other representations. Absolute Occurrences Absolute occurrences allow you to manage data that is unique to a specific application of an item in a process or product structure. You can edit BOM line property values in context to create an absolute occurrence. For example. an absolute occurrence represents a specific BOM line in the context of the top line item. Instances of occurrence groups. An instance of the representation of the top-level item is created and filtered to show only the occurrences that are members of the occurrence group (with its subgroups and members). By default. • Alternates You can define alternate processes and select a preferred alternate. you can create absolute occurrences of these subassemblies in the manufacturing environment with the required pressure set on each absolute occurrence. each of which may contain a different product structure.Basic Concepts • Effectivity rules You can set effectivity dates on processes in a similar way to which they can be applied to the product structure. for example. a specification describing the reason for the tire pressure change. Any changes affect only the current context. you can place a product view of an assembly and the corresponding process view in a composition for review and approval purposes. you manufacture a vehicle that is designed with four identical wheel and tire subassemblies. Using Compositions A composition is a special kind of structure context that allows components to be added from one or more structure contexts. while the rear tires must be inflated to 30 PSI. A composition may contain any of the following: • • • An instance of the representation of any top-level item. the front tires must be inflated to 33 PSI. the structure currently displayed. You can also define a range of unit or product serial numbers against which the process is effective. A new instance is created and associated with an occurrence in the source representation. To accommodate this difference. For example. the composition includes the complete representation. A composition typically models a scenario or manufacturing process. editing.Chapter 2 Basic Concepts When you create a composition. Using any member of an occurrence group as the top level context for creating and editing absolute occurrences. removals or changes are made to the source BOM line. it is treated as a single occurrence for all purposes. and manipulating graphics. you can manage and edit the occurrence groups in it in the same way as any other BOM line. If no editing context is defined. Configuring members of an occurrence group to match the configuration of the source view. Changing their position in any context. If an occurrence is a member of several occurrence groups in a single hierarchy. If you change the position of a member of the group. the occurrence line in the composition is updated accordingly. Comparing occurrence groups and their members. the in-context edit must be set to the appropriate context. This action creates a persistent absolute occurrence and the occurrence path representing the line in the composition. the relative position is changed. including: • Attaching data to occurrence groups in the context of the top line composition or any other context. it is grayed out in the composition. • • • • • • • • • If additions. Creating connection interfaces on the members of the occurrence group. If a member does not exist in the source. Defining item elements (GDEs) and connections as part of the occurrence group. 2-10 Teamcenter Manufacturing User’s and Administrator’s Manual ENG00025 D . Creating and retrieving 2D product views (snapshots) in compositions containing instances of occurrence groups. Attaching a 3D markup to them in the viewer. Creating. This may be done in one of the following ways: • If a configuration context is stored on the BOM line of the referenced structure (by association with its occurrence or absolute occurrence). • • • • The BOM line you select as the context must be a parent or ancestor of that member on the composition. the root item of the source BOM of the group is the context of the association.Basic Concepts Associating Data in the Context of a Composition When you associate absolute occurrence data to a member of an occurrence group in a composition. If the selected line is a subgroup in the instance of the occurrence group that brought this member into the composition. the context of the association is the root item of the source BOM of the occurrence group. Configuring Referenced Structures in a Composition You can configure members of a referenced structure in a composition from the configuration of the source BOM. If no line is selected as the context. any configuration context associated with a higher level overrides one attached at a lower level. the selected line is the context of the association. A referenced structure may be a subassembly. The final configuration of the referenced structure and its components also depends on the configuration of the composition BOM. If the selected line is a subassembly (not a subgroup) in the instance of the occurrence group that brought this member into the composition. If there is no stored configuration context and the source BOM is not open. Consequently. In general. the selected line itself is the context of the association. A subassembly or component is configured in a composition if it is successfully configured in both the composition BOM and the source BOM. Teamcenter applies the following rules to determine the context of the association: • If the selected line is a line higher than the instance of the occurrence group that brought this member into the composition. A subgroup cannot be a context if it does not exist in the hierarchy of the source BOM. the same data is attached to the same member in every instance of the occurrence group. the reference structure takes the same configuration as the one in the source BOM. If there is no stored configuration context. the referenced structure does not appear in the composition. single component. but the referenced structure is open and active in the source BOM. if multiple instances of the association are referenced in the composition. If the selected line is the instance of the of the occurrence group that brought this member into the composition. • • ENG00025 D Teamcenter Manufacturing User’s and Administrator’s Manual 2-11 . the referenced structure is configured by this configuration context. or occurrence group. the actual parent of this member in the source BOM is the context of association. After it is created. Teamcenter Manufacturing loads the related method. and manufacturing operations. Access may be further refined by subgroup. process planners design standard processes that are reused several times for different products. and may include references to standard resources. equipment. features. you can attach the geometry of the part to be processed. For example. and define the configurations of processes. When you create a new process operation. then use the templates as the basis of new manufacturing processes for similar products. the basic structure of the manufacturing process for a car is similar for a basic model or a premium model. you can create assembly setup templates containing assembly information for a typical assembly setup. For example: • The manufacturing engineer or process planner should have full permissions to access and modify process data. allowing the Teamcenter Engineering administrator to define appropriate access control privileges to the manufacturing processes. • • You define access permissions in access control lists (ACLs) with the Teamcenter Engineering Access Manager application.Chapter 2 Basic Concepts Process Templates In many manufacturing environments. Access Control and Workflow Manufacturing processes and operations are represented as items. 2-12 Teamcenter Manufacturing User’s and Administrator’s Manual ENG00025 D . Users in this group can view process data such as work instructions. Users in this group can change process operation sequences. For example. The template may include configuration rules that map the product data to process operations. but not make changes. an NC machinist may only have access to NC machining process operations. You can save such manufacturing processes as templates in a library. Similarly. When you initialize a setup from a template. you can browse the available templates and select one to create the process operation. Shop floor (assembly) personnel have read-only access to process data. examples of which include: • • • • • • Machining steps Painting Quality control Heat treatment Assembly Welding Each process operation has work instructions that describe how the operation is performed in an appropriate form. The engineer also produces work instructions for setting up the robot and procedures for the operator that must be completed before and after the robot executes the program. All this information is collectively managed as part of the NC machining process operation. for example. The manufacturing engineer may provide tooling instructions and setup procedures with the NC programs. ENG00025 D Teamcenter Manufacturing User’s and Administrator’s Manual 2-13 . The manufacturing engineer produces the work instructions as part of the process operation design activity. Similarly. for example. Work instructions can be generated by a software application that is integrated with Teamcenter Manufacturing. or tool list.Basic Concepts Process Operations A process operation describes one step in the manufacturing process of a product. the work instructions may be in the form of a robot program. you can generate NC programs in NX. an NC program. when the manufacturing engineer designs an assembly process operation. document file. Each manufacturing process includes many types of process operations. and is executed at one work area. the requirements may be included in the work instructions and the assignment may be made on the shop floor when the process operation is executed. The process designer may also set analysis data prior to completing the design to estimate time and cost from the available high-level information. setup information. it may be specified in the work instructions. 2-14 Teamcenter Manufacturing User’s and Administrator’s Manual ENG00025 D . but a specific machine may not be preassigned. It may include tooling information. You can perform analysis for one process operation or many process operations. The result is a modified in-process model and any instructions necessary for the next steps. If you do not explicitly assign it to a work area. • Work instruction data This information is created by the designer of the process operation and contains all the information necessary to complete the work. • Work area You can associate each process operation with one work area.Chapter 2 Basic Concepts Process Operation Data Each process operation may be associated with one or more of the following data types: • Input data This data is obtained from one or more of the previous steps of the in-process model. and the actions necessary to execute the operation. time and a manufacturing features list. • Output data Output data is generated by applying the work instructions to the input data. both the standard equipment of the work area and any additional equipment needed for the specific process operation. Each item in the product structure should be associated with a manufacturing model that the manufacturing engineer uses to develop the work instructions. • Product You can associate one or more items in the product structure with each process operation. the process may be performed on a three axis machine. • Equipment The process operation references all equipment required. • Analysis data Analysis data is derived from the work instructions and may include cost. For example. If you do not explicitly define the work area. shop floor personnel assign a machine according to their availability when the process operation is executed. Basic Concepts Defining an NC Machining Process Operation When you design an NC machining process operation. such as pocket. • Tools The cutting tools used in manufacturing operations to cut features. • Machining manufacturing features The geometry definitions of the manufacturing operations. hole. and tapping. mill-finish. The generic items associated with an NC process operation include: • Machine tools An NC machine that executes the NC program. in turn. slots. the tool path. center-frill. and tap. A tool path can be automatically generated from this description. you create an NC program. ENG00025 D Teamcenter Manufacturing User’s and Administrator’s Manual 2-15 . It must be included in the equipment definitions. mill-rough. such as mill. reaming. • NC manufacturing operation A description of how one tool moves in relation to a feature’s geometry. lathe. • Program A collection of manufacturing operations in the order of execution. ream. You may also generate setup instructions and a tool list for the machine operator. which are work instructions utilized by the NC machine to machine manufacturing features. generates the NC program. • Machining method The types of cuts that are performed during manufacturing operations. • Assembly sequence Describes the order in which assembly manufacturing operations are executed. The work instructions may contain robot programs if the assembly process operation uses a robot to perform some assembly actions. and move. • Assembly manufacturing operation Describes how a component moves with one tool or operator during the assembly sequence. • Assembly components Create assembly manufacturing operations to move these items to the correct positions. • Assembly method You can define general assembly methods such as weld. The generic items associated with an assembly and weld process operation include: • Robots and weld guns This equipment performs assembly instructions.Chapter 2 Basic Concepts Assembly and Weld Process Operation An assembly process operation provides the work instructions for assembling parts in a work area that is designated for assembly operations. 2-16 Teamcenter Manufacturing User’s and Administrator’s Manual ENG00025 D . glue. the planner might decide to buy material from external suppliers instead of manufacturing in-house to avoid resource constraints. ENG00025 D Teamcenter Manufacturing User’s and Administrator’s Manual 2-17 . A process operation can directly identify that a specific work area in the resource structure is needed to execute it. robots may weld assemblies. • Resource authors Users with this role define new resource components. For example. In this case. any arc welding robot on the shop floor can execute an arc welding process. In the case of a weld process operation. For example. the process definition influences the quality and layout of the resources. but a different resource (a manual welder) executes the operation. It must be included in the equipment definitions. Manufacturing execution systems (MESs) marshal the process definitions and the product order size. The process planner may receive feedback from the MES system and modify the process definition to improve performance. Process operations may only specify a requirement of the required resources. assemble components into standard tool assemblies. it may specify a weld workstation on the shop floor and a specific weld gun as the resources required for its execution. They may also be plant workers who use the process plans and update the resource inventory. The availability of resources affects the definition of manufacturing processes. You can use the assigned resources and the process requirements to estimate the time needed for execution. In locations such as assembly plants where meeting throughput requirements is critical. and assign jobs to specific resources according to their availability. the weld process operation does not directly reference specific instances of the weld work area and weld guns. in an automated assembly plant. In plants where weld robots are unavailable. Users of resources fall into three general categories: • Machine tools An NC machine that executes the NC program. the same manufacturing process may be followed. and define the attributes and properties of the components and assemblies. • Resource consumers Users with this role are manufacturing engineers who define process plans that utilize resources already defined by the authors.Basic Concepts Managing Resources Process operations require resources to execute them. For example. occurrence. For example. Teamcenter Manufacturing allows you to baseline a process structure (or a composition) and create a PDI in a single operation. the structure of part 100 may have been originally designed with two occurrences. An intent represents an event or alternate solution that is not bound to a date or unit number effectivity. and you can configure the various components. ensuring that all grouped additions and removals happen at the same time.Chapter 2 Basic Concepts Releasing a Manufacturing Process After you complete a manufacturing process. 2-18 Teamcenter Manufacturing User’s and Administrator’s Manual ENG00025 D . You can also provide intermediate releases of work-in-progress process designs for others to view. Consumers of a PDI can then work with the data. Incremental Changes You can control changes to the manufacturing process. Consequently. If you view the structure of part 100 for an effective date after the change occurred. approval and release processes. you may define an intent as a new prototype and group all changes required to build the prototype accordingly. You can define an effectivity for an incremental change. This intermediate snapshot of data is sometimes referred to as the preliminary data indicator (PDI). A design change is made that cancels the occurrence of part 300 and adds an occurrence of part 400 in its place. You can attach relevant data to an incremental change. as described in Workflow Help. Teamcenter Manufacturing allows you to create incremental changes to add components to and remove them from the structure. dataset. knowing that it will not change until the next PDI is released. For example. or attachment in the structure. These removals and additions remain linked to the incremental change order that carries the effectivity of the change. Teamcenter Manufacturing does not provide review. An incremental change order (ICO) groups several individual changes that can be released simultaneously to a baseline of the process or product. you may want to make it available for review and approval before manufacturing commences. The PDI may not be valid if this related data changes. or folder. but you can develop suitable processes with the Workflow application. you must also baseline any related structures at the same time. one of part 200 and the other of part 300. structure. You can also use incremental change to view the definition of a structure effective of a certain date or unit number. As many changes may be small and not related to each other. For example. or operations by revising the affected items. occurrences and attachments to a specific revision by applying appropriate revision rules. Each incremental change consequently comprises several individual and possibly unrelated revisions to a component. You normally assign an effectivity expressed as a date range or sequence of serial numbers to the change order. if you create a baseline of the process in this way. including a form. The process and its operations may reference occurrences of product data and plant data. you may want to attach the individual change requests that are satisfied by the incremental change. you see only parts 200 and 400. An incremental change may have revisions. You can also create intents to an incremental change. allowing (for example) all changes related to the production of a new model to be implemented simultaneously. are not visible to the user but may be accessed by advanced users. the change is applied. if the changes are already made but were not originally tracked against an incremental change. which allows you to still modify the incremental change. If Released status is applied. a removal is configured in preference to an addition. Addition and removal of attachments to an operation. You define a release status (typically Released) that applies the defined effectivity. These individual change elements. Changes that are tracked and recorded against an incremental change are: • • • • • Addition of activities to an operation. If more than one change affects an occurrence according to effectivity. The configuration rules that are applied to a component or attachment are as follows: • • If an occurrence has an associated change and the incremental change associated with that change is configured. The user can choose to view all configurations associated with an incremental change or to hide those components and attachments that are not configured by the current revision rule. you can no longer modify the incremental change. such as the addition of an occurrence or removal of an attachment. Changes to predecessor occurrences of processes or operations. Changes are normally tracked dynamically. ENG00025 D Teamcenter Manufacturing User’s and Administrator’s Manual 2-19 . these changes are recorded against the specific incremental change. Configuring Changes You can release a revision of an incremental change with an appropriate workflow. including forms and datasets. You can then apply further incremental changes to the baseline. as the user makes edits with an active incremental change. Tracking Changes When data changes in the context of an incremental change. Removal of activities from an operation. You can also release a revision of the incremental change with a Preliminary status. Creation of data such as forms and datasets.Basic Concepts You can also baseline changes by rolling up several incremental changes that apply to a certain date or unit number into a new single baseline revision. Changes may also be tracked retrospectively. Intents may optionally be configured by a revision rule. Controlling Access To create incremental changes against a structure. you may configure several alternative processes for evaluation and discussion and identify them as Alternate Process 1.Chapter 2 Basic Concepts Configuring With Intents You can define intents to represent milestones or events that cannot be defined by a date or unit number effectivity. The Teamcenter Engineering administrator controls this access with the Access Manager. Alternate Process 2. You can optionally apply one or more intents to an incremental change. Any incremental change that matches an intent set in the revision rule is selected. For example. a user must have access to the revision of the incremental change. An intent is applied to all revisions of the incremental change. when appropriate. You can configure an incremental change with both intents and effectivity. the incremental change is valid for all of those intents. and so on. 2-20 Teamcenter Manufacturing User’s and Administrator’s Manual ENG00025 D . as follows: • • • • If you apply several intents to an incremental change. 3-8 Customizing Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3 Part Manufacturing Planner . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9 ENG00025 D Teamcenter Manufacturing User’s and Administrator’s Manual . . . . . . . . . . . . . . . . . . . . . . 3-6 Report Generator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5 Resource Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Chapter 3 Product Architecture Prerequisites . 3-9 Technical Documentation . . . . . . . . . . . . 3-4 Multiple View Editor . . . 3-2 Manufacturing Structure Editor . . . 3-5 Factory Structure Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7 Collaboration Context . . . . . . . . . 3-8 Product Structure Editor . . . . . . . . . 3-7 Classification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Chapter 3 Product Architecture Teamcenter Manufacturing includes several applications through which users define and manage manufacturing processes. This chapter provides an overview of each application and its purpose. This chapter describes the following topics: • • • • • • • • • • • Prerequisites that must be completed before you use Teamcenter Manufacturing. The purpose and features of Manufacturing Structure Editor. The purpose and features of Part Manufacturing Planner. The purpose and features of Multiple View Editor. The purpose and features of Factory Structure Editor. The purpose and features of Resource Manager. The purpose and features of Report Generator. The purpose and features of Collaboration Context. The purpose and features of Classification. How to customize the operation of Teamcenter Manufacturing. The technical documentation provided with Teamcenter Manufacturing. ENG00025 D Teamcenter Manufacturing User’s and Administrator’s Manual 3-1 Chapter 3 Product Architecture Prerequisites Teamcenter Manufacturing provides an overlay that enhances the functionality of Teamcenter Engineering. Before installing and using Teamcenter Manufacturing, you must install and configure Teamcenter Engineering and its associated Oracle or SQL server database. You should refer to the Teamcenter Engineering technical documentation for information on how to install and configure the base product. When the base product is installed, you run a script that installs the Teamcenter Manufacturing overlay. If you using certain advanced functionality such as the collaboration context integration with Tecnomatix process planning software, you must install additional components. Several of the applications described in this section require licenses in addition to the standard Teamcenter Manufacturing product license. For details, contact your UGS representative. Some of the data tabs you frequently use to manage manufacturing data may not be available in your default environment. For details of how to add and remove data tabs, see the Rich Client Customization Programmer’s Guide. 3-2 Teamcenter Manufacturing User’s and Administrator’s Manual ENG00025 D operations. Create templates for processes. You can also identify the specific locations within the plant where each operation and activity is performed. For detailed information about how to use Manufacturing Structure Editor. As you build the process structure. and activities. variant rules and occurrences. Assign data to projects. Create or edit manufacturing views of the product. The manufacturing process plan includes a top-level structure of the process needed to manufacture the product. Create new operations as part of the process structure. The main activities that you can accomplish with this application are: • • • • • • • • • • • • • • Open a product structure that was created in Teamcenter Engineering. Create an intermediate data capture. and their position in the process. ENG00025 D Teamcenter Manufacturing User’s and Administrator’s Manual 3-3 . as well as a detailed design of the individual processes and activities included in the plan. Assign a classified resource to an operation. Import manufacturing features such as weld points from NX. see Manufacturing Structure Editor Help. you can assign resources to the various processes. Create or edit the plant structure which describes the hierarchy of work areas or locations in the factory where manufacturing operations are performed. Analyze the manufacturing process to ensure all components are consumed and are not consumed more than once. you can assign it as the target of a manufacturing process. Configure process structures with incremental changes. resources. When the product is open. Create a process structure for the target product. Create a preliminary data indicator (PDI) of the process structure. operations. Create or edit a setup structure that contains the tooling. You can also edit an existing process structure. parts.Product Architecture Manufacturing Structure Editor Manufacturing Structure Editor allows you to design a plan that details how to manufacture a product that is an assembly. and workpieces. or edit an existing operation. and activities. The main activities that you can accomplish with this application are: • • • • • • • • • • • • • Open a product structure that was created in Teamcenter Engineering. variant rules. and their position in the process. but several resources such as machine tools. resources. Configure process structures with incremental changes. Create an intermediate data capture.Chapter 3 Product Architecture Part Manufacturing Planner Part Manufacturing Planner allows you to design a plan that details how to manufacture a piece part product. Assign data to projects. Create or edit the plant structure which describes the hierarchy of work areas or locations in the factory where manufacturing operations are performed. Analyze the manufacturing process to ensure all components are consumed and are not consumed more than once. You can also identify the specific locations within the plant where each operation and activity is performed. drilling. You can plan the production process from raw material to end product. including cutting. operations. Assign one or more classified resources to an operation. Import manufacturing features such as weld points from NX through the NX CAM Integration. fixtures. and occurrences. 3-4 Teamcenter Manufacturing User’s and Administrator’s Manual ENG00025 D . and activities. cutting tools and gages are necessary. Create templates for processes. as well as a detailed design of the individual processes and activities to be included in the plan. and activities. In this environment. and workpieces. or edit an existing operation. see Part Manufacturing Planner Help. and quality checking operations. parts. operations. When the product is open. there is typically no production line. As you build the process structure. Create new operations as part of the process structure. Create or edit a setup structure that contains the tooling. you can assign resources to the various processes. milling. Create a process structure for the target product. The manufacturing process plan includes a top-level structure of the process needed to manufacture the product. For detailed information about how to use Part Manufacturing Planner. You can also edit an existing process structure. turning. such as a piston or engine fan blade. Attach work instructions to the process or operations. you can assign it as the target of a manufacturing process. variant options. Visualize your plant structure layout. and export a factory structure. View and edit the sequence of operations performed on the product on the shop floor. see Factory Structure Editor Help. Configure the product manually or with occurrences. alternative views of the product structure.Product Architecture Multiple View Editor Multiple View Editor allows you to create associative. see Multiple View Editor Help. You can: • • • • • • Create manufacturing-specific views of the product. then import it into Factory Structure Editor. then visualize the results. and organize the areas where the product is manufactured. • • • For detailed information about how to use the Factory Structure Editor. modify. including changes to transformations. ENG00025 D Teamcenter Manufacturing User’s and Administrator’s Manual 3-5 . Create an intermediate data capture. Rearrange the product structure hierarchy for manufacturing purposes without losing the association between the product and the process structure. View and edit a representation of the flow of materials between operations. • • For detailed information about how to use Multiple View Editor. Update the manufacturing view automatically when the product structure is updated. Assign components from the product view as consumed items and workpieces. Create a preliminary data indicator (PDI) of the factory structure. you create the detailed design of the factory structure in FactoryCAD. import. options. Typically. and revisions. Factory Structure Editor Factory Structure Editor allows you to: • Create. Create an intermediate data capture. and component additions and deletions. and process templates.Chapter 3 Product Architecture Resource Manager Resource Manager allows you to store and retrieve resources such as tools. see the Resource Manager Help. View the resource in the assembly viewer if a visualization (JT) file is attached to it. Search for classified resources by characteristics. 3-6 Teamcenter Manufacturing User’s and Administrator’s Manual ENG00025 D . Generally. for example. Resource Manager stores this data in combination with classification information. Send resources to other Teamcenter Manufacturing applications to include in processes. machines. the administrator creates and maintains each resource. Classify resources into hierarchical schemes with the Classification application described later in this chapter. Create resource reports. and it is organized into a hierarchy that is specific to your company. note that all properties fields are read-only. and activities. its properties and any attachments. In the example. Resource data is held in a database that is accessible to all users. AutoCAD files. Browse to identify where resources are used in the structure. You can: • • • • • • • • • Create and modify resource components and assemblies. Create and view attachments to resources such as work instructions in Microsoft Word format or alternate geometric representations. Typical Resource in Resource Manager For detailed information about how to use Resource Manager. You can configure the system such that other users can only view and consume the resource. operations. Figure 3-1. fixtures. Figure 3-1 shows how a manufacturing resource is stored in Resource Manager. Generate setup sheets. when collaborating with suppliers or exchanging data with a third-party application. A structure context contains one or more structures of the same type or different types. For detailed information about how to use the Report Generator. see Report Generator Help. For detailed information about Resource Browser. The configuration of a structure context is determined by the effective configuration context. for example. activities. and closure rules that define objects of interest. For detailed information about how to use Collaboration Context. You can also create a preliminary data indicator (PDI) of any structure in a collaboration context. This information can be printed or viewed. and you can create your own customized reports. ENG00025 D Teamcenter Manufacturing User’s and Administrator’s Manual 3-7 . which may include revision rules. part of a process. The structure context may include top-level items. Collaboration Context The collaboration context feature allows Teamcenter Manufacturing to share data in a process or product structure with another application such as Tecnomatix process planning software. The shared data can be managed or modified by either application and any changes are available in both environments. making it available to users who do not have access to Manufacturing Structure Editor. for example. a selected option set. see Resource Browser Help. A collaboration context is a collection of structure contexts that are used for a specific task. see Collaboration Context Help. Collaboration contexts are used when it is appropriate to create subsets of data in support of a particular business process. The Resource Browser application allows you to view and manipulate resource data that is shared in a collaboration context from the external application. or occurrence groups. Certain default reports are provided.Product Architecture Report Generator Report Generator allows you to create reports about the process plan and related operations. item revisions. Use compositions to bring together positioned elements from different structures. product structure. and plant structure. Create structure contexts in a collaboration context when it is necessary to store configuration rules with the structure data. 3-8 Teamcenter Manufacturing User’s and Administrator’s Manual ENG00025 D . You can: • • • • Develop a classification hierarchy for your company with the Classification Administration application. • For detailed information about Classification. When you design or revise the manufacturing process. the product configuration effective for a particular date or serial number range. A product structure managed by Product Structure Editor is the starting point for the design of your manufacturing process. and can be configured to show (for example) the product that is in production. Use change management to control revisions to classified items. Assign classified resources to the manufacturing process with Resource Manager. For detailed information about Product Structure Editor. you can use Product Structure Editor to view or edit information about the original product design. or a specific variant. Product Structure Editor Product Structure Editor allows you to manage design product structures. see Classification Help and Classification Administration Help. Search the classification hierarchy for classified resources.Chapter 3 Product Architecture Classification Classification allows you to classify all the resources associated with the manufacturing process. in this context. see Product Structure Editor Help. You can associate a graphical representation of the item with each member of a part family. as described previously. Associate a part family template to each class (a part family. may contain a particular type of tool). and querying for activities. Creating occurrence paths. Showing and hiding incremental changes. changing. For descriptions of these APIs. Creating operations. BOM line predecessors and incremental changes. and retrieving closure rules. PLM XML import and export functionality. Creating. Manipulating collaboration contexts. or press F2 to show the launch page for all online help modules. The published APIs allow you to customize or manipulate the following main areas of functionality: • • • • • • • Adding and creating occurrence groups. You can also press the F1 key to show online help for the active applications. Setting and retrieving configuration contexts. Certain Teamcenter Manufacturing technical documents are also provided in Adobe PDF format on the documentation CD provided with the release software. Creating and revising processes. changing. and removing structure contexts. Adding and removing closure rules.Product Architecture Customizing Functionality Teamcenter Manufacturing publishes APIs that allow you to customize the operation of your system or perform certain functions programmatically. Adding. Creating. and variant rules. Showing. Creating and revising work areas. revision rules. Setting. and hiding occurrence type filters. as follows: – – – – • • • • • • Creating and setting a collaboration context. Technical Documentation Teamcenter Manufacturing is supported by technical documentation that is available when you click the Help button in any of the product applications. retrieving. changing. ENG00025 D Teamcenter Manufacturing User’s and Administrator’s Manual 3-9 . see the Integration Toolkit Function Reference. setting. adding to. and removing occurrences. . . . 4-2 4-2 4-4 4-4 4-5 4-5 Searching for Appearances . . . . . . . . . . . . . . . . . . 4-8 Feature Management . . . . . . . Associating Data With Occurrences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8 ENG00025 D Teamcenter Manufacturing User’s and Administrator’s Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6 Variants and Variant Rules . . . . . . . . . . . . . . . . . . .Chapter 4 Principles Revisions . . . . . 4-1 Occurrences in the Manufacturing Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Occurrence Paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7 Precise and Imprecise Structures . . . . . . . . . Editing the Components of a Process Structure Editing the Process Structure View . . . . . . . . . . . . . . . . . . . . . Examples of Occurrences in Manufacturing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . For example. for example. Precise and imprecise structures. Revisions have a particular effectivity. you can specify that the new process or operation takes effect on a particular date or product number. Managing features. expressed as a date range or sequence of product serial numbers. Variants and variant rules. ENG00025 D Teamcenter Manufacturing User’s and Administrator’s Manual 4-1 .Chapter 4 Principles This chapter describes some of the basic principles that Teamcenter Manufacturing applies to the design and management of manufacturing processes. if you change the operation to use a different machine. The item contains the information about the process or operation that does not change. a single item may represent the operation in which the crankshaft is assembled onto the engine. When you revise an item. Revisions Each manufacturing process and operation is represented in the system by an item. Each item has one or more revisions that contain information that changes. the item revision of an operation may specify a particular operation that requires a specific welding machine. you revise the operation and create a new item revision. This chapter describes the following topics: • • • • • Revising processes and operations. Using occurrences. You can define revision rules that determine the revision of the item that is loaded in any particular situation. Occurrence groups may contain occurrences of parts and subassemblies that are not necessarily grouped together in the product design. you can create occurrences of each location of the robot relative to the standard component. • Installation cost The cost of installing a robot may differ from one area of the factory to another. To define this condition for the manufacturing process. or other attribute of the item at a specific point in the manufacturing process. Examples of Occurrences in Manufacturing The following list shows some examples of how occurrences may be applied in the manufacturing environment: • Variation from the design scenario Flexible components may change their shape in the context of a top-level product. You can combine multiple occurrences into occurrence groups in Teamcenter Manufacturing to model assembly and manufacturing requirements. it absorbs the weight of the car and becomes compressed. the occurrence of the assembly process for the left front wheel of a vehicle differs from the occurrence of the right front wheel.Chapter 4 Principles Occurrences in the Manufacturing Environment An occurrence (relative occurrence) is a persistent object that represents the usage of an item in the context of a top-level structure. However. a shock absorber in a car may not be compressed when in inventory. in the context of the suspension assembly. For example. in the context of the complete vehicle. For example. Each such standard component may have a structure of its own. 4-2 Teamcenter Manufacturing User’s and Administrator’s Manual ENG00025 D . position. It stores occurrence data such as usage specific names and descriptions or positional overrides. For example. in the context of its immediate parent. It represents the shape. you must associate a separate NX part and JT image with the occurrence of the compressed part in the car. and welding guns. Assigning a name to an absolute occurrence of an item does not override or change the attributes of the general item. the location of a component may change based on its relationship to other factory elements. You can associated different cost data with each occurrence of the robot. you might need to change the installed position of a robot in one area of the factory compared to another. when the part is assembled into a car. the vehicle may have two occurrences of a left wheel. As a result. • Factory configuration A factory structure contains many standard components such as robots. An absolute occurrence is a specific instance of an item. an occurrence group may collect all occurrences in the product that are within a given proximity of a part that you are designing. the geometric definition of the part changes in the context of the car. For example. Absolute occurrence data overrides relative occurrence data. Alternatively. To allow for these differences. even though the actual wheels are identical. conveyors. Users can name one of those occurrences as left rear wheel. When positioned in the factory. but author your actual processes in the Tecnomatix process planning software. to assemble the seats into the car. For example. • Integration with Tecnomatix Process Planning Software You may use Teamcenter Manufacturing to manage and maintain process data. To allow for this requirement. factory components may change their positions and associated data. If. for example. During this planning phase. the worker is positioned relative to the car in the context of the setup. ENG00025 D Teamcenter Manufacturing User’s and Administrator’s Manual 4-3 . In the manufacturing setup. including the steering wheel and pedals. the doors must be open. this change should not affect other instances (occurrences) of the robot. • Human studies A study or setup may contain a model of an assembly worker and instances of parts from the car model that interact with the worker. A robot may change its position as the result of a change to the design of a station layout. this in-process assembly includes the doors of a car. the steering wheel may be rotated along the steering bar or a pedal pressed to the down position.Principles • Manufacturing setup A setup is a composition that represents the environment in which an operation or study is performed. and you can change the positions of parts of the car to model different assembly scenarios. you should change the positions of the doors in the context of the in-process model during manufacturing. The position must be associated with the door only in the context of the product view (occurrence group) and should not affect the product definition. However. it is associated with the corresponding occurrences in Teamcenter Manufacturing. one of the occurrence groups represents the in-process assembly as it arrives at the station. Tecnomatix uses a data model in which each component in the factory is unique. the doors may be in the closed position in the design product structure. When you import data from Tecnomatix into Teamcenter Manufacturing. Information about the process structure is required during the planning phase of the process plan. The setup contains occurrences groups of various structures in the product and the factory. The positions of these parts can be changed only in the context of the study without affecting the original position in the product definition. However. In this case. The data in the setup overrides the data associated with the reference object. and variant conditions. including cost data. 4-4 Teamcenter Manufacturing User’s and Administrator’s Manual ENG00025 D . but you can also override lower level data at a higher level. It describes the usage of an item revision in the context of its immediate parent. It has object attributes and attachments. For example. which may be an item revision or an occurrence. • Occurrence data The data associated with a relative occurrence in the structure. • Occurrence data in the context of a structure view You can relate data to an occurrence in the context of a specific occurrence group. • Setup data A setup is an assembly structure that contains occurrences in an occurrence group. direct model data for visualization. Editing the Components of a Process Structure Structure components are lines in the process structure that belong to the top level item in a specific window. visualization files. The data on the setup occurrence overrides the data on the object it references. occurrences. Occurrences can have attributes such as transformations and notes. An occurrence in the setup may include a reference from an operation or process to an occurrence group. including: • Item revision data All data associated with the item revision. or items. There are many types of data that you might want to associate with an occurrence. and attachments such as a dataset or forms. You can attach the data with effectivity. names or IDs. you can attach a transformation. These lines may have occurrences in the context of the top level. • Item revision data Item revision data is associated with the configured item revision in the structure. You can attach data at any level. You can also attach data to occurrences by typed relationships. a design model.Chapter 4 Principles Associating Data With Occurrences You can associate data with occurrences. You may define data at several levels in the structure. transformations. You can edit the following data in the context of a BOM structure (BOM window): • Occurrence data Occurrences in a structure represent the usage of an item in its immediate parent. At any level. then later override the data at a different level of the structure. The data is always attached with a particular effectivity. data attached to an occurrence overrides data attached to the item revision. This configuration can support components with multiple positions in the structure or in exploded views. An occurrence path is automatically created for a component or subassembly and its ancestors when you assign it to an occurrence group from the base product view. You cannot create occurrence paths for occurrence groups. This data overrides the data on the occurrence attached to that line. Teamcenter Manufacturing uses occurrence paths to identify different occurrences of the same component or subassembly in the various product views. • Adding components You can add components to an occurrence group. You can also edit views with an incremental change order. You must have the appropriate privilege to access the item. You can associate attachments with the relationship. In this case. You edit the top-level structure associated with the occurrence group and add the new component to the end item.Principles Editing the Process Structure View A structure view appears in the assembly viewer and provides an image of part of the process structure. You can add instances to the view by dragging instances from another view of the structure or from the base structure. ENG00025 D Teamcenter Manufacturing User’s and Administrator’s Manual 4-5 . the line representing it is configured or removed as specified. Wherever the occurrence is visible. You can also create occurrence paths manually for a selected BOM line. You can only remove a component in the context of an incremental change order. You can edit structure view data in the following modes: • View-dependent edit You can attach an attribute override to the relationship on an occurrence. You cannot add components in a view dependent edit. Occurrence Paths An occurrence path of a component or subassembly is a database object that contains the path of a specific occurrence in the hierarchy of the base product view (engineering BOM) from the root assembly. • Removing components You can remove components from the top level with an incremental change order in a view dependent edit or an appearance dependent edit. the appearance is marked for deletion. in which the attachment to the occurrence is overridden or added. You can search for product appearances from Teamcenter Manufacturing. 4-6 Teamcenter Manufacturing User’s and Administrator’s Manual ENG00025 D . Any item that is defined as an end item should have its own appearances. They are generated for a product end item. when you create appearances for an end item that contains other end items. which is a target for a manufacturing process. All product appearances for an end item are grouped into a single appearance set.Chapter 4 Principles Searching for Appearances Appearances may be included in the product design to speed the time needed to retrieve. expand and search a large structure. They may be needed if a persistent reference to that instance is required from outside the context in which the instance is defined. appearances for that level are not initially created in the context of the end item. The creation of appearances is controlled so that they are created only for BOM lines that are needed. you do not use product appearances directly. However. In the Teamcenter Manufacturing environment. You would normally apply this to the top level structure. for example. you define the following parameters: • Option The option is an attribute of the item revision with a set of allowed values. These differences are typically configured as variants of the product design. When you configure variants. The variant condition is defined programmatically. ENG00025 D Teamcenter Manufacturing User’s and Administrator’s Manual 4-7 . you can configure variants to the manufacturing process to accommodate different configurations of the product. for example: car type = GLS. but may not be unique within the entire system. operation. but you can apply options anywhere in the process structure. if you manufacture two sizes of engine. gearbox = manual • Fixed default A specific default value that is applied if no other values are specified. For example. engine = 1200. if the default product manufacture is the 1200 engine and you rarely build other sizes. you can configure manufacturing variants that correspond to specific variants of the product design. for example: Load IF engine = 1200 • Variant rule A collection of option values that define programmatically the variant of the structure to configure. An option is attached to a specific revision of an item. there may be two allowed values—1200 and 1600. or other item. Option names are unique within an item revision. If so. you may set a fixed default of: engine = 1200 A fixed default is attached to an item revision of a process. such as a process or operation. • Variant condition A condition that you set on an occurrence to specify what option values are required to configure that occurrence.Principles Variants and Variant Rules Variant configuration allows you to create options (such as manufacturing locations) and allowed values (such as a specific plant within the company) and associate these options with an item revision. The underlying product structure remains unchanged. see Manufacturing Structure Editor Help and Part Manufacturing Planner Help. a weld point can be attached to two different components if they are welded together during the manufacturing process. the derived default may be: radio = stereo IF car type = GLX A derived default is attached to an item revision of a process. such as a configuration with revisions that are released for production or a product structure with the latest working revision of components. You can create item elements programmatically with ITK functions or import them from external systems such as NX through the NX CAM Integration. if you only fit a radio when you manufacture a particular product. operation. mating relationships. and check they are consumed in the process structure. Features are represented by item elements. ports. or other item. see Product Structure Editor Help. so you can design a manufacturing process for an imprecise assembly if the process does not change when the revision of a component changes. as described in NX CAM Integration in chapter 6. You can include item elements in occurrence groups. and connections as part of the process structure. for example. a precise assembly contains specified revisions of components and may need to be updated each time a component is revised. also called generic design elements (GDEs). see Manufacturing Structure Editor Help and Part Manufacturing Planner Help. For example. For details of how to define variants and variant rules for the product. search for and compare item elements. 4-8 Teamcenter Manufacturing User’s and Administrator’s Manual ENG00025 D . rather than specific revisions of those components.Chapter 4 Principles • Derived default A default value that depends on a condition. Integrations With Other Products. Features can be attached to one or more physical parts. The manufacturing process is linked to the specific configuration and may need to be updated more frequently than when working with imprecise assemblies. They allow engineers to create product structures and BOMs for varying configurations of the product. Precise and Imprecise Structures Teamcenter Manufacturing allows you to design manufacturing process for precise and imprecise assemblies An imprecise assembly contains components with unspecified revisions. Feature Management Teamcenter Manufacturing allows you to include manufacturing features such as weld points. For information about how to apply variants and variant rules to the manufacturing process. Conversely. For more information on this functionality. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating the Top-Level Process . . . . 5-28 Creating Templates for Publishing Manufacturing Data . . . . . . . . . . . . . . . and Work Areas Assigning Activities to Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-28 Displaying GD&T Symbols and Rich Text in Forms . . . . . . . . Creating Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Product. . . . . 5-18 Creating a Preliminary Data Indicator . . . . . . . . . . . . . . . . . . . . Creating Work Instructions . . . . 5-15 Designing a Fixture for Manufacturing . . . . . . . . . . . . . . . 5-33 5-34 5-34 5-35 ENG00025 D Teamcenter Manufacturing User’s and Administrator’s Manual . . . . . . . . . . . . . . . . . . . . . 5-2 Creating a Manufacturing Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-26 Customizing the Data Tabs Display . . . . Using XML Style Sheets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-16 Verifying the Manufacturing Process . . . . . . . . . . . . . . . 5-23 Creating an Intermediate Data Capture . . . . . . . . . . . . . . . . . 5-4 5-4 5-5 5-6 5-7 5-9 5-11 5-12 5-13 Managing Process Design With the Thin Client Interface . . . . . . . . . . . . . 5-18 Creating a Process. . Product. . . . . . . . . . . . 5-17 Creating Product Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Opening the Product . . . . . . . . . . . . . . . . . . . . Adding Resources to Operations . . . . . . . . . . . . . . . . . . . . . 5-14 Working With Flexible Components and NX . . . . . . . . . . . . . . . . . . . . . . . . . . 5-25 Creating a Bookmark . . . . . . . . .Chapter 5 Tasks and Use Cases Understanding the User Interface . . . . . . Configuring GD&T Symbols and Rich Text in Forms Using Preference Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14 Working With Occurrences for In-Process Assemblies . . 5-26 Enabling the GANTT Chart for Processes and Operations . . . . . . Assigning Work Areas . . . . . . . . . . . . Establishing Relationships Between Process. . . . . . . . . . 5-28 Configuring Incremental Changes . . . . . . . . . . or Plant Structure From a Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-38 Configuring Reports in the Rich Client . . . . . . . . . . . . . . . . . . . . . . . . 5-39 Troubleshooting Reports in the Rich Client . . . . . . . . . . . Running Batch Reports . . . . . . . Installing the Report Designs . . . . . . . . . .. . . . . . . . Prerequisites for Generating Thin Client Reports Setting Preferences for Thin Client Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . 5-43 5-44 5-44 5-46 5-46 5-46 5-47 5-47 5-47 Teamcenter Manufacturing User’s and Administrator’s Manual ENG00025 D . . . . . . . . . . .Generating PDF Reports . . . . . . . . . . . . .. . . Creating Weld Reports for Operations .. . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Updating Report Designs . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing the Transfer Mode . . . . . . . . . . . . . . . 5-37 Creating Reports in the Rich Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . Adding Links to the Thin Client User Interface . . . . . . . . . . . . . . . . . . . 5-41 Creating Reports in the Thin Client . . Creating templates for work instructions or other manufacturing publications. Creating. and configuring reports in the rich client and the thin client. Configuring incremental changes. Managing process design with the thin client interface. Displaying geometric definition and tolerance data (GD&T) symbols and rich text in forms. or product structure from a template. generating. This chapter describes the following topics: • • • • • • • • • • • • • • • An introduction to the user interface. Creating a bookmark. Designing a manufacturing fixture. Working with flexible resources and NX. Customizing the data tabs display. Creating a preliminary data indicator (PDI). Verifying the manufacturing process.Chapter 5 Tasks and Use Cases This chapter describes some of the main tasks you can perform with Teamcenter Manufacturing. Creating a manufacturing process. plant. Creating a product view. Creating a process. Working with in-process assemblies. • ENG00025 D Teamcenter Manufacturing User’s and Administrator’s Manual 5-1 . You create the MBOM from the EBOM (engineering BOM). An MBOM shows all the operations. activities and other items that are assigned to the process. resequencing and rearranging it as necessary to create an efficient manufacturing process. which are similar in concept to an assembly BOM.Chapter 5 Tasks and Use Cases Understanding the User Interface The process structure is presented in the form of an MBOM (manufacturing bill of materials). as follows: Item Product (open) Process (revision) (open) (BOM view revision) Operation Activity Plant or work area (open) (revision) Work area operation Work area attachment Workstation (revision) Consumed product Resource Operation setup (BOM view revision) Operation flow Station flow Weld point Allocated weld point Icon 5-2 Teamcenter Manufacturing User’s and Administrator’s Manual ENG00025 D . and their relationships. Each item in the BOM is represented by an icon according to its type. ENG00025 D Teamcenter Manufacturing User’s and Administrator’s Manual 5-3 .Tasks and Use Cases Item Datum point Allocated datum Barrel tool CLSF data PTP data Shop docs Drill tool Form tool Groove tool Machining Mill tool NC machining Icon (revision) Thread tool Tool Turning tool Attachment (process) (product) Library Reports Collaboration context Product context Plant context Process context Resource context Icons may appear slightly differently. depending on the version of Teamcenter Manufacturing you are using. This allows you to visualize representations of parts in the assembly viewer in Teamcenter Manufacturing. Creating a Manufacturing Process This section describes the general process you follow to design a manufacturing process for a part in an existing product. including in My Navigator and in the product structure in Product Structure Editor. and selecting the types to hide. Set the options in NX Manager to save images in JT format. parts. 4. you can hide the Teamcenter Manufacturing object types for Teamcenter Engineering users by choosing the Edit→Options menu option in a rich client application (for example. The component is visible in the BOM panel and the assembly viewer. choosing the General→Item option. 2.Chapter 5 Tasks and Use Cases By default. Product Structure Editor allows you to manage assemblies. Locate the product assembly with the My Navigator application in Teamcenter Engineering. Opening the Product When the design engineer releases the design. If appropriate. all Teamcenter Manufacturing object types are visible in Teamcenter Engineering. as described in the Command Suppression Help. 5-4 Teamcenter Manufacturing User’s and Administrator’s Manual ENG00025 D . This may result in a very complex structure displayed to the Teamcenter Engineering users. The examples describe a manufacturing process for a right crank arm. which is part of a crank assembly that was designed in NX. and components before you begin the planning process. 3. Product Structure Editor or Manufacturing Structure Editor). you should begin the planning process as follows: 1. An administrator can restrict commands to certain groups or roles with the Command Suppression application. Command Suppression Not all the commands described later in this chapter may be appropriate for all users. and send the component to Manufacturing Structure Editor or Part Manufacturing Planner. Identify the component to manufacture in the assembly. Send the product to Product Structure Editor and verify its assembly structure. Click the Plant tab and click Open Work Area. and can fabricate the component. Select the facility to fabricate the component.Tasks and Use Cases Assigning Work Areas After you identify the component to manufacture. 2. as follows: a. Select the parent work area in the BOM hierarchy and click Create New Work Area. ENG00025 D Teamcenter Manufacturing User’s and Administrator’s Manual 5-5 . save the images as JT files. Optionally. as follows: 1. b. You can generate plant layouts in FactoryCAD. when there are resource constraints at the primary facility. 3. choose Set Preferred Alternate from the popup menu. An alternate facility has similar capacity and equipment as the primary facility. and choose the alternate from the list of available facilities. A list of available facilities is shown in the BOM panel when you click the Plant tab. and work areas that are configured within it. 4. The Open Work Area dialog window opens. You can create an additional alternate facility by clicking the Alternate Component button in the bottom toolbar and selecting it from the list. allowing you to search for the applicable area and assign it to the product. assign alternate facilities to fabricate the component. you can then assign it to a location where it will be manufactured. Teamcenter Manufacturing displays the New Work Area dialog window. and attach the images to the appropriate work area. work centers. and select MEPlant from the Workarea Type list. You can expand the hierarchy of the facility to view departments. View the facility layout. If the work area does not exist. You can view the image in the assembly viewer when you select the work area in the hierarchy. right-click on the primary facility. Click OK to create the work area. a circled red letter A appears next to it in the hierarchy. create it. If the primary facility has preferred alternates. Locate the top-level work area and open it in Manufacturing Structure Editor or Part Manufacturing Planner. Enter a name and description for the new work area. To designate an alternate facility. for example. MEFabrication. 2. then define manufacturing processes for each of the other components.Chapter 5 Tasks and Use Cases Creating the Top-Level Process When you have data about the product and the work area where you will fabricate it. then click the New Process button. c. you can design the top-level manufacturing process. Teamcenter Manufacturing displays the Create New Process dialog window. Enter a name and description of the new process. you can design a manufacturing process for the fabrication of the right crank arm of the crankshaft assembly. 5-6 Teamcenter Manufacturing User’s and Administrator’s Manual ENG00025 D . but is closely related to. click OK or Apply to create it. Choose a process type from the dropdown list. for example. For example. When you have completed the new process definition. Click the Process tab. To create a new top-level process: 1. Click the Assign button and Teamcenter Manufacturing assigns a unique process identifier and revision number. the product and work areas. b. 3. Create the new process as follows: a. The manufacturing process is a separate Teamcenter Manufacturing item that can be revised and controlled separately from. You can organize and store such templates with the Classification application. and use the templates to create processes for similar products. You can also save manufacturing processes as templates. Select the top-level process and click the New Operation button. 4. for example. This ensures that NX Manager recognizes them when you generate CAM data. repeat each of the previous steps to create the other operations for the manufacturing process. For example. There are many different types of operation you can attach to the manufacturing process. Teamcenter Manufacturing displays the Create New Operation dialog window. a blank forging may be procured from a storage area. Choose an operation type from the dropdown list. the forging may be roughly machined on a CNC machine. To create an operation: 1. After you establish the basic hierarchy of processes and operations. Machining. and bench finished. 3. the forging may be finished on a CNC machine. the forging is inspected prior to finishing. 2. Finish machining. Quality control. inspected. c. click OK or Apply to create it. including: • • • • • Procurement of raw material. Click the Assign button. ENG00025 D Teamcenter Manufacturing User’s and Administrator’s Manual 5-7 . With the top-level operation still selected. After you complete the new operation definition. For example. You can also use the process flow viewer to resequence operations within the process. MEProcurement for a material procurement operation. the machined part is coated. For example. Finishing. Create the new operation as follows: a. b. For example. Teamcenter Manufacturing assigns a unique operation identifier and revision number. you can designate alternate operations if necessary. Designate machining operations as one of the operation types that your administrator specified in the NX_supported_operation_types preference.Tasks and Use Cases Creating Operations An operation is one step in the manufacturing process for a product and is executed at a single workstation. Enter a name and description of the new operation. For example. You can create additional alternate operations by clicking the Alternate Component button in the bottom toolbar and selecting them from the list. adjust the sequence of operations in the process by clicking the Process Flow tab and moving the connections between operations. Select and right-click the alternate operation. and choose the alternate from the list of available operations. Teamcenter Manufacturing displays a popup menu. The Structure panel may not contain a sequential list of operations. If necessary. If it is similar to the primary operation. you can use the primary operation as a template for the alternate operation definition. 6. Changing the sequence of operations in this way does not affect the order in which they are displayed in the process Structure panel. You can also edit the sequence number in each operation box in the flowchart to change the order of the operations in the process. create and designate alternate operations and select a preferred alternate. as follows: a. Choose Set Preferred Alternate from the popup menu. Create the alternate operation. 5-8 Teamcenter Manufacturing User’s and Administrator’s Manual ENG00025 D . b. c.Chapter 5 Tasks and Use Cases 5. d. If appropriate. following the previous steps. Select the work area. Teamcenter Manufacturing displays a popup menu. both structures are imported into Manufacturing Structure Editor or Part Manufacturing Planner when you open one of them. To assign a process to a product: a. This ensures any changes to the product configuration are reflected in the manufacturing structure. as follows: 1. double-click the work area to add it to the empty work area structure in the upper panel. any changes to the revision rules may affect variant and alternate operations in the process. b. c. Open and select the top-level process. When you associate a product and process in this way. g. e. d. then right-click the top-level process. Click the Open a Work Area by Name button and search for the work area. with the process structure in the lower panel and an empty work area structure in the upper panel. Click the Assign Mode button. Click the Open a Product by Name button and search for the product. Teamcenter Manufacturing divides the window horizontally. You can determine if a relationship exists between a process and a product by selecting the process and clicking the Attachments tab. Open and select the top-level process. If the relationship exists. e. you must link them to the product. then click the Product tab. Choose the Associate Product as Target option to establish the relationship between the product and process.Tasks and Use Cases Establishing Relationships Between Process. Select the product. 2. f. ENG00025 D Teamcenter Manufacturing User’s and Administrator’s Manual 5-9 . as follows: a. with the process structure in the lower panel and an empty product structure in the upper panel. the product item is shown as an attachment to the process revision. c. then click the Work Area tab. In the search results. In the search results. Teamcenter Manufacturing divides the window horizontally. Click the Assign Mode button. Assign the top-level process to a work area. Assign the top-level process to the product. and Work Areas After you create work areas and a manufacturing process containing operations. Teamcenter Manufacturing displays a popup menu. Similarly. d. then right-click the top-level process. Click the Assign Mode button again to remove the second panel. double-click the product to add it to the empty product structure in the upper panel. b. Product. Teamcenter Manufacturing divides the window horizontally. Choose the Associate Work Area option to establish the relationship between the work area and process. then right-click on the operation. d. Teamcenter Manufacturing displays a popup menu. Choose the Assign Work Area option to establish the relationship between the work area and operations. c. Click the Open a Work Area by Name button and search for the work area. b. When you associate a work area and operation in this way. When you associate a work area and process in this way. Click the Assign Mode button again to remove the second panel. e. Select the operation in the process. Highlight the work area. as follows: a. 5-10 Teamcenter Manufacturing User’s and Administrator’s Manual ENG00025 D . Assign each individual operation to a work area. then click the Work Area tab. Click the Assign Mode button. In the search results. both structures are imported into Manufacturing Structure Editor or Part Manufacturing Planner when you open one of them.Chapter 5 Tasks and Use Cases f. double-click the work area to add it to the empty work area structure in the upper panel. f. g. with the process structure in the lower panel and the plant structure in the upper panel. Click the Assign Mode button again to remove the second panel. g. 3. the work area becomes part of the operation’s setup. To create activities within an operation: 1. Teamcenter Manufacturing displays the Create New Activity dialog window. d. Click the Activities Flow tab or the Activities Gantt Chart tab and establish the correct sequence of activities by dragging connector arrows to new destinations or renumbering the activity boxes. download and run a CNC program. Select the operation that contains the activities and click the Operation Activities tab. c. After you have complete the new activity definition. For example. Select the activity root object in the right panel and click the Create New Activity button. and inspect the machined part. Create the new activity as follows: a. Enter a name and description of the new operation. e. An activity is not an item in Teamcenter Engineering and cannot be revised in the way that processes and operations can. 4. Choose an activity type from the dropdown list. Select the top-level activity and click the Operation Activities tab. 3. click OK or Apply to create it.Tasks and Use Cases Assigning Activities to Operations You can further define a process operation by creating a series of activities within it. Enter a start time and duration for the activity. Repeat the previous steps for each additional activity. if necessary. Do not create activities until their definitions are stable and unlikely to change. You can change these values later. MEMove for a movement of materials activity. for example. ENG00025 D Teamcenter Manufacturing User’s and Administrator’s Manual 5-11 . an NC machining operation may include activities to set up the part in a fixture. from the Gantt chart tab. 2. b. Change the sequence of activities does not affect their position in the activities hierarchy. Teamcenter Manufacturing opens the Classification application. Double-click the subclass to expand its structure. You can retrieve resources that are stored in the Classification application and attach them to the operation. as follows: 1. fixtures. 3. Example of Operation Setup For more information on managing classified resources. 5. NC data. work instructions. The current setup is visible in the assembly viewer. see Classification Help and Classification Administration Help. 5-12 Teamcenter Manufacturing User’s and Administrator’s Manual ENG00025 D . 2. click the Table tab to display a list of resources matching the search. and the product itself. Select the top-level operation in the process structure and click the Assign Resources button. in which a machine tool and several clamps (resources) are assigned to the manufacture of the target part. After the search completes. Figure 5-1. A setup contains the elements required by the operation and may include tools. human resources (operators). Select the resources to attach to the operation and click OK. 4. which are required for its execution. Expand the classification folders until you find the appropriate subclass.Chapter 5 Tasks and Use Cases Adding Resources to Operations You can associate one or more resources with an operation or activity. Click the Search button to search for the resources by name or characteristic. Figure 5-1 shows a typical operation setup. later in this chapter. 5. then OK. ENG00025 D Teamcenter Manufacturing User’s and Administrator’s Manual 5-13 . d. If you want to create manufacturing documentation for nontechnical users with limited computer skills (for example. Open the component in NX Manager and save a view for the drawing. 7. as follows: a.Tasks and Use Cases Creating Work Instructions After you define the process. For example. you could attach a Microsoft Word file that describes the steps an operator should perform or a NX drawing showing positioning information. Choose the File→Export option in NX Manager. notes. and click Import Selected Files. do the following: 1. Select the part file. You must regenerate the image file if you update the part file or drawing. Open the part in the Manufacturing Structure Editor or Part Manufacturing Planner application. Save the part file and the system displays the Import Files for Part dialog window. and save the drawing file. Expand the UGMASTER attachment to the item revision. or other work instructions. 3. assembly personnel). Add dimensions. Choose the View→Named References option and Teamcenter Manufacturing displays the Named References dialog window. Create the drawing and add the view to the drawing. Export the drawing in any suitable format such as GIF or JPG. see Creating Templates for Publishing Manufacturing Data. 4. 2. To create a drawing and attach it to an item. b. Image files are not directly associated with the NX part file. 6. Select the image file and click the Export button to view or print the GIF file. you can attach work instructions to it that contain additional information. as needed. Verify that the dataset is attached correctly by viewing the named references of the item. c. jt to the occurrence of F with respect to T. To define a JT file. together with other components. If another user now open the top-level assembly T in Teamcenter Manufacturing and views F in the product viewer. Working With Flexible Components and NX The following scenario is an example of how you can use occurrences to manage flexible components created in NX: 1. However. Import and save these definitions in Teamcenter Manufacturing. Use A in a top-level assembly (T). the engineer associates the affected items (for example.jt file is shown. the correct representation in the F2. 4.jt is shown. 2.jt file to an occurrence of F with respect to A. approves the assignment as complete.jt) and store it in the context of T. If not. The manufacturing engineer receives the assignment and completes the necessary work in rich client applications such as Manufacturing Structure Editor. 3. Create a JT file (F1. NX creates the JT file next time you save the design. the project manager may return the assignment to the manufacturing engineer for rework. 5-14 Teamcenter Manufacturing User’s and Administrator’s Manual ENG00025 D . if the user open A in the product viewer. Create a flexible component (F) in NX. choose the File→Options→Save Options menu option and select Save Teamcenter Vis Data. F1. 4. The project manager defines the task and submits it to a workflow. To meet this requirement. Also. you create another JT file (F2. even if other participants in these activities are working with the rich client applications. The project manager receives notification in the thin client inbox that the workflow assignment is approved and sent back. 2. Add F to a subassembly (B). Use subassembly B in another subassembly (A).jt) to represent the flexible component in context A. 7. if they are satisfactory. The workflow assigns the task to a manufacturing engineer.Chapter 5 Tasks and Use Cases Managing Process Design With the Thin Client Interface You can manage the design or modification of manufacturing processes with the thin client interface. attachments and reports) to the workflow assignment and approves it. Attach the F1. 3. 6. The project manager reviews the items attached to the workflow assignment and. A typical scenario is as follows: 1. attach F2. 5. On completion. which requires a change in the definition of the flexible component F. Tasks and Use Cases Working With Occurrences for In-Process Assemblies The following scenario is an example of how you can use occurrences to manage in-process assemblies: 1. Create a complete process plan for assembling a vehicle. 2. Create an in-process MBOM for the entire assembly process. Create appropriate occurrence groups with Multiple View Editor. 3. Identify a requirement to change the definition of the process for the stations where seats and instrument panels are installed. 4. Identify the occurrence group affected in those stations. 5. Open the occurrence group in Manufacturing Structure Editor or Part Manufacturing Planner, then choose occurrence-specific (in-context) editing. 6. Modify the positions of the doors to ensure they are open. 7. Save the occurrence group with the new transformations for the doors in the context of this in-process assembly structure. 8. Click the Viewer tab and verify that the in-process assembly structure shows the doors in the open position. ENG00025 D Teamcenter Manufacturing User’s and Administrator’s Manual 5-15 Chapter 5 Tasks and Use Cases Designing a Fixture for Manufacturing When you design a fixture to use in a manufacturing operation, you must know the state of the product in the manufacturing process in which the fixture is consumed. You also should know the factory components in which the operation is performed, and the relative positions of the in-process workpiece and the factory data. To design a fixture to hold the product in the factory location, the following general steps are necessary: 1. Identify the product components and datums for the fixture design. Put the occurrences of these objects in the structure into a persistent occurrence group. 2. Locate the in-process model of the product. Extract the components of interest for the fixture design from the in-process model into the persistent occurrence group. 3. Identify the factory area in which the operation that consumes the fixture is performed. Identify the relevant elements and interfaces, and put them into a persistent occurrence group. 4. Put the data obtained in the previous steps into a study for the tool designer. You can roughly set the position of the product in the factory. 5. Transfer the study into the CAD system for design. 6. Once the tool is available, assign the operations using the fixture to the newly designed tool. 7. Continue detailed planning with the newly created fixture. 5-16 Teamcenter Manufacturing User’s and Administrator’s Manual ENG00025 D Tasks and Use Cases Verifying the Manufacturing Process Teamcenter Manufacturing includes several analysis tools that allow you to check the completeness of the process, and identify discrepancies between the BOM and the bill of process (BOP). You can make the following checks: • • • Select a line in the BOM and search to see where this item is consumed in the manufacturing process. Select a searchable item in the process and find it in the original BOM. Interactively compare two assemblies in the BOP to identify differences and similarities. You can expand the BOP, select an assembly or subassembly, then initiate an interactive comparison. The results of the comparison are color-coded in the BOP display. Compare the product and the process in batch mode to ensure all appearances of product components are consumed in the process structure. You can save the results for later analysis. • For detailed information about performing these tasks, see Manufacturing Structure Editor Help and Part Manufacturing Planner Help. ENG00025 D Teamcenter Manufacturing User’s and Administrator’s Manual 5-17 Chapter 5 Tasks and Use Cases Creating Product Views You can save the configuration of the assembly viewer, including the current selection of objects, zoom factor, rotation angle, and pan displacement. The saved configuration or product view (sometimes called a snapshot view) is attached to the product, process, or plant structure that is associated with the view. Teamcenter Manufacturing assigns a thumbnail image to each saved configuration, allowing users to browse and retrieve configurations. For information about managing and using product views, see Manufacturing Structure Editor Help. To configure the product views feature, edit the com/ugsolutions/cme/snapshot/snapshot.properties file located in the Portal.jar file. If you change any of the settings in this file, exit and restart the rich client. You can change: • • The height in pixels of thumbnails, as defined by the thumbHeight setting. The width in pixels of thumbnails, as defined by the thumbWidth setting. You must set the height and width to the same value. • • The quality of thumbnails, as defined by the thumbQuality setting. Defined as a relative value between 0 (low) and 100 (high). Product views are sorted alphabetically in the viewer, according to the name of the dataset. If the snapShotDataset.case.SensitiveSort setting is false, the system ignores the case of the name; if it is set to true, names with uppercase initial letters appear before names with lower case initial letters (for example, Apple is listed before apple). When product views are created, the system assigns them a numeric value derived from the date and time they were created. To have new product views appear at the end of the list, set the snapShotDataset.numbersSortLast setting to true; to have new product views appear at the beginning of the list, set the snapShotDataset.numbersSortLast setting to false. • Creating a Process, Product, or Plant Structure From a Template You can create a product structure from a product template, a plant structure from a plant template, and process structure from a process template. You may choose to define a generic product structure that does not represent an actual manufactured product because it contains generic placeholders in place of variable parts. These placeholders are identified by absolute occurrences that are populated when an actual product structure is created from the template. The example in figure 5-2 shows a product structure template. Several components are represented by generic placeholders, for example, the part identified as absolute occurrence 3. 5-18 Teamcenter Manufacturing User’s and Administrator’s Manual ENG00025 D Tasks and Use Cases Figure 5-2. Typical Product Structure Template If you create a generic manufacturing process structure from the generic product structure, the occurrences in the generic product structure are consumed in the generic process structure. The resulting process structure is shown in figure 5-3. Figure 5-3. Typical Process Structure Template In this example, although no real parts are consumed in the operations that comprise the generic process, each consumed item has an identity. This identity of the item in the process structure is the same as it is in the product structure. Consequently, if you use this process structure as a template for the creation of a new process structure for manufacturing a product that maps exactly to the generic product structure, the product and process share the same absolute occurrences. The new process that you create from the template consumes the parts from the real product structure with the same absolute occurrences. The example in figure 5-4 shows the new process structure with actual operations; consumed parts are replaced with parts from the new product using mappings you define. ENG00025 D Teamcenter Manufacturing User’s and Administrator’s Manual 5-19 The location of the cloning rule preferences for a specific user is determined by a site preference. 5-20 Teamcenter Manufacturing User’s and Administrator’s Manual ENG00025 D . it determines if a substitution is necessary and takes one of four actions. • Ignore The new structure does not reference the object. generic work areas are substituted with specific absolute occurrences. These cloning rules are defined by preferences and the defined rules are available to users when creating an actual structure. For details about how to set preferences. see Manufacturing Structure Editor Help. You can associate multiple action rules with each preference. you must define cloning rules that allow Teamcenter Manufacturing to determine how to map objects between the structures. When Teamcenter Manufacturing encounters an object that is mapped between the template and the actual structure. product templates. and plant templates. see the Configuration Guide. Process Structure Created from Template Similarly. according to the mapping of the object type: • Clone Copies the object referenced by the template to a new object in the structure. For further information about creating structures from templates. Factory Structure Editor Help. • Reference The structure references the same object as the template. one each for process templates. Defining Cloning Rules To clone structures from templates or other structures. You can define three cloning rule preferences.Chapter 5 Tasks and Use Cases Figure 5-4. or Collaboration Context Help. if you define a mapping between the plant structure referenced by the template and the actual plant structure. Part Manufacturing Planner Help. in which case the configuration of consumed items does not affect the configuration of operations. These rules determine if objects are cloned. When there is no mapping for the MEConsumed item. referenced or ignored. Teamcenter creates a reference to the item from the cloned element.Template= Action_Rule_Name3 Action_Rule_Name4 .MEWorkArea:Map.MEConsumed:Map. the MEConsumed occurrence type maps consumed items to the corresponding occurrences. Optionally. . individual users may change the cloning action rules by editing their user preference file. If the same absolute occurrence appears more than once. Plant. The second action is the default action and is taken if the mapping fails. the MEConsumed occurrence type is mapped to the occurrence in the new structure. Teamcenter Manufacturing uses the absolute occurrence referenced from the template and finds the corresponding occurrence in the new product.Template= Action_Rule_Name1 Action_Rule_Name2 . The site administrator can change the controllingOccsForProcessConfiguration preference to map another occurrence type. For example. The general format of the cloning rule preferences is as follows: Process.Ignore *:*:OccType. Alternatively. this allows you to create a process structure from an existing process or from a process template. By default. When there is no mapping for the MEWorkArea item.Reference In this example.Template= Action_Rule_Name5 Action_Rule_Name6 ENG00025 D Teamcenter Manufacturing User’s and Administrator’s Manual 5-21 . this preference may be left unassigned. For example: *:*:OccType. In addition. You cannot change this behavior with the Business Modeler application. It links the consumed items for that operation to the occurrence in the new product. Product. Teamcenter Manufacturing only takes the specified action if an absolute occurrence or its ID is the same in the template and the structure.Tasks and Use Cases • Map The system maps the template to a replacement structure. Teamcenter Manufacturing ignores it. only the first matched instances is mapped. You can specify a second action after the Map action. . this rule may be allowed by a second (default) action: Reference or Ignore. Each site can define a set of cloning rules from which users may select. bom_view:Clone *:*:Attribute.contents:Clone class.contents:Reference 5-22 Teamcenter Manufacturing User’s and Administrator’s Manual ENG00025 D .IMAN_specification:Clone *:class.Template.Null:Clone *:*:OccType.*:Reference *:*:Relation.IMAN_Rendering:Clone *:*:Relation.Folder:*:Attribute.structure_revisions:Clone *:*:Attribute.variant_expression_block:Clone *:*:OccType.structure_revisions:Clone *:*:Attribute.Template.bom_view:Clone *:*:Attribute.items_tag:Clone *:*:Attribute.IMAN_MEFolder:Clone class.parent_item:Clone *:*:Attribute.IMAN_Rendering:Clone *:*:Relation.contents:Clone class.Ignoring_Consumes= *:*:Attribute.Action_Rule_Name1= *:*:Attribute.IMAN_specification:Clone *:class.MEActivity:*:Attribute. The following example shows a typical Action_Rule_Name1 variable for the Process.Mapping_Consumes= *:*:Attribute.variant_expression_block:Clone *:*:OccType.Null:Clone *:*:OccType.MEWorkpiece:Ignore *:*:OccType.Template= Mapping_Consumes Ignoring_Consumes Process.MEConsumed:Ignore *:*:OccType. you must define a new variable.Chapter 5 Tasks and Use Cases For each set of action rules.Ignore *:*:OccType.parent_item:Clone The following example shows two cloning rules (Mapping_Consumes and Ignore_Consumes) for process templates: Process.MEConsumed:Map.contents:Reference Process.MEActivity:Relation.items_tag:Clone *:*:Attribute.MEActivity:*:Attribute.MEWorkpiece:Ignore *:*:OccType.parent_item:Clone *:*:Attribute.Folder:*:Attribute.structure_revisions:Clone *:*:Attribute.bom_view:Clone *:*:Attribute.MEActivity:Relation.items_tag:Clone *:*:Attribute.Template.Template variable: Process.IMAN_MEFolder:Clone class.*:Reference *:*:Relation. Do not define any tasks. who can then complete associated work on the basis of the data in the PDI. PDI) that creates and adds an appropriate status to structures. Use the Type application to create the necessary status (for example. 3. so that users know the effectivity of the data provided. 4. you would not release individual processes or operations. PDI). Edit the Baseline site preference to identify the baseline procedure you wish to use.) You cannot release product data in the manufacturing environment. by setting the product and plant configuration rules to match the rules applied when you created the process baseline. Release product data with Product Structure Editor. Use the Workflow application to define a baseline release procedure (for example. Before you baseline a process structure. The processes and operations are related in the in-process assembly.Tasks and Use Cases Creating a Preliminary Data Indicator You can create a preliminary data indicator (PDI) or baseline of a manufacturing process that is in development. This ensures you can reproduce the process structure if necessary. and you would typically release them as a set. BaselineSuffix). the product structure and plant structure must have a baseline or release status. ENG00025 D Teamcenter Manufacturing User’s and Administrator’s Manual 5-23 . (To reproduce the exact baselined process or composition. BaselineSuffixRule) and attach it to the item types (for example. You would normally release PDIs at defined intervals. 2. You can then release the PDI to other users and external suppliers. Typically. you must: 1. you must baseline the associated product structure and plant structure. although Teamcenter Manufacturing does not constrain you from doing this. Before creating baselines. Use Business Modeler to create a naming rule (for example. Example of Baselined Process If you baseline a process. 5-24 Teamcenter Manufacturing User’s and Administrator’s Manual ENG00025 D . Teamcenter does not attempt to baseline consumed parts or assigned work areas. Figure 5-5.Chapter 5 Tasks and Use Cases Figure 5-5 shows an example of a baselined process in which the product and plant are also configured. as it assumes the manufacturing engineer does not own this data. If necessary. ENG00025 D Teamcenter Manufacturing User’s and Administrator’s Manual 5-25 . Collect all occurrences of interest from the product and process structures.Tasks and Use Cases Creating an Intermediate Data Capture You can capture the state of any structure or part of a structure for subsequent retrieval and viewing. and put them in structure contexts in the collaboration context. so it is referred to as an intermediate data capture (IDC). the captured data can be updated with any changes. see Collaboration Context Help. 6. and save it in Teamcenter. 5. Create a document that describes the conclusions of the project and save it with the composition. Add other nodes needed for the project to the structure context such as resources. you can open the IDC and compare the captured data with the current configuration of the product. Set closure rules for the composition that specify the objects of interest for capture. and release in the same way as other Teamcenter objects. Set the configuration rule for the product data and save it with the structure context. add it to the new structure context. An example scenario in which you use an IDC follows: 1. 9. 7. 8. The configuration rules are saved with the structure allowing its exact state at the time of capture to be reproduced each time it is retrieved. An IDC is a PLM XML file that you can manage. At a later time. 2. and instantiate the product occurrences into the composition. For further information about creating and manipulating IDCs. Create an IDC from the composition that includes only the objects of interest. The document may be updated if the project data changes. Create a composition structure. Creating an IDC does not affect any subsequent changes to the structure or its release by a Workflow process. 3. 4. parts from other products. and documents. This capture data does not represent the final released state of the structure. Initiate a project to validate how a product is manufactured and create a collaboration context to store the data needed. share. To do this. several tabs appear in the panel. and Factory Structure Editor applications. such as ItemRevision. You can open a bookmark file in NX or Teamcenter Visualization. Customizing the Data Tabs Display If you have administrator privileges. Tabs that only appear when particular components are selected in the parent panel. Part Manufacturing Planner. selection-specific group of tabs is displayed. Manufacturing Structure Editor. For more details. There are two types of tabs in each application: • • Tabs that always appear for a particular parent panel regardless of whether anything is selected. see Manufacturing Structure Editor Help. for example: BOMLine CfgAttachmentLine ImanItemBOPLine • The subtype of the selected display component. the system checks four criteria: • The class type of the selected display component. it is the occurrence type and for attachment lines it is the relation to the parent. • • 5-26 Teamcenter Manufacturing User’s and Administrator’s Manual ENG00025 D . The class type of the underlying component. When a user runs one of these applications and selects the data panel. which is generally the same as the class type. To determine the tabs to display. set the required view and choose the File→Save Bookmark menu option. or Collaboration Context Help.Chapter 5 Tasks and Use Cases Creating a Bookmark If you want to save a view in a shared directory or export it to another machine. However. You can change the tabs that appear by editing the application properties file. for BOM lines. create a bookmark file that contains the desired view. you can customize how data tabs display in the Collaboration Context. You can customize how the second. The subtype of the underlying component (the component type name). Part Manufacturing Planner Help. InClassAtt. in the Collaboration Context application. Attachments.underlying component classtype.TABS=Referencers.underlying component classtype.TABS subtype. Variant.TABS=Referencers. CMEViewer.TABS=Referencers.TABS For example. CMEViewer. CMEViewer. IncrementalChangeInfo GDELine. Report. IncrementalChangeInfo CfgAttachmentLine. IncrementalChangeInfo MEAppearanceLine.ItemRevision. Variant. InClassAtt.ItemRevision.TABS=ProductAppearance CfgAttachmentLine.TABS=ProductAppearance ImanItemBOPLine. CMEViewer. IncrementalChangeInfo. Attachments.underlying component subtype. Attachments.TABS=Referencers. Report.ItemRevision. You can edit these properties to change the tabs that are presented to the user: Display Display Display Display Display Display component component component component component component classtype.TABS subtype.TABS classtype.underlying component subtype.TABS=Referencers. IncrementalChangeInfo ImanItemBOPLine. IncrementalChangeInfo GDELinkLine. the system checks for six properties and add all the tabs found. Report. the default properties are: BOMLine.TABS=InClassAtt You can add or delete the names of tabs that are displayed for each data panel in this file. IncrementalChangeInfo AppGroupBOPLine. CMEViewer. CMEViewer.TABS classtype. Report.TABS=Referencers. ENG00025 D Teamcenter Manufacturing User’s and Administrator’s Manual 5-27 . InClassAtt. CMEViewer. Attachments. InClassAtt.Tasks and Use Cases For each selection.TABS subtype.TABS=Referencers. Report BOMLine. TABS=Referencers. 5. To hide unconfigured changes. By default. Configure the change types to use with incremental change with the Change Management application. To do this. To change this label. 2.Referencers. OPGanttChart MEProcessRevision. you must extract the mpp. incremental changes are not enabled. see the Teamcenter Engineering Configuration Guide. 4. as follows: MEProcessRevision.Types= OPGanttChart.properties. Define a release status that is attached to an incremental change when the user first creates it. ProcessAttachments. For more information. add the following line to the mpp_locale. For example. Incremental_Change_ReleaseStatus=Pending The status must already exist and have an Access Manager rule that allows write access to objects with this status. To enable incremental changes. Configuring Incremental Changes If you plan to use incremental changes to control the manufacturing process.CLASS=com. For more information. set the Incremental_Change_Management preference to true. set the ShowUnconfiguredByChangeEffectivity preference to true. as described in Change Management Viewer Help.cme.properties and mpp_locale. see the Rich Client Customization Programmer’s Guide.Flow. Report. 3. By default.Types= MEProcessRevision.OPGanttSubPanel OPGanttChart.Types= MEProcessRevision. you must complete the following steps: 1.ICON=/com/ugsolutions/cme/images/megant. By default.mpp. Ensure an In IC Context rule is available in Access Manager. all incremental changes (configured and unconfigured) are visible to the user.TABLABEL.properties file: OPGanttChart. you may need to enable the GANTT chart tab before you can view this information. allowing a user write access to a released structure.Flow.ProcessAttachments. see the Teamcenter Engineering Configuration Guide.jar file and edit the Process item Revision section of mpp. Depending on how your system is set up. 5-28 Teamcenter Manufacturing User’s and Administrator’s Manual ENG00025 D . For detailed information about customizing tabs. the label on the tab is OPGanttChart.properties files from the portal.Chapter 5 Tasks and Use Cases Enabling the GANTT Chart for Processes and Operations You can view a roll up of processes and operations in the GANTT chart.gif The first line of this example is edited to add the OPGanttChart entry and the last two lines are added.TABLABEL=Gantt Chart The label should now show Gantt Chart. the following setting creates each incremental change with a Pending status.ugsolutions. the process planner can collect them into a technical portfolio that may contain all the operation and process documentation for a particular assembly line. and 3D snapshot (product views). ensure the following preferences are set correctly: • IMAN_MEWorkInstructure_relation_primary Lists the object classes that can be pasted into a work instruction using this relation. • TCPublishing_Aliases.Tasks and Use Cases Creating Templates for Publishing Manufacturing Data Teamcenter Manufacturing provides an integration with the Teamcenter Engineering Visualization Publish feature. For more information about setting preferences. • TCPublishing_MRU_Alias_File Contains the most recently used alias file. including work instructions.IMAN_MEWorkInstruction The names of the available alias files for work instruction pages. graphics. such as assembly personnel. The process planners use these templates to create publishing pages that may include text. When all the publishing pages are complete. assembly instructions or any other documentation needed for your processes. Publishing pages is a general term for any document used by manufacturing personnel. maintenance instructions. Users manipulate publishing pages and portfolios in the data tabs of the Collaboration Context application. see the Configuration Guide. ENG00025 D Teamcenter Manufacturing User’s and Administrator’s Manual 5-29 . tables. To use this feature. If this preference is not set. You should also ensure that the Dataset_DefaultChildProperties preference for each user contains the following settings: IMAN_PublishingPageAssetContext IMAN_PortfolioPage IMAN_PortfolioConfiguredPage These settings allow users to cut and paste publishing pages and portfolios. you must install Microsoft Visio on each workstation that is used to create or view publishing pages. • TCPublishing_Clear_Alias_Before_Load Determines if Teamcenter clears the alias file when loaded or if changes are appended to the existing file. Before starting. • TCPublishing_Default_Alias_File The name of the installed alias file. This allows you to create publishing pages that can be view or printed by nontechnical users with limited computer skills. the user can choose from any alias file in the database. as described later in this section. You create a template for each of the publishing pages types needed in your organization from elements (Visio shapes) that are bound to Teamcenter data. the object path is invalid and the name attribute is the name of the process revision reached from the occurrence using the instancedRef attribute. Each alias may have alternate aliases that may have different paths to the required attributes. In both cases. Teamcenter includes a default alias file that you can use as the basis of your own mapping files and its location is defined in the TCPublishing_Default_Alias_File preference. For the shapes that are bound to Teamcenter data. The path to the object consists of the elements starting from the root element.description"> </alias> </alias> <aliasAlternate name="Operation" path=": Heade. Teamcenter evaluates the alternate aliases in the order you specify them and uses the first path that resolves to data in the alias file.Occurrence[RootRefs] tells Teamcenter to follow the header root element to a process occurrence. an entry of Header. you may be able to get the name from an operation revision or from the occurrence directly.. the root is the process occurrence.name"> <aliasAlternate name="Name" path="ProcessRevision[InstansedRef]. map the fields of the shape to the appropriate aliases you defined in the previous step and to a closure rule.ProcessRevision[RootRefs]"> <alias name="Name" path="name"> <alias name="Description" path="description"> </alias> </alias> This example defines an operation alias that has two alternate paths to reach the field.ProcessOccurrence[RootRefs]. Each alias file contains a header element that points to the root object of interest. Lay out the necessary shapes in Visio.PrcessRevision[RootRefs]"> <alias name="Name" path="ProcessRevision[InstansedRef].RevisionName"> <alias name="Description" path="ProcessRevision[InstansedRef]. Save the alias file under the TCPublishingAlias dataset. similar to the following example: <alias name=”Operation” > <alias name=Name><alias></alias> <alias name=Description><alias></alias> </alias> <aliasAlternate name="Operation" path=": Header. Optionally. You can use any standard shape supported in Visio or any custom shape created in Teamcenter Engineering Visualization Publish.Chapter 5 Tasks and Use Cases Creating a Template To create a template: 1. For example. 3. If the user selects the root element for the shape as the process revision. Shapes are bound to Teamcenter data by entries in a PLM XML alias mapping file. 5-30 Teamcenter Manufacturing User’s and Administrator’s Manual ENG00025 D . the name is the field that Teamcenter extracts from the operation revision. For example. 4. 2. If the header is not an occurrence. Define the necessary aliases in the mapping file to associate with the template. the root object is the process revision.Heade. If the user selects the process occurrence. you can also bind a shape to the UID of the root object. then enter a name and description for the new dataset. 2. later in this section. 2. Updating a New Publishing Alias To update an existing publishing alias from a modified alias file. ENG00025 D Teamcenter Manufacturing User’s and Administrator’s Manual 5-31 . In the list of dataset types.Tasks and Use Cases Creating a New Publishing Alias To create a new publishing alias from an existing alias file. you must load the alias file. do the following in My Navigator: 1. Each time you modify an alias dataset. Choose the Edit→Cut menu option to remove the existing named reference for this alias. Each time you create an alias dataset. Teamcenter updates the publishing alias. browse to the modified alias file and click OK or Apply. Click the Import button. later in this section. do the following in My Navigator: 1. Right-click the dataset and choose the Named References option. select TCPublishingAliases. as described in Loading the Alias File. you must reload the alias file. 3. Click the Import button. 3. Teamcenter creates the new publishing alias. as described in Loading the Alias File. browse to the new alias file and click OK. Choose the File→New→Dataset menu option and Teamcenter displays the New Dataset dialog window. click OK or Apply to load and unload alias files as necessary. When editing an existing publishing page. 5-32 Teamcenter Manufacturing User’s and Administrator’s Manual ENG00025 D . Create a new TCPublishingPage or load one of the publishing page templates. When the aliases are listed correctly. Select the viewer panel and verify that the publishing page is loaded. select it in the Available Aliases panel and click the + button. You can configure Teamcenter to show each publishing context in a separate tab. To remove (unload) an existing alias. For example. In your embedded Visio application. An asset is typically 3D geometry. If you update an existing alias dataset by replacing its named reference. Save the new or changed publishing page to associate it with the selected occurrence. 3. with available aliases listed in the left-hand panel and loaded aliases listed in the right-hand panel. 3. or a 2D image. 2. an empty page is displayed. reload it by checking the Reload aliases check box and clicking OK or Apply. 4. To load a new alias file. click the Add File by Name button and browse to the newly created alias dataset. the user may use the following procedure: 1. do the following in My Navigator: 1. If none exist. 2. a product snapshot view. To load a newly created alias dataset that is not already listed in the Available Aliases panel. Open the data tabs and select the tab for the required type of publishing page. the user can add.Chapter 5 Tasks and Use Cases Loading the Alias File To load or reload the alias file. Teamcenter displays the Load Alias File dialog window. remove or edit Visio shapes and associate them with Teamcenter assets. Working With Publishing Pages When creating and editing publishing pages. select it in the Loaded Aliases panel and click the – button. a Manufacturing user selects the Work Instructions tab and the tab shows all the publishing pages associated with the occurrence by an MEWorkInstructions relationship. Browse though the existing publishing pages or create a new publishing page from a template defined as described previously in this section. 4. Open a configured structure in the Collaboration Context application and select an occurrence. choose the File→Load Alias menu option. geometric dimensioning and tolerance symbols and rich text may not display correctly in the thin client. while a field titled Quantity would not. and converted to Formatting Object (FO) files.Tasks and Use Cases Displaying GD&T Symbols and Rich Text in Forms You can configure any form to contain geometric dimensioning and tolerance symbols or rich text in forms. You can generate forms in two formats: • HTML Teamcenter generates a PLM XML file from the process structure. Users may only edit or add geometric dimensioning and tolerance symbols or rich text in a field after clicking the edit button next to the relevant field. you add their names to the GDT_fields preference. Part Manufacturing Planner. For example. ENG00025 D Teamcenter Manufacturing User’s and Administrator’s Manual 5-33 . interpreted with XSL stylesheets. You can apply normal Access Manager rules to any form that contains geometric dimensioning and tolerance symbols. the user saves changes and leaves edit mode. To define fields that may contain geometric dimensioning and tolerance symbols. a field titled Work Instruction would be a good candidate for geometric dimensioning and tolerance symbols. The information must then be converted to PDF format by a third-party formatting tool. which is parsed. When editing or additions are complete. a user can add geometric dimensioning and tolerance symbols to the field in any instance of the form. control characters or font formatting from the buttons provided or the keyboard. • PDF Teamcenter generates a PLM XML file from the process structure. Once a field is added to this preference. They may then enter symbols. You can activate geometric dimensioning and tolerance symbols for any type of form. Detailed usage information is given in the online help for the applications that support this feature including Manufacturing Structure Editor. interpreted with XSL stylesheets. This feature is only supported in the rich client. and converted to HTML files. which is parsed. including master forms for a Teamcenter Engineering object. You can print and view reports that are generated from forms that contain geometric dimensioning and tolerance symbols or rich text. and Collaboration Context. in practice. you would restrict them to fields intended for engineering data. It is possible to include geometric dimensioning and tolerance symbols in any field of a form but. Remove the following setting in from the form_user. Whenever Teamcenter sees these attributes in a form.ugsolutions. Define the values previously held in the GDT_fields preference in the GDT_properties preference. work_instruction and tolerance. replace them with a \ character.Chapter 5 Tasks and Use Cases Migrating From Previous Releases If you used this feature in a previous release of Teamcenter Manufacturing. Define your form type information in the GDT_formtypes preference.iman. do the following to migrate to the Teamcenter 2005 SR1 implementation: 1. by setting preferences or by implementing XML stylesheets. for example. c. the name of the field is defined in the GDT_properties preference. do the following: 1. see the Configuration Guide. and enter a list of form type names as the value of this preference. Similarly. register Demo GdtForm as Demo\ GdtForm. XML stylesheets override any preference settings: This feature is only supported on Microsoft Windows systems. For detailed information. Prepare the names of GD&T and rich text properties as follows: a. In My Navigator. This preference contains the form types that contain geometric dimensioning and tolerance symbols. Ensure you have a supported browser installed on your workstation if you want to view or print HTML reports of information containing GD&T symbols.AutomaticGdtIMANForm 2. If the name of your form type contains empty spaces.properties field: <FORM TYPE="">. Configuring GD&T Symbols and Rich Text in Forms There are two ways to activate GD&T symbols and rich text in forms. Using Preference Settings To activate this feature with preference settings.form. Teamcenter recognizes these form types and. This preference contains a list of field titles that may contain geometric dimensioning and tolerance symbols or rich text. For example. Prepare a list of form attribute names—the attribute names you want Teamcenter to recognize. 3. For this preference. it renders this field as a GD&T/rich text field. 5-34 Teamcenter Manufacturing User’s and Administrator’s Manual ENG00025 D . if a form of one of these types has a GDT field (that is. it renders the attributes with a GD&T or rich text form field.FORMDEFINITION=com. see the Configuration Guide. For detailed information. create a new preference at the SITE level or above called GDT_formtypes. If the preference does not exist. choose the Edit→Option-→Search menu option and find the GDT_properties preference. create it at the SITE level or above. b. not UNIX. d. enter the names of the GD&T and rich text text form fields you want Teamcenter to recognize in the Values field. ENG00025 D Teamcenter Manufacturing User’s and Administrator’s Manual 5-35 . For this preference. 2. You can also use the XML style sheet mechanism to override these settings. If the preference does not exist. create a new preference at the SITE level or above called GDT_formtypes. Create the form types that can display geometric dimensioning and tolerance symbols or rich text. 4. Copy the gdtex. replace them with a \ character. Start the Schema Editor and create new classes that have attributes listed in the previous step under POM_object. if a form of one of these types has a GDT field (that is. Prepare the names of GD&T and rich text properties as follows: a. Teamcenter renders GD&T and rich text fields as specified by the GDT_properties and GDT_formtypes preference entries. you can also create item master forms or item revision master forms to support GD&T and rich text in those master forms. You must install this font file on every workstation where HTML are generated. and enter a list of form type names as the value of this preference. 3. you may create a new class called DemoGdtForm. create new form types that use the class you just created as the underlying POM class. Copy the Teamcenter Manufacturing report templates (. For example.Tasks and Use Cases You have now defined names of GD&T/rich text attributes (fields) and form types. If the name of your form type contains empty spaces. viewed or printed. do the following: 1. b. By default. Teamcenter recognizes these form types and. c. In My Navigator. the name of the field is defined in the GDT_properties preference). Verify you can now display and edit geometric dimensioning and tolerance symbols or rich text on the appropriate forms.ttf font file from the rich client installation directory to the FONTS directory of your Microsoft Windows system. Similarly. create it at the SITE level or above. register Demo GdtForm as Demo\ GdtForm. for example. Similarly. and can export the data into reports. In the Type application. as described in Using XML Style Sheets. as follows: a. Using XML Style Sheets To activate this feature with XML style sheets. choose the Edit→Option-→Search menu option and find the GDT_properties preference.XSL files) into the com\ugsolutions\cme\cmereport\default_files directory. later in this chapter. it renders this field as a GD&T/rich text field. b. Define the attributes for GD&T and rich text as String type with the maximum length possible. work_instruction and tolerance. For example. enter the names of the GD&T and rich text text form fields you want Teamcenter to recognize in the Values field. 5. you might create a new class called DemoGdtForm. b. comments and tolerance are rendered GD&T or rich text. you can also create item master forms or item revision master forms to support GD&T and rich text in those master forms. 2. Define the attributes for GD&T and rich text as String type with the maximum length possible. Create the form types that can display geometric dimensioning and tolerance symbols or rich text. Similarly. as described in the previous section). You must install this font file on every workstation where HTML are generated. Define an XML style sheet for the form type that contains GD&T or rich text fields. In the Type application. These rendering hints override any conflicting preference settings. In this example. Copy the gdtex. For example. The following XML example shows a style sheet for a form. as follows: a. 4. viewed or printed. Teamcenter uses the default renderer (it checks if a field is contains GD&T or rich text by looking at the preference settings. <rendering> <page title="General" titleKey="General" format="TwoColumn"> >firstcolumn> <property name="Quantity" modifiable="false"/> <property name="comments" renderingHint="gdtpanel" modifiable="true"/> <separator/> <property name="tolerance" renderingHint="gdtpanel" modifiable="false" /> </firstcolumn> <secondcolumn> <property name="work_instruction" renderingHint="textarea" modifiable="false"/> </secondcolumn> </page> <page title="Reservation" titleKey="Reservation"> </page> <page title="Project" titleKey="Project"> </page> <page title="All" titleKey="All"> </page> </rendering> 5-36 Teamcenter Manufacturing User’s and Administrator’s Manual ENG00025 D . Start the Schema Editor and create new classes that have attributes listed in the previous step under POM_object. By default.Chapter 5 Tasks and Use Cases You have now defined names of GD&T/rich text attributes (fields) and form types. while work_instruction is rendered as a text area. Teamcenter renders GD&T and rich text fields as specified by the GDT_properties and GDT_formtypes preference entries. create new form types that use the class you just created as the underlying POM class. You can also use the XML style sheet mechanism to override these settings. Enter gdtpanel as the rendering hint of the intended GD&T and rich text fields. If you do not give a rendering hint. as described in step 4. 3.ttf font file from the rich client installation directory to the FONTS directory of your Microsoft Windows system. but possible options include FOP. you must write XSL style sheets that define how GD&T and rich text should be translated into FO format.properties file from the default value of 50 and restart Teamcenter. Generating PDF Reports To generate reports from PLM XML data.dll library.Tasks and Use Cases 5. locate this file on the Teamcenter installation CD. and copy it into your system path. Verify you can now display and edit geometric dimensioning and tolerance symbols or rich text on the appropriate forms and can export the data into reports. increase the value of the EDITOR_UPDATE_LATENCY variable in the com\ugsolutions\iman|from\gdt\gdt. UGS does not provide or endorse a particular formatter. If the display of GD&T and rich text becomes unstable when you type quickly. XEP. Examples of the necessary style sheets are given in the Rich Client Customization Programmer’s Guide. If Teamcenter indicates it cannot find the corojdk11. You should also install a suitable third-party formatter to convert FO files into PDF files. You may want to test each of these options with your report data to determine which formatter gives the best results. and Standard FO + MathML. ENG00025 D Teamcenter Manufacturing User’s and Administrator’s Manual 5-37 . This instability occurs on slower machines. Click the Attachments tab. For example. You can view or print these reports with a Web browser. and the comparative number of bought and manufactured parts. 5-38 Teamcenter Manufacturing User’s and Administrator’s Manual ENG00025 D . Each part is linked to others to show the hierarchy in the assembly structure. you may want to create a report that details the usage of various machined components in assembly operations. as follows: 1. welds. quantity. Thumbnail pictures can also be included if required. Optionally. 4. see Report Generator Help. and Make/Buy status. For more information about generating reports. Select the process or operation on which you want a report and click the Report tab in the right panel.Chapter 5 Tasks and Use Cases Creating Reports in the Rich Client Teamcenter Manufacturing provides a framework on which you can create reports that are relevant to your manufacturing processes and a Report Generator that produces the predefined reports. Click the Generate Reports button to create the report. 3. Teamcenter Manufacturing extracts the following information: • • • The name or identification of each part consumed in the manufacturing process. You can double-click the report to open and view it. Detailed information about each part. such as the dimensions. you can click the Save button to save the report you generated. A graphical representation of the manufacturing structures and assemblies. 2. The generated report is shown as an attachment to the process or operation item revision. Click the button next to the Type field and select a report from the list of available types. A summary page may define the total number of components. From the definition of the product structure. ENG00025 D Teamcenter Manufacturing User’s and Administrator’s Manual 5-39 . 3. you must configure your Web browser and related settings. as described later. if you have not already done so.Tasks and Use Cases Configuring Reports in the Rich Client If you use the Report Generator application to create reports and view JT files. • If you are using the Microsoft Internet Explorer browser. During installation. Similar configuration steps are necessary if you are using another operating system.1 and run its setup program. turn off the Virtual Machine (VM) and enable Java. 5. If you are using the Netscape or Mozilla browsers. and mark up the image. as appropriate. then close and reopen the browser to complete any changes. try to avoid spaces in installation directory names. you must install the Java Runtime Environment (JRE). 4. This setting should be updated by the rich client viewer setup program. gather measurement data. • Install the rich client viewer version 5. choose the Tools→Internet Options menu option and the Internet Options dialog window appears. Click OK or Apply. For correct operation of this functionality. Teamcenter Manufacturing runs a Java™ applet that allows you to manipulate the view. Locate the Java (Sun) group of entries and ensure the Use Java 2 entry is checked. You can create this new environment variable as a system variable or a user variable for the current user. this procedure is not required. You should also create a PLMVIS_51_LIBPATH environment variable and set it to PV_Base_Dir\Program. as these may cause incorrect operation in certain circumstances. Deselect all entries in the Microsoft VM group. You should also verify that the PATH variable contains the PV_Base_Dir\Program. you can create a environment variable by choosing the Start→Settings→System menu option and clicking the Advanced→Environmental Variables tab. In Internet Explorer. as follows: The following instructions assume you are configuring a Microsoft Windows system. To do this: 1. If this entry does not appear. Click the Advanced tab and locate the Microsoft VM group of entries. where PV_Base_Dir is the base installation directory of the rich client viewer software. 2. If you are using Microsoft Windows. clear your current browser.Chapter 5 Tasks and Use Cases • Install and configure the JRE. 5-40 Teamcenter Manufacturing User’s and Administrator’s Manual ENG00025 D . If you changed the Java Runtime Parameters in the previous step.2_06 or earlier. Click the Advanced tab and ensure the Java Runtime Environment field contains the following entry with no spaces or line breaks: -classpath <PV_Base_Dir>\java. This loads the new environment variable setting into the browser. check each applicable checkbox. Display the Java console by choosing the Start→Settings→Control Panel→Java Console menu option. you must set the classpath variables with an = sign instead of a space. the applet is not registered.jar.com and follow the installation instructions provided. while for newer versions you would enter –classpath=C:\path. In later versions.security. as follows: 1.policy file in your JRE_HOME\lib\security directory with a text editor. • Modify the Java security settings to allow the browser to open the rich client viewer and JT files in one of the following ways: – Edit the java.AllPermission. – Use the policytool. then recheck the current browser and click Apply again. with older versions of Java. • Click the Browser tab and ensure that the checkbox for your browser is selected. For example. 2. Click the Basic tab and ensure the Show Java in System Tray checkbox is checked. This ensures the Java console is always present in the Windows system tray. If you enter an incorrect character. See the Sun documentation for information on using this tool. Add the following entry to this file: grant { permission java. you can select the Show Console button to open the Java console for debugging purposes whenever the applet is active. allowing easy access to it for troubleshooting.exe application in your JRE_HOME\bin directory to grant the same permissions. 4.<PV_Base_Dir>\java\VisWebS. click Apply. 3.<PV_Base_Dir> \java\eaisupportS. not a word processor. This example is correct if you are using Java 1. you would enter –classpath C:\path **. Download the JRE for your local language from http:/java. If you have more than one browser on your system. }. Optionally. if it is not already installed on your system.jar.4. jar and VisWebS. Choose the Start→Settings→Control Panel menu option and select the icon that matches the version number in the Java console window.system. If so. Verify there are no typographical errors or unnecessary spaces in the classpath definition.params property and check it contains the classpath string you entered when you configured the Java console. Ensure the eaisupportS. as described in Configuring Reports in the Rich Client. an Applet CMEReportJTViewerApplet not initiated error message may be displayed in the browser status line. Note the displayed value of the javaplugin.jar files are included in the classpath. you can place the modified java. Close all browser windows before testing changes. or if you also have the Java Software Development Kit (SDK) installed. On other platforms (including Windows XP).NoClassDefFoundError: com/eai/visweb/components/<AnyClassName> Possible solutions: – Check the Java console and verify the correct classpath is set. if the directory does not exist. identify the policy deployment directory by opening the Java console. open the Java console and check for error codes that may indicate the cause of the problem.policy file in the directory indicated by this property. create it. there may be more than one copy of the java.policy file in the Documents and Settings\<your user name> directory.lang. as described previously in this section. earlier in this chapter. there may be more than one Java control panel and you have not modified the correct one. typing s to dump all system properties. open the Java console and type s to dump all system properties. On many versions of Windows. Place your modified java.policy property.security.Tasks and Use Cases If you have more than one version of the JRE on your system. – ENG00025 D Teamcenter Manufacturing User’s and Administrator’s Manual 5-41 . Modify the classpath for this Java control panel.policy file. and noting the displayed value of the deployment. If possible.jre. – If the classpath is not correct. identify the version that is used by the browser. This error is identified by an error message similar to the following: java. as follows: • NoClassDefFoundError Java cannot access the rich client viewer JAR files. To view the classpath. Troubleshooting Reports in the Rich Client If the visualization feature does not work correctly. 4. earlier in this chapter. This error is identified by an error message similar to the following: java.4.NoSuchMethodError: sun.2_04. • NoSuchMethodError This error may be caused by a bug in certain versions of the JRE. including JRE 1. • VerifyError The JRE version is incompatible with the HTML page.jar file and update it if necessary.changeFrameAppContext To resolve this problem.dll Java does not have permission to execute the jawt. method: destroy signature: ()V) Incompatible object argument for function call at java. To resolve this problem. 5-42 Teamcenter Manufacturing User’s and Administrator’s Manual ENG00025 D .Class. and update it if necessary.lang. This assumes that you want to use the last version of the JRE that was installed.applet. Verify you have installed the correct version of the CMEReportJTViewer. This error is identified by an error message similar to the following: java. as described in Configuring Reports in the Rich Client. Verify that you have updated the Java security policy file correctly. – • Viewer window has no image The viewer window shows a green background and the icons are visible.lang. but there is no image in the window. as specified in the Teamcenter Engineering 2005 SR1 Release Bulletin. try right-clicking in the JT window and choosing All On or Fit All from the popup menu.AppletPanel.2_04.getDeclaredConstructors0(Native Method) Possible solutions: – Ensure you have installed the supported JRE version. typically JRE 1.VerifyError: (class:CMEReportJTViewerApplet.Chapter 5 Tasks and Use Cases • Could not load library jawt.dll file. try modifying the Java Runtime Environment definition to Use Java Plug-in Default.lang. visweb.java:718) .eai.components.Viewer3D. This error is identified by an error message similar to the following: An unexpected exception has been detected in native code outside the VM.java:285) Possible solutions: – – Install an updated version of the rich client viewer. Ensure you have the latest version of the CMEReportJTViewer.dll Current Java thread: at com.Tasks and Use Cases • EXCEPTION_ACCESS_VIOLATION The version of the rich client viewer you have installed is not compatible with the CMEReportJTViewer. You must also update the PATH environment variable and modify the classpath for the new version.eai.locked <0x108c3938> (a java.components. Creating Reports in the Thin Client The manufacturing report generation functionality in the thin client requires the Report Generator and PLM XML features of Teamcenter.shutdown(Viewer3D.Object) at com.PrimaryViewer.removeNotify(Module. ENG00025 D Teamcenter Manufacturing User’s and Administrator’s Manual 5-43 . Unexpected Signal : EXCEPTION_ACCESS_VIOLATION (0xc0000005) occurred at PC=0x6FD24D6 Function=Java_com_eai_visweb_components_PMI3D_nativeHideEntity+0x1D9 Library=C:\WINDOWS\system32\VisWeb. Visualization allows you to create and view 2D and 3D images in reports.eai.jar file in the reports directory.Module.components.nativeDestroyViewerDone (Native Method) at com.visweb.jar file in the reports directory.lang.visweb. Ensure that you have the appropriate Java Runtime Environment (JRE) and Visualization software installed on your system. 2. For more information. • IMAN_Report_Transfer_Area Contains the location of the temporary working directory where reports are generated (%IMAN_ROOT%\web\htdocs\web_reports). Ensure this subdirectory has global read and write permissions. 3. For more information. later in this chapter. if not. If not. Valid values are Process-Structures. Set this preference to web_reports. see the Teamcenter Engineering Visualization documentation. Check if a temp subdirectory exists in the %IMAN_ROOT%\web\htdocs\web_reports directory and. create it.jar file exists in the %IMAN_ROOT%\web\htdocs\web_reports\jar directory. install them as described in Installing the Report Designs. install it as described in Installing the Transfer Mode.Chapter 5 Tasks and Use Cases Prerequisites for Generating Thin Client Reports Before you can generate reports in the thin client. Set the required preferences for generating thin client reports. Check if the web_reports transfer mode is available and. 7. if not. Check if a jar subdirectory exists in the %IMAN_ROOT%\web\htdocs\web_reports directory and. 4. Setting Preferences for Thin Client Reports You must set the following preferences to generate reports in the thin client: • TC_suppress_report_designs Hides one or more manufacturing reports in the navigator. Product-Structures. 5-44 Teamcenter Manufacturing User’s and Administrator’s Manual ENG00025 D . create it. Check if the Teamcenter Manufacturing Web reports are installed in the database. as described in Setting Preferences for Thin Client Reports. later in this chapter. 5. • IMAN_TransferMode_XMLReport Contains the name of the transfer mode used when generating XML files containing reports. The CMEReportJTViewer.jar file contains the applet necessary to export reports. You must also install and set up the Visualization toolkit libraries. if not. If not. 6. the site administrator must configure it as follows: 1. following. copy it from the rich client ROOT directory. and Plant-Structures. Check if the CMEReportJTViewer. which are provided as a DLL file for Microsoft Windows systems. this JAR file is provided with the Teamcenter Visualization Mockup or Teamcenter Engineering Visualization installation files. Ensure the Teamcenter Engineering Visualization software is installed and configured for viewing 2D and 3D images in rich client. see the relevant Visualization documentation. txt). ENG00025 D Teamcenter Manufacturing User’s and Administrator’s Manual 5-45 .Tasks and Use Cases • Batch_Report_Request_File Contains the location of the flat file that defines how batches of reports are generated (%IMAN_ROOT%\web\htdocs\web_reports\data\batch_request. • WEB_MECollaborationContext_shown_relations= Contains the relation types to show with the MECollaborationContext object. see the Configuration Guide. MEResourceContext and PrivateContext objects. • WEB_StructureContext_shown_relations= WEB_MEProductContext_shown_relations= WEB_MEProcessContext_shown_relations= WEB_MEPlantContext_shown_relations= WEB_MEResourceContext_shown_relations= WEB_PrivateContext_shown_relations= Contain the relation types to show for all types that fall under the StructureContext. • Show_Msv_Occurrence_Types= Set to True to apply filters on occurrence types for data included in the reports. • Web_Report_Jars Contains the location of the report JAR files for the JT viewer (%IMAN_ROOT%\web\htdocs\web_reports\jar). For more information about setting preferences. If you encounter problems with the operation of this feature. rather than relative paths. • WEB_CCObject_shown_relations= Contains the relation types to show with the CCObject object. If you are using incremental change to manage data included in the reports. you should also set the Incremental_Change_Management preference to true. Each should be set to IMAN_reference. MEPlantContext. try setting absolute paths in these preferences. MEProcessContext. Set this preference to IMAN_CCContext and IMAN_reference. Set this preference to IMAN_CCContext and IMAN_reference. MEProductContext. xml file from the web\htdocs\iman\intl\loose folder to the web\htdocs\iman\intl\lang folder. links to open the Manufacturing Structure Viewer and the Product Structure Editor are not provided in the left-hand navigation panel. you must update the Teamcenter Manufacturing report design formatters in the database. 2. Restart the supervisor. Open a Teamcenter shell and enter the following command to install the default report designs: install_default_report_designs -u=infodba -p=infodba -g=dba -file=%IMAN_DATA%\report_writer\default_report_designs. To add these links: 1. for example: file=C:\Tceng1001\imandata\mfgweb\report_writer\default_report_designs. Installing the Report Designs Before you can create thin client reports. as follows: 1. en for English). 2. Copy the toolbar.xml 5-46 Teamcenter Manufacturing User’s and Administrator’s Manual ENG00025 D . Open a Teamcenter shell and enter the following command to install the default report designs: install_default_report_designs -u=infodba -p=infodba -g=dba -file=%IMAN_DATA%\report_writer\default_report_designs.Chapter 5 Tasks and Use Cases Adding Links to the Thin Client User Interface By default. Ensure that all users are logged out of the system. as follows: 1. where lang is the folder for your local language (for example.xml Ensure you include the complete path in the file argument.xml You can also install the report designs manually with the Report Designer application. Ensure that all users are logged out of the system. Updating Report Designs If you change report designs.xml -update_formatter Ensure you include the complete path in the file argument. for example: file=C:\Tceng1001\imandata\mfgweb\report_writer\default_report_designs. you must install the Teamcenter Manufacturing report designs in the database. 2. 4. ensure the product structure related to the process structure is open in the product window before you request this report. ENG00025 D Teamcenter Manufacturing User’s and Administrator’s Manual 5-47 . This report requires the Operation_WeldData. for example: file=C:\Tceng1001\imandata\mfgweb\default_Transfermodes. Creating Weld Reports for Operations You can create a weld report for an operation that is selected in the Manufacturing Structure Viewer. run the rep_batch_report utility by entering the following command: rep_batch_report -u=username -p=password -g=group For more information about running utilities. you must install a PLM XML transfer mode by running the following command from a Teamcenter shell: %IMAN_BIN%\plmxml_import -u=infodba -p=infodba -g=dba -xml_file= %IMAN_DATA%\defaultTransfermodes. Open the Report Designer application in the rich client. To create a batch of reports manually. 3. Add Operation_WeldData. Select the Process_Structures report design.xsl formatter. Use the sample script located in the IMAN_ROOT/web/htdocs/web_reports/data folder as the basis of your script and modify it to set the environment. 2. If this formatter is not visible when you select an operation in the Manufacturing Structure Viewer. Click the Modify button.xsl from the list of available report formatters to the list of selected formatters for a Process_Structures report design. you create a batch request file and define its location in the Batch_Report_Request_File preference.xml Running Batch Reports To create batches of reports. Ensure the file identified by this preference has global read/write permissions. You can also create a scheduled task that creates batches of reports automatically. do the following: 1. see the Utilities Reference manual.Tasks and Use Cases Installing the Transfer Mode To create reports.xml Ensure you enter the complete path for the xml_file argument. However. This command changes the database schema. Create this form type by running the following command from a Teamcenter shell: plmxml_import -u=infodba -p=password -g=dba -xml_file=%IMAN_ROOT%\web\htdocs\web_reports\data\Operation_Welds.xsl report formatter uses a new form type called OperationWelds.xml This command creates the new OperationWelds form type in the database that you can attach to an operation. 5-48 Teamcenter Manufacturing User’s and Administrator’s Manual ENG00025 D . it is not necessary to regenerate the schema manually.Chapter 5 Tasks and Use Cases The Operation_WeldData. . . . . . .Chapter 6 Integrations With Other Products NX CAM Integration . . . . . . . . . . . . . 6-6 Collaboration Context and Tecnomatix Integration . . Working With the NX CAM Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Extending the Classification Hierarchy with a New Class . . . . . . . . . . . . . . . . . . . . . . . . . . Loading CAM Data Into Teamcenter . . . . . . . . . . . . . . . . . . . . . 6-6 ENG00025 D Teamcenter Manufacturing User’s and Administrator’s Manual . . . . . . . . . . . . . . . . Creating Operation Types for the NX CAM Integration . . . . . . . . . . . . . . . . Modifying the CAM Integration to Display Additional Data Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1 6-2 6-3 6-3 6-4 6-5 FactoryCAD Integration . . . . . . . . . . . . . . . . . . . The FactoryCAD Integration that links Teamcenter Manufacturing and FactoryCAD. NX CAM Integration Teamcenter Manufacturing provides an interface to the NX Manufacturing application. and IPW into Teamcenter Manufacturing. shop documents. Linking Teamcenter Manufacturing with Tecnomatix process planning software using the collaboration context feature. 2.Chapter 6 Integrations With Other Products This chapter describes how Teamcenter Manufacturing interacts with external products. machine tools. ENG00025 D Teamcenter Manufacturing User’s and Administrator’s Manual 6-1 . Figure 6-1 shows how data that is defined in the NX Manufacturing application can be stored and managed in Teamcenter Manufacturing. PTP. Capture output from the NX Manufacturing application. Access the process plan created in by the process planner in Teamcenter. including CLSF. This chapter describes the following topics: • • • The NX CAM Integration that links Teamcenter Manufacturing and NX. allowing you to: 1. tooling and fixtures from NX CAM Integration. Capture and manage NC data in the Teamcenter Manufacturing environment. 4. 3. Access resources stored in Resource Manager including templates. Chapter 6 Integrations With Other Products Figure 6-1. Data associated with an operation may include the duration. machine parameters. The process planner generates work instructions from the activities. 3. including the NC setup. tooling and in-process models are available in Teamcenter Manufacturing. machining and inspection. 1. and shop floor documents. drilling. grinding. It assumes that the process planner has created the overall process plan in Teamcenter Manufacturing. 6-2 Teamcenter Manufacturing User’s and Administrator’s Manual ENG00025 D . 4. and target specifications. NC operations and other information available in Teamcenter Manufacturing. In addition. PTP. The process planner creates an NC operation in Teamcenter Manufacturing as part of the overall process plan. the process planner specifies the tooling and machine tools in the planning environment. CLSF. The NC programmer generates the necessary NC program information and this is also available in Teamcenter Manufacturing. The NC programmer can view these assignments. tooling. Using NX CAM Integration Data in Teamcenter Manufacturing Working With the NX CAM Integration The following sequence shows how Teamcenter Manufacturing transfers data between the process planner and the NC programmer. The NC programmer can add. or remove tools specified for the operation if additional criteria are identified. Optionally. 2. 6. The process planner may assign resources that are required by NC setups. modify. 5. The definitions are based on planning data such as data from an MES system. Typical operations may include milling. as Teamcenter Manufacturing updates the CAM environment. and the cutting tools. the NC programmer may create NC setups within a process and route them from within the CAM environment. its clamps and fixtures. Select MEOP operation. which includes all items included in the NX CAM setup templates and any additional resources. and verify that an MENCProgram activity was automatically created under the operation with the program name defined in NX CAM. Enter the name of the new type in the New subtype name field. By default. the operation is visible in the Setup Selection dialog in NX. Teamcenter Manufacturing displays the setup. Refresh the operation if necessary. 2. 4. and after assigning this type to a planning operation. To create a new operation type: 1. you can generate a CLSF file or postprocess the data to generate a PTP file.Integrations With Other Products Alternatively. the NC programmer may create tools in the NC environment and save them in Teamcenter Manufacturing. 4. In the Type application. You then save these files and documentation in Teamcenter Manufacturing and verify the results. For more information on setting preferences. open the Operation type. as follows: 1. 5. Open Part Manufacturing Planner and select the operation for which you generated CAM data. only an operation of the MENCMachining type is visible in NX. You can also create NX shop floor documentation that contains information about the CAM objects. ENG00025 D Teamcenter Manufacturing User’s and Administrator’s Manual 6-3 . You can create a new operation type specific to your needs. Check the PTP and CLSF files are added as datasets to the activity. These items may include the workpiece itself. Click the Attachments tab in the right-hand panel and verify the NX shop floor documentation is attached to the operation revision as a dataset. You can select any operation type supported by NX and specified in the NX_supported_operation_types preference. Click Create. Expand the selected operation. the machine tool. At the same time. Click the Operation Activities in the right-hand panel. 3. Creating Operation Types for the NX CAM Integration The NX CAM Integration allows you to see certain planning operation types that are created in Teamcenter in NX. double click these files to open them in a text editor. 3. Add the new name of the new type to the NX_supported_operation_types preference. see the Configuration Guide. 2. Loading CAM Data Into Teamcenter If you create CAM data in the NX CAM Integration. you can select your new operation type. see Manufacturing General Help in the NX Help collection. Add all necessary class attributes. 5. The new class ID is TAM0250. Create a new class in the Classification Administration application. to hold five parameter milling tools. You can find this file in the directory where NX is installed.Chapter 6 Integrations With Other Products Now. The new class now appears in the NX Library dialogs when you search for a tool in NX. To do this. When you open the part in the NX CAM Integration. Custom_Mill_Tool. or a complete discussion of NX Library. As NX supports only a limited number of tool types. The following steps show how to create a new class. 4. These are based on the attributes that appear in the tool dialogs within NX CAM. the operation appears in the list of visible operations in NX. proceed as follows: 1. these must be reflected in the NX Library dialogs so that you can search in the new classes from within NX. Every tool type within NX requires its own minimum set of attributes. To see the mandatory parameters necessary for a five parameter milling tool.def in an editor. Add the new class to the class hierarchy section of this file as explained in Entering the DB_Alias in the Class Hierarchy in the NX Library Help. Attribute numbers –1 to –1000 are reserved for UGS internal use only. Keep in mind that the NX Library mechanism only reflects tool assemblies found in the Resource Management→Tools→Assemblies branch of the classification hierarchy. 6-4 Teamcenter Manufacturing User’s and Administrator’s Manual ENG00025 D . see Classification Administration Help. For the example. 2. when you create a new operation in Part Manufacturing Planner. For more information on how to create a class in Classification. Open MACH\resource\library\tool\inclass\dbc_inclass_tlas. Restart NX and Teamcenter. you need to map every new tool assembly in Teamcenter to a tool type in NX. you must create the Custom_Mill_Tool class within Resource Management→Tools→Assemblies→Milling. see NX Library → Customizing NX Library → Creating New Classes & Subclasses → Mandatory Parameters for Classes in Manufacturing General Help. 3. Extending the Classification Hierarchy with a New Class If you are extending your Teamcenter Classification hierarchy with new classes. 3. you must customize Teamcenter to recognize these new data types. 8. Display the new document type in the activity along with the post processor files. you can display these files in Part Manufacturing Planner. enter the file type in the Format column. Ensure that NX CAM saves the new file type in the following directory: %TEMP%/item ID_xxx 2. 11. 9. Expand the Tools hierarchy and select Open. For more information about extending dataset types. 12. In the Admin group in Teamcenter. Enter the ending of the file type in the File column. Now. see Creating and Managing Dataset Types in Type Help. 7. Click OK. 14. Once you do this. activate the Select and Export check boxes. select UGCAMCLSF.nc. NC. for example. . ENG00025 D Teamcenter Manufacturing User’s and Administrator’s Manual 6-5 . NX stores a file with the . 4. Click Modify. 5. Select Parameters. the NX CAM Integration searches in the TEMP directory for those file extensions that you have customized using these steps and lists them in the Import ME Datasets for Part dialog window. b. Teamcenter displays the new data type in addition to all CL source files. If you want to: a. for example. Part Manufacturing Planner can display the files with the new data types in the activity or as an attachment. and shop floor documentation files with the operation in Part Manufacturing Planner. Display the new document type in the activity along with the CLS files.Integrations With Other Products Modifying the CAM Integration to Display Additional Data Types If you want to extend the NX CAM Integration to save files in an additional file format with your part file. Select Dataset Type. postprocessor. Select References. c. Customize the NX CAM Integration as follows: 1. Enter a reference name in the Reference column. select UGCAMShopDoc. Click to add a new line to the list of references. If the file is not a text file. select UGCAMPTP. 6. when you save an operation in NX CAM. open the Type application. If. 13. In the References List. Display the new document type as an attachment along with the shop floor documentation files. 10. for example.nc ending. while administrators can manage the synchronization process with the Application Interface Viewer in My Navigator.Chapter 6 Integrations With Other Products FactoryCAD Integration FactoryCAD is an optional UGS addition to the third-party AutoCAD product that allows you to design plant structures and layouts. each containing the definition of a shared product. then install additional components located in the Advanced Installations directory of the product CD-ROM. which are folders. you must install the collaboration context feature provided with Teamcenter Engineering. You can integrate the two systems. so that Tecnomatix or Teamcenter Manufacturing can share common data. The collaboration context contains one or more structure contexts. 6-6 Teamcenter Manufacturing User’s and Administrator’s Manual ENG00025 D . To ensure the shared data is always synchronized. Users can view and manipulate the shared data with the Collaboration Context application. it shares many data items with Teamcenter Manufacturing. Collaboration Context and Tecnomatix Integration Tecnomatix process planning software allows you to design manufacturing processes and manage them at the point of execution. or as JT files for visualization. or plant structure. revise. in which the data is linked to the product design. or department. and view the plant structure. Create and edit the plant structure. process. Configure. 3. You can import the completed design into Teamcenter Manufacturing and manage the design data as follows: 1. in which the shared data resides. 2. section. For detailed information about this integration. To obtain these capabilities. As such. see the Teamcenter Manufacturing Tecnomatix Collaboration Context Integration manual. you can define a collaboration context. Store FactoryCAD model files in DWG format. You can break the structure into logical groups by station. Appendix A Glossary ENG00025 D Teamcenter Manufacturing User’s and Administrator’s Manual . . Activities can be sequenced using time data and predecessor activities. Application Interface Viewer Viewer data tab in applications that allows users to monitor and control PLM XML data exchanges between Teamcenter Engineering and another application through a collaboration context. Activity Individual action to be performed within an operation. The appearance set enables Teamcenter Engineering to rapidly search the product structure of a family of related configurations without caching the entire product structure for each configuration. Application Interface Web Service Teamcenter Engineering extensions to a Web service such as gSOAP or WebLogic. Each activity is associated with a start time and duration.Appendix A Glossary This appendix defines Teamcenter Engineering terms. The total time for the operation is based on the cumulative duration of all activities within the operation. Appearances are created to allow quick searches of the entire structure. The system administrator defines the items requiring appearance sets. You can define data on the absolute occurrence that overrides the data stored on the item when you select the context assembly and view the structure. The appearance set is optional and typically maintained for a few end items that represent large assemblies when fast searching is critical. Appearance Set Collection of objects that define the use of every part ever included in an end item. Appearances Cache of configured BOM lines in the context of a specific top-line item. The parent assembly is the context in which the absolute occurrence exists. A Absolute Occurrence Relationship between a parent assembly and an item one or more levels lower down the structure. Application Interface Web Service includes a ENG00025 D Teamcenter Manufacturing User’s and Administrator’s Manual A-1 . AIWS See Application Interface Web Service. These extensions allow Teamcenter Engineering to share data in a collaboration context with another application. Appendix A Glossary SOAP server. B Base Product View The as designed bill of materials of the product. Assembly Classification Resource assembly ID and name of the class where the assembly is classified. and the holder type of the machine adapter can all be propagated to the assembly level. Assembly View View of the product data. In Resource Manager. Users can search the database for objects using the object’s attributes. See also BOM and Manufacturing View. BOM Bill of material. See also Design Bill of Material and Manufacturing Bill of Materials. an attribute is a name/value pair. BPV See Base Product View. the cutting diameter of the extension. For example. classes are displayed with class folder icons because they represent an aggregation of objects. color. while noncompound objects are called components. and price combination. Attribute Named storage variable that describes an object and is stored with the object. Assembly Compound object that is assembled from other objects and may add additional information to their interpretation. This provides a mechanism to make all attributes required for a cutting tool definition available at the tool assembly level. In an object. A-2 Teamcenter Manufacturing User’s and Administrator’s Manual ENG00025 D . Attribute Propagation Process of transferring attribute values from one object to another. An assembly classification is also the process of associating an assembly with a class and entering the attribute values that characterize it within its class. Class Folder Representation of aggregation of objects. but each car associated to the Automobile class has a different brand. In the Classification and Classification Search dialog class hierarchies. on a cutting tool. For example. attribute values are propagated from a propagation start point up the assembly structure to the assembly object. other assemblies are called subassemblies. C Class Set of objects that share the same list of attributes but distinguishable by the value the attributes acquire for specific objects. Contrast with Manufacturing Bill of Materials. Application Interface Web Service components are installed and deployed as part of the Web tier. in the database. In the context of an assembly. the cutting material of the insert. and price. color. an attribute is a field. the Automobile class can be defined by the brand. Collaboration Context Teamcenter Engineering application that enables users to view and manipulate data in a specific context. A cloning rule can also be applied when creating a structure from a template. but drill bit objects differ in length and diameter. The reference is the same type as the one in the template. Closure Rules In a collaboration context. ENG00025 D Teamcenter Manufacturing User’s and Administrator’s Manual A-3 . and the third-party applications themselves. such as Microsoft Office Integration and Teamcenter 2005 Integration for AutoCAD. such as Microsoft Office and AutoCAD. Teamcenter Engineering integrations with third-party applications.Glossary Class Hierarchy Structure defining subclasses that inherit the attributes of their superclasses. Classification Process of categorizing objects according to similarity in characteristics. For example. a set of rules that defines how structures are created when copying other structures of the same type. Classification Instance Lowest level component of the classification hierarchy in the Classification Search dialog window. While the objects in one class share the same characteristics. Component Objects used to build up an assembly or subassembly. Collaboration Context Project folder or directory that contains data shared by Teamcenter Engineering and a third-party application. Classification Hierarchy Structure used to categorize a company’s product data by common attributes. drill bits all share the length and diameter characteristics. Clone and Reference Copy action rule when using templates to create process structures. It may contain references to any other item in Teamcenter Engineering and such shared items may be modified by Teamcenter Engineering or the third-party application. the values of these characteristics may differ. Client Tier Teamcenter Engineering architectural tier that comprises the Teamcenter Engineering clients. Composition Special kind of structure context that allows components to be added from one or more structure contexts. Compositions are used for design studies and manufacturing processes that contain data from both product and plant structures. also called their parents or ancestors. Cloning Rules In a collaboration context. each of which may contain a different product structure. The object is copied to the database and a reference is made to the database clone. an ordered list of rules that define the objects included. See also Collaboration Context. and clone. Compare with Manufacturing Bill of Materials. One of the operations in the assembly process uses the delivery unit as a consumed part. The components of a delivery unit are not consumed in any of the operations. D Delivery Unit Subassembly that is manufactured separately and delivered to the assembly plant as a consumed part. E Effectivity Rule Rule used to set effective dates on released products and processes with a released status. grease. Smaller sites can run the pool of servers on the same host as the Web tier. Design Bill of Material List of components and subassemblies used to define an assembly structure. and closure rule applied to a collaboration context. End Item Top-level node of an assembly that can represent a product or a factory structure. reference. and the representation of the assembly structure itself.Appendix A Glossary Configuration Context In Collaboration Context. A device is designed to work as part of a machine tool or robot. Device Complex assembly that is represented as a simple component. The relation type is the same as in the template. Larger sites can distribute the pool of server processes across multiple hosts. and gloves. eM-Planner Interface Interface between Teamcenter Manufacturing and Tecnomatix eM-Planner that allows data exchange. variant rule. Copy Action Rule Predefined rule that defines how template is used to generate processes. Actions commonly performed include ignore. a revision rule. Copy by Reference Copy action rule when using templates to create process structures. The same database object is referenced in the clone. Enterprise Tier Teamcenter Engineering architectural tier that comprises a configurable pool of Teamcenter Engineering C++ server processes and a server manager. A-4 Teamcenter Manufacturing User’s and Administrator’s Manual ENG00025 D . A consumed item can include parts or components from the product structure in addition to materials such as oil. Consumed Item Item that is required during a manufacturing process or operation and must be ordered regularly to meet the production quota. a logical attribute of a product. a signal. or part. or part. group folders represent a group of related classes. F Factory Structure Editor Teamcenter Manufacturing application that allows users to design. ENG00025 D Teamcenter Manufacturing User’s and Administrator’s Manual A-5 . See also Generic Design Element. each of these aggregations has a different type of folder icon associated with it: a group folder icon. Alternatively. and enterprise tier. client tier. a class folder icon. resource tier. A feature may be represented by a generic design element (GDE) in a BOM. The Web tier. Group Type of class that does not have a list of attributes associated with it. Generic Design Element BOM item that cannot have different revisions. See also Feature. import.Glossary Equipment Description of the equipment used to perform manufacturing operations. Four-Tier Deployment Deployment of the Teamcenter Engineering four-tier architecture. Four-Tier Architecture Teamcenter Engineering architecture that includes four tiers: resource tier. or a subclass folder icon. G GDE See Generic Design Element. Group Folder In the Classification Search dialog. modify. Examples: a weld point. class. component. or a geometric pattern. component. Folder Graphical representation of an aggregation of objects. or subclass. Web tier. enterprise tier. H Hierarchy Structure in which each node can have only one parent but possibly multiple siblings and children. highest level in the classification hierarchy. and client tier can each be hosted on the same or separate computers. For easy distinction in the class hierarchy. and export a factory structure. such as a group. Feature Physical or geometric object associated with a product. These components can be consumed in operations if their parent assembly is not consumed. A-6 Teamcenter Manufacturing User’s and Administrator’s Manual ENG00025 D . Input Data In-process model and other data generated from the previous steps in an operation. A collection of geometry and geometric references and attributes that provide the means for creating work instructions for a manufacturing process. Compare with Design Bill of Material. weld points. The instance can correspond to a line in the BOM. rather than how it is designed. In-Process Model Product resulting from application of a manufacturing operation. Processes can have both sequential and parallel ordering. There is one root per database. operations. Manufacturing Feature Teamcenter Engineering item. Manufacturing View Hierarchical structure of occurrence groups. Manufacturing Structure Editor Teamcenter Manufacturing application that enables a user to design a plan detailing how to manufacture a product. They are associated with a product and a work area. Instance Single data object that is associated to a class. The components of subassemblies in the manufacturing view represent references to lines in the targeted product structure. The manufacturing view describes the components and subassemblies used by the assembly operations. MBOM See Manufacturing Bill of Materials. See also Assembly View. See also Feature. M Manufacturing Bill of Materials Defines how the product is manufactured. No action is taken to duplicate the object in the cloned structure. Ignore Copy action rule when using templates to create process structures. including holes. pockets. Manufacturing Process Collection of manufacturing subprocesses.Appendix A Glossary I ICM Root Folder Folder that anchors the classification hierarchy in the Classification Search dialog. and die faces. There are several types of features. and activities that make up a process plan. A manufacturing operation typically addresses several features of the same type. Output data can be the resulting in-process model and any instructions for the next step. Plant Manufacturing facility described by a hierarchical structure of work areas. Each method can be used by several manufacturing operations to perform work on different features. The occurrence path does not change if the configuration of the BOM changes. An occurrence group typically represents an assembly. Process Revision Modified version of a process. a work cell.Glossary Method Description of how equipment is used to perform work on a feature. different BOMs cannot contain the same occurrence paths. and individual workstations. It is the lowest revisable element in the manufacturing process structure. Process Operation Step in the manufacturing process executed at a specific work area. Multiple View Editor Teamcenter Manufacturing application that enables a user to describe and visualize the state of a product as it moves through a sequence of manufacturing processes and operations while maintaining associations to the product structure and the process/operation structure. Output Data Data generated as a result of applying instructions to input data. O Occurrence Hierarchical structure relationship between the immediate parent assembly and its child component item or item revision in a precise assembly. An occurrence path is unique to the context of a specific BOM. Occurrence Path Representation of the path from a top level assembly to an occurrence of a component or subassembly. alternative methods for building the target item. Different levels in the hierarchy represent the plant. ENG00025 D Teamcenter Manufacturing User’s and Administrator’s Manual A-7 . Compare with Product Structure and Process Structure. A process revision can be used to handle different configurations of assemblies. or changes to methods. Sometimes called relative occurrence. Occurrence Group Collection of occurrences and absolute occurrences in the BOM. P Part Manufacturing Planner Teamcenter Manufacturing application that enables a user to design a plan detailing how to manufacture a part. Plant Structure Hierarchy of the physical layout of a work area. This allows one set of appearances that can be configured by the effectivity of the part they represent. Product View Saved configuration of the assembly viewer. This BOM can then be loaded to display the configured variant. including the selection of objects.Appendix A Glossary Process Structure Hierarchy of manufacturing processes and operations with a sequenced relationship that together describe how a related product is manufactured. Product Structure Hierarchy of assembly parts and component parts with a geometric relationship between them. Compare with Product Structure. zoom factor. Examples of resources include robots. Propagation Process of transferring characteristics of one object to another object. Variant and revision rules define the generic BOM. Resource Assembly Set of resource components and/or subassemblies that are grouped to create an assembly to be used in a process. A-8 Teamcenter Manufacturing User’s and Administrator’s Manual ENG00025 D . Resource Item used to perform an operation or define a process. and machines. and pan displacements. All appearances of a product are collected into a set that is associated with one revision rule. PSP See Propagation Start Point. such as a manufacturing process. Propagation Start Point Component within an assembly structure that is the starting location for propagation. Product Appearance Persistent representation of a product line. for example. Both standard equipment and custom tools can be identified as resources. Product Item or assembly (hierarchy of components and subassemblies) to be manufactured. R Raw Material Initial in-process model before any manufacturing operations are performed. a bill of materials (BOM). Report Generator Teamcenter Manufacturing application that provides a format for producing reports about information in Teamcenter Manufacturing. Relative Occurrence See Occurrence. rotation angle. tools. Hierarchies are usually displayed as hanging trees with the root of the structure at the top and the leaves at the bottom. The setup also identifies the parts consumed and the resources used. washers. and an assembly structure represents how components and subassemblies are associated to build up an assembly. In Resource Manager. Resource Manager Teamcenter Manufacturing application that enables a user to store and retrieve resource-related data such as tools. classes. file servers. and Resource Manager.Glossary Resource Browser Plug-in component that allows users to retrieve classification-related data. The structure context can contain occurrence groups. and screws. See also Collaboration Context. a classification structure represents classes and their inheritance dependencies. Root Starting point of a hierarchy. most structures are hierarchical. and item revisions. and classification objects from a Teamcenter Engineering database when working in an external application. bolts. Resource Component Object that is a component of a resource assembly or subassembly. Part Manufacturing Planner. The structure can be viewed in several applications. fixtures. For example. Structure Context BOM or assembly structure contained in a collaboration context. Structure Representation of multiple objects and their interdependencies. such as a hierarchy with corresponding groups. and volumes. machines. they acquire the form of a tree where each node can have only one parent but multiple siblings and children. Collaboration Context. In a manufacturing view. including Product Structure Editor. Spare Part Small item that in Resource Manager is commonly entered as other components are. See also Delivery Unit and Workpiece. Resource Tier Teamcenter Engineering architectural tier comprising the database server. either a delivery unit or a workpiece. and process templates from a company-wide accessible database. Subassembly Assembly that is built into the assembly structure of another assembly or intended for that use. ENG00025 D Teamcenter Manufacturing User’s and Administrator’s Manual A-9 . Resource Structure Structure in which resource assemblies are hierarchically built. Examples include nuts. S Setup Configuration of the work area. Manufacturing Structure Editor. For example. database. items. a class might define the physical and accounting attributes for its objects. but a view for tool designers might display only the physical attributes. T Top Level Object at the root of a product structure where a process plan is being developed. Attribute properties can also be applied. View Tailored representation of objects within a class. Views are associated with abstract and storage classes. WebDAV service. such as robots and NC machines. which inherit every attribute of their parent classes and cannot be edited. The work area can represent the entire plant. V Variant Condition Rules applicable to one component in a product structure. and a view for accountants might display only pricing and order number attributes. Users can generate a hierarchy of work areas that is unique to their organizations. A-10 Teamcenter Manufacturing User’s and Administrator’s Manual ENG00025 D . Variant Rule Option Description of product variations that are usually applied to higher level assemblies or the product itself. an engine for a tractor where the tractor is the end product). There are two categories of work instructions: • • Human readable instructions are primarily used to provide information to the operator about how to perform the operation. The Web tier application also includes the Application Interface Web Service (AIWS). and thin client. Work areas are described by their location on the shop floor and the process capabilities they provide. Unlike classes. W Web Tier Teamcenter Engineering architectural tier that comprises a Java application running in a Java 2 Enterprise Edition (J2EE) application server. an individual work cell. users can define the inherited attributes assigned to a subclass. The Web tier is responsible for communication between the client tier and enterprise tier. Work Instruction Document that describes how an operation should be completed at a work area. or a station within the plant. Work Area Plant location performing an operation. Subclasses inherit the attributes of their parent classes. subclass instances represent a subset of attributes corresponding to a class. the work line. The top level can be either an end product being manufactured or a subassembly used in the end product (for example.Appendix A Glossary Subclass In the Classification Search dialog. Machine instructions are program files that include numerical code used to run numerically controlled machines. Teamcenter Engineering DIS Adapter. For example. the workpiece is positioned in the work area and the work instructions are performed. The resulting workpiece then flows to the next operation in the sequence. In each step of the manufacturing process.Glossary Workpiece Intermediate state of the product during the manufacturing process. where the next operation is performed. ENG00025 D Teamcenter Manufacturing User’s and Administrator’s Manual A-11 . . . . . . . . . . . . . 3-8 5-20 . . . . . . . . . Access control . . . . . . 3-5 FactoryCAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3 2-19 2-20 2-20 2-18 2-19 . . 7 . . . . . . . . . . . Adobe Acrobat Reader . 4-2 . . . . . . . . . . . . . Classification. . . . . . . . . . . . . . Code . . . . . . . Values . designing . . . . . . . . . . . Command line entries File contents . . . . . . . . . . . . . . . . . . . . . 9 5-31 . . . . . . . . . . . . . planning . . . . Consumed material . . . customizing Documentation . . . .. . . . Configuring . . . . . . . . . . . Assembly manufacturing. . . . . . . . . . . . . . . . Aliases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Operation . . .. . . . . . . Warning icons . . Compositions . . . . . . description . 2-3. . . . . . . . . . 2-9. . Command Suppression . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Fixture. . . . . . . . . Associating data in context . . . . . . . . . . . 7 . . . . . . . . . . . . 3-3 2-16 Caution icons . . . . . . . . . . . Note icons . . . . . . . . . . . . . 5-4 . 7 . . . . . . . . . . . 5-26 C CAM data. . . . . . . . Reference structures . . . . . . 5-28 GD&T symbols in forms . 2-2 . Controlling access . . . . . . . . . . . . . . . 5-33–5-34 Generic design elements (GDEs) . .. . . . . . . . . . . . . . . . . 5-26 . . . . . 2-9 2-11 2-11 5-34 . description . . planning Assembly operations . . 9 . . . . . Online help . . 9 Effectivity . . 4-6 . . . . Command line entry conventions . Cloning rules. . . . . . . . . . . . . . . 7 . . . . . . . . . . . . . Managing incremental . . . B Baseline . . . . . 3-5 Factory structure. . . . 4-8 File contents conventions . . . . . . . Revisions . . . . 2-12 . . . Configuring processes with rules . . . . . . . . . . . . . . APIs . . . . . . . . . . .. . . . . . . . . . Code conventions . 2-8 . . . . . 3-7 . . . . . . . . . . . . . . . 3-9 . . . . . 3-5 FactoryCAD Integration . . . . . . . . . . . . . 2-2 5-21 . .. . . . . 5-14 Forms Adding GD&T symbols . . . 5-23 Bookmark. . . . . . . . . . . . . . . . . . . . . . . . . . . . . E . . Tracking . . . 9 . . description . . . . . . . . . . . . . 5-16 Flexible components . . . 2-18. . . . . importing . . . . . . 2-18 ENG00025 D Teamcenter Manufacturing User’s and Administrator’s Manual Index-1 . . . . . . . . . . Conventions . . 5-11 . . . enabling . . . . . . . . 6 . . . . . . . . . . . . . . . . . . . . . . . . . 4-1 F Factory Structure Editor. . . . . Appearances. . . . . . . . . . . . . Consumed items . creating . . . . . . . . . . . . . . . . . . . . . 8 . . . . . . Collaboration context . . . . . . . . . . Syntax definitions . . . . . . . . . . . . . . . . . . . . . . . . . 6 . . . . . . . . . . .Index A Absolute occurrences . . . . . . . . . . . . . . . . D . Collaboration context. . . . 6 3-9 Data tabs display. . . . . . . . . 6-6 . . . . . . . . . . . . . . . . . . . . . 6-6 Features . . . . . controllingOccsForProcessConfiguration preference . . . . . Changes Configuring . . . . . . . . . . 6 . . . . 5-33 G GANTT chart. . 6 . . . . . . . . . . . . . . . . . . . . . . ACLs . . . . . . . . . . Configuring with intents . . . . . . . . . 4-8 I ICO . . . . . . . . . . . . Customization . . . . . . . . . . . . . . . defining . . . . . Printable files . . . . . . . . . . . . . . . . . . . . . . . searching for . . 6 . . . . . . . . 3-4. 2-2 . . . . 2-12 . . . . . . . . . . publishing pages . . . . . .. . . . . . . . . . . Names . . . . . . . . . . 7 . . . . 5-33 Adding rich text . . Activities Assigning to operations . . . . . . . . . . . . . . Configuring changes . . . 5-37 PDI . . . . . . Items . . . . . . . . . . . . 2-19 . . . . . . . . . . . . . . . . . . . . 4-4–4-5 Process templates . . 5-15 . . . Creating . Assigning activities . . 3-8 Product structure. . . . . . . . . . . . .. . 5-12 2-13. . . . . . . . . . . . . . . Planning . . . description . . .. 6 . . . . . . . 2-15 NX CAM Integration . . . . 3-5 . . . . . . . . . . . . 3-5 5-17 . see Intermediate data capture Imprecise structures . . . . . . creating . . . . . . . . . . . . . . . . . 2-20 . . Associating data with Examples . . . . Description . . . . . . . . . . . . . . . Intermediate data capture. . . . . . . . . 4-2 . . . . . . Manufacturing Structure Editor. Intents . . . . . . . . Controlling access . 4-1 . . . . . . . . . . . . . . . . . . . 2-14 Process operations . . . 5-12 . . . . . . . 2-16 Defining NC machining . . . . . . . . . . . . . . .Index Icon conventions . . . . . . . . . . . . . . . . . . . . . . . 4-4 . . . . . . 2-18 . . . . 5-44 Preliminary data indicator . . . . . . .. . Options . . . . . . . . . . . . . . . . managing . . . 5-9 Releasing processes . . . . Manufacturing BOM . . 2-17 Process operation data . . . . creating top level . . . . 4-5 . . . . . 5-23 Plant structure Creating from template . . . . . . . . . . . . . Verifying . . . 1-2 Precise structures . . . . . . . . . . . . . 2-19 . . . . . . . . . . . . . . . . . 5-43 Java security . . . . . . . . . . . J . . 5-28 . . . . 5-18 Definition . . . . . . . . . . . . . . 2-18 . . . . . . . . . . 2-2 . 3-3 . . . . . . . . . . . . 5-18 Definition . . . 2-2 Flexible components . . . . . definition . . . . . 4-2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8 . . . description N Name conventions . . . . . . . . . . 2-20 . . . . . . 3-8 Product views . . . . . . . . . . . . Intents . . . . . 4-4 . . 2-18 Processes. description . Online help . . Definition . . . . . . . . . . . . . 1-2 Editing . . . . . . . . . 4-5 4-2. . . . . . . . managing . . . . . . . . . 5-2 . . . . . . . . . . . 9 . . . . . . . . . . 5-7 . 5-18 Definition . . . . . . . . . . 3-4 PDF reports. . 3-5 P Part Manufacturing Planner. . . . . . . Multiple View Editor. . . . . . . . . . . . . . 4-8 Preferences. Occurrence paths . 5-40 M Manual set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8 4-1. . . . . . . . . . . . . . . . 5-4 Product Structure Editor. . 5-15 . .. . . . . . . . . 6 NC machining . . . . . . . . . . description . . . . . . . . . 9 5-2 1-2 2-3 . . . . 1-3 Process structure . . . . . . . 1-3 . . . . . . . . . .. . . . . . . . . . Incremental changes . . . . . . . . . . 5-23 Process design. . MBOM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-18 Index-2 Teamcenter Manufacturing User’s and Administrator’s Manual ENG00025 D . . . . 2-1 . . 5-29 R Raw material . . . . . . . . . . . . . . . . 5-14 . . . Incremental change order . . . . Tracking changes . . . . . . . . . . . . . . . . releasing . . . . . . . . . . . . . . . . . . . . Manufacturing execution systems Manufacturing features . . . . . . . . . . . 3-4 Process plan. . . . . . . . Operation activities . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . In-process model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 1-3. . . . . . . . 6-1 O Occurrence groups . . . . . . . . . . 5-4 . 5-25 . . . . . . . . . . . . . . Configuring with intents . . . . 2-2 Relationships. . . . . . . Manufacturing process Creating . . . . . . . . . IDC. . . . . planning . . . . . . . . 5-6 Product structure . . . . . . . . . . . . . . . . 2-12 Process. . . . . . . . 2-15 Process plan . . . . . . . . . . . creating Item elements . 2-5 Creating from template . thin client reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Occurrences . . . . 4-4 . . . . . . 1-2 Opening . . . . . . . . . . . . . . . . . . . . . . . . 2-1. 4-7 Java runtime environment (JRE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Operations . . . . . . . . . . . . . . . . consumed . . . . . . . . For in-process assemblies Occurrence paths . . . . . . .. Item revisions . 3-4 Part manufacturing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-18 . . . . Operation setup . . . . . 5-14 Process operation . . . . In-process assemblies . . . . . . . . . . . . . . . . . . . . 5-11 . . . . . . . . . . . . . . . . . . . . . . . . Installation prerequisites . . . . . . . . . . 5-18 Publishing work instructions . . . . 3-2 . . . . . . . . 2-2 Creating from template . . . . . Configuring . . . . . . . . . . . Items. 2-2 . . . . . . . . . . . . . . . . . . . 2-18 . . . . . . . . . 2-13 Assembly and weld . . . . . . . . . . . Adding resources . . . . . . . . . . . . . . . . . . . . . . . generating . . . . . . . . . . . . . . . . . . . . . . Java . . . . . . . . . . . 4-1 Incremental changes . . 5-12 Syntax definition conventions . . . . . . . . . . . 4-1 Rich client viewer Environment variables . . . . . . . . . . . updating (thin client) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Index Report designs. . . . . 2-8 For revisions . . . . 2-17. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Work area. . . . . . . . . . . . configuring in rich client . . . . . . 3-6 Resources . . . . . . . 3-7 Reports Creating in rich client . 5-46 Report designs. . . . . W Weld operations . . . . . . . . . . . . . . . . . 3-4 . . . . . . . 1-3 . . . . . . . . . . . 5-43 . . . . . . . . . . . . . . . . 2-18 Rules . 5-39 Reports. 5-39 Installation . . . . . 5-47 Reports. . . . . . . . . 5-38 Generating . . . . 1-3 Managing . . . . . . . . . . . . . . . . . . . 5-5 . . . . . . . troubleshooting . . . . . . . . . . . . 5-43–5-44 Running batch reports (thin client) . . Creating process structure from . . . . Work instructions . 4-4 Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-46 Installing transfer mode (thin client) . . . . . . . Work instruction data . . . . . . . . . . . . . . . . . 5-12 Explanation . . . . . . . 1-1 . . . . . . . 4-7 S Security. . . . . . . . . . . . . . 5-38 Installing designs (thin client) . 2-8 Revisions . . . . . . 4-3 . . . . . . . . . Work instructions . . . . . . . . . . . . . . . . . . . . . 4-1 Effectivity . . . . . . 5-46 Weld reports (thin client) . . . 2-16 . . . . . . . . . . . . . . . . . . 5-47 Updating designs (thin client) . . . . . . 4-1 Variants . . . . . . . . . . 2-13. 6 Revision rules . . 2-2. . . . . 1-3 . . . . . . . . . . . . . . . . installing (thin client) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . V Value conventions Variant conditions Variant rules . . . 2-2 Adding to operations . . . . . . . . . . . . Assigning . . . . . . . . Creating product structure from . Creating plant structure from . . 5-39 Java security . . . . . . . . scope . . . . . . . Work instructions. . . . . . . . . . . . . . . . Reports . 2-2 . . creating Workflow . . . . . . . Adding links to user interface . . Templates. Technical documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Transfer mode (thin client) . 6 4-7 4-7 4-7 . . process . . . . . . . . . . . . . . . . Tecnomatix process planner . . . 3-4 5-18 5-18 5-18 5-29 2-12 5-14 5-46 5-43 5-47 ENG00025 D Teamcenter Manufacturing User’s and Administrator’s Manual Index-3 . . . . . 6-6 . . . . . . . . description . . . . 3-9 . . . . . . . . . . . 8 T Teamcenter Manufacturing. Tecnomatix integration . . . . . . . . Tecnomatix process planning software Templates . . . . . . . . . . . . . . . . . . . . . 5-33 Rules Configuring processes . . . . . . Workstation. . . . . . . . . . . . Weld reports (thin client) . . . . . . . . . . . . . . 5-47 2-1–2-2. . . . . . . . . . . . 3-7 Resource Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . definition . . . . . . . . . . . . . . . . . Thin client . . . . . . . . . . 3-6 Revision conventions . . . . . . . . . . 5-40 Rich text in forms . . . . . . . . 2-12 . Work area . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-14 . X XALAN . . . . . . . . . . . . . . . . . . . . . . 5-41 Resource Browser. . . . 2-14 2-3. . . . . . 5-46 Report Generator. . . . . description . . . . . . . . 2-8. . . . . . . description . . . . . . . . . . description . 5-40 Setup Assembly structure . . . . . . . . . . . . . . . . . . . 5-13 . . Variants . . . 5-47 Prerequisites for thin client . . . . . . . . .