Teamcenter Getting Started with Teamcenter. Publication Number PLM00002 J - PDF Free Download (2022)

Transcription

1 Teamcenter 10.1 Getting Started with Teamcenter Publication Number PLM00002 J

2 Proprietary and restricted rights notice This software and related documentation are proprietary to Siemens Product Lifecycle Management Software Inc Siemens Product Lifecycle Management Software Inc. All Rights Reserved. Siemens and the Siemens logo are registered trademarks of Siemens AG. Teamcenter is a trademark or registered trademark of Siemens Product Lifecycle Management Software Inc. or its subsidiaries in the United States and in other countries. All other trademarks, registered trademarks, or service marks belong to their respective holders. 2 Getting Started with Teamcenter PLM00002 J

3 Contents Proprietary and restricted rights notice Overview of Teamcenter Overview of Teamcenter Before you begin Starting Teamcenter sessions Using preferences Using Teamcenter interfaces Teamcenter interfaces Using the rich client interface Managing your thin client interface Business Modeler IDE interface Teamcenter Client for Microsoft Office How Teamcenter supports product life cycle phases How Teamcenter supports product life cycle phases Systems engineering and requirements Managing design data and product structures Manufacturing process management Workflow and change management Document management basics Content management Managing contract data Vendor management Product visualization Classification and reuse CAE Data Management Repeatable Digital Validation Maintenance, repair, and overhaul Teamcenter solutions Dimensional Planning and Validation (DPV) Electronic Design Automation (EDA) Data sharing Common Teamcenter tasks Common Teamcenter tasks Viewing online help Working with data objects Working with folders Managing basic data Using 4th Generation Design Managing product structures Managing changes PLM00002 J Getting Started with Teamcenter 3

4 Contents Using workflow processes Importing and exporting data Running reports Using mail, , and instant messaging in Teamcenter Glossary A-1 Index Index-1 4 Getting Started with Teamcenter PLM00002 J

5 Chapter 1 Overview of Teamcenter Overview of Teamcenter Before you begin Starting Teamcenter sessions Logging on to Teamcenter Start a Teamcenter rich client session Logging on to the Teamcenter rich client Start a Teamcenter thin client session Teamcenter client user settings Using preferences PLM00002 J Getting Started with Teamcenter

6

7 Chapter 1 Overview of Teamcenter Overview of Teamcenter Teamcenter is a virtual gateway to your company s product information connecting all who need to collaborate with product and process knowledge. Teamcenter enables you to digitally manage your product and manufacturing data in the context of the product lifecycle. Using Teamcenter you can: Provide all users in your global organization access to data in real time. Manage product configuration. Control design changes and approvals. Provide information to downstream applications, such as enterprise resource planning (ERP) systems. Getting Started with Teamcenter introduces Teamcenter and the Teamcenter documentation set: Introduces the basic concepts of product lifecycle management and Teamcenter administration. Provides links to the detailed information related to the concepts described in the guide. Provides instructions for performing tasks that are common to many of the Teamcenter applications, such as printing information about your data, changing your user settings, and managing your desktop. This guide is for persons responsible for: Gathering, viewing, and reviewing data. Authoring data and completing work assignments. Creating, configuring, and managing complex product structures. Creating data and related manufacturing structures and processes. Administering Teamcenter. Teamcenter administrators should also review the Application Administration Guide and the System Administration Guide. PLM00002 J Getting Started with Teamcenter 1-1

8 Chapter 1 Overview of Teamcenter Before you begin Prerequisites Enable Teamcenter Configure Teamcenter Start Teamcenter Some of the applications and features described in this guide are not included with the standard Teamcenter product and must be licensed separately. For more information, contact your Siemens PLM Software representative. Teamcenter is installed using Teamcenter Environment Manager (TEM). For more information about installation considerations and installation procedures, see the installation guides for the operating system on which you run Teamcenter ( Installation on UNIX and Linux Servers Guide, Installation on Linux Clients Guide, Installation on Windows Servers Guide, or Installation on Windows Clients Guide). For information about installing particular options with TEM, see Teamcenter Environment Manager Help. Teamcenter is installed and initially configured using TEM. After Teamcenter is installed, you use configuration tools, such as the Business Modeler IDE to define business objects and rules that model your company s business processes. You use administrative tools such as the Organization application to model your company s organization in Teamcenter, Workflow Designer to define workflow processes to manage your data, and Access Manager to implement data security. You establish a Teamcenter session when you log on to Teamcenter. For more information, see Starting Teamcenter sessions. For information about hardware and software requirements, see the Siemens PLM Software Certification Database: Starting Teamcenter sessions When you log on to a Teamcenter client, you establish a Teamcenter session. After the session is established and Teamcenter is running, you open the application perspectives (rich client) or applications (thin client) used to perform your tasks. For more information about working in the rich client, see Rich client application perspectives. For more information about working in the thin client, see Thin client applications. Logging on to Teamcenter The initial Teamcenter logon window can vary, depending on the security configuration at your site. 1-2 Getting Started with Teamcenter PLM00002 J

9 Overview of Teamcenter Your administrator configures Teamcenter client communication system (TCCS) and Security Services to satisfy requirements in your installation. Supported capabilities include: The ability to log on to Teamcenter using Security Services in an applet-free mode. Support for logon authentication to Teamcenter using the Kerberos protocol. Support for zero sign-on for Windows systems using Kerberos. Support for logon authentication using soft certificate and smart card authentication. Smart card authentication is supported only on Windows systems. Kerberos is a network authentication protocol that allows nodes communicating over a nonsecure client-server network to verify identities in a secure manner. For additional information about setting up Kerberos authentication for Security Services, see Security Services Installation/Customization. For example, Kerberos authentication and the zero sign-on functionality is enabled during installation by clearing the Always prompt for user ID check box. In this case, a system user on a Windows host who is already logged on to the system through Kerberos can launch a Teamcenter client without being prompted to log on to Teamcenter. If your site uses proxy servers, multiple environments, or Security Services components such as single sign-on, you may be required to select an environment or respond to one or more additional authentication dialog boxes. When a site requires both a soft certificate and a smart card authentication to log on, you are initially prompted to select which certificate to use for authentication of a two-way Secure Sockets Layer (SSL) configured environment. In the rich client, when the soft certificate is selected the logon proceeds using the soft certificate, but if the smart card is not inserted in the reader the logon process may still prompt users to insert their smart card. Canceling this prompt causes it to display again, but canceling it a second time allows the logon to proceed successfully using the soft certificate. In the thin client, users may be prompted several times during single sign-on (SSO). o When both the SSO Login service configured for applet suppression and the Teamcenter Web tier are protected behind a two-way SSL server, the log on to the thin client may prompt the user for smart card credentials multiple times during logon. This is caused by the number of applets launched by the thin client; each applet requires an additional challenge. o When the SSO Login service is configured for applet mode (tcsso.login_service.enable_session_agent_applet is set to true) or the Teamcenter Web tier is not protected behind the two-way SSL security, the user may see two prompts for running in applet mode. PLM00002 J Getting Started with Teamcenter 1-3

10 Chapter 1 Overview of Teamcenter When you try to log on to an environment configured for smart card authentication when the smart card is not inserted, the logon fails. You may need to stop and restart Teamcenter client communication system (TCCS) to clear the error. For more information about configuring SSL and smart card authentication for Teamcenter, see the Security Services Installation/Customization guide. For more information about configuring SSL as part of TCCS configuration, see the appropriate client installation guide for Windows or UNIX/Linux. For additional information about administering the Teamcenter server proxy, see the System Administration Guide. For general information about Teamcenter security, see the Security Administration Guide. Start a Teamcenter rich client session Choose Start All Programs Teamcenter Teamcenter or double-click the Teamcenter icon on your desktop. Your Teamcenter client may be installed so the menu items include a version number, such as Teamcenter Tip If you do not have a Teamcenter shortcut icon: 1. Choose Start All Programs Teamcenter Teamcenter, and right-click Teamcenter. 2. Choose Send To Desktop (create shortcut). For information about command line options for rich client startup, see the Client Customization Programmer s Guide. Logging on to the Teamcenter rich client The rich client logon window has the following fields: User ID This is a required value. User accounts are created by administrators in the Organization application. You must provide a valid account ID to interact with Teamcenter. Password This is a required value. Passwords are created by administrators in the Organization application. Group This is an optional value. A group is an organizational collection of users who share data. A user account can belong to multiple groups and must be assigned to a default group. Groups are created by administrators in the Organization application. If you do not specify a group, the default group associated with the user account is used. 1-4 Getting Started with Teamcenter PLM00002 J

11 Overview of Teamcenter Role This is an optional value. Function-oriented cluster of users that models skills and/or responsibilities. The same roles are typically found in many groups. Roles are created by administrators in the Organization application. If you do not specify a role, the default role associated with the group is used. Server Specify the server to provide database access for your rich client session. Servers are configured during installation. For information about users, passwords, groups, and roles, see the Organization Guide. Depending on whether your site uses proxy servers, multiple environments, or Security Services components such as single sign-on, you may be required to select an environment or respond to one or more additional authentication dialog boxes. Start a Teamcenter thin client session 1. Open the Web browser and type the URL of the Web server in the Address box in the following format: machine_name is the network name of the system on which the Web server is running, port_number is the port on which it is configured to listen for requests, and application_name is the deployed application name (default is tc). For example: or Press Enter. The Teamcenter logon page is displayed in your browser. 3. Type your Teamcenter user name and password and click Login. Teamcenter appears in your browser. You are automatically logged on using your default group and role. Tip You can change your group or role by clicking the User Settings link in the navigation pane. Teamcenter client user settings The Teamcenter rich client and thin client let you modify user information for current and future sessions such as: Group Role PLM00002 J Getting Started with Teamcenter 1-5

12 Chapter 1 Overview of Teamcenter Project Revision Rule Default Group Location Code Tip You must have administrative privileges to change some settings. You can also click the user information link in the client window application header to access the User Settings dialog box. For information about changing user settings in the Teamcenter rich client, see the Rich Client Interface Guide. For information about changing user settings in the Teamcenter thin client, see the Thin Client Interface Guide. Using preferences Preferences are special environment variables stored in the Teamcenter database. Preference instances are used to control the behavior and display of Teamcenter applications. Teamcenter provides thousands of preferences that you can use to configure the product to your specific needs. Administrator and nonadministrator users can configure many aspects of a session, such as the checkout directory and how often Teamcenter checks for new system mail. Preferences can apply to the entire site, a specific user, a group, or a role. Preferences control the behavior of Teamcenter clients and servers. The rich client provides an Options dialog box that lets you interactively select to specify behaviors. The thin client also provides an Options dialog box that lets you set a more limited group of preferences. For more information about working with preferences and using options in the rich client, see the Rich Client Interface Guide. For more information about working with preference setting through options in the thin client, see the Thin Client Interface Guide. In the rich client, another set of preferences are provided by the WindowfiPreferences menu command. These client preferences, which are displayed and edited in the Preferences dialog box, are local to the user. These preferences are documented in the context of the applications to which they apply. 1-6 Getting Started with Teamcenter PLM00002 J

13 Chapter 2 Using Teamcenter interfaces Teamcenter interfaces Using the rich client interface Rich client interface Rich client perspectives and views Opening application perspectives in the rich client Rich client application perspectives Open a rich client perspective Switch between open perspectives Save, reset, or close a rich client perspective Working with the rich client navigation pane Configuring the display of applications Customizing the toolbar Configuring table data display in the rich client Managing your thin client interface Thin client interface Open an application in the thin client Thin client applications Working with the thin client navigation pane Business Modeler IDE interface Teamcenter Client for Microsoft Office PLM00002 J Getting Started with Teamcenter

14

15 Chapter 2 Using Teamcenter interfaces Teamcenter interfaces Teamcenter provides several interfaces, including a rich client interface, a Web-based thin client interface, a Business Modeler IDE, and Teamcenter Client for Microsoft Office. The rich client interface is used by authors, manufacturing authors, administrators, and other users to: Manage the design and configuration of product data. Create and maintain processes and process structures. Configure and maintain Teamcenter. Access data stored in the Teamcenter database. The thin client interface is used by consumers, manufacturing consumers, and reviewers to: View data, including product structure and variant information. Approve data attached to a workflow task. Visualize 2D drawings and 3D model. The thin client interface is ideal for suppliers, production staff, and other users who do not require extensive authoring or administrative access to Teamcenter. The Business Modeler IDE is used by administrators to customize the Teamcenter data model and configure basic functionality. Client for Office allows you to access Teamcenter directly through Microsoft Office Word, Excel, PowerPoint, and Outlook. Using the rich client interface The Teamcenter rich client, a platform-independent client implementation (Java application) for users who interact frequently with Teamcenter, runs on client hosts and serves as a gateway to your company s product information. You can integrate and run Teamcenter s product data management perspectives along with applications such as Microsoft Office, custom applications, Java plug-ins, or CAD/CAM/CAE applications, all from a common platform. The rich client accesses Teamcenter databases using a remote or local server. PLM00002 J Getting Started with Teamcenter 2-1

16 Chapter 2 Using Teamcenter interfaces The rich client provides a broad selection of application perspectives and views to manage your product information. You can use the rich client to: Create objects. Check in and check out items. Manage tasks. Rich client interface The rich client interface has a standard menu bar and toolbar with options that vary depending on the currently active application perspective. You can place the cursor over a rich client toolbar button to display a tooltip description. 1 Back and Forward buttons The Back and Forward buttons allow you to move between loaded Teamcenter applications. The small arrows next to the buttons let you select from the list of currently loaded applications. For more information about moving between loaded applications, see Switch between open perspectives. 2-2 Getting Started with Teamcenter PLM00002 J

17 Using Teamcenter interfaces 2 Application banner The application banner shows the name of the active application and lists the current user and role. You can double-click the user and role to display the User Settings dialog box in which you can change your current role if multiple roles are available to your user. For information about User Settings options, see Teamcenter client user settings. 3 Search box The Search box provides predefined quick searches using dataset, item ID, item name, keyword search, and advanced search features. For more information about the search feature in the rich client, see the Rich Client Interface Guide. 4 Navigation pane The navigation pane provides quick access to the data you use most. In addition to finding, organizing, and accessing your data, you can configure the display of the Teamcenter perspective buttons in the navigation pane to display only those perspectives that you use regularly to perform your tasks. Click the reorder button above the Search box to display the Navigation Section Ordering dialog box that lets you hide sections or change the order of sections in navigation pane. For information about configuring the navigation pane, see the Rich Client Interface Guide. 5 Application pane The application pane displays the application perspectives that are open in your Teamcenter session. By default, the Getting Started application perspective displays a single Getting Started view. 6 Getting Started application button 7 Primary applications 8 Secondary applications Application perspectives are composed of views that can be moved elsewhere in the Teamcenter window, or can be dragged out to the desktop. Such detached views remain connected to Teamcenter and continue to function in concert with other views. Provides access to the Getting Started application. Primary application buttons provide access to your most frequently used Teamcenter application perspectives. Secondary application buttons provide access to Teamcenter application perspectives you use infrequently. PLM00002 J Getting Started with Teamcenter 2-3

18 Chapter 2 Using Teamcenter interfaces 9 Clipboard button The clipboard button displays the Clipboard Contents dialog box, which contains references to objects that have been cut or copied from your workspace. The total number of objects on the clipboard is displayed to the right of the symbol. For more information about the clipboard in the rich client, see the Rich Client Interface Guide. The status message area on the lower-left side of the Teamcenter window is available to any application to indicate whether the client is ready for input or is working, so the user interface may not be accepting input at that time. The status messages on the lower-right side of the Teamcenter window indicate the status or activity of background threads for any potentially long operations. The default message is Working, but other messages, such as Loading children, can be supplied by the application running the background thread. Information shown in this area can often be observed in more detail in the Progress view. In the Progress view, some operation messages have a Cancel button that can be useful in cases where an operation was started but is not wanted at that time, such as when a user is loading thousands of nodes but decides that operation is not needed. On Windows systems, operational status for the rich client interface and the Teamcenter server is provided by the Teamcenter icon in the system tray. To display the running status dialog box, click the Teamcenter icon in the system tray. 2-4 Getting Started with Teamcenter PLM00002 J

19 Using Teamcenter interfaces The server and user interface condition symbols show the current status of the rich client interface and the Teamcenter server. The server status indicates the state of the Teamcenter server: o The server is ready, but there is no current communication between the client and the server. o o o The server is busy. The server appears to be idle. The server appears to be disconnected. The client status indicates the condition of the rich client: o o The user interface is responsive. The user interface is unresponsive. Rich client perspectives and views Within the Teamcenter rich client user interface, application functionality is provided in perspectives and views. Some applications use perspectives and views to arrange how functionality is presented. Other applications use a single perspective and view to present information. Your administrator can use the HiddenPerspectives preference to prevent the display of some Teamcenter perspectives in the rich client. For information about editing preference values, see the Preferences and Environment Variables Reference. If your site has online help installed, you can access application and view help from the rich client Help menu or by pressing F1. PLM00002 J Getting Started with Teamcenter 2-5

20 Chapter 2 Using Teamcenter interfaces For more information about rich client perspectives and views, see the Rich Client Interface Guide. Opening application perspectives in the rich client In the rich client, you can open application perspectives several ways: Use the navigation pane to select a primary or secondary application or to include other available applications in the primary or secondary listings. Tip If the navigation pane is not visible, use the Window Navigation Pane menu command to display it or click the Navigation Pane icon in the toolbar. Select a perspective using the Window Open Perspective menu command. Use the shortcut menu Send To command to open a selected object in another application. Not all perspectives may be installed or licensed at your site, and your site may have added or renamed perspectives after installation. Also, the order presented by the Window Open Perspective menu command defaults to an automatic alphabetization that gives precedence to uppercase letters over lowercase letters. The order of presentation may vary at your site. Rich client application perspectives Application Button Description 4G Designer 4G Designer- MBOM Reconciliation Lets you manage the design data of large products such as those found in the shipbuilding, automotive and aerospace industries. Use 4G Designer to create and manage collaborative designs, partitions, worksets, subsets, and design elements. For more information about 4G Designer, see the 4th Generation Design Guide. Lets you build a manufacturing bill of materials by assigning design elements from a collaborative design into a product structure representing the MBOM. For more information about the 4G Designer-MBOM Reconciliation perspective, see the Manufacturing Process Planner Guide. 2-6 Getting Started with Teamcenter PLM00002 J

21 Using Teamcenter interfaces Application Button Description ADA License Access Manager Appearance Configuration As-Built Manager Audit Manager Allows you to access International Traffic in Arms Regulations (ITAR), intellectual property (IP), and exclusion license administration capabilities as a non-dba group Teamcenter user. For more information about ADA License, see the Authorized Data Access License Guide. Enables administrators to control access to data in Teamcenter using the Access Manager (AM) rule tree, which is a collection of rules available at your site. For information about Access Manager, see the Access Manager Guide. Enables administrators to configure the use of appearances, which cache data to improve performance when managing large product structures. Tasks include defining the appearance sets for which the site tracks appearances and configuring the mapping of occurrence notes into appearance attributes. For information about Appearance Configuration, see the Appearance Configuration Guide. Lets you manage the as-built configuration of an asset realized from a product definition structure, such as a design or manufacturing structure. This is a separately licensed application installed as an optional overlay on the standard Teamcenter product. For more information about managing as-built configurations, see the As-Built Manager Guide. System administrators use Audit Manager to create and control audit logs that track selected properties for specified actions in the database. For information about Audit Manager, see the Audit Manager Guide. PLM00002 J Getting Started with Teamcenter 2-7

22 Chapter 2 Using Teamcenter interfaces Application Button Description Authorization CAE Manager CAE Manager (Legacy) (formerly CAE Structure Editor) CAE Structure Designer (formerly StructureMap Builder) Change Manager Classification System administrators use Authorization to grant access to Teamcenter administrative applications and utilities to users based on their group membership or their role in a group. For information about Authorization, see the Application Administration Guide. Lets you identify product data for analysis and create and manage corresponding CAE data. For information about CAE Manager, see the Simulation Process Management Guide. Provides CAE Manager and Inspector views to let you manage CAE processes and procedures, including definition of components for analysis, design validation, and analysis procedure verification. For information about CAE Manager, see the Simulation Process Management Guide. Enables you to create and manage structure map rules that can be used to generate CAE model structures. For information about CAE Structure Designer, see the Simulation Process Management Guide. Let you track changes to a product throughout its life cycle. You propose a change to a product and then manage the entire cycle of review, approval, and implementation of the change. For information about Change Manager, see the Change Manager Guide. Enables you to classify and categorize your product data based on predefined attribute values. For information about Classification, see the Classification Guide. 2-8 Getting Started with Teamcenter PLM00002 J

23 Using Teamcenter interfaces Application Button Description Classification Administration Command Suppression Content Management DPV Measurements Dashboard Enables administrators to define the groups, classes, subclasses, and views that form the Classification hierarchy. For information about Classification Administration, see the Classification Administration Guide. Provides Applications, Suppress Commands, and Organization views to let administrators control the display of menu and toolbar commands within Teamcenter perspectives. You can suppress the display of commands for an entire group hierarchy or a specific role within the hierarchy, for entire groups of users, and for users who are assigned a role within a group. It also allows you to suppress the display of specific commands on a designated menu or to suppress the display of entire menus. For information about Command Suppression, see the Application Administration Guide. Enables you to manage SGML and XML information stored in a Teamcenter database in conjunction with SGML/XML authoring tools to create technical publications in multiple formats. For information about Content Management, see the Content Management Guide. Allows Dimensional Planning and Validation data managers to view measurement data events based on their date or job serial number and to activate or deactivate selected events. For more information about DPV Measurements, see the Dimensional Planning and Validation Administration Guide. Shows the Reporting and Analytics dashboard. For more information about the Dashboard application, see the Report Builder Guide. PLM00002 J Getting Started with Teamcenter 2-9

24 Chapter 2 Using Teamcenter interfaces Application Button Description Database Utilities DesignContext Getting Started Issue Manager Launch Pad Used to access Teamcenter volume information and database user information. For information about using the Database Utilities application, see Getting Started with Automotive Edition. Lets you quickly focus on a particular work part in the Repeatable Digital Validation (RDV) environment and on any other parts affected within the context of a change to that part. RDV lets you accurately model specific product assembly configurations and use the results with analytical and visualization tools to facilitate learning and decision making. For information about DesignContext, see the DesignContext Guide. Provides a point from which you can quickly start working in Teamcenter. You can search for a part, open your worklist, view or edit product structure, or view or edit classification data. For information about the Getting Started application, see the Rich Client Interface Guide. Tracks problems, or issues, with a product by letting you manage the review, approval, and implementation of the issue. Also lets you view and manage requests for the penetration of structures that were generated in NX. For information about Issue Manager, see the Issue Manager Guide. Provides a visual desktop to place items and notes, called nodes, for quick reference in either a carousel or grid display mode. By default, the Launch Pad application is hidden unless an administrator removes it from the HiddenPerspectives preference value list. For information about using the Launch Pad application, see the Rich Client Interface Guide Getting Started with Teamcenter PLM00002 J

25 Using Teamcenter interfaces Application Button Description Lifecycle Viewer Used for visualization of parts and assemblies, Lifecycle Viewer provides multiple views that let you display and work with design data typically stored in CAD-data formats. Lifecycle Viewer functionality is available in multiple product configurations along with a variety of optional software modules. Teamcenter supports product visualization requirements in multiple ways, including: Lifecycle Viewer A Teamcenter application available in the rich client. Embedded viewers Viewers accessed within Teamcenter applications such as My Teamcenter and Structure Manager. Stand-alone viewer An application installed separately from Teamcenter, which supports both local and Teamcenter-managed data. Manufacturing 4D Scheduling Manufacturing BOM Reconciliation For information about Lifecycle Viewer and other visualization options, see Getting Started with Product Visualization. Provides a Schedule Manager view alongside process and product views to enable 4D analysis of very large structures. This analysis allows a manufacturing planner to visualize what parts of a structure are already assembled by a specific date in a given area of the product. For information about the Manufacturing 4D Scheduling perspective, see the Manufacturing Process Planner Guide. Provides two structure views with their accompanying Graphics views to help you align the engineering BOM with the manufacturing BOM. For information about Manufacturing Process Planner perspectives, see the Manufacturing Process Planner Guide. PLM00002 J Getting Started with Teamcenter 2-11

26 Chapter 2 Using Teamcenter interfaces Application Button Description Manufacturing Process Sequencing Manufacturing Work Instructions Manufacturing Process Planner (formerly Manufacturing Structure Editor) Multi-Structure Manager (formerly called Collaboration Context) My Teamcenter Provides PERT and Process Gantt views to help you specify the process flow. For information about Manufacturing Process Planner perspectives, see the Manufacturing Process Planner Guide. Provides Standard Text, Standard Text Library, and Textual Work Instruction views to assist you in authoring work instructions by choosing from a library of standard text elements. For information about the Manufacturing Work Instructions perspective, see the Manufacturing Process Planner Guide. Enables you to design a process plan for manufacturing a product. The process plan describes the overall strategy used to manufacture the product and defines the specific processes and operations used in the plan. For information about Manufacturing Process Planner, see the Manufacturing Process Planner Guide. Enables you to manage any of the structure types compatible with Teamcenter, including product structures and manufacturing process structures. For information about Multi-Structure Manager, see the Multi-Structure Manager Guide. Provides Teamcenter Component, Summary, Details, Viewer, and Impact Analysis views you use to perform many basic tasks such as viewing and modifying your data, initiating and participating in a workflow process, and checking your data into and out of the Teamcenter database. For information about My Teamcenter, see the My Teamcenter Guide Getting Started with Teamcenter PLM00002 J

27 Using Teamcenter interfaces Application Button Description Organization PLM XML/TC XML Export Import Administration Part Planner Plant Designer (formerly called Factory Structure Editor) Platform Designer Product Configurator Lets the Teamcenter administrator create and maintain your company s virtual organization within Teamcenter. This virtual organization is a way of organizing user accounts and their respective permissions and user groups. For information about Organization, see the Organization Guide. Enables administrators to create PLM XML import and export rules used to configure the import and export of data in PLM XML format. For information about PLM XML/TC XML Export Import Administration, see the PLM XML/TC XML Export Import Administration Guide. Enables you to design a plan that details how to manufacture a piece part product. For information about Part Planner, see the Part Planner Guide. Enables you to author and view factory layouts. For information about Plant Designer, see the Plant Designer Guide. Provides a mechanism to plan and control the evolution of product structures at your site by building generic structures of your products that contain a high degree of variability. Platform Designer uses architecture breakdowns to create and disseminate design content and product variability. For information about Platform Designer, see the Platform Designer Guide. Lets you define and manage the variability of a product, including options, option values, option families, option rules, and constraints (rule checks). For more information about Product Configurator, see the Product Configurator Guide. PLM00002 J Getting Started with Teamcenter 2-13

28 Chapter 2 Using Teamcenter interfaces Application Button Description Project Query Builder Registry Editor Relation Browser Report Builder Report Generator Enables administrators to control access to a Teamcenter database that is used by multiple organizations, such as project teams, development teams, suppliers, and customers. Access to data is controlled on a project-by-project basis. For information about Project, see the Project and Program Guide. Enables administrators to create, modify, and delete saved queries that are made available to the Teamcenter user community. For information about Query Builder, see the Query Builder Guide. Enables the editing of Teamcenter rich client registry files. This perspective is used only for editing registry files that are used for internationalization, dynamic class invocation, and configuration in the rich client framework. For information about Registry Editor, see the Registry Editor Guide. Provides Relation Browser, Image Preview, Graph Overview, and Properties views you use to perform basic tasks such browsing object relations, viewing 2D images, locating an object graphically in a map of relations, and examining the properties of a selected object. For information about Relation Browser, see the Relation Browser Guide. Enables administrators to build summary, item, and custom reports. For information about Report Builder, see the Report Builder Guide. Generates reports on products, manufacturing processes, and plant structures managed by Manufacturing Process Management. For information about Report Generator, see the Report Generator Guide Getting Started with Teamcenter PLM00002 J

29 Using Teamcenter interfaces Application Button Description Requirements Manager Resource Manager Schedule Manager Service Manager Service Planner Service Request Manager Enables the identification, allocation, and ongoing maintenance of product requirements. For information about Requirements Manager, see the Systems Engineering Guide. Manages manufacturing resources, such as cutting tools, machine tools, fixtures, weld guns, robots, and related documents. For information about Resource Manager, see the Resource Manager Guide. Enables you to define and manage schedules for your projects. These schedules can be shared with members of your team. You can allow team members to update specific tasks, schedule subsections of the project, or update the entire project schedule. For information about Schedule Manager, see the Schedule Manager Guide. Supports as-maintained structure management and service event management capabilities using the Contains, Disposition History, Log Entries, Physical Part Usage History, Service Details, Service Editor, and Utilization views. For information about Service Manager, see the Service Manager Guide. Lets you create and manage service plans, service requirements, work cards, activities, and other information to support the service planning process. Uses the Service Planner and Plan Details views. For information about Service Planner, see the Service Planner Guide. Supports service request management capabilities using the Open Service Request, Request Home, and Service Request Status views. For information about Service Request Manager, see the Service Request Manager Guide. PLM00002 J Getting Started with Teamcenter 2-15

30 Chapter 2 Using Teamcenter interfaces Application Button Description Service Scheduler Setup Wizard Software Parameter Manager Specification Manager Structure Manager (formerly called Product Structure Editor) Provides the capability to define, schedule, and implement service work using the Home, Service Editor, Service Scheduler, Work Order Home, and Summary views. For information about Service Scheduler, see the Service Scheduler Guide. Facilitates postinstallation set up of a Teamcenter database using an input file to populate the information required to create the basic components of the Teamcenter organization. Using Setup Wizard, a system administrator can create user/person definitions, assign a group/role to a user, and optionally define a default volume for assigned groups. For information about Setup Wizard, see the Setup Wizard Guide. Lets you manage embedded software parameters and their location into hardware controller memory space. You can segregate controller memory into multiple segments that can be divided into blocks. Software Parameter Manager provides the framework to import parameter addresses and conversion rules as well as to generate the flash file for each memory segment. For more information, see the Embedded Software Solutions Guide. Enables you to view and work with specifications that capture the complete definition of products and how to manufacture them. For information about Specification Manager, see the Specification Manager Guide. Enables you to create, edit, and configure product structures. For information about using Structure Manager, see the Structure Manager Guide Getting Started with Teamcenter PLM00002 J

31 Using Teamcenter interfaces Application Button Description Subscription Monitor Systems Engineering Validation Manager Volume Management Enables administrators to query subscriptions created in the database, to monitor and delete subscription events and actions, and to generate statistical reports related to subscriptions, events, and actions in either text or bar chart format. For information about Subscription Monitor, see the Subscription Monitor Guide. Encompasses functional modeling and requirements management. Functional modeling lets you represent the functional breakdowns of a product and decompose your proposed design or product into functional subsystems. Systems Engineering lets you identify, allocate, and maintain product requirements. These capabilities are provided by the Requirements view and the Function view, respectively. For information about functional modeling and requirements management, see the Systems Engineering Guide. Provides a decision mechanism to let users ensure an item revision meets compliance before it is released. Once validation processes are configured, users can select an item revision from My Teamcenter and confirm its compliance with the business rules defined at your site. For information about Validation Manager, see the Validation Manager Guide. Allows administrators to improve performance by creating migration policies that move lower priority files to either destination volumes or third-party storage systems. All data continues to appear online to users. Files stored on secondary and tertiary tiers can be read without moving them to the highest level. For information about Volume Management, see the Volume Management Guide. PLM00002 J Getting Started with Teamcenter 2-17

32 Chapter 2 Using Teamcenter interfaces Application Button Description Web Browser Workflow Designer Workflow Viewer Provides access to Web pages from within the rich client framework. Web Browser lets you navigate to Web pages and view Web pages within the rich client rather than switching to a separate Web browser. Web Browser also provides the capability to access MIME (Multipurpose Internet Mail Extension) file types and to view files created in other applications, such as Microsoft Word and Excel, through the Web browser. For information about Web Browser, see the Application Administration Guide. Enables administrators to design workflow processes using predefined tasks and handlers. For information about Workflow Designer, see the Workflow Designer Guide. Enables you to view in-progress workflow processes and related data. For information about Workflow Viewer, see the Workflow Viewer Guide. Open a rich client perspective You open an application perspective in the rich client in any of the following ways: Click the application button in the navigation pane. Select the perspective from the Window Open Perspective menu. Select an object in a navigation view and use the Send To shortcut menu command to select an application. Double-click an object in a navigation view to open the perspective associated with that object type. For example, to open My Teamcenter in the rich client, click My Teamcenter in the navigation pane. If you do not see My Teamcenter listed as a primary application, check for the My Teamcenter button in the secondary application button bar at the bottom of the navigation pane. You can use Configure Applications ( ) at the bottom of the navigation pane to find and place the My Teamcenter button in the navigation pane Getting Started with Teamcenter PLM00002 J

33 Using Teamcenter interfaces You can configure the display of application buttons in the rich client interface by designating perspectives to be primary or secondary. For more information, see Configuring the display of applications. Switch between open perspectives Use any of the following methods to change from the currently displayed open perspective to another open perspective: Use the Back button in the toolbar, its associated menu,, or Ctrl+Shift+F8 to display an application opened before the current application. Use the Forward button in the toolbar, its associated menu,, or Ctrl+F8 to display an application opened before the current application. Hold down Ctrl+F8 to display a Perspectives menu, and then release F8 and use your mouse or your keyboard arrows to select the perspective to display. Save, reset, or close a rich client perspective To save the currently active perspective when you have arranged a useful layout of views and view networks: 1. Choose WindowfiSave Perspective As. 2. Enter a new name for the perspective. 3. Click OK. To restore a perspective to its default state, choose WindowfiReset Perspective. This returns all default views to their original locations. You close an application perspective in rich client in any of the following ways: Click the X in the application banner. If you click the X in a view tab, only the selected view is closed and the application perspective remains active. Select the application, and then select WindowfiClose Perspective. Working with the rich client navigation pane The rich client navigation pane provides quick access to the data you use most. You can use the rich client navigation pane to find and organize your data and to help you perform common tasks, such as creating a part, creating a dataset, or applying a status to a part. PLM00002 J Getting Started with Teamcenter 2-19

34 Chapter 2 Using Teamcenter interfaces 1 Upper part of the navigation pane The reorder button above the Search box lets you display the Navigation Section Ordering dialog box to hide sections or change the order of sections in navigation pane. Quick-open Search provides predefined searches using dataset, item ID, item name, keyword search, and advanced search features. Quick Links provide access to your Home folder, worklist, saved searches, and web links. For information about working with Quick Links, see the Rich Client Interface Guide. Open Items displays links to items that are open in an active perspective Getting Started with Teamcenter PLM00002 J

35 Using Teamcenter interfaces History displays links to Teamcenter objects that you opened in the past. Links are displayed with the most recently closed object displayed at the top of the History list. Favorites displays links to Teamcenter objects that you have designated as favorites. For more information, see Add favorites to organize your data. 2 Primary application buttons 3 Secondary application buttons 4 Configure Applications button I Want To provides links to the tools used to complete tasks that you perform repeatedly, such as initiating a process or change. For more information about working with I Want To tasks, see the Rich Client Interface Guide. Provide access to your most frequently used Teamcenter applications. Provide access to the Teamcenter applications that you use infrequently. Provides access to the tools you can use to configure the display of primary and secondary applications. For information about specifying primary and secondary applications, see Configuring the display of applications. You can also show or hide the navigation pane. To show or hide the navigation pane: Choose Window fi Navigation Pane. For information about displaying the navigation pane, see the Rich Client Interface Guide. Configuring the display of applications You can configure the display of applications in the navigation pane by choosing a command from the Configure Applications menu pane. Menu commands include the following: at the bottom of the navigation Show More Applications Shows more applications in the listings for primary applications and secondary applications. Show Fewer Applications PLM00002 J Getting Started with Teamcenter 2-21

36 Chapter 2 Using Teamcenter interfaces Shows fewer applications to the listings for primary applications and secondary applications. Navigation Pane Options Specifies and organizes applications for listing as primary applications and secondary applications. Add or Remove buttons in the Navigation Pane Options dialog box. Moves applications between the primary applications and the secondary applications list. You can drag the sash up or down in the navigation pane to adjust the number of application buttons that appear in the primary and secondary application lists. If the secondary application area cannot contain all the applications, the applications that do not fit are displayed at the bottom of the Configure Applications menu. For information about configuring the navigation pane, see the Rich Client Interface Guide. Customizing the toolbar You can add commands or remove commands from Teamcenter rich client perspectives. The Customize Toolbar shortcut menu command displays the Customize Toolbar dialog box. The Customize Toolbar dialog box lets you add commands to the toolbar or remove commands from the toolbar for each Teamcenter rich client perspective you use frequently. The Restore Defaults shortcut menu command returns a perspective toolbar to its default state. For more information about customizing the toolbar, see the Rich Client Interface Guide. Some Teamcenter options do not have symbols associated with them. When you add these options to the toolbar, the generic button is displayed and the command name is shown as a tool tip when you move the mouse cursor over the button. Configuring table data display in the rich client You can configure the way data is displayed in tables throughout the rich client interface. The method of configuring data display in application table panes, such as in Structure Manager, differs from the method of configuring data display in view tables, such as the Details view in My Teamcenter Getting Started with Teamcenter PLM00002 J

37 Using Teamcenter interfaces After you configure the table data display using either method, you can: Apply the configuration to the current table. Save the configuration and apply it another time you want to view data. To configure the data display in an applications table pane, right-click a column header and choose the applicable command from the Table Function Menu. To configure the data display in a view table, click the Menu button applicable command from the view menu. and choose the PLM00002 J Getting Started with Teamcenter 2-23

38 Chapter 2 Using Teamcenter interfaces Managing your thin client interface The thin client home page is typically the default page that appears when you log on. It serves as a starting point to allow you to navigate to other functions. When you log on, the home page initially displays the contents of your Home folder in the tree pane. The Home folder is the root object (topmost) on the page. You can subsequently navigate to any other object that you have permission to access and view this object as the root object on the page. Any children of the root object display below the object. The object may be, for example, a dataset, structure, or collaboration context. When you click the link to an object in the home folder, Teamcenter displays the selected object with the object as the root and expanded by one level to show all of its immediate children. The children of an object display differently, depending on the type of object you select, as follows: Object type Folder Item Item revision All other workspace objects Visible children Folder contents Item revisions and all attachments arranged by relation type BOM view revision and all attachments arranged by relation type None You can expand and collapse the root object with the expand (+) and collapse ( ) buttons Getting Started with Teamcenter PLM00002 J

39 Using Teamcenter interfaces Thin client interface The thin client interface has a standard menu bar and toolbar with options that vary depending on the currently active application. You can place the cursor over a thin client toolbar button to display a tooltip description. 1 Menu bar and button bar Provides access to menu and button commands and lists the current user name, group, role, revision rule, and server. 2 Navigation pane Provides search functionality, link groups, and application buttons. You can expand and collapse the entire pane and pane groups, select what is displayed in primary and secondary areas, and configure the display of applications. 3 Component pane Displays component hierarchies in a tree view. You can resize this pane to be wider or narrower. PLM00002 J Getting Started with Teamcenter 2-25

40 Chapter 2 Using Teamcenter interfaces 4 Data pane The data pane displays tabbed information. Depending on the type of object selected and the configuration specified in your installation s XRT style sheet, you may see tabs such as Overview, Details, Related Datasets, Attachments, History, Change History, Where Used, Structure, Impact Analysis, Available Revisions, and Viewer. Groups of objects within a tab, called object sets, can be configured in the XRT style sheet. Each group of information can be configured to display in table, list, or thumbnail. Each group can also be supported by action command buttons such as Cut and Copy. For information about creating object sets, see the Client Customization Programmer s Guide. You can configure the columns in the Details tab. The default layout for thin client applications has a header bar containing menus, command buttons, and session information above three panes, arranged vertically side-by-side. Some thin client applications arrange the component pane and the data pane horizontally. The layout configuration for a thin client application can only be changed by customization. If instant messaging is configured, the data pane may also display the current Microsoft Office Communicator status of the owning and last modified users. For more information about configuring instant messaging, see the Application Administration Guide. Open an application in the thin client To open an application, click a primary or secondary application button in the navigation pane. For more information about the applications available in the thin client, see Thin client applications. For more information about working with the navigation pane, see Working with the thin client navigation pane. Thin client applications The thin client interface can be used to perform many of the same tasks you can perform in the rich client interface. However, there are fewer distinct applications available in the thin client, and administrative tasks cannot be performed in this interface Getting Started with Teamcenter PLM00002 J

41 Using Teamcenter interfaces The following table describes the thin client applications and shows the button associated with each application. Button Application name Description My Teamcenter Structure Manager Systems Engineering Manufacturing Process Planner Classification Adhoc Design Context Design Context Schedule Manager Lets you perform basic tasks, such as searching for your work, viewing and modifying your data, initiating and participating in a workflow process, and checking your data in to and out of the Teamcenter database. Lets you create, edit, and configure product structures. Lets you identify, allocate, and maintain product requirements. Lets you view a process plan that you create in the rich client Manufacturing Process Planner application and use to manufacture a product. The process plan describes the overall strategy used to manufacture the product and defines the specific processes and operations used in the plan. Lets you classify and retrieve your product data based on predefined attribute values. Lets you configure assemblies, and then send them in PLM XML format to stand-alone Teamcenter s lifecycle visualization mockup or NX to view. Lets you focus on a particular work part in the Repeatable Digital Validation (RDV) environment and any other parts affected within the context of a change to that part. RDV allows you to accurately model specific product assembly configurations and use the results with analytical and visualization tools to facilitate learning and decision making. Lets you define and manage schedules for your projects. These schedules can be shared with members of your team. You can allow team members to update specific tasks, schedule subsections of the project, or update the entire project schedule. PLM00002 J Getting Started with Teamcenter 2-27

42 Chapter 2 Using Teamcenter interfaces Button Application name Description Issue Manager Lets you track product problems, or issues, by letting you manage the review, approval, and implementation of the issue. For information about using these applications in the thin client, see the Thin Client Interface Guide. Working with the thin client navigation pane The thin client navigation pane provides quick access to applications and to the data you use most Getting Started with Teamcenter PLM00002 J

43 Using Teamcenter interfaces 1 Quick Search Quick Search Allows you to make a simple search for items and datasets by item ID, keyword, item name, or dataset name. Choose the search type from the list, type the search values, and click the Go button to begin. A progress dialog box is displayed for all searches lasting more than one second. A Cancel button in the progress dialog box is displayed for metadata-only queries. Advanced Search 2 Link groups Allows you to initiate advanced queries with predefined criteria. You can save query criteria that you use frequently. Choose Advanced from the search menu to set up an advanced search. For more information about searches, see Searching in Teamcenter. Quick Links Home Returns to your home page from any other page. My Worklist Displays your worklist from any other page. My Saved Searches Displays your saved searches. My Links Creates a list of bookmarks. My View Markup History Creates a list of your markups. Contains links to pages you have recently visited. Favorites Contains links to pages you have bookmarked using the Actions Add to Favorites menu command. For more information, see Add favorites to organize your data. I Want To PLM00002 J Getting Started with Teamcenter 2-29

44 Chapter 2 Using Teamcenter interfaces 3 Primary application buttons 4 Secondary application bar Contains shortcuts to common actions. Click Customize to change the list of actions. Provides access to your most frequently used Teamcenter applications. Provides access to your additional Teamcenter applications. The Configure Applications menu displays: Available primary and secondary application commands. Choose a menu command to load the selected application. The Navigation Settings command. Choose the Navigation Settings command to display the Navigation Settings dialog box. The Navigation Settings dialog box lets you add or remove applications from the primary and secondary areas, hide applications, reorder navigation pane items, organize favorites, and customize your I Want To list. You can also use the alternative Navigation Settings button at the top of the navigation pane to display the Navigation Settings dialog box, and you can use the Collapse button to hide the navigation pane. Installed and configured applications that do not appear in the primary or secondary areas, but still appear in the Available Applications pane of the Navigation Settings dialog box, do not appear in the thin client user interface. Your browser also provides a Favorites bookmark capability. You can save a URL bookmark using the browser Favorites feature. If you have the thin client configured with SSO (single sign-on) and SSL (secure socket layer), the browser does not return you to the expected location after you log off Teamcenter and log on again, while in the same browser session. After you log off, but within the same browser session, selecting a browser Favorites bookmark link to a thin client location causes the SSO Login Service to prompt you to log on to the application using your user name and password; then the SSO Login Service redirects you to the thin client configured for the application during installation. To use a browser Favorites bookmark link to access a specific location in the thin client after you log off, you must first end the current browser session (restart the browser). After you restart the browser, the Favorites bookmarked entry requires you to log on and then accesses the desired location Getting Started with Teamcenter PLM00002 J

45 Using Teamcenter interfaces Business Modeler IDE interface The Business Modeler IDE (Integrated Development Environment) is a tool for configuring basic functionality and for customizing the data model of your Teamcenter installation. It is installed using Teamcenter Environment Manager (TEM). The Business Modeler IDE is intended for business analysts who are responsible for tailoring Teamcenter for use at their companies. Users of the IDE must have a thorough understanding of how to perform end-user tasks with Teamcenter, and have some knowledge of the data model items used in Teamcenter. Use the IDE to create: Business objects Business objects are the fundamental objects used to model business data. Create business objects to represent, for example, product parts, documents, and change processes. Business objects are also known as types. Classes Classes are the persistent representations of the data model schema, and provide attributes to business objects. Classes are also known as the persistent object model (POM). Attributes Attributes are item characteristics such as name, number, and description. Attributes are attached to classes and business objects. All children of a class or business object inherit their parents attributes. Lists of values Lists of values (LOVs) are pick lists of values. They are commonly accessed by end users from a menu at the end of a data entry field. Options Options are miscellaneous items such as change objects, units of measure, and notes. Rules Rules define the business rules that govern how objects are handled, including how they are named and what actions can be undertaken on them. Creating rules is also known as business modeling. For more information about the Business Modeler IDE, see the Business Modeler IDE Guide. Teamcenter Client for Microsoft Office Manage Teamcenter data in real time with Teamcenter Client for Microsoft Office. Client for Office gives you access to Teamcenter directly through Microsoft Office Word, Excel, PowerPoint, and Outlook. PLM00002 J Getting Started with Teamcenter 2-31

46 Chapter 2 Using Teamcenter interfaces Client for Office adds a custom Teamcenter tab to the ribbon in Word, Excel, and PowerPoint. In Outlook, each open message contains the Teamcenter tab on the ribbon. Client for Office is independent of the Teamcenter rich client. You can work in Client for Office while the rich client is running. Or, you can work solely through the Client for Office without running the rich client. Authors, manufacturing authors, reviewers, and other users can use Client for Office to perform the following Teamcenter tasks: Save and edit Office documents in Teamcenter. Browse to and search for Office documents and other Teamcenter objects. Create folders, items, and item revisions in Teamcenter. Create and edit Teamcenter datasets. Insert Teamcenter object property values, search results, pictures, JT files, and hyperlinks in Office documents. Check out and check in Office documents in Teamcenter. Submit Office documents to Teamcenter workflows. Perform Teamcenter sign-offs. Import data from Excel to create and modify structures and objects in Teamcenter. Automatically synchronize property values between Office documents and Teamcenter datasets of the MS Office type. For more information about Client for Office, see the Client for Microsoft Office Guide Getting Started with Teamcenter PLM00002 J

47 Chapter 3 How Teamcenter supports product life cycle phases How Teamcenter supports product life cycle phases Systems engineering and requirements Managing design data and product structures Product structure and configuration management th Generation Design Manufacturing process management Workflow and change management Document management basics Content management Managing contract data Vendor management Product visualization Classification and reuse CAE Data Management Repeatable Digital Validation Maintenance, repair, and overhaul As-Built Manager Service Manager Service Planner Service Request Manager Service Scheduler Teamcenter solutions Consumer Packaged Goods Aerospace and Defense Automotive Edition Materials Management Substance Compliance PLM00002 J Getting Started with Teamcenter

48 Dimensional Planning and Validation (DPV) Electronic Design Automation (EDA) Data sharing Data Exchange Global Services Multi-Site Collaboration PLM XML Getting Started with Teamcenter PLM00002 J

49 Chapter 3 How Teamcenter supports product life cycle phases How Teamcenter supports product life cycle phases Teamcenter is a suite of digital product life cycle management solutions built on an open PLM foundation. The Teamcenter solution portfolio can be configured to achieve your PLM vision by: Integrating idea management and requirements planning into the digital life cycle management, product development, and manufacturing process. Linking partners and suppliers with secure global access to your product knowledge based on access rules. Enabling consistent, repeatable processes and commonality. Teamcenter supports all phases of the product life cycle, including planning, development, execution, and support by providing tools for: Systems engineering and requirements Managing design data and product structures Manufacturing process management Workflow and change management Document management basics Content management Managing contract data Vendor management Product visualization Classification and reuse CAE Data Management Repeatable Digital Validation Maintenance, repair, and overhaul PLM00002 J Getting Started with Teamcenter 3-1

50 Chapter 3 How Teamcenter supports product life cycle phases Teamcenter solutions Dimensional Planning and Validation (DPV) Electronic Design Automation (EDA) Data sharing Systems engineering and requirements You can use Teamcenter to represent the functional, logical, and physical breakdowns of a product. You can decompose your proposed design or product into functional subsystems with the Systems Engineering application. For example, the functional breakdown of a car may be decomposed into various functional subsystems, such as the music system and the braking system. In turn, the functional subsystems may contain various individual functions of the subsystems. In a functional model, components can be functions or functional subsystems. Once you identify the functional subsystems and components, you can assign requirements to them. Teamcenter provides an integration with functional modeling tools such as MATLAB Simulink, which allows you to author model data in external tools but manage it in Teamcenter. Requirements are the blueprint from which your company designs products. Systems Engineering connects requirements into product life cycle processes, driving design decisions and helping you to avoid problems. Product requirements are delivered to life cycle participants using the Web and through standard desktop tools like Microsoft Word, Excel, and Visio. For more information, see Getting Started with Systems Engineering and the Systems Engineering Guide. Managing design data and product structures Teamcenter provides two alternative ways you can manage design data and product structures: Product structure and configuration management With this approach, you use: o o o Structure Manager to create and enhance a product structure and to configure your product structures using revision configuration, occurrence configuration, or variant configuration techniques. Platform Designer to define baseline configurations and select the components that are variable and to which variations they are applied. Multi-Structure Manager to share product structures and design components in context using existing geometry as background information. 4th Generation Design (4GD) This approach is particularly suitable for development teams working on large products that typically include millions of parts, for example, those found in the 3-2 Getting Started with Teamcenter PLM00002 J

51 How Teamcenter supports product life cycle phases shipbuilding industry. It allow users to check out and modify the individual parts that comprise the overall design of the product, without locking the entire product or major assemblies. Product structure and configuration management Using Structure Manager, you can create a product structure that can be viewed as an indented listing of assemblies and piece parts. You can attach CAD files, specification documents or other information to the top-level assembly (the product itself), or to any of the assemblies or piece parts. You can build, view, and manipulate the product structure in Teamcenter, or you can import it from an MCAD system such as NX. You can further configure your product structures using revision configuration, occurrence configuration, or variant configuration techniques. Teamcenter also enables you to establish product platforms using Platform Designer to define baseline configurations and then select the components that are variable and to which variations they are applied. This allows you to manage multiple product variations by tracking those components that are common to the platform and those that are specific to a variation. Multi-Structure Manager enables you to share product structures and design components in context using existing geometry as background information. Sharing context allows you to evaluate form, fit, and function by leveraging existing spatial context. For more information, see: Getting Started with Product Structure Structure Manager Guide Platform Designer Guide Multi-Structure Manager Guide 4th Generation Design 4th Generation Design (4GD) lets users of NX CAD or Lifecycle Visualization to cooperate in real time during the design cycle of a product. 4GD is particularly suitable for development teams working on large products that typically include millions of parts, for example, those found in the shipbuilding industry. 4GD allows users to check out and modify the individual parts that comprise the overall design of the product, without locking the entire product or major assemblies. Users work in three main phases using the 4G Designer application: Product administration The system administrator configures the necessary customization of the default 4GD business objects to suit your enterprise s working environment and data model. PLM00002 J Getting Started with Teamcenter 3-3

52 Chapter 3 How Teamcenter supports product life cycle phases Product initiation When you initiate a product, the configuration developer, design team leader or other expert user defines the main systems into which engineering provides solutions. In many cases, the initial design is created from a similar product or from an existing template for the product type. This initial framework is called the collaborative design. Product authoring In this phase, design engineers populate the collaborative design with elements that describe the product design. It can contain CAD designs, product-specific geometry, and features such as welds and weld seams. The collaborative design can be populated directly or from within a workset that is realized into a subset in the collaborative design. Typically, the design team leader assigns tasks in various areas of the collaborative design to designers with appropriate skills and assigns worksets accordingly. For more information about 4GD basic concepts, see the 4th Generation Design Guide. Manufacturing process management Manufacturing Process Management manages data created in the manufacturing planning stage of the product life cycle. It allows you to manage assembly and fabrication of products whose design is managed in Teamcenter. Collaboration between design and manufacturing teams is realized using Manufacturing Process Planner. You can manage, relate, and consolidate product and process structures to compare as-designed, as-manufactured, or any other specific configuration. Accountability checks allow you to ensure that all components in the product structure are accounted for in the assembly process. When you manufacture piece parts, Part Planner helps manage the step-by-step operations and associated documentation of your CAM software. In addition, you can use Resource Manager to create and manage tools, machine tools, fixtures, robots and other resources found at your manufacturing facility. For more information, see: Getting Started with Manufacturing Manufacturing Process Planner Guide Part Planner Guide Resource Manager Guide Workflow and change management Teamcenter provides functionality that enables you to initiate, administer, review, approve, and execute product changes. By automating your change process, you can minimize change-related rework and coordinate tasks to be performed by individuals across your organization. Because Teamcenter change management 3-4 Getting Started with Teamcenter PLM00002 J

53 How Teamcenter supports product life cycle phases leverages product structure definitions, you can evaluate the impact of changes, track the status and completion of tasks, and maintain a comprehensive history of product changes throughout the lifecycle. Change management in Teamcenter is also tightly integrated with Schedule Manager and Workflow so you can schedule implementation activities and guide a change through its phases. For more information, see the Change Manager Guide, Getting Started with Workflow, the Workflow Viewer Guide, and the Workflow Designer Guide. In addition, if you have changes or issues that do not need to be addressed through an extensive, standardized change management process, such as the one that Change Manager supports, or you have highly visual information, you can use Issue Manager. Issue Manager automatically provides access to Siemens PLM Software design review and issue resolution tools, including NX, Lifecycle Visualization, and the Lifecycle Viewer. You can use Issue Manager in both the rich client and the thin client. Use both clients to create, review, and manage issues, but use the rich client to administer your issue management process. For more information about Issue Manager, see the Issue Manager Guide. Document management basics Document management functionality uses item revision definition configuration (IRDC) objects to simplify user interactions with information. This reduces the need to understand the Teamcenter data model and relationship model. Based on your business processes, IRDC objects defined in the Teamcenter Business Modeler IDE application let you automate document creation, rendering of presentation formats, document markup, document batch printing, and document availability. Document management functionality can be configured for any Teamcenter item, but some or all document management behaviors may be unavailable at your site. Document management uses IRDC to specify behaviors for Document items, DMTemplate items, and Dataset items. An IRDC object is created by an administrator or a customizer using the Business Modeler IDE application. This object lets you standardize document behavior at specific times in the life cycle of the document. Document behavior can be managed for New, Check In, Check Out, Copy (Save As), Revise, View/Markup, Cancel Check-Out, Sign, and Cancel Signing actions for a document. Managed behaviors can include creation and naming of derived visualization datasets, markup rules, and the creation of specified relations. Document management behavior configuration is designed primarily for Document items, but any of the behaviors can be used for any subtype of the Item type. The Document item is an object you create in Teamcenter. In document management, the document item is associated with one or more templates and dataset items in a manner configured to meet your business requirements. When PLM00002 J Getting Started with Teamcenter 3-5

54 Chapter 3 How Teamcenter supports product life cycle phases a document revision is sent to a workflow, a derived dataset can be created and attached to the document revision. When you render an item, you create a derived dataset from a source dataset. The render action is initiated from a checkin or from a workflow task. Such derived datasets are typically used when content must be provided outside the authoring organization and the ability to make changes to the original content must be restricted. For more information about rendering items, see Getting Started with Document Management. The DMTemplate item can be created by any user. A Teamcenter administrator can create an IRDC to associate a DMTemplate item with a specific item type and specific dataset types. The Dataset object represents an actual data file on the operating system or in Teamcenter. Datasets are typically authored content of some sort, such as Microsoft Office files or CAD data files. Markup access for documents is controlled by the Markup privilege, assigned by administrators in Access Manager. Markup is typically used for authoring with controlled iteration in the context of a change control object. o Documents used in markup are typically in Adobe PDF or Microsoft Word format. When Microsoft Word format is used, a markup summary can be extracted to Microsoft Excel. o o Markup in document management is not the same as Lifecycle Visualization markup, which is used for marking up illustrations and Lifecycle Visualization output. To perform markup in Adobe Acrobat or Adobe Reader, ensure the documents preference for PDF/A View Mode is set to Never. You can digitally sign a PDF file stored as a dataset named reference file with Adobe Acrobat and Adobe Reader. New style sheets let you configure create dialog boxes and summary display for Document objects. The Digital Sign Dataset ACL rule grants the owning user and owning group digital signing privileges for the dataset object. 3-6 Getting Started with Teamcenter PLM00002 J

55 How Teamcenter supports product life cycle phases Digital signing is supported only for PDF datasets created in Teamcenter 10.1 or later. o In the Adobe Reader, the PDF file must have Enable Usage Rights for Digitally Sign enabled. o o Use Adobe Acrobat or Adobe LiveCycle Reader Extensions to enable usage rights for PDF files. To perform digital signing in Adobe Acrobat or Adobe Reader, ensure the documents preference for PDF/A View Mode is set to Never. For information, see Getting Started with Document Management. Caution When you create markups or update markups using Adobe Acrobat or Adobe Reader, the markups must be saved in Teamcenter or canceled before you begin the Sign action for the PDF dataset file. You can use create style sheets provided for Document objects to customize the New Business Object wizard in the rich client and thin client to streamline the document creation process. Two user interface dialog boxes added to the New Business Object wizard support: Attaching files to a dataset for a new object. Submitting a new object to workflow. Additional capabilities provided by document management batch printing include creating configuration objects to manage printer configuration and system stamp configuration. Batch printing lets you select workspace objects, such as items, item revisions, or datasets, and print the associated documents with system stamps and watermarks. A system stamp can include the user name, the date and time, and other specified business item attributes. You can also define optional additional user stamps, which can be appended to the system stamp, to select when printing documents. The stamp content and position is specified in a MetaDataStamp (MDS) file. System stamps can be placed on the first page or all pages of the output. A watermark is a recognizable image or pattern in paper that appears as various shades of lightness or darkness when viewed by transmitted light or when viewed by reflected light against a dark background. Watermark characteristics are specified in the MDS file. For more information about working with MDS files, see the Application Administration Guide. Document management also benefits from: The use of full-text search retrieval indexes. The production of thumbnail graphics. For information about configuring document management functionality, see Getting Started with Document Management. PLM00002 J Getting Started with Teamcenter 3-7

56 Chapter 3 How Teamcenter supports product life cycle phases Content management Content Management allows technical publication authors to manage SGML and XML information stored in a Teamcenter database. Content is managed by creating publications comprised of topic components and associated graphics. Content Management works in conjunction with several publishing and editing tools. Publications can be generated from the application for both online and print formats. There is support for multiple language versions and the ability to manage topic through release cycles. For more information, see the Content Management Guide. Managing contract data Contracts are pivots that drive business across different industry sectors. A contract is a structured procurement document listing the milestones and the schedule dates of the contract event. This procurement document can be a list of data requirement items, such as design information, drawings, status reports, and so on. After the contract is created, the data analyst creates a workflow schedule to collate the feedback and the review comments that are generated during the data item approval process. This is done by initiating correspondence related to the contract. A graphical representation of managing contract data through Teamcenter is shown in the following figure. 3-8 Getting Started with Teamcenter PLM00002 J

57 How Teamcenter supports product life cycle phases The sequence of steps is as follows: 1. Create data item descriptions (DIDs). DIDs are predefined contract forms that specify data content, data format, and other specific instructions for the suppliers. You can maintain a DID repository to associate a data requirement item (DRI) to the contract. 2. Create a contract. The administrator or the data analyst creates a contract and contract revision in Teamcenter. You can also choose to create a contract event for scheduling the contract review and feedback process. 3. Create data requirement items. You must attach a data requirement item (DRI) to the contract. A DRI is a technical document or deliverable that forms the basis for structured procurement. It represents a single contractual data item as described in DID. 4. Define submittal delivery schedule for the deliverable. After the DRI is specified, you must initiate the review process. Submittal represents the data item submittal package or documentation that relates to the actual documents submitted. PLM00002 J Getting Started with Teamcenter 3-9

58 Chapter 3 How Teamcenter supports product life cycle phases 5. Provide feedback. It is important to monitor the correspondence related to the data item submittal package between you and the supplier. For more information, see the Aerospace and Defense Solution Guide. Vendor management Using Teamcenter vendor management, you can model vendor contributions to a product by capturing information about the vendors and the vendor parts they provide to satisfy the form, fit, and function of commercial parts. Using vendor management objects, you can: Associate commercial parts with vendor parts. Navigate from a vendor object to commercial parts and vendor parts that are associated with the vendor object. Navigate from a commercial part or a vendor part to the vendor associated with the part. Navigate between commercial parts and vendor parts. Manage company locations and contacts. Display vendor parts in Structure Manager, including support for BOM compare. Create configurable business rules for vendor management actions. Change a vendor for a vendor part. Classify commercial and vendor parts. Teamcenter vendor management is a prerequisite for the Teamcenter Aerospace and Defense solution. For more information, see the Getting Started with Vendor Management. Product visualization The visualization tools available in Teamcenter, including the embedded viewer, the Lifecycle Viewer, and the standalone Lifecycle Visualization application, enable even nontechnical users to interpret design data, review product structure, and mark up issues for collaboration. Lifecycle Visualization is used to view documents, 2D drawings, 3D models, PCB layouts and animation playback, and provides virtual mockup, measurement, and spatial analysis capabilities in prototyping software for handling extremely large assemblies. For information about product visualization, see the Getting Started with Product Visualization Getting Started with Teamcenter PLM00002 J

59 How Teamcenter supports product life cycle phases Classification and reuse Classification enables you to create a digital library of product definition data including information about your components, subassemblies and assemblies, documents, manufacturing tools and templates, work instructions, company policies, process definitions, standardized forms, data dictionary, and industry/government regulations. Hierarchical class definitions allow you to specify attributes and valid attribute values that are used to search for design elements for reuse in a new product or program. For more information, see the Classification Guide. CAE Data Management CAE Data Management is a packaged solution that provides unique simulation process and data management capabilities for CAE engineers and CAE analysts performing analysis work. It includes: CAE Manager Enables you to create and manage engineering analysis data in Teamcenter. CAE Structure Designer Enables you to create and manage structure map rules, and generate and assemble filter, reuse, and include rules in a structure map file and save it as a dataset. You can reuse the structure map files or the filter, reuse, and include rules to generate consistent CAE model structures. You can use CAE Data Management to manage and improve CAE processes by: Generating a CAE structure from a product structure including the complexity arising from multiple configurations or variants and solutions, or directly defining components and subsystems to be analyzed. Searching your existing knowledge base and enabling data reuse. Combining support for process workflows and program execution. Verifying the use of approved analysis procedures. Increasing access to performance information. Managing complex metadata associated with simulation including the solution parameters and results. Visualizing simulation results in a unique lifecycle simulation environment. Efficiently handling huge amounts of data associated with simulation. For more information, see the Simulation Process Management Guide. PLM00002 J Getting Started with Teamcenter 3-11

60 Chapter 3 How Teamcenter supports product life cycle phases Repeatable Digital Validation Repeatable Digital Validation (RDV) tools allow you to accurately model specific product assembly configurations and use the results with analytical and visualization tools to facilitate learning and decision making. You use these tools to create digital mockups of a product or part of a product, rather than having to create expensive physical models and mockups. You can filter product or product family data, so that the user only works in an area of interest and does not have to deal with the complexity of the full product. For more information, see Getting Started with RDV. Maintenance, repair, and overhaul Teamcenter provides various applications to manage structure configurations and service process data: As-Built Manager provides the capability to manage the as-built configuration of an asset realized from a product definition structure. Service Manager supports as-maintained structure management and service event management capabilities within Teamcenter. Service Planner supports service planning capabilities within Teamcenter. Service Request Manager supports service request process management capabilities within Teamcenter. Service Scheduler provides the capability to define, schedule, and document service work. As-Built Manager As-Built Manager is a separately-licensed application that is installed as an optional overlay on top of the standard Teamcenter product. This application provides the capability to manage the as-built configuration of an asset realized from a product definition structure, such as a design or manufacturing structure, and extends the traditional lifecycle coverage beyond the manufacturing of a product. As-Built Manager provides the capability to: Capture as-built information, such as valid alternate or substitute parts, for the design or manufacturing structure. Create the as-built physical product instantiation for any configured product structure. Store and manage additional information about the as-built physical part structure that is not tracked on the product definition structure, such as serial numbers and lot numbers. Reconcile the as-built structure with a configured product definition structure to identify parts that are missing, alternate, or deviations Getting Started with Teamcenter PLM00002 J

61 How Teamcenter supports product life cycle phases Compare the as-built structure to the product definition structure or to another as-built structure. View the design product definition structure and the as-built physical structure configuration side-by-side through embedded visualization capability available in the rich client environment. Import an as-built structure from an external manufacturing execution system (MES) or an enterprise resource planning (ERP) system using PLM XML. Export an as-built structure to an Teamcenter maintenance, repair, and overhaul (MRO) system using data exchange. For information about As-Built Manager, see the As-Built Manager Guide. Service Manager The Service Manager application supports as-maintained structure management and service event management capabilities within Teamcenter. As-maintained management is the base functionality of Service Manager and allows you to manage the as-maintained configuration of an asset over its lifetime. As-maintained structures are generated from, and validated against, product definition structures, such as design or planning structures. You can use the Service Manager as-maintained management to: Create the as-maintained physical product instantiation for any configured product definition structure. Store and manage additional information about the as-maintained physical part structure that is not tracked on the product definition structure, such as serial numbers and lot numbers. Reconcile the as-maintained structure with a configured product definition structure to identify parts that are missing, alternates, substitutes, or deviations. Track part utilization, part usage, and disposition history. Manage physical locations and the assets in those locations. Manually update the as-maintained structure with changes that occur over the lifetime of the physical asset. Compare the as-maintained structure to the product definition structure or to another as-maintained structure. View the as-designed product structure and the as-maintained physical structure configuration side-by-side or by using the embedded viewer available in the rich client. Import an as-maintained structure from an external manufacturing execution system (MES) or an enterprise resource planning (ERP) system in PLM XML. Manage as-maintained structures in a Multi-Site Collaboration environment. For information about Service Manager, see the Service Manager Guide. PLM00002 J Getting Started with Teamcenter 3-13

62 Chapter 3 How Teamcenter supports product life cycle phases Service Planner The Service Planner application supports service planning capabilities within Teamcenter. Service Planner is a separately licensed application that is installed as an optional overlay on top of the standard Teamcenter product. Service Planner lets users create and manage service plans, service requirements, work cards, activities, and other information to support the service planning process. You can use Service Planner to: Create and manage service plans for a neutral product. Create service partitions within a service plan to organize service requirements. Create and manage service requirements to define the maintenance that can be performed on a product. Create service requirements to address particular fault codes. Define frequencies for service requirements to determine when the work needs to be done. Set up dependencies or relations between service requirements. Define applicability between service requirements and neutral parts. Create and manage work cards to determine how the work needs to be done. Manage the work process flow by sequencing work cards to be done in a particular order or determine work that can be done in parallel. Create and manage activities that provide more detailed information about the planned work. Create characteristic definitions and attach them to neutral parts, work cards, or activities to define data that should be recorded as part of the maintenance. Define the particular skill level needed to perform or sign off the service work. Define any expendable materials or tools needed to perform the service work. Create notices and attach them to work cards or activities to provide additional information, such as any notes, warnings, or cautions related to the planned work. Manage the time estimates for the planned work. Create and manage the work instructions. Import and export Service Planner data in PLM XML format. Manage Service Planner data in a Multi-Site Collaboration environment. For information about Service Planner, see the Service Planner Guide Getting Started with Teamcenter PLM00002 J

63 How Teamcenter supports product life cycle phases Service Request Manager The Service Request Manager application supports service request process management capabilities within Teamcenter. Service Request Manager lets service providers manage customer requests for service from initiation through completion. Service Request Manager is a separately licensed application that is installed as an optional overlay on top of the standard Teamcenter product and the Service Manager application. You can use Service Request Manager to: Create and manage service catalogs and the individual standard service offerings contained in a service catalog. Capture service work requested by a customer through service requests. Define the scope of the service work by creating requested activities. Requested activities can be created from an existing service offering (catalog-based) or created as a stand-alone requested activity (noncatalog-based). Requalify a noncatalog-based requested activity to a service offering. Assign service work to roles by assigning participants. Assign work to external service organizations by delegating requested activities. Identify work that is a result of product or part discrepancy and capture details about those items through reported discrepancies. Manage approval and completion of service work through workflow and signoff process. Track estimated and actual time and cost of service work. Track status and history of service work. Manage service request processing in a Multi-Site Collaboration environment. For information about Service Request Manager, see the Service Request Manager Guide. Service Scheduler The Service Scheduler application lets companies define, schedule, and implement service for their products. The maintenance scheduler can define a complete work scope including the schedule of work, breakdown of activities, the resources required, the work assignments, and the estimated cost and labor. After the work scope is defined, service technicians complete their activities. They can record required information identified within the work scope, request resources needed to do the work, record discrepancies found while completing the work, and sign off the work. Using Service Scheduler, maintenance schedulers and service technicians can: Manually create work orders, schedules, job cards, and job tasks Assign people resources PLM00002 J Getting Started with Teamcenter 3-15

64 Chapter 3 How Teamcenter supports product life cycle phases Schedule assignments Estimate cost and labor Manage schedules Define part requests for required materials, tools, and equipment Receive issued materials, tools, and equipment Complete work assignments and perform signoffs Capture start/stop times and work time Define part movement transactions to drive configuration updates Capture discrepancies discovered during implementation of service For information about Service Scheduler, see the Service Scheduler Guide. Teamcenter solutions Teamcenter provides various products for specific industries: Consumer Packaged Goods Aerospace and Defense Automotive Edition Materials Management Substance Compliance Consumer Packaged Goods The Consumer Packaged Goods solution helps the consumer packaged goods and the food and beverage industries support the following areas: Brand management With brand management, you can classify and manage brands. Initiative management With initiative management, you can create and track initiatives such as package and artwork development. Finished product management Finished product management allows you to classify and manage finished products. Packaging and artwork 3-16 Getting Started with Teamcenter PLM00002 J

65 How Teamcenter supports product life cycle phases Packaging and artwork are the first things that a consumer notices on a product. Creating a package involves creating marketing briefs, design briefs, package roughs, copies, and so on (For a sample package and artwork design process, see Getting Started with Consumer Packaged Goods). With Teamcenter Consumer Packaged Goods solution, you can track and manage the steps in packaging and artwork creation. Interspec integration Interspec is a specification management tool that can be integrated with Teamcenter. Using Specification Manager, you can view, query, and manage specifications created in Interspec. For more information, see Getting Started with Consumer Packaged Goods. Aerospace and Defense The Aerospace and Defense solution provides data model extensions and features that you access through standard Teamcenter applications, such as My Teamcenter, Change Manager, Schedule Manager, and Structure Manager. The solution provides multiple industry-specific features that enable you to: Execute complex document-centric or part-centric development programs. Manage parts lists and standard parts. Use standard and custom notes to provide additional design details about parts and documents. Manage the program life cycle and its data, including program requirements, deliverable schedules, and related changes. Protect intellectual property and national security while promoting collaboration. In addition, you can extend Teamcenter Aerospace and Defense solution with other Teamcenter capabilities including: Systems Engineering and Requirements Management Simulation Process Management Manufacturing Process Management Content Management Maintenance, Repair, and Overhaul For more information, see the Aerospace and Defense Solution Guide. Automotive Edition Teamcenter Automotive Edition is a component of an industry-focused solution intended to meet the needs of design and manufacturing organizations within the automotive industry. Teamcenter Automotive Edition provides the GM Overlay installation that serves as a base implementation for automotive industry PLM00002 J Getting Started with Teamcenter 3-17

66 Chapter 3 How Teamcenter supports product life cycle phases users. Other customer-specific implementations can then be layered on top of the Teamcenter Automotive Edition overlay. This guide provides an overview of the commercial Teamcenter Automotive Edition and GM Overlay features and how these are used by manufacturers and suppliers. This guide is for persons responsible for installing and configuring Teamcenter Automotive Edition and GM Overlay features and for those who use these features, specifically General Motors, its suppliers, and partners. For more information, see Getting Started with Automotive Edition. Materials Management The Materials Management solution stores approved materials and substance information imported from a third-party database (for example, Granta, IMDS) into a materials library in the Teamcenter database. The materials and substances can also be created by a materials analyst. By storing the materials in Teamcenter, the Teamcenter materials library is available for use by other Siemens PLM Software applications, rather than each application owning individual material libraries. The Materials Management solution is required to support Substance Compliance. Materials Management provides the capability to designate the substance composition of materials, so that regulatory compliance reporting can be supported. For example, a Teamcenter part or BOM is sent to an external compliance checker to verify if the part or BOM is compliant with specific substance regulations. For more information, see the Materials Management Solution Guide. Substance Compliance The Substance Compliance solution is an environmental compliance solution that enables companies to conform to environmental laws, regulations, standards, and other requirements for their own parts and for the parts manufactured or supplied from an external source. Before sending a part or BOM for substance compliance check, the material and substance information must be available in the Teamcenter materials library. The material and substances are imported into Teamcenter by the materials analyst from an external materials library (for example, Granta, IMDS). Therefore, it is mandatory to install the Materials Management solution before installing the Substance Compliance solution. For more information about managing materials, see the Materials Management Solution Guide. The compliance officer role is provided in Substance Compliance to perform various tasks, such as requesting material substance declaration from suppliers, reviewing the material substance declarations received from the suppliers, and applying exemptions. The compliance officer sends a request to the supplier for the material and substance declaration using the My Teamcenter user interface. The supplier enters the required information in the material and substance declaration and sends the declaration back to the compliance officer. On receiving the declaration from the supplier, the compliance officer reviews it. After reviewing the declaration, the 3-18 Getting Started with Teamcenter PLM00002 J

67 How Teamcenter supports product life cycle phases compliance officer can either approve or reject the declaration. From Teamcenter, the compliance officer sends a part or BOM to the Compliance Process Manager (CPM) to verify if the part or BOM is environmentally compliant. The CPM sends the compliance result to Teamcenter. For more information, see the Substance Compliance Solution Guide. Dimensional Planning and Validation (DPV) Siemens PLM Software provides Tecnomatix Dimensional Planning and Validation (DPV), a quality management solution you can easily integrate into your Teamcenter environment. DPV enables the extended enterprise to collect, manage, dimensionally analyze, and report on quality measurement information. This report generation solution provides rapid access to design and manufacturing information that directly influence s your enterprise s quality targets. DPV provides you with: Enterprise-wide visibility to quality information. An integrated definition of your measurement process coordinated with product design, manufacturing planning, and plant layout. In-depth analysis of captured measurement information. Associative reporting, with initial and updated reports. Historical and summary measurement reporting. For more information, see Dimensional Planning and Validation Tutorial. Electronic Design Automation (EDA) Teamcenter EDA (Electronic Design Automation) integrates ECAD (Electronic Computer Aided Design) applications with Teamcenter to allow designers to manage their ECAD design, BOM, and related library data in Teamcenter. Teamcenter allows two types of EDA integrations: ECAD design integration This includes design tool integrations (Mentor Board Station, Cadence Allegro, Mentor PADS, Cadence OrCAD, Mentor Expedition, and Altium Designer). ECAD part library integration This includes library integrations (Mentor Board Station, Cadence Allegro, and Mentor Expedition). Both these integrations are separate functionalities and run separately. They can be installed either together or separately depending on your requirement. PLM00002 J Getting Started with Teamcenter 3-19

68 Chapter 3 How Teamcenter supports product life cycle phases Teamcenter EDA is separately licensed and distributed. For information about Electronic (EDA) Lifecycle Management documentation, contact the Global Technical Access Center (GTAC): Data sharing Teamcenter provides various capabilities to share data among the following products: Data Exchange provides data mapping, transfer, and synchronization between Teamcenter and Teamcenter Enterprise sites. Data Exchange provides data mapping, transfer, and synchronization between Teamcenter and Engineering Process Management sites. Data Exchange provides data transfers between OEM and supplier sites that: o o Use Teamcenter (managed sites) but are not connected to the OEM Teamcenter environment through offline transfers of briefcase files. Do not have Teamcenter (unmanaged sites) but use Briefcase Browser to access Teamcenter data in briefcase files. Global Services provides data transfers between various data sources, including third-party software such as JBDC databases. Multi-Site Collaboration provides data sharing and data synchronization between Teamcenter sites or between Teamcenter sites and Engineering Process Management sites. PLM XML data can be imported and exported for non-teamcenter sites. Additionally, Data Exchange supports exporting data in PDX format and can import and export to any system that supports TC XML format. Data Exchange Data Exchange allows you to transfer data between differing systems. This capability allows you to transition existing data from a different system to Teamcenter. The following terms are important in understanding transition between products. Term Transition Upgrade Definition A high-level term for moving data and users from one solution platform to another. Refers to updating a platform from one release level to another or to a new platform where the effort to transition is consistent with a release level upgrade Getting Started with Teamcenter PLM00002 J

69 How Teamcenter supports product life cycle phases Term Coexistence Integration Migration Definition A deployment environment where business process solutions are split across one or more platforms, but share, reuse, or otherwise enable programs based on either platform. The technical aspect of coexistence in the context of transition. A method of rapidly transitioning from one solution platform to another. Time is the major discriminator as compared to coexistence. Coexistence with Teamcenter Enterprise supports: Transfer of metadata, JT, and other files. o o o Bidirectional operation Transfer of CAD from Teamcenter Enterprise to Teamcenter Transfer of JT from Teamcenter to Teamcenter Enterprise Variability of data models on both ends. Transfer of ownership or modification rights. Batch and event based transfers that are scheduled, from a workflow, or user initiated. Coexistence with Engineering Process Management supports: Adding new Teamcenter production sites or upgrading existing Engineering Process Management sites in a progressive fashion that shares data across these environments. Integrating Teamcenter into a supply chain where partners can use either Teamcenter or Engineering Process Management. The Data Exchange Briefcase functionality supports: Non-networked Teamcenter to Teamcenter data sharing. Variability of data models on both ends. Transfer of metadata, JT, and CAD data (NX, CATIA, and Pro/ENGINEER). Data Exchange currently is not a full replacement of Multi-Site Collaboration for companies exchanging other types of CAD data or manufacturing data. Export of PDX data for use by applications supporting this format. For non-teamcenter suppliers, data import and export in PLM XML format. PLM00002 J Getting Started with Teamcenter 3-21

70 Chapter 3 How Teamcenter supports product life cycle phases Data Exchange also provides online tracking of active and scheduled data transfers, graphical mapping between schemas, and process flow control using Business Process Execution Language (BPEL). Global Services Global Services is the foundation for Data Exchange support for coexistence. It also provides the following capabilities: Real-time data aggregation Data publishing across dissimilar systems (loosely coupled integrations such as Teamcenter to Teamcenter Enterprise) Replication and synchronization across like systems (Multi-Site object-level replication) Multi-Site Collaboration Multi-Site Collaboration enables you to share synchronized product information with geographically dispersed partners and suppliers who work with Teamcenter. Multi-Site Collaboration enables multiple sites that maintain different business rules to exchange product definitions while retaining their local autonomy, as well as allowing the exchange of data with users outside your enterprise. A central database maintains a record of every information object that you intend to share across the Teamcenter network. This record indicates the database in which the objects reside, as well as attributes that you can reference to narrow your database searches. Objects are shared by publishing the object in the central database by indicating which sites are authorized to import the object. For more information, see the Multi-Site Collaboration Guide, the Preferences and Environment Variables Reference, and the appropriate installation guide for your platform. PLM XML PLM XML supports the export and import of Teamcenter objects, such as items, datasets, BOMs, forms, and folders, as well as system data, such as business rules and organization data. In PLM XML/TC XML Export Import Administration, you create transfer mode objects that define the import or export context by applying closure (traversal) rules, filter rules, action rules, and property set rules to the input or output of objects and system data. These rules can be a static set stored in the database or they can be applied only to a specific session. Rules stored in the database can be imported and exported. PLM XML/TC XML Export Import Administration also references Extensible Stylesheet Language Transformations (XSLT) files that describe how to transfer the source tree or data structure of an XML document into the result tree for a new XML document, which may be completely different in structure, and can be stored with the transfer mode objects and applied as a post-export or pre-import operation. The PLM XML framework does not support XSLT file validation; therefore, it is the implementor s responsibility to ensure valid XSLT format Getting Started with Teamcenter PLM00002 J

71 How Teamcenter supports product life cycle phases A product data management (PDM) system is used to store and retrieve data within a certain context. The context helps define how the data is used, filtered, and transformed. To accomplish this, the PDM system must have the capability to export and import data. In Teamcenter, this is done using the PLM XML import export framework with the various applications written to capitalize on this layer. One important aspect of data translation is that each translation has a unique purpose and scope. The purpose is associated to a business function and the application-specific interaction with the PDM system. Each instance of a translation is unique and different. A translation must be managed to support its mode of transfer, the traversal of data desired, the filtering of the data to be done and actions to apply to the translation. The PLM XML import export framework supports these unique translations. However, in Teamcenter-to-Teamcenter transfers, do not use PLM XML as a data synchronization mechanism to keep the structure modifications at both sites synchronized. PLM XML export cannot capture all of the edits made on a product structure at the source site. The exported PLM XML file only captures a snapshot of the product structure, so the repeated process of exporting from the source site and importing at the destination site causes unexpected results (the structures at both sites will not be synchronized). In these situations, use classic Multi-Site. Another important aspect of data translation is managing the mapping between the PDM data and the PLM XML standard entity schema for reading the data in and out. In the PLM XML import export framework, data entities are mapped using a known set of correspondence, where most data is automatically translated by the PLM XML import export module. The PLM XML import export module supports application extensibility for additional data translations. For the mapping between PLM XML entities and Teamcenter entities, see the PLM XML/TC XML Export Import Administration Guide. PLM XML is the interoperability mechanism for many products (internal and external). There are a variety of PLM XML representations available to represent the same data. For example, product structure can be represented by normal PLM XML export files from Teamcenter (ProductView and ProductDef, for example). These files can be used to import the same product structure to another Teamcenter instance. They can also be used by files exported using the bomwriter utility (mainly used for Lifecycle Visualization; these files cannot be imported). Before attempting to import a file to Teamcenter, determine the source of the file. If it is exported by another Teamcenter site or an application that matches Teamcenter exported files, it is a good candidate for import to Teamcenter. In a multiuser environment, when multiple users initiate import on the same data simultaneously (for example, multiple users updating the same assembly), only one is successful. The other users get a locking message (objects are locked by different user in different session). PLM XML cannot be used to share organization objects that are shared through global organization (Multi-Site). For more information, see the Multi-Site Collaboration Guide. PLM00002 J Getting Started with Teamcenter 3-23

72

73 Chapter 4 Common Teamcenter tasks Common Teamcenter tasks Viewing online help What help formats are available? Access the help library Access information about Teamcenter Access help for the current application Navigating the help collection (HTML) Access Teamcenter PDF files Search the PDF collection Viewing your Teamcenter PDF documentation on the ipad Working with data objects Teamcenter data objects Working with folders Home, Newstuff, and Mailbox folders Managing basic data Searching in Teamcenter Creating data Cutting, copying, pasting, and deleting data objects Dragging and dropping data objects Add favorites to organize your data Using projects to organize data Overview of object properties Working with relation properties Overview of checkout and checkin Explicit checkout Implicit checkout Identify the checkout owner of an object Check out an object Check in an object Transfer checkout to another user Cancel a checkout request View the checkout history of an object Providing notification of changes in checkout status View the notification list for an object Managing object protection Rules-based protection Object-based protection Using 4th Generation Design PLM00002 J Getting Started with Teamcenter

74 Managing product structures Repeatable Digital Validation Managing manufacturing data Managing Mechatronics data Managing publications Visualizing your product data Translating documents to derived output formats Previewing 2D and 3D images Classifying parts and components Managing changes Using workflow processes Importing and exporting data Importing objects Import a Teamcenter object Import a STEP file Import data from a PLM XML file Exporting objects Export an object Export objects in STEP format Export objects in PLM XML format Export objects using application interface mode Running reports Using mail, , and instant messaging in Teamcenter Sending and receiving Teamcenter mail Send a mail message Receiving and reading mail Address lists Create an address list Modify an address list Delete an address list Getting Started with Teamcenter PLM00002 J

75 Chapter 4 Common Teamcenter tasks Common Teamcenter tasks You perform Teamcenter tasks using a client. The most commonly used clients are the rich client and the thin client. The Teamcenter thin client is a browser-based interface you can use to navigate to various Teamcenter objects and functions. Access is available to the same Teamcenter server and data as the rich client uses. No thin client software is required on a Teamcenter client. You can use the thin client interface to perform many of the same tasks you can perform in the rich client interface. However, there are fewer distinct applications available in the thin client, and administrative tasks cannot be performed in this interface. The Teamcenter rich client, a platform-independent client implementation (Java application) for users who interact frequently with Teamcenter, runs on client hosts and serves as a gateway to your company s product information. It provides a broad selection of application perspectives and views to manage your product information. Administrators can use the rich client to: Implement and manage data access and security. Configure behavior when objects are created, saved, and revised. Create workflow templates. End users can use the rich client to: View and work with assemblies. Create, locate, revise, and save workspace objects. Check in and check out workspace objects. Perform and manage workflow tasks. Viewing online help Teamcenter provides help for each application, as well as a series of getting started guides. PLM00002 J Getting Started with Teamcenter 4-1

76 Chapter 4 Common Teamcenter tasks Teamcenter help is provided as online help files in HTML format and in PDF format. The Teamcenter HTML help collection must be installed and configured before it can be viewed. For more information about installing and configuring online help, see the appropriate server installation guide (for Windows or UNIX/Linux) and Teamcenter Environment Manager Help. The Teamcenter PDF help collection can be viewed from the documentation distribution media or installed on a Teamcenter host, and PDF files can be copied to a mobile device (such as an ipad or Android tablet) or printed for reading offline. What help formats are available? Teamcenter help is delivered in two formats: HTML and PDF. Each format has its own advantages. HTML (HyperText Markup Language) has the look and behavior typical to Web pages; small chunks of information extensively linked to other chunks of information. HTML lends itself to quickly reading, copying, and sharing smaller chunks of information, such as stepped procedures. The HTML directory on the documentation installation media contains HTML versions of the manuals. The Teamcenter online help requires a Web browser that supports Java for the search to work. The browser version and Java specification required for online help depends on the operating system you are using. For information about supported browsers and Java versions for your operating system, see the Siemens PLM Software Certification Database: certification/teamcenter.shtml Several features of the online help system require the display of popup windows; for example, searching the online help collection and viewing graphics. If a popup blocker utility is installed on the Web server or client workstation, you must configure the utility to allow popup windows from the online help domain. Otherwise, the online help system does not function correctly. The advantage of PDF (Portable Document Format) is its portability. Readers can easily entire deliverables to others and save the PDFs to other devices (such as an ipad or Android tablet) for use in locations without Internet connectivity. It is also easy to print chapters or entire documents with PDF. The PDF directory on the documentation distribution media contains Adobe PDF versions of the Teamcenter online help. From this directory, open the index.htm file in a Web browser to view the Teamcenter PDF Help Collection. You can view, search, and print individual guides or selected pages from within your Web browser. To search the entire PDF collection, click the Search button in the Teamcenter PDF Help Collection page. This launches Adobe Reader and loads 4-2 Getting Started with Teamcenter PLM00002 J

77 Common Teamcenter tasks the search index for the collection. In the Search dialog box in Adobe Reader, type the text you want to find. You can view these guides using Adobe Acrobat Reader, which you can download free from Adobe at If you want to share the PDF collection on your network, extract the PDF.zip from the documentation distribution media to a network location and set file permissions as necessary to allow viewing. o Viewing Adobe Acrobat files requires Adobe Acrobat Reader, which you can download free at Viewing Adobe Acrobat files within a Web browser requires the appropriate Adobe Acrobat plug-in for your Web browser. o If you share the Teamcenter PDF Help Collection on a Web (HTTP) server, you cannot search the entire PDF collection. The collection search functionality works only when you share the PDF collection from a file system location. For collection search capability, access the PDF collection in a Web browser using a URL with FILE protocol, for example: Local host: file:///d://pdf/index.htm Network host (UNC path): file://///host/pdf/index.htm o If you want to open PDF files directly, browse the PDF\pdf directory (Windows systems) or the PDF/pdf directory (UNIX/Linux systems) on the documentation distribution media. To open the PDF collection search, open the PDF index file, tchelp.pdx, in this directory. This launches Adobe Reader and loads the search index for the collection. For a demonstration of the help interface features, see the Teamcenter Help Tour. For more information about viewing Teamcenter PDF files on the ipad, see Viewing your Teamcenter PDF documentation on the ipad. Access the help library The Teamcenter HTML help collection must be installed and configured before it can be viewed. For more information about installing and configuring online help, see the appropriate server installation guide (for Windows or UNIX/Linux) and Teamcenter Environment Manager Help. In the rich client, choose HelpfiHelp Library or press Ctrl+F1 to access the full library. In the thin client, choose HelpfiHelp Library to access the full library. Access information about Teamcenter In the rich client, choose Help About. PLM00002 J Getting Started with Teamcenter 4-3

78 Chapter 4 Common Teamcenter tasks The system displays information about Teamcenter, including information about plug-ins and configuration details. In the thin client, choose Help About Teamcenter. Access help for the current application In the rich client, choose Help Current Application or press the F1 key to display help for the currently active view in the current application In the thin client, choose HelpfiCurrent Application to access help for the thin client current application. You can also choose HelpfiThin Client Interface Guide to access the Thin Client Interface Guide. Navigating the help collection (HTML) The Teamcenter help system includes: Toolbars for navigating and searching the help collection and for providing feedback about information in the help topics. A search results page in the same browser to reduce window clutter. Breadcrumb links on each page to help you track your location. A Topics (table of contents) pane that lists all help deliverables and provides sequential navigation through the topics and access to all specific topics in the help collection. o To move through topics page-by-page, click an entry in the table of contents and then press the down arrow. This displays the next topic and expands collapsed hierarchies as you proceed. o To hide or show the Topics pane, click the Show/Hide topics button. A topic content pane that displays topic information. Links to related information. 4-4 Getting Started with Teamcenter PLM00002 J

79 Common Teamcenter tasks 1 Navigation toolbar Displays the table of contents. Returns you to the home page. Lets you navigate back through the hierarchy of help categories. Prints the current page. 2 Search toolbar Advanced Search Displays search results. The Search box is available on every page. Displays previous search terms. Displays the advanced search page. Type text for your search in the Search box. Click Advanced Search to set search behaviors and filter search areas. Search tips are available in the advanced search page. PLM00002 J Getting Started with Teamcenter 4-5

80 Chapter 4 Common Teamcenter tasks To return to the search results page, use your browser s Back button or click Search again. 3 Feedback toolbar To search within an extensive topic, such as the glossary, use the browser Find command, for example, Ctrl+F in Windows Explorer or Cmnd+F in the Safari browser. Lets you send feedback about content. Access Teamcenter PDF files You can access Teamcenter PDF files directly from the documentation distribution media or from the location where you installed the PDF files using Teamcenter Environment Manager (TEM). To Unzip PDF files from the PDF.zip file (This is required if you have not installed the PDFs using TEM.) Access PDF files from the Teamcenter PDF launch page Access a PDF file directly Do this Locate the PDF.zip file in the documentation distribution media and extract it to a directory on your hard disk. Open the index.htm file in a browser to launch the PDF collection. Locate the guide you want and open the PDF file. Search the PDF collection You can search individual PDF files or search the entire Teamcenter PDF collection. The procedure you use depends on how you are accessing the PDF files. To Search individual PDF files Do this Use the search feature within Acrobat when you are accessing a PDF file from the PDF collection launch page or directly from the storage location. 4-6 Getting Started with Teamcenter PLM00002 J

81 Common Teamcenter tasks To Search all PDF files The Full Reader Search feature is not available when viewing PDF files in a Web browser. Using Acrobat Full Text Search Do this When you are accessing a PDF file from the PDF collection launch page, the full search feature is available only if your access is based on a file system location (rather than a Web (HTTP) server location): Click the Search button in the Teamcenter PDF Help Collection page. This launches Adobe Reader and loads the search index for the collection. In the Search box in Adobe Reader, type the text you want to find. When you are accessing PDF files directly from the installed location or from the documentation distribution media: 1. Open the PDF index file, tchelp.pdx. This launches Adobe Reader and loads the search index for the collection. 2. Type the text you want to find in the Search box in Adobe Reader. 1. Click the arrow next to the search text box and choose Open Full Reader Search, or type Ctrl+Shift+F to open Full Reader Search. 2. At the bottom of the Search dialog box, click Show More Options. 3. Under Look in, choose Select Index. 4. In the Index selection dialog box, click Add. 5. Browse to the PDF\pdf directory, select the tchelp.pdx file, and then click OK. 6. Type the text you want to find. Search results are displayed in the Results box. The steps may vary if you use Full Reader Search in an Adobe Acrobat product other than Acrobat Reader. Viewing your Teamcenter PDF documentation on the ipad You can view your Teamcenter PDF documentation using Apple s ibooks mobile application on the ipad. ibooks allows you to: Perform searches. PLM00002 J Getting Started with Teamcenter 4-7

82 Chapter 4 Common Teamcenter tasks Bookmark pages. 4-8 Getting Started with Teamcenter PLM00002 J

83 Common Teamcenter tasks Change the size of the page. PLM00002 J Getting Started with Teamcenter 4-9

84 Chapter 4 Common Teamcenter tasks Working with data objects Teamcenter uses data objects to represent your product data, such as parts, assemblies, processes, product changes, requirements, and specifications. These objects are stored in one or more database and can be shared with users across your enterprise. Access to your data is controlled by access rules that are applied to the data objects. The integrity of your data is protected by the managed check-in/check-out features that allow you to lock other users out of work that is in process, allowing them to view but not modify the information. Teamcenter data objects The following table describes the most commonly used Teamcenter objects. This list is not exhaustive; data objects are introduced in other guides throughout the Teamcenter library Getting Started with Teamcenter PLM00002 J

85 Common Teamcenter tasks For information about working with objects in a Teamcenter client, see the appropriate client guide. Object Folders Items and item revisions Relations Item and item revision relations Relation properties Datasets Description Folders are data objects that you use to organize product information. Folders can contain any other information object, including other folders. Items and item revisions are the fundamental objects used to manage information in Teamcenter. Items can be single parts or structures that represent a product, part, or component. Items can contain other data objects, including other items and folders. Item revisions are used to manage changes (revisions) to your product information. Relations associate objects. For example, datasets (secondary objects) are associated with item revisions (primary objects) using relation objects. The meaning of the secondary object can vary from one context to another. Enterprises typically use many pieces of information that in some way describe or relate to an item or item revision. Relations define the relationship between the item or item revision and the attached data. Relation properties record information specific to the association or context in which the object is used. You can create relations between objects, modify the properties of those relations, delete relations, and create saved queries based on relation business object attributes. Your administrator can create custom attributes (properties) to apply to relation business objects in the system. A single item can be associated to multiple items or contexts. Objects are associated by relations, and the meaning of the relation can vary from one context to another. Datasets are data objects that manage data files created by other software applications. Each dataset references at least two other objects: a dataset type that contains a list of tools that can operate on the dataset, and a tool that is used to create or modify the dataset. Each dataset can manage multiple operating system files. Each type of operating system file is called a named reference. PLM00002 J Getting Started with Teamcenter 4-11

86 Chapter 4 Common Teamcenter tasks Object Dataset relations Description Datasets are typically related to part and assembly items and item revisions, and an assembly in Teamcenter can have many related datasets. For example, an assembly can have any of the following dataset relations, among others: Requirements criteria are related through the Requirements relation. Criteria specify maximum weight or specific dimensions, for example, but not how the assembly is constructed. Design instructions are related through the Specification relation. These datasets describe methods, designs, processes, or procedures used to satisfy the requirements. Test plans are related through the Attaches relation. Test plans specify the test details exercised against the assembly before it is production ready. Assembly instructions are related through the attaches relation. These provide instructions for assembling components to create a part. CAD parts are related through an IMAN_Drawing relation. This dataset is created by a CAD tool such as NX. 3D visualization models are related through the 3DMarkup relation. This file is typically created in a third-party CAD tool like NX. Field reports are related through the Reference relation. These reports can provide various kinds of information, such as how the assembly is performing in production. In My Teamcenter in the rich client, use the Details view to see related items; the Relation column displays the name of the relation for each related dataset. Forms and master forms You can also sent objects to the Relation Browser application to explore relations graphically and to use the Properties view to list object attributes. Forms and master forms are data objects that display specific product information (properties) in a predefined template. Forms are often used to create a digital facsimile of an existing hard copy form. Master forms are used to display specific product information in a standardized format Getting Started with Teamcenter PLM00002 J

87 Common Teamcenter tasks Object BOM view and BOM view revisions Address lists Envelopes Aliases Alternate identifiers Design element Subset Workset Description BOM views are used to manage product structure information related to items. BOM view revisions are used to manage product structure for item revisions. An address list is any combination of valid users, groups, and/or external addresses. Envelopes are objects used to represent Teamcenter mail messages sent to you from other Teamcenter users. Envelopes can be used to send object references as well as simple text messages to other Teamcenter users. This is useful for throughout your enterprise. The capability to send an envelope is available in Teamcenter in the rich client but not in the thin client. Alias objects allow you to store items and item revisions in the Teamcenter database according to the naming conventions used by non-teamcenter user communities. Alternate identifiers store information about part numbers and attributes of the same part from different perspectives. They allow different user communities to identify and display an item or item revision according to their own rules rather than according to the rules of the user who created the object. A design element is a representation of a component in the context of the product. Design elements typically include geometric data and are authored by CAD users in NX. A subset is collection of design elements and a search recipe that, when configured, yield a precise definition of those design elements. The search recipe contains one or more search terms that locate the content of the subset definition. A workset is a composition of design content from collaborative designs and item structures. A workset provides local references to subset definitions and assemblies in an isolated space to update in a location that is unaffected by updates other users may make. It may contain subsets or item assemblies as its direct children. PLM00002 J Getting Started with Teamcenter 4-13

88 Chapter 4 Common Teamcenter tasks Object Partition Changes Collaboration contexts Structure contexts Description A partition is an element in a collaborative design that organizes and groups other elements as part of a hierarchical breakdown. Partitions are organized hierarchically into schemes and each partition scheme references a partition breakdown. Partitions are then added in the context of a selected scheme. Administrators use partition schemes to control the types of child partition that you can add to a partition. Change objects, including change orders and change requests, allow you to manage changes to a product definition and configuration. A collaboration context is a project folder or directory that contains shared data. This data may be shared between Teamcenter users or between Teamcenter itself and an external application. It can contain references to any other item in Teamcenter and to shared items that may be modified by Teamcenter or an external application. A structure context is a BOM or assembly structure contained in a collaboration context. The structure context can contain occurrence groups, items, and item revisions. Working with folders Folders are a flexible way to organize your product information. Folder objects can contain references to other objects and/or other folders. Use Teamcenter to: Create a new folder. Rename a folder. Move a folder. Print a folder. Delete a folder. Home, Newstuff, and Mailbox folders The My Teamcenter application always contains the three default folders: Home, Mailbox, and Newstuff. These folders are automatically created by the system Getting Started with Teamcenter PLM00002 J

89 Common Teamcenter tasks Home The objects you want to work with in the My Teamcenter application can be placed within your Home folder or within some folder structure beneath the Home folder. Mailbox The Mailbox folder is the receiving point for any Teamcenter mail that has been sent to you. When you receive new Teamcenter mail, you see an envelope object in your Mailbox folder. For information about using Teamcenter mail, see the My Teamcenter Guide. Newstuff The Newstuff folder is the default folder for newly created database objects. You can designate other folders as the default location for newly created database objects. Objects remain in a folder until you move or remove them. You can move through topics in a page-by-page manner by clicking an entry in the table of contents, and then pressing the down arrow. This displays the next topic, and even expands collapsed hierarchies as you proceed. Managing basic data You can use Teamcenter to manage basic data, such as searching for your work, navigating the user interface, creating and printing data, running reports, and classifying parts and components. Searching in Teamcenter The Teamcenter search functionality lets you find data in the Teamcenter database and, optionally, in a related Autonomy index search engine database. The Quick Search feature in the navigation pane lets you search for data by specifying the dataset name, item ID, item name, or a keyword. Quick search results cannot be saved to your saved searches list. You can use saved queries to search for your work in the Teamcenter database or in databases that are part of a Multi-Site Collaboration network. Saved queries are grouped into three categories: My Saved Searches This category contains queries that you ran previously and chose to save for later use. PLM00002 J Getting Started with Teamcenter 4-15

View more

Top Articles

You might also like

Latest Posts

Article information

Author: Dan Stracke

Last Updated: 12/01/2022

Views: 6065

Rating: 4.2 / 5 (43 voted)

Reviews: 90% of readers found this page helpful

Author information

Name: Dan Stracke

Birthday: 1992-08-25

Address: 2253 Brown Springs, East Alla, OH 38634-0309

Phone: +398735162064

Job: Investor Government Associate

Hobby: Shopping, LARPing, Scrapbooking, Surfing, Slacklining, Dance, Glassblowing

Introduction: My name is Dan Stracke, I am a homely, gleaming, glamorous, inquisitive, homely, gorgeous, light person who loves writing and wants to share my knowledge and understanding with you.