What every case study must contain
Outcome frameworks
| Area | Evidence to retain | Example calculation |
|---|---|---|
| Fleet visibility | Asset list, reporting uptime, event definitions, coverage gaps and support records. | Reporting assets ÷ expected reporting assets for the stated period. |
| Fuel monitoring | Calibration tables, refuel records, sensor events, investigations and reconciled consumption. | Verified variance compared with the same operational baseline and inclusion rules. |
| Generator telemetry | Controller data, run hours, alarm history, maintenance logs and power-state records. | Confirmed run time or alarm response measured with the declared data source. |
Why this matters
A percentage without a denominator, a time window or an operating context can mislead. Fuel use changes with route, load and season. Generator runtime changes with utility availability. Fleet event volume changes with configuration and network coverage. We publish these conditions with the result so readers can judge whether it applies to their operation.
Contribute an approved case study
Existing GT AFRIK customers can ask us to review a deployment for publication. We will agree the question, verify the records, define what can be disclosed and send the final draft for approval.