SDLG Excavator Fleet Planning: Matching Excavators, Tippers and Support Machines
Watch — 67 seconds: the complete SDLG range in Kenya
The excavator family this fleet guide serves — every SDLG machine in one film from the Ruai yard.
Video not playing? Download it or watch on YouTube — and for a machine of your own, call +254 718 686 967.
A fleet is not a collection of machines; it is a conversation between them — the excavator speaks in cycles, the tippers answer in hauls, the dozer grumbles about the face, the roller waits on the water, and the whole site moves at the speed of the slowest sentence. This guide covers SDLG excavator fleet planning the way the conversation actually runs: matching excavators and tippers through the cycle-and-haul arithmetic, then staffing the support rows — dozing, compaction and water supply — so that every machine's production lands where the programme needs it, across every project scale.
Quick answers if you are planning now: the excavator tipper matching arithmetic sizes the truck fleet, the support rows keep the matched machines working, and the interactions between the rows decide whether the fleet hums or queues. The mining-face version sits in the E6505H mining fleet planning guide, the tipper sizing side in the tipper fleet sizing guide and the range context in the excavator sizes explained guide; the desk at +254 718 686 967 plans the whole conversation.
| The core arithmetic | Excavator cycle time and bucket capacity against truck capacity and truck haul time — the matched pair everything else serves |
| The support rows | Dozing, compaction and water supply — the machines that keep the matched pair productive, each waiting on the others in turn |
| The interaction rule | Fleets fail at the interfaces, not the machines — the queue, the dry lift, the ungraded face and the unwatered layer are interface failures wearing machine costumes |
| The scale rule | The arithmetic's shape holds from the single-excavator plot cut to the multi-face quarry — only the numbers move, so the method scales |
| Verification date | 2026-11-03 |
The matching arithmetic: excavators and tippers
The construction fleet planning Kenya conversation starts with two timed loops. The excavator's loop: bucket capacity and fill factor against the excavator cycle time — dig, swing, dump, return — measured on the face the site actually presents. The tipper's loop: payload against the round trip — load, truck haul time out and back, queue, dump, return. Matching the loops: the number of tippers equals the tipper cycle divided by the loading time per truck, so the excavator never waits and no tipper queues long. The rows that distort the match: the haul road's condition, which moves the haul time more than the distance suggests; the dump point's turnaround, often the cycle's forgotten quarter; and the face's diggability, which moves the loading time more than the bucket's nameplate admits. The arithmetic fits on one page; the honesty is in timing both loops on the actual site rather than the planned one.
The support rows: dozing, compaction and water supply
The support machines planning rows complete the fleet. The dozer keeps the face and the haul roads in shape — the machine whose absence queues every other machine it serves, and whose production is everyone else's production. The roller serves the specification — lift thickness, moisture and pass count working to the testing regime, its production pacing the lift schedule the programme demands. And the water supply — bowser or source and distribution — serves the dust, the moisture conditioning and the compaction's honest moisture window together: the water supply fleet row is the quiet multiplier, because dry lifts refuse compaction, dusty roads slow hauls, and both bills arrive as fuel the matched pair burns unproductively. The compaction and water supply rows interact deliberately: the layer cannot compact without the moisture, the moisture cannot hold without the water plan, and the water plan is sized by the area and lifts the roller must cover per shift. Plan them as one row and they cost little; plan them apart and they bill separately, permanently.
The interaction rule: interfaces, not machines
Fleets rarely fail at their machines; they fail at the interfaces between them. The queue at the loading point: a matching error, not a truck problem. The lift refused by the tester: a water row failure, not a roller failure. The haul that doubled: a dozer row neglected, not a tipper's fault. The idle excavator behind a late blast: a planning interface, not an equipment one. The discipline that catches interface failures is the fleet review: the loops and rows timed together, the queues measured, the refusals counted, and the slowest sentence in the conversation found before it writes the week's production. The SDLG excavator fleet Kenya programmes that run this review weekly move the interface before it becomes the bottleneck — because by the time the queue is visible from the gate, the week has already paid for it.
Fleet by project scale: the same method, different numbers
| Scale | The fleet conversation looks like | The planning emphasis |
|---|---|---|
| Small — plot cuts, foundations, single site | One excavator, one or two tippers, a compact roller and a water arrangement | Multi-tasking machines and flexible roles; the interfaces are few but still timed |
| Medium — road sections, estates, water pans | Excavator and tipper fleet matched, dozer on the roads, roller on the lifts, bowser on rotation | The matching arithmetic earns its keep; the support rows staffed deliberately |
| Large — quarries, dams, mining support | Multiple faces, matched fleets per face, dedicated support machines and water systems | The interface review becomes the management system; the per-face loops measured separately |
The fleet by project scale framing is deliberately structural: the small fleet's excavator and the quarry's face machine speak the same arithmetic at different volumes, and the SDLG excavator fleet planning method scales because the loops and interfaces are the same loops and interfaces — only the fleet's patience for queues changes.
Misuse patterns that unmake fleets
- The machine-first plan: excavators specified before the tippers — the arithmetic run backwards and the trucks inherited to fit.
- Support priced at zero: the dozer, water and compaction rows discovered at the first dry, ungraded, unwatered shift.
- The queue accepted: waiting treated as normal — the interface failure normalised into the programme.
- Loops timed on the plan, not the site: cycles and hauls from the tender's optimism — the actual site invoices the difference.
- Scale copying: the small fleet's habits copied to the large site — the interfaces multiplied, the review never added.
Five checks before the fleet plan is signed
- Both loops are timed: excavator cycles and tipper hauls measured on the actual site.
- The match is calculated: truck count from the timed loops, refreshed per material change.
- The support rows are staffed: dozer, compaction and water planned as one interacting row.
- The interfaces are reviewed: queues, refusals and waits measured weekly.
- The plan scales honestly: per-face loops and interfaces measured separately where the site multiplies.
Working the knowledge with the desk
Send the project scale, production target and site details to +254 718 686 967 and the desk plans the whole conversation — the matched excavator and tipper fleet, the dozer, compaction and water rows, and the review rhythm that keeps the interfaces ahead of the bottlenecks. The SDLG excavator fleet Kenya plan is quoted with the machines, so the fleet arrives speaking one arithmetic. And the contractors who plan the conversation — the loops, the support rows and the interfaces together — own sites where the machines never queue, the lifts never refuse, and the slowest sentence is the one the review found before the week paid for it.
Frequently asked questions
1. How do we match excavators and tippers?
Time both loops — the excavator's cycle and the tipper's haul — on the actual site; the truck count is the tipper cycle divided by the loading time per truck, refreshed per material change.
2. What support machines does an excavation fleet need?
The dozer for faces and haul roads, the roller for the compaction specification, and the water supply for dust and moisture conditioning — planned as one interacting row, not three separate afterthoughts.
3. Why do excavation fleets underperform?
At the interfaces, not the machines — queues from matching errors, refused lifts from water failures, slow hauls from neglected roads; the interface review finds them before the week pays for them.
4. How does fleet planning change with project scale?
The arithmetic's shape holds from plot cut to quarry — the loops and interfaces are the same; only the numbers move, so the small fleet's method scales when the review cadence scales with it.
5. How important is water supply to the fleet?
Quietly decisive — dry lifts refuse compaction, dusty roads slow hauls, and both bills arrive as fuel the matched pair burns unproductively.
6. How many tippers per excavator?
The timed loops decide: haul cycle divided by loading time per truck, with the face's diggability and the road's condition inside both numbers — never a rule of thumb.
7. When should the fleet plan be refreshed?
Per material change, per haul-road condition change, and on the weekly interface review — the plan is a living arithmetic, not a mobilisation document.
8. Who plans the whole fleet conversation?
The SDLG desk at +254 718 686 967 — project scale, production target and site details in, matched fleet and support rows out.
Plan your excavation fleet with the SDLG desk
Send your project scale, production target and site details — we return the matched fleet plan and written quotation within 24 hours.
Disclaimer: Fleet arithmetic on this page is a planning method — cycle times, haul times and support rates are site measurements awaiting the project's real data. Machine figures live on each model's protected page. Figures verified 2026-11-03.
SDLG Excavator Fleet Planning: Matching Excavators, Tippers and Support Machines
Watch — 67 seconds: the complete SDLG range in Kenya
The excavator family this fleet guide serves — every SDLG machine in one film from the Ruai yard.
Video not playing? Download it or watch on YouTube — and for a machine of your own, call +254 718 686 967.
A fleet is not a collection of machines; it is a conversation between them — the excavator speaks in cycles, the tippers answer in hauls, the dozer grumbles about the face, the roller waits on the water, and the whole site moves at the speed of the slowest sentence. This guide covers SDLG excavator fleet planning the way the conversation actually runs: matching excavators and tippers through the cycle-and-haul arithmetic, then staffing the support rows — dozing, compaction and water supply — so that every machine's production lands where the programme needs it, across every project scale.
Quick answers if you are planning now: the excavator tipper matching arithmetic sizes the truck fleet, the support rows keep the matched machines working, and the interactions between the rows decide whether the fleet hums or queues. The mining-face version sits in the E6505H mining fleet planning guide, the tipper sizing side in the tipper fleet sizing guide and the range context in the excavator sizes explained guide; the desk at +254 718 686 967 plans the whole conversation.
| The core arithmetic | Excavator cycle time and bucket capacity against truck capacity and truck haul time — the matched pair everything else serves |
| The support rows | Dozing, compaction and water supply — the machines that keep the matched pair productive, each waiting on the others in turn |
| The interaction rule | Fleets fail at the interfaces, not the machines — the queue, the dry lift, the ungraded face and the unwatered layer are interface failures wearing machine costumes |
| The scale rule | The arithmetic's shape holds from the single-excavator plot cut to the multi-face quarry — only the numbers move, so the method scales |
| Verification date | 2026-11-03 |
The matching arithmetic: excavators and tippers
The construction fleet planning Kenya conversation starts with two timed loops. The excavator's loop: bucket capacity and fill factor against the excavator cycle time — dig, swing, dump, return — measured on the face the site actually presents. The tipper's loop: payload against the round trip — load, truck haul time out and back, queue, dump, return. Matching the loops: the number of tippers equals the tipper cycle divided by the loading time per truck, so the excavator never waits and no tipper queues long. The rows that distort the match: the haul road's condition, which moves the haul time more than the distance suggests; the dump point's turnaround, often the cycle's forgotten quarter; and the face's diggability, which moves the loading time more than the bucket's nameplate admits. The arithmetic fits on one page; the honesty is in timing both loops on the actual site rather than the planned one.
The support rows: dozing, compaction and water supply
The support machines planning rows complete the fleet. The dozer keeps the face and the haul roads in shape — the machine whose absence queues every other machine it serves, and whose production is everyone else's production. The roller serves the specification — lift thickness, moisture and pass count working to the testing regime, its production pacing the lift schedule the programme demands. And the water supply — bowser or source and distribution — serves the dust, the moisture conditioning and the compaction's honest moisture window together: the water supply fleet row is the quiet multiplier, because dry lifts refuse compaction, dusty roads slow hauls, and both bills arrive as fuel the matched pair burns unproductively. The compaction and water supply rows interact deliberately: the layer cannot compact without the moisture, the moisture cannot hold without the water plan, and the water plan is sized by the area and lifts the roller must cover per shift. Plan them as one row and they cost little; plan them apart and they bill separately, permanently.
The interaction rule: interfaces, not machines
Fleets rarely fail at their machines; they fail at the interfaces between them. The queue at the loading point: a matching error, not a truck problem. The lift refused by the tester: a water row failure, not a roller failure. The haul that doubled: a dozer row neglected, not a tipper's fault. The idle excavator behind a late blast: a planning interface, not an equipment one. The discipline that catches interface failures is the fleet review: the loops and rows timed together, the queues measured, the refusals counted, and the slowest sentence in the conversation found before it writes the week's production. The SDLG excavator fleet Kenya programmes that run this review weekly move the interface before it becomes the bottleneck — because by the time the queue is visible from the gate, the week has already paid for it.
Fleet by project scale: the same method, different numbers
| Scale | The fleet conversation looks like | The planning emphasis |
|---|---|---|
| Small — plot cuts, foundations, single site | One excavator, one or two tippers, a compact roller and a water arrangement | Multi-tasking machines and flexible roles; the interfaces are few but still timed |
| Medium — road sections, estates, water pans | Excavator and tipper fleet matched, dozer on the roads, roller on the lifts, bowser on rotation | The matching arithmetic earns its keep; the support rows staffed deliberately |
| Large — quarries, dams, mining support | Multiple faces, matched fleets per face, dedicated support machines and water systems | The interface review becomes the management system; the per-face loops measured separately |
The fleet by project scale framing is deliberately structural: the small fleet's excavator and the quarry's face machine speak the same arithmetic at different volumes, and the SDLG excavator fleet planning method scales because the loops and interfaces are the same loops and interfaces — only the fleet's patience for queues changes.
Misuse patterns that unmake fleets
- The machine-first plan: excavators specified before the tippers — the arithmetic run backwards and the trucks inherited to fit.
- Support priced at zero: the dozer, water and compaction rows discovered at the first dry, ungraded, unwatered shift.
- The queue accepted: waiting treated as normal — the interface failure normalised into the programme.
- Loops timed on the plan, not the site: cycles and hauls from the tender's optimism — the actual site invoices the difference.
- Scale copying: the small fleet's habits copied to the large site — the interfaces multiplied, the review never added.
Five checks before the fleet plan is signed
- Both loops are timed: excavator cycles and tipper hauls measured on the actual site.
- The match is calculated: truck count from the timed loops, refreshed per material change.
- The support rows are staffed: dozer, compaction and water planned as one interacting row.
- The interfaces are reviewed: queues, refusals and waits measured weekly.
- The plan scales honestly: per-face loops and interfaces measured separately where the site multiplies.
Working the knowledge with the desk
Send the project scale, production target and site details to +254 718 686 967 and the desk plans the whole conversation — the matched excavator and tipper fleet, the dozer, compaction and water rows, and the review rhythm that keeps the interfaces ahead of the bottlenecks. The SDLG excavator fleet Kenya plan is quoted with the machines, so the fleet arrives speaking one arithmetic. And the contractors who plan the conversation — the loops, the support rows and the interfaces together — own sites where the machines never queue, the lifts never refuse, and the slowest sentence is the one the review found before the week paid for it.
Frequently asked questions
1. How do we match excavators and tippers?
Time both loops — the excavator's cycle and the tipper's haul — on the actual site; the truck count is the tipper cycle divided by the loading time per truck, refreshed per material change.
2. What support machines does an excavation fleet need?
The dozer for faces and haul roads, the roller for the compaction specification, and the water supply for dust and moisture conditioning — planned as one interacting row, not three separate afterthoughts.
3. Why do excavation fleets underperform?
At the interfaces, not the machines — queues from matching errors, refused lifts from water failures, slow hauls from neglected roads; the interface review finds them before the week pays for them.
4. How does fleet planning change with project scale?
The arithmetic's shape holds from plot cut to quarry — the loops and interfaces are the same; only the numbers move, so the small fleet's method scales when the review cadence scales with it.
5. How important is water supply to the fleet?
Quietly decisive — dry lifts refuse compaction, dusty roads slow hauls, and both bills arrive as fuel the matched pair burns unproductively.
6. How many tippers per excavator?
The timed loops decide: haul cycle divided by loading time per truck, with the face's diggability and the road's condition inside both numbers — never a rule of thumb.
7. When should the fleet plan be refreshed?
Per material change, per haul-road condition change, and on the weekly interface review — the plan is a living arithmetic, not a mobilisation document.
8. Who plans the whole fleet conversation?
The SDLG desk at +254 718 686 967 — project scale, production target and site details in, matched fleet and support rows out.
Plan your excavation fleet with the SDLG desk
Send your project scale, production target and site details — we return the matched fleet plan and written quotation within 24 hours.
Disclaimer: Fleet arithmetic on this page is a planning method — cycle times, haul times and support rates are site measurements awaiting the project's real data. Machine figures live on each model's protected page. Figures verified 2026-11-03.
