Teamcenter 9.1: Publication Number PLM00049 H

Teamcenter 9.
Project and Program Guide
Publication Number
PLM00049 H
Proprietary and restricted rights notice
This software and related documentation are proprietary to Siemens Product

Lifecycle Management Software Inc.
2012 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 Project and Program Guide PLM00049 H

Contents
Proprietary and restricted rights notice . . . . . . . . . . . . . . . . . . . . . . . . . 2
Getting started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

Getting started with Project . . . . . . . . . .... . . . . . . . . . . . . . . . . . . . . . . . 1-1
Before you begin . . . . . . . . . . . . . . . . . . .... . . . . . . . . . . . . . . . . . . . . . . . 1-1
Project and Program interface . . . . . . . . .... . . . . . . . . . . . . . . . . . . . . . . . 1-2
Basic concepts about Project and Program ... . . . . . . . . . . . . . . . . . . . . . . . 1-9
Basic tasks using Project and Program . . .... . . . . . . . . . . . . . . . . . . . . . . . 1-13
Creating and administering projects . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

Creating and administering projects and programs . . . . . . . . . . . . . . . . . . . . 2-1
Project and program creation and administration process . . . . . . . . . . . . . . . . 2-1
Search for a project or program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
Create a new project or program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Create a project or program based on an existing project or program . . . . . . . . 2-3
Assign groups of users to a project or program . . . . . . . . . . . . . . . . . . . . . . . . 2-3
Assign individual users to a project or program . . . . . . . . . . . . . . . . . . . . . . . 2-4
Designate a project or program team administrator . . . . . . . . . . . . . . . . . . . . 2-5
Assign privileged team members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5
Set a users default project or program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5
Modify existing projects and programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6
Delete a project or program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6
Activating and deactivating projects and programs . . . . . . . . . . . . . . . . . . . . 2-7
Importing and exporting project or program data in a Multi-Site Collaboration
environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8
Applying project and program security (Access Manager) rules . . . . . . . . . . . . 2-9
Associating data dictionaries (libraries) with projects . . . . . . . . . . . . . . . . . . . 2-14
Configuring projects and programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

Configuring projects and programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
Defining default naming rules for projects . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
Assigning secondary objects to projects and programs . . . . . . . . . . . . . . . . . . 3-2
Automatically assigning objects to projects and programs . . . . . . . . . . . . . . . . 3-4
Restricting data creation to within the context of a project or program . . . . . . . 3-7
Controlling assignment of replicated (imported) data to projects . . . . . . . . . . . 3-7
Setting the current project for new Teamcenter sessions . . . . . . . . . . . . . . . . . 3-7
Selecting different object property values based on project assignment . . . . . . 3-8
Displaying projects to users based on current group and role . . . . . . . . . . . . . 3-8
Using pseudo folders to organize the display of objects in projects . . . . . . . . . . 3-8
Project and program preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8
Configuring smart folder filtering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

Apply smart folder filtering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
Viewing project data in My Teamcenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
PLM00049 H Project and Program Guide 3

Contents
Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Index-1
4 Project and Program Guide PLM00049 H

Chapter
1 Getting started
Getting started with Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Before you begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Project and Program interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2

Project and Program menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
File menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
Edit menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
View menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
Window menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
Project and Program quick links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
Project Administration window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6
Project administration buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6
Project administration tabs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7
Smart Folder Administration window . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8
Smart folder administration buttons . . . . . . . . . . . . . . . . . . . . . . . . . 1-8
Rich client perspectives and views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9
Basic concepts about Project and Program . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9

Project administrators and team members . . . . . . . . . . . . . . . . . . . . . . . 1-10
Ownership of data by a project or program . . . . . . . . . . . . . . . . . . . . . . . 1-11
Assigning data to projects and programs . . . . . . . . . . . . . . . . . . . . . . . . . 1-12
Assigning data to and removing data from projects and programs . . . . 1-12
Basic tasks using Project and Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-13
PLM00049 H Project and Program Guide

Chapter
1 Getting started
Getting started with Project

The Project and Program applications provide a mechanism for organizing data and
implementing access control based on project or program membership.
Project and Program are used by Teamcenter administrators to:
Set up projects and programs.
Assign users as members of projects and programs.
Implement access control based on project or program membership.
Apply filters to determine the subset of project or program data that users view
in My Teamcenter.
Associate data dictionaries (libraries) with projects and programs.
Project and Program work with Access Manager to control access to data by project
or program members.
Before you begin

Prerequisites Access to Project and Program is controlled by your Teamcenter
administrator.
In addition, only users with the following designations can
perform tasks in Project and Program:
Project administrators can create, modify, and delete
projects and programs. They can also add and remove team
members from projects and programs and apply access rules.
Note
Project administrators can only manage projects
and programs that they own. They cannot manage
projects or programs owned by other project
administrators. Ownership is established when the
project is created.
Project and program team administrators can modify

project and program information and add and remove team
PLM00049 H Project and Program Guide 1-1

Chapter 1 Getting started
members from the project or program. However, they cannot

create or delete a project.
Enable Project Project does not need to be enabled before you use it, but during
and Program installation, this feature must be selected.
The system can be configured to display the Project application
as Program. To do this, set the display name of the TC_Project
business object in the Business Modeler IDE to Program.
For more information, see Business Modeler IDE Guide.
Note
The Project application is automatically displayed as
Program when you install the ADS Foundation template.
If you have trouble accessing Project or Program, see your

system administrator; it may be a licensing issue.
Note
You can log on to Teamcenter only once. If you try to log
on to more than one workstation at a time, you see an
error message.
Configure You can set various options to configure the level of propagation
Project and applied when objects are assigned to projects or programs, to
Program specify whether project or program security rules are applied to
all projects and programs or only to the users current project
or program, and to specify whether BOM views and BOM view
revisions are assigned to the project or program when the items
or item revisions are assigned to the project or program.
For more information, see Configuring projects and programs.
Default rules for project-level or program-level security are
automatically defined when a project or program is created.
Additional security rules can be configured in Project or
Program by a project administrator or in Access Manager by
a Teamcenter administrator.
For additional information, see Applying project and program
security (Access Manager) rules or the Security Administration
Guide.
Start Project or
Program Click Project in the navigation pane.
Project and Program interface

The Project and Program application interfaces include two distinct windows, the
Project Administration window, which you use to create and administer projects or
programs, and the Smart Folder Administration window, which you use to configure
filtering criteria for displaying project and program data to users in My Teamcenter.
1-2 Project and Program Guide PLM00049 H

Getting started
You can access the Project and Program windows by opening the application and
clicking the links in the navigation pane.
Project and Program menus

Menu commands are available in an initial installation of the Teamcenter software.
File menu
Use the File menu commands to save your data objects, close an application, and
exit the rich client.
Menu command Purpose

Close Closes the application that is currently active in
your Teamcenter window.
Saves the information entered for a selected data
Save object.
Exits the rich client and all of the applications
Exit that are running in the work session.
Edit menu
Use the Edit menu commands to perform basic editing tasks on selected objects,
to view and/or change user settings and preferences, and to change the sequence
of rules in the default access rule tree.
Note
You must have read and write privileges to the objects you want to cut, copy,
or paste.

Removes a selected data object reference
Cut from the current location and places it on the
clipboard. You must have read privileges on the
object and write privileges on its container to
move or remove an object.
Replicates a data object reference in another
Copy location or application. You must have read
privileges for the selected object that you want
to copy. You can also create a copy by dragging
the object to another location or Teamcenter
application.
Moves a data object reference from the clipboard
Paste to the current location in the data object area.
It is important to select the proper destination
for the data object reference before choosing the
Paste menu command. You must have read and
write privileges to the destination object.


Deletes a selected data object from the database.
Delete In addition, you can use the Explore Selected
Components option (available in the Delete
dialog box) to select related objects for deletion
by either selecting them from the tree or
applying type/relation rules.
Changes the sequence of rules in the default
Up access rule tree. You select a rule and click Up to
move the rule up.
Changes the sequence of rules in the default
Down access rule tree. You select a rule and click Down
to move the rule down.
Provides access to the User Setting dialog box
User Setting used to:
View, define, or change company and group
profile information for a user.
View or change your default group, role, or

volume settings.
View or change logging privileges for a user

with dba privileges.
Lets you set preferences for a wide variety of
Options user interface attributes and application display
and processing attributes.
View menu
Use the View menu commands to refresh your display, expand the My Teamcenter
tree, and view object access and user information.

Refresh Reads information from the database and
updates the information displayed in the
workspace area.
Refresh Window Refreshes the information displayed in the
workspace area.
Expand Below Expands all objects in the My Teamcenter tree.
Window menu
Use the Window menu commands to open a new application window and customize
your desktop.

Open Perspective Allows you to open alternate collections of view
panes. This command is not used by default.

Getting started

Show View Allows you to open alternate view panes.
Save Perspective As Lets you save the perspective you have changed.
Reset Perspective Lets you reset a new perspective. It provides
several perspective options to choose.
Close Perspective This command is not used by default. If enabled
at your site, this command allows you to close an
alternate perspective.
Navigation Pane Displays or hides the navigation pane. A check
mark indicates that the navigation pane is
displayed.
Toolbar Displays or hides the toolbar. A check mark
indicates that the toolbar is displayed under the
menu bar.
Preferences Allows you to select preferences, such as color,
size, and width, for different layouts.
Project and Program quick links

There are two links in the Quick Links area of the navigation pane that are specific
to Project and Program:
Project Administration Provides access to the project administration interface
used to create and activate projects and programs, assign
users membership in projects and programs, and designate
project and program administrators and privileged team
members.
Smart Folder Provides access to the smart folder filter configuration
Administration interface used to define filtering criteria based on the
smart folder hierarchy. These filters control how project
and program data is displayed to users.
These links appear in both the Project Administration window and the Smart Folder
Administration window.

Project Administration window
1 Quick Links Displays links to navigate between the

Project Administration and Smart Folder
Administration windows.
For more information, see Project and Program
quick links.
2 Project or Program tree Displays the list of projects or programs in
Teamcenter. New projects and programs
appear in this list.
3 Project or program Displays information about the selected project
definition and rules or program.
If the Definition tab is selected. the properties
of the project or program are displayed. If the
AM Rules tab is selected, the security rules for
the project or program are displayed. If the
Libraries tab is selected, you can view which
data dictionaries are assigned to the project or
assign new dictionaries to the project.
For more information, see Creating and
administering projects and programs and
Applying project and program security (Access
Manager) rules.
Project administration buttons
Button Description
Navigation pane Turns the display of the navigation pane on and off.

Getting started
Button Description
Tree panel Turns the display of the project tree panel on and off.
Class Details Provides information about the project associated with
a class, the name of the parent class, and the library in
which the class is found.
Find groups Searches for a group in the organization tree when
a name or partial name and wildcard characters are
entered in the text box.
Find roles Searches for a role in the organization tree when a role
or partial role and wildcard characters are entered in
the text box.
Find users Searches for a user in the organization tree when a user
name or partial user name and wildcard characters
are entered in the text box.
Refresh tree Refreshes the organization tree.
Select privileged Opens the Select Privileged Team Members dialog box
team members where you can designate privileged team members.
Select a team Opens the Select a Team Administrator dialog box
administrator where you can designate a team member to be a team
administrator.
Project administration tabs
Tab Description
Definition Displays the Definition pane. Use this pane to create the
project or program, to assign project or program team
members, and to designate privileged team members.
AM Rules Displays the Access Manager Rules pane. Use this pane
to apply access rules to a project or program.
Note
Project administrators only have access to the In
Project branch of the rule tree. You cannot modify
other branches of the rule tree from within Project
or Program. In addition, moving the In Project
branch to a different position in the tree requires
Teamcenter administrative privileges and must be
done using the Access Manager application.

Smart Folder Administration window
1 Quick Links Displays links to navigate between the

Project Administration and Smart Folder
Administration windows.
2 Smart folder tree Displays the smart folder hierarchy. The smart
folder hierarchy consists of top-level abstract
folders and low-level data-driven folders.
For more information on how to configure the
smart folder hierarchy, see the Application
Administration Guide.
3 Filter tables Displays the set of filters that apply to the
selected smart folder hierarchy node.
For more information about how to configure
filters, see the Application Administration
Guide.
Smart folder administration buttons
Button Description
Add filter Adds a new row to the filter table that is used to define
additional filters for data-driven folders. Additional
filtering criteria can only be applied to data-driven
folders. Abstract folders in the hierarchy can only
apply a single filter criteria.
Remove filter Removes the selected row from either of the filter
tables.

Getting started
Rich client perspectives and views

Within the Teamcenter rich client user interface, application functionality is
provided in perspectives and views. Some applications use perspectives and views to
arrange how functionality is presented. Other applications use a single perspective
and view to present information.
Note
Your administrator can use the HiddenPerspectives preference to prevent
the display of some Teamcenter perspectives in the rich client.
For information about editing preference values, see the Preferences and
Environment Variables Reference.
If your site has online help installed, you can access application and view help from
the rich client Help menu or by pressing F1.
For more information about rich client perspectives and views, see the Rich Client
Interface Guide.
Basic concepts about Project and Program

Projects and programs organize data and are the basis for granting data access to
project and program team members. The following concepts apply to projects and
programs:
Only privileged team members or regular team members who are explicitly
granted ASSIGN_TO_PROJECT or REMOVE_FROM_PROJECT privileges
can assign data to and remove data from projects and programs.
The TC_project_validate_conditions preference controls which team roles
and access privileges are required to add and delete projects.
Project and program names must be unique within your site. Projects and
programs cannot have the same name as any group at the site.
Data can be assigned to or removed from projects and programs manually or

automatically when the data item is created, and items can be assigned to more
than one project or program.
Propagation rules define the associated data that is implicitly assigned to a

project or program when a primary item is assigned to the project or program.
All items in a complete product structure can be assigned to a project or program

using the update_project_bom utility.
Ownership of data can be assigned to a project or program by configuring the

autoAssignToProject extension in the Business Modeler IDE.
For more information, see Automatically assigning objects to projects and
programs.
Creation and maintenance of data can be restricted to within the context of a

program.

Note
When the program security attribute on a project is set to true, the project is
considered to be a program and is subject to program-level access rules.
Programs offer all the basic features of projects, but in addition you can:
Control access to program data at a higher level than typically applied
to project data.
Share data between programs by assigning the data to multiple programs.
For more information, see the Security Administration Guide.
Project administrators and team members

The following table describes the project administrators and team members who can
create, manage, and use projects and programs.
Team role Definition

Project administrator Teamcenter user with privileges to create and
administer projects and programs.
Project administrators can:
Modify projects and programs.
Delete projects and programs.
Add team members to projects and programs.
Assign privileges to team members.
Remove team members from projects and programs.
Note
These privileges only apply to projects and
programs that the project administrator owns.
Project or program team Project or program team member with privileges to
administrator modify project or program information. These privileges
apply to the project or program metadata, not to the
data assigned to projects and programs.
Project and program team administrators can:
Add team members to projects or programs in which
the team administrator is also a member.
Remove team members from projects or programs

in which the team administrator is also a member.
Note

Getting started
Team role Definition
There can be only one project or program team

administrator per project or program. However,
the project administrator can change the team
administrator for a project or program at any
time.
Privileged team members Project or program team members with privileges
to assign or remove objects from their projects or
programs.
Team members Team members (users) who do not have privileges to
assign objects to or remove objects from their projects
or programs.
The following diagram illustrates a typical project or program hierarchy.
Project or Program Selected Members
Privileged Team
Team Administrator Team Members
Members
Gordon, Jack Jones, Paul Franklin, Wendy
Belcher, Sarah Tracey, Don
Smith, William
Ownership of data by a project or program

The following concepts apply to ownership of data by a project or program:
Ownership of data by a project or program is established when an object is
created.
Ownership is assigned to the users current project or program. Users can

change the current project in their user session by choosing EditUser Setting
and selecting a project or program from the list.
Users can be prevented from creating an object without an owning project or

program. This can be accomplished in two ways:
o Set the value of the CreateDataWithNoActiveProgram global constant
to false.
o Configure the autoAssignToProject extension in the Business Modeler

IDE to automatically assign objects to projects upon creation.
Owning project or owning program can be used as a basis for controlling access
to data.
Once established, the relationship between an object and its owning project can
only be broken if the TC_allow_remove_owning_project preference is set to
allow users to remove objects from owning projects.

Assigning data to projects and programs

End users can manually assign data objects to projects and programs. In addition,
you can configure Teamcenter to automatically assign related objects to a project
or program when the primary object is assigned to the project or program, and you
can use the update_project_bom utility to assign or remove objects in a product or
manufacturing structure to or from a project or program. Teamcenter can also be
configured to automatically assign data objects to projects and programs when the
object is created.
Data objects can be assigned to projects and programs in one of three ways:
Manually assigned to projects or programs by users who are designated as
privileged team members. Privileged team members include:
o Project or program team administrator
o Privileged team members

Note
Additional project or program security can be achieved using the
ASSIGN_TO_PROJECT and REMOVE_FROM_PROJECT
privileges. The exact behavior of these privileges is controlled by the
TC_project_validate_conditions site preference.
Automatically assigned to projects or programs when the object is created. When

a new item revision is created, it is automatically assigned to the project or
program in which the user is currently working.
Teamcenter administrators define which objects can be automatically assigned
to projects and programs using the Business Modeler IDE to configure the
autoAssignToProject extension located in the Extension Definitions folder
under Rules.
Automatically assigned to projects or programs when the primary object is

assigned to the project or program. Project and program propagation rules
determine which secondary objects are assigned to a project or program when a
primary object type is assigned.
You can use the update_project_bom utility to assign or remove objects in a

product or manufacturing structure to or from a project or program.
Assigning data to and removing data from projects and programs

Data objects are assigned to and removed from projects and programs by users
designated as privileged team members or by users to whom assign and remove
privileges have been specifically granted by access control entries. Data can be
assigned to projects and programs when working in the following applications:
My Teamcenter
Change Viewer
Change Manager
Multi-Structure Manager

Getting started
Structure Manager
Part Planner
Plant Designer
Manufacturing Process Planner
The assignment of secondary objects to projects and programs and the automatic
assignment of objects to projects and programs must be configured by a Teamcenter
administrator. The assignment of BOM data to projects and programs is performed
by a Teamcenter administrator using the update_project_bom utility.
Basic tasks using Project and Program

Project and Program are administrative applications used to perform the following
tasks:
Define projects and programs.
Assign team members to projects and programs.
Designate team members as project or program team administrators and

privileged team members.
Configure Access Manager rules to implement project-level or program-level

security.
Configure smart folder filtering.
The tasks performed in Project or Program are only a subset of those required to
administer project-level or program-level security.
For information about administering and configuring project-level or program-level
security, including basic tasks and implementation examples, see the Security

Chapter
2 Creating and administering

projects
Creating and administering projects and programs . . . . . . . . . . . . . . . . . . . . 2-1
Project and program creation and administration process . . . . . . . . . . . . . . . . 2-1
Search for a project or program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
Create a new project or program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Create a project or program based on an existing project or program . . . . . . . . 2-3
Assign groups of users to a project or program . . . . . . . . . . . . . . . . . . . . . . . . 2-3
Assign individual users to a project or program . . . . . . . . . . . . . . . . . . . . . . . 2-4
Designate a project or program team administrator . . . . . . . . . . . . . . . . . . . . 2-5
Assign privileged team members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5
Set a users default project or program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5
Modify existing projects and programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6
Delete a project or program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6
Activating and deactivating projects and programs . . . . . . . . . . . . . . . . . . . . 2-7

Deactivate a project or program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7
Activate a project or program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7
Importing and exporting project or program data in a Multi-Site Collaboration

environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8
Applying project and program security (Access Manager) rules . . . . . . . . . . . . 2-9

Security rules for projects and programs . . . . . . . . . . . . . . . . . . . . . . . . . 2-10
Is Project Member rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10
In Project rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11
Is Program Member rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11
In Current Program rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12
In Inactive Program rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12
In Invisible Program rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12
Is Owned by Program rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13

Configure evaluation of rules that include the Role in Project and Role in Projects
of Object accessors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13
Configure evaluation of the ASSIGN_TO_PROJECT and
REMOVE_FROM_PROJECT privileges . . . . . . . . . . . . . . . . . . . . . . . . 2-14
Associating data dictionaries (libraries) with projects . . . . . . . . . . . . . . . . . . . 2-14

Add a data dictionary to a project or program . . . . . . . . . . . . . . . . . . . . . 2-15
Project and Program Guide PLM00049 H

Chapter
2 Creating and administering

projects
Creating and administering projects and programs

Projects and programs allow you to control user access to Teamcenter data. A project
or program is a grouping of objects that are accessible to users who are designated
as members of the project or program team. Data access rules can be implemented
based on projects and programs, roles in projects and programs, and ownership of
data by a project or program.
For examples of project-level and program-level security implementation, see the
Security Administration Guide.
Project and program creation and administration process

Project creation and administration tasks are preformed in the following order:
1. A project administrator is added to the Project Administration group by the
Teamcenter administrator.
For more information, see the Organization Guide.
2. A project is created with specific groups, users or roles assigned as team

members, privileged team members, and project team administrator.
For more information, see Assign privileged team members, and Designate a
project or program team administrator.
3. The users default project is set.

For more information, see Set a users default project or program.
4. As database objects are created, they are assigned to the project automatically or
manually by privileged team members.
For more information, see Assigning data to projects and programs.
Search for a project or program

1. In the Project or Program application, type a keyword (project or program ID or
name) in the box below the Project or Program tree.
2. Click Find .

Chapter 2 Creating and administering projects
Projects and programs matching the keyword are displayed in the tree.
Tip
To restore the tree display, click Reload .
Create a new project or program

1. Click the Definition tab.
Tip
If the Definition tab is not displayed, click the Project Administration
quick link.
2. Click the Project folder or the Program folder in the tree.
3. In the Definition pane, type a unique identifier for the project or program in the
ID box. (The maximum length for a project or program ID is 64 characters.)
For consistency, the format of the project and program ID and name can be
controlled by naming rules.
For more information, see the Business Modeler IDE Guide.
4. Type a name for the project or program in the Name box. The name must be
unique within your site, and it cannot be the same as the name of any group at
your site. (The maximum length for a project or program name is 32 characters.)
Caution
You cannot use characters such as , % * @, in project and program names.
5. (Optional) Type a description of the project or program in the Description box.
6. Select a status for the project or program:

Active Activates the project or program, which allows users to manage
data within the project or program.
Inactive Inactivates the project or program. Users can see the project or
program, but they cannot manage data within the project or
program.
Inactive and Inactivates the project or program and removes it from the
Invisible users display. Only project administrators can view the data
owned by an inactive and invisible project or program.
7. (Optional) Select the Use Program Security check box.
8. Assign individual users to a project or program or assign groups of users to

a project or program.

Creating and administering projects
Create a project or program based on an existing project or program

You can define a new project or program by copying an existing project or program
that has similar characteristics to the project or program you want to define.
This allows you to leverage existing membership assignments, access rules, and
associated data dictionaries (libraries).
1. In the Definition pane, select an existing project or program from the Project
tree or the Program tree.
Tip
To find a project or program in the tree, type a keyword (project or
program ID or name) and click Find .
2. Type a new project or program ID in the ID box. (The maximum length for a
project or program ID is 64 characters.)
3. Type a new project or program name in the Name box. (The maximum length for
a project or program name is 32 characters.)
Caution
You cannot use characters such as , % * @, in project and program names.
4. Modify any of the project or program settings, such as team member assignments
and Access Manager rules.
5. Click Copy.
The new project or program is created and displayed in the tree.
Assign groups of users to a project or program

You can assign groups of users to a project or program, or you can assign individual
users from various groups as members of a project or program.
Hierarchical group behavior applies to the assignment of users to projects and
programs. If you select a group that has subgroups, all users in the parent group and
subgroups are assigned membership in the project or program.
1. In the Member selection section of the Definition pane, locate the group in the
Organization tree.
Tip
You can search for the group by typing the group name or partial name
and wildcard characters in the box and clicking the Find groups button.
2. Select the group or subgroup and click the Add button.
3. After team members are assigned to the project or program, you can:
Designate a project or program team administrator.

Note
Only project administrators can designate a project or program team
administrator.
Assign privileged team members.
Click Create (when assigning members while defining a new project or

program).
Click Modify (when assigning members to an existing project or program).
Click Copy (when assigning members while creating a new project or

program from an existing project or program).
The symbol appears next to the name of the project or program team members
in the Selected Members tree.
Assign individual users to a project or program

1. In the Member selection section of the Definition pane, locate the users in the
Organization tree.
Tip
You can search for users by entering the user name or partial name and
wildcard characters in the box and clicking the Find users button.
2. Select the user or users and click the Add button.
3. After team members are assigned to the project or program, you can:
Designate a project or program team administrator.
Note
Only project administrators can designate a team administrator.
Assign privileged team members.
Click Create (when assigning members while defining a new project or

program).
Click Modify (when assigning members to an existing project or program).
Click Copy (when assigning members while creating a new project or

program from an existing project or program).
The symbol appears next to the name of the project or program team members
in the Selected Members tree.

Designate a project or program team administrator

1. In the Member selection section of the Definition pane, click Select a team
administrator .
Project or program team administrators can add team members to and remove
team members from projects in which they are members.
2. Select a user from the list and click OK.

Tip
You can search for users in the list by entering the user name or partial
name and wildcard characters in the search box and clicking Perform
find in display .
The symbol appears next to the name of the project or program team
administrator in the Selected Members tree.
Assign privileged team members

1. In the Member selection section of the Definition pane, click Select privileged
team members .
Privileged team members can assign objects to projects or remove objects from
projects.
2. Select users from the Team Members for Selection list and move them to the
Selected Team Members list by clicking . Click to move all users to the
Selected Team Members list.
Tip
You can search for users in the list by entering the user name or partial
name and wildcard characters in the search box and clicking Perform
find in display .
The symbol appears next to the name of the privileged team members in the
Selected Members tree.
Set a users default project or program

Note
The option to assign a default project or program is available only when the
Aerospace and Defense solution is installed.
In addition, users must be assigned to more than one project or program before
you can set a default project or program. If users are only assigned to one
project or program, that project or program is their default project or program.

1. In the Project or Program tree, select a default project or program for the user.
2. In the Member selection section of the Definition pane, right-click the user in the
Selected Members tree, and choose Set Default Project or Set Default Program.
Modify existing projects and programs
1. Select an existing project or program from the Project or Program tree.
2. Modify project or program settings by:

Adding or removing team members.
Assigning a new team administrator.
Assigning or removing privileged team member status.
Changing access rules.
3. Click Modify.
Modifications to the project or program information are saved to the database.
Note
Siemens PLM Software does not recommend changing the project or program
name or ID after data has been assigned to an active project or program.
Delete a project or program

1. Expand the Project or Program tree, and select the project or program that
you want to delete.

Tip
quick link.
3. Click Delete.
The Confirm Delete dialog box appears.
Note
You cannot delete a project or program that has data associated with it.
4. Click Yes.

Activating and deactivating projects and programs

Projects and programs have one of the following statuses that control access to the
data assigned to the project or program:
Active
Project or program data is visible and can be modified by project or program
team members.
Inactive
Project or program data is visible to project or program team members, but
the data cannot be modified.
Inactive and Invisible
Project or program data is invisible and cannot be modified. Only project
administrators can view the data owned by an inactive and invisible project
or program.
Note
Only project administrators can change the status of a project or program.
Deactivate a project or program

Note
You must be a project administrator to deactivate a project or program.
1. Expand the Project or Program tree and select the project or program to be
deactivated.
Tip
quick link.
3. Select a status option, either Inactive or Inactive and Invisible.
4. Click Modify.
Activate a project or program

Note
You must be a project administrator to activate a project or program.
1. Expand the Project or Program tree and select the project or program to be
activated.

Tip
quick link.
3. Select Active in the Status section.
4. Click Modify.
Importing and exporting project or program data in a Multi-Site

Collaboration environment
The following points should be considered when importing and exporting project or
program data in a Multi-Site Collaboration environment:
Project and program IDs are case sensitive and must match exactly across sites.
Siemens PLM Software recommends that you duplicate projects and programs
across sites before attempting to share project or program data.
Users, groups, projects, and programs must be replicated at all sites that share
project or program data. You can use the dsa_util utility to replicate users and
groups. Projects and programs must either be replicated individually, using
the Project or Program application or using the create_project utility, which
enables you to create projects or programs individually based on command line
input or in batch using input from a text file.
When an object that is assigned to a project or program is exported, the

explicitly assigned ID of the project or program is exported along with the other
data associated with the object. When that object (replica) is imported at the
receiving site, it is assigned to the project or program with the same ID. If an
imported object is assigned to multiple projects or programs, it is assigned to the
corresponding projects or programs at the importing site.
Note
If no matching project or program ID is found at the importing site, the
import operation proceeds. Teamcenter does not issue an error message.
When an imported object (replica) is assigned to a project or program, the

associated secondary objects are also assigned to the project or program
according to the propagation rules in effect at the receiving site.
When a replicated object is imported to a remote site by a

user who is not a privileged team member, the value of the
TC_multi_site_project_member_bypass preference determines whether the
object is assigned to the project or program. If the value of the preference is true,
the replicated object is assigned to the defined project or program upon import.
If the value of the preference is false, the replicated object is not assigned to
the project or program upon import.

Note
The TC_multi_site_project_member_bypass preference is not included
in your Teamcenter installation. You must add it to the database.
For information about adding preferences, see the Rich Client Interface
Guide.
Applying project and program security (Access Manager) rules

Project administrators can extend the default security rules, which grant read
access to project or program data to members of the project or program team, on a
project-by-project or program-by-program basis.
Note
Project administrators only have access to the In Project() > Projects
branch of the rule tree.
Using the Project branch in the rule tree, you can:

Grant or deny access to a particular group of users by applying the Owning
Group condition.
Grant or deny access to groups of users based on the groups categorization as

internal (OEM) or external (supplier) by applying the Owning Group Has
Security condition.
Grant access to data assigned to projects by applying the In Project condition.

Note
This rule is applied by default to any object assigned to an active project.
Grant or deny access to users based on their membership in a project by applying

the Is Project Member condition.
Grant or deny access to users based on their membership in a program by

applying the Is Program Member condition.
Deny users access to data if the owning program is not the active program in the
users session by applying the In Current Program condition.
Deny users access to data if the owning program is inactive by applying the In
Inactive Program condition.
Deny users access to data if the owning program is invisible by applying the In
Invisible Program condition.
Grant or deny access to program data by applying the Is Owned By Program

condition.
For more information about configuring project-level security rules, see the Security

Security rules for projects and programs

The Access Manager rule tree delivered as part of the standard Teamcenter
installation includes the following rules related to programs and projects:
In Current Program(false) > Not Current Program
In Inactive Program(true) > Inactive Program
Is Program Member(true) > Not Program Member
In Invisible Program(true) > Invisible Program
In Project() > Projects
Is Project Member(true) > Project Objects
Is Owned By Program() > Projects
For more information about applying program-level and project-level security rules,
see the Security Administration Guide.
Is Project Member rule
The Is Project Member(true) > Project Objects rule specifies whether the
users membership in the project is evaluated. This condition is true only when the
user is a current member of the project.
Note
The Is Project Member(true) > Project Objects rule can only be modified
by an administrator using the Access Manager application. It cannot be
modified from the Project application.
The Project Objects ACL grants project administrators and project team
administrators privileges to modify projects in which they are members. These
privileges apply to the project metatdata, not to the data assigned to projects.
The ACL is defined as follows.
Accessor Type Accessor ID Read Write Delete Change Change

Ownership
Owning User
Role Project
Administrator
Role Project Team
Administrator
World
Note
You can modify the Project Objects ACL to meet the project access
requirements at your site.

For more information about applying project-level security rules, see the Security
In Project rule
The In Project() > Projects rule grants access to data assigned to projects.
This default rule is applied to any object that is assigned to an active project.
The Projects ACL grants read privileges to the data in a project, as follows.
Read
Project Teams
The Project Teams accessor gives all team members read privileges to the data in
a project. For example, if the Design, Validation, and Documentation groups
are selected as a project team, the Project Teams accessor grants privileges to all
members of each group; therefore it is not necessary to use the Group accessor to
grant privileges to each group individually.
The project administrator can create or modify project security rules to meet the
requirements of a specific project by creating a new named ACL for the project or by
adding rules under the In Project condition in the rule tree. Project administrators
can modify rules using Project.
Note
Only an administrator with privileges to use Access Manager can change the
placement of the In Project rule in the AM rule tree. They can also modify
the order of the child nodes of the In Project branch of the rule tree.
For more information about applying project-level security rules, see the Security
Is Program Member rule
The Is Program Member(false) > Not Program Member rule denies read
access to users if the user is not a member of the owning program or shared program.
The Not Program Member ACL denies read access to the data in the program,
as follows.
Read
World
The World accessor denies read access to users if the user is not the member of the
owning program or the shared programs.
For more information about applying program-level security rules, see the Security

In Current Program rule
The In Current Program(false) > Not Current Program rule denies write,
delete, change, and export privileges to users if the owning program of the data is
not the active program for the users session.
The Not Current Program ACL denies the privileges to the data in a program,
as follows.
Read
World
The World accessor denies write, delete, change and export privileges to users if the
owning program of the data is not the active program for the users session.
In Inactive Program rule
The In Inactive Program (true) > Inactive Program rule denies write,
delete, change and export privileges to users if the owning program of the data
is in the inactive state.
The Inactive Program ACL denies write, delete, change and export privileges
to the data in the program, as follows.
Read
World
The World accessor denies write, delete, change and export privileges to users if
the owning program of the data is in the inactive state.
In Invisible Program rule
The Is Invisible Program (true) > Invisible Program rule denies read access
to users if the owning program of the data is in the invisible state.
The Invisible Program ACL denies read access to the data in the program, as
follows.
Read
World

The World accessor denies read access to program data if the program is in the
invisible state.
Is Owned by Program rule
The Is Owned By Program()>Projects rule grants or denies access to data

based on program or project ownership.
The Projects ACL grants read access to the data in the program, as follows.
Read
Project Teams
The Is Owned By Program rule can be configured to enable the exchange of

Aerospace and Defense program data between databases. Exchanging program data
requires that the user initiating the import or export is a member of the program to
which the objects being exchanged are assigned.
For information about configuring the Is Owned By Program rule to support the
exchange of Aerospace and Defense data, see the Aerospace and Defense Solution
Guide.
Configure evaluation of rules that include the Role in Project and Role
in Projects of Object accessors
You can set the AM_PROJECT_MODE preference to configure how the system
considers the users roles in active projects when evaluating access rules that use the
Role in Project or Role in Projects of Object accessors.
The system either:
Evaluates the users roles in the context of all active projects.
Evaluates the users roles in the context of the current project. The users current
project is the project specified for the active Teamcenter session.
Note
To view a users current project, choose EditUser Setting.
For more information about project preferences, see the Preferences and Environment
Variables Reference.
For more information about the Role in Project and Role in Projects of Object
accessors, see the Security Administration Guide.

Configure evaluation of the ASSIGN_TO_PROJECT and

REMOVE_FROM_PROJECT privileges
You can set the TC_project_validate_conditions preference to specify how the
ASSIGN_TO_PROJECT and REMOVE_FROM_PROJECT access privileges are
validated in conjunction with privileged project membership.
Note
This preference is not included in your Teamcenter installation. You must
add it to the database.
For information about adding preferences, see the Rich Client Interface Guide.
In addition, this preference does not apply to the assignment
of replicated objects during an import operation. The
TC_multi_site_project_member_bypass controls the privileges
required to assign replicated objects to projects upon import.
You can configure the following project access scenarios:

Users who are privileged project members can assign objects to or remove
objects from projects.
Users who are either privileged project team members or who have specific
ASSIGN_TO_PROJECT and REMOVE_FROM_PROJECT privileges can
assign objects to and remove objects from projects.
Users who are members of the project, but who are not privileged team members,
must have ASSIGN_TO_PROJECT and REMOVE_FROM_PROJECT
privileges to assign objects to and remove objects from projects.
Users who are privileged team members and also have ASSIGN_TO_PROJECT
and REMOVE_FROM_PROJECT privileges can assign objects to or remove
objects from projects.
For more information about project preferences, see the Preferences and Environment
Variables Reference.
For more information about configuring access privileges, see the Security
Associating data dictionaries (libraries) with projects

Data dictionaries are central repositories for key building blocks or components of
designs used in typical functional and logical design activities. These repositories
make it easy to reuse components in multiple designs across projects or programs.
Data dictionaries are modeled as libraries in the Classification application and can
be associated with projects or programs, which allows designers who are project
members to add data from the dictionary to function, logical, or physical model
structures.

Tip
Multiple data dictionaries (libraries) can be associated with a single project or
program. In addition, a single data dictionary can be associated with multiple
projects or programs.
For more information about working with data dictionaries, see Getting Started with
Systems Engineering or Getting Started with Mechatronics Process Management.
Add a data dictionary to a project or program

Data dictionaries are modeled as libraries using Classification classes. In this
procedure, data dictionaries are referred to as libraries.
1. In the Project Administration window, select a project in the Project tree.
2. Click the Libraries tab.
3. In the Hierarchy pane, expand the tree until you locate the library that you want
to associate with the selected project.
4. Select the library in the hierarchy, add it to the pane on the right side of the
window, and click the Save button located between the panes.
The library (data dictionary) is now associated with the project. Designers who are
project members can add data from the dictionary to model structures while working
in Systems Engineering or Structure Manager.

Chapter
3 Configuring projects and

programs
Configuring projects and programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
Defining default naming rules for projects . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
Assigning secondary objects to projects and programs . . . . . . . . . . . . . . . . . . 3-2

Secondary object propagation rules for projects and programs . . . . . . . . . . 3-2
Set relation propagation rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
Assigning BOM data to projects and programs . . . . . . . . . . . . . . . . . . . . . 3-3
Automatically assigning objects to projects and programs . . . . . . . . . . . . . . . . 3-4

Understanding the implications of the autoAssignToProject extension on
propagation rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
Restricting data creation to within the context of a project or program . . . . . . . 3-7
Controlling assignment of replicated (imported) data to projects . . . . . . . . . . . 3-7
Setting the current project for new Teamcenter sessions . . . . . . . . . . . . . . . . . 3-7
Selecting different object property values based on project assignment . . . . . . 3-8
Displaying projects to users based on current group and role . . . . . . . . . . . . . 3-8
Using pseudo folders to organize the display of objects in projects . . . . . . . . . . 3-8
Project and program preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8

Chapter
3 Configuring projects and

programs
Configuring projects and programs

Configuring projects and programs includes the following tasks:
Configuring naming rules to control the ID and name format when projects
are created.
Setting preferences that control different aspects of project and program

behavior.
Configuring how the assignment of secondary objects is handled when a primary

object is assigned to a project or program.
Using the update_project_bom utility to assign BOM data to a project.
Configuring the autoAssignToProject extension (using the Business Modeler

IDE) to automatically assign objects to projects when they are created.
Configuring the list of values displayed for the property of an object based on the
project that the object is assigned to.
Restricting the creation of data to within the context of a project or program by

setting the CreateDataWithNoActiveProgram global constant.
Applying access rules to project and program data.
Defining default naming rules for projects

Naming rules control the format of project names and IDs, allowing you to apply
custom naming conventions to your projects. While naming rules are not required
to use projects to organize and secure your data; they ensure that projects are
identified in a consistent manner. Naming rules are created and attached to project
properties using Business Modeler IDE.
For more information, see the Business Modeler IDE Guide.

Chapter 3 Configuring projects and programs
Assigning secondary objects to projects and programs

Teamcenter administrators can configure Teamcenter to implicitly assign related
objects to a project or program when the primary object is assigned to a project or
program.
For example, a propagation rule can be defined to assign datasets (secondary objects)
to a project or program when it has a specific relationship to an item revision
(primary object) assigned to the project or program. This is level-one propagation.
Note
Level-one propagation implicitly propagates forms when the dataset in which
they are contained is assigned to a project.
Secondary object propagation rules for projects and programs

The secondary object propagation rules are defined by relation type and apply to any
secondary object associated with a primary object by one of the included relation
types. By default, the following relation types are included for propagation:
Specifications
Manifestations
AltReps
Affected Item
Attaches
Solution Item
The propagation rules are valid when the following actions take place in Teamcenter:
When an item or item revision is assigned to a project or program, the related
objects are also assigned.
When a related object is cut from the object assigned to the project or program,
the related object is removed from the project or program.
When an attachment (related object) is pasted to an object, the attachment is

assigned to the project or program to which the primary object is assigned.
When an item is imported in a Multi-Site Collaboration environment.
When an imported object (replica) is assigned to a project or program, the

associated secondary objects are also assigned to the project or program
according to the propagation rules in effect at the receiving site.
Generally, you propagate secondary items that are related to the primary item by a
Specifications, Manifestations, Attaches, or AltReps relationship. Secondary
items related to primary items by Requirements and References relationships
generally do not need to be implicitly propagated to the project or program.
Set relation propagation rules

1. In the Project or Program application, choose EditOptions.

Note
Propagation rules apply to the entire site, and they can only be defined by
a user with dba privileges.
2. Select the Project or Program node in the Options tree.
3. In the Relation Propagation Rules section of the Options dialog box, add the
relation types to the Include Relations list. These are the relation types by
which secondary objects must be related to primary objects to be automatically
(implicitly) assigned to a project or program.
4. (Optional) Select Include BOMView/BOMView Revision for Item/Item Revision

to propagate BOM views and BOM view revisions when an item or item revision
is assigned to a project or program.
Note
BOM views and BOM view revisions are attached to items and item
revisions by attribute reference rather than by relation type.
5. Click OK or Apply.
Assigning BOM data to projects and programs

Objects contained in a product or manufacturing structure can be assigned
to or removed from projects or programs in batch mode by running the
update_project_bom utility.
Note
Only objects that were added to the project or program using the utility can
be removed using the utility.
The utility can be used to assign or remove objects at either the level-one or level-two
propagation level.
Level-one propagation processes BOM objects and their attached datasets. The
following structure (BOM) represents the focus of level-one propagation:
Item
Item revision
Dataset
This structure can be nested at multiple levels within a BOM. The depth to which
the utility processes the structure is determined by the depth argument. In
addition, the utility provides arguments that allow you to specify the type of object,
either item or item revision, to be used for level-one propagation, the revision rule by
which the BOM should be configured, and the unit number, effectivity date, and ID
of the end item associated with the revision rule. Variant rules can also be applied to
the structure before propagation.

Note
Objects assigned to a project or program as part of level-one propagation
are implicitly assigned to the project or program. Therefore, any change to
the relationship between the primary and secondary objects is reflected in
the project or program.
Level-two propagation processes dependent objects related to the datasets associated

with level-one objects. The following data model is supported for level-two
propagation:
Item
Item revision
Dataset Relation type Item revision
Dataset Relation type Dataset
Dataset Relation type Item
Note
Dependent objects assigned through level-two propagation are explicitly
assigned to the project or program. Objects that are explicitly assigned to a
project or program must also be explicitly removed. If the BOM object to
which the secondary object is related is removed from the project or program,
the dependent object remains assigned to the project or program.
The types of dependent objects that can be configured and processed

by the utility for level-two propagation are specified by setting the
TC_project_propagate_from_dataset preference.
The propagation level is determined by the level argument when you run the utility.
Automatically assigning objects to projects and programs

Teamcenter administrators can configure Teamcenter to automatically assign
certain types of objects to a project or program when the specified objects are created
by privileged team members.
The following object types can be configured for automatic assignment:
Item and item revision subtypes, such as engineering changes and documents
Forms
Datasets
For example, Teamcenter can be configured to assign new item revisions to the
current project or program of the user who creates the new item revision.
Note
Your current project or program is defined in the User Settings dialog box.
You can choose EditUser Setting to change your current project or program.

Use the Business Modeler IDE to configure the autoAssignToProject extension.

This extension defines the type of objects that are automatically assigned to the
users current project or program when the specified object is created. When you
assign an object to a project automatically, the project becomes the Owning Project.
Note
To be able to remove an object from the owning project, add the
TC_allow_remove_owning_project site preference and set it to true,
which allows you to right-click the object and choose ProjectRemove.
For more information about understanding the implications of the

autoAssignToProjectextension on propagation rules extension, see the Business
Modeler IDE Guide.
Understanding the implications of the autoAssignToProject extension

on propagation rules
The autoAssignToProject extension automatically assigns the selected workspace
object to the users current project, as defined by the work context or user settings.
The following table describes the types, operations, and extension points for which
the autoAssignToProject extension is valid.
Type Operation Extension point

Item and all subtypes Create Post-Action
of item
Item revision and Revise Post-Action
all subtypes of item
revision Save As To Existing Item
Create BaseLine Revision
Deep Copy
Create Revision
Dataset and all Save Post-Action
subtypes of dataset
Form and all subtypes Save Post-Action
of form
Configuring the autoAssignToProject internal extension for a business object has

implications on the project propagation rules. Project propagation rules determine
which secondary objects are assigned to a project when a primary business object is
assigned. When there is a conflict between a propagation rule and the execution of
the autoAssignToProject extension, the extension takes precedence.

Note
If a current project is not specified for the user, this extension is ignored
and the object is not automatically assigned. In addition, when the
autoAssignToProject extension is configured for an item or ECO, the
project name is preselected in the Assign to Projects page of the item or
ECO create, revise, and save as dialog boxes.
If you want users to be able to remove objects from an owning project,

you must create the TC_allow_remove_owning_project preference
before using the autoAssignToProject extension. If this preference is
not set, objects assigned to owning projects cannot be removed using the
ProjectRemove command.
The following points must be considered when implementing the

autoAssignToProject extension:
The autoAssignToProject extension applies only to newly created objects;
whereas, propagation of related objects to projects occurs whenever a relation
between two objects is created, modified, or deleted.
The autoAssignToProject extension explicitly assigns objects to projects;

therefore, the objects can only be removed from the project by explicitly
right-clicking the object in the Teamcenter rich client and choosing
ProjectRemove.
Propagation rules implicitly assign secondary objects to projects. Therefore,

when the primary object is explicitly removed from the project, the secondary
object is also removed from the project.
The following scenarios illustrate the relationship between extensions and

propagation rules when assigning objects to projects.
Scenario Project assignment behavior

The autoAssignToProject extension Both objects are automatically assigned to
is configured for types P (primary the current project, regardless of whether
object) and types S (secondary the Requirements relation is specified in
object). A user creates an object of the propagation rule list.
type P and an object of type S related
by the Requirements relation.
The autoAssignToProject extension The object of type P is automatically
is configured for types P (primary assigned to the current project based on
object), but not for types S (secondary the autoAssignToProject extension. If
object). A user creates an object of the Requirements relation is specified
type P and an object of type S related in the propagation rule list, the type S
by the Requirements relation. object is also assigned to the project. If the
Requirements relation is not specified in
the propagation rule list, the secondary
object is not assigned to the project.

Scenario Project assignment behavior

The autoAssignToProject Both the primary and secondary object
extension is configured for types are automatically assigned to the project
P (primary object) and types S based on the configuration of the extension,
(secondary object). In addition, the resulting in an explicit assignment rather
Requirements relation is defined than the implicit assignment that occurs
as a propagation rule. The user when an object is assigned to a project based
creates an object of type P and on propagation rules.
an object of type S. After creating
the objects, the user attaches the
secondary object to the primary
object using the Requirements
relationship.
Restricting data creation to within the context of a project or program

Set the CreateDataWithNoActiveProgram global constant to false to restrict
data creation to within the context of a program. When this constant is set to false,
users can only create data when:
An active program is set for the user session.
Program-level security is enabled for that program.

For more information about enabling program-level security, see Create a new
project or program.
To allow data creation outside the context of a program, set the global constant
CreateDataWithNoActiveProgram to true.
Controlling assignment of replicated (imported) data to projects

By default, users who import replicated objects into a database at a remote site must
be privileged project members for the imported data to be assigned to projects. If the
user is not a privileged project member, the import operation cannot assign the data
to an existing project. You can use the TC_multi_site_project_member_bypass
preference to bypass this behavior.
The TC_multi_site_project_member_bypass preference is not included in your
Teamcenter installation. You must add it to the database.
For information about adding preferences, see the Rich Client Interface Guide.
Setting the current project for new Teamcenter sessions

You can determine whether users current project settings persist from one
Teamcenter session to the next by setting the TC_set_current_project preference.
The default behavior is to save the users current project setting and apply it the
next time they log on to Teamcenter.
For more information, see the Preferences and Environment Variables Reference.

Selecting different object property values based on project assignment

As a Teamcenter administrator, you can configure the system so that users see
different lists of property values based on the project that the object is assigned to.
For example, if an item is assigned to project A, the list of values attached to the
Color property shows one set of colors to choose from, and if the item is assigned
to project B, the list of values attached to the Color property shows another set
of colors.
These conditional lists of values (LOVs) are defined in the Business Modeler IDE.
The conditions can only be defined using the owning_project, project_list,
owning_user, and owning_group project properties.
For more information about defining conditional lists of values, see the Business
Modeler IDE Guide.
Displaying projects to users based on current group and role

You can limit which projects are displayed to users throughout the Teamcenter
interface, for example, in the New Item dialog box or the Assign an Object to a
Project dialog box. By default, all active projects in which the user is a privileged
team member are displayed. You can set the TC_show_all_user_projects
preference to limit the display to only the projects that correspond to the users
current group and role.
Using pseudo folders to organize the display of objects in projects

You can specify properties to be displayed as pseudo folders under a node of the
TC_Project business object. After you specify a pseudo folder, all objects defined in
that property are shown in the folder under the TC_Project object.
Project and program preferences

The following preferences control the behavior of projects and programs.
AM_PROJECT_MODE
TC_project_validate_conditions
TC_multi_site_project_member_bypass
TC_project_propagate_from_dataset
TC_Project_DefaultChildProperties
TC_Project_PseudoFolder
TC_Program_Preferred_Items_relation_primary

TC_set_current_project
TC_show_all_user_projects
TC_current_role

Chapter
4 Configuring smart folder filtering
Apply smart folder filtering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
Viewing project data in My Teamcenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2

Using project smart folder filtering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
Applying project smart folder filtering . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4

Chapter
4 Configuring smart folder filtering
Apply smart folder filtering

Smart folders provide a mechanism for configuring arbitrary subdivisions of data
within a project or program based on functional and subfunctional units. Smart
folders are pseudo folders configured in a hierarchical structure; they are not
physical folder objects in Teamcenter.
A project or program hierarchy that defines the abstract and data-driven folders
used to filter project or program data based on object type and attribute is created in
Business Modeler IDE. This filtering controls what is displayed when users access
their project or program in the My Projects view, and it enables them to easily locate
data in large projects and programs.
After the folder hierarchy is defined in Business Modeler IDE, you can choose object
types, properties, and property values to filter data for display.
You can also filter project or program data in the absence of a smart folder hierarchy
by applying filters within a project or program.
1. In Project or Program, click the Smart Folder Administration quick link.
2. Expand the hierarchy tree to display the smart folders.

Note
If a smart folder hierarchy is not defined, only the project or program
objects are displayed in the tree.
3. Select a smart folder that you want to use to apply filtering criteria.
4. Select the Contribute to Filter Criteria check box.

The smart folder name appears in the filter table beneath the check box.
5. Select an object type from the Type list.
6. From the Property list, select a property corresponding to the object type.
When the project or program hierarchy is evaluated, the smart folder funnels
project or program data of the specified type and property value to the users
project or program display.
7. Continue down the tree, selecting folders and applying object types and
properties as filtering criteria.
The cumulative filter criteria is displayed in the table at the bottom of the
window.

Chapter 4 Configuring smart folder filtering
8. When you reach the leaf node (data driven folder) that displays the project or
program data, you can define additional filter criteria as follows:
a. Select the data driven folder in the tree.
b. Select the Contribute to Filter Criteria check box.

The folder name appears in the filter table beneath the check box.
c. Select an object type from the Type list.
d. From the Property list, select a property corresponding to the object type.
e. Click Add a filter button to add a new row to the filter table that is used
to define additional filters for data-driven folders.
Note
Additional filtering criteria can only be added to data-driven folders.
Abstract folders in the hierarchy only accept a single filter criterion.
For more information about configuring filters, see the Application
f. In the new row of the table, select the object type and property.
g. Enter a value for the property in the Value column.

When setting values to filter for user and group properties, you can filter
project data for the logged-on user or group by setting the value to $USER
or $GROUP. In addition, you can filter data based on properties that have
a null value by entering $NULL.
9. Click Save Filter Settings.

The filter settings are applied to the project. In the My Projects view, the data is
displayed according to this filter criteria.
Viewing project data in My Teamcenter

You can click the My Projects link in the navigation pane to view your projects and
associated data. This view is determined by the project administrator.

Configuring smart folder filtering
The My Projects view is similar to My Teamcenter views but with the following
differences:
Project Smart Folder Hierarchy
Displays the smart folder hierarchy as configured by the administrator, and
provides a filter button to display the Apply filters dialog box.
Note
The Apply filters dialog box lets you apply filtering based on source types,
properties, and values.
You select a project from the hierarchy to display information in the other My
Projects panes.
Summary
The summary view consists of two tabs:
o Project Data
Displays the filtered objects assigned to the selected project.
o Team
Displays the project team associated with the selected project.
Note
The content of the My Projects view varies when you install Consumer
Packaged Goods.
For more information, see Getting Started with Consumer Packaged Goods.
Using project smart folder filtering

The following considerations apply to project filtering:
It is not necessary to have an established smart folder hierarchy to apply filters
to your project data. In the absence of a smart folder hierarchy, project objects
are treated as abstract folders.

Chapter 4 Configuring smart folder filtering
Filters defined in My Teamcenter cannot be saved for future use. You must add
and remove them as required.
Multiple filter criteria can be applied to a data-driven smart folder . When

multiple filter criteria are applied, all data that meets the criteria appears under
the project or program. A logical OR is applied between each row in the filter
table to determine the display results.
Only one filter criteria can be applied to an abstract smart folder . If multiple
filters are applied to an abstract smart folder, no project data is displayed.
Applying project smart folder filtering

1. Click My Projects in the Quick Links section of the navigation pane.
The My Projects view appears.
2. In the My Projects view, expand a project object to view the data associated
with the project.
Note
Objects are displayed according to the project smart folder hierarchy
configuration defined by the project administrator and/or by any filters
that you apply.
If a smart folder hierarchy is configured for your project, you see folders
when you expand your project. Expand these folders to reveal your project
data.
3. To apply filters, select the project object in the My Projects view.

The Summary view shows details of the project object. The contents of the
Summary view vary according to the type of object selected.
4. Click the filter button to apply a filter to refine the list of objects for the
selected project.
The Apply filters dialog box appears.
5. Click the Add a filter button to populate a row in the table.

Configuring smart folder filtering
6. Choose filter criteria by clicking the Source Type, Property, and/or Value cells
and selecting a value from the list.
For example, you can add a filter to display the project data owned by the
Engineering group.
Note
You can remove rows from the filter table by clicking the Remove the
selected filter button . Click the Clear the filters button to remove
all values from the table.
7. Click OK to apply the filter.

The list of objects in the My Projects view is updated to reflect the applied filters.
Note
The filters you apply remain until you remove them. However, you cannot
save a filter configuration and retrieve it for future use.

Appendix
A Glossary

Appendix
A Glossary
access control list (ACL)

Access Manager component that contains a list of accessors and the privileges
granted, denied, and not set for each accessor.
Access Manager (AM)

Teamcenter application that enables the system administrator to grant users access
to Teamcenter objects.
accessor
Access Manager component that grants or denies privileges to clusters of users who
share certain common traits (for example, perform the same function or work on
the same project).
BOM view
Teamcenter object used to manage product structure information for an item.
BOM view revision (BVR)

Workspace object that stores the single-level assembly structure of an item revision.
Access can be controlled on the structure (BOM view revision) independently of
other data. BOM view revisions are meaningful only in the context of the item
revisions for which they are created.
Business Modeler IDE

Teamcenter application that enables a customer to define the following data model
objects: business objects, classes, attributes, lists of values, and rules.
BVR
See BOM view revision (BVR).
Change Viewer
Teamcenter application used to manage the process of controlling changes to a
products definition and configuration. Change Viewer provides an auditable history
of the objects used in a process, making an objects uses traceable. A site can use
Change Viewer to propose, incorporate, review, and approve changes. Change
Viewer can also be used to track and report change history and to notify members of
changes to their organization.
PLM00049 H Project and Program Guide A-1

Appendix A Glossary
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.
extension
Method or listener implemented for an extension point.
extension rule
Business rule that adds predefined behavior to a business objects operation and fires
as a precondition, preaction, or postaction.
group (Organization)
Organizational grouping of users at a site. Users can belong to multiple groups
and must be assigned to a default group.
hierarchy
Structure in which each node can have only one parent but possibly multiple siblings
and children.
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 relation
Description of an association between a Teamcenter item and a piece of information
that describes or is related to the item.
item revision
Workspace object generally used to manage revisions to items.
item revision relation

Description of an association between a Teamcenter item revision and a piece of
information that describes or is related to the item revision.
Manufacturing Process Planner

Teamcenter manufacturing process management application that enables a user to
design a plan detailing how to manufacture a product.
Multi-Structure Manager
Teamcenter application that enables users to view and manipulate data in a specific
context.
A-2 Project and Program Guide PLM00049 H

Glossary
My Teamcenter
Teamcenter rich client application that is the main access point for managing
product information. My Teamcenter provides the functionality for creating objects
in the Teamcenter database, querying the database for objects, checking in and
checking out objects, and managing tasks. Users can also open objects, automatically
launching the related application.
Each user has a personal My Teamcenter window that displays product information
as graphical objects. Although users share product information across the enterprise,
they organize this information individually in personal workspaces.
named ACL
Named group of access controls. See also access control list (ACL).
named reference
File types that are managed by a dataset. Datasets are the only workspace objects
that use named references.
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 application
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
companys 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.
owner
User that owns an object, initially the user who created it. Ownership can be
transferred from the owner to another user. An object owner usually has privileges
that are not granted to other users (for example, the privilege to delete the object).
owning group
Group that owns an object, usually the group of the user creating the object. Because
users commonly share data with other members of a group, additional privileges may
be granted to the owning group (for example, the privilege to write to the object).
Part Planner
Teamcenter manufacturing process management application that enables a user to
design a plan detailing how to manufacture a part.
Plant Designer
Teamcenter manufacturing process management application that allows users to
design, modify, import, and export a factory structure.

Appendix A Glossary
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.
privileged team member

Project team member with privileges to assign and remove objects from that
project. Compare with project team member.
program
Basis for identifying a group of objects available to multiple organizations, such
as program teams, development teams, suppliers, and customers for a particular
piece of work.
Program application
Teamcenter application used to define programs and assign program team members,
program team administrators, and privileged team members.
program team administrator

Program team member with privileges to modify program information and program
team members for that program. Only one program team administrator is allowed
per program.
program team member

Team member (user) who does not have privileges to assign objects to or remove
objects from their programs. Compare with privileged team member.
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.
Project administrator
Teamcenter super user with unrestricted access to administer projects they create
using the Project application. A Project administrator creates, modifies, and deletes
project information and team members.
Project application
Teamcenter application used to define projects and assign project team members,
project team administrators, and privileged team members.
project team administrator

Project team member with privileges to modify project information and project team
members for that project. Only one project team administrator is allowed per project.
project team member

Team member who does not have privileges to assign objects to or remove objects
from their projects. Compare with privileged team member.
relation
Description of an association between a Teamcenter object and a piece of information
that describes or is related to the object.

Glossary
rich client
Java-based user interface to Teamcenter installed on user workstations. The rich
client accesses Teamcenter databases using a remote or local server.
role
Function-oriented cluster of users that models skills and/or responsibilities. The
same roles are typically found in many groups. In Access Manager, role is an accessor
used to grant privileges to all users with the same skills and/or responsibilities
regardless of project.
role in group
Specific role in a specific group. In Access Manager, role in group is an accessor
used to grant privileges to all users with the same skills and/or responsibilities
in the same group.
role in owning group

Specific role in the objects owning group. In Access Manager, role in owning
group is an accessor used to grant privileges to users with the same skills and/or
responsibilities on the same project. For example, all designers in the owning group
are usually granted write privilege on their development data.
root
Starting point of a hierarchy. Hierarchies are usually displayed as hanging trees
with the root of the structure at the top and the leaves at the bottom.
rules-based protection
Conditions or rules that control who can or cannot access objects. These rules are
global (that is, they affect the entire Teamcenter site) and are enforced by the Access
Manager. These rules are defined by a system administrator.
rule tree
Access Manager component the system administrator uses to grant users access to
Teamcenter objects. It is a tree of rules and access permissions that when processed
determines the access that each user has to a specified object.
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.
Structure Manager
Teamcenter application that enables creation of generic product structures that can
be configured to show the product structure that is in production, effective on a
certain date, used by a particular customer, and so forth. Structure Manager enables
creation and modification of a product structure and its associated occurrence data,
display of a product structure in a multilevel indented format, and viewing graphics
tightly coupled to the structure for easy identification of a component by location in
the structure or in the embedded viewer.

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.
work context
Object containing user, group, role, and project requirements for a particular task.
Work contexts streamline the definition of the correct user settings required to
perform tasks. For example, a user typically assigned three types of tasks can create
three work contexts reflecting the required group/role settings. Rather than logging
out and logging back in with the required group/role settings, right-clicking a task
displays the users defined work contexts. Selecting the appropriate work context
automatically changes the users group/role settings. Work contexts can also define
the current project, if project functionality is used at the site.

Index
A E
Activating a program . . . . . . . . . . . . . . . 2-2 Enabling Program . . . . . . . . . . . . . . . . . 1-2
Activating a project . . . . . . . . . . . . . . . . 2-2 Enabling program security . . . . . . . . . . . 2-2
AM Rules tab . . . . . . . . . . . . . . . . . . . . 1-7 Enabling Project . . . . . . . . . . . . . . . . . . 1-2
Assigning BOM data to programs . . . . . . 3-3 Evaluating Role in Project accessor . . . . 2-13
Level-one propagation . . . . . . . . . . . . 3-3 Evaluating Role in Projects of Object
Level-two propagation . . . . . . . . . . . . 3-4 accessor . . . . . . . . . . . . . . . . . . . . . . 2-13
Assigning BOM data to projects . . . . . . . 3-3
Level-one propagation . . . . . . . . . . . . 3-3 I
Level-two propagation . . . . . . . . . . . . 3-4
update_project_bom utility . . . . . . . . . 3-3 ID box . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Assigning related objects to programs . . . 3-2 In Current Program rule . . . . . . . . . . . 2-12
Assigning related objects to projects . . . . 3-2 In Inactive Program rule . . . . . . . . . . . 2-12
Assigning team members In Invisible Program rule . . . . . . . . . . . 2-12
Groups . . . . . . . . . . . . . . . . . . . . . . . 2-3 Inactive Program ACL . . . . . . . . . . . . . 2-12
Hierarchical group behavior . . . . . . . . 2-3 Invisible Program ACL . . . . . . . . . . . . 2-12
autoAssignToProject extension . . . . . 3-43-5 Is Owned By Program rule . . . . . . . . . . 2-13
Automatically assigning data to projects Is Program Member rule . . . . . . . . . . . 2-11
autoAssignToProject extension . . . 3-43-5
Eligible data types . . . . . . . . . . . . . . . 3-4 L
Level-one propagation . . . . . . . . . . . . . . 3-3
C Level-two propagation . . . . . . . . . . . . . . 3-4
Configure program Level-two propagation preference . . . . . . 3-4
Restrict data creation to program
context . . . . . . . . . . . . . . . . . . . . . 3-7 M
Configuring Program . . . . . . . . . . . . . . . 1-2
Configuring Project . . . . . . . . . . . . . . . . 1-2 Menu commands
Configuring smart folder filtering . . . . . . 4-1 Close . . . . . . . . . . . . . . . . . . . . . . . . 1-3
Constants Close Perspective . . . . . . . . . . . . . . . . 1-5
CreateDataWithNoActiveProgram . . . . 3-7 Copy . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
Copying an existing program . . . . . . . . . 2-3 Cut . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
Copying an existing project . . . . . . . . . . 2-3 Delete . . . . . . . . . . . . . . . . . . . . . . . . 1-4
Current project . . . . . . . . . . . . . . . . . . . 3-7 Down . . . . . . . . . . . . . . . . . . . . . . . . 1-4
Exit . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
Expand Below . . . . . . . . . . . . . . . . . . 1-4
D Navigation Pane . . . . . . . . . . . . . . . . 1-5
Deactivating a program . . . . . . . . . . . . . 2-2 Open Perspective . . . . . . . . . . . . . . . . 1-4
Deactivating a project . . . . . . . . . . . . . . 2-2 Options . . . . . . . . . . . . . . . . . . . . . . . 1-4
Definition pane . . . . . . . . . . . . . . . . . . . 1-7 Paste . . . . . . . . . . . . . . . . . . . . . . . . 1-3
Description box . . . . . . . . . . . . . . . . . 2-2 Preferences . . . . . . . . . . . . . . . . . . . . 1-5
ID box . . . . . . . . . . . . . . . . . . . . . . . . 2-2 Refresh . . . . . . . . . . . . . . . . . . . . . . . 1-4
Name box . . . . . . . . . . . . . . . . . . . . . 2-2 Refresh Window . . . . . . . . . . . . . . . . . 1-4
Definition tab . . . . . . . . . . . . . . . . . . . . 1-7 Reset Perspective . . . . . . . . . . . . . . . . 1-5
Description box . . . . . . . . . . . . . . . . . . . 2-2 Save . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
PLM00049 H Project and Program Guide Index-1

Index
Save Perspective As . . . . . . . . . . . . . . 1-5 Inactive Program ACL . . . . . . . . . . . 2-12

Show View . . . . . . . . . . . . . . . . . . . . 1-5 Invisible Program ACL . . . . . . . . . . . 2-12
Toolbar . . . . . . . . . . . . . . . . . . . . . . . 1-5 Is Owned By Program rule . . . . . . . . 2-13
Up . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4 Is Program Member rule . . . . . . . . . . 2-11
User Setting . . . . . . . . . . . . . . . . . . . 1-4 Not Current Program ACL . . . . . . . . 2-12
Modifying an existing program . . . . . . . . 2-6 Not Program Member ACL . . . . . . . . 2-11
Modifying an existing project . . . . . . . . . 2-6 Projects ACL . . . . . . . . . . . . . . . . . . 2-13
My Projects view Program-level security tasks
Using . . . . . . . . . . . . . . . . . . . . . . . . 4-4 Configuring automatic assignment to
programs . . . . . . . . . . . . . . . . . . . 3-4
N Setting propagation rules . . . . . . . . . . 3-2
Programs
Name box . . . . . . . . . . . . . . . . . . . . . . . 2-2 Assigning BOM data to . . . . . . . . . . . . 3-3
Not Current Program ACL . . . . . . . . . . 2-12 Assigning related objects . . . . . . . . . . 3-2
Not Program Member ACL . . . . . . . . . 2-11 Automatically assigning data to . . . . . 3-4
Creating . . . . . . . . . . . . . . . . . . . . . . 2-2
O Deactivating . . . . . . . . . . . . . . . . . . . 2-2
Enabling . . . . . . . . . . . . . . . . . . . . . . 2-2
Organizing program information . . . . . . 4-1 Modifying . . . . . . . . . . . . . . . . . . . . . 2-6
Organizing project information . . . . . . . . 4-1 Propagation rules . . . . . . . . . . . . . . . . 3-2
Reload tree . . . . . . . . . . . . . . . . . . . . 2-2
P Searching . . . . . . . . . . . . . . . . . . . . . 2-1
Project
Perspectives Copying . . . . . . . . . . . . . . . . . . . . . . 2-3
In general . . . . . . . . . . . . . . . . . . . . . 1-9 Enabling . . . . . . . . . . . . . . . . . . . . . . 1-2
AM_PROJECT_MODE preference Filters . . . . . . . . . . . . . . . . . . . . . 4-34-4
AM_PROJECT_MODE . . . . . . . . . . . 2-13 Modifying . . . . . . . . . . . . . . . . . . . . . 2-6
Project and program . . . . . . . . . . . . . . 3-8 Prerequisites . . . . . . . . . . . . . . . . . . . 1-2
Prerequisites for Program . . . . . . . . . . . 1-2 Privileged team member . . . . . . . . . . 1-11
Prerequisites for Project . . . . . . . . . . . . 1-2 Project administrator . . . . . . . . . . . . 1-10
Privileged team member . . . . . . . . . . . 1-11 Project team administrator . . . . . . . . 1-11
Program Project team member . . . . . . . . . . . . 1-11
Copying . . . . . . . . . . . . . . . . . . . . . . 2-3 Smart folders . . . . . . . . . . . . . . . . 4-34-4
Enabling . . . . . . . . . . . . . . . . . . . . . . 1-2 Project administrator . . . . . . . . . . . . . 1-10
Prerequisites . . . . . . . . . . . . . . . . . . . 1-2 Project and program preferences . . . . . . 3-8
Program team administrator . . . . . . . 1-11 Project description . . . . . . . . . . . . . . . . 2-2
Program team member . . . . . . . . . . . 1-11 Project ID . . . . . . . . . . . . . . . . . . . . . . . 2-2
Program description . . . . . . . . . . . . . . . 2-2 Project menus . . . . . . . . . . . . . . . . . . . . 1-3
Program ID . . . . . . . . . . . . . . . . . . . . . 2-2 Edit . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
Program menus . . . . . . . . . . . . . . . . . . 1-3 File . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
Edit . . . . . . . . . . . . . . . . . . . . . . . . . 1-3 View . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
File . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3 Window . . . . . . . . . . . . . . . . . . . . . . . 1-4
View . . . . . . . . . . . . . . . . . . . . . . . . . 1-4 Project name . . . . . . . . . . . . . . . . . . . . 2-2
Window . . . . . . . . . . . . . . . . . . . . . . . 1-4 Project Objects ACL . . . . . . . . . . . . . . 2-10
Program name . . . . . . . . . . . . . . . . . . . 2-2 Project propagation rules . . . . . . . . . . . . 3-2
Program propagation rules . . . . . . . . . . 3-2 Project team administrator . . . . . . . . . 1-11
Program team administrator . . . . . . . . 1-11 Project team member . . . . . . . . . . . . . 1-11
Program team member . . . . . . . . . . . . 1-11 Project-level security
Program-level security Access rules . . . . . . . . . . . . . . . . . . . . 2-9
Access rules . . . . . . . . . . . . . . . . . . . . 2-9 Default access rules . . . . . . . . . . . . . 2-10
Default access rules . . . . . . . . . . . . . 2-10 Multi-Site Collaboration import and
In Current Program rule . . . . . . . . . 2-12 export . . . . . . . . . . . . . . . . . . . . . 2-8
In Inactive Program rule . . . . . . . . . 2-12 Project Objects ACL . . . . . . . . . . . . . 2-10
In Invisible Program rule . . . . . . . . . 2-12 Projects ACL . . . . . . . . . . . . . . . . . . 2-11
Index-2 Project and Program Guide PLM00049 H

Index
Project-level security tasks Reload program tree . . . . . . . . . . . . . . . 2-2

Applying Access Manager rules . . . . . . 2-9 Reload project tree . . . . . . . . . . . . . . . . 2-2
Configuring assignment of related Rich client perspectives and views . . . . . 1-9
objects . . . . . . . . . . . . . . . . . . . . . 3-1
Configuring automatic assignment to S
projects . . . . . . . . . . . . . . . . . . . . 3-4
Defining default naming rules . . . . . . . 3-1 Searching for programs . . . . . . . . . . . . . 2-1
Setting propagation rules . . . . . . . . . . 3-2 Searching for projects . . . . . . . . . . . . . . 2-1
Projects . . . . . . . . . . . . . . . . . . . . . . . 2-13 Security Rules pane . . . . . . . . . . . . . . . 1-7
Assigning BOM data to . . . . . . . . . . . . 3-3 Setting current project . . . . . . . . . . . . . . 3-7
Assigning data to . . . . . . . . . . . . . . . 1-12 Smart folder filtering . . . . . . . . . . . . . . . 4-1
Assigning related objects . . . . . . . . . . 3-2 Starting Program . . . . . . . . . . . . . . . . . 1-2
Automatically assigning data to . . . . . 3-4 Starting Project . . . . . . . . . . . . . . . . . . 1-2
Create . . . . . . . . . . . . . . . . . . . . . . . . 2-1
creating . . . . . . . . . . . . . . . . . . . . . . 2-2 T
Deactivating . . . . . . . . . . . . . . . . . . . 2-2
Multi-Site Collaboration TC_project_propagate_from_dataset
environment . . . . . . . . . . . . . . . . . 2-8 preference . . . . . . . . . . . . . . . . . . . . . . 3-4
Propagation rules . . . . . . . . . . . . . . . . 3-2 TC_set_current_project preference . . . . . 3-7
Reload tree . . . . . . . . . . . . . . . . . . . . 2-2 Team members . . . . . . . . . . . . . . . . . . 1-11
Searching . . . . . . . . . . . . . . . . . . . . . 2-1 Privileged team member . . . . . . . . . . 1-11
Projects ACL . . . . . . . . . . . . . . . . . . . 2-11 Program team administrator . . . . . . . 1-11
Propagation Project administrator . . . . . . . . . . . . 1-10
Level one . . . . . . . . . . . . . . . . . . . . . . 3-3 Project team administrator . . . . . . . . 1-11
Level two . . . . . . . . . . . . . . . . . . . . . 3-4 Team member . . . . . . . . . . . . . . . . . 1-11
Propagation rules . . . . . . . . . . . . . . . . . 3-2
U
R update_project_bom utility . . . . . . . . . . . 3-3
Reload Utilities
Program tree . . . . . . . . . . . . . . . . . . . 2-2 update_project_bom . . . . . . . . . . . . . . 3-3
Project tree . . . . . . . . . . . . . . . . . . . . 2-2
PLM00049 H Project and Program Guide Index-3

Teamcenter 9.1: Publication Number PLM00049 H

Diunggah oleh

Informasi Dokumen

Judul Asli

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

Teamcenter 9.1: Publication Number PLM00049 H

Diunggah oleh

Hak Cipta:

Format Tersedia

Teamcenter 9.

Project and Program Guide

This software and related documentation are proprietary to Siemens Product

2 Project and Program Guide PLM00049 H

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

Getting started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

Creating and administering projects . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

Configuring projects and programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

Configuring smart folder filtering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

PLM00049 H Project and Program Guide 3

4 Project and Program Guide PLM00049 H

Getting started with Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

Before you begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

Project and Program interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2

Basic concepts about Project and Program . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9

Basic tasks using Project and Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-13

PLM00049 H Project and Program Guide

Getting started with Project

Assign users as members of projects and programs.

Implement access control based on project or program membership.

Associate data dictionaries (libraries) with projects and programs.

Before you begin

Project and program team administrators can modify

PLM00049 H Project and Program Guide 1-1

members from the project or program. However, they cannot

If you have trouble accessing Project or Program, see your

Project and Program interface

1-2 Project and Program Guide PLM00049 H

Project and Program menus

Menu command Purpose

Menu command Purpose

PLM00049 H Project and Program Guide 1-3

Menu command Purpose

View or change your default group, role, or

View or change logging privileges for a user

Menu command Purpose

Menu command Purpose

1-4 Project and Program Guide PLM00049 H

Menu command Purpose

Project and Program quick links

PLM00049 H Project and Program Guide 1-5

Project Administration window

1 Quick Links Displays links to navigate between the

Project administration buttons

1-6 Project and Program Guide PLM00049 H

Project administration tabs

PLM00049 H Project and Program Guide 1-7

Smart Folder Administration window

1 Quick Links Displays links to navigate between the

Smart folder administration buttons

1-8 Project and Program Guide PLM00049 H

Rich client perspectives and views

Basic concepts about Project and Program

Data can be assigned to or removed from projects and programs manually or

Propagation rules define the associated data that is implicitly assigned to a

All items in a complete product structure can be assigned to a project or program

Ownership of data can be assigned to a project or program by configuring the

Creation and maintenance of data can be restricted to within the context of a

PLM00049 H Project and Program Guide 1-9

Share data between programs by assigning the data to multiple programs.

For more information, see the Security Administration Guide.

Project administrators and team members

Team role Definition