Teamcenter 10.1 Organization Guide - Help!help.aviacons.ru/tc10doc/PDF/en_US/tdocExt/pdf/organization.pdf · Proprietary and restricted rights notice This software and related documentation

Teamcenter 10.1

Organization Guide

Publication NumberPLM00029 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 Organization Guide PLM00029 J

Contents

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

Getting started with Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

What is Organization? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1Before you begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2Organization interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2Basic concepts for using Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5Basic tasks using Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7Understanding the Teamcenter Rapid Start organization . . . . . . . . . . . . . . . . 1-18

Defining sites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

What is a site? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1Create a site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1Modify a site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3Delete a site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3

Defining volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

What is a volume? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1Create a volume . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1Modify volume location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3Modify volume properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4Delete a volume . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5Controlling volume access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5Reallocating volume data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7

Defining roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

What is a role? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1Create a role . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2Modify a role . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2Delete a role . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2Add an existing role to a group using the Organization Role wizard . . . . . . . . . 4-3Add a new role to a group using the Organization Role wizard . . . . . . . . . . . . 4-4Assign a default role within a group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4

Defining groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

What is a group? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1What is a subgroup? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2Creating a group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2Modify a group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7Delete a group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7Group terms and concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8Group hierarchies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9Moving groups within the hierarchy and volume access . . . . . . . . . . . . . . . . . 5-10

PLM00029 J Organization Guide 3

Contents

Managing group members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10Add existing group as subgroup using the Organization Group wizard . . . . . . . 5-12Add new subgroups using the Organization Group wizard . . . . . . . . . . . . . . . 5-14

Defining persons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1

What is a person? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1Create a person . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1Modify a person . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2Delete a person . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3

Defining users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1

What is a user? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1Create a user . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1Modify a user . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5Deleting users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-6Delete a user . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-6Specifying password restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-7Configuring ADA for ITAR support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-7Changing user status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-8Add an existing user to a role/group using the Organization User wizard . . . . . 7-9Add a new user to a group/role using the Organization User wizard . . . . . . . . 7-11Managing internal, external, and remote user constructs . . . . . . . . . . . . . . . . 7-12Mapping and synchronization considerations . . . . . . . . . . . . . . . . . . . . . . . . 7-13

Defining administrative privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1

Considerations for managing administration accounts . . . . . . . . . . . . . . . . . . 8-1infodba account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2System administration accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2

Defining disciplines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1

What is a discipline? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1Create a discipline . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1Modify a discipline . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2Delete a discipline . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2Add a discipline to a group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2Remove a discipline from a group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3

Defining calendars . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1

Selecting which calendar type to use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1Modify the base calendar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1Create a user calendar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-2Modify a user calendar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-3

Defining external applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1

What is an external application? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1Creating external applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1Modify an external application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1Delete external applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-2

Defining languages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-1

4 Organization Guide PLM00029 J

Contents

What is a language? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-1Create a language . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-1Modify a language . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-2Delete a language . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-2

Defining graphic priority lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1

What is a graphic priority list? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1Create a graphic priority list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1Modify a graphic priority list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-2Delete a graphic priority list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-2

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

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

PLM00029 J Organization Guide 5

Chapter

1 Getting started withOrganization

What is Organization? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

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

Organization interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2Organization buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3Using Organization find . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4Rich client perspectives and views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5

Basic concepts for using Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5

Basic tasks using Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7Building the hierarchy using the Organization List tree . . . . . . . . . . . . . . 1-7Building the hierarchy using the Organization tree . . . . . . . . . . . . . . . . . 1-8Considerations for creating your virtual organization . . . . . . . . . . . . . . . . 1-9Creating your virtual organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11Filtering the Organization hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-13

Filter users by home site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-13Filter objects by site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-14

Exporting Organization objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-15Export Organization objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-17

Understanding the Teamcenter Rapid Start organization . . . . . . . . . . . . . . . . 1-18

PLM00029 J Organization Guide

Chapter

1 Getting started withOrganization

What is Organization?The Organization application enables you to create and maintain your company’sorganization within Teamcenter by organizing user accounts and their respectivepermissions and user groups. User accounts help you:

• Track changes to objects.

• Control access and privileges.

• Manage default object ownership.

Use this administrative application to perform tasks like:

• Setting up your organization for the first time

• Required organizational tasks:

o Defining sites

o Defining volumes

o Defining roles

o Defining groups

o Defining persons

o Defining users

• Optional organizational tasks:

o Defining administrative privileges

o Defining disciplines

o Defining calendars

o Defining external applications

• Miscellaneous tasks:

o Defining languages

PLM00029 J Organization Guide 1-1

Chapter 1 Getting started with Organization

o Defining graphic priority lists

Before you beginPrerequisites You must be a member of the dba group or be granted

authorization by a user with system administration privilegesin order to make modifications within Organization. Thisapplication is read-only to non-dba group users.

EnableOrganization

Organization does not need to be enabled before you can use it,but during installation, this feature must be selected.

If you have trouble accessing Organization, see your systemadministrator. It may be a licensing issue.

Note You can log on to Teamcenter only once. If you try tolog on to more than one workstation at a time, you willsee an error message.

ConfigureOrganization

Organization does not need to be configured before you use it.

StartOrganization Click Organization in the navigation pane.

Organization interface

1-2 Organization Guide PLM00029 J

Getting started with Organization

1 Organizationtree

TheOrganization tree enables you to view the structureof your organization at a glance. By expanding andcollapsing branches of the tree, you can view andmanage the organizational structure. Selecting a nodestarts Organization wizards used to create groups,subgroups, roles, disciplines, and users.

2 Filter byHome Sitebox

Use the Filter by Home Site box to filter objects (group,role, or user) by owing location.

For information about filtering the Organizationhierarchy, see Filtering the Organization hierarchy.

3 Find box Use the find box to filter the Organization tree to

find groups , roles , and users within theorganization. You can also use the find box to reloadthe Organization tree and to locate inactive groupmembers.

For more information about using the find box, seeUsing Organization find.

4 OrganizationList tree

The Organization List tree enables you to view andmanage the components of your organization by listinggroups, roles, disciplines, users, and persons. You canalso use the Organization List tree to manage sites,external applications, volumes, and calendars.

5 Definitionpane

Displays the properties for the selected Organizationobject.

Organization buttons

Buttons Description

Externally managed person definition.

Remotely managed person definition.

Internally managed person definition.

Externally managed user definition.

Remotely managed user definition.

Internally managed user definition.

Externally managed group definition.

Remotely managed group definition.



Buttons Description

Internally managed group definition.

Externally managed role definition.

Remotely managed role definition.

Internally managed role definition.

Using Organization findIf you experience difficulty browsing through the organization hierarchy to find acertain group, role, or user, you can use the Organization find function to locate it.

Use any of the following buttons in the Organization tree pane:

• Find group

• Find role

• Find user

• Reload the Organization tree

• Suppress/display inactive group members

The Organization find feature works in an identical way for each mode (group,role, and user). To use Organization find, type the text into the box and clickthe appropriate button. Note that the wildcard (*) character is accepted. TheOrganization tree is reloaded with the results of your search. If there are nomatches, a message informs you of this.

You can also filter objects by owning location (remote or local).

Note Replicated (remote) objects (user, group, role, and person) have two green

dots beside them to designate them as remote objects .

After performing a search, you can reload the Organization tree by clicking theReload button . This refreshes the organization in the current session; changesmade in different sessions cannot be guaranteed to be updated.

Note To get new organization objects (groups, subgroups, roles, users, anddisciplines) and modified objects in another session to display in theOrganization tree, select View®Refresh Window in the Organizationperspective. This action refreshes components loaded in the current sessionso that changes made in another session are available in the current session.Because this action usually takes a long time, use this when you want yourcurrent session to be in sync with the latest change in the database byanother session.



To suppress the display of inactive members in a group in the Organization tree, use

the Suppress inactive group members button in the Organization pane.

For information about filtering the Organization hierarchy, see Filtering theOrganization hierarchy.

For information about suppressing the display of inactive group members, seeSuppress the display of inactive group members in the Organization tree.

Rich client perspectives and views

Within the Teamcenter rich client user interface, application functionality isprovided in perspectives and views. Some applications use perspectives and views toarrange how functionality is presented. Other applications use a single perspectiveand view to present information.

Note Your administrator can use the HiddenPerspectives preference to preventthe display of some Teamcenter perspectives in the rich client.

For information about editing preference values, see the Preferences andEnvironment Variables Reference.

If your site has online help installed, you can access application and view help fromthe rich client Help menu or by pressing F1.

For more information about rich client perspectives and views, see the Rich ClientInterface Guide.

Basic concepts for using OrganizationAn organization is made up of groups. Groups contain subgroups, users, and persons.



• A group is a grouping of users who share data.

You can configure access to data owned by the group by:

o Using the Security setting, which allows or restricts access to data.

o Setting authorized data access (ADA) and International Traffic in ArmsRegulations (ITAR), which allows or restricts access to data based onclearance levels and data classification.

• A subgroup is a group with another group designated as its parent. A subgroupcan also be designated as a parent group itself. The position of subgroups withinthe Organization hierarchy can be managed by parenting and reparentinggroups.

• A role represents specific skills and/or responsibilities. The same roles aretypically found in many groups. The system grants data access based on groupand role.

• A user can belong to multiple groups and must be assigned to a default group.Each user in the group is assigned a role.

In addition, you can associate the following with users by:

o Creating a calendar, which allows you to set days off, holidays, and hours ina day for individual resources.

o Setting ADA and ITAR attributes to allow or restrict data access.



o Setting the licensing level to determine whether the user can create andmodify data or only view data.

• A person is a definition containing real-world information about each Teamcenteruser, such as name, address, and telephone number.

Within Organization you can view both local and replicated (remote) objects.



Basic tasks using OrganizationThe Organization application supports two methods of building the organizationhierarchy:

• Use the Organization List tree to build the hierarchy from the bottom up.

• Use the Organization tree wizards to build the hierarchy from the top down.

Note The make_user utility allows you to create your organization from acommand line or script. Use this utility to:

• Increase productivity.

Load your entire organization with one command.

• Perform disaster recovery.

Back up your organization.

• Perform migration.

You can populate your test and production environments.

For more information about the make_user utility, see the UtilitiesReference.

Building the hierarchy using the Organization List tree

When building the hierarchy from the bottom up, a person definition precedes auser definition, which in turn precedes a subgroup and/or group definition. Eachdefinition is constructed separately and manually associated to the other levelsof the organization hierarchy.



For example, user X is hired by ABC Company as a designer. User X is working as amember of a new development group responsible for designing products A and B.The following sequential actions are required to add user X to the organizationusing the Organization List tree:

1. Create a person definition reflecting user X’s real-world information, such asaddress and telephone number.

2. Create a user definition containing system-related information such as PersonName (this associates the person definition to the user definition), User ID, OSName, and Password.

3. Create the groups. You create a parent development group and Product A andB subgroups. One of these groups is specified as the default group in user X’suser definition.

4. Create the Designer role. You assign the role to the subgroups using the Groupspane.

To create persons, users, groups and subgroups, and roles by this method, selecta node from the Organization List tree and use the corresponding pane to definethe properties of the new entity.

Building the hierarchy using the Organization tree

Using the Organization tree, wizards are available to guide you through the creationof the groups and subgroups, users, roles, and persons that make up the organizationhierarchy. You can begin at the highest level in the Organization tree and seamlesslytraverse the hierarchy, creating new objects and/or adding existing objects using theOrganization wizards (Group, Role, and User). User and person definitions can becreated simultaneously using the Organization User wizard.



For example, user Y is hired by ABC Company as product validation manager for anew group being established to assure the quality of ABC Company’s products. Inone seamless process, you can add the new product validation group, the productvalidation manager role, and user Y’s user and person definitions to the ABCCompany Organization tree using the Organization wizards. You:

• Create the new parent group, Product Validation, within the Organization tree.

• Add the role of Product Validation Manager to the Product C Development group.

• Add the user and person definitions to the role/group.

To create new definitions or add existing persons, users, groups and subgroups, androles to the organization using this method, select a node from the Organization treeand start one of the Organization wizards from within the corresponding pane.

You can also perform organization management by creating, adding, modifying, andin some cases removing objects from the hierarchy, from within the Organizationtree.

Note • You cannot delete organization objects from the database from withinthe Organization tree. You must use the Organization List tree instead.

• Use the TC_org_tree_expansion preference to enable the expansion ofthe Organization tree based on the number of tree nodes and to increaseperformance.

Considerations for creating your virtual organization

Before you create your virtual organization, consider these points.



Consideration Description

What is the best way tostructure my organization?

Creating your virtual organization based on yourcompany’s organization chart is not always a goodidea because the structure of your company is alwayssubject to change.

You should look for a stable organization hierarchythat requires little or no changes.

How can I quickly set up myorganization?

The make_user utility is especially helpful whenfirst setting up your organization. This utility allowsyou to create your organization from a commandline or script. It enables you to load your entireorganization with one command.

For information about the make_user utility, seethe Utilities Reference.

What is a good suggestionfor setting the user ID?

When setting the user ID, use your Human Resourcedepartment’s recommendation as a possibility for aunique identifier.

What kind of security can Iset for groups?

You can set different types of security:

• Project-level

For more information about group rules forproject-level security, see the Project andProgram Guide.

• Authorized data access (ADA)

Allows or restricts access to data based onclearance levels and data classification

For information about configuring andadministering authorized data, see the SecurityAdministration Guide.

• International Traffic in Arms Regulations (ITAR)

For information about configuring andadministering authorized data access forintellectual property (IP) and ITAR, see theSecurity Administration Guide.



Consideration Description

What do I do if a user is outof the office for an extendedperiod of time (for example,medical leave)?

You can change the status of a user from active toinactive.

However, you cannot deactivate group members ifthey have any pending Workflow tasks. You mustfirst delegate these tasks to another group memberand then deactivate the user. You can use theglobal_transfer utility to transfer one user’s tasksto another user.

For more information, see the Utilities Reference.

You can also reassign the user’s tasks using the MyTeamcenter inbox feature.

For more information, see theMy Teamcenter Guide.

For information about changing user status, seeChanging user status.

When users change groupswithin the organization,how can I deactivate theirmembership within agroup?

When users leave the organization or change groupsor roles within the organization, you can deactivatetheir membership within a group. This preventsthem from logging on to the system as a member ofthe group and denies them access to informationrelated to their previous group and role.

For information about deactivating a group member,see Deactivate a group member.

A user is leaving thecompany. What do I need todo?

Because database objects are owned by individualusers, you must determine what to do with anyobjects owned by the user before deleting the userfrom the database.

• Before deleting the user object from theorganization, you must remove all relationships.

• Also, you must delete all of the user’s owneditems or transfer the owned items to anotheruser.

For information about deleting users, see Deletingusers.

Creating your virtual organization

As a Teamcenter administrator, you use the Organization application to create andmaintain your company’s virtual organization within Teamcenter. Because yourcompany’s organizational structure can change over time, it is important whendefining groups and roles that you look for a stable organization hierarchy thatrequires little or no change.



Note For group, role, user, and person objects, the Owning site property fieldindicates the site that manages the object. The Home site property fieldindicates the working site for the object. Both fields are displayed for eachof these objects. However, if one of the property fields is null, it indicatesthe object is local.

The basic process of creating a virtual organization includes the following stages:

1. Establish Teamcenter sites.

For information about creating sites, see Create a site.

2. Define the structure of your organization.

Note Roles, volumes, and persons are independent definitions. Any of thesecan be created without consideration of the other definitions.

a. Create volumes.

For information about creating volumes, see Create a volume.

b. Enable File Management System (FMS) control of new volumes.

c. Create roles.

Warning Do not delete the roles provided with Teamcenter. They arerequired for the product to function properly.

For information about creating roles, see Create a role.

d. Create groups and subgroups.

Warning Do not delete the system group provided with Teamcenter. It isrequired for the product to function properly.

Note Groups and users are dependent definitions. To create group anduser definitions, other definitions must exist:

• Group definitions require that a role is defined and suggest avolume be defined.

• User account definitions require a person definition and a groupdefinition.

For information about creating groups and subgroups, see Create a group orsubgroup using the Organization List tree.

e. Add roles to groups.

For information about adding roles to groups, see step 8 in Create a group orsubgroup using the Organization List tree.

3. Create users and persons.

a. Create person definitions.

For information about creating persons, see Create a person.



b. Create user accounts.

Note Themake_user utility allows you to create your organization froma command line or script.

For more information about themake_user utility, see the UtilitiesReference.

For information about creating users, see Create a user.

Filtering the Organization hierarchy

You can perform two types of object filtering of the Organization hierarchy:

• Filter users by home site

For example, you can filter for all users by home site or all sites.

• Filter objects by site

For example, you can filter for replicated (remote) or local objects by site.Filtering is activated only after you click one of the following buttons: Group ,

Role , or User .

Filter users by home site

1. From the Filter by Home Site box, select the home site on which to filter eitherby selecting All or a specific home site.

2. Type the name of the user in the search box, or type an asterisk (*) to displayall users.

3. Click the User button to display all users on the selected site that matchthe search criteria.

For example, the following figure shows the results for a search for all users havingthe home site IMC–2108652978.



Filter objects by site

You can use the Organization application to filter objects by site: all objects, localobjects, and replicated objects.

1. Select the home site on which to filter either by selecting All or a specific homesite.

2. Type the text string on which to search. You can enter the entire text string ora partial string using an asterisk (*).

3. Click the object button (Group, Role, or User).

This displays all objects of the selected type that are found on the designated site.



For example, the following results are all replicated users whose name begins withcaa that are found on all sites.



Exporting Organization objects

You can replicate organizational objects (users, groups, roles, persons, and groupmembers) using the Multi-Site export function to provide a global organization. Aglobal organization allows centralized administration for organization data usingMulti-Site Collaboration technology. You select a central site in your environmentto store the master copies or organization data’ the other sites contain read-onlyreplicas. You can make changes at the master site and synchronize the replicas atthe other sites. Global organization objects can be imported and exported much thesame as other Teamcenter objects, with the exception that they cannot have theirownership transferred to another site from the master site.

Note Existing sites that already have identical organization structures, alsoknown as cloned organization objects, must migrate the structure to thereplicated model to establish a true global organization.

For more information about global organization objects, see the Multi-SiteCollaboration Guide.

These exported (replicated) objects are created with the owning site maintainingthe master object, as with other Teamcenter objects. You can also synchronize thereplica objects to the master objects using the data_sync utility.



The user objects are assigned a home or working site attribute that allows you to usethem in global workflows. This allows Teamcenter to deliver a task to the correctuser at the correct working site.

A user object is also assigned an attribute that controls the remote sites that a usercan interactively log on to. Users can always log on to their home site.

As with other replicated objects, master Organization objects cannot be deleted untilthe export record for the replica objects is deleted. Master objects can be modified atthe owning site. At the replica site, you can modify the following information:

• Replica user objects:

o Last logon time can be reset using the Reset button.

o Default volume can be updated.

o Default local volume can be updated.

• Replica group objects:

o Default volume can be updated.

o Default local volume can be updated.

When you select an object from the Organization List tree, each object has differentoptions that allow more flexibility than if you select them from Organization tree.• User objects

When you select a user object for remote export, you can select from the followingoptions:

o All roles in the Default GroupIf this option is not selected, only the default role is exported. Otherwise,all roles for this group are exported.

o All roles in all groupsIf this option is selected, all group member roles associated with the userare exported.

The group and role for the GroupMember object must already exist at thetarget site prior to exporting the user; otherwise, the export fails.

• Group objects

When you select a group object for remote export, you can select from thefollowing options:

o All roles in Default GroupIf this option is not selected, only the default role is exported. Otherwise,all roles for this group are exported.

o All subgroupsIf this option is not selected, no subgroups are exported. Otherwise, allsubgroups are exported. Parent groups are always exported.



o All group members

If this option is not selected, no group members are exported. Otherwise, allgroup members of all roles selected for export are exported.

• Role objects

• Person objects

When you select a person object for remote export, there are no special optionsfrom which to choose.

Export Organization objects

1. Select an Organization object, for example, a role.

Note You can only export the following Organization objects: roles, groups,persons, and users.

2. Choose Tools→Export→Remote.

Teamcenter displays the Remote Export dialog box.

Note The Remote Export dialog box can vary depending on the object youselect for export and whether you select it from either the Organizationtree or the Organization List tree.

Caution To support export of Teamcenter objects among multiple sites, siteIDs must agree. Consider two sites: site A and site B. To exportobjects to one another, each site must be defined at both sites usingexactly the same site ID in each definition. This is especiallyimportant if you are using Multi-Site Collaboration.

For more information, see the Multi-Site Collaboration Guide.

3. Type the reason for the remote export in the Reason box.



4. Select the target remote sites by clicking next to the Target Sites box.

The system displays the Remote Site Selection dialog box.

5. Select the sites to add from the Available Sites list.

You can move items between the Available Sites and Selected Sites lists bydouble-clicking a site or selecting a site and clicking the plus ( ) or minus ( )buttons. After you select all the sites to be added, click OK.

6. To review the item to be exported, click More.

7. To export the item, click Yes.

Understanding the Teamcenter Rapid Start organizationTeamcenter Rapid Start provides an organizational structure of functional groupsand roles that correspond to the structure of a typical mid-sized organization. Youmust add users to the appropriate roles before they can access data in TeamcenterRapid Start. For more information, see What is a user?.

Note Teamcenter Rapid Start preconfigurations, such as Workflow andpermissions, are created based on the provided organization structure.Adding new groups and roles outside of the RapidStart group causes themto work incorrectly. Siemens PLM Software recommends that you create newgroups as children of RapidStart.

Group Description

RapidStart Root group of your Teamcenter Rapid Startorganization.

Engineering The primary focus of this group is generatingCAD data. Roles within this group includeAuthor, Checker, and Manager.

Management The primary focus of this group is reviewing andapproving data generated by the Engineeringgroup. Manager is the sole role in this group.

Manufacturing Roles within this group include Author,Checker, and Manager.

dba Default administration group.

A Teamcenter administrator, also referred to asdatabase administrator (DBA) or user with DBAprivileges, is any member of a special systemadministration group and is the primary personresponsible for maintaining the Teamcentersoftware, data volumes, and user accounts.



Group Descriptionsystem Special system group used to perform specialized

tasks in an overall system administrationstrategy. Currently, members of the systemgroup are primarily responsible for archiving andrestoring objects. Although any Teamcenter usercan mark an object for archive or restore, onlymembers of the system group can perform theactual object archive and restore operations.

Although a user can belong to both the systemgroup and a system administration group,members of the system group do not inherentlyhave the privileges required to perform allTeamcenter administrative tasks.

Warning Do not delete the system group fromthe database. Teamcenter does notfunction properly without this group.

ShopFloor The primary focus of this group is to provideaccess to the Shop Floor Viewer user interface toshop floor users. Consumer is the sole role inthis group. All users defined in this group haveaccess to the Shop Floor Viewer.

Project Administration The focus of this group is to create and manageproject schedules. Project Administrator isthe sole role in this group.



The following table describes the roles in the Teamcenter Rapid Start organization.

Role Description

Author This role is filled by users whose primary focusis creating and editing CAD data. This includescreating and vaulting data, initiating workflowprocesses, and basic product configuration.

Note If you have a Professional license ofTeamcenter Rapid Start, select this rolewhen creating a user.

Checker This role is filled by users whose primaryfocus is verifying in-process data. Users inthis role query for, view and print PDM data,participate in workflow processes and viewproduct structures.

Consumer This role is filled by users whose primary focusis viewing, approving, rejecting, or commentingon product and process information.

Manager This role is filled by users who need to create andedit technical data, but whose prime interface isnot a CAD application. Typical users in this roleare design managers, manufacturing engineers,and purchasing managers.

Publisher This role is filled by users who publish datato other Teamcenter Rapid Start sites usingMulti-Site Collaboration.

Project Administrator Teamcenter user with privileges to administerprojects using Project. A project administratorcreates, modifies, and deletes project informationand team members.

DBA Special role within Teamcenter Rapid Start thatprovides the privileges necessary to performadministrative tasks.


Chapter

2 Defining sites

What is a site? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

Create a site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

Modify a site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3

Delete a site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3


Chapter

2 Defining sites

What is a site?A site describes an individual installation of Teamcenter and comprises a singledatabase, all users accessing that database, and any additional non-Teamcenterresources such as hardware, networking capabilities, and third-party softwareapplications (tools) required to implement Teamcenter at the site.

Site definitions are comprised of an ID and name. Both the site name and ID mustbe unique. When Teamcenter objects are exported, the site ID is used internally byeach Teamcenter site to identify itself to other sites. The site name is also usedinternally and is stored in the database as a user-defined character string. To sharedata among sites, each Teamcenter database must store a definition of all of thesites in your enterprise.

Site names are generated automatically at the time of installation but should bemodified so that they are descriptive of the function or location of the site. Forexample, if the site is in Albany and all users working at that site share the samedatabase, Albany may be a suitable name for the site. But if this site is known as theABC Design Center, a name such as the ABC Design Center may be better.

Every site must have its own unique name and ID. The site ID is generatedautomatically when the database is installed.

Caution Never change the site ID of a database after it is established. The siteID is used to generate internal identifiers for Teamcenter objects thatmust be unique throughout your enterprise. Never reuse a site ID whencreating a new database. For this reason, never use the database’s importand export functions to replicate a database; always use Teamcenterimport and export capabilities.

As a user with DBA privileges, you use the Organization application to create,modify, and delete site definitions.

Create a site

1. Select the top-level Sites node from the Organization List tree.

The Sites pane appears.

2. Type a descriptive name for the site in the Site Name box.


Chapter 2 Defining sites

Caution To support export of Teamcenter objects among multiple sites, siteIDs must agree. Consider two sites: site A and site B. To exportobjects to one another, each site must be defined at both sites usingexactly the same site ID in each definition. This is especiallyimportant if you are using Multi-Site Collaboration.

For more information, see the Multi-Site Collaboration Guide.

3. Type a unique site ID in the Site ID box. The unique site ID must be an integer.

4. (Optional) Type the site node identifier in the Site Node/URL box. If you areusing Multi-Site Collaboration, and this site is configured to provide objectdirectory services (ODS), select the Provide Object Directory Services checkbox. Otherwise, select the Is A Hub check box.

5. (Optional) Type the service-oriented architecture (SOA) URL in the SOAURL box. This URL is used for SOA calls to this site. The URL is used forHTTP-based Multi-Site Collaboration.

6. (Optional) Type the Teamcenter Global Services URL in the Tc GS URL box.This is the Global Services endpoint for use in global Multi-Site Collaboration.

For more information, see the Data Exchange Guide.

7. (Optional) Type the geographical location of the site in the Geography box.Appropriate values are two-character codes from ISO 3166. This information isused for authorized data access.

The following fields are related to the geographical location of the site:

• If this is an object directory services (ODS) site, select the Provide ObjectDirectory Services check box. The ODS site maintains a record of eachobject in an entire Multi-Site Collaboration network.

• If this site is a hub, select the Is A Hub check box.

• If this site is enabled for Multi-Site Collaboration, select the HTTP EnabledMultisite check box.

• If this site uses TC XML payload instead of an object manager, select theUses TC XML Payload check box.

• If this site has no network connection to the local site, select the Is Offlinecheck box.

• For Teamcenter sites, the site ID must be the site ID of the site.

Sites that manage product data in a file system outside of Teamcenter areconsidered unmanaged sites. You must allocate a unique number for anunmanaged site.

If this site is unmanaged, select the Is Unmanaged check box.

Note This checkbox is enabled only when the Is Offline check box isselected.


Defining sites

• Select Allow deletion of replicated master objects to this site to allowreplicated master objects to this site.

8. Click Create.

The site is saved and displays in the Organization List tree.

Modify a siteCaution Never change the site ID of a database after it is established. The site

ID is used to generate internal identifiers for Teamcenter objects thatmust be unique throughout your enterprise. Never reuse a site ID whencreating a new database.

1. Select the node of the site definition to modify from the Organization List tree.

The Sites pane displays the properties of the site definition.

2. Modify the Site Name box.

Warning Ensure that the proper site ID is entered. Failure to do so maycompromise data integrity.

If you are using Multi-Site Collaboration and this site is configured to provideobject directory services (ODS), perform step 3. Otherwise, go to step 4.

3. Select Provide Object Directory Services.

4. Optionally, modify the Site Node/URL box.

5. Optionally, select Is A Hub.

6. Click Modify.

The system saves the changes to the site definition.

Delete a site1. Select the node of the site definition to delete from the Organization List tree.

The Sites pane displays the properties of the site definition.

2. Verify that the correct site is selected.

3. Click Delete.

The Delete Confirmation dialog box appears.

4. Click Yes to delete the site.

The Sites pane clears and the site is deleted from the database.


Chapter

3 Defining volumes

What is a volume? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

Create a volume . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

Modify volume location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3

Modify volume properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4

Delete a volume . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5

Controlling volume access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5Grant volume access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6Revoke volume access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7

Reallocating volume data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7Using the move_volume_files utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8Managing volume failover behavior . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8


Chapter

3 Defining volumes

What is a volume?A volume is a location where files are stored. A volume equates to a directory onthe operating system. Files stored in volumes are created by CAD applications orother third-party applications.

• Teamcenter retains the volume location (directory) and the file name.

• Users should always access files in volumes through Teamcenter.

Volumes are assigned to groups and users and define file locations for yourorganization structure. As a user with DBA privileges, you use the Organizationapplication to:

• Create and delete volumes.

• Modify volume location and properties.

• Control volume access.

Create a volumeNote Because of limitations and restrictions in NTFS file systems, Siemens PLM

Software recommends creating the volume on the machine where the diskphysically resides. It is important to choose a location that is constantlyaccessible to all users.


Chapter 3 Defining volumes

1. Select the top-level Volumes node from the Organization List tree.Teamcenter displays the Volumes pane.

2. Type a unique descriptive character string in the Volume Name box.

3. Type the name of the network node that physically contains the new volumein the Node Name box.

4. Select the machine type on which the volume will reside: Unix orWindows.

5. Depending on the machine type, type the full UNIX or Windows path of the newvolume in either the UNIX Path Name box or theWindows Path Name box.

6. Select the ID type (FSC, Filestore Group, Load Balancer) to indicate theelement in the FMS master configuration to which the new volume element is tobe added and type the ID in the ID box.The value you enter into the ID box varies depending upon where the newvolume is to be added in the FMS master configuration. That location in theconfiguration is determined by the ID type selection.

Following are examples of each ID type:

• FSC:<fscGroup id=”fscGroup1”

<fsc id=”fsc1” address=”http://csun17.ugs.com:4444”><volume id=”vol1” root=”/data/vol1”/>

</fsc><fsc id=”fsc2” address=”http://csun18.ugs.com:4444”>

<volume id=”vol2” root=”/data/vol2”/></fsc><clientmap subnet=”146.0.0.1” mask=”255.0.0.0”>

<assignedfsc fscid=”fsc1”/></clientmap>

</fscGroup>

To add a volume served by the fsc1 FSC, click the ID button for FSC andthen type fsc1 in the ID box.

• Filestore Group:<fscGroup id=”fscGroup1”

<filestoregroup id=”fsgroup1”><volume id=”vol1” root=”/data/vol1”/><volume id=”vol2” root=”/data/vol2”/>

</filestoregroup><filestoregroup id=”fsgroup2”>

<volume id=”vol3” root=”/data/vol3”/></filestoregroup>...

</fscGroup>

In this case, to add a volume to the second filestore group, click the ID buttonfor Filestore Group and type fsgroup2 in the ID box.

• Load Balancer:<fscGroup id=”fscGroup1”

<loadbalancer id=”loadBal1” address=”http://lb1.ugs.com:4454”>


Defining volumes

<volume id=”vol1” root=”/data/vol1”/></loadbalancer>...

</fscGroup>

In this case, click the ID button for Load Balancer and type loadBal1 inthe ID box.

When the new volume is created, you must specify where in the FMS masterconfiguration the definition of this volume should be placed: the FSC elementsection, the filestore group section, or the load balancer section.

Use the following FMS-related buttons as needed:

• ReloadMakes an FMS configuration the current and active configuration. This isuseful for updating the configuration with any manual changes that aremade.

• ReportDisplays the master and slave FSCs currently configured and the statusof each.

• DisplayDisplays the contents of the FMS master configuration file. It can be usefulfor determining what to add to a volume, for example, an FSC ID or filestoregroup.

7. Grant users or groups access to the volume, as described in Grant volume access.

8. Click Create.

Modify volume locationYou can use Organization to move a volume from one location to another on thesame host. Moving volumes involves copying the volume and its contents to a newlocation and deleting the old volume.

Note Moving a volume is different than merely modifying the path name attributeof the volume. Simply modifying the path name leaves the volume data inthe original location. Teamcenter looks for the data in the new path namelocation and cannot find it, rendering the data inaccessible to users.

A situation in which you use Organization to modify the path name attribute is aftermoving a volume to a different host, for example, after using operating system copytools to move a volume from one host to another host within the same enterprise. Inthis situation, after moving the volume, use Organization to modify the path nameattribute of the volume as described in step 6 of the following procedure.

For more information about copying a volume from one host to another host, see theSystem Administration Guide.



Warning To ensure data integrity, volumes must be moved only when there areno users logged on to Teamcenter.

1. Ensure that all users are logged off Teamcenter.

2. Select the volume to be moved from the Volumes list in the Organization Listtree.

3. Type the path name of the new volume location in the Path Name box.

4. Type the ID in the ID box because this value is not persisted in the database.

5. Click Modify.Teamcenter displays the Move Volume dialog box, prompting you to confirmwhether you want to move the selected volume.

Note Moving a volume can take an extended period of time. The exact timerequired depends on system, network bandwidth, and the amount ofdata being moved.

6. Perform one of the following steps:

• Click Yes to move the volume.The selected volume and all existing data within the volume are movedto the new location.

• Click No to change the volume location without moving the volume data.Teamcenter displays the Modify volume dialog box, informing you that thedata will be lost due to modification and prompting you to confirm whetherto continue.

Note Modifying the volume location does not delete the data. However, the data isinaccessible once the volume location is modified.

Modify volume propertiesWarning To ensure data integrity, modify volume properties only when no users

are logged on to Teamcenter. When modifying the path name, the newpath must be a valid operating system directory. Changing the path toan invalid directory results in loss of data.

1. Ensure that all users are logged off Teamcenter.

2. Select the volume to be modified from the Organization List tree.Teamcenter displays the properties of the volume in the Volumes pane.

3. Modify information in the Volume Name, Node Name, Machine Type or PathName boxes.

4. Click Modify.


Defining volumes

The system saves the changes to the volume definition.

Delete a volumeThe following are important restrictions you should note when deleting a volume.

• An existing volume can be deleted only if there are no database references tothe volume.

• A volume to be deleted must not be designated as the default volume of anygroup or user.

• Users must not have access to the volume. If objects were created that placedfiles in the volume, the objects must be deleted or moved to a different volumeusing a customized ITK program.

1. Select the volume to be deleted from the Organization List tree. Teamcenterdisplays the properties of the selected volume definition in the Volumes pane.

2. Verify that the correct volume has been selected.

3. Click Delete.The Delete Confirmation dialog box appears.

4. Click Yes to delete the volume.

The volume is deleted from the database.

Controlling volume accessUsers inherently have read access to newly created volumes. However, you mustexplicitly grant write access to the volume. To grant access, you must be logged onto the operating system as the root user and logged on to Teamcenter as a memberof the dba group.

When you grant users access to volumes, the system generates a subdirectoryidentified by the user’s name and ownership of the subdirectory is assigned to theuser.

When you grant access to a group, the system generates a subdirectory identifiedby the group name. The system does not generate subdirectories for subgroups,regardless of whether access inheritance is enabled. Subgroups share the directoryof the original group.

Granting volume access to a group does not implicitly grant access to all subgroupsunless specified by the TC_allow_inherited_group_volume_access preference.The default value of this preference is 0, indicating that subgroups do not inheritwrite access to the volume by default. Change the preference value to any non-zeronumber to allow inherited access.

Note Inherited access applies to all volumes including default local volumes, alsoknown as store and forward volumes.



For more information about setting preferences, see the Rich Client Interface Guide.

Note Access modes are granted accordingly: groups access mode = 777, usersaccess mode = 755.

Grant volume access

1. In the Organization List tree, select the volume to which you want to grantaccess.

Teamcenter displays the properties of the volume definition, including the list ofusers and groups with access to the volume, in the Volumes pane.

2. Click Grant.The system displays the Organization Selection dialog box.

Use any of the following buttons in the search pane:

• Search by group

• Search by role

• Search by user

• Reload the Organization tree

The search works in an identical way for each mode. To perform a search, typethe search text into the box and click the appropriate button. Note that the


Defining volumes

wildcard (*) character is accepted. The Organization tree is reloaded with theresults of your search. If there are no matches, a message informing you of this.

3. Select the groups, subgroups, and users to be granted access to the volume.

Note Multiple accessors can be selected by holding the control key and clickingthe group, subgroup, and user in the tree.

4. Click OK to grant access to the selected groups, subgroups, and users.

Teamcenter closes the Organization Selection dialog box and the new accessorsare displayed in the Accessors list of the Volumes pane.

Revoke volume access

1. Select the volume from which you want to revoke access.

Teamcenter displays the properties of the volume definition, including the list ofusers and groups with access to the volume in the Volumes pane.

2. From the Accessors list, select the group or user from whom volume accessis to be revoked.

Note When an accessor is selected, the Revoke button is active.

3. Click Revoke.

The group or user is removed from the Accessors list and can no longer write datato the volume.

Reallocating volume dataAs an administrator, you can reallocate volume data by defining volume storagecriteria based on business data using volume reallocation rules. These rulesare defined in an XML file and managed with the -rulesfile and -outrulesfilearguments of the move_volume_files utility.

For example, consider a site using both CAD and JT files. Because JT files arevolatile and can be recovered from the CAD file if lost, they are on a different backupschedule. The administrator wants all JT files stored in a different volume than theCAD files. Rules can be written in the XML file specifying different target volumesfor the JT and CAD files. Each time the utility is run, JT and CAD files not alreadystored in the respective target volume are moved to the appropriate destination. Youcan run the utility manually or as a cron job.

Note The volume reallocation rules do not affect any existing default volumesettings or default local volume settings.

For more information on reallocating volume data, see the System AdministrationGuide.



Using the move_volume_files utility

Themove_volume_files utility moves files from one volume to another by copyingthe files from source volume to destination volume, commits the database changes,and rolls back the copied files from the source volume. You can list the files that arecandidates to be moved, move the files based on the following:

• Last access data

• File size

• User-supplied input file list

• Volume selection rules and criteria supplied by an XML file.


Managing volume failover behavior

You can manage volume failover behavior by using the following preferences:

• TC_Volume_Failover_Trigger

Indicates the percentage full of a volume at which the file import is sent to thefailover volume.

• TC_Volume_Failover_Volume_Name

Indicates the volume to use in a failover situation. Use this preference with theTC_Volume_Failover_Trigger preference.

• TC_Volume_Status_Resync_Interval

Indicates the minimum amount of time that can pass before the percent fullvalue of a volume is retrieved from File Management System.

For more information on these preferences, see the Preferences and EnvironmentVariables Reference.

For more information on managing volume failover, see the System AdministrationGuide.


Chapter

4 Defining roles

What is a role? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

Create a role . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2

Modify a role . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2

Delete a role . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2

Add an existing role to a group using the Organization Role wizard . . . . . . . . . 4-3

Add a new role to a group using the Organization Role wizard . . . . . . . . . . . . 4-4

Assign a default role within a group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4


Chapter

4 Defining roles

What is a role?A role is an object that models the type of work a user is expected to perform ina group.

• A role can be assigned to multiple groups.

• Roles add another layer of data access control.

• Roles are created along functional lines.

Tip Use real-world descriptions, skills, and/or responsibilities.

Roles refine the group definitions of your organization structure. As a user withDBA privileges, you use the Organization application to:

• Create, modify, and delete role definitions.

• Add existing roles to the Organization tree.

• Add new roles to the Organization tree.

• Assign a default rule within a group.

Example

Robert Green is an Engineering Manager. In addition to his responsibilities asEngineering Manager, Robert must also perform standards work. Therefore, userrgreen has been assigned two roles in the high_performance group: EngineeringManager and Standards Engineer.


Chapter 4 Defining roles

Create a roleYou create roles to reflect the skills and responsibilities of the users in yourorganization. Roles can be created using the Organization List method describedor you can create and add a role to the Organization tree using the OrganizationRole wizard.

1. Select the top-level Roles node from the Organization List tree.

The Roles pane appears.

2. Type the following information:

• A new role in the Role box.

• Optionally, a descriptive character string in the Description box.

3. Click Create.

The new role is saved in the database and displayed in the Organization List tree.

For more information about adding the role to the Organization tree, see Add anexisting role to a group using the Organization Role wizard.

Modify a role1. Perform one of the following substeps:

• Select a role definition from the Organization List tree.

• Select a role definition from the Organization tree.

The Roles pane appears.

2. Modify any information contained in the Roles pane boxes by typing overexisting information.

NoteFor more information about the Localization button associated withthe Role box, see the Localization Guide.

3. Click Modify.

The modified role definition is saved in the database.

Delete a roleAs your organization evolves, you may want to permanently remove a role fromthe database. Roles can only be deleted by accessing the Roles pane from theOrganization List tree.


Defining roles

Caution Do not delete any default roles, for example, the Project Administratorrole. Doing so can cause issues with the rule tree or other processingthat depends on them. Siemens PLM Software recommends you leaveall default roles in place, even if you are not using the functionalityrelated to these roles.

Note You cannot delete a role that is referenced by another organization object.

1. Select the role node to be deleted from the Organization List tree.The Roles pane appears.

2. Verify that the correct role is selected.

3. Click Delete.The Delete Confirmation dialog box appears.

4. Click Yes to delete the role.

The Roles pane clears and the role is deleted from the database.

Add an existing role to a group using the Organization Role wizardThe Organization Role wizard can add an existing role to a group or subgroupin the Organization tree. Existing roles can also be added to existing groups inthe Organization tree. The procedure for using the Organization Role wizard toadd an existing role is the same, regardless of the activity being performed whenthe wizard is invoked.

1. Select the group node in the Organization tree to which you want to add the role.The Groups pane appears.

2. Click Add Role.The Organization Role wizard appears.

3. Select Add existing role to the group and click Next.Note The first role added to a group becomes the default role for that group.

4. Select the roles to be added to the group from the Existing Roles list. Youcan move items between the Existing Roles and Selected Roles lists bydouble-clicking a role or selecting a role and clicking the plus ( ) or minus ( )buttons. When you select all the roles to add, click Finish to continue or Closeto dismiss the wizard.

5. If you clicked Finish, perform one of the following actions:

• Select a What is next? option from the wizard. You can add another role tothe selected group or add a user to the role you just added.

For more information, see Add an existing user to a role/group using theOrganization User wizard or Add a new user to a group/role using theOrganization User wizard.


Chapter 4 Defining roles

• Click Home to return to step 1 of the Organization Role wizard.

• Click Close to dismiss the wizard.

The role is added to the Organization tree.

Add a new role to a group using the Organization Role wizardYou can use the Organization Role wizard to add a new role to a group during theprocess of creating the group or subgroup in the Organization tree.New roles can also be added to existing groups or subgroups in the Organizationtree. The procedure for using the Organization Role wizard to add a new role is thesame, regardless of the activity being performed when the wizard is invoked.

1. Select the group node in the Organization tree to which you want to add the role.The Groups pane appears.

2. Click Add Role.The Organization Role wizard appears.

3. Select Add new role to the group and click Next.Note The first role added to a group becomes the default role for that group.

4. Type the following information and click Close to create the new role or clickFinish to perform another action:

• A new role in the Role box.

• Optionally, a descriptive character string in the Description box.


• Select a What is next? option from the wizard. You can add another role tothe selected group or add a user to the role you just added.

For more information, see Add an existing user to a role/group using theOrganization User wizard or Add a new user to a group/role using theOrganization User wizard.

• Click Home to return to step 1 of the Organization Role wizard.


The role appears in the Organization and Organization List trees.

Assign a default role within a group1. In the Organization tree, expand the group and role structure corresponding to

the role that you want to set as the default.

Teamcenter displays the users assigned to this role.


Defining roles

2. Select the user node.

Teamcenter displays the user information.

3. In the Group Member Settings section, select the Default Role check box.

4. Click Modify.


Chapter

5 Defining groups

What is a group? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

What is a subgroup? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2

Creating a group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2Create a group or subgroup using the Organization List tree . . . . . . . . . . 5-3Create a parent group within the Organization tree . . . . . . . . . . . . . . . . . 5-6

Modify a group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7

Delete a group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7

Group terms and concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8

Group hierarchies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9

Moving groups within the hierarchy and volume access . . . . . . . . . . . . . . . . . 5-10

Managing group members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10Remove a member from a group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10Activate a group member . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11Deactivate a group member . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11Suppress the display of inactive group members in the Organization tree

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11

Add existing group as subgroup using the Organization Group wizard . . . . . . . 5-12

Add new subgroups using the Organization Group wizard . . . . . . . . . . . . . . . 5-14


Chapter

5 Defining groups

What is a group?A group represents a project in Teamcenter. Groups contain members (users) whotake on a role or multiple roles in the group. Groups represent data ownershipand therefore control data access. Two groups are provided with Teamcenter: dbaand system.

Warning Do not delete the system group provided with Teamcenter. It is requiredfor the product to function properly.

• Groups are defined along project lines, not functional lines, but can definethird-party organizations such as suppliers.

• A group member can be a member of many groups. For example, Robert Greencan belong to the high_performance and standards groups.

Groups make up the core of your organization structure. As a user with DBAprivileges, you use the Organization application to:

• Create, modify, and delete groups.

• Manage subgroups within the Organization tree.

• Assign default volumes to a group.

• Assign authorized data access privileges to a group.

Example


Chapter 5 Defining groups

What is a subgroup?A subgroup is a group with another group designated as its parent. A subgroup canalso be designated as a parent group itself. The position of subgroups within theOrganization hierarchy can be managed by parenting and reparenting groups.

• Subgroups are an excellent way to organize your users.

• Subgroups inherit access permissions, volumes, and preferences from theirparent.

Example

Creating a groupAs a user with DBA privileges, you create project-oriented groups to organizeclusters of users.

This topic discusses the procedures for creating:

• Parent groups and subgroups using the Organization List tree.This method presents all the group properties including a parent group propertyfor creating subgroups.

• Parent groups in the Organization tree.This method presents fewer group properties, but uses wizards instead to addthings like subgroups and roles.

Groups have several settings to configure access to data owned by the group.

• The internal/external Security setting allows or restricts access to data. Forexample, members of external groups can only access data in their group.

For more information about internal/external group access, see the SecurityAdministration Guide.

• The DBA Privilege setting, when selected, allows system administrationprivileges to members of the group.

• The authorized data access (ADA) and International Traffic in Arms Regulations(ITAR) setting allows or restricts access to data based on clearance levels anddata classification.


Defining groups

For information about configuring and administering authorized data, see theSecurity Administration Guide.

For more information regarding the creation and addition of subgroups in theOrganization tree, see Add new subgroups using the Organization Group wizard orAdd existing group as subgroup using the Organization Group wizard.

Create a group or subgroup using the Organization List tree

1. Select the top-level Groups node from the Organization List tree.

The Groups pane appears.

2. Type a group name in the Name box.

Note A group is identified uniquely by the combination of its name and itsparent. Two groups with different parents may have the same name,but two groups with the same parent may not have the same name.Additionally, subgroups may not have the same name as a parent group.

3. (Optional) Type a description in the Description box.

4. Choose whether the group is subject to Internal or External project-level securityrules. You can also leave the Security box blank, in which case project-levelsecurity rules are not applied.

For more information about group rules for project-level security, see the Projectand Program Guide.

5. If the new group is to be a subgroup (a child of an existing group), click ToParent to display the List of Defined Groups list and select, by double-clicking,a parent group from the list. If the new group is to be a parent group, leavethe Parent Group box blank.

Note When creating a subgroup in a group, the default volume is not assigned.Therefore, if the TC_allow_inherited_group_volume_accesspreference is not set to 1, manually set the volume for the subgroupafter creating the subgroup.

Inherited access applies to all volumes including default local volumes,also known as store and forward volumes.

6. If the group is to have system administration privileges, select the DBA Privilegecheck box. If not, leave the box blank.

7. Click Default Volume to display the List of Defined Volumes list and select, bydouble-clicking, a default volume for the group.

Caution If you create a group without assigning a default volume, groupmembers cannot save datasets. Therefore, Siemens PLM Softwarerecommends that you assign a default volume for the group.

8. Click Default Local Volume to display the List of Defined Volumes and select, bydouble-clicking, a default local volume for the group.



Use this temporary storage to upload a file into FMS volume storage.This temporary local volume allows the file to be stored locally before it isautomatically transferred to the final destination in the background. Once thefile is stored in the default local volume, the user can continue working withouthaving to wait for the upload to take place.

Note The Default Local Volume value must be different from the value in theDefault Volume box.

9. To add roles, click the Roles tab. Add one or more roles to the group by selectinga role from the List of Defined Roles list and either double-clicking it or clickingthe plus button to move it to the List of Selected Roles list. You can removeitems from the List of Selected Roles list by double-clicking a role or selecting arole and clicking the minus button .

Note The first role added to the group becomes the default role for that group.

10. To assign authorized data access (ADA) and International Traffic in ArmsRegulations (ITAR) attributes to a group, click the ADA/ITAR Attributes tab.Enter information in the following boxes in the ADA/ITAR Attributes area:• Organization Name

Specifies the name of the organization. An organization in the authorizeddata access context is a Teamcenter group that models a legal corporationor company whose members can be granted access to classified data.Organization Legal Name and Organization Alternate Name areamong the attributes an organization has that are derived from ISO 6253standards.

This box requires a value.

Note Organizations are a subclass of the group class and as such aresubject to hierarchical group behavior. Therefore, suborganizationsinherit the properties of the parent organization. Siemens PLMSoftware recommends that users be made members of the mostspecific organization possible to ensure the accuracy of keyattributes, such as the nationality of the organization.

• Organization Legal NameSpecifies the name designated by the organization as its official name ofrecord. This box is optional.

• Organization Alternate NameSpecifies a name that sufficiently verifies the identity of the organization.This can consist of truncation of the record name or it can be a tradename, initials, or acronyms by which the organization is known. This boxis optional.

• Organization AddressSpecifies the address of the organization. This box is optional.

• Organization URL


Defining groups

Specifies the URL of the organization. This box is optional.

• Operational StatusIndicates whether the organization is active, inactive, or obsolete. This boxis optional.

Note Although you can use this value to write Access Manager rules torestrict users belonging to inactive groups from accessing classifieddata, there are no COTS rules that use this property.

Following are the valid values for this box:

0 Indicates the organization group is active.

1 Indicates the organization group is temporarily inactive.

2 Indicates the organization group is permanently inactive.

The default value is 0 (active).

• Organization IDSpecifies a unique organization identifier. This box must contain a value.

• Organization TypeSpecifies the numbering scheme associated with the organization identifier.This box must contain a value.

• NationalitySpecifies the nationality of the organization. This box is optional.

Appropriate values are two-character codes from ISO 3166. If not specified,the organization is assumed to be at the same location as the database.

• CitizenshipSpecifies the citizenships of the user. The user can have multiplecitizenships. This box is optional.

To add a citizenship to the Citizenship list, click the Edit button to setthis box in edit mode. Enter the two-letter country code in the text box and

click the plus button .

To sort the list of multiple citizenships alphabetically, use the Sort button .

To remove citizenship entries from the Citizenship list, select a citizenshipin the Citizenship list and click the minus button .

Note o Citizenship is a two-letter country code from ISO 3166, forexample, US (United States) and GB (Great Britain).

o If a country code LOV is attached to the fnd()citizenshipsproperty of the User business object, a combination box isdisplayed to allow the selection of a citizenship from the countrycode list.



For information about configuring and administering authorized data access forintellectual property (IP) and ITAR, see the Security Administration Guide.

11. Click Create.

The group is saved in the database and displayed in the Organization andOrganization List trees.

Create a parent group within the Organization tree

1. Select the root (Organization) node of the Organization tree.


2. Type a unique group name in the Name box.


4. Choose whether the group is subject to Internal or External project-level securityrules. You can also leave the Security box blank, in which case project-levelsecurity rules are not applied.

For more information about group rules for project-level security, see the Projectand Program Guide.

5. If the group is to have system administration privileges, select the DBA Privilegecheck box. If not, leave the box blank.

6. Click Default Volume to display the List of Defined Volumes list and select, bydouble-clicking, a default volume for the group.

Caution If you create a group without assigning a default volume, groupmembers cannot save datasets. Therefore, Siemens PLM Softwarerecommends that you assign a default volume for the group.

7. Click Default Local Volume to display the List of Defined Volumes and select, bydouble-clicking, a default local volume for the group.

Use this temporary storage to upload a file into FMS volume storage.This temporary local volume allows the file to be stored locally before it isautomatically transferred to the final destination in the background. Once thefile is stored in the default local volume, the user can continue working withouthaving to wait for the upload to take place.

Note The Default Local Volume value must be different from the value in theDefault Volume box.

8. Click Create Group.

The parent group is saved in the database and displayed in the Organization andOrganization List trees.


Defining groups

Modify a groupYou can modify group definitions using the Organization List tree or theOrganization tree.1. Perform one of the following steps:

• Select the group to be modified from the Organization List tree.

• Select the group to be modified from the Organization tree.

The Groups pane displays the group definition.Caution Changing existing group names or structure (for example,

reparenting a group) can drastically impact Workflow functionality.Workflow processes do not complete if the group names are changedafter the process is started. Therefore, all Workflow processes,including Cascade Release (CR) and Change Management (CM)processes, must be modified before they are started to reflect anychanges in group names or structure, or they fail. Additionally, allcurrent (started) EPM jobs affected by group name or structurechanges must be terminated and new jobs must be started fromupdated procedure templates.

Because the group name is used in the directory structure to storeand locate information, changing the group name does not changethe path to existing datasets.

2. Modify any information in the Groups pane by either typing over the existinginformation or selecting a different option from the defined lists.

Note • To select a different option from a defined list, you must first clickClear in the list dialog box and then select another item from the listby double-clicking.

• For more information about the Localization button associatedwith the Name box, see the Localization Guide.

3. Click Modify.

The system saves the changes to the group definition.

Delete a groupWarning Do not delete the system group from the database under any

circumstances. Teamcenter does not function properly without thisgroup.

Caution Do not delete any default groups, for example, the ProjectAdministration group. Doing so can cause issues with the rule treeor other processing that depends on them. Siemens PLM Softwarerecommends you leave all default groups in place, even if you are notusing the functionality related to these groups.



Note You cannot delete group definitions that are referenced by anotherOrganization object. You must first delete users and roles referenced bythe group.

1. Select a group from the Groups list.


2. Verify that the correct group is selected.

3. Click Delete.


4. If the correct group appears, click Yes.

The Groups pane clears and the group is deleted from the database.

Group terms and concepts

Term/Concept Description

Groups and subgroups Groups and subgroups are project-oriented clusters ofusers. Each group has exactly one parent group (unlessit is at the top, or root, of the hierarchy, when it hasno parent) and may have one or more child groups(subgroups).

Default group When a user belongs to more than one group, one ofthem is designated as the default group. A default groupmust be designated for each user so that Teamcentercan store project files in a central location (for example,in the group volume).

The user’s default group is used at logon unless anothergroup is specified.

When Teamcenter Security Services is installed and theTC_SSO_SERVICE environment variable is set in thetc_profilevars file, logon uses the default Teamcentergroup.

Parent group A parent group is used to organize a configuration ofrelated subgroups.

System administrationgroup

A Teamcenter administrator, also referred to as databaseadministrator (DBA) or user with DBA privileges, is anymember of a special system administration group andis the primary person responsible for maintaining theTeamcenter software, data volumes, and user accounts.Teamcenter creates one system administration group(dba) during installation. You can create others asneeded.


Defining groups

Term/Concept Descriptionsystem group Teamcenter provides a special system group that is used

for performing specialized tasks in an overall systemadministration strategy. Currently, members of thesystem group are primarily responsible for archivingand restoring objects. Although any Teamcenter user canmark an object for archive or restore, only members ofthe system group can perform the actual object archiveand restore operations. This restriction also applies tomembers of a system administration group; they cannotperform archive and restore operations either.

Warning Do not delete the system group fromthe database under any circumstances.Teamcenter does not function properlywithout this group.

Although a user could belong to both the system groupand a system administration group, members of thesystem group do not inherently have the privilegesrequired to perform all Teamcenter administrative tasks.

Group administrator A group administrator is a group member who can add,modify, or remove group members.

Group administrators must be members of the groupthey are administering and these privileges are onlyvalid within that group.

Group names A group is identified uniquely by the combination of itsname and its parent. Two groups with different parentsmay have the same name, but two groups with the sameparent may not.

To distinguish between different groups with the samename, note the placement of the group within theOrganization tree.

Group hierarchiesGroups are organized into one or more trees or hierarchies. Each group has exactlyone parent group (unless it is at the top or root of the hierarchy, when it has noparent) and can have one or more subgroups.

The following list indicates the functional areas in Teamcenter that use grouphierarchies.

Functional area Group hierarchy use

Access Manager A group can inherit access permissions from itsparent.

Authorization Authorization rules are inherited within thegroup hierarchy.



Functional area Group hierarchy use

Volumes Groups can inherit access to a volume fromparent groups; therefore, you must considervolume access when modifying or movinghierarchical groups.

Preferences Group preferences can be inherited from theparent group.

Mail Mail can be sent to members of a group’ssubgroups, subgroups of subgroups, and so on,as well as to the named group only.

Workflow Signoffs can be assigned to members of a group’ssubgroups and members of the named group.

Moving groups within the hierarchy and volume accessMoving groups within a hierarchy can affect group member access to data dependingon how volumes are assigned.

• Existing files

Restructuring groups makes no difference; the files continue to be availablewithout any change in behavior.

• New files

If the group has its own assigned volume, restructuring makes no difference tovolume access. Files continue to be saved to the assigned volume. However, ifthe group does not have its own volume, but instead inherits access to a volumefrom an ancestor group, there may be a difference after the restructuring. Therestructured group now has a different set of ancestor groups; therefore, it eitherinherits access to a different volume or potentially has no volume access at all.

Managing group membersAs your real-world organization evolves and changes, your Teamcenter virtualorganization also changes. Implementing new projects, promoting personnel, andrestructuring your organization are all examples of real-world events that wouldnecessitate changes involving group members.

Remove a member from a groupNote You cannot remove the last instance of a user from the Organization tree if

the group from which you are removing the user is the user’s default group.

1. Select the user (group member) you want to remove from a group or subgroup inthe Organization tree.Teamcenter displays the user’s information.

2. Click Remove.


Defining groups

The system displays the Remove User Confirmation dialog box.

3. Click Yes to remove the user from the group.

Activate a group member

1. Select the user (group member) you want to activate in a group or subgroup inthe Organization tree.

Teamcenter displays the user’s information.

2. In the Group Member Settings section, choose the Active option.

3. Click Modify.

Deactivate a group member

When a user leaves the organization or changes groups or roles within theorganization, you can deactivate their membership within a group. This preventsthem from logging on to the system as a member of the group and denies them accessto information related to their previous group and role.

Note • Only an administrator or a user designated as a group administrator canchange a group member’s status from active to inactive.

Database objects are owned by individual users; therefore, objectownership does not change when a group member is deactivated.

• You cannot deactivate a group member if they have any pendingWorkflow tasks. You must first delegate these tasks to another groupmember and then deactivate the user. You can use the global_transferutility to transfer one user’s tasks to another user.


You can also reassign the user’s tasks using the My Teamcenter inboxfeature.

For more information, see the My Teamcenter Guide.

1. Select the user (group member) you want to deactivate from a group or subgroupin the Organization tree.

Teamcenter displays the user’s information.

2. In the Group Member Settings section, choose the Inactive option.

3. Click Modify.

Suppress the display of inactive group members in the Organizationtree

1. Expand the group in the Organization tree to display the roles and users withinthe group.



2. Click Suppress Inactive Group Members/Show Inactive Group Members .

Teamcenter filters the display to suppress group members who have beendesignated as inactive within a group or groups.

Note This feature suppresses the display of active and inactive users who aredesignated as inactive group members. However, users can be designatedas inactive but not be designated as inactive group members. In this case,the users are still displayed as group members when the Suppress InactiveGroup Member filter is applied.

You can restore the display of inactive group members in the tree by clicking thebutton again.

Add existing group as subgroup using the Organization Group wizardThere are two ways to add an existing group as a subgroup to the Organization tree.You can assign a parent group to the subgroup definition (for more information,see the Creating a group) or you can use the Organization Group wizard to add anexisting group to a parent group.

1. Select a group or subgroup from the Organization tree. The selected groupserves as the parent group for the subgroup you add.


2. Click Add Sub-Group.

The Organization Group wizard appears.

3. Select Add existing group as sub-group and click Next.

Caution Subgroups can be associated with one parent group. Therefore,selecting a group that is currently associated as a subgroup of anotherparent group breaks that parent-child relationship. Changingexisting group names or structure (for example, reparenting a group)can drastically impact Workflow functionality. Workflow processesdo not complete if the group names are changed after the processis started. Therefore, all Workflow processes, including CascadeRelease (CR) and Change Management (CM) processes, must bemodified to reflect any changes in group names or structure beforethey are started or else they fail. Additionally, all current (started)EPM jobs affected by group name or structure changes must beterminated and new jobs must be started from updated proceduretemplates.

4. Select the subgroups to add from the Available Groups list.


Defining groups

You can also use either of the following buttons in the search pane:

• Find group

• Reload all available groups

To perform a search, type the search text into the box and click the Search byGroup button . Note that the wildcard (*) character is accepted.

You can move items between the Available Groups and Selected Groups lists bydouble-clicking a group or selecting a group and clicking the right arrow ( ) orleft arrow ( ) buttons. After you select all of the subgroups, click Next or Finish.

5. Click Yes to add the selected groups.The Group(s) added dialog box appears.

6. Click OK.The Organization Group wizard displays the next step.

7. Perform one of the following actions:

• Select the What is next? option from the wizard. You can choose to addanother subgroup or add a role to the selected group.

For more information, see Add an existing role to a group using theOrganization Role wizard or Add a new role to a group using theOrganization Role wizard.



• Click Home to return to step 1 of the Organization Group wizard.


The subgroup appears in the Organization tree.

Add new subgroups using the Organization Group wizardYou can create new subgroups and add them to the Organization tree using theOrganization List method (for more information, see Creating a group) or by usingthe Organization Group wizard.

1. Select a group or subgroup from the Organization tree. The selected group servesas the parent group for new subgroup.


2. Click Add Sub-Group.The Organization Group wizard appears.

3. Select Add new group as sub-group and click Next.

4. Complete the following information:

• Type a group name in the Name box.Note A group is identified uniquely by the combination of its name and

its parent. Two groups with different parents may have the samename, but two groups with the same parent may not have the samename. Additionally, subgroups may not have the same name as aparent group.

• (Optional) Type a description of the group in the Description box.

• Choose whether this group is subject to Internal or External project-levelsecurity rules. You can also leave this box blank, in which case project-levelsecurity rules are not applied.

For more information about group rules for project-level security, see theProject and Program Guide.

• (Optional) If the group is to have system administration privileges, select theDBA Privilege check box. If not, leave it blank.

• Click Default Volume to display the List of Defined Volumes list and select,by double-clicking, a default volume for the group.

Caution If you create a group without assigning a default volume,group members cannot save datasets. Therefore, Siemens PLMSoftware recommends that you assign a default volume for thegroup.

• Click Default Local Volume to display the List of Defined Volumes andselect, by double-clicking, a default local volume for the group.


Defining groups

Use this temporary storage to upload a file into FMS volume storage.This temporary local volume allows the file to be stored locally before it isautomatically transferred to the final destination in the background. Oncethe file is stored in the default local volume, the user can continue workingwithout having to wait for the upload to take place.

Note The Default Local Volume value must be different from the value inthe Default Volume box.

5. When you are finished adding the information, click Finish to continue or Closeto dismiss the wizard.


• Select the What is next? option from the wizard. You can choose to addanother subgroup or add a role to the selected group.

For more information, see Add an existing role to a group using theOrganization Role wizard or Add a new role to a group using theOrganization Role wizard.

• Click Home to return to step 1 of the Organization Group wizard.


The new subgroup is saved in the database and displayed in the Organization andOrganization List trees.


Chapter

6 Defining persons

What is a person? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1

Create a person . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1

Modify a person . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2

Delete a person . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3


Chapter

6 Defining persons

What is a person?Persons are individuals who work at your site. A person has properties such asName, Address, and Employee Number.

• Consider creating all persons at your site using the following naming convention:

last-name, first-name, middle-initial

• Person definitions that are referenced by a User object cannot be deleted.

You must define a person for each Teamcenter user. As a user with DBA or groupadministrator privileges, you use the Organization application to:

• Create person definitions.

• Modify person definitions.

• Delete person definitions.

Example

Create a personPerson definitions contain real-world information about individual Teamcenter users.

Person definitions can be created:

• Simultaneously with the user definition when using the Organization Userwizard.

• Manually using the Organization List tree and corresponding pane.


Chapter 6 Defining persons

For more information, see Add a new user to a group/role using the OrganizationUser wizard.

These optional Person properties have resulting behavior:• E-Mail Address is required for workflow notification.

• Locale specifies the user’s locale, for example, en_US indicates English asspoken in the United States.

• Time Zone specifies the user’s time zone, for example, America/Chicagorepresents the Central time zone.

• User Image allows a graphic to be added for the person. You can add a pictureof the person that when a Person object is selected.

Note Often, the real-world information is similar for users residing in the samephysical location. In such cases, you can minimize the amount of data entryrequired by selecting the node of a person definition (from the OrganizationList tree) that possesses similar attributes to the person you want to create.To begin a definition from scratch with a blank Persons pane, select thetop-level Persons node from the Organization List tree.

1. Select a node from the Persons list in the Organization List tree. If you donot see nodes under the Persons list, double-click the top-level Persons nodeto display them.

The Persons pane displays the properties of the person definition.Note The entry in the Name box must be unique. You cannot create two

persons with the same name.

2. Type a unique name in the Name box. All other boxes are optional.

3. Click Create.

The new person definition is saved in the database and displays in the OrganizationList tree.

Modify a personAs the real-world information associated with a Teamcenter user changes, it may benecessary to update the person definition.

1. Select the node of the person definition to be modified from the OrganizationList tree.The Persons pane displays the properties of the person definition.

2. Modify any information contained in the Persons pane boxes by typing over theexisting information.

3. Click Modify.

The modified definition is saved in the database.


Defining persons

Delete a personAs your organization changes, it may become necessary to delete a person definitionfrom the database.

Note Person definitions that are referenced by another organization object cannotbe deleted. You must eliminate the reference before deleting.

1. Select the node of the person definition to be deleted from the Persons list in theOrganization List tree.

The Persons pane displays the properties of the person definition.

2. Click Delete.


3. Verify that the correct person is selected.

4. If the correct person appears, click Yes.

The Persons pane clears, and the person definition is deleted from the database.


Chapter

7 Defining users

What is a user? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1

Create a user . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1

Modify a user . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5

Deleting users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-6

Delete a user . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-6

Specifying password restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-7

Configuring ADA for ITAR support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-7

Changing user status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-8Inactivate a user account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-8Activate a user account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-9

Add an existing user to a role/group using the Organization User wizard . . . . . 7-9

Add a new user to a group/role using the Organization User wizard . . . . . . . . 7-11

Managing internal, external, and remote user constructs . . . . . . . . . . . . . . . . 7-12

Mapping and synchronization considerations . . . . . . . . . . . . . . . . . . . . . . . . 7-13


Chapter

7 Defining users

What is a user?A user is a person with an account known to the Teamcenter system. One person canhave several user accounts in Teamcenter. The Teamcenter implementation of useris completely separate from any operating system user account.

A user is assigned to a default group and takes on a role in the group. As a user withDBA privileges, you use the Organization application to:

• Create, modify, and delete user accounts.

• Maintain user password restrictions.

• Deactivate or activate user accounts.

• Assign group administrator privileges.

• Assign intellectual property and government clearances to data stored inTeamcenter for user accounts, along with defining multiple citizenships.

• Assign a license bundle to a user.

Example

Create a userYou create user accounts to identify each individual who interacts with Teamcenter.


Chapter 7 Defining users

User definitions can be created:

• From a role in the Organization tree using the Organization User wizard.

• Manually using the Organization List tree and corresponding pane.

For more information about creating a user using the Organization User wizard, seeAdd a new user to a group/role using the Organization User wizard.

These optional User properties have resulting behavior:• Password must conform to password restrictions.

Note o If a user is created without specifying a password, Teamcenterassigns the user ID as the password.

o If a user attempts to log into Teamcenter without entering apassword, a login failure occurs.

For more information about password restrictions, see Specifying passwordrestrictions.

• Last Login Time displays the last time this user logged onto Teamcenter.This helps to determine when a user is deactivated according to theTC_days_non_login_timeout preference. The default setting for thispreference is set to 0, allowing users to always log on. When deactivation doesoccur, Reset activates the user.

1. Select the top-level Users node from the Organization List tree.The Users pane appears.


Note • Do not use the delimiters defined in the TC_user_delimiterspreference when entering user information in either the PersonName box or the User ID box. (If the TC_user_delimiterspreference is not set, parentheses ( ) are the default delimiters.)Otherwise, the user name and user ID display incorrectly in theOrganization List tree.

• If you inadvertantly use the characters set in theTC_user_delimiters preference when you create a useror a person, use the make_user utility to correct the user ID andperson name delimiters.

a. Click to the right of the Person Name box to display the List of DefinedPersons list and select, by double-clicking, a person name from the list.

Caution If autologon is used at the site, the operating system user namemust be the same as the Teamcenter user ID and the passwordmust be valid for both accounts or autologon does not work.

b. Type a unique user name in the User ID box.


Defining users

c. Type the user’s OS name in the OS Name box.

Note Teamcenter uses the user’s OS name as a backup e-mail address ifno e-mail address is set in the Person object. This allows the user toreceive notifications and subscriptions.

d. Click Default Group to display the List of Defined Groups list and select agroup from the list by double-clicking.

Default Group specifies the group the user will be placed in the organizationand the default group assigned on logon.

e. Click Default Volume to display the List of Defined Volumes list and select avolume from the list by double-clicking.

Note Siemens PLM Software recommends that you do not define a defaultvolume for each user. If the default volume is not specified, thegroup’s default volume information is used.

f. Click Default Local Volume to display the List of Defined Volumes andselect, by double-clicking, a default local volume for the group.

Use this temporary storage to upload a file into FMS volume storage.This temporary local volume allows the file to be stored locally before it isautomatically transferred to the final destination in the background. Oncethe file is stored in the default local volume, the user can continue workingwithout having to wait for the upload to take place.

Note The Default Local Volume value must be different from the value inthe Default Volume box. Also, either box, the Default Volume box andthe Default Local Volume box, can be set without the other being set.

g. Select User Status, either Active or Inactive. The default setting is Active.

h. You can assign authorized data access (ADA) and International Trafficin Arms Regulations (ITAR) attributes to a user using the boxes in theADA/ITAR Attributes section.

• IP clearance

Specifies the intellectual property (IP) clearance level, which is the levelof access the user has to sensitive (classified) information. This box isoptional.

• Government clearance

Specifies the level of clearance that users have to classified data. Thisbox is optional.

• TTC date

Specifies the technology transfer certification (TTC) date, which is thedate when the user’s qualification for viewing exporting data markedas government classified lapses. Teamcenter revokes the user’s accessrights after the TTC date expires unless renewed. As administrator, youcan manually cancel a user’s TTC date at any time. This box is optional.



• Geography

Specifies the geographical location of the user. Appropriate values aretwo-character codes from ISO 3166. If not specified, the user is assumedto be at the same location as the database. This box is optional.

• Nationality

Specifies the nationality of the user, which you can set using the LOVcontaining two-character codes from ISO 3166. This box is optional.

• Citizenship

Specifies the citizenships of the user. The user can have multiplecitizenships. This box is optional.

To add a citizenship to the Citizenship list, enter a two-letter country

code in the text box and click the plus button . To add additionalcitizenships, click the Edit button to set this box in edit mode, enter

the two-letter country code in the text box, and click the plus button .

To sort the list of multiple citizenships alphabetically, use the Sortbutton .

To remove citizenship entries from the Citizenship list, select acitizenship in the Citizenship list and click the minus button .

Note o Citizenship is a two-letter country code from ISO 3166, forexample, US (United States) and GB (Great Britain).

o If a country code LOV is attached to the fnd()citizenshipsproperty of the User business object, a combination box isdisplayed to allow the selection of a citizenship from thecountry code list.

For information about configuring and administering authorized data accessfor IP and ITAR, see the Security Administration Guide.

For more information of how to maintain associations, geography, andlicenses, see the Authorized Data Access License Guide.

i. Set the licensing level to the appropriate level for the tasks the user performs.

License levels are used to enable usage by time or by features.

For descriptions of the available license levels, see your license agreementdocumentation.

For information about administering Teamcenter licenses, see the SystemAdministration Guide.

j. Select the appropriate license bundle from the License Bundle list. As anadministrator, you can assign a license bundle to a user.

If the selected license bundle has a base license level, the License Level boxis updated with this value and is made non-editable.


Defining users

For more information about license bundles, see the System AdministrationGuide.

k. Select the home site from the Home Site list. This is the site from which theuser is physically present and works.

l. Select which remote sites, if any, the user cannot interactively log into byclicking the Select Sites button to display the Site Selection dialog box.Note Users are always able to log on to their home site.

3. Click Create.

The new user definition is saved in the database.

Note A default role, as defined by the default group, is associated with the userdefinition.

Repeat steps 2 and 3 to create additional users.

Modify a userYou can modify user definitions from within the Organization List tree or theOrganization tree. However, the assignment of group administrator privileges canonly be performed by accessing the Users pane from the Organization tree.1. Perform one of the following substeps:

• Select a user definition from the Organization List tree.

• Select a user definition from the Organization tree.

The Users pane displays the user definition.

2. Modify any information contained in the Users pane by either typing over theexisting information or selecting a different option from the defined lists.

Note Because the Geography, Nationality, and Citizenship information of theselected user is private, only a user with system administrator privilegescan view this information. However, all users can view their own userinformation.

To remove entries in the Citizenship list, select the citizenship in the list to beremoved and click the minus button . To add additional citizenships to the

list, enter the two-letter country code in the text and click the plus buttonor select a country code from the country code list.

Note To select a different option from a defined list, you must first click Clearin the list dialog box and then select an item from the list.

3. Click Modify.

The changes to the user definition are saved in the database.



Deleting usersAs your organization changes, it may become necessary to delete a user from thedatabase. This is important because database objects are owned by users, and adetermination must be made about what to do with any objects owned by the userbefore deleting the user from the database.

Siemens PLM Software recommends that you first deactivate an obsolete useraccount in the database, then delete it when all references to the account have ceased.

Because the names of inactive users do not display in the LOVs throughout the richclient, inactive accounts cannot continue to be referenced by other users. Inactiveuser accounts cannot be logged on to the database, yet account records remain in thedatabase so that an audit trail can continue to reference the data.

Once all references to objects owned by the deactivated account are cleared fromthe database, and an audit trail of the account’s actions is no longer required, theaccount can safely and easily be deleted.

When you are ready to delete a user account, there are two options:

• Delete all objects owned by the user.

• Change ownership of all objects owned by the user. However, you cannot reassignobjects owned by a replicated user.

For more information about changing ownership, see theMy Teamcenter Guide.

For information about reassigning the user’s tasks using the My Teamcenterinbox feature, see the My Teamcenter Guide.

Note If deleting all objects owned by the user, the delete procedure fails if anyof these objects are referenced by another object. If this occurs, changeownership of the referenced objects to a different user.

Delete a user1. Select the user definition to be deleted from the Users list in the Organization

List tree.The Users pane displays the properties of the user definition.

2. Click Delete.The Delete User dialog box appears.

3. Confirm that the correct user definition is selected for deletion.

4. Perform one of the following substeps:

• If deleting all database objects owned by the user, go to step 7.

• If changing ownership of all database objects owned by the user, go to step 5.

5. Select the Change Object Ownership check box and click New Objects Owner.The List of Values list.

6. Select a new object owner from the New Objects Owner list by double-clicking.


Defining users

The name of the new owner on the New Objects Owner button.

7. Click Delete.

The user definition is permanently removed from the database.

Specifying password restrictionsTeamcenter enables companies to specify restrictions for passwords when creatinguser accounts. These password restrictions are controlled through preferencessettings and take effect upon password creation. Existing passwords are not affected.

Companies can set the following restrictions:

• Minimum length required (PASSWORD_minimum_characters)

• Mixed case required (PASSWORD_mixed_case_required)

• Minimum number of alpha or numeric characters required(PASSWORD_minimum_alpha and PASSWORD_minimum_digits)

• Special characters

ExamplesPASSWORD_minimum_characters=0

PASSWORD_mixed_case_required=false

PASSWORD_minimum_alpha=0

PASSWORD_minimum_digits=0

PASSWORD_special_characters=#,*,%

PASSWORD_minimum_special_chars=0

Note If a user attempts to log into Teamcenter without entering a password, alogon failure occurs.

For information about setting password preferences, see the Preferences andEnvironment Variables Reference.

Configuring ADA for ITAR supportWhen creating users, you can define the following ADA/ITAR attributes for each userin the ADA/ITAR Attributes section of the Users pane:• IP clearance

Intellectual property (IP) clearance applies to a specific user and specifies thelevel of access the user has to sensitive (classified) information.

• Government clearance and TTC date



Government clearance status and technology transfer certification (TTC) datetrack the user’s level of clearance for viewing data marked as governmentclassified. Teamcenter revokes the user’s access rights after the TTC dateexpires unless renewed. As an administrator, you may manually cancel a TTCat any time.

• Geography, nationality, and citizenship

Teamcenter uses nationality, citizenship (one or more), and geography (physicallocation) attributes to determine if the user is a foreign (non-U.S.) national forITAR purposes or a U.S. national located outside the U.S. In either of thesecases, if the user views classified material, it is considered an ADA export andrequires a license granting rights to export.

For information about configuring and administering authorized data, see theSecurity Administration Guide.

Changing user statusSiemens PLM Software recommends that you first deactivate an obsolete useraccount in the Teamcenter database, then delete it when all references to theaccount cease.

Because the names of inactive users do not display in the list of values (LOVs)throughout the rich client, inactive accounts cannot continue to be referenced byother users. Inactive user accounts cannot be logged on to the database, yet accountrecords remain in the database so that an audit trail can continue to reference thedata.

An account can be deleted when all references to objects owned by the deactivatedaccount are cleared from the database, and an audit trail of the account’s actions isno longer required.

Note A replicated (remote) user is designated by having two green dots beside the

user symbol to designate it as a remote object . As an administrator, youcannot modify the associated data. However, you can remove remote usersfrom your local organization structure.

Inactivate a user account1. Perform one of the following substeps:



The Users pane displays the properties of the user definition.Note Because database objects are owned by users, you must decide what to

do with any objects owned by the user being deactivated. You can eitherchange ownership of these objects to another user or allow ownership tobe retained by the inactive user.

2. Click Inactive.


Defining users

The Change Ownership button becomes available.

3. Perform one of the following substeps:

• If you want to change the ownership of the user’s database objects, go tostep 4.

• If you want ownership of the database objects to be retained by the inactiveuser, go to step 6.

4. Click Change Ownership.

5. Select a new owner for the database objects from the List of Defined Users list(double-click a user).

The name of the new owner on the Change Ownership button.

6. Click Modify.

7. If the Inactivate All Members dialog box displays and you want to set the user’sGroup Member Status to Inactive for all groups that the user belongs to, clickYes. If you want to keep the user’s Group Member Status set as they currentlyare for all groups, click No.

The user account is deactivated.

Activate a user account1. Perform one of the following substeps:



2. Click Active.

3. Click Modify.

The user account is activated.

Add an existing user to a role/group using the Organization Userwizard

The Organization User wizard can be used to add an existing user to a group duringthe process of creating a group/role combination in the Organization tree.Existing users can also be added to existing group/role combinations within theOrganization tree. The procedure for using the Organization User wizard to addan existing user is the same, regardless of the activity being performed when thewizard is invoked.

1. Select a role node from the Organization tree.The Roles pane.

2. Click Add User.



The Organization User wizard.

3. Select Add existing user to the group/role and click Next.

4. Select the users to add from the Available Users list.

You can also use either of the following buttons in the search pane:

• Find users

• Reload all available users

You can move items between the Available Users and Selected Users lists bydouble-clicking a user or selecting a user and clicking the right arrow ( ) or leftarrow ( ) buttons. After you select all the users to be added, click Finish tocontinue or Close to dismiss the wizard.

5. If you clicked Finish, a message appears asking if you want to add the selectedusers. Click Yes.

6. Click OK.

The User(s) added dialog box closes and you are returned to step 1 on theOrganization User wizard.

The user appears in the Organization tree as a child of the selected role.


Defining users

7. Click Close or repeat steps 1 through 6 to add additional users to the samerole/group combination.

Add a new user to a group/role using the Organization User wizardYou can add a new user to the Organization tree as part of the process of creatingthe group/role hierarchy.

You can also add a new user to an existing group/role combination in theOrganization tree. The procedure for using the Organization User wizard to add anew user is the same, regardless of the activity being performed when the wizard isinvoked.

1. Select a role node from the Organization tree.The Roles pane appears.

2. Click Add User.The Organization User wizard appears.

3. Select Add new user to the group/role and click Next.

4. Create the user by performing the following substeps:

a. Define the person to be associated with this user. If the person definitionalready exists, click Person Name to display the List of Defined Personslist and select, by double-clicking, a person name from the list. If a persondefinition does not yet exist, type the name of the individual in the PersonName box.

b. Type a unique user name in the User ID box.

c. Type the user’s OS name in the OS Name box.

d. Optionally, type a password. Default Group and Roles are already filled infor you.

e. Click Default Volume to display the List of Defined Volumes list and select,by double-clicking, a default volume for the group.

Caution If you create a group without assigning a default volume,group members cannot save datasets. Therefore, Siemens PLMSoftware recommends that you assign a default volume for thegroup.

f. Click Default Local Volume to display the List of Defined Volumes list andselect, by double-clicking, a default local volume for the group.

Note The Default Local Volume value must be different from the value inthe Default Volume box.

g. Set the licensing level to the appropriate level for the tasks the user performs.

License levels are used to enable usage by time or by features.



For descriptions of the available license levels, see your license agreementdocumentation.

For information about administering Teamcenter licenses, see the SystemAdministration Guide.

h. Select the appropriate license bundle from the License Bundle list. As anadministrator, you can assign a license bundle to a user.

If the selected license bundle has a base license level, the License Level boxis updated with this value and is made non-editable.

i. When all required input is complete, click Next or Finish.

j. Click Yes to create the new user.

If you created a new person definition while creating the new user, go to step 5.If you did not create a new person definition, go to step 6.

5. The Create Person dialog box appears. Click Yes to confirm that you want tocreate the new person.

6. The User(s) added dialog box appears. Click OK.The User(s) added dialog box is dismissed and you are returned to step 1 ofthe Organization User wizard.

The new user appears as a child of the selected role in the Organization tree.Additionally, the new user and person (if applicable) are displayed in theOrganization List tree.Note Persons are not displayed in the Organization tree.

7. Click Close to dismiss the Organization User wizard or repeat steps 3 through 6of this section to add additional users to the same role/group combination.

Managing internal, external, and remote user constructsNote External directory synchronization is intended for use in conjunction with

external directory authentication using Security Services.

User constructs synchronized from LDAP are updated each time theldapsync utility is run, and attribute changes made by other utilities areoverwritten by the ldapsync utility if those attributes are mapped forsynchronization. Teamcenter administrators are responsible for ensuringsynchronized data for externally managed user construct objects does not getoverwritten by other utilities. If it does get overwritten, the changes are lostthe next time the ldapsync utility is run to update the synchronized data.

You can organize your user base on a corporate LDAP directory server that is alsoused as a central user authentication repository for applications such as Teamcenter.This user data can be synchronized with Teamcenter using the ldapsync utility.User constructs maintained in this manner are considered to be externally managed.Users, groups, and roles created and maintained in Teamcenter are considered tobe internally managed. User constructs that are synchronized from an external


Defining users

directory at one site and distributed to remote sites are considered to be remotelymanaged.

The Teamcenter authorization infrastructure used at logon and within the AccessManager rule tree for object authorization works in the same manner for bothexternally managed and internally managed users. Externally managed userconstructs can exist in the same Teamcenter database as users constructs createdusing Teamcenter.

Externally managed, user, group, and role attributes mapped between the LDAPserver and the Teamcenter database cannot be updated using the Organizationapplication. However, attributes that are not mapped or are specific to Teamcenterusers, groups, and roles can be updated in Organization. The attributes of remotelymanaged user constructs cannot be modified in Teamcenter.

Replicated (remote) objects (group, role, person, and user) are designated by having

two green dots beside them to designate them as remote objects . As anadministrator, you cannot modify the associated data. However, you can removeremote objects from your local organization structure.

Mapping and synchronization considerationsThe synchronization process affects only user data that is new, or has been removed,deactivated, or updated. Certain attributes have special handling during thesynchronization process, as follows:

• Externally managed passwords are never synchronized with Teamcenter.

Note The passwords of externally managed users are set to the same value asthe user ID. This is merely a placeholder, because sites using externalsynchronization must also have external authentication configured;therefore, user passwords are authenticated against the LDAP directory.

• User status should not be mapped from an LDAP attribute. User status, activeor inactive, is synchronized with Teamcenter based on the following conditions:

o If the user exists in the LDAP server but not in Teamcenter, the user iscreated in Teamcenter using the mapped attributes from LDAP. The useris configured to be externally managed and the user’s status in Teamcenteris set to active.

o If the user exists in both the LDAP server and Teamcenter and the useris configured to be externally managed, the user’s mapped attributes aresynchronized from LDAP to Teamcenter. The user’s status in Teamcenteris set to active.

o If the user exists in Teamcenter but not in the LDAP server and the useris configured to be externally managed, the user’s status in Teamcenteris set to inactive.

Note The status field acts as an emergency override for the Teamcenteradministrator to disable externally managed user accounts withoutupdating the external directory and running the synchronizationprocess.


Chapter

8 Defining administrativeprivileges

Considerations for managing administration accounts . . . . . . . . . . . . . . . . . . 8-1

infodba account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2

System administration accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2


Chapter

8 Defining administrativeprivileges

Considerations for managing administration accountsAdministrative privileges are required to manage Teamcenter administrative datalike organization, access rules, and workflows. Administration accounts havepowerful access to data and must be controlled and managed with caution.

When managing administration accounts, consider these key points:

• The infodba account has all the Teamcenter system-level privileges.

• The Bypass administrative setting supersedes other privileges.

• Members of the dba group with the DBA role have complete system privileges.

• For each group:

o Create at least one member who acts as the administrator for that group.Group administrators can assign other group administrators in their group.

o Create a DBA role to manage roles for that group and assign the groupadministrator. The DBA role for a user in a non-dba group has no additionalprivileges over any other group member.


Chapter 8 Defining administrative privileges

infodba account

The infodba account has all the Teamcenter system-level privileges, including abypass switch to override access protections. The infodba account has special accesspermissions applied to data they create.

System administration accountsAdministrator privileges include the following settings:

Setting Privileges

Member of the dba group or anotherdba group

All system administration privileges.Users in the dba group have a Bypasstoggle that can be turned on with theUser Setting dialog box (Edit→UserSetting→Administrative).

Group administrator Special access privileges for data ownedby the group.

System administrator Configures access authorization toadministration applications and utilitiesbased on group and role in group.Member of a group with DBA privileges.

IP Admin role Manages intellectual property licenses.

For information about configuring andadministering authorized data access,see the Security Administration Guide.

ITAR Admin role Manages International Traffic in ArmsRegulations licenses.

For information about configuring andadministering authorized data access,see the Security Administration Guide.


Defining administrative privileges

Setting Privileges

DBA role Manages roles for that group and canassign the group administrator.

Member of the system group with theDBA role

Special access privileges for archive andrestore.

Bypass option turned on Overrides access protections andsupersedes other privileges.


Chapter

9 Defining disciplines

What is a discipline? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1

Create a discipline . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1

Modify a discipline . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2

Delete a discipline . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2

Add a discipline to a group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2

Remove a discipline from a group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3


Chapter

9 Defining disciplines

What is a discipline?A discipline is a set of users who have a common behavior, for example, developersthat have expertise in UNIX.

You have the option to define a discipline for each Teamcenter user. As a user withDBA or group administrator privileges, you can use the Organization application to:

• Create disciplines.

• Modify disciplines.

• Delete disciplines.

• Add disciplines to a group.

• Remove disciplines from a group.

Create a discipline1. Select the top-level Disciplines node from the Organization List tree.

The Disciplines pane appears.


• Type a unique name in the Name box.

• (Optional) Type a description in the Description box.

• Type a default rate in the Default Rate box, or accept the default value.

• Select the currency type from the Default Currency list, for example, USD,which denotes United States dollars.

• Select users from the List of Users list. Add one or more users to the list byselecting a user from the List of Users and either double-clicking the user

name or clicking the plus button to move them to the List of AssociatedUsers list. You can remove users from the List of Associated Users list bydouble-clicking a user or selecting a user and clicking the minus button .

3. Click Create .


Chapter 9 Defining disciplines

Modify a discipline1. From the Organization List tree, double-click Disciplines to display the existing

disciplines.

2. Select the discipline to be modified.

The Disciplines pane displays the discipline definition.

3. Modify any information in the Disciplines pane by typing over the existinginformation.

NoteFor more information about the Localization button associated withthe Name box, see the Localization Guide.

4. Click Modify.

The system saves the changes to the discipline definition.

Delete a discipline1. From the Organization List tree, double-click Disciplines to display the existing

disciplines.

2. Select the discipline to be deleted.

The Disciplines pane displays the discipline definition.

3. Click Delete.


The Disciplines pane clears and the discipline is deleted from the database.

Add a discipline to a group1. Select a group from the upper-left corner of the Organization tree.

The associated group pane appears.

2. Click Add Discipline.

The Organization Discipline Wizard appears.


Defining disciplines

3. Click Next.

4. Select the discipline to add to the group, click the plus button to add thediscipline to the Selected Disciplines list.

5. Click Next.

6. Click Yes to add the selected discipline.

7. Click Close.

The selected discipline is added to the group.

Remove a discipline from a group1. Select a group from the upper-left corner of the Organization tree.

The associated group pane appears.

2. Select the discipline to remove.

3. Click Remove .

The selected discipline is removed from the group.


Chapter

10 Defining calendars

Selecting which calendar type to use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1

Modify the base calendar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1

Create a user calendar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-2

Modify a user calendar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-3


Chapter

10 Defining calendars

Selecting which calendar type to useTeamcenter allows you to create four types of calendars that allow you to considerthings like work days, work hours, holidays, and vacations when developingschedules for your projects.

• The base calendar, which is installed by default with Teamcenter, is used as themaster calendar when creating schedules. It shows which days are workdays,hours in a workday, holidays, and days off. As an administrator, you can modifythe base calendar using Organization.

Teamcenter provides the following three default base calendars:

o Standard

o Night shift

o 24 hours

A site can have several base calendars.

• The user calendar allows you to set days off, holidays, and hours in a day for thecurrent user. You can create it using either My Teamcenter or Organization.

• The schedule calendar allows you to set days off, holidays, and hours in a dayfor the current schedule. Setup information is documented in the ScheduleManager Guide.

• The schedule user calendar allows you to set days off, holidays, and hours ina day for an individual resource (person or discipline). Setup information isdocumented in the Schedule Manager Guide.

As a user with DBA or group administrator privileges, use the Organizationapplication to modify the base calendar and create and modify the user calendar.

For more information about calendars, see the Schedule Manager Guide.

Modify the base calendar1. Select a calendar to modify, for example, Engineering calendar, from the

Calendars node in the Organization List tree.

The calendar to be modified appears in the calendar pane.


Chapter 10 Defining calendars

2. Edit the calendar information for your desired implementation.

• Select the month and year by either:

o Clicking the right arrow ( ) or left arrow ( ) buttons.

o Entering the desired date in the date field.

• Select the items from the For Selected Dates list.

• Select the working hours from the Daily Defaults list.

3. Click Modify .

The system saves the changes to the calendar definition.

Create a user calendar

1. Double-click the Users node from the Organization List tree to display alist of users.

The Users pane appears.

2. Select a user from the Organization List tree.

3. Right-click the user and choose Calendar→Create Calendar.


Defining calendars

A calendar is added to the Calendars node for the user.The Create User Calendar dialog box appears. Click Yes to verify you want tocreate a user calendar.

Modify a user calendar

1. Select the Calendars node from the Organization List tree.

The tree expands to show all existing users who have calendars on the system.

2. Select a calendar from the Organization List tree.

You can now edit the calendar.

NoteFor more information about the Localization button associated withthe Calendar Name box, see the Localization Guide.

3. Click Modify to save the changes to the user’s calendar.


Chapter

11 Defining external applications

What is an external application? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1

Creating external applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1

Modify an external application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1

Delete external applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-2


Chapter

11 Defining external applications

What is an external application?External applications are part libraries that are based on site objects.

In the Organization application, you can create, modify, and delete and externalapplications.

Creating external applications1. Select the top-level External Applications node from the Organization List

tree.

The External Applications pane appears.


a. Type a unique application name in the Application Name box using anycombination of alphanumeric characters. You can use the hyphen (-) andunderscore (_) special characters.

b. Type a unique application ID in the Application ID box. The application IDmust be any valid positive integer.

To automatically generate a unique application ID, click the Assign button.

c. Select the application type from the Application Type list.

d. Select Allow deletion of replicated master items to this site to allow thedeletion of replicated master items.

Note The Uses TCXML Payload check box only for information purposes andcannot be modified.

3. Click Create.

Modify an external application1. From the Organization List tree, double-click the External Applications node

to display the existing external applications.

2. Select the external application to be modified.


Chapter 11 Defining external applications

The External Applications pane displays the properties of the externalapplication definition.

3. Modify any information contained in the External Applications pane by typingover the existing information.

4. Click Modify.

The modified external application definition is saved in the database.

Delete external applications1. From the Organization List tree, double-click the External Applications node

to display the existing external applications.

2. Select the external application to be deleted.

3. Click Delete.


4. Verify that the correct external application is selected.

5. If the correct external application is displayed, click Yes.

The External Applications pane clears, and the external application definitionis deleted from the database.


Chapter

12 Defining languages

What is a language? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-1

Create a language . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-1

Modify a language . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-2

Delete a language . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-2


Chapter

12 Defining languages

What is a language?A language represents the vocabulary of a country or region. Languages areidentified by a unique language name and store such attributes as the ISO languagecode and ISO country code. In Content Management, languages are associated withcontent that is translated into specific languages.

As a user with DBA privileges, you use the Organization application to:

• Create languages.

• Modify languages.

• Delete languages.

Create a language

1. Select the top-level Language node from the Organization List tree.The Language pane appears.

2. In the Language Name box, type the name of the language.If you are creating a language for the DITA standard, use the allowed values,which are based on industry standards.

For more information, see the DITA Language Specification.

3. (Optional) Select the two-letter code for the language that corresponds to theISO standard.

4. (Optional) Select the two-letter country code for the language that correspondsto the ISO standard.

5. Type the string appended to the XML unique ID at construction of rendition filenames for documents in the Language File Initials box.

6. (Optional) Type descriptive text about the language in the Language Descriptionbox.

7. (Optional) In the Default Publishing Font box, type the default font forpublishing content in the language to PDF; for example, Helvetica.



http://docs.oasis-open.org/dita/v1.1/OS/langspec/common/localization-atts.html

Chapter 12 Defining languages

The following fields are related to the language selection:

• To enable logon, select the Login Enabled check box.

• To enable metadata, select the Metadata Enabled check box.

• To enable content, select the Content Enabled check box.

9. Click Create.

Modify a language1. From the Organization List tree, select the node of the language to modify.

The Language pane displays the properties of the language definition.

2. Modify any information in the Language pane boxes by typing over existinginformation.

3. Click Modify.

The system saves the changes to the language definition.

Delete a languageNote You cannot delete languages that are referenced by another object.

1. From the Organization List tree, select the node of the language to delete.

The Language pane displays the properties of the language definition.

2. Verify that the correct language is selected.

3. Click Delete.


4. If the correct language appears, click Yes.

The Language pane clears and the language is deleted from the database.


Chapter

13 Defining graphic priority lists

What is a graphic priority list? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1

Create a graphic priority list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1

Modify a graphic priority list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-2

Delete a graphic priority list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-2


Chapter

13 Defining graphic priority lists

What is a graphic priority list?A graphic priority list is a list of graphic uses in a specific order, for example: print,view, and thumbnail.Graphic priority lists are used in Content Management to manage graphic items andgraphic options. A graphic item has no specific file type but serves as a genericparent placeholder for one or more graphic options. A graphic option is a graphicfile of a specific type, such as a .png file. For example, a graphic item may benamed piston, and it may have several child graphic options named piston.eps,piston.jpg, and piston.png.

When you import a graphic option to the database, you assign one or more uses toit, which defines the contexts in which the graphic is best suited. For example, thepiston.png graphic option may have the view usage assigned to it.

In Content Management, when an editing or publishing tool editor opens an objectthat contains a graphic item, the tool uses a graphic priority list to select theappropriate graphic option.

As a user with DBA privileges, you use the Organization application to:

• Create graphic priority lists.

• Modify graphic priority lists.

• Delete graphic priority lists.

Create a graphic priority list

1. Select the top-level Graphic Priority List node from the Organization Listtree.

The Graphic Priority List pane appears.

2. In the Name box, type a unique name for the graphic priority list.

3. (Optional) In the Description box, type a description for the graphic priority list.

4. For each use you want to add to the priority list, select a use from the List of

Defined Uses list and either double-click it or click the plus button to moveit to the List of Selected Uses list. You can remove items from the List ofSelected Uses list by double-clicking a use or selecting a use and clicking theminus button .


Chapter 13 Defining graphic priority lists

Note Keep the uses in the order in which you want them to be selected for apublish or view action.

If the graphic is used for this purpose Select this graphic use

Icon in published output. ICONHigh-resolution graphic in printed output. PDFGraphic in a resolution appropriate for theprinter where it will be printed.

PRINT

Small-scale image. THUMBNAILLow-resolution image, typically for viewing only. VIEWImage to appear in a Web browser. WEB

5. In the Multiple Graphics Publish Max Options box, do one of the following:• For standard publishing, type 1.

• To make the graphic option selection dependent on the stylesheet, type avalue greater than 1, so that multiple copies of the graphic tag are added tothe content during publishing.

That number of graphic options are selected from the priority list. Forexample, if you type 3, the first three graphics in the priority list are selected.This is used for specific cases, such as for dynamic HTML contents, wherethe graphic resolution changes when a mouse hovers over a graphic.

6. Click Create.

Modify a graphic priority list1. From the Organization List tree, select the node of the graphic priority list to

modify.

The Graphic Priority List pane displays the properties of the graphic priority list.

2. Modify any information in the Graphic Priority List pane by typing over existinginformation.

3. Use the plus ( ) or minus ( ) buttons to arrange the uses in the list.

4. Click Modify.

Delete a graphic priority listNote You cannot delete graphic priority lists that are referenced by another object.

1. From the Organization List tree, select the node of the graphic priority list todelete.

The Graphic Priority List pane appears.


Defining graphic priority lists

2. Verify that the correct graphic priority list is selected.

3. Click Delete.


4. If the correct graphic priority list displays, click Yes.

The Graphic Priority List pane clears, and the graphic priority list is deletedfrom the database.


Appendix

A Glossary


Appendix

A Glossary

A

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

AMSee Access Manager (AM).

B

base calendarMaster calendar used when creating schedules.

C

calendarDefines working times.

D

disciplineSet of users who have a common behavior, for example, developers that haveexpertise in UNIX.

F

facilityPhysical location in an enterprise (for example, manufacturing plant or designcenter). One facility can comprise multiple sites. Compare with site.

G

graphic itemParent object that has one or more graphic files related to it. The graphic filescontain the same image but are of different file types.

PLM00029 J Organization Guide A-1

Appendix A Glossary

graphic optionGraphic object of a specific file type, for example, .png and .bmp. It is related to agraphic item, which is the parent object of graphic options that have the same imagebut are of different file types.

graphic priority listObject that specifies the priority with which graphic options are selected whencontent is viewed or published.

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

group administratorUser with special maintenance privileges for a group.

group preferenceTeamcenter preference applying to an entire group.

H

heterogeneous network environmentTeamcenter network environment consisting of hosts that do not all run the sameplatform, for example, a corporate server running on a UNIX host, a Web applicationserver running on a Linux host, and workstations running on Microsoft Windows.

Contrast with homogeneous network environment.

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

homogeneous network environmentTeamcenter network environment in which all hosts run the same platform, forexample, a corporate server, Web tier, and Teamcenter clients all running onMicrosoft Windows or all running on SUSE Linux.

Contrast with heterogeneous network environment.

L

List of Values (LOV)Pick list of values accessed by end users from a menu at the end of a data field.LOVs ensure consistent data entries in the rich client.

LOVSee List of Values (LOV).

M

Multi-Site CollaborationTeamcenter capability that allows the exchange of data objects among severalTeamcenter databases. Transfer of objects among databases is controlled by daemonprocesses running on designated servers. Objects are replicated by exporting themfrom their original database and importing them into the requesting database.Configuration of Multi-Site Collaboration is optional.

A-2 Organization Guide PLM00029 J

Glossary

Multi-Site Collaboration networkNetwork of independent Teamcenter sites that are within the same enterprise andshare data using Multi-Site Collaboration.

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.

O

object directory services serverMulti-Site Collaboration network node that runs a daemon process to handlepublication of data objects within a Multi-Site Collaboration environment. OneODS server node must be designated for each object directory services site and eachserver node can act only for one object directory services site.

object directory services siteSite with the database that maintains a record of each object in a Multi-SiteCollaboration network. At least one Teamcenter database on a Multi-SiteCollaboration network must be designated as an ODS site. This site is used to storepublication records for the data objects.

ODS serverSee object directory services server.

ODS siteSee object directory services site.

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.

organization treeGraphic display of the Teamcenter organization structure. Expanding and collapsingbranches of the tree enables viewing and managing the organizational structure.Selecting a node starts Organization wizards used to create groups, subgroups,roles, users, and persons.

owning siteMulti-Site Collaboration site where the master object resides. The owning site is theonly site where the object can be modified.


Appendix A Glossary

P

personDefinition containing real-world information about each Teamcenter user, such asname, address, and telephone number. Person definitions are stored as simple textstrings so that they can be easily changed and updated. The name must be unique.

perspectiveContainer in the rich client user interface for a set of views and editors collected toaccomplish specified tasks. See also view.

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.

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

R

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 accessorused to grant privileges to all users with the same skills and/or responsibilitiesregardless of project.

S

schedule calendarCalendar to define days off, holidays, and working times in a day for the currentschedule.

schedule user calendarCalendar to define days off, holidays, and working times in a day for a user in thatschedule.

Security ServicesServices that eliminate prompts for logon credentials when users switch Teamcenterproducts within a user session. Authentication is performed by an external identityservice provider, such as lightweight directory access protocol (LDAP), instead ofthe Teamcenter product. At a site that deploys multiple Teamcenter products andSecurity Services, users log on once to access all participating Teamcenter products.

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.

A-4 Organization Guide PLM00029 J

Glossary

site IDUnique identifier of a Teamcenter site. The site ID is used to generate internalidentifiers for Teamcenter objects that must be unique throughout an enterprise.Once established, site IDs should not be modified.

site nameUnique name of a Teamcenter site stored in the database as a user-defined characterstring.

system administratorTeamcenter user who is a member of the system administration group.

T

Teamcenter File Services (TCFS)File services that enable the Organization application to create volumes and performother administrative functions. TCFS also supports file access for legacy versions ofNX and Teamcenter lifecycle visualization.

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.

user calendarCalendar for individual users. User calendars specify holidays and working timesin a day.

V

viewSoftware element in a rich client user interface perspective. It provides the ability tonavigate hierarchies of information, display information about selected objects, openan editor, or display properties. See also perspective.

volumeOperating system directory controlled by Teamcenter and used to store the filesmanaged by Teamcenter. When a user performs an action that causes Teamcenterto create a file, the file is created in the Teamcenter volume. Users cannot directlyaccess the files in Teamcenter volumes; they must do so via a Teamcenter session.

W

workflowAutomation of the concept that all work flows through one or more businessprocesses to accomplish an objective. Using workflow, documents, information, andtasks are passed between participants during the completion of a particular process.

Workflow DesignerTeamcenter application that enables administrators to graphically design workflowprocess templates, incorporating company business practices and procedures intothe templates. Teamcenter users initiate workflow processes using these templates.


Index

AAccountsinfodba . . . . . . . . . . . . . . . . . . . . . . . 8-2System administration . . . . . . . . . 8-1–8-2

ActivatingGroup members . . . . . . . . . . . . . . . . 5-11User accounts . . . . . . . . . . . . . . . . . . 7-9

AddingDisciplines to a group . . . . . . . . . . . . . 9-2Existing groups . . . . . . . . . . . . . . . . 5-12Existing roles to a group . . . . . . . . . . . 4-3Existing users to a group/role . . . . . . . 7-9New roles to a group . . . . . . . . . . . . . . 4-4New subgroups . . . . . . . . . . . . . . . . 5-14New users to a group/role . . . . . . . . . 7-11

BBase calendars . . . . . . . . . . . . . . . . . . 10-124 hours . . . . . . . . . . . . . . . . . . . . . 10-1Night shift . . . . . . . . . . . . . . . . . . . 10-1Standard . . . . . . . . . . . . . . . . . . . . . 10-1

Building hierarchyOrganization List tree method . . . . . . 1-7Organization tree method . . . . . . . . . . 1-8

ButtonsGroup . . . . . . . . . . . . . . . . . . . . . . . . 1-3Person . . . . . . . . . . . . . . . . . . . . . . . 1-3Role . . . . . . . . . . . . . . . . . . . . . . . . . 1-3User . . . . . . . . . . . . . . . . . . . . . . . . . 1-3

Bypass switch . . . . . . . . . . . . . . . . . . . . 8-2

CCalendarsBase calendar . . . . . . . . . . . . . . . . . 10-1Schedule calendar . . . . . . . . . . . . . . 10-1Schedule user calendar . . . . . . . . . . . 10-1User calendar . . . . . . . . . . . . . . . . . 10-1

Changing user status . . . . . . . . . . . . . . 7-8Configuring Organization . . . . . . . . . . . 1-2Controlling volumes’ access . . . . . . . . . . 3-5CreatingDisciplines . . . . . . . . . . . . . . . . . . . . 9-1Graphic priority lists . . . . . . . . . . . . 13-1

Groups . . . . . . . . . . . . . . . . . . . . . . . 5-2Languages . . . . . . . . . . . . . . . . . . . . 12-1Parent groups . . . . . . . . . . . . . . . . . . 5-6Persons . . . . . . . . . . . . . . . . . . . . . . . 6-1Roles . . . . . . . . . . . . . . . . . . . . . . . . 4-2Sites . . . . . . . . . . . . . . . . . . . . . . . . . 2-1User calendars . . . . . . . . . . . . . . . . . 10-2Users . . . . . . . . . . . . . . . . . . . . . . . . 7-1Volumes . . . . . . . . . . . . . . . . . . . . . . 3-2

DDeactivating group members . . . . 1-11, 5-11Default groups, definition . . . . . . . . . . . 5-8Default local volume . . . . 5-4, 5-6, 5-15, 7-3Default roles . . . . . . . . . . . . . . . . . . . . . 4-4DeletingDisciplines . . . . . . . . . . . . . . . . . . . . 9-2Graphic priority lists . . . . . . . . . . . . 13-2Groups . . . . . . . . . . . . . . . . . . . . . . . 5-8Languages . . . . . . . . . . . . . . . . . . . . 12-2Persons . . . . . . . . . . . . . . . . . . . . . . . 6-3Roles . . . . . . . . . . . . . . . . . . . . . . . . 4-2Sites . . . . . . . . . . . . . . . . . . . . . . . . . 2-3Users . . . . . . . . . . . . . . . . . . . . 1-11, 7-6Volumes . . . . . . . . . . . . . . . . . . . . . . 3-5

DisciplinesAdding to a group . . . . . . . . . . . . . . . 9-2Creating . . . . . . . . . . . . . . . . . . . . . . 9-1Definition . . . . . . . . . . . . . . . . . . . . . 9-1Deleting . . . . . . . . . . . . . . . . . . . . . . 9-2Modifying . . . . . . . . . . . . . . . . . . . . . 9-2Removing from a group . . . . . . . . . . . 9-3

Displaying inactive group members . . . 5-11

EEnabling Organization . . . . . . . . . . . . . 1-2ExportingGroup objects . . . . . . . . . . . . . . . . . . 1-16Organization objects . . . . . . . . . . . . . 1-15Person objects . . . . . . . . . . . . . . . . . 1-17Role objects . . . . . . . . . . . . . . . . . . . 1-17User objects . . . . . . . . . . . . . . . . . . . 1-16

Exporting Organization objects . . . . . . 1-17

PLM00029 J Organization Guide Index-1

Index

External applicationsCreating . . . . . . . . . . . . . . . . . . . . . 11-1Defining . . . . . . . . . . . . . . . . . . . . . 11-1Deleting . . . . . . . . . . . . . . . . . . . . . 11-2Modifying . . . . . . . . . . . . . . . . . . . . 11-1

External directory synchronization . . . . 7-12

FFiltering . . . . . . . . . . . . . . . . . . . . . . . . 1-3Home site . . . . . . . . . . . . . . . . . . . . 1-13Objects by site . . . . . . . . . . . . . . . . . 1-14Organization hierarchy . . . . . . . . . . . 1-13

Find . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3Group . . . . . . . . . . . . . . . . . . . . . . . . 1-4Inactive group members . . . . . . . . . . . 1-4Reload . . . . . . . . . . . . . . . . . . . . . . . 1-4Role . . . . . . . . . . . . . . . . . . . . . . . . . 1-4User . . . . . . . . . . . . . . . . . . . . . . . . . 1-4

Gglobal_transfer utility . . . . . . . . . . . . . 5-11Granting volume access . . . . . . . . . . . . . 3-6Graphic priority lists . . . . . . . . . . . . . . 13-1Creating . . . . . . . . . . . . . . . . . . . . . 13-1Definition . . . . . . . . . . . . . . . . . . . . 13-1Deleting . . . . . . . . . . . . . . . . . . . . . 13-2Modifying . . . . . . . . . . . . . . . . . . . . 13-2

Group administrator, definition . . . . . . . 5-9Group names, definition . . . . . . . . . . . . . 5-9Groups . . . . . . . . . . . . . . . . . . . . . . . . . 5-1Activating members . . . . . . . . . . . . . 5-11Adding existing groups . . . . . . . . . . . 5-12Adding new subgroups . . . . . . . . . . . 5-14Creating . . . . . . . . . . . . . . . . . . . . . . 5-2Creating parent groups . . . . . . . . . . . 5-6Creating using Organization List

tree . . . . . . . . . . . . . . . . . . . . . . . 5-3Deactivating members . . . . . . . 1-11, 5-11Defining roles . . . . . . . . . . . . . . . . . . 4-1Definition . . . . . . . . . . . . . . . . . . . . . 1-6Deleting . . . . . . . . . . . . . . . . . . . . . . 5-8Displaying inactive members . . . . . . 5-11Exporting . . . . . . . . . . . . . . . . . . . . 1-17Externally managed . . . . . . . . . . . . . 7-12Group member . . . . . . . . . . . . . . . . . . 5-1Hierarchy . . . . . . . . . . . . . . . . . . . . . 5-9Managing . . . . . . . . . . . . . . . . . . . . 5-10Modifying . . . . . . . . . . . . . . . . . . . . . 5-7Parent . . . . . . . . . . . . . . . . . . . . . . . 5-8Removing members . . . . . . . . . . . . . 5-10Subgroups . . . . . . . . . . . . . . . . . . . . . 5-2Suppressing display of inactive

members . . . . . . . . . . . . . . . . . . 5-11

system . . . . . . . . . . . . . . . . . . . . . . . 5-9System administration . . . . . . . . . . . . 5-8

HHierarchyGroup . . . . . . . . . . . . . . . . . . . . . . . . 5-9Organization . . . . . . . . . . . . . . . . . . . 1-7

IInactivating user accounts . . . . . . . . . . . 7-8infodba . . . . . . . . . . . . . . . . . . . . . . . . . 8-2

LLanguages . . . . . . . . . . . . . . . . . . . . . 12-1Creating . . . . . . . . . . . . . . . . . . . . . 12-1Definition . . . . . . . . . . . . . . . . . . . . 12-1Deleting . . . . . . . . . . . . . . . . . . . . . 12-2Modifying . . . . . . . . . . . . . . . . . . . . 12-2

ldapsync utility . . . . . . . . . . . . . . . . . . 7-12

Mmake_user utility . . . . . . . . . . 1-7, 1-10, 7-2Managing groups . . . . . . . . . . . . . . . . 5-10Managing volume failover behavior . . . . 3-8ModifyingBase calendars . . . . . . . . . . . . . . . . 10-1Disciplines . . . . . . . . . . . . . . . . . . . . 9-2External applications . . . . . . . . . . . . 11-1Graphic priority lists . . . . . . . . . . . . 13-2Groups . . . . . . . . . . . . . . . . . . . . . . . 5-7Languages . . . . . . . . . . . . . . . . . . . . 12-2Persons . . . . . . . . . . . . . . . . . . . . . . . 6-2Roles . . . . . . . . . . . . . . . . . . . . . . . . 4-2Sites . . . . . . . . . . . . . . . . . . . . . . . . . 2-3User calendars . . . . . . . . . . . . . . . . . 10-3Users . . . . . . . . . . . . . . . . . . . . . . . . 7-5Volume locations . . . . . . . . . . . . . . . . 3-3Volume properties . . . . . . . . . . . . . . . 3-4

move_volume_files utility . . . . . . . . . 3-7–3-8

OOrganizationCalendars . . . . . . . . . . . . . . . . . . . . 10-1Definition . . . . . . . . . . . . . . . . . . . . . 1-5Disciplines . . . . . . . . . . . . . . . . . . . . 9-1Filter . . . . . . . . . . . . . . . . . . . . . . . . 1-3Find . . . . . . . . . . . . . . . . . . . . . . 1-3–1-4Graphic priority lists . . . . . . . . . . . . 13-1Group hierarchy . . . . . . . . . . . . . . . . 5-9Groups . . . . . . . . . . . . . . . . . . . . . . . 5-1Hierarchy . . . . . . . . . . . . . . . . . . . . . 1-7

Index-2 Organization Guide PLM00029 J

Index

Languages . . . . . . . . . . . . . . . . . . . . 12-1Passwords . . . . . . . . . . . . . . . . . . . . . 7-7Persons . . . . . . . . . . . . . . . . . . . . . . . 6-1Prerequisites . . . . . . . . . . . . . . . . . . . 1-2Roles . . . . . . . . . . . . . . . . . . . . . . . . 4-1Sites . . . . . . . . . . . . . . . . . . . . . . . . . 2-1Structure . . . . . . . . . . . . . . . . . . . . 1-10Users . . . . . . . . . . . . . . . . . . . . . . . . 7-1Volumes . . . . . . . . . . . . . . . . . . . . . . 3-1

Organization List tree . . . . . . . . . . . . . . 1-3Organization tree . . . . . . . . . . . . . . . . . 1-3

PParent groupsCreating . . . . . . . . . . . . . . . . . . . . . . 5-6Definition . . . . . . . . . . . . . . . . . . . . . 5-8

PasswordsExamples . . . . . . . . . . . . . . . . . . . . . 7-7Restrictions . . . . . . . . . . . . . . . . . . . . 7-7

Persons . . . . . . . . . . . . . . . . . . . . . . . . 6-1Creating . . . . . . . . . . . . . . . . . . . . . . 6-1Definition . . . . . . . . . . . . . . . . . . . . . 1-7Deleting . . . . . . . . . . . . . . . . . . . . . . 6-3Exporting . . . . . . . . . . . . . . . . . . . . 1-17Externally managed . . . . . . . . . . . . . 7-12Modifying . . . . . . . . . . . . . . . . . . . . . 6-2

PerspectivesIn general . . . . . . . . . . . . . . . . . . . . . 1-5

PreferencesTC_Volume_Failover_Trigger . . . . . . . 3-8TC_Volume_Failover_Volume_

Name . . . . . . . . . . . . . . . . . . . . . . 3-8TC_Volume_Status_Resync_

Interval . . . . . . . . . . . . . . . . . . . . 3-8Prerequisites for Organization . . . . . . . . 1-2

RReallocating volume data . . . . . . . . . . . . 3-7Reloading the Organization tree . . . . . . . 1-4RemovingDisciplines from a group . . . . . . . . . . . 9-3Members from groups . . . . . . . . . . . . 5-10

Revoking volume access . . . . . . . . . . . . . 3-7Rich client perspectives and views . . . . . 1-5Roles . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1Adding existing . . . . . . . . . . . . . . . . . 4-3Adding new . . . . . . . . . . . . . . . . . . . . 4-4Creating . . . . . . . . . . . . . . . . . . . . . . 4-2Default . . . . . . . . . . . . . . . . . . . . . . . 4-4Definition . . . . . . . . . . . . . . . . . . . . . 1-6Deleting . . . . . . . . . . . . . . . . . . . . . . 4-2Exporting . . . . . . . . . . . . . . . . . . . . 1-17

Externally managed . . . . . . . . . . . . . 7-12Modifying . . . . . . . . . . . . . . . . . . . . . 4-2Setting default . . . . . . . . . . . . . . . . . . 4-4

SSchedule calendars . . . . . . . . . . . . . . . 10-1Schedule user calendars . . . . . . . . . . . 10-1Security, setting . . . . . . . . . . . . . . . . . 1-10SitesCreating . . . . . . . . . . . . . . . . . . . . . . 2-1Definition . . . . . . . . . . . . . . . . . . . . . 2-1Deleting . . . . . . . . . . . . . . . . . . . . . . 2-3Modifying . . . . . . . . . . . . . . . . . . . . . 2-3

Starting Organization . . . . . . . . . . . . . . 1-2Subgroups . . . . . . . . . . . . . . . . . . . . . . 5-2Adding existing groups . . . . . . . . . . . 5-12Adding new . . . . . . . . . . . . . . . . . . . 5-14Definition . . . . . . . . . . . . . . . . . . . . . 1-6

Suppressing display of inactive members ingroups . . . . . . . . . . . . . . . . . . . . 1-4, 5-11System administration group . . . . . . . . . 5-8system group . . . . . . . . . . . . . . . . . . . . 5-9

TTC_Volume_Failover_Trigger . . . . . . . . . 3-8TC_Volume_Failover_Volume_Name . . . . 3-8TC_Volume_Status_Resync_Interval . . . . 3-8

UUser calendars . . . . . . . . . . . . . . . . . . 10-1Creating . . . . . . . . . . . . . . . . . . . . . 10-2Modifying . . . . . . . . . . . . . . . . . . . . 10-3

User construct synchronization . . . . . . 7-12User status . . . . . . . . . . . . . . . . . . . . . 1-11Users . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1Activating account . . . . . . . . . . . . . . . 7-9Adding existing . . . . . . . . . . . . . . . . . 7-9Adding new . . . . . . . . . . . . . . . . . . . 7-11Changing status . . . . . . . . . . . . . . . . 7-8Creating . . . . . . . . . . . . . . . . . . . . . . 7-1Definition . . . . . . . . . . . . . . . . . . . . . 1-6Deleting . . . . . . . . . . . . . . . . . . . . . . 7-6Exporting . . . . . . . . . . . . . . . . . . . . 1-17Externally managed . . . . . . . . . . . . . 7-12Inactivating account . . . . . . . . . . . . . . 7-8Modifying . . . . . . . . . . . . . . . . . . . . . 7-5

Utilitiesglobal_transfer . . . . . . . . . . . . . . . . 5-11ldapsync . . . . . . . . . . . . . . . . . . . . . 7-12make_user . . . . . . . . . . . . . . . . . 1-7, 7-2move_volume_files . . . . . . . . . . . . 3-7–3-8

PLM00029 J Organization Guide Index-3

Index

VVolume data, reallocating . . . . . . . . . . . 3-7Volumes . . . . . . . . . . . . . . . . . . . . . . . . 3-1Controlling access . . . . . . . . . . . . . . . 3-5Creating . . . . . . . . . . . . . . . . . . . . . . 3-2Definition . . . . . . . . . . . . . . . . . . . . . 3-1Deleting . . . . . . . . . . . . . . . . . . . . . . 3-5Granting access . . . . . . . . . . . . . . . . . 3-6Modifying location . . . . . . . . . . . . . . . 3-3Modifying properties . . . . . . . . . . . . . 3-4Reallocating data . . . . . . . . . . . . . . . . 3-7

Revoking access . . . . . . . . . . . . . . . . . 3-7

W

WizardsOrganization Group wizard . . . . . . . . 1-8,

5-12, 5-14Organization Role wizard . . . 1-8, 4-3–4-4Organization User wizard . . . . . . . . . 1-8,

6-1, 7-9, 7-11

Index-4 Organization Guide PLM00029 J

Documents

Teamcenter 10.1 Organization Guide - Help!help.aviacons.ru/tc10doc/PDF/en_US/tdocExt/pdf/organization.pdf · Proprietary and restricted rights notice This software and related documentation