Basic Administration > Managing Data > View Administration > Working with Views and View Associations
  
Working with Views and View Associations
Before a part can be assigned to a view, you must set up views and view associations for your Windchill system. A view can have many child views, but only one parent view.
Only the first view in the structure has no parent view. You can define only one such root view for your site. The following diagram provides an example of a typical view setup:
View-dependent versions of a part can be derived from parent views using the New View Version action. As shown in the diagram above, the Engineering view is the first view in the structure and is the parent of the Manufacturing view. Also, the Manufacturing view is the parent of the Facility 1, Facility 2, and Facility 3 views. Therefore, a Manufacturing version of the part can be built from the Engineering version of the part. Facility 1, Facility 2, and Facility 3 views can be derived from Manufacturing.
When a user creates a new view version of a part and it is the first version in the view, the new version begins a new version scheme. For example, if the Engineering version of a part is Revision B, the Manufacturing version of the part is labeled Revision A. Subsequent revisions of the Engineering version continue with Revision C, and so on. Subsequent revisions of the Manufacturing version or new view versions to the Manufacturing view continue with Revision B, and so on. Each view-dependent version of a part goes through its own life cycle process. For more information, see Out-of-the-Box Default Versioning Scheme.