Maximizing ROI of your investment in an RFID System

Most plants can point to the waste behind an RFID business case: people searching for tools, replacement purchases for items that later turn up, material waiting somewhere on site, or inventory held because nobody completely trusts the count.

The hard part is proving what those problems cost. Most of them are absorbed into other accounts, so before an RFID project can show a return, somebody has to establish a baseline the finance team will accept.

The costs you are already paying

Few RFID business cases depend on new revenue. Most rest on money the operation already spends without recording it as a cost, which is why these numbers stay invisible until someone goes looking for them.

The largest is usually time spent searching. In a plant of any size, a proportion of every shift is absorbed by people looking for equipment, fixtures or material that is definitely on site somewhere. None of it is logged, because nobody fills in a form to say they spent twenty minutes finding a torque wrench, and so a cost that runs into serious money across a year appears nowhere in the accounts.

Close behind it sits replacement purchasing. Items get bought again because nobody can find them, and some of them later turn up. The purchase order is recorded faithfully; the reason for it is not. The same is true of production waiting on material that is on site but unlocated, which is typically booked as a production variance rather than as a location failure, and so never reaches the RFID conversation.

Then there is inventory itself. Safety stock is partly a hedge against a number the business does not trust, and when the number becomes reliable the hedge can come down. That one is worth isolating in the case, because it releases working capital rather than reducing expense, and finance treats the two quite differently.

For regulated manufacturers there is a fifth line that often turns out to be the largest. Assembling evidence for an audit is real labor, performed by expensive people under time pressure, and an automatic read history reduces it substantially. We cover that in more detail in RFID for supply chain quality management.

Why the baseline decides everything

None of those costs is measured today, which makes them worth attacking and also makes the case hard to write. You cannot claim a saving against a figure that does not exist.

So the most valuable thing you can do, before any hardware is specified or quoted, is establish what the operation looks like today. This does not need to be elaborate. Pick three or four quantities you can measure the same way afterwards and record them properly.

Two things separate a baseline that holds from one that does not. The first is that it is measured rather than estimated, because an estimate is the first thing a reviewer will challenge and the discussion tends to end there. The second is that the method is agreed in advance with whoever will eventually review the result. That conversation is awkward at the start of a project and much harder at the end of one.

A proper baseline gives the approval case a number to work from and gives the eventual review something to measure against.

What it costs

In FactorySense projects where RFID has been a good fit and the baseline was measurable, we have seen the investment returned in periods ranging from a few months to roughly a year. That is our project experience, and another site should not treat it as a benchmark. The starting condition matters more than the technology. The costs come from four components.

1. Tags. Passive tags printed on standard label media are the lowest-cost item per unit, while rugged hard tags cost considerably more each.
2. Reader equipment. These are the fixed readers and antennas installed at dock doors and at the transition points the process needs to observe. The number of read points largely sets this line, because each one adds a location the system can see.
3. Installation and consulting labor. This varies with the facility, the RF environment and the number of read points, and it is a meaningful share of the total alongside the hardware.
4. Software. FactorySense is licensed annually, and the cost depends on the edition and the scope of the deployment.

Integration sits inside that third line and is the part most likely to move, because connecting reads to your company's ERP or MES means mapping read events onto business rules, which is bespoke work in every deployment.

Timing needs the same attention as totals, because the savings arrive at different points. Reduced search time and fewer replacement purchases show up almost immediately, within the first weeks of people trusting the system. Inventory reduction takes longer, since it waits until people trust the number. Compliance savings appear at the next audit, which may be months away. A case presented on first-quarter returns alone will understate what the investment does.

Decisions that move the number

Once the baseline exists, a few choices reliably change the outcome.

Starting where confidence is lowest is the most useful of them. The area your team already distrusts has the worst baseline, which means it also has the largest improvement available and the clearest before-and-after. Ask people which parts of the plant they do not believe the numbers for and they will tell you immediately.

The tagging level is next. Tagging at carrier, pallet or kit level rather than individual item level frequently answers the same operational question for a fraction of the tag spend, and the right level is usually larger than teams first assume.

Beyond that, the return depends on reads becoming transactions in the system of record, since a read that only updates a dashboard does not show up in the numbers. Existing barcode, BLE or GPS deployments can usually stay in place alongside RFID, which removes a cost line from the case entirely.

Where to start

We begin engagements with a facility visibility assessment before any proposal, for the reasons above. The baseline is the part that makes the eventual number defensible, it is specific to your operation, and it cannot be gathered remotely or inferred from someone else's deployment.

Book a Facility Visibility Assessment and we will measure it with your team, so the case you take to approval is built on your own numbers.