Analyses as Resources

Forward

Analyses in XFMEA and RCM++ are now reusable object references. More specifically the following analyses can be cast as objects:

• FMEAs
• Risk Discovery
• ...

Linked FMEA Illustration

To illustrate the concept/application, consider the two systems, Widget and Fidget, along with their corresponding system hierarchies, as shown below (using metasyntactic variables for names).

Widget Waldo Wibble [Wibble FMEA] Lidget [Lidget FMEA] Foobar Foo [Foo FMEA] Bar [Bar FMEA]

Fidget Garply Flob [Flob FMEA] Baz [Baz FMEA] Fubar Fu [Fu FMEA] Bar [Bar FMEA]

Then:

• The Widget is made up by the Waldo and Foobar subsystems and their associated lower level items as shown.
  • Furthermore, assume that an FMEA analysis was done at the lower level items.
• The Fidget system is made up of the Garply and Fubar subsystems.
  • Note that in this case both FooBar and Fubar subsystems share a common lower level item, Bar.

Since both the Widget|Foobar|Bar (oBar)and the Fidget|Fubar|Bar (uBar)one could (assuming no other stress/operational/interface/... differences) use the same FMEA for both. In this case they can be linked.

When linking FMEA or other analysis items:

1. A source needs to be defined. In this case if I am linking uBar to the existing oBar, oBar becomes the source and uBar is the link.
2. Changes/Edits can only be made to the source.
3. Sources can be any analyses in the same project, or any analyses in a Template project.
4. Template level permissions and security applies, and similar rules exist as with any other resource in Synthesis.

Basis, Impact & Discussion

Basis for Modification	Use.
Impact on V8/V9 Users	Impact
Discussion	Comment on this feature, or discuss it in the Synthesis Discussion area of our Discussion Forums.
These pages are not intended to replace, or be used in-lieu of the official software documentation. They are working/developments notes intended to facilitate communication between the user community and the development team. Features and specifications listed here are for discussion purposes and their final implementation in may be different than the specifications presented here.