Creating multiple views

Different users within an organization often need to view the structure of a product in different ways. For example, a designer may require a structure hierarchy that is organized by functional subsystem, while a manufacturing engineer may require a structure that reflects the manufacturing assembly process, to allow a better interface to an ERP system. These structures contain the same set of piece parts and represent the same overall physical part. It may therefore be possible to model the structures as different, independently modifiable views of the same assembly. The multiple views functionality allows you to model such structures in this way.

Note The creation of multiple views is discouraged for new Teamcenter deployments but continues to be supported for existing customers with successful deployments. Several possible alternatives to multiple views are available and require less maintenance of data. Multiple views You can also use multiple views if the different structures do not reference the same set of piece parts, for example, to model a spares structure that is derived from a design structure. You can also create multiple views to exchange data with ERP systems, particularly if are several manufacturing sites. The structures in the different view types are independent of each other—changes in one view type do not affect any others. If you intend to keep multiple views synchronized, you must do this manually using data generated by the Compare feature. You can apply access rights separately to each view type. Similarly, you can be submit each view separately to a release procedure. Typically, you employ a formal release process (for example, a change management procedure) to approve multiple views as consistent and valid before they are released and locked against change.

Note Teamcenter does not attach any semantic significance to specific view types. However, it is good practice for the name of each view type to reflect its function or purpose.