Book a Discovery Call
Book a Discovery Call
ASAP by Fennec Engineering

Safety Management Built on the Proven V-Model

The ASAP Platform is Fennec Engineering's software system of record for functional safety. It runs the full V-Model in one connected environment, from hazard analysis through the safety case, with every artifact traced to the next.

ASAP V-Model from hazard and risk assessment through the safety case, with validation links between requirements, design, realization, and testing
ASAP follows the V-Model from hazard analysis to the final safety case, with verification and validation linked back to the work they prove.

The nine stages of the ASAP V-Model

  1. Hazard & Risk Assessment: Identify hazards and tasks (HARA).

  2. Safety Concept: Define the mitigation strategy.

  3. Requirements: Set specific technical constraints.

  4. System Design: Define the architecture and reliability.

  5. Realization: Build and implement the system.

  6. Element Test: Verify individual components.

  7. Subsystem Test: Verify assembled subsystems.

  8. System Test: Validate the complete robot.

  9. Safety Case: Compile the final evidence dossier in ASAP Verify.

The diagram links each definition stage to its corresponding verification or validation stage.

ASAP standards checklist covering hierarchy of controls, risk assessment, reliability, machinery tagging, sensor characterization, PL and SIL determination, and HAZOP
The checklist summarizes the standards and methods that shape ASAP's risk, reliability, and validation workflows.

Standards shown in the checklist

Alongside its core standards, ASAP is influenced by these functional-safety methods and standards:

  • Hierarchy of Hazard Controls (ISO 12100 / ANSI B11.0)

  • Waterfall risk assessment methodology (ISO 13849 / ISO 12100)

  • Reliability Analysis and Component Failure Rates (SN 29500)

  • Risk elements and graphs (ISO 14121-2)

  • Machinery Directive Tagging (2006/42/EC)

  • Data processing to support sensor characterization (IEC 61496)

  • Performance Level and SIL determination (ISO 13849)

  • HAZOP Identification (SAE J2980 / ISO 26262 / IEC 61511)

How the published page explains the core standards

ASAP is built to the core functional safety standards and shaped by the wider stack real programs answer to.

  • IEC 61508. The parent functional safety standard for electrical/electronic systems. Requires assigning a Safety Integrity Level (SIL) to each safety function and proving, with evidence, the design meets it. It's the basis of ASAP's V-Model and its T2 qualification.

  • ISO 13849. Safety-related control systems in machinery. Requires a required Performance Level (PLr) per function, validated against what you built. ASAP calculates PL directly.

  • ISO 26262. Automotive functional safety. Hazard analysis and risk assessment drive an Automotive Safety Integrity Level (ASIL). ASAP handles the risk-assessment side.

Also reflected: ISO 12100 / ANSI B11.0, ISO 14121-2, the Machinery Directive 2006/42/EC, SAE J2980, IEC 61511, SN 29500, and IEC 61496 (optical safety sensors, the basis for the Test Cell's perception testing).

About T2 qualification. T2 tool qualification means an independent assessor has verified that a software tool used in safety work doesn't introduce errors of its own. IEC 61508 requires it. ASAP's tools are T2 qualified against IEC 61508-3 by TÜV Rheinland. It's the only NRTL-qualified toolset covering the full lifecycle, risk assessment through verification and traceability, not just one slice. For you: months of tool validation skipped, and outputs trusted the moment ASAP generates them.

Functional Safety Management

Get your entire team contributing to safety. Manage your safety program, delegate safety tasks, and conduct reviews.

Example shown in the product image

A Functional Safety Concept for an autonomous warehouse robot under ISO 13849-1, marked In Progress.

  • Sections: Safe States, Diagnostics, and Architecture

  • State graph: Normal Operation

  • State graph: Maintenance

  • State graph: Safe Torque Off (STO)

  • State graph: Safe Stop 1 (SS1)

  • State graph: Critical Fault

What the platform covers

  • User and Task Management. Runs the safety program and the assessment process.

  • Hazard and Risk Analysis. Identifies hazards, assesses risk, documents the HARA.

  • Safety Concepts. Develops the functional safety concept from the risks you've found.

  • Requirements. Defines, traces, and manages safety requirements.

  • Systems Design. Turns requirements into a detailed system design.

  • Systems Reliability. Evaluates reliability and works the failure modes.

  • Safety Case. Builds and maintains the safety case for certification.

  • Validation. Plans, runs, and manages system-level testing.

  • Testing. Tests components against their safety requirements.

ASAP Functional Safety Concept for an autonomous warehouse robot under ISO 13849-1, showing safe states, diagnostics, architecture, and a state graph

Easy Onboarding

Most safety work still starts with a blank spreadsheet: no framework, no template, no sense of what comes next.

The Platform is what that spreadsheet never was. It holds the structure, tracks the traceability people otherwise maintain by hand, and at every stage answers the question that eats the time: what do I do next.

Import, don't rebuild. Bring existing HARAs and documents in rather than starting over.

Traceable Safety Environment

One data model connects each hazard to its safety concept, requirement, design, test, and safety case.

A normal certification today spans six places: hazard log in a spreadsheet, requirements in another, clause tracking in one tool, test evidence in another, the safety case in a Word doc, the audit trail in email. The only thing joining them is an engineer copying IDs by hand.

That's where the expensive problems breed. Work gets re-keyed. The line from a passing test back to the hazard that justified it goes cold. And when the HARA changes, the change doesn't travel. Requirement, design, and test drift out of sync, and you find out at the assessor's desk instead of your own.

ASAP replaces that with one chain:

Hazard → Safety Concept → Requirement → Design → Test → Safety Case

Traced both directions. Change the requirement, see the test it breaks. Change the hazard, and every requirement hanging off it gets flagged instead of orphaned. One data model, one source of truth, hazard to safety case.

Intuitive Reliability Calculations

Change a component and the risk score recalculates. Change a requirement and you see, right then, everything downstream that moved. No finding out three weeks later, in a file someone forgot to send.

A few things a spreadsheet can't do:

  • A live HARA. Link mitigations to hazards, watch Performance Level recalculate as you work.

  • Reliability modeling for PL and SIL. SISTEMA functionality, rebuilt for the browser, with your component library in it.

  • One-click documentation. A full, assessor-ready Technical File, formatted how your TÜV assessor wants it.

  • Import, don't rebuild. Bring existing HARAs and documents in rather than starting over.

It connects to the tools you already use (requirements managers, sim environments, issue trackers) so the safety record stays current without re-keying.

Verification and Validation

AI in ASAP drafts the work and proves it was done thoroughly. You stay the one who decides.

Safety Harness is the part nobody else is doing. It's an observability layer that scores every AI action on how thoroughly it draws on the underlying safety data, and turns that into an audit-ready record you can hand a regulator or an assessor. When someone asks how much an AI contributed to a safety decision, and whether it did so rigorously, you have the answer on paper. Safety Harness works on ASAP's own AI and on your external copilots, which means it's how you keep any AI in your safety workflow accountable, not just ours.

Assess and Mitigate Risk

AI capabilities in ASAP accelerate the work, but a person verifies it, and the safety case stays inside the T2-qualified toolset so the outputs are still trusted.

Safety Advisor is an AI copilot inside the Platform. Describe your robot and the environment it works in, and it drafts the starting point: hazard scenarios, tasks, and safety requirements, grounded in ISO 12100, ISO 13849, and IEC 61508. It gets you off the blank page and onto real work in minutes instead of days. Every suggestion is flagged as AI-generated and waits for you to accept, edit, or reject it. It drafts. You decide. Nothing enters your safety case until an engineer has signed off on it.

Together these tools are the two halves of using AI in safety responsibly: Safety Advisor speeds the work up, Safety Harness proves the work was sound. This is also where ASAP's safety story extends past physical systems into AI behavior itself.

INTEGRATIONS

Connect Your Entire Safety Ecosystem

ASAP integrates with the tools you already use. From requirements management to simulation environments, keep your workflow connected.

ASAP integrations including requirements, development, simulation, robotics, cloud, monitoring, and spreadsheet tools
ASAP integration examples:
  • Jama Connect
  • IBM DOORS Next
  • Polarion ALM
  • Jira
  • Confluence
  • GitHub
  • Azure DevOps
  • Linear
  • Slack
  • NVIDIA Isaac Sim
  • MATLAB / Simulink
  • Gazebo
  • Unity Robotics Hub
  • ROS 2
  • AWS IoT Core
  • Grafana
  • Excel
  • Google Sheets

THE SOLUTION

Traceability from Hazard to Hardware

Live Risk Assessment

ISO 12100 compliant HARA that updates dynamically. Link mitigations directly to hazards. If you change a component, the risk score recalculates instantly.

  • Drag-and-drop Hazard Library
  • Real-time PLr Calculation
  • Example shown: Crushing hazard, initial risk High, Light Curtain mitigation, final risk Low (Hazard Analysis: Cell 1, v2.4)
ASAP risk assessment panel showing live hazard classification with ISO 12100 severity and probability ratings

Reliability Modeling

A modern, web-based alternative to SISTEMA. Drag-and-drop architecture to calculate Performance Levels (PL) and SIL ratings instantly.

  • Cloud Component Library
  • Import SISTEMA Files
  • Category 2, 3, 4 Architectures
  • Example shown: Input PL e → Logic PL e → Output PL e
ASAP reliability modeling interface showing component reliability calculations and system failure rate analysis

Automated Documentation

Stop formatting Word documents at 2 AM. Generate a 500-page Technical File with one click, perfectly formatted for your TÜV assessor.

  • Exports assessor-ready PDF and XML files
  • Example shown: Export Technical File
ASAP technical documentation export panel showing automated report generation for safety assessment files

QUICK START

Get Your Safety Case Started with ASAP Templates

Autonomous Mobile Robot

Pre-loaded hazard scenarios, ISO 3691-4 compliance structure, and validated mitigation strategies for AMRs in warehouse environments.

  • 45+ Pre-defined Hazards

  • ISO 3691-4 & ISO 13849 Ready

  • Validated Safety Functions

Collaborative Robot

Complete cobot safety assessment framework with ISO/TS 15066 compliance, power & force limiting validation, and risk reduction measures.

  • ISO/TS 15066 Compliance

  • Power & Force Limit Tests

  • Human-Robot Interaction Safety

Industrial Machinery

Machinery Directive 2006/42/EC compliant template with ANSI B11.0 hierarchy of controls and comprehensive risk assessment workflows.

  • Machinery Directive 2006/42/EC

  • ANSI B11.0 Control Hierarchy

  • CE Marking Documentation

Start Your Project in Minutes, Not Months

Each template includes pre-configured hazard libraries, proven mitigation strategies, and standards-compliant documentation structures. Simply customize to your specific application and you're ready to go.

Built where it couldn't afford to be wrong.

ASAP didn't start as a product. It started inside a fortune-5 automation program, stress-tested against real deployments long before anyone else could buy it. That work fed into something that hadn't been done before: a fully autonomous robot certified by TÜV Rheinland.

T2 Qualification

ASAP Platform tools have earned T2 qualification through TÜV Rheinland. That qualification validates the consistency and reliability of the platform and makes it eligible for assessor-qualified use.

Democratization of Safety

ASAP makes advanced safety work accessible to teams of all sizes. It embeds structure, guidance, and automation into every step, so even lean teams can meet the same standards as enterprise leaders.

Automated Documentation

ASAP automatically generates traceable, assessor-ready outputs. Teams spend less time formatting files and more time building. Every safety case is audit-ready from day one.

Automated Inputs & Outputs

ASAP connects your safety workflow to real system data. It automatically updates safety cases when inputs or specs change, reducing rework and improving accuracy across the board.

Guided Process

ASAP brings structure to complex safety work. It's a system you can trust to walk your team from early risk analysis to certification, no matter your experience level.

FAQ

What is ASAP, and what does it cover?

Fennec's functional safety program. It runs the full V-Model (HARA, functional safety concept, requirements, reliability/FMEDA, and test management) with traceability tying every artifact to the next. The tools are TÜV-qualified as offline (T2) tools under IEC 61508-3.

We're partway through the V-Model already. Do we start over?

No. Fennec's team loads your existing artifacts (HARA, SRS, safety concept) so you get traceability from here on. Many teams start small, usually with risk assessment or reliability/FMEDA, before the full V-Model.

Can we bring our spreadsheets in?

Yes. Fennec's team imports Excel-based HARAs and similar docs that roughly follow ISO 12100 structure.

Does it work with Jira?

Yes. Safety requirements built in ASAP push to systems like Jira, while staying fully traceable inside ASAP's safety case.

Can our assessor review work in the platform?

Yes, through an assessor portal. You invite them into a project and control when something's ready; they're notified when a new version is released. The evidence is already where they need it.

Can we get our data out?

Yes, all of it. HARAs to Excel; concepts, requirements, design, and test docs to Word-style files. All revision-controlled. It's your data.

Is our data isolated?

Yes, by design. Your risk decisions and test cases are never shown to another customer, and your data doesn't train anyone else's models.

Can we bring our own AI model, or turn AI off?

Yes to both. The AI layer is configurable per customer, bring-your-own-model included. Every AI suggestion is labeled and waits for a human to accept it; it won't populate an SRS or V&V plan on its own.

Does ASAP cover AI systems, or only physical machines?

Both. Safety Advisor and Safety Harness bring the same rigor to AI-driven systems: Advisor drafts safety work for human verification, and Harness records how thoroughly any AI (ours or your own) drew on the safety data behind each action.

A Fennec engineer reviewing safety evidence at a workstation

See it against your own program.

Bring your standard, your system, and your timeline. We'll show you how the evidence comes together.

30 minutes. No prep required.

Or send us your question

We use Google Analytics cookies to measure how visitors use this site. They are optional and only set if you accept. Privacy Policy