
Downtime Tracking Software for Ghanaian Operations
A parked machine is bleeding cedis.
When a machine stops, it is not always broken. Downtime tracking software records why it stopped, how long it stayed out of service, what is blocking recovery and who owns clearing it. For mining, construction, plant hire and civils operators, that is the difference between an idle day you can act on and one that only shows up when the billing comes up short.
At a glance
Downtime tracking identifies why equipment is not working, how long it remains unavailable and what is blocking recovery. It records the event with its cause, its owner and its recovery status, so a vague breakdown line becomes something management can act on. Downtime is not the same as idle time, availability or utilisation, and Darikoda holds all four against the same asset. Captured at source.
Representative product workflow · Illustrative data
See how the operating record captures this workflow
Fleet Readiness
Locations
5
No loader
1
Addressable idle
19%
Deliberate idle
8%
Resource balance
Pit A
Under-loadedLoaders
1
Haulers
5
Per loader
5.0
Dump B
No loaderLoaders
0
Haulers
3
Per loader
n/a
Idle classification
EX-12
38% idleThe definition
What is downtime tracking software?
Downtime tracking software is the structured recording of the periods when equipment is not performing the work it was put on site to do. Not a total at the end of the month, but the event itself, captured while the machine is still standing there.
For heavy equipment that means a record with enough on it to be acted on. A useful downtime event carries:
- The time it started.
- The time it ended.
- The reason the machine stopped.
- The asset it applies to.
- The operator on it when it stopped.
- The site or work area it happened in.
- The function responsible for clearing it.
- The action required next.
- The recovery status, up to return to service.
The value is not in measuring hours lost. Any spreadsheet can total hours. The value is in knowing why the time was lost and what has to change so it is not lost the same way next month. An hour attributed to a parts delay and an hour attributed to a missing operator are the same hour on a report and two completely different management problems.
Darikoda is downtime tracking software for heavy fleet operations in Ghana, and it sits inside the wider operational intelligence record rather than beside it, because the same asset that is down today is the one being costed, fuelled and utilised the rest of the month.
The distinction
Downtime, idle time and availability are not the same thing
These five terms get used interchangeably in fleet reporting. They are not interchangeable, and mixing them sends the problem to the wrong department. That is how a scheduling failure ends up on the workshop's report card.
| Concept | What it means | The management question | Example |
|---|---|---|---|
| Idle time | The machine is available and ready, but it is not doing productive work. | Why is a machine that could be working not working? | An excavator standing at the work front waiting on drawings, materials or fuel. |
| Downtime | The machine is not working because a specific operational constraint is preventing use. | What is stopping this machine, and who owns clearing it? | A dozer held in the workshop waiting on a hydraulic part. |
| Unavailability | The state a machine is in while it cannot be put to productive work when the operation needs it. | How much of the fleet can I actually deploy this week? | A grader out of service pending an inspection and a repair approval. |
| Availability | The measure of how much of the fleet was ready and usable at the point it was needed. | Is the fleet I own the fleet I can use? | Eighteen of twenty machines deployable, with a recorded reason and owner against the other two. |
| Utilisation | How much of the available capacity was actually used, and how productively it was used. | Did the machines that were available earn their keep? | A loader available all week, running six hours a day, productive for four of them. |
Unavailability is the state. Availability is the measure management reads. The deeper treatment of each sits in the Operating Notes on equipment idle time, daily plant utilisation and machine availability. This page is the software that records the events underneath them.
The problem
Idle time nobody can explain
Downtime is the cost that hides until the billing comes up short.
Equipment downtime gets lumped into one vague breakdown category.
The workshop blames the site. The site blames the workshop.
Fleet downtime only surfaces at month-end, when the billing comes up short.
Approvals for repairs sit unread in a WhatsApp thread.

A stopped machine is a question, not a verdict.
Waiting for a part, an operator, or an approval. Darikoda records which, so the right person can clear it.
The distinction
Tracking where a machine stops is not the same as knowing why
A tracker answers the first question well. It was built to. The problem is that the first question is the cheap one, and every question after it is where the cost actually sits.
| What is held | GPS and telematics | Darikoda downtime record |
|---|---|---|
| That it stopped | Recorded reliably. Position and movement are exactly what a tracker is built to deliver. | Recorded too, as the start of an event rather than as the whole of it. |
| Why it stopped | Inferred from the pattern, because a reason is not something a signal can see. | Captured as a categorised reason at the event, by the person who was standing next to the machine. |
| How long it was down | Measurable as elapsed stationary time. | Measured as time out of service, which is not the same as time not moving. A machine can be stationary and working, or moving and unproductive. |
| Who owns the bottleneck | Outside what the signal carries. | Attributed to a responsible function, so the event has somewhere to go instead of sitting between departments. |
| What action is pending | Outside what the signal carries. | Held as the current status: diagnosis, approval, parts, repair or testing. |
| When recovery is expected | Not something a position feed can answer. | Recorded as an expected completion against the open event, so planning has something to work from. |
| Whether it happened before | Visible as a repeated stop in the same place. | Visible as a repeated cause on the same asset or component, which is the version that changes a decision. |
None of this makes GPS useless. Position and movement are real signals and most operations should have them. The point is that they describe the machine, and downtime is a question about the operation around the machine. Darikoda is the layer that captures that context, alongside fleet management software and the rest of the operating record.
The lifecycle
From breakdown to back in service
Downtime is an event with a life, not a number at month-end. Each stage below is a place time gets lost, and each one is a place the record either holds or breaks.
- 01
Event occurs
The machine stops or becomes unavailable. This is the only moment when everyone involved knows exactly what happened.
- 02
Capture
The operator or supervisor records the event where it happened, offline if there is no signal, rather than reporting it up a chain later.
- 03
Categorise
A reason is assigned from a defined set, so downtime can be read by cause instead of arriving as one undifferentiated total.
- 04
Verify
The responsible person confirms the status of the machine, which stops a disputed event becoming two competing accounts.
- 05
Diagnose
Where a fault is involved, the workshop or operations determines what the machine actually needs. Diagnosis time is downtime and is recorded as such.
- 06
Approve
The repair, the parts or the operational intervention is authorised where authorisation is required. The waiting is recorded, not just the decision.
- 07
Resolve
The repair or the operational fix takes place, with the parts and the work held against the asset rather than in a separate book.
- 08
Return to service
The machine is confirmed ready and available again, which is the event that closes the clock rather than the moment the spanner goes down.
- 09
Report
Management sees the duration, the cause, where the time went inside it, and what it cost the operation in available capacity.
What management sees
Downtime, by cause
- Total downtime across the fleet
- Downtime per asset
- Downtime by cause category
- Downtime by site
- Downtime by project
- Downtime by shift
- Mean time to repair (MTTR)
- The longest single downtime events
- Repeated downtime causes
- Time lost to approval delays
- Time lost to parts delays
- Time lost to delayed certs
- The availability impact of the above

Every idle day is billable work that did not happen.
Categorised, timestamped and attributed, so idle time stops being a mystery at month-end.
By industry
Where the downtime actually costs

Mining
Haul trucks, excavators, loaders and the production equipment everything else queues behind. On remote sites the parts leg is long and the approval leg is longer, so a crusher down for a day is rarely down for mechanical reasons alone. Views for mining contractors and full mine operators.

Construction
Excavators, graders, compactors and loaders, where a machine out of service is a work front that stalls and a programme that slips. The approval that takes six days is a six-day availability loss with no mechanical cause behind it. Read the main contractor view.

Plant Hire
Unavailable rental equipment is lost rental days and a customer commitment you cannot meet. Repair turnaround is the commercial number here, and the recovery record is what defends the position when the hire is disputed. Read the hire firm view.

Civils
Road formation equipment, graders, rollers and excavators spread down a chainage, where one machine out of service stalls a work front that the following trades are already queued behind. Read the road contractor view.
What changes
What better downtime control changes
Downtime tracking does not repair anything. What it changes is how fast the right person finds out, and what management can see when they do.
- Faster recovery, because the event reaches the person who can clear it while it is still open.
- Better equipment availability, because the non-mechanical legs of a downtime event stop being invisible.
- Fewer unexplained idle days, because the reason is captured at the event rather than reconstructed.
- Clearer workshop accountability, held to the part of the delay the workshop actually controls.
- Better parts planning, because repeated parts delays surface as a pattern instead of a series of surprises.
- Stronger utilisation, because available capacity is visible against the work it was given.
- Less administrative reconstruction at month-end, and the hours that went into it back.
- Better project planning, because deployable capacity is a record rather than an estimate.
- Stronger commercial evidence when a client disputes a timeline or a deduction.
What any of that is worth depends on fleet size, the mix of causes you are actually carrying, how your approvals and procurement are structured and how far the implementation goes. We do not publish a downtime reduction percentage, because the honest answer is that your number comes out of your own record. The Operational Audit is where we find it, and it names the recurring downtime, the weak event capture, the approval bottlenecks, the workshop delays, the missing maintenance records and the unexplained idle periods specific to your operation.
Why Ghana
The Ghanaian context
On Ghanaian construction and mining sites, a machine can sit idle because the paperwork for a replacement part is stuck in a WhatsApp thread. That is not a joke about messaging apps. It is what happens when remote mining sites and dispersed construction projects are hours apart from the office, connectivity is unreliable at the point the event occurs, and the reporting line between the site and the office runs through whoever happens to be reachable. Parts procurement adds a leg that operations in denser markets do not carry, and approvals stretch across people who are rarely in the same place. Add multiple contractors and shared equipment on one site and the question of whose machine stopped, and whose decision unblocks it, gets genuinely hard to answer after the fact. We are not going to quote you a national downtime figure, because credible ones do not exist and your operation is not an average. What we will say is that the capture has to survive the conditions. Every event saves on the device and syncs when signal returns, so a supervisor at a remote work front records the machine going down at the moment it goes down rather than remembering it that evening. Darikoda surfaces those specific administrative bottlenecks so management can unblock the flow of work.
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.
What causes equipment downtime?
The causes
Downtime is not one thing and it does not belong to one department. Treating it as a workshop problem is the single most common reporting mistake in heavy fleet operations, because it puts the whole number in front of the one function that only controls part of it. Categorised properly, the causes fall into six groups:
- Mechanical. Engine faults, hydraulic failures, electrical faults, tyre failures and component failures. The category everyone assumes is the whole picture.
- Maintenance. Scheduled servicing, inspections, preventive maintenance and work that is overdue. Planned time out of service is still time out of service, and it should be visible as such rather than hidden.
- Parts and supply. Unavailable parts, delayed procurement, transport delays and supplier delays. On a Ghanaian operation this is often the longest single leg of a downtime event and the one least visible in the workshop report.
- Operational. No operator, poor scheduling, a work front that is not ready, supporting equipment unavailable, or a fuel issue. None of these are mechanical, and all of them stop the machine.
- Administrative. Repair approval, purchase approval, client instruction, certification delay or a project hold. The machine is fixable and the fix is waiting on a decision.
- External.Weather, road conditions, site access, a safety hold and other constraints outside the operation's control. Recording these matters precisely because they are not anybody's fault and should not be argued about.
The categories exist so management can find the actual bottleneck rather than the convenient one. A fleet reporting heavy downtime with most of it sitting in parts and administrative categories does not have a workshop problem. It has a procurement and approvals problem, and no amount of pressure on the workshop will move the number.
The Operating Note on machine availability makes the same argument from the capacity side, which is why availability cannot be managed inside the maintenance department alone.
MTTR tells you how long the machine stayed down. The reason tells you why.
MTTR
Mean time to repair is a useful number and this page is not arguing against it. The limit is that an average collapses a sequence into a single figure, and the sequence is where the recoverable time lives. A downtime event is not one block of repair. It runs:
- Downtime starts, at the moment the machine comes out of service.
- Diagnosis, working out what is actually wrong.
- Approval, waiting on authorisation for the repair or the spend.
- Parts, waiting on availability, procurement or transport.
- Repair, the work itself.
- Testing, confirming the machine does what it should.
- Return to service, the machine available again.
An MTTR of eleven days can be a workshop that is slow, or a workshop that fixed the machine in a day and waited ten for a part and a signature. Those are opposite problems with the same average. Parts delays, approval delays, workshop backlog, diagnosis time, transport, operator availability and external constraints all hide inside the same figure.
A timestamped operational record does not improve MTTR by itself. What it does is let management see which leg of the sequence the time actually disappeared into, which is the only basis on which the number can be improved deliberately rather than hopefully.
Repairs can be ready before the machine is
The bottleneck
A machine can stay out of service long after the technical problem is understood. The fault is diagnosed, the workshop knows what it needs, and the asset still stands there because the repair approval is waiting, the parts purchase has not been raised, the work order is pending, or nobody is clear whose decision it is. The sequence looks like this: fault identified, repair required, approval pending, parts pending, repair, return to service. Only one of those six is mechanical.
This page already said approvals sit unread in WhatsApp threads, because that is the specific shape the problem takes here. Closing it means the workshop record has to be readable by the people who are not in the workshop:
- The machine, by asset ID.
- The fault, as reported and as diagnosed.
- The date and time it was received.
- The diagnosis and what it calls for.
- The repair status.
- The parts status, including what is on order and what is waiting.
- The approval status, and who it is sitting with.
- The expected completion.
- The actual completion.
- The return-to-service confirmation.
That is not a maintenance management system and this page is not trying to become one. It is the visibility layer between the workshop and the field, so operations can see what is blocking a machine without walking into the bay to ask, and so an approval that has been pending six days surfaces as a six-day availability loss rather than as a mechanical failure.
The deeper workshop thread, from defect to work order to parts to spend, sits on heavy equipment maintenance software.
Downtime, availability and utilisation are one chain
The chain
These three get reported separately and they are the same story told at three distances. Downtime is the event. Availability is what the events do to the capacity you can deploy. Utilisation is what you managed to do with the capacity that was left. The chain runs one way: downtime reduces availability, and reduced availability reduces the usable capacity the business actually sells.
- A machine with heavy downtime has less available capacity, no matter how well it performs when it runs.
- A machine with almost no downtime can still be badly utilised, sitting available and unused because the work front was not ready.
- Availability falls further the longer recovery takes, which makes recovery speed a commercial number and not just a workshop one.
- A machine can be unavailable through breakdown, parts, repair, approvals, inspection, damage or an administrative hold, and only some of those are mechanical.
- So downtime does not equal utilisation, and neither one on its own tells management whether the fleet is earning.
That is why downtime tracking is not a standalone tool. Fleet management software tells management how the assets are being used. Downtime tracking explains where the capacity went. Read one without the other and you get a fleet that looks busy and underperforms, or one that looks reliable and still cannot deliver the programme.
The editorial versions are in the Operating Notes on daily plant utilisation and machine availability, which go further into why a single fleet-wide percentage hides the constraint it is supposed to expose.
Repeated downtime is a maintenance signal
The pattern
One downtime event is an incident. The same machine, the same component or the same failure type turning up repeatedly is information, and it is usually information the maintenance record could have surfaced earlier. Downtime tracking does not diagnose a mechanical root cause and we are not going to claim it does. It records the events accurately enough that the pattern becomes visible, and the pattern is what sends someone to look properly.
Read alongside maintenance history, the record supports investigation into:
- Recurring failures on the same asset.
- Service that is overdue against actual hours rather than the calendar.
- The same component failing repeatedly across a machine or a class of machines.
- Parts patterns, where the same item keeps being ordered.
- Repair frequency climbing on an asset approaching the end of its economic life.
That is the point where a downtime record stops being a report and starts being a decision. A machine whose repair frequency is climbing and whose availability keeps falling is telling management something about whether it should still be in the fleet.
Where damage rather than wear is involved, the Operating Note on equipment damage records covers how attribution holds up when the cause is disputed.
Frequently asked questions
The questions operators ask first
What is downtime tracking software?Read the answerClose answer
Downtime tracking software records the periods when equipment is not performing its intended work, along with the cause, the asset, the operator, the site, the function responsible for clearing it and the recovery status. For heavy fleets the value is not the total hours. It is knowing which part of the operation the hours were lost to.
What is equipment downtime?Read the answerClose answer
Equipment downtime is time when a machine is not working because a specific operational constraint is preventing use. That constraint can be mechanical, but it can equally be a parts delay, a pending approval, a missing operator or a safety hold. Downtime is the event. Availability is what those events do to the capacity you can deploy.
What causes equipment downtime?Read the answerClose answer
Six categories cover most of it. Mechanical faults, maintenance and inspections, parts and supply delays, operational causes such as no operator or a work front that is not ready, administrative causes such as repair and purchase approvals, and external causes such as weather or site access. Only the first two sit with the workshop, which is why reporting downtime as one number misdirects the fix.
What is the difference between downtime and idle time?Read the answerClose answer
Idle time is a machine that is available and ready but not doing productive work, usually waiting on fuel, drawings, materials or an instruction. Downtime is a machine that cannot be used because something is preventing it. An excavator waiting for drawings is idle. An excavator waiting for a hydraulic part is down. Both erode productive capacity, though an idling engine also burns fuel and engine hours while a stopped machine on downtime incurs standing ownership and programme delay costs, and they are fixed by completely different people.
Operating Note: the hidden cost of equipment idle timeWhat is the difference between downtime and availability?Read the answerClose answer
Downtime is the event. Availability is the measure of how much of the fleet was ready and usable when the operation needed it. Downtime reduces availability, and it reduces it further the longer recovery takes. A fleet can report acceptable availability on average while one critical machine has been unavailable for a fortnight, which is why the events underneath the percentage matter more than the percentage.
Operating Note: machine availabilityHow is downtime recorded?Read the answerClose answer
At the event, by the operator or supervisor who is standing there, using offline-first field capture. The record saves on the device and syncs when signal returns, so a machine going down at a remote work front is logged at the moment it happens rather than remembered that evening.
Can downtime be categorised by cause?Read the answerClose answer
Yes, and it is the single thing that makes downtime reporting useful. A reason is assigned from a defined set at the point of capture, so downtime can be read by cause, by asset, by site and by shift instead of arriving as one undifferentiated total nobody can act on.
What is MTTR?Read the answerClose answer
Mean time to repair is the average time from a machine coming out of service to it being available again. It is a useful headline and a poor diagnosis, because it collapses diagnosis, approval, parts, repair and testing into one figure. An eleven-day MTTR can be a slow workshop or a fast workshop waiting ten days on a part and a signature.
How do parts delays affect downtime?Read the answerClose answer
On remote Ghanaian sites where specialist parts are sourced through Tema or overseas, the parts and approval legs can exceed the spanner time in the bay yet remain the least visible in a standard workshop report. Recording the parts wait separately stops a procurement bottleneck being read as a maintenance failure, and turns a repeated delay into a stocking decision rather than a recurring surprise.
How do repair approvals affect downtime?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 work order is pending. That time is an availability loss with no mechanical cause. Recording the approval status and who it sits with is what makes it visible instead of absorbed.
Can downtime tracking help construction companies?Read the answerClose answer
Yes. A machine out of service on a construction site is a work front that stalls and a programme that slips behind it. Downtime by cause, by site and by project is what lets a main contractor see whether the delay came from the workshop, the supply chain or the approval chain.
Construction operations in GhanaCan mining contractors use downtime tracking?Read the answerClose answer
Yes. Haul trucks, excavators, loaders and production equipment all queue behind each other, so a single machine down has a production consequence rather than just an availability one. On remote sites where parts and approvals both take longer, separating those legs from the mechanical one is where the recoverable time is.
Mining operations in GhanaCan plant hire companies use downtime tracking?Read the answerClose answer
Yes, and repair turnaround is the commercial number for a hire business. Unavailable equipment is lost rental days and a customer commitment that cannot be met. The recovery record is also what defends the position when a hire period or a deduction is disputed.
Plant and equipment hire in GhanaDoes GPS tracking show downtime?Read the answerClose answer
GPS shows that a machine stopped and where it stopped, which is real and worth having. It cannot show why it stopped, who owns clearing it, what action is pending or when recovery is expected, because none of those are signals a position feed carries. A machine can also be stationary and working, or moving and unproductive. Darikoda is the layer that captures the context around the stop.
How does Darikoda improve downtime visibility?Read the answerClose answer
By capturing the event at source with its cause, owner and recovery status, then holding it against the same asset record that carries hours, fuel, utilisation and maintenance. That is what lets management see the duration, the cause, which leg of the recovery the time disappeared into, and what it cost in deployable capacity.
Does this help with claims defence?Read the answerClose answer
Yes. If a client disputes your timeline, you hold a timestamped record of exactly why the equipment was delayed, what was pending, who it was pending with and when it returned to service. That is an evidenced position rather than an argued one.
See 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.