ISO 26262 Functional Item Definition represents an essential aspect of the ISO 26262 standard, specifically designed for ensuring functional safety in road vehicles. It revolves around the precise delineation of the scope and operations of safety-critical components or systems within a vehicle. This meticulous clarification is pivotal for establishing a thorough comprehension of their functions, potential risks, and boundaries. It serves as the cornerstone for the creation of automotive systems that are not only safe but also dependable, facilitating robust hazard analysis, risk evaluation, and the integration of safety strategies.

 

The Item Definition will continue to evolve as we gain a deeper understanding of the design. We anticipate regular updates to the item definition as our knowledge grows

 

 

Schedule Safety Commander demo

 

 

Hazard Identification : Identify potential hazards that could arise from the operation of the vehicle or its systems. Hazards are situations or conditions that could lead to harm

Hazard Classification : classify identified hazards based on their potential impact, including harm to people, property, or the environment

Hazard Risk Assessment : assess the risk associated with each classified hazard. This involves evaluating the likelihood of the hazard occurring and the severity of its consequences

ASIL Determination : assign an Automotive Safety Integrity Level (ASIL) to each hazard based on its assessed risk. ASIL levels range from A (lowest) to D (highest)

Safety Goals Definition : establish safety goals for each identified hazard. Safety goals specify the required safety performance to mitigate or eliminate the associated risks

Functional Safety Concept : develop a functional safety concept that outlines how the vehicle or system will achieve the safety goals and mitigate the identified hazards

Technical Safety Concept : create a technical safety concept that describes the technical measures and strategies to achieve the safety goals and meet the ASIL requirements

Safety Requirements Specification : define safety requirements for the vehicle or system based on the technical safety concept. These requirements guide the design and implementation of safety-related functions

 

Safety Commander demo

 

 

Requirement Elicitation : identify and gather all safety-related requirements. These requirements define what the system or component must do to achieve functional safety goals

Classification of Requirements : categorize requirements based on their relevance to functional safety. ISO 26262 distinguishes between safety requirements, which are critical for safety, and non-safety requirements, which are not directly safety-related

Requirements Traceability : establish and maintain traceability between safety requirements, derived requirements, and higher-level objectives. This ensures that all requirements are aligned with safety goals

Requirements Documentation : document all safety-related requirements comprehensively. The documentation should include clear descriptions, rationale, and any assumptions made during requirement development

Requirements Validation : verify that the safety requirements are consistent, complete, and feasible. This process includes reviews, inspections, and simulations to ensure that requirements are achievable

 

Safety Commander demo

 

FMEDA is a critical step in the safety assessment process of ISO 26262, as it helps identify potential failure modes, assess their impact on safety, and determine the effectiveness of diagnostic measures. This analysis contributes to the overall safety of automotive systems by reducing the risk of dangerous failures

Component Selection : identify and select the components (hardware, software, sensors, etc.) that are safety-critical and require FMEDA analysis

Failure Modes Identification : for each selected component, identify potential failure modes. A failure mode is a specific way in which a component can fail

Failure Rate Assessment : determine the failure rates of the identified failure modes. This involves collecting data on failure rates from various sources, including field data, manufacturer data, and industry databases

Failure Mode Effects Analysis (FMEA) : analyze the effects of each failure mode on the safety functions and the overall system. Determine the severity of the effects, considering potential harm to people, property, or the environment

Diagnostic Coverage Assessment : assess the effectiveness of diagnostic mechanisms and safety measures in detecting or mitigating failure modes. Determine the diagnostic coverage of each safety mechanism

Single Point Failures Analysis (SPF) : identify and analyze single point failures within the system. Single point failures are failures that, if they occur, could lead to the loss of a safety function

Safe State Determination : determine the safe state or default behavior of the system or component in the event of a detected failure

Quantitative Analysis : quantify the risk associated with each failure mode by calculating the risk metrics, such as the Probability of Failure on Demand (PFD) and the Diagnostic Coverage (DC)

Safety Goal Compliance : verify that the failure modes, their effects, and the diagnostic coverage meet the safety goals defined for the system or component

Integration with Safety Requirements : Ensure that the results of the FMEDA analysis are integrated into the safety requirements and safety case for the system

 

Safety Commander demo