Naming the Master Models

The name you give the master models will allow you or anyone else to easily identify rules that need to be applied or maintained going forward.

There are a few points to keep in mind: -

1. The name you give the top level assembly is used to identify the rule set.
2. Sub-assemblies and parts can be shared across multiple assemblies.
3. Models that need to be controlled independently must have different names.
4. The original name can be overridden for the new file that gets created.
5. Assemblies cannot have the same name as parts.
   

I'll explain some more about the other points in subsequent posts, for now I'll start with the first item.

Rule Set identification

This is critical if you have many products in the database. If your database just contains one product, clicking run from the welcome screen on the DriveWorksXpress wizard will take you straight to the inputs required to specify that product.

However, chances are you have more than one item that can be automated. The Lintel example on the DriveWorksXpress website shows a good use of descriptive naming of the top level assembly. Here we have 5 very different models that can be selected for automation. Each one has a clear name given to the top level assembly that helps the user select the most appropriate one for specifying.

Once selected the user forms and rule set to automate that product are loaded and can be ran to generate the new engineering data.