One asset list across every site, parts buying that learns from real supplier lead times, lifecycle cost per machine, and inspection records that are ready before anyone asks for them. Built for ports, mining and heavy industry.
The category
EAM software tracks a machine from the day you buy it to the day you retire it, across every site you run. It sits above the day-to-day maintenance work. Past a certain size, the questions stop being about work orders and start being about money and risk.
The line between EAM and a CMMS is worth drawing clearly, because vendors blur it. A CMMS answers what needs fixing and who is fixing it. An EAM answers what you own, what each machine has cost you, when to replace it, and whether you can prove compliance when someone asks. Both sit inside Opsima's wider industrial software range.
The upgrade
You run several sites and nobody can produce one asset list that all of them agree on.
Parts are real money now, and the same part sits in stock under different numbers at different prices.
You decide whether to repair or replace on gut feel, because nobody can pull up what the machine has cost so far.
An audit costs you a week of digging up paperwork that should have been one report.
If two or more of those sound familiar, you have outgrown maintenance software and need asset management. That jump is what this page is about.
Capabilities
Nine areas, grouped around the way a heavy operation actually runs instead of around a list of features.
Lead times based on when suppliers actually deliver, rather than the date printed on the contract. Part numbers cleaned up across sites, so the same bearing stops sitting in stock four times under four codes at four prices. Purchase requests drafted from what you actually use.
Cost history for each machine, not just for a cost centre. Budgets built from what that machine has really cost you so far, and spend totalled up by site, so repair-or-replace stops being an argument and becomes a number.
Digital checklists for pre-shift checks and legally required inspections. Fixes get tracked until they are actually closed. The audit trail builds itself as the work happens, so nobody has to assemble it the week before the audit.
One list across sites, machine types and fleets of every age: STS cranes and straddle carriers on the quay, dozers and haul trucks at the pit, forklifts and reach trucks in the warehouse. A 1998 reach stacker and a 2025 electric crane fit the same structure, and neither has to be squeezed into a shape that does not suit it.
Condition, importance and risk, ranked above the day-to-day work, so your reliability team can argue from evidence. Which machines carry the most risk, which faults keep coming back, and where the next outage is most likely to start.
Availability, breakdown rate, planned maintenance completion and cost per hour, all built from the same records your crews already feed. Maintenance, operations and finance stop bringing three different spreadsheets to the same meeting.
Readings over time from sensors, PLCs and SCADA, stored and searchable right next to the machine record. What makes it different from a normal historian is what else lands there: the events no sensor can see, because somebody called them in over the radio.
Gateways, sensors and telematics all feed the same machine record, instead of a separate dashboard nobody opens. The point of connecting a machine is what ends up in its record.
SAP, Oracle and IBM Maximo stay your main system. Opsima reads what they already hold and writes clean records back into them. Nothing gets ripped out, and IT reviews and signs off the rollout in staging before it goes live.
The difference
Every EAM on the market handles connected machines well. Sensors report, the system stores, the dashboard draws the chart. The problem is everything else, and in heavy industry everything else is most of the fleet.
A crane spreader gets nursed through a shift and the operator mentions it on the radio. A hydraulic leak is caught during a walk-around and described in a message. A reach stacker is taken out of service for two hours and the reason gets explained out loud at handover. None of those machines sent a signal. All three events matter, and none reach the record.
Opsima picks up those events from the channels your crews already use and writes them to the machine record. 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
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. Maintenance, operations, IT and engineering all read one picture, and nobody had to change how they report.
Delivery
Your SAP, Oracle or Maximo stays your main system. Opsima adds a working layer around it and 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 old platform is the thing holding you back, hard to change and expensive to touch, 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
Fixing on condition, before it breaks, instead of on a calendar.
Work orders, planned maintenance and repair history, day to day.
Live status across mixed fleets, sites and shifts.
SAP, Maximo, Navis, telematics and the rest of your systems.
FAQ
Bring one asset class where the numbers never quite match what the yard sees. We build it on your real data and run it with you. You pay only after it goes live.