Multi-Discipline Supports
Administrator Guide
Project Upgrade for MDS Defaults : Preliminary Requirements
|
•
|
The existing Project to be converted, via the MDS12 Defaults Conversion Upgrade utility, must already be operating at version 12 of AVEVA Plant/Marine.
|
|
•
|
The MDS administrator should make sure that the existing project is backed-up, copied and saved, prior to entering the project and running the MDS12 Defaults Conversion Upgrade utility.
|
|
•
|
The standard MDS12 appware version of the application files and projects must be installed and included into the evars search paths for the Project, PMLLIB and PMLUI in the batch entry files.
|
|
•
|
|
•
|
The MDS administrator responsible for running the MDS12 Defaults Conversion Upgrade utility MUST have WRITE access to the nominated PARAGON database. The nominated PARAGON database must be the first CATALOGUE database in list order of the selected MDB, but not necessarily the first database in the MDB.
|
|
•
|
The MDS administrator responsible for running the MDS12 Defaults Conversion Upgrade utility MUST be a member of the Project CATALOGUE Administration Team, CATADMIN or the Team Master.
|
|
•
|
A typical example for the MDS12 Defaults Conversion Upgrade utility evar setting required for the Version 12 project and MDS12 application defaults directory search path is shown below:
|
set <projectcode>dflts - which may be a search path and where the example working project <projectcode> = TWD, and where possibly the clients CORPORATE project code = COR, and <DL> = Drive Letter,
|
•
|
AVEVA recommend that the project PARAGON database to be used to store the converted MDS12 application default settings should only contain the eight MDS12 defaults CATALOGUE elements shown earlier in this document.
|
|
•
|
Using an independent PARAGON database to store the MDS12 defaults will simplify the process of including and/or excluding as a foreign database, copying a foreign database or reconfiguring the database into another project. The MDS12 master MDS project defaults CATALOGUE database is named MDS/MDSAPPDEFAULTS. The AVEVA Database Number is 7351 and the associated Database File Number is also 7351, i.e. /%MDS000%/mds7351.
|
|
•
|
The client MDS12 project defaults CATALOGUE databases should follow a similar naming convention, but including the three letter project code, e.g. for a project named "TWD", the local project MDS12 PARAGON CATALOGUE database should be named MDSTWD/MDSAPPDEFAULTS.
|
|
•
|
A typical client corporate project named "COR", the corporate project MDS12 PARAGON CATALOGUE database should be named MDSCOR/MDSAPPDEFAULTS.
|
|
•
|
However if the eight MDS12 project defaults CATALOGUE elements are to be included into another existing PARAGON CATALOGUE database along with other project specific CATALOGUE data, then this is also acceptable, but not recommended because of the reasons stated above.
|
