Feedback on DC Configurator License

medini_1054438917

Hello, Our team has gone through the shared "FAE FMEDA config script" and have identified some issues with DC configurator license. Also, have listed few enhancements that may come handy while preparing rules for FAEs usage and stated them below. Problems: While using DC configurator license, FMEDA worksheet is editable whereas Checklist becomes Read-only meaning that FAEs cannot execute the script. Also, they will not be able to add elements from Safety model in to Related artifacts column. Currently DC configurator license allows us to edit failure rate prediction and select mission profile but we cannot change package type as it is part of Catalog Data which gets frozen. Enhancement: The existing rule for Clearing Safety Mechanism is applicable to specific Failure modes only where as we would also like to have a rule which can be used to remove some of the specific Safety mechanisms from the entire FMEDA worksheet. The existing rule for Deactivate Safety Related is applicable to Leaf level elements only where as we would also like to apply this at higher level of hierarchy so that it can allow us to deactivate safety related elements in the below sub-hierarchies. Regards, Rupesh

medini_1036867805

This was discussed in call with medini on 2/24/21. Action item for Michael Soden to come back to NXP with proposals for these challenges. Related Meeting notes:

Main topic
today: Feedback from DC configurator trials by Rupesh and Bhavik
see also https://medini.freshdesk.com/support/discussions/topics/1000103041 Checklist is not active
under "DC configurator" license. Answer Michael: Checklist
was just meant as a trial.
Checklist feature not intended to become available under DC
configurator license.
Checklist based feature will be moved to a dedicated feature
later on, once the work flow proves out to be useful. The current checklist of
NXP team is also only a trial.
It's not a fully mature, productized checklist.
It's not an issue to "recreate" the checklist in the
later expected new native medini feature Mission profile and
parameters of failure prediction can be changed.
Problem: Package type cannot be changed under DC configurator
license.
This is necessary for products which NXP offers in different
packages.
Package selection shall be possible for FAEs without having to go
through all TR62380 dialogues.
In next version a "config file" approach is planned to
support a flow like: FSA creates a config file
for each package and respective base failure rates FAE only selects the
respective config file for the package chosen by customer (no need to go
through TR61380 menus)

Michael
demoing this feature on an medini internal prototype
Functionality is understood, UI is still not finalized.
Need to talk also with Emiliano about this, because the flow shall also work
for AMS devices which apply a different prediction for the analog and digital
areas of the die.

DC configurator is really the
way forward for NXP, because it truly can offload the FAE from having to
understand and touch the FMEDA worksheet itself. In config sheet, for clearing
safety mechanisms, two flavors are required Clear it from a particular
IP failure mode (exists) Clear it overall, i.e. from
all IP failure modes In config sheet,
selecting/deselecting an IP shall also selecting/deselect all
sub-hierarchies AI Michael: Come back to NXP with
proposals for the presented challenges.