Operational intelligence is achieved by maintaining an immutable operating record.
The operating record is the structured, time-stamped, attributed history of what actually happened on site. Every fuel event. Every machine state change. Every approval. Every piece of certificate evidence. Every cross-hire deduction.
The intelligence is what you derive from the record: per-machine cost, per-shift truth, per-cert defendability, real-time across every project. You cannot have the intelligence without the record. The record without the intelligence is just data.
Operational intelligence software creates an immutable, time-stamped operating record of what happened on site. For Ghana's fleet-heavy operators, this means defending fuel reconciliation, mechanical availability, cert evidence, and approval cycles against the gap between site reality and office reporting.
Definition
Operational intelligence, plainly stated.
In plain terms: Darikoda creates the trusted field record your ERP, tracker, and finance team currently rely on people to reconstruct.
This is why operational intelligence does not replace your ERP, your telematics tracker, your CMMS, or your BI dashboard. It sits underneath them and feeds them the per-asset, per-shift truth they cannot produce on their own.
Captured at source. Defendable in dispute. Compoundable across contracts.
One record of what actually happened on site, that still holds up when the QS arrives, the deduction lands, or the rate is renegotiated.
What operational intelligence isn't.
Operational intelligence is often confused with adjacent tool categories. Each of those tools does its own job well. None of them are the operating record.
ERP / accounting system
Does well
Invoices, assets, depreciation, financial transactions
Doesn't see
What happened on site at the moment the work happened
GPS tracker / telematics
Does well
Location, basic utilisation, sometimes fuel
Doesn't see
Per-machine cost, operator attribution, maintenance history, approvals trail, certificate evidence, deduction defence
OEM telematics (Cat Product Link, KOMTRAX)
Does well
Single-OEM machine-health data
Doesn't see
Mixed-fleet visibility, manual fuel events at the bowser, parts and consumables, contract-level financials
CMMS / maintenance system
Does well
Work orders, scheduled maintenance
Doesn't see
Fuel integrity, operator behaviour, approvals, payment evidence, hire-deduction defence
Business intelligence (Power BI, Tableau)
Does well
Aggregating and visualising data from other systems
Doesn't see
Capturing data at source, structuring field reality, attributing actions to operators in real time
Operational intelligence (Darikoda)
What it is
The operating record, fuel, machine, downtime, certificate, approval and cross-hire cycles, attributed at source. The layer that makes the others credible.
| Tool category | What it does well | What it doesn't see |
|---|---|---|
| ERP / accounting system | Invoices, assets, depreciation, financial transactions | What happened on site at the moment the work happened |
| GPS tracker / telematics | Location, basic utilisation, sometimes fuel | Per-machine cost, operator attribution, maintenance history, approvals trail, certificate evidence, deduction defence |
| OEM telematics (Cat Product Link, KOMTRAX) | Single-OEM machine-health data | Mixed-fleet visibility, manual fuel events at the bowser, parts and consumables, contract-level financials |
| CMMS / maintenance system | Work orders, scheduled maintenance | Fuel integrity, operator behaviour, approvals, payment evidence, hire-deduction defence |
| Business intelligence (Power BI, Tableau) | Aggregating and visualising data from other systems | Capturing data at source, structuring field reality, attributing actions to operators in real time |
| Operational intelligence (Darikoda) | The operating record, fuel, machine, downtime, certificate, approval, cross-hire cycles, attributed at source | (this is the layer that makes the others credible) |
The margin is made and lost on site, by the shift.
Not in the office. In the hours, litres and loads that either get captured at source or get reconstructed from memory weeks later.
Where the leaks live.
Fuel
Dispensed at the bowser, consumed by the machine, reconciled at head office. Three handovers. Three places the number can drift.
Machine
Assigned to a project, worked through a shift, stood down for parts or weather, repaired and returned. Four states. Most operations only track the first.
Downtime
Diagnosed, waiting parts, repairing, testing. Most operations track downtime as one number, so they cannot see whether the real problem is procurement, scheduling, workshop capacity, or repair time.
Certificate
Measured (joint with consultant), evidenced (BoQ), submitted (IPC), defended (when the consultant cuts). Cert speed is cash flow. Cert defensibility is margin protection.
Approval
Requested (WhatsApp), approved (GM), delayed, costed. Most operations cannot see the cost of an approval delay until it has already lost them money.
Cross-hire
Plant hired in or out, machine hours and fuel sitting in two separate records. When they do not match at month-end, the reconciliation becomes a dispute and someone absorbs the gap.
Materials
Bought. Delivered. Issued. Consumed. By month-end the variance has already stopped a crew, started a supplier dispute, or shown up in the wrong number.
01 / The Gap
What your ERP can't see.
Every fleet operator I sit with tells me the same thing. Something is leaking. Fuel numbers don't add up. Certs run three weeks late. A dozer sat two months and no one can say why. You feel the money walking out. You can't point at it.
You've done the sensible things. A good GM. Trackers on the trucks. An ERP at GHS 150K a year, sold to you as total visibility. Two years in, you're still asking finance to pull a spreadsheet.
Your ERP was built for accounts. Invoices, assets, depreciation. Your question is different.
- Which machine earns? Which bleeds?
- When fuel goes missing, where?
- When a cert delays, which chainage is stuck?
No tool you own was built to answer that.
What you see
Your tracker shows the truck moved.
What you don't
Not that it left full and came back empty.
What you see
Your ERP shows GHS 185,000 on parts last quarter.
What you don't
Not that 40% went to two machines you should have retired two years ago.
What you see
Your spreadsheet shows the dozer came back to site.
What you don't
Not that it sat six weeks waiting for a job no one assigned.
What you see
Your supervisor says no downtime.
What you don't
Your workshop has four machines waiting for parts.
What you see
Your cert takes three people a week.
What you don't
The data was ready two weeks earlier.
Every card above is real. Anonymised.
That's what Darikoda was built to fix.
The work gets done. The margin leaks on the way to the office.
Not in the digging. In the gap between what the site did and what the month-end record can prove.
The shape of the leak
Small per-event drift. Large at the end of the year.
GHS 1M
Illustrative 5% recovery on a GHS 20M annual fuel spend.
(Illustrative model, your number from the audit.)
Pays for itself
The recovered leak covers the work. The audit gives you the exact number for your fleet, sized against what you stand to recover.
2 people, 1 week
Month-end cert pack as an export. Two people for a week, not ten for a month.
It works at this size. It stops working at the next one.
The informal system runs on trust, memory, and everyone knowing each other. Then you win a second contract, the fleet grows, or a new site opens. Here are six places where the informal system quietly fails.
Manual entry becomes one tap.
Paperwork search becomes instant query.
Not in this file
try the other four spreadsheets?
Payment cert PRJ-TEMA Ch. 12+400 to 14+200
Phone-chase approvals become one tap.
Fuel top-up 420L M-04 Kwame
GHS 3,108, who signs off?
Fuel top-up 420L M-04 Kwame
GHS 3,108 within limit
The supervisor on the tablet.
The fitter in the workshop.
The operator at the bowser.
Six moments on their shift where paper dies and margin comes back.
Three are how the day grinds for one person on shift.
Three are how the month falls apart between people at the office.
Month-end scramble becomes live dashboard.
"Who did what" becomes an immutable trail.
A 17-day dispute becomes a 2-minute sign-off.
Evidence: reconstructed from memory, gaps in the log.
Evidence: 47 work orders, 12 dispense logs, GPS-confirmed.
This is what you get back.
Six small shifts. One compound effect. The kind of time and cash that stops leaking once the record is in place. (Illustrative model, your number from the audit.)
Times compound. Supervisors stop chasing paper. Approvers stop dodging calls. Finance stops begging for data. The business starts running like a system.
Three engines, applied across every vertical.
Cost attribution, downtime structuring, fuel integrity. Each expresses differently per vertical, but the architecture underneath is the same.
Cost attribution
Cost per output unit, captured at the moment of the output. Cost per tonne in mining, per cubic metre in construction, per chainage metre in civils, per billable hour in plant hire. Live, not lagged. Per machine, per operator, per shift, per project.
Downtime structuring
Diagnosed, waiting parts, repairing, testing. Tracked at component level, not as one aggregate downtime number. The real bottleneck stops hiding inside a single breakdown figure, so it can finally be named and acted on.
Fuel integrity
Captured at source, wherever fuel changes hands, and tied to the operator, machine and project behind it. The largest single cost line in heavy-fleet operations becomes the most defensible.
The same operating record, under every Ghana fleet.
Mining, construction, civils, plant hire. Different machines, one gap between what the field did and what the office can account for.
Ghana, specifically
Operational intelligence in Ghana, specifically.
Poor signal connectivity
WhatsApp approvals
Mixed fleets
Site-to-office gap
Delayed reporting
Cert-heavy workflows
Generic operational intelligence software pretends to fit every operation. Darikoda is built to fit yours, not force you into a generic mould.
How operational intelligence applies, per vertical.
Each vertical applies the same operating record to its own commercial reality. Click through to the specific buyer brief.
Mining contractors and full miners.
Defending billable hours, fuel evidence at the mine's bowser, mechanical availability per asset, cost-per-tonne and cost-per-ounce visible the moment the work happens, L.I. 2431 procurement-list compliance.
Read the buyer brief
Construction developers, main contractors, and subcontractors.
Per-project profitability surfaced before quarterly review, material consumption variance the day it appears, subcontractor coordination at scale, approval cycle visibility, cert preparation that takes 2 people 1 week instead of 10 people 1 month.
Read the buyer brief
Civils contractors on FIDIC red book.
Chainage-level cost visibility, IPC defence under joint measurement, GHA reporting cycles, Big Push delivery discipline, plant utilisation across multiple road projects.
Read the buyer brief
Plant hire firms and main contractors operating internal hire.
Per-machine utilisation, hire-rate defence, deduction support against subcontractor disputes, redeployment visibility, working / faulty / not needed daily monitoring as a live commercial record.
Read the buyer briefThe cross-vertical reality
Plant hire and fleet-owner businesses serve mining, construction, civils, and quarry clients. Your operating record concerns are the same regardless of which vertical you serve most. That is why Darikoda's architecture is one record, applied per role.
Regulatory context referenced above: the L.I. 2431 procurement list is published by the Minerals Commission (Sixth Edition, January 2025), and the Big Push programme carries a GHC 30.8 billion allocation in the 2026 Budget.
Common questions about operational intelligence.
What is operational intelligence software?
Software that maintains an immutable operating record: the structured, time-stamped, attributed history of what happened on site. The intelligence is what you derive: per-machine cost, per-shift truth, per-cert defendability, real-time across every project. The record is the foundation. The intelligence is the output.
How is operational intelligence different from ERP?
ERP handles financial transactions: invoices, assets, depreciation, GL, AR, AP. It does not see what happened on site. Operational intelligence captures the field reality and feeds the ERP the per-asset, per-shift truth it cannot produce on its own. The two integrate.
How is it different from fleet management software?
Fleet management software (Trackunit, Samsara) handles location, basic utilisation, sometimes fuel telemetry. What it does not carry is the commercial reality behind the machine: which contract the hour belonged to, who ran it, what the work cost, why a deduction is disputed. Operational intelligence is the layer above that ties machine data to commercial reality.
How is it different from telematics or GPS tracking?
GPS tracking and telematics (Sky Ledge, Cat Product Link, KOMTRAX) capture location, hour-meter, machine-health telemetry. Operational intelligence captures the operator behind the machine, the contract behind the hour, the cost behind the fuel event, the dispute behind the deduction. Telemetry is an input. Operational intelligence is the structured record that makes the telemetry commercially meaningful.
Why does Ghana need operational intelligence software specifically built for it?
Ghana's operating reality includes L.I. 2431 procurement-list discipline, FIDIC red book joint measurement under GHA, the Big Push pipeline, internal cross-hire on road projects, sliding-scale royalty regime, parts lead times from Tema, Starlink-on-patchy-4G connectivity, WhatsApp as the default approval channel. Generic global tools weren't built for this reality. Darikoda was.
What does getting started look like?
First the operating record is configured to your fleet, contracts, reporting cadence and roles, and signed off only when it is ready for your operation. Then it proves itself in your live contracts before any ongoing commitment. The pace follows your operation, not a fixed clock.
How is it priced?
Every operation is priced from its own audit, because the leak and the fleet are different in each one. The free 30-minute audit produces the leakage number for yours, and the figure that matters is what you stand to recover against it. You keep the one-page leakage report regardless of next steps.
From the Operating Notes
Field analysis that goes deeper on this.
See how operational intelligence applies to your operation.
The Operational Audit takes 30 minutes. The one-page leakage report identifies which engine your operation is leaking through: cost attribution, downtime structuring, or fuel integrity. You keep it 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.