Update Failure Mode

Question

Status : rejected  Priority : Major, #99     Schedule : (according to Project Owner)      Current state : Solved with script from Customer     Critisism on current state : Failure Mode Librarys are static this is not a typical use case and will not change, if you would like to create a script I would propose to create a separate script to do exactly thatb but not interfer with the main script used provided by medini (as this might cause problems once there is any update to that script)     Objective of the change : efficient workflow     Proposed change : Native support for renaming of existing failure modes without creating new IDs in a Search and Replace manner     Original Author : Peter Ploß  running the script "update failure modes" causes diff & merge to detect many changes (see screenshot); it seems that internally a new ID is given to the failure modes; seems to happen when the element has different (additional) attributes?! expected behavior: only diff of attributes are applied to existing failure mode; see UpdateFailureMode.zip -> and make diff of the two projects in "afterRunningUpdateFailureModeScript" folder  20190709_EMB: Use Case is renaming of an existing failure mode.  2019-07-23_Ploß: I'll look into creating a script that allow renaming existing failure modes (search&replace)     a parent node: shall display changes of all of its children, when selected., line 16"

medini_1036016653 · Answer

Renaming of part types' failure modes (part library!) still needs to be handled with care. The experienced user can do so by making use of a search and replace script that I created (supporting regular expressions). Still I feel that this core functionality could operate more robustly, without having to use scripts.     Conext: We use a failure mode library where e.g. the failure rate distribution of capacitors are defined and this failure model is then assigned to several capacitors (1:m relation assigned using "allocate elements").     Proposal: The script "Update Failure Modes" could create a trace between failure model's failure mode and created failure mode of part type, so that during an update the renaming can take place. (deletion and recreation at least is very problematic due to assignments in FMEDAs (DC worksheets) being lost)

medini_1036016653 · Answer

Does medini consider improving on the library functionality in the future? While it is feasible that ZF maintains an adapted script for updating part type's failure modes with respect to the failure mode library, it is certainly wished for that longerm such a key functionality is part of the application.