nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

To import quantity information into the reliability of hardware architecture

medini_1056332009

Hi,

Is it possible import BOM with quantity metrics to the hardware architecture. As when i am impoting i am finding multiple components corresponding to quantity instead is it possible to see a component and quantity in the tabular editor using scripts.

Regards

Ratan

Find more posts tagged with

medini

medini legacy

Accepted answers

medini_1023909254

Hi Ratan,

it is highly recommended to use a BOM which is organized along the (unique) reference IDs and with quantity always set to 1 (i.e. for each RefID a separate line). Only in this way it is ensured that medini can enable an analysis in the FMEDA for the individual HW parts. Moreover, in this case also a subsequent update from a new version of the BOM can unambigously identify which elements have been added/removed/modified.

Usually all PCB design tools can generate a BOM in such a style if the appropriate settings are made. On the other side also the Excel PowerQuery feature can be used to split lines with multiple RefIDs into individual lines for each RefID

Best regards

Eckhardt

All comments

medini_1059007410

Hi Ratan,

Getting the quantity into medini as a profile property is possible without script:

When importing the BOM, import the parts' quantity (can be a decimal number) as/into the profile property "user_quantity"

* Note: During import, just type (or select) the profile property name into the header cell

If you want to use it in the reliability calculation, you can use the quantity information from a variable (at a part, Properties tab "Prediction") in a scaling expression. The scaling expression cannot use profile properties, so one would have to transfer the quantity from there to the variable. To automate this, you could use such a script:

Note: The script assumes to be in a sub-folder of the scripts folder (otherwise adjust the "load" commands for the libs), with the (up-to-date) libraries being in scripts/.lib.

// $EXPERIMENTAL$ $STRICT_MODE$ $WARNING_AS_ERROR$
/*
 * Copyright (c) 2021 ANSYS inc
 * All rights reserved.
 * 
 * The script is provided "as is" without warranty of any kind. 
 * ANSYS medini Technologies AG disclaims all warranties, either express or implied, 
 * including the warranties of merchantability and fitness for a particular purpose.
 * 
 * v2021-05-26 - initial version
 * v2021-06-16 - fix default quantity to "1.0" to cope with blocks in parts collections
 *
 * This script is intended to post-process a BOM import, to use the parts quantity (immported as profile property) within failure rate calculation.
 * USAGE: 
 * 1) When importing the BOM, import the parts' quantity (can be a decimal number) as/into the profile property "user_quantity"
 * Note: During import, just type (or select) the profile property name into the header cell
 * 2) Select the System/Function Model and execute this script via context menu
 * Note: For each part's "Prediction", the variable "quantity" and the "Scaling" formula will be overwritten!
 * 3) As a result the part's "failure rate" will be calculated by multiplying the part's "raw failure rate" (e.g. user defined or from a catalogue) by the part's quantity
 * 
 * SCRIPT LOGIC:
 * For each part in selected System/Function Model
 * - Find or create variable "quantity" and set it to the value of the profile property
 * - Set scaling formula to "failureRate = rawFailureRate * quantity;"
 * 
 */

load("../.lib/factory.js");
load("../.lib/finderEx.js");

console.log("=== START: Post-process Part Quantity in Prediction");
//check if selection is a fitting package
if (selection && selection[0] instanceof Metamodel.sysml.SysMLContainerPackage) {
 var p = selection[0];
 //console.log("Package prototype: {0}",p.prototype);
 //for each contained element...
 console.log("Found Elements: {0}",p.the_owned_elements.size());

 if (confirm("Do you want to process all items in this package?\nFor each part's 'Prediction', the variable 'quantity' and the 'Scaling' formula will be overwritten!")) {
 progressMonitor.beginTask("Processing parts", p.the_owned_elements.size());

 p.the_owned_elements.toArray().forEach(function (part) {
 //console.log("Part prototype: {0}",part.prototype);
 //...but only if actually a part
 if (part instanceof Metamodel.sysml.SysMLPart) {
 console.log("Part name: {0}",part.name);
 //Find or create variable "quantity" and set it to the value of the profile property
 var q = findOrCreateVariable(part, "quantity");
 //If user created blocks out of imported BOM before running this script, user_quantity might not exist or be empty. In that case use 1.0.
 if (part.user_quantity){
 q.value = part.user_quantity.replace(',', '.').trim();
 } else {
 part.user_quantity = "1.0";
 }
 //Set scaling formula to "failureRate = rawFailureRate * quantity;" - do this as 2nd step, as variable find/create ensures existence of "failureRateData"
 part.failureRateData.scaling = "failureRate = rawFailureRate * quantity;";
 }
 progressMonitor.worked(1);
 });
 alert("Done. Please re-calculate failure rates (in any of the parts).");
 }
}
console.log("=== STOP: Post-process Part Quantity in Prediction");

Does that help?

Regards,

Nils

medini_1023909254

Hi Ratan,

Best regards

Eckhardt

medini_1059007410

Hi Ratan,

Just to put Eckhardt's and my answer in context: The standard way and probably the way most automotive companies want and should apply is the one Eckhardt described. It's also explained in the general (ISO26262 focused) training session 7.

The script solution I provided is more for special purposes outside of automotive (e.g. calculation of general reliability calculations, without further detailed analysis), and is not well suited for maintaining an architecture model, which is supposed to be used for further FMEA/FMEDA work.

Regards,

Nils

medini_1059007410

Hi,

update of the script, so that it not only finds top level elements, but all - even in lower hierarchy levels, e.g. after applying "Restructure HW Model.js".

Happy Scripting,

Nils

medini_1059007410

Another smaller update