Faq Teamcenter

Teamcenter 10.
Frequently Asked Questions for

Teamcenter
Publication Number
PLM00125
Proprietary and restricted rights notice
This software and related documentation are proprietary to Siemens Product

Lifecycle Management Software Inc.
© 2013 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 Frequently Asked Questions for Teamcenter PLM00125

Contents
Proprietary and restricted rights notice . . . . . . . . . . . . . . . . . . . . . . . . . 2
Frequently Asked Questions for Teamcenter . . . . . . . . . . . . . . . . . . . . . 1-1

How do I use Frequently Asked Questions for Teamcenter? . . . . . . . . . . . . . . 1-1
What is the online help? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Who do I contact for more help with Teamcenter? . . . . . . . . . . . . . . . . . . . . . 1-1
Using the Teamcenter help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

How do I install and use the help? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
What help formats are available? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
How do I use the HTML help? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
How do I use the PDF help? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4
Installing Teamcenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

How do I use TEM to install Teamcenter? . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
How do I generate the composite ID I need to get a Teamcenter license? . . . . . 3-2
Where do I find instructions on how to install and run the licensing for
Teamcenter? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
I have installed my corporate server on a UNIX machine. How do I generate a
Windows TC_DATA directory for two-tier clients to use? . . . . . . . . . . . . . . . 3-3
Upgrading Teamcenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

How do I use TEM to upgrade Teamcenter? . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
What are type name collisions, and how do I find them in my database? . . . . . 4-2
Where do I find information about changes made to Teamcenter in previous
maintenance pack releases? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
Working with Business Modeler IDE . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

How do I manage Teamcenter’s data model? . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
How do I create a new business object (previously known as types) in Teamcenter
10.1? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
How do I add properties to an existing business object in Teamcenter 10.1? . . 5-2
How do I hide item types so that when users create a new item, these types are not
seen? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
In Teamcenter 10.1, can I still add attributes to all my classes? . . . . . . . . . . . . 5-2
Administering Teamcenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1

How do I use TEM to perform maintenance tasks? . . . . . . . . . . . . . . . . . . . . . 6-1
How do I clean my database? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2
What is the transient volume used for? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2
The transient volume definition is missing from the FMS configuration file. How can
I fix this? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3
Why don’t I see the changes that someone else made to an access control list? . . 6-3
PLM00125 Frequently Asked Questions for Teamcenter 3

Contents
I’ve found some preferences in the Java source code, but I cannot find documentation
on them. What do the preferences do? . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4
What is the difference between Audit Manager and Subscription Monitor? . . . 6-4
I restricted copy privileges, but users can still copy the object. Why? . . . . . . . . 6-5
Managing FMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1

What is FMS? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1
What is TCCS and how is it related to FCC? . . . . . . . . . . . . . . . . . . . . . . . . . 7-2
When do I need to restart the FCC? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2
How do I restart an FCC process? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2
How do I stop an FCC? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3
How do I reset a user’s FCC environment? . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5
Why am I getting errors after modifying the FCC configuration? . . . . . . . . . . . 7-5
Why am I getting errors after removing the FCC? . . . . . . . . . . . . . . . . . . . . . 7-6
Why am I getting errors after using the kill command to stop FCC processes? . . 7-6
Customizing Teamcenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1

How do I customize Teamcenter? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1
How do I change page layout without writing code? . . . . . . . . . . . . . . . . . . . . 8-1
How do I change menus? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1
How can I change the icons in the rich client interface? . . . . . . . . . . . . . . . . . 8-2
How can I change the icons in the thin client interface? . . . . . . . . . . . . . . . . . 8-2
How do I create a form for the rich client? . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3
What is the process for migrating my Engineering Process Management rich client
Java interface code into the Eclipse-based Teamcenter 10.1 interface? . . . . . 8-3
Working with the rich client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1

What users should use the rich client? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1
What can I do to improve my startup performance? . . . . . . . . . . . . . . . . . . . . 9-2
Will deleting my cache improve performance? . . . . . . . . . . . . . . . . . . . . . . . . 9-3
What are perspectives and views? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-4
What happened to applications? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-4
I see different Search boxes. Do they all search the same way? . . . . . . . . . . . . 9-5
How do I delegate signoff responsibility? . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-7
I meant to delegate my signoff, but instead I changed the responsible party. How do
I correct this? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-9
How do I view access privileges set for another user on an object? . . . . . . . . . . 9-10
Working with the thin client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1

What users should use the thin client? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1
How does the thin client differ from the rich client? . . . . . . . . . . . . . . . . . . . . 10-2
What Teamcenter functionality is available in the thin client? . . . . . . . . . . . . 10-3
What Teamcenter functionality is not available in the thin client? . . . . . . . . . . 10-3
Many commands are suppressed in the thin client, but are not listed as
suppressed in the Command Suppression application. How do I display these
commands? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-4
Managing changes and workflows . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1

What is a Teamcenter workflow? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1
Can I delete a workflow process template while workflows based on this template are
still running? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-3

Contents
Can I modify shipped task templates before adding them to a workflow? . . . . . 11-3
How do I find specific arguments or handlers used in different workflow
tasks? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-3
Working with product structures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-1

Why use generic product structures? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-1
Should I use classic variants or modular variants to manage options and
variants? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-1
When should I manage business parts and designs separately? . . . . . . . . . . . . 12-2
I want to perform spatial searches to identify parts that may interfere with the
assembly I am working on. My assembly is not complex (less than 200 parts).
What is the best option? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-2
Working with e-mail and Teamcenter mail . . . . . . . . . . . . . . . . . . . . . . 13-1

What is the difference between Teamcenter mail and my operating system
e-mail? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1
How does Teamcenter mail work? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1
What is involved in setting up external e-mail programs to support subscription
notification? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-2
Why are all the instant messaging symbols disabled (grayed out) throughout
Teamcenter? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-2
Classifying your product data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-1

What is the benefit of classifying my site’s data? . . . . . . . . . . . . . . . . . . . . . . 14-1
Why don’t I see any data when I open the Classification application? . . . . . . . . 14-1
Setting up programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-1

What are programs? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-1
How does the new concept of program align with the existing project, group, and role
concepts? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-1
Will I be able to have different rules (display rules, extension rules, GRM rules, and
so on) for each program? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-2
Will I be able to have different lists of values for each program? . . . . . . . . . . . 15-2
Will I be able to have different preferences for each program? . . . . . . . . . . . . . 15-2
Creating reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-1

How are reports created? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-1
What is the best way to create reports on my Teamcenter data? . . . . . . . . . . . 16-1
Working with visual reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-1

What can I do with visual reports? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-1
Can I work with visual reports in Teamcenter? . . . . . . . . . . . . . . . . . . . . . . . 17-1
Managing quality data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-1

What is the difference between DPV Reporting & Analysis and Teamcenter reporting
and analytics? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-1
What are features? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-1
How do I change the name of a feature? . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-2
Can I use measurement data to create feature definitions in DPV? . . . . . . . . . 18-2
How can I organize my plant? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-2
PLM00125 Frequently Asked Questions for Teamcenter 5

Contents
Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Index-1

Chapter
1 Frequently Asked Questions

for Teamcenter
How do I use Frequently Asked Questions for Teamcenter? . . . . . . . . . . . . . . 1-1
What is the online help? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Who do I contact for more help with Teamcenter? . . . . . . . . . . . . . . . . . . . . . 1-1
PLM00125 Frequently Asked Questions for Teamcenter

Chapter
1 Frequently Asked Questions

for Teamcenter
How do I use Frequently Asked Questions for Teamcenter?

Within Frequently Asked Questions for Teamcenter, Siemens PLM Software offers
introductory answers to frequently asked questions about Teamcenter.
The answers include links to additional information within the online help collection.
The additional information includes conceptual information, step-by-step procedures
for using functionality, and reference topics.
What is the online help?

The Teamcenter 10.1 Help Library provides complete documentation about
installing, configuring, administering, customizing, and using Teamcenter. Refer to
the this library for all matters concerning the implementation and use of Teamcenter
software.
You can install and configure the Teamcenter 10.1 Help Library for access directly
from a file system (rich clients only) or over the Web (thin clients and rich clients).
For more information about installing the library, see the appropriate server
installation guide (for Windows or UNIX/Linux).
Who do I contact for more help with Teamcenter?

The Global Technical Access Center (GTAC) is your focal point for post sale software
support. The center provides both application and operating system software
support by telephone and electronic access.
If you have any further questions about using Teamcenter, contact GTAC. It is
your source of current, accurate, version-controlled Teamcenter information. You
can access GTAC at:
http://support.industrysoftware.automation.siemens.com
PLM00125 Frequently Asked Questions for Teamcenter 1-1

Chapter
2 Using the Teamcenter help
How do I install and use the help? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
What help formats are available? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
How do I use the HTML help? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
How do I use the PDF help? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4

Chapter
2 Using the Teamcenter help
How do I install and use the help?

When installing Teamcenter using Teamcenter Environment Manager (TEM), you
have several options for installing the online help.
For more information about your installation options, see the Teamcenter
Environment Manager Help.
For more information about installing the help, see either the Installation on
Windows Servers Guide or the Installation on UNIX and Linux Servers Guide.
After installing the help, you can configure access to the online help from other rich
client hosts and other thin client Web applications.
For more information about configuring access to the help, see either the Installation
on Windows Servers Guide or the Installation on UNIX and Linux Servers Guide.
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.

Chapter 2 Using the Teamcenter help
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:
http://support.industrysoftware.automation.siemens.com/ certification/teamcenter.shtml
Note 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 e-mail 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
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 http://www.adobe.com.
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.
Note o Viewing Adobe Acrobat files requires Adobe Acrobat Reader, which
you can download free at http://www.adobe.com. 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
2-2 Frequently Asked Questions for Teamcenter PLM00125

Using the Teamcenter help
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 Teamcenter Help behavior and commands, see Getting
Started with Teamcenter.
How do I use the HTML help?

Tips for working with HTML format:
Copy and paste You can copy only one topic at a time. Click and drag to
highlight the content you want to copy.
Note If the content you want to copy runs beyond the space
on your screen, click and drag from the bottom of the
content up to the top.
The formatting of content pasted into a Microsoft Word

document (.doc files) is similar to the original HTML content.
Content pasted into a text file (.txt files) loses most of its
formatting.
Hyperlinks Hyperlinks can link to a topic within the same deliverable or to
a topic in a different deliverable.
• The links connect to a topic within the deliverable when
the link contains the name of a specific topic.
For example, How do I delegate signoff responsibility? links
to the topic of the same name within the Frequently Asked
Questions for Teamcenter deliverable.
• The links connect to a topic in a different deliverable when

the link is the name of a different deliverable.
For example, the link in the following paragraph connects
to a topic in the My Teamcenter Guide that discusses
signoff tasks:
o For more information about your options for completing

the perform-signoffs task, see the My Teamcenter
Guide.

Chapter 2 Using the Teamcenter help
Search toolbar
Displays search results. The

Search box is available on
every page.
Displays search tips.
• Type text for your search in the Search box.
• Click Preferences to set search behaviors and filter search

areas.
• To return to the search results page, use your browser’s

Back button or click Search again.
Note Search preferences and filters are also available from
the Filter your results? or Search all areas? link at
the top of the search results page.
Note To search within an extensive topic, such as the

glossary, use the browser Find command, such as
Ctrl+F in Windows Explorer or Cmnd+F in the Safari
browser.
Sharing links with To send a link that displays the HTML topic, the table of
other readers contents, and the help collection features such as the index
and search:
1. Place the cursor anywhere in the HTML topic.
The topic’s URL displays in the address bar at the top of
the page. For example:
2. Copy the contents of the address bar to your clipboard.
3. Paste the URL into an e-mail or other document.
How do I use the PDF help?

Tips for working with PDF format:

Using the Teamcenter help
Copy and paste You can drag your cursor through page after page of content,
and then copy the highlighted text to the clipboard. It is
possible, but not practical, to copy and paste numerous pages.
The formatting of content pasted into a Microsoft Word
document (.doc file) is not fully consistent with the original
PDF content. Page numbering and footer information is
included in the copy operation.
Hyperlinks As in HTML, hyperlinks containing the name of specific topics
link to topics within the deliverable.
For example, How do I delegate signoff responsibility? links to
the topic of the same name within Frequently Asked Questions
for Teamcenter.
However, hyperlinks in PDF format do not link to other
deliverables. For example, the reference in the following
paragraph does not link to the relevant topic in the My
Teamcenter Guide:
• For more information about your options for completing
the perform-signoffs task, see the My Teamcenter Guide.
Readers must manually navigate to the My Teamcenter Guide

and search for the subject.
Search Use the Find or Search options in Adobe Acrobat to search
the Teamcenter PDF collection using the Full Reader Search
feature available in Acrobat Reader. You can use this feature
when you open a PDF file from a local or network directory
that contains the complete Teamcenter PDF collection.
For more information about launching the PDF global search,
see Getting Started with Teamcenter.
Sharing links with Use the Email option in Adobe Acrobat to either e-mail a link to
other readers the help deliverable or to attach a PDF of the help deliverable
to the e-mail.

Chapter
3 Installing Teamcenter
How do I use TEM to install Teamcenter? . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
How do I generate the composite ID I need to get a Teamcenter license? . . . . . 3-2
Where do I find instructions on how to install and run the licensing for
Teamcenter? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
I have installed my corporate server on a UNIX machine. How do I generate a

Windows TC_DATA directory for two-tier clients to use? . . . . . . . . . . . . . . . 3-3

Chapter
3 Installing Teamcenter
How do I use TEM to install Teamcenter?

Teamcenter Environment Manager (TEM) is an installation wizard that installs,
upgrades, and updates Teamcenter configurations. At each step, TEM displays
a panel requesting information from you. Each panel provides online help that
describes the content of the panel. To view the online help for a given panel, click
Help.
To install a new version of Teamcenter, launch TEM from a Teamcenter software
distribution image (a disc or downloadable image) and select Install from the
Overview panel.
For more information, see the Teamcenter Environment Manager Help.

Chapter 3 Installing Teamcenter
How do I generate the composite ID I need to get a Teamcenter license?

A composite host ID (CID) is a unique identifier used as the host ID on the SERVER
line of the license file. It is distinguished from the default FlexNet host ID by the
COMPOSITE keyword. It is the host ID that associates a permanent license file
with a specific server. When the CID is used as the license server host ID, the
SERVER line reads as follows:
SERVER serverA COMPOSITE=37B5ED1AC61D 28000
To obtain a composite host ID for your license server, run the getcid utility on your
license server host. Download this utility from GTAC:
1. Open the GTAC Web site:
2. Click License Management®Download CID Utility.
3. On the Download CID Utility page, click NX and Other Products.
4. On the FTP site, click the directory corresponding to the platform type of your
license server, for example, wntx64.
5. On the resulting page, download the getcid.exe utility (Windows systems) or the
getcid utility (UNIX/Linux systems).
You must run the utility on the target license server (or on all three servers in a
redundant configuration). The output is a 12-digit hexadecimal number that is
the CID for that system. For example:
$ getcid.exe
The Siemens PLM Software licensing composite hostid is:
”COMPOSITE=37B5ED1AC61D”
After obtaining the CID, enter it into your customer record to generate a permanent
license file. You can enter your CID using either your WebKey account or by calling
your customer server representative. After the CID is entered into your customer
record, you are sent a permanent license file for you to install on your license server.
Note After you install the Siemens PLM License Server, the getcid utility is
available in your license server directory.
Where do I find instructions on how to install and run the licensing

for Teamcenter?
The Siemens PLM Software Common Licensing Server daemon, ugslmd, enforces
license usage. If you maintain installations of Teamcenter 10.1 and Teamcenter
2007.1 MP2 or earlier, you must maintain the old and new license daemons: ugslmd
for Teamcenter 10.1 and uglmd for versions of Teamcenter earlier than Teamcenter
2007.1 MP3.
For information about installing the Siemens PLM Software Common Licensing
Server daemon, see the appropriate server installation guide (for Windows or
UNIX/Linux) or the Upgrade Guide.

Installing Teamcenter
Teamcenter 10.1 employs named user licensing, which ties each user in the system
to an available license and ensures the total number of active licenses of each type in
the system is always less than or equal to the number of licenses purchased.
For more information about administering Teamcenter licensing, see the System
Administration Guide.
For more information about the Siemens PLM Software Common Licensing
Server, see the Siemens PLM Common Licensing User Guide in the
additional_documentation directory on the Teamcenter documentation
distribution image.
I have installed my corporate server on a UNIX machine. How do I

generate a Windows TC_DATA directory for two-tier clients to use?
If you have installed your corporate server on a UNIX machine, but need to generate
a Windows TC_DATA directory for your two-tier clients, create the TC_DATA
directory by performing a Foundation-only installation on a shared drive on a
Windows system. A full corporate server installation is not required.
To perform a Foundation-only installation, launch TEM and select Create a new
installation of the product from the Getting Started panel. As TEM progresses, do
not select any solutions to install. Expand the Base Install group and select the
Teamcenter Foundation feature.
Similarly, when TEM prompts for information regarding the Teamcenter database,
provide the information about the Teamcenter database in the UNIX installation.
Note The Foundation-only installation must be at the same version as the
corporate installation, down to the MP (maintenance pack) version. The
patch level can differ for the purposes of installation, but should be patched
to match before production use.

Chapter
4 Upgrading Teamcenter
How do I use TEM to upgrade Teamcenter? . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
What are type name collisions, and how do I find them in my database? . . . . . 4-2
Where do I find information about changes made to Teamcenter in previous

maintenance pack releases? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2

Chapter
4 Upgrading Teamcenter
How do I use TEM to upgrade Teamcenter?

Help.
To upgrade from an older version, launch TEM from a Teamcenter software
distribution image (a disc or downloadable image) and select Upgrade from the
Overview panel.
For more information about upgrading, see the Upgrade Guide.

Chapter 4 Upgrading Teamcenter
What are type name collisions, and how do I find them in my database?
A type name collision occurs when a type in your custom template has the same
name as one in a shipped Teamcenter template. A type name collision blocks an
Engineering Process Management database from being upgraded to Teamcenter
unified architecture. Operating a Teamcenter database with type name collisions can
result in data corruption, which is why upgrade is blocked when this issue is found.
You must resolve this issue by renaming your custom type object so that it no longer
collides with the identically named type in the shipped template.
For more information about resolving type name collisions from within Business
Modeler IDE, see the Business Modeler IDE Guide.
Teamcenter identifies type name collisions during upgrade from Engineering Process
Management to Teamcenter. However, you may want to pretest your database for
type name collisions and correct them, before attempting the upgrade.
Identify type name collisions before an upgrade with the Type Analysis Tool. This
is a stand-alone tool that inspects an Engineering Process Management database
for type name collisions. Run this tool on all Engineering Process Management
database sites when you are planning an upgrade and review the generated reports.
If any collisions are found, follow the instructions in the report to fix the issue before
upgrading to Teamcenter unified architecture.
Note When you use Teamcenter Environment Manager (TEM) to upgrade, the
upgrade sequence includes a panel asking you to validate your database for
any type name collisions. This step in the upgrade process ensures a type
name analysis is performed. Even if you have previously run the stand-alone
Type Analysis Tool, the collision test is executed in TEM during the upgrade.
TEM prompts you to enter the current release of your database, including
the maintenance pack level, if applicable. Do not guess at your full version
number, it distorts the analysis.
For more information about the Type Analysis Tool, see the Business Modeler IDE
Best Practices Guide on GTAC at the following URL:
http://support.industrysoftware.automation.siemens.com/docs/teamcenter/
Where do I find information about changes made to Teamcenter in

previous maintenance pack releases?
What’s New contains information about new features and functionality introduced in
Teamcenter 10.1.
For information about features and functionality added to maintenance packs
released prior Teamcenter 10.1 that were rolled into the current release, see the
Teamcenter Documentation page on the GTAC site at:

Chapter
5 Working with Business

Modeler IDE
How do I manage Teamcenter’s data model? . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
How do I create a new business object (previously known as types) in Teamcenter

10.1? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
How do I add properties to an existing business object in Teamcenter 10.1? . . 5-2
How do I hide item types so that when users create a new item, these types are not
seen? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
In Teamcenter 10.1, can I still add attributes to all my classes? . . . . . . . . . . . . 5-2

Chapter
5 Working with Business

Modeler IDE
How do I manage Teamcenter’s data model?

The Business Modeler IDE (Integrated Development Environment) is used for a
variety of tasks involved in the creation, configuration, and maintenance of the
Teamcenter data model.
Administrators and business analysts use Business Modeler IDE to:
• Add custom data model objects to extend the default Teamcenter data model.
Business Modeler IDE accomplishes this by separating your data model into its
own set of files that are kept apart from the standard data model, known as the
COTS (commercial off-the-shelf) data model.
Data model objects are collected into templates that contain the data
model for an application (also known as a solution). For example, the
foundation_template.xml file contains the data model for the Foundation
solution, the base Teamcenter application. When you use the Business Modeler
IDE to create a data model, your data model is rolled up into its own template.
For more information about how to create data model objects, see the Business
Modeler IDE Guide.
• Create custom code. If your organization produces software, you can use
Business Modeler IDE to write operations and generate the C++ boilerplate
code files. The Code Generation folder in the Extensions view is where you
do most of this work.
For more information about codeful customization, see the Business Modeler
IDE Guide.
How do I create a new business object (previously known as types)

in Teamcenter 10.1?
In Business Modeler IDE, create a new business object using the Business Objects
tab.
When you create a new business object, the system automatically updates the
schema, creating a new class of the same name.
For more information about creating business objects in Business Modeler IDE,
see the Business Modeler IDE Guide.

Chapter 5 Working with Business Modeler IDE
How do I add properties to an existing business object in Teamcenter

10.1?
In Business Modeler IDE, select the existing business object of the same name
from the Business Objects tab. Creating a new property on the business object
automatically adds an attribute of the same name to the corresponding class.
Note In Teamcenter, you work primarily with business objects and properties,
rather than working with classes and attributes.
You typically create a new property on the business object, which
automatically adds an attribute of the same name to the corresponding class,
rather than adding an attribute to the class.
You can still select a custom class and add an attribute.
For more information about working with custom classes, see the Business Modeler
IDE Guide.
How do I hide item types so that when users create a new item, these
types are not seen?
To hide item types from creation, make business object display rules. You must
create a rule for every item type that you want to hide from end users.
For more information, see the Business Modeler IDE Guide.
In Teamcenter 10.1, can I still add attributes to all my classes?

In Teamcenter 10.1, you can still add attributes to all your custom classes. You can
also add attributes to all classes shipped with Teamcenter, except the following:
POM_object POM_stub EffectivityMode

POM_class pom_session RoleInSchedule
POM_attribute AM_ACL NameField
POM_user AM_ACE NameRule
POM_group AM_named_tag ExtensionPoint
POM_member AM_privileges ExtensionDescriptor
POM_application AM_tree Extension
POM_imc User TypeBMOperation
POM_accessor Group PropertyBMOperation
POM_system_class GroupMember BMOperation
POM_dd Role BusinessRule
POM_data_manager ImanType TC_Preferences
POM_site_config GroupSecurityNamedTag DatasetType

Chapter
6 Administering Teamcenter
How do I use TEM to perform maintenance tasks? . . . . . . . . . . . . . . . . . . . . . 6-1
How do I clean my database? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2
What is the transient volume used for? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2
The transient volume definition is missing from the FMS configuration file. How can
I fix this? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3
Why don’t I see the changes that someone else made to an access control list? . . 6-3
I’ve found some preferences in the Java source code, but I cannot find documentation
on them. What do the preferences do? . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4
What is the difference between Audit Manager and Subscription Monitor? . . . 6-4
I restricted copy privileges, but users can still copy the object. Why? . . . . . . . . 6-5

Chapter
6 Administering Teamcenter
How do I use TEM to perform maintenance tasks?

Help.
To perform maintenance on an existing installation of Teamcenter, launch TEM
from Teamcenter’s home directory and select Configuration Manager from the
Maintenance panel.
For more information, see the Teamcenter Environment Manager Help.

Chapter 6 Administering Teamcenter
How do I clean my database?

Use the following command line utilities to clean your Teamcenter database. Click
the link for more information about each utility.
Utility Description
Clears dead process locks from the
clearlocks
database.
Repairs corrupted datasets and removes
dataset_cleanup
orphaned revision anchors.
Removes (purges) operating system
purge_volumes files that represent deleted Teamcenter
objects.
Allows you to view detailed information
about Teamcenter volumes and to
review_volumes
remove unreferenced operating system
files from these volumes.
Finds all corrupted Change Viewer
tasks, jobs, and other associated internal
verify_tasks
task model objects in order to delete
them from the database.
What is the transient volume used for?

Transient volumes are the mechanism used to transfer data either generated by or
required by the business logic server (TcServer). For example, transient volumes
are used during PLM XML export. The file is generated by the TcServer process
and written to a temporary area, the transient volume. A ticket for the file in the
transient volume is sent to the client that uses the ticket to retrieve the file.
In a four-tier configuration, each business logic or enterprise tier server requires a
transient volume. It is best practice to have a local FSC on each server to service the
local transient volume.
Client access to files within a transient volume is dependent on whether clients are
running in two-tier or four-tier. The tickets generated for client file access specify
either two-tier, or four-tier depending on how the client is connected to the TcServer.
• Two-tier transient volume file access
Clients in a two-tier environment can read and write to the same physical
location as the TcServer since they are on the same machine. In this case, the
FCC process reads files directly from the transient volume location.
File operations need no special fmsmaster.xml configuration because no FSCs
are required to transport the files, and thus no fmsmaster.xml configuration is
required.
• Four-tier transient volume file access

Clients in a four-tier environment do not have direct access to the transient
volume location and must use the FMS system to retrieve files. Thus, four-tier
transient file operations require transient volumes to be configured in the

Administering Teamcenter
fmsmaster.xml configuration file. Transient volumes are declared under an

FSC with direct access to the files, much like the TcServer process. The FSCs
that host transient volumes usually run on the same hosts, under the same
userids, as the TcServer process.
On the server side, two-tier or four-tier configuration makes no difference to how

the TcServer process assesses the transient volume. For more information on
configuring and administering transient volumes, see the System Administration
Guide.
The transient volume definition is missing from the FMS configuration

file. How can I fix this?
A transient volume’s identity is a unique value that is based on the site ID and
several of the transient volume preferences. This identity is called the transient
volume ID. Although a given tcserver only knows about a single logical transient
volume, other parts of the system (such as FMS) may need to work with more than
one transient volume and therefore transient volumes must be identifiable.
The transient volume ID listed in the FMS master configuration file is determined
by a combination of the site ID, the value of the Transient_Volume_RootDir
preference, and the value of the Transient_Volume_Installation_Location
environment variable/preference. Modifying any of these values changes the
transient volume ID, in which case you must manually modify the transient volume
ID listed in the master configuration file.
Note tc_profilevars sets the Transient_Volume_Installation_Location
environment variable to the computer/host name.
You can obtain a list of current volume definitions in the database by running the
backup_xmlinfo utility to generate the backup.xml file. The utility generates
transient volume information for the context in which the utility is being run (the
current tcserver context). All other server pools or hosts with transient volumes
are not identified.
For more information on modifying the transient volume ID, for the current server
context or a different server context, see the System Administration Guide.
Why don’t I see the changes that someone else made to an access
control list?
If an access control list (ACL) is modified by a user, other users who are logged on at
the same time are not affected by the updated ACL until they log off and log on again.
When an access control list (ACL) is modified by an administrator, users who are
logged on at the same time are not affected by the updated ACL until they log off and
log on again, or until the administrator recycles the server to pick up the changes.
For more information about using ACLs, see the Access Manager Guide.
For more information about using the Restart Warm Servers button, see the System

Chapter 6 Administering Teamcenter
I’ve found some preferences in the Java source code, but I cannot find
documentation on them. What do the preferences do?
Teamcenter uses undocumented preferences that are intended for use only by
Teamcenter development. These preferences do not display in the Teamcenter
interface or in the shipped preferences file. They can only be found by searching
the source code.
Teamcenter license agreements prohibit reverse engineering of any kind, including
works derived from decompiling Teamcenter object code or byte code to derive any
form of the original source code. Always access preferences using the Options dialog
box in the interface or the shipped tc_preferences.xml file. Internal preferences
are not supported. There is no obligation to fix or answer incident or problem reports
concerning their usage.
For more information about working with preference options and with the preference
XML file, see the Preferences and Environment Variables Reference.
Note Siemens PLM Software reserves the right to change or remove internal
preferences at any time with no advance warning. Undocumented features,
preferences, APIs and all Teamcenter source code are Siemens PLM
Software proprietary intellectual property.
Typically, if a preference is not documented, it is an internal preference. For more

information, contact GTAC at:
What is the difference between Audit Manager and Subscription

Monitor?
Administrators use Audit Manager to manage audit logs and Subscription Monitor
to manage subscriptions.
End users view audit logs to see the history of actions performed on objects and
use subscriptions to be notified when data is modified by another user or when the
release status of an item revision changes.
Audit logs document events that occur to objects in Teamcenter. Administrators can
create audit logs for virtually any event that occurs to a Teamcenter object. For
example, audit logs can be created to track when:
• Specified item types are checked out.
• Specified forms are created, modified, or deleted.
• Users approve specified target types in specified workflows.
• The Complete action on any workflow task fails.
• Access requests are denied.
Administrators create audit definition objects for each object/event to be tracked.

Audit logs can then be searched and viewed from Teamcenter.

Administering Teamcenter
For more information about creating audit definition objects and managing audit
logs, see the Audit Manager Guide.
Subscriptions are created by end users. Subscriptions are requests to be notified
when specified events occur to specified objects. For example, a user may subscribe
to be notified when:
• Any change is made to a specific type of document revision.
• A specific assembly is checked out.
• A Word document is added as a dataset to a specific type of item revision.
• Status is changed on specified parts.
Users are notified by Teamcenter mail when the specified events occur on the
specified objects.
For more information about creating subscriptions, see the My Teamcenter Guide.
Administrators use Subscription Monitor to manage all the different subscriptions
created by users. The application is used to generate subscription reports and
to manage subscription tables.
For more information about using Subscription Monitor, see the Subscription
Monitor Guide.
I restricted copy privileges, but users can still copy the object. Why?
The Access Manager Copy privilege controls the privilege to copy an object as a
new object using commands, such as Save As or Revise. It still allows users to copy
and paste an object as a reference, with no new object created.

Chapter
7 Managing FMS
What is FMS? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1
What is TCCS and how is it related to FCC? . . . . . . . . . . . . . . . . . . . . . . . . . 7-2
When do I need to restart the FCC? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2
How do I restart an FCC process? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2
How do I stop an FCC? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3
How do I reset a user’s FCC environment? . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5
Why am I getting errors after modifying the FCC configuration? . . . . . . . . . . . 7-5
Why am I getting errors after removing the FCC? . . . . . . . . . . . . . . . . . . . . . 7-6
Why am I getting errors after using the kill command to stop FCC processes? . . 7-6

Chapter
7 Managing FMS
What is FMS?
File Management System (FMS) is a file storage, caching, distribution, and
access system. FMS provides global, secure, high performance, and scalable file
management.
Use FMS to centralize data storage volumes on reliable backup file servers, while
keeping data close to users in shared data caches. This enables centralized storage
and wide distribution of file assets to the needed locations within a single standard
file management system.
FMS consists of two primary components:
• FMS server cache (FSC)
Provides a shared, secure, server-level cache. It uploads and downloads files to
other FSCs and to client caches.
An FSC can provide one or more modes of behavior, where each mode manages a
type of data including volume files, cache files, transient files, and configuration
files. A particular FSC can perform any or all of these functions simultaneously
depending on your FMS configuration. All FSCs provide at least one mode in
a properly configured FSC topology.
You define configuration, volume, and transient file modes explicitly in the
FMS configuration files using XML statements. Cache server functionality is
installed on each FSC but is only used if the FSC does not have direct access to
volume files.
• FMS client cache (FCC)

Provides a private user-level cache, just as Web browsers provide a read file
cache. The FCC provides a high-performance cache for both downloaded and
uploaded files. The FCC provides proxy interfaces to client programs and
connectivity to the server caches and volumes.
Any files captured by the FCC do not change, for either download or upload,
and for either whole files or partial files. All file copies and file segment copies
are identical throughout the system and never updated. New file versions are
checked into the system with a new GUID, but a file with an existing GUID in
the FMS system never changes. Therefore, there are no issues with file change
or cache consistency.
FCCs also provide access to the transient volume for the business server in
a Teamcenter two-tier configuration. The business server writes or reads
temporary files directly to a disk directory, and the rich clients access those files
using the standard FCC interfaces. This provides client independence from the

Chapter 7 Managing FMS
system configuration and ensures that client programs operate the same in both
two-tier and four-tier mode for file access functions.
What is TCCS and how is it related to FCC?

As of Teamcenter 9, the FCC runs within the Teamcenter client communication
system (TCCS) module.
TCCS is a container application that also includes the Teamcenter server proxy
(TcServerProxy) and the Teamcenter model event manager (TcMEM) services as
well as the FCC. All of the TCCS services begin and terminate together with the
container application.
Starting and stopping the FCC requires that you start and stop the entire TCCS,
including the TcServerProxy and TcMEM processes.
For information about managing TCCS, see the System Administration Guide.
When do I need to restart the FCC?

Restart the FCC when:
• You changed FCC elements that require a restart.
For information about which FCC elements require a restart, see the System
• A TCCS/FCC process executing in memory is not responding to pipe connection

attempts. For example, when all of the following events occur:
o The $FMS_HOME/bin/fccstat -status command reports that the FCC
is offline.
o The $FMS_HOME/bin/fccstat -start command cannot start the FCC.
o The $FMS_HOME/startfcc.bat reports that the FCC cache is locked.
• The TCCS container needs restarting for non-FCC reasons.
For more information, see How do I restart an FCC process?
How do I restart an FCC process?

1. Close all client applications.
2. Wait 10 seconds.
3. Run $FMS_HOME/bin/fccstat -restart.
If this method does not work, stop and restart the FCC:
1. Stop the FCC.
For more information, see How do I stop an FCC?.

Managing FMS
2. Run $FMS_HOME/bin/fccstat -start.
For more information about when and why to restart an FCC, see the System
How do I stop an FCC?

Whenever you stop an FCC, it is important that the shutdown process is as clean as
possible. You may want to stop an FCC because:
• It is no longer needed.
• You need to stop and restart the FCC to receive new configuration information.
For more information about when and why to restart an FCC, see the System
Regardless of why you stop an FCC, remember that the FCC runs within the TCCS
container process. Stopping an FCC also stops the TcServerProxy and TcMEM
processes.
Note Siemens PLM Software does not recommend using the operating system
kill command or the Windows Task Manager to stop an FCC unless
safer methods have failed. Doing so can cause issues with the FMS
fast cache, the FCC cache lock, the TCCS process lock, and any active
FCC/TcServerProxy/TcMEM transactions.
Before stopping an FCC, close all client applications and wait 10 seconds.
The following methods for stopping an FCC are listed in the order by which they
reduce the risk of corrupting the cache or creating a stuck lock file. If after stopping
an FCC, it does not properly restart, reset the user’s FCC environment.
For more information, see How do I reset a user’s FCC environment?
Method 1
• Run $FMS_HOME/bin/fccstat -stop.
This method stops an FCC if it is idle.

The system confirms that the user has shut down all the attached client
processes before stopping the FCC.
If nonidle clients are connected to the FCC, a message appears and the FCC is
not stopped. If you receive this message, confirm that all client applications are
disconnected from FCC/TCCS, wait 10 seconds, and retry.
Note A client is nonidle if it holds an open FCC file handle, an open segment
cache handle, or an open pipe connection that has made a request within
the past 5 to 10 seconds.
This method is effective 90 percent of the time and results in the cleanest
possible shutdown. The FCC can be restarted afterward with no data loss.
Method 2
• Run $FMS_HOME/bin/fccstat -kill.

This method stops an FCC if it is idle or nonidle, as long as it is responsive to

pipe commands.
The system does not confirm that the user has shut down all the attached client
processes before stopping the FCC. The system does not display a message that
other client applications are connected.
Any transactions in progress at the time the FCC is terminated may fail. This
can have a negative effect on the connected client applications.
This method is effective 99 percent of the time. The FCC can typically be
restarted afterward with no data loss.
Method 3
If a TCCS/FCC instance is not responsive to FCC pipe commands, it may report
FCC Offline even though the TCCS/FCC process is running. In this case, use
the tspstat or tcmemstat utility to stop the shared TCCS process.
Method 4 (only if TCCS/FCC running in foreground)
• Press Ctrl+C in the FCC foreground window.
The foreground window is available from the interface only if TCCS/FCC is
running in a visible command prompt window or shell. (This is not usually
the case.)
• Alternatively, close the TCCS command prompt window (Windows only).

Note If the FCC is running in a hidden window, and you have system
tools access, you can locate the hidden FCC window and send it a
WM_CLOSE message (Windows only).
This method is highly effective and usually results in a clean shutdown of the
FCC.
Method 5 (UNIX only)
• Run the operating system kill command without the -9 option.
This method stops an FCC if it is idle or nonidle, even when it is not responsive
to pipe commands.
This method stops the FCC as cleanly as possible. The effect is similar to method
2, but it is possible that file handles become stuck or that cache states are lost.
Method 6 (UNIX only)
• Run the operating system kill command with the -9 option.
This method performs a hard stop on the FCC. Usually, the contents of the FCC
fast cache (segment cache) are lost. Occasionally, the FCC lock file becomes stuck.
Method 7 (Windows only)
• From the Task Manager, select the user’s FCC process and click End
Process.
This method performs a hard stop on the FCC. Usually, the contents of the FCC
fast cache (segment cache) are lost. Occasionally, the FCC lock file becomes stuck.

Managing FMS
How do I reset a user’s FCC environment?

1. Stop all client applications that use FMS.
2. Stop the FCC process.

For more information, see How do I stop an FCC?
3. Reset the user’s system environment using one of the following methods:
• On a single-user machine, restart (or shut down and reboot) the operating
system.
• On a multiuser machine, log out and log back on.

If you cannot restart the FCC after performing step 3 because of locked file
handles, warn other users that the machine must be rebooted, and then
reboot the operating system.
4. Remove the following files from the user’s FCC cache directory. Corruption in
any of these files can prevent the FCC from restarting:
• fcc.lck
• fms.hsh
• fms.mf
• fms.set
• All files beginning with fms.ext (cache extent files)
Why am I getting errors after modifying the FCC configuration?

The following list discusses typical FCC modifications which, if the FMS
documentation in the Help Library is not followed, result in errors:
• Modified a routing or connection element in the fcc.xml file, and then did not
run the $FMS_HOME/bin/fccstat -reconfig command.
Changes made in the local fcc.xml file while the FCC is processing commands
for one or more applications require a manual FCC reconfiguration.
For more information about manual reconfiguration of an FCC, see the System
• Modified an FCC element that required an FCC restart. The effects of the
change are not applied until the FCC is restarted.
For a list of the FCC elements that require a manual restart, see the System
• Improperly shutting down an FCC may generate cache or lock errors upon
restart.
For information about appropriate shutdown methods, see How do I stop an FCC?
Clear these errors by restarting the user’s FCC environment.

Other FCC modifications incompletely applied may generate other errors. Most error
messages provide suggestions for how to correct the problem. Check the FCC log and
Teamcenter system logs for error messages.
For more information about accessing log files, see the System Administration Guide.
Why am I getting errors after removing the FCC?

If you remove the cache files, the cache is empty when FCC restarts. This can
generate errors in two areas:
• You cannot create new cache files on the local hard disk due to permission
settings, lack of disk space, or configuration mistakes.
Fixing the underlying issue typically resolves the FCC error.
• You cannot repopulate the cache because the FMS system from which the data
originated is not accessible on the network.
If the data is no longer available from the PLM volumes, you must find a new
data source. Fixing the underlying network access problem typically resolves
the FCC error.
Why am I getting errors after using the kill command to stop FCC
processes?
Siemens PLM Software does not recommend using the operating system kill
command or the Windows Task Manager to stop an FCC unless safer methods have
failed. Doing so can cause issues with the FMS fast cache, the FCC cache lock,
and active FCC transactions.
For recommended methods of stopping an FCC, see How do I stop an FCC?
If you use one of these methods to stop an FCC and receive errors, you must reset
the user’s FCC environment.

Chapter
8 Customizing Teamcenter
How do I customize Teamcenter? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1
How do I change page layout without writing code? . . . . . . . . . . . . . . . . . . . . 8-1
How do I change menus? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1
How can I change the icons in the rich client interface? . . . . . . . . . . . . . . . . . 8-2
How can I change the icons in the thin client interface? . . . . . . . . . . . . . . . . . 8-2
How do I create a form for the rich client? . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3
What is the process for migrating my Engineering Process Management rich client
Java interface code into the Eclipse-based Teamcenter 10.1 interface? . . . . . 8-3

Chapter
8 Customizing Teamcenter
How do I customize Teamcenter?

Teamcenter is based on a client-server architecture. Both the client and server
layers can be customized. The client is the user interface (UI) layer and is built
and customized using the Java language (rich client) and JavaScript (thin client).
The server layer can be customized using the Integration Toolkit (ITK), the C++
programming language, and service-oriented architecture.
For information about customizing the server layer, see the Server Customization
Programmer’s Guide.
Because the rich client is based on Eclipse, your customizations have access to all
Eclipse extension points and OSGi services. They can also use Teamcenter-developed
customization techniques. The basic rich client customization technique is to create
a plug-in that contains the customizations and deploy the custom plug-in to the rich
client installation. To effectively customize the rich client, you must be comfortable
working with Eclipse.
The thin client is a Web-based interface, providing access to your data using a
Web browser. Users have access to the same Teamcenter server and data as the
rich client uses. No thin client software is required on a Teamcenter client. When
customizing the thin client, put as much of your customization into the core code
and as little into the user interface as possible. If your installation uses multiple
interfaces, this minimizes duplication. Also, use simpler configuration and tailoring
techniques before using custom code.
For information about customizing the rich client and the thin client, see the Client
Customization Programmer’s Guide.
How do I change page layout without writing code?

You can change the page layout in both the rich client and thin client without
writing code by editing XML rendering style sheets. You can use style sheets to
change the layout of pages such as forms, the Properties dialog box, the Summary
view, and the creation wizard dialog boxes. Style sheets are XML documents stored
in XMLRenderingStylesheet datasets on the server.
For more information, see the Client Customization Programmer’s Guide.
How do I change menus?

You can remove or add menus in Teamcenter:
• Remove menus

Chapter 8 Customizing Teamcenter
Removing menus is known as command suppression. Use the Command

Suppression application to remove menus from the user interface. You can also
use business object display rules to hide objects from menus.
For more information, see the Application Administration Guide, the Client
Customization Programmer’s Guide, and the Business Modeler IDE Guide.
• Add menus
You can add menus to the user interface using different methods. For example,
you can use Eclipse to add a menu to the rich client or edit XML files to add a
menu to the thin client.
How can I change the icons in the rich client interface?

Icons are images placed on business object instances to identify them in the user
interface. To add or change icons on business object types, use the Fnd0Icon business
object constant in the Business Modeler IDE. The icon definitions are placed on the
server and used by the rich client. Previously, you had to perform a customization to
add the icons. Now it is done entirely through the Business Modeler IDE.
You can change the default icon for an existing business object or add an icon to
a newly created business object. You can also decorate the icon with images to
designate the business object’s state (for example, status, remote, checked out,
process, and so on).
For more information, see the Business Modeler IDE Guide.
Note You must use a different method to change the business object icons on the
thin client.
For instructions about changing business object icons in the thin client, see
the Client Customization Programmer’s Guide
How can I change the icons in the thin client interface?

In the thin client, business object icons are named and displayed by business
objects. You can change the icon displayed for a business object in the
staging_location/webapp_root/typeicons directory.
When you add a custom business object to Teamcenter, also add a business object
icon for it. You must name the icon with the same exact, case-sensitive name of the
business object. If the business object has spaces in its name, you must use an
underscore in the icon name for each space.
You can reuse copies of the icon for different business objects. If Teamcenter cannot
find the business object icon, it automatically loads the class icon. However, this
prevents caching, which slows performance, and should be avoided.

Customizing Teamcenter
Note You must use a different method to change the business object icons on the
rich client.
For instructions about changing business object icons in the rich client, see
the Business Modeler IDE Guide.
How do I create a form for the rich client?

A form in the rich client is a page that displays object properties. You may want to
create your own custom form to display only certain properties.
There are four ways you can create a form for the rich client:
• Use XML style sheets
Do this by modifying an existing XML style sheet or creating a new one. The
style sheet is an XML document stored as a XMLRenderingStylesheet
dataset. When a style sheet is registered for a specific object type or form, it
defines the display of the object or form properties. Registration information is
stored in the site preferences.
The thin client also uses the XML style sheets, so modifying them may change
the form’s appearance in the both the rich client and thin client.
• Use JavaBeans
Do this by launching Eclipse and creating a new JPanel component. Then add
Property bean components to the new JPanel component.
• Extend the abstract class

Do this by creating a form type, extending the schema, creating the form panel,
and registering the panel with the rich client.
• Create an automatic form

Do this by creating a form type and extending the schema.
For instructions, see the Client Customization Programmer’s Guide.
What is the process for migrating my Engineering Process

Management rich client Java interface code into the Eclipse-based
Teamcenter 10.1 interface?
If you customized the rich client in previous versions of Teamcenter or Engineering
Process Management, you may have to update your customizations to work with the
current version. For example:
• Place customizations into Eclipse plug-ins if they are not already.
• Some Java API classes, methods, and constructors are deprecated or obsolete
and should be replaced.
For more information about deprecated and obsolete API, see the Teamcenter
10.1 Release Bulletin.

Chapter 8 Customizing Teamcenter
• Some applications have their own plug-in. Open the TC_ROOT\portal\plugins

directory to see which applications have their own plug-in.
For more information about updating your Java customizations, see the Client
Customization Programmer’s Guide.

Chapter
9 Working with the rich client
What users should use the rich client? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1
What can I do to improve my startup performance? . . . . . . . . . . . . . . . . . . . . 9-2
Will deleting my cache improve performance? . . . . . . . . . . . . . . . . . . . . . . . . 9-3
What are perspectives and views? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-4
What happened to applications? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-4
I see different Search boxes. Do they all search the same way? . . . . . . . . . . . . 9-5
How do I delegate signoff responsibility? . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-7
I meant to delegate my signoff, but instead I changed the responsible party. How do
I correct this? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-9
How do I view access privileges set for another user on an object? . . . . . . . . . . 9-10

Chapter
9 Working with the rich client
What users should use the rich client?

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.
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.
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.
Most administrative tasks are accomplished in the various rich client administrative
applications, such as Access Manager, Organization, and Workflow Designer.
For more information on using these administrative applications, see the Access
Manager Guide, Organization Guide, and Workflow Designer Guide, respectively.
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.
Most user activities are accomplished in the My Teamcenter application, but users
may also regularly use other applications, such as Structure Manager or Relation
Browser, and commonly used views, such as Search, Search Results, JT Preview,
and Image Thumbnail Preview.
For more information about using the My Teamcenter application, see the My
Teamcenter Guide.

Chapter 9 Working with the rich client
What can I do to improve my startup performance?

The checked-out symbol displays to the right of the Teamcenter object. It is a
quick indicator of whether the object is checked out. When an object is checked
out, another user has exclusive access to it, preventing you from making changes
to the object until it is checked back in.
However, displaying this symbol for every object in a very large assembly (5,000 or
more objects) can degrade performance. Turning off the display of this symbol in
tree views (assembly trees, attachment trees, and so forth) improves performance.
Turn off the display of the symbol by setting the TC_show_checkedout_icon
preference to FALSE.
Checkout status always appears in the Details view, regardless of how you set the
display of the checked-out symbol. If you turn off the display of the checked-out
symbol, refer to the Checked Out column in this view to determine the check out
status of objects.
To turn off the display of the checked-out symbol:

1. Choose Edit→Options to display the Options dialog box.
2. Click the Index tab in the bottom left of the dialog box to display the Preferences
pane.

Working with the rich client
3. In the Search on preference name box, type TC_show_checkedout_icon. The

preference displays under Preferences List.
4. Select the preference from the list. In the Current values box, change the value
to FALSE.
5. Click Modify for the change in value to take effect.
6. Click Cancel to close the dialog box.
7. Log off your session. Log on again to see the change take effect. The symbol no
longer appears to the right of objects in tree views.
For more information setting preferences, see the Rich Client Interface Guide.
Will deleting my cache improve performance?

Yes, deleting your rich client cache can improve Teamcenter performance.
The Teamcenter rich client uses persistent cached information that is local and
specific to each user. The cache includes information about session windows, current
plug-ins, system configuration, dialogs, display preferences, and so on, and it
improves performance and tailors the user experience.
However, in the following situations, the cache can degrade performance:
• When a plug-in is updated with new or modified code, the cached information
does not match the new or modified plug-in, and the client may not work
properly. Remove the cache to let the rich client refresh the plug-in information.

• When a user opens thousands of items, the current application can become
slow to respond. The next time that user logs on to the rich client, the system
attempts to open the previously accessed items and can take a long time to
complete the startup. Remove the cache to work around this situation.
In these situations, removing the cache is recommended. This information can be

safely removed because the client regenerates any needed information, returning the
client to its state prior to the users initial login.
For information about removing the cache, see Rich Client Interface Guide.
What are perspectives and views?

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.
Note 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 is an
automatic alphabetization that gives precedence to uppercase letters over
lowercase letters. The order of presentation may vary at your site.
What happened to applications?

In Teamcenter 10.1, the rich client provides a single perspective and view for over
forty of the applications that were provided in Teamcenter 2007. (A few other
applications now contain multiple views by default.) The client is now configurable
on a per-user basis with user-based client configuration persistent between sessions.
You can:
• Work with existing applications in the new perspectives exactly as did in
previous Teamcenter versions.
• Include additional views in a perspective.
• Save provided perspectives in new configurations.
• Create new perspectives based on provided perspectives with views removed

or added.
• Display different views of the same data or rearrange views to display multiple
sets of information simultaneously.

For more information about rich client perspectives, see the Rich Client Interface
Guide.
I see different Search boxes. Do they all search the same way?
Teamcenter provides three different search mechanisms. You can use any or all of
the search mechanisms in conjunction with each other.
By default, all three mechanisms are enabled. You can modify the behavior of each
mechanism. Configuration is required to make full use of Advanced Search.
Quick Search
Display Displays a single-field search form, providing a quick input

method for users to search the Teamcenter database.
Behavior Generates searches based on a single criteria (such as item
ID, keyword, item name, or dataset name) selected from the
Perform Search menu. Administrators can set preferences to
determine which criteria display in this menu.
Use Provides quick searching of items and datasets. It requires
users to know the item ID or name, or the dataset name.
Quick searches are limited to a single user. They cannot be
stored by the user, nor shared with other users.
Availability This search mechanism is available by default in both rich
client and thin client. No configuration is required to use this
search with its default search queries. However, you can add
custom queries.
Configuration • Configure which objects display in the selection list (Item
options ID, Keyword Search, and so on).
• Implement keyword search functionality by configuring

and starting full text search.
For more information, see the Application Administration
Guide.
• Create custom queries.
Setup For information about configuring this search mechanism, see

the Application Administration Guide.
Advanced Search

Display Displays preconfigured search forms allowing users to specify

multiple search criteria relevant to the type of information
or object being sought.
Behavior Generates searches based on preconfigured search forms. The
search forms are derived from search queries. Hundreds of
search queries are shipped with Teamcenter. You can create
additional search queries (also called saved searches) using
Query Builder.
Use Distributes in-depth, customized search forms throughout the
site and/or throughout a global enterprise.
You can also incorporate full-text search capability into the
search forms, allowing users to search for datasets by attribute
value and search dataset files by keyword.
Building query definitions requires knowledge of the
Teamcenter POM (persistent object manager) schema, which
is a hierarchical arrangement of classes, subclasses, and
attributes. Particularly when including reference attributes
in the query.
Availability Advanced searches are available by default in both rich client
and thin client. No configuration is required for this search
functionality to display. However, making full use of this
search method requires creating search queries in Query
Builder and installing and configuring the Autonomy full text
search engine.
Configuration • Configure full-text search.
• Configure indexing.
• Create custom queries.
Setup For information about implementing and configuring this

search mechanism, see the Application Administration Guide.

Simple Search
Display Displays the available properties for the selected business

object, allowing users to create searches without an in-depth
knowledge of the Teamcenter POM schema. Only the relevant
properties for the selected object display. Users do not need
to understand the placement of attributes within the POM
schema.
Behavior Generates searches based on one or more property values of
selected business objects.
Users select an object type, and then build a search form by
selecting properties and specifying criteria.
Use Provides users a tool for creating their own customized
searches to search the local Teamcenter database, without a
strong knowledge of the POM schema.
These searches are limited to a single user. They cannot be
stored by the user, nor shared with other users.
Availability Simple searches are available in rich client only. It displays
by default. No configuration is required for this search
functionality, though you can set preferences to modify its
behavior.
Configuration • Modify default display settings.
• Filter the business object types available for search.
Setup For information about configuring this search mechanism, see

the Application Administration Guide.
How do I delegate signoff responsibility?

Signoff tasks are one of the most common tasks delivered to a user’s worklist. Signoff
tasks require users to review the attached target object, decide whether or not to
approve the contents of the target object, and indicate their decision by selecting
Approve or Reject in the Decision column in the Perform Signoff pane.

Users often want to transfer this signoff responsibility to another user. However,
users new to Teamcenter sometimes confuse delegating signoff responsibility with
reassigning task ownership.
To delegate your signoff responsibility, do not reassign the task.
Delegate your signoff responsibility by clicking your own user name in the
User-Group/Role column in the Perform Signoff pane. When the Delegate signoff
dialog box appears, expand the Organization tree to select the user to whom you
want to transfer your signoff responsibility.
Link Dialog box
For more information about your options for completing the perform-signoffs task,
see the My Teamcenter Guide.
There is an important distinction between signoff team members (listed in the
User-Group/Role column) and the responsible party. In the following graphic,
Short, Don is the responsible party. As the responsible party, Don has permission
to demote, promote, and delete the Review task and/or either of its two subtasks
(select-signoff-team and perform-signoffs).

Link Dialog box
Clicking the name next to the Responsible Party box displays the Assign
Responsible Party dialog box. Selecting a different user name within this dialog
box transfers all of Don’s permissions to the selected user. Users seldom need to
reassign the responsible party.
For more information about how to proceed if you have already mistakenly
reassigned the task to a new responsible party, see I meant to delegate my signoff,
but instead I changed the responsible party. How do I correct this?
I meant to delegate my signoff, but instead I changed the responsible

party. How do I correct this?
Users often want to transfer their signoff responsibility to another user. However,
users new to Teamcenter sometimes confuse delegating signoff responsibility with
reassigning task ownership.
For more information about the distinction between delegating signoff responsibility
and reassigning the responsibility party, see How do I delegate signoff responsibility?.
If you have already mistakenly reassigned the responsible party by clicking the
name to the right of the Responsible Party box, and then selecting a new name
from the Assign Responsible Party dialog box, you have transferred the right to
promote, demote, and delete the Review task and/or either of its two subtasks
(select-signoff-team and perform-signoffs) away from the original responsible party.

Link Dialog box
If it was your intention to delegate your signoff responsibility, rather than reassign
the responsible party, you must first reinstate the correct responsible party, and then
correctly delegate your signoff responsibility.
To reinstate the responsible party:
1. Click the name to the right of the Responsible Party box.
2. In the Assign Responsible Party dialog box, expand the Organization tree to
the group and role of the original responsible party. Select the name of the
original responsible party.
3. Click OK.
The dialog box closes, and the name to the right of the Responsible Party box
returns to the original responsible party.
To correctly delegate your signoff responsibility, see How do I delegate signoff

responsibility?
How do I view access privileges set for another user on an object?

You can view the access privileges set for another user on an object and see the
access control lists (ACLs) and Access Manager rules that define the privileges.
1. In My Teamcenter, select the object affected by the access rule and choose
View→Access.

Tip You can also right-click the object and choose Access from the shortcut
menu, or click on the toolbar.
The Access dialog box appears, showing your privileges on the selected object.
2. From the User, Group, and Role list, select another user, group, or role.
3. In the lower right corner of the Access dialog box, click .

The ACL Control List dialog box appears.

4. (Optional) Instead of just viewing this list, you can also return to the Access
dialog box and click the Extra Protection button to show the rules that apply
to a privilege being granted or denied.
The Extra Protection dialog box appears.
From this dialog box, you can easily see which branches in the Access Manager
rule tree were effective when evaluating each privilege.

Chapter
10 Working with the thin client
What users should use the thin client? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1
How does the thin client differ from the rich client? . . . . . . . . . . . . . . . . . . . . 10-2
What Teamcenter functionality is available in the thin client? . . . . . . . . . . . . 10-3
What Teamcenter functionality is not available in the thin client? . . . . . . . . . . 10-3
Many commands are suppressed in the thin client, but are not listed as
suppressed in the Command Suppression application. How do I display these
commands? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-4

Chapter
10 Working with the thin client
What users should use the thin client?

The Teamcenter thin client is a Web-browser 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.
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. The following table lists the applications available in the thin client.
Button Application name Description

My Teamcenter 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.
Structure Manager Lets you create, edit, and configure
product structures.
Systems Engineering Lets you identify, allocate, and maintain
product requirements.
Manufacturing Lets you view a process plan that you
Process Planner 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.
Classification Lets you classify and retrieve your
product data based on predefined
attribute values.
Adhoc Design Context Lets you configure assemblies, and
then send them in PLM XML format
to stand-alone Teamcenter’s lifecycle
visualization mockup or NX to view.

Chapter 10 Working with the thin client
Button Application name Description

Design Context 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.
Schedule Manager 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.
How does the thin client differ from the rich client?
Rich client • Requires Teamcenter client software installed on the local
(client) computer.
• Communicates with the Teamcenter server only as needed,

performing a variety of processing tasks locally.
• Displays the date and time of an action based on the

time zone identified on the system where the rich client
is installed.
o Interprets dates and times entered by the user based
on the time zone identified on the system where the
rich client is installed.
o Interprets search criteria entered by the user in the

rich client time zone.
• Supports a broader set of Teamcenter administrative and

user tasks.

Working with the thin client
Thin client • Does not require Teamcenter client software installed on

the local (client) computer.
• Communicates with the Teamcenter server for most

interactions, performing almost all processing tasks on the
Teamcenter server.
• Displays the date and time of an action based on the time

zone in effect on the server.
Interprets dates and times entered by the user, including
search criteria, based on the time zone in effect on the
server.
• Supports a subset of applications and Teamcenter user

tasks, but does not support many administrative tasks.
What Teamcenter functionality is available in the thin client?

Many commonly performed user tasks can be performed using the thin client,
including:
• Creating and managing basic data such as items, item revisions, datasets,
documents, vendor data, and other business objects.
• Participating in workflows.
• Searching in Teamcenter and managing reports.
• Navigating structures such as projects, occurrence groups, and structure

contexts.
• Creating and managing change objects, product structures, manufacturing

data, classification data, requirements, DesignContext data, schedule data,
collaboration context data, and electromechanical structures.
• Viewing audit logs.
• Viewing graphic data using embedded visualization.
• Importing and exporting data.
What Teamcenter functionality is not available in the thin client?

Administration and configuration capabilities are typically not available in the thin
client. Administrative applications not available through thin client include:
• Access Manager
• Audit Manager
• Organization
• Program

Chapter 10 Working with the thin client
• Volume Management
Many commands are suppressed in the thin client, but are not listed
as suppressed in the Command Suppression application. How do I
display these commands?
Administrators can suppress menu commands in both the rich client and thin client
interfaces using the Command Suppression application.
Note The Thin Client-specific section in the Suppress Commands tree displays
actions that appear only in the thin client, not in the rich client.
Additionally, administrators can also suppress thin client commands using the
WEB_menu_entry_suppressions preference. These preference settings override
any thin client suppression specified in the Command Suppression application.
If you do not see menu commands in the thin client that you expect to see,
check the setting of this preference. From the rich client, choose Edit→Options,
click the Index tab at the bottom of the Options dialog box, and search for the
WEB_menu_entry_suppressions preference to display this preference and its
settings.
Any values set for this preference override the selections made in the Command
Suppression application.
For more information about setting this preference, and for thin client menu
suppression suggestions, see the Thin Client Interface Guide.

Chapter
11 Managing changes and workflows
What is a Teamcenter workflow? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1
Can I delete a workflow process template while workflows based on this template are
still running? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-3
Can I modify shipped task templates before adding them to a workflow? . . . . . 11-3
How do I find specific arguments or handlers used in different workflow

tasks? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-3

Chapter
11 Managing changes and workflows
What is a Teamcenter workflow?

A workflow is the automation of business procedures in which documents,
information or tasks are passed from one participant to another in a way that
is governed by rules or procedures. Teamcenter workflows allow you to manage
your product data processes. You can create any type of workflow you need to
accommodate your business procedures.
Example A pharmaceutical company decides to implement workflows to shorten
drug development time, speeding medicines to people in need and
strengthening business performance.
After researching workflow solutions and investigating their own
company processes, the company determines the need for imaging
software to manage the drug test case report forms, data query software
to reduce correction time when errors were found in clinical data, and
data management software to enforce data integrity. Lifecycle data
management software such as Teamcenter provides all these solutions
in a single product.
The benefits of automating your business processes include:

• Improved efficiency.
The automation of your business processes can result in the elimination of
unnecessary steps.
• Better process control.

Company business processes are more easily managed with standardized work
methods and the availability of audit trails.
• Improved customer service.

Consistent business processes increases predictability in levels of response to
customers.
• Flexibility.
Computer-modeled processes can be quickly and easily redesigned to meet
changing business needs.
• Continual process improvement.

The resulting focus on business processes leads to their streamlining and
simplification.

Chapter 11 Managing changes and workflows
For example, you can create a simple review workflow in which an object is reviewed.
Depending on the outcome of the review, one of two tasks is then required. When
either of the tasks is performed, the workflow is complete. At completion, the object
is granted a specified status.
Typically, an object sent through a review workflow is granted Released status after
successful completion. Standard workflow behavior for released objects are that
their release time and date is marked and the object is made read-only.
In this example, if an item revision containing a design part and its accompanying
documentation is sent through design review, and the Post Approval task completes
(rather than the Post Rejection task), the item revision part is marked as Released
when the workflow finishes. The item revision and the objects it contains (the design
part, and the documentation) are made read-only. No further changes can be made
to the design, enforcing the review that was just performed.
In another example, you can create a more complicated workflow containing a

Condition task. In this workflow, whether a specified condition is met or not
determines the second round of tasks. Which tasks are required depend on whether
the condition was met.
Teamcenter workflows are extensible by handlers; small ITK programs used to

extend and customize the tasks. Handlers are essential to the creation of highly
functional, flexible workflows.
For more information about handlers, see the Workflow Designer Guide.
• Action handlers perform an action, such as attaching objects or sending an
e-mail.

Managing changes and workflows
• Rule handlers confirm a defined rule has been satisfied.
For more information about designing workflows to be deployed at your site, see
the Workflow Designer Guide.
Can I delete a workflow process template while workflows based on

this template are still running?
Yes, you can delete, edit, or rename a workflow process template while workflows
based on the template are in process.
Workflow processes are instantiated on saved workflow templates. Changes made to
workflow template do not effect active workflow processes unless the functionality
to apply workflow template changes to active workflow processes is configured and
you select the Apply template changes to all active workflow processes check
box after editing the workflow template.
For more information about creating and modifying workflow process templates, see
the Workflow Designer Guide.
For more information about applying workflow template edits to active workflow
processes, see the Workflow Designer Guide.
Can I modify shipped task templates before adding them to a

workflow?
You can extend shipped task templates by adding handlers. But you cannot modify
shipped task templates by changing the structure of the subtasks. Do not modify the
original task templates shipped with Teamcenter in this manner. Doing so affects all
subsequent workflows and may affect the database during a future upgrade when
the upgrade script attempts to update the task templates. Rather, you create your
own custom tasks to perform the desired actions.
For example, what if you want to add a task to your process that notifies users
of deadline inherent to the process. You know that the Route task shipped with
Teamcenter contains within it a Notify subtask. You would not strip out the
Acknowledge and Review subtasks within the Route task. Rather, you would
create a new task, for example, NotifyDeadline, and add the EPM-notify action
handler to the task.
How do I find specific arguments or handlers used in different

workflow tasks?
Use Workflow Designer’s export functionality to export the workflow processes you
want to search. The selected workflow templates are exported in XML format, which
you can then easily search. For example, if you have 2000 steps of workflow and
want to search how many tasks use the EPM-set-status handler, the best method is
to export all your workflows to a single XML file, and then search the file.
For more information about exporting templates from Workflow Designer, see the
Workflow Designer Guide.

Chapter
12 Working with product structures
Why use generic product structures? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-1
Should I use classic variants or modular variants to manage options and

variants? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-1
When should I manage business parts and designs separately? . . . . . . . . . . . . 12-2
I want to perform spatial searches to identify parts that may interfere with the
assembly I am working on. My assembly is not complex (less than 200 parts).
What is the best option? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-2

Chapter
12 Working with product structures
Why use generic product structures?

Structure Manager allows you to create generic product structures that can be
configured to show the product structure at a particular time or for a certain unit,
for example:
• The current production design of the product
• The product structure that was effective on a certain date
• A particular customer variant
By creating a single generic structure that can be configured according to a particular

user’s needs, you avoid duplicating assembly structures, with all the associated
problems of maintenance, redundant information, and complexity of searches.
Structure Manager displays your product structure in a multilevel indented list
format, making it easy to browse. This list is similar to the bill of materials (BOM)
that engineering organizations use to list manufacturing information.
For more information about working with Structure Manager, see the Structure
Manager Guide.
Should I use classic variants or modular variants to manage options

and variants?
The type of variant you use to manage options depends on your product design
and business practices.
Use classic variants if you have a nonmodular product structure that you do not
want to restructure or if you have limited scope for reuse of generic assemblies.
Use modular variants to facilitate reuse of lower level assemblies, to instantiate
business part numbers for a specific configuration, or to configure the same part
differently in different locations.
Note Modular variants cannot be used if you manage precise structures or if you
create architecture breakdowns in Platform Designer.
For more information, see Getting Started with Product Structure and the Structure
Manager Guide.

Chapter 12 Working with product structures
When should I manage business parts and designs separately?

Typically, you manage the business part and the design solution separately if
they have different lifecycles. For example, a part may have several design
representations in the case of flexible parts. Conversely, a design solution may apply
to multiple parts, for example, colored parts. In both cases, you should manage
them separately.
For more information, see Getting Started with Product Structure.
I want to perform spatial searches to identify parts that may interfere

with the assembly I am working on. My assembly is not complex (less
than 200 parts). What is the best option?
Consider using cacheless search if you have NX or JT files available. Unlike other
search mechanisms, cacheless search does not require that you create and maintain
secondary data caches. It can be combined with other search types such as attribute,
occurrence note, or Classification searches.
For more information, see the Structure Manager Guide.

Chapter
13 Working with e-mail and

Teamcenter mail
What is the difference between Teamcenter mail and my operating system

e-mail? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1
How does Teamcenter mail work? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1
What is involved in setting up external e-mail programs to support subscription

notification? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-2
Why are all the instant messaging symbols disabled (grayed out) throughout
Teamcenter? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-2

Chapter
13 Working with e-mail and

Teamcenter mail
What is the difference between Teamcenter mail and my operating

system e-mail?
Teamcenter provides an internal mail facility, called Teamcenter mail, as well as the
capability to use external e-mail programs such as Microsoft Outlook.
• Teamcenter mail lets you send mail from within the Teamcenter interface,
including attachments, to other Teamcenter users. You can also send e-mail
from Teamcenter to recipients who are not Teamcenter users by specifying a
valid SMTP address.
• In Teamcenter, notifications from Subscription Monitor, Workflow, and Schedule

Manager are sent by external e-mail (operating system mail).
Note An administrator can configure the EPM-notify and EPM-notify-report
workflow handlers to send Teamcenter mail and e-mail.
For information about using mail and e-mail in Teamcenter, see Getting Started
with Teamcenter.
For information about configuring Teamcenter mail and about configuring external
e-mail for subscription notification, see the Application Administration Guide.
How does Teamcenter mail work?

To use Teamcenter mail, you create an Envelope container object, select recipients,
enter a message, attach items from the clipboard, and then click Send to send the
message.
The mail is placed in the recipients’ Inbox, where each recipient can click the
envelope to display the contents in the Viewer pane.
Note An administrator must configure the EPM-notify and EPM-notify-report
workflow handlers to send Teamcenter mail and e-mail.

Chapter 13 Working with e-mail and Teamcenter mail
What is involved in setting up external e-mail programs to support

subscription notification?
An administrator must setup external (operating system) e-mail for subscription and
workflow notification. To configure this functionality:
• Set the TC_subscription preference to ON. This enables the Tools®Subscribe
menu command.
• Set the Mail_server_name preference to a valid SMTP mail server.

For information about mail gateway preferences, see the Preferences and
Environment Variables Reference.
• Set the TC_audit_manager=ON, TC_audit_manager_version=3, and

SCM_notification_history=true. These preferences enable notification
e-mails.
• Ensure a correct e-mail address is set for each Person in the Organization
application.
For information about creating and editing Person objects, see the Organization
Guide.
• Start the subscriptionmgrd subscription monitor process daemon.

For information about configuring and starting the subscriptionmgrd process
daemon, see the Subscription Monitor Guide.
Why are all the instant messaging symbols disabled (grayed out)
throughout Teamcenter?
Teamcenter rich client and thin client users can see when other users are available
for instant messaging with Microsoft Office Communicator. Teamcenter users can
view the current status of the owning and last modified users and can click the
Microsoft Office Communicator symbol in Teamcenter to initiate communication.
Note If instant messaging is not configured, the Microsoft Office Communicator

symbols of all users display grayed out.
Instant messaging must be configured by your Teamcenter administer.
For information about configuring Teamcenter instant messaging with Microsoft

Office Communicator, see the Application Administration Guide.

Chapter
14 Classifying your product data
What is the benefit of classifying my site’s data? . . . . . . . . . . . . . . . . . . . . . . 14-1
Why don’t I see any data when I open the Classification application? . . . . . . . . 14-1

Chapter
14 Classifying your product data
What is the benefit of classifying my site’s data?

Classification of your company’s product data (standard parts, technology data,
and manufacturing equipment) saves time by making component data easier to
find and retrieve and reduces costs by allowing you to reuse existing parts and
consolidate or eliminate duplicate or outdated parts. Classification is used to create
and maintain a hierarchical classification structure based on the attribute values of
your workspace objects.
You can use Classification to:
• Add classification objects (ICOs) to the classification hierarchy.
• Classify workspace objects.
• Find and retrieve classification objects.
• Modify the attribute values of Classification objects.
• Delete classification objects from the classification hierarchy.
For more information about using Classification, see the Classification Guide.
Why don’t I see any data when I open the Classification application?
Before you can use Classification, you must do one of the following:
• Create a classification structure manually.
For more information about creating a classification structure, see the
Classification Administration Guide.
• Import an existing classification hierarchy. This existing structure can be a

classification structure provided by Siemens PLM Software or by a third-party
vendor (such as a standard parts catalog).
For more information about importing and exporting a classification hierarchy,
see the Classification Administration Guide.
• In the manufacturing environment, load the manufacturing content kit from the
Teamcenter DVD. This kit contains a variety of sample data you can use in a
manufacturing environment.
For more information about populating the sample data, see the Installation on
Windows Servers Guide.

Chapter
15 Setting up programs
What are programs? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-1
How does the new concept of program align with the existing project, group, and role
concepts? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-1
Will I be able to have different rules (display rules, extension rules, GRM rules, and
so on) for each program? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-2
Will I be able to have different lists of values for each program? . . . . . . . . . . . 15-2
Will I be able to have different preferences for each program? . . . . . . . . . . . . . 15-2

Chapter
15 Setting up programs
What are programs?

The Program application in Teamcenter provides a mechanism for organizing data
and implementing access control based on program membership. The interface
includes two distinct windows, the Project Administration window, which you use
to create and administer programs, and the Smart Folder Administration window,
which you use to configure filtering criteria for displaying program data to users
in My Teamcenter.
The following concepts apply to programs:
• Only privileged team members can assign data to programs.
• Data can be assigned to or removed from programs manually or when the data
item is created, and items can be assigned to more than one program.
• Propagation rules define the associated data that is implicitly assigned to a

program when a primary item is assigned to the program.
• All items in a complete product structure can be assigned to a program using the
update_project_bom utility.
For more information about setting up programs, see Aerospace and Defense Solution
Guide.
How does the new concept of program align with the existing project,
group, and role concepts?
Programs and projects work the same. They are both used to organize data, and both
serve as the basis for granting/controlling data access to users. The only difference
between them are the program security rules. The Aerospace and Defense industry
works with programs because of the high level of security provided with the program
security rules. Program-level security can be enabled to restrict access to program
data. The default security rules can be extended to grant read access to program
data to members of the program team, on a program-by-program basis.
For more information about program security rules, see the Security Administration
Guide.
The access that groups and roles have to programs is similar to the access they have
to projects. Again, program security rules can be applied to programs, introducing
a higher level of security. When the program security attribute on a project is set
to true, Teamcenter considers the project as a program and program-level access
rules can be applied.

Chapter 15 Setting up programs
Note The display name of the Project application perspective can be configured to
display Program rather than Project by using the Business Modeler IDE
to configure the display name of the TC_Project business object.
In the Aerospace and Defense template, the display name of the TC_Project
business object is configured as Program.
For more information about configuring display names, see the Business
Modeler IDE Guide.
Will I be able to have different rules (display rules, extension rules,

GRM rules, and so on) for each program?
In Teamcenter, rules are decision points that govern the behavior of business objects,
including how they are named, what actions can be undertaken on them, and so on.
Creating rules is also known as business behavior modeling.
The following rules are applicable to programs:
• Naming rules
• Display rules
• Extension rules
• Deep copy rules
• Revision naming rules

Note Programs do not support GRM rules.
Rules are managed in Business Modeler IDE.

For more information about managing rules in Business Modeler IDE, see the
Business Modeler IDE Guide.
Will I be able to have different lists of values for each program?

Yes, you can have different lists of values for each program.
For more information, see Aerospace and Defense Solution Guide.
Will I be able to have different preferences for each program?

No, this is not possible.

Chapter
16 Creating reports
How are reports created? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-1
What is the best way to create reports on my Teamcenter data? . . . . . . . . . . . 16-1

Chapter
16 Creating reports
How are reports created?

Report Builder lets administrators create and manage Teamcenter report definitions.
After administrators create the report definitions, users can use these definitions to
generate reports from My Teamcenter in the rich client or the thin client.
Administrators can create several different kinds of reports:
• Summary reports present information based on a saved query definition.
• Item reports are run on one or more selected items based on a class of items.
• Custom reports show results based on custom processing.
What is the best way to create reports on my Teamcenter data?

You can use Report Builder to manage reports that were created with Teamcenter
reporting and analytics (TcRA). TcRA is a third-party product that extends
Teamcenter reporting capabilities. To use TcRA:
1. Download and install the appropriate version of the Teamcenter reporting and
analytics software distribution image from the Siemens PLM Software FTP
site at:
http://ftp.ugs.com/
2. Read the required preinstallation steps in the appropriate version of the

Teamcenter reporting and analytics Deployment Guide from the Global Technical
Access Center (GTAC) at:
http://support.industrysoftware.automation.siemens.com/docs/teamcenter/
3. Install the Reporting and Analytics option when you install Teamcenter.
For more information about installing this option, see the appropriate server
installation guide (for Windows or UNIX/Linux).
4. Download the Reporting and Analytics documentation from the Siemens PLM
Software download site at:
http://ftp.ugs.com/
Refer to the documentation to use the TcRA Mapper and BuildNPlay applications
to create and manage reports. Use Mapper to set user rights and to create the
cubes (similar to property sets) that are displayed in reports. Use BuildNPlay to
create and maintain the Reporting and Analytics report definitions.

Chapter 16 Creating reports
Teamcenter includes Report Generator, a reporting application. Use this application

to create reports from Manufacturing Process Planner and Part Planner data.
For more information about using this application, see the Report Generator Guide.

Chapter
17 Working with visual reports
What can I do with visual reports? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-1
Can I work with visual reports in Teamcenter? . . . . . . . . . . . . . . . . . . . . . . . 17-1

Chapter
17 Working with visual reports
What can I do with visual reports?

Use visual reports to quickly display and analyze parts of an assembly in meaningful
and well-organized ways. You can create search queries using conditions and regular
expression language. You create the scope of your searches by specifying part
metadata attributes and values. Then you apply the report rules so you can see
matched and unmatched parts in the viewing window.
Can I work with visual reports in Teamcenter?

It depends on which type of visual report you want to access. Visual reports can be
created from two different applications:
• Teamcenter lifecycle visualization (8.3 and later) including the stand-alone
application viewer and the Lifecycle Viewer
• NX (7.0 and later)
These two different visual report objects are separate entities. They are not
compatible.
From Teamcenter, you can easily work with visualization-based visual reports. You
cannot view NX-based visual reports.
Lifecycle Visualization NX
• Visual reports are saved in a local • Visual reports can be saved to the
file system as a .vpx file. Teamcenter database, but can only be
viewed in NX.
• You can save the report results to
My Teamcenter as a session. • A visual report created in NX and
saved to Teamcenter is saved as a
• You can also save the report report definition (.vpx) file. It can only
results to My Teamcenter as a be opened in NX.
PLM XML dataset, though this
dataset displays only the visual • The Teamcenter administrator can also
report results, not the visual use the Teamcenter Report Builder
report data structure. to create custom, server-side visual
reports exclusively for NX applications.
For more information about working
with these visual reports in For more information about working with
NX visual reports, see the topics regarding

Chapter 17 Working with visual reports
Lifecycle Visualization NX
Teamcenter, see Working with 3D the NX Visual Reporting tool delivered
Models. with the NX Help Collection.

Chapter
18 Managing quality data
What is the difference between DPV Reporting & Analysis and Teamcenter reporting
and analytics? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-1
What are features? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-1
How do I change the name of a feature? . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-2
Can I use measurement data to create feature definitions in DPV? . . . . . . . . . 18-2
How can I organize my plant? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-2

Chapter
18 Managing quality data
What is the difference between DPV Reporting & Analysis and

Teamcenter reporting and analytics?
DPV Reporting & Analysis is a statistical measurement analysis tool for organizing,
viewing, and comparing production measurement data while Teamcenter reporting
and analytics is a thin client tool for Teamcenter that lets managers compare
information from disparate sources, such as from customers or vendors. Teamcenter
reporting and analytics is built into Teamcenter Report Builder while DPV Reporting
& Analysis is an add-on to Teamcenter lifecycle visualization.
For more information about DPV Reporting & Analysis, see Using DPV Reporting
& Analysis in the DPV documentation.
For more information about Teamcenter reporting and analytics, see the Report
Generator Guide.
What are features?

Features represent the location of holes, pins, slots, tabs, and part and assembly
surfaces on a 3D model. All features have attributes that define the feature’s
measurement characteristics. For example, for a point, its feature attributes are the
X, Y, and Z locations and deviations from X, Y, and Z. The X, Y, and Z attributes help
you understand all six degrees of freedom and the relationship of the part outcome
based on assembly and stamping tools. Nominal feature attributes represent the
perfect or ideal location of the points.
The x feature attributes for a portion of the grille of an all-terrain vehicle (ATV)
are shown in the figure.
Inspection devices (such as, vision systems or Coordinate Measurement Systems) on

the shop floor measure the actual location of the features. DPV collects the measured
feature data and sends it to Teamcenter for storage. You then use DPV Reporting

Chapter 18 Managing quality data
& Analysis to visualize and analyze the measurement data to help identify and
resolve issues.
How do I change the name of a feature?

To change the name of a feature that you defined in Teamcenter and released for
production, follow these steps.
Tip If the routine that manages the Excel Engineering workbook or if the
workbook has a release status, you must revise the routine before you can
edit it.
1. In the workbook that defines the feature you want to rename, change its name in
the Feature Label column in the Feature Info tab and all specification set tabs
(ENGG and DML, by default).
2. Save the workbook and export the routine to the DPV Device Client.
Tip Use the workflow ExportRoutine_to_AI.
3. Load at least one measurement data file containing the new feature name.
The data now shows the new feature name and it inherits all of the data from
the previous feature name.
Can I use measurement data to create feature definitions in DPV?

You can use the DPV XML Generation stand-alone utility to generate feature
definitions from a measurement data file. The result is an Excel Engineering
workbook with all the engineering data from the data file. The XML Generation
utility is installed when you install DPV Device Client.
For more information, see Generating engineering data from measurement data.
Note You can also generate feature definitions from your CAD geometry using
Tecnomatix CMM Inspection.
For more information, see your DPV customer representative or your NX
documentation.
How can I organize my plant?

When defining a plant structure in Manufacturing Process Planner, you can organize
your plant in any way you like. Any items between the inspection operation and the
MEPrPlantProcess item are optional and for your organizational purposes only.
For example, you can define the following organization structure:
• Assembly line

Managing quality data
o Zone within the assembly line

Station within the zone
For more information about defining a plant, see Defining a plant process structure.

Appendix
A Glossary

Appendix
A Glossary
Access Manager (AM)

Teamcenter application that enables the system administrator to grant users access
to Teamcenter objects.
action handler
Handler used to extend and customize workflow task actions. Action handlers
perform such actions as displaying information, retrieving the results of previous
tasks (inherit), notifying users, setting object protections, and launching applications.
See also task handler.
assembly
Compound object that is assembled from other objects and may add additional
information to their interpretation.
• In the context of an assembly, other assemblies are called subassemblies, while
noncompound objects are called components.
• A single-level compound object that is distinct from a multilevel product

structure or bill of materials, which is a hierarchy of assemblies. Assembly
data is stored in a BOM view revision.
Business Modeler IDE

Teamcenter application that enables a customer to define data model objects such as
business objects, classes, attributes, lists of values, and rules.
business object
Logical grouping of data attributes and properties that are manipulated at the
enterprise level.
A Global Services business object allows users to query for and update information
in multiple data sources.
classification
Process of categorizing objects according to similarity in characteristics. While the
objects in one class share the same characteristics, the values of these characteristics
may differ. For example, drill bits all share the length and diameter characteristics,
but drill bit objects differ in length and diameter.
PLM00125 Frequently Asked Questions for Teamcenter A-1

Appendix A Glossary
client
Role played by a software component of a system when it requests particular services
be performed on its behalf by another entity, a server. See also server.
data model
Abstract model that describes how data is represented and used.
dataset
Teamcenter workspace object used to manage data files created by other software
applications. Each dataset can manage multiple operating system files, and each
dataset references a dataset tool object and a dataset business object.
File Management System (FMS)

System that manages uploading and downloading file data between clients and
volumes in both two-tier and four-tier architecture deployments.
• FMS provides volume servers for file management, a shared server-level
performance cache for shared data access between multiple users, a client-based
private user cache for rich clients, and a transient datastore mechanism for
transporting reports, PLM XML, and other nonvolume data between the
enterprise and client tiers.
• FMS file caching enables placing the data close to the user, while maintaining a
central file volume and database store.
FMS
See File Management System (FMS).
FMS client cache (FCC)

FMS process that runs on a client host, uploading files to an FMS server cache
process, requesting files from an FMS server cache process, and caching files on
the client host. The FCC process manages two caches of whole files: a write cache
containing files uploaded to a Teamcenter volume and a read cache containing files
downloaded from a Teamcenter volume. It also manages one segment file cache for
Teamcenter lifecycle visualization. Each Teamcenter rich client host requires a
local FMS client cache.
FMS master configuration file

File that configures FMS (fmsmaster.xml). The FMS master configuration file
describes the FMS network and defines groups of server caches. It can also define
default values for server caches and client caches, such as maximum sizes. Values
defined in the server cache configuration file and in the client cache configuration file
can override the default values defined in the master configuration file.
FMS server cache (FSC)

FMS process that runs on a server host and performs as a volume server (when
running on a host where a volume is located or directly mounted) or a cache server
(when running on a host where a volume is not located or directly mounted) and a
configuration server. As a volume or cache server, the FSC checks all file access
requests for a ticket that Teamcenter generates to authorize file access. As a cache
server, it manages two segment file caches, one for downloading files and one for
A-2 Frequently Asked Questions for Teamcenter PLM00125

Glossary
uploading files. As a configuration server, it provides FMS configuration information

to file client caches and other FSCs. As a transient server, it delivers PLM XML and
other transient files to clients. A minimum of one FSC must be deployed in any
Teamcenter installation. Multiple FSCs can be deployed, with each FSC performing
one designated purpose as either a volume, a cache, or a configuration server.
four-tier architecture
Teamcenter architecture that includes four tiers: resource tier, client tier, Web tier,
and enterprise tier. Contrast with two-tier architecture.
item
Workspace object generally used to represent a product, part, or component. Items
can contain other workspace objects including other items and object folders.
item revision
Workspace object generally used to manage revisions to items.
metadata
Object description in the Teamcenter database.
Multi-Site Collaboration
Teamcenter capability that allows the exchange of data objects among several
Teamcenter databases. Transfer of objects among databases is controlled by daemon
processes running on designated servers. Objects are replicated by exporting them
from their original database and importing them into the requesting database.
Configuration of Multi-Site Collaboration is optional.
navigation pane
Rich client framework component that displays buttons of the applications available
for use in the rich client. Clicking the application button launches the application.
Organization
Teamcenter application that enables a system administrator to create and manage
critical Teamcenter files and database entries. It is the point of access for creating a
company’s virtual organization and for performing system administration activities
such as volume creation, maintenance, and site administration. Organization
enables creation and management of person, user, role, and group definitions;
definition of the hierarchical structure of the Teamcenter organization; management
of data volumes; and establishment and maintenance of Teamcenter sites.
organization tree
Graphic display of the Teamcenter organization structure. Expanding and collapsing
branches of the tree enables viewing and managing the organizational structure.
Selecting a node starts Organization wizards used to create groups, subgroups,
roles, users, and persons.

Appendix A Glossary
part
Business item that is managed in a company’s part releasing system.
PLM XML
Siemens PLM Software format for facilitating product life cycle interoperability
using XML. PLM XML is open and based on standard W3C XML schemas.
Representing a variety of product data both explicitly and via references, PLM
XML provides a lightweight, extensible, and flexible mechanism for transporting
high-content product data over the Internet.
Preference
Configuration variable stored in a Teamcenter database and read when a Teamcenter
session is initiated. Preferences allow administrators and users to configure many
aspects of a session, such as user logon names and the columns displayed by default
in a properties table.
Preference Scope
Hierarchical range for which a Teamcenter preference can be set. The scope of a
preference can be site, group, role, or user.
Product Data
Teamcenter application used to access and interact with the items and item revisions
that represent a company’s products, parts, and components.
product lifecycle management (PLM)

Product lifecycle management (PLM) is an essential element in effectively creating
and using global innovation networks to enable organizations and their partners
to collaborate at every stage of the product life cycle. PLM provides businesses
with unified information at every stage of the product life cycle including planning,
development, execution, and support.
program view
View that provides a read-only view of tasks across multiple schedules.
project
Basis for identifying a group of objects available to multiple organizations, such as
project teams, development teams, suppliers, and customers for a particular piece
of work.
release status
Status associated with a workspace object when it is released through a workflow
process.
rich client
Java-based user interface to Teamcenter installed on user workstations. The rich
client accesses Teamcenter databases using a remote or local server. Compare to
thin client.

Glossary
rule handler
Handler used to integrate workflow business rules into Enterprise Process Modeling
processes at the task level. Rule handlers attach conditions to an action. See also
task handler.
server
System software component that performs a specifically defined set of software
services on behalf of one or more clients. In a typical Teamcenter installation,
servers are centralized on dedicated hosts that support a large number of clients.
Clients are distributed on hosts connected to the servers via various networking
techniques. See also client.
site
Individual installation of Teamcenter comprising a single Teamcenter database,
all users accessing that database, and additional resources such as hardware,
networking capabilities, and third-party software applications (tools) required to
implement Teamcenter at that site.
system administrator
Teamcenter user who is a member of the system administration group.
task (workflow)
Fundamental building block used to construct a process. Each task defines a set of
actions, rules, and resources used to accomplish that task.
task handler
Small Integration Toolkit program or function. Handlers are the lowest level
building blocks in Enterprise Process Modeling. They are used to extend and
customize tasks. There are two kinds of handlers: action handlers and rule handlers.
See also action handler and rule handler.
thin client
Teamcenter user interface that provides a streamlined browser-based view of product
information stored in a Teamcenter database. The thin client is configured in the
Web tier, which creates and serves its Web pages to the client. Compare to rich client.
transient volume
Operating system directory controlled by Teamcenter and used to store temporary
data for transport of reports, PLM XML, and other nonvolume data between the Web
tier and client tier in a deployment of the Teamcenter four-tier architecture.
two-tier architecture
Teamcenter architecture that includes a resource tier and a client tier. The resource
tier comprises the database server and database. The client tier comprises the
Teamcenter rich client, third-party applications that integrate with the rich client,
and a local server. This architecture supports only the Teamcenter rich client.
Contrast with four-tier architecture.

Appendix A Glossary
user
Definition that is the mechanism by which Teamcenter identifies and interacts with
each user. User definitions contain a name (derived from the person definition), user
ID, operating system name, and password.
volume
Operating system directory controlled by Teamcenter and used to store the files
managed by Teamcenter. When a user performs an action that causes Teamcenter
to create a file, the file is created in the Teamcenter volume. Users cannot directly
access the files in Teamcenter volumes; they must do so via a Teamcenter session.
workflow
Automation of the concept that all work flows through one or more business
processes to accomplish an objective. Using workflow, documents, information, and
tasks are passed between participants during the completion of a particular process.
Workflow Designer
Teamcenter application that enables administrators to graphically design workflow
process templates, incorporating company business practices and procedures into
the templates. Teamcenter users initiate workflow processes using these templates.

Index
A Command suppression for the thin

Access privileges client . . . . . . . . . . . . . . . . . . . . . . . . 10-4
Viewing for another user . . . . . . . . . 9-10 Composite ID for Teamcenter license . . . 3-1
ACL changes . . . . . . . . . . . . . . . . . . . . 6-3 Configuring external e-mail . . . . . . . . . 13-2
Adhoc Design Context . . . . . . . . . . . . . 10-1 Configuring search . . . . . . . . . . . . . . . . 9-5
Administering FMS . . . . . . . . . . . . . . . . 7-1 Copy privilege . . . . . . . . . . . . . . . . . . . . 6-5
Administering Teamcenter . . . . . . . . . . . 6-1 Creating a classification structure . . . . 14-1
Advanced search . . . . . . . . . . . . . . . . . . 9-5 Creating composite ID for Teamcenter
Applications license . . . . . . . . . . . . . . . . . . . . . . . . 3-1
Adhoc Design Context . . . . . . . . . . . 10-1 Creating reports . . . . . . . . . . . . . . . . . 16-1
Classification . . . . . . . . . . . . . . . . . . 10-1 Creating reports of Teamcenter data . . . 16-1
Design Context . . . . . . . . . . . . . . . . 10-2 Creating visual reports in
Manufacturing Process Planner . . . . 10-1 Teamcenter . . . . . . . . . . . . . . . . . . . . 17-1
My Teamcenter . . . . . . . . . . . . . . . . 10-1 Custom Java code migration into Teamcenter
Structure Manager . . . . . . . . . . . . . . 10-1 10.1 . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3
Systems Engineering . . . . . . . . . . . . 10-1 Customer hierarchy . . . . . . . . . . . . . . . 14-1
Applications in rich client . . . . . . . . . . . 9-1 Customizing Teamcenter . . . . . . . . . . . . 8-1
Applications in thin client . . . . . . . . . . 10-1 Customizing thin client interface icons . . 6-3
Assign command . . . . . . . . . . . . . . . . . . 9-9 Customizing user interface icons . . . . . . 8-2
Audit logs versus subscriptions . . . . . . . 6-4
Audit Manager versus Subscription D
Monitor . . . . . . . . . . . . . . . . . . . . . . . 6-4
Data model . . . . . . . . . . . . . . . . . . . . . . 5-1
Database clean up . . . . . . . . . . . . . . . . . 6-1
B Deep copy rules . . . . . . . . . . . . . . . . . . 15-2
Bill of material (BOM) . . . . . . . . . . . . . 12-1 Default security rules . . . . . . . . . . . . . 15-1
Business Modeler IDE . . . . . . . . . . . . . . 5-1 Defining a transient volume . . . . . . . . . . 6-3
Business parts . . . . . . . . . . . . . . . . . . 12-1 Delegating a signoff task . . . . . . . . . . . . 9-7
Deleting workflow process templates . . . 11-3
Design Context . . . . . . . . . . . . . . . . . . 10-2
C
Determining the transient volume
Cache errors . . . . . . . . . . . . . . . . . . . . . 7-5 definition . . . . . . . . . . . . . . . . . . . . . . 6-3
Cacheless search . . . . . . . . . . . . . . . . . 12-2 Display rules . . . . . . . . . . . . . . . . . . . 15-2
Catalog hierarchy . . . . . . . . . . . . . . . . 14-1 Documentation for maintenance pack
Change user interface icons . . . . . . . . . . 8-2 releases . . . . . . . . . . . . . . . . . . . . . . . 4-2
Changes to access control list . . . . . . . . . 6-3
Changing the Responsible Party . . . . . . . 9-9
E
Checked-out icon determines
performance . . . . . . . . . . . . . . . . . . . . 9-2 e-mail . . . . . . . . . . . . . . . . . . . . . . . . 13-1
Classic variants . . . . . . . . . . . . . . . . . 12-1 Enabling search . . . . . . . . . . . . . . . . . . 9-5
Classification . . . . . . . . . . . . . . . . . . . 10-1 Errors after modifying an FCC . . . . . . . . 7-5
Classifying product data . . . . . . . . . . . 14-1 Errors after removing an FCC . . . . . . . . 7-6
Cleaning a database . . . . . . . . . . . . . . . 6-1 Errors after stopping an FCC . . . . . . . . . 7-6
Client cache affecting startup Extension rules . . . . . . . . . . . . . . . . . . 15-2
performance . . . . . . . . . . . . . . . . . . . . 9-3 External e-mail programs . . . . . . . . . . 13-2
PLM00125 Frequently Asked Questions for Teamcenter Index-1

Index
F Item types hidden from creation

menus . . . . . . . . . . . . . . . . . . . . . . . . 5-2
FAQ overview . . . . . . . . . . . . . . . . . . . . 1-1
FCC . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1
FCC elements requiring a manual J
restart . . . . . . . . . . . . . . . . . . . . . . . . 7-5 Java custom code migration into Teamcenter
FCC in TCCS . . . . . . . . . . . . . . . . . . . . 7-2 10.1 . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3
FCC not responding to pipe attempts . . . 7-2
FCC, errors after modifying . . . . . . . . . . 7-5 L
FCC, errors after removing . . . . . . . . . . 7-6
FCC, errors after stopping . . . . . . . . . . . 7-6 Lifecycle Visualization visual reports . . 17-1
FCC, resetting a user’s . . . . . . . . . . . . . 7-4 Lock errors . . . . . . . . . . . . . . . . . . . . . . 7-5
FCC, restart when . . . . . . . . . . . . . . . . . 7-2
FCC, restarting . . . . . . . . . . . . . . . . 7-2–7-3 M
fcc.xml file modifications . . . . . . . . . . . . 7-5
Maintaining a database . . . . . . . . . . . . . 6-1
FMS . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1
Maintenance . . . . . . . . . . . . . . . . . . . . . 6-1
Forms . . . . . . . . . . . . . . . . . . . . . . . . . 8-3
Maintenance pack releases . . . . . . . . . . 4-2
Frequently asked questions . . . . . . . . . . 1-1
Managing business parts . . . . . . . . . . . 12-1
FSC . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1
Managing FMS . . . . . . . . . . . . . . . . . . . 7-1
Functionality not available in thin
Managing product designs . . . . . . . . . . 12-1
client . . . . . . . . . . . . . . . . . . . . . . . . 10-3
Managing workflows . . . . . . . . . . . . . . 11-1
Manually creating a classification
G structure . . . . . . . . . . . . . . . . . . . . . 14-1
Generating composite ID for Teamcenter Manufacturing Process Planner . . . . . . 10-1
license . . . . . . . . . . . . . . . . . . . . . . . . 3-1 Manufacturing Structure Editor, see
Generic structures . . . . . . . . . . . . . . . 12-1 Manufacturing Process Planner
GRM rules . . . . . . . . . . . . . . . . . . . . . 15-2 Manufacturing Tooling Library . . . . . . 14-1
GTAC contact information . . . . . . . . . . . 1-1 Menus . . . . . . . . . . . . . . . . . . . . . . . . . 8-1
Metamodel . . . . . . . . . . . . . . . . . . . . . . 5-1
Migrating custom Java code into Teamcenter
H 10.1 . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3
Help . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1 Modifying an FCC generates errors . . . . 7-5
Help collection Modifying task templates . . . . . . . . . . . 11-3
Search toolbar . . . . . . . . . . . . . . . . . . 2-4 Modular variants . . . . . . . . . . . . . . . . 12-1
Hide item types . . . . . . . . . . . . . . . . . . . 5-2 My Teamcenter . . . . . . . . . . . . . . . . . . 10-1
Hierarchical classification structure . . . 14-1
HTML help tips . . . . . . . . . . . . . . . . . . 2-3 N
HTML online help . . . . . . . . . . . . . . . . . 2-1
Naming rules . . . . . . . . . . . . . . . . . . . 15-2
New installation . . . . . . . . . . . . . . . . . . 3-1
I Nonmodular product structure . . . . . . . 12-1
Icons in the user interface . . . . . . . . . . . 8-2 NX visual reports . . . . . . . . . . . . . . . . 17-1
Improving client startup
performance . . . . . . . . . . . . . . . . . 9-2–9-3 O
Information about enhancements made during Online help . . . . . . . . . . . . . . . . . . . . . . 2-1
maintenance pack releases . . . . . . . . . . 4-2 Online help collection . . . . . . . . . . . . . . 1-1
Install Teamcenter license
instructions . . . . . . . . . . . . . . . . . . . . 3-2
Installing online help . . . . . . . . . . . . . . 1-1 P
Installing Teamcenter . . . . . . . . . . . . . . 3-1 PDF help tips . . . . . . .......... . . . . 2-4
Instructions for running Teamcenter PDF online help . . . . .......... . . . . 2-1
license . . . . . . . . . . . . . . . . . . . . . . . . 3-2 perform-signoffs task . .......... . . . . 9-7
Introduction . . . . . . . . . . . . . . . . . . . . . 1-1 Performance improved by removing
Introduction to the FAQ . . . . . . . . . . . . . 1-1 checked-out icon . . . .......... . . . . 9-2
Index-2 Frequently Asked Questions for Teamcenter PLM00125

Index
Perspectives Stopping an FCC generates errors . . . . . 7-6

Opening . . . . . . . . . . . . . . . . . . . . . . 9-4 Structure Manager . . . . . . . . . . . . . . . 10-1
Schedule Manager . . . . . . . . . . . . . . 10-2 Structure Manager application . . . . . . . 12-1
Pipe attempts, FCC not responding . . . . . 7-2 Subscription Monitor versus Audit
Platform Designer application . . . . . . . 12-1 Manager . . . . . . . . . . . . . . . . . . . . . . . 6-4
Preferences found in Java source code . . . 6-3 Subscriptions versus audit logs . . . . . . . 6-4
Process search . . . . . . . . . . . . . . . . . . 11-3 Systems Engineering . . . . . . . . . . . . . . 10-1
Product designs . . . . . . . . . . . . . . . . . 12-1
Product structure . . . . . . . . . . . . . . . . 12-1
Program application . . . . . . . . . . . . . . 15-1 T
Program lists of values . . . . . . . . . . . . 15-2 Task template modification . . . . . . . . . 11-3
Program preferences . . . . . . . . . . . . . . 15-2 TCCS contains the FCC . . . . . . . . . . . . . 7-2
Project Administration window . . . . . . 15-1 Teamcenter data reports . . . . . . . . . . . 16-1
Project application versus Program Teamcenter Environment Manager
application . . . . . . . . . . . . . . . . . . . . 15-1 (TEM) . . . . . . . . . . . . . . . . . . . . . . . . 3-1
Teamcenter functionality not in thin
Q client . . . . . . . . . . . . . . . . . . . . . . . . 10-3
Teamcenter help . . . . . . . . . . . . . . . . . . 2-1
Quick search . . . . . . . . . . . . . . . . . . . . . 9-5 Teamcenter mail . . . . . . . . . . . . . . . . . 13-1
Teamcenter maintenance . . . . . . . . . . . . 6-1
Teamcenter search . . . . . . . . . . . . . . . . 9-5
R Temporary data storage area . . . . . . . . . 6-2
Reassigning a signoff task . . . . . . . . . . . 9-7 Thin client applications . . . . . . . . . . . . 10-1
Reassigning the Responsible Party . . . . . 9-9 Thin client command suppression . . . . . 10-4
Removing an FCC generates errors . . . . . 7-6 Thin client functionality . . . . . . . . . . . 10-3
Reports of Teamcenter data . . . . . . . . . 16-1 Thin client versus rich client . . . . . . . . 10-2
Resetting a user’s FCC environment . . . . 7-4 Tips on HTML help . . . . . . . . . . . . . . . . 2-3
Responsible Party . . . . . . . . . . . . . . . . . 9-9 Tips on PDF help . . . . . . . . . . . . . . . . . 2-4
Restart an FCC, when . . . . . . . . . . . . . . 7-2 Transferring a signoff task . . . . . . . . . . . 9-7
Restarting an FCC . . . . . . . . . . . . . 7-2–7-3 Transferring data to/from the business logic
Restricting copying . . . . . . . . . . . . . . . . 6-5 server . . . . . . . . . . . . . . . . . . . . . . . . . 6-2
Revision naming rules . . . . . . . . . . . . . 15-2 Transient volume . . . . . . . . . . . . . . . . . 6-2
Rich client Transient volume definition . . . . . . . . . . 6-3
Form . . . . . . . . . . . . . . . . . . . . . . . . . 8-3 Type analysis tool . . . . . . . . . . . . . . . . . 4-1
Rich client applications . . . . . . . . . . . . . 9-1 Type name collisions . . . . . . . . . . . . . . . 4-1
Rich client perspectives . . . . . . . . . . . . . 9-1
Run Teamcenter license instructions . . . . 3-2 U
Undocumented preferences . . . . . . . . . . 6-3
S UNIX server Windows data directory . . . 3-3
Schedule Manager . . . . . . . . . . . . . . . . 10-2 Unsupported preferences . . . . . . . . . . . . 6-3
Search . . . . . . . . . . . . . . . . . . . . . . . . . 9-5 Updating changes to an ACL . . . . . . . . . 6-3
Search toolbar for help . . . . . . . . . . . . . 2-4 Upgrading Teamcenter . . . . . . . . . . . . . 4-1
Searching workflows . . . . . . . . . . . . . . 11-3 User interface icons . . . . . . . . . . . . . . . . 8-2
Security rules . . . . . . . . . . . . . . . . . . . 15-1 Using a transient volume . . . . . . . . . . . . 6-2
Setting a user’s FCC environment . . . . . 7-4 Using the FAQ . . . . . . . . . . . . . . . . . . . 1-1
Setup external e-mail . . . . . . . . . . . . . 13-2
Signoff tasks . . . . . . . . . . . . . . . . . . . . . 9-7 V
Simple search . . . . . . . . . . . . . . . . . . . . 9-5
Smart Folder Administration window . . 15-1 Variants . . . . . . . . . . . . . . . . . . . . . . . 12-1
Spatial search . . . . . . . . . . . . . . . . . . . 12-2 Viewing access privileges for another
Starting an FCC . . . . . . . . . . . . . . . 7-2–7-3 user . . . . . . . . . . . . . . . . . . . . . . . . . 9-10
Startup performance of the client . . . 9-2–9-3 Views in rich client . . . . . . . . . . . . . . . . 9-1
PLM00125 Frequently Asked Questions for Teamcenter Index-3

Index
Visual reports . . . . . . . . . . . . . . . . . . . 17-1 Windows data directory on UNIX

server . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
W Workflow process template deletion . . . 11-3
Workflow search . . . . . . . . . . . . . . . . . 11-3
WEB_menu_entry_suppressions preference
Working with Business Modeler IDE . . . . 5-1
for thin client command suppression . . 10-4
When restart an FCC . . . . . . . . . . . . . . 7-2
Index-4 Frequently Asked Questions for Teamcenter PLM00125

Faq Teamcenter

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Faq Teamcenter

Hochgeladen von

Copyright:

Verfügbare Formate

Teamcenter 10.

Frequently Asked Questions for

This software and related documentation are proprietary to Siemens Product

2 Frequently Asked Questions for Teamcenter PLM00125

Proprietary and restricted rights notice . . . . . . . . . . . . . . . . . . . . . . . . . 2

Frequently Asked Questions for Teamcenter . . . . . . . . . . . . . . . . . . . . . 1-1

Using the Teamcenter help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

Installing Teamcenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

Upgrading Teamcenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

Working with Business Modeler IDE . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

Administering Teamcenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1

PLM00125 Frequently Asked Questions for Teamcenter 3

Managing FMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1

Customizing Teamcenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1

Working with the rich client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1

Working with the thin client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1

Managing changes and workflows . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1

4 Frequently Asked Questions for Teamcenter PLM00125

Working with product structures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-1

Working with e-mail and Teamcenter mail . . . . . . . . . . . . . . . . . . . . . . 13-1

Classifying your product data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-1

Setting up programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-1

Creating reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-1

Working with visual reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-1

Managing quality data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-1

PLM00125 Frequently Asked Questions for Teamcenter 5

6 Frequently Asked Questions for Teamcenter PLM00125

1 Frequently Asked Questions

How do I use Frequently Asked Questions for Teamcenter? . . . . . . . . . . . . . . 1-1

What is the online help? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

Who do I contact for more help with Teamcenter? . . . . . . . . . . . . . . . . . . . . . 1-1

PLM00125 Frequently Asked Questions for Teamcenter

1 Frequently Asked Questions

How do I use Frequently Asked Questions for Teamcenter?

What is the online help?

Who do I contact for more help with Teamcenter?

PLM00125 Frequently Asked Questions for Teamcenter 1-1

2 Using the Teamcenter help

How do I install and use the help? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

What help formats are available? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

How do I use the HTML help? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3

How do I use the PDF help? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4

PLM00125 Frequently Asked Questions for Teamcenter

2 Using the Teamcenter help

How do I install and use the help?

What help formats are available?

PLM00125 Frequently Asked Questions for Teamcenter 2-1

The HTML directory on the documentation installation media contains HTML

• The advantage of PDF (Portable Document Format) is its portability. Readers

o If you share the Teamcenter PDF Help Collection on a Web (HTTP)

Network host (UNC path): file://///host/PDF/index.htm

2-2 Frequently Asked Questions for Teamcenter PLM00125

How do I use the HTML help?

The formatting of content pasted into a Microsoft Word

• The links connect to a topic in a different deliverable when

o For more information about your options for completing

PLM00125 Frequently Asked Questions for Teamcenter 2-3

Displays search results. The

• Type text for your search in the Search box.

• Click Preferences to set search behaviors and filter search

• To return to the search results page, use your browser’s

Note To search within an extensive topic, such as the

2. Copy the contents of the address bar to your clipboard.