Learning Forum

[conrado.serrano]

I am currently setting up an FMEDA workflow in ANSYS medini analyze and have a question regarding the automation of hardware part properties.

My goal is to avoid manually assigning failure rate categories (e.g., from SN 29500) to every individual component in my BOM. I would like to confirm the process for the following:

1. Part Library Integration: Can medini automatically populate 'Prediction' properties and FIT rates by matching the Manufacturer Part Number in my imported BOM against a pre-defined medini Part Library (.mpartlib)?

2. Import Configuration: Is there a specific configuration file or mapping rule I need to define so that the tool recognizes the Part Number as the unique identifier for the lookup?

3. Stress Data Propagation: If a component in the Part Library has defined stress parameters (e.g., power dissipation or voltage ratio), will these be automatically applied to the BOM instance upon import to calculate the final FIT?

Could you provide documentation or a sample template for a Part Library that demonstrates this automated lookup functionality?

[Madhu Kiran Kovoor]

Hello,

1) yes it is possible in Medini to auto populate predition and FIT rates based on Part Number. For this you need to build a part library.

• Go to Help >> Example >> HW library 
• Click file, new project "Project name" >> select HW library template
• Navigate to Libraries >> HW Part Library
• Create new library project
• Right click >> import BOM from excel >> select "Import type definitions" >> click next
• Select BOM excel
• Select work sheet
• Create mapping by clicking >> select partnumber for the column in your sheet consisting of partnumbers, and element kind for type of components
• after importing components, sort the components through a predefined script " right click on library >> execute >> restructure hw library model

2) Mapping rule is explained in point 1

3) The stress propagation and how it is used always depends on the failure rate catalogue. SN 29500 focusses mainly on the internal working cycles of the mission profile and requires to set the delta ambient and self increase to derived if you want to use the stress from mission profile at library element and instance. A mission profile can be assigned at multiple levels in your model and will be taken into account following the rule the closest mission profile wins and this can also be the one assigned to one model. The ambient temperature can also be set to derived if added to a structuring container and propargated to its children. IEC 62380 does need any derived setting of the values. It also uses Working Phases and Internal Working cycles. So in every case it depends highly on the use case and selection of failure rate catalogues.