DriveWorks Pro Concept: File Naming

naming is an important consideration when planning an implementation, and
DriveWorks affords complete flexibility in how files are named. This article
describes how files get named in DriveWorks, and how the names you choose
interact with the concept of alternatives and driven alternatives so that you
can build up libraries of parts that can be used again and again without
needing to be generated for each specification that is generated.

Simple File Names (Suffixed)

decides file names for models in a very simple way, for example, if we have the
following assembly stucture and file name rules:

  • MyAssembly [=DWSpecificationId]
    • MyPart1 [=DWSpecificationId]
    • MyPart2 [=DWSpecificationId]

DriveWorks will generate a new assembly and parts for a specification numbered
8, as follows:

  • MyAssembly8
    • MyPart1 8
    • MyPart2 8

Absolute File Names

It is
also possible to tell DriveWorks not to use the original file name at all, for

  • MyAssembly [="*A-"
    & DWSpecificationId]
    • MyPart1 [="*P1-"
      & DWSpecificationId]
    • MyPart2 [="*P2-"
      & DWSpecificationId]

create the following for a specification numbered 8:

  • A-8
    • P1-8
    • P2-8

Prefixed File Names

other possibility is to tell DriveWorks to use the result of the rule as a
prefix, for example:

  • MyAssembly [="*"
    & DWSpecificationId & "*"]
    • MyPart1 [="*" &
      DWSpecificationId & "*"]
    • MyPart2 [="*" &
      DWSpecificationId & "*"]

create the following for a specification numbered 8:

  • 8 MyAssembly
    • 8 MyPart
    • 8 MyPart

If you
have any questions about this process, or need any further assistance in
accessing your license keys – just visit the DriveWorks Pro Helpfile
or email us and we will be able to help you out! 

Jim TeDesco
Marketing Manager
Computer Aided Technology, Inc. 

  • Share this
Find Your Design Solution in the CATI Store.
Browse Products