About revision rules

Teamcenter's revision rules help business users configure product structure by selecting the specific item revisions. Privileged users and administrators can set up the revision rules by defining criteria for selecting specific item revisions. You can set up a revision by understanding how individual rule entries, each with specific parameters, determine which revision is loaded. You can learn the importance of entry precedence, how to group certain entries for equal precedence, and finally, how these rules enable effective management and configuration of product structures. A revision rule sets the criteria for selecting the appropriate revision of elements in a product structure. For example, users can choose whether to load working revisions or release revisions. As a privileged user (or an administrator), you set up revision rules by defining revision rule entries. Each rule entry defines a parameter that is used for evaluating which structure configuration must be loaded. The revision rule is evaluated based on the order of precedence of the rule entries. As soon as a revision is successfully configured, the rest of the rule entries are not evaluated. Therefore, you must set the order based on your site requirement. The different rule entries are: Revision rule entry Description Example Working It is used for loading the working item revision that do not have a release status. By default, the latest working revision is selected according to the date it was created. It can be made more specific by specifying an owing user and owning group. To load elements that John or Project X group are currently working on, you set up the revision rule as: Copy Working( Owning User = John ) Working( Owning Group = Project X) To load elements that belongs to the user currently logged on: Copy Working( Owning User = Current ) To load elements that belong to the group to which the user is currently logged on to: Copy Working( Owning Group = Current ) Status It is used for loading item revisions that are released with a specific status. It can be made more specific by specifying a specific status, release date, effective date, and effective unit number. To load the latest revision of elements as per their effective production date: Copy Has Status (Production, Configured by Effective Date ) To load the most recently released revision of elements that are either in the Production or Pre-Production state: Copy Has Status( Production, Configured by Date Released ) Has Status( Pre-Production, Configured by Date Released) Latest It is used for loading item revisions regardless of whether they are released or not. It can be made more specific by including the creation date, alphanumeric revision ID, numeric revision ID, and a combination of alpha and number revision IDs. To load the latest revisions of elements based on their creation date: Copy Latest( Creation Date ) To load the latest revisions of elements based on numeric revision ID: Copy Latest( Numeric Rev ID) Here, elements with non-numeric revision IDs are not loaded. Date It is used for loading item revision with a specific date. You can use this entry only with other entries. To load the latest revision of elements as on today: Copy Latest, today To load the latest revision of elements that are in Production as of 1-Jan-2007: Copy Has Status( Production, Release Date = 1-Jan-2007) Unit Number It is used in combination with the status rule entry with unit number effectivity. It is used for loading item revisions with a unit number as specified by the user. Typically, a unit number is a property of the end product or a major module of a product. As Teamcenter may manage many units, you typically qualify a unit number entry with an end item entry. To load the element revisions that are in Production based on a specific unit number: Copy Has Status( Production, Configured by Unit Number ) End item It is a product, system, or module with respect to which you configure a structure by effectivity. For example, you can configure the structure of unit number 110 in product X400, where X400 is the end item. Precise It is used for loading item revisions in a precise product structure. Override It is used for overriding all item revisions available in an override folder. The revision rule will not be evaluated for these item revisions. You can modify the order of the rule entries to change the precedence used when evaluating the revision rule. Certain rule entries can also be grouped so they are evaluated with equal precedence. In the case of status entries, you can group two or more different statuses with equal precedence. In the case of working entries, you can group different owners with equal precedence.

Example To load recently released revisions of structure elements irrespective of whether they are in the Production or Pre-Productions state, you group the status rule entry as follows: Copy [ Has Status( Production ), Configured by Date Released ) Has Status( Pre-Production, Configured by Date Released )] You can also group entries according to item type and occurrence type. Certain entries cannot be grouped together. The following are not valid combinations for grouping: Copy Latest Has Status, Configured By Release Date Copy Has Status( TCM Released ), Configured by EffectiveDate Has Status( Pending ), Configured by Release Date