Data Models for Designer Central

This section provides the data models for Designer Central.

The following topics are discussed:

Type Hierarchy

This figure shows the type hierarchy for CAD Model using in Designer Central. The children of MCAD Model are shown in the next figure.



This figure shows the type hierarchy for MCAD Model:



To support the Revision/Versioning function, separate base types are installed for versions. This graphic shows the type hierarchy for CAD Drawing:



Version Data Model

This figure shows an example data model for versioning, where the revision stream has been finalized:



In this example, the A Revision is the major object, and the A.0, A.1, and A.2 are versioned minor objects. All of the version are connected to the major object using the VersionOf relationship. Because A.2 is the most current version, it is also connected using the Latest Verison and Active Version relationships. In addition, A.2 was selected as the finalized version and is connected using the Finalized relationship.

Integration-Specific Relationships

Each integration can define relationships between designs and other objects. The Integration Exchange Framework supports these relationship classes:


  • AssemblyLike


  • FamilyLike


  • ExternalReferenceLike--Links between designs, but do not participate in the structure.
  • DerivedOutputLike--Derived output (for example, JT or jpeg) versions of a design are stored in a separate object and connected to the CAD object using the DerivedOutputLike relationship. Derived output objects do not get carried forward to subsequent versions.