Start with the decision, not the technology
A logistics lead is in a meeting whose first slide names a location system, while Station 4 is still idle because a kit is somewhere in the north buffer. The pain is already on the floor. The name of the technology is not the first question.
Name the pain before you name a system
The question that has to come first is what is breaking this week, for whom, and where. A supervisor who can say the drivers are hunting the north buffer while the line waits has a decision. A team that can only say it needs visibility does not. Write that sentence in floor language before anyone opens a brochure. RTLS and every other location product are answers. They stay useless until the question is one loss the shift already pays.
The same hall often holds several pains at once. Extra forklifts, late kits, long searches, hard walking routes, and a corner that keeps producing near misses are different losses. They do not share one fix, and they do not share one price. Pick the one the plant will actually enforce this quarter. The others can wait their turn.
Questions to answer on the floor
Use these in the meeting. Each one needs a place on site and a person who feels it. If nobody can point at the dock, the aisle, or the station, it is not ready to buy against.
1. What is my pain point? - Say it in one sentence a supervisor would use on the shift. Who is stuck, where, and what fails when they are stuck. "We cannot see the hall" is not a pain. "The last pallet of that SKU is not where the WMS says, and the driver has already left the dock" is a pain.
2. Do we have too many forklifts? - Count trucks against moves that truly need a truck. Empty returns, two drivers sent to the same cage, and a fleet that grew because search ate the shift are a fleet problem. The loss is driver time and vehicles you would not replace. A spaghetti diagram of one real shift usually shows those loops before any system diagram does. The same drain is described under the empty-round problem that still sits in most plants.
3. Are we missing deadlines? - Internal windows slip before customer windows do. A kit that misses takt at Station 4 becomes overtime, a reshuffled sequence, or a ship date that moves. Ask which deadline, which station, and how often in a normal week. A complaint without a clock is not yet a project.
4. Are people searching too long, and is the line idle when a delivery is missed? - Search and idle time travel together, and they are not the same number. Search is the walker or the driver who cannot find the cage. Idle time is the crew at the station who cannot start. A late material call-off that leaves WIP in the wrong buffer creates both. Dwell in the wrong place is often why the search starts.
5. Is the walking and the workload unfair? - Ergonomics here means who walks the long aisle, who lifts, and who carries the heavy route while another team stays at the dock. The pain is fatigue, strain, and the overtime that covers the person who cannot keep the pace. Overall labor effectiveness is one way plants already talk about that uneven load. Count hours on the hard route before you talk about a map.
6. Is safety the thing we keep explaining after the fact? - Near misses at a shared crossing, a person in a truck path, a stop inside a marked box. Ask how often it happens and who finds out too late. A no-go zone or a geofence is only a rule once the plant can say which corner and how many times a week. A rare corner and a daily corner are different decisions.
Count what each pain costs
Every pain you keep has to become a loss the plant can defend. Not a vendor percentage. A week of your own clock, then money the finance lead already uses. If you cannot finish the sum, you are not ready to compare technologies. Internal logistics optimization only pays when that sum is a fleet, a search, or an empty trip you have already priced.
Forklifts. Trucks you could park, times the driver cost of a shift, times the shifts in a week. Add the vehicle cost you already pay whether the truck hauls or hunts. Three crews spending the morning on empty loops is three crews. It is not a vague fleet problem.
Deadlines. Idle minutes at the station, times the people waiting, times the labor rate used for downtime. Add overtime or the expedite that follows a slipped ship window. That idle stretch is also what production already books against OEE when the station cannot run. A missed deadline that lives only in an email has no budget. The same miss written in hours does.
Search and missed deliveries. Searches per shift, times minutes, times the people looking, times their wage. Then, separately, minutes the line stands when the cage is late. Do not fold those into one blob. Walking and waiting are both real, and double-counting the same event makes the later comparison dishonest. Throughput lost on that station is the number production will recognize. Finding the cage is asset tracking only after you know which of those two clocks you are trying to stop.
Ergonomics and workload. Extra hours on the long route for a week, plus overtime and any recorded strain that already pulled someone off the job. That is the figure an ergonomics conversation needs. A picture of steps without hours is still only a picture.
Safety. Events in a month, times the stop, the investigation, and the reroute that followed. Do not invent a cost for harm you have not priced. Do record how often the corner fails. Frequency is what tells you whether the rule is worth enforcing.
Small numbers should stay small. If the week does not hurt, do not buy a system to decorate it. Large numbers become the only pains allowed to set the project. Later return on investment is this loss compared with what you spend to cut it. Without the loss, that comparison is a guess. Whether a live pin is even the right spend for the number you just wrote is the filter in when RTLS helps, and when it does not.
A week that makes the number obvious
On a Thursday in a white-goods hall, the tugger leaves the supermarket for a cage the WMS still shows in the north buffer. The driver radios that the cage is on the way. Station 4 has already burned ten minutes, which is a production monitoring problem before it is a warehouse story. A second driver is sent because the first one is walking aisles. Both trucks are busy. Neither move was the move the plan needed. By the end of the shift the fleet looks fully used, the line has a hole in the sequence, and the person who walked the long aisle is the one staying late.
That week is calculable without a new system. Dispatcher logs, a sample of calls, the idle codes on the line, and a count of empty returns will get you close. Plants that later followed their fleets usually did it because those loops were already on the overtime sheet. Write the sheet first.
Only then look at technology that fits the hall
When the pain and the weekly loss are written down, the next question is which technology fits this building, not which one has the finest brochure. Indoors under steel is a different place from an open yard. Finding a forklift is a different job from proving a person stepped into a marked box, or from knowing a cage passed a dock door. The environment, the thing you must find, and how fast the decision expires all constrain the later shortlist.
That shortlist is RTLS technologies out there. What the system means in plant language sits under what is RTLS. Read those after the exercise. Do not start there. A technology that answers a question you have not costed will be sized to the demo, then blamed when the shift does not change.
How the team runs the exercise
1. Pick one pain - One sentence, one place, one role. If the room names five pains, park four.
2. Count a normal week - Use clocks you already trust: idle codes, radio calls, overtime, empty returns, near-miss notes. Skip the best day and the worst day if they are not the week you staff for.
3. Write the loss in hours and in money - The figure finance will recognize. Separate search from line idle. Separate extra trucks from extra walking.
4. Then open the technology list - Keep only what can see the thing you counted, in the hall you have. If the loss is a late call-off with no location mystery, a location system is the wrong buy. If the loss is a hunt, the hunt decides how sure the answer must be.
twinzo comes in after that sheet exists. The job is the live hall view where the loss you counted can sit next to trucks, cages, and stations people already know, on a digital twin logistics and production will open during the shift. Capability detail is on the features overview. The decision to lock first is the pain and its cost.
Get in touch if you want to walk the same questions on your own facility model.