Multiple predefined contexts for a SEooC

Question

This topic is migrated from NXP's Excel based requirement list for medini, entry MEDNXP038.      Background:  For some semiconductor SEooC components, the supplier (NXP) already knows, that the component will be used in some distinct setups or use cases. Let's call them "contexts". The SEooC component supplier (NXP) can then already represent these distinct contexts in his safety analysis provided to the component integrators (customer).     Request:  medini shall allow:   That the NXP safety architect defines and maintains such contexts  That the NXP safety architect performs the safety analyses of the different contexts while reusing everything what the contexts have in common.  After NXP architect provides the SEooC safety analysis covering all contexts to an NXP field application engineer or to a customer's safety architect, then it shall be easy to select the appropriate context for the target application.

medini_1036867805 · Answer

MEDNXP076 of NXP's Excel based requirement list for medini falls into the same category.      Original description and discussion MEDNXP076:  All failure modes linked to a specific use case won't be considered if not selected.  2019-05-08 New requirement, needs further clarification/refinement   2019-05-29 Desired behavior: In case there is some optional 
functionality, it can impact multiple places in the FMEDA. The Safety 
Architect has knowledge about this and  this and would be able to adapt 
the FMEDA accordingly. The FAE does not have that deep understanding. 
For the FAE it is desired that he can switch on/off the functionality 
very simply and the FMEDA adapts "automatically". The desire is to 
offload the FAE from modifying individual lines in the FMEDA directly. 
This is considered as too high risk. 2019-06-04 MS: Feature request understood and enhancement need to be planned. 2019-08-21: ANSYS presented their proposal on FMEDA configurability. Looks reasonable.

medini_1036867805 · Answer

Original description and discussion MEDNXP038:  More safety analysis configuration, e.g. based on different defined contexts (different use cases, different mission profiles).  2018-03-09 works now already well for mission profiles. Need more discussion wrt. Use case parameters  2018-04-20 Intended to be addressed by "DC Configurator" approach. 
Michael Soden is feature owner. More detailed spec needed what shall be 
configurable or not. 2018-09-26 That's the DC configurator feature of R19.2. Needs to be 
tried out on NXP side. The aspect of "variants" can e.g. be addressed 
like in the model approach fro the 4 16FF variants. To be discussed with
 Markus whether this addresses his intentions, too.  2019-05-08 This includes also Emiliano's request "All failure modes /
 blocks linked to a specific communication won't be considered if not 
selected"   2019-06-02 MS: Looks like the same request as MEDNXP076   2019-07-24: MEDNXP076 is one sub-aspect of MEDNXP038 only. MEDNXP038 has a wider scope than failure modes only.   2019-08-21: ANSYS presented their proposal on FMEDA configurability. Looks reasonable.