Team Center Manufacturing User and Administrator Manual

Tecnomatix Teamcenter Manufacturing Users and Administrators Manual

Publication Number ENG00025 D

Tecnomatix Teamcenter Manufacturing Users and Administrators 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

Manual History

Manual Revision A B (Preliminary) B C D

Teamcenter Engineering Version 9.1.2 9.1.2.4 9.1.2.4 2005 (V10) 2005 SR1

Publication Date May 2004 November 2004 February 2005 September 2005 June 2006

This edition obsoletes all previous editions.

2006 UGS Corp. All Rights Reserved. Produced in the United States of America. 2 Teamcenter Manufacturing Users and Administrators Manual ENG00025 D

Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Audience . . . . . . . . . . . . . . . . . . . . . . . . . Organization . . . . . . . . . . . . . . . . . . . . . . Conventions . . . . . . . . . . . . . . . . . . . . . . . Teamcenter Engineering Documentation . . . Submitting Comments . . . . . . . . . . . . . . . . Software Copyright and Trademark Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5 5 5 6 9 9 9

Purpose of Teamcenter Manufacturing . . . . . . . . . . . . . . . . . . . . . . . . . 1-1 Scope of Teamcenter Manufacturing . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1 Structures and Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2 Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3 Basic Concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1 Manufacturing Planning Model . . Process Structure . . . . . . . . . . . . Conguring Processes With Rules Absolute Occurrences . . . . . . . . . Using Compositions . . . . . . . . . . Process Templates . . . . . . . . . . . . Access Control and Workow . . . . Process Operations . . . . . . . . . . . Managing Resources . . . . . . . . . . Releasing a Manufacturing Process Incremental Changes . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1 2-5 2-8 2-9 2-9 2-12 2-12 2-13 2-17 2-18 2-18

Product Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1 Prerequisites . . . . . . . . . . . . . Manufacturing Structure Editor Part Manufacturing Planner . . Multiple View Editor . . . . . . . . Factory Structure Editor . . . . . Resource Manager . . . . . . . . . Report Generator . . . . . . . . . . Collaboration Context . . . . . . . Classication . . . . . . . . . . . . . Product Structure Editor . . . . . Customizing Functionality . . . . Technical Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1 Revisions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1 Occurrences in the Manufacturing Environment . . . . . . . . . . . . . . . . . . . 4-2

ENG00025 D

Teamcenter Manufacturing Users and Administrators Manual

3

Contents

Searching for Appearances . . . . . Variants and Variant Rules . . . . Precise and Imprecise Structures Feature Management . . . . . . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

4-6 4-7 4-8 4-8

Tasks and Use Cases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1 Understanding the User Interface . . . . . . . . . . . . . . . . . . . . . . Creating a Manufacturing Process . . . . . . . . . . . . . . . . . . . . . . Managing Process Design With the Thin Client Interface . . . . . . Working With Flexible Components and NX . . . . . . . . . . . . . . . Working With Occurrences for In-Process Assemblies . . . . . . . . . Designing a Fixture for Manufacturing . . . . . . . . . . . . . . . . . . . Verifying the Manufacturing Process . . . . . . . . . . . . . . . . . . . . Creating Product Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a Process, Product, or Plant Structure From a Template Creating a Preliminary Data Indicator . . . . . . . . . . . . . . . . . . . Creating an Intermediate Data Capture . . . . . . . . . . . . . . . . . . Creating a Bookmark . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Customizing the Data Tabs Display . . . . . . . . . . . . . . . . . . . . . Enabling the GANTT Chart for Processes and Operations . . . . . Conguring Incremental Changes . . . . . . . . . . . . . . . . . . . . . . Creating Templates for Publishing Manufacturing Data . . . . . . . Displaying GD&T Symbols and Rich Text in Forms . . . . . . . . . . Creating Reports in the Rich Client . . . . . . . . . . . . . . . . . . . . . Creating Reports in the Thin Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1 NX CAM Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1 FactoryCAD Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-6 Collaboration Context and Tecnomatix Integration . . . . . . . . . . . . . . . . . 6-6 Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1 Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Index-1

Figures2-1. 2-2. 2-3. 3-1. 5-1. 5-2. 5-3. 5-4. 5-5. 6-1. Example of Fabrication Process . . . . . . . . . . . . . . . . . . . . . . . . Design and Manufacturing Representations of the Same Product Storing Different Information on the Same Components . . . . . . . Typical Resource in Resource Manager . . . . . . . . . . . . . . . . . . . Example of Operation Setup . . . . . . . . . . . . . . . . . . . . . . . . . . Typical Product Structure Template . . . . . . . . . . . . . . . . . . . . . Typical Process Structure Template . . . . . . . . . . . . . . . . . . . . . Process Structure Created from Template . . . . . . . . . . . . . . . . . Example of Baselined Process . . . . . . . . . . . . . . . . . . . . . . . . . Using NX CAM Integration Data in Teamcenter Manufacturing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4 2-5 2-6 3-6 5-12 5-19 5-19 5-20 5-24 6-2

4


ENG00025 D

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. You should understand the contents of this manual before you design a manufacturing process or any of its components.

AudienceThis manual is for persons responsible for using or administering Teamcenter Manufacturing.

OrganizationThis 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. Basic Concepts describes some of the basic concepts behind controlling manufacturing processes with Teamcenter Manufacturing. 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. Tasks and Use Cases describes the main tasks you can perform with Teamcenter Manufacturing. Integrations With Other Products describes how Teamcenter Manufacturing interacts with external products.

Chapter 3 Chapter 4

Chapter 5 Chapter 6

ENG00025 D


5

Preface

ConventionsThis manual uses the conventions described in the following sections.

Revision MarksTechnical changes are marked by a bar adjacent to the changed text.

Note, Caution, and Warning IconsThe following icons represent note, caution, and warning messages: A note icon identies general instructions or comments that need to be emphasized. A caution icon identies practices that can either produce results contrary to what you expect or result in damage to software or data. A warning icon identies practices that could result in permanent loss of data or software.

Names and ValuesThis manual represents system names, le names, and values in fonts that help you interpret the name or value. For example: The le name is pom_schema_server-name_sid. The conventions are: Bold Bold font represents unvarying text or numbers within a name or value. Capitalization is as it appears. In the preceding example, pom_schema_ identies an unvarying portion of the name. Italic Italic font represents text or numbers that vary. The characters in italic text describe the entry. Letters are shown in lowercase, but the varying text may include uppercase letters. In the preceding example, server-name and sid represent varying portions of the name. text-text A hyphen separates two words that describe a single entry. In the preceding example, server-name is a single value. For example, the name of the pom_schema_server-name_sid le may be: pom_schema_Blue5_f731

6


ENG00025 D

Preface

Command Line Entries, File Contents, and CodeThis manual represents command line input and output, the contents of system les, and computer code in fonts that help you understand how to enter text or to interpret displayed text. For example, 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, the computers response, the contents of system les, and computer code. Capitalization and spacing are shown exactly as you must enter the characters or as the computer displays the characters. In the preceding example, create_change_types identies an unvarying portion of the command.

Italic

Italic font represents text or numbers that vary. The words in italic text describe the entry. The words are shown in lowercase letters, but the varying text may include uppercase letters. When entering text, use the case required by the system. In the preceding example, user-name, password, group, and le-name identify varying portions of the command.

text-text

A hyphen separates two words that describe a single entry. In the preceding example, user-name is a single entry in the command.

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.dat

ENG00025 D


7

Preface

Syntax DenitionsThis manual uses a set of conventions to dene the syntax of Teamcenter commands, functions, and properties. Following is a sample syntax format: harvester_jt.pl [bookmark-le-name bookmark-le-name ...] [directory-name directory-name ...] The conventions are: Bold Bold text represents words and symbols you must enter exactly as shown. In the preceding example, you enter harvester_jt.pl exactly as shown. Italic Italic text represents values that you supply. In the preceding example, you supply values for bookmark-le-name and directory-name. text-text A hyphen separates two words that describe a single value. In the preceding example, bookmark-le-name is a single value. [] ... Brackets represent optional elements. An ellipsis indicates that you can repeat the preceding element.

Following are examples of correct syntax for the harvester_jt.pl: command:harvester_jt.pl harvester_jt.pl assembly123.bkm harvester_jt.pl assembly123.bkm assembly124.bkm assembly125.bkm harvester_jt.pl AssemblyBookmarks

8


ENG00025 D

Preface

Teamcenter Engineering DocumentationTeamcenter 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. You can access the printable manuals from the Teamcenter Engineering Documentation CD-ROM. To view the PDF-formatted manuals, use Adobe Acrobat Reader, downloadable free-of-charge from Adobe Systems Incorporated at the following URL: http://www.adobe.com Acrobat Reader allows you to view these manuals online and print selected pages, sections, or the entire manual. UGS grants permission for Teamcenter Engineering users to print, duplicate, and distribute this documentation.

Submitting CommentsPortions of Teamcenter software are provided by third-party vendors. Special agreements with these vendors require UGS to handle all problem reports concerning the software they provide. Please submit all comments directly to UGS. Please feel free to give us your opinion of the usability of this manual, to suggest specic improvements, and to report errors. Mail your comments to: UGS Technical Communications 4233 Lexington Avenue N., Suite 3290 Arden Hills, MN 55126-6198 U.S.A. To submit an incident report, you can use the UGS GTAC online support tools at the following URL: http://support.ugs.com

Software Copyright and Trademark Notices 2006 UGS Corp. All Rights Reserved. This software and related documentation are proprietary to UGS Corp. UGS and Teamcenter are registered trademarks or trademarks of UGS Corp. or its subsidiaries in the United States and in other countries. Java and all Java-based marks are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and other countries. All other trademarks or registered trademarks belong to their respective holders.

ENG00025 D


9

Chapter

1

Purpose of Teamcenter Manufacturing

Scope of Teamcenter Manufacturing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1 Structures and Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2 Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3

ENG00025 D


Chapter

1


Teamcenter Manufacturing allows you to manage assembly and fabrication of products whose design process is managed by Teamcenter Engineering. This chapter contains an introduction to the design of a manufacturing process and its components.

This chapter describes the following topics: The scope of the Teamcenter Manufacturing product. The structures and operations you can create and maintain. How to use resources as part of the manufacturing process.

Scope of Teamcenter ManufacturingThe product design and development lifecycle can be broken into the following stages: Design The development team produces the information that denes the nal product. This includes a complete description of the individual components (for example, geometry and tolerances) and an assembly structure. The design may require several analysis processes to ensure it meets the design specications, for example, stress analysis and thermal analysis. Manufacturing planning In this stage, the manufacturing planning team determines how the product is manufactured. This may include designing an overall plan for the manufacture of the product, and the detailed design of each individual machining or assembly step. After the process design is complete, it may be simulated to verify the reliability of the process by completing activities such as NC tool path verication and weld point allocation.

ENG00025 D


1-1

Chapter 1


Execution You can now assign the individual steps in the manufacturing plan to specic resources, using manufacturing orders or other criteria. When manufacturing commences, manufacturing execution systems (MESs) collect and manage realtime manufacturing information, perform inventory control, and schedule activities. These stages are not necessarily sequential. For example, the manufacturing process may be designed before the product design is complete. This allows the components of a process to be manufactured before the design of the entire product is released.

Teamcenter Manufacturing allows you to manage manufacturing and execution, using information generated in the design stage.

Structures and OperationsTeamcenter Manufacturing allows you to dene and manage preproduction planning information and its subsequent handoff to manufacturing. During the preproduction planning, you dene how, where, and with what resources the product is manufactured. The denitions of interest to Teamcenter Manufacturing users are as follows: Product structure The product structure denes the as-designed product. It is created by the design engineers in a CAD system such as NX and managed by Teamcenter Engineering. Teamcenter Manufacturing allows you to take the as-designed product structure, create alternative manufacturing views of the product and attach process denitions as necessary. (Optionally, the product structure may contain denitions of manufacturing features.) Plant structure The plant structure is a description of the factory in which the product is manufactured. Its denition is independent of, but related to, the manufacturing processes that are performed in it. Process structure The process structure is the model of the complete manufacturing plan, and describes how and where the product is manufactured. It contains information about which plant structure elements are used and where. It establishes links between the product, plant layout, and the resources necessary to produce the product. Operations and resources can be shared by several processes. You can dene multiple views of a process to allow for different manufacturing requirements. You can also vary the generic bill of process (BOP) by dening and applying variant or revision rules.

1-2


ENG00025 D


Process operations A process operation represents one controlled step in the process and contains the work done in one work area; technically, it is a leaf node in the process structure. Optionally, you can break a process operation into steps called activities. The process structure and operations, and the sequence in which they are performed comprise the process plan, which describes how the product is manufactured. Teamcenter Manufacturing provides interfaces to external systems, allowing you to import and export manufacturing data. For example, you can: Import manufacturing feature denitions through the NX CAM Integration Share process structure information with Tecnomatix manufacturing process planning systems. Export information to Visiprise SCE manufacturing execution systems (MES).

ResourcesResources are the equipment needed for the execution of manufacturing processes, and may include machine tools, robots, and weld guns. Shop oor equipment is typically organized into groupings called work areas. A work area is dened by a location on the shop oor and the process capability it provides. To group resources further, your organization may dene a hierarchy of work areas. For example, a plant may include a welding line, a lathe workstation, a milling workstation, and an inspection workstation. The welding line may contain a welding workstation and a welding work cell. You congure each work area with standard equipment, and you can further congure equipment that is needed to execute a specic process operation. The process designer tries to use as much standard equipment in the work area as possible. If additional equipment is needed, the process designer provides work instructions on how to congure the work area with the additional equipment. For example, an NC machining center may be preloaded with standard tools that are commonly used on the machine. If a process operation requires tools that are not preloaded, the operator loads them on the machine when the particular process operation is executed.

ENG00025 D


1-3

Chapter

2

Basic Concepts

Manufacturing Planning Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1 Process Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5 Conguring Processes With Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8 Absolute Occurrences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9 Using Compositions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9 Process Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12 Access Control and Workow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12 Process Operations . . . . . . . . . . . . . . . . . . . . . . Process Operation Data . . . . . . . . . . . . . . . . Dening an NC Machining Process Operation Assembly and Weld Process Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13 2-14 2-15 2-16

Managing Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-17 Releasing a Manufacturing Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-18 Incremental Changes . . . . . Tracking Changes . . . . . Conguring Changes . . . Conguring With Intents Controlling Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-18 2-19 2-19 2-20 2-20

ENG00025 D


Chapter

2

Basic Concepts

This chapter describes some of the basic concepts behind controlling manufacturing processes with Teamcenter Manufacturing.

This chapter describes the following topics: The model on which manufacturing planning is based. The concept of a process structure. How to congure processes with rules and occurrences. Using process templates to aid reuse. Maintaining access control and workow. The components of a process operation. Managing resources to increase manufacturing efciency. Releasing manufacturing processes. Using incremental changes to control modications to manufacturing processes.

Manufacturing Planning ModelThe manufacturing planning model includes several interrelated process and operation types, as follows: Manufacturing process A set of manufacturing process operations and other manufacturing processes that are closely related to each other. It is a mechanism to group operations into logical groups. It also maintains constraints on the order of execution between subprocesses and process operations. Process operation An operation that describes a controlled unit of work that is executed in a single work area with a specic conguration. Detailed work instructions describe how the operator or machine resources execute the operation. Examples of process operations include an NC machining operation on a single machine tool and an operation to assemble several components into a structure.

ENG00025 D


2-1

Chapter 2

Basic Concepts

Operation activities A breakdown of manufacturing process operations into activities, each with an associated start time and duration. The total time of an operation is calculated from the start time and duration of each activity. Workstation A unique location within the factory to which you can assign manufacturing operations, for example, a paint spraying booth. Plant A hierarchical structure of work areas in which operations and processes are executed. Work area Any element in the plant structure such as a factory, line, section, work cell, or station. Typically, a work area is assigned to one process operation. Product structure The denition of the product as it is designed. It describes a hierarchical structure of assemblies and component parts (as dened in the bill of materials or BOM), and the geometric relationship between them. Operation setup The model of an operation-specic conguration of an environment in which processes and operations are executed. It describes how consumed items, resources, and a standard work area are utilized to perform an operation. Consumed items Components in the product denition that are consumed by a manufacturing operation. Consumed material Items that are consumed by a manufacturing operation but are not part of the product denition, for example, glue or paint. Raw material The initial in-process model before any manufacturing operation is performed. In-process model The state of the product at some stage in the manufacturing process after an operation is executed. The raw material is the initial in-process model for the rst process operation in the manufacturing process. Any subsequent in-process model is created by applying a work instruction to the in-process model. Resource An item of equipment that performs an operation. A single resource can be used in several operations and processes.

2-2


ENG00025 D

Basic Concepts

Work instructions Documents that describe how work should be performed. A work instruction may be: Human readable instructions. They document the procedure by which the operator should perform an activity. Instructions may be printable or accessed from a Web page. Machine instructions. Program les that include code for programming numerically controlled machines, robots, or other equipment.

Teamcenter Manufacturing allows you to dene templates from which you can create work instructions. Manufacturing feature A set of entities and parameters that dene generic manufacturing data. For example, a weld point and its normal comprise a feature that describes where two points may be welded together. All such features should be associated with a process. Figure 2-1 shows a simplied representation of a product and the process to manufacture it. The product contains a component called Part I and the process for manufacturing this component is currently revised to Rev B. The manufacturing process comprises ve operations, and operation Op 20 has two tools and a xture assigned to it. These tools and the xture are stored in a Resource Manager library (see Resource Manager in chapter 3, Product Architecture, allowing you to reuse them in other operations. The plant where the manufacturing process takes place is also managed in Teamcenter Manufacturing, so that operation Op 20 is assigned to Cell B and operation Op 30 is performed by Lathe 2 in the same cell.

ENG00025 D


2-3

Chapter 2

Basic Concepts

Design (606) Process Sequence

Technical Dep.

NC Programmer

Mfg. Preparation

Shop Floor (95)

NC 1 for Plant A Product Release Create Mfg. Plan NC 2 for Supplier Release Plan Transfer MRP

ProductProduct

ProcessProcess

PlantLayout

+ Rev A

Rev A

Building A

- Rev B

Rev B

Building B

+ Part A

Op 10: Move part to machine

+ Section A

- Assy B

Op 20: Machining milling

- 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

- Cell B

Op 30: Machining turning

Lathe 1

Op 40: Move part to inspection

Mill 1

Op 40: Ship part to assembly a.

Lathe 2

Mill/Turn

Figure 2-1. Example of Fabrication Process

2-4


ENG00025 D

Basic Concepts

Process StructureTeamcenter Manufacturing provides a view of the manufacturing process that may be structured differently from the product structure. It allows you to link dened processes to the product and provide constraints on the order of process execution. The design and manufacturing representations of a product structure may be congured differently. The example in gure 2-2 shows the design representation of part of a car on the left side of the screen, while the manufacturing representation appears on the right side. The manufacturing view is divided by areas of the car (front, rear, middle and interior), while the design view is structured functionally. However, the identity of each component remains the same in each view. 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; in the manufacturing representation, it appears in the front section of the car, but the absolute occurrence identity remains 29.

Figure 2-2. Design and Manufacturing Representations of the Same Product

ENG00025 D


2-5

Chapter 2

Basic Concepts

However, each representation may contain information that is specic to design or manufacturing, and does not appear in the other representation. The example shown in gure 2-3 contains part of a car, in which the doors in the design representation are closed, but in the manufacturing representation are open. Different information is stored against the same components, although the components and their absolute identities are unchanged.

Figure 2-3. Storing Different Information on the Same Components

2-6


ENG00025 D

Basic Concepts

The following example shows the process for manufacturing a crankshaft. The manufacturing process comprises assembly and manufacturing steps, which must be executed in the correct sequence. The hierarchy of the processes and operations is as follows: Crankshaft Assy Rod and Piston - a subprocess to capture all activities of manufacturing the rod and piston. Assembly - assembly process operation to assemble the rod and piston. Rod - a subprocess to capture the manufacturing process of the rod. Raw material - a process operation to cut the raw material. NC machining rough - an NC machining process for rough cut. Heat treatment - the rough part goes through heat treatment. NC machining nish - the part is machined to its nal dimensions. Inspection - the part is inspected. Painting - the part is painted. End caps - a subprocess to manufacture the end caps. Piston - a subprocess to manufacture the piston. Crankshaft - a subprocess to manufacture the crankshaft. Crankshaft assembly Cylinder 1 - a subprocess to manufacture cylinder 1. Assembly level 1 - a subprocess to manufacture assembly level 1. End 1 [1] - the manufacturing process of end 1. Raw material - cutting the initial raw material. Machining - machining the part to its nal shape. Inspection - inspecting the part. Painting End 1 [2] - the alternate process to manufacturing End 1. End 2 - the manufacturing process of End 2. Assembly Operation - an assembly process to assemble the four pistons to the crankshaft.

Processes may vary according to the location of their execution, availability of resources, and time. Processes may also be revised independently of the product, in response to feedback from the shop oor personnel when executing the process.

ENG00025 D


2-7

Chapter 2

Basic Concepts

Conguring Processes With RulesA manufacturing process is designed for a specic product, and the process denition is tightly integrated with the product denition. Although the manufacturing process has conguration rules that are independent of the product conguration rules, the conguration rules of the product may automatically congure the associated manufacturing processes. For example, the product structure for a vehicle may include options for a CD or tape player. The manufacturing process for the dashboard mounting includes the following steps: 1. Make the molding. 2. Make the instrument panel. 3. Assemble the molding and instrument panel together. 4. Buy or make the tape player. 5. Buy or make the CD. 6. Assemble the tape player into the vehicle. 7. Assemble the CD player into the vehicle. When the tape player is selected, processes 1, 2, 3, 4, and 6 can be congured automatically in the process denition. When the CD player is selected, processes 1, 2, 3, 5, and 7 can be congured. You can also use the product revision rules to control the process structure. For example, the product includes occurrence A, which has two revisions, Working and Released. Each revision has a different manufacturing process. If the revision rule for the product congures Working revisions, you can use the rule to automatically congure the appropriate manufacturing process for building the working revision. You dene and apply revision rules for the product in Product Structure Editor, as described in Product Structure Editor Help. You can congure processes to accommodate variations in product structure in several ways: Variant rules You can dene options at the top level, then dene rules for each process derived from those options. For example, you can specify different process for the manufacture of item End 1 according to the process capabilities of the location. Revision rules You can load appropriate revisions of processes by applying predened revision rules.

2-8


ENG00025 D

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. You can also dene a range of unit or product serial numbers against which the process is effective.

Alternates You can dene alternate processes and select a preferred alternate.

Absolute OccurrencesAbsolute occurrences allow you to manage data that is unique to a specic application of an item in a process or product structure. Technically, an absolute occurrence represents a specic BOM line in the context of the top line item. For example, you manufacture a vehicle that is designed with four identical wheel and tire subassemblies. However, the front tires must be inated to 33 PSI, while the rear tires must be inated to 30 PSI. To accommodate this difference, you can create absolute occurrences of these subassemblies in the manufacturing environment with the required pressure set on each absolute occurrence. By default, creation of absolute occurrences is not enabled and the user must select absolute occurrence editing mode to permit this. Any changes affect only the current context, that is, the structure currently displayed. You can edit BOM line property values in context to create an absolute occurrence. You can also attach forms and datasets to an absolute occurrence, for example, a specication describing the reason for the tire pressure change.

Using CompositionsA composition is a special kind of structure context that allows components to be added from one or more structure contexts, each of which may contain a different product structure. A composition typically models a scenario or manufacturing process. For example, you can place a product view of an assembly and the corresponding process view in a composition for review and approval purposes. A composition may contain any of the following: An instance of the representation of any top-level item. In this case, the composition includes the complete representation. Instances of occurrences from other representations. A new instance is created and associated with an occurrence in the source representation. Instances of occurrence groups. An instance of the representation of the top-level item is created and ltered to show only the occurrences that are members of the occurrence group (with its subgroups and members).

ENG00025 D


2-9

Chapter 2

Basic Concepts

When you create a composition, you can manage and edit the occurrence groups in it in the same way as any other BOM line, including: Attaching data to occurrence groups in the context of the top line composition or any other context. This action creates a persistent absolute occurrence and the occurrence path representing the line in the composition. Attaching a 3D markup to them in the viewer. Changing their position in any context. If you change the position of a member of the group, the in-context edit must be set to the appropriate context. If no editing context is dened, the relative position is changed. Dening item elements (GDEs) and connections as part of the occurrence group. Creating connection interfaces on the members of the occurrence group. Comparing occurrence groups and their members. Creating and retrieving 2D product views (snapshots) in compositions containing instances of occurrence groups. Creating, editing, and manipulating graphics. Using any member of an occurrence group as the top level context for creating and editing absolute occurrences. Conguring members of an occurrence group to match the conguration of the source view. If a member does not exist in the source, it is grayed out in the composition.

If additions, removals or changes are made to the source BOM line, the occurrence line in the composition is updated accordingly. If an occurrence is a member of several occurrence groups in a single hierarchy, it is treated as a single occurrence for all purposes.

2-10


ENG00025 D

Basic Concepts

Associating Data in the Context of a CompositionWhen you associate absolute occurrence data to a member of an occurrence group in a composition, 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, the selected line itself is the context of the association. If the selected line is the instance of the of the occurrence group that brought this member into the composition, the root item of the source BOM of the group is the context of the association. Consequently, if multiple instances of the association are referenced in the composition, the same data is attached to the same member in every instance of the occurrence group. 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. A subgroup cannot be a context if it does not exist in the hierarchy of the source 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, the selected line is the context of the association. If no line is selected as the context, the actual parent of this member in the source BOM is the context of association.

The BOM line you select as the context must be a parent or ancestor of that member on the composition.

Conguring Referenced Structures in a CompositionYou can congure members of a referenced structure in a composition from the conguration of the source BOM. A referenced structure may be a subassembly, single component, or occurrence group. This may be done in one of the following ways: If a conguration context is stored on the BOM line of the referenced structure (by association with its occurrence or absolute occurrence), the referenced structure is congured by this conguration context. In general, any conguration context associated with a higher level overrides one attached at a lower level. If there is no stored conguration context, but the referenced structure is open and active in the source BOM, the reference structure takes the same conguration as the one in the source BOM. If there is no stored conguration context and the source BOM is not open, the referenced structure does not appear in the composition. The nal conguration of the referenced structure and its components also depends on the conguration of the composition BOM. A subassembly or component is congured in a composition if it is successfully congured in both the composition BOM and the source BOM.

ENG00025 D


2-11

Chapter 2

Basic Concepts

Process TemplatesIn many manufacturing environments, process planners design standard processes that are reused several times for different products. For example, the basic structure of the manufacturing process for a car is similar for a basic model or a premium model. You can save such manufacturing processes as templates in a library, then use the templates as the basis of new manufacturing processes for similar products. The template may include conguration rules that map the product data to process operations, and may include references to standard resources. When you create a new process operation, you can browse the available templates and select one to create the process operation. After it is created, you can attach the geometry of the part to be processed. Similarly, you can create assembly setup templates containing assembly information for a typical assembly setup. When you initialize a setup from a template, Teamcenter Manufacturing loads the related method, equipment, features, and manufacturing operations.

Access Control and WorkowManufacturing processes and operations are represented as items, allowing the Teamcenter Engineering administrator to dene appropriate access control privileges to the manufacturing processes. For example: The manufacturing engineer or process planner should have full permissions to access and modify process data. Users in this group can change process operation sequences, and dene the congurations of processes. Shop oor (assembly) personnel have read-only access to process data. Users in this group can view process data such as work instructions, but not make changes. Access may be further rened by subgroup. For example, an NC machinist may only have access to NC machining process operations.

You dene access permissions in access control lists (ACLs) with the Teamcenter Engineering Access Manager application.

2-12


ENG00025 D

Basic Concepts

Process OperationsA process operation describes one step in the manufacturing process of a product, and is executed at one work area. Each manufacturing process includes many types of process operations, 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, for example, an NC program, document le, or tool list. The manufacturing engineer produces the work instructions as part of the process operation design activity. Work instructions can be generated by a software application that is integrated with Teamcenter Manufacturing, for example, you can generate NC programs in NX. The manufacturing engineer may provide tooling instructions and setup procedures with the NC programs. All this information is collectively managed as part of the NC machining process operation. Similarly, when the manufacturing engineer designs an assembly process operation, the work instructions may be in the form of a robot program. 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.

ENG00025 D


2-13

Chapter 2

Basic Concepts

Process Operation DataEach 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. Work instruction data This information is created by the designer of the process operation and contains all the information necessary to complete the work. It may include tooling information, setup information, and the actions necessary to execute the operation. If you do not explicitly dene the work area, it may be specied in the work instructions. Output data Output data is generated by applying the work instructions to the input data. The result is a modied in-process model and any instructions necessary for the next steps. Analysis data Analysis data is derived from the work instructions and may include cost, time and a manufacturing features list. You can perform analysis for one process operation or many process operations. The process designer may also set analysis data prior to completing the design to estimate time and cost from the available high-level information. Product You can associate one or more items in the product structure with each 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. Work area You can associate each process operation with one work area. If you do not explicitly assign it to a work area, the requirements may be included in the work instructions and the assignment may be made on the shop oor when the process operation is executed. For example, the process may be performed on a three axis machine, but a specic machine may not be preassigned; shop oor personnel assign a machine according to their availability when the process operation is executed. Equipment The process operation references all equipment required, both the standard equipment of the work area and any additional equipment needed for the specic process operation.

2-14


ENG00025 D

Basic Concepts

Dening an NC Machining Process OperationWhen you design an NC machining process operation, you create an NC program, which are work instructions utilized by the NC machine to machine manufacturing features. You may also generate setup instructions and a tool list for the machine operator. The generic items associated with an NC process operation include: Machine tools An NC machine that executes the NC program. It must be included in the equipment denitions. Tools The cutting tools used in manufacturing operations to cut features. Machining manufacturing features The geometry denitions of the manufacturing operations, such as pocket, hole, slots, ream, and tap. Machining method The types of cuts that are performed during manufacturing operations, such as mill, lathe, mill-rough, mill-nish, center-frill, reaming, and tapping. Program A collection of manufacturing operations in the order of execution. NC manufacturing operation A description of how one tool moves in relation to a features geometry. A tool path can be automatically generated from this description; the tool path, in turn, generates the NC program.

ENG00025 D


2-15

Chapter 2

Basic Concepts

Assembly and Weld Process OperationAn assembly process operation provides the work instructions for assembling parts in a work area that is designated for assembly operations. The work instructions may contain robot programs if the assembly process operation uses a robot to perform some assembly actions. The generic items associated with an assembly and weld process operation include: Robots and weld guns This equipment performs assembly instructions. Assembly components Create assembly manufacturing operations to move these items to the correct positions. Assembly method You can dene general assembly methods such as weld, glue, and move. Assembly sequence Describes the order in which assembly manufacturing operations are executed. Assembly manufacturing operation Describes how a component moves with one tool or operator during the assembly sequence.

2-16


ENG00025 D

Basic Concepts

Managing ResourcesProcess operations require resources to execute them. The availability of resources affects the denition of manufacturing processes. For example, in an automated assembly plant, robots may weld assemblies. In plants where weld robots are unavailable, the same manufacturing process may be followed, but a different resource (a manual welder) executes the operation. A process operation can directly identify that a specic work area in the resource structure is needed to execute it. In the case of a weld process operation, it may specify a weld workstation on the shop oor and a specic weld gun as the resources required for its execution. 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, the process denition inuences the quality and layout of the resources. Process operations may only specify a requirement of the required resources. For example, any arc welding robot on the shop oor can execute an arc welding process. In this case, the weld process operation does not directly reference specic instances of the weld work area and weld guns. Manufacturing execution systems (MESs) marshal the process denitions and the product order size, and assign jobs to specic resources according to their availability. The process planner may receive feedback from the MES system and modify the process denition to improve performance. For example, the planner might decide to buy material from external suppliers instead of manufacturing in-house to avoid resource constraints. Users of resources fall into three general categories: Machine tools An NC machine that executes the NC program. It must be included in the equipment denitions. Resource authors Users with this role dene new resource components, assemble components into standard tool assemblies, and dene the attributes and properties of the components and assemblies. Resource consumers Users with this role are manufacturing engineers who dene process plans that utilize resources already dened by the authors. They may also be plant workers who use the process plans and update the resource inventory.

ENG00025 D


2-17

Chapter 2

Basic Concepts

Releasing a Manufacturing ProcessAfter you complete a manufacturing process, you may want to make it available for review and approval before manufacturing commences. Teamcenter Manufacturing does not provide review, approval and release processes, but you can develop suitable processes with the Workow application, as described in Workow Help. You can also provide intermediate releases of work-in-progress process designs for others to view. This intermediate snapshot of data is sometimes referred to as the preliminary data indicator (PDI). Consumers of a PDI can then work with the data, knowing that it will not change until the next PDI is released. The process and its operations may reference occurrences of product data and plant data. The PDI may not be valid if this related data changes. Consequently, if you create a baseline of the process in this way, you must also baseline any related structures at the same time. Teamcenter Manufacturing allows you to baseline a process structure (or a composition) and create a PDI in a single operation.

Incremental ChangesYou can control changes to the manufacturing process, structure, or operations by revising the affected items. As many changes may be small and not related to each other, Teamcenter Manufacturing allows you to create incremental changes to add components to and remove them from the structure. Each incremental change consequently comprises several individual and possibly unrelated revisions to a component, occurrence, or attachment in the structure. An incremental change order (ICO) groups several individual changes that can be released simultaneously to a baseline of the process or product. You can dene an effectivity for an incremental change, allowing (for example) all changes related to the production of a new model to be implemented simultaneously. You normally assign an effectivity expressed as a date range or sequence of serial numbers to the change order, ensuring that all grouped additions and removals happen at the same time. An incremental change may have revisions, and you can congure the various components, occurrences and attachments to a specic revision by applying appropriate revision rules. You can also create intents to an incremental change. An intent represents an event or alternate solution that is not bound to a date or unit number effectivity. For example, you may dene an intent as a new prototype and group all changes required to build the prototype accordingly. You can attach relevant data to an incremental change, including a form, dataset, or folder. For example, you may want to attach the individual change requests that are satised by the incremental change. You can also use incremental change to view the denition of a structure effective of a certain date or unit number. For example, the structure of part 100 may have been originally designed with two occurrences, one of part 200 and the other of part 300. A design change is made that cancels the occurrence of part 300 and adds an occurrence of part 400 in its place. These removals and additions remain linked to the incremental change order that carries the effectivity of the change. If you view the structure of part 100 for an effective date after the change occurred, you see only parts 200 and 400.

2-18


ENG00025 D

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. You can then apply further incremental changes to the baseline.

Tracking ChangesWhen data changes in the context of an incremental change, these changes are recorded against the specic incremental change. These individual change elements, such as the addition of an occurrence or removal of an attachment, are not visible to the user but may be accessed by advanced users. Changes that are tracked and recorded against an incremental change are: Addition of activities to an operation. Removal of activities from an operation. Addition and removal of attachments to an operation, including forms and datasets. Creation of data such as forms and datasets. Changes to predecessor occurrences of processes or operations.

Changes are normally tracked dynamically, as the user makes edits with an active incremental change. Changes may also be tracked retrospectively, if the changes are already made but were not originally tracked against an incremental change.

Conguring ChangesYou can release a revision of an incremental change with an appropriate workow. You dene a release status (typically Released) that applies the dened effectivity. You can also release a revision of the incremental change with a Preliminary status, which allows you to still modify the incremental change. If Released status is applied, you can no longer modify the incremental change. The user can choose to view all congurations associated with an incremental change or to hide those components and attachments that are not congured by the current revision rule. The conguration 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 congured, the change is applied. If more than one change affects an occurrence according to effectivity, a removal is congured in preference to an addition.

ENG00025 D


2-19

Chapter 2

Basic Concepts

Conguring With IntentsYou can dene intents to represent milestones or events that cannot be dened by a date or unit number effectivity. For example, you may congure several alternative processes for evaluation and discussion and identify them as Alternate Process 1, Alternate Process 2, and so on. You can optionally apply one or more intents to an incremental change, as follows: If you apply several intents to an incremental change, the incremental change is valid for all of those intents. An intent is applied to all revisions of the incremental change. Intents may optionally be congured by a revision rule. Any incremental change that matches an intent set in the revision rule is selected. You can congure an incremental change with both intents and effectivity, when appropriate.

Controlling AccessTo create incremental changes against a structure, a user must have access to the revision of the incremental change. The Teamcenter Engineering administrator controls this access with the Access Manager.

2-20


ENG00025 D

Chapter

3

Product Architecture

Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2 Manufacturing Structure Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3 Part Manufacturing Planner . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4 Multiple View Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5 Factory Structure Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5 Resource Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6 Report Generator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7 Collaboration Context . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7 Classication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8 Product Structure Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8 Customizing Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9 Technical Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9

ENG00025 D


Chapter

3


Teamcenter Manufacturing includes several applications through which users dene 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 Classication. How to customize the operation of Teamcenter Manufacturing. The technical documentation provided with Teamcenter Manufacturing.

ENG00025 D


3-1

Chapter 3


PrerequisitesTeamcenter Manufacturing provides an overlay that enhances the functionality of Teamcenter Engineering. Before installing and using Teamcenter Manufacturing, you must install and congure 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 congure 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 Programmers Guide.

3-2


ENG00025 D


Manufacturing Structure EditorManufacturing Structure Editor allows you to design a plan that details how to manufacture a product that is an assembly. The manufacturing process plan includes a top-level structure of the process needed to manufacture the product, as well as a detailed design of the individual processes and activities included in the plan. As you build the process structure, you can assign resources to the various processes, operations, and activities. You can also identify the specic locations within the plant where each operation and activity is performed. The main activities that you can accomplish with this application are: Open a product structure that was created in Teamcenter Engineering. When the product is open, you can assign it as the target of a manufacturing process. Create a process structure for the target product. You can also edit an existing process structure. Create new operations as part of the process structure, or edit an existing operation. Create or edit a setup structure that contains the tooling, resources, parts, and workpieces, and their position in the process. Assign a classied resource to an operation. Create or edit the plant structure which describes the hierarchy of work areas or locations in the factory where manufacturing operations are performed. Create or edit manufacturing views of the product. Import manufacturing features such as weld points from NX. Congure process structures with incremental changes, variant rules and occurrences. Analyze the manufacturing process to ensure all components are consumed and are not consumed more than once. Create templates for processes, operations, and activities. Create a preliminary data indicator (PDI) of the process structure. Create an intermediate data capture. Assign data to projects.

For detailed information about how to use Manufacturing Structure Editor, see Manufacturing Structure Editor Help.

ENG00025 D


3-3

Chapter 3


Part Manufacturing PlannerPart Manufacturing Planner allows you to design a plan that details how to manufacture a piece part product, such as a piston or engine fan blade. You can plan the production process from raw material to end product, including cutting, drilling, milling, turning, and quality checking operations. In this environment, there is typically no production line, but several resources such as machine tools, xtures, cutting tools and gages are necessary. The manufacturing process plan includes a top-level structure of the process needed to manufacture the product, as well as a detailed design of the individual processes and activities to be included in the plan. As you build the process structure, you can assign resources to the various processes, operations, and activities. You can also identify the specic locations within the plant where each operation and activity is performed. The main activities that you can accomplish with this application are: Open a product structure that was created in Teamcenter Engineering. When the product is open, you can assign it as the target of a manufacturing process. Create a process structure for the target product. You can also edit an existing process structure. Create new operations as part of the process structure, or edit an existing operation. Create or edit a setup structure that contains the tooling, resources, parts, and workpieces, and their position in the process. Assign one or more classied resources to an operation. Create or edit the plant structure which describes the hierarchy of work areas or locations in the factory where manufacturing operations are performed. Import manufacturing features such as weld points from NX through the NX CAM Integration. Congure process structures with incremental changes, variant rules, and occurrences. Analyze the manufacturing process to ensure all components are consumed and are not consumed more than once. Create templates for processes, operations, and activities. Attach work instructions to the process or operations. Create an intermediate data capture. Assign data to projects.

For detailed information about how to use Part Manufacturing Planner, see Part Manufacturing Planner Help.

3-4


ENG00025 D


Multiple View EditorMultiple View Editor allows you to create associative, alternative views of the product structure. You can: Create manufacturing-specic views of the product. Rearrange the product structure hierarchy for manufacturing purposes without losing the association between the product and the process structure. View and edit the sequence of operations performed on the product on the shop oor. View and edit a representation of the ow of materials between operations. Assign components from the product view as consumed items and workpieces. Update the manufacturing view automatically when the product structure is updated, including changes to transformations, variant options, and component additions and deletions. Congure the product manually or with occurrences, options, and revisions, then visualize the results. Create an intermediate data capture.

For detailed information about how to use Multiple View Editor, see Multiple View Editor Help.

Factory Structure EditorFactory Structure Editor allows you to: Create, modify, import, and export a factory structure. Typically, you create the detailed design of the factory structure in FactoryCAD, then import it into Factory Structure Editor. Visualize your plant structure layout, and organize the areas where the product is manufactured. Create a preliminary data indicator (PDI) of the factory structure. Create an intermediate data capture.

For detailed information about how to use the Factory Structure Editor, see Factory Structure Editor Help.

ENG00025 D


3-5

Chapter 3


Resource ManagerResource Manager allows you to store and retrieve resources such as tools, xtures, machines, and process templates. Resource data is held in a database that is accessible to all users. Resource Manager stores this data in combination with classication information, and it is organized into a hierarchy that is specic to your company. You can: Create and modify resource components and assemblies. Search for classied resources by characteristics. Classify resources into hierarchical schemes with the Classication application described later in this chapter. Send resources to other Teamcenter Manufacturing applications to include in processes, operations, and activities. View the resource in the assembly viewer if a visualization (JT) le is attached to it. Create resource reports. Browse to identify where resources are used in the structure. Create and view attachments to resources such as work instructions in Microsoft Word format or alternate geometric representations, for example, AutoCAD les. Generate setup sheets.

Figure 3-1 shows how a manufacturing resource is stored in Resource Manager. Generally, the administrator creates and maintains each resource, its properties and any attachments. You can congure the system such that other users can only view and consume the resource. In the example, note that all properties elds are read-only.

Figure 3-1. Typical Resource in Resource Manager For detailed information about how to use Resource Manager, see the Resource Manager Help.

3-6


ENG00025 D


Report GeneratorReport Generator allows you to create reports about the process plan and related operations, activities, product structure, and plant structure. This information can be printed or viewed, making it available to users who do not have access to Manufacturing Structure Editor. Certain default reports are provided, and you can create your own customized reports. For detailed information about how to use the Report Generator, see Report Generator Help.

Collaboration ContextThe 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 modied by either application and any changes are available in both environments. You can also create a preliminary data indicator (PDI) of any structure in a collaboration context. For detailed information about how to use Collaboration Context, see Collaboration Context Help. A collaboration context is a collection of structure contexts that are used for a specic task, for example, part of a process. A structure context contains one or more structures of the same type or different types. The structure context may include top-level items, item revisions, or occurrence groups. The conguration of a structure context is determined by the effective conguration context, which may include revision rules, a selected option set, and closure rules that dene objects of interest. Collaboration contexts are used when it is appropriate to create subsets of data in support of a particular business process, for example, when collaborating with suppliers or exchanging data with a third-party application. Create structure contexts in a collaboration context when it is necessary to store conguration rules with the structure data. Use compositions to bring together positioned elements from different structures. The Resource Browser application allows you to view and manipulate resource data that is shared in a collaboration context from the external application. For detailed information about Resource Browser, see Resource Browser Help.

ENG00025 D


3-7

Chapter 3


ClassicationClassication allows you to classify all the resources associated with the manufacturing process. You can: Develop a classication hierarchy for your company with the Classication Administration application. Assign classied resources to the manufacturing process with Resource Manager, as described previously. Search the classication hierarchy for classied resources. Associate a part family template to each class (a part family, in this context, may contain a particular type of tool). You can associate a graphical representation of the item with each member of a part family. Use change management to control revisions to classied items.

For detailed information about Classication, see Classication Help and Classication Administration Help.

Product Structure EditorProduct Structure Editor allows you to manage design product structures, and can be congured to show (for example) the product that is in production, the product conguration effective for a particular date or serial number range, or a specic variant. A product structure managed by Product Structure Editor is the starting point for the design of your manufacturing process. When you design or revise the manufacturing process, you can use Product Structure Editor to view or edit information about the original product design. For detailed information about Product Structure Editor, see Product Structure Editor Help.

3-8


ENG00025 D


Customizing FunctionalityTeamcenter Manufacturing publishes APIs that allow you to customize the operation of your system or perform certain functions programmatically. For descriptions of these APIs, see the Integration Toolkit Function Reference. The published APIs allow you to customize or manipulate the following main areas of functionality: Adding and creating occurrence groups. BOM line predecessors and incremental changes. Showing and hiding incremental changes. Adding, changing, and removing occurrences. Showing, setting, and hiding occurrence type lters. Adding and removing closure rules. Manipulating collaboration contexts, as follows: Creating and setting a collaboration context. Creating, adding to, retrieving, and removing structure contexts. Setting and retrieving conguration contexts. Setting, changing, and retrieving closure rules, revision rules, and variant rules.

Creating, changing, and querying for activities. Creating occurrence paths. Creating operations. Creating and revising processes. Creating and revising work areas. PLM XML import and export functionality.

Technical DocumentationTeamcenter Manufacturing is supported by technical documentation that is available when you click the Help button in any of the product applications. You can also press the F1 key to show online help for the active applications, or press F2 to show the launch page for all online help modules. Certain Teamcenter Manufacturing technical documents are also provided in Adobe PDF format on the documentation CD provided with the release software.

ENG00025 D


3-9

Chapter

4

Principles

Revisions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1 Occurrences in the Manufacturing Environment . . Examples of Occurrences in Manufacturing . . . Associating Data With Occurrences . . . . . . . . Editing the Components of a Process Structure Editing the Process Structure View . . . . . . . . Occurrence Paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2 4-2 4-4 4-4 4-5 4-5

Searching for Appearances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6 Variants and Variant Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7 Precise and Imprecise Structures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8 Feature Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8

ENG00025 D


Chapter

4

Principles

This chapter describes some of the basic principles that Teamcenter Manufacturing applies to the design and management of manufacturing processes.

This chapter describes the following topics: Revising processes and operations. Using occurrences. Variants and variant rules. Precise and imprecise structures. Managing features.

RevisionsEach manufacturing process and operation is represented in the system by an item. The item contains the information about the process or operation that does not change; for example, a single item may represent the operation in which the crankshaft is assembled onto the engine. Each item has one or more revisions that contain information that changes. For example, the item revision of an operation may specify a particular operation that requires a specic welding machine; if you change the operation to use a different machine, you revise the operation and create a new item revision. Revisions have a particular effectivity, expressed as a date range or sequence of product serial numbers. When you revise an item, you can specify that the new process or operation takes effect on a particular date or product number. You can dene revision rules that determine the revision of the item that is loaded in any particular situation.

ENG00025 D


4-1

Chapter 4

Principles

Occurrences in the Manufacturing EnvironmentAn occurrence (relative occurrence) is a persistent object that represents the usage of an item in the context of a top-level structure. It represents the shape, position, or other attribute of the item at a specic point in the manufacturing process. For example, the occurrence of the assembly process for the left front wheel of a vehicle differs from the occurrence of the right front wheel, even though the actual wheels are identical. You can combine multiple occurrences into occurrence groups in Teamcenter Manufacturing to model assembly and manufacturing requirements. Occurrence groups may contain occurrences of parts and subassemblies that are not necessarily grouped together in the product design. Alternatively, an occurrence group may collect all occurrences in the product that are within a given proximity of a part that you are designing. An absolute occurrence is a specic instance of an item, in the context of its immediate parent. It stores occurrence data such as usage specic names and descriptions or positional overrides. Absolute occurrence data overrides relative occurrence data. For example, the vehicle may have two occurrences of a left wheel, in the context of the suspension assembly. Users can name one of those occurrences as left rear wheel, in the context of the complete vehicle. Assigning a name to an absolute occurrence of an item does not override or change the attributes of the general item.

Examples of Occurrences in ManufacturingThe 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. For example, a shock absorber in a car may not be compressed when in inventory. However, when the part is assembled into a car, it absorbs the weight of the car and becomes compressed. As a result, the geometric denition of the part changes in the context of the car. To dene this condition for the manufacturing process, you must associate a separate NX part and JT image with the occurrence of the compressed part in the car. Factory conguration A factory structure contains many standard components such as robots, conveyors, and welding guns. Each such standard component may have a structure of its own. When positioned in the factory, the location of a component may change based on its relationship to other factory elements. For example, you might need to change the installed position of a robot in one area of the factory compared to another. To allow for these differences, 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. You can associated different cost data with each occurrence of the robot.

4-2


ENG00025 D

Principles

Manufacturing setup A setup is a composition that represents the environment in which an operation or study is performed. The setup contains occurrences groups of various structures in the product and the factory. In the manufacturing setup, one of the occurrence groups represents the in-process assembly as it arrives at the station. If, for example, this in-process assembly includes the doors of a car, the doors may be in the closed position in the design product structure. However, to assemble the seats into the car, the doors must be open. To allow for this requirement, 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 denition.

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, including the steering wheel and pedals. The positions of these parts can be changed only in the context of the study without affecting the original position in the product denition. For example, the steering wheel may be rotated along the steering bar or a pedal pressed to the down position. In this case, the worker is positioned relative to the car in the context of the setup, and you can change the positions of parts of the car to model different assembly scenarios.

Integration with Tecnomatix Process Planning Software You may use Teamcenter Manufacturing to manage and maintain process data, but author your actual processes in the Tecnomatix process planning software. Information about the process structure is required during the planning phase of the process plan. During this planning phase, factory components may change their positions and associated data. Tecnomatix uses a data model in which each component in the factory is unique. When you import data from Tecnomatix into Teamcenter Manufacturing, it is associated with the corresponding occurrences in Teamcenter Manufacturing. A robot may change its position as the result of a change to the design of a station layout. However, this change should not affect other instances (occurrences) of the robot.

ENG00025 D


4-3

Chapter 4

Principles

Associating Data With OccurrencesYou can associate data with occurrences, then later override the data at a different level of the structure. There are many types of data that you might want to associate with an occurrence, including cost data, transformations, visualization les, and variant conditions. You may dene data at several levels in the structure, including: Item revision data All data associated with the item revision. You can attach the data with effectivity. Occurrence data The data associated with a relative occurrence in the structure. It describes the usage of an item revision in the context of its immediate parent. The data is always attached with a particular effectivity. Occurrence data in the context of a structure view You can relate data to an occurrence in the context of a specic occurrence group. This conguration can support components with multiple positions in the structure or in exploded views. Setup data A setup is an assembly structure that contains occurrences in an occurrence group. The data in the setup overrides the data associated with the reference object, which may be an item revision or an occurrence. An occurrence in the setup may include a reference from an operation or process to an occurrence group, occurrences, or items. The data on the setup occurrence overrides the data on the object it references. You can attach data at any level, but you can also override lower level data at a higher level. For example, data attached to an occurrence overrides data attached to the item revision. At any level, you can attach a transformation, direct model data for visualization, a design model, names or IDs, and attachments such as a dataset or forms.

Editing the Components of a Process StructureStructure components are lines in the process structure that belong to the top level item in a specic window. These lines may have occurrences in the context of the top level. 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. Occurrences can have attributes such as transformations and notes. You can also attach data to occurrences by typed relationships. Item revision data Item revision data is associated with the congured item revision in the structure. It has object attributes and attachments.

4-4


ENG00025 D

Principles

Editing the Process Structure ViewA 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. You can also edit views with 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. This data overrides the data on the occurrence attached to that line. You can associate attachments with the relationship, in which the attachment to the occurrence is overridden or added. Adding components You can add components to an occurrence group. You edit the top-level structure associated with the occurrence group and add the new component to the end item. You must have the appropriate privilege to access the item. You cannot add components in a view dependent edit. Removing components You can remove components from the top level with an incremental change order in a view dependent edit or an appearan

Team Center Manufacturing User and Administrator Manual

Documents

Transcript of Team Center Manufacturing User and Administrator Manual