Using Catalogs

This task gives an overview of how catalogs must be stored and used in ENOVIA.
1. Catalogs that are stored in ENOVIA must point to parts that are resolved. This means that no design table can be associated with them, and all values must be defined.
2. Only catalogs with descriptions that point to CATPart or CATProduct documents should be stored in ENOVIA. Catalogs with descriptions that point to text files must be kept on disk. Examples are design rules and standards catalogs.
3. The entire master catalog should not be stored as one entity. Users should divide their catalogs so that there are no more than about 500 parts for each catalog.

Users should create a separate catalog for each family  - gate valve, pipe with bends, etc. This is how the sample catalog provided with this application is organized. This type of organization is not only necessary to conserve memory resources, but is also easier to work with.

See Creating Sub-Catalogs to learn how you can do this.

Click here to see the list of resources that can be placed in ENOVIA.

4. When you are executing the Reconciliation command you should not have a .catalog document open in the CATIA session, or the command will fail.  For example, after placing equipment in a design document, the .catalog document (that refers to the equipment reference document) is still in the session and there is no way to unload it. In order to run the Reconciliation command successfully, you must first save the design document and exit the session. After that, you can start a new session, call up the saved design document and use the Reconciliation command.

aendtask.gif (1477 bytes)