Work orders raised at the machine, services driven by run hours, parts visible across every site, and capture that survives having no signal.
The category
A CMMS, or computerized maintenance management system, is the software a maintenance team runs on day to day. It holds the work orders, the planned maintenance schedule, the spare parts, and the repair history of every machine. Its job is to answer what needs fixing, who is fixing it, and what happened last time.
That is a narrower question than the one an asset manager asks, and the difference is worth being clear about, because vendors blur it. An EAM system covers what you own across every site, what each machine has cost over its life, and whether compliance can be proved. Most teams start here and move up when several sites, real parts spend and audits arrive at once.
The gap
Nobody can say what maintenance cost last month without rebuilding it by hand.
The planned service was completed, and there is no record that it happened.
Parts get ordered twice because two sites cannot see each other shelves.
The breakdown history of a machine lives in the head of the person who fixed it.
Plenty of operations already run CMMS software and still recognise all four. That is the case this page is about.
Capabilities
Nine areas, grouped around the way a maintenance shift actually runs instead of around a list of modules.
A board that shows what is open, who has it, and what is stuck waiting on a part. Jobs get raised from the machine by the person who found the fault, so the ones that only ever got mentioned on the radio stop disappearing.
Services triggered by run hours, kilometres or cycles read off the machine, so a unit that sat idle for a month does not get serviced for work it never did. Due services are scheduled around the operation rather than dropped on it.
One record per machine covering every job, part and reading, across sites, machine types and fleets of any age. A 1998 reach stacker and a 2025 electric crane fit the same structure without either being forced into a shape that does not suit it.
Stock visible across every store rather than per site, with the same part under one code instead of four. Promising a repair for tomorrow stops depending on somebody walking to the shelf to check.
Jobs closed, hours read, photos taken and parts recorded where the work happened. Held on the device and synced when a connection returns. This is the difference between a maintenance record that is complete and one that is roughly right.
Digital checklists for pre-shift checks and legally required inspections, with corrective actions tracked until they are actually closed. The audit trail builds itself as the work happens.
Readings taken from telematics where they exist and captured by hand where they do not, both feeding the same schedule. Mixed fleets are the normal case, and a service plan that only works on connected units is not a service plan.
Planned against unplanned hours per machine, so the one unit quietly carrying most of the unplanned downtime becomes visible. That is usually the argument for replacing it, and usually the number nobody has.
SAP, Oracle and IBM Maximo stay your main system. Opsima reads what they already hold and writes completed work, consumed parts and readings back into them. Nothing gets ripped out.
The difference
Almost every operation that says its CMMS does not work has the same problem, and it is rarely the software. The jobs get done. The record of them is partial, because recording is a second task that happens somewhere other than where the work did.
A fitter nurses a spreader through a shift and mentions it at handover. A hydraulic leak is found on a walk-around and described out loud. A planned service is completed at the far end of a yard with no reception, and by the time the fitter is back at a desk there are four other things to do. None of that is negligence. It is what happens when the system of record sits somewhere the work does not.
Opsima closes that distance. Jobs are raised and closed at the machine, held on the device when there is no signal, and captured through the channels crews already use. That is why the availability number and what the yard actually sees stop disagreeing, and why a machine with no sensors still ends up with a real history.
In the field
Recorded equipment status changes went from roughly 1,000 a month to roughly 14,000 over the same period. The work was always happening. The record was not. Taavura's Earth Moving Division runs the same layer across quarries and infrastructure sites, after ERP integrations and standard fleet systems had already failed to stick with field crews.
Delivery
Your existing CMMS, SAP or Maximo stays the system of record. Opsima adds capture out where the work happens and reporting that reads across sites, then feeds clean records back in. Nothing gets ripped out, and IT reviews and signs off the rollout in staging before it goes live.
When the reason the records are empty is the software itself, hard to use in a yard and expensive to change, Opsima builds the replacement around your machines and the way your crews work. It runs on your servers or ours. Working software ships in weeks, and you pay once it earns its place.
Goes deeper
The upgrade: lifecycle cost, parts buying and compliance across every site.
Every category Opsima builds, and how a CMMS fits alongside them.
Getting ahead of failures on a schedule that reflects real use.
Fixing on condition, before it breaks, instead of on a calendar.
FAQ
Bring one asset class where the maintenance history has holes in it. We build it on your real data and run it with you. You pay only after it goes live.