Exchange and integration of component safety analyses between semi supplier and item integrator

medini_1036867805

This topic is migrated from NXP's Excel based requirement list for medini, entry MEDNXP010. Use case: The topic relates to the "Safety Element out of Context" paradigm of ISO 26262. It is a typical situation, that a semiconductor vendor performs a quantitative safety analysis for one of his products based on assumptions about its use. This analysis might get amended/customized to real use cases of its customers. There are cases, where also the customer of the semi vendor, i.e. system integrator, also uses medini to conduct his system safety analysis. However, this typically happens on a different abstraction level. Fault models are different. Failure effects from semiconductor level turn into failure modes on integration level. Problem to be solved: As the abstraction level changes between supplier and integrator, it is not useful for the integrator to simply "import" the safety analysis of the supplier. Some translation between abstraction levels has to take place. This is slightly related to the transitive fault-error-failure idea of ISO 26262. It might also be related to the standardization activities of Accellera Functional Safety group and IEEE P2851. Potentially medini fault-effect chains can be a starting point for a solution. Request: Provide a guideline and necessary features to enable inclusion of a semiconductor component SEooC safety analysis in medini into an item level safety analysis also in medini, while shifting the abstraction level. The workshop of Michael Soden on 2019 Digital Safety Conference "Safety analysis at semiconductor leveI and supply chain collaboration" sketched a potential solution for this.

medini_1036867805

Original description and discussion MEDNXP010: Step-by-step cookbook how an system integrator (NXP customer or NXP internal system integrator) can take NXP's SEooC safety analysis in medini and make use of it in his own system level safety analysis in medini. 2018-03-09 Will come with DC Configurator (mini medini) implementation 2018-07-20 Either a document report can be provided to customers. Or
new DC configurator can be used. A quick guide would be helpful here.
The "DC confurator" part of the usual user manual can serve this purpose
initially. Whether this will be sufficient needs to be seen. Maybe a
tutorial or video can improve this. 2018-10-08 A process guide is planned, which might cover this. Right now, no such step-by-step guide is in place in R19.2 2019-07-31 In alignment call, Olaf mentioned ideas about a "compositional safety analysis" feature to enable medini based collaboration between suppliers and integrators. This is roughly planned for 2021, but not confirmed yet.