ISO 26262-3:2018 · HARA
ASIL calculator.
Set the three classes of one hazardous event and see its ASIL, with the reason.
The ASIL determination table
One block per severity class. In each block the rows are exposure and the columns are controllability. Once you choose three classes above, the matching cell is marked.
| C1 | C2 | C3 | |
|---|---|---|---|
| E1 | QM | QM | QM |
| E2 | QM | QM | QM |
| E3 | QM | QM | A |
| E4 | QM | A | B |
| C1 | C2 | C3 | |
|---|---|---|---|
| E1 | QM | QM | QM |
| E2 | QM | QM | A |
| E3 | QM | A | B |
| E4 | A | B | C |
| C1 | C2 | C3 | |
|---|---|---|---|
| E1 | QM | QM | Aa |
| E2 | QM | A | B |
| E3 | A | B | C |
| E4 | B | C | D |
- S0, E0 and C0 are not in the table. For each of them the standard requires no ASIL (ISO 26262-3:2018, 6.4.3.4, 6.4.3.7 and 6.4.3.9). The calculator shows this as "No ASIL", which is not the same as a QM rating.
- a This cell carries a footnote in the standard: if the exposure only arises when several unlikely situations happen together, and that combination is rarer than E1, QM may be argued instead (ISO 26262-3:2018, 6.4.3.11).
- The table follows a simple pattern: start from ASIL D at S3, E4, C3 and go down one level for each class step lower, until QM.
What each class means
Severity, Clause 6.4.3.2
- S0
- No injuries: the consequences are clearly limited to material damage. No ASIL is required.
- S1
- Light and moderate injuries, short of the severe injuries of S2.
- S2
- Severe injuries, including life-threatening ones where survival is probable.
- S3
- Life-threatening injuries where survival is uncertain, and fatal injuries.
Exposure, Clause 6.4.3.5
- E0
- A situation so unlikely that it is not analysed further. The reason for excluding it must be recorded, and no ASIL is required.
- E1
- A situation most drivers meet less than once a year.
- E2
- A situation most drivers meet a few times a year, or one that takes up less than about 1% of operating time.
- E3
- A situation an average driver meets once a month or more, or one that takes up about 1% to 10% of operating time.
- E4
- A situation that occurs on almost every drive, or one that takes up more than about 10% of operating time.
Controllability, Clause 6.4.3.8
- C0
- Any driver avoids the harm with a routine action, or the loss of the function does not affect safe driving. No ASIL is required.
- C1
- Simple to control: more than 99 in 100 typical drivers or other road users avoid the harm.
- C2
- Normally controllable: between 90 and 99 in 100 typical drivers or other road users avoid the harm.
- C3
- Difficult or impossible to control: fewer than 90 in 100 typical drivers or other road users avoid the harm.
The descriptions are our own wording. The frequencies and time shares for exposure, and the 90 and 99 in 100 thresholds for controllability, are the informative guidance in ISO 26262-3:2018, Annex B; exposure can be rated either by how often a situation occurs or by how much of the operating time it takes up. The mapping in the table is the standard's Table 4.
Worked example: loss of brake assist in town
An illustration, not a rating to copy. The item is an electromechanical brake booster. The malfunction is a sudden loss of boost while the driver brakes. The operational situation is braking from about 50 km/h in urban traffic, with pedestrians and cyclists close by.
Severity, S3
Without boost the car stops later than the driver expects. The worst credible outcome in this situation is hitting a pedestrian at town speed, where survival is uncertain, so the team rates S3.
Exposure, E4
Braking in town with people close by happens on almost every drive. The team keeps the situation at that level instead of narrowing it to "a pedestrian on a crossing at that very moment", because finer and finer situations push the exposure down artificially.
Controllability, C2
The pedal still acts on the brakes through the hydraulic circuit, but it needs much more force. Most drivers press harder and stop in time, some react too late. The team argues C2 and supports it with braking tests with ordinary drivers.
Result, ASIL C
S3, E4 and C2 give ASIL C, and the safety goal for this event carries it. If the tests could not support C2, the team would have to take C3, and the safety goal would become ASIL D.
The table is the easy part. Each class needs a written rationale and the team's own evidence, such as accident data, driving statistics or controllability tests, and a reviewer checks them. No tool can supply that argument. The HARA concept guide covers the whole method, from operational situations to safety goals.
What people get wrong
- Putting the failure rate into exposure. Exposure is the probability of being in the operational situation. How often the item fails is not part of the hazard analysis; the resulting ASIL decides how well random and systematic faults must then be controlled (ISO 26262-3:2018, Annex B.1). The share of vehicles fitted with the item does not lower the exposure either (6.4.3.6).
- Taking credit for the item's own safety mechanisms. The hazard analysis rates the item as if its safety mechanisms did not exist, including mechanisms carried over from a predecessor. They belong in the functional safety concept (6.4.1.2).
- Rating controllability for a skilled driver. The class estimates how many typical drivers, fit to drive and licensed, avoid the harm. What a trained test driver manages is not the measure (6.4.3.8 and Annex B.4).
- Slicing operational situations until the exposure drops. Very narrow situations each get a lower exposure class, and so a lower ASIL. Group similar situations instead (6.4.2.7), and where there is reasonable doubt about a class, take the higher one (6.4.3.1).
- Reading QM as "no requirements". QM means normal quality management is enough for that risk. Safety requirements can still be written for the event, and the event and its assumptions stay in the hazard analysis (6.4.3.10 and 6.4.4.4).
- Using decomposition to lower the safety goal. The ASIL belongs to the hazardous event and its safety goal, and every requirement derived from the goal inherits it (6.4.4.2; ISO 26262-9:2018, 5.2). ASIL decomposition later splits a requirement over sufficiently independent elements, written for example ASIL B(D). The safety goal stays ASIL D, and so do the hardware metric targets (ISO 26262-9:2018, 5.4.5).
Clause numbers refer to ISO 26262-3:2018 unless another part is named. Last reviewed 19 November 2026.
ASIL calculator FAQ
Questions engineers ask about ASILs.
How is an ASIL determined?
In the hazard analysis and risk assessment, each hazardous event gets a severity class (S0 to S3), an exposure class (E0 to E4) and a controllability class (C0 to C3), each with a written rationale. ISO 26262-3:2018, Table 4 then maps the combination to QM or to ASIL A, B, C or D. Only the top class in all three, S3, E4 and C3, gives ASIL D.
What does QM mean in ISO 26262?
QM stands for quality management. It means the normal quality processes of the organisation are judged enough to manage the risk of that hazardous event, so ISO 26262 compliance is not required for it. It does not rule out safety requirements: the event can still have some.
What happens when a class is S0, E0 or C0?
None of the three appears in the determination table. For each of them the standard states that no ASIL is required (ISO 26262-3:2018, 6.4.3.4, 6.4.3.7 and 6.4.3.9). For E0 the reason for excluding the situation must be recorded, and in practice every such class needs a rationale that an assessor can follow.
Is exposure the probability that the system fails?
No. Exposure is the probability of being in the operational situation in which the malfunction would be dangerous, for example reversing out of a parking space. How often the item fails is not part of the hazard analysis, and the share of vehicles fitted with the item does not lower the exposure either.
Does ASIL decomposition change the ASIL of the safety goal?
No. Decomposition applies to safety requirements, not to the safety goal. It splits a requirement over redundant, sufficiently independent elements that can then be developed to a lower ASIL, written for example ASIL B(D). The safety goal keeps its ASIL, and the hardware metric targets stay at the original level.
Can a tool assign the ASIL for my project?
A tool can read the table, as this one does. The real work is choosing the classes: each one needs a rationale and evidence from the team, such as driving statistics, accident data or controllability tests, and the hazard analysis is reviewed before the safety goals are fixed.
Next step
From one cell of the table to a complete HARA.
The HARA concept guide covers the full method: hazardous events, operational situations, the rationale for each class and the safety goals. It is part of the Pro plan, and its public page shows the outline. A free account opens the complete Functional Safety Concept guide, 3 work-product templates, 5 random practice exams a month and the Markov and RBD simulators.