Related Topics:

Configurable Settings

Converting Configurable Settings from Version 5

When you convert an existing library profile from Xfmea/RCM++ 5, the application will add new configurable settings for new features that were added in the Synthesis version. Likewise, when you convert an existing project, its configurable settings will be updated in the same way.

Here is a summary of the settings that will be added, modified or changed:

Setting Type

Page

Comments

Interface

FMEA > Functions

New Op Seq Number field, which can be used to add a reference number to a function. In synchronized worksheets, the op seq number is also used to link a function to a particular item in the associated PDF worksheet or Control Plan worksheet.

 

Tasks > Properties (RCM specific)

Many of the properties that were in the FMEA > Tasks page are now configured as part of the task resources. (See Task Properties.)

The task properties that apply only in RCM++/RBI can be configured via the new Tasks > Properties (RCM specific) page.

 

FMEA > Sync Options

New options for creating FMEA functions from system hierarchy items or PFD worksheet operations.

 

FMEA > Criticality

The Probability of Loss field was removed and is now generated from the FMRA.

 

Control Plan > Sync Options

New options for synchronizing from the PFD Worksheet.

 

DVP&R > Sync Options

New options for separately synchronizing controls and actions.

 

PFD Worksheet

Added properties for the new PFD Worksheet functionality.

Occurrence Scale

Properties

New Quantitative Value column and options for automatically creating failure models based on the RPN occurrence ratings.

Task Logic

Properties

Some of the task properties were removed because they are now part of the task resources.

DFR Planner Templates

Properties

Added templates for the new DFR Planner functionality.

 

Upon conversion, the application will apply default values for all of the new settings. It is important to note that these defaults may need to be modified after the conversion if you plan to use the Quantitative Value setting in the FMRA calculations for the converted project. This is because the application is not able to interpret the numerical thresholds (if any) recorded in the Criteria descriptions, and therefore it must apply the same values for all converted rating scales.

For example, the following table shows part of the occurrence scale from the "DFMEA: AIAG-4" profile. As you can see, the default values that would be applied if you convert this rating scale from Version 5 would need to be changed to more appropriate values that match the thresholds specified in the text descriptions. For example, 1 in 1,000,000 vehicles is 0.000001, and so on.

Rating

Criteria

Quantitative Value

These are the values that will be applied to all scales by default upon conversion.

These are more appropriate values that match the criteria in this particular scale.

1 - Very Low

Failure is eliminated through preventive control.

0.000001

0.0000001

2 - Low

<=0.001 per thousand items/vehicles, 1 in 1,000,000

0.000010

0.000001

3 - Low

0.01 per thousand items/vehicles, 1 in 100,000

0.000100

0.000010

...

10 - Very High

=> 100 per thousand items/vehicles, => 1 in 10

0.900000

0.100000

 

When feasible, the most efficient and consistent way to apply these updates is to first obtain a fully updated profile in the Profiles/Library Manager and then use this profile to re-apply the settings for each converted project. Specifically, you will need to do the following:

  1. Decide which library you will use and then confirm that the new settings are fully updated for all active profiles in the library:

  2. Convert one or more existing projects from Version 5.

  3. For each converted project:

Of course, you also have the option to review and manually update the configurable settings for any particular project, if desired. These are accessible from the Configurable Settings pages in the Project Profiles window, and also from Project > Management > Configurable Settings.

 

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