FIDES Settings Manager

The FIDES Settings Manager window allows authorized users to manage all of the predefined FIDES settings that are saved in the current database. These settings are shared by all users for all FIDES analyses in all projects within the current database. In a secure database, the ability to manage the settings will be accessible only if you have the "Manage Lambda Predict database settings" permission.

To access the window, choose File > Manage Database > FIDES Settings Manager.

The FIDES Settings Manager window provides a separate button for each type of FIDES setting that can be saved in the database. The options for managing these saved settings are discussed in the following sections:

• Manage FIDES Categories
• Manage Database Phases
• Manage Phase Sets
• Manage Pi Factors
• Entity Audits
• Process Audits

Tip: Authorized users can also modify these settings while working on a particular FIDES analysis in the prediction folio. For example, when you use the Select Pi Factor window to set a particular property in a FIDES analysis (and only if you have the "Manage other database settings" permission), you will have the opportunity to add, edit or delete any of the saved pi factors of that particular type. Likewise, you can access the Manage Database Phases window when you’re using the Item Phases and Select Phases windows to select the phases that will be used to define the life profile of a particular system or assembly.

If you wish to use some or all of the same saved FIDES settings in multiple databases, there are two options:

• Click the Import button to use the Import FIDES Settings window to copy specific settings from another existing database at any time.
• Click the Save as Default button to save the settings from the current database to a separate resource file (*.lpd) so they will be copied over each time you create a new database from this computer. (See Default FIDES Settings for New Databases.)

In both cases, it’s important to remember that the settings are copied between files but not linked, and therefore it does not automatically ensure that the settings in different databases will remain synchronized after changes are applied. If you wish to keep the settings synchronized among multiple databases, you will need to apply the changes in one database and then import them into all other applicable databases. If you’re using an *.lpd file to automatically populate the settings in each new database that you create, you will also need to save the latest settings into the active resource file.