// Hardware Guide
How to Build a Duty Cycle Profile for Your Fleet
We wrote this because "what's your duty cycle" is the first question we ask on nearly every hardware conversation, and most fleets don't have a real answer written down anywhere. This is how we help build one.
Executive Summary
Nearly every major fleet decision — battery chemistry and voltage, electrification versus hybrid versus conventional, charging infrastructure sizing, predictive maintenance modeling — depends on the same underlying input: an accurate duty cycle profile. Most fleets don't have one written down anywhere; they have an informal, partial sense of how their vehicles and equipment are actually used, spread across several people's heads and a few disconnected reports. This guide walks through how to build a real duty cycle profile — what data to gather, how to structure it, and how to keep it current — so that it can actually support the purchasing and operational decisions that depend on it.
Why a Duty Cycle Profile Is a Prerequisite, Not a Nice-to-Have
A duty cycle profile is a structured description of how a vehicle or piece of equipment is actually operated: load, distance, schedule, environment, and usage pattern over time. It sounds like a basic thing to have on hand, and most fleet managers would say they know their operation well enough not to need it written down formally. In practice, the informal version usually breaks down under scrutiny — average route length is known, but the variance isn't; peak load is estimated, but not measured; charging or refueling windows are assumed to be consistent, but nobody has checked whether they actually are across different routes or seasons.
The reason this matters beyond a paperwork exercise: every one of the decisions this guide series covers — battery chemistry and voltage selection, electrification versus hybrid versus conventional, charging infrastructure sizing, demand charge management, predictive maintenance modeling — depends on an accurate duty cycle as an input. A decision made against an estimated or assumed duty cycle carries the risk of that estimate being wrong, and the cost of that error compounds because it's baked into a capital purchase or infrastructure investment that's expensive to unwind.
What a Duty Cycle Profile Actually Contains
Load Profile
The weight, volume, or power draw the vehicle or equipment carries or delivers over a typical operating cycle, including peak load and how often peak load actually occurs — not just the vehicle's rated capacity, but what it actually carries in practice. For equipment with variable power demands (refrigeration units, power takeoff equipment, lift mechanisms), the load profile should capture continuous baseline demand separately from peak demand spikes.
Distance and Route Profile
Typical daily distance, route variability (fixed route versus variable dispatch), terrain and elevation change, and how consistent the route pattern is week to week and season to season. A route that looks consistent on a monthly average can have meaningful day-to-day variance that matters for range and charging planning — capture the variance, not just the average.
Schedule and Utilization Pattern
Hours of operation, shift structure, idle time between uses, and how predictable the schedule is day to day. This is the input that determines available charging or refueling windows, and it's often less consistent in practice than assumed — worth actually measuring rather than relying on the nominal shift schedule, since real-world schedule adherence often diverges from the plan.
Environmental Conditions
Climate (temperature extremes affect battery performance and range), terrain (grade affects load and energy consumption), and operating environment (dust, moisture, temperature extremes affecting equipment wear) all factor into duty cycle and should be captured per route or per site rather than assumed uniform across a fleet operating in multiple locations.
Charging or Refueling Access
Where and when the vehicle or equipment can actually be charged or refueled — not just the nominal plan, but the actual available windows given real schedule adherence, facility access, and any competition for shared charging or refueling infrastructure among multiple vehicles.
Failure and Maintenance History
For fleets with existing equipment, historical maintenance records and failure patterns are part of the duty cycle profile — they're the record of how the current equipment has actually responded to the duty cycle being described, and they're the training data predictive maintenance models need to work from.
How to Gather This Data
Telematics and Existing Data Sources
If the fleet already has basic telematics, much of the route, distance, and utilization data may already exist — the gap is usually in aggregating it into a structured profile rather than leaving it scattered across individual vehicle reports. This is often the fastest and cheapest data source to start with, since it requires organizing existing data rather than collecting new data.
Direct Measurement Where Data Doesn't Exist Yet
For fleets without telematics, or for data points telematics doesn't capture (load weight, for instance, often isn't tracked by standard telematics), direct measurement over a representative period — a few weeks to a few months, depending on how much seasonal or cyclical variation the operation has — is worth the investment before making a major purchasing decision. A short, deliberate measurement period produces a far more reliable duty cycle profile than an estimate based on institutional memory.
Interviews With the People Who Actually Run the Routes
Drivers, operators, and dispatchers often know real-world duty cycle patterns — actual idle time, informal route deviations, schedule adherence in practice — that don't show up in any system. Structured interviews as part of the data-gathering process catch discrepancies between the documented plan and actual practice that pure data collection can miss.
Accounting for Seasonal and Cyclical Variation
A duty cycle profile built entirely from summer data will miss cold-weather effects on battery range and equipment wear; a profile built from a slow season will miss peak-season load and schedule pressure. Where the operation has meaningful seasonal variation, the profile should either span a full cycle or explicitly note which conditions it reflects and where it's likely to understate demand.
Structuring the Profile So It's Actually Usable
Segment by Route or Application, Not Just Fleet-Wide Averages
A single fleet-wide duty cycle average obscures the variation that actually matters for decisions like electrification segmentation or battery specification. Structure the profile by route type or application category, so a decision about one segment of the fleet can be made against that segment's actual duty cycle rather than a blended average that doesn't represent any specific vehicle well.
Capture Ranges, Not Just Averages
For every key metric — load, distance, schedule — record the typical range and the outlier cases, not just the average. The outliers are often what determines whether a piece of equipment or a charging infrastructure plan is actually adequate, since a system sized for the average will underperform whenever the operation hits the upper end of its actual range.
Make It a Living Document
A duty cycle profile built once and never revisited becomes stale as routes change, load patterns shift, and the fleet grows or changes composition. Build a periodic review into the operation — annually is reasonable for most fleets, more frequently for operations with rapidly changing route networks or customer demand — rather than treating the initial profile as a one-time exercise.
What a Good Duty Cycle Profile Enables
Once a real duty cycle profile exists, it becomes the shared input for every downstream decision: which routes are candidates for electrification and which should stay conventional or hybrid for now, what battery chemistry and voltage actually fit each segment, how to size and schedule charging infrastructure, and what a predictive maintenance model should be trained against. Decisions made against this kind of real, segmented, current duty cycle data are decisions a fleet manager can defend with evidence rather than justify after the fact — and they're decisions far less likely to need an expensive correction once the equipment is in the field and the assumptions get tested against reality.
Bring us your duty cycle — or let's build one together.
Every equipment, battery, and charging recommendation we make starts from your actual duty cycle, not a generic spec sheet.