Robustness validation: Difference between revisions

Content deleted Content added
Okeyes (WMF) (talk | contribs)
Added tags to the page using Page Curation (refimprove, technical)
m WPCleaner v1.19 - Repaired 2 links to disambiguation page - (You can help) - Breaker, Flasher, 2 to be fixed - REM, Robustness / Fixed using WP:WCW - Reference before punctuation - Spelling and typography
Line 3:
 
 
'''Robustness validation''' is a skills strategy with which the [[robustnessRobustness]]{{Disambiguation needed|date=October 2012}} 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
 
== 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]], [[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 ==
Line 40:
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.
 
It is necessary that the requirements from the product to the next level of the value chain be 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]]) gained from previous projects in order to avoid known vulnerabilities. Using the analysis of the changes of the new product and the use of different methods, such as [[REM]]{{Disambiguation needed|date=October 2012}}, [[DRBFM]]'' or'' design reviews, new potential vulnerabilities are identified early in order to make potential risks
 
== Other applications of robustness validation ==