Enterprise DNA

Instead of MEX

Stop renting MEX. Own your plant maintenance system.

We build your version around your plants, stores and maintenance routines, map your MEX records and run the agreed system for you. Omni by Enterprise DNA brings maintenance into your business Command Centre.

MEX lists starting prices of $1,080 for Advanced, $1,200 for Professional and $1,380 for Enterprise, per named user per year. Its pricing page does not state the dollar currency or tax treatment. Confirm both in your quote.

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 MEX bill covers

Named users, plan levels and your maintenance records

MEX prices its plans per named user. The free version gives your planner an owned maintenance record. Enterprise DNA scopes the migration, connections and field experience around the work your team actually does.

badge

Named-user access

The published starting prices apply to named-user licences. Compare the people on your quote with who actually plans and records the maintenance.

assignment

Work orders and requests

Advanced includes work-order and request management. The owned base records repairs, assignments, due dates and completion evidence.

event_repeat

Preventive scheduling

Advanced includes preventive scheduling. Your own service plans use recorded intervals and operating-hour readings.

inventory_2

Stores management

Professional adds inventory and stores management. The free base records spares, issues, receipts and internal reorder requests.

timer

Time and cost tracking

Professional adds time and cost tracking. The owned base totals recorded labour minutes, downtime and issued-parts cost, keeping currencies separate.

location_on

Multi-site management

Enterprise adds multi-site management. Your own database groups assets and open work by site, with access arrangements scoped for your team.

Your maintenance system

Start with the work the planner does every week

The backlog

Find the repairs that need a decision

Bring overdue jobs, missing assignments and parts delays into the same weekly review.

  • check List overdue work on critical assets
  • check Find jobs untouched for two weeks
  • check Group the backlog by person and site
  • check Record who finished the job and the supporting evidence

Preventive work

Service by date or running hours

Review approaching services and generate the work that is due. Repeating the review does not create another open copy of the same scheduled job.

  • check See services due in the coming week
  • check Catch equipment over its hour threshold
  • check Record cumulative readings with the operator named
  • check Advance the next service after recorded completion

Stores

Know what the repairs have consumed

Keep the physical stock count and the work record connected. Issue parts against a job and review the reorder list.

  • check Reject issues above the recorded stock count
  • check Keep the cost of each issued part
  • check Prepare internal parts requests
  • check Record full receipts once, with the delivery reference

Evidence and ownership

Put the maintenance history under your control

Keep instructions, inspection references and work records together. Change the questions and paperwork as your operation changes.

  • check Flag missing instructions and registration references
  • check Show overdue inspections and recorded defects
  • check Produce branded work packs and asset histories
  • check Combine your own fields in a review built for your site

Make it yours

Design your own MEX replacement

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

2. What it runs

3. Make it fit

4. Your colour

Your business · your MEX 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 MEX data across and run it for you.

What it looks like

Ask it like you would ask a colleague

Real results from the included fictional plant records. The dates come from the demo run. No customer information is shown.

forum

Plant Maintenance for Claude Code

Connected to your own database

What needs attention before we plan the week?

WO-1001

Set ti
CV-01
Tle st
Replace belt bearing
Atus da
Waiting parts
Ys overdue as
5
Signed to
Mia Patel

WO-1002

Set ti
AC-01
Tle st
Investigate pressure drop
Atus da
open
Ys overdue as
-2

Ask it anything

Ten questions your maintenance record answers

These work on the included fictional records. MEX also provides reporting and configurable dashboards. Your version lets you change the questions around your own site rules.

chat_bubble Which critical assets have overdue work?
chat_bubble Which maintenance plans are due by date or meter?
chat_bubble Which jobs have been untouched for two weeks?
chat_bubble Which repairs are waiting for parts?
chat_bubble Which stores items are at or below their reorder point?
chat_bubble Who has the largest open maintenance workload?
chat_bubble Which sites have the most overdue jobs?
chat_bubble Which assets have the most recorded downtime?
chat_bubble Which assets consumed parts, separated by currency?
chat_bubble Where are instructions, registrations or inspection records missing?

Switching

How to switch from MEX

A move usually involves exporting and checking your asset register, mapping the records you need, then comparing the new database with MEX before you stop using it.

  1. 1

    Export the records

    Ask MEX how to export what your account allows, usually CSV or Excel. Start with the asset register, then export the work history, service plans, meter readings, stores records and attachments you want to bring across. Keep the original exports unchanged. MEX does not publish one universal column layout, so check the available export options with MEX before you plan the import.

  2. 2

    Preview the asset import

    Start with the asset-register import and review its preview before loading records. Match your column headings where they differ, and check which columns will be mapped. The import supports explicit mapping, duplicate checks and keeps original columns. Treat work history, schedules, readings, parts and attachments as separate mapping work rather than assuming they will come across with the asset register.

  3. 3

    Review import checks

    Review the preview and duplicate checks before proceeding. Investigate records the import identifies, and correct any column mapping that does not match your data. The asset-register import does not cover all your MEX history, so keep those separate records in view and plan how they will be mapped before treating the move as complete.

  4. 4

    Run both side by side

    Keep MEX available while you use the new database for a short parallel check. Compare asset records and the history you chose to import against MEX, and investigate gaps or mismatches. Keep original export files and ask your maintenance team to confirm the new records support the work they need to do. Do not end MEX access until the comparison is acceptable.

  5. 5

    Switch off MEX

    Once you have checked the imported records and working process, make the new database your working record and end MEX only when you are ready. Keep the original exports and confirm you can access the records you need. The new base is a database with Claude Code, not a web front end.

construction

Where the real effort goes

The import itself is not usually the hardest part. The real work is mapping your MEX fields and site rules, then deciding how much work history, service plans, readings, stores data and attachment evidence to bring. The asset-register import is provided, while other history needs separate mapping and reconciliation. If Enterprise DNA installs and runs your version, Enterprise DNA handles this work with you.

Not ready for a call?

Get your MEX switch plan by email

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

Choose how much you want us to handle

Open source

Do it yourself

Free software

  1. 1 Clone the repo and run npm install
  2. 2 Run npm run demo, then open it in Claude Code, Codex, OpenCode or Cursor
  3. 3 Try the weekly review and inspection checks on the fictional records
  4. 4 Import your MEX asset CSV with the supplied mapping options into a fresh database
Get it on GitHub

Built around your business

We customise it

A scoped setup fee

  • check Your fields, service rules and paperwork
  • check Your MEX exports mapped and checked
  • check A web front end or different stack if you want one
  • check Connections and field capture agreed around your operation
Get your version built

Omni by Enterprise DNA

We run it for you

One setup fee, then a retainer

  • check Installed and connected through Omni by Enterprise DNA
  • check Migration checks against your actual MEX records
  • check Backups, access and ongoing operation agreed with your team
  • check Your maintenance record alongside the rest of your business
Book a call with Sam

Questions

Instead of MEX, answered

What does MEX cost, and what are we comparing? expand_more

MEX lists Advanced from $1,080, Professional from $1,200 and Enterprise from $1,380 per named user per year. The page does not specify currency or tax treatment, so check the quote. The free version has no software licence fee. Hosting and agent usage are separate, while Enterprise DNA scopes customisation and operation with you.

Can we bring our MEX history across? expand_more

The included import handles an asset-register CSV, with a preview and column mapping when your labels differ. Work history, service plans, readings, stores and attachments need separate mapping. Enterprise DNA reviews those exports and reconciles the records before you switch. Keep the original files and compare the result with MEX.

What about technicians on phones and offline work? expand_more

Enterprise DNA builds the agreed field experience into your version, including mobile capture, photos and offline needs where required. We scope those workflows with your technicians before changing how they work. The free base serves the maintenance planner through an owned database and printable summaries.

Does an inspection check prove the plant is safe? expand_more

No. The checks flag missing instructions, registration references, overdue inspection dates and recorded defects. Your competent people set the actual intervals and assess the plant. A defect puts the record on hold. Nothing automatically releases plant or replaces isolation, inspection or site approval.

Who owns it if we stop the managed service? expand_more

You own your database and the free base is open source under an MIT licence. You can export the complete record. Enterprise DNA agrees the hosting, access, backup and handover arrangements with you. Managed operation is one setup fee, then a retainer.

Bring your MEX bill and the maintenance backlog

Book 30 minutes with Sam. We look at the annual bill, one plant register and the jobs your team repeats each week, then agree what your own version needs to cover.

Book 30 minutes with Sam Get the free version

Plant Maintenance for Claude Code is free and open source, published by Enterprise DNA.

Done paying for MEX?

Get your version built