Modify custom FMEDA column during BOM import for changed components

Question

Dear scripting community,
I'm currently struggling with an "FMEDA completeness report" for our management.
As our management wants to have an overview about the FMEDA status we have introduced a new column with a drop down menue so the engineer can set the state of a component to, for example [new, in discussion, reviewed]. 
As the default is "new" each new component that is added during a BOM update is flagged as new. A script or report can then calculate the percentage of completed components but changed component remain in their state and are falsly reported as completed.
We have about 1300 components in our BOM and update them with every hardware release. Manually generating a delta BOM and changeing the state is boring and error prone.
Medini does analyse the BOM during update and identifies new, changed and deleted components. We would like to have a kind of hook at the BOM import to execute a script for each changed BOM item so that the property is set to a given value. Clearing or resetting to its inital state would also be fine.

medini_1024169437 · Answer

Hi Dominik,

I now prepared a simple eample that matches your use case but only contains the bare minimum. Let me explain how it works:

- at project level it has a profile flag to enable ro disable the observation completely:

- there is a sample system model, each part has a boolean flag "needs review", I decided for boolean to keep it simple but anything else should work too

- if the failure rate is now changed in the Prediction tab, the flag is set to true

- same happens if you update from the BOM

- the magic is done by a so called hook script that is listening for changes on the failure rate attribute

- if a change come sin, it checks for the global flag and if set, makes sure the needs review flag is set

- chekc the script and you see how its working

- it basically needs to register for classes and features to observe

- it needs to return "undefined" to not do anything or a function to execute further modifications in the transaction

Here is the MPRX. Note that this is a very powerful but risky feature! It is intentionally not documented as well but  I think you can work your way through.

Make sure you work in debug mode as any problem with the hook script is logged to the console but otherwise silently ignored and not shown to normal users.

Happy Power Scripting

Jan

medini_1072013307 · Answer

No, I still need help on this.

Thanks

Dominik

medini_1024169437 · Answer

So Dominik, you managed to implement your own solution or still looking for some help here?

Happy Scripting

Jan