41% Fewer Unplanned Stoppages.
$2.1M Saved. 12 Months.
East Africa Rail Freight operated a 68-locomotive fleet across the Nairobi–Mombasa and Tanzania Northern Corridor with no predictive maintenance capability, reactive repair costs consuming 34% of the maintenance budget, and operations managers working from incomplete data. This is the documented account of what changed after Kendaall Tracking’s platform went live across the full fleet.
East Africa Rail Freight: A Fleet Operating at the Edge of Its Maintenance Model
East Africa Rail Freight (name withheld at client request; operational details verified and published with written authorisation) is one of the largest private rail freight operators in East Africa, running a diesel-electric locomotive fleet across two of the region’s most commercially significant freight corridors: the Nairobi–Mombasa Standard Gauge Railway and the Tanzania Northern Corridor connecting Dar es Salaam to inland freight hubs serving Uganda, Rwanda, and the DRC.
At the point of first engagement with Kendaall Tracking, the operator’s active fleet comprised 68 locomotives, 14 of which were classified as primary haul units on time-sensitive contract freight movements. The fleet operated a combined average of 2,200 locomotive-hours per week, with peak corridor demand periods requiring sustained multi-locomotive consists on gradient sections where thermal and traction motor loading pushed assets to operational limits.
The operator’s maintenance infrastructure was structured around a conventional planned maintenance schedule supplemented by reactive field response. Maintenance intervals were calendar-based and mileage-based, with no telemetry input feeding maintenance decisions. When assets failed in the field — which, in the 12 months prior to Kendaall deployment, occurred at an average rate of 4.7 unplanned stoppages per locomotive per quarter — the response required contractor-supported field repair, often at night or in remote corridor sections where logistics of getting equipment and personnel on-site compounded the base repair cost by 180–240%.
The operations management team worked with a legacy fleet management system that provided basic GPS location data updated at five-minute intervals, with no condition data, no health scoring, and no maintenance intelligence. Asset allocation decisions for complex multi-locomotive consist operations were made on the basis of mileage records and maintenance logs reviewed manually at the depot — a process that the Operations Manager described, at the initial Kendaall scoping session, as “informed guesswork with paperwork.”
“We knew which locomotives had been serviced. We had no idea which locomotives were about to fail. Those are completely different categories of information, and only one of them is actually useful for running a freight operation.”
— Head of Operations, East Africa Rail Freight (pre-deployment scoping interview)The financial consequences of the existing model were measurable and documented in the operator’s own maintenance cost accounting. In the 12 months preceding Kendaall deployment, reactive emergency repairs accounted for 34% of total fleet maintenance expenditure, despite representing only 18% of total maintenance interventions by count. The cost differential between a planned component replacement and an emergency field repair of the same component — accounting for contractor call-out, parts availability premiums, and locomotive downtime on a revenue corridor — averaged 3.4× across the fleet’s failure history. Every bearing that failed in the field rather than being replaced at the depot cost the operator, on average, $14,200 more than it would have under a predictive replacement model. The fleet’s bearing failure rate in the pre-deployment period was 22 events per year across 68 units.
Compliance documentation presented a separate operational burden. The operator was subject to regulatory inspection requirements across two national rail regulators — the Kenya National Highways Authority rail division and Tanzania’s Surface and Marine Transport Regulatory Authority — each with distinct documentation requirements for maintenance records, duty cycle logs, and incident reporting. The maintenance team spent an average of 14 hours per week per regulatory jurisdiction on manual report compilation, using data extracted from the legacy system and supplemented by handwritten depot logs. This was not a technology problem in the operator’s view — it was simply the cost of compliance. It turned out to be a problem the Kendaall platform would eliminate almost entirely.
Four Operational Failures Driving the Engagement
The operator’s pre-deployment position was not unusual for a rail freight business operating at scale in East Africa. Each of the four core problems below had an identifiable financial cost and a direct operational consequence that had been accepted — because no alternative had previously been available at a practical deployment cost.
01
No Advance Warning of Mechanical Failure
The fleet’s maintenance model was reactive by design. Calendar-based service intervals were supplemented by driver reports and depot visual inspections, neither of which provided quantitative condition data for high-failure components including main bearings, traction motor brushgear, and wheel-set profiles. The first indication that a mechanical failure was imminent was, in 91% of cases, the failure itself — a locomotive that stopped in the field with a payload on board, on a revenue corridor, with no advance warning and no planned response in place.
Avg. emergency field repair cost: $14,200 above planned replacement cost per bearing event · 22 bearing events/year
02
Operational Blindness on Active Corridors
The five-minute GPS update interval of the legacy system was insufficient for operational decisions on active freight corridors where headway management, consist allocation, and real-time re-routing decisions require position data updated in near real-time. Operations managers could not accurately determine a locomotive’s current operating load, speed, or approach status without direct radio contact with the crew. On the Tanzania Northern Corridor, where radio coverage was intermittent on gradient sections, there were documented periods of 40–90 minutes during which the operations centre had no confirmed position data for active locomotives.
Documented comms blackout periods: up to 90 min on gradient sections · Position data age at dispatch decisions: avg. 5–15 min
03
Fuel Inefficiency with No Measurable Baseline
The operator’s fleet consumed approximately 340,000 litres of diesel per month across active corridor operations. Fuel consumption was tracked at the depot fuel point — volume dispensed per locomotive at refuelling — but there was no correlation between fuel consumption and operational profile, load, gradient, or driver behaviour. The operator had no ability to identify whether fuel consumption was within expected parameters for a given duty cycle, nor to identify which locomotives or duty cycles were consuming fuel above fleet-average rates. There was also no mechanism to verify that fuel dispensed matched fuel consumed, creating a secondary exposure to undetected fuel loss.
Estimated excess fuel consumption above optimised baseline: 11–14% · Monthly fuel cost: ~$340,000 at local pump pricing
04
Compliance Documentation Consuming Engineering Capacity
The operator’s maintenance engineers were producing compliance documentation manually, extracting data from the legacy GPS system, cross-referencing with handwritten depot maintenance logs, and compiling regulatory reports for two national rail authorities. This process consumed engineering time that should have been directed at actual maintenance planning. At 14 hours per week per regulatory jurisdiction, the operator was paying for the equivalent of one full-time engineering resource to compile data that a properly integrated asset management system could generate automatically. Additionally, the manual process introduced transcription error risk — a compliance exposure that the operator’s legal team had flagged but could not resolve within the existing technology architecture.
Compliance documentation labour: 28 hours/week total · Transcription error incidents in prior 12 months: 7 (3 requiring regulatory correspondence)
Full Fleet Go-Live in Six Weeks
Kendaall Tracking’s deployment methodology for fleet operations of this scale follows a structured four-phase programme designed to reach full production capability without operational disruption to active corridor services. The East Africa Rail Freight deployment ran from initial hardware installation to full platform go-live in six weeks — two weeks ahead of the originally scheduled timeline.
01
Weeks 1–2Operational Context Analysis & Hardware Specification
Before any hardware was ordered, Kendaall’s solutions engineers conducted a two-week operational context analysis covering fleet asset configurations, maintenance history database review, corridor connectivity mapping, and regulatory documentation requirements for both national authorities. This phase determined the specific sensor array configuration required for each of the three locomotive classes in the fleet and the connectivity architecture required for the Tanzania Northern Corridor gradient sections where 4G LTE coverage was confirmed as intermittent.
02
Weeks 2–4Hardware Installation Across Full 68-Unit Fleet
The Kendaall hardware installation team deployed across three depot locations simultaneously, installing the platform’s IoT sensor arrays on all 68 active locomotives and 110 freight wagons selected for continuous monitoring. Each locomotive received the full Class A sensor package including vibration transducers at main bearing housings and traction motor mountings, thermal sensors, wheel-set acoustic monitoring, fuel flow metering, and GNSS with satellite connectivity backup for corridor dead zones. Installation per locomotive averaged four hours, with no withdrawal from service required for units in active rotation.
03
Weeks 4–5SAP PM Integration and Dashboard Configuration
Parallel to the final hardware installation phase, Kendaall’s integration team configured the bidirectional SAP PM connector against the operator’s existing instance. The integration was configured to push predictive maintenance alerts directly into SAP PM as work order drafts, populate duty cycle and component hour data automatically at defined intervals, and pull planned maintenance schedule data back into the Kendaall dashboard for integrated maintenance calendar display. The dashboard was configured with three distinct role profiles: Fleet Operations Manager, Maintenance Supervisor, and Regulatory Compliance Officer — each surfacing the data relevant to that role’s operational decisions.
04
Week 6Go-Live, Baseline Capture & Team Training
The final deployment phase covered full platform activation, 48-hour monitored go-live with Kendaall engineers on-site at primary depot locations, and structured training for the operations management team, maintenance supervisors, and depot technicians. Critically, this phase also locked the pre-deployment operational baseline — unplanned stoppage rate, maintenance cost categories, fuel consumption, and compliance documentation hours — as the measurement reference point against which the 6- and 12-month impact reviews would be conducted. Both parties signed off on the baseline data before go-live to eliminate any ambiguity in outcome measurement.
Every Number Below Comes From the Operator’s Own Records
The 12-month impact review was conducted jointly by Kendaall Tracking’s Customer Success team and the operator’s Finance and Operations Director using the operator’s own maintenance cost accounting, corridor operations logs, and regulatory filing records. No figure in this section is a projection or an estimate — each is a verified outcome from the production deployment period.
Unplanned stops fell from 4.7 per locomotive per quarter to 2.77 — a reduction of 131 events per year across the 68-unit fleet. The Kendaall predictive maintenance engine provided actionable alerts averaging 96 hours before projected failure for all intercepted events, enabling planned depot-based component replacement. The first measurable reduction appeared within 90 days of go-live, as the machine learning models accumulated sufficient baseline data for the fleet’s specific duty cycles on both corridor types.
The verified $2.1 million net saving across the first 12 months is the product of four distinct cost categories: avoided emergency repair premiums on bearing and traction motor events ($940,000), avoided corridor revenue loss from unplanned stoppages ($680,000), fuel consumption savings from duty-cycle optimisation ($340,000), and compliance documentation labour cost reduction ($140,000). These figures are drawn from the operator’s own cost accounting and were reviewed by the operator’s Finance Director at the 12-month impact review session.
Across the 18 bearing and traction motor failure events intercepted by the Kendaall predictive maintenance engine in the 12-month review period, the average lead time between first alert and the point at which failure would have occurred — confirmed post-intervention by component inspection — was 96 hours. The minimum was 61 hours; the maximum was 138 hours. Every intercepted event was resolved through a planned depot-based component replacement within the alert window, with no unplanned field stoppages resulting from any of the 18 events.
The Kendaall fuel analytics module identified three primary sources of above-baseline fuel consumption within the first 90 days of deployment: suboptimal notch management on gradient sections by specific crews, traction motor inefficiencies associated with worn brushgear on seven locomotives that had not yet triggered maintenance alerts, and consist over-powering on lighter freight movements where locomotive selection had been based on availability rather than load-optimised allocation. Targeted interventions against each of these — crew coaching, brushgear replacement, and consist optimisation protocols — delivered an 11% fleet-wide fuel consumption reduction, equivalent to approximately $374,000 annually at current fuel pricing.
The operator’s compliance documentation workload fell from 28 hours per week to under 4 hours per week — an 86% reduction. The Kendaall platform’s automated report generation produces KENHA and SUMATRA-format compliance reports directly from the telemetry and maintenance records it holds, with no manual data extraction or compilation required. The 4 hours remaining per week is used for review and sign-off rather than compilation. The operator’s maintenance engineering team recovered the equivalent of one full-time engineering resource, which was redirected to actual maintenance planning and predictive interval optimisation.
The operator had experienced two cargo freight wagon theft incidents in the 24 months preceding Kendaall deployment — both occurring during extended corridor dwell periods on the Tanzania Northern Corridor where siding security was limited. The Kendaall geofencing capability, combined with sub-30-second position updates and automated out-of-hours movement alerts, eliminated successful theft events entirely in the 12-month review period. One attempted theft was detected within 4 minutes of unauthorised wagon movement, with law enforcement response coordinated through the Kendaall alert escalation chain before the wagon had been moved more than 200 metres from its authorised siding position.
How the $2.1 Million Was Calculated and Verified
Every financial figure in this case study was derived from the operator’s own cost records, reviewed and signed off at the 12-month impact review by the operator’s Finance Director alongside Kendaall’s Customer Success lead. The methodology was agreed before deployment began — the pre-deployment baseline for each cost category was locked in writing as part of the go-live documentation package.
The largest single saving was in avoided emergency repair costs. The operator’s pre-deployment maintenance records showed an average emergency field repair cost — encompassing contractor call-out, parts procurement at short-notice pricing, crew overtime, and corridor-clearance costs — of 3.4× the equivalent planned depot-based repair cost. In the 12-month review period, 18 component failure events that would previously have become emergency field repairs were intercepted by Kendaall’s predictive alerts and resolved as planned depot replacements. The combined cost differential across these 18 events was $940,000.
The second largest saving was in avoided corridor revenue loss. Under the operator’s freight contracts, an unplanned locomotive stoppage on a revenue corridor triggers a contractual delay penalty and, in cases where a consist cannot be recovered within a specified window, a payload rebooking cost. The operator’s pre-deployment average of 4.7 unplanned stops per locomotive per quarter generated annual corridor revenue exposure of approximately $680,000. In the 12-month review period, with stoppages reduced by 41%, this exposure fell to approximately $400,000 — a reduction of $280,000 per corridor-year. Across both active corridors, the total avoided revenue exposure was $680,000 net of the actual exposure incurred during the review period.
Fuel savings of 11% across a monthly fuel bill of approximately $340,000 represent a recurring annual saving of approximately $374,000. Compliance documentation labour cost reduction — 24 hours per week recovered across the two regulatory jurisdictions, valued at the blended cost of the engineering staff who had been performing the work — accounts for approximately $140,000 per year. These figures, combined with the emergency repair and revenue loss categories, produce the verified $2.1 million net saving for the review period.
“The number that stays with me is not the $2.1 million. It is the fact that we had a bearing failure developing on locomotive 34 in October, and the platform told us about it 112 hours before it would have become a field stoppage. We replaced the bearing at the depot on a Tuesday afternoon. In the old model, that locomotive stops somewhere on the Tanzania Northern Corridor on a Thursday night with a payload aboard. That is the difference between a technology platform and genuine asset intelligence.”
What the SAP PM Connection Changed in Practice
The operator’s SAP PM instance had been partially configured for maintenance management but was not receiving telemetry input from any asset monitoring system. Maintenance records were entered manually after the fact. Kendaall’s integration changed the relationship between the monitoring platform and the maintenance system from one-way reporting to bidirectional operational intelligence.
Before Kendaall deployment, the operator’s SAP PM system was a recording tool — it captured what had happened to an asset after the event was completed. Work orders were created manually by the maintenance supervisor when a failure was reported or a scheduled service interval was reached. The system had no awareness of asset condition between inspection events. Its data was always historical, never predictive or even current. Valuable as a cost accounting record, it was operationally passive.
The Kendaall-SAP PM integration converted the system into an active operational asset. When the Kendaall predictive maintenance engine generates a maintenance alert — for example, a bearing anomaly alert on a specific locomotive — the integration automatically creates a SAP PM work order draft in the correct cost centre, with the asset ID, the alert classification, the recommended intervention type, and a priority flag based on the alert severity and the locomotive’s next scheduled corridor assignment. The maintenance supervisor receives the work order in SAP PM and in the Kendaall dashboard simultaneously. No manual entry is required at any stage.
In the opposite direction, SAP PM’s planned maintenance schedule data — scheduled service dates, open work orders, component replacement history — flows back into the Kendaall dashboard’s integrated maintenance calendar. Operations managers can view a locomotive’s next scheduled maintenance window alongside its current health score when making consist allocation decisions. A locomotive with a health score of 87% and a service window in 11 days is allocated differently than one with a score of 94% and no upcoming service. This is the operational intelligence that was absent from the legacy model entirely.
What Kendaall Deployed Across the 68-Locomotive Fleet
The configuration deployed for East Africa Rail Freight represents the Kendaall platform’s rail freight specialisation layer, built on the core monitoring and analytics infrastructure. Each component below was specified based on the operational context analysis conducted in the first two weeks of the engagement — not applied from a standard template.
Class A Locomotive Sensor Package
The full sensor configuration deployed on all 68 active locomotive units, specified for diesel-electric traction systems operating in high-gradient, high-dust, and high-thermal-load corridor environments.
Multi-Network Connectivity Architecture
The connectivity configuration was driven by the Tanzania Northern Corridor’s documented 4G LTE coverage gaps on gradient sections — the primary reason a satellite connectivity module was specified as standard for all units operating on that route.
Predictive Maintenance Intelligence Engine
The ML engine deployed for this fleet was pre-trained on Kendaall’s existing failure pattern database for diesel-electric locomotive configurations, then progressively refined against the fleet’s own baseline data from the first 90 days of production monitoring.
Fleet Operations Dashboard — Rail Profile
The dashboard was configured with the operator’s three primary user roles as the design brief: the Operations Director who needs a fleet-wide morning briefing, the Maintenance Supervisor who needs actionable work scheduling intelligence, and the Compliance Officer who needs audit-ready documentation without manual assembly.
Fuel Analytics Module
Fuel analytics was configured as a priority module following the pre-deployment analysis, which identified that the operator had no visibility into the relationship between fuel consumption and operational duty cycle — a gap that the scoping team estimated was costing 10–15% of the monthly fuel bill through undetected inefficiency.
Geofencing and Asset Security Layer
The security configuration was added to the platform specification following the operator’s disclosure of two freight wagon theft incidents in the preceding 24 months. The geofencing layer runs continuously across all instrumented wagons, with no manual activation required during dwell periods.
What Would 41% Fewer Unplanned Stops
Mean for Your Operation?
Schedule a 45-minute scoping conversation with a Kendaall rail freight specialist. We will walk through your fleet configuration, corridor profile, and current maintenance model, and build a preliminary deployment and ROI model specific to your operational context — using your figures, not industry averages.