About Setting Uniqueness Level for Windchill Objects
Uniqueness level provides a mechanism to configure or manage the uniqueness of objects in your Windchill solution according to business requirements. The uniqueness of an object is determined by combination of Object key, Organization reference and Namespace.
You can set uniqueness level in Windchill either at site level or organization level during installation or upgrade. Organization level uniqueness is applicable for object numbers only, object name or file name is not supported.
Organization Level Uniqueness
Setting uniqueness at organization level provides the ability to support multiple business units within a single company to operate independently from one another with a single Windchill instance. Since the business units operate independently, the single company can have duplicate object numbers across its organizations.
For example, there are three different business unitsor organizationsOrg1, Org2 and Org3 within a company or site. Users can create parts with duplicate identities across the organizations because each of these organizations is unique by themselves. Which means, apart with number say, 000001 can exist in two different organizations Org1 and Org2 respectively.
Organization level uniqueness applies to container owned object types like WTpart, WTDocument, EPMDocument, etc.
Supported Object Types
The Organization level uniqueness applies to following object types:
• WTPart
• WTDocument
• EPMDocument
• PromotionNotice
• WTWorkSet
• WTVariance
• WTChangeRequest2
• WTChangeProposal
• WTChangeOrder2
• WTChangeIssue
• WTChangeInvestigation
• WTChangeActivity2
• WTAnalysisActivity
• ProductFamily
• ProductModelGroup
• ProductModel
• PartList
• MPMMfgProcess
• MPMControlCharacteristic
• MPMMfgStandardGroup
• MPMProcessPlan
• MPMOperation
• MPMSequence
• VariantSpec
• WTPartAlternateRep
• WorkPackage
Site Level Uniqueness
Setting uniqueness at site level provides the ability to use a single Windchill instance to represent the entire company. Since the single Windchill instance represents the entire company, the single business unit has to have a standardized single numbering sequence across the site. Every part number created will be unique across the site or company.
In this case the default organization is set as the owning organization for the created objects. Unless additional organizations need to be created to represent internal or external organizations (vendor or supplier).For example, there are three different organizations Org1, Org2 and Org3. Users can create parts that are unique across the site or company with default organization as the organization reference.So whena part with number 000001 is created, the part number will be unique at site level, that is unique across the entire Windchill system. The same part number cannot exist in two or more different organizations say Org1 and Org2 respectively
If you want to change the uniqueness from site level to organization level, it can be done while upgrading or migration. For more information, see
Configuring Uniqueness Level in
Windchill Upgrade Guide .