Standard · ISO 26262

ISO 26262 software for HARA, ASIL determination and safety goals

ISO 26262 requires structured functional safety work across item definition, hazard analysis and risk assessment, safety goals, safety requirements, verification evidence, and review activities. The standard does not tell teams to use one specific tool, but the workflow quickly becomes difficult to govern in spreadsheets alone.

Request pilot accessSee the product
HARA table: Hazards, operating situations, severity, exposure, controllability and ASIL for an ISO 26262 item, with review state per row.HARA table: Hazards, operating situations, severity, exposure, controllability and ASIL for an ISO 26262 item, with review state per row.HARA table: Hazards, operating situations, severity, exposure, controllability and ASIL for an ISO 26262 item, with review state per row.

The challenge

The ISO 26262 workflow challenge

Teams must keep HARA, ASIL reasoning, safety goals, requirements, work products, and confirmation review evidence consistent over time. Disconnected tooling increases review effort and weakens traceability.

With ASF Core

How Aegis SafeForge helps

Aegis SafeForge supports ISO 26262-aligned workflows with AI-assisted drafting, deterministic review boundaries, human approval, and traceability from project context through approved safety artifacts.

  • Guide teams from project context and item definition toward reviewed HARA outputs.
  • Carry approved decisions into safety goals, requirements, evidence, and audit-ready exports.
  • Maintain review state, ownership, and traceability for managers and reviewers.
  • Record the safety case, confirmation review, functional safety audit and assessment, configuration baseline and safety release alongside the analyses they confirm.

Methodology

ISO 26262 methodology supported by the workflow

Aegis SafeForge is designed to make each functional safety decision explicit, reviewable, and traceable. It assists the work pattern around ISO 26262 without claiming certification or replacing qualified engineering assessment.

  1. 01

    Item definition and context capture

    Capture item boundary, item functions, operating scenarios, operational states, safety assumptions, interfaces and source documents in one item definition before HARA starts.

  2. 02

    HARA and ASIL reasoning

    Work through hazardous events, severity, exposure, controllability, ASIL rationale and safety goals with deterministic consistency checks and required human approval, manually or with AI drafts; E0 or C0 rates as QM, and missing ratings stay visibly unrecorded instead of defaulted.

  3. 03

    Safety goal to requirement traceability

    Carry approved safety decisions into safety goals, functional safety requirements, technical safety requirements, verification evidence, and change-impact views.

  4. 04

    Review evidence and audit preparation

    Preserve ownership, review state, approval history, source references, exports, and open gaps so assessors can inspect the decision trail.

Industry profile in ASF Core

FMEDA captures inputs and external analysis references; ASF does not calculate PMHF. The value is shown as not computable, with the reason. Safety case, confirmation review, functional safety audit and assessment, configuration baseline and safety release are available as manually maintained work products, without AI generation. Supplier, tool-confidence, reuse and field records support recording and review, without automated qualification or release. Industry profiles do not imply certification or tool qualification.

ISO 26262 workflows

Item definition and system context · HARA and ASIL · Safety goals, FSC and TSC · FMEDA, FTA, DIA and TCA · Requirements traceability · Safety case and confirmation measures

Continue reading

FAQ

Frequently asked questions

What is ISO 26262?

ISO 26262 is the functional safety standard for electrical and electronic systems in road vehicles.

What does an ISO 26262 tool need to support?

It should support structured safety work products, traceability, review workflows, requirements links, evidence, and defensible engineering decisions.

Does Aegis SafeForge certify a system as ISO 26262 compliant?

No. Aegis SafeForge supports ISO 26262-aligned workflows and evidence management, but compliance decisions remain with qualified teams and assessors.

How does Aegis SafeForge support HARA?

Aegis SafeForge helps draft, structure, review, approve, and trace HARA records from project context into downstream safety artifacts.

Can Aegis SafeForge export ISO 26262 work products?

Yes. Each lifecycle group exports as a workbook (one sheet per table), and handoff packages carry a manifest of what was shared.

Compare ASF Core with your current process.

Bring one real bottleneck: HARA, TARA, traceability or evidence. We will show how ASF Core fits your process.

Request pilot accessBook a live walkthrough