ISO 26262

Effectively Manage the Auto Industry's Safety Development Cycle for Vehicles

Functional Safety Standard for Road Vehicles


Functional Safety Standard for Road Vehicles
Hardware and software systems for automotive applications are becoming increasingly complex, making it harder for automotive manufacturers and suppliers to achieve safety compliance.

New automotive standards like ISO 26262, released in November of 2011, give all manufacturers a common means to measure and document the safety of an automotive system while it is in service. Created specifically for production automobiles, 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.

Functional Safety and ISO 26262: Essential Tools and Strategies for Compliance

ISO 26262 will ultimately aid automotive OEMs and suppliers in the development of safety-related systems. However, many of these organizations are struggling with this stringent new standard as system complexity rises due to the exponential increase of software and electronics. With software and electronics driving up to 90% of automotive functionality, differentiation and innovation, these organizations face a common set of challenges:

Functional Safety and ISO 26262: Essential Tools and Strategies for Compliance
  • Disconnected and disparate development tools and data across system, software and hardware
  • Lack of process support and automation for the safety lifecycle
  • Manual and disconnected hazard analysis and risk assessment
  • Lack of reuse of global software development artifacts

PTC Integrity solves these complex challenges, helping automotive manufacturers reduce the cost and time required for ISO 26262 compliance while accelerating innovation in their software-intensive products. Examples of capabilities with PTC Integrity include:

  • Manage all development artifacts and processes in a single data model, from requirements to test results, models and calibrations, and risks and mitigations
  • Manage end-to-end traceability of these assets and be able to show that every requirement has been validated and every risk has been mitigated
  • Ensure strict change management procedures are adhered to across all lifecycle artifacts
  • Automate and enforce compliance requirements for model-driven development (MDD), providing trace-through model support

Product Quality and ISO 26262: Translating Compliance Goals into Safe Products

Product Quality and ISO 26262: Translating Compliance Goals into Safe Products
ISO 26262 requires System Safety Analysis to ensure that the final product will meet compliance goals. The System Safety Analysis takes place throughout product design, development, production and maintenance. The System Safety Analysis evaluates the proposed mechatronic system in context of the safety goals to:

  • Determine system performance metrics and hazard levels
  • Verify that the proposed system can achieve the safety goals set for the system
  • Identify tests, manufacturing controls and field feedback to monitor compliance

System Safety Analysis leverages a set of reliability engineering methodologies that vary depending upon expected risks. These may include:

  • Reliability Prediction to determine the failure rates of parts and systems
  • FMEA to assess the failure modes and effects on parts, assemblies, system design and processes
  • Test Plans and Manufacturing Control Plans to control mechatronic risks
  • Fault Tree Analysis to model system performance logic and identify the factors that contribute to catastrophic end-events
  • FRACAS, Nonconformance, Customer Complaints and CAPA to track test, manufacturing and field failures and to correct or prevent future issues