ISO 26262 and Product Quality

 Managing Road Vehicle Product Quality in Compliance with ISO 26262

PTC Windchill Quality SolutionsDesigned for series production cars, ISO 26262 provides a series of steps to manage functional safety and to regulate product development on a system, hardware and software level throughout the entire product lifecycle — from concept development through decommissioning.

Increasing complexity in the hardware, electronic and software systems used throughout automotive technologies has increased the complexity of achieving safety compliance for automotive manufacturers. New automotive standards like ISO 26262, released in November of 2011, aim to provide a common standard to measure how safe an automotive system will be in service.

PTC Windchill Quality Solutions offers a comprehensive line of reliability analysis and quality management tools designed to work together as a single software suite to reduce product and process risk, ensure system reliability, and improve quality and performance.


Additional Reliability Engineering Techniques and ISO 26262

Additional Reliability Engineering Techniques and ISO 26262These and other reliability engineering methodologies ― such as Reliability Block Diagrams, which predict reliability and maintainability needs for more complex system configurations; Event Tree Analysis, which is an inductive technique related to FTA; Markov, which considers systems that exhibit complex transitions between operational states; and Maintainability Prediction, which calculates maintenance needs and outputs service plans — all contribute to system design and development. These methodologies work in concert with other System Safety Analysis methods to verify and validate that the real-world system, as designed, has met its intended goals and target ASIL values for safety, reliability and quality.

Related Resources for ISO 26262

Related Resources for ISO 26262ISO 26262 and Requirements Management

As a risk-based safety standard, ISO 26262 is designed to assess and address possible hazards caused by the malfunctioning of electronic and electrical systems. It begins with a process of defining top-level requirements — both general and safety-related — from internal and external stakeholders, including customers. Top-level requirements are broken down further into specific system requirements and allocated to their component sub-systems.

Determining Safety Levels

Throughout this process, safety goals and hazard levels are determined for safety-critical requirements. Safety and hazard are represented with a value known as ASIL, or Automotive Safety Integrity Level, which quantifies the impact on the driver and other road users by combining probability of exposure, controllability of the situation and severity of the failure. Each ASIL is associated with a safety goal (i.e., safety requirement) to represent the value that the sub-system or system must achieve to fulfill that requirement. ASILs are critical to the product development process that follows the requirements development phase. They inform subsequent system design, test, production, operation, service and decommissioning activities, which must be completed with the ultimate objective of achieving the ASIL goal.