Robustness validation: Difference between revisions

Revision as of 14:48, 21 September 2012

Latest revision as of 04:34, 23 May 2024

(28 intermediate revisions by 15 users not shown)

Line 1:

{{Multiple issues|{{more citations needed|date=October 2012}}{{technical|date=October 2012}}

{{User sandbox}}

}}

<!-- EDIT BELOW THIS LINE -->

'''Robustness validation''' is a skills strategy with which the [[robustness]]Robustness of a product to the loading conditions of a real application is proven and targeted statements about risks and [[Reliability_engineeringReliability 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

== History ==

At the beginning of the 1970s a relatively high failure rates of electronic components were tolerable in [[automobile]]s, because they replaced mechanical components, which had a much higher [[failure rate]]. The underlying failure rates of bimetallic [[Automotive lighting|flasher]]s were 10% per year and the lifetime of mechanical [[BreakerCircuit breaker|ignition contacts]] at 10,000 miles. With the increasing number of [[semiconductor]]s in [[control unit]]s, and the introduction of the first safety systems ([[anti-lock brakes | ABS]]) in the 70s had to be addressed. Already in 1975, the'' General Specification for IC's in Automotive Applications'' <ref> General Specification for ICs in Automotive Applications, SAE Recommendation, 1975 </ref> as the first'' [[Society of Automotive Engineers | SAE ]] Recommendation was issued'','' the 1978 SAE standard'' <ref> General Specification for ICs in Automotive Applications, SAE standard, 1978, </ref> was declared and adopted by major semiconductor manufacturers.

The establishment of the Automotive Electronic Council ([[Automotive Electronics Council | AEC]]) 1994 by [[Ford Motor Company|Ford]], [[Chrysler]], [[General Motors | GM]] - [[ACDelco | Delco]] was also the Starting point for the AEC-Q100 qualification process ,<ref> Automotive Electronic Council's Stress Test Qualification for Integrated Circuits, AEC Q100, Rev. G, 2007, to [http://www.aecouncil.com/AECDocuments.html aecouncil.com] </ref>, was based on the SAE standards.

Due to the development of [[automotive]] and the ever-increasing complexity of vehicles associated with the demands for lower error rates of this qualification process , this process to decide by nonspecific tests, to cover a wide range of possible failure mechanisms, but only on the functionality of the component is out of date. In order to make statements about the robustness AEC Q100 can be replaced robustness validation.

== 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_InternationalSAE International| SAE]], [[ZVEI]], AEC and [[JSAE]] (Japanese Society of Automotive Engineers) was published, in which the guidelines for the contemporary [[Verification_and_validationVerification |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 to assess the reliability of electronic components by the specific requirements of the product are compared 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 distinguished. In the environmental requirements (mission profiles) and the functional requirements (use cases)

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

=== Mission Profiles ===

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

=== Mission Profilesprofiles ===

The mission profiles describes the loads and stresses acting on the product in actual use. These are, for example, changes in temperature, temperature profile, vibration and working of electrical and mechanical fields, or other environmental factors. It is important to specify the relevant stressors in their nature, intensity and duration of exposure, as well as the mix as closely as possible. With these details are given within specified accuracy projections regarding reliability of application and its components in field applications possible.

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

=== Use Cases ===

The use cases describe the nature and frequency of the operating conditions for which the product is designed. Please make sure that this addition to the normal operation of the possible cases of special operation and emergency operation. This meaning is not permissible, knowingly abuse.

The mission profiles describes the loads and stresses acting on the product in actual use. These are, for example, changes in temperature, temperature profile, vibration and working of electrical and mechanical fields, or other environmental factors. It is important to specify the relevant stressors in their nature, intensity and duration of exposure, as well as the mix as closely as possible. With these details areit givenis possible, within specified accuracy, projections regarding reliability of application and its components in field applications possible.

=== Use Casescases ===

The use cases describe the nature and frequency of the operating conditions for which the product is designed. PleaseOne should make sure that this addition to the normal operation of the possible cases of special operation and emergency operation. ThisIntentional meaningabuse is not permissible, knowingly abuseincluded.

=== Robustness margin ===

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

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

== Product Development ==

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

Today's standard qualification procedures for electronic components, assemblies and components for the automotive industry 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 implicitly. With the introduction of robustness validation priorities are defined in the development process again. The aim is to reduce the error's construction during the later phases of the project, which means ''front loading'' measures time in the product development process must be performed.

== Product Developmentdevelopment ==

It is necessary, the requirements from the product to the next level of the value chain break down in order to meet specific statements about possible vulnerabilities. Back in the early phases of the project is the knowledge (eg, from knowledge bases [[Lessons Learned]]) resorted previous projects in order to avoid known vulnerabilities documented. Using the analysis of the changes of the new product and the use of different methods, such as [[REM]], [[DRBFM]]'' or'' design reviews, new potential vulnerabilities are identified in order to analyze potential risks arising early and unavoidable. Which are hereby established critical parameters are used for the analysis of the feasibility of the project and flow optionally with the change of the initially established with one product requirements.

Validation occurs in the proof of the functional feasibility and reliability while meeting the functional and the implementation of the specifications are checked.

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

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 implicitlyimplicit. With the introduction of robustness validation, priorities are definedfocused inon the development process again. The aim is to reduce the construction error's construction during the later phases of the project, which means ''front loading'' measures time in the product development processtime mustline be performedprocess.

It is necessary, that the requirements from the product to the next level of the value chain breakbe broken down in order to meet specific statements about possible vulnerabilities. Back in the early phases of the project is the knowledge (ege.g., from knowledge bases [[Lessons Learned]]) resortedgained from previous projects in order to avoid known vulnerabilities documented. Using the analysis of the changes of the new product and the use of different methods, such as [[Resource Extraction Monitoring|REM]], [[DRBFMDesign Review Based on Failure Mode|RBFM]]'' or'' design reviews, new potential vulnerabilities are identified early in order to analyzemake potential risks arising early and unavoidable. Which are hereby established critical parameters are used for the analysis of the feasibility of the project and flow optionally with the change of the initially established with one product requirements.

== Other applications of robustness validation ==

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

In addition to the publication of the Handbook for Robustness Validation for semiconductor devices in 2007 was inthe [[ZVEI]] in the year 2008, anpublished additionalthe manual <ref> Handbook for Robustness Validation of Automotive Electric / Electronic Modules, ZVEI, 04/2008 published </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 ==

== Footnotes ==

<references />

== External links ==

* [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 47 ⟶ 57:

* [http://www.aecouncil.com/AECDocuments.html Homepage Automotive Electronics Council]

[[Category:Quality control tools]]

== Footnotes ==

<references />

[[category:Standardisation]]