Related Topics:

Importing from Prior Version Files

Converting MPC 3 Databases

If you have an existing systems and powerplant analysis that was created in MPC 3, it is easy to convert the *.rsm file into a new Synthesis repository.

Choose File > Open Repository, select MPC 3 (*.rsm) from the Files of type drop-down list, and then browse for the desired file.

When prompted to enter a username and password, enter the administrative login from the old *.rsm file.

Note: By default, a converted Version 3 database is a secure database that transfers any user accounts that were defined in the old database. After the new database has been created, the administrator should review the automatically created user accounts and update as appropriate. (See Security Options for more information about secure databases.)

The final step is to use the Tasks Conversion window to review the task records that will be imported and make any updates that may be needed (see details below). Once you have completed the review, click OK to start the import.

When the process completes, there will be a new standard database file in the same folder and with the same name as the original *.rsm file. The new file will have the extension *.rsr9 and the original *.rsm file will remain unchanged.

Tasks Conversion Window

The Tasks Conversion window displays a list of all of the tasks defined in the original database and allows you to review how the records will be converted upon import. For any properties that are displayed with blue text, you have the option to change the task record data before it is imported.

Some task properties are handled a bit differently in Version 9 than they were in Version 3. Specifically:

The following subsections describe the default conversion logic for Task Type, Interval and Zone.

Task Type

For the Discard and Restoration task types, there is no difference between Versions 3 and 9. The text in the Task Type (New Value) column will be displayed in italics to indicate that this property cannot be changed via the Tasks Conversion window.

For the remaining task types, the software will use the logic specified below to suggest a task type, but the property will be displayed in blue text to indicate that it can be edited. If you disagree with the default selection, you can choose one of the other eligible task types from the drop-down list, as shown in the following example.

If the task description contains:

The default option is to import the task as:

Visual

General Visual Inspection

Special Detail

Special Detailed Inspection

Health Monitor

Scheduled Structural Health Monitoring

Function

Functional Check

none of the words/phrases listed above

Detailed Inspection (DET)

 

Tip: The task types in MPC 9 are determined by the requirements of the MSG-3 guidelines and cannot be changed. However, the abbreviations can be configured to fit your particular preferences. If you want to change the default task type abbreviations (e.g., if you don’t want to use DIS for Discard, RST for Restoration, etc.), click the Task Type Abbreviations button. The changes that you make in the Define Task Type Abbreviations window will automatically apply to all analyses in the current database. This window is also accessible from File > Manage Repository > Task Types.

Interval Type and Interval

Two options are displayed at the top of the Tasks Conversion window to determine how the task intervals will be imported:

 

Tip: If you want to change the time units displayed in the drop-down list, click the Time Units button. The changes that you make in the Manage Units window will apply immediately to the tasks that you are currently importing, and also to all other analyses you may later add to this database. This window is also accessible from File > Manage Repository > Manage Units.

The Tasks Conversion window uses a variety of techniques to try to match the text field from Version 3 with one of the specified time units in Version 9. There will be a match if the name or abbreviation of a Version 9 time unit either starts with or contains the text in the Version 3 field. For some predefined time units, the software also recognizes other commonly used abbreviations for the time unit (e.g., the software will recognize any of the following abbreviations as flight hours: Flt/Hr, Flight H, Flt H or Flt/H).

If your data set contains a task interval that is not recognized, you can do any of the following:

Zonal Candidate and Zone

If all of the following conditions are met, the Zonal Candidate (New Value) column will be set to Yes by default and any information from the Zone field will be transferred during the import:

If you don’t want the task to be considered for zonal analysis even though it meets the requirements, you can click inside the Zonal Candidate (New Value) column and choose No from the drop-down list. If this column displays No in italics, this indicates that at least one of these conditions is not met and the property cannot be changed.

 

© 1992-2015. ReliaSoft Corporation. ALL RIGHTS RESERVED.