Catalogues and Specifications Reference Manual
Catalogue Database Structure : Principal Features of the Catalogue Database
Principal Features of the Catalogue Database
If a new Catalogue database (DB) is required, PARAGON can be used to construct it - see Manipulating the Catalogue Database using PARAGON for details of creating and manipulating a Catalogue DB using PARAGON.
The Catalogue 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 MODEL, 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 Catalogue Component (SCOM, SPRF, SJOI, SFIT, etc.) in the Catalogue (see Figure 4:1.: Interrelationship between Design Data, Catalogue and Specifications).
Whereas the Design data is specific to a particular MODEL, Catalogues and Specifications may be specific to a company but general to a number of projects in that company. For example, the same Catalogue Component may be referred to many times in a particular design and may also appear in other design projects proceeding at the same time.
Catalogues are usually built up as a library of catalogue macros. A selection of these macros can then be used to build up a project-specific Catalogue database containing only those Components which might be used on that project.
Figure 4:1.
Interrelationship between Design Data, Catalogue and Specifications
1974 to current year. AVEVA Solutions Limited and its subsidiaries. All rights reserved.
AVEVA Logo