BB25.G System level availability

From its-wiki.no

Jump to: navigation, search
Title System level availability
Page Title BB25.G System level availability
Technology Line Autonomy of Devices/Energy Efficiency of WSN
Lead partner PhLi
Leader Willem van Driel
Contributors PhLi, NXP AT, HH, VEMCO, Nokia, ITI, GUT, AVL, Tecnalia, Acciona, CISC, VTT
Related to Use Cases SCOTT:WP7, SCOTT:WP11, SCOTT:WP13
Description Objective: Set-up minimum efforts for application level fault injection, recoverability and fault tolerant scenarios. The basic idea of Fault Injection Techniques309310 is to emulate (is in fact imitate) both hardware and software to better predict the final product quality and reliability. To make models of the hardware, a good representation of the actual hardware is needed. In many cases, emulation can be used to evaluate the software components without the (final version of the) hardware. To create those models, the software requires the following: Representation of hardware models in transfer functions, derived from hardware simulation tools, physics of failure knowledge, Design of Experiments (DoE), or by using the transfer function from previous hardware versions
  • Models for functional parts of the hardware, to be able to test specific parts only.
  • Descriptions of interactions between models (dependency/relation) Per today, there is no agreement yet in the community about what availability and reliability means for complex large systems. The proposed dependability tree is published in311. But what are the right tools and methods for validation and verification of large and complex systems?
Main output In SCOTT we will investigate to what level fault injection can contribute to a fast release of large and complex systems. The output will be a description on how one should apply this technique and to what extend it will be succesfull in limiting the validation and verification of these systems.
BB category Methodology (for SW/HW development)
Baseline State-of-the-art is publisched in Papp & Exarchakos. It contains a proposal for the dependability tree. System level Fault Injection, however, is not part of it. This will be developed in SCOTT
Current TRL The current TRL for this Building Block (1-9) is TRL 2 – technology concept formulated.
Target TRL TRL 6 – technology demonstrated in relevant environment (industrially relevant environment in the case of key enabling technologies).
Facts about "BB25.G"RDF feed
BB categoryMethodology (for SW/HW development) +
BaselineState-of-the-art is publisched in Papp & Exarchakos. It contains a proposal for the dependability tree. System level Fault Injection, however, is not part of it. This will be developed in SCOTT +
Current TRLThe current TRL for this Building Block (1-9) is TRL 2 – technology concept formulated. +
DescriptionObjective: Set-up minimum efforts for applObjective: Set-up minimum efforts for application level fault injection, recoverability and fault tolerant scenarios. The basic idea of Fault Injection Techniques309310 is to emulate (is in fact imitate) both hardware and software to better predict the final product quality and reliability. To make models of the hardware, a good representation of the actual hardware is needed. In many cases, emulation can be used to evaluate the software components without the (final version of the) hardware. To create those models, the software requires the following: Representation of hardware models in transfer functions, derived from hardware simulation tools, physics of failure knowledge, Design of Experiments (DoE), or by using the transfer function from previous hardware versions
  • Models for functional parts of the hardware, to be able to test specific parts only.
  • Descriptions of interactions between models (dependency/relation) Per today, there is no agreement yet in the community about what availability and reliability means for complex large systems. The proposed dependability tree is published in311. But what are the right tools and methods for validation and verification of large and complex systems?verification of large and complex systems? +
Lead partnerPhLi +
LeaderWillem van Driel +
Main outputIn SCOTT we will investigate to what levelIn SCOTT we will investigate to what level fault injection can contribute to a fast release of large and complex systems. The output will be a description on how one should apply this technique and to what extend it will be succesfull in limiting the validation and verification of these systems.idation and verification of these systems. +
Page TitleBB25.G System level availability +
PartnerPhLi +, NXP AT +, HH +, VEMCO +, Nokia +, ITI +, GUT +, AVL +, Tecnalia +, Acciona +, CISC + and VTT +
Target TRLTRL 6 – technology demonstrated in relevant environment (industrially relevant environment in the case of key enabling technologies). +
Technology LineAutonomy of Devices/Energy Efficiency of WSN +
TitleSystem level availability +
WorkpackageSCOTT:WP7 +, SCOTT:WP11 + and SCOTT:WP13 +