Enterprise DNA

Instead of OpenBOM

Stop renting OpenBOM. Own your engineering change system.

We build around your release process, bring the agreed OpenBOM records across and run your version for you. Your engineers decide what is ready. Your business keeps the history.

OpenBOM Company lists US$90 per editor per month billed yearly, or US$165 billed monthly. Read-only access is free; data records and CAD add-ins are priced separately.

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

The OpenBOM bill

Editors, product records and the connections around them

Compare your actual contract with the work you need done. The published subscription has separate charges for people and product data.

paid

Editors on the Company plan

US$90 per editor per month on yearly billing. Count the people who maintain product records.

calendar_month

A different monthly rate

Company is US$165 per editor per month when billed monthly. Use your billing term when comparing.

database

Product records priced separately

Part numbers, component records and managed design files count toward the data-record dimension.

extension

CAD connections

CAD add-ins carry a separate charge. Scope the design connections your version needs.

sync

ERP connections

ERP integrations are quoted separately. Agree which production and purchasing records need to move.

visibility

Readers already have free access

OpenBOM includes unlimited read-only users. The comparison starts with paid editors, not everyone who views a design.

Your engineering register

Release the right revision with the right evidence

Changes

Start the week with the decisions waiting

See the design decisions that still need an owner or review.

  • check Review open changes by their agreed date.
  • check Separate overdue changes from upcoming work.
  • check Compare unresolved work by author.
  • check Find draft revisions untouched for a month.

Components

See where a part change reaches

Trace the dependency before releasing the next assembly.

  • check List the parents of a component revision.
  • check Follow dependencies through nested assemblies.
  • check Find obsolete components still specified in designs.
  • check Compare components shared across different assemblies.

Release

Keep approval attached to the revision

The free base checks its release conditions before changing a design to released.

  • check Require a reviewer different from the change author.
  • check Freeze a revision after approval.
  • check Recheck that each direct component is released.
  • check Record the operator and release note in the history.

Handover

Keep the instructions with the design

Prepare the review paperwork from the same records.

  • check Flag missing intended use and test references.
  • check Keep safe-use information on each revision.
  • check Produce branded change notices and design handovers.
  • check Add your own release questions and evidence fields.

Make it yours

Design your own OpenBOM replacement

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

2. What it runs

3. Make it fit

4. Your colour

Your business · your OpenBOM 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 OpenBOM 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 Engineering Changes for Claude Code. It runs in Claude Code inside the Claude app, so it feels like any chat you already use.

forum

Engineering Changes for Claude Code

Connected to your own database

Which engineering changes are overdue?

40000000-0000-4000-8000-000000000001

Name
Washdown guard review
Number
PUMP-100
Code
B
Author
Moana
Due
2026-10-03
Status
open
Days_past_due
9

Ask it anything

Questions to ask your engineering records

Each question has a working command in the free base. OpenBOM also offers reporting; the difference here is control over your records and review rules.

chat_bubble Which engineering changes have missed their agreed date?
chat_bubble Which approved designs are ready for release?
chat_bubble Which assemblies still specify an obsolete component?
chat_bubble Which draft designs have been untouched for a month?
chat_bubble Which owners have the most overdue changes?
chat_bubble Which components are shared across assemblies?
chat_bubble Which revisions lack test evidence or safe-use information?
chat_bubble Which assemblies depend on a particular component revision?
chat_bubble What quantities are required through a nested assembly?
chat_bubble Who recorded the last approval or design change?

Switching

How to switch from OpenBOM

A move usually involves exporting each bill of materials, testing the import, checking the draft records and running both systems side by side while you verify the handover.

  1. 1

    Export your BOM records

    Export each single-level bill of materials from OpenBOM as CSV, including part numbers, descriptions, quantities, unit labels and revision names. These are the records the free importer can bring across as drafts. CAD files, attachments, custom properties and historical approvals need a separate agreed migration. Do not assume they are included with the BOM export.

  2. 2

    Test the import first

    Start with a sample BOM and use the import's test run before saving records. If your CSV headings differ, map them to the fields the importer expects. The importer handles one single-level BOM at a time, so plan to repeat the process for additional assemblies and link their revisions after importing.

  3. 3

    Review the import results

    Check the test results before importing for real. Confirm that headings, part numbers, descriptions, quantities, unit labels and revisions have been read as intended. Identical lines are skipped, while conflicting descriptions or quantities stop the batch. Lines absent from the input are not silently deleted. Imported records are drafts, not historical approvals.

  4. 4

    Run both systems side by side

    For a short agreed period, keep OpenBOM as your live reference while you use the new register for selected work. Compare imported component lists, quantities and revisions with OpenBOM. Have the people who review changes check that the new records and evidence references support their handover. Note any gaps and correct the mapping or agreed migration before moving more work.

  5. 5

    Switch off OpenBOM

    Once the checks are complete and your team is working from the new register, agree a final cutover point. Confirm that remaining in-flight records are covered by the migration scope and that the people responsible know how to access and maintain the database. Then stop using OpenBOM in line with your account arrangements.

construction

Where the real effort goes

The real work is usually mapping your own fields and review rules, then deciding which history to bring. The BOM import creates drafts, not historical approvals, and CAD files, attachments and custom properties need a separate agreed migration. If you have Enterprise DNA run the move, they handle this migration work as part of the scoped setup.

Not ready for a call?

Get your OpenBOM switch plan by email

We will send you the step-by-step plan for moving your business off OpenBOM, 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 run it

Choose who builds and operates your version

Open source

Do it yourself

Free open-source base

  1. 1 Clone Engineering Changes for Claude Code and install its dependencies.
  2. 2 Run npm run demo and inspect the fictional engineering records.
  3. 3 Open it in Claude Code, Codex, OpenCode or Cursor.
  4. 4 Test your OpenBOM CSV import, then arrange your database, access and backups.
Get it on GitHub

Built around your business

We customise it

One setup fee, then an agreed retainer

  • check Map the OpenBOM records you need to retain.
  • check Add your fields, evidence requirements and review roles.
  • check Build a web front end or use a different stack when your workflow requires it.
  • check Agree CAD, document storage and production connections before implementation.
Get your version built

Omni by Enterprise DNA

We run it for you

One setup fee, then a monthly retainer

  • check Install your engineering register inside Omni by Enterprise DNA.
  • check Connect the agreed records to the rest of your business.
  • check Operate backups and the access arrangements agreed with you.
  • check Maintain your review rules as products and responsibilities change.
Book a discovery call

Questions

Instead of OpenBOM, answered

Which OpenBOM records can we bring across? expand_more

The free version imports a single-level bill of materials exported as CSV. Part numbers, descriptions, quantities, unit labels and revision names become draft records. Export headings can be mapped. CAD files, attachments, custom properties and historical approvals need a separate agreed migration.

Does this replace our CAD tools? expand_more

Keep the design tools your engineers use. The free base holds revision and approval records, with references to supporting evidence. We scope CAD connections, file storage and any editing screens as part of your custom version.

Does a passed check mean a design is safe? expand_more

No. The checks flag missing design information and unreleased components. Your engineers assess evidence and design safety. The included record prompts reference New Zealand upstream duties; other jurisdictions and specialist product rules need their own review.

What happens when an approved design changes? expand_more

Approval freezes that revision in the free base. A released design stays in the history and new work starts a new revision. Your version can add the change-request and authorisation rules your team uses.

What will Enterprise DNA charge, and how do we compare it? expand_more

We scope a setup fee and an ongoing retainer around your records, connections and operating needs. Compare that with your actual OpenBOM contract, including editor seats and add-ons. Free software still needs hosting, access management and maintenance.

Bring one product and its next release decision

Book a 30-minute call with Sam. Walk through one assembly, the evidence your reviewers need and your current OpenBOM bill. Agree what your version must hold, what needs connecting and who will operate it.

Book a discovery call Get the free version

Engineering Changes for Claude Code is free and open source, published by Enterprise DNA.

Done paying for OpenBOM?

Get your version built