Database Types

A project consists of the complete collection of information which relates to a single design. The project is identified by a name, allocated by the project administrator when the project is first initiated. The project name is used to identify the project to the system whenever the user wants to work in the project using AVEVA E3D™ which allows access rights and use of system resources to be monitored and controlled. Refer to How AVEVA E3D™ Data is Stored and Access Rights for further information on these functions.

There are different types of database which can go to make up a complete project:

DESIGN and DRAW Databases

•

MODEL Database

•

PADD (DRAW) Database

MODEL Database

The MODEL (design) databases contain all information needed to create a full-scale three-dimensional representation of the project. For the compositions of the principal types of design element, refer Introduction for further information.

You are normally allowed to modify the design databases which relate to their function in the design team, and will often have permission to look at other design databases so that their work is compatible with that of other designers.

Typical design functions, each of which may use a different design database, include:

•

Equipment design (process vessels, storage vessels, pumps, heat exchangers and so on)

•

Pipework design (the interconnecting pipes between the various equipment items)

•

Structural design (the columns, beams, walls, stairways and so on which support and give access to the operational equipment and pipework)

•

Hangers and Supports (specialised pipe support structures).

PADD (DRAW) Database

The Production of Annotated and Dimensioned Drawings (PADD) database holds data about both the pictorial content of drawings and about their annotation and dimensional information. It therefore holds a complete specification of the contents of a drawing. Its use is specific to the interactive drawing module DRAW, refer to Introduction for further information. The data in a model database will often reference data in other types of database such as ISOD (Spooler) and 2D Design databases.

ISOD (Spooler) Database

The ISOD database holds pipework spool drawings generated by the SPOOL module, refer to Spooling for further information.

•

•

The SCHEMATIC databases contain the data and connectivity information relating to the 2D schematic model, together with cross-references to the schematic drawings related to this. The schematic data is normally created and modified by direct graphical interaction with the related schematic drawings.

ENGINEERING Database

The ENGINEERING databases contain the conventional engineering data pertinent to the design.

Reference Databases:

The Reference databases contain all reference information needed for a design and/or project.

CATALOGUE Database

The CATALOGUE database contains a catalogue of the standard components which the user may select when designing pipework, ducting, hangers and supports or structural steelwork. It includes:

•

Dimensional details for each component

•

Details of permissible connections between different components and of the bolts needed to assemble flanged components

•

Specifications of the components, which define the conditions of use for each type (maximum pressure, temperature etc.)

•

A CATALOGUE database may contain a single ‘universal’ catalogue, but it will more commonly contain a general catalogue plus one or more specialised catalogues specific to particular design functions. Refer to Work Area for further information.

LEXICON (Dictionary) Database

The DICTIONARY database holds the definitions of user defined attributes (UDA) and user defined element types (UDET). User defined elements types allow objects in a database to be given a user defined name to replace the generic name, for example an EQUI element can be called a :PUMP or :VESSEL. Additional information can be stored in user defined attributes assigned to database elements and extracted into drawings and reports.

PROPERTIES Database

PROPERTIES is available for storing data about material properties, which may be needed to supplement Catalogue and Specification data for some design functions such as stress analysis. Its use is specialised and will not be described further in this manual. Refer to Properties Constructor and XPRD databases for further information.

Project Common Database

XPRD cross product databases contains comments available to all products.

Administration Databases

The Administration databases contain all admin information needed for a design and/or project.

SYSTEM Database

There is only one SYSTEM database in each project folder, it holds administrative information about the composition and use of the project, including the following.

Each module requires access to one or more specific database types, and entry to the module may be prevented if appropriate databases do not exist or if you do not have the appropriate access rights. New databases can only be created by the Project Administrator.

•

A list of databases of all categories which are usable in the project

•

A list of all users, identified by name and password, who can legally access the databases, and the operating team(s) to which they are assigned

•

A list of AVEVA E3D™ modules available for use in the project

•

Access control data, which defines those databases which are accessible to any specific user and whether he may modify them or only look at them

COMMS Database

The COMMS database stores the information about who is using which module and which databases are current. You have a separate area of the COMMS database, which can be accessed in write mode, and so can record module changes etc. You have read access to the other users’ areas, and so can find out about other users in the project.

MISC Database

The MISC database is used to store inter-user messages, and inter-database macros. The MISC database can only be opened in write mode by one user at a time, but many users can read from it. All users need to be able to write to this database, but only when they are sending messages or writing inter-database macros, or deleting messages and macros. All users can read from the database at any time.

TRANSACTION Database

To enable the System Administrator to monitor the progress of Global commands, AVEVA E3D™. Global stores details of issued commands in a TRANSACTION database. Transaction messages are generated in the database each time the progress of the command changes.

•

Transaction databases are only present when the installation incorporates the Global product.