Enterprise DNA

Instead of Intelex

Stop renting Intelex. Own your management of change system.

We build your version around how your sites control change, bring your Intelex change history across and run it for you. Start with your sign-off rules and the changes in operation today.

Intelex lists its entry Safety Essentials plan from US$44 per user a month, with a 25-user minimum billed annually. Management of Change is not in that plan, and the plans that cover it are quoted privately.

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 recurring bill

What your Intelex agreement pays for

Intelex publishes one price, for its entry safety plan. Management of change sits in the Advanced and Enterprise plans, which are quoted. Here is what that bill buys, set against owning the records yourself.

Layers

A whole platform for one workflow

Change control is one application on a platform that also covers incidents, environment, quality and sustainability. It is not in the entry plan, so a site that wants it is quoted for a plan across that wider platform.

Users

A login for everyone who signs

The entry plan is priced per user with a 25-user minimum. Every engineer, supervisor and manager who reviews or signs a change needs a seat.

Settings

Configured forms and workflows

Intelex describes its Advanced plan as services-assisted. Your change form, stages and checklists are set up with that help, on a platform you rent.

BarChart

Dashboards someone else designed

Reporting depth rises with the plan, from pre-defined dashboards to tailored reports. The questions you can ask depend on what has been built.

Smartphone

The phone app

Intelex lists its iOS and Android app with the Advanced plan. Its Essentials help pages say the mobile app is not supported on Essentials.

FileText

Documents and training as add-ons

On the entry plan, document control and training management are add-ons. A change is not finished until its procedures are updated and its people trained.

Your change control

The site change meeting, run from your own records

Before the change

No sign-off without the thinking behind it

Every change carries its technical basis, its effect on safety and health, and the review that tested it.

  • check Risk level decides which roles must sign
  • check Medium and high risk changes need a recorded risk review before anyone signs
  • check Flag changes that touch procedures, drawings or the safety case
  • check A rejection is kept; a sign-off is never overwritten

Start-up

Nothing goes live with a gap open

Start-up is refused until every gate passes, and the reason is listed in plain words.

  • check All sign-offs in, none rejected
  • check Training, procedure updates and checks done with evidence
  • check Pre-start-up safety review recorded by name and date
  • check At a major hazard site, the regulator notice recorded first

Temporary and emergency

Bypasses that cannot quietly become permanent

Temporary changes carry an expiry from the day they are raised. Emergency repairs go live first and collect their sign-offs after.

  • check Expired temporary changes top the weekly list
  • check Every extension needs a reason, and repeat extensions are flagged
  • check Emergency repairs missing sign-offs after a week are flagged
  • check Close-out records whether the plant was put back or the change made permanent

Your records

Answers your current dashboard was never built for

Ask in plain words and get the answer from your own change history, with the rule behind every flag.

  • check Days from request to start-up, by site and risk
  • check Who holds the most overdue change actions
  • check A branded change record and pre-start-up certificate for every change
  • check Every finding tied to the New Zealand or Australian rule it comes from

Make it yours

Design your own Intelex replacement

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

2. What it runs

3. Make it fit

4. Your colour

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

forum

Management of Change for Claude Code

Connected to your own database

What needs attention on our plant changes this week?

MOC-0004

Site
AKL
Title
Raise working inventory of tank T-104 from 40...
Owner
Aroha Ngata
Rule
safety case change not notified
Detail
major hazard site, status approved
Days
35

MOC-0006

Site
GEE
Title
Engineered clamp on leaking steam line SL-7
Owner
Sam Okafor
Rule
emergency change without approvals
Detail
missing safety, site_manager
Days
12

MOC-0005

Site
GEE
Title
Change CIP caustic dosing logic in PLC-3
Owner
Sam Okafor
Rule
started up with pre-start-up actions open
Detail
1 open: A-010
Days
10

MOC-0002

Site
HB
Title
Temporary bypass of high-level switch LSH-12 ...
Owner
Hemi Walker
Rule
temporary change past expiry
Detail
expired 2026-10-30, still in place
Days
5

MOC-0003

Site
AKL
Title
Change caustic soda supply from 50 percent to...
Owner
Aroha Ngata
Rule
waiting on approval
Detail
missing safety
Days
25

MOC-0001

Site
AKL
Title
Replace solvent transfer pump P-201 with a se...
Owner
Aroha Ngata
Rule
action overdue
Detail
A-004 drawing: Update P&ID 201 to show the ne...
Days
20

MOC-0007

Site
HB
Title
Hire compressor during overhaul of screw comp...
Owner
Hemi Walker
Rule
temporary change expiring
Detail
expires 2026-11-13
Days
9

MOC-0002

Site
HB
Title
Temporary bypass of high-level switch LSH-12 ...
Owner
Hemi Walker
Rule
action overdue
Detail
A-006 inspection: Fit the replacement LSH-12 ...
Days
5

MOC-0001

Site
AKL
Title
Replace solvent transfer pump P-201 with a se...
Owner
Aroha Ngata
Rule
close-out overdue
Detail
in operation since 2026-09-20
Days
45

MOC-0008

Site
GEE
Title
Reduce night shift on line 2 from three opera...
Owner
Tom Burke
Rule
draft gone quiet
Detail
raised 2026-09-25, not sent for review
Days
40

Ask it anything

Ten questions your change records answer

These run against the working demonstration today. Your own version asks them of your sites, your sign-off rules and your history.

chat_bubble Which temporary changes have passed their expiry date and are still in place?
chat_bubble Which changes went into operation with training or procedure updates still open?
chat_bubble Which changes are waiting on a sign-off, and whose?
chat_bubble Which changes at a major hazard site affect the safety case and have not been notified?
chat_bubble Which emergency changes still lack their sign-offs a week after the repair?
chat_bubble Which operating procedures and drawings are still to be updated after a change?
chat_bubble How many days does a change take from request to start-up, by site and risk?
chat_bubble Who holds the most overdue change actions?
chat_bubble Which temporary changes have been extended more than once?
chat_bubble Which changes have been in operation for a month without being closed out?

Switching

How to switch from Intelex

The move involves exporting your change requests and actions, mapping your records, checking the import, and running both systems side by side before you switch.

  1. 1

    Export changes and actions

    Export your Management of Change report view and its actions from Intelex. The migration path uses a CSV export of change requests and actions. What you can export may depend on your account and site setup, so check with Intelex if you cannot find those reports. Sign-offs, risk review worksheets and attachments do not come across in a simple CSV export, so identify what you need to retain separately.

  2. 2

    Prepare the new records

    Set up your sites in the new system before loading the records. Then use its import process to bring in the exported change requests and actions. Start with a test run rather than loading the records for real straight away. The test shows what the importer can match from your export without committing the import, giving you a chance to review the results first.

  3. 3

    Review the import findings

    Check the test results, including the counts and any fields or records the importer could not match. Intelex forms vary by configuration, so the importer reports mismatches instead of guessing. Review the flagged items against your source records and decide how to handle them. When you are satisfied with the mapping and findings, run the import for real.

  4. 4

    Run both systems briefly

    Keep Intelex available while your team checks the imported records against current change work. Confirm that people can find the changes and actions they need, and agree which system is the source of truth during this period. The two systems do not automatically stay in sync, so make a clear plan for recording new changes and updates while both are in use.

  5. 5

    Switch off Intelex

    Before stopping Intelex, reconcile the records created or updated during the side-by-side period and confirm that the information you need is retained. Make sure you have separately kept any sign-offs, review worksheets or attachments that were not included in the CSV import. Once your team is ready to work in the new system, stop using Intelex for change control.

construction

Where the real effort goes

The main work is usually mapping your Intelex fields and rules to the new records, then deciding how much history to bring across. The importer handles change requests and actions from a spreadsheet export, but it does not bring across sign-offs, risk review worksheets or attachments in a simple CSV. If Enterprise DNA installs and runs it for you, they handle this mapping as part of the migration.

Not ready for a call?

Get your Intelex switch plan by email

We will send you the step-by-step plan for moving your business off Intelex, 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, 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 and ask what needs attention
  3. 3 Set up your sites and sign-off rules, then test your Intelex export with a dry run
  4. 4 Put your logo on the change records and pre-start-up certificates in brand.json
Get it on GitHub

Built around your business

We customise it

One setup fee, then a retainer for ongoing work

  • check Your change types, risk matrix, sign-off roles and stages
  • check Your Intelex change history mapped and checked, sign-offs and attachments included
  • check A phone form for the plant floor or a web front end if your team wants one
  • check Links to your maintenance, document and training systems
Get your version built

Omni by Enterprise DNA

We run it for you

One setup fee, then a retainer

  • check Installed with access, backups and ownership agreed
  • check The weekly change review prepared for your site meeting
  • check Expiring bypasses and overdue actions chased before they become findings
  • check Run through Omni by Enterprise DNA beside the rest of your business
Book a change control review

Questions

Instead of Intelex, answered

What does Intelex cost compared with this? expand_more

Intelex lists its entry Safety Essentials plan from US$44 per user a month with a 25-user minimum, billed annually, and management of change is not in that plan. The plans that include it are quoted privately, so bring your agreement. The free version has no licence fee; hosting and your agent subscription are separate. Enterprise DNA builds and runs your version for one setup fee, then a retainer.

Can you bring our Intelex change history across? expand_more

Yes. The free version reads a spreadsheet export of your change requests and their actions, reports anything it cannot match, and does a test run first. Intelex forms are set up differently at every site, and sign-offs, review worksheets and attachments do not come out in a simple export. Mapping those is part of what we do for an installed version.

Does this meet our obligations as a major hazard facility? expand_more

It records what the rules expect a change process to show: the technical basis, the effect on safety, the review, the sign-offs, training before start-up, updated procedures and the regulator notice. Each check cites the New Zealand or Australian regulation it comes from. It supports your own review; it does not certify compliance or decide whether a change needs a notice.

Our operators and supervisors are not going to use a chat window. What then? expand_more

They do not have to. The change records and the weekly list print in your brand, and the same records can sit behind a simple phone form or a screen in the control room. We build that into your version where your team needs it, on the database you own.

What do we keep if we stop working with you? expand_more

Everything. The database, your version and the full change history, sign-offs and activity log included, are yours. A complete snapshot exports in one step, and we agree access, backups and recovery with you when it is set up.

Bring your change register and your Intelex bill

Spend 30 minutes with Sam. We will look at how your sites control change today, the temporary changes you have in place, and what your own version should do first.

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

Management of Change for Claude Code is free and open source, published by Enterprise DNA.

Done paying for Intelex?

Get your version built