Robustness validation: Difference between revisions

Revision as of 16:24, 5 October 2012

Revision as of 16:24, 5 October 2012

Line 1:

{{AFC submission|||ts=20120925130110|u=Colmanbyrne|ns=2}}

'''Robustness validation''' is a skills strategy with which the [[robustness]] of a product to the loading conditions of a real application is proven and targeted statements about risks and [[Reliability_engineering | reliability]] can be made. This strategy is particularly for use in the [[automotive industry]] however could be applied to any industry where high levels of reliability are required

Line 11 ⟶ 12:

== Initiators and participants ==

In April 2007, the'' Handbook for Robustness Validation of Semiconductor Devices in Automotive Applications'' <ref name="RVHB_SC">'' Handbook for Robustness Validation of Semiconductor Devices in Automotive Applications'' ZVEI, 04/2007 </ref> with international cooperation from [[SAE_International | SAE]], [[ZVEI]], AEC and [[JSAE]] (Japanese Society of Automotive Engineers) was published, in which the guidelines for the contemporary [[Verification_and_validation | validation]] of semiconductor components in the automotive applications were compiled. Companies were involved in this from the entire [[supply chain]] in the field of automotive electronics. In addition to vehicle manufacturers and suppliers, a large group of semiconductor manufacturers, this concept of skill is complemented with a current database. This so-called Knowledge Matrix <ref> [http://www.zvei.org/index.php?id=3796 Knowledge matrix with zvei.org] </ref> is a list of currently known failures includes mechanisms with causes, error methods and further information.

== Contents ==

Robustness Validation is used to assess the reliability of electronic components by comparing the specific requirements of the product with the actual "real life values​​". With the introduction of this methodology, a specific list of requirements (usually based on the [[Original_Equipment_Manufacturer | OEM]]) is required. The requirements for the product can be defined in the environmental requirements (mission profiles) and the functional requirements (use cases).

=== Mission Profiles ===

<!--[[Image:Potato_Diagram.jpg | thumb | Robustness for robustness validation based on the comparison of the application requirements, specification and technological limits of the component <ref name="RVHB_SC" />]]-->

Line 22 ⟶ 26:

=== Use Cases ===

The use cases describe the nature and frequency of the operating conditions for which the product is designed. One should make sure that this addition to the normal operation of the possible cases of special operation and emergency operation. Intentional abuse is not included.

=== Robustness margin ===

The lifetimes can be hedged by specific, tailored to the application and the failure mechanisms, determined tests. An essential process are [[End of life test]]s. From the distance of the requirements to the test results, the reliability and robustness of the device can be determined.

== Product Development ==

<!--[[Image:RV_flow.jpg | thumb | upright | Robustness Validation schedule of product development to mass production <ref name="RVHB_SC" />]]-->

Today's standard qualification procedures for electronic components, assemblies and components for the automotive industry is based on the use of standardized tests at the end of the product development of parts and components. In contrast, Robustness Validation is a process that includes the entire product development process, as well as mass production. The qualification of the components based on the robustness analysis is thus implicit. With the introduction of robustness validation, priorities are focused on the development process again. The aim is to reduce the construction error's during the later phases of the project, which means ''front loading'' measures in the product development time line process.

Line 34 ⟶ 41:

== Other applications of robustness validation ==

In addition to the publication of the Handbook for Robustness Validation for semiconductor devices in 2007 the [[ZVEI]] in 2008, published the manual <ref> Handbook for Robustness Validation of Automotive Electric / Electronic Modules, ZVEI, 04/2008 </ref> in which this procedure is described for the development and qualification of electronic control units in automobiles. There are also other activities in the field of sensors and electronic systems in the vehicle.

== Weblinks ==

* [http://www.zvei.org/index.php?id=alias Homepage ZVEI]

* [http://www.zvei.org/index.php?id=alias&type=1 Robustness Validation (ZVEI Internet)]

Line 46 ⟶ 55:

== Footnotes ==

<references />