Traceable Quality
Talk to us
Menu

Free tool

RFID pilot planner

One read point, four weeks, and pass marks you write down before the first read. Put in your traffic and it works out how many misses you can afford, then prints the plan on one page.

Where

One door or one station. Not the whole plant.

Carton, crate, bin, job card. Whatever passes the read point.

Model and price of the one you would buy in volume. Paper labels run ₹5 to ₹8, on-metal about ₹60.

Fills in the dates on the plan.

Traffic
items
days
items

The load only counts as read if every item on it reads.

Pass marks
%

99.9% a tag gives 95% of 50-case pallets complete. 99% gives about 60%.

%
events

Raw stray reads get logged. This is how many may get through the rules.

s an item
Who

30-day RFID pilot

Dispatch door 1

Read point
Dispatch door 1
Tagged
Shipper carton
Tag
Paper UHF label, ₹6, the one you would buy in volume
Dates
Four weeks from the start date
Owner
 
Hand count
 

Pass marks

MeasurePass markWhat it takes
Read rate per tag99.90% or betterAt most 1 missed in about 4,800 passes over weeks 2 and 3.
Loads read complete95% or betterAbout 96 loads of 50. At 99.9% a tag, expect 95.1% complete.
Stray reads that become events0Every raw stray read is logged with its time and the door it really used.
Tagging time5 s an item or lessTimed in week 1, by the people who'll do it.
TrafficNo changeSame forklifts, same speed, same route.

Week 1: tag and baseline

  • Fix the one read point. Everything else in the plant stays as it is.
  • Buy the tag you would buy in volume, from the supplier you would use. No vendor samples.
  • Tag real stock on the real line, at the position the tag will have in production, by the people who will do it.
  • Time the tagging. Seconds per item, per person.
  • Count by hand what passes the read point, every shift, against the ERP. That count is the baseline.
  • Write the pass marks below on this sheet and sign it before any reads come in.

Weeks 2 and 3: run it beside what you have

  • Switch nothing off. The manual count and the ERP carry on as before.
  • Every pass: what the reader saw, what the count says, what the ERP says.
  • Log every disagreement: which item, which load, which shift, where the tag sat, what was next to it.
  • Log every read of a tag that did not go through this point. Those are stray reads.
  • Same forklifts, same speed, same drivers. If the reader needs them to slow down, that is a finding.
  • Change nothing mid-run. If something has to change, note the time and start the count again.

Week 4: the sums

  • Read rate per tag: tags read over tags that passed.
  • Loads read complete: loads with every item read over all loads.
  • Stray reads, and how many of them became an event the ERP saw.
  • Where the misses cluster: middle of the load, against metal, under a tine, one shift.
  • Compare each number with the pass mark written in week 1. Not with what the vendor said.

If a mark is missed

Change one thing, then run weeks 2 and 3 again. Two changes at once and you won't know which one worked.

The log showsChange
Misses cluster in the middle of the loadTag position or a tag with more sensitivity. Then antenna angle.
Misses on items against metal or liquidAn on-metal tag (about ₹60) for those items, or move the tag.
Misses on one shiftHow the load is built or driven on that shift. Not the radio.
Stray reads becoming eventsThe rule that turns reads into events: a second antenna for direction and a beam break at the door.
Tagging is too slowPre-printed and encoded labels at the supplier, or a printer-encoder at the line.

Pass marks agreed before week 1.

Signed

Date

Made with the RFID pilot planner, iotready.com/tools/rfid-pilot-planner

One read point. Week 1: tag real stock and count by hand. Weeks 2 and 3: run beside what you have and log every miss. Week 4: read rate per tag, pallets complete, stray reads. Then pass, or change one thing.

What it works out

How many misses you can afford. Weeks 2 and 3 are when you count. Items a day times twelve working days is how many tags pass the reader. The planner then finds the most misses that still show your per-tag mark with 95% confidence. At 400 items a day and 99.9%, that’s 4,800 passes and at most one miss.

Four misses in 4,800 is 99.92%. It looks like a pass. But a tag that really reads 99.85% turns in four misses or fewer about one time in six, so four misses doesn’t show 99.9%. The planner won’t let the plain rate pass you on luck.

Whether the pilot is big enough. To show 99.9% with nothing missed you need about 3,000 passes. A read point that sees 100 items a day won’t get there in two weeks, and the planner says so.

Whether your marks agree. A load only counts as read if every item on it reads, so the per-load mark sets the per-tag one. 99% a tag on a 50-case pallet is about 60% of pallets complete. For 95% you need 99.9% a tag. If you set marks that can’t both be true, it tells you.

What it assumes

Misses are independent from one tag to the next. They aren’t, quite. Misses cluster in the middle of a shrink-wrapped pallet, against metal, under a forklift tine. That’s why the log asks where the tag sat, and why a clustered miss is a reason to move the tag before it’s a reason to buy a better reader.

The confidence sums use the Poisson approximation to the binomial, which is close when misses are rare. The pass mark is one-sided: it asks whether the rate is at least what you wrote down, not what the rate is.

The tag prices in the hints are part 14’s: paper UHF labels at ₹5 to ₹8 in volume, on-metal about ₹60. Your supplier’s quote beats both.

Before you start

Pick the read point you’ll learn the most from, not the easiest one. A dispatch door with mixed pallets tells you more than a station with one item on a conveyor. The 30-day pilot, week by week has the reasons behind each step. The range calculator shows why your floor will read shorter than the spec sheet.