Principal Features of the Catalog Database

If a new Catalog database (DB) is required, PARAGON can be used to construct it. See Manipulating the Catalog Database using PARAGON for further information on creating and manipulating a Catalog DB using PARAGON.

The Catalog data is held according to a strict hierarchy which is similar in form to that of the Design data.

When a Component is selected by the designer using Design, a Specification Reference (SPREF) is identified and held in the Design database. The SPREF points to a Specification Component (SPCOM) in the Specification. This in turn points to a Catalog Component (SCOM, SPRF, SJOI, SFIT, ) in the Catalog (refer to the Interrelationship between Design Data, Catalog and Specifications image).

Whereas the Design data is specific to a particular Design, Catalogs and Specifications may be specific to a company but general to a number of projects in that company. For example, the same Catalog Component may be referred to many times in a particular design and may also appear in other design projects proceeding at the same time.

Catalogs are usually built up as a library of catalog macros. A selection of these macros can then be used to build up a project-specific Catalog database containing only those Components which might be used on that project.

Interrelationship between Design Data, Catalog and Specifications