Wi-Fi asset tags help an organization find and manage equipment by sending observations into a location system. A useful project starts with the operational question: which zone contains a cart, whether a bin passed a doorway, or how recently an asset was observed. Choose the required answer before selecting tags or accepting an accuracy claim.
Define the location outcome
On a narrow screen, scroll the table sideways. Keyboard: focus the table and use the arrow keys.
| Required answer | Meaning for the user | Pilot evidence |
|---|---|---|
| Presence | The system recently detected this tag | Detection time and age of the last observation |
| Zone or room | The system assigns the asset to a named area | Correct assignments at boundaries and adjacent rooms |
| Position estimate | A map shows an estimated location | Error against surveyed test points and missing-result rate |
| Doorway event | A defined transition produces an event | Correct crossings, missed crossings and false events |
These outcomes can require different infrastructure. A system designed to identify a doorway crossing may use a dedicated exciter or other locating technology alongside Wi-Fi. Ask the supplier to show which component creates each result and which component transports it to the application.
Check the complete system
Draw the chain from tag to receiving infrastructure, location processing, asset database and user interface. Identify the supported access points or controllers, server or cloud service, software licenses, network configuration and any room or doorway hardware. Confirm how tag identifiers are associated with asset records and what happens when an asset is retired or a tag is reused.
A concrete example is Securitas Healthcare's T12sb datasheet, Revision A, February 23, 2026. It describes Wi-Fi communication with MobileView and separate tag variants, including an ultrasound version. Its doorway functions involve compatible exciters, and its battery-life estimate depends on configuration. Those details support a purchasing method: specify the complete variant and infrastructure, and request the assumptions behind each advertised outcome.
This guide's pilot concerns nonclinical equipment such as carts and storage bins. A healthcare manufacturer example establishes a technical dependency; it is not evidence that a particular system is suitable for an unrelated site's workflow or for tracking people.
Design a pilot that can fail clearly
Choose representative locations, including difficult boundaries, busy aisles and places where assets are commonly stored. Use the actual asset materials and intended tag mounting positions. Label the physical ground truth independently of the location application's display so the test does not merely repeat the system's own answer.
Download the asset-tag pilot worksheet. Record the tag model, firmware, reporting configuration, infrastructure version, mounting position and test time. Define the acceptable location age and the operational target before collecting results. Include stationary observations, ordinary movement, doorway transitions where relevant, and periods when the system should show that an asset has gone stale.
Have a tester record the true zone and time, then compare the application's result after the agreed observation interval. Preserve wrong results and missing results as distinct categories. A map that shows an old correct location can still mislead someone searching for an asset that has moved.
Read results with the denominator intact
In a fictional zone test with 40 scheduled observations, suppose 36 are correct, two name the wrong zone and two produce no fresh result. The correct-zone rate across all scheduled observations is 36 divided by 40, or 90%. The missing-result rate is two divided by 40, or 5%. These invented results illustrate reporting, not an acceptable threshold or a product benchmark.
Report location age and movement results alongside the percentage. A daily inventory workflow may tolerate a different delay from a cart-dispatch workflow. Set your threshold around the decision users must make and the cost of searching the wrong area.
Include maintenance and access controls
Ask how reporting intervals, movement, retries and configuration affect battery estimates. Include battery replacement labor, tag attachment checks, lost-tag handling, licensing and infrastructure support in the operating plan. Verify that the system flags an absent or stale tag in a way users can distinguish from a recently confirmed location.
Limit access to asset histories according to job responsibilities, document retention and export needs, and protect configuration credentials. Ask the supplier how updates, authentication and server connectivity are maintained. A tag's radio connection is only one part of the system's security and support lifecycle.
Make the purchase decision from the pilot
Retain the test configuration, observed failures, operating costs and acceptance decision. Require remediation and a targeted retest for failed zones or transitions. If the pilot meets the agreed outcome, document which asset types and areas were actually covered before expanding to others. That gives staff an honest basis for deciding when to trust the displayed location and when to investigate further.