Out-of-the-box Product and Library Context Templates
When Windchill PDMLink is installed, the following product and library templates are loaded:
Product Design -- This template provides a demonstration of how to setup a product context for use with the One Phase Development and Two Phase Development life cycle templates and state-based versioning. As described in detail later in this section, the default set of roles defined is Members, Promotion Reviewers, Promotion Approvers, Collaboration Manager, Variance Approvers, Marketing, Procurement Engineer, Designer, Quality Engineer, Manufacturing Engineer, Design Team Leader, Option Administrator, Package Creator, Change Review Board, Change Admin I, Change Admin II, Change Admin III, and Received Delivery Manager. Also, the Guests and Product Manager roles are created automatically. Some basic information about these roles is as follows:
The Members role is used as a basic role to grant context team membership. A set of access rules are defined for confirmed members of the context team.
The Designer and Design Team Leader roles are unique to this template and identify the people who are responsible for creating and maintaining the business objects used to design a product.
Additionally, there are marketing and engineering roles that are unique to this template that can be used to delineate those functions in the design process.
Access policies defined for Change Objects have been setup to work in conjunction with the closed-loop change process.
Members of the Guest role are granted Read access to all objects.
General Product and General Library -- These templates provide examples of how to setup basic access control for a general product or library context. As described in detail later in this section, the default set of roles defined is Members, Promotion Reviewers, Collaboration Manager, Variance Approvers, Promotion Approvers, Option Administrator, Package Creator, Change Review Board, Change Admin I, Change Admin II, Change Admin III, and Received Delivery Manager. Also, the Guests and Product/Library Manager roles are created automatically. Some basic information about these roles is a follows:
The Members role is used as a basic role to grant context team membership. A set of access rules are defined for confirmed members of the context team.
Access policies defined for Change Objects have been setup to work in conjunction with the closed-loop change process.
Members of the Guest role are granted Read access to all objects.
The product and library templates can define the same basic information that is discussed in Context Administrative Items. If you want to create a new product or library template, see Understanding Context Templates.
When users are working primarily with dynamic documents, you can start with the context template that is closest to your business model and modify the product or library that you create to meet your needs. For some general guidelines on administrative activities that you should consider doing, see Configuring Products or Libraries for Dynamic Documents.
Было ли это полезно?