Asset utilization sounds simple on paper: get more productive time out of the equipment you already paid for, shorten idle periods, and make sure the right tool is in the right place at the right moment. In practice, it takes discipline, clean data, and a fair amount of coordination across teams. That is exactly where real time location services, often abbreviated as RTLS, change the game. A real time location system helps you answer practical questions instantly: Where is the nearest available infusion pump? Which pallet jacks are unused for more than four hours per shift? How long does a high value mold sit between changeovers? Once those questions move from guesswork to facts, utilization improves as a side effect.
I have watched operations leaders in hospitals, factories, and distribution centers adopt RTLS in different ways, some modest and some sweeping. The wins tend to cluster in the same places. Staff stop hunting for scarce equipment. Preventive maintenance gets done on time because planners know actual run hours instead of estimates. Procurement stops ordering duplicates to cover for things that are unavailable in name only. The path to those wins is nuanced though, and worth mapping carefully.
Where utilization hides and how RTLS uncovers it
Any asset that moves or gets handed off frequently creates blind spots. Hospitals misplace wheelchairs on busy floors. Construction sites scatter generators and light towers across changing laydowns. Manufacturers stage die sets and specialty tools near lines and then forget them when priorities shift. Each blind spot hides utilization. If no one can find the item, it appears unavailable, so supervisors request more. If the item returns to storage but not to its assigned slot, it looks checked in but out of reach, so it goes unused even when it could cover a shift.
An RTLS network reduces those blind spots by attaching a unique identity to each asset and reporting its location as it moves. Most systems pair a small tag with fixed infrastructure like gateways, anchors, or readers, and then feed data into software that handles maps, events, and reports. The precision depends on the underlying radio and the density of installed hardware. With the right settings, you can see room level presence or sub meter accuracy on a production floor.
Once data starts flowing, patterns appear. A Midwest hospital I worked with thought it had a shortage of smart pumps. After instrumenting 1,800 pumps with Bluetooth Low Energy tags and placing readers on every other med floor, the team learned that 28 percent of the fleet sat idle during day shifts, and idleness spiked above 40 percent overnight. The pumps were not missing. They clustered in a few hallways and supply rooms after discharge pushes. Transport and biomed formed a new rounding routine, guided by the RTLS map and an alert for idle pumps past two hours. Within two weeks, rental spend fell to near zero, average search time dropped from 20 minutes to 4, and nursing satisfaction went up. The useful detail is not just that they could find a pump, but that they could spot idle clusters and create a workflow to move them.
In a high mix machine shop, the constraint often hides in setup time. One facility tagged 200 precision fixtures and used ultra wideband anchors to get fine grain visibility within cells. The plant manager discovered a recurring half hour gap between fixture return and the next job start. The fixtures were back in the area, but not at the shadow boards the operators relied on. A small change fixed it: a staging zone was defined in the RTLS map, with a short alert if a fixture stayed in staging more than ten minutes. The half hour gap shrank to 8 minutes on average. Across three shifts, that recovered almost 11 hours of spindle time per week without adding a single fixture.
These gains come from clarity, not magic. A real time location system turns subjective reports into measurable states: idle, in use, out for maintenance, or offsite. That clarity enables scheduling, right sizing, and faster turns.
The technology choices that shape accuracy and cost
An rtls provider will typically offer a playbook with several radio options. There is no single best choice. The right pick hinges on how precise you need to be, how often assets move, how many tags you can maintain, and what your buildings allow for in terms of power and network drops. It helps to think in terms of math: required accuracy, update rate, and density drive the number of anchors or readers, which sets both upfront and ongoing cost.
Here is a practical comparison from the field, with the understanding that every brand tunes these differently.
- Bluetooth Low Energy tags with fixed readers: Room level to 3 meters in many environments, with battery life often 3 to 5 years. Good for hospitals, offices, and warehouses. Readers can piggyback on PoE. Cost per tag is low, density of readers moderate. Passive RFID with handheld or portal readers: Not continuous tracking, but excellent for chokepoints like dock doors or tool cribs. Near zero tag maintenance, pennies per tag, higher cost in staff time unless fully automated portals exist. Ultra wideband anchors and tags: Sub meter accuracy in dense, multipath environments such as factories. Battery life shorter due to higher update rates, often 1 to 2 years depending on duty cycle. Infrastructure density higher. Wi Fi RSSI or round trip time: Leverages existing access points but accuracy varies widely, from 3 to 10 meters without careful tuning. Good for coarse presence and movement trends, not for tool level control. GPS or GNSS plus cellular or LoRa backhaul: Best for outdoor yards, construction sites, or fleets. Excellent for geofencing and route analysis. Power draw requires larger batteries or vehicle power.
That is one list for this article. Note the blended cases: a distribution center might pair BLE for indoor pallet jacks with GPS trackers on yard tractors, and then unify the data in a single rtls management console. You can also combine fixed infrastructure with handheld workflows, such as passive RFID for quarterly inventory and BLE for day to day visibility.
The radio decision dictates anchor placement and cable runs. On a brownfield floor with limited IT support, battery powered anchors that mesh back to a gateway can accelerate deployment but raise maintenance overhead. In a greenfield hospital tower with strong PoE and VLAN discipline, hardwired readers simplify operations and cybersecurity reviews. Neither is always better. I have seen plants save 20 percent in install cost with battery anchors, then spend it back two years later on a changeout project.
Where utilization gains appear first
You do not need perfect fidelity to find the first 20 percent gain. The early wins usually come from three behaviors: time lost to search, hoarding, and over provisioning. Each shows up in RTLS data as a pattern.
- Search time: If nurses spend 15 minutes per shift looking for a portable ultrasound, and you have 80 nurses across day and night, that is 20 hours per day. A simple map view with nearby assets cuts that by more than half. You will see time to first location query drop to a few minutes or seconds, and that shows up on the first week of usage reports. Hoarding: When users fear scarcity, they stash gear. The map reveals long dwell times in unexpected rooms. Set an alert for a wheelchair staying in an exam room more than 90 minutes after a visit ends. Each retrieval prevents a misperception of shortage and a request for extra units. Over provisioning: If preventive maintenance teams cannot locate equipment, they may schedule slack time or buy spares. Once location and state tie into the CMMS, you can run maintenance based on actual use and shorten downtime windows. One plant reduced spare fixture purchases by 15 percent in a year by proving that existing sets could cycle reliably with better handoffs.
Those numbers translate quickly. Consider a 250 bed hospital with 400 infusion pumps. Reducing rentals by just 6 pumps per month at 500 to 800 dollars per rental saves 3,000 to 4,800 dollars monthly. Cutting 10 minutes of average search time per nurse per shift across 100 nurses recovers 16 hours per day, which you may not turn into payroll reduction, but you do convert into more patient time, fewer delays, and less overtime.
In manufacturing, asset utilization jumps show up as higher overall equipment effectiveness not from faster cycles, but from shorter changeovers, fewer waits for fixtures, and less time swapping tools. A line that runs two https://juliusdomi003.timeforchangecounselling.com/building-a-robust-rtls-network-architecture-and-design-tips changeovers per shift and loses 12 minutes each to locating torque wrenches and carts can claw back 8 percent of scheduled time without changing product mix. RTLS data proves where the minutes go, so supervisors can reset habits credibly.
Integrating RTLS with systems you already rely on
On its own, a map is useful. Combined with your maintenance and planning tools, it becomes a lever. The best outcomes I have seen come from lightweight integration between the RTLS network, your CMMS or EAM, and whatever scheduling tool owns work orders.
A common pattern in hospitals: connect the RTLS provider’s event stream to the CMMS so that equipment status flips to available when a nurse hits a ready for pickup button, or when the device returns to a clean storage area. The biomed team can work from a live queue rather than phone calls. The state change also kicks off an automated check for preventive maintenance based on run time or count of uses if your devices report that telemetry. The facilities team gains a complete chain: in use, soiled, cleaned, available, or out for service. Utilization improves because the equipment returns to circulation faster and in a predictable way.
In factories, connect RTLS beacons to work instruction systems or MES. When a required fixture enters a cell, you can start the setup clock. If the fixture stays in the wrong aisle, a nudge goes to the water spider or material handler. You do not need to redesign the whole plant system to try this. One shop floor I worked with used only a webhook from the RTLS management console to a Slack channel that the team already watched. Each arrival or over dwell pinged the right person. That alone lifted on time starts by 12 points in a quarter.
ERP tie ins help with asset capitalization and depreciation. If a high value item leaves the site or crosses a geofence, the finance team gets an alert for audit purposes. It is not glamorous, but it prevents ugly conversations later.
Measuring utilization properly, not just tracking dots
A real time location system tempts teams to stare at dots on a map. Resist that habit. The value comes from state and time, not eye candy. Before you deploy, define the states you will care about and how you will infer them. You can do this without excessive complexity.
- Define locations that matter: clean storage, dirty hold, service bay, staging zone, active cell, quarantine. Define transitions with thresholds: idle if stationary in a corridor for 90 minutes, out of rotation if in maintenance more than 48 hours, hoarded if an exam room holds a wheelchair more than two hours after last patient discharge. Align to maintenance logic: for devices that report usage, tie location states to usage counters. If not, use dwell in active areas as a proxy for run time.
Then track a handful of metrics that go straight to utilization. Percent idle by hour and by unit. Average search time from first query to asset in hand. Turnaround time through cleaning or maintenance loops. Dwell in staging before next job start. Work with the frontline to set targets that feel realistic. Expect to tune thresholds in the first month as you learn what normal looks like.
One factory realized that their initial idle threshold of 15 minutes for carts in an aisle triggered far too many alerts during breaks and shift changes. They moved it to 35 minutes and filtered alerts during scheduled breaks. Noise dropped, adherence stayed high.
Realistic costs, and how to judge ROI without hand waving
Executives who have been pitched RTLS before will ask about total cost of ownership and return. The inputs are knowable with some ranges. Tags for BLE often land between 20 and 40 dollars each, with batteries that last 3 to 5 years if you use 1 to 2 second advertisement intervals. Readers can cost 300 to 800 dollars, plus installation. Ultra wideband tags run higher, 40 to 80 dollars, with denser anchors at 500 to 1,500 dollars each. Software is usually a per tag per month fee, 0.50 to 3.00 dollars, or a site license for very large fleets. Add labor for deployment and ongoing rtls management, which can start part time and grow as you scale.
ROI math should link to concrete reductions: rentals avoided, spares not purchased, overtime trimmed, and faster turns that lift throughput. Here is a simple, conservative model from a 600,000 square foot distribution center:
- 350 mobile assets tagged, mostly pallet jacks and carts. 70 fixed readers across the building. Capital for tags and readers, installed: 60,000 to 90,000 dollars. Software and support: 12,000 to 18,000 dollars per year.
Gains measured after three months:
- 18 minutes less per shift per picker spent searching or waiting, averaging 9 minutes reclaimed when a cart is found quickly and 9 minutes due to equipment now being staged correctly. With 60 pickers across two shifts, that is 36 hours per day. If only one third of that translates into throughput or reduced overtime, you recoup about 12 labor hours per day. Spare carts planned for purchase were cut by 20 units at 600 dollars each, a 12,000 dollar avoided cost. Weekend overtime tapering by 6 hours per week due to fewer start delays, at 35 dollars per hour, a run rate of about 10,000 dollars per year.
Even with cautious assumptions, the first year covered the initial outlay.
Hospitals often see faster returns because rental avoidance is immediate. A 300 bed facility that reduces rentals by 10 pumps at 600 dollars per month breaks even on a modest BLE deployment within quarters, not years.
Security, privacy, and clinical risk
Anything that watches movement raises fair questions. A mature rtls provider will support network segmentation, certificate based device onboarding, and encryption between tags, anchors, and the server. You should involve IT security early. For hospitals, emphasize that the system tracks equipment, not patients, unless you explicitly deploy patient badges with informed consent and appropriate governance.
Privacy concerns also show up around staff. Some unions and frontline teams push back on badges that might be used for performance management. The best practice is clear policy with technical limits that align to it. If the goal is asset utilization, do not track staff badges at all. If you must, restrict retention and access to the minimum. Be explicit about how data will and will not be used.
Clinical risk has a different shape. Any add on tag should not interfere with device operation, cleaning, or sterilization. Work with biomed to pick tags and fasteners that withstand disinfection cycles. Validate that tags do not block vents or ports, and that adhesives will not damage housings. These tasks seem small until one model of ventilator comes back with residue that voids a warranty. I have seen programs pause for months over that kind of misstep.
Pitfalls that slow programs, and how to avoid them
Two problems reappear across sectors. The first is infrastructure surprise. Everyone assumes power and network are available in the right spots. Then you start the walkdown and discover that half the planned anchor positions need new conduit or that ceiling lifts require different permits. Do a physical survey with facilities and IT, tape out anchor spots, and budget 10 to 20 percent contingency for changes.
The second problem is workflow neglect. Finding assets is not the same as restoring flow. If transport or materials handling teams do not own retrieval end to end, RTLS will show you idle clusters with painful clarity, and nothing will move. Before you go live, agree on who watches which dashboards, who responds to alerts during which hours, and how you will measure responsiveness. The goal is fewer manual calls, not a new stream of ignored pop ups.
Battery management deserves its own mention. Tags that die quietly create false negatives and erode trust. Use staggered deployment so not all batteries expire in the same month. Turn on low battery alerts that route to someone who actually carries a stock of replacements. In a 2,000 tag estate, aim to replace 50 to 100 per month on a rolling basis. It feels like a chore at first, then settles into rhythm.
How to pick a partner that can grow with you
Many vendors can show you dots on a demo map. Fewer will walk your floors and adapt to your constraints. When evaluating an rtls provider, do not stop at technical specs. Look for signs that they support operational adoption. Here is a short readiness checklist that has paid off for teams I support.
- Ask for references from customers with your footprint and environment, not just your industry. Request a pilot that covers at least one full workflow loop, such as clean to dirty to clean for hospital equipment, or tool crib to cell to crib in manufacturing. Verify that their rtls management console exposes API events and integrates with your CMMS or MES without brittle middleware. Confirm battery life and replacement processes with real duty cycle data, not best case lab numbers. Walk a site with them and place tape where anchors would go. If they skip this, expect budget surprises.
The right partner will welcome this conversation. They know that utilization gains depend as much on change management as on radio physics.
Scaling from one wing or cell to the whole enterprise
Start small, but not trivial. A pilot that tags five items teaches little. Choose a high impact slice with enough assets to show patterns and enough staff to need new habits. For a hospital, a med-surg wing with 150 devices across pumps, bladder scanners, and wheelchairs gives a meaningful test. For a plant, pick a value stream with two adjacent cells and 50 to 100 tools or fixtures, so you can see handoffs in context.
Expect to iterate on zone definitions and alert thresholds in the first month. Use that time to train super users who will anchor adoption when you scale. Then expand by concentric rings: add adjacent wings, then the whole floor, then the next building. Keep the architecture in mind. If you plan to grow to 10,000 tags, confirm that the rtls network scales without new licenses that torpedo your ROI.
I have rarely seen a program fail on technology alone. It fails when the sponsor changes jobs and no one owns the outcome, or when operational leaders never adopt the tool into their daily rhythm. Schedule brief weekly reviews where supervisors look at the same KPIs: idle clusters resolved, search time trends, turnaround times. If the numbers move, celebrate it. If they stall, adjust zones or responsibilities. Sustained outcomes come from attention, not just installation.
The difference between visibility and velocity
RTLS gives visibility. Utilization improves when you turn that visibility into velocity. That conversion rests on a few habits.
Tie location to action. Send retrieval alerts to the team that actually wheels equipment back, not to a shared email. Post a live board near the tool crib and empower the attendant to initiate moves.
Shorten the loop. If an asset moves to the wrong place, do not wait for the next shift to fix it. A prompt within minutes prevents pileups.
Close the loop into maintenance. When a device leaves for service, it should drop out of search results automatically. When it returns, it reenters cleanly. Shadow systems and sticky notes are where utilization goes to die.
None of that is glamorous, but it is what turns a map into time saved.
Final thought from the shop floor and the ward
Asset utilization improvements from real time location services share a pattern: they feel modest day by day, then unmistakable after a quarter. Staff stop wandering and start trusting that if the system says a pump is in clean storage, it will be there. Supervisors stop padding schedules to cover for missing fixtures. Procurement stops buying a third of something to compensate for uncertainty. The gains stick because they happen in the details of work, not in slogans.
Whether you run a hospital, a factory, or a distribution center, the same discipline applies. Pick the right technology for your accuracy needs and environment. Integrate just enough to feed the systems you already use. Measure states and times, not dots. Guard against the predictable pitfalls. And choose an rtls provider who treats your floors as the real requirement. Do that, and asset utilization will move in the one direction that matters.
TrueSpot
5601 Executive Dr suite 280, Irving, TX 75038
(866) 756-6656