•Key contact list for organization administrators.

•Documents describing organization-level types, document templates, life cycle templates, and workflow process templates.

Managing Organization-level Types and Attributes

Organization administrators can create and modify subtypes and relationship constraints in the organization context; however, they cannot create or modify global attributes, units (quantities of measure and measurement systems), or global enumerations unless they are part of the Attribute Administrators group. You can use existing global attributes, units, and global enumerations created by the site administrator on types for your organization.

When subtypes and attributes are created within an organization context, they are kept separate from all other organizations and remain private.

For more information about types and attributes, see the help available from the

Type and Attribute Management utility.

Managing Organization Templates

An organization context can define a number of document, life cycle, and workflow process templates that can be used by all the application contexts within the organization. To ensure consistency and maximize efficiency, an organization may want to define templates for specifications, presentations, reports, proposals, meeting minutes, and so forth. Life cycle and workflow process templates may be associated with each of the defined templates. Each organization inherits the templates defined in the site and can either use these site-defined templates or override them by defining organization-specific templates with the same name.

The organization can inherit the product, library, project, and program templates defined at the site level, or you can override these templates by defining templates for your organization. If Windchill ProjectLink is installed, you can create project and program templates. If Windchill PDMLink is installed, you can create product and library templates. For more information, see Understanding Context Templates on page 393 .

You can restrict which templates are made available to the applications within your organization by choosing to hide certain templates at the organization level. By only hiding templates, you limit the templates displayed by default and still allow context managers to override which templates are hidden in their particular application context. If you want to prevent a template from being used, you can disable it.

For more information, see the help from Organizations Templates table.

Managing Organization-level Object Initialization

Rules

You can configure how attributes (such as number) are displayed and generated using the Object Initialization Rules Administration utility. This utility defines how the initial attribute values for the object are established, how the attributes are displayed, and can determine basic relationships, such as life cycle association, when an object is created.

The Object Initialization Rules Administration utility is available from the Site or Organizations Utilities page. The rules established by the parent site are inherited by each organization context by default, but they can be overridden at the organization level. The rules are defined in XML format; you can view and update them.

For more information, see the Object Initialization Rules chapter of the PTC Windchill Specialized Administration Guide.

Auditing Activities Within the Organization

The auditing framework allows the system to capture historical information of who did what that caused changes in the Windchill database. The security auditing feature also provides a mechanism to retain historical records of security related events, such as privilege changes, team changes, and denial of access. Security audit reporting is helpful in highly regulated industries where it is necessary to identify events that may have resulted in a potential security breach.

Out-of-the-box, only the Organization Usage events are enabled. Any other specific events that you want captured must be individually enabled by the site administrator.

For more information, see the PTC Windchill Specialized Administration Guide.

Creating and Managing Access Control Policy Rules

The Policy Administration utility is used to create access control policy rules. You can create organization-level policies that apply to the entire organization from

Organizations Utilities. To establish site-level policies, create those policies that apply to all organizations in the system from Site Utilities.

You can define policies that control the level of access to information by organization members. For example, you may want to provide read access to all documents of type Engineering Specification to an engineering group in your organization. In this case, you need to first define an Engineering user-defined group and populate it with the appropriate members, then define a document type of Engineering Specification in your organization. Finally, you need to use the Policy Administration utility to define the access policy based on the document type, the group or groups provided access, and the access level.

Viewing and Managing Access Control for Objects

You can view both the ad hoc and policy access control rules that are set for objects (such as folders, parts, and documents) and then manage the ad hoc access control rules for the objects. Navigate to the object, and select the Manage Security action. From the Manage Security window, you can view access control for the object and set ad hoc access control rules for the object.

For more information, see the PTC Windchill Specialized Administration Guide and the online help available from the Manage Security window.

Creating and Managing Profiles

You can dynamically control which actions are visible to user, or group of users, within your organization by associating that information with a profile. Profiles are not an access control mechanism; they are a user interface control mechanism. A profile represents a typical category of user within a company and is based on the roles and privileges associated with that particular user category.

Profiles expose only the necessary functionality and information needed by a user. They create a focused and simplified user interface, reducing confusion by eliminating areas of the user interface that could be distracting.

For more information about profiles, see Profile Management on page 290

Configuring Numbering and Versioning Schemes

You can configure the number and versioning schemes used to uniquely identify parts, documents, and other objects in the organization. The organization context inherits the site-level schemes, but can optionally define its own schemes. In general, when a company is hosting Windchill for its internal users, the numbering and versioning schemes should be defined at the site level; you should not override the site-level schemes by defining schemes at the organization level.

For more information about numbering, see Administering the Numbering of

Parts, Documents, CAD Documents, and Change Objects on page 104

Monitoring and Managing Viewable Publishing

You can monitor and manage the publishing of viewable files that are optionally generated when CAD models are checked into products, libraries, and projects. You can also configure and update the watermarks used by the visualization tool when viewing document and part content.

For more information, see the PTC Windchill Visualization Services Guide.

Viewing Reports

You can access several predefined reports for information contained within your organization.

For more information on available reporting functionality, see the online help available from Organizations Reports.

Importing and Exporting Information

You can exchange information with another server, or between servers, or between a server and a file system using the Windchill import/export utilities. These utilities read and write system information in the Windchill XML format. The workflow and life cycle administration utilities accessible to you integrate the import/export functions.

For more information, see Importing and Exporting Life Cycle Templates on page 326 and the help available from the Workflow, Template Administration utility.

Purging, Archiving, and Restoring Jobs

You can create and manage purge jobs with the Purge Management utility. If you have the applicable functionality installed, you can create purge jobs to permanently remove data from the Windchill system or create an archive of the data to restore at a later time. This would apply to viewing, restoring, and deleting the contents of projects and programs.

Managing Preferences

Using the Preference Management utility on the Organizations Utilities, you can manage preferences at the organization level. Preferences set at the organization level affect all application contexts and users within the organization. Some preference values can be overridden by application contexts within the organization, unless locked at the organization level.