Which safety standards does TestAuto2 support?
TestAuto2 — Automotive Safety Solution supports four primary automotive safety and quality standards: ISO 26262 (Functional Safety for road vehicles), ISO 14971 (Medical device risk management, adapted for automotive), AIAG-VDA FMEA (Failure Mode and Effects Analysis methodology), and IATF 16949/APQP (Automotive Quality Management System with Advanced Product Quality Planning). Additionally, the solution provides foundational support for ISO 21448 (SOTIF) for analyzing hazards beyond malfunction scenarios. See Standards Compliance Model for detailed coverage.How does TestAuto2 implement ISO 26262 compliance?
The solution implements ISO 26262 through a multi-part workflow covering Concept Phase (Part 3), System Design (Part 4), and Hardware/Software development (Parts 5-6). You perform HARA (Hazard Analysis and Risk Assessment) using specialized risksheets that calculate ASIL ratings based on Severity × Exposure × Controllability matrices per ISO 26262-3 Table 4. Safety Goals are derived and traced through the V-model to System Requirements, Design Requirements, and verification test cases. Every artifact maintains bidirectional traceability required by Part 8. See ISO 26262 Functional Safety and Your First HARA Session.What’s the difference between HAZID and HARA workflows?
HAZID (Hazard Identification) is a preliminary risk discovery process using a simplified risk matrix (Severity × Likelihood → Risk Level) to systematically identify potential hazards early in concept phase. HARA (Hazard Analysis and Risk Assessment) is the formal ISO 26262-3 process that classifies each hazard using Severity (S0-S3), Exposure (E0-E4), and Controllability (C0-C3) parameters to determine ASIL levels (QM, A, B, C, D). HAZID typically feeds into HARA — you discover hazards in HAZID, then perform detailed ASIL classification in HARA before deriving Safety Goals. Both workflows use dedicated risksheet configurations. See HARA Risksheet Configuration and HAZID Risksheet Configuration.How does AIAG-VDA FMEA methodology differ from ISO 26262 FMEA?
AIAG-VDA FMEA uses Action Priority (High/Medium/Low) calculated from lookup tables based on Severity, Occurrence, and Detection ratings — it does NOT use RPN multiplication. ISO 26262 FMEA focuses on ASIL-driven analysis where failure modes are traced to hazards and safety goals, ensuring all ASIL-rated hazards have corresponding failure mode coverage. TestAuto2 supports both: AIAG-VDA Action Priority tables are implemented in DFMEA/PFMEA risksheets, while ISO 26262 traceability is enforced through the RTM domain model linking Failure Modes → Characteristics → Design Requirements → System Requirements → Safety Goals → Hazards. See AIAG-VDA FMEA Methodology and Action Priority Methodology.Does TestAuto2 generate compliance reports for audits?
Yes. The solution auto-generates ISO 26262 HARA Report with ASIL determination matrix and hazard register per Part 3, FMEA Summary Reports (System/Design/Process) with Action Priority distributions per AIAG-VDA, Requirements Traceability Report demonstrating bidirectional coverage per ISO 26262 Part 8, Risk Control Effectiveness Report evaluating pre/post mitigation risk reduction, and Safety Readiness Scorecard showing percentage completion across all standard requirements. All reports use Velocity macros querying live Polarion data — they update automatically as you complete work items. See Reports and Generate Safety Readiness Scorecard.How do I track compliance across multiple standards simultaneously?
Use the Standards Compliance Overview Dashboard which displays a live compliance matrix mapping your project artifacts to specific clauses across ISO 26262, AIAG-VDA, IATF 16949, and SOTIF. Each standard shows percentage completion for Requirements, Traceability, Verification, FMEA Coverage, and Documentation Status. The Safety Readiness Scorecard provides detailed per-standard metrics with drill-down queries to identify gaps. Navigate via Home → Standards Compliance or directly access your role dashboard (Safety Engineer, V&V Engineer, etc.) which highlights standard-specific tasks. See Standards Compliance Overview and Interpret Compliance Metrics.Standards Compliance Decision Matrix
Use this table to determine which standard workflow applies to your task:| Your Task | Primary Standard | Workflow Entry Point | Key Artifacts |
|---|---|---|---|
| Identify system-level hazards early in concept phase | ISO 26262 Part 3 | Create HARA Document | Hazards, Safety Goals, ASIL ratings |
| Analyze component failure modes and effects | AIAG-VDA FMEA | Create Design FMEA Document | Failure Modes, Action Priority (H/M/L) |
| Define manufacturing process controls | IATF 16949 / APQP | Create a Control Plan | Control Plan Items, SC/CC Characteristics |
| Analyze sensor performance limitations (non-malfunction) | ISO 21448 SOTIF | Create HARA Document with SOTIF Hazard Category | Hazards (SOTIF type), Risk Controls |
| Demonstrate verification coverage for safety requirements | ISO 26262 Part 4-6 | Link Tests to Requirements | Test Cases, Verification PowerSheet |
| Prove bidirectional traceability for audit | ISO 26262 Part 8 | Generate Traceability Report | Requirements, RTM PowerSheet |
Compliance Workflow Visualization
See Also
- Standards Compliance Model — Conceptual overview of multi-standard architecture
- Safety Readiness Scorecard — Per-standard compliance metrics
- ISO 26262 HARA Report — Auto-generated ASIL matrix and hazard register
- FMEA Reports — AIAG-VDA compliant DFMEA/PFMEA summaries
- Requirements Traceability Report — ISO 26262 Part 8 bidirectional coverage