Design Conventions
for Catalogues and Specifications
About This Guide
: Purpose of the Guide
Purpose of the Guide
Although in principle you have a lot of flexibility in the ways in which you can construct the database hierarchy for Catalogues and Specifications, in practice it is very important that you follow strict conventions within any given project to make sure complete compatibility of all data within that project. Further, unless there are exceptional reasons for not doing so, it is sensible to adopt common conventions for structuring all AVEVA E3D™ databases within your company, thus simplifying the exchange of data between projects.
If you intend to use the standard applications for building Catalogue databases (using PARAGON) and for accessing those databases during the Plant Design process (using MODEL), it is important that your data structures are compatible with those expected by the application macros. If this is not so, the transfer of information to and from the databases might not work successfully and the applications could fail.
This guide explains, with some examples, the essential features of the conventions used in building up the Catalogues and Specifications which are supplied by AVEVA. You must follow these conventions in your own Catalogues and Specifications if you want the standard AVEVA applications to work reliably with your data. In particular, some parts of the Catalogue database have been used to store information which is essential for the successful use of some design applications but which is not obvious catalogue data by the conventional definitions; for example, the Hangers and Supports application uses data stored in user-defined attributes in the Catalogues and Specifications to access associated information needed by the application.
1974 to current year.
AVEVA Solutions Limited and its subsidiaries. All rights reserved.
