How to Collect Electric Forklift Power Study Data Without Guessing

Imagine the charger aisle at 6:40 on a Tuesday morning: a clipboard in hand, and the clipboard is losing. Truck 14 has come back to the dock dead an hour into second shift. The dispatcher wants to know whether the fix is another battery or another charger, and the only number anyone can produce is the nameplate rating on the pack that just quit.

The method that answers him comes from the cited Toyota power-study example, documented at model scope, so what you get out of it depends on your measured duty cycle and your exact battery and charger system. It replaces nameplate arithmetic with amp hours and run time logged on your heaviest-used trucks across a two-to-four-week window. A shift runs out of power at its peak truck, not at the fleet average, and the study is built around that fact.

What a Power Study Actually Records

A power study records four streams on each instrumented truck: run time, idle hours, available charge hours, and the amp hours drawn each day. Data is generally collected for two to four weeks, on the trucks that carry the heaviest use.

Run time is loaded working time, the hours the truck is moving pallets, and it is the part of a shift that actually costs energy. Idle hours are the opposite kind of hour: the truck is switched on, the operator is on the clock, and the battery is barely working, which is why a truck can finish a long shift with charge still in it. Available charge hours describe the window in which energy can go back into the battery, meaning the gap between shifts, the break at changeover, the overnight stretch your building actually gives you rather than the one in a planning document. Amp hours used each day is the number everything else hangs on: measured energy out, per truck, per day.

Three of those fields describe time. One describes energy. Keep the distinction, because hours on the clock and energy out of the battery do not move together, and a shift plan that treats them as the same thing will be wrong in whichever direction your operation leans.

Why Amp Hours Decide the Shift, Not the Spec Sheet

A battery holds a fixed quantity of energy, and the work a shift asks of it varies truck to truck. The reason a fleet average misleads is operational, not statistical: a shift does not end when the average truck runs low, it ends when the truck doing the heaviest work goes dead, and everything queued behind it stops with it. Which means the binding constraint on your shift plan is peak amp-hour draw, not mean draw.

So the collection targets the heaviest-used trucks instead of a representative sample, and the answer comes down to one comparison per truck: amp hours consumed each day against the amp hours that can be returned inside the available charge hours. Get that comparison right on your worst truck and you have sized the real problem. Get it right on the fleet average and you have described a warehouse that isn't yours.

I'll take a side here. Trust the meter log before the spec sheet. Nameplate capacity divided by hourly draw is a wish, because it assumes a constant load on a battery whose real load nobody has measured. The exception is narrow but worth naming: if your duty cycle barely moves across the year and every truck carries roughly the same work, nameplate arithmetic will land close enough that the study mainly confirms what you already knew. Most warehouses are not that warehouse.

The stated payoff of the exercise is an appropriately sized battery and charger for your application, and "the application" is a measured amp-hour profile, not a brochure.

The Order of Steps, From Truck Choice to Shift Plan

The sequence matters, because each step depends on the one before it. Choose the trucks first: the ones dispatchers already know run out of charge under real work. Instrument those and run the collection for the full window, capturing the four fields daily per truck.

Reconcile before you count anything. Daily amp hours consumed against available charge hours, truck by truck, for every day in the window. This is the step people skip when they are in a hurry and already have a number in mind.

Then convert. The reconciliation produces the battery count and charger count the application needs. Sizing is an output of the study, never an input to it.

Last, keep the record. Amp hours together with run-time hours forecast battery life expectancy, which is how a replacement year goes into the capital plan instead of arriving as a surprise, and the same numbers give you a read on performance and longevity while there is still time to plan a replacement.

Key Points That Make Each Step Hold Up

Instrument the trucks that actually run out of charge. A study of the comfortable trucks returns a comfortable, useless answer.

Suppose a warehouse runs three reach trucks and only one of them works a dock ramp across both shifts. Average all three and the ramp truck disappears into the middle of the data. Study its amp hours alone and you find out what your second shift genuinely costs, which is the number your dispatcher has been guessing at since the truck died.

Make the window cover at least one full operating cycle so a peak day falls inside the sample rather than just outside it. Two weeks that miss month-end are two weeks of the wrong warehouse.

Hold the battery and charger pairing constant on each truck for the whole window. A mid-window pack swap quietly rewrites the data, because you can no longer tell whether day nine looks different because the work changed or because the battery did, which means the record stops being usable as an amp-hour baseline.

Log idle separately even when it feels like noise. Idle inflates run time without a proportional draw, so a truck that looks busy can be quietly under-loaded, and folding idle into run time drifts every ratio downstream of it.

Confirming the Data Is Good Enough to Buy On

Run four checks before anyone signs a battery or charger order.

Does each truck's daily amp-hour draw reconcile against its available charge hours? If consumption outruns what the charging window can return, you have a charging-window problem, and extra batteries buy runtime you still have no window to refill.

Does the run-time and idle split match what dispatchers see on the floor? A truck logged as working through a shift that the floor knows spent much of it parked at a dock door is a sensor placement question, not a planning input. Does the same truck repeat its pattern week over week? Consistency is the cheapest evidence that you captured normal operation instead of a strange Tuesday. And does the recommendation trace back to measured amp hours? If it doesn't, something got assumed somewhere between the log and the quote.

Keep the boundary in view while you check. This is one manufacturer's methodology at model scope, and its outcomes depend on the measured duty cycle and the specific battery and charger system in front of you. The steps travel; the numbers don't.

From Data to Battery Count and Replacement Year

Reconciliation turns into counts. Measured amp hours per day set against available charge hours tells you how many batteries a truck needs to get through a shift cycle, and how many chargers that implies, which is the guesswork the method claims to remove.

Replacement timing comes from the same record. Amp hours plus run-time hours forecast life expectancy, and a battery's performance and longevity trend is what lets you schedule a replacement instead of reacting to one. A truck whose amp-hour draw climbs while its run time holds steady is saying something about the pack, and the only reason you can hear it is that you have a baseline to read it against.

That is the argument for keeping the series after the study closes. The report ages; the series keeps earning.

What Power-Study Data Won't Settle for You

Some decisions sit outside what these four fields can settle, and pretending otherwise is how studies get blamed for plans they never supported. The numbers describe the trucks and the window you measured. Change the layout, add a mezzanine, shift the product mix, and the duty cycle moves with it, which means the study is a snapshot you re-run rather than a specification you file.

Labor scheduling and operator assignment live outside the method. Amp hours tell you what the work costs in energy; they don't tell you who drives what or how you stagger the breaks. Charger electrical supply at the charging location needs the people who own that building, and that conversation is a procurement question with a named owner, not an inference from a run-time log.

The tradeoff you accept with a short window is that a measurement period missing your peak week costs you exactly the shift you were trying to plan for. That is the one failure mode worth spending planning effort to avoid.

So is two to four weeks on a handful of trucks really enough to schedule every shift? Enough is not measured in weeks. It is measured by whether your worst week sits inside the window: if it does, that handful of trucks is the right handful and you can schedule from it. If your duty cycle swings seasonally, don't stretch one window across the whole year. Run the study on the peak season, while the trucks are actually failing, and plan the quiet months from that record.