Administrator
User Guide
AVEVA E3D™ Databases : AVEVA E3D™ Project Structure
All the information about the databases in an AVEVA E3D™ project is held in a Project Directory. A project is identified by a three-character code. For example, the sample project supplied with the product is SAM. There are other directories associated with every project which store inter-database connection macros, DRAFT picture files and ISODRAFT files. The structure of a Project Directory and the naming convention for the other files are shown below, using SAM as an example.
|
Note:
|
This example shows the AVEVA Solutions naming conventions for the directories. You can name them according to your own conventions, as long as the environment variables are correctly set. You cannot control the filenames: they will always be of the format prjnnnn, where prj is the project code, except that you can specify the filenumber (the nnnn part of the filename), refer to Creating Databases.
|
|
The SYSTEM database
|
|
|
The COMMS database
|
|
|
The MISC database
|
|
|
sam001 - samnnnn
|
Databases files which contain the actual model data. nnnn has a maximum of 255000, but numbers 7001 - 10000 and 250001 - 255000 are reserved for use by AVEVA Solutions.
|
|
The project-specific defaults directory. For more information about the DFLTS directory, refer to AVEVA Everthing3D™ Installation Guide.
|
Project environment variables must be set to the project directories. For the sample project, the environment variables are set in the supplied evars.bat file.
This is the default setting, but is user definable on installation. Refer to Setting Up a New Project for further information.
