Project

Teamcenter 10.1

Project and Program Guide

Publication NumberPLM00049 J

Proprietary and restricted rights notice

This software and related documentation are proprietary to Siemens ProductLifecycle Management Software Inc.

© 2013 Siemens Product Lifecycle Management Software Inc. All Rights Reserved.

Siemens and the Siemens logo are registered trademarks of Siemens AG. Teamcenteris a trademark or registered trademark of Siemens Product Lifecycle ManagementSoftware Inc. or its subsidiaries in the United States and in other countries. Allother trademarks, registered trademarks, or service marks belong to their respectiveholders.

2 Project and Program Guide PLM00049 J

Contents

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

Introduction to Project and Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Before you begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Characteristics of projects and programs . . . . . . . . . . . . . . . . . . . . . . . . . 9

Project administrators and team members . . . . . . . . . . . . . . . . . . . . . . 11

Ownership of data by a project or program . . . . . . . . . . . . . . . . . . . . . . 13

Assigning data to projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Project Administration window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Project and Program quick links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Project administration buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Project administration tabs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Smart Folder Administration window . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Smart folder administration buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

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

What are projects and programs? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1Using projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1Search for a project or program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1Search for users, groups, or roles in your projects and programs . . . . . . . . . . . 1-2Filter user display in the project member tree . . . . . . . . . . . . . . . . . . . . . . . . 1-3Creating and modifying projects and programs . . . . . . . . . . . . . . . . . . . . . . . 1-4Associating data dictionaries with projects . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6Assigning users to projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7Applying security rules to projects and programs . . . . . . . . . . . . . . . . . . . . . . 1-10Set a user’s default project or program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-16Considerations for importing and exporting project or program data in a Multi-SiteCollaboration environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-16

Configuring projects and programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

Project and program configuration tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1Default naming rules for projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1Assigning secondary objects to projects and programs . . . . . . . . . . . . . . . . . . 2-2Automatically assigning objects to projects and programs . . . . . . . . . . . . . . . . 2-4Restricting data creation to within the context of a project or program . . . . . . . 2-6Controlling assignment of replicated (imported) data to projects . . . . . . . . . . . 2-7Setting the current project for new Teamcenter sessions . . . . . . . . . . . . . . . . . 2-7

PLM00049 J Project and Program Guide 3

Contents

Selecting different object property values based on project assignment . . . . . . 2-7Displaying projects to users based on current group and role . . . . . . . . . . . . . 2-8Using pseudo folders to organize the display of objects in projects . . . . . . . . . . 2-8Project and program preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8

Configuring smart folder filtering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

What are project smart folders? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1Understanding the project smart folder hierarchy . . . . . . . . . . . . . . . . . . . . . 3-2Top-level smart folder hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2Top-level hierarchy example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2Creating the example project top-level hierarchy . . . . . . . . . . . . . . . . . . . . . . 3-3Associating data objects with smart folders . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3Using properties to filter data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4Project smart folder hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5Project smart folder hierarchy example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5Apply smart folder filtering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5Viewing project data in My Teamcenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7

Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Index-1


Introduction to Project and Program

The Project and Program applications provide a mechanism for organizing data andimplementing 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 viewin My Teamcenter.

• Associate data dictionaries (libraries) with projects and programs.

Project and Program work with Access Manager to control access to data by projector program members.

For information about configuring access to project and program data, see theSecurity Administration Guide.


Before you begin

Prerequisites Access to Project and Program is controlled by your Teamcenteradministrator.

Only users in the following roles and groups, or users in theDBA role within the dba group, can perform tasks in Projectand Program:

• Project Administrator in the Project Administration groupcan create, modify, and delete projects and programs. Theycan also add and remove team members from projects andprograms and apply access rules.

Note Users in the Project Administrator role can onlymanage projects and programs that they own. Theycannot manage projects or programs owned by otherusers in the Project Administrator role. Ownershipis established when the project is created.

• Team Administrator in the Project Administration groupcan modify project and program information and addand remove team members from the project or program.However, they cannot create or delete a project.

Enable Projectand Program

Project does not need to be enabled before you use it, but duringinstallation, this feature must be selected.

The system can be configured to display the Project applicationas Program. To do this, set the display name of the TC_Projectbusiness object in the Business Modeler IDE to Program.

For more information, see Business Modeler IDE Guide.

Note The Project application is automatically displayedas Program when you install the ADS Foundationtemplate.

If you have trouble accessing Project or Program, see yoursystem administrator; it may be a licensing issue.

Note You can log on to Teamcenter only once. If you try to logon to more than one workstation at a time, you see anerror message.


Before you begin

ConfigureProject andProgram

You can set various options to:

• Configure the level of propagation applied when objects areassigned to projects or programs.

• Specify whether project or program security rules areapplied to all projects and programs or only to the user’scurrent project or program

• Specify whether BOM views and BOM view revisions areassigned to the project or program when the items or itemrevisions are assigned to the project or program.

Default rules for project-level or program-level security areautomatically defined when a project or program is created.Additional security rules can be configured in Project orProgram by a project administrator or in Access Manager bya Teamcenter administrator.

Start Project orProgram Click Project in the navigation pane.


Characteristics of projects andprograms

Projects and programs organize data and are the basis for granting data access toproject and program team members. The following concepts apply to projects andprograms:

• Only privileged team members or regular team members who are explicitlygranted ASSIGN_TO_PROJECT or REMOVE_FROM_PROJECT privilegescan assign data to and remove data from projects and programs.

The TC_project_validate_conditions preference controls which team rolesand access privileges are required to add and delete projects.

• Project and program names must be unique within your site. Projects andprograms cannot have the same name as any group at the site.

• Data can be assigned to or removed from projects and programs manually orautomatically when the data item is created, and items can be assigned to morethan one project or program.

• Propagation rules define the associated data that is implicitly assigned to aproject 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 programusing the update_project_bom utility.

• Ownership of data can be assigned to a project or program by configuring theautoAssignToProject extension in the Business Modeler IDE.

For more information, see Automatically assigning objects to projects andprograms.

• Creation and maintenance of data can be restricted to within the context of aprogram.

Note When the program security attribute on a project is set to true, the projectis 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 appliedto project data.

• Share data between programs by assigning the data to multipleprograms.

For more information, see the Security Administration Guide.


Project administrators and teammembers

The following table describes the project administrators and team members who cancreate, manage, and use projects and programs.

Team role Definition

Project Administratorrole in ProjectAdministration group

Teamcenter user with privileges to create andadminister projects and programs.

Users in the Project Administrator role 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 andprograms that the project administrator owns.

Team Administrator rolein Project Administrationgroup

Project or program team members with privileges tomodify project or program information. These privilegesapply to the project or program metadata, not to thedata assigned to projects and programs.

Users in the Team Administrator role can:

• Add team members to projects or programs in whichthe team administrator is also a member.

• Remove team members from projects or programsin which the team administrator is also a member.

Note You can designate multiple team administratorsfor each project or program. This is oftennecessary to balance resource managementtasks for large projects.

Privileged teammembers Project or program team members with privilegesto assign or remove objects from their projects orprograms.


Project administrators and team members

Team role Definition

Team members Team members (users) who do not have privileges toassign objects to or remove objects from their projectsor programs.

The following diagram illustrates a typical project or program hierarchy.

Project or Program Selected Members

Team Administrator Privileged TeamMembers Team Members

Gordon, Jack Jones, Paul Franklin, WendyBelcher, Sarah Tracey, Don

Smith, William


Ownership of data by a project orprogram

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

• Ownership is assigned to the user’s current project or program. Users canchange the current project in their user session by choosing Edit→User Settingand selecting a project or program from the list.

• Users can be prevented from creating an object without an owning project orprogram. This can be accomplished in two ways:

o Set the value of the CreateDataWithNoActiveProgram global constantto false.

o Configure the autoAssignToProject extension in the Business ModelerIDE to automatically assign objects to projects upon creation.

• Owning project or owning program can be used as a basis for controlling accessto data.

• Once established, the relationship between an object and its owning project canonly be broken if the TC_allow_remove_owning_project preference is set toallow users to remove objects from owning projects.


Assigning data to projects

End users can manually assign data objects to projectsprojects and programs. Inaddition, you can configure Teamcenter to automatically assign related objects to aprojectproject or program when the primary object is assigned to the project, and youcan use the update_project_bom utility to assign or remove objects in a product ormanufacturing structure to or from a project. Teamcenter can also be configuredto automatically assign data objects to projectsprojects and programs when theobject is created.

Data objects can be assigned to projectsprojects and programs in the following ways:

• Manually assigned to projectsprojects or programs by users who are designatedas privileged team members. Privileged team members include:

o ProjectProject or program team administrator

o Privileged team members

Note Additional projectproject or program security can be achieved usingthe ASSIGN_TO_PROJECT and REMOVE_FROM_PROJECTprivileges. The exact behavior of these privileges is controlled by theTC_project_validate_conditions preference.

• Automatically assigned to projectsprojects or programs when the object iscreated. When a new item revision is created, it is automatically assigned to theprojectproject or program in which the user is currently working.

Teamcenter administrators define which objects can be automatically assignedto projectsprojects and programs using the Business Modeler IDE to configurethe autoAssignToProject extension located in the Extension Definitions folderunder Rules.

• Automatically assigned to projectsprojects or programs when the primaryobject is assigned to the projectproject or program. ProjectProject and programpropagation rules determine which secondary objects are assigned to aprojectproject or program when a primary object type is assigned.

• Using the update_project_bom utility to assign or remove objects in a productor manufacturing structure to or from a project or program.

Data can be assigned to projects when working in the following applications:

• My Teamcenter

• Change Manager

• Multi-Structure Manager

• Structure Manager


Assigning data to projects

• Part Planner

• Plant Designer

• Manufacturing Process Planner

• Content Management


Project Administration window

1 Quick Links Displays links to navigate between theProject Administration and Smart FolderAdministration windows.

For more information, see Project and Programquick links.

2 Project or Program tree Displays the list of projects or programs inTeamcenter. New projects and programsappear in this list.

3 Project or programdefinition and rules

Displays information about the selected projector program.

If the Definition tab is selected. the propertiesof the project or program are displayed. If theAM Rules tab is selected, the security rules forthe project or program are displayed. If theLibraries tab is selected, you can view whichdata dictionaries are assigned to the project orassign new dictionaries to the project.

For more information, see What are projectsand programs? and Applying project andprogram security (Access Manager) rules.



Project and Program quick linksThere are two links in the Quick Links area of the navigation pane that are specificto Project and Program:

Project Administration Provides access to the project administration interfaceused to create and activate projects and programs, assignusers membership in projects and programs, and designateproject and program administrators and privileged teammembers.

Smart FolderAdministration

Provides access to the smart folder filter configurationinterface used to define filtering criteria based on thesmart folder hierarchy. These filters control how projectand program data is displayed to users.

These links appear in both the Project Administration window and the Smart FolderAdministration window.

Project administration buttons

Button Description

Groups Filters the display of the organization tree or projectmember tree by groups. You can search for a specificgroup in either tree by entering the group name in thetext box and clicking the Groups button.

Roles Filters the display of the organization tree or projectmember tree by roles. You can search for a specific rolein either tree by entering the role name in the text box

and clicking the Roles button.Users Filters the display of the organization tree or project

member tree by users. You can search for a specificuser in either tree by entering the user name in the

text box and clicking the Users button.Clear Clears the search criteria and restores the organization

tree or project member tree to its previous state.

Refresh tree Refreshes the organization tree or project member treeand restores it to its original state.

Project administration tabs

Tab Description

Definition Displays the Definition pane. Use this pane to create theproject, to assign project team members, and to designateprivileged team members.



Tab DescriptionAM Rules Displays the Access Manager Rules pane. Use this pane

to apply access rules to a project.

Note Project administrators only have access to the InProject branch of the rule tree. You cannot modifyother branches of the rule tree from within Project.In addition, moving the In Project branch to adifferent position in the tree requires Teamcenteradministrative privileges and must be done usingthe Access Manager application.

Libraries Displays data dictionaries (libraries) that have beendefined in the Classification Administration application,and provides tools for associating these libraries withspecific projects or programs.


Smart Folder Administration window

1 Quick Links Displays links to navigate between theProject Administration and Smart FolderAdministration windows.

2 Smart folder tree Displays the smart folder hierarchy. The smartfolder hierarchy consists of top-level abstractfolders and low-level data-driven folders.

3 Filter tables Displays the set of filters that apply to theselected smart folder hierarchy node.

Smart folder administration buttonsButton Description

Add filter Adds a new row to the filter table that is used to defineadditional filters for data-driven folders. Additionalfiltering criteria can only be applied to data-drivenfolders. Abstract folders in the hierarchy can onlyapply a single filter criteria.

Remove filter Removes the selected row from either of the filtertables.


Chapter

1 Creating and administeringprojects

What are projects and programs? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

Using projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

Search for a project or program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

Search for users, groups, or roles in your projects and programs . . . . . . . . . . . 1-2

Filter user display in the project member tree . . . . . . . . . . . . . . . . . . . . . . . . 1-3

Creating and modifying projects and programs . . . . . . . . . . . . . . . . . . . . . . . 1-4Create a project or program based on an existing project or program . . . . . 1-4Create a new project or program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4Modify projects and programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5Set project status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5Delete a project or program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6

Associating data dictionaries with projects . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6What are data dictionaries? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6Add a data dictionary to a project or program . . . . . . . . . . . . . . . . . . . . . 1-7

Assigning users to projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7Assign individual users to a project or program . . . . . . . . . . . . . . . . . . . . 1-7Assign groups of users to a project or program . . . . . . . . . . . . . . . . . . . . . 1-7Assign all users in a role to a project . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8Select team administrators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9Designate privileged team members . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10

Applying security rules to projects and programs . . . . . . . . . . . . . . . . . . . . . . 1-10Applying project and program security (Access Manager) rules . . . . . . . . . 1-10Default security rules for projects and programs . . . . . . . . . . . . . . . . . . . 1-11

Access rules for projects and programs . . . . . . . . . . . . . . . . . . . . . . . 1-11Is Project Member rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12In Project rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12Is Program Member rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-13In Current Program rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-13In Inactive Program rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-13In Invisible Program rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-14Is Owned by Program rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-14

Configure evaluation of rules that include the Role in Project and Role in Projectsof Object accessors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-15

PLM00049 J Project and Program Guide

Configure evaluation of the ASSIGN_TO_PROJECT andREMOVE_FROM_PROJECT privileges . . . . . . . . . . . . . . . . . . . . . . . . 1-15

Set a user’s default project or program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-16

Considerations for importing and exporting project or program data in a Multi-SiteCollaboration environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-16

Project and Program Guide PLM00049 J

Chapter

1 Creating and administeringprojects

What are projects and programs?Projects and programs are groupings of objects that are accessible to users who aredesignated as members of the project or program team. Projects and programs allowyou to control user access to Teamcenter data. Data access rules can be implementedbased on projects and programs, roles in projects and programs, and ownership ofdata by a project or program. In addition, libraries of components (also referred to asdata dictionaries) can be associated with projects and programs to allow designersto easily reuse components that have gone through a formal, customer-specificapproval process.

Using projectsProject creation and administration tasks are preformed in the following order:

1. A project administrator is added to the Project Administrator role in theProject Administration group by the Teamcenter administrator.

2. A project is created with specific groups, users or roles assigned as teammembers, privileged team members, and team administrators.

3. The user’s default project is set.

Note To assign a default project, you must select the Use Program Securityoption when you define the project or program.

4. As database objects are created, they are assigned to the project automatically ormanually by privileged team members.

Search for a project or program1. 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 Search .

Projects and programs matching the keyword are displayed in the tree.

PLM00049 J Project and Program Guide 1-1

Chapter 1 Creating and administering projects

Note If no projects or programs are found that match your search criteria, theProject tree pane is empty.

To restore the tree display, click Reload .

Search for users, groups, or roles in your projects and programsWhen you administer projects or programs, you will search the organization forindividual users, users in certain roles, or users in certain groups to add to yourprojects or programs. You will also search your project membership for users, groups,and roles as part of ongoing project or program maintenance.

Organization search

Use the search box above the tree on the left side of the Member Selection pane tosearch the organization for users, groups, or roles to add as project members.

1. Enter the name of a user, group, or role in the text box.

2.

To... Click...Search for a user in the organization The User button .Search for a role in the organization The Roles button .Search for a group in the organization The Groups button .

When you search for a role, the organization tree displays the role within context ofthe groups it’s associated with.

Note If your search yields no results, the tree pane will be empty. Click theRefresh button or Clear button to restore the display.

Member search

Use the search box above the tree on the right side of the Member Selection tosearch the organization for users, groups, or roles to add as project members.

1-2 Project and Program Guide PLM00049 J

Creating and administering projects

1. Enter the name of a user, group, or role in the text box.

2.

To... Click...Search for a user in the project orprogram The User button .Search for a role in the project orprogram The Roles button .Search for a group in the project orprogram The Groups button .

When you search for a user, the member tree displays the groups and roles to whichthe user belongs. In the graphic above, Jena Rafferty is a project member bothin her role as a Designer in the Engineering group and as a Designer inthe LMD group.

Note If your search yields no results, the tree pane will be empty. Click theRefresh button or Clear button to restore the display.

Filter user display in the project member treeTo filter the project member display, choose Non-privileged, Privileged, or TeamAdministrator from the list above the project member tree.

Click the Refresh button or Clear button to restore the display.



Creating and modifying projects and programs

Create a project or program based on an existing project or programYou can define a new project or program by copying an existing project or programthat has similar characteristics to the project or program you want to define.This allows you to leverage existing membership assignments, access rules, andassociated data dictionaries (libraries).

1. In the Definition pane, select an existing project or program from the Projecttree or the Program tree.

Tip To find a project or program in the tree, type a keyword (project orprogram ID or name) and click Find .

2. Type a new project or program ID in the ID box. (The maximum length for aproject or program ID is 64 characters.)

3. Type a new project or program name in the Name box. (The maximum length fora project or program name is 32 characters.)

Caution You cannot use characters such as , % * @, in project and programnames.

4. Modify any of the project or program settings, such as team member assignmentsand access rules.

5. Click Copy.The new project or program is created and displayed in the tree.

Create a new project or program1. Click the Definition tab.

Tip If the Definition tab is not displayed, click the Project Administrationquick 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 theID 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 becontrolled 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 beunique within your site, and it cannot be the same as the name of any group atyour site. (The maximum length for a project or program name is 32 characters.)

Caution You cannot use characters such as , % * @, in project and programnames.

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 managedata within the project or program.

Inactive Inactivates the project or program. Users can see the project orprogram, but they cannot manage data within the project orprogram.

Inactive andInvisible

Inactivates the project or program and removes it from theuser’s display. Only project administrators can view the dataowned 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 toa project or program.

Modify 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 programname or ID after data has been assigned to an active project or program.

Set project statusNote You must be a team member in the Project Administrator role in the

Project Administration group to set the status of a project or program.

1. Expand the Project or Program tree and select the project or program.

2. Click the Definition tab.

Tip If the Definition tab is not displayed, click the Project Administrationquick link.

3. Select one of the following status options.



Option DescriptionActive 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 orprogram team members, but the data cannotbe modified.

Inactive and Invisible Project or program data is invisible and cannotbe modified. Only project administratorscan view the data owned by an inactive andinvisible project or program.

4. Click Modify for an existing project or program, or click Create for a new projector program.

Delete a project or program

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

2. Click the Definition tab.Tip If the Definition tab is not displayed, click the Project Administration

quick link.

3. Click Delete.The Confirm Delete dialog box appears.Note You can delete a project or program that has data assigned to it;

however, you cannot delete a project or program that owns data. Formore information about data ownership, see Ownership of data by aproject or program.

4. Click Yes.

Associating data dictionaries with projects

What are data dictionaries?

Data dictionaries are central repositories for key building blocks or components ofdesigns used in typical functional and logical design activities. These repositoriesmake it easy to reuse components in multiple designs across projects or programs.Data dictionaries are modeled as libraries in the Classification application and canbe associated with projects or programs, which allows designers who are projectmembers to add data from the dictionary to function, logical, or physical modelstructures.

Tip Multiple data dictionaries (libraries) can be associated with a single projector program. In addition, a single data dictionary can be associated withmultiple projects or programs.



Add a data dictionary to a project or programData dictionaries are modeled as libraries using Classification classes. In thisprocedure, 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 wantto associate with the selected project.

4. Select the library in the hierarchy, add it to the pane on the right side of thewindow, and click the Save button located between the panes.

The library (data dictionary) is now associated with the project. Designers who areproject members can add data from the dictionary to model structures while workingin Systems Engineering or Structure Manager.

Assigning users to projects

Assign individual users to a project or program1. In the Member selection area 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.

If your search yields no results, the tree pane will be empty. Click theRefresh button or Clear button to restore the display.

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 team administrator.

For more information, see Select team administrators.

Note Only project administrators can designate a project or program teamadministrator.

• Designate privileged team members.

For more information, see Designate privileged team members.

4. Click the Create button if you’ve added users to a new project, or click the Modifybutton if you’ve added users to an existing project.

Assign groups of users to a project or programYou can assign groups of users to a project or program.



Hierarchical group behavior applies to the assignment of users to projects andprograms. If you select a group that has subgroups, all users in the parent group andsubgroups are assigned membership in the project or program.

1. In the Member Selection area of the Definition pane, locate the group in theOrganization 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 groupsbutton.


2. Select the group or subgroup and click the Add button.

The group appears in the table of selected members at the right of the MemberSelection pane.








Assign all users in a role to a projectYou can assign all users in a specific role to a project or program.

1. In the Member Selection area of the Definition pane, locate the role in theOrganization tree.Tip You can search for the role by typing the role name (or partial name and

wildcard characters) in the box and clicking the Find roles button.

Teamcenter displays all roles matching the search criteria. The roles aredisplayed in context of the groups to which they belong.


2. Select the role and click the Add button.

The role appears in the table of selected members at the right of the MemberSelection pane.All users in the role are added as members of the project or program.










Select team administrators

Team administrators manage resources for projects and programs by assigningor removing users as resource needs change. Depending on the size of yourprojects/programs and the needs of your organization, you may choose to designate asingle team administrator or to designate multiple team administrators.

Designating multiple team administrators allows you to spread the burden ofadministrative tasks, which can be considerable for large projects. For small projectsyou may also want to designate multiple team administrators to ensure coverage inthe event that your primary team administrator is unavailable.

1. Select a project from the tree in the Project view.

2. Go to the Definition view and locate the team members (in the project membertree in the lower-right of the view) who will be team administrators.

Tip You can search for users, groups, or roles within the project member tree.


3. Select the team members, right click, and choose Select a project teamadministrator.

Note You can select individual users from different groups and roles or youcan select all users in a group or all users in a specific role.

The project member tree is updated, the icon is displayed next to the user’s name,and Team Administrator is displayed in the Status column of the tree table.



Designate privileged team members

Designating team members as privileged is one step in the process of granting accessto users to allow them to assign data to and remove data from projects and programs.

For information about the other steps in the process of granting access, see Applyingproject and program security (Access Manager) rules.

1. Select a project from the tree in the Project view.

2. Go to the Definition view and locate the team members (in the project membertree in the lower-right of the view) who will be designated as privileged users.

Tip You can search for users, groups, or roles within the project member tree.


3. Select the team members, right click, and choose Set Privileged Users.

Note You can select individual users from different groups and roles or youcan select all users in a group or all users in a specific role.

The project member tree is updated, the check mark icon is displayed next to theuser’s name, and Privileged is displayed in the Status column of the tree table.

Applying security rules to projects and programs

Applying project and program security (Access Manager) rules

Project administrators can extend the default security rules, which grant readaccess to project or program data to members of the project or program team, on aproject-by-project or program-by-program basis.

Note Project administrators only have access to the In Project() –> Projectsbranch 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 OwningGroup condition.



• Grant or deny access to groups of users based on the group’s categorization asinternal (OEM) or external (supplier) by applying the Owning Group HasSecurity 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 applyingthe Is Project Member condition.

• Grant or deny access to users based on their membership in a program byapplying the Is Program Member condition.

• Deny users access to data if the owning program is not the active program in theuser’s session by applying the In Current Program condition.

• Deny users access to data if the owning program is inactive by applying the InInactive Program condition.

• Deny users access to data if the owning program is invisible by applying the InInvisible Program condition.

• Grant or deny access to program data by applying the Is Owned By Programcondition.

For more information about configuring project-level security rules, see the SecurityAdministration Guide.

Default security rules for projects and programs

Access rules for projects and programs

The Access Manager rule tree delivered as part of the standard Teamcenterinstallation 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 theuser’s membership in the project is evaluated. This condition is true only when theuser is a current member of the project.

Note The Is Project Member(true) –> Project Objects rule can only bemodified by an administrator using the Access Manager application. Itcannot be modified from the Project application.

The Project Objects ACL grants project administrators and project teamadministrators privileges to modify projects in which they are members. Theseprivileges apply to the project metadata, not to the data assigned to projects.

The ACL is defined as follows.

Accessor Type Accessor ID Read Write Delete Change ChangeOwnership

Owning User

Role ProjectAdministrator

Role Project TeamAdministrator

World

Note You can modify the Project Objects ACL to meet the project accessrequirements at your site.

For more information about applying project-level security rules, see the SecurityAdministration Guide.

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.

ReadProject Teams

The Project Teams accessor gives all team members read privileges to the data ina project. For example, if the Design, Validation, and Documentation groupsare selected as a project team, the Project Teams accessor grants privileges to allmembers of each group; therefore it is not necessary to use the Group accessor togrant privileges to each group individually.

The project administrator can create or modify project security rules to meet therequirements 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 administratorscan modify rules using Project.

Note Only an administrator with privileges to use Access Manager can change theplacement of the In Project rule in the AM rule tree. They can also modifythe 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 SecurityAdministration Guide.

Is Program Member rule

The Is Program Member(false) –> Not Program Member rule denies readaccess 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.

ReadWorld

TheWorld accessor denies read access to users if the user is not the member of theowning program or the shared programs.

For more information about applying program-level security rules, see the SecurityAdministration Guide.

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 isnot the active program for the user’s session.

The Not Current Program ACL denies the privileges to the data in a program,as follows.

ReadWorld

TheWorld accessor denies write, delete, change and export privileges to users if theowning program of the data is not the active program for the user’s 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 datais in the inactive state.



The Inactive Program ACL denies write, delete, change and export privilegesto the data in the program, as follows.

ReadWorld

The World accessor denies write, delete, change and export privileges to users ifthe owning program of the data is in the inactive state.


In Invisible Program rule

The Is Invisible Program (true) –> Invisible Program rule denies read accessto 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, asfollows.

ReadWorld

The World accessor denies read access to program data if the program is in theinvisible state.


Is Owned by Program rule

The Is Owned By Program()–>Projects rule grants or denies access to databased on program or project ownership.

The Projects ACL grants read access to the data in the program, as follows.

ReadProject Teams

The Is Owned By Program rule can be configured to enable the exchange ofAerospace and Defense program data between databases. Exchanging program datarequires that the user initiating the import or export is a member of the program towhich the objects being exchanged are assigned.

For information about configuring the Is Owned By Program rule to support theexchange of Aerospace and Defense data, see the Aerospace and Defense SolutionGuide.



Configure evaluation of rules that include the Role in Project and Rolein Projects of Object accessors

You can set the AM_PROJECT_MODE preference to configure how the systemconsiders the user’s roles in active projects when evaluating access rules that use theRole in Project or Role in Projects of Object accessors.

The system either:

• Evaluates the user’s roles in the context of all active projects.

• Evaluates the user’s roles in the context of the current project. The user’s currentproject is the project specified for the active Teamcenter session.

Note To view a user’s current project, choose Edit→User Setting.

For more information about project preferences, see the Preferences and EnvironmentVariables Reference.

For more information about the Role in Project and Role in Projects of Objectaccessors, see the Security Administration Guide.

Configure evaluation of the ASSIGN_TO_PROJECT andREMOVE_FROM_PROJECT privileges

You can set the TC_project_validate_conditions preference to specify how theASSIGN_TO_PROJECT and REMOVE_FROM_PROJECT access privileges arevalidated in conjunction with privileged project membership.

You can configure the following project access scenarios:

• Users who are privileged project members can assign objects to or removeobjects from projects.

• Users who are either privileged project team members or who have specificASSIGN_TO_PROJECT and REMOVE_FROM_PROJECT privileges canassign 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_PROJECTprivileges to assign objects to and remove objects from projects.

• Users who are privileged team members and also have ASSIGN_TO_PROJECTand REMOVE_FROM_PROJECT privileges can assign objects to or removeobjects from projects.

For more information about project preferences, see the Preferences and EnvironmentVariables Reference.

For more information about configuring access privileges, see the SecurityAdministration Guide.



Note • This preference is not included in your Teamcenter installation. Youmust add it to the database.

For information about adding preferences, see the Rich Client InterfaceGuide.

• The TC_project_validate_conditions preference does not apply tothe assignment of replicated objects during an import operation. TheTC_multi_site_project_member_bypass controls the privilegesrequired to assign replicated objects to projects upon import.

• The TC_project_validate_conditions preference has no effect onwhich projects are displayed in the Teamcenter interface. Therefore, itis possible that users will see projects displayed in the interface, forexample in the User Settings dialog box, that they do not have access to.

Set a user’s default project or programNote • You must select the Use Program Security option in the project definition

to be able to set default projects.

• Users must be assigned to more than one project or program beforeyou can set a default project or program. If users are only assigned toone project or program, that project or program is their default projector program.

1. In the Project or Program tree, select a default project or program for the user.

2. In the Member selection area of the Definition pane, right-click the user in theSelected Members tree, and choose Set Default Project or Set Default Program.

Considerations for importing and exporting project or program data ina Multi-Site Collaboration environment

The following points should be considered when importing and exporting project orprogram 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 programsacross sites before attempting to share project or program data.



• Users, groups, projects, and programs must be replicated at all sites that shareproject or program data. You can use the dsa_util utility to replicate users andgroups. Projects and programs must either be replicated individually, usingthe Project or Program application or using the create_project utility, whichenables you to create projects or programs individually based on command lineinput or in batch using input from a text file.

• When an object that is assigned to a project or program is exported, theexplicitly assigned ID of the project or program is exported along with the otherdata associated with the object. When that object (replica) is imported at thereceiving site, it is assigned to the project or program with the same ID. If animported object is assigned to multiple projects or programs, it is assigned to thecorresponding projects or programs at the importing site.

Note If no matching project or program ID is found at the importing site, theimport operation proceeds. Teamcenter does not issue an error message.

• When an imported object (replica) is assigned to a project or program, theassociated secondary objects are also assigned to the project or programaccording to the propagation rules in effect at the receiving site.

• When a replicated object is imported to a remote site by auser who is not a privileged team member, the value of theTC_multi_site_project_member_bypass preference determines whether theobject 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 tothe project or program upon import.

Note The TC_multi_site_project_member_bypass preference is notincluded in your Teamcenter installation. You must add it to thedatabase.

For information about adding preferences, see the Rich Client InterfaceGuide.


Chapter

2 Configuring projects andprograms

Project and program configuration tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

Default naming rules for projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

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

Automatically assigning objects to projects and programs . . . . . . . . . . . . . . . . 2-4Understanding the implications of the autoAssignToProject extension onpropagation rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5

Restricting data creation to within the context of a project or program . . . . . . . 2-6

Controlling assignment of replicated (imported) data to projects . . . . . . . . . . . 2-7

Setting the current project for new Teamcenter sessions . . . . . . . . . . . . . . . . . 2-7

Selecting different object property values based on project assignment . . . . . . 2-7

Displaying projects to users based on current group and role . . . . . . . . . . . . . 2-8

Using pseudo folders to organize the display of objects in projects . . . . . . . . . . 2-8

Project and program preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8


Chapter

2 Configuring projects andprograms

Project and program configuration tasksConfiguring projects and programs includes the following tasks:

• Configuring naming rules to control the ID and name format when projectsare created.

• Setting preferences that control different aspects of project and programbehavior.

• Configuring how the assignment of secondary objects is handled when a primaryobject 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 ModelerIDE) to automatically assign objects to projects when they are created.

• Configuring the list of values displayed for the property of an object based on theproject that the object is assigned to.

• Restricting the creation of data to within the context of a project or program bysetting the CreateDataWithNoActiveProgram global constant.

• Applying access rules to project and program data.

Default naming rules for projectsNaming rules control the format of project names and IDs, allowing you to applycustom naming conventions to your projects. While naming rules are not requiredto use projects to organize and secure your data; they ensure that projects areidentified in a consistent manner. Naming rules are created and attached to projectproperties using Business Modeler IDE.

For more information, see the Business Modeler IDE Guide.


Chapter 2 Configuring projects and programs

Assigning secondary objects to projects and programsTeamcenter administrators can configure Teamcenter to implicitly assign relatedobjects to a project or program when the primary object is assigned to a project orprogram.

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 inwhich they are contained is assigned to a project.

Secondary object propagation rules for projects and programsThe secondary object propagation rules are defined by relation type and apply to anysecondary object associated with a primary object by one of the included relationtypes. By default, the following relation types are included for propagation:

SpecificationsManifestationsAltRepsAffected ItemAttachesSolution 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 relatedobjects 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 isassigned 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, theassociated secondary objects are also assigned to the project or programaccording to the propagation rules in effect at the receiving site.

Generally, you propagate secondary items that are related to the primary item by aSpecifications, Manifestations, Attaches, or AltReps relationship. Secondaryitems related to primary items by Requirements and References relationshipsgenerally do not need to be implicitly propagated to the project or program.

Set relation propagation rules1. In the Project or Program application, choose Edit→Options.

Note Propagation rules apply to the entire site, and they can only be definedby a user with dba privileges.

2. Select the Project or Program node in the Options tree.


Configuring projects and programs

3. In the Relation Propagation Rules section of the Options dialog box, add therelation types to the Include Relations list. These are the relation types bywhich 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 Revisionto propagate BOM views and BOM view revisions when an item or item revisionis assigned to a project or program.

Note BOM views and BOM view revisions are attached to items and itemrevisions by attribute reference rather than by relation type.

5. Click OK or Apply.

Assigning BOM data to projects and programsObjects contained in a product or manufacturing structure can be assignedto or removed from projects or programs in batch mode by running theupdate_project_bom utility.

Note Only objects that were added to the project or program using the utility canbe removed using the utility.

The utility can be used to assign or remove objects at either the level-one or level-twopropagation level.

Level-one propagation processes BOM objects and their attached datasets. Thefollowing 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 whichthe utility processes the structure is determined by the –depth argument. Inaddition, 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 bywhich the BOM should be configured, and the unit number, effectivity date, and IDof the end item associated with the revision rule. Variant rules can also be applied tothe structure before propagation.

Note Objects assigned to a project or program as part of level-one propagationare implicitly assigned to the project or program. Therefore, any change tothe relationship between the primary and secondary objects is reflected inthe project or program.

Level-two propagation processes dependent objects related to the datasets associatedwith level-one objects. The following data model is supported for level-twopropagation:

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 explicitlyassigned to the project or program. Objects that are explicitly assigned toa project or program must also be explicitly removed. If the BOM object towhich 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 processedby the utility for level-two propagation are specified by setting theTC_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 programsTeamcenter administrators can configure Teamcenter to automatically assigncertain types of objects to a project or program when the specified objects are createdby 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 thecurrent 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 Edit→User 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 theuser’s current project or program when the specified object is created. When youassign 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 theTC_allow_remove_owning_project preference and set it to true, whichallows you to right-click the object and choose Project→Remove.

For more information about understanding the implications of theautoAssignToProjectextension on propagation rules extension, see the BusinessModeler IDE Guide.



Understanding the implications of the autoAssignToProject extensionon propagation rules

The autoAssignToProject extension automatically assigns the selected workspaceobject to the user’s current project, as defined by the work context or user settings.

The following table describes the types, operations, and extension points for whichthe autoAssignToProject extension is valid.

Type Operation Extension point

Item and all subtypesof item

IMAN_import

IMAN_save

ITEM_create_from_rev

PostAction

Item revision andall subtypes of itemrevision

IMAN_save

ITEM_baseline_rev

ITEM_copy_rev

ITEM_copy_rev_to_existing

PostAction

Dataset and allsubtypes of dataset

AE_save_dataset PostAction

Form and all subtypesof form

IMAN_save PostAction

Configuring the autoAssignToProject internal extension for a business object hasimplications on the project propagation rules. Project propagation rules determinewhich secondary objects are assigned to a project when a primary business object isassigned. When there is a conflict between a propagation rule and the execution ofthe autoAssignToProject extension, the extension takes precedence.

Note • If a current project is not specified for the user, this extension is ignoredand the object is not automatically assigned. In addition, when theautoAssignToProject extension is configured for an item or ECO, theproject name is preselected in the Assign to Projects page of the item orECO 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 preferencebefore using the autoAssignToProject extension. If this preference isnot set, objects assigned to owning projects cannot be removed usingthe Project®Remove command.

The following points must be considered when implementing theautoAssignToProject extension:• The autoAssignToProject extension applies only to newly created objects;

whereas, propagation of related objects to projects occurs whenever a relationbetween 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 choosingProject®Remove.

• Propagation rules implicitly assign secondary objects to projects. Therefore,when the primary object is explicitly removed from the project, the secondaryobject is also removed from the project.

The following scenarios illustrate the relationship between extensions andpropagation rules when assigning objects to projects.

Scenario Project assignment behavior

The autoAssignToProject extensionis configured for types P (primaryobject) and types S (secondaryobject). A user creates an object oftypeP and an object of type S relatedby the Requirements relation.

Both objects are automatically assigned tothe current project, regardless of whetherthe Requirements relation is specified inthe propagation rule list.

The autoAssignToProject extensionis configured for types P (primaryobject), but not for typesS (secondaryobject). A user creates an object oftypeP and an object of type S relatedby the Requirements relation.

The object of type P is automaticallyassigned to the current project based onthe autoAssignToProject extension. Ifthe Requirements relation is specifiedin the propagation rule list, the type Sobject is also assigned to the project. If theRequirements relation is not specified inthe propagation rule list, the secondaryobject is not assigned to the project.

The autoAssignToProjectextension is configured for typesP (primary object) and types S(secondary object). In addition, theRequirements relation is definedas a propagation rule. The usercreates an object of type P andan object of type S. After creatingthe objects, the user attaches thesecondary object to the primaryobject using the Requirementsrelationship.

Both the primary and secondary objectare automatically assigned to the projectbased on the configuration of the extension,resulting in an explicit assignment ratherthan the implicit assignment that occurswhen an object is assigned to a project basedon propagation rules.

Restricting data creation to within the context of a project or programSet the CreateDataWithNoActiveProgram global constant to false to restrictdata 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 newproject or program.



This feature restricts creation of the following data types (and subtypes of thesedata types):

• Item

• Item revision

• Dataset

• Collaboration context

• Identifier

Other data types, such as folders and forms, are not restricted by theCreateDataWithNoActiveProgram global constant.

To allow data creation outside the context of a program, set the global constantCreateDataWithNoActiveProgram to true.

Controlling assignment of replicated (imported) data to projectsBy default, users who import replicated objects into a database at a remote site mustbe privileged project members for the imported data to be assigned to projects. If theuser is not a privileged project member, the import operation cannot assign the datato an existing project. You can use the TC_multi_site_project_member_bypasspreference to bypass this behavior.

The TC_multi_site_project_member_bypass preference is not included in yourTeamcenter 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 sessionsYou can determine whether users’ current project settings persist from oneTeamcenter session to the next by setting the TC_set_current_project preference.The default behavior is to save the user’s current project setting and apply it thenext time they log on to Teamcenter.

For more information, see the Preferences and Environment Variables Reference.

Selecting different object property values based on project assignmentAs a Teamcenter administrator, you can configure the system so that users seedifferent 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 theColor property shows one set of colors to choose from, and if the item is assignedto project B, the list of values attached to the Color property shows another setof 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 BusinessModeler IDE Guide.

Displaying projects to users based on current group and roleYou can limit which projects are displayed to users throughout the Teamcenterinterface, for example, in the New Item dialog box or the Assign an Object to aProject dialog box. By default, all active projects in which the user is a privilegedteam member are displayed. You can set the TC_show_all_user_projectspreference to limit the display to only the projects that correspond to the user’scurrent group and role.


Using pseudo folders to organize the display of objects in projectsYou can specify properties to be displayed as pseudo folders under a node of theTC_Project business object. After you specify a pseudo folder, all objects defined inthat property are shown in the folder under the TC_Project object.


Project and program preferencesThe 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

• TC_carry_project_info_on_clone


Chapter

3 Configuring smart folder filtering

What are project smart folders? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

Understanding the project smart folder hierarchy . . . . . . . . . . . . . . . . . . . . . 3-2

Top-level smart folder hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2

Top-level hierarchy example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2

Creating the example project top-level hierarchy . . . . . . . . . . . . . . . . . . . . . . 3-3

Associating data objects with smart folders . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3

Using properties to filter data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4

Project smart folder hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5

Project smart folder hierarchy example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5

Apply smart folder filtering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5

Viewing project data in My Teamcenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7Project smart folder filtering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8Apply project smart folder filtering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8


Chapter

3 Configuring smart folder filtering

What are project smart folders?Propagation of related data to projects can result in projects that contain thousandsof objects, many of which are not relevant to project team members (users). You canuse smart folders to filter project data.

Smart folders:

• Provide a mechanism for configuring arbitrary subdivisions of data within aproject based on functional and subfunctional units.

• Allow you to filter project data to only the subset of data that is relevant tothe project members.

• Maintain the context of the project family and program to which the individualprojects belong.

Filtering is applied using the Project application, and the filtered view of project datais presented to users in the My Projects pane in My Teamcenter.For more information, see the Project and Program Guide and the My TeamcenterGuide.

Types of smart foldersThere are two types of smart folders: abstract smart folders and data-driven smartfolders.

Abstract folders:

• Serve as funnels through which project data is filtered.

• Can be nested.

• Can be placed anywhere above or below the project folder in the hierarchy.

• Are used to configure the top-level project-specific smart folder hierarchy.

Data-driven smart folders:

• Are the leaf nodes in the project hierarchy.

• Display the data objects assigned to the project.

Note Smart folders are pseudo folders, they are not physical folder objects inTeamcenter.


Chapter 3 Configuring smart folder filtering

Understanding the project smart folder hierarchyThe smart folder hierarchy is created and maintained using Business Modeler IDEand Project. It consists of three distinct components:

• Top-level smart folder hierarchy.

• Project smart folder hierarchy.

• Properties by which objects (items) in projects are associated with folders inthe hierarchy.

Top-level smart folder hierarchyThe top-level smart folder hierarchy:

• Represents high-level functional units, such as programs and associatedprogram families.

• Provides context and is visible to all users who are members of projects withinthe hierarchy.

Top-level hierarchy exampleThe following figure illustrates a top-level folder.

Program A

Program Family A_1

Program Family A_2

Program Family A_3

Program B

Program Family B_1

Program Family B_2

Each branch in the hierarchy is represented by a list of values (LOV) that specifiessubbranches in the hierarchy. The Project Top Level Smart Folders LOV actsas the root of the hierarchy. It defines the branches in the hierarchy by specifyingthe LOV associated with each branch.

To create the project top-level smart folder hierarchy shown above, you must:

• Create three exhaustive string LOVs, beginning with the LOVs representingthe branches.

• Specify the Project Top Level Smart Folders LOV as the value for theProjectTopLevelSmartFolders global constant.

This enables the display of top-level smart folders in Project.


Configuring smart folder filtering

• Associate data objects with smart folders.

Creating the example project top-level hierarchyThe following process is used to create the top-level smart folder hierarchy shownin Top-level hierarchy example:

1. Create the Program A list of values (LOV), which represents the Program Afolder in the hierarchy.

2. Add the following values to the Program A LOV:

Program Family A_1Program Family A_2Program Family A_3

These values represent the folders that are sub-branches of Program A.

3. Create the Program B list of values (LOV), which represents the Program Bfolder in the hierarchy.

4. Add the following values to the Program B LOV:

Program Family B_1Program Family B_2

These values represent the folders that are sub-branches of Program B.

5. Create the Project Top Level Smart Folders list of values (LOV), whichrepresents the root of the hierarchy.

6. Add the following values to the Project Top Level Smart Folders LOV:

Program AProgram B

These values connect the Program A and Program B branches to the rootof the hierarchy.

7. Specify the Project Top Level Smart Folders as the value of theProjectTopLevelSmartFolders global constant.

For more information about creating the project top-level smart folders inBusiness Modeler IDE, see the Business Modeler IDE Guide.

Associating data objects with smart foldersItem properties are used to filter data objects that are assigned to projects.

The properties used as filters:

• Can be persistent properties.

• Can be compound properties.



• Must be available on the respective object types.

• Are generally custom properties defined by creating a new form and adding acompound property rule to display the properties from the form on the itemobject.

For more information about creating forms and compound property rules, see theBusiness Modeler IDE Guide.

Using properties to filter dataIn the figure shown in Top-level hierarchy example, the top-level smart folderhierarchy consists of programs and program families.

The following process is used to associate items with a program smart folder or aprogram family smart folder:

1. Create custom attributes named program and program family.

2. Expose the program and program family attributes on the item object.

For more information about creating and exposing custom attributes, see theBusiness Modeler IDE Guide.

3. Assign values to the properties of the items that you want to filter.

4. Configure filtering in the Project application.



Note Filtering is based on a combination of smart folder, source type, property,and value. Multiple filter criteria can be applied to data-driven drivensmart folders; however, only one filter criteria can be applied to anabstract smart folder.

For more information about applying filtering criteria, see the Projectand Program Guide.

Project smart folder hierarchyThe project smart folder hierarchy represents subdivisions of the data contained ina project.

The project smart folder hierarchy can be used in the context of a top-level smartfolder hierarchy or independently of a top-level hierarchy.

Project smart folder hierarchy exampleThe following figure illustrates a smart folder hierarchy that represents the projectsavailable at a Teamcenter site.

T–Upper Body (Project)

T467–Side Fittings (Abstract folder representing a subfunctional unit within the project.)

T0247–Frame Backlit Glass (Data-driven folder that displays filtered project data.)

T0248–Frame Frontlit Glass (Data-driven folder that displays filtered project data.)

L-Platform Body (Project)

L678–Side Fittings (Abstract folder Abstract folder representing a subfunctional unit within the project.)

L0395–System Fuel Feed (Data-driven folder that displays filtered project data.)

L0396–Trunk Lid (Data-driven folder that displays filtered project data.)

To create the project smart folder hierarchy shown above, you must:

• Create an exhaustive string LOV with values derived from the TC_Projectreference class.

• Specify the LOV as the value of the ProjectSmartFolders global constant.

For information about setting global constants, see the Business Modeler IDEGuide.

• Associate data objects with smart folders.

Apply smart folder filteringSmart folders provide a mechanism for configuring arbitrary subdivisions of datawithin a project or program based on functional and subfunctional units. Smart



folders are pseudo folders configured in a hierarchical structure; they are notphysical folder objects in Teamcenter.

A project or program hierarchy that defines the abstract and data-driven foldersused to filter project or program data based on object type and attribute is created inBusiness Modeler IDE. This filtering controls what is displayed when users accesstheir project or program in the My Projects view, and it enables them to easily locatedata in large projects and programs.

After the folder hierarchy is defined in Business Modeler IDE, you can choose objecttypes, properties, and property values to filter data for display.

You can also filter project or program data in the absence of a smart folder hierarchyby 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 programobjects 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 funnelsproject or program data of the specified type and property value to the user’sproject or program display.

7. Continue down the tree, selecting folders and applying object types andproperties as filtering criteria.

The cumulative filter criteria is displayed in the table at the bottom of thewindow.

8. When you reach the leaf node (data driven folder) that displays the project orprogram 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 usedto 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 What are projectsmart folders?.

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 filterproject data for the logged-on user or group by setting the value to $USERor $GROUP”. In addition, you can filter data based on properties that havea 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 isdisplayed according to this filter criteria.

Viewing project data in My TeamcenterYou can click the My Projects link in the navigation pane to view your projects andassociated data. This view is determined by the project administrator.

The My Projects view is similar to My Teamcenter views but with the followingdifferences:

• Project Smart Folder HierarchyDisplays 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 MyProjects panes.

• SummaryThe 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 ConsumerPackaged Goods.

For more information, see Getting Started with Consumer Packaged Goods.

Project smart folder filtering

The following considerations apply to project filtering:

• It is not necessary to have an established smart folder hierarchy to apply filtersto your project data. In the absence of a smart folder hierarchy, project objectsare treated as abstract folders.

• Filters defined in My Teamcenter cannot be saved for future use. You must addand remove them as required.

• Multiple filter criteria can be applied to a data-driven smart folder . Whenmultiple filter criteria are applied, all data that meets the criteria appears underthe project or program. A logical OR is applied between each row in the filtertable to determine the display results.

• Only one filter criteria can be applied to an abstract smart folder . If multiplefilters are applied to an abstract smart folder, no project data is displayed.

Apply project smart folder filtering

1. Click My Projects in the Quick Links section of the navigation pane in MyTeamcenter.

The My Projects view appears.

2. In the My Projects view, expand a project object to view the data associatedwith the project.



Note Objects are displayed according to the project smart folder hierarchyconfiguration defined by the project administrator and/or by any filtersthat you apply.

If a smart folder hierarchy is configured for your project, you see folderswhen you expand your project. Expand these folders to reveal yourproject 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 theSummary 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 theselected project.

The Apply filters dialog box appears.

5. Click the Add a filter button to populate a row in the table.

6. Choose filter criteria by clicking the Source Type, Property, and/or Value cellsand selecting a value from the list.

For example, you can add a filter to display the project data owned by theEngineering 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 removeall 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, youcannot save a filter configuration and retrieve it for future use.


Appendix

A Glossary


Appendix

A Glossary

A

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

Access Manager (AM)Teamcenter application that enables the system administrator to grant users accessto Teamcenter objects.

accessorAccess Manager component that grants or denies privileges to clusters of users whoshare certain common traits (for example, perform the same function or work onthe same project).

B

BOM viewTeamcenter 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 ofother data. BOM view revisions are meaningful only in the context of the itemrevisions for which they are created.

Business Modeler IDETeamcenter application that enables a customer to define data model objects such asbusiness objects, classes, attributes, lists of values, and rules.

BVRSee BOM view revision (BVR).

D

datasetTeamcenter workspace object used to manage data files created by other softwareapplications. Each dataset can manage multiple operating system files, and eachdataset references a dataset tool object and a dataset business object.

E

extensionMethod or listener implemented for an extension point.

PLM00049 J Project and Program Guide A-1

Appendix A Glossary

extension ruleBusiness rule that adds predefined behavior to a business object’s operation and firesas a precondition, preaction, or postaction.

G

group (Organization)Organizational grouping of users at a site. Users can belong to multiple groupsand must be assigned to a default group.

H

hierarchyStructure in which each node can have only one parent but possibly multiple siblingsand children.

I

itemWorkspace object generally used to represent a product, part, or component. Itemscan contain other workspace objects including other items and object folders.

item relationDescription of an association between a Teamcenter item and a piece of informationthat describes or is related to the item.

item revisionWorkspace object generally used to manage revisions to items.

item revision relationDescription of an association between a Teamcenter item revision and a piece ofinformation that describes or is related to the item revision.

M

Manufacturing Process PlannerTeamcenter manufacturing process management application that enables a user todesign a plan detailing how to manufacture a product.

Multi-Structure ManagerTeamcenter application that enables users to view and manipulate data in a specificcontext.

My TeamcenterIn the Teamcenter rich client and thin client, application that is the main accesspoint for managing product information. My Teamcenter provides the functionalityfor creating objects in the Teamcenter database, querying the database for objects,checking in and checking out objects, and managing tasks. Users can also openobjects, automatically launching the related application.

Each user has a personal My Teamcenter window that displays product informationas graphical objects. Although users share product information across the enterprise,they organize this information individually in personal workspaces.

A-2 Project and Program Guide PLM00049 J

Glossary

N

named ACLNamed group of access controls. See also access control list (ACL).

named referenceFile types that are managed by a dataset. Datasets are the only workspace objectsthat use named references.

navigation paneRich client framework component that displays buttons of the applications availablefor use in the rich client. Clicking the application button launches the application.

O

OrganizationTeamcenter application that enables a system administrator to create and managecritical Teamcenter files and database entries. It is the point of access for creating acompany’s virtual organization and for performing system administration activitiessuch as volume creation, maintenance, and site administration. Organizationenables creation and management of person, user, role, and group definitions;definition of the hierarchical structure of the Teamcenter organization; managementof data volumes; and establishment and maintenance of Teamcenter sites.

ownerUser that owns an object, initially the user who created it. Ownership can betransferred from the owner to another user. An object owner usually has privilegesthat are not granted to other users (for example, the privilege to delete the object).

owning groupGroup that owns an object, usually the group of the user creating the object. Becauseusers commonly share data with other members of a group, additional privileges maybe granted to the owning group (for example, the privilege to write to the object).

P

Part PlannerTeamcenter manufacturing process management application that enables a user todesign a plan detailing how to manufacture a part.

Plant DesignerTeamcenter manufacturing process management application that allows users todesign, modify, import, and export a factory structure.

preferenceConfiguration variable stored in a Teamcenter database and read when a Teamcentersession is initiated. Preferences allow administrators and users to configure manyaspects of a session, such as user logon names and the columns displayed by defaultin a properties table.

privileged team memberProject team member with privileges to assign and remove objects from thatproject. Compare with project team member.


Appendix A Glossary

programBasis for identifying a group of objects available to multiple organizations, suchas program teams, development teams, suppliers, and customers for a particularpiece of work.

Program applicationTeamcenter application used to define programs and assign program team members,program team administrators, and privileged team members.

program team administratorProgram team member with privileges to modify program information and programteam members for that program. Only one program team administrator is allowedper program.

program team memberTeam member (user) who does not have privileges to assign objects to or removeobjects from their programs. Compare with privileged team member.

projectBasis for identifying a group of objects available to multiple organizations, such asproject teams, development teams, suppliers, and customers for a particular pieceof work.

ProjectTeamcenter application used to define projects and assign project team members,project team administrators, and privileged team members.

Project administratorTeamcenter super user with unrestricted access to administer projects they createusing the Project application. A Project administrator creates, modifies, and deletesproject information and team members.

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

project team memberTeam member who does not have privileges to assign objects to or remove objectsfrom their projects. Compare with privileged team member.

R

relationDescription of an association between a Teamcenter object and a piece of informationthat describes or is related to the object.

rich clientJava-based user interface to Teamcenter installed on user workstations. The richclient accesses Teamcenter databases using a remote or local server. Compare tothin client.

roleFunction-oriented cluster of users that models skills and/or responsibilities. Thesame roles are typically found in many groups. In Access Manager, role is an accessor


Glossary

used to grant privileges to all users with the same skills and/or responsibilitiesregardless of project.

role in groupSpecific role in a specific group. In Access Manager, role in group is an accessorused to grant privileges to all users with the same skills and/or responsibilitiesin the same group.

role in owning groupSpecific role in the object’s owning group. In Access Manager, role in owninggroup is an accessor used to grant privileges to users with the same skills and/orresponsibilities on the same project. For example, all designers in the owning groupare usually granted write privilege on their development data.

rootStarting point of a hierarchy. Hierarchies are usually displayed as hanging treeswith the root of the structure at the top and the leaves at the bottom.

rules-based protectionConditions or rules that control who can or cannot access objects. These rules areglobal (that is, they affect the entire Teamcenter site) and are enforced by the AccessManager. These rules are defined by a system administrator.

rule treeAccess Manager component the system administrator uses to grant users access toTeamcenter objects. It is a tree of rules and access permissions that when processeddetermines the access that each user has to a specified object.

S

siteIndividual 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 toimplement Teamcenter at that site.

Structure ManagerTeamcenter application that enables creation of generic product structures that canbe configured to show the product structure that is in production, effective on acertain date, used by a particular customer, and so forth. Structure Manager enablescreation and modification of a product structure and its associated occurrence data,display of a product structure in a multilevel indented format, and viewing graphicstightly coupled to the structure for easy identification of a component by location inthe structure or in the embedded viewer.

T

thin clientTeamcenter user interface that provides a streamlined browser-based view of productinformation stored in a Teamcenter database. The thin client is configured in theWeb tier, which creates and serves its Web pages to the client. Compare to rich client.


Appendix A Glossary

U

userDefinition that is the mechanism by which Teamcenter identifies and interacts witheach user. User definitions contain a name (derived from the person definition), userID, operating system name, and password.

W

work contextObject containing user, group, role, and project requirements for a particular task.Work contexts streamline the definition of the correct user settings required toperform tasks. For example, a user typically assigned three types of tasks can createthree work contexts reflecting the required group/role settings. Rather than loggingout and logging back in with the required group/role settings, right-clicking a taskdisplays the user’s defined work contexts. Selecting the appropriate work contextautomatically changes the user’s group/role settings. Work contexts can also definethe current project, if project functionality is used at the site.


Index

A

Abstract smart folders . . . . . . . . . . . . . . 3-1Activating a program . . . . . . . . . . . . . . . 1-5Activating a project . . . . . . . . . . . . . . . . 1-5AM Rules tab . . . . . . . . . . . . . . . . . . . . 19Assigning BOM data to programs . . . . . . 2-3Level-one propagation . . . . . . . . . . . . 2-3Level-two propagation . . . . . . . . . . . . 2-3

Assigning BOM data to projects . . . . . . . 2-3Level-one propagation . . . . . . . . . . . . 2-3Level-two propagation . . . . . . . . . . . . 2-3update_project_bom utility . . . . . . . . . 2-3

Assigning related objects to programs . . . 2-2Assigning related objects to projects . . . . 2-2Assigning team membersGroups . . . . . . . . . . . . . . . . . . . . . . . 1-7Hierarchical group behavior . . . . . . . . 1-7Roles . . . . . . . . . . . . . . . . . . . . . . . . 1-8

autoAssignToProject extension . . . . . 2-4–2-5Automatically assigning data to projectsautoAssignToProject extension . . . . . . 2-4Eligible data types . . . . . . . . . . . . . . . 2-4

C

Configure programRestrict data creation to program

context . . . . . . . . . . . . . . . . . . . . . 2-6Configuring Program . . . . . . . . . . . . . . . . 8Configuring Project . . . . . . . . . . . . . . . . . 8Configuring smart folder filtering . . . . . . 3-5ConstantsCreateDataWithNoActiveProgram . . . . 2-6

Copying an existing program . . . . . . . . . 1-4Copying an existing project . . . . . . . . . . 1-4Current project . . . . . . . . . . . . . . . . . . . 2-7

D

Data driven smart folders . . . . . . . . . . . 3-1Deactivating a program . . . . . . . . . . . . . 1-5Deactivating a project . . . . . . . . . . . . . . 1-5Definition pane . . . . . . . . . . . . . . . . . . . 18Description box . . . . . . . . . . . . . . . . . 1-4

ID box . . . . . . . . . . . . . . . . . . . . . . . . 1-4Name box . . . . . . . . . . . . . . . . . . . . . 1-4

Definition tab . . . . . . . . . . . . . . . . . . . . 18Description box . . . . . . . . . . . . . . . . . . . 1-4

EEnabling Program . . . . . . . . . . . . . . . . . . 7Enabling program security . . . . . . . . . . . 1-5Enabling Project . . . . . . . . . . . . . . . . . . . 7Evaluating Role in Project accessor . . . . 1-14Evaluating Role in Projects of Objectaccessor . . . . . . . . . . . . . . . . . . . . . . 1-14

IID box . . . . . . . . . . . . . . . . . . . . . . . . . 1-4In Current Program rule . . . . . . . . . . . 1-13In Inactive Program rule . . . . . . . . . . . 1-13In Invisible Program rule . . . . . . . . . . . 1-14Inactive Program ACL . . . . . . . . . . . . . 1-14Invisible Program ACL . . . . . . . . . . . . 1-14Is Owned By Program rule . . . . . . . . . . 1-14Is Program Member rule . . . . . . . . . . . 1-13

LLevel-one propagation . . . . . . . . . . . . . . 2-3Level-two propagation . . . . . . . . . . . . . . 2-3Level-two propagation preference . . . . . . 2-4Libraries tab . . . . . . . . . . . . . . . . . . . . . 19

MModifying an existing program . . . . . . . . 1-5Modifying an existing project . . . . . . . . . 1-5My Projects viewUsing . . . . . . . . . . . . . . . . . . . . . . . . 3-8

NName box . . . . . . . . . . . . . . . . . . . . . . . 1-4Non-privileged project team member . . . 12Not Current Program ACL . . . . . . . . . . 1-13Not Program Member ACL . . . . . . . . . 1-13

PLM00049 J Project and Program Guide Index-1

Index

OOrganizing program information . . . . . . 3-5Organizing project information . . . . . . . . 3-5

PAM_PROJECT_MODE preferenceAM_PROJECT_MODE . . . . . . . . . . . 1-14

PreferencesProject and program . . . . . . . . . . . . . . 2-8

Prerequisites for Program . . . . . . . . . . . . 7Prerequisites for Project . . . . . . . . . . . . . 7Privileged team member . . . . . . . . . . . . 11ProgramCopying . . . . . . . . . . . . . . . . . . . . . . 1-4Enabling . . . . . . . . . . . . . . . . . . . . . . . 7Prerequisites . . . . . . . . . . . . . . . . . . . . 7Program team administrators . . . . . . . 11

Program description . . . . . . . . . . . . . . . 1-4Program ID . . . . . . . . . . . . . . . . . . . . . 1-4Program name . . . . . . . . . . . . . . . . . . . 1-4Program propagation rules . . . . . . . . . . 2-2Program team administrators . . . . . . . . 11Program-level securityAccess rules . . . . . . . . . . . . . . . . . . . 1-10Default access rules . . . . . . . . . . . . . 1-11In Current Program rule . . . . . . . . . 1-13In Inactive Program rule . . . . . . . . . 1-13In Invisible Program rule . . . . . . . . . 1-14Inactive Program ACL . . . . . . . . . . . 1-14Invisible Program ACL . . . . . . . . . . . 1-14Is Owned By Program rule . . . . . . . . 1-14Is Program Member rule . . . . . . . . . . 1-13Not Current Program ACL . . . . . . . . 1-13Not Program Member ACL . . . . . . . . 1-13Projects ACL . . . . . . . . . . . . . . . . . . 1-14

Program-level security tasksConfiguring automatic assignment to

programs . . . . . . . . . . . . . . . . . . . 2-4Setting propagation rules . . . . . . . . . . 2-2

ProgramsAssigning BOM data to . . . . . . . . . . . . 2-3Assigning related objects . . . . . . . . . . 2-2Automatically assigning data to . . . . . 2-4Creating . . . . . . . . . . . . . . . . . . . . . . 1-4Deactivating . . . . . . . . . . . . . . . . . . . 1-5Enabling . . . . . . . . . . . . . . . . . . . . . . 1-5Modifying . . . . . . . . . . . . . . . . . . . . . 1-5Propagation rules . . . . . . . . . . . . . . . . 2-2Reload tree . . . . . . . . . . . . . . . . . . . . 1-2Searching . . . . . . . . . . . . . . . . . . . . . 1-1

ProjectCopying . . . . . . . . . . . . . . . . . . . . . . 1-4Enabling . . . . . . . . . . . . . . . . . . . . . . . 7

Filters . . . . . . . . . . . . . . . . . . . . . . . . 3-8Modifying . . . . . . . . . . . . . . . . . . . . . 1-5Prerequisites . . . . . . . . . . . . . . . . . . . . 7Privileged team member . . . . . . . . . . . 11Project administrator . . . . . . . . . . . . . 11Project team administrators . . . . . . . . 11Smart folders . . . . . . . . . . . . . . . . . . . 3-8

Project administrator . . . . . . . . . . . . . . 11Project and program preferences . . . . . . 2-8Project description . . . . . . . . . . . . . . . . 1-4Project ID . . . . . . . . . . . . . . . . . . . . . . . 1-4Project name . . . . . . . . . . . . . . . . . . . . 1-4Project Objects ACL . . . . . . . . . . . . . . 1-12Project propagation rules . . . . . . . . . . . . 2-2Project smart folder hierarchy . . . . . . . . 3-5Project smart folders . . . . . . . . . . . . . . . 3-1Abstract folders . . . . . . . . . . . . . . . . . 3-1Data driven folders . . . . . . . . . . . . . . 3-1Project smart folder hierarchy . . . . . . . 3-5ProjectTopLevelSmartFolders global

constant . . . . . . . . . . . . . . . . . . . . 3-3Top level smart folder hierarchy . . . . . 3-2

Project team administrators . . . . . . . . . . 11Project-level securityAccess rules . . . . . . . . . . . . . . . . . . . 1-10Default access rules . . . . . . . . . . . . . 1-11Multi-Site Collaboration import and

export . . . . . . . . . . . . . . . . . . . . 1-16Project Objects ACL . . . . . . . . . . . . . 1-12Projects ACL . . . . . . . . . . . . . . . . . . 1-12

Project-level security tasksApplying Access Manager rules . . . . . 1-10Configuring assignment of related

objects . . . . . . . . . . . . . . . . . . . . . 2-1Configuring automatic assignment to

projects . . . . . . . . . . . . . . . . . . . . 2-4Defining default naming rules . . . . . . . 2-1Setting propagation rules . . . . . . . . . . 2-2

Projects . . . . . . . . . . . . . . . . . . . . . . . 1-14Assigning BOM data to . . . . . . . . . . . . 2-3Assigning related objects . . . . . . . . . . 2-2Automatically assigning data to . . . . . 2-4Create . . . . . . . . . . . . . . . . . . . . . . . . 1-1creating . . . . . . . . . . . . . . . . . . . . . . 1-4Deactivating . . . . . . . . . . . . . . . . . . . 1-5Multi-Site Collaboration

environment . . . . . . . . . . . . . . . . 1-17Propagation rules . . . . . . . . . . . . . . . . 2-2Reload tree . . . . . . . . . . . . . . . . . . . . 1-2Searching . . . . . . . . . . . . . . . . . . . . . 1-1

Projects ACL . . . . . . . . . . . . . . . . . . . 1-12ProjectTopLevelSmartFolders globalconstant . . . . . . . . . . . . . . . . . . . . . . . 3-3Propagation

Index-2 Project and Program Guide PLM00049 J

Index

Level one . . . . . . . . . . . . . . . . . . . . . . 2-3Level two . . . . . . . . . . . . . . . . . . . . . 2-3

Propagation rules . . . . . . . . . . . . . . . . . 2-2

RReloadProgram tree . . . . . . . . . . . . . . . . . . . 1-2Project tree . . . . . . . . . . . . . . . . . . . . 1-2

Reload program tree . . . . . . . . . . . . . . . 1-2Reload project tree . . . . . . . . . . . . . . . . 1-2

SSearching for programs . . . . . . . . . . . . . 1-1Searching for projects . . . . . . . . . . . . . . 1-1Security Rules pane . . . . . . . . . . . . . . . 19Setting current project . . . . . . . . . . . . . . 2-7Smart folder filtering . . . . . . . . . . . . . . . 3-5Starting Program . . . . . . . . . . . . . . . . . . 8

Starting Project . . . . . . . . . . . . . . . . . . . 8

TTC_project_propagate_from_datasetpreference . . . . . . . . . . . . . . . . . . . . . . 2-4TC_set_current_project preference . . . . . 2-7Team membersPrivileged team member . . . . . . . . . . . 11Program team administrators . . . . . . . 11Project administrator . . . . . . . . . . . . . 11Project team administrators . . . . . . . . 11

Top level smart folder hierarchy . . . . . . . 3-2

Uupdate_project_bom utility . . . . . . . . . . . 2-3Utilitiesupdate_project_bom . . . . . . . . . . . . . . 2-3

PLM00049 J Project and Program Guide Index-3

Documents

Project