Proven in Use
Learn when field history can qualify a reused element under ISO 26262-8, Clause 14: define the candidate, protect the service record from changes, reconstruct field data and decide whether the statistics can ever close.
- Chapters
- 11
- Chapters
- Reuse routes compared
- 8
- Reuse routes compared
- Worked example
- 1
- Worked example
Quick answers
- What is proven in use in ISO 26262?
- Proven in use is the argument defined in ISO 26262-8, Clause 14 that lets documented field experience stand in for development rigor when qualifying a reused element. Instead of showing the candidate was developed to the standard, you show it has accumulated enough relevant, unchanged service history with few enough attributed incidents that its demonstrated failure rate meets the target for the ASIL being claimed. The statistics use a Poisson model with a single-sided 70% confidence bound to convert vehicle-hours and incidents into a demonstrated rate. The offer is narrower than it sounds: changes reset the clock, data pipelines leak, and the per-ASIL targets form a numbers wall that closes the argument far more often than it opens it.
- How many hours of field data do you need for proven in use?
- It depends on the target for the claimed ASIL and on how many incidents are attributed to the candidate, and the answer is usually sobering. The required exposure grows with every attributed incident, and against the per-ASIL targets the fleet arithmetic quickly demands very large volumes of relevant, observed vehicle-hours. Item-level claims at the highest ASILs are almost never reachable. The course works through the statistics and the fleet arithmetic so you can tell before collecting data whether the argument can close, and covers decomposition and stated margin as the practical workarounds.
Why it pays for itself
Know when the argument closes
The per-ASIL rate targets and fleet arithmetic decide up front whether your field data can ever reach the bar, before you spend months assembling an argument the numbers wall will kill.
Run the Poisson math yourself
Convert vehicle-hours and attributed incidents into a demonstrated failure rate at the confidence level the clause asks for, and see how each additional incident raises the required evidence.
Screen all eight reuse routes
Clause 14 is one route among eight spanning process, product, and history evidence. A four-question triage tells you which route fits your candidate before you commit to any of them.
What you’ll be able to do
Pick the right reuse route
Screen a candidate against the available routes before investing in a Clause 14 argument.
Define a defensible candidate
Scope the candidate, its configuration and the requirements the credit applies to.
Protect and reconstruct the record
Track resetting changes and judge whether field data was really observed.
Read the statistics correctly
Understand what the confidence bound claims and when the targets are out of reach.
Choose between Clause 14 and ISO/PAS 8926
Route pre-existing software to the approach that can actually close.
Chapter by chapter
- 01
The Reuse Problem
See why almost nothing in a car is new, which three terms carry the clause, and where proven in use sits in Part 8.
- Three key terms
- Place in Part 8
- Origin of the idea
- 02
The Reuse Landscape
Pick the reuse route before arguing, using a short triage to tell whether Clause 14 fits your candidate at all.
- Route before argument
- Reuse routes
- Four-question triage
- 03
The Candidate
Treat a candidate as a claim rather than a part, choose its granularity, and scope the credit to specific requirements.
- Candidate as a claim
- Granularity
- Readiness check
- 04
Change and Environment
Learn which changes reset the service clock and how to compare the operational profile of the field with the new use.
- Resetting changes
- Change catalogue
- Operational profiles
- 05
Field Data
Judge whether hours were really observed, where field data comes from, what counts as an incident and how data quality is assessed.
- Observed hours
- Data sources
- Incident definition
- 06
The Statistics
Understand the question the math must answer, the model behind it, and the assumptions the formula makes without saying so.
- The model
- A short example
- Hidden assumptions
- 07
Targets and the Numbers Wall
Compare the acceptance targets with realistic fleet exposure and get a feel for how large the required service history becomes.
- Acceptance targets
- Fleet arithmetic
- Sense of scale
- 08
A Worked Example
Qualify a fictional carryover sensor step by step, then see why a software counter-example never had a chance.
- Exposure counting
- Incident screening
- Bound and verdict
- 09
When It Actually Works
Profile the candidates that succeed, the factors that kill an argument, the hybrid forms used in practice and who owns the evidence.
- Profile of a winner
- Argument killers
- Hybrid forms
- 10
Pre-Existing Software and ISO/PAS 8926
See why software fits Clause 14 badly, what ISO/PAS 8926 covers, and how to choose between the two routes.
- Structural mismatches
- Scope of ISO/PAS 8926
- Side-by-side comparison
- 11
Building the Argument
Decide what you deliver, how the credit lands in the safety case, and which questions to expect in the assessment.
- Deliverables
- Safety case placement
- Assessment questions
Read all 11 chapters with Expert.
Start with a free account: the complete Functional Safety Concept guide and 5 practice exams a month, then upgrade when you need this guide.
Expert plan pricingNot just text: the visual toolkit
The evidence spectrum
Process, product and history evidence placed on one axis.
Fragmented service history
How modifications split a long record into short usable segments.
The dark figure
Incidents narrowing through the observation chain before anyone counts them.
Fleet clock versus reset deadline
Cumulative fleet hours racing the next change that resets them.
ISO/PAS 8926 evaluation flow
The evaluation steps for pre-existing software at a glance.
A Carryover Sensor Module
Chapter 8 walks a fictional sensor module through candidate definition, exposure counting, incident screening and the final verdict.
- The candidate and its frozen configuration
- Counting exposure conservatively
- Screening field reports into counted incidents
- The confidence bound and the verdict
- A software counter-example that cannot close
Unlock in course
Who this guide is for
- Engineers carrying over a sensor, module, or ECU into a new vehicle program
- Safety managers weighing field-history qualification against re-development cost
- Reliability engineers sitting on warranty and field data they want to use as evidence
- Suppliers preparing a proven-in-use case an OEM assessor will interrogate
Frequently Asked Questions
Common questions about Proven in Use
Start the course today
A free account unlocks one full concept guide, 3 work product templates, 1 guided process, the Markov and RBD simulators, and 5 practice exams per month. The Pro and Expert plans unlock more of the 93-guide library. No credit card required.
Continue with
Where this topic leads next.
- Verification and assessmentChange Impact Analysis for Carryover & Modified SystemsMost automotive projects reuse existing systems. This page shows how ISO 26262 impact analysis and Part 8 Clause 8 change management decide what stays valid, what must be re-verified, and how to keep carryover, variants, and facelifts safe.
- Verification and assessmentHomologation, Regulations & LiabilityA functionally safe vehicle is not automatically a street-legal one, and an approved vehicle is not automatically liability-proof. Learn how type approval, the key UN Regulations and product liability law interlock with ISO 26262 for E/E and automated driving systems.
- Vehicle domainsActuator SafetyMotors, valves and relays are where safety goals become physical: learn how actuation channels fail stuck or runaway, how feedback and diagnostics catch it, and how safe states from de-energize to active hold are engineered and quantified.