The day shift is returning tags while the evening shift queues at the issue counter. The cabinet looks full, yet some devices are charging and others have not passed a connection check. A worker takes a tag, reaches the production area and returns for a replacement because it is not being observed. The inventory total looked adequate; the usable supply was not.
Consider a hypothetical US plant with shared reusable tracking devices. The right return-to-issue workflow depends on the actual model. Confirm whether it is rechargeable, has a replaceable battery or requires another service method. No single charging method or operating duration should be assumed across the tag range.
I. Count ready devices separately from returned devices
A returned tag needs identification, a condition check and the preparation steps appropriate to that model. Check its attachment hardware and connection, plus whatever battery information the actual configuration supplies. A device waiting for examination should not appear in the ready-to-issue total.
| Pool | Evidence needed | Next action |
|---|---|---|
| Returned | Physical return and previous assignment | Identify and inspect |
| Charging or service | Correct model-specific procedure | Check the required completion evidence |
| Ready to issue | Required checks and representative observation | Record a new assignment |
A device sitting in a cradle is not necessarily fully charged. Non-rechargeable models need their approved replacement or service process. Keep suspected faults in a distinct service pool rather than allowing them to circulate through the return tray.
II. Measure the circulation window, not just shift length
Required stock depends on when devices come back, how long checking and service take, and whether outgoing and incoming users overlap. A shared handover period can create demand before the previous pool is available. Record late returns separately from time spent preparing returned devices.
Transmission settings, environment and battery condition can change operating demands. Establish reserve stock from observed use and preparation times instead of choosing an unsupported universal percentage. After changing settings, repeat the check under comparable conditions. A schedule that works for one job or one shift may not support another.
III. Use ORBRO status as evidence for a defined check
ORBRO OS Device Manager supports device registration and status and connectivity monitoring. RTLS Manager provides tag and device monitoring alongside configuration results and operating history. These views help identify connection problems before issue.
Verify battery display availability, refresh behavior and any charging-complete signal for the chosen model and deployment. “Connected” does not mean fully charged or able to cover a whole shift. If the team wants automatic coordination with a charger or stock list, define the supported interface and state rules separately.
IV. End the old assignment before creating the new one
Shared tags may be issued to different people or assets on each shift. Retain the tag identifier, assigned target, start and end times and responsible issuer. Otherwise a new user’s movement may be attributed to the previous assignment. A device that has not physically returned should remain unresolved rather than being treated as available.
Check a representative working route after issue. A tag seen once at the counter has not established coverage around machinery or deep inside storage. When observations stop, examine attachment, reception conditions and configuration as well as power. Provide an operational fallback for work that cannot rely on the missing observations.
V. Log start-of-shift shortages and in-shift swaps differently
During a trial, record required devices, ready devices, service waiting and late returns at the actual start time. For an in-shift exchange, record when it occurred, where the tag was used, the confirmed cause and the new assignment. Do not label every exchange as battery depletion.
Compare similar shift duration, workloads and transmission settings. Review counter waiting, swaps and observation gaps together before adjusting stock or procedures. Retest under the different conditions represented across the shift pattern rather than relying on a single successful handover.
Closing thoughts
A returned tag and a ready tag are different operational states. Separating return, model-specific service, connection checks and reassignment makes shortages easier to explain and prevents untested devices from re-entering the issue pool.
For an ORBRO operating review, prepare the device models, users or assets per shift, issue and return schedule and required routes. Those details support a practical agreement on observable device status and the checks needed before issue.
