Maximizing ROI of your investment in an RFID System

The difficult part of an RFID business case is usually not identifying the waste. Most plants can point to it: 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 difficult 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

An RFID business case is rarely built on new revenue. It is built on money the operation is already spending without recording it as a cost, which is why these numbers are 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 they cannot be found rather than because they are gone. 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 therefore never reaches the RFID conversation at all even though it belongs there.

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 most significant of all. 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

Each of those costs shares a characteristic: it is currently unmeasured. That is what makes them worth attacking, and it is also why the case is 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 mildly uncomfortable at the start of a project, but considerably worse at the end of one.

Done properly, the baseline does two jobs at once. It gives the approval case a number to work from, and it 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, not a benchmark to apply blindly to another site. The starting condition matters more than the technology does. The costs themselves come from four components.

1. RFID tags themselves. For passive RFID tags, costs are typically in the pennies for printable tags, but can range up to a few dollars for "hard tags".
2. RFID sensor equipment. These are the fixed readers that are installed at dock doors and key transition points within your facility. These are typically sold as kits and cost a few thousand dollars per kit. Think of each sensor point as a pixel on a television; the more sensors, the higher resolution of a picture your system will be able to provide you of your operations.
3. Installation and consulting labor. This typically varies, but a rough rule of thumb is that the labor required to install an RFID system is 50% of the cost of the hardware.
4. Software costs. Depending on the edition of FactorySense you need, costs start as low as a few thousand dollars per year.

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.

It is worth setting expectations on timing as well as totals, because the savings do not all arrive together. 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 follows confidence in the number rather than the number itself. 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, what matters is whether reads become transactions. A read that updates a dashboard changes what somebody looks at; a read that updates the system of record changes what the business does, and only the second kind shows up in the numbers. And existing barcode, BLE or GPS deployments can usually coexist with RFID rather than being ripped out, which removes a cost line from the case entirely.

Where to start

We begin engagements with a facility visibility assessment rather than a proposal, and the reason is precisely the argument 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.