| 1. Define the inspection system’s safety role | Clarify whether the system only records inspection results, informs a human decision, or can control a vehicle function. Identify the item, operating conditions, interfaces, and foreseeable misuse. | System boundary, operational concept, interface list, and documented assumptions about operators and vehicle behavior. | ASIL is determined for vehicle-level safety goals through hazard analysis and risk assessment; it should not be assigned to a product simply because it performs inspection. |
| 2. Trace each safety-related function to its requirement | Check that functions such as fault detection, warning, interlock, or shutdown have clear requirements, defined response behavior, and traceable links to relevant safety goals. | Requirements traceability, safety concept, interface specifications, and verification records. | Confirm the ASIL allocated to each relevant safety requirement and whether ASIL decomposition is used. Do not assume every function has the same ASIL. |
| 3. Examine fault detection and safe response | Review how the system detects sensor, communication, software, or actuator faults, and what it does when data are missing, implausible, or delayed. | Fault-response descriptions, diagnostic test results, timing evidence, and documented safe-state behavior. | Safety mechanisms and their verification should be appropriate to the applicable safety requirements and ASIL. The required response depends on the hazard and system design. |
| 4. Verify sensors, measurements, and calibration | Check measurement range, accuracy, repeatability, environmental limits, calibration intervals, and detection limits for each inspection task. | Test methods, calibration records, uncertainty information, environmental test results, and acceptance criteria. | Measurement quality supports safety analysis but does not by itself establish ISO 26262 compliance or an ASIL capability. |
| 5. Assess software, data, and cybersecurity interfaces | Review software change control, version identification, access controls, data integrity, update procedures, and handling of corrupted or incomplete records. | Software configuration records, validation results, access-control rules, update history, and interface test reports. | Use the applicable functional-safety lifecycle and software requirements for the assigned ASIL. Cybersecurity risks should also be assessed under relevant cybersecurity processes; they are not interchangeable with ASIL. |
| 6. Check operation under real conditions | Evaluate usability, operator training needs, lighting, vibration, temperature, network availability, throughput, and recovery after power or communication loss. | Environmental and usability test results, operating limits, maintenance instructions, and failure-recovery procedures. | Severity, exposure, and controllability in the intended operating situation inform hazard analysis. A robust inspection workflow cannot replace that analysis. |
| 7. Review lifecycle evidence and supplier support | Confirm that safety-related changes, maintenance, issue reporting, and end-of-life handling can be managed throughout the system’s service life. | Safety documentation, change-impact process, maintenance plan, known-issue process, and support-period information. | QM and ASIL A, B, C, and D indicate different classifications of safety requirements under ISO 26262. The applicable development and assurance activities depend on the assigned ASIL and project context. |
| Important: ISO 26262 defines functional-safety processes for electrical and electronic systems in road vehicles. ASIL is established through hazard analysis and risk assessment, using severity, exposure, and controllability; it is not a general product rating. QM means that no ASIL is assigned to the relevant safety requirement. |