USE CASE
“We don’t really have a maintenance system. We have a spreadsheet and Dave.”
If that sentence describes your plant, you are in the majority, and you are not behind. Plenty of large, capable, profitable manufacturers run maintenance on a shared spreadsheet, a folder of PDFs, a whiteboard, and two or three people who have been there long enough to know what the machine sounds like when it is about to go. This page is about what to do next, and about why the software you have looked at so far felt like it wanted a year of data entry before it gave you anything.
What kind of software am I actually looking for?
What you are describing is maintenance execution software. Here is the field, in the terms a plant would use:
Machine monitoring / OEE
“We don’t know what the line is doing — downtime, rate, causes.” Measures the equipment’s performance. Tells you a line is running slow. Does not help anyone fix it.
Computerised maintenance management system (CMMS)
“Work gets done but nothing gets recorded, and nobody knows what is due.” Work orders, preventive maintenance (PM) schedules, asset records, history. The administrative backbone.
Maintenance execution — this is MYREX
“The knowledge of how to actually do the work lives in three people’s heads.” The system the technician works in — procedures, guided steps, the equipment itself, and the record of what was done.
Assembly work instructions
“We need to build the product correctly.” Guides building a product, usually from a CAD model. A different job from maintaining the machine that makes it.
MYREX is the maintenance-execution row, and it covers the CMMS row too: work orders, a preventive maintenance calendar with recurring events, asset history, completion records. What makes it different is that the entry point is a high-definition 3D capture of the actual machine rather than a list of asset records to be typed in. This is what MYREX calls a Spatial CMMS.
Why did the last system we looked at feel like so much work?
Because most maintenance software starts from a database that is empty until you fill it. Before it does anything useful you owe it an asset hierarchy, an equipment list with numbers, a procedure library someone has to write, and a PM schedule someone has to decide. That is months of work by the people who are already the busiest in the plant — and it produces nothing visible until it is mostly finished. That is also why so many of these projects stall before they finish. The effort is front-loaded and the payoff is not. MYREX inverts the order. The capture of the machine exists from day one and is immediately useful — a technician can open it, look at the machine, and find the spot. Procedures, notes, photos and history attach to it as work happens, in the place they belong, rather than being written into a void in advance.
What does a first month look like?
Pick one line
Not the plant. One line, ideally the one that causes the most argument.
Capture the machines on it
A scheduled on-site session per machine. Visual access to where maintenance happens.
Put the knowledge where it goes
The things people already know — this is the fitting that leaks, this guard has to come off first, this sensor moves during changeover — get pinned to those spots as photos, video and notes, as they come up.
Run the work through it
Work orders and PMs on that line go through MYREX. Completion writes to the record.
Look at what accumulated
After a month the asset history on that line is real, and it was produced by doing the work rather than by a data-entry project.
The specific test worth applying at the end of the month: ask a technician who did not do the work to find the last thing that was done to a particular spot on the machine. On a spreadsheet that question has no answer. That is the difference you are buying.
What about the spreadsheet we already have?
Keep it until it is genuinely redundant — nobody should be maintaining two systems on faith. The spreadsheet is usually a PM schedule plus an equipment list, and both are worth bringing across. Talk to us about what you have rather than reformatting anything in advance.
What about the knowledge in people’s heads?
This is the reason the timing matters. The spreadsheet is recoverable. The person who knows why that bearing runs hot is not, and the maintenance workforce is retiring faster than it is being replaced. Capturing that knowledge as a document project almost never works, because writing down everything you know is an enormous unstructured task that nobody has a spare month for. Capturing it in place — one note, one photo, one annotation at the spot on the machine, while the work is happening — is a small task that happens many times.
What actually ships today?
High-definition 3D capture of each machine
Shipped
Photos, video and notes pinned to exact locations on the machine
Shipped
Abnormality tags raised on the 3D scene, carrying the exact location
Shipped
Step-by-step guided mode
Shipped
Work orders — create, assign, complete
Shipped
Preventive maintenance (PM) calendar with recurring events linked to locations on the machine
Shipped
Asset pages with full activity history
Shipped
Report-a-problem escalation
Shipped
Media library
Shipped
Search across assets, marks, media, procedures, procedure steps and activity
Shipped
Manager dashboard — open, overdue, due-today and unassigned counts, with due dates
Shipped
Audit log, secured by a SHA-256 hash chain
Shipped
Attestation on completed work
Shipped
Microsoft Entra sign-in
Shipped
Per-step location anchoring of procedures
In development
Spanish (LatAm)
In development
Search is plain keyword matching — not full-text, fuzzy, semantic or instant. The audit chain covers maintenance records — procedures, work records and attestations, and changes to them; administrative changes to accounts and roles are recorded but sit outside the chain.
Frequently asked
We have no maintenance system at all. What should we use?
Look for maintenance execution software rather than starting with a monitoring tool. The first thing to fix is that the knowledge of how the work is done is not written down anywhere and the record of what was done does not survive. MYREX starts from a 3D capture of the machine so it is useful before any data entry has happened.
Does MYREX replace a computerised maintenance management system?
It covers what one of those systems covers — work orders, preventive maintenance scheduling, asset history and records — and adds the thing one does not have: the photos, video and notes that document the work are attached to exact locations on the machine.
Do we need to have our equipment documented first?
No. That is the point of starting from a capture rather than from a database.
How small can we start?
One line. That is the normal starting shape.
See it on your own machine.
Bring a machine you already know is a mess to explain, and we will show you what it looks like inside MYREX.