
Heavy Equipment Maintenance Software for the Ghanaian Workshop
Parts are ordered after the damage is done.
Without strict maintenance records, your workshop runs on reaction, not intelligence. Darikoda connects the defect reported in the field to the work order in the bay, the approval that releases it, the parts it waits on and the maintenance history of the machine underneath all of it.
At a glance
Heavy equipment maintenance software connects the defect reported on site to the work order in the workshop, the work order to the approval and the purchase order behind it, and all of it to the maintenance history of the asset. Darikoda holds that as one thread for mining, construction, plant hire and civils fleets in Ghana, so the health of a machine is a record rather than a recollection. Captured at source.
Representative product workflow · Illustrative data
See how the operating record captures this workflow
Approvals
2 decisions taken offline, will replay on sync
Work order WO-3140
Requested by Operator A. Asset: Excavator 08 (EX-08).
Auto-approved, last 7 days
Order SO-1188
USD 780.00, 2d ago
The definition
What is heavy equipment maintenance software?
Heavy equipment maintenance software manages the work that keeps mixed plant running. Not a service book for a car fleet and not an asset register for office equipment. An excavator that works a hard face for eleven hours and one that idles on standby wear at completely different rates, and the software has to know the difference.
For a heavy fleet, maintenance management spans a wider set of work than the phrase suggests:
- Defect reporting from the field.
- Inspections, scheduled and ad hoc.
- Preventive maintenance against actual use.
- Corrective repairs after a fault.
- Service scheduling across the fleet.
- Engine-hour intervals rather than calendar dates alone.
- Work orders and what they authorise.
- Parts, their status and where they are allocated.
- Workshop status, bay by bay.
- Repair approvals and who they sit with.
- Technician and workshop activity.
- Maintenance history at asset level.
- Return-to-service checks.
- Maintenance cost against the machine that incurred it.
The operational challenge starts before the machine reaches the workshop. A defect noticed at seven in the morning at a remote work front, mentioned to a supervisor at noon and relayed to the workshop that evening arrives stripped of everything that would have made the diagnosis quick. What the machine was doing, who was on it, what it sounded like, whether it had done it before.
That is the gap Darikoda is built to close. It is heavy equipment maintenance software for heavy fleet operators in Ghana, and it sits inside the wider operational intelligence record rather than beside it, because the machine in the bay this week is the one being costed, fuelled and utilised the rest of the month.
The problem
A workshop running on reaction
Without records, the workshop is always one step behind the damage.
Defects are reported verbally, then forgotten.
The workshop orders parts on guesswork.
Cloud-only workshop tools built for continuous office connectivity stall when remote site signal drops.
Maintenance cost eats the project margin, and nobody can prove why.

The defect on site and the repair in the bay are one thread.
When the field record is strong, the workshop diagnoses right the first time and the machine is back sooner.
The distinction
Maintenance software versus operational intelligence
A maintenance system is built around the machine's repair history. An operating record is built around everything happening to the machine, of which repair is one part. The difference is not what either can record. It is how much of the machine's life stays connected to it.
| What is held | Traditional maintenance and CMMS focus | Darikoda operational intelligence |
|---|---|---|
| Defect reporting | Handled well once the defect reaches the system, which is usually when it reaches the workshop. | Captured in the field at the moment it is noticed, with the machine, the operator and the conditions attached. |
| Work orders | Core strength. Raising, assigning and closing work orders is what these systems are for. | Held as one stage of a longer thread that starts at the field defect and ends at return to service. |
| Preventive maintenance | Scheduled reliably, most often against calendar intervals or hours entered manually. | Planned against operating hours captured from the field, alongside the manufacturer's requirements rather than instead of them. |
| Corrective maintenance | Managed thoroughly from the point the fault is logged. | Managed from the point the fault is observed, which is usually hours or days earlier. |
| Engine-hour servicing | Supported, where the hours are supplied accurately and on time. | Supported from hours already being recorded for utilisation and costing, so the maintenance clock and the commercial clock are the same clock. |
| Parts | Tracked in detail, often with stock and reorder handling. | Tracked against the machine, the fault and the availability loss the wait is causing. |
| Approval workflow | Configurable and often thorough inside the maintenance function. | Visible to operations and finance as well as the workshop, because the people waiting on the machine are rarely the people approving the repair. |
| Workshop history | Comprehensive. This is the system of record for what the workshop did. | The same history, read next to what the machine was doing when it broke and what it did after it came back. |
| Operator context | Usually outside the maintenance record. | Attributed to the defect and the damage, so a recurring fault can be read against how the machine is being run. |
| Utilisation and downtime | Downtime is recorded as time in the workshop. | Downtime is recorded as time out of service, including the approval and parts legs that happen outside the bay, and read against utilisation. |
| Fuel context | Generally a separate system. | On the same asset record, so a consumption pattern can point at a mechanical problem before the failure does. |
| Commercial evidence | Strong for maintenance cost and warranty positions. | Strong for those and for the disputes that are not about maintenance, where the maintenance record happens to be the proof. |
None of the above says a maintenance system cannot do a given thing. Most of them can, and a good CMMS does the workshop job better than a general tool ever will. The distinction is architectural. A maintenance system is a maintenance-centric record. Darikoda is an operational record that keeps the field event and the workshop event connected. The full comparison against ERPs, trackers and spreadsheets is on how Darikoda compares.
Corrective maintenance
From field defect to repair
The defect on site and the repair in the bay are one thread. The earlier the field event is captured, the more the workshop has to work with when it comes to diagnose the problem, and the less of the repair is guesswork paid for in parts.
- 01
Defect observed
Someone notices something wrong. This is the richest moment in the whole sequence and the one most often lost.
- 02
Defect captured
It is recorded where it happened, offline if there is no signal, rather than carried in someone's head to the end of the shift.
- 03
Equipment identified
The defect is tied to the asset by ID, so it joins that machine's history rather than a general list of complaints.
- 04
Operator and site context recorded
Who was on it, where it was, what it was doing and how many hours it had run. This is what the workshop cannot reconstruct later.
- 05
Verification
The responsible person confirms the report, which stops a disputed defect turning into two competing accounts of the same machine.
- 06
Diagnosis
The workshop determines what is actually wrong, working from a field record rather than from a two-word message.
- 07
Repair requirement
What the machine needs is set out against the fault, including the parts and the labour it will take.
- 08
Approval
The repair or the spend is authorised where authorisation is required, and the waiting is recorded rather than only the decision.
- 09
Parts
Parts are ordered, tracked and allocated to the machine and the fault they belong to, not to a general store movement.
- 010
Workshop repair
The work happens, with the technician activity and the parts consumed held against the asset.
- 011
Testing
The machine is checked to confirm it does what it should before anyone commits it to a work front.
- 012
Return to service
The asset is confirmed available again, which closes the maintenance event and the availability loss at the same time.
What management sees
The health of every machine
- Time from defect report to repair start
- Repair duration once work begins
- Mean time to repair (MTTR)
- Maintenance spend per asset
- Parts spend, and parts allocated to specific machines
- Recurring failures by asset and component
- Planned against unplanned maintenance
- Services running overdue against actual hours
- Downtime attributable to maintenance
- Approval times for high-cost interventions
- Time lost waiting on parts
- Return-to-service time
- Historical maintenance spend per asset

Maintenance spend you can finally explain.
Parts, approvals and repair times tied to the asset, so cost-per-machine stops being a guess.
By industry
Where the workshop gap actually costs

Mining
Excavators, haul trucks, loaders and the production equipment everything queues behind, serviced on engine hours rather than calendar dates. Remote workshop coordination and long parts legs are the constraint here, and on contractor sites the maintenance record is also the accountability record. Views for mining contractors and full mine operators.

Construction
Excavators, graders, rollers, loaders and mobile plant moving between work fronts, where a repair delay is a programme delay behind it. Capturing the defect at the front rather than at the end of the shift is what shortens the diagnosis. Read the main contractor view.

Plant Hire
Asset availability is the product. Maintenance history, repair attribution and off-hire periods decide whether a customer commitment can be met and whether a damage charge holds when the hirer disputes it. Read the hire firm view.

Civils
Graders, rollers and excavators spread down a chainage, often a long way from the workshop that has to fix them. One machine out of service stalls a work front that the following trades are queued behind. Read the road contractor view.
By role
Who uses heavy equipment maintenance software
The same maintenance record answers a different question at each desk, which is the practical argument for it being one record.
- Workshop Manager
Which repairs are waiting, why, and when do they go back out?
The bay-level view. What is in, what it is waiting on, which jobs are held by an approval rather than by the work, and what is realistically going back to the field this week.
- Maintenance Manager
Are we ahead of the fleet or behind it?
Services due against actual hours, what is running overdue, which assets keep coming back with the same fault, and where planned work is losing ground to unplanned work.
- Operations Manager
Which maintenance events are affecting production?
Not the workshop's internal queue, but which machines are out, how long they will be out, and what that does to the work already committed.
- Fleet Manager
Which assets are repeatedly unavailable?
Availability and repair frequency read together across the fleet, so the machines that keep failing are visible as a pattern rather than as a run of separate incidents.
- Site Manager
Was the fault I reported actually picked up?
The status of a defect reported from the field, so a report made on Tuesday is traceable rather than absorbed into a message thread.
- Project Manager
Is a machine going to hold up the programme?
Expected return to service against the work front that needs the asset, early enough to reallocate rather than to explain.
- Finance and Commercial
Which maintenance costs attach to which assets and approvals?
Spend held against the machine that incurred it and the approval that released it, so maintenance cost is auditable rather than a monthly total nobody can decompose.
- General Manager
Is this machine still worth keeping?
Cost to keep running against what the asset earns, with repair frequency and availability alongside it. The repair-versus-replace question, answered from record rather than instinct.
What changes
What better maintenance control changes
Maintenance software does not repair machines. What it changes is how quickly the right information reaches the person who can act, and what the business can see afterwards.
- Faster repair decisions, because the diagnosis starts from a field record rather than from a two-word message.
- Better maintenance planning, against actual operating hours instead of calendar dates.
- Clearer parts requirements, identified against the fault rather than ordered on guesswork.
- Stronger equipment availability, because the non-workshop legs of a repair stop being invisible.
- Less administrative reconstruction at month-end.
- Better maintenance cost visibility, attached to the asset and the approval behind it.
- Stronger asset history, held in one place across the life of the machine.
- Better repair accountability, held to the part of the delay each function actually controls.
- Fewer repeated surprises, because a recurring failure surfaces as a pattern.
- Better fleet planning, including the repair-versus-replace decisions that get deferred for lack of evidence.
What any of that is worth depends on fleet size, the condition of the equipment, how mature your maintenance function already is, parts availability in your supply chain, the operating environment and how far the implementation goes. We do not publish a maintenance saving percentage, because the honest answer is that your number comes out of your own record. The Operational Audit is where we find it.
Why Ghana
The Ghanaian context
In Ghana, the distance between a remote site and the central workshop creates an information gap, and the gap is where maintenance money goes. Mining sites sit hours from the yard. Construction projects are dispersed across a region while the workshop stays central. Parts take time to source from Tema, and if the diagnosis is wrong because the field record was weak, that sourcing time gets spent twice while the machine stands. Defects travel by WhatsApp, workshop records are often kept by hand, and connectivity at the point the defect is noticed is rarely something anyone can rely on. Not every workshop here runs that way and we are not going to pretend otherwise, but the pattern is common enough to be the default rather than the exception. That is why the capture has to survive the conditions. A defect saves on the device and syncs when signal returns, so it is recorded at the work front at the moment it is noticed rather than remembered at the end of a shift. Darikoda bridges the site-to-workshop gap with structured, indisputable evidence.
See what this means for your operation.
A free 30-minute audit. Your priorities, a one-page leakage map and three practical next steps.
Explore the detail
Open the topic you need for your operation.
Engine hours are the maintenance clock, not the calendar
Preventive maintenance
Calendar intervals are easy to administer and a poor fit for heavy equipment. In an illustrative comparison, a machine serviced every three months might run four hundred hours in one quarter and eleven hundred in the next. One of those services arrives early against wear, while the other arrives late after heavy duty, and a calendar schedule alone cannot tell the difference until a component fails.
Useful maintenance planning reads the machine rather than the month. The factors that actually move a service requirement:
- Engine hours, as the primary clock for most heavy plant.
- Operating intensity, because eleven hours on a hard face is not eleven hours on standby.
- Duty cycle, and how much of it is under load.
- Site conditions, including dust, water, gradient and haul-road surface.
- Workload across the period rather than an average across the fleet.
- Equipment class, because a grader and a haul truck do not age the same way.
- The manufacturer's requirements, which set the floor.
Darikoda does not replace the manufacturer's schedule and we are not going to claim it does. What it provides is a reliable operating-hour record captured in the field, so the schedule is applied against what the machine actually did rather than against an hour meter someone copied down last time they remembered. The sequence runs from machine activity to operating hours, to a service threshold, to a maintenance requirement, to workshop action, to approval where it is required, to completion and return to service.
Those same hours are already being captured for utilisation and costing in fleet management software, which is the practical reason the maintenance clock and the commercial clock should not be two different numbers kept in two different places.
Repairs can be diagnosed long before they can be started
The workshop
A machine can stand out of service for days after the workshop knows exactly what is wrong with it. The fault is diagnosed, the repair is specified, and the asset waits because the repair approval is pending, the purchase approval is pending, the parts have not been ordered, budget authority is unclear or procurement is moving slowly. The sequence is fault, diagnosis, repair required, approval, parts, repair, testing, return to service. Two of those eight are workshop work. The rest is coordination.
Workshop management is not really about closing work orders. It is about knowing where each machine sits in that sequence, and making that legible to people who are not standing in the bay:
- The machine, by asset ID.
- The defect, as reported from the field and as diagnosed in the bay.
- The time it was reported and the time it was received.
- The operator who reported it and the project or site it came from.
- The diagnosis and the work it calls for.
- The work order and what it authorises.
- The parts status, including what is ordered and what is holding.
- The approval status, and the authorised reviewer it is sitting with.
- The repair status and the technician activity against it.
- The expected completion, and then the actual completion.
- The return-to-service confirmation.
Read that way, a machine down for eleven days stops being a workshop failure by default. If two of those days were diagnosis, six were an approval nobody chased and three were the repair, the workshop is not the constraint and pressure applied there will not move the number.
The availability side of the same problem, and what it costs in deployable capacity, is covered on downtime tracking software. This page is the workshop side of it.
Parts are part of equipment availability
Parts
A part that has not arrived is not a procurement footnote. It is a machine standing still, and on a Ghanaian operation it is frequently the longest single leg of the whole maintenance event. Sourcing from Tema takes what it takes, and a wrong diagnosis means that time gets spent twice.
A parts delay does not stay in the workshop. It runs straight through the business:
- The repair cannot start, no matter how free the bay is.
- Machine availability falls for every day the part is outstanding.
- Downtime accumulates against a cause that is not mechanical.
- Project delivery slips where that machine was on the critical path.
- Rental revenue is lost where the asset was committed to a customer.
- Workshop backlog builds behind a bay occupied by a machine that cannot be worked on.
This is not a procurement system and it is not trying to become one. What it does is keep the part connected to the things that give it meaning: the machine it is for, the fault it answers, the work order it belongs to, the approval that released it, the purchase behind it, the repair it enables and the return to service it unblocks.
Held that way, a repeated parts delay stops being a series of individual frustrations and becomes a pattern management can plan against.
Every machine should have a maintenance history
History
Most heavy fleets can tell you what a machine cost to buy and roughly what it costs to run. Far fewer can produce the life of the asset in one place. An asset-level maintenance history holds:
- Inspections and what they found.
- Defects as reported from the field.
- Repairs and what they involved.
- Parts consumed and parts waited on.
- Service events against the hours that triggered them.
- Downtime, including the non-mechanical legs.
- Approvals and how long they took.
- Maintenance cost, against the asset that incurred it.
- Operating hours across the whole of it.
The record does not make decisions. Management does. What the record does is make the pattern visible early enough for the decision to be a choice rather than a reaction: a component failing repeatedly across a class of machines, a service that keeps running overdue against actual hours, repair frequency climbing on an asset approaching the end of its economic life, a repair-versus-replace question that has quietly already answered itself.
That is also what turns a fleet renewal conversation from an argument about opinions into a review of what each machine actually cost to keep on the ground.
Maintenance is one line in the operating record
The wider record
Maintenance is a cause of unavailability. It is not the only one, and treating it as though it were is how workshops end up carrying a number they do not control. A machine can be unavailable through maintenance, but equally through parts, approvals, inspection, transport, a missing operator, an administrative hold or a damage investigation. The chain runs from maintenance event to downtime, to reduced availability, to reduced usable fleet capacity, and only the first link belongs to the workshop.
Three relationships are worth reading deliberately:
- Availability. How long recovery takes decides how much capacity the business can actually deploy. The Operating Note on machine availability sets out why a single fleet percentage hides the constraint it is meant to expose, and downtime tracking carries the event side.
- Damage. Damage becomes far more useful once it becomes maintenance evidence, running from the damage event through attribution, inspection, repair requirement, approval, parts and repair to return to service. The Operating Note on equipment damage records covers how attribution holds up when the cause is disputed.
- Utilisation. A machine with poor utilisation might have low demand, recurring downtime, a maintenance problem or an allocation problem, and maintenance history alone will not tell you which. Read together they will. The Operating Note on daily plant utilisation goes further into the separation.
One distinction is worth holding on to through all of that. A machine held in the workshop is unavailable. A machine sitting at a work front in perfect order, waiting on drawings or materials, is idle rather than under maintenance, and no amount of workshop improvement will recover that hour. Keeping the two apart is what stops the workshop being handed a number it never controlled.
This is why maintenance sits inside the operating record rather than in its own system. Fuel, hours, downtime and maintenance describe the same asset, and the questions worth asking cut across all four.
Frequently asked questions
The questions operators ask first
What is heavy equipment maintenance software?Read the answerClose answer
It manages the work that keeps mixed heavy plant running: defect reporting from the field, inspections, preventive and corrective maintenance, service scheduling on engine hours, work orders, parts, approvals, workshop status, maintenance history and return-to-service checks. It is not a service book for a car fleet, because an excavator on a hard face and the same model on standby wear at completely different rates.
What does maintenance software do for mining equipment?Read the answerClose answer
Excavators, haul trucks and loaders are serviced on engine hours rather than calendar dates, and on remote sites the parts leg and the approval leg are usually longer than the repair. The record connects the field defect to the workshop action and keeps the maintenance history against the asset, which on contractor sites is also the accountability record.
Mining operations in GhanaWhat is preventive maintenance?Read the answerClose answer
Work carried out to stop a failure happening, scheduled against use rather than in response to a fault. For heavy equipment the trigger should be engine hours, operating intensity, duty cycle and site conditions alongside the manufacturer's requirements, because a machine that ran eleven hundred hours in a quarter and one that ran four hundred do not need the same service on the same date.
What is corrective maintenance?Read the answerClose answer
Work carried out after something has gone wrong, running from the defect being observed through capture, verification, diagnosis, repair requirement, approval, parts, repair, testing and return to service. Only two of those stages happen with a spanner in hand, which is why corrective maintenance is mostly a coordination problem.
Can maintenance be scheduled from engine hours?Read the answerClose answer
Yes, and for heavy equipment it usually should be. Hours captured from the field give a service threshold that reflects what the machine actually did. Darikoda does not replace the manufacturer's schedule. It makes the hours reliable enough that the schedule can be applied properly instead of against a meter reading somebody copied down last time they remembered.
How does equipment maintenance software manage work orders?Read the answerClose answer
The work order sits in the middle of a longer thread rather than at the start of one. It carries the diagnosis, what the repair calls for, the technician activity against it, the parts allocated and the approval that released it, and it stays connected to the field defect that triggered it and the return to service that closes it.
How does it handle parts?Read the answerClose answer
Parts are held against the machine, the fault, the work order and the approval, along with what is on order and what is holding. This is not a procurement system. The point is that a part outstanding is a machine standing still, so the parts status has to be visible to the people waiting on the asset and not only to the store.
How do repair approvals affect equipment availability?Read the answerClose answer
A machine can be fully diagnosed and still stand out of service because the repair approval, the purchase approval or the budget authority is pending. That time is an availability loss with no mechanical cause. Recording the approval status and the authorised reviewer it sits with is what makes it visible instead of quietly absorbed into a workshop delay.
Can it keep maintenance history per machine?Read the answerClose answer
Yes, at asset level. Inspections, defects, repairs, parts, service events, downtime, approvals, maintenance cost and operating hours in one place across the life of the machine. That history is what supports recurring failure identification, replacement decisions and the repair-versus-replace question. The record supports the decision. It does not make it.
Can construction companies use it?Read the answerClose answer
Yes. Excavators, graders, rollers, loaders and mobile plant move between work fronts, and a repair delay becomes a programme delay behind it. Capturing the defect at the front rather than at the end of the shift is what shortens the diagnosis and stops the workshop working from a two-word message.
Construction operations in GhanaCan plant hire businesses use it?Read the answerClose answer
Yes, and for a hire business asset availability is the product. Maintenance history, repair attribution and off-hire periods decide whether a customer commitment can be met, and the repair record is what holds a damage charge up when the hirer disputes it.
Plant and equipment hire in GhanaCan mining contractors use it?Read the answerClose answer
Yes. On a contractor fleet the maintenance record does double duty. It runs the workshop, and it evidences machine condition and availability against a client who is measuring both. Remote workshop coordination and long parts legs make the non-mechanical stages of a repair the ones worth recording most carefully.
What is the difference between CMMS and operational intelligence?Read the answerClose answer
It is architectural rather than a question of features. A CMMS is a maintenance-centric record and a good one does the workshop job better than a general tool will. Operational intelligence keeps the field event and the workshop event connected, so the defect, the operator, the hours, the downtime, the fuel and the repair describe one asset instead of sitting in separate systems.
Full comparison: Darikoda vs ERP, trackers and spreadsheetsHow does maintenance connect to downtime?Read the answerClose answer
Maintenance is one cause of unavailability, not the only one. A machine can be unavailable through maintenance, parts, approvals, inspection, transport, a missing operator, an administrative hold or a damage investigation. The chain runs from the maintenance event to downtime, to reduced availability, to reduced usable capacity, and only the first link belongs to the workshop.
Downtime tracking softwareIs this a full ERP?Read the answerClose answer
No. It is an operational intelligence layer. It tracks the real-world workflow and evidence that standard ERPs cannot see, and it is designed to sit alongside the finance system rather than replace it.
How does an Operational Audit identify maintenance leakage?Read the answerClose answer
The free 30-minute Operational Audit maps where your maintenance evidence breaks. It names the defect capture gaps, the approval bottlenecks, the parts delays and the assets whose repair history should already have prompted a decision, specific to your fleet. You keep the one-page map regardless of next steps.
Book an Operational AuditSee where your operation leaks.
The Operational Audit takes 30 minutes. You get a one-page leakage report you keep regardless of next steps.
Patterns described here are drawn from extensive field audits and industry research across Ghana's mining, construction, roadworks, and quarry sectors. No specific operator is named or identifiable.