FMEDA - Functional safety - ISSUES

• FSSetupMain
• Display either Renaming PI dialog or Create PI dialog:
• Using Ctrl+Left Arrow or Right Arrow does not tab between
words in Name field, but affects the underlying diagram.

• FSSetupMain
• Select Global on left, select Create PI, display Create PI dialog.
• Create several PIs: FMEDA-FTA Car, FMEDA-FTA Comp1 – FMEDA-FTA-Comp6, FMEDA-FTA Engine and FMEDA-FTA Carb.

• Select FMEDA-FTA Car on left, see FMEDA-FTA Car on right (in Item Element pullout), click on minus icon (Add/Remove Existing Item – Element) next to FMEDA-FTA Car.

• Add/Remove Existing Item-Element to the Element pops up in middle. It looks like the Elements after FMEDA-FTA Car are already under FMEDA-FTA Car, until you notice that the ones above it are indented as well. As a better user interface, remove the topic Element (FMEDA-FTA Car) from the hierarchy and put in a label above the tree with text such as Check components for Element FMEDA-FTA Car.

• When an Op Sit branch is created in the Op Sit table, the correct PI contains Op Sit ASI is created (See first red box below), but why are five ATI records with blank values created for the Id, Comment, Speed, Location and Road Conditions properties (See second red box below)? This is causing extra time that is not needed.

For example, in the table below, the three boxed items were selected from the dropdown and then changed, but the Description saved was still the original value I selected. Also, the Description field in the display is not updated, making it so the user doesn’t even know it’s being saved in the DB.

Issue 5 – Malfunction Associated Then Deleted Then Re-Associated

• Open HARA
• Adjust Exposure column width to be wider:

• Open FSR
• DSeg created at Global level (Cxt=1079) that should NOT be created. This at least accounts for one of probably many places where this is occurring. Current DB I got from Biju had 48 of these Global DSegs, all included in Global’s Design Segment Map.

• Open FSR
• Add DReqt in branch

Multiple VOC Numbering Schemes are getting created in RTree for PatternType=1 (VOC). There should only be one NumScm PatternType for a given PI. I can’t tell exactly when they are created, but I was working in RTree, creating flowdowns to new component DFuncs and DReqts when they occurred.

Just opening RTree for a new PI that hasn’t been opened in it yet creates a NumScm.
Expanding a DReqt to see its flowdowns causes another NumScm to be created. In fact, refreshing the RTree and then expanding a DReqt causes another NumScm to be created for the same PI and DReqt.

• Selected and expanded FMEDA-FTA Carb Element in dialog below.
• Clicked +F to add DFuncs.
• In new dialog, added a couple DFuncs and selected them and clicked Ok.

• Create DFunc, DReqt and DFail flowdowns in AQuAPro for FMEDA-FTA Carb.
• Open FTree, don’t see flowdown arrows:

After changing an OR Gate to an AND Gate:

Open TSR for FMEDA-FTA Car:
Select DFunc3 under FMEDA-FTA Comp1 in TSR:

1. Always open the most used PI.
2. Select a specific PI to always go to.
3. Don’t open any PI. After displaying a blank document or diagram, the user must then select a PI from left (Production Item) menu.

Multiple FMEDA Issues

Multiple FTA Issues

Note that values are saved in the DB, so if I re-edit the FM Dist values, what I entered are still there.

In the SRS, the sample Edit FM Dist dialog shows <Comp Name> which is a way to indicate that it should be replaced with the Comp Name’s Name:
So, the Edit FM Dist dialog at the top of this section should have a title of Edit FM Distribution Values for FF Carb Failures. Do not use () to enclose the component name and also leave a space after the word for.

And press the delete key to erase the value and then tab off the field, the Total Distribution is not recalculated. Even though the dialog recalculates when all fields contain a numeric value and a user tabs to another field, as soon as a blank is entered, recalculation does not occur.

Whenever an error or informatory message is to be displayed to the user, it should be displayed as a message box with an OK button and requires the user to press the OK button before doing any operation in the underlying window/dialog. This includes when a message is displayed from a dialog. This shows a message that is displayed when the OK button is pressed and FM Distribution is not 100:

Whenever an error or informatory message is to be displayed to the user, it should be displayed as a message box with an OK button and requires the user to press the OK button before doing any operation in the underlying window/dialog. This includes when a message is displayed from a dialog. This shows a message that is displayed when the OK button is pressed and FM Distribution is not 100:

9/07 Error or Informatory Messages to the User - Open
Whenever an error or informatory message is to be displayed to the user, it should be displayed as a message box with an OK button and requires the user to press the OK button before doing any operation in the underlying window/dialog. This includes when a message is displayed from a dialog. This shows a message that is displayed when the OK button is pressed and FM Distribution is not 100:

Display Add Probability dialog for a DFailU/DFail.
When two or more safety mechanisms are displayed in the listbox at the bottom, the OK and Cancel buttons are shifted down and no longer available:

You can see the OK and Cancel buttons getting shifted down, which should not happen:

I check PCM2 and PCM5 and leave PCM3 checked:

And press OK.

ALL 6 PCM-SMs get included in the DFMEA and therefore appear in the Add Probability dialog (see below). The current SMs section has been photoshopped to show all 7 PCM-SMs.

As described in the SRS, the state of the PCM-SMs can change between one display of the dialog and the next. But, it can also change after pressing the Add button or the Delete button. The SAME logic should apply, since the number of PCM-SMs is changing in all of these cases. Here is the part of the SRS that describes this:

Note that the state of the PCM-SMs can change between one display of the dialog and the next. The only difference between opening the dialog for the first time and subsequent times is that there could be DFailU/DCauU properties after the first time. FTA0920: So, based on their existence and validity, do the following for the checkbox and textbox fields when opening the dialog:
If there are valid DFailU/DCauU property values then
If #PCM-SMs >= 1 then
Enable SM Name and Diag Cov fields
Display DFailU/DCauU properties in the fields
Don’t check the checkbox
Else
Delete DFailU/DCauU properties
Don’t check the checkbox
Else
Delete DFailU/DCauU properties, if any (could be invalid –
one property but not the other or Diag Cov not valid)
If #PCM-SMs = 0 then
Disable SM Name and Diag Cov fields
Don’t check the checkbox
Else If #PCM-SMs = 1 then
Disable SM Name and Diag Cov fields
Display PCM-SM properties in the fields
Check the checkbox
Else If #PCM-SMs >= 2 then
Enable SM Name and Diag Cov fields
Don’t check the checkbox

Since this dialog saves data to the DB (such as the Edit SM Dist values) and the Add/Delete PCM-SMs, the Cancel button should be renamed to Close, since Cancel implies the user can cancel all actions done in the dialog and this is not true. The different, then, between OK and Close will be that OK will do the required verifications (such as making sure FM Dist = 100), whereas Close means close the dialog without verifications.

This has been mentioned, but not officially added here: OR Gates should appear as this symbol: , with the text inside of it and AND Gates should appear as this symbol: with the text inside of it.