Enterprise DNA

Instead of PQ-FMEA+

Reviewing PQ-FMEA+ costs? Own your failure review system.

We build your version around your engineering review, map your PQ-FMEA+ export and run it for you. Your engineers keep control of ratings, priorities and acceptance.

PQ-FMEA+ lists €837 net per month on a twelve-month subscription, €10,044 for the year. Paying annually is €7,536 net. Perpetual licences are also available. Compare your actual licence and payment terms.

Get your version built See it working
  • check_circleYour data in a database you own
  • check_circleOpen source, no lock-in
  • check_circleBuilt and run by Enterprise DNA

What the licence pays for

An analysis is more than its annual subscription

PQ-FMEA+ includes specialist analysis and document tools. Choose the review work you want to own and agree the engineering requirements before switching.

payments

A yearly commitment

The monthly-payment subscription totals €10,044 net over twelve months. The lower annual-payment option is €7,536 net.

location_on

A licensed location

The public subscription covers unlimited workstations at one company location. Corporate and multi-location terms are quoted separately.

update

Updates and support

Subscription plans include updates and technical support. Perpetual licensing is a separate option, so check what your current agreement already gives you.

account_tree

Failure analysis structure

The software connects failure analysis with control plans and process flow. Your owned version can focus on the failure chains and review evidence your team uses.

assignment

Action follow-up

PQ-FMEA+ provides employee task lists. Bring the due dates, completion evidence and independent checks into your own weekly review.

description

Documents and revisions

PQ-FMEA+ exports analysis records and keeps revision history. Your version retains the original export beside the records your engineers review.

Your working records, connected

Own the review that keeps the analysis useful

ENGINEERING ROUND

See where review is missing

Bring recorded priority, severity and current review evidence into the same conversation.

  • check Show high-severity failures separately
  • check Keep missing ratings visible
  • check Record the methodology behind each priority
  • check Find failures with no review of the latest version

ACTION EVIDENCE

Separate done from checked

An action needs completion evidence and a different named reviewer before it is marked verified.

  • check List overdue work by owner
  • check Record the test or document behind completion
  • check Record an independent verification reference
  • check Flag evidence tied to an older failure version

CONTROL PLANS

Keep controls tied to the failure

A change leaves the old control visible and identifies where a fresh link is needed.

  • check Record the characteristic and check method
  • check Keep the frequency and reaction plan together
  • check Name the person responsible
  • check Show controls that cover an earlier failure version

SOURCE AND HISTORY

Keep the evidence behind a change

Retain the original workbook and source row values while your own review history grows.

  • check Reconcile the imported failure count
  • check Keep unmapped values as source evidence
  • check Read earlier and current values in the change history
  • check Prepare branded analysis and action working papers

Make it yours

Design your own PQ-FMEA+ replacement

Everything starts from the open-source base. Then it gets your name, the parts you run, your rules and your data from PQ-FMEA+. Try it here, and we build the real one.

2. What it runs

3. Make it fit

4. Your colour

Your business · your PQ-FMEA+ replacement Your version
YB Your business

auto_awesome

Answered from your own database

Build my version

We build it from the open-source base, bring your PQ-FMEA+ data across and run it for you.

What it looks like

Ask it like you would ask a colleague

Real answers from the demo data that ships with Failure Review for Claude Code. It runs in Claude Code inside the Claude app, so it feels like any chat you already use.

forum

Failure Review for Claude Code

Connected to your own database

Which failures need review and follow-up?

code | analysis | mode | severity | action_priority | rpn | reviewed | open_actions | current_controls --------|-----------|-----------------------|----------|-----------------|-----|----------|--------------|----------------- PACK-01 | DEMO-PACK | Wrong label | | | | false | 1 | 0 FILL-02 | DEMO-FILL | Loose lid | 9 | M | 54 | false | 1 | 0 FILL-01 | DEMO-FILL | Underfilled container | 8 | H | 192 | true | 1 | 1

Ask it anything

Ten questions your review desk answers

These run against the working demo. They show the joins and local checks in your version, without claiming that PQ-FMEA+ cannot make similar reports.

chat_bubble Which high-severity failures still need a current engineering review?
chat_bubble Which improvement actions are late, and who owns them?
chat_bubble Which controls refer to an older version of a failure?
chat_bubble Which ratings have no recorded scoring basis?
chat_bubble Who has the largest overdue action list?
chat_bubble Which causes appear in more than one analysis?
chat_bubble Which analyses have had no edit or note in thirty days?
chat_bubble Which completion records became stale after a failure changed?
chat_bubble Who changed a failure and what did the earlier record say?
chat_bubble Which source workbook supplied this failure?

Switching

How to switch from PQ-FMEA+

The move involves exporting your FMEA sheet, mapping its columns, testing the import and reconciling the records before you rely on the new database.

  1. 1

    Export your FMEA sheet

    Export the FMEA sheet from PQ-FMEA+ as an XLSX workbook. Include the failure records and any fields you need to keep for review, such as ratings, priorities and action details. PQ-FMEA+ documents native XLSX export, but check with PQ-FMEA+ if you are unsure which export options your account allows. Keep the original workbook so you can compare it with the imported records.

  2. 2

    Map and test the import

    Map the columns in your workbook to the fields in Failure Review, then run the import in test mode before loading records for everyday use. The test lets you check how the mapping handles your data without treating the import as ready for use. Do not assume that every PQ-FMEA+ field has a direct match. Resolve unclear mappings with your engineers before proceeding.

  3. 3

    Reconcile flagged records

    Review the import results and check every failure row against the workbook. The import retains unmapped source values, and imported priorities are marked unreviewed. A malformed row stops the whole import, so correct the source or mapping and test again. Confirm ratings, priorities and action details with the people responsible for them. Treat action information from the source as evidence to review, not as an approved current action.

  4. 4

    Run both systems briefly

    Keep PQ-FMEA+ available while your team uses Failure Review for a short period. Compare the records and working papers used in your normal review work, and ask engineers to check that important history and current actions are represented as expected. Resolve differences before relying on the new database. Historical approvals, diagrams and action assignments may need separate mapping or review, so do not assume they transferred with the failure rows.

  5. 5

    Switch off PQ-FMEA+

    Once your team has checked the imported records and agreed that the new setup supports its review work, stop using PQ-FMEA+ for current records. Keep the original workbook and any other records you need to retain under your normal business practices. Confirm that the database and its backups are being managed appropriately before you rely on it as the working record.

construction

Where the real effort goes

The main effort is usually mapping your own fields and review rules, then deciding which history to bring across. Failure rows can be imported from the workbook, but historical approvals, diagrams, action assignments and custom rating definitions need separate mapping or review. Validate the mapping against an actual export. If Enterprise DNA installs and runs your version, it handles this mapping and import work with you.

Not ready for a call?

Get your PQ-FMEA+ switch plan by email

We will send you the step-by-step plan for moving your business off PQ-FMEA+, what the move really involves, and how we would do it for you.

One email with your plan. No spam, and you can unsubscribe any time.

Three ways to own it

Start with the free base or have your version built

Open source

Do it yourself

Free, open source

  1. 1 Clone the repo and run npm install, npm test and npm run demo
  2. 2 Open it in Claude Code, Codex, OpenCode or Cursor
  3. 3 Map your PQ-FMEA+ XLSX export and run import pq-fmea with --dry-run before importing
  4. 4 Review the records and set up controlled access and backups for shared use
Get it on GitHub

Built around your business

We customise it

One setup fee, then a retainer for ongoing work

  • check Your failure fields, scoring references and review rules
  • check Your PQ-FMEA+ export mapped and reconciled with engineering
  • check Your control-plan documents and customer requirements
  • check A web front end or a different stack where your team needs one
Get your version built

Omni by Enterprise DNA

We run it for you

One setup fee, then a retainer

  • check Installed with controlled access and backups
  • check Your weekly review and action working papers prepared
  • check Kept working as processes and requirements change
  • check Run through Omni by Enterprise DNA beside the rest of your business
Book a 30-minute review

Questions

Instead of PQ-FMEA+, answered

Is this a complete PQ-FMEA+ replacement? expand_more

The free base covers failure records, recorded ratings and priorities, action evidence, control links and working documents. Enterprise DNA scopes the diagrams, specialised forms, screens and integrations your version needs. Check that scope with your engineers before changing the software they rely on.

Will it certify our analysis or decide that a process is safe? expand_more

No. It checks whether review records and evidence are complete and current. Engineers supply the rating method, priority and acceptance decisions. A multiplied risk score is shown for context and never decides whether a risk is acceptable.

Can we bring our PQ-FMEA+ history across? expand_more

PQ-FMEA+ exports its analysis to a workbook. We map its columns, do a test run and reconcile the rows with you. The free base keeps the source workbook and row values. It has been tested with a synthetic workbook, so your actual export needs validation. Historical approvals, diagrams and action assignments need separate mapping or review.

What does PQ-FMEA+ cost compared with this? expand_more

Its published subscription is €837 net per month on a twelve-month commitment, or €10,044 net for the year. Annual payment is €7,536 net, and perpetual licences are also offered. The price list was checked on 12 November 2026. The free base has no licence charge. Enterprise DNA agrees one setup fee, then a retainer to customise and run your version.

What happens when a failure or control changes? expand_more

A failure edit keeps the earlier evidence but marks the previous review and control links as out of date. Completion evidence tied to an older version is flagged too. Your team reviews the change and records fresh evidence before relying on it.

Bring the licence and one real analysis

In a 30-minute call with Sam, compare your PQ-FMEA+ agreement with the review work you want to own. We can map the first analysis, agree your version and explain the setup fee and ongoing retainer.

Book a 30-minute call with Sam Get the free version

Failure Review for Claude Code is free and open source, published by Enterprise DNA.

Done paying for PQ-FMEA+?

Get your version built